MX Linux Forum

Posted: **Wed Feb 01, 2023 11:17 am**

I have downloaded MX-21.3_x64 KDE
Flashed it using balena etcher,
and tried installing on an "empty" PC, just usb live stick and clean SSD.

I have set lang and locale OK

followed by:
search for boot device
run live scripts
start init
and... nothing, just black screen

so, used Alt+F1

and... I am still waiting for /dev to be fully populated

How long should I be waiting, please?
Is there anything else I can do?
Have I missed anything?

edit: additional info
PC is directly connected/wired into router (i.e. not using wi-fi)

Moderator: images changed to links, please read the forum rules

Posted: **Wed Feb 01, 2023 11:57 am**

Balena Etcher doesn't always work properly with MX's ISOs. You will have a much better chance of success with Rufus on Windows, MX's own Live USB Maker or even Ventoy.

Posted: **Wed Feb 01, 2023 12:00 pm**

@j2mcgreg thanks for that
I have dusted off an old Win10 PC and will have a go with Rufus.
Shame, that I have to use Win to do it...

Will also try Liveusbmaker appimage

Posted: **Wed Feb 01, 2023 12:06 pm**

bambuko wrote: Wed Feb 01, 2023 12:00 pm @j2mcgreg thanks for that
I have dusted off an old Win10 PC and will have a go with Rufus.
Shame, that I have to use Win to do it...

Will also try Liveusbmaker appimage

One tip when using Rufus: if your target computer is UEFI capable, configure Rufus to use GPT.

Posted: **Wed Feb 01, 2023 12:27 pm**

Tried again with fresh live usb created using Live USB Maker from MX
and ... still exactly the same.
Tried both usb3 and usb2

very dissapointing

Posted: **Wed Feb 01, 2023 12:34 pm**

If you haven't (and if there is such an option):

Disable secure boot in Bios.

Disable "Fast Startup" in Windows.

Use the parameter

Code: Select all

nomodeset

if still not, use

Code: Select all

bp=b9

Posted: **Wed Feb 01, 2023 12:38 pm**

If it's a Bios pc , you can type the parameter into the white area then go on boot (press Enter),
If it's Uefi , select "Advanced Options"..

(Screens are different)

Posted: **Wed Feb 01, 2023 12:54 pm**

Thanks @Huckleberry Finn
It is UEFI DualBios machine
Fast boot is disabled
Boot Mode is UEFI and Legacy
Secure boot has always been disabled
There no Windows (it's an empty machine)

Not sure I follow your "parameter" instructions (sorry - being thick and slow...)

Just to eliminate it I will try now Rufus

Posted: **Wed Feb 01, 2023 12:59 pm**

It’s not likely the usb creation software if etcher is in use.

More likely some hardware compatibility issue. Not sure what though. Maybe getting hung up finding an internal drive or something. By the time you get to /dev populating the live init system is done and the system is in process of booting.

Raid disks?

Posted: **Wed Feb 01, 2023 1:02 pm**

Ok, I thought you already tried Rufus after that, then it was still the same.

That one is one of the officially recommended ways, how to prepare the usb.

Posted: **Wed Feb 01, 2023 1:04 pm**

dolphin_oracle wrote: Wed Feb 01, 2023 12:59 pm Raid disks?

Thank you @dolphin_oracle
I use NAS for my data and it is connected to the PC via router.
I will try with it switched off (just in case - it has never caused any problems before...)

Posted: **Wed Feb 01, 2023 1:29 pm**

Latest...

using Rufus created live usb (used GPT option), NAS turned OFF
and still NBG

Looking at the web, it seems to be fairly common and peculiarly Debian problem?
Trouble is, that there doesn't seem to be one solution - they are all different...
It shouldn't be that complicated

Posted: **Wed Feb 01, 2023 2:41 pm**

Images changed to links, please read the forum rules, thanks.

Posted: **Wed Feb 01, 2023 2:47 pm**

Eadwine Rose wrote: Wed Feb 01, 2023 2:41 pm ...please read the forum rules...

Thank you, adjusted image sizes to acceptable as per the rules

Posted: **Wed Feb 01, 2023 2:48 pm**

The bottleneck could also be the brand of USB drive being used. They are not all created equally well.

Posted: **Wed Feb 01, 2023 2:54 pm**

All my sticks are Kingston, so unless I buy different one just to try... I am stuck

Posted: **Wed Feb 01, 2023 3:17 pm**

bambuko wrote: Wed Feb 01, 2023 2:47 pm
Eadwine Rose wrote: Wed Feb 01, 2023 2:41 pm ...please read the forum rules...
Thank you, adjusted image sizes to acceptable as per the rules

Thanks :)

