On 09/12/2016 04:40 PM, Martin Michlmayr wrote:
* Philippe Clérié [2016-09-12 16:19]:
I managed to brick my QNAP HS-210 while trying to do a dist-upgrade to
testing. Not my fault though, I blame the whole thing on byobu and a loss of
power.
Anyway, QNAP does have a firmware recovery procedure
* Philippe Clérié [2016-09-12 16:19]:
> I managed to brick my QNAP HS-210 while trying to do a dist-upgrade to
> testing. Not my fault though, I blame the whole thing on byobu and a loss of
> power.
>
> Anyway, QNAP does have a firmware recovery procedure which I'm prepared to
> use, but I was wo
I managed to brick my QNAP HS-210 while trying to do a dist-upgrade to
testing. Not my fault though, I blame the whole thing on byobu and a
loss of power.
Anyway, QNAP does have a firmware recovery procedure which I'm prepared
to use, but I was wondering if there might be a faster way.
My da
On 12/09/2016 21:49, Lennart Sorensen wrote:
On Mon, Sep 12, 2016 at 09:33:12PM +0100, Michael Howard wrote:
As mentioned in an earlier post, the debian installer didn't work with the
AR0 board either. Debian are a bit behind the curve on these server boards.
Could be interesting to compare the
On Mon, Sep 12, 2016 at 09:33:12PM +0100, Michael Howard wrote:
> As mentioned in an earlier post, the debian installer didn't work with the
> AR0 board either. Debian are a bit behind the curve on these server boards.
Could be interesting to compare the /boot/config file for the ubuntu
and debian
On 12/09/2016 19:41, Phil Endecott wrote:
The Ubuntu mini.iso installer from here:
http://ports.ubuntu.com/ubuntu-ports/dists/yakkety/main/installer-arm64/current/images/netboot/
also works, with a 4.4.0 kernel:
[0.00] Booting Linux on physical CPU 0x0
[0.00] Initializing cgrou
On 2016-09-12 19:41 +0100, Phil Endecott wrote:
> The Ubuntu mini.iso installer from here:
>
>
> http://ports.ubuntu.com/ubuntu-ports/dists/yakkety/main/installer-arm64/current/images/netboot/
>
> also works, with a 4.4.0 kernel:
> ACPI is disabled:
>
> [0.083487] ACPI: Interpreter disabl
The Ubuntu mini.iso installer from here:
http://ports.ubuntu.com/ubuntu-ports/dists/yakkety/main/installer-arm64/current/images/netboot/
also works, with a 4.4.0 kernel:
[0.00] Booting Linux on physical CPU 0x0
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializ
lsore...@csclub.uwaterloo.ca wrote:
On Mon, Sep 12, 2016 at 05:47:34PM +0100, Phil Endecott wrote:
(BTW, note "EFI v2.40 by American Megatrends". I think that the people
who've installed UEFI on their MP30-AR0 boards (which shipped with only
U-Boot) have installed the open-source TianoCore. Th
On 12/09/2016 17:47, Phil Endecott wrote:
So that's a 4.2 kernel which seems to be using ACPI.
Presumably this is backported, or something.
The sig-altarch7-aarch64 branch from
'https://git.centos.org/summary/sig-altarch!kernel.git'
--
Mike Howard
On Mon, Sep 12, 2016 at 05:47:34PM +0100, Phil Endecott wrote:
> Hector Oron wrote:
> >using ACPI boot is recommended,
> >however it is not supported until 4.7 kernel series
>
> I've had a look at what CentOS does:
>
> [0.00] Booting Linux on physical CPU 0x0
> [0.00] Initializing
Hector Oron wrote:
using ACPI boot is recommended,
however it is not supported until 4.7 kernel series
I've had a look at what CentOS does:
[0.00] Booting Linux on physical CPU 0x0
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.000
On Mon, Sep 12, 2016 at 02:58:47PM +0100, Phil Endecott wrote:
> Hi Hector,
>
> Thanks for your reply.
>
> Hector Oron wrote:
> >Which BMC firmware are you using? AFAIK there is a broken DTB in the
> >manufacturer's firmware
>
> I replaced the shipped UEFI firmware (version D03 I think) with ver
On Sun, Sep 11, 2016 at 10:36:21PM +0200, Karsten Merker wrote:
> CCing Clint Adams (fakeroot maintainer) in the hope that he might
> be able to provide some further insight.
I don't have access to my ARM devices this week but if I did I would
try what's described in the gdb section of /usr/share/
Hi Hector,
Thanks for your reply.
Hector Oron wrote:
Which BMC firmware are you using? AFAIK there is a broken DTB in the
manufacturer's firmware
I replaced the shipped UEFI firmware (version D03 I think) with version
F01 from
http://b2b.gigabyte.com/products/product-page.aspx?pid=5912#bios
On 2016-09-12 09:03 +0200, Hector Oron wrote:
> Hello,
>
> 2016-09-09 19:29 GMT+02:00 Phil Endecott :
>
> > EFI stub: Booting Linux Kernel...
> > ConvertPages: Incompatible memory types
> > EFI stub: EFI_RNG_PROTOCOL unavailable, no randomness supplied
> > EFI stub: Using DTB from configuration t
Hello,
2016-09-09 19:29 GMT+02:00 Phil Endecott :
> EFI stub: Booting Linux Kernel...
> ConvertPages: Incompatible memory types
> EFI stub: EFI_RNG_PROTOCOL unavailable, no randomness supplied
> EFI stub: Using DTB from configuration table
Which BMC firmware are you using? AFAIK there is a broke
17 matches
Mail list logo