SuSE Linux PowerPC: Version 7.1
The following bugs and problems are known with the SuSE Linux 7.1 Developer Release for iSeries.
Tip: Since that release is based on SuSE Linux 7.1 for PowerPC, you may find valuable tips by searching the support database for the keyword PPC. Second important thing is to make sure is that your PTF level is adequate -- check against http://www-1.ibm.com/servers/eserver/iseries/linux/ptfs.html!
On the current kernel, the time of day drifts slightly, therefore if you're dependent on very accurate time of day, we would recommend synchronizing all the systems to a time server.
When running the a stress workload (heavily loaded Linux system) for more than 60+ hours, we are intermittently detecting a PCI 0x0301 error. The 0x0301 error is defined as: invalid bus or subbus number.
(This has been fixed in the 9/21 32 bit kernel. An update can be found on the FTP site.)
IBM Java (JVM 1.3.0) on iSeries Linux currently is restricted to heaps of 1 GB or less, larger heaps will result in errors.
The VNC packages on the initial 7.1-PPC release were broken. Please use
the packages that you find in the /updates
directory on the
iSeries CD-ROM, they contain special PPC patches.
Squid does not start on 7.1-PPC. Updates will be provided on our FTP site.
The version of tn5250, as contained on the distribution, was quite outdated. Update packages (current version) can be found here:
http://linux01.gwdg.de/suse/ftp.suse.com/suse/ppc/boot/iSeries/tn5250/
PF keys (function keys) do not work correctly when using the virtual console during install... example: user can't change package selections because the pf10 key ("ok") is being seen as ESC ("abort"). See the SuSE installation document for more details.
Attempts to install into a partition that has an existing Linux install can cause YaST to produce unpredictable errors. To avoid this, make sure to format the root partition before installing packages by selecting format=normal (option F6, then select "normal") for the root partition in the "creating filesystems" menu. (Note: See the manuals for help backing up existing data.)
You can configure network adapters during install (or after install) using YaST1. However, in some cases YaST1 will not update modules.conf, so any new adapters with modular drivers (which includes pcnet32, olympic, and acenic - the ethernet, token-ring, and gigabit ethernet drivers) will not have their modules loaded at boot time and thus will not function. To have the module loaded at boot time, start YaST1, and go to System Administration. Select Integrate hardware into System. Then select Configure networking device. Selecting the device name and type will write /etc/modules.conf with the information. This should be done before the device is configured with an ip address.
The device for virtual ethernet is going to have a number that corresponds with the number of the VLAN that is available. I.E. VLAN2 will show up as veth2 within your partition. If you want to install over this device you will have to set up the networking for that interface manually.
First run the network setup (options 3 in setup) and configure veth0 with the appropriate values for vethX. This will setup the proper network values for YaST. Then exit setup (Options 0) and edit /etc/install.inf so that the value of Netdevice from veth0 to vethX.
Now you need to start veth1. From the command line run the command "ifconfig vethX local IP numbernetmask netmask valuebroadcast boradcast valuemtu 1500" This will configure the device. After you have done this you need to add your default route: "route add default gw ip of your default gateway". Now your system is networked.
Now you may install over the network by entering yast and selecting to install by FTP. Yast will automatically recognize your networking and allow you to install by FTP.
If you want to install using NFS, manually create a directory in / (not in /mnt) and mount your exported copy of the cds. Next start YaST and select to do the installation from a reachable directory, selecting your mounted file system as the location from which to install.
When doing a network install with YaST1, the olympic module is not loaded, even if tr0 is the device setup for the install. The module needs to be manually loaded before starting the install.
When setting an additional virtual ethernet device in YaST1 (in the installed system), it is possible that you can't find the type "veth" for the device in the "System Administration --> Network configuration --> Network base configuration" menu. This depends on your version of YaST1. If there is no network type "veth0", you need to select 'other' in "Enter other device" (pf5).