[gentoo-amd64] Re: Nvidia forcedeth driver.

[Gordon Gallup]

Dear Bernhard,
   As you recommend, I send the output of dmesg and lspci when the
livecd installation pgm is running and when the resulting disk system
is running.  Actually, the lspci output is identical in the two cases,
and the two relevent lines are
-------------------------------------------------------------------------------------------
00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a1)
04:06.0 Ethernet controller: D-Link System Inc Gigabit Ethernet Adapter (rev 11)
--------------------------------------------------------------------------------------------
The dmesg outputs differ, however.
---------------------------livecd---------------------------------------------------------
forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.48.
PCI: Setting latency timer of device 0000:00:14.0 to 64
eth0: forcedeth.c: subsystem: 01462:7207 bound to 0000:00:14.0
eth0: no link during initialization.
eth0: no link during initialization.
skge 1.3 addr 0xfebfc000 irq 5 chip Yukon rev 1
skge eth1: addr 00:0f:3d:f2:b8:89
skge eth1: enabling interface
skge eth1: disabling interface
skge eth1: enabling interface
skge eth1: Link is up at 100 Mbps, full duplex, flow control tx and rx
---------------------------------------------------------------------------------------------------

---------------------------Disk
system------------------------------------------------------
forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.49.
PCI: Setting latency timer of device 0000:00:14.0 to 64
eth0: forcedeth.c: subsystem: 01462:7207 bound to 0000:00:14.0
----------------------------------------------------------------------------------------------------

BTW, I know this is OT, but what is the difference *.o and *.ko modules?
Thanks, Gordon


On 5/26/06, Bernhard Auzinger <e0026053@×××××××××××××××××.at> wrote:
> I think something else has gone wrong with your forcedeth driver. Gordon,
> maybe you could post the detailed feedback your system gives to you when try
> using the forcedeth driver.
>
> Sometimes it's a little bit confusing, which of both LAN adapters is eth0
> and
> which eth1. I guess you have to disable the forcedeth driver from your
> kernel
> to use your D-LINK adapter as eth0.
>
> rgds
>
> Bernhard
> --
> gentoo-amd64@g.o mailing list
>
>

-- 
gentoo-amd64@g.o mailing list