You are not logged in.
Hello, guys.
I have this problem I've been trying to solve for a couple of days, asked a lot of people and looked over here for similar problems, but couldn't solve it.
I bought a netbook (this one) that came with Windows 10 and changed it, I put Bunsenlabs.
I did the normal (not graphical, because it didn't work) installation, and in the ethernet part, it said "no ethernet card detected, select yours" but didn't select any, as my netbook doesn't have ethernet, and continued the installation. My computer, tho, does have wireless internet option, but when the installation were done, it shows "no network connection".(It worked in W10)
Mine is:
02:00.0 Network controller: Broadcom Corporation BCM43142 802.11b/g/n (rev 01)
and
Kernel driver in use: bcma-pci-bridge
Thank you in advance, guys!
Last edited by Head_on_a_Stick (2017-02-02 20:22:59)
I do not know why yet I live to say 'This thing's to do;' Sith I have cause and will and strength and means to do't. Examples gross as earth exhort me.
Offline
You need the wl driver for that device.
To build that driver without a connection, you will have to download the .deb files for your kernel headers and the broadcom-sta-dkms package on another device then transfer them to your laptop and use gdebi to install them (install the headers first).
Your box should then build the wl module, it can be loaded with:
sudo modprobe -r b44 b43 b43legacy ssb brcmsmac bcma
sudo modprobe wl
Offline
oh hey! thanks for the fast reply.
I'm having some "dependency is not satisfiable" error with both packages. I installed also libiw29_29-1.1_amd64.deb, and tried to do the same with build-essential, but also had a dependency error.
I do not know why yet I live to say 'This thing's to do;' Sith I have cause and will and strength and means to do't. Examples gross as earth exhort me.
Offline
I'm having some "dependency is not satisfiable" error with both packages.
You need to use the information in the error message to find out which other package(s) you need.
You can then search for these packages and download the necessary .deb files from this site:
https://www.debian.org/distrib/packages#search_packages
You shouldn't need build-essential for this btw, just the packages from the dependency chain should be enough.
It may actually be simpler and quicker to re-install the system from scratch and follow this guide instead:
http://crunchbang.org/forums/viewtopic.php?id=39366
Then the bunsen-netinstall script can be used afterwards:
https://github.com/BunsenLabs/bunsen-netinstall
Unfortunately, Broadcom cards are poorly supported under Linux
Offline
So I finally decided to download all the packages from the debian page. It was incredibly tedious but it worked! Now I have wifi.
Thank you a lot!
I do not know why yet I live to say 'This thing's to do;' Sith I have cause and will and strength and means to do't. Examples gross as earth exhort me.
Offline
Oh I say, good show sir!
How does BL perform on that machine?
We can check the hardware support if you want:
sudo update-pciids # update the device ID database
lspci -knn # post the output of this to show your hardware and drivers
Last edited by Head_on_a_Stick (2017-02-02 20:23:43)
Offline
Too late for you now, but there is actually a much simpler way to get that "wl" driver into an isolated machine with a little help from another connected user. Someone with a kernel of the same version and architecture on a connected machine just needs to install module-assistant and broadcom-sta-source and build a .deb package of the driver (module) on their machine-- then the deb can be uploaded, you download it and sneakernet it over to the isolated machine to install with dpkg.
You can try it now, in case you ever need to do an reinstall and need the driver again.
After installing those two packages, in a terminal as sysadmin, run
m-a build broadcom-sta-source
The deb package will be found in /usr/src.
Last edited by stevep (2017-02-03 00:02:26)
Offline
Too late for you now, but there is actually a much simpler way to get that "wl" driver into an isolated machine with a little help from another connected user. Someone with a kernel of the same version and architecture on a connected machine just needs to install module-assistant and broadcom-sta-source and build a .deb package of the driver (module) on their machine-- then the deb can be uploaded, you download it and sneakernet it over to the isolated machine to install with dpkg.
You can try it now, in case you ever need to do an reinstall and need the driver again.
After installing those two packages, in a terminal as sysadmin, run
m-a build broadcom-sta-source
The deb package will be found in /usr/src.
Oh wow! nice, I guess that such a good option too. (Faster in any case haha)
Oh I say, good show sir!
How does BL perform on that machine?
We can check the hardware support if you want:
sudo update-pciids # update the device ID database lspci -knn # post the output of this to show your hardware and drivers
It goes very well, actually. Faster than in my last machine (an atom netbook). I have some trouble with the Telegram desktop app, it works but the graphics act funny. Apart from that, it goes great. This is the output you asked for, sir:
00:00.0 Host bridge [0600]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SoC Transaction Register [8086:2280] (rev 21)
Subsystem: Hewlett-Packard Company Device [103c:815e]
Kernel driver in use: iosf_mbi_pci
00:02.0 VGA compatible controller [0300]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21)
Subsystem: Hewlett-Packard Company Device [103c:815e]
00:0b.0 Signal processing controller [1180]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller [8086:22dc] (rev 21)
Subsystem: Hewlett-Packard Company Device [103c:815e]
00:14.0 USB controller [0c03]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series USB xHCI Controller [8086:22b5] (rev 21)
Subsystem: Hewlett-Packard Company Device [103c:815e]
Kernel driver in use: xhci_hcd
00:1a.0 Encryption controller [1080]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Trusted Execution Engine [8086:2298] (rev 21)
Subsystem: Hewlett-Packard Company Device [103c:815e]
00:1b.0 Audio device [0403]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller [8086:2284] (rev 21)
Subsystem: Hewlett-Packard Company Device [103c:815e]
Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Express Port #1 [8086:22c8] (rev 21)
Kernel driver in use: pcieport
00:1c.3 PCI bridge [0604]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Express Port #4 [8086:22ce] (rev 21)
Kernel driver in use: pcieport
00:1f.0 ISA bridge [0601]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCU [8086:229c] (rev 21)
Subsystem: Hewlett-Packard Company Device [103c:815e]
00:1f.3 SMBus [0c05]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx SMBus Controller [8086:2292] (rev 21)
Subsystem: Hewlett-Packard Company Device [103c:815e]
01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader [10ec:5229] (rev 01)
Subsystem: Hewlett-Packard Company Device [103c:815e]
Kernel driver in use: rtsx_pci
02:00.0 Network controller [0280]: Broadcom Limited BCM43142 802.11b/g/n [14e4:4365] (rev 01)
Subsystem: Hewlett-Packard Company Device [103c:804a]
Kernel driver in use: wl
I do not know why yet I live to say 'This thing's to do;' Sith I have cause and will and strength and means to do't. Examples gross as earth exhort me.
Offline
Thanks for the feedback, I may end up buying one of those myself — the price is certainly right
I think that your graphics stack will be better supported if you follow this guide:
https://forums.bunsenlabs.org/viewtopic.php?id=1185
That hardware is a little too new for our Debian jessie-based release but the steps detailed in the link should improve things markedly.
We should have a new release out towards the end of the year (hopefully!) that will support such devices fully OOTB.
Offline
Hi there! too late, but I've been out of forum and BunsenWorld in general for a long time.
Got the HP Stream11 lately and decided to install BL on it.
With a USB ethernet adapter I've been able to connect to the internet, but the solution mentioned on this thread didn't solve my wifi problems. Googling a bit and found this guide.
Guess it's not the best solution to compile each time you upgrade the kernel, but I'm not planning to change my kernel in a while
Offline
Thanks for the tip!
Your machine has a different wireless card and should actually be supported, just with a poor connection:
Offline
Now I see on lspci output it's not the same model :S
That realtek card works poorly on linux, low signal and it freezes constantly...
If someone have the same problem on *buntu, this worked for me:
sudo add-apt-repository ppa:hanipouspilot/rtlwifi
sudo apt-get update
sudo apt-get install rtlwifi-new-dkms
But ubuntu and it's derivates are too heavy for that machine, bl works like a charm!
Offline
If someone have the same problem on *buntu, this worked for me:
sudo add-apt-repository ppa:hanipouspilot/rtlwifi sudo apt-get update sudo apt-get install rtlwifi-new-dkms
Note that this method should *not* be used in BunsenLabs.
According to my fdn link, the driver has been patched since kernel 4.1 so you may have a better experience in BunsenLabs using the kernel & firmware-realtek package from the jessie-backports repository
Offline
Note that this method should *not* be used in BunsenLabs.
Sure, I first tried Lubuntu but then made a bl partition for testing.
That method is just for Ubuntu and derivates.
According to my fdn link, the driver has been patched since kernel 4.1 so you may have a better experience in BunsenLabs using the kernel & firmware-realtek package from the jessie-backports repository
Great! Guess I will format and make a clean bl install to try last kernel from backports. Thx!
Offline