/proc/interrupts shows eth0 (sharing aic7xxx) now. The NIC is fully
functional now.
I was actually trying your 3c59x.c-2.2.19pre2.gz, and not the -2
version. Trying that now.
--Lee
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PRO
I Lee Hetherington wrote:
>
> Andrew Morton wrote:
>
> > Could you please test this 2.2 driver?
> >
> > http://www.uow.edu.au/~andrewm/linux/3c59x.c-2.2.19-pre2-2.gz
>
> Bingo! This driver works fine. Thanks.
And /proc/interrupts?
> (Why do hardware people keep tweaking things for s
Andrew Morton wrote:
> Could you please test this 2.2 driver?
>
> http://www.uow.edu.au/~andrewm/linux/3c59x.c-2.2.19-pre2-2.gz
Bingo! This driver works fine. Thanks.
(Why do hardware people keep tweaking things for seemingly unnecessary reasons?)
--Lee Hetherington
-
To unsubscrib
I Lee Hetherington wrote:
>
> Andrew Morton wrote:
>
> > Please do. The boot-time messages which come out of the driver
> > would be interesting. It would help if you add `debug=7' to
> > the 3c59x modprobe command line also.
>
> OK. I've included dmesg output due to modprobe with debug=7 fo
Yes, it is rev 78, but I have at least 20 of these working on other
machines (Precision 620) for a long time now. The difference in this
machine is the i850 chipset vs. the i810 in the 620.
This seems to be a problem of 3c59x making a successful call of
request_irq(), but nothing shows up in /pr
What is the output of 'lspci -v'? If it says that the chip revision is '78' then
this is one of the new 3C905CX (note the CX) NIC's or ASIC on the motherboard.
I've seen a problem with the 3c59x.c driver and this chip, it can send packets
but not receive any. The 3Com 3c90x-1.0.0i.tgz driver at
Sorry to follow up, but I forgot to note that it is trying to share IRQ
11 for aic7xx and eth0. However, even if I move the Adaptec card to
another slot, where it gets IRQ 10, still no joy for eth0 on IRQ 11.
--Lee Hetherington
-
To unsubscribe from this list: send the line "unsubscribe linux-
Andrew Morton wrote:
> Please do. The boot-time messages which come out of the driver
> would be interesting. It would help if you add `debug=7' to
> the 3c59x modprobe command line also.
OK. I've included dmesg output due to modprobe with debug=7 followed by ifup
(using pump -- problems pers
I Lee Hetherington wrote:
>
> Anybody get this working with 2.2.18 or 2.4.0-prerelease? I can't seem
> to get the on-board 3c905c to work. I've seen it without an interrupt
> assignment in /proc/interrupts. With Red Hat's pump (DHCP), it sends
> packets out but doesn't seem to see the response
Manfred wrote:
> Everything except the NIC works?
Yes.
> What do you mean with "without an interrupt assignment"?
> Is there no line for ethx in /proc/interrupt, or the number of
> interrupts remains 0?
There is no entry for eth0 anywhere in /proc/interrupts. That seems
strange.
> what does
> Anybody get this working with 2.2.18 or 2.4.0-prerelease?
> I can't seem to get the on-board 3c905c to work.
Everything except the NIC works?
> I've seen it without an interrupt assignment in
> /proc/interrupts. With Red Hat's pump (DHCP), it sends
> packets out but doesn't seem to see the re
Anybody get this working with 2.2.18 or 2.4.0-prerelease? I can't seem
to get the on-board 3c905c to work. I've seen it without an interrupt
assignment in /proc/interrupts. With Red Hat's pump (DHCP), it sends
packets out but doesn't seem to see the response.
I can provide more details.
--Lee
12 matches
Mail list logo
