From matt at genesi-usa.com Wed Oct 1 02:43:32 2008 From: matt at genesi-usa.com (Matt Sealey) Date: Wed Oct 1 02:43:39 2008 Subject: 64-bit atomic ops on 32-bit CPU -- was: ZFS .. on PowerPC ? In-Reply-To: <48E29BF3.40106@freebsd.org> References: <60ACBA3B-927C-4F2C-8680-A6B40B81E06C@mac.com> <48DA84D5.4010109@semihalf.com> <48DA99F8.7070904@semihalf.com> <111399E3-2BC7-4724-8AFB-A40F2A47E66D@mac.com> <48DBC59C.3040101@semihalf.com> <48E28E58.1020901@genesi-usa.com> <48E29BF3.40106@freebsd.org> Message-ID: <48E2E3D2.7020206@genesi-usa.com> Peter Grehan wrote: > Hi Matt, > >> Isn't there some kind of semaphore primitive in FreeBSD that can be >> used? > > The issue is the OpenSolaris ZFS code that makes liberal use of calls > such as atomic_add_64(&ptr_to_uint64). Indeed I had a look at the ZFS-FUSE project a while back, had a lot of discussion with the developer, and even got Tom Riddle of Sun involved in implementing a lot of the 32-bit atomicity code which wasn't present in Solaris at the time. > global lock for all 64-bit atomic operations, but it would be better if > this could be done without such workarounds on 32-bit ppc. What makes this any different to the Giant Lock problem? I don't suppose it needs to be TOO fine grained - after all there are still big locks in FreeBSD, Linux and pick-another-OS, they are just not so clumsy as the old FreeBSD Giant or Linux's equivalent. Stripping it down so that you have many 64-bit atomic access locks first, would be probably an easier task than attempting to come up with some clever way of implementing 64-bit atomicity on all 32-bit PPC processors. Why not simply access protect individual structures? For instance anything which you have to update some member in an atomic manner, lock the entire structure. Other atomic accesses can be made to other structures in parallel (within reason, since PPC can only hold one reservation at a time, so trying to get two locks in tandem will fail, but in this case, one will work, the atomic update will happen, and the other lock attempt will spin until it succeeds.. and then that atomic update will happen) -- Matt Sealey Genesi, Manager, Developer Relations From horst at sxemacs.org Thu Oct 2 22:31:33 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Thu Oct 2 22:31:42 2008 Subject: Extreme difficulty with partitioning on mac powerpc g4. Message-ID: <1222945436.15248.103.camel@horst-tla> Good evening. I'm having some significant trouble using the install.iso for ppc. This trouble being (with both 7.0-RELEASE and 7.1-BETA) that the installer insists on doing its partitioning with fdisk. I have used linux fdisk to make the partition tables up, and failing this attempted some semblance of partitioning with Mac OS X Disk Utility (an idea taken from OpenBSD install docs for ppc). I also attempted to use GParted, and none of these attempts at partitioning are being picked up. It all comes back to me hitting "custom install" as I always do, and the damned partitioner, and me trying to do _anything_ results in a SIG11 (Segmentation Violation i believe). a) Is there a known workaround? ` - b) If there is, why are there no docs anywhere on the internet? ` - c) If (following either assistance or dumb luck) I get it working, would a "walkthrough" be welcomed? (see lack of docs) |- d) If no known workaround, are there any suggestions from the ppc devs and users on this ML? Extra info: this is a Power Mac G4 (ADC/Gigabit Ethernet) with two harddrives: one 40GB and one 60GB. My intended partition layout is: /---------------- IDE0 Master: 40GB ----------------- Partition 0: (smallest amount possible) (whatever's needed to allow autoboot into FreeBSD, I've nuked OS X) Partition 1: (the remainder) FreeBSD UFS2, mountpoint / IDE0 Slave : 60GB ----------------- Partition 0: 2GB FreeBSD swap Partition 1: 58GB FreeBSD UFS2, mountpoint /usr \---------------- This is my first attempt at FreeBSD on a ppc, doubly so for a mac. I'm not, however, completely new to FreeBSD, I've run it before. Any help anyone here could provide in this matter would be much appreciated, and I will help as I can in procuring information for you if you require. I apologise for the incoherence of this message, I'm quite distressed by this. --Horst. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081002/a6ba43a0/attachment.pgp From nwhitehorn at freebsd.org Fri Oct 3 00:33:43 2008 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Fri Oct 3 00:33:49 2008 Subject: ADB support? [UPDATE] In-Reply-To: <48E0DDE6.5030909@freebsd.org> References: <46171.83.233.155.226.1222694615.squirrel@webmail.student.lth.se> <48E0DDE6.5030909@freebsd.org> Message-ID: <48E56977.9050407@freebsd.org> Nathan Whitehorn wrote: > Andreas J?nsson wrote: >> Hi, >> >> I'm wondering how the ADB keyboard support is coming along? >> The last thing I've seen on this list is from July. > > I've been stymied by a lack of hardware. It works great on my PowerMac > G3, but that has a different controller chip (CUDA) than the one > everybody wants support for (PMU, found in laptops). My current work is > here: > > http://people.freebsd.org/~nwhitehorn/adb.diff > > It has a PMU driver, which may just work. Of course, it more likely > won't... Motivated people are welcome to hack it, and I'd appreciate any > reports. To add this support, apply the patch to sys on a recent > -CURRENT, add the following to your kernel config, and recompile: > > device cuda > device pmu > device adb It appears my ability to fix bugs without hardware is better than I thought. I managed to borrow a G4 iBook today, and the internal keyboard works perfectly with the above patch applied. I'd appreciate some more testing, and will clean it up a little before committing. On another note, it appears that loader is broken on this machine. I had to roll back to one from the end of 2007 to get it to boot -- it stalled right before loading loader.conf. Maybe it has to do with how it started opening the NIC several times? -Nathan From andreast-list at fgznet.ch Fri Oct 3 19:15:09 2008 From: andreast-list at fgznet.ch (Andreas Tobler) Date: Fri Oct 3 19:15:16 2008 Subject: ppc project page change request. Message-ID: <48E66895.2030002@fgznet.ch> Hi, could someone please adjust my e-mail address in the section of 'Supported Hardware'? s/toa@pop.agri.ch/andreast-list@fgznet.ch/ Thanks, Andreas From minimarmot at gmail.com Fri Oct 3 19:20:23 2008 From: minimarmot at gmail.com (Ben Kaduk) Date: Fri Oct 3 19:20:30 2008 Subject: ADB support? [UPDATE] In-Reply-To: <48E56977.9050407@freebsd.org> References: <46171.83.233.155.226.1222694615.squirrel@webmail.student.lth.se> <48E0DDE6.5030909@freebsd.org> <48E56977.9050407@freebsd.org> Message-ID: <47d0403c0810031154m4fb03e41m651627b6f19fb22d@mail.gmail.com> On Thu, Oct 2, 2008 at 8:38 PM, Nathan Whitehorn wrote: > Nathan Whitehorn wrote: >> >> Andreas J?nsson wrote: >>> >>> Hi, >>> >>> I'm wondering how the ADB keyboard support is coming along? >>> The last thing I've seen on this list is from July. >> >> I've been stymied by a lack of hardware. It works great on my PowerMac G3, >> but that has a different controller chip (CUDA) than the one everybody wants >> support for (PMU, found in laptops). My current work is here: >> >> http://people.freebsd.org/~nwhitehorn/adb.diff >> >> It has a PMU driver, which may just work. Of course, it more likely >> won't... Motivated people are welcome to hack it, and I'd appreciate any >> reports. To add this support, apply the patch to sys on a recent -CURRENT, >> add the following to your kernel config, and recompile: >> >> device cuda >> device pmu >> device adb > > It appears my ability to fix bugs without hardware is better than I thought. > I managed to borrow a G4 iBook today, and the internal keyboard works > perfectly with the above patch applied. I'd appreciate some more testing, > and will clean it up a little before committing. > > On another note, it appears that loader is broken on this machine. I had to > roll back to one from the end of 2007 to get it to boot -- it stalled right > before loading loader.conf. Maybe it has to do with how it started opening > the NIC several times? > -Nathan I have a late-model iBook G4 that I'll test, once I get my (new) T400 thinkpad in a useable state. Thanks for putting all this work in! -Ben Kaduk From marcotrillo at gmail.com Sat Oct 4 18:25:50 2008 From: marcotrillo at gmail.com (Marco Trillo) Date: Sat Oct 4 18:25:56 2008 Subject: Apple Burgundy Audio: looking for testers Message-ID: Hi all, I've implemented output support for the Apple "Burgundy" audio device, in addition to the "Screamer" one which I mentioned in my earlier message (both of these use same DAVbus-style controller). These are the new-world machines wich this chip: - "PowerMac1,1" PowerMac G3 Blue&White - "PowerMac1,2" PowerMac G4 PCI graphics (Yikes) - "iMac,1" original iMac rev. A-D Anyone with one of these machines interested in testing it? Thanks, Marco. From grehan at freebsd.org Sat Oct 4 20:15:23 2008 From: grehan at freebsd.org (Peter Grehan) Date: Sat Oct 4 20:15:30 2008 Subject: Apple Burgundy Audio: looking for testers Message-ID: <20081005061439.EJS23099@dommail.onthenet.com.au> Hi Marco, >These are the new-world machines wich this chip: > >- "PowerMac1,1" PowerMac G3 Blue&White >- "PowerMac1,2" PowerMac G4 PCI graphics (Yikes) I have both of these :) >- "iMac,1" original iMac rev. A-D Used to have a rev B too though not anymore. Might take a while to dig the old machines out, but send me your patch anyways. later, Peter. From jrh29 at alumni.cwru.edu Sun Oct 5 13:42:45 2008 From: jrh29 at alumni.cwru.edu (Justin Hibbits) Date: Sun Oct 5 13:42:51 2008 Subject: Apple Burgundy Audio: looking for testers In-Reply-To: References: Message-ID: <20081005133119.GA64232@narn.knownspace> On Sat, Oct 04, 2008 at 08:25:49PM +0200, Marco Trillo wrote: > Hi all, > > I've implemented output support for the Apple "Burgundy" audio device, > in addition to the "Screamer" one which I mentioned in my earlier > message (both of these use same DAVbus-style controller). > > These are the new-world machines wich this chip: > > - "PowerMac1,1" PowerMac G3 Blue&White > - "PowerMac1,2" PowerMac G4 PCI graphics (Yikes) > - "iMac,1" original iMac rev. A-D > > Anyone with one of these machines interested in testing it? > > Thanks, > Marco. I don't have either of these, but I do have a "Snapper" audio controller. How hard would it be to write that driver, either by extending your existing driver, or porting the one from NetBSD? - Justin From marcotrillo at gmail.com Sun Oct 5 14:00:57 2008 From: marcotrillo at gmail.com (Marco Trillo) Date: Sun Oct 5 14:01:12 2008 Subject: Apple Burgundy Audio: looking for testers In-Reply-To: <20081005133119.GA64232@narn.knownspace> References: <20081005133119.GA64232@narn.knownspace> Message-ID: Hi, On Sun, Oct 5, 2008 at 3:31 PM, Justin Hibbits wrote: > On Sat, Oct 04, 2008 at 08:25:49PM +0200, Marco Trillo wrote: >> I've implemented output support for the Apple "Burgundy" audio device, >> in addition to the "Screamer" one which I mentioned in my earlier >> message (both of these use same DAVbus-style controller). >> >> These are the new-world machines wich this chip: >> >> - "PowerMac1,1" PowerMac G3 Blue&White >> - "PowerMac1,2" PowerMac G4 PCI graphics (Yikes) >> - "iMac,1" original iMac rev. A-D >> >> Anyone with one of these machines interested in testing it? >> >> Thanks, >> Marco. > > I don't have either of these, but I do have a "Snapper" audio controller. How > hard would it be to write that driver, either by extending your existing driver, > or porting the one from NetBSD? Support for the "Snapper" and "Tumbler" codecs is next on my todo list -- in fact I already have support for the I2S controller used there -- and it's almost ready. I'll post another message when I have it finished. Thanks! Marco. From andreast-list at fgznet.ch Sun Oct 5 21:00:22 2008 From: andreast-list at fgznet.ch (Andreas Tobler) Date: Sun Oct 5 21:00:28 2008 Subject: Call for testers: Apple ATA DMA In-Reply-To: <0D5AE023-0D54-43BA-A325-0E1BEEC39D28@mac.com> References: <48D389EE.9000207@FreeBSD.org> <645CD2B8-11A0-42E8-B5F9-C04DCF21F763@mac.com> <48D84C12.7070207@freebsd.org> <0DD89065-9CF3-45E4-89A0-70D6BBB9621D@mac.com> <48D92D44.6080807@freebsd.org> <48DA4037.9000508@freebsd.org> <48DBD6C0.5070005@freebsd.org> <48DD2DF7.2020901@freebsd.org> <48DDAC14.9070604@freebsd.org> <48DE7C93.5050506@freebsd.org> <0D5AE023-0D54-43BA-A325-0E1BEEC39D28@mac.com> Message-ID: <48E92AE2.108@fgznet.ch> Marcel Moolenaar wrote: > > On Sep 27, 2008, at 11:33 AM, Nathan Whitehorn wrote: > >> Peter Grehan wrote: >>> Hi Nathan, >>> > If I can get positive reports from a few more people who were >>>> having trouble, I'll drop this in the tree. >>> The imac's ata-4 is working solidly at UDMA-66. The difference in CPU >>> usage and i/o with dd at 32k block size is stunning: 2MB/7% idle >>> before, 18MB/75% idle with your patch. >> >> I guess DMA is a useful technology :) >> >> Thanks for testing -- I've committed the patch. I'll revisit it when >> Marcel tests it on Monday and it erases his hard drive... > > Good and bad news. > > The good: my Xserve is working fine and acd0 is now using UDMA33 > instead of BIOSPIO. > > The bad: my Mac Mini G4 is still having the same problems. This > is ad0 at UDMA66 and acd0 at UDMA33. I'll experiment with it a > bit later... I'll pick up here. Here I have a imac slot-loading, don't know which revision offhand. It's a 500MHz piece w/o fan. ad0: 78167MB at ata0-master UDMA66 acd0: DVDR at ata0-slave UDMA33 GEOM_LABEL: Label for provider acd0 is iso9660/CDROM. WARNING: WITNESS option enabled, expect reduced performance. Trying to mount root from ufs:/dev/ad0s10 lock order reversal: 1st 0xe19000 vfslock (vfslock) @ /usr/src/sys/kern/vfs_subr.c:372 2nd 0xdcce2c devfs (devfs) @ /usr/src/sys/kern/vfs_lookup.c:428 3rd 0xe18d48 vfslock (vfslock) @ /usr/src/sys/kern/vfs_subr.c:372 KDB: stack backtrace: 0xdf2cc898: at kdb_backtrace+0x4c 0xdf2cc8a8: at _witness_debugger+0x3c 0xdf2cc8c8: at witness_checkorder+0x878 0xdf2cc928: at __lockmgr_args+0x23c 0xdf2cc9a8: at vfs_busy+0x19c 0xdf2cc9c8: at vfs_mount_alloc+0x80 0xdf2cc9f8: at vfs_donmount+0xfe0 0xdf2ccba8: at kernel_mount+0x98 0xdf2ccbe8: at kernel_vmount+0xdc 0xdf2ccc28: at vfs_mountroot_try+0x110 0xdf2cccd8: at vfs_mountroot+0x424 0xdf2ccd38: at start_init+0x88 0xdf2ccd98: at fork_exit+0xf0 0xdf2ccdc8: at fork_trampoline+0xc lock order reversal: 1st 0xdcc9ec ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2051 2nd 0xe19000 vfslock (vfslock) @ /usr/src/sys/kern/vfs_subr.c:372 KDB: stack backtrace: 0xdf2cc928: at kdb_backtrace+0x4c 0xdf2cc938: at _witness_debugger+0x3c 0xdf2cc958: at witness_checkorder+0x878 0xdf2cc9b8: at __lockmgr_args+0x23c 0xdf2cca38: at vfs_busy+0x19c 0xdf2cca58: at lookup+0x86c 0xdf2ccae8: at namei+0x4a8 0xdf2ccb68: at kern_unlinkat+0x98 0xdf2ccc18: at kern_unlink+0x24 0xdf2ccc28: at vfs_mountroot_try+0x434 0xdf2cccd8: at vfs_mountroot+0x424 0xdf2ccd38: at start_init+0x88 0xdf2ccd98: at fork_exit+0xf0 0xdf2ccdc8: at fork_trampoline+0xc lock order reversal: 1st 0xc41048 user map (user map) @ /usr/src/sys/vm/vm_map.c:3115 2nd 0xdcc7cc ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2051 KDB: stack backtrace: 0xdf2cc960: at kdb_backtrace+0x4c 0xdf2cc970: at _witness_debugger+0x3c 0xdf2cc990: at witness_checkorder+0x878 0xdf2cc9f0: at __lockmgr_args+0x23c 0xdf2cca70: at ffs_lock+0x9c 0xdf2ccaa0: at VOP_LOCK1_APV+0xec 0xdf2ccac0: at _vn_lock+0x84 0xdf2ccb10: at vget+0xdc 0xdf2ccb50: at vnode_pager_lock+0x20c 0xdf2ccba0: at vm_fault+0x218 0xdf2cccb0: at trap_pfault+0x128 0xdf2ccce0: at trap+0x1ac 0xdf2ccda0: at powerpc_interrupt+0x15c 0xdf2ccdd0: user ISI trap by 0x1818714: srr1=0x4000d032 r1=0x7fffdee0 cr=0x24000048 xer=0 ctr=0 lock order reversal: 1st 0xd871c708 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:2443 2nd 0xff32800 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirhash.c:254 KDB: stack backtrace: 0xe1748780: at kdb_backtrace+0x4c 0xe1748790: at _witness_debugger+0x3c 0xe17487b0: at witness_checkorder+0x878 0xe1748810: at _sx_xlock+0x90 0xe1748840: at ufsdirhash_acquire+0x40 0xe1748860: at ufsdirhash_add+0x30 0xe1748880: at ufs_direnter+0x6d4 0xe17488f0: at ufs_makeinode+0x498 0xe1748a50: at ufs_create+0x44 0xe1748a60: at VOP_CREATE_APV+0xe0 0xe1748a80: at vn_open_cred+0x208 0xe1748b70: at vn_open+0x20 0xe1748b80: at kern_openat+0x11c 0xe1748cc0: at kern_open+0x34 0xe1748cd0: at open+0x28 0xe1748ce0: at trap+0x460 0xe1748da0: at powerpc_interrupt+0x15c 0xe1748dd0: user SC trap by 0x21b17df8: srr1=0xd032 r1=0x7f8f8dc0 cr=0x44002022 xer=0 ctr=0x21a08290 I did an upgrade from 7.0 with csup since the snapshots do not boot. After that I tried a buildworld with several hassles, after all I managed to install the whole stuff and the only thing which makes me curious is the one above, the LOR's. Do I have to worry about? @ Nathan, hat off, it feels snappier with your DMA stuff, THANKS! I'd like to help testing, especially the work from Nathan and Marco. Regards, Andreas From jrh29 at alumni.cwru.edu Mon Oct 6 02:02:57 2008 From: jrh29 at alumni.cwru.edu (Justin Hibbits) Date: Mon Oct 6 02:03:03 2008 Subject: Extreme difficulty with partitioning on mac powerpc g4. In-Reply-To: <1222945436.15248.103.camel@horst-tla> References: <1222945436.15248.103.camel@horst-tla> Message-ID: <20081006020251.GA1128@narn.knownspace> On Thu, Oct 02, 2008 at 09:03:56PM +1000, Horst G?nther Burkhardt III wrote: > a) Is there a known workaround? > ` - b) If there is, why are there no docs anywhere on the internet? > ` - c) If (following either assistance or dumb luck) I get it > working, would a "walkthrough" be welcomed? (see lack of docs) > |- d) If no known workaround, are there any suggestions from the ppc > devs and users on this ML? > > Extra info: this is a Power Mac G4 (ADC/Gigabit Ethernet) with two > harddrives: one 40GB and one 60GB. > > My intended partition layout is: > > /---------------- > IDE0 Master: 40GB > ----------------- > Partition 0: (smallest amount possible) (whatever's needed to allow > autoboot into FreeBSD, I've > nuked OS X) > > Partition 1: (the remainder) FreeBSD UFS2, mountpoint / > > > > IDE0 Slave : 60GB > ----------------- > Partition 0: 2GB FreeBSD swap > Partition 1: 58GB FreeBSD UFS2, mountpoint /usr > \---------------- I don't think partitioning is supported on ppc yet. Better to use the OS X Disk Utility, or another PPC partitioner before installing FreeBSD. > --Horst. - Justin From nwhitehorn at freebsd.org Mon Oct 6 04:15:05 2008 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Mon Oct 6 04:15:12 2008 Subject: Call for testers: Apple ATA DMA In-Reply-To: <48E92AE2.108@fgznet.ch> References: <48D389EE.9000207@FreeBSD.org> <645CD2B8-11A0-42E8-B5F9-C04DCF21F763@mac.com> <48D84C12.7070207@freebsd.org> <0DD89065-9CF3-45E4-89A0-70D6BBB9621D@mac.com> <48D92D44.6080807@freebsd.org> <48DA4037.9000508@freebsd.org> <48DBD6C0.5070005@freebsd.org> <48DD2DF7.2020901@freebsd.org> <48DDAC14.9070604@freebsd.org> <48DE7C93.5050506@freebsd.org> <0D5AE023-0D54-43BA-A325-0E1BEEC39D28@mac.com> <48E92AE2.108@fgznet.ch> Message-ID: On Sun, 05 Oct 2008 23:00:18 +0200, Andreas Tobler wrote: > Marcel Moolenaar wrote: >> >> On Sep 27, 2008, at 11:33 AM, Nathan Whitehorn wrote: >> >>> Peter Grehan wrote: >>>> Hi Nathan, >>>> > If I can get positive reports from a few more people who were >>>>> having trouble, I'll drop this in the tree. >>>> The imac's ata-4 is working solidly at UDMA-66. The difference in CPU >>>> usage and i/o with dd at 32k block size is stunning: 2MB/7% idle >>>> before, 18MB/75% idle with your patch. >>> >>> I guess DMA is a useful technology :) >>> >>> Thanks for testing -- I've committed the patch. I'll revisit it when >>> Marcel tests it on Monday and it erases his hard drive... >> >> Good and bad news. >> >> The good: my Xserve is working fine and acd0 is now using UDMA33 >> instead of BIOSPIO. >> >> The bad: my Mac Mini G4 is still having the same problems. This >> is ad0 at UDMA66 and acd0 at UDMA33. I'll experiment with it a >> bit later... > > I'll pick up here. > > Here I have a imac slot-loading, don't know which revision offhand. It's > a 500MHz piece w/o fan. > > [snipped dmesg] > > I did an upgrade from 7.0 with csup since the snapshots do not boot. The not booting is a bad sign. I know netbooting is broken for me on some machines with the current loader, due to changes in how it opens the network device which marius reverted for sparc64. > After that I tried a buildworld with several hassles, after all I > managed to install the whole stuff and the only thing which makes me > curious is the one above, the LOR's. > > Do I have to worry about? Nope. This is standard at the moment, and will get cleaned up eventually. I'd suggest turning off WITNESS and INVARIANTS in your kernel config, unless you are debugging something. It should speed up your system nicely. > @ Nathan, hat off, it feels snappier with your DMA stuff, THANKS! Glad to hear it! -Nathan From bugmaster at FreeBSD.org Mon Oct 6 11:07:00 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Oct 6 11:08:39 2008 Subject: Current problem reports assigned to freebsd-ppc@FreeBSD.org Message-ID: <200810061106.m96B6x07035573@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- a power/121407 ppc [panic] Won't boot up; strange error message. o power/112435 ppc [nexus] [patch] Update nexus children to use ofw_bus f o power/111296 ppc [kernel] [patch] [request] Support IMISS, DLMISS an DS o power/93203 ppc FreeBSD PPC Can't Write to Partitions. 4 problems total. From andreast-list at fgznet.ch Mon Oct 6 14:01:37 2008 From: andreast-list at fgznet.ch (Andreas Tobler) Date: Mon Oct 6 14:01:44 2008 Subject: Apple Screamer Audio: looking for testers In-Reply-To: References: Message-ID: <48EA1A3D.3010607@fgznet.ch> Hi Marco, Marco Trillo wrote: > - "PowerMac2,2" iMac DV ('00) (screamer, Device ID 11) This is one I own and it runs with CURRENT now. Tell me what to do. I picked the aoa.c from one your recent mails plus the dbma patch. Is there something else needed? TIA, Andreas From marcotrillo at gmail.com Mon Oct 6 15:48:27 2008 From: marcotrillo at gmail.com (Marco Trillo) Date: Mon Oct 6 15:48:33 2008 Subject: Apple Screamer Audio: looking for testers In-Reply-To: <48EA1A3D.3010607@fgznet.ch> References: <48EA1A3D.3010607@fgznet.ch> Message-ID: Hi, On Mon, Oct 6, 2008 at 4:01 PM, Andreas Tobler wrote: >> - "PowerMac2,2" iMac DV ('00) (screamer, Device ID 11) > > This is one I own and it runs with CURRENT now. > > Tell me what to do. I picked the aoa.c from one your recent mails plus the > dbma patch. Is there something else needed? Thank you for the interest! Just put the aoa.c file in sys/powerpc/powermac and enable the aoa.c driver in the kernel config, as in the following patch, and compile the kernel: --- conf/files.powerpc.orig 2008-10-04 17:12:47.000000000 +0000 +++ conf/files.powerpc 2008-10-04 17:13:09.000000000 +0000 @@ -107,6 +107,7 @@ powerpc/ofw/ofw_pci.c optional pci aim powerpc/ofw/ofw_pcib_pci.c optional pci aim powerpc/ofw/ofw_syscons.c optional sc aim +powerpc/powermac/aoa.c optional powermac pci aoa powerpc/powermac/ata_kauai.c optional powermac ata powerpc/powermac/ata_macio.c optional powermac ata powerpc/powermac/ata_dbdma.c optional powermac ata --- powerpc/conf/GENERIC 2008-08-20 08:31:58.000000000 +0000 +++ powerpc/conf/GENERIC 2008-10-04 17:14:19.000000000 +0000 @@ -79,6 +79,10 @@ # Standard busses device pci +# Sound devices +device sound +device aoa # Apple Onboard Audio (AOA) + # ATA and ATAPI devices device ata device atadisk # ATA disk drives Hope it works fine for you, Marco. From andreast-list at fgznet.ch Mon Oct 6 19:54:39 2008 From: andreast-list at fgznet.ch (Andreas Tobler) Date: Mon Oct 6 19:54:45 2008 Subject: physical memory limit? Message-ID: <48EA6CFB.8090002@fgznet.ch> Hi there, is there an upper physical memory size limitation on ppc? I play on a G3 imac with 1GB memory. On CURRENT. I often get SIGSEGV and a rebuild on that component succeeds. So, for me it seems strange. I'll change some DIMM's and see how far I get. But nevertheless, I remember back in 05, I had to reduce hw.physmem to 512MB. Is this still needed, Peter? TIA, Andreas From grehan at freebsd.org Mon Oct 6 20:39:41 2008 From: grehan at freebsd.org (Peter Grehan) Date: Mon Oct 6 20:39:47 2008 Subject: physical memory limit? Message-ID: <20081007063857.EJV27136@dommail.onthenet.com.au> Hi Andreas, >is there an upper physical memory size limitation on ppc? For an AIM system (G3/4/5) which is essentially Apple h/w, it's 2GB since Apple like to memory-map i/o above that. >I play on a G3 imac with 1GB memory. On CURRENT. I often >get SIGSEGV and a rebuild on that component succeeds. >So, for me it seems strange. I'll change some DIMM's and >see how far I get. I've not had that much RAM in a G3, but certainly have had 1GB in a number of G4's without problems. I'm guessing it's a VM bug rather than bad memory. Was the component you were building using a lot of VM ? (e.g. KDE) later, Peter. From andreast-list at fgznet.ch Mon Oct 6 20:54:55 2008 From: andreast-list at fgznet.ch (Andreas Tobler) Date: Mon Oct 6 20:55:02 2008 Subject: physical memory limit? In-Reply-To: <20081007063857.EJV27136@dommail.onthenet.com.au> References: <20081007063857.EJV27136@dommail.onthenet.com.au> Message-ID: <48EA7B1B.9050006@fgznet.ch> Hi Peter, Peter Grehan wrote: >> is there an upper physical memory size limitation on ppc? > > For an AIM system (G3/4/5) which is essentially Apple h/w, > it's 2GB since Apple like to memory-map i/o above that. Fortunately I have no more slots to fill :) >> I play on a G3 imac with 1GB memory. On CURRENT. I often >> get SIGSEGV and a rebuild on that component succeeds. >> So, for me it seems strange. I'll change some DIMM's and >> see how far I get. > > I've not had that much RAM in a G3, but certainly have had > 1GB in a number of G4's without problems. I'm guessing it's a > VM bug rather than bad memory. Was the component you were > building using a lot of VM ? (e.g. KDE) I remember back in 05 we had a similar issue when I tried 'buildworld' on a G4 alu book. Then you suggested to me to reduce hw.physmem to 512MB. Right now the failing parts are sporadic, during buildworld or buildkernel. For example, kerberos5 or openssl. Also nfs in buildkernel. You see somehow not predictable. A run over the failing part solves the 11. I'll reduce/replace the memory and see how it behaves. Thanks, Andreas From andreast-list at fgznet.ch Mon Oct 6 21:02:16 2008 From: andreast-list at fgznet.ch (Andreas Tobler) Date: Mon Oct 6 21:02:23 2008 Subject: Apple Screamer Audio: looking for testers In-Reply-To: References: <48EA1A3D.3010607@fgznet.ch> Message-ID: <48EA7CD4.7040404@fgznet.ch> Hi Marco, Marco Trillo wrote: > On Mon, Oct 6, 2008 at 4:01 PM, Andreas Tobler wrote: >>> - "PowerMac2,2" iMac DV ('00) (screamer, Device ID 11) >> This is one I own and it runs with CURRENT now. >> >> Tell me what to do. I picked the aoa.c from one your recent mails plus the >> dbma patch. Is there something else needed? > > Thank you for the interest! [snip] > Hope it works fine for you, Unfortunately, no. Silence. But this might be due to the fact that I do something wrong. I do not have the aifftools, so I simply tried the cdcontrol and there nothing happens, silence. Here the lines from dmesg: Oct 5 22:38:46 imacb kernel: pcm0: mem 0x14000- 0x14fff,0x8800-0x88ff,0x8900-0x89ff irq 24,9,10 on macio0 Oct 5 22:38:46 imacb kernel: interrupting at irq 9 Oct 5 22:38:46 imacb kernel: pcm0: [ITHREAD] Oct 5 22:38:46 imacb kernel: pcm0: codec: Oct 5 22:38:46 imacb kernel: pcm0: [ITHREAD] Oct 5 22:38:46 imacb kernel: Enabled outputs: SPEAKER Oct 5 22:38:46 imacb kernel: volume 3 3 Oct 5 22:38:46 imacb kernel: pcm_getbuffersize returned 65536 Oct 5 22:38:46 imacb kernel: aoa_dma_setprd: addr = 31064064, 32 slots Oct 5 22:38:46 imacb kernel: aoa_chan_setformat: format = 268435488 Oct 5 22:38:46 imacb kernel: aoa_chan_setspeed: speed = 44100 Oct 5 22:38:46 imacb kernel: aoa_chan_setformat: format = 268435488 Oct 5 22:38:46 imacb kernel: aoa_chan_setblocksize: blocksz = 2048, dma->blksz = 2048 Oct 5 22:38:46 imacb kernel: aoa_chan_setspeed: speed = 44100 Oct 5 22:38:46 imacb kernel: aoa_chan_setformat: format = 268435488 Oct 5 22:38:46 imacb kernel: aoa_chan_setblocksize: blocksz = 2048, dma->blksz = 2048 Oct 5 22:38:46 imacb kernel: aoa_chan_setblocksize: blocksz = 2048, dma->blksz = 2048 Oct 5 22:38:46 imacb kernel: aoa_chan_setspeed: speed = 44100 Oct 5 22:38:46 imacb kernel: aoa_chan_setformat: format = 268435488 Oct 5 22:38:46 imacb kernel: aoa_chan_setblocksize: blocksz = 2048, dma->blksz = 2048 I tried to plug/unplug headphones and I see on the stdout the detection of my action. But still no sound. Neither speaker nor headphones. Do you have an advice on how to test this feature? I tried to find the aifftools but the sf link seems broken. TIA, Andreas From marcotrillo at gmail.com Mon Oct 6 22:13:32 2008 From: marcotrillo at gmail.com (Marco Trillo) Date: Mon Oct 6 22:13:39 2008 Subject: Apple Screamer Audio: looking for testers In-Reply-To: <48EA7CD4.7040404@fgznet.ch> References: <48EA1A3D.3010607@fgznet.ch> <48EA7CD4.7040404@fgznet.ch> Message-ID: Hi, On Mon, Oct 6, 2008 at 11:02 PM, Andreas Tobler wrote: >> On Mon, Oct 6, 2008 at 4:01 PM, Andreas Tobler >> wrote: >>>> >>>> - "PowerMac2,2" iMac DV ('00) (screamer, Device ID 11) >>> >>> This is one I own and it runs with CURRENT now. >>> >>> Tell me what to do. I picked the aoa.c from one your recent mails plus >>> the >>> dbma patch. Is there something else needed? >> >> Thank you for the interest! > > [snip] > > >> Hope it works fine for you, > > Unfortunately, no. Silence. But this might be due to the fact that I do > something wrong. > I do not have the aifftools, so I simply tried the cdcontrol and there > nothing happens, silence. The 'cdcontrol' utility uses the CD drive itself to play the CD, it does not use the system digital audio device -- in fact it does not need sound support at all. To use the system audio device you can use a digital player -- many are available from the ports collection, for example "mpg321" for MP3 files. To play CDs you can rip the tracks from the CD with a tool such as "cdda2wav", "cdparanoia" or others, and then play the digital files with an audio player . The "aiffopen" utility is an example of such a player which reads AIFF files only. Thanks! Marco. From xcllnt at mac.com Tue Oct 7 02:00:05 2008 From: xcllnt at mac.com (Marcel Moolenaar) Date: Tue Oct 7 02:00:11 2008 Subject: Call for testers: Apple ATA DMA In-Reply-To: <48D92D44.6080807@freebsd.org> References: "b9c23c9f0809100322n1659cb36oa05acf2f13f3c7e1@mail.gmail.com" <48D389EE.9000207@FreeBSD.org> <48D3AD50.8070505@freebsd.org> <48D69679.1080701@freebsd.org> <48D7F437.1040603@FreeBSD.org> <645CD2B8-11A0-42E8-B5F9-C04DCF21F763@mac.com> <48D84C12.7070207@freebsd.org> <0DD89065-9CF3-45E4-89A0-70D6BBB9621D@mac.com> <48D92D44.6080807@freebsd.org> Message-ID: <87398D41-9E76-4694-969C-43D7006DC73D@mac.com> On Sep 23, 2008, at 10:54 AM, Nathan Whitehorn wrote: > Marcel Moolenaar wrote: *snip* >>>> Interesting. My G4 Mac Mini 1.5Ghz is hanging hard: >>>> : >>>> ad0: 76319MB at ata1-master UDMA100 >>>> acd0: DVDR at ata1-slave UDMA33 >>>> *hang* >>>> Could be related... *snip* > Ways to check if this is the problem: > 1) Limit devices to UDMA33. > 2) Disable DMA on acd0. I finally got some time to play around with it: o When I set hw.ata.ata_dma=0 & hw.ata.atapi_dma=0 at the loader prompt and boot, everything is fine and working in PIO4. o I can use atacontrol and change the mode of ad0 to udma4/udma66. o I can use atacontrol and change the mode of acd0 to udma2/udma33. o I can then change the mode of ad0 to udma5/udma100. Apparently udma100+udma33 can work, just not when it's configured automatically or directly... Could it make a difference if we first configure pio4 before we switch to udma? -- Marcel Moolenaar xcllnt@mac.com From grehan at freebsd.org Tue Oct 7 04:04:43 2008 From: grehan at freebsd.org (Peter Grehan) Date: Tue Oct 7 04:04:49 2008 Subject: physical memory limit? Message-ID: <20081007140359.EJV63125@dommail.onthenet.com.au> Hi Andreas, >I remember back in 05 we had a similar issue when I tried >'buildworld' on a G4 alu book. Then you suggested to me >to reduce hw.physmem to 512MB. Indeed, and I'm certain those problems were fixed in r1.115 of mmu_oea.c where the secondary PTEG hash was corrected. >I'll reduce/replace the memory and see how it behaves. OK, let us know how it goes. later, Peter. From horst at sxemacs.org Tue Oct 7 15:24:13 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Tue Oct 7 15:24:20 2008 Subject: bootloader installation Message-ID: <1223393073.15248.151.camel@horst-tla> I have installed FreeBSD, thanks to Richard for suggesting Finnix for partitioning, it did the job brilliantly. ... Where the hell is the bootloader? I can't find it anywhere, and thus don't know what to do with the 64MB HFS+ i set aside for it. :( Any help would be appreciated. Once again. My apologies for being horridly noobish here. -- Horst. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081007/9bef8bcd/attachment.pgp From nwhitehorn at freebsd.org Tue Oct 7 15:32:21 2008 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Tue Oct 7 15:32:28 2008 Subject: bootloader installation In-Reply-To: <1223393073.15248.151.camel@horst-tla> References: <1223393073.15248.151.camel@horst-tla> Message-ID: <48EB821B.80503@freebsd.org> Horst G?nther Burkhardt III wrote: > I have installed FreeBSD, thanks to Richard for suggesting Finnix for > partitioning, it did the job brilliantly. > > ... Where the hell is the bootloader? I can't find it anywhere, and thus > don't know what to do with the 64MB HFS+ i set aside for it. :( > > Any help would be appreciated. Once again. > > My apologies for being horridly noobish here. > -- Horst. It is /boot/loader. There is a boot.tbxi that you can install too (and find in /usr/src/release/powerpc) that will let you use the OF boot menu to select FreeBSD if you are dual-booting. We really need to make installation work better. Can we include a port of Apple's HFS implementation in base? I know APSL1 was impossible, but are there any thoughts on APSL2 now? Having HFS support should also be valuable on x86 with more people dual-booting FreeBSD/OS X now. I suppose that writing a simple write-only HFS implementation should not be too hard, either. Maybe this could be hooked into gpart bootcode? -Nathan From marcotrillo at gmail.com Tue Oct 7 15:33:07 2008 From: marcotrillo at gmail.com (Marco Trillo) Date: Tue Oct 7 15:33:13 2008 Subject: bootloader installation In-Reply-To: <1223393073.15248.151.camel@horst-tla> References: <1223393073.15248.151.camel@horst-tla> Message-ID: Hi, On Tue, Oct 7, 2008 at 5:24 PM, Horst G?nther Burkhardt III wrote: > I have installed FreeBSD, thanks to Richard for suggesting Finnix for > partitioning, it did the job brilliantly. > > ... Where the hell is the bootloader? I can't find it anywhere, and thus > don't know what to do with the 64MB HFS+ i set aside for it. :( Assuming you installed FreeBSD from CD, the loader is in the CD, in the directory. Simply copy the file in that directory to the root of your HFS partition (using Mac OS) and then you can boot from that partition. For example if the HFS partition is number X and your FreeBSD root partition is number Y, the following command will do it: 0> boot hd:X,loader hd:Y Hope that helps, Marco. From marcotrillo at gmail.com Tue Oct 7 15:37:20 2008 From: marcotrillo at gmail.com (Marco Trillo) Date: Tue Oct 7 15:37:26 2008 Subject: bootloader installation In-Reply-To: <48EB821B.80503@freebsd.org> References: <1223393073.15248.151.camel@horst-tla> <48EB821B.80503@freebsd.org> Message-ID: Hi, On Tue, Oct 7, 2008 at 5:36 PM, Nathan Whitehorn wrote: > I suppose that writing a simple write-only HFS implementation should not be > too hard, either. Maybe this could be hooked into gpart bootcode? The "hfsutils" package is very useful to format HFS partitions and copy the loader to it from within FreeBSD itself, without needing Mac OS. Regards, Marco. From horst at sxemacs.org Tue Oct 7 15:43:37 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Tue Oct 7 15:43:45 2008 Subject: bootloader installation In-Reply-To: References: <1223393073.15248.151.camel@horst-tla> Message-ID: <1223394238.15248.161.camel@horst-tla> On Tue, 2008-10-07 at 17:33 +0200, Marco Trillo wrote: > Hi, > Assuming you installed FreeBSD from CD, the loader is in the CD, in > the directory. > > Simply copy the file in that directory to the root of your > HFS partition (using Mac OS) and then you can boot from that > partition. For example if the HFS partition is number X and your > FreeBSD root partition is number Y, the following command will do it: > > 0> boot hd:X,loader hd:Y > > Hope that helps, > Marco. Most helpful. There's also a parameter in OF that allows autoboot, correct? (I don't intend to go back from FreeBSD if you get my drift.) Also, as I don't any longer have OS X there, can I boot into the freebsd that is on the hard disk, using the cd, from OF somehow, just until I install the loader? Another question, does the loader have to reside in the same place as the /boot directory? or can I leave /boot on the / UFS2 partition andmerely use the loader? On Tue, 2008-10-07 at 10:36 -0500, Nathan Whitehorn wrote: > We really need to make installation work better. Can we include a > port of Apple's HFS implementation in base? I know APSL1 was > impossible, but are there any thoughts on APSL2 now? Having HFS > support should also be valuable on x86 with more people dual-booting > FreeBSD/OS X now. > > I suppose that writing a simple write-only HFS implementation should > not be too hard, either. Maybe this could be hooked into gpart > bootcode? > -Nathan Hear hear about the installer. I think especially now that OS X is moving to the x86 platform, a lot of old ppc boxes will be left without maintained software - and to be honest despite some exceptional cases like the Finnix CD and most of Debian, hardware support in Linux is just shocking on many PPC macs. Hence FreeBSD having a fully viable PPC port will (from my standpoint anyway) be an asset to the community. If there's anything useful I can do (i can't code unfortunately) I'll be happy to try, by the way. I'm already thinking of writing some documentation on how to get FreeBSD installed painlessly, so that others don't go through the hell I've had here. Thanks. :) --Horst. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081007/f78a80c4/attachment.pgp From marcotrillo at gmail.com Tue Oct 7 15:51:49 2008 From: marcotrillo at gmail.com (Marco Trillo) Date: Tue Oct 7 15:51:55 2008 Subject: bootloader installation In-Reply-To: <1223394238.15248.161.camel@horst-tla> References: <1223393073.15248.151.camel@horst-tla> <1223394238.15248.161.camel@horst-tla> Message-ID: Hi, On Tue, Oct 7, 2008 at 5:43 PM, Horst G?nther Burkhardt III wrote: > There's also a parameter in OF that allows autoboot, > correct? (I don't intend to go back from FreeBSD if you get my drift.) Yes. You can configure OF to autoboot FreeBSD using the loader, but I think if you use the "boot.tbxi" file Nathan mentioned, OF will boot it automatically if it doesn't find Mac OS. > > Also, as I don't any longer have OS X there, can I boot into the freebsd > that is on the hard disk, using the cd, from OF somehow, just until I > install the loader? Sure. Just use "boot cd:0,\boot\loader hd:Y" where Y is the FreeBSD partition number. You can also install the loader from FreeBSD using "hfsutils". > > Another question, does the loader have to reside in the same place as > the /boot directory? or can I leave /boot on the / UFS2 partition > andmerely use the loader? > The loader resides in a HFS partition, which is not the /boot partition. You do not need a /boot partition, you can leave /boot in the / partition. Hope that helps, Marco. From grehan at freebsd.org Tue Oct 7 16:05:06 2008 From: grehan at freebsd.org (Peter Grehan) Date: Tue Oct 7 16:05:13 2008 Subject: bootloader installation Message-ID: <20081008020039.EJX00000@dommail.onthenet.com.au> Hi Nathan, >We really need to make installation work better. Yep. >Can we include a port of Apple's HFS implementation >in base? I know APSL1 was impossible, but are there any >thoughts on APSL2 now? Having HFS support should also be >valuable on x86 with more people dual-booting >FreeBSD/OS X now. ZFS shows how to incorporate a piece of s/w that may even have an unfriendly license. The ppc loader can do a boot-time module load so the same trick can be applied. I would imagine a port of Apple HFS code to be a "big job" with differences in the o/s maybe harder to mask out than with ZFS/Solaris since the OSX and FreeBSD have significant incompatible overlap. >I suppose that writing a simple write-only HFS >implementation should not be too hard, either. >Maybe this could be hooked into gpart bootcode? As Marco mentioned, there is hfsutils. Also, NetBSD had a Google SoC project to implement HFS, that at least produced some usable code: http://netbsd-soc.sourceforge.net/projects/hfs/ I don't know that the status is in NetBSD proper. later, Peter. From horst at sxemacs.org Tue Oct 7 16:11:11 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Tue Oct 7 16:11:18 2008 Subject: bootloader installation In-Reply-To: References: <1223393073.15248.151.camel@horst-tla> <1223394238.15248.161.camel@horst-tla> Message-ID: <1223395892.15248.167.camel@horst-tla> On Tue, 2008-10-07 at 17:51 +0200, Marco Trillo wrote: > Hi, > > On Tue, Oct 7, 2008 at 5:43 PM, Horst G?nther Burkhardt III > wrote: > > Also, as I don't any longer have OS X there, can I boot into the freebsd > > that is on the hard disk, using the cd, from OF somehow, just until I > > install the loader? > > Sure. Just use "boot cd:0,\boot\loader hd:Y" where Y is the FreeBSD > partition number. > > You can also install the loader from FreeBSD using "hfsutils". This is a problem. doing this from the OF console (btw, it's partition number 11 on disk 0 (disk0s11)) results in the following: DISK-LABEL: LOAD (noninterposed) not supportedload-size=0 adler32=1 LOAD-SIZE is too small ok 0 > ... I've tried all numbers after hd up to 16. Should I be specifying the device to read too? (the physical medium?) If so, how? (disk0s10 : HFS+ 64MB) txbi? (disk0s11 : UFS2 40GB) / (disk1s10 : SWAP 4GB) (disk1s11 : UFS2 56GB) /usr > > > > Another question, does the loader have to reside in the same place as > > the /boot directory? or can I leave /boot on the / UFS2 partition > > andmerely use the loader? > > > > The loader resides in a HFS partition, which is not the /boot > partition. You do not need a /boot partition, you can leave /boot in > the / partition. > > Hope that helps, > Marco. Thanks, most helpful. Unfortunately as said above it didn't quite go off without a hitch. :( -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081007/20bf87a5/attachment.pgp From marcotrillo at gmail.com Tue Oct 7 16:15:26 2008 From: marcotrillo at gmail.com (Marco Trillo) Date: Tue Oct 7 16:15:32 2008 Subject: bootloader installation In-Reply-To: <1223395892.15248.167.camel@horst-tla> References: <1223393073.15248.151.camel@horst-tla> <1223394238.15248.161.camel@horst-tla> <1223395892.15248.167.camel@horst-tla> Message-ID: Hi, On Tue, Oct 7, 2008 at 6:11 PM, Horst G?nther Burkhardt III wrote: > On Tue, 2008-10-07 at 17:51 +0200, Marco Trillo wrote: >> On Tue, Oct 7, 2008 at 5:43 PM, Horst G?nther Burkhardt III >> wrote: >> > Also, as I don't any longer have OS X there, can I boot into the freebsd >> > that is on the hard disk, using the cd, from OF somehow, just until I >> > install the loader? >> >> Sure. Just use "boot cd:0,\boot\loader hd:Y" where Y is the FreeBSD >> partition number. >> >> You can also install the loader from FreeBSD using "hfsutils". > > This is a problem. doing this from the OF console (btw, it's partition > number 11 on disk 0 (disk0s11)) results in the following: > > DISK-LABEL: LOAD (noninterposed) not supportedload-size=0 adler32=1 > > LOAD-SIZE is too small > ok > 0 > > Try "boot cd:,\boot\loader hd:11", without the "0". Hope that helps, Marco. From horst at sxemacs.org Tue Oct 7 16:23:18 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Tue Oct 7 16:23:24 2008 Subject: bootloader installation In-Reply-To: References: <1223393073.15248.151.camel@horst-tla> <1223394238.15248.161.camel@horst-tla> <1223395892.15248.167.camel@horst-tla> Message-ID: <1223396619.15248.170.camel@horst-tla> On Tue, 2008-10-07 at 18:15 +0200, Marco Trillo wrote: > Hi, > Try "boot cd:,\boot\loader hd:11", without the "0". > > Hope that helps, > Marco. That's one hurdle gone, thanks. Next thing is "can't load ?kernel?." And then i'm stuck in the bootloader with no way to figure out what's needed. (isn't the kernel called "GENERIC" and not "kernel"?) Thanks for all the help so far :) -- Horst. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081007/eef56fd8/attachment.pgp From marcotrillo at gmail.com Tue Oct 7 16:31:31 2008 From: marcotrillo at gmail.com (Marco Trillo) Date: Tue Oct 7 16:31:38 2008 Subject: bootloader installation In-Reply-To: <1223396619.15248.170.camel@horst-tla> References: <1223393073.15248.151.camel@horst-tla> <1223394238.15248.161.camel@horst-tla> <1223395892.15248.167.camel@horst-tla> <1223396619.15248.170.camel@horst-tla> Message-ID: Hi, On Tue, Oct 7, 2008 at 6:23 PM, Horst G?nther Burkhardt III wrote: > On Tue, 2008-10-07 at 18:15 +0200, Marco Trillo wrote: >> Hi, >> Try "boot cd:,\boot\loader hd:11", without the "0". >> >> Hope that helps, >> Marco. > > That's one hurdle gone, thanks. Next thing is "can't load ?kernel?." > > And then i'm stuck in the bootloader with no way to figure out what's > needed. (isn't the kernel called "GENERIC" and not "kernel"?) Hmm... since you listed "disk1" and "disk0" before, do you have two hard disks? If so, it is possible that the "hd" OF alias is not picking the correct disk where you installed FreeBSD. What is the output of the "devalias hd" command in OF, and what type of disks are "disk0" and "disk1" (ATA, USB, etc.) ? Regards, Marco. From horst at sxemacs.org Tue Oct 7 17:09:45 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Tue Oct 7 17:09:52 2008 Subject: bootloader installation In-Reply-To: References: <1223393073.15248.151.camel@horst-tla> <1223394238.15248.161.camel@horst-tla> <1223395892.15248.167.camel@horst-tla> <1223396619.15248.170.camel@horst-tla> Message-ID: <1223399407.15248.175.camel@horst-tla> On Tue, 2008-10-07 at 18:31 +0200, Marco Trillo wrote: > Hi, > > Hmm... since you listed "disk1" and "disk0" before, do you have two > hard disks? If so, it is possible that the "hd" OF alias is not > picking the correct disk where you installed FreeBSD. Yes, I have two hard disks. the 'hd' alias looks right, but I'm not familiar enough with OF to tell. 0 > devalias hd /pci@f2000000/@d/mac-io@7/ata-4@1f000/disk@0 ok 0 > > What is the output of the "devalias hd" command in OF, and what type > of disks are "disk0" and "disk1" (ATA, USB, etc.) ? Both disks are UDMA100, on the ATA bus. Internal, naturally. > Regards, > Marco. Is there any chance we could speak in realtime, such as on the ppc chatroom on freenode? (if you're on freenode, i'm PeanutHorst) I ask merely because it may be ... easier. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081007/f3a224f6/attachment.pgp From marcotrillo at gmail.com Tue Oct 7 17:25:54 2008 From: marcotrillo at gmail.com (Marco Trillo) Date: Tue Oct 7 17:26:01 2008 Subject: bootloader installation In-Reply-To: <1223399407.15248.175.camel@horst-tla> References: <1223393073.15248.151.camel@horst-tla> <1223394238.15248.161.camel@horst-tla> <1223395892.15248.167.camel@horst-tla> <1223396619.15248.170.camel@horst-tla> <1223399407.15248.175.camel@horst-tla> Message-ID: Hi, On Tue, Oct 7, 2008 at 7:10 PM, Horst G?nther Burkhardt III wrote: > On Tue, 2008-10-07 at 18:31 +0200, Marco Trillo wrote: >> Hi, >> >> Hmm... since you listed "disk1" and "disk0" before, do you have two >> hard disks? If so, it is possible that the "hd" OF alias is not >> picking the correct disk where you installed FreeBSD. > > Yes, I have two hard disks. the 'hd' alias looks right, but I'm not > familiar enough with OF to tell. > > 0 > devalias hd > /pci@f2000000/@d/mac-io@7/ata-4@1f000/disk@0 ok > 0 > > >> What is the output of the "devalias hd" command in OF, and what type >> of disks are "disk0" and "disk1" (ATA, USB, etc.) ? > > Both disks are UDMA100, on the ATA bus. Internal, naturally. OK. Then try with the aliases "ultra0" and "ultra1" (or maybe "ultra2") for the first and second hard disk drives, for example: 0> boot cd:,\boot\loader ultra1:11 If the above aliases do not work, you can also specify the full path. For example, for the second hard drive: 0> boot cd:\boot\loader /pci@f2000000/@d/mac-io@7/ata-4@1f000/disk@1:11 (use "disk@Z" for the Z hard disk on that particular ATA bus). Hope that's helpful, Marco. From horst at sxemacs.org Tue Oct 7 17:28:12 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Tue Oct 7 17:28:17 2008 Subject: bootloader installation In-Reply-To: <48EB9A89.80609@ShaneWare.Biz> References: <1223393073.15248.151.camel@horst-tla> <1223394238.15248.161.camel@horst-tla> <1223395892.15248.167.camel@horst-tla> <48EB9A89.80609@ShaneWare.Biz> Message-ID: <1223400513.15248.179.camel@horst-tla> On Wed, 2008-10-08 at 03:51 +1030, Shane Ambler wrote: > What machine is this on, an old beige G3? > > Is your problem the 8GB limit? Try having the kernel in a partition that > is completely inside the first 8GB. GOD NO. It's a ppc7400. Graphite Power Mac G4 400MHz ADC/GigE model. Using hd0:11 as the target allows the bootloader to Do Something (tm) but I have found the next glitch: 0 > boot cd:,\boot\loader hd0:11, load-size=39748 adler32=bb45cad1 Loading ELF CLAIM failed ok 0 > ^^ What the fsck?! -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081007/5341d5e2/attachment.pgp From nwhitehorn at freebsd.org Tue Oct 7 17:30:35 2008 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Tue Oct 7 17:30:41 2008 Subject: bootloader installation In-Reply-To: <1223400513.15248.179.camel@horst-tla> References: <1223393073.15248.151.camel@horst-tla> <1223394238.15248.161.camel@horst-tla> <1223395892.15248.167.camel@horst-tla> <48EB9A89.80609@ShaneWare.Biz> <1223400513.15248.179.camel@horst-tla> Message-ID: <48EB9CAF.9080401@freebsd.org> Horst G?nther Burkhardt III wrote: > On Wed, 2008-10-08 at 03:51 +1030, Shane Ambler wrote: > >> What machine is this on, an old beige G3? >> >> Is your problem the 8GB limit? Try having the kernel in a partition that >> is completely inside the first 8GB. >> > > GOD NO. > > It's a ppc7400. Graphite Power Mac G4 400MHz ADC/GigE model. > > Using hd0:11 as the target allows the bootloader to Do Something (tm) > but I have found the next glitch: > > 0 > boot cd:,\boot\loader hd0:11, load-size=39748 adler32=bb45cad1 > > Loading ELF > > > CLAIM failed > ok > 0 > > Well, this is why we need a better system (thanks for your persistence). I'm assuming you tried several commands, and then that one worked? OF sometimes needs you to reboot after a failed boot (reset-all, or hit the power button). If you don't, it gets itself into a bad state, and gives this message. -Nathan From FreeBSD at ShaneWare.Biz Tue Oct 7 17:36:31 2008 From: FreeBSD at ShaneWare.Biz (Shane Ambler) Date: Tue Oct 7 17:36:38 2008 Subject: bootloader installation In-Reply-To: <1223395892.15248.167.camel@horst-tla> References: <1223393073.15248.151.camel@horst-tla> <1223394238.15248.161.camel@horst-tla> <1223395892.15248.167.camel@horst-tla> Message-ID: <48EB9A89.80609@ShaneWare.Biz> Horst G?nther Burkhardt III wrote: > (disk0s10 : HFS+ 64MB) txbi? > (disk0s11 : UFS2 40GB) / > (disk1s10 : SWAP 4GB) > (disk1s11 : UFS2 56GB) /usr What machine is this on, an old beige G3? Is your problem the 8GB limit? Try having the kernel in a partition that is completely inside the first 8GB. -- Shane Ambler FreeBSD (at) ShaneWare (dot) Biz http://ShaneWare.Biz From horst at sxemacs.org Tue Oct 7 17:38:26 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Tue Oct 7 17:38:32 2008 Subject: bootloader installation In-Reply-To: <48EB9CAF.9080401@freebsd.org> References: <1223393073.15248.151.camel@horst-tla> <1223394238.15248.161.camel@horst-tla> <1223395892.15248.167.camel@horst-tla> <48EB9A89.80609@ShaneWare.Biz> <1223400513.15248.179.camel@horst-tla> <48EB9CAF.9080401@freebsd.org> Message-ID: <1223401128.15248.184.camel@horst-tla> On Tue, 2008-10-07 at 12:30 -0500, Nathan Whitehorn wrote: > Well, this is why we need a better system (thanks for your persistence). > I'm assuming you tried several commands, and then that one worked? OF > sometimes needs you to reboot after a failed boot (reset-all, or hit the > power button). If you don't, it gets itself into a bad state, and gives > this message. > -Nathan I'll be damned if I let a few glitches keep between me and my new shiny BSD box. Also, any help I can provide to you is the least I can do for you guys making and peddling such an excellent OS. Anyhow, after that, and using the line that works, we're back to the FreeBSD bootstrap loader. All goes well and then the line : can't load ?kernel? ... and then it drops me into the equivalent of a GrUB shell with the prompt: OK _ I'm really not understanding this. -- Horst. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081007/f6f07b78/attachment.pgp From marcotrillo at gmail.com Tue Oct 7 17:45:02 2008 From: marcotrillo at gmail.com (Marco Trillo) Date: Tue Oct 7 17:45:08 2008 Subject: bootloader installation In-Reply-To: <1223401128.15248.184.camel@horst-tla> References: <1223393073.15248.151.camel@horst-tla> <1223394238.15248.161.camel@horst-tla> <1223395892.15248.167.camel@horst-tla> <48EB9A89.80609@ShaneWare.Biz> <1223400513.15248.179.camel@horst-tla> <48EB9CAF.9080401@freebsd.org> <1223401128.15248.184.camel@horst-tla> Message-ID: Hi, On Tue, Oct 7, 2008 at 7:38 PM, Horst G?nther Burkhardt III wrote: > I'll be damned if I let a few glitches keep between me and my new shiny > BSD box. > > Also, any help I can provide to you is the least I can do for you guys > making and peddling such an excellent OS. > > Anyhow, after that, and using the line that works, we're back to the > FreeBSD bootstrap loader. > > All goes well and then the line : > > can't load ?kernel? That's because the "loading ELF" message is from the OF trying to load the loader, not from the loader trying to load the kernel. Can you try booting with the "ultra0" and "ultra1" aliases which I mentioned in my previous mail, to select one or the other hard disk? Do a "reset-all" if a boot attempt failed to avoid the "CLAIM failed" messages. Thanks, Marco. From horst at sxemacs.org Tue Oct 7 18:02:07 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Tue Oct 7 18:02:13 2008 Subject: bootloader installation In-Reply-To: References: <1223393073.15248.151.camel@horst-tla> <1223394238.15248.161.camel@horst-tla> <1223395892.15248.167.camel@horst-tla> <48EB9A89.80609@ShaneWare.Biz> <1223400513.15248.179.camel@horst-tla> <48EB9CAF.9080401@freebsd.org> <1223401128.15248.184.camel@horst-tla> Message-ID: <1223402549.15248.189.camel@horst-tla> On Tue, 2008-10-07 at 19:45 +0200, Marco Trillo wrote: > Hi, > > On Tue, Oct 7, 2008 at 7:38 PM, Horst G?nther Burkhardt III > wrote: > > All goes well and then the line : > > > > can't load ?kernel? > > That's because the "loading ELF" message is from the OF trying to load > the loader, not from the loader trying to load the kernel. > > Can you try booting with the "ultra0" and "ultra1" aliases which I > mentioned in my previous mail, to select one or the other hard disk? > Do a "reset-all" if a boot attempt failed to avoid the "CLAIM failed" > messages. > > Thanks, > Marco. Done and done. Still the same issue. I'm chatting on IRC with Nathan Whitehall about it, and we found a fix. In the bootloader, it is necessary to set currdev=ultra0:10 (in OF parlance this is ultra0:11 which leaves us up a certain creek without a certain implement) ... and then boot. I'm now in my comfy little root ttyv0 ready to get things rolling. Anything more I should be aware of? :) Thanks again for all your help. All of you. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081007/5ac2cc6c/attachment.pgp From andreast-list at fgznet.ch Tue Oct 7 18:50:48 2008 From: andreast-list at fgznet.ch (Andreas Tobler) Date: Tue Oct 7 18:50:56 2008 Subject: Apple Screamer Audio: looking for testers In-Reply-To: References: <48EA1A3D.3010607@fgznet.ch> <48EA7CD4.7040404@fgznet.ch> Message-ID: <48EBAF84.2090001@fgznet.ch> Hi, Marco Trillo wrote: >> Unfortunately, no. Silence. But this might be due to the fact that I do >> something wrong. >> I do not have the aifftools, so I simply tried the cdcontrol and there >> nothing happens, silence. > > The 'cdcontrol' utility uses the CD drive itself to play the CD, it > does not use the system digital audio device -- in fact it does not > need sound support at all. > > To use the system audio device you can use a digital player -- many > are available from the ports collection, for example "mpg321" for MP3 > files. To play CDs you can rip the tracks from the CD with a tool such > as "cdda2wav", "cdparanoia" or others, and then play the digital > files with an audio player . > The "aiffopen" utility is an example of such a player which reads AIFF > files only. Thanks for telling me. I'm not used to play with sound on my machines :) Ok, still building mpg321, was missing qt stuff etc. But nevertheless, I tried to play a bit around and I feel I have some basic issues which do not work. You say cdcontrol does not need sound support at all, do I expect correctly that I should get some sound out of my box then? Well, I do not get anything out of it right now. I followed the handbook's advices and cat'ed a file to /dev/dsp, nothing. Sorry, may I have missed a basic issue then? Do I need to setup something additional? As said, newbie here, only wanted to test. TIA, Andreas From andreast-list at fgznet.ch Tue Oct 7 18:55:57 2008 From: andreast-list at fgznet.ch (Andreas Tobler) Date: Tue Oct 7 18:56:04 2008 Subject: physical memory limit? In-Reply-To: <20081007140359.EJV63125@dommail.onthenet.com.au> References: <20081007140359.EJV63125@dommail.onthenet.com.au> Message-ID: <48EBB0BA.70403@fgznet.ch> Hi Peter, Peter Grehan wrote: >> I remember back in 05 we had a similar issue when I tried >> 'buildworld' on a G4 alu book. Then you suggested to me >> to reduce hw.physmem to 512MB. > > Indeed, and I'm certain those problems were fixed in r1.115 > of mmu_oea.c where the secondary PTEG hash was corrected. Ok, then I trust you :) >> I'll reduce/replace the memory and see how it behaves. > > OK, let us know how it goes. First step passed, I reduced to one 512MB DIMM and a full buildworld with parallel qt build passed. I'll try overnight with the other DIMM to exclude single DIMM failures. But still, I have some more possibilities then, slot1/2 is defect, DIMM 1 does not like co'op with DIMM 2, ECC vs. non ECC (one is marked with ECC support, the other isn't). Will take some hours to find out. Thanks, Andreas From andreast-list at fgznet.ch Tue Oct 7 19:52:46 2008 From: andreast-list at fgznet.ch (Andreas Tobler) Date: Tue Oct 7 19:52:53 2008 Subject: Apple Screamer Audio: looking for testers In-Reply-To: <48EBAF84.2090001@fgznet.ch> References: <48EA1A3D.3010607@fgznet.ch> <48EA7CD4.7040404@fgznet.ch> <48EBAF84.2090001@fgznet.ch> Message-ID: <48EBBE0B.8040009@fgznet.ch> Hi again, Andreas Tobler wrote: > Thanks for telling me. I'm not used to play with sound on my machines :) > > Ok, still building mpg321, was missing qt stuff etc. > > But nevertheless, I tried to play a bit around and I feel I have some > basic issues which do not work. > You say cdcontrol does not need sound support at all, do I expect > correctly that I should get some sound out of my box then? > Well, I do not get anything out of it right now. I followed the > handbook's advices and cat'ed a file to /dev/dsp, nothing. Just fyi, I discovered that I have three plugs to plugin headphones, two on the front side and one at the right side where all other plugs are located. (enet, usb, etc.) As said it's an imac. If I plug my headphones in on the right side and cat a 'file' to /dev/dsp I get some noise. I do not get noise on speaker nor on the other plugs. Still waiting for mpg321 for finishing... Does this ring something? TIA, Andreas From brueffer at FreeBSD.org Tue Oct 7 20:13:11 2008 From: brueffer at FreeBSD.org (Christian Brueffer) Date: Tue Oct 7 20:13:18 2008 Subject: bootloader installation In-Reply-To: <48EB821B.80503@freebsd.org> References: <1223393073.15248.151.camel@horst-tla> <48EB821B.80503@freebsd.org> Message-ID: <20081007194308.GA1268@haakonia.hitnet.RWTH-Aachen.DE> On Tue, Oct 07, 2008 at 10:36:59AM -0500, Nathan Whitehorn wrote: > Horst G?nther Burkhardt III wrote: > >I have installed FreeBSD, thanks to Richard for suggesting Finnix for > >partitioning, it did the job brilliantly. > > > >... Where the hell is the bootloader? I can't find it anywhere, and thus > >don't know what to do with the 64MB HFS+ i set aside for it. :( > > > >Any help would be appreciated. Once again. > > > >My apologies for being horridly noobish here. > > -- Horst. > > It is /boot/loader. There is a boot.tbxi that you can install too (and > find in /usr/src/release/powerpc) that will let you use the OF boot menu > to select FreeBSD if you are dual-booting. > > We really need to make installation work better. Can we include a port > of Apple's HFS implementation in base? I know APSL1 was impossible, but > are there any thoughts on APSL2 now? Having HFS support should also be > valuable on x86 with more people dual-booting FreeBSD/OS X now. > > I suppose that writing a simple write-only HFS implementation should not > be too hard, either. Maybe this could be hooked into gpart bootcode? > -Nathan > _______________________________________________ Take a look at http://people.freebsd.org/~yar for an old hfs port from the 5.x days. Unfortunately it never made it into the base system, maybe someone here would like to pick it up? - Christian -- Christian Brueffer chris@unixpages.org brueffer@FreeBSD.org GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081007/4e3f1d02/attachment.pgp From marcotrillo at gmail.com Tue Oct 7 20:47:39 2008 From: marcotrillo at gmail.com (Marco Trillo) Date: Tue Oct 7 20:47:46 2008 Subject: Apple Screamer Audio: looking for testers In-Reply-To: <48EBAF84.2090001@fgznet.ch> References: <48EA1A3D.3010607@fgznet.ch> <48EA7CD4.7040404@fgznet.ch> <48EBAF84.2090001@fgznet.ch> Message-ID: Hi, On Tue, Oct 7, 2008 at 8:50 PM, Andreas Tobler wrote: >>> Unfortunately, no. Silence. But this might be due to the fact that I do >>> something wrong. >>> I do not have the aifftools, so I simply tried the cdcontrol and there >>> nothing happens, silence. >> >> The 'cdcontrol' utility uses the CD drive itself to play the CD, it >> does not use the system digital audio device -- in fact it does not >> need sound support at all. >> >> To use the system audio device you can use a digital player -- many >> are available from the ports collection, for example "mpg321" for MP3 >> files. To play CDs you can rip the tracks from the CD with a tool such >> as "cdda2wav", "cdparanoia" or others, and then play the digital >> files with an audio player . >> The "aiffopen" utility is an example of such a player which reads AIFF >> files only. > > Thanks for telling me. I'm not used to play with sound on my machines :) Thank you for testing it and for your patience ... > Ok, still building mpg321, was missing qt stuff etc. Hmm... I find odd that mpg321 depends on qt stuff... :-( . > But nevertheless, I tried to play a bit around and I feel I have some basic > issues which do not work. > You say cdcontrol does not need sound support at all, do I expect correctly > that I should get some sound out of my box then? Yes, the CD analog output is connected to the sound device and can be mixed with the normal output -- this also applies to the modem for example. The current driver does not make this mixing configurable yet. However I think you get better results by playing the CD in digital mode using the system's device. Mac OS X for example does this. > Well, I do not get anything out of it right now. I followed the handbook's advices and > cat'ed a file to /dev/dsp, nothing. > Just fyi, I discovered that I have three plugs to plugin headphones, two on the front > side and one at the right side where all other plugs are located. (enet, usb, etc.) > As said it's an imac. > If I plug my headphones in on the right side and cat a 'file' to /dev/dsp I get some > noise. I do not get noise on speaker nor on the other plugs. The port on the right side is a line-out jack for use with an amplifier. Do you get any "Enabled outputs: ___" messages on the console when you plug and unplug the headphones on the left and right front ports? Thanks, Marco. From nwhitehorn at freebsd.org Tue Oct 7 20:56:55 2008 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Tue Oct 7 20:57:01 2008 Subject: bootloader installation In-Reply-To: <20081007194308.GA1268@haakonia.hitnet.RWTH-Aachen.DE> References: <1223393073.15248.151.camel@horst-tla> <48EB821B.80503@freebsd.org> <20081007194308.GA1268@haakonia.hitnet.RWTH-Aachen.DE> Message-ID: <48EBCD0A.9000807@freebsd.org> Christian Brueffer wrote: >> >> We really need to make installation work better. Can we include a port >> of Apple's HFS implementation in base? I know APSL1 was impossible, but >> are there any thoughts on APSL2 now? Having HFS support should also be >> valuable on x86 with more people dual-booting FreeBSD/OS X now. >> >> I suppose that writing a simple write-only HFS implementation should not >> be too hard, either. Maybe this could be hooked into gpart bootcode? >> -Nathan >> _______________________________________________ >> > > Take a look at http://people.freebsd.org/~yar for an old hfs port from > the 5.x days. Unfortunately it never made it into the base system, > maybe someone here would like to pick it up? > I used that on 5.3. It worked great. But the HFS code, the license, and the VFS layer have all changed a lot since then. I think it would be best to restart it from scratch. I asked about the license because the APSL was why it never made it into the tree in the first place. -Nathan From andreast-list at fgznet.ch Tue Oct 7 21:04:16 2008 From: andreast-list at fgznet.ch (Andreas Tobler) Date: Tue Oct 7 21:04:22 2008 Subject: Apple Screamer Audio: looking for testers In-Reply-To: References: <48EA1A3D.3010607@fgznet.ch> <48EA7CD4.7040404@fgznet.ch> <48EBAF84.2090001@fgznet.ch> Message-ID: <48EBCECC.4020802@fgznet.ch> Hiya, Marco Trillo wrote: > Thank you for testing it and for your patience ... Never ending until I reach the goal :) >> Ok, still building mpg321, was missing qt stuff etc. > > Hmm... I find odd that mpg321 depends on qt stuff... :-( . Hm, seems so. np so far, but having finished this build it will not get some success so far. My expectation. >> But nevertheless, I tried to play a bit around and I feel I have some basic >> issues which do not work. >> You say cdcontrol does not need sound support at all, do I expect correctly >> that I should get some sound out of my box then? > > Yes, the CD analog output is connected to the sound device and can be > mixed with the normal output -- this also applies to the modem for > example. The current driver does not make this mixing configurable > yet. > However I think you get better results by playing the CD in digital > mode using the system's device. Mac OS X for example does this. system's device? Which one? >> Well, I do not get anything out of it right now. I followed the handbook's advices and >> cat'ed a file to /dev/dsp, nothing. >> Just fyi, I discovered that I have three plugs to plugin headphones, two on the front >> side and one at the right side where all other plugs are located. (enet, usb, etc.) >> As said it's an imac. >> If I plug my headphones in on the right side and cat a 'file' to /dev/dsp I get some >> noise. I do not get noise on speaker nor on the other plugs. > > The port on the right side is a line-out jack for use with an amplifier. > > Do you get any "Enabled outputs: ___" messages on the console when you > plug and unplug the headphones on the left and right front ports? I see on all ports the activity I do, means, I see when I plugin/out a jack, on all three. Enabled outputs: Headphones/Speaker in the order I plug unplug the piece. If I cat something to /dev/dsp I even see the aoa_chan_setblocksize msg's on stdout. Thanks to your patience, Andreas From marcotrillo at gmail.com Tue Oct 7 22:15:14 2008 From: marcotrillo at gmail.com (Marco Trillo) Date: Tue Oct 7 22:16:15 2008 Subject: Apple Screamer Audio: looking for testers In-Reply-To: <48EBCECC.4020802@fgznet.ch> References: <48EA1A3D.3010607@fgznet.ch> <48EA7CD4.7040404@fgznet.ch> <48EBAF84.2090001@fgznet.ch> <48EBCECC.4020802@fgznet.ch> Message-ID: Hi, On Tue, Oct 7, 2008 at 11:04 PM, Andreas Tobler wrote: >>> Ok, still building mpg321, was missing qt stuff etc. >> >> Hmm... I find odd that mpg321 depends on qt stuff... :-( . > > Hm, seems so. np so far, but having finished this build it will not get some > success so far. My expectation. Hmm... if you have finished the mpg321 build, can you try applying the following patch for aoa.c ? --- aoa.c.orig 2008-10-07 23:33:14.000000000 +0200 +++ aoa.c 2008-10-07 23:52:25.000000000 +0200 @@ -661,10 +661,20 @@ DPRINTF(("\n")); - if (d->device_id == 5) { + if (d->device_id == 5 || d->device_id == 11) { DPRINTF(("Enabling programmable output.\n")); x |= SCREAMER_PROG_OUTPUT0; - } + } + + if (d->device_id == 8 || d->device_id == 11) { + + /* iMac DV. */ + DPRINTF(("iMac DV.\n")); + + x &= ~SCREAMER_MUTE_SPEAKER; + if (mask & (1 << 0)) + x |= SCREAMER_PROG_OUTPUT1; /* enable speaker. */ + } Screamer_write_locked(d, SCREAMER_CODEC_ADDR1, x); d->output_mask = mask; I hope that it improves things with the iMac DV. These "programmable output" bits are another thing that is very machine-specific :-( . > >>> But nevertheless, I tried to play a bit around and I feel I have some >>> basic >>> issues which do not work. >>> You say cdcontrol does not need sound support at all, do I expect >>> correctly >>> that I should get some sound out of my box then? >> >> Yes, the CD analog output is connected to the sound device and can be >> mixed with the normal output -- this also applies to the modem for >> example. The current driver does not make this mixing configurable >> yet. >> However I think you get better results by playing the CD in digital >> mode using the system's device. Mac OS X for example does this. > > system's device? Which one? The computer's built-in audio device, in this case the "Screamer" chip, in contrast with the chip on the CD unit. > >>> Well, I do not get anything out of it right now. I followed the >>> handbook's advices and >>> cat'ed a file to /dev/dsp, nothing. >>> Just fyi, I discovered that I have three plugs to plugin headphones, two >>> on the front >>> side and one at the right side where all other plugs are located. (enet, >>> usb, etc.) >>> As said it's an imac. >>> If I plug my headphones in on the right side and cat a 'file' to /dev/dsp >>> I get some >>> noise. I do not get noise on speaker nor on the other plugs. >> >> The port on the right side is a line-out jack for use with an amplifier. >> >> Do you get any "Enabled outputs: ___" messages on the console when you >> plug and unplug the headphones on the left and right front ports? > > I see on all ports the activity I do, means, I see when I plugin/out a jack, > on all three. > Enabled outputs: Headphones/Speaker in the order I plug unplug the piece. Well, at least the port detection is working. Once again thanks for your patience, Marco. From andreast-list at fgznet.ch Wed Oct 8 10:04:21 2008 From: andreast-list at fgznet.ch (Andreas Tobler) Date: Wed Oct 8 10:04:28 2008 Subject: Apple Screamer Audio: looking for testers In-Reply-To: References: <48EA1A3D.3010607@fgznet.ch> <48EA7CD4.7040404@fgznet.ch> <48EBAF84.2090001@fgznet.ch> <48EBCECC.4020802@fgznet.ch> Message-ID: <48EC85A1.90005@fgznet.ch> Hi, Marco Trillo wrote: > Hi, > > On Tue, Oct 7, 2008 at 11:04 PM, Andreas Tobler wrote: >>>> Ok, still building mpg321, was missing qt stuff etc. >>> Hmm... I find odd that mpg321 depends on qt stuff... :-( . >> Hm, seems so. np so far, but having finished this build it will not get some >> success so far. My expectation. This mpg321 was for nothing! I changed to mpg123, easier and enough for my purpose. > Hmm... if you have finished the mpg321 build, can you try applying the > following patch for aoa.c ? [snip] Done, and now I'm happy :) !!! > I hope that it improves things with the iMac DV. These "programmable > output" bits are another thing that is very machine-specific :-( . Yeah. >> system's device? Which one? > > The computer's built-in audio device, in this case the "Screamer" > chip, in contrast with the chip on the CD unit. Ok. >> Enabled outputs: Headphones/Speaker in the order I plug unplug the piece. > > Well, at least the port detection is working. And now even playing mp3 is working. The only thing I did not find out is how to play cd's, but that's not that important to me. > Once again thanks for your patience, Thank you for your work! Regards, Andreas From marcotrillo at gmail.com Wed Oct 8 13:17:29 2008 From: marcotrillo at gmail.com (Marco Trillo) Date: Wed Oct 8 13:17:35 2008 Subject: Apple Screamer Audio: looking for testers In-Reply-To: <48EC85A1.90005@fgznet.ch> References: <48EA1A3D.3010607@fgznet.ch> <48EA7CD4.7040404@fgznet.ch> <48EBAF84.2090001@fgznet.ch> <48EBCECC.4020802@fgznet.ch> <48EC85A1.90005@fgznet.ch> Message-ID: Hi, On Wed, Oct 8, 2008 at 12:04 PM, Andreas Tobler wrote: >> On Tue, Oct 7, 2008 at 11:04 PM, Andreas Tobler >> wrote: >>>>> >>>>> Ok, still building mpg321, was missing qt stuff etc. >>>> >>>> Hmm... I find odd that mpg321 depends on qt stuff... :-( . >>> >>> Hm, seems so. np so far, but having finished this build it will not get >>> some >>> success so far. My expectation. > > This mpg321 was for nothing! I changed to mpg123, easier and enough for my > purpose. I'm sorry you compiled all of that for nothing, "mpg321" was a bad example in that respect :-( > >> Hmm... if you have finished the mpg321 build, can you try applying the >> following patch for aoa.c ? > > [snip] > > Done, and now I'm happy :) !!! Very nice! :-) Thanks a lot for testing it, so the final version will work out of the box for (hopefully) all iMac DVs! [...] >>> Enabled outputs: Headphones/Speaker in the order I plug unplug the piece. >> >> Well, at least the port detection is working. > > And now even playing mp3 is working. > The only thing I did not find out is how to play cd's, but that's not that > important to me. You can use a tool such as "cdda2wav" (distributed as part of "cdrtools"), which has the ability to play CDs in 'live' but in digital mode; in addition, of course, it can rip the tracks to files in the hard disk... Thanks ! Marco. From drosih at rpi.edu Wed Oct 8 18:49:16 2008 From: drosih at rpi.edu (Garance A Drosihn) Date: Wed Oct 8 18:49:23 2008 Subject: bootloader installation In-Reply-To: <48EB821B.80503@freebsd.org> References: <1223393073.15248.151.camel@horst-tla> <48EB821B.80503@freebsd.org> Message-ID: [Hmm. I could have sworn I posted this yesterday, but I don't see it anywhere. Apologies if this is a duplicate] At 10:36 AM -0500 10/7/08, Nathan Whitehorn wrote: > >We really need to make installation work better. Can we include a >port of Apple's HFS implementation in base? I know APSL1 was >impossible, but are there any thoughts on APSL2 now? Having HFS >support should also be valuable on x86 with more people dual-booting >FreeBSD/OS X now. It seems to me that we could get away without any implementation of HFS. All we need is a sample HFS partition, with a large area on it reserved as a fake HFS file. Then have something which knows how to write the boot loader to that area. Note that this doesn't have to be a full implementation of HFS, just something that knows where the first byte of the reserved area is, and knows how to write to the raw disk. Make the reserved area two or three times the current size of the boot loader, or have two or three reserved areas (each being a separate fake HFS file). The reason for extra areas is so you could keep three different versions of the bootloader available. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu From andreast-list at fgznet.ch Wed Oct 8 19:23:35 2008 From: andreast-list at fgznet.ch (Andreas Tobler) Date: Wed Oct 8 19:23:41 2008 Subject: physical memory limit? In-Reply-To: <48EBB0BA.70403@fgznet.ch> References: <20081007140359.EJV63125@dommail.onthenet.com.au> <48EBB0BA.70403@fgznet.ch> Message-ID: <48ED08B2.2080700@fgznet.ch> Hi Peter, Andreas Tobler wrote: > Peter Grehan wrote: > >>> I remember back in 05 we had a similar issue when I tried >>> 'buildworld' on a G4 alu book. Then you suggested to me >>> to reduce hw.physmem to 512MB. >> >> Indeed, and I'm certain those problems were fixed in r1.115 >> of mmu_oea.c where the secondary PTEG hash was corrected. > > Ok, then I trust you :) Hm, I just read the commit log: --- Remove bogus increment of re-hashed PTEG index. This snuck in with r1.12 of pmap.c, and is potentially the cause of hangs reported on machines with a small amount of memory. On machines with sufficient RAM, and without a lot of processes running, this situation would probably never occur. --- Irritating issue is the part with 'hangs reported on machines with a small amount of memory'. I do not have small amount of ram, neither did I have hangs. I had 11 at that time. Now I have 11 again, but maybe due to other issues. Well on OS-X the machine does not complain. Even memtest doen't complain during the one hour period I let it run. Also, it might be that this needs a looong run of memtest to uncover something. Anyway. >>> I'll reduce/replace the memory and see how it behaves. >> >> OK, let us know how it goes. > > First step passed, I reduced to one 512MB DIMM and a full buildworld > with parallel qt build passed. > I'll try overnight with the other DIMM to exclude single DIMM failures. > But still, I have some more possibilities then, slot1/2 is defect, DIMM > 1 does not like co'op with DIMM 2, ECC vs. non ECC (one is marked with > ECC support, the other isn't). > Will take some hours to find out. Continued and found that both DIMM's seem to work in the first bank. Running a buildworld with a DIMM in the second bank failed for both, ECC/non ECC. So it seems it might be a problem with my HW. :( I even bought a new, non ECC DIMM and I seem to have the same pattern. Right now I try with 768MB (512MB/256MB ECC). Let you know about findings. Regards, Andreas From andreast-list at fgznet.ch Wed Oct 8 19:41:25 2008 From: andreast-list at fgznet.ch (Andreas Tobler) Date: Wed Oct 8 19:41:32 2008 Subject: Apple Screamer Audio: looking for testers In-Reply-To: References: <48EA1A3D.3010607@fgznet.ch> <48EA7CD4.7040404@fgznet.ch> <48EBAF84.2090001@fgznet.ch> <48EBCECC.4020802@fgznet.ch> <48EC85A1.90005@fgznet.ch> Message-ID: <48ED0CE2.1060006@fgznet.ch> Hi, Marco Trillo wrote: > I'm sorry you compiled all of that for nothing, "mpg321" was a bad > example in that respect :-( No worry. It's not the only machine I'm sitting in front of ;) > Very nice! :-) Thanks a lot for testing it, so the final version > will work out of the box for (hopefully) all iMac DVs! Hopefully yes. As I see from the cvs commits the dbdma part is already in, right? The aoa.c on your page is not yet updated with the fix you proposed me to test, is that coming soon work? Also, I'm just curious, how do you proceed to get this into sys/powerpc/powermac? > [...] >>>> Enabled outputs: Headphones/Speaker in the order I plug unplug the piece. >>> Well, at least the port detection is working. >> And now even playing mp3 is working. >> The only thing I did not find out is how to play cd's, but that's not that >> important to me. > > You can use a tool such as "cdda2wav" (distributed as part of > "cdrtools"), which has the ability to play CDs in 'live' but in > digital mode; in addition, of course, it can rip the tracks to files > in the hard disk... cdda2wav only seems to work with scsi drives? I ripped my cd's on OS-X to get a test mp3. > Thanks ! Thank you Marco! Regards, Andreas From ncoleman at internode.on.net Thu Oct 9 01:28:33 2008 From: ncoleman at internode.on.net (Nick Coleman) Date: Thu Oct 9 01:28:40 2008 Subject: Console ScrollBack on G4 Message-ID: <48ED5ABC.4040605@internode.on.net> I've just installed 7.0 on an old G4 iMac I was given. It was quite an experience as I've never used a Mac or FreeBSD before, so I had to learn about two new environments at the same time. Talk about the blind leading the blind :). (Many thanks to Peter Grehan's notes on the PPC install, couldn't have done it without them.) Anyway, I'm compiling a bunch of stuff on ports right now. I take it there are no binaries for Xorg? My question is: how do you scroll back the console buffer (sysconsole) with a Mac keyboard, since there isn't a Pause key. Many thanks, Nick From ncoleman at internode.on.net Thu Oct 9 03:01:42 2008 From: ncoleman at internode.on.net (Nick Coleman) Date: Thu Oct 9 03:01:47 2008 Subject: Extreme difficulty with partitioning on mac powerpc g4 [long] Message-ID: <48ED741B.3000203@internode.on.net> > Good evening. > > I'm having some significant trouble using the install.iso for ppc. This > trouble being (with both 7.0-RELEASE and 7.1-BETA) that the installer > insists on doing its partitioning with fdisk. I have used linux fdisk to > make the partition tables up, and failing this attempted some semblance > of partitioning with Mac OS X Disk Utility (an idea taken from OpenBSD > install docs for ppc). I also attempted to use GParted, and none of > these attempts at partitioning are being picked up. FWIW, I'm brand new to FreeBSD and Mac, so none of this is gospel, just what worked for me. It took me about 4 or 5 attempts before I got it to work. This is for 7.0 by the way. I ended up spending quite a few days reading various sites to get it to work, but successfully in the end. I found the netBSD instructions for the PPC to be quite helpful, and Peter Grehan's instructions too. I will go into a fair bit of detail for those reading this later, might save a few days of research. This is what I did: From what I understand, you need to use mac-fdisk (Debian, Mac OS X; I think it might even just be a frontend to parted) or parted. I used parted for a PPC build, in a Ubuntu live CD session. Ubuntu's latest releases don't support PPC, but their 6.x build is still maintained and does support it. I downloaded the live CD (700MB just to run parted!). Perhaps you could do it easier with a smaller build of a live CD, but I have a fast connection and by that point (tearing out hair!) couldn't be bothered faffing around to find something else. (BTW, does Gparted support ppc? I didn't think it did, so I didn't explore it any further other than reading their website intro.) I booted the Ubuntu live CD, opened a terminal session, ran parted, and created all the partitions. You need to create all the partitions now, so plan ahead on how many partitions and their sizing. I believe you can't create just one partition hoping to use sysinstall in FreeBSD later to subdivide it into the various partitions, you need to create them all now. Note the partition (slice) numbers and sizes for later. I then booted into the FreeBSD install CD. In my experience, you must use the boot iso and not the disk1 iso. For some reason, sysinstall was never successful in installing the packages if I had booted from disk1. In sysinstall, I [C]reated the partitions by using the existing ones I had already set up. I set it to rewrite file systems and swap. Do this even if you have a half-finished install already in the partitions. I was never successful at completing a previously failed install, so gave up and rewrote the file systems, thereby losing everything I had done in previous sessions. After I tried this method, it worked. Previously it failed every time at the point of installing packages (write error -1, couldn't write to ...etc) after downloading them. I installed packages with FTP to a local mirror. Several times it failed with "couldn't find packages/INDEX". Timeout bug? Again, if this happens, bite the bullet and start again, rewriting the file system in the partitions. I was never successful at restarting a failed install. Ha, I probably downloaded the entire distro about 5 times, lucky my ISP quota was unusually empty this month. So that's it. I ended up doing a minimum install because I got sick of downloading all those packages just for the install to fail. I ended up with a minimum just so I could get to a shell after rebooting. On a side note, by this stage, Open Firmware and I have quite a close relationship. :). Open Firmware is my bro'. > > It all comes back to me hitting "custom install" as I always do, and the > damned partitioner, and me trying to do _anything_ results in a SIG11 > (Segmentation Violation i believe). > > a) Is there a known workaround? > ` - b) If there is, why are there no docs anywhere on the internet? > ` - c) If (following either assistance or dumb luck) I get it > working, would a "walkthrough" be welcomed? (see lack of docs) > |- d) If no known workaround, are there any suggestions from the ppc > devs and users on this ML? > To be honest, I was surprised at how little info there is out on the net. I found only 3 (!) sites with good practical info. I wonder if it is just that there are very few people actually installing FreeBSD for the first time on a G4. Perhaps just you and me... :) -- Nick From horst at sxemacs.org Thu Oct 9 05:12:05 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Thu Oct 9 05:12:12 2008 Subject: Extreme difficulty with partitioning on mac powerpc g4 [long] In-Reply-To: <48ED741B.3000203@internode.on.net> References: <48ED741B.3000203@internode.on.net> Message-ID: <1223529153.15248.200.camel@horst-tla> On Thu, 2008-10-09 at 11:01 +0800, Nick Coleman wrote: > FWIW, I'm brand new to FreeBSD and Mac, so none of this is gospel, just > what worked for me. It took me about 4 or 5 attempts before I got it to > work. This is for 7.0 by the way. Welcome to FreeBSD, and welcome to Macintosh. > I ended up spending quite a few days reading various sites to get it to > work, but successfully in the end. I found the netBSD instructions for > the PPC to be quite helpful, and Peter Grehan's instructions too. That's odd, I found them to be a tad skeleton. > I will go into a fair bit of detail for those reading this later, might > save a few days of research. This is what I did: > > From what I understand, you need to use mac-fdisk (Debian, Mac OS X; I > think it might even just be a frontend to parted) or parted. I used > parted for a PPC build, in a Ubuntu live CD session. Ubuntu's latest > releases don't support PPC, but their 6.x build is still maintained and > does support it. I downloaded the live CD (700MB just to run parted!). > Perhaps you could do it easier with a smaller build of a live CD, but > I have a fast connection and by that point (tearing out hair!) couldn't > be bothered faffing around to find something else. (BTW, does Gparted > support ppc? I didn't think it did, so I didn't explore it any further > other than reading their website intro.) I eventually used Finnix for this at the suggestion of Richard DeLaurell. > So that's it. I ended up doing a minimum install because I got sick of > downloading all those packages just for the install to fail. I ended up > with a minimum just so I could get to a shell after rebooting. > > On a side note, by this stage, Open Firmware and I have quite a close > relationship. :). Open Firmware is my bro'. > To be honest, I was surprised at how little info there is out on the > net. I found only 3 (!) sites with good practical info. I wonder if > it is just that there are very few people actually installing FreeBSD > for the first time on a G4. Perhaps just you and me... :) You and Me Against The World comes to mind. Would you be interested in improving the PowerPC port page on the FreeBSD wiki with this information, with me ? :) It would definitely help other newcomers. -- Horst. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081009/34431975/attachment.pgp From marcotrillo at gmail.com Thu Oct 9 08:04:04 2008 From: marcotrillo at gmail.com (Marco Trillo) Date: Thu Oct 9 08:04:10 2008 Subject: Extreme difficulty with partitioning on mac powerpc g4 [long] In-Reply-To: <48ED741B.3000203@internode.on.net> References: <48ED741B.3000203@internode.on.net> Message-ID: Hi, On Thu, Oct 9, 2008 at 5:01 AM, Nick Coleman wrote: > From what I understand, you need to use mac-fdisk (Debian, Mac OS X; I think > it might even just be a frontend to parted) or parted. Actually the tool is called "pdisk", "mac-fdisk" is just a Debian rename for it (I don't know why). > PPC build, in a Ubuntu live CD session. Ubuntu's latest releases don't > support PPC, but their 6.x build is still maintained and does support it. > I downloaded the live CD (700MB just to run parted!). Hmm... an easier option is booting from the Mac OS X installation media. It contains a "Disk Utility" application that can be opened from the menu and can be used to create all the partitions -- and the tool is entirely graphical. It requires that the partitions be initially formated in either HFS (the Mac OS filesystem) or UFS; for the FreeBSD partition(s) either format can be used as they will be reformated later by sysinst using FreeBSD's own filesystems. For older Macs which come with Mac OS 9 media, a similar tool called "Drive setup" can be used. > [...] > On a side note, by this stage, Open Firmware and I have quite a close > relationship. :). Open Firmware is my bro'. :-) . Regards, Marco. From marcotrillo at gmail.com Thu Oct 9 08:18:00 2008 From: marcotrillo at gmail.com (Marco Trillo) Date: Thu Oct 9 08:18:07 2008 Subject: Apple Screamer Audio: looking for testers In-Reply-To: <48ED0CE2.1060006@fgznet.ch> References: <48EA7CD4.7040404@fgznet.ch> <48EBAF84.2090001@fgznet.ch> <48EBCECC.4020802@fgznet.ch> <48EC85A1.90005@fgznet.ch> <48ED0CE2.1060006@fgznet.ch> Message-ID: Hi, On Wed, Oct 8, 2008 at 9:41 PM, Andreas Tobler wrote: >> Very nice! :-) Thanks a lot for testing it, so the final version >> will work out of the box for (hopefully) all iMac DVs! > > Hopefully yes. As I see from the cvs commits the dbdma part is already in, > right? Yes, an improved version of the extensions for the dbdma API is already in thanks to Nathan. > The aoa.c on your page is not yet updated with the fix you proposed me to > test, is that coming soon work? > Also, I'm just curious, how do you proceed to get this into > sys/powerpc/powermac? Actually I have split the "aoa.c" file in different files for the different audio controllers, intended to go into the "sys/dev/sound/macio" directory, which is where all the other sound drivers for other platforms reside, instead of "sys/powerpc/powermac". The new, splitted version of the driver will of course include the fix :-) . >>> And now even playing mp3 is working. >>> The only thing I did not find out is how to play cd's, but that's not >>> that >>> important to me. >> >> You can use a tool such as "cdda2wav" (distributed as part of >> "cdrtools"), which has the ability to play CDs in 'live' but in >> digital mode; in addition, of course, it can rip the tracks to files >> in the hard disk... > > cdda2wav only seems to work with scsi drives? I ripped my cd's on OS-X to > get a test mp3. It also works with ATAPI drives if the kernel is compiled with ATAPI/CAM support -- just like the "cdrecord" utility. Regards, Marco. From marcotrillo at gmail.com Thu Oct 9 09:40:56 2008 From: marcotrillo at gmail.com (Marco Trillo) Date: Thu Oct 9 09:41:06 2008 Subject: Apple Tumbler and Snapper audio: looking for testers Message-ID: Hi all, I've implemented audio output for the "Tumbler" and "Snapper" Apple I2S-based audio devices. The machine I have is a eMac G4, but these devices are found on a lot of G3 and G4 systems. In particular, all iMac G4's, all eMacs, all iBook G4's and most of PowerBook G4's have either "Tumbler" or "Snapper". The following is a more detailed list. Anyone interested in testing it? Below is more information on how to obtain it. Thanks a lot! iMacs: - "PowerMac4,2" iMac G4 (2002) [tumbler] - "PowerMac4,5" iMac G4 17'' [tumbler] - "PowerMac6,1" iMac G4 17'' (2003) [tumbler?] - "PowerMac6,3" iMac G4 20'' (Nov 2003) [snapper?] eMacs: - "PowerMac4,4" eMac G4 (2002, 2003) [snapper] - "PowerMac6,4" eMac G4 (2004, 2005) [snapper] iBooks: - "PowerBook4,1" iBook G3 (May 2001) [tumbler] - "PowerBook4,2" iBook G3 [tumbler?] - "PowerBook4,3" iBook G3 (2002, 2003) [tumbler] - "PowerBook6,3" iBook G4 (2003) [snapper] - "PowerBook6,5" iBook G4 (2004) [snapper] - "PowerBook6,7" iBook G4 (2005) [snapper] PowerMacs: - "PowerMac3,4" PowerMac G4 "Digital audio" [tumbler] - "PowerMac3,5" PowerMac G4 "QuickSilver" [tumbler] - "PowerMac3,6" PowerMac G4 "Mirrored drive doors" [snapper] PowerBooks: - "PowerBook3,3" PowerBook G4 "Gigabit ethernet" [tumbler] - "PowerBook3,4" PowerBook G4 "DVI" [snapper] - "PowerBook3,5" PowerBook G4 [snapper] - "PowerBook5,1" PowerBook G4 [snapper] - "PowerBook5,2" PowerBook G4 [snapper] - "PowerBook5,3" PowerBook G4 [snapper] - "PowerBook5,4" PowerBook G4 [snapper] - "PowerBook5,5" PowerBook G4 [snapper] - "PowerBook5,6" PowerBook G4 [snapper] - "PowerBook5,7" PowerBook G4 [snapper?] - "PowerBook6,1" PowerBook G4 [snapper] - "PowerBook6,2" PowerBook G4 [snapper] - "PowerBook6,4" PowerBook G4 [snapper] - "PowerBook6,7" PowerBook G4 [snapper] - "PowerBook6,8" PowerBook G4 [snapper] The driver can be obtained in the following tarball: It includes the "sound/" and "powermac/" subdirectories to include in the kernel, something like this: $ cp -R sound/macio /usr/src/sys/dev/sound/macio $ cp powermac/* /usr/src/sys/powerpc/powermac/ In addition, the "patches/" subdirectory contains the following patches: - macio.patch to apply in /usr/src/sys/powerpc/powermac - files.patch to apply in /usr/src/sys/conf - generic.patch to apply in /usr/src/sys/powerpc/conf, for the GENERIC kernel. If you don't use the GENERIC kernel you can also enable it manually by including the following lines: device sound device davbus device i2s And of course, some dmesg output from my machine. It's very verbose due to debug being enabled: pcm0: mem 0x10000-0x10fff,0x8000-0x80ff,0x8100-0x81ff irq 30,1,2,31,3,4 on macio0 interrupting at irq 1 pcm0: [ITHREAD] GPIO : addr 0x6f GPIO : addr 0x70 GPIO : addr 0x75 interrupting at irq 61 pcm0: [ITHREAD] GPIO : addr 0x67 enabled outputs: SPEAKER resetting codec [...] kiic0: mem 0x18000-0x18fff irq 26 on macio0 [...] pcm0: codec: at address 6Ah on kiic0 $ cat /dev/sndstat FreeBSD Audio Driver (newpcm: 32bit 2007061600/powerpc) Installed devices: pcm0: at i2s [GIANT] (1p:1v/0r:0v channels default) Thanks and regards! Marco From marcotrillo at gmail.com Thu Oct 9 09:53:57 2008 From: marcotrillo at gmail.com (Marco Trillo) Date: Thu Oct 9 09:54:03 2008 Subject: Apple Tumbler and Snapper audio: looking for testers In-Reply-To: References: Message-ID: Hi, On Thu, Oct 9, 2008 at 11:40 AM, Marco Trillo wrote: > In particular, all iMac G4's, all eMacs, all iBook G4's and most of > PowerBook G4's have either "Tumbler" or "Snapper". ... and some PowerMacs, as detailed in the list. Oops, I forgot to mention that the volume defaults to 0 and that it can be changed with the mixer(8) utility. For example: $ mixer vol 93 Setting the mixer vol from XX:XX to 93:93. The output port is also changed automatically when something is plugged or unplugged to / from the headphone and line-out jacks. Thanks, Marco. From horst at sxemacs.org Thu Oct 9 14:21:27 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Thu Oct 9 14:21:34 2008 Subject: The only box that can't mount its own install media. Message-ID: <1223562121.15248.213.camel@horst-tla> I realise that this email may sound like a bad joke. Believe me it is not. I would like to know i can boot into BSD without needing a CD to boot from, before I start building my world. To this end I attempted to set up the bootloader as instructed earlier (boot.tbxi) by simply copying it to the root of the HFS partition. It would appear however that my computer will have none of that. So, next thing to try is copying /boot/loader from the CD to /loader on the HFS partition, as i was also instructed by another ML user. ... The FreeBSD cd won't mount. It just says : invalid argument when I try to specify a mountpoint, as such: # mount /dev/acd0 /mnt/cdrom Please forgive me if I'm Doing It Wrong. if the command # mount /dev/acd0 is used, the box simply does nothing, but on the otehr hand doesn't report an error. quaint, no? Also, to whoever shouted out earlier about improved UDMA support in the kernel, can I have links to the relevant downloads? I'm going to rebuild this thing anyhow so I may as well use the niceties :) Cheers. -- Horst. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081009/ea5d5d91/attachment.pgp From nwhitehorn at freebsd.org Thu Oct 9 15:01:14 2008 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Thu Oct 9 15:01:45 2008 Subject: The only box that can't mount its own install media. In-Reply-To: <1223562121.15248.213.camel@horst-tla> References: <1223562121.15248.213.camel@horst-tla> Message-ID: <48EE1DD4.8010906@freebsd.org> Horst G?nther Burkhardt III wrote: > I realise that this email may sound like a bad joke. Believe me it is > not. > > I would like to know i can boot into BSD without needing a CD to boot > from, before I start building my world. > > To this end I attempted to set up the bootloader as instructed earlier > (boot.tbxi) by simply copying it to the root of the HFS partition. It > would appear however that my computer will have none of that. You need both boot.tbxi and loader on the HFS partition. > So, next thing to try is copying /boot/loader from the CD to /loader on > the HFS partition, as i was also instructed by another ML user. > > ... The FreeBSD cd won't mount. It just says : > > invalid argument > > when I try to specify a mountpoint, as such: > > # mount /dev/acd0 /mnt/cdrom This is because the file system is wrong (hence invalid argument). mount defaults to UFS, and the CD is not a UFS file system. You want mount -t cd9660 /dev/acd0 /cdrom. I'd suggest reading the handbook or the mount manpage for this kind of thing, since it is not PowerPC-specific. > if the command > > # mount /dev/acd0 > > is used, the box simply does nothing, but on the otehr hand doesn't > report an error. quaint, no? If the device is listed in /etc/fstab, you want to use the mountpoint instead of the device name. E.g. mount /cdrom. > Also, to whoever shouted out earlier about improved UDMA support in the > kernel, can I have links to the relevant downloads? I'm going to rebuild > this thing anyhow so I may as well use the niceties :) It is in -CURRENT right now, waiting on some residual bugs to be merged into 7-STABLE. -Nathan From horst at sxemacs.org Thu Oct 9 15:19:46 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Thu Oct 9 15:19:53 2008 Subject: The only box that can't mount its own install media. In-Reply-To: <1223562121.15248.213.camel@horst-tla> References: <1223562121.15248.213.camel@horst-tla> Message-ID: <1223565620.15248.218.camel@horst-tla> On Fri, 2008-10-10 at 01:22 +1100, Horst G?nther Burkhardt III wrote: > I realise that this email may sound like a bad joke. Believe me it is > not. > > I would like to know i can boot into BSD without needing a CD to boot > from, before I start building my world. > > To this end I attempted to set up the bootloader as instructed earlier > (boot.tbxi) by simply copying it to the root of the HFS partition. It > would appear however that my computer will have none of that. > > So, next thing to try is copying /boot/loader from the CD to /loader on > the HFS partition, as i was also instructed by another ML user. [...] > Also, to whoever shouted out earlier about improved UDMA support in the > kernel, can I have links to the relevant downloads? I'm going to rebuild > this thing anyhow so I may as well use the niceties :) > > Cheers. > > -- Horst. Disregard that, i suck ... CD spindles. I figured out the mount problem. media's mounted, now I need to figure out how the loader works. Any volunteers to explain what drops where? (i'm using hfsutils, i have no os x anymore) Also, is there any more "elegant" bootloader for PPC that could be used? -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081009/8280ae0c/attachment.pgp From horst at sxemacs.org Thu Oct 9 15:29:31 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Thu Oct 9 15:29:37 2008 Subject: Apologies for failing. In-Reply-To: <1223565620.15248.218.camel@horst-tla> References: <1223562121.15248.213.camel@horst-tla> <1223565620.15248.218.camel@horst-tla> Message-ID: <1223566205.15248.224.camel@horst-tla> Update: I got the loader installed. So far, so hoopy. Now I just need to remember the hackery to auto-boot FreeBSD (something to do with setting the loader parameters in openfirmware) and she'll ride. Next tasks: - Compile better kernel - Set dhclient to run automatically on startup - Get X - Get Xfce - Get SXEmacs - Try and get the AIX/PPC binaries for Netscape Communicator 4 to run ;) (Note: The last point is purely "for the lulz", I don't actually intend to use it as my main browser.) Also, re Nathan Whitehorn: Was there not a way to get the UDMA support before it gets into -STABLE? I recall a patch. At any rate i'm running -BETA so it's not as though I care if a few tiny things are slightly imperfect :P Thanks again for all the help: -- Horst. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081009/8739c805/attachment.pgp From andreast-list at fgznet.ch Thu Oct 9 15:46:48 2008 From: andreast-list at fgznet.ch (Andreas Tobler) Date: Thu Oct 9 15:46:54 2008 Subject: ADB support? In-Reply-To: <48E0DDE6.5030909@freebsd.org> References: <46171.83.233.155.226.1222694615.squirrel@webmail.student.lth.se> <48E0DDE6.5030909@freebsd.org> Message-ID: <48EE2764.6070208@fgznet.ch> Hi Nathan, Nathan Whitehorn wrote: >> I'm wondering how the ADB keyboard support is coming along? >> The last thing I've seen on this list is from July. > > I've been stymied by a lack of hardware. It works great on my PowerMac > G3, but that has a different controller chip (CUDA) than the one > everybody wants support for (PMU, found in laptops). My current work is > here: > > http://people.freebsd.org/~nwhitehorn/adb.diff > > It has a PMU driver, which may just work. Of course, it more likely > won't... Motivated people are welcome to hack it, and I'd appreciate any > reports. To add this support, apply the patch to sys on a recent > -CURRENT, add the following to your kernel config, and recompile: > > device cuda > device pmu > device adb I guess 'device adb' only, is ok, right? Btw, do you have the viareg.h somewhere? I miss it while building the above patch. TIA, Andreas From tinderbox at freebsd.org Thu Oct 9 16:28:24 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Thu Oct 9 16:28:37 2008 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20081009162820.D947173039@freebsd-current.sentex.ca> TB --- 2008-10-09 15:11:01 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-10-09 15:11:01 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-10-09 15:11:01 - cleaning the object tree TB --- 2008-10-09 15:11:34 - cvsupping the source tree TB --- 2008-10-09 15:11:34 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-10-09 15:11:41 - building world (CFLAGS=-O -pipe) TB --- 2008-10-09 15:11:41 - cd /src TB --- 2008-10-09 15:11:41 - /usr/bin/make -B buildworld >>> World build started on Thu Oct 9 15:11:43 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Thu Oct 9 16:20:26 UTC 2008 TB --- 2008-10-09 16:20:26 - generating LINT kernel config TB --- 2008-10-09 16:20:26 - cd /src/sys/powerpc/conf TB --- 2008-10-09 16:20:26 - /usr/bin/make -B LINT TB --- 2008-10-09 16:20:26 - building LINT kernel (COPTFLAGS=) TB --- 2008-10-09 16:20:26 - cd /src TB --- 2008-10-09 16:20:26 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu Oct 9 16:20:26 UTC 2008 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] /src/sys/modules/ata/atapci/chipsets/ataacard/../../../../../dev/ata/chipsets/ata-acard.c:163: warning: nested extern declaration of 'ata_atapi' /src/sys/modules/ata/atapci/chipsets/ataacard/../../../../../dev/ata/chipsets/ata-acard.c: In function 'ata_acard_86X_setmode': /src/sys/modules/ata/atapci/chipsets/ataacard/../../../../../dev/ata/chipsets/ata-acard.c:202: warning: implicit declaration of function 'ata_check_80pin' /src/sys/modules/ata/atapci/chipsets/ataacard/../../../../../dev/ata/chipsets/ata-acard.c:202: warning: nested extern declaration of 'ata_check_80pin' /src/sys/modules/ata/atapci/chipsets/ataacard/../../../../../dev/ata/chipsets/ata-acard.c: At top level: /src/sys/modules/ata/atapci/chipsets/ataacard/../../../../../dev/ata/chipsets/ata-acard.c:285: warning: data definition has no type or storage class /src/sys/modules/ata/atapci/chipsets/ataacard/../../../../../dev/ata/chipsets/ata-acard.c:285: warning: type defaults to 'int' in declaration of 'ATA_DECLARE_DRIVER' /src/sys/modules/ata/atapci/chipsets/ataacard/../../../../../dev/ata/chipsets/ata-acard.c:285: warning: parameter names (without types) in function declaration *** Error code 1 Stop in /src/sys/modules/ata/atapci/chipsets/ataacard. *** Error code 1 Stop in /src/sys/modules/ata/atapci/chipsets. *** Error code 1 Stop in /src/sys/modules/ata/atapci. *** Error code 1 Stop in /src/sys/modules/ata. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-10-09 16:28:20 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-10-09 16:28:20 - ERROR: failed to build lint kernel TB --- 2008-10-09 16:28:20 - tinderbox aborted TB --- 3466.34 user 404.30 system 4639.48 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From andreast-list at fgznet.ch Thu Oct 9 18:53:26 2008 From: andreast-list at fgznet.ch (Andreas Tobler) Date: Thu Oct 9 18:53:34 2008 Subject: Apple Tumbler and Snapper audio: looking for testers In-Reply-To: References: Message-ID: <48EE5322.8030708@fgznet.ch> Hi Marco, Marco Trillo wrote: > I've implemented audio output for the "Tumbler" and "Snapper" Apple > I2S-based audio devices. > > The machine I have is a eMac G4, but these devices are found on a lot > of G3 and G4 systems. > In particular, all iMac G4's, all eMacs, all iBook G4's and most of > PowerBook G4's have either "Tumbler" or "Snapper". > > The following is a more detailed list. Anyone interested in testing > it? Below is more information on how to obtain it. I tested the package on my iMac DV. Thanks! Works fine. The test on my Alu G4 book is outstanding. I wanted to include the adb.diff from Nathan as well. But unfortunately I seem to miss a file, viareg.h for/from his patch. If I get this file soon I can continue building, otherwise I'll build w/o adb support. (Somehow important since I do not like to attach a USB kbd to my G4 Alu Book.) Let you know about the outcome. Thanks again, Andreas imacb# cat /dev/sndstat FreeBSD Audio Driver (newpcm: 32bit 2007061600/powerpc) Installed devices: pcm0: at davbus [GIANT] (1p:1v/0r:0v channels default) pcm0: mem 0x14000-0x14fff,0x8800-0x88ff,0x8900-0x89ff irq 24,9,10 on macio0 interrupting at irq 9 pcm0: [ITHREAD] pcm0: codec: . . . kiic0: mem 0x18000-0x18fff irq 26 on macio0 From nwhitehorn at freebsd.org Thu Oct 9 19:13:46 2008 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Thu Oct 9 19:13:52 2008 Subject: Apple Tumbler and Snapper audio: looking for testers In-Reply-To: <48EE5322.8030708@fgznet.ch> References: <48EE5322.8030708@fgznet.ch> Message-ID: <48EE57DD.8030202@freebsd.org> Andreas Tobler wrote: > Hi Marco, > > Marco Trillo wrote: > >> I've implemented audio output for the "Tumbler" and "Snapper" Apple >> I2S-based audio devices. >> >> The machine I have is a eMac G4, but these devices are found on a lot >> of G3 and G4 systems. >> In particular, all iMac G4's, all eMacs, all iBook G4's and most of >> PowerBook G4's have either "Tumbler" or "Snapper". >> >> The following is a more detailed list. Anyone interested in testing >> it? Below is more information on how to obtain it. > > I tested the package on my iMac DV. Thanks! > > Works fine. > > The test on my Alu G4 book is outstanding. I wanted to include the > adb.diff from Nathan as well. But unfortunately I seem to miss a file, > viareg.h for/from his patch. If I get this file soon I can continue > building, otherwise I'll build w/o adb support. (Somehow important > since I do not like to attach a USB kbd to my G4 Alu Book.) Sorry about that: http://people.freebsd.org/~nwhitehorn/viareg.h -Nathan From grehan at freebsd.org Thu Oct 9 19:52:30 2008 From: grehan at freebsd.org (Peter Grehan) Date: Thu Oct 9 19:52:37 2008 Subject: The only box that can't mount its own install media. Message-ID: <20081010055147.EJZ19410@dommail.onthenet.com.au> Hi Horst, >I need to figure out how the loader works. Any >volunteers to explain what drops where? (i'm using >hfsutils, i have no os x anymore) You'll want to copy the loader, and also a "tbxi" text file to the root directory of the HFS partition. The contents of the tbxi file can be derived from a couple of places - the FreeBSD release CD uses one: http://svn.freebsd.org/viewvc/base/head/release/powerpc/boot.tbxi?revision=133950&view=markup .. and replace the boot line with the partition that your kernel is on. Then, in OpenFirmware, set auto-boot? to true, boot-device to the disk, partition and file e.g. 0 > setenv boot-device hd:9,\boot.tbxi (after doing a test boot with 'boot hd:9,\boot.tbxi :) 0 > reset-all ... will save the env var and hopefully autoboot into FreeBSD. >Also, is there any more "elegant" bootloader for PPC that >could be used? I'd like to hope that Oliver Fromme's graphical loader work could be ported to the ppc/ofw loader. Here's a screen shot: http://www.secnetix.de/olli/FreeBSD/vloader/screenshot.png later, Peter. From grehan at freebsd.org Thu Oct 9 19:55:16 2008 From: grehan at freebsd.org (Peter Grehan) Date: Thu Oct 9 19:55:23 2008 Subject: Apologies for failing. Message-ID: <20081010055434.EJZ19575@dommail.onthenet.com.au> Hi Horst, >- Get X >- Get Xfce You'll have to build these from source. Best to leave overnight. Configuring the Xorg server is a bit of an adventure, though there are a few NetBSD configs out there to copy from. >- Get SXEmacs I'd love to see that running on PPC :) Last time I looked at Emacs, there was quite a bit of build glue to get it going. Too complicated for my patience at the time. >- Try and get the AIX/PPC binaries for Netscape Communicator 4 to run ;) Firefox doesn't built at the moment: it requires a cut'n'paste of the Net/OpenBSD ppc asm glue in XPCOM. Now, doing an AIX binary emulation for FreeBSD is certainly a large task :) later, Peter. From andreast-list at fgznet.ch Thu Oct 9 21:09:20 2008 From: andreast-list at fgznet.ch (Andreas Tobler) Date: Thu Oct 9 21:09:27 2008 Subject: Apple Tumbler and Snapper audio: looking for testers In-Reply-To: <48EE57DD.8030202@freebsd.org> References: <48EE5322.8030708@fgznet.ch> <48EE57DD.8030202@freebsd.org> Message-ID: <48EE72FC.8010502@fgznet.ch> Hi Nathan, Nathan Whitehorn wrote: >> The test on my Alu G4 book is outstanding. I wanted to include the >> adb.diff from Nathan as well. But unfortunately I seem to miss a file, >> viareg.h for/from his patch. If I get this file soon I can continue >> building, otherwise I'll build w/o adb support. (Somehow important >> since I do not like to attach a USB kbd to my G4 Alu Book.) > Sorry about that: > http://people.freebsd.org/~nwhitehorn/viareg.h Thanks, locking hard while booting after detecting adb mouse (touchpad?) No abd mouse attached. More details later. Bedtime. Thanks, Andreas From tinderbox at freebsd.org Thu Oct 9 22:03:03 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Thu Oct 9 22:03:16 2008 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20081009220300.2CA7A73039@freebsd-current.sentex.ca> TB --- 2008-10-09 20:46:41 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-10-09 20:46:41 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-10-09 20:46:42 - cleaning the object tree TB --- 2008-10-09 20:47:08 - cvsupping the source tree TB --- 2008-10-09 20:47:08 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-10-09 20:47:16 - building world (CFLAGS=-O -pipe) TB --- 2008-10-09 20:47:16 - cd /src TB --- 2008-10-09 20:47:16 - /usr/bin/make -B buildworld >>> World build started on Thu Oct 9 20:47:18 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Thu Oct 9 21:55:04 UTC 2008 TB --- 2008-10-09 21:55:04 - generating LINT kernel config TB --- 2008-10-09 21:55:04 - cd /src/sys/powerpc/conf TB --- 2008-10-09 21:55:04 - /usr/bin/make -B LINT TB --- 2008-10-09 21:55:04 - building LINT kernel (COPTFLAGS=) TB --- 2008-10-09 21:55:04 - cd /src TB --- 2008-10-09 21:55:04 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu Oct 9 21:55:04 UTC 2008 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] /src/sys/modules/ata/atapci/chipsets/ataacard/../../../../../dev/ata/chipsets/ata-acard.c:163: warning: nested extern declaration of 'ata_atapi' /src/sys/modules/ata/atapci/chipsets/ataacard/../../../../../dev/ata/chipsets/ata-acard.c: In function 'ata_acard_86X_setmode': /src/sys/modules/ata/atapci/chipsets/ataacard/../../../../../dev/ata/chipsets/ata-acard.c:202: warning: implicit declaration of function 'ata_check_80pin' /src/sys/modules/ata/atapci/chipsets/ataacard/../../../../../dev/ata/chipsets/ata-acard.c:202: warning: nested extern declaration of 'ata_check_80pin' /src/sys/modules/ata/atapci/chipsets/ataacard/../../../../../dev/ata/chipsets/ata-acard.c: At top level: /src/sys/modules/ata/atapci/chipsets/ataacard/../../../../../dev/ata/chipsets/ata-acard.c:285: warning: data definition has no type or storage class /src/sys/modules/ata/atapci/chipsets/ataacard/../../../../../dev/ata/chipsets/ata-acard.c:285: warning: type defaults to 'int' in declaration of 'ATA_DECLARE_DRIVER' /src/sys/modules/ata/atapci/chipsets/ataacard/../../../../../dev/ata/chipsets/ata-acard.c:285: warning: parameter names (without types) in function declaration *** Error code 1 Stop in /src/sys/modules/ata/atapci/chipsets/ataacard. *** Error code 1 Stop in /src/sys/modules/ata/atapci/chipsets. *** Error code 1 Stop in /src/sys/modules/ata/atapci. *** Error code 1 Stop in /src/sys/modules/ata. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-10-09 22:03:00 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-10-09 22:03:00 - ERROR: failed to build lint kernel TB --- 2008-10-09 22:03:00 - tinderbox aborted TB --- 3465.15 user 403.02 system 4578.05 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From jrh29 at alumni.cwru.edu Thu Oct 9 22:44:53 2008 From: jrh29 at alumni.cwru.edu (Justin Hibbits) Date: Thu Oct 9 22:44:59 2008 Subject: Apple Tumbler and Snapper audio: looking for testers In-Reply-To: References: Message-ID: <20081009220352.GA1138@narn.knownspace> Marco, On Thu, Oct 09, 2008 at 11:40:55AM +0200, Marco Trillo wrote: > Hi all, > > I've implemented audio output for the "Tumbler" and "Snapper" Apple > I2S-based audio devices. > > The machine I have is a eMac G4, but these devices are found on a lot > of G3 and G4 systems. > In particular, all iMac G4's, all eMacs, all iBook G4's and most of > PowerBook G4's have either "Tumbler" or "Snapper". > > The following is a more detailed list. Anyone interested in testing > it? Below is more information on how to obtain it. > > Thanks a lot! > PowerMacs: > - "PowerMac3,4" PowerMac G4 "Digital audio" [tumbler] > - "PowerMac3,5" PowerMac G4 "QuickSilver" [tumbler] > - "PowerMac3,6" PowerMac G4 "Mirrored drive doors" [snapper] > > The driver can be obtained in the following tarball: > > > It includes the "sound/" and "powermac/" subdirectories to include in > the kernel, something like this: > $ cp -R sound/macio /usr/src/sys/dev/sound/macio > $ cp powermac/* /usr/src/sys/powerpc/powermac/ > > In addition, the "patches/" subdirectory contains the following patches: > - macio.patch to apply in /usr/src/sys/powerpc/powermac > - files.patch to apply in /usr/src/sys/conf > - generic.patch to apply in /usr/src/sys/powerpc/conf, for the GENERIC kernel. > > If you don't use the GENERIC kernel you can also enable it manually by > including the following lines: > > device sound > device davbus > device i2s I applied the patch, and got all the same output on my MDD as in your email, but there is no /dev/pcm0. I do have a /dev/sndstat, and /dev/mixer0. The following is the output of /dev/sndstat: FreeBSD Audio Driver (newpcm: 32bit 2007061600/powerpc) Installed devices: pcm0: at i2s [GIANT] (1p:1v/0r:0v channels default) And my dmesg: pcm0: mem 0x10000-0x10fff,0x8000-0x80ff,0x8100-0x81ff irq 30,1,2 on macio0 interrupting at irq 1 pcm0: [ITHREAD] GPIO : addr 0x6f interrupting at irq 61 pcm0: [ITHREAD] GPIO : addr 0x67 GPIO : addr 0x70 interrupting at irq 60 pcm0: [ITHREAD] GPIO : addr 0x66 GPIO : addr 0x75 enabled outputs: SPEAKER resetting codec tumbler_write called without I2C? pcm_getbuffersize returned 65536 aoa_dma_setprd: addr = 13434880, 32 slots aoa_chan_setformat: format = 268435488 aoa_chan_setspeed: speed = 44100 aoa_chan_setformat: format = 268435488 aoa_chan_setblocksize: blocksz = 2048, dma->blksz = 2048 aoa_chan_setspeed: speed = 44100 aoa_chan_setformat: format = 268435488 aoa_chan_setblocksize: blocksz = 2048, dma->blksz = 2048 aoa_chan_setblocksize: blocksz = 2048, dma->blksz = 2048 aoa_chan_setspeed: speed = 44100 aoa_chan_setformat: format = 268435488 aoa_chan_setblocksize: blocksz = 2048, dma->blksz = 2048 kiic0: mem 0x18000-0x18fff irq 26 on macio0 pcm0: codec: at address 6Ah on kiic0 0a: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0b: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0c: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0d: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0e: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0f: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 10: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 13: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 14: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 14: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 15: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 16: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 17: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 18: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 19: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01: 60 43: 02 02: 01 00 00 00 00 00 04: 00 00 00 00 00 00 05: 72 06: 72 07: 10 00 00 00 00 00 00 00 00 08: 10 00 00 00 00 00 00 00 00 21: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 22: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 23: 00 00 00 24: 00 00 00 40: c2 04: 00 5a d5 00 5a d5 Anything else you need to diagnose this? - Justin From jrh29 at alumni.cwru.edu Fri Oct 10 03:06:17 2008 From: jrh29 at alumni.cwru.edu (Justin Hibbits) Date: Fri Oct 10 03:06:28 2008 Subject: Apple Tumbler and Snapper audio: looking for testers In-Reply-To: <20081009220352.GA1138@narn.knownspace> References: <20081009220352.GA1138@narn.knownspace> Message-ID: <20081010030612.GB1138@narn.knownspace> On Thu, Oct 09, 2008 at 06:03:52PM -0400, Justin Hibbits wrote: > I applied the patch, and got all the same output on my MDD as in your email, but > there is no /dev/pcm0. I do have a /dev/sndstat, and /dev/mixer0. The What's really odd is that I don't have any /dev/pcm*. I kldload'd snd_uaudio, which showed in the dmesg output as creating pcm1, but there is no /dev/pcm1 either. Any ideas why I wouldn't have a pcm device show up in /dev, but is created in the kernel? - Justin From nwhitehorn at freebsd.org Fri Oct 10 03:10:25 2008 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Fri Oct 10 03:10:31 2008 Subject: Apple Tumbler and Snapper audio: looking for testers In-Reply-To: <20081010030612.GB1138@narn.knownspace> References: <20081009220352.GA1138@narn.knownspace> <20081010030612.GB1138@narn.knownspace> Message-ID: <48EEC8BB.50802@freebsd.org> Justin Hibbits wrote: > On Thu, Oct 09, 2008 at 06:03:52PM -0400, Justin Hibbits wrote: >> I applied the patch, and got all the same output on my MDD as in your email, but >> there is no /dev/pcm0. I do have a /dev/sndstat, and /dev/mixer0. The > > What's really odd is that I don't have any /dev/pcm*. I kldload'd snd_uaudio, > which showed in the dmesg output as creating pcm1, but there is no /dev/pcm1 > either. Any ideas why I wouldn't have a pcm device show up in /dev, but is > created in the kernel? Sound devices on FreeBSD show up as /dev/audio and /dev/dsp, not /dev/pcm*. It may or may not show up in a directory listing. A good way to test your sound is to cat an au file (like this one: http://playground.sun.com/pub/p1275/misc/ofwsong.au) to /dev/audio. -Nathan From tinderbox at freebsd.org Fri Oct 10 03:32:34 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Fri Oct 10 03:32:46 2008 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20081010033231.0781973039@freebsd-current.sentex.ca> TB --- 2008-10-10 02:19:29 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-10-10 02:19:29 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-10-10 02:19:29 - cleaning the object tree TB --- 2008-10-10 02:19:46 - cvsupping the source tree TB --- 2008-10-10 02:19:46 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-10-10 02:19:53 - building world (CFLAGS=-O -pipe) TB --- 2008-10-10 02:19:53 - cd /src TB --- 2008-10-10 02:19:53 - /usr/bin/make -B buildworld >>> World build started on Fri Oct 10 02:19:56 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Fri Oct 10 03:27:38 UTC 2008 TB --- 2008-10-10 03:27:38 - generating LINT kernel config TB --- 2008-10-10 03:27:38 - cd /src/sys/powerpc/conf TB --- 2008-10-10 03:27:38 - /usr/bin/make -B LINT TB --- 2008-10-10 03:27:38 - building LINT kernel (COPTFLAGS=) TB --- 2008-10-10 03:27:38 - cd /src TB --- 2008-10-10 03:27:38 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Oct 10 03:27:39 UTC 2008 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/dev/usb/ohci_pci.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/dev/usb/sl811hs.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/dev/usb/slhci_pccard.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/dev/usb/uark.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/dev/usb/u3g.c /src/sys/dev/usb/u3g.c: In function 'u3g_attach': /src/sys/dev/usb/u3g.c:169: error: 'struct u3g_softc' has no member named 'sc_intr_number' /src/sys/dev/usb/u3g.c:170: error: 'struct u3g_softc' has no member named 'sc_intr_pipe' *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-10-10 03:32:30 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-10-10 03:32:30 - ERROR: failed to build lint kernel TB --- 2008-10-10 03:32:30 - tinderbox aborted TB --- 3318.81 user 389.25 system 4381.20 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From horst at sxemacs.org Fri Oct 10 05:50:03 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Fri Oct 10 05:50:09 2008 Subject: Apologies for failing. In-Reply-To: <20081010055434.EJZ19575@dommail.onthenet.com.au> References: <20081010055434.EJZ19575@dommail.onthenet.com.au> Message-ID: <1223617839.15248.231.camel@horst-tla> On Fri, 2008-10-10 at 05:54 +1000, Peter Grehan wrote: > Hi Horst, > > >- Get X > >- Get Xfce > > You'll have to build these from source. Best to leave > overnight. Configuring the Xorg server is a bit of an > adventure, though there are a few NetBSD configs out there to > copy from. I've never had trouble with X.Org configurations thankfully. Also I'm starting to wish I had a more powerful PPC box - srsly I should not have to build ViM of all things ;) (i want my modeline back too btw) > >- Get SXEmacs > > I'd love to see that running on PPC :) Last time I looked at > Emacs, there was quite a bit of build glue to get it going. > Too complicated for my patience at the time. I'm your man then. I work with the SXEmacs project. We already boast support for building on PPC/Darwin so given how much has been shared between the two it's not a huge leap to assume it can be made to work on PPC/FreeBSD relatively easily. :) Also, our build system is standard autotooled - aclocal, autoconf, configure, make, make install. It also has a Gentoo ebuild which I wrote (and which the project lead thought was impractical to do, but i proved him wrong haha) so theoretically it could even end up in ports if I figure out how to make a port. > >- Try and get the AIX/PPC binaries for Netscape Communicator > 4 to run ;) > Now, doing an AIX binary emulation for FreeBSD is certainly a > large task :) FreeBSD should already have AIX binary emulation layers ... If not, anywhere else I can get Netscape Communicator in a PPC binary form that will run on FreeBSD? It's important that it's Communicator and not say Mozilla or one of the opensourced forks. > later, > > Peter. Thanks. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081010/137c9442/attachment.pgp From marcotrillo at gmail.com Fri Oct 10 08:23:36 2008 From: marcotrillo at gmail.com (Marco Trillo) Date: Fri Oct 10 08:23:42 2008 Subject: Apple Tumbler and Snapper audio: looking for testers In-Reply-To: <20081009220352.GA1138@narn.knownspace> References: <20081009220352.GA1138@narn.knownspace> Message-ID: Hi, On Fri, Oct 10, 2008 at 12:03 AM, Justin Hibbits wrote: > I applied the patch, and got all the same output on my MDD as in your email, but > there is no /dev/pcm0. I do have a /dev/sndstat, and /dev/mixer0. The > following is the output of /dev/sndstat: Thanks for testing it! As Nathan commented, the pcm drivers "create" various /dev/dsp and /dev/audio device nodes. They are created "on demand" using devfs, so they will not appear when doing a ls in the /dev directory until they are opened for the first time, in this case by an audio player. Thanks, Marco. From jrh29 at alumni.cwru.edu Fri Oct 10 12:48:58 2008 From: jrh29 at alumni.cwru.edu (Justin Hibbits) Date: Fri Oct 10 12:49:05 2008 Subject: Apple Tumbler and Snapper audio: looking for testers In-Reply-To: References: <20081009220352.GA1138@narn.knownspace> Message-ID: <20081010124853.GC1138@narn.knownspace> On Fri, Oct 10, 2008 at 10:23:34AM +0200, Marco Trillo wrote: > Hi, > > On Fri, Oct 10, 2008 at 12:03 AM, Justin Hibbits wrote: > > I applied the patch, and got all the same output on my MDD as in your email, but > > there is no /dev/pcm0. I do have a /dev/sndstat, and /dev/mixer0. The > > following is the output of /dev/sndstat: > > Thanks for testing it! > > As Nathan commented, the pcm drivers "create" various /dev/dsp and > /dev/audio device nodes. They are created "on demand" using devfs, so > they will not appear when doing a ls in the /dev directory until they > are opened for the first time, in this case by an audio player. > > Thanks, > Marco. I had meant /dev/dsp*, not /dev/pcm, was a typo. When did they start getting created on demand? A kernel from roughly 2 months ago created /dev/dsp0 at load time, instead of access time, so I was confused this time around. Running an actual test, with ogg123, worked. I don't have speaker output, but I do have line-out output. I think the speaker output is a different issue, because I don't even get the startup chime through the speaker anymore. Guess long story short, it works well. Now I just need to get my ass in gear and get the altivec code done, then my G4 will be nearly 100% complete. - Justin From grehan at freebsd.org Fri Oct 10 14:00:30 2008 From: grehan at freebsd.org (Peter Grehan) Date: Fri Oct 10 14:00:36 2008 Subject: Apologies for failing. Message-ID: <20081010235944.EKA04750@dommail.onthenet.com.au> Hi Horst, >> >- Get SXEmacs >> >> I'd love to see that running on PPC :) Last time I looked at >> Emacs, there was quite a bit of build glue to get it going. >> Too complicated for my patience at the time. > >I'm your man then. I work with the SXEmacs project. We already boast >support for building on PPC/Darwin so given how much has been shared >between the two it's not a huge leap to assume it can be made to work on >PPC/FreeBSD relatively easily. :) Excellent. >Also, our build system is standard autotooled - aclocal, autoconf, >configure, make, make install. > >It also has a Gentoo ebuild which I wrote (and which the project lead >thought was impractical to do, but i proved him wrong haha) so >theoretically it could even end up in ports if I figure out how to make >a port. There's always the xemacs port to start from. >FreeBSD should already have AIX binary emulation layers ... There's a difference between should and does :) Even NetBSD doesn't have that. >If not, anywhere else I can get Netscape Communicator in a >PPC binary form that will run on FreeBSD? Not possible at this point. If Linux emulation existed, that would be the path to go down. later, Peter. From phk at phk.freebsd.dk Fri Oct 10 16:24:41 2008 From: phk at phk.freebsd.dk (Poul-Henning Kamp) Date: Fri Oct 10 16:24:48 2008 Subject: Apple Tumbler and Snapper audio: looking for testers In-Reply-To: Your message of "Fri, 10 Oct 2008 08:48:53 -0400." <20081010124853.GC1138@narn.knownspace> Message-ID: <71106.1223654343@critter.freebsd.dk> Cultural question: Did apple name their audio stuff after an atomic bomb testseries, or does "Tumbler Snapper" have a older reference that I am not aware off ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From andreast-list at fgznet.ch Fri Oct 10 18:13:48 2008 From: andreast-list at fgznet.ch (Andreas Tobler) Date: Fri Oct 10 18:13:59 2008 Subject: adb feedback Message-ID: <48EF9B58.3050208@fgznet.ch> Hi Nathan, in my first try I wanted to combine too much. Now I applied your patch only and built a kernel on my Aluminium G4 PowerBook. What a feeling to type on the PowerBook's own keyboard!!! Thanks a lot! Oct 10 15:16:50 wolfram kernel: pmu0: mem 0x16000-0x17fff irq 25 on macio0 Oct 10 15:16:50 wolfram kernel: pmu0: [ITHREAD] Oct 10 15:16:50 wolfram kernel: adb0: on pmu0 Oct 10 15:16:50 wolfram kernel: akbd0: at device 2 on adb0 Oct 10 15:16:50 wolfram kernel: kbd1 at akbd0 Oct 10 15:16:50 wolfram kernel: ams0: at device 3 on adb0 Oct 10 15:16:50 wolfram kernel: ams0: 4-button 400-dpi Unknown Pointing Device In my first try I wanted to combine the adb patch plus the work from Marco regarding sound. I need to find out what exactly blocked booting. After ams0: at device 3 on adb0 the machine hanged. Had to reboot hard. Might be a i2c vs. pmu interaction? Don't know yet. I first will find out if the sound patch works on it's own. Thanks a lot for this work! Regards, Andreas From marcotrillo at gmail.com Sat Oct 11 09:18:40 2008 From: marcotrillo at gmail.com (Marco Trillo) Date: Sat Oct 11 09:18:46 2008 Subject: Apple Tumbler and Snapper audio: looking for testers In-Reply-To: <20081010124853.GC1138@narn.knownspace> References: <20081009220352.GA1138@narn.knownspace> <20081010124853.GC1138@narn.knownspace> Message-ID: Hi, On Fri, Oct 10, 2008 at 2:48 PM, Justin Hibbits wrote: > I had meant /dev/dsp*, not /dev/pcm, was a typo. When did they start getting > created on demand? A kernel from roughly 2 months ago created /dev/dsp0 at load > time, instead of access time, so I was confused this time around. >From a quick look at CVS, it seems this was changed in revision 1.103 of sound/pcm/dsp.c (and corresponding revision 1.51 of man/man4/pcm.4). > Running an > actual test, with ogg123, worked. I don't have speaker output, but I do have > line-out output. I think the speaker output is a different issue, because I > don't even get the startup chime through the speaker anymore. Hmm.. the lack of startup chime through the speaker could be due to PRAM volume being set to muted, but this should not affect the driver at all, as it does not read the PRAM volume. Also I think the PRAM volume is global to all outputs, so it would affect the line-out as well. > > Guess long story short, it works well. Now I just need to get my ass in gear > and get the altivec code done, then my G4 will be nearly 100% complete. > Nice... Many thanks for testing it! Regards, Marco From nse at delfi-konsult.com Sat Oct 11 14:56:27 2008 From: nse at delfi-konsult.com (Niels S. Eliasen) Date: Sat Oct 11 14:56:34 2008 Subject: cvsup nogo for powerpc ?? what then ? Message-ID: <44F997E3-8142-4B53-A81D-934105F823E9@delfi-konsult.com> hi guys as cvsup is not intended for powerpc(ahem!) > ===> cvsup-without-gui-16.1h_4 is only for alpha amd64 i386 > sparc64, while you are running powerpc. > what do people use for updating the /usr/src tree ?? kind regards nse "Ach, crivens, what a wee snotter....." Quote from "The Wee Free Men" by Terry Pratchett From marcotrillo at gmail.com Sat Oct 11 14:58:02 2008 From: marcotrillo at gmail.com (Marco Trillo) Date: Sat Oct 11 14:58:08 2008 Subject: cvsup nogo for powerpc ?? what then ? In-Reply-To: <44F997E3-8142-4B53-A81D-934105F823E9@delfi-konsult.com> References: <44F997E3-8142-4B53-A81D-934105F823E9@delfi-konsult.com> Message-ID: Hi, On Sat, Oct 11, 2008 at 4:51 PM, Niels S. Eliasen wrote: > hi guys > > as cvsup is not intended for powerpc(ahem!) > >> ===> cvsup-without-gui-16.1h_4 is only for alpha amd64 i386 sparc64, >> while you are running powerpc. >> > what do people use for updating the /usr/src tree ?? I use the "csup" utility that comes with the base system. It works fine on powerpc. Regards, Marco. From bugmaster at FreeBSD.org Mon Oct 13 11:06:55 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Oct 13 11:08:38 2008 Subject: Current problem reports assigned to freebsd-ppc@FreeBSD.org Message-ID: <200810131106.m9DB6s6J029524@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- a power/121407 ppc [panic] Won't boot up; strange error message. o power/112435 ppc [nexus] [patch] Update nexus children to use ofw_bus f o power/111296 ppc [kernel] [patch] [request] Support IMISS, DLMISS an DS o power/93203 ppc FreeBSD PPC Can't Write to Partitions. 4 problems total. From horst at sxemacs.org Mon Oct 13 12:36:52 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Mon Oct 13 12:36:58 2008 Subject: Apologies for failing. In-Reply-To: <20081010235944.EKA04750@dommail.onthenet.com.au> References: <20081010235944.EKA04750@dommail.onthenet.com.au> Message-ID: <1223901470.10591.2.camel@horst-tla> On Fri, 2008-10-10 at 23:59 +1000, Peter Grehan wrote: > Not possible at this point. If Linux emulation existed, that > would be the path to go down. No no no no no. Linux emulation DOES exist in the freeBSD kernel. What you mean is if somehow it included JIT recompilation of x86 bytecode so that we could run linux-x86 binaries. And yes, I agree that would be awesome, however it would also take a metric fuckton (please pardon my french) of horsepower to pull off in realtime. (Has FreeBSD-ppc had all the binary emulation stuff stripped out of it, or could I theoretically run a linux binary that was built for ppc?) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081013/8cab5c8d/attachment.pgp From grehan at freebsd.org Mon Oct 13 16:27:28 2008 From: grehan at freebsd.org (Peter Grehan) Date: Mon Oct 13 16:27:34 2008 Subject: Apologies for failing. Message-ID: <20081014022645.EKE01815@dommail.onthenet.com.au> >No no no no no. Linux emulation DOES exist in the freeBSD >kernel. I ... know that :) It doesn't exist in the FreeBSD/ppc kernel. >(Has FreeBSD-ppc had all the binary emulation stuff stripped >out of it, or could I theoretically run a linux binary that >was built for ppc?) No. The Linux emu code isn't there, and the ppc-specific layer that converts FreeBSD<->Linux syscalls/signal etc hasn't been written. NB, for anyone interested in looking at that, there is an excellent series of articles by Emmanuel Dreyfus on the NetBSD/ppc Linux emu implementation that pretty much describes the work needed, sans NetBSD/FreeBSD differences: http://www.onlamp.com/pub/a/onlamp/2001/05/10/linux_bsd.html later, Peter. From nwhitehorn at freebsd.org Tue Oct 14 03:59:13 2008 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Tue Oct 14 03:59:44 2008 Subject: The only box that can't mount its own install media. In-Reply-To: <1223565620.15248.218.camel@horst-tla> References: <1223562121.15248.213.camel@horst-tla> <1223565620.15248.218.camel@horst-tla> Message-ID: <48F4190E.1070504@freebsd.org> Horst G?nther Burkhardt III wrote: > > Also, is there any more "elegant" bootloader for PPC that could be > used? I just committed a stage-1 boot loader to -CURRENT that generates a bootable HFS filesystem in the style of our other platforms (e.g. it will read the stage-3 loader from UFS). To use it: - update your source tree - cd /sys/boot/powerpc/boot1.chrp - make && make install - dd if=/boot/boot1.hfs of=/dev/bootstrap_partition OF should then find everything and load it by itself -- FreeBSD should even show up in the firmware boot menu. -Nathan From horst at sxemacs.org Wed Oct 15 10:31:18 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Wed Oct 15 10:31:26 2008 Subject: X hassles - "Device not found" Message-ID: <1224066748.10591.12.camel@horst-tla> Thanks to everyone's help, BSD is now booting autonomously on my mac. The next bit is to get X running. This is where I am thus far failing. First of all: pciconf -l output gives me : hostb0@pci0:0:11:0: class=0x060000 card=0x00000000 chip=0x0020106b rev=0x00 hdr=0x00 vgapci0@pci0:0:16:0: class=0x030000 card=0x00000000 chip=0x50461002 rev=0x00 hdr=0x00 hostb1@pci1:0:11:0: class=0x060000 card=0x00000000 chip=0x001f106b rev=0x00 hdr=0x00 pcib2@pci1:0:13:0: class=0x060400 card=0x00000000 chip=0x00261011 rev=0x05 hdr=0x01 none0@pci1:1:2:0: class=0x010000 card=0x78509004 chip=0x50789004 rev=0x03 hdr=0x00 macio0@pci1:1:7:0: class=0xff0000 card=0x00000000 chip=0x0022106b rev=0x03 hdr=0x00 ohci0@pci1:1:8:0: class=0x0c0310 card=0x00000000 chip=0x0019106b rev=0x00 hdr=0x00 ohci1@pci1:1:9:0: class=0x0c0310 card=0x00000000 chip=0x0019106b rev=0x00 hdr=0x00 fwohci0@pci1:1:10:0: class=0x0c0010 card=0x00000000 chip=0x8020104c rev=0x00 hdr=0x00 hostb2@pci3:0:11:0: class=0x060000 card=0x00000000 chip=0x001e106b rev=0x00 hdr=0x00 gem0@pci3:0:15:0: class=0x020000 card=0x00000000 chip=0x0021106b rev=0x01 hdr=0x00 Next: The issue is that X, on startup, can't find any screens. To this end I attach links to my xorg.conf (which should be correct) and my Xorg.0.log (which should tell the problem). I'm hoping someone else knows what to do better than I do. Hardware: ATi Rage 128 Pro w/ 16MB SDRAM on-card. Apple Studio Display 17" CRT (ADC -power-signal-usb-) Any ideas would be much appreciated. Thanks, -- Horst. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081015/a780c7ce/attachment.pgp From horst at sxemacs.org Wed Oct 15 10:39:01 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Wed Oct 15 10:39:07 2008 Subject: X hassles - "Device not found" In-Reply-To: <1224066748.10591.12.camel@horst-tla> References: <1224066748.10591.12.camel@horst-tla> Message-ID: <1224067213.10591.14.camel@horst-tla> On Wed, 2008-10-15 at 21:32 +1100, Horst G?nther Burkhardt III wrote: > Thanks to everyone's help, BSD is now booting autonomously on my mac. > The next bit is to get X running. This is where I am thus far failing. > > First of all: pciconf -l output gives me : > > > hostb0@pci0:0:11:0: class=0x060000 card=0x00000000 chip=0x0020106b > rev=0x00 hdr=0x00 > vgapci0@pci0:0:16:0: class=0x030000 card=0x00000000 chip=0x50461002 > rev=0x00 hdr=0x00 > hostb1@pci1:0:11:0: class=0x060000 card=0x00000000 chip=0x001f106b > rev=0x00 hdr=0x00 > pcib2@pci1:0:13:0: class=0x060400 card=0x00000000 chip=0x00261011 > rev=0x05 hdr=0x01 > none0@pci1:1:2:0: class=0x010000 card=0x78509004 chip=0x50789004 > rev=0x03 hdr=0x00 > macio0@pci1:1:7:0: class=0xff0000 card=0x00000000 chip=0x0022106b > rev=0x03 hdr=0x00 > ohci0@pci1:1:8:0: class=0x0c0310 card=0x00000000 chip=0x0019106b > rev=0x00 hdr=0x00 > ohci1@pci1:1:9:0: class=0x0c0310 card=0x00000000 chip=0x0019106b > rev=0x00 hdr=0x00 > fwohci0@pci1:1:10:0: class=0x0c0010 card=0x00000000 chip=0x8020104c > rev=0x00 hdr=0x00 > hostb2@pci3:0:11:0: class=0x060000 card=0x00000000 chip=0x001e106b > rev=0x00 hdr=0x00 > gem0@pci3:0:15:0: class=0x020000 card=0x00000000 chip=0x0021106b > rev=0x01 hdr=0x00 > > > > Next: The issue is that X, on startup, can't find any screens. > > To this end I attach links to my xorg.conf (which should be correct) > and > my Xorg.0.log (which should tell the problem). > > I'm hoping someone else knows what to do better than I do. > > > Hardware: ATi Rage 128 Pro w/ 16MB SDRAM on-card. > Apple Studio Display 17" CRT (ADC -power-signal-usb-) > > Any ideas would be much appreciated. > > > Thanks, > -- Horst. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081015/700c8d43/attachment.pgp From horst at sxemacs.org Wed Oct 15 10:41:04 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Wed Oct 15 10:41:10 2008 Subject: [Fwd: X hassles - "Device not found"] Message-ID: <1224067336.10591.17.camel@horst-tla> --- Note: Sorry about the dual consecutive mails, and the lack of links. I'm remedying that now. xorg.conf: http://omploader.org/vdHJm Xorg.0.log: http://omploader.org/vdHJn --- Thanks to everyone's help, BSD is now booting autonomously on my mac. The next bit is to get X running. This is where I am thus far failing. First of all: pciconf -l output gives me : hostb0@pci0:0:11:0: class=0x060000 card=0x00000000 chip=0x0020106b rev=0x00 hdr=0x00 vgapci0@pci0:0:16:0: class=0x030000 card=0x00000000 chip=0x50461002 rev=0x00 hdr=0x00 hostb1@pci1:0:11:0: class=0x060000 card=0x00000000 chip=0x001f106b rev=0x00 hdr=0x00 pcib2@pci1:0:13:0: class=0x060400 card=0x00000000 chip=0x00261011 rev=0x05 hdr=0x01 none0@pci1:1:2:0: class=0x010000 card=0x78509004 chip=0x50789004 rev=0x03 hdr=0x00 macio0@pci1:1:7:0: class=0xff0000 card=0x00000000 chip=0x0022106b rev=0x03 hdr=0x00 ohci0@pci1:1:8:0: class=0x0c0310 card=0x00000000 chip=0x0019106b rev=0x00 hdr=0x00 ohci1@pci1:1:9:0: class=0x0c0310 card=0x00000000 chip=0x0019106b rev=0x00 hdr=0x00 fwohci0@pci1:1:10:0: class=0x0c0010 card=0x00000000 chip=0x8020104c rev=0x00 hdr=0x00 hostb2@pci3:0:11:0: class=0x060000 card=0x00000000 chip=0x001e106b rev=0x00 hdr=0x00 gem0@pci3:0:15:0: class=0x020000 card=0x00000000 chip=0x0021106b rev=0x01 hdr=0x00 Next: The issue is that X, on startup, can't find any screens. To this end I attach links to my xorg.conf (which should be correct) and my Xorg.0.log (which should tell the problem). I'm hoping someone else knows what to do better than I do. Hardware: ATi Rage 128 Pro w/ 16MB SDRAM on-card. Apple Studio Display 17" CRT (ADC -power-signal-usb-) Any ideas would be much appreciated. Thanks, -- Horst. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081015/e2cc6462/attachment.pgp From grehan at freebsd.org Wed Oct 15 12:42:12 2008 From: grehan at freebsd.org (Peter Grehan) Date: Wed Oct 15 12:42:18 2008 Subject: [Fwd: X hassles - "Device not found"] In-Reply-To: <1224067336.10591.17.camel@horst-tla> References: <1224067336.10591.17.camel@horst-tla> Message-ID: <48F5E51B.7020207@freebsd.org> Hi Horst, > (WW) xf86EnableIO 5 > (II) xf86EnableIO: ffffffff > (WW) Can't map IO space! Try a 'sysctl hw.ofwfb.relax_mmap=1' before starting X. The Xorg ATI driver attempts to mmap more memory than the card reports, and the OFW syscons driver thinks this is an error. However, since X hasn't fixed this in years now, it's probably time to remove the check since every user trips up on it :( later, Peter. From horst at sxemacs.org Wed Oct 15 12:58:16 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Wed Oct 15 12:58:22 2008 Subject: X hassles - "Device not found" In-Reply-To: <48F5E51B.7020207@freebsd.org> References: <1224067336.10591.17.camel@horst-tla> <48F5E51B.7020207@freebsd.org> Message-ID: <1224075568.10591.22.camel@horst-tla> On Wed, 2008-10-15 at 06:42 -0600, Peter Grehan wrote: > > (WW) xf86EnableIO 5 > > (II) xf86EnableIO: ffffffff > > (WW) Can't map IO space! > > Try a 'sysctl hw.ofwfb.relax_mmap=1' before starting X. The Xorg ATI > driver attempts to mmap more memory than the card reports, and the OFW > syscons driver thinks this is an error. > > However, since X hasn't fixed this in years now, it's probably time to > remove the check since every user trips up on it :( ... Contrary to popular opinion, X.Org don't make improvements between releases. They just find ways to make things more bloated. A lot like Microsoft, then. ;-) (note the above was a joke) next error : (EE) R128: Failed to load module "fbdevhw" (module does not exist, 0) (EE) Screen(s) found, but none have a usable configuration. ^^ where do I find this mysterious "fbdevhw" ? Also how do I make "1" the default state for hw.ofwfb.relax_mmap ? (so I don't need to do it each restart) ... Thanks :) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081015/85cdc433/attachment.pgp From horst at sxemacs.org Thu Oct 16 15:13:31 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Thu Oct 16 15:13:38 2008 Subject: [Fwd: X hassles - "Device not found"] In-Reply-To: <48F5E51B.7020207@freebsd.org> References: <1224067336.10591.17.camel@horst-tla> <48F5E51B.7020207@freebsd.org> Message-ID: <1224170091.10591.25.camel@horst-tla> On Wed, 2008-10-15 at 06:42 -0600, Peter Grehan wrote: > Hi Horst, > > > (WW) xf86EnableIO 5 > > (II) xf86EnableIO: ffffffff > > (WW) Can't map IO space! > > Try a 'sysctl hw.ofwfb.relax_mmap=1' before starting X. The Xorg ATI > driver attempts to mmap more memory than the card reports, and the OFW > syscons driver thinks this is an error. > > However, since X hasn't fixed this in years now, it's probably time to > remove the check since every user trips up on it :( sysctl trick worked. Next problem is "fbdevhw". Error log: (EE) R128: Failed to load module "fbdevhw" (module does not exist, 0) (EE) Screen(s) found, but none have a usable configuration. Also, is there a way to make 'sysctl hw.ofwfb.relax_mmap=1' happen on startup, or be the default state? (Further question, anyone had luck getting ACPI Suspend or display sleep to work with macs?) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081016/0f8a876f/attachment.pgp From nwhitehorn at freebsd.org Thu Oct 16 15:17:09 2008 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Thu Oct 16 15:17:15 2008 Subject: [Fwd: X hassles - "Device not found"] In-Reply-To: <1224170091.10591.25.camel@horst-tla> References: <1224067336.10591.17.camel@horst-tla> <48F5E51B.7020207@freebsd.org> <1224170091.10591.25.camel@horst-tla> Message-ID: <48F75AD0.2000304@freebsd.org> Horst G?nther Burkhardt III wrote: > On Wed, 2008-10-15 at 06:42 -0600, Peter Grehan wrote: >> Hi Horst, >> >>> (WW) xf86EnableIO 5 >>> (II) xf86EnableIO: ffffffff >>> (WW) Can't map IO space! >> Try a 'sysctl hw.ofwfb.relax_mmap=1' before starting X. The Xorg ATI >> driver attempts to mmap more memory than the card reports, and the OFW >> syscons driver thinks this is an error. >> >> However, since X hasn't fixed this in years now, it's probably time to >> remove the check since every user trips up on it :( > > sysctl trick worked. > > Next problem is "fbdevhw". > > Error log: > > (EE) R128: Failed to load module "fbdevhw" (module does not exist, 0) > (EE) Screen(s) found, but none have a usable configuration. There is a configuration knob in the xorg.conf file you need to set: Option "UseFBDev" "off" > Also, is there a way to make 'sysctl hw.ofwfb.relax_mmap=1' happen on > startup, or be the default state? See sysctl.conf(5). > (Further question, anyone had luck getting ACPI Suspend or display sleep > to work with macs?) There is no suspend support on macs, and may never be. We could probably at least add cpufreq support, though. DPMS (display sleep) should work fine. -Nathan From horst at sxemacs.org Thu Oct 16 16:45:31 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Thu Oct 16 16:45:37 2008 Subject: [Fwd: X hassles - "Device not found"] In-Reply-To: <48F75AD0.2000304@freebsd.org> References: <1224067336.10591.17.camel@horst-tla> <48F5E51B.7020207@freebsd.org> <1224170091.10591.25.camel@horst-tla> <48F75AD0.2000304@freebsd.org> Message-ID: <1224175610.10591.30.camel@horst-tla> On Thu, 2008-10-16 at 10:16 -0500, Nathan Whitehorn wrote: > Horst G?nther Burkhardt III wrote: > > On Wed, 2008-10-15 at 06:42 -0600, Peter Grehan wrote: > >> Hi Horst, > >> > >>> (WW) xf86EnableIO 5 > >>> (II) xf86EnableIO: ffffffff > >>> (WW) Can't map IO space! > >> Try a 'sysctl hw.ofwfb.relax_mmap=1' before starting X. The Xorg ATI > >> driver attempts to mmap more memory than the card reports, and the OFW > >> syscons driver thinks this is an error. > >> > >> However, since X hasn't fixed this in years now, it's probably time to > >> remove the check since every user trips up on it :( > > > > sysctl trick worked. > > > > Next problem is "fbdevhw". > > > > Error log: > > > > (EE) R128: Failed to load module "fbdevhw" (module does not exist, 0) > > (EE) Screen(s) found, but none have a usable configuration. > > There is a configuration knob in the xorg.conf file you need to set: > Option "UseFBDev" "off" Cheers. Now to deal with the fact that i get a black screen where I should be seeing twm, and the fact that after hitting C-M-BS I don't get my syscons back. :( Is there no winning? :) (Do I have to install twm too? (also the led on the monitor isn't doing anything weird that would indicate out-of-range so i have no clue of the bug) > > Also, is there a way to make 'sysctl hw.ofwfb.relax_mmap=1' happen on > > startup, or be the default state? > > See sysctl.conf(5). Okay, i'll check that when i boot up again, I had to force power down in a moment of lack of clarity of mind. > > (Further question, anyone had luck getting ACPI Suspend or display sleep > > to work with macs?) > > There is no suspend support on macs, and may never be. We could probably > at least add cpufreq support, though. DPMS (display sleep) should work fine. I don't know how display sleep works - any pointers at docs would be appreciated. I don't like the idea of my 17" trinitron sitting there acquiring burn-in of console text, even though it would be AWESOME. I don't need suspend support so much - I'm fine leaving boxes running for days, weeks, months at a time. :) Thanks very much. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081016/e12609b8/attachment.pgp From bigguy_40 at yahoo.com Thu Oct 16 16:39:34 2008 From: bigguy_40 at yahoo.com (Chris "Bigguy") Date: Thu Oct 16 16:51:24 2008 Subject: freeBSD on PowerMac G4 install help needed In-Reply-To: <20081015120018.42E1C10656C1@hub.freebsd.org> Message-ID: <526328.319.qm@web33107.mail.mud.yahoo.com> I'm new on the list and Horsts' message was the first clue that I've gotten that someone can install FreeBSD on a Mac. I've been trying on-and-off for months without success (but learned a lot in the process). If someone(s) could help me, I'd be glad to document the process if it isn't already done. I have a Digital Audio system with 768M RAM and a CD reader. All my best - Chris; Rochester, New York From bruce at cran.org.uk Thu Oct 16 17:59:22 2008 From: bruce at cran.org.uk (Bruce Cran) Date: Thu Oct 16 17:59:28 2008 Subject: freeBSD on PowerMac G4 install help needed In-Reply-To: <526328.319.qm@web33107.mail.mud.yahoo.com> References: <20081015120018.42E1C10656C1@hub.freebsd.org> <526328.319.qm@web33107.mail.mud.yahoo.com> Message-ID: <20081016175920.GA7118@muon.cran.org.uk> On Thu, Oct 16, 2008 at 09:11:32AM -0700, Chris Bigguy wrote: > I'm new on the list and Horsts' message was the first clue that I've gotten that someone can install FreeBSD on a Mac. I've been trying on-and-off for months without success (but learned a lot in the process). If someone(s) could help me, I'd be glad to document the process if it isn't already done. > > I have a Digital Audio system with 768M RAM and a CD reader. > I recently installed FreeBSD on my iBook G4. I don't mind leaving the CD in the drive permanently though, so it makes the process simpler; also, I decided to have FreeBSD be the only OS on the Mac. Before you start, you might want to set auto-boot off in the OpenFirmware so you can figure out the correct boot command - see http://www.netneurotic.net/mac/openfirmware.html for details. First, I booted from the OS X install DVD, ran the Disk Utility and repartitioned the disk. Then, I swapped the DVD for the 8-CURRENT FreeBSD CD. That booted me into sysinstall where I went through the installation procedure, selecting each partition as a separate filesystem, since FreeBSD/ppc doesn't use slices. When the laptop had rebooted, it stopped at the OpenFirmware prompt and I just had to run boot cd:,\boot\loader hd:5 in order to boot the loader from the CD. That in turn loads the kernel from the HDD and boots into FreeBSD. In a previous installation I had to use hd:3 so you might have to try a few before it works. Once you've got it booting you might want to configure the boot-device and boot-file parameters in OpenFirmware and set auto-boot back to true if you want to boot into FreeBSD automatically. There are several steps where it's easy to go wrong - where are you getting stuck? -- Bruce Cran From bugmaster at FreeBSD.org Mon Oct 20 11:06:56 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Oct 20 11:08:39 2008 Subject: Current problem reports assigned to freebsd-ppc@FreeBSD.org Message-ID: <200810201106.m9KB6u2m082758@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- a power/121407 ppc [panic] Won't boot up; strange error message. o power/112435 ppc [nexus] [patch] Update nexus children to use ofw_bus f o power/111296 ppc [kernel] [patch] [request] Support IMISS, DLMISS an DS o power/93203 ppc FreeBSD PPC Can't Write to Partitions. 4 problems total. From jrh29 at alumni.cwru.edu Tue Oct 21 02:27:56 2008 From: jrh29 at alumni.cwru.edu (Justin Hibbits) Date: Tue Oct 21 02:28:03 2008 Subject: graphics on G4 Message-ID: <20081021022732.GB2578@narn.knownspace> An oddity I've found with FreeBSD/ppc on my G4 MDD -- when I do anything with graphics, after a while the whole machine just hangs when I try to spawn a new process. It's not a deterministic problem, it just happens 'eventually', but nearly 100% of the time it does happen -- when I start X or play with the framebuffer directly (mmap(2) of /dev/tty or /dev/mem with the offset of the video card). Has anyone else run into this problem? I haven't tried with the latest -CURRENT, but every kernel from January through August that I've built of -CURRENT has exhibited this problem. I have an ATI Radeon 9600 mac edition, in a MDD w/ 1.25GB RAM. - Justin From horst at sxemacs.org Tue Oct 21 09:50:57 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Tue Oct 21 09:51:04 2008 Subject: graphics on G4 In-Reply-To: <20081021022732.GB2578@narn.knownspace> References: <20081021022732.GB2578@narn.knownspace> Message-ID: <1224582766.10591.57.camel@horst-tla> On Mon, 2008-10-20 at 22:27 -0400, Justin Hibbits wrote: > An oddity I've found with FreeBSD/ppc on my G4 MDD -- when I do anything with > graphics, after a while the whole machine just hangs when I try to spawn a new > process. It's not a deterministic problem, it just happens 'eventually', but > nearly 100% of the time it does happen -- when I start X or play with the > framebuffer directly (mmap(2) of /dev/tty or /dev/mem with the offset of the > video card). Has anyone else run into this problem? I haven't tried with the > latest -CURRENT, but every kernel from January through August that I've built of > -CURRENT has exhibited this problem. I have an ATI Radeon 9600 mac edition, in > a MDD w/ 1.25GB RAM. > > - Justin Not sure if this is related, but I get the same thing on my G4 GbE/ADC when starting X - blank screen, then C-M-BS doesn't return syscons, nor does anything else. strangely enough if I type 'shutdown -h now' on a known root console, the system shuts down. I do experience a display hanng though. I only know this to be an issue with X - I haven't played with anything else yet. (7.1-BETA, -CURRENT unknown.) ATi Rage 128 Pro. Also, Justin, I envy you your machine. It sounds frickin' sweeeeeet. :) -- Horst -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081021/f97bf559/attachment.pgp From grehan at freebsd.org Tue Oct 21 15:57:59 2008 From: grehan at freebsd.org (Peter Grehan) Date: Tue Oct 21 15:58:05 2008 Subject: graphics on G4 Message-ID: <20081022015714.EKM92209@dommail.onthenet.com.au> Hi Justin, >An oddity I've found with FreeBSD/ppc on my G4 MDD -- >when I do anything with graphics, after a while the >whole machine just hangs when I try to spawn a new >process. It's not a deterministic problem, it just >happens 'eventually', but nearly 100% of the time it >does happen The framebuffer uses a large chunk of kernel VM when mmap'd. Are you able to dump some vm stats while doing this e.g. sysctl vm.kvm_free ? later, Peter. From jrh29 at alumni.cwru.edu Tue Oct 21 18:17:54 2008 From: jrh29 at alumni.cwru.edu (Justin Hibbits) Date: Tue Oct 21 18:18:00 2008 Subject: graphics on G4 In-Reply-To: <20081022015714.EKM92209@dommail.onthenet.com.au> References: <20081022015714.EKM92209@dommail.onthenet.com.au> Message-ID: <20081021181727.GC2578@narn.knownspace> Hi Peter, On Wed, Oct 22, 2008 at 01:57:14AM +1000, Peter Grehan wrote: > Hi Justin, > > >An oddity I've found with FreeBSD/ppc on my G4 MDD -- > >when I do anything with graphics, after a while the > >whole machine just hangs when I try to spawn a new > >process. It's not a deterministic problem, it just > >happens 'eventually', but nearly 100% of the time it > >does happen > > The framebuffer uses a large chunk of kernel VM when mmap'd. > Are you able to dump some vm stats while doing this e.g. > sysctl vm.kvm_free ? > > later, > > Peter. There is no vm.kvm_free sysctl on my install. Here are the stats from sysctl vm.phys_free, vm.vmtotal, and vm.loadavg while running X/windowmaker vm.phys_free: FREE LIST 0: ORDER (SIZE) | NUMBER | POOL 0 | POOL 1 | POOL 2 -- -- -- -- -- -- -- -- 10 ( 4096K) | 0 | 0 | 0 9 ( 2048K) | 0 | 0 | 0 8 ( 1024K) | 0 | 0 | 0 7 ( 512K) | 0 | 0 | 0 6 ( 256K) | 0 | 0 | 0 5 ( 128K) | 0 | 0 | 0 4 ( 64K) | 0 | 0 | 0 3 ( 32K) | 0 | 0 | 0 2 ( 16K) | 0 | 0 | 0 1 ( 8K) | 57 | 0 | 605 0 ( 4K) | 2 | 23 | 13370 vm.vmtotal: System wide totals computed every five seconds: (values in kilobytes) =============================================== Processes: (RUNQ: 1 Disk Wait: 0 Page Wait: 0 Sleep: 74) Virtual Memory: (Total: 1391388K, Active 288188K) Real Memory: (Total: 142548K Active 130496K) Shared Virtual Memory: (Total: 53356K Active: 51276K) Shared Real Memory: (Total: 23100K Active: 22912K) Free Memory Pages: 58896K vm.loadavg: { 0.15 0.10 0.07 } What other stats are relevant? I neglected to mention before, but it happens even when I exit out of X, or the program mmap()ing the video card quits. I have a hunch that it's overwriting some piece of memory needed by the process list. - Justin From grehan at freebsd.org Tue Oct 21 19:01:44 2008 From: grehan at freebsd.org (Peter Grehan) Date: Tue Oct 21 19:32:44 2008 Subject: graphics on G4 Message-ID: <20081022050101.EKN14563@dommail.onthenet.com.au> Hi Justin, >> The framebuffer uses a large chunk of kernel VM when mmap'd. >> Are you able to dump some vm stats while doing this e.g. >> sysctl vm.kvm_free ? I shouldn't hit send before the morning coffee :( mmap'ing uses process VM, not kernel, except for the extra alloc's needed for this but these should all come from the non-KVA UMA small malloc area. >There is no vm.kvm_free sysctl on my install. That's probably i386/amd64 only. Worth adding for ppc though. >vm.vmtotal: >System wide totals computed every five seconds: (values in kilobytes) >=============================================== >Processes: (RUNQ: 1 Disk Wait: 0 Page Wait: 0 Sleep: 74) >Virtual Memory: (Total: 1391388K, Active 288188K) >Real Memory: (Total: 142548K Active 130496K) >Shared Virtual Memory: (Total: 53356K Active: 51276K) >Shared Real Memory: (Total: 23100K Active: 22912K) >Free Memory Pages: 58896K > >vm.loadavg: { 0.15 0.10 0.07 } > >What other stats are relevant? > >I neglected to mention before, but it happens even when I exit out of X, or the >program mmap()ing the video card quits. I have a hunch that it's overwriting >some piece of memory needed by the process list. That sounds like a good place to start. For the case when the program mmap's the video, does it write to all the pages ? One thing to try would be to write a known value to screen memory e.g. 0xdeadcode, and on exit see if that triggers a panic rather than a hang. later, Peter. From andreast-list at fgznet.ch Tue Oct 21 19:56:11 2008 From: andreast-list at fgznet.ch (Andreas Tobler) Date: Tue Oct 21 19:56:17 2008 Subject: imacDV and X11 Message-ID: <48FE33D7.3080505@fgznet.ch> Hi all, this is just a fyi. I read the list and see people are struggling about X11 conf. Here my bits, maybe they are helpful to somebody. I have an imacDV with CURRENT. The one which has a defective mem slot. FreeBSD 8.0-CURRENT #0: Sat Oct 18 21:04:01 CEST 2008 andreast@imacb:/usr/obj/export/devel/fbsd-src/src/sys/ANDREAST cpu0: Motorola PowerPC 750 revision 3.2, 500.00 MHz cpu0: L1 I-cache enabled, L1 D-cache enabled cpu0: 512KB write-back backside cache cpu0: HID0 8090c0a4 real memory = 526626816 (502 MB) avail memory = 506875904 (483 MB) I run X11 with gdm and xfce4. Icewm did not build as of last weekend. Np. I built everthing on my own. I attach my xorg.conf, I hope I'm allowed to, regarding list policies. Regarding the kbd settings, I advise to use the standard ones. I use my own one which is not submitted to xorg. I did not follow the rules there. but I can use @ | etc on my ch_DE mac USB kbd as I'm used to under OS-X. (Here @ is under alt-g, | under alt-7, etc) If anybody is interested in my Xorg.0.log mail me. Feel free to ask. Btw, I use similar settings on vmware-fusion on a macbook pro where I run amd64-*freebsd8. But there I struggle about the display size. Nevertheless, amazing work of you fbsd people! Thanks! Andreas -------------- next part -------------- Section "ServerLayout" Identifier "X.org Configured" Screen 0 "Screen0" 0 0 InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" EndSection Section "Files" RgbPath "/usr/local/share/X11/rgb" ModulePath "/usr/local/lib/xorg/modules" FontPath "/usr/local/lib/X11/fonts/misc/" FontPath "/usr/local/lib/X11/fonts/TTF/" FontPath "/usr/local/lib/X11/fonts/OTF" FontPath "/usr/local/lib/X11/fonts/Type1/" FontPath "/usr/local/lib/X11/fonts/100dpi/" FontPath "/usr/local/lib/X11/fonts/75dpi/" EndSection Section "Module" Load "extmod" # Load "record" Load "dbe" Load "dri" Load "glx" Load "GLcore" Load "xtrap" # Load "freetype" # Load "type1" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "XkbModel" "macintosh" Option "XkbLayout" "de_CH" Option "XkbOptions" "grp:lswitch,grp:switch" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/sysmouse" Option "ZAxisMapping" "4 5 6 7" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Apple" ModelName "Apple iMac CRT" DisplaySize 270 200 HorizSync 60.0 - 60.0 VertRefresh 75.0 - 95.0 Option "DPMS" "true" EndSection Section "Device" ### Available Driver options are:- ### Values: : integer, : float, : "True"/"False", ### : "String", : " Hz/kHz/MHz" ### [arg]: arg optional #Option "NoAccel" # [] #Option "SWcursor" # [] #Option "Dac6Bit" # [] #Option "Dac8Bit" # [] #Option "DMAForXv" # [] #Option "ForcePCIMode" # [] #Option "CCEPIOMode" # [] #Option "CCENoSecurity" # [] #Option "CCEusecTimeout" # #Option "AGPMode" # #Option "AGPSize" # #Option "RingSize" # #Option "BufferSize" # #Option "EnablePageFlip" # [] #Option "Display" # #Option "PanelWidth" # #Option "PanelHeight" # #Option "ProgramFPRegs" # [] Option "UseFBDev" "off" #Option "VideoKey" # #Option "ShowCache" # [] #Option "VGAAccess" # [] Identifier "Card0" Driver "ati" VendorName "ATI Technologies Inc" BoardName "Rage 128 PR/PRO AGP 4x TMDS" BusID "PCI:0:16:0" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor "Monitor0" DefaultDepth 24 SubSection "Display" Modes "1024x768" "800x600" "640x480" Viewport 0 0 Depth 8 EndSubSection SubSection "Display" Modes "1024x768" "800x600" "640x480" Viewport 0 0 Depth 16 EndSubSection SubSection "Display" Modes "1024x768" "800x600" "640x480" Viewport 0 0 Depth 24 EndSubSection EndSection From nwhitehorn at freebsd.org Tue Oct 21 22:20:00 2008 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Tue Oct 21 22:20:31 2008 Subject: graphics on G4 In-Reply-To: <20081022050101.EKN14563@dommail.onthenet.com.au> References: <20081022050101.EKN14563@dommail.onthenet.com.au> Message-ID: <48FE557C.5020207@freebsd.org> Peter Grehan wrote: > Hi Justin, > > >>> The framebuffer uses a large chunk of kernel VM when mmap'd. >>> Are you able to dump some vm stats while doing this e.g. >>> sysctl vm.kvm_free ? >>> > > I shouldn't hit send before the morning coffee :( mmap'ing > uses process VM, not kernel, except for the extra alloc's > needed for this but these should all come from the non-KVA UMA > small malloc area. > One thing that worries me about our PMAP layer could cause this. This machine has a lot of RAM. What happens if we have physical or device memory in the same range as kmem VAs? It seems like trying to modify it through the BAT map (as zero/copy page, /dev/mem and friends do) will overwrite random bits of KVA instead... -Nathan From tinderbox at freebsd.org Tue Oct 21 23:21:45 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Tue Oct 21 23:22:02 2008 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20081021232142.093CA73039@freebsd-current.sentex.ca> TB --- 2008-10-21 22:08:38 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-10-21 22:08:38 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-10-21 22:08:38 - cleaning the object tree TB --- 2008-10-21 22:09:10 - cvsupping the source tree TB --- 2008-10-21 22:09:10 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-10-21 22:09:17 - building world (CFLAGS=-O -pipe) TB --- 2008-10-21 22:09:17 - cd /src TB --- 2008-10-21 22:09:17 - /usr/bin/make -B buildworld >>> World build started on Tue Oct 21 22:09:19 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Tue Oct 21 23:17:01 UTC 2008 TB --- 2008-10-21 23:17:01 - generating LINT kernel config TB --- 2008-10-21 23:17:01 - cd /src/sys/powerpc/conf TB --- 2008-10-21 23:17:01 - /usr/bin/make -B LINT TB --- 2008-10-21 23:17:01 - building LINT kernel (COPTFLAGS=) TB --- 2008-10-21 23:17:01 - cd /src TB --- 2008-10-21 23:17:01 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue Oct 21 23:17:02 UTC 2008 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/dev/ppbus/immio.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/dev/ppbus/lpbb.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/dev/ppbus/lpt.c cc1: warnings being treated as errors /src/sys/dev/ppbus/lpt.c: In function 'lpt_attach': /src/sys/dev/ppbus/lpt.c:402: warning: assignment makes pointer from integer without a cast /src/sys/dev/ppbus/lpt.c: In function 'lptopen': /src/sys/dev/ppbus/lpt.c:479: warning: assignment makes integer from pointer without a cast *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-10-21 23:21:41 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-10-21 23:21:41 - ERROR: failed to build lint kernel TB --- 2008-10-21 23:21:41 - tinderbox aborted TB --- 3298.10 user 390.92 system 4382.80 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From tinderbox at freebsd.org Tue Oct 21 23:41:09 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Tue Oct 21 23:41:15 2008 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20081021232142.093CA73039@freebsd-current.sentex.ca> TB --- 2008-10-21 22:08:38 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-10-21 22:08:38 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-10-21 22:08:38 - cleaning the object tree TB --- 2008-10-21 22:09:10 - cvsupping the source tree TB --- 2008-10-21 22:09:10 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-10-21 22:09:17 - building world (CFLAGS=-O -pipe) TB --- 2008-10-21 22:09:17 - cd /src TB --- 2008-10-21 22:09:17 - /usr/bin/make -B buildworld >>> World build started on Tue Oct 21 22:09:19 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Tue Oct 21 23:17:01 UTC 2008 TB --- 2008-10-21 23:17:01 - generating LINT kernel config TB --- 2008-10-21 23:17:01 - cd /src/sys/powerpc/conf TB --- 2008-10-21 23:17:01 - /usr/bin/make -B LINT TB --- 2008-10-21 23:17:01 - building LINT kernel (COPTFLAGS=) TB --- 2008-10-21 23:17:01 - cd /src TB --- 2008-10-21 23:17:01 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue Oct 21 23:17:02 UTC 2008 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/dev/ppbus/immio.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/dev/ppbus/lpbb.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/dev/ppbus/lpt.c cc1: warnings being treated as errors /src/sys/dev/ppbus/lpt.c: In function 'lpt_attach': /src/sys/dev/ppbus/lpt.c:402: warning: assignment makes pointer from integer without a cast /src/sys/dev/ppbus/lpt.c: In function 'lptopen': /src/sys/dev/ppbus/lpt.c:479: warning: assignment makes integer from pointer without a cast *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-10-21 23:21:41 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-10-21 23:21:41 - ERROR: failed to build lint kernel TB --- 2008-10-21 23:21:41 - tinderbox aborted TB --- 3298.10 user 390.92 system 4382.80 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From tinderbox at freebsd.org Wed Oct 22 04:52:06 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Wed Oct 22 04:52:24 2008 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20081022045202.21B1773039@freebsd-current.sentex.ca> TB --- 2008-10-22 03:38:28 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-10-22 03:38:28 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-10-22 03:38:28 - cleaning the object tree TB --- 2008-10-22 03:39:00 - cvsupping the source tree TB --- 2008-10-22 03:39:00 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-10-22 03:39:07 - building world (CFLAGS=-O -pipe) TB --- 2008-10-22 03:39:07 - cd /src TB --- 2008-10-22 03:39:07 - /usr/bin/make -B buildworld >>> World build started on Wed Oct 22 03:39:09 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Wed Oct 22 04:47:27 UTC 2008 TB --- 2008-10-22 04:47:27 - generating LINT kernel config TB --- 2008-10-22 04:47:27 - cd /src/sys/powerpc/conf TB --- 2008-10-22 04:47:27 - /usr/bin/make -B LINT TB --- 2008-10-22 04:47:27 - building LINT kernel (COPTFLAGS=) TB --- 2008-10-22 04:47:27 - cd /src TB --- 2008-10-22 04:47:27 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Wed Oct 22 04:47:28 UTC 2008 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/dev/ppbus/immio.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/dev/ppbus/lpbb.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/dev/ppbus/lpt.c cc1: warnings being treated as errors /src/sys/dev/ppbus/lpt.c: In function 'lpt_attach': /src/sys/dev/ppbus/lpt.c:402: warning: assignment makes pointer from integer without a cast /src/sys/dev/ppbus/lpt.c: In function 'lptopen': /src/sys/dev/ppbus/lpt.c:479: warning: assignment makes integer from pointer without a cast *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-10-22 04:52:02 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-10-22 04:52:02 - ERROR: failed to build lint kernel TB --- 2008-10-22 04:52:02 - tinderbox aborted TB --- 3301.73 user 384.54 system 4413.44 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From tinderbox at freebsd.org Wed Oct 22 04:52:41 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Wed Oct 22 04:52:48 2008 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20081022045202.21B1773039@freebsd-current.sentex.ca> TB --- 2008-10-22 03:38:28 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-10-22 03:38:28 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-10-22 03:38:28 - cleaning the object tree TB --- 2008-10-22 03:39:00 - cvsupping the source tree TB --- 2008-10-22 03:39:00 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-10-22 03:39:07 - building world (CFLAGS=-O -pipe) TB --- 2008-10-22 03:39:07 - cd /src TB --- 2008-10-22 03:39:07 - /usr/bin/make -B buildworld >>> World build started on Wed Oct 22 03:39:09 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Wed Oct 22 04:47:27 UTC 2008 TB --- 2008-10-22 04:47:27 - generating LINT kernel config TB --- 2008-10-22 04:47:27 - cd /src/sys/powerpc/conf TB --- 2008-10-22 04:47:27 - /usr/bin/make -B LINT TB --- 2008-10-22 04:47:27 - building LINT kernel (COPTFLAGS=) TB --- 2008-10-22 04:47:27 - cd /src TB --- 2008-10-22 04:47:27 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Wed Oct 22 04:47:28 UTC 2008 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/dev/ppbus/immio.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/dev/ppbus/lpbb.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/dev/ppbus/lpt.c cc1: warnings being treated as errors /src/sys/dev/ppbus/lpt.c: In function 'lpt_attach': /src/sys/dev/ppbus/lpt.c:402: warning: assignment makes pointer from integer without a cast /src/sys/dev/ppbus/lpt.c: In function 'lptopen': /src/sys/dev/ppbus/lpt.c:479: warning: assignment makes integer from pointer without a cast *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-10-22 04:52:02 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-10-22 04:52:02 - ERROR: failed to build lint kernel TB --- 2008-10-22 04:52:02 - tinderbox aborted TB --- 3301.73 user 384.54 system 4413.44 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From horst at sxemacs.org Wed Oct 22 06:37:49 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Wed Oct 22 06:37:57 2008 Subject: Resignation, X being a , and assorted questions. In-Reply-To: <48FE33D7.3080505@fgznet.ch> References: <48FE33D7.3080505@fgznet.ch> Message-ID: <1224657584.10591.72.camel@horst-tla> Note: the following is divided into sections: Hi all. ----- X11 ----- I've decided I'm probably going to have to set up an X-less system, at any rate X is failing pretty hard here. I no longer have a traceable error set, just a black screen. Just in case I _have_ somehow cocked up, I need to ask an obvious question. Does X still compile with twm by default, or do I need to compile a window manager to do anything? Xorg.0.log nopasted to http://rafb.net/p/tCJhpm51.html xorg.conf has been proven not to be wrong. ( Yes I realise it looks normal. But surely X doesn't take five minutes to start? It didn't on my Pentium II :( ) ------------ Networking ------------ It seems FreeBSD does not always try to do DHCP configuration at boot of the onboard gem0 - This is slightly annoying as it always boots up thinking it's 1976. I'm sure you can understand why this is of concern. I've tried editing some of the bootscripts for this to no avail - any ideas? ------- Audio ------- I'm not sure of the soundcard this mac uses, but I believe it's Apple Crystal (a look at the motherboard and there's a small chip that says CRYSTAL that looks like the sound chip on the iMac) so... I think FreeBSD supports it. Is there a good way to test sound with the base system (i.e. without installing mpg123?) Thanks in advance for any answers, and I apologise if i'm getting slightly annoying. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081022/89fbff03/attachment.pgp From marcotrillo at gmail.com Wed Oct 22 09:10:56 2008 From: marcotrillo at gmail.com (Marco Trillo) Date: Wed Oct 22 09:11:02 2008 Subject: Resignation, X being a , and assorted questions. In-Reply-To: <1224657584.10591.72.camel@horst-tla> References: <48FE33D7.3080505@fgznet.ch> <1224657584.10591.72.camel@horst-tla> Message-ID: Hi, On Wed, Oct 22, 2008 at 8:39 AM, Horst G?nther Burkhardt III wrote: > ------------ > Networking > ------------ > It seems FreeBSD does not always try to do DHCP configuration at boot of > the onboard gem0 - This is slightly annoying as it always boots up > thinking it's 1976. I'm sure you can understand why this is of concern. > > I've tried editing some of the bootscripts for this to no avail - any > ideas? Do you have a line such as ifconfig_gem0="DHCP" added to your /etc/rc.conf file ? > > ------- > Audio > ------- > I'm not sure of the soundcard this mac uses, but I believe it's Apple > Crystal (a look at the motherboard and there's a small chip that says > CRYSTAL that looks like the sound chip on the iMac) so... I think > FreeBSD supports it. Is there a good way to test sound with the base > system (i.e. without installing mpg123?) > The Crystal chip is indeed the sound codec -- it can be either the "Burgundy" (CS4211) chip, used on original iMacs, or the "Screamer" (CS4212) chip, used on iMac DVs and late iMac G3s. What model of iMac is this? I have a driver and patch that supports both of these devices -- currently audio output only. It should apply at least to 8.0-current and to 7.x -- let me know if you are interested on testing it . Thanks, Marco From horst at sxemacs.org Wed Oct 22 09:37:10 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Wed Oct 22 09:37:18 2008 Subject: Resignation, X being a , and assorted questions. In-Reply-To: References: <48FE33D7.3080505@fgznet.ch> <1224657584.10591.72.camel@horst-tla> Message-ID: <1224668347.10591.76.camel@horst-tla> On Wed, 2008-10-22 at 11:10 +0200, Marco Trillo wrote: > Hi, > > ------- > > Audio > > ------- > > I'm not sure of the soundcard this mac uses, but I believe it's Apple > > Crystal (a look at the motherboard and there's a small chip that says > > CRYSTAL that looks like the sound chip on the iMac) so... I think > > FreeBSD supports it. Is there a good way to test sound with the base > > system (i.e. without installing mpg123?) > > > > The Crystal chip is indeed the sound codec -- it can be either the > "Burgundy" (CS4211) chip, used on original iMacs, or the "Screamer" > (CS4212) chip, used on iMac DVs and late iMac G3s. What model of iMac > is this? CS4212-KL so it's a Screamer. This isn't an iMac though - i'm just saying it's the same sort of physical chip as the iMac's sound chip. This is a Power Mac G4 Gigabit Ethernet / ADC (also known as a PowerMac3,3 in gestaltid nomenclature) > I have a driver and patch that supports both of these devices -- > currently audio output only. It should apply at least to 8.0-current > and to 7.x -- let me know if you are interested on testing it . I'm interested in testing it, and a good thing too as I'm going to compile a new kernel soon - so I can remove some of the unneeded stuff like fwe :) > Thanks, > Marco > -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081022/63fcd7c9/attachment.pgp From tinderbox at freebsd.org Wed Oct 22 10:15:55 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Wed Oct 22 10:16:07 2008 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20081022101547.B07D273039@freebsd-current.sentex.ca> TB --- 2008-10-22 09:02:52 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-10-22 09:02:52 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-10-22 09:02:52 - cleaning the object tree TB --- 2008-10-22 09:03:18 - cvsupping the source tree TB --- 2008-10-22 09:03:18 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-10-22 09:03:23 - building world (CFLAGS=-O -pipe) TB --- 2008-10-22 09:03:23 - cd /src TB --- 2008-10-22 09:03:23 - /usr/bin/make -B buildworld >>> World build started on Wed Oct 22 09:03:25 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Wed Oct 22 10:11:15 UTC 2008 TB --- 2008-10-22 10:11:15 - generating LINT kernel config TB --- 2008-10-22 10:11:15 - cd /src/sys/powerpc/conf TB --- 2008-10-22 10:11:15 - /usr/bin/make -B LINT TB --- 2008-10-22 10:11:15 - building LINT kernel (COPTFLAGS=) TB --- 2008-10-22 10:11:15 - cd /src TB --- 2008-10-22 10:11:15 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Wed Oct 22 10:11:15 UTC 2008 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/dev/ppbus/immio.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/dev/ppbus/lpbb.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/dev/ppbus/lpt.c cc1: warnings being treated as errors /src/sys/dev/ppbus/lpt.c: In function 'lpt_attach': /src/sys/dev/ppbus/lpt.c:402: warning: assignment makes pointer from integer without a cast /src/sys/dev/ppbus/lpt.c: In function 'lptopen': /src/sys/dev/ppbus/lpt.c:479: warning: assignment makes integer from pointer without a cast *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-10-22 10:15:47 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-10-22 10:15:47 - ERROR: failed to build lint kernel TB --- 2008-10-22 10:15:47 - tinderbox aborted TB --- 3298.85 user 386.80 system 4375.04 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From tinderbox at freebsd.org Wed Oct 22 10:16:29 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Wed Oct 22 10:16:35 2008 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20081022101547.B07D273039@freebsd-current.sentex.ca> TB --- 2008-10-22 09:02:52 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-10-22 09:02:52 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-10-22 09:02:52 - cleaning the object tree TB --- 2008-10-22 09:03:18 - cvsupping the source tree TB --- 2008-10-22 09:03:18 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-10-22 09:03:23 - building world (CFLAGS=-O -pipe) TB --- 2008-10-22 09:03:23 - cd /src TB --- 2008-10-22 09:03:23 - /usr/bin/make -B buildworld >>> World build started on Wed Oct 22 09:03:25 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Wed Oct 22 10:11:15 UTC 2008 TB --- 2008-10-22 10:11:15 - generating LINT kernel config TB --- 2008-10-22 10:11:15 - cd /src/sys/powerpc/conf TB --- 2008-10-22 10:11:15 - /usr/bin/make -B LINT TB --- 2008-10-22 10:11:15 - building LINT kernel (COPTFLAGS=) TB --- 2008-10-22 10:11:15 - cd /src TB --- 2008-10-22 10:11:15 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Wed Oct 22 10:11:15 UTC 2008 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/dev/ppbus/immio.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/dev/ppbus/lpbb.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/dev/ppbus/lpt.c cc1: warnings being treated as errors /src/sys/dev/ppbus/lpt.c: In function 'lpt_attach': /src/sys/dev/ppbus/lpt.c:402: warning: assignment makes pointer from integer without a cast /src/sys/dev/ppbus/lpt.c: In function 'lptopen': /src/sys/dev/ppbus/lpt.c:479: warning: assignment makes integer from pointer without a cast *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-10-22 10:15:47 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-10-22 10:15:47 - ERROR: failed to build lint kernel TB --- 2008-10-22 10:15:47 - tinderbox aborted TB --- 3298.85 user 386.80 system 4375.04 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From marcotrillo at gmail.com Wed Oct 22 10:17:50 2008 From: marcotrillo at gmail.com (Marco Trillo) Date: Wed Oct 22 10:17:57 2008 Subject: Resignation, X being a , and assorted questions. In-Reply-To: <1224668347.10591.76.camel@horst-tla> References: <48FE33D7.3080505@fgznet.ch> <1224657584.10591.72.camel@horst-tla> <1224668347.10591.76.camel@horst-tla> Message-ID: Hi, On Wed, Oct 22, 2008 at 11:39 AM, Horst G?nther Burkhardt III wrote: > >> >> The Crystal chip is indeed the sound codec -- it can be either the >> "Burgundy" (CS4211) chip, used on original iMacs, or the "Screamer" >> (CS4212) chip, used on iMac DVs and late iMac G3s. What model of iMac >> is this? > > CS4212-KL so it's a Screamer. This isn't an iMac though - i'm just > saying it's the same sort of physical chip as the iMac's sound chip. > > This is a Power Mac G4 Gigabit Ethernet / ADC (also known as a > PowerMac3,3 in gestaltid nomenclature) Nice, I also have a PowerMac G4 with a Screamer chip which I used to develop the driver, so it should work fine there. > >> I have a driver and patch that supports both of these devices -- >> currently audio output only. It should apply at least to 8.0-current >> and to 7.x -- let me know if you are interested on testing it . > > I'm interested in testing it, and a good thing too as I'm going to > compile a new kernel soon - so I can remove some of the unneeded stuff > like fwe :) > Ok :) The driver is available at: The tar.gz file includes the "sound/macio" subdirectory to include in the kernel, something like this: $ cp -R sound/macio /usr/src/sys/dev/sound/macio The "powermac/" and "patches/" subdirectories can be ignored, as they are not needed for Screamer devices. To register the new driver you can just append the following lines to the /usr/src/sys/conf/files.powerpc file : dev/sound/macio/aoa.c optional powermac davbus dev/sound/macio/davbus.c optional powermac davbus (Alternatively you can apply "patches/files.patch" in /usr/src/sys/conf, but it's possible that it does not apply cleanly to 7.x or recent -current.) To enable the driver you can add the following lines to GENERIC or your kernel config file: device sound device davbus (Or alternatively apply "patches/generic.patch" in /usr/src/sys/powerpc/conf, but as before it may not apply cleanly to 7.x or recent -current.) When booting the new kernel you should get a "pcm0" device, so you can just use any digital player to play sound files, and the "mixer" utility to configure the volume. If you plug something to the rear panel output jack, the internal speaker will be muted automatically. Thanks! Marco From tinderbox at freebsd.org Wed Oct 22 15:52:13 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Wed Oct 22 15:52:26 2008 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20081022155202.90CE273039@freebsd-current.sentex.ca> TB --- 2008-10-22 14:38:25 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-10-22 14:38:25 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-10-22 14:38:25 - cleaning the object tree TB --- 2008-10-22 14:38:45 - cvsupping the source tree TB --- 2008-10-22 14:38:45 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-10-22 14:38:51 - building world (CFLAGS=-O -pipe) TB --- 2008-10-22 14:38:51 - cd /src TB --- 2008-10-22 14:38:51 - /usr/bin/make -B buildworld >>> World build started on Wed Oct 22 14:38:53 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Wed Oct 22 15:47:16 UTC 2008 TB --- 2008-10-22 15:47:16 - generating LINT kernel config TB --- 2008-10-22 15:47:16 - cd /src/sys/powerpc/conf TB --- 2008-10-22 15:47:16 - /usr/bin/make -B LINT TB --- 2008-10-22 15:47:16 - building LINT kernel (COPTFLAGS=) TB --- 2008-10-22 15:47:16 - cd /src TB --- 2008-10-22 15:47:16 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Wed Oct 22 15:47:16 UTC 2008 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/dev/ppbus/immio.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/dev/ppbus/lpbb.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/dev/ppbus/lpt.c cc1: warnings being treated as errors /src/sys/dev/ppbus/lpt.c: In function 'lpt_attach': /src/sys/dev/ppbus/lpt.c:402: warning: assignment makes pointer from integer without a cast /src/sys/dev/ppbus/lpt.c: In function 'lptopen': /src/sys/dev/ppbus/lpt.c:479: warning: assignment makes integer from pointer without a cast *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-10-22 15:52:02 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-10-22 15:52:02 - ERROR: failed to build lint kernel TB --- 2008-10-22 15:52:02 - tinderbox aborted TB --- 3297.34 user 388.62 system 4417.10 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From tinderbox at freebsd.org Wed Oct 22 15:52:55 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Wed Oct 22 15:53:01 2008 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20081022155202.90CE273039@freebsd-current.sentex.ca> TB --- 2008-10-22 14:38:25 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-10-22 14:38:25 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-10-22 14:38:25 - cleaning the object tree TB --- 2008-10-22 14:38:45 - cvsupping the source tree TB --- 2008-10-22 14:38:45 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-10-22 14:38:51 - building world (CFLAGS=-O -pipe) TB --- 2008-10-22 14:38:51 - cd /src TB --- 2008-10-22 14:38:51 - /usr/bin/make -B buildworld >>> World build started on Wed Oct 22 14:38:53 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Wed Oct 22 15:47:16 UTC 2008 TB --- 2008-10-22 15:47:16 - generating LINT kernel config TB --- 2008-10-22 15:47:16 - cd /src/sys/powerpc/conf TB --- 2008-10-22 15:47:16 - /usr/bin/make -B LINT TB --- 2008-10-22 15:47:16 - building LINT kernel (COPTFLAGS=) TB --- 2008-10-22 15:47:16 - cd /src TB --- 2008-10-22 15:47:16 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Wed Oct 22 15:47:16 UTC 2008 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/dev/ppbus/immio.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/dev/ppbus/lpbb.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/dev/ppbus/lpt.c cc1: warnings being treated as errors /src/sys/dev/ppbus/lpt.c: In function 'lpt_attach': /src/sys/dev/ppbus/lpt.c:402: warning: assignment makes pointer from integer without a cast /src/sys/dev/ppbus/lpt.c: In function 'lptopen': /src/sys/dev/ppbus/lpt.c:479: warning: assignment makes integer from pointer without a cast *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-10-22 15:52:02 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-10-22 15:52:02 - ERROR: failed to build lint kernel TB --- 2008-10-22 15:52:02 - tinderbox aborted TB --- 3297.34 user 388.62 system 4417.10 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From jrh29 at alumni.cwru.edu Wed Oct 22 19:31:46 2008 From: jrh29 at alumni.cwru.edu (Justin Hibbits) Date: Wed Oct 22 19:31:55 2008 Subject: graphics on G4 In-Reply-To: <48FE557C.5020207@freebsd.org> References: <20081022050101.EKN14563@dommail.onthenet.com.au> <48FE557C.5020207@freebsd.org> Message-ID: <20081022193118.GD2578@narn.knownspace> On Tue, Oct 21, 2008 at 05:19:40PM -0500, Nathan Whitehorn wrote: > Peter Grehan wrote: > > Hi Justin, > > > > > >>> The framebuffer uses a large chunk of kernel VM when mmap'd. > >>> Are you able to dump some vm stats while doing this e.g. > >>> sysctl vm.kvm_free ? > >>> > > > > I shouldn't hit send before the morning coffee :( mmap'ing > > uses process VM, not kernel, except for the extra alloc's > > needed for this but these should all come from the non-KVA UMA > > small malloc area. > > > One thing that worries me about our PMAP layer could cause this. This > machine has a lot of RAM. What happens if we have physical or device > memory in the same range as kmem VAs? It seems like trying to modify it > through the BAT map (as zero/copy page, /dev/mem and friends do) will > overwrite random bits of KVA instead... > -Nathan I'm not sure where all the RAM lies, but according to ofwdump, the base address of the video memory is 0xa0008000 -- a rather strange address, being 32k offset from base. I'm not sure what the whole memory map is, though. Is there an easy way to get this? I'll run the 0xdeadc0de test in a couple weeks when I get back from vacation, since I don't know if it'll have crashed before I leave, because it's not an instantaneous crash, it just happens -- minutes, hours, or days, either while running or after exiting the "offending" program. - Justin From grehan at freebsd.org Wed Oct 22 18:05:06 2008 From: grehan at freebsd.org (Peter Grehan) Date: Wed Oct 22 20:09:29 2008 Subject: graphics on G4 Message-ID: <20081023040422.EKQ11018@dommail.onthenet.com.au> Hi Nathan, >One thing that worries me about our PMAP layer could cause >this. This machine has a lot of RAM. What happens if we have >physical or device memory in the same range as kmem VAs? >It seems like trying to modify it through the BAT map (as >zero/copy page, /dev/mem and friends do) will overwrite >random bits of KVA instead... Apple h/w seems to use 0-2G for RAM, and 2G and up for MMIO. G5's can then use > 4G for additional RAM. I've not seen a system that has a conflict with the 2 seg's used for KVA, but I wouldn't say it's not possible. Justin - can you drop into OFW, do a 'dev screen' and '.properties', and list the 'address' property ? later, Peter. From horst at sxemacs.org Wed Oct 22 21:02:00 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Wed Oct 22 21:02:06 2008 Subject: Resignation, X being a , and assorted questions. In-Reply-To: References: <48FE33D7.3080505@fgznet.ch> <1224657584.10591.72.camel@horst-tla> <1224668347.10591.76.camel@horst-tla> Message-ID: <1224709441.10591.97.camel@horst-tla> On Wed, 2008-10-22 at 12:17 +0200, Marco Trillo wrote: > > This is a Power Mac G4 Gigabit Ethernet / ADC (also known as a > > PowerMac3,3 in gestaltid nomenclature) > > Nice, I also have a PowerMac G4 with a Screamer chip which I used to > develop the driver, so it should work fine there. That sounds incredibly brilliant :D I don't suppose there's a driver for the Apple onboard modem? I think it's a V.92 jobby, possibly a softmodem. (also it's one of the ones that can be removed from the motherboard) pciconf has nothing to say about it, nor does usbdevs :\ -- Thanks, Horst -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081022/411fbc48/attachment.pgp From nwhitehorn at freebsd.org Wed Oct 22 21:03:24 2008 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Wed Oct 22 21:03:42 2008 Subject: Resignation, X being a , and assorted questions. In-Reply-To: <1224709441.10591.97.camel@horst-tla> References: <48FE33D7.3080505@fgznet.ch> <1224657584.10591.72.camel@horst-tla> <1224668347.10591.76.camel@horst-tla> <1224709441.10591.97.camel@horst-tla> Message-ID: <48FF9507.3030407@freebsd.org> Horst G?nther Burkhardt III wrote: > On Wed, 2008-10-22 at 12:17 +0200, Marco Trillo wrote: > >>> This is a Power Mac G4 Gigabit Ethernet / ADC (also known as a >>> PowerMac3,3 in gestaltid nomenclature) >>> >> Nice, I also have a PowerMac G4 with a Screamer chip which I used to >> develop the driver, so it should work fine there. >> > > That sounds incredibly brilliant :D > > I don't suppose there's a driver for the Apple onboard modem? I think > it's a V.92 jobby, possibly a softmodem. > > (also it's one of the ones that can be removed from the motherboard) > > pciconf has nothing to say about it, nor does usbdevs :\ > The modem is attached to one of the built-in uarts. I believe you have to enable it somehow, though, and I don't believe we support that. -Nathan From horst at sxemacs.org Wed Oct 22 22:32:16 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Wed Oct 22 22:32:22 2008 Subject: Resignation, X being a , and assorted questions. In-Reply-To: <48FF9507.3030407@freebsd.org> References: <48FE33D7.3080505@fgznet.ch> <1224657584.10591.72.camel@horst-tla> <1224668347.10591.76.camel@horst-tla> <1224709441.10591.97.camel@horst-tla> <48FF9507.3030407@freebsd.org> Message-ID: <1224714856.10591.102.camel@horst-tla> On Wed, 2008-10-22 at 16:03 -0500, Nathan Whitehorn wrote: > The modem is attached to one of the built-in uarts. I believe you have > to enable it somehow, though, and I don't believe we support that. > -Nathan Oh well, it's not as if I'll ever need it anyway :) Thanks for the prompt answer. Two more questions - Is it safe to remove "kbdmux" from the kernel on my mac? (I use a usb keyboard, if that has anything to do with it)... Also am I right in assuming that md (memory disks) are an implementation of RAMdisk functionality? and thus that I could safely remove it and md_root from the kernel? Thanks, -- Horst. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081022/f1e56091/attachment.pgp From tinderbox at freebsd.org Fri Oct 24 02:05:56 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Fri Oct 24 02:06:08 2008 Subject: [releng_7_1 tinderbox] failure on powerpc/powerpc Message-ID: <20081024020553.2E0421B5078@freebsd-stable.sentex.ca> TB --- 2008-10-24 02:00:39 - tinderbox 2.4 running on freebsd-stable.sentex.ca TB --- 2008-10-24 02:00:39 - starting RELENG_7_1 tinderbox run for powerpc/powerpc TB --- 2008-10-24 02:00:39 - mkdir /tinderbox/RELENG_7_1/powerpc TB --- 2008-10-24 02:00:39 - mkdir /tinderbox/RELENG_7_1/powerpc/powerpc TB --- 2008-10-24 02:00:39 - cleaning the object tree TB --- 2008-10-24 02:00:39 - cvsupping the source tree TB --- 2008-10-24 02:00:39 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7_1/powerpc/powerpc/supfile TB --- 2008-10-24 02:05:53 - building world (CFLAGS=-O2 -pipe) TB --- 2008-10-24 02:05:53 - cd /src TB --- 2008-10-24 02:05:53 - ERROR: /src: No such file or directory TB --- 2008-10-24 02:05:53 - tinderbox aborted TB --- 2.05 user 0.79 system 313.33 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7_1-powerpc-powerpc.full From tinderbox at freebsd.org Fri Oct 24 02:06:53 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Fri Oct 24 02:07:05 2008 Subject: [releng_7_1 tinderbox] failure on powerpc/powerpc Message-ID: <20081024020553.2E0421B5078@freebsd-stable.sentex.ca> TB --- 2008-10-24 02:00:39 - tinderbox 2.4 running on freebsd-stable.sentex.ca TB --- 2008-10-24 02:00:39 - starting RELENG_7_1 tinderbox run for powerpc/powerpc TB --- 2008-10-24 02:00:39 - mkdir /tinderbox/RELENG_7_1/powerpc TB --- 2008-10-24 02:00:39 - mkdir /tinderbox/RELENG_7_1/powerpc/powerpc TB --- 2008-10-24 02:00:39 - cleaning the object tree TB --- 2008-10-24 02:00:39 - cvsupping the source tree TB --- 2008-10-24 02:00:39 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7_1/powerpc/powerpc/supfile TB --- 2008-10-24 02:05:53 - building world (CFLAGS=-O2 -pipe) TB --- 2008-10-24 02:05:53 - cd /src TB --- 2008-10-24 02:05:53 - ERROR: /src: No such file or directory TB --- 2008-10-24 02:05:53 - tinderbox aborted TB --- 2.05 user 0.79 system 313.33 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7_1-powerpc-powerpc.full _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From nse at delfi-konsult.com Fri Oct 24 12:47:01 2008 From: nse at delfi-konsult.com (Niels S. Eliasen) Date: Fri Oct 24 12:47:08 2008 Subject: freebsd-update ?? nogo on PowerPC ? Message-ID: Anyone knows why I'm getting the following: running "freebsd-update -r 7.1-BETA2" > root]# freebsd-update upgrade --debug -r 7.1-BETA2 > Looking up update.FreeBSD.org mirrors... 1 mirrors found. > Fetching public key from update1.FreeBSD.org... fetch: http://update1.FreeBSD.org/7.0-RELEASE/powerpc/pub.ssl > : Not Found > failed. os is it just so simple that "freebsd-update" is not supported on PowerPC ? kind regards nse "Ach, crivens, what a wee snotter....." Quote from "The Wee Free Men" by Terry Pratchett From tinderbox at freebsd.org Fri Oct 24 13:57:43 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Fri Oct 24 13:58:29 2008 Subject: [releng_7_1 tinderbox] failure on powerpc/powerpc Message-ID: <20081024135741.153441B507A@freebsd-stable.sentex.ca> TB --- 2008-10-24 13:57:34 - tinderbox 2.4 running on freebsd-stable.sentex.ca TB --- 2008-10-24 13:57:34 - starting RELENG_7_1 tinderbox run for powerpc/powerpc TB --- 2008-10-24 13:57:34 - cleaning the object tree TB --- 2008-10-24 13:57:34 - cvsupping the source tree TB --- 2008-10-24 13:57:34 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7_1/powerpc/powerpc/supfile TB --- 2008-10-24 13:57:41 - building world (CFLAGS=-O2 -pipe) TB --- 2008-10-24 13:57:41 - cd /src TB --- 2008-10-24 13:57:41 - ERROR: /src: No such file or directory TB --- 2008-10-24 13:57:41 - tinderbox aborted TB --- 1.41 user 0.06 system 6.48 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7_1-powerpc-powerpc.full From tinderbox at freebsd.org Sat Oct 25 02:17:37 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Sat Oct 25 02:18:21 2008 Subject: [releng_7_1 tinderbox] failure on powerpc/powerpc Message-ID: <20081025021734.CCEFE1B507A@freebsd-stable.sentex.ca> TB --- 2008-10-25 02:17:27 - tinderbox 2.4 running on freebsd-stable.sentex.ca TB --- 2008-10-25 02:17:27 - starting RELENG_7_1 tinderbox run for powerpc/powerpc TB --- 2008-10-25 02:17:27 - cleaning the object tree TB --- 2008-10-25 02:17:27 - cvsupping the source tree TB --- 2008-10-25 02:17:27 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7_1/powerpc/powerpc/supfile TB --- 2008-10-25 02:17:34 - building world (CFLAGS=-O2 -pipe) TB --- 2008-10-25 02:17:34 - cd /src TB --- 2008-10-25 02:17:34 - ERROR: /src: No such file or directory TB --- 2008-10-25 02:17:34 - tinderbox aborted TB --- 1.37 user 0.12 system 7.79 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7_1-powerpc-powerpc.full From jrh29 at alumni.cwru.edu Sat Oct 25 02:45:52 2008 From: jrh29 at alumni.cwru.edu (Justin Hibbits) Date: Sat Oct 25 02:45:58 2008 Subject: graphics on G4 In-Reply-To: <20081023040422.EKQ11018@dommail.onthenet.com.au> References: <20081023040422.EKQ11018@dommail.onthenet.com.au> Message-ID: <20081025024544.GA22527@narn.knownspace> On Thu, Oct 23, 2008 at 04:04:22AM +1000, Peter Grehan wrote: > Hi Nathan, > > >One thing that worries me about our PMAP layer could cause > >this. This machine has a lot of RAM. What happens if we have > >physical or device memory in the same range as kmem VAs? > >It seems like trying to modify it through the BAT map (as > >zero/copy page, /dev/mem and friends do) will overwrite > >random bits of KVA instead... > > Apple h/w seems to use 0-2G for RAM, and 2G and up for MMIO. > G5's can then use > 4G for additional RAM. I've not seen a > system that has a conflict with the 2 seg's used for KVA, but > I wouldn't say it's not possible. > > Justin - can you drop into OFW, do a 'dev screen' and > '.properties', and list the 'address' property ? > > later, > > Peter. The address property is a0008000, from ofw. This seems like a rather odd address, being 8 pages inside the 2.5GB memory space. - Justin From marcotrillo at gmail.com Sun Oct 26 12:17:49 2008 From: marcotrillo at gmail.com (Marco Trillo) Date: Sun Oct 26 12:17:57 2008 Subject: ATA DMA problems with recent -current Message-ID: Hi all, I just updated my -current kernel to today sources -- the previous kernel was from Oct 11. With the new kernel I'm getting ad0 ATA DMA timeouts, which get worse when I stress the drive. The timeouts look like this: ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=3952128 ad0: TIMEOUT - READ_DMA retrying (0 retries left) LBA=3952128 ad0: FAILURE - READ_DMA timed out g_vfs_done(): ad0s4 [READ(offset=1746108416, length=65536)] error=5 vnode_pager_getpages: I/O read error At first, they are occasional and only happen sometimes -- in fact I didn't notice them when booting the first time. However, I then tried to unpack the ports.tar.gz file, like this: $ gzcat ports.tar.gz | tar xf - -C /usr ... which, after unpacking a couple of files, hanged, getting WRITE_DMA timeouts from the kernel. All write attempts to the drive from that point failed. I rebooted the system, and the filesystem appeared dirty to fsck the next boot. Some information from the new kernel -- the full dmesg is at the end of the message: Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.0-CURRENT #57: Sun Oct 26 10:31:37 UTC 2008 mtrillo@emac6:/usr/src/sys/powerpc/compile/GENERIC $ dmesg | grep ata ata0 mem 0x20000-0x20fff,0x8800-0x88ff irq 24,12 on macio0 ata0: [ITHREAD] ata1: mem 0xf5004000-0xf5007fff irq 39 at device 13.0 on pci2 ata1: [ITHREAD] acd0: DVDR at ata0-master WDMA2 ad0: 38166MB at ata1-master UDMA100 $ vmstat -i interrupt total rate irq1: pcm0 1 0 irq61: pcm0 1 0 irq24: ata0 35 0 irq29: ohci0 1 0 irq63: ohci1 ohci+ 59 0 irq39: ata1 943 5 irq40: fwohci0 2 0 irq41: gem0 119 0 Total 1161 6 In contrast, my previous kernel, compiled Oct 11, works perfectly with ATA DMA. The same tests that fail badly on the new kernel (like unpacking ports.tar.gz) complete without any problems on the Oct 11 kernel. Some information from the Oct 11 kernel : Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.0-CURRENT #56: Sat Oct 11 15:57:13 UTC 2008 mtrillo@emac6:/usr/src/sys/powerpc/compile/GENERIC $ dmesg | grep ata ata0 mem 0x20000-0x20fff,0x8800-0x88ff irq 24,12 on macio0 ata0: [ITHREAD] ata1: mem 0xf5004000-0xf5007fff irq 39,1 at device 13.0 on pci2 ata1: [ITHREAD] acd0: DVDR at ata0-master WDMA2 ad0: 38166MB at ata1-master UDMA100 $ vmstat -i interrupt total rate irq1: pcm0 1 0 irq61: pcm0 1 0 irq24: ata0 35 0 irq29: ohci2 1 0 irq63: ohci3 ohci+ 6 0 irq39: ata1 915 10 irq40: fwohci0 2 0 irq41: gem0 364 4 Total 1325 15 Here is a full dmesg of the new kernel. In both this kernel and the working Oct 11 kernel, my "aoa" driver for sound is enabled. This is the only modification with respect to a CVS GENERIC kernel. Oct 26 11:39:20 emac6 syslogd: kernel boot file is /boot/kernel/kernel Oct 26 11:39:20 emac6 kernel: Copyright (c) 1992-2008 The FreeBSD Project. Oct 26 11:39:20 emac6 kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Oct 26 11:39:20 emac6 kernel: The Regents of the University of California. All rights reserved. Oct 26 11:39:20 emac6 kernel: FreeBSD is a registered trademark of The FreeBSD Foundation. Oct 26 11:39:20 emac6 kernel: FreeBSD 8.0-CURRENT #57: Sun Oct 26 10:31:37 UTC 2008 Oct 26 11:39:20 emac6 kernel: mtrillo@emac6:/usr/src/sys/powerpc/compile/GENERIC Oct 26 11:39:20 emac6 kernel: WARNING: WITNESS option enabled, expect reduced performance. Oct 26 11:39:20 emac6 kernel: cpu0: Motorola PowerPC 7447A revision 1.1, 1250.00 MHz Oct 26 11:39:20 emac6 kernel: cpu0: HID0 8450c0bc Oct 26 11:39:20 emac6 kernel: real memory = 792965120 (756 MB) Oct 26 11:39:20 emac6 kernel: avail memory = 762540032 (727 MB) Oct 26 11:39:20 emac6 kernel: kbd0 at kbdmux0 Oct 26 11:39:20 emac6 kernel: nexus0: Oct 26 11:39:20 emac6 kernel: unin0: on nexus0 Oct 26 11:39:20 emac6 kernel: unin0: Version 210 Oct 26 11:39:20 emac6 kernel: pcib0: on nexus0 Oct 26 11:39:20 emac6 kernel: pci0: on pcib0 Oct 26 11:39:20 emac6 kernel: vgapci0: port 0x400-0x4ff mem 0x98000000-0x9fffffff,0x90000000-0x9000ffff irq 48 at device 16.0 on pci0 Oct 26 11:39:20 emac6 kernel: pcib1: on nexus0 Oct 26 11:39:20 emac6 kernel: pci1: on pcib1 Oct 26 11:39:20 emac6 kernel: macio0: mem 0x80000000-0x8007ffff at device 23.0 on pci1 Oct 26 11:39:20 emac6 kernel: openpic0: mem 0x40000-0x7ffff on macio0 Oct 26 11:39:20 emac6 kernel: scc0: mem 0x13000-0x13fff,0x8400-0x84ff,0x8500-0x85ff,0x8600-0x86ff,0x8700-0x87ff irq 22,5,6,23,7,8 on macio0 Oct 26 11:39:20 emac6 kernel: scc0: [FILTER] Oct 26 11:39:20 emac6 kernel: scc0: [FILTER] Oct 26 11:39:20 emac6 kernel: uart0: on scc0 Oct 26 11:39:20 emac6 kernel: uart0: [FILTER] Oct 26 11:39:20 emac6 kernel: uart1: on scc0 Oct 26 11:39:20 emac6 kernel: uart1: [FILTER] Oct 26 11:39:20 emac6 kernel: pcm0: mem 0x10000-0x10fff,0x8000-0x80ff,0x8100-0x81ff irq 30,1,2,31,3,4 on macio0 Oct 26 11:39:20 emac6 kernel: interrupting at irq 1 Oct 26 11:39:20 emac6 kernel: pcm0: [ITHREAD] Oct 26 11:39:20 emac6 kernel: GPIO : addr 0x6f Oct 26 11:39:20 emac6 kernel: GPIO : addr 0x70 Oct 26 11:39:20 emac6 kernel: GPIO : addr 0x75 Oct 26 11:39:20 emac6 kernel: interrupting at irq 61 Oct 26 11:39:20 emac6 kernel: pcm0: [ITHREAD] Oct 26 11:39:20 emac6 kernel: GPIO : addr 0x67 Oct 26 11:39:20 emac6 kernel: enabled outputs: HEADPHONE Oct 26 11:39:20 emac6 kernel: resetting codec Oct 26 11:39:20 emac6 kernel: tumbler_write called without I2C? Oct 26 11:39:20 emac6 kernel: pcm_getbuffersize returned 65536 Oct 26 11:39:20 emac6 kernel: aoa_dma_setprd: addr = 13434880, 32 slots Oct 26 11:39:20 emac6 kernel: aoa_chan_setformat: format = 268435488 Oct 26 11:39:20 emac6 kernel: aoa_chan_setspeed: speed = 44100 Oct 26 11:39:20 emac6 kernel: aoa_chan_setformat: format = 268435488 Oct 26 11:39:20 emac6 kernel: aoa_chan_setblocksize: blocksz = 2048, dma->blksz = 2048 Oct 26 11:39:20 emac6 kernel: aoa_chan_setspeed: speed = 44100 Oct 26 11:39:20 emac6 kernel: aoa_chan_setformat: format = 268435488 Oct 26 11:39:20 emac6 kernel: aoa_chan_setblocksize: blocksz = 2048, dma->blksz = 2048 Oct 26 11:39:20 emac6 kernel: aoa_chan_setblocksize: blocksz = 2048, dma->blksz = 2048 Oct 26 11:39:20 emac6 kernel: aoa_chan_setspeed: speed = 44100 Oct 26 11:39:20 emac6 kernel: aoa_chan_setformat: format = 268435488 Oct 26 11:39:20 emac6 kernel: aoa_chan_setblocksize: blocksz = 2048, dma->blksz = 2048 Oct 26 11:39:20 emac6 kernel: kiic0: mem 0x18000-0x18fff irq 26 on macio0 Oct 26 11:39:20 emac6 kernel: ata0 mem 0x20000-0x20fff,0x8800-0x88ff irq 24,12 on macio0 Oct 26 11:39:20 emac6 kernel: ata0: [ITHREAD] Oct 26 11:39:20 emac6 kernel: ohci0: mem 0x80083000-0x80083fff irq 29 at device 26.0 on pci1 Oct 26 11:39:20 emac6 kernel: ohci0: [GIANT-LOCKED] Oct 26 11:39:20 emac6 kernel: ohci0: [ITHREAD] Oct 26 11:39:20 emac6 kernel: usb0: OHCI version 1.0, legacy support Oct 26 11:39:20 emac6 kernel: usb0: on ohci0 Oct 26 11:39:20 emac6 kernel: usb0: USB revision 1.0 Oct 26 11:39:20 emac6 kernel: uhub0: on usb0 Oct 26 11:39:20 emac6 kernel: uhub0: 2 ports with 2 removable, self powered Oct 26 11:39:20 emac6 kernel: ohci1: mem 0x80082000-0x80082fff irq 63 at device 27.0 on pci1 Oct 26 11:39:20 emac6 kernel: ohci1: [GIANT-LOCKED] Oct 26 11:39:20 emac6 kernel: ohci1: [ITHREAD] Oct 26 11:39:20 emac6 kernel: usb1: OHCI version 1.0 Oct 26 11:39:20 emac6 kernel: usb1: on ohci1 Oct 26 11:39:20 emac6 kernel: usb1: USB revision 1.0 Oct 26 11:39:20 emac6 kernel: uhub1: on usb1 Oct 26 11:39:20 emac6 kernel: uhub1: 3 ports with 3 removable, self powered Oct 26 11:39:20 emac6 kernel: ohci2: mem 0x80081000-0x80081fff irq 63 at device 27.1 on pci1 Oct 26 11:39:20 emac6 kernel: ohci2: [GIANT-LOCKED] Oct 26 11:39:20 emac6 kernel: ohci2: [ITHREAD] Oct 26 11:39:20 emac6 kernel: usb2: OHCI version 1.0 Oct 26 11:39:20 emac6 kernel: usb2: on ohci2 Oct 26 11:39:20 emac6 kernel: usb2: USB revision 1.0 Oct 26 11:39:20 emac6 kernel: uhub2: on usb2 Oct 26 11:39:20 emac6 kernel: uhub2: 2 ports with 2 removable, self powered Oct 26 11:39:20 emac6 kernel: ehci0: mem 0x80080000-0x800800ff irq 63 at device 27.2 on pci1 Oct 26 11:39:20 emac6 kernel: ehci0: [GIANT-LOCKED] Oct 26 11:39:20 emac6 kernel: ehci0: [ITHREAD] Oct 26 11:39:20 emac6 kernel: usb3: EHCI version 1.0 Oct 26 11:39:20 emac6 kernel: usb3: companion controllers, 3 ports each: usb1 usb2 Oct 26 11:39:20 emac6 kernel: usb3: on ehci0 Oct 26 11:39:20 emac6 kernel: usb3: USB revision 2.0 Oct 26 11:39:20 emac6 kernel: uhub3: on usb3 Oct 26 11:39:20 emac6 kernel: uhub3: 5 ports with 5 removable, self powered Oct 26 11:39:20 emac6 kernel: pcib2: on nexus0 Oct 26 11:39:20 emac6 kernel: pci2: on pcib2 Oct 26 11:39:20 emac6 kernel: ata1: mem 0xf5004000-0xf5007fff irq 39 at device 13.0 on pci2 Oct 26 11:39:20 emac6 kernel: ata1: [ITHREAD] Oct 26 11:39:20 emac6 kernel: fwohci0: mem 0xf5000000-0xf5000fff irq 40 at device 14.0 on pci2 Oct 26 11:39:20 emac6 kernel: fwohci0: [FILTER] Oct 26 11:39:20 emac6 kernel: fwohci0: OHCI version 1.10 (ROM=0) Oct 26 11:39:20 emac6 kernel: fwohci0: No. of Isochronous channels is 8. Oct 26 11:39:20 emac6 kernel: fwohci0: EUI64 00:0d:93:ff:fe:57:39:60 Oct 26 11:39:20 emac6 kernel: fwohci0: Phy 1394a available S400, 2 ports. Oct 26 11:39:20 emac6 kernel: fwohci0: Link S400, max_rec 2048 bytes. Oct 26 11:39:20 emac6 kernel: firewire0: on fwohci0 Oct 26 11:39:20 emac6 kernel: fwe0: on firewire0 Oct 26 11:39:20 emac6 kernel: if_fwe0: Fake Ethernet address: 02:0d:93:57:39:60 Oct 26 11:39:20 emac6 kernel: fwe0: Ethernet address: 02:0d:93:57:39:60 Oct 26 11:39:20 emac6 kernel: sbp0: on firewire0 Oct 26 11:39:20 emac6 kernel: fwohci0: Initiate bus reset Oct 26 11:39:20 emac6 kernel: fwohci0: BUS reset Oct 26 11:39:20 emac6 kernel: fwohci0: node_id=0xc800ffc0, gen=2, CYCLEMASTER mode Oct 26 11:39:20 emac6 kernel: gem0: mem 0xf5200000-0xf53fffff irq 41 at device 15.0 on pci2 Oct 26 11:39:20 emac6 kernel: miibus0: on gem0 Oct 26 11:39:20 emac6 kernel: bmtphy0: PHY 0 on miibus0 Oct 26 11:39:20 emac6 kernel: bmtphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Oct 26 11:39:20 emac6 kernel: gem0: 10kB RX FIFO, 4kB TX FIFO Oct 26 11:39:20 emac6 kernel: gem0: Ethernet address: 00:0d:93:57:39:60 Oct 26 11:39:20 emac6 kernel: gem0: [ITHREAD] Oct 26 11:39:20 emac6 kernel: sc0: on nexus0 Oct 26 11:39:20 emac6 kernel: sc0: Unknown <16 virtual consoles, flags=0x300> Oct 26 11:39:20 emac6 kernel: uhub4: on uhub1 Oct 26 11:39:20 emac6 kernel: uhub4: 3 ports with 2 removable, bus powered Oct 26 11:39:20 emac6 kernel: ums0: on uhub4 Oct 26 11:39:20 emac6 kernel: ums0: 1 buttons. Oct 26 11:39:20 emac6 kernel: ukbd0: on uhub4 Oct 26 11:39:20 emac6 kernel: kbd1 at ukbd0 Oct 26 11:39:20 emac6 kernel: uhid0: on uhub4 Oct 26 11:39:20 emac6 kernel: Timecounter "decrementer" frequency 41620997 Hz quality 0 Oct 26 11:39:20 emac6 kernel: Timecounters tick every 10.000 msec Oct 26 11:39:20 emac6 kernel: firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) Oct 26 11:39:20 emac6 kernel: firewire0: bus manager 0 (me) Oct 26 11:39:20 emac6 kernel: acd0: DVDR at ata0-master WDMA2 Oct 26 11:39:20 emac6 kernel: ad0: 38166MB at ata1-master UDMA100 Oct 26 11:39:20 emac6 kernel: pcm0: codec: at address 6Ah on kiic0 Oct 26 11:39:20 emac6 kernel: WARNING: WITNESS option enabled, expect reduced performance. Oct 26 11:39:20 emac6 kernel: Trying to mount root from ufs:/dev/ad0s4 Oct 26 11:39:20 emac6 kernel: lock order reversal: Oct 26 11:39:20 emac6 kernel: 1st 0xc41048 user map (user map) @ vm/vm_map.c:3115 Oct 26 11:39:20 emac6 kernel: 2nd 0xe1d7cc ufs (ufs) @ kern/vfs_subr.c:2049 Oct 26 11:39:20 emac6 kernel: KDB: stack backtrace: Oct 26 11:39:20 emac6 kernel: 0xdebaf930: at kdb_backtrace+0x4c Oct 26 11:39:20 emac6 kernel: 0xdebaf950: at _witness_debugger+0x3c Oct 26 11:39:20 emac6 kernel: 0xdebaf970: at witness_checkorder+0x8d0 Oct 26 11:39:20 emac6 kernel: 0xdebaf9d0: at __lockmgr_args+0x23c Oct 26 11:39:20 emac6 kernel: 0xdebafa50: at ffs_lock+0x9c Oct 26 11:39:20 emac6 kernel: 0xdebafa80: at VOP_LOCK1_APV+0xec Oct 26 11:39:20 emac6 kernel: 0xdebafaa0: at _vn_lock+0x84 Oct 26 11:39:20 emac6 kernel: 0xdebafaf0: at vget+0xdc Oct 26 11:39:20 emac6 kernel: 0xdebafb30: at vnode_pager_lock+0x20c Oct 26 11:39:20 emac6 kernel: 0xdebafb90: at vm_fault+0x218 Oct 26 11:39:20 emac6 kernel: 0xdebafca0: at trap_pfault+0x128 Oct 26 11:39:20 emac6 kernel: 0xdebafce0: at trap+0x1ac Oct 26 11:39:20 emac6 kernel: 0xdebafda0: at powerpc_interrupt+0x15c Oct 26 11:39:20 emac6 kernel: 0xdebafdd0: user ISI trap by 0x1815a04: srr1=0x4000d032 Oct 26 11:39:20 emac6 kernel: r1=0x7fffdee0 cr=0x24000048 xer=0 ctr=0 Oct 26 11:39:20 emac6 root: /etc/rc: WARNING: Dump device does not exist. Savecore not run. Oct 26 11:39:27 emac6 kernel: ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=3950368 Oct 26 11:39:37 emac6 kernel: ad0: TIMEOUT - READ_DMA retrying (0 retries left) LBA=3950368 Oct 26 11:39:37 emac6 kernel: ad0: FAILURE - READ_DMA timed out LBA=3950368 Oct 26 11:39:37 emac6 kernel: g_vfs_done():ad0s4[READ(offset=1745207296, length=114688)]error = 5 Thanks! Marco From marcotrillo at gmail.com Sun Oct 26 12:47:15 2008 From: marcotrillo at gmail.com (Marco Trillo) Date: Sun Oct 26 12:47:21 2008 Subject: ATA DMA problems with recent -current In-Reply-To: References: Message-ID: Hi, On Sun, Oct 26, 2008 at 1:17 PM, Marco Trillo wrote: > Here is a full dmesg of the new kernel. In both this kernel and the > working Oct 11 kernel, my "aoa" driver for sound is enabled. This is > the only modification with respect to a CVS GENERIC kernel. Hmm... I forgot to mention the changes to the 'ldscript.powerpc' file, which are required to get the kernel to boot in this machine. I think it's possible that I have a messed up source tree. Or a messed up "compile/" object directory. I'm going to remove the "compile/GENERIC" directory and get a fresh source tree from CVS, without any modifications (except the 'ldscript.powerpc' file which I mentioned above); and see if the problems persist. Thanks, Marco From marcotrillo at gmail.com Sun Oct 26 15:19:23 2008 From: marcotrillo at gmail.com (Marco Trillo) Date: Sun Oct 26 15:19:36 2008 Subject: ATA DMA problems with recent -current In-Reply-To: References: Message-ID: Hi, On Sun, Oct 26, 2008 at 1:47 PM, Marco Trillo wrote: > On Sun, Oct 26, 2008 at 1:17 PM, Marco Trillo wrote: >> Here is a full dmesg of the new kernel. In both this kernel and the >> working Oct 11 kernel, my "aoa" driver for sound is enabled. This is >> the only modification with respect to a CVS GENERIC kernel. > > Hmm... I forgot to mention the changes to the 'ldscript.powerpc' file, > which are required to get the kernel to boot in this machine. > > > I think it's possible that I have a messed up source tree. Or a messed > up "compile/" object directory. > > I'm going to remove the "compile/GENERIC" directory and get a fresh > source tree from CVS, without any modifications (except the > 'ldscript.powerpc' file which I mentioned above); and see if the > problems persist. Done that; cleaned the object directory and compiled a new kernel from scratch, without 'aoa' driver or other modifications, but it didn't make a difference - I still get the DMA timeouts. Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.0-CURRENT #0: Sun Oct 26 13:16:40 UTC 2008 mtrillo@emac6:/usr/src/sys/powerpc/compile/GENERIC ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=30824128 ad0: TIMEOUT - READ_DMA retrying (0 retries left) LBA=30824128 ad0: FAILURE - READ_DMA timed out LBA=30824128 g_vfs_done():ad0s4[READ(offset=15504572416, length=114688)]error = 5 Thanks, Marco From nwhitehorn at freebsd.org Sun Oct 26 15:30:15 2008 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Sun Oct 26 15:30:45 2008 Subject: ATA DMA problems with recent -current In-Reply-To: References: Message-ID: <49048D19.7070309@freebsd.org> Marco Trillo wrote: > Hi all, > > I just updated my -current kernel to today sources -- the previous > kernel was from Oct 11. With the new kernel I'm getting ad0 ATA DMA > timeouts, which get worse when I stress the drive. > The only thing that changed since 11 Oct was that I redid the PCI handling by importing sparc64's architecture. This *should* have changed nothing, since I just reshuffled some code, but apparently it didn't. One of the few actual changes was that ata_kauai now attaches only to the first IRQ (39) instead of both OF IRQs (39 and 1). However, it never used the second one, so it should have changed nothing. Things to try: - Make ata_kauai add IRQ 1 to its resource list again, just like it hardcodes 39. - IRQ 1 is shared with the i2s controller. Try disabling it? I'm pretty confused about how it is that things have broken, though. -Nathan From marcotrillo at gmail.com Sun Oct 26 15:57:54 2008 From: marcotrillo at gmail.com (Marco Trillo) Date: Sun Oct 26 15:58:01 2008 Subject: ATA DMA problems with recent -current In-Reply-To: <49048D19.7070309@freebsd.org> References: <49048D19.7070309@freebsd.org> Message-ID: Hi, On Sun, Oct 26, 2008 at 4:30 PM, Nathan Whitehorn wrote: >> Hi all, >> >> I just updated my -current kernel to today sources -- the previous >> kernel was from Oct 11. With the new kernel I'm getting ad0 ATA DMA >> timeouts, which get worse when I stress the drive. >> > > The only thing that changed since 11 Oct was that I redid the PCI handling > by importing sparc64's architecture. This *should* have changed nothing, > since I just reshuffled some code, but apparently it didn't. One of the few > actual changes was that ata_kauai now attaches only to the first IRQ (39) > instead of both OF IRQs (39 and 1). However, it never used the second one, > so it should have changed nothing. Things to try: > > - Make ata_kauai add IRQ 1 to its resource list again, just like it > hardcodes 39. > - IRQ 1 is shared with the i2s controller. Try disabling it? > > I'm pretty confused about how it is that things have broken, though. I removed the i2s driver, but got the same results. However I think I have located the source of the problem. I diffed the 'ident' output on both kernels and noticed something which seemed related: - $FreeBSD: src/sys/dev/ata/ata-dma.c,v 1.157 2008/10/09 12:56:57 sos Exp $ + $FreeBSD: src/sys/dev/ata/ata-dma.c,v 1.158 2008/10/21 18:51:55 jhb Exp $ Then I reverted ata-dma.c to revision 1.157. It works! I get no more timeouts. Currently it's untarring the ports.tar.gz file quite happily! Thanks, Marco From nwhitehorn at freebsd.org Sun Oct 26 16:00:57 2008 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Sun Oct 26 16:01:07 2008 Subject: ATA DMA problems with recent -current In-Reply-To: References: <49048D19.7070309@freebsd.org> Message-ID: <49049447.4070401@freebsd.org> Marco Trillo wrote: > Hi, > > On Sun, Oct 26, 2008 at 4:30 PM, Nathan Whitehorn > wrote: >>> Hi all, >>> >>> I just updated my -current kernel to today sources -- the previous >>> kernel was from Oct 11. With the new kernel I'm getting ad0 ATA DMA >>> timeouts, which get worse when I stress the drive. >>> >> The only thing that changed since 11 Oct was that I redid the PCI handling >> by importing sparc64's architecture. This *should* have changed nothing, >> since I just reshuffled some code, but apparently it didn't. One of the few >> actual changes was that ata_kauai now attaches only to the first IRQ (39) >> instead of both OF IRQs (39 and 1). However, it never used the second one, >> so it should have changed nothing. Things to try: >> >> - Make ata_kauai add IRQ 1 to its resource list again, just like it >> hardcodes 39. >> - IRQ 1 is shared with the i2s controller. Try disabling it? >> >> I'm pretty confused about how it is that things have broken, though. > > I removed the i2s driver, but got the same results. > > However I think I have located the source of the problem. > > I diffed the 'ident' output on both kernels and noticed something > which seemed related: > > - $FreeBSD: src/sys/dev/ata/ata-dma.c,v 1.157 2008/10/09 12:56:57 sos Exp $ > + $FreeBSD: src/sys/dev/ata/ata-dma.c,v 1.158 2008/10/21 18:51:55 jhb Exp $ > > Then I reverted ata-dma.c to revision 1.157. It works! I get no more > timeouts. Currently it's untarring the ports.tar.gz file quite > happily! Intriguing... that change was a typo fix. I guess we have to limit the maximum ATA DMA size for our controllers. I'll look around and commit a real fix later today. -Nathan From andreast-list at fgznet.ch Sun Oct 26 21:25:23 2008 From: andreast-list at fgznet.ch (Andreas Tobler) Date: Sun Oct 26 21:25:35 2008 Subject: adb feedback In-Reply-To: <48EF9B58.3050208@fgznet.ch> References: <48EF9B58.3050208@fgznet.ch> Message-ID: <4904E03F.40308@fgznet.ch> Andreas Tobler wrote: > What a feeling to type on the PowerBook's own keyboard!!! > Thanks a lot! > > Oct 10 15:16:50 wolfram kernel: pmu0: mem > 0x16000-0x17fff irq 25 on macio0 > Oct 10 15:16:50 wolfram kernel: pmu0: [ITHREAD] > Oct 10 15:16:50 wolfram kernel: adb0: on pmu0 > Oct 10 15:16:50 wolfram kernel: akbd0: at device 2 on adb0 > Oct 10 15:16:50 wolfram kernel: kbd1 at akbd0 > Oct 10 15:16:50 wolfram kernel: ams0: at device 3 on adb0 > Oct 10 15:16:50 wolfram kernel: ams0: 4-button 400-dpi Unknown Pointing > Device Thanks for committing this one! http://docs.freebsd.org/cgi/getmsg.cgi?fetch=106841+0+current/svn-src-head Will try soon. Regards, Andreas From horst at sxemacs.org Sun Oct 26 21:43:20 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Sun Oct 26 21:43:26 2008 Subject: aoa.c driver for Screamer ... In-Reply-To: References: <48FE33D7.3080505@fgznet.ch> <1224657584.10591.72.camel@horst-tla> <1224668347.10591.76.camel@horst-tla> <1224788068.10591.105.camel@horst-tla> Message-ID: <1225057546.10591.127.camel@horst-tla> On Fri, 2008-10-24 at 10:15 +0200, Marco Trillo wrote: > Hi, > Oops, that's because it requires the latest DBDMA code, which has not > yet been MFCed to the 7.x branch. > > The solution is to update the files > - /usr/src/sys/powerpc/powermac/dbdma.c > - /usr/src/sys/powerpc/powermac/dbdmavar.h > - /usr/src/sys/powerpc/include/dbdma.h > to the latest versions from -current. > > They can be downloaded from CVSweb: > > > > > > > Hope that helps, and thanks for your interest in the driver! > > Marco [ ... several patches later ... ] ... How much of this kernel will have to be -CURRENT to get it to build and work? Next problem has been hit :) ===> bm (all) cc -Os -pipe -mcpu=7400 -mtune=7400 -maltivec -mabi=altivec -Wno-error -fno-strict-aliasing -D_KERNEL -DKLD_MODULE -std=c99 -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj/usr/src/sys/POWERMAC/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -g -mlongcall -fno-omit-frame-pointer -I/usr/obj/usr/src/sys/POWERMAC -msoft-float -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c /usr/src/sys/modules/bm/../../dev/bm/if_bm.c /usr/src/sys/modules/bm/../../dev/bm/if_bm.c: In function 'bm_attach': /usr/src/sys/modules/bm/../../dev/bm/if_bm.c:492: warning: passing argument 2 of 'dbdma_allocate_channel' makes integer from pointer without a cast /usr/src/sys/modules/bm/../../dev/bm/if_bm.c:492: warning: passing argument 3 of 'dbdma_allocate_channel' makes pointer from integer without a cast /usr/src/sys/modules/bm/../../dev/bm/if_bm.c:492: warning: passing argument 4 of 'dbdma_allocate_channel' makes integer from pointer without a cast /usr/src/sys/modules/bm/../../dev/bm/if_bm.c:492: error: too few arguments to function 'dbdma_allocate_channel' /usr/src/sys/modules/bm/../../dev/bm/if_bm.c:494: warning: passing argument 2 of 'dbdma_allocate_channel' makes integer from pointer without a cast /usr/src/sys/modules/bm/../../dev/bm/if_bm.c:494: warning: passing argument 3 of 'dbdma_allocate_channel' makes pointer from integer without a cast /usr/src/sys/modules/bm/../../dev/bm/if_bm.c:494: warning: passing argument 4 of 'dbdma_allocate_channel' makes integer from pointer without a cast /usr/src/sys/modules/bm/../../dev/bm/if_bm.c:494: error: too few arguments to function 'dbdma_allocate_channel' *** Error code 1 Stop in /usr/src/sys/modules/bm. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/obj/usr/src/sys/POWERMAC. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. [ bsdbox ] [ root ] [ /usr/src ] ==> Looks like the new dbdma code is a tad tits-uppish :( Thanks, -- Horst (btw, cc'ed back to list in case anyone knows what to do about the dbdma break) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081026/617e6c1f/attachment.pgp From bugmaster at FreeBSD.org Mon Oct 27 11:07:19 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Oct 27 11:08:48 2008 Subject: Current problem reports assigned to freebsd-ppc@FreeBSD.org Message-ID: <200810271107.m9RB7IKY002061@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- a power/121407 ppc [panic] Won't boot up; strange error message. o power/112435 ppc [nexus] [patch] Update nexus children to use ofw_bus f o power/111296 ppc [kernel] [patch] [request] Support IMISS, DLMISS an DS o power/93203 ppc FreeBSD PPC Can't Write to Partitions. 4 problems total. From tinderbox at freebsd.org Mon Oct 27 11:43:07 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Mon Oct 27 11:43:14 2008 Subject: [releng_7_1 tinderbox] failure on powerpc/powerpc Message-ID: <20081025021734.CCEFE1B507A@freebsd-stable.sentex.ca> TB --- 2008-10-25 02:17:27 - tinderbox 2.4 running on freebsd-stable.sentex.ca TB --- 2008-10-25 02:17:27 - starting RELENG_7_1 tinderbox run for powerpc/powerpc TB --- 2008-10-25 02:17:27 - cleaning the object tree TB --- 2008-10-25 02:17:27 - cvsupping the source tree TB --- 2008-10-25 02:17:27 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7_1/powerpc/powerpc/supfile TB --- 2008-10-25 02:17:34 - building world (CFLAGS=-O2 -pipe) TB --- 2008-10-25 02:17:34 - cd /src TB --- 2008-10-25 02:17:34 - ERROR: /src: No such file or directory TB --- 2008-10-25 02:17:34 - tinderbox aborted TB --- 1.37 user 0.12 system 7.79 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7_1-powerpc-powerpc.full _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From tinderbox at freebsd.org Mon Oct 27 12:03:13 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Mon Oct 27 12:04:02 2008 Subject: [releng_7_1 tinderbox] failure on powerpc/powerpc Message-ID: <20081024135741.153441B507A@freebsd-stable.sentex.ca> TB --- 2008-10-24 13:57:34 - tinderbox 2.4 running on freebsd-stable.sentex.ca TB --- 2008-10-24 13:57:34 - starting RELENG_7_1 tinderbox run for powerpc/powerpc TB --- 2008-10-24 13:57:34 - cleaning the object tree TB --- 2008-10-24 13:57:34 - cvsupping the source tree TB --- 2008-10-24 13:57:34 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7_1/powerpc/powerpc/supfile TB --- 2008-10-24 13:57:41 - building world (CFLAGS=-O2 -pipe) TB --- 2008-10-24 13:57:41 - cd /src TB --- 2008-10-24 13:57:41 - ERROR: /src: No such file or directory TB --- 2008-10-24 13:57:41 - tinderbox aborted TB --- 1.41 user 0.06 system 6.48 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7_1-powerpc-powerpc.full _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From tinderbox at freebsd.org Mon Oct 27 18:38:07 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Mon Oct 27 18:38:23 2008 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20081027183804.2541073039@freebsd-current.sentex.ca> TB --- 2008-10-27 17:17:16 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-10-27 17:17:16 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-10-27 17:17:16 - cleaning the object tree TB --- 2008-10-27 17:17:55 - cvsupping the source tree TB --- 2008-10-27 17:17:55 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-10-27 17:18:02 - building world (CFLAGS=-O -pipe) TB --- 2008-10-27 17:18:02 - cd /src TB --- 2008-10-27 17:18:02 - /usr/bin/make -B buildworld >>> World build started on Mon Oct 27 17:18:04 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Mon Oct 27 18:30:01 UTC 2008 TB --- 2008-10-27 18:30:01 - generating LINT kernel config TB --- 2008-10-27 18:30:01 - cd /src/sys/powerpc/conf TB --- 2008-10-27 18:30:01 - /usr/bin/make -B LINT TB --- 2008-10-27 18:30:01 - building LINT kernel (COPTFLAGS=) TB --- 2008-10-27 18:30:01 - cd /src TB --- 2008-10-27 18:30:01 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Oct 27 18:30:01 UTC 2008 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] mac_bsdextended.o(.data+0x560): undefined reference to `ugidfw_check_setacl_vnode' mac_bsdextended.o(.data+0x564): undefined reference to `ugidfw_vnode_check_setextattr' mac_bsdextended.o(.data+0x568): undefined reference to `ugidfw_vnode_check_setflags' mac_bsdextended.o(.data+0x56c): undefined reference to `ugidfw_vnode_check_setmode' mac_bsdextended.o(.data+0x570): undefined reference to `ugidfw_vnode_check_setowner' mac_bsdextended.o(.data+0x574): undefined reference to `ugidfw_vnode_check_setutimes' mac_bsdextended.o(.data+0x578): undefined reference to `ugidfw_vnode_check_stat' mac_bsdextended.o(.data+0x57c): undefined reference to `ugidfw_vnode_check_unlink' *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-10-27 18:38:03 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-10-27 18:38:03 - ERROR: failed to build lint kernel TB --- 2008-10-27 18:38:03 - tinderbox aborted TB --- 3489.67 user 414.66 system 4847.20 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From tinderbox at freebsd.org Tue Oct 28 01:30:56 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Tue Oct 28 01:31:03 2008 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20081028013052.9326673039@freebsd-current.sentex.ca> TB --- 2008-10-28 00:10:46 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-10-28 00:10:46 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-10-28 00:10:46 - cleaning the object tree TB --- 2008-10-28 00:11:10 - cvsupping the source tree TB --- 2008-10-28 00:11:10 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-10-28 00:11:18 - building world (CFLAGS=-O -pipe) TB --- 2008-10-28 00:11:18 - cd /src TB --- 2008-10-28 00:11:18 - /usr/bin/make -B buildworld >>> World build started on Tue Oct 28 00:11:19 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Tue Oct 28 01:25:33 UTC 2008 TB --- 2008-10-28 01:25:33 - generating LINT kernel config TB --- 2008-10-28 01:25:33 - cd /src/sys/powerpc/conf TB --- 2008-10-28 01:25:33 - /usr/bin/make -B LINT TB --- 2008-10-28 01:25:33 - building LINT kernel (COPTFLAGS=) TB --- 2008-10-28 01:25:33 - cd /src TB --- 2008-10-28 01:25:33 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue Oct 28 01:25:33 UTC 2008 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] /src/sys/dev/usb/u3g.c:495: error: 'struct u3gstub_softc' has no member named 'dev' /src/sys/dev/usb/u3g.c:502: error: 'struct u3gstub_softc' has no member named 'dev' /src/sys/dev/usb/u3g.c:509: error: 'struct u3gstub_softc' has no member named 'dev' /src/sys/dev/usb/u3g.c:457: warning: unused variable 'self' /src/sys/dev/usb/u3g.c: In function 'u3gstub_attach': /src/sys/dev/usb/u3g.c:587: error: 'struct u3gstub_softc' has no member named 'dev' /src/sys/dev/usb/u3g.c:591: error: 'struct u3gstub_softc' has no member named 'dev' /src/sys/dev/usb/u3g.c:595: error: 'struct u3gstub_softc' has no member named 'dev' *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-10-28 01:30:52 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-10-28 01:30:52 - ERROR: failed to build lint kernel TB --- 2008-10-28 01:30:52 - tinderbox aborted TB --- 3363.85 user 399.55 system 4806.42 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From tinderbox at freebsd.org Tue Oct 28 07:30:58 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Tue Oct 28 07:31:11 2008 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20081028073054.B22D673039@freebsd-current.sentex.ca> TB --- 2008-10-28 06:12:13 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-10-28 06:12:13 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-10-28 06:12:13 - cleaning the object tree TB --- 2008-10-28 06:12:37 - cvsupping the source tree TB --- 2008-10-28 06:12:37 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-10-28 06:12:43 - building world (CFLAGS=-O -pipe) TB --- 2008-10-28 06:12:43 - cd /src TB --- 2008-10-28 06:12:43 - /usr/bin/make -B buildworld >>> World build started on Tue Oct 28 06:12:44 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Tue Oct 28 07:25:42 UTC 2008 TB --- 2008-10-28 07:25:42 - generating LINT kernel config TB --- 2008-10-28 07:25:42 - cd /src/sys/powerpc/conf TB --- 2008-10-28 07:25:42 - /usr/bin/make -B LINT TB --- 2008-10-28 07:25:42 - building LINT kernel (COPTFLAGS=) TB --- 2008-10-28 07:25:42 - cd /src TB --- 2008-10-28 07:25:42 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue Oct 28 07:25:42 UTC 2008 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] /src/sys/dev/usb/u3g.c:495: error: 'struct u3gstub_softc' has no member named 'dev' /src/sys/dev/usb/u3g.c:502: error: 'struct u3gstub_softc' has no member named 'dev' /src/sys/dev/usb/u3g.c:509: error: 'struct u3gstub_softc' has no member named 'dev' /src/sys/dev/usb/u3g.c:457: warning: unused variable 'self' /src/sys/dev/usb/u3g.c: In function 'u3gstub_attach': /src/sys/dev/usb/u3g.c:587: error: 'struct u3gstub_softc' has no member named 'dev' /src/sys/dev/usb/u3g.c:591: error: 'struct u3gstub_softc' has no member named 'dev' /src/sys/dev/usb/u3g.c:595: error: 'struct u3gstub_softc' has no member named 'dev' *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-10-28 07:30:54 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-10-28 07:30:54 - ERROR: failed to build lint kernel TB --- 2008-10-28 07:30:54 - tinderbox aborted TB --- 3362.02 user 400.15 system 4720.98 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From andreast-list at fgznet.ch Tue Oct 28 21:43:36 2008 From: andreast-list at fgznet.ch (Andreas Tobler) Date: Tue Oct 28 21:44:03 2008 Subject: ATA DMA problems with recent -current In-Reply-To: <49049447.4070401@freebsd.org> References: <49048D19.7070309@freebsd.org> <49049447.4070401@freebsd.org> Message-ID: <49076462.9020406@fgznet.ch> Hi, Nathan Whitehorn wrote: >> Then I reverted ata-dma.c to revision 1.157. It works! I get no more >> timeouts. Currently it's untarring the ports.tar.gz file quite >> happily! > > Intriguing... that change was a typo fix. I guess we have to limit the > maximum ATA DMA size for our controllers. I'll look around and commit a > real fix later today. I saw you committed something to ata_kauai.c. And in the commit log it sounds to me that the real problem is not solved yet, correct? I built yesterday on my imac and see these errors: ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=29430560 ad0: TIMEOUT - READ_DMA retrying (0 retries left) LBA=29430560 ad0: FAILURE - READ_DMA timed out LBA=29430560 I have wired my ata to macio. Thanks, Andreas From nwhitehorn at freebsd.org Tue Oct 28 22:10:59 2008 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Tue Oct 28 22:11:36 2008 Subject: ATA DMA problems with recent -current In-Reply-To: <49076462.9020406@fgznet.ch> References: <49048D19.7070309@freebsd.org> <49049447.4070401@freebsd.org> <49076462.9020406@fgznet.ch> Message-ID: <49078DDB.30904@freebsd.org> Andreas Tobler wrote: > Hi, > > Nathan Whitehorn wrote: > >>> Then I reverted ata-dma.c to revision 1.157. It works! I get no more >>> timeouts. Currently it's untarring the ports.tar.gz file quite >>> happily! >> >> Intriguing... that change was a typo fix. I guess we have to limit >> the maximum ATA DMA size for our controllers. I'll look around and >> commit a real fix later today. > > I saw you committed something to ata_kauai.c. And in the commit log it > sounds to me that the real problem is not solved yet, correct? I just fixed this about 5 minutes ago -- yesterday's patch to ata_kauai was unrelated. -Nathan From andreast-list at fgznet.ch Tue Oct 28 22:13:38 2008 From: andreast-list at fgznet.ch (Andreas Tobler) Date: Tue Oct 28 22:13:46 2008 Subject: ATA DMA problems with recent -current In-Reply-To: <49078DDB.30904@freebsd.org> References: <49048D19.7070309@freebsd.org> <49049447.4070401@freebsd.org> <49076462.9020406@fgznet.ch> <49078DDB.30904@freebsd.org> Message-ID: <49078E8F.1030105@fgznet.ch> Nathan Whitehorn wrote: > Andreas Tobler wrote: >> Hi, >> >> Nathan Whitehorn wrote: >> >>>> Then I reverted ata-dma.c to revision 1.157. It works! I get no more >>>> timeouts. Currently it's untarring the ports.tar.gz file quite >>>> happily! >>> >>> Intriguing... that change was a typo fix. I guess we have to limit >>> the maximum ATA DMA size for our controllers. I'll look around and >>> commit a real fix later today. >> >> I saw you committed something to ata_kauai.c. And in the commit log it >> sounds to me that the real problem is not solved yet, correct? > I just fixed this about 5 minutes ago -- yesterday's patch to ata_kauai > was unrelated. Whee, great. Will test and report asap! Thanks, Andreas From tinderbox at freebsd.org Wed Oct 29 11:43:42 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Wed Oct 29 11:43:49 2008 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20081029114339.E296073039@freebsd-current.sentex.ca> TB --- 2008-10-29 10:25:03 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-10-29 10:25:03 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-10-29 10:25:03 - cleaning the object tree TB --- 2008-10-29 10:25:33 - cvsupping the source tree TB --- 2008-10-29 10:25:33 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-10-29 10:25:39 - building world (CFLAGS=-O -pipe) TB --- 2008-10-29 10:25:39 - cd /src TB --- 2008-10-29 10:25:39 - /usr/bin/make -B buildworld >>> World build started on Wed Oct 29 10:25:40 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Wed Oct 29 11:38:13 UTC 2008 TB --- 2008-10-29 11:38:13 - generating LINT kernel config TB --- 2008-10-29 11:38:13 - cd /src/sys/powerpc/conf TB --- 2008-10-29 11:38:13 - /usr/bin/make -B LINT TB --- 2008-10-29 11:38:13 - building LINT kernel (COPTFLAGS=) TB --- 2008-10-29 11:38:13 - cd /src TB --- 2008-10-29 11:38:13 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Wed Oct 29 11:38:14 UTC 2008 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/dev/usb/ohci_pci.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/dev/usb/sl811hs.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/dev/usb/slhci_pccard.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/dev/usb/uark.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/dev/usb/u3g.c /src/sys/dev/usb/u3g.c:54:1: error: "U3G_DEBUG" redefined In file included from /src/sys/dev/usb/u3g.c:50: ./opt_u3g.h:1:1: error: this is the location of the previous definition *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-10-29 11:43:39 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-10-29 11:43:39 - ERROR: failed to build lint kernel TB --- 2008-10-29 11:43:39 - tinderbox aborted TB --- 3357.40 user 403.41 system 4716.80 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From ed at 80386.nl Wed Oct 29 19:05:58 2008 From: ed at 80386.nl (Ed Schouten) Date: Wed Oct 29 19:08:19 2008 Subject: FreeBSD on my old rusty PowerBook 12" Message-ID: <20081029190724.GH1165@hoeg.nl> Hello all, A couple of days ago I saw a commit flash by, which added ADB support to FreeBSD. This means I can finally use FreeBSD on my old PowerBook 12", which is doing nothing right now. I tried to install FreeBSD on the system and it somewhat works, but I think I need to do something differently to get it working properly. I downloaded the 200810 snapshot, which does not support ADB, so I'm using an USB keyboard right now. Good enough. When I get into the installer, it seems there is some kind of hard-coded disk layout. I only have ad0s2 and ad0s3, where ad0s2 is 128 MB and ad0s3 is the rest of the disk. I can't create any more partitions. So right now I've put / on ad0s2 and /usr on ad0s3, which is pretty awful. About boot loaders: I just booted from the harddisk by running in the ofw console: boot cd:\boot\loader hd:2 But I want to have a boot loader on the harddisk itself. I read something about putting a HFS partition on the disk and storing a file in it? Is that what ad0s2 is for? Sorry if I'm asking silly questions, but this is the first time I installed FreeBSD on something different than {i386,amd64,sparc64}. Thanks! -- Ed Schouten WWW: http://80386.nl/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081029/ee7c8036/attachment.pgp From nwhitehorn at freebsd.org Wed Oct 29 19:23:57 2008 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Wed Oct 29 19:24:03 2008 Subject: FreeBSD on my old rusty PowerBook 12" In-Reply-To: <20081029190724.GH1165@hoeg.nl> References: <20081029190724.GH1165@hoeg.nl> Message-ID: <4908B834.4030805@freebsd.org> Ed Schouten wrote: > Hello all, > > A couple of days ago I saw a commit flash by, which added ADB support to > FreeBSD. This means I can finally use FreeBSD on my old PowerBook 12", > which is doing nothing right now. > Welcome to PPC! The introduction of the MPsafe TTY layer was what fixed the last locking bugs in akbd that I hadn't managed to track down, so thanks :) > I tried to install FreeBSD on the system and it somewhat works, but I > think I need to do something differently to get it working properly. > > I downloaded the 200810 snapshot, which does not support ADB, so I'm > using an USB keyboard right now. Good enough. When I get into the > installer, it seems there is some kind of hard-coded disk layout. I only > have ad0s2 and ad0s3, where ad0s2 is 128 MB and ad0s3 is the rest of the > disk. I can't create any more partitions. So right now I've put / on > ad0s2 and /usr on ad0s3, which is pretty awful. > Sysinstall doesn't (currently) have the ability to modify APM layouts. gpart does. This should be fixed. The result is that sysinstall just uses whatever partitions happen to be on your disk already. > About boot loaders: I just booted from the harddisk by running in the > ofw console: > > boot cd:\boot\loader hd:2 > > But I want to have a boot loader on the harddisk itself. I read > something about putting a HFS partition on the disk and storing a file > in it? Is that what ad0s2 is for? > I have a hack in head to solve this. If you rebuild world, you will get a /boot/boot1.hfs. This is a little (800 K) HFS partition with a port of the sparc64 boot1 in it, which you can dd to an 800 K partition to get OFW to boot your machine. However, sysinstall doesn't know about this yet either. You can make this and your regular FreeBSD partitions with gpart, then use dd and boot1.hfs to get a bootable system with sane partitioning. -Nathan From ed at 80386.nl Wed Oct 29 20:03:19 2008 From: ed at 80386.nl (Ed Schouten) Date: Wed Oct 29 20:03:25 2008 Subject: FreeBSD on my old rusty PowerBook 12" In-Reply-To: <4908B834.4030805@freebsd.org> References: <20081029190724.GH1165@hoeg.nl> <4908B834.4030805@freebsd.org> Message-ID: <20081029200443.GI1165@hoeg.nl> Hello Nathan, * Nathan Whitehorn wrote: > Ed Schouten wrote: >> Hello all, >> >> A couple of days ago I saw a commit flash by, which added ADB support to >> FreeBSD. This means I can finally use FreeBSD on my old PowerBook 12", >> which is doing nothing right now. >> > Welcome to PPC! The introduction of the MPsafe TTY layer was what fixed > the last locking bugs in akbd that I hadn't managed to track down, so > thanks :) That's very great to hear! The TTY layer was I guess one of the last remaining core components of the kernel that exclusively used Giant, so getting the graphics/input layers fixed up should become a lot more easy now. >> I tried to install FreeBSD on the system and it somewhat works, but I >> think I need to do something differently to get it working properly. >> >> I downloaded the 200810 snapshot, which does not support ADB, so I'm >> using an USB keyboard right now. Good enough. When I get into the >> installer, it seems there is some kind of hard-coded disk layout. I only >> have ad0s2 and ad0s3, where ad0s2 is 128 MB and ad0s3 is the rest of the >> disk. I can't create any more partitions. So right now I've put / on >> ad0s2 and /usr on ad0s3, which is pretty awful. >> > Sysinstall doesn't (currently) have the ability to modify APM layouts. > gpart does. This should be fixed. The result is that sysinstall just > uses whatever partitions happen to be on your disk already. >> About boot loaders: I just booted from the harddisk by running in the >> ofw console: >> >> boot cd:\boot\loader hd:2 >> >> But I want to have a boot loader on the harddisk itself. I read >> something about putting a HFS partition on the disk and storing a file >> in it? Is that what ad0s2 is for? >> > I have a hack in head to solve this. If you rebuild world, you will get > a /boot/boot1.hfs. This is a little (800 K) HFS partition with a port of > the sparc64 boot1 in it, which you can dd to an 800 K partition to get > OFW to boot your machine. However, sysinstall doesn't know about this > yet either. You can make this and your regular FreeBSD partitions with > gpart, then use dd and boot1.hfs to get a bootable system with sane > partitioning. That sounds great. Unfortunately I can't find a CD image which has a fixit shell on it (there are no fixit disks?) so I think I can't properly partition my harddisk with gpart right now. You happen to know where I can find a FreeBSD PPC disc which allows me to do this? Thanks! -- Ed Schouten WWW: http://80386.nl/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081029/a8086059/attachment.pgp From horst at sxemacs.org Wed Oct 29 20:11:26 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Wed Oct 29 20:11:33 2008 Subject: FreeBSD on my old rusty PowerBook 12" In-Reply-To: <20081029200443.GI1165@hoeg.nl> References: <20081029190724.GH1165@hoeg.nl> <4908B834.4030805@freebsd.org> <20081029200443.GI1165@hoeg.nl> Message-ID: <1225311181.10591.145.camel@horst-tla> On Wed, 2008-10-29 at 21:04 +0100, Ed Schouten wrote: > That sounds great. Unfortunately I can't find a CD image which has a > fixit shell on it (there are no fixit disks?) so I think I can't > properly partition my harddisk with gpart right now. You happen to know > where I can find a FreeBSD PPC disc which allows me to do this? Thanks! I don't believe such a disc exists for PowerPC. You might try a linux livecd like finnix-ppc which was what I used, as it has GNU Parted which _will_ set up your partitions properly. Alternatively you could boot into OSX with installer disc 1 and use the Disk Utility. It doesn't matter what type of partition is what just as long as you have that small HFS one (which the dd image will take care of anyway). Then just sysinstall as normal. Happy BSDing on your mac! -- Horst. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081029/a9c48052/attachment.pgp From ross at grinz.com Wed Oct 29 20:16:28 2008 From: ross at grinz.com (Ross Gohlke) Date: Wed Oct 29 20:16:35 2008 Subject: FreeBSD on my old rusty PowerBook 12" In-Reply-To: <20081029190724.GH1165@hoeg.nl> References: <20081029190724.GH1165@hoeg.nl> Message-ID: <4908C120.3010508@grinz.com> Ed Schouten wrote: > Hello all, > > A couple of days ago I saw a commit flash by, which added ADB support to > FreeBSD. This means I can finally use FreeBSD on my old PowerBook 12", > which is doing nothing right now. > > I tried to install FreeBSD on the system and it somewhat works, but I > think I need to do something differently to get it working properly. > > I downloaded the 200810 snapshot, which does not support ADB, so I'm > using an USB keyboard right now. Good enough. When I get into the > installer, it seems there is some kind of hard-coded disk layout. I only > have ad0s2 and ad0s3, where ad0s2 is 128 MB and ad0s3 is the rest of the > disk. I can't create any more partitions. So right now I've put / on > ad0s2 and /usr on ad0s3, which is pretty awful. > > About boot loaders: I just booted from the harddisk by running in the > ofw console: > > boot cd:\boot\loader hd:2 > > But I want to have a boot loader on the harddisk itself. I read > something about putting a HFS partition on the disk and storing a file > in it? Is that what ad0s2 is for? > > Sorry if I'm asking silly questions, but this is the first time I > installed FreeBSD on something different than {i386,amd64,sparc64}. > Thanks! > Do you have an old Mac OS X Installer disc? If so, it contains Disk Utility, which will allow you to partition the drive, creating a small HFS partition and as many UFS(2) partitions as you want. You will need to know the identities of each partition when you get to sysinstall. You can do this in Disk Utility by selecting each new partition and clicking Info. Older versions (10.1, 10.2) of OS X might use UFS, I'm pretty sure newer versions use UFS2. Regardless, Disk Utility simply calls it UNIX File System. This is the first I've heard of ADB support, and I don't own a USB keyboard; I used Disk Utility in Tiger (10.4) to create a dual-boot drive, so the HFS partition wasn't a problem. I was able to successfully boot into FreeBSD before I lost access to a keyboard, not much else. Happy FreeBSDing! -- Ross Gohlke > http://www.GRINZ.com (P) 901.276.9750 (Memphis) / 310.356.6906 (Los Angeles) (FAX/HOTLINE) 877.806.0861 AIM: grinzie GIZMO/SKYPE: rossgohlke JABBER: ross@chat.grinz.com 111 S. Highland St. #424, Memphis, TN 38111 | Always up. | From bruce at cran.org.uk Thu Oct 30 00:22:04 2008 From: bruce at cran.org.uk (Bruce Cran) Date: Thu Oct 30 00:22:23 2008 Subject: iBook G4 hang at ADB mouse detection Message-ID: <20081030000652.GA18695@muon.cran.org.uk> I just upgraded to the very latest -CURRENT and my iBook now hangs at boot: ... pmu0: mem 0x16000-0x17fff irq 25 on macio0 pmu0: [MPSAFE] pmu0: [ITHREAD] pmu0: PMU child pmu0: PMU child pmu0: PMU child pmu0: PMU child pmu0: PMU child adb0: on pmu0 akbd0: at device 2 on adb0 kbd: new array size 4 kbd1 at atkbd0 ams0: at device 3 on adb0 Anything I can do to try and track down the problem? -- Bruce Cran From ed at 80386.nl Thu Oct 30 06:15:40 2008 From: ed at 80386.nl (Ed Schouten) Date: Thu Oct 30 06:15:46 2008 Subject: PowerBook 12" hangs right after attaching ams0 Message-ID: <20081030061645.GJ1165@hoeg.nl> Hello all, After using finnix to partition my PowerBook's hard driver (thanks Horst), I managed to install FreeBSD properly. I still have to look into the boot loader issue, but I first want to get the keyboard working. I upgraded from the Oct 2008 snapshot CD to yesterday evening's HEAD. After recompiling the kernel and booting it, it gets stuck right after attaching ams0. I don't have time to copy the entire dmesg by hand here, so here are the last messages when I `boot -v': | adb0: on pmu0 | akbd0: at device 2 on adb0 | kbd: new array size 4 | kbd1 at akbd0 | ams0: at device 3 on adb0 Nathan, is there some special kernel compile switch/command I can run to provide you with more data? -- Ed Schouten WWW: http://80386.nl/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081030/1ae73a88/attachment.pgp From andreast-list at fgznet.ch Thu Oct 30 06:40:59 2008 From: andreast-list at fgznet.ch (Andreas Tobler) Date: Thu Oct 30 06:41:06 2008 Subject: PowerBook 12" hangs right after attaching ams0 In-Reply-To: <20081030061645.GJ1165@hoeg.nl> References: <20081030061645.GJ1165@hoeg.nl> Message-ID: <490956E5.50209@fgznet.ch> Ed Schouten wrote: > Hello all, > > After using finnix to partition my PowerBook's hard driver (thanks > Horst), I managed to install FreeBSD properly. I still have to look into > the boot loader issue, but I first want to get the keyboard working. > > I upgraded from the Oct 2008 snapshot CD to yesterday evening's HEAD. > After recompiling the kernel and booting it, it gets stuck right after > attaching ams0. I don't have time to copy the entire dmesg by hand here, > so here are the last messages when I `boot -v': > > | adb0: on pmu0 > | akbd0: at device 2 on adb0 > | kbd: new array size 4 > | kbd1 at akbd0 > | ams0: at device 3 on adb0 > > Nathan, is there some special kernel compile switch/command I can run to > provide you with more data? > Fyi, I see the same behavior on an albook G4. But with a previous version of the patch it did work. Will investigate tonight. Thanks, Andreas From nwhitehorn at freebsd.org Thu Oct 30 13:44:38 2008 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Thu Oct 30 13:45:08 2008 Subject: PowerBook 12" hangs right after attaching ams0 In-Reply-To: <20081030061645.GJ1165@hoeg.nl> References: <20081030061645.GJ1165@hoeg.nl> Message-ID: <4909BA61.8060008@freebsd.org> Ed Schouten wrote: > Hello all, > > After using finnix to partition my PowerBook's hard driver (thanks > Horst), I managed to install FreeBSD properly. I still have to look into > the boot loader issue, but I first want to get the keyboard working. > > I upgraded from the Oct 2008 snapshot CD to yesterday evening's HEAD. > After recompiling the kernel and booting it, it gets stuck right after > attaching ams0. I don't have time to copy the entire dmesg by hand here, > so here are the last messages when I `boot -v': > > | adb0: on pmu0 > | akbd0: at device 2 on adb0 > | kbd: new array size 4 > | kbd1 at akbd0 > | ams0: at device 3 on adb0 > > Nathan, is there some special kernel compile switch/command I can run to > provide you with more data? > Drat. Could you try the patch at http://people.freebsd.org/~nwhitehorn/adb-delayed-attach.diff? I'd also be interested to know what the bit of your dmesg around macgpio0 looks like, in particular the line from the attachment for pmuextint0. Unfortunately, ams0's attach doesn't have any debug information in it. It is stuck somewhere between lines 171 and 183 of adb_mouse.c, if you want to fill it with printf(). -Nathan From ed at 80386.nl Thu Oct 30 09:00:56 2008 From: ed at 80386.nl (Ed Schouten) Date: Thu Oct 30 09:01:03 2008 Subject: PowerBook 12" hangs right after attaching ams0 In-Reply-To: <4909BA61.8060008@freebsd.org> References: <20081030061645.GJ1165@hoeg.nl> <4909BA61.8060008@freebsd.org> Message-ID: <20081030160143.GL1165@hoeg.nl> Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081030/65f1bfb9/attachment.pgp From nwhitehorn at freebsd.org Thu Oct 30 09:10:23 2008 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Thu Oct 30 09:10:30 2008 Subject: PowerBook 12" hangs right after attaching ams0 In-Reply-To: <20081030160143.GL1165@hoeg.nl> References: <20081030061645.GJ1165@hoeg.nl> <4909BA61.8060008@freebsd.org> <20081030160143.GL1165@hoeg.nl> Message-ID: <4909DC87.6080203@freebsd.org> Ed Schouten wrote: > Hello Nathan, > > * Nathan Whitehorn wrote: >> Drat. Could you try the patch at >> http://people.freebsd.org/~nwhitehorn/adb-delayed-attach.diff? > > After applying the patch, it still gets stuck during boot. Could you try the latest HEAD? I poked around at my machines this morning to try to make them hang, succeeded, and then fixed some problems that make mouse probes hang after the keyboard is probed successfully. >> Unfortunately, ams0's attach doesn't have any debug information in it. >> It is stuck somewhere between lines 171 and 183 of adb_mouse.c, if you >> want to fill it with printf(). > > I can confirm it indeed gets stuck in adb_mouse_attach(), namely during > its call to adb_set_device_handler(). I've just added a `return (ENXIO)' > to adb_mouse_probe(), so I can at least boot my PowerBook for now. The > keyboard support rocks. Thanks! :-) That's about what I expected. The change I added make it retry commands like that if they get stuck, inside of looping forever on a reply. Glad your keyboard works, though! > There are some random things I still have to look into: > > - I've dd'd the boot loader to /dev/ad0s2, but for some reason my Mac > still refuses to boot from it. What is the partition type (gpart show) for ad0s2? I think it might need to be set to !Apple_Bootstrap. The partition size may also need to be exactly 800K. You should be able to change both of these things with the system up, though you might need to enable foot shooting in geom. > - The processor still runs at 533 MHz. I think Linux also did this when > I tried it 3-4 years ago. OF sets it to this at boot. I think there is something you can change at the firmware prompt to bring it up to full speed, but my memory is foggy. I recently picked up a G4 iBook, and am going to look at cpufreq once my work calms down a little in a month or so. Feel free to beat me to it, though :) -Nathan From ed at 80386.nl Thu Oct 30 10:18:33 2008 From: ed at 80386.nl (Ed Schouten) Date: Thu Oct 30 10:18:41 2008 Subject: PowerBook 12" hangs right after attaching ams0 In-Reply-To: <4909DC87.6080203@freebsd.org> References: <20081030061645.GJ1165@hoeg.nl> <4909BA61.8060008@freebsd.org> <20081030160143.GL1165@hoeg.nl> <4909DC87.6080203@freebsd.org> Message-ID: <20081030171918.GM1165@hoeg.nl> * Nathan Whitehorn wrote: > Ed Schouten wrote: >> Hello Nathan, >> >> * Nathan Whitehorn wrote: >>> Drat. Could you try the patch at >>> http://people.freebsd.org/~nwhitehorn/adb-delayed-attach.diff? >> >> After applying the patch, it still gets stuck during boot. > > Could you try the latest HEAD? I poked around at my machines this > morning to try to make them hang, succeeded, and then fixed some > problems that make mouse probes hang after the keyboard is probed > successfully. I will. Unfortunately I have to compile some things first, so I'll get back to you on that. >> There are some random things I still have to look into: >> >> - I've dd'd the boot loader to /dev/ad0s2, but for some reason my Mac >> still refuses to boot from it. > > What is the partition type (gpart show) for ad0s2? I think it might need > to be set to !Apple_Bootstrap. The partition size may also need to be > exactly 800K. You should be able to change both of these things with the > system up, though you might need to enable foot shooting in geom. Even after shrinking the partition to exactly 1600 sectors and using !Apple_Bootstrap, it still doesn't work. Output of `gpart show' below: | => 10 117210230 ad0 APM (60.0GB) | 10 54 - free - (27.6KB) | 64 1600 1 !Apple_Bootstrap (819.2KB) | 1664 448 - free - (229.4KB) | 2112 524288 2 !Apple_UNIX_SVR2 (268.4MB) | 526400 2097152 3 !Apple_UNIX_SVR2 (1073.7MB) | 2623552 524288 4 !Apple_UNIX_SVR2 (268.4MB) | 3147840 524288 5 !Apple_UNIX_SVR2 (268.4MB) | 3672128 16777216 6 !Apple_UNIX_SVR2 (8.6GB) | 20449344 96760896 7 !Apple_UNIX_SVR2 (49.5GB) When I boot my system, I first get the classic folder icon with the question mark in it. After a couple of seconds, I end up in the Open Firmware console. Thanks for your help so far! -- Ed Schouten WWW: http://80386.nl/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081030/6ebecf3d/attachment.pgp From bruce at cran.org.uk Thu Oct 30 11:02:05 2008 From: bruce at cran.org.uk (Bruce Cran) Date: Thu Oct 30 11:02:12 2008 Subject: PowerBook 12" hangs right after attaching ams0 In-Reply-To: <4909DC87.6080203@freebsd.org> References: <20081030061645.GJ1165@hoeg.nl> <4909BA61.8060008@freebsd.org> <20081030160143.GL1165@hoeg.nl> <4909DC87.6080203@freebsd.org> Message-ID: <20081030174243.GA23679@muon.cran.org.uk> On Thu, Oct 30, 2008 at 11:10:47AM -0500, Nathan Whitehorn wrote: > Ed Schouten wrote: >> Hello Nathan, >> >> * Nathan Whitehorn wrote: >>> Drat. Could you try the patch at >>> http://people.freebsd.org/~nwhitehorn/adb-delayed-attach.diff? >> >> After applying the patch, it still gets stuck during boot. > > Could you try the latest HEAD? I poked around at my machines this > morning to try to make them hang, succeeded, and then fixed some > problems that make mouse probes hang after the keyboard is probed > successfully. > >>> Unfortunately, ams0's attach doesn't have any debug information in it. >>> It is stuck somewhere between lines 171 and 183 of adb_mouse.c, if you >>> want to fill it with printf(). >> >> I can confirm it indeed gets stuck in adb_mouse_attach(), namely during >> its call to adb_set_device_handler(). I've just added a `return (ENXIO)' >> to adb_mouse_probe(), so I can at least boot my PowerBook for now. The >> keyboard support rocks. Thanks! :-) > > That's about what I expected. The change I added make it retry commands > like that if they get stuck, inside of looping forever on a reply. Glad > your keyboard works, though! > >> There are some random things I still have to look into: >> >> - I've dd'd the boot loader to /dev/ad0s2, but for some reason my Mac >> still refuses to boot from it. > > What is the partition type (gpart show) for ad0s2? I think it might need > to be set to !Apple_Bootstrap. The partition size may also need to be > exactly 800K. You should be able to change both of these things with the > system up, though you might need to enable foot shooting in geom. > >> - The processor still runs at 533 MHz. I think Linux also did this when >> I tried it 3-4 years ago. > > OF sets it to this at boot. I think there is something you can change at > the firmware prompt to bring it up to full speed, but my memory is foggy. > On my iBook G4 you can configure the CPU to run at the max frequency with: dev /cpus/PowerPC,G4@0 set-dfs-high OF uses a tree for navigation: instead of 'cd' you change 'directories' using the 'dev' command. You can run 'ls' to see what sub-directories are available and run 'words' to see what commands are available. -- Bruce From andreast-list at fgznet.ch Thu Oct 30 15:22:00 2008 From: andreast-list at fgznet.ch (Andreas Tobler) Date: Thu Oct 30 15:22:07 2008 Subject: PowerBook 12" hangs right after attaching ams0 In-Reply-To: <4909DC87.6080203@freebsd.org> References: <20081030061645.GJ1165@hoeg.nl> <4909BA61.8060008@freebsd.org> <20081030160143.GL1165@hoeg.nl> <4909DC87.6080203@freebsd.org> Message-ID: <490A3374.3070309@fgznet.ch> Nathan Whitehorn wrote: > Could you try the latest HEAD? I poked around at my machines this > morning to try to make them hang, succeeded, and then fixed some > problems that make mouse probes hang after the keyboard is probed > successfully. Done here, see attached dmesg. >> - The processor still runs at 533 MHz. I think Linux also did this when >> I tried it 3-4 years ago. > > OF sets it to this at boot. I think there is something you can change at > the firmware prompt to bring it up to full speed, but my memory is foggy. As mentioned in another mail, at OF boot prompt: dev /cpus/PowerPC,G4@0 set-dfs-high Nathan, THANKS! Regards, Andreas P.S, the ata timeout issues have also gone. Well, on this machine I use fw, but on the imac they have gone for sure. -------------- next part -------------- Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.0-CURRENT #0: Thu Oct 30 21:43:51 CET 2008 andreast@wolfram.andreas.nets:/usr/obj/export/head/src/sys/ANDREAST cpu0: Motorola PowerPC 7447A revision 1.1, 1504.63 MHz cpu0: HID0 8450c0bc cpu0: HID1 8000fc80 real memory = 1063497728 (1014 MB) avail memory = 1027358720 (979 MB) kbd0 at kbdmux0 nexus0: powermac_nvram0: on nexus0 powermac_nvram0: bank0 generation 400, bank1 generation 399 unin0: on nexus0 unin0: Version 210 pcib0: on nexus0 pci0: on pcib0 vgapci0: port 0x400-0x4ff mem 0xb8000000-0xbfffffff,0xb0000000-0xb000ffff irq 48 at device 16.0 on pci0 pcib1: on nexus0 pci1: on pcib1 macio0: mem 0x80000000-0x8007ffff at device 23.0 on pci1 openpic0: mem 0x40000-0x7ffff on macio0 macgpio0: mem 0x50-0x7f on macio0 pmuextint0: gpio 9 irq 47 on macgpio0 scc0: mem 0x13000-0x13fff,0x8400-0x84ff,0x8500-0x85ff,0x8600-0x86ff,0x8700-0x87ff irq 22,5,6,23,7,8 on macio0 scc0: [FILTER] scc0: [FILTER] uart0: on scc0 uart0: [FILTER] uart1: on scc0 uart1: [FILTER] pmu0: mem 0x16000-0x17fff irq 25 on macio0 pmu0: [ITHREAD] adb0: on pmu0 ata0 mem 0x20000-0x20fff,0x8800-0x88ff irq 24,12 on macio0 ata0: [ITHREAD] pci1: at device 18.0 (no driver attached) pci1: at device 19.0 (no driver attached) ohci0: mem 0xa0003000-0xa0003fff irq 29 at device 26.0 on pci1 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered ohci1: mem 0xa0002000-0xa0002fff irq 63 at device 27.0 on pci1 ohci1: [GIANT-LOCKED] ohci1: [ITHREAD] usb1: OHCI version 1.0 usb1: on ohci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 3 ports with 3 removable, self powered ohci2: mem 0xa0001000-0xa0001fff irq 63 at device 27.1 on pci1 ohci2: [GIANT-LOCKED] ohci2: [ITHREAD] usb2: OHCI version 1.0 usb2: on ohci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xa0000000-0xa00000ff irq 63 at device 27.2 on pci1 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb3: EHCI version 1.0 usb3: companion controllers, 3 ports each: usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: on usb3 uhub3: 5 ports with 5 removable, self powered pcib2: on nexus0 pci2: on pcib2 ata1: mem 0xf5004000-0xf5007fff irq 39 at device 13.0 on pci2 ata1: [ITHREAD] fwohci0: mem 0xf5000000-0xf5000fff irq 40 at device 14.0 on pci2 fwohci0: [FILTER] fwohci0: OHCI version 1.10 (ROM=0) fwohci0: No. of Isochronous channels is 8. fwohci0: EUI64 00:0d:93:ff:fe:35:b3:80 fwohci0: invalid speed 7 (fixed to 3). fwohci0: Phy 1394a available S800, 3 ports. fwohci0: Link S800, max_rec 4096 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:0d:93:35:b3:80 fwe0: Ethernet address: 02:0d:93:35:b3:80 sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc800ffc1, gen=2, CYCLEMASTER mode gem0: mem 0xf5200000-0xf53fffff irq 41 at device 15.0 on pci2 miibus0: on gem0 e1000phy0: PHY 0 on miibus0 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto gem0: 10kB RX FIFO, 4kB TX FIFO gem0: Ethernet address: 00:0d:93:35:b3:80 gem0: [ITHREAD] sc0: on nexus0 sc0: Unknown <16 virtual consoles, flags=0x300> ukbd0: on uhub0 kbd1 at ukbd0 ums0: on uhub0 ums0: 5 buttons. Timecounter "decrementer" frequency 18432000 Hz quality 0 Timecounters tick every 10.000 msec firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me) firewire0: bus manager 1 (me) acd0: DVDR at ata0-master WDMA2 ad0: 76319MB at ata1-master UDMA100 akbd0: at device 2 on adb0 kbd2 at akbd0 ams0: at device 3 on adb0 ams0: 4-button 400-dpi Unknown Pointing Device firewire0: New S400 device ID:0001d200005b017a da0 at sbp0 bus 0 target 0 lun 0 da0: Fixed Simplified Direct Access SCSI-4 device da0: 50.000MB/s transfers da0: 57231MB (117210240 512 byte sectors: 255H 63S/T 7296C) Trying to mount root from ufs:/dev/da0s5 gem0: link state changed to UP Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...0 0 done All buffers synced. Uptime: 9m6s Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.0-CURRENT #1: Thu Oct 30 22:00:57 CET 2008 andreast@wolfram.andreas.nets:/usr/obj/export/head/src/sys/ANDREAST cpu0: Motorola PowerPC 7447A revision 1.1, 1504.63 MHz cpu0: L1 I-cache enabled, L1 D-cache enabled cpu0: write-back backside cache cpu0: HID0 8450c0bc cpu0: HID1 8000fc80 real memory = 1063497728 (1014 MB) avail memory = 1027358720 (979 MB) kbd0 at kbdmux0 nexus0: powermac_nvram0: on nexus0 powermac_nvram0: bank0 generation 400, bank1 generation 399 unin0: on nexus0 unin0: Version 210 pcib0: on nexus0 pci0: on pcib0 vgapci0: port 0x400-0x4ff mem 0xb8000000-0xbfffffff,0xb0000000-0xb000ffff irq 48 at device 16.0 on pci0 pcib1: on nexus0 pci1: on pcib1 macio0: mem 0x80000000-0x8007ffff at device 23.0 on pci1 openpic0: mem 0x40000-0x7ffff on macio0 macgpio0: mem 0x50-0x7f on macio0 pmuextint0: gpio 9 irq 47 on macgpio0 scc0: mem 0x13000-0x13fff,0x8400-0x84ff,0x8500-0x85ff,0x8600-0x86ff,0x8700-0x87ff irq 22,5,6,23,7,8 on macio0 scc0: [FILTER] scc0: [FILTER] uart0: on scc0 uart0: [FILTER] uart1: on scc0 uart1: [FILTER] pmu0: mem 0x16000-0x17fff irq 25 on macio0 pmu0: [ITHREAD] adb0: on pmu0 ata0 mem 0x20000-0x20fff,0x8800-0x88ff irq 24,12 on macio0 ata0: [ITHREAD] pci1: at device 18.0 (no driver attached) pci1: at device 19.0 (no driver attached) ohci0: mem 0xa0003000-0xa0003fff irq 29 at device 26.0 on pci1 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered ohci1: mem 0xa0002000-0xa0002fff irq 63 at device 27.0 on pci1 ohci1: [GIANT-LOCKED] ohci1: [ITHREAD] usb1: OHCI version 1.0 usb1: on ohci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 3 ports with 3 removable, self powered ohci2: mem 0xa0001000-0xa0001fff irq 63 at device 27.1 on pci1 ohci2: [GIANT-LOCKED] ohci2: [ITHREAD] usb2: OHCI version 1.0 usb2: on ohci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xa0000000-0xa00000ff irq 63 at device 27.2 on pci1 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb3: EHCI version 1.0 usb3: companion controllers, 3 ports each: usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: on usb3 uhub3: 5 ports with 5 removable, self powered pcib2: on nexus0 pci2: on pcib2 ata1: mem 0xf5004000-0xf5007fff irq 39 at device 13.0 on pci2 ata1: [ITHREAD] fwohci0: mem 0xf5000000-0xf5000fff irq 40 at device 14.0 on pci2 fwohci0: [FILTER] fwohci0: OHCI version 1.10 (ROM=0) fwohci0: No. of Isochronous channels is 8. fwohci0: EUI64 00:0d:93:ff:fe:35:b3:80 fwohci0: invalid speed 7 (fixed to 3). fwohci0: Phy 1394a available S800, 3 ports. fwohci0: Link S800, max_rec 4096 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:0d:93:35:b3:80 fwe0: Ethernet address: 02:0d:93:35:b3:80 sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc800ffc1, gen=2, CYCLEMASTER mode gem0: mem 0xf5200000-0xf53fffff irq 41 at device 15.0 on pci2 miibus0: on gem0 e1000phy0: PHY 0 on miibus0 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto gem0: 10kB RX FIFO, 4kB TX FIFO gem0: Ethernet address: 00:0d:93:35:b3:80 gem0: [ITHREAD] sc0: on nexus0 sc0: Unknown <16 virtual consoles, flags=0x300> ukbd0: on uhub0 kbd1 at ukbd0 ums0: on uhub0 ums0: 5 buttons. Timecounter "decrementer" frequency 18432000 Hz quality 0 Timecounters tick every 10.000 msec firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me) firewire0: bus manager 1 (me) acd0: DVDR at ata0-master WDMA2 ad0: 76319MB at ata1-master UDMA100 akbd0: at device 2 on adb0 kbd2 at akbd0 ams0: at device 3 on adb0 ams0: 4-button 400-dpi Unknown Pointing Device firewire0: New S400 device ID:0001d200005b017a da0 at sbp0 bus 0 target 0 lun 0 da0: Fixed Simplified Direct Access SCSI-4 device da0: 50.000MB/s transfers da0: 57231MB (117210240 512 byte sectors: 255H 63S/T 7296C) Trying to mount root from ufs:/dev/da0s5 gem0: link state changed to UP From ed at 80386.nl Thu Oct 30 22:46:21 2008 From: ed at 80386.nl (Ed Schouten) Date: Thu Oct 30 22:46:27 2008 Subject: PowerBook 12" hangs right after attaching ams0 In-Reply-To: <20081030171918.GM1165@hoeg.nl> References: <20081030061645.GJ1165@hoeg.nl> <4909BA61.8060008@freebsd.org> <20081030160143.GL1165@hoeg.nl> <4909DC87.6080203@freebsd.org> <20081030171918.GM1165@hoeg.nl> Message-ID: <20081031054643.GN1165@hoeg.nl> * Ed Schouten wrote: > * Nathan Whitehorn wrote: > > Ed Schouten wrote: > >> Hello Nathan, > >> > >> * Nathan Whitehorn wrote: > >>> Drat. Could you try the patch at > >>> http://people.freebsd.org/~nwhitehorn/adb-delayed-attach.diff? > >> > >> After applying the patch, it still gets stuck during boot. > > > > Could you try the latest HEAD? I poked around at my machines this > > morning to try to make them hang, succeeded, and then fixed some > > problems that make mouse probes hang after the keyboard is probed > > successfully. > > I will. Unfortunately I have to compile some things first, so I'll get > back to you on that. Done. It now boots properly: | ams0: at device 3 on adb0 | ams0: 2-button 400-dpi Unknown Pointing Device I suspect ams(4) uses a protocol that's not supported by moused yet? If so, maybe I can find some time to look into that. -- Ed Schouten WWW: http://80386.nl/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081031/58b809f0/attachment.pgp From nwhitehorn at freebsd.org Fri Oct 31 05:53:40 2008 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Fri Oct 31 05:53:46 2008 Subject: PowerBook 12" hangs right after attaching ams0 In-Reply-To: <20081031054643.GN1165@hoeg.nl> References: <20081030061645.GJ1165@hoeg.nl> <4909BA61.8060008@freebsd.org> <20081030160143.GL1165@hoeg.nl> <4909DC87.6080203@freebsd.org> <20081030171918.GM1165@hoeg.nl> <20081031054643.GN1165@hoeg.nl> Message-ID: <490AFFF0.3010708@freebsd.org> Ed Schouten wrote: > * Ed Schouten wrote: >> * Nathan Whitehorn wrote: >>> Ed Schouten wrote: >>>> Hello Nathan, >>>> >>>> * Nathan Whitehorn wrote: >>>>> Drat. Could you try the patch at >>>>> http://people.freebsd.org/~nwhitehorn/adb-delayed-attach.diff? >>>> After applying the patch, it still gets stuck during boot. >>> Could you try the latest HEAD? I poked around at my machines this >>> morning to try to make them hang, succeeded, and then fixed some >>> problems that make mouse probes hang after the keyboard is probed >>> successfully. >> I will. Unfortunately I have to compile some things first, so I'll get >> back to you on that. > > Done. It now boots properly: > > | ams0: at device 3 on adb0 > | ams0: 2-button 400-dpi Unknown Pointing Device > > I suspect ams(4) uses a protocol that's not supported by moused yet? If > so, maybe I can find some time to look into that. > Glad it works, and thanks for testing! It works just fine with moused. We just don't have a cursor on the console on PPC, though you can still select stuff if you can divine the position of the cursor in advance. It should also work fine in X. If you feel motivated, you could add a "trackpad" class in adb_mouse_attach(), so it doesn't say Unknown Pointing Device -Nathan From ross at grinz.com Fri Oct 31 08:33:33 2008 From: ross at grinz.com (Ross Gohlke) Date: Fri Oct 31 08:33:39 2008 Subject: Issue with sasldb... In-Reply-To: <0E42A5B4-50A4-4A1D-A0A3-47B693A64D16@delfi-konsult.com> References: <2D03106C-0299-4ADA-9B22-C76E331BD17D@delfi-konsult.com> <00CFF0B8-6236-4031-BCCB-79984B7CF641@mac.com> <20080607001220.b15ba937.stas@FreeBSD.org> <0E42A5B4-50A4-4A1D-A0A3-47B693A64D16@delfi-konsult.com> Message-ID: <490B25DB.10000@grinz.com> I had the same problem yesterday installing the latest cyrus-sasl2 from ports: Oct 31 10:15:47 rorty reconstruct[1965]: unable to dlopen /usr/local/lib/sasl2/libsasldb.so.2: /usr/local/lib/sasl2/libsasldb.so.2: Unsupported relocation type 6 in non-PLT relocations My system: Apple Xserve Dual 1GHz FreeBSD 7.0-RELEASE-p5 #0: Wed Oct 29 17:02:37 CDT 2008 The new kernel is GENERIC + IPFilter, PostgreSQL, PF/ALTQ Is this fixed in newer versions? If so, which version is most stable? Should I try 7.1B2? Should I wait for 7.1? Thanks. Ross Niels S. Eliasen wrote: > Hi guys > Den 06/06/2008 kl. 22.12 skrev Stanislav Sedov: > >> On Fri, 06 Jun 2008 10:36:04 -0700 >> Marcel Moolenaar mentioned: >> >>> It looks like libsasldb.so.2 contains code that hasn't been >>> compiled with -fPIC. This typically happens when a shared >>> library is constructed by linking against an archive library. >>> >> >> It seems that all objects libsasldb.so.2, although some of them >> are from ar archive) is built from only PIC objects. >> >> Niels, can you provide a full build log of cyrus-sasl2, so >> we can take a look if there're some problems with build >> script? > Yep.. will do..... > >> >> -- >> Stanislav Sedov >> ST4096-RIPE > > regards > niels > > > > _______________________________________________ > freebsd-ppc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ppc > To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" -- Ross Gohlke > http://www.GRINZ.com (P) 901.276.9750 (Memphis) / 310.356.6906 (Los Angeles) (FAX/HOTLINE) 877.806.0861 AIM: grinzie GIZMO/SKYPE: rossgohlke JABBER: ross@chat.grinz.com 111 S. Highland St. #424, Memphis, TN 38111 | Always up. | From danfe at FreeBSD.org Fri Oct 31 20:33:14 2008 From: danfe at FreeBSD.org (Alexey Dokuchaev) Date: Fri Oct 31 20:33:21 2008 Subject: FreeBSD on my old rusty PowerBook 12" In-Reply-To: <4908C120.3010508@grinz.com> References: <20081029190724.GH1165@hoeg.nl> <4908C120.3010508@grinz.com> Message-ID: <20081101033314.GA53970@FreeBSD.org> On Wed, Oct 29, 2008 at 03:01:36PM -0500, Ross Gohlke wrote: > Do you have an old Mac OS X Installer disc? If so, it contains Disk > Utility, which will allow you to partition the drive, creating a small > HFS partition and as many UFS(2) partitions as you want. You will need > to know the identities of each partition when you get to sysinstall. You > can do this in Disk Utility by selecting each new partition and clicking > Info. > > Older versions (10.1, 10.2) of OS X might use UFS, I'm pretty sure newer > versions use UFS2. Regardless, Disk Utility simply calls it UNIX File > System. > > This is the first I've heard of ADB support, and I don't own a USB > keyboard; I used Disk Utility in Tiger (10.4) to create a dual-boot > drive, so the HFS partition wasn't a problem. This sounds like fun. I'd like to be able to dual-boot between OSX and FreeBSD. Is this procedure documented somewhere (wiki maybe)? Looks like I have to create three partitions: 800K strapping one, OSX HFS+, FreeBSD UFS2. Does the loader in 800K needs any treatment to see both OSes and be able to select which one to boot? Thanks. ./danfe From nwhitehorn at freebsd.org Fri Oct 31 22:43:20 2008 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Fri Oct 31 22:43:25 2008 Subject: FreeBSD on my old rusty PowerBook 12" In-Reply-To: <20081101033314.GA53970@FreeBSD.org> References: <20081029190724.GH1165@hoeg.nl> <4908C120.3010508@grinz.com> <20081101033314.GA53970@FreeBSD.org> Message-ID: <490BEC95.10705@freebsd.org> Alexey Dokuchaev wrote: > On Wed, Oct 29, 2008 at 03:01:36PM -0500, Ross Gohlke wrote: >> Do you have an old Mac OS X Installer disc? If so, it contains Disk >> Utility, which will allow you to partition the drive, creating a small >> HFS partition and as many UFS(2) partitions as you want. You will need >> to know the identities of each partition when you get to sysinstall. You >> can do this in Disk Utility by selecting each new partition and clicking >> Info. >> >> Older versions (10.1, 10.2) of OS X might use UFS, I'm pretty sure newer >> versions use UFS2. Regardless, Disk Utility simply calls it UNIX File >> System. >> >> This is the first I've heard of ADB support, and I don't own a USB >> keyboard; I used Disk Utility in Tiger (10.4) to create a dual-boot >> drive, so the HFS partition wasn't a problem. > > This sounds like fun. I'd like to be able to dual-boot between OSX and > FreeBSD. Is this procedure documented somewhere (wiki maybe)? Looks > like I have to create three partitions: 800K strapping one, OSX HFS+, > FreeBSD UFS2. Does the loader in 800K needs any treatment to see both > OSes and be able to select which one to boot? The CHRP boot script in the boot1 block I was discussing earlier lets you choose an OS at boot using the standard OF menu system (i.e. press Option at boot time and choose a partition). I haven't added niceties like an appropriate icon yet, though. -Nathan