Hi,
OK, I got a normal boot again, by upgrading udev to 0.087-2 (from
unstable). It appears that the initramfs-tools from unstable also needs
a newer udev. This does make the ide-disk module get loaded and the
machine boots normally now. Of course I still don't know what the
"can't find init" prob
Hi again,
So, the problem I had is mostly solved, I can boot again, so there's no
huge problem anymore. The only problem is that the ide-disk module
isn't loaded automatically (anymore). This worked fine in the past, so,
something must be wrong.
Note that I installed initramfs-tools 0.55b and tha
Hi,
The remaining problem is that everytime I boot now, I get dropped into a busybox shell where I need to do a
modprobe ide-disk
exit
to continue booting.
Otherwise, it can't find /dev/hda6 (my root partition), because there
are no /dev/hd* devices yet (as the ide-disk module has not been loaded
Hi,
THanks for your input, Frans.2006/3/18, Frans Pop <[EMAIL PROTECTED]>:
> error that it can't find /dev/hda6 (and drops into BusyBox). I suppose> this is because /dev hasn't been populated yet...
/dev/hda6 contains your root filesystem, right?
Indeed.
When you are dropped into the shell:- chec
On Friday 17 March 2006 23:34, Manuel Bilderbeek wrote:
> Hey! The problem with the "no init found" is gone! So, the cause was
> in the initrd after all! Altough, it booted a lot further, it still
> didn't complete it: when it wants to mount the root fs, it gives an
> error that it can't find /dev/
Hi,
Following my own idea from the previous mail: I found initramfs-tools
0.55b on p.d.o. and downloaded it in the chroot which I described in
the previous mail. There I installed it and reran the initramfs-tools
update from the very first mail from you and rebooted.
Hey! The problem with the "no
Hi,
Next try: I ran grub-install from the chroot, mounting with -o dev
made this work. I even did an update-grub and got a menu.lst. After
setting it all up, I could indeed select the image and attempt a boot.
But I get exactly the same thing: no init found.
So, it doesn't seem to be a grub probl
Hi,
2006/3/17, maximilian attems <[EMAIL PROTECTED]>:
> [ again keep the bug report on cc,
> last reminder ]
Sorry, I got desperate and forgot all about it.
> the device command is crucial if you have no valid /boot/grub/device.map
> you need to adapt the said device to the device of your syst
Hi,
2006/3/17, maximilian attems <[EMAIL PROTECTED]>:
> the easiest thing for your is to look for your next local debian expert.
I'm afraid that's me :)
> you may have forgotten to install the grub package inside of your chroot.
You explicitly told me to run grub-install from outside the chroot
[ please keep the bug report on cc, or i'll really get angry. ]
On Fri, 17 Mar 2006, Manuel Bilderbeek wrote:
> Should I dpkg -i this package from the chroot and then do the
> update-initramfs line from the original reply you sent to my original bug
> report?
the easiest thing for your is to loo
On Thu, 16 Mar 2006, Manuel Bilderbeek wrote:
>
> 2006/3/15, maximilian attems <[EMAIL PROTECTED]>:
> >
> > > I'll first try with lilo if you can confirm that I should indeed run
> > > udev as you said, ignoring the very strong warning.
> >
> > please use grub if lilo didn't work out.
> >
>
> I
hello manuel,
On Wed, 15 Mar 2006, Manuel Bilderbeek wrote:
> > if lilo doesn't work out for you use from knoppix (adapt to your device)
> > grub-install --root-directory=/mnt/hda1 /dev/hda
>
> I'll first try with lilo if you can confirm that I should indeed run
> udev as you said, ignoring the
Hi,
2006/3/15, maximilian attems <[EMAIL PROTECTED]>:
> ok so that's the bug you hit, it's closed by 0.55b
> lilo doesn't grog that the initd.img changed without beeing rerun
> grub is much friendlier in those regards.
So I've read.
> yes you need
> a) proc from outside the chroot or maybe it's
Hi,
I'm getting rather desperate: would it be useful to do a
apt-get install --reinstall linux-image-2.6.15-1-k7
from the chroot?
2006/3/15, Manuel Bilderbeek <[EMAIL PROTECTED]>:
> Hi again,
>
> Some more info:
>
> 2006/3/15, maximilian attems <[EMAIL PROTECTED]>:
> > if yes fetch 0.55 from inco
Hi again,
Some more info:
2006/3/15, maximilian attems <[EMAIL PROTECTED]>:
> if yes fetch 0.55 from incoming.debian.org or unstable.
Unstable has 0.53c and in incoming.debian.org I only see one file "REPORT".
So, I have no idea how to get it.
--
Grtjs,
Manuel
PS: http://manuel.msxnet.org/
Hi,
2006/3/15, maximilian attems <[EMAIL PROTECTED]>:
> do you use lilo?
Yes I do.
> if yes fetch 0.55 from incoming.debian.org or unstable.
But, will it be able to update my initrd.img via the chroot?
As you have read, I'm having loads of trouble with that.
> did you get dropped to a shell,
Hi
Running the latest Knoppix with a 2.6.12 kernel doesn't help. Please
let me know what I can do to get my system booting again...
Thanks in advance.
--
Grtjs,
Manuel
PS: http://manuel.msxnet.org/
Hi,
I got the same problem again, and it seems it has been caused by yet
another update of initramfs-tools, as there's a 0.53c version in my
/var/cache/apt/archives
The problem is that this time I don't have the other kernel image to
boot. So, I'm writing this from a boot from an old Knoppix cd.
Hi,
maximilian attems wrote:
Anyway, if my kernel image is going to be replaced, while it came from
the linux-image package, does this mean that this kernel package should
be rebuilt with the new initramfs or something?
i don't understand that question.
linux-image generates in postinstall th
On Sun, 26 Feb 2006 19:23:16 +0100
maximilian attems <[EMAIL PROTECTED]> wrote:
> On Sun, 26 Feb 2006, Manuel Bilderbeek wrote:
> > Anyway, if my kernel image is going to be replaced, while it came
> > from the linux-image package, does this mean that this kernel
> > package should be rebuilt wit
On Sun, 26 Feb 2006, Manuel Bilderbeek wrote:
> maximilian attems wrote:
> >please don't drop the bug report out of cc.
>
> OK, the whole world gets to read stupid details on my system. :P
well bug reports are full of that. develepment can't touch all the
possible user interactions.. ;)
> >>D
Hi,
maximilian attems wrote:
please don't drop the bug report out of cc.
OK, the whole world gets to read stupid details on my system. :P
Does this take (temporarily) extra disk space? I only have 8MB left on
my /boot partition.
your boot partition should already contain an /boot/initd.img
On Sun, 26 Feb 2006, Manuel Bilderbeek wrote:
> Hi,
>
> Off the record:
naah,
please don't drop the bug report out of cc.
> maximilian attems wrote:
> >try the following commands
> >update-initramfs -t -u -k 2.6.15-1-k7
>
> Does this take (temporarily) extra disk space? I only have 8MB left o
Processing commands for [EMAIL PROTECTED]:
> tags 354458 moreinfo
Bug#354458: Kernel panic after upgrading initramfs-tools/klibc-utils/libklibc
There were no tags set.
Tags added: moreinfo
> stop
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking
tags 354458 moreinfo
stop
On Sun, Feb 26, 2006 at 03:42:49PM +0100, Manuel Bilderbeek wrote:
> Yesterday my stock kernel 2.6.15-1-k7 booted fine, but today it panics
> with the message that it can't mount the root fs. The 2.6.12 kernel
> which I also still have installed works just fine.
>
> It a
Package: initramfs-tools
Version: 0.52b
Severity: important
Hello,
Yesterday my stock kernel 2.6.15-1-k7 booted fine, but today it panics
with the message that it can't mount the root fs. The 2.6.12 kernel
which I also still have installed works just fine.
It appears that yesterday, in the daily
26 matches
Mail list logo
