As this is the same problem I reported in #487489 I am Cc'ing the bugreport (without snipping)
On Wed, Jun 25, 2008 at 02:20:18PM +1000, Kel Modderman wrote: > On Thursday 29 May 2008 22:01:39 Andrei Popescu wrote: > > On Sun, May 25, 2008 at 11:44:28PM +0300, Andrei Popescu wrote: > > > On Sun, May 25, 2008 at 09:54:31AM +1000, Kel Modderman wrote: > > > > > > > The wpa_cli daemon is absent from your output, which is confusing as it > > > > is > > > > shown to start in your above ifup -v output. > > > > > > Yes, if I ifdown/ifup the interface I can also connect with wpa_cli, but > > > not before. Do you have any idea why? Where should I start looking? > > > > > > Other than /e/n/interfaces and /etc/wpa_supplicant/wpa-roam.conf I > > > didn't touch any configs. Everything is default sid (if sid has any > > > defaults ;)) > > > > Now I'm starting to think this is somehow related to the fact that I'm > > running insserv. > > The only boot time conflict with wpa roaming I am aware of is described at: > http://bugs.debian.org/396137 The only difference is that I removed any SXX links for hwclock as per Petter Reinholdtsen's tips for improving boot speed and I have UTC=yes in /etc/default/rcS > > Otherwise the fact that it's not connecting properly seems to be > > more related to the kernel driver (ipw2200). I'll try investigating > > in that direction. This I already know is not true. The card is connecting just as I documented in the bug report. > Thanks, Kel. Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein)
signature.asc
Description: Digital signature
