All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: "René Rebe" <rene@exactcode.de>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Alexey Zaytsev <alexey.zaytsev@gmail.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] AHCI problems.
Date: Tue, 17 May 2011 16:13:55 +0200	[thread overview]
Message-ID: <48AB5324-57E1-4142-BA05-8ACCF57EB981@suse.de> (raw)
In-Reply-To: <84C1E0C8-21B7-4CB5-A5FC-781F0679F287@exactcode.de>


On 17.05.2011, at 16:07, René Rebe wrote:

> Hi,
> +
> On 17.05.2011, at 15:46, Alexander Graf wrote:
> 
>> 
>> On 15.05.2011, at 18:41, Alexey Zaytsev wrote:
>> 
>>> Hi again.
>>> 
>>> After reverting 667bb59, ahci works fine in Linux, if I boot it with
>>> -kernel, but grub seems to have some problems.
>>> Grub2 gets to the rescue prompt. The disk and its partitions seem to
>>> be detected correctly, but not the filesystem.
>>> Grub-legacy (from illumos) complains about checksum verification
>>> failures, supposedly in stage2.
>> 
>> So I just tried again and grub-legacy works just fine for me with an opensuse image, after rebuilding SeaBIOS to enable AHCI. I suppose you're trying this on Ubuntu?
> 
> This is exactly the phenomena I was seeing the other week when I tested it. From a quick glance it looked like the BIOS returned errors when grub tried to read the FS.

Hm. Ok, I'll give Ubuntu a spin then.


Alex

  reply	other threads:[~2011-05-17 14:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-15 16:41 [Qemu-devel] AHCI problems Alexey Zaytsev
2011-05-17 13:46 ` Alexander Graf
2011-05-17 14:07   ` René Rebe
2011-05-17 14:13     ` Alexander Graf [this message]
2011-05-19 20:29   ` Alexey Zaytsev
2011-05-20 17:27     ` Alexey Zaytsev
2011-05-21  9:08       ` Alexander Graf
2011-05-21 10:26         ` Alexey Zaytsev
2011-05-21 11:46           ` Alexey Zaytsev
2011-05-21 12:00             ` Alexander Graf
2011-05-21 13:56               ` Alexey Zaytsev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48AB5324-57E1-4142-BA05-8ACCF57EB981@suse.de \
    --to=agraf@suse.de \
    --cc=alexey.zaytsev@gmail.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rene@exactcode.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.