Boot problem [IBM Intellistation POWER 9114-275]

Shined · **Joined:** 17 Oct 2009, 14:57 **Posts:** 2

Hi,
As far as I can tell I have followed the install instructions for 2.5a correctly but im having a boot issue when yaboot tries to start up.
I configured my HD sda as follows
SDA1: Prep partition ( or chrp or whatever its called )
SDA2: 4 Gig Linux partition
SDA3: 28Gig Linux partition
SDA4: 4.4Gig Swap partition

I then followed the instructions and on reboot the system bios equivilent was able to detect the SCSI hard drive where it could not before and it designated it U0.1-P1/Z1-A3,0.

But when i try and boot I get the following when i try from yaboot which loads successfuly of partition 1.

I type in to the boot: prompt

U0.1-P1/Z1-A3,0:2/etc/yaboot.conf OR
device=U0.1-P1/Z1-A3,0 partition=2 file=/etc/yaboot.conf

and i get this.
Please wait, loading kernel...
U0.1-P1/Z1-A3,0:2,vmlinux unable to open file, invalid device.

What am I doing wrong. And what should I have in /etc/yaboot.conf

Cheers in advance

acrux · **Posted:** 18 Oct 2009, 01:31

i can understand you are talking about CRUX PPC 2.5a (64 bit) on a POWER machine equipped with a first 36GB SCSI disk drive.

that's from CRUX PPC 2.5 Handbook:

Code:

[Note] If you're using an IBM RS/6000 or iSeries/pSeries computer, creating PC-Style partition table is recommended; cfdisk or fidks are suitable for this. You will need a special PReP Boot partition (type 41) of 8 megabytes.

Code:

On IBM RS/6000 and pSeries computers, edit /etc/yaboot.conf to boot the kernel you just compiled and type dd if=/usr/lib/yaboot/yaboot.chrp of=/dev/sd?? where sd?? is the device corresponding to the disk and PReP Boot partition.
[Note] Remember that where /etc/yaboot.conf resides must be the first Ext2fs formatted partition available on your disk. 

It means you need to do a low-level copy of yaboot.chrp into your PReP partition and put your bootkernel and /etc/yaboot.conf into your first ext2fs formatted partition.

E.g. /dev/sda3 as boot partition with ext2 filesystem:

Code:

Disk /dev/sda: 73.4 GB, 73407820800 bytes
128 heads, 32 sectors/track, 35003 cylinders
Units = cylinders of 4096 * 512 = 2097152 bytes
Disk identifier: 0x416a4baa

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1           5       10224   41  PPC PReP Boot
/dev/sda2               6         518     1050624   82  Linux swap / Solaris
/dev/sda3             519         583      133120   83  Linux
/dev/sda4             584       35003    70492160    5  Extended
/dev/sda5             584        5704    10487792   83  Linux
/dev/sda6            5705       35003    60004336   83  Linux

Code:

Filesystem    Type    Size  Used Avail Use% Mounted on
/dev/sda5 reiserfs     11G  2.5G  7.6G  25% /
/dev/sda6 reiserfs     58G  9.4G   48G  17% /home
/tmp         tmpfs    2.0G   14M  2.0G   1% /tmp
shm          tmpfs    2.0G     0  2.0G   0% /dev/shm
/dev/sda3     ext2    126M   37M   83M  31% /boot

Code:

root@power4:/home/acrux# ls -laR /boot
total 36013
drwxr-xr-x  4 root root     1024 Oct 10 22:28 .
drwxr-xr-x 20 root root      464 May 30 15:11 ..
-rw-r--r--  1 root root  1927086 Oct  4 14:43 System.map-2.6.30.8
-rw-r--r--  1 root root  1859378 Oct 10 22:58 System.map-2.6.31.3
-rw-r--r--  1 root root    40491 Oct  4 14:43 config-2.6.30.8
-rw-r--r--  1 root root    43607 Oct 10 22:58 config-2.6.31.3
drwxr-xr-x  2 root root     1024 Oct 10 22:28 etc
drwx------  2 root root    12288 May  6 19:40 lost+found
-rwxr-xr-x  1 root root 11090884 Oct  4 14:45 vmlinux-2.6.30.8
-rwxr-xr-x  1 root root 10041527 Oct 10 22:58 vmlinux-2.6.31.3
lrwxrwxrwx  1 root root       16 Oct 10 22:28 vmlinuz -> vmlinux-2.6.31.3
-rw-r--r--  1 root root      140 May  9 09:48 yaboot.msg

/boot/etc:
total 3
drwxr-xr-x 2 root root 1024 Oct 10 22:28 .
drwxr-xr-x 4 root root 1024 Oct 10 22:28 ..
-rw-r--r-- 1 root root  529 Oct 10 22:28 yaboot.conf

