kernel modules

[doctormo at gmail.com (Martin Owens)]

Does this effect the operation of HAL? because I've got a number of
devices in my researching (optical drives mostly) saying their scsi
devices and yet are children of the ide chipset. very odd I thought
but this might be a reason for it and I can make amends.

Best Regards, Martin Owens

On 08/05/07, Kristian Hermansen <kristian.hermansen at gmail.com> wrote:
> jbk wrote:
> > The kernel maintainers have introduced a new way to address ide devices
> > via the libata module. From what I can glean from the conversations I
> > have encoutered on bugzilla (RH) the new driver addresses ide devices as
> > scsi. This has created problems for some users myself included. I have
> > an atapi tape drive that just doesn't work under that regime. I have
> > found that I can manually unload all the scsi modules and then I can
> > access the tape drive just fine. But how do I keep these scsi modules
> > from reloading  on reboot?
>
> libata is far superior than the old IDE subsystem.  However, if you need
> to disable it for any reason, you should be able to pass an option to
> the kernel like libata=0.  Check the docs...
> --
> Kristian Hermansen
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> _______________________________________________
> Discuss mailing list
> Discuss at blu.org
> http://lists.blu.org/mailman/listinfo/discuss
>

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.