From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: Date: Mon, 12 May 2008 17:13:11 +0200 From: "David du Colombier" <0intro@gmail.com> To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net> In-Reply-To: <200805121456.m4CEuqX03870@demeter.cs.utwente.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200805121010.m4CAAJX14857@demeter.cs.utwente.nl> <9f3897940805120552j2524b4ael7ea0092754ce0266@mail.gmail.com> <200805121320.m4CDKsX02428@demeter.cs.utwente.nl> <200805121456.m4CEuqX03870@demeter.cs.utwente.nl> Subject: Re: [9fans] Bitsy's WaveLAN problem Topicbox-Message-UUID: a53c3ea4-ead3-11e9-9d60-3106f5b1d025 > do you have a single or double slot sleeve? > the double slot sleeve needs extra code to work -- > hmm... if you would have such one it wouldn't have worked at all > and you mentioned that it has somewhat worked, thus, single sleeve? I have a single slot sleeve since I seen before on this mailing list that the double sleeve is not supported. It worked two or three times yesterday. I was able to connect to the Access Point, but I was not able to ping other machines. The first time, the kernel crashed 30 seconds after. Since, I tried many times, and it does not work anymore. bitsy# echo -n 'configure #l0 wavelan' > /dev/pcm0ctl echo: write error: couldn't configure device The cause of this problem was identified in my second e-mail, after many print debugging. It was caused by the function w_cmd() in the file /sys/src/9/bitsy/wavelan.c. When it worked, I was using a timeout of 100000. Even with the same kernel and ramdisk, sometimes it works (very rarely), often it won't works. -- David du Colombier