I recommend drinking
Announcement
Collapse
No announcement yet.
Three PC Brands Where SecureBoot On Linux Is Botched
Collapse
X
-
-
Originally posted by Ex-Cyber View PostI think the most likely scenario is that the option to disable it remains present, but Windows 9 or 10 will refuse to "activate" unless it's enabled. Not so much for Microsoft's sake (they'd rather have you using an illegal Windows system than a legal Linux system), but rather to enforce restrictions on Windows Store apps.
Comment
-
What does this mean for installing/booting Linux on Samsung laptops?
This is probably a "dumb question" -- but I am not clear on the point:
Since this "samsung-laptop" driver is not usable, what happens when someone tries to install (or boot) Linux on an affected Samsung laptop, without using that driver?
(or for that matter, on unaffected ones)?
Is there a more generic driver as fall-back?
Does the boot just hang?
Comment
-
Originally posted by Bernard Swiss View PostThis is probably a "dumb question" -- but I am not clear on the point:
Since this "samsung-laptop" driver is not usable, what happens when someone tries to install (or boot) Linux on an affected Samsung laptop, without using that driver?
(or for that matter, on unaffected ones)?
Is there a more generic driver as fall-back?
Does the boot just hang?All opinions are my own not those of my employer if you know who they are.
Comment
-
Originally posted by Ericg View PostCertain things may not work, such as multimedia keys or maybe suspend or key-based backlight control. Really depends on just how much hardware control is samsung-specific and therefore how much of "normal" control is altered by samsung-laptop. I know on Dell systems if you dont boot with dell-laptop then suspend and backlight can be f*cked up.
That gives me a significantly better idea what we're talking about.
On the other hand, I don't see why those should need vendor/model specific drivers, in the first place...
I personally wouldn't care about multi-media keys, but things like suspend/hibernate and backlight control do make a real difference.
Comment
-
Originally posted by Bernard Swiss View PostThanks!
That gives me a significantly better idea what we're talking about.
On the other hand, I don't see why those should need vendor/model specific drivers, in the first place...
I personally wouldn't care about multi-media keys, but things like suspend/hibernate and backlight control do make a real difference.
Backlight is a problem because maybe some wires aren't where they are "Normally" or maybe a jumper is backwards, things like that. This laptop specifically (Dell XPS 13z Ultrabook) doesn't have the normal backlight control, its vendor specific instead of just being "Intel backlight." I had to go further than most to get Linux running on here, I had to run a custom kernel and even then its not exactly how I want things to be. For example thanks to what is either a buggy bios or a buggy disk controller, this laptop refuses to boot with the new GPT partition layout. Granted its not a big deal to do the old style MS-DOS style layout, but its still a problem.All opinions are my own not those of my employer if you know who they are.
Comment
-
Originally posted by grotgrot View PostYou could then be reassured that only operating systems and their kernels that you allow to run are in fact what is running.
If you manage a whole bunch of servers in data centre, it would again be nice to know that only kernels you authorise can run on the systems.
The only real value in 'Secure Boot' is enforcing vendor lockin on the people who buy the hardware. For everyone else its a real pain for minimal benefit.
Comment
Comment