Tracking Debian testing/unstable with BunsenLabs

dolly · 2016-08-16 12:12:45

Thanks Head_... as usual I feel a bit... :8 when I get the obvious put in front of my nose. All well as far as I can see after the d-u. Did it the naughty way without a plan B in case of a blackscreenofdeath though. This was on a straight Debian sid LXDE/Openbox system that I use for fun stuff while exercising my Linux mixunderstandings so it would not have been a total disaster for me anyway.
My Bunsid systems are both really messed up and I do not think I will try to unmess them.

KrunchTime · 2016-08-17 06:05:35

@dolly & HoaS: I don't know...I read the bug report and it stated user names and passwords appearing in the terminal. I've seen some weird text in the terminal when shutting down. I saw one of the web addresses I typed in earlier in the day.

Head_on_a_Stick wrote:

Always remember to backup or snapshot before a `dist-upgrade` though!

Bah! I like living on the edge. I've never backed up or taken a snapshot. ]:D Then again, I can always fall back on my stable installs if unstable gets borked.

Last edited by KrunchTime (2016-08-17 06:08:25)

pvsage · 2016-08-18 21:02:57

dolly wrote:

Got this today, but how critical is it?

critical bugs of systemd (231-1 → 231-3) <Outstanding>
 b1 - #834367 - systemctl daemon-reexec (as run on systemd upgrade) causes all keystrokes to go to text console in addition to X (including passwords)
serious bugs of gnupg (1.4.20-6 → 2.1.14-5) <Outstanding>
 b2 - #834368 - gnupg: update to gnupg2 broke gpg-agent autostart
 b3 - #834399 - gnupg: gnupg2-bases gpg breaks Gajim

This is resolved in (231-4), which just dropped today.

Note: I experienced bad performance in X after today's upgrade, with the cursor disappearing and the image appearing to freeze, seems related to keyboard navigation shortcuts like alt-back in web browser or alt-F4 to close a graphical application; also the virtual consoles don't display. Attempting to switch to one of the virtual consoles and back to X refreshes the screen. Will let everyone know if graphics are still problematic after a reboot.

EDIT: All good, as predicted, after reboot.

Last edited by pvsage (2016-08-18 21:12:44)

Head_on_a_Stick · 2016-08-18 21:12:36

pvsage wrote:

I experienced bad performance in X after today's upgrade

What card is it?

xf86-video-intel (xserver-xorg-video-intel) seems to generate a lot of complaints on the Arch forums, it may be time to go modesetting with Intel cards.

pvsage · 2016-08-18 21:15:03

^ See my edit above. (To answer your question, Nvidia with nouveau drivers.)

My guess is the X server just needed to be restarted.

KrunchTime · 2016-08-20 23:47:31

I guess I'm going to start performing dist-upgrades outside of X. Twice within the last 4 or 5 updates on my laptop, my screen went blank with a blinking cursor during installation of upgraded packages and today, my mouse pointer disappeared during a dist-upgrade on my desktop. In all three instances, a reboot cleared things up. Nice how-to on dist-upgrading outside of X in the Siduction Manual.

Snap · 2016-08-21 08:48:34

I guess I'm going to start performing dist-upgrades outside of X.

IMO, if tracking Sid this is one of the first and most important things to learn, though apparently not an expended practice amongst Sid users.

Good switch, KrunchTime.

KrunchTime · 2016-08-22 05:43:11

Snap wrote:

I guess I'm going to start performing dist-upgrades outside of X.
IMO, if tracking Sid this is one of the first and most important things to learn, though apparently not an expended practice amongst Sid users.
Good switch, KrunchTime.

Well, I've been doing updates under X since this summer without incident until recently. So far, nothing bad has happened but I don't think it's good to perform three-finger reboots.

I forgot that evidently Siduction is setup with wireless network access outside of X. I attempted to follow the steps to upgrade outside of X only to remember that BL doesn't have root enabled by default. I logged in using my username and performed the other commands using sudo, but when I performed...

sudo apt-get update

...I was getting errors about the different repos not being accessible. Then I remembered I had the same issue when I ran an instance of CrunchBang under Unstable. For some reason, logging out disables wireless network access.

