Hi Kel,
Am Sonntag, 19. August 2007 10:49 schrieb Kel Modderman:
> On Sun, 5 Aug 2007 05:28:56 am Jurij Smakov wrote:
> > reassign 431657 wpasupplicant
> > thanks
> >
> > On Sat, Aug 04, 2007 at 07:52:46PM +0200, Michael Lansche wrote:
> > > Hi Jurij,
> >
Hi Jurij,
Am Freitag, 3. August 2007 23:21 schrieb Jurij Smakov:
> Ok, that looks pretty regular. Another thing I can suggest is to try
> to add a delay (like 'sleep 5') to the start/pre-up branch in the
> /etc/wpa_supplicant/ifupdown.sh, right after conf_wpa_supplicant line.
> That delay should g
Am Sonntag, 29. Juli 2007 15:49 schrieb Jurij Smakov:
> Hi,
>
> After reading the thread on debianhelp [0], I wonder whether your
> problems might be related to wpa_supplicant configuration. Maybe it
> fails to authenticate to access point the first time during some race
> condition? Could you post
Hi Jurij,
- original Nachricht
Betreff: Bug#431657: automatic wlan connection at bootprocess on Etch only on
second try
Gesendet: Mo, 16. Jul 2007
Von: Jurij Smakov<[EMAIL PROTECTED]>
> Hi Michael,
>
> There is a line
>
> sleep 3
>
> in the start_daemon() function of the /etc/in
Hello,
> Hello,
>
> I have exactly the same behaviour on my laptop with Etch installed
>and a device driven by madwifi module... I suspect that the DHCP
>client start too early, before connection / authentication is done...
>only a supposition...
>
> with regards,
> Frédé
I think my solution is only a workaround and there must be a problem in the
boot sequence of Etch belonging to ipw3945d.
I didn't change anything on the standard Etch boot sequence after installation.
Regards
Michael Lansche
6 matches
Mail list logo
