BunsenLabs RC2 & Realtek Network Adapters

Maki · 2016-04-14 17:45:21

Hello all,

I have just installed the BunsenLabs RC2 on my desktop, which has a Realtek ethernet controller with hardware ID
PCI\VEN_10EC&DEV_8168&SUBSYS_85541043&REV_0C

Unfortunately it seems the installer either does not recognize it or does not have the (nonfree) firmware available, and I am left with an unconnected system.

The installer then leaves the system relatively unfinished to the point where apt-offline can't even update it to a system which could get itself online again.

Is there any way this could be fixed so the installer contains the nonfree firmware or otherwise correctly installs it?

If anyone has any ideas on how I may get my system to a more operational state while having no internet connection, that would be wonderful as well. ^-^; I have been trying to throw packages at it via a USB drive, but to no avail just yet.

damo · 2016-04-14 18:16:50

Can we see the card and driver details, from the output of

lspci -knn | grep -EiA2 net

Maki · 2016-04-14 18:28:06

damo wrote:

Can we see the card and driver details, from the output of
lspci -knn | grep -EiA2 net

I'll have to output it to a file, transfer it to a computer with internet, and then post it here. Having dinner right now, so gimme a few minutes.

xaos52 · 2016-04-14 18:46:56

Post output of

dmesg | grep firmware

To see which firmware version it requires.
It is possible that you will need the firmware package from jessie-backports.
If that is the case, you will have to download the package from a network connected system, transfer the .deb file via usb disk, and install it locally on the system with non-working connection using

dpkg -i <path-to-the-deb>

You can get the package from this location

Let us know if you need more info.

Good luck

Maki · 2016-04-16 11:25:34

I managed to get it to work after some initial troubles getting the correct version of apt-offline to run, but I won't leave you guys hanging.
Here are the outputs to the questions asked:

damo wrote:

Can we see the card and driver details, from the output of
lspci -knn | grep -EiA2 net

$ lspci -knn | grep -EiA2 net
03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0c)
	Subsystem: ASUSTeK Computer Inc. Device [1043:8554]
	Kernel driver in use: r8169

xaos52 wrote:

Post output of
dmesg | grep firmware
To see which firmware version it requires.
It is possible that you will need the firmware package from jessie-backports.
If that is the case, you will have to download the package from a network connected system, transfer the .deb file via usb disk, and install it locally on the system with non-working connection using
dpkg -i <path-to-the-deb>
You can get the package from this location
Let us know if you need more info.
Good luck

$ dmesg | grep firmware
[    7.360875] r8169 0000:03:00.0: firmware: direct-loading firmware rtl_nic/rtl8168g-2.fw

damo · 2016-04-16 14:24:58

Maki wrote:

I managed to get it to work after some initial troubles getting the correct version of apt-offline to run, but I won't leave you guys hanging......

....and the fix was...? (for the benefit of others with the same problem)

Anything to do with this for example? The pain of an Realtek (RTL8111/RTL8168) ethernet card

Maki · 2016-04-16 16:45:56

damo wrote:

Maki wrote:
I managed to get it to work after some initial troubles getting the correct version of apt-offline to run, but I won't leave you guys hanging......
....and the fix was...? (for the benefit of others with the same problem)
Anything to do with this for example? The pain of an Realtek (RTL8111/RTL8168) ethernet card

I have no clue what the fix was beyond me running apt-offline's update cycle after setting up my (EMPTY!) sources.list as follows:

## BunsenLabs
deb http://pkg.bunsenlabs.org/debian bunsen-hydrogen main
deb http://pkg.bunsenlabs.org/debian jessie-backports main

## Debian
deb http://http.debian.net/debian wheezy main contrib non-free
deb http://http.debian.net/debian jessie main contrib non-free

## Debian Updates
deb http://http.debian.net/debian jessie-updates main

## Debian Security
deb http://security.debian.org/ wheezy/updates main
deb http://security.debian.org/ jessie/updates main

## Debian Backports
deb http://http.debian.net/debian wheezy-backports main contrib non-free
deb http://http.debian.net/debian jessie-backports main contrib non-free

## Debian Testing
# deb http://http.debian.net/debian testing main contrib non-free

The network 'just worked' after I finally got apt-offline to upgrade stuff via my laptop and a USB drive (which was headache-worthy and I can't help wonder if there's no easier way to do this), and after about the 4th or 5th system reboot.

I haven't had to download the driver from the realtek site as described in the linked story, no. Things just sorted themselves and left me sitting here wondering what happened exactly. x_X

