Graham, You can edit the "/etc/udev/rules.d/70-persistent-net.rules" file to reorder the interface names.
Lonnie On May 4, 2011, at 3:30 PM, Graham S. Jarvis wrote: > Hello all, > > I'm "playing with a Traverse Technologies Viking ADSL2+ card and here are my > experiences so far. > > Firstly, although the 8139cp module is listed in rc.modules > > astlinux # cat rc.modules > # These modules get modprobe'd when the system starts up. > #rtc > #Comment out the modules you don't need, and change the order to > #move eth0 to eth1, etc. > #Ethernet support > #10/100 first, then Gigabit > 3c59x > typhoon > tulip > eepro100 > natsemi > forcedeth > 8139cp > 8139too > via-rhine > pcnet32 > acenic > e1000 > ns83820 > r8169 > tg3 > sk98lin > > it doesn't exist on the system, > > astlinux # modprobe 8139cp > FATAL: Module 8139cp not found. > > astlinux # find / -name "8139*" > /sys/bus/pci/drivers/8139too > /sys/module/mii/holders/8139too > /sys/module/8139too > /oldroot/mnt/asturo/lib/modules/2.6.27.49-astlinux/kernel/drivers/net/8139too.ko > /lib/modules/2.6.27.49-astlinux/kernel/drivers/net/8139too.ko > > > The Ethernet controller on the Viking card is however being loaded with the > 8139too driver. > > > astlinux # lspci -vvvvv > [SNIP] > 02:04.0 Ethernet controller: Realtek Semiconductor Co., Ltd. > RTL-8139/8139C/8139C+ (rev 20) > Subsystem: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- > Stepping- > SERR+ FastB2B- DisINTx- > Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- > <TAbort- > <MAbort- >SERR- <PERR- INTx- > Latency: 66 (8000ns min, 16000ns max), Cache Line Size: 32 bytes > Interrupt: pin A routed to IRQ 16 > Region 0: I/O ports at 1000 [size=256] > Region 1: Memory at 40200000 (32-bit, non-prefetchable) [size=256] > Kernel driver in use: 8139too > Kernel modules: 8139too > > 02:08.0 Ethernet controller: Intel Corporation 82801BA/BAM/CA/CAM Ethernet > Controller (rev 01) > Subsystem: Compaq Computer Corporation EtherExpress PRO/100 VM > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- > Stepping- > SERR+ FastB2B- DisINTx- > Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- > <TAbort- > <MAbort- >SERR- <PERR- INTx- > Latency: 66 (2000ns min, 14000ns max), Cache Line Size: 32 bytes > Interrupt: pin A routed to IRQ 20 > Region 0: Memory at 40000000 (32-bit, non-prefetchable) [size=4K] > Region 1: I/O ports at 1800 [size=64] > Capabilities: [dc] Power Management version 2 > Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA > PME(D0+,D1+,D2+,D3hot+,D3cold+) > Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=2 PME- > Kernel driver in use: eepro100 > Kernel modules: eepro100, e100 > [SNIP] > > > but dmesg says "Use the "8139cp" driver for improved performance and > stability." > > astlinux # dmesg|grep 8139 > 8139too Fast Ethernet driver 0.9.28 > 8139too 0000:02:04.0: This (id 10ec:8139 rev 20) is an enhanced 8139C+ chip > 8139too 0000:02:04.0: Use the "8139cp" driver for improved performance and > stability. > 8139too 0000:02:04.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 > 8139too 0000:02:04.0: unknown chip version, assuming RTL-8139 > 8139too 0000:02:04.0: TxConfig = 0x74800000 > eth1: RealTek RTL8139 at 0xd082a000, 00:0a:fa:20:04:84, IRQ 16 > eth1: Identified 8139 chip type 'RTL-8139' > > > So, 2 questions: > > A) Where do I get a good 8139cp driver and will it be added to the next > Astlinux > release? > > B) How do I force the RTL8139cp to be eth0 and the "real" Ethernet card to be > eth1? > At the moment eth0 is the "real" Ethernet card (eepro100) but I don't > understand > why it is loaded as eth0 when lspci puts it after the RTL8139cp (see lspci o/p > above). > > astlinux # dmesg > [snip] > VFS: Mounted root (ext2 filesystem). > Freeing unused kernel memory: 212k freed > Linux Tulip driver version 1.1.15 (Feb 27, 2007) > eepro100.c:v1.09j-t 9/29/99 Donald Becker > eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin > <[email protected]> and others > eepro100 0000:02:08.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20 > eth0: OEM i82557/i82558 10/100 Ethernet, 00:02:a5:2b:47:6c, IRQ 20. > Board assembly 010700-001, Physical connectors present: RJ45 > Primary interface chip i82555 PHY #1. > General self-test: passed. > Serial sub-system self-test: passed. > Internal registers self-test: passed. > ROM checksum self-test: passed (0x04f4518b). > natsemi dp8381x driver, version 2.1, Sept 11, 2006 > originally by Donald Becker <[email protected]> > 2.4.x kernel port by Jeff Garzik, Tjeerd Mulder > 8139too Fast Ethernet driver 0.9.28 > 8139too 0000:02:04.0: This (id 10ec:8139 rev 20) is an enhanced 8139C+ chip > 8139too 0000:02:04.0: Use the "8139cp" driver for improved performance and > stability. > 8139too 0000:02:04.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 > 8139too 0000:02:04.0: unknown chip version, assuming RTL-8139 > 8139too 0000:02:04.0: TxConfig = 0x74800000 > eth1: RealTek RTL8139 at 0xd082a000, 00:0a:fa:20:04:84, IRQ 16 > eth1: Identified 8139 chip type 'RTL-8139' > via-rhine.c:v1.10-LK1.4.3 2007-03-06 Written by Donald Becker > pcnet32.c:v1.35 21.Apr.2008 [email protected] > Intel(R) PRO/1000 Network Driver - version 7.3.21-k3-NAPI > Copyright (c) 1999-2006 Intel Corporation. > ns83820.c: National Semiconductor DP83820 10/100/1000 driver. > Real Time Clock Driver v1.12ac > [SNIP] > > If I change the network config in the GUI so that the external i/f is eth0 > with > an address of 192.168.1.2 (the Vikings Ethernet i/f) and the internal network > as > eth1 with the internal network address, when I reboot eth0 is _still_ the real > Ethernet card and I lock myself out because it now has the 192.168.1.2 address > instead of something in my network address range. > > > Sorry about the embedded "debug" output - I hope it doesn't make this mail too > difficult to read. > > All the Best, > > -Graham- > > > > ------------------------------------------------------------------------------ > WhatsUp Gold - Download Free Network Management Software > The most intuitive, comprehensive, and cost-effective network > management toolset available today. Delivers lowest initial > acquisition cost and overall TCO of any competing solution. > http://p.sf.net/sfu/whatsupgold-sd > _______________________________________________ > Astlinux-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to > [email protected]. > > ------------------------------------------------------------------------------ WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd _______________________________________________ Astlinux-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [email protected].
