From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:220.127.116.11) Gecko/20070313 Fedora/18.104.22.168-5.fc6 Firefox/22.214.171.124
Description of problem:
I have been using this tape drive for 5 Yrs. without problem. I do have to compile the ide-tape.ko module at every kernel update but that has never been a problem and I did the same for this update. The tape drive is a Seagate STT8000a atapi drive on ide1 typically identified as hdd on my system.
What I have noticed about the latest compiled module is that it is approximately 30Kbytes smaller than the last 4 modules that I have compiled.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. After kernel update download matching kernel source srpm. Execute the rpmbuild > kernel.spec command to build the patched source tree as normal user. CD to /ide directory where ide-tape.c is located and rename the existing Makefile to makefile.orig
2. Create Makefile per the release note instructions for compiling kernel modules for the running kernel. Issue the make command as normal user, review the output for error messages, none reported.
3. As root copy ide-tape.ko to /lib/modules/2.6.20-1.2925.fc6/kernel/drivers/ide/
4. Issue depmod -a, issue MAKEDEV -x ht0 nht0 or reboot for devices to be created
5. Issue mt -f /dev/nht0 status, in this case I get the following:
/dev/nht0: No such device or address
/dev/nht0: No such device or address
I should see the status output that shows what block is currently listed and some error check output for the device.
# less /var/log/dmesg | head
Linux version 2.6.20-1.2925.fc6 (email@example.com) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-51)) #1 SMP Sat Mar 10 18:38:39 EST 2007
Command line: ro root=LABEL=/12 iommu=noaperture rhgb quiet
I will post log and command output as an attachment.
Created attachment 150319 [details]
Output from log/messages and list of previous modules compiled
I have listed the severity as normal, but for me I cannot upgrade to this kernel
till the problem is resolved. I cannot access or create backups without the
ide-tape module working.
Do you have the tape module correctly loaded, and is the device node in /dev
there? (it'll be managed by udev so mknoding it won't make much difference on a
There are better ways of building modules than *in* the kernel tree - you can
build the module separately and overwrite the original if really needed. But,
why do you need to build your own tape module, anyway? :-)
(In reply to comment #3)
> Do you have the tape module correctly loaded, and is the device node in /dev
> there? (it'll be managed by udev so mknoding it won't make much difference on a
> There are better ways of building modules than *in* the kernel tree - you can
> build the module separately and overwrite the original if really needed.
I do use short cuts in compiling, I grabbed from a couple different source trees
and compiled one at a time inserting each in lib/modules as described
above,overwriting each in turn, but I don't know what you mean by "in the kernel
tree" other than I could compile in the user directory some folder. The kernel
tree is a good filing system that keeps me familiar with the structure.
> why do you need to build your own tape module, anyway? :-)
I need to compile ide-tape because it is not compiled by default being
considered "expiremental" by the maintainers. I've used it for ten years so it
baffles me that it is considered as such. Ide-scsi needs a separate cable
because it shares the same cable as the cd. I don't care to install a separate
controller and have another piece of hardware to maintain.
Now, what output would be helpful in diagnosing this?
Please table this bug report.
I have just discovered that there is a hardware problem with the drive that
occured just prior to the latest kernel update.
We still need to look at what happens to tape devices now that
IDE subsystem is gone. In theory, they should be picked by st
automatically with libata... or do they?
That worries me scripts for all the ide devices.
See bug 234106
I have found that the hardware still works in Fc5.