|
Home > Archive > Linux Debian support > June 2007 > mkinitrd/yaird in amd64
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
mkinitrd/yaird in amd64
|
|
| Linonut 2007-06-03, 1:13 pm |
| Here's a little knot I'm having. I've been building a new kernel to
replace 2.6.18 (2.6.21.3). I do it by unpacking source, copying the
/boot/config-2.6.18-4-amd64 to .config, doing a quick menuconfig, and
then the make, make modules_install sequence. Then I make an initrd
image using mkinitrd or yaird.
Right now, though, I'm getting kernel panic on startup. I'm also seein
that my new initrd image is about 1 Mb in size, while the old one was
about 5 Mb in size.
Am I missing some key element?
Thanks in advance.
--
There's no place like ~
| |
| Linonut 2007-06-03, 1:13 pm |
| After takin' a swig o' grog, Linonut belched out this bit o' wisdom:
> Here's a little knot I'm having. I've been building a new kernel to
> replace 2.6.18 (2.6.21.3). I do it by unpacking source, copying the
> /boot/config-2.6.18-4-amd64 to .config, doing a quick menuconfig, and
> then the make, make modules_install sequence. Then I make an initrd
> image using mkinitrd or yaird.
>
> Right now, though, I'm getting kernel panic on startup. I'm also seein
> that my new initrd image is about 1 Mb in size, while the old one was
> about 5 Mb in size.
I'm currently using Debian's kernel-package setup to try this build.
I really would prefer to do all the steps manually, though. I like
Debian, but I need to know how to build the kernel manually on other
systems (just because).
--
Windows -- Microsoft's great gavage.
| |
| Darren Salt 2007-06-03, 1:13 pm |
| I demand that Linonut may or may not have written...
> After takin' a swig o' grog, Linonut belched out this bit o' wisdom:
[vbcol=seagreen]
[vbcol=seagreen]
> I'm currently using Debian's kernel-package setup to try this build.
> I really would prefer to do all the steps manually, though. I like Debian,
> but I need to know how to build the kernel manually on other systems (just
> because).
Complete guess, based on the lack of info about the kernel panic...
Check that you have the appropriate IDE or SATA drivers selected. While
you're at it, you should check the firewalling options (if you were using
iptables). In both cases, drivers will have become deselected due to changes
in which options are needed to select them.
--
| Darren Salt | linux or ds at | nr. Ashington, | Toon
| RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army
| + Use more efficient products. Use less. BE MORE ENERGY EFFICIENT.
BASIC is to computer programming as "qwerty" is to typing.
| |
| sk8r-365 2007-06-03, 1:13 pm |
| Linonut said:
<snip>
Gavage? Nice gaff! In many ways I fully agree except for the
"nutritional" aspect.
--
sk8r-365
http://goodbye-microsoft.com/
| |
| Linonut 2007-06-04, 1:14 pm |
| After takin' a swig o' grog, Darren Salt belched out this bit o' wisdom:
> I demand that Linonut may or may not have written...
>
>
> Complete guess, based on the lack of info about the kernel panic...
>
> Check that you have the appropriate IDE or SATA drivers selected. While
> you're at it, you should check the firewalling options (if you were using
> iptables). In both cases, drivers will have become deselected due to changes
> in which options are needed to select them.
I monkeyed with both mkinitrd and yaird, but only got as far as having
the kernel "waiting for /sys/block/sda/dev".
I tried mkinitramfs, and it finally yielded a 5 Mb initrd image, but it
stalled "waiting for root filesystem to become available".
I then explored more deeply in "make menuconfig", and saw that the
sata_nv modules was /not/ selected. I rebuilt, but no go. (I later
realized that I forgot to do the "make modules_install", but ...)
In the meantime, I reconfigured one more time, this time building ext3
and sata_nv /into/ the kernel, and now it all works fine. Should have
done that it the beginning, as this custom kernel is meant only for the
current machine.
Sigh.
--
The computer revolution is over. The computers won.
| |
| AJackson 2007-06-06, 1:14 am |
| On Jun 4, 5:46 pm, Linonut <lino...@bellsouth.net> wrote:
> After takin' a swig o' grog, Darren Salt belched out this bit o' wisdom:
> In the meantime, I reconfigured one more time, this time building ext3
> and sata_nv /into/ the kernel, and now it all works fine. Should have
> done that it the beginning, as this custom kernel is meant only for the
> current machine.
A good place to look for information like this is http://wiki.debian.org/
and http://www.debian-administration.org/
Good luck
| |
| Linonut 2007-06-06, 7:13 am |
| After takin' a swig o' grog, AJackson belched out this bit o' wisdom:
> On Jun 4, 5:46 pm, Linonut <lino...@bellsouth.net> wrote:
>
>
> A good place to look for information like this is http://wiki.debian.org/
> and http://www.debian-administration.org/
I think I had it "solved" (I believe it would have worked for
mkinitramfs, if not for mkinitrd and yaird, if I had remember to
do the "make modules_install"), but builing the drivers into the kernel
is acceptable for what I'm doing.
I did check out a lot of info in the latter URL.
What surprised me was that the configuration of the kernel I installed,
as represented by /boot/config-2.6.18-4-amd64 and /proc/config.gz,
didn't appear to contain the SATA_NV module I needed.
Even following the kernel-package steps and installing the result *.deb
file failed.
I'm going to keep avoid the distro's methods of installing the kernel,
even if I slip up now and then.
--
Tux rox!
| |
| AJackson 2007-06-07, 7:14 pm |
| On Jun 6, 1:25 pm, Linonut <lino...@bellsouth.net> wrote:
> I'm going to keep avoid the distro's methods of installing the kernel,
> even if I slip up now and then.
Why? It doesn't demand a special selection of modules. You could
always add the ones you need, like you do. But it's still better to
make a package and install that. At least I find running it myself get
me much mor problems than doing it th Debian way...
| |
| Linonut 2007-06-08, 1:15 pm |
| After takin' a swig o' grog, AJackson belched out this bit o' wisdom:
> On Jun 6, 1:25 pm, Linonut <lino...@bellsouth.net> wrote:
>
> Why? It doesn't demand a special selection of modules. You could
> always add the ones you need, like you do. But it's still better to
> make a package and install that. At least I find running it myself get
> me much mor problems than doing it th Debian way...
Unfortunately, although I followed the Debian way properly, it did not
work. Maybe because of some problems I didn't know about, in the
..config, until later.
With that final thought in mind, I might revisist the Debian way at some
point.
But the manual way works under Gentoo and Slackware, too, so I still
like it.
--
Tux rox!
|
|
|
|
|