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 pa
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
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
> ca
rent 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
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
e
> > 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
> > athn
gt; 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, 0x
on 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
ace' 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, a
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.
>
ci0 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 fu
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(0x80bc19
igured
"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 de
13 matches
Mail list logo
