dolphin_oracle's respins (updated June 23, 2024)

[richb]

Yes, that took care of it, thx!

I don't see a way to mark this as solved. Must be due to the context I'm guessing.

You aren’t the original poster so you can’t mark. But yeah no applicable anyway.

Thanks DO. I did not notice that.

[dolphin_oracle]

Hi all,
Hello @dolphin oracle, (a noob question) ... Can you explain more precisely the advantages & inconvenients, and the goal, of a "bare respin" version. And if a MX23-bare-respin is planed? (And why the need of a only systemd version, for a better compatibility ?)

the bare respin had few preinstalled applications. some people like that. I do not have a mx23 version planned at this time. there is already a "minimal" respin. https://sourceforge.net/projects/mx-lin ... X-Minimal/

and there is no real need for a systemd-only respin. it was mostly a platform for me to see if I could make the live persistence system at least operation under systemd without making gigantic changes to the live system. its not error free but is probably "good enough" for enthusiasts. a few folks don't want to mess with sysVinit for whatever reason (usual some service that doesn't have an init script) and the respin removes that for them.

[oops]

... OK, thank you for your accurate explanation dolphin_oracle.

[a_freed_man]

Next issue is that it doesn't detect the WiFi adaptor in the system. It is "WiFi 6" according to beeLink.
Seems like these Intel based systems in the last few years have chipsets that prove to be difficult to program. I have an Acer Swift laptop that sound doesn't work properly (doesn't auto detect when headphones are plugged in for one thing, I have to manually select the output device. Sometimes it comes out of both headphones & speakers!).

I posted the quick info here. Here is the Network section from it:

Code: Select all

Network:
  Device-1: Intel driver: iwlwifi v: kernel modules: wl port: N/A bus-ID: 00:14.3
    chip-ID: 8086:54f0 class-ID: 0280
  IF: wlan0 state: down mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 v: kernel pcie:
    gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 01:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>

The above isn't what I'm seeing right now. Could be I turned on WiFi in my router when I took the quick info before. I will restart with phone hotspot on to see if it's detected now... It wasn't. The quick info for the network has also changed slightly, showing:

Code: Select all

Device 1: Intel driver: N/A modules: iwlwifi, wl port N/A bus-ID: 00:14.3 chip-ID: 8086:54f0
class-ID: 0280

The difference is the "N/A modules vs "kernel modules", so probably not significant.

Is there an rfkill or equiv on MX23? The info for one of the other guys in that thread had the same chipset on his beeLink and his interface was UP, so I'll send him a DM to ask what he did to get WiFi working.

The MX Network Assistant shows wl, iwlwifi drivers (and others), and 2 items under status tab. The 1st is Network Controller which has no interface and cannot be disabled. The 2nd is for the wired eth0. Net diagnostics tab is useless for this type of issue. Rescanning shows same info.

[manyroads]

@dolphin_oracle Am I right to assume that the bare systemd version can/might be run as unstable? For me a "thin MX" that is capable of running unstable would be wonderful.

[dolphin_oracle]

@dolphin_oracle Am I right to assume that the bare systemd version can/might be run as unstable? For me a "thin MX" that is capable of running unstable would be wonderful.

if you mean the sid/unstable debian repo, I wouldn't recommend it. but its linux, you can do what you want.

[manyroads]

@dolphin_oracle Am I right to assume that the bare systemd version can/might be run as unstable? For me a "thin MX" that is capable of running unstable would be wonderful.

if you mean the sid/unstable debian repo, I wouldn't recommend it. but its linux, you can do what you want.

I often do... generally everything I break I'm lucky enough to patch back together; I'll test the systemd only version first. Then I'll trim things down to see where it breaks. If I come up with something useful/ workable, I'll share it with "both people" who might be interested.

[l0dr3]

@a_freed_man

1.) blacklist the broadcom 'wl' modules stuff ...
2.) Intel AX101 chipset needs at least a kernel v6.4.xx ++, see my experiences w#my BeeLink EQ12 in this post/thread:
viewtopic.php?p=731457#p731457

greetz

l0dr3

[dolphin_oracle]

messing around with a spin that only includes sysVinit. oddly, plymouth (the boot splash daemon) is proving to be a challenge.

[a_freed_man]

@a_freed_man

1.) blacklist the broadcom 'wl' modules stuff ...
2.) Intel AX101 chipset needs at least a kernel v6.4.xx ++, see my experiences w#my BeeLink EQ12 in this post/thread:
viewtopic.php?p=731457#p731457

greetz

l0dr3

I did manage to get WiFi working by installing a 6.4 kernel from mx-package manager, but still no bluetooth. I tried renaming the ibt*4150 files to ibt*1050 but no change to behavior, it still won't load firmware.