MX Linux Forum

Posted: **Mon Sep 09, 2019 12:58 am**

I don't know why it didn't install on your computer so I cannot tell you if the changes would influence that, but there were fixes in the installer. It's only you who can tell us if it installs on your computer, we cannot tell you if it will install on your computer. If it's too hard to test, then don't test it and cross the fingers that the official release will work.

Posted: **Mon Sep 09, 2019 1:00 am**

blindside wrote: Mon Sep 09, 2019 12:35 am I tried the first beta and it would just not work. Put 18.3 back on, but wondering if it was worth it to try the next beta iteration?

"Work" as in,

1) cannot even bootup, or
2) can boot up live but can't install?

If the latter, I'm sure the devs working on the installer like AK-47, fehlix, etc would love to hear from you, as your terminal output might help them squash even more bugs.

If 1), the live system devs would love to hear from you.

Posted: **Mon Sep 09, 2019 1:18 am**

Running from Live USB. Have found no problems so far. Did take a long time to get WiFi setup, needed driver unblacklisted.

Siles]

Posted: **Mon Sep 09, 2019 1:58 am**

dolphin_oracle wrote: Sun Sep 08, 2019 7:19 pm try this installer please:

https://drive.google.com/open?id=17fyNn ... YwX_zBfiWa

Success ! I could install to sda20

One remark, when i chose to install grub to pbr , the drop-down did not defautl to the root i had chosen (sda20) but to the first linux-type partition (sda7)
I wanted to post the minstall.log, but the system rebooted at the end of installation (without prompting me)
Also i am a little surprised at the one-line fstab that was generated

Code: Select all

# Pluggable devices are handled by uDev, they are not in fstab
UUID=6d78f48e-4c54-449d-9774-1a6dd5b15ec3 / ext4 defaults 1 1

edit: forget the remark about eagerly rebooting, i simply had not noticed the checkbox in the last installer screen (reboot immediately or something to that effect)

Posted: **Mon Sep 09, 2019 3:32 am**

First test on Samsung Laptop with Nvidia GFX

Clean install to existing partition.
Installed OK - auto-mounting and auto-opening a window for each partition appears to be fixed on Installer, but NOT on Thunar. So, if you're just exploring the Live session and plug in an external USB HDD a window opens for each partition... this might freak-out newish users with many partitions on external media.
All settings carried over from Live session to install

Code: Select all

System:    Host: mx19 Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           Desktop: Xfce 4.14.1 Distro: MX-19beta-2.1_x64 patito feo September 8  2019 
           base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Laptop System: SAMSUNG product: RV411/RV511/E3511/S3511/RV711 v: N/A 
           serial: <filter> 
           Mobo: SAMSUNG model: RV411/RV511/E3511/S3511/RV711 serial: <filter> BIOS: Phoenix 
           v: 03PA.M001.20110312.XW date: 03/12/2011 
Battery:   ID-1: BAT1 charge: 5.4 Wh condition: 5.4/47.5 Wh (11%) model: SAMSUNG Electronics 
           status: Full 
CPU:       Topology: Dual Core model: Intel Core i3 M 380 bits: 64 type: MT MCP arch: Nehalem 
           rev: 5 L2 cache: 3072 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 20218 
           Speed: 1463 MHz min/max: 933/2533 MHz Core speeds (MHz): 1: 1464 2: 1463 3: 1463 
           4: 1463 
Graphics:  Device-1: NVIDIA GT218M [GeForce 315M] vendor: Samsung Co driver: nouveau v: kernel 
           bus ID: 02:00.0 
           Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1366x768~60Hz 
           OpenGL: renderer: NVA8 v: 3.3 Mesa 18.3.6 direct render: Yes 
Audio:     Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Samsung Co 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
           Device-2: NVIDIA High Definition Audio vendor: Samsung Co driver: snd_hda_intel 
           v: kernel bus ID: 02:00.1 
           Sound Server: ALSA v: k4.19.0-6-amd64 
Network:   Device-1: Broadcom Limited BCM4313 802.11bgn Wireless Network Adapter vendor: Askey 
           driver: wl v: kernel port: 2000 bus ID: 03:00.0 
           IF: wlan0 state: dormant mac: <filter> 
           Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Samsung Co 
           driver: r8169 v: kernel port: 4000 bus ID: 05:00.0 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 1.14 TiB used: 5.09 GiB (0.4%) 
           ID-1: /dev/sda vendor: Seagate model: ST1000LM048-2E7172 size: 931.51 GiB 
           ID-2: /dev/sdb type: USB vendor: Toshiba model: MK2555GSX H size: 232.89 GiB 
Partition: ID-1: / size: 25.71 GiB used: 5.09 GiB (19.8%) fs: ext4 dev: /dev/sdb8 
Sensors:   System Temperatures: cpu: 57.0 C mobo: 57.0 C gpu: nouveau temp: 61 C 
           Fan Speeds (RPM): N/A 
Info:      Processes: 186 Uptime: 2m Memory: 5.69 GiB used: 485.0 MiB (8.3%) Init: SysVinit 
           runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 inxi: 3.0.33

First test on Toshiba Laptop with AMD GFX

Clean install to existing partition.
Installed OK - auto-mounting and auto-opening a window for each partition appears to be fixed on Installer, but NOT on Thunar. So, if you're just exploring the Live session and plug in an external USB HDD a window opens for each partition... this might freak-out newish users with many partitions on external media.
All settings carried over from Live session to install

