Broadcom network card driver support issues [ongoing]

If you are new to Linux or new to Sabayon Linux and just not sure where to post, here ya go. Post without fear of being told to RTFM :-)

Moderator: Moderators

Broadcom network card driver support issues [ongoing]

Postby pinkytoes » Mon Mar 03, 2014 12:56

i just installed Sabayon GNOME (64bit) on my acer v5 571p
but so far not making any headway getting it on the internet.

i tried # lspci -vnn | grep 14e4 and looked up the last chunk:
http://wireless.kernel.org/en/users/Drivers/b43
and it turns out the b43 drivers don't support my tech. [4359]
nano /etc/modprobe.d/blacklist.conf shows wl blacklisted.

then i tried blacklisting both b43 and bcma, and unlisting wl
but still don't know how to get a network manager running.
# etc/init.d/net.eth0 start returns this message:
* WARNING: net.eth0 is already starting.

is there anywhere to get an fwcutter version for sabayon?
do i have to buy a second wifi card for my brand new laptop?
Last edited by pinkytoes on Mon May 12, 2014 18:10, edited 2 times in total.
Sabayon GNOME (64bit Steam) on acer v5 571p (also e1-572p)
pinkytoes
Simple Hen
 
Posts: 56
Joined: Sun Mar 02, 2014 20:06

Re: nm-applet: failed to initialise D-bus

Postby BoeroBoy » Tue Mar 04, 2014 1:09

If you're in a new install you're probably using SystemD instead of the traditional Sysvinit (/etc/init.d/net.x start). Also keep in mind that NetworkManager and init scripts are a little different. Check the forum below:

http://forums.gentoo.org/viewtopic-t-82 ... art-0.html

If you're using systemd, try checking the output of systemctl status NetworkManager
User avatar
BoeroBoy
Simple Hen
 
Posts: 68
Joined: Fri Feb 23, 2007 20:25

Re: nm-applet: failed to initialise D-bus

Postby pinkytoes » Wed Mar 05, 2014 3:20

#http://i62.tinypic.com/14x03kn.png
suddenly i have wifi on my system tray pulldown

If you're in a new install you're probably using SystemD instead of the traditional Sysvinit

Code: Select all
$ cat /proc/1/stat
1 (systemd)


If you're using systemd, try checking the output of systemctl status NetworkManager

Code: Select all
# systemctl status NetworkManager
NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib64/systemd/system/NetworkManager.service; enabled)
   Active: active (running) since Tue 2014-03-04 06:34:53 EST; 5h 13min ago
 Main PID: 3936 (NetworkManager)
   CGroup: name=systemd:/system/NetworkManager.service
           └─3936 /usr/sbin/NetworkManager --no-daemon

Mar 04 06:34:53  NetworkManager[3936]:
 <warn> /sys/devices/virtual/net/lo:
 couldn't determine device driver; ignoring...
Mar 04 06:34:53  NetworkManager[3936]:
 <info> ModemManager available in the bus
Mar 04 06:34:53  NetworkManager[3936]:
 <info> wpa_supplicant started
Mar 04 06:34:53  NetworkManager[3936]:
 <info> (eth0) supports 1 scan SSIDs
Mar 04 06:34:53  NetworkManager[3936]:
 <warn> Trying to remove a non-existant call id.
Mar 04 06:34:53  NetworkManager[3936]:
 <info> (eth0): supplicant interface state:
 starting -> ready
Mar 04 06:34:53  NetworkManager[3936]:
 <info> (eth0): device state change: unavailable
 -> disconnected (reason 'supplicant-available') [20 30 42]
Mar 04 06:34:53  NetworkManager[3936]:
 <info> (eth0): supplicant interface state:
 ready -> disconnected
Mar 04 06:34:53  NetworkManager[3936]:
 <info> (eth0) supports 1 scan SSIDs
Mar 04 06:34:58  NetworkManager[3936]:
 <info> (eth0): supplicant interface state: disconnected -> inactive
Last edited by pinkytoes on Tue Apr 29, 2014 0:02, edited 5 times in total.
Sabayon GNOME (64bit Steam) on acer v5 571p (also e1-572p)
pinkytoes
Simple Hen
 
Posts: 56
Joined: Sun Mar 02, 2014 20:06

Re: nm-applet: failed to initialise D-bus

Postby pinkytoes » Wed Mar 12, 2014 17:59

so the update that just went through
asked me to manually review and remove:
Plymouth plugin, Sysd shim, and Orc settings
this all made good sense, and so i did...

but now rigo is giving me a wake up that
it's extremely important to update
/etc/modprobe.d/blacklist.conf
before rebooting the system.

Edit / Difference / Discard / Accept
are the four buttons rigo gives me,
edit seems to be the stock .conf file
difference seems to be changes i made.

my question is since b43 does not support
my laptop's wireless networking card,
is it safe to stop blacklisting it now?
also does discard or accept mean revert?

