Hi, I *was* running SuSE 10 x86_64 with no problems up until this morning when I installed the latest security patch (a new kernel). Now I have no network connection, my system is running at a snail's pace, and I can't even reboot the machine. I'm used to having to recompile my Nvidia graphics driver, and reconfigure vmware whenever I get a new kernel like this. Now the problem I seem to have is with my on-board NIC. In the past I have used Nvidia's nvnet kernel module to support the CK804 network interface, but this now seems to be screwed. Has anyone else noticed this behaviour? Anyone using an Nforce4 motherboard might think twice before applying this update, rather than just accepting it as I did. Any hints/tips on how I might fix this would be greatly appreciated. Sys details: Giga-byte Ultra9 Nforce4 mobo Athlon64 X2 4400+ SuSE 10.0 x86_64 Yours, Jon -- Jonathan Brooks (Ph.D.) Research Fellow PaIN Group, Department of Physiology Anatomy & Genetics Le Gros Clark Place, University of Oxford, South Parks Road, Oxford, OX1 3QX tel: 01865-282654 fax: 01865-282656
Okay please ignore my previous email - a hard reboot fixed it(?). God know why. Cheers, The-boy-who-cried-wolf Jonathan Brooks wrote:
Hi,
I *was* running SuSE 10 x86_64 with no problems up until this morning when I installed the latest security patch (a new kernel). Now I have no network connection, my system is running at a snail's pace, and I can't even reboot the machine.
I'm used to having to recompile my Nvidia graphics driver, and reconfigure vmware whenever I get a new kernel like this. Now the problem I seem to have is with my on-board NIC. In the past I have used Nvidia's nvnet kernel module to support the CK804 network interface, but this now seems to be screwed. Has anyone else noticed this behaviour?
Anyone using an Nforce4 motherboard might think twice before applying this update, rather than just accepting it as I did.
Any hints/tips on how I might fix this would be greatly appreciated.
Sys details:
Giga-byte Ultra9 Nforce4 mobo Athlon64 X2 4400+ SuSE 10.0 x86_64
Yours,
Jon
-- Jonathan Brooks (Ph.D.) Research Fellow PaIN Group, Department of Physiology Anatomy & Genetics Le Gros Clark Place, University of Oxford, South Parks Road, Oxford, OX1 3QX tel: 01865-282654 fax: 01865-282656
Hi Jonathan, * On Thu, May 25, 2006 at 12:57 PM (+0100), Jonathan Brooks wrote:
I *was* running SuSE 10 x86_64 with no problems up until this morning when I installed the latest security patch (a new kernel). Now I have no network connection, my system is running at a snail's pace, and I can't even reboot the machine.
I noticed such a strange behaviour at my system, too. I am using SuSE 10.0 x86_64, kernel vanilla-2.6.16.18 on an AMD Athlon X2 4800+, EPOX 9NPA+ Ultra (nForce4 Ultra chipset): Sometimes it happens that I don't have onboard sound, network and USB support after booting up. As far as I found out (it hasn't occured often enough to let me have a systematic look for the failure): - just a "reboot" doesn't seem to help. After booting up, the failure will be there again. - but, like it happened to you, "shutdown" and "power on" has solved it whenever it happend. - just doing a "/etc/rc.d/boot.coldplug restart" seems to fix it without rebooting or shutting down - a few seconds after entering this command, the devices seem to come up normally. I am not absolutely sure, but it also seems that it rather happens after the system was "hard powered off" (powered off using the power supplys's switch on the computer's rear side), but, as I said before, I haven't investigated it systematically, so I cannot say if this really triggers it.
Anyone using an Nforce4 motherboard might think twice before applying this update, rather than just accepting it as I did.
Any hints/tips on how I might fix this would be greatly appreciated.
Sys details:
Giga-byte Ultra9 Nforce4 mobo Athlon64 X2 4400+ SuSE 10.0 x86_64
Our systems are indeed quite similar (same CPU series, same chipset, same distribution version). The main difference seems to be the kernel version. So perhaps you could try to restart "coldplug" if it happens again and see whether it helps. If so, it will be a strong indication that we are really experiencing the same problem. Best regards, Steffen
Steffen Moser wrote:
Hi Jonathan,
* On Thu, May 25, 2006 at 12:57 PM (+0100), Jonathan Brooks wrote:
I *was* running SuSE 10 x86_64 with no problems up until this morning when I installed the latest security patch (a new kernel). Now I have no network connection, my system is running at a snail's pace, and I can't even reboot the machine.
I noticed such a strange behaviour at my system, too.
I am using SuSE 10.0 x86_64, kernel vanilla-2.6.16.18 on an AMD Athlon X2 4800+, EPOX 9NPA+ Ultra (nForce4 Ultra chipset):
Sometimes it happens that I don't have onboard sound, network and USB support after booting up. As far as I found out (it hasn't occured often enough to let me have a systematic look for the failure):
- just a "reboot" doesn't seem to help. After booting up, the failure will be there again.
- but, like it happened to you, "shutdown" and "power on" has solved it whenever it happend.
- just doing a "/etc/rc.d/boot.coldplug restart" seems to fix it without rebooting or shutting down - a few seconds after entering this command, the devices seem to come up normally.
I am not absolutely sure, but it also seems that it rather happens after the system was "hard powered off" (powered off using the power supplys's switch on the computer's rear side), but, as I said before, I haven't investigated it systematically, so I cannot say if this really triggers it.
Anyone using an Nforce4 motherboard might think twice before applying this update, rather than just accepting it as I did.
Any hints/tips on how I might fix this would be greatly appreciated.
Sys details:
Giga-byte Ultra9 Nforce4 mobo Athlon64 X2 4400+ SuSE 10.0 x86_64
Our systems are indeed quite similar (same CPU series, same chipset, same distribution version).
The main difference seems to be the kernel version.
So perhaps you could try to restart "coldplug" if it happens again and see whether it helps. If so, it will be a strong indication that we are really experiencing the same problem.
Best regards, Steffen
I have been experiencing similar things on my Compaq Presario 3240 AMD64-based laptop (with nVidia nForce 3 chipset) with SuSE 10 and kernel of the day 2.6.16. I thought it was because I enabled full pre-emption. I found out that the necessary modules do not load sometimes. So, if I have no ethernet or sound, I load the appropriate modules as root ('8139too' for the built-in ethernet and 'snd_intel8x0' for the sound), run 'rcalsasound restart' as root, and all is fine afterwards. (I manually invoke 'dhcpcd eth0' all the time.) I observed that whenever I had no sound, I also had no ethernet and vice- versa. I did not try USB when I had no ethernet and no sound. I would think that the situation with USB would be different because when a USB device is attached, that is supposed to generate a hotplug event, which should cause the necessary modules to load. CF -- Running 64-bit Linux on AMD64
Hi, * On Mon, May 29, 2006 at 07:52 AM (-0400), Constantine 'Gus' Fantanas wrote:
I have been experiencing similar things on my Compaq Presario 3240 AMD64-based laptop (with nVidia nForce 3 chipset) with SuSE 10 and kernel of the day 2.6.16.
That's quite interesting as it seems that it isn't a special problem of the nForce4 Ultra.
I thought it was because I enabled full pre-emption.
At least I can't confirm this. I've configured the kernel's pre- emption property as "Preemption Model (Voluntary Kernel Preemption (Desktop)". I suppose that you mean "Preemptible Kernel (Low-Latency Desktop)" with "full pre-emption", don't you?
I found out that the necessary modules do not load sometimes. So, if I have no ethernet or sound, I load the appropriate modules as root ('8139too' for the built-in ethernet and 'snd_intel8x0' for the sound), run 'rcalsasound restart' as root, and all is fine afterwards.
I think that this would solve it in my case, too. Most probably the reinitializing of "coldplug" does just the same thing.
(I manually invoke 'dhcpcd eth0' all the time.) I observed that whenever I had no sound, I also had no ethernet and vice- versa.
Yes, exactly the same here.
I did not try USB when I had no ethernet and no sound.
As I use an optical mouse that is connected via USB I recognize the occurence of the problem at first when looking at the mouse when the login screen appears - when the problem occurs, the mouse's LED stays just dark, it doesn't move (of course) and then I can be sure that the NIC and the sound are dead, too.
I would think that the situation with USB would be different because when a USB device is attached, that is supposed to generate a hotplug event, which should cause the necessary modules to load.
That's quite possible as I haven't tried to unplug and reconnect the USB mouse, yet. The next time it happens I will try to have a closer look. Perhaps I can find any reasons (looking at the kernel ring buffer and the log files) why the loading of the modules fails. Best regards, Steffen
participants (3)
-
Constantine 'Gus' Fantanas -
Jonathan Brooks -
Steffen Moser