| 2007-04-20 23:37:28 |
Evan Huus |
bug |
|
|
added bug |
| 2007-04-21 03:11:49 |
Brian Murray |
None: statusexplanation |
|
|
|
| 2007-04-21 08:28:58 |
Dan O'Huiginn |
xorg: status |
Unconfirmed |
Needs Info |
|
| 2007-04-21 08:28:58 |
Dan O'Huiginn |
xorg: assignee |
|
daniel-ohuiginn |
|
| 2007-04-21 08:28:58 |
Dan O'Huiginn |
xorg: statusexplanation |
|
Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description didn't include enough information.
Please include the information requested from [WWW] https://help.ubuntu.com/community/DebuggingXAutoconfiguration as separate attachments. |
|
| 2007-04-21 16:10:18 |
Evan Huus |
bug |
|
|
added attachment 'Output of "lspci -n"' (Output of "lspci -n") |
| 2007-04-21 16:11:51 |
Evan Huus |
bug |
|
|
added attachment 'Output of "sudo discover --disable..."' (Output of "sudo discover --disable...") |
| 2007-04-21 16:14:28 |
Evan Huus |
bug |
|
|
added attachment 'Output of "sudo xresprobe <driver>"' (Output of "sudo xresprobe <driver>") |
| 2007-04-21 18:25:58 |
Evan Huus |
bug |
|
|
added attachment 'xorg.conf unedited' (xorg.conf unedited) |
| 2007-04-21 18:27:13 |
Evan Huus |
bug |
|
|
added attachment 'xorg.conf edited' (xorg.conf edited) |
| 2007-04-21 20:00:06 |
Dan O'Huiginn |
xorg: status |
Needs Info |
Confirmed |
|
| 2007-04-21 20:00:06 |
Dan O'Huiginn |
xorg: assignee |
daniel-ohuiginn |
|
|
| 2007-04-21 20:00:06 |
Dan O'Huiginn |
xorg: statusexplanation |
Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description didn't include enough information.
Please include the information requested from [WWW] https://help.ubuntu.com/community/DebuggingXAutoconfiguration as separate attachments. |
Thanks for providing that information. |
|
| 2007-05-24 18:58:30 |
Bryce Harrington |
xorg: status |
Confirmed |
Needs Info |
|
| 2007-05-24 18:58:30 |
Bryce Harrington |
xorg: importance |
Undecided |
Medium |
|
| 2007-05-24 18:58:30 |
Bryce Harrington |
xorg: statusexplanation |
Thanks for providing that information. |
Thanks for reporting this bug.
It sounds like there are at least two issues here. First, that in safe graphics mode it is not detecting your radeon card; safe graphics mode ought to *always* work. Second, that it is not detecting your monitor.
The second issue is already known (bug 3731), so I'm going to focus this bug report on the first issue.
However, it sounds like you've worked around the first issue. For the second issue, the workaround is to add the HorizSync and VertRefresh rates for your monitor. Currently it is using generic values which probably aren't appropriate for your monitor. Usually you can find this info from your monitor's manual, or by looking on the monitor manufacturer's website in their support channels. If you do find this info, can you please report it back here so we can add it to our database so it works in future versions of ubuntu?
|
|
| 2007-06-02 01:39:32 |
Bryce Harrington |
xorg: status |
Needs Info |
Unconfirmed |
|
| 2007-06-02 01:39:32 |
Bryce Harrington |
xorg: statusexplanation |
Thanks for reporting this bug.
It sounds like there are at least two issues here. First, that in safe graphics mode it is not detecting your radeon card; safe graphics mode ought to *always* work. Second, that it is not detecting your monitor.
The second issue is already known (bug 3731), so I'm going to focus this bug report on the first issue.
However, it sounds like you've worked around the first issue. For the second issue, the workaround is to add the HorizSync and VertRefresh rates for your monitor. Currently it is using generic values which probably aren't appropriate for your monitor. Usually you can find this info from your monitor's manual, or by looking on the monitor manufacturer's website in their support channels. If you do find this info, can you please report it back here so we can add it to our database so it works in future versions of ubuntu?
|
|
|
| 2007-06-15 02:35:44 |
Bryce Harrington |
xorg: status |
Unconfirmed |
Needs Info |
|
| 2007-06-15 02:35:44 |
Bryce Harrington |
xorg: importance |
Medium |
Low |
|
| 2007-06-15 02:35:44 |
Bryce Harrington |
xorg: statusexplanation |
|
Too bad about the Proview, but let me see if I understand the remaining issues properly:
a. When booting the LiveCD, it detects your onboard video card and configures xorg.conf to use it instead of the added radeon card. (This sounds sort of like Bug #75316, except the opposite, or like bug 103223)
b. It is picking "vesa" for your onboard intel video card instead of "i810" or "intel" as it should
c. After manually fixing it to use the Radeon with the open source 'radeon' driver, it works correctly, except that there is a garbage screen that appears after the boot screen but before the login screen.
Bug c. may actually be in the splash screen rather than in xorg. Can you verify this by modifying your /boot/grub/menu.lst and removing the 'splash' option? If this makes the problem go away, then that bug is in usplash. |
|
| 2007-06-15 17:25:11 |
Bryce Harrington |
xorg: status |
Needs Info |
Confirmed |
|
| 2007-06-15 17:25:11 |
Bryce Harrington |
xorg: statusexplanation |
Too bad about the Proview, but let me see if I understand the remaining issues properly:
a. When booting the LiveCD, it detects your onboard video card and configures xorg.conf to use it instead of the added radeon card. (This sounds sort of like Bug #75316, except the opposite, or like bug 103223)
b. It is picking "vesa" for your onboard intel video card instead of "i810" or "intel" as it should
c. After manually fixing it to use the Radeon with the open source 'radeon' driver, it works correctly, except that there is a garbage screen that appears after the boot screen but before the login screen.
Bug c. may actually be in the splash screen rather than in xorg. Can you verify this by modifying your /boot/grub/menu.lst and removing the 'splash' option? If this makes the problem go away, then that bug is in usplash. |
|
|
| 2007-12-06 19:50:58 |
Timo Aaltonen |
marked as duplicate |
|
103223 |
|
