Many thanks to Dr. Thomas P. Blinn, who got me running in the right
direction.
Turns out that it wasn't USB at all that was messing me up, but the
aha_chim driver. In fact, the USB driver loads just fine.
The machine that I was trying to get to run 5.1 has an Adaptec 7891B based
controller in it. When it would boot the kernel, it would fall over on the
driver which seems to be specifically made for Adaptec 7895 chips. I don't
need either of these chips in Tru64, so dropping them wasn't an issue.
the final solution is this:
-install the disk on another machine
-make a custom kernel and edit the kernel config to put a # in front of
the line refering to the aha_chim module
-remove the aha_chim module from /sys/BINARY
after all this, the system will work correctly.
Kurt
Original Question:
> Hi all,
> we're trying to run Tru64 v5.1, Whenever the kernel boots, it fails at
> loading the USB drivers. Is there a kernel flag to disable the USB driver
> in the kernel?
>
> thanks,
> Kurt
Responses:
On what platform? If there is a USB interface chip in the system, the
USB support is going to get loaded. There is no kernel flag to disable
the USB support. Some platforms are KNOWN to have a defective USB chip
on them, and for those platforms (the AlphaPC 164/SX is the only one I
know of off-hand), the USB subsystem won't configure. But Digital did
not ever sell the AlphaPC 164/SX motherboards with UNIX support, and as
far as I know, there should be none of these really odd boards out in
the real world running Tru64 UNIX V5.1.
But I can't say for certain that there are no other platforms that
were ever built that have a defective USB interface; and you didn't
say what platform you've got.
If you can identify the USB driver lines in the kernel configuration
file, then you can build a target kernel (if you can get the system
to boot!) that will not have USB support built into the kernel. Then
if you can find the USB support kernel module on disk (it should be
in /sys/BINARY) and rename it (or remove it), when you boot your new
kernel that doesn't have USB support, the support won't get loaded
into the kernel "on the fly" (because if it's not in the kernel and
the system knows which module is needed, it WILL get loaded during
the system startup process).
The more likely problem is either (a) you have a defective device on
your USB bus, or (b) you have a defective motherboard with a broken
USB interface chip.
But without knowing a lot more about your configuration, I have no
idea which of the two above is the root cause.
Tom
Dr. Thomas P. Blinn + UNIX Software Group + Compaq Computer Corporation
110 Spit Brook Road, MS ZKO3-2/W17 Nashua, New Hampshire 03062-2698
Technology Partnership Engineering Phone: (603) 884-0646
Internet: tpb_at_zk3.dec.com Compaq's Easynet: alpha::tpb
ACM Member: tpblinn_at_acm.org PC_at_Home: tom_at_felines.mv.net
Worry kills more people than work because more people worry than work.
Keep your stick on the ice. -- Steve Smith ("Red Green")
My favorite palindrome is: Satan, oscillate my metallic sonatas.
-- Phil Agre, pagre_at_alpha.oac.ucla.edu
Yesterday it worked / Today it is not working / UNIX is like that
-- apologies to Margaret Segall
Opinions expressed herein are my own, and do not necessarily represent
those of my employer or anyone else, living or dead, real or imagined.
Received on Fri Oct 27 2000 - 01:29:16 NZDT