public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Keith Roberts <keith@karsites.net>
Cc: devzero@web.de, linux-kernel@vger.kernel.org
Subject: Re: Problems with edd
Date: Wed, 11 Jun 2008 13:13:46 -0700	[thread overview]
Message-ID: <485031FA.6070303@zytor.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0806112102350.18067@www.karsites.net>

Keith Roberts wrote:
>>
>> I have put in syslinux 3.70-pre16 code to print the source of this 
>> message.  You may want to try to grab isolinux from this release and 
>> update your CD image to get some useful debugging info out of this.
>>
>>     -hpa
> 
> Not being a kernel guru, I'm not sure how to do that hpa?
> 
> Where do I get isolinux from please?
> 

ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/syslinux-3.70-pre16.tar.bz2

> how do I update my CD image?

You will need to run mkisofs with the same options used to generate the 
image.

In a pinch, if you can point me to the original ISO I could try to 
doctor it.

> I'm willing to give this a try if it will sort out the problem.

That would be useful.  This is potentially a previously unreported BIOS 
issue which might have a straightforward workaround, so I'm eager to get 
the data.

	-hpa

  reply	other threads:[~2008-06-11 20:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10 21:58 Problems with edd devzero
2008-06-10 22:44 ` H. Peter Anvin
2008-06-10 22:48 ` H. Peter Anvin
2008-06-10 23:39 ` H. Peter Anvin
2008-06-11 20:08   ` Keith Roberts
2008-06-11 20:13     ` H. Peter Anvin [this message]
2008-06-11 23:52       ` Keith Roberts
2008-06-11 23:55         ` H. Peter Anvin
2008-06-11 11:18 ` Keith Roberts
  -- strict thread matches above, loose matches on Subject: below --
2008-06-10 17:48 Keith Roberts

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=485031FA.6070303@zytor.com \
    --to=hpa@zytor.com \
    --cc=devzero@web.de \
    --cc=keith@karsites.net \
    --cc=linux-kernel@vger.kernel.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