MX-19 Beta 3 Feedback

Message
Author
User avatar
Eadwine Rose
Administrator
Posts: 14471
Joined: Wed Jul 12, 2006 2:10 am

Re: MX-19 Beta 3 Feedback

#261 Post by Eadwine Rose »

I had to do what DO in that video does as well. Put everything on UEFI, and CSM has to be disabled. When I disabled that CSM one loads of things flipped to UEFI only. Which is what I wanted :)


You will know that you booted in UEFI mode on the liveusb when you check if you have /sys/firmware/efi
That directory will only exist if you are booted in UEFI mode, if that is not there you have not done it right.

You will also see it state UEFI when you start the boot screen (the bios).
MX-23.6_x64 July 31 2023 * 6.1.0-34amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.216.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030

SwampRabbit
Posts: 3602
Joined: Tue Jun 14, 2016 2:02 pm

Re: MX-19 Beta 3 Feedback

#262 Post by SwampRabbit »

It was this system I posted about before, it’s got the same motherboard, RAM, and similar CPU to BitJam’s PC so it might not be a good reference for other people’s problems.

Code: Select all

 System:    Host: mx19b3 Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-amd64 
           root=UUID=9643d157-63d7-40cb-8691-9c4c177dce58 ro quiet amd_iommu=on iommu=pt splash 
           Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-19beta-3_x64 patito feo September 22  2019 
           base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Desktop System: Gigabyte product: N/A v: N/A serial: <filter> Chassis: type: 3 
           serial: <filter> 
           Mobo: Gigabyte model: 990FXA-UD3 R5 v: x.x serial: <filter> UEFI: American Megatrends 
           v: F2 date: 04/01/2015 
CPU:       Topology: 8-Core model: AMD FX-8300 bits: 64 type: MCP arch: Bulldozer 
           family: 15 (21) model-id: 2 stepping: N/A microcode: 6000852 L2 cache: 2048 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 53042 
           Speed: 1401 MHz min/max: 1400/3300 MHz boost: enabled Core speeds (MHz): 1: 1401 
           2: 1404 3: 1405 4: 1406 5: 1405 6: 1400 7: 1403 8: 1401 
           Vulnerabilities: Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 
           mitigation: Full AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling 
Graphics:  Device-1: AMD Ellesmere [Radeon RX 470/480] vendor: Micro-Star MSI driver: amdgpu 
           v: kernel bus ID: 01:00.0 chip ID: 1002:67df 
           Display: x11 server: X.Org 1.20.4 driver: amdgpu,ati 
           unloaded: fbdev,modesetting,radeon,vesa resolution: 1920x1080~60Hz 
           OpenGL: 
           renderer: Radeon RX 570 Series (POLARIS10 DRM 3.27.0 4.19.0-6-amd64 LLVM 7.0.1) 
           v: 4.5 Mesa 18.3.6 direct render: Yes 
Audio:     Device-1: AMD SBx00 Azalia vendor: Gigabyte driver: snd_hda_intel v: kernel 
           bus ID: 00:14.2 chip ID: 1002:4383 
           Device-2: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] 
           vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus ID: 01:00.1 
           chip ID: 1002:aaf0 
           Sound Server: ALSA v: k4.19.0-6-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte 
           driver: r8169 v: kernel port: d000 bus ID: 04:00.0 chip ID: 10ec:8168 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 268.29 GiB used: 5.19 GiB (1.9%) 
           ID-1: /dev/sda vendor: Silicon Power model: SPCC Solid State Disk size: 238.47 GiB 
           block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 4A0 
           scheme: GPT 
           ID-2: /dev/sdb type: USB vendor: SanDisk model: Cruzer Glide 3.0 size: 29.81 GiB 
           block size: physical: 512 B logical: 512 B serial: <filter> rev: 1.00 scheme: MBR 
Partition: ID-1: / raw size: 236.19 GiB size: 231.49 GiB (98.01%) used: 5.19 GiB (2.2%) fs: ext4 
           dev: /dev/sda2 
           ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda3 