I'm sorry I can't give any further explanation on this.

Last edited by Maki (2016-04-16 16:47:06)

Head_on_a_Stick · 2016-04-16 16:49:46

Maki wrote:

(EMPTY!) sources.list

Your sources.list was empty?

Did you select a mirror during the installation?

Maki wrote:

## Debian Testing
# deb http://http.debian.net/debian testing main contrib non-free

This is not a good idea.

Please read https://wiki.debian.org/DontBreakDebian … nkenDebian & http://forums.debian.net/viewtopic.php?f=20&t=114130

Maki · 2016-04-16 16:51:15

Head_on_a_Stick wrote:

Maki wrote:
(EMPTY!) sources.list
Your sources.list was empty?
Did you select a mirror during the installation?

Considering my network was not working, I was unable to select a mirror during installation.

Head_on_a_Stick wrote:

Maki wrote:
## Debian Testing
# deb http://http.debian.net/debian testing main contrib non-free
This is not a good idea.
Please read https://wiki.debian.org/DontBreakDebian … nkenDebian & http://forums.debian.net/viewtopic.php? … 0&start=15

It's commented-out, isn't it?

Head_on_a_Stick · 2016-04-16 16:55:40

Maki wrote:

It's commented-out, isn't it?

Well yes but why have it there if you're not going to use it?

To use packages from testing/unstable in BunsenLabs, it is recomended that you backport them or at least recompile the source in jessie to avoid any risks of b0rkage.

Head_on_a_Stick · 2016-04-16 16:58:06

Maki wrote:

Considering my network was not working, I was unable to select a mirror during installation.

So to summarise: your device is too new to be supported by the stock Debian jessie packages having been manufactured after the jessie repositories were frozen.

You installed the newer firmware package from jessie-backports to get the device working.

As there was no connection during the installation, you had to add the sources yourself.

Maki · 2016-04-16 17:29:29

Head_on_a_Stick wrote:

Maki wrote:
It's commented-out, isn't it?
Well yes but why have it there if you're not going to use it?
To use packages from testing/unstable in BunsenLabs, it is recomended that you backport them or at least recompile the source in jessie to avoid any risks of b0rkage.

I mainly just have it in there so I remember it exists in case I need it for something-or-other in the future. It's not hurting anyone while being commented-out.

Head_on_a_Stick wrote:

Maki wrote:
Considering my network was not working, I was unable to select a mirror during installation.
So to summarise: your device is too new to be supported by the stock Debian jessie packages having been manufactured after the jessie repositories were frozen.

No, my computer was bought in 2012~2013 (Debian Jessie was frozen on November 5th, 2014), using cheap parts because I didn't have a lot of money at the time. It was mid-range at best. It just has a shoddy network controller.

Head_on_a_Stick wrote:

You installed the newer firmware package from jessie-backports to get the device working.
As there was no connection during the installation, you had to add the sources yourself.

I had to use apt-offline and a laptop with a frankenupdated "CrunchBang to Jessie-with-BL" system on it, but that seems a fair assessment.

Head_on_a_Stick · 2016-04-16 17:43:46

OK, thanks for the information!

#1 2016-04-14 17:45:21

BunsenLabs RC2 & Realtek Network Adapters

#2 2016-04-14 18:16:50

Re: BunsenLabs RC2 & Realtek Network Adapters

#3 2016-04-14 18:28:06

Re: BunsenLabs RC2 & Realtek Network Adapters

#4 2016-04-14 18:46:56

Re: BunsenLabs RC2 & Realtek Network Adapters

#5 2016-04-16 11:25:34

Re: BunsenLabs RC2 & Realtek Network Adapters

#6 2016-04-16 14:24:58

Re: BunsenLabs RC2 & Realtek Network Adapters

#7 2016-04-16 16:45:56

Re: BunsenLabs RC2 & Realtek Network Adapters

#8 2016-04-16 16:49:46

Re: BunsenLabs RC2 & Realtek Network Adapters

#9 2016-04-16 16:51:15

Re: BunsenLabs RC2 & Realtek Network Adapters

#10 2016-04-16 16:55:40

Re: BunsenLabs RC2 & Realtek Network Adapters

#11 2016-04-16 16:58:06

Re: BunsenLabs RC2 & Realtek Network Adapters

#12 2016-04-16 17:29:29

Re: BunsenLabs RC2 & Realtek Network Adapters

#13 2016-04-16 17:43:46

Re: BunsenLabs RC2 & Realtek Network Adapters

Board footer