Posted: **Wed Feb 01, 2023 3:21 pm**

We have some progress... hurrah

I am getting past the
waiting for /dev to be fully populated

In amongst many suggestion on interweb, there was soemone who sorted his problems by adding failsafe to Boot options.
Don't ask me how or why, but someone here might know?

It still means nothing, because now, I eventually end up with black screen again (but I do recall seeing something about it in the manual?)

Posted: **Wed Feb 01, 2023 3:33 pm**

You never mentioned the make and model of the computer involved. Could you tell us now?

Posted: **Wed Feb 01, 2023 3:46 pm**

@j2mcgreg

I am sorry. It is my own make and model

built with:
Quad-Core i504690K CPU @3.50GHz
and (unfortunately) NVIDIA GeForce GTX 1650 SUPER
15.5 GiB memory

and now for the good news

I got as far as seeing KDE screen
by using failsafe and nomodeset
It still looks crap but I am sure it will be possible to improve (with your help, I guess)

Posted: **Wed Feb 01, 2023 3:59 pm**

Since you got that far, you could try using the Nvidia Driver installer in MX Tools to install the proprietary Nvidia driver.

Posted: **Wed Feb 01, 2023 4:09 pm**

Yes, I do expect headache with NVIDIA drivers (have been there before

)
If it wasn't for the money I'd change graphic card (and I might still do it) but in the meantime new driver is job No1
before anything else.

Posted: **Wed Feb 01, 2023 7:02 pm**

As expected... the whole thing is right PITA,
I have now tried update NVIDIA drivers twice, with no success.
Now removed and the only way I can boot installed (not live usb) MX is by setting following boot parameters:
failsafe and nomodeset

Clearly this is not a solution, just a bodge
I need help, please...

Code: Select all

