[Bug 140051] Re: amd driver fails to autoconfigure
On a Linutop with General Software BIOS (build date: 2007-01-18), DDC works like a charm and X auto-configuration succeeds too. Earlier BIOS releases for the Linutop had DDC support disabled and a serial console instead. My X.log is attached. ** Attachment added: "X.log on a Linutop with General Software BIOS patched with DDC support." http://launchpadlibrarian.net/11440146/Xorg.0.log -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
I am going to port the patches to Hardy's 1.4 debs. I have not started to build a development environment yet. Can someone in the know, tell me if it's easy to build 1.4 debs under Gutsy, or if I have to setup Hardy. -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
The new patched debs fix DDC issues on: GSW BIOS + GX2 GSW BIOS + LX I have also tested the debs on non-Geode hardware (intel chipset) and there are no ill effects of the xorg patch on that driver. Great fix!!! Hope to see it in gutsy and hardy soon! -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
Problems with console switching is a separate issue see https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- amd/+bug/180742 instead. -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
I installed it on Linutop board based with Geode LX 700, works well. But it's still broken with GDM when return to console ctrl alt F1, -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
I installed your packages and now my Lucida LT2610 thin client (LX Geode) works well. Both ddc and automatic X configuration are ok. -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
I have built Gutsy packages of both xserver-xorg-core and xserver-xorg- vidoe-amd and uploaded them in my PPA: https://launchpad.net/%7Eq-funk/+archive By installing both, GX/LX users should get a functioning driver with DDC and automatic X configuration. Can subscribers to this bug test this and report on their results? Thanks! -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
Actually, putting these into gutsy-proposed before Hardy is doing things in the wrong order; gutsy-proposed should only be used for patches known to fix issues, and where you are working towards getting them posted as an SRU. From the descriptions, these patches change the failure behavior but don't solve the issue, so I would expect the SRU reviewers to reject it. Generally, the order I prefer is to produce a one-off deb and/or ppa package, get a few people to validate it, then upload to Hardy for moderately wider testing. If after a few days in Hardy, it hasn't caused any mayhem, *then* it would be appropriate to put into gutsy- proposed, and work towards an SRU. I can take care of doing all of that packaging work. If you do wish to get this into gutsy as an SRU, please file two bug reports (one for each patch), with the following information: - Add to description a statement explaining impact of the bug to justify the backport - Explain how the bug has been addressed in the development branch - Point at the (small, unobtrusive) patch being proposed - Add to description detailed steps for reproducing the issue - Discuss regression potential and how users could be affected (The above is from the SRU process at wiki.ubuntu.com). -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
With reference to: >> I meant confirmation of whether these two x86emu patches fix the bug or not. My two patches do not solve the "DDC not working" bug. They fix two bugs in x86emu that cause the freeze. I plan on working on the DDC/EDID issues later this week. -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
I meant confirmation of whether these two x86emu patches fix the bug or not. -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
I confirm this bug. -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
There's actually 2 patches against x86emu found in X server >= 1.3 that need to be tested: http://www.jukie.net/~bart/patches/xorg-server/20080111/0001-X86EMU- added-blacklist-for-I-O-port-in-0-0xFF-range.patch and http://www.jukie.net/~bart/patches/xorg-server/20080111/0001-X86EMU- pass-the-correct-bus-dev-fn-tag-to-pci-emula.patch Ideally, these should be released to Gutsy as an update, to allow people to test and report on their success before Hardy is released, so that Ubuntu X maintainers have enough time to patch the server in Hardy too. We need confirmation from as many of the users subscribed to this bug, before we can proceed with the release. -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
More about the Geode LX crash with Generla Software BIOS... There seems to be an inconsistency between what the x86emu gets from the PCI handling code and by accessing hardware directly. x86emu relies on a set of functions to emulate PCI access. When things goes wrong, the emulator is asked to execute an OUT instruction on port 0x20. I've put together a patch against xserver-xorg package that prevents accesses to BAD registers. This turns a freeze into a segfault in X. http://www.jukie.net/~bart/patches/xorg-server/20080111/0001-X86EMU- added-blacklist-for-I-O-port-in-0-0xFF-range.patch It does not address the DDC not working, I hope that after fixing the bugs in x86emu, things may improve. Anyway, I am continuing to investigate the real cause of the PCI access issue. To find out more read this thread: http://lists.freedesktop.org/archives/xorg/2008-January/031811.html -Bart -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
I have an ALIX1c lx800 motherboard from pcengines, after a long effort I successed to be able run Xorg 1.3 with the latest driver amd_drv.so. Now I have a really strange problem. Xorg works perfect, I can easily manage dpms modes and resolutions, but whenever I want to go back to console w/o X the display shows a message "out of range" and it doesnt fix until restartx or reboot. eventually this happens when I reboot or shutdown too, it is obvious that the driver fails the console after killing X. I have tried every single driver in the forum. no luck I appreciate any help or suggestion. best regards Joe BLACK -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
I have uploaded packages based upon upstream 2.7.7.4 that should fix this issue for most hardware configurations. A known exception is hardware booting off General Software BIOS, on which there are issues with X server 1.3 and newer, more specifically with the x86emu component of X server, that cause a complete hardware freeze. General Software has been notified through various channels. Gutsy packages (source and binary) can be found at: http://q-funk.iki.fi/debian/pool/x/xserver-xorg-video-amd/ Hardy packages are being synchronized from Debian and should be available soon. -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
xserver-xorg-video-amd (2.7.7.4-1gutsy1) gutsy; urgency=medium * Reverted 2.7.7.2-2 debian/control changes to produce Gutsy package. xserver-xorg-video-amd (2.7.7.4-1) unstable; urgency=low * New upstream release: [GX][LX] PreInit fixes to avoid segfaults on X -configure. This is known to work on products with GeodeROM and Insyde BIOSes. On products with a General Software BIOS, a freeze occurs while X is probing VBE. The same issue occurs with LinuxBIOS and VGAROM, but not with LinuxBIOS omitting VGAROM. Both issues appear to be caused by X server core upgrading from vm86 to x86emu since X server release 1.3, which requires fixing x86emu, or the concerned BIOSes, or both. xserver-xorg-video-amd (2.7.7.3-1) unstable; urgency=low * New upstream release. xserver-xorg-video-amd (2.7.7.2-2) unstable; urgency=low * Bumped Build-Depends to X server 1.4 core as follow: + xserver-xorg-dev (>= 1:1.1.1) to (>= 2:1.4). + x11proto-randr-dev (no version) to (>= 1.2). * Bumped binary target Provides correspondingly as follow: xserver-xorg-video-1.0 to xserver-xorg-video-2. * Above changes break compatibility with Debian/Etch and Ubuntu/Gutsy, but restore ABI/API compatibility with X.org 7.3 (Closes: #443285). xserver-xorg-video-amd (2.7.7.2-1) unstable; urgency=low * New upstream release. xserver-xorg-video-amd (2.7.7.0-1) unstable; urgency=low * New upstream release: This is the first official upstream release to come out of GIT. Many thanks go to AMD's Jordan Crouse and to other OLPC developers for making this release happen. -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
Great! I'm able to use Xorg at 1280x1024x16 without any trouble! :-) I just had to tune a few things manually, like: - HorizSync & VertRefresh to allow full screen size - DefaultDepth to get 16 bits depth - Modes in SubSection "Display" to get the size I wanted But we should be able to get most of this automagically. See what "ddcprobe" gives: vbe: VESA 2.0 detected. oem: Advanced Micro Devices memory: 16384kb mode: 640x480x256 mode: 800x600x256 mode: 1024x768x256 mode: 1280x1024x256 mode: 640x480x32k mode: 640x480x64k mode: 640x480x16m mode: 800x600x32k mode: 800x600x64k mode: 800x600x16m mode: 1024x768x32k mode: 1024x768x64k mode: 1024x768x16m mode: 1280x1024x32k mode: 1280x1024x64k mode: 1280x1024x16m mode: 1600x1200x32k mode: 1600x1200x64k edid: edidfail >From that we could guess horizontal & vertical data... -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
** Attachment added: "xwininfo" http://launchpadlibrarian.net/11120631/xwininfo-root_20080103_0026.txt -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
Oh... We can't attach more than one file at a time?? ** Attachment added: "Xorg.0.log" http://launchpadlibrarian.net/11120605/Xorg.0.log_20080103_0026.txt.bz2 -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
I've just discovered this bug report and reading it with interest. :-) I have a Linuterm, which is also based on the ThinCan DBE61. I'm trying to let it run LTSP on a Ubuntu "Gutsy" basis. Bartman, I've just downloaded and installed your packages. The Xorg server is able to start without crash or hang, in 800x600x8. I've attached my xorg.conf, Xorg.0.log and xwininfo. Let me know if you need any other information. I'll try to use this from know and see how far it's usable. Thanks for the research and packaging! ** Attachment added: "xorg.conf" http://launchpadlibrarian.net/11120601/xorg.conf_20080103_0026.txt -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
Looking at the PDF that Guilherme attached to the bug, it appears that that Brazilian thin client boots off a General Software BIOS. -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
Guilherme Straioto: you reported that the driver fails on a Brazilian- made thin client. Could you tell us which brand and version of BIOS is used to boot it? Thanks! -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
The discussion started here continued on the xorg mailing list. Here is the thread... http://lists.x.org/archives/xorg-driver-geode/2007-December/02.html I have been debugging the problem on and off and made some headway recently... http://lists.x.org/archives/xorg-driver-geode/2007-December/74.html http://lists.x.org/archives/xorg-driver-geode/2007-December/75.html In the last message I give links to a proposed fix to the xorg- server-1.3.0.0 Gutsy package... http://www.jukie.net/~bart/patches/xorg-server/20071222/0001-X86EMU- blacklist-I-O-port-20-for-INT-10-emulation.patch I have rebuilt the packages and they are available here: http://www.jukie.net/~bart/debian/xorg/xserver-xorg-core_1.3.0.0.dfsg-12ubuntu8_i386.deb http://www.jukie.net/~bart/debian/xorg/xserver-xorg-video-amd_2.7.7.3-1_i386.deb The xorg-core includes my patch that just ignores reads/writes to IO port 0x20. The xorg-video-amd includes Jordan's patch rebased onto 2.7.7.3. If you have a change to try it, please let me know if it made any difference on your hardware. Note, however, that the xorg-core spits out a lot of port access messages... so it takes longer to start up. Also, it seems that DDC still does not work, but at least it does not freeze. -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
I don't know how Scotty got that. On my machine, this new deb causes the whole system to freeze after boot and become unresponsive Gutsy LTSP5 with xserver-xorg-viedo-amd-2.7.7.0-1ubuntu1 retrieved from MatrinEric's repo. -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
Scott reported a few days ago that auto-configuration no longer crashes (which suggests that Jordan's patch indeed does work), but that X fails to find the largest available resolution (which suggests a broken DDC support in X or in this driver.). -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
I installed the new driver but still not worked in my thin client, I am almost giving up, my thin client also runs AMD geode, http://www.brazilmkt.com.br/iclient/ Use Ubuntu Gusty upgraded from Feisty, LTSP 5. -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
Test packages (Gutsy chroot in pbuilder) are available at http://q-funk.iki.fi/debian/pool/x/xserver-xorg-video-amd/ The debdiff is attached. ** Attachment added: "debdiff_xserver-xorg-video-amd_2.7.7.0-1_2.7.7.0-1ubuntu1" http://launchpadlibrarian.net/10299432/debdiff_xserver-xorg-video-amd_2.7.7.0-1_2.7.7.0-1ubuntu1.diff -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
We essentially need to test for two things with this patch: 1) does it solve the crash everyone experiences? 2) does it help X auto-configure itself to the maximum resolution offered by the display? -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
As a test, I built a driver against the OLPC tree. It freezes the whole system dead, as soon as X launches, presumably because it includes support for the OLPC DCON. -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
In response to Bernardo's comment, here is the diff between git://anongit.freedesktop.org/git/xorg/driver/xf86-video-amd.git and git://dev.laptop.org/xf86-amd-devel ** Attachment added: "differences between OLPC and FreeDesktop trees for this AMD X.org driver" http://launchpadlibrarian.net/10253518/xf86-amd.diff -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
Bernardo Innocenti recalls having fixed this particular issue in the OLPC fork. He suggests cherry-picking useful changes from: http://dev.laptop.org/git?p=olpc-2.6 -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
Another comment from Anti Sullin: > So for a quick fix without any monitor detection, I just added > > if (flags & PROBE_DETECT) return TRUE; > > to the LXPreInit beginning (after variable declarations). > X comes up and we have a picture... although [EMAIL PROTECTED], 256colors > only. Btw, this hack just makes the probe work, but it breaks DDC. The exact PROBE_DETECT check comes a bit later, but the code in between crashes. I guess that the the existing PROBE_DETECT flag check with GeodeProbeDDC() call should be moved before vgahw module loading, but I haven't looked all dependencies how that could be implemented. Actually, a good point of start would be to see what other drivers are doing - a lot of the drivers are using the vga/vesa bios for DDC information - so the beginning of the PreInit could probably just be copied from some other driver (i.e. I see a lot of similarities with ati r128_driver.c). -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
I am with the same problem I am using Edubuntu Server 10 Ltsp 5, with a thin client called Brazilian iclient description attached, it uses the video driver amd but not start the way of no X. ** Attachment added: "thin_client.pdf" http://launchpadlibrarian.net/10161730/thin_client.pdf -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
** Changed in: xserver-xorg-video-amd (Ubuntu) Importance: Medium => High Status: Confirmed => Triaged -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
I can confirm this problem with Ubuntu 7.04 and 7.10 running on a Linutop PC equipped with an Geode LX processor. Is anyone working on a fix? -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
Anti Sullin of artecdesign.ee made the following comments : After a full day of debugging, the result is: we have a picture (although as we don't support DDC monitor detection, it's defaulted to [EMAIL PROTECTED] 256colors; didn't look where that comes from). Still, the system has some strange problems, things crash etc... But that may be a problem of my edubuntu server. X gets started twice. Once with -configure option, that autodetects video HW and monitors and writes config file. Second run is started with that config file. On the first run, all drivers are probed. Those, that existed, are preinit'ed to try to get monitor information (if not, then defaults are probably used). (screen configuration is not there as it does not exist yet). On second run, the AMD driver is loaded and preinit is called. But at that point, the screen information is already there and everything works. The bug is that the screen information is not passed to the PreInit function at probe run. (in AMD/geode LX case LXPreInit()). LXPreInit loads vgahw module (for manipulating something via vga i/o addreses... is this needed at all?) and then calls function vgaHWGetHWRec there. That accesses scrp->confScreen->options, but scrp->confScreen is a null pointer because we are on a probe run and we don't have any screens yet... And BANG, segmentation fault. (Some more accesses of scrp->confScreen are in LXPreInit, too... so removing vgahw doesn't help). The gdb log about the crash, too. Program received signal SIGSEGV, Segmentation fault. 0xb7816f6f in vgaHWGetHWRec (scrp=0x8227610) at ../../../../hw/xfree86/vgahw/vgaHW.c:1721 1721../../../../hw/xfree86/vgahw/vgaHW.c: No such file or directory. in ../../../../hw/xfree86/vgahw/vgaHW.c (gdb) bt #0 0xb7816f6f in vgaHWGetHWRec (scrp=0x8227610) at ../../../../hw/xfree86/vgahw/vgaHW.c:1721 #1 0xb7cc8a35 in LXPreInit (pScrni=0x8227610, flags=1) at amd_lx_driver.c:488 #2 0x080bb72e in DoConfigure () at ../../../../hw/xfree86/common/xf86Configure.c:985 #3 0x080a8b05 in InitOutput (pScreenInfo=0x8202a80, argc=3, argv=0xbfac7dd4) at ../../../../hw/xfree86/common/xf86Init.c:388 #4 0x08076ceb in main (argc=3, argv=0xbfac7dd4, envp=0xbfac7de4) at ../../dix/main.c:370 Fix: - 1) as on ati driver, the driver does not have to initialize anything IF the PROBE_DETECT flag is present. We should detect monitor (but don't have to). After that, we need just to return TRUE; So for a quick fix without any monitor detection, I just added if (flags & PROBE_DETECT) return TRUE; to the LXPreInit beginning (after variable declarations). X comes up and we have a picture... although [EMAIL PROTECTED],256colors only. 2) maybe the vgahw should be removed as on ati : http://lists.freedesktop.org/archives/xorg/2004-December/004951.html ? Is it needed at all? -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
So from the strace, it looks like it's failing while trying to load
vgahw. Maybe it'd be worth adding `Disable "vgahw"` in the Modules
section?
Of course, I wonder why it is trying to load vgahw - shouldn't it be
attempting to load -amd? According to the strace, prior to the vgahw
stuff, it does find the chipset as GeodeLX:
write(0, "(II) AmdProbe: Probing for suppo"..., 46) = 46
write(0, "(II) AmdProbe: Before MatchPciIn"..., 41) = 41
write(0, "(--) Chipset GeodeLX found\n", 27) = 27
...
write(0, "(II) AmdProbe: MatchPCI (1)!\n", 29) = 29
write(0, "(II) AmdProbe: CPUDetected 32!\n", 31) = 31
write(0, "(II) resource ranges after xf86C"..., 59) = 59
write(0, "\t[0] -1\t0\t0x0010 - 0x0ff"..., 45) = 45
...
write(0, "(II) AMD(0): AmdProbe: result (1"..., 35) = 35
write(0, "(II) resource ranges after probi"..., 36) = 36
Then there's a bunch of hex stuff I don't grok, and it ends up deciding
to use vga:
write(0, "(II) Setting vga for screen 0.\n", 31) = 31
lseek(6, 4, SEEK_SET) = 4
write(6, "\7\0 \2", 4) = 4
write(0, "(II) Loading sub module \"vgahw\"\n", 32) = 32
write(0, "(II) LoadModule: \"vgahw\"", 24) = 24
Looks like it also attempted to load fbdevhw:
open("/usr/lib/xorg/modules/linux/",
O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 7
...
stat64("libfbdevhw.so", 0xbfc1c24c) = -1 ENOENT (No such file or directory)
Any of this mean anything to you guys?
--
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
[Bug 140051] Re: amd driver fails to autoconfigure
Hmm, here's what it's doing immediately prior to printing the backtrace:
write(0, "(II) Loading /usr/lib/xorg/modul"..., 48) = 48
open("/usr/lib/xorg/modules//libvgahw.so", O_RDONLY) = 7
read(7, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\320\21"..., 512) = 512
fstat64(7, {st_mode=S_IFREG|0644, st_size=27921, ...}) = 0
mmap2(NULL, 21848, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 7, 0) =
0xb780b000
mmap2(0xb781, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 7, 0x5) = 0xb781
close(7)= 0
write(0, "(II) Module vgahw: vendor=\"X.Org"..., 45) = 45
write(0, "\tcompiled for 1.3.0", 19)= 19
write(0, ", module version = 0.1.0\n", 25) = 25
write(0, "\tABI class: X.Org Video Driver, "..., 44) = 44
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
rt_sigaction(SIGSEGV, {SIG_IGN}, {0x80c9500, [SEGV], SA_RESTART}, 8) = 0
write(2, "\nBacktrace:\n", 12) = 12
write(0, "\nBacktrace:\n", 12) = 12
--
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
[Bug 140051] Re: amd driver fails to autoconfigure
strace ** Attachment added: "xorg.strace" http://launchpadlibrarian.net/9510926/xorg.strace -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
** Changed in: xserver-xorg-video-amd (Ubuntu) Assignee: Bryce Harrington (bryceharrington) => (unassigned) -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
Scott, How about trying an strace? strace Xorg -configure :1 > /tmp/xorg-strace 2>&1 ** Changed in: xserver-xorg-video-amd (Ubuntu) Importance: Undecided => Medium Status: New => Confirmed ** Changed in: xserver-xorg-video-amd (Ubuntu) Assignee: (unassigned) => Bryce Harrington -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
Tried, no difference, other than the two EE lines regarding the ztv driver disappear. I installed the xserver-xorg-driver-amd-dbg package in the chroot, hoping for something more than a hex address within the driver where it's failing, but no go. Am I missing something? Any way to get an indication as to where it's dying in the driver? Scott -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
Can you try deleting /usr/lib/xorg/modules/drivers/ztv_drv.so and see if helps auto-configuration succeed? -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
Output of Xorg -configure :1 > /tmp/xorg-output 2>&1 ** Attachment added: "xorg-output" http://launchpadlibrarian.net/9300306/xorg-output -- 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
[Bug 140051] Re: amd driver fails to autoconfigure
lspci ** Attachment added: "lspci-vv" http://launchpadlibrarian.net/9300310/lspci-vv -- 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