Sensors:   System Temperatures: cpu: 24.8 C mobo: N/A gpu: amdgpu temp: 27 C 
           Fan Speeds (RPM): N/A gpu: amdgpu fan: 1128 
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: 237 Uptime: N/A Memory: 15.63 GiB used: 540.1 MiB (3.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 
Pretty sure it has CSM enabled but will check later.
NEW USERS START HERE FAQS, MX Manual, and How to Break Your System - Don't use Ubuntu PPAs! Always post your Quick System Info (QSI) when asking for help.

User avatar
Eadwine Rose
Administrator
Posts: 14471
Joined: Wed Jul 12, 2006 2:10 am

Re: MX-19 Beta 3 Feedback

#263 Post by Eadwine Rose »

My own conky is not transparent in MX19. Same file content below on 18.3, but on mx19 it shows a solid black background. Same in the 2.1 beta.

Any ideas?
edit: solved, see bottom of this post.

Conky code:

Code: Select all

conky.config = {
    alignment = 'bottom_left',
    background = false,
    border_width = 1,
    cpu_avg_samples = 2,
    default_color = 'DDDDDD',
    default_outline_color = 'white',
    default_shade_color = 'black',
    draw_borders = false,
    draw_graph_borders = true,
    draw_outline = false,
    draw_shades = false,
    use_xft = true,
    xftalpha = 0.8,
    font = 'Monospace:size=8',
    gap_x = -1850,
    gap_y = 45,
    minimum_height = 5,
    minimum_width = 5,
    maximum_width = 250,
    net_avg_samples = 2,
    no_buffers = true,
    double_buffer = true,
    out_to_console = false,
    out_to_stderr = false,
    extra_newline = false,
    imlib_cache_size =0,
    override_utf8_locale = true,
    own_window = true,
    own_window_class = 'conky-semi',
    own_window_type = 'override',
    own_window_transparent = true,
    own_window_hints = 'undecorated,below,sticky,skip_taskbar,skip_pager',
    stippled_borders = 0,
    update_interval = 1.0,
    uppercase = false,
    use_spacer = 'none',
    total_run_times = 0,
    show_graph_scale = false,
    show_graph_range = false
}
 
conky.text = [[
${color Tan1}System uptime${goto 105}${color}${uptime}    
${color Tan1}IP number${goto 105}${color}${execi 3600 wget -q -O - http://icanhazip.com}
${color Tan1}Motherboard${goto 105}${color}Asus Tuf B450-Plus Gaming
${color Tan1}MB temp${goto 105}${color}${exec sensors | grep 'temp2' | cut -c16-17}C
${color Tan1}Case fan${goto 105}${color}${exec sensors | grep 'fan2'| cut -b 15-21}
${color Tan1}CPU${goto 105}${color}AMD Ryzen 7 2700     
${color Tan1}CPU usage${goto 105}${color}${cpu cpu0}%
${color Tan1}CPU temperature${goto 105}${color}${exec sensors | grep 'Tdie' | cut -c16-19}C / 95C
${color Tan1}CPU frequency${goto 105}$color${freq} Mhz         
${color Tan1}CPU fan speed${goto 105}${color}${exec sensors | grep 'fan1'| cut -b 15-21} 
#${color Tan1}Chassis fan 4 speed ${color}${exec sensors | grep 'fan4'| cut -b 15-21}
#ram usage with no-buffer = false conky will show actual amount of RAM + Cached memory, set to true will show actual memory being used
${color Tan1}Ram in use${goto 105}${color}${mem} / $memmax
# calculate down and up speed scale (150*1000000)/8/1024 where 150 is the amount of mbits the eth0 connection has
# calculate down and up speed scale (25*1000000)/8/1024 where 25 is the amount of mbits the wlan0 connection has
${color Tan1}Eth0 down${goto 105}${color}${downspeedgraph eth0 10,70 00ff00 00ff00 21362KiB} ${downspeed eth0}
${color Tan1}Eth0 up${goto 105}${color}${upspeedgraph eth0 10,70 ff0000 ff0000 19531KiB} ${color}${upspeed eth0}
${color Tan1}Wlan0 down${goto 105}${color}${downspeedgraph wlan0 10,70 00ff00 00ff00 10254KiB} ${downspeed wlan0}
${color Tan1}Wlan0 up${goto 105}${color}${upspeedgraph wlan0 10,70 ff0000 ff0000 5371KiB} ${color}${upspeed wlan0}
#${color Tan1}PCI adapter temp   ${color}${exec sensors | grep 'temp1' | cut -c16-17}C 
${color Tan1}/dev/sda${goto 105}${color}${hddtemp /dev/sda}C
${color Tan1}/dev/sdb${goto 105}${color}${hddtemp /dev/sdb}C
${color Tan1}/dev/sdc${goto 105}${color}${hddtemp /dev/sdc}C
${color Tan1}/dev/sdd${goto 105}${color}${hddtemp /dev/sdd}C
${color Tan1}/dev/sde${goto 105}${color}${hddtemp /dev/sde}C
${color Tan1}GeForce fan${goto 105}${color}${exec nvidia-smi -a | grep -i fan | cut -c39-40}%
${color Tan1}GeForce 1050Ti${goto 105}${color}${nvidia temp}C / 97C
${color Tan1}GeForce ram${goto 105}${color}${exec nvidia-smi --query-gpu=memory.used --format=csv,noheader} / ${exec nvidia-smi --query-gpu=memory.total --format=csv,noheader}

${color Tan1}TOP${alignr}          PID    CPU    MEM 
${color}${top name 1}${alignr}${color}${top pid 1} ${top cpu 1} ${top mem 1}
${color}${top name 2}${alignr}${color}${top pid 2} ${top cpu 2} ${top mem 2}
${color}${top name 3}${alignr}${color}${top pid 3} ${top cpu 3} ${top mem 3}
${color}${top name 4}${alignr}${color}${top pid 4} ${top cpu 4} ${top mem 4}
${color}${top name 5}${alignr}${color}${top pid 5} ${top cpu 5} ${top mem 5}

${font Verdana:size=8}${color Tan1}OB ${color}${rss http://www.omroepbrabant.nl/rss/?feed=west 15 item_titles 2}
${color Tan1}BN ${color}${rss http://www.bndestem.nl/roosendaal/rss.xml 15 item_titles 2}
#${color Tan1}Nieuws.nl ${color}${rss http://nieuws.nl/feed/ 15 item_titles 2}
${color Tan1}BD ${color}${rss http://www.bd.nl/brabant/rss.xml 15 item_titles 2}
#${color Tan1}Nu.nl ${color}${rss http://www.nu.nl/rss/algemeen 15 item_titles 2}
#${color Tan1}GeenStijl ${color}${rss https://www.geenstijl.nl/feeds/recent.atom 15 item_titles 2}
#${color Tan1}CNN ${color}${rss http://rss.cnn.com/rss/cnn_latest.rss 15 item_titles 2}

${color}${exec tail -n4 /var/log/syslog | fold -w41}
]]

Code: Select all

System:    Host: eadwineMX19beta3 Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-amd64 
           root=UUID=ae052a7a-c62e-4f4c-8c21-c2f812806ebc ro quiet 
           Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-19beta-3_x64 patito feo September 22  2019 
           base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Desktop Mobo: ASUSTeK model: TUF B450-PLUS GAMING v: Rev X.0x serial: <filter> 
           UEFI: American Megatrends v: 1607 date: 06/17/2019 
Battery:   Device-1: hidpp_battery_0 model: Logitech MX Ergo Multi-Device Trackball 
           serial: <filter> charge: 100% (should be ignored) rechargeable: yes 
           status: Discharging 
CPU:       Topology: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+ 
           family: 17 (23) model-id: 8 stepping: 2 microcode: 800820C L2 cache: 4096 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
           bogomips: 102192 
           Speed: 1379 MHz min/max: 1550/3200 MHz boost: enabled Core speeds (MHz): 1: 1376 
           2: 1378 3: 1541 4: 1546 5: 1389 6: 1406 7: 1547 8: 1546 9: 1373 10: 1547 11: 1379 
           12: 1404 13: 1546 14: 1547 15: 1544 16: 1475 
           Vulnerabilities: Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 
           mitigation: Full AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling 
Graphics:  Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: ASUSTeK driver: nvidia v: 418.74 
           bus ID: 08:00.0 chip ID: 10de:1c82 
           Display: x11 server: X.Org 1.20.4 driver: nvidia 
           unloaded: fbdev,modesetting,nouveau,vesa alternate: nv 
           resolution: 1920x1080~60Hz, 1920x1080~60Hz 
           OpenGL: renderer: GeForce GTX 1050 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 418.74 
           direct render: Yes 
Audio:     Device-1: Conexant Systems CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D 
           Comb 
           vendor: Hauppauge works driver: cx23885 v: 0.0.4 bus ID: 07:00.0 chip ID: 14f1:8880 
           Device-2: NVIDIA GP107GL High Definition Audio vendor: ASUSTeK driver: snd_hda_intel 
           v: kernel bus ID: 08:00.1 chip ID: 10de:0fb9 
           Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus ID: 0a:00.3 chip ID: 1022:1457 
           Device-4: Logitech QuickCam E 3500 type: USB driver: snd-usb-audio,uvcvideo 
           bus ID: 3-1:2 chip ID: 046d:09a4 serial: <filter> 
           Sound Server: ALSA v: k4.19.0-6-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK 
           driver: r8169 v: kernel port: f000 bus ID: 03:00.0 chip ID: 10ec:8168 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Ralink MT7601U Wireless Adapter type: USB driver: mt7601u bus ID: 1-1:2 
           chip ID: 148f:7601 serial: <filter> 
           IF: wlan0 state: down mac: <filter> 
Drives:    Local Storage: total: 1.82 TiB used: 87.62 GiB (4.7%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 2B6Q scheme: GPT 
           ID-2: /dev/sdb vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 2B6Q scheme: GPT 
           ID-3: /dev/sdc vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 3B6Q scheme: GPT 
           ID-4: /dev/sdd type: USB vendor: Seagate model: BUP Slim RD size: 931.51 GiB 
           block size: physical: 4096 B logical: 512 B serial: <filter> rev: 0109 scheme: MBR 
           ID-5: /dev/sde vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 3B6Q scheme: GPT 
Partition: ID-1: / raw size: 58.59 GiB size: 57.42 GiB (98.00%) used: 5.88 GiB (10.2%) fs: ext4 
           dev: /dev/sdc1 
           ID-2: /home raw size: 166.48 GiB size: 162.87 GiB (97.83%) used: 254.1 MiB (0.2%) 
           fs: ext4 dev: /dev/sdc3 
           ID-3: swap-1 size: 7.81 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sdc2 
Sensors:   System Temperatures: cpu: 35.2 C mobo: 27.0 C gpu: nvidia temp: 33 C 
           Fan Speeds (RPM): cpu: 551 fan-2: 755 fan-3: 0 fan-4: 736 fan-6: 0 gpu: nvidia 
           fan: 25% 
           Voltages: 12v: N/A 5v: N/A 3.3v: 3.36 vbat: 3.27 
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: 313 Uptime: 19m Memory: 31.41 GiB used: 1.40 GiB (4.5%) 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 



Hah, got it.


Add line

Code: Select all

own_window_argb_visual = true,

in the top bit, and fixed :happy:



*mutter* always happens right after you post :laugh:
MX-23.6_x64 July 31 2023 * 6.1.0-34amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.216.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030

User avatar
Jerry3904
Administrator
Posts: 23089
Joined: Wed Jul 19, 2006 6:13 am

Re: MX-19 Beta 3 Feedback

#264 Post by Jerry3904 »

Try these changes:

Code: Select all

    own_window_class = 'conky',
    own_window_type = 'conky',
That's what the others are using.
Production: 5.10, MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin

User avatar
Eadwine Rose
Administrator
Posts: 14471
Joined: Wed Jul 12, 2006 2:10 am

Re: MX-19 Beta 3 Feedback

#265 Post by Eadwine Rose »

See the bottom of my post, it has been solved pretty much right after I posted *groan* lol
MX-23.6_x64 July 31 2023 * 6.1.0-34amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.216.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030

User avatar
Jerry3904
Administrator
Posts: 23089
Joined: Wed Jul 19, 2006 6:13 am

Re: MX-19 Beta 3 Feedback

#266 Post by Jerry3904 »

That was my next suggestion...
Production: 5.10, MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin

User avatar
dreamer
Posts: 889
Joined: Sun Oct 15, 2017 11:34 am

Re: MX-19 Beta 3 Feedback

#267 Post by dreamer »

Jerry3904 wrote: Mon Oct 07, 2019 6:03 pm Maybe there is some dependence on resolution. On my test machine, I am unable to make the notifications cover the panel when it is at the top or bottom, no matter how big I make the panel(went up to 70).
It's good now. I think an update solved it. :happy:
Adrian wrote: Mon Oct 07, 2019 7:29 pm Yeah, it's normal to still show when it shuts down but at reboot it shouldn't be there anymore, if you see this again, can you please let me know if you still see the "splash" in the boot options line? That shows both in mx-boot-options "kernel parameters line" and more importantly it's in the "linux" line in /boot/grub/grub.conf you could check that with a one liner:

Code: Select all

grep splash /boot/grub/grub.cfg
If you see some output there it means the key word is present.
Thanks. I haven't installed Beta 3, but I have copied your info so I have it when I need it.
Note to self and others: SysVinit is a good option. However if you run into problems try with systemd first. This applies to AppImages, Flatpaks, GitHub packages and even some Debian packages.

User avatar
bpr323
Posts: 172
Joined: Thu Jun 20, 2019 10:17 am

Re: MX-19 Beta 3 Feedback

#268 Post by bpr323 »

Woo-Hoo!!! BROTHERS AND SISTERS - I WAS ABLE TO INSTALL MX19b3 on my X1 carbon g4 this morning! I'm a genius! AMEN and PRAISE THE LORD
So ... here's the idiots guide to MX-19b3 auto-install using entire disk
1) I burnt a new MX19b3 "base" ISO with LUM using my working MX-19 b2.1 on X1 g5
2) Took my X1 g4 running MX-18.3-sept and changed in BIOS Boot = [UEFI Only] and SRM = [DISABLED] ----- > thank you Eadwine Rose !!!!!!! :number1:
3) Booted X1 g4 from MX-19b3 USB to live desktop
Now, important note for MX Devs
I don't know what use cases you guys test for the minstall GUI routine, but I went through these:
a) User is installing 19.3 on top of existing MX-18.3 (gpt partition table, but boot is on mbr as per my case) -> FAIL with Error msg "Cannot format required partitions"
b) After failed step (a) User has re-formatted MX-18.3 partitions to Fat32 and Ext4 respectively - nothing fancy-shmancy like changing labels, mount points, etc. -> FAIL Gpt shows (!) for ESP (missing software)
c) Lets assume User has a brand new NVMe M.2 (or wants to blow it away) - let's create msdos partition table with Gparted (but no partitions) and format entire disk to Fat32 -> FAIL
d) as above, let's create gpt partitions table (but no partitions) and format entire disk to Ext4 -> FAIL
e) let's create a new gpt partitions table and leave the disk unformatted - SUCCESS
SUMMARY
Your MX-19b3 auto-install GUI with UEFI will FAIL if:
1) You haven't set up your BIOS correctly, i.e. Secure Boot = [DISABLED] + UEFI Boot = [UEFI Only] + SMR = [DIsabled]
2) You're installing 19b3 over MX-18.3 which has had its boot set to MBR, or any other scenario except you blow away your entire disk and create a new GPT partition table (do NOT create any partitions and do NOT format the disk)
NEXT Test Cycle
Install MX19b3 from customised snapshot ISO (minstall.conf regression if/when Devs fix it) on:
a) same machine, over existing 19b3 (recovery)
b) different machine with whole disk blown away - as per Use case (e) above

User avatar
asqwerth
Developer
Posts: 7787
Joined: Sun May 27, 2007 5:37 am

Re: MX-19 Beta 3 Feedback

#269 Post by asqwerth »

I'm a bit confused, but if you were manually trying to install mx19 over a specific existing partition, that isn't "auto install using entire disk", right?

:confused:
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400

User avatar
bpr323
Posts: 172
Joined: Thu Jun 20, 2019 10:17 am

Re: MX-19 Beta 3 Feedback

#270 Post by bpr323 »

asqwerth wrote: Wed Oct 09, 2019 11:33 pm I'm a bit confused, but if you were manually trying to install mx19 over a specific existing partition, that isn't "auto install using entire disk", right?

:confused:
Yes, you are.
Where in my use cases above does it say "manually install" :rolleyes:
I was trying to do the "auto-install using entire disk" but each time after it failed I would go to Gparted and try to delete/format the partitions on my disk and repeat auto install again - without using "custom install" (bottom option) which you refer to as "manual"

Locked

Return to “General”