Page 1 of 1
After install cannot boot
Posted: Tue Aug 15, 2023 11:39 am
by heydave
I am a complete user - that's why I love MX. It works. That being said, i purchased a new laptop for my daughter's homeschool, a first for me.
It is an HP Laptop 15-fd0. I made a MX23 live USB and used it to install. I just used the "whole disk" option. When It finished, I shut down and tried to get it to boot from the hard drive. It gave me a window that said "Hard Disk Error (3F0)". No matter what I tried, it would not boot. I put the MX23 USB back in and it still would not boot, even to the USB. I says there is no operating system.
It will bot a MX21.2 USB that I had, but the mousepad will not work. I tried to get it to install the MX21, using the tab and arrow keys etc., but could not get past the first page about the partition stuff.
Please tell me I did not turn my first new laptop into a brick.
I love MX, but I do not know what I screwed up.
Re: After install cannot boot
Posted: Tue Aug 15, 2023 11:48 am
by MXRobo
Maybe, again maybe:
viewtopic.php?p=726017#p726017
First what have to done to prepare for the installation, and how? who, what, where, when, why, how, etc.,e.g. secure boot, fast start, usb bootable, locks, etc.
++EDIT++ Others may want to see the QSI, even if from the Live USB.
Good luck.
Re: After install cannot boot
Posted: Tue Aug 15, 2023 11:54 am
by razor2021
It must be a HP error thing. See link --> and try the hard reset and/or BIOS default settings steps first. I am not sure if you can run HP recovery if you've formatted the whole disk for MX23.
https://www.easeus.com/backup-recovery/ ... k-3f0.html
Re: After install cannot boot
Posted: Tue Aug 15, 2023 12:06 pm
by heydave
Initially, I just changed the boot order to "USB Flash/USB Hard Disk" first, "USB CD/DVD ROM Drive" second, "OS Boot Manager" third, and "USB Network Adapter" last' Then when the MX23 USB booted and worked, I found it would not work with the Realtek wireless card. I added a wireless USB, everything was fine, so I hit install. When it wouldn't boot, I went to an old computer to look through the forum. Found that I needed to disable secure boot, I did, still nothing. I tried to boot the stick again, to just reinstall, and it would not boot either. Checked the stick in another system - it works there. tried a MX 21.2 stick in the HP it boots, but the touchpad wont work (thought I could just rtry to install 21 instead). I tried "clearing secure boot keys" as well as "loading factory Default Keys".
Re: After install cannot boot
Posted: Tue Aug 15, 2023 12:18 pm
by Charlie Brown
Maybe you enter Bios settings and reset (all) to Factory Defaults, save, then (other than re-doing the boot sequence) just change the secure boot to disabled (also change sata mode to Ahci, if it's not like that by default) save, exit.
Re: After install cannot boot
Posted: Tue Aug 15, 2023 12:26 pm
by heydave
It must be a HP error thing. See link --> and try the hard reset and/or BIOS default settings steps first. I am not sure if you can run HP recovery if you've formatted the whole disk for MX23.
https://www.easeus.com/backup-recovery/ ... k-3f0.html
I tried Hard reset, biut the battery ion non removable. Then I tried the Restore BIOS settings. Aside from having to fix the Boot order, no change.
Maybe you enter Bios settings and reset (all) to Factory Defaults, save, then (other than re-doing the boot sequence) just change the secure boot to disabled (also change sata mode to Ahci, if it's not like that by default) save, exit.
I reset all I could, there was nothing regarding SATA or AHCI. I even opened the back, thinking I could maybe change in a different hard driveor something, but I couldn't even find the SSD at all.
Re: After install cannot boot
Posted: Tue Aug 15, 2023 12:29 pm
by j2mcgreg
I suspect that you are going to have to reinstall Win 11, then:
1) log into a Microsoft account and retrieve the BitLocker key --> you will need the key if disabling BitLocker in step #3 fails and you have to start over
2) disable Bitlocker, Secure Boot, and Fast Start Up
3) now access the bios and also disable Secure Boot there --> when you do so, it will ask if you want to install another OS. Say yes, type in the key provided and then you can reboot and install MX
these are the steps I had to take when I originally installed MX on my HP 15 in Feb 2022
Edited to add that you can not do a legacy (MBR) install on these HPs.
Re: After install cannot boot
Posted: Tue Aug 15, 2023 12:34 pm
by CharlesV
That machine most likely has an NVME drive.
First, if your booting with an mx 21 liveUSB, then its not the HP that is the problem.
If I am understanding what your posts are saying, then If you booted once with the mx 23 drive and then could no longer boot from it, then something in the install attempted to install TO that USB drive most likely. ( I saw something like this happen on my HP ENVY x360 2-in-1 Laptop 15-ew0xxx .
Redo your MX 23 liveUSB and try that boot and install again - making SURE that your installing TO the HP's nvme drive!!
Re: After install cannot boot
Posted: Tue Aug 15, 2023 12:39 pm
by heydave
OOH. I booted the MX 21 Stick again and noticed a Boot Rescue option. I hit it and it gave me a list.. I tried one marked "MX23 @[fat] (hd1,1)/EFI/mx23/grubx64.efi" It booted me into my fully function mx 23! Is there a way to make that work without going through the mx 21 stick first. I reckon i need to do something with grub but i do not know how.
Re: After install cannot boot
Posted: Tue Aug 15, 2023 12:56 pm
by fehlix
heydave wrote: Tue Aug 15, 2023 12:39 pm
OOH. I booted the MX 21 Stick again and noticed a Boot Rescue option. I hit it and it gave me a list.. I tried one marked "MX23 @[fat] (hd1,1)/EFI/mx23/grubx64.efi" It booted me into my fully function mx 23! Is there a way to make that work without going through the mx 21 stick first. I reckon i need to do something with grub but i do not know how.
Maybe ... but let gather first some infos_
* Quick System Info
* The output of EFI boot entries within the NVRAM:
run those commands as normal user:
* The partitions involved:
* and also
Thanks
PS: Post all between those [
code]code-tags[/code]
Re: After install cannot boot
Posted: Tue Aug 15, 2023 1:08 pm
by heydave
Hi Fehlix,
Since I am now in (kinda)I copied the Quick System Info.
Code: Select all
System:
Kernel: 6.1.0-10-amd64 [6.1.38-2] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-10-amd64 root=UUID=<filter> ro quiet splash
Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
dm: LightDM v: 1.26.0 Distro: MX-23_x64 Libretto July 31 2023 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Laptop System: HP product: HP Laptop 15-fd0xxx v: N/A serial: <superuser required> Chassis:
type: 10 serial: <superuser required>
Mobo: HP model: 8B36 v: 62.21 serial: <superuser required> UEFI: AMI v: F.03 date: 03/06/2023
Battery:
ID-1: BAT0 charge: 30.3 Wh (72.5%) condition: 41.8/41.0 Wh (101.8%) volts: 12.6 min: 11.2
model: HP Primary type: Li-ion serial: <filter> status: charging cycles: 2
CPU:
Info: model: Intel N200 bits: 64 type: MCP arch: Alder Lake level: v3 note: check built: 2021+
process: Intel 7 (10nm ESF) family: 6 model-id: 0xBE (190) stepping: 0 microcode: 0x10
Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 384 KiB desc: d-4x32 KiB; i-4x64 KiB
L2: 2 MiB desc: 1x2 MiB L3: 6 MiB desc: 1x6 MiB
Speed (MHz): avg: 2070 high: 2108 min/max: 800/3700 scaling: driver: intel_pstate
governor: powersave cores: 1: 2054 2: 2070 3: 2049 4: 2108 bogomips: 7987
I hope this is helpful information. I am not quite sure how to use the things you suggested, but am willing to learn. My day job is a shepherd and chicken wrangler, so a bit over my head.
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
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: Enhanced IBRS, IBPB: conditional, RSB filling, PBRSB-eIBRS: Not
affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel Alder Lake-N [UHD Graphics] vendor: Hewlett-Packard driver: i915 v: kernel
arch: Gen-12.2 process: Intel 10nm built: 2021-22+ ports: active: eDP-1 empty: HDMI-A-1
bus-ID: 00:02.0 chip-ID: 8086:46d0 class-ID: 0300
Device-2: Cheng Uei Precision Industry (Foxlink) HP True Vision HD Camera type: USB
driver: uvcvideo bus-ID: 1-3:3 chip-ID: 05c8:0b08 class-ID: fe01 serial: <filter>
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99") s-diag: 414mm (16.31")
Monitor-1: eDP-1 model: ChiMei InnoLux 0x1541 built: 2021 res: 1366x768 hz: 60 dpi: 101
gamma: 1.2 size: 344x193mm (13.54x7.6") diag: 394mm (15.5") ratio: 16:9 modes: 1366x768
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel Graphics (ADL-N) direct-render: Yes
Audio:
Device-1: Intel vendor: Hewlett-Packard driver: sof-audio-pci-intel-tgl
alternate: snd_hda_intel,snd_sof_pci_intel_tgl bus-ID: 00:1f.3 chip-ID: 8086:54c8 class-ID: 0401
API: ALSA v: k6.1.0-10-amd64 status: kernel-api tools: alsamixer,amixer
Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active
2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek vendor: Hewlett-Packard driver: N/A modules: wl pcie: speed: Unknown lanes: 63
link-max: gen: 6 speed: 64 GT/s port: 3000 bus-ID: 01:00.0 chip-ID: 10ec:b85b class-ID: 0280
Device-2: Ralink MT7601U Wireless Adapter type: USB driver: mt7601u bus-ID: 1-2:2
chip-ID: 148f:7601 class-ID: 0000 serial: <filter>
IF: wlan0 state: up mac: <filter>
Bluetooth:
Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 bus-ID: 1-8:4 chip-ID: 0bda:b85d
class-ID: e001 serial: <filter>
Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2
sub-v: 91cb hci-v: 5.2 rev: dfb7
Info: acl-mtu: 1021:6 sco-mtu: 255:12 link-policy: rswitch hold sniff park
link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio,
telephony
Drives:
Local Storage: total: 352.07 GiB used: 8.42 GiB (2.4%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 model: KLUDG4UHGC-B0E1 size: 119.2 GiB block-size: physical: 4096 B
logical: 4096 B type: N/A serial: N/A rev: 1001 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: SanDisk model: USB 3.2Gen1 size: 232.88 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?
Partition:
ID-1: / raw-size: 118.94 GiB size: 116.52 GiB (97.96%) used: 8.42 GiB (7.2%) fs: ext4
dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 256 MiB size: 255.3 MiB (99.73%) used: 4 KiB (0.0%) fs: vfat
dev: /dev/sda1 maj-min: 8:1
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
System Temperatures: cpu: 57.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos:
Packages: pm: dpkg pkgs: 2062 libs: 1047 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
pkgs: 0 pm: flatpak pkgs: 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 bookworm-updates main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bookworm main non-free
Info:
Processes: 224 Uptime: 4m wakeups: 76 Memory: 3.49 GiB used: 1.83 GiB (52.5%) Init: SysVinit
v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12 Client: shell wrapper
v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
Re: After install cannot boot
Posted: Tue Aug 15, 2023 1:17 pm
by fehlix
heydave wrote: Tue Aug 15, 2023 1:08 pm
Hi Fehlix,
Since I am now in (kinda)I copied the Quick System Info.
Code: Select all
System:
Kernel: 6.1.0-10-amd64 [6.1.38-2] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-10-amd64 root=UUID=<filter> ro quiet splash
Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
dm: LightDM v: 1.26.0 Distro: MX-23_x64 Libretto July 31 2023 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Laptop System: HP product: HP Laptop 15-fd0xxx v: N/A serial: <superuser required> Chassis:
type: 10 serial: <superuser required>
Mobo: HP model: 8B36 v: 62.21 serial: <superuser required> UEFI: AMI v: F.03 date: 03/06/2023
Battery:
ID-1: BAT0 charge: 30.3 Wh (72.5%) condition: 41.8/41.0 Wh (101.8%) volts: 12.6 min: 11.2
model: HP Primary type: Li-ion serial: <filter> status: charging cycles: 2
CPU:
Info: model: Intel N200 bits: 64 type: MCP arch: Alder Lake level: v3 note: check built: 2021+
process: Intel 7 (10nm ESF) family: 6 model-id: 0xBE (190) stepping: 0 microcode: 0x10
Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 384 KiB desc: d-4x32 KiB; i-4x64 KiB
L2: 2 MiB desc: 1x2 MiB L3: 6 MiB desc: 1x6 MiB
Speed (MHz): avg: 2070 high: 2108 min/max: 800/3700 scaling: driver: intel_pstate
governor: powersave cores: 1: 2054 2: 2070 3: 2049 4: 2108 bogomips: 7987
I hope this is helpful information. I am not quite sure how to use the things you suggested, but am willing to learn. My day job is a shepherd and chicken wrangler, so a bit over my head.
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
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: Enhanced IBRS, IBPB: conditional, RSB filling, PBRSB-eIBRS: Not
affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel Alder Lake-N [UHD Graphics] vendor: Hewlett-Packard driver: i915 v: kernel
arch: Gen-12.2 process: Intel 10nm built: 2021-22+ ports: active: eDP-1 empty: HDMI-A-1
bus-ID: 00:02.0 chip-ID: 8086:46d0 class-ID: 0300
Device-2: Cheng Uei Precision Industry (Foxlink) HP True Vision HD Camera type: USB
driver: uvcvideo bus-ID: 1-3:3 chip-ID: 05c8:0b08 class-ID: fe01 serial: <filter>
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99") s-diag: 414mm (16.31")
Monitor-1: eDP-1 model: ChiMei InnoLux 0x1541 built: 2021 res: 1366x768 hz: 60 dpi: 101
gamma: 1.2 size: 344x193mm (13.54x7.6") diag: 394mm (15.5") ratio: 16:9 modes: 1366x768
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel Graphics (ADL-N) direct-render: Yes
Audio:
Device-1: Intel vendor: Hewlett-Packard driver: sof-audio-pci-intel-tgl
alternate: snd_hda_intel,snd_sof_pci_intel_tgl bus-ID: 00:1f.3 chip-ID: 8086:54c8 class-ID: 0401
API: ALSA v: k6.1.0-10-amd64 status: kernel-api tools: alsamixer,amixer
Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active
2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek vendor: Hewlett-Packard driver: N/A modules: wl pcie: speed: Unknown lanes: 63
link-max: gen: 6 speed: 64 GT/s port: 3000 bus-ID: 01:00.0 chip-ID: 10ec:b85b class-ID: 0280
Device-2: Ralink MT7601U Wireless Adapter type: USB driver: mt7601u bus-ID: 1-2:2
chip-ID: 148f:7601 class-ID: 0000 serial: <filter>
IF: wlan0 state: up mac: <filter>
Bluetooth:
Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 bus-ID: 1-8:4 chip-ID: 0bda:b85d
class-ID: e001 serial: <filter>
Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2
sub-v: 91cb hci-v: 5.2 rev: dfb7
Info: acl-mtu: 1021:6 sco-mtu: 255:12 link-policy: rswitch hold sniff park
link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio,
telephony
Drives:
Local Storage: total: 352.07 GiB used: 8.42 GiB (2.4%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 model: KLUDG4UHGC-B0E1 size: 119.2 GiB block-size: physical: 4096 B
logical: 4096 B type: N/A serial: N/A rev: 1001 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: SanDisk model: USB 3.2Gen1 size: 232.88 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?
Partition:
ID-1: / raw-size: 118.94 GiB size: 116.52 GiB (97.96%) used: 8.42 GiB (7.2%) fs: ext4
dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 256 MiB size: 255.3 MiB (99.73%) used: 4 KiB (0.0%) fs: vfat
dev: /dev/sda1 maj-min: 8:1
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
System Temperatures: cpu: 57.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos:
Packages: pm: dpkg pkgs: 2062 libs: 1047 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
pkgs: 0 pm: flatpak pkgs: 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 bookworm-updates main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bookworm main non-free
Info:
Processes: 224 Uptime: 4m wakeups: 76 Memory: 3.49 GiB used: 1.83 GiB (52.5%) Init: SysVinit
v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12 Client: shell wrapper
v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
Thanks for the QSI,
would you mind open terminal as normal user and run the commands mentioned.
Copy & paste command and output as text here.
Re: After install cannot boot
Posted: Tue Aug 15, 2023 1:18 pm
by heydave
efibootmgr -v
BootCurrent: 0004
Timeout: 0 seconds
BootOrder: 0003,0001,0000,0004
Boot0000* Windows Boot Manager HD(1,GPT,ee6665b6-7874-4cf2-9d78-4d034ddfba7a,0x100,0x10400)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0001* MX Linux HD(1,GPT,a561ef3e-0f47-42bb-acbf-5eb81e76b0e8,0x100,0x10000)/File(\EFI\MX\grubx64.efi)
Boot0003* MX23 HD(1,GPT,a561ef3e-0f47-42bb-acbf-5eb81e76b0e8,0x100,0x10000)/File(\EFI\MX23\grubx64.efi)
Boot0004* USB Drive (UEFI) - USB PciRoot(0x0)/Pci(0x14,0x0)/USB(12,0)/HD(2,MBR,0x9104a1d9,0x1d1a6800,0x18800)..BO
$ lsblk -f -o +PARTUUID
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS PARTUUID
sda
├─sda1
│ vfat FAT32 EFI-SYSTEM
│ C77D-2391 255.3M 0% /boot/efi a561ef3e-0f47-42bb-acbf-5eb81e76b0e8
└─sda2
ext4 1.0 rootMX23
5e836122-6b9d-4554-82f0-f0299f76b08f 102.1G 7% / 881117e0-8490-49bf-8375-091d8e273ab3
sdb
├─sdb1
│ ext4 1.0 MX-Live-usb
│ 4b576f92-e57c-4390-98c8-a577fafbab25 9104a1d9-01
└─sdb2
vfat FAT32 MX-UEFI
F56C-575E 9104a1d9-02
sudo parted --list
[sudo] password for Katie:
Model: SAMSUNG KLUDG4UHGC-B0E1 (scsi)
Disk /dev/sda: 128GB
Sector size (logical/physical): 4096B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 269MB 268MB fat32 primary boot, esp
2 269MB 128GB 128GB ext4 primary
Model: USB SanDisk 3.2Gen1 (scsi)
Disk /dev/sdb: 250GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 250GB 250GB primary ext4 boot
2 250GB 250GB 51.4MB primary fat32 esp
Sorry about the format. I didn't understand the code tag thing, but i figured out the terminal.
Re: After install cannot boot
Posted: Tue Aug 15, 2023 1:25 pm
by fehlix
heydave wrote: Tue Aug 15, 2023 1:18 pm
Code: Select all
efibootmgr -v
BootCurrent: 0004
Timeout: 0 seconds
BootOrder: 0003,0001,0000,0004
Boot0000* Windows Boot Manager HD(1,GPT,ee6665b6-7874-4cf2-9d78-4d034ddfba7a,0x100,0x10400)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0001* MX Linux HD(1,GPT,a561ef3e-0f47-42bb-acbf-5eb81e76b0e8,0x100,0x10000)/File(\EFI\MX\grubx64.efi)
Boot0003* MX23 HD(1,GPT,a561ef3e-0f47-42bb-acbf-5eb81e76b0e8,0x100,0x10000)/File(\EFI\MX23\grubx64.efi)
Boot0004* USB Drive (UEFI) - USB PciRoot(0x0)/Pci(0x14,0x0)/USB(12,0)/HD(2,MBR,0x9104a1d9,0x1d1a6800,0x18800)..BO
$ lsblk -f -o +PARTUUID
Code: Select all
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS PARTUUID
sda
├─sda1
│ vfat FAT32 EFI-SYSTEM
│ C77D-2391 255.3M 0% /boot/efi a561ef3e-0f47-42bb-acbf-5eb81e76b0e8
└─sda2
ext4 1.0 rootMX23
5e836122-6b9d-4554-82f0-f0299f76b08f 102.1G 7% / 881117e0-8490-49bf-8375-091d8e273ab3
sdb
├─sdb1
│ ext4 1.0 MX-Live-usb
│ 4b576f92-e57c-4390-98c8-a577fafbab25 9104a1d9-01
└─sdb2
vfat FAT32 MX-UEFI
F56C-575E 9104a1d9-02
sudo parted --list
Code: Select all
Model: SAMSUNG KLUDG4UHGC-B0E1 (scsi)
Disk /dev/sda: 128GB
Sector size (logical/physical): 4096B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 269MB 268MB fat32 primary boot, esp
2 269MB 128GB 128GB ext4 primary
Model: USB SanDisk 3.2Gen1 (scsi)
Disk /dev/sdb: 250GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 250GB 250GB primary ext4 boot
2 250GB 250GB 51.4MB primary fat32 esp
Sorry about the format. I didn't understand the code tag thing, but i figured out the terminal.
Just reformated within the reply, so you see how it should look like and we can read it better.
Another one, please:
Re: After install cannot boot
Posted: Tue Aug 15, 2023 1:28 pm
by heydave
find /boot/efi -ls
1 4 drwxrwxr-x 2 root root 4096 Dec 31 1969 /boot/efi
I like the way you formatted. I'll need to figure that out.
Re: After install cannot boot
Posted: Tue Aug 15, 2023 1:36 pm
by fehlix
heydave wrote: Tue Aug 15, 2023 1:28 pm
find /boot/efi -ls
1 4 drwxrwxr-x 2 root root 4096 Dec 31 1969 /boot/efi
I like the way you formatted. I'll need to figure that out.
Hmme, so we are getting closer ...
what would this show:
Re: After install cannot boot
Posted: Tue Aug 15, 2023 1:38 pm
by heydave
$ ls -ld /boot/grub/*
drwxr-xr-x 2 root root 4096 Aug 14 20:55 /boot/grub/fonts
-rw------- 1 root root 6938 Jan 1 2023 /boot/grub/grub.cfg
-rw-r--r-- 1 root root 1024 Jan 1 2023 /boot/grub/grubenv
drwxr-xr-x 2 root root 20480 Aug 14 17:49 /boot/grub/i386-pc
drwxr-xr-x 2 root root 4096 Jan 1 2023 /boot/grub/locale
drwxr-xr-x 8 root root 4096 Jul 29 23:56 /boot/grub/themes
-rw-r--r-- 1 root root 2392304 Jul 29 23:57 /boot/grub/unicode.pf2
drwxr-xr-x 2 root root 16384 Jan 1 2023 /boot/grub/x86_64-efi
Re: After install cannot boot
Posted: Tue Aug 15, 2023 1:38 pm
by Charlie Brown
heydave wrote: Tue Aug 15, 2023 1:28 pm...need to figure that out.
Using the </> icon , i.e. :
Re: After install cannot boot
Posted: Tue Aug 15, 2023 1:42 pm
by heydave
Thanks Charlie Brown. I can now make it look better! My day job is a shepherd and chicken wrangler, and I side gig a homeschool dad. I have a lot to learn with the tech things.
Re: After install cannot boot
Posted: Tue Aug 15, 2023 1:50 pm
by fehlix
heydave wrote: Tue Aug 15, 2023 1:38 pm
$ ls -ld /boot/grub/*
Code: Select all
drwxr-xr-x 2 root root 4096 Aug 14 20:55 /boot/grub/fonts
-rw------- 1 root root 6938 Jan 1 2023 /boot/grub/grub.cfg
-rw-r--r-- 1 root root 1024 Jan 1 2023 /boot/grub/grubenv
drwxr-xr-x 2 root root 20480 Aug 14 17:49 /boot/grub/i386-pc
drwxr-xr-x 2 root root 4096 Jan 1 2023 /boot/grub/locale
drwxr-xr-x 8 root root 4096 Jul 29 23:56 /boot/grub/themes
-rw-r--r-- 1 root root 2392304 Jul 29 23:57 /boot/grub/unicode.pf2
drwxr-xr-x 2 root root 16384 Jan 1 2023 /boot/grub/x86_64-efi
Seems you either re-installed at least twice or/and tried with MXLiveUSB Boot Repair.
B/c you have both /boot/grub/x86_64-efi and /boot/grub/i386-pc folder,
whith the later one probably the only succeful one.
...
Anyway:
First we need to re-install efi-Grub bootoader:
run this:
Code: Select all
sudo grub-install --force-extra-removable --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=MX23 --recheck
post the command and any error or success:
next show again the efi-loader in NVRAM:
and the find:
and last re-generate the GRUB menu:
Post always the commadn and the text output.
Re: After install cannot boot
Posted: Tue Aug 15, 2023 1:58 pm
by heydave
Yeah, I guess I did all of those things.
Code: Select all
sudo grub-install --force-extra-removable --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=MX23 --recheck
[sudo] password for Katie:
Installing for x86_64-efi platform.
Installation finished. No error reported.
Code: Select all
$ efibootmgr -v
BootCurrent: 0004
Timeout: 0 seconds
BootOrder: 0003,0001,0000,0004
Boot0000* Windows Boot Manager HD(1,GPT,ee6665b6-7874-4cf2-9d78-4d034ddfba7a,0x100,0x10400)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0001* MX Linux HD(1,GPT,a561ef3e-0f47-42bb-acbf-5eb81e76b0e8,0x100,0x10000)/File(\EFI\MX\grubx64.efi)
Boot0003* MX23 HD(1,GPT,a561ef3e-0f47-42bb-acbf-5eb81e76b0e8,0x100,0x10000)/File(\EFI\MX23\grubx64.efi)
Boot0004* USB Drive (UEFI) - USB PciRoot(0x0)/Pci(0x14,0x0)/USB(12,0)/HD(2,MBR,0x9104a1d9,0x1d1a6800,0x18800)..BO
Code: Select all
$ find /boot/efi -ls
1 4 drwxrwxr-x 3 root root 4096 Dec 31 1969 /boot/efi
113 4 drwxrwxr-x 4 root root 4096 Aug 15 13:52 /boot/efi/EFI
114 4 drwxrwxr-x 2 root root 4096 Aug 15 13:52 /boot/efi/EFI/MX23
115 136 -rw-rw-r-- 1 root root 139264 Aug 15 13:52 /boot/efi/EFI/MX23/grubx64.efi
116 4 drwxrwxr-x 2 root root 4096 Aug 15 13:52 /boot/efi/EFI/BOOT
117 136 -rw-rw-r-- 1 root root 139264 Aug 15 13:52 /boot/efi/EFI/BOOT/BOOTX64.EFI
Code: Select all
$ sudo update-grub
Generating grub configuration file ...
Found theme: /boot/grub/themes/mx_linux/theme.txt
Found linux image: /boot/vmlinuz-6.1.0-10-amd64
Found initrd image: /boot/initrd.img-6.1.0-10-amd64
Found mtest-64.efi image: /boot/uefi-mt/mtest-64.efi
Adding boot menu entry for EFI firmware configuration
done
Re: After install cannot boot
Posted: Tue Aug 15, 2023 2:09 pm
by razor2021
Now reboot and see if you are able to boot clean into grub and choose MX23 default. And ...? The suspense is killing me.
Re: After install cannot boot
Posted: Tue Aug 15, 2023 2:14 pm
by heydave
oy...no...still the same. Had to come in through the mx21 stick then the boot rescue under grub. When I tried without it i just got the same error message as before.
Re: After install cannot boot
Posted: Tue Aug 15, 2023 2:20 pm
by razor2021
I'm assuming you put back the boot order so the BIOS knows the boot off the disk operating system? I know you did, but just had to ask.
Re: After install cannot boot
Posted: Tue Aug 15, 2023 2:21 pm
by heydave
I will double check...
Re: After install cannot boot
Posted: Tue Aug 15, 2023 2:29 pm
by heydave
Boot order is USb/Flash, then USB CD/DVD, then OS System. If i boot without the mx21 stick i still get "Boot device not found Hard disk (3F0)" error. it does seem like there are different choices in grub on the boot rescue. I still chose the mx23 one
Re: After install cannot boot
Posted: Tue Aug 15, 2023 2:36 pm
by Charlie Brown
Then "just in case" take hdd to top , save, retry (without the usb stick).
If still the same: wait a bit more for some other suggestions. If nothing works: Boot once more like that, indirectly, then install rEFInd.
Code: Select all
sudo apt update ; sudo apt install refind -y ; sudo refind-install
Reboot.
Re: After install cannot boot
Posted: Tue Aug 15, 2023 2:52 pm
by heydave
Charlie Brown wrote: Tue Aug 15, 2023 2:36 pm
Then "just in case" take hdd to top , save, retry (without the usb stick).
If still the same: wait a bit more for some other suggestions. If nothing works: Boot once more like that, indirectly, then install rEFInd.
Code: Select all
sudo apt update ; sudo apt install refind -y ; sudo refind-install
Reboot.
I booted that way (OS at top) several times. No dice.
Please pardon my ignorance, but do I enter the code you gave me as one command, or do I enter it as different commands broken at the semicolon?
Re: After install cannot boot
Posted: Tue Aug 15, 2023 2:54 pm
by Charlie Brown
heydave wrote: Tue Aug 15, 2023 2:52 pm... do I enter the code you gave me as one command...?
Yep :)
Just copy (the whole) -paste - press Enter.
All are ready (the semicolons make them be executed one after the other ...)
Re: After install cannot boot
Posted: Tue Aug 15, 2023 2:58 pm
by heydave
Thanks. Here is the dialogue.
Code: Select all
sudo apt update ; sudo apt install refind -y ; sudo refind-install
[sudo] password for Katie:
Hit:1 http://deb.debian.org/debian bookworm-updates InRelease
Hit:2 http://security.debian.org/debian-security bookworm-security InRelease
Hit:3 http://deb.debian.org/debian bookworm InRelease
Hit:4 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
40 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Recommended packages:
sbsigntool
The following NEW packages will be installed:
refind
0 upgraded, 1 newly installed, 0 to remove and 40 not upgraded.
Need to get 3,696 kB of archives.
After this operation, 5,327 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian bookworm/main amd64 refind amd64 0.13.2-1+b1 [3,696 kB]
Fetched 3,696 kB in 1s (3,702 kB/s)
Preconfiguring packages ...
Selecting previously unselected package refind.
(Reading database ... 279643 files and directories currently installed.)
Preparing to unpack .../refind_0.13.2-1+b1_amd64.deb ...
Unpacking refind (0.13.2-1+b1) ...
Setting up refind (0.13.2-1+b1) ...
Installing rEFInd to the ESP...
Processing triggers for man-db (2.11.2-2) ...
ShimSource is none
Installing rEFInd on Linux....
ESP was found at /boot/efi using vfat
Found rEFInd installation in /boot/efi/EFI/refind; upgrading it.
Installing driver for ext4 (ext4_x64.efi)
Copied rEFInd binary files
Notice: Backed up existing icons directory as icons-backup.
Existing refind.conf file found; copying sample file as refind.conf-sample
to avoid overwriting your customizations.
Keeping existing NVRAM entry
rEFInd is set as the default boot manager.
Existing //boot/refind_linux.conf found; not overwriting.
I am rebooting now.
Re: After install cannot boot
Posted: Tue Aug 15, 2023 2:59 pm
by Charlie Brown
I'm excited
Re: After install cannot boot
Posted: Tue Aug 15, 2023 3:01 pm
by Charlie Brown
In the meantime you can also:
(Not related to this issue... Just "40 packages can be upgraded." )
Re: After install cannot boot
Posted: Tue Aug 15, 2023 3:02 pm
by heydave
still the same error message and no boot.
Booting from the mx21 stick, into mx 23 on thesystem, this thing flies. I love mx. I dunno how I goofed this up.
Re: After install cannot boot
Posted: Tue Aug 15, 2023 3:04 pm
by Charlie Brown
Oh, then it's something else, not just a boot issue (efibootmgr also shows the boot order as we would like to set to: MX at #1 position ...)
Re: After install cannot boot
Posted: Tue Aug 15, 2023 3:06 pm
by fehlix
heydave wrote: Tue Aug 15, 2023 1:58 pm
Yeah, I guess I did all of those things.
Code: Select all
sudo grub-install --force-extra-removable --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=MX23 --recheck
[sudo] password for Katie:
Installing for x86_64-efi platform.
Installation finished. No error reported.
Code: Select all
$ efibootmgr -v
BootCurrent: 0004
Timeout: 0 seconds
BootOrder: 0003,0001,0000,0004
Boot0000* Windows Boot Manager HD(1,GPT,ee6665b6-7874-4cf2-9d78-4d034ddfba7a,0x100,0x10400)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0001* MX Linux HD(1,GPT,a561ef3e-0f47-42bb-acbf-5eb81e76b0e8,0x100,0x10000)/File(\EFI\MX\grubx64.efi)
Boot0003* MX23 HD(1,GPT,a561ef3e-0f47-42bb-acbf-5eb81e76b0e8,0x100,0x10000)/File(\EFI\MX23\grubx64.efi)
Boot0004* USB Drive (UEFI) - USB PciRoot(0x0)/Pci(0x14,0x0)/USB(12,0)/HD(2,MBR,0x9104a1d9,0x1d1a6800,0x18800)..BO
Code: Select all
$ find /boot/efi -ls
1 4 drwxrwxr-x 3 root root 4096 Dec 31 1969 /boot/efi
113 4 drwxrwxr-x 4 root root 4096 Aug 15 13:52 /boot/efi/EFI
114 4 drwxrwxr-x 2 root root 4096 Aug 15 13:52 /boot/efi/EFI/MX23
115 136 -rw-rw-r-- 1 root root 139264 Aug 15 13:52 /boot/efi/EFI/MX23/grubx64.efi
116 4 drwxrwxr-x 2 root root 4096 Aug 15 13:52 /boot/efi/EFI/BOOT
117 136 -rw-rw-r-- 1 root root 139264 Aug 15 13:52 /boot/efi/EFI/BOOT/BOOTX64.EFI
Code: Select all
$ sudo update-grub
Generating grub configuration file ...
Found theme: /boot/grub/themes/mx_linux/theme.txt
Found linux image: /boot/vmlinuz-6.1.0-10-amd64
Found initrd image: /boot/initrd.img-6.1.0-10-amd64
Found mtest-64.efi image: /boot/uefi-mt/mtest-64.efi
Adding boot menu entry for EFI firmware configuration
done
OK, thanks.
Now, let's try to tidy up some entries within UEFI in the NVRAM:
This way:
First that Windows guy:
next the not used "MX Linux" entry:
Now when you reboot during early bootup (aks "POST"), Press F9 or F10 to get into the UEFI boot options list.
Do yet get the MX23 listed.
If not, you may need go into UEFI/PC-Bios setup and manually select/allow the a efi-loader under /EFI/MX23/grubx64.efi on the ESP (EFI System Partition)
Re: After install cannot boot
Posted: Tue Aug 15, 2023 3:12 pm
by heydave
Code: Select all
$ sudo efibootmgr -v -B -b 0
[sudo] password for Katie:
BootCurrent: 0004
Timeout: 0 seconds
BootOrder: 0002,0003,0001,0004
Boot0001* MX Linux HD(1,GPT,a561ef3e-0f47-42bb-acbf-5eb81e76b0e8,0x100,0x10000)/File(\EFI\MX\grubx64.efi)
Boot0002* rEFInd Boot Manager HD(1,GPT,a561ef3e-0f47-42bb-acbf-5eb81e76b0e8,0x100,0x10000)/File(\EFI\refind\refind_x64.efi)
Boot0003* MX23 HD(1,GPT,a561ef3e-0f47-42bb-acbf-5eb81e76b0e8,0x100,0x10000)/File(\EFI\MX23\grubx64.efi)
Boot0004* USB Drive (UEFI) - USB PciRoot(0x0)/Pci(0x14,0x0)/USB(12,0)/HD(2,MBR,0x9104a1d9,0x1d1a6800,0x18800)..BO
Code: Select all
$ sudo efibootmgr -v -B -b 1
[sudo] password for Katie:
BootCurrent: 0004
Timeout: 0 seconds
BootOrder: 0002,0003,0004
Boot0002* rEFInd Boot Manager HD(1,GPT,a561ef3e-0f47-42bb-acbf-5eb81e76b0e8,0x100,0x10000)/File(\EFI\refind\refind_x64.efi)
Boot0003* MX23 HD(1,GPT,a561ef3e-0f47-42bb-acbf-5eb81e76b0e8,0x100,0x10000)/File(\EFI\MX23\grubx64.efi)
Boot0004* USB Drive (UEFI) - USB PciRoot(0x0)/Pci(0x14,0x0)/USB(12,0)/HD(2,MBR,0x9104a1d9,0x1d1a6800,0x18800)..BO
Rebooting now...
Re: After install cannot boot
Posted: Tue Aug 15, 2023 3:19 pm
by heydave
After hitting f9 boot options, I do not get mx23 listed. I get a window that says to select boot device, but my only choice is "bbot from EFI file" if I enter that,I get "No Valid file system Available"
Re: After install cannot boot
Posted: Tue Aug 15, 2023 3:28 pm
by heydave
If not, you may need go into UEFI/PC-Bios setup and manually select/allow the a efi-loader under /EFI/MX23/grubx64.efi on the ESP (EFI System Partition)
I dont think I have this in my BIOS
Re: After install cannot boot
Posted: Tue Aug 15, 2023 3:36 pm
by Charlie Brown
Although you already said you installed using the "whole disk" option, "just in case":
Let's see if ESP has the flags ...
Re: After install cannot boot
Posted: Tue Aug 15, 2023 3:37 pm
by fehlix
heydave wrote: Tue Aug 15, 2023 3:28 pm
If not, you may need go into UEFI/PC-Bios setup and manually select/allow the a efi-loader under /EFI/MX23/grubx64.efi on the ESP (EFI System Partition)
I dont think I have this in my BIOS
Ok; some of those UEFI-systems (PC-BIOS/UEFI)systesm) do only allow to preselct efi-booloader when secureboot is enabled. So you might enable secureboot again, and if there is an Supervisor-Password field you may also need set first such thing (write down use a simple one). WHen rebooted into UEFI-ssysem Setup with SecureBoot enabled you may need enter the supervisout password. (or may be not).
Now search again within UEFI-system to add an efi-file. Or the internal boot-drive to boot allow in efi-mode.
The check whether efi-loader are signed is not done now, only when booting. So you may disabled secureboot again.
Re: After install cannot boot
Posted: Tue Aug 15, 2023 3:40 pm
by fehlix
Charlie Brown wrote: Tue Aug 15, 2023 3:36 pm
Although you already said you installed using the "whole disk" option, "just in case":
Let's see if ESP has the flags ...
was already posted...
Re: After install cannot boot
Posted: Tue Aug 15, 2023 3:42 pm
by Charlie Brown
Ah, yes, here:
Number Start End Size File system Name Flags
1 1049kB 269MB 268MB fat32 primary boot, esp
Re: After install cannot boot
Posted: Tue Aug 15, 2023 4:07 pm
by heydave
Ok; some of those UEFI-systems (PC-BIOS/UEFI)systesm) do only allow to preselct efi-booloader when secureboot is enabled. So you might enable secureboot again, and if there is an Supervisor-Password field you may also need set first such thing (write down use a simple one). WHen rebooted into UEFI-ssysem Setup with SecureBoot enabled you may need enter the supervisout password. (or may be not).
Now search again within UEFI-system to add an efi-file. Or the internal boot-drive to boot allow in efi-mode.
The check whether efi-loader are signed is not done now, only when booting. So you may disabled secureboot again
.
i enabled secure boot and set a password - still n o options in Bios or in Boot f9 menu,
did not get a chance to run the
sudo parted -l
because now I get error message "Verification failed : (ox1A) Security Verification" it gives an ok which when entered gives a screen that says "SHim uefi key managament then press any key for MOK management. that gives choices: continue boot (which fails), enroll key from disk, or enroll hash from disk.
I had to get another computer to send this.
Re: After install cannot boot
Posted: Tue Aug 15, 2023 4:23 pm
by heydave
]OK bsck to booting in from the mx21 stick and the boot rescue.
Ran the command from Charlie Brown
Code: Select all
sudo parted -l
[sudo] password for Katie:
Model: SAMSUNG KLUDG4UHGC-B0E1 (scsi)
Disk /dev/sda: 128GB
Sector size (logical/physical): 4096B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 269MB 268MB fat32 primary boot, esp
2 269MB 128GB 128GB ext4 primary
Model: USB SanDisk 3.2Gen1 (scsi)
Disk /dev/sdb: 250GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 250GB 250GB primary ext4 boot
2 250GB 250GB 51.4MB primary fat32 esp
Re: After install cannot boot
Posted: Tue Aug 15, 2023 4:29 pm
by fehlix
heydave wrote: Tue Aug 15, 2023 4:07 pm
Ok; some of those UEFI-systems (PC-BIOS/UEFI)systesm) do only allow to preselct efi-booloader when secureboot is enabled. So you might enable secureboot again, and if there is an Supervisor-Password field you may also need set first such thing (write down use a simple one). WHen rebooted into UEFI-ssysem Setup with SecureBoot enabled you may need enter the supervisout password. (or may be not).
Now search again within UEFI-system to add an efi-file. Or the internal boot-drive to boot allow in efi-mode.
The check whether efi-loader are signed is not done now, only when booting. So you may disabled secureboot again
.
i enabled secure boot and set a password - still n o options in Bios or in Boot f9 menu,
did not get a chance to run the
sudo parted -l
because now I get error message "Verification failed : (ox1A) Security Verification" it gives an ok which when entered gives a screen that says "SHim uefi key managament then press any key for MOK management. that gives choices: continue boot (which fails), enroll key from disk, or enroll hash from disk.
That's good, as it shows it tries to boot the non-sign efiloader. ANd fails good.
Now next go again into F10 UEFI setup and try to select an EFI file on the ESP may be it is labeled "select as trusted".
When done, disabled secureboot again. And check F9 uefi boot options list.
Re: After install cannot boot
Posted: Tue Aug 15, 2023 4:47 pm
by heydave
in the F10 it still has no place to even select any such files. There is a dearth of choices, very sparse.
in the F9 i still get only "boot from EFI File", but no other choice only "enter to select an option" or "F10 to enter bios" entering bios still no place to even select. i have look at all the pages and offering not even something grayed out.
i think when it failed good, I had some choices(had to look quick and with understanding which I do not have Sorry)
Re: After install cannot boot
Posted: Tue Aug 15, 2023 5:32 pm
by fehlix
heydave wrote: Tue Aug 15, 2023 4:47 pm
in the F10 it still has no place to even select any such files. There is a dearth of choices, very sparse.
in the F9 i still get only "boot from EFI File", but no other choice only "enter to select an option" or "F10 to enter bios" entering bios still no place to even select. i have look at all the pages and offering not even something grayed out.
i think when it failed good, I had some choices(had to look quick and with understanding which I do not have Sorry)
Is there an option to switch to Legacy instead of UEFI, would that boot the MX23 stick?
Re: After install cannot boot
Posted: Tue Aug 15, 2023 5:39 pm
by heydave
unfortunately not in the bios. the only place i saw that was in the installer somewhere i think. I reckon i really messed this thing up.
Re: After install cannot boot
Posted: Tue Aug 15, 2023 5:58 pm
by Charlie Brown
What happens when you press Enter (to select an option) here? :
in the F9 i still get only "boot from EFI File", but no other choice only "enter to select an option" or ...
Re: After install cannot boot
Posted: Tue Aug 15, 2023 6:05 pm
by fehlix
heydave wrote: Tue Aug 15, 2023 5:39 pm
unfortunately not in the bios. the only place i saw that was in the installer somewhere i think. I reckon i really messed this thing up.
Not sure, if you search for the error message you posted, there seems to be quite a number of HP users with similar reports. OTOH, it rties to boot with secure enabled, so maybe something else. WOuld it boot into if you shrink the currently big -root partition using LiveUSB-> Gparted and create an empty addional partition, where you re-install MX-21 root into that partition. So keep the existing MX23 install and try to add a MX21 install do reuse the existing ESP in the "Use for" column of the installer. Only to make sure it's not related with the newer MX-23 build. And if that would boot we could add an entry into the boot menu to boot into MX23.
Re: After install cannot boot
Posted: Tue Aug 15, 2023 6:17 pm
by heydave
Sounds a little over my head, but I would be like to try. Only thing is I gotta go chase sheep right now (really). Could I start here at this thread tomorrow? I'm not gonna lie, I'll need a bit (more) babying. I'd like to learn though. Kind of the reason I went with MX. Help for dummies like me. Just FYI, I have been helping other older people with older windog systems switch to MX21. So far for me, bulletproof. Gonna like 23 from what I've seen.
Thank You to all that have been helping me. gotta run. be back tomorrow
Re: After install cannot boot
Posted: Wed Aug 16, 2023 7:18 am
by heydave
As of this morning, the Hp will still not boot from the hard drive. It will not boot from the MX23 stick. It WILL boot from the MX21 stick by way of the grub rescue boot option, into MX 23 on the hard drive. This is the 23 as i installed it with the username and such, fully functional.
If I try to boot into MX21 itself on the stick, all seems well, BUT the touchpad does not work, so I cannot use it to install 21.
Also, both the MX21 and MX23 stick operate normally on other computers.
Re: After install cannot boot
Posted: Wed Aug 16, 2023 7:25 am
by fehlix
BTW, what method was used to create the MX23 LiveUSB. In case you used Rufus on windows, there was a report with recent GRUB upgrade may be used by Rufus, to make the system not boot - something with secureboot related.
Re: After install cannot boot
Posted: Wed Aug 16, 2023 7:31 am
by heydave
I used the MX Live USB maker in my MX21 installed system. And old Dell from Maybe 2008 or 2009.
Re: After install cannot boot
Posted: Wed Aug 16, 2023 7:52 am
by fehlix
heydave wrote: Wed Aug 16, 2023 7:31 am
I used the MX Live USB maker in my MX21 installed system. And old Dell from Maybe 2008 or 2009.
May be a last attempt:
When booted into the installed system:
Can you try this:
Code: Select all
sudo mkdir -p /boot/efi/EFI/Microsoft/Boot
and
Code: Select all
sudo cp /boot/efi/EFI/MX23/grubx64.efi /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi
This for the weird case, that they have hardcoded the path of MS win boot loader
and wrongly assume there is not system to boot if it is missing.
Als when re-boot make sure you pull out all external Media after shutdown and do a fresh start.
Re: After install cannot boot
Posted: Wed Aug 16, 2023 8:15 am
by heydave
Code: Select all
Katie@KatieMX23:~
$ sudo mkdir -p /boot/efi/EFI/Microsoft/Boot
[sudo] password for Katie:
Katie@KatieMX23:~
Code: Select all
Katie@KatieMX23:~
$ sudo cp /boot/efi/EFI/MX23/grubx64.efi /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi
Katie@KatieMX23:~
Did both. Didn't return much (my ignorance, dunno what it should return).
Rebooting now with the USB stick removed.
Re: After install cannot boot
Posted: Wed Aug 16, 2023 8:19 am
by heydave
Still goes to an error window "boot device not found, please install an operating system"
Re: After install cannot boot
Posted: Wed Aug 16, 2023 8:43 am
by Charlie Brown
heydave wrote: Wed Aug 16, 2023 8:15 am
Code: Select all
Katie@KatieMX23:~
$ sudo mkdir -p /boot/efi/EFI/Microsoft/Boot
[sudo] password for Katie:
Katie@KatieMX23:~
Code: Select all
Katie@KatieMX23:~
$ sudo cp /boot/efi/EFI/MX23/grubx64.efi /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi
Katie@KatieMX23:~
Did both. Didn't return much...
That's ok, it does (did) it silently.
Re: After install cannot boot
Posted: Wed Aug 16, 2023 9:13 am
by fehlix
heydave wrote: Wed Aug 16, 2023 8:19 am
Still goes to an error window "boot device not found, please install an operating system"
Another weird attempt:
Open Gparted and right-click on the rootMX23 partition -> Manage flags -> select legacy_boot.
Re: After install cannot boot
Posted: Wed Aug 16, 2023 9:20 am
by heydave
ok, but quick question... I am a bit afraid of gparted. will this keep us from what at least coming in from the mx 21 grub rescue boot?
Re: After install cannot boot
Posted: Wed Aug 16, 2023 9:20 am
by Charlie Brown
MX 21 usb boots and 23 doesn't .. might it be something kernel-related? One is signed , the other is not (afaik). (And the weird thing is that the signed one is the Debian 12 kernel).
@heydave ok, I know this is the 100th same question, but just to make it sure:
When resetting to factory defaults, the secure boot also turns to enabled. So, have you turned it back to disabled after that? Or checked the current setting?
Re: After install cannot boot
Posted: Wed Aug 16, 2023 10:07 am
by heydave
would it help to post a screenshot of gparted image before I pull the trigger on this? Kinda worried about not getting in via mx 21 stick afterwards. If screenshot would be helpful, I have taken it but can't seem to get it into post editor.
Re: After install cannot boot
Posted: Wed Aug 16, 2023 10:28 am
by Charlie Brown
Mamma Mia ,
I thought you already did that with
post #5 :)
Re: After install cannot boot
Posted: Wed Aug 16, 2023 10:28 am
by heydave
Sorry Charlie Brown. I just saw this, rebooted and checked.
Secure Boot is Disabled.
Code: Select all
MX 21 usb boots and 23 doesn't .. might it be something kernel-related? One is signed , the other is not (afaik). (And the weird thing is that the signed one is the Debian 12 kernel).
MX21 doesn't really boot properly. If I boot into it, the touchpad does not work, because I had at one point thought to install MX21 but could not. I use the MX21 stick to get to the rescue boot thing, then from there into MX 23 on the hard drive, which operates normally otherwise.
Both my MX21 and MX23 sticks boot and operate normally on my other system.
Fehlix had suggested using gparted from MX23 harddrive to enable legacy boot. I am certainly willing, but I have not yet tried, because I am afraid that I might no longer be able to get in from the MX21 rescue boot.
Re: After install cannot boot
Posted: Wed Aug 16, 2023 10:32 am
by Charlie Brown
Ok, but ... you marked the thread as solved. Is it ok now or marked accidentally?
Btw. on MX-21 you can use a mouse temporarily or just use the tab key (the one under the " ) (also arrow keys to navigate , and space bar to select/deselect something) , and from menu access "MX Tweak", the last tab, and select "Use libinput driver ..." apply.
Re: After install cannot boot
Posted: Wed Aug 16, 2023 10:39 am
by heydave
I saw it was marked solved, but i dont know how that happened. I am still in over my head. Must be marked accidentally.
I tried to use the tab and arrow keys to get to "install", but once in, I could only get part way and then could not select what i needed (dont remember at this point which)
Code: Select all
and access "MX Tweak" , the last tab and select "Use libinput driver ..." apply.
Didint understand (sorry)
Re: After install cannot boot
Posted: Wed Aug 16, 2023 10:42 am
by Charlie Brown
In fact, (iirc you said no) there must be a way to make it use the Legacy mode in Bios, then it would be simpler.
(On some brands/models such changes require creating an Admin pw. first - etc...)
_____________
The MX Tweak .. after you see the desktop, from menu (pressing the start menu / Windows key on keyboard) .. then tab, arrow etc.. to navigate ...
Press the Win. key, type tweak, press Enter, right-arrow key to go to last tab ... then the tab key 1-2 times and when that libinput option is highlighted press the space bar (to mark it) ... tab key again to go to the "Apply" button ... press Enter.
Re: After install cannot boot
Posted: Wed Aug 16, 2023 10:49 am
by j2mcgreg
Charlie Brown wrote: Wed Aug 16, 2023 10:42 am
In fact, (iirc you said no) there must be a way to make it use the Legacy mode in Bios, then it would be simpler.
(On some brands/models such changes require creating an Admin pw. first - etc...)
_____________
The MX Tweak .. after you see the desktop, from menu (pressing the start menu / Windows key on keyboard) .. then tab, arrow etc.. to navigate ...
Press the Win. key, type
tweak, press Enter, right-arrow key to go to last tab ...
You can't do an MBR install on modern HP's. They only accept UEFI, but they do allow a user to disable Secure Boot.
Re: After install cannot boot
Posted: Wed Aug 16, 2023 10:50 am
by Charlie Brown
In the meantime, you can do that simply on the pc that MX-21 works (no need to tab etc. just open MX Tweak from menu) , then "MX RemasterCC" from menu to make it permanent on the live usb.
Re: After install cannot boot
Posted: Wed Aug 16, 2023 10:52 am
by Charlie Brown
j2mcgreg wrote: Wed Aug 16, 2023 10:49 am... on modern HP's. They only ...
I just remember the unforgettable nice words of Mr. Torvalds when they said "Nvidia". :)
(Though I'm an HP user, both laptops)
Re: After install cannot boot
Posted: Wed Aug 16, 2023 10:59 am
by j2mcgreg
@heydave
When you created the USB install drive, did you specify that the install utility use GPT partitioning or did you just accept the defaults?
Re: After install cannot boot
Posted: Wed Aug 16, 2023 11:02 am
by heydave
I just accepted the defaults. I am just a user in over my head. That's why I like MX, it takes care of those things for me.
Re: After install cannot boot
Posted: Wed Aug 16, 2023 11:02 am
by Charlie Brown
MBR:
/dev/sdb maj-min: 8:16 type: USB vendor: SanDisk model: USB 3.2Gen1 size: 232.88 GiB
block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 1.00 scheme: MBR
But according to devs ( @fehlix ) that doesn't matter.
Re: After install cannot boot
Posted: Wed Aug 16, 2023 11:04 am
by MXRobo
Everyone – first my apologies for even entering this post which is several layers over my head, and additional apologies if this has already been addressed, but I'd feel remise if I didn't inquire.
Heydave said that the touchpad does not work, surely this isn't something as simple as "Tap touchpad to click" needs to be checked/enabled in Mouse and Touchpad>Devices - > - > Touchpad?
Maybe wishing for a simple solution.
Re: After install cannot boot
Posted: Wed Aug 16, 2023 11:04 am
by Charlie Brown
Meanwhile, you can remove the solved mark clicking the check-mark icon on post #61 :)
Re: After install cannot boot
Posted: Wed Aug 16, 2023 11:07 am
by Charlie Brown
MXRobo wrote: Wed Aug 16, 2023 11:04 am... "Tap touchpad to click" needs to be checked/enabled..?
That one is to be able to use it to click, like using the buttons.
Re: After install cannot boot
Posted: Wed Aug 16, 2023 11:09 am
by MXRobo
I know, I just thought maybe....
Re: After install cannot boot
Posted: Wed Aug 16, 2023 11:18 am
by heydave
Code: Select all
It will not boot from the MX23 stick. It WILL boot from the MX21 stick by way of the grub rescue boot option, into MX 23 on the hard drive. This is the 23 as i installed it with the username and such, fully functional.
If I try to boot into MX21 itself on the stick, all seems well, BUT the touchpad does not work, so I cannot use it to install 21.
Also, both the MX21 and MX23 stick operate normally on other computers.
I did try to enable the touchpad in 21 proper, but it simply wont even recognize it is there.
Is there any other way to install MX21 on this particular system. I love MX23 it runs on my older systems.
Re: After install cannot boot
Posted: Wed Aug 16, 2023 11:18 am
by razor2021
Maybe its just me, but I doubt the USB sticks are an issue. And it might be mostly a disk boot corruption causing the BIOS on the laptop to not recognize the boot partition where GRUB sits. Perhaps if possible, use the HP tool to recover the device first back to its original state since none of the current data/MX21/MX23 is needed anyway with the first installation
@heydave used when he selected the "whole disk" option and got the "Hard Disk 3F0 Error"?
If the OP wants to try to recover back to original state, he might want to try using the HP Cloud Recovery Tool (if supported). To do this, you have to use another laptop with Windows and access to Microsoft Store, and download the hp cloud recovery tool and follow instructions to put onto a USB stick. Then use the USB stick to recover the first HP laptop back to its factory state.
To check if your laptop is supported --> go here
http://support.hp.cloud-recovery.s3-web ... zonaws.com
The HP cloud restore
might/should reformat the boot disk properly to its factory settings. I have not used it, but it seems a more viable approach.
That said, if laptop was recovered, I would then update the BIOS afterwards (with secureboot disabled) and upgrade from the current F.03 Rev.A to the latest F.05 Rev.A.
Now, when everything is running Win10/11 in a good state, he might need to disable all the secureboot stuff in the BIOS prior to any linux install. He can then install MX23 using UEFI, since its a newer laptop and not MBR. He would be fully experienced by now with all the steps he's taken so far.
Re: After install cannot boot
Posted: Wed Aug 16, 2023 11:26 am
by Charlie Brown
heydave wrote: Wed Aug 16, 2023 11:18 am... any other way to install MX21 on this particular system...?
You can use a mouse , no matter new/very old (maybe borrow from someone just for 10 min.).
Re: After install cannot boot
Posted: Wed Aug 16, 2023 11:27 am
by CharlesV
Please forgive me if this has been covered, I scanned for it but didnt see it.
First, the OP *was* able to boot an MX23 LiveUSB and attempt an install...
Second, AFTER that attempted install, two things were obvious:
1) The LiveUSB disk didnt work again, and
2) There appears to be an install ON the HP nvme - just not booting from it -unless its boot strapped from an option from the OTHER live usb.
So..
a) Something happened to the MX23 live boot! Has there been a Second mx 23 Live boot created and tried out ?
b) Has there been any attempt reset the HP bios and ONLY turn off secure boot, then attempt an MX 23 install again?
On my HP (2023) I had several times when the MX installer would attempt to write to the USB stick on install, and when I didnt catch it, it obviously was a mess and I had to redo the stick.
Re: After install cannot boot
Posted: Wed Aug 16, 2023 11:29 am
by CharlesV
And one more potential thing ... Why not install mx 21 onto this HP, using a mouse, and then once up and loaded, push updates and work at the trackpad issue ?
Re: After install cannot boot
Posted: Wed Aug 16, 2023 11:30 am
by Charlie Brown
CharlesV wrote: Wed Aug 16, 2023 11:27 am...
a) Something happened to the MX23 live boot!..
Yes, but it works (boots) on other computers :)
Re: After install cannot boot
Posted: Wed Aug 16, 2023 11:31 am
by Charlie Brown
CharlesV wrote: Wed Aug 16, 2023 11:27 am...b) Has there been any attempt reset the HP bios and ONLY turn off secure boot, then ...
Yes, even at post #5 :)
Re: After install cannot boot
Posted: Wed Aug 16, 2023 11:32 am
by CharlesV
If that is the case, then WHY was OP able to boot and install to the HP, but not able to boot again with that stick ?
Re: After install cannot boot
Posted: Wed Aug 16, 2023 11:34 am
by CharlesV
Charlie Brown wrote: Wed Aug 16, 2023 11:31 am
CharlesV wrote: Wed Aug 16, 2023 11:27 am...b) Has there been any attempt reset the HP bios and ONLY turn off secure boot, then ...
Yes, even at post #5 :)
AH, but there was a bunch of stuff listed in post # 6... so my question was if there was a reset and
*only* a secure boot off.
Re: After install cannot boot
Posted: Wed Aug 16, 2023 11:34 am
by j2mcgreg
heydave wrote: Wed Aug 16, 2023 11:02 am
I just accepted the defaults. I am just a user in over my head. That's why I like MX, it takes care of those things for me.
I think that you should rewrite the MX ISO to your install drive using our Live USB Maker, but this time, prior to the actual write. click on "Show Advanced Options" and then put a check mark beside GPT partitioning. Then let the utility write the ISO. Once it's complete, use the drive to reinstall MX using the "Automatic Install using entire drive" option on your laptop. That's how I set up Live USB Maker when I put MX 23 on my HP 15. By way of proof that it works, here's the QSI for my HP 15:
Code: Select all
System:
Kernel: 6.2.14-1-liquorix-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
intel_pstate=disable hpet=disable rcupdate.rcu_expedited=1
BOOT_IMAGE=/boot/vmlinuz-6.2.14-1-liquorix-amd64 root=UUID=<filter> ro quiet splash
Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
dm: LightDM v: 1.26.0 Distro: MX-23_ahs_x64 Libretto July 31 2023 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Laptop System: HP product: HP Laptop 15-ef2xxx v: N/A serial: <superuser required> Chassis:
type: 10 serial: <superuser required>
Mobo: HP model: 887A v: 59.21 serial: <superuser required> UEFI: AMI v: F.27 date: 10/20/2022
Battery:
ID-1: BAT0 charge: 40.5 Wh (99.5%) condition: 40.7/40.7 Wh (100.0%) volts: 13.0 min: 11.3
model: HP Primary type: Li-ion serial: <filter> status: charging
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M325 serial: <filter>
charge: 55% (should be ignored) rechargeable: yes status: discharging
CPU:
Info: model: AMD Ryzen 3 5300U with Radeon Graphics bits: 64 type: MT MCP arch: Zen 2 gen: 3
level: v3 note: check built: 2020-22 process: TSMC n7 (7nm) family: 0x17 (23)
model-id: 0x68 (104) stepping: 1 microcode: 0x8608104
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache: L1: 256 KiB
desc: d-4x32 KiB; i-4x32 KiB L2: 2 MiB desc: 4x512 KiB L3: 4 MiB desc: 1x4 MiB
Speed (MHz): avg: 2692 high: 3893 min/max: 1400/3900 boost: enabled scaling:
driver: acpi-cpufreq governor: ondemand cores: 1: 1729 2: 1700 3: 3743 4: 3129 5: 3893 6: 3889
7: 1730 8: 1730 bogomips: 41521
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: retbleed mitigation: untrained return thunk; SMT enabled with STIBP protection
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, STIBP: always-on, RSB filling,
PBRSB-eIBRS: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Lucienne vendor: Hewlett-Packard driver: amdgpu v: kernel arch: GCN-5 code: Vega
process: GF 14nm built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4
speed: 16 GT/s ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 03:00.0 chip-ID: 1002:164c
class-ID: 0300 temp: 35.0 C
Device-2: Luxvisions Innotech HP TrueVision HD Camera type: USB driver: uvcvideo bus-ID: 1-3:3
chip-ID: 30c9:0013 class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: amdgpu
unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
Monitor-1: eDP-1 mapped: eDP model: AU Optronics 0x5799 built: 2021 res: 1920x1080 hz: 60
dpi: 142 gamma: 1.2 size: 344x194mm (13.54x7.64") diag: 395mm (15.5") ratio: 16:9 modes:
max: 1920x1080 min: 640x480
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: AMD Radeon Graphics (renoir LLVM 15.0.6 DRM 3.49
6.2.14-1-liquorix-amd64) direct-render: Yes
Audio:
Device-1: AMD Renoir Radeon High Definition Audio vendor: Hewlett-Packard driver: snd_hda_intel
v: kernel bus-ID: 1-2:2 pcie: chip-ID: 041e:324d class-ID: 0300 gen: 3 serial: <filter>
speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s bus-ID: 03:00.1 chip-ID: 1002:1637
class-ID: 0403
Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: Hewlett-Packard
driver: snd_rn_pci_acp3x v: kernel alternate: snd_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x,
snd_acp_pci, snd_rpl_pci_acp6x, snd_pci_ps, snd_sof_amd_renoir, snd_sof_amd_rembrandt pcie:
gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s bus-ID: 03:00.5
chip-ID: 1022:15e2 class-ID: 0480
Device-3: AMD Family 17h/19h HD Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel
pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s bus-ID: 03:00.6
chip-ID: 1022:15e3 class-ID: 0403
Device-4: Creative Sound Blaster Play! 3 type: USB driver: hid-generic,snd-usb-audio,usbhid
API: ALSA v: k6.2.14-1-liquorix-amd64 status: kernel-api tools: alsamixer,amixer
Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active
2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8822CE 802.11ac PCIe Wireless Network Adapter vendor: Hewlett-Packard
driver: rtw_8822ce v: N/A modules: rtw88_8822ce,wl pcie: gen: 1 speed: 2.5 GT/s lanes: 1
port: f000 bus-ID: 01:00.0 chip-ID: 10ec:c822 class-ID: 0280
IF: wlan0 state: up mac: <filter>
Bluetooth:
Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 bus-ID: 1-4:4 chip-ID: 0bda:b00c
class-ID: e001 serial: <filter>
Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 3.0 lmp-v: 5.1
sub-v: d2e3 hci-v: 5.1 rev: cc6
Info: acl-mtu: 1021:6 sco-mtu: 255:12 link-policy: rswitch hold sniff park
link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio,
telephony
Drives:
Local Storage: total: 476.94 GiB used: 22.46 GiB (4.7%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: PC SN530 SDBPNPZ-512G-1006
size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD
serial: <filter> rev: HPS2 temp: 28.9 C scheme: GPT
Partition:
ID-1: / raw-size: 476.69 GiB size: 468.13 GiB (98.21%) used: 22.46 GiB (4.8%) fs: ext4
dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 3 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
System Temperatures: cpu: 40.1 C mobo: N/A gpu: amdgpu temp: 34.0 C
Fan Speeds (RPM): fan-1: 0 fan-2: 0
Repos:
Packages: pm: dpkg pkgs: 2093 libs: 1068 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
pkgs: 0 pm: flatpak pkgs: 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 bookworm-updates main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bookworm main non-free
2: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bookworm ahs
Info:
Processes: 270 Uptime: 5h 12m wakeups: 28067 Memory: 7.09 GiB used: 1.95 GiB (27.5%)
Init: SysVinit v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0
alt: 12 Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
Re: After install cannot boot
Posted: Wed Aug 16, 2023 11:37 am
by heydave
Maybe its just me, but I doubt the USB sticks are an issue. And it might be mostly a disk boot corruption causing the BIOS on the laptop to not recognize the boot partition where GRUB sits. Perhaps if possible, use the HP tool to recover the device first back to its original state since none of the current data/MX21/MX23 is needed anyway with the first installation @heydave used when he selected the "whole disk" option and got the "Hard Disk 3F0 Error"?
If the OP wants to try to recover back to original state, he might want to try using the HP Cloud Recovery Tool (if supported). To do this, you have to use another laptop with Windows and access to Microsoft Store, and download the hp cloud recovery tool and follow instructions to put onto a USB stick. Then use the USB stick to recover the first HP laptop back to its factory state.
I did try the built in recovery tool, but it was apparently looking for windows (which was gone). I would like to start over from the original state, but I do not have access to a windows computer.
First, the OP *was* able to boot an MX23 LiveUSB and attempt an install...
Second, AFTER that attempted install, two things were obvious:
1) The LiveUSB disk didnt work again, and
2) There appears to be an install ON the HP nvme - just not booting from it -unless its boot strapped from an option from the OTHER live usb.
So..
a) Something happened to the MX23 live boot! Has there been a Second mx 23 Live boot created and tried out ?
b) Has there been any attempt reset the HP bios and ONLY turn off secure boot, then attempt an MX 23 install again?
On my HP (2023) I had several times when the MX installer would attempt to write to the USB stick on install, and when I didnt catch it, it obviously was a mess and I had to redo the stick.
I did not make a second stick, but the MX23 stick does work as a live USB on another system so not installed onto the USB.
The MX23 NVME (that I get to via MX21 stick/rescue boot) is the one i installed (same user name password etc.).
We did attempt to reset BIOS to original.
So... should I make another MX23 Live USB, reset the BIOS again?
Re: After install cannot boot
Posted: Wed Aug 16, 2023 11:39 am
by CharlesV
j2mcgreg wrote: Wed Aug 16, 2023 11:34 am
heydave wrote: Wed Aug 16, 2023 11:02 am
I just accepted the defaults. I am just a user in over my head. That's why I like MX, it takes care of those things for me.
I think that you should rewrite the MX ISO to your install drive using our Live USB Maker, but this time, prior to the actual write. click on "Show Advanced Options" and then put a check mark beside GPT partitioning. Then let the utility write the ISO. Once it's complete, use the drive to reinstall MX using the "Automatic Install using entire drive" option on your laptop. That's how I set up Live USB Maker when I put MX 23 on my HP 15. By way of proof that it works, here's the QSI for my HP 15:
+1 ( My HP : HP ENVY x360 2-in-1 Laptop 15-ew0xxx 2/2023 )
Yes, new MX 23 live boot, reset bios, only secure boot off.
Re: After install cannot boot
Posted: Wed Aug 16, 2023 11:49 am
by heydave
Headed to my other system to make the USB... Fingers crossed...
Re: After install cannot boot
Posted: Wed Aug 16, 2023 1:28 pm
by heydave
I think that you should rewrite the MX ISO to your install drive using our Live USB Maker, but this time, prior to the actual write. click on "Show Advanced Options" and then put a check mark beside GPT partitioning. Then let the utility write the ISO. Once it's complete, use the drive to reinstall MX using the "Automatic Install using entire drive" option on your laptop. That's how I set up Live USB Maker when I put MX 23 on my HP 15. By way of proof that it works, here's the QSI for my HP 15:
I did as you suggested. It booted from the new MX23 stick. I installed using full disk option. successfully completed.
When i tried to reboot the hard drive ( or nve or ?) it still went to message cant find boot device please install an operating system.
I can, however now get the MX23 USB to boot, and get to the boot rescue from there. from there I can select and boot into the hard drive as normal.
Re: After install cannot boot
Posted: Wed Aug 16, 2023 1:36 pm
by Charlie Brown
heydave wrote: Wed Aug 16, 2023 1:28 pm... it still went to message cant find boot device...
Just a stupid question: It shows no Grub menu, right? Directly and only that message when you press the power button ...
Re: After install cannot boot
Posted: Wed Aug 16, 2023 1:37 pm
by heydave
No Grub just a prolonged black the the blue error window,
Re: After install cannot boot
Posted: Wed Aug 16, 2023 1:38 pm
by Charlie Brown
It's probably a setting in Bios, but what ...
Re: After install cannot boot
Posted: Wed Aug 16, 2023 1:39 pm
by heydave
And in this BIOS, there are so few things to even change. Seems very limited options, and nothing my uneducated eye even relates much to the boot other than the secure boot - which is definitely disabled.
Re: After install cannot boot
Posted: Wed Aug 16, 2023 1:40 pm
by j2mcgreg
Just on the off chance that the bios is fixated on your USB drive, check the boot order and ensure that the NVMe is given first priority.
Re: After install cannot boot
Posted: Wed Aug 16, 2023 1:42 pm
by Charlie Brown
Maybe a workaround is needed for now: Install Grub somewhere else (i.e. on the usb stick) and keep the usb stick attached when (before) booting ... Or so ...
Re: After install cannot boot
Posted: Wed Aug 16, 2023 1:43 pm
by razor2021
For me, that still points to the main disk which as indicated from prior posts as some sort of flash mobile drive type --> KLUDG4UHGC-B0E1 (<- this serial number must be someone's idea of fun?)
If it was a SSD, it would be easy to reformat in another laptop and possibly correct it (would involve removing it and inserting into another laptop etc.). I would still lean to prepping a USB stick for the HP Cloud recovery tool using another Windows desktop/laptop machine, and see if it can then be used to fix the flash drive on this HP laptop. There must be some area on the flash that's corrupted from the first install. If this full install did not recover it, there must be some area on the mobile flash drive that is not seen/touched. In theory, the Windows and disk drivers would know how to deal with this corruption on the mobile flash drive for your laptop. Again, just my 2 cents. Hope there is an easier route, of course ...
Re: After install cannot boot
Posted: Wed Aug 16, 2023 1:46 pm
by Charlie Brown
razor2021 wrote: Wed Aug 16, 2023 1:43 pm... would be easy to reformat in another laptop ...
Live usb boots fine.
Re: After install cannot boot
Posted: Wed Aug 16, 2023 1:48 pm
by razor2021
Charlie Brown wrote: Wed Aug 16, 2023 1:46 pm
razor2021 wrote: Wed Aug 16, 2023 1:43 pm... would be easy to reformat in another laptop ...
Live usb boots fine.
Yes, I meant the internal mobile flash drive - which is the main storage that's he's formatting for the whole disk. Normally, its a removable SSD, NVME or HDD. In this case, the serial says its some sort of mobile flash drive. Not sure if this is removable or soldered on motherboard.
Code: Select all
Drives:
Local Storage: total: 352.07 GiB used: 8.42 GiB (2.4%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 model: KLUDG4UHGC-B0E1 size: 119.2 GiB block-size: physical: 4096 B
logical: 4096 B type: N/A serial: N/A rev: 1001 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: SanDisk model: USB 3.2Gen1 size: 232.88 GiB
block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 1.00 scheme: MBR
Re: After install cannot boot
Posted: Wed Aug 16, 2023 1:49 pm
by Charlie Brown
Yep. I just mean, it could also be done on live session (formatting etc.)
Re: After install cannot boot
Posted: Wed Aug 16, 2023 1:51 pm
by razor2021
Ok, I get what you're saying the KLUDG is the external USB stick.
Re: After install cannot boot
Posted: Wed Aug 16, 2023 1:52 pm
by Charlie Brown
The only thing I wonder is (to make sure whether it's something about the disk):
What happens if you install Windows,
or any other distro,
or at least: manually install MX.
Re: After install cannot boot
Posted: Wed Aug 16, 2023 1:55 pm
by CharlesV
It appears to be plugged into a G4 2Lane interface , so I believe it could be removed... but what are you going to put it into ?
( and could it be replaced with a different nvme or ssd ? )
Or possibly attempt an mx 21 install. (but if grub is not booting .. probably no difference anyway. - talking aloud)
Re: After install cannot boot
Posted: Wed Aug 16, 2023 1:56 pm
by razor2021
Charlie Brown wrote: Wed Aug 16, 2023 1:49 pm
Yep. I just mean, it could also be done on live session (formatting etc.)
Yeah - I only realized that when you guys mentioned it in the above posts ... in a live session, one can do that too. Did not occur to me before when I used to recover older SSDs on my previous installs. Will remember that for future.
Re: After install cannot boot
Posted: Wed Aug 16, 2023 1:57 pm
by heydave
Just on the off chance that the bios is fixated on your USB drive, check the boot order and ensure that the NVMe is given first priority.
Just changed it to give OS sytem first position and Usb 2nd. No change.
Maybe a workaround is needed for now: Install Grub somewhere else (i.e. on the usb stick) and keep the usb stick attached when (before) booting ... Or so ...
Not ideal, but at least it works.
For me, that still points to the main disk which as indicated from prior posts as some sort of flash mobile drive type --> KLUDG4UHGC-B0E1 (<- this serial number must be someone's idea of fun?)
If it was a SSD, it would be easy to reformat in another laptop and possibly correct it (would involve removing it and inserting into another laptop etc.). I would still lean to prepping a USB stick for the HP Cloud recovery tool using another Windows desktop/laptop machine, and see if it can then be used to fix the flash drive on this HP laptop. There must be some area on the flash that's corrupted from the first install. If this full install did not recover it, there must be some area on the mobile flash drive that is not seen/touched. In theory, the Windows and disk drivers would know how to deal with this corruption on the mobile flash drive for your laptop. Again, just my 2 cents. Hope there is an easier route, of course ...
You might be right, but I'm not sure Ican find a windows machine, and I havent even looked at windows in probably a dozen years or more. might be hard for this old dog... :)
Yes, I meant the internal mobile flash drive - which is the main storage that's he's formatting for the whole disk. Normally, its a removable SSD, NVME or HDD. In this case, the serial says its some sort of mobile flash drive. Not sure if this is removable or soldered on motherboard.
I opened the back, and didn't even recognize anything resembling a hard drive, a card or anything removable.
Re: After install cannot boot
Posted: Wed Aug 16, 2023 1:59 pm
by razor2021
CharlesV wrote: Wed Aug 16, 2023 1:55 pm
It appears to be plugged into a G4 2Lane interface , so I believe it could be removed... but what are you going to put it into ?
( and could it be replaced with a different nvme or ssd ? )
Or possibly attempt an mx 21 install. (but if grub is not booting .. probably no difference anyway. - talking aloud)
Yes, either recover removable disk in separate laptop that has an expansion slot, or get a new disk. Cheapest recovery is still the hp recovery tool. Else he would have to boot always from a usb stick. Not a good long term solution.
Re: After install cannot boot
Posted: Wed Aug 16, 2023 1:59 pm
by CharlesV
Off topic, @razor2021 .. your tag line is wanting me to start pushing some one-liners...
You know your a dino if...
( I shall refrain - sorry.. too much coffee this am ! ;-p )
Re: After install cannot boot
Posted: Wed Aug 16, 2023 2:00 pm
by razor2021
heydave wrote: Wed Aug 16, 2023 1:57 pm
...
I opened the back, and didn't even recognize anything resembling a hard drive, a card or anything removable.
There's a drive there, its possibly under the keyboard. I looked for a Youtube vid with this specs, the closest I found was this ->
https://www.youtube.com/watch?v=YYRxT98ulfs
Re: After install cannot boot
Posted: Wed Aug 16, 2023 2:01 pm
by heydave
Ok, I get what you're saying the KLUDG is the external USB stick.
I think KLUDG is the internal "drive"
Re: After install cannot boot
Posted: Wed Aug 16, 2023 2:02 pm
by CharlesV
Specs for that model show storage options: ( this must be that select model ;-/ )
1 TB PCIe® NVMe™ Value M.2 Solid-State Drive
512 GB PCIe® NVMe™ Value M.2 Solid-State Drive
256 GB PCIe® NVMe™ Value M.2 Solid-State Drive
128 GB PCIe® NVMe™ Value M.2 Solid-State Drive
128 GB UFS (available only with select models)
Re: After install cannot boot
Posted: Wed Aug 16, 2023 2:04 pm
by CharlesV
Do you have any type of other slot on the side for an SD chip maybe ? (mine has SD chip slot, and your generic model shows one .)
Possibly that could boot strap you up with grub installed to that?
Re: After install cannot boot
Posted: Wed Aug 16, 2023 2:08 pm
by razor2021
@CharlesV is right. A small SD card to bootstrap you for the interim. The KLUDG4U is a UFS chip that must be soldered onto the motherboard. This link shows no interface that can be plugged in -->
https://semiconductor.samsung.com/estor ... uhdc-b0e1/
Re: After install cannot boot
Posted: Wed Aug 16, 2023 2:12 pm
by heydave
Specs for that model show storage options: ( this must be that select model ;-/ )
1 TB PCIe® NVMe™ Value M.2 Solid-State Drive
512 GB PCIe® NVMe™ Value M.2 Solid-State Drive
256 GB PCIe® NVMe™ Value M.2 Solid-State Drive
128 GB PCIe® NVMe™ Value M.2 Solid-State Drive
128 GB UFS (available only with select models)
Confirmed "select Model". I am a lucky guy to have been selected.
Do you have any type of other slot on the side for an SD chip maybe ? (mine has SD chip slot, and your generic model shows one .)
Possibly that could boot strap you up with grub installed to that?
It has only 2 USB ( one of which is taken up by a wireless adapter, since the Realtek wirelesswon't work) it has an HDMI, and A small port (Tyoe C maybe).
It is for my daughter to homeschool, so maybe I could put grub on a small format USB (so she didn't break it. Or I suppose she could just remove it after booting...
Re: After install cannot boot
Posted: Wed Aug 16, 2023 2:15 pm
by heydave
If it has an SD, I cannot find it. Still a lucky guy.
Re: After install cannot boot
Posted: Wed Aug 16, 2023 2:17 pm
by Charlie Brown
Lads and Lasses , regarding "KLUDG" :
ID-1: /dev/sda maj-min: 8:0 model: KLUDG4UHGC-B0E1 size: 119.2 GiB block-size: physical: 4096 B
logical: 4096 B type: N/A serial: N/A rev: 1001 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: SanDisk model: USB 3.2Gen1 size: 232.88 GiB
block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 1.00 scheme: MBR
Partition:
ID-1: / raw-size: 118.94 GiB size: 116.52 GiB (97.96%) used: 8.42 GiB (7.2%) fs: ext4
dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 256 MiB size: 255.3 MiB (99.73%) used: 4 KiB (0.0%) fs: vfat
dev: /dev/sda1 maj-min: 8:1
Re: After install cannot boot
Posted: Wed Aug 16, 2023 2:21 pm
by heydave
Don't know if it matters, but here is the QSI with the new USB Drive with MX23.
Code: Select all
System:
Kernel: 6.1.0-10-amd64 [6.1.38-2] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-10-amd64 root=UUID=<filter> ro quiet splash
Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
dm: LightDM v: 1.26.0 Distro: MX-23_x64 Libretto July 31 2023 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Laptop System: HP product: HP Laptop 15-fd0xxx v: N/A serial: <superuser required> Chassis:
type: 10 serial: <superuser required>
Mobo: HP model: 8B36 v: 62.21 serial: <superuser required> UEFI: AMI v: F.03 date: 03/06/2023
Battery:
ID-1: BAT0 charge: 42.9 Wh (100.0%) condition: 42.9/41.0 Wh (104.5%) volts: 13.0 min: 11.2
model: HP Primary type: Li-ion serial: <filter> status: full cycles: 2
CPU:
Info: model: Intel N200 bits: 64 type: MCP arch: Alder Lake level: v3 note: check built: 2021+
process: Intel 7 (10nm ESF) family: 6 model-id: 0xBE (190) stepping: 0 microcode: 0x10
Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 384 KiB desc: d-4x32 KiB; i-4x64 KiB
L2: 2 MiB desc: 1x2 MiB L3: 6 MiB desc: 1x6 MiB
Speed (MHz): avg: 962 high: 975 min/max: 800/3700 scaling: driver: intel_pstate
governor: powersave cores: 1: 946 2: 975 3: 964 4: 964 bogomips: 7987
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
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: Enhanced IBRS, IBPB: conditional, RSB filling, PBRSB-eIBRS: Not
affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel Alder Lake-N [UHD Graphics] vendor: Hewlett-Packard driver: i915 v: kernel
arch: Gen-12.2 process: Intel 10nm built: 2021-22+ ports: active: eDP-1 empty: HDMI-A-1
bus-ID: 00:02.0 chip-ID: 8086:46d0 class-ID: 0300
Device-2: Cheng Uei Precision Industry (Foxlink) HP True Vision HD Camera type: USB
driver: uvcvideo bus-ID: 1-3:4 chip-ID: 05c8:0b08 class-ID: fe01 serial: <filter>
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99") s-diag: 414mm (16.31")
Monitor-1: eDP-1 model: ChiMei InnoLux 0x1541 built: 2021 res: 1366x768 hz: 60 dpi: 101
gamma: 1.2 size: 344x193mm (13.54x7.6") diag: 394mm (15.5") ratio: 16:9 modes: 1366x768
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel Graphics (ADL-N) direct-render: Yes
Audio:
Device-1: Intel vendor: Hewlett-Packard driver: sof-audio-pci-intel-tgl
alternate: snd_hda_intel,snd_sof_pci_intel_tgl bus-ID: 00:1f.3 chip-ID: 8086:54c8 class-ID: 0401
API: ALSA v: k6.1.0-10-amd64 status: kernel-api tools: alsamixer,amixer
Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active
2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek vendor: Hewlett-Packard driver: N/A modules: wl pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: 3000 bus-ID: 01:00.0 chip-ID: 10ec:b85b class-ID: 0280
Device-2: Ralink MT7601U Wireless Adapter type: USB driver: mt7601u bus-ID: 1-2:3
chip-ID: 148f:7601 class-ID: 0000 serial: <filter>
IF: wlan0 state: up mac: <filter>
Bluetooth:
Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 bus-ID: 1-8:5 chip-ID: 0bda:b85d
class-ID: e001 serial: <filter>
Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2
sub-v: 91cb hci-v: 5.2 rev: dfb7
Info: acl-mtu: 1021:6 sco-mtu: 255:12 link-policy: rswitch hold sniff park
link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio,
telephony
Drives:
Local Storage: total: 147.87 GiB used: 8.44 GiB (5.7%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 model: KLUDG4UHGC-B0E1 size: 119.2 GiB block-size: physical: 4096 B
logical: 4096 B type: N/A serial: N/A rev: 1001 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: SanDisk model: Cruzer Glide size: 28.67 GiB
block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 1.00 scheme: GPT
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 49.96 GiB size: 48.87 GiB (97.83%) used: 8.36 GiB (17.1%) fs: ext4
dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 256 MiB size: 255.3 MiB (99.73%) used: 288 KiB (0.1%) fs: vfat
dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 68.99 GiB size: 67.35 GiB (97.63%) used: 85.3 MiB (0.1%) fs: ext4
dev: /dev/sda3 maj-min: 8:3
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
System Temperatures: cpu: 54.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos:
Packages: pm: dpkg pkgs: 2062 libs: 1047 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
pkgs: 0 pm: flatpak pkgs: 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 bookworm-updates main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bookworm main non-free
Info:
Processes: 212 Uptime: 33m wakeups: 14 Memory: 3.49 GiB used: 1.65 GiB (47.2%) Init: SysVinit
v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12 Client: shell wrapper
v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
Re: After install cannot boot [Solved]
Posted: Wed Aug 16, 2023 2:26 pm
by Charlie Brown
In the meantime, you can even install it to that SanDisk model: USB 3.2 (and even encrypt). Since it's 3.2 it won't be slow and you can carry in your pocket/keyring :D
Re: After install cannot boot
Posted: Wed Aug 16, 2023 2:33 pm
by heydave
I reckon that's what we'll have to do. I guess I should have bought an old machine and MXed it up. Would have been cheaper and better. WallyWorld wins again.
I want to thank you and everyone for the help in this thing. I means a lot, and for what it is worth, in the rural community i live in, with lots of older folks and limited incomes, I have been and will continue to push MX. I discovered you on MX19 and quickly switched from "another distro" which I had previously set folks up with. It is still ok, But MX is better, simpler and more useful.
The time you all gave me to try to fix this I cannot repay.
Thank You all Again.
Re: After install cannot boot
Posted: Wed Aug 16, 2023 2:38 pm
by Charlie Brown
You're always welcome.
Just, we don't know whether there's something with the disk.. So, later and when you don't feel lazy you can try installing something else, as above, just to see whether the disk boots then...
Also on live session you can run GSmartControl from menu, nothing to lose ...
Thank you, too for trying all the suggestions, these are so valuable feedback to devs.
Re: After install cannot boot
Posted: Wed Aug 16, 2023 2:43 pm
by CharlesV
Yes indeed some VERY useful info here.
Just an fyi - This machine appears to be this one from walmart
HP 15.6", Intel Processor N200 (Pentium) 4GB RAM, 128GB UFS, Scarlet Red, Windows 11 Home in S Mode, 15-fd0083wm
Re: After install cannot boot
Posted: Wed Aug 16, 2023 2:45 pm
by heydave
Yeah, I hate to bail on you, but I have to get to my much neglected chores. I will have to look at GSmartControl as I don't know what it is.
I am sorry we did not get more information for the MX team, but my uneducated 2 cents figures it is something to do with the UFS not really being a drive in the sense that it is some CHEAP work around, and perhaps the boot is somehow directly so it won't look elsewhere. My uneducated guess.
If I do get any answers for you, do I post on this thread, or somewhere else?
Re: After install cannot boot
Posted: Wed Aug 16, 2023 2:47 pm
by heydave
Just an fyi - This machine appears to be this one from walmart
HP 15.6", Intel Processor N200 (Pentium) 4GB RAM, 128GB UFS, Scarlet Red, Windows 11 Home in S Mode, 15-fd0083wm
It is true. The mistake that started it all.
Re: After install cannot boot
Posted: Wed Aug 16, 2023 2:51 pm
by Charlie Brown
heydave wrote: Wed Aug 16, 2023 2:45 pm...If I do get any answers for you, do I post on this thread, or somewhere else?..
Any way you like.. this thread may be , it'll stay open (not locked by admins).
But, don't be disappointed, as we don't know why it cannot boot, maybe there's still a setting we're missing. (If the drive was completely faulty/broken it wouldn't boot indirectly, wouldn't let you format, install etc...)
Re: After install cannot boot
Posted: Wed Aug 16, 2023 6:22 pm
by MXRobo
Wild shot in the dark: [for others with more knowledge]
https://www.ibiblio.org/oswg/oswg-night ... ivers.html
Search bios, the 4th bios.
=========
https://tldp.org/HOWTO/html_single/LILO/
#5
Beforehand:
