[Bug 118225] Re: ATI FireGL V5200 not working at all

2007-11-03 Thread David Balažic
With the 7.10 desktop i386 CD, it works fine. It starts X with the vesa driver. ** Changed in: xorg (Ubuntu) Status: New = Fix Released -- ATI FireGL V5200 not working at all https://bugs.launchpad.net/bugs/118225 You received this bug notification because you are a member of Ubuntu

[Bug 118225] Re: ATI FireGL V5200 not working at all

2007-10-19 Thread zour1el
As with Fiesty Live CD, Gutsy Live has the same issue with FireGL 5250 cards. So far the only way i have been able to load all the way up is by the way Cristóbal described the only difference is I nano into xorg and manually edit -- ATI FireGL V5200 not working at all

[Bug 118225] Re: ATI FireGL V5200 not working at all

2007-10-19 Thread zour1el
As with Fiesty Live CD, Gutsy Live has the same issue with FireGL 5250 cards. So far the only way i have been able to load all the way up is by the way Cristóbal described the only difference is I nano into xorg and manually edit -- ATI FireGL V5200 not working at all

[Bug 118225] Re: ATI FireGL V5200 not working at all

2007-07-19 Thread Tormod Hope
My T60p is working fine. The installation of ubuntu goes fine. And it works out of the box. But the restricted drivers application want me to install a driver for my V5200. After i install the driver the fglrxinfo says that i have ATI Radeon x1300. br TommeN -- ATI FireGL V5200 not

[Bug 118225] Re: ATI FireGL V5200 not working at all

2007-06-27 Thread Cristóbal M . Palmer
Hi. I've got a lenovo ThinkPad T60p here with the FireGL V5250 and I have the same problem. My workaround was as follows: (1) boot liveCD, X fails as described. (2) at shell prompt, sudo -s (2a) apt-get update (2b) apt-get install xorg-driver-fglrx fglrx-control (2c) dpkg-reconfigure

[Bug 118225] Re: ATI FireGL V5200 not working at all

2007-06-17 Thread David Balažic
You mean #2, right ? ;-) It still says : E: Couldn't find package install displayconfig-gtk -- ATI FireGL V5200 not working at all https://bugs.launchpad.net/bugs/118225 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. --

[Bug 118225] Re: ATI FireGL V5200 not working at all

2007-06-15 Thread David Balažic
0.) I booted and got no error at all, just dropped to a shell on VT1 1.) sudo dpkg-reconfe xserver-xorg : autodetect does not find anything so I choose vesa. It works fine in 640x480 mode. I tried higher resoutions by editing xorg.conf, but the crash. 2.) sudo apt-get install displayconfig-gtk :

[Bug 118225] Re: ATI FireGL V5200 not working at all

2007-06-15 Thread Bryce Harrington
Hmm, for #3, try this: sudo apt-get update sudo apt-get install displayconfig-gtk sudo displayconfig-gtk ** Changed in: xorg (Ubuntu) Status: Needs Info = Unconfirmed -- ATI FireGL V5200 not working at all https://bugs.launchpad.net/bugs/118225 You received this bug

[Bug 118225] Re: ATI FireGL V5200 not working at all

2007-06-14 Thread Bryce Harrington
Here are a few different things to try: 1. Run sudo dpkg-reconfe xserver-xorg, and choose only the 640x480 mode (or the 800x600 mode) 2. Install and run displayconfig-gtk sudo apt-get install displayconfig-gtk sudo displayconfig-gtk Use this tool to select the correct graphics

[Bug 118225] Re: ATI FireGL V5200 not working at all

2007-06-05 Thread Bryce Harrington
** Changed in: xorg (Ubuntu) Status: Needs Info = Unconfirmed -- ATI FireGL V5200 not working at all https://bugs.launchpad.net/bugs/118225 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list

[Bug 118225] Re: ATI FireGL V5200 not working at all

2007-06-02 Thread David Balažic
If I manually add VertRefresh and HorizSync then: - it ends (no crash) with can not find screen(s) (or similar, I don't remember exactly) If I widen the frequency range (so I guess now it finds a resolution), then it crashes like described above. If I remove xorg.conf , it crashes just the

[Bug 118225] Re: ATI FireGL V5200 not working at all

2007-06-01 Thread David Balažic
** Attachment added: Xorg.0.log http://launchpadlibrarian.net/7910941/Xorg.0.log -- ATI FireGL V5200 not working at all https://bugs.launchpad.net/bugs/118225 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs

[Bug 118225] Re: ATI FireGL V5200 not working at all

2007-06-01 Thread David Balažic
** Attachment added: xorg.conf http://launchpadlibrarian.net/7910940/xorg.conf -- ATI FireGL V5200 not working at all https://bugs.launchpad.net/bugs/118225 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs

[Bug 118225] Re: ATI FireGL V5200 not working at all

2007-06-01 Thread Bryce Harrington
*** This bug is a duplicate of bug 3731 *** https://bugs.launchpad.net/bugs/3731 Thanks for reporting this problem. Sounds like another example of the installer failing to detect hardware, as it's trying to use Generic for both your video card and monitor. However, judging from the log files

[Bug 118225] Re: ATI FireGL V5200 not working at all

2007-06-01 Thread Bryce Harrington
*** This bug is a duplicate of bug 3731 *** https://bugs.launchpad.net/bugs/3731 ** This bug has been marked a duplicate of bug 3731 Xorg resolution falling back to 640x480 and/or 800x600 when h/v freqs incorrect -- ATI FireGL V5200 not working at all

[Bug 118225] Re: ATI FireGL V5200 not working at all

2007-06-01 Thread David Balažic
*** This bug is a duplicate of bug 3731 *** https://bugs.launchpad.net/bugs/3731 Are you sure ? Bug 3731 is about bad detection of monitor, mine is about a crash. I don't get a wrong resolution. I don't get anything. Manually adding VertRefresh and HorizSync doesn't help. -- ATI FireGL

[Bug 118225] Re: ATI FireGL V5200 not working at all

2007-06-01 Thread Bryce Harrington
It looks like the same root cause. The misdetection in 3731 _usually_ just reduces the number of available resolutions to one or two for most people, but it is possible in some rare cases (such as yours) for it to reduce the number to zero. I believe that the crash is due to it finding no