Control: reassign 849875 wpasupplicant Control: severity 849875 serious Hallo, * Steven Monai [Mon, Jan 02 2017, 08:11:03AM]: > On 17-01-02 04:04 AM, Eduard Bloch wrote: > > * Steven Monai [Sun, Jan 01 2017, 12:59:22PM]: > >> I wanted to try downgrading to the previous version of the package, > >> but it appears that the sid version recently migrated to stretch, > >> and so I can only find the jessie and jessie-backports versions. > > > > You can find them on http://snapshot.debian.org/package/broadcom-sta/ > > Thanks! How was I not aware of this fantastic resource? > > > However, I doubt this alone will solve your problem. I sometimes get > > this kind of hickups, and they don't go away, even with a reboot. What > > helps is a real power cycle (i.e. pull the battery, wait some seconds, > > reinstall). > > If true, this really sucks. I don't want to believe that I need to > resort to voodoo techniques to get hardware working. :(
Please don't beat the messenger and I don't know for sure. This might be a stupid coincidence or a problem with some of my APs. But I am still not impressed by the quality of that driver. > [Some time passes...] > > So I tried downgrading the broadcom-sta-dkms package to the previous > version (6.30.223.271-4), and there was no change, unfortunately. :( > > Next, I decided to try a scientific approach, systematically downgrading > the other packages that directly affect wifi, namely the network-manager > and wpasupplicant packages. So I restored the broadcom-sta-dkms package > back to the current version, and proceeded to use dpkg to directly > install the .deb files for network-manager and wpasupplicant downloaded > from snapshot.debian.org. > > Summary of my findings: > > Downgrading network-manager made no difference. I tried the previous two > package versions (1.4.2-3 and 1.4.2-2). > > Downgrading wpasupplicant, however, resulted in a successful wifi > connection! Specifically, the version of wpasupplicant currently in > stretch (2.5-2+v2.4-3+b1) works for me, with the other two packages > (broadcom-sta-dkms and network-manager) at their latest versions in sid. > > So, for now, I have put a hold on the wpasupplicant package, to keep > version 2.5-2+v2.4-3+b1 installed. Oh, that's bad. Let's reassign to the wpasupplicant with appropriate severity. @Andrew and wpasupplicant folks: feel free to downgrade since the driver is non-free and I cannot reproduce it with my hardware but if true this will hit some users. > Eduard: Should this information be shared with the wpasupplicant package > maintainer(s)? It seems like there could be some kind of incompatibility > between the the latest versions of broadcom-sta-dkms and wpasupplicant. Thanks for the report and additional investigation! Best Regards, Eduard. -- <Salz> jjFux: Ted hieß ja früher auch Walther <Salz> winkiller: hm... es sind 8... die 7 kandidaten und NOTA <Madkiss> Ist der jetzt eigentlich eine gespaltene Persönlichkeit, bei der aber beide Teile bekloppt sind?
