Index: ports/macppc/faq.xml =================================================================== RCS file: /cvsroot/htdocs/ports/macppc/faq.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- ports/macppc/faq.xml 29 Aug 2007 10:26:21 -0000 1.4 +++ ports/macppc/faq.xml 19 Sep 2009 20:59:15 -0000 1.5 @@ -5,8 +5,8 @@ - - + + @@ -71,13 +71,12 @@ NetBSD - 3.1 install notes — supported hardware and how to - install. + url="ftp://ftp.NetBSD.org/pub/NetBSD/NetBSD-&release.latest;/macppc/INSTALL.html">NetBSD &release.latest; install notes — supported hardware + and how to install. - port-macppc mail + port-macppc mailing list — if you have any additional questions please subscribe. @@ -129,7 +128,7 @@ If you don't see this message on screen (or serial console), then you haven't properly entered Open Firmware. If your machine starts to boot -Mac OS (i.e. the screen turns grey and a happy mac, broken folder, or +Mac OS (i.e., the screen turns grey and a happy mac, broken folder, or flashing question mark appears), then skip down to . If your screen stays black and you have an older mac, see . If your screen is all weird, @@ -156,8 +155,7 @@ url="../../docs/network/netboot/">Diskless HOW-TO, particularly in the macppc-specific -section, and the section on common netboot problems (). +section, and . 0 > boot enet:,ofwboot.xcf file: 192.168.0.11,/ofwboot.xcfloading XCOFF tsize=C280 dsize=14AC bsize=2620 entry=600000 @@ -210,7 +208,7 @@ may need to build a kernel with the root device hard-coded; see . -If your system hangs here and you have a new PowerBook, then read +If your system hangs here and you have a PowerBook, then read . swapctl: adding /dev/sd0b as swap device at priority 0 @@ -222,7 +220,7 @@ />. If you're running sysinst and it says I can not find any -hard disk for use by NetBSD then you should see then you should see . @@ -274,7 +272,7 @@ (Apple's open source BSD), partition with the NetBSD pdisk (not the native Darwin pdisk), and run the following commands (using the correct disk and - partition numbers, ofcourse): + partition numbers, of course): # newfs_hfs /dev/disk0s3 # mkdir -p /mnt @@ -334,7 +332,7 @@ How do I share files between the OSes on my machine? -Integrated into the Partitioning +See the Partitioning HOW-TO. @@ -342,7 +340,7 @@ Explaining the partition naming schemes -Moved to the Partitioning +See the Partitioning HOW-TO. @@ -350,9 +348,8 @@ Why does the screen scroll text so slowly? -The text console code is not optimized in the GENERIC kernel. There -is accelerated text console code in NetBSD 1.6 and later, but it is not -enabled by default. +The text console code is not optimized in the GENERIC kernel. Accelerated +text console code exists, but it is not enabled by default. You will need to build a new kernel. Add the following line to your kernel @@ -409,10 +406,10 @@ My PowerComputing clone's clock drifts too much. -Yeah, it appears that the timebase in Open +It appears that the timebase in Open Firmware doesn't match the hardware. You need to correct it. -See the See this post by Adam Lebsack. @@ -423,8 +420,8 @@ Various people have reported that they can't get their NetBSD/macppc systems to boot unattended. What happens is that Open Firmware loads the -kernel just fine, but the kernel can't seem to find the root device (i.e. -where the / filesystem is located). +kernel just fine, but the kernel can't seem to find the root device (i.e., +where the / filesystem is located). At the prompt, type in the device name for your root disk (usually something like sd0a or wd0a), swap @@ -472,7 +469,7 @@ - Apple PDM: Any x1xx machine, e.g. 6100, + Apple PDM: Any x1xx machine, e.g., 6100, 6150, 7100, 8100. @@ -487,7 +484,7 @@ - Power Computing "Power" series: Such as the + Power Computing "Power" series, such as the "Power 100" and "Power 120". @@ -542,17 +539,12 @@ Are PowerPC-based PowerBooks supported? -Many of them. See the NetBSD/macppc -supported models list. +Most of them are. See the NetBSD/macppc +supported models list for details. -The PowerBook 1400, 2300, and 5300 are not supported, because they do +The PowerBook 1400, 2300, and 5300 are not supported because they do not have Open Firmware. -Sometimes newly released laptop models have different built-in -keyboard glue and it takes NetBSD a while to catch up. If you have a newly -released model, try posting to port-macppc@NetBSD.org. - Note that power management is not yet supported, so it is not possible to suspend and resume a PowerBook while running NetBSD. @@ -577,7 +569,7 @@ Some users have reported that their system won't boot NetBSD if a new CPU is installed into the early PCI PowerMacintosh systems (7300 - 9600). -If you find that this is the case (i.e. you downgrade to a 604 and NetBSD +If you find that this is the case (i.e., you downgrade to a 604 and NetBSD works), then you may need to boot Mac OS once to install the nvramrc patches for your CPU daughtercard. From this point on, you should not use System Disk, as it will @@ -611,7 +603,8 @@ If your L3 cache is not enabled by default, then follow the directions in this post +url="http://mail-index.NetBSD.org/port-macppc/2003/02/27/0000.html">post. + @@ -619,8 +612,8 @@ What peripherals are supported? The -NetBSD/macppc 3.1 Install Notes have a full list of supported +url="ftp://ftp.NetBSD.org/pub/NetBSD/NetBSD-&release.latest;/macppc/INSTALL.html"> +NetBSD/macppc &release.latest; Install Notes have a full list of supported hardware in the section "Supported devices". Unless otherwise specified, third-party devices (such as PCI and cardbus cards) cannot be used to boot NetBSD/macppc. @@ -636,11 +629,11 @@ - Support for multiprocessor CPU cards is available in - NetBSD/macppc 2.0 and later. You will need to use a - GENERIC.MP kernel or add "options - MULTIPROCESSOR" to your kernel configuration. Without these - options, NetBSD will only use one CPU. + Support for multiprocessor CPU cards is available. + You will need to use a GENERIC.MP kernel or + add "options MULTIPROCESSOR" to your kernel + configuration. Without these options, NetBSD will only use one CPU. + @@ -669,7 +662,7 @@ - PCI, PCMCIA, cardbus, and USB ethernet devices + PCI, PCMCIA, CardBus, and USB ethernet devices (tlp, epic, ex, fxp, rtk, vr, @@ -829,7 +822,7 @@ - USB, PCI, and cardbus-based serial ports. + USB, PCI, and CardBus-based serial ports. @@ -839,7 +832,7 @@ Many add-on USB devices are supported. See the page - on the Machine-independent USB + on machine-independent USB drivers. @@ -851,10 +844,10 @@ Many cards are supported, but untested with NetBSD/macppc. - See the pages on the Machine-independent PCMCIA - drivers and the Machine-independent Cardbus + See the pages on machine-independent PCMCIA + drivers and machine-independent CardBus drivers. @@ -865,9 +858,9 @@ - Many cards are supported, but untested with NetBSD/macppc See - the pages on the Machine-independent PCI + Many cards are supported but untested with NetBSD/macppc. See + the pages on machine-independent PCI drivers. @@ -935,8 +928,7 @@ How do I use my AirPort or AirMac network? -Wireless networking was first supported in NetBSD 1.6. AirPort -Extreme is not currently supported. +AirPort Extreme is not currently supported. Briefly, what you need to do is set up your wireless card to use DHCP to find its IP address, and set up the correct media type (typically @@ -1050,12 +1042,12 @@ Are there bugs in my machine's Open Firmware implementation? Probably. The -NetBSD/macppc 3.1 Install Notes describe how to patch or upgrade -your Open Firmware to work around these bugs. See the section on "Updating -your BootROM" for Open Firmware 3 systems, and the section "Older Open -Firmware System Preparation" for systems with Open Firmware 1.0.5, 2.0.x, -and 2.4. +url="ftp://ftp.NetBSD.org/pub/NetBSD/NetBSD-&release.latest;/macppc/INSTALL.html"> +NetBSD/macppc &release.latest; Install Notes describe how to patch +or upgrade your Open Firmware to work around these bugs. See the section +on "Updating your BootROM" for Open Firmware 3 systems, and the section +"Older Open Firmware System Preparation" for systems with Open Firmware +1.0.5, 2.0.x, and 2.4. @@ -1063,10 +1055,10 @@ How do I get to the Open Firmware prompt? Read the NetBSD -3.1 install notes. In particular, scroll down to the section on -"Getting to Open Firmware" for your particular version of Open -Firmware. +url="ftp://ftp.NetBSD.org/pub/NetBSD/NetBSD-&release.latest;/macppc/INSTALL.html"> +NetBSD &release.latest; install notes. In particular, scroll down +to the section on "Getting to Open Firmware" for your particular version +of Open Firmware. For the lazy, you can use Apple's System Disk to set your machine to always boot into Open Firmware. See the brief You didn't read the NetBSD -3.1 install notes. In particular, scroll down to the section on -"Getting to the Open Firmware Prompt on Older Models". It's a bit lengthy, -but very clear in describing the proper steps to set up Open -Firmware. +url="ftp://ftp.NetBSD.org/pub/NetBSD/NetBSD-&release.latest;/macppc/INSTALL.html"> +NetBSD &release.latest; install notes. In particular, scroll down +to the section on "Getting to the Open Firmware Prompt on Older Models". +It's a bit lengthy, but very clear in describing the proper steps to set +up Open Firmware. Briefly, all Open Firmware 1.0.5 and most Open Firmware 2.0.x systems will default to using the `Modem' serial port for the console instead of @@ -1101,7 +1093,7 @@ url="SystemDisk-tutorial/">System Disk and you're using a PowerMacintosh 7300 - 8600 model, then you may need to apply the additional patches for your /chaos/control on-board video to sync -propertly (see ). +properly (see ). If you're using a Performa 5500 or 6500, you may need to apply some NVRAMRC patches to use your on-board video. See the this post describing the issues. At this time, no one has reported a -successful install onto a TAM, although, this should be possible by setting +successful install onto a TAM, although this should be possible by setting the input and output devices to ttya with System Disk and connecting a serial cable to another machine running a terminal emulator. @@ -1235,7 +1227,7 @@ 220 V) and remove the battery from the motherboard. It may take some time (hours) for the charge stored in the power supply to drain and the NVRAM to clear. To speed up the process you might try pressing the power button. -More riskily (i.e. do at your own risk) you can try connecting the battery +More riskily (i.e., do at your own risk) you can try connecting the battery backwards in the socket or shorting the terminals with a resistor. Don't forget to set the date! @@ -1253,7 +1245,7 @@ A simple, but awkward solution is to use the hexadecimal representation of the character you want to use. Enclose the entire -command in double-quotes " and replace the character +command in double-quotes and replace the character with its hex code preceeded by a double-quote and enclosed in parenthesis. For example backslash is replaced by "(5C). After the command in quotes you need to have the FORTH commands to either display @@ -1282,8 +1274,7 @@ You can configure various properties of your system related to -booting. This table merely lists the common commands you might be -using and their syntax. +booting. This table merely describes some common commands. Common commands @@ -1351,7 +1342,7 @@ set-default variable - sets the variable to its default value. + sets variable to its default value. See . @@ -1359,7 +1350,7 @@ boot boot-device boot-fileloads and runs a program boot-file on - boot-device, we use it to load + boot-device; we use it to load ofwboot (the "partition zero" bootloader) or ofwboot.xcf and then the NetBSD kernel @@ -1628,8 +1619,8 @@ resource to determine which ID System Disk uses for your model. Then edit the appropriate OFpt resource. -Make sure that, after you are done modifying your settings, that you -store them permanently, by typing: +Make sure that you permanently store your settings after you are done +modifying them, by typing:0 > reset-all @@ -1665,14 +1656,14 @@ real-base depends on Open Firmware version - Kernel memory location. Kernel memory location. See . load-base depends on Open Firmware version - bootloader memory location. bootloader memory location. See @@ -1724,8 +1715,8 @@
- Zapping your PRAM Command-Option-P-R will erase - any settings you have made to these Open Firmware variables. + Zapping your PRAM with Command-Option-P-R will + erase any settings you have made to these Open Firmware variables. Booting your Open Firmware 1.0.5 system into Mac OS will erase any settings you have made to these Open Firmware variables. @@ -1734,7 +1725,7 @@ settings such that your system won't boot anymore. Zapping the PRAM doesn't fix it. In this case, you will need to unplug your system and remove the battery from your motherboard for about 10 minutes. On a - PowerBook, the equivalent is to resetting your power manager. + PowerBook, resetting your power manager is equivalent. @@ -1752,12 +1743,12 @@ Open Firmware 3 -Do not change the +Do not change load-base. Open Firmware 3 machines have re-writable firmware, and users have found that changing the load-base has overwritten their flash BootROM, rendering their machines dead (requiring an expensive trip back to Apple). Do not change the load-base on an Open +role="strong">Do not change load-base on an Open Firmware 3 machine. Apple has fixed Open Firmware 3 such that you needn't change load-base to boot. @@ -1794,7 +1785,7 @@ What's the deal with the "real-base" setting? The Open Firmware environment variable real-base -is the address where OpenFirmware uses for itself. The default value of +is the address OpenFirmware uses for itself. The default value of real-base might be -1 (0xffffffff), but it will cause problems because OF 1.0.5 and 2.x machines use 0x400000 if real-base is the default value. The kernel is loaded to @@ -1802,9 +1793,9 @@ a kernel larger than about 3 MB. Open Firmware 3 machines have re-writable firmware, and users have -found that changing the real-base will overwrite their +found that changing real-base will overwrite their firmware, rendering their machines dead (requiring an expensive trip back -to Apple). Do not change the +to Apple). Do not change real-base on an Open Firmware 3 machine. Open Firmware 3 does a much better job of dealing with large kernels, so this is not really an issue. @@ -1824,7 +1815,7 @@ make your machine no longer boot (see to recover from it). -A workaround for this problem is that you can build a kernel that is +A workaround for this problem is to build a kernel that is less than 3 MB in size. Since none of the Open Firmware 1.0.5, 2.0.x, or 2.4 models have built-in USB, you can build a @@ -1983,7 +1974,7 @@ HFS+, and MS-DOS. The official NetBSD install CD-R image and floppy images are a bit -funky (i.e. they have a "partition zero" bootloader). You won't be able to +funky (i.e., they have a "partition zero" bootloader). You won't be able to get a listing of the files from within Open Firmware. For example, to get a listing of the files on a floppy, type: @@ -2015,9 +2006,9 @@ What are the supported ways of booting NetBSD/macppc? See the -NetBSD/macppc 3.1 Install Notes and read the section entitled -"Available Boot Media". +url="ftp://ftp.NetBSD.org/pub/NetBSD/NetBSD-&release.latest;/macppc/INSTALL.html"> +NetBSD/macppc &release.latest; Install Notes and read the section +entitled "Available Boot Media". @@ -2028,12 +2019,11 @@ This depends entirely on what version of Open Firmware your machine has, and what you're trying to boot from. Read the "Preparing the Bootable Media" and "Open Firmware boot syntax" sections of the -NetBSD/macppc 3.1 Install Notes. +url="ftp://ftp.NetBSD.org/pub/NetBSD/NetBSD-&release.latest;/macppc/INSTALL.html"> +NetBSD/macppc &release.latest; Install Notes. See also , the -ofwboot(8) man page, the -installboot(8) man page. +&man.ofwboot.8; man page, and the &man.installboot.8; man page. @@ -2178,7 +2168,7 @@ -Where is the official NetBSD/macppc CD-R image stored? +Where is the official NetBSD/macppc ISO image stored? Look for the NetBSD Download Site closest to you, download the image, and burn it to a @@ -2186,8 +2176,8 @@ See the section titled "Creating the NetBSD/macppc CD-R" in the -NetBSD/macppc 3.1 Install Notes. +url="ftp://ftp.NetBSD.org/pub/NetBSD/NetBSD-&release.latest;/macppc/INSTALL.html"> +NetBSD/macppc &release.latest; Install Notes. @@ -2199,7 +2189,7 @@ url="http://mail-index.NetBSD.org/port-macppc/1999/03/12/0002.html">port-macppc mail archives.) -Note, this is entirely different than the Darwin BootX +Note that this is entirely different than the Darwin BootX bootloader. @@ -2209,8 +2199,8 @@ Yes, although it is a bit tricky. Yaboot itself provides a mechanism to boot BSD systems, but unfortunately it does not work correctly (at -least, with NetBSD). However, you can benefit from this feature because, -with little manual intervention, it works. Follow these steps: +least, with NetBSD). However, you can benefit from this feature, because +with a little manual intervention, it works. Follow these steps: @@ -2233,11 +2223,11 @@ Edit the ofboot.b script within the - partition you have just mounted (e.g. + partition you have just mounted (e.g., /mnt/ofboot.b). Locate the line that starts with - :bootybsd: it holds the command required to - launch our NetBSD installation, which we must correct to make it - work. That said, edit the line and place the command you typically use + :bootybsd. It holds the command required to + launch our NetBSD installation, which we must correct to make + work. Edit the line and place the command you typically use from within Open Firmware to boot NetBSD. Here is an example: :bootybsd " Booting BSD..." .printf 100 ms load-base release-load-area " hd:2,ofwboot hd:5/netbsd" $boot ; @@ -2319,7 +2309,7 @@ can't OPEN enet: ok - Bootp or DHCP server isn't responding to client's request. Check + The BOOTP or DHCP server isn't responding to client's request. Check that the server is running, that it's on the same ethernet subnet, and that it has the correct ethernet hardware (MAC) address for the client. Look for local-mac-address in the output of: @@ -2557,7 +2547,7 @@ Where's my disk? (a.k.a. sysinst says <literal>I can not find any -hard disk for use by NetBSD</literal>) +hard disks for use by NetBSD) Well, that's a good question! @@ -2639,33 +2629,11 @@ - -Where is -<literal>ldconfig</literal>/<literal>ld.so.conf</literal>? - -NetBSD/macppc uses ELF, so it does not have -ldconfig or ld.so.conf. See the -NetBSD ELF FAQ for more -details. - - - - -How can I cross-compile from another host/OS? - -NetBSD 1.6 and later systems have full support for cross-compilation -of the base system, even as a non-root user and even on non-NetBSD hosts. -See the Cross-building -NetBSD under NetBSD Documentation -pages for details. - - - Can NetBSD/macppc run MkLinux or LinuxPPC binaries? -Yes. Linux binary compatibility for PowerPC ports is supported in -NetBSD 1.6 and later, but is not enabled by default. You will need to +Yes. Linux binary compatibility for PowerPC ports is supported, +but is not enabled by default. You will need to build a kernel with options COMPAT_LINUX uncommented. Applications that are reported to work include Opera, which will crash on first startup. On the second startup, if you go to the advanced settings dialog and uncheck "asynchronous DNS", it should work -without troubles. +without trouble. It is probably worth mentioning that the JDK works quite well. Java applications such as Can NetBSD/macppc run Mac OS binaries? Well, some day someone might get Mac-on-linux +url="http://www.maconlinux.org/">Mac-on-linux (for LinuxPPC) to work. Meanwhile, try emulators/BasiliskII or VMac both of which emulate a 68k +url="http://www.vmac.org">VMac, both of which emulate a 68k Mac. @@ -2706,10 +2674,9 @@ Can NetBSD/macppc run Darwin/Mac OS X binaries? -Work is in progress, and some support for running Darwin binaries is -present in NetBSD-current. Check the COMPAT_MACH and COMPAT_DARWIN -status page -for up to date information about this project. +There was some work being done on this, but the project has been +abandoned for now. See the +Mach and Darwin binary compatibility page for details. @@ -2770,27 +2737,19 @@ you can create a hardware hack that appears to the computer to be the "power" key on an ADB keyboard. All Macs have a real power switch (be it soft or hard power), it may just be a bit hidden. This will void your -warrantee, don't hold us liable, etc. See Chris Tribo's post to the mailing list on this topic. -Why there's no wscons mapping "us.swapctrlcaps" for ADB -keyboard? +Why is there no wscons mapping "us.swapctrlcaps" for ADB +keyboards? -ADB keyboard generates weird key code — it generates a key code -when it gets pressed then released (= caps lock set), and another key code -when it gets pressed and released (= caps lock released). In the kernel -code sys/arch/macppc/dev/akbd.c the weird key code -gets translated into wscons key code. Because of this weirdness, the best -result we will be able to get is, unfortunately, a locking control -key. - -On NetBSD-current (1.6A or later), options -CAPS_IS_CONTROL will hardcode capslock key into control key. -(Even with weird LED behavior it should be useful.) +ADB keyboards emulate a mechanically-locked key, which makes things +difficult for wscons. To treat the caps lock key as a control key, build +a kernel with options CAPS_IS_CONTROL in it.