Search Results for 'startx'

[Member stevesr0]

Hi The Mas,

thank you.

In case anyone is interested, my routine for avoiding systemd additions with upgrades is as follows:

1. Run sudo apt update && sudo apt full-upgrade

2. Say “no” when asked if you want to proceed with the upgrade.

3. Launch aptitude and examine each candidate upgrade package.

4. Make a list of all packages that change from a nosystemd version to a regular debian one.

5. Hold all the packages on the list using

sudo apt-mark hold <package name>

6. Rerun #1.

7. If not comfortable, recheck any suspicious package.

8. When comfortable, rerun #1 and “yes”.

9. run the initiation script and then startx and check that Pipewire still works.

N.B. when a package upgrade to a nosystemd version appears, I unhold the package before upgrading by running

sudo apt-mark unhold <package name>

Might seem tedious, but I only do this for the Sid machine and it usually involves only one cycle.

Of course if someone has a better way to do this, I would appreciate learning it.

stevesr0

• This reply was modified 4 months, 2 weeks ago by stevesr0.
• This reply was modified 4 months, 2 weeks ago by stevesr0.

[Member techore]

@masinic et al, happy holiday and stay warm. I am seeing the news on the your weather. Looks awful.

This is my new daily driver once I finish the dwm spin. I am hopeful to have all the winkles worked out with one more beta, but a Christmas release isn’t going to happen as I hoped. I have a week off in January and it will be published in January in whatever state it is in come the end of my vacation.

System:
  Kernel: 6.1.0-1.1-liquorix-amd64 arch: x86_64 bits: 64 compiler: gcc
    v: 10.2.1 Desktop: dwm v: 6.4 dm: startx
    Distro: antiX-22-runit_x64-core Grup Yorum 18 October 2022
    base: Debian GNU/Linux 11 (bullseye)
Machine:
  Type: Laptop System: ASUSTeK product: ROG Strix G513QY_G513QY v: 1.0
    serial: <filter>
  Mobo: ASUSTeK model: G513QY v: 1.0 serial: <filter>
    UEFI: American Megatrends LLC. v: G513QY.318 date: 03/29/2022
Battery:
  ID-1: BAT0 charge: 87.2 Wh (100.0%) condition: 87.2/90.0 Wh (96.9%)
    volts: 17.2 min: 15.9 model: AS3GWYF3KC GA50358 serial: <filter>
    status: full
CPU:
  Info: 8-core model: AMD Ryzen 9 5980HX with Radeon Graphics bits: 64
    type: MT MCP arch: Zen 3 rev: 0 cache: L1: 512 KiB L2: 4 MiB L3: 16 MiB
  Speed (MHz): avg: 3300 min/max: 1200/5024 boost: enabled cores: 1: 3300
    2: 3300 3: 3300 4: 3300 5: 3300 6: 3300 7: 3300 8: 3300 9: 3300 10: 3300
    11: 3300 12: 3300 13: 3300 14: 3300 15: 3300 16: 3300 bogomips: 105402
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: AMD Navi 22 vendor: ASUSTeK driver: N/A arch: RDNA 2 pcie:
    speed: 16 GT/s lanes: 16 bus-ID: 03:00.0 chip-ID: 1002:73df
  Device-2: AMD Cezanne vendor: ASUSTeK driver: amdgpu v: kernel
    arch: GCN 5.1 pcie: speed: 8 GT/s lanes: 16 ports: active: eDP-1
    empty: HDMI-A-1 bus-ID: 08:00.0 chip-ID: 1002:1638
  Display: server: X.Org v: 1.20.11 driver: X: loaded: amdgpu
    unloaded: fbdev,modesetting,radeon,vesa gpu: amdgpu
    resolution: 2560x1440~165Hz
  OpenGL:
    renderer: AMD RENOIR (DRM 3.49.0 6.1.0-1.1-liquorix-amd64 LLVM 11.0.1)
    v: 4.6 Mesa 20.3.5 direct render: Yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1
    port: f000 bus-ID: 04:00.0 chip-ID: 10ec:8168
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi
    v: kernel pcie: speed: 5 GT/s lanes: 1 bus-ID: 05:00.0 chip-ID: 8086:2725
  IF: wlan0 state: down mac: <filter>
