wi0 is always status: no carrier
I've finally coerced FreeBSD 5.4 to see my PCMCIA WLAN card (with many thanks to Warner), but it always reports "status: no carrier". I'm attempting to connect to an open WAP that broadcasts it's SSID, so my understanding is that it should be as simple as "ifconfig wi0 ad.dr.es.s netmask 255.255.255.0" or "dhclient wi0", but neither of those work. If I do manually specify an address, then I can ping that address, but I'm not sure if that actually means anything. I've also been running tcpdump on the DHCP server for that wireless network. I can see plenty of traffic from the other machines, but absolutely nothing from the laptop. My /boot/loader.conf looks like: hint.acpi.0.disabled="1" hint.apic.0.disabled="1" hw.cbb.start_memory=0xd800 Is there something else I'm blatantly missing? -- Kirk Strauser pgp9kYEVrUpMN.pgp Description: PGP signature
Re: wi0 is always status: no carrier
On Thu, 12 May 2005, Kirk Strauser wrote: I've finally coerced FreeBSD 5.4 to see my PCMCIA WLAN card (with many thanks to Warner), but it always reports "status: no carrier". I'm attempting to connect to an open WAP that broadcasts it's SSID, so my understanding is that it should be as simple as "ifconfig wi0 ad.dr.es.s netmask 255.255.255.0" or "dhclient wi0", but neither of those work. Be sure to set the ssid: ifconfig wi0 ssid whatever -- Tod McQuillin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: wi0 is always status: no carrier
> Is there something else I'm blatantly missing? If my memory serves me correctly, you need to explicitely force the interface up, eg: # ifconfig wi0 up After setting the SSID. Mine works after doing this, it's an ASUS WL-100. -- Rink P.W. Springer- http://rink.nu "God, root, what is difference?" - Pitr, Userfriendly pgpFSK1QXHfpQ.pgp Description: PGP signature
Re: wi0 is always status: no carrier
In message: <[EMAIL PROTECTED]> Kirk Strauser <[EMAIL PROTECTED]> writes: : I've finally coerced FreeBSD 5.4 to see my PCMCIA WLAN card (with many thanks : to Warner), but it always reports "status: no carrier". I'm attempting to : connect to an open WAP that broadcasts it's SSID, so my understanding is that : it should be as simple as "ifconfig wi0 ad.dr.es.s netmask 255.255.255.0" or : "dhclient wi0", but neither of those work. If I do manually specify an : address, then I can ping that address, but I'm not sure if that actually : means anything. : : I've also been running tcpdump on the DHCP server for that wireless network. : I can see plenty of traffic from the other machines, but absolutely nothing : from the laptop. : : My /boot/loader.conf looks like: : : hint.acpi.0.disabled="1" : hint.apic.0.disabled="1" : hw.cbb.start_memory=0xd800 : : Is there something else I'm blatantly missing? Kirk's dmesg showed some interesting IRQ routing issues that might be the problem: pir0: on motherboard $PIR: BIOS IRQ 11 for 0.7.INTA is not valid for link 0x22 $PIR: BIOS IRQ 11 for 0.7.INTB is not valid for link 0x22 Can you send me the output of http://people.freebsd.org/~msmith/pir.c to make sure that's not the problem. What does vmstat show for irq 10? How about other IRQs? Warner ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: wi0 is always status: no carrier
On Friday 13 May 2005 04:06 pm, M. Warner Losh wrote: > Kirk's dmesg showed some interesting IRQ routing issues that might be > the problem: > > pir0: on motherboard > $PIR: BIOS IRQ 11 for 0.7.INTA is not valid for link 0x22 > $PIR: BIOS IRQ 11 for 0.7.INTB is not valid for link 0x22 > > Can you send me the output of http://people.freebsd.org/~msmith/pir.c > to make sure that's not the problem. Here it is: $PIR table at 0x2816d890 version 1.0 PCI interrupt router at 0:0.0 vendor 0x0 device 0x0 PCI-only interrupts [ 11] entry bus slot device 00: 00 0008 INTA 00 [ ] INTB 00 [ ] INTC 00 [ ] INTD 00 [ ] 01: 00 0004 INTA 02 [ 9 ] INTB 00 [ ] INTC 00 [ ] INTD 00 [ ] 02: 00 0006 INTA 00 [ ] INTB 00 [ ] INTC 00 [ ] INTD 00 [ ] 03: 00 0007 INTA 22 [10 ] INTB 22 [10 ] INTC 22 [10 ] INTD 22 [10 ] > What does vmstat show for irq 10? How about other IRQs? It doesn't show irq 10 at all: interrupt total rate irq0: clk 74997 99 irq1: atkbd0 975 1 irq6: fdc0 209 0 irq7: ppc0 1 0 irq8: rtc 96004127 irq13: npx01 0 irq14: ata0 2777 3 irq15: ata1 50 0 Total 175014233 -- Kirk Strauser pgpTLI84LAcLN.pgp Description: PGP signature
Re: wi0 is always status: no carrier
In message: <[EMAIL PROTECTED]>
Kirk Strauser <[EMAIL PROTECTED]> writes:
: On Friday 13 May 2005 04:06 pm, M. Warner Losh wrote:
:
: > Kirk's dmesg showed some interesting IRQ routing issues that might be
: > the problem:
: >
: > pir0: on motherboard
: > $PIR: BIOS IRQ 11 for 0.7.INTA is not valid for link 0x22
: > $PIR: BIOS IRQ 11 for 0.7.INTB is not valid for link 0x22
: >
: > Can you send me the output of http://people.freebsd.org/~msmith/pir.c
: > to make sure that's not the problem.
:
: Here it is:
:
: $PIR table at 0x2816d890 version 1.0
: PCI interrupt router at 0:0.0 vendor 0x0 device 0x0
: PCI-only interrupts [ 11]
: entry bus slot device
: 00: 00 0008 INTA 00 [ ]
: INTB 00 [ ]
: INTC 00 [ ]
: INTD 00 [ ]
: 01: 00 0004 INTA 02 [ 9 ]
: INTB 00 [ ]
: INTC 00 [ ]
: INTD 00 [ ]
: 02: 00 0006 INTA 00 [ ]
: INTB 00 [ ]
: INTC 00 [ ]
: INTD 00 [ ]
: 03: 00 0007 INTA 22 [10 ]
: INTB 22 [10 ]
: INTC 22 [10 ]
: INTD 22 [10 ]
:
:
: > What does vmstat show for irq 10? How about other IRQs?
:
: It doesn't show irq 10 at all:
:
: interrupt total rate
: irq0: clk 74997 99
: irq1: atkbd0 975 1
: irq6: fdc0 209 0
: irq7: ppc0 1 0
: irq8: rtc 96004127
: irq13: npx01 0
: irq14: ata0 2777 3
: irq15: ata1 50 0
OK. It looks like the PCI routing code in this case is in error. It
assumes that PCI only interrupts are the only ones that can be in the
PIR table (not sure why it doesn't complain about irq9 in INTA for
your device at pci0.4, but that's likely because there's no device in
dmesg there).
In src/sys/i386/pci/pci_pir.c, try changing:
static int
pci_pir_valid_irq(struct pci_link *pci_link, int irq)
{
if (!PCI_INTERRUPT_VALID(irq))
return (0);
return (pci_link->pl_irqmask & (1 << irq));
}
to be
static int
pci_pir_valid_irq(struct pci_link *pci_link, int irq)
{
if (!PCI_INTERRUPT_VALID(irq))
return (0);
return (1);
}
and let me know if it works for you. The older code, before some
recent changes, didn't have this sanity check in it because many older
systems were, ummm, suboptimal in how they presented the $PIR to the
system. Looks like you might have one of these systems. I think I
still have a laptop that had this defect in my laptop pile, but
finding it may be hard...
Warner
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: wi0 is always status: no carrier
On May 14, 2005, at 1:54 AM, M. Warner Losh wrote: In message: <[EMAIL PROTECTED]> Kirk Strauser <[EMAIL PROTECTED]> writes: : On Friday 13 May 2005 04:06 pm, M. Warner Losh wrote: : : > Kirk's dmesg showed some interesting IRQ routing issues that might be : > the problem: : > : > pir0: on motherboard : > $PIR: BIOS IRQ 11 for 0.7.INTA is not valid for link 0x22 : > $PIR: BIOS IRQ 11 for 0.7.INTB is not valid for link 0x22 : > : > Can you send me the output of http://people.freebsd.org/~msmith/pir.c : > to make sure that's not the problem. : : Here it is: : : $PIR table at 0x2816d890 version 1.0 : PCI interrupt router at 0:0.0 vendor 0x0 device 0x0 : PCI-only interrupts [ 11] : entry bus slot device : 00: 00 0008 INTA 00 [ ] : INTB 00 [ ] : INTC 00 [ ] : INTD 00 [ ] : 01: 00 0004 INTA 02 [ 9 ] : INTB 00 [ ] : INTC 00 [ ] : INTD 00 [ ] : 02: 00 0006 INTA 00 [ ] : INTB 00 [ ] : INTC 00 [ ] : INTD 00 [ ] : 03: 00 0007 INTA 22 [10 ] : INTB 22 [10 ] : INTC 22 [10 ] : INTD 22 [10 ] : : : > What does vmstat show for irq 10? How about other IRQs? : : It doesn't show irq 10 at all: : : interrupt total rate : irq0: clk 74997 99 : irq1: atkbd0 975 1 : irq6: fdc0 209 0 : irq7: ppc0 1 0 : irq8: rtc 96004127 : irq13: npx01 0 : irq14: ata0 2777 3 : irq15: ata1 50 0 OK. It looks like the PCI routing code in this case is in error. It assumes that PCI only interrupts are the only ones that can be in the PIR table (not sure why it doesn't complain about irq9 in INTA for your device at pci0.4, but that's likely because there's no device in dmesg there). That's not what it means. The 'BIOS IRQ' bit means that it read IRQ 11 out of the intlin register because the BIOS put it there, but the BIOS value seems invalid. I have a patch to make the PIR code trust the BIOS in this case over the $PIR table that you can test if you want. Actually, I committed the patch finally a while ago. It is rev 1.117 in HEAD. It should backport to 5.x directly. Try that and see if it fixes your problem. -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: wi0 is always status: no carrier
In message: <[EMAIL PROTECTED]> John Baldwin <[EMAIL PROTECTED]> writes: : : On May 14, 2005, at 1:54 AM, M. Warner Losh wrote: : : > In message: <[EMAIL PROTECTED]> : > Kirk Strauser <[EMAIL PROTECTED]> writes: : > : On Friday 13 May 2005 04:06 pm, M. Warner Losh wrote: : > : : > : > Kirk's dmesg showed some interesting IRQ routing issues that might : > be : > : > the problem: : > : > : > : > pir0: on motherboard : > : > $PIR: BIOS IRQ 11 for 0.7.INTA is not valid for link 0x22 : > : > $PIR: BIOS IRQ 11 for 0.7.INTB is not valid for link 0x22 : > : > : > : > Can you send me the output of : > http://people.freebsd.org/~msmith/pir.c : > : > to make sure that's not the problem. : > : : > : Here it is: : > : : > : $PIR table at 0x2816d890 version 1.0 : > : PCI interrupt router at 0:0.0 vendor 0x0 device 0x0 : > : PCI-only interrupts [ 11] : > : entry bus slot device : > : 00: 00 0008 INTA 00 [ : > ] : > : INTB 00 [ : > ] : > : INTC 00 [ : > ] : > : INTD 00 [ : > ] : > : 01: 00 0004 INTA 02 [ 9 : > ] : > : INTB 00 [ : > ] : > : INTC 00 [ : > ] : > : INTD 00 [ : > ] : > : 02: 00 0006 INTA 00 [ : > ] : > : INTB 00 [ : > ] : > : INTC 00 [ : > ] : > : INTD 00 [ : > ] : > : 03: 00 0007 INTA 22 [10 : > ] : > : INTB 22 [10 : > ] : > : INTC 22 [10 : > ] : > : INTD 22 [10 : > ] : > : : > : : > : > What does vmstat show for irq 10? How about other IRQs? : > : : > : It doesn't show irq 10 at all: : > : : > : interrupt total rate : > : irq0: clk 74997 99 : > : irq1: atkbd0 975 1 : > : irq6: fdc0 209 0 : > : irq7: ppc0 1 0 : > : irq8: rtc 96004127 : > : irq13: npx01 0 : > : irq14: ata0 2777 3 : > : irq15: ata1 50 0 : > : > OK. It looks like the PCI routing code in this case is in error. It : > assumes that PCI only interrupts are the only ones that can be in the : > PIR table (not sure why it doesn't complain about irq9 in INTA for : > your device at pci0.4, but that's likely because there's no device in : > dmesg there). : : That's not what it means. The 'BIOS IRQ' bit means that it read IRQ 11 : out of the intlin register because the BIOS put it there, but the BIOS : value seems invalid. I have a patch to make the PIR code trust the : BIOS in this case over the $PIR table that you can test if you want. : Actually, I committed the patch finally a while ago. It is rev 1.117 : in HEAD. It should backport to 5.x directly. Try that and see if it : fixes your problem. That makes some sense. The device probes at 10, but if it really should be 11, then that would explain it all. Warner ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: wi0 is always status: no carrier
On Friday 20 May 2005 10:20 pm, John Baldwin wrote: > I have a patch to make the PIR code trust the BIOS in this case over the > $PIR table that you can test if you want. Actually, I committed the patch > finally a while ago. It is rev 1.117 in HEAD. It should backport to 5.x > directly. Try that and see if it fixes your problem. I wiped the drive and started over with a new install. Then, I applied your patch and rebooted into the new kernel. My dmesg output was identical between the two kernels (save for the normal little things like minor skew in clock rates). Pardon my ignorance, but should I be somehow requesting that my cbb device get bound to IRQ 11 instead of 10? There's no line containing "cbb" in /boot/device.hints; should I add one? -- Kirk Strauser pgpvNLWdUrcKr.pgp Description: PGP signature
Re: wi0 is always status: no carrier
On Friday 27 May 2005 02:48 pm, you wrote: > The patch should change the IRQ numbers and also print out a line about how > it is trusting your BIOS over the $PIR, so I think you didn't backport the > patch correctly or boot the patched kernel somehow. Here's what I did: 1) Install 5.4 to an empty drive. 2) Create a minimal /boot/loader.conf: hw.ata.ata_dma="0" hw.ata.atapi_dma="0" hw.cbb.start_memory="0xd8000" boot_verbose="YES" because FreeBSD picks the wrong DMA mode for my drive, and following Warner's advice to use the right memory segment for the PCMCIA card. 3) Cold reboot, boot into GENERIC, and capture dmesg1 (attached). 4) Get http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/pci/pci_pir.c (version 1.117 2005/04/14 18:25:09 jhb, md5 12c65b66c81266694bf2a87dc36cae6e) and move it onto the laptop. 5) cd /usr/src/sys/i386/pci; rm pci_pir.c; cp /tmp/pci_pir.c . (the one from step 4 above) 6) cd /usr/src/sys/i386/conf; cp GENERIC WOOZLE 7) cd /usr/src; make buildkernel KERNCONF=WOOZLE; make installkernel KERNCONF=WOOZLE 8) Cold reboot into the new kernel and capture dmesg2 (attached). The two kernels are different sizes (5896397 for GENERIC and 5896729 for WOOZLE), and I can't imagine how the old pci_pir.c would be in there (since I explicitly deleted it from the drive before compiling the new kernel), yet the dmesgs really are almost identical: $ diff -u dmesg1 dmesg2 --- dmesg1 Fri May 27 22:03:56 2005 +++ dmesg2 Fri May 27 22:39:45 2005 @@ -1,13 +1,13 @@ Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. -FreeBSD 5.4-RELEASE #0: Sun May 8 10:21:06 UTC 2005 -[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC +FreeBSD 5.4-RELEASE #0: Fri May 27 22:32:39 CDT 2005 +root@:/usr/obj/usr/src/sys/WOOZLE Preloaded elf kernel "/boot/kernel/kernel" at 0xc09df000. -Calibrating clock(s) ... i8254 clock: 1193114 Hz +Calibrating clock(s) ... i8254 clock: 1193115 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 -Calibrating TSC clock ... TSC clock: 334093721 Hz +Calibrating TSC clock ... TSC clock: 334093741 Hz CPU: AMD-K6(tm) 3D+ Processor (334.09-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x591 Stepping = 1 Features=0x8021bf @@ -415,7 +415,7 @@ unknown: at port 0x2f8-0x2ff on isa0 Device configuration finished. procfs registered -Timecounter "TSC" frequency 334093721 Hz quality 800 +Timecounter "TSC" frequency 334093741 Hz quality 800 Timecounters tick every 10.000 msec lo0: bpf attached ata0-master: pio=0x0c wdma=0x22 udma=0x44 cable=80pin Any other ideas of what I might try? The draw of the Gentoo is strengthening, but I really don't want to go that route. -- Kirk Strauser Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.4-RELEASE #0: Sun May 8 10:21:06 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel "/boot/kernel/kernel" at 0xc09df000. Calibrating clock(s) ... i8254 clock: 1193114 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 334093721 Hz CPU: AMD-K6(tm) 3D+ Processor (334.09-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x591 Stepping = 1 Features=0x8021bf AMD Features=0x8800 Data TLB: 128 entries, 2-way associative Instruction TLB: 64 entries, 1-way associative L1 data cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative L1 instruction cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative L2 internal cache: 256 kbytes, 32 bytes/line, 2 lines/tag, 4-way associative Write Allocate Disable real memory = 402653184 (384 MB) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x0010 - 0x003f, 3145728 bytes (768 pages) 0x00c25000 - 0x1790, 382644224 bytes (93419 pages) avail memory = 384335872 (366 MB) bios32: Found BIOS32 Service Directory header at 0xc00fa700 bios32: Entry = 0xfab80 (c00fab80) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0xabb0 pnpbios: Found PnP BIOS data at 0xc00fb720 pnpbios: Entry = f:b748 Rev = 1.0 Other BIOS signatures found: wlan: <802.11 Link Layer> mem: K6-family MTRR support enabled (2 registers) null: random: io: npx0: [FAST] npx0: on motherboard npx0: INT 16 interface cpu0 on motherboard pci_open(1):mode 1 addr port (0x0cf8) is 0x8848 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=c7011045) pcibios: BIOS version 2.10 Found $PIR table, 4 entries at 0xc00fd890 PCI-Only Interrupts: 11 Location Bus Device Pin
Re: wi0 is always status: no carrier
On Sunday 22 May 2005 06:24 pm, Kirk Strauser wrote: > On Friday 20 May 2005 10:20 pm, John Baldwin wrote: > > I have a patch to make the PIR code trust the BIOS in this case over the > > $PIR table that you can test if you want. Actually, I committed the > > patch finally a while ago. It is rev 1.117 in HEAD. It should backport > > to 5.x directly. Try that and see if it fixes your problem. > > I wiped the drive and started over with a new install. Then, I applied > your patch and rebooted into the new kernel. My dmesg output was identical > between the two kernels (save for the normal little things like minor skew > in clock rates). Pardon my ignorance, but should I be somehow requesting > that my cbb device get bound to IRQ 11 instead of 10? There's no line > containing "cbb" in /boot/device.hints; should I add one? The patch should change the IRQ numbers and also print out a line about how it is trusting your BIOS over the $PIR, so I think you didn't backport the patch correctly or boot the patched kernel somehow. -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: wi0 is always status: no carrier
On Friday 27 May 2005 11:48 pm, Kirk Strauser wrote: > On Friday 27 May 2005 02:48 pm, you wrote: > > The patch should change the IRQ numbers and also print out a line about > > how it is trusting your BIOS over the $PIR, so I think you didn't > > backport the patch correctly or boot the patched kernel somehow. > > Here's what I did: I see. It's because your PIR lists 10 as the only IRQ that it does this. You can override the IRQ with a hint at least using 1.117 of pci_pir.c. Try setting 'hw.pci.link.0x22.irq=11' in the loader to force the IRQ to 11 to see if that works. -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: wi0 is always status: no carrier
On Wednesday 01 June 2005 10:07 am, John Baldwin wrote: > I see. It's because your PIR lists 10 as the only IRQ that it does this. > You can override the IRQ with a hint at least using 1.117 of pci_pir.c. > Try setting 'hw.pci.link.0x22.irq=11' in the loader to force the IRQ to 11 > to see if that works. THAT DID IT! John, Warner, I can't thank you enough for taking the time to help me get my little laptop working. I know you're both busy, and my hardware was *far* from mainstream, yet you both took my cry for help seriously and walked me through the hard parts. Thanks again, -- Kirk Strauser pgpdqSojuEGWD.pgp Description: PGP signature
Re: wi0 is always status: no carrier
In message: <[EMAIL PROTECTED]> Kirk Strauser <[EMAIL PROTECTED]> writes: : On Wednesday 01 June 2005 10:07 am, John Baldwin wrote: : : > I see. It's because your PIR lists 10 as the only IRQ that it does this. : > You can override the IRQ with a hint at least using 1.117 of pci_pir.c. : > Try setting 'hw.pci.link.0x22.irq=11' in the loader to force the IRQ to 11 : > to see if that works. : : THAT DID IT! : : John, Warner, I can't thank you enough for taking the time to help me get my : little laptop working. I know you're both busy, and my hardware was *far* : from mainstream, yet you both took my cry for help seriously and walked me : through the hard parts. We should document this in the pci man page. :-0 Warner ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: wi0 is always status: no carrier
On Wednesday 01 June 2005 11:57 pm, M. Warner Losh wrote: > In message: <[EMAIL PROTECTED]> > > Kirk Strauser <[EMAIL PROTECTED]> writes: > : On Wednesday 01 June 2005 10:07 am, John Baldwin wrote: > : > I see. It's because your PIR lists 10 as the only IRQ that it does > : > this. You can override the IRQ with a hint at least using 1.117 of > : > pci_pir.c. Try setting 'hw.pci.link.0x22.irq=11' in the loader to force > : > the IRQ to 11 to see if that works. > : > : THAT DID IT! > : > : John, Warner, I can't thank you enough for taking the time to help me get > : my little laptop working. I know you're both busy, and my hardware was > : *far* from mainstream, yet you both took my cry for help seriously and > : walked me through the hard parts. > > We should document this in the pci man page. :-0 Well, knowing that it works I might be able to work up a patch to make this edge case work as well. -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
