QNX® 4 Product Suite 2015 Experimental Release Notes#

The QNX 4 Product Suite 2015 is available for a beta testing as Experimental Release.

What's new in this product suite?#

The QNX 4 Product Suite 2015 includes the following new drivers and components:

• Fsys.ahci
  New driver to support AHCI SATA controllers

• Pg.i915
  New driver to support multiple monitors on Intel i915/i945/i965

Other changes include:

• Proc32
  Added option -E0 and alternative PCI BIOS int 1Ah handler

• Dev32.ansi
  Added support of USB keyboards in console

• Network drivers
  The following drivers have been updated to support new versions of the controller family:
  Net.e1000
  Net.rtl

• nettrap
  Updated to support the latest network drivers.

• Graphics drivers
  The following drivers have been updated to support new controllers:
  Pg.i830
  Pg.intelhd

• Input
  Added -s option to suppress keyboard events on mouse events

Installing on AHCI SATA disk controller#

1. In the first installation program step, press F12 or choose the Run installation in diagnostic mode check box.
2. Press F2 or the Next button.
3. In the "Hardware adapter type" list, select "AHCI Disk Controller".
4. Press F2 or the Next button.
5. The auto-detect hardware procedure should find AHCI SATA controllers and disks.
6. AHCI support lets you install QNX on a AHCI SATA controllers.

USB support in the installation program#

To enable USB support during the installation:

1. Enable the USB stack (press F7) in the Safe Mode menu to run the io-usb manager.
2. In the first installation program step, press F12 or choose the Run installation in diagnostic mode check box.
3. Press F2 or the Next button.
4. In the "Hardware adapter type" list, select "USB mass storage device".
5. Press F2 or the Next button.
6. The auto-detect hardware procedure should find all connected USB mass storage devices (USB CD-ROM, USB floppy, USB flash).
7. USB support lets you install QNX from a USB CDROM and install QNX on a USB flash.

USB support lets you install QNX from a USB CDROM and install QNX on a USB flash. The installation program currently doesn't support preparing a boot floppy for the USB floppy drives.

Known issues#

• It's possible to mount different USB sticks with specific mountpoints by using the Fsys.umass did and vid arguments, but the documentation doesn't explain how. (Ref# J228998)
  Workaround: You must specify the did and vid in full hexadecinal form (e.g., vid=0x1233, not vid=1233). Preparsing the output of usb is the only way.
  If you're specifying a device and a vendor, you must specify the devno and busno (4 arguments).
  The -N option must be unique for each invocation of Fsys.umass.
• The purpose of vpim is to convert Latin characters into Japanese characters, so if you put the Input driver into Kana (Japanese phonetic alphabet) mode, none of the vpim option modes have any effect. This is normal behavior, as vpim operates only on Latin character input (Romaji). If you're in Kana mode and you want to use vpim, put the Input driver back into Romaji mode via the Alt-key chord.
• On some boards, if you use a USB keyboard and a USB mouse in PS/2 legacy mode, the USB mouse might work incorrectly in Photon; it might move erratically and generate right-button clicks. (Ref# 71682)
  Workaround: Add the -R option to the kbd protocol in the command you use to launch the Input manager, or in /etc/config/trap/input.$NODE or /etc/config/bin/input.$NODE.
• If you upgrade from a previous version of the QNX 4 Product Suite to the QNX 4 Product Suite 2010 version and "QNX 4.25 OS Patch Level G+" component from 2008 CD was installed it'll block the QNX4 Documentation Patch G" component (you'll see that QNX4 Documentation component has two installed patches and patch G is already installed).
  Workaround: Remove QNX 4 Documentation component (F8) and then Install Documentation component with patch G again.
  Note: If you upgrade from a previous version (2008 or 2009) of the QNX 4 Product Suite to the 2010 version we recommend to remove components "QNX 4.25 OS Patch Level G+" and "QNX 4.25 OS Patch 2009" before the update. This components was excluded from the QNX 4 Product Suite 2010. To remove components run phinstall program from 2008 or 2009 product Suit CD.
• The Fsys.atapi driver supports SATA drives only in legacy IDE mode. (Ref# 56067)
• Don't run crttrap trap while you're running Photon; if you do, your system might crash, or even get corrupted. (Ref# 72418)
  Workaround: Run crttrap trap only in text mode.
  Note: If your system boots automatically into Photon, you can get to text mode by moving /etc/config/bin/ph.num (where num is your system's node number) to a different location, such as root's home directory, and then rebooting. You can move the file back to its original location later if you wish to boot into Photon again.
• USB keyboards or USB mice can freeze sometimes if the USB keyboard and USB mouse are used at the same time and Net and io-usb are sharing one interrupt line.
  Workaround: Restart Photon or the Input manager.
• On several boards, the installation program can hang up on ATAPI detection if the USB stack is enabled (F7 in the Safe Mode menu).
• The installation program can hang if you try to probe and set video mode during the installation for some unsupported video controllers.
  Workaround: Skip the video mode probe procedure during the installation. (Answer "No" for the installer question "Do you want to probe and set video modes now?"). The first time you boot: Comment out the line with Hydra.ms in the file /qnx4/graphics/trappers/crttrap.list.
  Run crttrap trap to probe the video mode.
  Start Photon.
  Note: Unsupported graphics controllers will work in 640x480x16 mode only.
• If you've installed both the TCPIP 4.25 stack and TCPIP 5.10, and you then remove the currently used version of TCPIP in the Phinstall program, then to set up the links for the remaining TCP/IP, run the /usr/tcprt/switch.tcpip script. You can also use this script to switch between the versions of TCP/IP.
• The TCPIP 5.10 configuration script updates only the /etc/config/bin/tcpip.$NODE script during the installation and leaves /etc/netstart and /etc/nfsstart unchanged. If you're using the /etc/netstart script to launch TCP/IP 4.25 components, and you then update to TCPIP 5.10, you have to edit the /etc/netstart and /etc/nfsstart scripts manually or replace these files with netstart and nfsstart from the /etc/config/socket directory. This directory contains default configuration files and scripts for the currently used TCP/IP stack.