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
--- Die Bundesliga hat begonnen! Alle Tore, alle Ergebnisse, alle News: Pocket Liga jetzt im https://app.adjust.com/dpynzd oder https://app.adjust.com/dpynzd herunterladen - kostenlos!
On 09.01.2017 17:32, g6094199@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
Am 09.01.2017 um 18:35 schrieb Matthias Fischer:
On 09.01.2017 17:32, g6094199@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
On 10.01.2017 17:18, g6094199@freenet.de wrote:
Am 09.01.2017 um 18:35 schrieb Matthias Fischer:
On 09.01.2017 17:32, g6094199@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,
Hi,
sorry but no Windoze systems around to test.
Ok.
Maybe this is a problem with the uefi/bios combination?!
Since I got rather old machines here - running windows 7 - I don't know... ;-)
Btw its not a big deal to burn a CD but its some kind of oldschool and a bit annoing when time is short.
Faster machines only WAIT faster for your input... ;-))
If you run Linux, meet the Wiki, perhaps this could help:
https://wiki.ipfire.org/en/installation/write-a-flash-image ("Linux and other *nixes")
HTH, Matthias
-
g6094199＠freenet.de -
Matthias Fischer