16 Aug
2009
16 Aug
'09
9:39 p.m.
Hello all!
I'm just compiling/configuring a 2.6.30.4 vanilla kernel. Only with the
current configuration it won't start.
When I boot and I can choose the kernel and it tries to start, but then the
two LEDs on my keyboard (as in letters and numbers :-) ) start to blink
rhythmically and nothing else happens.
Does anyone of you have some standard ideas of, what to change? I already
tried:
1. The RCU settings
2. disabled tickless system
3. disabled control groups
4. double-checked, that I chose the correct CPU and ACPI settings
Points I'm not sure about are some of the memory options. There are options
to disallow extensive access of /dev/mem, checking for corrupt memory and
something concerning AMI and PHOENIX biosen to have the first 64k of memory.
Those weren't there the last time I made my kernel.
If anyone has helpful hints (not take a look at the screen please! :-) ),
then I'd be _VERY_ grateful!
Kindest regards
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
17 Aug
17 Aug
7:52 a.m.
Julien Claassen wrote:
Hello all!
I'm just compiling/configuring a 2.6.30.4 vanilla kernel. Only with the
current configuration it won't start.
When I boot and I can choose the kernel and it tries to start, but then the
two LEDs on my keyboard (as in letters and numbers :-) ) start to blink
rhythmically and nothing else happens.
Does anyone of you have some standard ideas of, what to change? I already
tried:
1. The RCU settings
2. disabled tickless system
3. disabled control groups
4. double-checked, that I chose the correct CPU and ACPI settings
Points I'm not sure about are some of the memory options. There are options
to disallow extensive access of /dev/mem, checking for corrupt memory and
something concerning AMI and PHOENIX biosen to have the first 64k of memory.
Those weren't there the last time I made my kernel.
If anyone has helpful hints (not take a look at the screen please! :-) ),
then I'd be _VERY_ grateful!
Kindest regards
Julien
Hi, Julien.
A couple of things caught me out on a recent kernel build that may or
may not be relevant to you.
If you are building the kernel the "Debian way" using make-kpkg, you now
have to take the additional step of:
update-initramfs -c -k 2.6.30.4
after installing the kernel deb.
Check that you have an initrd line in your grub menu.lst entry and that
it points to something sensible.
I also discovered that it helps to have the appropriate modules for the
disc drives compiled in! Yes really!
WRT to new config options I accepted the defaults which seems to work fine.
Regards, G.
8:10 a.m.
On Monday 17 August 2009 12:53:52 Garry Ogle wrote:
Julien Claassen wrote:
I think the dpkg -i does this for you.
Hello all!
I'm just compiling/configuring a 2.6.30.4 vanilla kernel. Only with
the current configuration it won't start.
When I boot and I can choose the kernel and it tries to start, but
then the two LEDs on my keyboard (as in letters and numbers :-) ) start
to blink rhythmically and nothing else happens.
Does anyone of you have some standard ideas of, what to change? I
already tried:
1. The RCU settings
2. disabled tickless system
3. disabled control groups
4. double-checked, that I chose the correct CPU and ACPI settings
Points I'm not sure about are some of the memory options. There are
options to disallow extensive access of /dev/mem, checking for corrupt
memory and something concerning AMI and PHOENIX biosen to have the first
64k of memory. Those weren't there the last time I made my kernel.
If anyone has helpful hints (not take a look at the screen please! :-)
), then I'd be _VERY_ grateful!
Kindest regards
Julien
Hi, Julien.
A couple of things caught me out on a recent kernel build that may or
may not be relevant to you.
If you are building the kernel the "Debian way" using make-kpkg, you now
have to take the additional step of:
update-initramfs -c -k 2.6.30.4 after installing the kernel deb.
Check that you have an initrd line in your grub menu.lst entry and that
it points to something sensible.
I also discovered that it helps to have the appropriate modules for the
disc drives compiled in! Yes really!
Are you using the initrd?
Since I have dispensed with this, I must compile in everything necessary to
mount my boot/root file system.
If I use the initrd, then this stuff can be there instead.
WRT to new config options I accepted the defaults which seems to work fine.
Regards, G.
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
8:32 a.m.
Thanks, both of you!
I don't use initrd, haven't done for ages. I suppose, that I have all my
disk drivers in there, although the symbol isn't called something with eide
any longer. :-)
Just now I went over the complete configuration again, changed a few things
here and there and read some more help articles. But at least - of early this
morning- I could be sure, that my ALSA had started before the hanging. I'll
try again now and let's see what comes off it.
Kindest regards
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
9:43 a.m.
> Julien Claassen wrote:
>> Hello all!
>> I'm just compiling/configuring a 2.6.30.4 vanilla kernel. Only with
>> the current configuration it won't start.
>>
>> <snipped>
> Garry Ogle wrote:
>
> If you are building the kernel the "Debian way" using make-kpkg, you now
> have to take the additional step of:
>
> update-initramfs -c -k 2.6.30.4
David Baron wrote:
I think the dpkg -i does this for you.
It used to. Now you need the right options set in
/etc/initramfs-tools/hooks, or it doesn't happen.
Regards, G.
9:56 a.m.
My kernel is running now. Don't know which of the options I got wrong! And
even the friggin' tape is working! Perfect!
Thanks for the help!
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
8:53 a.m.
Julien Claassen wrote:
I'm just compiling/configuring a 2.6.30.4
vanilla kernel. Only with the
current configuration it won't start.
Does anyone of you have some standard ideas of what to change?
Well, you should not change any settings as compared to your previously
working kernel, if possible.
Copy the file .config from the old kernel, then run
yes "" | make oldconfig
to use the default for all new options.
HTH
Clemens
8:56 a.m.
That's a good tip! Thanks Clemens. I'll do that if the next boot fails. That
should get me better results.
Kindest regards
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
5623
days inactive
5624
days old
linux-audio-user@lists.linuxaudio.org
8 comments
4 participants
participants (4)
-
Clemens Ladisch -
David Baron -
Garry Ogle -
Julien Claassen