In a similar vein to this comment, I have just got a new Samsung Series 9 laptop (has a build stamp of May 2013, so I'm hoping it would be free of the EFI bug) and installed Fedora 19 on it. It took me a fair bit of internet searching until I found that this was the reason that things like the keyboard backlight can't be controlled.
I installed F19 in UEFI mode, but it doesn't boot if I change it to CSM, I guess because there's no standard grub MBR? Are there any other pros/cons of CSM?
For now I will probably stick with UEFI, but if there's a compelling reason to change, I will. I'd really like these nice features to all work 100% though. Is there any way to force samsung-laptop to load? Or any way to check if the EFI bug has been resolved? My laptop is still under warranty so I'm not too worried about the possibility of a brick.
Power management, mobile and firmware developer on Linux. Security developer at Aurora. Ex-biologist. mjg59 on Twitter. Content here should not be interpreted as the opinion of my employer. Also on Mastodon.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Re: Samsung-module
Date: 2013-08-01 02:38 pm (UTC)I installed F19 in UEFI mode, but it doesn't boot if I change it to CSM, I guess because there's no standard grub MBR? Are there any other pros/cons of CSM?
For now I will probably stick with UEFI, but if there's a compelling reason to change, I will. I'd really like these nice features to all work 100% though. Is there any way to force samsung-laptop to load? Or any way to check if the EFI bug has been resolved? My laptop is still under warranty so I'm not too worried about the possibility of a brick.