Weblog entry #5 for mindmerge
See all weblog entries made by mindmerge.
#5
getty respawn too fast
Posted by mindmerge on Sat 28 Jul 2007 at 17:47
Long story short... I received a video from a friend regarding Microsoft's keyboardless something or other... I am running an etch/stable desktop for the most part.
Well I decide I would like to watch the movie... I download an xmms win32 codec from testing which prompts for a libc6 upgrade to a cvs version of the package.
I did go ahead and type, "Yes, do as I say!" so it is my bad... but here is the solution I worked out for the havoc I unleashed upon myself.
Once I logged out and attempted to login... I was greeted with an error message similar to the following... "getty id 1 respawn too fast" "stop for 5 minutes".
That last part is not right I am certain I just can't remember the exact verbage... and I am too lazy to give you my google searches I did yesterday... if interested merely type "getty respawn too fast" into google and you will see what I found.
Essentially the methods that I have found thus far on searches have not worked. Some suggested changing /etc/inittab which I did try using knoppix... to no avail. I even attempted using /bin/getty as opposed to /sbin/getty.
In the end the route that ended up fixing the problem was to ssh to the box from another box and using aptitude I installed util-linux (which would not install with the current cvs version of libc6) which promptly gave me a package selection error. I looked at the suggestion which was to remove the previously installed xmms cwin32 codec and downgrade the libc6 package to the etch/stable version.
Pretty simple... unfortunately I had to get to a very remote host that had access via ssh to this particular system. ;-)
Summary:
Gain access to the host, verify that util-linux is installed. Otherwise??? Perhaps a future entry...
Well I decide I would like to watch the movie... I download an xmms win32 codec from testing which prompts for a libc6 upgrade to a cvs version of the package.
I did go ahead and type, "Yes, do as I say!" so it is my bad... but here is the solution I worked out for the havoc I unleashed upon myself.
Once I logged out and attempted to login... I was greeted with an error message similar to the following... "getty id 1 respawn too fast" "stop for 5 minutes".
That last part is not right I am certain I just can't remember the exact verbage... and I am too lazy to give you my google searches I did yesterday... if interested merely type "getty respawn too fast" into google and you will see what I found.
Essentially the methods that I have found thus far on searches have not worked. Some suggested changing /etc/inittab which I did try using knoppix... to no avail. I even attempted using /bin/getty as opposed to /sbin/getty.
In the end the route that ended up fixing the problem was to ssh to the box from another box and using aptitude I installed util-linux (which would not install with the current cvs version of libc6) which promptly gave me a package selection error. I looked at the suggestion which was to remove the previously installed xmms cwin32 codec and downgrade the libc6 package to the etch/stable version.
Pretty simple... unfortunately I had to get to a very remote host that had access via ssh to this particular system. ;-)
Summary:
Gain access to the host, verify that util-linux is installed. Otherwise??? Perhaps a future entry...
Comments on this Entry
Couldn't you just boot in single user mode?
By the way, were you successful in watching the movie? :-)
[ Parent | Reply to this comment ]
Actually, no I did not watch the movie, but no biggie.
I had the same issue when attempting single user mode as I had removed util-linux during the upgrade of libc6 to install the xmms-wma package. I also attempted the fail-safe kernel... eh it was worth a shot. Init was unable to find /sbin/getty.
Arg... in the end it was my fault.
I had the same issue when attempting single user mode as I had removed util-linux during the upgrade of libc6 to install the xmms-wma package. I also attempted the fail-safe kernel... eh it was worth a shot. Init was unable to find /sbin/getty.
Arg... in the end it was my fault.
[ Parent | Reply to this comment ]