2003-03-21 15:07:43

by Jos Hulzink

[permalink] [raw]
Subject: 2.5.65: 3C905 driver doesn't work.

Hi,

2.5.65 doesn't connect to my network via my network card:

00:0b.0 Ethernet controller: 3Com Corporation 3c905 100BaseTX [Boomerang]

My switch does show a link, but the dhcpcd negotiation fails, and no activity
is shown.

All kernel logs look normal, no errors, card is detected correctly.

My configuration is attached.

Jos


Attachments:
(No filename) (332.00 B)
config.gz (5.34 kB)
Download all attachments

2003-03-21 15:26:17

by Dave Jones

[permalink] [raw]
Subject: Re: 2.5.65: 3C905 driver doesn't work.

On Fri, Mar 21, 2003 at 04:18:36PM +0100, Jos Hulzink wrote:

> 2.5.65 doesn't connect to my network via my network card:
>
> 00:0b.0 Ethernet controller: 3Com Corporation 3c905 100BaseTX [Boomerang]
>
> My switch does show a link, but the dhcpcd negotiation fails, and no activity
> is shown.
>
> All kernel logs look normal, no errors, card is detected correctly.

try booting with..
"acpi=off"
"noapic"
"acpi=off noapic"

For me, the third one gets it working again on two boxes.
Without that, packets are sent, but nothing is ever recieved.

Dave

2003-03-21 17:20:24

by Jos Hulzink

[permalink] [raw]
Subject: Re: 2.5.65: 3C905 driver doesn't work.

On Fri, 21 Mar 2003, Dave Jones wrote:

> On Fri, Mar 21, 2003 at 04:18:36PM +0100, Jos Hulzink wrote:
>
> > 2.5.65 doesn't connect to my network via my network card:
> >
> > 00:0b.0 Ethernet controller: 3Com Corporation 3c905 100BaseTX [Boomerang]
> >
> > My switch does show a link, but the dhcpcd negotiation fails, and no activity
> > is shown.
> >
> > All kernel logs look normal, no errors, card is detected correctly.
>
> try booting with..
> "acpi=off"
> "noapic"
> "acpi=off noapic"
>
> For me, the third one gets it working again on two boxes.
> Without that, packets are sent, but nothing is ever recieved.
>

For me, the third option results in a kernel panic very early during boot
:( I'm trying to get more info out of it.

Other options untested yet.

Jos

2003-03-21 17:42:59

by Dave Jones

[permalink] [raw]
Subject: Re: 2.5.65: 3C905 driver doesn't work.

On Fri, Mar 21, 2003 at 06:31:24PM +0100, Jos Hulzink wrote:
> > "acpi=off noapic"
> > For me, the third one gets it working again on two boxes.
> > Without that, packets are sent, but nothing is ever recieved.
> For me, the third option results in a kernel panic very early during boot
> :( I'm trying to get more info out of it.

Interesting, can you post that panic ?

Dave

2003-03-23 11:42:32

by Jos Hulzink

[permalink] [raw]
Subject: Re: 2.5.65: 3C905 driver doesn't work.

On Friday 21 March 2003 16:37, Dave Jones wrote:
> On Fri, Mar 21, 2003 at 04:18:36PM +0100, Jos Hulzink wrote:
> > 2.5.65 doesn't connect to my network via my network card:
> >
> > 00:0b.0 Ethernet controller: 3Com Corporation 3c905 100BaseTX
> > [Boomerang]
> >
> > My switch does show a link, but the dhcpcd negotiation fails, and no
> > activity is shown.
> >
> > All kernel logs look normal, no errors, card is detected correctly.
>
> try booting with..
> "acpi=off"
> "noapic"
> "acpi=off noapic"
>
> For me, the third one gets it working again on two boxes.
> Without that, packets are sent, but nothing is ever recieved.
>

Okay, this indeed works for me too.

Interesting is this:

MPS 1.4 disabled in BIOS (no irq rerouting table in memory), acpi enabled in
kernel, apic on: 3Com module tries to claim IRQ 0, which is of course
incorrect.

the IRQ rerouting causes trouble for my SCSI card too, I guess we're still a
long way from usable ACPI and APIC :( If I can be of any help to test things,
please let me know.

Jos

2003-03-23 11:43:18

by Jos Hulzink

[permalink] [raw]
Subject: Re: 2.5.65: 3C905 driver doesn't work.

On Friday 21 March 2003 18:53, Dave Jones wrote:
> On Fri, Mar 21, 2003 at 06:31:24PM +0100, Jos Hulzink wrote:
> > > "acpi=off noapic"
> > > For me, the third one gets it working again on two boxes.
> > > Without that, packets are sent, but nothing is ever recieved.
> >
> > For me, the third option results in a kernel panic very early during
> > boot
> >
> > :( I'm trying to get more info out of it.
>
> Interesting, can you post that panic ?

Located, caused by a magically jumped back Processor setting (P4 code doesn't
work on P2)

Jos