* "Stefan G. Weichinger" <monitor AT oops.co DOT at> [2004:03:08:16:03:45+0100]
scribed:
> Hi, Michael,
>
> on Montag, 08. März 2004 at 15:48 you wrote to amanda-users:
>
> MDS> I am using the stock Debian kernel:
>
> MDS> kernel-image-2.6.3-1-686
>
> MDS> From config-2.6.3-1-686:
>
> MDS> #
> MDS> # SCSI device support
> MDS> #
> MDS> CONFIG_SCSI=m
> MDS> CONFIG_SCSI_PROC_FS=y
>
> MDS> #
> MDS> # SCSI support type (disk, tape, CD-ROM)
> MDS> #
> MDS> CONFIG_BLK_DEV_SD=m
> MDS> CONFIG_CHR_DEV_ST=m
> ...
>
> MDS> What am I missing?
>
> Maybe you don't have the right modutils installed. The format of
> modules has changed with 2.6, so you need other tools for using and
> handling them.
>
> Are you able to do a "modprobe scsi" in your 2.6-environment?
>
> Do the commands modprobe, lsmod, rmmod work there?
For the record, upgrading module-init-tools from 3.0-pre9-1 to
3.0-pre10-1 did the trick for me!
I do not know why this worked, because the changelog indicates only some
upstream release issue.
Also, as a loadable module (regardless kernel 2.4.25 or 2.6.3), `st' is
_not_ loaded (e.g., lsmod) until userland tries to use it. In my case,
that is the `mt-st' package, which I have not changed in many weeks.
Bottomline, I upgraded module-init-tools and rebooted, and now userland
has no problems communicating with /dev/nst0.
Thank you for your help.
--
Best Regards,
mds
mds resource
877.596.8237
-
Dare to fix things before they break . . .
-
Our capacity for understanding is inversely proportional to how much
we think we know. The more I know, the more I know I don't know . . .
--
signature.asc
Description: Digital signature
|