On 2005-05-25, Ibrahim Mubarak <[EMAIL PROTECTED]> wrote:
> OK. So I went ahead and downloaded the latest kernel off of kernel.org,
> compiled it and installed it. Still mkinitrd doesn't output the image.
I don't know much about this, but perhaps it's as simple as
"mkinitrd -o /boot/initrd.img".
--- David Jardine <[EMAIL PROTECTED]> wrote:
> On Wed, May 25, 2005 at 11:44:49AM -0700, Ibrahim Mubarak wrote:
> > --- Marty <[EMAIL PROTECTED]> wrote:
> > > I think this is normally done by the command "make modules
> install"
> > > (after
> > > compiling the modules using "make modules." There
Ibrahim Mubarak wrote:
Well, I am not bypassing anything. I am using make-kpkg. I use this
guide http://newbiedoc.sourceforge.net/system/kernel-pkg.html.en
| Sorry. Your mention of grabbing a kernel off of kernel.org is what
threw me off. I had thought you had to use the debian-patched k
On Wed, May 25, 2005 at 11:44:49AM -0700, Ibrahim Mubarak wrote:
> --- Marty <[EMAIL PROTECTED]> wrote:
> > I think this is normally done by the command "make modules install"
> > (after
> > compiling the modules using "make modules." There is a more
> > fundamental
> > issue here, however, regard
--- Phil Dyer <[EMAIL PROTECTED]> wrote:
> I'm guessing that you do have initrd enabled in the kernel?
>
> Block Devices -> RAM Disk Support -> Initial RAM disk (initrd)
>
> phil
Actually, I didn't. I never had it turned on. But I went ahead and got
back to the debien kernel-source package and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ibrahim Mubarak said:
> OK. So I went ahead and downloaded the latest kernel off of kernel.org,
> compiled it and installed it. Still mkinitrd doesn't output the image.
> So I tried to mkinitrd of the running kernel. Still nothing. I am
> guessing it i
Ibrahim Mubarak wrote:
Well, I am not bypassing anything. I am using make-kpkg. I use this
guide http://newbiedoc.sourceforge.net/system/kernel-pkg.html.en
Sorry. Your mention of grabbing a kernel off of kernel.org is what
threw me off. I had thought you had to use the debian-patched kernel
Charles Hallenbeck wrote:
On Wed, 25 May 2005, Marty wrote:
apt-get install make-kpkg;man make-kpkg
I tried to fetch that package, with this result:
hhs48:~# apt-get install make-kpkg
Reading Package Lists... Done
Building Dependency Tree... Done
E: Couldn't find package make-kpkg
I am tra
On Wed, 25 May 2005, Marty wrote:
apt-get install make-kpkg;man make-kpkg
I tried to fetch that package, with this result:
hhs48:~# apt-get install make-kpkg
Reading Package Lists... Done
Building Dependency Tree... Done
E: Couldn't find package make-kpkg
I am tracking unstable through mirr
--- Marty <[EMAIL PROTECTED]> wrote:
> I think this is normally done by the command "make modules install"
> (after
> compiling the modules using "make modules." There is a more
> fundamental
> issue here, however, regarding custom kernels in a debian system,
> which I
> address below.
>
> >
> >
Ibrahim Mubarak wrote:
--- Ibrahim Mubarak <[EMAIL PROTECTED]> wrote:
Hi all,
I am trying to make my custom-compiled 2.6.11 kernel (source package
version 2.6.11-5) bootable. For lilo and since 2.6, i have both
vmlinuz
links and initrd images for my kernels. For some reason, this one is
not goi
--- Ibrahim Mubarak <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I am trying to make my custom-compiled 2.6.11 kernel (source package
> version 2.6.11-5) bootable. For lilo and since 2.6, i have both
> vmlinuz
> links and initrd images for my kernels. For some reason, this one is
> not going through.
Hi all,
I am trying to make my custom-compiled 2.6.11 kernel (source package
version 2.6.11-5) bootable. For lilo and since 2.6, i have both vmlinuz
links and initrd images for my kernels. For some reason, this one is
not going through. I usually end up building the initrd images myself
(I bet som
13 matches
Mail list logo
