Re: StartX problem solved !!
First of all THANX a lot for helping me.. I havent tried the i810 driver i always trying VESA or VIA for the monitor driver.. Now i can boot perfectly and the serial mouse problem is also solved after selecting MICROSOFT in the input device section I found this from the debian forum itself. THank you once again.. Best Wishes..and have a nice time.. Ankur Patel. On 2/14/07, cga2000 [EMAIL PROTECTED] wrote: On Mon, Feb 12, 2007 at 03:56:05PM EST, Kent West wrote: conn intel wrote: USING $ startx $(which xterm) -- :6 , I am getting the blank screen as said and using ctrl alt backspace i am able to return back to the command prompt. Here is the output of 'lspci' attached with the email. Note :: I am getting vertical strips when default system boots or when i try to start graphical interface...in any case it shows vertical strips.but it wont go ahead of that and stucks there itself without prompting for login screen. 5)Are you getting any error messages that are not part of the log files you've included? No.. I am not getting any error message. Check /var/log/xorg.0.log (or /var/log/XFree86.0.log) and look for lines with EE or WW. They may be clues. Also, somewhere in that file should be a notice as to which configuration file it's using. Make sure that file is the same one you're tinkering with. 6)Have you tried the vga driver in XF86Config-4 instead of vesa, or have you tried dropping the DefaultDepth from 24 to 16? I have tried all the way. Both good suggestions in my experience at least. Another thing that has worked for me in the past though I am unsure why is to make sure you boot to the vesafb framebuffer. You need to give the boot loader and extra parm: vga=nnn -- something conservative such as vga=791 should be fine. In grub it's easy to do it on the fly .. you arrow down to whatever you want to boot and then type 'e' for edit and then arrow down again to the line that says something like kernel .. type 'e' again .. add the vga parm at the end of the line .. hit enter .. I think .. and then hit 'b' to start booting .. I'm sure you can do it with lilo as well but I can't remember all the details. I think you need to hit TAB and after that it's pretty much the same. Yeah, I know .. this all sounds a little crazy .. but since it shouldn't take more than a couple minutes .. I would give it a shot. Thanks, cga -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: StartX problem
On Mon, Feb 12, 2007 at 03:56:05PM EST, Kent West wrote: conn intel wrote: USING $ startx $(which xterm) -- :6 , I am getting the blank screen as said and using ctrl alt backspace i am able to return back to the command prompt. Here is the output of 'lspci' attached with the email. Note :: I am getting vertical strips when default system boots or when i try to start graphical interface...in any case it shows vertical strips.but it wont go ahead of that and stucks there itself without prompting for login screen. 5)Are you getting any error messages that are not part of the log files you've included? No.. I am not getting any error message. Check /var/log/xorg.0.log (or /var/log/XFree86.0.log) and look for lines with EE or WW. They may be clues. Also, somewhere in that file should be a notice as to which configuration file it's using. Make sure that file is the same one you're tinkering with. 6)Have you tried the vga driver in XF86Config-4 instead of vesa, or have you tried dropping the DefaultDepth from 24 to 16? I have tried all the way. Both good suggestions in my experience at least. Another thing that has worked for me in the past though I am unsure why is to make sure you boot to the vesafb framebuffer. You need to give the boot loader and extra parm: vga=nnn -- something conservative such as vga=791 should be fine. In grub it's easy to do it on the fly .. you arrow down to whatever you want to boot and then type 'e' for edit and then arrow down again to the line that says something like kernel .. type 'e' again .. add the vga parm at the end of the line .. hit enter .. I think .. and then hit 'b' to start booting .. I'm sure you can do it with lilo as well but I can't remember all the details. I think you need to hit TAB and after that it's pretty much the same. Yeah, I know .. this all sounds a little crazy .. but since it shouldn't take more than a couple minutes .. I would give it a shot. Thanks, cga -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: StartX problem
On Sat, Feb 10, 2007 at 06:34:53PM -0500, cga2000 wrote: Same as Kent says according to the Xfree86 log, it does not look like X is having any kind of problem. Try the following from a linux console: $ startx $(which xterm) -- :6 Does anything happen? If all you have is a blank screen, you may be in X already and you should be able to get back to a linux console via Ctrl+Alt+Backspace and/or Ctrl+Alt+Fn (F1, F2, F3..). Please provide more detail as to what you are doing since that does not appear in logs and config file. Also just typing: 'X' (without the quotes) at a shell prompt will also help eliminate the DE, WM, etc. As cga2000 wrote: Ctrl+Alt+Backspace will get back to your shell prompt. -- Chris. == Don't forget to check that your /etc/apt/sources.lst entries point to etch and not testing, otherwise you may end up with a broken system once etch goes stable. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: StartX problem
Hello Friends, Thank You for your responses. I have work around what you all have said :: USING $ startx $(which xterm) -- :6 , I am getting the blank screen as said and using ctrl alt backspace i am able to return back to the command prompt. Here is the output of 'lspci' attached with the email. Note :: I am getting vertical strips when default system boots or when i try to start graphical interface...in any case it shows vertical strips.butit wont go ahead of that and stucks there itself without prompting for login screen. 1) Do you, or do you not have gdm installed? Yes, i do have gdm and xdm installed. 2)Is gdm trying to start and then failing? YES 3) Are you then trying to run startx? After getting failure from gdm...i am killing all the processes related to gdm and then trying to start using startx. 4) Are you doing so as a normal user or as root (I believe root will fail on startx by default)? I have also tried to start using normal user but invain. 5)Are you getting any error messages that are not part of the log files you've included? No.. I am not getting any error message. 6)Have you tried the vga driver in XF86Config-4 instead of vesa, or have you tried dropping the DefaultDepth from 24 to 16? I have tried all the way. I have tried with kernel version 2.6.8 default which is coming with debain-3.1r1 sarge. Again waiting for your responses.. Thank You, Ankur. Have a Nice time and Good day ahead.. PC Configuration :: Pentium III processor with 128 MB ram, 80GB hardisk, Samtron '56V' monitor, logitech (serial) mouse, TVS Gold Keyboard,LG CDROM. OUTPUT :: LSPCI command :00:00.0 Host bridge: Intel Corp. 82810E DC-133 GMCH [Graphics Memory Controller Hub] (rev 03) :00:01.0 VGA compatible controller: Intel Corp. 82810E DC-133 CGC [Chipset Graphics Controller] (rev 03) :00:1e.0 PCI bridge: Intel Corp. 82801AA PCI Bridge (rev 02) :00:1f.0 ISA bridge: Intel Corp. 82801AA ISA Bridge (LPC) (rev 02) :00:1f.1 IDE interface: Intel Corp. 82801AA IDE (rev 02) :00:1f.2 USB Controller: Intel Corp. 82801AA USB (rev 02) :00:1f.3 SMBus: Intel Corp. 82801AA SMBus (rev 02) :00:1f.5 Multimedia audio controller: Intel Corp. 82801AA AC'97 Audio (rev 02) :01:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
Re: StartX problem
conn intel wrote: USING $ startx $(which xterm) -- :6 , I am getting the blank screen as said and using ctrl alt backspace i am able to return back to the command prompt. Here is the output of 'lspci' attached with the email. Note :: I am getting vertical strips when default system boots or when i try to start graphical interface...in any case it shows vertical strips.but it wont go ahead of that and stucks there itself without prompting for login screen. 5)Are you getting any error messages that are not part of the log files you've included? No.. I am not getting any error message. Check /var/log/xorg.0.log (or /var/log/XFree86.0.log) and look for lines with EE or WW. They may be clues. Also, somewhere in that file should be a notice as to which configuration file it's using. Make sure that file is the same one you're tinkering with. 6)Have you tried the vga driver in XF86Config-4 instead of vesa, or have you tried dropping the DefaultDepth from 24 to 16? I have tried all the way. I'm unsure what all the way means. I'd try even dropping down to 8. I would also try the i810 driver. Also, since this is an integrated driver, that means it's using system RAM; there may be an option in the BIOS to up the available video memory; look into that. (Dell had a series of computers four or five years ago in which a certain BIOS (A03 maybe?) was buggy and didn't correctly report the 8 MB assigned in the BIOS to the OS; a firmware update solved that for me.) PC Configuration :: Pentium III processor with 128 MB ram, 80GB hardisk, Samtron '56V' monitor, logitech (serial) mouse, TVS Gold Keyboard,LG CDROM. OUTPUT :: LSPCI command :00:00.0 Host bridge: Intel Corp. 82810E DC-133 GMCH [Graphics Memory Controller Hub] (rev 03) :00:01.0 VGA compatible controller: Intel Corp. 82810E DC-133 CGC [Chipset Graphics Controller] (rev 03) snip -- Kent West http://kentwest.blogspot.com http://kentwest.blogspot.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: StartX problem
conn intel wrote: Hello friends, I am using debian for few yrs.but i havent seen such problem.. I have installed it on pentium III machine and i could not able to do startx. I am not getting graphical version. could anyone give their suggestions..? Here is the XF86config-4 , XFree86.0.log and gdm.log are attached with this email. Thank You.. Have a Nice time and good day ahead. Ankur. I don't see any obvious errors in your XFree86.0.log. However, I'm confused by your mention of startx and inclusion of a gdm.log file. If gdm is running, then I would expect startx to fail. If gdm tried to start, but failed, and then you manually tried startx, I'm unsure if gdm might not still be causing blockage (although I don't think so). Can you give us a bit more detail? Do you, or do you not have gdm installed? Is gdm trying to start and then failing? Are you then trying to run startx? Are you doing so as a normal user or as root (I believe root will fail on startx by default)? Are you getting any error messages that are not part of the log files you've included? Has it ever worked on this machine? What is the output of lspci? How much RAM is on your video card? Have you tried the vga driver in XF86Config-4 instead of vesa, or have you tried dropping the DefaultDepth from 24 to 16? -- Kent West Westing Peacefully http://kentwest.blogspot.com
Re: StartX problem
On Sat, Feb 10, 2007 at 04:15:24PM EST, conn intel wrote: Hello friends, I am using debian for few yrs.but i havent seen such problem.. I have installed it on pentium III machine and i could not able to do startx. I am not getting graphical version. could anyone give their suggestions..? Here is the XF86config-4 , XFree86.0.log and gdm.log are attached with this email. Thank You.. Have a Nice time and good day ahead. Ankur. Same as Kent says according to the Xfree86 log, it does not look like X is having any kind of problem. Try the following from a linux console: $ startx $(which xterm) -- :6 Does anything happen? If all you have is a blank screen, you may be in X already and you should be able to get back to a linux console via Ctrl+Alt+Backspace and/or Ctrl+Alt+Fn (F1, F2, F3..). Please provide more detail as to what you are doing since that does not appear in logs and config file. Thanks, cga -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: startx problem
On Thu, 17 Jul 2003 11:12:44 +1000 Jennifer [EMAIL PROTECTED] wrote: , then I use command to test X startx, but I could not start X, rather I get the error message. Please see the attached file for details. from attachment (II) LoadModule: xtt (II) Loading /usr/X11R6/lib/modules/fonts/libxtt.a Duplicate symbol TT_FreeType_Version in /usr/X11R6/lib/modules/fonts/libxtt.a:xttmodule.o Also defined in /usr/X11R6/lib/modules/fonts/libfreetype.a Looks like two modules are butting heads trying to do the same thing. I'm not familiar with xtt, but I think that onlyfreetype is used in typical setups. Edit /etc/X11/XF86Config - probably towards the top there's a Module section that contains lines like Load xtt Load freetype Delete or comment out (#) the xtt line and see if that helps. Todd -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: startx problem
Looks like two modules are butting heads trying to do the same thing. I'm not familiar with xtt, but I think that onlyfreetype is used in typical setups. Edit /etc/X11/XF86Config - probably towards the top there's a Module section that contains lines like Load xtt Load freetype Delete or comment out (#) the xtt line and see if that helps. ** Hi, Todd, I edit /etc/X11/XF86Config-4 (by the way, it is XF86Config-4, not XF86Config). and commented out (#) the line of Load xtt. Now I reboot and startx. I still could not start X, and it came another problem. Something like: Fatal server error: Add Scren/ScrenInit failed for driver0 Please see the attached for detail. What should I do next? Thank you very much for your advice Jennifer XFREE86.0 Description: Binary data
Re: startx problem
Jennifer wrote: Looks like two modules are butting heads trying to do the same thing. I'm not familiar with xtt, but I think that onlyfreetype is used in typical setups. Edit /etc/X11/XF86Config - probably towards the top there's a Module section that contains lines like Load xtt Load freetype Delete or comment out (#) the xtt line and see if that helps. ** Hi, Todd, I edit /etc/X11/XF86Config-4 (by the way, it is XF86Config-4, not XF86Config). and commented out (#) the line of Load xtt. Now I reboot and startx. I still could not start X, and it came another problem. Something like: Fatal server error: Add Scren/ScrenInit failed for driver0 Please see the attached for detail. What should I do next? Thank you very much for your advice Jennifer It looks like you may be using the framebuffer. Look in XF86Config-4 for a line referring to framebuffer, and if it's set to Yes, set it to No and give that a try. -- Kent -- Kent West ([EMAIL PROTECTED]) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: startx problem
It looks like you may be using the framebuffer. Look in XF86Config-4 for a line referring to framebuffer, and if it's set to Yes, set it to No and give that a try. -- Dear Kent and other Debian users, I could not find any words like framebuffer in XF86Config-4. so I used dpkg-reconfigure xserver-xfree86; and I did not select using framebuffer this time. Then I reboot the system and startx. But It looks like coming the same problem. Please see the attached log file and also can you please have a look at my configure of XF86Config-4, any mistakes I made there? Thanks very much. Jennifer Kent -- Kent West ([EMAIL PROTECTED]) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] XFREE86.0 Description: Binary data XF86CONF Description: Binary data
Re: startx problem
On Thu, 17 Jul 2003 14:06:07 +1000 Jennifer [EMAIL PROTECTED] wrote: Then I reboot the system and startx. But It looks like coming the same problem. Please see the attached log file... No, it's a very different problem. You did read the log file, didn't you? We see... snip from log ==) VGA(0): videoRam: 256 kBytes. ... (II) VGA(0): Not using default mode 640x350 (insufficient memory for mode) (II) VGA(0): Not using default mode 640x400 (insufficient memory for mode) onward and onward through the modes So X thinks your video card has only 256K of RAM - note that's a K, not an M. No remotely standard video mode can squash its data into 256K. Not sure why debconf got the memory so wrong. You could try running the configuration program again as before - this time, be sure to 1) select the appropriate card - GeForce or nvidia or similar and 2) specify the video memory - you may need to give this in KB, i.e. 64MB = 64 x 1024K = 65536K. Alternatively, you could edit XF86Config-4 by hand. Change the driver line in the Device section to vesa or maybe nv and add a line in the same section that says VideoRam 65536 Hope that helps... Todd -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: startx problem--fixed!
Dear Todd This time I edited XF86Config-4 by hand(vi). Change the driver line in the Device section to vesa , and add a line in the same section that says VideoRam 65536 Then reboot, and the Gnome was beautifully appearing in front of me. Woo, so nice to see it. Very good. I know I would not have had such good feeling without you and all other Debian users' help. Thanks very much for all your precious help and time. It is really great to have experts helping you along before you are pulling all your hair off. Now I will advance to my next hard trip_install Oracle 9i on Debian! Best regards Jennifer No, it's a very different problem. You did read the log file, didn't you? We see... snip from log ==) VGA(0): videoRam: 256 kBytes. ... (II) VGA(0): Not using default mode 640x350 (insufficient memory for mode) (II) VGA(0): Not using default mode 640x400 (insufficient memory for mode) onward and onward through the modes So X thinks your video card has only 256K of RAM - note that's a K, not an M. No remotely standard video mode can squash its data into 256K. Not sure why debconf got the memory so wrong. You could try running the configuration program again as before - this time, be sure to 1) select the appropriate card - GeForce or nvidia or similar and 2) specify the video memory - you may need to give this in KB, i.e. 64MB = 64 x 1024K = 65536K. Alternatively, you could edit XF86Config-4 by hand. Change the driver line in the Device section to vesa or maybe nv and add a line in the same section that says VideoRam 65536 Hope that helps... Todd -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: startx problem
Tran Tuan Anh wrote: Hi all, I've just installed Debian, but cannot bring the window system up. When I run startx it gives Fatal server error: no screens found. I am using Philips 107S monitor, Video adapter: GeForce2 MX, 64 MB Could anyone tell me how to set this up? Thanks a lot! Tuan Anh Yeah, RTFM. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: startx problem
On Sun, Apr 06, 2003 at 05:08:14PM +0300, yaron wrote: Tran Tuan Anh wrote: Hi all, I've just installed Debian, but cannot bring the window system up. When I run startx it gives Fatal server error: no screens found. I am using Philips 107S monitor, Video adapter: GeForce2 MX, 64 MB Could anyone tell me how to set this up? Thanks a lot! Tuan Anh Yeah, RTFM. Useful, really useful. Tran, try this: man XF86Config-4 If it's more technical than you're used to - try again! Come and ask again if you've /really/ tried to work it out. People here aren't all as rude as the last answer you got, but they're not a hand-holding community - you get what you pay for :-) Hope this helps, jc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: startx problem - one step closer
Dave Bacon wrote: Thanks to Jaume for the very helpful reply. After following the suggestion listed below I am now able to bring up a graphical display, but it is only an x(mouse cursor) on top of a coarse gray back ground. I am not sure, but I think I still may need to specify which Window Manager to use. Am I on the right track? If so, how do I tell X which window manager to bring up by default. Hi, just edit your .xsession file ;-) or the global one located at /etc/X11/Xsession or either apt-get intall --reinstall _your_favorite_window_manager have luck! jaume.
Re: startx problem - $??P?+@(
Dave Bacon wrote: Hello, I have just upgraded quite a few packages with dselect. And now when I run startx I receive the following error messages. Can you help? var: allowed_users, value: rootonly var: nice_value, value: . /etc/X11/X is not executable ls -l /etc/X11/X and look at the file that X is linked to, then: find / -name _file_ ln -s path_to_file /etc/X11/X have luck ! jaume. Doesn't that creates a file with a strange name in the dir from which startx was run? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Shaul Karl [EMAIL PROTECTED]
Re: startx problem
Dave Bacon wrote: Hello, I have just upgraded quite a few packages with dselect. And now when I run startx I receive the following error messages. Can you help? var: allowed_users, value: rootonly var: nice_value, value: . /etc/X11/X is not executable ls -l /etc/X11/X and look at the file that X is linked to, then: find / -name _file_ ln -s path_to_file /etc/X11/X have luck ! jaume.
Re: startx problem - one step closer
Thanks to Jaume for the very helpful reply. After following the suggestion listed below I am now able to bring up a graphical display, but it is only an x(mouse cursor) on top of a coarse gray back ground. I am not sure, but I think I still may need to specify which Window Manager to use. Am I on the right track? If so, how do I tell X which window manager to bring up by default. Thanks again for your help Dave Bacon Jaume Teixi wrote: Dave Bacon wrote: Hello, I have just upgraded quite a few packages with dselect. And now when I run startx I receive the following error messages. Can you help? var: allowed_users, value: rootonly var: nice_value, value: . /etc/X11/X is not executable ls -l /etc/X11/X and look at the file that X is linked to, then: find / -name _file_ ln -s path_to_file /etc/X11/X have luck ! jaume. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- _ Dave G. Bacon Computer Network Manager Outagamie Waupaca Library System 225 N. Oneida St., Appleton, WI 54911 920/832-6193(voice), 920/832-6422(FAX) [EMAIL PROTECTED] _
Re: startx problem
is there any problem? the stuff below looks like normal X run. the X is probably on vt7 generally, when you wantto launch X you run startx (from command line) or xdm (usually from inittab). erik Pascal THIVENT wrote: Hi, when i launch X, i get this message : XFree86 Version 3.3.6 / X Window System (protocol Version 11, revision 0, vendor release 6300) Release Date: January 8 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://www.XFree86.Org/FAQ) Operating System: Linux 2.2.17pre10 i686 [ELF] Configured drivers: S3V: accelerated server for S3 graphics adaptors (Patchlevel 0) s3_ViRGE (using VT number 7) XF86Config: /usr/X11R6/lib/X11/XF86Config (**) stands for supplied, (--) stands for probed/default values (**) XKB: keymap: xfree86(fr) (overrides other XKB settings) (**) Mouse: type: Microsoft, device: /dev/mouse, baudrate: 1200 (**) Mouse: buttons: 3 (**) S3V: Graphics device ID: DSV3325DX (**) S3V: Monitor ID: CM0800 (--) S3V: Mode 800x600 needs hsync freq of 64.02 kHz. Deleted. (--) S3V: Mode 1024x768 needs hsync freq of 62.50 kHz. Deleted. (--) S3V: Mode 1152x864 needs hsync freq of 62.42 kHz. Deleted. (--) S3V: Mode 1280x1024 needs hsync freq of 64.25 kHz. Deleted. (--) S3V: Mode 1024x768 needs hsync freq of 70.24 kHz. Deleted. (--) S3V: Mode 1152x864 needs hsync freq of 70.88 kHz. Deleted. (--) S3V: Mode 1280x1024 needs hsync freq of 74.59 kHz. Deleted. (--) S3V: Mode 1600x1200 needs hsync freq of 75.00 kHz. Deleted. (--) S3V: Mode 1152x864 needs hsync freq of 76.01 kHz. Deleted. (--) S3V: Mode 1280x1024 needs hsync freq of 78.86 kHz. Deleted. (--) S3V: Mode 1024x768 needs hsync freq of 80.21 kHz. Deleted. (--) S3V: Mode 1280x1024 needs hsync freq of 81.13 kHz. Deleted. (--) S3V: Mode 1600x1200 needs hsync freq of 87.50 kHz. Deleted. (--) S3V: Mode 1152x864 needs hsync freq of 89.62 kHz. Deleted. (--) S3V: Mode 1280x1024 needs hsync freq of 91.15 kHz. Deleted. (--) S3V: Mode 1600x1200 needs hsync freq of 93.75 kHz. Deleted. (--) S3V: Mode 1600x1200 needs hsync freq of 105.77 kHz. Deleted. (--) S3V: Mode 1280x1024 needs hsync freq of 107.16 kHz. Deleted. (--) S3V: Mode 1800X1440 needs hsync freq of 96.15 kHz. Deleted. (--) S3V: Mode 1800X1440 needs hsync freq of 104.52 kHz. Deleted. (**) FontPath set to /usr/lib/X11/fonts/misc/:unscaled,/usr/lib/X11/fonts/75dpi/:unscaled,/usr/l ib/X11/fonts/100dpi/:unscaled,/usr/lib/X11/fonts/Type1/,/usr/lib/X11/fonts/S peedo/,/usr/lib/X11/fonts/misc/,/usr/lib/X11/fonts/75dpi/,/usr/lib/X11/fonts /100dpi/ (--) S3V: PCI: ViRGE/DX or /GX rev 1, Linear FB @ 0xf000 (--) S3V: chipset: ViRGE/DX rev. 1 (**) S3V: chipset driver: s3_VIRGE (**) S3V: videoram: 4096k (**) S3V: Ramdac type: s3_trio64 (**) S3V: Ramdac speed: 170 MHz (--) S3V: Using Trio32/64 programmable clock (MCLK 69.801 MHz) (--) S3V: Maximum allowed dot-clock: 170.000 MHz (**) S3V: Mode 1024x768: mode clock = 75.000 (**) S3V: Mode 800x600: mode clock = 60.750 (**) S3V: Mode 640x480: mode clock = 30.000 (**) S3V: Using 16 bpp. Color weight: 565 (--) S3V: Virtual resolution set to 1024x768 (--) S3V: Local bus LAW is 0xF00x (--) S3V: Using a banksize of 4096k, line width of 1024 System: `/usr/X11R6/lib/X11/xkb/xkbcomp -w 1 -R/usr/X11R6/lib/X11/xkb -xkm -m fr -em1 The XKEYBOARD keymap compiler (xkbcomp) reports: -emp -eml Errors from xkbcomp are not fatal to the X server keymap/xfree86 /var/tmp/xfree86.xkm' Any idea ? Pascal Thivent -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
RE: startx problem
But what about the end of the output ? ... System: `/usr/X11R6/lib/X11/xkb/xkbcomp -w 1 -R/usr/X11R6/lib/X11/xkb -xkm -m fr -em1 The XKEYBOARD keymap compiler (xkbcomp) reports: -emp -eml Errors from xkbcomp are not fatal to the X server keymap/xfree86 /var/tmp/xfree86.xkm' ... what does this mean ? -Message d'origine- De: Erik Steffl [mailto:[EMAIL PROTECTED] Date: mercredi 22 novembre 2000 12:16 À: Debian User List (Adresse de messagerie) Objet: Re: startx problem is there any problem? the stuff below looks like normal X run. the X is probably on vt7 generally, when you wantto launch X you run startx (from command line) or xdm (usually from inittab). erik Pascal THIVENT wrote: Hi, when i launch X, i get this message : XFree86 Version 3.3.6 / X Window System (protocol Version 11, revision 0, vendor release 6300) Release Date: January 8 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://www.XFree86.Org/FAQ) Operating System: Linux 2.2.17pre10 i686 [ELF] Configured drivers: S3V: accelerated server for S3 graphics adaptors (Patchlevel 0) s3_ViRGE (using VT number 7) XF86Config: /usr/X11R6/lib/X11/XF86Config (**) stands for supplied, (--) stands for probed/default values (**) XKB: keymap: xfree86(fr) (overrides other XKB settings) (**) Mouse: type: Microsoft, device: /dev/mouse, baudrate: 1200 (**) Mouse: buttons: 3 (**) S3V: Graphics device ID: DSV3325DX (**) S3V: Monitor ID: CM0800 (--) S3V: Mode 800x600 needs hsync freq of 64.02 kHz. Deleted. (--) S3V: Mode 1024x768 needs hsync freq of 62.50 kHz. Deleted. (--) S3V: Mode 1152x864 needs hsync freq of 62.42 kHz. Deleted. (--) S3V: Mode 1280x1024 needs hsync freq of 64.25 kHz. Deleted. (--) S3V: Mode 1024x768 needs hsync freq of 70.24 kHz. Deleted. (--) S3V: Mode 1152x864 needs hsync freq of 70.88 kHz. Deleted. (--) S3V: Mode 1280x1024 needs hsync freq of 74.59 kHz. Deleted. (--) S3V: Mode 1600x1200 needs hsync freq of 75.00 kHz. Deleted. (--) S3V: Mode 1152x864 needs hsync freq of 76.01 kHz. Deleted. (--) S3V: Mode 1280x1024 needs hsync freq of 78.86 kHz. Deleted. (--) S3V: Mode 1024x768 needs hsync freq of 80.21 kHz. Deleted. (--) S3V: Mode 1280x1024 needs hsync freq of 81.13 kHz. Deleted. (--) S3V: Mode 1600x1200 needs hsync freq of 87.50 kHz. Deleted. (--) S3V: Mode 1152x864 needs hsync freq of 89.62 kHz. Deleted. (--) S3V: Mode 1280x1024 needs hsync freq of 91.15 kHz. Deleted. (--) S3V: Mode 1600x1200 needs hsync freq of 93.75 kHz. Deleted. (--) S3V: Mode 1600x1200 needs hsync freq of 105.77 kHz. Deleted. (--) S3V: Mode 1280x1024 needs hsync freq of 107.16 kHz. Deleted. (--) S3V: Mode 1800X1440 needs hsync freq of 96.15 kHz. Deleted. (--) S3V: Mode 1800X1440 needs hsync freq of 104.52 kHz. Deleted. (**) FontPath set to /usr/lib/X11/fonts/misc/:unscaled,/usr/lib/X11/fonts/75dpi/:u nscaled,/usr/l ib/X11/fonts/100dpi/:unscaled,/usr/lib/X11/fonts/Type1/,/usr/l ib/X11/fonts/S peedo/,/usr/lib/X11/fonts/misc/,/usr/lib/X11/fonts/75dpi/,/usr /lib/X11/fonts /100dpi/ (--) S3V: PCI: ViRGE/DX or /GX rev 1, Linear FB @ 0xf000 (--) S3V: chipset: ViRGE/DX rev. 1 (**) S3V: chipset driver: s3_VIRGE (**) S3V: videoram: 4096k (**) S3V: Ramdac type: s3_trio64 (**) S3V: Ramdac speed: 170 MHz (--) S3V: Using Trio32/64 programmable clock (MCLK 69.801 MHz) (--) S3V: Maximum allowed dot-clock: 170.000 MHz (**) S3V: Mode 1024x768: mode clock = 75.000 (**) S3V: Mode 800x600: mode clock = 60.750 (**) S3V: Mode 640x480: mode clock = 30.000 (**) S3V: Using 16 bpp. Color weight: 565 (--) S3V: Virtual resolution set to 1024x768 (--) S3V: Local bus LAW is 0xF00x (--) S3V: Using a banksize of 4096k, line width of 1024 System: `/usr/X11R6/lib/X11/xkb/xkbcomp -w 1 -R/usr/X11R6/lib/X11/xkb -xkm -m fr -em1 The XKEYBOARD keymap compiler (xkbcomp) reports: -emp -eml Errors from xkbcomp are not fatal to the X server keymap/xfree86 /var/tmp/xfree86.xkm' Any idea ? Pascal Thivent -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: startx problem
I think it just means that if there were any errors, they wouldn't be fatal. I actually had an xkbcomp error recently (tried to use a non-existing key map), but lo and behold, it wasn't fatal (just disabled my backspace key). So I think as long as you don't get any actual error message, you can ignore this. j On Wed, Nov 22, 2000 at 01:22:16PM +0100, Pascal THIVENT wrote: But what about the end of the output ? ... System: `/usr/X11R6/lib/X11/xkb/xkbcomp -w 1 -R/usr/X11R6/lib/X11/xkb -xkm -m fr -em1 The XKEYBOARD keymap compiler (xkbcomp) reports: -emp -eml Errors from xkbcomp are not fatal to the X server keymap/xfree86 /var/tmp/xfree86.xkm' ... what does this mean ?
Re: startx problem
i had a similar problem (back when i had X installed) - to get to the windows environment, just press alt+F7 to get to the virtual terminal (it may be ctrl+alt+F7, i'm telnetting on a windows machine right now and can't check - sorry). happy holidays! On Wed, 22 Nov 2000, Erik Steffl wrote: is there any problem? the stuff below looks like normal X run. the X is probably on vt7 generally, when you wantto launch X you run startx (from command line) or xdm (usually from inittab). erik Pascal THIVENT wrote: Hi, when i launch X, i get this message : XFree86 Version 3.3.6 / X Window System (protocol Version 11, revision 0, vendor release 6300) Release Date: January 8 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://www.XFree86.Org/FAQ) Operating System: Linux 2.2.17pre10 i686 [ELF] Configured drivers: S3V: accelerated server for S3 graphics adaptors (Patchlevel 0) s3_ViRGE (using VT number 7) XF86Config: /usr/X11R6/lib/X11/XF86Config (**) stands for supplied, (--) stands for probed/default values (**) XKB: keymap: xfree86(fr) (overrides other XKB settings) (**) Mouse: type: Microsoft, device: /dev/mouse, baudrate: 1200 (**) Mouse: buttons: 3 (**) S3V: Graphics device ID: DSV3325DX (**) S3V: Monitor ID: CM0800 (--) S3V: Mode 800x600 needs hsync freq of 64.02 kHz. Deleted. (--) S3V: Mode 1024x768 needs hsync freq of 62.50 kHz. Deleted. (--) S3V: Mode 1152x864 needs hsync freq of 62.42 kHz. Deleted. (--) S3V: Mode 1280x1024 needs hsync freq of 64.25 kHz. Deleted. (--) S3V: Mode 1024x768 needs hsync freq of 70.24 kHz. Deleted. (--) S3V: Mode 1152x864 needs hsync freq of 70.88 kHz. Deleted. (--) S3V: Mode 1280x1024 needs hsync freq of 74.59 kHz. Deleted. (--) S3V: Mode 1600x1200 needs hsync freq of 75.00 kHz. Deleted. (--) S3V: Mode 1152x864 needs hsync freq of 76.01 kHz. Deleted. (--) S3V: Mode 1280x1024 needs hsync freq of 78.86 kHz. Deleted. (--) S3V: Mode 1024x768 needs hsync freq of 80.21 kHz. Deleted. (--) S3V: Mode 1280x1024 needs hsync freq of 81.13 kHz. Deleted. (--) S3V: Mode 1600x1200 needs hsync freq of 87.50 kHz. Deleted. (--) S3V: Mode 1152x864 needs hsync freq of 89.62 kHz. Deleted. (--) S3V: Mode 1280x1024 needs hsync freq of 91.15 kHz. Deleted. (--) S3V: Mode 1600x1200 needs hsync freq of 93.75 kHz. Deleted. (--) S3V: Mode 1600x1200 needs hsync freq of 105.77 kHz. Deleted. (--) S3V: Mode 1280x1024 needs hsync freq of 107.16 kHz. Deleted. (--) S3V: Mode 1800X1440 needs hsync freq of 96.15 kHz. Deleted. (--) S3V: Mode 1800X1440 needs hsync freq of 104.52 kHz. Deleted. (**) FontPath set to /usr/lib/X11/fonts/misc/:unscaled,/usr/lib/X11/fonts/75dpi/:unscaled,/usr/l ib/X11/fonts/100dpi/:unscaled,/usr/lib/X11/fonts/Type1/,/usr/lib/X11/fonts/S peedo/,/usr/lib/X11/fonts/misc/,/usr/lib/X11/fonts/75dpi/,/usr/lib/X11/fonts /100dpi/ (--) S3V: PCI: ViRGE/DX or /GX rev 1, Linear FB @ 0xf000 (--) S3V: chipset: ViRGE/DX rev. 1 (**) S3V: chipset driver: s3_VIRGE (**) S3V: videoram: 4096k (**) S3V: Ramdac type: s3_trio64 (**) S3V: Ramdac speed: 170 MHz (--) S3V: Using Trio32/64 programmable clock (MCLK 69.801 MHz) (--) S3V: Maximum allowed dot-clock: 170.000 MHz (**) S3V: Mode 1024x768: mode clock = 75.000 (**) S3V: Mode 800x600: mode clock = 60.750 (**) S3V: Mode 640x480: mode clock = 30.000 (**) S3V: Using 16 bpp. Color weight: 565 (--) S3V: Virtual resolution set to 1024x768 (--) S3V: Local bus LAW is 0xF00x (--) S3V: Using a banksize of 4096k, line width of 1024 System: `/usr/X11R6/lib/X11/xkb/xkbcomp -w 1 -R/usr/X11R6/lib/X11/xkb -xkm -m fr -em1 The XKEYBOARD keymap compiler (xkbcomp) reports: -emp -eml Errors from xkbcomp are not fatal to the X server keymap/xfree86 /var/tmp/xfree86.xkm' Any idea ? Pascal Thivent -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
