Re: [XFree86] startx not working
Check past posting on how to start font server. Your font server is not running. surya santosh wrote: Hi I am using RedHat Linux 2.4.18-14. I rebooted my machine to DOS and again rebooted in LINUX. When i type startx at the shell, it is displaying as Server Crash and the dump is attached. Please help me in finding out the problem. Regards Surya Santosh __ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/ --- Name: XFree86.0.log XFree86.0.log Type: Text Document (application/x-unknown-content-type-txtfile) Encoding: base64 Description: XFree86.0.log ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] 4.4.0 compilation problems
Try starting with a minimum change to your host.def Arthur Rinkel wrote: Hi, I'm having some troubles compiling Xfree86 version 4.4.0 on my homebrew Linux system (kernel 2.4.20). A 'make World' recognizes my system as: Linux distribution: unknown libc: 6.2.2 binutils: 21.3 GCC: 3.0 I've compiled with and without changes to certain .cf files, but in the end that doesn't matter. Thus far the programs 'bdftopcf' and 'mkcfm' produce undefined references to all kind of symbols during compilation (eg. xf86printf, xf86strlcat). These symbols seem to be defined in source files contained in the directories under xc/programs/Xserver/hw/xfree86/. When make World arrives at 'bdftopcf' these files (in the form of .o and/or .a files) aren't compiled yet... Running 'make' manually from within the directories does create the objects and libraries, however still an error occurs while compiling scanpci.c under .../xfree86/etc/ (i.e. undefined reference to 'cos'). Also, the Makefile of 'bdftopcf' for example, does not contain a line to include the library archive which contains the symbol xf86printf (which appears in .../os-support/libxf86_os.a). The Makefile does include the library freetype, fntstubs and Xfont, of which the latter contains an undefined reference to xf86printf, so maybe here's something going wrong... I mean, maybe Xfont shouldn't miss this symbol. Now I've manually added the required library paths and names to the Makefile, but that's not the way ofcourse. So I'm puzzled as to why the libraries under .../hw/xfree86/ aren't created on time. Any ideas? Grtz, Arthur ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] 4.4.0 compilation problems
Attach your host.def Arthur Rinkel wrote: On Fri, Mar 11, 2005 at 08:51:14AM -0800, Bukie Mabayoje wrote: Try starting with a minimum change to your host.def I have tried an empty host.def and a host.def with the following 2 modifications: - uncommented ServerToInstall setting - XF86CardDrivers set to 'mga' only Everytime I have those compilation errors... Grtz, Arthur ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Partially successful installation/startup
Post the log and configuration file when you try to start X automatically. Norm wrote: - Original Message - From: Bukie Mabayoje [EMAIL PROTECTED] To: xfree86@xfree86.org Sent: Wednesday, March 09, 2005 7:31 PM Subject: Re: [XFree86] Partially successful installation/startup You need to update the Font Server Port # in your configuration file. Change the line FontPath unix/:-1 to FontPath unix/:7100 Norm wrote: Sorry for the delay but I don't get on the 737 very often any more. Anyway, while I was watching it boot today, I noticed that during the boot process it said that the startup of the Font Server failed. That's probably why we can't execute 'init 5' to start X Window. Since we can execute the 'startx' script, everything we need is obviously there, but, I'd guess, not in the right places. What do I need to do to get the Font Server to start up during bootup? Go into /etc/init.d directory and search for xfs. Login as root do ./xfs start Did it start or failed? Okay -- quick summary: 1. Linux based on RedHat 6.2 with 2.2.18 kernel with Real-Time Linux v3.1 patches applied. 2. Pentium III on a Single Board Computer with on-board Chips Technology (CT) 69000 AGP with 2 MB video memory. 3. If we try to execute 'init 5' the system goes into a endless -- and uninterruptible -- cycling of trying and failing to start the X Window system 4. If, at a text shell prompt, we execute 'startx' the X Window system starts perfectly. 5. During bootup one of the messages is that the X-Font Server failed to start. A. I changed the FontPath line in the XF86Config file as directed above. B.. I executed '/etc/rc.d/init.d/xfs start' and it (apparently) succeeds. BUT .. trying to execute 'startx' afterwards fails with the message [not exact wording] ...can't find font: fixed ... and the system starts the endless trying-to-start-and-failing loop. It was necessary to change the FontServer back to -1 in order to have 'startx' work. AND 'init 5' fails as before. Clearly we can manually execute 'startx' after logging into a text shell each time but we'd really like to get it to happen automatically on bootup. Any suggestions? Norm ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Partially successful installation/startup
Can you telnet to the system? Norm wrote: You've already got the Configuration File which was posted before with just the recommended change of the FontServer socket. I'm not sure how to get a log file if I have to cycle power to regain control of the system because the process is cycling and uninterruptible. I suppose I could try to write a QD shell script to sleep for a few seconds and then perform a shutdown. Do you think this would work? Norm - Original Message - From: Bukie Mabayoje [EMAIL PROTECTED] To: xfree86@xfree86.org Sent: Friday, March 11, 2005 3:19 PM Subject: Re: [XFree86] Partially successful installation/startup Post the log and configuration file when you try to start X automatically. Norm wrote: - Original Message - From: Bukie Mabayoje [EMAIL PROTECTED] To: xfree86@xfree86.org Sent: Wednesday, March 09, 2005 7:31 PM Subject: Re: [XFree86] Partially successful installation/startup You need to update the Font Server Port # in your configuration file. Change the line FontPath unix/:-1 to FontPath unix/:7100 Norm wrote: Sorry for the delay but I don't get on the 737 very often any more. Anyway, while I was watching it boot today, I noticed that during the boot process it said that the startup of the Font Server failed. That's probably why we can't execute 'init 5' to start X Window. Since we can execute the 'startx' script, everything we need is obviously there, but, I'd guess, not in the right places. What do I need to do to get the Font Server to start up during bootup? Go into /etc/init.d directory and search for xfs. Login as root do ./xfs start Did it start or failed? Okay -- quick summary: 1. Linux based on RedHat 6.2 with 2.2.18 kernel with Real-Time Linux v3.1 patches applied. 2. Pentium III on a Single Board Computer with on-board Chips Technology (CT) 69000 AGP with 2 MB video memory. 3. If we try to execute 'init 5' the system goes into a endless -- and uninterruptible -- cycling of trying and failing to start the X Window system 4. If, at a text shell prompt, we execute 'startx' the X Window system starts perfectly. 5. During bootup one of the messages is that the X-Font Server failed to start. A. I changed the FontPath line in the XF86Config file as directed above. B.. I executed '/etc/rc.d/init.d/xfs start' and it (apparently) succeeds. BUT .. trying to execute 'startx' afterwards fails with the message [not exact wording] ...can't find font: fixed ... and the system starts the endless trying-to-start-and-failing loop. It was necessary to change the FontServer back to -1 in order to have 'startx' work. AND 'init 5' fails as before. Clearly we can manually execute 'startx' after logging into a text shell each time but we'd really like to get it to happen automatically on bootup. Any suggestions? Norm ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Partially successful installation/startup
I was watching it boot today, I noticed that during the boot process it said that the startup of the Font Server failed. That's probably why we can't execute 'init 5' to start X Window. Since we can execute the 'startx' script, everything we need is obviously there, but, I'd guess, not in the right places. What do I need to do to get the Font Server to start up during bootup? Thanks Norm - Original Message - From: Bukie Mabayoje [EMAIL PROTECTED] To: xfree86@xfree86.org Sent: Thursday, February 17, 2005 11:59 AM Subject: Re: [XFree86] Partially successful installation/startup Post your configuration file. Norm wrote: The basic setup is a Pentium-III Linux system that started with RedHat 6.2 patched with the FSM Labs GPL-version of Real-Time Linux installed from the FSM-labs installation CD-ROM. We've used it many times on several diverse systems, both desktop PCs and Single Board Computer (SBC)-based rackmount boxes with essentially no problems at all. On this particular box we had installed the system and had it running fine, then changed the SBC. Of course, the VGA chipset changed as well so we had to install the SBC-manufacturer's VGA driver and use Xconfigurator to modify the old configuration to the new system. The result is that we can successfully start the system into run-state 3 (text mode) and then login and issue a `startx` command from a text console to get the X-Window system running just fine. When we do, the output on the text console is insmod: a module named agpgart already exists XFCom_i810 Version 3.3.6 / X Window System (protocol Version 11, revision 0, vendor release 6300) Release Date: May 19 2000 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://support.intel.com/support/graphics/intel810/linuxsoftware.htm) Operating System: Linux 2.2.14-5.0 i686 [ELF] Configured drivers: SVGA: server for SVGA graphics adaptors (Patchlevel 0): i810, i810-dc100, i810e, i815, generic (using VT number 7) XF86Config: /usr/X11R6/lib/X11/XF86Config (**) stands for supplied, (--) stands for probed/default values (**) XKB: keycodes: xfree86 (**) XKB: types: default (**) XKB: compat: default (**) XKB: symbols: us(pc101) (**) XKB: geometry: pc (**) XKB: rules: xfree86 (**) XKB: model: pc101 (**) XKB: layout: us (**) Mouse: type: PS/2, device: /dev/mouse, buttons: 3 (**) Mouse: 3 button emulation (timeout: 50ms) (**) SVGA: Graphics device ID: Intel Corporation|82810E CGC [Chipset Graphics Controller] (**) SVGA: Monitor ID: My Monitor Warning: The directory /usr/X11R6/lib/X11/fonts/TrueType does not exist. Entry deleted from font path. (**) FontPath set to unix/:-1 (--) SVGA: PCI: Intel Unknown chipset (0x7125) rev 3, Memory @ 0xe800, 0xeff8 (--) SVGA: GART: allocated 4096K system ram (--) SVGA: chipset: i810e (--) SVGA: videoram: 4096k (**) SVGA: Option dac_8_bit (**) SVGA: Using 24 bpp, Depth 24, Color weight: 888 (--) SVGA: Maximum allowed dot-clock: 128.000 MHz (**) SVGA: Mode 800x600: mode clock = 36.000 (--) SVGA: i810e: Display width padded to 2496 bytes (832 pixels). (--) SVGA: Virtual resolution set to 800x600 (--) SVGA: SpeedUp code selection modified because virtualX != 1024 (--) SVGA: Intel i810e (--) SVGA: i810e: MMIO registers at 0xEFF8 (--) SVGA: i810e: Linear framebuffer at 0xE800 (--) SVGA: i810e: Using hardware cursor (--) SVGA: Setting dot clock to 36.0 MHz [ 0x10 0x1 0x40 ] [ 18 3 4 ] (--) SVGA: chose watermark 0x22008000: (tab.freq 40.0) (--) SVGA: Using XAA (XFree86 Acceleration Architecture) (--) SVGA: XAA: Solid filled rectangles (--) SVGA: XAA: Screen-to-screen copy (--) SVGA: XAA: 8x8 color expand pattern fill (--) SVGA: XAA: Indirect CPU to screen color expansion (imagetext, polytext) (--) SVGA: XAA: Using 6 128x85 areas for pixmap caching (--) SVGA: XAA: Caching tiles (--) SVGA: XAA: Horizontal and vertical lines and segments SESSION_MANAGER=local/sac:/tmp/.ICE-unix/879,tcp/sac:1037 SetKbdSettings - type: 0 rate: 19 delay: 263 snumlk: 0 SetKbdSettings - Succeeded AUDIT: Wed Feb 16 08:40:26 2005: 876 X: client 10 rejected from local host Xlib: connection to :0.0 refused by server Xlib: Client is not authorized to connect to Server xscreensaver: Can't open display: :0 xscreensaver: initial effective
Re: [XFree86] Partially successful installation/startup
Replace the configuration Section Files with the one below. You don't need font server running if you specify the font path Section "Files" #FontPath "unix/:7100" # local font server # if the local font server has problems, we can fall back on these FontPath "/usr/lib/X11/fonts/misc" FontPath "/usr/lib/X11/fonts/cyrillic" FontPath "/usr/lib/X11/fonts/100dpi/:unscaled" FontPath "/usr/lib/X11/fonts/75dpi/:unscaled" FontPath "/usr/lib/X11/fonts/Type1" FontPath "/usr/lib/X11/fonts/Speedo" FontPath "/usr/lib/X11/fonts/100dpi" FontPath "/usr/lib/X11/fonts/75dpi" EndSection Make sure xfs is not automatically started Norm wrote: - Original Message - From: "Bukie Mabayoje" [EMAIL PROTECTED]> To: xfree86@xfree86.org> Sent: Wednesday, March 09, 2005 7:31 PM Subject: Re: [XFree86] Partially successful installation/startup > You need to update the Font Server Port # in your configuration file. > Change the line FontPath "unix/:-1" to FontPath "unix/:7100" > > Norm wrote: > > > Sorry for the delay but I don't get on the 737 very often any more. > > > > Anyway, while I was watching it boot today, I noticed that during the boot > > process it said that the startup of the Font Server failed. That's probably > > why we can't execute 'init 5' to start X Window. Since we can execute the > > 'startx' script, everything we need is obviously there, but, I'd guess, not > > in the right places. What do I need to do to get the Font Server to start > > up during bootup? > > Go into /etc/init.d directory and search for xfs. > Login as root > do ./xfs start > Did it start or failed? > > > > > Okay -- quick summary: 1. Linux based on RedHat 6.2 with 2.2.18 kernel with Real-Time Linux v3.1 patches applied. 2. Pentium III on a Single Board Computer with on-board Chips Technology (CT) 69000 AGP with 2 MB video memory. 3. If we try to execute 'init 5' the system goes into a endless -- and uninterruptible -- cycling of trying and failing to start the X Window system 4. If, at a text shell prompt, we execute 'startx' the X Window system starts perfectly. 5. During bootup one of the messages is that the X-Font Server failed to start. A. I changed the FontPath line in the XF86Config file as directed above. B.. I executed '/etc/rc.d/init.d/xfs start' and it (apparently) succeeds. BUT .. trying to execute 'startx' afterwards fails with the message [not exact wording] "...can't find font: fixed ..." and the system starts the endless trying-to-start-and-failing loop. It was necessary to change the FontServer back to -1 in order to have 'startx' work. AND 'init 5' fails as before. Clearly we can manually execute 'startx' after logging into a text shell each time but we'd really like to get it to happen automatically on bootup. Any suggestions? Norm ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Partially successful installation/startup
Note, I sent you two separate mail on what to try out. One with xfs and the other without. Have a good weekend! Bukie Norm wrote: It'll be (at least) Monday before I get back on the aircraft but I definitely will do those things. Thanks much. Norm - Original Message - From: Bukie Mabayoje [EMAIL PROTECTED] To: xfree86@xfree86.org Sent: Friday, March 11, 2005 3:49 PM Subject: Re: [XFree86] Partially successful installation/startup 1. Remove this line from your configuration file and try it again FontPath /usr/X11R6/lib/X11/fonts/TrueType 2. Also, make sure you have FontPath unix/:7100 3. Make sure xfs is running do ps -eaf | grep xfs to verify 4. Check the port number do netstat -a | grep 7100 to verify Norm wrote: RESENDING BECAUSE I GOT A MESSAGE THAT THE POSTING HAD BEEN DELETED BECAUSE OF AN ATTACHMENT. Sorry for the delay but I don't get on the 737 very often any more. Anyway, while I was watching it boot today, I noticed that during the boot process it said that the startup of the Font Server failed. That's probably why we can't execute 'init 5' to start X Window. Since we can execute the 'startx' script, everything we need is obviously there, but, I'd guess, not in the right places. What do I need to do to get the Font Server to start up during bootup? Thanks Norm THE XF86CONFIG FILE FOLLOWS THIS LINE # 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 /usr/X11R6/lib/X11/fonts/TrueType FontPath unix/:-1 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 CrtlAltBS server abort sequence # This allows clients to receive this key event. #DontZap # Uncomment this to disable the CrtlAltKP_+/KP_- mode switching # sequences. This allows clients to receive these key events. #DontZoom EndSection # ** # Input devices # ** # ** # Keyboard section # ** Section Keyboard Protocol Standard # when using XQUEUE, comment out the above line, and uncomment the # following line #Protocol Xqueue AutoRepeat 500 5 # Let the server do the NumLock processing. This should only be # required when using pre-R6 clients #ServerNumLock # Specify which keyboard LEDs can be user-controlled (eg, with xset(1)) #Xleds 1 2 3 #To set the LeftAlt to Meta, RightAlt key to ModeShift, #RightCtl key to Compose, and ScrollLock key to ModeLock: LeftAlt Meta RightAlt Meta ScrollLock Compose RightCtl Control # To disable the XKEYBOARD extension, uncomment XkbDisable. # XkbDisable # To customise the XKB settings to suit your keyboard, modify the # lines below (which are the defaults). For example, for a non-U.S. # keyboard, you will probably want to use: # XkbModel pc102 # If you have a US Microsoft Natural keyboard, you can use: # XkbModel microsoft # # Then to change the language, change the Layout setting. # For example, a german layout can be obtained with: # XkbLayout de # or: # XkbLayout de # XkbVariant nodeadkeys # # If you'd like to switch the positions of your capslock and # control keys, use: # XkbOptions
Re: [XFree86] Partially successful installation/startup
I have being in that environment before, so don't let us break the rules. Norm wrote: No. It's the only Linux computer in the airplane though I suppose I could bring in a portable after clearing it with security. I'll have to think about the possibility of that. There's a pure MS-DOS computer and a Windows 95 box but I'm not sure if the Win95 PC even has a NIC. WHOA. We've got several Silicon Graphics IRIX computers in there. I'll see if I can work a telnet connection (even a temporary one) from the Indigo2 -- assuming we don't tell security about it until after we've done it. [They really hate the I've done the following:... messages but there's not much they can do about it except slap my hand and since I'm overdue for retirement anyway ...] Thanks for the suggestion. Norm - Original Message - From: Bukie Mabayoje [EMAIL PROTECTED] To: xfree86@xfree86.org Sent: Friday, March 11, 2005 3:40 PM Subject: Re: [XFree86] Partially successful installation/startup Can you telnet to the system? Norm wrote: You've already got the Configuration File which was posted before with just the recommended change of the FontServer socket. I'm not sure how to get a log file if I have to cycle power to regain control of the system because the process is cycling and uninterruptible. I suppose I could try to write a QD shell script to sleep for a few seconds and then perform a shutdown. Do you think this would work? Norm - Original Message - From: Bukie Mabayoje [EMAIL PROTECTED] To: xfree86@xfree86.org Sent: Friday, March 11, 2005 3:19 PM Subject: Re: [XFree86] Partially successful installation/startup Post the log and configuration file when you try to start X automatically. Norm wrote: - Original Message - From: Bukie Mabayoje [EMAIL PROTECTED] To: xfree86@xfree86.org Sent: Wednesday, March 09, 2005 7:31 PM Subject: Re: [XFree86] Partially successful installation/startup You need to update the Font Server Port # in your configuration file. Change the line FontPath unix/:-1 to FontPath unix/:7100 Norm wrote: Sorry for the delay but I don't get on the 737 very often any more. Anyway, while I was watching it boot today, I noticed that during the boot process it said that the startup of the Font Server failed. That's probably why we can't execute 'init 5' to start X Window. Since we can execute the 'startx' script, everything we need is obviously there, but, I'd guess, not in the right places. What do I need to do to get the Font Server to start up during bootup? Go into /etc/init.d directory and search for xfs. Login as root do ./xfs start Did it start or failed? Okay -- quick summary: 1. Linux based on RedHat 6.2 with 2.2.18 kernel with Real-Time Linux v3.1 patches applied. 2. Pentium III on a Single Board Computer with on-board Chips Technology (CT) 69000 AGP with 2 MB video memory. 3. If we try to execute 'init 5' the system goes into a endless -- and uninterruptible -- cycling of trying and failing to start the X Window system 4. If, at a text shell prompt, we execute 'startx' the X Window system starts perfectly. 5. During bootup one of the messages is that the X-Font Server failed to start. A. I changed the FontPath line in the XF86Config file as directed above. B.. I executed '/etc/rc.d/init.d/xfs start' and it (apparently) succeeds. BUT .. trying to execute 'startx' afterwards fails with the message [not exact wording] ...can't find font: fixed ... and the system starts the endless trying-to-start-and-failing loop. It was necessary to change the FontServer back to -1 in order to have 'startx' work. AND 'init 5' fails as before. Clearly we can manually execute 'startx' after logging into a text shell each time but we'd really like to get it to happen automatically on bootup. Any suggestions? Norm ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86
Re: [XFree86] Partially successful installation/startup
You need to update the Font Server Port # in your configuration file. Change the line FontPath unix/:-1 to FontPath unix/:7100 Norm wrote: Sorry for the delay but I don't get on the 737 very often any more. Anyway, while I was watching it boot today, I noticed that during the boot process it said that the startup of the Font Server failed. That's probably why we can't execute 'init 5' to start X Window. Since we can execute the 'startx' script, everything we need is obviously there, but, I'd guess, not in the right places. What do I need to do to get the Font Server to start up during bootup? Go into /etc/init.d directory and search for xfs. Login as root do ./xfs start Did it start or failed? Thanks Norm - Original Message - From: Bukie Mabayoje [EMAIL PROTECTED] To: xfree86@xfree86.org Sent: Thursday, February 17, 2005 11:59 AM Subject: Re: [XFree86] Partially successful installation/startup Post your configuration file. Norm wrote: The basic setup is a Pentium-III Linux system that started with RedHat 6.2 patched with the FSM Labs GPL-version of Real-Time Linux installed from the FSM-labs installation CD-ROM. We've used it many times on several diverse systems, both desktop PCs and Single Board Computer (SBC)-based rackmount boxes with essentially no problems at all. On this particular box we had installed the system and had it running fine, then changed the SBC. Of course, the VGA chipset changed as well so we had to install the SBC-manufacturer's VGA driver and use Xconfigurator to modify the old configuration to the new system. The result is that we can successfully start the system into run-state 3 (text mode) and then login and issue a `startx` command from a text console to get the X-Window system running just fine. When we do, the output on the text console is insmod: a module named agpgart already exists XFCom_i810 Version 3.3.6 / X Window System (protocol Version 11, revision 0, vendor release 6300) Release Date: May 19 2000 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://support.intel.com/support/graphics/intel810/linuxsoftware.htm) Operating System: Linux 2.2.14-5.0 i686 [ELF] Configured drivers: SVGA: server for SVGA graphics adaptors (Patchlevel 0): i810, i810-dc100, i810e, i815, generic (using VT number 7) XF86Config: /usr/X11R6/lib/X11/XF86Config (**) stands for supplied, (--) stands for probed/default values (**) XKB: keycodes: xfree86 (**) XKB: types: default (**) XKB: compat: default (**) XKB: symbols: us(pc101) (**) XKB: geometry: pc (**) XKB: rules: xfree86 (**) XKB: model: pc101 (**) XKB: layout: us (**) Mouse: type: PS/2, device: /dev/mouse, buttons: 3 (**) Mouse: 3 button emulation (timeout: 50ms) (**) SVGA: Graphics device ID: Intel Corporation|82810E CGC [Chipset Graphics Controller] (**) SVGA: Monitor ID: My Monitor Warning: The directory /usr/X11R6/lib/X11/fonts/TrueType does not exist. Entry deleted from font path. (**) FontPath set to unix/:-1 (--) SVGA: PCI: Intel Unknown chipset (0x7125) rev 3, Memory @ 0xe800, 0xeff8 (--) SVGA: GART: allocated 4096K system ram (--) SVGA: chipset: i810e (--) SVGA: videoram: 4096k (**) SVGA: Option dac_8_bit (**) SVGA: Using 24 bpp, Depth 24, Color weight: 888 (--) SVGA: Maximum allowed dot-clock: 128.000 MHz (**) SVGA: Mode 800x600: mode clock = 36.000 (--) SVGA: i810e: Display width padded to 2496 bytes (832 pixels). (--) SVGA: Virtual resolution set to 800x600 (--) SVGA: SpeedUp code selection modified because virtualX != 1024 (--) SVGA: Intel i810e (--) SVGA: i810e: MMIO registers at 0xEFF8 (--) SVGA: i810e: Linear framebuffer at 0xE800 (--) SVGA: i810e: Using hardware cursor (--) SVGA: Setting dot clock to 36.0 MHz [ 0x10 0x1 0x40 ] [ 18 3 4 ] (--) SVGA: chose watermark 0x22008000: (tab.freq 40.0) (--) SVGA: Using XAA (XFree86 Acceleration Architecture) (--) SVGA: XAA: Solid filled rectangles (--) SVGA: XAA: Screen-to-screen copy (--) SVGA: XAA: 8x8 color expand pattern fill (--) SVGA: XAA: Indirect CPU to screen color expansion (imagetext, polytext) (--) SVGA: XAA: Using 6 128x85 areas for pixmap caching (--) SVGA: XAA: Caching tiles (--) SVGA: XAA: Horizontal and vertical lines and segments SESSION_MANAGER=local/sac:/tmp/.ICE-unix/879,tcp/sac:1037 SetKbdSettings - type: 0 rate: 19 delay: 263 snumlk: 0 SetKbdSettings - Succeeded AUDIT: Wed Feb 16 08:40:26 2005: 876 X: client 10 rejected from local host Xlib: connection
Re: [XFree86] External Lcd Problems with laptop! Aaaargh!
Alex Mavrogonatos wrote: Hi, thanks for the reply! I tried removing modelines but still nothing. The horizontal-vertical frequencies are out of the monitor's manual, but I also tried playing around with those settings because I read somewhere that sometimes a mode might be slightly out of those limits but still work with the monitor. I've actually seen this be done in windows with the help of the utility I downloaded (or at least I think I did, since I'm not an expert when it comes to frequencies in general!). That didn't work either. Since I am getting a video signal from the laptop though, is there anyway I can find out what resolution X is trying to bring up? It is not trying to bring up any resolution, because your screen section does match the hardware. Let X generate the configuration file, and then use that file as the starting point. Thanks again for your time! --- Benstead, Kevin [EMAIL PROTECTED] wrote: In my (admittedly limited) experience I've always had problems with modelines. A number of times the configuration program has put a mode line in that did not do the job. However having said that I've always been able to resolve the problem by simply removing any mode lines from the config file. Provided you have the correct horizontal and vertical refresh rates in the monitor section you should not have a problem. So try removing your mode lines from your monitor section and see what happens. All the mode line is doing is supeceding the BIOS or driver settings for the screen resolution you have chosen. Kevin email: [EMAIL PROTECTED] Tel: +44 (0)118 971 5032 __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] bugs
Post your /etc/X11/XF86Config-4 Elizabeth Lara wrote: Hi, I'm working with a mandrake linux server (10.0), my graphic enviroment was working fine but suddenly the graphic mode stop and I can't start it. I attached the log file. Thanks for your help. Elizabeth Lara UAEM Mexico --- Name: XFree86.0.log XFree86.0.logType: Text Document (application/x-unknown-content-type-txtfile) Encoding: 7bit ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] problems at startx
Agustin.Lobo wrote: Thanks Bukie, but I have both a Waitec and a ViewSonic monitor and start X with startx -- +xinerama The next two lines is from your log. (II) MGA(0): Monitor name: WAITEC LCD (II) MGA(1): Monitor name: WAITEC LCD I don't know why DDC is returning same monitor on both port. (actually don't know which one is monitor1 and which one is monitor2...) How should I set up the Monitor section? A good documentation is located at http://mirror.etf.bg.ac.yu/tldp/HOWTO/Xinerama-HOWTO/index.html Agus Dr. Agustin Lobo Instituto de Ciencias de la Tierra (CSIC) Lluis Sole Sabaris s/n 08028 Barcelona SPAIN tel 34 93409 5410 fax 34 93411 0012 [EMAIL PROTECTED] On Fri, 4 Mar 2005, Bukie Mabayoje wrote: 1. In your XF86Config-4 file you need to assign a port # for the xfs interface. Currently it is set to unix/:-1. Change the -1 to7100. Make sure the Font server is running before starting X 2. If you don't want to use the Font server then you have to specify the font location e.g. Assuming you have the following on your box FontPath /usr/lib/X11/fonts/misc FontPath /usr/lib/X11/fonts/cyrillic FontPath /usr/lib/X11/fonts/100dpi/:unscaled FontPath /usr/lib/X11/fonts/75dpi/:unscaled FontPath /usr/lib/X11/fonts/Type1 FontPath /usr/lib/X11/fonts/Speedo FontPath /usr/lib/X11/fonts/100dpi FontPath /usr/lib/X11/fonts/75dpi 3a.Your Section Monitor1 is a little confusing. According to the information returned by the DDC you have 1. a WAITEC LCD monitor not a ViewSonic VP190 2. Your Video card will only support VertRefresh 60-75Hz. So change your monitor1 VertRefresh to 60-75 3. Your Video card will only support HorizSync 31-60Khz. Change your monitor 1 HorizSync to 31-60 3b.Your Section Monitor1 is a little confusing. According to the information returned by the DDC you have 1. Your Video card will only support VertRefresh 60-75Hz. So change your monitor2 VertRefresh to 50-75 2. Your Video card will only support HorizSync 31-60Khz. Change your monitor2 HorizSync to 31-60 4. Your ModeLine should be Modeline [EMAIL PROTECTED] 80.00 992 1024 1320 1352 744 758 767 782 Agustin.Lobo wrote: Here it is, thanks for your help. Agus ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] problems at startx (modeline)
Agustin.Lobo wrote: Sorry, forgot this one: On Fri, 4 Mar 2005, Bukie Mabayoje wrote: 4. Your ModeLine should be Modeline [EMAIL PROTECTED] 80.00 992 1024 1320 1352 744 758 767 782 Where? Should I have just one Modeline for each monitor? The same one? No -- Wouldn't be same. In your previous mail you have two different monitor and they may not have the same spec. However, you don't have to specify the modeline on version 4.0.1 and above, it is computed for you Agus Agustin.Lobo wrote: Here it is, thanks for your help. Agus ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Regarding server crash
Post your /etc/X11/XF86Config prakash Raghavadass wrote: Hello, I am a support engineer in armia sytems, Infopark,Kochi,India. Please help me to get back my xserver running, i have included my error report with this mail please help me ASAP . Thanking You Regards Prakash.r --- Name: XFree86.0.log XFree86.0.logType: Text Document (application/x-unknown-content-type-txtfile) Encoding: base64 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] problems at startx
1. In your XF86Config-4 file you need to assign a port # for the xfs interface. Currently it is set to unix/:-1. Change the -1 to7100. Make sure the Font server is running before starting X 2. If you don't want to use the Font server then you have to specify the font location e.g. Assuming you have the following on your box FontPath /usr/lib/X11/fonts/misc FontPath /usr/lib/X11/fonts/cyrillic FontPath /usr/lib/X11/fonts/100dpi/:unscaled FontPath /usr/lib/X11/fonts/75dpi/:unscaled FontPath /usr/lib/X11/fonts/Type1 FontPath /usr/lib/X11/fonts/Speedo FontPath /usr/lib/X11/fonts/100dpi FontPath /usr/lib/X11/fonts/75dpi 3a.Your Section Monitor1 is a little confusing. According to the information returned by the DDC you have 1. a WAITEC LCD monitor not a ViewSonic VP190 2. Your Video card will only support VertRefresh 60-75Hz. So change your monitor1 VertRefresh to 60-75 3. Your Video card will only support HorizSync 31-60Khz. Change your monitor 1 HorizSync to 31-60 3b.Your Section Monitor1 is a little confusing. According to the information returned by the DDC you have 1. Your Video card will only support VertRefresh 60-75Hz. So change your monitor2 VertRefresh to 50-75 2. Your Video card will only support HorizSync 31-60Khz. Change your monitor2 HorizSync to 31-60 4. Your ModeLine should be Modeline [EMAIL PROTECTED] 80.00 992 1024 1320 1352 744 758 767 782 Agustin.Lobo wrote: Here it is, thanks for your help. Agus ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] problems at startx
Post your /etc/X11/XF86Config-4 Agustin.Lobo wrote: I can't start up, I normally do it with startx -- +xinerama I'd appreciate your help Thanks Dr. Agustin Lobo Instituto de Ciencias de la Tierra (CSIC) Lluis Sole Sabaris s/n 08028 Barcelona SPAIN tel 34 93409 5410 fax 34 93411 0012 [EMAIL PROTECTED] --- This is a pre-release version of XFree86, and is not supported in any way. Bugs may be reported to XFree86@XFree86.Org and patches submitted to [EMAIL PROTECTED] Before reporting bugs in pre-release versions, please check the latest version in the XFree86 CVS repository (http://www.XFree86.Org/cvs). XFree86 Version 4.3.0.1 Release Date: 15 August 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.19-44mdkenterprise i686 [ELF] Build Date: 18 November 2004 Before reporting problems, check http://www.XFree86.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/XFree86.0.log, Time: Wed Mar 2 17:50:46 2005 (==) Using config file: /etc/X11/XF86Config-4 (==) ServerLayout layout1 (**) |--Screen screen1 (0) (**) | |--Monitor monitor1 (**) | |--Device device1 (**) |--Screen screen2 (1) (**) | |--Monitor monitor2 (**) | |--Device device2 (**) |--Input Device Keyboard1 (**) Option XkbModel pc105 (**) XKB: model: pc105 (**) Option XkbLayout es (**) XKB: layout: es (WW) Option XkbOptions requires an string value (==) Keyboard: CustomKeycode disabled (**) |--Input Device Mouse1 (**) FontPath set to unix/:-1 (==) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (**) Option AllowMouseOpenFail (++) Xinerama: enabled Using vt 7 (--) using VT number 7 (WW) Open APM failed (/dev/apm_bios) (No such file or directory) (II) Module ABI versions: XFree86 ANSI C Emulation: 0.2 XFree86 Video Driver: 0.6 XFree86 XInput driver : 0.4 XFree86 Server Extension : 0.2 XFree86 Font Renderer : 0.4 (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.3.0.1, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (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.3.0.1, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (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 1022,700c card , rev 11 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1022,700d card , rev 00 class 06,04,00 hdr 01 (II) PCI: 00:07:0: chip 1022,7410 card , rev 02 class 06,01,00 hdr 80 (II) PCI: 00:07:1: chip 1022,7411 card , rev 01 class 01,01,8a hdr 00 (II) PCI: 00:07:3: chip 1022,7413 card , rev 01 class 06,80,00 hdr 00 (II) PCI: 00:07:4: chip 1022,7414 card , rev 07 class 0c,03,10 hdr 00 (II) PCI: 00:09:0: chip 1022,2020 card , rev 10 class 01,00,00 hdr 00 (II) PCI: 00:0b:0: chip 3388,0021 card , rev 15 class 06,04,00 hdr 01 (II) PCI: 00:0d:0: chip 9005,00cf card 10f1,2462 rev 01 class 01,00,00 hdr 80 (II) PCI: 00:0d:1: chip 9005,00cf card 10f1,2462 rev 01 class 01,00,00 hdr 80 (II) PCI: 00:0f:0: chip 10b7,9805 card 10f1,2462 rev 78 class 02,00,00 hdr 00 (II) PCI: 00:10:0: chip 10b7,9805 card 10f1,2462 rev 78 class 02,00,00 hdr 00 (II) PCI: 01:05:0: chip 102b,2527 card 102b,0f84 rev 01 class 03,00,00 hdr 00 (II) PCI:
Re: External CRT works on 1024x768 but LCD not. Please Help!!!
Alan Hourihane wrote: On Fri, Feb 18, 2005 at 03:39:28PM -0800, Bukie Mabayoje wrote: Alan Hourihane wrote: I became aware of this problem few years back (since 2003). The first time I experienced it was with a DELL laptop, and I didn't have free time then to debug it when I actually had the laptop. I going to see if I can figure the problem out (why the LCD is not working) just by reading the code. I've already done work in this area. And I've got a driver up at http://www.fairlite.demon.co.uk/intel.html if anyone wants to test it. What does this driver fix? Switching between CRT, LCD and CRT+LCD type combinations through the Fn-F7/F8 switching. Plus a few other minor fixes. This is definitely a good feature to have. Alan. ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: External CRT works on 1024x768 but LCD not. Please Help!!!
Alan Hourihane wrote: On Sat, Feb 19, 2005 at 08:17:07PM -0300, Nqnsome wrote: Hi Christian, Thanks for answering. Christian Zietz wrote: I still suppose that your BIOS only recognizes the LCD as a 800x600 one, while the CRT is recognized correctly as being able to display 1024x768. The Windows XP driver doesn't care about the BIOS but bypasses it. X on the other hand needs the BIOS to set the resolution because the information on how to do that without the BIOS is not publicly available. CU Christian Sorry, but what do you mean with how to do that? What kind of information is (not!) in the BIOS that tells X how to change the resolution? A function? A memory address? Something else? No. Christian is saying that the programming information is not publicly available so that the driver can bypass using the BIOS. Which is what the Windows drivers do. I am asking this because, if I have more information about what is possibly broken/missing in the BIOS, I can try to contact the manufacturer and ask for a fix. Without specific information it is difficult to get a useful answer from the manufacturer (COMPAL). Just tell COMPAL that the ModeAttributes field for bit 0 which is called 'Mode supported by hardware configuration' is not being set when asking the Video BIOS for available supported resolutions with the LFP (Local Flat Panel). The Video BIOS call is 0x4F01 with the mode set to 0x34 for 1024x768 at 8bpp, 0x45 for 1024x768 at 16bpp and 0x54 for 1024x768 at 32bpp. Let me write you a small program to read the value. Then can be sure if plugging the external crt confuses the BIOS. You have a very valid point :) WHY IT WORKS ON WINDOWS. Can you boot DOS? Alan. ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: [XFree86] X-windows will not start / Debian 3.1 sarge / tried variouskernels
WW I810(0) Extended BIOS function 0x5f11 not supported. The 0x5f11 should be 0x4f11. Something is messed up in your install. (unless ox5f is an OEM function that I don't know about) Try woody Thomas Milo Somers wrote: For my first Linux install experience, I chose Debian 3.1 (sarge) because I thought it would be easy for a novice to install and more likely to be compatible with my hardware, a Dell Dimension 4600 P4 2.66GHz BIOS Ver. A07, purchased about a year ago. Installing from CDs, on the first attempt, I selected the linux26 install method and allowed the install program to choose the default kernel-image-2.6.8-2-k7-smp. I think I did the config okay, but in the end, the kernel failed to load. Thinking the problem might be the kernel, on the second attempt, I went with the default install method and allowed the install program to install the default 2.4 kernel. This also failed to load. The third time, I chose install method expert26 and when the time came to manually choose the kernel to load, I selected the second line on the kernel list kernel-image-2.6.8-2-k7. Completing the basic install, the kernel did load and everything seemed to be okay. So, I proceeded to installation of X-windows, using command: apt-get install gnome-desktop-environment x-window-system gdm. During the config process, I got some warning screens along the way that said something like Unavailable modules and devices that need them: - i810-tco (Intel Corp. 82801EB/ER (ICH5/ICH5R) LPC Bridge - e100 (Intel Corp. 82562EZ 10/100 Ethernet controller), - ide-mod (Linux IDE driver) - ide-detect (Linux IDE detection) - ide-floppy (Linux IDE floppy) - ide-scsi (Linux IDE SCSI emulation layer) Nevertheless, I completed the config process. However, when it came time to start X-Windows, it did not start and I got an error screen saying X-Windows was probably not configured correctly. (I don't doubt it!) Finding myself back at the command line, I reviewed the log file /var/log/XFree86.0.log and noticed the following significant warnings and errors: WW Open APM failed. WW I810(0) Extended BIOS function 0x5f11 not supported. EE I810(0): No video BIOS modes for chosen depth. EE Screens found, but none have a usable configuration. and finally: Fatal Server Error: No screens found. At this point, I followed someone's suggestion to try yet another kernel. I chose kernel-2.6.8-2-386.That kernel loaded okay and so I attempted the install of gnome and x-window system. When I completed the loading and config and rebooted, I did not get the same error screen, but nevertheless x did not start and when I checked log file /var/log/XFree86.0.log I found the same warnings and errors: WW Open APM failed (dev/apm_bios) WW I810(0) Extended BIOS function 0x5f11 not supported. EE I810(0): No video BIOS modes for chosen depth. EE Screens found, but none have a usable configuration. Fatal Server Error: No screens found. It does look like I am missing the right driver for my video controller, but I am at a loss as to where to look for a solution. I expected a Dell Intel machine to be pretty standard, with a good chance of Linux-compatibility, but I guess I was wrong. At this point, I don't know whether I made config errors, whether I am using the wrong kernel, or whether my hardware is incompatible with Debian 3.1 (sarge) and I need to try the stable Debian 3.0 (woody). But will even woody be compatible with my computer? At this point, I think I need the help of an expert, so I invite suggestions to help me move forward getting the X-Window systems to run. Thx in advance. Tom Tom (my email: [EMAIL PROTECTED]) ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: External CRT works on 1024x768 but LCD not. Please Help!!!
Read my comments in blue. And I am still looking into this. Nqnsome wrote: Hi, Can someone help me, please!? I have a Compal CY27 laptop. The graphics chipset is (as reported by lspci): :00:02.0 VGA compatible controller: Intel Corp. 82852/855GM Integrated Graphics Device (rev 02) :00:02.1 Display controller: Intel Corp. 82852/855GM Integrated Graphics Device (rev 02) The 82852GM supports two independent display. You have one at 00:02:.0 and the other at 00:02.1. You are configured to use BusID "PCI:0:2:0". I am not sure which video port 0:2:0 drivers. One thing you can try is change BusID to "PCI:0:2:1". I read all material on the net about the memory/vbios problems with this chipset. I do not think I have this problem because I can change the memory allocated to the graphics card in the BIOS setup program, and the XFree output reflects these changes. I have tried all kinds of patchs, all the latest XFree versions available (including 4.4.0), several distros (FC1, FC2, Mandrake 10 and now, Debian unstable), the IBM driver, asked the dealer and manufacturer for a BIOS update, but my LCD never reaches 1024x768 (only 800x600 and 640x480). Actually, a few months ago, I gave out trying to make the LCD work under 1024x768, after all this dozens of failed trials. I am getting back to this because I just find out that, if I connect a external CRT monitor (actually a Samsung SyncMaster 700p) to the CRT out of my laptop, 1024x768 works on it! I am completely puzzled. I suspect the reason it works is that your system have two graphics controller. And one of it is the 350Mhz 24-bit RAMDAC that support a regular scan analog monitor. If XFree can make the external monitor works on 1024x768, why it can not do the same with the LCD? LCD and CRT don't use same code. I was told that my graphics chipset has a vbios problem that prevents Xfree from recognizing its ability to work under 1024x768, but, if this is true, why that external CRT works under 1024x768? I must note that under WinXP the LCD works on 1024x768 and that the XiG X server can also do the same. Now that it is clear that Xfree can produce 1024x768 with my chipset and my LCD supports 1024x768, how can I force Xfree to try 1024x768 on the LCD? My XF86Config-4 can be found here: http://paginas.terra.com.br/educacao/nqnsome/xf86config.txt The XFree output can be found here: http://paginas.terra.com.br/educacao/nqnsome/xfree_output.txt I am really sorry for my bad English. Thanks a lot for your assistance. Regards, Sergio ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.8.8 - Release Date: 2/14/2005 ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: External CRT works on 1024x768 but LCD not. Please Help!!!
Alex Deucher wrote: On Fri, 18 Feb 2005 17:03:33 -0300, SLCB [EMAIL PROTECTED] wrote: Hi, Thanks a lot for replying, really! The 82852GM supports two independent display. You have one at 00:02:.0 and the other at 00:02.1. You are configured to use BusID PCI:0:2:0. I am not sure which video port 0:2:0 drivers. One thing you can try is change BusID to PCI:0:2:1.I suspect the reason it works is that your system have two graphics controller. And one of it is the 350Mhz 24-bit RAMDAC that support a regular scan analog monitor. Are these BusIDs related to the display pipes reported in the Xfree log: ... (II) I810(0): Display Info: CRT: attached: TRUE, present: TRUE, size: (800,600) (II) I810(0): Display Info: TV: attached: FALSE, present: TRUE, size: (800,600) (II) I810(0): Display Info: DFP (digital flat panel): attached: FALSE, present: FALSE, size: (0,0) (II) I810(0): Display Info: LFP (local flat panel): attached: TRUE, present: TRUE, size: (1024,768) (II) I810(0): Display Info: TV2 (second TV): attached: FALSE, present: FALSE, size: (0,0) (II) I810(0): Display Info: DFP2 (second digital flat panel): attached: FALSE, present: FALSE, size: (0,0) (II) I810(0): Currently active displays on Pipe A: (II) I810(0): CRT (II) I810(0): No active displays on Pipe B. ... I mean: Display Pipe A = BusID PCI:0:2:0 Display Pipe B = BusID PCI:0:2:1 or vice-versa? no. the second one is just a placeholder for the windows drivers so you get: Intel 82852GM Display controller Intel 82852GM Display controller (secondary) in the windows device manager. you'll want to use the primary id for both heads. Alex is correct. Let focus on the primary display controller on PCI:0:2:0 with Display Pipe A and Display Pipe B. In your case you can only have PipeA=CRT and PipeB=LCD (LFP). That is why you have the following information (II) I810(0): Display Info: CRT: attached: TRUE, present: TRUE, size: (800,600) (II) I810(0): Display Info: LFP (local flat panel): attached: TRUE, present: TRUE, size: (1024,768) The problem is why XFree is saying there is no active display on Pipe B (II) I810(0): No active displays on Pipe B Alex ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: External CRT works on 1024x768 but LCD not. Please Help!!!
SLCB wrote: Hi, Thanks a lot for replaying!!! Alex Deucher wrote: it should use 02.0. .1 is just a placeholder for the windows drivers AFAIK. Sorry if this is a stupid question, but what exactly means to be placeholder in this case? There is a technical meaning for 02.1 It is on PCI Bus 0, Device Id 2 function 0 or function 1. That is what Alex meant when he said you have two device on one component. Thanks a lot. Regards, Sergio -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.8.8 - Release Date: 2/14/2005 ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: External CRT works on 1024x768 but LCD not. Please Help!!!
Nqnsome wrote: Hi, Thanks again. Alex Deucher wrote: Alex is correct. Let focus on the primary display controller on PCI:0:2:0 with Display Pipe A and Display Pipe B. In your case you can only have PipeA=CRT and PipeB=LCD (LFP). That is why you have the following information (II) I810(0): Display Info: CRT: attached: TRUE, present: TRUE, size: (800,600) (II) I810(0): Display Info: LFP (local flat panel): attached: TRUE, present: TRUE, size: (1024,768) The problem is why XFree is saying there is no active display on Pipe B (II) I810(0): No active displays on Pipe B you can use the monitorlayout option to force on the pipes. see the i810 man page. Alex Now I understand the Pipes, but is still a mistery for me why lspci sees the 0:2:1, if it is a Windows placeholder (propably because I do not understand what a placeholder is...). Regarding the No active displays on Pipe B, this probably happens because, before starting X, I disable the LCD with the keyboard sequence FN+F5. If I do not do this, the screen becomes unreadble I became aware of this problem few years back (since 2003). The first time I experienced it was with a DELL laptop, and I didn't have free time then to debug it when I actually had the laptop. I going to see if I can figure the problem out (why the LCD is not working) just by reading the code. (I guess because the CRT works in 1024x768 and the LCD do not). Not exactly. Both the crt and lcd support 1024x768 Thanks a lot for the explanations, but I would like to return to the question why the CRT works under 1024x768 and the LCD not. Can this be related to the VESA VBE DCC that does not work on the LCD? no Thanks again. Regards, Sergio -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.8.8 - Release Date: 2/14/2005 ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: External CRT works on 1024x768 but LCD not. Please Help!!!
Alan Hourihane wrote: I became aware of this problem few years back (since 2003). The first time I experienced it was with a DELL laptop, and I didn't have free time then to debug it when I actually had the laptop. I going to see if I can figure the problem out (why the LCD is not working) just by reading the code. I've already done work in this area. And I've got a driver up at http://www.fairlite.demon.co.uk/intel.html if anyone wants to test it. What does this driver fix? Alan. ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: [XFree86] Abort X server
Omar Barneto wrote: I'am running the X server over a linux machine (kernel version 2.4.20) and sometimes the server abort with the error: fatal server error Caught signal 4.Server aborting How I can avoid this problem or ignore the signal 4.What do signal 4 means.? You may have a memory corruption issue. signal 4 is SIGILL which means illegal instruction. Can you explain how and when this happens? Need to know if it is at the the same spot every time. Just a suggestion you are running fairly old Xfree 4.2..0 why not upgrade to a later version 4.4.0 or 4.3.0 Thanks in advance. --- XFree86 Version 4.2.0 (Red Hat Linux release: 4.2.0-72) / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 23 January 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-11smp i686 [ELF] Build Host: daffy.perf.redhat.com Module Loader present OS Kernel: Linux version 2.4.20 ([EMAIL PROTECTED]) (gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7)) #8 Tue Oct 5 16:14:04 ART 2004 P 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: Fri Feb 18 08:19:00 2005 (==) Using config file: /etc/X11/XF86Config (==) ServerLayout Default Layout (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device Videocard0 (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc105 (**) XKB: model: pc105 (==) Keyboard: CustomKeycode disabled (**) FontPath set to unix/:7100 (**) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (--) using VT number 2 (WW) Open APM failed (/dev/apm_bios) (No such file or directory) (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.0, 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.0, 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 = 0x80003bc0, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1106,0601 card 1106,0601 rev 05 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1106,8601 card , rev 00 class 06,04,00 hdr 01 (II) PCI: 00:07:0: chip 1106,0686 card 1106, rev 40 class 06,01,00 hdr 80 (II) PCI: 00:07:1: chip 1106,0571 card 1106,0571 rev 06 class 01,01,8a hdr 00 (II) PCI: 00:07:2: chip 1106,3038 card 0925,1234 rev 1a class 0c,03,00 hdr 00 (II) PCI: 00:07:3: chip 1106,3038 card 0925,1234 rev 1a class 0c,03,00 hdr 00 (II) PCI: 00:07:4: chip 1106,3057 card 1106,3057 rev 40 class 06,80,00 hdr 00 (II) PCI: 00:07:5: chip 1106,3058 card 1106,3058 rev 50 class 04,01,00 hdr 00 (II) PCI: 00:09:0: chip 10ec,8139 card 10ec,8139 rev 10 class 02,00,00 hdr 00 (II) PCI: 01:00:0: chip 1023,8500 card 1023,8500 rev 6a class 03,00,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.0, module version =
Re: External CRT works on 1024x768 but LCD not. Please Help!!!
I can't look into this problem tonight I will be able to see if I can help you tomorrow. If you need to use your laptop without the external crt, use the vesa driver for now. Nqnsome wrote: Hi, Can someone help me, please!? I have a Compal CY27 laptop. The graphics chipset is (as reported by lspci): :00:02.0 VGA compatible controller: Intel Corp. 82852/855GM Integrated Graphics Device (rev 02) :00:02.1 Display controller: Intel Corp. 82852/855GM Integrated Graphics Device (rev 02) I read all material on the net about the memory/vbios problems with this chipset. I do not think I have this problem because I can change the memory allocated to the graphics card in the BIOS setup program, and the XFree output reflects these changes. I have tried all kinds of patchs, all the latest XFree versions available (including 4.4.0), several distros (FC1, FC2, Mandrake 10 and now, Debian unstable), the IBM driver, asked the dealer and manufacturer for a BIOS update, but my LCD never reaches 1024x768 (only 800x600 and 640x480). Actually, a few months ago, I gave out trying to make the LCD work under 1024x768, after all this dozens of failed trials. I am getting back to this because I just find out that, if I connect a external CRT monitor (actually a Samsung SyncMaster 700p) to the CRT out of my laptop, 1024x768 works on it! I am completely puzzled. If XFree can make the external monitor works on 1024x768, why it can not do the same with the LCD? I was told that my graphics chipset has a vbios problem that prevents Xfree from recognizing its ability to work under 1024x768, but, if this is true, why that external CRT works under 1024x768? I must note that under WinXP the LCD works on 1024x768 and that the XiG X server can also do the same. Now that it is clear that Xfree can produce 1024x768 with my chipset and my LCD supports 1024x768, how can I force Xfree to try 1024x768 on the LCD? My XF86Config-4 can be found here: http://paginas.terra.com.br/educacao/nqnsome/xf86config.txt The XFree output can be found here: http://paginas.terra.com.br/educacao/nqnsome/xfree_output.txt I am really sorry for my bad English. Thanks a lot for your assistance. Regards, Sergio ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.8.8 - Release Date: 2/14/2005 ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: [XFree86] Partially successful installation/startup
Post your configuration file. Norm wrote: The basic setup is a Pentium-III Linux system that started with RedHat 6.2 patched with the FSM Labs GPL-version of Real-Time Linux installed from the FSM-labs installation CD-ROM. We've used it many times on several diverse systems, both desktop PCs and Single Board Computer (SBC)-based rackmount boxes with essentially no problems at all. On this particular box we had installed the system and had it running fine, then changed the SBC. Of course, the VGA chipset changed as well so we had to install the SBC-manufacturer's VGA driver and use Xconfigurator to modify the old configuration to the new system. The result is that we can successfully start the system into run-state 3 (text mode) and then login and issue a `startx` command from a text console to get the X-Window system running just fine. When we do, the output on the text console is insmod: a module named agpgart already exists XFCom_i810 Version 3.3.6 / X Window System (protocol Version 11, revision 0, vendor release 6300) Release Date: May 19 2000 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://support.intel.com/support/graphics/intel810/linuxsoftware.htm) Operating System: Linux 2.2.14-5.0 i686 [ELF] Configured drivers: SVGA: server for SVGA graphics adaptors (Patchlevel 0): i810, i810-dc100, i810e, i815, generic (using VT number 7) XF86Config: /usr/X11R6/lib/X11/XF86Config (**) stands for supplied, (--) stands for probed/default values (**) XKB: keycodes: xfree86 (**) XKB: types: default (**) XKB: compat: default (**) XKB: symbols: us(pc101) (**) XKB: geometry: pc (**) XKB: rules: xfree86 (**) XKB: model: pc101 (**) XKB: layout: us (**) Mouse: type: PS/2, device: /dev/mouse, buttons: 3 (**) Mouse: 3 button emulation (timeout: 50ms) (**) SVGA: Graphics device ID: Intel Corporation|82810E CGC [Chipset Graphics Controller] (**) SVGA: Monitor ID: My Monitor Warning: The directory /usr/X11R6/lib/X11/fonts/TrueType does not exist. Entry deleted from font path. (**) FontPath set to unix/:-1 (--) SVGA: PCI: Intel Unknown chipset (0x7125) rev 3, Memory @ 0xe800, 0xeff8 (--) SVGA: GART: allocated 4096K system ram (--) SVGA: chipset: i810e (--) SVGA: videoram: 4096k (**) SVGA: Option dac_8_bit (**) SVGA: Using 24 bpp, Depth 24, Color weight: 888 (--) SVGA: Maximum allowed dot-clock: 128.000 MHz (**) SVGA: Mode 800x600: mode clock = 36.000 (--) SVGA: i810e: Display width padded to 2496 bytes (832 pixels). (--) SVGA: Virtual resolution set to 800x600 (--) SVGA: SpeedUp code selection modified because virtualX != 1024 (--) SVGA: Intel i810e (--) SVGA: i810e: MMIO registers at 0xEFF8 (--) SVGA: i810e: Linear framebuffer at 0xE800 (--) SVGA: i810e: Using hardware cursor (--) SVGA: Setting dot clock to 36.0 MHz [ 0x10 0x1 0x40 ] [ 18 3 4 ] (--) SVGA: chose watermark 0x22008000: (tab.freq 40.0) (--) SVGA: Using XAA (XFree86 Acceleration Architecture) (--) SVGA: XAA: Solid filled rectangles (--) SVGA: XAA: Screen-to-screen copy (--) SVGA: XAA: 8x8 color expand pattern fill (--) SVGA: XAA: Indirect CPU to screen color expansion (imagetext, polytext) (--) SVGA: XAA: Using 6 128x85 areas for pixmap caching (--) SVGA: XAA: Caching tiles (--) SVGA: XAA: Horizontal and vertical lines and segments SESSION_MANAGER=local/sac:/tmp/.ICE-unix/879,tcp/sac:1037 SetKbdSettings - type: 0 rate: 19 delay: 263 snumlk: 0 SetKbdSettings - Succeeded AUDIT: Wed Feb 16 08:40:26 2005: 876 X: client 10 rejected from local host Xlib: connection to :0.0 refused by server Xlib: Client is not authorized to connect to Server xscreensaver: Can't open display: :0 xscreensaver: initial effective uid/gid was root/root (0/0) xscreensaver: running as nobody/nobody (99/99) xscreensaver: Errors at startup are usually authorization problems. Did you read the manual and the FAQ? Specifically, the parts of the manual that talk about XAUTH, XDM, and root logins? http://www.jwz.org/xscreensaver/man.html subshell.c: couldn't get terminal settings: Inappropriate ioctl for device X connection to :0.0 broken (explicit kill or server shutdown). Gdk-ERROR **: X connection to :0.0 broken (explicit kill or server shutdown). X connection to :0.0 broken (explicit kill or server shutdown). X connection to :0.0 broken (explicit kill or server shutdown). Gdk-ERROR **: X connection to :0.0 broken (explicit kill or server shutdown). Gdk-WARNING **: GdkWindow 0x385 unexpectedly destroyed Gdk-ERROR **: X connection to :0.0 broken (explicit kill or server shutdown). Gdk-ERROR **: X connection to :0.0 broken (explicit kill or server shutdown). Gdk-ERROR **: X connection to :0.0 broken (explicit kill or
Re: [XFree86] CVS XFree86 i830 failure on DELL inspiron 2600
Nicolas Joly wrote: On Wed, Feb 16, 2005 at 06:23:24PM -0500, David Dawes wrote: > On Wed, Feb 16, 2005 at 09:00:43PM +0100, Nicolas Joly wrote: > > > >Hi, > > > >I just tried CVS XFree86 on my DELL Inspiron 2600 with Intel 82830MP > >Integrated Video running under NetBSD/i386, and got bad results ... > >This machine worked flawlessly with the previous release (4.4.0), with > >1024x768, depth 16. > > > >When i try to start the server, problems begins ... The LFP remains > >black and the server start eating all the CPU ! > > I'd guess from the log that it is getting stuck setting the video mode. > However, you would need to either attach to the XFree86 process with > gdb, or kill it (with SIGSEGV or SIGQUIT) and run gdb on the resulting > core to find our for certain. Perhaps Alan has some ideas about what > is going wrong here. To help debugging, i recompiled everything with `-g -O0' and made the server static. It seems that you're right, according to the 2 following traces : (gdb) bt #0 0x0847011e in write_w (pInt=0x8af5a00, addr=8080, val=48988) at generic.c:532 #1 0x0848a94d in pushw (pInt=0x8af5a00, val=48988) at helper_exec.c:95 #2 0x0848a99c in run_bios_int (num=0, pInt=0x8af5a00) at helper_exec.c:134 #3 0x0848bd2d in int_handler (pInt=0x8af5a00) at xf86int10.c:53 #4 0x0846f063 in x86emu_do_int (num=0) at xf86x86emu.c:25 #5 0x08470535 in x86emu_intr_handle () at decode.c:57 #6 0x0847064a in X86EMU_exec () at decode.c:113 #7 0x0846f0a7 in xf86ExecX86int10 (pInt=0x8af5a00) at xf86x86emu.c:39 #8 0x08462b27 in VBESetVBEMode (pVbe=0x8b04480, mode=49223, block=0x0) at vbe.c:526 #9 0x082b4016 in I830VESASetVBEMode (pScrn=0x8af2800, mode=49223, block=0x0) at i830_driver.c:3375 #10 0x082b4131 in I830VESASetMode (pScrn=0x8af2800, pMode=0x8b0f000) at i830_driver.c:3450 #11 0x082b6d41 in I830BIOSEnterVT (scrnIndex=0, flags=0) at i830_driver.c:4841 #12 0x082b5bb2 in I830BIOSScreenInit (scrnIndex=0, pScreen=0x8b01e00, argc=3, argv=0xbfbfebec) at i830_driver.c:4302 #13 0x084b1c2c in AddScreen (pfnInit=0x82b53f0 I830BIOSScreenInit>, argc=3, argv=0xbfbfebec) at main.c:763 #14 0x08413b8a in InitOutput (pScreenInfo=0x8ae92e0, argc=3, argv=0xbfbfebec) at xf86Init.c:1145 #15 0x084b0f13 in main (argc=3, argv=0xbfbfebec, envp=0xbfbfebfc) at main.c:355 #16 0x0804bdb6 in ___start () #0 Mem_rw (addr=0) at helper_exec.c:434 #1 0x0847d1ec in x86emuOp_iret (op1=207 '') at ops.c:8904 #2 0x0847068f in X86EMU_exec () at decode.c:117 #3 0x0846f0a7 in xf86ExecX86int10 (pInt=0x8af5a00) at xf86x86emu.c:39 #4 0x08462b27 in VBESetVBEMode (pVbe=0x8b04480, mode=49223, block=0x0) at vbe.c:526 #5 0x082b4016 in I830VESASetVBEMode (pScrn=0x8af2800, mode=49223, block=0x0) at i830_driver.c:3375 #6 0x082b4131 in I830VESASetMode (pScrn=0x8af2800, pMode=0x8b0f000) at i830_driver.c:3450 #7 0x082b6d41 in I830BIOSEnterVT (scrnIndex=0, flags=0) at i830_driver.c:4841 #8 0x082b5bb2 in I830BIOSScreenInit (scrnIndex=0, pScreen=0x8b01e00, argc=3, argv=0xbfbfebec) at i830_driver.c:4302 #9 0x084b1c2c in AddScreen (pfnInit=0x82b53f0 I830BIOSScreenInit>, argc=3, argv=0xbfbfebec) at main.c:763 #10 0x08413b8a in InitOutput (pScreenInfo=0x8ae92e0, argc=3, argv=0xbfbfebec) at xf86Init.c:1145 #11 0x084b0f13 in main (argc=3, argv=0xbfbfebec, envp=0xbfbfebfc) at main.c:355 #12 0x0804bdb6 in ___start () The process is looping in `X86EMU_exec()'. The problem is not here. The problem happened during the I830xxx calls. I am still studying the data sheet. It seems a register/functionality is not present on the device. You can use the vesa driver if you need a working box for now. > Does the "vesa" driver still work OK? Works fine, at least, with 1024x768 at depth 16. > >I tracked the problem on the i810 driver module; and noticed that it > >appeared with the i915M support (CHANGELOG 252 - 01/09/2005). > > > >I noticed some built-in modes detection changes, and a problem with HW > >(ARGB) cursor allocation (full log attached): > > The ARGB cursor requires kernel agp support for allocating more than one > page for AGP_PHYS_MEMORY requests. From what Alan said when this I asked > about this on the devel list a couple of weeks ago, recent Linux kernels > have the necessary support for this. The NetBSD (and FreeBSD) agp modules > would need similar updates in order for this to work. I doubt that the > problem you are seeing is related to this though. Ok. I'll see this one later. -- Nicolas Joly Biological Software and Databanks. Institut Pasteur, Paris. ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Odd Screen Overlap - Fixed
I have not being following the thread since Mark is on it. But, if I understand your question. Can your monitor keep working on 75Hz instead of 60Hz. The answer is YES. As long as it is in the specified range that should be okay. Carl F. Hall wrote: Thanks for the suggestions Mark. I changed the vert sync range and horiz. range to the those you said were in the log file for the monitor's EDID. After doing so, I still had the problem but now have available 75Hz along w/ 60Hz. I didn't think my monitor worked at anything by 60 but whatever. So I selected 75Hz and the overlap went away! If this will detremental to my monitor, someone please let me know. Otherwise, I'm going to keep on going with it. Thanks again for all of the very knowledgeable help. _Carl Mark Vojkovich wrote: The monitor's EDID (printed out in the logfile) indicates a prefered mode, which implies the native panel resolution is 1280x1024. It also specifies a vertical sync range of 56-76 Hz and horizontal range of 30-80 kHz (you have 50-75 and 30-65 in your XF86Config). XFree86 chose a [EMAIL PROTECTED] (64KHz) VESA mode with an identical refresh rate to the prefered mode in the EDID. In short, the mode XFree86 chose should have worked, and it sounds like it did at one time, so I guess we can't rule out a hardware issue. You can try changing the sync pulses. It's using the following modeline now: Modeline 1280x1024 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync If you put that line in the Section Monitor XFree86 will use it instead of the internal one. You can change the pulses by changing the +/- before the hsync and/or vsync. You also might want to check your monitor cable to make sure it's plugged in tightly. If this doesn't work you could try lowering that pixel clock (the 108.00) a bit to see if it works any better (eg. something between 102 and 108). Does your video card have a DVI connector? If you use it you will be bypassing your monitor's analog circuitry. Mark. On Mon, 14 Feb 2005, Carl F. Hall wrote: I have an LCD monitor that does auto adjustments based on the input and not a lot, but some, adjusting I can do manually outside of color and contrast. Other resolutions seem to work fine so I can't agree with the hardware assessment but I'm not informed enough on the area to completely disagree. Is there anything I can change in the config to change the vertical synch pulses and maybe fix it that way? Doug McNutt wrote: At 10:40 -0500 2/14/05, Carl F. Hall wrote: I have an overlap at the bottom of the screen that is a copy of the first 10-15 pixels of the top of the screen. I'm running at 1280x1024. When I switch to 1024x768, the problem doesn't show. I've tried adjusting the monitor but there are useful things, namely the status bar, behind that overlap. Sounds like a typical hardware problem. The internal adjustment in your monitor is probably called vertical phase. The monitor is failing to synch tightly to the vertical synch pulses form the video card when the rate is pushed too high. If you're lucky it's just an internal adjustment but it's more-often due to change in value of a capacitor on the printed circuit board. I doubt that those pixels are actually copies but if they are I'm all wrong. The video card would have to be thoroughly messed up to send some pixels twice. It's extremely rare for that kind of problem to originate in a video card. -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.306 / Virus Database: 265.8.7 - Release Date: 2/10/2005 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.306 / Virus Database: 265.8.7 - Release Date: 2/10/2005 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Problem with programs/Xserver/GL/glx/glxcmds.c
This is a mesa issue.
"Willing, John (J.K.)" wrote:
While running with a commercial CAD
program, we encountered a problem with the OpenGL libraries.
In Function DoMakeCurrent
640 if (prevglxc) {
641
if (prevglxc->drawPixmap) {
642
if (prevglxc->drawPixmap != prevglxc->readPixmap) {
643
/*
644
** The previous drawable was a glx pixmap, release it.
645
*/
646
prevglxc->readPixmap->refcnt--;
We came across a problem where prevglxc->readPixmap
is NULL causing a Segmentation Fault at line 646. I resolved the
issue by changing line 641 to:
641
if (prevglxc->drawPixmap prevglxc->readPixmap) {
John Willing
Re: [Mesa3d-dev] Re: [XFree86] Problem with programs/Xserver/GL/glx/glxcmds.c
I may be wrong, I thought we get all the glx stuff from your group.
Ian Romanick wrote:
Brian Paul wrote:
Bukie Mabayoje wrote:
This is a mesa issue.
Willing, John (J.K.) wrote:
While running with a commercial CAD program, we encountered a problem
with the OpenGL libraries.
In Function DoMakeCurrent
640 if (prevglxc) {
641 if (prevglxc-drawPixmap) {
642 if (prevglxc-drawPixmap != prevglxc-readPixmap) {
643 /*
644 ** The previous drawable was a glx pixmap,
release it.
645 */
646 prevglxc-readPixmap-refcnt--;
We came across a problem where prevglxc-readPixmap is NULL causing a
Segmentation Fault at line 646. I resolved the issue by changing
line 641 to:
641 if (prevglxc-drawPixmap prevglxc-readPixmap) {
John Willing
What file is that in?
It's in programs/Xserver/GL/glx/glxcmds.c. This file is *NOT* in the
Mesa tree. This is part of the Xserver. Bukie, how do you figure that
this is a Mesa problem?
___
XFree86 mailing list
XFree86@XFree86.Org
http://XFree86.Org/mailman/listinfo/xfree86
Re: [Mesa3d-dev] Re: [XFree86] Problem with programs/Xserver/GL/glx/glxcmds.c
The file is located Mesa/src/glx/x11 in your tree
and xc/programs/Xserver/GLglx in the Xfree86 tree.
But they are both out of sync. My Assumption is that Xfree86 uses the mesa
stuff. I may be wrong.
Brian Paul wrote:
Bukie Mabayoje wrote:
This is a mesa issue.
Willing, John (J.K.) wrote:
While running with a commercial CAD program, we encountered a problem
with the OpenGL libraries.
In Function DoMakeCurrent
640 if (prevglxc) {
641 if (prevglxc-drawPixmap) {
642 if (prevglxc-drawPixmap != prevglxc-readPixmap) {
643 /*
644 ** The previous drawable was a glx pixmap,
release it.
645 */
646 prevglxc-readPixmap-refcnt--;
We came across a problem where prevglxc-readPixmap is NULL causing a
Segmentation Fault at line 646. I resolved the issue by changing line
641 to:
641 if (prevglxc-drawPixmap prevglxc-readPixmap) {
John Willing
What file is that in?
-Brian
___
XFree86 mailing list
XFree86@XFree86.Org
http://XFree86.Org/mailman/listinfo/xfree86
___
XFree86 mailing list
XFree86@XFree86.Org
http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Emailing: XFree86.0.log
You don't have font server running. Or you can take the unix:/7000 out of your configuration file if you have locally installed fonts. Anyway, check past mail about other who have the same problem. Yissakhar Beck wrote: Dear sir, My X widow system doesn't start right any more, what's the problem? If it's that I am missing some files, please e-mail hem to me with instructions. Sincerly, A wanting customer --- _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 _XSERVTransOpen: transport open failed for inet6/localhost.localdomain:0 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 XFree86 Version 4.4.0 Release Date: 29 February 2004 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.18-14 i686 [ELF] Current Operating System: Linux localhost.localdomain 2.4.20-31.9 #1 Tue Apr 13 17:38:41 EDT 2004 i686 Build Date: 27 February 2004 Changelog Date: 29 February 2004 Before reporting problems, check http://www.XFree86.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/XFree86.0.log, Time: Sun Feb 13 08:26:12 2005 (==) Using config file: /etc/X11/XF86Config (==) ServerLayout Default Layout (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device Videocard0 (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc105 (**) XKB: model: pc105 (**) Option XkbLayout us (**) XKB: layout: us (==) Keyboard: CustomKeycode disabled (**) |--Input Device DevInputMice (**) FontPath set to unix/:7100 (**) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (II) Open APM successful (II) Module ABI versions: XFree86 ANSI C Emulation: 0.2 XFree86 Video Driver: 0.7 XFree86 XInput driver : 0.4 XFree86 Server Extension : 0.2 XFree86 Font Renderer : 0.4 (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.4.0, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (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.4.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.7 (--) using VT number 7 (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,1130 card , rev 02 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,1131 card , rev 02 class 06,04,00 hdr 01 (II) PCI: 00:1e:0: chip 8086,244e card , rev 01 class 06,04,00 hdr 01 (II) PCI: 00:1f:0: chip 8086,2440 card , rev 01 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,244b card 8086,4541 rev 01 class 01,01,80 hdr 00 (II) PCI: 00:1f:2: chip 8086,2442 card 8086,4541 rev 01 class 0c,03,00 hdr 00 (II) PCI: 00:1f:3: chip 8086,2443 card 8086,4541 rev 01 class 0c,05,00 hdr 00 (II) PCI: 01:0a:0: chip 1274,5880 card 1274,2003 rev 02 class 04,01,00 hdr 00 (II) PCI: 01:0b:0: chip 10ec,8139 card 10ec,8139 rev 10 class 02,00,00 hdr 00 (II) PCI: 02:00:0: chip 10de,0100 card 10de,0007 rev 10 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,2), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x - 0x (0x1)
Re: [XFree86] XFree86 BUG
NOT XFree86 BUG . You don't have font server running Do --- ps -eaf | grep xfs to check if it is running. chamara wrote: Hello, Currently I?m being stuck with my font server. Here is the detailed log report. Glad to get out of this before running out of my blood. Need Help! XFree86 Version 4.3.0 (Red Hat Linux release: 4.3.0-2) Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.20-3bigmem i686 [ELF] Build Date: 27 February 2003 Build Host: porky.devel.redhat.com Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present OS Kernel: Linux version 2.4.20-8 ([EMAIL PROTECTED]) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 Thu Mar 13 17:54:28 EST 2003 P 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: Thu Feb 10 23:01:35 2005 (==) Using config file: /etc/X11/XF86Config (==) ServerLayout Default Layout (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device Videocard0 (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc105 (**) XKB: model: pc105 (**) Option XkbLayout us (**) XKB: layout: us (==) Keyboard: CustomKeycode disabled (**) |--Input Device DevInputMice (**) FontPath set to unix/:7100 (**) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (++) using VT number 7 (II) Open APM successful (II) Module ABI versions: XFree86 ANSI C Emulation: 0.2 XFree86 Video Driver: 0.6 XFree86 XInput driver : 0.4 XFree86 Server Extension : 0.2 XFree86 Font Renderer : 0.4 (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.3.0, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (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.3.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x80010004, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,2560 card 8086,2560 rev 03 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,2561 card , rev 03 class 06,04,00 hdr 01 (II) PCI: 00:1d:0: chip 8086,24c2 card 8086,5356 rev 02 class 0c,03,00 hdr 80 (II) PCI: 00:1d:1: chip 8086,24c4 card 8086,5356 rev 02 class 0c,03,00 hdr 00 (II) PCI: 00:1d:2: chip 8086,24c7 card 8086,5356 rev 02 class 0c,03,00 hdr 00 (II) PCI: 00:1d:7: chip 8086,24cd card 8086,5356 rev 02 class 0c,03,20 hdr 00 (II) PCI: 00:1e:0: chip 8086,244e card , rev 82 class 06,04,00 hdr 01 (II) PCI: 00:1f:0: chip 8086,24c0 card , rev 02 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,24cb card 8086,5356 rev 02 class 01,01,8a hdr 00 (II) PCI: 00:1f:3: chip 8086,24c3 card 8086,5356 rev 02 class 0c,05,00 hdr 00 (II) PCI: 01:00:0: chip 10de,0110 card , rev b2 class 03,00,00 hdr 00 (II) PCI: 02:01:0: chip 1102,8938 card 1102,5938 rev 00 class 04,01,00 hdr 00 (II) PCI: 02:04:0: chip 14f1,2f00 card 14f1,2004 rev 01 class 07,80,00 hdr 00 (II) PCI: 02:05:0: chip 10b9,545a card 201f,545a rev 00 class 07,03,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,2), 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-PCI bridge: (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 1 non-prefetchable memory range: [0] -1 0 0xfc90 - 0xfe9f (0x210) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 0 0xe460 - 0xf46f (0x1010) MX[B] (II) PCI-to-PCI bridge: (II) Bus 2: bridge is at (0:30:0), (0,2,2), BCTRL: 0x0006 (VGA_EN is cleared) (II) Bus 2 I/O range: [0] -1 0 0xd000 - 0xd0ff (0x100) IX[B] [1] -1 0 0xd400 - 0xd4ff (0x100) IX[B] [2] -1 0 0xd800 - 0xd8ff (0x100) IX[B] [3] -1 0 0xdc00 - 0xdcff (0x100) IX[B] (II) Bus 2 non-prefetchable
Re: [XFree86] Xfree configuration problem
1. Can you do /sbin/lspci and post it. 2. Can you do uname -a or uname -r and post it. The 865GV chipset was released after RH 2.1 AS, maybe for some reason it is having difficult in recognizing the video controller. But I doubt it. Anyway, there is a work around that Mark posted a while back. Try Mark's suggestion . A workaround would be to specify the bus id explicitly in the Section Device of the XF86Config file. Eg.: BusIDPCI 00:02:0 Mauricio Rojas wrote: Hi Guys, I have a problem to start X with my computer. I have demo server of Linux RedHat 2.1 AS on a Asus P4P800-MX (Intel 865GV) and a Intel Extreme Graphics Could help me with the configuration please? Regards, Mauricio (II) Loading extension GLX (II) LoadModule: pex5 (II) Reloading /usr/X11R6/lib/modules/extensions/libpex5.a (II) Loading extension X3D-PEX (II) LoadModule: record (II) Loading /usr/X11R6/lib/modules/extensions/librecord.a (II) Module record: vendor=The XFree86 Project compiled for 4.1.0, module version = 1.13.0 Module class: XFree86 Server Extension ABI class: XFree86 Server Extension, version 0.1 (II) Loading extension RECORD (II) LoadModule: xie (II) Loading /usr/X11R6/lib/modules/extensions/libxie.a (II) Module xie: vendor=The XFree86 Project compiled for 4.1.0, module version = 1.0.0 Module class: XFree86 Server Extension ABI class: XFree86 Server Extension, version 0.1 (II) Loading extension XIE (II) LoadModule: i810 (II) Loading /usr/X11R6/lib/modules/drivers/i810_drv.o (II) Module i810: vendor=The XFree86 Project compiled for 4.1.0, module version = 1.0.0 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.4 (II) LoadModule: mouse (II) Loading /usr/X11R6/lib/modules/input/mouse_drv.o (II) Module mouse: vendor=The XFree86 Project compiled for 4.1.0, module version = 1.0.0 Module class: XFree86 XInput Driver ABI class: XFree86 XInput driver, version 0.2 (II) I810: Driver for Intel i810 chipset: i810, i810-dc100, i810e, i815 (II) Primary Device is: PCI 00:02:0 (--) Assigning device section with no busID to primary device (EE) No devices detected. Fatal server error: no screens found ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] rebooting failure-
type this command who -r you should see run-level 5 If you don't see it, that means you are not running at run level 5. RH automatically starts xfs at run level 5 You can change your inittab to default to run level 5 id:5:initdefault: Or you can start it manual at your current run level --- /etc/init.d/xfs start Your problem is you don't have font server running. saji kurian wrote: from saji TAS,Bangalore today after a due to power failure the system is went off.after that i try to rebbot it ,it get into booting but i can't go to the GUI mod,after the booting. it show some error while i try to got GUI from text terminal using [EMAIL PROTECTED] root]#startx i using the cluster system having two nodes the report of the problem is attached with this mail. as in the file /var/log/XFree86.0.log i expect a solution through the mail saji bangalore 09/02/05 __ Do you Yahoo!? Yahoo! Mail - now with 250MB free storage. Learn more. http://info.mail.yahoo.com/mail_250 --- Name: XFree86.0.log XFree86.0.log Type: Text Document (application/x-unknown-content-type-txtfile) Encoding: base64 Description: XFree86.0.log ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Xfree configuration problem
I have the same chipset you have. And the lspci information is the same as yours. So this is not an hw issue. my X was able to identify the video on Kernel 2.2.20 and 2.4.18. Also, I am running a older version of XFree 4.1.0.1 so it is not XFree issue either. I don't know if demo234.isc.cl 2.4.9-e.3 = Red Hat 2.1 2.4.9-e.3. Anyway did you try Mark's workaround? Mauricio Rojas wrote: Hello, 1.- here it is the first output 00:00.0 Host bridge: Intel Corporation: Unknown device 2570 (rev 02) 00:02.0 VGA compatible controller: Intel Corporation: Unknown device 2572 (rev 02) 00:1d.0 USB Controller: Intel Corporation: Unknown device 24d2 (rev 02) 00:1d.1 USB Controller: Intel Corporation: Unknown device 24d4 (rev 02) 00:1d.2 USB Controller: Intel Corporation: Unknown device 24d7 (rev 02) 00:1d.3 USB Controller: Intel Corporation: Unknown device 24de (rev 02) 00:1d.7 USB Controller: Intel Corporation: Unknown device 24dd (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82820 820 (Camino 2) Chipset PCI (rev c2) 00:1f.0 ISA bridge: Intel Corporation: Unknown device 24d0 (rev 02) 00:1f.1 IDE interface: Intel Corporation: Unknown device 24db (rev 02) 00:1f.3 SMBus: Intel Corporation: Unknown device 24d3 (rev 02) 00:1f.5 Multimedia audio controller: Intel Corporation: Unknown device 24d5 (rev 02) 01:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 (rev 10) 2.- the second one Linux demo234.isc.cl 2.4.9-e.3 #1 Fri May 3 17:02:43 EDT 2002 i686 unknown Chao, Mauricio Rojas P. Gerente Producto y Servicio ISC S.A. (http://www.isc.cl) fono: 56 2 2362306 fax: 56 2 2362088 -Mensaje original- De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] En nombre de Bukie Mabayoje Enviado el: Miércoles, 09 de Febrero de 2005 18:00 Para: xfree86@xfree86.org Asunto: Re: [XFree86] Xfree configuration problem 1. Can you do /sbin/lspci and post it. 2. Can you do uname -a or uname -r and post it. The 865GV chipset was released after RH 2.1 AS, maybe for some reason it is having difficult in recognizing the video controller. But I doubt it. Anyway, there is a work around that Mark posted a while back. Try Mark's suggestion . A workaround would be to specify the bus id explicitly in the Section Device of the XF86Config file. Eg.: BusIDPCI 00:02:0 Mauricio Rojas wrote: Hi Guys, I have a problem to start X with my computer. I have demo server of Linux RedHat 2.1 AS on a Asus P4P800-MX (Intel 865GV) and a Intel Extreme Graphics Could help me with the configuration please? Regards, Mauricio (II) Loading extension GLX (II) LoadModule: pex5 (II) Reloading /usr/X11R6/lib/modules/extensions/libpex5.a (II) Loading extension X3D-PEX (II) LoadModule: record (II) Loading /usr/X11R6/lib/modules/extensions/librecord.a (II) Module record: vendor=The XFree86 Project compiled for 4.1.0, module version = 1.13.0 Module class: XFree86 Server Extension ABI class: XFree86 Server Extension, version 0.1 (II) Loading extension RECORD (II) LoadModule: xie (II) Loading /usr/X11R6/lib/modules/extensions/libxie.a (II) Module xie: vendor=The XFree86 Project compiled for 4.1.0, module version = 1.0.0 Module class: XFree86 Server Extension ABI class: XFree86 Server Extension, version 0.1 (II) Loading extension XIE (II) LoadModule: i810 (II) Loading /usr/X11R6/lib/modules/drivers/i810_drv.o (II) Module i810: vendor=The XFree86 Project compiled for 4.1.0, module version = 1.0.0 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.4 (II) LoadModule: mouse (II) Loading /usr/X11R6/lib/modules/input/mouse_drv.o (II) Module mouse: vendor=The XFree86 Project compiled for 4.1.0, module version = 1.0.0 Module class: XFree86 XInput Driver ABI class: XFree86 XInput driver, version 0.2 (II) I810: Driver for Intel i810 chipset: i810, i810-dc100, i810e, i815 (II) Primary Device is: PCI 00:02:0 (--) Assigning device section with no busID to primary device (EE) No devices detected. Fatal server error: no screens found ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Xfree configuration problem
uot;MinY" "15372" # Option "MaxY" "1230" # Option "ScreenNumber" "0" # Option "ReportingMode" "Scaled" # Option "ButtonNumber" "1" # Option "SendCoreEvents" # EndSection # # Section "InputDevice" # Identifier "touchscreen1" # Driver "elo2300" # Option "Device" "/dev/ttyS0" # Option "MinX" "231" # Option "MaxX" "3868" # Option "MinY" "3858" # Option "MaxY" "272" # Option "ScreenNumber" "0" # Option "ReportingMode" "Scaled" # Option "ButtonThreshold" "17" # Option "ButtonNumber" "1" # Option "SendCoreEvents" # EndSection # ** # Monitor section # ** # Any number of monitor sections may be present Section "Monitor" Identifier "Sony1304" # HorizSync is in kHz unless units are specified. # HorizSync may be a comma separated list of discrete values, or a # comma separated list of ranges of values. # NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S # USER MANUAL FOR THE CORRECT NUMBERS. HorizSync 28-50 # HorizSync 30-64 # multisync # HorizSync 31.5, 35.2 # multiple fixed sync frequencies # HorizSync 15-25, 30-50 # multiple ranges of sync frequencies # VertRefresh is in Hz unless units are specified. # VertRefresh may be a comma separated list of discrete values, or a # comma separated list of ranges of values. # NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S # USER MANUAL FOR THE CORRECT NUMBERS. VertRefresh 50-87 EndSection # BUKIE3: Need to change Section Monitor to match you monitor # ** # Graphics device section # ** # Any number of graphics device sections may be present # Standard VGA Device: Section "Device" Identifier "Standard VGA" VendorName "Unknown" BoardName "Unknown" # The chipset line is optional in most cases. It can be used to override # the driver's chipset detection, and should not normally be specified. # Chipset "generic" # The Driver line must be present. When using run-time loadable driver # modules, this line instructs the server to load the specified driver # module. Even when not using loadable driver modules, this line # indicates which driver should interpret the information in this section. Driver "vga" # The BusID line is used to specify which of possibly multiple devices # this section is intended for. When this line isn't present, a device # section can only match up with the primary video device. For PCI # devices a line like the following could be used. This line should not # normally be included unless there is more than one video device # intalled. # BusID "PCI:0:10:0" # VideoRam 256 # Clocks 25.2 28.3 EndSection # Device configured by xf86config: Section "Device" Identifier "Intel-865" Driver "vga" # unsupported card #VideoRam 4096 # Insert Clocks lines here if appropriate EndSection # ** # Screen sections # ** # Any number of screen sections may be present. Each describes # the configuration of a single screen. A single specific screen section # may be specified from the X server command line with the "-screen" # option. Section "Screen" Identifier "Screen 1" Device "Intel-865" Monitor "Sony1304" DefaultDepth 16 Subsection "Display" Depth 8 Modes "640x480" "800x600" "1024x768" "1280x1024" ViewPort 0 0 EndSubsection Subsection "Display" Depth 16 Modes "640x480" "800x600" "1024x768" "1280x1024" ViewPort 0 0 EndSubsection Subsection "Display" Depth 24 Modes "640x480" "800x600" "1024x768" "1280x1024" ViewPort 0 0 EndSubsection EndSection # BUKIE4: Check your resulution # ** # ServerLayout sections. # ** # Any number of ServerLayout sections may be present. Each describes # the way multiple screens are organised. A specific ServerLayout # section may be specified from the X server command line with the # "-layout" option. In the absence of this, the first section is used. # When now ServerLayout section is present, the first Screen section # is used
Re: [XFree86] R128: No matching device
Aaron Yang wrote: rtl stands for real time linux it turns out Mark is right after all. the problem lies with my sound card, so what i did was to remove it, and X Server recognizes the video card instead, and everything worked out fine. for this matter, can anyone fix this bug in linux-2.4.20-rtl kernel? I am still not comfortable to say it is the kernel either. If your sound card is advertising itself as prehistoric VGA. Then I think we should do more test before we conclude that the device is a VGA. If you don't mind can you put back the sound card and run lspci -vv Mark Marc, Wouldn't it be a good idea when we detect this strange cards, that we should still continue the bus scan to determine if there is another video (e.g non prehistoric or AGP ) present on the bus. And if a non prehistoric or AGP is found on the bus then choose it as the default. linux-2.4.20 seems to be able to work around it. thanks to all for your valuable help! --- Marc Aurele La France [EMAIL PROTECTED] wrote: On Sat, 5 Feb 2005, Bukie Mabayoje wrote: Mark Vojkovich wrote: On Fri, 4 Feb 2005, Aaron Yang wrote: i'm using xfree86 v4.3.0, redhat 9 and ati rage pro 8mb agp g.accel. everything works fine when i boot in linux kernel 2.4.20. after compiling and booting into linux-2.4.20-rtl, i can't start my X Server and i get the following errors. pls help, thanks! (!!) More than one primary device found (--) PCI: (0:14:0) unknown vendor (0x1274) unknown chipset (0x5880) rev 2, I/O @ 0x1080/6 (--) PCI: (1:0:0) ATI Technologies Inc Rage 128 RL/VR AGP rev 0, Mem @ 0xf800/26, 0xf010/14, I/O @ 0x9000/8 This looks like either a bug in your sound card, or more likely a motherboard bios bug. I really doubts if that is the case. BIOS don't usually make such catastrophic errors. I am pretty sure it is not the BIOS. The PCI configuration space Class Code should be a clue. Base Class Sub-Class Interface Meaning 00h 00h 00h All currently implemented devices except for VGA-compatible device 00h 01h 00h VGA-Compatible device 03h 00h 000b VGA-compatible controller. Memory addresses 0Ah through 0Bh I/O addressses 3B0h to 3BBh and 3C0h to 3DFh and all aliases of these addresses. 03h 00h 0001b 8514-compatible controller - 2E8h and its aliases, 2EAh-2EFh 03h 01h 00h XGA controller 03h 80h 00h other display controller 04h 00h 00h Video device 04h 01h 00h Audio device 04h 80h 00 Other multimedia device If it is the BIOS the video will never appear a boot. Perhaps your previous kernel had a workaround for this while your upgraded kernel did not. Do you know what the rtl means at the end of linux-2.4.20-rtl ? Anyhow, what happened is that your motherboard marked your sound card as the primary display card. If you look at /proc/pci it probably identified your sound card as a VGA controller. A workaround would be to specify the bus id explicitly in the Section Device of the XF86Config file. Eg.: BusIDPCI:1:0:0 In absence of the explicit bus ID, XFree86 is defaulting to the primary display device, which in this case, happens to be your sound card :) I agree this isn't a BIOS nor kernel issue. But, Mark's right nonetheless. The sound adapter is mis-advertising itself as a prehistoric VGA (not the first time). For now, specify the BusID and everything will be fine. I'll have this fixed in 4.5. 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 __ Do you Yahoo!? Yahoo! Mail - now with 250MB free storage. Learn more. http://info.mail.yahoo.com/mail_250
Re: [XFree86] R128: No matching device
Mark Vojkovich wrote: On Fri, 4 Feb 2005, Aaron Yang wrote: hi everyone, i'm using xfree86 v4.3.0, redhat 9 and ati rage pro 8mb agp g.accel. everything works fine when i boot in linux kernel 2.4.20. after compiling and booting into linux-2.4.20-rtl, i can't start my X Server and i get the following errors. pls help, thanks! (!!) More than one primary device found (--) PCI: (0:14:0) unknown vendor (0x1274) unknown chipset (0x5880) rev 2, I/O @ 0x1080/6 (--) PCI: (1:0:0) ATI Technologies Inc Rage 128 RL/VR AGP rev 0, Mem @ 0xf800/26, 0xf010/14, I/O @ 0x9000/8 This looks like either a bug in your sound card, or more likely a motherboard bios bug. I really doubts if that is the case. BIOS don't usually make such catastrophic errors. I am pretty sure it is not the BIOS. The PCI configuration space Class Code should be a clue. Base Class Sub-Class Interface Meaning 00h 00h 00h All currently implemented devices except for VGA-compatible device 00h 01h 00h VGA-Compatible device 03h 00h 000bVGA-compatible controller. Memory addresses 0Ah through 0Bh I/O addressses 3B0h to 3BBh and 3C0h to 3DFh and all aliases of these addresses. 03h 00h 0001b 8514-compatible controller - 2E8h and its aliases, 2EAh-2EFh 03h 01h 00h XGA controller 03h 80h 00hother display controller 04h 00h 00hVideo device 04h 01h 00h Audio device 04h 80h 00 Other multimedia device If it is the BIOS the video will never appear a boot. Perhaps your previous kernel had a workaround for this while your upgraded kernel did not. Do you know what the rtl means at the end of linux-2.4.20-rtl ? Anyhow, what happened is that your motherboard marked your sound card as the primary display card. If you look at /proc/pci it probably identified your sound card as a VGA controller. A workaround would be to specify the bus id explicitly in the Section Device of the XF86Config file. Eg.: BusIDPCI:1:0:0 In absence of the explicit bus ID, XFree86 is defaulting to the primary display device, which in this case, happens to be your sound card :) Mark. Mark. ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] XW GUI server crash
Has someone help you? I am seen this problem before, if you install as user Y and you try to loging as user X you will get that error. Do init 5 and see what happens. MARIUSZ ZIEMNICKI wrote: Hi, I have used Linux for four days. Yesterday GUI server problem occured. After xauth : creating new /root/.Xauthority using, writing, /root/.Xauthority ... /home/amigo/.Xauthor for 'amigo' user message as follows appears (for super- and user ); Fatal server error, can't read file /tem/.X0-lock xinit : connection refused (errno 111) : unable to connect to X server xinit : no such process (errno 3): server error. After that /user/X11R6/bin/startx : line 133 : /dev/null : permission denied appears while logged in as a user. This doesn't make sense. Anyone should be above to write the null device. I run Linux Amigo ( Slackware ) on i586, DOS primary partition. Please help me retriev GUI access.Thanks in advance. Looking forward to hearing from you. Rgds, Mariusz -- ___ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Fatal Server Error - No Screens Found
I couldn't find where agpgart is loaded. It needs to be loaded for you video card to work well. [EMAIL PROTECTED] wrote: When I attempt to configure, I receive an error message about missing libglide2x.so, not sure if it is related to my main problem of no screens found. My intuition leads me to suspect this is something to do with my having a video card in a AGP slot on a motherboard with an integrated video card. My display works fine in text mode, but I am unable to get into any kind of graphics mode. When I do startx I get a black screen and only return to text mode after several CTRL-C attempts. My monitor is plugged into the video card in the AGP slot. It works perfectly fine in Windows XP with my current setup. Thanks for any suggestions you may be able to provide. Bob King ** Contents of Log File Follow ** _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 _XSERVTransOpen: transport open failed for inet6/subbob.us:0 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 XFree86 Version 4.4.0 Release Date: 29 February 2004 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.7-10custom i686 [ELF] Current Operating System: Linux subbob.us 2.4.7-10 #1 Thu Sep 6 17:27:27 EDT 2001 i686 Build Date: 27 February 2004 Changelog Date: 29 February 2004 Before reporting problems, check http://www.XFree86.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/XFree86.0.log, Time: Sat Jan 29 08:53:42 2005 (==) Using config file: /etc/X11/XF86Config-4 (==) ServerLayout Anaconda Configured (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device NVIDIA GeForce 256 (generic) (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc105 (**) XKB: model: pc105 (**) Option XkbLayout us (**) XKB: layout: us (==) Keyboard: CustomKeycode disabled (**) FontPath set to unix/:7100 (**) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (II) Open APM successful (II) Module ABI versions: XFree86 ANSI C Emulation: 0.2 XFree86 Video Driver: 0.7 XFree86 XInput driver : 0.4 XFree86 Server Extension : 0.2 XFree86 Font Renderer : 0.4 (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.4.0, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (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.4.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.7 (--) using VT number 7 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x8070, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1039,0650 card 1039,0650 rev 01 class 06,00,00 hdr 80 (II) PCI: 00:01:0: chip 1039,0001 card , rev 00 class 06,04,00 hdr 01 (II) PCI: 00:02:0: chip 1039,0008 card , rev 00 class 06,01,00 hdr 80 (II) PCI: 00:02:2: chip 1039,7001 card 1039,7001 rev 07 class 0c,03,10 hdr 00 (II) PCI: 00:02:3: chip 1039,7001 card 1039,7001 rev 07 class 0c,03,10 hdr 00 (II) PCI: 00:02:5: chip 1039,5513 card 1039,5513 rev d0 class 01,01,80 hdr 80 (II) PCI: 00:02:7: chip 1039,7012 card 1462,5330 rev a0 class 04,01,00 hdr 00 (II) PCI: 00:07:0: chip 14f1,1033 card 122d,4034 rev 08 class 07,80,00 hdr 00 (II) PCI: 00:0f:0: chip 10ec,8139 card 10ec,8139 rev 10 class 02,00,00 hdr 00 (II) PCI: 01:00:0: chip 1002,4150 card 1545,7c20 rev 00 class 03,00,00 hdr 80 (II) PCI: 01:00:1: chip 1002,4170 card 1545,7c21 rev 00 class 03,80,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,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -100x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -100x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -100x - 0x (0x0) MX[B] (II) PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x000e (VGA_EN is set) (II) Bus 1 I/O range: [0] -100xd000 - 0xd0ff (0x100) IX[B] [1] -100xd400 - 0xd4ff (0x100) IX[B] [2] -10
Re: [XFree86] Re: [XFree86] Fatal Server Error - No Screens Found
Some thing like that, but not exactly. That is for Intel's chip. You don't have an Intel chip. I think you have GeForce. Some kernel already have it. You just have to enable it. I don't know about 2.4.7-10. It is available in 2.4.18. [EMAIL PROTECTED] wrote: Does that mean I need to update the kernel? I found the following information on the agpgart you refer to at: http://www.xfree86.org/~dawes/845driver.html In addition to building/installing XFree86 CVS code, a recent 2.4.x kernel is needed. 2.4.19 or later is recommended. If you want to use the DRI support, an updated i830 DRM module is also required, and it is best to build one from either the XFree86 or DRI source tree. To do this you will also need your kernel source installed. Here is an example of how to build and load the i830 DRM module: # cd xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel # make -f Makefile.linux i830.o # modprobe agpgart # rmmod i830 # insmod i830.o Here is an example of how to install the i830 DRM module so that it will be loaded automatically when needed: # mv /lib/module/`uname -r`/kernel/drivers/char/drm/i830.o \ /lib/module/`uname -r`/kernel/drivers/char/drm/i830.o.save # cp i830.o /lib/module/`uname -r`/kernel/drivers/char/drm For full functionality when using the 852GM, 855GM or 865G chipsets, an updated agpgart kernel module is also required. A patch for the 2.4.20 kernel can be found here, a patch for the 2.5.56 kernel is here, and a tarball with the complete source for the agpgart driver in a form that can be built standalone for 2.4.x and older 2.5.x kernels can be found here. The 852GM, 855GM and 865G support should be included with future 2.5.6x kernels. I couldn't find where agpgart is loaded. It needs to be loaded for you video card to work well. ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: What happened to the fonts?
Marc Aurele La France wrote: On Tue, 25 Jan 2005, Marc Aurele La France wrote: > On Thu, 20 Jan 2005, Mark Vojkovich wrote: >> On Thu, 20 Jan 2005, Marc Aurele La France wrote: >>> On Thu, 20 Jan 2005, Bukie Mabayoje wrote: >>>> Mark Vojkovich wrote: >>>>> I synced up and built and now, though the server starts fine, >>>>> apps can't get any fonts. Window managers claim they can't find >>>>> fontsets like fixed so menus and such have no text in them. >>>>> xfontsel seems to work though. Anyone know what's going on? >>>>> It's like the fonts.alias isn't being read anymore. I can >>>>> see fixed in the fonts.alias and I can see the corresponding >>>>> font in the fonts.dir and I can see that the font file exists >>>>> and can verify that the server acknowledged that font path. >>>> I am looking into a similar problem too, when xfs is not running. >>> I've been able to make the fontset message appear with a simple test case >>> (holding down the control key and pressing any mouse button while the >>> pointer >>> is in an xterm). >> I don't see that message with xterm. TWM menus don't work though. >> But, if I run TWM remotely from another machine it works. I think >> that implies that it's a problem with the local libraries. Another >> data point, is a test app that opens "fixed" seems to work fine, so >> it's not the case that aliases are broken in general - just in some >> cases. >> Bukie, how long have you been seeing this problem? I updated >> yesterday and saw it for the first time. The last time I updated >> was Nov 26. so that gives a pretty large window. It was reported in the xfree86 by someone else earlier this month. And I was able to reproduce it using their Linux distribution. I can't test it in red hat because Red hat always start xfs when running X. So I am currently trying to debug it using debian. The fact is X should run without xfs running. > Mark (and anyone else, of course), > Please tell me whether the attached patch fixes (your version of) the > problem. Umm. That's not right. Further investigation shows the xterm behaviour I was seeing was due to an NLS configuration error. Also, the TWM menus I see look as expected. Can you narrow down this problem a bit more? 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. ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel Sorry, I my mail system crashed and I lost some mail. That is why I didn't respond to your message.
Re: [XFree86] Problem with xserver
Are your sure you are running redhat 9.0 OS Kernel: Linux version 2.4.21-4.ELsmp ([EMAIL PROTECTED]) (gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-20)) #1 SMP Fri Oct 3 17:52:56 EDT 2003 The above from you log looks like Red Hat EL 3.0 Nkoa Nama wrote: hi, i'm using redha 9.0. My xserver don't start i don't know why. Can you help me to solve this problem the log file of my xserver is in attachment Thank you for your help Dcouvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour vos mails ! Crez votre Yahoo! Mail sur http://fr.mail.yahoo.com/ --- Name: XFree86.0.log XFree86.0.log Type: Text Document (application/x-unknown-content-type-txtfile) Encoding: base64 Description: XFree86.0.log
Re: [XFree86] Problem with xserver
My Error picked up the wrong log file. Sorry about that Nkoa Nama wrote: hi, i'm using redha 9.0. My xserver don't start i don't know why. Can you help me to solve this problem the log file of my xserver is in attachment Thank you for your help Découvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour vos mails ! Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com/ --- Name: XFree86.0.log XFree86.0.log Type: Text Document (application/x-unknown-content-type-txtfile) Encoding: base64 Description: XFree86.0.log ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: What happened to the fonts?
I am looking into a similar problem too, when xfs is not running. Mark Vojkovich wrote: I synced up and built and now, though the server starts fine, apps can't get any fonts. Window managers claim they can't find fontsets like fixed so menus and such have no text in them. xfontsel seems to work though. Anyone know what's going on? It's like the fonts.alias isn't being read anymore. I can see fixed in the fonts.alias and I can see the corresponding font in the fonts.dir and I can see that the font file exists and can verify that the server acknowledged that font path. Mark. ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: [XFree86] ATI Drivers
I should have some answer for your issue sometimes this week. Zach Beck wrote: Zach Beck writes: 1) uname -a gives Linux THASAY 2.4.26 #6 Mon Jun 14 19:07:27 PDT 2004 i686 unknown unknown GNU/Linux 2) No, it's not an install of 9.0. It's a fresh install of Slackware 10.0 3) XFree86 Version 4.4.0 Release Date: 29 February 2004 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.26 i686 [ELF] Current Operating System: Linux THASAY 2.4.26 #6 Mon Jun 14 19:07:27 PDT 2004 i686 Build Date: 23 December 2004 Changelog Date: 29 February 2004 Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present Bukie Mabayoje wrote: I have Redhat 9 installed now. I compared your font directory with the one here. They don't match. Can you answer the following questions: 1. run this command /uname -a/ and send the output to me.. 2. Is your OS an update of Redhat 9.0? 3. Login as root and run this command /X -version/ and send the output to me. Need to have the same configuration inorder to debug your issue. Zach Beck wrote: Here you go. Thanks a ton. Bukie Mabayoje wrote: I don't see a problem with the driver. It seems your problem is related to fonts run this command -find /usr/X11R6/lib/X11/fonts/ -name * -print fontdirlist.txt send me the file. Just need to check that the font path exist on your disk. Zach Beck wrote: Can't seem to get the drivers working. Attached is XFree86.0.log Thanks in advance Zach ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] raport
You already have a copy running or do what it says. See text below in blue [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] jacol]$ startx Using authority file /home/jacol/.Xauthority Writing authority file /home/jacol/.Xauthority Fatal server error: Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. When reporting a problem related to a server crash, please send the full server output, not just the last messages. Please report problems to [EMAIL PROTECTED] ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Screen Resolution
I just completed on installation of RH 9.0 on an Intel Motherboard D865GVHZ with the 865GV graphic controller. And X started with 1024x724 24-bit color. Your issue is not the distribution of RH 9.0 with the INTEL 865 driver which is actually the i810 driver. Your problem is something else. Maybe BIOS configuration related. Anyway let me know what else I can do for you. I am done working on the issue because I can't reproduce the problem with RH 9.0 and 865GV chipset.. Bob Pelletier wrote: Hi. I have now done both a custom install and an install using all default packages only on 2 DELL different machines configured exactly the same and both fail with this same problem (INTEL 865). What more info would you need to troubleshoot this? They will not recognize 1024x768 config. Thanks.Bob Bukie Mabayoje [EMAIL PROTECTED]> wrote: So do I edit /etc/X11/xinit/xinitrc? no Am I editing the same section of code? not really My comment below was a response to your original statement in black below > X11 is started at run level 5 on Redhat. If you don't what it started don't run at level 5. But then, other multi-user stuff wouldn't be available. You better off removing from the startup script.. The X server startup script is /etc/X11/xinit/xinitrc. The automatic startup of X server is typically done in rc.sysinit script. > > That's what I hate about red hat.. It appears that the new version of it doesn't allow for you to have the option to not automatically start the Xserver... Unfortunately, (I'm sure someone has a better idea) the only solution I have is to reinstall red hat.. :( The real problem is the following: > > Hi. I am having the same problem with the same DELL stuff. I have been trying to get an answer for a couple of weeks on how to fix it. I have reinstalled. I am about to try different hardware. Let me know if you hear anything. Thanks. > > Bob > > > > Asadullah FAYZi wrote: Hi; > > I have just started instalation of Redhat 9, Howevr i am not able to > > change the screen Resolution from 800x600, I tried mony times but didnt > > work. after setting the resolution to 1024x768 the system wants me to > > logout and restart Xserver.After logging out i see that the sitting is > > back to previous value.Actullay i have two questios > > 1- what does it mean by restarting Xserver? > > 2-How can I set the resolution to desired values. > > i am using Dell branded PC with intel 865 main Board. > > > > Can anyone help me in this regard please, It seems that you can't get 1024x768 resolution, I am correct? Can you post your /etc/X11/XF86Config file? If it is a configuration script problem I will be able to tell you immediately or else I have to install redhat 9.0 on my play box and see if I can duplicate the problem. My play box is being used right now to build Xfree86 4.4.0 on debian 3.0r3 and it is not going very well at the moment. The other machines are production machines that I can't mess with, they are running RH EL3.0 and doing 1024x768 on the local console. Bob Pelletier wrote: Hi. Thanks again. So do I edit /etc/X11/xinit/xinitrc? Am I editing the same section of code?Bob Bukie Mabayoje [EMAIL PROTECTED]> wrote: The X server startup script is /etc/X11/xinit/xinitrc. The automatic startup of X server is typically done in rc.sysinit script. James Thogmartin wrote: > Where would he find the startup script? > -Original Message- > From: Bukie Mabayoje<[EMAIL PROTECTED]> > Date: Mon, 03 Jan 2005 15:41:14 > To:xfree86@xfree86.org > Subject: Re: [XFree86] Screen Resolution > > X11 is started at run level 5 on Redhat. If you don't what it started don't run at level 5. But then, other multi-user stuff wouldn't be available. You better off removing from the startup script. > > look at /etc/X11/XF86Config and locate the text below. What does it say? > > section "Screen" > Identifier "Screen0" > Device "Videocard0" > Monitor "Monitor0" > DefaultDepth 24 > SubSection "Display" > Depth 24 > Modes "1024x768" "800x600" "640x480" > EndSubSection > EndSection > > James Thogmartin wrote: > > > That's what I hate about red hat.. It appears that the new version of it d oesn't allow for you to have the option to not automatically start the Xserver... Unfortunately, (I'm sure someone has a better idea) the only solution I have is to reinstall red hat.. :( > > -Original Message- > > From: Bob Pelletier<[EMAIL PROTECTED]> > > Date: Mon, 03 Jan 2005 12:45:26 > > To:xfree86@xfree86.org > > Subject: Re: [XFree86] Screen Resolution > > > > Hi Jason. Thanks for responding. I did the alt-ctl-backspace and the screen flashed and went back to the LOGIN screen which is the first screen with print overlaying its
Re: [XFree86] Screen Resolution (Problem Fixed)
At what resolution? Bob Pelletier wrote: Hi All. Great news. Got a work around. Lowered the color settings to 256 and both machines are working. Thanks all.Bob Bukie Mabayoje [EMAIL PROTECTED]> wrote: Bob, I need this section from your XFreeConfig Section "Device" Identifier "Videocard0" Driver "tdfx" VendorName "Videocard vendor" BoardName "Voodoo3 (generic)" VideoRam 16384 EndSection I expect yours to say i810 or something similar. The driver shipped with XFree86 Version 4.3.0 is the old driver. And it is known to have a few problem. I think there is a newer driver. I need to read some code before I can confirm it. Basically, we are going to use the new XFree86 with the latest driver. We'll get your system up and running -bukie Bob Pelletier wrote: Hi. I have the same thing as you have: XFree86 Version 4.3.0 (Red Hat Linux release: 4.3.0-2) Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.20-3bigmem i686 [ELF] Build Date: 27 February 2003 Build Host: porky.devel.redhat.com Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present OS Kernel: Linux version 2.4.20-8 ([EMAIL PROTECTED]) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 Thu Mar 13 17:54:28 EST 2003 Bob If the current redhat 9.0 driver doesn't support it, I will be glad to write the code to support 1024x768 with 24-Bit. It seems lots of people want that support. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: [XFree86] ATI Drivers
There is a difference between Linux THASAY and Slackware 10.0 see text below The kernel are the same but the X package are not. One is from XFree86 and the other is from X.org I also experienced font problems when starting X. I have an error during the installation when the install script was installing X11-fonts-misc-6.7.0-noarch-1.tgz. After the fresh install was completed I manual installed all the fonts. So it was not the media. Anyway, Yes there is a font problem with the installation. I will work your issue currently with the other issue I am currently working, since I have to work with x.org X version anyway. Their version may have the updated Intel video driver that I need for another issue. The moment I have the solution I will get back to you. THASAY ---> Linux THASAY 2.4.26 #6 Mon Jun 14 19:07:27 PDT 2004 i686 unknown unknown GNU/Linux XFree86 Version 4.4.0 Release Date: 29 February 2004 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.26 i686 [ELF] Current Operating System: Linux THASAY 2.4.26 #6 Mon Jun 14 19:07:27 PDT 2004 i686 Build Date: 23 December 2004 Changelog Date: 29 February 2004 Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present Slackware 10.0 --> Linux slackware 2.4.26 #6 Mon Jun 14 19:07:27 PDT 2004 i686 unknown unknown GNU/Linux Release Date: 18 December 2003 X Protocol Version 11, Revision 0, Release 6.7 Build Operating System: Linux 2.4.26 i686 [ELF] Current Operating System: Linux slackware 2.4.26 #6 Mon Jun 14 19:07:27 PDT 2004 i686 Build Date: 05 June 2004 Before reporting problems, check http://wiki.X.Org to make sure that you have the latest version. Module Loader present Zach Beck wrote: Zach Beck writes: 1) uname -a gives Linux THASAY 2.4.26 #6 Mon Jun 14 19:07:27 PDT 2004 i686 unknown unknown GNU/Linux 2) No, it's not an install of 9.0. It's a fresh install of Slackware 10.0 3) XFree86 Version 4.4.0 Release Date: 29 February 2004 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.26 i686 [ELF] Current Operating System: Linux THASAY 2.4.26 #6 Mon Jun 14 19:07:27 PDT 2004 i686 Build Date: 23 December 2004 Changelog Date: 29 February 2004 Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present Bukie Mabayoje wrote: > I have Redhat 9 installed now. > I compared your font directory with the one here. They don't match. > Can you answer the following questions: > 1. run this command /uname -a/ and send the output to me.. > 2. Is your OS an update of Redhat 9.0? > 3. Login as root and run this command /X -version/ and send the output > to me. > > Need to have the same configuration inorder to debug your issue. > > Zach Beck wrote: > >> Here you go. Thanks a ton. >> >> Bukie Mabayoje wrote: >> >> >I don't see a problem with the driver. It seems your problem is related >> >to fonts >> > >> >run this command ->find /usr/X11R6/lib/X11/fonts/ -name "*" >> -print > >> >fontdirlist.txt >> > >> >send me the file. Just need to check that the font path exist on your >> >disk. >> > >> > >> >Zach Beck wrote: >> > >> > >> > >> >>Can't seem to get the drivers working. Attached is XFree86.0.log >> >> >> >>Thanks in advance >> >> >> >>Zach >> >> >> >> >> >> >> ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Screen Resolution
Bob, I need this section from your XFreeConfig Section "Device" Identifier "Videocard0" Driver "tdfx" VendorName "Videocard vendor" BoardName "Voodoo3 (generic)" VideoRam 16384 EndSection I expect yours to say i810 or something similar. The driver shipped with XFree86 Version 4.3.0 is the old driver. And it is known to have a few problem. I think there is a newer driver. I need to read some code before I can confirm it. Basically, we are going to use the new XFree86 with the latest driver. We'll get your system up and running -bukie Bob Pelletier wrote: Hi. I have the same thing as you have: XFree86 Version 4.3.0 (Red Hat Linux release: 4.3.0-2) Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.20-3bigmem i686 [ELF] Build Date: 27 February 2003 Build Host: porky.devel.redhat.com Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present OS Kernel: Linux version 2.4.20-8 ([EMAIL PROTECTED]) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 Thu Mar 13 17:54:28 EST 2003 Bob If the current redhat 9.0 driver doesn't support it, I will be glad to write the code to support 1024x768 with 24-Bit. It seems lots of people want that support.
Re: [XFree86] Screen Resolution
Bob, I have Redhat 9.0 installed now. Can you do me a little favor? I have to have a non edited XF86Config file from your disk. The text at the end of this mail is a fresh install of Redhat 9.0 XFree86Config file 1.) I need to make sure the correct modules are being loaded 2.) And the Monitor section is actually correct. When I was doing the install, the install program couldn't identify the monitor. That may be a driver bug or the monitor doesn't support DDC (Probably monitor doesn't support functionality --- very old monitor). Anyway, I manually identify the correct monitor. And it got the H-Sync and V-refresh frequency correct. Based on the text you sent me, You wouldn't be able to do 1024x768 with 24-bit color. Don't know yet if eventually you will be able do 1024x768 with 24-bit color. The following text is from Intel's web site For SuSE only, in the "screen" section: Add a line for "DefaultDepth 24" Add a line under Subsection "Display," after "Depth 24" add a line for "Modes "1024x768" "800x600" as appropriate for your system Example: Section "Screen" Identifier "Screen0" Device "Card0" Monitor "Monitor0" DefaultDepth 24 Subsection "Display" Depth 24 Modes "1024x768" "800x600" EndSubSection End Section This was a while back, I am pretty sure by now the Intel 865 should be able to do 1024x768 with 24-bit. I am currently investigating if it can handle it. I also need your output from this command Steps: 1. Login as root 2. Type: X -version. 3. Send me the entire output. The output from the play-box is below XFree86 Version 4.3.0 (Red Hat Linux release: 4.3.0-2) Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.20-3bigmem i686 [ELF] Build Date: 27 February 2003 Build Host: porky.devel.redhat.com Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present OS Kernel: Linux version 2.4.20-8 ([EMAIL PROTECTED]) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 Thu Mar 13 17:54:28 EST 2003 If the current redhat 9.0 driver doesn't support it, I will be glad to write the code to support 1024x768 with 24-Bit. It seems lots of people want that support. PLAY-BOX XFree86Config # XFree86 4 configuration created by pyxf86config Section "ServerLayout" Identifier "Default Layout" Screen 0 "Screen0" 0 0 InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" InputDevice "DevInputMice" "AlwaysCore" EndSection Section "Files" # RgbPath is 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. # 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. 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" # Specify which keyboard LEDs can be user-controlled (eg, with xset(1)) # Option "Xleds" "1 2 3" # To disable the XKEYBOARD extension, uncomment XkbDisable. # Option "XkbDisable" # To customise the XKB settings to suit your keyboard, modify the # lines below (which are the defaults). For example, for a non-U.S. # keyboard, you will probably want to use: # Option "XkbModel" "pc102" # If you have a US Microsoft Natural keyboard, you can use: # Option "XkbModel" "microsoft" # # Then to change the language, change the Layout setting. # For example, a german layout can be obtained with: # Option "XkbLayout" "de" # or: # Option "XkbLayout" "de" # Option "XkbVariant" "nodeadkeys" # # If you'd like to switch the positions of your capslock and # control keys, use: # Option "XkbOptions" "ctrl:swapcaps" # Or if you just want both to be control, use: # Option "XkbOptions" "ctrl:nocaps" # Identifier "Keyboard0" Driver "keyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc105" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "Microsoft" Option "Device" "/dev/ttyS0" Option "ZAxisMapping" "4 5" Option "Emulate3Buttons" "no" EndSection Section "InputDevice" # If the normal CorePointer mouse is not a USB mouse then # this input device can be used in AlwaysCore mode to let you # also use USB mice at the same time. 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 "Sony CPD-1304" HorizSync 28.0 - 50.0 VertRefresh 50.0 - 87.0 Option "dpms" EndSection Section "Device" Identifier "Videocard0" Driver "tdfx" VendorName "Videocard vendor" BoardName "Voodoo3 (generic)" VideoRam 16384 EndSection Section "Screen" Identifier "Screen0" Device
Re: [XFree86] ATI Drivers
I have Redhat 9 installed now. I compared your font directory with the one here. They don't match. Can you answer the following questions: 1. run this command uname -a and send the output to me.. 2. Is your OS an update of Redhat 9.0? 3. Login as root and run this command X -version and send the output to me. Need to have the same configuration inorder to debug your issue. Zach Beck wrote: Here you go. Thanks a ton. Bukie Mabayoje wrote: >I don't see a problem with the driver. It seems your problem is related >to fonts > >run this command ->find /usr/X11R6/lib/X11/fonts/ -name "*" -print > >fontdirlist.txt > >send me the file. Just need to check that the font path exist on your >disk. > > >Zach Beck wrote: > > > >>Can't seem to get the drivers working. Attached is XFree86.0.log >> >>Thanks in advance >> >>Zach >>
Re: [XFree86] Fwd: X Server Error
Did you change the color depth? or video driver? What is the name and brand of your video card? Vincent Ngundi wrote: Hi, I've been running Redhat 9 for quite sometime. All of a sudden, I got the following error as I was booting I cannot the X Server (your graphical user interface). it is likely that it's not set up correctly. The log file is as shown below (Please get back to me ASAP): /* Start of log file */ XFree86 Version 4.3.0 (Red Hat Linux release: 4.3.0-2) Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.20-3bigmem i686 [ELF] Build Date: 27 February 2003 Build Host: porky.devel.redhat.com Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present OS Kernel: Linux version 2.4.20-8 ([EMAIL PROTECTED]) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 Thu Mar 13 17:54:28 EST 2003 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: Fri Jan 7 19:12:23 2005 (==) Using config file: /etc/X11/XF86Config (==) ServerLayout XFree86 Configured (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device Card0 (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (==) Keyboard: CustomKeycode disabled (WW) `fonts.dir' not found (or not valid) in /usr/X11R6/lib/X11/fonts/CID/. Entry deleted from font path. (Run 'mkfontdir' on /usr/X11R6/lib/X11/fonts/CID/). (**) FontPath set to /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/ (**) RgbPath set to /usr/X11R6/lib/X11/rgb (**) ModulePath set to /usr/X11R6/lib/modules (++) using VT number 7 (II) Open APM successful (II) Module ABI versions: XFree86 ANSI C Emulation: 0.2 XFree86 Video Driver: 0.6 XFree86 XInput driver : 0.4 XFree86 Server Extension : 0.2 XFree86 Font Renderer : 0.4 (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.3.0, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (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.3.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (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 1106,0691 card 1043,80e7 rev c4 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1106,8598 card , rev 00 class 06,04,00 hdr 01 (II) PCI: 00:04:0: chip 1106,0686 card 1043,80e7 rev 40 class 06,01,00 hdr 80 (II) PCI: 00:04:1: chip 1106,0571 card , rev 06 class 01,01,8a hdr 00 (II) PCI: 00:04:2: chip 1106,3038 card 0925,1234 rev 1a class 0c,03,00 hdr 00 (II) PCI: 00:04:3: chip 1106,3038 card 0925,1234 rev 1a class 0c,03,00 hdr 00 (II) PCI: 00:04:4: chip 1106,3057 card , rev 40 class 06,00,00 hdr 00 (II) PCI: 00:09:0: chip 1317,0985 card 1113,1216 rev 11 class 02,00,00 hdr 00 (II) PCI: 00:0b:0: chip 4005,4000 card 4005,4000 rev 00 class 04,01,00 hdr 00 (II) PCI: 01:00:0: chip 1039,0300 card 1039,0300 rev 90 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,1), 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-PCI bridge: (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 1 I/O range: [0] -1 0 0xd000 - 0xdfff (0x1000) IX[B] (II) Bus 1 non-prefetchable memory range: [0] -1 0 0xef00 - 0xefdf (0xe0) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 0 0xeff0 - 0xfbff (0xc10) 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) (II) Host-to-PCI bridge: (II) Bus -1: bridge is at (0:4:4), (-1,-1,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus -1 I/O range: [0] -1 0 0x - 0x (0x1) IX[B] (II) Bus -1 non-prefetchable memory range: [0] -1 0
Re: [XFree86] Xfree86 log error
It is not very clear if you are running Redhat 9 Linux or the Linux Aurox. The log files says Redhat. What do you mean by on my laptop(Aurox distribution) the laptop or the Linux. Please provide a more detail information from the time it was working to the time it stops working. thanks Gilles Robert wrote: Hello, After several months of good operation of my RedHat 9 Linux on my laptop (Aurox distribution), I am not able anymore to launch the X server . Please find attached the corresponding .log file. Any help will be very welcome. Regards, Gilles XFree86.0.log This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be assured to be secure or correct as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. --- Name: XFree86.0.log XFree86.0.log Type: Text Document (application/x-unknown-content-type-txtfile) Encoding: base64 Description: XFree86.0.log ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Xfree86 log error
X should be able to run without the font server. I am seeing a lot more problems with XFree86 on Red Hat 9. The moment I am done with my current investigation on debian I will put Red Hat 9 on my play box and see why are these problem occurring so often. I am a little puzzled why most people say it use to work and then stop. That doesn't typically happens with computer. Unless there is a hardware failure or binary corruption. Benstead, Kevin wrote: http://xfree86.linuxwiki.org/FAQErrorMessages has a description of what to do to fix this. The basic problem is that RedHat insists on installing X with a font server which at some later date it then stops from running. No one to my knowledge has ever identified why RedHat does this. The FAQ explains how to get your X running without using a Font Server. Kevin email: [EMAIL PROTECTED] Tel: +44 (0)118 971 5032 -Original Message- From: Andrew Haninger [mailto:[EMAIL PROTECTED] Sent: 07 January 2005 13:40 To: xfree86@xfree86.org Subject: Re: [XFree86] Xfree86 log error You appear to be having the unable to find font 'fixed' error that shows up oh-so-often. This can be tricky to fix, but I've always found that either enabling xfs or installing font packages helps to resolve the problem. You can usually find a list of daemons by running 'ntsysv' and scrolling down the list to the bottom. If it's not turned on, enable the X Font Server 'xfs' and try again. If that doesn't work, try reinstalling the X font packages that came with Redhat 9. Hope this helps. -Andy ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] another error while trying to compile xfree86 4.4.0
XFree86 4.4.0 builds on a fresh Debian 3.0r3
Thu Jan 6 23:08:20 PST 2005
Full build of XFree86 version 4.4.0 (29 February
2004) complete.
Linux debian 2.2.20-idepci #1 Sat Apr 20 12:45:19
EST 2002 i686 unknown
NO ISSUE
There are just a few extra packages that are required on the build machine.
STEPS:
1. Get a fresh 3.0r3 with debian base install.
2. Install the following packages or there later versions
2a) cracklib.2.7.tar.gz
OR> the binary version
2b) libpng_1.0.12.orig.tar.gz OR> the binary version
2c) Linux-PAM-0.78.tar.bz2 OR> the binary version
2d) ncurses_5.2.20020112a.orig.tar.gz OR> the binary version
2e) zlib-1.1.4.tar
3) Then follow the build instruction for XFree86 version 4.40
James Thogmartin wrote:
I looked around on debian's site, and noticed that
r3 is apparently the newer version.. I couldn't find r4 anywhere on there..
And then I went to the mirror where I got the release I installed.. And
it said it was r1. So, I'm wondering if xfree86 4.4.0 is compatible with
the base tools included with r1.. I'm trying to download the first cd for
r3 using "jigdo" so ill see how that goes... I would like a sort of forecast
so I can see how your install goes though.
-Original Message-
From: Bukie Mabayoje [EMAIL PROTECTED]>
Date: Mon, 03 Jan 2005 15:22:38
To:xfree86@xfree86.org
Subject: Re: [XFree86] another error while trying to compile xfree86
4.4.0
I have a fresh 3.0r3 installed now, I will try and follow
your steps. -- Install the packages as I go when I need them. I will get
back to you soon.
James Thogmartin wrote: v\:* {behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);} .shape {behavior:url(#default#VML);}
I did the net install, and as far as the toolset goes, Im just installing
packages as I go when I need them
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
On Behalf Of Bukie Mabayoje
Sent: Monday, January 03, 2005 7:44 AM
To: xfree86@xfree86.org
Subject: Re: [XFree86] another error while trying to compile xfree86
4.4.0
I like to duplicate your env here so that I can see what is going on
(basically do the build). I need more info about your toolset package and
which woody? You said 3.0 r3 or r4 James Thogmartin wrote:
This is starting to feel like a never ending battle..:
cd ../../exports/lib ln -s ../../lib/font/libXfont.a .
make[4]: *** No rule to make target `fontfile/module/DONE', needed
by `libfontbase.a'. Stop.
make[4]: Leaving directory `/root/xc/lib/font'
make[3]: *** [all] Error 2
make[3]: Leaving directory `/root/xc/lib'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/root/xc'
make[1]: *** [World] Error 2
make[1]: Leaving directory `/root/xc'
make: *** [World] Error 2
cryptic-networks:~/xc#
now, I can replace files that it supposedly cant find.. thats no problem..
but I have no idea how to fix this one..
Computers are like air conditioners. They don't work properly if you
open Windows.
BlackBerry service provided by Nextel
___
XFree86 mailing list
XFree86@XFree86.Org
http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] another error while trying to compile xfree86 4.4.0
cd /usr/local/include
or
cd /usr/include
su root
enter root password
ln -s /???//extras/zlib/*.h . #comment
there is period there just in case didn't see it
Just link the header files to one of the include search path. That should
do it.
James Thogmartin wrote:
Mine
keeps saying that it cant find zlib.h
so what ive been doing to resolve
that, is copying everything in the /extras/zlib directory to where-ever
its looking for zlib.. but thats extremely annoying.. is there any easier
method? Thanks
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf OfBukie Mabayoje
Sent:
Friday, January 07, 2005 8:04 AM
To:xfree86@xfree86.org
Subject:
Re: [XFree86] another error while trying to compile xfree86 4.4.0
XFree86
4.4.0 builds on a fresh Debian 3.0r3
Thu
Jan 6 23:08:20 PST 2005
Full
build of XFree86 version 4.4.0 (29 February 2004) complete.
Linux
debian 2.2.20-idepci #1 Sat Apr 20 12:45:19 EST 2002 i686 unknown
NO
ISSUE
There
are just a few extra packages that are required on the build machine.
STEPS:
1. Get a fresh 3.0r3 with
debian base install.
2. Install the following
packages or there later versions
2a) cracklib.2.7.tar.gz
OR> the binary version
2b) libpng_1.0.12.orig.tar.gz
OR> the binary version
2c) Linux-PAM-0.78.tar.bz2
OR> the binary version
2d) ncurses_5.2.20020112a.orig.tar.gz
OR> the binary version
2e) zlib-1.1.4.tar
3) Then follow the build
instruction for XFree86 version 4.40
James
Thogmartin wrote:
I
looked around on debian's site, and noticed that r3 is apparently the newer
version.. I couldn't find r4 anywhere on there.. And then I went to the
mirror where I got the release I installed.. And it said it was r1. So,
I'm wondering if xfree86 4.4.0 is compatible with the base tools included
with r1.. I'm trying to download the first cd for r3 using "jigdo" so ill
see how that goes... I would like a sort of forecast so I can see how your
install goes though.
-Original Message-
From: Bukie Mabayoje [EMAIL PROTECTED]>
Date: Mon, 03 Jan 2005 15:22:38
To:xfree86@xfree86.org
Subject: Re: [XFree86] another
error while trying to compile xfree86 4.4.0
I
have a fresh 3.0r3 installed now, I will try and follow your
steps. -- Install the packages as I go when I need them. I will get back
to you soon.
James Thogmartin wrote:
v\:* {behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);} w\:*
{behavior:url(#default#VML);} .shape {behavior:url(#default#VML);}
I
did the net install, and as far as the toolset goes, Im just installing
packages as I go when I need them
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
On Behalf Of Bukie Mabayoje
Sent:
Monday, January 03, 2005 7:44 AM
To:xfree86@xfree86.org
Subject: Re: [XFree86] another
error while trying to compile xfree86 4.4.0
I
like to duplicate your env here so that I can see what is going on (basically
do the build). I need more info about your toolset package and which woody?
You said 3.0 r3 or r4 James Thogmartin wrote:
This is starting to feel
like a never ending battle..:
cd ../../exports/lib
ln -s ../../lib/font/libXfont.a .
make[4]: *** No rule to
make target `fontfile/module/DONE', needed by `libfontbase.a'. Stop.
make[4]: Leaving directory
`/root/xc/lib/font'
make[3]: *** [all] Error
2
make[3]: Leaving directory
`/root/xc/lib'
make[2]: *** [all] Error
2
make[2]: Leaving directory
`/root/xc'
make[1]: *** [World] Error
2
make[1]: Leaving directory
`/root/xc'
make: *** [World] Error
2
cryptic-networks:~/xc#
now, I can replace files
that it supposedly cant find.. thats no problem.. but I have no idea how
to fix this one..
Computers are like air conditioners.
They don't work properly if you open Windows.
BlackBerry service provided
by Nextel
___
XFree86 mailing list
XFree86@XFree86.Org
http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Screen Resolution
I need a little more detail. When you say INTEL 865: 865 is a platform chipset and there are 865G, 865GV, 865PE and 865P. 1.) The 865G has graphic controller and AGP interface 2.) The 865GV has only graphic controller. No AGP interface 3.) I don't have a clue about 865PE and 865P. I will look it up later. For item 1: there is the possibility that you may have an AGP card in your system there is also the possibility that you are using the onboard graphic controller and not have an AGP card. and the third possibility is you have a PCI add-on video card in your system For item 2: NO AGP support. You may have a add-on PCI video card or the possibility that you are using the onboard graphic chip. For item 3: DON'T KNOW YET. I need more information. Are you using the onboard graphic controller or a add-on video or AGP video? Bob Pelletier wrote: Hi. I have now done both a custom install and an install using all default packages only on 2 DELL different machines configured exactly the same and both fail with this same problem (INTEL 865). What more info would you need to troubleshoot this? They will not recognize 1024x768 config. Thanks.Bob Bukie Mabayoje [EMAIL PROTECTED]> wrote: So do I edit /etc/X11/xinit/xinitrc? no Am I editing the same section of code? not really My comment below was a response to your original statement in black below > X11 is started at run level 5 on Redhat. If you don't what it started don't run at level 5. But then, other multi-user stuff wouldn't be available. You better off removing from the startup script.. The X server startup script is /etc/X11/xinit/xinitrc. The automatic startup of X server is typically done in rc.sysinit script. > > That's what I hate about red hat.. It appears that the new version of it doesn't allow for you to have the option to not automatically start the Xserver... Unfortunately, (I'm sure someone has a better idea) the only solution I have is to reinstall red hat.. :( The real problem is the following: > > Hi. I am having the same problem with the same DELL stuff. I have been trying to get an answer for a couple of weeks on how to fix it. I have reinstalled. I am about to try different hardware. Let me know if you hear anything. Thanks. > > Bob > > > > Asadullah FAYZi wrote: Hi; > > I have just started instalation of Redhat 9, Howevr i am not able to > > change the screen Resolution from 800x600, I tried mony times but didnt > > work. after setting the resolution to 1024x768 the system wants me to > > logout and restart Xserver.After logging out i see that the sitting is > > back to previous value.Actullay i have two questios > > 1- what does it mean by restarting Xserver? > > 2-How can I set the resolution to desired values. > > i am using Dell branded PC with intel 865 main Board. > > > > Can anyone help me in this regard please, It seems that you can't get 1024x768 resolution, I am correct? Can you post your /etc/X11/XF86Config file? If it is a configuration script problem I will be able to tell you immediately or else I have to install redhat 9.0 on my play box and see if I can duplicate the problem. My play box is being used right now to build Xfree86 4.4.0 on debian 3.0r3 and it is not going very well at the moment. The other machines are production machines that I can't mess with, they are running RH EL3.0 and doing 1024x768 on the local console. Bob Pelletier wrote: Hi. Thanks again. So do I edit /etc/X11/xinit/xinitrc? Am I editing the same section of code?Bob Bukie Mabayoje [EMAIL PROTECTED]> wrote: The X server startup script is /etc/X11/xinit/xinitrc. The automatic startup of X server is typically done in rc.sysinit script. James Thogmartin wrote: > Where would he find the startup script? > -Original Message- > From: Bukie Mabayoje<[EMAIL PROTECTED]> > Date: Mon, 03 Jan 2005 15:41:14 > To:xfree86@xfree86.org > Subject: Re: [XFree86] Screen Resolution > > X11 is started at run level 5 on Redhat. If you don't what it started don't run at level 5. But then, other multi-user stuff wouldn't be available. You better off removing from the startup script. > > look at /etc/X11/XF86Config and locate the text below. What does it say? > > section "Screen" > Identifier "Screen0" > Device "Videocard0" > Monitor "Monitor0" > DefaultDepth 24 > SubSection "Display" > Depth 24 > Modes "1024x768" "800x600" "640x480" > EndSubSection > EndSection > > James Thogmartin wrote: > > > That's what I hate about red hat.. It appears that the new version of it d oesn't allow for you to have the option to not automatically start the Xserver... Unfortunately, (I'm sure someone has a better idea) the only solution I have is to reinstall red hat.. :( > > -Original Message- > > Fro
Re: [XFree86] Screen Resolution
The X server startup script is /etc/X11/xinit/xinitrc. The automatic startup of X server is typically done in rc.sysinit script. James Thogmartin wrote: Where would he find the startup script? -Original Message- From: Bukie Mabayoje [EMAIL PROTECTED] Date: Mon, 03 Jan 2005 15:41:14 To:xfree86@xfree86.org Subject: Re: [XFree86] Screen Resolution X11 is started at run level 5 on Redhat. If you don't what it started don't run at level 5. But then, other multi-user stuff wouldn't be available. You better off removing from the startup script. look at /etc/X11/XF86Config and locate the text below. What does it say? section Screen Identifier Screen0 Device Videocard0 MonitorMonitor0 DefaultDepth 24 SubSection Display Depth 24 Modes1024x768 800x600 640x480 EndSubSection EndSection James Thogmartin wrote: That's what I hate about red hat.. It appears that the new version of it doesn't allow for you to have the option to not automatically start the Xserver... Unfortunately, (I'm sure someone has a better idea) the only solution I have is to reinstall red hat.. :( -Original Message- From: Bob Pelletier [EMAIL PROTECTED] Date: Mon, 03 Jan 2005 12:45:26 To:xfree86@xfree86.org Subject: Re: [XFree86] Screen Resolution Hi Jason. Thanks for responding. I did the alt-ctl-backspace and the screen flashed and went back to the LOGIN screen which is the first screen with print overlaying itself. For example RED HAT is sitting right on top of my Welcome to .. Also tool bar is unreadable due to words too big. Any ideas. Thanks. Bob James Thogmartin [EMAIL PROTECTED] wrote: You can hit control+alt+backspace until the Xserver dies, to force it to close.. But for restarting the Xserver, it means to simply shutdown the Xserver, and putting in startx again.. IF you have access to the console, if not, you probably need to reboot... -Original Message- From: Bob Pelletier Date: Mon, 03 Jan 2005 11:56:33 To:xfree86@xfree86.org Subject: Re: [XFree86] Screen Resolution Hi. I am having the same problem with the same DELL stuff. I have been trying to get an answer for a couple of weeks on how to fix it. I have reinstalled. I am about to try different hardware. Let me know if you hear anything. Thanks. Bob Asadullah FAYZi wrote: Hi; I have just started instalation of Redhat 9, Howevr i am not able to change the screen Resolution from 800x600, I tried mony times but didnt work. after setting the resolution to 1024x768 the system wants me to logout and restart Xserver.After logging out i see that the sitting is back to previous value.Actullay i have two questios 1- what does it mean by restarting Xserver? 2-How can I set the resolution to desired values. i am using Dell branded PC with intel 865 main Board. Can anyone help me in this regard please, __ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. BlackBerry service provided by Nextel ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 Do you Yahoo!? Yahoo! Mail - now with 250MB free storage. Learn more. BlackBerry service provided by Nextel ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 BlackBerry service provided by Nextel ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Screen Resolution
So do I edit /etc/X11/xinit/xinitrc? no Am I editing the same section of code? not really My comment below was a response to your original statement in black below > X11 is started at run level 5 on Redhat. If you don't what it started don't run at level 5. But then, other multi-user stuff wouldn't be available. You better off removing from the startup script.. The X server startup script is /etc/X11/xinit/xinitrc. The automatic startup of X server is typically done in rc.sysinit script. > > That's what I hate about red hat.. It appears that the new version of it doesn't allow for you to have the option to not automatically start the Xserver... Unfortunately, (I'm sure someone has a better idea) the only solution I have is to reinstall red hat.. :( The real problem is the following: > > Hi. I am having the same problem with the same DELL stuff. I have been trying to get an answer for a couple of weeks on how to fix it. I have reinstalled. I am about to try different hardware. Let me know if you hear anything. Thanks. > > Bob > > > > Asadullah FAYZi wrote: Hi; > > I have just started instalation of Redhat 9, Howevr i am not able to > > change the screen Resolution from 800x600, I tried mony times but didnt > > work. after setting the resolution to 1024x768 the system wants me to > > logout and restart Xserver.After logging out i see that the sitting is > > back to previous value.Actullay i have two questios > > 1- what does it mean by restarting Xserver? > > 2-How can I set the resolution to desired values. > > i am using Dell branded PC with intel 865 main Board. > > > > Can anyone help me in this regard please, It seems that you can't get 1024x768 resolution, I am correct? Can you post your /etc/X11/XF86Config file? If it is a configuration script problem I will be able to tell you immediately or else I have to install redhat 9.0 on my play box and see if I can duplicate the problem. My play box is being used right now to build Xfree86 4.4.0 on debian 3.0r3 and it is not going very well at the moment. The other machines are production machines that I can't mess with, they are running RH EL3.0 and doing 1024x768 on the local console. Bob Pelletier wrote: Hi. Thanks again. So do I edit /etc/X11/xinit/xinitrc? Am I editing the same section of code?Bob Bukie Mabayoje [EMAIL PROTECTED]> wrote: The X server startup script is /etc/X11/xinit/xinitrc. The automatic startup of X server is typically done in rc.sysinit script. James Thogmartin wrote: > Where would he find the startup script? > -Original Message- > From: Bukie Mabayoje<[EMAIL PROTECTED]> > Date: Mon, 03 Jan 2005 15:41:14 > To:xfree86@xfree86.org > Subject: Re: [XFree86] Screen Resolution > > X11 is started at run level 5 on Redhat. If you don't what it started don't run at level 5. But then, other multi-user stuff wouldn't be available. You better off removing from the startup script. > > look at /etc/X11/XF86Config and locate the text below. What does it say? > > section "Screen" > Identifier "Screen0" > Device "Videocard0" > Monitor "Monitor0" > DefaultDepth 24 > SubSection "Display" > Depth 24 > Modes "1024x768" "800x600" "640x480" > EndSubSection > EndSection > > James Thogmartin wrote: > > > That's what I hate about red hat.. It appears that the new version of it doesn't allow for you to have the option to not automatically start the Xserver... Unfortunately, (I'm sure someone has a better idea) the only solution I have is to reinstall red hat.. :( > > -Original Message- > > From: Bob Pelletier<[EMAIL PROTECTED]> > > Date: Mon, 03 Jan 2005 12:45:26 > > To:xfree86@xfree86.org > > Subject: Re: [XFree86] Screen Resolution > > > > Hi Jason. Thanks for responding. I did the alt-ctl-backspace and the screen flashed and went back to the LOGIN screen which is the first screen with print overlaying itself. For example RED HAT is sitting right on top of my Welcome to .. Also tool bar is unreadable due to words too big. Any ideas. Thanks. > > Bob > > > > James Thogmartin<[EMAIL PROTECTED]>wrote: You can hit control+alt+backspace until the Xserver dies, to force it to close.. But for restarting the Xserver, it means to simply shutdown the Xserver, and putting in startx again.. IF you have access to the console, if not, you probably need to reboot... > > -Original Message- > > From: Bob Pelletier > > Date: Mon, 03 Jan 2005 11:56:33 > > To:xfree86@xfree86.org > > Subject: Re: [XFree86] Screen Resolution > > > > Hi. I am having the same problem with the same DELL stuff. I have been trying to get an answer for a couple of weeks on how to fix it. I have reinsta
Re: [XFree86] another error while trying to compile xfree86 4.4.0
I like to duplicate your env here so that I can see what is going on (basically do the build). I need more info about your toolset package and which woody? You said 3.0 r3 or r4 James Thogmartin wrote: This is starting to feel like a never ending battle..: cd ../../exports/lib ln -s ../../lib/font/libXfont.a . make[4]: *** No rule to make target `fontfile/module/DONE', needed by `libfontbase.a'. Stop. make[4]: Leaving directory `/root/xc/lib/font' make[3]: *** [all] Error 2 make[3]: Leaving directory `/root/xc/lib' make[2]: *** [all] Error 2 make[2]: Leaving directory `/root/xc' make[1]: *** [World] Error 2 make[1]: Leaving directory `/root/xc' make: *** [World] Error 2 cryptic-networks:~/xc# now, I can replace files that it supposedly cant find.. thats no problem.. but I have no idea how to fix this one.. Computers are like air conditioners. They don't work properly if you open Windows.
Re: [XFree86] another error while trying to compile xfree86 4.4.0
I have a fresh 3.0r3 installed now, I will try and follow your steps. -- Install the packages as I go when I need them. I will get back to you soon. James Thogmartin wrote: I did the net install, and as far as the toolset goes, Im just installing packages as I go when I need them From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf OfBukie Mabayoje Sent: Monday, January 03, 2005 7:44 AM To: xfree86@xfree86.org Subject: Re: [XFree86] another error while trying to compile xfree86 4.4.0 I like to duplicate your env here so that I can see what is going on (basically do the build). I need more info about your toolset package and which woody? You said 3.0 r3 or r4 James Thogmartin wrote: This is starting to feel like a never ending battle..: cd ../../exports/lib ln -s ../../lib/font/libXfont.a . make[4]: *** No rule to make target `fontfile/module/DONE', needed by `libfontbase.a'. Stop. make[4]: Leaving directory `/root/xc/lib/font' make[3]: *** [all] Error 2 make[3]: Leaving directory `/root/xc/lib' make[2]: *** [all] Error 2 make[2]: Leaving directory `/root/xc' make[1]: *** [World] Error 2 make[1]: Leaving directory `/root/xc' make: *** [World] Error 2 cryptic-networks:~/xc# now, I can replace files that it supposedly cant find.. thats no problem.. but I have no idea how to fix this one.. Computers are like air conditioners. They don't work properly if you open Windows.
Re: [XFree86] Screen Resolution
X11 is started at run level 5 on Redhat. If you don't what it started don't run at level 5. But then, other multi-user stuff wouldn't be available. You better off removing from the startup script. look at /etc/X11/XF86Config and locate the text below. What does it say? section Screen Identifier Screen0 Device Videocard0 MonitorMonitor0 DefaultDepth 24 SubSection Display Depth 24 Modes1024x768 800x600 640x480 EndSubSection EndSection James Thogmartin wrote: That's what I hate about red hat.. It appears that the new version of it doesn't allow for you to have the option to not automatically start the Xserver... Unfortunately, (I'm sure someone has a better idea) the only solution I have is to reinstall red hat.. :( -Original Message- From: Bob Pelletier [EMAIL PROTECTED] Date: Mon, 03 Jan 2005 12:45:26 To:xfree86@xfree86.org Subject: Re: [XFree86] Screen Resolution Hi Jason. Thanks for responding. I did the alt-ctl-backspace and the screen flashed and went back to the LOGIN screen which is the first screen with print overlaying itself. For example RED HAT is sitting right on top of my Welcome to .. Also tool bar is unreadable due to words too big. Any ideas. Thanks. Bob James Thogmartin [EMAIL PROTECTED] wrote: You can hit control+alt+backspace until the Xserver dies, to force it to close.. But for restarting the Xserver, it means to simply shutdown the Xserver, and putting in startx again.. IF you have access to the console, if not, you probably need to reboot... -Original Message- From: Bob Pelletier Date: Mon, 03 Jan 2005 11:56:33 To:xfree86@xfree86.org Subject: Re: [XFree86] Screen Resolution Hi. I am having the same problem with the same DELL stuff. I have been trying to get an answer for a couple of weeks on how to fix it. I have reinstalled. I am about to try different hardware. Let me know if you hear anything. Thanks. Bob Asadullah FAYZi wrote: Hi; I have just started instalation of Redhat 9, Howevr i am not able to change the screen Resolution from 800x600, I tried mony times but didnt work. after setting the resolution to 1024x768 the system wants me to logout and restart Xserver.After logging out i see that the sitting is back to previous value.Actullay i have two questios 1- what does it mean by restarting Xserver? 2-How can I set the resolution to desired values. i am using Dell branded PC with intel 865 main Board. Can anyone help me in this regard please, __ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. BlackBerry service provided by Nextel ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 Do you Yahoo!? Yahoo! Mail - now with 250MB free storage. Learn more. BlackBerry service provided by Nextel ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] PLEASE HELP Fatal server error: no screens found
Try matching the depth/bpp with windows 24/32 or just do as the message say. (EE) VMWARE(0): Currently unavailable depth/bpp of 16/16 requested. The guest X server must run at the same depth and bpp as the host (which are currently 24/32). This is automatically detected. Please do not specify a depth on the command line or via the config file. smjscollins wrote: I am using VMware Workstation 4.5.2 on a WIN XP Host. I installed RedHat 9.0 on a virtual machine. I then modified the "Display" settings and color resolution useing GNOME desktop and this resolted in : (Please see attached XFree86.0.log and XF86Config for more detail) "(II) Setting vga for screen 0. (--) VMWARE(0): VMware SVGA regs at (0x1460, 0x1461) (II) Loading sub module "vgahw" (II) LoadModule: "vgahw" (II) Loading /usr/X11R6/lib/modules/libvgahw.a (II) Module vgahw: vendor="The XFree86 Project" compiled for 4.3.0, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.6 (--) VMWARE(0): caps: 0x3FF3 (--) VMWARE(0): depth: 24 (--) VMWARE(0): bpp: 32 (--) VMWARE(0): vram: 16777216 (--) VMWARE(0): pbase: 0xf600 (--) VMWARE(0): mwidt: 2360 (--) VMWARE(0): mheig: 1770 (EE) VMWARE(0): Currently unavailable depth/bpp of 16/16 requested. The guest X server must run at the same depth and bpp as the host (which are currently 24/32). This is automatically detected. Please do not specify a depth on the command line or via the config file. (II) UnloadModule: "vmware" (II) UnloadModule: "vgahw" (II) Unloading /usr/X11R6/lib/modules/libvgahw.a (EE) Screen(s) found, but none have a usable configuration. 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]" I have been doing my due dilligance searching he internet for answers and have hit a road block - can you please point me to the appropriate section of the Config to fix this problem? Regards, Sean Collins XFree86 Version 4.3.0 (Red Hat Linux release: 4.3.0-2) Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.20-3bigmem i686 [ELF] Build Date: 27 February 2003 Build Host: porky.devel.redhat.com Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present OS Kernel: Linux version 2.4.20-8smp ([EMAIL PROTECTED]) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 SMP Thu Mar 13 17:45:54 EST 2003 PF 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: Sun Jan 2 05:34:24 2005 (==) Using config file: "/etc/X11/XF86Config" (==) ServerLayout "Simple Layout" (**) |-->Screen "Screen 1" (0) (**) | |-->Monitor "vmware" (**) | |-->Device "VMware SVGA" (**) |-->Input Device "Mouse1" (**) |-->Input Device "Keyboard" (**) Option "AutoRepeat" "500 30" (WW) Option "XkbCompat" requires an string value (**) Option "XkbRules" "xfree86" (**) XKB: rules: "xfree86" (**) Option "XkbModel" "pc104" (**) XKB: model: "pc104" (**) Option "XkbLayout" "us" (**) XKB: layout: "us" (==) Keyboard: CustomKeycode disabled (**) FontPath set to "/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75dpi/:unscaled,/usr/X11R6/lib/X11/fonts/100dpi/:unscaled,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/" (**) RgbPath set to "/usr/X11R6/lib/X11/rgb" (==) ModulePath set to "/usr/X11R6/lib/modules" (--) using VT number 7 (II) Open APM successful (II) Module ABI versions: XFree86 ANSI C Emulation: 0.2 XFree86 Video Driver: 0.6 XFree86 XInput driver : 0.4 XFree86 Server Extension : 0.2 XFree86 Font Renderer : 0.4 (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.3.0, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (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.3.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (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,7190 card 15ad,1976 rev 01 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,7191 card , rev 01 class 06,04,00 hdr 01 (II) PCI: 00:07:0: chip 8086,7110 card 15ad,1976 rev 08 class 06,01,00 hdr 80 (II) PCI:
Re: [XFree86] (no subject)
try a monitor that can do the minimum vga res. You have ega monitor it seems. K Vanitha wrote: Dear Sir/Madam, please find attachment. This is the error displayed while trying to StartX in Linux 7.2. Send me the possible solutions to sort out the problem. Regards, Vanitha. Name: temp tempType: Plain Text (TEXT/PLAIN) Encoding: BASE64 ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] nvidia GeForce FX 5200
Check out this document: www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/pdf/XFree-Local-multi-user-HOWTO.pdf [EMAIL PROTECTED] wrote: I am trying to load linux on my machine and I can not get the X server to run. I am assuming it is a problem with this driver? Do you have a step by step solution for me? ___ XFree86 mailing list XFree86@XFree86.Org http://XFree86.Org/mailman/listinfo/xfree86
