--
Dan Amborn
dam...@newsguy.com
you can assigned via an alias the module with one card in
/etc/modprobe.d/my_eth
---bof---
#assigned integrated nforce2 to eth0
alias eth0 forcedeth
#assigned the other pcicard to eth1
alias eth1 other_module
---eof---
good luck \o_
Whoa I thought this was going to work...but it didn't. I almost feel
I need a psycic to figure out what eth0 and eth1 are going to be
sometimes. Here is the file I made for myself from the info you gave
me. I named it ethernet and dropped it in /etc/modprobe.d
<start of file>
# These aliases are used so they are assigned correctly
# and consistantly using the 2.6 kernel series.
# This is placed in /etc/modprobe.d/
#assigned Digital DS21140 Tulip to eth0
alias eth0 tulip
#assigned Intel PRO/1000 to eth1
alias eth1 e1000
<end of file>
--
Dan Amborn
dam...@newsguy.com
>Whoa I thought this was going to work...but it didn't. I almost feel
>I need a psycic to figure out what eth0 and eth1 are going to be
>sometimes. Here is the file I made for myself from the info you gave
>me. I named it ethernet and dropped it in /etc/modprobe.d
>
>
><start of file>
># These aliases are used so they are assigned correctly
># and consistantly using the 2.6 kernel series.
># This is placed in /etc/modprobe.d/
>
>#assigned Digital DS21140 Tulip to eth0
>alias eth0 tulip
>
>#assigned Intel PRO/1000 to eth1
>alias eth1 e1000
><end of file>
What does dmesg say about eth0 and eth1? Does this vary between boots?
Are tulip + e1000 compiled as modules? Udev enabled?
2.6.18.3 touches the e1000 driver, might be worth a try.
Grant.
--
http://bugsplatter.mine.nu/
> I am running Slackware 11.0. I installed the latest kernel 2.6.18.2
> from 2.4.33.3 and now my eth0 and eth1 change randomly each time I
> reboot. Never did this running the 2.4 kernel. Is there a work
> around for this. This is my first time running the 2.6 kernel.
See /etc/udev/rules.d/network-devices.rules
--
I do not approve anything that tampers with natural ignorance.
Ignorance is like a delicate exotic fruit; touch it and the bloom
is gone.
>What does dmesg say about eth0 and eth1? Does this vary between boots?
>Are tulip + e1000 compiled as modules? Udev enabled?
>
>2.6.18.3 touches the e1000 driver, might be worth a try.
>
>Grant.
Yes it does vary between boots and both are compiled as modules with
udev enabled. It can be pretty consistant for a while and then bam it
can vary every boot. It seems to be more consistant if I power it
down. Most of the time when I power it down the e1000 driver gets set
as eth0 which is the opposite of what it was with 2.4. I'll try
2.6.18.3 and see what it does. Here is the complete dmesg.
Linux version 2.6.18.2 (root@Anakin) (gcc version 3.4.6) #1 Tue Nov 7
20:12:29 CST 2006
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f400 (usable)
BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000001fef0000 (usable)
BIOS-e820: 000000001fef0000 - 000000001fef3000 (ACPI NVS)
BIOS-e820: 000000001fef3000 - 000000001ff00000 (ACPI data)
BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
0MB HIGHMEM available.
510MB LOWMEM available.
On node 0 totalpages: 130800
DMA zone: 4096 pages, LIFO batch:0
Normal zone: 126704 pages, LIFO batch:31
DMI 2.2 present.
Allocating PCI resources starting at 20000000 (gap: 1ff00000:ded00000)
Detected 2231.227 MHz processor.
Built 1 zonelists. Total pages: 130800
Kernel command line: BOOT_IMAGE=Linux-26 ro root=2102
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 8192 bytes)
Console: colour dummy device 80x25
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 515008k/523200k available (2175k kernel code, 7640k reserved,
589k data, 164k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor
mode... Ok.
Calibrating delay using timer specific routine.. 4466.72 BogoMIPS
(lpj=8933455)
Security Framework v1.0.0 initialized
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0383fbff c1c3fbff 00000000 00000000
00000000 00000000 00000000
CPU: After vendor identify, caps: 0383fbff c1c3fbff 00000000 00000000
00000000 00000000 00000000
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
CPU: After all inits, caps: 0383fbff c1c3fbff 00000000 00000420
00000000 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Compat vDSO mapped to ffffe000.
CPU: AMD Athlon(tm) XP stepping 01
Checking 'hlt' instruction... OK.
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xfaf50, last bus=1
PCI: Using configuration type 1
Setting up standard PCI resources
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
Boot video device is 0000:01:00.0
PCI: Using IRQ router VIA [1106/3227] at 0000:00:11.0
PCI: Bridge: 0000:00:01.0
IO window: disabled.
MEM window: d8000000-dfffffff
PREFETCH window: e0000000-e7ffffff
PCI: Setting latency timer of device 0000:00:01.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 16384 bind 8192)
TCP reno registered
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
vesafb: framebuffer at 0xe0000000, mapped to 0xe0800000, using 937k,
total 65536k
vesafb: mode is 800x600x8, linelength=800, pages=7
vesafb: protected mode interface info at c000:b540
vesafb: pmi: set display start = c00cb585, set palette = c00cb60a
vesafb: pmi: ports = 3b4 3b5 3ba 3c0 3c1 3c4 3c5 3c6 3c7 3c8 3c9 3cc
3ce 3cf 3d0 3d1 3d2 3d3 3d4 3d5 3da
vesafb: scrolling: redraw
vesafb: Pseudocolor: size=8:8:8:8, shift=0:0:0:0
Console: switching to colour frame buffer device 100x37
fb0: VESA VGA frame buffer device
Real Time Clock Driver v1.12ac
platform pc8736x_gpio.0: NatSemi pc8736x GPIO Driver Initializing
platform pc8736x_gpio.0: no device found
nsc_gpio initializing
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing
enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
loop: loaded (max 8 devices)
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
HPT302: IDE controller at PCI slot 0000:00:09.0
PCI: setting IRQ 11 as level-triggered
PCI: Found IRQ 11 for device 0000:00:09.0
PCI: Sharing IRQ 11 with 0000:00:10.2
PCI: Sharing IRQ 11 with 0000:00:10.3
HPT302: chipset revision 1
HPT302: 100% native mode on irq 11
HPT37X: using 33MHz PCI clock
ide2: BM-DMA at 0xb000-0xb007, BIOS settings: hde:DMA, hdf:DMA
HPT37X: using 33MHz PCI clock
ide3: BM-DMA at 0xb008-0xb00f, BIOS settings: hdg:DMA, hdh:pio
Probing IDE interface ide2...
hde: Maxtor 6Y120L0, ATA DISK drive
hdf: WDC WD600BB-00CAA0, ATA DISK drive
ide2 at 0xa000-0xa007,0xa402 on irq 11
Probing IDE interface ide3...
hdg: WDC WD1600JB-00FUA0, ATA DISK drive
ide3 at 0xa800-0xa807,0xac02 on irq 11
VP_IDE: IDE controller at PCI slot 0000:00:0f.1
PCI: VIA IRQ fixup for 0000:00:0f.1, from 255 to 0
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt8237 (rev 00) IDE UDMA133 controller on pci0000:00:0f.1
ide0: BM-DMA at 0xd400-0xd407, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xd408-0xd40f, BIOS settings: hdc:DMA, hdd:pio
Probing IDE interface ide0...
hda: JLMS XJ-HD165H, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: PIONEER DVD-RW DVR-107D, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hde: max request size: 128KiB
hde: 240121728 sectors (122942 MB) w/2048KiB Cache, CHS=65535/16/63,
UDMA(100)
hde: cache flushes supported
hde: hde1 < hde5 hde6 > hde2
hdf: max request size: 128KiB
hdf: 117231408 sectors (60022 MB) w/2048KiB Cache, CHS=65535/16/63,
UDMA(100)
hdf: cache flushes not supported
hdf: hdf1
hdg: max request size: 512KiB
hdg: 312581808 sectors (160041 MB) w/8192KiB Cache, CHS=19457/255/63,
UDMA(100)
hdg: cache flushes supported
hdg: hdg1
hda: ATAPI 48X DVD-ROM drive, 512kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
hdc: ATAPI 40X DVD-ROM DVD-R CD-R/RW drive, 2000kB Cache, UDMA(33)
ide-floppy driver 0.99.newide
usbmon: debugfs is not available
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI Shortcut mode
Time: tsc clocksource has been installed.
ReiserFS: hde2: found reiserfs format "3.6" with standard journal
input: AT Translated Set 2 keyboard as /class/input/input0
ReiserFS: hde2: using ordered data mode
ReiserFS: hde2: journal params: device hde2, size 8192, journal first
block 18, max trans len 1024, max batch 900, max commit age 30, max
trans age 30
ReiserFS: hde2: checking transaction log (hde2)
ReiserFS: hde2: Using r5 hash to sort names
VFS: Mounted root (reiserfs filesystem) readonly.
Freeing unused kernel memory: 164k freed
Adding 2097136k swap on /dev/hde6. Priority:-1 extents:1
across:2097136k
Intel(R) PRO/1000 Network Driver - version 7.1.9-k4-NAPI
Copyright (c) 1999-2006 Intel Corporation.
PCI: setting IRQ 5 as level-triggered
PCI: Found IRQ 5 for device 0000:00:0a.0
PCI: Sharing IRQ 5 with 0000:00:10.4
PCI: Sharing IRQ 5 with 0000:00:11.5
Linux Tulip driver version 1.1.13 (May 11, 2002)
USB Universal Host Controller Interface driver v3.0
input: PC Speaker as /class/input/input1
Linux agpgart interface v0.101 (c) Dave Jones
e1000: 0000:00:0a.0: e1000_probe: (PCI:33MHz:32-bit) 00:0e:0c:ba:e3:e1
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
PCI: setting IRQ 10 as level-triggered
PCI: Found IRQ 10 for device 0000:00:0b.0
tulip0: EEPROM default media type Autosense.
tulip0: Index #0 - Media MII (#11) described by a 21140 MII PHY (1)
block.
tulip0: MII transceiver #1 config 3000 status 7829 advertising 01e1.
eth1: Digital DS21140 Tulip rev 34 at e0b62000, 00:C0:F0:31:44:B3, IRQ
10.
PCI: Found IRQ 5 for device 0000:00:10.4
PCI: Sharing IRQ 5 with 0000:00:0a.0
PCI: Sharing IRQ 5 with 0000:00:11.5
ehci_hcd 0000:00:10.4: EHCI Host Controller
ehci_hcd 0000:00:10.4: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:10.4: irq 5, io mem 0xe8081000
ehci_hcd 0000:00:10.4: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 8 ports detected
PCI: setting IRQ 3 as level-triggered
PCI: Found IRQ 3 for device 0000:00:10.0
PCI: Sharing IRQ 3 with 0000:00:10.1
uhci_hcd 0000:00:10.0: UHCI Host Controller
uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:10.0: irq 3, io base 0x0000d800
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
PCI: Found IRQ 3 for device 0000:00:10.1
PCI: Sharing IRQ 3 with 0000:00:10.0
uhci_hcd 0000:00:10.1: UHCI Host Controller
uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:10.1: irq 3, io base 0x0000dc00
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
PCI: Found IRQ 11 for device 0000:00:10.2
PCI: Sharing IRQ 11 with 0000:00:09.0
PCI: Sharing IRQ 11 with 0000:00:10.3
uhci_hcd 0000:00:10.2: UHCI Host Controller
uhci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:10.2: irq 11, io base 0x0000e000
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
PCI: Found IRQ 11 for device 0000:00:10.3
PCI: Sharing IRQ 11 with 0000:00:09.0
PCI: Sharing IRQ 11 with 0000:00:10.2
uhci_hcd 0000:00:10.3: UHCI Host Controller
uhci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 5
uhci_hcd 0000:00:10.3: irq 11, io base 0x0000e400
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
agpgart: Detected VIA KT400/KT400A/KT600 chipset
agpgart: AGP aperture is 128M @ 0xd0000000
PCI: Found IRQ 5 for device 0000:00:11.5
PCI: Sharing IRQ 5 with 0000:00:0a.0
PCI: Sharing IRQ 5 with 0000:00:10.4
PCI: Setting latency timer of device 0000:00:11.5 to 64
usb 2-2: new low speed USB device using uhci_hcd and address 2
usb 2-2: configuration #1 chosen from 1 choice
input: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM) as
/class/input/input2
input: USB HID v1.10 Mouse [Microsoft Microsoft 5-Button Mouse with
IntelliEye(TM)] on usb-0000:00:10.0-2
parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE,EPP]
parport0: irq 7 detected
parport0: Printer, Hewlett-Packard HP LaserJet 1100
lp0: using parport0 (polling).
lp0: console ready
Capability LSM initialized
ReiserFS: hde5: found reiserfs format "3.6" with standard journal
ReiserFS: hde5: using ordered data mode
ReiserFS: hde5: journal params: device hde5, size 8192, journal first
block 18, max trans len 1024, max batch 900, max commit age 30, max
trans age 30
ReiserFS: hde5: checking transaction log (hde5)
ReiserFS: hde5: Using r5 hash to sort names
ReiserFS: hdf1: found reiserfs format "3.6" with standard journal
ReiserFS: hdf1: using ordered data mode
ReiserFS: hdf1: journal params: device hdf1, size 8192, journal first
block 18, max trans len 1024, max batch 900, max commit age 30, max
trans age 30
ReiserFS: hdf1: checking transaction log (hdf1)
ReiserFS: hdf1: Using r5 hash to sort names
ReiserFS: hdg1: found reiserfs format "3.6" with standard journal
ReiserFS: hdg1: using ordered data mode
ReiserFS: hdg1: journal params: device hdg1, size 8192, journal first
block 18, max trans len 1024, max batch 900, max commit age 30, max
trans age 30
ReiserFS: hdg1: checking transaction log (hdg1)
ReiserFS: hdg1: Using r5 hash to sort names
e1000: eth0: e1000_watchdog: NIC Link is Up 10 Mbps Half Duplex
ip_tables: (C) 2000-2006 Netfilter Core Team
Netfilter messages via NETLINK v0.30.
ip_conntrack version 2.4 (4087 buckets, 32696 max) - 204 bytes per
conntrack
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
eth1: Setting half-duplex based on MII#1 link partner capability of
0021.
eth1: no IPv6 routers present
eth0: no IPv6 routers present
--
Dan Amborn
dam...@newsguy.com
>On Tue, 21 Nov 2006 13:52:30 -0600, Dan Amborn wrote:
>
>> I am running Slackware 11.0. I installed the latest kernel 2.6.18.2
>> from 2.4.33.3 and now my eth0 and eth1 change randomly each time I
>> reboot. Never did this running the 2.4 kernel. Is there a work
>> around for this. This is my first time running the 2.6 kernel.
>
>See /etc/udev/rules.d/network-devices.rules
Thanks, I will give it a read while my kernel compiles.
--
Dan Amborn
dam...@newsguy.com
>On Tue, 21 Nov 2006 22:43:28 +0000 (UTC), Jakub Jankowski
><sha...@spam.atn.pl> wrote:
>
>>On Tue, 21 Nov 2006 13:52:30 -0600, Dan Amborn wrote:
>>
>>> I am running Slackware 11.0. I installed the latest kernel 2.6.18.2
>>> from 2.4.33.3 and now my eth0 and eth1 change randomly each time I
>>> reboot. Never did this running the 2.4 kernel. Is there a work
>>> around for this. This is my first time running the 2.6 kernel.
>>
>>See /etc/udev/rules.d/network-devices.rules
>
>Thanks, I will give it a read while my kernel compiles.
That wasn't much of a read lol, but it did the trick! I found that
even if the settings were reversed early in the boot that it would be
cleared up once I got to the dhcp server address request. Rebooted
about ten times in different ways and all came out fine. Thanks
everyone.
--
Dan Amborn
dam...@newsguy.com
It is addressed in this file:
http://slackware.osuosl.org/slackware-11.0/CHANGES_AND_HINTS.TXT
(which is included on the cd 1 ISO).
RW (robw810)
--