/boot/lost+found:
total 13
drwx------ 2 root root 12288 May  6 19:40 .
drwxr-xr-x 4 root root  1024 Oct 10 22:28 ..

Code:

root@power4:/home/acrux# cat /boot/etc/yaboot.conf
#
# yaboot-1.3.14 on pSeries 9114-275 (2-way POWER4+)
#

device=/pci@400000000110/pci@2,4/pci1069,b166@1/scsi@0/sd@3,0
partition=3
nonvram

message=/yaboot.msg
delay=10

timeout=30
default=crux

image=/vmlinuz
        label=crux
        root=/dev/sda5
        append="video=gxt4500"
        read-only

image=/vmlinuz
        label=crux-ttyS0,9600
        root=/dev/sda5
        append="console=ttyS0,9600"
        read-only

image=/vmlinux-2.6.30.8
        label=old
        root=/dev/sda5
        read-only

enablecdboot
enableofboot
enablenetboot

# EOF

Then, if you want a reiserfs root filesystem (like in my example) you are obliged to make a first ext2fs boot partition where to put your /etc/yaboot.conf and eventually your bootkernel.

Shined · **Joined:** 17 Oct 2009, 14:57 **Posts:** 2

I understand what you have done and yes its what ive done baring this.

I have not yaboot.conf in my /etc directory to edit.

in your yaboot.conf file

#
# yaboot-1.3.14 on pSeries 9114-275 (2-way POWER4+)
#

device=/pci@400000000110/pci@2,4/pci1069,b166@1/scsi@0/sd@3,0
where do you get this information from mine looks totaly different - the bios equivilent shows
U0.1-P1/Z1-A3,0 and the only time I see anything like yours is when its trying to search for the drive - far to fast to read.

Please bare in mind I have a mediocre knowledge of linux and 0 knowledge of this machine until i got it.

partition=3

message=/yaboot.msg
delay=10

timeout=30
default=crux

image=/vmlinuz
label=crux
root=/dev/sda5
append="video=gxt4500"
read-only

image=/vmlinuz
label=crux-ttyS0,9600
root=/dev/sda5
append="console=ttyS0,9600"
read-only

image=/vmlinux-2.6.30.8
label=old
root=/dev/sda5
read-only

enablecdboot
enableofboot

acrux · **Posted:** 18 Oct 2009, 13:18

Shined wrote:

I understand what you have done and yes its what ive done baring this.

I have not yaboot.conf in my /etc directory to edit.

make your own one.

Shined wrote:

in your yaboot.conf file

#
# yaboot-1.3.14 on pSeries 9114-275 (2-way POWER4+)
#

device=/pci@400000000110/pci@2,4/pci1069,b166@1/scsi@0/sd@3,0
where do you get this information from mine looks totaly different - the bios equivilent shows
U0.1-P1/Z1-A3,0 and the only time I see anything like yours is when its trying to search for the drive - far to fast to read.

you can read it in device-tree/aliases. You, also, can use ofpathname utils from powerpc-utils but i'm not sure it safely works on that machines. Apropos, what's your machine?

Power Architecture machines don't have "bios" and U0.1-p1/Z1-A3,0 is only a code from Service Processor during boot tests of your machine.
I strongly suggest you read your own machine manual.

acrux · **Posted:** 26 Oct 2009, 15:01

something goes wrong during resincyng our forum's database and two messages were missed in action. Here a copy:

Shined wrote:

The install is done as specified I will have to quickly check over things tho as when I built the kernel just to ensure things were as the crux cd version I used linux....pseries.config in make menuconfig ; however this failed to boot getting stuck on the prom line ... im sure this is my fault but will let you all know if im still stuck.

Maybe you compiled the vanilla kernel.
GXT6500P isn't supported by linux kernel then you have to apply our patch. After the installation process you'll find it as /usr/src/linux-2.6.29.4.patch.
Our provided patch enables support also for the IBM GXT4000P and GXT6500P display adaptor based on Raster Engine RC1000, found on some IBM System P (pSeries) machines. This driver doesn't use Geometry Engine GT1000.

Code:

$ cd /usr/src/linux-2.6.29.4
$ make mrproper
$ cp ../linux-2.6.29.4-Pseries.config .config
$ patch -p1 < ../cruxppc-logo.diff
$ patch -p1 < ../linux-2.6.29.4.patch
$ make menuconfig
$ make all
$ make modules_install
$ cp vmlinux /boot/vmlinux
$ cp System.map /boot/System.map

CRUX PPC

A lightweight GNU/Linux distribution for PowerPC!

Boot problem [IBM Intellistation POWER 9114-275]

Who is online