From: Keith Roberts <keith@karsites.net>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problems with edd
Date: Thu, 12 Jun 2008 00:52:40 +0100 (BST) [thread overview]
Message-ID: <alpine.LFD.1.10.0806120029040.23296@www.karsites.net> (raw)
In-Reply-To: <485031FA.6070303@zytor.com>
On Wed, 11 Jun 2008, H. Peter Anvin wrote:
> To: Keith Roberts <keith@karsites.net>
> From: H. Peter Anvin <hpa@zytor.com>
> Subject: Re: Problems with edd
>
> 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.
OK - thankyou for that, hpa
> In a pinch, if you can point me to the original ISO I could try to doctor
> it.
I originally got mine from:
http://mirror.switch.ch/ftp/mirror/fedora/linux/releases/9/Fedora/i386/iso/Fedora-9-i386-netinst.iso
The sha1sum is:
3b1df20ece05d64c34dd9c64400975b74eded0f2 Fedora-9-i386-netinst.iso
I have also put it on my website, just in case it gets
updated on the mirrors:
http://www.karsites.net/fedora/9/Fedora-9-i386-netinst.iso
obviously same sha1sum ;)
The Fedora guys are following this thread now. I have put
the link to your patch on my Fedora bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=450678
I have never built an iso file before, but I'll read up on
it. My plan was to copy the files from the F9 net-installer
CD to my hard drive, update them with your patch, and then
re-make the iso file and burn that back to CD-R. Would that
work?
>> 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
Regards
Keith
next prev parent reply other threads:[~2008-06-11 23:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 21:58 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
2008-06-11 23:52 ` Keith Roberts [this message]
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=alpine.LFD.1.10.0806120029040.23296@www.karsites.net \
--to=keith@karsites.net \
--cc=hpa@zytor.com \
--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
all inboxes | Powered by JetHome®