Problem, installing Debian on RS6000 P43-140

2004-09-05 Thread Juergen Braun
Hello,

I have a problem when trying to install Debian on an IBM RS6000 P43-140

I set up a dhcp/tftp Server (Debian stable, x86) and downloaded the file

http://ftp2.de.debian.org/debian/dists/sid/main/installer-powerpc/current/images/powerpc/netboot/vmlinuz-prep.initrd

saved this file as /tftpboot/boot.img and booted the P43 from net. The
box started downloading the boot image, but stopped after 2500 packets
and displays F77 on the LEDs:

RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000
RS/6000

 memory  keyboard network  scsi  speaker   ok
BOOTP S = 1  R = 1
FILE: /tftpboot/boot.img

Load Addr=0x60 Max File Size=0x1000
Packet Count = 2500   

Any hints, what can be wrong?

jaybe


signature.asc
Description: This is a digitally signed message part


Re: Problem, installing Debian on RS6000 P43-140

2004-09-05 Thread Juergen Braun
On Sun, 2004-09-05 at 13:05, nicolas wrote:
> On Sun, 2004-09-05 at 12:47, Juergen Braun wrote:
> > Hello,
> > 
> > I have a problem when trying to install Debian on an IBM RS6000 P43-140
> > 
> > I set up a dhcp/tftp Server (Debian stable, x86) and downloaded the file
> > 
> > http://ftp2.de.debian.org/debian/dists/sid/main/installer-powerpc/current/images/powerpc/netboot/vmlinuz-prep.initrd
> > 
> > saved this file as /tftpboot/boot.img and booted the P43 from net. The
> > box started downloading the boot image, but stopped after 2500 packets
> > and displays F77 on the LEDs:
> > 
> > RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000
> > RS/6000
> > 
> >  memory  keyboard network  scsi  speaker   ok
> > BOOTP S = 1  R = 1
> > FILE: /tftpboot/boot.img
> > 
> > Load Addr=0x60 Max File Size=0x1000
> > Packet Count = 2500   
> > 
> > Any hints, what can be wrong?
> > 
> > jaybe
> 
> Hi,
> 
> the tftp transert can been aborted by an arp request (seen this on a FAS
> on the net). The workaround is to add a static entry for your 7043-140
> 
> arp -s ip_7043-140 mac_7043-140
> 
> I use this and I can netboot my 7043-140. If this works for you, can you
> tell me if the debian installer detects your scsi card and can install
> the right module ? Thanks

It looks that the scsi card isn't detected:
Linux/PPC load: load_ramdisk=1 console=ttyS0
Uncompressing Linux...done.
Now booting the kernel
Total memory = 512MB; using 1024kB for hash table (at c030)
Linux version 2.6.7-powerpc ([EMAIL PROTECTED]) (gcc version 3.3.4 (Debian
1:3.3.4-3)4
PReP architecture
IBM planar ID: 00d5
MPIC at 0xfddc (0x3ddc), length 0x0004 mapped to 0xeffc
On node 0 totalpages: 131072
  DMA zone: 131072 pages, LIFO batch:16
  Normal zone: 0 pages, LIFO batch:1
  HighMem zone: 0 pages, LIFO batch:1
Built 1 zonelists
Kernel command line: load_ramdisk=1 console=ttyS0
OpenPIC Version 1.0 (4 CPUs and 16 IRQ sources) at effc
PID hash table entries: 4096 (order 12: 32768 bytes)
time_init: decrementer frequency = 16.622468 MHz
Console: colour dummy device 80x25
Memory: 511424k available (1656k kernel code, 1088k data, 160k init, 0k
highmem)
Calibrating delay loop... 330.75 BogoMIPS
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
checking if image is initramfs...it isn't (no cpio magic); looks like an
initrd
Freeing initrd memory: 4299k freed
NET: Registered protocol family 16
PCI: Probing PCI hardware
Setting PCI interrupts for a "IBM 43P-140 (Tiger1)"
PCI: Cannot allocate resource region 0 of device :00:0b.0
PCI: Cannot allocate resource region 0 of device :00:0c.0
PCI: Cannot allocate resource region 0 of device :00:10.0
PCI: Cannot allocate resource region 0 of device :00:12.0
Thermal assist unit not available
audit: initializing netlink socket (disabled)
audit(948037132.670:0): initialized
devfs: 2004-01-31 Richard Gooch ([EMAIL PROTECTED])
devfs: boot_options: 0x0
Initializing Cryptographic API
Generic RTC Driver v1.07
Macintosh non-volatile memory driver v1.1
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing
disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
pmac_zilog: 0.6 (Benjamin Herrenschmidt <[EMAIL PROTECTED]>)
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
input: Macintosh mouse button emulation
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
mice: PS/2 mouse device common for all mice
NET: Registered protocol family 2
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 131072 bind 65536)
RAMDISK: Compressed image found at block 0
VFS: Mounted root (cramfs filesystem) readonly.
VFS: Cannot open root device "" or unknown-block(8,3)
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on unknown-block(8,3)
 <0>Rebooting in 180 seconds..

