Installation - boot after installation fails
Hello everyone, I downloaded the debian netinstaller - debian-6.0.7-powerpc-netinst.iso - and installed on a p505. The installation process goes well, but the boot fails. I tried using the LVM with multiple partitions and got this message If you omit "device:" and "partno" yaboot will use the values of "device=" and "partition=" in yaboot.conf, right now those are set to: device=/vdevice/v-scsi@3002/@1 partition=-1 And after a reinstall using the whole disk, no LVM I got: If you omit "device:" and "partno" yaboot will use the values of "device=" and "partition=" in yaboot.conf, right now those are set to: device=/vdevice/v-scsi@3002/@1 partition=2 The other key message, same for both is: Please wait, loading kernel... Can't open device /vdevice/v-scsi@3002/@1:2,/boot/vmlinux: Unable to open file, Invalid device I have located a number of bugs with "Invalid device" in them http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641852 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637519 but these seem to be focused on issues with the installer and power7. My question is about after the installation. How to proceed? How to document - better - what is wrong? Thanks. Michael
Re: Installation - boot after installation fails
>From memory it is creating three partitions - boot, swap and /. The boot partition is position 1 iirc. On Mon, Mar 18, 2013 at 3:23 PM, Lennart Sorensen < lsore...@csclub.uwaterloo.ca> wrote: > On Sun, Mar 17, 2013 at 08:01:08PM +0100, Michael Felt wrote: > > Hello everyone, > > > > I downloaded the debian netinstaller - debian-6.0.7-powerpc-netinst.iso - > > and installed on a p505. The installation process goes well, but the boot > > fails. > > > > I tried using the LVM with multiple partitions and got this message > > If you omit "device:" and "partno" yaboot will use the values of > > "device=" and "partition=" in yaboot.conf, right now those are set to: > > device=/vdevice/v-scsi@3002/@1 > > partition=-1 > > > > And after a reinstall using the whole disk, no LVM I got: > > If you omit "device:" and "partno" yaboot will use the values of > > "device=" and "partition=" in yaboot.conf, right now those are set to: > > device=/vdevice/v-scsi@3002/@1 > > partition=2 > > > > The other key message, same for both is: > > Please wait, loading kernel... > > Can't open device > > /vdevice/v-scsi@3002/@1:2,/boot/vmlinux: Unable to open file, > Invalid > > device > > > > I have located a number of bugs with "Invalid device" in them > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641852 > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637519 > > > > but these seem to be focused on issues with the installer and power7. My > > question is about after the installation. > > > > How to proceed? How to document - better - what is wrong? > > How are you partitioning the disk? > > My understanding is that yaboot requries boot partition to install to > so at least that one can't be in LVM. > > I stopped using yaboot a long time ago, but the debian installer still > seems to prefer it on powerpc. > > -- > Len Sorensen >
Re: Installation - boot after installation fails
4 to 5 years ago I was only able to get Linux to boot, (Redhat, Novell, Debian) unless it was a physical disk. I have not tried that yet because I do not have an empty disk to supply. And if that worked I would just uninstall it as that is "too expensive" in terms of resources. I have tried the "install64/export64" options Guided LVM (and I choose as many partitions as possible) and the Guided "one partition" - recommended for new users option. The partitions are created, the install runs fine, but on reboot - nada. IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM | Elapsed time since release of system processors: 28 mins 41 secs Config file read, 4096 bytes Welcome to yaboot version 1.3.13 Enter "help" to get some basic usage information boot: Linux Please wait, loading kernel... Can't open device /vdevice/v-scsi@3002/@1:2,/boot/vmlinux: Unable to open file, Invalid device boot: help Press the tab key for a list of defined images. The label marked with a "*" is is the default image, press to boot it. To boot any other label simply type its name and press . To boot a kernel image which is not defined in the yaboot configuration file, enter the kernel image name as [[device:][partno],]/path, where "device:" is the OpenFirmware device path to the disk the image resides on, and "partno" is the partition number the image resides on. Note that the comma (,) is only required if you specify an OpenFirmware device, if you only specify a filename you should not start it with a "," If you omit "device:" and "partno" yaboot will use the values of "device=" and "partition=" in yaboot.conf, right now those are set to: device=/vdevice/v-scsi@3002/@1 partition=2 boot: That is all I get. I am willing to spend some time on this - but I do not know the "Linux" way these days. Clear instructions, clear requests for info (e.g., if you can jump out of the install and look at something, manual divvy if you prefer, etc..) just might be a few hours to days between responses as I also have regular work to attend to. Thanks!!! for your assistance! Michael On Mon, Mar 18, 2013 at 9:36 PM, Frank Fegert wrote: > Hello, > > On Mon, Mar 18, 2013 at 08:36:10PM +0100, Michael Felt wrote: > > >From memory it is creating three partitions - boot, swap and /. The boot > > partition is position 1 iirc. > > i'd probably start with the guided partitioning and modify from > there to your own needs. A bootable setup looks like this in my > case, with sda2 being "/": > > host:/# sfdisk -l > Disk /dev/sda: 36864 cylinders, 64 heads, 32 sectors/track > Warning: The partition table looks like it was made > for C/H/S=*/255/63 (instead of 36864/64/32). > For this listing I'll assume that geometry. > Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting > from 0 > >Device Boot Start End #cyls#blocks Id System > /dev/sda1 * 0+ 0 1- 8001 41 PPC PReP Boot > /dev/sda2 1 122 122 979965 83 Linux > /dev/sda312346984576 36756720 8e Linux LVM > /dev/sda4 0 - 0 00 Empty > > Is yours a LPARed environment with disks mapped from VIO servers, > or are the disks real physical ones? > > Best regards, > > Frank >
Re: Installation - boot after installation fails
p.s. disk types tried: logical volume from a vgClient volume group, iSCSI LUN (virtual "physical" disk). sizes: 10G and 12G (I regularly install AIX on 4 and 6G "disks"). On Mon, Mar 18, 2013 at 10:56 PM, Michael Felt wrote: > 4 to 5 years ago I was only able to get Linux to boot, (Redhat, Novell, > Debian) unless it was a physical disk. I have not tried that yet because I > do not have an empty disk to supply. And if that worked I would just > uninstall it as that is "too expensive" in terms of resources. > > I have tried the "install64/export64" options Guided LVM (and I choose as > many partitions as possible) and the Guided "one partition" - recommended > for new users option. > > The partitions are created, the install runs fine, but on reboot - nada. > > IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM > IBM > | > Elapsed time since release of system processors: 28 mins 41 secs > > Config file read, 4096 bytes > > Welcome to yaboot version 1.3.13 > Enter "help" to get some basic usage information > boot: Linux > > Please wait, loading kernel... > Can't open device > /vdevice/v-scsi@3002/@1:2,/boot/vmlinux: Unable to open file, Invalid > device > boot: help > > Press the tab key for a list of defined images. > The label marked with a "*" is is the default image, press to > boot it. > > To boot any other label simply type its name and press . > > To boot a kernel image which is not defined in the yaboot configuration > file, enter the kernel image name as [[device:][partno],]/path, where > "device:" is the OpenFirmware device path to the disk the image > resides on, and "partno" is the partition number the image resides on. > Note that the comma (,) is only required if you specify an OpenFirmware > device, if you only specify a filename you should not start it with a "," > > > If you omit "device:" and "partno" yaboot will use the values of > "device=" and "partition=" in yaboot.conf, right now those are set to: > device=/vdevice/v-scsi@3002/@1 > partition=2 > > boot: > > > That is all I get. I am willing to spend some time on this - but I do not > know the "Linux" way these days. > Clear instructions, clear requests for info (e.g., if you can jump out of > the install and look at something, manual divvy if you prefer, etc..) > > just might be a few hours to days between responses as I also have regular > work to attend to. > > Thanks!!! for your assistance! > > Michael > > > On Mon, Mar 18, 2013 at 9:36 PM, Frank Fegert wrote: > >> Hello, >> >> On Mon, Mar 18, 2013 at 08:36:10PM +0100, Michael Felt wrote: >> > >From memory it is creating three partitions - boot, swap and /. The >> boot >> > partition is position 1 iirc. >> >> i'd probably start with the guided partitioning and modify from >> there to your own needs. A bootable setup looks like this in my >> case, with sda2 being "/": >> >> host:/# sfdisk -l >> Disk /dev/sda: 36864 cylinders, 64 heads, 32 sectors/track >> Warning: The partition table looks like it was made >> for C/H/S=*/255/63 (instead of 36864/64/32). >> For this listing I'll assume that geometry. >> Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting >> from 0 >> >>Device Boot Start End #cyls#blocks Id System >> /dev/sda1 * 0+ 0 1- 8001 41 PPC PReP Boot >> /dev/sda2 1 122 122 979965 83 Linux >> /dev/sda312346984576 36756720 8e Linux LVM >> /dev/sda4 0 - 0 00 Empty >> >> Is yours a LPARed environment with disks mapped from VIO servers, >> or are the disks real physical ones? >> >> Best regards, >> >> Frank >> > >
Re: Installation - boot after installation fails
well in this case the newer machine must be the vios version (2.2.2.×) because my hardware is p5 generation. guess i'll just have to wait for the netboot respositories to update. i have waited "many moons" - what is a few more? thanks for the explanation! Original message From: Lennart Sorensen Date: 19/03/2013 16:50 (GMT+01:00) To: Michael Felt Cc: Frank Fegert ,debian-powerpc@lists.debian.org Subject: Re: Installation - boot after installation fails On Mon, Mar 18, 2013 at 10:56:00PM +0100, Michael Felt wrote: > 4 to 5 years ago I was only able to get Linux to boot, (Redhat, Novell, > Debian) unless it was a physical disk. I have not tried that yet because I > do not have an empty disk to supply. And if that worked I would just > uninstall it as that is "too expensive" in terms of resources. > > I have tried the "install64/export64" options Guided LVM (and I choose as > many partitions as possible) and the Guided "one partition" - recommended > for new users option. > > The partitions are created, the install runs fine, but on reboot - nada. > > IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM > | > Elapsed time since release of system processors: 28 mins 41 secs > > Config file read, 4096 bytes > > Welcome to yaboot version 1.3.13 > Enter "help" to get some basic usage information > boot: Linux > Please wait, loading kernel... > Can't open device > /vdevice/v-scsi@3002/@1:2,/boot/vmlinux: Unable to open file, Invalid > device > boot: help > > Press the tab key for a list of defined images. > The label marked with a "*" is is the default image, press to boot > it. > > To boot any other label simply type its name and press . > > To boot a kernel image which is not defined in the yaboot configuration > file, enter the kernel image name as [[device:][partno],]/path, where > "device:" is the OpenFirmware device path to the disk the image > resides on, and "partno" is the partition number the image resides on. > Note that the comma (,) is only required if you specify an OpenFirmware > device, if you only specify a filename you should not start it with a "," > > If you omit "device:" and "partno" yaboot will use the values of > "device=" and "partition=" in yaboot.conf, right now those are set to: > device=/vdevice/v-scsi@3002/@1 > partition=2 > > boot: > > > That is all I get. I am willing to spend some time on this - but I do not > know the "Linux" way these days. > Clear instructions, clear requests for info (e.g., if you can jump out of > the install and look at something, manual divvy if you prefer, etc..) > > just might be a few hours to days between responses as I also have regular > work to attend to. > > Thanks!!! for your assistance! I just noticed the yaboot version. 1.3.13 has some issues with "newer" IBM machines. 1.3.16 works much better, but that's only in the next debian release (although I suppose that can't be that far away from being released now). See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=473725 for some of the info on this problem. -- Len Sorensen
Re: Installation - boot after installation fails
upgrade? how? i am using netinst.iso to do the install, and what is installed does not boot! will try 2) when i have access. travelling/work keeps me away atm. Original message From: Gasha Date: 19/03/2013 15:23 (GMT+01:00) To: debian-powerpc@lists.debian.org Subject: Re: Installation - boot after installation fails Hi, in short: 1) upgrade yaboot pkg from wheezy (at least 1.3.16) 2) /vdevice will not work, use device=/dev/sda G On 03/19/2013 03:23 PM, Frank Fegert wrote: > Hello, > > i had several issues in the past with Debian on IBM Power, please see > the list archives if you have an archeological interest ;-) Some of > those issues were firmware/microcode related, some were related to VIOS > mapped disks and i also had a similar issue to the one your experiencing > due to the rather old v1.3.13 yaboot used in Debian v6.0.x. I also could > imagine, that you're missing the appropriate iSCSI driver in the initrd > image. To rule out the mentioned yaboot issue, could you please try an > install with a current snapshot of the Debian v7.x [1] installer image? > This contains a known working yaboot v1.3.16. > > Best regards, > > Frank > > > [1] > http://cdimage.debian.org/cdimage/weekly-builds/powerpc/iso-cd/debian-testing-powerpc-netinst.iso > > > On Mon, Mar 18, 2013 at 10:57:52PM +0100, Michael Felt wrote: > >> p.s. disk types tried: logical volume from a vgClient volume group, iSCSI >> LUN (virtual "physical" disk). >> >> sizes: 10G and 12G (I regularly install AIX on 4 and 6G "disks"). >> >> On Mon, Mar 18, 2013 at 10:56 PM, Michael Felt wrote: >> >> >>> 4 to 5 years ago I was only able to get Linux to boot, (Redhat, Novell, >>> Debian) unless it was a physical disk. I have not tried that yet because I >>> do not have an empty disk to supply. And if that worked I would just >>> uninstall it as that is "too expensive" in terms of resources. >>> >>> I have tried the "install64/export64" options Guided LVM (and I choose as >>> many partitions as possible) and the Guided "one partition" - recommended >>> for new users option. >>> >>> The partitions are created, the install runs fine, but on reboot - nada. >>> >>> IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM >>> IBM >>> | >>> Elapsed time since release of system processors: 28 mins 41 secs >>> >>> Config file read, 4096 bytes >>> >>> Welcome to yaboot version 1.3.13 >>> Enter "help" to get some basic usage information >>> boot: Linux >>> >>> Please wait, loading kernel... >>> Can't open device >>> /vdevice/v-scsi@3002/@1:2,/boot/vmlinux: Unable to open file, Invalid >>> device >>> boot: help >>> >>> Press the tab key for a list of defined images. >>> The label marked with a "*" is is the default image, press to >>> boot it. >>> >>> To boot any other label simply type its name and press. >>> >>> To boot a kernel image which is not defined in the yaboot configuration >>> file, enter the kernel image name as [[device:][partno],]/path, where >>> "device:" is the OpenFirmware device path to the disk the image >>> resides on, and "partno" is the partition number the image resides on. >>> Note that the comma (,) is only required if you specify an OpenFirmware >>> device, if you only specify a filename you should not start it with a "," >>> >>> >>> If you omit "device:" and "partno" yaboot will use the values of >>> "device=" and "partition=" in yaboot.conf, right now those are set to: >>> device=/vdevice/v-scsi@3002/@1 >>> partition=2 >>> >>> boot: >>> >>> >>> That is all I get. I am willing to spend some time on this - but I do not >>> know the "Linux" way these days. >>> Clear instructions, clear requests for info (e.g., if you can jump out of >>> the install and look at something, manual divvy if you prefer, etc..) >>> >>> just might be a few hours to days between responses as I also have regular >>> work to attend to. >>> > > -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/514874d3.4030...@pie-dabas.net
Re: Installation - boot after installation fails
I'll give it a shot. On Wed, Mar 20, 2013 at 3:06 PM, Lennart Sorensen < lsore...@csclub.uwaterloo.ca> wrote: > On Wed, Mar 20, 2013 at 08:33:34AM +0100, Michael Felt wrote: > > upgrade? how? i am using netinst.iso to do the install, and what is > installed does not boot! > > > > will try 2) when i have access. travelling/work keeps me away atm. > > You could when at the end of the install, instead of finishing the > install, ask for a shell and download the yaboot from wheezy and > install it. > > Something like: > > drop to shell: > > # chroot /target > # apt-get install wget(in case it isn't there already) > # cd /tmp > # wget > http://ftp.us.debian.org/debian/pool/main/y/yaboot/yaboot_1.3.16-4_powerpc.deb > # dpkg -i yaboot_1.3.16-4_powerpc.deb > # rm yaboot_1.3.16-4_powerpc.deb > # exit > # exit > > You should be back in the installer menu. At this point try the boot > loader step again and see if it works now. > > I did not test those steps so hopefully I remember correctly how the > installer behaves. > > -- > Len Sorensen >
Re: Installation - boot after installation fails
201] Mount-cache hash table entries: 256 [0.002323] Initializing cgroup subsys ns [0.002333] Initializing cgroup subsys cpuacct [0.002344] Initializing cgroup subsys devices [0.002352] Initializing cgroup subsys freezer [0.002360] Initializing cgroup subsys net_cls [0.002795] Processor 1 found. [0.002814] Brought up 2 CPUs [0.003711] devtmpfs: initialized [0.011407] regulator: core version 0.5 [0.011502] NET: Registered protocol family 16 [0.011537] IBM eBus Device Driver [0.011809] POWER5+/++ performance monitor hardware support registered [0.012914] PCI: Probing PCI hardware [0.013580] bio: create slab at 0 [0.013765] vgaarb: loaded [0.013949] Switching to clocksource timebase [0.016461] NET: Registered protocol family 2 [0.016639] IP route cache hash table entries: 4096 (order: 3, 32768 bytes) [0.017219] TCP established hash table entries: 16384 (order: 6, 262144 bytes) [0.017414] TCP bind hash table entries: 16384 (order: 6, 262144 bytes) [0.017549] TCP: Hash tables configured (established 16384 bind 16384) [0.017562] TCP reno registered [0.017670] NET: Registered protocol family 1 [0.035623] IOMMU table initialized, virtual merging enabled [0.039616] audit: initializing netlink socket (disabled) [0.039641] type=2000 audit(1363818744.036:1): initialized [0.049874] HugeTLB registered 16 MB page size, pre-allocated 0 pages [0.049888] HugeTLB registered 16 GB page size, pre-allocated 0 pages [0.052690] VFS: Disk quotas dquot_6.5.2 [0.052804] Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [0.052938] msgmni has been set to 720 [0.053317] alg: No test for stdrng (krng) [0.053421] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) [0.053438] io scheduler noop registered [0.053447] io scheduler anticipatory registered [0.053457] io scheduler deadline registered [0.053578] io scheduler cfq registered (default) [0.056221] Linux agpgart interface v0.103 [0.056339] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [0.056550] pmac_zilog: 0.6 (Benjamin Herrenschmidt < b...@kernel.crashing.org>) [0.05] input: Macintosh mouse button emulation as /devices/virtual/input/input0 [0.056723] Uniform Multi-Platform E-IDE driver [0.056763] ide-gd driver 1.18 [0.056892] mice: PS/2 mouse device common for all mice [0.056958] rtc-generic rtc-generic: rtc core: registered rtc-generic as rtc0 [0.057721] TCP cubic registered [0.057957] NET: Registered protocol family 10 [0.059643] Mobile IPv6 [0.059653] NET: Registered protocol family 17 [0.059806] registered taskstats version 1 [0.059941] rtc-generic rtc-generic: setting system clock to 2013-03-20 22:32:24 UTC (1363818744) [0.059983] Initalizing network drop monitor service [0.060051] List of all partitions: [0.060060] No filesystem could mount root, tried: [0.060074] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [0.060089] Call Trace: [0.060102] [c00016137c40] [c00108fc] .show_stack+0x6c/0x174 (unreliable) [0.060124] [c00016137cf0] [c04f4238] .panic+0x80/0x1b0 [0.060141] [c00016137d80] [c068518c] .mount_block_root+0x2dc/0x318 [0.060160] [c00016137e50] [c06853cc] .prepare_namespace+0x17c/0x1d0 [0.060179] [c00016137ee0] [c0684478] .kernel_init+0x26c/0x298 [0.060196] [c00016137f90] [c0026c18] .kernel_thread+0x54/0x70 [0.060214] Rebooting in 180 seconds.. = Well, a step forward. Is there an argument I could have tried giving to ybin to update the info in the config file? And, I had also tried the same AIX like device string with the squeeze, did not work. And, I hope this helps! Michael On Wed, Mar 20, 2013 at 10:03 PM, Michael Felt wrote: > I'll give it a shot. > > > On Wed, Mar 20, 2013 at 3:06 PM, Lennart Sorensen < > lsore...@csclub.uwaterloo.ca> wrote: > >> On Wed, Mar 20, 2013 at 08:33:34AM +0100, Michael Felt wrote: >> > upgrade? how? i am using netinst.iso to do the install, and what is >> installed does not boot! >> > >> > will try 2) when i have access. travelling/work keeps me away atm. >> >> You could when at the end of the install, instead of finishing the >> install, ask for a shell and download the yaboot from wheezy and >> install it. >> >> Something like: >> >> drop to shell: >> >> # chroot /target >> # apt-get install wget(in case it isn't there already) >> # cd /tmp >> # wget >> http://ftp.us.debian.org/debian/pool/main/y/yaboot/yaboot_1.3.16-4_powerpc.deb >> # dpkg -i yaboot_1.3.16-4_powerpc.deb >> # rm yaboot_1.3.16-4_powerpc.deb >> # exit >> # exit >> >> You should be back in the installer menu. At this point try the boot >> loader step again and see if it works now. >> >> I did not test those steps so hopefully I remember correctly how the >> installer behaves. >> >> -- >> Len Sorensen >> > >
Re: Installation - boot after installation fails
found it, yaboot.conf The original contents: ## 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/disk/by-id/scsi-SAIX_VDASD_0002c0cad30001134deb16ba.4-part1" device=/vdevice/v-scsi@3002/@1 partition=2 root="UUID=c9498eff-1727-4484-93e6-94249972c918" timeout=50 install=/usr/lib/yaboot/yaboot enablecdboot image=/boot/vmlinux label=Linux read-only initrd=/boot/initrd.img image=/boot/vmlinux.old label=old read-only initrd=/boot/initrd.img.old == ~ # chroot /target # ls boot System.map-2.6.32-5-powerpc64 initrd.img-2.6.32-5-powerpc64 config-2.6.32-5-powerpc64 vmlinux initrd.img vmlinux-2.6.32-5-powerpc64 # ls -l boot total 24016 -rw-r--r-- 1 root root 2344890 Feb 25 09:45 System.map-2.6.32-5-powerpc64 -rw-r--r-- 1 root root93214 Feb 25 09:45 config-2.6.32-5-powerpc64 lrwxrwxrwx 1 root root 29 Mar 24 18:15 initrd.img -> initrd.img-2.6.32-5-powerpc64 -rw-r--r-- 1 root root 10699255 Mar 24 18:18 initrd.img-2.6.32-5-powerpc64 lrwxrwxrwx 1 root root 26 Mar 24 18:15 vmlinux -> vmlinux-2.6.32-5-powerpc64 -rw-r--r-- 1 root root 11403398 Feb 25 09:45 vmlinux-2.6.32-5-powerpc64 changed (/target)/etc/yaboot.conf to ... boot="/dev/disk/by-id/scsi-SAIX_VDASD_0002c0cad30001134deb16ba.4-part1" ## device=/vdevice/v-scsi@3002/@1 device=/vdevice/v-scsi@3002/@8100:2 partition=2 root="UUID=c9498eff-1727-4484-93e6-94249972c918" timeout=50 install=/usr/lib/yaboot/yaboot enablecdboot image=/boot/vmlinux label=Linux read-only initrd=/boot/initrd.img deleted this part... image=/boot/vmlinux.old ... = ybin says: ybin: Warning: You must manually configure OpenFirmware to boot. What does this mean? regards, Michael p.s. results follow. On Thu, Mar 21, 2013 at 9:50 PM, Lennart Sorensen < lsore...@csclub.uwaterloo.ca> wrote: > On Thu, Mar 21, 2013 at 07:09:22PM +0100, Michael Felt wrote: > > Thanks. But not knowing yaboot (yes, such people exist :p@me ) how do I > > verify what exists (I can do an install again, perhaps add the right > device > > string as well) and get it installed by ybin? > > > > Note: internet to server is currently down. Maintenance. > > I think you can look at the yaboot config file on the boot partition. > It is a text file. > > -- > Len Sorensen >
Re: Installation - boot after installation fails
The boot list shows: Version SF240_418 SMS 1.6 (c) Copyright IBM Corp. 2000,2005 All rights reserved. --- Select Device Device Current Device Number Position Name 1.3 Virtual Ethernet ( loc=U9115.505.062C0CA-V5-C4-T1 ) 2.2 SCSI 10737 MB Harddisk, part=1 () ( loc=U9115.505.062C0CA-V5-C2-T1-W8100-L0 ) 3.1 SCSI CD-ROM ( loc=U9115.505.062C0CA-V5-C2-T1-W8200-L0 ) Choose #2 System choose "Linux" by itself, and booted :) So, did I make a typo last time, or what do you suggest? (did it use "old" by accident?) regards, Michael On Sun, Mar 24, 2013 at 6:45 PM, Michael Felt wrote: > found it, yaboot.conf > > The original contents: > ## 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/disk/by-id/scsi-SAIX_VDASD_0002c0cad30001134deb16ba.4-part1" > device=/vdevice/v-scsi@3002/@1 > partition=2 > root="UUID=c9498eff-1727-4484-93e6-94249972c918" > timeout=50 > install=/usr/lib/yaboot/yaboot > enablecdboot > > image=/boot/vmlinux > label=Linux > read-only > initrd=/boot/initrd.img > > image=/boot/vmlinux.old > label=old > read-only > initrd=/boot/initrd.img.old > == > ~ # chroot /target > # ls boot > System.map-2.6.32-5-powerpc64 initrd.img-2.6.32-5-powerpc64 > config-2.6.32-5-powerpc64 vmlinux > initrd.img vmlinux-2.6.32-5-powerpc64 > # ls -l boot > total 24016 > -rw-r--r-- 1 root root 2344890 Feb 25 09:45 System.map-2.6.32-5-powerpc64 > -rw-r--r-- 1 root root93214 Feb 25 09:45 config-2.6.32-5-powerpc64 > lrwxrwxrwx 1 root root 29 Mar 24 18:15 initrd.img -> > initrd.img-2.6.32-5-powerpc64 > -rw-r--r-- 1 root root 10699255 Mar 24 18:18 initrd.img-2.6.32-5-powerpc64 > lrwxrwxrwx 1 root root 26 Mar 24 18:15 vmlinux -> > vmlinux-2.6.32-5-powerpc64 > -rw-r--r-- 1 root root 11403398 Feb 25 09:45 vmlinux-2.6.32-5-powerpc64 > > changed (/target)/etc/yaboot.conf to > ... > > boot="/dev/disk/by-id/scsi-SAIX_VDASD_0002c0cad30001134deb16ba.4-part1" > ## device=/vdevice/v-scsi@3002/@1 > device=/vdevice/v-scsi@3002/@8100:2 > partition=2 > root="UUID=c9498eff-1727-4484-93e6-94249972c918" > timeout=50 > install=/usr/lib/yaboot/yaboot > enablecdboot > > image=/boot/vmlinux > label=Linux > read-only > initrd=/boot/initrd.img > > deleted this part... > image=/boot/vmlinux.old > > ... > = > ybin says: > ybin: Warning: You must manually configure OpenFirmware to boot. > > What does this mean? > > regards, > Michael > > p.s. results follow. > > > On Thu, Mar 21, 2013 at 9:50 PM, Lennart Sorensen < > lsore...@csclub.uwaterloo.ca> wrote: > >> On Thu, Mar 21, 2013 at 07:09:22PM +0100, Michael Felt wrote: >> > Thanks. But not knowing yaboot (yes, such people exist :p@me ) how do I >> > verify what exists (I can do an install again, perhaps add the right >> device >> > string as well) and get it installed by ybin? >> > >> > Note: internet to server is currently down. Maintenance. >> >> I think you can look at the yaboot config file on the boot partition. >> It is a text file. >> >> -- >> Len Sorensen >> > >
Re: Installation - boot after installation fails
Repeat - to all this time: Does the info I found here need to go into a bug report, or has someone already collected the key information? regards, Michael On Sun, Mar 24, 2013 at 6:50 PM, Michael Felt wrote: > The boot list shows: > Version SF240_418 > SMS 1.6 (c) Copyright IBM Corp. 2000,2005 All rights reserved. > > --- > Select Device > Device Current Device > Number Position Name > 1.3 Virtual Ethernet > ( loc=U9115.505.062C0CA-V5-C4-T1 ) > 2.2 SCSI 10737 MB Harddisk, part=1 () > ( loc=U9115.505.062C0CA-V5-C2-T1-W8100-L0 ) > 3.1 SCSI CD-ROM > ( loc=U9115.505.062C0CA-V5-C2-T1-W8200-L0 ) > > > Choose #2 > > System choose "Linux" by itself, and booted :) > > So, did I make a typo last time, or what do you suggest? (did it use "old" > by accident?) > > regards, > Michael > > > > On Sun, Mar 24, 2013 at 6:45 PM, Michael Felt wrote: > >> found it, yaboot.conf >> >> The original contents: >> ## 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/disk/by-id/scsi-SAIX_VDASD_0002c0cad30001134deb16ba.4-part1" >> device=/vdevice/v-scsi@3002/@1 >> partition=2 >> root="UUID=c9498eff-1727-4484-93e6-94249972c918" >> timeout=50 >> install=/usr/lib/yaboot/yaboot >> enablecdboot >> >> image=/boot/vmlinux >> label=Linux >> read-only >> initrd=/boot/initrd.img >> >> image=/boot/vmlinux.old >> label=old >> read-only >> initrd=/boot/initrd.img.old >> == >> ~ # chroot /target >> # ls boot >> System.map-2.6.32-5-powerpc64 initrd.img-2.6.32-5-powerpc64 >> config-2.6.32-5-powerpc64 vmlinux >> initrd.img vmlinux-2.6.32-5-powerpc64 >> # ls -l boot >> total 24016 >> -rw-r--r-- 1 root root 2344890 Feb 25 09:45 System.map-2.6.32-5-powerpc64 >> -rw-r--r-- 1 root root93214 Feb 25 09:45 config-2.6.32-5-powerpc64 >> lrwxrwxrwx 1 root root 29 Mar 24 18:15 initrd.img -> >> initrd.img-2.6.32-5-powerpc64 >> -rw-r--r-- 1 root root 10699255 Mar 24 18:18 initrd.img-2.6.32-5-powerpc64 >> lrwxrwxrwx 1 root root 26 Mar 24 18:15 vmlinux -> >> vmlinux-2.6.32-5-powerpc64 >> -rw-r--r-- 1 root root 11403398 Feb 25 09:45 vmlinux-2.6.32-5-powerpc64 >> >> changed (/target)/etc/yaboot.conf to >> ... >> >> boot="/dev/disk/by-id/scsi-SAIX_VDASD_0002c0cad30001134deb16ba.4-part1" >> ## device=/vdevice/v-scsi@3002/@1 >> device=/vdevice/v-scsi@3002/@8100:2 >> partition=2 >> root="UUID=c9498eff-1727-4484-93e6-94249972c918" >> timeout=50 >> install=/usr/lib/yaboot/yaboot >> enablecdboot >> >> image=/boot/vmlinux >> label=Linux >> read-only >> initrd=/boot/initrd.img >> >> deleted this part... >> image=/boot/vmlinux.old >> >> ... >> = >> ybin says: >> ybin: Warning: You must manually configure OpenFirmware to boot. >> >> What does this mean? >> >> regards, >> Michael >> >> p.s. results follow. >> >> >> On Thu, Mar 21, 2013 at 9:50 PM, Lennart Sorensen < >> lsore...@csclub.uwaterloo.ca> wrote: >> >>> On Thu, Mar 21, 2013 at 07:09:22PM +0100, Michael Felt wrote: >>> > Thanks. But not knowing yaboot (yes, such people exist :p@me ) how do >>> I >>> > verify what exists (I can do an install again, perhaps add the right >>> device >>> > string as well) and get it installed by ybin? >>> > >>> > Note: internet to server is currently down. Maintenance. >>> >>> I think you can look at the yaboot config file on the boot partition. >>> It is a text file. >>> >>> -- >>> Len Sorensen >>> >> >> >
Re: Installation - boot after installation fails
I posted, i.e., mailed, a summary of what is needed for a successful install to 641...@bugs.debian.org. Have not seen anything show up on the list yet, so I hope it is "accepted". regards, Michael On Sun, Mar 17, 2013 at 8:01 PM, Michael Felt wrote: > Hello everyone, > > I downloaded the debian netinstaller - debian-6.0.7-powerpc-netinst.iso - > and installed on a p505. The installation process goes well, but the boot > fails. > > I tried using the LVM with multiple partitions and got this message > If you omit "device:" and "partno" yaboot will use the values of > "device=" and "partition=" in yaboot.conf, right now those are set to: > device=/vdevice/v-scsi@3002/@1 > partition=-1 > > And after a reinstall using the whole disk, no LVM I got: > If you omit "device:" and "partno" yaboot will use the values of > "device=" and "partition=" in yaboot.conf, right now those are set to: > device=/vdevice/v-scsi@3002/@1 > partition=2 > > The other key message, same for both is: > Please wait, loading kernel... > Can't open device > /vdevice/v-scsi@3002/@1:2,/boot/vmlinux: Unable to open file, Invalid > device > > I have located a number of bugs with "Invalid device" in them > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641852 > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637519 > > but these seem to be focused on issues with the installer and power7. My > question is about after the installation. > > How to proceed? How to document - better - what is wrong? > > Thanks. > > Michael > >
showstopper for debian-7.1.0-powerpc-netinst.iso on POWER5 (p505) and iscsi disk
Last march I started a thread - that with help - resolved the problem of installing from debian-6.0.7-powerpc-netinst.iso - and installed on a p505. downloading the new yaboot as part of the install (thanks to Lennart Sorensen for the hints/instructions that got me going) and I could install and boot! However, today I tried the debian-7.1.0-powerpc-netinst.iso and this is not successful - "out of the box". 1) entering "install" at the boot prompt brought me right back to the boot prompt, just pressing enter worked much better. 2) show stopper for an install on IBM POWER (p505) using vscsi for hdisk0. And again the "winner" is yaboot. ┌┤ [!!] Install yaboot on a hard disk ├─┐ ┌│ │ ││ No bootstrap partition found │ ││ No hard disks were found which have an "Apple_Bootstrap" partition. │ ││ You must create an 819200-byte partition with type "Apple_Bootstrap". │ ││ │ │││ └│ │ └───┘ I had chosen the option "whole disk" - all in one - recommended for new, and it created two partitions only (#2 ext4, and #5 swap). Is my assumption correct that I will need to use manual and create an additional partition named "Apple_Bootstrap" _(for now at least) - and if so, is there a preferred disk partition # to be used? Thanks for the feedback. p.s. a pointer to the bugs site is also welcome and I'll report and feed the bug report. Sincerely, Michael
Re: showstopper for debian-7.1.0-powerpc-netinst.iso on POWER5 (p505) and iscsi disk
Hi Frank, Thanks for the quick reply. I could follow your report a lot better than the archives from february. As I mentioned, I did an install using the 6.0.7 netinst iso image (is this squeeze?), using a vtopt DVD device. The problem I had is that the default grub did not assign the correct, nor could it boot from the device. Note: my hardware is "only" Power5, so I do not know how applicable this is for Power7. My VIOS is fairly current though (v2.2.2.+). In short, the only change I made was switching the netinst.iso from version 6.0.7 to 7.1.0. I have no clue how I would correct the problem of how the partition layout was made before: SCSI1 (0,1,0) (sda) - 10.7 GB AIX VDASDa x x > #1 primary7.3 MB B K a x x > #2 primary 10.2 GB F ext3/ a x x > #5 logical 504.4 MB F swapswapa x to what it made this evening (no screen capture, but I recall only two partitions: #2 ext4, and #5 swap. In short, whatever program is supposed to be making these partitions, is not. Also, I recall that it was calling it SCSI1 (0,3,0) - maybe because I modified disks and it know has LUN ID 0x8300, rather 0x8100 - would that have that effect (server is powered off, or I would look again). (atcually, not sure if it said SCSI1 - but I recall being surprised by the (0,3,0) identifier/string. When I have more time I will do the install again, and make a screen shot. regards, Michael On Tue, Aug 6, 2013 at 5:23 AM, Frank Fegert wrote: > Hello Michael, > > On Tue, Aug 06, 2013 at 03:44:01AM +0800, Michael Felt wrote: > > [...] > > > > ??? [!!] Install yaboot on a hard disk > ? > > ?? > ??? > > ?? No bootstrap partition found >??? > > ?? No hard disks were found which have an "Apple_Bootstrap" > partition. ??? > > ?? You must create an 819200-byte partition with type > "Apple_Bootstrap". ??? > > ?? > ??? > > ?? > ??? > > ?? > ??? > > > > > > > I had chosen the option "whole disk" - all in one - recommended for new, > > and it created two partitions only (#2 ext4, and #5 swap). > > > > Is my assumption correct that I will need to use manual and create an > > additional partition named "Apple_Bootstrap" _(for now at least) - and if > > so, is there a preferred disk partition # to be used? > > > > Thanks for the feedback. > > > > p.s. a pointer to the bugs site is also welcome and I'll report and feed > > the bug report. > > do you per chance have the d-i ISO image mounted via a VTOPT device > from e.g. a underlying VIO server? If so, please take a look at: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=352914 > > starting at Message #194. Or the mailing list archive here: > http://lists.debian.org/debian-powerpc/2013/02/msg00023.html > > In my case it turned out the installer did everything fine WRT the > partition layout, but the "find-partitions" command used to detect > the "Apple_Bootstrap" partition stumbled upon the ISO image mounted > via a VTOPT from the VIO server. See here for a full writeup of the > whole ordeal: > http://www.bityard.org/blog/2013/02/17/debian_wheezy_on_ibm_power > > According to the latest update in the bug report this issue should > be fixed in more recent versions of the d-i. Didn't test this with > the new versions though ... > > HTH & best regards, > > Frank Fegert >
Fwd: Re: showstopper for debian-7.1.0-powerpc-netinst.iso on POWER5 (p505) and iscsi disk
forgot reply all... -- Forwarded message -- From: "Lennart Sorensen" Date: Aug 7, 2013 10:40 PM Subject: Re: showstopper for debian-7.1.0-powerpc-netinst.iso on POWER5 (p505) and iscsi disk To: "Michael Felt" Cc: On Tue, Aug 06, 2013 at 03:44:01AM +0800, Michael Felt wrote: > Last march I started a thread - that with help - resolved the problem of > installing from > debian-6.0.7-powerpc-netinst.iso - and installed on a p505. downloading the > new yaboot as part of the install (thanks to Lennart Sorensen for the > hints/instructions that got me going) and I could install and boot! > > However, today I tried the debian-7.1.0-powerpc-netinst.iso and this is > not successful - "out of the box". > > 1) entering "install" at the boot prompt brought me right back to the boot > prompt, just pressing enter worked much better. > > 2) show stopper for an install on IBM POWER (p505) using vscsi for hdisk0. > And again the "winner" is yaboot. > >┌┤ [!!] Install yaboot on a hard disk ├─┐ > ┌│ │ > ││ No bootstrap partition found │ > ││ No hard disks were found which have an "Apple_Bootstrap" partition. │ > ││ You must create an 819200-byte partition with type "Apple_Bootstrap". │ > ││ │ > ││ │ > └│ │ > └───┘ > > I had chosen the option "whole disk" - all in one - recommended for new, > and it created two partitions only (#2 ext4, and #5 swap). > > Is my assumption correct that I will need to use manual and create an > additional partition named "Apple_Bootstrap" _(for now at least) - and if > so, is there a preferred disk partition # to be used? > > Thanks for the feedback. > > p.s. a pointer to the bugs site is also welcome and I'll report and feed > the bug report. I don't think your IBM box needs an Apple_Bootstrap partition, but I might be remembering wrong given after trying to deal with yaboot, I switched to grub and had enough email exchanges with the grub develoeprs to get grub2 working on the IBM boxes with software RAID. I really like that setup much better. We currently have both a p520 and a p710 booting of software raid with grub2. -- Len Sorensen
Re: Re: showstopper for debian-7.1.0-powerpc-netinst.iso on POWER5 (p505) and iscsi disk
Well, I tried the install again. ANd made a small change. The previous attempt was using a logical volume as the data area exported to the partition as hdisk0. I'll repeat that later - as a test. However, when installing to an iscsi disk (exported via vscsi to client, so iscsi mounted by the VIOS - I do this regularly for AIX installs). I get a disk partiton proposal that I expect: +-¦ [!] Partition disks +-+ ¦ ¦ ¦ Selected for partitioning: ¦ ¦ ¦ ¦ SCSI1 (0,1,0) (sda) - AIX VDASD: 12.9 GB ¦ ¦ ¦ ¦ The disk can be partitioned using one of several different schemes. ¦ ¦ If you are unsure, choose the first one. ¦ ¦ ¦ ¦ Partitioning scheme: ¦ ¦ ¦ ¦All files in one partition (recommended for new users) ¦ ¦Separate /home partition ¦ ¦Separate /home, /usr, /var, and /tmp partitions ¦ ¦ ¦ ¦ ¦ ¦ ¦ +-+ This is with an iscsi disk being presented via vscsi interface +¦ [!!] Partition disks +-+ ¦ ¦ ¦ This is an overview of your currently configured partitions and mount ¦ ¦ points. Select a partition to modify its settings (file system, mount ¦ ¦ point, etc.), a free space to create partitions, or a device to ¦ ¦ initialize its partition table. ¦ ¦ ¦ ¦ Configure the Logical Volume Manager ¦ ¦ Configure encrypted volumes¦ ¦ ¦ ¦ ¦ ¦ SCSI1 (0,1,0) (sda) - 12.9 GB AIX VDASD¦ ¦ ¦ > #1 primary7.3 MB B K ¦ ¦ ¦ > #2 primary 12.3 GB f ext4/ ¦ ¦ ¦ > #5 logical 591.4 MB f swapswap¦ ¦ ¦ ¦ ¦ ¦ Undo changes to partitions ¦ ¦ Finish partitioning and write changes to disk ¦ ¦ ¦ ¦ ¦ ¦ ¦ +-+ But, in the end, install fails - no recognizable boot partition. However, when studying what was made - the partitioner seems to know what is about: +¦ [!!] Partition disks +-+ ¦ ¦ ¦ You are editing partition #1 of SCSI1 (0,1,0) (sda). No existing file ¦ ¦ system was detected in this partition. ¦ ¦ ¦ ¦ Partition settings: ¦ ¦ ¦ ¦ Use as: PowerPC PReP boot partition ¦ ¦ ¦ ¦ Bootable flag: on ¦ ¦ ¦ ¦ Copy data from another partition ¦ ¦ Erase data on this partition ¦ ¦ Delete the partition ¦ ¦ Done setting up the partition ¦ ¦ ¦ ¦ ¦ ¦ ¦ +-+ So, is this a bug - in what, and if so, where do I submit my findings? regards, Michael On Thu, Aug 8, 2013 at 5:16 PM, Michael Felt wrote: > forgot reply all... > -- Forwarded message -- > From: "Lennart Sorensen" > Date: Aug 7, 2013 10:40 PM > Subject: Re: showstopper for debian-7.1.0-powerpc-netinst.iso on POWER5 > (p505) and iscsi disk > To: "Michael Felt" > Cc: > > On Tue, Aug 06, 2013 at 03:44:01AM +0800, Michael Felt wrote: > > Last march I started a thread - that with help - resolved the problem of > > installing from > > debian-6.0.7-powerpc-netinst.iso - and installed on a p505. downloading > the > > new yaboot as part of the install (thanks to Lennart Sorensen for the > > hints/instructions that got me going) and I could install and boot! > > > > However, today I tried the debian-7.1.0-powerpc-netinst.iso and this is > > not successful - "out of the box". > > > > 1) entering "install" at the boot prompt brought me right back to the > boot > > prompt, just pressing enter worked much better. > > > > 2) show stopper for an install on IBM POWER (p505) using vscsi for > hdisk0. > > And again the "winner" is yaboot. > > > >┌┤ [!!] Install yaboot on a hard disk > ├─┐ > > ┌│ > │ > > ││ No bootstrap partition found >│ > > ││ No hard disks were found which have an "Apple_Bootstrap" partition. > │ > > ││ You must create an 819200-byte partition with type > "Apple_Bootstrap". │ > > ││ > │ > > ││ > │ > > └│ > │ > > > └───┘ > > > > I had chosen the option "whole disk" - all in one - recommended f
Re: Re: showstopper for debian-7.1.0-powerpc-netinst.iso on POWER5 (p505) and iscsi disk
Update: same hw configuration - but using the netinst 6.0.7 iso image for boot and installation. Where the 7.1.0 says no where to go, the 6.0.7 one says: ┌─┤ [!!] Install yaboot on a hard disk ├──┐ │ │ │ Yaboot (the Linux boot loader) needs to be installed on a hard disk │ │ partition in order for your system to be bootable. Please choose the │ │ destination partition from among these partitions that have the │ │ bootable flag set. │ │ │ │ Warning: this will erase all data on the selected partition! │ │ │ │ Device for boot loader installation: │ │ │ │ /dev/sda1 │ │ │ │ │ │ │ └─┘ My suspicion is that it is a bug in "something" - yaboot, or the installer, that "something" does not recognize the partition type "PowerPC PReP boot partition". Ideas - better suggestions! Michael On Thu, Aug 8, 2013 at 6:59 PM, Michael Felt wrote: > Well, I tried the install again. ANd made a small change. The previous > attempt was using a logical volume as the data area exported to the > partition as hdisk0. I'll repeat that later - as a test. However, when > installing to an iscsi disk (exported via vscsi to client, so iscsi mounted > by the VIOS - I do this regularly for AIX installs). > I get a disk partiton proposal that I expect: > > > +-¦ [!] Partition disks > +-+ > > ¦ ¦ > ¦ Selected for > partitioning: ¦ > > ¦ ¦ > ¦ SCSI1 (0,1,0) (sda) - AIX VDASD: 12.9 > GB¦ > > ¦ ¦ > ¦ The disk can be partitioned using one of several different > schemes. ¦ > ¦ If you are unsure, choose the first > one.¦ > > ¦ ¦ > ¦ Partitioning > scheme:¦ > > ¦ ¦ > ¦All files in one partition (recommended for new > users) ¦ > ¦Separate /home > partition ¦ > ¦Separate /home, /usr, /var, and /tmp > partitions ¦ > > ¦ ¦ > ¦ Back> ¦ > > ¦ ¦ > > +-+ > > This is with an iscsi disk being presented via vscsi interface > > > +¦ [!!] Partition disks > +-+ > > ¦ ¦ > ¦ This is an overview of your currently configured partitions and > mount ¦ > ¦ points. Select a partition to modify its settings (file system, > mount ¦ > ¦ point, etc.), a free space to create partitions, or a device > to ¦ > ¦ initialize its partition > table. ¦ > > ¦ ¦ > ¦ Configure the Logical Volume > Manager ¦ > ¦ Configure encrypted volumes > ¦ ¦ > ¦ > ¦ ¦ > ¦ SCSI1 (0,1,0) (sda) - 12.9 GB AIX VDASD > ¦ ¦ > ¦ > #1 primary7.3 MB B K > ¦ ¦ > ¦ > #2 primary 12.3 GB f ext4/ > ¦ ¦ > ¦ > #5 logical 591.4 MB f swapswap > ¦ ¦ > ¦ > ¦ ¦ > ¦ Undo changes to > partitions ¦ > ¦ Finish partitioning and write changes to > disk ¦ > > ¦ ¦ > ¦ Back> ¦ > > ¦ ¦ > > +-+ > > But, in the end, install fails - no recognizable boot partition. > > > > However, when studying what was made - the pa
Re: Re: showstopper for debian-7.1.0-powerpc-netinst.iso on POWER5 (p505) and vscsi disk (was iscsi)
On Thu, Aug 8, 2013 at 7:56 PM, Michael Felt wrote: > Update: same hw configuration - but using the netinst 6.0.7 iso image for > boot and installation. Where the 7.1.0 says no where to go, the 6.0.7 one > says: > > ┌─┤ [!!] Install yaboot on a hard disk > ├──┐ > > │ │ > │ Yaboot (the Linux boot loader) needs to be installed on a hard > disk │ > │ partition in order for your system to be bootable. Please choose > the │ > │ destination partition from among these partitions that have > the │ > │ bootable flag > set. │ > > │ │ > │ Warning: this will erase all data on the selected > partition!│ > > │ │ > │ Device for boot loader > installation:│ > > │ │ > │ > /dev/sda1 │ > > │ │ > │ Back> │ > > │ │ > > └─┘ > > My suspicion is that it is a bug in "something" - yaboot, or the > installer, that "something" does not recognize the partition type "PowerPC > PReP boot partition". > > Ideas - better suggestions! > > Michael > > On Thu, Aug 8, 2013 at 6:59 PM, Michael Felt wrote: > >> Well, I tried the install again. ANd made a small change. The previous >> attempt was using a logical volume as the data area exported to the >> partition as hdisk0. I'll repeat that later - as a test. However, when >> installing to an iscsi disk (exported via vscsi to client, so iscsi mounted >> by the VIOS - I do this regularly for AIX installs). >> I get a disk partiton proposal that I expect: >> >> >> +-¦ [!] Partition disks >> +-+ >> >> ¦ ¦ >> ¦ Selected for >> partitioning: ¦ >> >> ¦ ¦ >> ¦ SCSI1 (0,1,0) (sda) - AIX VDASD: 12.9 >> GB¦ >> >> ¦ ¦ >> ¦ The disk can be partitioned using one of several different >> schemes. ¦ >> ¦ If you are unsure, choose the first >> one.¦ >> >> ¦ ¦ >> ¦ Partitioning >> scheme:¦ >> >> ¦ ¦ >> ¦All files in one partition (recommended for new >> users) ¦ >> ¦Separate /home >> partition ¦ >> ¦Separate /home, /usr, /var, and /tmp >> partitions ¦ >> >> ¦ ¦ >> ¦ > Back> ¦ >> >> ¦ ¦ >> >> +-+ >> >> This is with an iscsi disk being presented via vscsi interface >> >> >> +¦ [!!] Partition disks >> +-+ >> >> ¦ ¦ >> ¦ This is an overview of your currently configured partitions and >> mount ¦ >> ¦ points. Select a partition to modify its settings (file system, >> mount ¦ >> ¦ point, etc.), a free space to create partitions, or a device >> to ¦ >> ¦ initialize its partition >> table. ¦ >> >> ¦ ¦ >> ¦ Configure the Logical Volume >> Manager
Re: Re: showstopper for debian-7.1.0-powerpc-netinst.iso on POWER5 (p505) and iscsi disk
Just tried a netinst again yesterday - and was surprised that the PReP boot partition is now recognized. Boot starts, but fails at. boot: Linux Please wait, loading kernel... Elf64 kernel loaded... Loading ramdisk... ext2: i/o error 2133571364 in read ramdisk loaded at 0170, size: 8192 Kbytes OF stdout device is: /vdevice/vty@3000 Preparing to boot Linux version 3.2.0-4-powerpc64 (debian-ker...@lists.debian.or [0.504591] Initializing network drop monitor service [0.504850] List of all partitions: [0.504859] No filesystem could mount root, tried: [0.504873] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [0.504883] Call Trace: [0.504895] [c0007e47fc30] [c00134e0] .show_stack+0x80/0x130 (unreliable) [0.504912] [c0007e47fce0] [c04b9054] .panic+0x88/0x204 [0.504927] [c0007e47fd80] [c0676f3c] .mount_block_root+0x2b0/0x2c8 [0.504953] [c0007e47fe50] [c0677140] .prepare_namespace+0x170/0x1b0 [0.504968] [c0007e47fee0] [c0676b14] .kernel_init+0x204/0x20c [0.504982] [c0007e47ff90] [c001ca0c] .kernel_thread+0x54/0x70 [0.510270] Rebooting in 180 seconds..EPOW <0x6440040006c 0x0 0x0> As the initial "complaint" seems to be solved for netinst, going to try DVD install (and see if I can look at the current yaboot.conf, etc.. to figure out what is going wrong. One thing I noticed, that is a surprise is: [0.00] Using 1TB segments As I do not think my model support 1TB segments but later may be okay as: [0.469005] HugeTLB registered 16 MB page size, pre-allocated 0 pages [0.469021] HugeTLB registered 16 GB page size, pre-allocated 0 pages Anyway, a lot to learn. Thanks to whoever for fixing the yaboot installation error (or did I fix it by having done an install with 6.0.7 - question: should I zero out the disk and try a netinst again?) On Thu, Aug 8, 2013 at 4:00 PM, Lennart Sorensen < lsore...@csclub.uwaterloo.ca> wrote: > On Thu, Aug 08, 2013 at 06:59:01PM +0800, Michael Felt wrote: > > Well, I tried the install again. ANd made a small change. The previous > > attempt was using a logical volume as the data area exported to the > > partition as hdisk0. I'll repeat that later - as a test. However, when > > installing to an iscsi disk (exported via vscsi to client, so iscsi > mounted > > by the VIOS - I do this regularly for AIX installs). > > I get a disk partiton proposal that I expect: > > > > > > +-¦ [!] Partition disks > > +-+ > > ¦ > > ¦ > > ¦ Selected for partitioning: > > ¦ > > ¦ > > ¦ > > ¦ SCSI1 (0,1,0) (sda) - AIX VDASD: 12.9 GB > > ¦ > > ¦ > > ¦ > > ¦ The disk can be partitioned using one of several different schemes. > > ¦ > > ¦ If you are unsure, choose the first one. > > ¦ > > ¦ > > ¦ > > ¦ Partitioning scheme: > > ¦ > > ¦ > > ¦ > > ¦All files in one partition (recommended for new users) > > ¦ > > ¦Separate /home partition > > ¦ > > ¦Separate /home, /usr, /var, and /tmp partitions > > ¦ > > ¦ > > ¦ > > ¦ > > ¦ > > ¦ > > ¦ > > > > > +-+ > > > > This is with an iscsi disk being presented via vscsi interface > > > > > > +¦ [!!] Partition disks > > +-+ > > ¦ > > ¦ > > ¦ This is an overview of your currently configured partitions and mount > > ¦ > > ¦ points. Select a partition to modify its settings (file system, mount > > ¦ > > ¦ point, etc.), a free space to create partitions, or a device to > > ¦ > > ¦ initialize its partition table. > > ¦ > > ¦ > > ¦ > > ¦ Configure the Logical Volume Manager > > ¦ > > ¦ Configure encrypted volumes¦ > > ¦ > > ¦ ¦ > > ¦ > > ¦ SCSI1 (0,1,0) (sda) - 12.9 GB AIX VDASD¦ > > ¦ > > ¦ > #1 primary7.3 MB B K ¦ > > ¦ > > ¦ > #2 primary 12.3 GB f ext4/ ¦ > > ¦ > > ¦ > #5 logical 591.4 MB f swapswap¦ > > ¦ > > ¦ ¦ > > ¦ > > ¦ Undo cha
Re: Re: showstopper for debian-7.1.0-powerpc-netinst.iso on POWER5 (p505) and iscsi disk
Well, this seems to be solved - as long as you load for the target initrd So, you must choose "expert" for the install method, and when the procedure prompts: +-¦ [?] Install the base system +-+ ¦ ¦ ¦ The primary function of an initrd is to allow the kernel to mount the ¦ ¦ root file system. It therefore needs to contain all drivers and ¦ ¦ supporting programs required to do that. ¦ ¦ ¦ ¦ A generic initrd is much larger than a targeted one and may even be ¦ ¦ so large that some boot loaders are unable to load it but has the ¦ ¦ advantage that it can be used to boot the target system on almost any ¦ ¦ hardware. With the smaller targeted initrd there is a very small ¦ ¦ chance that not all needed drivers are included. ¦ ¦ ¦ ¦ Drivers to include in the initrd: ¦ ¦ ¦ ¦generic: include all available drivers ¦ ¦targeted: only include drivers needed for this system ¦ ¦ ¦ ¦ ¦ ¦ ¦ +-+ Be sure and choose "targeted". Hope this helps! On Sun, Aug 11, 2013 at 3:18 PM, Michael Felt wrote: > Just tried a netinst again yesterday - and was surprised that the PReP > boot partition is now recognized. > > Boot starts, but fails at. > > boot: Linux > Please wait, loading kernel... >Elf64 kernel loaded... > Loading ramdisk... > ext2: i/o error 2133571364 in read > ramdisk loaded at 0170, size: 8192 Kbytes > OF stdout device is: /vdevice/vty@3000 > Preparing to boot Linux version 3.2.0-4-powerpc64 > (debian-ker...@lists.debian.or > > > [0.504591] Initializing network drop monitor service > [0.504850] List of all partitions: > [0.504859] No filesystem could mount root, tried: > [0.504873] Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(0,0) > [0.504883] Call Trace: > [0.504895] [c0007e47fc30] [c00134e0] > .show_stack+0x80/0x130 (unreliable) > [0.504912] [c0007e47fce0] [c04b9054] .panic+0x88/0x204 > [0.504927] [c0007e47fd80] [c0676f3c] > .mount_block_root+0x2b0/0x2c8 > [0.504953] [c0007e47fe50] [c0677140] > .prepare_namespace+0x170/0x1b0 > [0.504968] [c0007e47fee0] [c0676b14] > .kernel_init+0x204/0x20c > [0.504982] [c0007e47ff90] [c001ca0c] > .kernel_thread+0x54/0x70 > [0.510270] Rebooting in 180 seconds..EPOW <0x6440040006c 0x0 0x0> > > As the initial "complaint" seems to be solved for netinst, going to try > DVD install (and see if I can look at the current yaboot.conf, etc.. to > figure out what is going wrong. > > One thing I noticed, that is a surprise is: > [0.00] Using 1TB segments > As I do not think my model support 1TB segments > > but later may be okay as: > [0.469005] HugeTLB registered 16 MB page size, pre-allocated 0 pages > [0.469021] HugeTLB registered 16 GB page size, pre-allocated 0 pages > > Anyway, a lot to learn. > > Thanks to whoever for fixing the yaboot installation error (or did I fix > it by having done an install with 6.0.7 - question: should I zero out the > disk and try a netinst again?) > > > On Thu, Aug 8, 2013 at 4:00 PM, Lennart Sorensen < > lsore...@csclub.uwaterloo.ca> wrote: > >> On Thu, Aug 08, 2013 at 06:59:01PM +0800, Michael Felt wrote: >> > Well, I tried the install again. ANd made a small change. The previous >> > attempt was using a logical volume as the data area exported to the >> > partition as hdisk0. I'll repeat that later - as a test. However, when >> > installing to an iscsi disk (exported via vscsi to client, so iscsi >> mounted >> > by the VIOS - I do this regularly for AIX installs). >> > I get a disk partiton proposal that I expect: >> > >> > >> > +-¦ [!] Partition disks >> > +-+ >> > ¦ >> > ¦ >> > ¦ Selected for partitioning: >> > ¦ >> > ¦ >> > ¦ >> > ¦ SCSI1 (0,1,0) (sda) - AIX VDASD: 12.9 GB >> > ¦ >> > ¦ >> > ¦ >> > ¦ The disk can be partitioned using one of several different schemes. >> > ¦ >> > ¦ If you are unsure, choose the first one. >> > ¦ >> > ¦ >> > ¦ >> > ¦ Partitioning scheme: >> > ¦ >> > ¦ >> > ¦ >> > ¦All files in one partition (recommended for new users) >> > ¦ >> > ¦Separate /home part
Re: HELP: test kernel patches on the real thing -- installs but won't reboot after install...
I have not read, not looked for an netinst image - if so, I can test on Power6 in any case (using VIOS for virtual ethernet and vscsi for network and disk devices). On Tue, Apr 28, 2015 at 12:56 PM, Rick Thomas wrote: > > On Apr 27, 2015, at 4:22 PM, Rick Thomas wrote: > > On 4/27/2015 1:46 PM, Milan Kupcevic wrote: > >> On 04/27/2015 04:21 PM, Rick Thomas wrote: > >>> I have a dual processor G5 tower Mac that has the “wind tunnel” > >>> problem. > >> Do you have this problem with the final Jessie release? > >> Milan > > I haven't tried Jessie final release on it yet. I'll give it a shot > tonight. > > Enjoy! > > Rick > > I tried installing jessie final on it. The installer runs OK to > completion but when it comes time to reboot into the installed system, I > get “Loading second stage bootloader…” and a folder icon with a blinking > “?” in the middle. > > I tried booting from the DVD in “rescue” mode and installing the bootstrap > again from the rescue menu. No help… > > The machine in question is a Power Mac dual core G5 similar to the one > shown on this web page — > > http://www.everymac.com/systems/apple/powermac_g5/specs/powermac_g5_dual_2.0.html > > Also, the installer seemed to have trouble getting an IPv4 dhcp address > (though it does fine at getting an IPv6 address from the local router — so > it looks like there’s no problem with the network hardware.) > > I’ve had wheezy installed and running happily on this machine recently. > > Any thoughts? > > Rick > > -- > To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > Archive: > https://lists.debian.org/9fbb3ad1-d37f-43fe-a859-62af7abab...@pobox.com > >
Re: Help with the arm64 and ppc64el installation-guides needed
By the way - I just looked at your installation instructions and I did not find anything about how to install in POWER Server environment, i.e., as a virtual machine (aka LPAR) on IBM POWER5 and later. The ppc64le using KVM will obviously be different, but people using powerpc (historically 32-bit - is that correct, and why I cannot SMOKE perl with -Duse64bitall ?). Anyway - I have an installation 'story' I wrote up quite a while ago. http://www.rootvg.net/content/view/560/88/ I just reused this procedure to install Jessie and it still works fine. I like the command-line install very much. One of my reasons that debian is my personal favorite for Linux on Power. BTW: I notice a slight difference in how 'login as root' works between wheezy and jessie. On both systems I have enabled 'root login' for my initial tests. With wheezy I cannot login as root on the console, but can login using ssh. On Jessie this is the reverse. I assume this is deliberate. (I'll open a new thread to ask how to manage this, because sshd_config - which I know - seems to permit RootLogin (--without-password) but I have not managed to get it to work. Normally I do not want this, but for testing - logging in as root is how I start learning many things (i.e., I skip installing sudo and sudo su -). So, the question for here - regarding documentation - is there a CHANGES document I have missed that summarizes and/or details the changes (intended) between wheezy and jessie? Michael On Mon, Apr 13, 2015 at 9:46 PM, Holger Wansing wrote: > Hi, > > "Lennart Sorensen" wrote: > > On Mon, Apr 13, 2015 at 09:37:42PM +0200, Holger Wansing wrote: > > > Hi, > > > > > > Samuel Thibault wrote: > > > > Holger Wansing, le Sat 11 Apr 2015 17:13:06 +0200, a écrit : > > > > > +arch_porturl="ppc64el" > > > > > +arch_listname="ppc64el" > > > > > > > > Please take care when updating these to be sure to understand > > > > what they mean. http://www.debian.org/ports/ppc64el and > > > > http://lists.debian.org/debian-ppc64el don't exist. > > > > > > I knew this! > > > But there needs to be created a site under > > > http://www.debian.org/ports/ for ppc64el, when ppc64el gets a release > arch. > > > The only page for ppc64el on the ports page ATM is on the debian wiki. > > > That will have to be changed. > > > Otherwise that above entity in our d-i manual will fail to work, no > > > matter which arch name you choose. > > > > I would think that just like armhf uses the debian-arm list, ppc64el > > will continue to use the debian-powerpc list. > > Yeah, I just saw that Samuel left the above entities at "powerpc". > That does of course work :-) > > > Holger > > -- > > Created with Sylpheed 3.2.0 under > D E B I A N L I N U X 7 . 0 W H E E Z Y ! > > Registered Linux User #311290 - https://linuxcounter.net/ > > > > -- > To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > Archive: > https://lists.debian.org/20150413214642.d550d8d8f90c341da72e7...@wansing-online.de > >
Re: Help with the arm64 and ppc64el installation-guides needed
Maybe - last time I tried - I mistyped the login - because login from console is working for both - thanks for the reply. re: root login on sshd - guess I need to read more carefully. I know about the cipher changes starting with OpenSSH 6.7, but had not yet stumbled on anything extra blocking root login. My apologies for a false statement! Must test again and again (so I will have to reload ubuntu, opensles and fedora to see which ones of those refuse root login at console. If both are blocked (with the newer openssh) may make some maintenance work difficult. Further - any interest in a different (in what way please) story on installing debian on PowerVM enabled systems? On Sat, May 2, 2015 at 2:16 PM, Ben Hutchings wrote: > On Sat, 2015-05-02 at 11:15 +0200, Michael Felt wrote: > [...] > > > BTW: I notice a slight difference in how 'login as root' works between > > wheezy and jessie. On both systems I have enabled 'root login' for my > > initial tests. With wheezy I cannot login as root on the console, but > > can login using ssh. On Jessie this is the reverse. I assume this is > > deliberate. > [...] > > The ssh part: yes, and that's documented in the release notes: > < > https://www.debian.org/releases/jessie/powerpc/release-notes/ch-information.en.html#openssh > >. > > The console part: I don't think so; this is probably a bug in wheezy. > The last time I had that sort of problem, it was due to an omission from > the file /etc/securetty (list of devices that root may log in through). > But in wheezy that file does include hvc0. > > Ben. > > -- > Ben Hutchings > Q. Which is the greater problem in the world today, ignorance or apathy? > A. I don't know and I couldn't care less. >
Re: Help with the arm64 and ppc64el installation-guides needed
Just read the link re: PermitRoot --without-password My comment - typical "developer" string - because many people are looking for passwordless login for root, and from my UNIX background I would take "--without-password" very literally. I suspect what is intended is "--no-password-auth-permitted", meaning some other form of authentication is accepted, e.g., PKI. Because of the comment in sshd_config I was thinking it was something in the PAM configuration I needed to look at. And, FYI - if you follow the suggestion in the sshd_config (re PAM) no login for anyone (using passwords at least) is permitted. Thank you for the link - I shall copy my keys in (later) and report back. And secondly, for the link - for the changes history! Excellent! Michael On Sat, May 2, 2015 at 6:19 PM, Michael Felt wrote: > Maybe - last time I tried - I mistyped the login - because login from > console is working for both - thanks for the reply. > > re: root login on sshd - guess I need to read more carefully. I know about > the cipher changes starting with OpenSSH 6.7, but had not yet stumbled on > anything extra blocking root login. > > My apologies for a false statement! Must test again and again (so I will > have to reload ubuntu, opensles and fedora to see which ones of those > refuse root login at console. If both are blocked (with the newer openssh) > may make some maintenance work difficult. > > Further - any interest in a different (in what way please) story on > installing debian on PowerVM enabled systems? > > On Sat, May 2, 2015 at 2:16 PM, Ben Hutchings wrote: > >> On Sat, 2015-05-02 at 11:15 +0200, Michael Felt wrote: >> [...] >> >> > BTW: I notice a slight difference in how 'login as root' works between >> > wheezy and jessie. On both systems I have enabled 'root login' for my >> > initial tests. With wheezy I cannot login as root on the console, but >> > can login using ssh. On Jessie this is the reverse. I assume this is >> > deliberate. >> [...] >> >> The ssh part: yes, and that's documented in the release notes: >> < >> https://www.debian.org/releases/jessie/powerpc/release-notes/ch-information.en.html#openssh >> >. >> >> The console part: I don't think so; this is probably a bug in wheezy. >> The last time I had that sort of problem, it was due to an omission from >> the file /etc/securetty (list of devices that root may log in through). >> But in wheezy that file does include hvc0. >> >> Ben. >> >> -- >> Ben Hutchings >> Q. Which is the greater problem in the world today, ignorance or apathy? >> A. I don't know and I couldn't care less. >> > >
Re: Guide to getting ported?
I probably do not know enough to write it well enough myself - mainly because I am unsure of your intended audience. If it is debian you may only be interested in porting between different linux versions - which could be 'tricky' in itself. However, I see you mention 'OpenBSD', and linuxisms. Why not 'POSIX'? Why not compiler differences (even different versions of gcc have key differences). As "aixtools" I try to package (port) open-source to AIX and the main problems I run into is that for literally one function in a complex library (e.g., glib) that has nearly impossible demands to meet on a non-linux platform (i.e., they 'demand' a feature of gcc for packaging the complete library) using it's legacy compiler - means the package will likely never be ported or maintained outside of a linux environment - where gcc is the 'native' compiler, plus glibc (which is different that POSIX libc) - aka run-time environments. As I said above, I am probably not the right person to right this - alone at least. But I do feel some 'guidance' about how to design and develop with portability in mind. Every dependency added (because it was there) adds a potential for a security breach via those dependencies (and their respective dependencies). Portability is not 'for free' - it requires planning and documentation. While it might be a 'hassle' your code might be mich more secure, and certainly easier to port, if you look at the (one) function you are using from a someone else's library - and embed it in your code. That is, rather than just a list of soem areas that affect portability - think about a high-level description of the common causes of 'lack of portability' and how to test and/or code for exposure to these common causes. Sometimes it is 'as simple' as finding (multiple) someone(s) with another platform who just tries to package (or just make install) it. Also test that 'make DESTDIR=/some/where/else install' works well. p.s. - Very glad to see you are opening the discussion! Michael On Sat, May 2, 2015 at 1:32 AM, Steven Chamberlain wrote: > Hi, > > Paul Wise wrote: > > Do any porters have any input on this page? > > https://wiki.debian.org/GettingPorted > > This page seems it will be useful; I will add some bits to it. > > Regards, > -- > Steven Chamberlain > ste...@pyro.eu.org > > > -- > To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > Archive: https://lists.debian.org/20150501233237.gc46...@pyro.eu.org > >
Re: Help with the arm64 and ppc64el installation-guides needed
Maybe something else to add to the release notes - the new /etc/NetworkManager/* (I hate long names and caps - I know this is not UNIX, but one of the goals of UNIX was to keep things short, fewer key presses, and less output (the example given was IBM 'mainframe' that gave a page of text for a command that had no output - making it much easier to start the 'pipe' concept - only send the output) compared to /etc/network/* for configuring (static) interfaces. imho a real pain - every distribution of Linux has a different way of doing things (although I am beginning to think it is a different version of Linux - change things because we can - because every distribution of Linux seems to be a different version of Linux). Previous UNIX vendors would have been hung out to dry for this kind of 'change management (read mis-management). (imho). Anyway, please add NetworkManager - and other core Linux changes, or a link to 'Linux-world' changes - although I would expect Debian to take responsibility for the list of changes between: Linux wheezy 3.2.0-4-powerpc64 #1 SMP Debian 3.2.68-1+deb7u1 ppc64 GNU/Linux and Linux jessie 3.16.0-4-powerpc64 #1 SMP Debian 3.16.7-ckt9-3 (2015-04-23) ppc64 GNU/Linux my two cents. On Sat, May 2, 2015 at 2:16 PM, Ben Hutchings wrote: > On Sat, 2015-05-02 at 11:15 +0200, Michael Felt wrote: > [...] > > > BTW: I notice a slight difference in how 'login as root' works between > > wheezy and jessie. On both systems I have enabled 'root login' for my > > initial tests. With wheezy I cannot login as root on the console, but > > can login using ssh. On Jessie this is the reverse. I assume this is > > deliberate. > [...] > > The ssh part: yes, and that's documented in the release notes: > < > https://www.debian.org/releases/jessie/powerpc/release-notes/ch-information.en.html#openssh > >. > > The console part: I don't think so; this is probably a bug in wheezy. > The last time I had that sort of problem, it was due to an omission from > the file /etc/securetty (list of devices that root may log in through). > But in wheezy that file does include hvc0. > > Ben. > > -- > Ben Hutchings > Q. Which is the greater problem in the world today, ignorance or apathy? > A. I don't know and I couldn't care less. >
Re: Help with the arm64 and ppc64el installation-guides needed
And last little bit - what is the linux world thinking - spaces in file names? Good grief. (as well as very long names). root@jessie:/etc/NetworkManager# ls -l system* total 4 -rw--- 1 root root 260 May 1 22:44 Wired connection 1 On Sun, May 3, 2015 at 2:49 PM, Michael Felt wrote: > Maybe something else to add to the release notes - the new > /etc/NetworkManager/* (I hate long names and caps - I know this is not > UNIX, but one of the goals of UNIX was to keep things short, fewer key > presses, and less output (the example given was IBM 'mainframe' that gave a > page of text for a command that had no output - making it much easier to > start the 'pipe' concept - only send the output) compared to /etc/network/* > for configuring (static) interfaces. > > imho a real pain - every distribution of Linux has a different way of > doing things (although I am beginning to think it is a different version of > Linux - change things because we can - because every distribution of Linux > seems to be a different version of Linux). > > Previous UNIX vendors would have been hung out to dry for this kind of > 'change management (read mis-management). (imho). > > Anyway, please add NetworkManager - and other core Linux changes, or a > link to 'Linux-world' changes - although I would expect Debian to take > responsibility for the list of changes between: > Linux wheezy 3.2.0-4-powerpc64 #1 SMP Debian 3.2.68-1+deb7u1 ppc64 > GNU/Linux > and > Linux jessie 3.16.0-4-powerpc64 #1 SMP Debian 3.16.7-ckt9-3 (2015-04-23) > ppc64 GNU/Linux > > my two cents. > > On Sat, May 2, 2015 at 2:16 PM, Ben Hutchings wrote: > >> On Sat, 2015-05-02 at 11:15 +0200, Michael Felt wrote: >> [...] >> >> > BTW: I notice a slight difference in how 'login as root' works between >> > wheezy and jessie. On both systems I have enabled 'root login' for my >> > initial tests. With wheezy I cannot login as root on the console, but >> > can login using ssh. On Jessie this is the reverse. I assume this is >> > deliberate. >> [...] >> >> The ssh part: yes, and that's documented in the release notes: >> < >> https://www.debian.org/releases/jessie/powerpc/release-notes/ch-information.en.html#openssh >> >. >> >> The console part: I don't think so; this is probably a bug in wheezy. >> The last time I had that sort of problem, it was due to an omission from >> the file /etc/securetty (list of devices that root may log in through). >> But in wheezy that file does include hvc0. >> >> Ben. >> >> -- >> Ben Hutchings >> Q. Which is the greater problem in the world today, ignorance or apathy? >> A. I don't know and I couldn't care less. >> > >
Re: yaboot: How to load Debian8 netboot installation images directly from the boot: prompt?
10 days late replying - my apologies. PowerPC - if I read that in a literal sense - is that basically "oldish" Macs that were build on the PowerPC processor. If the answer is yes, is there any interest in the Ubuntu Community to have a refresh/new document that focuses on the non-Mac POWER servers (POWER8 is gaining in popularity both as bare metal and as "virtual machine" aka parition). I am willing to assist - but have to limit myself to what I have (Power4 - bare metal, Power5 (bare metal/virtual) and Power6 (virtual only as I cannot bring it down to bare metal without an outage). And I know someone with a Power7 - entry system. I would have to look (and might actually find) someone with a Power8 for testing. Sincerely, Michael Felt On Tue, May 26, 2015 at 3:14 PM, Herminio Hernandez Jr. < herminio.hernande...@gmail.com> wrote: > Here is how you boot with usb. > > https://wiki.ubuntu.com/PowerPCFAQ#How_do_I_boot_from_a_USB_drive.3F > > Sent from my iPhone > > On May 26, 2015, at 2:37 AM, Clark Wang wrote: > > On Tue, May 26, 2015 at 3:05 PM, yu wrote: > >> As I know, yaboot can't set vmlinux and initrd at the same time in its >> prompt, the right way is to load an alternative config file, such as >> "conf file=/boot/deb/yaboot.conf", but in this yaboot.conf, both >> vmlinux and initrd.gz are under /, the path is incorrect. >> >> so I guess you can write a new yaboot.conf in a USB flash drive, like: >> >> boot=/dev/sdaX(the prep partition) >> partition=3 >> root=/dev/sda3 >> timeout=30 >> >> image=/boot/vmlinux (can use the jessie kernel image directly, not >> netboot image) >> label=Linux >> initrd=/boot/initrd.img >> >> >> and then try to load the conf file in yaboot prompt by >> >> conf [device=device] [partition=partno] [file=/path/to/configfile] >> >> p.s. I'm not sure whether yaboot can load a conf in usb device or not >> under iBook :( >> > > Thanks for the info. I may give it a try. > > -clark > >> >> 2015-05-26 14:17 GMT+08:00 clarkw : >> > On Tue, May 26, 2015 at 2:09 PM, Petter Adsen wrote: >> >> >> >> On Tue, 26 May 2015 13:16:04 +0800 >> >> Clark Wang wrote: >> >> >> >> > On Tue, May 26, 2015 at 1:10 PM, Herminio Hernandez Jr < >> >> > herminio.hernande...@gmail.com> wrote: >> >> > >> >> > > On Tue, 2015-05-26 at 10:22 +0800, Clark Wang wrote: >> >> > > > I have an `iBook G4` and have `Debian 8 (Jessie)` installed on >> it. >> >> > > > Yesterday I did something stupid (messed up `yaboot.conf` and ran >> >> > > > `ybin`) and now the system cannot boot up. >> >> > > > >> >> > > > The old Debian 8 was installed on a single partition >> (`/dev/sda3`, >> >> > > > `ext4`). I ever put the Debian 8 netboot installation images >> >> > > > (downloaded from here) under `/boot/deb/`: >> >> > > > >> >> > > > /boot/deb/initrd.gz >> >> > > > /boot/deb/vmlinux >> >> > > > /boot/deb/yaboot >> >> > > > /boot/deb/yaboot.conf >> >> > > > >> >> > > > So how can I boot the netboot installation images from the >> `boot:` >> >> > > > prompt and reinstall Debian 8? >> >> > > > >> >> > > > I tried `boot: hd:3,/boot/deb/vmlinux root=/dev/ram read-only >> >> > > > initrd=/boot/deb/initrd.gz initrd-size=300` but it did not >> >> > > > work. (The screenshot taken with my phone.) >> >> > > > >> >> > > > >> >> > > > Thanks. >> >> > > > >> >> > > > >> >> > > > >> >> > > > -clark >> >> > > > >> >> > > You can use the netinst cd as a recovery cd by doing the following. >> >> > > >> >> > >> >> > I forgot to mention that my iBook's CD drive is broken. :) >> >> > >> >> > > >> >> > > 1. boot into the cd and at boot type recovery >> >> > > >> >> > >> >> > Or can I boot the netboot installation images (under /boot/deb/) from >> >> > the Open Firmware prompt? >> >> >> >> Can the machine boot from a USB flash drive? Or over the network? One >> >> of these approaches might be easier for you. >> > >> > >> > I'm trying to find out how to boot form USB. Boot from network also >> sounds >> > good. I'll investigate how to setup a DHCP and TFTP server on my OS X >> > (Yosemite) and how to boot iBook from network. >> >> >> >> >> >> Other than that, I'm afraid I can't help you - I know nothing about >> >> yaboot. >> > >> > >> > I never know about yaboot and Open Firmware when I was using Mac OS X >> on the >> > iBook. They're all mysterious to me. Still learning. :) >> > >> > Thanks. >> > >> > -clark >> >> >> >> >> >> Petter >> >> >> >> -- >> >> "I'm ionized" >> >> "Are you sure?" >> >> "I'm positive." >> > >> > >> > >
Re: yaboot: How to load Debian8 netboot installation images directly from the boot: prompt?
I use, mainly the netinst.iso myself - and for Debian5, debian7 and debian8 it has worked (debian 5 on Power4 - standalone and Power5 - virtual, but need a whole disk), debian6 I got to work - eventually (Power5 only tried), but needed to patch yaboot everytime so I waited for Debian7. Debian7 worked in virtual mode, virtual disks (but not when using fancy disk management). Debian 8 I have only tried as a virtual machine on Power6. The biggest difference though is bare-metal, or virtualised - setting up the VIOS to support an install in whatever way. Maybe USB could be used as an install source. Sounds simplier with bare metal - an HMC can assign a USB port hard into a partition, but it is less mobile - and I do not know if IVM (integrated virtual manager - in any case VIOS as "HMC"). I have written those instructions on my Power/AIX portal and am willing to rework them to fit into a Debian FAQ format. For anyone interested: (for wheezy, but same instructions work for jessie!): http://www.rootvg.net/content/view/560/88/ On Fri, Jun 5, 2015 at 3:52 PM, Lennart Sorensen < lsore...@csclub.uwaterloo.ca> wrote: > On Fri, Jun 05, 2015 at 02:58:38PM +0200, Michael Felt wrote: > > 10 days late replying - my apologies. > > PowerPC - if I read that in a literal sense - is that basically "oldish" > > Macs that were build on the PowerPC processor. If the answer is yes, is > > there any interest in the Ubuntu Community to have a refresh/new document > > that focuses on the non-Mac POWER servers (POWER8 is gaining in > popularity > > both as bare metal and as "virtual machine" aka parition). I am willing > to > > assist - but have to limit myself to what I have (Power4 - bare metal, > > Power5 (bare metal/virtual) and Power6 (virtual only as I cannot bring it > > down to bare metal without an outage). And I know someone with a Power7 - > > entry system. I would have to look (and might actually find) someone > with a > > Power8 for testing. > > Hmm, I guess I have only ever tried booting from the net install cd image, > which at least worked for power6 and power7 IBM systems. > > I don't recall which boot loader the CD image uses. I use grub2 on the > installed systems though. > > -- > Len Sorensen >
Re: Q: Debian ppc boot with pearpc
Is this a Power Systems system, or closer to a Mac? On Sat, Jun 6, 2015 at 8:25 AM, Hideki Yamane wrote: > Hi, > > I've installed pearpc and tried to boot Debian 7.8/8.0 ppc iso, but > failed. > error message is > > - > cd:-1,\install\yaboot.conf": Unkwon or corrupt filesystem > Can't open config file > Welcome to yaboot version 1.3.16 > Enter "help" to get some basic usage information > Default supplied on the command line: eval > boot: > - > > However, can boot (and stucked) Gentoo iso with same ppc.conf. > What's wrong with it? > - iso image > - need some special config with pearpc > - other > > Can someone tell me how to boot Debian ppc? > > > -- > Regards, > > Hideki Yamane henrich @ debian.or.jp/org > http://wiki.debian.org/HidekiYamane > > > -- > To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > Archive: > https://lists.debian.org/20150606152541.ebf469363ff963d2416c0...@debian.or.jp > >
