Running 4.8 patch/stable with all updated, apm disable via config, upgraded from
4.7 patch/stable.

Any time ral0 is initialized (in hostap mode) using, say, sh /etc/netstart, the
following message is shown on the console:
ral0: timeout waiting for BBP

The code shows that when this happens, the device initialization is aborted and
EIO error is returned, making 4.8 patch/stable useless for running the box as a
wireless access point using ral.

This may ordinarily point to hardware failing except for two things:
1. checking the code shows that the busy bit is actually cleared because no
"cannot read from BBP" message is seen, only a 0 is returned from the version
flash read. My guess is that some firmware is being loaded wrong onto the
hardware in 4.8?
...and
2. ral0 initializes just fine without the timeout using either my previous 4.7
kernel, or the -current kernel which I am running now.

The relevant parts of dmesg (relevant imho; if there is more that is needed,
please advise) are:
ral0 at pci0 dev 14 function 0 "Ralink RT2561S" rev 0x00: irq 3, address 00:24:1
d:39:f6:84
ral0: MAC/BBP RT2561C, RF RT2527

Also, pcidump -v shows for this device:
 0:14:0: Ralink RT2561S
        0x0000: Vendor ID: 1814 Product ID: 0301
        0x0004: Command: 0017 Status ID: 0410
        0x0008: Class: 02 Subclass: 80 Interface: 00 Revision: 00
        0x000c: BIST: 00 Header Type: 00 Latency Timer: 20 Cache Line Size: 08
        0x0010: BAR mem 32bit addr: 0xe3800000
        0x0014: BAR empty (00000000)
        0x0018: BAR empty (00000000)
        0x001c: BAR empty (00000000)
        0x0020: BAR empty (00000000)
        0x0024: BAR empty (00000000)
        0x0028: Cardbus CIS: 00000601
        0x002c: Subsystem Vendor ID: 1458 Product ID: e934
        0x0030: Expansion ROM Base Address: 00000000
        0x0038: 00000000
        0x003c: Interrupt Pin: 01 Line: 03 Min Gnt: 00 Max Lat: 00
        0x0040: Capability 0x01: Power Management

I don't know what to do next here. I am ...
[ message continues ]

