Created attachment 383490 [details] /var/log/message I've updated my Fed11 to Fed12 (new installation not upgrade) on my laptop Dell D410 (i915 chipset). I had no problem till i returned to work where i plugged my laptop on its docking station with external screen. Here is what happens. The computer boots normally till the login screen. After having entered my login/password, it starts to log in and freezes. The gnome menu never appears and the system seems to be freezed. I can still connect through ssh and launch any console commands but can't change init level. I've tried to connect with a brand new user but it's the same result. If i remove the laptop from the docking and reboot it, there is no problem. I didn't have that problem with fed 11. I join the message log.
I've just tried to connect an external display instead of using the docking station. I've the same result. If i log in without the external display connected, the laptop has no problem, but when i connect the display, it freezes
Here is what appears in /var/log/messages when i plug the external screen Jan 19 08:47:41 localhost kernel: [drm] TV-16: set mode NTSC 480i 0 Jan 19 08:47:41 localhost kernel: [drm] TV-16: set mode NTSC 480i 0 Jan 19 08:48:41 localhost ntpd[1513]: synchronized to 79.99.122.30, stratum 2 Jan 19 08:49:08 localhost kernel: [drm] TV-16: set mode NTSC 480i 0 Jan 19 08:49:08 localhost kernel: [drm] TV-16: set mode NTSC 480i 0 Jan 19 08:49:08 localhost kernel: [drm] DAC-6: set mode 20 These 3 last lines appears and the laptop screen freezes. I can still connect with ssh. I've added the Xorg.0.log file. Here is what's added to the file when the external display is connected. (II) intel(0): EDID for output LVDS1 (II) intel(0): Manufacturer: SEC Model: 3157 Serial#: 0 (II) intel(0): Year: 2005 Week: 0 (II) intel(0): EDID Version: 1.3 (II) intel(0): Digital Display Input (II) intel(0): Max Image Size [cm]: horiz.: 26 vert.: 16 (II) intel(0): Gamma: 2.20 ...
Created attachment 385329 [details] /var/log/Xorg.0.log
*** This bug has been marked as a duplicate of bug 540552 ***