[fedora-arm] Re: no hdmi audio on older tv
On 11/9/18 11:50 AM, Peter Robinson wrote: > On Fri, Nov 9, 2018 at 8:29 AM Jiri Vanek wrote: >> >> 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 >> :( > > Have you tried a different HDMI cable? I've seen issues where people > report problems and try a different cable and it's fine. There's Yes. I tried four cables. Each of them on both TVs. Each behaved same for me. *however* factr that I had tried several different cables, does not mean I used different type of cable. they are very likely from same shop in my neighbourhood, likely same vendor and price level, just bought in different times. > completely different code paths between the upstream fully open stack > that Fedora uses and Raspbian which uses the closed source proprietary > driver where the firmware actually does quite a bit of the work. I'm aware of this difference in view like "it exists". But do not know details of the difference between proprietary and open implementation. I was hoping for magical switch for HDMI, but looks lie there is none. Thanx a lot! J. > >> >> On 11/1/18 8:02 PM, stan wrote: >>> On Thu, 1 Nov 2018 13:55:53 +0100 >>> Jiri Vanek 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. >> ___ >> arm mailing list -- arm@lists.fedoraproject.org >> To unsubscribe send an email to arm-le...@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 jva...@redhat.comM: +420775390109 ___ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-le...@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
[fedora-arm] Re: no hdmi audio on older tv
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 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. ___ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-le...@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
[fedora-arm] Re: no hdmi audio on older tv
On 10/30/18 6:23 PM, stan wrote:
> On Tue, 30 Oct 2018 13:41:50 +0100
> Jiri Vanek 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 '1700671200014c2d9d02
>> for non working and
>> value '1700671200014c2d9b03
>> 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 -- us...@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@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/us...@lists.fedoraproject.org
>
--
Jiri Vanek
Senior QE engineer, OpenJDK QE lead, Mgr.
Red Hat Czech
jva...@redhat.comM: +420775390109
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@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
[fedora-arm] Re: no hdmi audio on older tv
On 10/30/18 6:23 PM, stan wrote:
> On Tue, 30 Oct 2018 13:41:50 +0100
> Jiri Vanek 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 '1700671200014c2d9d02
>> for non working and
>> value '1700671200014c2d9b03
>> 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 -- us...@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@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/us...@lists.fedoraproject.org
>
--
Jiri Vanek
Senior QE engineer, OpenJDK QE lead, Mgr.
Red Hat Czech
jva...@redhat.comM: +420775390109
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@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
[fedora-arm] Re: no hdmi audio on older tv
On 11/1/18 1:37 PM, Jiri Vanek wrote:
> 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
actualy.. on raspbian, aslamixer is not same as in f29. It is same for default,
but it have control
for the v4l-hdmi (just calls it bcm245..whatever according to theirs custom
driver)
> - 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 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 '1700671200014c2d9d02
>>> for non working and
>>> value '1700671200014c2d9b03
>>> 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
>>> '1700671200014c2d9b0353414d53554e47090707'
>>> + value
>>> '1700671200014c2d9d0253414d53554e4709070700000000'
>>> comment {
>>> access 'read volatile'
>>> type BYTES
>>>
>>>
>>> --
>>> Jiri Vanek
>>> Senior QE engineer, OpenJDK QE lead, Mgr.
>>> Red Hat Czech
>>> jva...@redhat.comM: +420775390109
>>>
>>>
>>> ___
[fedora-arm] Re: no hdmi audio on older tv
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 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 '1700671200014c2d9d02
>> for non working and
>> value '1700671200014c2d9b03
>> 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
>> '1700671200014c2d9b0353414d53554e470907070000'
>> + value
>> '1700671200014c2d9d0253414d53554e47090707'
>> comment {
>> access 'read volatile'
>> type BYTES
>>
>>
>> --
>> Jiri Vanek
>> Senior QE engineer, OpenJDK QE lead, Mgr.
>> Red Hat Czech
>> jva...@redhat.comM: +420775390109
>>
>>
>> ___
>> arm mailing list -- arm@lists.fedoraproject.org
>> To unsubscribe send an email to arm-le...@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
jva...@redhat.comM: +420775390109
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@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
[fedora-arm] no hdmi audio on older tv
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 '1700671200014c2d9d02
for non working and
value '1700671200014c2d9b03
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
'1700671200014c2d9b0353414d53554e47090707'
+ value
'1700671200014c2d9d0253414d53554e47090707'
comment {
access 'read volatile'
type BYTES
--
Jiri Vanek
Senior QE engineer, OpenJDK QE lead, Mgr.
Red Hat Czech
jva...@redhat.comM: +420775390109
STDERR:
cat: /tmp/alsa-info.GXybsmPDbN/acpidevicestatus.tmp: No such file or directory
cat: '/sys/module/(null)/parameters/*': No such file or directory
upload=true=true=
!!
!!ALSA Information Script v 0.4.64
!!
!!Script ran on: Mon Oct 29 14:15:02 UTC 2018
!!Linux Distribution
!!--
Fedora release 29 (Twenty Nine) NAME=Fedora ID=fedora PRETTY_NAME="Fedora 29
(Twenty Nine)" CPE_NAME="cpe:/o:fedoraproject:fedora:29"
HOME_URL="https://fedoraproject.org/;
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f29/system-administrators-guide/;
SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help;
BUG_REPORT_URL="https://bugzilla.redhat.com/; REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=29 REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=29
PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy; Fedora
release 29 (Twenty Nine) Fedora release 29 (Twenty Nine)
!!DMI Information
!!---
Manufacturer: raspberrypi
Product Name: rpi
Product Version:
Firmware Version: 2018.09
Board Vendor: raspberrypi
Board Name:rpi
!!ACPI Device Status Information
!!---
!!Kernel Information
!!--
Kernel release:4.18.12-300.fc29.aarch64
Operating System: GNU/Linux
Architecture: aarch64
Processor: aarch64
SMP Enabled: Yes
!!ALSA Version
!!
Driver version: k4.18.12-300.fc29.aarch64
Library version:1.1.6
Utilities version: 1.1.6
!!Loaded ALSA modules
!!---
(null)
!!Sound Servers on this system
!!
Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes
Jack:
Installed - Yes (/usr/bin/jackd)
Running - No
!!Soundcards recognised by ALSA
!!-
0 [vc4hdmi]: vc4-hdmi - vc4-hdmi
raspberrypi-rpi--rpi
!!PCI Soundcards installed in the system
!!--
[fedora-arm] Re: Fwd: raspberry pi aarch64 bcm2835-v4l2 (camera module)
On 10/26/18 1:13 PM, Peter Robinson wrote: > On Thu, Oct 25, 2018 at 11:22 AM Jiri Vanek wrote: >> >> Hmm, >> >> uder some circumstance, after few seconds every desktop X environment goes >> "non drawing" > > I don't know what you mean by this, what are you doing when this > happens, which apps? Sorry for confussion and mixing topics. I had filled a: https://bugzilla.redhat.com/show_bug.cgi?id=1643484 for its tracking. Slim is really dummy login manager, I had originally suspicion that theissue is hidden here. > >> Wen I installed fluxbox, it worked like a charm >> When I add, or install as alon, any "bigger one" - (mate, xfce), it goes non >> drawing, and it even >> prevent fluxbox from proepr work. >> * First few minutes (sometimes only seconds) it works like charm >> * then the gui stop to draw >> * however it responds >> *if you click to menu, nothing show, >> * but if you click any program, again nothing show, but progream starts >> * even cursor changes when it goes over the running, invisible program >> * the program responds (but agian, ntohingis visible) >> >> Can it be messa issue? Do you have some advice about display drivers please? >> J. >> On 10/25/18 11:32 AM, Peter Robinson wrote: >>>> On 10/24/18 1:31 PM, Peter Robinson wrote: >>>>>> Hello! >>>>>> >>>>>> Have somebody sucsesfully run the official[1] rpi camera on Fedora, >>>>>> aarch64? >>>>>> >>>>>> I have f29 sucesfully running on pi 3B+ and the only glitch is my >>>>>> inability tu run cammera:( >>>>> >>>> >>>> Thank you very much for kind answer. Btw, great work on aarch64 and small >>>> baords! >>>> >>>>> Not yet, we do have the drivers enabled in 4.19 in rawhide, and >>>>> there's some changes in Fedora 29 which will allow us to use the >>>>> config.txt to enable HATs and hardware like the the camera. I've not >>>> >>>> There is a question how to do this right. When I was playing with camera >>>> on rasbian, it was eating >>>> enormous resources. So it will not be enugh to jsut read config.txt but >>>> also adapt it in runtime. >>>> >>>> Thus I ended with "dual boot" one with rasbian for camera only, and one >>>> with fully featured fedora. >>> >>> Yes, there's a bunch of work done on a number of components here, the >>> Raspberry Pi has media acceleration engine and various other features >>> that will all assist this, the problem is a lot of these are focused >>> around the original not open source drivers, there's work being done >>> to enable the media acceleration at the same time as the camera. >>> >>>>> had the time to yet pull those bits together to actually test the >>>>> camera and fix the likely missing bits. I'm hoping to get to the final >>>>> pieces including the testing of it and the documentation on how to >>>>> enable it and actually make sure it works in the coming weeks. If >>>>> you're interested in helping out I can provide some details of how I >>>>> think it should work. >>>> >>>> Once the documentation is done, I will hlp with testing for sure. >>>> >>>> TYVM! >>>> J. >>>>> >>>>> Peter >>>>> ___ >>>>> arm mailing list -- arm@lists.fedoraproject.org >>>>> To unsubscribe send an email to arm-le...@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 >>>> jva...@redhat.comM: +420775390109 >>> _______ >>> arm mailing list -- arm@lists.fedoraproject.org >>> To unsubscribe send an email to arm-le...@lists.fedoraproject.org >>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html >>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines &g
[fedora-arm] Re: Fwd: raspberry pi aarch64 bcm2835-v4l2 (camera module)
On 10/25/18 5:13 PM, Jiri Vanek wrote: > On 10/25/18 4:13 PM, Jiri Vanek wrote: >> On 10/25/18 12:22 PM, Jiri Vanek wrote: >>> Hmm, >>> >>> uder some circumstance, after few seconds every desktop X environment goes >>> "non drawing" >>> Wen I installed fluxbox, it worked like a charm >>> When I add, or install as alon, any "bigger one" - (mate, xfce), it goes >>> non drawing, and it even >>> prevent fluxbox from proepr work. >>> * First few minutes (sometimes only seconds) it works like charm >>> * then the gui stop to draw >>> * however it responds >>> *if you click to menu, nothing show, >>> * but if you click any program, again nothing show, but progream starts >>> * even cursor changes when it goes over the running, invisible program >>> * the program responds (but agian, ntohingis visible) >> >> Interesting. When switched to slim, all issues disappeared again...:wq > > One moreupdate: > it looks like resposnible is: > Install mesa-dri-drivers-18.2.2-1.fc29.aarch64 @fedora > Install mesa-filesystem-18.2.2-1.fc29.aarch64@fedora > Install mesa-libGLU-9.0.0-16.fc29.aarch64@fedora one of those is also likely guilty: compiler-rt aarch64 7.0.0-1.fc29 fedora 2.4 M libomp aarch64 7.0.0-1.fc29 fedora 247 k mesa-dri-driversaarch64 18.2.2-1.fc29 fedora11 M mesa-libOpenCL aarch64 18.2.2-1.fc29 fedora 278 k poclaarch64 1.2-0.2.rc1.fc29 fedora 1.8 M qt5-qtwayland aarch64 5.11.1-2.fc29 fedora 772 k And looking to the intersection: mesa-dri-drivers is most likely the winner:( > >>> >>> Can it be messa issue? Do you have some advice about display drivers please? >>> J. >>> On 10/25/18 11:32 AM, Peter Robinson wrote: >>>>> On 10/24/18 1:31 PM, Peter Robinson wrote: >>>>>>> Hello! >>>>>>> >>>>>>> Have somebody sucsesfully run the official[1] rpi camera on Fedora, >>>>>>> aarch64? >>>>>>> >>>>>>> I have f29 sucesfully running on pi 3B+ and the only glitch is my >>>>>>> inability tu run cammera:( >>>>>> >>>>> >>>>> Thank you very much for kind answer. Btw, great work on aarch64 and small >>>>> baords! >>>>> >>>>>> Not yet, we do have the drivers enabled in 4.19 in rawhide, and >>>>>> there's some changes in Fedora 29 which will allow us to use the >>>>>> config.txt to enable HATs and hardware like the the camera. I've not >>>>> >>>>> There is a question how to do this right. When I was playing with camera >>>>> on rasbian, it was eating >>>>> enormous resources. So it will not be enugh to jsut read config.txt but >>>>> also adapt it in runtime. >>>>> >>>>> Thus I ended with "dual boot" one with rasbian for camera only, and one >>>>> with fully featured fedora. >>>> >>>> Yes, there's a bunch of work done on a number of components here, the >>>> Raspberry Pi has media acceleration engine and various other features >>>> that will all assist this, the problem is a lot of these are focused >>>> around the original not open source drivers, there's work being done >>>> to enable the media acceleration at the same time as the camera. >>>> >>>>>> had the time to yet pull those bits together to actually test the >>>>>> camera and fix the likely missing bits. I'm hoping to get to the final >>>>>> pieces including the testing of it and the documentation on how to >>>>>> enable it and actually make sure it works in the coming weeks. If >>>>>> you're interested in helping out I can provide some details of how I >>>>>> think it should work. >>>>> >>>>> Once the documentation is done, I will hlp with testing for sure. >>>>> >>>>> TYVM! >>>>> J. >>>>>> >>>>>> Peter >>>>>> ___ >>>>>> arm mailing list -- arm@lists.fedoraproject.org >>>>&g
[fedora-arm] Re: Fwd: raspberry pi aarch64 bcm2835-v4l2 (camera module)
On 10/25/18 4:13 PM, Jiri Vanek wrote: > On 10/25/18 12:22 PM, Jiri Vanek wrote: >> Hmm, >> >> uder some circumstance, after few seconds every desktop X environment goes >> "non drawing" >> Wen I installed fluxbox, it worked like a charm >> When I add, or install as alon, any "bigger one" - (mate, xfce), it goes non >> drawing, and it even >> prevent fluxbox from proepr work. >> * First few minutes (sometimes only seconds) it works like charm >> * then the gui stop to draw >> * however it responds >> *if you click to menu, nothing show, >> * but if you click any program, again nothing show, but progream starts >> * even cursor changes when it goes over the running, invisible program >> * the program responds (but agian, ntohingis visible) > > Interesting. When switched to slim, all issues disappeared again...:wq One moreupdate: it looks like resposnible is: Install mesa-dri-drivers-18.2.2-1.fc29.aarch64 @fedora Install mesa-filesystem-18.2.2-1.fc29.aarch64@fedora Install mesa-libGLU-9.0.0-16.fc29.aarch64@fedora >> >> Can it be messa issue? Do you have some advice about display drivers please? >> J. >> On 10/25/18 11:32 AM, Peter Robinson wrote: >>>> On 10/24/18 1:31 PM, Peter Robinson wrote: >>>>>> Hello! >>>>>> >>>>>> Have somebody sucsesfully run the official[1] rpi camera on Fedora, >>>>>> aarch64? >>>>>> >>>>>> I have f29 sucesfully running on pi 3B+ and the only glitch is my >>>>>> inability tu run cammera:( >>>>> >>>> >>>> Thank you very much for kind answer. Btw, great work on aarch64 and small >>>> baords! >>>> >>>>> Not yet, we do have the drivers enabled in 4.19 in rawhide, and >>>>> there's some changes in Fedora 29 which will allow us to use the >>>>> config.txt to enable HATs and hardware like the the camera. I've not >>>> >>>> There is a question how to do this right. When I was playing with camera >>>> on rasbian, it was eating >>>> enormous resources. So it will not be enugh to jsut read config.txt but >>>> also adapt it in runtime. >>>> >>>> Thus I ended with "dual boot" one with rasbian for camera only, and one >>>> with fully featured fedora. >>> >>> Yes, there's a bunch of work done on a number of components here, the >>> Raspberry Pi has media acceleration engine and various other features >>> that will all assist this, the problem is a lot of these are focused >>> around the original not open source drivers, there's work being done >>> to enable the media acceleration at the same time as the camera. >>> >>>>> had the time to yet pull those bits together to actually test the >>>>> camera and fix the likely missing bits. I'm hoping to get to the final >>>>> pieces including the testing of it and the documentation on how to >>>>> enable it and actually make sure it works in the coming weeks. If >>>>> you're interested in helping out I can provide some details of how I >>>>> think it should work. >>>> >>>> Once the documentation is done, I will hlp with testing for sure. >>>> >>>> TYVM! >>>> J. >>>>> >>>>> Peter >>>>> ___ >>>>> arm mailing list -- arm@lists.fedoraproject.org >>>>> To unsubscribe send an email to arm-le...@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 >>>> jva...@redhat.comM: +420775390109 >>> ___ >>> arm mailing list -- arm@lists.fedoraproject.org >>> To unsubscribe send an email to arm-le...@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 jva...@redhat.comM: +420775390109 ___ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-le...@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
[fedora-arm] Re: Fwd: raspberry pi aarch64 bcm2835-v4l2 (camera module)
>>> >>> Yes, there's a bunch of work done on a number of components here, the Hello! kernel-4.18.16-300.fc29.aarch64 killed wifi ad sound drivers on my pi 3b+ aarch64 with kernel-4.18.12-300.fc29.aarch64 all works fine. FYI. J. >>> Raspberry Pi has media acceleration engine and various other features >>> that will all assist this, the problem is a lot of these are focused >>> around the original not open source drivers, there's work being done >>> to enable the media acceleration at the same time as the camera. >>> >>>>> had the time to yet pull those bits together to actually test the >>>>> camera and fix the likely missing bits. I'm hoping to get to the final >>>>> pieces including the testing of it and the documentation on how to >>>>> enable it and actually make sure it works in the coming weeks. If >>>>> you're interested in helping out I can provide some details of how I >>>>> think it should work. >>>> >>>> Once the documentation is done, I will hlp with testing for sure. >>>> >>>> TYVM! >>>> J. >>>>> >>>>> Peter >>>>> ___ >>>>> arm mailing list -- arm@lists.fedoraproject.org >>>>> To unsubscribe send an email to arm-le...@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 >>>> jva...@redhat.comM: +420775390109 >>> ___ >>> arm mailing list -- arm@lists.fedoraproject.org >>> To unsubscribe send an email to arm-le...@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 jva...@redhat.comM: +420775390109 ___ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-le...@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
[fedora-arm] Re: Fwd: raspberry pi aarch64 bcm2835-v4l2 (camera module)
On 10/25/18 12:22 PM, Jiri Vanek wrote: > Hmm, > > uder some circumstance, after few seconds every desktop X environment goes > "non drawing" > Wen I installed fluxbox, it worked like a charm > When I add, or install as alon, any "bigger one" - (mate, xfce), it goes non > drawing, and it even > prevent fluxbox from proepr work. > * First few minutes (sometimes only seconds) it works like charm > * then the gui stop to draw > * however it responds > *if you click to menu, nothing show, > * but if you click any program, again nothing show, but progream starts > * even cursor changes when it goes over the running, invisible program > * the program responds (but agian, ntohingis visible) Interesting. When switched to slim, all issues disappeared again...:wq > > Can it be messa issue? Do you have some advice about display drivers please? > J. > On 10/25/18 11:32 AM, Peter Robinson wrote: >>> On 10/24/18 1:31 PM, Peter Robinson wrote: >>>>> Hello! >>>>> >>>>> Have somebody sucsesfully run the official[1] rpi camera on Fedora, >>>>> aarch64? >>>>> >>>>> I have f29 sucesfully running on pi 3B+ and the only glitch is my >>>>> inability tu run cammera:( >>>> >>> >>> Thank you very much for kind answer. Btw, great work on aarch64 and small >>> baords! >>> >>>> Not yet, we do have the drivers enabled in 4.19 in rawhide, and >>>> there's some changes in Fedora 29 which will allow us to use the >>>> config.txt to enable HATs and hardware like the the camera. I've not >>> >>> There is a question how to do this right. When I was playing with camera on >>> rasbian, it was eating >>> enormous resources. So it will not be enugh to jsut read config.txt but >>> also adapt it in runtime. >>> >>> Thus I ended with "dual boot" one with rasbian for camera only, and one >>> with fully featured fedora. >> >> Yes, there's a bunch of work done on a number of components here, the >> Raspberry Pi has media acceleration engine and various other features >> that will all assist this, the problem is a lot of these are focused >> around the original not open source drivers, there's work being done >> to enable the media acceleration at the same time as the camera. >> >>>> had the time to yet pull those bits together to actually test the >>>> camera and fix the likely missing bits. I'm hoping to get to the final >>>> pieces including the testing of it and the documentation on how to >>>> enable it and actually make sure it works in the coming weeks. If >>>> you're interested in helping out I can provide some details of how I >>>> think it should work. >>> >>> Once the documentation is done, I will hlp with testing for sure. >>> >>> TYVM! >>> J. >>>> >>>> Peter >>>> ___ >>>> arm mailing list -- arm@lists.fedoraproject.org >>>> To unsubscribe send an email to arm-le...@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 >>> jva...@redhat.comM: +420775390109 >> ___ >> arm mailing list -- arm@lists.fedoraproject.org >> To unsubscribe send an email to arm-le...@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 jva...@redhat.comM: +420775390109 ___ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-le...@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
[fedora-arm] Re: Fwd: raspberry pi aarch64 bcm2835-v4l2 (camera module)
Hmm, uder some circumstance, after few seconds every desktop X environment goes "non drawing" Wen I installed fluxbox, it worked like a charm When I add, or install as alon, any "bigger one" - (mate, xfce), it goes non drawing, and it even prevent fluxbox from proepr work. * First few minutes (sometimes only seconds) it works like charm * then the gui stop to draw * however it responds *if you click to menu, nothing show, * but if you click any program, again nothing show, but progream starts * even cursor changes when it goes over the running, invisible program * the program responds (but agian, ntohingis visible) Can it be messa issue? Do you have some advice about display drivers please? J. On 10/25/18 11:32 AM, Peter Robinson wrote: >> On 10/24/18 1:31 PM, Peter Robinson wrote: >>>> Hello! >>>> >>>> Have somebody sucsesfully run the official[1] rpi camera on Fedora, >>>> aarch64? >>>> >>>> I have f29 sucesfully running on pi 3B+ and the only glitch is my >>>> inability tu run cammera:( >>> >> >> Thank you very much for kind answer. Btw, great work on aarch64 and small >> baords! >> >>> Not yet, we do have the drivers enabled in 4.19 in rawhide, and >>> there's some changes in Fedora 29 which will allow us to use the >>> config.txt to enable HATs and hardware like the the camera. I've not >> >> There is a question how to do this right. When I was playing with camera on >> rasbian, it was eating >> enormous resources. So it will not be enugh to jsut read config.txt but >> also adapt it in runtime. >> >> Thus I ended with "dual boot" one with rasbian for camera only, and one with >> fully featured fedora. > > Yes, there's a bunch of work done on a number of components here, the > Raspberry Pi has media acceleration engine and various other features > that will all assist this, the problem is a lot of these are focused > around the original not open source drivers, there's work being done > to enable the media acceleration at the same time as the camera. > >>> had the time to yet pull those bits together to actually test the >>> camera and fix the likely missing bits. I'm hoping to get to the final >>> pieces including the testing of it and the documentation on how to >>> enable it and actually make sure it works in the coming weeks. If >>> you're interested in helping out I can provide some details of how I >>> think it should work. >> >> Once the documentation is done, I will hlp with testing for sure. >> >> TYVM! >> J. >>> >>> Peter >>> ___ >>> arm mailing list -- arm@lists.fedoraproject.org >>> To unsubscribe send an email to arm-le...@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 >> jva...@redhat.comM: +420775390109 > ___ > arm mailing list -- arm@lists.fedoraproject.org > To unsubscribe send an email to arm-le...@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 jva...@redhat.comM: +420775390109 ___ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-le...@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
[fedora-arm] Re: Fwd: raspberry pi aarch64 bcm2835-v4l2 (camera module)
On 10/24/18 1:31 PM, Peter Robinson wrote: >> Hello! >> >> Have somebody sucsesfully run the official[1] rpi camera on Fedora, aarch64? >> >> I have f29 sucesfully running on pi 3B+ and the only glitch is my inability >> tu run cammera:( > Thank you very much for kind answer. Btw, great work on aarch64 and small baords! > Not yet, we do have the drivers enabled in 4.19 in rawhide, and > there's some changes in Fedora 29 which will allow us to use the > config.txt to enable HATs and hardware like the the camera. I've not There is a question how to do this right. When I was playing with camera on rasbian, it was eating enormous resources. So it will not be enugh to jsut read config.txt but also adapt it in runtime. Thus I ended with "dual boot" one with rasbian for camera only, and one with fully featured fedora. > had the time to yet pull those bits together to actually test the > camera and fix the likely missing bits. I'm hoping to get to the final > pieces including the testing of it and the documentation on how to > enable it and actually make sure it works in the coming weeks. If > you're interested in helping out I can provide some details of how I > think it should work. Once the documentation is done, I will hlp with testing for sure. TYVM! J. > > Peter > ___ > arm mailing list -- arm@lists.fedoraproject.org > To unsubscribe send an email to arm-le...@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 jva...@redhat.comM: +420775390109 ___ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-le...@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
[fedora-arm] Fwd: raspberry pi aarch64 bcm2835-v4l2 (camera module)
Hello! Have somebody sucsesfully run the official[1] rpi camera on Fedora, aarch64? I have f29 sucesfully running on pi 3B+ and the only glitch is my inability tu run cammera:( Best regards from Java world J. [1] https://www.raspberrypi.org/products/camera-module-v2/ ___ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-le...@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
