| View previous topic :: View next topic |
| Author |
Message |
Xenocide
n00b
Joined: 08 Jan 2003
Posts: 5
|
 Posted: Sat Jan 18, 2003 8:53 pm Post subject: No login on boot |
 |
|
I've been hammering away at this for a couple of weeks now but I've encountered an unexpected result thats proving to be difficult. The installation went smoothly using stage3 and GRP, but on reboot the init scripts halt. It makes it all the way to bringing up local and then halts. It also says something about not finding a fsck.xml or some such but the partitions seem to be fine otherwise. None of the other virtual terminals (alt + f2, etc) bring up a login either.
Boring statistics: AMD k6-2 500Mhz, geforce2 mx 400, 192M RAM.
Any insight would be appreciated. |
|
| Back to top |
|
 |
PT_LAmb
Guru
Joined: 22 Apr 2002
Posts: 332
Location: Lisboa (Lisbon), Portugal
|
| Posted: Sat Jan 18, 2003 9:07 pm Post subject: |
|
|
If you could get the complete error, and of course the last 3 or 4 lines, maybe someone could help you.
Ricardo Cordeiro
_________________
SETI@Home - http://setiathome.ssl.berkeley.edu/ |
|
| Back to top |
|
|
Xenocide
n00b
Joined: 08 Jan 2003
Posts: 5
|
| Posted: Sat Jan 18, 2003 9:17 pm Post subject: |
|
|
There's no error, the init just stops.
| Code: |
* Bringing up eth0 ... [ok]
* some other stuff thats supposed to be here... [ok]
* Bringing up local .... [ok]
|
Thats what it says. We thought it might be the local script so we removed it once and it just did the same thing sans the local message. It just sits there without a login prompt either way. |
|
| Back to top |
|
|
David_Escott
l33t
Joined: 12 Jan 2003
Posts: 952
Location: Boston, MA
|
| Posted: Sun Jan 19, 2003 12:07 am Post subject: |
|
|
| Do you have devfs? because devfs creates the ttys that login needs. I had this before when my devfsd.conf was borked up. |
|
| Back to top |
|
|
Twink
Apprentice
Joined: 06 Dec 2002
Posts: 178
Location: New Zealand
|
| Posted: Sun Jan 19, 2003 3:07 am Post subject: |
|
|
| yeah this problem has happened to me a few times now, keep forgetting to turn line wrap off in nano, so annoying |
|
| Back to top |
|
|
David_Escott
l33t
Joined: 12 Jan 2003
Posts: 952
Location: Boston, MA
|
| Posted: Sun Jan 19, 2003 6:34 am Post subject: |
|
|
alias nano='nano -w'
in your bashrc will save you some trouble in the future with nano linewrapping . |
|
| Back to top |
|
|
Xenocide
n00b
Joined: 08 Jan 2003
Posts: 5
|
| Posted: Sun Jan 19, 2003 11:22 pm Post subject: |
|
|
| Well I reinstalled from scratch being careful about that nano thing and still nothing. My roommate went through several kernel compiles convinced it was a kernel error (I highly doubt it). I'm starting from a stage 3 tarball, is it possible that its bad? |
|
| Back to top |
|
|
David_Escott
l33t
Joined: 12 Jan 2003
Posts: 952
Location: Boston, MA
|
| Posted: Sun Jan 19, 2003 11:36 pm Post subject: |
|
|
| ssh does not need a tty (at least if i remember right maybe someone can correct me) so you might try to get ssh running on your box and then you could shell in to it as see what you find. I assume there isnt anything in the logs |
|
| Back to top |
|
|
magxe
n00b
Joined: 20 Jan 2003
Posts: 5
|
| Posted: Mon Jan 20, 2003 11:05 pm Post subject: |
|
|
| hey folks i got the same problem. unfortunately my laptop isn't responding on ssh. so no idea how i can get gentoo workin! |
|
| Back to top |
|
|
Twink
Apprentice
Joined: 06 Dec 2002
Posts: 178
Location: New Zealand
|
| Posted: Tue Jan 21, 2003 2:05 am Post subject: |
|
|
| use the recovery cd, mount your drives then use chroot to get into it. |
|
| Back to top |
|
|
magxe
n00b
Joined: 20 Jan 2003
Posts: 5
|
| Posted: Tue Jan 21, 2003 3:43 pm Post subject: |
|
|
| it's what i've done. but i don't find any hint why this problem occurs |
|
| Back to top |
|
|
David_Escott
l33t
Joined: 12 Jan 2003
Posts: 952
Location: Boston, MA
|
| Posted: Tue Jan 21, 2003 6:50 pm Post subject: |
|
|
put this in conf.d/start.local
ls -l /dev/tty* > /root/tty.check
Then boot normally, and the go back to the recovery cd just to make sure that the ttys are there.
If they are then chroot yourself into your gentoo system and try to run agetty, and login see if either of those are failing. The only reason I can think that you wouldn't get a login is if agetty can't grab a login (but then again I don't know much about init). |
|
| Back to top |
|
|
David_Escott
l33t
Joined: 12 Jan 2003
Posts: 952
Location: Boston, MA
|
|
| Back to top |
|
|
magxe
n00b
Joined: 20 Jan 2003
Posts: 5
|
| Posted: Wed Jan 22, 2003 10:14 am Post subject: |
|
|
| nop. but i tried your other suggestion.it was as usual. when i start agetty in the chrooted environment i got just a litle help about agetty. |
|
| Back to top |
|
|
Are`awn
n00b
Joined: 02 Feb 2003
Posts: 38
|
| Posted: Thu Feb 06, 2003 4:31 pm Post subject: everything looks right... |
|
|
I am having the same issue on a VIA EPIA-M motherboard with a 933 C3 processor. I am able to login via SSH fine, there just isn't a console. I compiled from stage1, with the following in my /etc/make.conf.
CHOST="i586-pc-linux-gnu"
CFLAGS="-march=i586 -m3dnow -O3 -pipe -fomit-frame-pointer"
CXXFLAGS="-march=i586 -m3dnow -O3 -pipe -fomit-frame-pointer"
I also compiled using distcc. My kernel is gentoo-sources-2.4.19-r10 Looks like agetty is running, here is my ps output:
UID PID PPID C STIME TTY TIME CMD
root 1 0 2 11:10 ? 00:00:05 init
root 2 1 0 11:10 ? 00:00:00 [migration_CPU0]
root 3 1 0 11:10 ? 00:00:00 [keventd]
root 4 1 0 11:10 ? 00:00:00 [kapmd]
root 5 1 0 11:10 ? 00:00:00 [ksoftirqd_CPU0]
root 6 1 0 11:10 ? 00:00:00 [kswapd]
root 7 1 0 11:10 ? 00:00:00 [bdflush]
root 8 1 0 11:10 ? 00:00:00 [kupdated]
root 9 1 0 11:10 ? 00:00:00 [kreiserfsd]
root 33 1 0 11:10 ? 00:00:00 /sbin/devfsd /dev
root 2815 1 0 11:10 ? 00:00:00 metalog [MASTER]
root 2817 2815 0 11:10 ? 00:00:00 metalog [KERNEL]
root 2819 1 0 11:10 ? 00:00:00 /usr/sbin/crond
root 3044 1 0 11:10 ? 00:00:00 /usr/sbin/sshd
root 3056 1 0 11:10 vc/1 00:00:00 /sbin/agetty 38400 tty1 linux
root 3057 1 0 11:10 vc/2 00:00:00 /sbin/agetty 38400 tty2 linux
root 3058 1 0 11:10 vc/3 00:00:00 /sbin/agetty 38400 tty3 linux
root 3059 1 0 11:10 vc/4 00:00:00 /sbin/agetty 38400 tty4 linux
root 3060 1 0 11:10 vc/5 00:00:00 /sbin/agetty 38400 tty5 linux
root 3061 1 0 11:10 vc/6 00:00:00 /sbin/agetty 38400 tty6 linux
root 3062 3044 0 11:10 ? 00:00:00 /usr/sbin/sshd
root 3064 3062 0 11:11 pts/0 00:00:00 -bash
root 3151 3064 0 11:13 pts/0 00:00:00 ps -ef
I did as suggested above, adding the "ls -l /dev/tty* > /root/tty.check" in the /etc/init.d/local, here is the output:
crw-rw-rw- 1 root root 5, 0 Dec 31 1969 /dev/tty
lr-xr-xr-x 1 root root 4 Feb 6 06:10 /dev/tty0 -> vc/0
lr-xr-xr-x 1 root root 4 Feb 6 06:10 /dev/tty1 -> vc/1
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty10 -> vc/10
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty11 -> vc/11
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty12 -> vc/12
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty13 -> vc/13
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty14 -> vc/14
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty15 -> vc/15
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty16 -> vc/16
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty17 -> vc/17
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty18 -> vc/18
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty19 -> vc/19
lr-xr-xr-x 1 root root 4 Feb 6 06:10 /dev/tty2 -> vc/2
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty20 -> vc/20
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty21 -> vc/21
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty22 -> vc/22
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty23 -> vc/23
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty24 -> vc/24
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty25 -> vc/25
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty26 -> vc/26
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty27 -> vc/27
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty28 -> vc/28
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty29 -> vc/29
lr-xr-xr-x 1 root root 4 Feb 6 06:10 /dev/tty3 -> vc/3
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty30 -> vc/30
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty31 -> vc/31
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty32 -> vc/32
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty33 -> vc/33
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty34 -> vc/34
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty35 -> vc/35
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty36 -> vc/36
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty37 -> vc/37
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty38 -> vc/38
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty39 -> vc/39
lr-xr-xr-x 1 root root 4 Feb 6 06:10 /dev/tty4 -> vc/4
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty40 -> vc/40
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty41 -> vc/41
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty42 -> vc/42
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty43 -> vc/43
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty44 -> vc/44
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty45 -> vc/45
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty46 -> vc/46
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty47 -> vc/47
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty48 -> vc/48
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty49 -> vc/49
lr-xr-xr-x 1 root root 4 Feb 6 06:10 /dev/tty5 -> vc/5
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty50 -> vc/50
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty51 -> vc/51
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty52 -> vc/52
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty53 -> vc/53
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty54 -> vc/54
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty55 -> vc/55
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty56 -> vc/56
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty57 -> vc/57
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty58 -> vc/58
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty59 -> vc/59
lr-xr-xr-x 1 root root 4 Feb 6 06:10 /dev/tty6 -> vc/6
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty60 -> vc/60
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty61 -> vc/61
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty62 -> vc/62
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/tty63 -> vc/63
lr-xr-xr-x 1 root root 4 Feb 6 06:10 /dev/tty7 -> vc/7
lr-xr-xr-x 1 root root 4 Feb 6 06:10 /dev/tty8 -> vc/8
lr-xr-xr-x 1 root root 4 Feb 6 06:10 /dev/tty9 -> vc/9
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/ttyS0 -> tts/0
lr-xr-xr-x 1 root root 5 Feb 6 06:10 /dev/ttyS1 -> tts/1
Any ideas ?
thanks |
|
| Back to top |
|
|
mischer
n00b
Joined: 09 Feb 2003
Posts: 16
Location: Goettingen, Germany
|
| Posted: Sun Feb 09, 2003 1:58 pm Post subject: |
|
|
| David_Escott wrote: | | Do you have devfs? because devfs creates the ttys that login needs. I had this before when my devfsd.conf was borked up. |
Hi!
I had exactly the same problem as described above installing gentoo from scratch (from stage1, for the first time ever). Looking for hints in this forum, I found this thread, and I think, the devfs-hint might have been the solution for me:
I had devfs enabled in the kernel, devfsd integrated in the init process, and had not changed the conf file, but it did not work. Then I reconfigured the kernel so as to not only enable devfs-support (as pointed out by the installation guide) but also automatically mount the devfs before entering init. Afterwards it worked! I actually do not know about the devfs so I don't understand why it worked, and maybe there is a better way... but anyways this appears to gave done the trick.
After all, this problem seems to be not so uncommon, so maybe this observation is of some help?
Michael |
|
| Back to top |
|
|
David_Escott
l33t
Joined: 12 Jan 2003
Posts: 952
Location: Boston, MA
|
| Posted: Sun Feb 09, 2003 8:27 pm Post subject: |
|
|
| I was a little confused about your ps output. Did you get that by putting ps -ef >/root/ps.check in the local script? Or was that from when you got the machine booted with the cd? |
|
| Back to top |
|
|
Are`awn
n00b
Joined: 02 Feb 2003
Posts: 38
|
| Posted: Sun Feb 09, 2003 9:32 pm Post subject: ps results |
|
|
Thats from turning on ssh and logging in via ssh. I may not get a login prompt, but I am still able to login via ssh. Another problem I am seeing, that I am not able to shutdown correctly either. I press ctrl-alt-del and I get:
INIT: Switching to runlevel: 6
INIT: Sending Processes the TERM signal
If I do it a couple more times, and the shutdown will progress over a couple more items, ending at:
* Sending all processes the TERM signal ...
where then my system just sits there..... |
|
| Back to top |
|
|
mischer
n00b
Joined: 09 Feb 2003
Posts: 16
Location: Goettingen, Germany
|
| Posted: Sun Feb 09, 2003 10:46 pm Post subject: Re: ps results |
|
|
| Are`awn wrote: | Another problem I am seeing, that I am not able to shutdown correctly either. I press ctrl-alt-del and I get:
INIT: Switching to runlevel: 6
INIT: Sending Processes the TERM signal
If I do it a couple more times, and the shutdown will progress over a couple more items, ending at:
* Sending all processes the TERM signal ...
where then my system just sits there..... |
Was the same with me. After enabling automatic mounting of devfs in kernel options,
all worked fine! (See my posting above.) |
|
| Back to top |
|
|
Are`awn
n00b
Joined: 02 Feb 2003
Posts: 38
|
| Posted: Sun Feb 09, 2003 11:30 pm Post subject: Set to Automatically mount at boot |
|
|
I do have it set to automatically mount at boot. Someone in the gentoo irc also mention to keep /dev/pts, did that to and no luck  [/quote] |
|
| Back to top |
|
|
Are`awn
n00b
Joined: 02 Feb 2003
Posts: 38
|
| Posted: Sun Feb 09, 2003 11:38 pm Post subject: no seems everything is just screwed up |
|
|
| After this last rebuild, I am now unable to even ssh into the box.... I will start from scratch again, from stage 1. Just rebuilding everything from scratch on this C3 933 takes abit of time.... LoL |
|
| Back to top |
|
|
Are`awn
n00b
Joined: 02 Feb 2003
Posts: 38
|
| Posted: Mon Feb 10, 2003 1:55 pm Post subject: My situation resolved. |
|
|
Ok, I rebuilt my EPIA-M C3 933 last night from Stage1. I used the CFLAGS="-march=i586 -m3dnow -O3 -fomit-frame-pointer". After I finally finished my reward was the same result... boot would appear to stop at 'Starting Local'. This time, I could login via SSH. Out of desperation, since my board could be considered funky I tried the 2.4.20-gentoo-r1 kernel (before I was using the 2.4.19-gentoo-r10 kernel). I copied my .config from the 2.4.19 directory to the 2.4.20, and recompiled. After I applied the new kernel, all is well... I now get my console login prompt.
Thanks for all of your help,
Are`awn |
|
| Back to top |
|
|
vers_iq
Apprentice
Joined: 18 May 2002
Posts: 264
|
| Posted: Mon Feb 10, 2003 6:04 pm Post subject: |
|
|
I dont if this will help, which baselayout version u have? If u happenned have 1.8.6.2 installed, try to revert to the previous one.
_________________
"You know the world is going crazy when the best rapper is a white guy, the best golfer is a black guy, the Swiss hold the America's cup, France accusing the US of arrogance and Germany doesn't want to go to war." |
|
| Back to top |
|
|
mpool
n00b
Joined: 16 Dec 2002
Posts: 26
|
| Posted: Mon Feb 10, 2003 8:28 pm Post subject: |
|
|
Do you have symmetric multi-processing support (SMP) enabled in your kernel? That was causing the same no login at boot problem on my machine. (SMP was selected in the default .config.) I disabled it (I think it is under general setup but I'm not booted to linux right now so I can't check). Then I ran into dependency problems when re-compiling so I did:
| Code: | cd /usr/src/linux
cp .config /root/.config
make mrproper
cp /root/.config
make dep && make clean bzImage modules modules_install
|
Then I copied the new kernel over to /boot and ran lilo. Everything works fine for me now!
Madeline |
|
| Back to top |
|
|
mischer
n00b
Joined: 09 Feb 2003
Posts: 16
Location: Goettingen, Germany
|
| Posted: Mon Feb 10, 2003 10:07 pm Post subject: |
|
|
| mpool wrote: | | Do you have symmetric multi-processing support (SMP) enabled in your kernel? That was causing the same no login at boot problem on my machine. (SMP was selected in the default .config.) ... |
Aaah good point. When saying that enabling "automounting of devfs" in my kernel config solved the problem, I actually only suspected this because it was mentioned earlier as possible cause. But in fact I also disabled SMP !!! So we seem to be tracking the problem down. Was SMP the only thing you changed that time?
Michael |
|
| Back to top |
|
|
|
Installing Gentoo
