Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

kernel modules



jbk wrote:
> Kristian Hermansen wrote:
> 
>> 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...
> 
> Yes, it looks like libata might be far superior as long as you don't 
> have devices that are out of the main stream. I don't know which docs to 
> read. Libata is too new to be in the kernel parameters doc, and is not 
> well documented itself. Looking for something that the maintainers would 
> never think you would want to do...
> 
> Jim KR
> 
> 
I stand corrected on the kernel parameters doc, here is what 
I found:
combined_mode=	[HW] control which driver uses IDE ports in 
combined mode: legacy IDE driver, libata, or both (in the 
libata case, libata.atapi_enabled=1 may be useful as well). 
  Note that using the ide or libata options may affect your 
device naming (e.g. by changing hdc to sdb). Format: 
combined (default), ide, or libata

So in case I'm dense how do I decipher this?

Jim KR

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





BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org