Adobe Flash for arm64 does not exist. ADOBE stopped supporting Flash some time ago. It is dead technology.

https://clinicalmbchb.com/flash-player-support-on-arm64-os-samsung-dex-android/

U need to try out something around rasbian better, fedora I doubt will fully support old arm on 32 bit


El 30 abr. 2020 11:04, ng0...@gmail.com escribió:
Hi, since I am quite happy now with the RPi 4B and Workstation 32 on, it is still not fit for the purpose of streaming video of some old cctv cameras that only work via a browser flash plugin.

Two options exist:

1) Firefox w/ install instructions from https://docs.fedoraproject.org/en-US/quick-docs/using-adobe-flash/ which fail:
  - package flash-plugin-32.0.0.363-release.i386 does not have a compatible architecture
  - package flash-plugin-32.0.0.363-release.x86_64 does not have a compatible architecture

and

2) Chromium following these instructions which work fine on my desktop computer:

sudo gtar xzf flash_player_ppapi_linux.x86_64.tar.gz -C /usr/lib64/chromium-browser/PepperFlash/
cd /usr/lib64/chromium-browser/PepperFlash/
sudo chown -R root:root *

However both fail on the RPi 4B when testing them https://get.adobe.com/flashplayer/about/ Other than flash video content plays fine on it.

Any ideas for a quick fix and/or what is planned upstream?

BTW, if anyone tries to set up a hotspot that should remember to run "sudo nm-connection-editor" and change the firewall setting from "default" to e.g. Workstation. Otherwise, it will not allow to connect when firewalld is not installed. It took me quite some time to figure out that one.

Regards, Thomas B

On Wed, Apr 22, 2020 at 5:23 PM Thomas H.P. Andersen <phomes@gmail.com> wrote:


On Sat, Apr 18, 2020 at 10:56 AM Thomas <ng0177@gmail.com> wrote:

> Just remove the cma= entry in the grub.cfg on the vfat partition it
> will be easier, and an order of magnitude quicker.


> I had a similar issue with recent kernels that I solved by removing
> a cma= setting from the kernel boot line.

I removed cma= but it had no effect, see below.

Thanks, Thomas


Fedora-Workstation-32-20200416.n.0.aarch64.raw.xz

/EFI/fedora/grub.cfg

  set kernelopts="root=UUID=72ca87a8-123e-4645-a352-05639bb65638 ro
cma=256MB "


You should update both EFI/fedora/grub.cfg and EFI/fedora/grubenv
 
> But do be warned, there is no accelerated graphics on the RPi4 and
> hence it is well and truly unsupported for any graphical systems.
>
> > On Fri, Apr 17, 2020 at 1:17 PM Peter Robinson <
> > pbrobinson@gmail.com> wrote:
> > >
> > > On Fri, Apr 17, 2020 at 12:13 PM <ng0177@gmail.com> wrote:
> > > >
> > > > Thanks for that! In one of latest images it gets stuck at the
> > > > point shown in the attached screenshot.
> > >
> > > What image are you using, full file name please.
> > >
> > > What revision of the hardware do you have? You should have a line
> > > at
> > > the early U-Boot phase that looks something like:
> > > RPI 4 Model B (0xc03111)
> > >
> > > I'm interested in the hex values at the end.
> > >
> > > > Good to have your clarification on RPi4 support in the Kernel.
> > > >
> > > > Thomas
> > > >
> > > > On Fri, Apr 17, 2020 at 12:01 PM Peter Robinson <
> > > > pbrobinson@gmail.com> wrote:
> > > > >
> > > > > Hi Thomas,
> > > > >
> > > > > > Hi, testing of daily images from
> > > > > > https://dl.fedoraproject.org/pub/fedora-secondary/development/32/Workstation/aarch64/images/
> > > > > > Raspberry Pi 4 defies the keyboard.
> > > > >
> > > > > I'm not sure what you mean by defies in this context? They
> > > > > keyboard
> > > > > doesn't work? At what point are you having issues. There is
> > > > > no support
> > > > > for USB (actually the PCIe), hence keyboards, in the U-Boot
> > > > > firmware
> > > > > which means it won't work in grub or the early boot process.
> > > > > Once it
> > > > > gets to Linux such as the login prompt they keyboard should
> > > > > work find
> > > > > as there is USB support.
> > > > >
> > > > > > I have been under the assumption that 5.6 has support
> > > > > > built-in? Any ideas?
> > > > >
> > > > > Support for what exactly? Support for a device such as the
> > > > > RPi4 is not
> > > > > a binary thing. There is initial support and enablement so
> > > > > it's useful
> > > > > for a number of situations but the support is far from
> > > > > complete and
> > > > > hence while for a it works for a lot of use cases we don't
> > > > > officially
> > > > > support the RPi4 yet because the HW enablement is incomplete.
> > > > >
> > > > > Peter
_______________________________________________
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org

_______________________________________________
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org

Reply via email to