From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: <22d045f858ff5e9b4daddb410540be94@tiscali.it> In-Reply-To: From: Greg Gallagher Date: Mon, 28 Jun 2021 07:33:00 -0400 Message-ID: Subject: Re: Raspberry pi 4 second monitor problem on xeno3 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: 77dab@tiscali.it Cc: xenomai@xenomai.org On Mon, Jun 28, 2021 at 4:30 AM davide via Xenomai 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=3D1M 8250.nr_uarts=3D0 cma=3D64M > >> > bcm2708_fb.fbwidth=3D1920 bcm2708_fb.fbheight=3D1080 bcm2708_fb.fbswap=3D= 1 > >> > smsc95xx.macaddr=3DDC:A6:32:F5:24:DE vc_mem.mem_base=3D0x3ec00000 > >> > vc_mem.mem_size=3D0x40000000 console=3DttyS0,115200 console=3Dtty1 > >> > root=3DPARTUUID=3D84c8ffd9-02 rootfstype=3Dext4 elevator=3Ddeadline > >> > fsck.repair=3Dyes rootwait quiet splash plymouth.ignore-serial-consoles > >> > isolcpus=3D2,3 xenomai.supported_cpus=3D0xC > >> [ 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=E2=82=AC al mese http://tisca.li/Smart70 It=E2=80=99s possible the drivers aren=E2=80=99t working in the kernel with= out ipipe, you=E2=80=99ll want to confirm that first. If you didn=E2=80=99t compile t= he kernel yourself you=E2=80=99ll want to find the sources so you can debug.. Greg > > >