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
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
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
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.
:
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
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
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
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:
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:
: :
: :
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-
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
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: PCI Interrupt Routing Table: 4 Entries 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
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: PCI Interrupt Routing Table: 4 Entries on motherboard
:
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
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
15 matches
Mail list logo