@(#)PLATFORM 6.24 01/05/11 SUPPORTED PLATFORMS ------------------- The source code of this version of xmcd and cda supports the following operating system and hardware environments. Note: The enhanced CDDBČ(tm) service is enabled only on some platforms. The "classic" CDDB(tm) service is used on all the others. See the CDDB file for details. 1. Apple A/UX - A/UX version 3.0 or later (on Apple Macintosh m68k, with devscsi module installed) 2. Berkeley Software Design, Inc. BSD/OS - BSD/OS version 2.x (on Intel x86 PC-compatible) - BSD/OS version 3.x (on Intel x86 PC-compatible) - BSD/OS version 4.x (on Intel x86 PC-compatible and Sun Sparc) 3. Compaq / Digital Equipment Tru64 UNIX, Digital UNIX or OSF/1 - version 1.3 or later (on Digital Alpha AXP) 4. Compaq / Digital Equipment Ultrix - Ultrix version 4.3 or later (on DECStations, with SCSI CAM installed) 5. Data General DG/UX - DG/UX version 5.4R3.00 or later (on DG AViiON m88k) 6. FreeBSD - FreeBSD 2.0.5 or later (on Intel x86 PC-compatible) - FreeBSD 4.0 or later (on Digital Alpha AXP) 7. Hewlett Packard HP-UX - HP-UX release 9.x (HP 9000 m68k Series 300, Series 400) - HP-UX release 9.x (HP 9000 PA-RISC Series 700 WSIO) - HP-UX release 10.x (HP 9000 PA-RISC Series 700 WSIO) - HP-UX release 11.x (HP 9000 PA-RISC Series 700 WSIO) 8. IBM AIX - AIX version 3.2.x (on IBM RS/6000 Power and compatibles) - AIX version 4.x (on IBM RS/6000 Power/PowerPC and compatibles) 9. Linux - Linux 1.0 or later (on Intel x86 PC-compatible) - AlphaLinux 2.1 or later (on Digital Alpha AXP) - SparcLinux 2.0 or later (on Sun Sparc or compatibles) - Linux-ppc 2.1 or later (on Apple Macintosh PowerPC or compatibles) 10. NetBSD - NetBSD 1.0A or later (on Intel x86 PC-compatible, Sun Sparc and other platforms) 11. OpenBSD - OpenBSD 2.x or later (on Intel x86 PC-compatible, Sun Sparc and other platforms) 12. QNX - QNX version 4.22 or later (on Intel x86 PC-compatible) 13. SCO UNIX System V Release 3.2 (on Intel x86 PC-compatible) (SCO UnixWare see below) - SCO UNIX 3.2v4.x - Open Desktop version 2.x - Open Desktop version 3.x - Open Server release 5.x 14. Siemens Pyramid Reliant UNIX System V Release 4 - SINIX-N on RM200, RM400 - SINIX-P on RM600 15. Silicon Graphics Irix System V Release 4 - Irix version 4.x (on SGI platforms) - Irix version 5.x (on SGI platforms) - Irix and Irix64 version 6.x (on SGI platforms) 16. Sony NEWS-OS - NEWS-OS 4.1 or later (on Sony NEWS/m68k) 17. Stratus FTX System V Release 4 - FTX version 3.x (on Stratus Continuum PA-RISC platforms) 18. SunOS - SunOS 4.1.x / Solaris 1.x (on Sun Sparc and compatibles) 19. Sun Solaris System V Release 4 - Solaris 2.x and later (on Sun Sparc and Intel x86 compatibles) 20. UNIX System V Release 4.0 (on Intel x86 PC-compatible) (Note: 4.0.3 or later recommended) - AT&T - Consensys - Dell - ESIX - ISC - Microport - Micro Station Technology - UHC - USL 21. UNIX System V Release 4.0 (on Motorola m88k) - Motorola 22. UNIX System V Release 4.2 (on Intel x86 PC-compatible) - Consensys - Information Foundation - Univel/Novell UnixWare 1.x - Onsite - USL 23. UNIX System V Release 4.2MP (on Intel x86 PC-compatible) - Novell/SCO UnixWare 2.x 24. UNIX System V Release 5 (on Intel x86 PC-compatible) - SCO UnixWare 7.x PLATFORM-SPECIFIC NOTES ----------------------- Please read this section as well as the RELNOTES file for important information about setting up and using xmcd and cda. AIX 4.x: For IDE drive users: If you eject a CD with xmcd or cda, then load a new CD, you may find that the time of the last track is incorrect. This is caused by an apparent bug in the AIX IDE CD-ROM driver: It does not purge its in-core lead-out location information when you ejected the CD. A workaround is to set xmcd's closeOnEject parameter to True. This forces xmcd and cda to close and re-open the device when you eject the CD and clears up the problem. BSDI BSD/OS: On the BSDI BSD/OS 2.x platform, the xmcd and cda volume, balance and channel routing controls will not work unless you apply a minor patch to the disk device driver. In the /sys/dev/scsi/sd.c file, find the sdopen() function, and look for code similar to the following: if ((sc->sc_type & TYPE_TYPE_MASK) == TYPE_ROM && flags & FWRITE) return (EROFS); Comment-out or remove these two lines of code. This code was intended to prevent an application from opening a CD-ROM drive for writing (since the CD-ROM media is read-only). This restriction is not necessary, as a write operation to the CD-ROM would fail anyway. However, due to the design of the SCSI pass-through mechanism in BSD/OS, xmcd/cda needs to "write" out SCSI mode data in order to implement the volume, balance and channel routing controls. This patch allows xmcd/cda to open the CD-ROM device with the write attribute enabled. After applying this patch, you must then build a new kernel and reboot. You should also set the CD-ROM device node to enable both read and write permissions. If you decide not to patch the disk driver, then you should set the following parameters to "False" in the XMCDLIB/config/DEVICE configuration file: volumeControlSupport: False balanceControlSupport: False channelRouteSupport: False The Hitachi SCSI-1 CD-ROM drives will not work on the BSD/OS 2.x platform without some changes to the SCSI driver. The specific changes necessary are beyond the scope of these notes. If you must use the Hitachi SCSI-1 drives please e-mail xmcd@amb.org for information. ATAPI CD-ROM drives are supported only on BSD/OS 3.x and later. See the DRIVES file for details. Digital UNIX (OSF/1) and Ultrix: The minimum Ultrix and OSF/1 OS version listed above should be heeded. Running xmcd and cda on earlier releases of either OS may cause the system to crash, due to bugs in the OS. You must create the /dev/cam device before using xmcd/cda under Ultrix. To do so, type the following commands while logged in as root: cd /dev MAKEDEV cam Data General DG/UX: For DG/UX, you must configure the CD-ROM to be a user SCSI device instead of a SCSI disk. To do so, follow these steps: 1) Find the line in the file /var/Build/system. which represents your CD-ROM drive and change the prefix "sd" to "scsi". 2) Rebuild and reboot your kernel. FreeBSD: You should set the CD-ROM device node to enable both read and write permissions. Release and snap versions of FreeBSD 2.0.5R needs a patch in the SCSI driver in order to work with xmcd (otherwise, the kernel may panic). In /sys/scsi/scsi_ioctl.c, around line 323: Original code: /* if no data, no need to translate it.. */ bp->b_un.b_addr = 0; bp->b_dev = dev; bp->b_flags = 0; scsistrategy(bp); ret = bp->b_error; Fixed code: /* if no data, no need to translate it.. */ bp->b_un.b_addr = 0; bp->b_dev = dev; bp->b_flags = B_BUSY; scsistrategy(bp); ret = bp->b_error; FreeBSD 2.x uses the SCIOCCOMMAND ioctl for SCSI pass-through support whereas FreeBSD 3.x uses the CAM mechanism. Moreover, FreeBSD 3.x has changed to the ELF binary format. Xmcd/cda executable binaries compiled for FreeBSD 2.x cannot be used on FreeBSD 3.x and vice versa. In order for xmcd and cda to work on a FreeBSD 3.x system, you must have the CAM pass-through driver configured in your kernel: device pass0 And you must have the CAM transport layer and pass-through devices in /dev: cd /dev sh MAKEDEV xpt1 sh MAKEDEV pass8 Where the number at the end of the device name is the number of devices to create. You only need one transport layer device, but you will need one pass-through device node for each SCSI device in your system. FreeBSD 4.0 on Alpha AXP platforms may requires a kernel patch to the atapi-cd driver to prevent a kernel panic in the CDIOCSETVOL ioctl function, caused by an unaligned memory access bug in the atapi-cd driver. Without a atapi-cd driver fix, you must set xmcd/cda's volumeControlSupport, balanceControlSupport and channelRouteSupport parameters to False in order to avoid the kernel panic. HP-UX: On the m68k systems, you should set the CD-ROM device node to enable both read and write permissions. For PA-RISC platforms, only systems running the WSIO (Workstation I/O) device driver subsystem are supported. Xmcd and cda will not work on systems running the SIO (Server I/O) device driver subsystem. Due to a bug in the HP-UX Bourne Shell (/bin/sh), the install.sh script will fail on some versions of HP-UX. The Korn Shell (/bin/ksh) should be used instead. To install the pre-compiled xmcd binary distribution, run the install.sh script like this: ksh ./install.sh On some HP-UX 10.x systems, you may need to apply some HP software patches ("Audio subsystem patch, et. al") in order for the Audio Control utility to recognize the CD-ROM as an input source or otherwise function correctly. Please inquire with HP customer support for details. Linux: If you have an IDE/ATAPI drive and run it under SCSI-emulation, then you should answer 'y' to the following question when configuring xmcd/cda: Does this drive use a SCSI interface? If you encounter any errors while running xmcd with a drive under SCSI-emulation, you may need to tweak a parameter or two. Please refer to the Xmcd Configurtion Guide web page: http://www.amb.org/xmcd/config.html If you're running the GNOME environment and would like to have xmcd automatically start when you insert a CD (instead of the default gtcd player), edit the file $HOME/.gnome/magicdev, and locate the following line: cd_play_command=gtcd --play --device %d change it to: cd_play_command=xmcd In addition, after xmcd starts for the first time, click the Options button (the one with the tools symbol) on the xmcd main window, and in the popup, select "On load: auto play" and "On eject: auto exit", then click "Save". The Hitachi SCSI-1 CD-ROM drives will not work on the Linux platform without some changes to the SCSI driver. The specific changes necessary are beyond the scope of these notes. If you must use the Hitachi SCSI-1 drives please e-mail xmcd@amb.org for information. QNX: Under QNX, xmcd must be configured to run under the "QNX ioctl method" to operate all CD-ROM drive types. The "SCSI pass-through" method is not available. You must have the Fsys driver to create /dev/cd0. If the Audio driver is installed, /dev/dsp will automatically be used. Note: A stable, post-beta Audio driver is present only on QNX 4.23 and later. Warning: The Iso9660fsys driver must NOT be running while you use xmcd/cda, or else you risk filesystem corruption. Sun SunOS 4.1.x: The current SunOS 4.1.x run-time support is limited to systems running the sun4c and sun4m kernels. To find out which kernel you have, use the "arch -k" command. The Hitachi SCSI-1 CD-ROM drives will not work on the SunOS 4.1.x platform as an audio CD player. These drives were provided as standard equipment with some Sparc-compatible workstations. There is no way to make them work with xmcd and cda under SunOS 4.1.x. The only solution is to upgrade to a SCSI-2, Sun-compatible CD-ROM drive. Xmcd and cda uses gethostbyname(3) to convert host names into IP addresses for CDDB server access. The gethostbyname() function in the SunOS 4.1.x C library uses NIS to resolve host names. NIS is usually set up to resolv host names within an intranet, not the Internet. DNS (domain name service) is what's normally used for Internet host name resolution. You should explicitly link xmcd/cda with the /usr/lib/libresolv.a library (which contains an alternative gethostbyname() that uses DNS). To do this, add -lresolv to the final link command line of xmcd and cda's Makefiles. Alternatively, you can modify the SunOS shared C library such that it will support DNS. This has the benefit of "fixing" the other TCP/IP utilities such as telnet, ftp, etc. to use DNS too. For details on how to do that, try a web search with the keywords "SunOS DNS". Sun Solaris 2.x and later: On Solaris platforms, you should use the virtual CD-ROM device (such as /vol/dev/aliases/cdrom0) if the Solaris Volume Manager (/usr/sbin/vold) is also running. You should set xmcd's "solaris2VolumeManager" common parameter and either the "closeOnEject" or "exitOnEject" device-specific parameter to True when operating under the Volume Manager. If you want the Volume Manager to automatically start xmcd when a CD is inserted, you can specify the action_workman.so start-up program in the /etc/rmmount.conf file: action cdrom action_workman.so /usr/local/bin/X11/xmcd Substitute /usr/local/bin/X11 with the actual path to your xmcd binary. See rmmount(1M) and rmmount.conf(4) for more information. If the Solaris Volume Manager is running, you should only use the Eject button on the xmcd main window to eject the CD. Do not use the eject button on the CD-ROM drive itself. UnixWare (all versions): If you encounter unexplained and random xmcd or cda crashes, it is possible that some or all of these kernel tunable parameters need to be increased: HDATLIM, SDATLIM, HSTKLIM, SSTKLIM, HVMMLIM, SVMMLIM, SFNOLIM See the idtune(1M) command about tuning kernel parameters.