Arch Linux

MGu3l

Member

From: Medellín, Colombia

Registered: 2009-12-19

Posts: 109

Re: Quick-init - Boot your arch in 10 seconds

hi.. i just wanted to say that this its a great way to decrease the time of your boot. sadly, i had to.. i guess one would call it "bugs", wich are...

1. prompt in all terminals take about 5-10 seconds to appear, it doesn't matter if it's gnome-terminal, sakura, xterm, or even a console login... first time you open a terminal, takes 5-10 seconds to the prompt to appear

2. scroll up/down in chromium or any browser is kind of laggy... don't know how to describe this, but isn't smooth.

after 3 days thinking why was that happening, i decided to remove quick-init and everything was back to normal

hope that someone could give me a solution for this.. or at least, that this information i provide could be useful to someone

---

"Dream as if you'll live forever, live as if you'll die today" - James Dean

thoughtcrime

Member

Registered: 2008-09-27

Posts: 156

Website

Re: Quick-init - Boot your arch in 10 seconds

I haven't read the thread except for the very first posts. Anyway, quick-init does not work with encrypted root partitions. Once you install it, it will render your system useless until you plug-in a live cd and copy the original init file over the one by quick-init.

---

- blog (about arch and other stuff): http://thoughtyblog.wordpress.com/
- x86_64 user

anonymous_user

Member

Registered: 2009-08-28

Posts: 3,059

Re: Quick-init - Boot your arch in 10 seconds

Anyone with the 2.6.32 kernel using quick-init? Is it working better?

billy_bibbit

Member

Registered: 2009-02-25

Posts: 5

Re: Quick-init - Boot your arch in 10 seconds

Anyone with the 2.6.32 kernel using quick-init? Is it working better?

Before

After

adriano, thanks a lot!

Last edited by billy_bibbit (2010-01-17 16:19:56)

Rednaxela

Member

Registered: 2009-12-28

Posts: 2

Re: Quick-init - Boot your arch in 10 seconds

Awesome stuff! This brings my netbook's boot time from 21 seconds down to 12 seconds without any optimizations other than installing quick-init! I'm going to see how low I can get it to go now. Bootchart seems to show most of the slowness being in GDM/X11 now really.

Primoz

Member

From: Ljubljana-Slovena-EU

Registered: 2009-03-04

Posts: 688

Re: Quick-init - Boot your arch in 10 seconds

I also thank you I got from cca 16-13s to 10-9s.
it really cool. I doubt I could get it faster as it is...

---

Arch x86_64 ATI AMD APU KDE frameworks 5
---------------------------------
Whatever I do, I always end up with something horribly mis-configured.

Jedipottsy

Member

Registered: 2008-05-22

Posts: 18

Re: Quick-init - Boot your arch in 10 seconds

i can't get this to work, on boot i the filesystem check fails, saying

/dev/sda2:
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is correupt, and you might try running e2fsck with an alternative superblock:
      e2fsck -b 8193 <device>

Im using ext4, so how can i modify the script to check for ext4 not ext2?

Thanks

gee

Member

Registered: 2006-11-29

Posts: 313

Re: Quick-init - Boot your arch in 10 seconds

When my / partition gets messed up and need an urgent fsck, the keyboard does not work and I cannot enter my root password... no issue with normal init...

elliott

Member

Registered: 2006-03-07

Posts: 296

Re: Quick-init - Boot your arch in 10 seconds

Does anyone have this working with Qingy? I tried, but Qingy fails to start the first time. It will start if I login then logout, so I assume something necessary isn't starting in time before Qingy comes up.

Feb 22 09:47:31, qingy on tty1, [DEBUG] You chose a screen saver timeout of 5 minutes.
Feb 22 09:47:31, qingy on tty2, [DEBUG] You chose a screen saver timeout of 5 minutes.
Feb 22 09:47:31, qingy on tty2, [DEBUG] You chose a screen power management timeout of 30 minutes.
Feb 22 09:47:31, qingy on tty1, [DEBUG] You chose a screen power management timeout of 30 minutes.
Feb 22 09:47:31, qingy on tty2, [DEBUG] added keybinding: 'win' will switch to left tty...
Feb 22 09:47:31, qingy on tty2, [DEBUG] added keybinding: 'menu' will switch to right tty...
Feb 22 09:47:31, qingy on tty2, [DEBUG] added keybinding: 'ALT-p' will poweroff machine...
Feb 22 09:47:31, qingy on tty2, [DEBUG] added keybinding: 'ALT-r' will reboot machine...
Feb 22 09:47:31, qingy on tty2, [DEBUG] added keybinding: 'ALT-s' will activate screen saver...
Feb 22 09:47:31, qingy on tty2, [DEBUG] added keybinding: 'ALT-z' will put machine to sleep...
Feb 22 09:47:31, qingy on tty2, [DEBUG] added keybinding: 'CTRL-ESC' will revert to text mode...
Feb 22 09:47:31, qingy on tty1, [DEBUG] added keybinding: 'win' will switch to left tty...
Feb 22 09:47:31, qingy on tty1, [DEBUG] added keybinding: 'menu' will switch to right tty...
Feb 22 09:47:31, qingy on tty1, [DEBUG] added keybinding: 'ALT-p' will poweroff machine...
Feb 22 09:47:31, qingy on tty2, [DEBUG] The following logging facilities will be used: FILE CONSOLE 
Feb 22 09:47:31, qingy on tty2, [DEBUG] Session locking is NOT enabled.
Feb 22 09:47:31, qingy on tty1, [DEBUG] added keybinding: 'ALT-r' will reboot machine...
Feb 22 09:47:31, qingy on tty1, [DEBUG] added keybinding: 'ALT-s' will activate screen saver...
Feb 22 09:47:31, qingy on tty1, [DEBUG] added keybinding: 'ALT-z' will put machine to sleep...
Feb 22 09:47:31, qingy on tty1, [DEBUG] added keybinding: 'CTRL-ESC' will revert to text mode...
Feb 22 09:47:31, qingy on tty1, [DEBUG] The following logging facilities will be used: FILE CONSOLE 
Feb 22 09:47:31, qingy on tty1, [DEBUG] Session locking is NOT enabled.
Feb 22 09:47:32, qingy on tty1, [DEBUG] You chose a screen saver timeout of 5 minutes.
Feb 22 09:47:32, qingy on tty1, [DEBUG] You chose a screen power management timeout of 30 minutes.
Feb 22 09:47:32, qingy on tty1, [DEBUG] added keybinding: 'win' will switch to left tty...
Feb 22 09:47:32, qingy on tty1, [DEBUG] added keybinding: 'menu' will switch to right tty...
Feb 22 09:47:32, qingy on tty1, [DEBUG] added keybinding: 'ALT-p' will poweroff machine...
Feb 22 09:47:32, qingy on tty1, [DEBUG] added keybinding: 'ALT-r' will reboot machine...
Feb 22 09:47:32, qingy on tty1, [DEBUG] added keybinding: 'ALT-s' will activate screen saver...
Feb 22 09:47:32, qingy on tty1, [DEBUG] added keybinding: 'ALT-z' will put machine to sleep...
Feb 22 09:47:32, qingy on tty1, [DEBUG] added keybinding: 'CTRL-ESC' will revert to text mode...
Feb 22 09:47:32, qingy on tty1, [DEBUG] The following logging facilities will be used: FILE CONSOLE 
Feb 22 09:47:32, qingy on tty1, [DEBUG] Session locking is NOT enabled.
Feb 22 09:47:32, qingy on tty1, [DEBUG] Native theme resolution is '1024x768'
Feb 22 09:47:32, qingy on tty1, [ERROR] Cannot get console framebuffer resolution!
Feb 22 09:47:32, qingy on tty1, [DEBUG] firing up GUI
Feb 22 09:47:32, qingy-DirectFB on tty1, [DEBUG] You chose a screen saver timeout of 5 minutes.
Feb 22 09:47:32, qingy-DirectFB on tty1, [DEBUG] You chose a screen power management timeout of 30 minutes.
Feb 22 09:47:32, qingy-DirectFB on tty1, [DEBUG] added keybinding: 'win' will switch to left tty...
Feb 22 09:47:32, qingy-DirectFB on tty1, [DEBUG] added keybinding: 'menu' will switch to right tty...
Feb 22 09:47:32, qingy-DirectFB on tty1, [DEBUG] added keybinding: 'ALT-p' will poweroff machine...
Feb 22 09:47:32, qingy-DirectFB on tty1, [DEBUG] added keybinding: 'ALT-r' will reboot machine...
Feb 22 09:47:32, qingy-DirectFB on tty1, [DEBUG] added keybinding: 'ALT-s' will activate screen saver...
Feb 22 09:47:32, qingy-DirectFB on tty1, [DEBUG] added keybinding: 'ALT-z' will put machine to sleep...
Feb 22 09:47:32, qingy-DirectFB on tty1, [DEBUG] added keybinding: 'CTRL-ESC' will revert to text mode...
Feb 22 09:47:32, qingy-DirectFB on tty1, [DEBUG] The following logging facilities will be used: FILE CONSOLE 
Feb 22 09:47:32, qingy-DirectFB on tty1, [DEBUG] Session locking is NOT enabled.
Feb 22 09:47:32, qingy-DirectFB on tty1, [DEBUG] redirected stderr to logging facilities...
Feb 22 09:47:32, qingy-DirectFB on tty1, [ERROR] Unrecoverable DirectFB error: reverting to text mode!
Feb 22 09:47:32, qingy-DirectFB on tty1, [ERROR] This usually means that you have an issue with DirectFB, not with qingy...
Feb 22 09:47:32, qingy-DirectFB on tty1, [ERROR] Most likely you don't have your console framebuffer properly set up.
Feb 22 09:47:32, qingy-DirectFB on tty1, [ERROR] Please turn on DEBUG log level in qingy to see exactly why DirectFB is letting you down.
Feb 22 09:47:32, qingy-DirectFB on tty1, [DEBUG] Starting GUI shutdown...
Feb 22 09:47:32, qingy-DirectFB on tty1, [DEBUG] GUI shutdown complete
Feb 22 09:47:33, qingy on tty1, [DEBUG] GUI exited
Feb 22 09:47:33, qingy on tty1, [DEBUG] GUI failed and no auth data present: reverting to text mode
Feb 22 09:47:33, qingy-DirectFB on tty1, [DEBUG]    ~~~~~~~~~~~~~~~~~~~~~~~~~~| DirectFB 1.4.3 |~~~~~~~~~~~~~~~~~~~~~~~~~~
Feb 22 09:47:34, qingy-DirectFB on tty1, [DEBUG]         (c) 2001-2009  The world wide DirectFB Open Source Community
Feb 22 09:47:34, qingy-DirectFB on tty1, [DEBUG]         (c) 2000-2004  Convergence (integrated media) GmbH
Feb 22 09:47:34, qingy-DirectFB on tty1, [DEBUG]       ----------------------------------------------------------------
Feb 22 09:47:34, qingy-DirectFB on tty1, [DEBUG] (*) DirectFB/Core: Single Application Core. (2010-01-20 07:09) 
Feb 22 09:47:34, qingy-DirectFB on tty1, [DEBUG] (!) Direct/Util: opening '/dev/fb0' and '/dev/fb/0' failed
Feb 22 09:47:34, qingy-DirectFB on tty1, [DEBUG]     --> No such file or directory
Feb 22 09:47:34, qingy-DirectFB on tty1, [DEBUG] (!) DirectFB/FBDev: Error opening framebuffer device!
Feb 22 09:47:34, qingy-DirectFB on tty1, [DEBUG] (!) DirectFB/FBDev: Use 'fbdev' option or set FRAMEBUFFER environment variable.
Feb 22 09:47:34, qingy-DirectFB on tty1, [DEBUG] (!) DirectFB/Core: Could not initialize 'system_core' core!
Feb 22 09:47:34, qingy-DirectFB on tty1, [DEBUG]     --> Initialization error!
Feb 22 09:47:34, qingy-DirectFB on tty1, [DEBUG] stderr logger process shutting down...
Feb 22 09:47:47, qingy on tty1, [DEBUG] Unable to open directory "/etc/X11/Sessions/"
Feb 22 09:47:48, qingy on tty1, [DEBUG] Unable to open directory "/etc/X11/Sessions/"
Feb 22 09:47:48, qingy on tty1, [DEBUG] Starting text session with argument #0: -bash
Feb 22 09:47:54, qingy on tty1, [DEBUG] You chose a screen saver timeout of 5 minutes.
Feb 22 09:47:54, qingy on tty1, [DEBUG] You chose a screen power management timeout of 30 minutes.
Feb 22 09:47:54, qingy on tty1, [DEBUG] added keybinding: 'win' will switch to left tty...
Feb 22 09:47:54, qingy on tty1, [DEBUG] added keybinding: 'menu' will switch to right tty...
Feb 22 09:47:54, qingy on tty1, [DEBUG] added keybinding: 'ALT-p' will poweroff machine...
Feb 22 09:47:54, qingy on tty1, [DEBUG] added keybinding: 'ALT-r' will reboot machine...
Feb 22 09:47:54, qingy on tty1, [DEBUG] added keybinding: 'ALT-s' will activate screen saver...
Feb 22 09:47:54, qingy on tty1, [DEBUG] added keybinding: 'ALT-z' will put machine to sleep...
Feb 22 09:47:54, qingy on tty1, [DEBUG] added keybinding: 'CTRL-ESC' will revert to text mode...
Feb 22 09:47:54, qingy on tty1, [DEBUG] The following logging facilities will be used: FILE CONSOLE 
Feb 22 09:47:54, qingy on tty1, [DEBUG] Session locking is NOT enabled.
Feb 22 09:47:54, qingy on tty1, [DEBUG] You chose a screen saver timeout of 5 minutes.
Feb 22 09:47:54, qingy on tty1, [DEBUG] You chose a screen power management timeout of 30 minutes.
Feb 22 09:47:54, qingy on tty1, [DEBUG] added keybinding: 'win' will switch to left tty...
Feb 22 09:47:54, qingy on tty1, [DEBUG] added keybinding: 'menu' will switch to right tty...
Feb 22 09:47:54, qingy on tty1, [DEBUG] added keybinding: 'ALT-p' will poweroff machine...
Feb 22 09:47:54, qingy on tty1, [DEBUG] added keybinding: 'ALT-r' will reboot machine...
Feb 22 09:47:54, qingy on tty1, [DEBUG] added keybinding: 'ALT-s' will activate screen saver...
Feb 22 09:47:54, qingy on tty1, [DEBUG] added keybinding: 'ALT-z' will put machine to sleep...
Feb 22 09:47:54, qingy on tty1, [DEBUG] added keybinding: 'CTRL-ESC' will revert to text mode...
Feb 22 09:47:54, qingy on tty1, [DEBUG] The following logging facilities will be used: FILE CONSOLE 
Feb 22 09:47:54, qingy on tty1, [DEBUG] Session locking is NOT enabled.
Feb 22 09:47:54, qingy on tty1, [DEBUG] Native theme resolution is '1024x768'
Feb 22 09:47:54, qingy on tty1, [DEBUG] Framebuffer resolution is '800x480'.
Feb 22 09:47:54, qingy on tty1, [DEBUG] firing up GUI
Feb 22 09:47:54, qingy-DirectFB on tty1, [DEBUG] You chose a screen saver timeout of 5 minutes.
Feb 22 09:47:54, qingy-DirectFB on tty1, [DEBUG] You chose a screen power management timeout of 30 minutes.
Feb 22 09:47:54, qingy-DirectFB on tty1, [DEBUG] added keybinding: 'win' will switch to left tty...
Feb 22 09:47:54, qingy-DirectFB on tty1, [DEBUG] added keybinding: 'menu' will switch to right tty...
Feb 22 09:47:54, qingy-DirectFB on tty1, [DEBUG] added keybinding: 'ALT-p' will poweroff machine...
Feb 22 09:47:54, qingy-DirectFB on tty1, [DEBUG] added keybinding: 'ALT-r' will reboot machine...
Feb 22 09:47:54, qingy-DirectFB on tty1, [DEBUG] added keybinding: 'ALT-s' will activate screen saver...
Feb 22 09:47:54, qingy-DirectFB on tty1, [DEBUG] added keybinding: 'ALT-z' will put machine to sleep...
Feb 22 09:47:54, qingy-DirectFB on tty1, [DEBUG] added keybinding: 'CTRL-ESC' will revert to text mode...
Feb 22 09:47:54, qingy-DirectFB on tty1, [DEBUG] The following logging facilities will be used: FILE CONSOLE 
Feb 22 09:47:54, qingy-DirectFB on tty1, [DEBUG] Session locking is NOT enabled.
Feb 22 09:47:54, qingy-DirectFB on tty1, [DEBUG] redirected stderr to logging facilities...
Feb 22 09:47:55, qingy-DirectFB on tty1, [DEBUG] Unable to open directory "/etc/X11/Sessions/"
Feb 22 09:47:55, qingy-DirectFB on tty1, [DEBUG] Found new screen (1 so far): FBDev Primary Screen, has power management support
Feb 22 09:47:55, qingy-DirectFB on tty1, [DEBUG]    ~~~~~~~~~~~~~~~~~~~~~~~~~~| DirectFB 1.4.3 |~~~~~~~~~~~~~~~~~~~~~~~~~~
Feb 22 09:47:55, qingy-DirectFB on tty1, [DEBUG]         (c) 2001-2009  The world wide DirectFB Open Source Community
Feb 22 09:47:55, qingy-DirectFB on tty1, [DEBUG]         (c) 2000-2004  Convergence (integrated media) GmbH
Feb 22 09:47:55, qingy-DirectFB on tty1, [DEBUG]       ----------------------------------------------------------------
Feb 22 09:47:55, qingy-DirectFB on tty1, [DEBUG] (*) DirectFB/Core: Single Application Core. (2010-01-20 07:09) 
Feb 22 09:47:55, qingy-DirectFB on tty1, [DEBUG] (*) Direct/Thread: Started 'VT Flusher' (-1) [DEFAULT OTHER/OTHER 0/0] <8388608>...
Feb 22 09:47:55, qingy-DirectFB on tty1, [DEBUG] (*) DirectFB/FBDev: Found 'inteldrmfb' (ID 0) with frame buffer at 0xd07df000, 1500k (MMIO 0xf7f00000, 512k)
Feb 22 09:47:55, qingy-DirectFB on tty1, [DEBUG] (*) Direct/Modules: suppress module 'linux_input'
Feb 22 09:47:55, qingy-DirectFB on tty1, [DEBUG] (*) Direct/Thread: Started 'Keyboard Input' (-1) [INPUT OTHER/OTHER 0/0] <8388608>...
Feb 22 09:47:55, qingy-DirectFB on tty1, [DEBUG] (*) DirectFB/Input: Keyboard 0.9 (directfb.org)
Feb 22 09:47:55, qingy-DirectFB on tty1, [DEBUG] (*) Direct/Thread: Started 'PS/2 Input' (-1) [INPUT OTHER/OTHER 0/0] <8388608>...
Feb 22 09:47:55, qingy-DirectFB on tty1, [DEBUG] (*) DirectFB/Input: IMPS/2 Mouse 1.0 (directfb.org)
Feb 22 09:47:55, qingy-DirectFB on tty1, [DEBUG] (*) DirectFB/Genefx: MMX detected and enabled
Feb 22 09:47:55, qingy-DirectFB on tty1, [DEBUG] (*) DirectFB/Graphics: MMX Software Rasterizer 0.6 (directfb.org)
Feb 22 09:47:55, qingy-DirectFB on tty1, [DEBUG] (*) DirectFB/Core/WM: Default 0.3 (directfb.org)
Feb 22 09:47:55, qingy-DirectFB on tty1, [DEBUG] (*) Direct/Interface: Loaded 'FT2' implementation of 'IDirectFBFont'.
Feb 22 09:47:55, qingy-DirectFB on tty1, [DEBUG] (*) Direct/Interface: Loaded 'PNG' implementation of 'IDirectFBImageProvider'.
Feb 22 09:48:02, qingy-DirectFB on tty1, [DEBUG] Starting GUI shutdown...
Feb 22 09:48:02, qingy-DirectFB on tty1, [DEBUG] GUI shutdown complete
Feb 22 09:48:02, qingy-DirectFB on tty1, [DEBUG] stderr logger process shutting down...
Feb 22 09:48:02, qingy on tty1, [DEBUG] GUI exited
Feb 22 09:48:02, qingy on tty1, [DEBUG] Unable to open directory "/etc/X11/Sessions/"
Feb 22 09:48:02, qingy on tty1, [DEBUG] Starting text session with argument #0: -bash

Also, despite what the wiki says, Qingy does work with KMS.

Last edited by elliott (2010-02-22 14:51:32)

MascHman

Member

Registered: 2010-05-14

Posts: 1

Re: Quick-init - Boot your arch in 10 seconds

This is great ! However some restarts later all of my USB devices stopped working. The output of "lsusb" prints not a single line :-/

I had to remove this package to get usb working again, 'cause i really need a stable system. But when things run fine again, i will return to this awesome piece of software

Hund

Member

From: Sweden

Registered: 2010-03-22

Posts: 479

Website

Re: Quick-init - Boot your arch in 10 seconds

My HTPC boots 2 sec slower with quick-init and the "Master Front" in alsamixer was always set to "0" and there was no solution to it either.

---

My website

Nimatek

Member

Registered: 2009-09-22

Posts: 25

Re: Quick-init - Boot your arch in 10 seconds

I ran into two issues while testing this.

First, the tty login. When using quick-init there is a delay after typing in the user name and hitting enter, presumably because all the stuff is still loading in the background. Because of this one has to pay attention for the Password prompt to appear and not start typing it right away, otherwise it appears on the screen  which is not a good thing.

The second issue is that switching back and forth between X and tty reliably causes the system to lock up here, not sure what might be the reason. It works fine without quick-init.

Looks interesting though, the boot time is reduced quite a bit. I'll keep an eye on this

choogi

Member

Registered: 2009-10-06

Posts: 60

Re: Quick-init - Boot your arch in 10 seconds

Holy smokes! This package is awesome!

This package brought my boot time down by quite a bit, but I still can't say for sure because I can't get "start X at boot" working on my Intel 965 chipset--has anyone had any success with this?.  It used to work fine with classic init when I configured it following the instructions on the "Start X at Boot" ArchWiki page.  However, now it just loads a log in prompt at the end of boot and waits for me to log in.  When I log in and then execute "startx" I get the following error:

(II) LoadModule: "intel"
(II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
(II) Module intel: vendor="X.Org Foundation"
    compiled for 1.7.4.901, module version = 2.10.0
    Module class: X.Org Video Driver
    ABI class: X.Org Video Driver, version 6.0
(II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
    i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G,
    E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
    965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
    4 Series, G45/G43, Q45/Q43, G41, B43, Clarkdale, Arrandale
(II) Primary Device is: PCI 00@00:02:0
(EE) intel(0): No kernel modesetting driver detected.
(II) UnloadModule: "intel"
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:

On the other hand, if I don't start X at boot (and leave /etc/inittab unmodified), I get a different error.  After everything is booted, all of the boot messages get cleared and all I see is a blinking cursor in the middle of the screen.  I can see text when I type, so I'm able to log in and start X manually, but I can't see any of the boot messages from my daemons, etc.  I've already deleted the escape codes in my /etc/issue long ago.  If it makes a difference, even with classic init, my system used to randomly clear all of my boot messages after loading udev.  This might not have anything to do with quick-init, and if not, then feel free to direct me somewhere else.

arch0r

Member

From: From the Chron-o-John

Registered: 2008-05-13

Posts: 597

Re: Quick-init - Boot your arch in 10 seconds

is there any way to start x at boot? qinit always switches to runlevel 3 even if i set the runlevel to 5 and in the qinittab

ApotheoZ

Member

Registered: 2009-08-10

Posts: 40

Re: Quick-init - Boot your arch in 10 seconds

Work pretty nice on my nc10.
Thank you very much !

deus___

Member

From: Luxembourg

Registered: 2010-06-02

Posts: 2

Re: Quick-init - Boot your arch in 10 seconds

Okay, so this package kinda messed up a lot here.

First of all, after entering INIT Level 3, it went straight to a TTY, remaning there for a few seconds, and starting my Login Manager afterwards (SLiM), which was pretty annoying.
Second of all, my ~/.xinitrc wasn't loaded (I noticed this when I added a command which wasn't executed).
Then, I was unable to uninstall the package. Well, i could use "yaourt -R quick-init", it all went good, but then I was unable to reboot (HAL refused to, and sent me back to a TTY and eventually to my login manager).
Re-Installing quick-init messed up my /etc/rc.conf (some daemons, such as slim, were removed).

If anyone has got an idea how to fully remove quick-init and going back to "before quick-init", I'd be really grateful.

/Edit
Well, apparently my whole rc.conf was reset. :-/

Last edited by deus___ (2010-06-05 07:05:41)

---

"A man can't be too careful in the choice of his enemies." - Oscar Wilde

hash

Member

From: Poland

Registered: 2008-07-31

Posts: 111

Re: Quick-init - Boot your arch in 10 seconds

@deus

If you would read pacman output then you shouldn't have this problems:

Before the reboot you MUST restore the default inittab with:
cp /etc/inittab.original /etc/inittab

I've used quick-init some time ago, and had no problems with uninstalling it.

deus___

Member

From: Luxembourg

Registered: 2010-06-02

Posts: 2

Re: Quick-init - Boot your arch in 10 seconds

Nevermind, I fixed everything manually. Works good now. :-)

Last edited by deus___ (2010-06-06 09:29:22)

---

"A man can't be too careful in the choice of his enemies." - Oscar Wilde

Google

Member

From: Mountain View, California

Registered: 2010-05-31

Posts: 484

Website

Re: Quick-init - Boot your arch in 10 seconds

Ok, so I installed the scripts and now when I try to boot it says check disk failed (and the disk is mounted read only). I can't uninstall the scripts it says 'data base not found' so what can I do?

Google

Member

From: Mountain View, California

Registered: 2010-05-31

Posts: 484

Website

Re: Quick-init - Boot your arch in 10 seconds

nevermind, I figured it out: I had to do this:

$mount -n -o remount,rw /
$cp /etc/inittab.original /etc/inittab

Malstrond

Member

From: Germany

Registered: 2009-06-03

Posts: 98

Re: Quick-init - Boot your arch in 10 seconds

I tried it, sadly it just increases my boottime by 327%.
I have no idea what the hell modprobe is doing during that time. The issue could be the ipw2200 module because it needs to load firmware which is not available yet (but it normally fails instantly) or btrfs, but I don't know enough about it.
With quick-init:

Without quick-init:

Thinkpad X41, stock arch kernel, just a boot into the console.

/Edit:
The problem was indeed the ipw2200 module. It is loaded by modprobe, can't load the firmware yet and fails, but it stays loaded and never reports anything to modprobe which in turn just waits for ip2w200 until some kind of internal timeout until occurs. Pic:

14s is quite impressive for this system. It has a 4000RPM 1.8'' HDD. I barely get 15MB/s sequential I/O. Although I can complete logging in to the VC before KMS kicks in. Lol.:D

Last edited by Malstrond (2010-06-14 22:40:47)

Cookie

Member

Registered: 2008-03-08

Posts: 119

Re: Quick-init - Boot your arch in 10 seconds

I just installed this on my imac and boots up very quickly and loads SLIM without any problem, however I get message below

 swapon: /dev/sda5/ stat failed:  no such file or directory

/dev/sda5 is my swap partition, I can manually activate the swap, is there a reason why  get that message above?

Last edited by Cookie (2010-06-15 00:40:38)

---

Linux nabcake in training...
ArchLinux64

voidzero

Member

Registered: 2007-06-21

Posts: 109

Re: Quick-init - Boot your arch in 10 seconds

Maybe the first line of /etc/qinit.sysinit should show /etc/qinit.sysinit instead of /etc/rc.sysinit..

The_Muh

Member

Registered: 2010-05-21

Posts: 3

Re: Quick-init - Boot your arch in 10 seconds

I installed quick-init today (kernel 2.6.34) and its booting very fast. But: i have to start the alsa-daemon and netcfg manually. alsa is in the daemons-array, netcfg in the rc.local. I dunno why, but i have to wait ~5 seconds before i can use my wlan-device....

i think quick-init does not load the hardware early enough...

//edit: i solved the problem with alsa - i dunno how, but now the alsa-daemon works.

Last edited by The_Muh (2010-06-18 15:59:52)

lilsirecho

Veteran

Registered: 2003-10-24

Posts: 5,000

Re: Quick-init - Boot your arch in 10 seconds

A side note re: boot time.

Calimero has a french archlinux "live" OS which boots with cp2ram, openbox, pacmanfm,midori, wicd, smplayer, avidemux, among many others ....boots to desktop in 15 secs.

It has provision for addons for persistence and has english version capability as well as x86_64.  Download is somewhere near 550mb (can't recall).  Cd or flash.

Kernel is 32 at present.

---

Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit!     X-ray confirms Iam spineless!