2.3.50+vlab mvme bootload

2.3.50+vlab mvme bootload

[David Monro]

Hi.

I've had a shot at booting using your prep bootloader - grabbed the
patch from vlab and dropped it into the bitkeeper 2.3.50 tree. The patch
went in cleanly and the build suceeded.

However it behaves in a strange way. I've only managed to make it
produce any output at all once, and I still don't know what I did to
make it boot that time. Normally it simply sits there and then
eventually goes beep and reboots. Below is the output from the one time
I got any:

Keyboard error 2, using serial console!

Model: IBM PPS Model 6050/6070 (E)
Serial: IBM607055372CD
Processor/Bus frequencies (Hz): 133333333/66666667
Time Base Divisor: 4000
Original MSR: 1030
Original HID0: d000c084
Original R31: 3fb268

PCI: Probing PCI hardware
Configurable PCI resources:
IO Port resources:
   00000000 007fffff 00000100 (@09ff90b8)
     00000000 00000000 40000100 (@09f43198)
       20000000 200000ff 60000101 (@09f43a74)
       01000200 0100021f 60000101 (@09f435a4)
       00001000 00001007 60000101 (@09f4333c)
IO Memory resources:
   00000000 3cffffff 00000200 (@09ff90d4)
     00000000 00000000 40000200 (@09f431b4)
       01000000 01ffffff 60000200 (@09f43cdc)
       013fff00 013fffff 60000200 (@09f43a90)
       02800000 02ffffff 60000200 (@09f4380c)
       00000000 0000001f 60000200 (@09f435c0)
     00000000 00000000 40001200 (@09f431d0)
       000c0000 000c7fff 60007200 (@09f43d84)
       000c0000 000cffff 60007200 (@09f438b4)
       00000000 0000ffff 60007200 (@09f4364c)
Allocation requirements: io=00001000, mem=01a00000
Before actual allocations:
IO Port resources:
   00000000 007fffff 00000100 (@09ff90b8)
     00010000 00010fff 40000100 (@09f43198)
       00000000 000000ff 60000101 (@09f43a74)
       00000000 0000001f 60000101 (@09f435a4)
       00000000 00000007 60000101 (@09f4333c)
IO Memory resources:
   00000000 3cffffff 00000200 (@09ff90d4)
     00000000 018fffff 40000200 (@09f431b4)
       00000000 00ffffff 60000200 (@09f43cdc)
       00000000 007fffff 60000200 (@09f4380c)
       00000000 000000ff 60000200 (@09f43a90)
       00000000 0000001f 60000200 (@09f435c0)
     00000000 000fffff 40001200 (@09f431d0)
       00000000 0000ffff 60007200 (@09f438b4)
       00000000 0000ffff 60007200 (@09f4364c)
       00000000 00007fff 60007200 (@09f43d84)
Allocated PCI resources:
IO Port resources:
   00000000 007fffff 00000100 (@09ff90b8)
     00010000 00010fff 40000100 (@09f43198)
       00010000 000100ff 40000101 (@09f43a74)
       00010100 0001011f 40000101 (@09f435a4)
       00010120 00010127 40000101 (@09f4333c)
IO Memory resources:
   00000000 3cffffff 00000200 (@09ff90d4)
     01000000 028fffff 40000200 (@09f431b4)
       01000000 01ffffff 40000200 (@09f43cdc)
       02000000 027fffff 40000200 (@09f4380c)
       02800000 028000ff 40000200 (@09f43a90)
       02800100 0280011f 40000200 (@09f435c0)
     02900000 029fffff 40001200 (@09f431d0)
       02900000 0290ffff 40007200 (@09f438b4)
       02910000 0291ffff 40007200 (@09f4364c)
       02920000 02927fff 40007200 (@09f43d84)
Calling the emulator.
ROM enabled @2920000
bad signature: 4444.

Linux/PPC load: console=ttyS0 root=/dev/hda5 hda=3079,64,32 hdc=swapdata
-b

Uncompressing the kernel...done
Now building bootinfo...
done
Now booting...
Kernel at 0x00000000, size=0x204024
Initrd at 0x09ff8af8, size=0x0
Boot info 0x00205000, size=0x78
Residual data at 0x00206000
loaded at:     00358050 0036EE70
relocated to:  00800000 00816E20
board data at: 00121FE0 001289EC
relocated to:  00810314 00816D20
zimage at:     00363050 003F0DD0
relocated to:  00817000 008A4D80
avail ram:     00400000 00800000

