Fedora 29 64 bit - Raspberry Pi 3 - rngd
by Winfried de Heiden
Hi all,
Using Fedora 29 on Raspberry Pi 3 I seem to have a problem using rndg:
uname -aLinux replica.blabla.bla 4.18.16-300.fc29.aarch64 #1 SMP Sat Oct 20 23:12:22 UTC 2018 aarch64 aarch64 aarch64 GNU/Linuxcat /etc/redhat-release Fedora release 29 (Twenty Nine)
rngd is running:ps -ef | grep rngroot 4710 4409 13 10:57 pts/1 00:00:47 rngd -f -r /dev/hwrng -o /dev/random
The module to support bcm2835 hardware is loaded:lsmod | grep rngbcm2835_rng 16384 0
However, rng is painfully slow:
time rngtest -c 10 < /dev/randomrngtest 6Copyright (c) 2004 by Henrique de Moraes HolschuhThis is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
rngtest: starting FIPS tests...rngtest: bits received from input: 200032rngtest: FIPS 140-2 successes: 10rngtest: FIPS 140-2 failures: 0rngtest: FIPS 140-2(2001-10-10) Monobit: 0rngtest: FIPS 140-2(2001-10-10) Poker: 0rngtest: FIPS 140-2(2001-10-10) Runs: 0rngtest: FIPS 140-2(2001-10-10) Long run: 0rngtest: FIPS 140-2(2001-10-10) Continuous run: 0rngtest: input channel speed: (min=2.201; avg=5.458; max=380.585)Kibits/srngtest: FIPS tests speed: (min=28.132; avg=28.328; max=28.468)Mibits/srngtest: Program run time: 35792670 microseconds
real 0m35.801suser 0m0.001ssys 0m0.071s
Running CentOS 7.5 on an older Raspberry Pi 2 will do much much faster:
ps -ef | grep rngdroot 14024 1 1 10:54 ? 00:00:14 /sbin/rngd -f -r /dev/hwrng -o /dev/random
time rngtest -c 10 < /dev/randomrngtest 5Copyright (c) 2004 by Henrique de Moraes HolschuhThis is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
rngtest: starting FIPS tests...rngtest: bits received from input: 200032rngtest: FIPS 140-2 successes: 10rngtest: FIPS 140-2 failures: 0rngtest: FIPS 140-2(2001-10-10) Monobit: 0rngtest: FIPS 140-2(2001-10-10) Poker: 0rngtest: FIPS 140-2(2001-10-10) Runs: 0rngtest: FIPS 140-2(2001-10-10) Long run: 0rngtest: FIPS 140-2(2001-10-10) Continuous run: 0rngtest: input channel speed: (min=135.793; avg=166.586; max=191.200)Kibits/srngtest: FIPS tests speed: (min=22.076; avg=22.243; max=22.334)Mibits/srngtest: Program run time: 1181718 microseconds
real 0m1.192suser 0m0.002ssys 0m0.141s
Whatś happening here? It seems like the bcm2835_rng is not picked up; despite the module is loaded.
Hope someone can help!
Winfried
5 years, 5 months
Re: no hdmi audio on older tv
by Jiri Vanek
So this is getting more and more funny.
None of your recommendations helped:(( bwd luck, bad thak you a lto anyway for brainstromign.
I borrowed one of the hdmi->Vga+jack boxes (I think it isi this one:
https://iczc.cz/dkqm7qdad2hnra334bu7igbro5_7/obrazek) and....
Now fedora have audio, and raspbian no:D
Considering how hdmi protocol works, I really think that fedroa simply tries newer communication
first (where to change this?) , but fallbeack do not work. And raspbian is trying older
communication first, and fails to upgrade the communication.
Obviously there is some little green goblin in the middle of the way in HDMI :(
On 11/1/18 8:02 PM, stan wrote:
> On Thu, 1 Nov 2018 13:55:53 +0100
> Jiri Vanek <jvanek(a)redhat.com> wrote:
>
>> sudo dnf downgrade kernel
>> Last metadata expiration check: 2 days, 19:55:43 ago on Mon 29 Oct
>> 2018 05:55:23 PM CET. Package kernel of lowest version already
>> installed, cannot downgrade it. same for alsa*
>>
>> I failed to updte kernel. at least Network stopped working:(
>
> Here is the last 4.17 kernel for f29,
>
> https://koji.fedoraproject.org/koji/buildinfo?buildID=1088633
>
> You can try a *newer* kernel, the latest 4.18 kernel, 4.18-16
>
> https://koji.fedoraproject.org/koji/buildinfo?buildID=1154877
>
> or the first 4.19 kernel for 4.30. It should work just fine on f29, I
> think, since I have been compiling it and running it on f28.
I was allready told that for rPI rawhide is bringing many positive changes. So this may be one of
those. Will try later in the development cycle.
>
> https://koji.fedoraproject.org/koji/buildinfo?buildID=1155120
>
> Is there a reason you are using the 4.18-12 kernel?
Nothing particular. It was in stablw when I preapred the baord, and next udpate break networking. So
I turned back.
>
> Have you tried updating your system from the repositories since install?
>
> Here is an older version of alsa you can try. There were two updates
> of alsa only for f29 and f30 after this, so it is a possible difference
> from f28.
>
> https://koji.fedoraproject.org/koji/buildinfo?buildID=1106034
>
> Download the binary rpms for the packages you have installed, then from
> the directory where they are type, as root,
>
> dnf -C downgrade [list of rpms]
>
> If this doesn't solve your problem, I'm stumped. You should have sound.
>
thanx a lot!
J.
5 years, 5 months
Installing on EspressoBin
by Derek G. Buckley
Hello,
Are there any resources/guides on installing fedora to an EspressoBin? I have limited experience installing to arm (raspberry pi and odroid hc2) and this seems to be more difficult then just dd to a sd card and install u-boot. Any resources would be greatly appreciated.
5 years, 5 months
Re: no hdmi audio on older tv
by Jiri Vanek
On 10/30/18 6:23 PM, stan wrote:
> On Tue, 30 Oct 2018 13:41:50 +0100
> Jiri Vanek <jvanek(a)redhat.com> wrote:
>
> I'm not familiar with hdmi, but I'll try to give you some ideas.
>
>> I have f29 (ernel kernel-4.18.12-300.fc29 ) on machine, which is
>> changing its place from time to time - between two TVs. Old, and
>> older:)
>>
>> Both are connected by HDMI. Video output is fine, even acceleration
>> is working, but sound work only on newer of those two.
>>
>> I don't know if this is regression, because this machine replaced 32b
>> rapbery2 with kodi, which was working without issues on both TVs (but
>> was eaten by (not mine) dog)
>
> Can you try an older version of the kernel? Or alsa? It sure sounds
> like a regression, but the audio information doesn't support that. Just
> a check to be sure.
sudo dnf downgrade kernel
Last metadata expiration check: 2 days, 19:55:43 ago on Mon 29 Oct 2018 05:55:23 PM CET.
Package kernel of lowest version already installed, cannot downgrade it.
same for alsa*
I failed to updte kernel. at least Network stopped working:(
>
>>
>> I was following
>> https://fedoraproject.org/wiki/How_to_debug_sound_problems but had
>> not found much:
>> - with removed pulseaudio, the aplay -vv segfaults
>> - I really on pulseaudio anyway, as I need to transfer sound to
>> this machine over network
>>
>> - the diff of alsa-info.sh's is really minimal [1], only
>> [cite]
>> state.vc4hdmi {
>> control.1 {
>> iface PCM
>> name ELD
>> value '100007006712000100000000000000004c2d9d02
>> for non working and
>> value '100007006712000100000000000000004c2d9b03
>> for working
>> [/cite]
>
> If alsa didn't know about the interface for the failing device, it
> wouldn't be able to specify a control. Are there any warnings or
> errors in the journal during boot, or when trying to play?
>>
>> - when alsamixer is opened, then the default looks like working,
>> and the job on old tv; but not do nothing older tv.
>> - when alsamixer -c0 is opened, then the vc4-hdmi reports no
>> control for selected device for *both* tvs (which is same as f6 and
>> selecting vc4-hdmi)
>>
>> Does anybody have a clue what to try?
>
> Great troubleshooting report, very complete.
>
> Is it possible that you changed a setting on the older TV that isn't
> working? Because, like you said, it *should* be working.
>
> What happens if you just use an audio player to send only audio to the
> older TV from the command line? Maybe try such with debugging enabled.
> Or look in the logs to see if it complains about anything.
>
> e.g. mplayer -vv [audio-file]
> or
> mplayer -vv -novideo [video-file]
>
> Since the hdmi is the only device, it should route to the TV to play.
> I think.
>
> If there are no errors and it acts like it is playing, that really
> points to the older TV having an issue.
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>
--
Jiri Vanek
Senior QE engineer, OpenJDK QE lead, Mgr.
Red Hat Czech
jvanek(a)redhat.com M: +420775390109
5 years, 5 months
Re: no hdmi audio on older tv
by Jiri Vanek
On 10/30/18 6:23 PM, stan wrote:
> On Tue, 30 Oct 2018 13:41:50 +0100
> Jiri Vanek <jvanek(a)redhat.com> wrote:
>
> I'm not familiar with hdmi, but I'll try to give you some ideas.
>
>> I have f29 (ernel kernel-4.18.12-300.fc29 ) on machine, which is
>> changing its place from time to time - between two TVs. Old, and
>> older:)
>>
>> Both are connected by HDMI. Video output is fine, even acceleration
>> is working, but sound work only on newer of those two.
>>
>> I don't know if this is regression, because this machine replaced 32b
>> rapbery2 with kodi, which was working without issues on both TVs (but
>> was eaten by (not mine) dog)
>
> Can you try an older version of the kernel? Or alsa? It sure sounds
> like a regression, but the audio information doesn't support that. Just
> a check to be sure.
sure. will do. Just will tak e abit longer.
>
>>
>> I was following
>> https://fedoraproject.org/wiki/How_to_debug_sound_problems but had
>> not found much:
>> - with removed pulseaudio, the aplay -vv segfaults
>> - I really on pulseaudio anyway, as I need to transfer sound to
>> this machine over network
>>
>> - the diff of alsa-info.sh's is really minimal [1], only
>> [cite]
>> state.vc4hdmi {
>> control.1 {
>> iface PCM
>> name ELD
>> value '100007006712000100000000000000004c2d9d02
>> for non working and
>> value '100007006712000100000000000000004c2d9b03
>> for working
>> [/cite]
>
> If alsa didn't know about the interface for the failing device, it
> wouldn't be able to specify a control. Are there any warnings or
> errors in the journal during boot, or when trying to play?
>>
>> - when alsamixer is opened, then the default looks like working,
>> and the job on old tv; but not do nothing older tv.
>> - when alsamixer -c0 is opened, then the vc4-hdmi reports no
>> control for selected device for *both* tvs (which is same as f6 and
>> selecting vc4-hdmi)
>>
>> Does anybody have a clue what to try?
>
> Great troubleshooting report, very complete.
>
> Is it possible that you changed a setting on the older TV that isn't
> working? Because, like you said, it *should* be working.
nope. both raspbian and kodi still keeps playing.
>
> What happens if you just use an audio player to send only audio to the
> older TV from the command line? Maybe try such with debugging enabled.
> Or look in the logs to see if it complains about anything.
>
> e.g. mplayer -vv [audio-file]
> or
> mplayer -vv -novideo [video-file]
I play only from commandline - aplay - and it prints no otput. it behaves corrctly as if it s been
playing. Will try to get more debug output here.
>
> Since the hdmi is the only device, it should route to the TV to play.
> I think.
>
> If there are no errors and it acts like it is playing, that really
> points to the older TV having an issue.
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>
--
Jiri Vanek
Senior QE engineer, OpenJDK QE lead, Mgr.
Red Hat Czech
jvanek(a)redhat.com M: +420775390109
5 years, 5 months
Re: no hdmi audio on older tv
by Jiri Vanek
On 10/31/18 3:32 PM, Stephen John Smoogen wrote:
> I have seen this before but it was due to the HDMI cable. They have
> chips inside of them and if they can't 'talk' correctly with one side
> or the other, they drop sound (aka to stop you from pirating etc). I
> would try a different cable and see if that makes any difference.
Hi!
Had tried this. tired 3 caables. all behave same:
- all works fine with kodi or raspian (Linux cam.local 4.14.71-v7+ #1145 SMP Fri Sep 21 15:38:35
BST 2018 armv7l GNU/Linux
) on both tv
- all works fine with f28 on newer tv, none work with f29 on older tv
so cable out of guilt:(
thanx a lot!
j.
> On Wed, 31 Oct 2018 at 08:33, Jiri Vanek <jvanek(a)redhat.com> wrote:
>>
>>
>> Hello!
>>
>> I have f29 (kernel-4.18.12-300.fc29.aarch64 ) on machine, which is changing its place from time to
>> time - between two TVs. Old, and older:)
>>
>> Both are connected by HDMI. Video output is fine, even acceleration is working, but sound work only
>> on newer of those two.
>>
>> I don't know if this is regression, because this machine replaced 32b rapbery2 with kodi, which was
>> working without issues on both TVs (but was eaten by (not mine) dog)
>>
>> I was following https://fedoraproject.org/wiki/How_to_debug_sound_problems but had not found much:
>> - with removed pulseaudio, the aplay -vv segfaults
>> - I really on pulseaudio anyway, as I need to transfer sound to this machine over network
>>
>> - the diff of alsa-info.sh's is really minimal [1], only
>> [cite]
>> state.vc4hdmi {
>> control.1 {
>> iface PCM
>> name ELD
>> value '100007006712000100000000000000004c2d9d02
>> for non working and
>> value '100007006712000100000000000000004c2d9b03
>> for working
>> [/cite]
>>
>> - when alsamixer is opened, then the default looks like working, and the job on old tv; but not do
>> nothing older tv.
>> - when alsamixer -c0 is opened, then the vc4-hdmi reports no control for selected device for
>> *both* tvs (which is same as f6 and selecting vc4-hdmi)
>>
>> Does anybody have a clue what to try?
>>
>> Thanx in advance form java world,
>> J.
>>
>>
>> [1]
>> --- /home/jvanek/Desktop/workingAudio
>> +++ /home/jvanek/Desktop/nonWorkingAudio
>> @@ -1,5 +1,5 @@
>> STDERR:
>> -cat: /tmp/alsa-info.TzPwpaQcKW/acpidevicestatus.tmp: No such file or directory
>> +cat: /tmp/alsa-info.GXybsmPDbN/acpidevicestatus.tmp: No such file or directory
>> cat: '/sys/module/(null)/parameters/*': No such file or directory
>>
>>
>> @@ -8,7 +8,7 @@
>> !!ALSA Information Script v 0.4.64
>> !!################################
>>
>> -!!Script ran on: Mon Oct 29 14:09:06 UTC 2018
>> +!!Script ran on: Mon Oct 29 14:15:02 UTC 2018
>>
>>
>> !!Linux Distribution
>> @@ -152,7 +152,7 @@
>> control.1 {
>> iface PCM
>> name ELD
>> - value
>> '100007006712000100000000000000004c2d9b0353414d53554e470907070000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
>> + value
>> '100007006712000100000000000000004c2d9d0253414d53554e470907070000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
>> comment {
>> access 'read volatile'
>> type BYTES
>>
>>
>> --
>> Jiri Vanek
>> Senior QE engineer, OpenJDK QE lead, Mgr.
>> Red Hat Czech
>> jvanek(a)redhat.com M: +420775390109
>>
>>
>> _______________________________________________
>> arm mailing list -- arm(a)lists.fedoraproject.org
>> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
>
>
>
--
Jiri Vanek
Senior QE engineer, OpenJDK QE lead, Mgr.
Red Hat Czech
jvanek(a)redhat.com M: +420775390109
5 years, 5 months
