I had a look at the changelog and yes there were lots of entries for ath5k (assuming that may be the problem) for .rc1.
And as far as I can tell all of them have the problem, though it is harder to get .rc1 and .rc2 up; if I were a tougher CLI jockey I would set up a test case using terminal utilities and try it via a console.
020638rc1.201101192228 -- boots badly (1)(2). Network scans but not connected immediately
020638rc2.201101220905 -- boots badly(1)(2). Network scans but not connected immediately
020638rc3.201102010912 -- boots OK after message(1). Network not connected immediately
(1):message: /proc/device-tree can't find root (on console)
(2): video terrible but switching consoles gets X to redraw
I had a look at the changelog and yes there were lots of entries for ath5k (assuming that may be the problem) for .rc1.
And as far as I can tell all of them have the problem, though it is harder to get .rc1 and .rc2 up; if I were a tougher CLI jockey I would set up a test case using terminal utilities and try it via a console.
020638rc1. 201101192228 -- boots badly (1)(2). Network scans but not connected immediately 201101220905 -- boots badly(1)(2). Network scans but not connected immediately 201102010912 -- boots OK after message(1). Network not connected immediately
020638rc2.
020638rc3.
(1):message: /proc/device-tree can't find root (on console)
(2): video terrible but switching consoles gets X to redraw