Bug#619236: [Cbe-oss-dev] Bug#619236: installation-reports: installation works fine on PS3 now, but we still can't boot after the installation

2011-04-15 Thread Antonio Ospite
On Wed, 30 Mar 2011 15:03:26 -0700
Geoff Levand ge...@infradead.org wrote:

 On 03/22/2011 02:29 AM, Antonio Ospite wrote:
  Hi,
  
  the installation on PS3 now completes pretty fine, however there are 
  still some details that could be improved.
  
  The installer warns about the boot loader not being installed, which is 
  fine, I already had the 'petitboot' bootloader installed, but some 
  configuration is still needed to make the system actually boot _after_ 
  the installation.
  
  petitboot needs a /etc/kboot.conf in the root filesystem with this 
  content to successfully boot the installed system:
  
  linux=/boot/vmlinux initrd=/boot/initrd.img root=/dev/ps3da1 quiet
  
[...]

 I encountered the same problems as Antonio.  Once the installer
 was finished, but before it rebooted the system I used this from
 a tty console:
 
   echo 'linux=/boot/vmlinux initrd=/boot/initrd.img root=/dev/ps3da1'  
 /target/etc/kboot.conf
 
 -Geoff

Hi,

I've gone a little bit further on this: I started to put together a
kboot-mkconfig script (shamelessly copied from grub-mkconfig) along
with an update-kboot and some kernel install hooks, you can find it
here:

http://git.ao2.it/kboot-utils.git/

You can build the package with dpkg-buildpackage -tc.

The idea is to have d-i to install this kboot-utils package when
machine==PS3, and let the postinst script of the package generate
the kboot.conf for us, but I haven't got that far yet.

The main concern is about how to detect the actual device the rootfs is
going to be on, right now I am doing:
LINUX_ROOT_DEVICE=$(mount | grep ' / ' | cut -d ' ' -f 1)

and my current understanding is that this is going to work even from
the installer because d-i would be calling apt in a chroot /target
context when installing the kboot-utils package, but I'd like to have
some confirmation about that.

And a review about the state of the package will be appreciated too.

With Kind Regards,
   Antonio

-- 
Antonio Ospite
http://ao2.it

PGP public key ID: 0x4553B001

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?


pgpW7MfNmWrOk.pgp
Description: PGP signature


Bug#619236: [Cbe-oss-dev] Bug#619236: installation-reports: installation works fine on PS3 now, but we still can't boot after the installation

2011-03-30 Thread Geoff Levand
On 03/22/2011 02:29 AM, Antonio Ospite wrote:
 Hi,
 
 the installation on PS3 now completes pretty fine, however there are 
 still some details that could be improved.
 
 The installer warns about the boot loader not being installed, which is 
 fine, I already had the 'petitboot' bootloader installed, but some 
 configuration is still needed to make the system actually boot _after_ 
 the installation.
 
 petitboot needs a /etc/kboot.conf in the root filesystem with this 
 content to successfully boot the installed system:
 
 linux=/boot/vmlinux initrd=/boot/initrd.img root=/dev/ps3da1 quiet
 

I could successfully do a gnome desktop install using the
20110329 daily:

  
http://cdimage.debian.org/cdimage/daily-builds/daily/20110329-5/powerpc/iso-cd/debian-testing-powerpc-netinst.iso

I encountered the same problems as Antonio.  Once the installer
was finished, but before it rebooted the system I used this from
a tty console:

  echo 'linux=/boot/vmlinux initrd=/boot/initrd.img root=/dev/ps3da1'  
/target/etc/kboot.conf

-Geoff




-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4d93a8ae.2090...@infradead.org



Bug#619236: installation-reports: installation works fine on PS3 now, but we still can't boot after the installation

2011-03-22 Thread Antonio Ospite
Package: installation-reports
Severity: important
Tags: d-i



-- Package-specific info:

Boot method: CD
Image version: 
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/powerpc/iso-cd/debian-testing-powerpc-netinst.iso
 19-Mar-2011 10:28
Date: 19-Mar-2011 15:00

