From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: [FEATURE REQUEST] firewire IEEE 1394 (ohci) module
Date: Mon, 14 Nov 2011 13:20:27 +0100 [thread overview]
Message-ID: <4EC1078B.4000704@gmail.com> (raw)
In-Reply-To: <j9r0lc$725$1@dough.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]
On 14.11.2011 13:13, Robert wrote:
> Robert wrote:
>>
>> (as far as Linux is concerned, currently I help me using FiWi by
>> loading the Linux kernel&initrd from another device, which needs
>> special updates etc.)
>>
>
> Note: I remember the first installation of Grub into the internal HD
> MBR while installing Debian 6 on Firewire: Where was no warning, but
> on reboot the Laptop was dead on the rescue prompt of Grub (which
> could do only 'ls' and nothing else). "error: device not found" or so.
> and even the original Windows on intern could not be started.
>
> Maybe there can be added a check&warning at install time if Grub
> cannot load its own modules (which obviously remained on the Firewire
> parititition.)
>
It's not easy to check whether BIOS has firewire support.
> Robert
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next prev parent reply other threads:[~2011-11-14 12:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-13 23:55 [FEATURE REQUEST] firewire IEEE 1394 (ohci) module Robert
2011-11-14 0:21 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-14 12:03 ` Robert
2011-11-14 12:13 ` Robert
2011-11-14 12:20 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2011-11-14 12:16 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=4EC1078B.4000704@gmail.com \
--to=phcoder@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).