Graphics:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics vendor: Gigabyte driver: N/A alternate: 1915 bus-ID: 00:02.0 chip-ID: 8086:0412 class-ID: 0300
Device-2: NVIDIA TU116 [GeForce GTX 1650 SUPER] driver: N/A alternate: nouveau
bus-ID: 01:00.0 chip-ID: 10de: 2187 class-ID: 0300 
Display: x11 server: X.Org 1.20.14 compositor: kwin_x11 driver: loaded: nouveau, vesa 
unloaded: fbdev, modesetting alternate: nv display-ID: :0 screens: 1 Screen-1: 0 s-res: 1024x768 s-dpi: 96 s-size: 271x203mm (10.7x8.0")
s-diag: 339mm (13.3")
Monitor-1: default res: 1024x768
OpenGL: renderer: llvmpipe (LLVM 14.0.5 256 bits) v: 4.5 Mesa 22.0.5 direct render: Yes

Posted: **Wed Feb 01, 2023 7:09 pm**

Boot like that, (in fact that's why I typed "Advanced Options" for uefi as it (the option) already appears there as "failsafe nomodeset" for I thought you'd guess) then go on install MX. Later you can install the Nvidia driver when booted to installed one.

Or, have a try if it boots with no issues with the regular MX (Xfce).

Posted: **Wed Feb 01, 2023 7:15 pm**

@Huckleberry Finn
That's exactly what I have done
I am talking in my last post about installed (not live usb)
MX is already installed.
I have installed best available NVIDIA driver twice, every time ending up in total mess with black screen etc

Posted: **Wed Feb 01, 2023 7:17 pm**

Ok, then just:

Code: Select all

sudo rm /etc/X11/xorg.conf

Reboot

Also post QSI (see my signature below).

Posted: **Wed Feb 01, 2023 7:19 pm**

Or just access the installed MX's partition via live session (using the file manager simply), then delete the /etc/X11/xorg.conf .

(If there is of course, not the directory or others, just the file xorg.conf )

Posted: **Wed Feb 01, 2023 7:30 pm**

That's not the full QSI.

Till then:

Drivers are not loaded cause failsafe etc. are still in your boot parameters. Remove both failsafe (and) nomodeset in "Kernel Parameters" box in "MX Boot Options".

Posted: **Wed Feb 01, 2023 7:34 pm**

... I wish we knew those specs a bit earlier:

On live session just try (no others like nomodeset etc..)

Code: Select all

vcard=off

if still not:

Code: Select all

vcard=menu

then select Intel when it asks.

(You can simply press E then type after ... quiet splash ... and press F10 to go on boot)

Posted: **Wed Feb 01, 2023 7:35 pm**

I have posted pertinent (graphics) part of QSI - I will add full one
xorg.conf is already removed (after failed NVIDIA driver install) as per MX wiki
I have checked kernel parameters and nomodeset is not there - I have to set it manually (edit at boot) every time I boot, to be able to boot at all

Posted: **Wed Feb 01, 2023 7:43 pm**

Full QSI:
and like I said before - nomodeset is there, not because I didn't delete it, but because I had to edit it at boot to be able to boot at all.

Code: Select all

System:    Kernel: 6.0.0-6mx-amd64 [6.0.12-1~mx21+1] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/boot/vmlinuz-6.0.0-6mx-amd64 
           root=UUID=<filter> ro quiet splash nomodeset 
           Desktop: KDE Plasma 5.20.5 wm: kwin_x11 vt: 7 dm: SDDM 
           Distro: MX-21.3_KDE_x64 Wildflower January 15  2023 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop Mobo: Gigabyte model: Z97M-D3H v: x.x serial: <filter> 
           BIOS: American Megatrends v: F8 date: 09/18/2015 
CPU:       Info: Quad Core model: Intel Core i5-4690K bits: 64 type: MCP arch: Haswell family: 6 
           model-id: 3C (60) stepping: 3 microcode: 28 cache: L2: 6 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28001 
           Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 1337 2: 1300 3: 1000 4: 1300 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled 
           Type: mds mitigation: Clear CPU buffers; SMT disabled 
           Type: meltdown mitigation: PTI 
           Type: mmio_stale_data status: Unknown: No mitigations 
           Type: retbleed status: Not affected 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW, STIBP: disabled, 
           RSB filling, PBRSB-eIBRS: Not affected 
           Type: srbds mitigation: Microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
           vendor: Gigabyte driver: N/A alternate: i915 bus-ID: 00:02.0 chip-ID: 8086:0412 
           class-ID: 0300 
           Device-2: NVIDIA TU116 [GeForce GTX 1650 SUPER] driver: N/A alternate: nouveau 
           bus-ID: 01:00.0 chip-ID: 10de:2187 class-ID: 0300 
           Display: x11 server: X.Org 1.20.14 compositor: kwin_x11 driver: loaded: nouveau,vesa 
           unloaded: fbdev,modesetting alternate: nv display-ID: :0 screens: 1 
           Screen-1: 0 s-res: 1024x768 s-dpi: 96 s-size: 271x203mm (10.7x8.0") 
           s-diag: 339mm (13.3") 
           Monitor-1: default res: 1024x768 
           OpenGL: renderer: llvmpipe (LLVM 14.0.5 256 bits) v: 4.5 Mesa 22.0.5 direct render: Yes 
Audio:     Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel 
           v: kernel bus-ID: 00:03.0 chip-ID: 8086:0c0c class-ID: 0403 
           Device-2: Intel 9 Series Family HD Audio vendor: Gigabyte driver: snd_hda_intel 
           v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8ca0 class-ID: 0403 
           Device-3: NVIDIA TU116 High Definition Audio driver: snd_hda_intel v: kernel 
           bus-ID: 01:00.1 chip-ID: 10de:1aeb class-ID: 0403 
           Device-4: JMTek LLC. USB PnP Audio Device type: USB 
           driver: hid-generic,snd-usb-audio,usbhid bus-ID: 2-9:7 chip-ID: 0c76:161f 
           class-ID: 0300 
           Sound Server-1: ALSA v: k6.0.0-6mx-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte 
           driver: r8169 v: kernel port: d000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 111.79 GiB used: 8.19 GiB (7.3%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SHFS37A120G size: 111.79 GiB 
           block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> 
           rev: BBF0 scheme: MBR 
Partition: ID-1: / raw-size: 106.16 GiB size: 103.93 GiB (97.90%) used: 8.19 GiB (7.9%) fs: ext4 
           dev: /dev/sda1 maj-min: 8:1 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 5.62 GiB used: 0 KiB (0.0%) priority: -2 
           dev: /dev/sda2 maj-min: 8:2 
Sensors:   System Temperatures: cpu: 29.8 C mobo: 27.8 C 
           Fan Speeds (RPM): N/A 
Repos:     Packages: note: see --pkg apt: 2364 lib: 1343 flatpak: 0 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bullseye main non-free
           2: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bullseye ahs
Info:      Processes: 210 Uptime: 4m wakeups: 1 Memory: 15.47 GiB used: 1 GiB (6.5%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 10.2.1 
           alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06 
Boot Mode: BIOS (legacy, CSM, MBR)

Posted: **Wed Feb 01, 2023 7:47 pm**

Ok, one might need that on live session but it's weird if it doesn't boot without that now.

If it's just a black screen without it:

Code: Select all

i915.invert_brightness=1

(without others again, no failsafe, no nomodeset)

Posted: **Wed Feb 01, 2023 7:49 pm**

yes, I add this manually before boot

Posted: **Wed Feb 01, 2023 7:53 pm**

Ok, just try 2 things: On live session: vcard=off and on the installed one invert... as you do temporarily, press E ...

Posted: **Wed Feb 01, 2023 8:00 pm**

what was the nvidia install failure? did the install fail or did the driver just not work?

you have two graphics parts listed. I presume your monitor is plugged into the nvidia card. is it possible to disable the integrated gpu in your system bios?

Posted: **Wed Feb 01, 2023 8:11 pm**

@dolphin_oracle
no, the install was fine (and declared success) but the driver didn't work.
I have followed instructions here:
https://mxlinux.org/wiki/hardware/nvidi ... -recovery/
by getting back to console and tidying up everything

yes, monitor is plugged into nvidia card.
don't know about disabling integrated one?
(it doesn't cause problems with other distros...)

Posted: **Wed Feb 01, 2023 8:12 pm**

Huckleberry Finn wrote: Wed Feb 01, 2023 7:53 pm Ok, just try 2 things: On live session: vcard=off and on the installed one invert... as you do temporarily, press E ...

I tried invert on installed one - didn't make any difference
still black screen with blinking cursor top LH corner

will try live session and report back

Posted: **Wed Feb 01, 2023 8:23 pm**

Huckleberry Finn wrote: Wed Feb 01, 2023 7:53 pm .....On live session: vcard=off

YES, YES

my monitor is recognised, display is OK

I will try installing with that?

Posted: **Wed Feb 01, 2023 8:46 pm**

Thank you for your patience everybody!
and in particular @Huckleberry Finn

Works perfectly when installed without any ffuf with NVIDIA drivers...

Posted: **Wed Feb 01, 2023 10:33 pm**

Posted: **Thu Feb 02, 2023 3:50 am**

@Huckleberry Finn
I would love to know and understand what has happened and why this particular booting parameter has worked?
I tried searching but so far haven't found anything....

only this so far:
https://www.forum.mxlinux.org/viewtopic ... 4&p=710944

Posted: **Thu Feb 02, 2023 5:46 am**

bambuko wrote: Thu Feb 02, 2023 3:50 am I would love to know and understand what has happened and why this particular booting parameter has worked?

Please post QSI "Quick System Info", which may help to see what system you have.

Posted: **Thu Feb 02, 2023 5:49 am**

He already gave it in this post in the thread:

https://forum.mxlinux.org/viewtopic.php ... 74#p711874

Posted: **Thu Feb 02, 2023 5:50 am**

Eadwine Rose wrote: Thu Feb 02, 2023 5:49 am He already gave it in this post in the thread:

https://forum.mxlinux.org/viewtopic.php ... 74#p711874

Thanks to long thread I guess.

+++EDIT+++
Perhabs, post QSI from LiveUSB with the parameter which worked to get booted,
so we see what was loaded.
Thanks

Posted: **Thu Feb 02, 2023 8:22 am**

@bambuko Shortly:

With MX 19 it's a new feature: Detect double-cards:

vcard=on => Detect hybrid graphics then disable the non-Intel video drivers (This one is the default)
vcard=off => Disable video card detection
vcard=menu => Show video card options (Then you select Intel or Nvidia (or whatever) and mostly Intel works)

However, as in that thread and in many previous threads (also in other languages forums) the one that almost always works is vcard=off (that's why I said "I wish we knew the specs earlier" cause I would directly tell to try that one (when I see it's not a single-card machine) rather than wasting time with nomodeset etc..) .. therefore my humble suggestion (on this opportunity) to MX Team is make "off" the default.

Posted: **Thu Feb 02, 2023 12:47 pm**

fehlix wrote: Thu Feb 02, 2023 5:50 am...post QSI from LiveUSB with the parameter which worked to get booted,
so we see what was loaded...

sorry for the delay (I am still finding my way round MX

)
here it is:

Code: Select all

System:    Kernel: 6.0.0-6mx-amd64 [6.0.12-1~mx21+1] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: quiet splasht nosplash vcard=off 
           Desktop: KDE Plasma 5.20.5 wm: kwin_x11 vt: 7 dm: SDDM 
           Distro: MX-21.3_KDE_x64 Wildflower January 15  2023 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop Mobo: Gigabyte model: Z97M-D3H v: x.x serial: <filter> 
           BIOS: American Megatrends v: F8 date: 09/18/2015 
CPU:       Info: Quad Core model: Intel Core i5-4690K bits: 64 type: MCP arch: Haswell family: 6 
           model-id: 3C (60) stepping: 3 microcode: 1C cache: L2: 6 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 27999 
           Speed: 1000 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 1000 2: 1000 3: 1000 4: 900 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled 
           Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled 
           Type: meltdown mitigation: PTI 
           Type: mmio_stale_data status: Unknown: No mitigations 
           Type: retbleed status: Not affected 
           Type: spec_store_bypass status: Vulnerable 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 
           mitigation: Retpolines, STIBP: disabled, RSB filling, PBRSB-eIBRS: Not affected 
           Type: srbds status: Vulnerable: No microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
           vendor: Gigabyte driver: i915 v: kernel bus-ID: 00:02.0 chip-ID: 8086:0412 
           class-ID: 0300 
           Device-2: NVIDIA TU116 [GeForce GTX 1650 SUPER] driver: nouveau v: kernel 
           bus-ID: 01:00.0 chip-ID: 10de:2187 class-ID: 0300 
           Display: x11 server: X.Org 1.20.14 compositor: kwin_x11 driver: loaded: modesetting 
           unloaded: fbdev,vesa display-ID: :0 screens: 1 
           Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.7x15.0") 
           s-diag: 777mm (30.6") 
           Monitor-1: DVI-D-1 res: 2560x1440 hz: 60 dpi: 109 size: 597x336mm (23.5x13.2") 
           diag: 685mm (27") 
           OpenGL: renderer: NV168 v: 4.3 Mesa 22.0.5 direct render: Yes 
Audio:     Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel 
           v: kernel bus-ID: 00:03.0 chip-ID: 8086:0c0c class-ID: 0403 
           Device-2: Intel 9 Series Family HD Audio vendor: Gigabyte driver: snd_hda_intel 
           v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8ca0 class-ID: 0403 
           Device-3: NVIDIA TU116 High Definition Audio driver: snd_hda_intel v: kernel 
           bus-ID: 01:00.1 chip-ID: 10de:1aeb class-ID: 0403 
           Device-4: JMTek LLC. USB PnP Audio Device type: USB 
           driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-9:7 chip-ID: 0c76:161f 
           class-ID: 0300 
           Sound Server-1: ALSA v: k6.0.0-6mx-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte 
           driver: r8169 v: kernel port: d000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 3.76 GiB used: 2.34 GiB (62.3%) 
           ID-1: /dev/sda maj-min: 8:0 type: USB vendor: Kingston model: DataTraveler 2.0 
           size: 3.76 GiB block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> 
           rev: 1.00 scheme: MBR 
           SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure? 
Swap:      Alert: No swap data was found. 
Sensors:   System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nouveau temp: 29.0 C 
           Fan Speeds (RPM): N/A 
Repos:     Packages: note: see --pkg apt: 2296 lib: 1284 flatpak: 0 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ bullseye main non-free
           2: deb http://mxrepo.com/mx/repo/ bullseye ahs
Info:      Processes: 224 Uptime: 1m wakeups: 1 Memory: 15.47 GiB used: 1.09 GiB (7.0%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: N/A 
           alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06 
Boot Mode: BIOS (legacy, CSM, MBR)

Posted: **Thu Feb 02, 2023 12:51 pm**

As a conclusion:

You disabled the "Detect hybrid graphics then disable the non-Intel video drivers"

and both drivers (i915 and Nouveau (+ modesetting)) were loaded as it should be (rather than Intel only etc.) :

Graphics:

Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
vendor: Gigabyte driver: i915 v: kernel bus-ID: 00:02.0 chip-ID: 8086:0412
class-ID: 0300

Device-2: NVIDIA TU116 [GeForce GTX 1650 SUPER] driver: nouveau v: kernel
bus-ID: 01:00.0 chip-ID: 10de:2187 class-ID: 0300

Display: x11 server: X.Org 1.20.14 compositor: kwin_x11 driver: loaded: modesetting
unloaded: fbdev,vesa display-ID: :0 screens: 1
...

OpenGL: renderer: NV168 v: 4.3 Mesa 22.0.5 direct render: Yes

Posted: **Thu Feb 02, 2023 12:53 pm**

Huckleberry Finn wrote: Thu Feb 02, 2023 8:22 am ...my humble suggestion (on this opportunity) to MX Team is make "off" the default.

Thank you for the explanation.
I have missed totally the significance and confusion caused by the unused integral GPU on motherboard (as opposed to specific GPU card into which my monitor is plugged in).
I (as a humble user) support your suggestion to change vcard default.
If it wasn't for my perseverance and your help I (and few other potential users trying to install it, I guess?) would have given up and moved on quite some time ago...

Posted: **Thu Feb 02, 2023 1:00 pm**

Thank you, too for the feedback and for trying again and again :)

Posted: **Thu Feb 02, 2023 1:58 pm**

bambuko wrote: Thu Feb 02, 2023 12:47 pm
fehlix wrote: Thu Feb 02, 2023 5:50 am...post QSI from LiveUSB with the parameter which worked to get booted,
so we see what was loaded...
sorry for the delay (I am still finding my way round MX )
here it is:

OK, thanks.
If you enable

vcard=menu

and select nvidia would it boot into X?

Posted: **Thu Feb 02, 2023 2:47 pm**

fehlix wrote: Thu Feb 02, 2023 1:58 pm ...vcard=menu
and select nvidia would it boot into X?

Don't know, but will try and report back

Posted: **Thu Feb 02, 2023 3:03 pm**

OK, this is what happened:

Code: Select all

live-vcard: Video card selection
Removing file /var/lib/live-estate/vcard-mode 
Found 2 Video devices 
Found 1 Intel Video device
Detected possible Hybrid Graphies 
Video Card Menu forced
Please select a video card to use
1) Intel Xeon E3-1288 v3/4th Gen Core Processor Integrated Graphics Controller (rev 86) 
2) NVIDIA TU116 [GeForce GTX 1658 SUPER] (rev al) 
0) Quit/disable
Press <Enter> to quit
>2
Newly selected video card 
NVIDIA TU116 (GeForce GTX 1658 SUPER] (rev al) 
Setting Xorg bus-id to 0000:01:00.0 
disabling modeset for 1915 in file /lib/modprobe.d/video-card-disable.conf 
Press <Enter> to continue

and it installed perfectly OK

here the usual info:

Code: Select all

System:    Kernel: 6.0.0-6mx-amd64 [6.0.12-1~mx21+1] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/antiX/vmlinuz quiet splasht nosplash vcard=menu 
           Desktop: KDE Plasma 5.20.5 wm: kwin_x11 vt: 7 dm: SDDM 
           Distro: MX-21.3_KDE_x64 Wildflower January 15  2023 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop Mobo: Gigabyte model: Z97M-D3H v: x.x serial: <filter> 
           UEFI: American Megatrends v: F8 date: 09/18/2015 
CPU:       Info: Quad Core model: Intel Core i5-4690K bits: 64 type: MCP arch: Haswell family: 6 
           model-id: 3C (60) stepping: 3 microcode: 1C cache: L2: 6 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 27999 
           Speed: 1200 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 900 2: 900 3: 995 4: 900 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled 
           Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled 
           Type: meltdown mitigation: PTI 
           Type: mmio_stale_data status: Unknown: No mitigations 
           Type: retbleed status: Not affected 
           Type: spec_store_bypass status: Vulnerable 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 
           mitigation: Retpolines, STIBP: disabled, RSB filling, PBRSB-eIBRS: Not affected 
           Type: srbds status: Vulnerable: No microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
           vendor: Gigabyte driver: N/A alternate: i915 bus-ID: 00:02.0 chip-ID: 8086:0412 
           class-ID: 0300 
           Device-2: NVIDIA TU116 [GeForce GTX 1650 SUPER] driver: nouveau v: kernel 
           bus-ID: 01:00.0 chip-ID: 10de:2187 class-ID: 0300 
           Display: x11 server: X.Org 1.20.14 compositor: kwin_x11 driver: loaded: modesetting 
           unloaded: fbdev,vesa display-ID: :0 screens: 1 
           Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.7x15.0") 
           s-diag: 777mm (30.6") 
           Monitor-1: DVI-D-1 res: 2560x1440 hz: 60 dpi: 109 size: 597x336mm (23.5x13.2") 
           diag: 685mm (27") 
           OpenGL: renderer: NV168 v: 4.3 Mesa 22.0.5 direct render: Yes 
Audio:     Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel 
           v: kernel bus-ID: 00:03.0 chip-ID: 8086:0c0c class-ID: 0403 
           Device-2: Intel 9 Series Family HD Audio vendor: Gigabyte driver: snd_hda_intel 
           v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8ca0 class-ID: 0403 
           Device-3: NVIDIA TU116 High Definition Audio driver: snd_hda_intel v: kernel 
           bus-ID: 01:00.1 chip-ID: 10de:1aeb class-ID: 0403 
           Device-4: JMTek LLC. USB PnP Audio Device type: USB 
           driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-9:7 chip-ID: 0c76:161f 
           class-ID: 0300 
           Sound Server-1: ALSA v: k6.0.0-6mx-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte 
           driver: r8169 v: kernel port: d000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 3.76 GiB used: 2.34 GiB (62.3%) 
           ID-1: /dev/sda maj-min: 8:0 type: USB vendor: Kingston model: DataTraveler 2.0 
           size: 3.76 GiB block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> 
           rev: 1.00 scheme: MBR 
           SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure? 
Swap:      Alert: No swap data was found. 
Sensors:   System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nouveau temp: 29.0 C 
           Fan Speeds (RPM): N/A 
Repos:     Packages: note: see --pkg apt: 2296 lib: 1284 flatpak: 0 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ bullseye main non-free
           2: deb http://mxrepo.com/mx/repo/ bullseye ahs
Info:      Processes: 210 Uptime: 2m wakeups: 1 Memory: 15.47 GiB used: 1.05 GiB (6.8%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: N/A 
           alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06 
Boot Mode: UEFI
Video Tweaks:
Detected possible Hybrid Graphics

Posted: **Thu Feb 02, 2023 3:29 pm**

bambuko wrote: Thu Feb 02, 2023 3:03 pm OK, this is what happened:

Code: Select all

live-vcard: Video card selection
Removing file /var/lib/live-estate/vcard-mode 
Found 2 Video devices 
Found 1 Intel Video device
Detected possible Hybrid Graphies 
Video Card Menu forced
Please select a video card to use
1) Intel Xeon E3-1288 v3/4th Gen Core Processor Integrated Graphics Controller (rev 86) 
2) NVIDIA TU116 [GeForce GTX 1658 SUPER] (rev al) 
0) Quit/disable
Press <Enter> to quit
>2
Newly selected video card 
NVIDIA TU116 (GeForce GTX 1658 SUPER] (rev al) 
Setting Xorg bus-id to 0000:01:00.0 
disabling modeset for 1915 in file /lib/modprobe.d/video-card-disable.conf 
Press <Enter> to continue

and it installed perfectly OK

Code: Select all

Video Tweaks:
Detected possible Hybrid Graphics

OK, thanks. In case your system allows to connect a video-monitor to the integrated graphics controller
I guess the system would use this device and boot into X.
The video-card detection for Hybrid Graphics was added to the LiveSystem to avoid those laptops with hybrid-graphics would show a black screen. In your case the detection was not optimal, b/c you simply did not connect a video-device to the integrated card but the vcard-detection assumed a hybrid-card. Probably some tweaking within the vcard-detection would help in order not see such a setup as "Hybrid Graphics".
So for now, lessons learned, for anybody with an integrated graphics controller but not a Hybrid Graphics and an addtional graphics card may choose vcard boot option to select the active device.
Turning vcard off by default within the ISO-LiveSystem is not the way forward, as this would create lot of issues with hybrid-card laptops.

Posted: **Thu Feb 02, 2023 3:45 pm**

@fehlix
I would have thought that vcard=menu would be optimal and safe option covering all the angles, plus very much more informative than black screen with blinking cursor...

Anyway, my personal problem is solved, so the only question for you guys is whether you want/need to do anything about it? for future and other users?

MX Linux Forum

live usb doesn't go beyond "start init" (waiting for /dev to be fully populated)

live usb doesn't go beyond "start init" (waiting for /dev to be fully populated) [Solved]

Re: live usb doesn't go beyond "start init"

Re: live usb doesn't go beyond "start init"

Re: live usb doesn't go beyond "start init"

Re: live usb doesn't go beyond "start init"

Re: live usb doesn't go beyond "start init"

Re: live usb doesn't go beyond "start init"

Re: live usb doesn't go beyond "start init"

Re: live usb doesn't go beyond "start init"

Re: live usb doesn't go beyond "start init"

Re: live usb doesn't go beyond "start init"

Re: live usb doesn't go beyond "start init"

Re: live usb doesn't go beyond "start init"

Re: live usb doesn't go beyond "start init"

Re: live usb doesn't go beyond "start init"

Re: live usb doesn't go beyond "start init"

Re: live usb doesn't go beyond "start init"

Re: live usb doesn't go beyond "start init"

Re: live usb doesn't go beyond "start init"

Re: live usb doesn't go beyond "start init"

Re: live usb doesn't go beyond "start init" (waiting for /dev to be fully populated)

Re: live usb doesn't go beyond "start init" (waiting for /dev to be fully populated)

Re: live usb doesn't go beyond "start init" (waiting for /dev to be fully populated)

Re: live usb doesn't go beyond "start init" (waiting for /dev to be fully populated)

Re: live usb doesn't go beyond "start init" (waiting for /dev to be fully populated)

Re: live usb doesn't go beyond "start init" (waiting for /dev to be fully populated)

Re: live usb doesn't go beyond "start init" (waiting for /dev to be fully populated)

Re: live usb doesn't go beyond "start init" (waiting for /dev to be fully populated)

Re: live usb doesn't go beyond "start init" (waiting for /dev to be fully populated)

Re: live usb doesn't go beyond "start init" (waiting for /dev to be fully populated)

Re: live usb doesn't go beyond "start init" (waiting for /dev to be fully populated)

Re: live usb doesn't go beyond "start init" (waiting for /dev to be fully populated)

Re: live usb doesn't go beyond "start init" (waiting for /dev to be fully populated)

Re: live usb doesn't go beyond "start init" (waiting for /dev to be fully populated)

Re: live usb doesn't go beyond "start init" (waiting for /dev to be fully populated)

Re: live usb doesn't go beyond "start init" (waiting for /dev to be fully populated)

Re: live usb doesn't go beyond "start init" (waiting for /dev to be fully populated)

Re: live usb doesn't go beyond "start init" (waiting for /dev to be fully populated)

Re: (solved) live usb doesn't go beyond "start init" (waiting for /dev to be fully populated)

Re: (solved) live usb doesn't go beyond "start init" (waiting for /dev to be fully populated)

Re: (solved) live usb doesn't go beyond "start init" (waiting for /dev to be fully populated)

Re: (solved) live usb doesn't go beyond "start init" (waiting for /dev to be fully populated)

Re: (solved) live usb doesn't go beyond "start init" (waiting for /dev to be fully populated)

Re: (solved) live usb doesn't go beyond "start init" (waiting for /dev to be fully populated)

Re: (solved) live usb doesn't go beyond "start init" (waiting for /dev to be fully populated)

Re: (solved) live usb doesn't go beyond "start init" (waiting for /dev to be fully populated)

Re: (solved) live usb doesn't go beyond "start init" (waiting for /dev to be fully populated)

Re: (solved) live usb doesn't go beyond "start init" (waiting for /dev to be fully populated)

Re: (solved) live usb doesn't go beyond "start init" (waiting for /dev to be fully populated)

Re: (solved) live usb doesn't go beyond "start init" (waiting for /dev to be fully populated)

Re: (solved) live usb doesn't go beyond "start init" (waiting for /dev to be fully populated)

Re: (solved) live usb doesn't go beyond "start init" (waiting for /dev to be fully populated)

Re: (solved) live usb doesn't go beyond "start init" (waiting for /dev to be fully populated)

Re: (solved) live usb doesn't go beyond "start init" (waiting for /dev to be fully populated)