Re: acx(4) fails to assossiate on OpenBSD 4.2
Didn't try. Anyway, I switched the cards between the OpenBSD box in question and avaliable WinXP box, now everything works like charm.
Re: acx(4) fails to assossiate on OpenBSD 4.2
On Mon, Dec 17, 2007 at 11:01:14PM +0100, Claudio Jeker wrote: > On Tue, Dec 18, 2007 at 12:33:57AM +0300, Dmitrij Czarkoff wrote: > > 2007/12/17, df <[EMAIL PROTECTED]>: > > > Noticed that acx0 had an MSDU (MAC Service Data Unit) life timeout > > >- I know you said you loaded the firmware...was it the latest? 13 Oct > > > 07 > > > acx-firmware-1.4.tgz > > > > Yes, I used 1.4. > > > > >- What are the specifics of your connection string to the AP (Access > > > Point)? > > > I.E., how did you use ifconfig, and is the AP utilizing encryption? > > > > I run 'ifconfig acx0 nwid my_nwid && dhclient acx0". Or just the same > > two commands with timeout. Nothing happens. > > > > My acx111 spews out quite a few watchdog timeouts but works very well. > > acx0 at pci0 dev 14 function 0 "TI ACX111" rev 0x00: irq 11 > acx0: ACX111, radio Radia (0x16), EEPROM ver 5, address 00:a0:c5:92:92:a1 > > So it could be that you have a flaky card. Maybe I get annoyed enough to > fix the watchdog timeouts somewhen during the holydays... > I have a couple of boxen that spew errors as well... These same boxen require the following to associate with an AP #ifconfig acx0 inet 192.168.1.10 netmask 255.255.255.0 nwid my-ap \ nwkey 0x26characters #dhcient acx0 I have this in a script...don't know why I have to give it a static address first (obviously something I have messed up), but it works ;o) Regards, Doug
Re: acx(4) fails to assossiate on OpenBSD 4.2
On Tue, Dec 18, 2007 at 12:33:57AM +0300, Dmitrij Czarkoff wrote: > 2007/12/17, df <[EMAIL PROTECTED]>: > > Noticed that acx0 had an MSDU (MAC Service Data Unit) life timeout > >- I know you said you loaded the firmware...was it the latest? 13 Oct 07 > > acx-firmware-1.4.tgz > > Yes, I used 1.4. > > >- What are the specifics of your connection string to the AP (Access > > Point)? > > I.E., how did you use ifconfig, and is the AP utilizing encryption? > > I run 'ifconfig acx0 nwid my_nwid && dhclient acx0". Or just the same > two commands with timeout. Nothing happens. > My acx111 spews out quite a few watchdog timeouts but works very well. acx0 at pci0 dev 14 function 0 "TI ACX111" rev 0x00: irq 11 acx0: ACX111, radio Radia (0x16), EEPROM ver 5, address 00:a0:c5:92:92:a1 So it could be that you have a flaky card. Maybe I get annoyed enough to fix the watchdog timeouts somewhen during the holydays... -- :wq Claudio
Re: acx(4) fails to assossiate on OpenBSD 4.2
2007/12/17, df <[EMAIL PROTECTED]>: > Noticed that acx0 had an MSDU (MAC Service Data Unit) life timeout >- I know you said you loaded the firmware...was it the latest? 13 Oct 07 > acx-firmware-1.4.tgz Yes, I used 1.4. >- What are the specifics of your connection string to the AP (Access > Point)? > I.E., how did you use ifconfig, and is the AP utilizing encryption? I run 'ifconfig acx0 nwid my_nwid && dhclient acx0". Or just the same two commands with timeout. Nothing happens. 2007/12/17, Alexey Suslikov <[EMAIL PROTECTED]>: > Other choices to try: > > - use -current with 1.4 firmware (recommended), > - disable apm, disable pcibios, enable acpi, > - disable ehci (or skc, or both), > - use bsd.mp. I used 1.4 firmware, tried with apm disabled and acpi enabled with no result and bsd.mp kernel fails to boot on my hardware. I believe the very problem with a card is the hardware problem - will be trying to check it tomorrow in WinXP box. -- Dmitrij D. Czarkoff
Re: acx(4) fails to assossiate on OpenBSD 4.2
df wrote: > Sorry for top posting...and the intrusion... > Just wondering if you solved this problem? > > Noticed that acx0 had an MSDU (MAC Service Data Unit) life timeout > - I know you said you loaded the firmware...was it the latest? 13 Oct 07 > acx-firmware-1.4.tgz > - What are the specifics of your connection string to the AP (Access Point)? > I.E., how did you use ifconfig, and is the AP utilizing encryption? He is running 4.2 so firmware should be 1.3 (1.4 is for -current). Other choices to try: - use -current with 1.4 firmware (recommended), - disable apm, disable pcibios, enable acpi, - disable ehci (or skc, or both), - use bsd.mp. - Alexey.
Re: acx(4) fails to assossiate on OpenBSD 4.2
Sorry for top posting...and the intrusion...
Just wondering if you solved this problem?
Noticed that acx0 had an MSDU (MAC Service Data Unit) life timeout
- I know you said you loaded the firmware...was it the latest? 13 Oct 07
acx-firmware-1.4.tgz
- What are the specifics of your connection string to the AP (Access Point)?
I.E., how did you use ifconfig, and is the AP utilizing encryption?
On Mon, Dec 17, 2007 at 01:09:13AM +0300, Dmitrij Czarkoff wrote:
> OpenBSD 4.2 (RAMDISK_CD) #468: Tue Aug 28 11:02:17 MDT 2007
> [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/RAMDISK_CD
> cpu0: Intel(R) Pentium(R) 4 CPU 3.00GHz ("GenuineIntel" 686-class) 3 GHz
> cpu0:
> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,CNXT-ID,xTPR
> real mem = 1072984064 (1023MB)
> avail mem = 1031516160 (983MB)
> mainbus0 at root
> bios0 at mainbus0: AT/286+ BIOS, date 09/01/04, BIOS32 rev. 0 @
> 0xf0010, SMBIOS rev. 2.3 @ 0xf04a0 (66 entries)
> bios0: vendor American Megatrends Inc. version "080009 " date 09/01/2004
> bios0: ASUSTeK Computer Inc. P4P800SE
> apm0 at bios0: Power Management spec V1.2
> apm0: flags 30102 dobusy 0 doidle 1
> pcibios0 at bios0: rev 2.1 @ 0xf/0x1
> pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf5fe0/256 (14 entries)
> pcibios0: PCI Interrupt Router at 000:31:0 ("Intel 82801EB/ER LPC" rev 0x00)
> pcibios0: PCI bus #2 is the last bus
> bios0: ROM list: 0xc/0xd000
> cpu0 at mainbus0
> pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
> pchb0 at pci0 dev 0 function 0 "Intel 82865G/PE/P CPU-I/0-1" rev 0x02
> ppb0 at pci0 dev 1 function 0 "Intel 82865G/PE/P CPU-AGP" rev 0x02
> pci1 at ppb0 bus 1
> vga1 at pci1 dev 0 function 0 "ATI Radeon 9600 Pro" rev 0x00
> wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
> "ATI Radeon 9600 Pro Sec" rev 0x00 at pci1 dev 0 function 1 not configured
> uhci0 at pci0 dev 29 function 0 "Intel 82801EB/ER USB" rev 0x02: irq 10
> uhci1 at pci0 dev 29 function 1 "Intel 82801EB/ER USB" rev 0x02: irq 11
> uhci2 at pci0 dev 29 function 2 "Intel 82801EB/ER USB" rev 0x02: irq 5
> uhci3 at pci0 dev 29 function 3 "Intel 82801EB/ER USB" rev 0x02: irq 10
> ehci0 at pci0 dev 29 function 7 "Intel 82801EB/ER USB2" rev 0x02: irq 11
> usb0 at ehci0: USB revision 2.0
> uhub0 at usb0: Intel EHCI root hub, rev 2.00/1.00, addr 1
> ppb1 at pci0 dev 30 function 0 "Intel 82801BA AGP" rev 0xc2
> pci2 at ppb1 bus 2
> skc0 at pci2 dev 5 function 0 "Marvell Yukon 88E8001/8003/8010" rev
> 0x13, Yukon Lite rev. A3 (0x7): irq 11
> sk0 at skc0 port A: address 00:11:2f:9e:7c:3a
> eephy0 at sk0 phy 0: Marvell 88E1011 Gigabit PHY, rev. 5
> "TI ACX111" rev 0x00 at pci2 dev 9 function 0 not configured
> ichpcib0 at pci0 dev 31 function 0 "Intel 82801EB/ER LPC" rev 0x02:
> 24-bit timer at 3579545Hz
> pciide0 at pci0 dev 31 function 1 "Intel 82801EB/ER IDE" rev 0x02:
> DMA, channel 0 configured to compatibility, channel 1 configured to
> compatibility
> atapiscsi0 at pciide0 channel 0 drive 0
> scsibus0 at atapiscsi0: 2 targets
> cd0 at scsibus0 targ 0 lun 0: <_NEC, DVD_RW ND-3500AG, 2.16> SCSI0
> 5/cdrom removable
> cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
> pciide0: channel 1 disabled (no drives)
> pciide1 at pci0 dev 31 function 2 "Intel 82801EB SATA" rev 0x02: DMA,
> channel 0 configured to native-PCI, channel 1 configured to native-PCI
> pciide1: using irq 5 for native-PCI interrupt
> wd0 at pciide1 channel 0 drive 0:
> wd0: 16-sector PIO, LBA48, 152627MB, 312581808 sectors
> wd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 5
> "Intel 82801EB/ER SMBus" rev 0x02 at pci0 dev 31 function 3 not configured
> "Intel 82801EB/ER AC97" rev 0x02 at pci0 dev 31 function 5 not configured
> usb1 at uhci0: USB revision 1.0
> uhub1 at usb1: Intel UHCI root hub, rev 1.00/1.00, addr 1
> usb2 at uhci1: USB revision 1.0
> uhub2 at usb2: Intel UHCI root hub, rev 1.00/1.00, addr 1
> usb3 at uhci2: USB revision 1.0
> uhub3 at usb3: Intel UHCI root hub, rev 1.00/1.00, addr 1
> usb4 at uhci3: USB revision 1.0
> uhub4 at usb4: Intel UHCI root hub, rev 1.00/1.00, addr 1
> isa0 at ichpcib0
> isadma0 at isa0
> pckbc0 at isa0 port 0x60/5
> pckbd0 at pckbc0 (kbd slot)
> pckbc0: using irq 1 for kbd slot
> wskbd0 at pckbd0: console keyboard, using wsdisplay0
> npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
> pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
> pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
> fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
> fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
> biomask ffe5 netmask ffe5 ttymask ffe7
> rd0: fixed, 3800 blocks
> dkcsum: wd0 matches BIOS drive 0x80
> root on rd0a swap on rd0b dump on rd0b
> OpenBSD 4.2 (GENERIC) #375: Tue Aug 28 10:38:44 MDT 2007
> [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
> cpu0: Intel(R) Pentium(R) 4 CPU 3.00GHz ("GenuineIntel" 686-class) 3 GHz
> cpu0:
> FPU,V86,DE,PSE,TSC,MSR,P
Re: acx(4) fails to assossiate on OpenBSD 4.2
OpenBSD 4.2 (RAMDISK_CD) #468: Tue Aug 28 11:02:17 MDT 2007
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/RAMDISK_CD
cpu0: Intel(R) Pentium(R) 4 CPU 3.00GHz ("GenuineIntel" 686-class) 3 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,CNXT-ID,xTPR
real mem = 1072984064 (1023MB)
avail mem = 1031516160 (983MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 09/01/04, BIOS32 rev. 0 @
0xf0010, SMBIOS rev. 2.3 @ 0xf04a0 (66 entries)
bios0: vendor American Megatrends Inc. version "080009 " date 09/01/2004
bios0: ASUSTeK Computer Inc. P4P800SE
apm0 at bios0: Power Management spec V1.2
apm0: flags 30102 dobusy 0 doidle 1
pcibios0 at bios0: rev 2.1 @ 0xf/0x1
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf5fe0/256 (14 entries)
pcibios0: PCI Interrupt Router at 000:31:0 ("Intel 82801EB/ER LPC" rev 0x00)
pcibios0: PCI bus #2 is the last bus
bios0: ROM list: 0xc/0xd000
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 82865G/PE/P CPU-I/0-1" rev 0x02
ppb0 at pci0 dev 1 function 0 "Intel 82865G/PE/P CPU-AGP" rev 0x02
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "ATI Radeon 9600 Pro" rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
"ATI Radeon 9600 Pro Sec" rev 0x00 at pci1 dev 0 function 1 not configured
uhci0 at pci0 dev 29 function 0 "Intel 82801EB/ER USB" rev 0x02: irq 10
uhci1 at pci0 dev 29 function 1 "Intel 82801EB/ER USB" rev 0x02: irq 11
uhci2 at pci0 dev 29 function 2 "Intel 82801EB/ER USB" rev 0x02: irq 5
uhci3 at pci0 dev 29 function 3 "Intel 82801EB/ER USB" rev 0x02: irq 10
ehci0 at pci0 dev 29 function 7 "Intel 82801EB/ER USB2" rev 0x02: irq 11
usb0 at ehci0: USB revision 2.0
uhub0 at usb0: Intel EHCI root hub, rev 2.00/1.00, addr 1
ppb1 at pci0 dev 30 function 0 "Intel 82801BA AGP" rev 0xc2
pci2 at ppb1 bus 2
skc0 at pci2 dev 5 function 0 "Marvell Yukon 88E8001/8003/8010" rev
0x13, Yukon Lite rev. A3 (0x7): irq 11
sk0 at skc0 port A: address 00:11:2f:9e:7c:3a
eephy0 at sk0 phy 0: Marvell 88E1011 Gigabit PHY, rev. 5
"TI ACX111" rev 0x00 at pci2 dev 9 function 0 not configured
ichpcib0 at pci0 dev 31 function 0 "Intel 82801EB/ER LPC" rev 0x02:
24-bit timer at 3579545Hz
pciide0 at pci0 dev 31 function 1 "Intel 82801EB/ER IDE" rev 0x02:
DMA, channel 0 configured to compatibility, channel 1 configured to
compatibility
atapiscsi0 at pciide0 channel 0 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: <_NEC, DVD_RW ND-3500AG, 2.16> SCSI0
5/cdrom removable
cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
pciide0: channel 1 disabled (no drives)
pciide1 at pci0 dev 31 function 2 "Intel 82801EB SATA" rev 0x02: DMA,
channel 0 configured to native-PCI, channel 1 configured to native-PCI
pciide1: using irq 5 for native-PCI interrupt
wd0 at pciide1 channel 0 drive 0:
wd0: 16-sector PIO, LBA48, 152627MB, 312581808 sectors
wd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 5
"Intel 82801EB/ER SMBus" rev 0x02 at pci0 dev 31 function 3 not configured
"Intel 82801EB/ER AC97" rev 0x02 at pci0 dev 31 function 5 not configured
usb1 at uhci0: USB revision 1.0
uhub1 at usb1: Intel UHCI root hub, rev 1.00/1.00, addr 1
usb2 at uhci1: USB revision 1.0
uhub2 at usb2: Intel UHCI root hub, rev 1.00/1.00, addr 1
usb3 at uhci2: USB revision 1.0
uhub3 at usb3: Intel UHCI root hub, rev 1.00/1.00, addr 1
usb4 at uhci3: USB revision 1.0
uhub4 at usb4: Intel UHCI root hub, rev 1.00/1.00, addr 1
isa0 at ichpcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
biomask ffe5 netmask ffe5 ttymask ffe7
rd0: fixed, 3800 blocks
dkcsum: wd0 matches BIOS drive 0x80
root on rd0a swap on rd0b dump on rd0b
OpenBSD 4.2 (GENERIC) #375: Tue Aug 28 10:38:44 MDT 2007
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Pentium(R) 4 CPU 3.00GHz ("GenuineIntel" 686-class) 3 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,CNXT-ID,xTPR
real mem = 1072984064 (1023MB)
avail mem = 1029885952 (982MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 09/01/04, BIOS32 rev. 0 @
0xf0010, SMBIOS rev. 2.3 @ 0xf04a0 (66 entries)
bios0: vendor American Megatrends Inc. version "080009 " date 09/01/2004
bios0: ASUSTeK Computer Inc. P4P800SE
apm0 at bios0: Power Management spec V1.2
apm0: AC on, battery charge unknown
apm0: flags 30102 dobusy 0 doidle 1
pcibios0 at bios0: rev 2.1 @ 0xf/0x1
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf5fe0/256 (
Re: acx(4) fails to assossiate on OpenBSD 4.2
misc@ doesn't allow attachments, pasting it in the message body will be fine. On 2007/12/16 22:32, Dmitrij Czarkoff wrote: > 2007/12/15, Stuart Henderson <[EMAIL PROTECTED]>: > > Nobody can tell from the information you included - send the dmesg... > > # cat dmesg | grep acx > acx0 at pci2 dev 9 function 0 "TI ACX111" rev 0x00: irq 11 > acx0: ACX111, radio Radia (0x16), EEPROM ver 5, address 00:0f:3d:58:67:a1 > acx0: watchdog timeout > acx0: watchdog timeout > acx0: watchdog timeout > acx0: watchdog timeout > acx0: watchdog timeout > acx0: watchdog timeout > acx0: watchdog timeout > acx0: watchdog timeout > acx0: watchdog timeout > acx0: watchdog timeout > acx0: watchdog timeout > acx0: watchdog timeout > acx0: TX failed -- MSDU life timeout > acx0: watchdog timeout > acx0: watchdog timeout > acx0: watchdog timeout > acx0: watchdog timeout > > See full dmesg attached. [..] > [demime 1.01d removed an attachment of type application/x-gzip which had a > name of dmesg.gz]
Re: acx(4) fails to assossiate on OpenBSD 4.2
2007/12/15, Stuart Henderson <[EMAIL PROTECTED]>: > Nobody can tell from the information you included - send the dmesg... # cat dmesg | grep acx acx0 at pci2 dev 9 function 0 "TI ACX111" rev 0x00: irq 11 acx0: ACX111, radio Radia (0x16), EEPROM ver 5, address 00:0f:3d:58:67:a1 acx0: watchdog timeout acx0: watchdog timeout acx0: watchdog timeout acx0: watchdog timeout acx0: watchdog timeout acx0: watchdog timeout acx0: watchdog timeout acx0: watchdog timeout acx0: watchdog timeout acx0: watchdog timeout acx0: watchdog timeout acx0: watchdog timeout acx0: TX failed -- MSDU life timeout acx0: watchdog timeout acx0: watchdog timeout acx0: watchdog timeout acx0: watchdog timeout See full dmesg attached. 2007/12/16, df <[EMAIL PROTECTED]>: > You did download and install the firmware mentioned in the acx manpage..right? Yes, I've installed a firmware package mensioned in manual. -- Dmitrij D. Czarkoff [demime 1.01d removed an attachment of type application/x-gzip which had a name of dmesg.gz]
Re: acx(4) fails to assossiate on OpenBSD 4.2
On Sat, Dec 15, 2007 at 08:33:11PM +0300, Dmitrij Czarkoff wrote: > I've got a D-Link DWL-G520+ wireless acx111-based PCI card. It is > listed as supported device on acx(4) man page. When I boot up my i386 > box, I get it picked up by acx driver, but when I try to run dhclient > on acx0, I get no DHCPOFFERs, but only "acx0: watchdog timeout" errors > comming up about every 5 seconds. No more messages in dmesg since boot > time. > > After setting hostname.acx0, I get the same messages with same result > in boot time. > > Can anything be done about it? > You did download and install the firmware mentioned in the acx manpage..right?
Re: acx(4) fails to assossiate on OpenBSD 4.2
On 2007/12/15 20:33, Dmitrij Czarkoff wrote: > I've got a D-Link DWL-G520+ wireless acx111-based PCI card. It is > listed as supported device on acx(4) man page. When I boot up my i386 > box, I get it picked up by acx driver, but when I try to run dhclient > on acx0, I get no DHCPOFFERs, but only "acx0: watchdog timeout" errors > comming up about every 5 seconds. No more messages in dmesg since boot > time. > > After setting hostname.acx0, I get the same messages with same result > in boot time. > > Can anything be done about it? Nobody can tell from the information you included - send the dmesg... I had nothing but good experience with the acx111 minipci I extracted from some commercial access-point and put into a Soekris running OpenBSD.