Drives:
  Local Storage: total: 2.35 TiB used: 9.89 GiB (0.4%)
Info:
  Processes: 298 Uptime: 10m Memory: 30.77 GiB used: 1.72 GiB (5.6%)
  Init: runit v: N/A runlevel: 2 Compilers: gcc: 10.2.1 alt: 10 Packages:
  apt: 1347 Shell: fish v: 3.1.2 running-in: kitty inxi: 3.3.19

[Member techore]

antiX 22 runit dwm unofficial beta 7 on a Asus UX330UAK which was my daily driver.

Upgraded from antiX 5.10 kernl to a Liquorix 6.1 Kernel to resolve an issue with its Intel Bluetooth chipset. Originally, my intent was to bump the kernel to 5.15.x which is being purported to fix the issue but the Liquorix install script installed 6.1. What I get for not reading the script more closely. /shrug. I will do it manually next time.

techore@axdwmb7 ~> sudo inxi -zv3x
System:
  Kernel: 6.1.0-1.1-liquorix-amd64 arch: x86_64 bits: 64 compiler: gcc
    v: 10.2.1 Desktop: dwm v: 6.4 dm: startx
    Distro: antiX-22-runit_x64-core Grup Yorum 18 October 2022
    base: Debian GNU/Linux 11 (bullseye)
Machine:
  Type: Laptop System: ASUSTeK product: UX330UAK v: 1.0 serial: <filter>
  Mobo: ASUSTeK model: UX330UAK v: 1.0 serial: <filter>
    UEFI: American Megatrends v: UX330UAK.305 date: 05/02/2017
Battery:
  ID-1: BAT0 charge: 38.8 Wh (100.0%) condition: 38.8/57.1 Wh (68.0%)
    volts: 11.6 min: 11.6 model: ASUSTeK ASUS Battery serial: N/A
    status: not charging
CPU:
  Info: dual core model: Intel Core i5-7200U bits: 64 type: MT MCP
    arch: Amber/Kaby Lake note: check rev: 9 cache: L1: 128 KiB L2: 512 KiB
    L3: 3 MiB
  Speed (MHz): avg: 2601 min/max: 400/2601 boost: enabled cores: 1: 2601
    2: 2601 3: 2601 4: 2601 bogomips: 21599
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel HD Graphics 620 vendor: ASUSTeK driver: i915 v: kernel
    arch: Gen9.5 ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 00:02.0
    chip-ID: 8086:5916
  Device-2: Realtek USB2.0 HD UVC WebCam type: USB driver: uvcvideo
    bus-ID: 1-5:3 chip-ID: 0bda:58d1
  Display: server: X.Org v: 1.20.11 driver: X: loaded: modesetting
    unloaded: fbdev,vesa gpu: i915 resolution: 1920x1080~60Hz
  OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.3.5
    direct render: Yes
Network:
  Device-1: Intel Wireless 8260 driver: iwlwifi v: kernel pcie:
    speed: 2.5 GT/s lanes: 1 bus-ID: 02:00.0 chip-ID: 8086:24f3
  IF: wlan0 state: down mac: <filter>
  Device-2: Intel Bluetooth wireless interface type: USB driver: btusb
    bus-ID: 1-8:4 chip-ID: 8087:0a2b
  Device-3: ASIX AX88179 Gigabit Ethernet type: USB driver: ax88179_178a
    bus-ID: 2-1:2 chip-ID: 0b95:1790
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 238.47 GiB used: 6.1 GiB (2.6%)
Info:
  Processes: 165 Uptime: 5m Memory: 7.66 GiB used: 870.2 MiB (11.1%)
  Init: runit v: N/A runlevel: 2 Compilers: gcc: 10.2.1 alt: 10 Packages:
  apt: 1347 Shell: fish v: 3.1.2 running-in: kitty inxi: 3.3.19

[Member techore]

Happy Friday to you too.

