Bugzilla – Bug 132502
network module not loaded after first reboot of VNC installation
Last modified: 2006-02-13 16:06:46 UTC
I installed (fresh installation, no update) a machine using VNC with the following boot parameters: vnc=1 vncpassword=secret usessh=1 sshpassword=secret install=nfs://10.12.80.30/media/cdrom It worked fine until the first reboot (into the second stage of the installation) - but then it failed terribly: the kernel module for the network card was not loaded and I could not continue the installation. As workaround, I added a modprobe command to boot.local and rebooted. With this trick, it worked. You can find the y2logs at https://bugzilla.novell.com/attachment.cgi?id=56560
So far I don't see any obvious cause in the logs. Can you describe in what way and when it failed? Please attach also /var/lib/YaST2/install.inf (there may be passwords, edit them out), the output of hwinfo --netcard, and a tarball of /etc/sysconfig/hardware. http://www.opensuse.org/Bug_Reporting_FAQ#YaST
> Can you describe in what way and when it failed? As I described: After the very first reboot (into the second stage of installation), the kernel module for the network card (ne2k-pci IIRC) was not loaded. Obviously I couldn't continue installation over the network ;-) modprobe worked fine (both entered manually on a locally connected keyboard and after a reboot in boot.local), so I guess there is no problem with the kernel module itsself. If you need more details, please ask more detailed ;-) > Please attach [...] The problematic machine isn't reachable for me at the moment, so this will take some time. I'll let this bug in needinfo state until I have the requested files.
Created attachment 61802 [details] content of /etc/sysconfig/hardware/ (as tar.gz) Sorry for the long delay, but today was the first time I could reach the problematic machine. Happy bughunting ;-) and have a good New Year!
Created attachment 61803 [details] Output of hwinfo --netcard
Created attachment 61804 [details] /var/lib/YaST2/install.inf (password changed)
I can see that the hwcfg file for ne2k-pci was written by create_interface before the reboot (comment 3). It looks like a udev problem.
Christian, any idea what's going wrong here?
No. Would be nice to have debug output from udev.
What exactly do you need? (I don't know much about debugging udev...) Again, the machine is not reachable for me at the moment - feel free to set this bug to needinfo if you need the udev debugging output.
Sorry, I can't debug that.