[Bug 1111689] Re: Due to possibly bricking the system, the samsung-laptop driver should not be allowed to run if booting from EFI
** Changed in: linux (Ubuntu) Status: Incomplete = Invalid ** Changed in: linux (Ubuntu Precise) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/689 Title: Due to possibly bricking the system, the samsung-laptop driver should not be allowed to run if booting from EFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1111689] Re: Due to possibly bricking the system, the samsung-laptop driver should not be allowed to run if booting from EFI
Brad Figg, given this report has some overlap with https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1199401 and the requested patches are in Raring+ as per: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-raring.git;a=commit;h=83e68189745ad931c2afd45d8ee3303929233e7f http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-raring.git;a=commit;h=e0094244e41c4d0c7ad69920681972fc45d8ce34 Would there be anything else or may the linux (Ubuntu) task be closed out? ** Changed in: linux (Ubuntu) Status: In Progress = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/689 Title: Due to possibly bricking the system, the samsung-laptop driver should not be allowed to run if booting from EFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1111689] Re: Due to possibly bricking the system, the samsung-laptop driver should not be allowed to run if booting from EFI
This bug was fixed in the package linux - 3.5.0-24.37 --- linux (3.5.0-24.37) quantal-proposed; urgency=low [Luis Henriques] * Release Tracking Bug - LP: #1117492 [ Tim Gardner ] * [Config] CONFIG_ALX=m for x86 only - LP: #927782 linux (3.5.0-24.36) quantal-proposed; urgency=low [Luis Henriques] * Release Tracking Bug - LP: #1116501 [ Adam Lee ] * [Config] Enable RTSX_PCI modules - LP: #1057089 [ Andy Whitcroft ] * [Config] enable various HVC consoles - LP: #1102206 [ Brad Figg ] * Revert SAUCE: samsung-laptop: disable in UEFI mode - LP: #689 [ Herton Ronaldo Krzesinski ] * [Config] updateconfigs for 3.5.7.3 stable update * d-i: Add mellanox ethernet drivers to nic-modules - LP: #1015339 [ Kamal Mostafa ] * SAUCE: alx driver import script - LP: #927782 [ Qualcomm Atheros, Inc ] * SAUCE: alx: Update to heads/master - LP: #927782 [ Seth Forshee ] * SAUCE: samsung-laptop: Add quirk for broken acpi_video backlight on N250P - LP: #1086921 [ Stefan Bader ] * (config) Move 9p modules into generic package - LP: #1107658 [ Tim Gardner ] * [debian] Remove dangling symlink from headers package - LP: #1112442 * [config] CONFIG_ALX=m - LP: #927782 * [Config] Add alx to d-i nic-modules - LP: #927782 [ Upstream Kernel Changes ] * Revert 8139cp: revert set ring address before enabling receiver - LP: #1102417 * Revert ath9k_hw: Update AR9003 high_power tx gain table - LP: #1102417 * Revert drm/i915: no lvds quirk for Zotac ZDBOX SD ID12/ID13 - LP: #1102417 * Revert ALSA: hda - Shut up pins at power-saving mode with Conexnat codecs - LP: #1106966, #886975 * be2net: don't call vid_config() when there's no vlan config - LP: #1083088 * be2net: cleanup be_vid_config() - LP: #1083088 * be2net: do not modify PCI MaxReadReq size - LP: #1083088 * be2net: fix reporting number of actual rx queues - LP: #1083088 * be2net: do not use SCRATCHPAD register - LP: #1083088 * be2net: Fix driver load for VFs for Lancer - LP: #1083088 * be2net: Explicitly clear the reserved field in the Tx Descriptor - LP: #1083088 * be2net: Regression bug wherein VFs creation broken for multiple cards. - LP: #1083088 * be2net: Fix to trim skb for padded vlan packets to workaround an ASIC Bug - LP: #1083088 * be2net: Fix Endian - LP: #1083088 * be2net: Fix error while toggling autoneg of pause parameters - LP: #1083088 * be2net : Fix die temperature stat for Lancer - LP: #1083088 * be2net: Fix initialization sequence for Lancer - LP: #1083088 * be2net: Activate new FW after FW download for Lancer - LP: #1083088 * be2net: Fix cleanup path when EQ creation fails - LP: #1083088 * be2net: Enable RSS UDP hashing for Lancer and Skyhawk - LP: #1083088 * be2net: dont pull too much data in skb linear part - LP: #1083088 * be2net: Fix VF driver load for Lancer - LP: #1083088 * be2net: Ignore physical link async event for Lancer - LP: #1083088 * be2net: Fix to parse RSS hash from Receive completions correctly. - LP: #1083088 * netpoll: revert 6bdb7fe3104 and fix be_poll() instead - LP: #1083088 * be2net: create RSS rings even in multi-channel configs - LP: #1083088 * be2net: fix max VFs reported by HW - LP: #1083088 * be2net: fix FW default for VF tx-rate - LP: #1083088 * be2net: fixup malloc/free of adapter-pmac_id - LP: #1083088 * be2net: fix wrong handling of be_setup() failure in be_probe() - LP: #1083088 * be2net: cleanup code related to be_link_status_query() - LP: #1083088 * be2net: fix vfs enumeration - LP: #1083088 * be2net: Remove code that stops further access to BE NIC based on UE bits - LP: #1083088 * mtip32xx: Add support for new devices - LP: #1099913 * mtip32xx: Handle NCQ commands during the security locked state - LP: #1099913 * mtip32xx: Increase timeout for standby command - LP: #1099913 * mtip32xx: Proper reporting of write protect status on big-endian - LP: #1099913 * mtip32xx: Change printk to pr_ - LP: #1099913 * mtip32xx: Remove dead code - LP: #1099913 * mtip32xx: fix user_buffer check in exec_drive_command - LP: #1099913 * mtip32xx:Added appropriate timeout value for secure erase - LP: #1099913 * mtip32xx: fix potential crash on SEC_ERASE_UNIT - LP: #1099913 * mtip32xx: Fix to make lba address correct in big-endian systems - LP: #1099913 * mtip32xx: Fix incorrect mask used for erase mode - LP: #1099913 * mtip32xx: fix shift larger than type warning - LP: #1099913 * mtip32xx: fix potential NULL pointer dereference in mtip_timeout_function() - LP: #1099913 * mtip32xx: Fix padding issue - LP: #1099913 * KVM: PPC: e500: fix allocation size error on g2h_tlb1_map - LP: #1102417 *
[Bug 1111689] Re: Due to possibly bricking the system, the samsung-laptop driver should not be allowed to run if booting from EFI
@fabri We reverted an earlier version of the patch to disable the samsung- laptop driver and then committed a newer, better version of the patch that came from upstream. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/689 Title: Due to possibly bricking the system, the samsung-laptop driver should not be allowed to run if booting from EFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1111689] Re: Due to possibly bricking the system, the samsung-laptop driver should not be allowed to run if booting from EFI
I don't actually have a Samsung laptop to try this on however, the patches were clean cherry-picks of the upstream commits which have been Linus' tree for a little while so should have gotten some testing. I recommend that we accept these changes and I'm going go to ahead and mark this as verified. ** Tags removed: verification-needed-quantal ** Tags added: verification-done-quantal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/689 Title: Due to possibly bricking the system, the samsung-laptop driver should not be allowed to run if booting from EFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1111689] Re: Due to possibly bricking the system, the samsung-laptop driver should not be allowed to run if booting from EFI
Just checked the kernel on my samsung 530u3c laptop, and it works, thanks Brad. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/689 Title: Due to possibly bricking the system, the samsung-laptop driver should not be allowed to run if booting from EFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1111689] Re: Due to possibly bricking the system, the samsung-laptop driver should not be allowed to run if booting from EFI
Dear Bratt, I have a samsung 530u3c on which I installed a recent daily image of precise with the kernel 3.5.0-23-generic #35~precise1-Ubuntu SMP Fri Jan 25 17:13:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux In my update-manager I have your kernel (3.5.0-24.37) as an update in the proposed updates. In the changelog is written * Revert SAUCE: samsung-laptop: disable in UEFI mode I don't really want samsung-laptop to run, but with this changelog message it looks as if it is re-instated. I am not sure if I should update now, because I don't want to run samsung-laptop and risk to brick my samsung. Now in the title of this bug report it is written that samsung-laptop should not be run in uefi mode... I am confused. If you can reassure me that samsung-laptop does not run under uefi with this kernel I could try it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/689 Title: Due to possibly bricking the system, the samsung-laptop driver should not be allowed to run if booting from EFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1111689] Re: Due to possibly bricking the system, the samsung-laptop driver should not be allowed to run if booting from EFI
This bug is awaiting verification that the kernel for Quantal in -proposed solves the problem (3.5.0-24.37). Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-quantal' to 'verification-done-quantal'. If verification is not done by one week from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-quantal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/689 Title: Due to possibly bricking the system, the samsung-laptop driver should not be allowed to run if booting from EFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1111689] Re: Due to possibly bricking the system, the samsung-laptop driver should not be allowed to run if booting from EFI
** Changed in: linux (Ubuntu Quantal) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/689 Title: Due to possibly bricking the system, the samsung-laptop driver should not be allowed to run if booting from EFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1111689] Re: Due to possibly bricking the system, the samsung-laptop driver should not be allowed to run if booting from EFI
There are a larger number of commits involved in pulling this functionality back into Precise. Test kernels can be found at: http://people.canonical.com/~bradf/lp689/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/689 Title: Due to possibly bricking the system, the samsung-laptop driver should not be allowed to run if booting from EFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
