This is a bug in the 2.6.30 source. The quick work-around for this is:
update-initramfs -c -k "uname"
"uname" being whatever you've named your custom kernel & do it without
the quotations.
Check to see if there is now an initrd-image file for your kernel in the /
boot directory & if th
On Sun, Jul 19, 2009 at 01:06:51PM +0200, Siggy Brentrup wrote:
> On Sun, Jul 19, 2009 at 01:13 -0700, Don Quixote de la Mancha wrote:
> > Remove just the word "single" and you should be good to go.
> >
> > Don Quixote
>
> Lucky Don Quixote :), obviously you never have been hitten by fsck not
>
> On Sun, Jul 19, 2009 at 01:13 -0700, Don Quixote de la Mancha wrote:
>> On Sat, Jul 18, 2009 at 5:39 AM, Soren Orel wrote:
>> > hmmm.. it works, but I have to hit Ctrl+D at every boot... :D
>>
>> On some of your vmlinux lines in your menu.lst you have the word
>> "single". That boots you into si
> hmmm.. it works, but I have to hit Ctrl+D at every boot... :D
>
> http://img149.imageshack.us/img149/5726/screenshotual.png
>
You got that error using make-kpkg, or just as a general kernel error?
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe
> hmmm.. it works, but I have to hit Ctrl+D at every boot... :D
>
> http://img149.imageshack.us/img149/5726/screenshotual.png
>
You got that error using make-kpkg, or just as a general kernel error?
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe
It only brings up this error message on a VirtualBox machine.. :D
I tried to compile the vanillia kernel on two other machines, and it worked,
booted without error.. :)
The VirtualBox machine was only to try, how it works, thank you!
On Sun, Jul 19, 2009 at 1:06 PM, Siggy Brentrup wrote:
> On Sun
On Sun, Jul 19, 2009 at 01:13 -0700, Don Quixote de la Mancha wrote:
> On Sat, Jul 18, 2009 at 5:39 AM, Soren Orel wrote:
> > hmmm.. it works, but I have to hit Ctrl+D at every boot... :D
>
> On some of your vmlinux lines in your menu.lst you have the word
> "single". That boots you into single-u
On Sat, Jul 18, 2009 at 5:39 AM, Soren Orel wrote:
> hmmm.. it works, but I have to hit Ctrl+D at every boot... :D
On some of your vmlinux lines in your menu.lst you have the word
"single". That boots you into single-user mode, that you exit from by
hitting Ctrl-D.
Remove just the word "single"
hmmm.. it works, but I have to hit Ctrl+D at every boot... :D
http://img149.imageshack.us/img149/5726/screenshotual.png
On Sat, Jul 18, 2009 at 12:00 PM, Siggy Brentrup wrote:
> Sorry that I didn't see this thread earlier.
>
> On Sat, Jul 18, 2009 at 11:17 +0200, Soren Orel wrote:
> > it works!
Sorry that I didn't see this thread earlier.
On Sat, Jul 18, 2009 at 11:17 +0200, Soren Orel wrote:
> it works!
>
> I just forget:
>
> cp arch/x86/boot/bzImage /boot/vmlinuz-2.6.30-1
>
>
> and:
> mkinitramfs -o /boot/initrd.img-2.6.30-1 2.6.30.1
% apt-get install kernel-package
% man make-kpk
it works!
I just forget:
cp arch/x86/boot/bzImage /boot/vmlinuz-2.6.30-1
and:
mkinitramfs -o /boot/initrd.img-2.6.30-1 2.6.30.1
and to edit grub:
title kernel 2.6.30.1-barminev
root (hd0,1)
kernel /vmlinuz-2.6.30-1 root=/dev/hda2 ro
initrd /initrd.img-2.6.30-1
thank you!!! alias köszi! :D
O
Aioanei Rares wrote:
mkinitrd is a standard command on all linux systems, so you can check
its manual page. Maybe man update-initramfs can help too. Best of
luck.
On 7/17/09, Don Quixote de la Mancha wrote:
In your Grub menu.lst file, there are some lines that look like this one:
initrd
mkinitrd is a standard command on all linux systems, so you can check
its manual page. Maybe man update-initramfs can help too. Best of
luck.
On 7/17/09, Don Quixote de la Mancha wrote:
> In your Grub menu.lst file, there are some lines that look like this one:
>
> initrd /initrd.img-2
In your Grub menu.lst file, there are some lines that look like this one:
initrd /initrd.img-2.6.26-2-686
You need a line like that just below the item for the kernel you're
trying to boot, except that you want the initrd version to match the
new kernel version.
initrd stands for Init
thank you for the quick replies :O
I just only did, what I mentioned in the starting mail:S
ls -la /boot:
http://pastebin.com/f7dc58737
cat /boot/grub/menu.lst
http://pastebin.com/f566152fc
On Fri, Jul 17, 2009 at 9:11 PM, Don Quixote de la Mancha <
quix...@dulcineatech.com> wrote:
> Did you b
Did you build and install your initrd? You might need to load a
module to mount your root filesystem, and if so it should be in the
initrd.
The initrd also needs to be named in your grub entry.
It's not enough just to build and install the module, because those
are accessible only after your roo
trying in single mode:
http://img514.imageshack.us/img514/7868/screenshotsrf.png
trying in normal mode:
http://img219.imageshack.us/img219/6290/screenshot1u.png
I forget to tell, that this pc uses lvm :S
On Fri, Jul 17, 2009 at 8:59 PM, Aioanei Rares wrote:
> Soren Orel wrote:
>
>> debian lenny
Soren Orel wrote:
debian lenny
I download 2.6.30-1 source
tar -xjf linux-2.6.30.1.tar.bz2
cd linux-2.6.30.1
cp /boot/config-2.6.26-2-686 ./.config
apt-get install make gcc libncurses5-dev
make menuconfig (replace M to *):
Device Drivers - Multiple device support (RAID and LVM) - Device
mapper
debian lenny
I download 2.6.30-1 source
tar -xjf linux-2.6.30.1.tar.bz2
cd linux-2.6.30.1
cp /boot/config-2.6.26-2-686 ./.config
apt-get install make gcc libncurses5-dev
make menuconfig (replace M to *):
Device Drivers - Multiple device support (RAID and LVM) - Device mapper
support
File systems
19 matches
Mail list logo
