MX Linux Forum

Posted: **Fri Jan 17, 2025 12:11 pm**

I am hoping to be able to use an external SSD to have an MX 23 environment to fiddle with. I thought I was doing the right things by using an MX 23 Live USB and directing the install to an old 256 GB SATA SSD via USB. It seemed to partition, format, and install MX but it won't boot.

I've tried changing the BIOS settings for enabling*/disabling Legacy USB support, enabling/disabling* UEFI boot mode, and moving the USB/SSD up the boot order to the top, and it still won't boot. In fact, the machine won't boot at all when the SSD is plugged in, OR it ignores it and goes to the internal drive. Don't know much about fiddling with BIOS or boot options.

(* == normal setting.)

Any ideas or suggestions?

QSI:

Code: Select all

Snapshot created on: 20240214_0932
System:    Kernel: 6.12.6-1-liquorix-amd64 [6.12-7~mx21ahs+1] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: audit=0 intel_pstate=disable amd_pstate=disable 
           BOOT_IMAGE=/boot/vmlinuz-6.12.6-1-liquorix-amd64 root=UUID=<filter> ro quiet splash 
           i915.i915_enable_fbc=1 i915.lvds_downclock=1 drm.vblankoffdelay=1 
           cpufreq.default_governor=powersave threadirqs zswap.enabled=1 
           Desktop: Xfce 4.18.1 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.18.0 vt: 7 
           dm: LightDM 1.26.0 Distro: MX-21.3_x64 Wildflower October 20  2021 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: SAMSUNG product: RF511/RF411/RF711 v: 10HX serial: <filter> 
           Chassis: type: 9 serial: <filter> 
           Mobo: SAMSUNG model: RF511/RF411/RF711 v: 10HX serial: <filter> 
           BIOS: American Megatrends v: 10HX.M034.20110426.SSH date: 04/26/2011 
Battery:   ID-1: BAT1 charge: 35.5 Wh (80.0%) condition: 44.4/48.8 Wh (90.9%) volts: 10.7 
           min: 11.1 model: SAMSUNG Electronics type: Li-ion serial: N/A status: Not charging 
           Device-1: hidpp_battery_0 model: Logitech ERGO M575 Trackball serial: <filter> 
           charge: 30% rechargeable: yes status: N/A 
