From owner-freebsd-ppc@freebsd.org Sun Nov 15 00:36:33 2015 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A91F3A2E586 for ; Sun, 15 Nov 2015 00:36:33 +0000 (UTC) (envelope-from pascal@freebsd.drecker.com) Received: from mail.perfidia.de (mail.perfidia.de [91.102.12.21]) by mx1.freebsd.org (Postfix) with ESMTP id 54F0417B3; Sun, 15 Nov 2015 00:36:32 +0000 (UTC) (envelope-from pascal@freebsd.drecker.com) Received: from pdreckerw10 (unknown [172.16.64.126]) by mail.perfidia.de (Postfix) with ESMTPSA id C02284188B; Sun, 15 Nov 2015 01:36:30 +0100 (CET) From: "Pascal Drecker" To: "'Nathan Whitehorn'" , References: <002d01d11a71$c2d60e90$48822bb0$@freebsd.drecker.com> <563FDEFA.4030900@freebsd.org> <000801d11ae7$770af770$6520e650$@freebsd.drecker.com> <564505A2.1080806@freebsd.org> <000701d11ecb$5b056690$111033b0$@freebsd.drecker.com> <56477434.604@freebsd.org> In-Reply-To: <56477434.604@freebsd.org> Subject: RE: FreeBSD on an IBM Virtual I/O Server (VIOS) Date: Sun, 15 Nov 2015 01:36:30 +0100 Message-ID: <000001d11f3d$ac207750$046165f0$@freebsd.drecker.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQJ1mhdL4q+BcihISmcvlztvYtZH2QIEn9tjAdTmsYgB3DB21QGHtDuFAw6Ca8qdAOdUMA== Content-Language: de X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Nov 2015 00:36:33 -0000 I tested the following commands with little success: 0 > boot /vdevice/v-scsi@30000002/disk@8400000000000000,0:,\boot\loader only, unknown word ok 0 > boot /vdevice/v-scsi@30000002/disk@8400000000000000:1,\boot\loader only, unknown word ok 0 > boot /vdevice/v-scsi@30000002/disk@8400000000000000:2,\boot\loader ok 0 > boot /vdevice/v-scsi@30000002/disk@8400000000000000,\boot\loader ok 0 > boot /vdevice/v-scsi@30000002/disk@8400000000000000,0:1,\boot\loader only, unknown word ok 0 > boot /vdevice/v-scsi@30000002/disk@8400000000000000,0:2,\boot\loader ok 0 > boot /vdevice/v-scsi@30000002/disk@8400000000000000,0:,\boot\test ok I enabled VERBOSE-DEBUG for the CDROM device and run the tests 1 and 3 again: 0 > boot /vdevice/v-scsi@30000002/disk@8400000000000000,0:,\boot\loader sd0 : timed-spin sd0 : BLOCK-SIZE sd0 : read-block-size SCSI disk: read-cap SCSI disk: read-cap blk-size & max-lba =800 , 3d0d5 sd0 : BLOCK-SIZE SCSI disk : max-transfer =fffe00 sd0 : BLOCK-SIZE SCSI disk : READ-BLOCKS parms =6a2e800 , 0 , 1 SCSI disk : SEEK parms=0 , 0 SCSI disk : SEEK total=0 SCSI disk : READ-BLOCKS parms =6a24000 , 0 , 8 sd0 : BLOCK-SIZE SCSI disk : max-transfer =fffe00 SCSI disk : READ-BLOCKS parms =6a20000 , 10 , 8 SCSI disk : READ-BLOCKS parms =6a20000 , 8aa , 8 SCSI disk : READ-BLOCKS parms =6a20000 , b5a , 8 SCSI disk : READ-BLOCKS parms =6a20000 , 9c1a , 8 sd0 : timed-spin sd0 : BLOCK-SIZE sd0 : read-block-size SCSI disk: read-cap SCSI disk: read-cap blk-size & max-lba =800 , 3d0d5 sd0 : BLOCK-SIZE SCSI disk : max-transfer =fffe00 sd0 : BLOCK-SIZE SCSI disk : READ-BLOCKS parms =6a2e800 , 0 , 1 SCSI disk : SEEK parms=0 , 0 SCSI disk : SEEK total=0 SCSI disk : READ-BLOCKS parms =6a24000 , 0 , 8 sd0 : BLOCK-SIZE SCSI disk : max-transfer =fffe00 SCSI disk : READ-BLOCKS parms =6a20000 , 10 , 8 SCSI disk : READ-BLOCKS parms =6a20000 , 8aa , 8 SCSI disk : READ-BLOCKS parms =6a20000 , b5a , 8 SCSI disk : READ-BLOCKS parms =6a20000 , 9c1a , 8 only, unknown word ok 0 > boot /vdevice/v-scsi@30000002/disk@8400000000000000:2,\boot\loader sd0 : timed-spin sd0 : BLOCK-SIZE sd0 : read-block-size SCSI disk: read-cap SCSI disk: read-cap blk-size & max-lba =800 , 3d0d5 sd0 : BLOCK-SIZE SCSI disk : max-transfer =fffe00 sd0 : BLOCK-SIZE SCSI disk : READ-BLOCKS parms =6a2e800 , 0 , 1 Can't open disk label package sd0 : timed-spin sd0 : BLOCK-SIZE sd0 : read-block-size SCSI disk: read-cap SCSI disk: read-cap blk-size & max-lba =800 , 3d0d5 sd0 : BLOCK-SIZE SCSI disk : max-transfer =fffe00 sd0 : BLOCK-SIZE SCSI disk: read-cap SCSI disk: read-cap blk-size & max-lba =800 , 3d0d5 SCSI disk : SEEK parms=0 , 0 SCSI disk : SEEK total=0 SCSI disk : READ-BLOCKS parms =6a24000 , 0 , 8 ok I think that the boot loader is found in test 1. What is meant by "only, unknown word"? Illegal opcode? The machine has a POWER7+ cpu. -Pascal -----Original Message----- From: Nathan Whitehorn [mailto:nwhitehorn@freebsd.org] Sent: Samstag, 14. November 2015 18:50 To: Pascal Drecker ; freebsd-ppc@freebsd.org Subject: Re: FreeBSD on an IBM Virtual I/O Server (VIOS) Blast. Can you try this? boot /vdevice/v-scsi@30000002/disk@8400000000000000,0:,\boot\loader You could also try deleting the ,0 and adding a 1 or a 2 between the : and then , at the end. Thanks for the real-time debugging here. The CD boot code was built for PowerKVM and apparently they don't find bootable media the same way. -Nathan On 11/14/15 02:58, Pascal Drecker wrote: > Thanks for your help. Unfortunately I got the following error if I try > to boot from your image. > -Pascal > > VSCSI Node Menu > VSCSI Node String: /vdevice/v-scsi@30000002 > ----------------------------------------------------------------- > > 1. List Attached VSCSI Devices > 2. Select a VSCSI Device > > 3. Enable/Disable VSCSI Adapter Debug flags > > q - Quit/Exit > > ==> 2 > > 1. 8100000000000000 - 15360 MB Disk drive 2. 8400000000000000 - CDROM > drive > > Select a VSCSI Device : 2 > > VSCSI Device Menu > VSCSI Target Address ==> 8400000000000000 VSCSI Device String: > /vdevice/v-scsi@30000002/disk@8400000000000000,0:0 > VSCSI Device: CDROM drive > ---------------------------------------------------------------------- > > 1. Display Inquiry Data > 2. Spin up Drive > 3. Spin down Drive > 4. Continuous random Reads ( hit any key to stop ) > 5. Enable/Disable Device Debug flags 98. Boot from this Device > > q - Quit/Exit > > ==> 98 > \ > Detected bad memory access to address: fffffffffffffffe Package path = > /packages/utilities FAILED TO BOOT FROM DEVICE > > Hit a key to continue... > > > -----Original Message----- > From: Nathan Whitehorn [mailto:nwhitehorn@freebsd.org] > Sent: Donnerstag, 12. November 2015 22:33 > To: Pascal Drecker ; > freebsd-ppc@freebsd.org > Subject: Re: FreeBSD on an IBM Virtual I/O Server (VIOS) > > Can you try the image at > http://people.freebsd.org/~nwhitehorn/FreeBSD-11-pseries.iso? > -Nathan > > On 11/09/15 04:09, Pascal Drecker wrote: >> I can get into the Open Firmware Prompt. >> >> ##################################################################### >> >> 1) vios >> >> $ lsmap -vadapter vhost2 >> SVSA Physloc Client >> Partition ID >> --------------- -------------------------------------------- >> ------------------ >> vhost2 U8202.E4D.21F0FBV-V1-C15 0x00000004 >> >> VTD vtopt1 >> Status Available >> LUN 0x8400000000000000 >> Backing device cd0 >> Physloc U78AA.001.WZSL43C-P2-D9 >> Mirrored N/A >> >> VTD vtscsi2 >> Status Available >> LUN 0x8100000000000000 >> Backing device vdiskFBSD10 >> Physloc >> Mirrored N/A >> >> VTD vtusbdd0 >> Status Available >> LUN 0x8200000000000000 >> Backing device usbms0 >> Physloc U78AA.001.WZSL43C-D1-T1-L1 >> Mirrored N/A >> >> ##################################################################### >> >> 2) open firmware prompt => trying to boot from cd (ISO: 10.2 Release >> and >> CURRENT_2015-10-23) >> >> 0 > ioinfo >> >> !!! IOINFO: FOR IBM INTERNAL USE ONLY !!! >> This tool gives you information about SCSI,IDE,SATA,SAS,and USB >> devices attached to the system >> >> Select a tool from the following >> >> 1. SCSIINFO >> 2. IDEINFO >> 3. SATAINFO >> 4. SASINFO >> 5. USBINFO >> 6. FCINFO >> 7. VSCSIINFO >> >> q - quit/exit >> >> ==> 7 >> >> VSCSIINFO Main Menu >> Select a VSCSI Node from the following list: >> # Location Code Pathname >> --------------------------------------------------------------- >> 1. U8202.E4D.21F0FBV-V4-C2-T1 /vdevice/v-scsi@30000002 >> >> q - Quit/Exit >> >> ==> 1 >> >> VSCSI Node Menu >> VSCSI Node String: /vdevice/v-scsi@30000002 >> ----------------------------------------------------------------- >> >> 1. List Attached VSCSI Devices >> 2. Select a VSCSI Device >> >> 3. Enable/Disable VSCSI Adapter Debug flags >> >> q - Quit/Exit >> >> ==> 2 >> >> 1. 8100000000000000 - 15360 MB Disk drive 2. 8200000000000000 - 1911 >> MB Disk drive 3. 8400000000000000 - CDROM drive >> >> Select a VSCSI Device : 3 >> >> VSCSI Device Menu >> VSCSI Target Address ==> 8400000000000000 VSCSI Device String: >> /vdevice/v-scsi@30000002/disk@8400000000000000,0:0 >> VSCSI Device: CDROM drive >> --------------------------------------------------------------------- >> - >> >> 1. Display Inquiry Data >> 2. Spin up Drive >> 3. Spin down Drive >> 4. Continuous random Reads ( hit any key to stop ) >> 5. Enable/Disable Device Debug flags 98. Boot from this Device >> >> q - Quit/Exit >> >> ==> 98 >> \ >> Detected bad memory access to address: fffffffffffffffe Package path >> = /packages/utilities FAILED TO BOOT FROM DEVICE >> >> Hit a key to continue... >> >> ##################################################################### >> >> 3) open firmware prompt => trying to boot from usb (IMG: 10.2 Release >> and >> CURRENT_2015-10-23) >> >> VSCSI Node Menu >> VSCSI Node String: /vdevice/v-scsi@30000002 >> ----------------------------------------------------------------- >> >> 1. List Attached VSCSI Devices >> 2. Select a VSCSI Device >> >> 3. Enable/Disable VSCSI Adapter Debug flags >> >> q - Quit/Exit >> >> ==> 2 >> >> 1. 8100000000000000 - 15360 MB Disk drive 2. 8200000000000000 - 1911 >> MB Disk drive 3. 8400000000000000 - CDROM drive >> >> Select a VSCSI Device : 2 >> >> VSCSI Device Menu >> VSCSI Target Address ==> 8200000000000000 VSCSI Device String: >> /vdevice/v-scsi@30000002/disk@8200000000000000,0:0 >> VSCSI Device: 1911 MB Disk drive >> --------------------------------------------------------------------- >> - >> >> 1. Display Inquiry Data >> 2. Spin up Drive >> 3. Spin down Drive >> 4. Continuous random Reads ( hit any key to stop ) >> 5. Enable/Disable Device Debug flags 98. Boot from this Device >> >> q - Quit/Exit >> >> ==> 98 >> >> FAILED TO BOOT FROM DEVICE >> >> Hit a key to continue... >> >> ##################################################################### >> >> Unfortunately I do not know how to directly start the loader from cd. >> >> -Pascal >> >> PS: I'm a IBM Power Systems newbie. >> >> >> -----Original Message----- >> From: Nathan Whitehorn [mailto:nwhitehorn@freebsd.org] >> Sent: Montag, 9. November 2015 00:47 >> To: freebsd-ppc@freebsd.org; pascal@freebsd.drecker.com >> Subject: Re: FreeBSD on an IBM Virtual I/O Server (VIOS) >> >> It sounds like the firmware is not reading the bootinfo.txt correctly >> for some reason. Can you get to a Open Firmware prompt? The boot >> loader is in \boot\loader on the CD. Otherwise, I can send you a test > image. >> -Nathan >> >> On 11/08/15 14:06, Pascal Drecker wrote: >>> Hi, >>> >>> I like to install FreeBSD on an IBM Virtual I/O Server (VIOS). >>> >>> The current VIOS version (v2.2.3.50 - Standard Edition) is installed >>> and VIOS is running on an IBM Power 720 Express (Model 8202-E4D). >>> >>> The following operating systems are successfully installed using the >>> dvd-ram >>> drive: >>> >>> * IBM i V7R2 >>> * AIX 7.1 >>> * Ubuntu 14.04 >>> * Ubuntu 15.10 >>> >>> Every-time I try to boot FreeBSD from the dvd-ram I got the >>> following >>> message: >>> >>> .----------------------------------. >>> | No Operating Systems Installed | >>> `----------------------------------' >>> >>> I tested the following images: >>> >>> * FreeBSD-9.3-RELEASE-powerpc-powerpc64-disc1.iso >>> * FreeBSD-10.1-RELEASE-powerpc-powerpc64-disc1.iso >>> * FreeBSD-10.2-RELEASE-powerpc-powerpc64-disc1.iso >>> * FreeBSD-11.0-CURRENT-powerpc-powerpc64-20151023-r289846-bootonly.iso >>> >>> The IBM Power 720 Express has an Power7+. The processor >>> compatibility modes "POWER6", "POWER6+" and "POWER7" are already tested. >>> >>> Has anybody an idea? >>> >>> Thank you for replies, >>> >>> Pascal >>> >>> _______________________________________________ >>> freebsd-ppc@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-ppc >>> To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" >>> >