3.2v4.2 hardware failure on boot

[edfair]

I'm soliciting suggestions for solution on the following failure on a new install of 3.2v4.2 with 426D (Y2K patch) on a P100 dual boot dos/unix 520mb scsi primary (200dos/320unix), 500 mb scsi secondary, scsi tape.
Installs correctly from tape, attaches the second drive and allows it to be used. Then fails at some unknown point after multiple reboots.
Hardware record of good boot:
F0 to F4 %serial 0
F5 F6 %floppy
F7F8F9 %console
F10F11F12 %adapter
F13F14 %tape
GH0to H6 %disk
Hardware record of failure:
F0 to F4 %serial 0
%serial 1 (note: I haven't configured this)
F5F6 %floppy
F7F8F9 %console
F10 %parallel (I haven't configured this either)
F11F12F13 %adapter
F14 Warning: No Computone board found (faulty error message)
F15F16 %tape
Once the failure happens the tape is useless and the 2nd hard drive doesn't attach. It isn't recognized as a legitimate device.
Hard drives and scsi controller have been replaced. Ed Fair
efair@atlnet.com

Any advice I give is my best judgement based on my interpretation of the facts you supply.

Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.

 

[stanhubble]

Ed ,

are you restoring anything?
it looks like its booting a different kernel.
are you configuring something that is suggesting a reboot?
can you boot with the unix.old?

stan

 

[edfair]

Loaded stuff from tape onto both drives, but nothing conflicting with OS files.
Have only unix & unix.old with .old being the one prior to the initial rebuild where it added the BTLD scsi driver.
Unix and unix.old both give the hardware detect problem.
I probably will reinstall from floppies as a double check, but don't think it will make a difference.
And the fact that it does it on a normal reboot blows my mind. Ed Fair
efair@atlnet.com

Any advice I give is my best judgement based on my interpretation of the facts you supply.

Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.

 

[stanhubble]

Ed,

is the pnp option turned off in the bios?

 

[edfair]

yes Ed Fair
efair@atlnet.com

Any advice I give is my best judgement based on my interpretation of the facts you supply.

Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.

 

[edfair]

Mis-spoke. All legacy isa except pci/isa-pnp on irq11 for the scsi controller. Ed Fair
efair@atlnet.com

Any advice I give is my best judgement based on my interpretation of the facts you supply.

Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.

 

[Megabitman]

My first guess is that the Computone board is conflicting with the PCI controller. I see that you've manually set the IRQ for all devices in the bios to legacy.. except the SCSI... what Computone board are you using? The real old boards failed above 16 MBytes of RAM (Good Lord, can you imagine in this day and age?) because of the addressing... and what about the release number of the driver? What scsi controller? Things that make you go hmmmmmm.....

 

[edfair]

There is no Computone board. It, and the 2nd serial port plus the parallel port show up somehow after the data from 2 filesystems is restored. This is a program and data only restore from a system that has a Computone board and the other hardware installed.
Nothing I can see from the backupedge generated data backup accesses any of the initialization files to put these devices into the kernel.
I have traced to the point that it is coming on the restore but haven't had time yet to do a detail search of what is actually being restored.
Backupedge generation is for two locations /avs and /avs99 (avs is a filesystem) and tarring it off onto the new machine gets the failure on the next boot. Ed Fair
efair@atlnet.com

Any advice I give is my best judgement based on my interpretation of the facts you supply.

Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.

 

[Megabitman]

Sorry for the delay in getting back to you... somehow you are restoring the /unix kernel. That's the ONLY way that hardware devices will show up after a restore (the stubs for the devices are "linked" into the kernel and regardless whether the devices exist or not, they will show up). Since that must be the case, you are replacing the kernel with a version that probably doesn't contain the same mount points and/or instructions. You might need to make a copy of the /unix kernel before you restore, then copy it back.

Let me know

 

[edfair]

It isn't coming from a restored kernel. I copied the kernel from a good one then copied it back after a restore just to be sure.
Suspicion only at this time thatit is something in a boot up file that is trying to initialize. But I haven't dug into the backupedge archive to see what it might have saved in addition to the directories it was supposed to. Ed Fair
efair@atlnet.com

Any advice I give is my best judgement based on my interpretation of the facts you supply.

Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.