FC5
Net Llama!
netllama
Sat Jun 10 13:09:33 PDT 2006
On 06/10/2006 12:30 PM, Rick Sivernell wrote:
> Lonnie
>
>> > I am using the Nvida nforce3 350 gc chipset, it is built into the mobo, The lan
>> > ctrl works with the MarvelGigabit LanPHY. from book on page 1-3.
>>
>> What book is this?
> Asus K8N-E Delux Users Guide
>
>
> [root at RSivernell ~]# lspci
> 00:00.0 Host bridge: nVidia Corporation nForce3 250Gb Host Bridge (rev a1)
> 00:01.0 ISA bridge: nVidia Corporation nForce3 250Gb LPC Bridge (rev a2)
> 00:01.1 SMBus: nVidia Corporation nForce 250Gb PCI System Management (rev a1)
> 00:02.0 USB Controller: nVidia Corporation CK8S USB Controller (rev a1)
> 00:02.1 USB Controller: nVidia Corporation CK8S USB Controller (rev a1)
> 00:02.2 USB Controller: nVidia Corporation nForce3 EHCI USB 2.0 Controller (rev
> a2) 00:05.0 Bridge: nVidia Corporation CK8S Ethernet Controller (rev a2)
> 00:06.0 Multimedia audio controller: nVidia Corporation nForce3 250Gb AC'97 Audio
> Controller (rev a1) 00:08.0 IDE interface: nVidia Corporation CK8S Parallel ATA
> Controller (v2.5) (rev a2) 00:0b.0 PCI bridge: nVidia Corporation nForce3 250Gb
> AGP Host to PCI Bridge (rev a2) 00:0e.0 PCI bridge: nVidia Corporation nForce3
> 250Gb PCI-to-PCI Bridge (rev a2) 00:18.0 Host bridge: Advanced Micro Devices
> [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host
> bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2
> Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
> 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
> Miscellaneous Control 01:00.0 VGA compatible controller: nVidia Corporation NV34
> [GeForce FX 5500] (rev a1) 02:06.0 Ethernet controller: Realtek Semiconductor
> Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) 02:0b.0 FireWire (IEEE 1394): VIA
> Technologies, Inc. IEEE 1394 Host Controller (rev 80) 02:0c.0 Mass storage
> controller: Silicon Image, Inc. SiI 3114 [SATALink/SATARaid] Serial ATA
> Controller (rev 02) [root at RSivernell ~]#
You realize that your mail client is removing all the EOL characters,
right? The output above is nearly unreadable, however again, I don't
see Marvell mentioned anywhere.
>
> /etc/sysconfig/hwrconf
> class: NETWORK
> bus: PCI
> detached: 0
> device: eth1
> driver: forcedeth
> desc: "nVidia Corporation CK8S Ethernet Controller"
> network.hwaddr: 00:11:2f:7f:17:ec
> vendorId: 10de
> deviceId: 00df
> subVendorId: 1043
> subDeviceId: 80a7
> pciType: 1
> pcidom: 0
> pcibus: 0
> pcidev: 5
> pcifn: 0
> -
> class: NETWORK
> bus: PCI
> detached: 0
> device: eth0
> driver: 8139too
> desc: "Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+"
> network.hwaddr: 00:50:fc:8f:6f:5a
> vendorId: 10ec
> deviceId: 8139
> subVendorId: 10ec
> subDeviceId: 8139
> pciType: 1
> pcidom: 0
> pcibus: 2
> pcidev: 6
> pcifn: 0
I don't see anything in the output above to suggest that you've got a
Marvell NIC.
> -
>
> set /etc/modprobe.cnf:
> [root at RSivernell ~]# more /etc/modprobe.conf
> alias scsi_hostadapter sata_sil
> alias eth0 8139too
> alias eth1 forcedeth
> alias scsi_hostadapter1 sata_nv
> alias snd-card-0 snd-intel8x0
> options snd-card-0 index=0
> options snd-intel8x0 index=0
> remove snd-intel8x0 { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; }; /sbin/
> modprobe -r --ignore-remove snd-intel8x0
> alias snd-card-1 snd-mpu401
> options snd-card-1 index=1
> options snd-mpu401 index=1
> remove snd-mpu401 { /usr/sbin/alsactl store 1 >/dev/null 2>&1 || : ; }; /sbin/mo
> dprobe -r --ignore-remove snd-mpu401
> [root at RSivernell ~]#
>
> [root at RSivernell ~]# locate *forcedeth*
> /lib/modules/2.6.15-1.2054_FC5/kernel/drivers/net/forcedeth.ko
> /lib/modules/2.6.16-1.2122_FC5/kernel/drivers/net/forcedeth.ko
> /usr/src/kernels/2.6.16-1.2122_FC5-x86_64/include/config/forcedeth
> /usr/src/kernels/2.6.16-1.2122_FC5-x86_64/include/config/forcedeth/module.h
> [root at RSivernell ~]#
>
> [root at RSivernell ~]# /etc/init.d/network restart
> Shutting down interface eth0: [ OK ]
> Shutting down loopback interface: [ OK ]
> Bringing up loopback interface: [ OK ]
> Bringing up interface eth0: [ OK ]
> Bringing up interface eth1: /etc/init.d/functions: line 433: 27834 Segmentation
> fault $* [FAILED]
something is causing a segfault. you should report that as a bug
assuming that your system is up to date.
> [root at RSivernell ~]#
>
> What driver name are you using for this Nvidia lan?
forcedeth, the same as your system is using. Is there a reason why
you're restarting all networking on the box just to bring up a single
network device? Why not just do "ifup eth1" ?
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
L. Friedman netllama at linux-sxs.org
LlamaLand http://netllama.linux-sxs.org
13:05:01 up 14 days, 17:38, 1 user, load average: 0.10, 0.11, 0.03
More information about the Linux-users
mailing list