Re: PCI-CardBus bridge + PCMCIA Lucent WaveLAN IEEE troubles
John Hay wrote: > > : Are there any datasheets available for this bridge ? > > > > Yes. However, I've had several reports of the lucent wavelan bridge > > working flawlessly. > > I recall (but might be wrong) that most if not all sucess stories are > on notebooks with the TI-1225 on the motherboard. Maybe the notebook > bios do something more than isn't done on a normal pc? My TI-1220 works flawlessly. ed To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCI-CardBus bridge + PCMCIA Lucent WaveLAN IEEE troubles
In message <[EMAIL PROTECTED]> John Hay writes: : our problem is even before a (non) working interrupt would come into the : picture. I'd have to say that based on the evidence so far, that the interrupts aren't getting routined correctly, or that there's an interrupt conflict. This is almost certainly at the cardbus bridge layer, even though I don't want it to be :-) Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCI-CardBus bridge + PCMCIA Lucent WaveLAN IEEE troubles
In message <[EMAIL PROTECTED]> John Hay writes: : I recall (but might be wrong) that most if not all sucess stories are : on notebooks with the TI-1225 on the motherboard. Maybe the notebook : bios do something more than isn't done on a normal pc? That's entirely possible. All notebook BIOSes that I've looked at try to initialize the cardbus bridge into some known state. Many of the initialize it into a state very compatible with FreeBSD's assumptions (sometimes with some setup help from the user). Some don't. Nearly none of the desktops do the right thing as far as initialization of the cards goes, so as we see more card bus bridges we have to get smarters. On the laptops as well, one can add a TI-950 or equivalent part wired to the south bridge (well, the pci isa bridge which I think is usually called the south bridge) which allows one to do serial interrupt ISA routing over the PCI bus. I'm not sure how many desktops, if any, do this sort of thing. I just now found the datasheet from TI and have started looking at it. It does support some kind of PCI standard on the topic, but I've not looked into enough to know how standard this standard is. Briefly, it allows one to route any IRQ or PCI interrupt using a serial protocol for the interrupt. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCI-CardBus bridge + PCMCIA Lucent WaveLAN IEEE troubles
In message <[EMAIL PROTECTED]> Michael Vasilenko writes: : I have only 11 & 15 IRQ used - for Bridge and for NIC OK. : I have only ONE pccard, but why kernel thinks that I have two and : they are inserted? (see at the bottom of dmesg) : Maybe problem in init of TI chip? Likely. That's a problem. : pcic0: at port 0x3e0 iomem 0xd irq 11 on isa0 : pcic0: management irq 11 : ^^ - polling mode for pcic0 didn't solve the problem ok. : pccard: card inserted, slot 1 : ^ : why? bug? : ed0: starting DAD for fe80:0001::0200:21ff:fed7:676e : ed0: DAD complete for fe80:0001::0200:21ff:fed7:676e - no duplicates found : wi0: at port 0x240-0x27f irq 9 slot 0 on pccard0 : ^^ ^^^ :I've tried 0x100,0x300,etc and 5,7,10 ok. I'm not sure what's going on here... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCI-CardBus bridge + PCMCIA Lucent WaveLAN IEEE troubles
> In message <[EMAIL PROTECTED]> John Hay writes: > : This is where I'm stuck too. I think there might be some more initialization > : of the TI1225 necesary. > > I've added some init of the ti chipsets to -current. They are enough > for my TI-1221 based card to allow me to talk to the modems that I > have. Yes, that is the code I'm running. From looking at the wi driver I think our problem is even before a (non) working interrupt would come into the picture. It looks like the driver give a command to the card to allocate a transmit buffer and then it does a poll loop reading the status of the card and it is there that it timeout. Doing some manual inb()s at the port addresses of the wi card, it looks like the card is there, ie. I don't read 0xffs back, but for some reason the card does not react in the way that the driver expects. John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCI-CardBus bridge + PCMCIA Lucent WaveLAN IEEE troubles
> : Are there any datasheets available for this bridge ? > > Yes. However, I've had several reports of the lucent wavelan bridge > working flawlessly. I recall (but might be wrong) that most if not all sucess stories are on notebooks with the TI-1225 on the motherboard. Maybe the notebook bios do something more than isn't done on a normal pc? John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCI-CardBus bridge + PCMCIA Lucent WaveLAN IEEE troubles
On Fri, 14 Apr 2000, Warner Losh wrote: > : The situation is interesting - when I remove /dev/card1,2,3, pccardd > : get started, ifconfig wi0 works, but on any xmit - ping, etc.. > : I've got: > : > : wi0: xmit failed > : wi0: tx buffer allocation failed > : wi0: device timeout > : > : and pccardd didn't catch pccard events - removing and inserting cards... > > You have interrupt problems. Don't share with anything else. Don't > use interrupts of *ANY* other hardware in your system *AT*ALL*. I have only 11 & 15 IRQ used - for Bridge and for NIC Thanks alot, but your input didn't help... I tried different IRQs for pccard, polling and "normal" (have irq) mode, but no success. I have only ONE pccard, but why kernel thinks that I have two and they are inserted? (see at the bottom of dmesg) Maybe problem in init of TI chip? My full dmesg: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #4: Sat Apr 15 10:45:51 GMT 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/SETUP.5 Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 300683001 Hz CPU: Pentium II/Pentium II Xeon/Celeron (300.68-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x634 Stepping = 4 Features=0x80f9ff real memory = 33554432 (32768K bytes) config> q avail memory = 29634560 (28940K bytes) Preloaded elf kernel "kernel" at 0xc031e000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc031e09c. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 isab0: at device 2.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f at device 2.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 pci0: at 2.2 chip1: port 0x5000-0x500f at device 2.3 on pci0 ed0: port 0xe400-0xe41f irq 15 at device 15.0 on pci0 ed0: supplying EUI64: 00:00:21:ff:fe:d7:67:6e ed0: address 00:00:21:d7:67:6e, type NE2000 (16 bit) pcic-pci0: mem 0xea00-0xea000fff irq 11 at device 16.0 on pci0 pcic-pci0: TI12XX PCI Config Reg: [pwr save][pci only] pcic-pci1: mem 0xea004000-0xea004fff irq 11 at device 16.1 on pci0 pcic-pci1: TI12XX PCI Config Reg: [pwr save][pci only] fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> pcic0: at port 0x3e0 iomem 0xd irq 11 on isa0 pcic0: management irq 11 ^^ - polling mode for pcic0 didn't solve the problem pccard0: on pcic0 pccard1: on pcic0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ad0: 4112MB [8912/15/63] at ata0-master using UDMA33 Mounting root from ufs:/dev/ad0s1a pccard: card inserted, slot 0 pccard: card inserted, slot 1 ^ why? ed0: starting DAD for fe80:0001::0200:21ff:fed7:676e ed0: DAD complete for fe80:0001::0200:21ff:fed7:676e - no duplicates found wi0: at port 0x240-0x27f irq 9 slot 0 on pccard0 ^^ ^^^ I've tried 0x100,0x300,etc and 5,7,10 wi0: Ethernet address: 00:60:1d:f6:cc:5d wi0: tx buffer allocation failed wi0: starting DAD for fe80:000b::0260:1dff:fef6:cc5d wi0: xmit failed wi0: DAD complete for fe80:000b::0260:1dff:fef6:cc5d - no duplicates found wi0: device timeout wi0: tx buffer allocation failed wi0: xmit failed wi0: device timeout wi0: tx buffer allocation failed Michael Vasilneko To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCI-CardBus bridge + PCMCIA Lucent WaveLAN IEEE troubles
In message <[EMAIL PROTECTED]> Michael Vasilenko writes: : Are there any datasheets available for this bridge ? Yes. However, I've had several reports of the lucent wavelan bridge working flawlessly. ti's web site has them somewhere. In reading them, I don't see anything that we should do that we're not doing. I don't have an exact URL handy. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCI-CardBus bridge + PCMCIA Lucent WaveLAN IEEE troubles
On Fri, 14 Apr 2000, Warner Losh wrote: > In message <[EMAIL PROTECTED]> John Hay writes: > : This is where I'm stuck too. I think there might be some more initialization > : of the TI1225 necesary. > > I've added some init of the ti chipsets to -current. They are enough > for my TI-1221 based card to allow me to talk to the modems that I > have. But it seems to be not enough for TI-1225... Are there any datasheets available for this bridge ? Michael Vasilenko To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCI-CardBus bridge + PCMCIA Lucent WaveLAN IEEE troubles
Edwin Culp wrote:
> Michael,
>
> I just threw one in my laptop a couple of days ago. I didn't even have to recompile
>the kernel. I just
> added the stock WaveLAN section to my pccard.conf let it load the if_wi.ko and it
>worked. Although when I
> reboot I have to take the card out and put it back in because there seems to be a
>delay with the kernel
> module that causes the driver to initially fail that probably wouldn't happen if I
>had support compiled
> into the kernel, but I really didn't plan to use it that often but it is working so
>well I think that I
> will.
>
> My pccard.conf is :
> # Generally available IO ports
> io 0x240-0x360
> # Generally available IRQs (Built-in sound-card owners remove 5)
> irq 9 11
> #
> # Cut out my modem and nic entries.
> #
> # Lucent WaveLAN/IEEE
> card "Lucent Technologies" "WaveLAN/IEEE"
> config 0x1 "wi0" ?
> insert logger -t pccard:$device -s WaveLAN/IEEE inserted
> insert /etc/pccard_ether $device
> remove logger -t pccard:$device -s WaveLAN/IEEE removed
> remove /sbin/ifconfig $device delete
>
> The messages are:
> # kldstat
>1 0xc0c73000 5000 if_wi.ko
>
> pccard1: on pcic0
> pccard: card inserted, slot 0
> pccard: card removed, slot 0
> pccard: card inserted, slot 0
> wi0: at port 0x240-0x27f irq 9 slot 0 on pccard0
> wi0: Ethernet address: 00:60:1d:03:f4:08
Forgot, sorry. The difference that I see is that you have TI PCI-1225.
pcic-pci0: irq 10 at device 3.0 on pci0
pcic-pci0: TI12XX PCI Config Reg: [speaker enable][pwr save][CSC serial isa irq]
pcic-pci1: irq 10 at device 3.1 on pci0
pcic-pci1: TI12XX PCI Config Reg: [speaker enable][pwr save][CSC serial isa irq]
pcic0: at port 0x3e0-0x3e1 on isa0
pcic0: Polling mode
>
>
> Hope this helps.
>
> ed
>
> P.S. I did have to make some configuration changes with wicontrol to communicate
>with my in-talk/nokia
> access point.
>
> "Michael I. Vasilenko" wrote:
>
> > Recently our firm bought Lucent wireless hardware - PCI Adapter and
> > PCMCIA card. After unsucsessfull trying to get it work on 3.4+PAO,
> > I've upgraded to 5.0-CURRENT.
> >
> > All hardware ssems to be detected, pccardc pccardmem 0xd4000 is ok,
> > but after running pccardd it says:
> >
> > pccardd[166]: Card "Lucent Technologies"("WaveLAN/IEEE") matched "Lucent
>Technologies" ("WaveLAN/IEEE")
> > pccardd[166]: Using I/O addr 0x100, size 64
> > pccardd[166]: Setting config reg at offs 0x3e0 to 0x41, Reset time = 50 ms
> > pccardd[166]: Assigning I/O window 0, start 0x100, size 0x40 flags 0x5
> > /kernel: wi0: at port 0x100-0x13f irq 7 slot 0 on pccard0
> > /kernel: wi0: Ethernet address: 00:60:1d:f6:cc:5d
> >
> > and machine just hangs completly.
> >
> > Any help would be great.
> >
> > kernel config:
> >
> > device card
> > device pcic0 at isa?
> > device wi
> >
> > kernel.conf:
> >
> > config> port pcic0 0x3e0
> > config> irq pcic0 5
> > config> iomem pcic0 0xd4000
> > config> q
> >
> > pieces of dmesg:
> >
> > ...
> > pcic-pci0: mem 0xea00-0xea000fff irq 10 at
>device 16.0 on pci0
> > pcic-pci0: TI12XX PCI Config Reg: [pwr save][pci only]
> > pcic-pci0: Legacy address set to 0x3e0
> > pcic-pci1: mem 0xea004000-0xea004fff irq 10 at
>device 16.1 on pci0
> > pcic-pci1: TI12XX PCI Config Reg: [pwr save][pci only]
> > ...
> > pcic0: at port 0x3e0 iomem 0xd4000 irq 5 drq 0 on isa0
> > pcic0: management irq 5
> > pccard0: on pcic0
> > pccard1: on pcic0
> > ...
> > pccard: card inserted, slot 0
> > pccard: card inserted, slot 1
> >
> > 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
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: PCI-CardBus bridge + PCMCIA Lucent WaveLAN IEEE troubles
Michael,
I just threw one in my laptop a couple of days ago. I didn't even have to recompile
the kernel. I just
added the stock WaveLAN section to my pccard.conf let it load the if_wi.ko and it
worked. Although when I
reboot I have to take the card out and put it back in because there seems to be a
delay with the kernel
module that causes the driver to initially fail that probably wouldn't happen if I had
support compiled
into the kernel, but I really didn't plan to use it that often but it is working so
well I think that I
will.
My pccard.conf is :
# Generally available IO ports
io 0x240-0x360
# Generally available IRQs (Built-in sound-card owners remove 5)
irq 9 11
#
# Cut out my modem and nic entries.
#
# Lucent WaveLAN/IEEE
card "Lucent Technologies" "WaveLAN/IEEE"
config 0x1 "wi0" ?
insert logger -t pccard:$device -s WaveLAN/IEEE inserted
insert /etc/pccard_ether $device
remove logger -t pccard:$device -s WaveLAN/IEEE removed
remove /sbin/ifconfig $device delete
The messages are:
# kldstat
1 0xc0c73000 5000 if_wi.ko
pccard1: on pcic0
pccard: card inserted, slot 0
pccard: card removed, slot 0
pccard: card inserted, slot 0
wi0: at port 0x240-0x27f irq 9 slot 0 on pccard0
wi0: Ethernet address: 00:60:1d:03:f4:08
Hope this helps.
ed
P.S. I did have to make some configuration changes with wicontrol to communicate with
my in-talk/nokia
access point.
"Michael I. Vasilenko" wrote:
> Recently our firm bought Lucent wireless hardware - PCI Adapter and
> PCMCIA card. After unsucsessfull trying to get it work on 3.4+PAO,
> I've upgraded to 5.0-CURRENT.
>
> All hardware ssems to be detected, pccardc pccardmem 0xd4000 is ok,
> but after running pccardd it says:
>
> pccardd[166]: Card "Lucent Technologies"("WaveLAN/IEEE") matched "Lucent
>Technologies" ("WaveLAN/IEEE")
> pccardd[166]: Using I/O addr 0x100, size 64
> pccardd[166]: Setting config reg at offs 0x3e0 to 0x41, Reset time = 50 ms
> pccardd[166]: Assigning I/O window 0, start 0x100, size 0x40 flags 0x5
> /kernel: wi0: at port 0x100-0x13f irq 7 slot 0 on pccard0
> /kernel: wi0: Ethernet address: 00:60:1d:f6:cc:5d
>
> and machine just hangs completly.
>
> Any help would be great.
>
> kernel config:
>
> device card
> device pcic0 at isa?
> device wi
>
> kernel.conf:
>
> config> port pcic0 0x3e0
> config> irq pcic0 5
> config> iomem pcic0 0xd4000
> config> q
>
> pieces of dmesg:
>
> ...
> pcic-pci0: mem 0xea00-0xea000fff irq 10 at
>device 16.0 on pci0
> pcic-pci0: TI12XX PCI Config Reg: [pwr save][pci only]
> pcic-pci0: Legacy address set to 0x3e0
> pcic-pci1: mem 0xea004000-0xea004fff irq 10 at
>device 16.1 on pci0
> pcic-pci1: TI12XX PCI Config Reg: [pwr save][pci only]
> ...
> pcic0: at port 0x3e0 iomem 0xd4000 irq 5 drq 0 on isa0
> pcic0: management irq 5
> pccard0: on pcic0
> pccard1: on pcic0
> ...
> pccard: card inserted, slot 0
> pccard: card inserted, slot 1
>
> 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: PCI-CardBus bridge + PCMCIA Lucent WaveLAN IEEE troubles
In message <[EMAIL PROTECTED]> John Hay writes: : This is where I'm stuck too. I think there might be some more initialization : of the TI1225 necesary. I've added some init of the ti chipsets to -current. They are enough for my TI-1221 based card to allow me to talk to the modems that I have. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCI-CardBus bridge + PCMCIA Lucent WaveLAN IEEE troubles
In message <[EMAIL PROTECTED]> John Hay writes: : Uhmm, but if pcic use that interrupt, then there is no interrupt that : pccardd can give to the pcmcia card? Or can you have more than one : interrupt from the PCI card to the motherboard? Yes. PCI cards have 4 different interrupt lines, although FreeBSD doesn't use pcibios to route the other lines. If you can't get another irq line routed on your machine, then you'll have to use polling for the pcic and use irq10 for the cards that you insert. My desktop with a cardbus bridge just works with one irq line for management, and a different one for card operations. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCI-CardBus bridge + PCMCIA Lucent WaveLAN IEEE troubles
> > > Delete or rename /dev/card1 and you should get further. It will most > > probably still not work, but it won't hang anymore. > > Thanks, it still don't work, but didn't hang anymore :) > > > You probably also have to tell pccardd to use the same interrupt that > > pcic-pci0 got, because I don't see how else it can work, but I'm not > > sure. I mean a PCI card can't generate different interrupts than the > > one(s) connected to its pins can it? > > The situation is interesting - when I remove /dev/card1,2,3, pccardd > get started, ifconfig wi0 works, but on any xmit - ping, etc.. > I've got: > > wi0: xmit failed > wi0: tx buffer allocation failed > wi0: device timeout > This is where I'm stuck too. I think there might be some more initialization of the TI1225 necesary. John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCI-CardBus bridge + PCMCIA Lucent WaveLAN IEEE troubles
> In message <[EMAIL PROTECTED]> John Hay writes: > : You probably also have to tell pccardd to use the same interrupt that > : pcic-pci0 got, because I don't see how else it can work, but I'm not > : sure. I mean a PCI card can't generate different interrupts than the > : one(s) connected to its pins can it? > > No. You have to tell pcic to use that interrupt. and tell pccardd to > *NOT* use that interrupt. Interrupt sharing rarely works when pccard > is in the mix. Don't do it, unless you know what you are doing. And > even then, if anything at all doesn't work, stop doing it. Uhmm, but if pcic use that interrupt, then there is no interrupt that pccardd can give to the pcmcia card? Or can you have more than one interrupt from the PCI card to the motherboard? John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCI-CardBus bridge + PCMCIA Lucent WaveLAN IEEE troubles
In message <[EMAIL PROTECTED]> Michael Vasilenko writes: : : : On Fri, 14 Apr 2000, John Hay wrote: : : > Delete or rename /dev/card1 and you should get further. It will most : > probably still not work, but it won't hang anymore. : : Thanks, it still don't work, but didn't hang anymore :) : : > You probably also have to tell pccardd to use the same interrupt that : > pcic-pci0 got, because I don't see how else it can work, but I'm not : > sure. I mean a PCI card can't generate different interrupts than the : > one(s) connected to its pins can it? : : The situation is interesting - when I remove /dev/card1,2,3, pccardd : get started, ifconfig wi0 works, but on any xmit - ping, etc.. : I've got: : : wi0: xmit failed : wi0: tx buffer allocation failed : wi0: device timeout : : and pccardd didn't catch pccard events - removing and inserting cards... You have interrupt problems. Don't share with anything else. Don't use interrupts of *ANY* other hardware in your system *AT*ALL*. I'll be the first to talk about how bad interrupt choice is in the current pccard code. I'm also one of the first to be doing something about it with NEWCARD... :-) Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCI-CardBus bridge + PCMCIA Lucent WaveLAN IEEE troubles
In message <[EMAIL PROTECTED]> John Hay writes: : You probably also have to tell pccardd to use the same interrupt that : pcic-pci0 got, because I don't see how else it can work, but I'm not : sure. I mean a PCI card can't generate different interrupts than the : one(s) connected to its pins can it? No. You have to tell pcic to use that interrupt. and tell pccardd to *NOT* use that interrupt. Interrupt sharing rarely works when pccard is in the mix. Don't do it, unless you know what you are doing. And even then, if anything at all doesn't work, stop doing it. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCI-CardBus bridge + PCMCIA Lucent WaveLAN IEEE troubles
On Fri, 14 Apr 2000, John Hay wrote: > Delete or rename /dev/card1 and you should get further. It will most > probably still not work, but it won't hang anymore. Thanks, it still don't work, but didn't hang anymore :) > You probably also have to tell pccardd to use the same interrupt that > pcic-pci0 got, because I don't see how else it can work, but I'm not > sure. I mean a PCI card can't generate different interrupts than the > one(s) connected to its pins can it? The situation is interesting - when I remove /dev/card1,2,3, pccardd get started, ifconfig wi0 works, but on any xmit - ping, etc.. I've got: wi0: xmit failed wi0: tx buffer allocation failed wi0: device timeout and pccardd didn't catch pccard events - removing and inserting cards... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCI-CardBus bridge + PCMCIA Lucent WaveLAN IEEE troubles
Delete or rename /dev/card1 and you should get further. It will most
probably still not work, but it won't hang anymore.
You probably also have to tell pccardd to use the same interrupt that
pcic-pci0 got, because I don't see how else it can work, but I'm not
sure. I mean a PCI card can't generate different interrupts than the
one(s) connected to its pins can it?
John
--
John Hay -- [EMAIL PROTECTED]
>
> Recently our firm bought Lucent wireless hardware - PCI Adapter and
> PCMCIA card. After unsucsessfull trying to get it work on 3.4+PAO,
> I've upgraded to 5.0-CURRENT.
>
> All hardware ssems to be detected, pccardc pccardmem 0xd4000 is ok,
> but after running pccardd it says:
>
> pccardd[166]: Card "Lucent Technologies"("WaveLAN/IEEE") matched "Lucent
>Technologies" ("WaveLAN/IEEE")
> pccardd[166]: Using I/O addr 0x100, size 64
> pccardd[166]: Setting config reg at offs 0x3e0 to 0x41, Reset time = 50 ms
> pccardd[166]: Assigning I/O window 0, start 0x100, size 0x40 flags 0x5
> /kernel: wi0: at port 0x100-0x13f irq 7 slot 0 on pccard0
> /kernel: wi0: Ethernet address: 00:60:1d:f6:cc:5d
>
> and machine just hangs completly.
>
> Any help would be great.
>
> kernel config:
>
> devicecard
> devicepcic0 at isa?
> devicewi
>
> kernel.conf:
>
> config> port pcic0 0x3e0
> config> irq pcic0 5
> config> iomem pcic0 0xd4000
> config> q
>
> pieces of dmesg:
>
> ...
> pcic-pci0: mem 0xea00-0xea000fff irq 10 at
>device 16.0 on pci0
> pcic-pci0: TI12XX PCI Config Reg: [pwr save][pci only]
> pcic-pci0: Legacy address set to 0x3e0
> pcic-pci1: mem 0xea004000-0xea004fff irq 10 at
>device 16.1 on pci0
> pcic-pci1: TI12XX PCI Config Reg: [pwr save][pci only]
> ...
> pcic0: at port 0x3e0 iomem 0xd4000 irq 5 drq 0 on isa0
> pcic0: management irq 5
> pccard0: on pcic0
> pccard1: on pcic0
> ...
> pccard: card inserted, slot 0
> pccard: card inserted, slot 1
>
>
>
>
> 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: PCI-CardBus bridge + PCMCIA Lucent WaveLAN IEEE troubles
Of all the gin joints in all the towns in all the world, Michael I.
Vasilenko had to walk into mine and say:
> pccardd[166]: Card "Lucent Technologies"("WaveLAN/IEEE") matched "Lucent
>Technologies" ("WaveLAN/IEEE")
> pccardd[166]: Using I/O addr 0x100, size 64
> pccardd[166]: Setting config reg at offs 0x3e0 to 0x41, Reset time = 50 ms
> pccardd[166]: Assigning I/O window 0, start 0x100, size 0x40 flags 0x5
> /kernel: wi0: at port 0x100-0x13f irq 7 slot 0 on pccard0
> /kernel: wi0: Ethernet address: 00:60:1d:f6:cc:5d ^^^
>
> and machine just hangs completly.
You did disable the parallel port on this machine so that you can safely
use IRQ 7, right? And I don't mean "take the parallel port driver out
of the kernel config." I mean "go into the computer's BIOS setup screen
and turn the parallel port off."
-Bill
--
=
-Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu
Work: [EMAIL PROTECTED] | Center for Telecommunications Research
Home: [EMAIL PROTECTED] | Columbia University, New York City
=
"It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness"
=
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
