From owner-freebsd-ppc@freebsd.org Sun Nov 8 02:41:46 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 2079AA27368 for ; Sun, 8 Nov 2015 02:41:46 +0000 (UTC) (envelope-from hamiltcl@verizon.net) Received: from vms173025pub.verizon.net (vms173025pub.verizon.net [206.46.173.25]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 00FC41594 for ; Sun, 8 Nov 2015 02:41:45 +0000 (UTC) (envelope-from hamiltcl@verizon.net) Received: from lenoil1 ([96.255.168.17]) by vms173025.mailsrvcs.net (Oracle Communications Messaging Server 7.0.5.32.0 64bit (built Jul 16 2014)) with ESMTPA id <0NXH00DQM65CG940@vms173025.mailsrvcs.net> for freebsd-ppc@freebsd.org; Sat, 07 Nov 2015 20:41:37 -0600 (CST) X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=EdU1O6SC c=1 sm=1 tr=0 a=TXQDfM1T7tsaHFmtCUVSow==:117 a=o1OHuDzbAAAA:8 a=oR5dmqMzAAAA:8 a=kj9zAlcOel0A:10 a=qtqOOiqGOCEA:10 a=nzvzCOpdARRK07WlCjgA:9 a=CjuIK1q_8ugA:10 From: "Curtis Hamilton" To: Subject: DRM Support for Nouveau Date: Sat, 07 Nov 2015 21:41:21 -0500 Message-id: <001001d119ce$f482df70$dd889e50$@verizon.net> MIME-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit X-Mailer: Microsoft Outlook 15.0 Thread-index: AdEZzqFnYqgSpxFnSbyBjQ+M1P9x/A== Content-language: en-us 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, 08 Nov 2015 02:41:46 -0000 Now that there is DRM support for Radeon based cards, has any work been done to support nVidia cards? From owner-freebsd-ppc@freebsd.org Sun Nov 8 22:15:08 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 E0EA8A292F4 for ; Sun, 8 Nov 2015 22:15:07 +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 7CF061F75 for ; Sun, 8 Nov 2015 22:15:07 +0000 (UTC) (envelope-from pascal@freebsd.drecker.com) Received: from pdreckerw10 (unknown [172.16.64.126]) by mail.perfidia.de (Postfix) with ESMTPSA id 1BF58418A1 for ; Sun, 8 Nov 2015 23:06:46 +0100 (CET) From: "Pascal Drecker" To: Subject: FreeBSD on an IBM Virtual I/O Server (VIOS) Date: Sun, 8 Nov 2015 23:06:46 +0100 Message-ID: <002d01d11a71$c2d60e90$48822bb0$@freebsd.drecker.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdEacZ0gFlLkjMYLSsOeM6mbxN1eXw== Content-Language: de Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 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, 08 Nov 2015 22:15:08 -0000 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 From owner-freebsd-ppc@freebsd.org Sun Nov 8 23:47:19 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 955C0A2A8BC for ; Sun, 8 Nov 2015 23:47:19 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 81274128F for ; Sun, 8 Nov 2015 23:47:19 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from zeppelin.tachypleus.net (75-101-50-44.static.sonic.net [75.101.50.44]) (authenticated bits=0) by c.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id tA8Nl6k5014224 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 8 Nov 2015 15:47:07 -0800 Subject: Re: FreeBSD on an IBM Virtual I/O Server (VIOS) To: freebsd-ppc@freebsd.org, pascal@freebsd.drecker.com References: <002d01d11a71$c2d60e90$48822bb0$@freebsd.drecker.com> From: Nathan Whitehorn Message-ID: <563FDEFA.4030900@freebsd.org> Date: Sun, 8 Nov 2015 15:47:06 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <002d01d11a71$c2d60e90$48822bb0$@freebsd.drecker.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Sonic-CAuth: UmFuZG9tSVZGidTxMf5DBD09EXFhv7xH9p8i2nq3O2hCITdcQogAUrVVlHceifF51IQiz8r+dp6sKVbpEzb2gdENz44X9Gy8+f7xnaCUN7s= X-Sonic-ID: C;tsD4BHOG5RGYAb0U9jFv0A== M;uIxDBXOG5RGYAb0U9jFv0A== X-Spam-Flag: No X-Sonic-Spam-Details: 0.0/5.0 by cerberusd 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, 08 Nov 2015 23:47:19 -0000 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" > From owner-freebsd-ppc@freebsd.org Mon Nov 9 12:09:21 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 E61F5A29428 for ; Mon, 9 Nov 2015 12:09:21 +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 90F151ECD; Mon, 9 Nov 2015 12:09:21 +0000 (UTC) (envelope-from pascal@freebsd.drecker.com) Received: from pdreckerw10 (unknown [172.16.64.126]) by mail.perfidia.de (Postfix) with ESMTPSA id 8088F4188B; Mon, 9 Nov 2015 13:09:18 +0100 (CET) From: "Pascal Drecker" To: "'Nathan Whitehorn'" , References: <002d01d11a71$c2d60e90$48822bb0$@freebsd.drecker.com> <563FDEFA.4030900@freebsd.org> In-Reply-To: <563FDEFA.4030900@freebsd.org> Subject: RE: FreeBSD on an IBM Virtual I/O Server (VIOS) Date: Mon, 9 Nov 2015 13:09:20 +0100 Message-ID: <000801d11ae7$770af770$6520e650$@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+BcihISmcvlztvYtZH2QIEn9tjnTp1gFA= 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: Mon, 09 Nov 2015 12:09:22 -0000 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" > From owner-freebsd-ppc@freebsd.org Mon Nov 9 19:35:57 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 4757CA2AB7A for ; Mon, 9 Nov 2015 19:35:57 +0000 (UTC) (envelope-from hamiltcl@verizon.net) Received: from vms173025pub.verizon.net (vms173025pub.verizon.net [206.46.173.25]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 239271E27; Mon, 9 Nov 2015 19:35:56 +0000 (UTC) (envelope-from hamiltcl@verizon.net) Received: from lenoil1 ([96.255.168.17]) by vms173025.mailsrvcs.net (Oracle Communications Messaging Server 7.0.5.32.0 64bit (built Jul 16 2014)) with ESMTPA id <0NXK00321BR7N7H0@vms173025.mailsrvcs.net>; Mon, 09 Nov 2015 13:35:32 -0600 (CST) X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=MtGvkDue c=1 sm=1 tr=0 a=TXQDfM1T7tsaHFmtCUVSow==:117 a=o1OHuDzbAAAA:8 a=oR5dmqMzAAAA:8 a=kj9zAlcOel0A:10 a=qtqOOiqGOCEA:10 a=6I5d2MoRAAAA:8 a=uEd7BzGGqdLLeDZ1V2YA:9 a=CjuIK1q_8ugA:10 From: "Curtis Hamilton" To: "'Andreas Tobler'" , "'Steve Wills'" , "'Justin Hibbits'" Cc: "'FreeBSD PowerPC ML'" References: <002a01d11001$a4b126e0$ee1374a0$@verizon.net> <003701d1102a$ee366c70$caa34550$@verizon.net> <00f701d1129c$b82b0400$28810c00$@verizon.net> <563370BF.8010602@FreeBSD.org> <012c01d11328$caef1220$60cd3660$@verizon.net> <5633D743.9070002@fgznet.ch> <5633E35A.50402@fgznet.ch> <5635458E.2070700@fgznet.ch> <018b01d11582$a7300950$f5901bf0$@verizon.net> <5637DD7D.5060106@fgznet.ch> In-reply-to: Subject: RE: OpenJDK for PowerPC64 Date: Mon, 09 Nov 2015 14:35:13 -0500 Message-id: <006a01d11b25$c18f9f10$44aedd30$@verizon.net> MIME-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit X-Mailer: Microsoft Outlook 15.0 Thread-index: AQKRkMsb+GvouUjCqm4Yxd05iNTYtAHpldllAV94MsUBawMSHgIHk2b5Ak5uG5sCFhOKpAJFjLidATxg7hwBEmTV6gKSd7h+AiYfn5ecZRuhcIAKpRJw Content-language: en-us 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: Mon, 09 Nov 2015 19:35:57 -0000 Andreas, Just checking to see how things progressing for you. -Curtis -----Original Message----- From: Curtis Hamilton [mailto:hamiltcl@verizon.net] Sent: Monday, November 02, 2015 8:13 PM To: 'Andreas Tobler' ; 'Steve Wills' ; 'Justin Hibbits' Cc: 'FreeBSD PowerPC ML' Subject: RE: OpenJDK for PowerPC64 I forgot to mentioned this in my notes. GCJ is equivalent to JDK5 (java 1.5), however both JDK6 and JDK7 are hard coded to require 1.6 . You'll need to make the following edits: OPENJDK6: jdk/make/common/shared/Platform.gmk (line 91) OpenJDK7: jdk/make/common/shared/Defs-versions.gmk (line 222) Just change the version from 1.6 to 1.5. -Curtis -----Original Message----- From: Andreas Tobler [mailto:andreast-list@fgznet.ch] Sent: Monday, November 02, 2015 5:03 PM To: Curtis Hamilton ; 'Steve Wills' ; 'Justin Hibbits' Cc: 'FreeBSD PowerPC ML' Subject: Re: OpenJDK for PowerPC64 On 02.11.15 16:25, Curtis Hamilton wrote: > Attached are the instructions for setting up a bootstrap for building > OpenJDK on FreeBSD. In an earlier email I provided the build script > used to build the BSD-Port mercurial, using the bootstrap setup in the instructions. > > > Let me know if you have questions. Thanks! I missed the step to build classpath, what a nice project at that time ;) But next, what do I have to build? How is the sequence to 'bootstrap' openjdk? I'm a newbie in this regard. I get this when I do a make in java/openjdk7 (with patched Makefile from a previous post) ERROR: Your BOOTDIR environment variable does not point \n to a valid JDK for bootstrapping this build. \n A JDK 7 build must be bootstrapped using \n JDK 1.6. fcs (or later). \n Apparently, your bootstrap JDK is version 1.5.0 \n Please update your ALT_BOOTDIR setting and start your build again. \n This is with openjdk7. The same happens with openjdk6. my compiler chain is gcc-6.0. I think a few things are missing here. Andreas From owner-freebsd-ppc@freebsd.org Mon Nov 9 20:31:53 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 6639AA2AE60 for ; Mon, 9 Nov 2015 20:31:53 +0000 (UTC) (envelope-from andreast-list@fgznet.ch) Received: from smtp.fgznet.ch (unknown [IPv6:2001:4060:1:1001::14:54]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 232471F20; Mon, 9 Nov 2015 20:31:53 +0000 (UTC) (envelope-from andreast-list@fgznet.ch) Received: from [192.168.225.14] (dhclient-91-190-14-19.flashcable.ch [91.190.14.19]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by fgznet.ch (Postfix) with ESMTPS id 01E09CB7C0; Mon, 9 Nov 2015 21:31:48 +0100 (CET) Subject: Re: OpenJDK for PowerPC64 To: Curtis Hamilton , 'Steve Wills' , 'Justin Hibbits' References: <002a01d11001$a4b126e0$ee1374a0$@verizon.net> <003701d1102a$ee366c70$caa34550$@verizon.net> <00f701d1129c$b82b0400$28810c00$@verizon.net> <563370BF.8010602@FreeBSD.org> <012c01d11328$caef1220$60cd3660$@verizon.net> <5633D743.9070002@fgznet.ch> <5633E35A.50402@fgznet.ch> <5635458E.2070700@fgznet.ch> <018b01d11582$a7300950$f5901bf0$@verizon.net> <5637DD7D.5060106@fgznet.ch> <006a01d11b25$c18f9f10$44aedd30$@verizon.net> Cc: 'FreeBSD PowerPC ML' From: Andreas Tobler Message-ID: <564102B4.40005@fgznet.ch> Date: Mon, 9 Nov 2015 21:31:48 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <006a01d11b25$c18f9f10$44aedd30$@verizon.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.73 on 127.0.1.1 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: Mon, 09 Nov 2015 20:31:53 -0000 Hi Curtis, On 09.11.15 20:35, Curtis Hamilton wrote: > Just checking to see how things progressing for you. -ENOTIME :) It didn't succeed after editing the mentioned files. I started investigating but I couldn't find the issue. Then I went back to my compiler to-do plate, and I'm still there. For me, as an unexperienced user, the build instructions are not very clear. I learned that I need a gcj and classpath. Then I tought to jump into the ports tree, java/openjdk6|7 and do a make. Here I had learned from you that I have to edit these files: OPENJDK6: jdk/make/common/shared/Platform.gmk (line 91) OpenJDK7: jdk/make/common/shared/Defs-versions.gmk (line 222) and change the hardcoded 1.6 to 1.5. ok. But still, I seem to misunderstand some bits. This is the latest error where I gave up: -def-pcompile: [javac] Compiling 2 source files to /export/build/obj/usr/ports/java/openjdk7/work/openjdk/build/bsd-powerpc/langtools/build/toolclasses [javac] javac: error: 6: No such file or directory [javac] javac: error: 6: No such file or directory [javac] javac: error: unrecognized command line option '-sourcepath' [javac] javac: error: unrecognized command line option '-target' [javac] javac: error: unrecognized command line option '-source' BUILD FAILED /export/build/obj/usr/ports/java/openjdk7/work/openjdk/langtools/make/build.xml:860: Compile failed; see the compiler error output for details. build.xml: ----- <<<< line 860 ----- What I'd need is a diff for the openjdk6/7 Makefile and patches if needed which I could just place in the files section. Then my expectation would be go and make :) I know, it is a hard thing. But you know the fine details and I really lack the time to dive in atm. Thanks, Andreas From owner-freebsd-ppc@freebsd.org Mon Nov 9 21:01:32 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 9DFCEA29A79 for ; Mon, 9 Nov 2015 21:01:32 +0000 (UTC) (envelope-from hamiltcl@verizon.net) Received: from vms173023pub.verizon.net (vms173023pub.verizon.net [206.46.173.23]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7BFB91831 for ; Mon, 9 Nov 2015 21:01:32 +0000 (UTC) (envelope-from hamiltcl@verizon.net) Received: from lenoil1 ([96.255.168.17]) by vms173023.mailsrvcs.net (Oracle Communications Messaging Server 7.0.5.32.0 64bit (built Jul 16 2014)) with ESMTPA id <0NXK00727CX9TFB0@vms173023.mailsrvcs.net> for freebsd-ppc@freebsd.org; Mon, 09 Nov 2015 14:00:46 -0600 (CST) X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=WpDWSorv c=1 sm=1 tr=0 a=TXQDfM1T7tsaHFmtCUVSow==:117 a=o1OHuDzbAAAA:8 a=oR5dmqMzAAAA:8 a=qtqOOiqGOCEA:10 a=DAwyPP_o2Byb1YXLmDAA:9 a=V1IJGOk8rp39UtrKp2sA:9 a=CjuIK1q_8ugA:10 a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8 a=VMlSUAP4C5rH3jNr7SgA:9 a=gKO2Hq4RSVkA:10 a=UiCQ7L4-1S4A:10 a=hTZeC7Yk6K0A:10 a=frz4AuCg-hUA:10 From: "Curtis Hamilton" To: Subject: Airport Extreme WiFi Broken in FreeBSD 10.2 Date: Mon, 09 Nov 2015 15:00:28 -0500 Message-id: <006b01d11b29$47fd5990$d7f80cb0$@verizon.net> MIME-version: 1.0 X-Mailer: Microsoft Outlook 15.0 Thread-index: AdEbJeoshtUYVCtMSMacjFJ+5/LrDA== Content-language: en-us Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 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: Mon, 09 Nov 2015 21:01:32 -0000 Has anyone else tried to load the BWI module in 10.2? I attempted to load the kernel module and build a new kernel with the module built-in. In both cases the boot process freezes with the following errors: ata2: at channel0 on atapci0 ata2: WARNING DMA initialization failed, disabling DMA ata2: FAILURE - alloc sg_map ata2: WARNING DMA allocation failed, disabling DMA A few lines before this the following error is shown: bwi0: can't allocate DMA mem bwi0: 0th TX ring DMA alloc-failed Everything works fine in 10.1 From owner-freebsd-ppc@freebsd.org Mon Nov 9 21:44:05 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 3146FA2A89A for ; Mon, 9 Nov 2015 21:44:05 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F40AD151B for ; Mon, 9 Nov 2015 21:44:04 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by iodd200 with SMTP id d200so200948180iod.0 for ; Mon, 09 Nov 2015 13:44:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:cc:content-type; bh=JNZ4JAy9Aa+KLFe5Gj0bdDp2W842f5BZGojf7WfY3qQ=; b=nfJkWMapzn0pZT9GGbh6IGYS60L8+UDZ48s0fGaUNrjUO3Fo6TzcMvpBFOr2daki56 MByRc3uqKjVouYm1yA8SwNXLRFRk5zavpltlzV6HQh6KqZ7BmWYoV1t6yZ6LhT3FFOcC 9FIF06VHWZtZyVLEMjyLjWdGbazkkQIIYxxdmcGHyhCHwP3IQVij4N7Kf0MRny6pqDMa zmyuNitVspHDr8klOA8x2rnE5VYmo7VIWaX0mfp0kOMSvv0zE2wvQD2gZjE+Ep++PICo ZdMw9O5NHzeX+zeROYKyiwmt3o6Pt1UgkNfsYaVOCkxFp7+NtVLlVSJ6u6LIE8FNzXjR yv+g== MIME-Version: 1.0 X-Received: by 10.107.152.2 with SMTP id a2mr569943ioe.123.1447105444362; Mon, 09 Nov 2015 13:44:04 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.36.217.196 with HTTP; Mon, 9 Nov 2015 13:44:04 -0800 (PST) Date: Mon, 9 Nov 2015 13:44:04 -0800 X-Google-Sender-Auth: DJ-Agy8tv49OdODgRu80PXRl5Bk Message-ID: Subject: Re: Airport Extreme WiFi Broken in FreeBSD 10.2 From: Adrian Chadd To: Curtis Hamilton Cc: FreeBSD PowerPC ML Content-Type: text/plain; charset=UTF-8 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: Mon, 09 Nov 2015 21:44:05 -0000 Hi, It looks like there's something up with the memory management, not wifi. ata2 failing and bwi failing in DMA memory allocation is the hint. :) -a On 9 November 2015 at 12:00, Curtis Hamilton wrote: > Has anyone else tried to load the BWI module in 10.2? I attempted to load > the kernel module and build a new kernel with the module built-in. In both > cases the boot process freezes with the following errors: > > > > ata2: at channel0 on atapci0 > > ata2: WARNING DMA initialization failed, disabling DMA > > ata2: FAILURE - alloc sg_map > > ata2: WARNING DMA allocation failed, disabling DMA > > > > A few lines before this the following error is shown: > > > > bwi0: can't allocate DMA mem > > bwi0: 0th TX ring DMA alloc-failed > > > > Everything works fine in 10.1 > > _______________________________________________ > 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" From owner-freebsd-ppc@freebsd.org Tue Nov 10 13:32:31 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 24375A2A91C for ; Tue, 10 Nov 2015 13:32:31 +0000 (UTC) (envelope-from hamiltcl@verizon.net) Received: from vms173019pub.verizon.net (vms173019pub.verizon.net [206.46.173.19]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 079961B2C; Tue, 10 Nov 2015 13:32:31 +0000 (UTC) (envelope-from hamiltcl@verizon.net) Received: from lenoil1 ([96.255.168.17]) by vms173019.mailsrvcs.net (Oracle Communications Messaging Server 7.0.5.32.0 64bit (built Jul 16 2014)) with ESMTPA id <0NXL00C5ZMTJWS80@vms173019.mailsrvcs.net>; Tue, 10 Nov 2015 06:32:07 -0600 (CST) X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=MtGvkDue c=1 sm=1 tr=0 a=TXQDfM1T7tsaHFmtCUVSow==:117 a=o1OHuDzbAAAA:8 a=oR5dmqMzAAAA:8 a=kj9zAlcOel0A:10 a=qtqOOiqGOCEA:10 a=pGLkceISAAAA:8 a=6I5d2MoRAAAA:8 a=jh7xevo7HZBcaG2-9s8A:9 a=CjuIK1q_8ugA:10 From: "Curtis Hamilton" To: "'Adrian Chadd'" Cc: "'FreeBSD PowerPC ML'" References: In-reply-to: Subject: RE: Airport Extreme WiFi Broken in FreeBSD 10.2 Date: Tue, 10 Nov 2015 07:31:47 -0500 Message-id: <008401d11bb3$c4c31430$4e493c90$@verizon.net> MIME-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit X-Mailer: Microsoft Outlook 15.0 Thread-index: AQIPxCP+vRcQVtpYjevgebsScL8Fsp4X3fKA Content-language: en-us 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: Tue, 10 Nov 2015 13:32:31 -0000 I'll investigate. My initial presumption that it was a bwi module issue is because ata2 initializes just fine without the bwi module. -----Original Message----- From: adrian.chadd@gmail.com [mailto:adrian.chadd@gmail.com] On Behalf Of Adrian Chadd Sent: Monday, November 09, 2015 4:44 PM To: Curtis Hamilton Cc: FreeBSD PowerPC ML Subject: Re: Airport Extreme WiFi Broken in FreeBSD 10.2 Hi, It looks like there's something up with the memory management, not wifi. ata2 failing and bwi failing in DMA memory allocation is the hint. :) -a On 9 November 2015 at 12:00, Curtis Hamilton wrote: > Has anyone else tried to load the BWI module in 10.2? I attempted to > load the kernel module and build a new kernel with the module > built-in. In both cases the boot process freezes with the following errors: > > > > ata2: at channel0 on atapci0 > > ata2: WARNING DMA initialization failed, disabling DMA > > ata2: FAILURE - alloc sg_map > > ata2: WARNING DMA allocation failed, disabling DMA > > > > A few lines before this the following error is shown: > > > > bwi0: can't allocate DMA mem > > bwi0: 0th TX ring DMA alloc-failed > > > > Everything works fine in 10.1 > > _______________________________________________ > 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" From owner-freebsd-ppc@freebsd.org Tue Nov 10 20:54:28 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 52F11A2BC7B for ; Tue, 10 Nov 2015 20:54:28 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ig0-x233.google.com (mail-ig0-x233.google.com [IPv6:2607:f8b0:4001:c05::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1DDAD176E for ; Tue, 10 Nov 2015 20:54:28 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by igbxm8 with SMTP id xm8so9108227igb.1 for ; Tue, 10 Nov 2015 12:54:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=D6rOjk0WwyflqlzOc88BfIFJ+sxtk/JNKoX3EuL5j10=; b=DS5lFEQ4I760zLadhN65ifWl8hBzMOMKM4GSPYcdfZtVSljmW/6FdJZPqpaTrGKkyd +HvSd2K3R9W4Tg+5aN2KV2iXfSEa7+OLubpxx/zvebV1fUSjpAL7inbha9usQTrR99u4 +iLNmLufxHltUkRotcu8Gt8qciH/Z8dF2tEy+TMnO0lU19vteRPr2mYYkRduDpqAKa9x VovkeQ5JE8TMbw5w6xRsEio10sVibtFMJfC3Wrvnw+yN49wOJdjyqkfu3GWFclSM84w7 D6bwUZiY+Us/Oe9E31lQ9H+MByYl7dWF9J71Mu+fGfhwxTanfnvtbpHW1ijTnYsAtwXj RkUQ== MIME-Version: 1.0 X-Received: by 10.50.62.104 with SMTP id x8mr5819036igr.22.1447188867607; Tue, 10 Nov 2015 12:54:27 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.36.217.196 with HTTP; Tue, 10 Nov 2015 12:54:27 -0800 (PST) In-Reply-To: <008401d11bb3$c4c31430$4e493c90$@verizon.net> References: <008401d11bb3$c4c31430$4e493c90$@verizon.net> Date: Tue, 10 Nov 2015 12:54:27 -0800 X-Google-Sender-Auth: t6Z0Bm0yVzzClA7Rb-8j7MNrUfE Message-ID: Subject: Re: Airport Extreme WiFi Broken in FreeBSD 10.2 From: Adrian Chadd To: Curtis Hamilton Cc: FreeBSD PowerPC ML Content-Type: text/plain; charset=UTF-8 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: Tue, 10 Nov 2015 20:54:28 -0000 It's not initialising fine; it's actually logging a warning. :) -a On 10 November 2015 at 04:31, Curtis Hamilton wrote: > I'll investigate. My initial presumption that it was a bwi module issue is > because ata2 initializes just fine without the bwi module. > > -----Original Message----- > From: adrian.chadd@gmail.com [mailto:adrian.chadd@gmail.com] On Behalf Of > Adrian Chadd > Sent: Monday, November 09, 2015 4:44 PM > To: Curtis Hamilton > Cc: FreeBSD PowerPC ML > Subject: Re: Airport Extreme WiFi Broken in FreeBSD 10.2 > > Hi, > > It looks like there's something up with the memory management, not wifi. > ata2 failing and bwi failing in DMA memory allocation is the hint. :) > > > > -a > > > On 9 November 2015 at 12:00, Curtis Hamilton wrote: >> Has anyone else tried to load the BWI module in 10.2? I attempted to >> load the kernel module and build a new kernel with the module >> built-in. In both cases the boot process freezes with the following > errors: >> >> >> >> ata2: at channel0 on atapci0 >> >> ata2: WARNING DMA initialization failed, disabling DMA >> >> ata2: FAILURE - alloc sg_map >> >> ata2: WARNING DMA allocation failed, disabling DMA >> >> >> >> A few lines before this the following error is shown: >> >> >> >> bwi0: can't allocate DMA mem >> >> bwi0: 0th TX ring DMA alloc-failed >> >> >> >> Everything works fine in 10.1 >> >> _______________________________________________ >> 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" > From owner-freebsd-ppc@freebsd.org Wed Nov 11 02:06:01 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 25595A2AECD for ; Wed, 11 Nov 2015 02:06:01 +0000 (UTC) (envelope-from hamiltcl@verizon.net) Received: from vms173023pub.verizon.net (vms173023pub.verizon.net [206.46.173.23]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0013D10AE; Wed, 11 Nov 2015 02:06:00 +0000 (UTC) (envelope-from hamiltcl@verizon.net) Received: from lenoil1 ([96.255.168.17]) by vms173023.mailsrvcs.net (Oracle Communications Messaging Server 7.0.5.32.0 64bit (built Jul 16 2014)) with ESMTPA id <0NXM00GJ4OGPKVC0@vms173023.mailsrvcs.net>; Tue, 10 Nov 2015 20:05:14 -0600 (CST) X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=J+9Xl1TS c=1 sm=1 tr=0 a=TXQDfM1T7tsaHFmtCUVSow==:117 a=o1OHuDzbAAAA:8 a=oR5dmqMzAAAA:8 a=qtqOOiqGOCEA:10 a=DAwyPP_o2Byb1YXLmDAA:9 a=pGLkceISAAAA:8 a=6I5d2MoRAAAA:8 a=M4Tfym8Tc2kH9ScgawEA:9 a=U43LrpnFpgho8hIN:21 a=fH3vrkO0eynoeoGB:21 a=CjuIK1q_8ugA:10 a=_2ZTPHEeGeexyLdk5w0A:9 From: "Curtis Hamilton" To: "'Adrian Chadd'" Cc: "'FreeBSD PowerPC ML'" References: <008401d11bb3$c4c31430$4e493c90$@verizon.net> In-reply-to: Subject: RE: Airport Extreme WiFi Broken in FreeBSD 10.2 Date: Tue, 10 Nov 2015 21:04:52 -0500 Message-id: <00aa01d11c25$5b095140$111bf3c0$@verizon.net> MIME-version: 1.0 Content-type: multipart/mixed; boundary="----=_NextPart_000_00AB_01D11BFB.72412BF0" X-Mailer: Microsoft Outlook 15.0 Thread-index: AQIPxCP+vRcQVtpYjevgebsScL8FsgHk9TGjAZs7Hwmd/LafUA== Content-language: en-us 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: Wed, 11 Nov 2015 02:06:01 -0000 This is a multipart message in MIME format. ------=_NextPart_000_00AB_01D11BFB.72412BF0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit I've checked the log and don't see any warnings. Attached is my current log. What am I missing? Unfortunately, the system does not complete the boot process with the bwi module loaded. so I do not have a log for that process. BTW, I've tried manually loading the module after booting, both without and with the airport firmware. Without the airport firmware the system complains but continues to run, however with the firmware the system locks up. -Curtis -----Original Message----- From: adrian.chadd@gmail.com [mailto:adrian.chadd@gmail.com] On Behalf Of Adrian Chadd Sent: Tuesday, November 10, 2015 3:54 PM To: Curtis Hamilton Cc: FreeBSD PowerPC ML Subject: Re: Airport Extreme WiFi Broken in FreeBSD 10.2 It's not initialising fine; it's actually logging a warning. :) -a On 10 November 2015 at 04:31, Curtis Hamilton wrote: > I'll investigate. My initial presumption that it was a bwi module > issue is because ata2 initializes just fine without the bwi module. > > -----Original Message----- > From: adrian.chadd@gmail.com [mailto:adrian.chadd@gmail.com] On Behalf > Of Adrian Chadd > Sent: Monday, November 09, 2015 4:44 PM > To: Curtis Hamilton > Cc: FreeBSD PowerPC ML > Subject: Re: Airport Extreme WiFi Broken in FreeBSD 10.2 > > Hi, > > It looks like there's something up with the memory management, not wifi. > ata2 failing and bwi failing in DMA memory allocation is the hint. :) > > > > -a > > > On 9 November 2015 at 12:00, Curtis Hamilton wrote: >> Has anyone else tried to load the BWI module in 10.2? I attempted to >> load the kernel module and build a new kernel with the module >> built-in. In both cases the boot process freezes with the following > errors: >> >> >> >> ata2: at channel0 on atapci0 >> >> ata2: WARNING DMA initialization failed, disabling DMA >> >> ata2: FAILURE - alloc sg_map >> >> ata2: WARNING DMA allocation failed, disabling DMA >> >> >> >> A few lines before this the following error is shown: >> >> >> >> bwi0: can't allocate DMA mem >> >> bwi0: 0th TX ring DMA alloc-failed >> >> >> >> Everything works fine in 10.1 >> >> _______________________________________________ >> 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" > ------=_NextPart_000_00AB_01D11BFB.72412BF0 Content-Type: application/octet-stream; name="dmesg.today" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="dmesg.today" Copyright (c) 1992-2015 The FreeBSD Project.=0A= Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994=0A= The Regents of the University of California. All rights reserved.=0A= FreeBSD is a registered trademark of The FreeBSD Foundation.=0A= FreeBSD 10.2-STABLE #0 r287149: Thu Aug 27 03:46:55 UTC 2015=0A= = root@releng1.nyi.freebsd.org:/usr/obj/powerpc.powerpc64/usr/src/sys/GENER= IC64 powerpc=0A= gcc version 4.2.1 20070831 patched [FreeBSD]=0A= VT(ofwfb): resolution 1680x1050=0A= cpu0: IBM PowerPC 970MP revision 1.1, 2300.29 MHz=0A= cpu0: Features dc000000=0A= cpu0: HID0 1511081=0A= real memory =3D 5878026240 (5605 MB)=0A= avail memory =3D 5531877376 (5275 MB)=0A= FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs=0A= cpu0: dev=3Dff89d680 (BSP)=0A= cpu1: dev=3Dff89eb70=0A= kbd0 at kbdmux0=0A= random: initialized=0A= ofwbus0: on nexus0=0A= cpulist0: on ofwbus0=0A= cpu0: on cpulist0=0A= pcr0: on cpu0=0A= cpu1: on cpulist0=0A= pcr1: on cpu1=0A= powermac_nvram0: mem 0xfff04000-0xfff07fff on ofwbus0=0A= powermac_nvram0: bank0 generation 550, bank1 generation 551=0A= unin0: mem 0xf8000000-0xf8ffffff on = ofwbus0=0A= unin0: Version 66=0A= iichb0: mem 0xf8001000-0xf8001fff irq 0 on unin0=0A= iicbus0: on iichb0=0A= ds17750: at addr 0x94 on iicbus0=0A= ds16310: at addr 0x96 on iicbus0=0A= max66900: at addr 0x98 on iicbus0=0A= max66901: at addr 0x9c on iicbus0=0A= htpic0: mem 0xf8040000-0xf807ffff on unin0=0A= pcib0: mem 0xf0000000-0xf1ffffff on ofwbus0=0A= pci0: on pcib0=0A= vgapci0: mem = 0x92000000-0x92ffffff,0xa0000000-0xbfffffff,0x91000000-0x91ffffff irq 3 = at device 0.0 on pci0=0A= vgapci0: Boot video device=0A= pcib1: mem = 0xf2000000-0xf47fffff,0xf8070000-0xf8070fff on ofwbus0=0A= pcib1: 86 HT IRQs on device 7.0=0A= pci1: on pcib1=0A= pcib1: Enabling MSI window for HyperTransport slave at pci1:0:1:0=0A= pcib2: at device 1.0 on pci1=0A= pci2: on pcib2=0A= pcib3: at device 2.0 on pci1=0A= pci3: on pcib3=0A= bge0: mem = 0xfa530000-0xfa53ffff,0xfa520000-0xfa52ffff irq 66 at device 4.0 on pci3=0A= bge0: CHIP ID 0x00008003; ASIC REV 0x08; CHIP REV 0x80; PCI-X 33 MHz=0A= miibus0: on bge0=0A= brgphy0: PHY 1 on miibus0=0A= brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, = 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow=0A= bge0: Ethernet address: 00:16:cb:3a:88:88=0A= bge1: mem = 0xfa510000-0xfa51ffff,0xfa500000-0xfa50ffff irq 67 at device 4.1 on pci3=0A= bge1: CHIP ID 0x00008003; ASIC REV 0x08; CHIP REV 0x80; PCI-X 33 MHz=0A= miibus1: on bge1=0A= brgphy1: PHY 1 on miibus1=0A= brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, = 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow=0A= bge1: Ethernet address: 00:16:cb:3a:88:89=0A= pcib4: at device 3.0 on pci1=0A= pci4: on pcib4=0A= pcib5: at device 4.0 on pci1=0A= pci5: on pcib5=0A= pcib6: at device 5.0 on pci1=0A= pci6: on pcib6=0A= pcib7: at device 6.0 on pci1=0A= pci7: on pcib7=0A= pcib8: at device 7.0 on pci1=0A= pci8: on pcib8=0A= gem0: mem 0xfa200000-0xfa3fffff at device = 15.0 on pci8=0A= gem0: invalid MAC address=0A= device_attach: gem0 attach returned 6=0A= pcib9: at device 8.0 on pci1=0A= pci9: on pcib9=0A= macio0: mem 0x80000000-0x8007ffff at device 7.0 = on pci9=0A= macgpio0: mem 0x50-0x8a on macio0=0A= scc0: mem = 0x13000-0x13fff,0x8400-0x84ff,0x8500-0x85ff,0x8600-0x86ff,0x8700-0x87ff = irq 23,17,18,24,19,20 on macio0=0A= uart0: on scc0=0A= uart1: on scc0=0A= iichb1: mem 0x18000-0x18fff irq 27 on macio0=0A= iicbus1: on iichb1=0A= onyx0: at addr 0x8c on iicbus1=0A= iicbus1: at addr 0x24=0A= pcm0: mem = 0x10000-0x10fff,0x8000-0x80ff,0x8100-0x81ff irq 28,11,12,30,15,16 on = macio0=0A= pci9: at device 1.0 (no driver attached)=0A= ohci0: mem 0x80082000-0x80082fff irq 70 at = device 11.0 on pci9=0A= usbus0 on ohci0=0A= ohci1: mem 0x80081000-0x80081fff irq 70 at = device 11.1 on pci9=0A= usbus1 on ohci1=0A= ehci0: mem 0x80080000-0x800800ff irq = 70 at device 11.2 on pci9=0A= usbus2: EHCI version 1.0=0A= usbus2 on ehci0=0A= pcib10: at device 9.0 on pci1=0A= pci10: on pcib10=0A= atapci0: mem 0xfa402000-0xfa403fff = irq 10 at device 12.0 on pci10=0A= pcib1: failed to reserve resource for pcib10=0A= atapci0: 0x10 bytes of rid 0x20 res 4 failed (0, 0xffffffffffffffff).=0A= ata2: at channel 0 on atapci0=0A= ata3: at channel 1 on atapci0=0A= ata4: at channel 2 on atapci0=0A= ata5: at channel 3 on atapci0=0A= ata0: mem 0xfa404000-0xfa407fff irq 38,37 = at device 13.0 on pci10=0A= fwohci0: <1394 Open Host Controller Interface> mem 0xfa400000-0xfa400fff = irq 39 at device 14.0 on pci10=0A= fwohci0: OHCI version 1.0 (ROM=3D0)=0A= fwohci0: No. of Isochronous channels is 8.=0A= fwohci0: EUI64 00:14:51:ff:fe:41:47:5a=0A= fwohci0: invalid speed 7 (fixed to 3).=0A= fwohci0: Phy 1394a available S800, 3 ports.=0A= fwohci0: Link S800, max_rec 4096 bytes.=0A= firewire0: on fwohci0=0A= fwe0: on firewire0=0A= if_fwe0: Fake Ethernet address: 02:14:51:41:47:5a=0A= fwe0: Ethernet address: 02:14:51:41:47:5a=0A= sbp0: on firewire0=0A= fwohci0: Initiate bus reset=0A= fwohci0: fwohci_intr_core: BUS reset=0A= fwohci0: fwohci_intr_core: node_id=3D0x00000002, SelfID Count=3D1, = CYCLEMASTER mode=0A= smu0: on ofwbus0=0A= iichb2: on smu0=0A= iicbus2: on iichb2=0A= smusat0: at addr 0xb0 on iicbus2=0A= iicbus2: at addr 0xd4=0A= iichb3: on smu0=0A= iicbus3: on iichb3=0A= Timecounter "timebase" frequency 33333333 Hz quality 0=0A= Event timer "decrementer" frequency 33333333 Hz quality 1000=0A= Timecounters tick every 1.000 msec=0A= firewire0: 3 nodes, maxhop <=3D 2 cable IRM irm(2) (me) =0A= firewire0: bus manager 2 =0A= max66900: 2 sensors detected.=0A= max66901: 2 sensors detected.=0A= random: unblocking device.=0A= usbus0: 12Mbps Full Speed USB v1.0=0A= usbus1: 12Mbps Full Speed USB v1.0=0A= ugen0.1: at usbus0=0A= uhub0: on usbus0=0A= ugen1.1: at usbus1=0A= uhub1: on usbus1=0A= usbus2: 480Mbps High Speed USB v2.0=0A= ugen2.1: at usbus2=0A= uhub2: on usbus2=0A= uhub0: 3 ports with 3 removable, self powered=0A= uhub1: 2 ports with 2 removable, self powered=0A= uhub2: 5 ports with 5 removable, self powered=0A= ada0 at ata2 bus 0 scbus0 target 0 lun 0=0A= ada0: ATA8-ACS SATA 3.x device=0A= ada0: Serial Number 9VP6KXTM=0A= ada0: 150.000MB/s transfers (SATA 1.x, UDMA5, PIO 8192bytes)=0A= ada0: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C)=0A= ada0: Previously was known as ad0=0A= ada1 at ata3 bus 0 scbus1 target 0 lun 0=0A= ada1: ATA-7 SATA 2.x device=0A= ada1: Serial Number 9QG9QKH4=0A= ada1: 150.000MB/s transfers (SATA 1.x, UDMA5, PIO 8192bytes)=0A= ada1: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C)=0A= ada1: Previously was known as ad1=0A= cd0 at ata0 bus 0 scbus4 target 0 lun 0=0A= cd0: Removable CD-ROM SCSI device=0A= cd0: Serial Number M0064S32313=0A= cd0: 66.700MB/s transfers (UDMA4, ATAPI 12bytes, PIO 65534bytes)=0A= cd0: cd present [1100623 x 2048 byte records]=0A= SMP: AP CPU #1 launched=0A= ugen2.2: at usbus2=0A= umass0: on usbus2=0A= umass0: SCSI over Bulk-Only; quirks =3D 0x0100=0A= umass0:6:0:-1: Attached to scbus6=0A= sa0 at umass-sim0 bus 0 scbus6 target 0 lun 0=0A= sa0: Removable Sequential Access SCSI-3 device=0A= sa0: Serial Number 48553108084D3639=0A= sa0: 40.000MB/s transfers=0A= ugen2.3: at usbus2=0A= uhub3: = on usbus2=0A= uhub3: MTT enabled=0A= uhub3: 3 ports with 2 removable, self powered=0A= ugen2.4: at usbus2=0A= uhub4: on usbus2=0A= uhub4: 3 ports with 2 removable, bus powered=0A= ugen2.5: at usbus2=0A= ukbd0: on usbus2=0A= kbd1 at ukbd0=0A= uhid0: on usbus2=0A= ugen2.6: at usbus2=0A= hid_get_item: Number of items truncated to 255=0A= hid_get_item: Number of items truncated to 255=0A= uhid1: = on usbus2=0A= hid_get_item: Number of items truncated to 255=0A= hid_get_item: Number of items truncated to 255=0A= hid_get_item: Number of items truncated to 255=0A= Root mount waiting for: usbus2=0A= ugen2.7: at usbus2=0A= ums0: on usbus2=0A= ums0: 4 buttons and [XYZW] coordinates ID=3D0=0A= Trying to mount root from ufs:/dev/ada0s3 [rw]...=0A= ugen0.2: at usbus0=0A= ukbd1: = on usbus0=0A= kbd2 at ukbd1=0A= ums1: = on usbus0=0A= ums1: 5 buttons and [XY] coordinates ID=3D0=0A= pid 1258 (firefox), uid 0: exited on signal 11 (core dumped)=0A= (sa0:umass-sim0:0:0:0): REWIND. CDB: 01 00 00 00 00 00 =0A= (sa0:umass-sim0:0:0:0): CAM status: CCB request completed with an error=0A= (sa0:umass-sim0:0:0:0): Retrying command=0A= (sa0:umass-sim0:0:0:0): REWIND. CDB: 01 00 00 00 00 00 =0A= (sa0:umass-sim0:0:0:0): CAM status: SCSI Status Error=0A= (sa0:umass-sim0:0:0:0): SCSI status: Check Condition=0A= (sa0:umass-sim0:0:0:0): SCSI sense: UNIT ATTENTION asc:29,2 (SCSI bus = reset occurred)=0A= (sa0:umass-sim0:0:0:0): Retrying command (per sense data)=0A= (sa0:umass-sim0:0:0:0): SPACE(6). CDB: 11 00 00 26 46 00 =0A= (sa0:umass-sim0:0:0:0): CAM status: CCB request completed with an error=0A= (sa0:umass-sim0:0:0:0): Error 5, Retries exhausted=0A= pid 95271 (about-gui), uid 0: exited on signal 11 (core dumped)=0A= pid 95299 (pc-usermanager), uid 0: exited on signal 11 (core dumped)=0A= pid 95310 (pc-sysinstaller), uid 0: exited on signal 11 (core dumped)=0A= pid 95303 (pc-sysinstaller), uid 0: exited on signal 11 (core dumped)=0A= pid 95573 (pc-servicemanager), uid 0: exited on signal 11 (core dumped)=0A= pid 6075 (python2.7), uid 0: exited on signal 11 (core dumped)=0A= pid 1503 (firefox), uid 0: exited on signal 6 (core dumped)=0A= ------=_NextPart_000_00AB_01D11BFB.72412BF0-- From owner-freebsd-ppc@freebsd.org Thu Nov 12 21:33:35 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 74F20A2D76F for ; Thu, 12 Nov 2015 21:33:35 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 58BAC1919 for ; Thu, 12 Nov 2015 21:33:35 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from zeppelin.tachypleus.net (airbears2-136-152-142-62.airbears2.berkeley.edu [136.152.142.62]) (authenticated bits=0) by c.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id tACLXSZO022236 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 12 Nov 2015 13:33:28 -0800 Subject: Re: FreeBSD on an IBM Virtual I/O Server (VIOS) To: Pascal Drecker , freebsd-ppc@freebsd.org References: <002d01d11a71$c2d60e90$48822bb0$@freebsd.drecker.com> <563FDEFA.4030900@freebsd.org> <000801d11ae7$770af770$6520e650$@freebsd.drecker.com> From: Nathan Whitehorn Message-ID: <564505A2.1080806@freebsd.org> Date: Thu, 12 Nov 2015 13:33:22 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <000801d11ae7$770af770$6520e650$@freebsd.drecker.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Sonic-CAuth: UmFuZG9tSVYmgCtHY5H0wmUfYthMEyF1Rva5P87hY7ivELip1/tlRgCAvl0pdHdn9/k/Ir23dE7uHk19IQ7O3MkDoHFRj2bVA+mMnDWy3f8= X-Sonic-ID: C;CukdA4WJ5RGIaL0U9jFv0A== M;JodUA4WJ5RGIaL0U9jFv0A== X-Spam-Flag: No X-Sonic-Spam-Details: 0.0/5.0 by cerberusd 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: Thu, 12 Nov 2015 21:33:35 -0000 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" >> > From owner-freebsd-ppc@freebsd.org Sat Nov 14 10:58:22 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 3B764A2DC24 for ; Sat, 14 Nov 2015 10:58:22 +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 CBE741AC9; Sat, 14 Nov 2015 10:58:21 +0000 (UTC) (envelope-from pascal@freebsd.drecker.com) Received: from pdreckerw10 (unknown [172.16.64.126]) by mail.perfidia.de (Postfix) with ESMTPSA id 8A7234188B; Sat, 14 Nov 2015 11:58:09 +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> In-Reply-To: <564505A2.1080806@freebsd.org> Subject: RE: FreeBSD on an IBM Virtual I/O Server (VIOS) Date: Sat, 14 Nov 2015 11:58:10 +0100 Message-ID: <000701d11ecb$5b056690$111033b0$@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+BcihISmcvlztvYtZH2QIEn9tjAdTmsYgB3DB21Z0kr6uA 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: Sat, 14 Nov 2015 10:58:22 -0000 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" >> > From owner-freebsd-ppc@freebsd.org Sat Nov 14 17:49:54 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 78367A2F1E9 for ; Sat, 14 Nov 2015 17:49:54 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 617751818 for ; Sat, 14 Nov 2015 17:49:54 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from zeppelin.tachypleus.net (75-101-50-44.static.sonic.net [75.101.50.44]) (authenticated bits=0) by c.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id tAEHneGH029496 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sat, 14 Nov 2015 09:49:41 -0800 Subject: Re: FreeBSD on an IBM Virtual I/O Server (VIOS) To: Pascal Drecker , freebsd-ppc@freebsd.org 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> From: Nathan Whitehorn Message-ID: <56477434.604@freebsd.org> Date: Sat, 14 Nov 2015 09:49:40 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <000701d11ecb$5b056690$111033b0$@freebsd.drecker.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Sonic-CAuth: UmFuZG9tSVYSG/hDHSksKal6egpSLAbZPygWzAr3WeqHSDDZsJnFjJ0HlcoQlHPwptVaF3Qb3mXXqkxla7+KUQmWDbMQt6cF+6Ssz+c3FJU= X-Sonic-ID: C;DK/KFPiK5RGCU70U9jFv0A== M;5HE5FfiK5RGCU70U9jFv0A== X-Spam-Flag: No X-Sonic-Spam-Details: 0.0/5.0 by cerberusd 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: Sat, 14 Nov 2015 17:49:54 -0000 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" >>> >