From: "Vesa Jääskeläinen" <chaac@nic.fi>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH/DRAFT] Support linux boot protocol >= 2.02 long command-lines
Date: Fri, 02 May 2008 20:07:06 +0300 [thread overview]
Message-ID: <481B4A3A.5020305@nic.fi> (raw)
In-Reply-To: <9e0cf0bf0805020959xc8bbd57u889988bc2a2111ca@mail.gmail.com>
Alon Bar-Lev wrote:
> On 5/2/08, Vesa Jääskeläinen <chaac@nic.fi> wrote:
>> Hi Alon,
>>
>> So when did vmware stop working? Can you tell me what you did try to do to
>> get it working? I have one vmware here handy so I could try it out.
>>
>> Thanks,
>> Vesa Jääskeläinen
>
> Hi!
>
> Stopped working when I installed grub-2 :)
> Working fine with grub-1.
>
> I am using vmware-server-1.0.5.80187, with ide configuration also for disks.
>
> But anyway... Why don't I get lspci command available if I added this
> to grub-install and see it loaded in lsmod output?
Hi Alon,
Actually I meant that I have used it before in vmware desktop and it
worked fine. So I was wondering when it got broken and how did exactly
you try it out to reproduce the issue here. Because grub 2 "has to" work
in vmware too :)
Eg. tell that you ran this and this. And then did that.
I think lspci might also need some device database. So if it cannot load
it may fail. But lets first tackle this vmware problem :)
Thanks,
Vesa Jääskeläinen
next prev parent reply other threads:[~2008-05-02 17:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 16:36 [PATCH/DRAFT] Support linux boot protocol >= 2.02 long command-lines Alon Bar-Lev
2008-05-02 16:50 ` Vesa Jääskeläinen
2008-05-02 16:59 ` Alon Bar-Lev
2008-05-02 17:07 ` Vesa Jääskeläinen [this message]
2008-05-02 17:17 ` Alon Bar-Lev
2008-05-02 18:04 ` Vesa Jääskeläinen
2008-05-02 18:10 ` Alon Bar-Lev
2008-05-02 18:27 ` Vesa Jääskeläinen
2008-05-02 19:03 ` Alon Bar-Lev
2008-05-02 19:44 ` Vesa Jääskeläinen
2008-05-02 20:28 ` Alon Bar-Lev
2008-05-02 20:48 ` Vesa Jääskeläinen
2008-05-02 21:04 ` Alon Bar-Lev
2008-05-02 21:17 ` Alon Bar-Lev
2008-05-02 21:39 ` [PATCH] " Alon Bar-Lev
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=481B4A3A.5020305@nic.fi \
--to=chaac@nic.fi \
--cc=grub-devel@gnu.org \
/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.