Re: 2.1.120 report [misc. stuff/longish]

Mike (mike@oakley.keble.ox.ac.uk)
Thu, 10 Sep 1998 20:42:39 +0100 (GMT)


On Tue, 8 Sep 1998, Felix von Leitner wrote:

> Thus spake Nicholas J. Leon (nicholas@binary9.net):
> > c59x.c:v0.99F 8/7/98 Donald Becker
> > http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
> > The PCI BIOS has not enabled this device! Updating PCI command
> > 0000->0005.
> > eth1: 3Com 3c905 Boomerang 100baseTx at 0xef00, 00:60:97:7b:34:41, IRQ 5
> > 8K word-wide RAM 3:5 Rx:Tx split, MII interface.
> > MII transceiver found at address 24, status 7849.
> > Enabling bus-master transmits and whole-frame receives.
>
> I think that PCI BIOS statement is harmless.

I'm not so sure it is. I don't get it with v0.99E of the driver, but I do
with 0.99F. Does anyone actually know that the new PCI stuff in 0.99F is
not what is causing the problems?

> I don't get it, but my card is not working, too.
> 2.1.119 works fine, 2.1.120 does nothing at all on the ethernet. I have
> another machine connected via a crossed Cat5 cable to a lowly 10BaseT
> NE2k card with a tcpdump running, and 2.1.120 does nothing at all on the
> Ethernet. ping and tcpdump of course show me the packets on the 2.1.120
> machine, but the other machine does not do anything.
>
Verion 0.99F of the driver (the one in 2.1.120) seems to be totally
screwed. Go back to the 3c59x.c from 2.1.119 (0.99E) and forget about it
until some nice clever person fixes it :)

> > 4. unmounting / at shutdown/reboot doesn't work.
>
> > I've heard mention of this on the list, but haven't heard any solutions
> > for it yet. So this is just a "me too!".
>
> Works fine for me.
>
Works for me too :)

--
Mike <rickettm@ox.compsoc.net>

Adding sound to movies would be like putting lipstick on the Venus de Milo. -- actress Mary Pickford, 1925

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/faq.html