joecool
Posts: 7
Joined: Mon Oct 30, 2017 10:46 am

Re: [SOLVED] can't use keyboard/touchpad on boot

Thu Nov 02, 2017 9:07 am

Hi justin,
Thank you for the tip.
Justin wrote:
Thu Nov 02, 2017 6:26 am
Solus Blog wrote:You can add your required kernel arguments to /etc/kernel/cmdline or /etc/kernel/cmdline/*.conf, and clr-boot-manager will merge those as appropriate into the final command line for each kernel. This is merged with the vendor cmdline, part of the kernel package, and any automatic cmdline that may be generated by clr-boot-manager itself (such as the root= or rd.luks.uuid= parameters). Once done, just run sudo clr-boot-manager update to commit the changes.
I made a directory cmdline in /etc/kernel and Solus-lts-4.9.59-55.conf inside like this:

/etc/kernel/cmdline/Solus-lts-4.9.59-55.conf

Code: Select all

radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1
Then I did sudo clr-boot-manager update but nothing has been changed at all.

I also gave a shot to the following but to no avail:

/etc/kernel/cmdline/Solus-lts-4.9.59-55.conf

Code: Select all

title Solus 3
linux /EFI/com.solus-project/kernel-com.solus-project.lts.4.9.59-55
initrd /EFI/com.solus-project/initrd-com.solus-project.lts.4.9.59-55
options root=PARTUUID=2f74cb71-6645-46da-8eee-e50f30d80130 quiet loglevel=3 splash systemd.show_status=false rw radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1

User avatar
Justin
Development Team
Posts: 3613
Joined: Mon Jul 28, 2014 10:42 am
Location: Adelaide, Australia
Contact: Website Google+ Twitter

Re: [SOLVED] can't use keyboard/touchpad on boot

Thu Nov 02, 2017 10:43 am

cmdline is the file you need to put things in, not a folder :)

sunnyflunk
Development Team
Posts: 2892
Joined: Sun Mar 13, 2016 11:35 pm

Re: [SOLVED] can't use keyboard/touchpad on boot

Fri Nov 03, 2017 6:58 am

joecool wrote:
Thu Nov 02, 2017 5:02 am
This is just for a side note, but could possibly help some other people suffering from similar problems:

After some playing around with EFI, I found a slight difference between /boot/efi/loader/entries/Solus-current-4.13.10-30.conf and /boot/efi/loader/entries/Solus-lts-4.9.59-55.conf:

Solus-current-4.13.10-30.conf

Code: Select all

title Solus 3
linux /EFI/com.solus-project/kernel-com.solus-project.current.4.13.10-30
initrd /EFI/com.solus-project/initrd-com.solus-project.current.4.13.10-30
options root=PARTUUID=2f74cb71-6645-46da-8eee-e50f30d80130 quiet loglevel=3 splash systemd.show_status=false rw radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 
Solus-lts-4.9.59-55.conf

Code: Select all

title Solus 3
linux /EFI/com.solus-project/kernel-com.solus-project.lts.4.9.59-55
initrd /EFI/com.solus-project/initrd-com.solus-project.lts.4.9.59-55
options root=PARTUUID=2f74cb71-6645-46da-8eee-e50f30d80130 quiet loglevel=3 splash systemd.show_status=false rw 
You can see there's an additional line "radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1" on Solus-current-4.13.10-30.conf.I thought this might be a cause for the problem and tried to fix it by adding the line to Solus-lts-4.9.59-55.conf via nano.But the line disappears at all as soon as I run sudo clr-boot-manager update .

I wonder it could possibly fix the problem if I can add the line successfully to Solus-lts-4.9.59-55.conf.It's just what I thought as an inexperienced newbie though... :idea:
4.9 kernel is too old to have support for those features, hence, they aren't included for that kernel.

joecool
Posts: 7
Joined: Mon Oct 30, 2017 10:46 am

Re: [SOLVED] can't use keyboard/touchpad on boot

Fri Nov 03, 2017 8:57 am

Thank you justin and sunnyflunk.
cmdline is the file you need to put things in, not a folder :)
That really makes sense, I totally got it now.It seems like I can do sudo cat /etc/kernel/cmdline radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 and then sudo clr-boot-manager update but I'm not courageous enough to modify the system as it'd possibly do some harm even to my current kernel.
4.9 kernel is too old to have support for those features, hence, they aren't included for that kernel.
Then there seems to be no choice other than waiting for a future update for some fix.

Anyway, you all have made my day so much and now It's been solved. :)

Return to “Tutorials”