On a test laptop using beta3 of antiX 22 dwm spin. There is going to be a beta4 but if I stop adding more features beta4 should be the last beta.

System:
  Kernel: 5.10.142-antix.2-amd64-smp arch: x86_64 bits: 64 compiler: gcc
    v: 10.2.1 Desktop: dwm v: 6.4 dm: startx
    Distro: antiX-22-runit_x64-core Grup Yorum 18 October 2022
    base: Debian GNU/Linux 11 (bullseye)
Machine:
  Type: Laptop System: ASUSTeK product: G750JX v: 1.0 serial: <filter>
  Mobo: ASUSTeK model: G750JX v: 1.0 serial: <filter>
    UEFI: American Megatrends v: G750JX.208 date: 08/19/2013
Battery:
  ID-1: BAT0 charge: 21.2 Wh (39.8%) condition: 53.3/89.2 Wh (59.8%)
    volts: 15.1 min: 15.1 model: ASUSTeK G750-59 serial: N/A status: charging
CPU:
  Info: quad core model: Intel Core i7-4700HQ bits: 64 type: MT MCP
    arch: Haswell rev: 3 cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
  Speed (MHz): avg: 2534 high: 3139 min/max: 800/3400 cores: 1: 2402
    2: 2666 3: 2395 4: 2395 5: 2488 6: 3139 7: 2395 8: 2395 bogomips: 38315
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: NVIDIA GK106M [GeForce GTX 770M] vendor: ASUSTeK driver: nvidia
    v: 390.154 arch: Kepler pcie: speed: 8 GT/s lanes: 16 bus-ID: 01:00.0
    chip-ID: 10de:11e0
  Device-2: IMC Networks USB2.0 UVC HD Webcam type: USB driver: uvcvideo
    bus-ID: 3-7:4 chip-ID: 13d3:5188
  Display: server: X.Org v: 1.20.11 driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa alternate: nv gpu: nvidia
    resolution: 1920x1080~60Hz
  OpenGL: renderer: GeForce GTX 770M/PCIe/SSE2 v: 4.6.0 NVIDIA 390.154
    direct render: Yes
Network:
  Device-1: Broadcom BCM4352 802.11ac Wireless Network Adapter
    vendor: AzureWave driver: wl v: kernel pcie: speed: 5 GT/s lanes: 1
    bus-ID: 03:00.0 chip-ID: 14e4:43b1
  IF: wlan0 state: down mac: <filter>
  Device-2: Qualcomm Atheros QCA8171 Gigabit Ethernet vendor: ASUSTeK
    driver: alx v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: d000
    bus-ID: 04:00.0 chip-ID: 1969:10a1
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 718.79 GiB used: 5.05 GiB (0.7%)
Info:
  Processes: 202 Uptime: 8m Memory: 31.28 GiB used: 1.09 GiB (3.5%)
  Init: runit v: N/A runlevel: 2 Compilers: gcc: 10.2.1 alt: 10 Packages:
  apt: 1159 Shell: fish v: 3.1.2 running-in: kitty inxi: 3.3.19

[Member stevesr0]

Hi olsztyn,

Thanks for reply and for searching my packages <g>.

No, the pipewire packages were already installed. (The latest nosystemd versions only!)

(Before installing the script, pipewire only worked with libelogind0 installed.)

Now, WITHOUT libelogind0 installed, I just run the script before starting Xorg with startx.

Pipewire, wireplumber and pavucontrol are all working automagically.

I don’t have to run the EXPORT part.

stevesr0

P.S.

My next step is to get a liveusb of this current install (without libelogind0) and see if Pipewire works smoothly on my other two computers.

[Member stevesr0]

Thank you Brian M. (I don’t know your preference in the use of your name – as there might be other “Brian” members, I figured that your last initial might be more specific; happy to change to what you like.)

I have produced a live usb that is an apparent clone of my Fujitsu antiX Sid install. I have tried running it on all three of my computers. It booted immediately to a terminal login (as it is supposed to) on all three computers. On the Fujitsu and Lenovo Yoga, I had no trouble starting Xorg using startx. The first time I tried launching on my newest computer, which has both an integrated intel GPU and an Nvidia GPU, it ended with a connection refused error.

