Many web sites nowadays claim that 4.2.10 was the last
COHERENT version. This is wrong, there was 4.2.12 and
4.2.14. I do not have 4.2.12 disks, because back then I had
all sources needed to build a 4.2.12 system from a 4.2.10
distribution. Nowadays you can do that too with everything
open sourced.
In 4.2.14 there were so many changes that one really needs a
complete distribution. I found time to fiddle (don't ask)
with 25 year old floppy disks and got > them imaged. The
4.2.14 distributions disks are available at: https://www.autometer.de/unix4fun/coherent/ftp/distrib/Coherent-4.2.14/
I have installed the base system on Virtualbox and it's
working stable and solid. When I have spare time I'll also
install the DDK and the 4.2.14 kernel sources on the box, to
see how and if the stuff works.
Anyway, you can install and examine the distribution your self :-)
Have fun,
Udo
The device driver for IDE hard disks has bugs in 4.2.14. The source
for the AT driver that corrects one of the bugs is available here:
https://www.autometer.de/unix4fun/coherent/ftp/distrib/Coherent-4.2.14/patches/
I have not noticed any issues with 4.2.14.
But how would I apply the patch ?
Thanks
John
On Sunday, October 11, 2020 at 6:11:27 PM UTC+2, John McCue wrote:
If you use the full kernel source kit you need to repair it there too.
There is another problem somewhere, if you try to fsck the second hd
the kernel will panic. I suspected the IDE disk driver, but even on
close inspection the fixed version looks good to me.
Then I tried the same with the IDE driver from r12, no problem. Do not
do this if you are not a kernel developer! I use cloned VM's for such
things, just to have a look and get an idea and then throw away such
clones.
I am not a kernel developer, but if I think I need
to apply the patch I will use a clone. So far I
have not noticed anything in Virtual Box.
Problem always happens if reading lots of data from a raw
disk device and update wants to sync the disks. So I tried:
dd if=/dev/rat1a of=/tmp/dump bs=512 count=80000
Sure thing, in the moment update tries to sync this also results in a
kernel page fault.
Avoid using a raw disk device if you don't have to.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 443 |
Nodes: | 16 (2 / 14) |
Uptime: | 53:49:30 |
Calls: | 9,188 |
Calls today: | 4 |
Files: | 13,474 |
Messages: | 6,051,200 |