linux-apus-devel

2.4.0-test4 problem

[Michel <dae...@st...>]

Using either the 990106 or latest boothack, doesn't boot, just resets the
machine when it should switch to the pm2fb display. Nothing from {boot,d}mesg.

What on earth could cause such strange behaviour?


Michel


-- 
                               Reboot America.
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86, Team *AMIGA*, AUGS

Re: 2.4.0-test4 problem

[<fp...@zu...>]

On Mon, Jul 24, 2000 at 01:07:54PM +0200, Michel Dänzer wrote:
> 
> 
> Using either the 990106 or latest boothack, doesn't boot, just resets the
> machine when it should switch to the pm2fb display. Nothing from {boot,d}mesg.
> 
> What on earth could cause such strange behaviour?

2.4.0-test4 boots for me. At least it did yesterday.
-- 
Frank Petzold, IBM Zurich Research Laboratory, Säumerstrasse 4,
CH-8803 Rüschlikon/Switzerland, Tel.  +41-1-724-84-42  Fax.   +41-1-724-89-56
 Business email: fp...@zu...          Private email: pe...@he...
   The opinions expressed here are mine and not necessarily those of IBM.

Re: 2.4.0-test4 problem

[Roman Z. <zi...@fh...>]

Hi,

> Using either the 990106 or latest boothack, doesn't boot, just resets the
> machine when it should switch to the pm2fb display. Nothing from {boot,d}mesg.
> 
> What on earth could cause such strange behaviour?

What gives 'objdump -p vmlinux'? If you see two program headers, send me
that kernel (bzipped please :) ).

bye, Roman

Re: 2.4.0-test4 problem

[Michel <dae...@st...>]

Roman Zippel wrote:

> > Using either the 990106 or latest boothack, doesn't boot, just resets the
> > machine when it should switch to the pm2fb display. Nothing from
> > {boot,d}mesg.
> >
> > What on earth could cause such strange behaviour?
> 
> What gives 'objdump -p vmlinux'? If you see two program headers, send me
> that kernel (bzipped please :) ).

vmlinux:     file format elf32-powerpc

Program Header:
    LOAD off    0x00010000 vaddr 0xc0000000 paddr 0xc0000000 align 2**16
         filesz 0x001bde90 memsz 0x001fce24 flags rwx

How does that look? What do these values mean?


Michel


-- 
It's not a bug, it's tradition!
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86, Team *AMIGA*, AUGS

Re: 2.4.0-test4 problem

[Roman Z. <zi...@fh...>]

Hi,

> vmlinux:     file format elf32-powerpc
> 
> Program Header:
>     LOAD off    0x00010000 vaddr 0xc0000000 paddr 0xc0000000 align 2**16
>          filesz 0x001bde90 memsz 0x001fce24 flags rwx
> 
> How does that look? What do these values mean?

Hmm, that looks ok. debug=mem gives you nothing? Tried you other boot
options?

bye, Roman

Re: 2.4.0-test4 problem

[Michel <da...@re...>]

Roman Zippel wrote:

> > vmlinux:     file format elf32-powerpc
> >
> > Program Header:
> >     LOAD off    0x00010000 vaddr 0xc0000000 paddr 0xc0000000 align 2**16
> >          filesz 0x001bde90 memsz 0x001fce24 flags rwx
> >
> > How does that look? What do these values mean?
> 
> Hmm, that looks ok. debug=mem gives you nothing? Tried you other boot
> options?

I basically used "debug debug=mem nobats" (and a ramdisk).


Michel


-- 
Therapy is expensive, popping bubble wrap is cheap. You choose.
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86, Team *AMIGA*, AUGS

Re: 2.4.0-test4 problem

[Roman Z. <zi...@fh...>]

Hi,

> I basically used "debug debug=mem nobats" (and a ramdisk).

I never tested with a ramdisk and can you also try without nobats?

bye, Roman

Re: 2.4.0-test4 problem

[Michel <da...@re...>]

Roman Zippel wrote:

> > I basically used "debug debug=mem nobats" (and a ramdisk).
> 
> I never tested with a ramdisk and can you also try without nobats?

I have (supposed a semicolon in front of it in the start script disables it?),
sorry I forgot to mention that.

I'll try without the ramdisk, can't do it before Thursday evening though.


Any 603e users who have succesfully booted a recent kernel?


Michel


-- 
Why drink & drive when you can smoke and fly???
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86, Team *AMIGA*, AUGS

Re: 2.4.0-test4 problem

[Alan B. <al...@ms...>]

hi,

> Any 603e users who have succesfully booted a recent kernel?

by recent you mean the 2.2.10's on linux-apus.sourceforge or do you mean
the 2.4.x test kernels?

alan

Re: 2.4.0-test4 problem

[Michel <dae...@st...>]

Alan Buxey wrote:

> > Any 603e users who have succesfully booted a recent kernel?
> 
> by recent you mean the 2.2.10's on linux-apus.sourceforge or do you mean
> the 2.4.x test kernels?

What do you think? (reading the subject line ;)

Seriously, sorry I wasn't more clear...


Michel


-- 
It's not a bug, it's tradition!
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86, Team *AMIGA*, AUGS