Snap · 2016-08-22 07:29:24

I have no experience with bunsid, sorry. I always use ceni in Sid. Never had an issue.

tknomanzr · 2016-08-22 07:30:08

^ If you use NetworkManager, then it is by design.

Head_on_a_Stick · 2016-08-22 07:30:38

KrunchTime wrote:

For some reason, logging out disables wireless network access.

NetworkManager must turn off when the user logs out, probably a security feature.

You could switch to /etc/network/interfaces & ifupdown instead:

https://wiki.debian.org/WiFi/HowToUse#Command_Line

If you do this, disable NetworkManager with:

sudo systemctl disable NetworkManager ModemManager

KrunchTime · 2016-08-22 09:50:43

@snap, tknomanzr, & HoaS: Didn't know that about NetworkManager. However, I did log back in. I just wasn't under X. I can't remember if Ceni was used when I used Siduction a couple of years ago or so. I'm almost positive that I had NetworkManager installed under Siduction. My curiosity is piqued...I'll have to checkout the package list over at Siduction.

Thank you for the detailed how-to, HoaS. You remind me of machinebacon from my early days on the CrunchBang forums with your Linux knowledge.

Head_on_a_Stick · 2016-08-22 20:56:50

Wow, high praise indeed -- thanks KT!

damo · 2016-08-22 22:12:59

Head_on_a_Stick wrote:

Wow, high praise indeed -- thanks KT!

"The Stickonator"

dolly · 2016-09-02 10:18:30

Sid, you little ungrateful punk! I will NOT play with you anymore

KrunchTime · 2016-09-04 21:13:16

Apparently, recent network-manager upgrades result in this on my ASUS AIO desktop when I attempt to use WiFi:

Don't know if it's the issue, but found this via a web search: New MAC Address Randomization Breaks WiFi with Various Drivers

Wireless troubleshooting info:

uname -rv
4.7.0-1-amd64 #1 SMP Debian 4.7.2-1 (2016-08-28)

lspci -knn | grep -EiA2 net
02: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. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1043:8554]
	Kernel driver in use: r8169
	Kernel modules: r8169
03:00.0 Network controller [0280]: Broadcom Corporation BCM4352 802.11ac Wireless Network Adapter [14e4:43b1] (rev 03)
	Subsystem: AzureWave BCM4352 802.11ac Wireless Network Adapter [1a3b:2123]
	Kernel driver in use: wl
	Kernel modules: bcma, wl

