-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Greetings,
I was testing:
openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.armv6l-2017.03.13-Build1.8.raw.xz
from:
http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Ras…
On RaspberryPi 1 Model B
It installs fine - expands the file system, creates the dracut based
init and boots to a usable system. But when I reboot, grub fails with:
error: attempt to read or write outside of partition.
and drops me to the grub rescue system.
Poking around the rescue system, I've found that I can see 4 partitions,
one which is ext2 and has the normal Linux files. From here, most of
the recovery guides say to set the root and prefix variables and then
load the normal module. I can execute the commands:
set root=(hd0,gpt2)
set prefix=(hd0,gpt2)/boot/grub2
and list the files in the various directories - normal.mod exists in
/boot/grub2/arm-efi/ - but when I try:
insmod normal
I still get the error: attempt to read or write outside of partition.
Somewhat interestingly, if I miss-type the prefix (say; /boot/grub) the
error changes to a "file not found" one.
I was hoping someone might have some ideas about what to try next.
- -Alex
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAljUJnYACgkQYZYc2javKOllFQCeNiB6oZYpnKxgmKsbdUtcQNrO
mOIAoJBXe8913EIzBfD04P/PqfPjFv9e
=ZZC3
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
I have just updated my previously working RI 3 to the latest kernel
for openSUSE 42.2
It seems that the device now generates a unique MAC address on the
wired Ethernet connection each time it is powered on. Could this
happen? If so, how can I change it back to use a fixed MAC address?
--
Roger Oberholtzer
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Has anyone been playing with one of these? I'm not making much progress
myself - eventually I'd like to get openSUSE running of course, but for
starters, I'm just trying with the ubuntu core from
http://wiki.friendlyarm.com/wiki/index.php/NanoPi_NEO_Air
The device seems to be booting (blue light flashing), but it's not
picking up an IP-address from dhcp.
--
Per Jessen, Zürich (6.7°C)
http://www.dns24.ch/ - free dynamic DNS, made in Switzerland.
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi,
this is a known OBS bug, asked the admins to deploy a fix shortly.
Greetings,
Dirk
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi Guys,
On the rpi3 since it does not seem to have any CMOS battery type thing
(correct me if I'm wrong), it boots with the epoch time on boot every
time. I am using the following image:
http://download.opensuse.org/ports/aarch64/distribution/leap/42.2/appliance…
I have added an internal corporate ntp server to /etc/ntp.conf, which
works fine, but it takes quite a while for the ntp daemon to sync the
time. The time needs to be correct as some things I am using on the
rpi3 depend on the time being correct (such as docker). Generally
about four minutes in, the time successfully changes:
Thu Jan 1 01:03:50 IST 1970
Thu Mar 16 11:45:19 GMT 2017
I am connected via ethernet, I see the daemon is configured in systemd
to start after network.target, but it seems this is not enough (maybe
it's too soon to start the ntp daemon?) to get the time synced quickly.
Also when this time jump occurs, XFCE decides to lock my screen, so I
have to login again.
Any ideas on solutions, before I come up with my own?
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
I don't seem to be able to run NTP on my nanopi neo air - when I try to
start it, it enters a loop of stopping and starting, reporting "0.0.0.0
c01d 0d kern kernel time sync disabled". If I do a single-shot
"ntpd -g -q", it works. The RTC seems very stable and I don't need
microsecond accuracy, so a once-a-day "ntpd -g -q" would probably be
enough. Still, I'd like to run ntp - is this some sort of hardware
support issue? AFAICT, the Allwinner H3 does have an RTC.
>From dmesg:
[6.850728] sun6i-rtc 1f00000.rtc: rtc core: registered rtc-sun6i as rtc0
[6.850736] sun6i-rtc 1f00000.rtc: RTC enabled
Thanks for your suggestions.
--
Per Jessen, Zürich (6.8°C)
http://www.hostsuisse.com/ - virtual servers, made in Switzerland.
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hello,
I rebooted my raspberry pi today after not being able to ssh
into it under certain scenarios. When booting I now receive the message
"error: You need to load the kernel first" at GRUB. Recovery mode
generates the same error when I go to Advanced Boot Options. I won't
necessarily cry over having to reinstall as it won't take terribly long
to do so, but is there something I can try to resolve this without
reinstalling?
Thanks,
Bryon
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
I wonder what in blocking the update of Tumbleweed for aarch64 on the RPi3.
The last update was on Feb. 2.
--
fr.gr.
member openSUSE
Freek de Kruijf
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi Guys,
I am seeing an issue with configuring static ip and hostname on
openSUSE-Leap42.2-ARM-XFCE-raspberrypi3.aarch64-2017.02.02-Build1.17.raw.xz
image. My colleague Godfrey configures static ip and hostname fine via
UI. It seems once we change the time from 1 Jan 1970 to current time we
seem to lose the static ip. Anybody ever seen an issue like this?
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
