[Ubuntu-x-swat] [Bug 560570] Re: fglrx fails to identify attached monitor, displays blank screen

2010-08-18 Thread Manuel Sanchez
I'm delighted to report that my instance of this bug was fixed by the latest released of the Catalyst drivers (10.7). I've tested this along with kernel 2.6.32-24 and Xserver 2:1.7.6-2ubuntu7.3 (all 32 bit). Compiz and GL in general work fine. Many thanks to the fglrx team for the fix Manuel --

[Ubuntu-x-swat] [Bug 560570] Re: fglrx fails to identify attached monitor, displays blank screen

2010-06-22 Thread Manuel Sanchez
Thanks for the hint Felix, as you suggested I downloaded the latest Catalyst, installed the generated packages (rel 8.741 in my case) and run aticonfig. Unfortunately it failed with the same behaviour as before. Is there any way to put the driver in any sort of 'verbose mode' so I can gather more

[Ubuntu-x-swat] [Bug 560570] Re: fglrx fails to identify attached monitor, displays blank screen

2010-06-22 Thread Manuel Sanchez
Indeed, I'm using a socket AM2 motherboard equipping the nForce 430 chipset (aka MCP51); to be more precise it is an Asus model A8MN-BR, marketed as Hematite-GL8E by HP. I presume Chris from post #13 has the same model. I'll check for other reports with this particular gpu/chipset combo to see

[Ubuntu-x-swat] [Bug 560570] Re: fglrx fails to identify attached monitor, displays blank screen

2010-06-22 Thread Manuel Sanchez
After some digging, I've found ticket filed for this same issue in ATI's bugzilla: http://ati.cchtml.com/show_bug.cgi?id=1794 what I gathered from other thread references in the ticket is that the issues with MCP51 follow a regression in Catalyst 9.9 ** Bug watch added: ATi Linux Platform Bugs

[Ubuntu-x-swat] [Bug 560570] Re: fglrx fails to identify attached monitor, displays blank screen

2010-06-17 Thread Manuel Sanchez
Just to report that the behaviour experienced after updating flgrx to the latest version (2:8.723.0ubuntu4) is identical (brief flash in Plymouth, then Xorg hangs with 100% CPU load on boot). The outputs for all logs all the same (nothing meaningful, AFAIU). I reiterate my offer to the developers

[Ubuntu-x-swat] [Bug 565870] Re: Xorg crashes with 855GM on boot: Failed to submit batchbuffer: Input/output error

2010-05-16 Thread Manuel Sanchez
whoops; in comment #7 please s/adverts/averts/g -- Xorg crashes with 855GM on boot: Failed to submit batchbuffer: Input/output error https://bugs.launchpad.net/bugs/565870 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in

[Ubuntu-x-swat] [Bug 569475] [NEW] [HD5450] Cannot load module fglrxdrm after xorg-driver-fglrx 2:8.723.1-0ubuntu3 update

2010-04-24 Thread Manuel Sanchez
Public bug reported: After updating xorg-driver-fglrx to 2:8.723.1-0ubuntu3, the machine previously exhibiting the behaviour described in bug #560570 (running 10.04 beta) now fails to load libfglrxdrm.so and reverts to vesa. I presume this is an update error unrelated to the problem defined in

[Ubuntu-x-swat] [Bug 569475] Re: [HD5450] Cannot load module fglrxdrm after xorg-driver-fglrx 2:8.723.1-0ubuntu3 update

2010-04-24 Thread Manuel Sanchez
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/45203332/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/4520/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/45203334/Dependencies.txt **

[Ubuntu-x-swat] [Bug 568716] Re: [i855GM] playing any video causes a hard crash

2010-04-23 Thread Manuel Sanchez
*** This bug is a duplicate of bug 558633 *** https://bugs.launchpad.net/bugs/558633 I believe this bug matches the description of bug #558633, as xv also fails in my case ** This bug has been marked a duplicate of bug 558633 Xorg hangs up when trying to play video using xv on i855 --

[Ubuntu-x-swat] [Bug 565870] Re: Xorg crashes with 855GM on boot: Failed to submit batchbuffer: Input/output error

2010-04-23 Thread Manuel Sanchez
I filed the video playing problem described above as #568716, which I also believe is a duplicate of bug #558633 -- Xorg crashes with 855GM on boot: Failed to submit batchbuffer: Input/output error https://bugs.launchpad.net/bugs/565870 You received this bug notification because you are a

[Ubuntu-x-swat] [Bug 568716] [NEW] [i855GM] playing any video causes a hard crash

2010-04-22 Thread Manuel Sanchez
Public bug reported: Binary package hint: xserver-xorg-video-intel Since installing 10.04 beta on a laptop equipped with a intel 855GM graphics card, I've been consistently experiencing the following: when trying to play video media in any format, using either Totem or vlc, X windows crashes and

[Ubuntu-x-swat] [Bug 568716] Re: [i855GM] playing any video causes a hard crash

2010-04-22 Thread Manuel Sanchez
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/45050445/BootDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/45050446/Dependencies.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/45050447/Lspci.txt ** Attachment added:

[Ubuntu-x-swat] [Bug 565870] Re: Xorg crashes with 855GM on boot: Failed to submit batchbuffer: Input/output error

2010-04-20 Thread Manuel Sanchez
Hi bryce, Sorry for the inconvenience of the tarball; I had to report this bug collecting this information by hand, rather than using the ubuntu tool. The interface only allows 1 file at a time, thus this seemed the most convenient way to file a bug with all the relevant information already

[Ubuntu-x-swat] [Bug 565870] Re: Xorg crashes with 855GM on boot: Failed to submit batchbuffer: Input/output error

