Yeah, my system boots fine with 3.10.0-4 if I remove all of the i915
parameters in GRUB too. Those parameters used to be required to get a
working framebuffer on the MBP 8,2 but I guess they aren't anymore.
I'll update the description and title based on the new information.
** Description changed
Daily build is also fine:
jean-louis@laptop-jl:~$ uname -a
Linux laptop-jl 3.11.0-999-generic #201307210423 SMP Sun Jul 21 08:24:50 UTC
2013 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
Booted system.
Kernel -3:
jean-louis@laptop-jl:~$ sudo modprobe kvm_intel nested=1
jean-louis@laptop-jl:~$
=> Works fine, no errors.
Kernel -4:
jean-louis@laptop-jl:~$ sudo modprobe kvm_intel nested=1
ERROR: could not insert 'kvm_intel': Unknown symbol in module, or unknown
parameter (see dmes
Ok I did some additional debugging.
update-initramfs -u -k 3.10.0-3-generic:
3.10.0-3 still boots fine, so update-initramfs doesn't break it.
update-initramfs -u -k 3.10.0-4-generic:
Neither does it fix the problem on -4 kernel
boot arguments:
The defaults are:
linux /boot/vmlinuz-3.10.0-4-gen
update-initramfs I meant there, not upgrade..
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/1203211
Title:
Kernel 3.10.0-4 fails on graphical boot with i915
To manage notifications a
So its pretty clear i915 not loading is the problem from that, if you
sudo upgrade-initramfs -u -k 3.10.0-3-generic does it break the -3
kernel too? 3.11 allows invalid module parameters instead of preventing
the module from loading so whatever is broken here will be "fixed" soon
when saucy is upda
Yeah, I thought it was strange because I looked at the changelog for
3.10.0-4 and nothing logically corresponded with this. Since I'm getting
"modeset" is an invalid parameter and Jean-Louis is getting that
"i915_enable_rc6" is invalid, I'm guessing i915 is completely broken (or
modprobe, but I ass
There were absolutely no changes that would cause this in 3.10.0-4
compared to -3 (only 3 patches, one for hyperv, one to enable dynamic
debugging, and one adding a pci id for a realtek sd card reader..). Can
you attach /var/log/kern.log and /var/log/kern.log.1 that will have
historical dmesg info
I'm using Lightdm, so set gdm bug as invalid.
** Changed in: gdm (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/1203211
Title:
Kernel 3.10
@Jean-Louis Dupond, are you using GDM or are you using a different
display manager? If you're experiencing the same thing and not using
GDM/Ubuntu GNOME, I'll mark the bug as not affecting GDM.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscri
Same here with Optimus system:
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core
Processor Family Integrated Graphics Controller (rev 09)
01:00.0 VGA compatible controller: NVIDIA Corporation GF108M [GeForce GT 540M]
(rev a1)
3.10.0-4 is broken, 3.10.0-3 works fine.
The -
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdm (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/1203211
also problems with nvidia and new kernel 3.10.0-4 x64 on ubuntu saucy (unity).
with previous kernel 3.10.0-3 there were no errors.
really strage behaviour with keyboard, mouse. system is unusable. had to revert
to 3.10.0-3.
--
You received this bug notification because you are a member of Ubun
13 matches
Mail list logo