dmesg | grep -Ei 'wlan|firmw|dhc'
[    0.486650] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[    1.273479] sdhci: Secure Digital Host Controller Interface driver
[    1.273482] sdhci: Copyright(c) Pierre Ossman
[    6.834838] ene_ir: Firmware regs: c1 01
[    8.174731] wlan0: Broadcom BCM43b1 802.11 Hybrid Wireless Controller 0.0.0.0 (obfuscated) (r587334)
[    8.236050] [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS
[    8.443944] wl 0000:03:00.0 wlp3s0: renamed from wlan0
[    9.684675] bluetooth hci0: firmware: failed to load brcm/BCM20702A1-13d3-3404.hcd (-2)
[    9.684711] bluetooth hci0: Direct firmware load for brcm/BCM20702A1-13d3-3404.hcd failed with error -2
[   17.885697] r8169 0000:02:00.0: firmware: direct-loading firmware rtl_nic/rtl8168g-2.fw
[  549.109500] bluetooth hci0: firmware: failed to load brcm/BCM20702A1-13d3-3404.hcd (-2)
[  549.109502] bluetooth hci0: Direct firmware load for brcm/BCM20702A1-13d3-3404.hcd failed with error -2

sudo rfkill list
0: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
1: asus-wlan: Wireless LAN
	Soft blocked: no
	Hard blocked: no
3: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no

Last edited by KrunchTime (2016-09-04 21:52:51)

Head_on_a_Stick · 2016-09-05 06:21:55

Does the connection work if you add the details to /etc/network/interfaces and use `ifup wlps30`?

The stanza should look something like this:

auto wlp3s0
iface wlan0 inet dhcp
        wpa-ssid name_of_the_access_point
        wpa-psk the_password

Check the interface name with `ip link`

https://wiki.debian.org/WiFi/HowToUse#Command_Line

You can disable NetworkManager with:

# systemctl disable NetworkManager ModemManager --now

Enable it again with:

# systemctl enable NetworkManager ModemManager --now

We had a few problem threads about NetworkManager over on the Arch forums recently, unfortunately I didn't pay much attention 'cos I don't like that program

KrunchTime · 2016-09-05 08:09:28

@HoaS: Thank you for the detailed info. I'll give it a try and let you know the outcome. ...I don't like that program What do you use for network management and why do you prefer it over network-manager?

Actually, ip link is a bit obtuse in providing the interface name for wifi. I like inxi -n or inxi -F.

Last edited by KrunchTime (2016-09-05 08:17:53)

Head_on_a_Stick · 2016-09-05 19:33:46

KrunchTime wrote:

...I don't like that program What do you use for network management and why do you prefer it over network-manager?

I dislike NetworkManager generally just because I find it to be far too abstracted -- the program's actions are very opaque and it does many things that I absolutely do not need.

I prefer my network configuration to be as simple as possible and to use the native (CLI) tools of the distribution.

In Arch I use systemd-networkd with systemd-resolved for DNS and wpa_supplicant (started via a systemd unit file) to authenticate with the wireless access point.

In Debian I use /etc/network/interfaces

In Alpine Linux /etc/network/interfaces is also used but the authentication is handled by a separate wpa_supplicant boot script for the openrc init system:
https://wiki.alpinelinux.org/wiki/Conne … cess_point

Finally, in OpenBSD I use /etc/hostname.iwn0 & /etc/mygate (for static IPs with no dhcp) as per hostname.if(5) & myname(5)

As you can see, I'm not a fan of GUIs

KrunchTime · 2016-09-05 20:37:11

Head_on_a_Stick wrote:

As you can see, I'm not a fan of GUIs

Neither is machinebacon.

#281 2016-08-16 12:12:45

Re: Tracking Debian testing/unstable with BunsenLabs

#282 2016-08-17 06:05:35

Re: Tracking Debian testing/unstable with BunsenLabs

#283 2016-08-18 21:02:57

Re: Tracking Debian testing/unstable with BunsenLabs

#284 2016-08-18 21:12:36

Re: Tracking Debian testing/unstable with BunsenLabs

#285 2016-08-18 21:15:03

Re: Tracking Debian testing/unstable with BunsenLabs

#286 2016-08-20 23:47:31

Re: Tracking Debian testing/unstable with BunsenLabs

#287 2016-08-21 08:48:34

Re: Tracking Debian testing/unstable with BunsenLabs

#288 2016-08-22 05:43:11

Re: Tracking Debian testing/unstable with BunsenLabs

#289 2016-08-22 07:29:24

Re: Tracking Debian testing/unstable with BunsenLabs

#290 2016-08-22 07:30:08

Re: Tracking Debian testing/unstable with BunsenLabs

#291 2016-08-22 07:30:38

Re: Tracking Debian testing/unstable with BunsenLabs

#292 2016-08-22 09:50:43

Re: Tracking Debian testing/unstable with BunsenLabs

#293 2016-08-22 20:56:50

Re: Tracking Debian testing/unstable with BunsenLabs

#294 2016-08-22 22:12:59

Re: Tracking Debian testing/unstable with BunsenLabs

#295 2016-09-02 10:18:30

Re: Tracking Debian testing/unstable with BunsenLabs

#296 2016-09-04 21:13:16

Re: Tracking Debian testing/unstable with BunsenLabs

#297 2016-09-05 06:21:55

Re: Tracking Debian testing/unstable with BunsenLabs

#298 2016-09-05 08:09:28

Re: Tracking Debian testing/unstable with BunsenLabs

#299 2016-09-05 19:33:46

Re: Tracking Debian testing/unstable with BunsenLabs

#300 2016-09-05 20:37:11

Re: Tracking Debian testing/unstable with BunsenLabs

Board footer