Raspberry Pi and its 7" display

[Kevin Cummings]

Hi Folks,
	Longtime Fedora user here.  Last winter, I got a Raspberry Pi, and
installed F28 on it.  Using the HDMI output, it works well.  Recently, I
picked up the Raspberry Pi 7" display (and case).  After hooking up the
display to the Pi via the ribbon cable, I booted it up.

The 7" display works well as the initial console, and I see all the
usual messages go flying by.  At some point (when it decides to switch
to graphics mode) the display goes blank.  Nothing on it.  I cannot
switch even to a virtual console.  The new case blocks using the HDMI
port, so I had to remove the Pi from the case (while leaving the ribbon
cable attached to the display).  After plugging a monitor into the HDMI
port, what I discovered was that the Pi boots using the display as
console, then switches to the HDMI port for the X11 driver.  (not useful)

How can I get the X11 display to come up on the 7" display in graphics
mode.  What do I need?  A new xorg-x11-drv driver?  A newer kernel?

I'd like to turn this into a MythTV server (with a USB capture) and use
the display as a system console with the ability to watch videos on it.
(Yeah, I'm aware that its only a 800x400 screen.)  Failing that, I'd
like to use it in a "tablet" mode and get used to the touch screen
interface.

-- 
Kevin J. Cummings
cummings(a)kjchome.homeip.net
cummings(a)kjc386.framingham.ma.us
kjchome(a)icloud.com
Registered Linux User #1232 (http://www.linuxcounter.net/)

[Ted Davis]

Hi Kevin,

Do you or anyone know if gpm works on these rpi touchscreens in console-tty?

And/Or question 2:

F29 aarch are .xz, need I have fedora installed say x86-64, to have dnf (?)
to write the aarch image for rpi 3 B+?

Or, is there a writable  .iso available instead of the f29.aarch.xz?

Ty

Ted

On Saturday, December 8, 2018, Kevin Cummings <cummings(a)kjchome.homeip.net&gt;
wrote:

>  Hi Folks,
>          Longtime Fedora user here.  Last winter, I got a Raspberry Pi, and
>  installed F28 on it.  Using the HDMI output, it works well.  Recently, I
>  picked up the Raspberry Pi 7" display (and case).  After hooking up the
>  display to the Pi via the ribbon cable, I booted it up.
>
>  The 7" display works well as the initial console, and I see all the
>  usual messages go flying by.  At some point (when it decides to switch
>  to graphics mode) the display goes blank.  Nothing on it.  I cannot
>  switch even to a virtual console.  The new case blocks using the HDMI
>  port, so I had to remove the Pi from the case (while leaving the ribbon
>  cable attached to the display).  After plugging a monitor into the HDMI
>  port, what I discovered was that the Pi boots using the display as
>  console, then switches to the HDMI port for the X11 driver.  (not useful)
>
>  How can I get the X11 display to come up on the 7" display in graphics
>  mode.  What do I need?  A new xorg-x11-drv driver?  A newer kernel?
>
>  I'd like to turn this into a MythTV server (with a USB capture) and use
>  the display as a system console with the ability to watch videos on it.
>  (Yeah, I'm aware that its only a 800x400 screen.)  Failing that, I'd
>  like to use it in a "tablet" mode and get used to the touch screen
>  interface.
>
>  --
>  Kevin J. Cummings
>  cummings(a)kjchome.homeip.net
>  cummings(a)kjc386.framingham.ma.us
>  kjchome(a)icloud.com
>  Registered Linux User #1232 (http://www.linuxcounter.net/)
>  _______________________________________________
>  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
>

[Peter Robinson]

On Sun, Dec 9, 2018 at 1:52 AM Ted Davis <12e3pi(a)gmail.com&gt; wrote:
>  Hi Kevin,
>
>  Do you or anyone know if gpm works on these rpi touchscreens in console-tty? 
Not currently.

>  And/Or question 2:
>
>  F29 aarch are .xz, need I have fedora installed say x86-64, to have dnf (?) to write the
> aarch image for rpi 3 B+?
>
>  Or, is there a writable  .iso available instead of the f29.aarch.xz? 
Please read the docs and start a new thread if they don't answer your questions.

> Ty
>
> Ted
>
> On Saturday, December 8, 2018, Kevin Cummings <cummings(a)kjchome.homeip.net&gt;
wrote:
>>
>> Hi Folks,
>>         Longtime Fedora user here.  Last winter, I got a Raspberry Pi, and
>> installed F28 on it.  Using the HDMI output, it works well.  Recently, I
>> picked up the Raspberry Pi 7" display (and case).  After hooking up the
>> display to the Pi via the ribbon cable, I booted it up.
>>
>> The 7" display works well as the initial console, and I see all the
>> usual messages go flying by.  At some point (when it decides to switch
>> to graphics mode) the display goes blank.  Nothing on it.  I cannot
>> switch even to a virtual console.  The new case blocks using the HDMI
>> port, so I had to remove the Pi from the case (while leaving the ribbon
>> cable attached to the display).  After plugging a monitor into the HDMI
>> port, what I discovered was that the Pi boots using the display as
>> console, then switches to the HDMI port for the X11 driver.  (not useful)
>>
>> How can I get the X11 display to come up on the 7" display in graphics
>> mode.  What do I need?  A new xorg-x11-drv driver?  A newer kernel?
>>
>> I'd like to turn this into a MythTV server (with a USB capture) and use
>> the display as a system console with the ability to watch videos on it.
>> (Yeah, I'm aware that its only a 800x400 screen.)  Failing that, I'd
>> like to use it in a "tablet" mode and get used to the touch screen
>> interface.
>>
>> --
>> Kevin J. Cummings
>> cummings(a)kjchome.homeip.net
>> cummings(a)kjc386.framingham.ma.us
>> kjchome(a)icloud.com
>> Registered Linux User #1232 (http://www.linuxcounter.net/)
>> _______________________________________________
>> 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/[e-mail]
>
> _______________________________________________
> 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/[e-mail]

[Peter Robinson]

>  Hi Folks,
>          Longtime Fedora user here.  Last winter, I got a Raspberry Pi, and
>  installed F28 on it.  Using the HDMI output, it works well.  Recently, I 
Any reason for F-28 instead of F-29?

>  picked up the Raspberry Pi 7" display (and case).  After hooking
> up the
>  display to the Pi via the ribbon cable, I booted it up.
>
>  The 7" display works well as the initial console, and I see all the
>  usual messages go flying by.  At some point (when it decides to switch
>  to graphics mode) the display goes blank.  Nothing on it.  I cannot
>  switch even to a virtual console.  The new case blocks using the HDMI
>  port, so I had to remove the Pi from the case (while leaving the ribbon
>  cable attached to the display).  After plugging a monitor into the HDMI
>  port, what I discovered was that the Pi boots using the display as
>  console, then switches to the HDMI port for the X11 driver.  (not useful) 
If you block the vc4 driver it will continue to work as a pure non
accelerated display, at the moment when the accelerated driver
initialises it can't detect the DSI attached display so it goes blank.
The support status is documented in the Fedora Raspberry Pi FAQ [1]

>  How can I get the X11 display to come up on the 7" display in
> graphics
>  mode.  What do I need?  A new xorg-x11-drv driver?  A newer kernel? 
The Raspberry Pi doesn't have, nor will ever have a xorg driver. The
driver is a 3D mesa accelerated driver, the 2D support is via glamor
(2D over 3D) to mesa.

The upstream open source driver we use doesn't yet fully support the
touch screen display, I don't believe it's far off but upstream is yet
to finish the work to have it supported.

>  I'd like to turn this into a MythTV server (with a USB capture)
> and use
>  the display as a system console with the ability to watch videos on it.
>  (Yeah, I'm aware that its only a 800x400 screen.)  Failing that, I'd
>  like to use it in a "tablet" mode and get used to the touch screen
>  interface. 
Well when it's supported upstream it will be enabled.

[1]
https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi#Is_the_Rasp...

[Kevin Cummings]

On 12/10/18 9:20 PM, Peter Robinson wrote:
> > Hi Folks,
> >         Longtime Fedora user here.  Last winter, I got a Raspberry Pi, and
> > installed F28 on it.  Using the HDMI output, it works well.  Recently, I
>  
>  Any reason for F-28 instead of F-29? 
Lazy?  I think you're lucky I upgraded it from the F27 I originally
installed....

> > picked up the Raspberry Pi 7" display (and case).  After
> hooking up the
> > display to the Pi via the ribbon cable, I booted it up.
> >
> > The 7" display works well as the initial console, and I see all the
> > usual messages go flying by.  At some point (when it decides to switch
> > to graphics mode) the display goes blank.  Nothing on it.  I cannot
> > switch even to a virtual console.  The new case blocks using the HDMI
> > port, so I had to remove the Pi from the case (while leaving the ribbon
> > cable attached to the display).  After plugging a monitor into the HDMI
> > port, what I discovered was that the Pi boots using the display as
> > console, then switches to the HDMI port for the X11 driver.  (not useful)
>  
>  If you block the vc4 driver it will continue to work as a pure non
>  accelerated display, at the moment when the accelerated driver
>  initialises it can't detect the DSI attached display so it goes blank. 
So if I blacklist the vc4 driver, will an X11 session start up on the
display?  If not, can I modify the boot up to bring Linux up in command
line only mode?  Will the virtual consoles work in that mode?

I don't (yet) understand the uboot stuff.  In a PC, I can interrupt grub
and edit the command line to put kernel options on the boot line.  I
don't know how to do that with uboot.

>  The support status is documented in the Fedora Raspberry Pi FAQ [1]
Yes, it talks about supporting the touchscreen display.  But there are
two parts:  The graphics display, and the touch screen.  Is the graphics
screen currently supported?

I can wait for touchscreen support.

> > How can I get the X11 display to come up on the 7" display
> in graphics
> > mode.  What do I need?  A new xorg-x11-drv driver?  A newer kernel?
>  
>  The Raspberry Pi doesn't have, nor will ever have a xorg driver. The
>  driver is a 3D mesa accelerated driver, the 2D support is via glamor
>  (2D over 3D) to mesa. 
Sorry, in all the PCs I've every used, there has been a specific driver
to get X11 to run (reasonably) on every different video card I've had to
run X11 on.  I'm not familiar with using them as only frame-buffer.  So
this is new territory for me.

>  The upstream open source driver we use doesn't yet fully support
> the
>  touch screen display, I don't believe it's far off but upstream is yet
>  to finish the work to have it supported. 
Yes, that's what [1] says.

> > I'd like to turn this into a MythTV server (with a USB
> capture) and use
> > the display as a system console with the ability to watch videos on it.
> > (Yeah, I'm aware that its only a 800x400 screen.)  Failing that, I'd 
I should have said 800x480 screen, and I also see that text mode
actually runs at 720x480?

> > like to use it in a "tablet" mode and get used to the
> touch screen
> > interface.
>  
>  Well when it's supported upstream it will be enabled.
>  
>  [1]
> https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi#Is_the_Rasp...
>  _______________________________________________
>  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/[e-mail]
Thanks for the help so far.

-- 
Kevin J. Cummings
cummings(a)kjchome.homeip.net
cummings(a)kjc386.framingham.ma.us
kjchome(a)icloud.com
Registered Linux User #1232 (http://www.linuxcounter.net/)

[Peter Robinson]

On Tue, Dec 11, 2018 at 3:18 AM Kevin Cummings
<cummings(a)kjchome.homeip.net&gt; wrote:
>  On 12/10/18 9:20 PM, Peter Robinson wrote:
>  >> Hi Folks,
>  >>         Longtime Fedora user here.  Last winter, I got a Raspberry Pi, and
>  >> installed F28 on it.  Using the HDMI output, it works well.  Recently, I
>  >
>  > Any reason for F-28 instead of F-29?
>
>  Lazy?  I think you're lucky I upgraded it from the F27 I originally
>  installed....
>
>  >> picked up the Raspberry Pi 7" display (and case).  After hooking up the
>  >> display to the Pi via the ribbon cable, I booted it up.
>  >>
>  >> The 7" display works well as the initial console, and I see all the
>  >> usual messages go flying by.  At some point (when it decides to switch
>  >> to graphics mode) the display goes blank.  Nothing on it.  I cannot
>  >> switch even to a virtual console.  The new case blocks using the HDMI
>  >> port, so I had to remove the Pi from the case (while leaving the ribbon
>  >> cable attached to the display).  After plugging a monitor into the HDMI
>  >> port, what I discovered was that the Pi boots using the display as
>  >> console, then switches to the HDMI port for the X11 driver.  (not useful)
>  >
>  > If you block the vc4 driver it will continue to work as a pure non
>  > accelerated display, at the moment when the accelerated driver
>  > initialises it can't detect the DSI attached display so it goes blank.
>
>  So if I blacklist the vc4 driver, will an X11 session start up on the
>  display?  If not, can I modify the boot up to bring Linux up in command
>  line only mode?  Will the virtual consoles work in that mode?
>
>  I don't (yet) understand the uboot stuff.  In a PC, I can interrupt grub
>  and edit the command line to put kernel options on the boot line.  I
>  don't know how to do that with uboot. 
U-Boot in basically a firmware so in the context you put it it's not
grub2 or like it, on aarch64 mode on the Raspberry Pi we have grub2,
in F-30 we should this for ARMv7 too, The extlinux boot menu is
rudimentary, it doesn't support editing.

>  > The support status is documented in the Fedora Raspberry Pi FAQ
> [1]
>
>  Yes, it talks about supporting the touchscreen display.  But there are
>  two parts:  The graphics display, and the touch screen.  Is the graphics
>  screen currently supported? 
No

>  I can wait for touchscreen support.
>
>  >> How can I get the X11 display to come up on the 7" display in graphics
>  >> mode.  What do I need?  A new xorg-x11-drv driver?  A newer kernel?
>  >
>  > The Raspberry Pi doesn't have, nor will ever have a xorg driver. The
>  > driver is a 3D mesa accelerated driver, the 2D support is via glamor
>  > (2D over 3D) to mesa.
>
>  Sorry, in all the PCs I've every used, there has been a specific driver
>  to get X11 to run (reasonably) on every different video card I've had to
>  run X11 on.  I'm not familiar with using them as only frame-buffer.  So
>  this is new territory for me. 
X11 drivers are going away, even in the PC case, EG these days for new
intel devices it uses mesa/3D glamor for Xorg too.

> > The upstream open source driver we use doesn't yet fully support the
> > touch screen display, I don't believe it's far off but upstream is yet
> > to finish the work to have it supported.
>
> Yes, that's what [1] says.
>
> >> I'd like to turn this into a MythTV server (with a USB capture) and use
> >> the display as a system console with the ability to watch videos on it.
> >> (Yeah, I'm aware that its only a 800x400 screen.)  Failing that,
I'd
>
> I should have said 800x480 screen, and I also see that text mode
> actually runs at 720x480?
>
> >> like to use it in a "tablet" mode and get used to the touch
screen
> >> interface.
> >
> > Well when it's supported upstream it will be enabled.
> >
> > [1]
https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi#Is_the_Rasp...
> > _______________________________________________
> > 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/[e-mail]
>
> Thanks for the help so far.
>
> --
> Kevin J. Cummings
> cummings(a)kjchome.homeip.net
> cummings(a)kjc386.framingham.ma.us
> kjchome(a)icloud.com
> Registered Linux User #1232 (http://www.linuxcounter.net/)
> _______________________________________________
> 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/[e-mail]

[Kevin J Cummings]

>  On 12/10/18 10:18 PM, Kevin Cummings wrote:
> > On 12/10/18 9:20 PM, Peter Robinson wrote:
> > Any reason for F-28 instead of F-29?
>  
>  Lazy?  I think you're lucky I upgraded it from the F27 I originally
>  installed.... 
OK, I updated to f29 running 4.19.7-300.fc29

The first thing I noticed was that I had no wifi device.  ifcfg only
showed eth0, lo, & vibr0 as network devices.

My second boot of the day recognized my wifi and connected.

The next thing I did was update 28 more packages, including a new kernel
(4.19.8-300.fc29).

Upon rebooting it, no wifi again.  In fact after 6 more reboots, none of
them had wifi.  so I rebooted the 4.19.7-300.f29 kernel I still had,
which had a working wifi the last time I ran it.  No wifi.

Rebooted again back to 4.19.7-200.fc28 kernel, and bang!  Wifi is up and
running.

I could have sworn there was a statement in the Fedora ARM wiki that
says that wifi should work out of the box for my Pi 3B after 4.19.2.

> >> picked up the Raspberry Pi 7" display (and case).  After
> hooking up the
> >> display to the Pi via the ribbon cable, I booted it up.
> >> 
> >> The 7" display works well as the initial console, and I see all the
> >> usual messages go flying by.  At some point (when it decides to switch
> >> to graphics mode) the display goes blank.  Nothing on it.  I cannot
> >> switch even to a virtual console.  The new case blocks using the HDMI
> >> port, so I had to remove the Pi from the case (while leaving the ribbon
> >> cable attached to the display).  After plugging a monitor into the HDMI
> >> port, what I discovered was that the Pi boots using the display as
> >> console, then switches to the HDMI port for the X11 driver.  (not useful)
> > 
> > If you block the vc4 driver it will continue to work as a pure non
> > accelerated display, at the moment when the accelerated driver
> > initialises it can't detect the DSI attached display so it goes blank. 
OK, so I added the vc4 module with a "blacklist vc4" in my modprobe stuff.

>  So if I blacklist the vc4 driver, will an X11 session start up on
> the
>  display?  If not, can I modify the boot up to bring Linux up in command
>  line only mode?  Will the virtual consoles work in that mode? 
Yes, the HDMI stuff is now disabled and a non-accelerated X11 server
starts up.  Yeah, its a little small @ 800x480.  BUT IT WORKS!

>  I don't (yet) understand the uboot stuff.  In a PC, I can
> interrupt grub
>  and edit the command line to put kernel options on the boot line.  I
>  don't know how to do that with uboot. 
I found the /boot/extlinux/extlinux.conf file, and made by hand
modifications there to get where I am.

Happy that I don't NEED an HDMI screen anymore, and X11 runs on the
display.  YEA!

Peter, thanks for the pointers!

[Peter Robinson]

>  > On 12/10/18 10:18 PM, Kevin Cummings wrote:
>  >> On 12/10/18 9:20 PM, Peter Robinson wrote:
>  >> Any reason for F-28 instead of F-29?
>  >
>  > Lazy?  I think you're lucky I upgraded it from the F27 I originally
>  > installed....
>
>  OK, I updated to f29 running 4.19.7-300.fc29
>
>  The first thing I noticed was that I had no wifi device.  ifcfg only
>  showed eth0, lo, & vibr0 as network devices.
>
>  My second boot of the day recognized my wifi and connected.
>
>  The next thing I did was update 28 more packages, including a new kernel
>  (4.19.8-300.fc29).
>
>  Upon rebooting it, no wifi again.  In fact after 6 more reboots, none of
>  them had wifi.  so I rebooted the 4.19.7-300.f29 kernel I still had,
>  which had a working wifi the last time I ran it.  No wifi.
>
>  Rebooted again back to 4.19.7-200.fc28 kernel, and bang!  Wifi is up and
>  running.
>
>  I could have sworn there was a statement in the Fedora ARM wiki that
>  says that wifi should work out of the box for my Pi 3B after 4.19.2. 
That fixed an issue for aarch64, there's two distinct and different issues.

The issue you're seeing is being followed in the following bug, and as
you've noticed with it coming and going depending on boot it's very
intermittent and hence proving quite elusive to track down.
https://bugzilla.redhat.com/show_bug.cgi?id=1652093

> >>> picked up the Raspberry Pi 7" display (and case).  After hooking up
the
> >>> display to the Pi via the ribbon cable, I booted it up.
> >>>
> >>> The 7" display works well as the initial console, and I see all
the
> >>> usual messages go flying by.  At some point (when it decides to switch
> >>> to graphics mode) the display goes blank.  Nothing on it.  I cannot
> >>> switch even to a virtual console.  The new case blocks using the HDMI
> >>> port, so I had to remove the Pi from the case (while leaving the ribbon
> >>> cable attached to the display).  After plugging a monitor into the HDMI
> >>> port, what I discovered was that the Pi boots using the display as
> >>> console, then switches to the HDMI port for the X11 driver.  (not
useful)
> >>
> >> If you block the vc4 driver it will continue to work as a pure non
> >> accelerated display, at the moment when the accelerated driver
> >> initialises it can't detect the DSI attached display so it goes blank.
>
> OK, so I added the vc4 module with a "blacklist vc4" in my modprobe stuff.
>
> > So if I blacklist the vc4 driver, will an X11 session start up on the
> > display?  If not, can I modify the boot up to bring Linux up in command
> > line only mode?  Will the virtual consoles work in that mode?
>
> Yes, the HDMI stuff is now disabled and a non-accelerated X11 server
> starts up.  Yeah, its a little small @ 800x480.  BUT IT WORKS!
>
> > I don't (yet) understand the uboot stuff.  In a PC, I can interrupt grub
> > and edit the command line to put kernel options on the boot line.  I
> > don't know how to do that with uboot.
>
> I found the /boot/extlinux/extlinux.conf file, and made by hand
> modifications there to get where I am.
>
> Happy that I don't NEED an HDMI screen anymore, and X11 runs on the
> display.  YEA!
>
> Peter, thanks for the pointers!
> _______________________________________________
> 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/[e-mail]

[Torbjorn Jansson]

On 2018-12-11 03:20, Peter Robinson wrote:
> > I'd like to turn this into a MythTV server (with a USB
> capture) and use
> > the display as a system console with the ability to watch videos on it.
> > (Yeah, I'm aware that its only a 800x400 screen.)  Failing that, I'd
> > like to use it in a "tablet" mode and get used to the touch screen
> > interface.
>  
>  Well when it's supported upstream it will be enabled.
>  
>  [1]
> https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi#Is_the_Rasp...

A bit off-topic but i just checked the url above and noticed something:
Under section "Power Supplies" we have this text:
"The Raspberry Pi 3 Series needs a 2.5W PSU"

Surely this must be a typo, 2.5W would mean 5v at 500mA and that's unlikely to 
be enough for a rpi3, even older official power supplies was 2amp and that is 10W

So it must be Amps and not Watts.

[Peter Robinson]

On Wed, Dec 12, 2018 at 10:18 AM Torbjorn Jansson
<torbjorn.jansson(a)mbox200.swipnet.se&gt; wrote:
>  On 2018-12-11 03:20, Peter Robinson wrote:
>  >> I'd like to turn this into a MythTV server (with a USB capture) and use
>  >> the display as a system console with the ability to watch videos on it.
>  >> (Yeah, I'm aware that its only a 800x400 screen.)  Failing that, I'd
>  >> like to use it in a "tablet" mode and get used to the touch screen
>  >> interface.
>  >
>  > Well when it's supported upstream it will be enabled.
>  >
>  > [1]
> https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi#Is_the_Rasp...
>
>
>  A bit off-topic but i just checked the url above and noticed something:
>  Under section "Power Supplies" we have this text:
>  "The Raspberry Pi 3 Series needs a 2.5W PSU"
>
>  Surely this must be a typo, 2.5W would mean 5v at 500mA and that's unlikely to
>  be enough for a rpi3, even older official power supplies was 2amp and that is 10W
>
>  So it must be Amps and not Watts. 
Correct, the PSU stuff is also covered in prerequisites and it was
correct there and links there to the official Raspberry Pi PSU docs,
I've also updated the other bit.

[Torbjorn Jansson]

On 2018-12-08 23:32, Kevin Cummings wrote:
>  Hi Folks,
>  	Longtime Fedora user here.  Last winter, I got a Raspberry Pi, and
>  installed F28 on it.  Using the HDMI output, it works well.  Recently, I
>  picked up the Raspberry Pi 7" display (and case).  After hooking up the
>  display to the Pi via the ribbon cable, I booted it up.
>  
>  The 7" display works well as the initial console, and I see all the
>  usual messages go flying by.  At some point (when it decides to switch
>  to graphics mode) the display goes blank.  Nothing on it.  I cannot
>  switch even to a virtual console.  The new case blocks using the HDMI
>  port, so I had to remove the Pi from the case (while leaving the ribbon
>  cable attached to the display).  After plugging a monitor into the HDMI
>  port, what I discovered was that the Pi boots using the display as
>  console, then switches to the HDMI port for the X11 driver.  (not useful)
>  
>  How can I get the X11 display to come up on the 7" display in graphics
>  mode.  What do I need?  A new xorg-x11-drv driver?  A newer kernel?
>  
>  I'd like to turn this into a MythTV server (with a USB capture) and use
>  the display as a system console with the ability to watch videos on it.
>  (Yeah, I'm aware that its only a 800x400 screen.)  Failing that, I'd
>  like to use it in a "tablet" mode and get used to the touch screen
>  interface.
>   
i do have a couple of suggestions and ideas that might be of help.
i'm a longtime user of mythtv and what i really like about it is its scheduler.
but there are other areas that could use with improving or using something else 
for.

so one idea is to let tvheadend control your capture devices (for example usb 
based) and then point mythtv backend at tvheadend.
to make this work i created a php script to produce a correctly formatted m3u 
file based on data from tvheadend automatically that makes mythbackend happy.
basically mythbackend streams from tvheadend.

this kind of setup can give you a few additional things compared to a pure 
mythtv setup.
main reason for me was the lack of dvb-t2 plp support in mythtv making most 
channels not show up, plp is supported in tvheadend with a bit of fiddling with 
settings.
also you can then use for example kodi as frontend and let kodi use tvheadend 
as pvr and setup your media library (like recordings) to point to where 
mythbackend stores it.


only thing your then missing is a way to schedule things in mythbackend but web 
interface probably works.

i don't know if it is easier to setup kodi instead of trying to get x11 working 
with your display.


one issue you will likely run into is that tvheadend at least the one in fedora 
28 does not include the needed bits for support for a ca module.
this i had to rebuild myself and compile in.
the issue is the need for libdvben50221 that is part of dvb-apps but not 
included by default in the package.
i haven't followed development of tvheadend closely in this area but i hope it 
gets fixed properly and ca module support gets added to tvheadend in fedora.

oh, i almost forgot.
as you know the filenames created by mythtv is not very user friendly so i made 
a script around mythlink.pl so it can tell the difference between movies and 
series and then produce a folder structure more compatible with kodi and its 
way of figuring out what metadata to load.
another way instead of this would be to point kodi at the upnp exposed library 
by the backend, this is also a quite nice structure with sane titles and so on.

[Peter Robinson]

>  On 2018-12-08 23:32, Kevin Cummings wrote:
>  > Hi Folks,
>  >       Longtime Fedora user here.  Last winter, I got a Raspberry Pi, and
>  > installed F28 on it.  Using the HDMI output, it works well.  Recently, I
>  > picked up the Raspberry Pi 7" display (and case).  After hooking up the
>  > display to the Pi via the ribbon cable, I booted it up.
>  >
>  > The 7" display works well as the initial console, and I see all the
>  > usual messages go flying by.  At some point (when it decides to switch
>  > to graphics mode) the display goes blank.  Nothing on it.  I cannot
>  > switch even to a virtual console.  The new case blocks using the HDMI
>  > port, so I had to remove the Pi from the case (while leaving the ribbon
>  > cable attached to the display).  After plugging a monitor into the HDMI
>  > port, what I discovered was that the Pi boots using the display as
>  > console, then switches to the HDMI port for the X11 driver.  (not useful)
>  >
>  > How can I get the X11 display to come up on the 7" display in graphics
>  > mode.  What do I need?  A new xorg-x11-drv driver?  A newer kernel?
>  >
>  > I'd like to turn this into a MythTV server (with a USB capture) and use
>  > the display as a system console with the ability to watch videos on it.
>  > (Yeah, I'm aware that its only a 800x400 screen.)  Failing that, I'd
>  > like to use it in a "tablet" mode and get used to the touch screen
>  > interface.
>  >
>
>  i do have a couple of suggestions and ideas that might be of help.
>  i'm a longtime user of mythtv and what i really like about it is its scheduler.
>  but there are other areas that could use with improving or using something else
>  for.
>
>  so one idea is to let tvheadend control your capture devices (for example usb
>  based) and then point mythtv backend at tvheadend.
>  to make this work i created a php script to produce a correctly formatted m3u
>  file based on data from tvheadend automatically that makes mythbackend happy.
>  basically mythbackend streams from tvheadend.
>
>  this kind of setup can give you a few additional things compared to a pure
>  mythtv setup.
>  main reason for me was the lack of dvb-t2 plp support in mythtv making most
>  channels not show up, plp is supported in tvheadend with a bit of fiddling with
>  settings.
>  also you can then use for example kodi as frontend and let kodi use tvheadend
>  as pvr and setup your media library (like recordings) to point to where
>  mythbackend stores it.
>
>
>  only thing your then missing is a way to schedule things in mythbackend but web
>  interface probably works.
>
>  i don't know if it is easier to setup kodi instead of trying to get x11 working
>  with your display.
>
>
>  one issue you will likely run into is that tvheadend at least the one in fedora
>  28 does not include the needed bits for support for a ca module.
>  this i had to rebuild myself and compile in.
>  the issue is the need for libdvben50221 that is part of dvb-apps but not
>  included by default in the package. 
Did you filed a bug for the missing bits? I don't see one here:
https://apps.fedoraproject.org/packages/dvb-apps/bugs

>  i haven't followed development of tvheadend closely in this area
> but i hope it
>  gets fixed properly and ca module support gets added to tvheadend in fedora. 
I have no idea what you mean by "ca module support", is that a kernel
module?  A mythtv module or something in another package?

> oh, i almost forgot.
> as you know the filenames created by mythtv is not very user friendly so i made
> a script around mythlink.pl so it can tell the difference between movies and
> series and then produce a folder structure more compatible with kodi and its
> way of figuring out what metadata to load.
> another way instead of this would be to point kodi at the upnp exposed library
> by the backend, this is also a quite nice structure with sane titles and so on.
> _______________________________________________
> 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/[e-mail]