Re: Xircom realport rem56g problems
Hi, I just built fresh -current (NEWCARD) but it didn't work. I'm beginning to suspect that we have different cards, since the dc driver won't recognize mine. The dc driver seems to expect that vendor id is 0x115d and device id 0x0003. On my card the vendor id is 0x0105 and device id is 0x110a. On the back of the card is says realport ethernet 10/100+modem 56 and REM56G-100. Ari S. On Wednesday 04 December 2002 19:35, Sam Leffler wrote: On Tuesday 03 December 2002 18:38, Sam Leffler wrote: Try the dc driver instead of xe. I have the same card and it worked once I added the cardbus glop to read the MAC address from the CIS. I was going to use NEWCARD kernel, is it possible to use another driver with it ? I use NEWCARD and the dc driver. device miibus # MII bus support device dc # Xircom cardbus ethernet device ep # Etherlink III based cards device wi # WaveLAN/Intersil/Symbol 802.11 wireless NICs. My fix to read the MAC from the CIS was committed last week so you need up to date source. Or do I have to go back to oldcard with pccardd where I can specify the driver in pccardd.conf ? No oldcard and no pccardd. I setup devd to handle card insert/remove. Sam To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Xircom realport rem56g problems
I just built fresh -current (NEWCARD) but it didn't work. I'm beginning to suspect that we have different cards, since the dc driver won't recognize mine. The dc driver seems to expect that vendor id is 0x115d and device id 0x0003. On my card the vendor id is 0x0105 and device id is 0x110a. On the back of the card is says realport ethernet 10/100+modem 56 and REM56G-100. You're correct, I have the RBEM56G-100 and it has vendor id 0x115d. Sorry. Sam To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Xircom realport rem56g problems
From: Sam Leffler [EMAIL PROTECTED] Date: Mon, 9 Dec 2002 09:35:08 -0800 Sender: [EMAIL PROTECTED] I just built fresh -current (NEWCARD) but it didn't work. I'm beginning to suspect that we have different cards, since the dc driver won't recognize mine. The dc driver seems to expect that vendor id is 0x115d and device id 0x0003. On my card the vendor id is 0x0105 and device id is 0x110a. On the back of the card is says realport ethernet 10/100+modem 56 and REM56G-100. You're correct, I have the RBEM56G-100 and it has vendor id 0x115d. Sorry. For the record, the REM56G-100 is a 16-bit card while the RBEM56G-100 is a 32-bit CardBus card with similar functionality (100 Mbps Ethernet and 56 Kbps modem). R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Xircom realport rem56g problems
Hi, I'm trying to get Xircom realport ethernet card (+modem) working on -current (the card works ok on -stable). When plugging the card in, I get: xe0: Xircom CreditCard Ethernet + Modem at port 0x2e8-0x2ef. device_probe_and_attach: xe0 attach returned 19 ie. it returns ENODEV. After browsing around in /sys/dev/xe/if_xe_pccard.c, I noticed that there is a table of various cards against which the driver checks the inserted card. The matching ID for this kind of card would be 0x6 but that is not in table, which causes the driver to return ENODEV. I added an entry with id 0x6 and flags MOHAWK | DINGO (don't know if this is ok, assumed so from -stable messages) No luck with this either. Now there is a loop in driver (line 230 or so) which never reaches XE_CARD_TYPE_FLAGS_DINGO. for(i=1; i!=XE_CARD_TYPE_FLAGS_DINGO; i=i1) , shouldn't this be for(i=1; i!=(XE_CARD_TYPE_FLAGS_DINGO1); i=i1) After changing this, I now get error code 12 (ENOMEM) from xe_activate. There seems to be some kind of a problem in allocating io port or interrupt. Any ideas, what could I try next ? Ari S. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Xircom realport rem56g problems
Try the dc driver instead of xe. I have the same card and it worked once I added the cardbus glop to read the MAC address from the CIS. Sam - Original Message - From: Ari Suutari [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, December 03, 2002 4:41 AM Subject: Xircom realport rem56g problems Hi, I'm trying to get Xircom realport ethernet card (+modem) working on -current (the card works ok on -stable). When plugging the card in, I get: xe0: Xircom CreditCard Ethernet + Modem at port 0x2e8-0x2ef. device_probe_and_attach: xe0 attach returned 19 ie. it returns ENODEV. After browsing around in /sys/dev/xe/if_xe_pccard.c, I noticed that there is a table of various cards against which the driver checks the inserted card. The matching ID for this kind of card would be 0x6 but that is not in table, which causes the driver to return ENODEV. I added an entry with id 0x6 and flags MOHAWK | DINGO (don't know if this is ok, assumed so from -stable messages) No luck with this either. Now there is a loop in driver (line 230 or so) which never reaches XE_CARD_TYPE_FLAGS_DINGO. for(i=1; i!=XE_CARD_TYPE_FLAGS_DINGO; i=i1) , shouldn't this be for(i=1; i!=(XE_CARD_TYPE_FLAGS_DINGO1); i=i1) After changing this, I now get error code 12 (ENOMEM) from xe_activate. There seems to be some kind of a problem in allocating io port or interrupt. Any ideas, what could I try next ? Ari S. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Xircom realport rem56g problems
Hi, On Tuesday 03 December 2002 18:38, Sam Leffler wrote: Try the dc driver instead of xe. I have the same card and it worked once I added the cardbus glop to read the MAC address from the CIS. I was going to use NEWCARD kernel, is it possible to use another driver with it ? Or do I have to go back to oldcard with pccardd where I can specify the driver in pccardd.conf ? Ari S. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
