Operating Systems > Linux and UNIX

X problems

<< < (5/6) > >>

LorKorub:
You can use Ctrl+Alt+F1-F6 to get a virtual terminal. Ctrl+Alt+F7 (otherwise known as tty07) is the terminal reserved for X.

Why you have a blank screen on tty01 is beyond me. You might have to adjust your default run levels in /etc/inittab. Make sure your default run-level is at 5 (multiuser level.) That way, you will have virtual terminals where you can screw around with the X config file, and not have to reboot everytime.  

You still haven't told us what kind of card you are using.  Some cards are not supported under X, and you have to manually load drivers. I had to do this on a friend's machine that was using some Trio 3D piece of shit.

choasforages:
actally, it depends on the init config which terminal XFree86 is on. i know on some of the BSD's i have used, it was ctrl + alt + f5. as for the resolution, it automatically using the highest resolution it can. i don't know howto setup a default resolution lower then the highest one avialable.

beltorak0:
When the computer boots with X, the "/etc/inittab" file should reserve one tty for the console (for just these situations).  In slackware it's tty06 ([Ctrl] [Alt] [F6]); in red hat it might be 5.  try them all.  X Windows opens itself on 7 when run (at least in linux), probably because it's the next number availible.

Now for X itself.  Have you tried to set the card driver to "unsupported VESA"?  it might at least be usable.  If on the other hand what you have is usable (except for the fact that the default res is too low), then there are several lines that need to be dealt with in XF86Config;

--- Code: ---
--- End code ---
The important lines are "DefaultDepth", which for me is set to 24 (as in bits-per-pixel).  So, under the appropriate SubSection "Display" you can see the default modes associated with it.  The first mode listed is the default.  They should be a reference to another section of the file: Section "Monitor".  It should have a listing for each mode you defined during the config setup, but especially the one you use most.

--- Code: ---
--- End code ---

For referencing, the name has to be the same one referenced inside the screen section: (quoted again for clarity)

--- Code: ---
--- End code ---

--- Code: ---
--- End code ---

--- Code: ---
--- End code ---


hope this helps;


just FYI, the relavent lines at the bottom of "/etc/inittab" (for slackware) are

--- Code: ---
--- End code ---

It is saying that consoles 1-5 are open for runlevels 1,2,3, and 5, but only console 6 is open for 1,2,3,4, and 5.  slackware uses runlevel 4 for booting into X... redhat uses 5 (or is that 3?), so adjust accordingly.

[ January 17, 2003: Message edited by: beltorak ]

[ January 17, 2003: Message edited by: beltorak ]

Maniaman:
X workd for the most part now. I'm still stuck with KDE and command prompt login. When I try to open /etc/inittab it tells me Permission Denied (I'm logged in as root) I could just reboot and fix it but I dont want to loose my uptime  

beltorak0:
so what are the perms on that file: "ls -l /etc/inittab"?  it's odd that you don't have any perms on it as root....

as for the default wm -- check your home directory.  there should be a file: ".xinitrc".  That is the control script that runs when you "startx".  It might be a symlink, in which case it should point to one of the scripts in "/etc/X11/xinit/xinitrc.$wm".  If you want to save it, move it to something like ".old.xinitrc" and do "ln -s /etc/X11/xinit/xinitrc.gnome .xinitrc" to set your default wm to gnome.  It should take effect when you "startx".

when you get your write perms back to /etc/inittab you can make the changes necessary to kick you into runlevel 5 upon boot.  failing that, this can be used as an ugly workaround:


--- Code: ---
--- End code ---

Save this as "/etc/init.d/rc3.d/S99telinit5", and don't forget to "chmod ug+x S99telinit5".

and HEED the warning in the header.  For most boot loaders you can pass the "single" option to the kernel at boot time to boot into runlevel 1 -- it might be wise to try this out first....

Also, since i don't have a SysV type setup, i might be wrong about that "/etc/init.d/" directory.  It might be "/etc/rc.d".

have fun

Navigation

[0] Message Index

[#] Next page

[*] Previous page