Re: newcard/cardbus instabilities
In message [EMAIL PROTECTED] Mike Smith writes: : This looks OK, though you might want to disable the pccard support, since : it's known to be broken right now. pccard support is not broken right now. If there's a "known" issue, I sure don't know about it. Oh, sorry, I'm obviously out of date. The problem that Johny was seeing was that 'device pccard' causes broken interrupt delivery for cardbus cards. If that's meant to work, I can see if I can reproduce it locally. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newcard/cardbus instabilities
In message [EMAIL PROTECTED] Mike Smith writes: : The problem that Johny was seeing was that 'device pccard' causes broken : interrupt delivery for cardbus cards. If that's meant to work, I can see : if I can reproduce it locally. It is ment to work and works for me on my VAIO all the time. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newcard/cardbus instabilities
In message [EMAIL PROTECTED] "Johny Mattsson (EPA)" writes: : The xl driver spits out numerous "xl0: watchdog timeout", and I get pings : around the one second mark, even to machines on the same switch. Trying to : maintain TCP sessions without keeping a running ping in the background is : futile, due to the packet loss. : : So basically, I'm wondering what I can do to help getting this : fixed? It looks like the IRQ isn't beeing assigned properly. You'll have to help us figure out why. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newcard/cardbus instabilities
In message [EMAIL PROTECTED] Mike Smith writes: : This looks OK, though you might want to disable the pccard support, since : it's known to be broken right now. pccard support is not broken right now. If there's a "known" issue, I sure don't know about it. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newcard/cardbus instabilities
In message [EMAIL PROTECTED] "Johny Mattsson (EPA)" writes: : I also removed the "device pccard" config option, and as a result : lost support for the modem card, but in return this fixed the : watchdog timeouts, and the lan card works quite well now. : I guess I'll have to keep a backup kernel with the old pcic compiled : in if I want to use the modem... for now I'm very happy to have a : working lan card! Ah. You aren't supposed to compile in both oldcard and newcard at the same time... Wanrer To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: newcard/cardbus instabilities
I'm having problems getting -current (last attempt was 3/16 build) to detect my 3COM network card in my TI CardBus bridge in a Compaq Armada. Actually, worse than that is trying to run the install while the laptop is in a docking station. The system locks up after announcing that it has found a PCMCIA controller. I suspect this is because, while in the docking station, there are two. NetBSD does something similar. While running through the system scan, it announces that it has found one then announces it has found another then stops and says (almost literally), wait, we just saw that. Then it dumps to debug mode. Any experiences or thoughts on getting this to work would be appreciated. I'd love to get a BSD on my laptop. Ric To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newcard/cardbus instabilities
I even have a worse problem. I tried this on my system (a sony vaio PCG-XG18) which has a mini-docking station on the back of it (which allows you access to a third pcmcia slot, and a whole slew of other video goodies/serial ports/etc.). The problem is if the mini docking station isn't there, all the parts/chips/controllers are internal to the laptop, so it still sees them. The cardbus code sees the second controller (which drives the third slot) and than gracefully pukes all over it's self. So unless I have the mini docking station plugged in it doesn't work. But if it is, I can use my xircom rbem56g-100 and a linksys cardbus card just fine. I do however lose the ability to use my wavelan card and my two other pcmcia cards (non cardbus). I can't wait until all these issues are resolved (I really don't wanna run Linux again). This is just a FYI. Greg * Johny Mattsson (EPA) ([EMAIL PROTECTED]) [010323 07:25]: My suggestion? Chop out the power management stuff in xl_attach() and see what happens. Okay, did that. Effect: got rid of the D0/D6 printout, and instead got the following two once I sent something on the interface: cstsevent occures, 0x3410 pwrevent occures, 0x3410 This does not seem to have any adverse effects though. Perhaps worth mentioning is that I get these even if I just reboot from fbsd to fbsd, not only when I do windoze-fbsd. I also removed the "device pccard" config option, and as a result lost support for the modem card, but in return this fixed the watchdog timeouts, and the lan card works quite well now. I guess I'll have to keep a backup kernel with the old pcic compiled in if I want to use the modem... for now I'm very happy to have a working lan card! Thanks a whole lot guys, I really appreciate it! /Johny PS. Sorry if this is still in HTML format, it shouldn't be, but I'm stuck with outlook and it just doesn't seem to want to take a hint. -- Greg Rumple [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newcard/cardbus instabilities
On Fri, 23 Mar 2001, Greg Rumple wrote: I even have a worse problem. I tried this on my system (a sony vaio PCG-XG18) which has a mini-docking station on the back of it (which allows you access to a third pcmcia slot, and a whole slew of other video goodies/serial ports/etc.). The problem is if the mini docking station isn't there, all the parts/chips/controllers are internal to the laptop, so it still sees them. The cardbus code sees the second controller (which drives the third slot) and than gracefully pukes all over it's self. So unless I have the mini docking station plugged in it doesn't work. But if it is, I can use my xircom rbem56g-100 and a linksys cardbus card just fine. I do however lose the ability to use my wavelan card and my two other pcmcia cards (non cardbus). I can't wait until all these issues are resolved (I really don't wanna run Linux again). This is just a FYI. Greg Mind telling me how you got the rbem56g-100 to work? I haven't had any luck getting mine to work in a Dell Inspiron 4000. Frank To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newcard/cardbus instabilities
On 23-Mar-01 Bill Paul wrote: That's a bit ugly. xl0: 3Com 3c575C Fast Etherlink XL port 0x3000-0x307f mem 0x4402-0x4403,0x44002480-0x440024ff,0x44002400-0x4400247f irq 10 at device 0.0 on cardbus1 xl0: chip is in D6 power mode -- setting to D0 I'm a bit worried about this; "D6" doesn't really exist, so it's possible that something is going wrong here. Bill; you might have some better ideas than I do. Suggestions? My suggestion? Chop out the power management stuff in xl_attach() and see what happens. The xl driver is using the pci_get_powerstate() and pci_set_powerstate() routines right now in order to check for PCI NICs that have been forced into the D3 state by Windoze during shutdown. However, those functions are internal to the PCI bus code, and I'm not sure what will happen when you try to use them with devices that are children of a cardbus bus. So, edit /sys/pci/if_xl.c, find the xl_attach() function, and comment out/#ifdef out/delete the section that checks the power state of the card. Like Mike says, the D6 state is bogus. Unfortunately, I can't test this myself at the moment since I find myself without a laptop. I might be able to coerce^Wconvince John Baldwin to let me test this with his though. You'll have to coerce^Wconvince Mike or Warner to fix cardbus resource allocation so that cardbus cards don't try to stomp on PCI devices on my machine and freeze it until I eject the card. :) -Bill -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newcard/cardbus instabilities
Firstly, please don't send HTML mail. It's bad, and people have a hard time dealing with it. Semi-recently grabbed a snapshot of -CURRENT (from 03/06) to see if I could finally get my 3Com 3c575C Fast Etherlink XL cardbus lancard to work. I saw it mentioned in the HARDWARE.TXT so I decided to give it a go. What I didn't realize was that the newcard/cardbus was still in its early stages. So what I am experiencing now is that the card is properly detected (which doesn't happen with the card/pcic devices), _but_ when using it, I experience frequent timeouts and delays. The xl driver spits out numerous "xl0: watchdog timeout", and I get pings around the one second mark, even to machines on the same switch. Trying to maintain TCP sessions without keeping a running ping in the background is futile, due to the packet loss. So basically, I'm wondering what I can do to help getting this fixed? I very much want to see proper cardbus support (having to run windoze to get net connectivity is highly annoying and counter productive). I don't have any means of running cvsup regularly (stuck behind heavy firewall), and I unfortunately have no experience with writing device drivers, but should otherwise be able to tweak code as instructed. I'll be happy to be a testbed for the 3c575C (and I'll be very happy when I can report that it seems to work flawlessly!). ... pccbb0: TI1225 PCI-CardBus Bridge at device 4.0 on pci0 pccbb0: PCI Memory allocated: 4400 pci_cfgintr_unique: hard-routed to irq 10 pci_cfgintr: 0:4 INTA routed to irq 10 cardbus0: Cardbus bus (newcard) on pccbb0 pccard0: 16-bit PCCard bus on pccbb0 pccbb1: TI1225 PCI-CardBus Bridge at device 4.1 on pci0 pccbb1: PCI Memory allocated: 44001000 pci_cfgintr_unique: hard-routed to irq 10 pci_cfgintr: 0:4 INTB routed to irq 10 This looks OK, though you might want to disable the pccard support, since it's known to be broken right now. pccbb1: card inserted: event=0x, state=3b20 pccbb1: pccbb_power: CARD_VCC_0V and CARD_VPP_0V [44] pccbb1: pccbb_power: CARD_VCC_3V and CARD_VPP_VCC [11] pccbb1: bad Vcc request. ctrl=0x33, status=0x3b20 That's a bit ugly. xl0: 3Com 3c575C Fast Etherlink XL port 0x3000-0x307f mem 0x4402-0x4403,0x44002480-0x440024ff,0x44002400-0x4400247f irq 10 at device 0.0 on cardbus1 xl0: chip is in D6 power mode -- setting to D0 I'm a bit worried about this; "D6" doesn't really exist, so it's possible that something is going wrong here. Bill; you might have some better ideas than I do. Suggestions? -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newcard/cardbus instabilities
That's a bit ugly. xl0: 3Com 3c575C Fast Etherlink XL port 0x3000-0x307f mem 0x4402-0x4403,0x44002480-0x440024ff,0x44002400-0x4400247f irq 10 at device 0.0 on cardbus1 xl0: chip is in D6 power mode -- setting to D0 I'm a bit worried about this; "D6" doesn't really exist, so it's possible that something is going wrong here. Bill; you might have some better ideas than I do. Suggestions? My suggestion? Chop out the power management stuff in xl_attach() and see what happens. The xl driver is using the pci_get_powerstate() and pci_set_powerstate() routines right now in order to check for PCI NICs that have been forced into the D3 state by Windoze during shutdown. However, those functions are internal to the PCI bus code, and I'm not sure what will happen when you try to use them with devices that are children of a cardbus bus. So, edit /sys/pci/if_xl.c, find the xl_attach() function, and comment out/#ifdef out/delete the section that checks the power state of the card. Like Mike says, the D6 state is bogus. Unfortunately, I can't test this myself at the moment since I find myself without a laptop. I might be able to coerce^Wconvince John Baldwin to let me test this with his though. -Bill To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: newcard/cardbus instabilities
Title: RE: newcard/cardbus instabilities My suggestion? Chop out the power management stuff in xl_attach() and see what happens. Okay, did that. Effect: got rid of the D0/D6 printout, and instead got the following two once I sent something on the interface: cstsevent occures, 0x3410 pwrevent occures, 0x3410 This does not seem to have any adverse effects though. Perhaps worth mentioning is that I get these even if I just reboot from fbsd to fbsd, not only when I do windoze-fbsd. I also removed the device pccard config option, and as a result lost support for the modem card, but in return this fixed the watchdog timeouts, and the lan card works quite well now. I guess I'll have to keep a backup kernel with the old pcic compiled in if I want to use the modem... for now I'm very happy to have a working lan card! Thanks a whole lot guys, I really appreciate it! /Johny PS. Sorry if this is still in HTML format, it shouldn't be, but I'm stuck with outlook and it just doesn't seem to want to take a hint.
Re: newcard/cardbus instabilities
Hello, just as an additional data-point: I am using an HP Omnibook 4150 (not the 4150B-Version!) with the 3COM-Card just fine. (Actually I am writing this from this machine) The corresponding lines from dmesg are: pccbb0: TI1220 PCI-CardBus Bridge at device 4.0 on pci0 pccbb0: PCI Memory allocated: 4400 pci_cfgintr_unique: hard-routed to irq 10 pci_cfgintr: 0:4 INTA routed to irq 10 cardbus0: Cardbus bus (newcard) on pccbb0 pccard0: 16-bit PCCard bus on pccbb0 pccbb1: TI1220 PCI-CardBus Bridge at device 4.1 on pci0 pccbb1: PCI Memory allocated: 44001000 pci_cfgintr_unique: hard-routed to irq 10 pci_cfgintr: 0:4 INTB routed to irq 10 cardbus1: Cardbus bus (newcard) on pccbb1 pccard1: 16-bit PCCard bus on pccbb1 pccbb0: card inserted: event=0x, state=3820 pccbb0: pccbb_power: CARD_VCC_0V and CARD_VPP_0V [44] pccbb0: pccbb_power: CARD_VCC_3V and CARD_VPP_VCC [11] TUPLE: LINKTARGET [3]: 43 49 53 Manufacturer ID: 01015752 TUPLE: CONFIG_CB [6]: 03 01 00 00 00 00 TUPLE: CFTABLE_ENTRY_CB [13]: 41 9a 01 b5 1e 01 b5 1e 02 30 ff ff 01 cardbus0: Opening BAR: type=IO, bar=10, len=0040 Product version: 5.0 Product name: 3Com Corporation | 3CCFE575CT | LAN Cardbus Card | 004 | Functions: Network Adaptor, Memory CIS reading done xl0: 3Com 3c575C Fast Etherlink XL port 0x3000-0x307f mem 0x4402-0x4403fff f,0x44002080-0x440020ff,0x44002000-0x4400207f irq 10 at device 0.0 on cardbus0 xl0: chip is in D6 power mode -- setting to D0 xl0: Ethernet address: 00:00:86:5b:96:ea miibus0: MII bus on xl0 ukphy0: Generic IEEE 802.3u media interface on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto cardbus1: Detaching card: no cards to detach! pccbb1: pccbb_power: CARD_VCC_0V and CARD_VPP_0V [44] And as you can see I am getting the D6 power-state too, but still everything works fine (as long as I have the card inserted during boot and I do not suspend/resume). I am able to get around 8MBytes/sec with this card. Michael On Thu, 22 Mar 2001, Mike Smith wrote: Firstly, please don't send HTML mail. It's bad, and people have a hard time dealing with it. Semi-recently grabbed a snapshot of -CURRENT (from 03/06) to see if I could finally get my 3Com 3c575C Fast Etherlink XL cardbus lancard to work. I saw it mentioned in the HARDWARE.TXT so I decided to give it a go. What I didn't realize was that the newcard/cardbus was still in its early stages. So what I am experiencing now is that the card is properly detected (which doesn't happen with the card/pcic devices), _but_ when using it, I experience frequent timeouts and delays. The xl driver spits out numerous "xl0: watchdog timeout", and I get pings around the one second mark, even to machines on the same switch. Trying to maintain TCP sessions without keeping a running ping in the background is futile, due to the packet loss. So basically, I'm wondering what I can do to help getting this fixed? I very much want to see proper cardbus support (having to run windoze to get net connectivity is highly annoying and counter productive). I don't have any means of running cvsup regularly (stuck behind heavy firewall), and I unfortunately have no experience with writing device drivers, but should otherwise be able to tweak code as instructed. I'll be happy to be a testbed for the 3c575C (and I'll be very happy when I can report that it seems to work flawlessly!). ... pccbb0: TI1225 PCI-CardBus Bridge at device 4.0 on pci0 pccbb0: PCI Memory allocated: 4400 pci_cfgintr_unique: hard-routed to irq 10 pci_cfgintr: 0:4 INTA routed to irq 10 cardbus0: Cardbus bus (newcard) on pccbb0 pccard0: 16-bit PCCard bus on pccbb0 pccbb1: TI1225 PCI-CardBus Bridge at device 4.1 on pci0 pccbb1: PCI Memory allocated: 44001000 pci_cfgintr_unique: hard-routed to irq 10 pci_cfgintr: 0:4 INTB routed to irq 10 This looks OK, though you might want to disable the pccard support, since it's known to be broken right now. pccbb1: card inserted: event=0x, state=3b20 pccbb1: pccbb_power: CARD_VCC_0V and CARD_VPP_0V [44] pccbb1: pccbb_power: CARD_VCC_3V and CARD_VPP_VCC [11] pccbb1: bad Vcc request. ctrl=0x33, status=0x3b20 That's a bit ugly. xl0: 3Com 3c575C Fast Etherlink XL port 0x3000-0x307f mem 0x4402-0x4403,0x44002480-0x440024ff,0x44002400-0x4400247f irq 10 at device 0.0 on cardbus1 xl0: chip is in D6 power mode -- setting to D0 I'm a bit worried about this; "D6" doesn't really exist, so it's possible that something is going wrong here. Bill; you might have some better ideas than I do. Suggestions? -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL
