Re: Atheros AR9300
On Wed, Nov 15, 2017 at 03:04:15PM -0500, mabi wrote: > Hi, > > I just got myself a new firewall device (Lanner FW-7526) to replace my dying > Soekris box. That new firewall shipped with an Atheros AR9300 wireless chip > and just realized from the dmesg output and athn man page (OpenBSD 6.2) that > this chip must not be supported (yet). > > The dmesg output is the following: > > "Atheros AR9300" rev 0x01 at pci4 dev 0 function 0 not configured > > Is my conclusion here correct? or am I just missing a non-free firmware > (though I ran the fw_update command already). > > Best regards, > Mabi Not yet supported. And athn(4) PCI devices do not require any firmware, a firmware is only needed for athn(4) USB devices. I would suggest to try locating an athn(4) AR9280 or ral(4) RT2700/RT2800 device instead.
Atheros AR9300
Hi, I just got myself a new firewall device (Lanner FW-7526) to replace my dying Soekris box. That new firewall shipped with an Atheros AR9300 wireless chip and just realized from the dmesg output and athn man page (OpenBSD 6.2) that this chip must not be supported (yet). The dmesg output is the following: "Atheros AR9300" rev 0x01 at pci4 dev 0 function 0 not configured Is my conclusion here correct? or am I just missing a non-free firmware (though I ran the fw_update command already). Best regards, Mabi
Re: athn(4) Atheros AR9300 testing request
On Fri, Nov 16, 2012 at 07:21:14PM -0800, Robert Connolly wrote: I have an AR9285. Is that useful? Not for what I want to know. Thanks though! Also, please while you're in there... I get device timeout's constantly, and it disconnects and reconnects to my router. Maybe you can find the cause. That's interesting but it's most likely a separate issue.
athn(4) Atheros AR9300 testing request
Is anyone able to test athn(4) in -current with the following device, and report back to me (off-list is fine) whether or not it is working? Atheros AR9300 Vendor ID: 168c Product ID: 0030 (vendor and produced IDs are shown by 'sudo pcidump -v') I'm trying to get a similar device to work (AR9485), which shares driver code with the AR9300, and would like to know whether problems I'm seeing are specific to that device. Thanks!
Re: athn(4) Atheros AR9300 testing request
I have an AR9285. Is that useful? Also, please while you're in there... I get device timeout's constantly, and it disconnects and reconnects to my router. Maybe you can find the cause. On Fri, Nov 16, 2012 at 4:20 AM, Stefan Sperling s...@openbsd.org wrote: Is anyone able to test athn(4) in -current with the following device, and report back to me (off-list is fine) whether or not it is working? Atheros AR9300 Vendor ID: 168c Product ID: 0030 (vendor and produced IDs are shown by 'sudo pcidump -v') I'm trying to get a similar device to work (AR9485), which shares driver code with the AR9300, and would like to know whether problems I'm seeing are specific to that device. Thanks!
Re: fatal page fault with atheros ar9300
On Sun, Feb 05, 2012 at 09:48:59PM +0100, Tomas Bodzar wrote: On Sun, Feb 5, 2012 at 11:30 AM, Delan Azabani de...@azabani.com wrote: Hi, I'm trying OpenBSD for the first time, and have experienced issues getting the installer to boot on my netbook. My netbook is a Toshiba NB500 (part number PLL50A-00M00D) with an Intel Atom N550 CPU. As it has no CD drive, I used PXE with the following two files: 5.0/amd64/pxeboot 5.0/amd64/bsd.rd When booting the installer, I got a panic. The output visible on my screen at the time of panic is as follows: START OUTPUT acpiprt3 at acpi0: bus 9 (EXP3) acpiprt4 at acpi0: bus -1 (EXP4) acpiprt5 at acpi0: bus 17 (PCIB) pci0 at mainbus0 bus 0 bridge mem address conflict 0xf050/0x10 pchb0 at pci0 dev 0 function 0 Intel Pineview DMI rev 0x02 vga1 at pci0 dev 2 function 0 Intel Pineview Video rev 0x02 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) Intel Pineview Video rev 0x02 at pci0 dev 2 function 1 not configured Intel 82801GB HD Audio rev 0x02 at pci0 dev 27 function 0 not configured ppb0 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x02: msi pci1 at ppb0 bus 5 ppb1 at pci0 dev 28 function 1 Intel 82801GB PCIE rev 0x02: msi pci2 at ppb1 bus 7 athn0 at pci2 dev 0 function 0 Atheros AR9300 rev 0x01: apic 4 int 17 uvm_fault(0x80bc1970, 0x0, 0, 1) - e fatal page fault in supervisor mode trap type 6 code 0 rip 8017dfd5 cs 8 rflags 10286 cr2 ??0 cpl e rsp 80bf5890 panic: trap type 6, code=0, pc=8017dfd5 The operating system has halted. Please press any key to reboot. ??END OUTPUT ?? As the fault occurred right after the line beginning with athn0, I tried booting the installer again, after removing the wireless adapter (it is Mini PCI Express), and the installer booted perfectly. Here is some relevant output from the 'lspci' tool under Linux: START OUTPUT 07:00.0 Network controller [0280]: Atheros Communications Inc. AR9300 Wireless LAN adaptor [168c:0030] (rev 01) ??END OUTPUT ?? I hope that this information is helpful. If you need any more, please let me know and I will be more than happy to help in any way I can. Did you try to boot snapshot already? As with newer HW it's better to try newest system. First of all, I apologise for not making a timely reply. Also, mutt didn't CC the list the first time around, so I had to send this twice. Yes, I have tried the latest snapshot, using the following two files: 1155a52524fde0cf151b63ce9490e1323ff2d0d63fa44594fda6d6ef8d214581 bsd.rd c89c333ce5aa510ce48492c59a542365003945a1c2e6387d4c56777dd71a4ea4 pxeboot from snapshots/amd64/bsd.rd and snapshots/amd64/pxeboot. Unfortunately, I got exactly the same result.
Re: fatal page fault with atheros ar9300
On 2012-02-05, Delan Azabani de...@azabani.com wrote: Hi, I'm trying OpenBSD for the first time, and have experienced issues getting the installer to boot on my netbook. My netbook is a Toshiba NB500 (part number PLL50A-00M00D) with an Intel Atom N550 CPU. As it has no CD drive, I used PXE with the following two files: 5.0/amd64/pxeboot 5.0/amd64/bsd.rd Try booting the normal GENERIC kernel instead (bsd). Unlike the RAMDISK kernel this will include ddb so hopefully you will be able to use 'trace'. Booting a -current kernel is preferable for this. athn0 at pci2 dev 0 function 0 Atheros AR9300 rev 0x01: apic 4 int 17 uvm_fault(0x80bc1970, 0x0, 0, 1) - e fatal page fault in supervisor mode trap type 6 code 0 rip 8017dfd5 cs 8 rflags 10286 cr2 0 cpl e rsp 80bf5890 panic: trap type 6, code=0, pc=8017dfd5
Re: fatal page fault with atheros ar9300
Well, I have made an interesting discovery. I gave the 'bsd' kernel a spin instead of 'bsd.rd', and I got a panic. However, the panic was for not finding a rootfs: panic: root device (230c0009f2e600f0) not found Stopped at Debugger+0x5: leave RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS BUG! DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THIS INFORMATION! This is a good sign, I assume, as the 'bsd' kernel isn't meant to be run by itself, am I correct? I scrolled back in the dmesg a few screens, and found this: athn0 at pci2 dev 0 function 0 Atheros AR9300 rev 0x01: apic 4 int 17 athn0: AR9300 rev 3 (2T2R), REM rev 0, address 1c:65:9d:de:de:56 So the wireless adapter is detected and working on this kernel, but not on 'bsd.rd'. Any ideas?
Re: fatal page fault with atheros ar9300
I have more information, hopefully useful, about this problem. To recap,
the installer bsd.rd fails to boot unless I 'disable athn' in UKC. The
installer bsd boots, but of course panics because there is no rootfs. I
managed to install OpenBSD using bsd.rd (with athn disabled), but upon booting
into OpenBSD, I get a fault with a nice trace:
BEGIN
athn0 at pci2 dev 0 function 0 Atheros AR9300 rev 0x01: apic 4 int 17
uvm_fault(0x80d2a0a0, 0x0, 0, 1) - e
kernel: page fault trap, code=0
Stopped at athn_write_serdes+0x15: movl0(%r13,%rbx,4),%edx
athn_write_serdes() at athn_write_serdes+0x15
athn_config_pcie() at athn_config_pcie+0x16
ar9003_attach() at ar9003_attach+0x199
athn_attach() at athn_attach+0x586
athn_pci_attach() at athn_pci_attach+0x1de
config_attach() at config_attach+0x1d4
pci_probe_device() at pci_probe_device+0x462
pci_enumerate_bus() at pci_enumerate_bus+0xe9
config_attach() at config_attach+0x1d4
ppbattach() at ppbattach+0x32f
end trace frame: 0x80e30bf0, count: 0
ddb{0}
END
Like the installer bsd.rd, the installed OpenBSD can boot by disabling athn
in UKC. Running 'ps' in ddb shows only 'swapper' running, nothing else.
Hopefully someone will be able to gather something from this trace.
Re: fatal page fault with atheros ar9300
On Sat, Feb 11, 2012 at 12:41 PM, Delan Azabani de...@azabani.com wrote:
I have more information, hopefully useful, about this problem. To recap,
the installer bsd.rd fails to boot unless I 'disable athn' in UKC. The
installer bsd boots, but of course panics because there is no rootfs. I
managed to install OpenBSD using bsd.rd (with athn disabled), but upon
booting
into OpenBSD, I get a fault with a nice trace:
BEGIN
athn0 at pci2 dev 0 function 0 Atheros AR9300 rev 0x01: apic 4 int 17
uvm_fault(0x80d2a0a0, 0x0, 0, 1) - e
kernel: page fault trap, code=0
Stopped at B B B athn_write_serdes+0x15: movl B B 0(%r13,%rbx,4),%edx
athn_write_serdes() at athn_write_serdes+0x15
athn_config_pcie() at athn_config_pcie+0x16
ar9003_attach() at ar9003_attach+0x199
athn_attach() at athn_attach+0x586
athn_pci_attach() at athn_pci_attach+0x1de
config_attach() at config_attach+0x1d4
pci_probe_device() at pci_probe_device+0x462
pci_enumerate_bus() at pci_enumerate_bus+0xe9
config_attach() at config_attach+0x1d4
ppbattach() at ppbattach+0x32f
end trace frame: 0x80e30bf0, count: 0
ddb{0}
B END B
Like the installer bsd.rd, the installed OpenBSD can boot by disabling athn
in UKC. Running 'ps' in ddb shows only 'swapper' running, nothing else.
Hopefully someone will be able to gather something from this trace.
Maybe you can try it as well http://www.openbsd.org/faq/faq2.html#Bugs
So install of snapshot and use of system is possible when athn
disabled in UKC, right? Did you try both i386 and amd64? Do you have
latest BIOS in your system or are there some repairs available and
related to your wifi device?
Re: fatal page fault with atheros ar9300
On Sat, Feb 11, 2012 at 01:58:52PM +0100, Tomas Bodzar wrote:
On Sat, Feb 11, 2012 at 12:41 PM, Delan Azabani de...@azabani.com wrote:
I have more information, hopefully useful, about this problem. To recap,
the installer bsd.rd fails to boot unless I 'disable athn' in UKC. The
installer bsd boots, but of course panics because there is no rootfs. I
managed to install OpenBSD using bsd.rd (with athn disabled), but upon
booting
into OpenBSD, I get a fault with a nice trace:
BEGIN
athn0 at pci2 dev 0 function 0 Atheros AR9300 rev 0x01: apic 4 int 17
uvm_fault(0x80d2a0a0, 0x0, 0, 1) - e
kernel: page fault trap, code=0
Stopped at ?? ?? ??athn_write_serdes+0x15: movl ?? ??0(%r13,%rbx,4),%edx
athn_write_serdes() at athn_write_serdes+0x15
athn_config_pcie() at athn_config_pcie+0x16
ar9003_attach() at ar9003_attach+0x199
athn_attach() at athn_attach+0x586
athn_pci_attach() at athn_pci_attach+0x1de
config_attach() at config_attach+0x1d4
pci_probe_device() at pci_probe_device+0x462
pci_enumerate_bus() at pci_enumerate_bus+0xe9
config_attach() at config_attach+0x1d4
ppbattach() at ppbattach+0x32f
end trace frame: 0x80e30bf0, count: 0
ddb{0}
??END ??
Like the installer bsd.rd, the installed OpenBSD can boot by disabling athn
in UKC. Running 'ps' in ddb shows only 'swapper' running, nothing else.
Hopefully someone will be able to gather something from this trace.
Maybe you can try it as well http://www.openbsd.org/faq/faq2.html#Bugs
So install of snapshot and use of system is possible when athn
disabled in UKC, right? Did you try both i386 and amd64? Do you have
latest BIOS in your system or are there some repairs available and
related to your wifi device?
I have just tried i386, and all the same symptoms occur. My BIOS is up to date
according to Toshiba's website. Stefan Sperling sent me a possible patch. I
pulled the amd64 kernel sources, patched athn.c, recompiled, and now OpenBSD
boots perfectly without disabling athn. 'ifconfig' shows athn0 too, now.
On Sat, Feb 11, 2012 at 01:37:00PM +0100, Stefan Sperling wrote:
This might prevent the crash. I have no idea if it will give you
a working device though. This part of the PCIe config process only
seems to affect power management but I have no idea what it really does.
Index: athn.c
===
RCS file: /cvs/src/sys/dev/ic/athn.c,v
retrieving revision 1.71
diff -u -p -r1.71 athn.c
--- athn.c8 Jan 2011 15:05:24 - 1.71
+++ athn.c11 Feb 2012 12:30:54 -
@@ -789,7 +789,8 @@ void
athn_config_pcie(struct athn_softc *sc)
{
/* Disable PLL when in L0s as well as receiver clock when in L1. */
- athn_write_serdes(sc, sc-serdes);
+ if (sc-serdes)
+ athn_write_serdes(sc, sc-serdes);
DELAY(1000);
/* Allow forcing of PCIe core into L1 state. */
fatal page fault with atheros ar9300
Hi, I'm trying OpenBSD for the first time, and have experienced issues getting the installer to boot on my netbook. My netbook is a Toshiba NB500 (part number PLL50A-00M00D) with an Intel Atom N550 CPU. As it has no CD drive, I used PXE with the following two files: 5.0/amd64/pxeboot 5.0/amd64/bsd.rd When booting the installer, I got a panic. The output visible on my screen at the time of panic is as follows: START OUTPUT acpiprt3 at acpi0: bus 9 (EXP3) acpiprt4 at acpi0: bus -1 (EXP4) acpiprt5 at acpi0: bus 17 (PCIB) pci0 at mainbus0 bus 0 bridge mem address conflict 0xf050/0x10 pchb0 at pci0 dev 0 function 0 Intel Pineview DMI rev 0x02 vga1 at pci0 dev 2 function 0 Intel Pineview Video rev 0x02 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) Intel Pineview Video rev 0x02 at pci0 dev 2 function 1 not configured Intel 82801GB HD Audio rev 0x02 at pci0 dev 27 function 0 not configured ppb0 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x02: msi pci1 at ppb0 bus 5 ppb1 at pci0 dev 28 function 1 Intel 82801GB PCIE rev 0x02: msi pci2 at ppb1 bus 7 athn0 at pci2 dev 0 function 0 Atheros AR9300 rev 0x01: apic 4 int 17 uvm_fault(0x80bc1970, 0x0, 0, 1) - e fatal page fault in supervisor mode trap type 6 code 0 rip 8017dfd5 cs 8 rflags 10286 cr2 0 cpl e rsp 80bf5890 panic: trap type 6, code=0, pc=8017dfd5 The operating system has halted. Please press any key to reboot. END OUTPUT As the fault occurred right after the line beginning with athn0, I tried booting the installer again, after removing the wireless adapter (it is Mini PCI Express), and the installer booted perfectly. Here is some relevant output from the 'lspci' tool under Linux: START OUTPUT 07:00.0 Network controller [0280]: Atheros Communications Inc. AR9300 Wireless LAN adaptor [168c:0030] (rev 01) END OUTPUT I hope that this information is helpful. If you need any more, please let me know and I will be more than happy to help in any way I can.
Re: fatal page fault with atheros ar9300
On Sun, Feb 5, 2012 at 11:30 AM, Delan Azabani de...@azabani.com wrote: Hi, I'm trying OpenBSD for the first time, and have experienced issues getting the installer to boot on my netbook. My netbook is a Toshiba NB500 (part number PLL50A-00M00D) with an Intel Atom N550 CPU. As it has no CD drive, I used PXE with the following two files: 5.0/amd64/pxeboot 5.0/amd64/bsd.rd When booting the installer, I got a panic. The output visible on my screen at the time of panic is as follows: START OUTPUT acpiprt3 at acpi0: bus 9 (EXP3) acpiprt4 at acpi0: bus -1 (EXP4) acpiprt5 at acpi0: bus 17 (PCIB) pci0 at mainbus0 bus 0 bridge mem address conflict 0xf050/0x10 pchb0 at pci0 dev 0 function 0 Intel Pineview DMI rev 0x02 vga1 at pci0 dev 2 function 0 Intel Pineview Video rev 0x02 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) Intel Pineview Video rev 0x02 at pci0 dev 2 function 1 not configured Intel 82801GB HD Audio rev 0x02 at pci0 dev 27 function 0 not configured ppb0 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x02: msi pci1 at ppb0 bus 5 ppb1 at pci0 dev 28 function 1 Intel 82801GB PCIE rev 0x02: msi pci2 at ppb1 bus 7 athn0 at pci2 dev 0 function 0 Atheros AR9300 rev 0x01: apic 4 int 17 uvm_fault(0x80bc1970, 0x0, 0, 1) - e fatal page fault in supervisor mode trap type 6 code 0 rip 8017dfd5 cs 8 rflags 10286 cr2 B 0 cpl e rsp 80bf5890 panic: trap type 6, code=0, pc=8017dfd5 The operating system has halted. Please press any key to reboot. B END OUTPUT B As the fault occurred right after the line beginning with athn0, I tried booting the installer again, after removing the wireless adapter (it is Mini PCI Express), and the installer booted perfectly. Here is some relevant output from the 'lspci' tool under Linux: START OUTPUT 07:00.0 Network controller [0280]: Atheros Communications Inc. AR9300 Wireless LAN adaptor [168c:0030] (rev 01) B END OUTPUT B I hope that this information is helpful. If you need any more, please let me know and I will be more than happy to help in any way I can. Did you try to boot snapshot already? As with newer HW it's better to try newest system.