On my second boot, it went as smoothly as with the other two computers.

So superficially, this might work on a variety of computers!

Parenthetically, since this liveusb DOES have libelogind0 installed, Pipewire works. This was the first time I looked at the “new” computer’s audio settings in Pipewire and they DID reflect the hardware on that machine, which is different from the Fujitsu. A little wow moment. (I will include libelogind0 so people can see if Pipewire works with this iso, assuming the iso boots ok to X for them. They can then try removing libelogind0 and see if they can find a way to run Pipewire without it.)

My plan (pending comments from y’alls) is to strip off the files from my home directory and other personal stuff and generate a snapshot from THAT running system and use live-usb-maker to produce an iso I can post somewhere. A family member is being discharged from the hospital soon and I will be visiting and trying to help out, so there may be a delay.

stevesr0
————————————————————————————-
**As an aside, I have noticed a number of posts by folks seeking to use Pipewire. I think it would be neat to “build” a team to (as Brian suggested) look at the Pipewire source code in order to understand where the various problems might be in trying to use it in antiX. Some issues I have heard of include setting a runtime directory as an environment variable (in the absence of systemd), dependencies declared in the source code that require systemd, and issues with the programs used for seat management when running Xorg (including lack of support for Wireplumber?). If several people were interested in looking into these and educating each other, a successful general approach to Pipewire without systemd on antiX might be developed for the benefit of all who might want to try Pipewire. Especially if a newer version could be backported to stable. And of course, the directions would have to include how not to update to incompatible versions <g>.

stevesr0

[Member techore]

On Asus N705U using antiX 22 dwm spin beta1, drinking coffee, and working through the creation of a control center in preparation for beta2. Hoping to get this done this year, but it is taking longer than expected. Isn’t that usually the case?

inxi -v3xz

System:
  Kernel: 5.10.142-antix.2-amd64-smp arch: x86_64 bits: 64 compiler: gcc
    v: 10.2.1 Desktop: dwm v: 6.4 dm: startx
    Distro: antiX-22-runit_x64-core Grup Yorum 18 October 2022
    base: Debian GNU/Linux 11 (bullseye)
Machine:
  Type: Laptop System: ASUSTeK product: X705UDR v: 1.0 serial: <filter>
  Mobo: ASUSTeK model: X705UDR v: 1.0 serial: <filter>
    UEFI-[Legacy]: American Megatrends v: X705UDR.317 date: 04/17/2019
Battery:
  ID-1: BAT0 charge: 45.8 Wh (98.9%) condition: 46.3/42.1 Wh (110.0%)
    volts: 11.5 min: 11.5 model: ASUSTeK ASUS Battery serial: N/A
    status: not charging
CPU:
  Info: quad core model: Intel Core i7-8550U bits: 64 type: MT MCP
    arch: Coffee Lake rev: A cache: L1: 256 KiB L2: 1024 KiB L3: 8 MiB
  Speed (MHz): avg: 3917 high: 4001 min/max: 400/4000 cores: 1: 3913
    2: 3742 3: 3897 4: 3913 5: 3967 6: 4001 7: 3950 8: 3958 bogomips: 31999
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel UHD Graphics 620 vendor: ASUSTeK driver: i915 v: kernel
    arch: Gen9.5 ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 00:02.0
    chip-ID: 8086:5917
  Device-2: NVIDIA GP107M [GeForce GTX 1050 Mobile] driver: N/A
    arch: Pascal pcie: speed: Unknown lanes: 63 bus-ID: 01:00.0
    chip-ID: 10de:1c8d
  Device-3: IMC Networks USB2.0 VGA UVC WebCam type: USB driver: uvcvideo
    bus-ID: 1-5:2 chip-ID: 13d3:5a01
  Display: server: X.Org v: 1.20.11 driver: X: loaded: modesetting
    unloaded: fbdev,vesa gpu: i915 resolution: 1920x1080~60Hz
  OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2)
    v: 4.6 Mesa 20.3.5 direct render: Yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1
    port: d000 bus-ID: 02:00.0 chip-ID: 10ec:8168
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Realtek RTL8822BE 802.11a/b/g/n/ac WiFi adapter
    vendor: AzureWave driver: rtw_8822be v: N/A pcie: speed: 2.5 GT/s lanes: 1
    port: c000 bus-ID: 03:00.0 chip-ID: 10ec:b822
  IF: wlan0 state: down mac: <filter>
  IF-ID-1: virbr0 state: down mac: <filter>
