Re: printer problems and more on Re: Screen corruption on startup 2.4.0-test7

From: James Simmons (jsimmons@acsu.buffalo.edu)
Date: Sat Sep 09 2000 - 07:56:40 EST


> > This would be vgacon, having never figured out if it's even possible
> > to get framebuffers working on the machine.
> >
> > Also, the normal power-saving/screen-saving function of blanking the
> > screen is not working.
> >
> Hello,
>
> More information from /var/log/messages (this is a short extract):
>
> Sep 3 19:09:28 kindling mingetty[10251]: /dev/tty6: cannot open tty:
> No such device
> Sep 3 19:09:28 kindling mingetty[10257]: /dev/tty3: cannot open tty:
> No such device
> Sep 3 19:09:28 kindling mingetty[10250]: /dev/tty5: cannot open tty:
> No such device
> Sep 3 19:09:28 kindling mingetty[10249]: /dev/tty4: cannot open tty:
> No such device
> Sep 3 19:09:28 kindling mingetty[10266]: /dev/tty4: cannot open tty:
> No such device
> Sep 3 19:09:28 kindling mingetty[10268]: /dev/tty4: cannot open tty:
> No such device
> Sep 3 19:09:28 kindling mingetty[10264]: /dev/tty5: cannot open tty:
> No such device
> Sep 3 19:09:28 kindling mingetty[10262]: /dev/tty3: cannot open tty:
> No such device
> Sep 3 19:09:28 kindling mingetty[10260]: /dev/tty6: cannot open tty:
> No such device
> Sep 3 19:09:28 kindling mingetty[10276]: /dev/tty6: cannot open tty:
> No such device
> Sep 3 19:09:28 kindling mingetty[10274]: /dev/tty3: cannot open tty:
> No such device
> Sep 3 19:09:28 kindling mingetty[10270]: /dev/tty4: cannot open tty:
> No such device
> Sep 3 19:09:28 kindling mingetty[10272]: /dev/tty5: cannot open tty:
> No such device
> Sep 3 19:09:28 kindling mingetty[10278]: /dev/tty6: cannot open tty:
> No such device
> Sep 3 19:09:28 kindling mingetty[10286]: /dev/tty6: cannot open tty:
> No such device
> Sep 3 19:09:28 kindling mingetty[10284]: /dev/tty5: cannot open tty:
> No such device
> Sep 3 19:09:28 kindling mingetty[10282]: /dev/tty4: cannot open tty:
> No such device
> Sep 3 19:09:28 kindling mingetty[10280]: /dev/tty3: cannot open tty:
> No such device
> Sep 3 19:09:28 kindling mingetty[10294]: /dev/tty3: cannot open tty:
> No such device
> Sep 3 19:09:28 kindling mingetty[10290]: /dev/tty5: cannot open tty:
> No such device
> Sep 3 19:09:28 kindling mingetty[10296]: /dev/tty3: cannot open tty:
> No such device
> Sep 3 19:09:28 kindling init: Id "3" respawning too fast: disabled
> for 5 minutes
> Sep 3 19:09:28 kindling mingetty[10292]: /dev/tty4: cannot open tty:
> No such device
> Sep 3 19:09:28 kindling mingetty[10288]: /dev/tty6: cannot open tty:
> No such device
> Sep 3 19:09:28 kindling mingetty[10302]: /dev/tty6: cannot open tty:
> No such device
> Sep 3 19:09:28 kindling mingetty[10304]: /dev/tty6: cannot open tty:
> No such device
> Sep 3 19:09:28 kindling init: Id "6" respawning too fast: disabled
> for 5 minutes
> Sep 3 19:09:28 kindling mingetty[10300]: /dev/tty4: cannot open tty:
> No such device
> Sep 3 19:09:28 kindling mingetty[10306]: /dev/tty4: cannot open tty:
> No such device
> Sep 3 19:09:28 kindling init: Id "4" respawning too fast: disabled
> for 5 minutes
> Sep 3 19:09:28 kindling mingetty[10298]: /dev/tty5: cannot open tty:
> No such device
> Sep 3 19:09:28 kindling mingetty[10308]: /dev/tty5: cannot open tty:
> No such device
> Sep 3 19:09:28 kindling mingetty[10310]: /dev/tty5: cannot open tty:
> No such device
> Sep 3 19:09:28 kindling init: Id "5" respawning too fast: disabled
> for 5 minutes

Yipes!! I have seen this happen when /etc/inittab is messed up.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Fri Sep 15 2000 - 21:00:12 EST