Network doesn't come up unless I run Yast?
I just installed Suse 9.3 on a new machine with an Intel D945GTP mobo which uses Intel 82573V/82574V ethernet controller.
During the install, yast found the NIC & I configured it with static IP, DNS, and Gateway; and I assigned it a host and domain name. When I reboot the machine, the NIC does not come up. If I run ifconfig, it only shows the loopback. If I /etc/init.d/network restart, I still only getthe loopback. However, if I run yast, click on "Network Controllers" and let it look for available controllers, the NIC comes up, with my configuration... and at that point, if I run ifconfig, it shows the NIC. Why must I run Yast for the NIC to work? |
Hi,
Not sure if my problem was related to yours, I have managed at long last to get Wireless lan connectivity using ndiswrapper. I also had the problem that after boot the network was not there. In my case if I logged on as root, the wireless wlan0 connection would come up but if I logged on as 'ordinary Joe' user - it would not. I know with Linux there seems to be many ways to resolve the same problem and in my case I added the module to be modprobed - ndiswrapper - to the entry in Yast : Yast Network devices Network card Select your card Then edit button advanced hardware details module name 'ndiswrapper' [in my case] then closed out. It may be that your card needs a module loaded? Now when I boot the wlan0 service boots on startup. Additionally, Check in Yast Yast Network devices Network card Select your card Then edit button advanced Detailed settings -ensure 'device activation' is set to 'at boot time'. then closed out. Regards Joe Linux Noob :p |
Quote:
I ran 'lsmod >> foo' before running yast, then 'lsmod >> bar' after running yast & diff'd them. Sure enough, e1000 was not loaded until yast ran. Following your steps above, I entered 'e1000' for the module name & am all set. Thanks for the tip! |
All times are GMT -5. The time now is 05:01 PM. |