Hi Stephen (and anyone else),
I'm experiencing your same problem. I was looking for a solution on the
web but I'd say unsuccessfully. I couldn't found any reply to his
complaint (that is in fact the only one I've found around) and I was
wondering if you received a solution or a tip in private.

Sorry for this late email, I usually don't like to disturb others and it
usually works (I found the solution on internet). But in this case I
didn't find anything at all! And this quite impressed me. I was thinking
that ral as AP was widely used too.

Thanks in advance, any tip/direction is more than welcome.



 
 
 --
 Caselle da 1GB, trasmetti allegati fino a 3GB e in piu' IMAP, POP3 e SMTP autenticato? GRATIS solo con Email.it http://www.email.it/f
 
 Sponsor:
 Idee Regalo Personalizzate a partire da euro 3.90! Su MisterCupido.com alta qualit` a prezzi imbattibili... e questa settimana GRATIS per te, la confezione regalo!
 Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=11027&d=12-12

[ message continues ]

Out of curiosity, could you post your hostname.xxx configuration
files? (minus the sensitive parts of course, like wpa-psk info etc.)


alta qualit` a prezzi imbattibili... e questa settimana GRATIS per te, la

[ message continues ]

Hi there,
because of my needs I'm using a small script to start the AP that by the way includes the following command line:
ifconfig ral0 inet $AP_IPADDR netmask $AP_SUBMASK media autoselect mediaopt hostap mode $MODE chan $CHAN bssid $MAC_MASK nwid $NWID -powersave wpa wpaakms psk wpaciphers ccmp wpagroupcipher ccmp wpaprotos wpa2 wpapsk `cat /root/WPA-PSK-64HEX` debug up

and for the record:
$MODE=11g
$CHAN (I've tried many)
-powersave (disabled on purpose as not supported)

This was working flawlessly for the last three releases on two different
APs which have different hardware.

Are you experiencing the same problem?





 
 
 --
 Caselle da 1GB, trasmetti allegati fino a 3GB e in piu' IMAP, POP3 e SMTP autenticato? GRATIS solo con Email.it http://www.email.it/f
 
 Sponsor:
 Email Paghe e' un ufficio paghe on line al servizio della tua azienda, attivo 24 ore su 24, facile da usare e conveniente. E' il tuo consulente del lavoro dedicato.
* Gratis fino al 31/12/2010
 Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=10680&d=17-12

[ message continues ]

Hi everybody.
Sorry to re-post this issue but nobody replied and I don't think me and S. Biggs are the only one experiencing this issue.

I'm experiencing the same problem Stephen has (described below). I was looking for a solution on the
web but I'd say unsuccessfully. I couldn't found any reply to his
complaint (the one posted by S. Biggs is in fact the only one I've found around).
Here's my pcidump -v output related to the wireless AP:
 5:4:0: Ralink RT2561S
        0x0000: Vendor ID: 1814 Product ID: 0301
        0x0004: Command: 0107 Status ID: 0410
        0x0008: Class: 02 Subclass: 80 Interface: 00 Revision: 00
        0x000c: BIST: 00 Header Type: 00 Latency Timer: 42 Cache Line Size: 10
        0x0010: BAR mem 32bit addr: 0xf8510000
        0x0014: BAR empty (00000000)
        0x0018: BAR empty (00000000)
        0x001c: BAR empty (00000000)
        0x0020: BAR empty (00000000)
        0x0024: BAR empty (00000000)
        0x0028: Cardbus CIS: 00000601
        0x002c: Subsystem Vendor ID: 1432 Product ID: 7128
        0x0030: Expansion ROM Base Address: 00000000
        0x0038: 00000000
        0x003c: Interrupt Pin: 01 Line: 05 Min Gnt: 00 Max Lat: 00
        0x0040: Capability 0x01: Power Management

Everything's running on OpenBSD 4.8 RELEASE.
Thanks in advance, any tip/direction is more than welcome.




[ message continues ]

I got 4.8-current on my access point and it is works just fine.

If that box of yours also is a NFS client using TCP, don't update,
because thats more or less broken right now. :-(

[ message continues ]

Perfect!
The answer is yes, it's also an NFS server, probably not for long but at
the present time yes.
Anyway, you're the second person that confirms the correct functionality
of the ral as an AP on the 4.8-CURRENT (the first that I found was
Stephen Biggs on Tue, 2010-11-30 at 03:33). I'm wondering if they're
planning to release a small patch on the patch branch to fix this. I
would avoid to switch to the current one that, BTW, wouldn't be much
worse than to wait another 5 months for the new release.

I would really avoid to do so but I'm seriously considering to downgrade
the AP to the previous release (4.7) or to rely on a commercial
solution.



 
 
 --
 Caselle da 1GB, trasmetti allegati fino a 3GB e in piu' IMAP, POP3 e SMTP autenticato? GRATIS solo con Email.it http://www.email.it/f
 
 Sponsor:
 Vuoi farti o vuoi fare un regalo originale? Visita MisterCupido.com e personalizza con foto: quadri, tazze, puzzle, cuscini, magliette, peluche, borse, portachiavi...
 Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=11025&d=15-12

[ message continues ]

Already recompiled the kernel and the whole userland approximately three
weeks ago on the patch/stable branch. It didn't fix the issue.
No further kernel patches have been released since then
(the last is 004: RELIABILITY FIX: November 17, 2010). :(

I hope a solution would come up soon, I really like my OpenBSD AP.




[ message continues ]

Thanks, I'll give it a try.


[ message continues ]

The fastest way to get help is to help yourself.  Starting with "cvs
diff -u -rOPENBSD_4_7 -rOPENBSD_4_8 rt*" wouldn't be a bad way to go
about that.

[ message continues ]

For me this fixed the issue:
cvs up -D 2010/08/01 sys/dev/ic/rt2661* sys/dev/pci/if_ral_pci.c

The commit breaking it was dated 2010/08/04, just in case someone wants 
to investigate. But since it is working in current I don't see much 
sense doing that.

HTH
   Markus

[ message continues ]