On Sat, Jun 02, 2001 at 05:13:30PM +0100, Pete French wrote:
> > But you're right, in fact 3com cards 3c905 and 3c905c are quite
> > different.
As far as I can see the general consensus is that we don't know yet ;)
> It is the general consensu that this affect 3C905 cards only, not any of the
>
> But you're right, in fact 3com cards 3c905 and 3c905c are quite
> different.
It is the general consensu that this affect 3C905 cards only, not any of the
other 3COM cards that use the xl driver ? I have a 3C900B-TPO in a remote
machine that I was going to have a try at upgrading sometime in the
Hi,
Am Sa , dem 02. Jun 2001, um 22:25 + Uhr schrubte K Karthik
zum Thema [Re: Problem with xl driver (cvsup 2001-06-02)]:
> No problems for me. My dmesg line:
> *--*
> xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0x1000-0x107f mem
> 0xf400-0xf47f irq 11 at d
No problems for me. My dmesg line:
*--*
xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0x1000-0x107f mem
0xf400-0xf47f irq 11 at device 13.0 on pci0
*--*
scanpci:
*--*
pci bus 0x0 cardnum 0x0d function 0x: vendor 0x10b7 device 0x9200
3COM Device unknown
*--*
Don't know if "C" (3c90
Hi,
Am Sa , dem 02. Jun 2001, um 11:51 + Uhr schrubte Wilko Bulte
zum Thema [Re: Problem with xl driver (cvsup 2001-06-02)]:
> This is most likely PR kern/27722
>
>
> http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27722
>
> Wilko
Yes, this was exactly the cure.
Everything r
This is most likely PR kern/27722
http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27722
Wilko
> Hi...
>
> my buildworld of this morning shows a little uncomfortable problem with
> the xl driver:
>
> media: ... status: no carrier
>
> The card is a 3c905 - TX (scanpci: device 0x9050) and never ma
