electragician

I would think the solution was more in the bios update than the kernel, but you never know ;) My nForce2 board (Asus A7N8X Deluxe Rev 1.04) has worked flawlessly in Mandrake 10 CE and now 10 OE, but I've always kept the bios updated. I'm currently running the latesest available kernel from the 10OE update sources, but I've had no trouble with the other kernels I've tried. I also don't run any boot options such as "noapic" etc... never had to, and my USB devices all work just great.

I had the exact same problem, and never did find a fix. One of the updates a couple of weeks back screwed up Python (I believe thats what BT and Shadows Experimental both used. Both programs would attempt to load, and then die. I never did find a fix, and then reformatted and installed another distro out of curiosity.Now I'm back to my favorite (Mandrake 10.0 CE of course) and everything is fine... but I've only installed a few updates due to the mirror fiasco. As a temporary fix, if you can't figure out what the problem is with BT you can always get Azureus and use it, as it's java based.

You guys are great :) I'm a newbie and have been battling this problem the past couple of days, and this is definitely a bug due to an update, I'd think, as I'm seeing the exact same thing. I decided a reinstall of the nvidia drivers might be in order, and in doing some reading up to reinstall them, noticed there was a new kernel available. (2.6.3-7 or some such, from memory). I grabbed it, grabbed it's source, configured Lilo to use it as the default kernel, and then reinstalled the nVidia drivers. Thats when I realised the problem all along was that my XF86Config-4 being overwritten at boot. Just popped in here to see if anyone else was having the same problem, and now I find the fix waiting here patiently for me to read ;) Another work around, and the one that I've been using thus far, is to let the system load, su to root, use editor of choice to edit and save the updated XF86Config-4 file and then init 3 ,then init 5. System would work flawlessly that way and load the correct drivers (as Harddrake is already loaded I guess, and not looking for new hardware at that point). It's a pain, but does work. Edit: How can I tell if someone has submitted this to Mandrake in a bug report? I looked at the FAQ but didn't see anything about submitting bugs, etc...