Dustpuppy

I've now installed 2005, run all the updates for that, changed the source, updated urpmi and then did --auto-select. It's currently on package 320 out of 450 and no problems.

Urgh. Urpmi urpmi on a newly installed system gave segmentation fault :( I gave my LE discs to my brother, so I'm currently burning some more as it might work better from that that 10.1. Oh well.

Thanks! I'm getting the feeling that a basic re-install of 10.1 followed by an urpmi update will be the way to go: I think you're right and the current installation is rather trashed. Luckily everything's backed up, so it'll be annoying rather than a disaster. Unless anyone thinks my system can be raised from the dead as it is?

Ah, that's the secret. Urpmi urpmi gives segmentation fault How do I force an install from the discs?

I decided to update my 10.1 box straight to 2006. Set the sources to 2006 via easyurpmi and then urpmi --auto select. It got to the 72nd package and found something to do with GLIBC that it didn't like, tried to restart urpmi and then came up with segmentation fault (core dumped). I restarted into command line mode, but anything to do with urpmi (even urpmf) gets the segmentation fault error returned. I can't start X because of a GLIBC error. Help! What do I do? I can't install 2006 straight as I don't have access to the .iso's!

What's the output of "glxinfo" (su to root first)?

I'm being a bit dense here - are the 2006 mirrors there for anyone, or just the club members? I can't find 2006 on easyurpmi...

Cool B)

You do know that this board is nothing to do with the company Mandriva? It's a collection of autonomous individuals who help because they want to. And quite frankly at the moment you are not exactly making me want to help you. Got a beef with Mandriva? Go yell at them, not us.

Have you tried this? let's-eat-gary's thread

Or you can get a run prompt up by doing alt-F2 and then type in "kdesu" followed by the command. Eg to open the /mnt folder as root in Konqueror, do "kdesu konqueror /mnt". A prompt will then come up asking for your root password. Give it, and away you go.

"Install software" is look at stuff you DON'T have. "Browse installed software" is look at stuff you DO have.

This appears to have been fixed in 1.5 beta, which is useful.

It's certainly better than that truly freaky penguin (I don't have a graphical boot for that reason!). However, it does strike me as vaguely reminisent of Stalinist art posters - the brave Penguin looks boldly into the future, defying all enemies of truth and justice... But definitely an improvement. Doesn't give you the feeling that the graphic designer was having a bad trip on something distinctly illegal.

Thanks for that - I gave it a go, but no luck. I've currently disassembled the thing as far as it will go, and I can't find anything that looks like a jumper/switch/anything at all that will change position. The manual is currently sitting in my old office which is 90 mins away and to which I don't have easy acess. Humph.

It's soldered in - would I need to invest in a soldering iron? Is it something that can be done at a DIY level?

Having found that I really can't do without my laptop, I'm trying to resurrect my old and dead one. Much googling has lead to the idea that resetting the cmos might help. After taking the thing apart (a very frustrating exercise) I've located the cmos. Unfortunately, everything that I can find online about how to reset it doesn't apply. It's a round brown and silver battery about the size of a 1 eurocent piece (just smaller than a 1p piece), it's soldered onto the mobo and there are no visible jumpers near it. So does anyone know how to reset a cmos like this?

Try a text-based install: at the prompt, press F1 and then enter "text" as the install option. That should get around the ram problem.

Where did it hang? I can imagine it wouldn't be happy with a GUI install with that little ram - did it get that far? And did you burn your CDs at a nice slow speed to prevent bad burns?

Deer Park Alpha started off as nice and fast on my system, and then as soon as I clicked to make this comment, it started spending ages at the "looking up..." bit. So the solution to the mystery is: Firefox is sentient, and has a cute sense of humour. "I'm sorry Dave, I can't let you click that."

I had this problem a lot with 10.1 and a new Netgear router - when you click, it would spend ages looking up the site and then connecting to it. I upgraded the firmware and that helped a lot, and then I looked at the DNS servers (via the mcc, not on the router which gets them automatically from the isp) and saw that the primary server was 127.0.0.1. I removed that and things were perfect. Then I ugraded to 10.2 then LE and no problems... but now, for no apparent reason, it's started doing it again. I found that 127.0.0.1 had crept back again, but removing it and doing to firefox tweaks haven't got it fully back to speed again. No idea what's happened there!

LE will install fine on your system. The only issues there might be are with display managers, but even there you should be fine with all as most of the time ram is the limiting factor. It all depends how much eye-candy you want. KDE might run a bit slow if you want it to do lots of fancy things. Gnome is generally lighter so might be a good first choice. If you want a very fast display manager, go with Icewm - a bit of a learning curve, but plenty of documentation and you can always ask about stuff here. Icewm has fewer bells and whistles, but you can get some very funky themes for it. Go for it, and fiddle if it doesn't do what you want it to do.

As indeed it is - see sig, desktop 3.

It's now purring like a kitten B) . New fan installed, I went for a decent £10 one, and it's working so well that I even put Mandrake on it. It locked up once during the install, but I've had several hours of uptime since with no problem. And you can no longer use the case as a barbeque. Now all I need is some more ram. Thanks all!

I've just been given a very elderly HP that I'm trying to resurrect as an abiword/firefox machine (64 MB ram, 800MHZ Athlon). I've had to put in a new harddrive (160GB, maxtor) as the old one was screwed completely by windoze and adware/virii. I've put Damn Small Linux on it as I don't think it would cope with Mandy, even with Icewm or fluxbox. It installed fine, but there seems to be problems with overheating. After about half an hour (from a cold start) it will lock up completely, to the extent that a hard switch-off is the only thing that will work. It's also scorchingly hot. As far as I can tell, the heat is coming from the processor's heatsink. The fan that's over the heatsink (rather than the power unit fan) isn't working, so the obvious thing to do is replace the fan - but what I wanted to ask was if this sounds like an overheating problem or something else. Do you reckon this will be solved by a new fan, or is the system just screwed? Cheers!