09-18-2014, 11:19 PM
(09-18-2014, 09:25 PM)hardball45 link Wrote: my issue is not that there is a workaround for the problem, my issue is why it works after you do the update but not after the restart. How can that be a Broadcom issue when it works just fine until reboot AFTER the update process? There are many other distributions that work seamlessly with the Broadcom card with no issues what so ever, LXLE, MINT, even Puppy and Simplicity(which is based on puppy) to name a few, I had an issue with a Debian release, Robolinux, but that was the only other one that I tried that had an issue with the Broadcom card. So again I reiterate, how can it be a Broadcom issue?
Hello hardball45,
some of the reasons why a driver may work, then after making an update and rebooting it doesn't are -
1/ because the correct driver is not being told to load on boot. (may be related to #2)
or
2/ the incorrect driver is being told to load on boot/hasn't been uninstalled/removed.
or
3/ more than one are being told to load on boot, and causing an issue.
Re; #1, #2 this shows clearly a cycle such as you are experiencing whereby rebooting reproduces the problem that was "already solved" << that was not in fact fully solved and needs work doing to complete its solution.
Providing information relating to these changes will enable more experienced members to work with you toward a more full and complete solution to the issue.
Broadcom blameless not so, they do not support legacy card, for example, very well, and the Open Source community is where the work to create drivers to support Broadcom products has occurred, because Broadcom followed the M$haft business model of taking consumers money and running, then attempting to force the consumer to replace perfectly functional hardware due to their lack of support.
It may be worth looking at which drivers are installed and which driver is in use, in the seamlessly working instances as this may well provide a solution for the same in LL for you, and others.