Q1. I booted RT-Mach from SCSI hard disk, but bootstrap stopped with a message like:
Can't open paging file /dev/sd0s1a/mach_servers/paging_file: 2502
Paging file name ?
A1. The installer makes a symbolic link from /dev/hd0b to /mach_servers/paging_file. You can solve this problem by either of the following.
- Just hit CR key.
This is the simplest way. RT-Mach boots without paging system.
- Specify an appropriate device.
If your system is booted from SCSI Hard Disk(ID:0), you can specify the appropriate device as follows:
# ln -s /dev/sd0b /mach_servers/paging_file
"sd[0-3][a-h]" means a SCSI device. [0-3] is the device's ID and [a-h] is the partition number. In this example, "sd0b" means partition b of SCSI device that has ID:0.
- Specify appropriate file.
RT-Mach can use a file for paging. The file size must be n*4kbytes. This is because the page size is 4kbytes.
Q2. When I boot from second IDE hard disk, bootstrap stopped with a message like:
Can't open paging file /dev/hd0s2a/mach_servers/paging_file: 2502
Paging file name ?A2. Basically the same as A1. When you specify a paging file on a IDE hard disk, do as follows:
# ln -s /dev/hd1b /mach_servers/paging_file
"hd[0-3][a-h]" means an IDE device. 0 is primary master device,1 is primary slave device, 2 is secondary master device and 3 is secondary slave device. [a-h] means partition number. In this example, "hd1b" means partition b of primary slave IDE device.
Q3. When I boot from SCSI hard disk, bootstrap stopped with a message like:
Can't open server directory /dev/sd?a/mach_servers: 2502
Server directory? [ /dev/sd?a/mach_servers ]
A3. You can change your SCSI IDs only sequentially from 0 to 3. This results from the difference of handling SCSI devices between FreeBSD and RT-Mach. FreeBSD's SCSI device is named by the order which they are found. RT-Mach's SCSI device named by SCSI ID.For example consider a system which has some SCSI devices whose ID are 0, 2 and 3. FreeBSD and RT-Mach name devices as follows:
SCSI ID FreeBSD RT-Mach 0 sd0 sd0 2 sd1 sd2 3 sd2 sd3
Q4. Lites panics when I remove /mach_servers/emulator
A4. Every process needs Lites emulator, so that they can communicate with Lites server. By default, Lites uses /mach_servers/emulator as a Lites emulator. If you want to change Lites emulator to new one, do as follows:
# mv /mach_servers/emulator /mach_servers/emulator.old
# cp /anywhere/new.emulator /mach_servers/emulator.new
# mv /mach_servers/emulator.new /mach_servers/emulator
Q5. I can't mount NFS file system by mount_nfs with a message like:mount_nfs: /mnt: Invalid argument
A5. By default, mount_nfs first tries to mount NFS file system using version 3, then version 2. Lites currently does not support NFS version 3 but support version 2. You can forcefully mount with version 2 as follows:
# mount_nfs -2 anywhere:/remote/mnt /mnt
Q6. Lites panics by un-identifiable reason and prints prompts "db>".
How do I reboot Lites?
A6. You can reboot Lites as follows:db> call kdreboot
$Id: trouble.html,v 1.2 1999/03/25 13:04:52 moriai Exp $