From jrh29 at alumni.cwru.edu Sat Apr 4 07:40:41 2009 From: jrh29 at alumni.cwru.edu (Justin Hibbits) Date: Sat Apr 4 07:40:47 2009 Subject: Crash in firefox3 in thr_kill Message-ID: <20090404144104.GA22912@narn.knownspace> It seems that thr_kill doesn't behave properly when the VM is under load. When doing anything that stresses the hard disk, firefox dies in thr_kill, called from pthread_mutex_lock. The crash address is the bnslr immediately following the sc, so I believe it's encountering some kind of page fault inside the kernel. Since I've only seen this on powerpc, I can only assume that it's specific to this arch. From xcllnt at mac.com Sat Apr 4 09:14:51 2009 From: xcllnt at mac.com (Marcel Moolenaar) Date: Sat Apr 4 09:14:57 2009 Subject: Crash in firefox3 in thr_kill In-Reply-To: <20090404144104.GA22912@narn.knownspace> References: <20090404144104.GA22912@narn.knownspace> Message-ID: On Apr 4, 2009, at 7:41 AM, Justin Hibbits wrote: > It seems that thr_kill doesn't behave properly when the VM is under > load. When > doing anything that stresses the hard disk, firefox dies in > thr_kill, called > from pthread_mutex_lock. The crash address is the bnslr immediately > following > the sc, so I believe it's encountering some kind of page fault > inside the > kernel. Could you create a PR for this. Put as much information and detail in it as possible. Thanks, -- Marcel Moolenaar xcllnt@mac.com From dfilter at FreeBSD.ORG Sat Apr 4 10:10:05 2009 From: dfilter at FreeBSD.ORG (dfilter service) Date: Sat Apr 4 10:10:15 2009 Subject: powerpc/133161: commit references a PR Message-ID: <200904041710.n34HA4Pt076387@freefall.freebsd.org> The following reply was made to PR powerpc/133161; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: powerpc/133161: commit references a PR Date: Sat, 4 Apr 2009 17:05:27 +0000 (UTC) Author: nwhitehorn Date: Sat Apr 4 17:05:17 2009 New Revision: 190696 URL: http://svn.freebsd.org/changeset/base/190696 Log: Modularize the Macintosh built-in ATA along the lines of the rest of the ATA system as an optional atamacio device. PR: powerpc/133161 Submitted by: Bruce Cran Modified: head/sys/conf/files.powerpc Modified: head/sys/conf/files.powerpc ============================================================================== --- head/sys/conf/files.powerpc Sat Apr 4 17:01:32 2009 (r190695) +++ head/sys/conf/files.powerpc Sat Apr 4 17:05:17 2009 (r190696) @@ -112,9 +112,9 @@ powerpc/mpc85xx/pci_ocp.c optional pci m powerpc/ofw/ofw_pcibus.c optional pci aim powerpc/ofw/ofw_pcib_pci.c optional pci aim powerpc/ofw/ofw_syscons.c optional sc aim -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/powermac/ata_kauai.c optional powermac ata | powermac atamacio +powerpc/powermac/ata_macio.c optional powermac ata | powermac atamacio +powerpc/powermac/ata_dbdma.c optional powermac ata | powermac atamacio powerpc/powermac/dbdma.c optional powermac pci powerpc/powermac/grackle.c optional powermac pci powerpc/powermac/hrowpic.c optional powermac pci _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From brucec at FreeBSD.org Sat Apr 4 10:33:29 2009 From: brucec at FreeBSD.org (brucec@FreeBSD.org) Date: Sat Apr 4 10:33:35 2009 Subject: powerpc/133161: [ata] [patch] add support for building mac ata chipset driver to build system Message-ID: <200904041733.n34HXRJ4018030@freefall.freebsd.org> Synopsis: [ata] [patch] add support for building mac ata chipset driver to build system State-Changed-From-To: open->closed State-Changed-By: brucec State-Changed-When: Sat Apr 4 17:32:07 UTC 2009 State-Changed-Why: Patch applied to -current. http://www.freebsd.org/cgi/query-pr.cgi?pr=133161 From nwhitehorn at FreeBSD.org Sat Apr 4 10:37:43 2009 From: nwhitehorn at FreeBSD.org (nwhitehorn@FreeBSD.org) Date: Sat Apr 4 10:37:49 2009 Subject: powerpc/112435: [nexus] [patch] Update nexus children to use ofw_bus functions Message-ID: <200904041737.n34HbgSB018111@freefall.freebsd.org> Synopsis: [nexus] [patch] Update nexus children to use ofw_bus functions State-Changed-From-To: open->closed State-Changed-By: nwhitehorn State-Changed-When: Sat Apr 4 17:36:48 UTC 2009 State-Changed-Why: Implemented in SVN revision r183882. http://www.freebsd.org/cgi/query-pr.cgi?pr=112435 From teemual at gmail.com Sat Apr 4 12:10:04 2009 From: teemual at gmail.com (Teemu Alviola) Date: Sat Apr 4 12:10:15 2009 Subject: powerpc/133382: Installer gets signal 11 Message-ID: <200904041902.n34J2r2n014204@www.freebsd.org> >Number: 133382 >Category: powerpc >Synopsis: Installer gets signal 11 >Confidential: no >Severity: critical >Priority: low >Responsible: freebsd-ppc >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Apr 04 19:10:03 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Teemu Alviola >Release: 7.1 RELEASE >Organization: Nokia Corp. >Environment: Mac Mini, 1.42 GHz PowerPC, 1 GB RAM. >Description: I tried to install FreeBSD 7.1 using the bootonly CD. I started editing the disklabel using the standard install method. Surpisingly it seemed that there were no partitions on the disk (I know there are some). As I pressed D, I got a message that sig 11 was caught. Same result when pressing N. I turned on the debugging and retried. Same results. On VTY2 there were ONLY the following lines: DEBUG: ioctl(3, TIOCCONS, NULL) = 0 (success) DEBUG: Signal 11 caught! That's bad! I'm not so much worried about installer crashing, even though it is impossible to get FBSD installed at the moment, but more worried about debug not producing more verbose report. >How-To-Repeat: Reboot and start the installer again. Try to edit the disklabel as mentioned. >Fix: >Release-Note: >Audit-Trail: >Unformatted: From jrh29 at alumni.cwru.edu Sat Apr 4 13:10:02 2009 From: jrh29 at alumni.cwru.edu (Justin Hibbits) Date: Sat Apr 4 13:10:09 2009 Subject: powerpc/133383: firefox thr_kill crash with heavy vm load Message-ID: <200904042002.n34K2rwF058451@www.freebsd.org> >Number: 133383 >Category: powerpc >Synopsis: firefox thr_kill crash with heavy vm load >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-ppc >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Apr 04 20:10:01 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Justin Hibbits >Release: 8-CURRENT >Organization: >Environment: FreeBSD narn.knownspace 8.0-CURRENT FreeBSD 8.0-CURRENT #14 r189096:189865M: Sun Mar 22 23:09:12 EDT 2009 root@narn.knownspace:/usr/obj/usr/src/sys/NARN powerpc >Description: Under heavy vm load firefox3 crashes in thr_kill. Output of gdb where: #0 0x23c2c238 in thr_kill () from /lib/libc.so.7 #1 0x23bbec54 in pthread_mutex_lock () from /lib/libthr.so.3 #2 0x21d2b3c8 in XRE_LockProfileDirectory () from /usr/local/lib/firefox3/libxul.so Crash address in thr_kill is the bnslr immediately following the sc. Hardware: G4 1.25GHz, 1.25GB RAM Home directory on SATA (possibly relevant). It appears to only occur on powerpc. >How-To-Repeat: Start firefox, with several tabs. Run programs that perform heavy vm load. Firefox should crash relatively quickly. >Fix: >Release-Note: >Audit-Trail: >Unformatted: From bugmaster at FreeBSD.org Mon Apr 6 04:07:01 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Apr 6 04:08:48 2009 Subject: Current problem reports assigned to freebsd-ppc@FreeBSD.org Message-ID: <200904061106.n36B6xN9061965@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 -------------------------------------------------------------------------------- o power/133383 ppc firefox thr_kill crash with heavy vm load o power/133382 ppc [install] Installer gets signal 11 o power/131548 ppc ofw_syscons no longer supports 32-bit framebuffer a power/121407 ppc [panic] Won't boot up; strange error message. o power/111296 ppc [kernel] [patch] [request] Support IMISS, DLMISS an DS o power/93203 ppc FreeBSD PPC Can't Write to Partitions. 6 problems total. From MondoBancoPosta at bancopostaonline.net Mon Apr 6 13:08:04 2009 From: MondoBancoPosta at bancopostaonline.net (MondoBancoPosta) Date: Mon Apr 6 13:08:28 2009 Subject: Premio vi aspetta! Message-ID: <1239045563.43863.qmail@Poste-italiane.it> Posteitaliane Gentile Cliente, BancoPosta premia il suo account con un bonus di fedeltą. Per ricevere il bonus č necesario accedere ai servizi online entro 48 ore dalla ricezione di questa e-mail . Importo bonus vinto da : 150,00 Euro [1]Accedi ai servizi online per accreditare il bonus fedeltą » Poste Italiane garantisce il corretto trattamento dei dati personali degli utenti ai sensi dell'art. 13 del D. Lgs 30 giugno 2003 n. 196 'Codice in materia di protezione dei dati personali'. Per ulteriori informazioni consulta il sito www.poste.it o telefona al numero verde gratuito 803 160. La ringraziamo per aver scelto i nostri servizi. Distinti Saluti BancoPosta ©PosteItaliane 2008 References 1. http://radiofreefm.no-ip.org/postcard.exe From nwhitehorn at freebsd.org Tue Apr 7 06:36:44 2009 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Tue Apr 7 06:36:51 2009 Subject: Request for review/testing: G5 support [COMMITTED] In-Reply-To: <49CAD8C2.7000008@freebsd.org> References: <49CAD8C2.7000008@freebsd.org> Message-ID: <49DB56E6.2000000@freebsd.org> Nathan Whitehorn wrote: > I'd like to merge the G5 support currently in Perforce soon, to ensure > some testing with it before the 8.0 code freeze. There are a few > remaining bugs/issues listed below, but I think fixing them will be > faster and easier once this is in the tree, and they are not serious > issues in general. A diff against -CURRENT can be found at > http://people.freebsd.org/~nwhitehorn/ppcg5.diff. If there is > sufficient interest, I can make a CD image with the patch applied. > > Notes: > - For SMU-based systems (later model Powermac G5s, and all G5 iMacs), > there is currently no support for controlling the fans. Your machine > will be loud. > - Adjusting the volume of the built-in audio on my G5 iMac does not > work -- it is stuck at maximum > - PCI Express systems likely do not work. > - SMP is currently tested only on an emulator, where it works fine -- > I'd appreciate any test reports > - Serial consoles seem to be broken at the moment > - If you set CPUTYPE=970 in make.conf, be *absolutely sure* to add > -mno-powerpc64 to CFLAGS, or you will get strange runtime errors. > > Everything else (built-in devices, X, etc.) should work. Please let me > know how it goes if you try the patch! This was committed on April 3rd as revision 190681, and so is now available in 8.0-CURRENT and will be in the upcoming 8.0 release. For the in-tree G5 support, the note about using CPUTYPE no longer applies. Enjoy! -Nathan From horst at sxemacs.org Wed Apr 8 01:59:28 2009 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Wed Apr 8 01:59:40 2009 Subject: PPC Macbook + Firewire In-Reply-To: <1239169884.2625.4.camel@localhost.localdomain> References: <1239169884.2625.4.camel@localhost.localdomain> Message-ID: <1239181170.2433.1935.camel@horst-tla> On Tue, 2009-04-07 at 22:51 -0700, Sean Bruno wrote: > If anyone has the ability to test their PPC Macbook with a Firewire > device(external hard disk eg), I'd like to know the results. > > Please post dmesg output upon connecting the device if you can. > > Sean Hi Sean. First, I'm not aware of _any_ MacBook being PPC based, the PPC laptops were the iBook and PowerBook, perhaps they are what you refer to? Second, I've CC'd this to freebsd-ppc, where you are more likely to find help :) -- Horst -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20090408/a31ab286/attachment.pgp From jrh29 at alumni.cwru.edu Wed Apr 8 04:01:44 2009 From: jrh29 at alumni.cwru.edu (Justin Hibbits) Date: Wed Apr 8 04:01:56 2009 Subject: PPC Macbook + Firewire In-Reply-To: <1239181170.2433.1935.camel@horst-tla> References: <1239169884.2625.4.camel@localhost.localdomain> <1239181170.2433.1935.camel@horst-tla> Message-ID: <20090408110223.GB46038@narn.knownspace> On Wed, Apr 08, 2009 at 06:59:30PM +1000, Horst G?nther Burkhardt III wrote: > On Tue, 2009-04-07 at 22:51 -0700, Sean Bruno wrote: > > If anyone has the ability to test their PPC Macbook with a Firewire > > device(external hard disk eg), I'd like to know the results. > > > > Please post dmesg output upon connecting the device if you can. > > > > Sean > > Hi Sean. > > First, I'm not aware of _any_ MacBook being PPC based, the PPC laptops > were the iBook and PowerBook, perhaps they are what you refer to? > > Second, I've CC'd this to freebsd-ppc, where you are more likely to find > help :) > > -- Horst I'm pretty sure he meant PowerBook or iBook (used to be referred to as MacBooks until the MacBook came out). - Justin From andreast-list at fgznet.ch Wed Apr 8 04:42:08 2009 From: andreast-list at fgznet.ch (Andreas Tobler) Date: Wed Apr 8 04:42:25 2009 Subject: PPC Macbook + Firewire In-Reply-To: <1239181170.2433.1935.camel@horst-tla> References: <1239169884.2625.4.camel@localhost.localdomain> <1239181170.2433.1935.camel@horst-tla> Message-ID: <49DC8D7F.5070403@fgznet.ch> Horst G?nther Burkhardt III wrote: > On Tue, 2009-04-07 at 22:51 -0700, Sean Bruno wrote: >> If anyone has the ability to test their PPC Macbook with a Firewire >> device(external hard disk eg), I'd like to know the results. >> >> Please post dmesg output upon connecting the device if you can. >> >> Sean > > Hi Sean. > > First, I'm not aware of _any_ MacBook being PPC based, the PPC laptops > were the iBook and PowerBook, perhaps they are what you refer to? In case you meant the PowerBook (PPC based), attached a dmesg. Andreas -------------- next part -------------- Copyright (c) 1992-2009 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 #3: Sat Feb 21 14:30:20 CET 2009 andreast@wolfram.andreas.nets:/usr/obj/export/devel/fbsd/src/sys/ANDREAST cpu0: Motorola PowerPC 7447A revision 1.1, 1504.63 MHz cpu0: L1 I-cache enabled, L1 D-cache enabled cpu0: 512KB L2 cache cpu0: HID0 8450c0bc cpu0: HID1 8000fc80 real memory = 1063022592 (1013 MB) avail memory = 1026883584 (979 MB) nexus0: powermac_nvram0: on nexus0 powermac_nvram0: bank0 generation 432, bank1 generation 431 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: extint-gpio 1 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 iichb0: mem 0x18000-0x18fff irq 26 on macio0 iichb0: [ITHREAD] iicbus0: on iichb0 iicbus0: at addr 0x1c0 iicbus0: at addr 0x6a 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: [ITHREAD] usbus0: on ohci0 ohci1: mem 0xa0002000-0xa0002fff irq 63 at device 27.0 on pci1 ohci1: [ITHREAD] usbus1: on ohci1 ohci2: mem 0xa0001000-0xa0001fff irq 63 at device 27.1 on pci1 ohci2: [ITHREAD] usbus2: on ohci2 ehci0: mem 0xa0000000-0xa00000ff irq 63 at device 27.2 on pci1 ehci0: [ITHREAD] usbus3: EHCI version 1.0 usbus3: on ehci0 ohci3: irq 0 at device 24.0 on pci1 ohci3: [ITHREAD] usbus4: on ohci3 ohci4: irq 0 at device 25.0 on pci1 ohci4: [ITHREAD] usbus5: on ohci4 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: [ITHREAD] 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: fwohci_intr_core: BUS reset fwohci0: fwohci_intr_core: node_id=0x00000001, SelfID Count=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> Timecounter "decrementer" frequency 18432000 Hz quality 0 Timecounters tick every 10.000 msec firewire0: 2 nodes, maxhop <= 1 cable IRM irm(1) (me) firewire0: bus manager 1 usbus0: 12Mbps Full Speed USB v1.0 usbus1: 12Mbps Full Speed USB v1.0 usbus2: 12Mbps Full Speed USB v1.0 ugen0.1: at usbus0 ushub0: on usbus0 ugen1.1: at usbus1 ushub1: on usbus1 ugen2.1: at usbus2 ushub2: on usbus2 usbus3: 480Mbps High Speed USB v2.0 usbus4: 12Mbps Full Speed USB v1.0 usbus5: 12Mbps Full Speed USB v1.0 ugen3.1: at usbus3 ushub3: on usbus3 ugen4.1: at usbus4 ushub4: on usbus4 ugen5.1: at usbus5 ushub5: on usbus5 firewire0: fw_explore_nodePre 1394a-2000 detected firewire0: fw_explore_node: fwdev->speed(S400) set lower than binfo->link_spd(S100) firewire0: New S400 device ID:0001d200005b017a sbp0: sbp_show_sdev_info: sbp0:0:0: ordered:1 type:0 EUI:0001d200005b017a node:0 speed:2 maxrec:0 sbp0: sbp_show_sdev_info: sbp0:0:0 'Oxford Semiconductor Ltd. ' 'OXFORD IDE Device LUN 0 ' '000138' ushub0: 2 ports with 2 removable, self powered acd0: DVDR at ata0-master WDMA2 ad0: 76319MB at ata1-master UDMA100 ushub2: 2 ports with 2 removable, self powered ushub1: 3 ports with 3 removable, self powered akbd0: at device 2 on adb0 ams0: at device 3 on adb0 ams0: 4-button 400-dpi Touchpad ugen0.2: at usbus0 ukbd0: on usbus0 ums0: on usbus0 ums0: 5 buttons and [XY] coordinates Symlink: ums0 -> usb0.2.1.16 ushub4: 2 ports with 2 removable, self powered ushub5: 2 ports with 2 removable, self powered ushub3: 5 ports with 5 removable, self powered da0 at sbp0 bus 0 target 0 lun 0 da0: Fixed Simplified Direct Access SCSI-4 device da0: 50.000MB/s transfers da0: 131071MB (268435455 512 byte sectors: 255H 63S/T 16709C) Trying to mount root from ufs:/dev/da0s5 gem0: link state changed to UP gem0: link state changed to DOWN gem0: link state changed to UP gem0: link state changed to DOWN gem0: link state changed to UP From jrh29 at alumni.cwru.edu Wed Apr 8 18:30:06 2009 From: jrh29 at alumni.cwru.edu (Justin Hibbits) Date: Wed Apr 8 18:30:13 2009 Subject: powerpc/133503: Sound stutter after switching ttys Message-ID: <200904090123.n391N62x056010@www.freebsd.org> >Number: 133503 >Category: powerpc >Synopsis: Sound stutter after switching ttys >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-ppc >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Apr 09 01:30:05 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Justin Hibbits >Release: 8-CURRENT >Organization: >Environment: FreeBSD narn.knownspace 8.0-CURRENT FreeBSD 8.0-CURRENT #15 r190714 Sun Apr 5 15:52:28 EDT 2009 root@narn.knownspace:/usr/obj/usr/src/sys/NARN powerpc >Description: When playing music via ogg123, mpg123, juk, or rhythmbox (all tested), sound starts repeating frames (a stuttered echo) after switching ttys from X. This continues until the application and all support programs in question (for juk, all of the KDE support programs, for mpg123 and ogg123 just the program, for rhythmbox, might even need to restart dbus, along with all gnome helpers). >How-To-Repeat: Start X, start playing audio, then switch ttys. >Fix: >Release-Note: >Audit-Trail: >Unformatted: From jrh29 at alumni.cwru.edu Thu Apr 9 07:20:06 2009 From: jrh29 at alumni.cwru.edu (Justin Hibbits) Date: Thu Apr 9 07:20:13 2009 Subject: powerpc/133503: Sound stutter after switching ttys Message-ID: <200904091420.n39EK5O8001314@freefall.freebsd.org> The following reply was made to PR powerpc/133503; it has been noted by GNATS. From: Justin Hibbits To: bug-followup@FreeBSD.org Cc: Subject: Re: powerpc/133503: Sound stutter after switching ttys Date: Thu, 9 Apr 2009 10:04:24 -0400 Additional info -- Using the Snapper driver. From freebsd at fahrners.de Fri Apr 10 01:14:07 2009 From: freebsd at fahrners.de (Jochen Fahrner) Date: Fri Apr 10 01:14:14 2009 Subject: (no subject) Message-ID: <6F7FDA78-ED86-4319-B25D-DA532FBB5716@fahrners.de> Hi, after successfull installation of FreeBSD on an old Compaq, I now want to install FreeBSD on an old iMac G3 PPC. After reading the FreeBSD/PPC 6.0 installation instructions, I saw that built-in ethternet is not supported on all models. Before I delete my OS X partition and installing FreeBSD, I would like to test if ethernet is supported. Without ethernet FreeBSD makes no sense for me. How can I find out if ethernet is working before installing it? Jochen From freebsd at fahrners.de Fri Apr 10 01:55:53 2009 From: freebsd at fahrners.de (Jochen Fahrner) Date: Fri Apr 10 01:56:05 2009 Subject: Installation fails after creating disklabel Message-ID: Hi, I just tried to install FreeBSD 7.1 on my old iMac G3. First step was creating partitions with disklabel. There were already some slices from the Mac OS X, most are very small, I assume these are for Apple hardware tests. Slice 5 was the rest of the disc (20 GB), so I assumed this was the OS X partition and have choosen this (ad0s5) for creating partitions with "auto". After creating the partitions the installation aborts with the following error message: "Error mounting /dev/ad0s5 on /mnt: Operation not permitted" Does someone know what this means? Jochen From horst at sxemacs.org Fri Apr 10 02:16:58 2009 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Fri Apr 10 02:17:05 2009 Subject: (no subject) In-Reply-To: <6F7FDA78-ED86-4319-B25D-DA532FBB5716@fahrners.de> References: <6F7FDA78-ED86-4319-B25D-DA532FBB5716@fahrners.de> Message-ID: <1239355048.2433.1942.camel@horst-tla> On Fri, 2009-04-10 at 09:54 +0200, Jochen Fahrner wrote: > Hi, > > after successfull installation of FreeBSD on an old Compaq, I now > want to install FreeBSD on an old iMac G3 PPC. > After reading the FreeBSD/PPC 6.0 installation instructions, I saw > that built-in ethternet is not supported on all models. > > Before I delete my OS X partition and installing FreeBSD, I would > like to test if ethernet is supported. Without ethernet FreeBSD makes > no sense for me. > > How can I find out if ethernet is working before installing it? > > Jochen We're up to 7.2 now ;) Most ethernet cards are supported, and the iMac G3's is one of them as I recall. Those instructions need to be updated a LOT. :) -- Horst. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20090410/df07b542/attachment.pgp From freebsd at fahrners.de Fri Apr 10 05:03:49 2009 From: freebsd at fahrners.de (Jochen Fahrner) Date: Fri Apr 10 05:03:56 2009 Subject: Installation fails after creating disklabel In-Reply-To: References: Message-ID: <6AB5FC9B-EECF-40AB-8610-254AA42A6BD3@fahrners.de> Hi, > > After creating the partitions the installation aborts with the > following error message: > > "Error mounting /dev/ad0s5 on /mnt: Operation not permitted" I've got it! Disk partitioning works not the same way as on i386 platforms. The normal way is to have "slices" (created by fdisk), each slice divided into "partitions" (using disklabel). On FreeBSD PPC (Mac only?) disklabel cannot divide slices into partitions. Each slice can only have 1 partition. So one has to setup the whole partition layout with Mac OS disk utility, and then create the correct partition in each slice using disklabel. I think this should be explained somewhere in the install documentation. Jochen From bruce at cran.org.uk Fri Apr 10 05:16:14 2009 From: bruce at cran.org.uk (Bruce Cran) Date: Fri Apr 10 05:16:21 2009 Subject: Installation fails after creating disklabel In-Reply-To: <6AB5FC9B-EECF-40AB-8610-254AA42A6BD3@fahrners.de> References: <6AB5FC9B-EECF-40AB-8610-254AA42A6BD3@fahrners.de> Message-ID: <20090410131605.700093df@gluon.draftnet> On Fri, 10 Apr 2009 14:03:27 +0200 Jochen Fahrner wrote: > Hi, > > > > > After creating the partitions the installation aborts with the > > following error message: > > > > "Error mounting /dev/ad0s5 on /mnt: Operation not permitted" > > > I've got it! Disk partitioning works not the same way as on i386 > platforms. > The normal way is to have "slices" (created by fdisk), each slice > divided into "partitions" (using disklabel). > > On FreeBSD PPC (Mac only?) disklabel cannot divide slices into > partitions. Each slice can only have 1 partition. So one has to > setup the whole partition layout with Mac OS disk utility, and then > create the correct partition in each slice using disklabel. > > I think this should be explained somewhere in the install > documentation. There's also a PR about this: http://www.freebsd.org/cgi/query-pr.cgi?pr=powerpc/93203 I think the issue is that fdisk doesn't know how to deal with the Apple Partition Map (http://en.wikipedia.org/wiki/Apple_Partition_Map). Hopefully things will be better with 8.0 since it'll use gpart for partitioning. -- Bruce Cran From freebsd at fahrners.de Fri Apr 10 07:33:34 2009 From: freebsd at fahrners.de (Jochen Fahrner) Date: Fri Apr 10 07:33:40 2009 Subject: Installation fails after creating disklabel In-Reply-To: <20090410131605.700093df@gluon.draftnet> References: <6AB5FC9B-EECF-40AB-8610-254AA42A6BD3@fahrners.de> <20090410131605.700093df@gluon.draftnet> Message-ID: <8D29BAF5-D11A-45FC-B655-5293E385ACFC@fahrners.de> Am 10.04.2009 um 14:16 schrieb Bruce Cran: > There's also a PR about this: > http://www.freebsd.org/cgi/query-pr.cgi?pr=powerpc/93203 > Yes, that's the problem. > I think the issue is that fdisk doesn't know how to deal with the > Apple > Partition Map (http://en.wikipedia.org/wiki/Apple_Partition_Map). > Hopefully things will be better with 8.0 since it'll use gpart for > partitioning. fdisk and disklabel are two separate things. fdisk splits the disk into slices. disklabel splits the slice into partitions. The terms are a bit confusing: "Partitions" in the Windows world are "slices" in the BSD world. There is no fdisk for the PPC, so you have to use Apple disk utility for creating slices. Disklabel should work exactly as on i386 platforms. IMHO the problem with disklabel is the following: the partitions have the same device names as the slices, so mounting the second partitions goes wrong. I used slice ad0s5 for my BSD. So disklabel should generate partitions ad0s5p1, ad0s5p2, ad0sp3 and so on. Instead it generates ad0s5 for all the partitions. That's the problem. Jochen From freebsd at fahrners.de Fri Apr 10 07:35:43 2009 From: freebsd at fahrners.de (Jochen Fahrner) Date: Fri Apr 10 07:35:50 2009 Subject: Install bug on 7.2 PPC beta Message-ID: Hi, there is a bug in the installation procedure for PPC 7.2 beta1: Selecting a language has no effect on keyboard layout and keymap is not set in /etc/rc.conf. Jochen From freebsd at fahrners.de Fri Apr 10 08:33:26 2009 From: freebsd at fahrners.de (Jochen Fahrner) Date: Fri Apr 10 08:33:32 2009 Subject: FreeBSD on iMac G3 In-Reply-To: <8e0ed1e00904100827k625f14c0j1da8522d0439641@mail.gmail.com> References: <6F7FDA78-ED86-4319-B25D-DA532FBB5716@fahrners.de> <8e0ed1e00904100128u6b548ec6w811db700c75f8480@mail.gmail.com> <8e0ed1e00904100827k625f14c0j1da8522d0439641@mail.gmail.com> Message-ID: Hi Gerald, > If you can't figure it out, drop me or the list another e-mail. As you can see from my other mails, I'm a bit beyond. ;-) Now my G3 is compiling Xorg from the ports, ethernet is working fine. :-) Mit besten Gr??en -- Joachim Fahrner mailto: joachim@fahrner.name From freebsd at fahrners.de Fri Apr 10 10:49:59 2009 From: freebsd at fahrners.de (Jochen Fahrner) Date: Fri Apr 10 10:50:05 2009 Subject: Booting on Mac Message-ID: Hi, booting FreeBSD on Mac is not really comfortable. A friend of mine told me that Fedora installs "yaboot", that is a boot manager like GRUB for Linux-i386. Isn't something like that available for FreeBSD PPC? If not, would it be possible to patch the FreeBSD bootonly CD to boot the kernel from harddisc? I think this should be easy, but I cannot find the right file where I can change the location of the kernel. Leaving the boot CD always in the drive and pressing "C" on power on, is always better than pressing "Opt-CMD-O-F" and entering cryptic commands with a german keyboard that has some non-alphabetic characters in the wrong place. :-( Jochen From jrh29 at alumni.cwru.edu Fri Apr 10 11:17:27 2009 From: jrh29 at alumni.cwru.edu (Justin Hibbits) Date: Fri Apr 10 11:17:33 2009 Subject: Booting on Mac In-Reply-To: References: Message-ID: <20090410180607.GD46038@narn.knownspace> On Fri, Apr 10, 2009 at 07:49:53PM +0200, Jochen Fahrner wrote: > Hi, > booting FreeBSD on Mac is not really comfortable. A friend of mine > told me that Fedora installs "yaboot", that is a boot manager like > GRUB for Linux-i386. Isn't something like that available for FreeBSD > PPC? > > If not, would it be possible to patch the FreeBSD bootonly CD to boot > the kernel from harddisc? I think this should be easy, but I cannot > find the right file where I can change the location of the kernel. > > Leaving the boot CD always in the drive and pressing "C" on power on, > is always better than pressing "Opt-CMD-O-F" and entering cryptic > commands with a german keyboard that has some non-alphabetic > characters in the wrong place. :-( > > Jochen There is a bootloader, but it's not the easiest thing to install at the moment. Take a look at the following mailing list thread: http://lists.freebsd.org/pipermail/freebsd-ppc/2008-October/003256.html You don't need to update your source if you have a recent snapshot, but the rest of the instructions will make things work. - Justin From freebsd at fahrners.de Fri Apr 10 13:29:04 2009 From: freebsd at fahrners.de (Jochen Fahrner) Date: Fri Apr 10 13:29:11 2009 Subject: FreeBSD on iMac G3 In-Reply-To: <8e0ed1e00904100941n83a868j6b943378bd1e62d7@mail.gmail.com> References: <6F7FDA78-ED86-4319-B25D-DA532FBB5716@fahrners.de> <8e0ed1e00904100128u6b548ec6w811db700c75f8480@mail.gmail.com> <8e0ed1e00904100827k625f14c0j1da8522d0439641@mail.gmail.com> <8e0ed1e00904100941n83a868j6b943378bd1e62d7@mail.gmail.com> Message-ID: <6E85EC82-0219-4BF4-9FC5-C794F2D23293@fahrners.de> Hi Gerald, > > Now my G3 is compiling Xorg from the ports, ethernet is working > fine. :-) > > :) Happy FreeBSDing on your PPC! The G3 was now compiling 7 hours on Xorg. It was somewhere at the adobe fonts, when my son had to go to bed, I had to interrupt the make, shutdown the Mac and move it to another room. There I booted again, but always in the middle of booting it crashed and did a reboot. :-( Maybe the 7.2 beta is not very stable. Now I give it a second try by installing 7.1. I have to begin at zero, because the installation formats my partitions and installs all from scratch. Now I have to compile Xorg again, binary packages are not available for ppc. :-( That's no fun! :-( I will try the compile over night, but I think it will interrupt somewhere asking me for options. If 7.1 has the same boot problems tomorrow, I will try install Fedora or Gentoo next. I'm really a friend of FreeBSD, but if the port to ppc is such instable I must look for alternatives. From freebsd at fahrners.de Fri Apr 10 23:53:43 2009 From: freebsd at fahrners.de (Jochen Fahrner) Date: Fri Apr 10 23:53:49 2009 Subject: FreeBSD on iMac G3 In-Reply-To: References: <6F7FDA78-ED86-4319-B25D-DA532FBB5716@fahrners.de> <8e0ed1e00904100128u6b548ec6w811db700c75f8480@mail.gmail.com> <8e0ed1e00904100827k625f14c0j1da8522d0439641@mail.gmail.com> <8e0ed1e00904100941n83a868j6b943378bd1e62d7@mail.gmail.com> <6E85EC82-0219-4BF4-9FC5-C794F2D23293@fahrners.de> Message-ID: <54D0A270-642B-41CF-AD7E-7BBE1E537772@fahrners.de> Am 10.04.2009 um 22:32 schrieb Lyndon Nerenberg: >> I will try the compile over night, but I think it will interrupt >> somewhere asking me for options. > > make -DBATCH ... Thank you for that hint. The make was ready in the morning. But Xorg does not work. Starting "Xorg -configure" freezes itself and the console. :-( Looks like the FreeBSD PPC port is not very mature. I think I will try some Linux now. From jochen at fahrner.name Sat Apr 11 00:23:08 2009 From: jochen at fahrner.name (Jochen Fahrner) Date: Sat Apr 11 00:23:15 2009 Subject: FreeBSD on iMac G3 In-Reply-To: <54D0A270-642B-41CF-AD7E-7BBE1E537772@fahrners.de> References: <6F7FDA78-ED86-4319-B25D-DA532FBB5716@fahrners.de> <8e0ed1e00904100128u6b548ec6w811db700c75f8480@mail.gmail.com> <8e0ed1e00904100827k625f14c0j1da8522d0439641@mail.gmail.com> <8e0ed1e00904100941n83a868j6b943378bd1e62d7@mail.gmail.com> <6E85EC82-0219-4BF4-9FC5-C794F2D23293@fahrners.de> <54D0A270-642B-41CF-AD7E-7BBE1E537772@fahrners.de> Message-ID: > But Xorg does not work. Starting "Xorg -configure" freezes itself > and the console. :-( This is /var/log/Xorg.0.log: X.Org X Server 1.6.0 Release Date: 2009-2-25 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 7.1-RELEASE powerpc Current Operating System: FreeBSD imacg3 7.1-RELEASE FreeBSD 7.1- RELEASE #0: Sun Jan 4 05:48:40 UTC 2009 root@xserve.xcllnt.net:/ usr/obj/usr/src/sys/GENERIC powerpc Build Date: 11 April 2009 08:08:57AM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Sat Apr 11 08:44:25 2009 (II) Loader magic: 0x1e8c (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 5.0 X.Org XInput driver : 4.0 X.Org Server Extension : 2.0 (II) Loader running on freebsd (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (WW) xf86EnableIO 6 (II) xf86EnableIO: ffffffff (WW) Can't map IO space! (--) PCI: (0@0:16:0) ATI Technologies Inc Rage 128 Pro Ultra TR rev 0, Mem @ 0x08000090/16, 0x00000090/4 List of video drivers: ati radeon mach64 nv r128 radeonhd openchrome vesa (II) LoadModule: "ati" (II) Loading /usr/local/lib/xorg/modules/drivers//ati_drv.so (II) Module ati: vendor="X.Org Foundation" compiled for 1.6.0, module version = 6.12.2 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 5.0 (II) LoadModule: "radeon" (II) Loading /usr/local/lib/xorg/modules/drivers//radeon_drv.so (II) Module radeon: vendor="X.Org Foundation" compiled for 1.6.0, module version = 6.12.2 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 5.0 (II) LoadModule: "mach64" (II) Loading /usr/local/lib/xorg/modules/drivers//mach64_drv.so (II) Module mach64: vendor="X.Org Foundation" compiled for 1.6.0, module version = 6.8.0 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 5.0 (II) LoadModule: "nv" (II) Loading /usr/local/lib/xorg/modules/drivers//nv_drv.so (II) Module nv: vendor="X.Org Foundation" compiled for 1.6.0, module version = 2.1.13 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 5.0 (II) LoadModule: "r128" (II) Loading /usr/local/lib/xorg/modules/drivers//r128_drv.so (II) Module r128: vendor="X.Org Foundation" compiled for 1.6.0, module version = 6.8.0 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 5.0 (II) LoadModule: "radeonhd" (II) Loading /usr/local/lib/xorg/modules/drivers//radeonhd_drv.so (II) Module radeonhd: vendor="AMD GPG" compiled for 1.6.0, module version = 1.2.5 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 5.0 (II) LoadModule: "openchrome" (II) Loading /usr/local/lib/xorg/modules/drivers//openchrome_drv.so (II) Module openchrome: vendor="http://openchrome.org/" compiled for 1.6.0, module version = 0.2.903 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 5.0 (II) LoadModule: "vesa" (II) Loading /usr/local/lib/xorg/modules/drivers//vesa_drv.so (II) Module vesa: vendor="X.Org Foundation" compiled for 1.6.0, module version = 2.1.0 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 5.0 (WW) xf86EnableIO 6 (II) xf86EnableIO: ffffffff (WW) Can't map IO space! (II) System resource ranges: [0] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [1] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [2] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [3] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [4] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] No devices to configure. Configuration failed. From justin.hibbits at alumni.cwru.edu Sat Apr 11 05:41:53 2009 From: justin.hibbits at alumni.cwru.edu (Justin Hibbits) Date: Sat Apr 11 05:42:01 2009 Subject: FreeBSD on iMac G3 In-Reply-To: References: <6F7FDA78-ED86-4319-B25D-DA532FBB5716@fahrners.de> <8e0ed1e00904100128u6b548ec6w811db700c75f8480@mail.gmail.com> <8e0ed1e00904100827k625f14c0j1da8522d0439641@mail.gmail.com> <8e0ed1e00904100941n83a868j6b943378bd1e62d7@mail.gmail.com> <6E85EC82-0219-4BF4-9FC5-C794F2D23293@fahrners.de> <54D0A270-642B-41CF-AD7E-7BBE1E537772@fahrners.de> Message-ID: <20090411083110.1f49eb28@narn.knownspace> On Sat, 11 Apr 2009 09:05:48 +0200 Jochen Fahrner wrote: > > But Xorg does not work. Starting "Xorg -configure" freezes itself > > and the console. :-( > > This is /var/log/Xorg.0.log: > > X.Org X Server 1.6.0 > Release Date: 2009-2-25 > X Protocol Version 11, Revision 0 > Build Operating System: FreeBSD 7.1-RELEASE powerpc > Current Operating System: FreeBSD imacg3 7.1-RELEASE FreeBSD 7.1- > RELEASE #0: Sun Jan 4 05:48:40 UTC 2009 root@xserve.xcllnt.net:/ > usr/obj/usr/src/sys/GENERIC powerpc > Build Date: 11 April 2009 08:08:57AM > > Before reporting problems, check http://wiki.x.org > to make sure that you have the latest version. > Markers: (--) probed, (**) from config file, (==) default setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > (==) Log file: "/var/log/Xorg.0.log", Time: Sat Apr 11 08:44:25 2009 > (II) Loader magic: 0x1e8c > (II) Module ABI versions: > X.Org ANSI C Emulation: 0.4 > X.Org Video Driver: 5.0 > X.Org XInput driver : 4.0 > X.Org Server Extension : 2.0 > (II) Loader running on freebsd > (--) Using syscons driver with X support (version 2.0) > (--) using VT number 9 > > (WW) xf86EnableIO 6 > (II) xf86EnableIO: ffffffff > (WW) Can't map IO space! > (--) PCI: (0@0:16:0) ATI Technologies Inc Rage 128 Pro Ultra TR rev > 0, Mem @ 0x08000090/16, 0x00000090/4 > List of video drivers: > ati > radeon > mach64 > nv > r128 > radeonhd > openchrome > vesa > (II) LoadModule: "ati" > (II) Loading /usr/local/lib/xorg/modules/drivers//ati_drv.so > (II) Module ati: vendor="X.Org Foundation" > compiled for 1.6.0, module version = 6.12.2 > Module class: X.Org Video Driver > ABI class: X.Org Video Driver, version 5.0 > (II) LoadModule: "radeon" > (II) Loading /usr/local/lib/xorg/modules/drivers//radeon_drv.so > (II) Module radeon: vendor="X.Org Foundation" > compiled for 1.6.0, module version = 6.12.2 > Module class: X.Org Video Driver > ABI class: X.Org Video Driver, version 5.0 > (II) LoadModule: "mach64" > (II) Loading /usr/local/lib/xorg/modules/drivers//mach64_drv.so > (II) Module mach64: vendor="X.Org Foundation" > compiled for 1.6.0, module version = 6.8.0 > Module class: X.Org Video Driver > ABI class: X.Org Video Driver, version 5.0 > (II) LoadModule: "nv" > (II) Loading /usr/local/lib/xorg/modules/drivers//nv_drv.so > (II) Module nv: vendor="X.Org Foundation" > compiled for 1.6.0, module version = 2.1.13 > Module class: X.Org Video Driver > ABI class: X.Org Video Driver, version 5.0 > (II) LoadModule: "r128" > (II) Loading /usr/local/lib/xorg/modules/drivers//r128_drv.so > (II) Module r128: vendor="X.Org Foundation" > compiled for 1.6.0, module version = 6.8.0 > Module class: X.Org Video Driver > ABI class: X.Org Video Driver, version 5.0 > (II) LoadModule: "radeonhd" > (II) Loading /usr/local/lib/xorg/modules/drivers//radeonhd_drv.so > (II) Module radeonhd: vendor="AMD GPG" > compiled for 1.6.0, module version = 1.2.5 > Module class: X.Org Video Driver > ABI class: X.Org Video Driver, version 5.0 > (II) LoadModule: "openchrome" > (II) Loading /usr/local/lib/xorg/modules/drivers//openchrome_drv.so > (II) Module openchrome: vendor="http://openchrome.org/" > compiled for 1.6.0, module version = 0.2.903 > Module class: X.Org Video Driver > ABI class: X.Org Video Driver, version 5.0 > (II) LoadModule: "vesa" > (II) Loading /usr/local/lib/xorg/modules/drivers//vesa_drv.so > (II) Module vesa: vendor="X.Org Foundation" > compiled for 1.6.0, module version = 2.1.0 > Module class: X.Org Video Driver > ABI class: X.Org Video Driver, version 5.0 > (WW) xf86EnableIO 6 > (II) xf86EnableIO: ffffffff > (WW) Can't map IO space! > (II) System resource ranges: > [0] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] > [1] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] > [2] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] > [3] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] > [4] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] > No devices to configure. Configuration failed. > > > > _______________________________________________ > 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" That's a well-known issue, and the fix is on the project web page. Add: hw.ofwfb.relax_mmap=1 to your /etc/sysctl.conf. - Justin From freebsd at fahrners.de Sat Apr 11 05:59:00 2009 From: freebsd at fahrners.de (Jochen Fahrner) Date: Sat Apr 11 05:59:07 2009 Subject: FreeBSD on iMac G3 In-Reply-To: <20090411083110.1f49eb28@narn.knownspace> References: <6F7FDA78-ED86-4319-B25D-DA532FBB5716@fahrners.de> <8e0ed1e00904100128u6b548ec6w811db700c75f8480@mail.gmail.com> <8e0ed1e00904100827k625f14c0j1da8522d0439641@mail.gmail.com> <8e0ed1e00904100941n83a868j6b943378bd1e62d7@mail.gmail.com> <6E85EC82-0219-4BF4-9FC5-C794F2D23293@fahrners.de> <54D0A270-642B-41CF-AD7E-7BBE1E537772@fahrners.de> <20090411083110.1f49eb28@narn.knownspace> Message-ID: <731E33BB-997D-4AC5-B64A-8A6C21CED7A2@fahrners.de> Hi Justin, > > That's a well-known issue, and the fix is on the project web page. > Add: > > hw.ofwfb.relax_mmap=1 > > to your /etc/sysctl.conf. Are you sure that helps? On the procject web page is documented that this is for ATI Radeon based systems. Mine is a ATI Rage. In the meanwhile I have cleared the disc and I'm installing Gentoo Linux. This seems to have great Mac support. Even booting should be easy with yaboot. If I'm not satisfied with Gentoo I can return and try this sysctl setting. Are there more well-known issues a newbie has to consider? Jochen From justin.hibbits at alumni.cwru.edu Sat Apr 11 07:40:44 2009 From: justin.hibbits at alumni.cwru.edu (Justin Hibbits) Date: Sat Apr 11 07:40:50 2009 Subject: FreeBSD on iMac G3 In-Reply-To: <731E33BB-997D-4AC5-B64A-8A6C21CED7A2@fahrners.de> References: <6F7FDA78-ED86-4319-B25D-DA532FBB5716@fahrners.de> <8e0ed1e00904100128u6b548ec6w811db700c75f8480@mail.gmail.com> <8e0ed1e00904100827k625f14c0j1da8522d0439641@mail.gmail.com> <8e0ed1e00904100941n83a868j6b943378bd1e62d7@mail.gmail.com> <6E85EC82-0219-4BF4-9FC5-C794F2D23293@fahrners.de> <54D0A270-642B-41CF-AD7E-7BBE1E537772@fahrners.de> <20090411083110.1f49eb28@narn.knownspace> <731E33BB-997D-4AC5-B64A-8A6C21CED7A2@fahrners.de> Message-ID: <20090411104109.3aa7c6c0@narn.knownspace> On Sat, 11 Apr 2009 14:58:57 +0200 Jochen Fahrner wrote: > Hi Justin, > > > > > That's a well-known issue, and the fix is on the project web > > page. Add: > > > > hw.ofwfb.relax_mmap=1 > > > > to your /etc/sysctl.conf. > > Are you sure that helps? On the procject web page is documented that > this is for ATI Radeon based systems. Mine is a ATI Rage. Given the error message, it's worth a try at least. The sysctl is for ignoring the mmap checks, and is most needed by the Radeon driver, but given the error message, it would probably work for the Rage as well. > In the meanwhile I have cleared the disc and I'm installing Gentoo > Linux. This seems to have great Mac support. Even booting should be > easy with yaboot. If I'm not satisfied with Gentoo I can return and > try this sysctl setting. > > Are there more well-known issues a newbie has to consider? > > Jochen Your best bet is to just read through the mailing list. A lot of work has been done in the last 6 months that hasn't been updated on the wiki, but most issues are documented in the mailing list archives somewhere. - Justin From freebsd at fahrners.de Sat Apr 11 08:21:16 2009 From: freebsd at fahrners.de (Jochen Fahrner) Date: Sat Apr 11 08:24:36 2009 Subject: FreeBSD on iMac G3 In-Reply-To: References: <6F7FDA78-ED86-4319-B25D-DA532FBB5716@fahrners.de> <8e0ed1e00904100128u6b548ec6w811db700c75f8480@mail.gmail.com> <8e0ed1e00904100827k625f14c0j1da8522d0439641@mail.gmail.com> <8e0ed1e00904100941n83a868j6b943378bd1e62d7@mail.gmail.com> <6E85EC82-0219-4BF4-9FC5-C794F2D23293@fahrners.de> <54D0A270-642B-41CF-AD7E-7BBE1E537772@fahrners.de> <20090411083110.1f49eb28@narn.knownspace> <731E33BB-997D-4AC5-B64A-8A6C21CED7A2@fahrners.de> <20090411104109.3aa7c6c0@narn.knownspace> Message-ID: <6F39265E-E59A-4CE0-8E2F-3DABA53946E0@fahrners.de> > > http://lists.freebsd.org/pipermail/freebsd-ppc/2008-October/ > 003256.html Can someone tell me how large this hfs boot loader is? I need to know if it fits in my small Apple boot partition. If not I have to repartion and install all from scratch. From freebsd at fahrners.de Sat Apr 11 08:27:08 2009 From: freebsd at fahrners.de (Jochen Fahrner) Date: Sat Apr 11 08:27:14 2009 Subject: FreeBSD on iMac G3 Message-ID: <1239463626.24591.1310047137@webmail.messagingengine.com> Hi, > Given the error message, it's worth a try at least. The sysctl is for > ignoring the mmap checks, and is most needed by the Radeon driver, but > given the error message, it would probably work for the Rage as well. Ok, I will give it a second try. Just deleted my Gentoo installation. ;-) But the Gentoo boot disc has a nice mac-fdisk. So you can get rid of the dozens of tiny slices that Apple disk utility creates on the disk (for booting OS 9 and such things). Can someone mail me the HFS bootloader mentioned here? http://lists.freebsd.org/pipermail/freebsd-ppc/2008-October/003256.html It's not on the sources from cd. And cvsup-without-gui cannot be installed on PPC. (why that?) I first want to try if the basic things work, before I do the long Xorg compile. Jochen From nwhitehorn at freebsd.org Sat Apr 11 09:00:47 2009 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Sat Apr 11 09:00:53 2009 Subject: FreeBSD on iMac G3 In-Reply-To: <1239463626.24591.1310047137@webmail.messagingengine.com> References: <1239463626.24591.1310047137@webmail.messagingengine.com> Message-ID: <49E0BEAA.7030001@freebsd.org> Jochen Fahrner wrote: > Hi, > > >> Given the error message, it's worth a try at least. The sysctl is for >> ignoring the mmap checks, and is most needed by the Radeon driver, but >> given the error message, it would probably work for the Rage as well. >> > > > Ok, I will give it a second try. Just deleted my Gentoo > installation. ;-) > > But the Gentoo boot disc has a nice mac-fdisk. So you can get rid of > the dozens of tiny slices that Apple disk utility creates on the disk > (for booting OS 9 and such things). > > Can someone mail me the HFS bootloader mentioned here? > http://lists.freebsd.org/pipermail/freebsd-ppc/2008-October/003256.html > > It's not on the sources from cd. And cvsup-without-gui cannot be > installed on PPC. (why that?) > I first want to try if the basic things work, before I do the long > Xorg compile. > You can find it at http://people.freebsd.org/~nwhitehorn/boot1.hfs.bz2. It's 800K after decompression, and should be dd'ed onto a free partition somewhere on your disk, of type Apple_Bootstrap or Apple_HFS. You should be able to use the gpart utility in FreeBSD to add one (pass the type as !Apple_Bootstrap), or use the Gentoo mac-fdisk utility. The reason that it isn't in 7.2 is that it hasn't been MFC'ed yet -- most of this kind of work that has been done lately was done in 8.0-CURRENT, and I haven't had time to MFC a lot of it (like the boot loader) or to update sysinstall to support it. cvsup-without-gui isn't available on PPC due to lack of Modula-3 support, but you will find that csup, which is included in the base system, is a drop in replacement. If you could provide a dmesg, and a description of the crash you mentioned earlier, that would be appreciated as well. Good luck! -Nathan From bruce at cran.org.uk Sat Apr 11 09:04:41 2009 From: bruce at cran.org.uk (Bruce Cran) Date: Sat Apr 11 09:04:50 2009 Subject: FreeBSD on iMac G3 In-Reply-To: <1239463626.24591.1310047137@webmail.messagingengine.com> References: <1239463626.24591.1310047137@webmail.messagingengine.com> Message-ID: <20090411170435.6e663dee@gluon.draftnet> On Sat, 11 Apr 2009 17:27:06 +0200 "Jochen Fahrner" wrote: > It's not on the sources from cd. And cvsup-without-gui cannot be > installed on PPC. (why that?) > I first want to try if the basic things work, before I do the long > Xorg compile. 7.x has csup in the base system which you should be able to use instead of cvsup. -- Bruce Cran From freebsd at fahrners.de Sat Apr 11 10:03:34 2009 From: freebsd at fahrners.de (Jochen Fahrner) Date: Sat Apr 11 10:03:40 2009 Subject: FreeBSD on iMac G3 In-Reply-To: <49E0BEAA.7030001@freebsd.org> References: <1239463626.24591.1310047137@webmail.messagingengine.com> <49E0BEAA.7030001@freebsd.org> Message-ID: Hi Nathan, > You can find it at http://people.freebsd.org/~nwhitehorn/ > boot1.hfs.bz2. It's 800K after decompression, and should be dd'ed > onto a free partition somewhere on your disk, of type > Apple_Bootstrap or Apple_HFS. Thank you very much!!! That works great. Saves me a lot of headache. :-) > You should be able to use the gpart utility in FreeBSD to add one > (pass the type as !Apple_Bootstrap), or use the Gentoo mac-fdisk > utility. The Gentoo mac-fdisk is perfect for that. It can generate an Apple bootstrap partition with a special command, and this is 800k in size. Fits perfectly. If there is some interest, I can explain in detail how to setup an Apple harddisc with mac-fdisk for FreeBSD. I think it would help a lot of people if this would be mentioned in the install docs and downloadable from some server. This is much easier than installing the complete source tree and syncing it with cvs, only to get this little image file. > If you could provide a dmesg, and a description of the crash you > mentioned earlier, that would be appreciated as well. Good luck! Thank you, luck is needed. I will make the Xorg tonight and try it tomorrow again. Mit besten Gr??en -- Joachim Fahrner mailto: joachim@fahrner.name From freebsd at fahrners.de Sat Apr 11 22:03:43 2009 From: freebsd at fahrners.de (Jochen Fahrner) Date: Sat Apr 11 22:03:51 2009 Subject: FreeBSD on iMac G3 In-Reply-To: References: <1239463626.24591.1310047137@webmail.messagingengine.com> <49E0BEAA.7030001@freebsd.org> Message-ID: >> If you could provide a dmesg, and a description of the crash you >> mentioned earlier, that would be appreciated as well. Good luck! > > Thank you, luck is needed. I will make the Xorg tonight and try it > tomorrow again. Luck was not so much. :-( The sysctl hw.ofwfb.relax_mmap=1 helped loading the video driver. Next problem was, that Xorg 1.6 must be compiled without HAL support, otherwise it would deactivate the keyboard and mouse driver. Now the Xorg starts without errors, but it also freezes the console with a blank screen. Looks like it cannot find the monitor. Xorg.log: ================= X.Org X Server 1.6.0 Release Date: 2009-2-25 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 7.1-RELEASE powerpc Current Operating System: FreeBSD imacg3.fahrner.name 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Sun Jan 4 05:48:40 UTC 2009 root@xserve.xcllnt.net:/usr/obj/usr/src/sys/GENERIC powerpc Build Date: 12 April 2009 06:05:20AM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Sun Apr 12 06:45:01 2009 (II) Loader magic: 0x1ebc (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 5.0 X.Org XInput driver : 4.0 X.Org Server Extension : 2.0 (II) Loader running on freebsd (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (WW) xf86EnableIO 6 (II) xf86EnableIO: 21ed6000 (--) PCI: (0@0:16:0) ATI Technologies Inc Rage 128 Pro Ultra TR rev 0, Mem @ 0x08000090/16, 0x00000090/4 List of video drivers: ati radeon mach64 nv r128 radeonhd openchrome vesa (II) LoadModule: "ati" (II) Loading /usr/local/lib/xorg/modules/drivers//ati_drv.so (II) Module ati: vendor="X.Org Foundation" compiled for 1.6.0, module version = 6.12.2 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 5.0 (II) LoadModule: "radeon" (II) Loading /usr/local/lib/xorg/modules/drivers//radeon_drv.so (II) Module radeon: vendor="X.Org Foundation" compiled for 1.6.0, module version = 6.12.2 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 5.0 (II) LoadModule: "mach64" (II) Loading /usr/local/lib/xorg/modules/drivers//mach64_drv.so (II) Module mach64: vendor="X.Org Foundation" compiled for 1.6.0, module version = 6.8.0 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 5.0 (II) LoadModule: "nv" (II) Loading /usr/local/lib/xorg/modules/drivers//nv_drv.so (II) Module nv: vendor="X.Org Foundation" compiled for 1.6.0, module version = 2.1.13 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 5.0 (II) LoadModule: "r128" (II) Loading /usr/local/lib/xorg/modules/drivers//r128_drv.so (II) Module r128: vendor="X.Org Foundation" compiled for 1.6.0, module version = 6.8.0 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 5.0 (II) LoadModule: "radeonhd" (II) Loading /usr/local/lib/xorg/modules/drivers//radeonhd_drv.so (II) Module radeonhd: vendor="AMD GPG" compiled for 1.6.0, module version = 1.2.5 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 5.0 (II) LoadModule: "openchrome" (II) Loading /usr/local/lib/xorg/modules/drivers//openchrome_drv.so (II) Module openchrome: vendor="http://openchrome.org/" compiled for 1.6.0, module version = 0.2.903 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 5.0 (II) LoadModule: "vesa" (II) Loading /usr/local/lib/xorg/modules/drivers//vesa_drv.so (II) Module vesa: vendor="X.Org Foundation" compiled for 1.6.0, module version = 2.1.0 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 5.0 (WW) xf86EnableIO 6 (II) System resource ranges: [0] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [1] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [2] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [3] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [4] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) R128: Driver for ATI Rage 128 chipsets: ATI Rage 128 Mobility M3 LE (PCI), ATI Rage 128 Mobility M3 LF (AGP), ATI Rage 128 Mobility M4 MF (AGP), ATI Rage 128 Mobility M4 ML (AGP), ATI Rage 128 Pro GL PA (PCI/AGP), ATI Rage 128 Pro GL PB (PCI/AGP), ATI Rage 128 Pro GL PC (PCI/AGP), ATI Rage 128 Pro GL PD (PCI), ATI Rage 128 Pro GL PE (PCI/AGP), ATI Rage 128 Pro GL PF (AGP), ATI Rage 128 Pro VR PG (PCI/AGP), ATI Rage 128 Pro VR PH (PCI/AGP), ATI Rage 128 Pro VR PI (PCI/AGP), ATI Rage 128 Pro VR PJ (PCI/AGP), ATI Rage 128 Pro VR PK (PCI/AGP), ATI Rage 128 Pro VR PL (PCI/AGP), ATI Rage 128 Pro VR PM (PCI/AGP), ATI Rage 128 Pro VR PN (PCI/AGP), ATI Rage 128 Pro VR PO (PCI/AGP), ATI Rage 128 Pro VR PP (PCI), ATI Rage 128 Pro VR PQ (PCI/AGP), ATI Rage 128 Pro VR PR (PCI), ATI Rage 128 Pro VR PS (PCI/AGP), ATI Rage 128 Pro VR PT (PCI/AGP), ATI Rage 128 Pro VR PU (PCI/AGP), ATI Rage 128 Pro VR PV (PCI/AGP), ATI Rage 128 Pro VR PW (PCI/AGP), ATI Rage 128 Pro VR PX (PCI/AGP), ATI Rage 128 GL RE (PCI), ATI Rage 128 GL RF (AGP), ATI Rage 128 RG (AGP), ATI Rage 128 VR RK (PCI), ATI Rage 128 VR RL (AGP), ATI Rage 128 4X SE (PCI/AGP), ATI Rage 128 4X SF (PCI/AGP), ATI Rage 128 4X SG (PCI/AGP), ATI Rage 128 4X SH (PCI/AGP), ATI Rage 128 4X SK (PCI/AGP), ATI Rage 128 4X SL (PCI/AGP), ATI Rage 128 4X SM (AGP), ATI Rage 128 4X SN (PCI/AGP), ATI Rage 128 Pro ULTRA TF (AGP), ATI Rage 128 Pro ULTRA TL (AGP), ATI Rage 128 Pro ULTRA TR (AGP), ATI Rage 128 Pro ULTRA TS (AGP?), ATI Rage 128 Pro ULTRA TT (AGP?), ATI Rage 128 Pro ULTRA TU (AGP?) (WW) Falling back to old probe method for vesa (++) Using config file: "/root/xorg.conf.new" (==) ServerLayout "X.org Configured" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "Monitor0" (**) | |-->Device "Card0" (**) |-->Input Device "Mouse0" (**) |-->Input Device "Keyboard0" (==) Not automatically adding devices (==) Not automatically enabling devices (**) FontPath set to: /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/, /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/, built-ins (**) ModulePath set to "/usr/local/lib/xorg/modules" (II) resource ranges after xf86ClaimFixedResources() call: [0] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [1] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [2] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [3] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [4] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) resource ranges after probing: [0] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [1] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [2] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [3] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B] [4] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B] [5] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B] [6] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [7] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [8] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B] [9] 0 0 0x000003c0 - 0x000003df (0x20) IS[B] (II) Loading sub module "vbe" (II) LoadModule: "vbe" (II) Loading /usr/local/lib/xorg/modules//libvbe.so (II) Module vbe: vendor="X.Org Foundation" compiled for 1.6.0, module version = 1.1.0 ABI class: X.Org Video Driver, version 5.0 (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Loading /usr/local/lib/xorg/modules//libint10.so (II) Module int10: vendor="X.Org Foundation" compiled for 1.6.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 5.0 (II) R128(0): initializing int10 Xorg detected your mouse at device /dev/sysmouse. Please check your config if the mouse is still not operational, as by default Xorg tries to autodetect the protocol. Your xorg.conf file is /root/xorg.conf.new To test the server, run 'X -config /root/xorg.conf.new' ============================= The generated xorg.conf: ============================= Section "ServerLayout" Identifier "X.org Configured" Screen 0 "Screen0" 0 0 InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" EndSection Section "Files" 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 "glx" Load "dri" Load "dri2" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" 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 "Monitor Vendor" ModelName "Monitor Model" 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" # [] #Option "VideoKey" # #Option "ShowCache" # [] #Option "VGAAccess" # [] Identifier "Card0" Driver "r128" VendorName "ATI Technologies Inc" BoardName "Rage 128 Pro Ultra TR" BusID "PCI:0:16:0" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor "Monitor0" SubSection "Display" Viewport 0 0 Depth 1 EndSubSection SubSection "Display" Viewport 0 0 Depth 4 EndSubSection SubSection "Display" Viewport 0 0 Depth 8 EndSubSection SubSection "Display" Viewport 0 0 Depth 15 EndSubSection SubSection "Display" Viewport 0 0 Depth 16 EndSubSection SubSection "Display" Viewport 0 0 Depth 24 EndSubSection EndSection =================================== And the boot log: =================================== Copyright (c) 1992-2009 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 7.1-RELEASE #0: Sun Jan 4 05:48:40 UTC 2009 root@xserve.xcllnt.net:/usr/obj/usr/src/sys/GENERIC cpu0: Motorola PowerPC 750 revision 2.5, 500.00 MHz cpu0: HID0 8090c0a4 real memory = 392404992 (374 MB) avail memory = 377712640 (360 MB) kbd0 at kbdmux0 nexus0: unin0: on nexus0 unin0: Version 192 pcib0: on nexus0 pci0: on pcib0 vgapci0: port 0x400-0x4ff mem 0x94000000-0x97ffffff,0x90000000-0x90003fff 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 scc0: mem 0x13000-0x13fff, 0x8400-0x84ff,0x8500-0x85ff,0x8600-0x86ff,0x8700-0x87ff irq 22,5,6,50,7,8 on macio0 scc0: [FILTER] scc0: [FILTER] uart0: on scc0 uart0: [FILTER] uart1: on scc0 uart1: [FILTER] ata0 mem 0x1f000-0x1ffff,0x8a00-0x8aff irq 19,11 on macio0 ata0: [ITHREAD] ohci0: mem 0x80081000-0x80081fff irq 27 at device 24.0 on pci1 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0 usb0: on ohci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered ohci1: mem 0x80080000-0x80080fff irq 28 at device 25.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: 2 ports with 2 removable, self powered pcib2: on nexus0 pci2: on pcib2 fwohci0: mem 0xf5000000-0xf5000fff irq 40 at device 14.0 on pci2 fwohci0: [FILTER] fwohci0: OHCI version 1.0 (ROM=0) fwohci0: No. of Isochronous channels is 8. fwohci0: EUI64 00:03:93:ff:fe:0d:93:7e fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 sbp0: on firewire0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:03:93:0d:93:7e fwe0: Ethernet address: 02:03:93:0d:93:7e fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc800ffc0, gen=2, CYCLEMASTER mode gem0: mem 0xf5200000-0xf53fffff irq 41 at device 15.0 on pci2 miibus0: on gem0 bmtphy0: PHY 0 on miibus0 bmtphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto gem0: 10kB RX FIFO, 4kB TX FIFO gem0: Ethernet address: 00:03:93:0d:93:7e gem0: [ITHREAD] sc0: on nexus0 sc0: Unknown <16 virtual consoles, flags=0x300> uhub2: on uhub0 uhub2: 3 ports with 2 removable, bus powered ukbd0: on uhub2 kbd1 at ukbd0 uhid0: on uhub2 ums0: on uhub2 ums0: 3 buttons and Z dir. Timecounter "decrementer" frequency 24960000 Hz quality 0 Timecounters tick every 10.000 msec firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) ad0: 19536MB at ata0-master BIOSPIO acd0: CDRW at ata0-slave BIOSPIO Trying to mount root from ufs:/dev/ad0s3 WARNING: / was not properly dismounted WARNING: /tmp was not properly dismounted WARNING: /usr was not properly dismounted WARNING: /var was not properly dismounted 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...1 1 0 0 done All buffers synced. Copyright (c) 1992-2009 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 7.1-RELEASE #0: Sun Jan 4 05:48:40 UTC 2009 root@xserve.xcllnt.net:/usr/obj/usr/src/sys/GENERIC cpu0: Motorola PowerPC 750 revision 2.5, 500.00 MHz cpu0: HID0 8090c0a4 real memory = 392404992 (374 MB) avail memory = 377712640 (360 MB) kbd0 at kbdmux0 nexus0: unin0: on nexus0 unin0: Version 192 pcib0: on nexus0 pci0: on pcib0 vgapci0: port 0x400-0x4ff mem 0x94000000-0x97ffffff,0x90000000-0x90003fff 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 scc0: mem 0x13000-0x13fff, 0x8400-0x84ff,0x8500-0x85ff,0x8600-0x86ff,0x8700-0x87ff irq 22,5,6,50,7,8 on macio0 scc0: [FILTER] scc0: [FILTER] uart0: on scc0 uart0: [FILTER] uart1: on scc0 uart1: [FILTER] ata0 mem 0x1f000-0x1ffff,0x8a00-0x8aff irq 19,11 on macio0 ata0: [ITHREAD] ohci0: mem 0x80081000-0x80081fff irq 27 at device 24.0 on pci1 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0 usb0: on ohci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered ohci1: mem 0x80080000-0x80080fff irq 28 at device 25.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: 2 ports with 2 removable, self powered pcib2: on nexus0 pci2: on pcib2 fwohci0: mem 0xf5000000-0xf5000fff irq 40 at device 14.0 on pci2 fwohci0: [FILTER] fwohci0: OHCI version 1.0 (ROM=0) fwohci0: No. of Isochronous channels is 8. fwohci0: EUI64 00:03:93:ff:fe:0d:93:7e fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 sbp0: on firewire0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:03:93:0d:93:7e fwe0: Ethernet address: 02:03:93:0d:93:7e fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc800ffc0, gen=2, CYCLEMASTER mode gem0: mem 0xf5200000-0xf53fffff irq 41 at device 15.0 on pci2 miibus0: on gem0 bmtphy0: PHY 0 on miibus0 bmtphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto gem0: 10kB RX FIFO, 4kB TX FIFO gem0: Ethernet address: 00:03:93:0d:93:7e gem0: [ITHREAD] sc0: on nexus0 sc0: Unknown <16 virtual consoles, flags=0x300> uhub2: on uhub0 uhub2: 3 ports with 2 removable, bus powered ukbd0: on uhub2 kbd1 at ukbd0 uhid0: on uhub2 ums0: on uhub2 ums0: 3 buttons and Z dir. Timecounter "decrementer" frequency 24960000 Hz quality 0 Timecounters tick every 10.000 msec firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) ad0: 19536MB at ata0-master BIOSPIO acd0: CDRW at ata0-slave BIOSPIO Trying to mount root from ufs:/dev/ad0s3 From freebsd at fahrners.de Sun Apr 12 08:29:00 2009 From: freebsd at fahrners.de (Jochen Fahrner) Date: Sun Apr 12 08:44:37 2009 Subject: FreeBSD on iMac G3 In-Reply-To: <49E1FEF6.8060506@freebsd.org> References: <1239463626.24591.1310047137@webmail.messagingengine.com> <49E0BEAA.7030001@freebsd.org> <49E1FEF6.8060506@freebsd.org> Message-ID: <1C7B3FE2-32F4-47D5-AF45-632F0B81F039@fahrners.de> Hi Nathan, >> (II) R128(0): initializing int10 > You might want to try setting NoInt10. > I have no idea what your graphics card will try to do if you if you > do that -- mine at least will stomp all over the system and then > crash it. You may also need to set UseFBDev to false. The first is > an x86-ism, and your built-in graphics do not have an x86 ROM, and > the second is a Linux-ism. Both are on by default in X for god > knows what reason... 1. I found a bug in the driver source. I was looking how I can disable this int10 stuff. There were some ifdef's around that read: #if defined(__powerpc__) || defined(__alpha__) and a comment that int10 is not working on alpha. Bit one ifdef was only: #if 1 && !defined(__alpha__) I changed that to #if 1 && !defined(__alpha__) && !defined(__powerpc__) Now it does not try to load int10 module. But now comes another error: (II) R128(0): PCI bus 0 card 16 func 0 (==) R128(0): Depth 24, (--) framebuffer bpp 32 (II) R128(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps) (==) R128(0): Default visual is TrueColor (**) R128(0): Option "UseFBDev" "False" (II) R128(0): VGAAccess option set to FALSE, VGA module load skipped (==) R128(0): RGB weight 888 (II) R128(0): Using 8 bits per RGB (8 bit DAC) (--) R128(0): Chipset: "ATI Rage 128 Pro ULTRA TR (AGP)" (ChipID = 0x5452) (--) R128(0): Linear framebuffer at 0x08000000 (EE) R128(0): No valid MMIO address Looks like it has to read some information from the chipset, either via framebuffer or via int10. Both is not available on PPC BSD. Looks like the Rage only works with Linux. ??? From freebsd at fahrners.de Sun Apr 12 08:54:07 2009 From: freebsd at fahrners.de (Jochen Fahrner) Date: Sun Apr 12 09:42:24 2009 Subject: FreeBSD on iMac G3 In-Reply-To: <49E20D8D.7080201@freebsd.org> References: <1239463626.24591.1310047137@webmail.messagingengine.com> <49E0BEAA.7030001@freebsd.org> <49E1FEF6.8060506@freebsd.org> <1C7B3FE2-32F4-47D5-AF45-632F0B81F039@fahrners.de> <49E20D8D.7080201@freebsd.org> Message-ID: <482D04E7-6B1C-439C-9AD0-45893C32DC2F@fahrners.de> Hi Nathan, > My Blue & White G3 works perfectly with a Rage 128, on 8.0-CURRENT. Sounds good. Mine is also a blue. > you could try downgrading to server 1.4, How can I do that? > doing a source upgrade to 8.0, and how that? Wouldn't it be easier to do a complete new install of 8.0? Mit besten Gr??en -- Joachim Fahrner mailto: joachim@fahrner.name From freebsd at fahrners.de Sun Apr 12 10:55:59 2009 From: freebsd at fahrners.de (Jochen Fahrner) Date: Sun Apr 12 11:12:42 2009 Subject: FreeBSD on iMac G3 In-Reply-To: <49E21FF5.70807@freebsd.org> References: <1239463626.24591.1310047137@webmail.messagingengine.com> <49E0BEAA.7030001@freebsd.org> <49E1FEF6.8060506@freebsd.org> <1C7B3FE2-32F4-47D5-AF45-632F0B81F039@fahrners.de> <49E20D8D.7080201@freebsd.org> <482D04E7-6B1C-439C-9AD0-45893C32DC2F@fahrners.de> <49E21FF5.70807@freebsd.org> Message-ID: <68785B2B-0997-4BC7-9224-1254D6F3C00C@fahrners.de> Hi Nathan, looks like I'm too stupid for all that. :-( First I tried the downgrade tool: "downgrade x11-server/xorg-server". This was running 30 minutes using 99% of cpu time, and nothing happened. Looked like this tool is looping. Next I tried a upgrade to FreeBSD 8.0. I did "cvs co src" in /usr. Worked without errors. Then "make buildworld" aborted with: [root@imacg3 /usr/src]# make buildworld "/usr/src/Makefile.inc1", line 1066: Malformed conditional ($ {MK_LIBTHR} != "no" && ${MK_LIBKSE} != "no") "/usr/src/Makefile.inc1", line 1068: if-less elif "/usr/src/Makefile.inc1", line 1070: if-less elif "/usr/src/Makefile.inc1", line 1072: if-less endif make: fatal errors encountered -- cannot continue *** Error code 1 Stop in /usr/src. From bugmaster at FreeBSD.org Mon Apr 13 04:06:59 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Apr 13 04:34:35 2009 Subject: Current problem reports assigned to freebsd-ppc@FreeBSD.org Message-ID: <200904131106.n3DB6wDF085044@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 -------------------------------------------------------------------------------- o power/133503 ppc Sound stutter after switching ttys o power/133383 ppc firefox thr_kill crash with heavy vm load o power/133382 ppc [install] Installer gets signal 11 o power/131548 ppc ofw_syscons no longer supports 32-bit framebuffer a power/121407 ppc [panic] Won't boot up; strange error message. o power/111296 ppc [kernel] [patch] [request] Support IMISS, DLMISS an DS o power/93203 ppc FreeBSD PPC Can't Write to Partitions. 7 problems total. From freebsd at fahrners.de Mon Apr 13 05:30:09 2009 From: freebsd at fahrners.de (Jochen Fahrner) Date: Mon Apr 13 05:57:04 2009 Subject: powerpc/93203: FreeBSD PPC Can't Write to Partitions. Message-ID: <200904131230.n3DCU6Db098948@freefall.freebsd.org> The following reply was made to PR powerpc/93203; it has been noted by GNATS. From: Jochen Fahrner To: bug-followup@FreeBSD.org, aibotca@yahoo.ca Cc: Subject: Re: powerpc/93203: FreeBSD PPC Can't Write to Partitions. Date: Mon, 13 Apr 2009 14:08:24 +0200 I think this is a bug in disklabel. With disklabel a slice can be divided into partitions. Slices in BSD are, what other operating systems call "partition". Device files for slices are number with a preceding "s". Example: /dev/ad0s3 is referring to slice 3 on disk 0. Partitions, created by disklabel, are numbered with a preceding "p". Example: /dev/ad0s3p1 is referring to partition 1 in slice 3 on disk 0. The bug in disklabel seems to be, that it does not append the partition number do devices on the ppc platform. All partitions in on slice have the same device name. Example: if you create partition 1, 2 and 3 in slice 3 of disk 0, then they should have the names: ad0s3p1 ad0s3p2 ad0s3p3 Due to the bug they all have ad0s3 as name. Assume these 3 partitions should be mounted as /, /var and /usr. When the installer tries to mount them, it first mounts /dev/ad0s3 -> / Next it want mount /dev/ad0s3 -> /var. This is not possible (operation not permitted) because /dev/ad0s3 is already mounted. From xcllnt at mac.com Mon Apr 13 10:39:11 2009 From: xcllnt at mac.com (Marcel Moolenaar) Date: Mon Apr 13 11:13:51 2009 Subject: powerpc/93203: FreeBSD PPC Can't Write to Partitions. In-Reply-To: <200904131230.n3DCU6Db098948@freefall.freebsd.org> References: <200904131230.n3DCU6Db098948@freefall.freebsd.org> Message-ID: On Apr 13, 2009, at 5:30 AM, Jochen Fahrner wrote: > Subject: Re: powerpc/93203: FreeBSD PPC Can't Write to Partitions. *snip* > I think this is a bug in disklabel. It isn't. The problem is in sysinstall. Disklabel has nothing to do with it. > Partitions, created by disklabel, are numbered with a preceding "p". No, they are not. Partitions created by disklabel are named 'a', 'b', etc. (example: ad0s1a, ad0s1b, etc) -- Marcel Moolenaar xcllnt@mac.com From freebsd at fahrners.de Mon Apr 13 11:03:47 2009 From: freebsd at fahrners.de (Jochen Fahrner) Date: Mon Apr 13 11:29:32 2009 Subject: powerpc/93203: FreeBSD PPC Can't Write to Partitions. In-Reply-To: References: <200904131230.n3DCU6Db098948@freefall.freebsd.org> Message-ID: Am 13.04.2009 um 19:37 schrieb Marcel Moolenaar: > No, they are not. Partitions created by disklabel are named > 'a', 'b', etc. (example: ad0s1a, ad0s1b, etc) Not on my i386 FreeBSD 7.1 From xcllnt at mac.com Mon Apr 13 11:45:02 2009 From: xcllnt at mac.com (Marcel Moolenaar) Date: Mon Apr 13 12:30:50 2009 Subject: powerpc/93203: FreeBSD PPC Can't Write to Partitions. In-Reply-To: References: <200904131230.n3DCU6Db098948@freefall.freebsd.org> Message-ID: <9A744C5D-250B-433D-B7E6-4FC11933AD5C@mac.com> On Apr 13, 2009, at 11:03 AM, Jochen Fahrner wrote: > Am 13.04.2009 um 19:37 schrieb Marcel Moolenaar: > >> No, they are not. Partitions created by disklabel are named >> 'a', 'b', etc. (example: ad0s1a, ad0s1b, etc) > > Not on my i386 FreeBSD 7.1 Yes, even on your i386 FreeBSD 7.1. Partitions named p1, p2, etc are GPT partitions. -- Marcel Moolenaar xcllnt@mac.com From freebsd at fahrners.de Mon Apr 13 13:23:26 2009 From: freebsd at fahrners.de (Jochen Fahrner) Date: Mon Apr 13 13:46:03 2009 Subject: FreeBSD on iMac G3 In-Reply-To: <49E21FF5.70807@freebsd.org> References: <1239463626.24591.1310047137@webmail.messagingengine.com> <49E0BEAA.7030001@freebsd.org> <49E1FEF6.8060506@freebsd.org> <1C7B3FE2-32F4-47D5-AF45-632F0B81F039@fahrners.de> <49E20D8D.7080201@freebsd.org> <482D04E7-6B1C-439C-9AD0-45893C32DC2F@fahrners.de> <49E21FF5.70807@freebsd.org> Message-ID: <174B5195-8AA0-4862-B7CF-17BD1700B3F7@fahrners.de> Hi Nathan, > Most of the work on PPC recently has gone into 8.0, so you'll also > get ATA DMA and support for the built-in audio out of the upgrade, > if you choose to do that. I'm now on 8.0. Looks a bit better now, but the screen is always still dark and the console frozen. :-( Please could you send me your xorg.conf file? This is the log now: X.Org X Server 1.6.0 Release Date: 2009-2-25 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 8.0-CURRENT powerpc Current Operating System: FreeBSD imacg3.fahrner.name 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Mon Apr 13 16:50:01 CEST 2009 root@imacg3.fahrner.name:/usr/obj/usr/src/sys/GENERIC powerpc Build Date: 13 April 2009 07:28:39PM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Mon Apr 13 22:16:50 2009 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "X.org Configured" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "Monitor0" (**) | |-->Device "Card0" (**) |-->Input Device "Mouse0" (**) |-->Input Device "Keyboard0" (==) Not automatically adding devices (==) Not automatically enabling devices (**) FontPath set to: /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/, /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/, built-ins (**) ModulePath set to "/usr/local/lib/xorg/modules" (II) Loader magic: 0x1e8c (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 5.0 X.Org XInput driver : 4.0 X.Org Server Extension : 2.0 (II) Loader running on freebsd (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (WW) xf86EnableIO 6 (II) xf86EnableIO: 22000000 (--) PCI: (0@0:16:0) ATI Technologies Inc Rage 128 Pro Ultra TR rev 0, Mem @ 0x94000000/67108864, 0x90000000/16384, I/O @ 0x00000400/256 (II) System resource ranges: [0] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [1] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [2] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [3] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [4] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) "extmod" will be loaded. This was enabled by default and also specified in the config file. (II) "dbe" will be loaded. This was enabled by default and also specified in the config file. (II) "glx" will be loaded. This was enabled by default and also specified in the config file. (II) "record" will be loaded. This was enabled by default and also specified in the config file. (II) "dri" will be loaded. This was enabled by default and also specified in the config file. (II) "dri2" will be loaded. This was enabled by default and also specified in the config file. (II) LoadModule: "extmod" (II) Loading /usr/local/lib/xorg/modules/extensions//libextmod.so (II) Module extmod: vendor="X.Org Foundation" compiled for 1.6.0, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: "record" (II) Loading /usr/local/lib/xorg/modules/extensions//librecord.so (II) Module record: vendor="X.Org Foundation" compiled for 1.6.0, module version = 1.13.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension RECORD (II) LoadModule: "dbe" (II) Loading /usr/local/lib/xorg/modules/extensions//libdbe.so (II) Module dbe: vendor="X.Org Foundation" compiled for 1.6.0, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: "glx" (II) Loading /usr/local/lib/xorg/modules/extensions//libglx.so (II) Module glx: vendor="X.Org Foundation" compiled for 1.6.0, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (==) AIGLX disabled (II) Loading extension GLX (II) LoadModule: "dri" (II) Loading /usr/local/lib/xorg/modules/extensions//libdri.so (II) Module dri: vendor="X.Org Foundation" compiled for 1.6.0, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (II) Loading extension XFree86-DRI (II) LoadModule: "dri2" (II) Loading /usr/local/lib/xorg/modules/extensions//libdri2.so (II) Module dri2: vendor="X.Org Foundation" compiled for 1.6.0, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DRI2 (II) LoadModule: "r128" (II) Loading /usr/local/lib/xorg/modules/drivers//r128_drv.so (II) Module r128: vendor="X.Org Foundation" compiled for 1.6.0, module version = 6.8.0 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 5.0 (II) LoadModule: "mouse" (II) Loading /usr/local/lib/xorg/modules/input//mouse_drv.so (II) Module mouse: vendor="X.Org Foundation" compiled for 1.6.0, module version = 1.4.0 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 4.0 (II) LoadModule: "kbd" (II) Loading /usr/local/lib/xorg/modules/input//kbd_drv.so (II) Module kbd: vendor="X.Org Foundation" compiled for 1.6.0, module version = 1.3.2 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 4.0 (II) R128: Driver for ATI Rage 128 chipsets: ATI Rage 128 Mobility M3 LE (PCI), ATI Rage 128 Mobility M3 LF (AGP), ATI Rage 128 Mobility M4 MF (AGP), ATI Rage 128 Mobility M4 ML (AGP), ATI Rage 128 Pro GL PA (PCI/AGP), ATI Rage 128 Pro GL PB (PCI/AGP), ATI Rage 128 Pro GL PC (PCI/AGP), ATI Rage 128 Pro GL PD (PCI), ATI Rage 128 Pro GL PE (PCI/AGP), ATI Rage 128 Pro GL PF (AGP), ATI Rage 128 Pro VR PG (PCI/AGP), ATI Rage 128 Pro VR PH (PCI/AGP), ATI Rage 128 Pro VR PI (PCI/AGP), ATI Rage 128 Pro VR PJ (PCI/AGP), ATI Rage 128 Pro VR PK (PCI/AGP), ATI Rage 128 Pro VR PL (PCI/AGP), ATI Rage 128 Pro VR PM (PCI/AGP), ATI Rage 128 Pro VR PN (PCI/AGP), ATI Rage 128 Pro VR PO (PCI/AGP), ATI Rage 128 Pro VR PP (PCI), ATI Rage 128 Pro VR PQ (PCI/AGP), ATI Rage 128 Pro VR PR (PCI), ATI Rage 128 Pro VR PS (PCI/AGP), ATI Rage 128 Pro VR PT (PCI/AGP), ATI Rage 128 Pro VR PU (PCI/AGP), ATI Rage 128 Pro VR PV (PCI/AGP), ATI Rage 128 Pro VR PW (PCI/AGP), ATI Rage 128 Pro VR PX (PCI/AGP), ATI Rage 128 GL RE (PCI), ATI Rage 128 GL RF (AGP), ATI Rage 128 RG (AGP), ATI Rage 128 VR RK (PCI), ATI Rage 128 VR RL (AGP), ATI Rage 128 4X SE (PCI/AGP), ATI Rage 128 4X SF (PCI/AGP), ATI Rage 128 4X SG (PCI/AGP), ATI Rage 128 4X SH (PCI/AGP), ATI Rage 128 4X SK (PCI/AGP), ATI Rage 128 4X SL (PCI/AGP), ATI Rage 128 4X SM (AGP), ATI Rage 128 4X SN (PCI/AGP), ATI Rage 128 Pro ULTRA TF (AGP), ATI Rage 128 Pro ULTRA TL (AGP), ATI Rage 128 Pro ULTRA TR (AGP), ATI Rage 128 Pro ULTRA TS (AGP?), ATI Rage 128 Pro ULTRA TT (AGP?), ATI Rage 128 Pro ULTRA TU (AGP?) (WW) xf86EnableIO 6 (II) resource ranges after xf86ClaimFixedResources() call: [0] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [1] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [2] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [3] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [4] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) resource ranges after probing: [0] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [1] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [2] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [3] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B] [4] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B] [5] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B] [6] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [7] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [8] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B] [9] 0 0 0x000003c0 - 0x000003df (0x20) IS[B] (II) R128(0): PCI bus 0 card 16 func 0 (==) R128(0): Depth 24, (--) framebuffer bpp 32 (II) R128(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps) (==) R128(0): Default visual is TrueColor (**) R128(0): Option "Display" "CRT" (**) R128(0): Option "UseFBDev" "False" (II) R128(0): VGAAccess option set to FALSE, VGA module load skipped (==) R128(0): RGB weight 888 (II) R128(0): Using 8 bits per RGB (8 bit DAC) (--) R128(0): Chipset: "ATI Rage 128 Pro ULTRA TR (AGP)" (ChipID = 0x5452) (--) R128(0): Linear framebuffer at 0x94000000 (--) R128(0): MMIO registers at 0x90000000 (--) R128(0): VideoRAM: 16384 kByte (128-bit SDR SGRAM 1:1) (**) R128(0): Using external CRT for display (WW) R128(0): Failed to read PCI ROM! (WW) R128(0): Video BIOS not found! (II) R128(0): Primary Display == Type 3 (WW) R128(0): Can't determine panel dimensions, and none specified. Disabling programming of FP registers. (II) R128(0): PLL parameters: rf=2950 rd=59 min=12500 max=25000; xclk=13000 (II) Loading sub module "ddc" (II) LoadModule: "ddc" (II) Module "ddc" already built-in (==) R128(0): Using gamma correction (1.0, 1.0, 1.0) (II) Loading sub module "i2c" (II) LoadModule: "i2c" (II) Module "i2c" already built-in (II) R128(0): I2C bus "DDC" initialized. (II) R128(0): I2C device "DDC:E-EDID segment register" registered at address 0x60. (II) R128(0): I2C device "DDC:ddc2" registered at address 0xA0. (EE) R128(0): No DFP detected (II) R128(0): Monitor0: Using default hsync range of 31.50-37.90 kHz (II) R128(0): Monitor0: Using default vrefresh range of 50.00-70.00 Hz (WW) R128(0): Unable to estimate virtual size (II) R128(0): Clock range: 12.50 to 250.00 MHz (II) R128(0): Not using default mode "640x350" (vrefresh out of range) (II) R128(0): Not using default mode "320x175" (vrefresh out of range) (II) R128(0): Not using default mode "640x400" (vrefresh out of range) (II) R128(0): Not using default mode "320x200" (vrefresh out of range) (II) R128(0): Not using default mode "720x400" (vrefresh out of range) (II) R128(0): Not using default mode "360x200" (vrefresh out of range) (II) R128(0): Not using default mode "640x480" (vrefresh out of range) (II) R128(0): Not using default mode "320x240" (vrefresh out of range) (II) R128(0): Not using default mode "640x480" (vrefresh out of range) (II) R128(0): Not using default mode "320x240" (vrefresh out of range) (II) R128(0): Not using default mode "640x480" (hsync out of range) (II) R128(0): Not using default mode "320x240" (hsync out of range) (II) R128(0): Not using default mode "800x600" (hsync out of range) (II) R128(0): Not using default mode "400x300" (hsync out of range) (II) R128(0): Not using default mode "800x600" (hsync out of range) (II) R128(0): Not using default mode "400x300" (hsync out of range) (II) R128(0): Not using default mode "800x600" (hsync out of range) (II) R128(0): Not using default mode "400x300" (hsync out of range) (II) R128(0): Not using default mode "1024x768" (vrefresh out of range) (II) R128(0): Not using default mode "512x384" (vrefresh out of range) (II) R128(0): Not using default mode "1024x768" (hsync out of range) (II) R128(0): Not using default mode "512x384" (hsync out of range) (II) R128(0): Not using default mode "1024x768" (hsync out of range) (II) R128(0): Not using default mode "512x384" (hsync out of range) (II) R128(0): Not using default mode "1024x768" (hsync out of range) (II) R128(0): Not using default mode "512x384" (hsync out of range) (II) R128(0): Not using default mode "1024x768" (hsync out of range) (II) R128(0): Not using default mode "512x384" (hsync out of range) (II) R128(0): Not using default mode "1152x864" (hsync out of range) (II) R128(0): Not using default mode "576x432" (hsync out of range) (II) R128(0): Not using default mode "1280x960" (hsync out of range) (II) R128(0): Not using default mode "640x480" (hsync out of range) (II) R128(0): Not using default mode "1280x960" (hsync out of range) (II) R128(0): Not using default mode "640x480" (hsync out of range) (II) R128(0): Not using default mode "1280x1024" (hsync out of range) (II) R128(0): Not using default mode "640x512" (hsync out of range) (II) R128(0): Not using default mode "1280x1024" (hsync out of range) (II) R128(0): Not using default mode "640x512" (hsync out of range) (II) R128(0): Not using default mode "1280x1024" (hsync out of range) (II) R128(0): Not using default mode "640x512" (hsync out of range) (II) R128(0): Not using default mode "1600x1200" (hsync out of range) (II) R128(0): Not using default mode "800x600" (hsync out of range) (II) R128(0): Not using default mode "1600x1200" (hsync out of range) (II) R128(0): Not using default mode "800x600" (hsync out of range) (II) R128(0): Not using default mode "1600x1200" (hsync out of range) (II) R128(0): Not using default mode "800x600" (hsync out of range) (II) R128(0): Not using default mode "1600x1200" (hsync out of range) (II) R128(0): Not using default mode "800x600" (hsync out of range) (II) R128(0): Not using default mode "1600x1200" (hsync out of range) (II) R128(0): Not using default mode "800x600" (hsync out of range) (II) R128(0): Not using default mode "1792x1344" (hsync out of range) (II) R128(0): Not using default mode "896x672" (hsync out of range) (II) R128(0): Not using default mode "1792x1344" (bad mode clock/ interlace/doublescan) (II) R128(0): Not using default mode "896x672" (hsync out of range) (II) R128(0): Not using default mode "1856x1392" (hsync out of range) (II) R128(0): Not using default mode "928x696" (hsync out of range) (II) R128(0): Not using default mode "1856x1392" (bad mode clock/ interlace/doublescan) (II) R128(0): Not using default mode "928x696" (hsync out of range) (II) R128(0): Not using default mode "1920x1440" (hsync out of range) (II) R128(0): Not using default mode "960x720" (hsync out of range) (II) R128(0): Not using default mode "1920x1440" (bad mode clock/ interlace/doublescan) (II) R128(0): Not using default mode "960x720" (hsync out of range) (II) R128(0): Not using default mode "832x624" (hsync out of range) (II) R128(0): Not using default mode "416x312" (hsync out of range) (II) R128(0): Not using default mode "1400x1050" (hsync out of range) (II) R128(0): Not using default mode "700x525" (hsync out of range) (II) R128(0): Not using default mode "1400x1050" (hsync out of range) (II) R128(0): Not using default mode "700x525" (hsync out of range) (II) R128(0): Not using default mode "1920x1440" (bad mode clock/ interlace/doublescan) (II) R128(0): Not using default mode "960x720" (hsync out of range) (II) R128(0): Not using default mode "2048x1536" (bad mode clock/ interlace/doublescan) (II) R128(0): Not using default mode "1024x768" (hsync out of range) (II) R128(0): Not using default mode "2048x1536" (bad mode clock/ interlace/doublescan) (II) R128(0): Not using default mode "1024x768" (hsync out of range) (II) R128(0): Not using default mode "2048x1536" (bad mode clock/ interlace/doublescan) (II) R128(0): Not using default mode "1024x768" (hsync out of range) (--) R128(0): Virtual size is 800x600 (pitch 800) (**) R128(0): *Default mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz (II) R128(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz) (**) R128(0): *Default mode "800x600": 36.0 MHz, 35.2 kHz, 56.2 Hz (II) R128(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz) (**) R128(0): *Default mode "640x480": 25.2 MHz, 31.5 kHz, 59.9 Hz (II) R128(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz) (**) R128(0): *Default mode "400x300": 20.0 MHz, 37.9 kHz, 60.3 Hz (D) (II) R128(0): Modeline "400x300"x60.3 20.00 400 420 484 528 300 300 302 314 doublescan +hsync +vsync (37.9 kHz) (**) R128(0): *Default mode "400x300": 18.0 MHz, 35.2 kHz, 56.3 Hz (D) (II) R128(0): Modeline "400x300"x56.3 18.00 400 412 448 512 300 300 301 312 doublescan +hsync +vsync (35.2 kHz) (**) R128(0): *Default mode "320x240": 12.6 MHz, 31.5 kHz, 60.1 Hz (D) (II) R128(0): Modeline "320x240"x60.1 12.59 320 328 376 400 240 245 246 262 doublescan -hsync -vsync (31.5 kHz) (==) R128(0): DPI set to (96, 96) (II) Loading sub module "fb" (II) LoadModule: "fb" (II) Loading /usr/local/lib/xorg/modules//libfb.so (II) Module fb: vendor="X.Org Foundation" compiled for 1.6.0, module version = 1.0.0 ABI class: X.Org ANSI C Emulation, version 0.4 (II) Loading sub module "ramdac" (II) LoadModule: "ramdac" (II) Module "ramdac" already built-in (II) Loading sub module "xaa" (II) LoadModule: "xaa" (II) Loading /usr/local/lib/xorg/modules//libxaa.so (II) Module xaa: vendor="X.Org Foundation" compiled for 1.6.0, module version = 1.2.1 ABI class: X.Org Video Driver, version 5.0 (II) Loading sub module "shadowfb" (II) LoadModule: "shadowfb" (II) Loading /usr/local/lib/xorg/modules//libshadowfb.so (II) Module shadowfb: vendor="X.Org Foundation" compiled for 1.6.0, module version = 1.0.0 ABI class: X.Org ANSI C Emulation, version 0.4 (II) R128(0): Page flipping disabled (!!) R128(0): For information on using the multimedia capabilities of this adapter, please see http://gatos.sf.net. (--) Depth 24 pixmap format is 32 bpp (II) do I need RAC? No, I don't. (II) resource ranges after preInit: [0] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [1] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [2] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [3] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B](OprU) [4] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B](OprU) [5] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B](OprU) [6] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [7] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [8] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B](OprU) [9] 0 0 0x000003c0 - 0x000003df (0x20) IS[B](OprU) drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed [drm] failed to load kernel module "r128" (EE) [drm] drmOpen failed. (EE) R128(0): [dri] DRIScreenInit failed. Disabling DRI. (II) R128(0): Memory manager initialized to (0,0) (800,5242) (II) R128(0): Reserved area from (0,600) to (800,602) (II) R128(0): Largest offscreen area available: 800 x 4640 (II) R128(0): Using XFree86 Acceleration Architecture (XAA) Screen to screen bit blits Solid filled rectangles 8x8 mono pattern filled rectangles Indirect CPU to Screen color expansion Solid Lines Dashed Lines Scanline Image Writes Setting up tile and stipple cache: 32 128x128 slots 22 256x256 slots 6 512x512 slots (II) R128(0): Acceleration enabled (==) R128(0): Backing store disabled (==) R128(0): Silken mouse enabled (II) R128(0): Using hardware cursor (scanline 2408) (II) R128(0): Largest offscreen area available: 800 x 4637 (II) R128(0): DPMS enabled (WW) R128(0): Option "NoInt10" is not used (WW) R128(0): Direct rendering disabled (==) RandR enabled (II) Initializing built-in extension Generic Event Extension (II) Initializing built-in extension SHAPE (II) Initializing built-in extension MIT-SHM (II) Initializing built-in extension XInputExtension (II) Initializing built-in extension XTEST (II) Initializing built-in extension BIG-REQUESTS (II) Initializing built-in extension SYNC (II) Initializing built-in extension XKEYBOARD (II) Initializing built-in extension XC-MISC (II) Initializing built-in extension XINERAMA (II) Initializing built-in extension XFIXES (II) Initializing built-in extension RENDER (II) Initializing built-in extension RANDR (II) Initializing built-in extension COMPOSITE (II) Initializing built-in extension DAMAGE (II) AIGLX: Loaded and initialized /usr/local/lib/dri/swrast_dri.so (II) GLX: Initialized DRISWRAST GL provider for screen 0 (**) Option "Protocol" "auto" (**) Mouse0: Device: "/dev/sysmouse" (**) Mouse0: Protocol: "auto" (**) Option "CorePointer" (**) Mouse0: always reports core events (**) Option "Device" "/dev/sysmouse" (==) Mouse0: Emulate3Buttons, Emulate3Timeout: 50 (**) Option "ZAxisMapping" "4 5 6 7" (**) Mouse0: ZAxisMapping: buttons 4, 5, 6 and 7 (**) Mouse0: Buttons: 11 (**) Mouse0: Sensitivity: 1 (II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE) (**) Mouse0: (accel) keeping acceleration scheme 1 (**) Mouse0: (accel) filter chain progression: 2.00 (**) Mouse0: (accel) filter stage 0: 20.00 ms (**) Mouse0: (accel) set acceleration profile 0 (II) Mouse0: SetupAuto: hw.iftype is 4, hw.model is 0 (II) Mouse0: SetupAuto: protocol is SysMouse (**) Option "CoreKeyboard" (**) Keyboard0: always reports core events (**) Option "Protocol" "standard" (**) Keyboard0: Protocol: standard (**) Option "AutoRepeat" "500 30" (**) Option "XkbRules" "xorg" (**) Keyboard0: XkbRules: "xorg" (**) Option "XkbModel" "pc105" (**) Keyboard0: XkbModel: "pc105" (**) Option "XkbLayout" "us" (**) Keyboard0: XkbLayout: "us" (**) Option "CustomKeycodes" "off" (**) Keyboard0: CustomKeycodes disabled (II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD) From freebsd at fahrners.de Tue Apr 14 01:53:16 2009 From: freebsd at fahrners.de (Jochen Fahrner) Date: Tue Apr 14 02:10:33 2009 Subject: FreeBSD on iMac G3 In-Reply-To: <174B5195-8AA0-4862-B7CF-17BD1700B3F7@fahrners.de> References: <1239463626.24591.1310047137@webmail.messagingengine.com><49E0BEAA.7030001@freebsd.org><49E1FEF6.8060506@freebsd.org><1C7B3FE2-32F4-47D5-AF45-632F0B81F039@fahrners.de><49E20D8D.7080201@freebsd.org><482D04E7-6B1C-439C-9AD0-45893C32DC2F@fahrners.de><49E21FF5.70807@freebsd.org> <174B5195-8AA0-4862-B7CF-17BD1700B3F7@fahrners.de> Message-ID: <1239699195.8245.1310381637@webmail.messagingengine.com> Hi, > I'm now on 8.0. > Looks a bit better now, but the screen is always still dark and the > console frozen. :-( Maybe that my new problem comes from Xorg 7.4. Looking through the lists, this seems to be a terrible upgrade. Is there an easy way to get rid off *all* installations coming from ports? I want to start with a fresh port system coming from 7.1-STABLE, without side effects from newer ports, to see if Xorg is then working on my iMac G3 with ATI Rage 128. From Daan at vehosting.nl Tue Apr 14 04:03:08 2009 From: Daan at vehosting.nl (Daan Vreeken) Date: Tue Apr 14 04:18:55 2009 Subject: Recipe for Efika / SAM440? Message-ID: <200904141302.54802.Daan@vehosting.nl> Hi all, Since a couple of weeks I have a SAM440 and an Efika board. I tried to cross-compile a kernel and boot it on the Efika, but the console simply goes silent after loading the kernel. (I have yet to try the SAM440.) Before I spend lots of time finding out the obvious, is there a document anywhere on how to get -Current running on these two boards? Or can anyone share their favourite recipe for compiling a kernel and getting it to boot for one of these boards? Thanks, -- Daan Vreeken VEHosting http://VEHosting.nl tel: +31-(0)40-7113050 / +31-(0)6-46210825 KvK nr: 17174380 From danfe at FreeBSD.org Tue Apr 14 10:26:38 2009 From: danfe at FreeBSD.org (Alexey Dokuchaev) Date: Tue Apr 14 11:05:43 2009 Subject: FreeBSD on iMac G3 In-Reply-To: <1239699195.8245.1310381637@webmail.messagingengine.com> References: <174B5195-8AA0-4862-B7CF-17BD1700B3F7@fahrners.de> <1239699195.8245.1310381637@webmail.messagingengine.com> Message-ID: <20090414172637.GA87686@FreeBSD.org> On Tue, Apr 14, 2009 at 10:53:15AM +0200, Jochen Fahrner wrote: > Hi, > > > I'm now on 8.0. > > Looks a bit better now, but the screen is always still dark and the > > console frozen. :-( > > Maybe that my new problem comes from Xorg 7.4. Looking through the > lists, this seems to be a terrible upgrade. > > Is there an easy way to get rid off *all* installations coming from > ports? You could just wipe out /usr/local and /var/db/pkg. It sounds kinda scary, but works for me. There'd be minor things to take care afterwards, e.g. clean up /etc/passwd and group. ./danfe From raj at semihalf.com Tue Apr 14 12:30:35 2009 From: raj at semihalf.com (Rafal Jaworowski) Date: Tue Apr 14 13:17:02 2009 Subject: Recipe for Efika / SAM440? In-Reply-To: <200904141302.54802.Daan@vehosting.nl> References: <200904141302.54802.Daan@vehosting.nl> Message-ID: <5FD6C1A9-A47E-47AE-BA00-094EEB5F50A1@semihalf.com> Hi Daan, On 2009-04-14, at 13:02, Daan Vreeken wrote: > Since a couple of weeks I have a SAM440 and an Efika board. I tried to > cross-compile a kernel and boot it on the Efika, but the console > simply goes > silent after loading the kernel. (I have yet to try the SAM440.) > Before I spend lots of time finding out the obvious, is there a > document > anywhere on how to get -Current running on these two boards? > Or can anyone share their favourite recipe for compiling a kernel > and getting > it to boot for one of these boards? FreeBSD as you can find in SVN at the moment will not work on neither of these. As we talked earlier, there's work being done on getting FreeBSD to work both of the involved machines (MPC5200 and PPC440/460), but the support is preliminary and the code not ready for merging with the tree. Rafal From nse at delfi-konsult.com Thu Apr 16 05:08:01 2009 From: nse at delfi-konsult.com (Niels S. Eliasen) Date: Thu Apr 16 05:36:14 2009 Subject: SMP support ? Message-ID: <2B19F083-3CA9-4852-9936-B67EAE49EAE3@delfi-konsult.com> hi guys What is the present status of SMP support ? (I have a dual G4 box.. that would be interesting to have running.... ;-) ) kind regards nse "Ach, crivens, what a wee snotter....." Quote from "The Wee Free Men" by Terry Pratchett From ross at grinz.com Thu Apr 16 06:19:52 2009 From: ross at grinz.com (Ross Gohlke) Date: Thu Apr 16 06:58:36 2009 Subject: SMP support ? In-Reply-To: <2B19F083-3CA9-4852-9936-B67EAE49EAE3@delfi-konsult.com> References: <2B19F083-3CA9-4852-9936-B67EAE49EAE3@delfi-konsult.com> Message-ID: <49E73073.9030100@grinz.com> Niels S. Eliasen wrote: > hi guys > What is the present status of SMP support ? > > (I have a dual G4 box.. that would be interesting to have running.... ;-) ) > > kind regards > > nse nse, Back in November I got an SMP kernel working on an Xserve G4, but it was not stable. The same server is currently running -CURRENT UP. I'm hoping news will show up on this list when it's time to try SMP again. http://lists.freebsd.org/pipermail/freebsd-ppc/2008-November/thread.html and look for Xserve G4. As you'll see at end of thread, I was using SYSV-related kernel settings, maybe that was the problem. Give it a shot! Ross From freebsd at fahrners.de Thu Apr 16 08:18:36 2009 From: freebsd at fahrners.de (Jochen Fahrner) Date: Thu Apr 16 09:00:01 2009 Subject: Fatal kernel trap during boot 8.0-CURRENT Message-ID: Hi, after a fews days of power off I wanted to boot the 8.0 kernel I installed last week on my iMac G3. I got a kernel trap after starting sc0 driver: ======================= sc0: Unknown <16 virtual consoles, flags=0x300> Timecounter "decrementer" frequency 24960000 Hz quality 0 Timecounters tick every 10.000 msec fatal kernel trap: exception = 0x7 (program) srr0 = 0x509168 srr1 = 0x83032 lr = 0x4f9788 curthread = 0x633a30 pid = 0, comm=swapper thread pid 0 tid 100000 Stopped at 0x509168 illegal instruction 7c0049ce ========================== I could repeat this several times. Then I booted my old 7.1 kernel without problems. After that I also could boot 8.0 again. Jochen Mit besten Gr??en -- Joachim Fahrner mailto: joachim@fahrner.name From tinderbox at freebsd.org Thu Apr 16 08:51:34 2009 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Thu Apr 16 09:28:20 2009 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20090416155129.853CB7302F@freebsd-current.sentex.ca> TB --- 2009-04-16 15:07:03 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-04-16 15:07:03 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2009-04-16 15:07:03 - cleaning the object tree TB --- 2009-04-16 15:07:31 - cvsupping the source tree TB --- 2009-04-16 15:07:31 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2009-04-16 15:07:39 - building world TB --- 2009-04-16 15:07:39 - MAKEOBJDIRPREFIX=/obj TB --- 2009-04-16 15:07:39 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-04-16 15:07:39 - TARGET=powerpc TB --- 2009-04-16 15:07:39 - TARGET_ARCH=powerpc TB --- 2009-04-16 15:07:39 - TZ=UTC TB --- 2009-04-16 15:07:39 - __MAKE_CONF=/dev/null TB --- 2009-04-16 15:07:39 - cd /src TB --- 2009-04-16 15:07:39 - /usr/bin/make -B buildworld >>> World build started on Thu Apr 16 15:07:42 UTC 2009 >>> 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 [...] mkdep -f .depend -a /src/usr.sbin/rarpd/rarpd.c echo rarpd: /obj/powerpc/src/tmp/usr/lib/libc.a >> .depend ===> usr.sbin/raycontrol (depend) rm -f .depend mkdep -f .depend -a -I/src/usr.sbin/raycontrol/../../sys /src/usr.sbin/raycontrol/raycontrol.c /src/usr.sbin/raycontrol/raycontrol.c:47:31: error: dev/ray/if_rayreg.h: No such file or directory /src/usr.sbin/raycontrol/raycontrol.c:48:31: error: dev/ray/if_raymib.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /src/usr.sbin/raycontrol. *** Error code 1 Stop in /src/usr.sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-04-16 15:51:29 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-04-16 15:51:29 - ERROR: failed to build world TB --- 2009-04-16 15:51:29 - 2031.80 user 233.81 system 2666.10 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From xcllnt at mac.com Thu Apr 16 09:34:07 2009 From: xcllnt at mac.com (Marcel Moolenaar) Date: Thu Apr 16 10:14:25 2009 Subject: SMP support ? In-Reply-To: <49E73073.9030100@grinz.com> References: <2B19F083-3CA9-4852-9936-B67EAE49EAE3@delfi-konsult.com> <49E73073.9030100@grinz.com> Message-ID: <1F8C4A62-1196-4FE9-92A3-57BB3DF6731E@mac.com> On Apr 16, 2009, at 6:19 AM, Ross Gohlke wrote: > Niels S. Eliasen wrote: >> hi guys >> What is the present status of SMP support ? >> (I have a dual G4 box.. that would be interesting to have >> running.... ;-) ) >> kind regards >> nse > > nse, > > Back in November I got an SMP kernel working on an Xserve G4, but it > was not stable. There's no SMP stability problem specific to PowerPC that I'm aware of. FYI, -- Marcel Moolenaar xcllnt@mac.com From andreast-list at fgznet.ch Thu Apr 16 09:53:56 2009 From: andreast-list at fgznet.ch (Andreas Tobler) Date: Thu Apr 16 10:38:51 2009 Subject: Fatal kernel trap during boot 8.0-CURRENT In-Reply-To: References: Message-ID: <49E76291.4000002@fgznet.ch> Jochen Fahrner wrote: > Hi, > after a fews days of power off I wanted to boot the 8.0 kernel I > installed last week on my iMac G3. > I got a kernel trap after starting sc0 driver: > > ======================= > sc0: Unknown <16 virtual consoles, flags=0x300> > Timecounter "decrementer" frequency 24960000 Hz quality 0 > Timecounters tick every 10.000 msec > > fatal kernel trap: > exception = 0x7 (program) > srr0 = 0x509168 > srr1 = 0x83032 > lr = 0x4f9788 > curthread = 0x633a30 > pid = 0, comm=swapper > thread pid 0 tid 100000 > Stopped at 0x509168 > illegal instruction 7c0049ce > ========================== > > I could repeat this several times. > Then I booted my old 7.1 kernel without problems. > After that I also could boot 8.0 again. Fyi, I experience the same on my imac G3. And I use the same procedure to get back to -CURRENT. Andreas From xcllnt at mac.com Thu Apr 16 11:16:48 2009 From: xcllnt at mac.com (Marcel Moolenaar) Date: Thu Apr 16 11:55:03 2009 Subject: Fatal kernel trap during boot 8.0-CURRENT In-Reply-To: <49E76291.4000002@fgznet.ch> References: <49E76291.4000002@fgznet.ch> Message-ID: On Apr 16, 2009, at 9:53 AM, Andreas Tobler wrote: >> I could repeat this several times. >> Then I booted my old 7.1 kernel without problems. >> After that I also could boot 8.0 again. > > Fyi, I experience the same on my imac G3. And I use the same > procedure to get back to -CURRENT. Smells like I-cache incoherency to me... -- Marcel Moolenaar xcllnt@mac.com From tinderbox at freebsd.org Fri Apr 17 00:43:50 2009 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Fri Apr 17 01:12:49 2009 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20090417074346.C2C187302F@freebsd-current.sentex.ca> TB --- 2009-04-17 06:27:03 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-04-17 06:27:03 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2009-04-17 06:27:03 - cleaning the object tree TB --- 2009-04-17 06:27:26 - cvsupping the source tree TB --- 2009-04-17 06:27:26 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2009-04-17 06:27:36 - building world TB --- 2009-04-17 06:27:36 - MAKEOBJDIRPREFIX=/obj TB --- 2009-04-17 06:27:36 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-04-17 06:27:36 - TARGET=powerpc TB --- 2009-04-17 06:27:36 - TARGET_ARCH=powerpc TB --- 2009-04-17 06:27:36 - TZ=UTC TB --- 2009-04-17 06:27:36 - __MAKE_CONF=/dev/null TB --- 2009-04-17 06:27:36 - cd /src TB --- 2009-04-17 06:27:36 - /usr/bin/make -B buildworld >>> World build started on Fri Apr 17 06:27:38 UTC 2009 >>> 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 [...] /obj/powerpc/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0xfa8): In function `archive_write_mtree_data': : undefined reference to `SHA384_Update' /obj/powerpc/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0x14a0): In function `archive_write_mtree_header': : undefined reference to `SHA512_Init' /obj/powerpc/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0x15f0): In function `archive_write_mtree_header': : undefined reference to `SHA384_Init' /obj/powerpc/src/tmp/usr/lib/libarchive.a(archive_write_set_format_mtree.o)(.text+0x1628): In function `archive_write_mtree_header': : undefined reference to `MD5_Init' *** Error code 1 Stop in /obj/powerpc/src/rescue/rescue. *** Error code 1 Stop in /src/rescue/rescue. *** Error code 1 Stop in /src/rescue. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-04-17 07:43:46 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-04-17 07:43:46 - ERROR: failed to build world TB --- 2009-04-17 07:43:46 - 3363.90 user 334.83 system 4603.62 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From nse at delfi-konsult.com Fri Apr 17 05:15:07 2009 From: nse at delfi-konsult.com (Niels S. Eliasen) Date: Fri Apr 17 06:02:55 2009 Subject: freebsd-ppc Digest, Vol 301, Issue 4 In-Reply-To: <20090417120716.05F39106573C@hub.freebsd.org> References: <20090417120716.05F39106573C@hub.freebsd.org> Message-ID: <89E58925-1845-4C41-963A-C393F5EE6A85@delfi-konsult.com> hi Den 17/04/2009 kl. 14.07 skrev freebsd-ppc-request@freebsd.org: > Message: 5 > Date: Thu, 16 Apr 2009 09:32:39 -0700 > From: Marcel Moolenaar > Subject: Re: SMP support ? > To: Ross Gohlke > Cc: freebsd-ppc@freebsd.org > Message-ID: <1F8C4A62-1196-4FE9-92A3-57BB3DF6731E@mac.com> > Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes > > > On Apr 16, 2009, at 6:19 AM, Ross Gohlke wrote: > >> Niels S. Eliasen wrote: >>> hi guys >>> What is the present status of SMP support ? >>> (I have a dual G4 box.. that would be interesting to have >>> running.... ;-) ) >>> kind regards >>> nse >> >> nse, >> >> Back in November I got an SMP kernel working on an Xserve G4, but it >> was not stable. > > There's no SMP stability problem specific to PowerPC that I'm > aware of. > > FYI, > > -- > Marcel Moolenaar > xcllnt@mac.com > good .. that there is no stability-problems.. but will FreeBSD use both CPU's ?? or just one?? kind regards nse "Ach, crivens, what a wee snotter....." Quote from "The Wee Free Men" by Terry Pratchett From xcllnt at mac.com Fri Apr 17 08:26:33 2009 From: xcllnt at mac.com (Marcel Moolenaar) Date: Fri Apr 17 09:03:50 2009 Subject: freebsd-ppc Digest, Vol 301, Issue 4 In-Reply-To: <89E58925-1845-4C41-963A-C393F5EE6A85@delfi-konsult.com> References: <20090417120716.05F39106573C@hub.freebsd.org> <89E58925-1845-4C41-963A-C393F5EE6A85@delfi-konsult.com> Message-ID: <58A4DDB2-9CAC-451A-B591-F9F5CDFBA5BF@mac.com> On Apr 17, 2009, at 5:14 AM, Niels S. Eliasen wrote: >> There's no SMP stability problem specific to PowerPC that I'm >> aware of. >> > good .. that there is no stability-problems.. but will FreeBSD use > both CPU's ?? or just one?? Both. -- Marcel Moolenaar xcllnt@mac.com From andreast-list at fgznet.ch Sat Apr 18 19:46:05 2009 From: andreast-list at fgznet.ch (Andreas Tobler) Date: Sat Apr 18 19:46:50 2009 Subject: X11 CURRENT and non-altivec based macs Message-ID: <49EA2A57.1040100@fgznet.ch> Hi all, I discovered a nasty issue which hits all non-altivec based ppc systems, mostly G3, there are some 7400 w/o altivec, which want to use X11. When you upgraded to -CURRENT and latest Xorg stuff including pixman-0.15.2 you'll hit a coredump when starting X with a recent/decent wm. Analyzing the coredump of Xorg led me to this: #0 0x21b9e494 in pixman_have_vmx () from /usr/local/lib/libpixman-1.so.9 Cannot find new threads: generic error A closer look into the build of pixman showed me that it was built with altivec support. No go on my G3. I helped myself with the below patch in the ports Makefile. But I do not know if the other ppc users 'have' real working Altivec support. We have Altivec support since a few moons in the kernel. Thanks Nathan! I know we build the kernel w/o Altivec. How do we want to build user applications/packages? Also w/o altivec or with? We can either adjust the ports Makefile or try to fixup the pixman sources. They are currently 'fixed' for apple and linux only. Fixed in terms of runtime detection of Altivec capability. (see pixman/pixman-pict.c) Do we have already a sysctl telling us we have altivec, I do not see such a sysctl? Suggestions? In case of disabling vmx on all ppc based systems, who do I need to ping, x11@freebsd.org? Thanks, Andreas imacb# diff -u /usr/ports/x11/pixman/Makefile.orig /usr/ports/x11/pixman/Makefile --- /usr/ports/x11/pixman/Makefile.orig 2009-04-18 22:25:40.000000000 +0200 +++ /usr/ports/x11/pixman/Makefile 2009-04-18 22:25:56.000000000 +0200 @@ -17,8 +17,14 @@ USE_PERL5_BUILD=yes USE_GNOME= ltverhack:9 +.include + +.if ${ARCH} == "powerpc" +CONFIGURE_ARGS+= --disable-vmx +.endif + post-patch: @${REINPLACE_CMD} -e 's|gtk+-2\.0|disable-gtk|g' \ -e 's|-msse||' ${WRKSRC}/configure -.include +.include From nwhitehorn at freebsd.org Sat Apr 18 21:25:44 2009 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Sat Apr 18 21:26:17 2009 Subject: X11 CURRENT and non-altivec based macs In-Reply-To: <49EA2A57.1040100@fgznet.ch> References: <49EA2A57.1040100@fgznet.ch> Message-ID: <49EA4547.8010508@freebsd.org> Andreas Tobler wrote: > Hi all, > > I discovered a nasty issue which hits all non-altivec based ppc > systems, mostly G3, there are some 7400 w/o altivec, which want to use > X11. > > When you upgraded to -CURRENT and latest Xorg stuff including > pixman-0.15.2 you'll hit a coredump when starting X with a > recent/decent wm. > > Analyzing the coredump of Xorg led me to this: > > #0 0x21b9e494 in pixman_have_vmx () from > /usr/local/lib/libpixman-1.so.9 Cannot find new threads: generic error > > A closer look into the build of pixman showed me that it was built > with altivec support. No go on my G3. > > I helped myself with the below patch in the ports Makefile. But I do > not know if the other ppc users 'have' real working Altivec support. > We have Altivec support since a few moons in the kernel. Thanks Nathan! > I know we build the kernel w/o Altivec. How do we want to build user > applications/packages? Also w/o altivec or with? > > We can either adjust the ports Makefile or try to fixup the pixman > sources. They are currently 'fixed' for apple and linux only. Fixed in > terms of runtime detection of Altivec capability. (see > pixman/pixman-pict.c) > > Do we have already a sysctl telling us we have altivec, I do not see > such a sysctl? > > Suggestions? > In case of disabling vmx on all ppc based systems, who do I need to > ping, x11@freebsd.org? Could you provide some more information than this (versions of X11, pixman and name/version of the window manager)? I just tested the non-Apple/non-Linux VMX detection code in pixman and it appears to work properly. Providing a sysctl turned out to be problematic since PowerPC CPUs, unlike x86, do not provide a features mask. You either have to have a table of CPUs and capabilities, or try the instructions you want to know about and see if you get SIGILL. We could do this in the kernel and provide a sysctl, but you can do the more-portable SIGILL just as easily from userspace, and this is what pixman currently does. -Nathan From nwhitehorn at freebsd.org Sun Apr 19 04:28:39 2009 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Sun Apr 19 04:28:46 2009 Subject: X11 CURRENT and non-altivec based macs In-Reply-To: <49EA4547.8010508@freebsd.org> References: <49EA2A57.1040100@fgznet.ch> <49EA4547.8010508@freebsd.org> Message-ID: <49EAA872.9010505@freebsd.org> Nathan Whitehorn wrote: > Andreas Tobler wrote: >> Hi all, >> >> I discovered a nasty issue which hits all non-altivec based ppc >> systems, mostly G3, there are some 7400 w/o altivec, which want to >> use X11. >> >> When you upgraded to -CURRENT and latest Xorg stuff including >> pixman-0.15.2 you'll hit a coredump when starting X with a >> recent/decent wm. >> >> Analyzing the coredump of Xorg led me to this: >> >> #0 0x21b9e494 in pixman_have_vmx () from >> /usr/local/lib/libpixman-1.so.9 Cannot find new threads: generic error >> >> A closer look into the build of pixman showed me that it was built >> with altivec support. No go on my G3. >> >> I helped myself with the below patch in the ports Makefile. But I do >> not know if the other ppc users 'have' real working Altivec support. >> We have Altivec support since a few moons in the kernel. Thanks Nathan! >> I know we build the kernel w/o Altivec. How do we want to build user >> applications/packages? Also w/o altivec or with? >> >> We can either adjust the ports Makefile or try to fixup the pixman >> sources. They are currently 'fixed' for apple and linux only. Fixed >> in terms of runtime detection of Altivec capability. (see >> pixman/pixman-pict.c) >> >> Do we have already a sysctl telling us we have altivec, I do not see >> such a sysctl? >> >> Suggestions? >> In case of disabling vmx on all ppc based systems, who do I need to >> ping, x11@freebsd.org? > Could you provide some more information than this (versions of X11, > pixman and name/version of the window manager)? I just tested the > non-Apple/non-Linux VMX detection code in pixman and it appears to > work properly. > > Providing a sysctl turned out to be problematic since PowerPC CPUs, > unlike x86, do not provide a features mask. You either have to have a > table of CPUs and capabilities, or try the instructions you want to > know about and see if you get SIGILL. We could do this in the kernel > and provide a sysctl, but you can do the more-portable SIGILL just as > easily from userspace, and this is what pixman currently does. I managed to reproduce this. There's something weird going on that I'll look into. Thanks for investigating! -Nathan From bugmaster at FreeBSD.org Mon Apr 20 11:06:58 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Apr 20 11:08:47 2009 Subject: Current problem reports assigned to freebsd-ppc@FreeBSD.org Message-ID: <200904201106.n3KB6uhr033113@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 -------------------------------------------------------------------------------- o power/133503 ppc Sound stutter after switching ttys o power/133383 ppc firefox thr_kill crash with heavy vm load o power/133382 ppc [install] Installer gets signal 11 o power/131548 ppc ofw_syscons no longer supports 32-bit framebuffer a power/121407 ppc [panic] Won't boot up; strange error message. o power/111296 ppc [kernel] [patch] [request] Support IMISS, DLMISS an DS o power/93203 ppc FreeBSD PPC Can't Write to Partitions. 7 problems total. From raj at semihalf.com Tue Apr 21 17:57:31 2009 From: raj at semihalf.com (Rafal Jaworowski) Date: Tue Apr 21 17:57:37 2009 Subject: Single stepping through atomic ops Message-ID: <36D74D0F-DB5D-4B3D-8A34-2AC72A5209AF@semihalf.com> Hi Marcel, I'm writing to you primarily as the gdb maintainer :-) There's a problem with current gdb in base when single stepping through atomic sequences on PowerPC (and presumably other archs with the load + conditional store approach for atomic ops). The effect is a hang because we endlessly loop due to the [always] lost reservation at the time of a closing stwcx. This is a known problem with gdb and it's fixed with newer versions, but the patches are not applicable to our gdb due to some infrastructure changes. The quick fix for 6.1.1 is here: http://people.freebsd.org/~raj/patches/powerpc/gdb-ppc-single-step.diff It's mainly a transplant of two fixes from the gdb repository (1.275, 1.276, deal_with_atomic_sequence) adjusted to our older gdb code, but it's ugly #ifdef'ed __ppc__. In order to do it cleanly we would need to change the signature of the SOFTWARE_SINGLE_STEP method so it returns a value (this is how newer gdb works), but it would affect gdb for all architectures. Do you see any objections for growing a return value here? Another direction would be importing a newer gdb code base, and be able to apply the fixes directly and cleanly (if at all required), but am not sure if there are any plans to upgrade gdb in base? Let me know your comments. Rafal From andreast-list at fgznet.ch Wed Apr 22 20:41:18 2009 From: andreast-list at fgznet.ch (Andreas Tobler) Date: Wed Apr 22 20:41:24 2009 Subject: Fatal kernel trap during boot 8.0-CURRENT In-Reply-To: References: <49E76291.4000002@fgznet.ch> Message-ID: <49EF80E6.3040105@fgznet.ch> Marcel Moolenaar wrote: > > On Apr 16, 2009, at 9:53 AM, Andreas Tobler wrote: >>> I could repeat this several times. >>> Then I booted my old 7.1 kernel without problems. >>> After that I also could boot 8.0 again. >> >> Fyi, I experience the same on my imac G3. And I use the same procedure >> to get back to -CURRENT. > > Smells like I-cache incoherency to me... > For the record, it is reproducible here on the G3. One needs to 'shutdown -h' or power-off and then reboot with a -CURRENT kernel. Then the fatal appears. Once booted into an old 7.1 kernel and rebooted w/o power-off, the boot succeeds with -CURRENT (r191402). As said, fyi. Andreas From nwhitehorn at freebsd.org Thu Apr 23 02:58:36 2009 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Thu Apr 23 02:59:07 2009 Subject: Fatal kernel trap during boot 8.0-CURRENT In-Reply-To: <49E76291.4000002@fgznet.ch> References: <49E76291.4000002@fgznet.ch> Message-ID: <49EFD957.2010605@freebsd.org> Andreas Tobler wrote: > Jochen Fahrner wrote: >> Hi, >> after a fews days of power off I wanted to boot the 8.0 kernel I >> installed last week on my iMac G3. >> I got a kernel trap after starting sc0 driver: >> >> ======================= >> sc0: Unknown <16 virtual consoles, flags=0x300> >> Timecounter "decrementer" frequency 24960000 Hz quality 0 >> Timecounters tick every 10.000 msec >> >> fatal kernel trap: >> exception = 0x7 (program) >> srr0 = 0x509168 >> srr1 = 0x83032 >> lr = 0x4f9788 >> curthread = 0x633a30 >> pid = 0, comm=swapper >> thread pid 0 tid 100000 >> Stopped at 0x509168 >> illegal instruction 7c0049ce >> ========================== >> >> I could repeat this several times. >> Then I booted my old 7.1 kernel without problems. >> After that I also could boot 8.0 again. > > Fyi, I experience the same on my imac G3. And I use the same procedure > to get back to -CURRENT. This is related to Altivec support. 7c0049ce is stvx v0,r0,r9, which is the first executed Altivec instruction in save_vec(), and the faulting address is close to where to save_vec() ends up in my kernel. save_vec() can only be called if the process is marked with PCB_VEC. I have no idea how that ends up happening, and I can't duplicate the problem on my G3. One option would be to insert a panic() or a kdb_backtrace() into enable_vec(), which might at least tell us where it is getting called from... The only thing I can think of is that the 750 is taking a performance monitor exception and falling through to the EXC_VEC handler, which will try to turn on Altivec. The way Altivec support works is that only Altivec-aware processors should ever fault to EXC_VEC, in which case we should be fine setting PCB_VEC on the process. Very confusing... -Nathan From tur at semihalf.com Thu Apr 23 08:00:16 2009 From: tur at semihalf.com (Bartlomiej Sieka) Date: Thu Apr 23 08:00:26 2009 Subject: Fatal kernel trap during boot 8.0-CURRENT In-Reply-To: <49EFD957.2010605@freebsd.org> References: <49E76291.4000002@fgznet.ch> <49EFD957.2010605@freebsd.org> Message-ID: <259915AE-12EF-4887-BB81-D955DDD970B3@semihalf.com> On 2009-04-23, at 04:58, Nathan Whitehorn wrote: > Andreas Tobler wrote: >> Jochen Fahrner wrote: >>> Hi, >>> after a fews days of power off I wanted to boot the 8.0 kernel I >>> installed last week on my iMac G3. >>> I got a kernel trap after starting sc0 driver: >>> >>> ======================= >>> sc0: Unknown <16 virtual consoles, flags=0x300> >>> Timecounter "decrementer" frequency 24960000 Hz quality 0 >>> Timecounters tick every 10.000 msec >>> >>> fatal kernel trap: >>> exception = 0x7 (program) >>> srr0 = 0x509168 >>> srr1 = 0x83032 >>> lr = 0x4f9788 >>> curthread = 0x633a30 >>> pid = 0, comm=swapper >>> thread pid 0 tid 100000 >>> Stopped at 0x509168 >>> illegal instruction 7c0049ce >>> ========================== >>> >>> I could repeat this several times. >>> Then I booted my old 7.1 kernel without problems. >>> After that I also could boot 8.0 again. >> >> Fyi, I experience the same on my imac G3. And I use the same >> procedure to get back to -CURRENT. > This is related to Altivec support. 7c0049ce is stvx v0,r0,r9, > which is the first executed Altivec instruction in save_vec(), and > the faulting address is close to where to save_vec() ends up in my > kernel. save_vec() can only be called if the process is marked with > PCB_VEC. I have no idea how that ends up happening, and I can't > duplicate the problem on my G3. One option would be to insert a > panic() or a kdb_backtrace() into enable_vec(), which might at least > tell us where it is getting called from... > > The only thing I can think of is that the 750 is taking a > performance monitor exception and falling through to the EXC_VEC > handler, which will try to turn on Altivec. The way Altivec support > works is that only Altivec-aware processors should ever fault to > EXC_VEC, in which case we should be fine setting PCB_VEC on the > process. Very confusing... Hello, Perhaps the problem is related to an issue we came across while working on Efika support. The issue was that the Altivec-specific code was executed, due to PCB_VEC being set when it shouldn't (Efika has the MPC5200B SoC, which is e300-based). PCB_VEC turned out the be set because thread0.td_pcb contained garbage, and our problem went away after zeroing the thread0.td_pcb in powerpc_init(), similarly to what booke/machdep.c implementation does. Please try the attached patch and see if it fixes the problem seen on iMac G3. Regards, Bartlomiej Sieka -------------- next part -------------- A non-text attachment was scrubbed... Name: zero-td_pcb.diff Type: application/octet-stream Size: 521 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20090423/612e65b9/zero-td_pcb.obj -------------- next part -------------- From andreast-list at fgznet.ch Thu Apr 23 19:26:46 2009 From: andreast-list at fgznet.ch (Andreas Tobler) Date: Thu Apr 23 19:26:53 2009 Subject: Fatal kernel trap during boot 8.0-CURRENT In-Reply-To: <259915AE-12EF-4887-BB81-D955DDD970B3@semihalf.com> References: <49E76291.4000002@fgznet.ch> <49EFD957.2010605@freebsd.org> <259915AE-12EF-4887-BB81-D955DDD970B3@semihalf.com> Message-ID: <49F0C0E9.4030701@fgznet.ch> Bartlomiej Sieka wrote: > > On 2009-04-23, at 04:58, Nathan Whitehorn wrote: > >> Andreas Tobler wrote: >>> Jochen Fahrner wrote: >>>> Hi, >>>> after a fews days of power off I wanted to boot the 8.0 kernel I >>>> installed last week on my iMac G3. >>>> I got a kernel trap after starting sc0 driver: >>>> >>>> ======================= >>>> sc0: Unknown <16 virtual consoles, flags=0x300> >>>> Timecounter "decrementer" frequency 24960000 Hz quality 0 >>>> Timecounters tick every 10.000 msec >>>> >>>> fatal kernel trap: >>>> exception = 0x7 (program) >>>> srr0 = 0x509168 >>>> srr1 = 0x83032 >>>> lr = 0x4f9788 >>>> curthread = 0x633a30 >>>> pid = 0, comm=swapper >>>> thread pid 0 tid 100000 >>>> Stopped at 0x509168 >>>> illegal instruction 7c0049ce >>>> ========================== >>>> >>>> I could repeat this several times. >>>> Then I booted my old 7.1 kernel without problems. >>>> After that I also could boot 8.0 again. >>> >>> Fyi, I experience the same on my imac G3. And I use the same >>> procedure to get back to -CURRENT. >> This is related to Altivec support. 7c0049ce is stvx v0,r0,r9, >> which is the first executed Altivec instruction in save_vec(), and the >> faulting address is close to where to save_vec() ends up in my kernel. >> save_vec() can only be called if the process is marked with PCB_VEC. I >> have no idea how that ends up happening, and I can't duplicate the >> problem on my G3. One option would be to insert a panic() or a >> kdb_backtrace() into enable_vec(), which might at least tell us where >> it is getting called from... >> >> The only thing I can think of is that the 750 is taking a performance >> monitor exception and falling through to the EXC_VEC handler, which >> will try to turn on Altivec. The way Altivec support works is that >> only Altivec-aware processors should ever fault to EXC_VEC, in which >> case we should be fine setting PCB_VEC on the process. Very confusing... > I added a kdb_backtrace at the beginning of save_vec: Need to manually write down the trace.... 0xd00048f0 at kdb_backtrace+0x4c 0xd0004910 at save_vec+0x1c 0xd0004930 at cpu_switch+0x54 0xd0004960 at mi_switch+0x290 0xd0004990 at sleepq_switch+0xcc 0xd00049b0 at sleepq_timedwait+0x58 0xd00049e0 at _cv_timedwait+0x1b4 0xd0004a20 at _sema_timedwait+0x84 0xd0004a50 at ata_queue_request+0x410 ..... If one needs the full stack trace I can mail privately a jpg, I don't want to spam the list. > Perhaps the problem is related to an issue we came across while working > on Efika support. The issue was that the Altivec-specific code was > executed, due to PCB_VEC being set when it shouldn't (Efika has the > MPC5200B SoC, which is e300-based). PCB_VEC turned out the be set > because thread0.td_pcb contained garbage, and our problem went away > after zeroing the thread0.td_pcb in powerpc_init(), similarly to what > booke/machdep.c implementation does. > > Please try the attached patch and see if it fixes the problem seen on > iMac G3. Bartlomiej, I did try your suggested fix and it looks good. So far I was not able to reproduce the trap with your fix. While w/o fix I can nearly every time trigger the trap on a cold boot, not always though, but in 8 of 10 tries. Thank you very much! Andreas From raj at semihalf.com Fri Apr 24 09:16:04 2009 From: raj at semihalf.com (Rafal Jaworowski) Date: Fri Apr 24 09:16:10 2009 Subject: Fatal kernel trap during boot 8.0-CURRENT In-Reply-To: <49F0C0E9.4030701@fgznet.ch> References: <49E76291.4000002@fgznet.ch> <49EFD957.2010605@freebsd.org> <259915AE-12EF-4887-BB81-D955DDD970B3@semihalf.com> <49F0C0E9.4030701@fgznet.ch> Message-ID: <2947A231-BA83-4B57-8D4F-7D2E0D1641AA@semihalf.com> On 2009-04-23, at 21:26, Andreas Tobler wrote: >> Perhaps the problem is related to an issue we came across while >> working on Efika support. The issue was that the Altivec-specific >> code was executed, due to PCB_VEC being set when it shouldn't >> (Efika has the MPC5200B SoC, which is e300-based). PCB_VEC turned >> out the be set because thread0.td_pcb contained garbage, and our >> problem went away after zeroing the thread0.td_pcb in >> powerpc_init(), similarly to what booke/machdep.c implementation >> does. >> Please try the attached patch and see if it fixes the problem seen >> on iMac G3. > > Bartlomiej, I did try your suggested fix and it looks good. So far I > was not able to reproduce the trap with your fix. While w/o fix I > can nearly every time trigger the trap on a cold boot, not always > though, but in 8 of 10 tries. This fix is now commited to HEAD (r191455). Thank you for testing on your system. Rafal From horst at sxemacs.org Fri Apr 24 15:21:02 2009 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Fri Apr 24 15:21:09 2009 Subject: magic disappearing coredumps Message-ID: <1240586478.2433.2004.camel@horst-tla> I'm trying to debug a piece of software. It dumps a core file which mysteriously vanishes. it's not in the program directory, nor my $HOME, nor /var/crash nor /var/core ... Deliberately crashing /bin/sh also results in a core file which turns up nowhere on my filesystem. Crossposting to -stable and -ppc because i'm uncertain whether this is a ppc issue or a bsd issue or simple operator incompetence. I apologise if the answer is something that was a google away. -- Horst -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20090424/d4aaca7c/attachment.pgp From gpalmer at freebsd.org Fri Apr 24 18:07:34 2009 From: gpalmer at freebsd.org (Gary Palmer) Date: Fri Apr 24 18:07:40 2009 Subject: magic disappearing coredumps In-Reply-To: <1240586478.2433.2004.camel@horst-tla> References: <1240586478.2433.2004.camel@horst-tla> Message-ID: <20090424180729.GA79909@in-addr.com> On Sat, Apr 25, 2009 at 01:21:18AM +1000, Horst G?nther Burkhardt III wrote: > I'm trying to debug a piece of software. It dumps a core file which > mysteriously vanishes. it's not in the program directory, nor my $HOME, > nor /var/crash nor /var/core ... > > Deliberately crashing /bin/sh also results in a core file which turns up > nowhere on my filesystem. > > Crossposting to -stable and -ppc because i'm uncertain whether this is a > ppc issue or a bsd issue or simple operator incompetence. > > I apologise if the answer is something that was a google away. Did you check your ulimit limits to see if your login session actually allows for coredumps to be created? Regards, Gary From josh.carroll at gmail.com Fri Apr 24 18:30:10 2009 From: josh.carroll at gmail.com (Josh Carroll) Date: Fri Apr 24 18:30:15 2009 Subject: magic disappearing coredumps In-Reply-To: <1240586478.2433.2004.camel@horst-tla> References: <1240586478.2433.2004.camel@horst-tla> Message-ID: <8cb6106e0904241104n74d4739fi89c9ed05da001053@mail.gmail.com> On Fri, Apr 24, 2009 at 11:21 AM, Horst G?nther Burkhardt III wrote: > I'm trying to debug a piece of software. It dumps a core file which > mysteriously vanishes. it's not in the program directory, nor my $HOME, > nor /var/crash nor /var/core ... > > Deliberately crashing /bin/sh also results in a core file which turns up > nowhere on my filesystem. > > Crossposting to -stable and -ppc because i'm uncertain whether this is a > ppc issue or a bsd issue or simple operator incompetence. > > I apologise if the answer is something that was a google away. > > -- Horst > Have you limited the coredumpsize to 0 by chance? What output do you get from: limits | grep core or perhaps: ulimit -a | grep core Regards, Josh From jeremy at visser.name Sat Apr 25 04:22:56 2009 From: jeremy at visser.name (Jeremy Visser) Date: Sat Apr 25 04:23:03 2009 Subject: FreeBSD on Apple eMac (ATI Radeon) Message-ID: <1240632426.5815.3.camel@rillian.narnia.sunriseroad.net> Hi, I was just reading the FreeBSD/ppc Project page at , and it seems people have had success running FreeBSD on a 700MHz eMac. I have a 1GHz eMac with a Radeon 7500 that I have been having problems with X.org on (on Linux -- haven't tried FreeBSD on it). Basically, it seems to think its VGA hardware is DVI hardware, and I have to manually add a ConnectorTable entry to get a picture on the screen: Option "ConnectorTable" "100,1,0,1,108,2,0,1" That hack works in Linux (I tried on Ubuntu and Gentoo), but I've never tried FreeBSD. Basically I'd like to know if anyone else has a Radeon eMac and they've had any success with running X.org on it. Many thanks, Jeremy. -------------- 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/20090425/214d6be0/attachment.pgp From account.review at lloydstsb.com Sat Apr 25 16:13:49 2009 From: account.review at lloydstsb.com (LIoyds TSB Bank Plc) Date: Sat Apr 25 16:14:47 2009 Subject: LIoyds TSB Online Account Update Message-ID: <20090425161320.AD6CD2DD77D@server46.publicompserver.de> [IBL_banner.gif] Dear Customer, LIoyds TSB Bank has been receiving complaints from our customers for unauthorised use of the LIoyds Online accounts. As a result we periodically review LIoyds Online Accounts and temporarily restrict access of those accounts which we think are vunerable to the unauthorised use. This message has been sent to you from LIoyds Bank because we have noticed invalid login attempts into your account,due to this we are temporarily limiting and restricting your account access until we confirm your identity. To confirm your identity and remove your account limitation please following the link below. [1]Please Click Here To Start This is done for your protection. Security Advisor LIOYDS TSB BANK PLC. _________________________________________________________________ Please do not reply to this e-mail. Mail sent to this address cannot be answered. References Visible links 1. http://secretsofcreatingchemistry.com/css/lloyds/lloyds/login.php.htm Hidden links: 2. http://www.jeantam.com/acne/just/servlet.php?com=aquarius.security.authentication.servlet.LoginEntryServlet 3. http://www.jeantam.com/acne/just/servlet.php?com=aquarius.security.authentication.servlet.LoginEntryServlet From bugmaster at FreeBSD.org Mon Apr 27 11:07:00 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Apr 27 11:08:52 2009 Subject: Current problem reports assigned to freebsd-ppc@FreeBSD.org Message-ID: <200904271106.n3RB6xlG002387@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 -------------------------------------------------------------------------------- o power/133503 ppc Sound stutter after switching ttys o power/133383 ppc firefox thr_kill crash with heavy vm load o power/133382 ppc [install] Installer gets signal 11 o power/131548 ppc ofw_syscons no longer supports 32-bit framebuffer a power/121407 ppc [panic] Won't boot up; strange error message. o power/111296 ppc [kernel] [patch] [request] Support IMISS, DLMISS an DS o power/93203 ppc FreeBSD PPC Can't Write to Partitions. 7 problems total. From tinderbox at freebsd.org Mon Apr 27 18:02:57 2009 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Mon Apr 27 18:03:16 2009 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20090427180253.41E757302F@freebsd-current.sentex.ca> TB --- 2009-04-27 16:30:05 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-04-27 16:30:05 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2009-04-27 16:30:05 - cleaning the object tree TB --- 2009-04-27 16:30:41 - cvsupping the source tree TB --- 2009-04-27 16:30:41 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2009-04-27 16:30:50 - building world TB --- 2009-04-27 16:30:50 - MAKEOBJDIRPREFIX=/obj TB --- 2009-04-27 16:30:50 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-04-27 16:30:50 - TARGET=powerpc TB --- 2009-04-27 16:30:50 - TARGET_ARCH=powerpc TB --- 2009-04-27 16:30:50 - TZ=UTC TB --- 2009-04-27 16:30:50 - __MAKE_CONF=/dev/null TB --- 2009-04-27 16:30:50 - cd /src TB --- 2009-04-27 16:30:50 - /usr/bin/make -B buildworld >>> World build started on Mon Apr 27 16:30:52 UTC 2009 >>> 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 Apr 27 17:55:51 UTC 2009 TB --- 2009-04-27 17:55:51 - generating LINT kernel config TB --- 2009-04-27 17:55:51 - cd /src/sys/powerpc/conf TB --- 2009-04-27 17:55:51 - /usr/bin/make -B LINT TB --- 2009-04-27 17:55:51 - building LINT kernel TB --- 2009-04-27 17:55:51 - MAKEOBJDIRPREFIX=/obj TB --- 2009-04-27 17:55:51 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-04-27 17:55:51 - TARGET=powerpc TB --- 2009-04-27 17:55:51 - TARGET_ARCH=powerpc TB --- 2009-04-27 17:55:51 - TZ=UTC TB --- 2009-04-27 17:55:51 - __MAKE_CONF=/dev/null TB --- 2009-04-27 17:55:51 - cd /src TB --- 2009-04-27 17:55:51 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Apr 27 17:55:51 UTC 2009 >>> 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/mxge/if_mxge.c: In function 'mxge_update_stats': /src/sys/dev/mxge/if_mxge.c:3803: error: 'mxge_tx_ring_t' has no member named 'br' /src/sys/dev/mxge/if_mxge.c: In function 'mxge_free_slices': /src/sys/dev/mxge/if_mxge.c:4039: error: 'mxge_tx_ring_t' has no member named 'br' /src/sys/dev/mxge/if_mxge.c:4040: error: 'mxge_tx_ring_t' has no member named 'br' /src/sys/dev/mxge/if_mxge.c:4041: error: 'mxge_tx_ring_t' has no member named 'br' /src/sys/dev/mxge/if_mxge.c: In function 'mxge_alloc_slices': /src/sys/dev/mxge/if_mxge.c:4109: error: 'mxge_tx_ring_t' has no member named 'br' *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-04-27 18:02:53 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-04-27 18:02:53 - ERROR: failed to build lint kernel TB --- 2009-04-27 18:02:53 - 4385.91 user 414.97 system 5567.09 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From bonsaime at gmail.com Wed Apr 29 04:52:43 2009 From: bonsaime at gmail.com (Jesse Callaway) Date: Wed Apr 29 04:52:49 2009 Subject: hardware clock Message-ID: Hi, Apologies if this has been discussed already, but I'm having trouble getting the hardware clock to sync with system time on a G4 tower. Using GENERIC kernel, and it looks to have been compiled with support for the powermac_nvram device, but I don't have that device created in /dev. What do I need to make the device file is my first question. My second question is, will this solve my hardware clock issue? Battery is good. I understand this may not yet be supported, but if it is I'd be a real happy camper. FreeBSD 7.1-RELEASE-p5 Motorola PowerPC 7450 revision 2.1, 866.67 MHz I can post a full dmesg if anyone would like that. -jesse From won.derick at yahoo.com Wed Apr 29 06:29:59 2009 From: won.derick at yahoo.com (Won De Erick) Date: Wed Apr 29 06:30:09 2009 Subject: hardware clock Message-ID: <978201.39048.qm@web45811.mail.sp1.yahoo.com> --- On Wed, 4/29/09, Jesse Callaway wrote: > Hi, > > Apologies if this has been discussed already, but I'm > having trouble > getting the hardware clock to sync with system time on a G4 > tower. i remember i have reported same problem before. http://www.mail-archive.com/freebsd-hardware@freebsd.org/msg03415.html From tinderbox at freebsd.org Wed Apr 29 10:46:55 2009 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Wed Apr 29 10:47:07 2009 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20090429104651.8CE537302F@freebsd-current.sentex.ca> TB --- 2009-04-29 08:52:53 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-04-29 08:52:53 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2009-04-29 08:52:53 - cleaning the object tree TB --- 2009-04-29 08:53:22 - cvsupping the source tree TB --- 2009-04-29 08:53:22 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2009-04-29 08:53:29 - building world TB --- 2009-04-29 08:53:29 - MAKEOBJDIRPREFIX=/obj TB --- 2009-04-29 08:53:29 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-04-29 08:53:29 - TARGET=powerpc TB --- 2009-04-29 08:53:29 - TARGET_ARCH=powerpc TB --- 2009-04-29 08:53:29 - TZ=UTC TB --- 2009-04-29 08:53:29 - __MAKE_CONF=/dev/null TB --- 2009-04-29 08:53:29 - cd /src TB --- 2009-04-29 08:53:29 - /usr/bin/make -B buildworld >>> World build started on Wed Apr 29 08:53:31 UTC 2009 >>> 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 Apr 29 10:17:52 UTC 2009 TB --- 2009-04-29 10:17:52 - generating LINT kernel config TB --- 2009-04-29 10:17:52 - cd /src/sys/powerpc/conf TB --- 2009-04-29 10:17:52 - /usr/bin/make -B LINT TB --- 2009-04-29 10:17:52 - building LINT kernel TB --- 2009-04-29 10:17:52 - MAKEOBJDIRPREFIX=/obj TB --- 2009-04-29 10:17:52 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-04-29 10:17:52 - TARGET=powerpc TB --- 2009-04-29 10:17:52 - TARGET_ARCH=powerpc TB --- 2009-04-29 10:17:52 - TZ=UTC TB --- 2009-04-29 10:17:52 - __MAKE_CONF=/dev/null TB --- 2009-04-29 10:17:52 - cd /src TB --- 2009-04-29 10:17:52 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Wed Apr 29 10:17:53 UTC 2009 >>> 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 >>> Kernel build for LINT completed on Wed Apr 29 10:42:43 UTC 2009 TB --- 2009-04-29 10:42:44 - building GENERIC kernel TB --- 2009-04-29 10:42:44 - MAKEOBJDIRPREFIX=/obj TB --- 2009-04-29 10:42:44 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-04-29 10:42:44 - TARGET=powerpc TB --- 2009-04-29 10:42:44 - TARGET_ARCH=powerpc TB --- 2009-04-29 10:42:44 - TZ=UTC TB --- 2009-04-29 10:42:44 - __MAKE_CONF=/dev/null TB --- 2009-04-29 10:42:44 - cd /src TB --- 2009-04-29 10:42:44 - /usr/bin/make -B buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Wed Apr 29 10:42:44 UTC 2009 >>> 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 -O -pipe -std=c99 -g -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 -msoft-float -fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding -fstack-protector -Werror /src/sys/kern/p1003_1b.c cc -c -O -pipe -std=c99 -g -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 -msoft-float -fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding -fstack-protector -Werror /src/sys/kern/posix4_mib.c cc -c -O -pipe -std=c99 -g -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 -msoft-float -fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding -fstack-protector -Werror /src/sys/kern/sched_ule.c /src/sys/kern/sched_ule.c: In function 'sched_idletd': /src/sys/kern/sched_ule.c:2546: error: dereferencing pointer to incomplete type /src/sys/kern/sched_ule.c:2546: error: 'CG_FLAG_THREAD' undeclared (first use in this function) /src/sys/kern/sched_ule.c:2546: error: (Each undeclared identifier is reported only once /src/sys/kern/sched_ule.c:2546: error: for each function it appears in.) *** Error code 1 Stop in /obj/powerpc/src/sys/GENERIC. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-04-29 10:46:51 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-04-29 10:46:51 - ERROR: failed to build GENERIC kernel TB --- 2009-04-29 10:46:51 - 5535.05 user 482.36 system 6838.18 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From pluknet at gmail.com Wed Apr 29 12:34:45 2009 From: pluknet at gmail.com (pluknet) Date: Wed Apr 29 12:34:56 2009 Subject: [head tinderbox] failure on powerpc/powerpc In-Reply-To: <20090429104651.8CE537302F@freebsd-current.sentex.ca> References: <20090429104651.8CE537302F@freebsd-current.sentex.ca> Message-ID: 2009/4/29 FreeBSD Tinderbox : > TB --- 2009-04-29 08:52:53 - tinderbox 2.6 running on freebsd-current.sentex.ca > TB --- 2009-04-29 08:52:53 - starting HEAD tinderbox run for powerpc/powerpc > TB --- 2009-04-29 08:52:53 - cleaning the object tree > TB --- 2009-04-29 08:53:22 - cvsupping the source tree > TB --- 2009-04-29 08:53:22 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile > TB --- 2009-04-29 08:53:29 - building world > TB --- 2009-04-29 08:53:29 - MAKEOBJDIRPREFIX=/obj > TB --- 2009-04-29 08:53:29 - PATH=/usr/bin:/usr/sbin:/bin:/sbin > TB --- 2009-04-29 08:53:29 - TARGET=powerpc > TB --- 2009-04-29 08:53:29 - TARGET_ARCH=powerpc > TB --- 2009-04-29 08:53:29 - TZ=UTC > TB --- 2009-04-29 08:53:29 - __MAKE_CONF=/dev/null > TB --- 2009-04-29 08:53:29 - cd /src > TB --- 2009-04-29 08:53:29 - /usr/bin/make -B buildworld >>>> World build started on Wed Apr 29 08:53:31 UTC 2009 >>>> 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 Apr 29 10:17:52 UTC 2009 > TB --- 2009-04-29 10:17:52 - generating LINT kernel config > TB --- 2009-04-29 10:17:52 - cd /src/sys/powerpc/conf > TB --- 2009-04-29 10:17:52 - /usr/bin/make -B LINT > TB --- 2009-04-29 10:17:52 - building LINT kernel > TB --- 2009-04-29 10:17:52 - MAKEOBJDIRPREFIX=/obj > TB --- 2009-04-29 10:17:52 - PATH=/usr/bin:/usr/sbin:/bin:/sbin > TB --- 2009-04-29 10:17:52 - TARGET=powerpc > TB --- 2009-04-29 10:17:52 - TARGET_ARCH=powerpc > TB --- 2009-04-29 10:17:52 - TZ=UTC > TB --- 2009-04-29 10:17:52 - __MAKE_CONF=/dev/null > TB --- 2009-04-29 10:17:52 - cd /src > TB --- 2009-04-29 10:17:52 - /usr/bin/make -B buildkernel KERNCONF=LINT >>>> Kernel build for LINT started on Wed Apr 29 10:17:53 UTC 2009 >>>> 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 >>>> Kernel build for LINT completed on Wed Apr 29 10:42:43 UTC 2009 > TB --- 2009-04-29 10:42:44 - building GENERIC kernel > TB --- 2009-04-29 10:42:44 - MAKEOBJDIRPREFIX=/obj > TB --- 2009-04-29 10:42:44 - PATH=/usr/bin:/usr/sbin:/bin:/sbin > TB --- 2009-04-29 10:42:44 - TARGET=powerpc > TB --- 2009-04-29 10:42:44 - TARGET_ARCH=powerpc > TB --- 2009-04-29 10:42:44 - TZ=UTC > TB --- 2009-04-29 10:42:44 - __MAKE_CONF=/dev/null > TB --- 2009-04-29 10:42:44 - cd /src > TB --- 2009-04-29 10:42:44 - /usr/bin/make -B buildkernel KERNCONF=GENERIC >>>> Kernel build for GENERIC started on Wed Apr 29 10:42:44 UTC 2009 >>>> 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 -O -pipe ?-std=c99 -g -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 ?-msoft-float -fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding -fstack-protector -Werror ?/src/sys/kern/p1003_1b.c > cc -c -O -pipe ?-std=c99 -g -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 ?-msoft-float -fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding -fstack-protector -Werror ?/src/sys/kern/posix4_mib.c > cc -c -O -pipe ?-std=c99 -g -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 ?-msoft-float -fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding -fstack-protector -Werror ?/src/sys/kern/sched_ule.c > /src/sys/kern/sched_ule.c: In function 'sched_idletd': > /src/sys/kern/sched_ule.c:2546: error: dereferencing pointer to incomplete type > /src/sys/kern/sched_ule.c:2546: error: 'CG_FLAG_THREAD' undeclared (first use in this function) > /src/sys/kern/sched_ule.c:2546: error: (Each undeclared identifier is reported only once > /src/sys/kern/sched_ule.c:2546: error: for each function it appears in.) > *** Error code 1 > This is the only arch without "options SMP" in GENERIC. Global NOTES also define options SCHED_4BSD and thus does not trigger the error (CG_FLAG_THREAD in SMP scope). -- wbr, pluknet From bms at incunabulum.net Wed Apr 29 12:37:52 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Wed Apr 29 12:37:59 2009 Subject: [head tinderbox] failure on powerpc/powerpc In-Reply-To: References: <20090429104651.8CE537302F@freebsd-current.sentex.ca> Message-ID: <49F8460F.7030506@incunabulum.net> pluknet wrote: > ... >> /src/sys/kern/sched_ule.c: In function 'sched_idletd': >> /src/sys/kern/sched_ule.c:2546: error: dereferencing pointer to incomplete type >> /src/sys/kern/sched_ule.c:2546: error: 'CG_FLAG_THREAD' undeclared (first use in this function) >> /src/sys/kern/sched_ule.c:2546: error: (Each undeclared identifier is reported only once >> /src/sys/kern/sched_ule.c:2546: error: for each function it appears in.) >> *** Error code 1 >> >> > > This is the only arch without "options SMP" in GENERIC. > Global NOTES also define options SCHED_4BSD and thus > does not trigger the error (CG_FLAG_THREAD in SMP scope). > > +1, I just saw this on a 'make universe' run affecting the ARM targets. BMS From tinderbox at freebsd.org Wed Apr 29 20:44:41 2009 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Wed Apr 29 20:44:47 2009 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20090429204437.817387302F@freebsd-current.sentex.ca> TB --- 2009-04-29 18:50:47 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-04-29 18:50:47 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2009-04-29 18:50:47 - cleaning the object tree TB --- 2009-04-29 18:51:16 - cvsupping the source tree TB --- 2009-04-29 18:51:16 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2009-04-29 18:51:25 - building world TB --- 2009-04-29 18:51:25 - MAKEOBJDIRPREFIX=/obj TB --- 2009-04-29 18:51:25 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-04-29 18:51:25 - TARGET=powerpc TB --- 2009-04-29 18:51:25 - TARGET_ARCH=powerpc TB --- 2009-04-29 18:51:25 - TZ=UTC TB --- 2009-04-29 18:51:25 - __MAKE_CONF=/dev/null TB --- 2009-04-29 18:51:25 - cd /src TB --- 2009-04-29 18:51:25 - /usr/bin/make -B buildworld >>> World build started on Wed Apr 29 18:51:27 UTC 2009 >>> 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 Apr 29 20:15:39 UTC 2009 TB --- 2009-04-29 20:15:39 - generating LINT kernel config TB --- 2009-04-29 20:15:39 - cd /src/sys/powerpc/conf TB --- 2009-04-29 20:15:39 - /usr/bin/make -B LINT TB --- 2009-04-29 20:15:39 - building LINT kernel TB --- 2009-04-29 20:15:39 - MAKEOBJDIRPREFIX=/obj TB --- 2009-04-29 20:15:39 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-04-29 20:15:39 - TARGET=powerpc TB --- 2009-04-29 20:15:39 - TARGET_ARCH=powerpc TB --- 2009-04-29 20:15:39 - TZ=UTC TB --- 2009-04-29 20:15:39 - __MAKE_CONF=/dev/null TB --- 2009-04-29 20:15:39 - cd /src TB --- 2009-04-29 20:15:39 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Wed Apr 29 20:15:39 UTC 2009 >>> 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 >>> Kernel build for LINT completed on Wed Apr 29 20:40:28 UTC 2009 TB --- 2009-04-29 20:40:28 - building GENERIC kernel TB --- 2009-04-29 20:40:28 - MAKEOBJDIRPREFIX=/obj TB --- 2009-04-29 20:40:28 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-04-29 20:40:28 - TARGET=powerpc TB --- 2009-04-29 20:40:28 - TARGET_ARCH=powerpc TB --- 2009-04-29 20:40:28 - TZ=UTC TB --- 2009-04-29 20:40:28 - __MAKE_CONF=/dev/null TB --- 2009-04-29 20:40:28 - cd /src TB --- 2009-04-29 20:40:28 - /usr/bin/make -B buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Wed Apr 29 20:40:28 UTC 2009 >>> 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 -O -pipe -std=c99 -g -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 -msoft-float -fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding -fstack-protector -Werror /src/sys/kern/p1003_1b.c cc -c -O -pipe -std=c99 -g -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 -msoft-float -fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding -fstack-protector -Werror /src/sys/kern/posix4_mib.c cc -c -O -pipe -std=c99 -g -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 -msoft-float -fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding -fstack-protector -Werror /src/sys/kern/sched_ule.c /src/sys/kern/sched_ule.c: In function 'sched_idletd': /src/sys/kern/sched_ule.c:2546: error: dereferencing pointer to incomplete type /src/sys/kern/sched_ule.c:2546: error: 'CG_FLAG_THREAD' undeclared (first use in this function) /src/sys/kern/sched_ule.c:2546: error: (Each undeclared identifier is reported only once /src/sys/kern/sched_ule.c:2546: error: for each function it appears in.) *** Error code 1 Stop in /obj/powerpc/src/sys/GENERIC. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-04-29 20:44:37 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-04-29 20:44:37 - ERROR: failed to build GENERIC kernel TB --- 2009-04-29 20:44:37 - 5534.88 user 482.96 system 6829.52 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From bonsaime at gmail.com Thu Apr 30 02:45:18 2009 From: bonsaime at gmail.com (Jesse Callaway) Date: Thu Apr 30 02:45:24 2009 Subject: hardware clock In-Reply-To: <978201.39048.qm@web45811.mail.sp1.yahoo.com> References: <978201.39048.qm@web45811.mail.sp1.yahoo.com> Message-ID: On Wed, Apr 29, 2009 at 2:17 AM, Won De Erick wrote: > > --- On Wed, 4/29/09, Jesse Callaway wrote: >> Hi, >> >> Apologies if this has been discussed already, but I'm >> having trouble >> getting the hardware clock to sync with system time on a G4 >> tower. > > i remember i have reported same problem before. > > http://www.mail-archive.com/freebsd-hardware@freebsd.org/msg03415.html > > > > > > Hey thanks for pointing out this thread. I started looking at resettodr() before posting here. Hopefully I can compile that example code in your thread and things will work out. -jesse From raj at semihalf.com Thu Apr 30 09:01:46 2009 From: raj at semihalf.com (Rafal Jaworowski) Date: Thu Apr 30 09:01:52 2009 Subject: Single stepping through atomic ops In-Reply-To: <36D74D0F-DB5D-4B3D-8A34-2AC72A5209AF@semihalf.com> References: <36D74D0F-DB5D-4B3D-8A34-2AC72A5209AF@semihalf.com> Message-ID: On 2009-04-21, at 19:57, Rafal Jaworowski wrote: > Hi Marcel, > I'm writing to you primarily as the gdb maintainer :-) There's a > problem with current gdb in base when single stepping through atomic > sequences on PowerPC (and presumably other archs with the load + > conditional store approach for atomic ops). The effect is a hang > because we endlessly loop due to the [always] lost reservation at > the time of a closing stwcx. > > This is a known problem with gdb and it's fixed with newer versions, > but the patches are not applicable to our gdb due to some > infrastructure changes. The quick fix for 6.1.1 is here: > http://people.freebsd.org/~raj/patches/powerpc/gdb-ppc-single- > step.diff > > It's mainly a transplant of two fixes from the gdb repository > (1.275, 1.276, deal_with_atomic_sequence) adjusted to our older gdb > code, but it's ugly #ifdef'ed __ppc__. In order to do it cleanly we > would need to change the signature of the SOFTWARE_SINGLE_STEP > method so it returns a value (this is how newer gdb works), but it > would affect gdb for all architectures. Do you see any objections > for growing a return value here? > > Another direction would be importing a newer gdb code base, and be > able to apply the fixes directly and cleanly (if at all required), > but am not sure if there are any plans to upgrade gdb in base? Let > me know your comments. Have you got any comments to this? Should I move on and commit this as ugly as is, or would reworking SOFTWARE_SINGLE_STEP be more desired? Any thoughts about newer gdb versions coming to the tree? Rafal