and then it sat there for a while, then went beep and rebooted.

I assume that the other times it booted it tried to send the output
somewhere other than the serial ports, but it didn't turn up on either
of the video ports. I even tried booting with the keyboard unplugged,
but that didn't work either.

Looks like it is doing some sort of resource reallocation, even if I
have no idea what all the numbers mean yet :-) I assume the 'Calling the
emulator' bit means it tried to execute one of the non-existent video
roms in the system and failed.

I'll try the 2.2.12 one at some point, but my SO is due back from a
business trip tomorrow so hacking productivity will now collapse back to
normal levels :-)

Cheers,

	David

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: 2.3.50+vlab mvme bootload

[Gabriel Paubert]

On Sat, 11 Mar 2000, David Monro wrote:

> Hi.
>
> I've had a shot at booting using your prep bootloader - grabbed the
> patch from vlab and dropped it into the bitkeeper 2.3.50 tree. The patch
> went in cleanly and the build suceeded.
>
> However it behaves in a strange way. I've only managed to make it
> produce any output at all once, and I still don't know what I did to
> make it boot that time. Normally it simply sits there and then
> eventually goes beep and reboots. Below is the output from the one time
> I got any:
>
> Keyboard error 2, using serial console!

Normal, the bootloaderr switches automaticaly to serial console when it
does not find a display _and_ a connected keyboard.

>
> Model: IBM PPS Model 6050/6070 (E)
> Serial: IBM607055372CD
> Processor/Bus frequencies (Hz): 133333333/66666667
> Time Base Divisor: 4000
> Original MSR: 1030
> Original HID0: d000c084
> Original R31: 3fb268
>
> PCI: Probing PCI hardware
> Configurable PCI resources:
[That's how they were originally mapped]
> IO Port resources:
>    00000000 007fffff 00000100 (@09ff90b8)
>      00000000 00000000 40000100 (@09f43198)
>        20000000 200000ff 60000101 (@09f43a74)	<--- too high for Linux
>        01000200 0100021f 60000101 (@09f435a4)
>        00001000 00001007 60000101 (@09f4333c)
> IO Memory resources:
>    00000000 3cffffff 00000200 (@09ff90d4)
>      00000000 00000000 40000200 (@09f431b4)
>        01000000 01ffffff 60000200 (@09f43cdc)
>        013fff00 013fffff 60000200 (@09f43a90)
>        02800000 02ffffff 60000200 (@09f4380c)
>        00000000 0000001f 60000200 (@09f435c0)	<--- disabled
>      00000000 00000000 40001200 (@09f431d0)
>        000c0000 000c7fff 60007200 (@09f43d84)
>        000c0000 000cffff 60007200 (@09f438b4)
>        00000000 0000ffff 60007200 (@09f4364c) <--- disabled
> Allocation requirements: io=00001000, mem=01a00000
[snipped]
> Allocated PCI resources:
[After the alocator has run]
> IO Port resources:
>    00000000 007fffff 00000100 (@09ff90b8)
>      00010000 00010fff 40000100 (@09f43198)
>        00010000 000100ff 40000101 (@09f43a74) <--- SCSI
>        00010100 0001011f 40000101 (@09f435a4) <--- Ethernet
>        00010120 00010127 40000101 (@09f4333c) <--- FireCoral
> IO Memory resources:
>    00000000 3cffffff 00000200 (@09ff90d4)
>      01000000 028fffff 40000200 (@09f431b4)
>        01000000 01ffffff 40000200 (@09f43cdc) <--- 16Mb video RAM (9100)
>        02000000 027fffff 40000200 (@09f4380c) <--- 8Mb video RAM (S3)
>        02800000 028000ff 40000200 (@09f43a90) <--- SCSI
>        02800100 0280011f 40000200 (@09f435c0) <--- Ethernet
>      02900000 029fffff 40001200 (@09f431d0)
>        02900000 0290ffff 40007200 (@09f438b4) <--- ROM
>        02910000 0291ffff 40007200 (@09f4364c) <--- ROM
>        02920000 02927fff 40007200 (@09f43d84) <--- ROM

So far the allocation of PCI resources looks reasonable, quite compact
without clashes...
> Calling the emulator.
> ROM enabled @2920000
> bad signature: 4444.

No problem, the emulator does not find a valid ROM signature and gives up
before trying to execute the ROM BIOS...


>
> Linux/PPC load: console=ttyS0 root=/dev/hda5 hda=3079,64,32 hdc=swapdata
> -b
>
> Uncompressing the kernel...done
> Now building bootinfo...
> done
> Now booting...
> Kernel at 0x00000000, size=0x204024
> Initrd at 0x09ff8af8, size=0x0
> Boot info 0x00205000, size=0x78
> Residual data at 0x00206000

Now the following is strange:

> loaded at:     00358050 0036EE70
> relocated to:  00800000 00816E20
> board data at: 00121FE0 001289EC
> relocated to:  00810314 00816D20
> zimage at:     00363050 003F0DD0
> relocated to:  00817000 008A4D80
> avail ram:     00400000 00800000

these are the messages from the oter bootloader as if it were nested or
something strange. Here is what I get on my machines:
Calling the emulator.
ROM enabled @fc6b0000

Linux/PPC load: console=ttyS0

Uncompressing the kernel...done
Now building bootinfo...
done
Now booting...
Kernel at 0x00000000, size=0x1e72c4
Initrd at 0x00eca000, size=0x0
Boot info 0x001e8000, size=0x4c
Residual data at 0x001e9000
PReP architecture
Total memory = 16MB; using 0kB for hash table (at 00000000)
Linux version 2.3.50 (root@vdevel) (gcc version 2.95.2 19991024 (release/franzo)
) #11 Thu Mar 9 12:09:21 CET 2000
Boot arguments: console=ttyS0

> and then it sat there for a while, then went beep and rebooted.

I don't understand how you got this, but did I mention how to use prepboot
or not ?

select CONFIG_EXPERIMENTAL to make CONFIG_PREPBOOT available. Then take
the zImage in arch/ppc/prepboot prodiced by make zImage. it can be dd'ed
onto a 0x41 type partition or netbooted if your netboot provides residual
data.

> I assume that the other times it booted it tried to send the output
> somewhere other than the serial ports, but it didn't turn up on either
> of the video ports. I even tried booting with the keyboard unplugged,
> but that didn't work either.

Unplugging the keyboard may help with my bootloader since it should
automatically fall back to serial console. Actually if the keyboard was
plugged it might have failed depending on the mode of the video...

> Looks like it is doing some sort of resource reallocation, even if I
> have no idea what all the numbers mean yet :-) I assume the 'Calling the
> emulator' bit means it tried to execute one of the non-existent video
> roms in the system and failed.

