Bug 232783
| Summary: | The ide-tape.ko module that I routinely compile for each kernel update does net recognise the tape device when loaded. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kelly-Rand <jbk> | ||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | Brian Brock <bbrock> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 6 | ||||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2007-03-18 17:39:44 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Kelly-Rand
2007-03-17 19:05:08 UTC
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 reboot). 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? :-) Jon. (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 > reboot). > > 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? Jim K-R 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. My apologies Jim K-R 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. Jim K-R See bug 234106 I have found that the hardware still works in Fc5. |