Re: [XFree86] Trident Blade, "no screens"
On Wed, Nov 12, 2003 at 11:31:45AM -0800, John Chandler wrote: >David Dawes writes: > > On Wed, Nov 12, 2003 at 08:04:16AM -0800, John Chandler wrote: > > >David Dawes writes: > > > > On Wed, Nov 12, 2003 at 01:01:13AM -0800, John Chandler wrote: > > > > >Thank you very much for your response. What you suggest had an > > > > >effect, but not an entirely good one... > > > > > > > > > >David Dawes writes: > > > > > > On Tue, Nov 11, 2003 at 01:27:54PM -0800, John Chandler wrote: > > > > > > >When I my newly-installed RedHat system launches, X fails with > > > > > > >this message: > > > > > > > > > > > > > >[...] > > > > > > > (II) Primary Device is: PCI 00:08:0 > > > > > > > (WW) TRIDENT: No matching Device section for instance (BusID PCI:1:0:0) > > > > > > > found > > > > > > > (EE) No devices detected. > > > > > > > > > > > > > > Fatal server error: > > > > > > > no screens found > > > > > > > > > > > > >(--) PCI:*(0:8:0) Silicon Integrated Systems [SiS] SiS300/305 PCI/AGP VGA > > > > > > >Display Adapter rev 144, Mem @ 0xd000/27, 0xe000/17, I/O @ > > > > > > >0xdc00/7 > > > > > > >(--) PCI: (1:0:0) Trident Microsystems CyberBlade/i1 rev 106, Mem @ > > > > > > >0xdd80/23, 0xde00/17, 0xdd00/23 > > > > > > > > >[...] > > > > Well, the primary card is the one that you get the BIOS boot messages > > on, and which Linux boots on. Since your monitor is plugged into > > the add-in PCI card, it's almost certain that it is the SiS card. > > So that's the driver you need to be using. The VideoRam lines > > usually should be commented out, so don't worry about that. I'm > > not up on which SiS cards are supported by the 4.3 sis driver, but > > since Thomas is following this thread, I'm sure he can help with > > that. > > > > Have you tried modifying your XFree86 4.x config to use the "sis" driver > > instead of the "trident" driver? > >Do I have to do anything besides change "Trident" to "SiS"? E.g., do >I need to specify a Busid? If you change the line Driver "trident" to Driver "sis" that should do it. Also, remove any Busid line you might have added. David -- David Dawes developer/release engineer The XFree86 Project www.XFree86.org/~dawes ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] (no subject)
XFree86.0.log Description: Binary data
Re: [XFree86] S O S
That looks like the libextmod.a you have is newer than your X-server. Mark. On Wed, 12 Nov 2003, Mohamad Waluyo wrote: > after I changed my session to KDE, I got a problem where X couldn't started. > Error log is enclosed. > > Any reason why ? > > > > > (II) Module shadow: vendor="The XFree86 Project" > > compiled for 4.2.1, module version = 1.0.0 > > ABI class: XFree86 ANSI C Emulation, version 0.1 > > (II) Loading sub module "fb" > > (II) LoadModule: "fb" > > (II) Loading /usr/X11R6/lib/modules/libfb.a > > (II) Module fb: vendor="The XFree86 Project" > > compiled for 4.2.1, module version = 1.0.0 > > ABI class: XFree86 ANSI C Emulation, version 0.1 > > (II) do I need RAC? No, I don't. > > (II) resource ranges after preInit: > > [0] -1 0xffe0 - 0x (0x20) MX[B](B) > > [1] -1 0x0010 - 0x3fff (0x3ff0) MX[B]E(B) > > [2] -1 0x000f - 0x000f (0x1) MX[B] > > [3] -1 0x000c - 0x000e (0x3) MX[B] > > [4] -1 0x - 0x0009 (0xa) MX[B] > > [5] -1 0xcd103000 - 0xcd1030ff (0x100) MX[B] > > [6] -1 0xcd101000 - 0xcd10107f (0x80) MX[B] > > [7] -1 0xcd10 - 0xcd100fff (0x1000) MX[B] > > [8] -1 0xcd102000 - 0xcd102fff (0x1000) MX[B] > > [9] -1 0xe000 - 0xe3ff (0x400) MX[B] > > [10] -1 0xcd00 - 0xcd01 (0x2) MX[B](B) > > [11] -1 0xc000 - 0xc7ff (0x800) MX[B](B) > > [12] 0 0x000a - 0x000a (0x1) MS[B] > > [13] 0 0x000b - 0x000b7fff (0x8000) MS[B] > > [14] 0 0x000b8000 - 0x000b (0x8000) MS[B] > > [15] -1 0x - 0x (0x1) IX[B] > > [16] -1 0x - 0x00ff (0x100) IX[B] > > [17] -1 0xec00 - 0xecff (0x100) IX[B] > > [18] -1 0xe800 - 0xe87f (0x80) IX[B] > > [19] -1 0xe400 - 0xe47f (0x80) IX[B] > > [20] -1 0xe000 - 0xe0ff (0x100) IX[B] > > [21] -1 0x4000 - 0x400f (0x10) IX[B] > > [22] -1 0xd000 - 0xd07f (0x80) IX[B](B) > > [23] 0 0x03b0 - 0x03bb (0xc) IS[B] > > [24] 0 0x03c0 - 0x03df (0x20) IS[B] > > (II) Loading sub module "int10" > > (II) LoadModule: "int10" > > (II) Reloading /usr/X11R6/lib/modules/linux/libint10.a > > (II) VESA(0): initializing int10 > > (II) VESA(0): Primary V_BIOS segment is: 0xc000 > > (II) VESA(0): VESA BIOS detected > > (II) VESA(0): VESA VBE Version 3.0 > > (II) VESA(0): VESA VBE Total Mem: 8192 kB > > (II) VESA(0): VESA VBE OEM: SiS > > (II) VESA(0): VESA VBE OEM Software Rev: 1.0 > > (II) VESA(0): VESA VBE OEM Vendor: Silicon Integrated Systems Corp. > > (II) VESA(0): VESA VBE OEM Product: 6325 > > (II) VESA(0): VESA VBE OEM Product Rev: 1.11.23 > > (==) VESA(0): Write-combining range (0xc000,0x80) > > virtual address = 0x40148000 - physical address = > > 0xc000 - size = 8388608 > > (==) VESA(0): Default visual is TrueColor > > (==) VESA(0): Backing store disabled > > (**) Option "dpms" > > (**) VESA(0): DPMS enabled > > Symbol RegisterResourceName from module > > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > > Symbol RegisterResourceName from module > > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > > Symbol RegisterResourceName from module > > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > > Symbol RegisterResourceName from module > > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > > Symbol RegisterResourceName from module > > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > > Symbol RegisterResourceName from module > > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > > Symbol RegisterResourceName from module > > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > > Symbol RegisterResourceName from module > > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > > Symbol RegisterResourceName from module > > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > > Symbol RegisterResourceName from module > > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > > Symbol FindClientResourcesByType from module > > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > > Symbol ResourceNames from module > > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > > Symbol RegisterResourceName from module > > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > > Symbol lastResourceType from module > > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > > Symbol ResourceNames from module > > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > > Symbol lastResourceType from module > > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > > Symbol lastResourceType from module > > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > > Symbol FindAllClientResources from module > > /usr/X11R6/lib/modules/extensions/libextmod.a
RE: [XFree86] ATI Radeon VE (7000) config
Thank Alex, It all works fine now, I ended up with Option "SWCursor" "true" (message HWCursor not recognised) but assume the effect is the same. Thanks again Martin Emms. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Armada 1750 problem
On Wed, 12 Nov 2003 [EMAIL PROTECTED] wrote: > I wonder if someone can give a newbie a hand ? I am running Red Hat 9.0 > on a Compaq Armada which contains an internal ATI Rage LT Pro. The > display is working but there is a weird problem. > Like most laptops the screen goes blank when the lid is closed. When > this happens X Windows crashes and all I get is a blank screen after I > lift the lid again. The following additional information may help: > 1) This problem does not occur during boot (before X Windows starts) or >in CMOS setup or when running the original OS (Windows 98SE). >Hardware is therefore assumed to be OK. > 2) After X Windows crashes I can press Alt-F1 to Alt-F6 and get a >viewable text screen. Alt-F7 should get me back to X Windows but all >I see is a blank screen. > 3) Everything else continues to work after X Windows crashes, for >example the CD Player in KDE continues to play an audio CD. > If someone can tell me how to access the setup and log files I can post > them but for now I am not sure where to look. All replies to > [EMAIL PROTECTED] please. Such problems are usually caused by the BIOS performing some action on the screen that the driver is not aware of. The X server has some support for APM which might help, but I am not conversant with it. Alternatively, you could run apmd, or some such daemon, and configure it to issue `chvt` commands which would cause the X server to switch in and out of its virtual terminal when power management events occur. 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 Core Team member. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Problem with ATI Rage Mobility P/M AGP 2x
On Wed, 29 Oct 2003, Roman Banz wrote: > I'm running Debian 3.0 on my laptop with KDE 3.1.4 > ATI Rage Mobility graphics chip with 8Mb of memory. > Everything was fine until a few days ago when I downloaded the > lastest Xserver upgrade from 4.1 to 4.2. At that point when I > re-started X-windows I found that I had several 1 m/m white strip from the > top to the bottom of the screen. I've tried > re-configuring X-windows and various other things. Refuses to work > at all. After re-configuring I've done 'XFree86 -xf86config > /root/XF86Config.new' The new XF86Config is in /root. Still get the > same white strip at the bottom of the screen. > and it still doesn't want to work properly. > Anyone know how to sort this out ? I've attached some info in the > hope that someone can explain. Try specifying a Virtual resolution of 1400x1050. This would be an insertion of a "Virtual 1400 1050" line in the appropriate Display subsection of your XF86Config. 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 Core Team member. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Trident Blade, "no screens"
David Dawes writes: > On Wed, Nov 12, 2003 at 08:04:16AM -0800, John Chandler wrote: > >David Dawes writes: > > > On Wed, Nov 12, 2003 at 01:01:13AM -0800, John Chandler wrote: > > > >Thank you very much for your response. What you suggest had an > > > >effect, but not an entirely good one... > > > > > > > >David Dawes writes: > > > > > On Tue, Nov 11, 2003 at 01:27:54PM -0800, John Chandler wrote: > > > > > >When I my newly-installed RedHat system launches, X fails with > > > > > >this message: > > > > > > > > > > > >[...] > > > > > > (II) Primary Device is: PCI 00:08:0 > > > > > > (WW) TRIDENT: No matching Device section for instance (BusID PCI:1:0:0) > > > > > > found > > > > > > (EE) No devices detected. > > > > > > > > > > > > Fatal server error: > > > > > > no screens found > > > > > > > > > > >(--) PCI:*(0:8:0) Silicon Integrated Systems [SiS] SiS300/305 PCI/AGP VGA > > > > > >Display Adapter rev 144, Mem @ 0xd000/27, 0xe000/17, I/O @ 0xdc00/7 > > > > > >(--) PCI: (1:0:0) Trident Microsystems CyberBlade/i1 rev 106, Mem @ > > > > > >0xdd80/23, 0xde00/17, 0xdd00/23 > > > > > > >[...] > > Well, the primary card is the one that you get the BIOS boot messages > on, and which Linux boots on. Since your monitor is plugged into > the add-in PCI card, it's almost certain that it is the SiS card. > So that's the driver you need to be using. The VideoRam lines > usually should be commented out, so don't worry about that. I'm > not up on which SiS cards are supported by the 4.3 sis driver, but > since Thomas is following this thread, I'm sure he can help with > that. > > Have you tried modifying your XFree86 4.x config to use the "sis" driver > instead of the "trident" driver? Do I have to do anything besides change "Trident" to "SiS"? E.g., do I need to specify a Busid? Thanks, and I'm sorry I'm so ignorant. -jmc ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Supported video card
Thomas Winischhofer writes: > John Chandler wrote: > > > Since I've been having some problems getting XFree86 to come up > > properly, I've been wondering if I shouldn't just get a new video card > > to eliminate the uncertainty of what card to specify in the config > > file. Two questions: > > > > 1. If I say, "Chaintech nVidia GeForce MX400 64MB AGP," does anyone > > break out in hives? Is there a list of video cards that are > > either very well supported or have been problematic in practice? > > (erm, Three Questions!) > > Can't answer that one, but make sure your mother board has a AGP > connector before buying an AGP card. > > Maybe the reason for buying the PCI version of the SiS card had to do > what that? > > After further investigation, it seems you have either a VIA GA-6VMM or > GA-7VMM. These have NO AGP slot. > > Thomas Thank you. I'm now 10x closer to being an expert than I was yesterday. Which says more about yesterday than today. Thanks. -jmc ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] You won't find it under $100 anywhere else!
Just inches long and charged in less than one minute the new mini RC helicopter is this holiday seasons best seller! Selling for only half the price of those at retail stores our mini helicopters are selling out fast! Unlike the mini RC cars of last year the mini RC helicopter is so much more functional and so much more in demand that they will NOT last long! This is not just a mini RC car that looks like a helicopter like some of the fakes selling now, our mini RC helicopters actually fly using a small remote control! The MINI RC helicopter is so easy to control anyone can use it! Get yours now while we can still offer them at such a great discount! http://www.xmas4cheap.net/copter2/ not interested http://www.xmas4cheap.net/b.htm
Re: [XFree86] Supported video card
John Chandler wrote: Since I've been having some problems getting XFree86 to come up properly, I've been wondering if I shouldn't just get a new video card to eliminate the uncertainty of what card to specify in the config file. Two questions: 1. If I say, "Chaintech nVidia GeForce MX400 64MB AGP," does anyone break out in hives? Is there a list of video cards that are either very well supported or have been problematic in practice? (erm, Three Questions!) Can't answer that one, but make sure your mother board has a AGP connector before buying an AGP card. Maybe the reason for buying the PCI version of the SiS card had to do what that? After further investigation, it seems you have either a VIA GA-6VMM or GA-7VMM. These have NO AGP slot. Thomas -- Thomas Winischhofer Vienna/Austria thomas AT winischhofer DOT net *** http://www.winischhofer.net/ twini AT xfree86 DOT org ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Trident Blade, "no screens"
John Chandler wrote: > Thomas Winischhofer writes: > > John Chandler wrote: > > > > >(--) PCI:*(0:8:0) Silicon Integrated Systems [SiS] SiS300/305 PCI/AGP VGA Display Adapter rev 144, Mem @ 0xd000/27, 0xe000/17, I/O @ 0xdc00/7 > > > > >(--) PCI: (1:0:0) Trident Microsystems CyberBlade/i1 rev 106, Mem @ 0xdd80/23, 0xde00/17, 0xdd00/23 > > > > > [...] > > > > The monitor is not connected to the on-board video card, it is > > > This is slightly OT: Is the SiS 300/305 really on-board? If so, > > what MB is this? > > Other than reading the mfr's name off the card (which I've tried but I > can't find anything helpful printed there), or just managing to > remember what I was doing 18 months ago, how do I tell? After googling a little bit, it seems that the combination of VIA PCI devices (1106,) with the trident graphics controller (1023,8500) is found quite often, which makes me believe the trident is on-board, and the SiS is a SiS 300 PCI card plugged into a PCI slot of the main board. So, if you want to avoid the on-board (=trident) graphics, you need to use the SiS driver. Information on that driver is provided at http://www.winischhofer.net/linuxsisvga.shtml > The info above came from software probes, and it appears that one line > describes an SiS AGP interface. Well, the SiS 300 comes in two flavors, one PCI and one AGP version. Thomas -- Thomas Winischhofer Vienna/Austria thomas AT winischhofer DOT net *** http://www.winischhofer.net/ twini AT xfree86 DOT org ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Trident Blade, "no screens"
On Wed, Nov 12, 2003 at 08:04:16AM -0800, John Chandler wrote: >David Dawes writes: > > On Wed, Nov 12, 2003 at 01:01:13AM -0800, John Chandler wrote: > > >Thank you very much for your response. What you suggest had an > > >effect, but not an entirely good one... > > > > > >David Dawes writes: > > > > On Tue, Nov 11, 2003 at 01:27:54PM -0800, John Chandler wrote: > > > > >When I my newly-installed RedHat system launches, X fails with > > > > >this message: > > > > > > > > > >[...] > > > > > (II) Primary Device is: PCI 00:08:0 > > > > > (WW) TRIDENT: No matching Device section for instance (BusID PCI:1:0:0) > > > > > found > > > > > (EE) No devices detected. > > > > > > > > > > Fatal server error: > > > > > no screens found > > > > > > > > >(--) PCI:*(0:8:0) Silicon Integrated Systems [SiS] SiS300/305 PCI/AGP VGA > > > > >Display Adapter rev 144, Mem @ 0xd000/27, 0xe000/17, I/O @ 0xdc00/7 > > > > >(--) PCI: (1:0:0) Trident Microsystems CyberBlade/i1 rev 106, Mem @ > > > > >0xdd80/23, 0xde00/17, 0xdd00/23 > > > > >[...] > > > > > If you want XFree86 to run on the Trident card without making > > > > it the primary you'll need to edit your XF86Config file to tell > > > > the trident driver which device it should be driving. You can > > > > do that by adding the following line to the relevant Device > > > > section of your XF86Config file: > > > > > > > > Busid "1:0:0" > > > > > > > > > >I tried this, and when I restarted the server from the command > > >line, the screen went dark and never came back. I was able to do > > >a ctrl-alt-f1 to get back to screen one where I was then able to > > >do a ctr-c and abort the server. I thought the trouble might be > > >that I hadn't rebooted, so I tried that. This time, the screen > > >went dark and stayed dark. Any clue what I ought to do at this > > >point? (I guess I first have to look up how to boot RedHat 9 > > >without starting X...) > > > > > > > A second alternative is that you really want to be using the built-in > > > > SiS video. > > > > > >I wish I had a decent on-board video interface. > > > > Based on what you've said, maybe it's the Trident that is on-board > > and the SiS is the external card? If that's the case, you need to > > modify your XF86Config to use the "sis" driver instead of the > > "trident" driver (and remove the 'busid' line you just added). > > >[...] > >I don't have much info about the other driver. And of course, I've >lost the docs for the add-on card, too. I'd look at the mfr's web >site, but there's not much writing on the card, so I don't know *what* >mfr. (It's amazing how worthless a card can become without docs.) >What I do have is the XF86Config file that works with this add-on >card. I attach it below, and perhaps it reveals something. That looks like an XFree86 3.3.x config file. A lot from the 3.3.x server that worked with this file would probably provide more info. >I note that in the "Graphics device" sections, the VideoRam lines are >commented out (I don't know why, and don't remember doing it), but it >is my vague recollection that the on-board interface had 1/4 MB and >the add-on had 32MB. Well, the primary card is the one that you get the BIOS boot messages on, and which Linux boots on. Since your monitor is plugged into the add-in PCI card, it's almost certain that it is the SiS card. So that's the driver you need to be using. The VideoRam lines usually should be commented out, so don't worry about that. I'm not up on which SiS cards are supported by the 4.3 sis driver, but since Thomas is following this thread, I'm sure he can help with that. Have you tried modifying your XFree86 4.x config to use the "sis" driver instead of the "trident" driver? David -- David Dawes developer/release engineer The XFree86 Project www.XFree86.org/~dawes ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Supported video card
Since I've been having some problems getting XFree86 to come up properly, I've been wondering if I shouldn't just get a new video card to eliminate the uncertainty of what card to specify in the config file. Two questions: 1. If I say, "Chaintech nVidia GeForce MX400 64MB AGP," does anyone break out in hives? Is there a list of video cards that are either very well supported or have been problematic in practice? (erm, Three Questions!) 2. There used to be a configurator program that allowed me to pick video cards, monitors, etc. from lists, but this seems to have been left in the dustbin of CVS. Currently, I am aware of two ways to configure XFree86: A. run "XFree86 --reconfigure" and hope it does the right thing (which in my case it doesn't), or B. edit the config file by hand, making sure to spell everything right. Is that it, or is there a utility that replaces the old configurator and allows that kind of constrained choice? -jmc ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] problems
This means that X is looking for the fonts on the unix socket 7100 and can't find them. Usually this means that your font server is down. You prolly just need to make sure that xfs is running. If you are using RH try: # service xfs restart On Wed, 2003-11-12 at 10:22, Beth E. Moore wrote: > Could not init font path element unix/:7100, removing from list! -- Mike Wilson<[EMAIL PROTECTED] ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] problems
Attached is the log file. Please advise. Beth M. Flanagan XFree86.0.log Description: application/sas-log
[XFree86] server crash with 'I830WaitLpRing' error message
Hi, I’ve installed a RedHat 9.0 and encountered problems with the Xserver. About every 15 minutes it crashes with an Error message in I830WaitLpRing(). I saw that there was a lot of buzz around it lately but haven’t managed to figure out the solution. I’ve tried to disable the i830 module but it didn’t help. Any suggestions? Thanks, Yuval
Re: [XFree86] PPC 3d acceleration ati radeon 9000 (Dual 1GHZ G4)
juggl3r wrote: what is ppc? is it related in any way to 3d acceleration in ATI cards? It's fairly common shorthand for PowerPC. On Mon, 2003-11-10 at 18:22, Ian Romanick wrote: Raymond Born wrote: Will it ever work. Is there a way that it can already work? It should already work. Various users and developers use this class of ATI hardware on PPC without troubles. What problems are you having? ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Trident Blade, "no screens"
Thomas Winischhofer writes: > John Chandler wrote: > > > >(--) PCI:*(0:8:0) Silicon Integrated Systems [SiS] SiS300/305 PCI/AGP VGA > > Display Adapter rev 144, Mem @ 0xd000/27, 0xe000/17, I/O @ 0xdc00/7 > > > >(--) PCI: (1:0:0) Trident Microsystems CyberBlade/i1 rev 106, Mem @ > > 0xdd80/23, 0xde00/17, 0xdd00/23 > > > > [...] > > The monitor is not connected to the on-board video card, it is > > This is slightly OT: Is the SiS 300/305 really on-board? If so, > what MB is this? Other than reading the mfr's name off the card (which I've tried but I can't find anything helpful printed there), or just managing to remember what I was doing 18 months ago, how do I tell? The info above came from software probes, and it appears that one line describes an SiS AGP interface. It is also intuitively appealing to think of the integrated peripherals as having PCI id's starting with 0 rather than 1, but I don't know if that really means anything. My recollection is that the on-board interface had 1/4 MB, which is why I replaced it. Is the amount of RAM specified by one of those numbers? That might be a clue. -jmc ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Trident Blade, "no screens"
David Dawes writes: > On Wed, Nov 12, 2003 at 01:01:13AM -0800, John Chandler wrote: > >Thank you very much for your response. What you suggest had an > >effect, but not an entirely good one... > > > >David Dawes writes: > > > On Tue, Nov 11, 2003 at 01:27:54PM -0800, John Chandler wrote: > > > >When I my newly-installed RedHat system launches, X fails with > > > >this message: > > > > > > > >[...] > > > > (II) Primary Device is: PCI 00:08:0 > > > > (WW) TRIDENT: No matching Device section for instance (BusID PCI:1:0:0) found > > > > (EE) No devices detected. > > > > > > > > Fatal server error: > > > > no screens found > > > > > > >(--) PCI:*(0:8:0) Silicon Integrated Systems [SiS] SiS300/305 PCI/AGP VGA > > > >Display Adapter rev 144, Mem @ 0xd000/27, 0xe000/17, I/O @ 0xdc00/7 > > > >(--) PCI: (1:0:0) Trident Microsystems CyberBlade/i1 rev 106, Mem @ > > > >0xdd80/23, 0xde00/17, 0xdd00/23 > > > [...] > > > If you want XFree86 to run on the Trident card without making > > > it the primary you'll need to edit your XF86Config file to tell > > > the trident driver which device it should be driving. You can > > > do that by adding the following line to the relevant Device > > > section of your XF86Config file: > > > > > > Busid "1:0:0" > > > > > > >I tried this, and when I restarted the server from the command > >line, the screen went dark and never came back. I was able to do > >a ctrl-alt-f1 to get back to screen one where I was then able to > >do a ctr-c and abort the server. I thought the trouble might be > >that I hadn't rebooted, so I tried that. This time, the screen > >went dark and stayed dark. Any clue what I ought to do at this > >point? (I guess I first have to look up how to boot RedHat 9 > >without starting X...) > > > > > A second alternative is that you really want to be using the built-in > > > SiS video. > > > >I wish I had a decent on-board video interface. > > Based on what you've said, maybe it's the Trident that is on-board > and the SiS is the external card? If that's the case, you need to > modify your XF86Config to use the "sis" driver instead of the > "trident" driver (and remove the 'busid' line you just added). > [...] I don't have much info about the other driver. And of course, I've lost the docs for the add-on card, too. I'd look at the mfr's web site, but there's not much writing on the card, so I don't know *what* mfr. (It's amazing how worthless a card can become without docs.) What I do have is the XF86Config file that works with this add-on card. I attach it below, and perhaps it reveals something. I note that in the "Graphics device" sections, the VideoRam lines are commented out (I don't know why, and don't remember doing it), but it is my vague recollection that the on-board interface had 1/4 MB and the add-on had 32MB. Again, I greatly appreciate the presence of experts in this field. Thank you. -jmc # File generated by XConfigurator. # ** # Refer to the XF86Config(4/5) man page for details about the format of # this file. # ** # ** # Files section. This allows default font and rgb paths to be set # ** Section "Files" # The location of the RGB database. Note, this is the name of the # file minus the extension (like ".txt" or ".db"). There is normally # no need to change the default. RgbPath "/usr/X11R6/lib/X11/rgb" # Multiple FontPath entries are allowed (they are concatenated together) # By default, Red Hat 6.0 and later now use a font server independent of # the X server to render fonts. FontPath "unix/:7100" EndSection # ** # Server flags section. # ** Section "ServerFlags" # Uncomment this to cause a core dump at the spot where a signal is # received. This may leave the console in an unusable state, but may # provide a better stack trace in the core dump to aid in debugging #NoTrapSignals # Uncomment this to disable the server abort sequence # This allows clients to receive this key event. #DontZap # Uncomment this to disable the / mode switching # sequences. This allows clients to receive these key events. #DontZoom EndSection # ** # Input devices # ** # ** # Keyboard section # ***
RE: [XFree86] ATI Radeon VE (7000) config
You will need to use sw cursor with 4.3 due to a bug in the final release. add: Option "HWCursor" "false" to the device sections of your config. Also, if you want one big logical screen instead of two separate screens, add: Option "xinerama" to the serverflags section of your config. Alex -- I have read a related email and added the line : Option "MonitorLayout" "CRT,CRT" I now get dual screen under KDE however (2 independent KDE screens not clones) it seams which works fine apart from if I move the mouse into the left hand screen then the right hand screen goes off and wont come back on. Do I really need to recompile !!! __ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] re problem installing Gnome
df is the utility you want. use -h for human readable output. Reality is but a brief respite between my fantasies. -unknown ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Trident Blade, "no screens"
On Wed, Nov 12, 2003 at 01:01:13AM -0800, John Chandler wrote: >Thank you very much for your response. What you suggest had an >effect, but not an entirely good one... > >David Dawes writes: > > On Tue, Nov 11, 2003 at 01:27:54PM -0800, John Chandler wrote: > > >When I my newly-installed RedHat system launches, X fails with this > > >message: > > > > > >[...] > > > (II) Primary Device is: PCI 00:08:0 > > > (WW) TRIDENT: No matching Device section for instance (BusID PCI:1:0:0) found > > > (EE) No devices detected. > > > > > > Fatal server error: > > > no screens found > > > > >(--) PCI:*(0:8:0) Silicon Integrated Systems [SiS] SiS300/305 PCI/AGP VGA Display > > >Adapter rev 144, Mem @ 0xd000/27, 0xe000/17, I/O @ 0xdc00/7 > > >(--) PCI: (1:0:0) Trident Microsystems CyberBlade/i1 rev 106, Mem @ > > >0xdd80/23, 0xde00/17, 0xdd00/23 > > > > The easiest way to deal with this would be to make the AGP video > > card the primary video card from your BIOS configuration (assuming > > that it has such an option). That way you'll be using the same > > card with XFree86 that you're booting on. The XFree86 server is > > showing the primary video (the one you're bootting up with) to > > currently be the on-board SiS video. Where do you have your > > monitor connected? > >The monitor is not connected to the on-board video card, it is >connected to the one that is mounted in a PCI slot. The on-board >video has a very small amount of RAM and would only support >Fisher-Price resolutions. Apparently the only thing I can do in the >BIOS is specify which of the two to initialize first, I can't make the >on-board one disappear entirely. One might argue that there are good >reasons for that... > > > If you want XFree86 to run on the Trident card without making it > > the primary you'll need to edit your XF86Config file to tell the > > trident driver which device it should be driving. You can do that > > by adding the following line to the relevant Device section of your > > XF86Config file: > > > > Busid "1:0:0" > > > >I tried this, and when I restarted the server from the command line, >the screen went dark and never came back. I was able to do a >ctrl-alt-f1 to get back to screen one where I was then able to do a >ctr-c and abort the server. I thought the trouble might be that I >hadn't rebooted, so I tried that. This time, the screen went dark and >stayed dark. Any clue what I ought to do at this point? (I guess I >first have to look up how to boot RedHat 9 without starting X...) > > > A second alternative is that you really want to be using the built-in > > SiS video. > >I wish I had a decent on-board video interface. Based on what you've said, maybe it's the Trident that is on-board and the SiS is the external card? If that's the case, you need to modify your XF86Config to use the "sis" driver instead of the "trident" driver (and remove the 'busid' line you just added). > > [We should make busid optional in cases like this where there is > > only one card the driver could possibly be wanting to use.] > >I understand that it's not reasonable to expect you to comment on >someone else's product, but maybe you have some idea why the X server >used by the RH graphical install sequence seemed to choose the right >card? I mean what could account for the different behavior -- it >can't be that RH uses someone else's X server for installs, can it? Maybe their installer uses the vesa driver, which would handle the primary card. David -- David Dawes developer/release engineer The XFree86 Project www.XFree86.org/~dawes ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] ATI Radeon VE (7000) config
I have read a related email and added the line : Option "MonitorLayout" "CRT,CRT" I now get dual screen under KDE however (2 independent KDE screens not clones) it seams which works fine apart from if I move the mouse into the left hand screen then the right hand screen goes off and wont come back on. Do I really need to recompile !!! XF86Config Description: Binary data
Re: [XFree86] Video S3 - ProSavage-8
The current savage driver doesn't work, Use "vesa" instead. Arnie On Tue, 11 Nov 2003 10:20:07 -0300 [EMAIL PROTECTED] wrote: Install in my pc they, and it doesn't work me the video targeta. Nesitaria that sent me the dirvers or something to solve my problem. The pattern is: PROSAVAGE8 - KM266 Thank you ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] S O S
after I changed my session to KDE, I got a problem where X couldn't started. Error log is enclosed. Any reason why ? > > (II) Module shadow: vendor="The XFree86 Project" > compiled for 4.2.1, module version = 1.0.0 > ABI class: XFree86 ANSI C Emulation, version 0.1 > (II) Loading sub module "fb" > (II) LoadModule: "fb" > (II) Loading /usr/X11R6/lib/modules/libfb.a > (II) Module fb: vendor="The XFree86 Project" > compiled for 4.2.1, module version = 1.0.0 > ABI class: XFree86 ANSI C Emulation, version 0.1 > (II) do I need RAC? No, I don't. > (II) resource ranges after preInit: > [0] -1 0xffe0 - 0x (0x20) MX[B](B) > [1] -1 0x0010 - 0x3fff (0x3ff0) MX[B]E(B) > [2] -1 0x000f - 0x000f (0x1) MX[B] > [3] -1 0x000c - 0x000e (0x3) MX[B] > [4] -1 0x - 0x0009 (0xa) MX[B] > [5] -1 0xcd103000 - 0xcd1030ff (0x100) MX[B] > [6] -1 0xcd101000 - 0xcd10107f (0x80) MX[B] > [7] -1 0xcd10 - 0xcd100fff (0x1000) MX[B] > [8] -1 0xcd102000 - 0xcd102fff (0x1000) MX[B] > [9] -1 0xe000 - 0xe3ff (0x400) MX[B] > [10] -1 0xcd00 - 0xcd01 (0x2) MX[B](B) > [11] -1 0xc000 - 0xc7ff (0x800) MX[B](B) > [12] 0 0x000a - 0x000a (0x1) MS[B] > [13] 0 0x000b - 0x000b7fff (0x8000) MS[B] > [14] 0 0x000b8000 - 0x000b (0x8000) MS[B] > [15] -1 0x - 0x (0x1) IX[B] > [16] -1 0x - 0x00ff (0x100) IX[B] > [17] -1 0xec00 - 0xecff (0x100) IX[B] > [18] -1 0xe800 - 0xe87f (0x80) IX[B] > [19] -1 0xe400 - 0xe47f (0x80) IX[B] > [20] -1 0xe000 - 0xe0ff (0x100) IX[B] > [21] -1 0x4000 - 0x400f (0x10) IX[B] > [22] -1 0xd000 - 0xd07f (0x80) IX[B](B) > [23] 0 0x03b0 - 0x03bb (0xc) IS[B] > [24] 0 0x03c0 - 0x03df (0x20) IS[B] > (II) Loading sub module "int10" > (II) LoadModule: "int10" > (II) Reloading /usr/X11R6/lib/modules/linux/libint10.a > (II) VESA(0): initializing int10 > (II) VESA(0): Primary V_BIOS segment is: 0xc000 > (II) VESA(0): VESA BIOS detected > (II) VESA(0): VESA VBE Version 3.0 > (II) VESA(0): VESA VBE Total Mem: 8192 kB > (II) VESA(0): VESA VBE OEM: SiS > (II) VESA(0): VESA VBE OEM Software Rev: 1.0 > (II) VESA(0): VESA VBE OEM Vendor: Silicon Integrated Systems Corp. > (II) VESA(0): VESA VBE OEM Product: 6325 > (II) VESA(0): VESA VBE OEM Product Rev: 1.11.23 > (==) VESA(0): Write-combining range (0xc000,0x80) > virtual address = 0x40148000 - physical address = > 0xc000 - size = 8388608 > (==) VESA(0): Default visual is TrueColor > (==) VESA(0): Backing store disabled > (**) Option "dpms" > (**) VESA(0): DPMS enabled > Symbol RegisterResourceName from module > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > Symbol RegisterResourceName from module > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > Symbol RegisterResourceName from module > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > Symbol RegisterResourceName from module > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > Symbol RegisterResourceName from module > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > Symbol RegisterResourceName from module > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > Symbol RegisterResourceName from module > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > Symbol RegisterResourceName from module > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > Symbol RegisterResourceName from module > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > Symbol RegisterResourceName from module > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > Symbol FindClientResourcesByType from module > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > Symbol ResourceNames from module > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > Symbol RegisterResourceName from module > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > Symbol lastResourceType from module > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > Symbol ResourceNames from module > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > Symbol lastResourceType from module > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > Symbol lastResourceType from module > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > Symbol FindAllClientResources from module > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > Symbol lastResourceType from module > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > Symbol TypeMask from module > /usr/X11R6/lib/modules/extensions/libextmod.a is unresolved! > (II) Setting vga for screen 0. > (II) Initializing built-in extension MI
Re: [XFree86] ATI Radeon VE (7000) config
Compile X from CVS and it'll work perfectly. The Radeon driver in 4.3.0 has poor support to dual-display Radeon 7000 cards. Alon. Martin Emms wrote: Anyone managed to make the dual display feature work reliably on any ATI card ? I need help with my XF86Config file. I have 2 screens linked to a Radeon VE (7000) card in the AGP slot, I am running Redhat 9 with XFree86-4.3. The best I have managed is to get X running on both screens at once in "clone mode" (both screen showing the same thing). However the second screen goes off as soon as the mouse crosses a window (eg. xterm). To get this to work I had to initialise the macine to runlevel 3 then start X from the command line with "xinit". Trying to run KDE on runlevel 5, the second screen goes off as soon as X is initialised. This is the XF86Config file I was using, there are suggestions from a lot of different sources in here (man pages, readme files and suggestions on forums) but still no joy. # XFree86 4 configuration created by redhat-config-xfree86 Section "ServerLayout" Identifier "Default Layout" Screen 0 "Screen0" 0 0 Screen 1 "Screen1" RightOf "Screen0" InputDevice"Mouse0" "CorePointer" InputDevice"Keyboard0" "CoreKeyboard" InputDevice"DevInputMice" "AlwaysCore" EndSection Section "Files" RgbPath "/usr/X11R6/lib/X11/rgb" FontPath "unix/:7100" EndSection Section "Module" Load "dbe" Load "extmod" Load "fbdevhw" Load "glx" Load "record" Load "freetype" Load "type1" # Load "dri" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "keyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc105" Option "XkbLayout" "gb" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "PS/2" Option "Device" "/dev/psaux" Option "ZAxisMapping" "4 5" Option "Emulate3Buttons" "no" EndSection Section "InputDevice" Identifier "DevInputMice" Driver "mouse" Option "Protocol" "IMPS/2" Option "Device" "/dev/input/mice" Option "ZAxisMapping" "4 5" Option "Emulate3Buttons" "no" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName"AOC Spectrum" DisplaySize 320 240 HorizSync30.0 - 95.0 VertRefresh 50.0 - 160.0 Option "dpms" EndSection Section "Monitor" Identifier "Monitor1" VendorName "Monitor Vendor" ModelName"Daytek DT-1770" DisplaySize 320 240 HorizSync30.0 - 70.0 VertRefresh 50.0 - 150.0 Option "dpms" EndSection Section "Device" Identifier "Videocard0" Driver "radeon" VendorName "Videocard vendor" BoardName "ATI Radeon VE" # VideoRam65536 BusID "PCI:1:0:0" Option "CloneDisplay" "2" EndSection Section "Screen" Identifier "Screen0" Device "Videocard0" Monitor"Monitor0" DefaultDepth 16 SubSection "Display" Depth 16 Modes"1024x768" "800x600" "640x480" EndSubSection EndSection Section "Screen" Identifier "Screen1" Device "Videocard0" Monitor"Monitor1" DefaultDepth 16 SubSection "Display" Depth 16 Modes"1024x768" "800x600" "640x480" EndSubSection EndSection # Section "DRI" # Group0 # Mode 0666 # EndSection ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] ATI Radeon VE (7000) config
Title: Message Anyone managed to make the dual display feature work reliably on any ATI card ? I need help with my XF86Config file. I have 2 screens linked to a Radeon VE (7000) card in the AGP slot, I am running Redhat 9 with XFree86-4.3. The best I have managed is to get X running on both screens at once in "clone mode" (both screen showing the same thing). However the second screen goes off as soon as the mouse crosses a window (eg. xterm). To get this to work I had to initialise the macine to runlevel 3 then start X from the command line with "xinit". Trying to run KDE on runlevel 5, the second screen goes off as soon as X is initialised. This is the XF86Config file I was using, there are suggestions from a lot of different sources in here (man pages, readme files and suggestions on forums) but still no joy. # XFree86 4 configuration created by redhat-config-xfree86 Section "ServerLayout" Identifier "Default Layout" Screen 0 "Screen0" 0 0 Screen 1 "Screen1" RightOf "Screen0" InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" InputDevice "DevInputMice" "AlwaysCore"EndSection Section "Files" RgbPath "/usr/X11R6/lib/X11/rgb" FontPath "unix/:7100"EndSection Section "Module" Load "dbe" Load "extmod" Load "fbdevhw" Load "glx" Load "record" Load "freetype" Load "type1"# Load "dri"EndSection Section "InputDevice" Identifier "Keyboard0" Driver "keyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc105" Option "XkbLayout" "gb"EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "PS/2" Option "Device" "/dev/psaux" Option "ZAxisMapping" "4 5" Option "Emulate3Buttons" "no"EndSection Section "InputDevice" Identifier "DevInputMice" Driver "mouse" Option "Protocol" "IMPS/2" Option "Device" "/dev/input/mice" Option "ZAxisMapping" "4 5" Option "Emulate3Buttons" "no"EndSection Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName "AOC Spectrum" DisplaySize 320 240 HorizSync 30.0 - 95.0 VertRefresh 50.0 - 160.0 Option "dpms"EndSection Section "Monitor" Identifier "Monitor1" VendorName "Monitor Vendor" ModelName "Daytek DT-1770" DisplaySize 320 240 HorizSync 30.0 - 70.0 VertRefresh 50.0 - 150.0 Option "dpms"EndSection Section "Device" Identifier "Videocard0" Driver "radeon" VendorName "Videocard vendor" BoardName "ATI Radeon VE"# VideoRam 65536 BusID "PCI:1:0:0" Option "CloneDisplay" "2"EndSection Section "Screen" Identifier "Screen0" Device "Videocard0" Monitor "Monitor0" DefaultDepth 16 SubSection "Display" Depth 16 Modes "1024x768" "800x600" "640x480" EndSubSectionEndSection Section "Screen" Identifier "Screen1" Device "Videocard0" Monitor "Monitor1" DefaultDepth 16 SubSection "Display"Depth 16Modes "1024x768" "800x600" "640x480" EndSubSectionEndSection # Section "DRI"# Group 0# Mode 0666# EndSection
[XFree86] problem in installing LINUX 9.0 (Mandrake)
R/Sir, I have install Linux 9.0 (Mandrake) on my system. But it does not show me graphical view. It gives error as given below (EE) Sreen(s) Found, but none have a usable configuration. Fatal server error: no screen found. It also give some message : XFree86 Version 4.2.1 / xwindow system (protocol version 11 , revision 0, vendor release 6600) Release sate : 3 september 2002 If server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problem. My motherboard is D845DLLY release on 10 june 2002.I have also attach log file (/var/log/XFree86.0.log) with this mail. Sir please give me a solution for above problem as early as possible. Sir please mail me on [EMAIL PROTECTED] Thank you. Kapil Bobde Click onthe image to chat with me XFree86 Version 4.2.1 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 3 September 2002 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/) Build Operating System: Linux 2.4.18-23mdkenterprise i686 [ELF] Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/XFree86.0.log", Time: Tue Nov 11 22:29:52 2003 Using vt 7 (--) using VT number 7 (WW) Open APM failed (/dev/apm_bios) (No such device) (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.5 XFree86 XInput driver : 0.3 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.3 (II) Loader running on linux (II) LoadModule: "bitmap" (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor="The XFree86 Project" compiled for 4.2.1, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.3 (II) Loading font Bitmap (II) LoadModule: "pcidata" (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor="The XFree86 Project" compiled for 4.2.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,2560 card 8086,2560 rev 01 class 06,00,00 hdr 00 (II) PCI: 00:02:0: chip 8086,2562 card 8086,4c59 rev 01 class 03,00,00 hdr 00 (II) PCI: 00:1d:0: chip 8086,24c2 card 8086,4c59 rev 01 class 0c,03,00 hdr 80 (II) PCI: 00:1d:1: chip 8086,24c4 card 8086,4c59 rev 01 class 0c,03,00 hdr 00 (II) PCI: 00:1d:2: chip 8086,24c7 card 8086,4c59 rev 01 class 0c,03,00 hdr 00 (II) PCI: 00:1d:7: chip 8086,24cd card 8086,4c59 rev 01 class 0c,03,20 hdr 00 (II) PCI: 00:1e:0: chip 8086,244e card , rev 81 class 06,04,00 hdr 01 (II) PCI: 00:1f:0: chip 8086,24c0 card , rev 01 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,24cb card 8086,4c59 rev 01 class 01,01,8a hdr 00 (II) PCI: 00:1f:3: chip 8086,24c3 card 8086,4c59 rev 01 class 0c,05,00 hdr 00 (II) PCI: 00:1f:5: chip 8086,24c5 card 8086,0303 rev 01 class 04,01,00 hdr 00 (II) PCI: End of PCI scan (II) LoadModule: "scanpci" (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci: vendor="The XFree86 Project" compiled for 4.2.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5 (II) UnloadModule: "scanpci" (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (II) Host-to-PCI bridge: (II) PCI-to-ISA bridge: (II) PCI-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x08 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0x - 0x (0x0) MX[B] (II) Bus 1: bridge is at (0:30:0), (0,1,1), BCTRL: 0x06 (VGA_EN is cleared) (II) Bus 1 I/O range: (II) Bus 1 non-prefetchable memory range: [0] -1 0xff80 - 0xff8f (0x10) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 0xe6a0 - 0xe6af (0x10) MX[B] (II) Bus -1: bridge is at (0:31:0), (0,-1,0), BCTRL: 0x08 (VGA_EN is set) (II) Bus -1 I/O range: (II) Bus -1 non-prefetchable memory range: (II) Bus -1 prefetchable memory range: (--) PCI:*(0:2:0) Intel unknown chipset (0x2562) rev 1, Mem @ 0xf000/27, 0xffa8/19 List of video drivers: atimisc r128 radeon mga glint nv tga s3 s3virge sis rendition neomagic i740 tdfx savage cirrus vmware tseng trident chi
[XFree86] refresh problems
Hi * i've some problem: On my monitor documentation i can read: 1024*768 @ 100Hz in my XF86-config-4 section Monito i've: Modeline "1024x768" 115.50 1024 1056 1248 1440 768 771 781 802 -hsync -vsync and in the section Screen: Modes "1280x1024" "1024x768" "800x600" "640x480" now the problem is that it start the Gnome Display Manager with the resolution of [EMAIL PROTECTED] but i'd like [EMAIL PROTECTED], the problem is that when i switch to [EMAIL PROTECTED] gnome make some errors: the login window of gdm is ok but after the gnome desktop is cutted on the right and at the bottom, i can try to change dimensions via hardware monitor panel but can't visualize all my desktop, where is the problem, is a gnome problem ? my eyes will be very happy ;) bye paolo -- _ For your security, this mail has been scanned and protected by Inflex ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Trident Blade, "no screens"
John Chandler wrote: > >(--) PCI:*(0:8:0) Silicon Integrated Systems [SiS] SiS300/305 PCI/AGP VGA Display Adapter rev 144, Mem @ 0xd000/27, 0xe000/17, I/O @ 0xdc00/7 > >(--) PCI: (1:0:0) Trident Microsystems CyberBlade/i1 rev 106, Mem @ 0xdd80/23, 0xde00/17, 0xdd00/23 > [...] The monitor is not connected to the on-board video card, it is This is slightly OT: Is the SiS 300/305 really on-board? If so, what MB is this? Thomas -- Thomas Winischhofer Vienna/Austria thomas AT winischhofer DOT net *** http://www.winischhofer.net/ twini AT xfree86 DOT org ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Armada 1750 problem
Hi there I wonder if someone can give a newbie a hand ? I am running Red Hat 9.0 on a Compaq Armada which contains an internal ATI Rage LT Pro. The display is working but there is a weird problem. Like most laptops the screen goes blank when the lid is closed. When this happens X Windows crashes and all I get is a blank screen after I lift the lid again. The following additional information may help: 1) This problem does not occur during boot (before X Windows starts) or in CMOS setup or when running the original OS (Windows 98SE). Hardware is therefore assumed to be OK. 2) After X Windows crashes I can press Alt-F1 to Alt-F6 and get a viewable text screen. Alt-F7 should get me back to X Windows but all I see is a blank screen. 3) Everything else continues to work after X Windows crashes, for example the CD Player in KDE continues to play an audio CD. If someone can tell me how to access the setup and log files I can post them but for now I am not sure where to look. All replies to [EMAIL PROTECTED] please. Thank you. Ed Almos Budapest, Hungary Miert fizetsz az internetert? Korlatlan, ingyenes internet hozzaferes a FreeStarttol. Probald ki most! http://www.freestart.hu
Re: [XFree86] Trident Blade, "no screens"
Thank you very much for your response. What you suggest had an effect, but not an entirely good one... David Dawes writes: > On Tue, Nov 11, 2003 at 01:27:54PM -0800, John Chandler wrote: > >When I my newly-installed RedHat system launches, X fails with this > >message: > > > >[...] > > (II) Primary Device is: PCI 00:08:0 > > (WW) TRIDENT: No matching Device section for instance (BusID PCI:1:0:0) found > > (EE) No devices detected. > > > > Fatal server error: > > no screens found > > >(--) PCI:*(0:8:0) Silicon Integrated Systems [SiS] SiS300/305 PCI/AGP VGA Display > >Adapter rev 144, Mem @ 0xd000/27, 0xe000/17, I/O @ 0xdc00/7 > >(--) PCI: (1:0:0) Trident Microsystems CyberBlade/i1 rev 106, Mem @ 0xdd80/23, > >0xde00/17, 0xdd00/23 > > The easiest way to deal with this would be to make the AGP video > card the primary video card from your BIOS configuration (assuming > that it has such an option). That way you'll be using the same > card with XFree86 that you're booting on. The XFree86 server is > showing the primary video (the one you're bootting up with) to > currently be the on-board SiS video. Where do you have your > monitor connected? The monitor is not connected to the on-board video card, it is connected to the one that is mounted in a PCI slot. The on-board video has a very small amount of RAM and would only support Fisher-Price resolutions. Apparently the only thing I can do in the BIOS is specify which of the two to initialize first, I can't make the on-board one disappear entirely. One might argue that there are good reasons for that... > If you want XFree86 to run on the Trident card without making it > the primary you'll need to edit your XF86Config file to tell the > trident driver which device it should be driving. You can do that > by adding the following line to the relevant Device section of your > XF86Config file: > > Busid "1:0:0" > I tried this, and when I restarted the server from the command line, the screen went dark and never came back. I was able to do a ctrl-alt-f1 to get back to screen one where I was then able to do a ctr-c and abort the server. I thought the trouble might be that I hadn't rebooted, so I tried that. This time, the screen went dark and stayed dark. Any clue what I ought to do at this point? (I guess I first have to look up how to boot RedHat 9 without starting X...) > A second alternative is that you really want to be using the built-in > SiS video. I wish I had a decent on-board video interface. > [We should make busid optional in cases like this where there is > only one card the driver could possibly be wanting to use.] I understand that it's not reasonable to expect you to comment on someone else's product, but maybe you have some idea why the X server used by the RH graphical install sequence seemed to choose the right card? I mean what could account for the different behavior -- it can't be that RH uses someone else's X server for installs, can it? -jmc ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] hanging before gdm
RH9.0 (Shrik) XFree86 4.3.0 Gnome 2.4 I installed XFree86 4.3.0 using the installation script, then I installed gnome using garnome. There were some errors at the end of installatino of gnome using garnome referring to mozilla-gtdsomething. I rebooted into linux and now, when my gdm is supposed to appear, the screen flashes between the text login and a blue screen saying that x cannot be started. The first time this happened it said it was going to configure and then restart x. But now all I get are random flashes between screens. Sometimes I can see the text log-in screen, but then it flashes away. Anyone know what the problem is? Tom ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