It tried, but failed before doing any damage since the signature
did not indicate a valid rom.

	Gabriel.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: 2.3.50+vlab mvme bootload

[David Monro]

Gabriel Paubert wrote:
>
> On Sat, 11 Mar 2000, David Monro wrote:
>
> > Hi.
> >
> > I've had a shot at booting using your prep bootloader - grabbed the
> > patch from vlab and dropped it into the bitkeeper 2.3.50 tree. The patch
> > went in cleanly and the build suceeded.
> >
> > However it behaves in a strange way. I've only managed to make it
> > produce any output at all once, and I still don't know what I did to
> > make it boot that time. Normally it simply sits there and then
> > eventually goes beep and reboots. Below is the output from the one time
> > I got any:
> >
> > Keyboard error 2, using serial console!
>
> Normal, the bootloaderr switches automaticaly to serial console when it
> does not find a display _and_ a connected keyboard.

Yes but the funny thing is, the run where I got output was when I had
the keyboard plugged in. Even unplugging the keyboard didn't get me any
messages agin. I will have to hack it to always use serial console for
now (the '850 has built in video etc).

[pci data, looks OK, removed]

> >
> > Linux/PPC load: console=ttyS0 root=/dev/hda5 hda=3079,64,32 hdc=swapdata
> > -b
> >
> > Uncompressing the kernel...done
> > Now building bootinfo...
> > done
> > Now booting...
> > Kernel at 0x00000000, size=0x204024
> > Initrd at 0x09ff8af8, size=0x0
> > Boot info 0x00205000, size=0x78
> > Residual data at 0x00206000
>
> Now the following is strange:
>
> > loaded at:     00358050 0036EE70
> > relocated to:  00800000 00816E20
> > board data at: 00121FE0 001289EC
> > relocated to:  00810314 00816D20
> > zimage at:     00363050 003F0DD0
> > relocated to:  00817000 008A4D80
> > avail ram:     00400000 00800000

Oops, I cut and pasted too much - this the beginning of the bootloader
messages from the next time I booted. Sorry about that...
>
> these are the messages from the oter bootloader as if it were nested or
> something strange. Here is what I get on my machines:
> Calling the emulator.
> ROM enabled @fc6b0000
>
> Linux/PPC load: console=ttyS0
>
> Uncompressing the kernel...done
> Now building bootinfo...
> done
> Now booting...
> Kernel at 0x00000000, size=0x1e72c4
> Initrd at 0x00eca000, size=0x0
> Boot info 0x001e8000, size=0x4c
> Residual data at 0x001e9000

Mine stops here; I never get to the next line.

> PReP architecture
> Total memory = 16MB; using 0kB for hash table (at 00000000)
> Linux version 2.3.50 (root@vdevel) (gcc version 2.95.2 19991024 (release/franzo)
> ) #11 Thu Mar 9 12:09:21 CET 2000
> Boot arguments: console=ttyS0
>
> > and then it sat there for a while, then went beep and rebooted.
>
> I don't understand how you got this, but did I mention how to use prepboot
> or not ?
>
> select CONFIG_EXPERIMENTAL to make CONFIG_PREPBOOT available. Then take
> the zImage in arch/ppc/prepboot prodiced by make zImage. it can be dd'ed
> onto a 0x41 type partition or netbooted if your netboot provides residual
> data.

I did the above, and dd'd it onto a floppy which seems to work just fine
for other kernels.

I've just rebuilt it to ignore the keyboard and vga, and the bootloader
now prints on the serial port again. But I never get past the following:

Linux/PPC load: console=ttyS0 root=/dev/fd0 load_ramdisk=1

Uncompressing the kernel...done
Now building bootinfo...
done
Now booting...
Kernel at 0x00000000, size=0x204024
Initrd at 0x09ff8918, size=0x0
Boot info 0x00205000, size=0x68
Residual data at 0x00206000


Cheers,
	David

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: 2.3.50+vlab mvme bootload

[Gabriel Paubert]

On Sun, 12 Mar 2000, David Monro wrote:

> Yes but the funny thing is, the run where I got output was when I had
> the keyboard plugged in. Even unplugging the keyboard didn't get me any
> messages agin. I will have to hack it to always use serial console for
> now (the '850 has built in video etc).

Ok, maybe your keyboard controller behaves differently. These beasts are
so weird.

> Oops, I cut and pasted too much - this the beginning of the bootloader
> messages from the next time I booted. Sorry about that...

Ok...

> Mine stops here; I never get to the next line.

That's very unfortunate, this is the most difficult to debug transition
period. As soon as you get a single kernel message,  everything is often
right. Maybe I've busted interrupt controller code on yur machine...

> > I don't understand how you got this, but did I mention how to use prepboot
> > or not ?
> >
> > select CONFIG_EXPERIMENTAL to make CONFIG_PREPBOOT available. Then take
> > the zImage in arch/ppc/prepboot prodiced by make zImage. it can be dd'ed
> > onto a 0x41 type partition or netbooted if your netboot provides residual
> > data.
>
> I did the above, and dd'd it onto a floppy which seems to work just fine
> for other kernels.
>
> I've just rebuilt it to ignore the keyboard and vga, and the bootloader
> now prints on the serial port again. But I never get past the following:
>
> Linux/PPC load: console=ttyS0 root=/dev/fd0 load_ramdisk=1

Did you try witout load_ramdisk ? The strange thing in any case is that
you don't get any message. Try with console=ttyS0 only just in case, but I
suspect sommething else which is probably very stupid like a mismatch
between bootloader and kernel about parameter passing or so but hard to
track from here :-(

When I had this kind or problems, I usually added code to send a single
char to the serial port and looked where it stopped in head.S. If the
video is in text mode this can also be done by writing chars to the
screen. But the kernel at least has to reach the point where BATs are
loaded...

	Gabriel.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/