Xorg config problems
I recycle old P2 class machines for a set of applications at work. I switched to Xorg for these machines a while back, and was pleased to find that I did not have to create a config file for Xorg as it was able to autodetect all the correct stuff. Today, though I ran up on 2 machines that are the older end of the spectrum of machines that I use for this, and for some reason this does not seem to be working. Here's the Xorg logfiel from oen of these amchines: X Window System Version 6.9.0 Release Date: 21 December 2005 X Protocol Version 11, Revision 0, Release 6.9 Build Operating System: FreeBSD 6.1 i386 [ELF] Current Operating System: FreeBSD pulpsysal.fas.com 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #0: Sat Mar 4 13:00:51 EST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 Build Date: 06 March 2006 Before reporting problems, check http://wiki.X.Org to make sure that you have the latest version. 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/Xorg.0.log, Time: Sat Mar 11 10:55:35 2006 (EE) Unable to locate/open config file (II) Module ABI versions: X.Org ANSI C Emulation: 0.2 X.Org Video Driver: 0.8 X.Org XInput driver : 0.5 X.Org Server Extension : 0.2 X.Org Font Renderer : 0.4 (II) Loader running on freebsd (II) LoadModule: bitmap (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.so (II) Module bitmap: vendor=X.Org Foundation compiled for 6.9.0, module version = 1.0.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.so (II) Module pcidata: vendor=X.Org Foundation compiled for 6.9.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 0.8 (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (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,1237 card , rev 02 class 06,00,00 hdr 00 (II) PCI: 00:04:0: chip 8086,7000 card , rev 01 class 06,01,00 hdr 80 (II) PCI: 00:04:1: chip 8086,7010 card , rev 00 class 01,01,80 hdr 00 (II) PCI: 00:06:0: chip 8086,1229 card 8086,0001 rev 02 class 02,00,00 hdr 00 (II) PCI: 00:0d:0: chip 1013,00b8 card ,00ff rev 45 class 03,00,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,0), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:4:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (--) PCI:*(0:13:0) Cirrus Logic GD 5446 rev 69, Mem @ 0xfc00/25, 0xfecff000/12 xf86AutoConfig: Primary PCI is 0:13:0 Running /usr/X11R6/bin/getconfig -X 6090 -I /etc/X11,/usr/X11R6/etc/X11,/usr/X11R6/lib/modules,/usr/X11R6/lib/X11/getconfig -v 0x1013 -d 0x00b8 -r 0x45 -s 0x -b 0x00ff -c 0x0300 New driver is cirrus (==) Using default built-in configuration (53 lines) (==) --- Start of built-in configuration --- Section Module Loadextmod Loaddbe Loadglx Loadfreetype EndSection Section Monitor Identifier Builtin Default Monitor Option TargetRefresh 75.0 EndSection Section Device Identifier Builtin Default cirrus Device 0 Driver cirrus EndSection Section Screen Identifier Builtin Default cirrus Screen 0 Device Builtin Default cirrus Device 0 Monitor Builtin Default Monitor EndSection Section Device Identifier Builtin Default fbdev Device 0 Driver fbdev EndSection Section Screen Identifier Builtin Default fbdev Screen 0 Device Builtin Default fbdev Device 0 Monitor Builtin Default Monitor EndSection Section Device Identifier Builtin Default vesa Device 0 Driver vesa EndSection Section Screen Identifier Builtin Default vesa Screen 0 Device Builtin Default vesa Device 0 Monitor Builtin Default Monitor EndSection Section Device Identifier
Re: Xorg config problems
stan wrote: I recycle old P2 class machines for a set of applications at work. I switched to Xorg for these machines a while back, and was pleased to find that I did not have to create a config file for Xorg as it was able to autodetect all the correct stuff. Today, though I ran up on 2 machines that are the older end of the spectrum of machines that I use for this, and for some reason this does not seem to be working. Here's the Xorg logfiel from oen of these amchines: *SNIP* My guess is thta the graphics cards on these machiens ahve too lilltle memory to work with the default set of assumptions on these machines. However I really don't need very hi-res displays on these amchines. Any sugestions as to how to get Xorg to work with these machines? Try doing an X -configure, which will write out an xorg.conf file for you. You can then tweak the settings to something that works. It looks like, from the log you sent, that the hsync refresh rate that Xorg is guessing is wrong. You might be able to google on your video card and find the right setting. HTH, Micah ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Xorg config problems
stan wrote: I recycle old P2 class machines for a set of applications at work. I switched to Xorg for these machines a while back, and was pleased to find that I did not have to create a config file for Xorg as it was able to autodetect all the correct stuff. Today, though I ran up on 2 machines that are the older end of the spectrum of machines that I use for this, and for some reason this does not seem to be working. Here's the Xorg logfiel from oen of these amchines: snipped (WW) CIRRUS(0): Mode pool is empty (EE) CIRRUS(0): No valid modes found (II) UnloadModule: cirrus (II) UnloadModule: ddc (II) Unloading /usr/X11R6/lib/modules/libddc.so (II) UnloadModule: i2c (II) Unloading /usr/X11R6/lib/modules/libi2c.so (II) UnloadModule: int10 (II) Unloading /usr/X11R6/lib/modules/libint10.so (II) UnloadModule: vgahw (II) Unloading /usr/X11R6/lib/modules/libvgahw.so (II) UnloadModule: cirrus_alpine (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found Please consult the The X.Org Foundation support at http://wiki.X.Org for help. Please also check the log file at /var/log/Xorg.0.log for additional information. My guess is thta the graphics cards on these machiens ahve too lilltle memory to work with the default set of assumptions on these machines. However I really don't need very hi-res displays on these amchines. Any sugestions as to how to get Xorg to work with these machines? Hmm. Looks like you'll need to make some spec changes in a config file. Generate one with `Xorg -configure` ... it won't actually run X, but will test and tell you where it placed the file. Try X again, and make sure it's finding said file (check the output on ttyv0 or wherever ... log file will say also IIRC). You'll then need to tweak Refresh rates and Sync for your monitors and see what happens. Please include standard disclaimers, waivers of damages and remember YMMV and all that. ;-) HTH, Kevin Kinsey -- The meta-Turing test counts a thing as intelligent if it seeks to devise and apply Turing tests to objects of its own creation. -- Lew Mammel, Jr. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Xorg config problems
On 3/11/06, stan [EMAIL PROTECTED] wrote: I recycle old P2 class machines for a set of applications at work. I switched to Xorg for these machines a while back, and was pleased to find that I did not have to create a config file for Xorg as it was able to autodetect all the correct stuff. Today, though I ran up on 2 machines that are the older end of the spectrum of machines that I use for this, and for some reason this does not seem to be working. snip (WW) CIRRUS(0): Mode pool is empty (EE) CIRRUS(0): No valid modes found Usually this means you need to specify your horizontal and vertical sync and refresh rates. I would run: X -configure cp xorg.conf.new /etc/X11/xorg.conf then add some lines like: Section Monitor Identifier Barfy HorizSync 31-92 # Taken from my monitor, VertRefresh 55-160 # Don't use these values. EndSection and change Section Screen Monitor Barfy Frequently on older cards the monitor's capabilities cannot be detected which can lead to very conservative defaults which can lead to no valid modes. There is a database of these values (I've found it to be accurate, if incomplete): http://www.monitorworld.com/monitors_home.html -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Xorg config problems
switched to Xorg for these machines a while back, and was pleased to find that I did not have to create a config file for Xorg as it was able to autodetect all the correct stuff. anyway - it's always better to create this file based on autoconfig made by -configure option. it's quite unlikely autodetect will get the most of your monitor and card. and in your case - autoconfig can't deal with such cases. but for CL5446 i have my config already done for 1024x768x16bit display - if you like. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