Machine: Sony PS3
Partitions:
FilesystemType   1K-blocks  Used Available Use% Mounted on
/dev/ps3da1   ext425635140   1149880  23183040   5% /
tmpfstmpfs  112732 0112732   0% /lib/init/rw
udev tmpfs   50056   128 49928   1% /dev
tmpfstmpfs  112732 0112732   0% /dev/shm

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Clock/timezone setup:   [O]
User/password setup:[O]
Install tasks:  [O]
Install boot loader:[E]
Overall install:[O]

Comments/Problems:

Hi,

the installation on PS3 now completes pretty fine, however there are 
still some details that could be improved.

The installer warns about the boot loader not being installed, which is 
fine, I already had the 'petitboot' bootloader installed, but some 
configuration is still needed to make the system actually boot _after_ 
the installation.

petitboot needs a /etc/kboot.conf in the root filesystem with this 
content to successfully boot the installed system:

linux=/boot/vmlinux initrd=/boot/initrd.img root=/dev/ps3da1 quiet

On my installation the / mount point is for /dev/ps3da1, and /boot is on 
the same partition, but a script like the following can be used to 
figure these things out after the installation:

[ BEGIN build_kboot.conf.sh ]---
#!/bin/sh

ROOTFS=$(mount | grep ' / ' | cut -d ' ' -f 1)
OLD_CMDLINE=$(cat /proc/cmdline | sed -e 's/root=[^[:space:]]*\s//')

CMDLINE=root=$ROOTFS $OLD_CMDLINE

find /boot -type f -name vmlinu* |
while read file;
do
  VERSION=$(echo $file | cut -d '-' -f 2- );
  echo -n $VERSION=$file;
  echo -n  initrd=/boot/initrd.img-$VERSION;
  echo -n  $CMDLINE
  echo
done
[ END build_kboot.conf.sh ]---

Can the /etc/kboot.conf file be created by the installer automatically 
when the system is a PS3? (Ideally kboot.conf should be recreated after 
each kernel install).

Also, can the installer be told to install the ps3-utils package
automatically when the system is a PS3?

It looks like these system dependent configurations are done in 
hw-detect, I'll try to provide a patch for these, but some guidance will 
be very much appreciated.

Thanks,
   Antonio Ospite
   http://ao2.it

-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION=Debian GNU/Linux installer
DISTRIB_RELEASE=7.0 (wheezy) - installer build 20110318-00:16
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux ps3 2.6.37-2-powerpc64 #1 SMP Sun Feb 27 13:21:25 UTC 2011 
ppc64 GNU/Linux
usb-list: 
usb-list: Bus 01 Device 01: PS3 EHCI Host Controller [1d6b:0002]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 00
usb-list:Manufacturer: Linux 2.6.37-2-powerpc64 ehci_hcd
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
usb-list: 
usb-list: Bus 01 Device 02: USB2.0 Hub [05e3:0607]
usb-list:Level 01 Parent 01 Port 01  Class 09(hub  ) Subclass 00 Protocol 02
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 02 Driver hub
usb-list: 
usb-list: Bus 01 Device 03: Wireless Keyboard/Mouse [099a:7202]
usb-list:Level 02 Parent 02 Port 00  Class 00(ifc ) Subclass 00 Protocol 00
usb-list:Interface 00: Class 03(HID  ) Subclass 01 Protocol 01 Driver usbhid
usb-list:Interface 01: Class 03(HID  ) Subclass 01 Protocol 02 Driver usbhid
usb-list: 
usb-list: Bus 02 Device 01: PS3 EHCI Host Controller [1d6b:0002]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 00
usb-list:Manufacturer: Linux 2.6.37-2-powerpc64 ehci_hcd
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
usb-list: 
usb-list: Bus 02 Device 02: Bluetooth Transceiver [054c:0267]
usb-list:Level 01 Parent 01 Port 01  Class e0(wlcon) Subclass 01 Protocol 01
usb-list:Manufacturer: Sony
usb-list:Interface 00: Class e0(wlcon) Subclass 01 Protocol 01 Driver none
usb-list:Interface 01: Class e0(wlcon) Subclass 01 Protocol 01