Hello all,I am very new to this list (even thought I have some Debian experience on some other arch like x86 and mainly parisc since about 8 years now) ;-).
My title looks a bit like previous thread: <http://lists.debian.org/debian-powerpc/2008/03/msg00009.html> but is actualy very different, thought.
Having the oportunity to build an additional virtual partition on a p510, I take this opportunity to install my favorit Debian on it and use the latest debian-40r3-powerpc-netinst.iso (dated 18-Feb-2008).
Using: "expert64 nosmp video=ofonly ramdisk_size=100000000" at 'boot:' prompt allow me (even if not always clear to me) to build a custom install of my tast:
PreP on a Primary slice /dev/sda1 of 64Mb /boot on another Primary slice /dev/sda2 of 128Mb swap on a Logical slice /dev/sd5 3Gb (the vpar can increase until 2Gb of the 4 physical Gb) / on a Logical slice /dev/sda6 of 2Gb The rest on a logical volume on a Logical slice /dev/sda7 of 10Gb as follow: /dev/mapper/p5tst001vg-home /home (512Mb) /dev/mapper/p5tst001vg-tmp /tmp (128Mb) /dev/mapper/p5tst001vg-UsrSrc /usr/src (2Gb) /dev/mapper/p5tst001vg-var /var (512Mb) /dev/mapper/p5tst001vg-DebApt /DebApt (2Gb) (to grab debian pkg with apt) Everything seems to works fine until the reboot, SMS menu? So I try to select the new install hard disk as boot device but: [snip] /vdevice/v-scsi@30000015/disk@8100000000000000:-1,/etc/yaboot.conf: Unknown or corrupt filesystem Can't open config file Welcome to yaboot version 1.3.13 Enter "help" to get some basic usage information boot: Now at this 'boot:' prompt I tried: boot: /vdevice/v-scsi@30000015/disk@8100000000000000:2,/vmlinux root=/dev/sda6 Please wait, loading kernel... Elf64 kernel loaded... OF stdout device is: /vdevice/vty@30000000 Hypertas detected, assuming LPAR ! command line: root=/dev/sda6 memory layout at init: alloc_bottom : 00000000020f7000 alloc_top : 0000000008000000 alloc_top_hi : 0000000030000000 rmo_top : 0000000008000000 ram_top : 0000000030000000 Looking for displays instantiating rtas at 0x00000000076a1000 ... done 0000000000000000 : boot cpu 0000000000000000 copying OF device tree ... Building dt strings... Building dt structure... Device tree strings 0x00000000022f8000 -> 0x00000000022f9271 Device tree struct 0x00000000022fa000 -> 0x0000000002302000 Calling quiesce ... [snip] Starting Linux PPC64 #1 SMP Mon Feb 11 16:53:36 UTC 2008 ----------------------------------------------------- ppc64_pft_size = 0x19 physicalMemorySize = 0x30000000 ppc64_caches.dcache_line_size = 0x80 ppc64_caches.icache_line_size = 0x80 htab_address = 0x0000000000000000 htab_hash_mask = 0x3ffff -----------------------------------------------------Linux version 2.6.18-6-powerpc64 (Debian 2.6.18.dfsg.1-18etch1) (waldi@debian.org) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Mon Feb 11 16:53:36 UTC 2008
[boot]0012 Setup Arch No ramdisk, default root is /dev/sda2 EEH: PCI Enhanced I/O Error Handling Enabled PPC64 nvram contains 7168 bytes [boot]0015 Setup Done Built 1 zonelists. Total pages: 196608 Kernel command line: root=/dev/sda6 [boot]0020 XICS Init [snip] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled pmac_zilog: 0.6 (Benjamin Herrenschmidt <benh@kernel.crashing.org>) RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize 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 TCP bic registered NET: Registered protocol family 1 NET: Registered protocol family 17 VFS: Cannot open root device "sda6" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) As yaboot is very new to me (I just learn that it needs a PreP slice): - I'm not sure to have correctly sized it (64Mb???) - I don't know how to specify the path to initrd.img? I so reboot from the install cd;I just forgot the 'rescue' option and so just use 'Excute a shell' from 'expert64' and reach well to mount the installed stuff ;-)
My fstab looks perfect:
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/sda6 / ext3 defaults,errors=remount-ro 0 1
/dev/mapper/p5tst001vg-DebApt /DebApt ext3 defaults 0 2
/dev/sda2 /boot ext3 defaults 0 2
/dev/mapper/p5tst001vg-home /home ext3 defaults 0 2
/dev/mapper/p5tst001vg-tmp /tmp ext3 defaults 0 2
/dev/mapper/p5tst001vg-UsrSrc /usr/src ext3 defaults 0 2
/dev/mapper/p5tst001vg-var /var ext3 defaults 0 2
/dev/sda5 none swap sw 0 0
/dev/hde /media/cdrom0 udf,iso9660 user,noauto 0 0
The yaboot.conf seems to be well install too:
## yaboot.conf generated by debian-installer
##
## run: "man yaboot.conf" for details. Do not make changes until you have!!
## see also: /usr/share/doc/yaboot/examples for example configurations.
##
## For a dual-boot menu, add one or more of:
## bsd=/dev/hdaX, macos=/dev/hdaY, macosx=/dev/hdaZ
boot=/dev/sda1
partition=2
root=/dev/sda6
timeout=50
install=/usr/lib/yaboot/yaboot
enablecdboot
image=/vmlinux
label=Linux
read-only
initrd=/initrd.img
append="nosmp ramdisk_size=100000000"
image=/vmlinux.old
label=old
read-only
initrd=/initrd.img.old
append="nosmp ramdisk_size=100000000"
=== <> ===
In the install syslog (which I also join gzip), I just noticed some stuff about this yaboot:
[snip]
Mar 14 10:13:14 main-menu[961]: INFO: Menu item 'yaboot-installer' selected
Mar 14 10:13:14 yaboot-installer: info: architecture: powerpc/chrp_rs6k
[snip]
Mar 14 10:13:15 kernel: program find-partitions is using a deprecated SCSI ioctl, please convert it to SG_IO
Mar 14 10:13:15 kernel: ioctl32(find-partitions:17037): Unknown cmd fd(7) cmd(41a04403){01} arg(ffc81058) on
/dev/mapper/p5tst001vg-DebApt
Mar 14 10:13:15 kernel: ioctl32(find-partitions:17037): Unknown cmd fd(7) cmd(41a04403){01} arg(ffc81038) on
/dev/mapper/p5tst001vg-DebApt
Mar 14 10:13:15 kernel: ioctl32(find-partitions:17037): Unknown cmd fd(7) cmd(41a04403){01} arg(ffc81058) on
/dev/mapper/p5tst001vg-UsrSrc
Mar 14 10:13:15 kernel: ioctl32(find-partitions:17037): Unknown cmd fd(7) cmd(41a04403){01} arg(ffc81038) on
/dev/mapper/p5tst001vg-UsrSrc
Mar 14 10:13:15 kernel: ioctl32(find-partitions:17037): Unknown cmd fd(7) cmd(41a04403){01} arg(ffc81058) on
/dev/mapper/p5tst001vg-home
Mar 14 10:13:15 kernel: ioctl32(find-partitions:17037): Unknown cmd fd(7) cmd(41a04403){01} arg(ffc81038) on
/dev/mapper/p5tst001vg-home
Mar 14 10:13:15 kernel: ioctl32(find-partitions:17037): Unknown cmd fd(7) cmd(41a04403){01} arg(ffc81058) on
/dev/mapper/p5tst001vg-tmp
Mar 14 10:13:15 kernel: ioctl32(find-partitions:17037): Unknown cmd fd(7) cmd(41a04403){01} arg(ffc81038) on
/dev/mapper/p5tst001vg-tmp
Mar 14 10:13:15 kernel: ioctl32(find-partitions:17037): Unknown cmd fd(7) cmd(41a04403){01} arg(ffc81058) on
/dev/mapper/p5tst001vg-var
Mar 14 10:13:15 kernel: ioctl32(find-partitions:17037): Unknown cmd fd(7) cmd(41a04403){01} arg(ffc81038) on
/dev/mapper/p5tst001vg-var
Mar 14 10:13:15 yaboot-installer: info: guessed bootstrap partitions: /dev/sda1
Mar 14 10:13:15 yaboot-installer: info: guessed default bootstrap partition: /dev/sda1
[snip]
Mar 14 10:13:28 os-prober: debug: running /usr/lib/os-probes/mounted/40lsb on mounted /dev/mapper/p5tst001vg-var
Mar 14 10:13:28 os-prober: debug: running /usr/lib/os-probes/mounted/90linux-distro on mounted /dev/mapper/p5tst001vg-var
Mar 14 10:13:28 yaboot-installer: info: ofpath returned nothing; leaving out device= line and praying
Mar 14 10:13:28 kernel: ioctl32(nvsetenv:17692): Unknown cmd fd(7) cmd(20007043){' '} arg(00000009) on /dev/nvram
Those 2 last lines make me think, that's the actual issue even thought it seems happy :<?
Mar 14 10:13:28 yaboot-installer: mkofboot: Installing primary bootstrap /usr/lib/yaboot/yaboot onto /dev/sda1...
Mar 14 10:13:29 yaboot-installer: mkofboot: Installation successful
Mar 14 10:13:29 yaboot-installer: mkofboot: Installation complete.
mmm I am sceptical:
- is new yaboot release (1.3.14) would help?
- is a new kernel image (e.g. 2.6.24) would better help yaboot-installer?
- or would be even better to update yaboot-installer to a most recent release?
All comments, idea are welcome.
Tia,
J.
PS: I tried also to boot the testing "debian-testing-powerpc-netinst.iso" (dated 08-Mar-2008) but even with
"ramdisk_size=100000000" it always failed to open initrd image (iirc wrong formated file?)
Attachment:
syslog.gz
Description: GNU Zip compressed data