Re: 2.1.30 and 3c900 module: Transmitter access conflict
[EMAIL PROTECTED] (Ferenc Kiraly) writes: The subject says it all: I am installing a Debian 1.3.1 system on a brand new PC with a 3c900 Combo board. I use that card with the vortex driver and it works fine ... I think the 3c59x module is the wrong one. Thanks for you answer. I don't know about the vortex driver. Anyway, the 3c59x is okay for that card. Its author, Donald Becker, told me that indeed the autoprobe for AUI does not work, because of apparently insufficient demand for that feature. However, I have as yet no explanations for some (apparently innocuous) error messages appearing at and shortly after module iniatialisation. The card seems to work okay. I brought the discussions on the [EMAIL PROTECTED] list. Again, thanks to all that have helped. -=- MIME -=- --Boundary_(ID_Fy0Nmukjup0C7yYi9Ndneg) Content-type: text/plain This report relates to a message you sent with the following header fields: Message-id: [EMAIL PROTECTED] Date: Mon, 10 Nov 1997 10:29:06 +0100 From: Francesco Potorti` [EMAIL PROTECTED] To: [EMAIL PROTECTED] (Ferenc Kiraly) Subject: Re: 2.1.30 and 3c900 module: Transmitter access conflict Your message cannot be delivered to the following recipients: Recipient address: [EMAIL PROTECTED] Reason: Not found in directory --Boundary_(ID_Fy0Nmukjup0C7yYi9Ndneg) Content-type: message/DELIVERY-STATUS Original-envelope-id: [EMAIL PROTECTED] Reporting-MTA: dns; mailsrv.cnuce.cnr.it Action: failed Status: 5.1.1 (Not found in directory) Original-recipient: rfc822;[EMAIL PROTECTED] Final-recipient: rfc822;[EMAIL PROTECTED] --Boundary_(ID_Fy0Nmukjup0C7yYi9Ndneg) Content-type: MESSAGE/RFC822 Return-path: [EMAIL PROTECTED] Received: from DIRECTORY-DAEMON by mailsrv.cnuce.cnr.it (PMDF V5.1-9 #16550) id [EMAIL PROTECTED]; Mon, 10 Nov 1997 10:27:13 MET Received: from fly.cnuce.cnr.it ([131.114.192.86]) by mailsrv.cnuce.cnr.it (PMDF V5.1-9 #16550) with SMTP id [EMAIL PROTECTED] for [EMAIL PROTECTED]; Mon, 10 Nov 1997 10:27:11 MET Received: by fly.cnuce.cnr.it (Smail3.1.26.7 #3) id m0xUq9b-0001LgC; Mon, 10 Nov 1997 10:29 +0100 (MET) Date: Mon, 10 Nov 1997 10:29:06 +0100 From: Francesco Potorti` [EMAIL PROTECTED] Subject: Re: 2.1.30 and 3c900 module: Transmitter access conflict In-reply-to: [EMAIL PROTECTED]'s message of 6 Nov 97 09:00:10 GMT Sender: [EMAIL PROTECTED] (Francesco Potorti`) Sender: [EMAIL PROTECTED] To: [EMAIL PROTECTED] (Ferenc Kiraly) Cc: [EMAIL PROTECTED] Message-id: [EMAIL PROTECTED] MIME-version: 1.0 X-Mailer: Gnus v5.3/Emacs 19.34 Content-type: TEXT/PLAIN Lines: 20 References: [EMAIL PROTECTED] [EMAIL PROTECTED] (Ferenc Kiraly) writes: The subject says it all: I am installing a Debian 1.3.1 system on a brand new PC with a 3c900 Combo board. I use that card with the vortex driver and it works fine ... I think the 3c59x module is the wrong one. Thanks for you answer. I don't know about the vortex driver. Anyway, the 3c59x is okay for that card. Its author, Donald Becker, told me that indeed the autoprobe for AUI does not work, because of apparently insufficient demand for that feature. However, I have as yet no explanations for some (apparently innocuous) error messages appearing at and shortly after module iniatialisation. The card seems to work okay. I brought the discussions on the [EMAIL PROTECTED] list. Again, thanks to all that have helped. --Boundary_(ID_Fy0Nmukjup0C7yYi9Ndneg)-- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: 2.1.30 and 3c900 module: Transmitter access conflict
The subject says it all: I am installing a Debian 1.3.1 system on a brand new PC with a 3c900 Combo board. Since I have a Buslogic Flashpoint SCSI card, I used the disks under the special/ directory, which use 2.1.30. Loading the 3c59x module seems to work, because the module correctly recognises the board. It then prints the following messages: Hi! I use that card with the vortex driver and it works fine ... I think the 3c59x module is the wrong one. feri. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
2.1.30 and 3c900 module: Transmitter access conflict
Hi, The subject says it all: I am installing a Debian 1.3.1 system on a brand new PC with a 3c900 Combo board. Since I have a Buslogic Flashpoint SCSI card, I used the disks under the special/ directory, which use 2.1.30. Loading the 3c59x module seems to work, because the module correctly recognises the board. It then prints the following messages: 3c59x.c:v0.30-all 12/23/96 [EMAIL PROTECTED] 3Com EtherLink III: Overriding PCI latency timer (CFLT) setting of 32, new value is 255. loading device 'eth0'... eth0: 3Com 3c900 Boomerang 10Mbps/Combo at 0xd400, 00:60:08:12:4d:ef, IRQ 12 Internal config register is 10302d8, transceivers 0xe138. 8K word-wide RAM 3:5 Rx:Tx split, autoselect/10baseT interface. Which is okay (I think), apart from the fact that the used interface is really the AUI. Then I run /etc/init.d/network, obtaining these messages: eth0: initial media type 10baseT. eth0: vortex_open() InternalConfig 010302d8. eth0: vortex_open() irq 12 media status 8800. eth0: Media selection timer tick happened, 10baseT. eth0: Media 10baseT is has no link beat, 80c0. eth0: Media selection failed, now trying 10base2 port. eth0: Media selection timer finished, 10base2. eth0: Media selection timer tick happened, 10base2. eth0: Media 10base2 is has no indication, 4810. eth0: Media selection timer finished, 10base2. I would have expected a word about the AUI interface, but there is not. Anyway, if I now try a ping to a numerical IP address, I get sequences of: eth0: Transmitter access conflict. and, needless to say, no response to the ping is received (so I assume nothing is getting out of the card). Anyone has any idea of what's happening? Donald, are you listening? Thanks to all Francesco -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: 2.1.30 and 3c900 module: Transmitter access conflict
On Wed, 05 Nov 1997 14:09:00 +0700 Francesco Potorti` ([EMAIL PROTECTED]) wrote: The subject says it all: I am installing a Debian 1.3.1 system on a brand new PC with a 3c900 Combo board. Since I have a Buslogic Flashpoint SCSI card, I used the disks under the special/ directory, which use 2.1.30. Loading the 3c59x module seems to work, because the module correctly recognises the board. It then prints the following messages: 3c59x.c:v0.30-all 12/23/96 [EMAIL PROTECTED] 3Com EtherLink III: Overriding PCI latency timer (CFLT) setting of 32, new value is 255. loading device 'eth0'... eth0: 3Com 3c900 Boomerang 10Mbps/Combo at 0xd400, 00:60:08:12:4d:ef, IRQ 12 Internal config register is 10302d8, transceivers 0xe138. 8K word-wide RAM 3:5 Rx:Tx split, autoselect/10baseT interface. Which is okay (I think), apart from the fact that the used interface is really the AUI. Then I run /etc/init.d/network, obtaining these messages: eth0: initial media type 10baseT. Have you tried running the 3Com setup program (under DOS) and set the card not to use Plug-And-Play mode ? And also maybe select the media type manually ? Phil. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: 2.1.30 and 3c900 module: Transmitter access conflict
3c59x.c:v0.30-all 12/23/96 [EMAIL PROTECTED] ^ This is incredibly old. Check the Ethernet-HOWTO for the URL of the site where you can download a version (0.46something) which works fine. Thanks. This is the version that comes with 2.0.30. Maybe the kernel maintainers should be made aware of this. I'll download the latest ASAP. Francesco -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: 2.1.30 and 3c900 module: Transmitter access conflict
On Wednesday 5 November 97, at 14 h 9, the keyboard of Francesco Potorti` [EMAIL PROTECTED] wrote: 3c59x.c:v0.30-all 12/23/96 [EMAIL PROTECTED] ^ This is incredibly old. Check the Ethernet-HOWTO for the URL of the site where you can download a version (0.46something) which works fine. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: 2.1.30 and 3c900 module: Transmitter access conflict
On Wed, 5 Nov 1997, Philippe Troin wrote: On Wed, 05 Nov 1997 14:09:00 +0700 Francesco Potorti` ([EMAIL PROTECTED]) wrote: The subject says it all: I am installing a Debian 1.3.1 system on a brand new PC with a 3c900 Combo board. Since I have a Buslogic Flashpoint SCSI card, I used the disks under the special/ directory, which use 2.1.30. Loading the 3c59x module seems to work, because the module correctly recognises the board. It then prints the following messages: 3c59x.c:v0.30-all 12/23/96 [EMAIL PROTECTED] 3Com EtherLink III: Overriding PCI latency timer (CFLT) setting of 32, new value is 255. loading device 'eth0'... eth0: 3Com 3c900 Boomerang 10Mbps/Combo at 0xd400, 00:60:08:12:4d:ef, IRQ 12 Internal config register is 10302d8, transceivers 0xe138. 8K word-wide RAM 3:5 Rx:Tx split, autoselect/10baseT interface. Which is okay (I think), apart from the fact that the used interface is really the AUI. Then I run /etc/init.d/network, obtaining these messages: eth0: initial media type 10baseT. Have you tried running the 3Com setup program (under DOS) and set the card not to use Plug-And-Play mode ? And also maybe select the media type manually ? I had a similar set-up where I needed to use the AUI interface. I found that the autoselect mechanism got fooled and I had to set the media type manually at boot time (or at module load time). I think it was options=1, but you ought to check the doc's for sure. (I would, but my system is not accessible at the moment.) Hope this helps, Andy Dougherty [EMAIL PROTECTED] Dept. of Physics Lafayette College, Easton PA 18042 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: 2.1.30 and 3c900 module: Transmitter access conflict
On Wed, 5 Nov 1997, Philippe Troin wrote: I had a similar set-up where I needed to use the AUI interface. I found that the autoselect mechanism got fooled and I had to set the media type manually at boot time (or at module load time). I think it was options=1, but you ought to check the doc's for sure. (I would, but my system is not accessible at the moment.) I had tried `insmod 3c59x options=1', which I guessed by looking at the sources (what docs?), but I was fooled into thinking that didn't work because the load message said autoselect/10baseT interface. However, I just tried again and, after running ifconfig, I get eth0: media override to transceiver 1 (10Mbs AUI) and indeed it works. Thanks to all for your help (I'll get the latest version of the driver nonetheless). -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
