Hi,
Just asking if this is only me or it's a wider problem: I recently
updated my cubox-i with zypper, pulling in kernel-default-4.4.114, and
after reboot the box boots, but several drivers are missing, so there is
no wired ethernet, no mmcblk, etc.
After booting and waiting for a while, dmesg starts to complain about
driver detection did not finish in time (sadly I don't have the
backtrace at hand, it already went out of the buffer of the serial
console).
For now I worked around the problem this way:
- download the repo-oss (ie. non-update) kernel-default-4.4.76 rpm on an
other machine, copied it to an usb stick
- install the old kernel-default from the usb stick
- copy the /boot from the root fs to the usb stick
- use the other machine to update the /boot on the mmcblk device where
u-boot reads it
So is this only me or do other cubox-i users see the same?
Thanks,
Miklos
Hello,
I am (stilL) trying to boot openSUSE on Rock64. I use JeOS image from
Contrib:Rockchip and manually built bootloader (with
0001-XXX-openSUSE-XXX-Prepend-partition-.patch). And currently I see the
following new issue:
mmc1 is current device
Scanning mmc 1:2...
52462 bytes read in 43 ms (1.2 MiB/s)
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
Scanning mmc 1:1...
Found EFI removable media binary efi/boot/bootaa64.efi
reading efi/boot/bootaa64.efi
1247744 bytes read in 58 ms (20.5 MiB/s)
## Starting EFI application at 02000000 ...
Card did not respond to voltage select!
mmc_init: -95, time 10
Scanning disk rksdmmc(a)ff520000.blk...
Scanning disk rksdmmc(a)ff500000.blk...
Found 2 disks
Welcome to GRUB!
ethernet@ff540000 Waiting for PHY auto negotiation to complete.........
TIMEOUT !
Could not initialize PHY ethernet@ff540000
GNU GRUB version 2.02
Minimal BASH-like line editing is supported. For the first word, TAB
lists possible command completions. Anywhere else TAB lists possible
device or file completions.
grub>
I see that both dtb file and EFI GRUB executable are loaded. But instead
of GRUB menu I see GRUB command line. I suppose it means that grub
failed to fetch GRUB configuration. How could I debug further what is wrong?
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
I experienced problems with the 1GB memory of the Raspberry Pi 3, so I went to
a Banana Pi M64, which has almost the same specifications as the RPi3, except
it has 2 GB memory, and it uses a slightly different CPU. I even found an
image to run openSUSE Tumbleweed on it from a year ago. The image used the
same repository as the repository for the RPi3 (aarch64). However upgrading to
a newer version of Tumbleweed failed. As far as I could see the only issue is
a slightly different kernel and boot system.
Currently I am trying to implement my services on it using Debian Stretch.
I would very much like to use openSUSE on it, because I am more familiar with
it. Debian is quite different, both in managing packages as in configuration
of the services.
If I can be of assistance in implementing openSUSE on a Banana Pi M64 I am
quite willing to do that. Don't know if I have the necessary knowledge.
--
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
There are 2 different cubieboard2 versions:
http://dl.cubieboard.org/model/CubieBoard2/
The 2012 one has nand flash, or TSD flash but I expect that's uncommen.
The 2015 one has EMMC or TSD flash, nand flash versions don't exist, and
a battery for a RTC.
Apparently the EMMC and TSD versions are interchangeable, and that flash
behaves like an SD card.
http://dl.cubieboard.org/model/CubieBoard2/CubieBoard2-20151211-EMMC/Docs/L…
Has anyone tested openSUSE on a 2015 version of cubieboard2? Or is the
JeOS image for the 2012 version? Or both?
Thanks,
Volker
--
Volker Kuhlmann
http://volker.top.geek.nz/ Please do not CC list postings to me.
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi,
is there any chance that the Tumbleweed repo will be getting updates soon?
The current release for both armv6hl and armv7hl is "openSUSE Tumbleweed
20180622".
Ralph
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Leap 15.0 ARM comes preconfigured with a list of repositories that can
be added in yast. Unfortunately, they're all the x86_64 ones.
Which repos can I use for ARM systems - is there a list somewhere?
And is it separate for leap, factory, tumbleweed?
Looking at e.g. https://build.opensuse.org/project/show/security,
ARM architecure building is only enabled for factory_ARM. I'm looking
for some packages for leap 15.0. Am I supposed to use the factory
packages, or how can I get leap packages?
Thanks muchly,
Volker
--
Volker Kuhlmann
http://volker.top.geek.nz/ Please do not CC list postings to me.
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
I have a Samsung Chromebook Plus which as a Rockchip 3399 processor. It
now has Crostini which lets me run Linux distributions in containers.
https://www.reddit.com/r/Crostini/
Naturally I want to run openSUSE. These folks have lots of containers,
including openSUSE but not openSUSE for ARM64.
https://uk.images.linuxcontainers.org/https://us.images.linuxcontainers.org/
Does anybody know to get or make an ARM64 openSUSE container suitable
for Crostini?
Bill
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Which packages do I have to install on a JeOS image to get the yast2
GUI? It's not yast2-x11, and yast2-control-center-qt wants to install
195 packages and 325MB - really? Surely the yast GUI doesn't need ghostscript,
gstreamer, graphviz, a whole pile of languages I couldn't possibly
understand, mozilla-nspr and more mozilla stuff, or
parallel-printer-support, when yast TUI doesn't need all that??
Thanks muchly,
Volker
--
Volker Kuhlmann
http://volker.top.geek.nz/ Please do not CC list postings to me.
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
I'm referring to:
https://en.opensuse.org/HCL:Raspberry_Pi3
-> "USB key installation method" -> 2. Copy the firmware and
bootloader ...
u-boot.bin
==========
Leap 42.3: works
http://download.opensuse.org/ports/aarch64/distribution/leap/42.3/repo/oss/…
TW: won't boot - rainbow screen (see release date!)
http://download.opensuse.org/ports/aarch64/tumbleweed/repo/oss/aarch64/u-bo…
Leap 15.0: won't boot - rainbow screen!
http://download.opensuse.org/ports/aarch64/distribution/leap/15.0/repo/oss/…
raspberrypi-firmware:
=====================
Leap 42.3: too old
https://opensuse.pkgs.org/42.3/opensuse-oss/raspberrypi-firmware-2016.09.02…
TW: dead link!
https://opensuse.pkgs.org/tumbleweed/opensuse-oss/raspberrypi-firmware-2018…
Leap 15.0: the only choice
https://opensuse.pkgs.org/15.0/opensuse-oss/raspberrypi-firmware-2018.03.13…
Was happy to see agraf's changelog from 2018-03-14:
- Update to 3347884 (2018-03-13)
- Add support for new RPi3 B+ (bsc#1085262)
So we have a mess with u-boot.bin (=Leap 42.3) and raspberrypi-firmware
(=Leap 15.0), that enables the sd-card starting on a RPi3 B+!
How to continue?
Download the Leap 42.3 ISO (or the Tumbleweed ISO, or the Leap 15.0 ISO)?
All installations made with kernel command line
"modprobe.blacklist=vc4", as recommended.
Started with TW ISO on USB key:
openSUSE-Tumbleweed-DVD-aarch64-Snapshot20180622.iso
- Installation starts, left me with a black background and a white
mouse-cursor when switching to graphical part.
Leap 15.0:
openSUSE-Leap-15.0-DVD-aarch64-Build124.1.iso
- dto.
Leap 42.3:
- openSUSE-Leap-42.3-DVD-aarch64-Build0200-Media.iso
Installation process starts, but wants to prepare the USB key (itself)
for installation instead of mmcblk0 (sd card).
Trying to adapt the partition scheme from USB0 -> mmc with expert
setting fails (system hanging)!
How to go on?
Any help appreciated!
THX in advance.
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi,
I regularly fetch the latest Chromebook JeOS images via
---
osc getbinaries openSUSE:Factory:ARM:Live JeOS:JeOS-chromebook images armv7l
---
and test them on my Chromebook. The images still fail to boot for me
("Starting Kernel", then black screen forever), but since
openSUSE-Tumbleweed-ARM-JeOS-chromebook.armv7l-2018.07.23-Build1.1 there
are messages that Grub is loading and a splash screen just like on x86_64.
The Leap 15 JeOS image doesn't boot either. It is still unclear to me, why
the Chromebook images fail. I saw U-Boot patches regarding MMC mode and
device tree blob files, not sure whether these are relevant for my issues.
Is somebody out there, who's successfully running the openSUSE armv7l port
on Snow? ChromeOS updates are no longer available for Snow, so running an
alternative OS is more desireable than ever...
Best regards,
--D.
---
Daniel Bischof <suse-bugz(a)bischof.org>
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org