| Author |
Problem installing Digital Unix on FreeAXP |
rsilva
Member
Posts: 4
Joined: 24.02.11 |
| Posted on February 28 2011 04:06 |
|
|
I'm trying to setup Digital Unix 4.0C on FreeAXP and when booting from the Digital Unix CD it always fails to mount the root file system.
My FreeAXP configuration is very simple: only a clean disk image file on DKA100 for the installation and the CD drive on DKA200. I've already tried different alternatives as far as the DKA100 disk file is concerned:
1 - A new 2GB disk image file created with FreeAXP.
2 - A new 1,5 GB disk image of type RZ27 downloaded from the FreeAXP site (empty disk image files available for download).
3 - A new 2GB disk image file created and formatted with disklabel and newfs at a PersonalAlpha emulator that I installed previously with the same Digital Unix version.
With all of them the installation always fails as following:
>>>BOOT DKA200
(boot dka200.2.0.6.0 -flags A)
block 0 of dka200.2.0.6.0 is a valid boot block
reading 16 blocks from dka200.2.0.6.0
bootstrap code read in
base = 1f2000, image_start = 0, image_bytes = 2000
initializing HWRPB at 2000
initializing page table at 1e4000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code
Digital UNIX boot - Fri Nov 15 21:24:46 EST 1996
Loading hupdate ...
Starting hupdate at 0x20000000
Loading vmunix ...
Loading at fffffc0000230000
Current PAL Revision <0x1000000010538>
Switching to OSF PALcode Succeeded
New PAL Revision <0x100000002012e>
Sizes:
text = 4769280
data = 1253168
bss = 2497296
Starting at 0xfffffc0000404240
B-cache could not be auto-sized
Alpha boot: available memory from 0xc80000 to 0x7ffe000
Digital UNIX V4.0B (Rev. 564); Sat Nov 16 00:01:00 EST 1996
physical memory = 128.00 megabytes.
available memory = 115.57 megabytes.
using 161 buffers containing 1.25 megabytes of memory
AlphaServer 400 4/166 system
DECchip 21071
82378IB (SIO) PCI/ISA Bridge
Firmware revision: 7.0
PALcode: OSF version 1.46
pci0 at nexus
psiop0 at pci0 slot 6
Loading SIOP: script 800200, reg 82000400, data 40844180
scsi0 at psiop0 slot 0
rz0 at scsi0 target 0 lun 0 (LID=0) (DEC RZ58 (C) DEC 2000) (Wide32)
rz2 at scsi0 target 2 lun 0 (LID=1) (DEC RRD42 (C) DEC 4.5d) (Wide32)
isa0 at pci0
gpc0 at isa0
ace0 at isa0
fd internal driver error: FDI PROBE FAIL (A,11).
fdi0 not probed
tu0: DECchip 21040-AA: Revision: 4.1
tu0: ethernet address pattern not found
tu0 in pci slot 11 not probed
kernel console: ace0
ADVFS: using 1152 buffers containing 9.00 megabytes of memory
panic (cpu 0): vfs_mountroot: cannot mount root
syncing disks... done
DUMP: No primary swap, no explicit dumpdev.
Nowhere to put header, giving up.
halted CPU 0
halt code = 5
HALT instruction executed
PC = fffffc0000405cb0
>>>
I had absolutely no problem in installing the same operating system in Personal Alpha but with FreeAXP it always fails. Can anyone please give me a clue about this?
Thanks in advance. |
|
|
| Author |
RE: Version of FreeAXP Possibly ? |
John Manger
Moderator
Posts: 63
Location: nr Heathrow, Middlesex, UK
Joined: 18.03.10 |
| Posted on March 01 2011 02:53 |
|
|
Hi,
What version of FreeAXP are you experimenting with ?
I notice the boot strings indicate 'Digital UNIX V4.0B (Rev. 564)'. V4.0B is not one we have tested yet, but I'd expect it to work ... However, at this point, I'm wondering if this is a product of an old/older release of FreeAXP ? since we don't see vfs_mountroot panics at all under V3.2C/G or V4.0D/F/G.
Either way, since you have release V4.0B, we would be very interested in obtaining a copy to test with.
regards,
John M
Edited by John Manger on March 02 2011 00:47 |
|
|
| Author |
RE: pka0_disconnect setting ? |
John Manger
Moderator
Posts: 63
Location: nr Heathrow, Middlesex, UK
Joined: 18.03.10 |
| Posted on March 01 2011 03:07 |
|
|
Hi again,
Try setting pka0_disconnect to 0 before you boot :
>>> set pka0_disconnect 0
>>> init
ff.fe.fd.fc.fb.fa.f9.f8.f7.f6.f5.
ef.df.ee.ed.ec.f4.eb.ea.e9.e8.e7.e6.....e5.
V7.0-9, built on Mar 18 1999 at 13:25:37
>>> boot dka200
It ~might~ help.
John M |
|
|
| Author |
RE: Problem installing Digital Unix on FreeAXP |
rsilva
Member
Posts: 4
Joined: 24.02.11 |
| Posted on March 01 2011 06:01 |
|
|
Hi John,
I'm using the last FreeAXP version (307) and the label on my Digital Unix CD says "DIGITAL UNIX V4.0C" and "Includes DIGITAL UNIX 4.0B" so probably the kernel version is in fact 4.0B.
I'm running FreeAXP on a PC with Windows XP SP2 1GB RAM, but I've also tried in a Windows 2003 server with 3GB RAM and the results were the same.
Interestingly, I followed your suggestion of setting pka0_disconnect to 0 and it still fails but now with a completely new description:
>>>boot dka200
(boot dka200.2.0.6.0 -flags 0)
block 0 of dka200.2.0.6.0 is a valid boot block
reading 16 blocks from dka200.2.0.6.0
bootstrap code read in
base = 1f2000, image_start = 0, image_bytes = 2000
initializing HWRPB at 2000
initializing page table at 1e4000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code
Digital UNIX boot - Fri Nov 15 21:24:46 EST 1996
Loading hupdate ...
Starting hupdate at 0x20000000
Loading vmunix ...
Loading at fffffc0000230000
Current PAL Revision <0x1000000010538>
Switching to OSF PALcode Succeeded
New PAL Revision <0x100000002012e>
Sizes:
text = 4769280
data = 1253168
bss = 2497296
Starting at 0xfffffc0000404240
B-cache could not be auto-sized
Alpha boot: available memory from 0xc80000 to 0x7ffe000
Digital UNIX V4.0B (Rev. 564); Sat Nov 16 00:01:00 EST 1996
physical memory = 128.00 megabytes.
available memory = 115.57 megabytes.
using 161 buffers containing 1.25 megabytes of memory
AlphaServer 400 4/166 system
DECchip 21071
82378IB (SIO) PCI/ISA Bridge
Firmware revision: 7.0
PALcode: OSF version 1.46
pci0 at nexus
psiop0 at pci0 slot 6
Loading SIOP: script 800200, reg 82000000, data 40844180
cam_logger: CAM_ERROR packet
cam_logger: bus 0 target 2 lun 3
ss_perform_timeout
timeout on disconnected request
cam_logger: CAM_ERROR packet
cam_logger: bus 0 target 2 lun 3
ss_abort_done
SCSI abort has been performed
trap: invalid memory read access from kernel mode
faulting virtual address: 0x0000000000000050
pc of faulting instruction: 0xfffffc00004e7800
ra contents at time of fault: 0xfffffc00004e8be8
sp contents at time of fault: 0xffffffff8798b988
panic (cpu 0): kernel memory fault
DUMP: No primary swap, no explicit dumpdev.
Nowhere to put header, giving up.
halted CPU 0
halt code = 5
HALT instruction executed
PC = fffffc0000405cb0
>>>
This sounds to errors related with the disks emulation don't you think(it doesn't even display the SCSI devices found)?
When I reset pka0_disconnect to 1 again, it failed with the same error messages I posted the first time.
I have another older Digital Unix V3.2D but with this one the results are even worse:
>>>init
ff.fe.fd.fc.fb.fa.f9.f8.f7.f6.f5.
ef.df.ee.ed.ec.f4.eb.ea.e9.e8.e7.e6.....e5.
V7.0-9, built on Mar 18 1999 at 13:25:37
>>>show
auto_action HALT
boot_dev
boot_file
boot_osflags 0
boot_reset OFF
bootdef_dev
booted_dev
booted_file
booted_osflags
bus_probe_algorithm old
char_set 0
console serial
control_disfd enable
control_idema enable
control_irq11 scsi
control_irq12 mouse
control_scsi_term internal
controlp on
dump_dev
enable_audit ON
ffauto OFF
ffnext OFF
kbd_hardware_type PCXAL
language 36
language_name English(American)
license MU
mopv3_boot OFF
os_type UNIX
pal VMS PALcode V5.56-2, OSF PALcode X1.46-2
pci_parity off
pka0_disconnect 1
pka0_fast 1
pka0_host_id 7
quick_start OFF
scsi_poll ON
srm2ctrl
srm2dev
sys_serial_num
tga_sync_green 0
timer_tps 1
tt_allow_login 1
tty_dev 0
version V7.0-9 Mar 18 1999 13:25:37
>>>boot dka200
(boot dka200.2.0.6.0 -flags 0)
block 0 of dka200.2.0.6.0 is a valid boot block
reading 16 blocks from dka200.2.0.6.0
bootstrap code read in
base = 1f2000, image_start = 0, image_bytes = 2000
initializing HWRPB at 2000
initializing page table at 1e4000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code
can't open osf_boot
halted CPU 0
halt code = 5
HALT instruction executed
PC = 20000030
>>>
Can it be a CD problem? I'm going to try to copy them.
Regards,
rsilva |
|
|
| Author |
RE: Problem installing Digital Unix on FreeAXP |
rsilva
Member
Posts: 4
Joined: 24.02.11 |
| Posted on March 01 2011 08:42 |
|
|
Hi again,
I'm wondering if this cannot be a problem with the CDs. I retried several times in different machines and sometimes fails saying:
panic (cpu 0): vfs_mountroot: cannot mount root
and other times fails saying:
cam_logger: CAM_ERROR packet
cam_logger: bus 0 target 2 lun 3
ss_perform_timeout
This later one refers to bus 0 target 2 which is the CD, right?
Anyway, as I was successful installing on PersonalAlpha some time ago, I had the idea of starting up FreeAXP using the PersonalAlpha disk (I read somewhere in the user manual that this would be possible). However now I have a very basic failure: when starting FreeAXP with the PersonalAlpha disk it says that the CPU is different and then halts.
In fact FreeAXP emulates an Alpha Server 400 and PersonalAlpha emulates a DEC3000/400, but according to the user manual FreeAXP would support it. Am I missing something?
|
|
|
| Author |
RE: Odd results .... |
John Manger
Moderator
Posts: 63
Location: nr Heathrow, Middlesex, UK
Joined: 18.03.10 |
| Posted on March 01 2011 11:36 |
|
|
It certainly looks like a disk or scsi problem. For now, forget about pka0_disconnect ;-) I think I'll get Bruce to release to you a more recent version as 307 will be replaced very shortly by a new release of FreeAXP anyway.
As to using a PA boot disk, as you say PA emulates a DEC 3000-400, which is quite different from an Alphaserver 400. The former was a turbo-channel system, the later a PCI system. Booting the '/genvmunix' (-file /genvmunix) from your PA build may work ~if~ it is V3.2C or later. The Alphaserver 400 4/166 is only supported by V3.2C upwards.
The V3.2D boot result looks most odd. Clearly the disk is 'visible' :
> block 0 of dka200.2.0.6.0 is a valid boot block
>reading 16 blocks from dka200.2.0.6.0
...but then it can't find to the filesystem's boot program
> can't open osf_boot
Have you got the image DKA200 set to 'cd', or is this the physical device ? If it is the physical CD, is Explorer accessing the device ? or the index service attempting to index it ?, or autorun attempting to examine it ? The older Tru64 CDs are not in any format known to Windows ...
Could you show us your cfg file ?
regards,
John M |
|
|
| Author |
RE: Problem installing Digital Unix on FreeAXP |
rsilva
Member
Posts: 4
Joined: 24.02.11 |
| Posted on March 02 2011 01:40 |
|
|
Hi,
I received Bruce's new version and finally I could successfully install from my Digital Unix CD without any errors and it seems to be working well! THANKS A LOT!
Now I'm going to configure the system and to make more deep tests and I will let you know the final results with this V4.0B version.
Regarding your questions about the problems with the FreeAXP 307, now I know that the CDs are good as the installation with the 345 version was successful - I'm using original DEC CDs in both cases (V4.0B and V3.2D). I will still try to follow your clues about the Windows index service or autorun, because for me this also seems very odd. As a final note, Windows Explorer in fact doesn't show any content from the CDs.
The config file is as follows:
/* -- FreeAXP Config --
-1000
9000
4098
C:\Program Files\FreeAXP\Capela_dka0.img
1
4
1
1
1
1
-- */
cp = control
{
cp_log = logfile
{
filename = "C:\Program Files\FreeAXP\Capela.log";
}
alpha = alpha
{
memory=128M;
image = "C:\Program Files\FreeAXP\Capela.nvr";
pcibus = dc21071da
{
data = "C:\Program Files\FreeAXP\Capela.toy";
serial0 = i16550
{
s0_tn = telnet
{
port = 9000;
wait = true;
action = """C:\Program Files\FreeAXP\putty.exe"" telnet://localhost:9000";
}
}
pci7 = i82378
{
}
pci6 = symbios
{
disk0.0 = file
{
image = "C:\Program Files\FreeAXP\Capela_dka0.img";
}
disk0.2 = device
{
device = "\\.\cdrom0";
read_only = true;
cdrom = true;
}
}
}
}
}
|
|
|
