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
Hi
When will new Tumbleweed images be published for Raspberry Pi 3 (3B, 3B+)?
Images on http://download.opensuse.org/ports/aarch64/tumbleweed/images/
are dated Feb 02, 2018 and don't work on the 3B+.
Or can I use an alternative method to install Tumbleweed on a 3B+? (how?)
Thanks.
Cheers,
Cor.
suse(a)vger.net
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
The openSUSE info for the Beagle Board Black
(https://en.opensuse.org/HCL:BeagleBone_Black) says:
To boot from µSD card, you must press boot select switch
button (near µSD slot) on power-on.
Otherwise, you will boot from internal eMMC.
Is this still the case? I am guessing that this is a board-related
thing. Is there no way to get the board to boot from the µSD card
automatically?
I do not have a card yet. I want to explore the ARM PRU (programmable
real-time unit). But booting from the µSD will be a requirement if we
chose to use this card.
--
Roger Oberholtzer
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi,
I've just booted 15.0 image on BeagleBone Black. It works as expected,
surprisingly, nothing crashed yet.
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi,
When will Leap 15 for Aarch64 arrive? I am already running Leap 15 on my
laptop and wanted to give it a try also on my SoftIron ARM box. But
currently
http://download.opensuse.org/ports/aarch64/distribution/leap/15.0/iso/
is empty...
Bye,
CzP
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi,
Trying to setup the pi to work with a UHD monitor, I've been reading
that it can be done, but I've got what appears to be one remaining
hurdle.
This works:
#cvt -r 3840 2160 60
#xrandr --newmode "3840x2160" 533.00 3840 3888 3920 4000 2160 2163
2168 2222 +hsync -vsync
#xrandr --addmode HDMI-1 3840x2160
This doesn't:
#xrandr --output HDMI-1 --mode "3840x2160" --rate 60 --fb 4096x4096 --
panning 4096x4096
error is:
xrandr: screen cannot be larger than 2048x2048 (desired size
4096x4096)
How do I change the default to something larger than 2048x2048
(desired is 4096x4096)?
Is there a way to change it dynamically, or do I need to do some work
with xorg.conf files?
I pulled the image openSUSE-Tumbleweed-ARM-X11-raspberrypi3.aarch64-
2018.04.30-Build2.4.raw.xz but it doesn't seem to matter which one I
start with, they all have the 2048x2048 limit.
-Steve
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
I am very pleased to see a new image for the Raspberry Pi 3B in repository
http://download.opensuse.org/ports/aarch64/tumbleweed/images
I installed the image and it works. I also noticed that /boot/grub2/grub.conf
only contains one console parameter, console=ttyS1,115200n8, on the boot
command line. I have a connected serial interface to the proper GIO pins and I
do see the initial output of the boot process appear on the screen. Even the
GRUB screen, when pressing t. However I used to see also the output of the
boot process of openSUSE, which used to appear when having only this console
parameter in the boot command. This output does not appear.
How do I get this output and how do I get the ability to log in on this serial
line?
Bug report?
--
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
Hello,
Is it possible to have Ubuntu:18.04:Ports with aarch64?
I am trying to make some experiments with GStreamer and RockChip SBC and
I need to rebuild specific deb-packages. Everything was ok until I found
that only x86_64 is available.
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org