SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I install Slackware 12 and have eth0, eth1, eth2 and lo according to ifconfig -a. I do nothing but reboot and ifconfig shows I have eth1, eth2, eth3 and lo !!
Where did eth0 go and where did eth3 come from?
I install Slackware 12 and have eth0, eth1, eth2 and lo according to ifconfig -a. I do nothing but reboot and ifconfig shows I have eth1, eth2, eth3 and lo !!
Where did eth0 go and where did eth3 come from?
Hi,
From cli (command line);
Code:
~#dmesg | grep eth #see the eth devices
~#lspci -vv #see the devices information
~#ifconfig -a #know devices at boot
You should see all the known devices and associate the assignments to each.
The 'ifconfig' will give you only the active devices and the 'ifconfig -a' will give you all known devices (whether up or down). Do a 'man ifconfig' to see the options.
Look at the assignments for the output of the commands to see what was assigned.
Where to start?
Apologies for my spelling (past, present & future).
I am running a cable modem connected by USB on an asus mother board with nVidia nForce2 MCP networking adaptor on eth0 Marvell Gigabit LAN on eth1 and iee1394 on eth2. I don't use any firewire or LAN devices.
I have no problems using the net on eth0 with Slk 11.0 on kernel 2.4.n or Mandriva 2007 on kernel 2.6.n so I am assuming I don't have a hardware problem.
I know a bit about computers (well you would have to if you want to install Slackware) but not much about networking so can you check my installation details. I set /dev/modem to ttys0 because I always have, I set up networking as - my ip address = 192.168.1.100 because that is what I got from Kinfocenter/Networkinterfaces, netmask = 255.255.255.0 because it always seems to be that, gateway = 192.168.1.1 because the install sets it that way and it seems to work, nameserver = 203.87.88.1 because that is the ip address of my isp.
I have tried all 4 kernels that come with the install as well as every combination of /dev/modem and static ip or dhcp I could think of. The above setup is the only one that seems to let get on the net but only on the first boot.
Here is the info I have
from dmesg | grep eth
forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.60.
eth0: forcedeth.c: subsystem: 01043:80a7 bound to 0000:00:04.0
eth1: Yukon Gigabit Ethernet 10/100/1000Base-T Adapter
eth2: register 'cdc_ether' at usb-0000:00:02.0-2, CDC Ethernet Device, 00:30:0a:44:7a:14
usbcore: registered new interface driver cdc_ether
from lsconfig -a after the first boot after the install
eth0 Link encap:Ethernet HWaddr 00:00:6C7:E3:85
inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::200:6cff:fed7:e385/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:468 (468.0 b)
Interrupt:17 Base address:0xa000
this is the only time I get eth0.
Last time I looked I had eth1, eth2 & eth11. It seems to increase by 1 every time I reboot.
This is from /var/log/debug
Aug 4 01:30:47 nyloc kernel: eth0: no IPv6 routers present
as you can see from the time stamp (see below) this was the first boot so is it relevant (it is the only message like that in the file).
this an edit of /var/log/messages
Initial boot
Aug 4 01:30:28 nyloc syslogd 1.4.1: restart.
Aug 4 01:30:28 nyloc kernel: klogd 1.4.1, log source = /proc/kmsg started.
Aug 4 01:30:28 nyloc kernel: Linux version 2.6.21.5-smp (root@midas) (gcc version 4.1.2) #2 SMP Tue Jun 19 14:58:11 CDT 2007
Aug 4 01:30:30 nyloc logger: /etc/rc.d/rc.inet1: /sbin/route add default gw 192.168.1.1 metric 1
Aug 4 01:30:30 nyloc logger: /etc/rc.d/rc.inet1: /sbin/route add default gw 192.168.1.1 metric 1
Aug 4 01:30:30 nyloc logger: SIOCADDRT: No such process
Aug 4 01:30:30 nyloc logger: /etc/rc.d/rc.inet1: /sbin/ifconfig eth0 192.168.1.100 broadcast 192.168.1.255 netmask 255.255.255.0
Aug 4 01:30:30 nyloc logger: SIOCADDRT: No such process
Aug 4 01:30:30 nyloc logger: /etc/rc.d/rc.inet1: /sbin/route add default gw 192.168.1.1 metric 1
Aug 4 01:30:30 nyloc logger: /etc/rc.d/rc.inet1: /sbin/ifconfig lo 127.0.0.1
Aug 4 01:30:30 nyloc logger: /etc/rc.d/rc.inet1: /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo
Aug 4 01:30:36 nyloc kernel: NET: Registered protocol family 10
Aug 4 01:30:36 nyloc kernel: lo: Disabled Privacy Extensions
reboot
Aug 4 01:36:52 nyloc syslogd 1.4.1: restart.
Aug 4 01:36:52 nyloc kernel: klogd 1.4.1, log source = /proc/kmsg started.
Aug 4 01:36:52 nyloc kernel: Linux version 2.6.21.5-smp (root@midas) (gcc version 4.1.2) #2 SMP Tue Jun 19 14:58:11 CDT 2007
Aug 4 01:36:54 nyloc logger: /etc/rc.d/rc.inet1: /sbin/route add default gw 192.168.1.1 metric 1
Aug 4 01:36:54 nyloc logger: /etc/rc.d/rc.inet1: /sbin/route add default gw 192.168.1.1 metric 1
Aug 4 01:36:54 nyloc logger: SIOCADDRT: No such process
Aug 4 01:36:54 nyloc logger: SIOCADDRT: No such process
Aug 4 01:36:54 nyloc logger: /etc/rc.d/rc.inet1: /sbin/ifconfig lo 127.0.0.1
Aug 4 01:36:54 nyloc logger: /etc/rc.d/rc.inet1: /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo
Aug 4 01:36:54 nyloc logger: /etc/rc.d/rc.inet1: /sbin/route add default gw 192.168.1.1 metric 1
Aug 4 01:36:54 nyloc logger: SIOCADDRT: No such process
Aug 4 01:36:55 nyloc kernel: NET: Registered protocol family 10
Aug 4 01:36:55 nyloc kernel: lo: Disabled Privacy Extensions
rebooot with non smp kernel
Aug 4 13:20:38 nyloc syslogd 1.4.1: restart.
Aug 4 13:20:38 nyloc kernel: klogd 1.4.1, log source = /proc/kmsg started.
Aug 4 13:20:38 nyloc kernel: ter generic identify, caps: 0383fbff c1c3fbff 00000000 00000000 00000000 00000000 00000000
Aug 4 13:20:40 nyloc logger: /etc/rc.d/rc.inet1: /sbin/route add default gw 192.168.1.1 metric 1
Aug 4 13:20:40 nyloc logger: SIOCADDRT: No such process
Aug 4 13:20:40 nyloc logger: /etc/rc.d/rc.inet1: /sbin/route add default gw 192.168.1.1 metric 1
Aug 4 13:20:40 nyloc logger: SIOCADDRT: No such process
Aug 4 13:20:40 nyloc logger: /etc/rc.d/rc.inet1: /sbin/ifconfig lo 127.0.0.1
Aug 4 13:20:40 nyloc logger: /etc/rc.d/rc.inet1: /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo
Aug 4 13:20:41 nyloc logger: /etc/rc.d/rc.inet1: /sbin/route add default gw 192.168.1.1 metric 1
Aug 4 13:20:41 nyloc logger: SIOCADDRT: No such process
Aug 4 13:20:42 nyloc kernel: NET: Registered protocol family 10
Aug 4 13:20:42 nyloc kernel: lo: Disabled Privacy Extensions
So it seems I am missing some software
I have looked at lsmod from this install as well as from Slk 11 and Mandriva and cannot see anything that should be relevant in their lists that is not in Slk 12. Nor is there any difference between first and subsequent boots in content but there is a difference in order.
So how do I find out what I need?
Nothing in /var/log tells what I am missing
WHAT I REALLY WANT TO KNOW IS WHY IT WORKS ON THE FIRST BOOT !!!!!!!!!!!!!!!!!!!!!!!!
I have been chasing red geese and wild herrings for 4-5 days because of that.
Some of the settings for static ip and dhcp I tried resulted in Firefox not working (it would not find the site in the startup script and took about 5 minutes to fail) but konqeror would work fine as a net browser. Can anyone explain that red herring?
If you use the non-smp generic kernel, please read /extra/linux-2.6.21.5-nosmp-sdk/README.TXT.
I have also a ASUS motherboard with nVidia nForce2 networking adaptor. At initial boot it was correctly detected by kernel, but at second don't. I had to disable acpi (append="acpi=off" in /etc/lilo.conf) and my network adapter work again. I use a generic-non-smp 2.6.21.5 kernel too.
~#dmesg | grep eth #see the eth devices
~#lspci -vv #see the devices information
~#ifconfig #show what is active
~#ifconfig -a #know devices at boot
~#lsmod #show modules
Post the output of the commands in a vbcode window (# or Quote at top of reply window).
It's possible I have dodgy install cd's so that might make recompiling the kernel a good idea.
However I learned long ago not to compile the current kernel and compiling a newer kernel won't tell me what's wrong with the current one.
On the other hand if I use .config from /boot as the config file I should be able to replicate the install kernel and modules.
Or is that idea just another wild goose?
"I love traffic lights, but only when they are green"
I see too many "Unknown device" in your lspci -vv output. What motherboard model do you have exactly? I suspect is not a clean ASUSTeK Computer Inc. A7N8X Mainboard.
With the problems for the eth devices, I suspect the rules. The nethelper.sh detects the devices an creates the '/etc/udev/rules.d/75-network-devices.rules' at boot time. The increment of the device number puzzles me. Did you modify the permissions for the '/etc/udev/rules.d' files?
As to;
Quote:
It's possible I have dodgy install cd's so that might make recompiling the kernel a good idea.
However I learned long ago not to compile the current kernel and compiling a newer kernel won't tell me what's wrong with the current one.
On the other hand if I use .config from /boot as the config file I should be able to replicate the install kernel and modules.
Or is that idea just another wild goose?
Where did you get your Slackware 12.0 iso? Downloaded iso? If so cdrom/dvd? Did you check the iso .md5? Not just rely on a check with k3b or whatever.
If you downloaded the cd/dvd iso then be sure to check the md5sum for the original iso. From the cli;
Code:
~#cd /downloadisolocation #cdromiso.iso cdromiso.md5
~#md5sum -c cdromiso.md5 #substitute the correct name to check
This will check the download iso with the known md5sum that you should also get when you download the iso.
You could have a bad burn, to check the cd/dvd with the original iso md5, use this CdromMd5sumsAfterBurning.
A little work on your part to check the cd/dvd to original iso but worth the effort. If a bad burn then you could slowdown the image burn speed. Be sure the media is matched to your device!
You should also read the CHANGES_AND_HINTS.TXT, RELEASE_NOTES and UPGRADE.TXT to get some helpful information. As PV states, you should try to use one of the smp kernels if possible.
Quote:
It's possible I have dodgy install cd's so that might make recompiling the kernel a good idea.
If your cd(s) are bad, then you should correct that first. The compile of a kernel will not solve that issue.
I haven't directly modified permissions /etc/udev. As I said I know little about networking.
/etc/udev/rules.d/75-network-devices.rules
Quote:
# Local network rules to name your network cards.
#
# These rules were generated by nethelper.sh, but you can
# customize them.
#
# You may edit them as needed.
# (If, for example, your machine has more than one network
# card and you need to be sure they will always be given
# the same name, like eth0, based on the MAC address)
#
# If you delete this file, /lib/udev/nethelper.sh will try to
# generate it again the next time udev is started.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
7:E3:85 
