You are not logged in.
Pages: 1
There is same topic in this forum but still I don't know how to solve my problem.
I've got gdm in daemons and after few sec my X are on and I can't do ANYTHING but reboot.
Before X starts i can change tty or log in, but gdm will start anyway.
Its my first instalation of Arch, previously i was using Ubuntu. After installation everything was working fine, I installed some stuff, mouse and keyboard was working fine, but it cracked after reboot .
Last edited by Uriziel (2009-07-10 21:55:33)
Offline
kk, but I can't check if its started or start it after my X starts, and I don't know how to prevent it
btw. afair i added hal to daemons
Offline
As I wrote before my X starts automatically because of gdm in daemons, that's why I don't know what to do
Offline
Just for knowing how treasure archwiki:
http://wiki.archlinux.org/index.php/Xorg
This line: "Add hal to DAEMONS array of /etc/rc.conf"
Offline
That still doesn't solve my problem because I can't prevent auto startx
Last edited by Uriziel (2009-07-10 22:03:13)
Offline
As I wrote before X starts automatically after boot
Offline
No, how can I do that?
I'm Ubuntu user : <, everything there was done in some simple, lame way so I didn't learn anything about 'true' Linux there
Offline
wow... did you follow the Beginners Guide?
Offline
Well, yeah, afair I did everything what's in there.
But there isn't anything about inittab besides kde section
Offline
So... You installed X, didn't test it assuming everything was all right, and went on installing a DE and a DM..? I remember the Beginner's Guide explicitally mentioning testing X before moving on You can remove gdm/kdm/xdm from your daemons so X won't be started in your boot sequence, then you can test HAL and your X server.
Offline
Well, everything was working fine, I was running gnome, installed some stuff, it cracked after reboot.
How can I remove gdm from daemons when X starts and I can't do anything but reboot? I'm still waiting for this solution
Offline
Ah, I'm sorry: I shouldn't be so quick in my judgement I think you should be able to modify your boot sequence in GRUB. I think you can enter a custom line in order not to boot into X, although I'm not entirely sure how this can be done... I hope someone more experienced than me can help you!
Last edited by whordijk (2009-07-10 22:46:48)
Offline
Read his posts. He has gdm being launched from his daemons array (which is a bad idea, if you want to launch X at startup look at /etc/inittab)
Appending 3 to the kernel line won't help.
Uri, what you should do is boot with the arch install cd, mount whatever partition has your /etc directory on it, and edit the file /etc/rc.conf At the end of this file will be this section
# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
#
Your daemons line might look like this:
DAEMONS=(syslog-ng dbus network netfs gpm crond avahi-daemon gdm)
In the list of daemons, remove gdm, and add hal.
Then unmount everything and reboot, arch should boot to a console login, where you can then use startx to see if it works properly with hal.
If that works, and you want to boot to an X login (like gdm),
uncomment (delete the #) this line in /etc/inittab
#x:5:respawn:/usr/sbin/gdm -nodaemon
and change
id:3:initdefault:
to
id:5:initdefault:
Then if you ever have a problem again with X not starting, you can add 3 to the kernel boot line (with GRUB or LILO), which will start Arch in runlevel 3, which is console login.
Last edited by theapodan (2009-07-10 23:45:50)
Offline
People forget to install the mouse and keyboard.
pacman -S xf86-input-keyboard
pacman -S xf86-input-mouse
To add on to the above, further down in the inittab there is a few login manager options, just make sure to comment out xdm with a"#" then uncomment GDM.
pink
Last edited by Mr Pink57 (2009-07-11 03:31:29)
Even a broken clock is right twice a day.
Diplomacy without force is like music without instruments.
Offline
Uh, the simple solution to editing the files before going into the X is to add "-- single" or maybe just "single" to the end of the kernel line in GRUB. (If you don't know, you have to press e on the selection, I think, and then e again on the specific line you're editing; just pay attention to the directions/options at the bottom of the screen). This should take you down to single user mode - a mode for editing important config files, etc. before launching into the general use setup. You'll be prompted for your root password. Edit the /etc/rc.conf there,
I'd agree with Mr Pink57, a lot of people (myself included - what hell) forget to install xf86-input-keyboard and xf86-input-mouse. I think this is included in the evdev package, though, so you could just add xf86-input-evdev (I think that's what it's called. Look around a bit.)
Also, welcome to Arch. :-)
Offline
@theapodan What's the benefit of using inittab versus the daemons array other than being able to append 3 to the end of the kernel line? Anything?
Offline
By using inittab, and appending 3 to the bootline, you can boot into console login if X breaks. If you use the daemons array, you wouldn't be able to boot into multiuser (console) login without some hassle.
I can't think of any downsides to using inittab.
Offline
you need to be in single user mode, last I knew all you had to do was add a '1' to the grub line. AFAIK booting to 3 (or was that 5) will run rc.d and launch gdm.
Anyway, using single user mode to add a ! in front of gdm in /etc/rc.conf and rebooting won't hurt anything.
I think this is also why the prefered way to start a login manager is through inittab 5 not as a daemon, even though it's easier
Last edited by jacko (2009-07-11 20:57:38)
Offline
If there's no other way, use the installation cd. When you're logged, mount your disk and rewrite your files. It might be the easiest way.
Offline
Pages: 1