I am trying to install openSUSE 13.2 on a cubieboard1 that I bought
about 2 years ago. It has an A10 and the PCB is labelled 2012-09-09.
Out of the box it boots flawlessly into the Android 4.0.4, kernel 3.0.8
Nov 2012, stored on its nand flash ex factory. See its serial output
below.
Putting this
[0s] Using BUILD_ROOT=/var/cache/obs/worker/root_4/.mount
[0s] Using BUILD_ARCH=armv7l:armv6l:armv5tel
[0s] Doing kvm build in /var/cache/obs/worker/root_4/root
[0s]
[1s]
[1s] armbuild18 started "build exaile.spec" at Tue Mar 24 08:56:31 UTC 2015.
[1s]
[1s] Buildi
On 24.03.15 09:59, Andreas Schwab wrote:
> [0s] Using BUILD_ROOT=/var/cache/obs/worker/root_4/.mount
> [0s] Using BUILD_ARCH=armv7l:armv6l:armv5tel
> [0s] Doing kvm build in /var/cache/obs/worker/root_4/root
> [0s]
> [1s]
> [1s] armbuild18 started "build exaile.spec" at
On 24.03.15 09:37, Volker Kuhlmann wrote:
> I am trying to install openSUSE 13.2 on a cubieboard1 that I bought
> about 2 years ago. It has an A10 and the PCB is labelled 2012-09-09.
>
> Out of the box it boots flawlessly into the Android 4.0.4, kernel 3.0.8
> Nov 2012, stored on its nand flash
This image at least boots:
http://download.opensuse.org/ports/armv7hl/factory/images/openSUSE-Factory-ARM-JeOS-cubieboard.armv7l-1.12.1-Build269.1.raw.xz
However it fails to activate networking in general (no IPv4 address, no
routes, no gateway, no resolv.conf - yes the LAN DHCP server works
well)
On Dienstag, 24. März 2015, 10:09:10 wrote Alexander Graf:
>
> On 24.03.15 09:59, Andreas Schwab wrote:
> > [0s] Using BUILD_ROOT=/var/cache/obs/worker/root_4/.mount
> > [0s] Using BUILD_ARCH=armv7l:armv6l:armv5tel
> > [0s] Doing kvm build in /var/cache/obs/worker/root_4/root
> > [
On 24.03.15 10:34, Volker Kuhlmann wrote:
> This image at least boots:
> http://download.opensuse.org/ports/armv7hl/factory/images/openSUSE-Factory-ARM-JeOS-cubieboard.armv7l-1.12.1-Build269.1.raw.xz
>
> However it fails to activate networking in general (no IPv4 address, no
> routes, no gateway
On 24.03.15 10:35, Adrian Schröter wrote:
> On Dienstag, 24. März 2015, 10:09:10 wrote Alexander Graf:
>>
>> On 24.03.15 09:59, Andreas Schwab wrote:
>>> [0s] Using BUILD_ROOT=/var/cache/obs/worker/root_4/.mount
>>> [0s] Using BUILD_ARCH=armv7l:armv6l:armv5tel
>>> [0s] Doing kvm build
On Dienstag, 24. März 2015, 10:41:21 wrote Alexander Graf:
>
> On 24.03.15 10:35, Adrian Schröter wrote:
> > On Dienstag, 24. März 2015, 10:09:10 wrote Alexander Graf:
> >>
> >> On 24.03.15 09:59, Andreas Schwab wrote:
> >>> [0s] Using BUILD_ROOT=/var/cache/obs/worker/root_4/.mount
> >>> [
On 24.03.15 10:46, Adrian Schröter wrote:
> On Dienstag, 24. März 2015, 10:41:21 wrote Alexander Graf:
>>
>> On 24.03.15 10:35, Adrian Schröter wrote:
>>> On Dienstag, 24. März 2015, 10:09:10 wrote Alexander Graf:
On 24.03.15 09:59, Andreas Schwab wrote:
> [0s] Using BUILD_ROOT=
armbuild15:
[ 6729s] ### WATCHDOG MARKER START ###
[ 6732s] [ 6698.252495] SysRq : Power Off
[ 6732s] [ 6698.253838] reboot: Power down
[ 6737s] Warning: clean shut down of the VM didn't work
[ 6737s] [ 6703.295918] Kernel panic - not syncing: Attempted to kill init!
exitcode=0x
[ 6737s]
Hi Andreas,
> [ 6737s] [ 6703.295918] Kernel panic - not syncing: Attempted to kill init!
> exitcode=0x
> [ 6737s] [ 6703.295918]
> [ 6739s] [ 6703.298680] Rebooting in 1 seconds..Reboot failed -- System halted
Apparently the guest kernel needs more features now, I’ll look into it.
G
Hi Adrian,
> [ 16s] linux64 /usr/bin/qemu-system-arm -no-reboot -nographic -vga none
> -net none -enable-kvm -M virt
Thats the issue, some when the build script was changed to use -M virt. It
would have been great to know such major changes that in advance :-(
I’ll try to fix it up
On Dienstag, 24. März 2015, 11:56:15 wrote Dirk Müller:
> Hi Adrian,
>
> > [ 16s] linux64 /usr/bin/qemu-system-arm -no-reboot -nographic -vga
> > none -net none -enable-kvm -M virt
>
> Thats the issue, some when the build script was changed to use -M virt. It
> would have been great
>> [ 6737s] [ 6703.295918] Kernel panic - not syncing: Attempted to kill init!
>> exitcode=0x
>> [ 6737s] [ 6703.295918]
>> [ 6739s] [ 6703.298680] Rebooting in 1 seconds..Reboot failed -- System
>> halted
> Apparently the guest kernel needs more features now, I’ll look into it.
This is
On Dienstag, 24. März 2015, 15:53:14 wrote Dirk Müller:
> >> [ 6737s] [ 6703.295918] Kernel panic - not syncing: Attempted to kill
> >> init! exitcode=0x
> >> [ 6737s] [ 6703.295918]
> >> [ 6739s] [ 6703.298680] Rebooting in 1 seconds..Reboot failed -- System
> >> halted
> > Apparently th
On 03/24/2015 03:57 PM, Adrian Schröter wrote:
On Dienstag, 24. März 2015, 15:53:14 wrote Dirk Müller:
[ 6737s] [ 6703.295918] Kernel panic - not syncing: Attempted to kill init!
exitcode=0x
[ 6737s] [ 6703.295918]
[ 6739s] [ 6703.298680] Rebooting in 1 seconds..Reboot failed -- System
Hi,
>> hm, does it make sense to have also "virt" kernel&initrd images in
>> kernel-obs-build
>> package?
> No, the -default flavor should just run on all machine types.
It should, but its not as efficient. -default is more than twice the
size (and needs initrd) than the guest kernel.. its not th
On 03/24/2015 06:16 PM, Dirk Müller wrote:
Hi,
hm, does it make sense to have also "virt" kernel&initrd images in
kernel-obs-build
package?
No, the -default flavor should just run on all machine types.
It should, but its not as efficient. -default is more than twice the
size (and needs initrd
19 matches
Mail list logo
