7 Aug
2009
7 Aug
'09
16:54
... >> Which Suse Version ? >SuSE 10.3 32bit >> Which hardware is used ? >Giga-byte RTL 8111/8168B PCI Express Ethernet Controller >> - Is the correct network driver loaded ? >Yes, i think so. It is the same driver which is loaded during manual >installaiton. Does the driver from the initrd has the same version as the one from the DVD ? ... >> - Are you able to do a manual installation meaning configuring the >> network by hand ( Select driver , set IP a.s.o ) What I was trying to say was: Can you after a failed network installation - YAST simply say it does not find the installation source or what so ever - * Unload any network driver. * Select from yast the correct driver * Load the driver * Configure the network and installation source * Ping the adapter from another machine. With these steps we will simple check whether or not a network driver gets loaded and activated. In case it will work: - Either YAST loads the wrong adapter during initial boot or - you need to set the netwait option on the command line to give the adapter some time to initialize. In case YAST loads the wrong adapter you can supply an "insmod: Mydriver" on the command line as well. NOTE: I do not know the correct syntax for giving "info" file options on the "append" section of the kernel command line. So I use an info file since ages. In case it will not work at all. - Check on the command line during a network installation if ifconfig will show an interface (eth) at all - I think on TTY4 (press F4) is the command line during installation - In case you see a eth device check that the value for in/out trffic is larger then zero . - Test with dhcpcd - Machine can not be pinged from another node on the network but an eth device exist- check for dmesg error on the command line as well. Then I would say that the network driver from the initrd is different or missing then that from the DVD. Thus you have to find out the driver file and version from the initrd on your boot server and compare this information with the version on the DVD AS WELL as from an installed system which has been installed via DVD. In the past I had an issue where I had to update the initrd with another driver. ... >> Broadcom Card was named a litte bit different. >What do you mean with "named a little bit different"? I do not have the details anymore. But basicly the broadcom driver ( I think it was tg3) was loaded during network installation without any error but no eth device got configured due to the fact that the name of the device changed from something like ABC1000x ( PCI-e ) to ABC1000e ( PCI Express ) hth Hajo -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org