From: g6094199@freenet.de
To: development@lists.ipfire.org
Subject: Re: USB i586 install boot panics
Date: Tue, 10 Jan 2017 17:18:31 +0100 [thread overview]
Message-ID: <ab29e28f-99d2-9b9e-a84e-9ec6edeee296@chefmail.de> (raw)
In-Reply-To: <181105c3-a5fe-833d-19d9-7a7ffe4c0fe3@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1060 bytes --]
Am 09.01.2017 um 18:35 schrieb Matthias Fischer:
> On 09.01.2017 17:32, g6094199(a)freenet.de wrote:
>>> He guys!
>>>
>>>
>>> I loaded the current ipfire-2.19.i586-full-core108.iso and created an
>>> usb boot stick (with unetbootin which is quiet reliable imho). While
>>> booting the kernel panics with the error attached in the pic.
>>>
>>> The board is amd e450 based, uefi capable, but bios booted.
>>>
>>>
>>> Now i created an CD out of the iso and this one is working fine. So the
>>> USB behavior is expected, a incompability or a bug?
>>>
>>>
>>> regards
>>>
>>> Sash
> BTDT - not on exactly the same machine, but it worked.
>
> If you got a windows machine handy, you might want to try
> "win32diskimager" to write the image file to USB stick.
>
> => http://sourceforge.net/projects/win32diskimager/
>
> HTH,
> Matthias
>
Hi Matthias,
sorry but no Windoze systems around to test.
Maybe this is a problem with the uefi/bios combination?!
Btw its not a big deal to burn a CD but its some kind of oldschool and a
bit annoing when time is short.
Sash
next prev parent reply other threads:[~2017-01-10 16:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <22b8c33414ec7513e5a2097d70f0cd7b@email.freenet.de>
2017-01-09 17:35 ` Matthias Fischer
2017-01-10 16:18 ` g6094199 [this message]
2017-01-10 17:17 ` Matthias Fischer
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=ab29e28f-99d2-9b9e-a84e-9ec6edeee296@chefmail.de \
--to=g6094199@freenet.de \
--cc=development@lists.ipfire.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