linux-kernel - RE: libata update?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sun, 3 Dec 2006 23:26:44 -0500
From:	"Erik Ohrnberger" <Erik@...ohome.org>
To:	<linux-kernel@...r.kernel.org>
Subject: RE: libata update?

> -----Original Message-----
> From: Robert Hancock [mailto:hancockr@...w.ca] 
> Sent: Sunday, December 03, 2006 10:52 AM
> To: erik@...ohome.org
> Cc: linux-kernel@...r.kernel.org
> Subject: Re: libata update?
> 
> Erik Ohrnberger wrote:
> > It's been a number of months since I build a custom kernel with the 
> > libata incorporated to deal with multiple Promise EIDE controller 
> > card's 'DMA Expiry' errors.
> > 
> > I'd like to re-build basically the same thing with an 
> updated kernel 
> > and updates libata.  Could someone point me into the right 
> direction 
> > to achieve this?
> > 
> > Thanks in advance
> > Erik.
> 
> All of the PATA stuff was merged in 2.6.19, if you want the 
> very latest and greatest you can try the -mm tree..
> 
> -- 

Not to sound too dense or anything, but is there a HOWTO for this kernel to
enable the libata code?  

I've read through the Documentation/kernel-parameters.txt file, and seems
like all I have to do is include libata.atapi_enabled=1 combined_mode=libata
on the grub.conf line to enable it, but when I boot that kernel with that
option, I get an error message: 'Block device /dev/sda1 is not a valid root
device' and a 'boot() ::' prompt.

Thanks in advance,
	Erik.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/