On Mon, Oct 31, 2005 at 07:30:21PM +0100, Guus Sliepen wrote:
> >
> > First, the bug report lack any details (what does not
> > work). Second, it looks like a driver problem, so you may want to
> > forward on the Prism54 mailing list.
>
> Oh, have you looked at http://bugs.debian.org/336302? This was not the
> original bugreport, but a follow-up.
My bad, I did not look at the original report (not that the
original report had much details anyway - iwconfig/ifconfig/dmesg
output ?).
All those bugs smell like driver or configuration issues. WEP
is notoriously touch and go, so I would try to isolate that. Also, it
seems that in both cases if the upgrade did involve a kernel update,
and I would finger that as a potential cause. The newer kernel
*should* work, but networking is currently in flux in the kernel, so
that may be the cause.
> Met vriendelijke groet / with kind regards,
> Guus Sliepen <email address hidden>
On Mon, Oct 31, 2005 at 07:30:21PM +0100, Guus Sliepen wrote: bugs.debian. org/336302? This was not the
> >
> > First, the bug report lack any details (what does not
> > work). Second, it looks like a driver problem, so you may want to
> > forward on the Prism54 mailing list.
>
> Oh, have you looked at http://
> original bugreport, but a follow-up.
My bad, I did not look at the original report (not that the ifconfig/ dmesg
original report had much details anyway - iwconfig/
output ?).
All those bugs smell like driver or configuration issues. WEP
is notoriously touch and go, so I would try to isolate that. Also, it
seems that in both cases if the upgrade did involve a kernel update,
and I would finger that as a potential cause. The newer kernel
*should* work, but networking is currently in flux in the kernel, so
that may be the cause.
> Met vriendelijke groet / with kind regards,
> Guus Sliepen <email address hidden>
Have fun...
Jean