Re: starting X fails: out of scan range
libre fan wrote:
libre fan wrote:
Last Friday I updated Debian (lot of xorg stuff was updated) and when I
rebooted I got this message on the screen: out of scan range
I reconfigured several times trying to correct errors, and I compared the
original Xfree config file with the present xorg.config. I really don't know
how to put the matter straight.
Something else you may want to try:
1) Shutdown your system for maintenance if possible (otherwise stop X
from running)
2) Save a copy of your /etc/X/xorg.conf file somewhere (other than in
/etc/X)
3) Remove the 'xorg.conf' file in /etc/X
4) run dexconf ('man dexconf' to see what this command does)
HTH
--
Sincerely
Jose Alburquerque
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X fails: out of scan range
libre fan wrote: Last Friday I updated Debian (lot of xorg stuff was updated) and when I rebooted I got this message on the screen: out of scan range I reconfigured several times trying to correct errors, and I compared the original Xfree config file with the present xorg.config. I really don't know how to put the matter straight. I set the default depths at 16 then later at 24. I set the default and only resolution at 1024x768 because this has always worked. Here are snippets from the latest Xorg.log (/var/log/Xorg.0.log): (--) MGA(0): Chipset: mgag200 (**) MGA(0): Depth 24, (--) framebuffer bpp 32 (==) MGA(0): RGB weight 888 (==) MGA(0): Using AGP 1x mode (--) MGA(0): Linear framebuffer at 0xF500 (--) MGA(0): VideoRAM: 8192 kByte (II) MGA(0): Supported VESA Video Modes: ... (II) MGA(0): [EMAIL PROTECTED] (interlaced) (II) MGA(0): [EMAIL PROTECTED] (II) MGA(0): [EMAIL PROTECTED] (II) MGA(0): [EMAIL PROTECTED] (II) MGA(0): [EMAIL PROTECTED] ... (==) MGA(0): Min pixel clock is 17 MHz (--) MGA(0): Max pixel clock is 250 MHz (II) MGA(0): Sony CDP-110GS/EST: Using hsync range of 30.00-70.00 kHz (II) MGA(0): Sony CDP-110GS/EST: Using vrefresh range of 48.00-120.00 Hz (II) MGA(0): Clock range: 17.75 to 250.00 MHz (WW) (1024x768,Sony CDP-110GS/EST) mode clock 94.5MHz exceeds DDC maximum 0MHz (WW) (1024x768,Sony CDP-110GS/EST) mode clock 133.475MHz exceeds DDC maximum 0MHz (II) MGA(0): Not using default mode 1024x768 (hsync out of range) (--) MGA(0): Virtual size is 1024x768 (pitch 1024) (**) MGA(0): *Default mode 1024x768: 94.5 MHz, 68.7 kHz, 85.0 Hz (II) MGA(0): Modeline 1024x768 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync ... BTW I also get font errors, like this: (WW) `fonts.dir' not found (or not valid) in /usr/X11R6/lib/X11/fonts/misc. Entry deleted from font path. (Run 'mkfontdir' on /usr/X11R6/lib/X11/fonts/misc). (WW) `fonts.dir' not found (or not valid) in /usr/X11R6/lib/X11/fonts/100dpi/.Entry deleted from font path. (Run 'mkfontdir' on /usr/X11R6/lib/X11/fonts/100dpi/). (WW) `fonts.dir' not found (or not valid) in /usr/X11R6/lib/X11/fonts/75dpi/. Entry deleted from font path. (Run 'mkfontdir' on /usr/X11R6/lib/X11/fonts/75dpi/). (WW) `fonts.dir' not found (or not valid) in /usr/X11R6/lib/X11/fonts/100dpi. Entry deleted from font path. (Run 'mkfontdir' on /usr/X11R6/lib/X11/fonts/100dpi). ... I no longer get errors in the log file still the message out of scan range is displayed after I type startx. Your help would be much appreciated! cheers, libre fan -- View this message in context: http://www.nabble.com/starting-X-fails%3A-out-of-scan-range-tf2330274.html#a6633861 Sent from the Debian User mailing list archive at Nabble.com. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X fails: out of scan range
libre fan wrote:
Hello,
I have a Debian Etch+Sid and Xubuntu Dapper dual-boot.
Last Friday I updated Debian (lot of xorg stuff was updated) and when I
rebooted I got this message on the screen: out of scan range
Though X is started (I typed startx on a terminal) Wdm (my display
manager) doesn't load.
Is the message to do with the monitor config? Everyting worked fine before
hand -- I have had Debian-based distros for about three years now without
any hardware problems.
What can I do? Can you help me? perhaps I could downgrade: comment the sid
lines oin my sources.list, pat-get get update, uninstall x.org, reinstall it
from the Etch repositories?
There must be a simpler way. Run xorg config?
Many thanks in advance!
Sounds to me like the error your getting is because your monitor
settings are not correct in your /etc/X/xorg.conf file. You probably
replaced your config when you updated. Reconfiguring the xserver-xorg
package ('sudo dpkg-reconfigure xserver-xorg') might fix your problem.
--
Sincerely
Jose Alburquerque
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X fails: out of scan range
Jos? Alburquerque-3 wrote:
libre fan wrote:
Last Friday I updated Debian (lot of xorg stuff was updated) and when I
rebooted I got this message on the screen: out of scan range
Sounds to me like the error your getting is because your monitor
settings are not correct in your /etc/X/xorg.conf file. You probably
replaced your config when you updated. Reconfiguring the xserver-xorg
package ('sudo dpkg-reconfigure xserver-xorg') might fix your problem.
I did reconfigure as you suggest. I get two error messages: no usable
screen and no frame buffer found. I see there's an option in the
dpkg-reconfigure xserver-xorg process to do without the frame buffer. i'll
check again if I disabled this option.
I compared the xorg.conf files in Debian and in Xubuntu, and corrected the
reference of the screen.
Cheers
--
View this message in context:
http://www.nabble.com/starting-X-fails%3A-out-of-scan-range-tf2330274.html#a6499854
Sent from the Debian User mailing list archive at Nabble.com.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X makes the screen go white (newb - new install)
Could have found what's causing the issue. I have no idea what he's talking about though... Looking in to it now, but any help is appreciated. Jeroen --- start quote --- Framebuffer/X notes New - I managed to replace the atyfb code of 2.4.27 with the one of 2.4.16. This means there are dozens of new drivers available for for users which need the framebuffer-patch. Due to its completely different design, 2.6.8.x kernels still bring along difficulties in respect of forward porting. Anyway, the resulting 2.4.27 kernel is available as a deb-package. Using kernel 2.4.16 with or without full-width console patch works fine with X. Mind that the following modeline is required: ModeLine 1024x480 65.00 1024 1032 1176 1344 480 488 494 563 -hsync - vsync The atyfb of 2.4.18 and later seems to have changed a lot. The full- width console patch doesn't apply cleanly anymore - not even this one. If framebuffer support is compiled in, Xfree86 4.3 whites the screen slowly which doesn't look healthy. Not even the modeline entry helps. Xserver-mach64 works insufficiently (corrupts the screen and mouse-input is translated horribly). I'm trying to insert the 2.4.16 atyfb code into higher kernels (probably 2.6.8). Results will be published here upon success. --- end quote --- from http://gefechtsdienst.de/uman/c1ve-general.html On 06 Sep 2005, at 00:54, jeroen wrote: Sorry if this came in double, the resend i did might have tricked your mail rules (it did trick mine) Jeroen On 05 Sep 2005, at 22:19, Oliver Lupton wrote: I'm a newbie too, but try running 'gdm' (GNOME Display Manager, I think) instead of 'startx' and see how that works. #gdm returns a command not found On 05 Sep 2005, at 22:25, Kent West wrote: jeroen wrote: I used apt to get me the files i needed during the installation (i did have to do an 'ifup -a' to get the network up - and still have to after every reboot - but that's slightly OT here). Take a look at /etc/network/interfaces (also man interfaces for examples). Once configured, a simple /etc/init.d/networking restart (or reboot, which will run this script during bootup) should get your network up. It's getting late now, and my primary concern is getting something of a GUI, ifup isn't that hard to type ;). But many thanks for pointing me to the solution. Greatly appreciated! Some pictures i took during this happening can be found here: http://www.yuru.be/debian/startx_1.jpg (going from 1 to 6) These images look like your video settings are not suitable for your hardware; what happens if you remove that ModeLine you added? When i comment out the modeline (and un-comment out the HorizSync and VertRefresh) i get the same white screen. What other minor changes did you make? My complete config can now be found @ http://www.yuru.be/debian/XF86Config-4 other changes i made are: /OptionXkbLayoutukto -OptionXkbLayoutgb Probably nothing serious or X killing, just changed it to the working config i found on the cam.ac.uk site /IdentifierConfigured Mouse /OptionEmulate3Buttontrue /OptionZAxisMapping4 5 to -IdentifierConfigured Mouse -OptionButtons5 -OptionZAxisMapping5 4 Same here, just copied it, hoping it would work like a charm. Other changes are: Adding the modeline and commenting out the HorizSync and VertRefresh. The last thing i changed where all resolutions in the Display Subsections of the Screen Section (was 320x240 640x480) Ctrl-Alt-Backspace should kill it from within X. Hey cool, thanks! I was trying to do that with Ctrl-Alt-Delete... With my limited knowledge i though i could have forgotten to add a window manager I don't think so; this looks like a video sync -type issue. You can double-check this possibility by installing another wm (aptitude install icewm, etc), or make sure you've got xterm installed (aptitude install xterm) and then put icewm or xterm in the file ~/.xinitrc (you'll probably have to create the file), and then run startx. If you put icewm in ~/.initrc, Icewm should start up; if you put xterm, you should get an xterm (with no window controls; you can type exit to shut down X in such a case). Tried this, with both suggested wms (and both .xinitrc and .initrc - was this a typo or are they indeed different?), they produce the same white screen. You where right that i had to create both files. I renamed them so there never was both a .xinitrc and and .initrc in my ~/. Remember that USB disk you mentioned? I bet it works with USB fobs as well. Doh! Thanks for that. It's the only floppy drive i have so i have to plug it in and out, it works, that's most important. I do have a problem with copying my XFree86.0.log, It gives a -36 error when i try to copy it over to my mac. I'll look into that
Re: starting X makes the screen go white (newb - new install)
This is starting to look like a blog ;) I installed the kernel found on the previously mentioned page (http:// gefechtsdienst.de/uman/c1ve-general.html). It doesn't look really nice. Full screen console is built in but is shifted (not placed correctly, with white band down the screen). Startx (with fvwm) works fine. That means i get to see the graphical login screen now... the screen itself doesn't really look nice, with stripes all over the place. As mentioned in the above page the problems with the white screen allegedly happen with Xfree86 4.3. I'm now looking into removing the version i have running now and replace it with a previous version. If i get this to work with the standard default kernel i will be a happy man. kernel compiling is a bit over the top for me right now i think. Maybe next week ;D Cheers, Jeroen On 06 Sep 2005, at 20:35, jeroen wrote: Could have found what's causing the issue. I have no idea what he's talking about though... Looking in to it now, but any help is appreciated. Jeroen --- start quote --- Framebuffer/X notes New - I managed to replace the atyfb code of 2.4.27 with the one of 2.4.16. This means there are dozens of new drivers available for for users which need the framebuffer-patch. Due to its completely different design, 2.6.8.x kernels still bring along difficulties in respect of forward porting. Anyway, the resulting 2.4.27 kernel is available as a deb-package. Using kernel 2.4.16 with or without full-width console patch works fine with X. Mind that the following modeline is required: ModeLine 1024x480 65.00 1024 1032 1176 1344 480 488 494 563 - hsync -vsync The atyfb of 2.4.18 and later seems to have changed a lot. The full- width console patch doesn't apply cleanly anymore - not even this one. If framebuffer support is compiled in, Xfree86 4.3 whites the screen slowly which doesn't look healthy. Not even the modeline entry helps. Xserver-mach64 works insufficiently (corrupts the screen and mouse-input is translated horribly). I'm trying to insert the 2.4.16 atyfb code into higher kernels (probably 2.6.8). Results will be published here upon success. --- end quote --- from http://gefechtsdienst.de/uman/c1ve-general.html On 06 Sep 2005, at 00:54, jeroen wrote: Sorry if this came in double, the resend i did might have tricked your mail rules (it did trick mine) Jeroen On 05 Sep 2005, at 22:19, Oliver Lupton wrote: I'm a newbie too, but try running 'gdm' (GNOME Display Manager, I think) instead of 'startx' and see how that works. #gdm returns a command not found On 05 Sep 2005, at 22:25, Kent West wrote: jeroen wrote: I used apt to get me the files i needed during the installation (i did have to do an 'ifup -a' to get the network up - and still have to after every reboot - but that's slightly OT here). Take a look at /etc/network/interfaces (also man interfaces for examples). Once configured, a simple /etc/init.d/networking restart (or reboot, which will run this script during bootup) should get your network up. It's getting late now, and my primary concern is getting something of a GUI, ifup isn't that hard to type ;). But many thanks for pointing me to the solution. Greatly appreciated! Some pictures i took during this happening can be found here: http://www.yuru.be/debian/startx_1.jpg (going from 1 to 6) These images look like your video settings are not suitable for your hardware; what happens if you remove that ModeLine you added? When i comment out the modeline (and un-comment out the HorizSync and VertRefresh) i get the same white screen. What other minor changes did you make? My complete config can now be found @ http://www.yuru.be/debian/XF86Config-4 other changes i made are: /OptionXkbLayoutukto -OptionXkbLayoutgb Probably nothing serious or X killing, just changed it to the working config i found on the cam.ac.uk site /IdentifierConfigured Mouse /OptionEmulate3Buttontrue /OptionZAxisMapping4 5 to -IdentifierConfigured Mouse -OptionButtons5 -OptionZAxisMapping5 4 Same here, just copied it, hoping it would work like a charm. Other changes are: Adding the modeline and commenting out the HorizSync and VertRefresh. The last thing i changed where all resolutions in the Display Subsections of the Screen Section (was 320x240 640x480) Ctrl-Alt-Backspace should kill it from within X. Hey cool, thanks! I was trying to do that with Ctrl-Alt-Delete... With my limited knowledge i though i could have forgotten to add a window manager I don't think so; this looks like a video sync -type issue. You can double-check this possibility by installing another wm (aptitude install icewm, etc), or make sure you've got xterm installed (aptitude install xterm) and then
Re: starting X makes the screen go white (newb - new install)
continuing blog i installed the x-server from woody, x starts up fine now, jeej! i guess this issue is closed, unless this was a bad idea. Thx for reading my ramblings, Jeroen On 06 Sep 2005, at 21:06, jeroen wrote: This is starting to look like a blog ;) I installed the kernel found on the previously mentioned page (http://gefechtsdienst.de/uman/c1ve-general.html). It doesn't look really nice. Full screen console is built in but is shifted (not placed correctly, with white band down the screen). Startx (with fvwm) works fine. That means i get to see the graphical login screen now... the screen itself doesn't really look nice, with stripes all over the place. As mentioned in the above page the problems with the white screen allegedly happen with Xfree86 4.3. I'm now looking into removing the version i have running now and replace it with a previous version. If i get this to work with the standard default kernel i will be a happy man. kernel compiling is a bit over the top for me right now i think. Maybe next week ;D Cheers, Jeroen On 06 Sep 2005, at 20:35, jeroen wrote: Could have found what's causing the issue. I have no idea what he's talking about though... Looking in to it now, but any help is appreciated. Jeroen --- start quote --- Framebuffer/X notes New - I managed to replace the atyfb code of 2.4.27 with the one of 2.4.16. This means there are dozens of new drivers available for for users which need the framebuffer-patch. Due to its completely different design, 2.6.8.x kernels still bring along difficulties in respect of forward porting. Anyway, the resulting 2.4.27 kernel is available as a deb-package. Using kernel 2.4.16 with or without full-width console patch works fine with X. Mind that the following modeline is required: ModeLine 1024x480 65.00 1024 1032 1176 1344 480 488 494 563 - hsync -vsync The atyfb of 2.4.18 and later seems to have changed a lot. The full-width console patch doesn't apply cleanly anymore - not even this one. If framebuffer support is compiled in, Xfree86 4.3 whites the screen slowly which doesn't look healthy. Not even the modeline entry helps. Xserver-mach64 works insufficiently (corrupts the screen and mouse-input is translated horribly). I'm trying to insert the 2.4.16 atyfb code into higher kernels (probably 2.6.8). Results will be published here upon success. --- end quote --- from http://gefechtsdienst.de/uman/c1ve-general.html On 06 Sep 2005, at 00:54, jeroen wrote: Sorry if this came in double, the resend i did might have tricked your mail rules (it did trick mine) Jeroen On 05 Sep 2005, at 22:19, Oliver Lupton wrote: I'm a newbie too, but try running 'gdm' (GNOME Display Manager, I think) instead of 'startx' and see how that works. #gdm returns a command not found On 05 Sep 2005, at 22:25, Kent West wrote: jeroen wrote: I used apt to get me the files i needed during the installation (i did have to do an 'ifup -a' to get the network up - and still have to after every reboot - but that's slightly OT here). Take a look at /etc/network/interfaces (also man interfaces for examples). Once configured, a simple /etc/init.d/networking restart (or reboot, which will run this script during bootup) should get your network up. It's getting late now, and my primary concern is getting something of a GUI, ifup isn't that hard to type ;). But many thanks for pointing me to the solution. Greatly appreciated! Some pictures i took during this happening can be found here: http://www.yuru.be/debian/startx_1.jpg (going from 1 to 6) These images look like your video settings are not suitable for your hardware; what happens if you remove that ModeLine you added? When i comment out the modeline (and un-comment out the HorizSync and VertRefresh) i get the same white screen. What other minor changes did you make? My complete config can now be found @ http://www.yuru.be/debian/XF86Config-4 other changes i made are: /OptionXkbLayoutukto -OptionXkbLayoutgb Probably nothing serious or X killing, just changed it to the working config i found on the cam.ac.uk site /IdentifierConfigured Mouse /OptionEmulate3Buttontrue /OptionZAxisMapping4 5 to -IdentifierConfigured Mouse -OptionButtons5 -OptionZAxisMapping5 4 Same here, just copied it, hoping it would work like a charm. Other changes are: Adding the modeline and commenting out the HorizSync and VertRefresh. The last thing i changed where all resolutions in the Display Subsections of the Screen Section (was 320x240 640x480) Ctrl-Alt-Backspace should kill it from within X. Hey cool, thanks! I was trying to do that with Ctrl-Alt-Delete... With my limited knowledge i though i could have forgotten to add a window
Re: starting X makes the screen go white (newb - new install)
jeroen wrote: Hello all, --intro I'm trying (finally) to get debian to work on my Vaio PCG-C1VE. Using the latest version of the installer (floppy images) i succeeded in installing 3.1 on the little b*st*rd. Previous versions didn't support USB disks (at least not on a noob level) so thx debian! I used apt to get me the files i needed during the installation (i did have to do an 'ifup -a' to get the network up - and still have to after every reboot - but that's slightly OT here). Once i got the machine to boot from its own HD i though it would be nice to have GUI to learn my way around debian (and linux in general). --/intro fresh install i did: #apt-get install x-window-system #apt-get install gnome immediately after this i used vi to change my /etc/X11/XF86Config-4. The most important change i did was adding this modeline: ModeLine 1024x480 65.00 1024 1032 1176 1344 480 488 494 563 -hsync - vsync together with some other minor changes i found on http://www- jcsu.jesus.cam.ac.uk/~mma29/c1/ #startx works fine (this means it starts up ;-/ ), the only thing i get to see is a black screen which bleeds to a very white blue (starting at the edges). Some vertical and horizontal lines can be seen as well, all at the edge of some very white colours. Some pictures i took during this happening can be found here: http://www.yuru.be/debian/startx_1.jpg (going from 1 to 6) The only way to get me out of this white hell is by tapping Ctrl-Alt- F1, followed by Ctrl-C to stop the X server. With my limited knowledge i though i could have forgotten to add a window manager (didn't i read somewhere that this is not included in gnome??) so i did #apt-get install fvwm nothing changed. So here i am writing this mail, hoping somebody here can put me on the right track. Thx for taking the time to read this, Jeroen I would include my XFree86.0.log but i have no idea how to get it of the laptop (skipped mail config in debian installer...) I'm a newbie too, but try running 'gdm' (GNOME Display Manager, I think) instead of 'startx' and see how that works. I think that apt-get install gnome should have installed metacity, GNOME's window manager. Good luck. Oliver -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X makes the screen go white (newb - new install)
jeroen wrote: I used apt to get me the files i needed during the installation (i did have to do an 'ifup -a' to get the network up - and still have to after every reboot - but that's slightly OT here). Take a look at /etc/network/interfaces (also man interfaces for examples). Once configured, a simple /etc/init.d/networking restart (or reboot, which will run this script during bootup) should get your network up. Once i got the machine to boot from its own HD i though it would be nice to have GUI to learn my way around debian (and linux in general). --/intro fresh install i did: #apt-get install x-window-system #apt-get install gnome immediately after this i used vi to change my /etc/X11/XF86Config-4. The most important change i did was adding this modeline: ModeLine 1024x480 65.00 1024 1032 1176 1344 480 488 494 563 -hsync - vsync together with some other minor changes i found on http://www- jcsu.jesus.cam.ac.uk/~mma29/c1/ #startx works fine (this means it starts up ;-/ ), the only thing i get to see is a black screen which bleeds to a very white blue (starting at the edges). Some vertical and horizontal lines can be seen as well, all at the edge of some very white colours. Some pictures i took during this happening can be found here: http://www.yuru.be/debian/startx_1.jpg (going from 1 to 6) These images look like your video settings are not suitable for your hardware; what happens if you remove that ModeLine you added? What other minor changes did you make? The only way to get me out of this white hell is by tapping Ctrl-Alt- F1, followed by Ctrl-C to stop the X server. Ctrl-Alt-Backspace should kill it from within X. With my limited knowledge i though i could have forgotten to add a window manager I don't think so; this looks like a video sync -type issue. (didn't i read somewhere that this is not included in gnome??) so i did #apt-get install fvwm nothing changed. So here i am writing this mail, hoping somebody here can put me on the right track. Thx for taking the time to read this, Jeroen I would include my XFree86.0.log but i have no idea how to get it of the laptop (skipped mail config in debian installer...) Remember that USB disk you mentioned? I bet it works with USB fobs as well. -- Kent West Technology Support /A/bilene /C/hristian /U/niversity -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X makes the screen go white (newb - new install)
Kent West wrote: jeroen wrote: With my limited knowledge i though i could have forgotten to add a window manager I don't think so; this looks like a video sync -type issue. You can double-check this possibility by installing another wm (aptitude install icewm, etc), or make sure you've got xterm installed (aptitude install xterm) and then put icewm or xterm in the file ~/.xinitrc (you'll probably have to create the file), and then run startx. If you put icewm in ~/.initrc, Icewm should start up; if you put xterm, you should get an xterm (with no window controls; you can type exit to shut down X in such a case). -- Kent West Technology Support /A/bilene /C/hristian /U/niversity -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X makes the screen go white (newb - new install)
On 05 Sep 2005, at 22:19, Oliver Lupton wrote: I'm a newbie too, but try running 'gdm' (GNOME Display Manager, I think) instead of 'startx' and see how that works. #gdm returns a command not found On 05 Sep 2005, at 22:25, Kent West wrote: jeroen wrote: I used apt to get me the files i needed during the installation (i did have to do an 'ifup -a' to get the network up - and still have to after every reboot - but that's slightly OT here). Take a look at /etc/network/interfaces (also man interfaces for examples). Once configured, a simple /etc/init.d/networking restart (or reboot, which will run this script during bootup) should get your network up. It's getting late now, and my primary concern is getting something of a GUI, ifup isn't that hard to type ;). But many thanks for pointing me to the solution. Greatly appreciated! Some pictures i took during this happening can be found here: http://www.yuru.be/debian/startx_1.jpg (going from 1 to 6) These images look like your video settings are not suitable for your hardware; what happens if you remove that ModeLine you added? When i comment out the modeline (and un-comment out the HorizSync and VertRefresh) i get the same white screen. What other minor changes did you make? My complete config can now be found @ http://www.yuru.be/debian/XF86Config-4 other changes i made are: /OptionXkbLayoutukto -OptionXkbLayoutgb Probably nothing serious or X killing, just changed it to the working config i found on the cam.ac.uk site /IdentifierConfigured Mouse /OptionEmulate3Buttontrue /OptionZAxisMapping4 5 to -IdentifierConfigured Mouse -OptionButtons5 -OptionZAxisMapping5 4 Same here, just copied it, hoping it would work like a charm. Other changes are: Adding the modeline and commenting out the HorizSync and VertRefresh. The last thing i changed where all resolutions in the Display Subsections of the Screen Section (was 320x240 640x480) Ctrl-Alt-Backspace should kill it from within X. Hey cool, thanks! I was trying to do that with Ctrl-Alt-Delete... With my limited knowledge i though i could have forgotten to add a window manager I don't think so; this looks like a video sync -type issue. You can double-check this possibility by installing another wm (aptitude install icewm, etc), or make sure you've got xterm installed (aptitude install xterm) and then put icewm or xterm in the file ~/.xinitrc (you'll probably have to create the file), and then run startx. If you put icewm in ~/.initrc, Icewm should start up; if you put xterm, you should get an xterm (with no window controls; you can type exit to shut down X in such a case). Tried this, with both suggested wms (and both .xinitrc and .initrc - was this a typo or are they indeed different?), they produce the same white screen. You where right that i had to create both files. I renamed them so there never was both a .xinitrc and and .initrc in my ~/. Remember that USB disk you mentioned? I bet it works with USB fobs as well. Doh! Thanks for that. It's the only floppy drive i have so i have to plug it in and out, it works, that's most important. I do have a problem with copying my XFree86.0.log, It gives a -36 error when i try to copy it over to my mac. I'll look into that tomorrow (when i follow your tips on the interfaces). Now it's time for me to go to bed, i'm on CET and have to work tomorrow. Thank you for your time, Jeroen jeroen wrote: Hello all, --intro I'm trying (finally) to get debian to work on my Vaio PCG-C1VE. Using the latest version of the installer (floppy images) i succeeded in installing 3.1 on the little b*st*rd. Previous versions didn't support USB disks (at least not on a noob level) so thx debian! I used apt to get me the files i needed during the installation (i did have to do an 'ifup -a' to get the network up - and still have to after every reboot - but that's slightly OT here). Once i got the machine to boot from its own HD i though it would be nice to have GUI to learn my way around debian (and linux in general). --/intro fresh install i did: #apt-get install x-window-system #apt-get install gnome immediately after this i used vi to change my /etc/X11/XF86Config-4. The most important change i did was adding this modeline: ModeLine 1024x480 65.00 1024 1032 1176 1344 480 488 494 563 - hsync - vsync together with some other minor changes i found on http://www- jcsu.jesus.cam.ac.uk/~mma29/c1/ #startx works fine (this means it starts up ;-/ ), the only thing i get to see is a black screen which bleeds to a very white blue (starting at the edges). Some vertical and horizontal lines can be seen as well, all at the edge of some very white colours. Some pictures i took during this happening can be found here: http://www.yuru.be/debian/startx_1.jpg
Re: starting X makes the screen go white (newb - new install)
Sorry if this came in double, the resend i did might have tricked your mail rules (it did trick mine) Jeroen On 05 Sep 2005, at 22:19, Oliver Lupton wrote: I'm a newbie too, but try running 'gdm' (GNOME Display Manager, I think) instead of 'startx' and see how that works. #gdm returns a command not found On 05 Sep 2005, at 22:25, Kent West wrote: jeroen wrote: I used apt to get me the files i needed during the installation (i did have to do an 'ifup -a' to get the network up - and still have to after every reboot - but that's slightly OT here). Take a look at /etc/network/interfaces (also man interfaces for examples). Once configured, a simple /etc/init.d/networking restart (or reboot, which will run this script during bootup) should get your network up. It's getting late now, and my primary concern is getting something of a GUI, ifup isn't that hard to type ;). But many thanks for pointing me to the solution. Greatly appreciated! Some pictures i took during this happening can be found here: http://www.yuru.be/debian/startx_1.jpg (going from 1 to 6) These images look like your video settings are not suitable for your hardware; what happens if you remove that ModeLine you added? When i comment out the modeline (and un-comment out the HorizSync and VertRefresh) i get the same white screen. What other minor changes did you make? My complete config can now be found @ http://www.yuru.be/debian/XF86Config-4 other changes i made are: /OptionXkbLayoutukto -OptionXkbLayoutgb Probably nothing serious or X killing, just changed it to the working config i found on the cam.ac.uk site /IdentifierConfigured Mouse /OptionEmulate3Buttontrue /OptionZAxisMapping4 5 to -IdentifierConfigured Mouse -OptionButtons5 -OptionZAxisMapping5 4 Same here, just copied it, hoping it would work like a charm. Other changes are: Adding the modeline and commenting out the HorizSync and VertRefresh. The last thing i changed where all resolutions in the Display Subsections of the Screen Section (was 320x240 640x480) Ctrl-Alt-Backspace should kill it from within X. Hey cool, thanks! I was trying to do that with Ctrl-Alt-Delete... With my limited knowledge i though i could have forgotten to add a window manager I don't think so; this looks like a video sync -type issue. You can double-check this possibility by installing another wm (aptitude install icewm, etc), or make sure you've got xterm installed (aptitude install xterm) and then put icewm or xterm in the file ~/.xinitrc (you'll probably have to create the file), and then run startx. If you put icewm in ~/.initrc, Icewm should start up; if you put xterm, you should get an xterm (with no window controls; you can type exit to shut down X in such a case). Tried this, with both suggested wms (and both .xinitrc and .initrc - was this a typo or are they indeed different?), they produce the same white screen. You where right that i had to create both files. I renamed them so there never was both a .xinitrc and and .initrc in my ~/. Remember that USB disk you mentioned? I bet it works with USB fobs as well. Doh! Thanks for that. It's the only floppy drive i have so i have to plug it in and out, it works, that's most important. I do have a problem with copying my XFree86.0.log, It gives a -36 error when i try to copy it over to my mac. I'll look into that tomorrow (when i follow your tips on the interfaces). Now it's time for me to go to bed, i'm on CET and have to work tomorrow. Thank you for your time, Jeroen jeroen wrote: Hello all, --intro I'm trying (finally) to get debian to work on my Vaio PCG-C1VE. Using the latest version of the installer (floppy images) i succeeded in installing 3.1 on the little b*st*rd. Previous versions didn't support USB disks (at least not on a noob level) so thx debian! I used apt to get me the files i needed during the installation (i did have to do an 'ifup -a' to get the network up - and still have to after every reboot - but that's slightly OT here). Once i got the machine to boot from its own HD i though it would be nice to have GUI to learn my way around debian (and linux in general). --/intro fresh install i did: #apt-get install x-window-system #apt-get install gnome immediately after this i used vi to change my /etc/X11/XF86Config-4. The most important change i did was adding this modeline: ModeLine 1024x480 65.00 1024 1032 1176 1344 480 488 494 563 - hsync - vsync together with some other minor changes i found on http://www- jcsu.jesus.cam.ac.uk/~mma29/c1/ #startx works fine (this means it starts up ;-/ ), the only thing i get to see is a black screen which bleeds to a very white blue (starting at the edges). Some vertical and horizontal lines can be seen as well, all at the edge
Re: starting x
Hello cfk ([EMAIL PROTECTED]) wrote: Thank you very much for the tip. I did do a 'apt-get install x-window-system', and a number of good things happened. I can now do a startx and get twm. I can also right-click and get a tclsh8.4. Thats the good news. Unfortunately, being unfamiliar with apt-get yet, I dont know how to get say kde or gnome up. I am currently trying: apt-get install kde kdevelop kdelibs kdebase after a search of archives and it seems to be working. After that, I wonder what the incantation is to start kde and perhaps more importantly, where I can go to figure out a few steps after that, other then googling. kde should be started by default and be preferred over twm if you run startx. Anyway I suggest you install the KDE login manager kdm, which lets you select which WM/DE you want to log into. There are also other ways, like creating your own ~/.xsession and adding startkde (make sure that allow-user-xsession is in your /etc/X11/Xsession.options), or telling startx which command to run. best regards Andreas Janssen -- Andreas Janssen [EMAIL PROTECTED] PGP-Key-ID: 0xDC801674 ICQ #17079270 Registered Linux User #267976 http://www.andreas-janssen.de/debian-tipps-sarge.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting x
On Sun, 19 Dec 2004 04:00:12 +0100, cfk wrote: after a search of archives and it seems to be working. After that, I wonder what the incantation is to start kde and perhaps more importantly, where I can go to figure out a few steps after that, other then googling. tasksel helps a lot with this. You're probably still missing a display manager from your Red Hat experience. Since you're into KDE, I suggest kdm. Though, being a GNOME geek, I also have to point out that GDM is much better ;-) -- Best Regards, | This signature is currently under construction. Sebastian | Please check back later! | | mailbox in From silently drops any mail 20k -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting x
On Sat, Dec 18, 2004 at 06:59:01PM -0800, cfk wrote: On Saturday 18 December 2004 18:14, Sam Watkins wrote: Dear Sam: Thank you very much for the tip. I did do a 'apt-get install x-window-system', and a number of good things happened. I can now do a startx and get twm. I can also right-click and get a tclsh8.4. Thats the good news. Unfortunately, being unfamiliar with apt-get yet, I dont know how to get say kde or gnome up. I am currently trying: apt-get install kde kdevelop kdelibs kdebase after a search of archives and it seems to be working. After that, I wonder what the incantation is to start kde and perhaps more importantly, where I can go to figure out a few steps after that, other then googling. Charles the following sequence yields: [EMAIL PROTECTED]:~$ ls /usr/bin | grep kde . kdebugdialog kde-config . startkde wkdemenu.pl It seems to be startkde, so startx `which startkde` should get you there -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting x
On Sun, Dec 19, 2004 at 12:18:14PM +0100, Sebastian Kapfer wrote: Since you're into KDE, I suggest kdm. Though, being a GNOME geek, I also have to point out that GDM is much better ;-) maybe we need an uber-display manager that lets the user choose what display manager they want to use before entering the login ;) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting x
On Saturday 18 December 2004 5:44 pm, cfk wrote: Gentlemen: Its my turn to be a newbie to Debian, although I have used Red Hat for a few years. Please bear with me and suggest how I may get my newly installed Sarge to start X. Searching through the archives would have told you you need to install X before you can run it a lot faster than asking the same thing again. -- Paul Johnson [EMAIL PROTECTED] http://ursine.dyndns.org/~baloo/ pgpxzewU9tnR6.pgp Description: PGP signature
Re: starting x
cfk wrote: Gentlemen: Its my turn to be a newbie to Debian, although I have used Red Hat for a few years. Please bear with me and suggest how I may get my newly installed Sarge to start X. I try the incantation startx from either a user or root command prompt and get command not found. Charles Perhaps `apt-get install xserver-xfree86' is needed smime.p7s Description: S/MIME Cryptographic Signature
Re: starting x
On Saturday 18 December 2004 17:42, Robert Vangel wrote: cfk wrote: Gentlemen: Its my turn to be a newbie to Debian, although I have used Red Hat for a few years. Please bear with me and suggest how I may get my newly installed Sarge to start X. I try the incantation startx from either a user or root command prompt and get command not found. Charles Perhaps `apt-get install xserver-xfree86' is needed Dear Robert: Thank you for your kind reply. I was in the midst of reading apt-get's commands and options as I come up to speed on Debian. I did try 'apt-get install xserver-xfree86' and apt-get finishes very quickly saying: Reading Package Lists... Done Building Dependency Tree ... Done xserver-xfree86 is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded Then I invoke startx from the root prompt and get -bash: startx: command not found So, I did 'echo $PATH' and found /usr/bin/X11 was in the path, went there and saw there was no 'startx', but there was an 'X', which when run, gives me a modest blank X screen. Unfortunately, no menu or any right click mouse option such as 'open terminal'. I can go 'Alt-Ctrl-F1', F2 or F3 where F1 shows some error messages, F2 gets me back to the big blank X window and F3 gives me a new logon prompt with an inoperable keyboard. At this point I am pressing the reset switch and starting over and hoping for a bit more advice. Charles -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting x
startx is not part of the X server, it is in the package x-base-clients. You should: apt-get install x-window-system-core or probably: apt-get install x-window-system you can look at what each of these meta packages depends on with: apt-cache show x-window-system-core you can see reverse dependencies with apt-cache rdepends xterm you can find out what package contains a certain file with apt-file: apt-get install apt-file apt-file search startx apt-cache rdepends x-base-clients etc. good luck! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting x
Sam Watkins wrote: startx is not part of the X server, it is in the package x-base-clients. You should: apt-get install x-window-system-core or probably: apt-get install x-window-system you can look at what each of these meta packages depends on with: apt-cache show x-window-system-core you can see reverse dependencies with apt-cache rdepends xterm you can find out what package contains a certain file with apt-file: apt-get install apt-file apt-file search startx apt-cache rdepends x-base-clients etc. good luck! x-window-system is the one I was thinking of, sorry! startx is actually part of xbase-clients, which installing x-window-system would end up installing. smime.p7s Description: S/MIME Cryptographic Signature
Re: starting x
On Saturday 18 December 2004 18:14, Sam Watkins wrote: startx is not part of the X server, it is in the package x-base-clients. You should: apt-get install x-window-system-core or probably: apt-get install x-window-system you can look at what each of these meta packages depends on with: apt-cache show x-window-system-core you can see reverse dependencies with apt-cache rdepends xterm you can find out what package contains a certain file with apt-file: apt-get install apt-file apt-file search startx apt-cache rdepends x-base-clients etc. good luck! Dear Sam: Thank you very much for the tip. I did do a 'apt-get install x-window-system', and a number of good things happened. I can now do a startx and get twm. I can also right-click and get a tclsh8.4. Thats the good news. Unfortunately, being unfamiliar with apt-get yet, I dont know how to get say kde or gnome up. I am currently trying: apt-get install kde kdevelop kdelibs kdebase after a search of archives and it seems to be working. After that, I wonder what the incantation is to start kde and perhaps more importantly, where I can go to figure out a few steps after that, other then googling. Charles -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X hangs on network timeout (hosts file ignored)
On Wed, Jul 14, 2004 at 12:08:39AM +0100, Steven Satelle wrote: On Tue, 13 Jul 2004 20:28:56 +0300, Micha Feigin wrote: Same behavior (I am using wdm and no xdmcp and the no listen on tcp switch). It seems like /usr/X11R6/bin/X is whats causing the trouble, running tcpdump when X startx shows the name lookup BTW: you know, I think we're barking up the wrong tree, in fact I dont even think we are in the woods at all ;-) It might well be a bug. but a bug in what? Try without any x sessions running run 'X' as root and see how long does it take to start, that way you can see if it is xfree or (I assume your using it) gnome. Running just X also hangs in the same way, so its X that's giving the problems. I am not running gnome btw, I'm running FVWM (gnome is too slow,heavy and not configurable enough). Also running wdm gives the same problem and its not starting .xsession or gnome-session so thats not the problem. Assuming it starts quickly, next you want to type: $ export DISPLAY=localhost:0.0 $ gnome-session (or enter the name of your wm's main app) If what I think the problem is is right this should be slow to launch, so exit it (not X just the wm) and this time on another console run 'netstat -c' This will show all network connections and refresh them every few seconds. then relaunch your wm and see does any new datagrams or streams open up in netstat, esp ones that sit in a state of 'SYN_SENT' You are going to get a few going no further than /tmp/.orbit-root, I'm fairly sure they will be streams, they are what gives gnome its network transparency, even local only connections open up sockets. Thats what I think the problem is, gnome is trying to open up a network socket to somewhere. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] +++ This Mail Was Scanned By Mail-seCure System at the Tel-Aviv University CC. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X hangs on network timeout (hosts file ignored)
On Tue, Jul 13, 2004 at 01:49:29AM +0100, Steven Satelle wrote: On Mon, 12 Jul 2004 17:58:40 +0300, Micha Feigin wrote: BTW I got the following reply after I tried reporting a bug on netbase on this: [...] this is how it's supposed to work. host(1) is an interface to the resolver library, which does not use /etc/hosts by design. The problem is that it seems that a few other things seem to be ignoring the /etc/hosts file also. what package are you getting host from, I dont have it on my system. whats /usr/bin/host in your /etc/resolv.conf, mine has search personal.ie nameserver 192.168.1.1 domain luna.local nameserver 192.168.0.1 I think you should have nameserver 127.0.0.1 in there before any remote binds, I dont, but then, I dont have a problem ;-) I think If you have 127.0.0.1 in there as the first nameserver it will check the local one first (/etc/hosts) Doesn't work. apart from that what happens if you run startx without gdm running? Same behavior (I am using wdm and no xdmcp and the no listen on tcp switch). It seems like /usr/X11R6/bin/X is whats causing the trouble, running tcpdump when X startx shows the name lookup BTW: 20:25:55.791908 IP litshi.luna.local.32784 rice.luna.local.domain: 6405+ A? -.luna.local. (30) 20:25:55.792612 IP litshi.luna.local.32785 rice.luna.local.domain: 7688+ PTR? 1.0.168.192.in-addr.arpa. (42) 20:25:55.793239 IP rice.luna.local.domain litshi.luna.local.32784: 6405 NXDomain* 0/1/0 (80) 20:25:55.793411 IP litshi.luna.local.32786 rice.luna.local.domain: 6406+ A? -. (19) 20:25:55.793894 IP rice.luna.local.domain litshi.luna.local.32785: 7688* 1/1/0 PTR[|domain] 20:25:55.794140 IP litshi.luna.local.32787 rice.luna.local.domain: 7689+ PTR? 3.0.168.192.in-addr.arpa. (42) 20:25:55.794252 IP rice.luna.local.domain litshi.luna.local.32786: 6406 NXDomain 0/1/0 (94) 20:25:55.794411 IP litshi.luna.local.32788 rice.luna.local.domain: 6407+ A? -.luna.local. (30) 20:25:55.795182 IP rice.luna.local.domain litshi.luna.local.32787: 7689* 1/1/0 PTR[|domain] 20:25:55.795591 IP rice.luna.local.domain litshi.luna.local.32788: 6407 NXDomain* 0/1/0 (80) 20:25:55.795645 IP litshi.luna.local.32788 rice.luna.local.domain: 6408+ A? -. (19) 20:25:55.796280 IP rice.luna.local.domain litshi.luna.local.32788: 6408 NXDomain 0/1/0 (94) 20:25:55.796419 IP litshi.luna.local.32788 rice.luna.local.domain: 6409+ A? local:root.luna.local. (39) 20:25:55.797114 IP rice.luna.local.domain litshi.luna.local.32788: 6409 NXDomain* 0/1/0 (89) 20:25:55.797158 IP litshi.luna.local.32788 rice.luna.local.domain: 6410+ A? local:root. (28) 20:25:55.797800 IP rice.luna.local.domain litshi.luna.local.32788: 6410 NXDomain 0/1/0 (103) 20:26:00.790557 arp who-has litshi.luna.local tell rice.luna.local 20:26:00.790591 arp reply litshi.luna.local is-at 08:00:46:5b:70:62 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] +++ This Mail Was Scanned By Mail-seCure System at the Tel-Aviv University CC. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X hangs on network timeout (hosts file ignored)
On Tue, 13 Jul 2004 20:28:56 +0300, Micha Feigin wrote: Same behavior (I am using wdm and no xdmcp and the no listen on tcp switch). It seems like /usr/X11R6/bin/X is whats causing the trouble, running tcpdump when X startx shows the name lookup BTW: you know, I think we're barking up the wrong tree, in fact I dont even think we are in the woods at all ;-) It might well be a bug. but a bug in what? Try without any x sessions running run 'X' as root and see how long does it take to start, that way you can see if it is xfree or (I assume your using it) gnome. Assuming it starts quickly, next you want to type: $ export DISPLAY=localhost:0.0 $ gnome-session (or enter the name of your wm's main app) If what I think the problem is is right this should be slow to launch, so exit it (not X just the wm) and this time on another console run 'netstat -c' This will show all network connections and refresh them every few seconds. then relaunch your wm and see does any new datagrams or streams open up in netstat, esp ones that sit in a state of 'SYN_SENT' You are going to get a few going no further than /tmp/.orbit-root, I'm fairly sure they will be streams, they are what gives gnome its network transparency, even local only connections open up sockets. Thats what I think the problem is, gnome is trying to open up a network socket to somewhere. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X hangs on network timeout (hosts file ignored)
On Mon, Jul 12, 2004 at 12:06:41AM +0100, Steven Satelle wrote: Ping uses the hosts file but host seems to ignore it. So if the nameserver is not reachable then ping hostname works but host hostname returns 192.168.0.1 connect: Network is unreachable Nameserver not reachable litshi.luna.local A record not found, try again my /etc/hosts has the following lines: 127.0.0.1 localhost 127.0.0.1 litshi.luna.local litshi (I know pointing hostname to 127.0.0.1 is not advised, but its a laptop and has several possible IPs). Any ideas? right you are getting me puzzled now :-) I suppose a bit of fishing is in order what's in /etc/host.conf, it should say 'order hosts,bind' order hosts,bind multi on that file tells the sys how to resolve hosts in the network, you want it to check the local hosts file before going to bind also whats in /etc/hostname? It should, at least on my sys, have the litshi hostname of the sys, not the fqdn, just the hostid.If It doesnt use 'hostname litshi' to set it, ignore the fqdn for now, just try with that. If that doesnt work, have you looked at m$ windows recently ;-) If even that doesnt work you could try (dont tell anyone I said this) a reboot, after setting the hostname and entering it into /etc/hosts, the files may just need to be re-read hostname returns litshi now I tried pulling the cable and testing again: ping litshi PING litshi.luna.local (127.0.0.1) 56(84) bytes of data. 64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.112 ms 64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.082 ms 64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.082 ms host litshi Nameserver not responding litshi.luna.local A record not found, try again (after reconnecting cable) host litshi litshi.luna.local A 192.168.0.3 /etc/hosts file: cat /etc/hosts 127.0.0.1 localhost 127.0.0.1 litshi.luna.local litshi Tried everything as root and checked read permissions for all the files ll /etc/ | grep -v .r..r..r total 1620 -rw---1 root root 144 2002-01-18 10:13 at.deny -rw---1 root root 549 2004-04-27 04:07 group- -rw-r-1 root shadow467 2004-05-08 16:54 gshadow -rw---1 root root 457 2004-04-27 04:07 gshadow- -rw---1 root root 998 2004-05-08 16:55 passwd- -rw-r-1 root shadow745 2004-05-08 16:55 shadow -rw---1 root root 685 2004-04-01 15:52 shadow- -r--r-1 root root 302 2004-04-01 06:14 sudoers Anything else that could cause the problem? BTW I got the following reply after I tried reporting a bug on netbase on this: [...] this is how it's supposed to work. host(1) is an interface to the resolver library, which does not use /etc/hosts by design. The problem is that it seems that a few other things seem to be ignoring the /etc/hosts file also. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] +++ This Mail Was Scanned By Mail-seCure System at the Tel-Aviv University CC. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X hangs on network timeout (hosts file ignored)
On Mon, 12 Jul 2004 17:58:40 +0300, Micha Feigin wrote: BTW I got the following reply after I tried reporting a bug on netbase on this: [...] this is how it's supposed to work. host(1) is an interface to the resolver library, which does not use /etc/hosts by design. The problem is that it seems that a few other things seem to be ignoring the /etc/hosts file also. what package are you getting host from, I dont have it on my system. whats in your /etc/resolv.conf, mine has search personal.ie nameserver 192.168.1.1 I think you should have nameserver 127.0.0.1 in there before any remote binds, I dont, but then, I dont have a problem ;-) I think If you have 127.0.0.1 in there as the first nameserver it will check the local one first (/etc/hosts) apart from that what happens if you run startx without gdm running? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X hangs on network timeout (hosts file ignored)
Incoming from Steven Satelle: On Mon, 12 Jul 2004 17:58:40 +0300, Micha Feigin wrote: [...] this is how it's supposed to work. host(1) is an interface to the resolver library, which does not use /etc/hosts by design. The problem is that it seems that a few other things seem to be ignoring the /etc/hosts file also. what package are you getting host from, I dont have it on my system. whats in your /etc/resolv.conf, mine has search personal.ie nameserver 192.168.1.1 If you want to augment that, it may be dependent on the package/transport you use to set up your network. I use pppd and I see there's a /etc/ppp/resolv/provider that lists nameserver xxx.xxx.xxx.xxx records to be used to create resolv.conf -- Any technology distinguishable from magic is insufficiently advanced. (*) http://www.spots.ab.ca/~keeling - - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X hangs on network timeout
--- Micha Feigin [EMAIL PROTECTED] wrote: I'm not sure yet on what package to report this bug, but was wondering if anyone else experiences it too. Have a look at the bugpage for 'xserver-xfree86'. If it isn't listed there, then maybe consider filing one. -- Thomas Adam = The Linux Weekend Mechanic -- http://linuxgazette.net TAG Editor -- http://linuxgazette.net shrug We'll just save up your sins, Thomas, and punish you for all of them at once when you get better. The experience will probably kill you. :) -- Benjamin A. Okopnik (Linux Gazette Technical Editor) ___ALL-NEW Yahoo! Messenger - so many all-new ways to express yourself http://uk.messenger.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X hangs on network timeout
On Sun, 11 Jul 2004 20:18:19 +0100, Thomas Adam wrote: --- Micha Feigin [EMAIL PROTECTED] wrote: I'm not sure yet on what package to report this bug, but was wondering if anyone else experiences it too. Have a look at the bugpage for 'xserver-xfree86'. If it isn't listed there, then maybe consider filing one. no, its caused by the machine trying to resolve its name over eth0 AFAIR. If the network is up. If you've configured the network, you've set a hostname, so it is trying to resolvethat. add the hostname to /etc/hosts and you shouldnt have any further problems. at least AFAIR -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X hangs on network timeout (hosts file ignored)
On Sun, Jul 11, 2004 at 08:33:15PM +0100, Steven Satelle wrote: On Sun, 11 Jul 2004 20:18:19 +0100, Thomas Adam wrote: --- Micha Feigin [EMAIL PROTECTED] wrote: I'm not sure yet on what package to report this bug, but was wondering if anyone else experiences it too. Have a look at the bugpage for 'xserver-xfree86'. If it isn't listed there, then maybe consider filing one. no, its caused by the machine trying to resolve its name over eth0 AFAIR. If the network is up. If you've configured the network, you've set a hostname, so it is trying to resolvethat. add the hostname to /etc/hosts and you shouldnt have any further problems. at least AFAIR Ping uses the hosts file but host seems to ignore it. So if the nameserver is not reachable then ping hostname works but host hostname returns 192.168.0.1 connect: Network is unreachable Nameserver not reachable litshi.luna.local A record not found, try again my /etc/hosts has the following lines: 127.0.0.1 localhost 127.0.0.1 litshi.luna.local litshi (I know pointing hostname to 127.0.0.1 is not advised, but its a laptop and has several possible IPs). Any ideas? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] +++ This Mail Was Scanned By Mail-seCure System at the Tel-Aviv University CC. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X hangs on network timeout
On Sun, 11 Jul 2004 22:53:09 +0200, Otto Wyss wrote: On Sun, 11 Jul 2004 20:18:19 +0100, Thomas Adam wrote: no, its caused by the machine trying to resolve its name over eth0 AFAIR. If the network is up. If you've configured the network, you've set a hostname, so it is trying to resolvethat. add the hostname to /etc/hosts and you shouldnt have any further problems. at least AFAIR What do you enter into /etc/hosts if you get the ip via DHCP? O. Wyss I dont know, try typing 'uname -n' that prints off the hostname your using. if by any chance your using a static dhcp address (thats what I tend to use, but I configure my own dhcp server) you will always be assigned the same address and therefore always get the same name and you could enter that into /etc/hosts. another easy option would be to set a hostname on the pc. just enter a name into /etc/hostname. That will set a perminent hostname on the pc, then enter that into /etc/hosts -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X hangs on network timeout (hosts file ignored)
Ping uses the hosts file but host seems to ignore it. So if the nameserver is not reachable then ping hostname works but host hostname returns 192.168.0.1 connect: Network is unreachable Nameserver not reachable litshi.luna.local A record not found, try again my /etc/hosts has the following lines: 127.0.0.1 localhost 127.0.0.1 litshi.luna.local litshi (I know pointing hostname to 127.0.0.1 is not advised, but its a laptop and has several possible IPs). Any ideas? right you are getting me puzzled now :-) I suppose a bit of fishing is in order what's in /etc/host.conf, it should say 'order hosts,bind' that file tells the sys how to resolve hosts in the network, you want it to check the local hosts file before going to bind also whats in /etc/hostname? It should, at least on my sys, have the hostname of the sys, not the fqdn, just the hostid.If It doesnt use 'hostname litshi' to set it, ignore the fqdn for now, just try with that. If that doesnt work, have you looked at m$ windows recently ;-) If even that doesnt work you could try (dont tell anyone I said this) a reboot, after setting the hostname and entering it into /etc/hosts, the files may just need to be re-read -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SOLVED: Re: starting X
On Fri, Jan 03, 2003 at 04:26:09PM -0500, Nori Heikkinen wrote: it seems weird to me that i'm in the group 'nori' and not 'users', but Debian creates a new user for each group by default. I think it's possible to change that, but I've never felt the need... the permissions on my homedir are correct, and i can create directories and files myself. they *were* weird when i copied everything from CD (everything was 444, pretty much -- but my homedir never was) ... but i've changed the only ones that matter, afaict. Ouchy. I had this problem when I restored from a CD too. In future I'll be much more careful with my mkisofs options. The only programs that really cared for me tho were SSH and GPG, for obvious reasons :) -rob msg22518/pgp0.pgp Description: PGP signature
Re: starting X
On Fri, Jan 03, 2003 at 02:35:35AM -0500, Nori Heikkinen wrote: however, it's segfaulting and refusing to do much once it gets to the 'WindowMaker' line in my ~/.xsession. ~/.xsession-errors tells me it's because i can't create a GNUstep directory, and tells me to run wmaker.inst: why can't it create the directory is what bothers me. are the permissions on your home dir not allowing you to create directories? or, perhaps if you've restored your homedir as root it's still owned by root? what happens if you try and create it manually from the cmdline? normally if you don't have that directory it should create it automatically without complaining much. (of course i forgot to copy these files from my old hard drive when i was making backups, as i didn't know what they were ... well, this is how you learn, i guess!) wmaker.inst seems to not really exist, except on some french Debian page somewhere. what should i do to generate the GNUstep directories and files that WindowMaker needs? it's just window manager settings and preferences, not having it shouldn't have broken anything. i'm guessing this is a symptom of another problem... sean msg22216/pgp0.pgp Description: PGP signature
Re: starting X
hey nori, hope your computer has thawed off a bit :) anyways, iirc this is provided by xserver-xfree86. the easy way to make sure you have everything installed that you need for x is to run tasksel and check the box for x windows. sean On Thu, Jan 02, 2003 at 06:01:17PM -0500, Nori Heikkinen wrote: first, thanks to all for your patience with my questions as i'm bringing up my box. i really appreciate it. right now, i'm trying to get X set up. i've downloaded and installed xdm, wmaker, and xbase-clients, which is all i seem to need to get a GUI up and going. on the hard drive which i'm replacing with this installation, to start window maker, i just typed 'startx' as root. reading manpages, i see that's a frontend to xinit, which is also in xbase-clients. right now, startx gives me the following error: /usr/X11RG/lib/X11/xinit/xserverrc: /usr/bin/X11/X: No such file or directory and more along those lines (i.e., one error said many times over). it's true -- there's nothing called 'X' in /usr/bin/X11. I'm assuming this is either a package i need to download, or something that gets created in a configuration somewhere. 'apt-cache search | egrep ^X' shows nothing, so I'm guessing it's not a package ... what do i need to install or configure to make this work? thanks a lot, /nori -- .~. nori @ sccs.swarthmore.edu /V\ http://www.sccs.swarthmore.edu/~nori/jnl/ // \\ @ maenad.net /( )\ www.maenad.net ^`~'^ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] msg22057/pgp0.pgp Description: PGP signature
Re: starting X
On Thursday 02 January 2003 06:40 pm, sean finney wrote: hey nori, hope your computer has thawed off a bit :) anyways, iirc this is provided by xserver-xfree86. the easy way to make sure you have everything installed that you need for x is to run tasksel and check the box for x windows. currently, tasksel seems to just install x-window-system. I assume by your methodology that you are more interested in initally going with a minimal install, so try apt-cache show x-window-system apt-cache show x-window-system-core then pick one and apt-get install it. -jason pepas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Starting X on second screen
On Wed, Oct 16, 2002 at 01:31:48PM +1000, Russell wrote:
Tom Cook wrote:
[snip]
In this line, I have recently (this morning) discovered the joys of
x2x to link two X displays. I have two p2/333s on my desk, and until
today I had two keyboards and mice, too. Now I'm writing this on one
display from the keyboard and mouse of the other - cool! Now I need a
few more boxen...
That's easy if both your boxes are linux;)
On linux: apt-get install x2vnc
On the other OS: hunt for vnc, download, run {setup,install}.exe, pray
and consider rebooting.
Same functionality as x2x, and allows you to control the other box
from the linux box.
--
Karl E. Jørgensen
[EMAIL PROTECTED]
www.karl.jorgensen.com
Today's fortune:
The sunlights differ, but there is only one darkness.
-- Ursula K. LeGuin, The Dispossessed
msg07330/pgp0.pgp
Description: PGP signature
Re: Starting X on second screen
On Tue, Oct 15, 2002 at 01:36:42PM +1000, Russell wrote: Hi all, When using xdm, there's no where to enter command line parameters to startx or initx (0:1 etc) for using a second monitor, so is there an option for this in .Xsession or some other file? I'm not using XDM at the moment, but GDM is controlled by files in /etc/X11/gdm; I imagine XDM works similarly. -rob msg07094/pgp0.pgp Description: PGP signature
Re: Starting X on second screen
On Tue, Oct 15, 2002 at 07:52:24PM +1000, Rob Weir wrote: On Tue, Oct 15, 2002 at 01:36:42PM +1000, Russell wrote: Hi all, When using xdm, there's no where to enter command line parameters to startx or initx (0:1 etc) for using a second monitor, so is there an option for this in .Xsession or some other file? I'm not using XDM at the moment, but GDM is controlled by files in /etc/X11/gdm; I imagine XDM works similarly. Yeah, I used to use xdm. There are several files in xdm's configuration directory that have to do with that, there's a script to run for each display, a file that lists the displays to start (I think xservers or something similar), and a resource file that contains resources for displays (both common and display-specific). -- Michael Heironimus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Starting X on second screen
On 0, Kent West [EMAIL PROTECTED] wrote: Tom Cook wrote: How would you start multiple screens using startx? 'startx -- :0.1' doesn't work for me, but then I don't have multiple screens. I believe this would attempt to start X on the Virtual Desktop #1 on the first (:0) display; what you probably want is: startx -- :1 Not so. The :x.y notation refers to different screens connected to the same display. A 'screen' in X terminology is not a monitor but a complete input/output system (monitor, keyboard, mouse) that is controlled by the same X server. The 'x' is which X server to connect to, and the 'y' is which screen on that server to display on. I thought (rather excitedly) that :0.1 might mean virtual desktop 1, but virtual desktops are a WM illusion, nothing more. So: $ xterm -display :0.1 xterm Xt error: Can't open display: :0.1 $ xterm -display :0.0 $ Screens are different concepts to X servers and also different to multi-headed displays (I think - not sure on that). I have never seen a system with more than one screen. In this line, I have recently (this morning) discovered the joys of x2x to link two X displays. I have two p2/333s on my desk, and until today I had two keyboards and mice, too. Now I'm writing this on one display from the keyboard and mouse of the other - cool! Now I need a few more boxen... Tom -- Tom Cook Information Technology Services, The University of Adelaide Intellectual freedom is not the freedom to believe anything, but the freedom to believe only the truth. - Dr. John Stott Get my GPG public key: https://pinky.its.adelaide.edu.au/~tkcook/tom.cook-at-adelaide.edu.au msg07263/pgp0.pgp Description: PGP signature
Re: Starting X on second screen
Tom Cook wrote: On 0, Michael Heironimus [EMAIL PROTECTED] wrote: On Tue, Oct 15, 2002 at 07:52:24PM +1000, Rob Weir wrote: On Tue, Oct 15, 2002 at 01:36:42PM +1000, Russell wrote: Hi all, When using xdm, there's no where to enter command line parameters to startx or initx (0:1 etc) for using a second monitor, so is there an option for this in .Xsession or some other file? I'm not using XDM at the moment, but GDM is controlled by files in /etc/X11/gdm; I imagine XDM works similarly. Yeah, I used to use xdm. There are several files in xdm's configuration directory that have to do with that, there's a script to run for each display, a file that lists the displays to start (I think xservers or something similar), and a resource file that contains resources for displays (both common and display-specific). Yup, the default /etc/X11/xdm/Xservers even has an example for multiple local X displays. Not sure if this is what you want for multiple screens though... Each X server (display) that is started controls one keyboard, mouse, and one or more monitors. The first X server is assigned display :0, the next gets :1 etc. The second monitor on server :0 is assigned :0.1. How would you start multiple screens using startx? 'startx -- :0.1' doesn't work for me, but then I don't have multiple screens. I think that would be starting a second X server that would conflict with the first (display :0). If what you want is two X _servers_ running, then you need this in Xservers: :0 local /usr/X11R6/bin/X :0 vt9 -bpp 16 :1 local /usr/X11R6/bin/X :1 vt10 -bpp 8 but that is different to multiple screens. It also locks me out;) Both servers are trying to use the same keyboard, mouse, and monitor. If you do startx, it starts display :0:0. My first monitor shows X and fvwm. The second monitor shows only X (with xinerama turned off in XF86Config-4). If i enter xterm -display :0.1 in an xterm, it starts a second xterm on the other monitor, but i can't access it with mouse or keyboard. I'm using different layout sections in xf86config-4 to start with different monitor arrangements now anyway. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Starting X on boot. (Not xdm, kdm gdm style)
On Sat, Sep 21, 2002 at 11:54:14AM -0400, Stephen Gran wrote: I suppose the other way to go about doing this is through inittab. X takes an argument for user, IIRC, and so you could have inittab start X for a specific user at a specific runlevel (say 2, the Debian default). This would bypass the (x,k,g)dm issue entirely. Thanks a lot. I found this page that has all the details about your suggested approach. http://www.linuxgazette.com/issue52/tag/14.html -- Alex Polite http://plusseven.com/gpg/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Starting X directly
On Mon, Sep 10, 2001 at 02:15:39PM +0200, Julio Merino wrote: Hi all, how can I setup my desktop system to directly boot into X and do login? That is, like some distros (i.e. mdk) do, that they boot directly into KDE without asking to log in. Thanks. -- FreeBSD is the power-- Julio Merino [EMAIL PROTECTED] ICQ: 18961975 Fiddle around with /etc/kde/kdmrc There are settings in there to let you log in as a default password and user. -- Danie Roux *shuffle* Adore Unix
Re: Starting X directly
Julio Merino wrote: Hi all, how can I setup my desktop system to directly boot into X and do login? That is, like some distros (i.e. mdk) do, that they boot directly into KDE without asking to log in. Thanks. apt-get install gdm or apt-get install kdm hth joerg -- Did you know that if you play a Windows 2000 cd backwards, you will hear the voice of Satan? That's nothing! If you play it forward, it'll install Windows 2000.
Re: Starting X directly
On Mon, Sep 10, 2001 at 02:21:50PM +0200, Danie Roux wrote: On Mon, Sep 10, 2001 at 02:15:39PM +0200, Julio Merino wrote: Fiddle around with /etc/kde/kdmrc There are settings in there to let you log in as a default password and user. Well, I guess this is a security hole...? Thanks. -- Danie Roux *shuffle* Adore Unix -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- FreeBSD is the power-- Julio Merino [EMAIL PROTECTED] ICQ: 18961975 pgpHKZB96351y.pgp Description: PGP signature
Re: Starting X directly
On Mon, Sep 10, 2001 at 02:52:41PM +0200, Julio Merino wrote: On Mon, Sep 10, 2001 at 02:21:50PM +0200, Danie Roux wrote: On Mon, Sep 10, 2001 at 02:15:39PM +0200, Julio Merino wrote: Fiddle around with /etc/kde/kdmrc There are settings in there to let you log in as a default password and user. Well, I guess this is a security hole...? Thanks. Without a doubt it's a security hole, since it's not secure at all :-) -- Danie Roux *shuffle* Adore Unix
Re: Starting X directly
What I meant as security hole... I wanted to say if that kdm autologin is a security hole exploitable remotely? Thanks. PS: This is not a real reply... I've erased all topic threads :p -- FreeBSD is the power-- Julio Merino [EMAIL PROTECTED] ICQ: 18961975 pgpSSFIMbolcZ.pgp Description: PGP signature
Re: Starting X directly
On Mon, Sep 10, 2001 at 03:36:59PM +0200, Julio Merino wrote: What I meant as security hole... I wanted to say if that kdm autologin is a security hole exploitable remotely? No, it's only a problem if you have evil people who have physical access to the machine so that they could reboot it and get logged in automatically. I think this is so anyway. Maybe if you started a remote X session it would be able to log you in, but I don't think it lets you do this. So no more a security hole then having a floppy drive in the machine into which somebody could stick a boot disk.
Re: Starting X directly
On Mon, Sep 10, 2001 at 03:36:59PM +0200, Julio Merino wrote: What I meant as security hole... I wanted to say if that kdm autologin is a security hole exploitable remotely? Thanks. No, but don't quote me on that. -- Danie Roux *shuffle* Adore Unix
Re: Starting X directly
On Mon, Sep 10, 2001 at 11:55:27PM +1000, Tom Massey wrote: On Mon, Sep 10, 2001 at 03:36:59PM +0200, Julio Merino wrote: What I meant as security hole... I wanted to say if that kdm autologin is a security hole exploitable remotely? No, it's only a problem if you have evil people who have physical access to the machine so that they could reboot it and get logged in automatically. I think this is so anyway. Maybe if you started a remote X session it would be able to log you in, but I don't think it lets you do this. So no more a security hole then having a floppy drive in the machine into which somebody could stick a boot disk. Ok, I have no evil people at home, lol. But having physical access to the computer is like having full control, so I think I'll stick with this autologin for some time (until I get bored of it). Thanks for your help. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- FreeBSD is the power-- Julio Merino [EMAIL PROTECTED] ICQ: 18961975 pgpmr27U1PVY8.pgp Description: PGP signature
Re: Starting X/Gnome
Hi HawkY, under /root or your home directory create a file called .xinitrc (be careful! there's a dot before the 'x') and put in it simply: gnome-session In so doing, when you issue startx a gnome session will be run. This is a powerful way of customizing your desktop. For instance I have a user for which I put the following two lines in .xinitrc: ./office52/./soffice icewm When I run startx a Star Office 5.2 session is started. Another important file to customize your X window is .xsession which is called by xdm. Vittorio On Mon, 04 Jun 2001, HawkY wrote: Date: Mon, 04 Jun 2001 14:04:27 +0200 To: Debian User Mailing List debian-user@lists.debian.org From: HawkY [EMAIL PROTECTED] Subject: Starting X/Gnome Hi! Where can I define what I want to launch at startup? (I don't want X to be started at startup.) I've installed Gnome, but I want to launch it. (I might be wrong. I don't really know much about X.) When X is started, I get a login prompt. (Big white window with large black letters.) If I enter the data, it launches WMaker. Is it Gnome? (I'd like to install Ximian Gnome but when I try to launch Red Carpet I get a message: GTK error: Error opening display or something.) Is it beaceuse X is still running? (When I press ctrl+alt+f7.) Thanx! HawkY -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Spruce: Yeah baby, YEAH!
Re: Starting X/Gnome
On Mon, Jun 04, 2001 at 02:04:27PM +0200, HawkY wrote: Where can I define what I want to launch at startup? (I don't want X to be started at startup.) Your default runlevel is specified in /etc/inittab (it's probably 2), and the programs that are launched for each runlevel are specified in its rc directory (that is, all the programs that launch at runlevel two are specified in /etc/rc2.d, and all the ones for runlevel five are specified in /etc/rc5.d, etc.). If there's something in there that you don't want to run, just remove it. There's a proper Debian way of doing this, but, er, I don't know it :). In your case you probably want to remove S99gdm or S99xdm from /etc/rc2.d. I've installed Gnome, but I want to launch it. (I might be wrong. I don't really know much about X.) Edit .xsession (in your home directory), so that it contains exec gnome-session Then type startx and hit enter. When X is started, I get a login prompt. (Big white window with large black letters.) If I enter the data, it launches WMaker. Is it Gnome? Nope. Gnome is a desktop environment -- like MS Windows, with a file manager and help system and method of launching programs and a window manager and blah blah blah :) -- whereas WindowMaker is just (just, he says! :) a window manager. (I'd like to install Ximian Gnome but when I try to launch Red Carpet I get a message: GTK error: Error opening display or something.) Is it beaceuse X is still running? (When I press ctrl+alt+f7.) Edit your /etc/apt/sources.list file so that it contains deb http://red-carpet.ximian.com/debian stable main and then run apt-get update apt-get install task-ximian-gnome ...although it sounds like you've got Ximian Gnome installed already, if you've got Red Carpet on your system. It sounds like you're getting that GTK error because you're trying to run Red Carpet from a console -- you'll need to run it from a virtual terminal like xterm or rxvt while you're in X. Cheers! Andrew Sione Taumoefolau [EMAIL PROTECTED] http://users.pipeline.com.au/tonga/
Re: Starting X through INIT and kdm
On Mon, May 07, 2001 at 06:22:00PM +0200, Raffaele Sandrini wrote: Hi all Until now i start X with the startx command. I'd like to set it up that init X starts with the kdm interface. How do i do this on debian. I think that has somethiing to do with the alternatives System... Do i have to make a script by myself? Pls give some hints :-))) Do you have the kdm package installed? kent -- From seeing and seeing the seeing has become so exhausted First line of The Panther - R. M. Rilke
Re: Starting X through INIT and kdm
On Monday 07 May 2001 18:55, ktb wrote: On Mon, May 07, 2001 at 06:22:00PM +0200, Raffaele Sandrini wrote: Hi all Until now i start X with the startx command. I'd like to set it up that init X starts with the kdm interface. How do i do this on debian. I think that has somethiing to do with the alternatives System... Do i have to make a script by myself? Pls give some hints :-))) Do you have the kdm package installed? kent I have installed it but i compile KDE for myself (developer) earlier i was on a SuSE system there configure the init process by myself. My question is only if what system Debian is using the probbalby easy the process or if i have to build all init scripts by myself? I wont install QT,KDE and stuff like that over debian packages... cheers, Raffaele -- Raffaele Sandrini [EMAIL PROTECTED] For encrypted Mail get my Public Key from search.keyserver.net ID is: 0xEC4950E9 Fingerprint: FFEA 3317 8624 4771 A05D 2AFA 46A2 A22B EC49 50E9
Re: starting x manually as non-root
David B Harris writes: dbh Check /etc/X11/Xwrapper.config . Changing allowed_users from rootonly to console had the desired effect. Thx, Bernd. -- Bernd Sokolowsky @ home
Re: starting x
using /dev/saux works fine! thankx for all the replies everyone thankx A. Sullivan On Fri, Mar 17, 2000 at 06:17:26PM -0800, Beavis wrote: Detected PS/2 Mouse Port. i am using the /dev/ttyS01 during config. my systems says ttyS01 at do u think it could be the mouse? Using S3 (86C325) driver and XF86-SVGA server colors look ok Well, do you have a PS/2 mouse, or a serial mouse? /dev/ttySn is the device name for a serial port, so if you have a serial mouse, that's what you use. But if you have a PS/2-type mouse (with the little DIN connector), you have to use /dev/psaux instead. -- Andrew Sullivan Computer Services [EMAIL PROTECTED]Burlington Public Library +1 905 639 3611 x158 2331 New Street Burlington, Ontario, Canada L7R 1J4
Re: starting x
In xf86config when it asks where your mouse is, default /dev/mouse, try /dev/psaux. Also tell it youhave a ps/2 mouse when it asks what kind of mouse you have. you can also do this in XF86Setup. Erik Ryberg Beavis wrote: hello, i am slowly coming along in terms of setting up x.i have gotten past the grey screen w/ an x in the middle, to a purple one with icons in the corner, one w/ a blk/wht moon. another w/ a computer, and another with some kind of graph. As well as an icon in the other corner. my mouse doesn't move and the tab keys don't do anything either. My pointer just sits in the middle of the screen.dmesg reads:Detected PS/2 Mouse Port.i am using the /dev/ttyS01 during config. my systems saysttyS01 at do u think it could be the mouse? Using S3 (86C325) driver and XF86-SVGA servercolors look ok any ideas would be appreciated.thankx again debianlist beavis (butthead says hi!)
Re: starting x
my mouse doesn't move and the tab keys don't do anything either. My pointer just sits in the middle of the screen. dmesg reads: Detected PS/2 Mouse Port. i am using the /dev/ttyS01 during config. my systems says ttyS01 at If you are using PS/2 mouse, your mouse is located on /dev/psaux /dev/ttyS0-4 are serial ports, so you need to know exactly where it is. Rerun xf86config or XF86Setup and set the right mouse type and device. beavis (butthead says hi!) Technically, Butthead does not say 'hi', he says Come to Butthead But 'hi' will work for now. *obviously too much B'n'B in early college years* Andrew - Andrei S. Ivanov [EMAIL PROTECTED] [EMAIL PROTECTED] http://scorpio.dynodns.net -| http://scorpio.myip.org-| --All the pages bundled together. http://arshes.dyndns.org -| If one does not work, try another :) UIN 12402354 To get my GnuPG public key, go to scorpio.dynodns.net/GnuPG scorpio.myip.org/GnuPG arshes.dyndns.org/GnuPG -
Re: starting X apps as root
Robert Vollmert [EMAIL PROTECTED] writes: is there a comfortable way of starting programs as root when I'm logged in as a normal user? Look into the sudo package. -- Henning Makholm http://www.diku.dk/students/makholm
Re: Starting X From .bash_profile
I have a Diamond Sonic Impact sound card. Which driver should I use? My system is Debian 2.0.
Re: starting X at boot
On Sat, 25 Apr 1998, Alain Toussaint wrote: i think i found the problem,if i do a cat /etc/init.d/xdm,there's nothing who's writen on screen but if i do a cat /etc/init.d/xdm.dpkg-dist,then i have this output (it will be shown after my message),does it's possible that dpkg failed to update the /etc/init.d/xdm ??? Actually, I've had this happen before to me too. I don't remember what the exact circumstances were, so I didn't submit a bug report. Can you describe the exact procedure that led to this situation? Cheers, Joost -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X at boot
Actually, I've had this happen before to me too. I don't remember what the exact circumstances were, so I didn't submit a bug report. Can you describe the exact procedure that led to this situation? i don't know,it's just that i looked in the boot sequence (to be exact,in the /etc/init.d/ section),and found 2 files (xdm and xdm.dpkg-dist),i did a cat on these files (hoping they where text like files) and found that there where nothing in xdm and there where text in the second one,in the upper part of the xdm.dpkg-dist file,i found this inscription ( #/etc/init.d/xdm: start or stop XDM.),so far,except curiosity,there where no way i could know that the source of my problem was these files. hope it help. Alain Cheers, Joost -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X at boot
On Mon, 27 Apr 1998, Alain Toussaint wrote: Actually, I've had this happen before to me too. I don't remember what the exact circumstances were, so I didn't submit a bug report. Can you describe the exact procedure that led to this situation? i don't know,it's just that i looked in the boot sequence (to be exact,in the /etc/init.d/ section),and found 2 files (xdm and xdm.dpkg-dist),i did a cat on these files (hoping they where text like files) and found that there where nothing in xdm and there where text in the second one,in the upper part of the xdm.dpkg-dist file,i found this inscription ( #/etc/init.d/xdm: start or stop XDM.),so far,except curiosity,there where no way i could know that the source of my problem was these files. I'm not sure if I'm answering the question, but here goes anyway. When you installed xbase, you are likely to have got that little message along the lines of File /etc/init.d/xdm found already on system, N O keeps your version, Y I replaces it with package maintainer's version Z to investigate. I can't recall what writes the first version, but it's empty and needs to be replaced at this point. (I don't use Z, but just Alt-F2 to have a look.) It actually doesn't matter what you respond with in the sense that the same files exist on the system, just their names change. You either end up with Y xdm.dpkg-old (the empty original) and xdm (correctly installed) N xdm.dpkg-dist (the one you should have installed) and xdm (the empty original) if I remember the names correctly. The same juggling occurs with /etc/X11/Xserver and you can end up with any of /bin/false or XF86_None or XF86_Mach64 (or whatever). Cheers, -- Email: [EMAIL PROTECTED] Tel: +44 1908 653 739 Fax: +44 1908 655 151 Snail: David Wright, Earth Science Dept., Milton Keynes, England, MK7 6AA Disclaimer: These addresses are only for reaching me, and do not signify official stationery. Views expressed here are either my own or plagiarised. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X at boot
i think i found the problem,if i do a cat /etc/init.d/xdm,there's nothing
who's writen on screen but if i do a cat /etc/init.d/xdm.dpkg-dist,then i
have this output (it will be shown after my message),does it's possible
that dpkg failed to update the /etc/init.d/xdm ???
Alain
--/etc/init.d/xdm.dpkg-dist
#!/bin/sh
# /etc/init.d/xdm: start or stop XDM.
test -x /usr/bin/X11/xdm || exit 0
test -f /etc/X11/config || exit 0
if grep -q ^xbase-not-configured /etc/X11/config
then
exit 0
fi
run_xdm=0
if grep -q ^start-xdm /etc/X11/config
then
run_xdm=1
fi
case $1 in
start)
if [ $run_xdm = 1 ]
then
start-stop-daemon --start --verbose --exec /usr/bin/X11/xdm
fi
;;
stop)
if [ $run_xdm = 1 ]
then
start-stop-daemon --stop --verbose --pidfile /var/run/xdm-pid \
--exec /usr/bin/X11/xdm
fi
;;
*)
echo Usage: /etc/init.d/xdm {start|stop}
exit 1
esac
exit 0
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X at boot
it work !! i copied the xdm.dpkg-dist file over xdm and now,i boot with X enabled !! Alain p.s.something to check next time that a user run into this problem. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X at boot
What version of grep do you have there? Version 2.1-7 is broken, that might also be the cause. In any case, you can always look at /var/log/xdm-errors i dont even have this file ( /var/log/xdm-error) and grep is version 2.0 thanks for your help. Alain Cheers, Joost -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X at boot
On Fri, 24 Apr 1998, Alain Toussaint wrote: i was surfing on the internet and viewed some comments on enabling X at boot,i tried the trick down there ( modify /etc/X11/config so the line no-start-xdm look like start-xdm,backup /etc/inittab and modify so when booting,it load into runlevel 5) but this hasn't worked,is there some When I enabled my XDM I didn't mess with /etc/inittab I just modified /etc/X11/config like the one I am attaching to you. (Sorry for the attachment... but I coundn't cut/paste... not on my machine... ;) document i could read for enabling X at boot ( and i did read a lot of the manpage sooner this week on this) ??? p.s.i put the backup inittab back into the /etc directory so it start back in runlevel 2. p.p.s.i'm using debian 1.3.1 Alain I think that everything should work just fine with the above config file, at least it does for me... ;) Daniel. __ Daniel Doro Ferranteemail: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] System Administrator http://www.cecm.usp.br/~danieldf CECM - Curso de Ciencias Moleculares - USP Course of Molecular Sciences - University of Sao Paulo # This file contains configuration flags for the X Window System. # For a description of the meanings of the flags, see # /usr/doc/X11/debian.README run-xconsole obey-nologin allow-user-resources allow-user-modmap allow-user-xsession allow-failsafe xdm-start-server #start-xdm no-start-xdm
Re: starting X at boot
On Fri, 24 Apr 1998, Alain Toussaint wrote: i was surfing on the internet and viewed some comments on enabling X at boot,i tried the trick down there ( modify /etc/X11/config so the line no-start-xdm look like start-xdm,backup /etc/inittab and modify so when booting,it load into runlevel 5) but this hasn't worked,is there some document i could read for enabling X at boot ( and i did read a lot of the manpage sooner this week on this) ??? p.s.i put the backup inittab back into the /etc directory so it start back in runlevel 2. You probably have to add a single line to /etc/X11/xdm/Xservers too: ---cut--- # $XConsortium: Xserv.ws.cpp,v 1.3 93/09/28 14:30:30 gildea Exp $ # # Xservers file, workstation prototype # # This file should contain entries to start the servers on the # local machine; if you have more than one display (not screen), # you can add entries to the list (one per line). If you also # have some X terminals connected which do not support XDMCP, # you can add them here as well. Each X terminal line should # look like: # XTerminalName:0 foreign # # X servers are automatically added to this file by the Debian # xbase and xserver configuration scripts. :0 local /usr/X11R6/bin/X ---cut--- Look at the last line, I bet it is missing on your system. It tells xdm which xserver to run on what display. If there is no such line, xdm will still be running, you'll just not notice anything you would expect (like seeing the xserver you expect it to start.) Cheers, Joost -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X at boot
Have you guys already tried Debian's xbase-configure yet? It is normally run during the xbase package install, but I believe that it will setup xdm to start at boot if you haven't already done so. -Ossama __ Ossama Othman [EMAIL PROTECTED] --- PGP Keys --- Public: http://astrosun.tn.cornell.edu/staff/othman/OO_PUBLIC.asc REVOKED: http://astrosun.tn.cornell.edu/staff/othman/OO_REVOKED.asc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X at boot
# xbase and xserver configuration scripts. :0 local /usr/X11R6/bin/X ---cut--- Look at the last line, I bet it is missing on your system. It tells xdm which xserver to run on what display. If there is no such line, xdm will still be running, you'll just not notice anything you would expect (like seeing the xserver you expect it to start.) Cheers, the line is there and my /etc/X11/config file is writen as this: # This file contains configuration flags for the X Window System. # For a description of the meanings of the flags, see # /usr/doc/X11/debian.README run-xconsole obey-nologin allow-user-resources allow-user-modmap allow-user-xsession allow-failsafe start-xdm xdm-start-server i think there other thing to play as well but dont know what. Alain Joost -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X at boot
Have you guys already tried Debian's xbase-configure yet? It is normally run during the xbase package install, but I believe that it will setup xdm to start at boot if you haven't already done so. -Ossama i'll check into this. Alain -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X at boot
On Fri, 24 Apr 1998, Alain Toussaint wrote: i think there other thing to play as well but dont know what. Oh. Too bad that it didn't help you then. What version of grep do you have there? Version 2.1-7 is broken, that might also be the cause. In any case, you can always look at /var/log/xdm-errors Cheers, Joost -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Starting X-Windows 8bpp
Can anyone tell me how to start X-Windows at greater than 8bpp. I am using XFree86 and using an X Server which is capable of this. Try the following from the user account that you want to use for X windows viewing. cd touch .xserverrc [Then use the editor of your choice to edit .xserverrc] [With the editor, save the following .xserverrc file in your /home/user directory.] exec X :0 -bpp 16 That should allow you to view with 16-bit color, and you may adapt it for the other color depths (if any) that your video card allow. I suspect that there may be other ways of doing it, also. Art Lemasters Thanks -- John Wingfield Committee Member Website Manager British Double Reed Society [EMAIL PROTECTED] http://www.bdrs.demon.co.uk/ -- 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: Starting X-Windows 8bpp
Take a glance at xinit or startx's man page. It boils down to a -bpp option. -- --- How can you see, when your mind is not open? How can you think, when your eyes are closed? - Jason Bonham Band, Ordinary Black and White --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Starting X in 16 bpp ?
I created the file /etc/X11/xinit/xserverrc and it is a text file saying X -bpp 16 and it works, and I think this came from the XFree86 documentation, so perhaps it isn't the debian way of doing things, which is what you asked for, Binary Bar - Australia's first free access internet bar/cafe/gallery. 243 Brunswick Street, Fitzroy, Melbourne, Australia. 12:00pm - 11:00pm http://www.binary.net.au On Tue, 9 Sep 1997 [EMAIL PROTECTED] wrote: On Sep 9, Ricardo Muggli wrote What is the debian whay of starting X in 16 bpp? I can do this: startx -- -bpp 16 but I would like to be able to do just startx. Any information as to what file(s) I need to modify would be greatly appreciated. Put DefaultColorDepth 16 in Section Screen of /etc/X11/XF86Config . HTH, Ray -- Tevens ben ik van mening dat Nederland overdekt dient te worden. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] . -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Starting X in 16 bpp ?
On Sep 9, Ricardo Muggli wrote What is the debian whay of starting X in 16 bpp? I can do this: startx -- -bpp 16 but I would like to be able to do just startx. Any information as to what file(s) I need to modify would be greatly appreciated. Put DefaultColorDepth 16 in Section Screen of /etc/X11/XF86Config . HTH, Ray -- Tevens ben ik van mening dat Nederland overdekt dient te worden. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Starting X in 16 bpp ?
Ricardo Muggli wrote: What is the debian whay of starting X in 16 bpp? I can do this: startx -- -bpp 16 but I would like to be able to do just startx. First, in your .profile or .login or whatever assure that your bin is first. For a .profile with sh or bash or ksh ... export PATH=$HOME/bin:$PATH then, if you don't have one yet, mkdir $HOME/bin then do this: echo /usr/bin/X11/startx -- -bpp 16 $HOME/bin/startx chmod +x $HOME/bin/startx from now on you can simply: startx to start X. HTH Any information as to what file(s) I need to modify would be greatly appreciated. - [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] . -- - Ralph Winslow [EMAIL PROTECTED] The IQ of the group is that of the member whose IQ is lowest divided by the number of members. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: starting X with another display
On Thu, 19 Jun 1997, BG Lim wrote: What is the command to open a separate display instead of VT7? For startx, it's exec startx -- :1 but I don't know about xdm. ...RickM... -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: starting X with another display
On Thu, 19 Jun 1997, BG Lim wrote: What is the command to open a separate display instead of VT7? For startx, it's exec startx -- :1 but I don't know about xdm. This is, if you have another screen attached to your computer. But I suppose you want to run another X server. I had to do this with for to be able to test a program I was develloping under different conditions. It's possible to add a line in /etc/X11/xdm/Xserver: :1 local tty08 /usr/X11R6/bin/X -bpp 8 -cc 3 -bpp 8 of course is the depth of color planes, and -cc 3 is the visual type. As a reminder, I put in mine these comments: # 0 for StaticGray # 1 for GrayScale # 2 for StaticColor # 3 for PseudoColor # 4 for TrueColor # 5 for DirectColor But actually, It might be a better idea to call this manually with startx, if you don't need the 2nd X server running all the time. -- Ciccio C. Simon [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: starting X with another display
On Thu, 19 Jun 1997, Ciccio wrote: On Thu, 19 Jun 1997, BG Lim wrote: What is the command to open a separate display instead of VT7? For startx, it's exec startx -- :1 but I don't know about xdm. This is, if you have another screen attached to your computer. But I suppose you want to run another X server. I had to do this with No, I'm doing this as I write. The above command opens another xserver on VT8 and I can switch back and forth with CTRL-ALT-F7 / F8. ...RickM... -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