(post timestamped for noon, it's 1pm. what gives?)
Sabayon GNOME (64bit Steam) on acer v5 571p (also e1-572p)
pinkytoes
Simple Hen
 
Posts: 56
Joined: Sun Mar 02, 2014 20:06

Re: nm-applet: failed to initialise D-bus

Postby pinkytoes » Thu Mar 13, 2014 14:15

the answer is yes, reverting to the recommended
version of blacklist.conf will break my wifi again. ):
also, accept was the option to revert to original,
making discard the option to retain the fixes.

It seems the changes to blacklist.conf where what
got networkmanager working again, not systemctl.
not sure what to make of urgent wake up requiring
that i re-break my wifi before safely rebooting.
Sabayon GNOME (64bit Steam) on acer v5 571p (also e1-572p)
pinkytoes
Simple Hen
 
Posts: 56
Joined: Sun Mar 02, 2014 20:06

Re: nm-applet: failed to initialise D-bus

Postby pinkytoes » Sun Apr 06, 2014 6:09

this makes twice that i bought the line
about how the world would end if i didnt
let this update's configuration changes
break my wifi yet again. this is just cruel.
Last edited by pinkytoes on Tue Apr 29, 2014 2:52, edited 1 time in total.
Sabayon GNOME (64bit Steam) on acer v5 571p (also e1-572p)
pinkytoes
Simple Hen
 
Posts: 56
Joined: Sun Mar 02, 2014 20:06

Re: nm-applet: failed to initialise D-bus

Postby pinkytoes » Mon Apr 28, 2014 23:59

this time i noticed the Broadcom licence
in the list rigo needed me to okay to proceed,
but there was not even the courtesy of an
urgent if incorrect plea to break my wifi now.

i accepted the licences, okayed the updates
and -poof- my wifi is completely broken again.
have to check blacklist.conf to see if that's it.
no misleading message - good. no wifi - bad.
Sabayon GNOME (64bit Steam) on acer v5 571p (also e1-572p)
pinkytoes
Simple Hen
 
Posts: 56
Joined: Sun Mar 02, 2014 20:06

Re: nm-applet: failed to initialise D-bus

Postby pinkytoes » Tue Apr 29, 2014 0:08

so it turns out there was no warning to change blacklist.conf
because no changes were made. blacklist bcma and b43 but not wl.
so now i have no nm-applet, no wifi, no easy explanation for why
and no clear course for what to do next. urgent please help!
Sabayon GNOME (64bit Steam) on acer v5 571p (also e1-572p)
pinkytoes
Simple Hen
 
Posts: 56
Joined: Sun Mar 02, 2014 20:06

Re: nm-applet: failed to initialise D-bus

Postby pinkytoes » Tue Apr 29, 2014 2:27

hey moderators, if moving this thread to Networking and Wireless
will get it more airtime, i have no problem with that at all.
i honestly exhausted everything the internet has to say
with wifi not working with sabayon installed on my laptop.

so when i checked blacklist.conf and it hadn't been changed,
i have no means at all to empower myself within the confines of sabayon.
does this mean i have to roll-back to a pre-breaking-update kernel?'
or is my only method to regain internet to try a different linux distro?

it was good to learn why blacklist.conf could break my wifi
but this learning curve is too demoralising to deal with.
is there no testing done before unleashing wifi breaking updates?
not having wifi means camping out at a friend's just to fix the problem.
Last edited by pinkytoes on Tue Apr 29, 2014 4:52, edited 1 time in total.
Sabayon GNOME (64bit Steam) on acer v5 571p (also e1-572p)
pinkytoes
Simple Hen
 
Posts: 56
Joined: Sun Mar 02, 2014 20:06

Re: nm-applet: failed to initialise D-bus

Postby pinkytoes » Tue Apr 29, 2014 2:51

here is what systemctl status NetworkManager has to say on the matter:
Code: Select all
<info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0
<info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
<info> (eth0): bringing up device.
<info> (eth0): preparing device.
<info> (eth0): deactivating device (reason 'managed') [2]
<info> Added default wired connection 'Wired connection 1'
          for /sys/devices/pci0000:00/0000:00:1c.2/0000:02:00.2/net/eth0
[b]<warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
<warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
<warn> Couldn't acquire object manager proxy: Error calling StartServiceServiceByName
             for org.bluez: GDBus.Error:org.freedesktop.systemd1.LoadFailed:
              Unit dbus-org.bluez service failed to load: No such file or directory[/b]
<info> ModemManager available in the bus
Sabayon GNOME (64bit Steam) on acer v5 571p (also e1-572p)
pinkytoes
Simple Hen
 
Posts: 56
Joined: Sun Mar 02, 2014 20:06

Next

Return to Beginners|Newbies Area

Who is online

Users browsing this forum: No registered users and 1 guest