2010-04-20 Thread Manuel Sanchez
** Attachment added: contents of the original tarball (syslog.1) http://launchpadlibrarian.net/44942006/syslog.1 -- Xorg crashes with 855GM on boot: Failed to submit batchbuffer: Input/output error https://bugs.launchpad.net/bugs/565870 You received this bug notification because you are a

[Ubuntu-x-swat] [Bug 565870] Re: Xorg crashes with 855GM on boot: Failed to submit batchbuffer: Input/output error

2010-04-20 Thread Manuel Sanchez
** Attachment added: contents of the original tarball (Xorg.1.conf) http://launchpadlibrarian.net/44942040/Xorg.1.log -- Xorg crashes with 855GM on boot: Failed to submit batchbuffer: Input/output error https://bugs.launchpad.net/bugs/565870 You received this bug notification because you

[Ubuntu-x-swat] [Bug 565870] Re: Xorg crashes with 855GM on boot: Failed to submit batchbuffer: Input/output error

2010-04-20 Thread Manuel Sanchez
With regards to enabling KMS, I was under the wrong impression that it was still enabled for the intel driver. Re-enabling it via i915.modeset=1 on the grub cmd line adverts the crash and X boots successfully. However DRI seems to have been deliberately disabled (see attached Xorg.conf), thus

[Ubuntu-x-swat] [Bug 511001] Re: [i855] Lucid Freeze shortly after X startup (needs KMS blacklist?)

2010-04-20 Thread Manuel Sanchez
Just to let you know that bug #565870 presents a case where disabling KMS actually causes X to crash on boot. -- [i855] Lucid Freeze shortly after X startup (needs KMS blacklist?) https://bugs.launchpad.net/bugs/511001 You received this bug notification because you are a member of Ubuntu-X,

[Ubuntu-x-swat] [Bug 565870] Re: Xorg crashes with 855GM on boot: Failed to submit batchbuffer: Input/output error

2010-04-19 Thread Manuel Sanchez
For further information, I've tried disabling KMS both with nomodeset and i915.modeset = 0 on the grub cmd line, both of which caused no change. -- Xorg crashes with 855GM on boot: Failed to submit batchbuffer: Input/output error https://bugs.launchpad.net/bugs/565870 You received this bug

[Ubuntu-x-swat] [Bug 560570] Re: fglrx fails to identify attached monitor, displays blank screen

2010-04-18 Thread Manuel Sanchez
Thanks Gary, I'm afraid my problem doesn't have to do with multiple monitors as I only have 1 attached. I will try to get hold of a second one to test whether this is due to the monitor not being supported, but from the way it hangs X I doubt so (otherwise it should bail out with no screens found

[Ubuntu-x-swat] [Bug 565870] [NEW] Xorg crashes with 855GM on boot: Failed to submit batchbuffer: Input/output error

2010-04-18 Thread Manuel Sanchez
Public bug reported: Binary package hint: xserver-xorg-video-intel After updating to xserver-xorg-video-intel to version 2:2.9.1-3ubuntu4 on a laptop running Lucid Lynx beta, and rebooting, it crashed after showing the boot splash screen. The machine was not reachable via ssh, so I rebooted it

[Ubuntu-x-swat] [Bug 565870] Re: Xorg crashes with 855GM on boot: Failed to submit batchbuffer: Input/output error

2010-04-18 Thread Manuel Sanchez
** Attachment added: Xorg log, syslog of the failed boot, along with lspci's out http://launchpadlibrarian.net/44679235/logs_and_lspci.tar.gz -- Xorg crashes with 855GM on boot: Failed to submit batchbuffer: Input/output error https://bugs.launchpad.net/bugs/565870 You received this bug

[Ubuntu-x-swat] [Bug 560570] Re: fglrx fails to identify attached monitor, displays blank screen

2010-04-14 Thread Manuel Sanchez
As by my previous post, I don't think this is a duplicate of Bug#552644, since the latest update didn't fix it. It may be related, though. ** Description changed: After installing fglrx 2:8.721.0ubuntu10 on Lucid Lynx beta 1 and running 'aticonfig --initial', X (1.7.5) only displays a blank

[Ubuntu-x-swat] [Bug 560570] Re: fglrx fails to identify attached monitor, displays blank screen

2010-04-13 Thread Manuel Sanchez
*** This bug is a duplicate of bug 552644 *** https://bugs.launchpad.net/bugs/552644 I'm afraid I wasn't as lucky as Nick and 2:8.723-0ubuntu1 didn't fix my problem. The only difference I could notice is that there is a slight flash of the screen when it hangs on the splash screen, while the

[Ubuntu-x-swat] [Bug 560570] Re: fglrx fails to identify attached monitor, displays blank screen

2010-04-12 Thread Manuel Sanchez
Hello Felix, I'm enclosing the correct version of the log files, along with the xorg.conf file generated by aticonfig. There is a slight change of behaviour since updating gdm; now rather than stalling on a blank screen, X now stalls on the ubuntu 10.04 splash (screen white lettering on top of

[Ubuntu-x-swat] [Bug 560570] [NEW] fglrx fails to identify attached monitor, displays blank screen

2010-04-11 Thread Manuel Sanchez
Public bug reported: After installing fglrx 2:8.721.0ubuntu10 on Lucid Lynx beta 1 and running 'aticonfig --initial', X (1.7.5) only displays a blank screen (system is running, can be ssh'ed in). This is the same effect experienced on a prior Karmic Koala installation with an older version of the

[Ubuntu-x-swat] [Bug 560570] Re: fglrx fails to identify attached monitor, displays blank screen

2010-04-11 Thread Manuel Sanchez
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/43764367/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/43764368/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/43764370/Dependencies.txt **