Drives:
  Local Storage: total: 1.14 TiB used: 7.89 GiB (0.7%)
Info:
  Processes: 198 Uptime: 41m Memory: 15.52 GiB used: 2.62 GiB (16.9%)
  Init: runit v: N/A runlevel: 2 Compilers: gcc: 10.2.1 alt: 10 Packages:
  apt: 1201 Shell: fish v: 3.1.2 running-in: kitty inxi: 3.3.19

[Member kelsoo]

yes. well it was already installed when I finally tried. Before that I installed

gpm

xserver-xorg-video-intel (atom)
xserver-xorg-input-evdev
xserver-xorg-input-mouse

But like I said startx as root and everythings working, mouse and keyboard all fine. Seem like a permissions thing somewhere

#typo

• This reply was modified 5 months ago by kelsoo.

antiX22 core, notion window manager, startx as root and everything’s working dandy. Start as user zilch. gpm installed and console works fine. I vaguely recall Debian may have done something about root logging in but no Idea if that affects antiX. default groups, clues appreciated.

• This topic was modified 5 months ago by kelsoo.

[Anonymous]

@olsztyn,

about your ‘startx’ problem
For starters, you should be able to do it with the command
/usr/bin/startx
try.

As for their x61,
have you tried the kernel parameter ‘nomodeset‘ ?

[Member techore]

Troubleshooting a bug with my antiX spin on an older Asus laptop. No closer to fixing the bug, but everything else seems to be working from the spin ISO.

inxi -v3xz
System:
  Kernel: 5.10.142-antix.2-amd64-smp arch: x86_64 bits: 64 compiler: gcc
    v: 10.2.1 Desktop: dwm v: 6.4 dm: startx
    Distro: antiX-22-runit_x64-core Grup Yorum 18 October 2022
    base: Debian GNU/Linux 11 (bullseye)
Machine:
  Type: Laptop System: ASUSTeK product: G750JX v: 1.0 serial: <filter>
  Mobo: ASUSTeK model: G750JX v: 1.0 serial: <filter>
    BIOS: American Megatrends v: G750JX.208 date: 08/19/2013
Battery:
  ID-1: BAT0 charge: 54.1 Wh (100.0%) condition: 54.1/89.2 Wh (60.7%)
    volts: 15.1 min: 15.1 model: ASUSTeK G750-59 serial: N/A status: full
CPU:
  Info: quad core model: Intel Core i7-4700HQ bits: 64 type: MT MCP
    arch: Haswell rev: 3 cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
  Speed (MHz): avg: 2396 high: 2397 min/max: 800/3400 cores: 1: 2395
    2: 2396 3: 2395 4: 2395 5: 2396 6: 2397 7: 2397 8: 2397 bogomips: 38312
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: NVIDIA GK106M [GeForce GTX 770M] vendor: ASUSTeK driver: nvidia
    v: 390.154 arch: Kepler pcie: speed: 8 GT/s lanes: 16 bus-ID: 01:00.0
    chip-ID: 10de:11e0
  Device-2: IMC Networks USB2.0 UVC HD Webcam type: USB driver: uvcvideo
    bus-ID: 3-7:4 chip-ID: 13d3:5188
  Display: server: X.Org v: 1.20.11 driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa alternate: nv gpu: nvidia
    resolution: 1920x1080~60Hz
  OpenGL: renderer: GeForce GTX 770M/PCIe/SSE2 v: 4.6.0 NVIDIA 390.154
    direct render: Yes
