MX-19 RC1 Feedback thread

[Eadwine Rose]

19.1? *giggle* MX19 isn't even final yet

[BitJam]

I did everything the same as my 18.3 persistent live USB but it won't boot.
When I reboot the computer I get a quick flash of "Missing operating system" then the Grub on the HD boots the OS installed on the HD.
Gparted shows the same MX-Live-USB, MX-UEFI and encrypted partitions as a good 18.3 USB.
I don't know how to tell what is going on.

This is a bug in the latest live-usb-maker. Assume your live-usb is /dev/sdd and I'm assuming you're using the default msdos partitioning. You can verify the problem by running:

Code: Select all

sudo parted /dev/sdd print
[...]
Number  Start   End     Size    Type     File system  Flags
 1      1049kB  157MB   156MB   primary  ext4
 2      157MB   32.0GB  31.9GB  primary               boot
 3      32.0GB  32.1GB  51.4MB  primary  fat32        esp

The first partition should be the boot partition but the 2nd is has the "boot" flag. You should be able to fix this in gparted or with this parted command:

Code: Select all

sudo parted /dev/sdd set 2 boot off set 1 boot on print
[...]
Number  Start   End     Size    Type     File system  Flags
 1      1049kB  157MB   156MB   primary  ext4         boot
 2      157MB   32.0GB  31.9GB  primary
 3      32.0GB  32.1GB  51.4MB  primary  fat32        esp

I replicated the problem you reported and I verified that the command above fixed it and got the live-usb to boot. I will next fix the LUM program. I believe this got broken when we added the data-first option. I think I tested data-first and data-first plus encryption but not encryption by itself.

I'm sorry for the inconvenience!

[JayM]

19.1? *giggle* MX19 isn't even final yet

I know. My advice to people, especially those who don't know Linux or MX that well and just want to use it, is to be patient and wait a while, maybe a few months, before upgrading to 19 and let a few more bugs get worked out if there are any..; At very least wait until MX-19 Official Release has been out for a month or so before having newbies tackle upgrading to it. This is a major release, MX-18 will still be supported for a couple-three years, so there's no hurry.

[richb]

19.1? *giggle* MX19 isn't even final yet

I know. My advice to people, especially those who don't know Linux or MX that well and just want to use it, is to be patient and wait a while, maybe a few months, before upgrading to 19 and let a few more bugs get worked out if there are any..; At very least wait until MX-19 Official Release has been out for a month or so before having newbies tackle upgrading to it. This is a major release, MX-18 will still be supported for a couple-three years, so there's no hurry.

Or if you have the luxury of a large drive install MX 19 Final on another partiton(s) or on another drive. Keep 18.3 and "play" with 19. When you are comfortable with it and any bugs are quashed, I do not expect many, it can become your daily driver. That is what I have done. Although I have been running 19 since the first beta daily, I am keeping a copy of 18.3 on another drive for a while.
I intend to not fresh install final keeping RC1 up to date, depending on the final guidance from the Developers and it will be, actually currently is my daily driver.

[BV206]

I think this is a MX 19 problem but I don't know how to troubleshoot this.
I downloaded the RC1 iso, made a usb stick, it booted with no problems.
I updated/upgraded it then I tried to make a persistent live USB.
Live USB Creator made the new USB with no errors.
I did everything the same as my 18.3 persistent live USB but it won't boot.
When I reboot the computer I get a quick flash of "Missing operating system" then the Grub on the HD boots the OS installed on the HD.
Gparted shows the same MX-Live-USB, MX-UEFI and encryted partitions as a good 18.3 USB.
I don't know how to tell what is going on.

Please run MX Tools/Quick System Info after booting your live USB, then right-click paste into a reply. (Quick System Info automatically copies the information to the clipboard and formats it properly for the forum so all you have to do is paste it.) Thanks.

OK but I think I can fix it now. I didn't know about the boot flag issue.

Code: Select all

System:    Host: mx1 Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: quiet splasht 
           Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-19RC1_x64 patito feo October 15  2019 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Laptop System: Hewlett-Packard product: HP Pavilion g7 Notebook PC 
           v: 0690130000204610000620100 serial: <filter> Chassis: type: 10 serial: <filter> 
           Mobo: Hewlett-Packard model: 3568 v: 21.46 serial: <filter> BIOS: Insyde v: F.6A 
           date: 05/13/2013 
CPU:       Topology: Dual Core model: AMD A4-3305M APU with Radeon HD Graphics bits: 64 
           type: MCP arch: Fusion family: 12 (18) model-id: 1 stepping: N/A microcode: 3000027 
           L2 cache: 1024 KiB 
           flags: lm nx pae sse sse2 sse3 sse4a svm bogomips: 7586 
           Speed: 801 MHz min/max: 800/1900 MHz boost: enabled Core speeds (MHz): 1: 800 2: 800 
           Vulnerabilities: Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown 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: Full AMD retpoline, STIBP: disabled, RSB filling 
