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
Processing commands for [EMAIL PROTECTED]:
> submitter 270743 !
Bug#270743: radeonfb cannot detect display panel size and breaks
Changed Bug submitter from Nikolaus Schulz <[EMAIL PROTECTED]> to Nikolaus
Schulz <[EMAIL PROTECTED]>.
> thanks
Stopping processing here.
Please contact me if you nee
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
Package: kernel-image-2.6.8-powerpc
Version: 2.6.8-3
Severity: important
Hello,
booting kernel 2.6.8 on my iBook 2.2 with a Radeon Mobility M7, the
radeonfb driver fails to detect the display panel size, resulting in a
blank screen.
I found some people reporting they could successfully start X
Hi,
Sven Luther writes:
> Yeah, i personally feel that the bootargs patch may not be the best
> solution though, and that
> a recompilation of the incriminated object file in mkvmlinuz,
I already told you this is not acceptable because it requires at least
a complete toolchain on every system,
reassign 261893 gcc-3.3
thanks
* Jan-Jaap van der Heijden wrote:
> On Wed, Sep 01, 2004 at 11:36:09PM +0200, Christoph Hellwig wrote:
> > On Wed, Sep 01, 2004 at 11:33:31PM +0200, Jan-Jaap van der Heijden wrote:
> > > I don't think placing a strategic printk() qualifies as a fix though :-)
> > > M
On Wed, Sep 01, 2004 at 11:36:09PM +0200, Christoph Hellwig wrote:
> On Wed, Sep 01, 2004 at 11:33:31PM +0200, Jan-Jaap van der Heijden wrote:
> > I don't think placing a strategic printk() qualifies as a fix though :-)
> > Maybe GCC is to blame here. I'm using gcc 3.3.4-6sarge1.0.1 (current from
Package: kernel-image-2.6.8-powerpc
Version: 2.6.8-4
Severity: minor
According to Apple documentation, pressing the fn-key plus the keypad
enter key on an iBook is supposed to generate a Menu scancode. But it
doesn't, and the keysym it generates exposes a bug in the X scancode to
keysym conversion
On Wed, Sep 08, 2004 at 11:57:01AM +0200, Jens Schmalzing wrote:
> Hi,
>
> Sven Luther writes:
>
> > Yeah, well, it may be needed in a self compiled kernel from the
> > kernel-source-2.6.8, where the user like to set it, don't you think ?
>
> In fact, I don't.
Well, in fact i faced the problem
Hi,
Sven Luther writes:
> Yeah, well, it may be needed in a self compiled kernel from the
> kernel-source-2.6.8, where the user like to set it, don't you think ?
In fact, I don't.
> So, you advocate shipping a broken command line support on chrp/pmac
> because you are too lazy or uninterested t
Package: kernel-source-2.6.8
Thanks Julien. I now forward this to the kernel-source-2.6.8 package in order
to not lose it in my mail archive.
Friendly,
Sven Luther
On Wed, Sep 08, 2004 at 11:44:56AM +0200, Julien BLACHE wrote:
> Sven Luther <[EMAIL PROTECTED]> wrote:
>
> Hi Sven,
>
> >> Use f
On Wed, Sep 08, 2004 at 11:00:12AM +0200, Jens Schmalzing wrote:
> Hi,
>
> Sven Luther writes:
>
> > Well, no, why ? The patch is a correct fix, which makes the default
> > command line work, do you seriously think it is better to have a
> > broken default commandline on chrp/pmac,
>
> I know fo
Hi,
Sven Luther writes:
> Well, no, why ? The patch is a correct fix, which makes the default
> command line work, do you seriously think it is better to have a
> broken default commandline on chrp/pmac,
I know for sure that the default command line is not needed for
PowerMacs, as one can use a
On Wed, Sep 08, 2004 at 08:28:52AM +0200, Jens Schmalzing wrote:
> Hi,
>
> Sven Luther writes:
>
> > Can you check with giving the root device explicitly with : -r root when
> > creating the initrd ?
>
> Same thing. This is because the -r flag is only used for figuring out
> the necessary modul
Hi,
Sven Luther writes:
> Can you check with giving the root device explicitly with : -r root when
> creating the initrd ?
Same thing. This is because the -r flag is only used for figuring out
the necessary modules.
> Also, if the same problems happens in d-i when you don't specifify
> root=/d
On Wed, Sep 08, 2004 at 07:18:39AM +0200, Jens Schmalzing wrote:
> Hi,
>
> Sven Luther writes:
>
> > Can you provide a full serial log output ?
>
> Sure. It's attached.
Ok, it finds the initrd all right, but fails to mount the root filesystem and
then pivot_root into it. Classical error. So, t
Package: kernel-image-2.6.8-1-k7
Version: 2.6.8-2
Severity: important
Not the worst thing on earth, but the source symlink in
/lib/modules/2.6.8-1-k7 is pointing at the home directory of the person
who built it instead of somewhere in /usr/src or not being there at all.
$ ls -l /lib/modules/2.6
Hi,
Sven Luther writes:
> Can you provide a full serial log output ?
Sure. It's attached.
> Is the panic in question one happening because it doesn't find the
> initrd, or something else ?
It doesn't find the root filesystem if I omit the root option from the
kernel command line.
> How do yo
19 matches
Mail list logo
