Hi -
> From: Christian Groessler <cpg(a)aladdin.de>
> > Look at the /VERSION file. The first or second line will have
> > the patchlevel. That file's updated by each patch.
>
> I have 400. I assume www.2bsd.com contains the newest patches? So 442
> is the latest?
Wow, that is quite old.
A faster link is at FTP.TO.GD-ES.COM (that's a T-1 vs the ISDL
link I have at home).
It _might_ be easier to create an install tape from the files in
the 2.11 portion of the PUPS archive - I think that was updated
to about patchlevel 432 or so. There is documentation on how to
create a boot tape, etc from the compressed files.
On the other hand it might be instructive/interesting/whatever to
apply the 42 updates manually - just be sure to read the instructions
that come with each one :)
Cheers,
Steven
Warren,
Does the archive contain any Venix images that are not in "tdo" format? I
have been unsuccessful in creating the floppies using that method. If I
could get an image from "dd", I could use my VAX or PDP to create images for
my Pro-380.
Thanks,
-Steve Davidson
Hi,
On 02/27/2002 03:25:22 PM PST "Steven M. Schultz" wrote:
>
>Hello again -
>
>> From: Christian Groessler <cpg(a)aladdin.de>
>> Regarding the patchlevels, how do I find out which patchlevel my
>> system is at?
>
> Look at the /VERSION file. The first or second line will have
> the patchlevel. That file's updated by each patch.
I have 400. I assume www.2bsd.com contains the newest patches? So 442
is the latest?
regards,
chris
Hello again -
> From: Christian Groessler <cpg(a)aladdin.de>
> > Mmmm, I wonder if the problems you were having were caused by
> > /dev not being correctly populated.
>
> Maybe. I noticed they're missing and recreated them by hand. Perhaps I
> made a mistake there.
It would be easy enough to do - or perhaps a critical one was
left out. Filesystems without device nodes can be moved
with a 'tar' pipeline but the root filesystem is special.
> It's a problem of the p11 emulator I use. I got a patch off-list which
> fixed it. It was some signed/unsigned thing.
Ah ha!
> Regarding the patchlevels, how do I find out which patchlevel my
> system is at?
Look at the /VERSION file. The first or second line will have
the patchlevel. That file's updated by each patch.
Cheers,
Steven
Hi,
On 02/26/2002 03:29:07 PM PST "Steven M. Schultz" wrote:
>
> Mmmm, I wonder if the problems you were having were caused by
> /dev not being correctly populated.
Maybe. I noticed they're missing and recreated them by hand. Perhaps I
made a mistake there.
>> $ df
>> Filesystem 1K-blocks Used Avail Capacity Mounted on
>> /dev/xp0a 7816 2658 5158 04% /
>> /dev/xp0g 151625 117599 34026 08% /usr
>> $
>>
>> Btw, the capacity values look a bit strange?
>
> Yes, they do look (more than a little bit) strange.
>
> On my system here (a P11 based emulated PDP-11 - I have a real 11/73
> but it is only powered up when I'm actively testing):
>
>Filesystem 1K-blocks Used Avail Capacity Mounted on
>/dev/xp0a 8228 3163 5065 38% /
>/dev/xp0h 155328 84188 71140 54% /usr
>
> What patchlevel did you mention the system was at? There were a lot
> of patches issued after the ' 2.11_rp_unknown' image was created.
> One thing, which probably will not make any difference, to try would
> be to recompile 'df' (and possibly 'libc') and see if the problem
> changes. Looks like it's a math error of some kind so either
> the compiler/libraries are broken or P11's having a problem doing
> arithmetic.
It's a problem of the p11 emulator I use. I got a patch off-list which
fixed it. It was some signed/unsigned thing.
Regarding the patchlevels, how do I find out which patchlevel my
system is at?
regards,
chris
I've uploaded version 0.0.2 of "v7upgrade" to my Web site:
http://www.southern-storm.com.au/v7upgrade.html
It is now possible to run a stripped-down v7 userland
environment on top of a Linux/i386 kernel, using the
v7 Bourne shell.
A good chunk of the "shellutils" programs have now been
upgraded, including all of your usual favourites (cat, chmod,
cp, date, dd, diff, echo, kill, ls, mkdir, mv, od, rm, rmdir,
among others).
Getting the Bourne shell to work on top of Linux was quite
the adventure, to say the least. S.R. did some very naughty
things in that code. :-)
The code also compiles cleanly for the bcc/8086 target,
although I don't yet have a v7 kernel to run it on yet.
Cheers,
Rhys.
Hello,
I am getting the following error when I try to boot my PDP. The Card
details for the CPU and the Memory Board are as under.
Here are the details of the Various cards.
Slot 1(ABCD) KDJ11-BB (M8190)
Slot 2(ABCD) MSV11-QA(M7551)
Slot 3 (AB) M3107
Slot 3 (CD) Blank
Slot 4 (AB) Solna prinitng machine card
Slot 4 (CD) BIT Scandiavia card
Slot 5 (AB) Blank
Slot 5 (CD) M7555
Can some one please guide what I can do besides replacing the old card
with a new card.
Regards,
Shroff
Testing in progress - Please wait
1 2 3 4 5 6
Error 46
Memory Error
See troubleshooting documentation
Error PC = 173242 PCR page = 15 Program listing address = 015242
R0 = 060000 R1 = 125252 R2 = 125652 R3 = 052525
R4 = 001000 R5 = 040000 R6 = 172300 Par3 = 034000
Expected data = 125252
Bad data = 125652
Address = 03400000
Command Description
1 Rerun test
2 Loop on test
3 Map memory and I/O page
Type a command then press the RETURN key: 3
Memory Map
Starting Ending Size in CSR CSR Bus
Address address K Bytes address type type
00000000 - 03777776 1024 17772100 Parity Qbus
Press the RETURN key when ready to continue
I/O page Map
Starting Ending
Address address
17760440 - 17760456
17765000 - 17765776 CPU ROM or EEPROM
17772100 Memory CSR
17772150 - 17772152
17772200 - 17772276 Supervisor I and D PDR/PAR's
17772300 - 17772376 Kernel I and D PDR/PAR's
17772516 MMR3
17773000 - 17773776 CPU ROM
17777160 - 17777166
17777520 - 17777524 BCSR, PCR, BCR/BDR
17777546 Clock CSR
17777560 - 17777566 Console SLU
17777572 - 17777576 MMR0,1,2
17777600 - 17777676 User I and D PDR/PAR's
17777744 - 17777752 MSER, CCR, MREG, Hit/Miss
17777766 CPU Error
17777772 PIRQ
Press the RETURN key when ready to continue
I/O page Map
Starting Ending
Address address
17777776 PSW
Press the RETURN key when ready to continue
Error 46
Memory Error
See troubleshooting documentation
Error PC = 173242 PCR page = 15 Program listing address = 015242
R0 = 060000 R1 = 125252 R2 = 125652 R3 = 052525
R4 = 001000 R5 = 040000 R6 = 172300 Par3 = 034000
Expected data = 125252
Bad data = 125652
Address = 03400000
Command Description
1 Rerun test
2 Loop on test
3 Map memory and I/O page
Type a command then press the RETURN key:
Hi!
> From: Christian Groessler <cpg(a)aladdin.de>
> > Did you use dump+restor?
>
> No, tar. I tried again with dump and restor and now it works! Thanks
> for the hint! I seldomly use dump/restore.
Ah ha! For moving filesystems dump+restor or 'afio' need to be
used. Dump+restor also have the advantage of preserving the
file flags (see chflags(2) and chflags(1)) - other utilities do
not preserve that metadata.
The other thing that dump+restor (or afio) handle correctly is
the special files in /dev. 'tar' does not know how to archive
files such as "/dev/rp0a".
Mmmm, I wonder if the problems you were having were caused by
/dev not being correctly populated.
> Now there's enough space in /:
>
> $ df
> Filesystem 1K-blocks Used Avail Capacity Mounted on
> /dev/xp0a 7816 2658 5158 04% /
> /dev/xp0g 151625 117599 34026 08% /usr
> $
>
> Btw, the capacity values look a bit strange?
Yes, they do look (more than a little bit) strange.
On my system here (a P11 based emulated PDP-11 - I have a real 11/73
but it is only powered up when I'm actively testing):
Filesystem 1K-blocks Used Avail Capacity Mounted on
/dev/xp0a 8228 3163 5065 38% /
/dev/xp0h 155328 84188 71140 54% /usr
What patchlevel did you mention the system was at? There were a lot
of patches issued after the ' 2.11_rp_unknown' image was created.
One thing, which probably will not make any difference, to try would
be to recompile 'df' (and possibly 'libc') and see if the problem
changes. Looks like it's a math error of some kind so either
the compiler/libraries are broken or P11's having a problem doing
arithmetic.
Cheers,
Steven Schultz
sms(a)2bsd.com
Hi,
On 02/25/2002 09:16:31 AM PST "Steven M. Schultz" wrote:
>
>Hi -
>
>> > I see Greg mentioned running fsck. That sounds like an excellent
>> > suggestion.
>>
>> Yes, but it didn't help :-(
>
>> What can this be?
>
> It might be necessary to use the '-s' option . "fsck -s" will
> unconditionally rebuild the freelist.
This didn't work either.
>
>> I tried something else, I copied the contents of the root fs
>> elsewhere, newfs'd the root partition and copied the contents back.
>
> Did you use dump+restor?
No, tar. I tried again with dump and restor and now it works! Thanks
for the hint! I seldomly use dump/restore.
Now there's enough space in /:
$ df
Filesystem 1K-blocks Used Avail Capacity Mounted on
/dev/xp0a 7816 2658 5158 04% /
/dev/xp0g 151625 117599 34026 08% /usr
$
Btw, the capacity values look a bit strange?
regards,
chris
Hi -
> > I see Greg mentioned running fsck. That sounds like an excellent
> > suggestion.
>
> Yes, but it didn't help :-(
> What can this be?
It might be necessary to use the '-s' option . "fsck -s" will
unconditionally rebuild the freelist.
> I tried something else, I copied the contents of the root fs
> elsewhere, newfs'd the root partition and copied the contents back.
Did you use dump+restor?
> But now booting stops when it normally starts init,
>
Oh no!
> -------------
> : unix
> Boot: bootdev=05010 bootcsr=0176700
>
> 2.11 BSD UNIX #1: Fri Feb 15 18:47:18 PST 2002
> chris@pdp11:/usr/src/sys/PDP11CPG
>
> attaching qe0 csr 174440
> qe0: DEC DEQNA addr 08:00:2b:07:82:6c
> attaching lo0
>
> phys mem = 2097152
> avail mem = 1647872
> user mem = 307200
>
> -------------
>
> ... and here it hangs. Do I have to consider something else when I
> newfs the root partition?
The boot block, /boot, /unix, /netnix and /etc/init, /bin/sh are
intact since the system got as far as printing the memory numbers.
After the memory stats the '/etc/autoconfig' process should be
run ('init' runs it) and the device probes should take place.
The only thing I can think of (and it's a wild guess) is that the
"clock" isn't running - thru the boot process clock interrupts
aren't used but when 'init' goes to run 'autoconfig' the system nees
clock interrupts in order to drive the context switching. Either
the clock isn't running or /etc/autoconfig got corrupted somehow
in the copying.
Steven Schultz
sms(a)2bsd.com
