Hide Forgot
Created attachment 840380 [details] dmesg from boot Description of problem: [rms@roque ~]$ sudo modprobe samsung-laptop modprobe: ERROR: could not insert 'samsung_laptop': No such device Version-Release number of selected component (if applicable): [rms@roque ~]$ rpm -q kernel kernel-3.11.6-301.fc20.x86_64 kernel-3.11.10-301.fc20.x86_64 [rms@roque ~]$ uname -a Linux roque 3.11.10-301.fc20.x86_64 #1 SMP Thu Dec 5 14:01:17 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Actual results: Strange failure, what device is it looking for? Why is it not there? samsung directory is not present: [rms@roque ~]$ ls -laF /sys/devices/platform/ total 0 drwxr-xr-x. 12 root root 0 Dec 22 17:38 ./ drwxr-xr-x. 14 root root 0 Dec 22 17:38 ../ drwxr-xr-x. 3 root root 0 Dec 22 17:38 alarmtimer/ drwxr-xr-x. 4 root root 0 Dec 22 17:38 coretemp.0/ drwxr-xr-x. 3 root root 0 Dec 22 17:38 efifb.0/ drwxr-xr-x. 4 root root 0 Dec 22 17:38 Fixed MDIO bus.0/ drwxr-xr-x. 5 root root 0 Dec 22 17:38 i8042/ drwxr-xr-x. 3 root root 0 Dec 22 17:38 microcode/ drwxr-xr-x. 3 root root 0 Dec 22 17:38 pcspkr/ drwxr-xr-x. 2 root root 0 Dec 22 17:49 power/ drwxr-xr-x. 3 root root 0 Dec 22 17:38 regulatory.0/ drwxr-xr-x. 4 root root 0 Dec 22 17:38 serial8250/ -rw-r--r--. 1 root root 4096 Dec 22 17:38 uevent [rms@roque ~]$ Expected results: Loaded module, /sys/devices/platform/samsung/... available exposing access to features like controlling keyboard brightness and fan
Still happens with Linux 3.12: [rms@roque f]$ sudo modprobe samsung-laptop [sudo] password for rms: modprobe: ERROR: could not insert 'samsung_laptop': No such device [rms@roque f]$ uname -a Linux roque 3.12.5-302.fc20.x86_64 #1 SMP Tue Dec 17 20:42:32 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux [rms@roque f]$
Hi Rui, the driver returns ENODEV when loaded under the following conditions: - Booted from EFI - Dmi fields not recognized Can you upload the output of dmidecode to this case please? Thanks, Michele
Created attachment 844263 [details] sudo dmidecode > demidecode.txt
I guess I'm screwed as I'm booting under EFI. Will I have to find out how to revert back to legacy BIOS or is it safer to reinstall? In any case, I have attached dmidecode's output.
Hi Rui, the reason it is disabled with EFI is the following: commit e0094244e41c4d0c7ad69920681972fc45d8ce34 Author: Matt Fleming <matt.fleming> Date: Thu Jan 3 09:02:37 2013 +0000 samsung-laptop: Disable on EFI hardware It has been reported that running this driver on some Samsung laptops with EFI can cause those machines to become bricked as detailed in the following report, https://bugs.launchpad.net/ubuntu-cdimage/+bug/1040557 There have also been reports of this driver causing Machine Check Exceptions on recent EFI-enabled Samsung laptops, https://bugzilla.kernel.org/show_bug.cgi?id=47121 So disable it if booting from EFI since this driver relies on grovelling around in the BIOS memory map which isn't going to work. The DMI info would match, so we can definitely confirm that it is the EFI thing. I have no idea what's faster (reinstall vs. tweaking around) sorry
OH, ok, I see. I read about this a long while ago, I expected this would have been fixed in the meanwhile and not an issue anymore. I will reinstall with legacy boot then, thanks!