installed feisty properly but gutsy failed on pc with asus m2a-vm with integrated ati radeon x1250

Bug #161215 reported by frettt on 2007-11-09
18
Affects Status Importance Assigned to Milestone
Ubuntu
Undecided
Unassigned

Bug Description

installed feisty 64-bit properly on pc wit asus m2a-vm with integrated ati radeon x1250 but i cant install gutsy on the same mainboard. curious!!! ugrade (online) from feisty to gutsy worked very properly. I think there is something wrong on the live cd (missing libraries?). I burned the cd three times on three different machines and i downloaded the image again to avoid a corrupt cd.

best regards
frettt

(ubuntu rocks)

Tormod Volden (tormodvolden) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Can you please give more details on what goes wrong? Verbatime error messages, or screenshot photos? Thanks in advance.

Ricardo L. Febrero (rlfebrero) wrote :

I also have a problem. I have a X1250 on a AMD690 Chipset based motherboard (Asus MA69G s3h) and, when I install Gutsy, there's no problem until I try to use fglrx driver. Then, it just freezes as soon as X.org starts. I have to manually uninstall the driver from safe-mode and reboot.
Maybe there's a problem with drivers, I think there's a new version with better quality from ATI/AMD. It doesn't give any error message, just freezes.
There's no way to make it work with 3D accel.
Thanks!!

duncang (duncan-rotherbridge) wrote :

This may be the same bug as I had and also bugs 154162, 147547, 175822.

Ubuntu 7.10, Gigabyte GA-MA69GM-S2H with ATI X1250. Could not perform graphical install, text install appears to hang after reboot. Fixed by installing latest ATI drivers (8.1 Jan 2008 ) and setting default screen resolution to 1024x768 in /etc/usplash.conf.

Tormod Volden (tormodvolden) wrote :

frett, is the problem after installing Restricted Drivers (fglrx)?

Tormod Volden (tormodvolden) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers