You are not logged in.
the "problem" is this:
Loading Think3UXGA ....................
or
Loading Think3XGA ....................
takes much longer than
Loading arch ....................
Why takes the own-built-kernel much longer to load than the one that comes with arch?
Did i forgot something in the kernel-configuration? (i dont think there is anything as option there to speed up the kernel-loading-at-boot)
my lilo looks like:
# /etc/lilo.conf
boot=/dev/discs/disc0/disc
default=Think3XGA
timeout=50
lba32
prompt
menu-scheme=Yk:kw
image=/boot/vmlinuz
label=arch
root=/dev/discs/disc0/part2
read-only
vga=791
image=/boot/Think3
label=Think3UXGA
root=/dev/discs/disc0/part2
read-only
vga=884
image=/boot/Think3
label=Think3XGA
root=/dev/discs/disc0/part2
read-only
vga=791
other=/dev/discs/disc0/part1
label=winxp
# End of file
and the funniest thing is:
-rw-r--r-- 1 root root 1706805 Aug 28 07:34 Think3
-rw-r--r-- 1 root root 1821845 Aug 26 00:52 vmlinuz
(Think3 is smaller than the arch)
The impossible missions are the only ones which succeed.
Offline
The default arch kernel is built by makepkg, with the following flags (see makepkg.conf):
CHOST="i686-pc-linux-gnu"
CFLAGS="-march=i686 -O2 -pipe"
CXXFLAGS="-march=i686 -O2 -pipe"
Did you use the same flags for your custom kernels?
Offline
i actually use makepkg to compile it ... so, yes, they are the same ... but i use in config a "Pentium 4" setting ... maybe this can change the flags (but they are also i686 for a P4, arent they?)
as i let the kernel build overnight... i dont watch the output ... now i run the compile again: and i can see CFLAGS and CXXFLAGS in the verbose output ... yes
----------------------
maybe to clear the descrption of the problem (only to check if you understood my horrible english, sorry)
only the loading takes long (about 25s on a P4-2GHz machine) ... the kernel works fine when it loaded --- the arch 2.4.21 loads in about 3 or 4s ... what is much faster
The impossible missions are the only ones which succeed.
Offline
I'm not sure if you are doing this already, but it might be helpful if you take the basic default configs, run makepkg, until it starts compiling, break it out, go into your linux source dir, do
make menuconfig
then only change those options that are different from those in the default arch config. that way it is as close to the default arch config as possible. Save the config file to your /usr/abs/kernels/kernel/config (or whatever the directory is), delete the entire "pkg" dir, and run makepkg again.
Hapy.
Offline
I'm not sure if you are doing this already, but it might be helpful if you take the basic default configs, run makepkg, until it starts compiling, break it out, go into your linux source dir, do
make menuconfig
then only change those options that are different from those in the default arch config. that way it is as close to the default arch config as possible. Save the config file to your /usr/abs/kernels/kernel/config (or whatever the directory is), delete the entire "pkg" dir, and run makepkg again.
Hapy.
yes, since 2.4.20 my kernel-config is based on the original from arch ... and i do exactly the thing you said, only with
make xconfig
:-)
... only the one i download as binary (pacman -S kernel) is fast loading
-> is it only me, or is this in general so?
The impossible missions are the only ones which succeed.
Offline
is it only me, or is this in general so?
I use an own compiled kernel from the scratch with acpi, sis-patches, but I couldn't find any difference in the speed of loading between my own and the original arch-kernel...
Just as a hint, I downloaded the original kernel-source from www.kernel.org, patched it, used the .config from the arch-installation and just activated the sis and acpi options.
Kernel version is 2.4.21
Offline