Re: [XFree86] dual adapters, ISA and integrated
On Sun, 4 Jan 2004, David Koski wrote: I have an old PowerMate V75 with an intergrated video that is too incapable for XF86 so I added an old Mach32 ISA card. I was able to get it to not conflict by setting the integrated video to monochrome. But I was not able to disable it completely. Now when I try to configure XF86Config (Debian, current, just installed) using the debian configuration program it asks for a PCI ID number. But I want to configure for the ISA card (Mach32). I am at loss how to do it manually. Assuming that the system's BIOS chose the Mach32 as the primary adapter, you should be able to generate a workable XF86Config using `XFree86 -configure`. However, the Mach32 will be treated as a VGA Wonder. I.e., in 4.*, there is no support for Mach32 acceleration like there was in XFree86 3.*. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] dual adapters, ISA and integrated
On Mon, 5 Jan 2004, David Koski wrote: I have an old PowerMate V75 with an intergrated video that is too incapable for XF86 so I added an old Mach32 ISA card. I was able to get it to not conflict by setting the integrated video to monochrome. But I was not able to disable it completely. Now when I try to configure XF86Config (Debian, current, just installed) using the debian configuration program it asks for a PCI ID number. But I want to configure for the ISA card (Mach32). I am at loss how to do it manually. Assuming that the system's BIOS chose the Mach32 as the primary adapter, you should be able to generate a workable XF86Config using `XFree86 -configure`. However, the Mach32 will be treated as a VGA Wonder. I.e., in 4.*, there is no support for Mach32 acceleration like there was in XFree86 3.*. The primary adapter seems to be the built in one. I set it to monochrome mode because I couldn't disable it and in VGA mode it only has 1 Meg of memory. The secondary one is the Mach32 in a ISA slot. (Actually I tried a Rendition V1000-E with similar results). The problem seems to be when xf86cfg and xf86config configure for the primary. But I solved the problem by installing LTSP (www.ltsp.org) software. It is faster anyway as the hard disk is slow. Now the computer is just an X terminal (hard disk disconnected). I would still suggest `XFree86 -configure`. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Cannot startx with root but okay with normal user
On Tue, 6 Jan 2004, Choo BK wrote: I have just changed to ATI Rage Mobility VGA card and when booting up, the hardware configuration wizard correctly detected the card as ATI Rage Mobility. However, when I startx using the root login, it shows no devices detected error. I use normal user to login and I do not face any problems. Attached is the XFree86 log file, pls advise. Thank you. That's because you ended up configuring it with the wrong driver. Change your XF86Config to specify Driver ati, instead of Driver sis. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Mach64 GX configuration help !
On Sat, 24 Jan 2004, Vinay Tandon wrote: I'm using ATI Technologies Inc 210888GX [Mach64 GX] card. The ati driver gives the following error: Driver does not support depth 32 at fbbpp 32 Please let me know whether the support for this has been included in the ati driver. has been == no, will be == yes at some point in the future. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] (no subject)
On Tue, 27 Jan 2004, Marc Goodboy wrote: I recently installed Gentoo Linux on a Compaq Proliant 1850R. I then installed XFree86 version 4.3.0. When I start X then monitor flickers, goes blank then Xserver locks up and does not allow me to exit without turning off the computer. I am using a cordless logitech keyboard with the receiver hooked to a 4 port Linksys KVM switch. The monitor is a Samsung SyncMaster 151v LCD. The video hardware in the proliant is ATI Rage IIc(integrated) with 1024 Mb of Ram. I have worked with Xserver before and have not had any problem, but this is my first install on a Proliant. Any suggestions? If the SyncMaster supports DDC (which should show up in the log), you can derive proper timings it. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] XFree86 on Solaris 9/SPARC with UPA graphics
On Sat, 31 Jan 2004, Matt Prazak wrote: --- Matt Prazak [EMAIL PROTECTED] wrote: I haven't had much luck with Google, the list archives, or READMEs on this subject, so I guess I'll go ahead and ask: what is the status of the sunffb driver with respect to Solaris/SPARC in the most recent versions of XFree86? The 4.3.0 documentation says this driver is Linux-only, and I get the No devices to configure. Configuration failed. message from running XFree86 -configure under Solaris. My platform is Solaris 9 on an Ultra 30 with a Creator3D series 2 card. The main reason I want to try XFree86 in place of Sun's X server is to see whether I get better XInput support with some GTK+ applications. I just wanted to clarify that I'm asking about versions beyond 4.3.0 (development, release-canidate, etc.), as what I wrote above sounds a little as if I had answered my own question. The XFree86 port to this platform is still a work in progress, and as such, must still be built from source (preferrably CVS source). Follow the instructions in Domain.note and README.Solaris. If problems remain after this please post about them on [EMAIL PROTECTED] Patches to bring this port closer to binary distribution quality would also be most appreciated. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] XFree86 4.3.x: ValueUnion and loaded variable names
On Wed, 18 Feb 2004, Kelledin wrote: While compiling XFree86-4.3.0.1 recently, I got the following error message: In file included from text-mode.c:47: loader.h:78: warning: ISO C doesn't support unnamed structs/unions loader.h:78: unnamed fields of type other than struct or union are not allowed text-mode.c: In function `TextMode': text-mode.c:208: warning: string length `535' is greater than the length `509' ISO C89 compilers are required to support make[5]: *** [text-mode.o] Error 1 make[5]: Leaving directory `/usr/src/incept/BUILD/xc/programs/Xserver/hw/xfree86/xf86cfg' make[4]: *** [all] Error 2 make[4]: Leaving directory `/usr/src/incept/BUILD/xc/programs/Xserver/hw/xfree86' make[3]: *** [hw/xfree86] Error 2 make[3]: Leaving directory `/usr/src/incept/BUILD/xc/programs/Xserver' make[2]: *** [install] Error 2 make[2]: Leaving directory `/usr/src/incept/BUILD/xc/programs' make[1]: *** [install] Error 2 make[1]: Leaving directory `/usr/src/incept/BUILD/xc' make: *** [install] Error 2 I looked into it, and it's occurring because of the following line in the ValueUnion type: Boolbool; bool is a loaded name. It's a defined type in all C++ compilers, and it's also defined in plain old non-C++ gcc whenever something includes stdbool.h. In my case, I hit it for the first time yesterday because curses.h from ncurses 5.4 now includes the stdbool.h header. So far I see three possible solutions: 1) force ncurses to not include stdbool.h. This definitely isn't ideal, primarily because it won't stop the next package from including stdbool.h, and then we'll be dealing with this garbage all over again. 2) undefine the bool type before defining the ValueUnion type (see attached patch). This is hardly ideal, as several other source files in XFree86 depend on that type, and this could give us headaches down the road. Plus, I don't know how portable this hack is--it might not work on other toolchains besides linux+gcc+libc6. 3) rename the ValueUnion.bool field to something else, like xbool or boolval. This would be the perfect solution, except that ValueUnion.bool is part of a documented API for XFree86 driver modules, and it wouldn't be particularly nice to break the API. I would assume there would be ABI breakage as well, since I'm not sure exactly how unions get handled at link-time across different platforms. What I'd probably do is go with (2) for the current 4.3.0 branch, and implement (3) for 4.4.0 or some later release where a driver API break is marginally acceptable. Anything besides (3) should just be treated as a temporary stopgap measure, as otherwise we'd just be digging ourselves deeper into the same hole. First off, 2) doesn't work if stdbool.h is #included after the headers being modified here. Secondly (and perhaps more to the point), is that stdbool.h is a very recent (glibc-wise) invention (read: bleeding edge). So, in your shoes, I'd first talk to the glibc people about the implications of an stdbool.h in the first place. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Please help: using any new kernels, xserver won't start
On Tue, 24 Feb 2004, Jim Thomas wrote: I'm running RedHat Enterprise Edition and am trying to change my kernel to facilitate some networking issues. I've been frustrated by the xserver not being able to boot when using the networking kernel, so I've tried with a plain vanilla kernel and the same thing happens (see error msg and logfile below). When I boot to the original redhat kernel in grub, everything works fine. I haven't changed anything about the X configuration that came with the original distribution. Please Help! Here's the error message I get when the system attempts to start the graphical login screen: I cannot start the X server (your graphical interface). It is likely that it is not set up correctly. Would you like to view the X server output to diagnose the problem? Then it gives me the first few lines of the logfile up until (==) Using config file: /etc/X11/XF86Config and asks if I want to run the configuration tool, which just runs for a minute and then the error message come up again. Then the whole process starts over. The log you included appears incomplete. Given the system is not hanging at this point, I'd expect further messages after the loading of the vbe module. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] ATI Driver help needed.
On Mon, 8 Mar 2004, Darcy Parker wrote: I have just tried to install Mandrake 9.2. I have an ATI Rage Pro 8 MB AGP VGA video card (Bios 11349801101 P/N 1024980511) on a Samsung SyncMaster 3 Monitor (CVM4967T). The setup tried to identify the Video card as a ATI Mach64 Ultra. So far regarless of which version of xFree I try or different combinations of video/monitor settings I make I can't seem to get it to work. If I am not mistaken, DrakeX is using 800x600x16 (see as loading) which seems to work fine. When the setup gets to the Graphics configuration It seems to fail, even though a test at 800x600x16 passes. I am new to Linux and could use some guidance here. For a start, post your /var/log/XFree86.*.log* Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] ATI Driver help needed.
On Wed, 10 Mar 2004, Darcy Parker wrote: On Mon, 8 Mar 2004, Darcy Parker wrote: I have just tried to install Mandrake 9.2. I have an ATI Rage Pro 8 MB AGP VGA video card (Bios 11349801101 P/N 1024980511) on a Samsung SyncMaster 3 Monitor (CVM4967T). The setup tried to identify the Video card as a ATI Mach64 Ultra. So far regarless of which version of xFree I try or different combinations of video/monitor settings I make I can't seem to get it to work. If I am not mistaken, DrakeX is using 800x600x16 (see as loading) which seems to work fine. When the setup gets to the Graphics configuration It seems to fail, even though a test at 800x600x16 passes. I am new to Linux and could use some guidance here. For a start, post your /var/log/XFree86.*.log* Thanks Mark, Please find attached log file after issueing startx command. ^ c! I don't know why DrakeX isn't working, but you can generate a basic configuration by running `XFree86 -configure` and moving the resulting $HOME/XF86Config.new into /etc/X11/XF86Config-4. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] latest changes in CVS locksup System
On Fri, 12 Mar 2004, PSI-Systems wrote: Please try the attached patch. FWIW, if this patch doesn't apply cleanly, then your report is based on out-dated information. It applyed cleanly, but doesn't work! I made a guess that's the new gcc-3.4, so I recompiled all (make distcleann make World) with gcc-3.3 but the whole systems still locks up. Please help! What's with all the ! ? Don't panic. CVS trunk isn't due for release anytime soon... I'll get back to tou. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] XF86 Server Crash
On Fri, 5 Mar 2004, Wes Jennings wrote: I have a persistent XF86 server crash. Here are some details and my attached /var/log file. Any help with what I am dealing with greatly appreciated. Thanks in advance, Wes Jennings email: wes @harbornet.com 1. Generic 200MHz Pentium computer with 128Meg memory, running icewm-??? 2. I have not experienced any other problem except when running xboard-4-0.7, as shipped with Slackware-9.1. When I attempt to run xboard, it creates a server crash, not immediately, but within the first minute or less of operation. This happens if I am running the chess playing engine or running xboard in stand-alone mode. So it is something basically wrong with xboard, the XFree86 server, or something about how the interact. 3. The /var/log/XFree86.0.log is attached below, but there is one last paragraph of error messages that did not reach this log file. It states the following. XIO: fatal IO error 104 (Connection reset by peer) on X server :0.0 after 194628 requests (194510 known processed) with 0 events remaining. xterm: fatal IO error 32 (Broken pipe) or KillClient on X server :0.0 xinit: connection to X server lost. Acually, it states the following: Fatal server error: Caught signal 11. Server aborting When reporting a problem related to a server crash, please send the full server output, not just the last messages. This can be found in the log file /var/log/XFree86.0.log. Please report problems to [EMAIL PROTECTED] Would it be possible for you to check if the problem persists with XFree86 4.4? Thanks. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] latest changes in CVS locksup System
On Fri, 12 Mar 2004, Marc Aurele La France wrote: Please try the attached patch. FWIW, if this patch doesn't apply cleanly, then your report is based on out-dated information. It applyed cleanly, but doesn't work! I made a guess that's the new gcc-3.4, so I recompiled all (make distcleann make World) with gcc-3.3 but the whole systems still locks up. Please help! What's with all the ! ? Don't panic. CVS trunk isn't due for release anytime soon... I'll get back to tou. Please try the attached. This is in addition to what I've already got you to apply. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. PSI2.diff.gz Description: Binary data
Re: [XFree86] XF86 Server Crash
On Sun, 14 Mar 2004, Wes Jennings wrote: Actually, it states the following: Fatal server error: Caught signal 11. Server aborting I noticed this message. Do you figure the xboard program is sending an abort command that the X server is picking up? That doen't make any sense in the way I am using xboard. I am trying to play a chess game with it, not exit from it or bang away with some non-sense commands. Abort command?!? You're confused. Signal 11 is a segfault. In the server in this case. When reporting a problem related to a server crash, please send the full server output, not just the last messages. This can be found in the log file /var/log/XFree86.0.log. Please report problems to [EMAIL PROTECTED] Would it be possible for you to check if the problem persists with XFree86 4.4? I have never upgrading to a new X system before. I'm inclining to stay with my Slackware-9.1 distribution setup which is using X server 4.3. What is the logic behind changing to version 4.4? Is it known that version 4.3 has certain known problems that I am dealing with? 1) Yes, there were (note tense) related problems in 4.3 that have since been fixed. 2) This isn't a support line. I don't have time to deal with issues that have already been dealt with. Thanks for your response! Any insight on how to solve this problem would be appreciated. Wes Jennings, email: [EMAIL PROTECTED] ... Then set this in your From: lines. That what you have there bounces is most annoying. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] 4.4.0 and IPv6
On Tue, 16 Mar 2004, T. Horsnell (tsh) wrote: I need to build 4.4.0 from source without IPv6 support. I cant see how to do this from the 'Building XFree86 from a Source Distribution' docs, and there'e no mention of any obvious config params in xfree86-4.4.0/src/xc/config/cf/xf86site.def. Any ideas anyone? '#define BuildIPv6 NO' in xc/config/cf/host.def Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] Am I compiling the right thing?
On Wed, 17 Mar 2004, Edward Ned Harvey wrote: I have Solaris 8 on sparc, and I want Xnest to run in a window, so I can open more CDE sessions on other Solaris machines. There is no binary distribution of Xnest available for the sparc version of sol8. There is only the intel version that I can find. I have downloaded and compiled XF86 versions 4.0.2, 4.1.0, 4.2.0, and 4.3.0 (Have trouble compiling v4.4.0) But when the build is finished, there is no file called xnest or Xnest. Am I trying to compile the right package, or should I be trying something else? (I downloaded these, extracted them all, and built according to the instructions:) X430src-1.tgz X430src-2.tgz X430src-3.tgz X430src-4.tgz X430src-5.tgz X430src-6.tgz X430src-7.tgz Please read xc/programs/Xserver/hw/xfree86/doc/README.Solaris That's very good information, and thank you very much. However, I still don't have an Xnest binary, and I still don't know how to get one. When I compile XFree86, am I *supposed* to get an Xnest binary? Or am I building the wrong package somehow? Xnest (and Xvfb) should be built by default, if your host.def asserts BuildXFree86OnSparcSunOS. Otherwise, you need to assert XnestServer and/or XVirtualFramebufferServer. Don't forget to `make World` when you change these settings. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] r128 XVideo bug
On Mon, 26 Jan 2004 [EMAIL PROTECTED] wrote: Hello all... I'm new to the list but figured I'd pass along some information that I found through a rather frustrating experience. I have built a VGA-NTSC converter board (NOT a scan converter) for high-quality TV-Out on any card. I discovered that the r128 driver does a very strange thing with XVideo on an interlaced monitor. It doesn't draw the bottom half of of a video (played with MythTV or mplayer), but stretches the top to fill the screen. After much surfing around, I eventually tried the GATOS driver for the same card. This does not have the problem. Relevent info it: XFree86 4.3.0 (Latest RedHat9 update) ATI Rage 128 16 MB AGP card Any interlaced modeline (first discovered using [EMAIL PROTECTED] Hz Interlaced) I have just committed a fix for this. Thanks for reporting the problem. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Re: SoundBlaster Live! 5.1 Value Detected as VGA Device:
On Sun, 21 Mar 2004, Mark Vojkovich wrote: I am using the latest BIOS for my machine, a DELL Dimension XPS R400. The BIOS version is A13, the newest thing from Dell's website. Albiet, it was created in 1999, but it's the newest they have. There is no onboard video on my motherboard - the second video device the X-server thinks it found is the SoundBlaster Live! 5.1 Value card (CT4830). There are no video ports on the sound card, just 4 audio jacks and a MIDI/Joystick port. Proof of this list error is found by running lspci, which says the SB Live! is a VGA Compatible Unclassified Device. Here's the output from that: That sounds like a motherboard BIOS bug then, or a bug with the SB Live card's PCI config space. It's b). Creator is notorious for producing adapters that mis-advertise their PCI type as 00/01 (prehistoric VGA) instead of 04/01 (multimedia audio). Also, the motherboard BIOS has no way of overriding these types. Adding: BusID PCI:0:13:0 to the Section Device will force the ATI driver to use the correct card. Hopfully XFree86's RAC support isn't confused by the two VGA compatible devices. That helps, certainly, but by then, this hardware bug has already caused us to not mark the Radeon as the primary adapter. This causes an attempt to re-initialise the Radeon, which is not a good idea due to a separate bug in its BIOS. This'll require a code change to fix. But I'm not sure what the best way to fix this is. There's a mechanism in the server to override advertised PCI types, but it's not pervasive, affecting only certain areas. Anyway, I'll look into it. In the meantime, I'd suggest ripping out the Creative, perhaps replacing with an adapter that doesn't display this problem. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Re: SoundBlaster Live! 5.1 Value Detected as VGA Device:
On Sun, 21 Mar 2004, Marc Aurele La France wrote: I am using the latest BIOS for my machine, a DELL Dimension XPS R400. The BIOS version is A13, the newest thing from Dell's website. Albiet, it was created in 1999, but it's the newest they have. There is no onboard video on my motherboard - the second video device the X-server thinks it found is the SoundBlaster Live! 5.1 Value card (CT4830). There are no video ports on the sound card, just 4 audio jacks and a MIDI/Joystick port. Proof of this list error is found by running lspci, which says the SB Live! is a VGA Compatible Unclassified Device. Here's the output from that: That sounds like a motherboard BIOS bug then, or a bug with the SB Live card's PCI config space. It's b). Creator is notorious for producing adapters that mis-advertise their PCI type as 00/01 (prehistoric VGA) instead of 04/01 (multimedia audio). I, of course, meant Creative, not Creator. Also, the motherboard BIOS has no way of overriding these types. Adding: BusID PCI:0:13:0 to the Section Device will force the ATI driver to use the correct card. Hopfully XFree86's RAC support isn't confused by the two VGA compatible devices. That helps, certainly, but by then, this hardware bug has already caused us to not mark the Radeon as the primary adapter. This causes an attempt to re-initialise the Radeon, which is not a good idea due to a separate bug in its BIOS. This'll require a code change to fix. But I'm not sure what the best way to fix this is. There's a mechanism in the server to override advertised PCI types, but it's not pervasive, affecting only certain areas. Anyway, I'll look into it. In the meantime, I'd suggest ripping out the Creative, perhaps replacing with an adapter that doesn't display this problem. It turns out there's a straightforward workaround for this problem. As root, do ... cd /usr/X11R6/lib/modules cp libpcidata.a libpcidata.backup cp libscanpci.a libpcidata.a ... and stop and restart the X server. The BusID specification should then be unnecessary (as would removing the Sound Blaster adapter). Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Re: SoundBlaster Live! 5.1 Value Detected as VGA Device:
On Mon, 22 Mar 2004, Andrew D. wrote: After reading your e-mail, Marc, I instantly rebooted from Win98 (where I'm reading this info) to Mandrake Linux's Failsafe. I logged in a root, edited my XF86Config-4 file and commented out the PCIbus line. I closed that down, and followed your instructions for replacing the libpcidata.a file with my libscanpci.a file. After that, I rebooted my machine. Upon starting Mandrake 10 normally, I was given the following error by my X-Server: (EE) LoadModule: Module pcidata does not have a pcidataModuleData data object. Doh! Silly me... Attached is the new log file. Thanks so much for your input and your quick responses. If only Microsoft gave tech support this quickly. ~~ Andrew Marc Aurele La France wrote: It turns out there's a straightforward workaround for this problem. As root, do ... cd /usr/X11R6/lib/modules cp libpcidata.a libpcidata.backup cp libscanpci.a libpcidata.a Replace that last command with ... sed 's/scanpci/pcidata/g' libscanpci.a libpcidata.a (Good thing the two strings are the same length...) ... and stop and restart the X server. The BusID specification should then be unnecessary (as would removing the Sound Blaster adapter). Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Re: Thank you!!!
On Tue, 23 Mar 2004, Andrew D. wrote: Marc, Thank you so much for your input on the XFree86 mailing list. After I ran... cd /usr/X11R6/lib/modules cp libpcidata.a libpcidata.backup sed 's/scanpci/pcidata/g' libscanpci.a libpcidata.a ... and restarted my computer, the sound card and the video card played nice. I get sound signals sent to the sound card, and video signals to the video card. It's nice to have technology work for a change. :P I've posted the solution at LinuxBeginner.org, with proper credit to you in the appropriate places. Hopefully someone else can benefit from this experience. Thank you, thank you, thank you. *repeat ad infinitum* ~~ Andrew D. [EMAIL PROTECTED] You're most welcome (also ad infinitum). The required change has already been committed so that the problem will no longer occur in post-4.4 versions. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Help with broken X please.
On Wed, 24 Mar 2004, Mark Vojkovich wrote: If /proc/pci also shows multiple instances of that S3 card then I think your motherboard bios has a bug. If /proc/pci only shows one S3 card, then this looks like an XFree86 bug and perhaps you should try XFree86 4.4 instead. If /proc/pci shows multiple S3 cards, I don't think XFree86 4.4 would work any better than your current server. Actually, the problem of ghost devices should be solved in 4.4 (regardless of OS and/or kernel). Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] end of block range 0xffb begin 0xfffffffc ???????
- 0xb8ff (0x100) IX[B] [3] -1 0 0xbc00 - 0xbcff (0x100) IX[B] [4] -1 0 0xc000 - 0xc0ff (0x100) IX[B] [5] -1 0 0xc400 - 0xc4ff (0x100) IX[B] [6] -1 0 0xc800 - 0xc8ff (0x100) IX[B] [7] -1 0 0xcc00 - 0xccff (0x100) IX[B] [8] -1 0 0xd000 - 0xd0ff (0x100) IX[B] [9] -1 0 0xd400 - 0xd4ff (0x100) IX[B] [10] -1 0 0xd800 - 0xd8ff (0x100) IX[B] [11] -1 0 0xdc00 - 0xdcff (0x100) IX[B] (II) Bus 2 non-prefetchable memory range: [0] -1 0 0xed80 - 0xedff (0x80) MX[B] (II) Bus 2 prefetchable memory range: [0] -1 0 0xefe0 - 0xefef (0x10) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:31:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (--) PCI:*(1:0:0) nVidia Corporation NV15 [GeForce2 GTS/Pro] rev 163, Mem @ 0xee 00/24, 0xf000/27, BIOS @ 0xefff/16 (II) Addressable bus resource ranges are [0] -1 0 0x - 0x (0x0) MX[B] [1] -1 0 0x - 0x (0x1) IX[B] (II) OS-reported resource ranges: [0] -1 0 0xffe0 - 0x (0x20) MX[B](B) [1] -1 0 0x0010 - 0x3fff (0x3ff0) MX[B]E(B) [2] -1 0 0x000f - 0x000f (0x1) MX[B] [3] -1 0 0x000c - 0x000e (0x3) MX[B] [4] -1 0 0x - 0x0009 (0xa) MX[B] [5] -1 0 0x - 0x (0x1) IX[B] [6] -1 0 0x - 0x00ff (0x100) IX[B] (II) PCI Memory resource overlap reduced 0xf800 from 0xfbff to 0xf7ff (EE) end of block range 0xffb begin 0xfffc *** If unresolved symbols were reported above, they might not *** be the reason for the server aborting. Fatal server error: Caught signal 11. Server aborting When reporting a problem related to a server crash, please send the full server output, not just the last messages. This can be found in the log file /var/log/XFree86.0.log. Please report problems to [EMAIL PROTECTED] - I'm using Gentoo 2004.0 stage1 Thank you for your help! I need to see the output from two successive `scanpci -v` runs before I can begin to address this problem. Thanks. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] VeraIt.ttf installation bug (and patch)
On Mon, 29 Mar 2004, Patrick J. Volkerding wrote: Greetings XFree86 developers, I received a bug report today (from Stepan Roh) that VeraIt.ttf was missing from Slackware's XFree86-fonts-scale-4.4.0-noarch-1.tgz package, and found that it was left out of the fonts/scaled/TTF/Imakefile in XFree86 4.4.0. The trivial patch below will fix it. This has already been committed, but thanks anyway. Thanks for your great work, Thanks for yours too. Pat --- ./fonts/scaled/TTF/Imakefile.orig 2003-12-31 11:30:39.0 -0800 +++ ./fonts/scaled/TTF/Imakefile 2004-03-29 12:13:14.0 -0800 @@ -5,7 +5,7 @@ luxisb.ttf luxisbi.ttf luxisr.ttf luxisri.ttf VERASRCDIR = $(TOP)/extras/fonts/Bitstream-Vera -VERAFONTS = Vera.ttf VeraBI.ttf VeraBd.ttf VeraMoBI.ttf VeraMoBd.ttf \ +VERAFONTS = Vera.ttf VeraBI.ttf VeraBd.ttf VeraIt.ttf VeraMoBI.ttf VeraMoBd.ttf \ VeraMoIt.ttf VeraMono.ttf VeraSe.ttf VeraSeBd.ttf FONTS = $(LUXIFONTS) $(VERAFONTS) Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] problems asus l5800
On Sun, 4 Apr 2004, lycos wrote: (--) PCI:*(0:15:0) VMWare Inc unknown chipset (0x0405) rev 0, Mem @ 0xfa00/24, 0xf900/24, I/O @ 0x1400/4 Nothing else needs to be said... Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Weird Problem : Need help or explanation!
On Sun, 4 Apr 2004, David Hill wrote: I just noticed (while looking at /var/log/messages) that when I boot Linux (on a dual P3 500 with onboard scsi controllers) there is absolutely NO PROBLEMS. XDM starts with the login windows and everything looks fine. As soon as I type the username/password and login Xfree/KDE, there is a lot of Parity Errors observed. Could the problem be in the Linux/Ati rage 128 drivers for X ? What I don't understand is that XDM is using Xfree. So why the problem is occuring only when XDM gives the control to Xfree/KDE? I'm not pretty sure of the location of the problem, but it's pretty weird. There is PCI parity errors until I press ENTER in the XDM login window. Anything else on the computer will work just fine. Before entering the window manager or quitting XDM or else, I can kill -9, ctrl-alt-backspace, /etc/rc2.d/S99xdm restart anytime and there is no problem. I can listen to my mp3s, do ANYTHING with the computer... but as I said earlier, as soon as I login using XDM, or else, type startx, it starts making noise/bad parity on the scsi controler. I think it could be an IRQ problem, but the point is that the parity error messages are only happening (and wont quit until I restart the computer) when I use Xfree... That's plausible, I suppose. But, first, let's see if the parity errors persists with Option NoAccel in your XF86Config's device section. This'll slow things down considerably, of course, but would shed light on the problem. Thanks. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] XFree86 4.3.0.2 server not exiting
On Wed, 7 Apr 2004, Ulrich Teichert wrote:
I'm having a wierd problem with XFree86 4.3.0.2 (build from source on
x86-linux, running on a settop box with a Geode chip, nsc driver, keyboard
and mouse over TV-IR and fed into /dev/tty0 and /dev/gpmdata, repectively)
First, the X server runs like a charm. Stable and reliable, does not seem
to have memory leaks or something. Very nice, until it comes to stopping
it. CTRL-C on the console or SIGTERM does not terminate the server and
it is using all CPU it can get in a busy loop. It is killable with SIGKILL,
though.
I really would like to understand the problem behind it, before I start
fiddeling with a workaround (like killing the Xserver with SIGKILL instead
of SIGTERM anytime). I suspect it's just a configuration issue.
[...]
I traced it down where the server is hanging, it's the same spot everytime,
but I wasn't able to see the C-source of it, despite building *everything*
with debug and using a libc with debugging symbols (nfs mounted - the box
does not have a hard disk). The stack trace is:
#0 0x401a875c in ?? ()
#1 0x4018a6b7 in ?? ()
#2 0x4018a6e6 in ?? ()
#3 0x081667da in AnimCurCloseScreen (index=0, pScreen=0x83327e0)
at animcur.c:126
#4 0x080c07c5 in main (argc=8, argv=0xbdc4, envp=0xbde8) at main.c:459
Line 126 in animcur.c is:
ret = (*pScreen-CloseScreen) (index, pScreen);
(gdb) p screenInfo
$2 = {imageByteOrder = 0, bitmapScanlineUnit = 32, bitmapScanlinePad = 32,
bitmapBitOrder = 0, numPixmapFormats = 7, formats = {{depth = 1 '\001',
bitsPerPixel = 1 '\001', scanlinePad = 32 ' '}, {depth = 4 '\004',
bitsPerPixel = 8 '\b', scanlinePad = 32 ' '}, {depth = 8 '\b',
bitsPerPixel = 8 '\b', scanlinePad = 32 ' '}, {depth = 15 '\017',
bitsPerPixel = 16 '\020', scanlinePad = 32 ' '}, {depth = 16 '\020',
bitsPerPixel = 16 '\020', scanlinePad = 32 ' '}, {depth = 24 '\030',
bitsPerPixel = 32 ' ', scanlinePad = 32 ' '}, {depth = 32 ' ',
bitsPerPixel = 32 ' ', scanlinePad = 32 ' '}, {depth = 0 '\0',
bitsPerPixel = 0 '\0', scanlinePad = 0 '\0'}}, arraySize = 16,
numScreens = 1, screens = {0x83327e0, 0x0 repeats 15 times},
numVideoScreens = 1}
(gdb) p pScreen
$6 = 0x3d5
The disassembled x86 code where it loops is:
0x401a9759: mov%ebx,%edx
0x401a975b: in (%dx),%al
0x401a975c: test %al,%al
0x401a975e: jl 0x401a9759
0x401a9760: mov$0x30,%al
0x401a9762: mov%esi,%edx
0x401a9764: out%al,(%dx)
(gdb) info all-registers
eax0xff 255
ecx0x3d5981
edx0x3d5981
ebx0x3d5981
[snip]
The loop starts at 0x401a9759 and goes to 0x401a975e. If I jump to
0x401a9760 in the debugger, the server terminates. So, it reads 0x3d5,
whatever that is (probably I/O stuff) and the test never succeeds.
Looks like it's looping in function gfx_vga_mode_switch() near the tail end of
xc/programs/Xserver/hw/xfree86/drivers/ncs/gfx/vga_gu1.c, part of which reads
/* WAIT UNTIL SOFTVGA HAS VALIDATED MODE IF ENDING MODE SWITCH */
/* This is for VSA1 only, where SoftVGA waits until the next */
/* vertical blank to validate the hardware state. */
if ((!active) (!(gu1_detect_vsa2( {
OUTB(crtcindex, 0x33);
while (INB(crtcdata) 0x80) ;
}
Change this to ...
/* WAIT UNTIL SOFTVGA HAS VALIDATED MODE IF ENDING MODE SWITCH */
/* This is for VSA1 only, where SoftVGA waits until the next */
/* vertical blank to validate the hardware state. */
if ((!active) (!(gu1_detect_vsa2( {
int cnt = 256;
OUTB(crtcindex, 0x33);
while (--cnt (INB(crtcdata) 0x80));
}
... and see what happens.
Marc.
+--+---+
| Marc Aurele La France | work: 1-780-492-9310 |
| Computing and Network Services | fax:1-780-492-1729 |
| 352 General Services Building | email: [EMAIL PROTECTED] |
| University of Alberta +---+
| Edmonton, Alberta | |
| T6G 2H1 | Standard disclaimers apply|
| CANADA | |
+--+---+
XFree86 developer and VP. ATI driver and X server internals.
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] XFree86 4.3.0.2 server not exiting
On Wed, 14 Apr 2004, Ulrich Teichert wrote:
first, sorry for the delay. I had a short vacation over easter.
Not a problem.
(gdb) info all-registers
eax0xff 255
ecx0x3d5981
edx0x3d5981
ebx0x3d5981
[snip]
The loop starts at 0x401a9759 and goes to 0x401a975e. If I jump to
0x401a9760 in the debugger, the server terminates. So, it reads 0x3d5,
whatever that is (probably I/O stuff) and the test never succeeds.
Looks like it's looping in function gfx_vga_mode_switch() near the tail end of
xc/programs/Xserver/hw/xfree86/drivers/ncs/gfx/vga_gu1.c, part of which reads
/* WAIT UNTIL SOFTVGA HAS VALIDATED MODE IF ENDING MODE SWITCH */
/* This is for VSA1 only, where SoftVGA waits until the next */
/* vertical blank to validate the hardware state. */
if ((!active) (!(gu1_detect_vsa2( {
OUTB(crtcindex, 0x33);
while (INB(crtcdata) 0x80) ;
}
Change this to ...
/* WAIT UNTIL SOFTVGA HAS VALIDATED MODE IF ENDING MODE SWITCH */
/* This is for VSA1 only, where SoftVGA waits until the next */
/* vertical blank to validate the hardware state. */
if ((!active) (!(gu1_detect_vsa2( {
int cnt = 256;
OUTB(crtcindex, 0x33);
while (--cnt (INB(crtcdata) 0x80));
}
... and see what happens.
Great! Now, it terminates correctly,
Thanks a million,
Well, that's fine, but my suggestion is only a workaround. I don't have docs
for this chip, but it would be better to know what CRTC 0x33 is, what this code
is waiting for (0x80 isn't my idea of descriptive), and why the hardware isn't
turning off this bit.
Marc.
+--+---+
| Marc Aurele La France | work: 1-780-492-9310 |
| Computing and Network Services | fax:1-780-492-1729 |
| 352 General Services Building | email: [EMAIL PROTECTED] |
| University of Alberta +---+
| Edmonton, Alberta | |
| T6G 2H1 | Standard disclaimers apply|
| CANADA | |
+--+---+
XFree86 developer and VP. ATI driver and X server internals.
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Can't build XFree86
On Wed, 21 Apr 2004, Noel Henson wrote: I've looked everywhere on the web for a solution to this problem and have come up empty handed. I've been trying to build 4.4.0 for two days now and I still get this when trying to build: In file included from text-mode.c:47: loader.h:78: warning: ISO C doesn't support unnamed structs/unions loader.h:78: unnamed fields of type other than struct or union are not allowed text-mode.c: In function `TextMode': text-mode.c:220: warning: string length `535' is greater than the length `509' ISO C89 compilers are required to support make[6]: *** [text-mode.o] Error 1 make[6]: Leaving directory `/usr/src/XFree-4.4.0/xc/programs/Xserver/hw/xfree86/xf86cfg' make[5]: *** [all] Error 2 make[5]: Leaving directory `/usr/src/XFree-4.4.0/xc/programs/Xserver/hw/xfree86' make[4]: *** [hw/xfree86] Error 2 make[4]: Leaving directory `/usr/src/XFree-4.4.0/xc/programs/Xserver' make[3]: *** [all] Error 2 make[3]: Leaving directory `/usr/src/XFree-4.4.0/xc/programs' make[2]: *** [all] Error 2 make[2]: Leaving directory `/usr/src/XFree-4.4.0/xc' make[1]: *** [World] Error 2 make[1]: Leaving directory `/usr/src/XFree-4.4.0/xc' make: *** [World] Error 2 Any help would be great. There is already a fix for this error in both the xf-4_4-branch and HEAD branches of XFree86's CVS repository. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] XFree86 4.3.0.2 server not exiting
On Wed, 21 Apr 2004, Ulrich Teichert wrote: [workaround patch for hang-on-exit on Geode hardware in xc/programs/Xserver/hw/xfree86/drivers/nsc/gfx/vga_gu1.c] Well, that's fine, but my suggestion is only a workaround. I don't have docs for this chip, but it would be better to know what CRTC 0x33 is, what this code is waiting for (0x80 isn't my idea of descriptive), and why the hardware isn't turning off this bit. After a bit of googling, I've found the offical docs on the AMD website: http://www.amd.com/us-en/ConnectivitySolutions/TechnicalResources/0,,50_2334_2496_9919,00.html You'll need a registration, but that's it. There's an AMD Geode SC1200/1201 Processor Data Book with full description of the video registers. Now, if I'd only would understand why the code is poking around in reserved registers - but probably I just don't understand what's going on there or the video registers are mapped into another region. OK, I'll have a look. In the meantime, I've committed the change. Thanks. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] failed server
Project compiled for 4.3.0, module version = 1.0.0 Module class: XFree86 XInput Driver ABI class: XFree86 XInput driver, version 0.4 (II) ATI: ATI driver (version 6.4.18) for chipsets: ati, ativga (II) R128: Driver for ATI Rage 128 chipsets: ATI Rage 128 Mobility M3 LE (PCI), ATI Rage 128 Mobility M3 LF (AGP), ATI Rage 128 Mobility M4 MF (AGP), ATI Rage 128 Mobility M4 ML (AGP), ATI Rage 128 Pro GL PA (PCI/AGP), ATI Rage 128 Pro GL PB (PCI/AGP), ATI Rage 128 Pro GL PC (PCI/AGP), ATI Rage 128 Pro GL PD (PCI), ATI Rage 128 Pro GL PE (PCI/AGP), ATI Rage 128 Pro GL PF (AGP), ATI Rage 128 Pro VR PG (PCI/AGP), ATI Rage 128 Pro VR PH (PCI/AGP), ATI Rage 128 Pro VR PI (PCI/AGP), ATI Rage 128 Pro VR PJ (PCI/AGP), ATI Rage 128 Pro VR PK (PCI/AGP), ATI Rage 128 Pro VR PL (PCI/AGP), ATI Rage 128 Pro VR PM (PCI/AGP), ATI Rage 128 Pro VR PN (PCI/AGP), ATI Rage 128 Pro VR PO (PCI/AGP), ATI Rage 128 Pro VR PP (PCI), ATI Rage 128 Pro VR PQ (PCI/AGP), ATI Rage 128 Pro VR PR (PCI), ATI Rage 128 Pro VR PS (PCI/AGP), ATI Rage 128 Pro VR PT (PCI/AGP), ATI Rage 128 Pro VR PU (PCI/AGP), ATI Rage 128 Pro VR PV (PCI/AGP), ATI Rage 128 Pro VR PW (PCI/AGP), ATI Rage 128 Pro VR PX (PCI/AGP), ATI Rage 128 GL RE (PCI), ATI Rage 128 GL RF (AGP), ATI Rage 128 RG (AGP), ATI Rage 128 VR RK (PCI), ATI Rage 128 VR RL (AGP), ATI Rage 128 4X SE (PCI/AGP), ATI Rage 128 4X SF (PCI/AGP), ATI Rage 128 4X SG (PCI/AGP), ATI Rage 128 4X SH (PCI/AGP), ATI Rage 128 4X SK (PCI/AGP), ATI Rage 128 4X SL (PCI/AGP), ATI Rage 128 4X SM (AGP), ATI Rage 128 4X SN (PCI/AGP), ATI Rage 128 Pro ULTRA TF (AGP), ATI Rage 128 Pro ULTRA TL (AGP), ATI Rage 128 Pro ULTRA TR (AGP), ATI Rage 128 Pro ULTRA TS (AGP?), ATI Rage 128 Pro ULTRA TT (AGP?), ATI Rage 128 Pro ULTRA TU (AGP?) (II) RADEON: Driver for ATI Radeon chipsets: ATI Radeon QD (AGP), ATI Radeon QE (AGP), ATI Radeon QF (AGP), ATI Radeon QG (AGP), ATI Radeon VE/7000 QY (AGP), ATI Radeon VE/7000 QZ (AGP), ATI Radeon Mobility M7 LW (AGP), ATI Mobility FireGL 7800 M7 LX (AGP), ATI Radeon Mobility M6 LY (AGP), ATI Radeon Mobility M6 LZ (AGP), ATI FireGL 8700/8800 QH (AGP), ATI Radeon 8500 QI (AGP), ATI Radeon 8500 QJ (AGP), ATI Radeon 8500 QK (AGP), ATI Radeon 8500 QL (AGP), ATI Radeon 9100 QM (AGP), ATI Radeon 8500 QN (AGP), ATI Radeon 8500 QO (AGP), ATI Radeon 8500 Qh (AGP), ATI Radeon 8500 Qi (AGP), ATI Radeon 8500 Qj (AGP), ATI Radeon 8500 Qk (AGP), ATI Radeon 8500 Ql (AGP), ATI Radeon 8500 BB (AGP), ATI Radeon 7500 QW (AGP), ATI Radeon 7500 QX (AGP), ATI Radeon 9000 Id (AGP), ATI Radeon 9000 Ie (AGP), ATI Radeon 9000 If (AGP), ATI Radeon 9000 Ig (AGP), ATI Radeon Mobility M9 Ld (AGP), ATI Radeon Mobility M9 Le (AGP), ATI Radeon Mobility M9 Lf (AGP), ATI Radeon Mobility M9 Lg (AGP), ATI Radeon 9500 AD (AGP), ATI Radeon 9500 AE (AGP), ATI Radeon 9500 AF (AGP), ATI FireGL Z1/X1 AG (AGP), ATI Radeon 9700 Pro ND (AGP), ATI Radeon 9700/9500Pro NE (AGP), ATI Radeon 9700 NF (AGP), ATI FireGL X1 NG (AGP) (II) Primary Device is: PCI 00:0b:0 (--) Assigning device section with no busID to primary device (EE) No devices detected. Fatal server error: no screens found When reporting a problem related to a server crash, please send the full server output, not just the last messages. This can be found in the log file /var/log/XFree86.0.log. Please report problems to [EMAIL PROTECTED] +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Compaq EN Deskpro SFF PIII/550 + Xfree
On Tue, 4 May 2004, Dev Team wrote: I'm trying to run XFree86 on a Debian system (unstable), on a Compaq EN Deskpro SFF PIII/550. This system has an ATI Technologies Inc 3D Rage Pro AGP 1X/2X (rev 5c) VGA controller. Well, when i try to run startx, the display freezes.. ALT+CTRL+F1, F2, etc does not work. The same with ALT+CTRL+backspace. I can access the computer through network, via ssh... but i have either to kill startx, or i have to reboot.. It sounds like it's in a loop. While ssh'ed in, what does `top` show? I could supply the log file, if someone could help me.. Yes, that would be a good place to start. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] cvs build problems
On Thu, 6 May 2004, Stefan Lucke wrote: I've some troubles compiling XFree86 cvs version. Last weekend I tried HEAD from cvs, had my troubles which I could finally resolve with removing #define DefaultGcc2i386Opt -O2 and using the default one (commented out). After installing this build I had troubles with segmentation faults in some applications which I could track down to fonts access to lucida family (KDE font selector crashed, suses's yast2 software installer crashed). So I went back to xf-4_4_99_3 with cvs update -A -d -r xf-4_4_99_3. Did my make World, make install and suprisingly crashes disappeared. (font selection for lucida is OK and yast2 software installer is ok too). Next I gave xf-4_4_99_4 a chance but make World failed. Has anyone made similar experiences or are there known problems with 4_4_99_4 or HEAD ? Your tree is not consistent. Re-checkout (not update nor anything else) the tag you want and start again. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Cannot get Xfree86 to work on a dec alpha with a mach64 video
On Sun, 16 May 2004 [EMAIL PROTECTED] wrote: The version of XFree86 4.2.1 The Operating System and its version number. FreeBSD 5.0-RC The video hardware that you are using. ATI Mach64 with ATI 18818-1, att20c408-13 Hardware: Alpha 1000A 5/333 Dell Ultrascan 15FS get the following error using # XFree86 -xf86config XF86Config (EE) ATI(0) Cannot read V_BIOS (5) That's not the problem. Any help would be appreciated Try specifying the virtual resolution you actually want instead of the bogus one you've got in your XF86Config now. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Xfree86 problems
On Tue, 18 May 2004, Super User wrote: i am working on putting the x windows system on my freebsd system at home and am experiencing some daunting problems compiling and configuring the entire x windows system any help would be greatly appreciated It looks like you have a Chipset specification in your /etc/X11/XF86Config. Comment it out. FWIW, you have a 3D Rage, which is a Mach64 variant, not a Rage 128, as you apparent told the configuration tool. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] XFree86: PCI device limited to 64 for xf86scanpci
On Wed, 26 May 2004, Busacker, Dale L wrote: I am currently working on a platform that has 75 PCI devices with the last one being the video controller. The latest releases of XFree limits the number of PCI devices scanned by xf86scanpci to 64 (MAX_PCI_DEVICES in xfree/os-support/bus/Pci.h). I have increased this to 128 to work on my platform but not being familiar with this code I am unsure what potential side effects might result. I don't see any side-effects, potential or otherwise. I'll commit a change to double the limit. Thanks. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] cvs build problems
On Fri, 7 May 2004, Stefan Lucke wrote: On Donnerstag, 6. Mai 2004 23:00, Marc Aurele La France wrote: On Thu, 6 May 2004, Stefan Lucke wrote: I've some troubles compiling XFree86 cvs version. Last weekend I tried HEAD from cvs, had my troubles which I could finally resolve with removing #define DefaultGcc2i386Opt -O2 and using the default one (commented out). After installing this build I had troubles with segmentation faults in some applications which I could track down to fonts access to lucida family (KDE font selector crashed, suses's yast2 software installer crashed). So I went back to xf-4_4_99_3 with cvs update -A -d -r xf-4_4_99_3. Did my make World, make install and suprisingly crashes disappeared. (font selection for lucida is OK and yast2 software installer is ok too). Next I gave xf-4_4_99_4 a chance but make World failed. Has anyone made similar experiences or are there known problems with 4_4_99_4 or HEAD ? Your tree is not consistent. Re-checkout (not update nor anything else) the tag you want and start again. Thanks, but that didn't change anything. The only advantage is that I can fallback to xf-4_4_99_3 with a simple make install since now I've separate trees. [EMAIL PROTECTED]:/home/nfs/extra/src/div/X11 ll insgesamt 105994 -rw-r--r--1 stefan users 649126 2004-05-07 17:41 cvs-01.log -rw-r--r--1 stefan users 672073 2004-05-07 19:44 cvs-xf-4_4_99_3.log -rw-r--r--1 stefan users 670215 2004-05-07 19:29 cvs-xf-4_4_99_4.log drwxr-xr-x5 stefan users 92 2004-05-06 19:39 dri -rw-r--r--1 stefan users54301927 2004-04-30 23:24 X11-xc-01-tar.gz -rw-r--r--1 stefan users52224253 2004-04-30 23:40 X11-xc-02-tar.gz drwxr-xr-x 13 stefan users 476 2004-05-07 17:40 xc_head drwxr-xr-x 13 stefan users 563 2004-05-07 18:58 xc_head_build drwxr-xr-x 14 stefan users1006 2004-05-06 22:21 xc.old drwxr-xr-x 12 stefan users 446 2004-05-07 19:42 xc_xf_4_4_99_3 drwxr-xr-x 12 stefan users 539 2004-05-07 20:49 xc_xf_4_4_99_3_build drwxr-xr-x 12 stefan users 446 2004-05-07 19:28 xc_xf_4_4_99_4 drwxr-xr-x 12 stefan users 509 2004-05-07 19:38 xc_xf_4_4_99_4_build [EMAIL PROTECTED]:/home/nfs/extra/src/div/X11 cvs head: segmentation faults with lucida fonts cvs xf-4_4_99_4: does not compile cvs xf-4_4_99_3: no seg faults with lucida fonts If you're using gcc = 3.1. make sure you're compiling with -fno-strict-alising. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] cvs build problems
On Wed, 26 May 2004, Marc Aurele La France wrote: On Fri, 7 May 2004, Stefan Lucke wrote: cvs head: segmentation faults with lucida fonts cvs xf-4_4_99_4: does not compile cvs xf-4_4_99_3: no seg faults with lucida fonts If you're using gcc = 3.1. make sure you're compiling with -fno-strict-alising. Oops. I meant -fno-strict-aliasing. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Server confusion over Primary display device.
On Fri, 21 May 2004, Tim Lynch wrote: I have written an XFree86 driver for Peritek's Siliconmotion731-based PMC board. The driver integrates a couple of video capture devices. PROBLEM: When I designate my PCI board as the Primary (console) device, things work great. The problem occurs when I designate the on-board graphics to be the console and then try to use my PCI board to host XFree86. The first server start after system boot correctly identifies my board as non-Primary and the driver treats the board accordingly. During any successive server starts, the pciBusprobe identifies my board as the Primary and, as you can imagine, bad things happen. Do you have any experience and/or directions for this situation? I'm a bit unclear on something here. Are the successive server starts while the first is still running? It sounds like the common layer isn't properly restoring VGA routing. Please post `lspci -v` stdout's produced before and after the first server start, and another after the first invocation ends. Thanks. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Problems using Xfree4.4 with Solaris 8 and a Silicon Motion SM722 graphics device
On Mon, 24 May 2004, Simon Egerton wrote: I'm having problems getting XFree 4.4 up and running with Solaris 8 on my ix86 base board using a Silicon Motion 722 graphics device. I've installed the Solaris 8 binaries and configured the XF86config file, but when I launch XFree I'm left with a blank screen. I've tried the same hardware set-up under Linux, installing again from the 4.4 binaries, and everything works fine. I've attached the respective log files, Solaris and Linux. From the Solaris log file I can see that the video BIOS is not detected, and the Silicon Motion driver is stuck in a loop issuing video reset commands. Has anyone else experienced the same problem? Is there a fix or workaround to get XFree working under Solaris with this SM graphics device? Here's something you can try on the Solaris side. Do everything as root. Install the aperture driver. Intructions for this are in README.Solaris. Ignore the part of it that says the aperture driver shouldn't be required in your situation. After the reconfiguration boot back into Solaris, but before starting the server, ensure that /dev/fbs/aperture exists and move (or rename) /dev/xsvc. Now start the server. I can't promise that this'll work, but if it does, you'll end up with a functional setup (and I have changes to make for the next release). If this doesn't work, it's likely Solaris clobbers the BIOS data the server needs, in which case changes to the int10 module will be needed to always re-initialise the adapter. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] SyncOnGreen for Sun 1662b fixed resolution monitor?
On 25 May 2004, Greg Stark wrote: Which drivers and cards are capable of sync on green and what do I need to achieve it? I've put the ``Option SyncOnGreen'' in the Monitor section. Do I need a separate csync option somewhere? Browsing the source it seems not every driver implements this. I have a choice of three graphics cards: :02:0b.0 Display controller: Texas Instruments TVP4010 [Permedia] (rev 01) :02:0a.0 VGA compatible controller: ATI Technologies Inc 3D Rage I/II 215GT [Mach64 GT] (rev 41) :01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 04) From the source it looks like the only one that actually implements SyncOnGreen is the MGA driver. That kind of sucks because I really don't want to give up the good graphics card for my main monitor. Is there any way to get sync on green using either of these other cards? Maybe a jumper? What other inexpensive cards that I might find in a bargain bin are capable of sync-on-green? As far as I know, no ATI adapter has hardware support for SOG. They all support composite sync however. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Problem setting up XFree86 in Debian
On Tue, 8 Jun 2004, Edward Hammerbeck wrote: Greetings. I am running the most recent stable Debian (3.0) on a Sparc Ultra 10 with all standard equipment. I'm having trouble getting X configured correctly, and I was hoping someone could give me a hand. I'm new to Linux and new to XFree86, so forgive my n00bness. I've attached my XFree86.log and Free86Config files. I'd appreciate any feedback you can offer. XFree86 4.1.0.1 is _much_ too old for this. Upgrade. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] XRecordQueryVersion Error
On Thu, 10 Jun 2004, Sachin Shah wrote:
I had written following code,
int Major, Minor ;
Display * LocalDpy = localDisplay ();
Display * RecDpy = localDisplay ();
int LocalScreen = DefaultScreen ( LocalDpy );
if ( ! XRecordQueryVersion (localDisplay (), Major, Minor ) )
{
QMessageBox::information(0,Error,XRecord extension not supported on
server, QMessageBox::Ok );
}
I got error :
undefined reference to `XRecordQueryVersion'
I had checked include file.. it's extern function..
So, for this extension, any more compiler option is required ???
-lXrender might be a good idea...
Marc.
+--+---+
| Marc Aurele La France | work: 1-780-492-9310 |
| Computing and Network Services | fax:1-780-492-1729 |
| 352 General Services Building | email: [EMAIL PROTECTED] |
| University of Alberta +---+
| Edmonton, Alberta | |
| T6G 2H1 | Standard disclaimers apply|
| CANADA | |
+--+---+
XFree86 developer and VP. ATI driver and X server internals.
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] [distro maintainer] sources packages, build and shared libraries
On Sat, 12 Jun 2004, cityhunter wrote: greetings I'm JL MALET and I'm one of the maintainers of sorecer linux distribution i'd like first to thank you for doing a such good job and as it seems it will continue ^_^ I hope that next releases will be as good as the planing. lets begin the real topic of this mail I'm a distro maintainer and this distro is sorcerer, which is a source compiled distro. as other packages XFree86 get compiled what sort out of 2 last year is some trouble because XFree86 provide some 3rd parties sources and compile them such sources are for exemple Xft, freetype what's wrong with this? lot trouble, not for me but for the users why? because XFree86 releases are far less often than the included package which means that a bug fix in Xft for exemple won't be provided to end user until XFree86 release. we can't provide both compile script without generating conflicts (compilation issues, problem related to the order of compilations) so we can't provide end user a bug free box so 1 possibilitie offers to us 1)wait for you folks to release this is troublesome. because the end user is always harmed in this case a mozilla that expect the Xft bug to be fixed will ever crash for 3-6 months. I wonder why you still provide such sources builtin since it's not a good practice : the right one used from nearly every opensources projects is to let the user get and compile the dependencies and then build the package (and since sorcery do the dependencies traking for us^_^) for you providing 3rd parties source means bandwidth consuming too so that's the main goal of this mail : isn't it impossible to split the sources so that 3rd parties project get independant and build separatly? for exemple a good choice sor my point of view could be : a package to provide core of X11 : servers, utils that are required to have the servers running (drivers, keymaps compilers...), that are provided by you a package to provide utils of X11 : xterms that is optional other packages as you want, each should be independant and self compilable 3rd parties sources aren't provided : Freetype or Xft for exemple shouldn't be included but listed on web site as requirements or options doing so will ensure a quality : every bugfix of 3rd parties are directly included when released... You can use the imake magic needed to build against the background libraries. I believe Gentoo does this. Doing this by default is no better than the current situation, as many systems do not provide the needed libraries. It would be better if imake were changed to be smarter about things like this. Patches welcome. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] vgabase
On Wed, 16 Jun 2004, Andrzej Popielewicz wrote: I am porting one of the older releases of XFree, namely 2.1. That's pretty old. Simple question : what is the meaning of VGABASE (defined as 0xf000 or 0xff00 depending on OS). vgaBase is the virtual address of memory mapped to VGA 0xa. vgaVirtBase is set to VGABASE for SVGA server (and to vgaBase for mono nonbanked) .Or in other words : how to set vgaVirtBase for SVGA ? VGABASE is a value used to distinguish between banked framebuffer data, and non-banked framebuffer data (or pixmap data). Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] 4.3-4.4 ATI Mach64 regression
On Mon, 14 Jun 2004, Amitai Schlair wrote: On a beige Power Macintosh G3 with ATI 3D Rage Pro video running NetBSD 2.0_BETA, XFree86 4.3 worked. XFree86 4.4 doesn't: ... (--) PCI:*(0:18:0) ATI Technologies Inc 3D Rage I/II 215GT [Mach64 GT] rev 154, Mem @ 0x8200/24, I/O @ 0x0400/8 ... (WW) ATI: PCI/AGP Mach64 in slot 0:18:0 could not be detected! As an experiment, I replaced ati_drv.o and atimisc.o with the versions from 4.3, and X worked again. More information: http://netbsd.schmonz.com/xf44-ati/XF86Config http://netbsd.schmonz.com/xf44-ati/pcictl-pci0-dump-18.txt http://netbsd.schmonz.com/xf44-ati/xf43-log.txt http://netbsd.schmonz.com/xf44-ati/xf44-log.txt http://netbsd.schmonz.com/xf44-ati/xf44-with-ati43-log.txt (FWIW, the 4.3 and 4.4 builds I'm using both came from NetBSD xsrc.) The same symptoms manifest with 4.4 on a Power Macintosh 6500 with very similar video, though I haven't tried the 4.3 ATI driver with that one yet. Is there more information I can provide? Ideas of things to try? I'm up for a binary search if that's what it takes, but would prefer to try something less time-consuming first if possible. :-) It would seem the 4.4 driver was mis-compiled. Please send me (privately) xc/programs/Xserver/hw/xfree86/drivers/ati/Makefile from your 4.4 build. Thanks. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Error message logs
On Tue, 15 Jun 2004, Bill Wise wrote: When I tried to start Yellow Dog Linux's GUI with the startx command from the command line (of course) I got an error message that suggested I send the log to you. There are several, so I send them all in hopes you'll be able to figure something out. I see no error in these logs. Please re-specify your query. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] 4.3-4.4 ATI Mach64 regression
On Mon, 21 Jun 2004, Amitai Schlair wrote: It would seem the 4.4 driver was mis-compiled. Please send me (privately) xc/programs/Xserver/hw/xfree86/drivers/ati/Makefile from your 4.4 build. Replying publicly as there's no Makefile in that directory. :-) The 4.4 build in which I saw this problem was cross-compiled using NetBSD's build system, from an i386 host for a macppc target. (NetBSD keeps XFree86 in xsrc, then has a shadow tree of Makefiles in src/x11. xsrc can be read-only, and mine is, so no Makefiles were made there. Then send me the corresponding Makefile in src/x11. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] vgabase
On Tue, 22 Jun 2004, Andrzej Popielewicz wrote: I am porting one of the older releases of XFree, namely 2.1. That's pretty old. Simple question : what is the meaning of VGABASE (defined as 0xf000 or 0xff00 depending on OS). vgaBase is the virtual address of memory mapped to VGA 0xa. vgaVirtBase is set to VGABASE for SVGA server (and to vgaBase for mono nonbanked) .Or in other words : how to set vgaVirtBase for SVGA ? VGABASE is a value used to distinguish between banked framebuffer data, and non-banked framebuffer data (or pixmap data). Are You sure ? VGABASE is used(in banked case) in different vgaSetReadWrite etc routines(usually in assembler) , in order to set the corresponding bank for given buffer pointer. It is treated as usual address(pointer)(?). Or You simply mean the same ? The question is not what VGABASE is good for, but why it is set to 0xf000 . VGABASE is a value that should never occur for a real framebuffer, banked or otherwise. I'll grant that VGABASE could have been set to the same value regardless of OS/architecture, and it was at one time. Over time, it was changed only for those situations where the original value isn't suitable, and it wasn't globally changed to prevent breaking what was already working. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] 4.3-4.4 ATI Mach64 regression
On Mon, 21 Jun 2004, Amitai Schlair wrote: Then send me the corresponding Makefile in src/x11. It's this one: http://cvsweb.netbsd.org/bsdweb.cgi/src/x11/Xserver/hw/xfree86/drivers/ati/Makefile?rev=1.3content-type=text/x-cvsweb-markup That Makefile is broken as it completely ignores architecture-specific flags setup by the Imakefile. Given that the driver works when compiled through imake (as intended), you should report this problem to the NetBSD folk who, for reasons of their own, decided to re-invent the wheel WRT how XFree86 is compiled. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Cannot run X on a ia64
On Thu, 1 Jul 2004, De Leeuw Guy wrote: Hello, I'm new on the list, and newbie with X. But I have a problem on a Bull novascale computer (ia64). I run rh AS2.1, no problems. I install debian-sarge-ia64 and cannot start X. The X server run, without errors but I have a black screen. I cannot use CTRL+ALT+BACKSPACE, only CTR+ALT+DEL work. I make a ssh connection to kill the startx process. I search from 3 days without succès, any idees are welcome. Thanks in advance, Guy The linux kernel is the 2.6.7 smp for ia64 Video card : ATI Match 64 Rage XL 16Mb Your system is based on Intel's E8870 motherboard chipset, support for which has yet to be written. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Cannot run X on a ia64
On Fri, 2 Jul 2004, De Leeuw Guy wrote: Le ven 02/07/2004 à 17:12, Marc Aurele La France a écrit : On Thu, 1 Jul 2004, De Leeuw Guy wrote: I'm new on the list, and newbie with X. But I have a problem on a Bull novascale computer (ia64). I run rh AS2.1, no problems. I install debian-sarge-ia64 and cannot start X. The X server run, without errors but I have a black screen. I cannot use CTRL+ALT+BACKSPACE, only CTR+ALT+DEL work. I make a ssh connection to kill the startx process. I search from 3 days without succès, any idees are welcome. The linux kernel is the 2.6.7 smp for ia64 Video card : ATI Match 64 Rage XL 16Mb Your system is based on Intel's E8870 motherboard chipset, support for which has yet to be written. May thanks for your respons. But why XFree 4.1 run on RH AS 2.1 and not on XFree 4.3 on debian ? You are running a much newer kernel on the debian system. If you downgrade to, say, 2.4.26, things would likely work again. Note that I am _not_ saying that this is a kernel problem. It's just that, over time, the kernel is becoming smarter about ACPI than the X server can currently handle. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] problem with displaying X on eOne
On Thu, 8 Jul 2004, Eric Franz wrote: With the console style, it fits the monitor perfectly, as well as the splash screen for grub, but when X starts, the video image is shifted to the left, and part of the screen is cut off...and there is a giant black bar along the right side of the screen. Also, the screen's height is smaller than what could fit the monitor. First, your log shows that you are being bitten by a bug found in the common layer's mode validation shortly after 4.3's release. The work-around is to specify, in your XF86Config, the virtual resolution you want, which, I assume, in this case would be 'Virtual 1024 768'. `man XF86Config` for placement. Secondly, it appears from your description that you are using the kernel's buggy atyfb to provide the non-X console. Switch to vesafb instead, or no fbcon at all. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] XFree86 verion 4.4 / Shared Libraries
On Thu, 8 Jul 2004, EXT-Holvenstot, Christopher wrote: I am currently one of a group of people who are charged with rehosting the International Space Station's PCS platform from an IBM 750XD ThinkPad running Solaris X86 2.5 to the newer IBM A31p ThinkPad running a stripped down version of Red Hat Linux 9.0. One of the ongoing minor problems we have had is that from time to time, when the display shifts from text mode to graphical mode (or back) it gets jumbled - sort of like the horizontal refresh rate is not detected correctly (if there is such a thing on a laptop's LCD screen) We have found that upgrading from the 4.3 version to the 4.4 version of XFree86 appears to remedy this problem. However, there is one minor issue that I am trying to deal with - the construction of a 4.4 RPM which will fit into our automated install process - all version 4.4 testing to date has been done using X installed using the XFree86 supplied install scripts and the requisite truckload of tgz files downloaded from the XFree86 website. I have downloaded and reviewed several version 4.4 RPM bundles, but they all seem to have one common issue - they require glibc to be at higher level than the version 2.3.2 we have. For us this is a major problem - we are so far along in getting our system qualified for manned space flight that there is major resistance to making any core system change. So, like a dummy, I decided to start down the road of building my own XFree86 4.4 RPM. For the most part this has gone OK - all of the required files arrear to end up in the right place. However, when you bring x up you get a number of messages saying that there was an error loading shared libraries - specifically libXmuu.so.1 and libX.so.6. I have verified that these files are actually on the system. If I come up in single user mode and manually start the configuration routine I do get the graphical screen with the X cursor. The files in question do reside in /usr/X11R6/lib - but this path does not show up in the path statement or in LD_LIBRARY_PATH on either a functional system, or the one that I built which is slightly less than functional. What am I missing here? Any suggestions? `man ldconfig`? But, perhaps, I'm stating the obvious... Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Mono LCD with 1BPP: Character Display Reversed!!
On Sun, 25 Jul 2004, Mark Vojkovich wrote: On Sun, 25 Jul 2004, Samuel Teng wrote: Please do help me!! I tried to run XFree86-4.2.0 on a Monochromonic LCD with 1BPP support. But the characters are displayed in a reversed style! For example, if the bitmap is 101, it will be displayed as 0101. What do you mean displayed reversed? If LSBFirst, then the LSB will be the leftmost pixel and the MSB will be the rightmost pixel. I have set the IMAGE_BYTE_ORDER and BITMAP_BIT_ORDER to LSBFirst. Then why it is reversed? Those are the settings for mfb. On ix86 (among others), IMAGE_BYTE_ORDER must be LSBFirst; BITMAP_BIT_ORDER, MSBFirst; and BITMAP_SCANLINE_UNIT 8, for 1bpp operation. This is all set up by the xf1bpp framebuffer. It therefore seems likely you are using the wrong framebuffer. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] (no subject)
On Wed, 21 Jul 2004, Nagaraju Pothineni only sent a log file. (EE) Problem description not found Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] How to set up two monitors with ATI Mach64 Rage Pro AGP and S3 Trio64V2 (fwd)
On Fri, 23 Jul 2004, A.Sulaiman wrote: I have spent over a week trying various XF86Config options, and have exhaustively searched the net to no avail. I look forward to any help on this problem. My system is a PIII-500 Dell Optiplex GX1 originally with just an on board ATI Mach64 (ATI|3D Rage Pro AGP 1X/2X, 8MB ) and runs a standard FedoraCore1 (fresh installation). Everything generally worked well (with lots of memory, fast disk, fvwm window manager, firefox and of course linux, the PIII is still as quick as the rest of them, even with scores of active windows). Due to an office move, I recently have to give up my 19 trinitron display on 1600x1200 to a 17 LCD which is limited to 1280x1024. A second LCD was available, so I added an old 2MB S3 Trio64V PCI card to attach it to. It immediately become the primary monitor. Dell BIOS have no option to switch the default monitor selection. This is a real bummer, as I cannot get the other LCD monitor attached to the ATI Mach64 to work, I am now restricted to just 1024x768 with the S3 Trio. There don't seem to be any problem with the h/w BIOS boot and linux initialisations in recognizing the two display cards. The snag seems to occur during XFree86 initialisation - the dreaded (EE) message. Note: I have attached both my XFree86.0.log XF86Config files in it's entirety. Here are some extracts from /var/log/XFree86.0.log: (**) ATI(1): Chipset: mach64. (**) ATI(1): Depth 16, (--) framebuffer bpp 16 (II) Loading sub module int10 (II) LoadModule: int10 (II) Reloading /usr/X11R6/lib/modules/linux/libint10.a (EE) ATI(1): Cannot read V_BIOS (WW) ATI(1): Unable to initialise int10 interface. (EE) ATI(1): Adapter has not been initialised. (II) UnloadModule: ati (II) UnloadModule: int10 (II) UnloadModule: atimisc (II) Unloading /usr/X11R6/lib/modules/drivers/atimisc_drv.o This is a system BIOS issue, a problem particularly common with Dell's lobotomised BIOSes. And there's very little the driver can do about it. Depending on your kernel, you _might_ be able to get past this point by configuring it to use atyfb to drive the Rage Pro. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] How to set up two monitors with ATI Mach64 Rage Pro AGP and S3 Trio64V2 (fwd)
On Tue, 27 Jul 2004, Jay R. Ashworth wrote: On Tue, Jul 27, 2004 at 08:16:32AM -0600, Marc Aurele La France wrote: This is a system BIOS issue, a problem particularly common with Dell's lobotomised BIOSes. And there's very little the driver can do about it. Depending on your kernel, you _might_ be able to get past this point by configuring it to use atyfb to drive the Rage Pro. Would it be practical to teach XFree to let the user lie to it, and pretend to be the BIOS? I know it would be another config file (or extension), but this seems a fairly common problem. Is the problem just that the BIOS won't tell X what it needs to know, or does it actively get in the way? Such things as video memory timing and the like are VERY adapter-specific, making it quite unrealistic for the driver to perform adapter initialisation. Thus the driver requires that the adapter be previously initialised or have a BIOS available. This is simply a consequence of ATI's adapter design and there's dick-all the driver can do about it. One could, I suppose, boot with the onboard adapter as primary, save its initialised BIOS somewhere, and have int10 use that copy in the multihead situation. But the code to do that (securely or not) just isn't there. Your options, at this point, are to talk to Dell (dead end), give up on the onboard adapter in multihead, replace your motherboard, or get a system that's not so broken. Or, as I suggested above, atyfb _might_ come in handy for a change. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] How to set up two monitors with ATI Mach64 Rage Pro AGP and S3 Trio64V2 (fwd)
On Wed, 28 Jul 2004, Asri Sulaiman wrote: Marc Aurele La France wrote: Your options, at this point, are to talk to Dell (dead end), give up on the onboard adapter in multihead, replace your motherboard, or get a system that's not so broken. Or, as I suggested above, atyfb _might_ come in handy for a change. I would like to try atyfb first. But please forgive my ignorance. What would be the best way to set it up? I found atyfb.o in /lib/modules/2.4.22-1.2115.nptl/kernel/drivers/video/aty modprobe atyfb seems ok at first, but system hang when I do init 3. Well, I did say atyfb _might_ work, not _would_ work. Put modprobe in rc.local, and it hang during boot. (Fortunately I found the install CD needed to do a rescue. A good side effect: it moved me to convert all my ext2 partition to ext3 so recovery would not be so long next time I hit reset) Adding Load atyfb in the XF86Config file, Section Module: it says module not found in XF86 log. Right. atyfb is a kernel module, not an XFree86 one. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Trouble with Start X on Red Hat Linux Advanced Server 2.1
On Tue, 3 Aug 2004, Aijaz Ahmed wrote: I have a Intel Itanium machine with Red Hat Linux Advance Server 2.1 installed on it. The VGA card is ATI RAGE XL. When I startx on this machine I get the following error. I will really appreciate any help on this. XFree86 Version 4.1.0 (Red Hat Linux release: 4.1.0-38) / X Window System (protocol Version 11, revision 0, vendor release 6510) Release Date: 2 June 2001 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/FAQ) Build Operating System: Linux 2.4.18-e.0.20smp ia64 [ELF] Build Host: boris.devel.redhat.com [...] (==) ATI(0): Chipset: ati. (**) ATI(0): Depth 16, (--) framebuffer bpp 16 (EE) ATI(0): Adapters found to be in VGA mode on server entry are not supported by the MMIO-only version of this driver. 1) The driver was miscompiled for this platform. 2) XFree86 4.1.0 is much too old for this to work anyway. 3) Double posting your query doesn't help. 4) Talk to RedHat. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] ATI NV cards Dual-head problem
On Wed, 1 Sep 2004 [EMAIL PROTECTED] wrote: Good morning to all. I can't get dual head mode working. It is funny to see what happens to me on the right screen so take a look. The e_mails content is over here: http://imp.homeunix.org/dual/en/ There are infos and log files. There have been a number of acceleration fixes for Mach64's since 4.2.1.1. Try upgrading. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Dual Screen not working, help?
On Tue, 24 Aug 2004, Tamas Hauer wrote: I am trying to start an X server with two screens on two VGA cards. Here they are: [EMAIL PROTECTED] root]# lspci | grep VGA 01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 Pro Ultra TF 02:01.0 VGA compatible controller: ATI Technologies Inc 264VT [Mach64 VT] (rev 40) (see the output of lspci -vv at : http://cern.ch/tamas.hauer/X/lspci) The interesing ( I think) part of XF86Config is below, (the whole thing is at: http://cern.ch/tamas.hauer/X/XF86Config.dual). For testing purposes, I define three layouts: Single, Second and Xine. These should start one screen on the first or the second monitor and the xinerama, respectively. Then I do: startx -- -xf86config XF86Config.dual -layout Single startx -- -xf86config XF86Config.dual -layout Second startx -- -xf86config XF86Config.dual -layout Xine The first two work as expected but the dual setup does not. In that case I get a single screen on my primary monitor (the one defined in Single) and nothing else. I would greatly appreciate any insight. The XFree logs are here: http://cern.ch/tamas.hauer/X/XFree86.0.log.Single http://cern.ch/tamas.hauer/X/XFree86.0.log.Second http://cern.ch/tamas.hauer/X/XFree86.0.log.Xine I tried various combinations of drivers (ati and vesa) for the two cards, no success Please post the output of `scanpci -v`, one run just after a power-down/reboot but before the X server starts. It seems your system BIOS is not allocating resources to the secondary adapter. If that's the case, you are very lucky that the VESA driver works at all. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Bug report
On Fri, 27 Aug 2004 [EMAIL PROTECTED] wrote: My X server worked well until I upgrated my kernel to Linux-2.6.8: It still works with kernels up to Linux-2.6.8-pre2, but crashes with segmentation-fault on any kernel from linux-2.6.8-pre3 onward. So far, this only happens on my AMD computer, and regardless of which video-card I use (I tried three different cards - two AGP and one PCI) and whether I configure the driver to be VESA or not, or even VGA. The exact same software however, works fine when being run on a Pentium-4. This first happened on XFree 4.3.0, so I just installed the latest XFree 4.4.0, but it makes no difference. I am using a plain kernel with no modules and no direct rendering, as I do not even require any fancy acceleration, just that I can get into graphics mode from time to time to view the web. Your /proc/cpuinfo indicates you have an Athlon64, but you are running an X server binary meant for i686's. That's not likely to work. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Bug report
On Sun, 5 Sep 2004 [EMAIL PROTECTED] wrote: My X server worked well until I upgrated my kernel to Linux-2.6.8: It still works with kernels up to Linux-2.6.8-pre2, but crashes with segmentation-fault on any kernel from linux-2.6.8-pre3 onward. So far, this only happens on my AMD computer, and regardless of which video-card I use (I tried three different cards - two AGP and one PCI) and whether I configure the driver to be VESA or not, or even VGA. The exact same software however, works fine when being run on a Pentium-4. This first happened on XFree 4.3.0, so I just installed the latest XFree 4.4.0, but it makes no difference. I am using a plain kernel with no modules and no direct rendering, as I do not even require any fancy acceleration, just that I can get into graphics mode from time to time to view the web. Your /proc/cpuinfo indicates you have an Athlon64, but you are running an X server binary meant for i686's. That's not likely to work. The question then is how could it work before? The Athlon64 is designed to be fully PC/x86-compatible: it works only in 32-bit mode unless one has a 64-bit operating system that turns on the appropriate hardware bits to make it a 64-bit machine - but I don't have such an operating system, so if the Athlon was operating in 64-bit mode I could not even boot. The fact is that the exact same program (the X server) and its supporting files, running on exactly the same hardware, was fully functional under the Linux-2.6.8-pre2 and earlier kernels and crash under kernels from Linux-2.6.8-pre3 onward, so it must be either a newly introduced kernel bug, or an old bug in the X server making wrong assumptions about some unpromised kernel behaviour. Perhaps it would help if I could lay my hands on a binary version of the X program that has more debug information that I can present to this list. Fair enough. I've looked into this a bit more. Please try the attached source patch. It assumes that the problem is due to pre3's mmap() changes. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. Amd64Loader.diff.gz Description: Binary data
Re: [XFree86] Bug report
On Wed, 8 Sep 2004 [EMAIL PROTECTED] wrote: Fair enough. I've looked into this a bit more. Please try the attached source patch. It assumes that the problem is due to pre3's mmap() changes. Thank you very much - this worked! PS. I hope this fix will be included in future XFree86 releases. You're welcome. I've just committed this. Thanks for doing such a stellar job at narrowing down the kernel version that uncovered the problem. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] V4.4.99.12 Compile error - BUSmemcpy - unknown flag unknown opt ion -- Solaris 8
On Wed, 8 Sep 2004, Otten, Dave (Mission Systems) wrote: Attempting to compile v4.4.99.12 on Solaris 8 using gcc, resulted in unknown flag -$ -- see below: (output from make World log) rm -f xf86_IlHack.o gcc -c -O2 -fno-strength-reduce -DNO_ASM -Wall -Wpointer-arith -Wundef -I../../../../../../programs/Xserver/hw/xfree86/common -I../../../../../../programs/Xserver/hw/xfree86/os-support -I. -I../../../../../../programs/Xserver/include -I../../../../../../exports/include/X11 -I../../../../../.. -I../../../../../../exports/include -Dsun -Di386 -DSVR4 -D__EXTENSIONS__ -D__i386 -DSHAPE -DXINPUT -DXKB -DLBX -DXAPPGROUP -DXCSECURITY -DTOGCUP -DXF86BIGFONT -DDPMSExtension -DPIXPRIV -DPANORAMIX -DRENDER -DRANDR -DAVOID_GLYPHBLT -DPIXPRIV -DSINGLEDEPTH -DXFreeXDGA -DXvExtension -DXFree86LOADER -DXFree86Server -DXF86VIDMODE -DXvMCExtension -DSMART_SCHEDULE -DBUILDDEBUG -DXResExtension -DX_BYTE_ORDER=X_LITTLE_ENDIAN -D__SOL8__ -DNDEBUG xf86_IlHack.c rm -f BUSmemcpy.i /usr/ccs/lib/cpp -Dsun -Di386 -DSVR4 -D__EXTENSIONS__ -D__i386 -$ -I../../../../../../programs/Xserver/hw/xfree86/common -I../../../../../../programs/Xserver/hw/xfree86/os-support -I. -I../../../../../../programs/Xserver/include -I../../../../../../exports/include/X11 BUSmemcpy.S | \ grep -v '^\#' BUSmemcpy.i unknown flag -$ rm -f BUSmemcpy.o /usr/ccs/bin/as -xarch=v8plus -o BUSmemcpy.o BUSmemcpy.i Assembler: , line 1 : -xarch=v8plus unknown option *** Error code 127 make: Fatal error: Command failed for target `BUSmemcpy.o' Current working directory /usr/xc/programs/Xserver/hw/xfree86/os-support/misc *** Error code 1 make: Fatal error: Command failed for target `misc' Current working directory /usr/xc/programs/Xserver/hw/xfree86/os-support *** Error code 1 make: Fatal error: Command failed for target `all' Current working directory /usr/xc/programs/Xserver/hw/xfree86 *** Error code 1 make: Fatal error: Command failed for target `hw/xfree86' Current working directory /usr/xc/programs/Xserver *** Error code 1 make: Fatal error: Command failed for target `all' Current working directory /usr/xc/programs *** Error code 1 make: Fatal error: Command failed for target `all' Current working directory /usr/xc *** Error code 1 make: Fatal error: Command failed for target `World' Current working directory /usr/xc *** Error code 1 make: Fatal error: Command failed for target `World' Please read README.Solaris more carefully. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] system always crashed when using Xfree86(on notebook)
On Thu, 9 Sep 2004, yancl wrote: sorry for boring you but i have no other choice :(,i had reinstalled Freebsd(5.2.1released) several times for this problem,almost every time i run starx it will cause crashed of the system,i must cut the power,strip down the battery,for restart the system. for the first time,i install kdegnome but you know it won't work,then i reinstall system and do nothing but configure the Xfree86,i tried 4.3.0,and 4.4.0 but all didn't work,my card is ATI LT pro,there is no problem with the hardware,because when i had despaired i juse install the windowsXP to test if the hardware is something wrong,but it works good, i'm so sad and can't bear it,i really like freebsd and want to use it on my work,i didn't use the stable version under 5.X,because my Ethernet card is CardBus which just supported by 5.x , every time i just generate the XFree86Config.new file ,and run XFree86 -xf86config /root/XF86Config.new to test ,it will crashed.:( and no log file,below is the file named XFree86.0.log.old placed at /var/log/,maybe useful . Please attach the output of 4.4's `scanpci -v -v -V 3` run on this machine before an attempt to run the X server. Thanks. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Strange X Lockup problem with Xinerama - take 2
On Mon, 20 Sep 2004, Phil Dibowitz wrote:
I've been dealing with a strange X-locking problem for quite some time. I've
been trying to gather information, and I think I've gathered about as much as
I can. The problem only occurs when using Xinerama.
SYMPTOM:
If I go to certain web pages in firefox or mozilla, and then click on a link,
it will cause X to go unresponsive. The x server goes into a loop of:
select(256, [1 3 4 5 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
27 28 29 30 31], NULL, NULL, {103, 371000}) =3D 1 (in [26], left {103,
356000})
read(26, [EMAIL PROTECTED]@[EMAIL PROTECTED]..., 4096)
= 80
read(26, 0x856ecc0, 4096) =3D -1 EAGAIN (Resource temporarily unavailable)
gettimeofday({1094757921, 253529}, NULL) = 0
select(256, [1 3 4 5 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
27 28 29 30 31], NULL, NULL, {103, 356000}) = ? ERESTARTNOHAND (To be
restarted)
Firefox or mozilla are just sitting in a poll.
At this point my mouse can move, but no windows accept input. Focus does not
change, typing doesn't work, numlock/capslock won't work, ctrl-alt-backspace
won't work, etc.
Perhaps we can nail down what firefox/mozilla is repeatedly requesting. What
does `xdpyinfo -queryExtensions` say?
Marc.
+--+---+
| Marc Aurele La France | work: 1-780-492-9310 |
| Computing and Network Services | fax:1-780-492-1729 |
| 352 General Services Building | email: [EMAIL PROTECTED] |
| University of Alberta +---+
| Edmonton, Alberta | |
| T6G 2H1 | Standard disclaimers apply|
| CANADA | |
+--+---+
XFree86 developer and VP. ATI driver and X server internals.
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Strange X Lockup problem with Xinerama - take 2
On Mon, 20 Sep 2004, Phil Dibowitz wrote: On Mon, Sep 20, 2004 at 03:13:40PM -0600, Marc Aurele La France wrote: Perhaps we can nail down what firefox/mozilla is repeatedly requesting. What does `xdpyinfo -queryExtensions` say? I'm assuming this wouldn't change when X freezes? Under that assumption, this is from X not frozen: Thanks, this helps muchly. The only reason I can think of that this output would not correspond to that of the looping server would be extensions being initialised in a different order, a situation I see as highly unlikely, if at all possible. On the assumption that this xdpyinfo output is in fact relevent, then your server strace shows, among other things, two client connections repeatedly calling XShmPutImage(), to which the server never replies (with success or failure). At this point, I don't really know whether it's relevent to the problem that there are two such connections, nor whether the lack of server response is normal XShmPutImage() behaviour for this case. For the latter, I'd like you to capture another server strace, this one without Xinerama and as near as possible to the scenario that would cause the Xinerama loop. Please take care to not delete the original strace's you've made available through your web site. If this non-hang strace shows a server response to the client's XShmPutImage() (or some other server behaviour), then there's likely something amiss with xc/programs/Xserver/Xext/shm.c's ProcPanoramiXShmPutImage(), perhaps with its handling of sendEvent, at which point I'd ask Mark, one with more knowledge of Xinerama internals than me, to investigate further. The server strace also shows -- and this might be a red herring -- a number of client connections making XCreateColormap() calls. Some of these are being accepted by the server, but most are being nixed, presumably due to VisualID settings/differences. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Is there a man page for the s3 driver in 4.4.0?
On Mon, 20 Sep 2004, Steve Kleiser wrote: http://www.xfree86.org/4.4.0/manindex4.html lists a man page for s3 virge, but not for other chip sets (in my case, Vision 968 on a Stealth64 VRAM PCI). I can load the module s3 if I specify it explicitly, but have not yet been able to configure it. Is the 3.3.6 documentation still applicable? I've also tried starting Xfree86 w/o any config file to let the server auto-configure, but to no avail. The resulting log file from that particular attempt is attached. The video card seems to appear at multiple bus addresses (and on buses 0, 64, and 65?). The lspci command shows the chip/card at PCI:0:6:0, which is the first of the probe results, but that doesn't appear to get chosen as primary. And what are all those other probe results anyway? I don't really see how these ghost devices could still be detected. Can you build from source? There're a few things I'd like you to try. Thanks. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Strange X Lockup problem with Xinerama - take 2
On Wed, 22 Sep 2004, Mark Vojkovich wrote: On Wed, 22 Sep 2004, Marc Aurele La France wrote: On Mon, 20 Sep 2004, Phil Dibowitz wrote: On Mon, Sep 20, 2004 at 03:13:40PM -0600, Marc Aurele La France wrote: Perhaps we can nail down what firefox/mozilla is repeatedly requesting. What does `xdpyinfo -queryExtensions` say? I'm assuming this wouldn't change when X freezes? Under that assumption, this is from X not frozen: Thanks, this helps muchly. The only reason I can think of that this output would not correspond to that of the looping server would be extensions being initialised in a different order, a situation I see as highly unlikely, if at all possible. On the assumption that this xdpyinfo output is in fact relevent, then your server strace shows, among other things, two client connections repeatedly calling XShmPutImage(), to which the server never replies (with success or failure). At this point, I don't really know whether it's relevent to the problem that there are two such connections, nor whether the lack of server response is normal XShmPutImage() behaviour for this case. For the latter, I'd like you to capture another server strace, this one without Xinerama and as near as possible to the scenario that would cause the Xinerama loop. Please take care to not delete the original strace's you've made available through your web site. If this non-hang strace shows a server response to the client's XShmPutImage() (or some other server behaviour), then there's likely something amiss with xc/programs/Xserver/Xext/shm.c's ProcPanoramiXShmPutImage(), perhaps with its handling of sendEvent, at which point I'd ask Mark, one with more knowledge of Xinerama internals than me, to investigate further. My Xinerama system stays up for weeks on end and I spend alot of time using Mozilla and Netscape. Perhaps one of these new apps is using RENDER and it's something related to that? If there was a fundamental bug in shm's Xinerama support I would have expected somebody to find it long ago. That code is many years old and I'm not aware of any outstanding bugs. It seems more likely that there is some new extension usage going on, and that extension has some Xinerama issues. The strace doesn't show any other extension being involved. IOW, there is no call to feel defensive about this. The facts will speak for themselves. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Strange X Lockup problem with Xinerama - take 2
On Wed, 22 Sep 2004, Marc Aurele La France wrote: On Wed, 22 Sep 2004, Mark Vojkovich wrote: On Wed, 22 Sep 2004, Marc Aurele La France wrote: On Mon, 20 Sep 2004, Phil Dibowitz wrote: On Mon, Sep 20, 2004 at 03:13:40PM -0600, Marc Aurele La France wrote: Perhaps we can nail down what firefox/mozilla is repeatedly requesting. What does `xdpyinfo -queryExtensions` say? I'm assuming this wouldn't change when X freezes? Under that assumption, this is from X not frozen: Thanks, this helps muchly. The only reason I can think of that this output would not correspond to that of the looping server would be extensions being initialised in a different order, a situation I see as highly unlikely, if at all possible. On the assumption that this xdpyinfo output is in fact relevent, then your server strace shows, among other things, two client connections repeatedly calling XShmPutImage(), to which the server never replies (with success or failure). At this point, I don't really know whether it's relevent to the problem that there are two such connections, nor whether the lack of server response is normal XShmPutImage() behaviour for this case. For the latter, I'd like you to capture another server strace, this one without Xinerama and as near as possible to the scenario that would cause the Xinerama loop. Please take care to not delete the original strace's you've made available through your web site. If this non-hang strace shows a server response to the client's XShmPutImage() (or some other server behaviour), then there's likely something amiss with xc/programs/Xserver/Xext/shm.c's ProcPanoramiXShmPutImage(), perhaps with its handling of sendEvent, at which point I'd ask Mark, one with more knowledge of Xinerama internals than me, to investigate further. My Xinerama system stays up for weeks on end and I spend alot of time using Mozilla and Netscape. Perhaps one of these new apps is using RENDER and it's something related to that? If there was a fundamental bug in shm's Xinerama support I would have expected somebody to find it long ago. That code is many years old and I'm not aware of any outstanding bugs. It seems more likely that there is some new extension usage going on, and that extension has some Xinerama issues. The strace doesn't show any other extension being involved. IOW, there is no call to feel defensive about this. The facts will speak for themselves. I think I might have located the problem. The server is not reporting the correct drawable in a completion event requested by an Xinerama-fied XShmPutImage request. The attached is a possible fix for that. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. shm.diff.gz Description: Binary data
Re: [XFree86] XFree86 makefiles, gcc and stdin. gcc: no input files
On Fri, 24 Sep 2004, Michael Shell wrote: I have run into a curious issue when trying to build XFree86 (4.4.0 or 4.4.99.13) from source on my i586 Linux system. I have the sinking feeling that it is an easy problem with an obvious solution, but one that somehow eludes me. The symptoms are bizarre. After compilation (apparently without errors) and installation (make World, make install, make install.man), several key installed files have zero length - the most critical of which is startx. If the empty startx is replaced with a valid script, X windows can be started, but xrdb is inoperative, and some applications (e.g., xmms) will have jerky screen updates - which apparently is caused by the fact that /etc/X11/locale/locale.dir is empty. Some man pages are also empty (e.g., /usr/X11R6/man/man1/Xnest.1x has a zero file length). Acting on the assumption that all these problems are related, I decided to start by tracking down what was causing the empty Xnest man page. In my build directory (buildxc), the Makefile (in buildxc/programs/Xserver/hw/xnest) contains (around line 1060): Xnest.$(MANNEWSUFFIX):: Xnest.$(MANSRCSUFFIX) $(RM) $@ sed -e 's/\\$$/\\ /' Xnest.$(MANSRCSUFFIX) | $(RAWCPP) $(MANDEFS) $(EXTRAMANDEFS) | sed -e '/^# ... (I have removed the tabs and truncated this very long line for readability). Now, on my system with my own custom host.def (email me if you need to see this), the xnest.man build line becomes: sed -e 's/\\$/\\ /' Xnest.man | gcc -march=i586 -pipe -E -undef -traditional ... which FAILS with error gcc: no input files. Unfortunately, compilation does not stop with this error and the resulting Xnest._man output is empty. Custom host.def indeed. Setting CppCmd to gcc anything is incorrect. Let it default to /lib/cpp, or simply cpp. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Strange X Lockup problem with Xinerama - take 2
On Fri, 24 Sep 2004, Mark Vojkovich wrote: I think I might have located the problem. The server is not reporting the correct drawable in a completion event requested by an Xinerama-fied XShmPutImage request. The attached is a possible fix for that. That works, but I think there's just a typo in the original code that keeps it from working the way it was intended. FOR_NSCREENS should have been FOR_NSCREENS_BACKWARD. The idea was that it counts down and sends the event on the last one (index zero) which had the correct drawable. Alot of functions use the BACKWARD version for this an similar reasons. OK, thanks. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Strange X Lockup problem with Xinerama - take 2
On Sat, 25 Sep 2004, Phil Dibowitz wrote: I think I might have located the problem. The server is not reporting the correct drawable in a completion event requested by an Xinerama-fied XShmPutImage request. The attached is a possible fix for that. That works, but I think there's just a typo in the original code that keeps it from working the way it was intended. FOR_NSCREENS should have been FOR_NSCREENS_BACKWARD. The idea was that it counts down and sends the event on the last one (index zero) which had the correct drawable. Alot of functions use the BACKWARD version for this an similar reasons. OK, thanks. There are two instances of FOR_NSCREENS in the original code -- which one is supposed to be changed? The one in ProcPanoramiXShmPutImage(). And are you saying that changing FOR_NSCREENS will fix the problem alone, or that the patch is also needed? The strace doesn't show enough of each packet read by the server to know for certain if the application requested events in its original XShmPutImage(), so I don't know for certain that this will fix the problem. But the fix is a definite candidate. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] ATI Rage Mobility AGP 2x with XFree86 4.4
On Wed, 13 Oct 2004 [EMAIL PROTECTED] wrote: The XF86Config is attached for reference. I am using FreeBSD 5.3 and trying to install XFree86 4.4. I currently am running XFree86 4.3 (so I can write this email :) The attached file works and has worked with 4.0 - 4.3 of XFree86. On 4.4 starting xdm yields a black screen with no errors logged to /var/log/XFree86.0.log. xdm starts and can be canceled. The hardware is a Dell Inspiron 7500 circa 10/99. The problem seems to track the ATI Rage Mobility card as another FreeBSD user with the same card on an IBM ThinkPad is having the same symptoms. From pciconf -lv: [EMAIL PROTECTED]:0:0: class=0x06 card=0x chip=0x71908086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = '82443BX/ZX 440BX/ZX CPU to PCI Bridge (AGP Implemented)' class= bridge subclass = HOST-PCI : [EMAIL PROTECTED]:0:0: class=0x03 card=0x009e1028 chip=0x4c4d1002 rev=0x64 hdr=0x00 vendor = 'ATI Technologies' device = '01541014 Rage P/M Mobility AGP 2x' class= display subclass = VGA Is this a know problem? I could not find it in the active bug list. Any work around-s? This should be fixed as of 4.4.99.7, specifically CHANGELOG #133. There are no workarounds. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Strange X Lockup problem with Xinerama - take 2
On Tue, 28 Sep 2004, Phil Dibowitz wrote: On Sat, Sep 25, 2004 at 07:14:14PM -0600, Marc Aurele La France wrote: There are two instances of FOR_NSCREENS in the original code -- which one is supposed to be changed? The one in ProcPanoramiXShmPutImage(). Okay, I tried _just_ this change and I still can reproduce the lockup (I found another site that reliable does it). That site being Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Multihead setup: ATI 3D Rage P/M Mobility AGP 2x and Xinerama
On Mon, 8 Nov 2004, Tristan Miller wrote: I am trying to set up a multihead display with the Xinerama extensions to XFree86 4.3.0.1 on GNU/Linux (SuSE 9.0). I have a Sony Vaio laptop with a 3D Rage P/M Mobility AGP 2x video card. I know that this video card is capable of dual display mode as I've got it working with Windows XP. I also have no problem running single displays either on the built-in LCD or on the external monitor (or on both, but of course in that case both monitors display the same thing rather than separate desktops). I understand that for multiheaded video cards, the XF86Config file must be set up with two Monitor and two Screen sections, one for each monitor, and also two separate but nearly identical Device sections. If the video card has two separate BusIDs (as revealed by /proc/pci), then each Device section must specify a unique BusID. However, if the video card has a single BusID, then the line Screen 0 should be added to the first Device section, and Screen 1 to the second. (Sources: http://www.kclug.org/pipermail/kclug/2002-September/010412.html and http://freedesktop.org/bin/view/XOrg/FAQMiscellaneous#How_do_I_set_up_a_multihead_conf.) My video card has only one entry in /proc/pci: Bus 1, device 0, function 0: VGA compatible controller: ATI Technologies Inc Rage Mobility P/M AGP 2x (rev 100). IRQ 5. Master Capable. Latency=66. Min Gnt=8. Non-prefetchable 32 bit memory at 0xe900 [0xe9ff]. I/O at 0x9000 [0x90ff]. Non-prefetchable 32 bit memory at 0xe810 [0xe8100fff]. Therefore I set up my XF86Config file with the Screen 0/Screen 1 variant. However, when I try to test the configuration, I get the following error message (extracted from the log file /var/log/Xorg.0.log): (II) LoadModule: ati (II) Loading /usr/X11R6/lib/modules/drivers/ati_drv.o (II) Module ati: vendor=The XFree86 Project compiled for 4.2.0, module version = 6.4.7 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.5 (II) v4l driver for Video4Linux (II) ATI: ATI driver (version 6.4.7) for chipsets: ati, ativga (II) R128: Driver for ATI Rage 128 chipsets: ATI Rage 128 RE (PCI), ATI Rage 128 RF (AGP), ATI Rage 128 RG (AGP), ATI Rage 128 RK (PCI), ATI Rage 128 RL (AGP), ATI Rage 128 SM (AGP), ATI Rage 128 Pro PD (PCI), ATI Rage 128 Pro PF (AGP), ATI Rage 128 Pro PP (PCI), ATI Rage 128 Pro PR (PCI), ATI Rage 128 Pro ULTRA TF (AGP), ATI Rage 128 Pro ULTRA TL (AGP), ATI Rage 128 Pro ULTRA TR (AGP), ATI Rage 128 Mobility LE (PCI), ATI Rage 128 Mobility LF (AGP), ATI Rage 128 Mobility MF (AGP), ATI Rage 128 Mobility ML (AGP) (II) RADEON: Driver for ATI Radeon chipsets: ATI Radeon QD (AGP), ATI Radeon QE (AGP), ATI Radeon QF (AGP), ATI Radeon QG (AGP), ATI Radeon VE QY (AGP), ATI Radeon VE QZ (AGP), ATI Radeon Mobility LW (AGP), ATI Radeon Mobility LY (AGP), ATI Radeon Mobility LZ (AGP), ATI Radeon 8500 QL (AGP), ATI Radeon 8500 BB (AGP), ATI Radeon 7500 QW (AGP) (II) Primary Device is: PCI 01:00:0 (II) ATI: Candidate Device section Rage Mobility 1. (II) ATI: Candidate Device section Rage Mobility 0. (II) ATI: Shared PCI/AGP Mach64 in slot 1:0:0 detected. (EE) ATI: XF86Config Device sections Rage Mobility 1 and Rage Mobility 0 may not be assigned to the same adapter. (EE) No devices detected. The message strikes me as fairly clear. This isn't supported. If you want to know why, search the devel@ archives. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Multihead setup: ATI 3D Rage P/M Mobility AGP 2x and Xinerama
On Mon, 8 Nov 2004, Tristan Miller wrote: On Monday 08 November 2004 16:37, Marc Aurele La France wrote: (EE) ATI: XF86Config Device sections Rage Mobility 1 and Rage Mobility 0 may not be assigned to the same adapter. (EE) No devices detected. The message strikes me as fairly clear. This isn't supported. If you want to know why, search the devel@ archives. I did search them, but couldn't find anything addressing this problem. Searching for the name of my video card or for the may not be assigned to the same adapter message didn't produce any useful results; the former just had something about 2D acceleration. If you're aware of a relevant thread, could you please post a link or suggest some alternative keywords I could try for a search? Well, after some digging, your best bet is probably ... http://xfree86.desiato.de/xfree86/pipermail/xpert/2000-August/000715.html This doesn't reference exactly the same problem, but it is related in the sense that what you are talking about also involves the driver's current (in-)ability to manage two CRTCs. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] difficulties configuring after upgrade
On Fri, 12 Nov 2004, damon fasching wrote: I have just upgraded my Linux distribution, which included an upgrade of the XFree86 version. I've been mucking around with my configuration file for a couple of days with no luck. Here are my system details: XFree86 version: 4.3.0 OS: debian gnu linux kernel 2.4.27 monitor: Viewsonic P220f video card: Diamond Fire GL Pro 100 (pretty old video card) lspci has the line: VGA compatible controller: Texas Instruments TVP4020 [Permedia 2] (rev 01) I've attached three files. 1) /var/log/XFree86.0.log 2) XF86Config-4: My current configuration file. 3) XF86Config_old: The configuration which worked with the earlier version of XFree86 I was using. I've messed around a lot with the depth parameter, based on the error message I was getting. I'm pretty sure the driver I was using before was 'vga'. That is the driver I was using when the attached XFree86.0.log was generated. When things weren't working, out of paranoia, I tried every available xserver. Almost all of them failed with no devices detected...no surprises there. A couple of them, 'generic' and 'glint', gave the errors Given depth (32) is not supported by this driver and Screen(s) found, but none have a usable configuration The 'vesa' and 'vga' drivers both gave the same error messages, those in the attached log file: Weight given (000) is inconsistent with the depth (32) and Screen(s) found, but none have a usable configuration In the configuration I used with the older version of XFree86, ColorDepth of 32 worked fine. I also had 'accel' as the driver. I don't think 'vga' is one of the 'accel' drivers, but am not sure about that. I don't know what to try nextany ideas? Your XF86Config's default depth is invalid. Specify 24 instead of 32. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] feature requests
On Fri, 19 Nov 2004, Michael Hamilton wrote: Is there a place to submit feature requests? You can submit them as new requests in the Bugzilla at bugs.xfree86.org. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Documentation of the RAC
On Fri, 26 Nov 2004, Matrix wrote: You would know to inform some site to me where I can find documentation on the RAC (Resource Access Control) ? There is some documentation in xc/programs/Xserver/hw/xfree86/RAC.Notes in the source. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Documentation of the RAC
On Fri, 26 Nov 2004, Matrix wrote: You would know to inform some site to me where I can find documentation on the RAC (Resource Access Control) ? There is some documentation in xc/programs/Xserver/hw/xfree86/RAC.Notes in the source. Would have some another documentation more complete of this subject that you knows? Well, there are various odds ends in DESIGN and Domain.note, but aside from the source itself, that's about it. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] XFree86-4.4.0 Build On Solaris-8/SPARC [Configuration Problem]
On Fri, 26 Nov 2004, ASIF IQBAL wrote: i am trying to bring up XFree86-4.4.0 on solaris-8/SPARC. I have built the XFree86 source on solaris 8/SPARC, during which i have done the following. 1. Edited #define BuildXFree86OnSparcSunOS YES #define ThreadedX NO in xc/programs/Xserver/hw/xfree86/etc/bindist/Solaris/host.def 2. Copy host.def as cp xc/programs/Xserver/hw/xfree86/etc/bindist/Solaris/host.def xc/config/cf/ 3. vi config/imake/Makefile.ini change CC = gcc PREPROCESS_CMD = gcc -E 4. make World World.log 21 tail -f World.log During building i got the error in xc/programs/glxinfo/ directory that __eprintf: symbol referencing error. for that change CC=g++ in Makefile of glxinfo directory. then again i build it with just make. got an error of png.h not found. For that install libpng and build once again. After building, i installed the binaries by the command make install then while i try to configure by XFree86 -configure i got the following error log. can anybody give me the solution for this?... [...] (WW) xf86LinearVidMem: failed to open /dev/fbs/aperture (No such file or directory) (WW) xf86LinearVidMem: either /dev/fbs/aperture or /dev/xsvc device driver required (WW) xf86LinearVidMem: linear memory access disabled Read these. Then follow that up with README.Solaris. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: Re: [XFree86] XFree86-4.4.0 Build On Solaris-8/SPARC [Configuration Problem]
On Sat, 27 Nov 2004, ASIF IQBAL wrote: On Fri, 26 Nov 2004 Marc Aurele La France wrote : On Fri, 26 Nov 2004, ASIF IQBAL wrote: i am trying to bring up XFree86-4.4.0 on solaris-8/SPARC. I have built the XFree86 source on solaris 8/SPARC, during which i have done the following. 1. Edited #define BuildXFree86OnSparcSunOS YES #define ThreadedX NO in xc/programs/Xserver/hw/xfree86/etc/bindist/Solaris/host.def 2. Copy host.def as cp xc/programs/Xserver/hw/xfree86/etc/bindist/Solaris/host.def xc/config/cf/ 3. vi config/imake/Makefile.ini change CC = gcc PREPROCESS_CMD = gcc -E 4. make World World.log 21 tail -f World.log During building i got the error in xc/programs/glxinfo/ directory that __eprintf: symbol referencing error. for that change CC=g++ in Makefile of glxinfo directory. then again i build it with just make. got an error of png.h not found. For that install libpng and build once again. After building, i installed the binaries by the command make install then while i try to configure by XFree86 -configure i got the following error log. can anybody give me the solution for this?... [...] (WW) xf86LinearVidMem: failed to open /dev/fbs/aperture (No such file or directory) (WW) xf86LinearVidMem: either /dev/fbs/aperture or /dev/xsvc device driver required (WW) xf86LinearVidMem: linear memory access disabled Read these. Then follow that up with README.Solaris. Thanks for your valuable information. I am able to install the aperture driver according to README under aperture/README. The driver compiled for 64 bit and there was no issue with adding the driver. I have confirmed the driver installation with modinfo | grep aperture. But after this step when I tried once again, XFree86 -configure the system hangs. The last line of then console output as follows. (==) Log file: /var/log/XFree86.0.log, Time: Fri Nov 26 16:50:37 2004 Then I restarted the system, and when I checked XFree86.0.log, I could not see any messages. Am I missing still any configuration steps. Can this error be associated with (WW) xf86LinearVidMem: linear memory access disabled. Can you explain possible reasons for this error. Did I miss any specific configuration during building. If /dev/fbs/aperture still does not exist on your system, then either you did not do a reconfigure boot (a simple reboot won't suffice), or it failed for some reason. Check /var/log/messages. Also, if you used gcc to generate the aperture driver, ensure its version is 3.2 or later. Earlier gcc's simply won't work. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: Re: Re: [XFree86] XFree86-4.4.0 Build On Solaris-8/SPARC [Configuration Problem]
On Sat, 27 Nov 2004, ASIF IQBAL wrote: If /dev/fbs/aperture still does not exist on your system, then either you did not do a reconfigure boot (a simple reboot won't suffice), or it failed for some reason. After installing the aperture driver I performed touch /reconfigure followed by a init 6 as specified in README. And also after reboot I confirmed the existence of /dev/fbs/aperture in the system. Then I issued the command to configure XFree86 using XFree86 -configure which resulted in a system hang. I power-cycled the system and checked the /var/log/messages, couldn't see any messages. How can I confirm that my aperture driver is working fine ? And I am not getting the reason for system hang when I ran XFree86 -configure. Am I missing any other configuration ?... Also, if you used gcc to generate the aperture driver, ensure its version is 3.2 or later. Earlier gcc's simply won't work. My gcc version is 3.4.2 and version details are bash-2.03# gcc -v Reading specs from /usr/local/lib/gcc/sparc-sun-solaris2.8/3.4.2/specs Configured with: ../configure --with-as=/usr/ccs/bin/as --with-ld=/usr/ccs/bin/ld --disable-nls Thread model: posix gcc version 3.4.2 My system configuration is $uname -a SunOS testhost 5.8 Generic_108528-13 sun4u sparc SUNW,Sun-Blade-100 The only possible explanation for this behaviour that I can think of right now is that this system contains one or more SBUS or UPA display adapter(s). Only PCI display adapters are known to work in the UltraSPARC/SunOS port. Although I'm working to correct that, that code just isn't ready yet. Move /usr/X11R6/lib/modules/drivers/sun*_drv.o elsewhere, and retry `XFree86 -configure` Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] 4.4.0/32 bit/64 bit/protocol not supported
On Sun, 28 Nov 2004, Michael Albert wrote: I just installed XFree86-4_4_0 from source on an AMD running Linux 2.6.8.1/SMP (gcc-3.4.2, Suse 9.1). After make World/make install the desktop seemed a little slow starting, so I ran ldconfig and rebooted. Now, all 64-bit applications run O.K., and so do non-X-windows 32-bit applications. However, 32-bit X-windows applications fail with: Xlib: connection to :0.0 refused by server Xlib: Protocol not supported by server Error: Can't open display: :0.0 Many libraries in /usr/X11R6/lib64 were rebuilt, but none, as far as I can tell, in /usr/X11R6/lib, where the 32-bit libraries are. Any suggestions? Can I induce the build process to rebuild the 32-bit libraries? Why is this necessary--if the protocol is through a socket/pipe, why should the libraries need to updated? Isn't the protocol supposed to be independent of this, or is there some sort of accelerated protocol that is being used by default which requires fine-tuned consistency? I haven't built the tree on this architecture yet, but the build system does have the ability to generate libraries against multiple libc ABI's. I don't know whether the x86_64 build takes avantage of this by default, but it is certainly possible to make it do so. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] XFree86-4.4.0 Build On Solaris-8/SPARC [Configuration Problem]
each time after performing any changes in the source I do make followed by make install which actually takes lot of time. For this particular problem, it would be easier to work the `scanpci` utility. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] [XFree86 on Solaris/X86] (EE) GLINT(1): Cannot read V_BIOS(3)
On Tue, 30 Nov 2004, asif iqbal wrote: I am trying to bring up my Permedia card on PCI by XFree86-4.4.0 on Solaris-8/X86. At first I have configured XFree86 only with SIS card, and it worked fine. Then while I tried to configure both SIS and Permedia cards together by the command XFree86 -configure, the file in /var/log/XFree86.0.log have the error message showing like (EE) GLINT(1): Cannot read V_BIOS(3) can anybody give me the solution for this. And for the configured file i got after the above step XF86Config.new, and i tried to check the Xserver by the command XFree86 -xf86config XF86Config.new the system hanged. Please give me the solution for this. There is a possible fix for this in our CVS. If that doesn't work, it might be that the driver for /dev/xsvc doesn't allow certain mappings, in which case you would have to switch to the XFree86-provided aperture driver. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] XFree86-4.4.0 Build On Solaris-8/SPARC [Configuration Problem]
On Wed, 2 Dec 2004, ASIF IQBAL wrote: I have attached output of the command prtconf in the log file prtconfLog. Right now I am not working on the scanpci problem because by scanning idx = 10 it has detected my VGA card in the system. I have exited from the PCI device scan while loop and allowed XFree86 to proceed further which resulted in my XFree86 -configure to complete. But I have one issue here I could perform this XFree86 -configure only when I connect it to the Sun-Blade-100 machine through a telnet session remotely. When I issue the same command from the sun's console login the system hangs. This behaviour was very much peculiar for me. Thanks for the prtconf output. This doesn't look good... The reason I am suggesting scanpci is that it uses the very same PCI scan code as the server but is far easier to debug. You have obviously modified a copy of a recent snapshot to get it to run. In order to proceed with debugging this problem, please undo your change and use the resulting hw/xfree86/etc/scanpci to determine the last pciDeviceTag attempted by pciGenFindNext() before the hang. To do so, you might want to compile os-support/bus/Pci.c with -DDEBUGPCI. I assume you know how to do that, given you've already modified this code. [...] After performing the 5th step it gave me the following error: Could not init font path element /usr/X11R6/lib/X11/fonts/TTF/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! These are inconsequential and can be ignored. What could be the reason for this error. Note I ran the XFree86 -xf86config /XF86Config.new from the telnet session only. Am I skipping any configuration steps still? I suspect the server is _not_ hung. Rather, on this architecture, the server blanks the screen on exit because it has no VGA text mode to restore. Thanks. Marc. P.S.: I do not appreciate receiving some five copies of your response. Please avoid reposting your queries on this list. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] XFree86-4.4.0 Build On Solaris-8/SPARC [Configuration Problem]
On Fri, 3 Dec 2004, ASIF IQBAL wrote: On Fri, 03 Dec 2004 Marc Aurele La France wrote : On Fri, 3 Dec 2004, ASIF IQBAL wrote: On further debugging I identifed that the last scanned PCI device was ATI Technologies Inc Rage XL which is our display card and its tag is 0x1009800. Please refer the following log details of tag numbers and the PCI device details got from the /varlog/XFree86.log. Following is the scanpci command output for exiting when idx = 10 (my hack to stop scanning PCI). This isn't quite what I need to know. For this test, please undo your hack (which I assume is in Pci.c). Then cd xc/programs/Xserver/hw/xfree86/os-support/bus rm -f Pci.o makeg EXTRA_DEFINES=-DDEBUGPCI Pci.o cd ../ make cd ../etc make scanpci sync;sync;sync ./scanpci I need to know the last line `scanpci` (as build above) produces before it crashes the system. Attatched is the complete log file got during the execution of scanpci command. Sorry for bothering too much. This file is incomplete. It has been truncated by the fsck that results after the system crashed. I need to know the last line you see WITH YOUR EYES when you run the specially compiled `scanpci`. In fact it would be better if you ran it from a remote root login into the machine. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] XFree86-4.4.0 Build On Solaris-8/SPARC [Configuration Problem]
On Tue, 7 Dec 2004, ASIF IQBAL wrote: On further debugging I identifed that the last scanned PCI device was ATI Technologies Inc Rage XL which is our display card and its tag is 0x1009800. Please refer the following log details of tag numbers and the PCI device details got from the /varlog/XFree86.log. Following is the scanpci command output for exiting when idx = 10 (my hack to stop scanning PCI). This isn't quite what I need to know. For this test, please undo your hack (which I assume is in Pci.c). Then cd xc/programs/Xserver/hw/xfree86/os-support/bus rm -f Pci.o makeg EXTRA_DEFINES=-DDEBUGPCI Pci.o cd ../ make cd ../etc make scanpci sync;sync;sync ./scanpci I need to know the last line `scanpci` (as build above) produces before it crashes the system. Attatched is the complete log file got during the execution of scanpci command. Sorry for bothering too much. This file is incomplete. It has been truncated by the fsck that results after the system crashed. I need to know the last line you see WITH YOUR EYES when you run the specially compiled `scanpci`. In fact it would be better if you ran it ^^ ** from a remote root login into the machine. I have connected to the SUN Blade/SPARC server through putty login and when i ran the /usr/X11R6/bin/scanpci, the last two lines that i got are as bellow. pci bus 0x0100 cardnum 0x13 function 0x00: vendor 0x1002 device 0x4752 ATI Technologies Inc Rage XL. and can you please elaborate your words It has been truncated by the fsck that results after the system crashed. I didn't say /usr/X11R6/bin/scanpci. I'm refering to the /export/XFree86/XFree86-4.4/xc/programs/Xserver/hw/xfree86/etc/scanpci that was specially built for this test. Marc. PS: Please reply in-line, not at the top. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Xnest and fvwm
On Tue, 7 Dec 2004, Benoit Galarneau wrote: I have a small problem with fvwm. XDMCP is enable on a linux computer running fvwm windows manager. With Solaris, we start a Xnest connection with a query to the linux computer. I log and everything is fine except for a particular application. The application menu's item are not there. I see the menu scrolling down but the text is not there. Everything else is working, mouse click (left, middle and right button). There is no problem without Xnest. When I start a X :1 -query Linux_IP, everything is good. I'll assume the X you're refering to here is Solaris's Xsun. It's possible the application requires backing store and/or save unders to operate. According to our source at least (and X.Org's), Xnest explicitly disables both on its screens. This would be the reason behind the behaviour you're seeing if it also occurs under `Xsun :1 -bs -su -query Linux_IP`. If so, you would then need to hack Xnest (or the application's) source code to change this. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] XFree86-4.4.0 Build On Solaris-8/SPARC [Configuration Problem]
On Wed, 8 Dec 2004, ASIF IQBAL wrote: Some more inputs I gathered on the scanpci issue are as follows: 1) scanpci () crashing is not consistent all the time. After removing my fix, and with the build procedure suggested by you, once it executed without system crashing, for a longer duration. But it was running for half an hour or so never ending, until I killed the process using Ctrl-c. 2) When I tried connecting remotely to the sparc, it never gave me a consistent output. The best last few lines that I could get are given below (and is got through the visual observation only). pciGenFindNext: pciDeviceTag = 0x100f800, devid = 0x pciGenFindNext: pciBusNum 256 pciGenFindNext: pciFuncNum 0 pciReadLong(0x100f800, 0) pciGenFindNext: next bus pciGenFindNext: pciBusInfo[257] = 0x891b0 pciGenFindNext: [257, 0, 0] pciReadLong(0x101, 0) This I got with a slight delay placed in pciReadLong () function within the if condition. This delay was added by me to breath for some time to place the log output in the console. Excellent. This seems to be implying that the bus scan is crashing the system when it gets around to probing what's behind your PCI bridge. To confirm this, the command ... mmapr /dev/fbs/aperture 0x01FE0101 4 /dev/null ... (as root) should consistently crash the system. Does it? Also, please do as root after a fresh reboot ... mmapr /dev/fbs/aperture 0x01FE01002800 256 pci5.dat ... and send me 'pci5.dat' as an attachment. This is a dump of the PCI bridge's configuration space (i.e. binary data), which hopefully will tell me what needs to be done to prevent the crash. Note that I'm assumning `mmapr` is in your $PATH. It should have been installed as '/usr/X11R6/bin/mmapr'. Be very careful with this utility. Typographical errors in its use can be disastrous. Thanks. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals.
Re: [XFree86] XFree86-4.4.0 Build On Solaris-8/SPARC [Configuration Problem]
On Thu, 9 Dec 2004, ASIF IQBAL wrote: On Thu, 09 Dec 2004 Marc Aurele La France wrote : On Wed, 8 Dec 2004, ASIF IQBAL wrote: Some more inputs I gathered on the scanpci issue are as follows: 1) scanpci () crashing is not consistent all the time. After removing my fix, and with the build procedure suggested by you, once it executed without system crashing, for a longer duration. But it was running for half an hour or so never ending, until I killed the process using Ctrl-c. 2) When I tried connecting remotely to the sparc, it never gave me a consistent output. The best last few lines that I could get are given below (and is got through the visual observation only). pciGenFindNext: pciDeviceTag = 0x100f800, devid = 0x pciGenFindNext: pciBusNum 256 pciGenFindNext: pciFuncNum 0 pciReadLong(0x100f800, 0) pciGenFindNext: next bus pciGenFindNext: pciBusInfo[257] = 0x891b0 pciGenFindNext: [257, 0, 0] pciReadLong(0x101, 0) This I got with a slight delay placed in pciReadLong () function within the if condition. This delay was added by me to breath for some time to place the log output in the console. Excellent. This seems to be implying that the bus scan is crashing the system when it gets around to probing what's behind your PCI bridge. To confirm this, the command ... mmapr /dev/fbs/aperture 0x01FE0101 4 /dev/null ... (as root) should consistently crash the system. Does it? Marc you are right. The system is crashed after the execution of the command. I have confirmed this behaviour by repeating twice. Also, please do as root after a fresh reboot ... mmapr /dev/fbs/aperture 0x01FE01002800 256 pci5.dat ... and send me 'pci5.dat' as an attachment. This is a dump of the PCI bridge's configuration space (i.e. binary data), which hopefully will tell me what needs to be done to prevent the crash. Note that I'm assumning `mmapr` is in your $PATH. It should have been installed as '/usr/X11R6/bin/mmapr'. Be very careful with this utility. Typographical errors in its use can be disastrous. I have attached the pci5.dat binary as requested which is got by executing the mmap command. And this didn't have any effect (ie. no system crash). Can you elaborate the significance of the address for mmapr function. `mmapr /dev/fbs/aperture` reads the CPU's physical address space. This address space is divided into various sub-areas (system memory, PCI configuration, PCI I/O, PCI memory, to name a few). In your case, PCI configuration space resides at displacement 0x01FE0100 within this address space for a total length of 128KB. But, for some reason we are hopefully about to determine, the top 64K of this space is not accessible, and it should be. As root, please do (_exactly_ as shown) ... mmapw -b /dev/fbs/aperture 0x01FE01002864 0x7C mmapr /dev/fbs/aperture 0x01FE0101 4 /dev/null ... and tell me if the second command (the `mmapr`) still crashes your system. The `mmapw` is very important here. Its effect is to tell your PCI bridge to ignore most PCI errors that occur on its secondary bus segment. If this works, i.e. no crash, I can then change the X server's (and scanpci's) bus scan to do the same thing and this problem will be solved. Thanks. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals.
Re: Re: [XFree86] XFree86-4.4.0 Build On Solaris-8/SPARC [Configuration Problem]
On Fri, 10 Dec 2004, ASIF IQBAL wrote: Excellent. This seems to be implying that the bus scan is crashing the system when it gets around to probing what's behind your PCI bridge. To confirm this, the command ... mmapr /dev/fbs/aperture 0x01FE0101 4 /dev/null ... (as root) should consistently crash the system. Does it? Marc you are right. The system is crashed after the execution of the command. I have confirmed this behaviour by repeating twice. Also, please do as root after a fresh reboot ... mmapr /dev/fbs/aperture 0x01FE01002800 256 pci5.dat ... and send me 'pci5.dat' as an attachment. This is a dump of the PCI bridge's configuration space (i.e. binary data), which hopefully will tell me what needs to be done to prevent the crash. I have attached the pci5.dat binary as requested which is got by executing the mmap command. And this didn't have any effect (ie. no system crash). Can you elaborate the significance of the address for mmapr function. `mmapr /dev/fbs/aperture` reads the CPU's physical address space. This address space is divided into various sub-areas (system memory, PCI configuration, PCI I/O, PCI memory, to name a few). In your case, PCI configuration space resides at displacement 0x01FE0100 within this address space for a total length of 128KB. But, for some reason we are hopefully about to determine, the top 64K of this space is not accessible, and it should be. As root, please do (_exactly_ as shown) ... mmapw -b /dev/fbs/aperture 0x01FE01002864 0x7C mmapr /dev/fbs/aperture 0x01FE0101 4 /dev/null ... and tell me if the second command (the `mmapr`) still crashes your system. The `mmapw` is very important here. Its effect is to tell your PCI bridge to ignore most PCI errors that occur on its secondary bus segment. Marc, still the system seems to crashing for the mmapr. I have executed first mampw followed by mmapr. I confirmed this beahviour by trying twice. Is there any way that I could confirm my mmapw of 0x7c is successfull using? Will this work mmapr -b /dev/fbs/aperture 0x01FE01002864. If so were can I To verify that the value was correctly written, you can pipe mmapr's stdout into /usr/bin/od, i.e. ... mmapr -b /dev/fbs/aperture 0x01FE01002864 | /usr/bin/od -t x1 I should, at some point, change mmapr to optionally pretty-print its output. see the read value ? In the console or else. I will stay today overnight so that I can try the steps suggested by you and reply you immedieatly. Please confirm me if you need, so that we can complete this issue and will allow me to proceed furter. At this point, I need to ask you to install an adapter into one of the machine's PCI slots. Any adapter will do, as long as it's PCI of course. It doesn't even need to be a video adapter. The intent is to put an adapter behind the PCI bridge. If after installing this adapter, the command ... mmapr /dev/fbs/aperture 0x01FE0101 4 /dev/null ... no longer crashes the system, then please send me the pci5.dat2 that results from ... mmapr /dev/fbs/aperture 0x01FE01002800 256 pci5.dat2 ... and I'll compare that with the pci5.dat you've previously sent. I'll also need to see the updated `prtconf -Ppv` output. Actually, come to think of it, the prtconf output would be useful whether or not installing the extra adapter crashes the system on the mmapr command. Thanks. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: Re: Re: [XFree86] XFree86-4.4.0 Build On Solaris-8/SPARC [Configuration Problem]
On Mon, 13 Dec 2004, ASIF IQBAL wrote:
As root, please do (_exactly_ as shown) ...
mmapw -b /dev/fbs/aperture 0x01FE01002864 0x7C
mmapr /dev/fbs/aperture 0x01FE0101 4 /dev/null
... and tell me if the second command (the `mmapr`) still crashes your
system. The `mmapw` is very important here. Its effect is to tell your
PCI bridge to ignore most PCI errors that occur on its secondary bus
segment.
Marc, still the system seems to crashing for the mmapr. I have executed
first mampw followed by mmapr. I confirmed this beahviour by trying twice.
Is there any way that I could confirm my mmapw of 0x7c is successfull
using? Will this work mmapr -b /dev/fbs/aperture 0x01FE01002864. If so
were can I
To verify that the value was correctly written, you can pipe mmapr's stdout
into /usr/bin/od, i.e. ...
mmapr -b /dev/fbs/aperture 0x01FE01002864 | /usr/bin/od -t x1
There is a typo here. This should have been ...
mmapr -b /dev/fbs/aperture 0x01FE01002864 1 | /usr/bin/od -t x1
... i.e. with the length of the area specified.
I should, at some point, change mmapr to optionally pretty-print its
output.
At this point, I need to ask you to install an adapter into one of the
machine's PCI slots. Any adapter will do, as long as it's PCI of course.
It doesn't even need to be a video adapter. The intent is to put an
adapter behind the PCI bridge. If after installing this adapter, the
command ...
mmapr /dev/fbs/aperture 0x01FE0101 4 /dev/null
... no longer crashes the system, then please send me the pci5.dat2 that
results from ...
mmapr /dev/fbs/aperture 0x01FE01002800 256 pci5.dat2
... and I'll compare that with the pci5.dat you've previously sent. I'll
also need to see the updated `prtconf -Ppv` output.
Actually, come to think of it, the prtconf output would be useful whether
or not installing the extra adapter crashes the system on the mmapr
command.
Marc even after adding the PCI card, still the system crashing. I had
Permedia card which I wanted to finally test with XFree86 in sparc. After
placing the new card in PCI slot I have taken the prtconf -Ppv output,
Please refer the attached log logPci.txt.
Still I have doubt with the mmapw of 0x7C. Because when I read back I am
getting octal value of 0. Following is the sequence of comamnd I have
executed in the shell.
bash-2.03# mmapw -b /dev/fbs/aperture 0x01FE01002864 0x7C
bash-2.03#
bash-2.03# mmapr -b /dev/fbs/aperture 0x01FE01002864 | /usr/bin/od -t x1
mmapr [-{bwlqL}] file offset length
endianness flags:
-b output one byte at a time
-w output up to two aligned bytes at a time
-l output up to four aligned bytes at a time (default)
-q output up to eight aligned bytes at a time
-L same as -l
000
bash-2.03# mmapr /dev/fbs/aperture 0x01FE0101 4 /dev/null
-- System hanged here -
Is the second mmapr is as expected or not ?
See above.
Given the system still hangs, even after installing an adapter, I have
requested access to such a machine here on campus so that I can explore this
problem more thouroughly. I'll get back to you.
Marc.
+--+---+
| Marc Aurele La France | work: 1-780-492-9310 |
| Computing and Network Services | fax:1-780-492-1729 |
| 352 General Services Building | email: [EMAIL PROTECTED] |
| University of Alberta +---+
| Edmonton, Alberta | |
| T6G 2H1 | Standard disclaimers apply|
| CANADA | |
+--+---+
XFree86 developer and VP. ATI driver and X server internals.
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86
Re: Re: Re: Re: [XFree86] XFree86-4.4.0 Build On Solaris-8/SPARC [Configuration Problem]
On Sat, 18 Dec 2004, ASIF IQBAL wrote: Marc later I identified it and confirmed that ther was no issue with write of 0x7c. In the meantime I was going through the PCI code of XFree86 file sparcPci.c in function sparcPciInit (). I came across the following expression for mapping the PCI aperture memory. There seems to be some type mismatch for the fourth parameter. domain.pci = (char *)sparcMapAperture(-1, VIDMEM_MMIO, pci_addr + PCI_MAKE_TAG(domain.bus_min, 0, 0), PCI_MAKE_TAG(domain.bus_max - domain.bus_min + 1, 0, 0)) - PCI_MAKE_TAG(domain.bus_min, 0, 0); ie there seems to be one extra bracket closed before the -. Is this the way the final expreessions needs to be. I am not sure. Can you look into it. PCI_MAKE_TAG(domain.bus_max - domain.bus_min + 1, 0, 0)) - ^ That not-so-extra parenthesis ends the arguments to be passed to sparcMapAperture(). Another Issue that I came across was that printing using xf86MsgVerb behaves abnormally. I am having this issue whne I have more than one prameter for xf86MsgVerb. Trying to do folloiwng has issue. data1 = 0x0; data2 = 0x200; xf86MsgVerb (Value data1 = 0x%x data2 = 0x%x \n, data1, data2) Look at the prototype for that function in common/xf86.h. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Tool chain for MIPS
On Wed, 29 Dec 2004, Jithin Girish wrote: I want to build XFree86 for a MIPS (RM 5231) based computer. can anybody here, tell me which toolchain should i use for that ?? What OS? Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Tool chain for MIPS
On Thu, 30 Dec 2004, Jithin Girish wrote: I want to build XFree86 for a MIPS (RM 5231) based computer. can anybody here, tell me which toolchain should i use for that ?? What OS? On the target machine the OS is Montavista Hard Hat Linux 2.0. On the host machine it is Redhat Linux 8.0. So you're cross-compiling? If so, I can't really help you as that's not my usual MO. I doubt building MIPS binaries on an x86 is done all that often. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
