Hi Per,

Per Lundberg wrote:

>    PL> But this is the strange thing: one of the network adapters on
>    PL> this motherboard are supposed to be based on this chip. I
>    PL> cannot get it working with Linux, though.
>
>Update: I now checked with lspci and this is the only ethernet card being 
>listed:
>
>0000:03:00.0 Ethernet controller: Marvell Technology Group Ltd.: Unknown 
>device 4362 (rev 15)
>        Subsystem: Micro-Star International Co., Ltd.: Unknown device 058c
>        Flags: bus master, fast devsel, latency 0, IRQ 12
>        Memory at fe600000 (64-bit, non-prefetchable) [size=16K]
>        I/O ports at be00 [size=256]
>        Capabilities: <available only to root>
>
>I run this network adapter with forcedeth. The other network adapter
>is thus not even listed in the lspci output, which is probably the reason
>why it is not detected by neither forcedeth or sk98lin...
>
>And yes, this is PCIe.
>  
>
I have a Gigabyte K8NS Ultra-930 motherboard with the nForce3 250
chipset and two NICs:

Marvell Yukon 88E8001
<http://www.marvell.com/products/pcconn/yukon/88E8001.jsp>
ICS1883 (forcedeth
<http://www.hailfinger.org/carldani/linux/patches/forcedeth/>)

The ICS1883 is the nforce3 NIC, which takes the forcedeth driver. The
reason I'm writing is that lspci
doesn't see it, but the driver loads and it works as a gigabit NIC. I
have it working fine with the 2.6.12-rc1 and rc2 kernels, no tweaks or
patches required.

On installation, I ran into the problem that the D-I 2.6.8 forcedeth
driver loaded, didn't work, and then blocked the operation of the
sk98lin needed for the Yukon. I had to rename the forcedeth.ko module in
/lib/modules to prevent it from loading and was then able to use the
Yukon to upgrade the kernel and make the nVidia NIC work too. In brief,
it's invisible, but don't let that fool you.

And BTW, I seriously doubt you're really running your Marvell Yukon with
a forcedeth driver.

Cheers,
Dave










-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to