On Thu, Sep 16, 2004 at 12:09:58AM -0500, Hollis Blanchard wrote:
> On Sep 8, 2004, at 11:20 PM, Jens Schmalzing wrote:
> >
> >Hollis Blanchard writes:
> >
> >>pivot_root: No sKernel panic: Attempted to kill init!
> >>uch file or dire ctory
> >>/sbin/ini<0>Rebooting in 180 seconds..t: 426: cannot o
On Sep 8, 2004, at 11:20 PM, Jens Schmalzing wrote:
Hollis Blanchard writes:
pivot_root: No sKernel panic: Attempted to kill init!
uch file or dire ctory
/sbin/ini<0>Rebooting in 180 seconds..t: 426: cannot open dev/console:
No such file
What kernel command line did you use? Try passing a root opt
Hi,
Hollis Blanchard writes:
> pivot_root: No sKernel panic: Attempted to kill init!
> uch file or dire ctory
> /sbin/ini<0>Rebooting in 180 seconds..t: 426: cannot open dev/console:
> No such file
What kernel command line did you use? Try passing a root option
there, set to wherever you keep y
On Wed, Sep 08, 2004 at 09:10:50PM -0500, Hollis Blanchard wrote:
> On Sep 7, 2004, at 1:29 PM, Jens Schmalzing wrote:
> >
> >Hollis Blanchard writes:
> >
> >>Does this mean the ramdisk is bad?
> >
> >Could well be. You can check its contents with 'fsck.cramfs -v
> >/initrd.img'.
>
> The ramdisk
On Sep 7, 2004, at 1:29 PM, Jens Schmalzing wrote:
Hollis Blanchard writes:
Does this mean the ramdisk is bad?
Could well be. You can check its contents with 'fsck.cramfs -v
/initrd.img'.
The ramdisk seems ok, at least fsck does not complain.
Any way I can get some debug output from it?
On the se
Hi,
Hollis Blanchard writes:
> Does this mean the ramdisk is bad?
Could well be. You can check its contents with 'fsck.cramfs -v /initrd.img'.
> Any way I can get some debug output from it?
On the serial console? Put console=ttyS0 last in the kernel command
line. Then /dev/console will poin
On Sep 6, 2004, at 5:51 PM, Jens Schmalzing wrote:
What I meant is, can you install
kernel-source-2.6.8, configure all drivers needed for bringing up your
root filesystem into the kernel, build that kernel, and boot it.
Works fine.
Does this mean the ramdisk is bad? Any way I can get some debug out
Hi,
Hollis Blanchard writes:
> > Can you try a non-initrd kernel built from Debian sources?
> Kernel panic: VFS: Unable to mount root fs on unknown-block(3,3)
> <0>Rebooting in 180 seconds..
>
> It's missing some drivers that I assume would be present on the
> initrd...
This is bound to happ
On Sep 6, 2004, at 4:38 PM, Jens Schmalzing wrote:
Hollis Blanchard writes:
Steps to reproduce:
1. install kernel-image-2.6.8-powerpc
2. run mkvmlinuz with "do_initrd = Yes" in kernel-img.cnf
3. boot the resulting vmlinuz-2.6.8-powerpc on PReP
[...]
Setting PCI interrupts for a "IBM 7248, PowerSeri
Hi,
Hollis Blanchard writes:
> Steps to reproduce:
> 1. install kernel-image-2.6.8-powerpc
> 2. run mkvmlinuz with "do_initrd = Yes" in kernel-img.cnf
> 3. boot the resulting vmlinuz-2.6.8-powerpc on PReP
[...]
> Setting PCI interrupts for a "IBM 7248, PowerSeries 830/850 (Carolina)"
[...]
> Ker
Package: kernel-image-2.6.8-powerpc
Version: 2.6.8-3
Severity: important
Steps to reproduce:
1. install kernel-image-2.6.8-powerpc
2. run mkvmlinuz with "do_initrd = Yes" in kernel-img.cnf
3. boot the resulting vmlinuz-2.6.8-powerpc on PReP
Results:
loaded at: 00480410 00A51004
relocated to:
11 matches
Mail list logo