[Bug 479597] Re: HP Mini 311 - Does not always boot

Mark mtigges at gmail.com
Wed May 5 05:15:53 UTC 2010


Sorry to add so many messages to this thread, just wanted to give an
update, and hopefully, and more knowledgable soul can help

I added these three lines to blacklist.conf

  blacklist ssb
  blacklist b43
  blacklist b43-pci-bridge

It still hangs on boot.  I eventually was able to get it to boot with
enough tries.

  lsmod | grep b43

Shows nothing ... but ssb is still running.  During the boot it still
hangs at the same normal place (when it does most times).

The most recent reboot the mouse is  working ... not sure why this time,
and not others.

And the latest is .........

I installed the STA drivers from broadcom and the machine came up with
no problems.   Unfortunately, I haven't been able to get the wireless
working.  I have a valid wpa_supplicant.conf file,

When I run wpa_supplicant -dd it just keeps timing out and attempting
the scan again.

I noticed with the new drivers that my interface is now eth1 for the
wireless card, and not wlan0.  The big difference I've found  is that I
don't seem to be able set the essid, whenever I run iwconfig it also
shows the essid as empty, no matter how many times I run "sudo iwconfig
eth1 essid <name>"

Has anyone else seen that or know what the problem might be?

FOR UBUNTU NEWBS like me ... in order to install the sta drivers 'sudo
apt-get install broadcom-sta-common' or, at least in netbook remix I
found a dialog accessable from the main status bar through an icon at
the top right.  It's not there now though after a reboot.  It brought up
a Proprietary Drivers dialog though that enabled me to select the
broadcom sta driver, and some others, I chose the NVIDIA ION driver too.
I'll get around to testing that later.  I believe you can get the same
dialog through System -> Administration -> Hardware Drivers

Oh, and the mouse is still working! lol.

-- 
HP Mini 311 - Does not always boot
https://bugs.launchpad.net/bugs/479597
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.




More information about the kernel-bugs mailing list