What additional parameter must be specified, that Linux is booting from
the initial ramdisk?
Linux/PPC load: load_ramdisk=1 console=ttyS0

> 
> Nicolas
> 


signature.asc
Description: This is a digitally signed message part


Re: Problem, installing Debian on RS6000 P43-140

2004-09-05 Thread Juergen Braun

> What additional parameter must be specified, that Linux is booting from
> the initial ramdisk?
> Linux/PPC load: load_ramdisk=1 console=ttyS0
Found it myself:
Linux/PPC load: root=/dev/ram load_ramdisk=1 console=ttyS0

Will try now to install, but I guess, that it will fail , cause the scsi
controller hasn't been detected.

jaybe


signature.asc
Description: This is a digitally signed message part


Re: Problem, installing Debian on RS6000 P43-140

2004-09-05 Thread Juergen Braun
On Sun, 2004-09-05 at 14:02, nicolas wrote:
> On Sun, 2004-09-05 at 13:30, Juergen Braun wrote:
> > > What additional parameter must be specified, that Linux is booting from
> > > the initial ramdisk?
> > > Linux/PPC load: load_ramdisk=1 console=ttyS0
> > Found it myself:
> > Linux/PPC load: root=/dev/ram load_ramdisk=1 console=ttyS0
> > 
> > Will try now to install, but I guess, that it will fail , cause the scsi
> > controller hasn't been detected.
> > 
> > jaybe
> 
> With debian installer, the hardware are discovered later, and the boot
> messages like you/copy paste are not important for hardware support.
> Just go through the install process to the detect hardware and partition
> hard drive? You'll see if your card is detected or not
When I choose "guided partitioning", I got this menu, but can't select
any harddisk. So I guess, that the installer hasn't found my scsi
controller.


+ÄÄ+ [!!] Partition disks +ÄÄÄ+
| |
| Disk space to partition:|
| |
|  Manually edit partition table  |
| |
||
| |
+Ä+

BTW, what Debian package do I have to install to get an linux8x8 font
for konsole?

jaybe


signature.asc
Description: This is a digitally signed message part


Re: Problem, installing Debian on RS6000 P43-140

2004-09-05 Thread Juergen Braun
On Sun, 2004-09-05 at 15:37, Jens Schmalzing wrote:
> Hi,
> 
> Juergen Braun writes:
> 
> > It looks that the scsi card isn't detected:
> 
> Support for SCSI hardware is built as modules and will be loaded later
> in the installation process.  Make sure you use a *very* recent d-i
> build, because Bug#263156 has only been fixed a few days ago.
I tried this one:
http://people.debian.org/~luther/d-i/images/2004-09-05/powerpc/netboot/vmlinuz-prep.initrd

After selecting German as language, the console (serial console) stays
blank, LEDs are off, nothing more happens

> 
> Regards, Jens.


signature.asc
Description: This is a digitally signed message part


Re: Problem, installing Debian on RS6000 P43-140

2004-09-07 Thread Juergen Braun
On Mon, 2004-09-06 at 09:25, Sven Luther wrote:
> On Sun, Sep 05, 2004 at 03:19:51PM +0200, Juergen Braun wrote:
> > On Sun, 2004-09-05 at 14:02, nicolas wrote:
> > > On Sun, 2004-09-05 at 13:30, Juergen Braun wrote:
> > > > > What additional parameter must be specified, that Linux is booting 
> > > > > from
> > > > > the initial ramdisk?
> > > > > Linux/PPC load: load_ramdisk=1 console=ttyS0
> > > > Found it myself:
> > > > Linux/PPC load: root=/dev/ram load_ramdisk=1 console=ttyS0
> > > > 
> > > > Will try now to install, but I guess, that it will fail , cause the scsi
> > > > controller hasn't been detected.
> > > > 
> > > > jaybe
> > > 
> > > With debian installer, the hardware are discovered later, and the boot
> > > messages like you/copy paste are not important for hardware support.
> > > Just go through the install process to the detect hardware and partition
> > > hard drive? You'll see if your card is detected or not
> > When I choose "guided partitioning", I got this menu, but can't select
> > any harddisk. So I guess, that the installer hasn't found my scsi
> > controller.
> > 
> > 
> > +ÄÄ+ [!!] Partition disks +ÄÄÄ+
> > | |
> > | Disk space to partition:|
> > | |
> > |  Manually edit partition table  |
> > | |
> > ||
> > | |
> > +Ä+
> > 
> > BTW, what Debian package do I have to install to get an linux8x8 font
> > for konsole?
> 
> This is a known bug in parted, which i am fixing now. Try tomorrows daily
> built, or try out the one from friday/saturday.
I tried
http://people.debian.org/~luther/d-i/images/2004-09-07/powerpc/netboot/vmlinuz-prep.initrd
and
http://people.debian.org/~luther/d-i/images/2004-09-03/powerpc/netboot/vmlinuz-prep.initrd