Network:
  Device-1: Broadcom BCM4352 802.11ac Wireless Network Adapter
    vendor: AzureWave driver: wl v: kernel pcie: speed: 5 GT/s lanes: 1
    bus-ID: 03:00.0 chip-ID: 14e4:43b1
  IF: wlan0 state: down mac: <filter>
  Device-2: Qualcomm Atheros QCA8171 Gigabit Ethernet vendor: ASUSTeK
    driver: alx v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: d000
    bus-ID: 04:00.0 chip-ID: 1969:10a1
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 704.24 GiB used: 5.11 GiB (0.7%)
Info:
  Processes: 191 Uptime: 6m Memory: 31.28 GiB used: 1.1 GiB (3.5%)
  Init: runit v: N/A runlevel: 2 Compilers: gcc: 10.2.1 alt: 10 Packages:
  apt: 1109 Shell: fish v: 3.1.2 running-in: kitty inxi: 3.3.19

[Member olsztyn]

Reporting progress. Or rather the lack of it:
– Installed Sysvinit version of SID ISO and performed dist-upgrade as before
– Installed basic components following the same process as outlined above by @Christophe.

Result: Execution of startx results in the same failure as for Runit version of SID Core ISO.
Looks like I am still missing something to get over this hurdle. The good news is that there seems no difference between behavior of Sysvinit and Runit. Both result in the same failure following the same install sequence.
Therefore it must be something missing, step I still need to get over this hurdle.
Both were installed on the same model machines – Thinkpad X61. It could be something related to this machine model too. I will try on a different model machine, just to nail down this…
In the interim I want to thank for all the helpful advice I received. It is a learning process for me…

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Moderator christophe]

andyprough wrote:

Up
0
I’m assuming you created an ~/.xinitrc file with the “exec jwm” or whatever window manager line to instruct startx what to do.

From my experience, if you only have one wm installed, startx will use it automatically (at least it works that way with jwm).

It’s probably a good way to do it (andyprough’s suggestion), so you can change it up in the future.

confirmed antiX frugaler, since 2019

[Moderator Brian Masinick]

andyprough wrote:

I’m assuming you created an ~/.xinitrc file with the “exec jwm” or whatever window manager line to instruct startx what to do.

One thing I didn’t note is that I did not use runit or Sid last night with my core installation. So it could be one of those like you said.

Yeah, I don’t know about that either. I’ve built antiX Core many times in the past, but with my current network availability, it’s difficult to find ANY wired network solutions around me anymore; therefore I generally need a setup with that built in; otherwise I’m forced to hack my solutions (which I’ve done too), but that takes too much time to do very often (unless I build tools to copy ALL of the stuff I need, and I haven’t done that).

I am, however, using a runit version of antiX 22 right now on my HP-14, and in fact, I had to hack in some firmware, a different kernel, and a few modules to get this one working too.
So yes, it CAN be done, but it takes work, and the specifics will VARY from system to system.

In my case, I needed a newer kernel to support my hardware; brought that in, didn’t work. Found that my wireless firmware was missing one file, brought the missing file in; STILL no go. So I went to MX Linux, which I believe was one of the distros working here, looked at everything it had in place, and literally copied every /lib/module, kernel related config and module files, anything else I could spot that interacted or mentioned the kernel or the wireless firmware I was using, and finally got it working; that’s a LOT of work that required hours of research. On top of that, REGULAR MX Linux doesn’t work either; I have to have the AHS (Advanced Hardware Support) stuff for newer images in order to get it working. PCLinuxOS, MX Linux AHS, and openSUSE have these; I got siduction working too; don’t remember if it worked immediately or if I had to do the same prep; seems to me I had to do it to something else; anyway, once I did it on this hardware, it was easier to copy it from a working system, but these kinds of issues are not exactly “portable” to fix; they can differ slightly for each hardware platform in question; some may work out of the box, others need tweaks.

That’s one positive of my Dell Inspiron 5558; it has always worked with my hardware AND software!

--
Brian Masinick

[Member andyprough]

I’m assuming you created an ~/.xinitrc file with the “exec jwm” or whatever window manager line to instruct startx what to do.

One thing I didn’t note is that I did not use runit or Sid last night with my core installation. So it could be one of those like you said.