Raspberry pi 4 second monitor problem on xeno3

Raspberry pi 4 second monitor problem on xeno3

[77dab]

  

Hi, it is the first time I ask for an help on this mailing list.
My
setup:
-Raspberry Pi 4, 4gb ram (forced to 3gb) running debian buster
64bit.

pi@picat:~ $ uname -a
Linux picat 4.19.126-v8-xeno3+ #1 SMP
PREEMPT Wed Mar 24 12:53:24 +07 2021 aarch64 GNU/Linux 

pi@picat:~ $
hostnamectl

...cut...
Operating System: Debian GNU/Linux 10 (buster)

Kernel: Linux 4.19.126-v8-xeno3+
 Architecture: arm64

- two HDMI
identical monitor connected . 1920x1080 60Hz 148.6 MHz clock.

My
propblem:
on a clean raspbian 64bit, with 5.x kernel both monitors work
as expected.
I'm working on a prebuilt image to use as an Ethercat
Master, Picat4, from simplerobot.org, which has this kernel, and what
happens is that at booting both monitors start, I see booting info on
second monitor for 2-3 seconds, after that image get frozen on the
second monitor and the first starts as expected with the system running
fine.

this is an extract of dmesg:

pi@picat:~ $ dmesg | grep fb
[
0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 cma=64M
bcm2708_fb.fbwidth=1920 bcm2708_fb.fbheight=1080 bcm2708_fb.fbswap=1
smsc95xx.macaddr=DC:A6:32:F5:24:DE vc_mem.mem_base=0x3ec00000
vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1
root=PARTUUID=84c8ffd9-02 rootfstype=ext4 elevator=deadline
fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
isolcpus=2,3 xenomai.supported_cpus=0xC
[ 0.172711] pci_bus 0000:00:
root bus resource [mem 0x600000000-0x603ffffff] (bus address
[0xf8000000-0xfbffffff])
[ 0.176577] bcm2708_fb soc:fb: FB found 2
display(s)
[ 0.209547] bcm2708_fb soc:fb: Registered framebuffer for
display 0, size 1920x1080
[ 0.233066] bcm2708_fb soc:fb: Registered
framebuffer for display 1, size 1920x1080

from those commands I confirm
monitors are recognized:

pi@picat:~ $ tvservice -l
2 attached
device(s), display ID's are : 
Display Number 2, type HDMI 0
Display
Number 7, type HDMI 1
pi@picat:~ $ tvservice -v 2 -s
state 0xa [HDMI CEA
(16) RGB lim 16:9], 1920x1080 @ 60.00Hz, progressive
pi@picat:~ $
tvservice -v 7 -s
state 0xa [HDMI CEA (16) RGB lim 16:9], 1920x1080 @
60.00Hz, progressive

...and 2 framebuffers are created:

pi@picat:~ $
ls /dev/fb*
/dev/fb0 /dev/fb1

BUT xrandr give me this:

pi@picat:~ $
xrandr 
xrandr: Failed to get size of gamma for output default
Screen 0:
minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080
default
connected 1920x1080+0+0 0mm x 0mm
 1920x1080 0.00*

only one
monitor...

I know that's a Raspberry, and I have to expect strange
behave, but it looks promising that at booting both monitors work,
so..

Can you point me in the right direction to look where, when and
why the second monitor stops to work?

Thanks, Davide.
 



Con Tiscali Mobile Smart 70 hai 70 GB in 4G, minuti illimitati e 100 SMS a soli 7,99€ al mese http://tisca.li/Smart70

Re: Raspberry pi 4 second monitor problem on xeno3

[Greg Gallagher]

On Sat, Jun 26, 2021 at 9:06 AM davide via Xenomai <xenomai@xenomai.org>
wrote:

>
>
> Hi, it is the first time I ask for an help on this mailing list.
> My
> setup:
> -Raspberry Pi 4, 4gb ram (forced to 3gb) running debian buster
> 64bit.
>
> pi@picat:~ $ uname -a
> Linux picat 4.19.126-v8-xeno3+ #1 SMP
> PREEMPT Wed Mar 24 12:53:24 +07 2021 aarch64 GNU/Linux
>
> pi@picat:~ $
> hostnamectl
>
> ...cut...
> Operating System: Debian GNU/Linux 10 (buster)
>
> Kernel: Linux 4.19.126-v8-xeno3+
>  Architecture: arm64
>
> - two HDMI
> identical monitor connected . 1920x1080 60Hz 148.6 MHz clock.
>
> My
> propblem:
> on a clean raspbian 64bit, with 5.x kernel both monitors work
> as expected.
> I'm working on a prebuilt image to use as an Ethercat
> Master, Picat4, from simplerobot.org, which has this kernel, and what
> happens is that at booting both monitors start, I see booting info on
> second monitor for 2-3 seconds, after that image get frozen on the
> second monitor and the first starts as expected with the system running
> fine.
>
> this is an extract of dmesg:
>
> pi@picat:~ $ dmesg | grep fb
> [
> 0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 cma=64M
> bcm2708_fb.fbwidth=1920 bcm2708_fb.fbheight=1080 bcm2708_fb.fbswap=1
> smsc95xx.macaddr=DC:A6:32:F5:24:DE vc_mem.mem_base=0x3ec00000
> vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1
> root=PARTUUID=84c8ffd9-02 rootfstype=ext4 elevator=deadline
> fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
> isolcpus=2,3 xenomai.supported_cpus=0xC
> [ 0.172711] pci_bus 0000:00:
> root bus resource [mem 0x600000000-0x603ffffff] (bus address
> [0xf8000000-0xfbffffff])
> [ 0.176577] bcm2708_fb soc:fb: FB found 2
> display(s)
> [ 0.209547] bcm2708_fb soc:fb: Registered framebuffer for
> display 0, size 1920x1080
> [ 0.233066] bcm2708_fb soc:fb: Registered
> framebuffer for display 1, size 1920x1080
>
> from those commands I confirm
> monitors are recognized:
>
> pi@picat:~ $ tvservice -l
> 2 attached
> device(s), display ID's are :
> Display Number 2, type HDMI 0
> Display
> Number 7, type HDMI 1
> pi@picat:~ $ tvservice -v 2 -s
> state 0xa [HDMI CEA
> (16) RGB lim 16:9], 1920x1080 @ 60.00Hz, progressive
> pi@picat:~ $
> tvservice -v 7 -s
> state 0xa [HDMI CEA (16) RGB lim 16:9], 1920x1080 @
> 60.00Hz, progressive
>
> ...and 2 framebuffers are created:
>
> pi@picat:~ $
> ls /dev/fb*
> /dev/fb0 /dev/fb1
>
> BUT xrandr give me this:
>
> pi@picat:~ $
> xrandr
> xrandr: Failed to get size of gamma for output default
> Screen 0:
> minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080
> default
> connected 1920x1080+0+0 0mm x 0mm
>  1920x1080 0.00*
>
> only one
> monitor...
>
> I know that's a Raspberry, and I have to expect strange
> behave, but it looks promising that at booting both monitors work,
> so..
>
> Can you point me in the right direction to look where, when and
> why the second monitor stops to work?
>
> Thanks, Davide.
>
>
>
>
> Con Tiscali Mobile Smart 70 hai 70 GB in 4G, minuti illimitati e 100 SMS a
> soli 7,99€ al mese http://tisca.li/Smart70
>

Hi,
  Are you using ipipe or dovetail? This may not be a xenomai issue, how do
you build your kernel?

Thanks

Greg

>
>

Re: Raspberry pi 4 second monitor problem on xeno3

[77dab]

  
Hi, Found out it's using iPipe here. 
Is there something I can look
for to understand why it doesn't work? 

Il 26.06.2021 15:09 Greg
Gallagher ha scritto: 

> On Sat, Jun 26, 2021 at 9:06 AM davide via
Xenomai wrote: 
> 
>> Hi, it is the first time I ask for an help on this
mailing list.
>> My
>> setup:
>> -Raspberry Pi 4, 4gb ram (forced to
3gb) running debian buster
>> 64bit.
>> 
>> pi@picat:~ $ uname -a
>>
Linux picat 4.19.126-v8-xeno3+ #1 SMP
>> PREEMPT Wed Mar 24 12:53:24 +07
2021 aarch64 GNU/Linux 
>> 
>> pi@picat:~ $
>> hostnamectl
>> 
>>
...cut...
>> Operating System: Debian GNU/Linux 10 (buster)
>> 
>>
Kernel: Linux 4.19.126-v8-xeno3+
>> Architecture: arm64
>> 
>> - two
HDMI
>> identical monitor connected . 1920x1080 60Hz 148.6 MHz clock.
>>

>> My
>> propblem:
>> on a clean raspbian 64bit, with 5.x kernel both
monitors work
>> as expected.
>> I'm working on a prebuilt image to use
as an Ethercat
>> Master, Picat4, from simplerobot.org [1], which has
this kernel, and what
>> happens is that at booting both monitors start,
I see booting info on
>> second monitor for 2-3 seconds, after that
image get frozen on the
>> second monitor and the first starts as
expected with the system running
>> fine.
>> 
>> this is an extract of
dmesg:
>> 
>> pi@picat:~ $ dmesg | grep fb
>> [
>> 0.000000] Kernel
command line: coherent_pool=1M 8250.nr_uarts=0 cma=64M
>>
bcm2708_fb.fbwidth=1920 bcm2708_fb.fbheight=1080 bcm2708_fb.fbswap=1
>>
smsc95xx.macaddr=DC:A6:32:F5:24:DE vc_mem.mem_base=0x3ec00000
>>
vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1
>>
root=PARTUUID=84c8ffd9-02 rootfstype=ext4 elevator=deadline
>>
fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
>>
isolcpus=2,3 xenomai.supported_cpus=0xC
>> [ 0.172711] pci_bus
0000:00:
>> root bus resource [mem 0x600000000-0x603ffffff] (bus
address
>> [0xf8000000-0xfbffffff])
>> [ 0.176577] bcm2708_fb soc:fb: FB
found 2
>> display(s)
>> [ 0.209547] bcm2708_fb soc:fb: Registered
framebuffer for
>> display 0, size 1920x1080
>> [ 0.233066] bcm2708_fb
soc:fb: Registered
>> framebuffer for display 1, size 1920x1080
>> 
>>
from those commands I confirm
>> monitors are recognized:
>> 
>>
pi@picat:~ $ tvservice -l
>> 2 attached
>> device(s), display ID's are :

>> Display Number 2, type HDMI 0
>> Display
>> Number 7, type HDMI 1
>>
pi@picat:~ $ tvservice -v 2 -s
>> state 0xa [HDMI CEA
>> (16) RGB lim
16:9], 1920x1080 @ 60.00Hz, progressive
>> pi@picat:~ $
>> tvservice -v
7 -s
>> state 0xa [HDMI CEA (16) RGB lim 16:9], 1920x1080 @
>> 60.00Hz,
progressive
>> 
>> ...and 2 framebuffers are created:
>> 
>> pi@picat:~
$
>> ls /dev/fb*
>> /dev/fb0 /dev/fb1
>> 
>> BUT xrandr give me this:
>>

>> pi@picat:~ $
>> xrandr 
>> xrandr: Failed to get size of gamma for
output default
>> Screen 0:
>> minimum 1920 x 1080, current 1920 x 1080,
maximum 1920 x 1080
>> default
>> connected 1920x1080+0+0 0mm x 0mm
>>
1920x1080 0.00*
>> 
>> only one
>> monitor...
>> 
>> I know that's a
Raspberry, and I have to expect strange
>> behave, but it looks
promising that at booting both monitors work,
>> so..
>> 
>> Can you
point me in the right direction to look where, when and
>> why the
second monitor stops to work?
>> 
>> Thanks, Davide.
>> 
>> Con Tiscali
Mobile Smart 70 hai 70 GB in 4G, minuti illimitati e 100 SMS a soli
7,99EUR al mese http://tisca.li/Smart70 [2]
> 
> Hi, 
> Are you using
ipipe or dovetail? This may not be a xenomai issue, how do you build
your kernel? 
> Thanks 
> Greg
  


Con Tiscali Mobile Smart 70 hai 70 GB in 4G, minuti illimitati e 100 SMS a soli 7,99€ al mese http://tisca.li/Smart70

Re: Raspberry pi 4 second monitor problem on xeno3

[Greg Gallagher]

On Mon, Jun 28, 2021 at 4:30 AM davide via Xenomai <xenomai@xenomai.org>
wrote:

>
> Hi, Found out it's using iPipe here.
> Is there something I can look
> for to understand why it doesn't work?
>
> Il 26.06.2021 15:09 Greg
> Gallagher ha scritto:
>
> > On Sat, Jun 26, 2021 at 9:06 AM davide via
> Xenomai wrote:
> >
> >> Hi, it is the first time I ask for an help on this
> mailing list.
> >> My
> >> setup:
> >> -Raspberry Pi 4, 4gb ram (forced to
> 3gb) running debian buster
> >> 64bit.
> >>
> >> pi@picat:~ $ uname -a
> >>
> Linux picat 4.19.126-v8-xeno3+ #1 SMP
> >> PREEMPT Wed Mar 24 12:53:24 +07
> 2021 aarch64 GNU/Linux
> >>
> >> pi@picat:~ $
> >> hostnamectl
> >>
> >>
> ...cut...
> >> Operating System: Debian GNU/Linux 10 (buster)
> >>
> >>
> Kernel: Linux 4.19.126-v8-xeno3+
> >> Architecture: arm64
> >>
> >> - two
> HDMI
> >> identical monitor connected . 1920x1080 60Hz 148.6 MHz clock.
> >>
>
> >> My
> >> propblem:
> >> on a clean raspbian 64bit, with 5.x kernel both
> monitors work
> >> as expected.
> >> I'm working on a prebuilt image to use
> as an Ethercat
> >> Master, Picat4, from simplerobot.org [1], which has
> this kernel, and what
> >> happens is that at booting both monitors start,
> I see booting info on
> >> second monitor for 2-3 seconds, after that
> image get frozen on the
> >> second monitor and the first starts as
> expected with the system running
> >> fine.
> >>
> >> this is an extract of
> dmesg:
> >>
> >> pi@picat:~ $ dmesg | grep fb
> >> [
> >> 0.000000] Kernel
> command line: coherent_pool=1M 8250.nr_uarts=0 cma=64M
> >>
> bcm2708_fb.fbwidth=1920 bcm2708_fb.fbheight=1080 bcm2708_fb.fbswap=1
> >>
> smsc95xx.macaddr=DC:A6:32:F5:24:DE vc_mem.mem_base=0x3ec00000
> >>
> vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1
> >>
> root=PARTUUID=84c8ffd9-02 rootfstype=ext4 elevator=deadline
> >>
> fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
> >>
> isolcpus=2,3 xenomai.supported_cpus=0xC
> >> [ 0.172711] pci_bus
> 0000:00:
> >> root bus resource [mem 0x600000000-0x603ffffff] (bus
> address
> >> [0xf8000000-0xfbffffff])
> >> [ 0.176577] bcm2708_fb soc:fb: FB
> found 2
> >> display(s)
> >> [ 0.209547] bcm2708_fb soc:fb: Registered
> framebuffer for
> >> display 0, size 1920x1080
> >> [ 0.233066] bcm2708_fb
> soc:fb: Registered
> >> framebuffer for display 1, size 1920x1080
> >>
> >>
> from those commands I confirm
> >> monitors are recognized:
> >>
> >>
> pi@picat:~ $ tvservice -l
> >> 2 attached
> >> device(s), display ID's are :
>
> >> Display Number 2, type HDMI 0
> >> Display
> >> Number 7, type HDMI 1
> >>
> pi@picat:~ $ tvservice -v 2 -s
> >> state 0xa [HDMI CEA
> >> (16) RGB lim
> 16:9], 1920x1080 @ 60.00Hz, progressive
> >> pi@picat:~ $
> >> tvservice -v
> 7 -s
> >> state 0xa [HDMI CEA (16) RGB lim 16:9], 1920x1080 @
> >> 60.00Hz,
> progressive
> >>
> >> ...and 2 framebuffers are created:
> >>
> >> pi@picat:~
> $
> >> ls /dev/fb*
> >> /dev/fb0 /dev/fb1
> >>
> >> BUT xrandr give me this:
> >>
>
> >> pi@picat:~ $
> >> xrandr
> >> xrandr: Failed to get size of gamma for
> output default
> >> Screen 0:
> >> minimum 1920 x 1080, current 1920 x 1080,
> maximum 1920 x 1080
> >> default
> >> connected 1920x1080+0+0 0mm x 0mm
> >>
> 1920x1080 0.00*
> >>
> >> only one
> >> monitor...
> >>
> >> I know that's a
> Raspberry, and I have to expect strange
> >> behave, but it looks
> promising that at booting both monitors work,
> >> so..
> >>
> >> Can you
> point me in the right direction to look where, when and
> >> why the
> second monitor stops to work?
> >>
> >> Thanks, Davide.
> >>
> >> Con Tiscali
> Mobile Smart 70 hai 70 GB in 4G, minuti illimitati e 100 SMS a soli
> 7,99EUR al mese http://tisca.li/Smart70 [2]
> >
> > Hi,
> > Are you using
> ipipe or dovetail? This may not be a xenomai issue, how do you build
> your kernel?
> > Thanks
> > Greg
>
>
>
> Con Tiscali Mobile Smart 70 hai 70 GB in 4G, minuti illimitati e 100 SMS a
> soli 7,99€ al mese http://tisca.li/Smart70


It’s possible the drivers aren’t working in the kernel without ipipe,
you’ll want to confirm that first.  If you didn’t compile the kernel
yourself you’ll want to find the sources so you can debug..

Greg

> <http://tisca.li/Smart70>
>
>

Re: Raspberry pi 4 second monitor problem on xeno3

[77dab]

  
kernel comes from here: 
https://github.com/thanhtam-h/rpi4-xeno3

One thing: even if desktop isn't extended to the second screen, and
xrandr sees only a 'default' screen 
if I give: 

cat /dev/random >
/dev/fb1  
the second screen gets filled.. 
it sounds odd to me, because
that means framebuffer is open and working. 
So, what's going on here?

Il 28.06.2021 13:33 Greg Gallagher ha scritto: 

> It's possible the
drivers aren't working in the kernel without ipipe, you'll want to
confirm that first. If you didn't compile the kernel yourself you'll
want to find the sources so you can debug.. 
> Greg
  


Con Tiscali Mobile Smart 70 hai 70 GB in 4G, minuti illimitati e 100 SMS a soli 7,99€ al mese http://tisca.li/Smart70

Re: Raspberry pi 4 second monitor problem on xeno3

[Greg Gallagher]

On Mon, Jun 28, 2021 at 8:12 AM davide via Xenomai <xenomai@xenomai.org>
wrote:

>
> kernel comes from here:
> https://github.com/thanhtam-h/rpi4-xeno3
>
> One thing: even if desktop isn't extended to the second screen, and
> xrandr sees only a 'default' screen
> if I give:
>
> cat /dev/random >
> /dev/fb1
> the second screen gets filled..
> it sounds odd to me, because
> that means framebuffer is open and working.
> So, what's going on here?
>
> Il 28.06.2021 13:33 Greg Gallagher ha scritto:
>
> > It's possible the
> drivers aren't working in the kernel without ipipe, you'll want to
> confirm that first. If you didn't compile the kernel yourself you'll
> want to find the sources so you can debug..
> > Greg
>
>
>
> Con Tiscali Mobile Smart 70 hai 70 GB in 4G, minuti illimitati e 100 SMS a
> soli 7,99€ al mese http://tisca.li/Smart70
>

This doesn’t sound like a xenomai or ipipe issue, you’ll have to do some
further debug and see if this issue is being caused by the ipipe or
xenomai.  Right now what you have described doesn’t sound like an issue
with the real-time core.

Greg

>
>

Re: Raspberry pi 4 second monitor problem on xeno3

[77dab]

  
(sorry if I'm down-quoting, but I cannot write below here..) 
I
agree with you, it's just I don't know how to debug this..

I'm looking
at /var/log/Xorg.0.log differences between the non-working situation Vs
a standard debian64bit working one:
first difference is -> working:

[
5.854] (II) xfree86: Adding drm device (/dev/dri/card1)
[ 5.862] (II)
xfree86: Adding drm device (/dev/dri/card0)

while those lines aren't
present in the NOT-working, and there is:

[ 5.307] (EE) open
/dev/dri/card0: No such file or directory

does that tells anything?

Il
28.06.2021 14:17 Greg Gallagher ha scritto: 

> On Mon, Jun 28, 2021 at
8:12 AM davide via Xenomai wrote: 
> 
>> kernel comes from here: 
>>
https://github.com/thanhtam-h/rpi4-xeno3 [1]
>> 
>> One thing: even if
desktop isn't extended to the second screen, and
>> xrandr sees only a
'default' screen 
>> if I give: 
>> 
>> cat /dev/random >
>> /dev/fb1

>> the second screen gets filled.. 
>> it sounds odd to me, because
>>
that means framebuffer is open and working. 
>> So, what's going on
here?
>> 
>> Il 28.06.2021 13:33 Greg Gallagher ha scritto: 
>> 
>> >
It's possible the
>> drivers aren't working in the kernel without ipipe,
you'll want to
>> confirm that first. If you didn't compile the kernel
yourself you'll
>> want to find the sources so you can debug.. 
>> >
Greg
>> 
>> Con Tiscali Mobile Smart 70 hai 70 GB in 4G, minuti
illimitati e 100 SMS a soli 7,99EUR al mese http://tisca.li/Smart70
[2]
> 
> This doesn't sound like a xenomai or ipipe issue, you'll have
to do some further debug and see if this issue is being caused by the
ipipe or xenomai. Right now what you have described doesn't sound like
an issue with the real-time core. 
> Greg
  


Con Tiscali Mobile Smart 70 hai 70 GB in 4G, minuti illimitati e 100 SMS a soli 7,99€ al mese http://tisca.li/Smart70

Re: Raspberry pi 4 second monitor problem on xeno3

[Greg Gallagher]

On Mon, Jun 28, 2021 at 9:02 AM davide via Xenomai <xenomai@xenomai.org>
wrote:

>
> (sorry if I'm down-quoting, but I cannot write below here..)
> I
> agree with you, it's just I don't know how to debug this..
>
> I'm looking
> at /var/log/Xorg.0.log differences between the non-working situation Vs
> a standard debian64bit working one:
> first difference is -> working:
>
> [
> 5.854] (II) xfree86: Adding drm device (/dev/dri/card1)
> [ 5.862] (II)
> xfree86: Adding drm device (/dev/dri/card0)
>
> while those lines aren't
> present in the NOT-working, and there is:
>
> [ 5.307] (EE) open
> /dev/dri/card0: No such file or directory
>
> does that tells anything?
>
> Il
> 28.06.2021 14:17 Greg Gallagher ha scritto:
>
> > On Mon, Jun 28, 2021 at
> 8:12 AM davide via Xenomai wrote:
> >
> >> kernel comes from here:
> >>
> https://github.com/thanhtam-h/rpi4-xeno3 [1]
> >>
> >> One thing: even if
> desktop isn't extended to the second screen, and
> >> xrandr sees only a
> 'default' screen
> >> if I give:
> >>
> >> cat /dev/random >
> >> /dev/fb1
>
> >> the second screen gets filled..
> >> it sounds odd to me, because
> >>
> that means framebuffer is open and working.
> >> So, what's going on
> here?
> >>
> >> Il 28.06.2021 13:33 Greg Gallagher ha scritto:
> >>
> >> >
> It's possible the
> >> drivers aren't working in the kernel without ipipe,
> you'll want to
> >> confirm that first. If you didn't compile the kernel
> yourself you'll
> >> want to find the sources so you can debug..
> >> >
> Greg
> >>
> >> Con Tiscali Mobile Smart 70 hai 70 GB in 4G, minuti
> illimitati e 100 SMS a soli 7,99EUR al mese http://tisca.li/Smart70
> [2]
> >
> > This doesn't sound like a xenomai or ipipe issue, you'll have
> to do some further debug and see if this issue is being caused by the
> ipipe or xenomai. Right now what you have described doesn't sound like
> an issue with the real-time core.
> > Greg
>
>
>
> Con Tiscali Mobile Smart 70 hai 70 GB in 4G, minuti illimitati e 100 SMS a
> soli 7,99€ al mese http://tisca.li/Smart70
>
> Ok, you may be missing a driver or certain modules aren’t loaded yet. You
could see if you can log an issue on the GitHub project you referenced. But
this doesn’t look to be a xenomai or ipipe issue so this list probably
won’t be able to help too much.

Greg

Re: Raspberry pi 4 second monitor problem on xeno3

[77dab]

  Ok, thank you for your time.

Il 28.06.2021 15:49 Greg Gallagher ha
scritto: 

> On Mon, Jun 28, 2021 at 9:02 AM davide via Xenomai wrote:

> 
>> (sorry if I'm down-quoting, but I cannot write below here..) 
>>
I
>> agree with you, it's just I don't know how to debug this..
>> 
>>
I'm looking
>> at /var/log/Xorg.0.log differences between the
non-working situation Vs
>> a standard debian64bit working one:
>> first
difference is -> working:
>> 
>> [
>> 5.854] (II) xfree86: Adding drm
device (/dev/dri/card1)
>> [ 5.862] (II)
>> xfree86: Adding drm device
(/dev/dri/card0)
>> 
>> while those lines aren't
>> present in the
NOT-working, and there is:
>> 
>> [ 5.307] (EE) open
>> /dev/dri/card0:
No such file or directory
>> 
>> does that tells anything?
>> 
>> Il
>>
28.06.2021 14:17 Greg Gallagher ha scritto: 
>> 
>> > On Mon, Jun 28,
2021 at
>> 8:12 AM davide via Xenomai wrote: 
>> > 
>> >> kernel comes
from here: 
>> >>
>> https://github.com/thanhtam-h/rpi4-xeno3 [1] [1]
>>
>> 
>> >> One thing: even if
>> desktop isn't extended to the second
screen, and
>> >> xrandr sees only a
>> 'default' screen 
>> >> if I
give: 
>> >> 
>> >> cat /dev/random >
>> >> /dev/fb1
>> 
>> >> the
second screen gets filled.. 
>> >> it sounds odd to me, because
>> >>
>>
that means framebuffer is open and working. 
>> >> So, what's going
on
>> here?
>> >> 
>> >> Il 28.06.2021 13:33 Greg Gallagher ha scritto:

>> >> 
>> >> >
>> It's possible the
>> >> drivers aren't working in the
kernel without ipipe,
>> you'll want to
>> >> confirm that first. If you
didn't compile the kernel
>> yourself you'll
>> >> want to find the
sources so you can debug.. 
>> >> >
>> Greg
>> >> 
>> >> Con Tiscali
Mobile Smart 70 hai 70 GB in 4G, minuti
>> illimitati e 100 SMS a soli
7,99EUR al mese http://tisca.li/Smart70 [2]
>> [2]
>> > 
>> > This
doesn't sound like a xenomai or ipipe issue, you'll have
>> to do some
further debug and see if this issue is being caused by the
>> ipipe or
xenomai. Right now what you have described doesn't sound like
>> an
issue with the real-time core. 
>> > Greg
>> 
>> Con Tiscali Mobile
Smart 70 hai 70 GB in 4G, minuti illimitati e 100 SMS a soli 7,99EUR al
mese http://tisca.li/Smart70 [3]
> 
> Ok, you may be missing a driver or
certain modules aren't loaded yet. You could see if you can log an issue
on the GitHub project you referenced. But this doesn't look to be a
xenomai or ipipe issue so this list probably won't be able to help too
much. 
> Greg
  


Con Tiscali Mobile Smart 70 hai 70 GB in 4G, minuti illimitati e 100 SMS a soli 7,99€ al mese http://tisca.li/Smart70