[Bug 635439] Re: No UEFI boot on Dell Precision M4500
*** This bug is a duplicate of bug 705588 *** https://bugs.launchpad.net/bugs/705588 ** This bug has been marked a duplicate of bug 705588 Dell latitute E6510 doesn't boot in uefi mode * You can subscribe to bug 705588 by following this link: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/705588/+subscribe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/635439 Title: No UEFI boot on Dell Precision M4500 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 705588] Re: Dell latitute E6510 doesn't boot in uefi mode
I marked #635439 as a duplicate of this bug, because I don't think it is a casper problem, but rather a Linux one. And it is not specific to the Dell Precision M4500 or the Dell Latitude E6510 because I ran into it with my Lenovo ThinkPad T420 as well. I also tried the UEFI-enabled unofficial Archboot Arch Linux boot CD and it hangs in the same way (the screen is just not blank but displays the GRUB2 background image forever, in Ubuntu 11.04 there is no background image so it is blank), so I am fairly sure these issues are highly related. Furthermore: I was able to reproduce the problem with the Archboot CD on a non-EFI system using VirtualBox where I enabled EFI emulation, set the Archboot-CD as boot device and had exactly the same behaviour as on my T420 hardware. Any ideas? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/705588 Title: Dell latitute E6510 doesn't boot in uefi mode -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 705588] Re: Dell latitute E6510 doesn't boot in uefi mode
Oh, phcoder in #grub suggested to use 'noefi' which works. But then I cannot use the efivars which is neccessary to set up GRUB2 properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/705588 Title: Dell latitute E6510 doesn't boot in uefi mode -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 216436] Re: [regression] Brightness hotkeys don't work anymore
*** This bug is a duplicate of bug 212790 *** https://bugs.launchpad.net/bugs/212790 Mika Fischer, you might have run into the same problem as in #146710, see my first comment. There seem to be various amounts of breakage: brightness not working via Fn-keys, various other Fn-keys not working, backlight modification not working at all. Do I understand you right? You updated the BIOS (just like me) and it stopped working? -- [regression] Brightness hotkeys don't work anymore https://bugs.launchpad.net/bugs/216436 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146710] Re: backlight brighness control does not work (Samsung Q45 with Nvidia GForce 8400M)
For me (on a R60+, as mentioned above) it is: [ 114.681006] atkbd.c: Unknown key pressed (translated set 2, code 0x88 on isa0060/serio0). [ 114.681006] atkbd.c: Use 'setkeycodes e008 keycode' to make it known. [ 115.279328] atkbd.c: Unknown key pressed (translated set 2, code 0x89 on isa0060/serio0). [ 115.279328] atkbd.c: Use 'setkeycodes e009 keycode' to make it known. So Samsung seems to disable these keys also in other models. Do you have the disable backlight button (Fn+F4)? Does it work? For me it doesn't: [ 242.132450] atkbd.c: Unknown key pressed (translated set 2, code 0x84 on isa0060/serio0). [ 242.132450] atkbd.c: Use 'setkeycodes e004 keycode' to make it known. Or can you disable WLAN (Fn+F9) (there's also a led on the front of the laptop). For me, it's broken, too: [ 298.608234] atkbd.c: Unknown key pressed (translated set 2, code 0x86 on isa0060/serio0). [ 298.608234] atkbd.c: Use 'setkeycodes e006 keycode' to make it known. The brightness keys can be easily fixed, it only requires mapping these keys to a program which modifies the brightness (via writing to /proc/acpi/video/ATIM/LCD/brightness or whatver your display is), but the other features are not modifiable via /proc as far as I know. -- backlight brighness control does not work (Samsung Q45 with Nvidia GForce 8400M) https://bugs.launchpad.net/bugs/146710 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278230] Re: Python 2.6 for Intrepid
I don't see the problem with Ubuntu 8.10 shipping only Python 2.6. Migrating to a newer Python version is not that easy, take a look how long it took Debian or Gentoo to switch their default version to 2.5. For 2.6 Ubuntu 9.04 will be early enough, I'm sure there won't be a switch to Python 3.0 before Ubuntu 9.10. Maybe even later, but that depends less on Ubuntu but rather on the adaptation rate of the community. The faster they are 3.0 compatible, the earlier Ubuntu can use 3.0 as default. Still, 2.x will be around for quite some years. I tried building a python2.6 package from the python2.5 sources (updated via uupdate), but it fails quite early due to changes in the Makefile targets, due to the new documentation and the custom patches fail to apply. So it's a bit of work to get it to build properly. The only thing that is a bit of a pity is that the update-process was not started when the Python 2.6 alphas or betas came out (there was a Python 2.6 PPA of some alpha version by doko, but it was deleted). Then it would be easy to create PPAs immediately after the final release and/or upload them to Debian experimental (they are in freeze too). -- Python 2.6 for Intrepid https://bugs.launchpad.net/bugs/278230 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146710] Re: backlight brighness control does not work (Samsung Q45 with Nvidia GForce 8400M)
I've been experiencing this problem on my R60 Aura T5250 Deeloy ever since I updated from BIOS 01YI (WLAN, Backlight and Brightness not working anymore). These keys work when one is in the BIOS setup and only get disabled when the system is booting in ACPI mode. On Windows, Samsung has a tool called Easy Display Manager (on the Samsung CD and also available online) which takes over the control of these settings. So this stuff does not work on Windows either, because Samsung has disabled that recently and supplies this tool only for Windows (speaking with the tech support does help to understand the problem). So, in case these keys work for you in the BIOS and work with this Easy Display Manager, you have the exact same problem as I have. In case anyone has the original 01YI BIOS - please contact me, maybe there is a way to downgrade. -- backlight brighness control does not work (Samsung Q45 with Nvidia GForce 8400M) https://bugs.launchpad.net/bugs/146710 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
