[Bug 270912] Re: GX2 an EXA makes X to crash in Intrepid

2008-10-20 Thread Jordan Crouse
If it is crashing in DoMigration, then it is probably crashing in the
upload functions.  There is an off chance that it is crashing because we
are missing a newer hook that EXA needs.  It would really help if you
built in debugging and ran GDB on the X server to see where it gets off
track.

-- 
GX2 an EXA makes X to crash in Intrepid
https://bugs.launchpad.net/bugs/270912
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 234898] Re: unable to change screen resolution....

2008-06-09 Thread Jordan Crouse
Wait, are you talking about the splash screen, or X itself?  You talk
about it not finding the -geode driver, yet you also talk about it
defaulting to 800x600, which seem to be conflicting problems.

If you are talking about the splash screen running at 800x600, then
this is a known problem.  Blacklist the lxfb module.

-- 
unable to change screen resolution
https://bugs.launchpad.net/bugs/234898
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 140051] Re: xf86-video-amd: fails to autoconfigure

2008-06-02 Thread Jordan Crouse
I presume this is a TFT panel?  If so, then this the different bug that
Bart already fixed. Fading to white means that the the vsync and hsync
were removed from the panel,  but since you hit the vm86 bug, the VGA
isn't getting control.

-- 
xf86-video-amd: fails to autoconfigure
https://bugs.launchpad.net/bugs/140051
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 214119] Re: [HARDY] Koolu W.E. (ION A603) does not detect higher resolution than 800x600

2008-04-22 Thread Jordan Crouse
I would rather not make this part of a 2.8.1 release, and I would like
to stick to our existing roadmap of a 2.9.0 release on June 15.   That
will give us time to do the other work that we had planned. I have not
been convinced that we are in a hurry here to make any distribution
based deadlines, which is really the only reason why we make releases in
the first place.

-- 
[HARDY] Koolu W.E. (ION A603) does not detect higher resolution than 800x600
https://bugs.launchpad.net/bugs/214119
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 214119] Re: [HARDY] Koolu W.E. (ION A603) does not detect higher resolution than 800x600

2008-04-17 Thread Jordan Crouse
1) Attach your X log and we can be sure that you are using the resolution that 
the monitor reported.  This is one of many problems with DDC/EDID.  People 
don't realize that there isn't a connection between what the display controller 
can do, what the monitor can do, and what the monitor reports that it can do.  
When you chose to use DDC, then you are blindly restricted to what the monitor 
tells you to use.   You *can* use other resolutions, but that will involve 
hacking an xorg.conf file.
2) Xorg -configure works from the GIT tree, so the driver and the X server 
agree on probing the PCI ID at least.  I'm not sure how the detection and 
installation works in Ubuntu, so somebody more knowledgeable then myself will 
need to evaluate that.
3) That is kernel based breakage - it has nothing to do with the X driver
4) Ditto.

Unfortunately, this patch _is_ our simple workaround - all other
workarounds are far more complex.   But I do agree this patch needs more
far more testing - it is still some time away from being added to the
GIT repository, let alone making it into any distros.

-- 
[HARDY] Koolu W.E. (ION A603) does not detect higher resolution than 800x600
https://bugs.launchpad.net/bugs/214119
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 214119] Re: [HARDY] Koolu W.E. (ION A603) does not detect higher resolution than 800x600

2008-04-16 Thread Jordan Crouse
We are not at all ready for this patch to go into production systems.
Please remove your test packages immediately - I'm afraid we have
officially lost the race to get into Hardy.

-- 
[HARDY] Koolu W.E. (ION A603) does not detect higher resolution than 800x600
https://bugs.launchpad.net/bugs/214119
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 140051] Re: Ubuntu bug report for AMD driver

2007-11-11 Thread Jordan Crouse
On 11/11/07 13:36 +0200, Martin-Éric Racine wrote:
 On 11/5/07, Jordan Crouse [EMAIL PROTECTED] wrote:
  On 17/09/07 14:43 +0300, Martin-Éric Racine wrote:
   Greetings everyone,
  
   Can anyone reproduce the following bug?
  
   https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amd/+bug/140051
 
  Patch is attached - just a trivial re-arranging of the first few
  commands in PreInit.
 
  [LX] Re-arrange PreInit to avoid segfaults in Xorg -configure
 
  Re-arrange the early part of PreInit so that Xorg -configure can run
  cleanly.
 
 I patched and repacked:
 http://q-funk.iki.fi/debian/pool/x/xserver-xorg-video-amd/
 
 I tested this with a ThinCan (http://www.thincan.com) running on a
 Geode LX and while -configure doesn't crash, detection of the best
 available resolution and color depth still fails. We end up in what
 appears to be 640x480 @ 4 bit.

That would be really unfortunate, because we don't support 4 bit in the
AMD driver.  Logs would be useful here.

Jordan

-- 
amd driver fails to autoconfigure
https://bugs.launchpad.net/bugs/140051
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs