Profile
Matthew Garrett
About Matthew
Active Entries
- 1: TVs are all awful
- 2: More in the series of bizarre UEFI bugs
- 3: Samsung laptop bug is not Linux specific
- 4: Playing with Thunderbolt under Linux on Apple hardware
- 5: A short introduction to TPMs
- 6: Rebooting
- 7: Update on leaked UEFI signing keys - probably no significant risk
- 8: Leaked UEFI signing keys
- 9: Secure Boot and Restricted Boot.
- 10: The current state of UEFI and Linux
Expand Cut Tags
No cut tags
no subject
Date: 2013-02-01 09:42 am (UTC)Basically the Kernel "oopsed" and when i rebooted the motherboard turned out fried. At the time i did not report it because i did not have much information about the event and i was, and i am, still not sure what happened. Now that i read about the Samsung issue i find that very familiar. Anyway, fortunately my D30 was still under warranty and i was not able to reproduce after it was repaired.
I also was not able to boot Fedora 18 UEFI installation on both my D30 as well as my X220. I use to have Fedora 16 installed in UEFI mode and it worked fine. In Fedora 18 i was not able to make that work. When i press the Fedora item from the UEFI menu nothing happens (Nothing bootable found). It might just be me but even if so, i guess it is not as intuitive as it could be.