Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#21634 - Using once in innittab prevent X from starting correctly

Attached to Project: Arch Linux
Opened by Thomas Courbon (thcourbon) - Monday, 08 November 2010, 09:14 GMT
Last edited by Jan de Groot (JGC) - Tuesday, 09 November 2010, 08:20 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
According to the Arch wiki you can speed up your boot process by using "once" instead of "wait" as the action keyword on several place into /etc/inittab.

replacing the line :
rm:2345:wait:/etc/rc.multi

by:
rm:2345:once:/etc/rc.multi

leads (me ?) to a screen that goes in sleep mode when booting while complaining that "No detected signal". Further investigations (bringing a tty wake the screen) show that the following error is repported (twice) at the end of dmesg :
[drm:output_poll_execute] *ERROR* delayed enqueue failed -125


Additional info:
* packages version:
kernel 2.6.35.8-1
mesa 7.8.3-2 (and all its companion packages)
xf86-video-ati 6.13.2-1 (I have a hd5770 video card)
xorg 1.9.2-1

GRUB2 1.98-5

* config and/or log files :
I use GRUB2, a GPT partitioning scheme. For what's left, I just installed arch from scratch on a brand new SSD following the beginner's guide, official Archlinux install guide and wiki articles. So as this was my first attempt to tinker the system, nothing special.



Steps to reproduce:
Replace wait by once in the inittab's line in question, reboot. the system will hang each time.

This task depends upon

Closed by  Jan de Groot (JGC)
Tuesday, 09 November 2010, 08:20 GMT
Reason for closing:  Won't fix
Comment by Jan de Groot (JGC) - Monday, 08 November 2010, 23:29 GMT
Ah, so you decide to skip execution of rc.multi and start X while the system is booting. I don't think that's a normal supported configuration, as rc.multi needs to do quite some things on your system before X can be started.

Loading...