Code: Select all

System:    Host: mx19 Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           Desktop: Xfce 4.14.1 Distro: MX-19beta-2.1_x64 patito feo September 8  2019 
           base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Laptop System: TOSHIBA product: Satellite L650D v: PSK1SE-00C00PEN 
           serial: <filter> 
           Mobo: TOSHIBA model: Portable PC serial: <filter> BIOS: Insyde v: 1.80 
           date: 06/29/2011 
Battery:   ID-1: BAT0 charge: 22.8 Wh condition: 23.1/47.5 Wh (49%) model: PA3817U-1BRS 
           status: Charging 
CPU:       Topology: Dual Core model: AMD Turion II P520 bits: 64 type: MCP arch: K10 rev: 3 
           L2 cache: 2048 KiB 
           flags: lm nx pae sse sse2 sse3 sse4a svm bogomips: 9177 
           Speed: 800 MHz min/max: 800/2300 MHz Core speeds (MHz): 1: 800 2: 800 
Graphics:  Device-1: AMD RV710/M92 [Mobility Radeon HD 4530/4570/545v] 
           vendor: Toshiba America Info Systems driver: radeon v: kernel bus ID: 01:00.0 
           Display: x11 server: X.Org 1.20.4 driver: ati,radeon unloaded: fbdev,modesetting,vesa 
           resolution: 1366x768~60Hz 
           OpenGL: renderer: AMD RV710 (DRM 2.50.0 / 4.19.0-6-amd64 LLVM 7.0.1) 
           v: 3.3 Mesa 18.3.6 direct render: Yes 
Audio:     Device-1: AMD SBx00 Azalia vendor: Toshiba America Info Systems driver: snd_hda_intel 
           v: kernel bus ID: 00:14.2 
           Device-2: AMD RV710/730 HDMI Audio [Radeon HD 4000 series] 
           vendor: Toshiba America Info Systems driver: snd_hda_intel v: kernel bus ID: 01:00.1 
           Sound Server: ALSA v: k4.19.0-6-amd64 
Network:   Device-1: Realtek RTL8191SEvB Wireless LAN driver: rtl8192se v: kernel port: 3000 
           bus ID: 02:00.0 
           IF: wlan0 state: up mac: <filter> 
           Device-2: Qualcomm Atheros AR8152 v1.1 Fast Ethernet 
           vendor: Toshiba America Info Systems driver: atl1c v: 1.0.1.1-NAPI port: 2000 
           bus ID: 08:00.0 
           IF: eth0 state: down mac: <filter> 
Drives:    Local Storage: total: 344.68 GiB used: 4.89 GiB (1.4%) 
           ID-1: /dev/sda vendor: Fujitsu model: MHW2120BH size: 111.79 GiB 
           ID-2: /dev/sdb type: USB vendor: Toshiba model: MK2555GSX H size: 232.89 GiB 
Partition: ID-1: / size: 25.71 GiB used: 4.89 GiB (19.0%) fs: ext4 dev: /dev/sdb8 
Sensors:   System Temperatures: cpu: 59.8 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Info:      Processes: 156 Uptime: 4m Memory: 2.93 GiB used: 453.4 MiB (15.1%) Init: SysVinit 
           runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 inxi: 3.0.33

FN Keys for Brightness work out-of-the-box on AMD-based Laptop - Needed acpi_backlight=vendor etc to fix on Nvidia-based Laptop

Posted: **Mon Sep 09, 2019 3:39 am**

jorgosek wrote: Sun Sep 08, 2019 11:55 pm USB Live.LibreOffice not start,just flash for a moment.

Were you running liveUSB at the time AND running the installer, or?

Because I saw the same thing happen in that exact scenario.

Posted: **Mon Sep 09, 2019 3:41 am**

rej wrote: Mon Sep 09, 2019 12:06 am
Don't know if this is intentional:

When the panels (transparent or not) are in "hidden" mode, they leave a white line on the screen where they are hidden.

Could this be that you are running Compton or similar and have shadows (I believe that is what it is called) enabled?

Posted: **Mon Sep 09, 2019 4:21 am**

Needed acpi_backlight=vendor etc to fix on Nvidia-based Laptop

What's the "etc" part? Is this boot parameter something that needs to go in the Manual/Wiki?

Posted: **Mon Sep 09, 2019 4:40 am**

On a UEFI machine, updated from live, during install no disk is pre-selected for the user. The 'Use Disk' field is blank. Selecting 'Auto install using entire disk' with the 'Use Disk' field blank is permitted. The confirmation pop-up asks if disk(0) should be used. Clicking 'Yes' causes the installer to close. Launching the installer again, and trying to manually select a disk to install to fails because no disk can be selected; the field stays blank.

Re-booting, but not updating first allows installation to proceed normally, with the only disk in the machine appearing in the 'Use Disk@ filed.

Installation worked normally on this machine with 19b1.

Chris

Posted: **Mon Sep 09, 2019 4:55 am**

That's a known issue with the most recent version of the installer (19.9.05). You can check which version you have by running: minstall --version
The previous build (19.9.03) does not have this problem and is the one included in MX 19b2.1 so, just this time, try it without updating the installer.

MX Linux Forum

MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: (cannot install to sda20)

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback

Re: MX-19 Beta 2.1 Feedback