On 04/08/10 00:42, Manoj Iyer wrote: > Can someone please test kernel in > http://kernel.ubuntu.com/~manjo/lucid/lp561802/ > > This kernel has a backport of patch from upstream SHAID > fe27d53e5c597ee5ba5d72a29d517091f244e974 that was reported to fix this > issue(561802). What is confusing is that the kernel in > http://kernel.ubuntu.com/~manjo/lucid/lp578673/ does not contain this > path yet it was reported in comment #53 that this kernel fixed the > issue(561802) reported in this bug. I would like to clear this > confusion. If this SHAID indeed fixes this issue, I need to send this > patch to sta...@kernel and then SRU for Lucid. I really appreciate your > help. > > Manoj,
I've just given it another shot this morning using the above kernel and my system still locked up after connecting the vga port and running xrandr. As far as I can tell I've installed the kernel correctly. The md5sums from the files in the deb package match the ones from the files that get installed to /boot/ - and I've set that kernel as the default choice in the grub menu. Bit of a n00b question I know, but how can I be sure that I *am* actually running the above kernel? Uname output is: <bla> 2.6.32-24-386 #38 SMP Thu Jul 8 21:22:46 UTC 2010 i686 GNU/Linux I just want to make sure that I'm not giving you a false negative. :-) Alex -- [lucid] [i915] blank screen on Latitude E6410 https://bugs.launchpad.net/bugs/561802 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