but no success.

> 
> Friendly,
> 
> Sven Luther
> 


signature.asc
Description: This is a digitally signed message part


Installing Debian on P43-140

2004-09-07 Thread Juergen Braun
On Fri, 2004-09-03 at 07:23, Jens Schmalzing wrote:
> Hi,
> 
> Juergen Braun writes:
> 
> > The stock debian kernel didn't work,
> 
> Which one was that?  Could you try the new 2.6 based debian-installer,
> available for example from
> 
> http://people.debian.org/~luther/d-i/images/daily/powerpc/netboot/>
> 
> and report your success or failure to [EMAIL PROTECTED]
I'm trying the new installer but with no success so far (already maild
to the debian-powerpc mailing list)


But I installed debian with the boot floppy from

 http://www.solinno.co.uk/7043-140/files/2.4.19/zImage.prep-2.4.19
and the root-floppy from

http://ftp2.de.debian.org/debian/dists/woody/main/disks-powerpc/current/prep/images-1.44/root.bin

and this started a debian stable installation.

I also booted the installation with the zImage.prep-2.4.19 floppy and
installed a new kernel kernel-image-2.4.18-powerpc
But can't get the machine to boot from disk

I have the following partitioning:
  Disk Drive: /dev/sda
 Size: 9100369920 bytes
  Heads: 64   Sectors per Track: 32   Cylinders: 8678

NameFlags  Part Type  FS Type  [Label]   
Size (MB)

--
sda1BootPrimary   PPC PReP
Boot2.10
sda2Primary   Linux swap
511.71
sda3Primary   Linux ext3   
4095.74
Pri/Log   Free Space   
4490.01

And tried to install the bootloader with
yabootconfig -r /dev/sda3 -b /dev/sda1

p43:~# yabootconfig -r /dev/sda3 -b /dev/sda1
yaboot is the Linux Loader for PowerPC.  yabootconfig sets up your
system to boy
from your hard disk, without the need for a boot CD, floppy or a network
boot.
Install yaboot bootstrap on /dev/sda1 to boot Linux from /dev/sda3?
[Yes]
Creating a simple /etc/yaboot.conf...
Running mkofboot to make the disk bootable...
mkofboot: Warning: Incompatible version of `nvsetenv', nvram will not be
updated
Done
p43:~#

What's the problem with this error message?
Why isn't the system bootgin from disk? The following boot order is
configured:
floppy
cdrom
disk
network


Thanks
jaybe


signature.asc
Description: This is a digitally signed message part


Re: [rplu] Re: Installing Debian on P43-140

2004-09-08 Thread Juergen Braun
On Wed, 2004-09-08 at 06:40, Jens Schmalzing wrote:
> Hi,
> 
> Juergen Braun writes:
> 
> > debian stable installation [...] kernel-image-2.4.18-powerpc
> 
> The kernel image in this package is an uncompressed ELF file (called
> vmlinux), while you need a compressed kernel image file with PReP boot
> code glued onto it.  Those are typically called vmlinuz or
> zImage.prep.  The one from the boot floppy should do fine; after all,
> it managed to boot your machine for installation.
> 
> > And tried to install the bootloader with
> > yabootconfig -r /dev/sda3 -b /dev/sda1
> [...]
> 
> > What's the problem with this error message?
> 
> > Why isn't the system booting from disk?
> 
> Because you have a PReP machine, and PReP is for real men who don't
> bother with flimsy bootloaders and other fancy stuff.
> 
> In order to get a kernel onto the PReP boot partition, just write it
> there.  The exact command is
> 
>  dd if=/where/you/keep/your/zImage.prep of=/dev/sda1
Works perfect.
I used the image I already booted in the installation mode
http://www.solinno.co.uk/7043-140/files/2.4.19/zImage.prep-2.4.19
and dumped this to /dev/sda1

Now it boots directly from disk!

Thanks

Will continue to test the new debian installer and will create a kernel
directly on my RS6000 box.

> 
> Regards, Jens.


signature.asc
Description: This is a digitally signed message part