Jun 11, 2016 OpenBSD on a PowerBook G4: A brief overview. This mainly pertains to OpenBSD 5.4 on a PowerPC based Mac. During the OpenBSD install process. TrueOS follows FreeBSD Current, with the latest drivers, security updates, and development tools.

I have a question for the BSD communities in general. Why are the PowerPC ports of all the BSDs so buggy? On NetBSD 6.1.4 I got as far as burning a CD, which OpenFirmware doesn't even consider a valid boot location.

On OpenBSD 5.5 I can install it, but no matter what configuration, I cannot boot it from the HDD. On FreeBSD 10.0 I can install it, boot it, but I cannot install anything. It can't download pkg. (I am bamboozled as to why they would not include this on the install CDs.) 'portsnap fetch' downloads the ports tree, finishes verifying it, and just sits there without releasing my console. I am forced to reboot the computer with ctrl+alt+del. Upon logging back in and attempting portsnap update, it tells me to download it (again).

Why do none of the three BSDs with PowerPC support work at all on them and fail at the most basic things? I've installed Debian 6 on several PowerPC macs in the past, and I have not run into a single typo, let alone show-stopping bug. EDIT: Just so people know, I am not bashing the BSDs. I far prefer FreeBSD to Linux (at least on x86 hardware) but I cannot get any of them to work on PowerPC for one reason or another.

Download Game Sao Untuk Pcs. Luck of the draw with hardware can be like that sometimes. The people capable of fixing boot issues are very few and far between, and can't possibly have all the hardware configurations out there.

Using a less common platform like PPC with a much smaller dev team like the BSDs is really just asking for trouble, I'm afraid. FreeBSD failed to boot or install on any of my x86 hardware (which was mostly cheap junk) from 5.0 up until 8.x when I just gave up.

Obviously it must have worked for most people, I was just unlucky. Tried again at 10.0, and so far that's worked perfectly on every system I've tried it on. I'm not asking for tech support at this point. I've given up the prospect of *BSD on PowerPC, it's never going to happen, as I don't have the time to sit here for 12 hours trying to find why something this basic isn't working like it's supposed to because it wasn't tested before release.

I am having to fix or find workarounds at every turn with the BSDs on PPC. For example, for some reason FreeBSD didn't set the system time properly during installation, and ntpd doesn't change the time if the difference is over 1k seconds? Why on earth would you put such a limit in?

The 'date' man page is horribly misdocumented, as apparently using seconds, and the century values when setting the time is an illegal format. My point is why is this stuff not being tested? I mean these are such basic things that this should never happen in a million years, yet here it is. It wasn't tested before release. This is probably close to the heart of the matter. PowerPC just isn't that common compared to x86.

It can't be as well tested. Developers may easily miss differences between particular PPC platforms. Your model may have its own unique quirks or non-standard stuff that the software developer never dealt with. I also could never get anything to work on PPC (I attempted with an old Mac about a decade ago). My conclusion was that much of the problem stemmed from platform implementations failing to meet standards.

Sometimes you'd expect OpenFirmware to do one thing, but then it does something else. Why on earth would you put such a limit in? I think NTP is designed to adjust for small variations among clocks.

The idea is to keep the clock from drifting over a long period of time and stay accurate. If your time/date is COMPLETELY off then this should be brought to the sysadmin's attention and be dealt with through configuration. I think NTP is designed to adjust for small variations among clocks.

The idea is to keep the clock from drifting over a long period of time and stay accurate. If your time/date is COMPLETELY off then this should be brought to the sysadmin's attention and be dealt with through configuration. At the very least they should make sure their documentation is up to date and correct. That is one thing I really like about OpenBSD's man pages, I almost never need to google how to use something, or about how it works. Also, I am confident OpenFirmWare is working correctly, as FreeBSD has no problem booting from it, and if there were quirks, the developer of the ofwboot loader could look at FreeBSD's to make sure. As for NetBSD I have no idea what they did to make the CD unbootable.

FreeBSD 10 was the first release that officially released with Clang as the default, base compiler. Most ports, unless specially marked, now compile using the base ('pre-installed') clang. However, clang development is moderately rapid, and so the version of clang in base can be out of date frequently - not only do we have to wait for clang to be imported into base, but then we have to recompile from base ( make world) to install it; the other alternative for the more enterprising operator would be to navigate the source tree and attempt to rebuild and reinstall just clang. It would be a lot easier to just use the version of clang that's in ports under lang/clangXX. Installing that's easy enough, but then how does one modify the ports infrastructure to use that install of clang instead of the base install of clang?

PowerPC See also the official project page. Note: If you're adding relevant information here, please poke someone to update ppc.sgml. Developer notes • • • • Supported Hardware • All New World Apple PowerPC machines (ones with built-in USB ports, 1999-2006) • Freescale MPC85XX evaluation boards • Sony Playstation 3 (powerpc64 only, starting with FreeBSD 9.0) Getting started • Instructions: • Starting with 9.0, the installer works properly, and most of the above instructions can be ignored OFW commands Sometimes you need these hints: • Booting from hard drive: boot cd:, BOOT LOADER cd:0 • PXEbooting: boot enet:0, loader.ppc Xorg Xorg should work on all supported Apple hardware. Console restore after leaving X11 may or may not work, depending on your graphics hardware. Peter Grehan tested X11 on: • rev B iMac (Rage 3D Pro 215GP, accel disabled). • 700Mhz eMac (Nvidia GeForce2 MX) • 12' 1.33G G4 powerbook (Nvidia GeForce G5200) • and Martin Minkus has run it on a 350MHz iMac, Rage 128VR.

On ATI Radeon-based machines there are still some problems: • Sometimes Option 'NoAccel' is required • The Xserver sometimes seems to have problems querying the Monitor Modes Sound uaudio(4) works. Snd_ai2s(4) and snd_davbus(4) support built-in audio on various Mac models. Links • Open Firmware Quick Reference: • Garance A. Drosehn's description about FreeBSD on the Minimac: • FreeBSD on the PowerMac G-series thread on the FreeBSD Forum: powerpc (last edited 2016-12-06 19:15:32 by ).