OK, just installed Slack 10.2 with the 2.6.13 kernel. When I do a ifconfig I do not see the eth0. I can do an 'lspci' and this is what shows up....


root@GEEK:~# lspci
00:00.0 Host bridge: Silicon Integrated Systems [SiS] 735 Host (rev 01)
00:01.0 PCI bridge: Silicon Integrated Systems [SiS] Virtual PCI-to-PCI bridge (AGP)
00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS85C503/5513 (LPC Bridge)
00:02.1 SMBus: Silicon Integrated Systems [SiS] SiS961/2 SMBus Controller
00:02.2 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 07)
00:02.3 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 07)
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0)
00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] Sound Controller (rev a0)
00:03.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 90)
00:09.0 VGA compatible controller: Trident Microsystems CyberBlade/XP (rev 63)
00:0d.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 0c)
root@GEEK:~#

As you can see I have 2 nic cards there. They are both set * in the kernel.

Any Ideas?????????

Can you do a ifconfig eth0 up ?? Once its up you can run dhclient eth0 or whatever you use to get a IP address with. Im sure theres a way to point it to a specific card you want but im not sure how. You would have to read the man page for that.

I have a SiS900 NIC on my slackware machine that also has two NICS and had this happen and the above fixed it. I simply took the easy way out and modified rc.local with
ifconfig eth0 up
ifconfig eth1 up
dhcpd eth0
adsl-start



If the above works then you probably got a problem with the network initialization script, most likely just not set with the execute bit and so the boot script skips running it.. just a guess. Thats probably completely wrong but Ive seen it in my LFS systems a few times before. I never bothered to actually find the cause for mine doing this, it worked so I left it at that - just a test box anyway.

did you run " netconfig " after the installation ?
if not, do that .

then run /etc/rc.d/rc.inet1 restart
( all as root )

egag

Thanks for the response....

I recieve an 'eth0: unknown interface: No such device' during the boot up.

I have tried all the above with no joy. Any other recommendations?

If u did full install with test26.s kernel then u will need modules,alsa driver,?headers,source for 2.6.13 kernel on installcd2. ( u should remove 2.4.31 kernel,etc 1st if u didnt do this during install. ) Installpkg or pkgtool can help.
lspci and lsmod can help see if correct driver/module for ur nic is installed. check etc/rc.d/rc.modules to see if correct module in uncommented.
if u use dsl connexn slw10.2 uses pppoe-setup instead of former adsl-setup. Good luck.

ok I went into rc.modules and uncommented my nic cards. I also checked the kernel to make sure that the drivers were there. Should I be leaving the drivers as [M] or[*]? When I reboot I get 'Module not found eepro100' and also one for the SIS900. When I make changes to the kernel and save it, I do a 'make && make modules_install' then reboot. Is this correct?

Sorry for the ignorance..........and thanks for the help.

I only said that if u did 10.2 full install with test2.6s(2.6.13) kernel then the rest of setup will use
default 2.4.31kernel modules,alsa driver,headers, and source. This will cause errors with modules and drivers. Pkgtool or removepkg can help remove the default ones.
( Picking test26.s kernel then doing expert install allow u to uncomment the 2.4.31 stuff earlier.)
If so then install 2.6.13 source,modules,maybe headers,and alsa driver available on 2nd install cd at 2.6.13 directory. pkgtool can install them as long as u tell it what directory on cd2 to install from. Then reboot. This doesn't require make....steps.
If u rolled ur own 2.6x kernel then others will have to help u further.