[arch-general] gdm not found when booting into runlevel 5
I already have one instance of Archlinux installed that has xorg, and KDE installed, and from looking at /var/cache/pacman/pkg, I also have gdm installed. Now this instance of Archlinux works fine, and I can login to KDE with no problems. The graphics driver is trident, and according to /etc/X11/xorg.conf, that is the one that is being used. I now have installed another instance of Archlinux (Don't Panic) on a new machine that I've built. Mobo is Asus M2N-X Plus, and has no onboard graphics card, so I installed one with an ati chipset . Booting into Archlinux is ok, and I did a pacman -S xorg, and after that, a startx started the xserver with no problems, apart from the usual crappy display. I then did a pacman -S kde, and a whole bunch of kde stuff was installed, but a reboot, and changing to runlevel 5 just brought me back to the text (runlevel3) login. Looking at my earlier install of Don't Panic, I see that I'd also installed the gdm package, so I installed it on my new install of Don't Panic. Doing a reboot after this, there is no change, and booting up, and appending the kernel line to 5 has no effect, and I still find myself in runlevel 3. Is there some file that I need to edit, in order to use gdm as the display manager? Nigel.
On Thu, Jun 19, 2008 at 2:23 PM, Nigel Henry <cave.dnb2m97pp@aliceadsl.fr> wrote:
I already have one instance of Archlinux installed that has xorg, and KDE installed, and from looking at /var/cache/pacman/pkg, I also have gdm installed. Now this instance of Archlinux works fine, and I can login to KDE with no problems. The graphics driver is trident, and according to /etc/X11/xorg.conf, that is the one that is being used.
I now have installed another instance of Archlinux (Don't Panic) on a new machine that I've built. Mobo is Asus M2N-X Plus, and has no onboard graphics card, so I installed one with an ati chipset .
Booting into Archlinux is ok, and I did a pacman -S xorg, and after that, a startx started the xserver with no problems, apart from the usual crappy display.
I then did a pacman -S kde, and a whole bunch of kde stuff was installed, but a reboot, and changing to runlevel 5 just brought me back to the text (runlevel3) login.
Looking at my earlier install of Don't Panic, I see that I'd also installed the gdm package, so I installed it on my new install of Don't Panic. Doing a reboot after this, there is no change, and booting up, and appending the kernel line to 5 has no effect, and I still find myself in runlevel 3.
Is there some file that I need to edit, in order to use gdm as the display manager?
Nigel.
You need to edit /etc/inittab
Aaron Griffin wrote:
On Thu, Jun 19, 2008 at 2:23 PM, Nigel Henry <cave.dnb2m97pp@aliceadsl.fr> wrote:
Is there some file that I need to edit, in order to use gdm as the display manager?
Nigel.
You need to edit /etc/inittab
Not saying you're wrong, but personally I've never edited the inittab file, and I'm still able to start whatever DM I want. Just adding the appropriate DM (e.g., gdm, kdm, slim, etc.) to the end of the DAEMONS line in rc.conf has always done the trick for me. HTH, DR
David Rosenstrauch wrote:
Aaron Griffin wrote:
On Thu, Jun 19, 2008 at 2:23 PM, Nigel Henry <cave.dnb2m97pp@aliceadsl.fr> wrote:
Is there some file that I need to edit, in order to use gdm as the display manager?
Nigel.
You need to edit /etc/inittab
Not saying you're wrong, but personally I've never edited the inittab file, and I'm still able to start whatever DM I want.
Just adding the appropriate DM (e.g., gdm, kdm, slim, etc.) to the end of the DAEMONS line in rc.conf has always done the trick for me.
HTH,
DR
As stated on the official Arch Linux wiki there is two way of actually doing this: http://wiki.archlinux.org/index.php/Adding_a_login_manager_(KDM%2C_GDM%2C_or... Aaron was refering to the inittab method.
On Thu, Jun 19, 2008 at 2:39 PM, David Rosenstrauch <darose@darose.net> wrote:
Aaron Griffin wrote:
On Thu, Jun 19, 2008 at 2:23 PM, Nigel Henry <cave.dnb2m97pp@aliceadsl.fr> wrote:
Is there some file that I need to edit, in order to use gdm as the display manager?
Nigel.
You need to edit /etc/inittab
Not saying you're wrong, but personally I've never edited the inittab file, and I'm still able to start whatever DM I want.
Just adding the appropriate DM (e.g., gdm, kdm, slim, etc.) to the end of the DAEMONS line in rc.conf has always done the trick for me.
You're correct - I personally don't edit inittab either. I use rc.conf for slim as well. But, his question was regarding "which file to edit", so I figured I'd answer directly.
On Thursday 19 June 2008 21:48, Aaron Griffin wrote:
On Thu, Jun 19, 2008 at 2:39 PM, David Rosenstrauch <darose@darose.net> wrote:
Aaron Griffin wrote:
On Thu, Jun 19, 2008 at 2:23 PM, Nigel Henry
<cave.dnb2m97pp@aliceadsl.fr> wrote:
Is there some file that I need to edit, in order to use gdm as the display manager?
Nigel.
You need to edit /etc/inittab
Not saying you're wrong, but personally I've never edited the inittab file, and I'm still able to start whatever DM I want.
Just adding the appropriate DM (e.g., gdm, kdm, slim, etc.) to the end of the DAEMONS line in rc.conf has always done the trick for me.
You're correct - I personally don't edit inittab either. I use rc.conf for slim as well. But, his question was regarding "which file to edit", so I figured I'd answer directly.
Now I don't remember doing all this stuff on my first install of Archlinux (Don't Panic), but I've just looked at /etc/group in my first install, and copied the gdm line to my new install, as below. gdm:x:1001: Now when I bootup, and appending the kernel line to use runlevel 5, I get the screen for gdm. So far so good. I enter the username, and password, but all i get is a blue screen with a white window which looks like a KDE Konsole in the top left corner. The mouse cursor is stuck in the middle of the screen, and can't be moved. Well don't ask me why, but I've left it for a few minutes with this window showing in the top left corner, then done a ctrl alt backspace, and now the mouse pointer is active on the gdm login screen. I select a session (KDE), enter username, password, and KDE starts up, and is working as it always has done. All a bit mind boggling. I may be speaking too soon, as I havn't rebooted it yet, but I'll come back if there are further problems. Rock n Roll eh!! Nigel.
participants (4)
-
Aaron Griffin
-
Christian Babeux
-
David Rosenstrauch
-
Nigel Henry