[Ubuntu-x-swat] [Bug 438000] Re: [i945gm] [karmic] X servers hangs when settings up dual monitor config

2009-11-04 Thread jpiesing
I've been doing some more testing on the Dell D420 referred to in #14. If I boot with the 2nd monitor connected, the system starts with the displayed mirrored. I can then use system / preferences / display to make the displays different. If I unplug the monitor, I can use system / preferences /

[Ubuntu-x-swat] [Bug 438000] Re: [i945gm] [karmic] X servers hangs when settings up dual monitor config

2009-11-03 Thread jpiesing
I'm seeing similar symptoms with a clean Karmic install on a Dell Latitude D420. Connect up a second screen, go to system/preferences/display and the display hangs with a black screen. The graphics controller is as follows; 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME,

[Ubuntu-x-swat] [Bug 347587] Re: [i4500MHD] Kubuntu: X asserts on pI830-batch_ptr != 0 on resume from suspend (UXA bug)

2009-07-01 Thread jpiesing
Is there any chance of a Jaunty version of this fix appearing in x-updates? -- [i4500MHD] Kubuntu: X asserts on pI830-batch_ptr != 0 on resume from suspend (UXA bug) https://bugs.launchpad.net/bugs/347587 You received this bug notification because you are a member of Ubuntu-X, which is the

[Ubuntu-x-swat] [Bug 384730] Re: [i945GM] screen goes black about once per day after upgrading to latest intel drivers

2009-06-12 Thread jpiesing
I've removed both UXA and virtual from Xorg.conf and I'm seeing if the problems re-occur. So far they haven't but I'll need to give it more time to be confident. Also https://bugs.launchpad.net/bugs/385830 hasn't re-occurred either (logout on resume from suspend). -- [i945GM] screen goes

[Ubuntu-x-swat] [Bug 384730] Re: [i945GM] screen goes black about once per day after upgrading to latest intel drivers

2009-06-11 Thread jpiesing
Ctrl+Alt+F1 does indeed add a drmDropMaster line each time I switch to a VT. ** Attachment added: Xorg.0.log showing switch to VT and return http://launchpadlibrarian.net/27769425/Xorg.0.log -- [i945GM] screen goes black about once per day after upgrading to latest intel drivers

[Ubuntu-x-swat] [Bug 384730] [NEW] screen goes black about once per day after upgrading to latest intel drivers

2009-06-08 Thread jpiesing
Public bug reported: Binary package hint: xserver-xorg-video-intel I was advised to upgrade to version 2.7.1 of the intel drivers from x-updates in order to get dual-screen to work (see https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/379805). Since then, about once per

[Ubuntu-x-swat] [Bug 384730] Re: screen goes black about once per day after upgrading to latest intel drivers

2009-06-08 Thread jpiesing
** Attachment added: The last 200 lines of syslog after the screen goes black before reboot http://launchpadlibrarian.net/27638201/syslog -- screen goes black about once per day after upgrading to latest intel drivers https://bugs.launchpad.net/bugs/384730 You received this bug notification

[Ubuntu-x-swat] [Bug 384730] Re: screen goes black about once per day after upgrading to latest intel drivers

2009-06-08 Thread jpiesing
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/27638166/Dependencies.txt ** Attachment added: LsHal.txt http://launchpadlibrarian.net/27638167/LsHal.txt ** Attachment added: LsMod.txt http://launchpadlibrarian.net/27638168/LsMod.txt ** Attachment added: LsPci.txt

[Ubuntu-x-swat] [Bug 379805] Re: [i945gm] virtual 2048 in xorg.conf causes blank white screen on login

2009-06-07 Thread jpiesing
Sorry for the delay in replying - work's been rather busy. Switching to UXA solves this problem. The white screen is gone! Dual screen behaves as expected. Unfortunately somewhere in the set of updates which got installed something else broke. About once per day, the entire screen just goes

[Ubuntu-x-swat] [Bug 379805] Re: [i945gm] virtual 2048 in xorg.conf causes blank white screen on login

2009-05-30 Thread jpiesing
Where should I find a suitable version of xorg-xserver-video-intel-dbg? As far as I can see, it's not in regular jaunty, jaunty-proposed or the x-swat PPA. The laptop is a Dell Latitude D420. -- [i945gm] virtual 2048 in xorg.conf causes blank white screen on login

[Ubuntu-x-swat] [Bug 379805] Re: [i945gm] virtual 2048 in xorg.conf causes blank white screen on login

2009-05-26 Thread jpiesing
** Attachment added: Xorg.0.log - not working http://launchpadlibrarian.net/27168442/Xorg.0.log.old -- [i945gm] virtual 2048 in xorg.conf causes blank white screen on login https://bugs.launchpad.net/bugs/379805 You received this bug notification because you are a member of Ubuntu-X, which

[Ubuntu-x-swat] [Bug 379805] Re: virtual keyword in xorg.conf causes blank white screen on login

2009-05-23 Thread jpiesing
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/27093431/Dependencies.txt ** Attachment added: LsHal.txt http://launchpadlibrarian.net/27093432/LsHal.txt ** Attachment added: LsMod.txt http://launchpadlibrarian.net/27093433/LsMod.txt ** Attachment added: LsPci.txt

[Ubuntu-x-swat] [Bug 320173] Re: [jaunty] Mouse and keyboard stop responding

2009-05-16 Thread jpiesing
I'm having the same problem having just installed Jaunty on a Dell Latitude D420. It's happened twice today having installed Jaunty last night. One of the questions asked if hal was running. Here's the output of ps aux | grep hal 105 2555 0.0 0.1 6684 2768 ?Ss 13:54 0:12

[Ubuntu-x-swat] [Bug 320173] Re: [jaunty] Mouse and keyboard stop responding

2009-05-16 Thread jpiesing
I've just re-started hal (/etc/init.d/hal restart) and the problem is still here. Attached is the output of lshal after this. ** Attachment added: Output of lshal when keyboard input is not working - after hal restart

[Ubuntu-x-swat] [Bug 320173] Re: [jaunty] Mouse and keyboard stop responding

2009-05-16 Thread jpiesing
** Attachment added: Output of lshal when keyboard input is not working http://launchpadlibrarian.net/26825488/lshal-keyboard-not-working -- [jaunty] Mouse and keyboard stop responding https://bugs.launchpad.net/bugs/320173 You received this bug notification because you are a member of