when I change my graphics card X no longer works

Bug #110088 reported by Michal Suchanek
2
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: xorg

When I replace my graphics card with one that has chipset from a different manufacturer X no longer works.

Of course, it works if I reconfigure it with X -configure or dpkg-reconfigure xserver-xorg. I usually get suboptimal results this way (low resolution and/or refresh rate) but it works to some extent.

But why should I ever run such script manually? It is obvious that the card is different.

Revision history for this message
Bryce Harrington (bryce) wrote :

The current X configuration system runs only at install time, so if you swap hardware after installation, problems like this can occur.

You did the right thing to run X -configure or dpkg-reconfigure. However, sometimes your monitor doesn't get detected (see bug 3731), which results in the suboptimal resolution and refresh rates. As a workaround, if you edit your /etc/X11/xorg.conf file you can fix the refresh rates for your monitor.

Longer term our hope is to make use of Xorg's built-in hardware detection, making all this reconfiguration work unnecessary. See bug 3731 for details.

Revision history for this message
Michal Suchanek (hramrach) wrote :

That's not going to be flawless either. X hardware detection is also very buggy.
However, I think it is step in the right direction. Instead of maintaining a different hardware detection with different bugs Ubuntu users will collect data about the cases where X detection fails.

Revision history for this message
Bryce Harrington (bryce) wrote : Re: [Bug 110088] Re: when I change my graphics card X no longer works

On Thu, Apr 26, 2007 at 07:29:06AM -0000, Michal Suchanek wrote:
> *** This bug is a duplicate of bug 3731 ***
> https://bugs.launchpad.net/bugs/3731
>
> That's not going to be flawless either. X hardware detection is also very buggy.
> However, I think it is step in the right direction. Instead of maintaining a different hardware detection with different bugs Ubuntu users will collect data about the cases where X detection fails.
>

Certainly, it won't be perfect. But the advantage of using something
common with upstream is we can rely on the larger community to help with
addressing those bugs, and won't have to fix them independently.

I also plan to continue maintaining the current system and hopefully
fixing up whatever bugs can easily be repaired, so that it will be
available if the upstream detection system fails in some circumstances
and a fallback is required. I think you mentioned in one of the other
bugs that there are cases where xresprobe works but xorg's detection
doesn't.

Bryce

Revision history for this message
Michal Suchanek (hramrach) wrote :

On 30/04/07, Bryce Harrington <email address hidden> wrote:
> *** This bug is a duplicate of bug 3731 ***
> https://bugs.launchpad.net/bugs/3731
>
> On Thu, Apr 26, 2007 at 07:29:06AM -0000, Michal Suchanek wrote:
> > *** This bug is a duplicate of bug 3731 ***
> > https://bugs.launchpad.net/bugs/3731
> >
> > That's not going to be flawless either. X hardware detection is also very buggy.
> > However, I think it is step in the right direction. Instead of maintaining a different hardware detection with different bugs Ubuntu users will collect data about the cases where X detection fails.
> >
>
> Certainly, it won't be perfect. But the advantage of using something
> common with upstream is we can rely on the larger community to help with
> addressing those bugs, and won't have to fix them independently.
>
> I also plan to continue maintaining the current system and hopefully
> fixing up whatever bugs can easily be repaired, so that it will be
> available if the upstream detection system fails in some circumstances
> and a fallback is required. I think you mentioned in one of the other
> bugs that there are cases where xresprobe works but xorg's detection
> doesn't.
>
> Bryce

At the very least, the gdm "your X failed to start" script could run
the reconfiguration. But that would require a text mode equivalent of
gksu to be consistent.

Thanks

Michal

Revision history for this message
Michal Suchanek (hramrach) wrote :

The debconf script for xserver-xorg is not very good for reconfiguration after hardware change. It won't detect the card driver, and it always asks useless questions about keyboard and modules.

Revision history for this message
Bhavani Shankar (bhavi) wrote :

Yes it happened to me also when I changed my primary video card from
IGMA to nvidia

On 5/4/07, Michal Suchanek <email address hidden> wrote:
> *** This bug is a duplicate of bug 3731 ***
> https://bugs.launchpad.net/bugs/3731
>
> The debconf script for xserver-xorg is not very good for reconfiguration
> after hardware change. It won't detect the card driver, and it always
> asks useless questions about keyboard and modules.
>
> --
> when I change my graphics card X no longer works
> https://bugs.launchpad.net/bugs/110088
> You received this bug notification because you are a member of Kubuntu
> Team, which is a subscriber of a duplicate bug (via bug 3731).
>
> --
> kubuntu-bugs mailing list
> <email address hidden>
> https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
>

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.