On Mon, 2010-04-12 at 02:10 +0100, Bruno Girin wrote:
> With *-20, it won't boot anymore.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/561151
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/
On Mon, 2010-04-12 at 12:09 +0530, Vishal Rao wrote:
> Bruno,
>
> What are your hardware specs and SSD model?
>
> Try passing " libata.force=noncq " as kernel boot param and see if it helps?
>
> Helps with my Intel DP5DP motherboard and Crucial M225 SSD (IndiLinux
> barefoot controller/firmware)
Bruno,
What are your hardware specs and SSD model?
Try passing " libata.force=noncq " as kernel boot param and see if it helps?
Helps with my Intel DP5DP motherboard and Crucial M225 SSD (IndiLinux
barefoot controller/firmware)...
HTH
Vishal
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-d
On Sun, Apr 11, 2010 at 8:10 PM, Bruno Girin wrote:
> Hi all,
>
> First of all, apologies for cross-posting to different lists, I'm just
> not sure where is the best place to ask this question.
>
> I upgraded my laptop to Lucid beta 2 today, in an attempt to test-drive
> it. It all worked fine unt
Hi all,
First of all, apologies for cross-posting to different lists, I'm just
not sure where is the best place to ask this question.
I upgraded my laptop to Lucid beta 2 today, in an attempt to test-drive
it. It all worked fine until the system updated the kernel from
2.6.32-19 to 2.6.32-20. Wit