ASUS UX31E and GL752VW (T4092T) : OMLx 3.03 installation


#1

Hello,
I’d like to share how I installed the current last OMLx release in November. Both laptops were running OMLx 2014 before but as this version is not supported anymore I had to switch to the future. It was a bit scary… :wink:

UX31E
2014.2 was running perfectly on it. I had to resize the partitions and the things went wrong. Thanks to a wise backup done before proceeding I recovered my home partition. I decided to install 3.03. All went fine and everything is working as expected!

The only issue came from the id/group of the main user’s home. Previously they started at 500, now they start at 1000. There is two solutions: either you manually set the id/group of the 3.03 user(s) to match the 2014 one(s), or you change the id/group of all documents of the former home.
I chose the 2d solution because I didn’t want my main user to be considered as a service by the system.
A simple command line did the trick:

find /home2/jcl/ -user 501 -group 506 -exec chown jcl:jcl '{}' \;

As you can see, the former id/group was 501/506. I must add that I always mount the home partition as /home2/, then, step by step, I create links to the actual home directory. Thus I can do some tests before really using my own files. This is particularly true for config fles.

GL752VW
Unfortunately, the things weren’t as simple. The first challenge were to start the live mode.
Details: the laptop has the last available bios (Version 214 - 09/12/2017) and the secure boot is disabled.

If I edit the basic graphics mode entry, I can delete the nomodeset parameter:

and bingo:


Note: when starting the basic graphics mode in VBox, it is also necessary to remove nomodeset.

  • I’m now able to install the system. Nothing wrong till reboot.

  • Reboot : the default kernel parameters don’t let me get a graphical session. Here they are:

BOOT_IMAGE=/boot/vmlinuz-4.13.12-desktop-2omv

root=UUID= 74e869a6-ea0e-47c4-b258-20b47da20be1 
ro 
scsi_mod.use_blk_mq=1 
quiet 
resume=UUID=27b0197b-854a-46b8-8571-77392934ce8a
rw 
logo.nologo 
audit=0

"acpi_osi=Linux" 
"acpi_osi=!Windows 2012" 

acpi_backlight=vendor 
rd.timeout=120

Some researches later, I finally chose (main changes in red):

BOOT_IMAGE=/boot/vmlinuz-4.13.12-desktop-2omv 
root=UUID=74e869a6-ea0e-47c4-b258-20b47da20be1 
ro 
scsi_mod.use_blk_mq=1 
quiet 
resume=UUID=27b0197b-854a-46b8-8571-77392934ce8a
rw 
logo.nologo 
audit=0 

"acpi_osi=!"
"acpi_osi=Windows 2009"

I don’t understand very well the effect of those parameters but now, I have a laptop which works almost perfectly and better than with 2014:

– the screen light can be adjusted (with 2014, only the kernel 4.1.15 nrjQL allowed that)
– the function keys work
– the suspend mode work (not possible with 2014 ==> X froze)
– the battery lasts longer (with governor powersave)
– the processors frequency can be boosted (nominal 2600 MHz, boost up to 3100 MHz; only 2600 MHz with kernel 4.1.15)

The only remaining issues are:
– non working touch pad (it seems this is the case with other distros)
– sometimes, since some updates that occurred in December, the system freezes if it remains not used for a long time (3 - 4 hours)

Now I can really use this laptop even during travel.
You know what? I’m happy :slight_smile:

EDIT: I had to add that the system is more reactive than before.


Compartir /home
(luca) #2

Sooner or later I’ll have to leave 2014 too, but keep a dual boot system.
I think it is possible change UID_MIN and GID_MIN parameter values to 500 in /etc/login.defs and in sddm.conf.


Je n'ai pas les permissions de modifier mes fichiers (partition de données commune)
#3

Thanks for the info. Anyway, I guess there will be more and more services and switching to uids/gids > 1000 will will be unavoidable one day.
If I remember well, in 1990’s, the uids started from 100…


#4

Good news (for me): since the kernel 4.19.8 I’m able to use the touch pad. All is functional.
And my laptop is still working :wink:
I hope this will still be the case with OMLx 4!
Thanks to all and happy new year.


(Tomasz Paweł Gajc) #5

Well it took me a lot of time to find missing kernel configs to enable that crazy touchpad setups over smbus. Yes on 4.0 it also works, as i was affected by that issue too.


#6

A special thanks to you TPG!