On Sun, May 19, 2019 at 06:49:25PM +0300, 3 wrote:
> > On Sun, May 19, 2019 at 12:33:33PM +0300, 3 wrote:
> >> shit. i have upgraded to 6.5 and now the interface is losing settings
> >> after about 30 seconds:
> >> athn0: flags=8843 mtu 1500
> >> lladdr b0:48:7a:8c:41:79
> >> index
> On Sun, May 19, 2019 at 12:33:33PM +0300, 3 wrote:
>> shit. i have upgraded to 6.5 and now the interface is losing settings
>> after about 30 seconds:
>> athn0: flags=8843 mtu 1500
>> lladdr b0:48:7a:8c:41:79
>> index 17 priority 4 llprio 3
>> groups: wlan
>> media
On Sun, May 19, 2019 at 12:33:33PM +0300, 3 wrote:
> shit. i have upgraded to 6.5 and now the interface is losing settings
> after about 30 seconds:
> athn0: flags=8843 mtu 1500
> lladdr b0:48:7a:8c:41:79
> index 17 priority 4 llprio 3
> groups: wlan
> media: IEEE802
> This should fix attach but there's some other remaining problem.
> The device detaches itself again when I try to use it.
> diff 709e530bc956c51de2da4aff727d8da450babdc4 /usr/src
> blob - 74025dba1aff37e328c92779398e428caef72c04
> file + sys/dev/ic/ar9287.c
> --- sys/dev/ic/ar9287.c
> +++ sys/de
> This should fix attach but there's some other remaining problem.
> The device detaches itself again when I try to use it.
> diff 709e530bc956c51de2da4aff727d8da450babdc4 /usr/src
> blob - 74025dba1aff37e328c92779398e428caef72c04
> file + sys/dev/ic/ar9287.c
> --- sys/dev/ic/ar9287.c
> +++ sys/de
On Sun, Feb 10, 2019 at 07:12:38PM +0100, Sebastian Reitenbach wrote:
> I get the same bad ROM checksum message with the broken device,
> and indeed, the device that worked before, now gives the same bad ROM checksum
> message when I insert it. It only give a different checksum:
> previously workin
Am Sonntag, Februar 10, 2019 14:19 CET, Stefan Sperling
schrieb:
> On Sun, Feb 10, 2019 at 11:50:35AM +0100, Sebastian Reitenbach wrote:
> > The non-working one shows up as AR7015 in Windows, but I don't see a AR7015
> > chipset
> > mentioned in athn(4), therefore I wanted to verify, if that pa
On Sun, Feb 10, 2019 at 11:50:35AM +0100, Sebastian Reitenbach wrote:
> The non-working one shows up as AR7015 in Windows, but I don't see a AR7015
> chipset
> mentioned in athn(4), therefore I wanted to verify, if that particular
> chipset is actually
> supported by our athn(4) at all?
Indeed,
gt; athn0 at uhub3 port 3 configuration 1 interface 0 "ATHEROS USB WLAN" rev
> > 2.00/2.02 addr 5
> > athn0: failed loadfirmware of file athn-open-ar7010 (error 2)
> > athn0: could not load firmware
> > athn0 at uhub3 port 3 configuration 1 interface 0 "
> athn0: failed loadfirmware of file athn-open-ar7010 (error 2)
> athn0: could not load firmware
> athn0 at uhub3 port 3 configuration 1 interface 0 "ATHEROS USB WLAN" rev
> 2.00/2.02 addr 5
> athn0: bad ROM checksum 0x2c64
> athn0: could not read ROM
> athn0: could
checksum. That is on i386, amd64 and mips64el.
> athn0 at uhub3 port 3 configuration 1 interface 0 "ATHEROS USB WLAN" rev
> 2.00/2.02 addr 5
> athn0: bad ROM checksum 0x2c64
> athn0: could not read ROM
> athn0: could not attach chip
>
> usbdevs -v:
> addr 05: 0c
http://man.openbsd.org/fw_update
OT: Bad subject line, bad email address, at least I see them like this in marc.
ub3 port 3 configuration 1 interface 0 "ATHEROS USB WLAN" rev
2.00/2.02 addr 5
athn0: bad ROM checksum 0x2c64
athn0: could not read ROM
athn0: could not attach chip
usbdevs -v:
addr 05: 0cf3:7015 ATHEROS, USB WLAN
high speed, power 500 mA, config 1, rev 2.02, iSerial 12345
13 matches
Mail list logo