Graphics:  Device-1: AMD Sumo [Radeon HD 6480G] vendor: Hewlett-Packard driver: radeon v: kernel 
           bus ID: 00:01.0 chip ID: 1002:9649 
           Display: x11 server: X.Org 1.20.4 driver: ati,radeon unloaded: fbdev,modesetting,vesa 
           resolution: 1600x900~60Hz 
           OpenGL: renderer: AMD SUMO2 (DRM 2.50.0 / 4.19.0-6-amd64 LLVM 7.0.1) 
           v: 3.3 Mesa 18.3.6 compat-v: 3.1 direct render: Yes 
Audio:     Device-1: AMD BeaverCreek HDMI Audio [Radeon HD 6500D and 6400G-6600G series] 
           vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:01.1 
           chip ID: 1002:1714 
           Device-2: AMD FCH Azalia vendor: Hewlett-Packard driver: snd_hda_intel v: kernel 
           bus ID: 00:14.2 chip ID: 1022:780d 
           Sound Server: ALSA v: k4.19.0-6-amd64 
Network:   Device-1: Realtek RTL8188CE 802.11b/g/n WiFi Adapter vendor: Hewlett-Packard 
           driver: rtl8192ce v: kernel port: 3000 bus ID: 01:00.0 chip ID: 10ec:8176 
           IF: wlan0 state: down mac: <filter> 
           Device-2: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet 
           vendor: Hewlett-Packard RTL810xE driver: r8169 v: kernel port: 2000 bus ID: 02:00.0 
           chip ID: 10ec:8136 
           IF: eth0 state: down mac: <filter> 
Drives:    Local Storage: total: 310.69 GiB used: 5.90 GiB (1.9%) 
           ID-1: /dev/sda vendor: PNY model: CS900 240GB SSD size: 223.57 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 0208 scheme: MBR 
           ID-2: /dev/sdb type: USB vendor: Lexar model: USB Flash Drive size: 29.81 GiB 
           block size: physical: 512 B logical: 512 B serial: <filter> rev: 8.07 scheme: MBR 
           ID-3: /dev/sdc type: USB vendor: SanDisk model: Ultra Fit size: 57.30 GiB block size: 
           physical: 512 B logical: 512 B serial: <filter> rev: 1.00 scheme: MBR 
Partition: ID-1: / raw size: N/A size: 2.63 GiB used: 23.7 MiB (0.9%) fs: overlay 
           source: ERR-102 
Sensors:   System Temperatures: cpu: 42.9 C mobo: N/A gpu: radeon temp: 49 C 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/antix.list 
           1: deb http://iso.mxrepo.com/antix/buster buster main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian buster main contrib non-free
           2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ buster main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 186 Uptime: 3m Memory: 3.34 GiB used: 559.7 MiB (16.4%) Init: SysVinit 
           v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 
           running in: quick-system-in inxi: 3.0.36 

[winemaker]

JayM and RichB - that sounds like good sound advice. esp someone like me who needs a serious working system daily and also am too dumb to work out any glitches if there are a few gremlins left. i was seriously thinking of maybe installing rc1 today if i get the time but i may ponder that thought a bit more.

[chrispop99]

JayM and RichB - that sounds like good sound advice. esp someone like me who needs a serious working system daily and also am too dumb to work out any glitches if there are a few gremlins left. i was seriously thinking of maybe installing rc1 today if i get the time but i may ponder that thought a bit more.

Alternatively if you have a USB pen drive, set it up live with persistence and see if MX-19 works well for you. All your files within your MX-18 install will be accessible to you should you want them.

Chris

[richb]

JayM and RichB - that sounds like good sound advice. esp someone like me who needs a serious working system daily and also am too dumb to work out any glitches if there are a few gremlins left. i was seriously thinking of maybe installing rc1 today if i get the time but i may ponder that thought a bit more.

Alternatively if you have a USB pen drive, set it up live with persistence and see if MX-19 works well for you. All your files within your MX-18 install will be accessible to you should you want them.

Chris

+1

[Jerry3904]

Even more alternatively, run 19 in a VM on 18 for a while--or vice versa (what I will do on my production machine)

[BV206]

OK but I think I can fix it now. I didn't know about the boot flag issue.

This morning I noticed LUM was one of the packages that upgraded before I tried to make another USB.
I set the boot flags as what is shown a few posts back.
Now at least it can find the correct boot partition on the USB but then I get:
Fatal error
Encrypted device /dev/sdb2 is not a LUKS device.
I had encrypt checked in LUM so it looks like it made an encrypted partition but it can't use it for some reason.

If I don't check encrypt in LUM then it makes the USB with the correct boot flags and it boots normally.