[SOLVED] Installing Kernel from MX-Package removes wireless-regdb

[g3lux]

Hi, there.
I'm using MXLinux 19.3 with systemd. I had kernel 4.19 by default.
And via MX-packageinstaller i installed a more recent kernel.
"linux-image-5.6.0-2-amd64-unsigned" and "linux-headers-5.6.0-2-amd64".
Found it weird that it uninstalled "wireless-regdb" and "crda".
And if i try to install either "wireless-regdb" and "crda", it says it uninstall's "linux-image-5.6.0-2-amd64-unsigned"...

Any specific reason for recent kernel, uninstalling "wireless-regdb" and "crda"

my /var/log/syslog i get this "error", despite wireless working just fine

Code: Select all

mx-thinkpad kernel: [    5.836335] platform regulatory.0: firmware: failed to load regulatory.db (-2)
mx-thinkpad kernel: [    5.836341] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
mx-thinkpad kernel: [    5.836344] cfg80211: failed to load regulatory.db

And "iw reg get"

Code: Select all

global
country 00: DFS-UNSET
	(2402 - 2472 @ 40), (6, 20), (N/A)
	(2457 - 2482 @ 20), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN
	(2474 - 2494 @ 20), (6, 20), (N/A), NO-OFDM, PASSIVE-SCAN
	(5170 - 5250 @ 80), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN
	(5250 - 5330 @ 80), (6, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN
	(5490 - 5730 @ 160), (6, 20), (0 ms), DFS, PASSIVE-SCAN
	(5735 - 5835 @ 80), (6, 20), (N/A), PASSIVE-SCAN
	(57240 - 63720 @ 2160), (N/A, 0), (N/A)
	

[JayM]

Please run Quick System Info and post your system information as per the forum rules by following the instructions here. Thanks.

[g3lux]

Code: Select all

System:    Host: <filter> Kernel: 5.6.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.6.0-2-amd64 
           root=UUID=<filter> ro quiet splash 
           init=/lib/systemd/systemd 
           Desktop: Openbox 3.6.1 info: tint2 dm: LightDM 1.26.0 
           Distro: MX-19.3_x64 patito feo February 15  2020 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Laptop System: LENOVO product: 2325U9T v: ThinkPad X230 serial: <filter> 
           Chassis: type: 10 serial: <filter> 
           Mobo: LENOVO model: 2325U9T serial: <filter> UEFI [Legacy]: LENOVO 
           v: G2ETB7WW (2.77 ) date: 09/24/2019 
Battery:   ID-1: BAT0 charge: 27.6 Wh condition: 48.1/62.6 Wh (77%) volts: 11.2/10.8 
           model: SANYO 45N1172 type: Li-ion serial: <filter> status: Discharging 
CPU:       Topology: Dual Core model: Intel Core i5-3320M bits: 64 type: MT MCP arch: Ivy Bridge 
           family: 6 model-id: 3A (58) stepping: 9 microcode: 21 L2 cache: 3072 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 20751 
           Speed: 2233 MHz min/max: 1200/3300 MHz Core speeds (MHz): 1: 1567 2: 1914 3: 1385 
           4: 1615 
           Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, 
           STIBP: conditional, RSB filling 
           Type: srbds status: Vulnerable: No microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel 3rd Gen Core processor Graphics vendor: Lenovo driver: i915 v: kernel 
           bus ID: 00:02.0 chip ID: 8086:0166 
           Display: x11 server: X.Org 1.20.4 driver: intel compositor: compton 
           v: 0.1~beta2+20150922 resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel Ivybridge Mobile v: 4.2 Mesa 18.3.6 compat-v: 3.0 
           direct render: Yes 
Audio:     Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Lenovo 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:1e20 
           Sound Server: ALSA v: k5.6.0-2-amd64 
Network:   Device-1: Intel 82579LM Gigabit Network vendor: Lenovo driver: e1000e v: 3.2.6-k 
           port: 6080 bus ID: 00:19.0 chip ID: 8086:1502 
           IF: eth0 state: down mac: <filter> 
           Device-2: Intel Wireless 7260 driver: iwlwifi v: kernel port: efa0 bus ID: 03:00.0 
           chip ID: 8086:08b1 
           IF: wlan0 state: up mac: <filter> 
           IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A 
Drives:    Local Storage: total: 471.36 GiB used: 88.70 GiB (18.8%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 850 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 3B6Q scheme: MBR 
           ID-2: /dev/sdb vendor: Samsung model: SSD PM871 mSATA 256GB SED size: 238.47 GiB 
           block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 3D6Q 
           scheme: GPT 
Partition: ID-1: / raw size: 104.46 GiB size: 102.32 GiB (97.95%) used: 40.77 GiB (39.8%) 
           fs: ext4 dev: /dev/sda4 
           ID-2: swap-1 size: 6.92 GiB used: 0 KiB (0.0%) fs: swap swappiness: 10 (default 60) 
           cache pressure: 100 (default) dev: /dev/sdb3 
Sensors:   System Temperatures: cpu: 50.0 C mobo: 0.0 C 
           Fan Speeds (RPM): cpu: 2964 
Repos:     Active apt repos in: /etc/apt/sources.list 
           1: deb https://dl.bintray.com/tizonia/debian buster main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian buster main contrib non-free
           2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
           1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/headset.list 
           1: deb [arch=amd64] http://headsetapp.co/headset-electron/debian stable non-free
           Active apt repos in: /etc/apt/sources.list.d/mopidy.list 
           1: deb https://apt.mopidy.com/ buster main contrib non-free
           2: deb-src https://apt.mopidy.com/ buster main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb https://ftp.caliu.cat/pub/distribucions/mxlinux/MX-Packages/mx/repo/ buster main non-free
           Active apt repos in: /etc/apt/sources.list.d/nodesource.list 
           1: deb https://deb.nodesource.com/node_12.x buster main
           2: deb-src https://deb.nodesource.com/node_12.x buster main
           Active apt repos in: /etc/apt/sources.list.d/skype-stable.list 
           1: deb [arch=amd64] https://repo.skype.com/deb stable main
           Active apt repos in: /etc/apt/sources.list.d/spotify.list 
           1: deb http://repository.spotify.com stable non-free
           Active apt repos in: /etc/apt/sources.list.d/tor.list 
           1: deb https://deb.torproject.org/torproject.org buster main
           2: deb-src https://deb.torproject.org/torproject.org buster main
           No active apt repos in: /etc/apt/sources.list.d/various.list 
           Active apt repos in: /etc/apt/sources.list.d/vivaldi.list 
           1: deb http://repo.vivaldi.com/stable/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/vscode.list 
           1: deb [arch=amd64] http://packages.microsoft.com/repos/vscode stable main
Info:      Processes: 244 Uptime: 1h 23m Memory: 7.53 GiB used: 3.12 GiB (41.4%) Init: systemd 
           v: 241 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 

[tony37]

You won't have this problem with the wireless-regdb version from the ahs repo (advanced hardware support). I think that for your computer it's absolutely safe to enable the ahs repo in MX Repo Manager, then do "sudo apt update" and then do all the available upgrades.
If you don't want to upgrade to ahs, you can also install wireless-regdb from Debian Backports or MX Test. All those versions won't try to remove your kernel.
Related threads: viewtopic.php?f=104&t=61578&p=608988#p608988 and viewtopic.php?f=55&p=609054

[g3lux]

You won't have this problem with the wireless-regdb version from the ahs repo (advanced hardware support). I think that for your computer it's absolutely safe to enable the ahs repo in MX Repo Manager, then do "sudo apt update" and then do all the available upgrades.
If you don't want to upgrade to ahs, you can also install wireless-regdb from Debian Backports or MX Test. All those versions won't try to remove your kernel.
Related threads: viewtopic.php?f=104&t=61578&p=608988#p608988 and viewtopic.php?f=55&p=609054

Thank you. Yes, i installed "wireless-regdb" from MX Test. And now installed "crda" without a problem.

Will look into AHS repo. It seems only for "firmware" or dkms stuff. Does it touch like "vlc, obs-studio"?
I was thinking if there is a way to enable also the "MX-Test Repo" for apt command. (Without having to open mx-packageinstaller").
Would make updating obs-studio and such easier?

The only thing about installing from MXTest, is that packages if you don't look there for updates, some get left "behind".

I like debian based and more familiar. Than Arch Based

[tony37]

Will look into AHS repo. It seems only for "firmware" or dkms stuff. Does it touch like "vlc, obs-studio"?
I was thinking if there is a way to enable also the "MX-Test Repo" for apt command. (Without having to open mx-packageinstaller").
Would make updating obs-studio and such easier?

The only thing about installing from MXTest, is that packages if you don't look there for updates, some get left "behind".

At this point, the ahs repo wouldn't make a difference for vlc or obs-studio. The initial blog post about this repo is at https://mxlinux.org/blog/new-advanced-h ... for-short/
It's possible to enable the MX Test repo in MX Repo Manager and then on command line you can use "sudo apt install -t a=mx,c=test package_name" if you want to install a package from the test repo. If you really want automatic upgrades for specific packages from MX test, then you could create an apt preferences file in /etc/apt/preferences.d with for example following content:

Code: Select all

Package: obs-studio obs-plugins libobs0
Pin: release a=mx,c=test
Pin-Priority: 100

This will upgrade the obs-studio packages from MX Test if you manually chose to install those. But of course packages from the test repo are more likely to have bugs, so I wouldn't recommend this as a general rule.