CPU:       Info: Quad Core model: Intel Core i7-2630QM bits: 64 type: MT MCP arch: Sandy Bridge 
           family: 6 model-id: 2A (42) stepping: 7 microcode: 2F cache: L2: 6 MiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31927 
           Speed: 1067 MHz min/max: 800/2001 MHz boost: disabled Core speeds (MHz): 1: 1995 
           2: 1995 3: 960 4: 1443 5: 900 6: 1995 7: 800 8: 900 
           Vulnerabilities: Type: gather_data_sampling status: Not affected 
           Type: itlb_multihit status: KVM: Split huge pages 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: mmio_stale_data status: Unknown: No mitigations 
           Type: reg_file_data_sampling status: Not affected 
           Type: retbleed status: Not affected 
           Type: spec_rstack_overflow status: Not affected 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW; STIBP: 
           conditional; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics 
           vendor: Samsung Co driver: i915 v: kernel bus-ID: 00:02.0 chip-ID: 8086:0116 
           class-ID: 0300 
           Device-2: NVIDIA GF108M [GeForce GT 540M] driver: nvidia v: 390.157 bus-ID: 01:00.0 
           chip-ID: 10de:0df4 class-ID: 0302 
           Device-3: Silicon Motion WebCam SCB-1100N type: USB driver: uvcvideo bus-ID: 2-1.1:3 
           chip-ID: 2232:1008 class-ID: 0e02 
           Display: x11 server: X.Org 1.20.14 compositor: xfwm4 v: 4.18.0 driver: 
           loaded: modesetting unloaded: fbdev,vesa display-ID: :0.0 screens: 1 
           Screen-1: 0 s-res: 1600x2820 s-dpi: 96 s-size: 423x746mm (16.7x29.4") 
           s-diag: 858mm (33.8") 
           Monitor-1: LVDS-1 res: 1600x900 hz: 60 dpi: 106 size: 382x215mm (15.0x8.5") 
           diag: 438mm (17.3") 
           Monitor-2: VGA-1 res: 1080x1920 hz: 60 
           OpenGL: renderer: Mesa Intel HD Graphics 3000 (SNB GT2) v: 3.3 Mesa 22.0.5 
           compat-v: 3.1 direct render: Yes 
Audio:     Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: Samsung Co 
           driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1c20 class-ID: 0403 
           Device-2: NVIDIA GF108 High Definition Audio driver: snd_hda_intel v: kernel 
           bus-ID: 01:00.1 chip-ID: 10de:0bea class-ID: 0403 
           Device-3: Tenx USB AUDIO type: USB driver: hid-generic,snd-usb-audio,usbhid 
           bus-ID: 1-1:2 chip-ID: 1130:1620 class-ID: 0300 
           Device-4: AKAI MPKmini2 type: USB driver: hid-generic,snd-usb-audio,usbhid 
           bus-ID: 1-2.2:4 chip-ID: 2011:0715 class-ID: 0103 serial: <filter> 
           Sound Server-1: ALSA v: k6.12.6-1-liquorix-amd64 running: yes 
           Sound Server-2: JACK v: 1.9.21 running: no 
           Sound Server-3: PulseAudio v: 14.2 running: no 
           Sound Server-4: PipeWire v: 0.3.58 running: yes 
Network:   Device-1: Broadcom BCM4313 802.11bgn Wireless Network Adapter vendor: Askey driver: wl 
           v: kernel modules: bcma port: e040 bus-ID: 02:00.0 chip-ID: 14e4:4727 class-ID: 0280 
           IF: wlan0 state: up mac: <filter> 
           Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Samsung Co 
           driver: r8169 v: kernel port: b000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200 
           IF: eth0 state: down mac: <filter> 
Drives:    Local Storage: total: 2.96 TiB used: 355.68 GiB (11.7%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB 
           block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> 
           rev: 2B6Q scheme: MBR 
           ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: Seagate model: BUP Slim BK 
           size: 1.82 TiB block-size: physical: 4096 B logical: 512 B type: N/A serial: <filter> 
           rev: 0109 scheme: GPT 
           ID-3: /dev/sdc maj-min: 8:32 type: USB vendor: Sabrent model: SABRENT size: 238.47 GiB 
           block-size: physical: 4096 B logical: 512 B type: N/A serial: <filter> rev: 0204 
           scheme: MBR 
Partition: ID-1: / raw-size: 456.78 GiB size: 448.54 GiB (98.20%) used: 144.26 GiB (32.2%) 
           fs: ext4 dev: /dev/sda5 maj-min: 8:5 
Swap:      Kernel: swappiness: 10 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 7.81 GiB used: 0 KiB (0.0%) priority: -2 
           dev: /dev/sda6 maj-min: 8:6 
Sensors:   System Temperatures: cpu: 60.0 C mobo: 60.0 C 
           Fan Speeds (RPM): N/A 
Repos:     Packages: 3240 note: see --pkg apt: 3204 lib: 1619 flatpak: 36 
           No active apt repos in: /etc/apt/sources.list 
           No active apt repos in: /etc/apt/sources.list.d/bluemail.list 
           Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list 
           1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ bullseye main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
           1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
           No active apt repos in: /etc/apt/sources.list.d/microsoft-edge.list 
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://ftp.osuosl.org/pub/mxlinux/mx/repo/ bullseye main non-free
           2: deb http://ftp.osuosl.org/pub/mxlinux/mx/repo/ bullseye ahs
           No active apt repos in: /etc/apt/sources.list.d/spotify.list 
           Active apt repos in: /etc/apt/sources.list.d/extrepo_librewolf.sources 
           1: deb [arch=amd64 arm64] https://repo.librewolf.net librewolf main
           Active apt repos in: /etc/apt/sources.list.d/winehq-bullseye.sources 
           1: deb [arch=amd64 i386] https://dl.winehq.org/wine-builds/debian bullseye main
Info:      Processes: 343 Uptime: 18m wakeups: 127 Memory: 7.68 GiB used: 3.06 GiB (39.9%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 10.2.1 
           alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06 
Boot Mode: BIOS (legacy, CSM, MBR)

Posted: **Sat Jan 18, 2025 2:02 am**

You might consider running GParted in the live version to check the flags on the external drive. ( partition --> Manage flags)
And you can also check that the installed partitions look appropriate.
From the info above, it looks like your machine can only do a legacy boot. And a 2011 bios is quite old imho.
For a legacy boot <esp> should be unticked, and <boot> ticked, if I remember correctly.
If you can open the dialog box on bootup to select the drive to boot from you can tell if there is a legacy and/or efi boot option for that drive. An inappropriate boot setup will either not be displayed, or may not boot if selected.
Hopefully others have a better idea.

Posted: **Mon Jan 20, 2025 3:25 pm**

Thanks, @Geek3579 ! I got busy with other projects (such as installing MX 23.5 in a partition in my internal SSD) and haven't gotten back to this issue yet. I'll give your suggestion(s) a try. Yes, this is an old -- but reliable!! -- machine. The bios does have UEFI boot support, but it's not enabled. I think I tried enabling it but the external drive still didn't boot (and while it was plugged in, most other boot stuff caused the machine to turn off -- even during bios navigation, not sure what to make of that).

EDIT: okay, looked at the flags on the boot partition on the external SSD and only boot is set. Not sure what all this means!

Posted: **Tue Jan 21, 2025 1:33 am**

Durhammer wrote: Mon Jan 20, 2025 3:25 pm Thanks, @Geek3579 ! I got busy with other projects (such as installing MX 23.5 in a partition in my internal SSD) and haven't gotten back to this issue yet. I'll give your suggestion(s) a try. Yes, this is an old -- but reliable!! -- machine. The bios does have UEFI boot support, but it's not enabled. I think I tried enabling it but the external drive still didn't boot (and while it was plugged in, most other boot stuff caused the machine to turn off -- even during bios navigation, not sure what to make of that).

EDIT: okay, looked at the flags on the boot partition on the external SSD and only boot is set. Not sure what all this means!

I would think that this boot flag is set for a legacy boot, not UEFI. You can change it using Gparted, and if necessary change it back again without affecting anything.

Posted: **Tue Jan 21, 2025 4:00 am**

On 24 Jul 2020, @fehlix wrote up a cool way of installing MX on an external USB drive so that it will boot no matter if running UEFI firmware or from BIOS.

Posted: **Tue Jan 21, 2025 8:30 am**

Antediluvian wrote: Tue Jan 21, 2025 4:00 am On 24 Jul 2020, @fehlix wrote up a cool way of installing MX on an external USB drive so that it will boot no matter if running EFI firmware or from BIOS.

Ah, so it only matters how the USB drive is created/formatted? Ye olde Samsung RF711 here does have UEFI boot but not enabled. I think I already tried booting with it enabled, but only for the external SSD I was trying to boot. Still, I *think* it might have booted up my internal drive Linux just fine. Have to give that a try, but you or @fehlix seem to suggest it's what's on the drive that matters. True? If so, whey kewl! And thanks!

Posted: **Tue Jan 21, 2025 10:52 am**

If you change the BIOS Boot to External Drive as first choice you may get what you want. It worked for me. I had a Samsung portable SSD T7 in my USB C drive port installed with MX 23.5 while I also had an internal NVME with Linux Mint 22.1 on it, sort of a dual boot by choosing which drive to boot from holding down F9 at bootup. Using a Bosgame mini PC.

Posted: **Tue Jan 21, 2025 11:17 am**

Thanks @beardedragon -- for some reason, when I did that before, my computer simply shut down. Maybe formatting the installer USB stick UEFI and GPT will allow it to install on the external (USB) SSD, as the previous couple of posts and link suggest. Gonna have to give it a try....

Posted: **Tue Jan 21, 2025 12:25 pm**

Use EXT4 or EXFat format on "external drive" as well as UEFI.

Posted: **Tue Jan 21, 2025 2:17 pm**

Durhammer wrote: Tue Jan 21, 2025 8:30 am
Antediluvian wrote: Tue Jan 21, 2025 4:00 am On 24 Jul 2020, @fehlix wrote up a cool way of installing MX on an external USB drive so that it will boot no matter if running EFI firmware or from BIOS.
Ah, so it only matters how the USB drive is created/formatted? Ye olde Samsung RF711 here does have UEFI boot but not enabled. I think I already tried booting with it enabled, but only for the external SSD I was trying to boot. Still, I *think* it might have booted up my internal drive Linux just fine. Have to give that a try, but you or @fehlix seem to suggest it's what's on the drive that matters. True? If so, whey kewl! And thanks!

From what you wrote I don't think you have it right. The firmware/BIOS settings of the computer determines the boot type (UEFI or BIOS). If a drive is to boot successfully then the boot type on the drive must be prepared in a way compatible with the firmware/BIOS settings. For example, if the firmware/BIOS settings of the computer are set to UEFI boot only and the drive is set for legacy/BIOS/MBR boot only then the drive won't boot.

The "trick" that fehlix wrote up prepares the external drive for booting either way, that is, no matter what the firmware/BIOS of the computer is set to the drive will boot (provides you select that drive from the boot order). This makes is easier to use your external drive on different computers, for example.

Posted: **Wed Jan 22, 2025 10:38 am**

Sheesh, I really bothched the first attempt at doing this the way @fehlix wrote up, namely because I let the installer reboot before doing the stuff after the "don't reboot" note. And somehow, I seem to have buggered up the USB installer drive such that it won't even finish booting up -- gets to the MX splash screen, then does a shutdown. I suppose I need to re-create the USB live MX installer. Not a big biggie. (But if there's a way to rescue the USB stick, that would work also.)

However, the other problem encountered during the first-first install of MX to the external SSD failed due to thermal shutdown. I let the machine sit for an hour or so then booted up and did the second-first install, which managed to complete. This thermal business is all due to the #$% Nvidia Optimus crap on my laptop, and can only be shut down by installing the acpi_call package, using modprobe to insert it, and then running the included script that does a slew of attempts to shut off the card. On mine, two of them work. So the question is, is there some way to bake this into the USB MX installer, either via persistence, or by connecting the laptop to ethernet (or use my Android tablet's wifi tethering) and doing the above work prior to firing up the installation itself?

On a related note, I was curious about rEFInd, and saw @fehlix's comments about putting it on your internal SSD in this post. However, it requires that my internal SSD be one set up with GPT and an ESP. Currently, mine is a BIOS boot setup with three partitions -- MBR, spare, and one large extended partition. Can this somehow be changed over to GPT/ESP without clobbering my logical partitions? As you might guess, I am a real idiot when it comes to all this partitioning and booting stuff. Slooowly and imperfectly learning.

Posted: **Fri Jan 24, 2025 12:21 am**

I had time to make the drive per fehlix's July 2020 post and test it. An older HP P3-1394 (UEFI) and Dell N7010 (MBR only PC) were used. The disk, 'SSD 64GB' was created on the latter.

I then reformatted that post into a How-To form and added a few pics for those that text only doc's grind their gears. Making a bootable external USB drive with MX Linux installed PDF 154 Kb.

HP P2-1394 (UEFI)

Code: Select all

System:
  Kernel: 6.1.0-30-amd64 [6.1.124-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-30-amd64 root=UUID=<filter> ro quiet splash
  Desktop: Xfce v: 4.20.0 tk: Gtk v: 3.24.38 info: xfce4-panel wm: xfwm v: 4.20.0 vt: 7
    dm: LightDM v: 1.32.0 Distro: MX-23.5_x64 Libretto Jan 12  2025 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Desktop System: Hewlett-Packard product: p2-1394 v: 1.00 serial: <superuser required>
    Chassis: type: 3 serial: <superuser required>
  Mobo: PEGATRON model: 2AE2 v: 1.02 serial: <superuser required> UEFI: AMI v: 8.06
    date: 08/15/2012
CPU:
  Info: model: Intel Core i3-2120T bits: 64 type: MT MCP arch: Sandy Bridge gen: core 2 level: v2
    built: 2010-12 process: Intel 32nm family: 6 model-id: 0x2A (42) stepping: 7 microcode: 0x2F
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
    desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
  Speed (MHz): avg: 2237 high: 2258 min/max: 1600/2600 scaling: driver: intel_cpufreq
    governor: ondemand cores: 1: 2258 2: 2234 3: 2228 4: 2230 bogomips: 20752
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW; STIBP: conditional; RSB
    filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: Hewlett-Packard
    driver: i915 v: kernel arch: Gen-6 code: Sandybridge process: Intel 32nm built: 2011 ports:
    active: VGA-1 empty: DP-1,HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:0102 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.20.0 driver: X: loaded: intel
    dri: crocus gpu: i915 display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1024x768 s-dpi: 96 s-size: 271x204mm (10.67x8.03") s-diag: 339mm (13.35")
  Monitor-1: VGA-1 mapped: VGA1 res: 1024x768 hz: 60 size: N/A modes: max: 1024x768 min: 640x480
  API: OpenGL v: 3.3 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 2000 (SNB GT1)
    direct-render: Yes
Audio:
  Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: Hewlett-Packard 6
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1c20 class-ID: 0403
  API: ALSA v: k6.1.0-30-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 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: Qualcomm Atheros AR8152 v2.0 Fast Ethernet vendor: Hewlett-Packard driver: atl1c
    v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 02:00.0 chip-ID: 1969:2062
    class-ID: 0200
  IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
  Device-2: Realtek 802.11ac NIC type: USB driver: rtl8821cu bus-ID: 2-1.4:4 chip-ID: 0bda:c811
    class-ID: 0000 serial: <filter>
  IF: wlan0 state: dormant mac: <filter>
Drives:
  Local Storage: total: 171.42 GiB used: 10.78 GiB (6.3%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 type: USB model: SSD 64GB size: 59.63 GiB block-size:
    physical: 512 B logical: 512 B type: SSD serial: <filter> scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Fanxiang model: S101 120GB size: 111.79 GiB block-size:
    physical: 512 B logical: 512 B speed: 3.0 Gb/s type: SSD serial: <filter> rev: A25D scheme: GPT
Partition:
  ID-1: / raw-size: 59.12 GiB size: 57.9 GiB (97.92%) used: 10.78 GiB (18.6%) fs: ext4
    dev: /dev/sda3 maj-min: 8:3
  ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%) used: 288 KiB (0.1%) fs: vfat
    dev: /dev/sda2 maj-min: 8:2
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: 26.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 2137 libs: 1065 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://mirror.math.princeton.edu/pub/mxlinux/mx/repo/ bookworm main non-free
Info:
  Processes: 223 Uptime: 30m wakeups: 1 Memory: 7.62 GiB used: 1.64 GiB (21.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

Dell N7010 (MBR only)

Code: Select all

System:
  Kernel: 6.1.0-30-amd64 [6.1.124-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-30-amd64 root=UUID=<filter> ro quiet splash
  Desktop: Xfce v: 4.20.0 tk: Gtk v: 3.24.38 info: xfce4-panel wm: xfwm v: 4.20.0 vt: 7
    dm: LightDM v: 1.32.0 Distro: MX-23.5_x64 Libretto Jan 12  2025 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Portable System: Dell product: Inspiron N7010 v: A11 serial: <superuser required>
  Mobo: Dell model: 08VFX1 v: A11 serial: <superuser required> BIOS: Dell v: A11 date: 03/31/2011
Battery:
  ID-1: BAT0 charge: 5.4 Wh (100.0%) condition: 5.4/5.3 Wh (100.7%) volts: 11.2 min: 11.1
    model: PANASONIC Dell type: Li-ion serial: <filter> status: full
CPU:
  Info: model: Intel Core i5 M 460 bits: 64 type: MT MCP arch: Westmere gen: core 1 level: v2
    built: 2010-11 process: Intel 32nm family: 6 model-id: 0x25 (37) stepping: 5 microcode: 0x7
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
    desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
  Speed (MHz): avg: 1656 high: 1775 min/max: 1199/2534 boost: enabled scaling:
    driver: acpi-cpufreq governor: ondemand cores: 1: 1775 2: 1639 3: 1615 4: 1596 bogomips: 20217
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW; STIBP: conditional; RSB
    filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel Core Processor Integrated Graphics vendor: Dell driver: i915 v: kernel
    arch: Gen-5.75 process: Intel 45nm built: 2010 ports: active: LVDS-1 empty: DP-1,HDMI-A-1,VGA-1
    bus-ID: 00:02.0 chip-ID: 8086:0046 class-ID: 0300
  Device-2: Microdia 1.3 MPixel Integrated Webcam type: USB driver: uvcvideo bus-ID: 1-1.4:3
    chip-ID: 0c45:641d class-ID: 0e02
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.20.0 driver: X: loaded: intel
    dri: crocus gpu: i915 display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1600x900 s-dpi: 96 s-size: 424x239mm (16.69x9.41") s-diag: 487mm (19.16")
  Monitor-1: LVDS-1 mapped: LVDS1 model: Seiko Epson 0x544b built: 2009 res: 1600x900 hz: 60
    dpi: 106 gamma: 1.2 size: 382x215mm (15.04x8.46") diag: 438mm (17.3") ratio: 16:9 modes: 1600x900
  API: OpenGL v: 2.1 Mesa 22.3.6 renderer: Mesa Intel HD Graphics (ILK) direct-render: Yes
Audio:
  Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Dell 5 driver: snd_hda_intel
    v: kernel bus-ID: 00:1b.0 chip-ID: 8086:3b56 class-ID: 0403
  API: ALSA v: k6.1.0-30-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 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: Broadcom BCM4313 802.11bgn Wireless Network Adapter vendor: Dell Inspiron M5010 / XPS
    8300 driver: wl v: kernel modules: bcma pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0
    chip-ID: 14e4:4727 class-ID: 0280
  IF: wlan0 state: dormant mac: <filter>
  Device-2: Qualcomm Atheros AR8152 v1.1 Fast Ethernet vendor: Dell driver: atl1c v: kernel pcie:
    gen: 1 speed: 2.5 GT/s lanes: 1 port: 2000 bus-ID: 04:00.0 chip-ID: 1969:2060 class-ID: 0200
  IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 655.8 GiB used: 10.78 GiB (1.6%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: HM641JI size: 596.17 GiB block-size:
    physical: 512 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 5400 serial: <filter> rev: 0003
    scheme: MBR
  ID-2: /dev/sdb maj-min: 8:16 type: USB model: SSD 64GB size: 59.63 GiB block-size:
    physical: 512 B logical: 512 B type: SSD serial: <filter> scheme: GPT
Partition:
  ID-1: / raw-size: 59.12 GiB size: 57.9 GiB (97.92%) used: 10.78 GiB (18.6%) fs: ext4
    dev: /dev/sdb3 maj-min: 8:19
  ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%) used: 288 KiB (0.1%) fs: vfat
    dev: /dev/sdb2 maj-min: 8:18
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.0 C mobo: N/A
  Fan Speeds (RPM): cpu: 2961
Repos:
  Packages: pm: dpkg pkgs: 2137 libs: 1065 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://mirror.math.princeton.edu/pub/mxlinux/mx/repo/ bookworm main non-free
Info:
  Processes: 234 Uptime: 2m wakeups: 2 Memory: 7.56 GiB used: 1.53 GiB (20.2%) 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: BIOS (legacy, CSM, MBR)

The only 'downside' I see so far is the external drive's Grub menu gets all the onboard drive (creating PC) details. I've moved the external drive back and forth between the two above PC's with the only interaction required is bringing up the one-time boot menu and choosing the drive.

Keep in mind that some PCs only detect bootable USBs when they are powered on.

Edit - added disk name 'SSD 64GB' for clarity.

Posted: **Fri Jan 24, 2025 11:09 am**

Thanks, @FullScale4Me!!! I'll give it a try!

EDIT: Aaaaaaarrrrgggghhhh. Okay, I tried it, and I think there "might be" (is) one thing missing in both the original and the new step-by-step writeup. I. e., HOW TO NOT REBOOT. At the end of the installation, the installer GUI has a "Finish" button, which, if clicked, goes straight to rebooting the system, and if there's a way to stop it, I don't know what it is. Maybe what should have been added was to NOT click the "Finish" button??? And then go into the 2.1 and 2.2 steps????

Do I have to repeat the install process again, with whatever intervention steps there might be, or can the last two steps somehow be done after the fact, but again in the Live MX USB environment? @fehlix ? @FullScale4Me ?

At least I didn't experience the thermal shutdown thanks to the prep prior to firing up the installer!

Posted: **Fri Jan 24, 2025 11:51 am**

FullScale4Me wrote: Fri Jan 24, 2025 12:21 am The only 'downside' I see so far is the external drive's Grub menu gets all the onboard drive (creating PC) details. I've moved the external drive back and forth between the two above PC's with the only interaction required is bringing up the one-time boot menu and choosing the drive.

Disable OS-prober , easiest with

Code: Select all

sudo chmod -x /etc/grub.d/30_os-prober

so it will only list own entries.

Posted: **Fri Jan 24, 2025 12:29 pm**

Please see my edit to my previous page. How do I prevent the reboot?

Posted: **Fri Jan 24, 2025 12:37 pm**

Durhammer wrote: Fri Jan 24, 2025 12:29 pm Please see my edit to my previous page. How do I prevent the reboot?

Maybe, untick to reboot on the last installer page.

Posted: **Fri Jan 24, 2025 12:50 pm**

Beauty about MX-linux . as to its Other Featured, anti-X version to which likes to work OFF Flash Drive. If by chance you have a couple 32g min but 64g flash drives or > work nicely to operate "MX-Linux" on a Flash Stick.
after Target Flash-drive is completely written " Success "
load or boot to now this "Live" you can also steer the Live to Install to this 2nd Flash no different than how to install to SSD/M2/Spinner. select this Drive and install as normal. Completed you can power the system remove both and reinstall the new Installed Flash with MX
and boot it up like Live and now your running direct off flash drive. I ran various copies and customized each. Surprised that MX shined with this feature.
Everything works the same. Any additional Drives you have seen "Not Mounted" can also be simply clicked by thunar etc to auto-magic mount and your good.
scripting a login to mount or to run when want to listen to you audio or visual content . All the simple to also perform. Per other comment one necessary item is your bios/cmos has the ability to boot from USB. If live worked then any Flash drive should work - a usual ameritrend bios has F8 after you hear the 1st reset "Beep" (caveat sucks by all new Case manufactures many "No Longer" include beep speakers, some Computer stores do sell button speaker that easily place direct on the mobo's "Button led Header")
2nd caveat Backups and snapshots then should be carefully with practice set to external or internal BIG Storage drives. .. cheers ..

Posted: **Fri Jan 24, 2025 3:51 pm**

I updated the How-To document and added the updates cited in this thread.

Making a bootable external USB drive with MX Linux installed PDF, 154 Kb, updated: 24 January 2025.

Posted: **Fri Jan 24, 2025 5:14 pm**

Thanks. @fehlix, @atomick, and @FullScale4Me . I'll give it a try,

Sooo.... no way to do this without a re-re-reinstall? Sigh.....

EDIT: NOW I see why I missed that checkbox -- prior to this, all the focus of action was in the middle section (setting up user name, etc.) and at the bottom ("Close" ... "Next" ... etc.), and THIS THING is at the TOP. Ahem -- not the best design/layout choice, IMHO.

EDIT #2: Done with the installation, the install MBR grub, the install ESP grub, and the RE-install of the MBR grub (@FullScale4Me, might actually want to make this a 2.3 block of instructions for idjits like me!).

Let's see if it works. Thanks, everyone!

Posted: **Fri Jan 24, 2025 5:45 pm**

Durhammer wrote: Fri Jan 24, 2025 5:14 pm Sooo.... no way to do this without a re-re-reinstall? Sigh.....

Sure, no need to reinstall.
Reboot with LiveUSB, and -reinstall grub-boot loader into MBR of the drive.
Also note: MBR/DOS partition table is good for "legacy" MBR/BIOS boot,
but in case the UEFI-firmware is not too buggy, booting in UEFI-mode from
a DOS/MBR drive is supposed to work. But make sure you set the "esp", flag on the created ESP.
When booting in UEFI mode you would have at least 2 associated Boot entries
with the UEFI-boot loader/boot options list on the SSD.
The one "MX Linux" which the installer has created on the ESP under /EFI/mx/grubx64.efi
and another one with listed as something "Drive/Manufacture", that's the fallback entry generated dynamically
every boot by the UEFI firmeware located on ESP under /EFI/Boot/bootx64.efi. The idea of the fallback entry is
incase UEFI-NVRAM have lost memory, you would still have fallback entry to boot from "Drive".
Kind of what legacy BIOS boor is about "boot from Drive" is efffectively boot from MBR.
HTH

Posted: **Fri Jan 24, 2025 6:21 pm**

Thanks, @fehlix. Thanks, @FullScale4Me. And thanks, @atomick -- might be trying your approach next.

The good gnus -- right away, the machine started booting to the new USB SSD Got the new grub menu, it sees all the installations on the hard drive as well -- cool. MUCH BETTER THAN BEFORE, where the system wouldn't even get to the grub menu, it would just halt and catch fire. However....

The bad gnus:

Epic_fail_3.jpg

Any idea what I might have done wrong? This is way above my pay grade and competence, obviously.

Any other suggestions?

Again, thanks for sticking with me. Don Quixote signing off for now....

Posted: **Fri Jan 24, 2025 6:31 pm**

Durhammer wrote: Fri Jan 24, 2025 6:21 pm Thanks, @fehlix. Thanks, @FullScale4Me. And thanks, @atomick -- might be trying your approach next.

The good gnus -- right away, the machine started booting to the new USB SSD Got the new grub menu, it sees all the installations on the hard drive as well -- cool. MUCH BETTER THAN BEFORE, where the system wouldn't even get to the grub menu, it would just halt and catch fire. However....

The bad gnus:

Epic_fail_3.jpg

Any idea what I might have done wrong? This is way above my pay grade and competence, obviously.

Any other suggestions?

Again, thanks for sticking with me. Don Quixote signing off for now....

Boot from LiveUSB.
Mount the rootMX partition e.g with Thunar
post:

Code: Select all

cat /media/demo/*/etc/fstab

and

Code: Select all

sudo cat  /media/demo/*/boot/grub/grub.cfg

and also

Code: Select all

lsblk -f -o +PARTUUID

and

Code: Select all

sudo efibootmgr -v

maybe that's enough.

Posted: **Fri Jan 24, 2025 8:55 pm**

Patience and observe to the steps. perform a couple times and you'll achieve confidence. "i-Ching" phrase.

Code: Select all

 Thru Repetition the Source Becomes Ones Own!

Posted: **Sat Jan 25, 2025 10:38 am**

Thanks, everyone!

Before I rush out and perform the requested diagnostic steps on the USB drives, I have a question. In @FullScale4Me's latest (excellent) iteration of step-by-step (also excellent) instructions from @fehlix, I am wondering about this step within section 2.0 Installing MX Linux:

Code: Select all

5. Disable OS-prober so the Grub menu will only list own entries (vs the PC's internal drives). Type in a terminal window:
'sudo chmod -x /etc/grub.d/30_os-prober' (without ' ')

Am I correct that at the point this is done, you're still in the MX Live USB environment, and not the target USB SSD environment? Wouldn't that have made a difference? If so, should there be an appropriate cd command prior to this?

Posted: **Sat Jan 25, 2025 12:47 pm**

Durhammer wrote: Sat Jan 25, 2025 10:38 am Thanks, everyone!

Before I rush out and perform the requested diagnostic steps on the USB drives, I have a question. In @FullScale4Me's latest (excellent) iteration of step-by-step (also excellent) instructions from @fehlix, I am wondering about this step within section 2.0 Installing MX Linux:
Code: Select all
5. Disable OS-prober so the Grub menu will only list own entries (vs the PC's internal drives). Type in a terminal window:
'sudo chmod -x /etc/grub.d/30_os-prober' (without ' ')
Am I correct that at the point this is done, you're still in the MX Live USB environment, and not the target USB SSD environment? Wouldn't that have made a difference? If so, should there be an appropriate cd command prior to this?

update-grub will only run on a non-Live, i.e. on a "normal" installed system. And os-prober get's triggerd by update-grub, if not disabled.
One most robust way to disable os-prober would by to take away the execution bit, another one to uninstall os-prober.
You can disable os-prober from the booted LiveSystem by running the tool "Chroot Rescue Scan" from the menu,
or on CLI with:

Code: Select all

sudo chroot-rescue-scan

Select the found install you want to visit.
and issue at the "chroot>" prompt

Code: Select all

chmod -x /etc/grub.d/30_os-prober

perhaps follow by

Code: Select all

update-grub

Leave chroot with "exit"

Posted: **Sat Jan 25, 2025 12:51 pm**

"How bizarre, how bizarre...."

Okay, maybe this is bizarre, maybe not. I had done the MX Snapshot in the MX Live USB setting, where I noticed that it seems to say it's a personal snapshot -- there's no checkbox or anything to make any different "kind" of snapshot. I also noticed that the Help file that is displayed when you click the Help button seems to be out of sync with the actual app; in particular, the second screen in the Help file shows and discusses a button to "Edit Configuration File" but that button does not exist in the app itself. Dunno what needs to be done about that. Bug report?

Prior to the snapshot, I had edited the .fluxbox/startup command in the Live USB environment to see if it carried over from boot to boot of same. So I shutdown the computer and proceeded to boot up. The new targeted USB-connected portable SSD also was connected and powered on.

Now, instead of booting into the Live USB environment, I was presented with a grub menu with the new portable SSD's MX 23.4 (at that time), as well as the other bootable OSes on my laptop's SSD (MX 23.5 Xfce, Q4OS, and another MX 23.5 Fluxbox). Dang if the external drive's MX didn't come up!!! I'm updating/upgrading that right now, setting up the stuff to shut off the Nvidia GPU and do the xrandr before firing up Fluxbox itself, but still mystified by it all.

I'm sort of wondering what happens if I don't have the external SSD available when I next boot, or if the Live USB stick isn't also inserted. I'm going to have to check out those things, as well as what happens without either being available at boot (vanilla laptop internal SSD only).

Anyway, success! Not sure about how the external drive will do on another laptop, but I'll check that out, too. (Really not sure what it will do when the USB stick is disconnected, but will check it out also.)

Crazy! New QSI:

Code: Select all

System:
  Kernel: 6.1.0-25-amd64 [6.1.106-3] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-25-amd64 root=UUID=<filter> ro quiet splash
  Desktop: Fluxbox v: 1.3.7 info: tint2 vt: 7 dm: LightDM v: 1.32.0 Distro: MX-23.5_fluxbox_x64
    Libretto September 15 2024 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Laptop System: SAMSUNG product: RF511/RF411/RF711 v: 10HX serial: <superuser required>
    Chassis: type: 9 serial: <superuser required>
  Mobo: SAMSUNG model: RF511/RF411/RF711 v: 10HX serial: <superuser required>
    UEFI: American Megatrends v: 10HX.M034.20110426.SSH date: 04/26/2011
Battery:
  ID-1: BAT1 charge: 35.1 Wh (79.1%) condition: 44.4/48.8 Wh (90.9%) volts: 10.8 min: 11.1
    model: SAMSUNG Electronics type: Li-ion serial: N/A status: not charging
  Device-1: hidpp_battery_0 model: Logitech ERGO M575 Trackball serial: <filter> charge: 100%
    rechargeable: yes status: discharging
CPU:
  Info: model: Intel Core i7-2630QM bits: 64 type: MT MCP arch: Sandy Bridge gen: core 2 level: v2
    built: 2010-12 process: Intel 32nm family: 6 model-id: 0x2A (42) stepping: 7 microcode: 0x2F
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache: L1: 256 KiB
    desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB desc: 1x6 MiB
  Speed (MHz): avg: 1496 high: 1766 min/max: 800/2900 scaling: driver: intel_cpufreq
    governor: ondemand cores: 1: 1439 2: 1624 3: 1591 4: 1436 5: 1333 6: 1472 7: 1766 8: 1308
    bogomips: 31926
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW; STIBP: conditional; RSB
    filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: Samsung Co
    driver: i915 v: kernel arch: Gen-6 code: Sandybridge process: Intel 32nm built: 2011 ports:
    active: LVDS-1,VGA-1 empty: DP-1,HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:0116 class-ID: 0300
  Device-2: NVIDIA GF108M [GeForce GT 540M] vendor: Samsung Co driver: N/A alternate: nouveau
    non-free: series: 390.xx+ status: legacy-active (EOL~late 2022) arch: Fermi code: GF1xx
    process: 40/28nm built: 2010-16 pcie: speed: Unknown lanes: 63 link-max: gen: 6 speed: 64 GT/s
    bus-ID: 01:00.0 chip-ID: 10de:0df4 class-ID: 0302
  Device-3: Silicon Motion WebCam SCB-1100N type: USB driver: uvcvideo bus-ID: 1-1.1:3
    chip-ID: 2232:1008 class-ID: 0e02
  Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: modesetting unloaded: fbdev,vesa
    dri: crocus gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1600x2877 s-dpi: 96 s-size: 422x759mm (16.61x29.88") s-diag: 868mm (34.19")
  Monitor-1: LVDS-1 pos: primary,bottom-l model: ChiMei InnoLux 0x1733 built: 2012 res: 1600x900
    hz: 60 dpi: 106 gamma: 1.2 size: 382x215mm (15.04x8.46") diag: 448mm (17.6") ratio: 16:9
    modes: 1600x900
  Monitor-2: VGA-1 pos: top-right model: Dell P2214H serial: <filter> built: 2015 res: 1080x1920
    hz: 60 dpi: 102 gamma: 1.2 size: 268x477mm (10.55x18.78") diag: 547mm (21.5") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  API: OpenGL v: 3.3 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 3000 (SNB GT2)
    direct-render: Yes
Audio:
  Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: Samsung Co 6
    driver: snd_hda_intel v: kernel bus-ID: 2-1:2 bus-ID: 00:1b.0 chip-ID: 1130:1620 class-ID: 0300
    chip-ID: 8086:1c20 class-ID: 0403
  Device-2: NVIDIA GF108 High Definition Audio driver: snd_hda_intel v: kernel pcie:
    speed: Unknown lanes: 63 link-max: gen: 6 speed: 64 GT/s bus-ID: 01:00.1 chip-ID: 10de:0bea
    class-ID: 0403
  Device-3: Tenx USB AUDIO type: USB driver: hid-generic,snd-usb-audio,usbhid
  Device-4: AKAI MPKmini2 type: USB driver: hid-generic,snd-usb-audio,usbhid bus-ID: 2-2.2:4
    chip-ID: 2011:0715 class-ID: 0103 serial: <filter>
  API: ALSA v: k6.1.0-25-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 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: Broadcom BCM4313 802.11bgn Wireless Network Adapter vendor: Askey driver: wl v: kernel
    modules: bcma pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 02:00.0 chip-ID: 14e4:4727
    class-ID: 0280
  IF: wlan0 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Samsung Co
    driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: b000 bus-ID: 03:00.0
    chip-ID: 10ec:8168 class-ID: 0200
  IF: eth0 state: down mac: <filter>
Bluetooth:
  Device-1: Broadcom BCM2070 Bluetooth Device type: USB driver: btusb v: 0.8 bus-ID: 3-1.3:4
    chip-ID: 0a5c:219c class-ID: fe01 serial: <filter>
  Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 2.0 lmp-v: 3.0
    sub-v: 4203 hci-v: 3.0 rev: 274
  Info: acl-mtu: 1021:8 sco-mtu: 64:1 link-policy: rswitch hold sniff park
    link-mode: peripheral accept service-classes: rendering, capturing, audio, telephony
Drives:
  Local Storage: total: 2.98 TiB used: 8.42 GiB (0.3%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 2B6Q scheme: MBR
  ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: SanDisk model: Cruzer Glide size: 14.59 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?
  ID-3: /dev/sdc maj-min: 8:32 type: USB vendor: Seagate model: BUP Slim BK size: 1.82 TiB
    block-size: physical: 4096 B logical: 512 B type: N/A serial: <filter> rev: 0109 scheme: GPT
  ID-4: /dev/sdd maj-min: 8:48 type: USB vendor: Sabrent model: SABRENT size: 238.47 GiB
    block-size: physical: 4096 B logical: 512 B type: N/A serial: <filter> rev: 0204 scheme: GPT
Partition:
  ID-1: / raw-size: 100 GiB size: 97.87 GiB (97.87%) used: 6.73 GiB (6.9%) fs: ext4 dev: /dev/sdd3
    maj-min: 8:51
  ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%) used: 428 KiB (0.1%) fs: vfat
    dev: /dev/sdd2 maj-min: 8:50
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 12 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sdd4
    maj-min: 8:52
Sensors:
  System Temperatures: cpu: 55.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 1890 libs: 907 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://mirror.math.princeton.edu/pub/mxlinux/mx/repo/ bookworm main non-free
Info:
  Processes: 262 Uptime: 1h 1m wakeups: 16 Memory: 7.67 GiB used: 2.11 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

Posted: **Sat Jan 25, 2025 1:15 pm**

Maybe you are too much adjusting at the same time. Adjusting thr LiveUSb to make it work with you special setup and also the same time external SSD Installtion in a special way work.
I'd probably stick to sort one issue at the time, so at least someone can follow what you are doing...

Posted: **Sat Jan 25, 2025 2:11 pm**

fehlix wrote: Sat Jan 25, 2025 1:15 pm Maybe you are too much adjusting at the same time. Adjusting thr LiveUSb to make it work with you special setup and also the same time external SSD Installtion in a special way work.
I'd probably stick to sort one issue at the time, so at least someone can follow what you are doing...

It was accidental, kind sir.

I was trying to test out the multi-monitor ticket's GPU mods alone, not two things at one time.

I was expecting only the Live USB boot but had not disabled the external SSD.

Some maybe good things are discovered accidentally.

And I do need to do the separate test of having only the external SSD available, not the Live USB.

Posted: **Sat Jan 25, 2025 5:28 pm**

In the words of Alvin the Chipmunk, "all right, Dave!!!"

I do have to adjust the boot device order in BIOS to bring the SSD to the top prior to starting. Not yet sure of what happens if the system is shut down but the SSD is still plugged in. Might work, might not.

The kernel panic issue shown somewhere above has again occurred, but going through the BIOS setup and booting away has fixed it, at least once. Perhaps a timing thing?

So it would seem that I have a workable, bootable, external SSD with MX Linux 23.5 Fluxbox edition up and running. There are Fluxbox issues I'm seeing that I can open a new ticket for if I can't figure it out.

I'm going to test out the SSD on a different computer to see what happens, especially what happens when the Flutzbox startup script tries to set the display but there's no dual monitor. Should be interesting. I bet I need to use --auto in the xrandr command rather than the explicit geometry stuff....

More later, likely!

Thanks to everyone's help, especially @fehlix ! :yourock:

Posted: **Sat Jan 25, 2025 6:35 pm**

Okay, I'd say it's working just peachy. I'm on my widdle HP Stream 13 notebook. Any questions or suggestions before I mark this as SOLVED????

Code: Select all

System:
  Kernel: 6.1.0-30-amd64 [6.1.124-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-30-amd64 root=UUID=<filter> ro quiet splash
  Desktop: Fluxbox v: 1.3.7 info: tint2 vt: 7 dm: LightDM v: 1.32.0 Distro: MX-23.5_fluxbox_x64
    Libretto September 15 2024 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Laptop System: Hewlett-Packard product: HP Stream Notebook PC 13 v: Type1 - ProductConfigId
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: Hewlett-Packard model: 802A v: 56.12 serial: <superuser required> UEFI: Insyde v: F.14
    date: 08/25/2015
Battery:
  ID-1: BAT0 charge: 27.4 Wh (100.0%) condition: 27.4/27.4 Wh (100.0%) volts: 12.6 min: 11.4
    model: Hewlett-Packard Primary type: Li-ion serial: N/A status: full
CPU:
  Info: model: Intel Celeron N2840 bits: 64 type: MCP arch: Silvermont level: v2 built: 2013-15
    process: Intel 22nm family: 6 model-id: 0x37 (55) stepping: 8 microcode: 0x838
  Topology: cpus: 1x cores: 2 smt: <unsupported> cache: L1: 112 KiB desc: d-2x24 KiB; i-2x32 KiB
    L2: 1024 KiB desc: 1x1024 KiB
  Speed (MHz): avg: 597 high: 695 min/max: 500/2582 scaling: driver: intel_cpufreq
    governor: ondemand cores: 1: 500 2: 695 bogomips: 8666
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds mitigation: Clear CPU buffers; SMT disabled
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass status: Not affected
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW; STIBP: disabled; RSB
    filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & Display vendor: Hewlett-Packard
    driver: i915 v: kernel arch: Gen-7 process: Intel 22nm built: 2012-13 ports: active: eDP-1
    empty: DP-1,HDMI-A-1,VGA-1 bus-ID: 00:02.0 chip-ID: 8086:0f31 class-ID: 0300
  Device-2: Chicony HP Truevision HD type: USB driver: uvcvideo bus-ID: 1-1:2 chip-ID: 04f2:b45e
    class-ID: 0e02
  Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: modesetting unloaded: fbdev,vesa
    dri: crocus gpu: i915 display-ID: :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: Seiko Epson 0x3859 built: 2012 res: 1366x768 hz: 60 dpi: 118 gamma: 1.2
    size: 293x165mm (11.54x6.5") diag: 336mm (13.2") ratio: 16:9 modes: 1366x768
  API: OpenGL v: 4.2 Mesa 22.3.6 renderer: Mesa Intel HD Graphics (BYT) direct-render: Yes
Audio:
  Device-1: Intel Atom Processor Z36xxx/Z37xxx Series High Definition Audio vendor: Hewlett-Packard
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:0f04 class-ID: 0403
  API: ALSA v: k6.1.0-30-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 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: Broadcom BCM43142 802.11b/g/n vendor: Hewlett-Packard driver: wl v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 bus-ID: 02:00.0 chip-ID: 14e4:4365 class-ID: 0280
  IF: wlan0 state: up mac: <filter>
Bluetooth:
  Device-1: Broadcom BCM43142A0 Bluetooth Device type: USB driver: btusb v: 0.8 bus-ID: 1-4.3:5
    chip-ID: 0a5c:216c class-ID: fe01 serial: <filter>
  Report: hciconfig ID: hci0 rfk-id: 1 state: down bt-service: N/A rfk-block: hardware: no
    software: no address: <filter>
  Info: acl-mtu: 0:0 sco-mtu: 0:0 link-mode: peripheral accept
Drives:
  Local Storage: total: 386.68 GiB used: 13.63 GiB (3.5%)
  ID-1: /dev/mmcblk0 maj-min: 179:0 vendor: SK Hynix model: HBG4e size: 29.12 GiB block-size:
    physical: 512 B logical: 512 B type: SSD serial: <filter> rev: 0x7 scheme: MBR
  SMART Message: Unknown smartctl error. Unable to generate data.
  ID-2: /dev/mmcblk1 maj-min: 179:768 model: SR128 size: 119.08 GiB block-size: physical: 512 B
    logical: 512 B type: SSD serial: <filter> scheme: MBR
  SMART Message: Unknown smartctl error. Unable to generate data.
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-3: /dev/sda maj-min: 8:0 type: USB vendor: Sabrent model: SABRENT size: 238.47 GiB
    block-size: physical: 4096 B logical: 512 B type: N/A serial: <filter> rev: 0204 scheme: GPT
Partition:
  ID-1: / raw-size: 100 GiB size: 97.87 GiB (97.87%) used: 10.11 GiB (10.3%) fs: ext4
    dev: /dev/sda3 maj-min: 8:3
  ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%) used: 428 KiB (0.1%) fs: vfat
    dev: /dev/sda2 maj-min: 8:2
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 12 GiB used: 3.5 MiB (0.0%) priority: -2 dev: /dev/sda4
    maj-min: 8:4
Sensors:
  System Temperatures: cpu: 37.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: 1983 pm: dpkg pkgs: 1971 libs: 950 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 12
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
    1: deb [arch=amd64 signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg] https://brave-browser-apt-release.s3.brave.com/ stable main
  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://mirror.math.princeton.edu/pub/mxlinux/mx/repo/ bookworm main non-free
Info:
  Processes: 195 Uptime: 3m wakeups: 2 Memory: 1.81 GiB used: 1.28 GiB (70.3%) 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

Posted: **Sat Jan 25, 2025 8:10 pm**

Maybe post also QSI from the other dual-monitor with the left-rotated screen the QSI.
And suggest, to adjust the xrandr line within the startup, this way.
Detect whether both LVDS and VGA monitor are connected and only in this case apply the xrandr command like

Code: Select all

[ "$(xrandr | grep -w connected | grep -c -E '^(LVDS|VGA)')" = "2" ] && xrandr ... hier your long xrand command

which would make the dual-monitor xrandr-command only run when both are connect on the dual-monitor pc.

Posted: **Sat Jan 25, 2025 8:44 pm**

fehlix wrote: Sat Jan 25, 2025 8:10 pm Maybe post also QSI from the other dual-monitor with the left-rotated screen the QSI.
And suggest, to adjust the xrandr line within the startup, this way.
Detect whether both LVDS and VGA monitor are connected and only in this case apply the xrandr command like
Code: Select all
[ "$(xrandr | grep -w connected | grep -c -E '^(LVDS|VGA)')" = "2" ] && xrandr ... hier your long xrand command
which would make the dual-monitor xrandr-command only run when both are connect on the dual-monitor pc.

Hey, interesting idea! Right now, it's working fine on this smaller (13") laptop screen (the Samsung is 17" and the Dell VGA monitor is 22"). I had already switched the xrandr command to use --auto, as mentioned earlier. Everything looks great on the little screen here, but I DID have a psensor window that might have been glued to the VGA monitor. The psensor app shows up in the panel taskbar, but the display is nowhere to be found. I think I had configured it to be frozen where it was. Would your scheme fix this? Thank you for going the extra mile(S)!

EDIT: oh yeah, not quite sure what you mean about the QSI for the "other: dual-monitor setup. I only have one, my main (Samsung) laptop. This little HP Stream 13 only has its 13" lcd display. (And the QSI on the previous page of this post *should* have both monitors.)

Posted: **Sat Jan 25, 2025 8:56 pm**

maybe I thought it was another pc... but any way good it worked

Posted: **Sat Jan 25, 2025 9:03 pm**

fehlix wrote: Sat Jan 25, 2025 8:56 pm maybe I thought it was another pc... but any way good it worked

Me, too! Maybe, though, you and @FullScale4Me should figure out that one point in his (your combined) instructions where you do the chmod to stop the portable SSD grub from seeing any other OSes (though it's not really too much of a detriment, but the instructions might not really do anything as-is?). You guys will have a great document for other folks to use. I sure benefited from the collab!

EDIT: gonna go plug back to the Samsung and see if the psensor window shows up again!

Posted: **Sun Jan 26, 2025 9:35 am**

Think your working with a power supply issue. on this laptop? pg 3 of this endurance shows a boot screen 1st line say zstd compressed data file CORRUPT. The Other thing on the QSI is battery. its showing 11.2 volt min is 11.1 volt but that is the luck part 11.7 really is a cutoff anything lower and your stressing the electronics to expectations it no long can support to perform. fundamentals. If an Flash Drive with Live MX can be booted and try install its writing to install copy of files onto the SSD are not making it 100 % as designed. the SSD USB adaptor should have its own additional 5volt PS powering the adaptor USB plugged in to the port your using.
The Bios if flash and SSD connected and all power should show as usb devices and possibly manufacture name. Normally Laptop Bios are pretty useless for absolute detail yet reverse your USB ports around re- Live Flash and SSD ports around. Would believe there is a Boot Mgr option via F12 or F8 or Esc hold whilst reboot or power on to bring this menu up can you see both the USB-SSD device drive and the Flash Live , these should reveal the manufacture of these devices like Kingston blah blah Seagate or what ever drive is plugged in to use. These simple details can easily be skipped and can reveal what your beating the carpet by to get MX installed.

Boot Flash to Desktop Live. Can you click around the DT and does it all function.
Open Gparted and format this SSD does it succeed and now verify this do all the details reveal factor of the drive info "With Out Any Type Errors" ?. Install Live onto the SSD.. Do not boot but reBoot the Flash drive with your MX - Live at the DT open thunar see if you left side you see the SSD can you click it and mount it. file manage into media demo UUID/ new file system. Can you click around folders click home click your new account name folder open feather pad and write a test file save it here write it out and close it come back to it and reopen can you read what you typed.
Think to believe connecting the SSD to another computer reveals its all right and why does it not work. Think to believe due to the age and type the PS might be causing a red herring issue. Something to step thru in a different approach. Try similar opening a terminal shell and cd /media/*/* pwd and see if your on the new installed file system all the same. And sudo write a test file using nano/vim and try the same write read tests. These might work . still think your operating on a almost dead PS. Worth the duration now that you've climbed the tree up and down to get MX installed .. Another small tiny Linux OS might work. But love of MX is the fathom of Linux.
and no mask required. See if you can try the Hardinfo2 off the Live and see if you can cd to media and select this SSD and run thru the details and try some tests. Think they may fail. ! Revealing a possible PS is your all trouble. Food for thought.

Posted: **Sun Jan 26, 2025 3:29 pm**

Hey @atomick -- thanks for your comments! I think we're good here. I just booted up into the external SSD where I have MX 23.5 Fluxbox edition installed (both my MX's on the internal SSD are Xfce). Yes, everything in the laptop is old, including the battery. Samsung has a software switch that keeps you from over-charging it to extend battery life. (I thought it used to be at 85%, but right now it's 80%). AFAIK, voltage is fine for the design (some folks deliberately under-volt), OR, dunno if tlp and thermald do anything to the voltage to keep the power consumption low, but in any case, I think it's alright. For the record, the current QSI is posted down below.

@fehlix, going back to my comment about booting F-box up back on the Samsung after the li'l bitty 13" HP, it did fine. I did not have to fiddle with bios to see the external drive. It (MX 23.5 with F-box) did show up as the top grub menu choice, and I *think* all three other installed distros on the internal drive also showed up, though the last one installed (MX 23.5 Xfce) was not at the top, my old MX 21.4 was. Not sure which grub was in control, but probably the external drive?

The psensor window, not visible at all on the HP's single monitor, came up in the top monitor where it had been (it was set to remember where it was, so that is expected). A strange by-product of the series of different architecture boots is that back here, the wallpaper that was set and should have been restored by nitrogen, was not, just the huge, stretched silver MX Linux logo. Dunno what to make of that.

Maybe the last (bwahaha) question on this external SSD installation and boot business is -- what happens if I install yet another distro on this bad boy? Do I need to follow any special instructions afterward? (Boot back into MX and re-install legacy grub maybe?)

Code: Select all

System:
  Kernel: 6.1.0-30-amd64 [6.1.124-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-30-amd64 root=UUID=<filter> ro quiet splash
  Desktop: Fluxbox v: 1.3.7 info: tint2 vt: 7 dm: LightDM v: 1.32.0 Distro: MX-23.5_fluxbox_x64
    Libretto September 15 2024 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Laptop System: SAMSUNG product: RF511/RF411/RF711 v: 10HX serial: <superuser required>
    Chassis: type: 9 serial: <superuser required>
  Mobo: SAMSUNG model: RF511/RF411/RF711 v: 10HX serial: <superuser required>
    UEFI: American Megatrends v: 10HX.M034.20110426.SSH date: 04/26/2011
Battery:
  ID-1: BAT1 charge: 35.5 Wh (80.0%) condition: 44.4/48.8 Wh (90.9%) volts: 10.7 min: 11.1
    model: SAMSUNG Electronics type: Li-ion serial: N/A status: not charging
  Device-1: hidpp_battery_0 model: Logitech ERGO M575 Trackball serial: <filter> charge: 100%
    rechargeable: yes status: discharging
CPU:
  Info: model: Intel Core i7-2630QM bits: 64 type: MT MCP arch: Sandy Bridge gen: core 2 level: v2
    built: 2010-12 process: Intel 32nm family: 6 model-id: 0x2A (42) stepping: 7 microcode: 0x2F
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache: L1: 256 KiB
    desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB desc: 1x6 MiB
  Speed (MHz): avg: 812 high: 900 min/max: 800/2900 scaling: driver: intel_cpufreq
    governor: ondemand cores: 1: 800 2: 800 3: 800 4: 900 5: 800 6: 800 7: 800 8: 800 bogomips: 31929
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW; STIBP: conditional; RSB
    filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: Samsung Co
    driver: i915 v: kernel arch: Gen-6 code: Sandybridge process: Intel 32nm built: 2011 ports:
    active: LVDS-1,VGA-1 empty: DP-1,HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:0116 class-ID: 0300
  Device-2: NVIDIA GF108M [GeForce GT 540M] vendor: Samsung Co driver: N/A alternate: nouveau
    non-free: series: 390.xx+ status: legacy-active (EOL~late 2022) arch: Fermi code: GF1xx
    process: 40/28nm built: 2010-16 pcie: speed: Unknown lanes: 63 link-max: gen: 6 speed: 64 GT/s
    bus-ID: 01:00.0 chip-ID: 10de:0df4 class-ID: 0302
  Device-3: Silicon Motion WebCam SCB-1100N type: USB driver: uvcvideo bus-ID: 1-1.1:3
    chip-ID: 2232:1008 class-ID: 0e02
  Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: modesetting unloaded: fbdev,vesa
    dri: crocus gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1600x2820 s-dpi: 96 s-size: 422x744mm (16.61x29.29") s-diag: 855mm (33.68")
  Monitor-1: LVDS-1 pos: primary,bottom model: ChiMei InnoLux 0x1733 built: 2012 res: 1600x900
    hz: 60 dpi: 106 gamma: 1.2 size: 382x215mm (15.04x8.46") diag: 448mm (17.6") ratio: 16:9
    modes: 1600x900
  Monitor-2: VGA-1 pos: top model: Dell P2214H serial: <filter> built: 2015 res: 1080x1920 hz: 60
    dpi: 102 gamma: 1.2 size: 268x477mm (10.55x18.78") diag: 547mm (21.5") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  API: OpenGL v: 3.3 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 3000 (SNB GT2)
    direct-render: Yes
Audio:
  Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: Samsung Co 6
    driver: snd_hda_intel bus-ID: 2-1:2 v: kernel chip-ID: 1130:1620 bus-ID: 00:1b.0 class-ID: 0300
    chip-ID: 8086:1c20 class-ID: 0403
  Device-2: NVIDIA GF108 High Definition Audio driver: snd_hda_intel v: kernel pcie:
    speed: Unknown lanes: 63 link-max: gen: 6 speed: 64 GT/s bus-ID: 01:00.1 chip-ID: 10de:0bea
    class-ID: 0403
  Device-3: Tenx USB AUDIO type: USB driver: hid-generic,snd-usb-audio,usbhid
  Device-4: AKAI MPKmini2 type: USB driver: hid-generic,snd-usb-audio,usbhid bus-ID: 2-2.2:4
    chip-ID: 2011:0715 class-ID: 0103 serial: <filter>
  API: ALSA v: k6.1.0-30-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 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: Broadcom BCM4313 802.11bgn Wireless Network Adapter vendor: Askey driver: wl v: kernel
    modules: bcma pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 02:00.0 chip-ID: 14e4:4727
    class-ID: 0280
  IF: wlan0 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Samsung Co
    driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: b000 bus-ID: 03:00.0
    chip-ID: 10ec:8168 class-ID: 0200
  IF: eth0 state: down mac: <filter>
Bluetooth:
  Device-1: Broadcom BCM2070 Bluetooth Device type: USB driver: btusb v: 0.8 bus-ID: 3-1.3:3
    chip-ID: 0a5c:219c class-ID: fe01 serial: <filter>
  Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 2.0 lmp-v: 3.0
    sub-v: 4203 hci-v: 3.0 rev: 274
  Info: acl-mtu: 1021:8 sco-mtu: 64:1 link-policy: rswitch hold sniff park
    link-mode: peripheral accept service-classes: rendering, capturing, audio, telephony
Drives:
  Local Storage: total: 2.96 TiB used: 212.36 GiB (7.0%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 2B6Q scheme: MBR
  ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: Seagate model: BUP Slim BK size: 1.82 TiB
    block-size: physical: 4096 B logical: 512 B type: N/A serial: <filter> rev: 0109 scheme: GPT
  ID-3: /dev/sdc maj-min: 8:32 type: USB vendor: Sabrent model: SABRENT size: 238.47 GiB
    block-size: physical: 4096 B logical: 512 B type: N/A serial: <filter> rev: 0204 scheme: GPT
Partition:
  ID-1: / raw-size: 100 GiB size: 97.87 GiB (97.87%) used: 10.12 GiB (10.3%) fs: ext4
    dev: /dev/sdc3 maj-min: 8:35
  ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%) used: 428 KiB (0.1%) fs: vfat
    dev: /dev/sdc2 maj-min: 8:34
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 12 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sdc4
    maj-min: 8:36
Sensors:
  System Temperatures: cpu: 51.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: 1983 pm: dpkg pkgs: 1971 libs: 950 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 12
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
    1: deb [arch=amd64 signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg] https://brave-browser-apt-release.s3.brave.com/ stable main
  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://mirror.math.princeton.edu/pub/mxlinux/mx/repo/ bookworm main non-free
Info:
  Processes: 244 Uptime: 4m wakeups: 4 Memory: 7.67 GiB used: 969.9 MiB (12.4%) 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

Posted: **Sun Jan 26, 2025 5:44 pm**

Okay, another interesting twist to all this -- somehow (thanks, Fluxbox!) I right-clicked and accidentally clicked the stupid "Leave" or "Out of Sight" menu item at the bottom, and got logged out (?) or it might have caused a restart. In any case, the next grub menu was from my internal SSD. Not a real problem, just a curious by-product. I automatically get the external SSD grub menu when I boot up from a shutdown. Just things to get used to!?

Posted: **Wed Jan 29, 2025 1:43 am**

Durhammer wrote: Sat Jan 25, 2025 9:03 pm Me, too! Maybe, though, you and @FullScale4Me should figure out that one point in his (your combined) instructions where you do the chmod to stop the portable SSD grub from seeing any other OSes (though it's not really too much of a detriment, but the instructions might not really do anything as-is?). You guys will have a great document for other folks to use. I sure benefited from the collab!

I added a pic for the do not reboot checkbox.

I addressed the above point and the one you mentioned earlier in this thread in post #19.

I built the disk two more times; once with KDE and then Fluxbox.

I tested all 3 disks again on a UEFI and an MBR-only PC and confirmed the boot mode each time.

Adjusted some text to improve the match to 'exact' for the apps in use.

Making a bootable external USB drive with MX Linux installed PDF 154 Kb. Revised 29-January-2025.

Disks in use:
Dogfish 64 GB SSD, Seagate 250 GB 7200 RPM 'spinning rust' and Timetec M.2 SATA 250 GB.
All in ORICO USB 3.0 enclosures. M.2 enclosure.
PC's used for testing
Dell Inspiron 7010 MBR and HP Pavilion P2-1394 UEFI.

Posted: **Wed Jan 29, 2025 6:08 pm**

Looks good to me, @FullScale4Me, though I still wonder about that step 2.1 where we nix the executable permissions on the OS prober in grub. I had thought I'd done that, but still see the bootables on my internal SSD when I boot up the external drive's OS. I actually kinda like it. And really, I'd like it if my internal drive's grub would see and allow boot to the external drive, but I guess that doesn't happen bcz it's UEFI????

And I repeat the "last question" I penned in a post above this one -- what will happen if I (or anyone else following the instructions) install a different distro on the external SSD? Does one need to re-do both MBR and UEFI grubs afterward?

Thanks for the excellent procedure and write-up, both you and @fehlix!

Posted: **Wed Jan 29, 2025 10:27 pm**

Durhammer wrote: Wed Jan 29, 2025 6:08 pm Looks good to me, @FullScale4Me, though I still wonder about that step 2.1 where we nix the executable permissions on the OS prober in grub. I had thought I'd done that, but still see the bootables on my internal SSD when I boot up the external drive's OS.

Running sudo update-grub while booted on the eternal drive will drop those extra entries, With os-prober disabled they will NOT be re-added.

Durhammer wrote: Wed Jan 29, 2025 6:08 pm And I repeat the "last question" I penned in a post above this one -- what will happen if I (or anyone else following the instructions) install a different distro on the external SSD? Does one need to re-do both MBR and UEFI grubs afterward?

You could go the easy way, Ventoy, or add a custom entry to the existing grub menu.
See - What is the recommended way to chainload separate Ubuntu /boot partition

After doing so rerun sudo update-grub while booted on the external drive to add the new partition to grub.cfg,

Edit: spelling error fix.

Posted: **Wed Jan 29, 2025 11:28 pm**

FullScale4Me wrote: Wed Jan 29, 2025 10:27 pm [You could go the easy way, Ventoy, or add a custom entry to the existing grub menu.
See - What is the recommended way to chainload separate Ubuntu /boot partition

After doing so rerun sudo update-grub while booted on the eternal drive to add the new partition to grub.cfg,

I looked at the article you linked to, and I just say "eek -- that's Greek"!!! Sorry, still new to this boot stuff. I'll keep grubbing around. Maybe I'll grok it some day!

MX Linux Forum

How to install and run MX 23 on external SSD

How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD

Re: How to install and run MX 23 on external SSD