at
device
4.0 on pci2
ar5212ChipTest: address test failed addr: 0x8000 -
wr:0x != rd:0x
ar5212Attach: hardware self-test failed
ath0: unable to attach hardware; HAL status 14
device_attach: ath0 attach returned 6
I read the registers 4004 and 4010 again to make sure the
values
: hardware self-test failed
ath0: unable to attach hardware; HAL status 14
device_attach: ath0 attach returned 6
I read the registers 4004 and 4010 again to make sure the
values
still are the same, which indeed they are.
I hope this helps.
Thanks!
On Donnerstag, 13. Dezember 2012 at 10:18 PM
ar5212Attach: hardware self-test failed
ath0: unable to attach hardware; HAL status 14
device_attach: ath0 attach returned 6
I read the registers 4004 and 4010 again to make sure the
values
still are the same, which indeed they are.
I hope this helps.
Thanks!
On Donnerstag, 13. Dezember 2012
-
wr:0x != rd:0x
ar5212Attach: hardware self-test failed
ath0: unable to attach hardware; HAL status 14
device_attach: ath0 attach returned 6
I read the registers 4004 and 4010 again to make sure the
values
still are the same, which indeed they are.
I hope this helps.
Thanks
be is:
ath0: Atheros 5413 mem 0xfdee-0xfdee irq 16 at device
4.0 on pci2
ar5212ChipTest: address test failed addr: 0x8000 -
wr:0x != rd:0x
ar5212Attach: hardware self-test failed
ath0: unable to attach hardware; HAL status 14
device_attach: ath0 attach returned 6
I read
on pci2
ar5212ChipTest: address test failed addr: 0x8000 -
wr:0x != rd:0x
ar5212Attach: hardware self-test failed
ath0: unable to attach hardware; HAL status 14
device_attach: ath0 attach returned 6
I read the registers 4004 and 4010 again to make sure the values
still
ar5212ChipTest: address test failed addr: 0x8000 -
wr:0x != rd:0x
ar5212Attach: hardware self-test failed
ath0: unable to attach hardware; HAL status 14
device_attach: ath0 attach returned 6
I read the registers 4004 and 4010 again to make sure the values
still are the same, which
ar5212ChipTest: address test failed addr: 0x8000 - wr:0x !=
rd:0x
ar5212Attach: hardware self-test failed
ath0: unable to attach hardware; HAL status 14
device_attach: ath0 attach returned 6
I read the registers 4004 and 4010 again to make sure the values still are
the same
Hello everyone,
I'm afraid I still don't know what exactly BAR is, or how I get its value that
I'm supposed to plug into the line John provided:
dd if=/dev/mem bs=4 iseek=((start of bar + reg offset)/4) count=1 | hd
I assumed that start of bar is 0xfdee in my case, since dmesg reports
ath0:
On 13 December 2012 13:11, hu...@hush.com wrote:
Hello everyone,
I'm afraid I still don't know what exactly BAR is, or how I get its value
that I'm supposed to plug into the line John provided:
dd if=/dev/mem bs=4 iseek=((start of bar + reg offset)/4) count=1 | hd
I assumed that start of
On Monday, December 10, 2012 5:20:53 pm Adrian Chadd wrote:
Hi,
The fact the initial probe/attach fails by returning 0x means
the chip isn't right on the bus.
It's either just not mapped in correctly, or it's powered off.
If it were just asleep, it'd return 0xdeadc0de or
On 11 December 2012 12:49, John Baldwin j...@freebsd.org wrote:
Look, it's up to you to look at more registers if you want to debug this
further. PCI says everything is ok, so the ball is in your court.
Right, that's why I've asked for those two above registers.
There are other things that
On Friday, December 07, 2012 4:59:37 am hu...@hush.com wrote:
Hello,
thank you for your answer.
Unfortunately, I'm unexperienced with FreeBSD, and am absolutely unfamiliar
with hardware specifics. During this mail conversion, I have heard abour BAR
for the first time, and therefore, I
Hi,
The fact the initial probe/attach fails by returning 0x means
the chip isn't right on the bus.
It's either just not mapped in correctly, or it's powered off.
If it were just asleep, it'd return 0xdeadc0de or 0xdeadbeef or
something similar like that.
Try AR_SCR (0x4004) and
Hello,
thank you for your answer.
Unfortunately, I'm unexperienced with FreeBSD, and am absolutely unfamiliar
with hardware specifics. During this mail conversion, I have heard abour BAR
for the first time, and therefore, I know neither what exactly I should do
(e.g. how I can find the start
On Friday, November 23, 2012 5:56:02 pm Adrian Chadd wrote:
Thanks for this!
I'm sorry it hasn't gotten any more attention. I've cc'ed john because
he understands the PCI-PCI resource allocation stuff and I currently
don't; I'm hoping he can stare at this and see what's going on.
But yes,
failed addr: 0x8000 -
wr:0x != rd:0x
ar5212Attach: hardware self-test failed
ath0: unable to attach hardware; HAL status 14
device_attach: ath0 attach returned 6
and am left unable to use the device.
I tried 8.3-RELEASE i386 as well as 10.0-CURRENT amd64 and
i386
snapshots from
: hardware self-test failed
ath0: unable to attach hardware; HAL status 14
device_attach: ath0 attach returned 6
and am left unable to use the device.
I tried 8.3-RELEASE i386 as well as 10.0-CURRENT amd64 and
i386
snapshots from https://snapshots.glenbarber.us/Latest/
(seemlingly
built a few days
16 at device
4.0 on pci2
ar5212ChipTest: address test failed addr: 0x8000 -
wr:0x != rd:0x
ar5212Attach: hardware self-test failed
ath0: unable to attach hardware; HAL status 14
device_attach: ath0 attach returned 6
and am left unable to use the device.
I tried 8.3-RELEASE
: hardware self-test failed
ath0: unable to attach hardware; HAL status 14
device_attach: ath0 attach returned 6
and am left unable to use the device.
I tried 8.3-RELEASE i386 as well as 10.0-CURRENT amd64 and i386
snapshots from https://snapshots.glenbarber.us/Latest/ (seemlingly
built a few days ago
ath0: unable to attach hardware; HAL status 14
device_attach: ath0 attach returned 6
and am left unable to use the device.
I tried 8.3-RELEASE i386 as well as 10.0-CURRENT amd64 and i386
snapshots from https://snapshots.glenbarber.us/Latest/
(seemlingly
built a few days ago) and received the same
addr: 0x8000 -
wr:0x != rd:0x
ar5212Attach: hardware self-test failed
ath0: unable to attach hardware; HAL status 14
device_attach: ath0 attach returned 6
and am left unable to use the device.
I tried 8.3-RELEASE i386 as well as 10.0-CURRENT amd64 and i386
snapshots from https
-test failed
ath0: unable to attach hardware; HAL status 14
device_attach: ath0 attach returned 6
and am left unable to use the device.
I tried 8.3-RELEASE i386 as well as 10.0-CURRENT amd64 and i386 snapshots from
https://snapshots.glenbarber.us/Latest/ (seemlingly built a few days ago
23 matches
Mail list logo
