msmmbl
Posts: 7
Joined: Thu Jun 27, 2019 2:25 pm

After upgrade To buster Composite output stop working

Thu Jun 27, 2019 2:45 pm

I follow the guide in this article https://www.raspberrypi.org/blog/buster ... -raspbian/, to upgrade my raspberry 3 from Stretch to buster. But I found Composite output stop working. It was worked when system was Stretch.

VNC stop working too, It says "Cannot currently show the desktop". I found this thread https://www.raspberrypi.org/forums/view ... p?t=216737 and try set resolution in raspi-config. After reboot, VNC worked, but still no Composite output.

here is my config.txt:

Code: Select all

# For more options and information see
# http://rpf.io/configtxt
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
overscan_left=24
overscan_right=32
overscan_top=8
overscan_bottom=8

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# Uncomment some or all of these to enable the optional hardware interfaces
dtparam=i2c_arm=on
#dtparam=i2s=on
dtparam=spi=on

# Uncomment this to enable the lirc-rpi module
#dtoverlay=lirc-rpi

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
dtparam=audio=on
[2018年 12月 02日 星期日 17:34:18 CST] Executing cat
# Enable HiFiberry Amp
#dtoverlay=hifiberry-amp

# Enable HiFiberry DAC Light
#dtoverlay=hifiberry-dac

# Enable HiFiberry DAC Standard/Pro
#dtoverlay=hifiberry-dacplus


# Enable HiFiberry Digi
#dtoverlay=hifiberry-digi

# Enable iqaudio-dac
#dtoverlay=iqaudio-dac

# Enable iqaudio-dac+
#dtoverlay=iqaudio-dacplus

# Enable iqaudio-DigiAMP+
#dtoverlay=iqaudio-dacplus,unmute_amp

# Enable iqaudio-Digi+
#dtoverlay=iqaudio-digi-wm8804-audio

# Enable JustBoom DAC and AMP Card
#dtoverlay=justboom-dac

# Enable JustBoom Digi Cards
#dtoverlay=justboom-digi

audio_pwm_mode = 2

which VNC and Composite output are both works when system Stretch. I found this article(https://www.raspberrypi.org/blog/buster ... -raspbian/) says " analogue video output is disabled by default" on buster . But how can I enable it on Raspberry 3?

jamesh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 23076
Joined: Sat Jul 30, 2011 7:41 pm

Re: After upgrade To buster Composite output stop working

Thu Jun 27, 2019 3:10 pm

You need to either use raspi-config or the config gui to enable composite, or edit config.txt and add enable_tvout=1

We had to disable composite by default for performance reasons, but this does mean that the Pi4 runs more slowly when composite is enabled. Bizarre, but true!
Principal Software Engineer at Raspberry Pi (Trading) Ltd.
Contrary to popular belief, humorous signatures are allowed. Here's an example...
"My grief counseller just died, luckily, he was so good, I didn't care."

msmmbl
Posts: 7
Joined: Thu Jun 27, 2019 2:25 pm

Re: After upgrade To buster Composite output stop working

Fri Jun 28, 2019 1:19 am

jamesh wrote:
Thu Jun 27, 2019 3:10 pm
You need to either use raspi-config or the config gui to enable composite, or edit config.txt and add enable_tvout=1

We had to disable composite by default for performance reasons, but this does mean that the Pi4 runs more slowly when composite is enabled. Bizarre, but true!
Thank you, But enable_tvout is raspberry 4 only param. I use raspberry 3.

msmmbl
Posts: 7
Joined: Thu Jun 27, 2019 2:25 pm

Re: After upgrade To buster Composite output stop working

Fri Jun 28, 2019 2:21 am

Some new finding.
1. Add hdmi_force_hotplug=1 to config.txt, VNC works and show Desktop. Then /opt/vc/bin/tvservice -c "PAL 4:3", it says:
[E] Failed to power on SDTV with explicit settings (mode:2 aspect:1)

2. comment hdmi_force_hotplug=1, VNC say "Cannot currently show the desktop". After run /opt/vc/bin/tvservice -c "PAL 4:3", it says "Powering on SDTV with explicit settings (mode:2 aspect:1)", and TV change from no signal to black screen, and can't see desktop.

msmmbl
Posts: 7
Joined: Thu Jun 27, 2019 2:25 pm

Re: After upgrade To buster Composite output stop working

Fri Jun 28, 2019 2:26 am

I will try a fresh install buster, not upgrade, to see the problem.

klricks
Posts: 6499
Joined: Sat Jan 12, 2013 3:01 am
Location: Grants Pass, OR, USA
Contact: Website

Re: After upgrade To buster Composite output stop working

Fri Jun 28, 2019 2:50 am

jamesh wrote:
Thu Jun 27, 2019 3:10 pm
You need to either use raspi-config or the config gui to enable composite, or edit config.txt and add enable_tvout=1

We had to disable composite by default for performance reasons, but this does mean that the Pi4 runs more slowly when composite is enabled. Bizarre, but true!
On my RPi3B+ composite does not work. There is no option for composite in raspi-config and enable_tvout=1 does not work.
I also tried enabling sdtv= x in config.txt
Unless specified otherwise my response is based on the latest and fully updated Raspbian Buster w/ Desktop OS.

jamesh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 23076
Joined: Sat Jul 30, 2011 7:41 pm

Re: After upgrade To buster Composite output stop working

Fri Jun 28, 2019 6:34 am

Hmm, interesting. Will need to take a look at that.
Principal Software Engineer at Raspberry Pi (Trading) Ltd.
Contrary to popular belief, humorous signatures are allowed. Here's an example...
"My grief counseller just died, luckily, he was so good, I didn't care."

maazl2
Posts: 4
Joined: Sun Jun 30, 2019 5:06 pm

Re: After upgrade To buster Composite output stop working

Sun Jun 30, 2019 5:22 pm

Same problem here with Raspberry Model 1.
Regardless if I upgrade from Stretch or do a clean Raspbian Buster install composite video output is always dead. I fiddled around with config.txt, but no change.

The upgraded installation is reachable via ssh.
If I do

Code: Select all

tvservice -c "PAL 4:3"
there is some signal, but it is entirely black.
I see the following error in kern.log:

Code: Select all

Jun 30 18:34:43 raspi kernel: [    0.264940] bcm2708_fb soc:fb: Unable to determine number of FB's. Assuming 1
Jun 30 18:34:43 raspi kernel: [    0.265000] bcm2708_fb soc:fb: FB found 1 display(s)
Jun 30 18:34:43 raspi kernel: [    0.265719] raspberrypi-firmware soc:firmware: Request 0x00048003 returned status 0x80000001
Jun 30 18:34:43 raspi kernel: [    0.265780] bcm2708_fb soc:fb: Failed to allocate GPU framebuffer (-22)
Jun 30 18:34:43 raspi kernel: [    0.265834] bcm2708_fb soc:fb: probe failed, err -22
Jun 30 18:34:43 raspi kernel: [    0.265893] bcm2708_fb: probe of soc:fb failed with error -22
I think the 4.19 kernel or the firmware is the problem.

thadhouse
Posts: 3
Joined: Fri Jun 28, 2019 1:13 am

Re: After upgrade To buster Composite output stop working

Mon Jul 01, 2019 2:16 am

Is there a way to download stretch still, for those of us that still need composite working? I can't find a download for it easily on the site, and I need composite output for one of my projects.

Either that, or hopefully a fix can be found soon.


jamesh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 23076
Joined: Sat Jul 30, 2011 7:41 pm

Re: After upgrade To buster Composite output stop working

Mon Jul 01, 2019 9:07 am

Github issue is here

https://github.com/raspberrypi/firmware/issues/1166

Can someone try and answer the question from 6by9?
Principal Software Engineer at Raspberry Pi (Trading) Ltd.
Contrary to popular belief, humorous signatures are allowed. Here's an example...
"My grief counseller just died, luckily, he was so good, I didn't care."

klricks
Posts: 6499
Joined: Sat Jan 12, 2013 3:01 am
Location: Grants Pass, OR, USA
Contact: Website

Re: After upgrade To buster Composite output stop working

Mon Jul 01, 2019 12:34 pm

jamesh wrote:
Mon Jul 01, 2019 9:07 am
Github issue is here

https://github.com/raspberrypi/firmware/issues/1166

Can someone try and answer the question from 6by9?
On a RPi3B+
$ vcgencmd get_config enable_tvout
enable_tvout is unknown
pi@raspberrypi:~ $

enable_tvout=1 to /boot/config.txt. did not help.
Unless specified otherwise my response is based on the latest and fully updated Raspbian Buster w/ Desktop OS.

jamesh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 23076
Joined: Sat Jul 30, 2011 7:41 pm

Re: After upgrade To buster Composite output stop working

Mon Jul 01, 2019 1:34 pm

Ah, as 6by9 stated on the github, we currently build the older devices firmware on a different branch, and that doesn't have the enable_tvout option. He's going to investigate further.
Principal Software Engineer at Raspberry Pi (Trading) Ltd.
Contrary to popular belief, humorous signatures are allowed. Here's an example...
"My grief counseller just died, luckily, he was so good, I didn't care."

hippy
Posts: 5588
Joined: Fri Sep 09, 2011 10:34 pm
Location: UK

Re: After upgrade To buster Composite output stop working

Mon Jul 01, 2019 2:17 pm

jamesh wrote:
Mon Jul 01, 2019 9:07 am
Github issue is here

https://github.com/raspberrypi/firmware/issues/1166

Can someone try and answer the question from 6by9?
Tested Stretch on Pi 1B Rev 2 with only composite connected, composite display works on booting for NTSC and PAL.

Same composite only set-up, but booting Buster, no display.

Code: Select all

pi@raspberrypi:~ $ tvservice -s
state 0x120001 [TV is off]
pi@raspberrypi:~ $ vcgencmd get_config enable_tvout
enable_tvout is unknown
After adding sdtv_mode=1 and reboot, same. Same for =2.

Code: Select all

pi@raspberrypi:~ $ tvservice -c "NTSC 4:3"
Powering on SDTV with explicit settings (mode:0 aspect:1)
pi@raspberrypi:~ $ tvservice -s
state 0x40001 [NTSC 4:3], 720x480 @ 60.00Hz, interlaced
No display. Same with PAL. After reboot, back to original "TV is off".

With sdtv_mode=1, enable_tvout=1 and reboot, same -

Code: Select all

pi@raspberrypi:~ $ tvservice -s
state 0x120001 [TV is off]
pi@raspberrypi:~ $ vcgencmd get_config enable_tvout
enable_tvout is unknown
pi@raspberrypi:~ $ uname -a
Linux raspberrypi 4.19.50+ #896 Thu Jun 20 16:09:52 BST 2019 armv6l GNU/Linux
pi@raspberrypi:~ $ cat /proc/cpuinfo
processor       : 0
model name      : ARMv6-compatible processor rev 7 (v6l)
BogoMIPS        : 697.95
Features        : half thumb fastmult vfp edsp java tls 
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x0
CPU part        : 0xb76
CPU revision    : 7

Hardware        : BCM2835
Revision        : 000f
Serial          : 000000001cb81749
pi@raspberrypi:~ $ 
Not sure if relevant, but there are no /dev/fb* devices created under Buster, there is a /dev/fb0 with Stretch.

jamesh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 23076
Joined: Sat Jul 30, 2011 7:41 pm

Re: After upgrade To buster Composite output stop working

Tue Jul 02, 2019 1:14 pm

I have found the problem and fixed it. WIll be in a rpi-update in the near future.
Principal Software Engineer at Raspberry Pi (Trading) Ltd.
Contrary to popular belief, humorous signatures are allowed. Here's an example...
"My grief counseller just died, luckily, he was so good, I didn't care."

msmmbl
Posts: 7
Joined: Thu Jun 27, 2019 2:25 pm

Re: After upgrade To buster Composite output stop working

Tue Jul 02, 2019 2:12 pm

jamesh wrote:
Tue Jul 02, 2019 1:14 pm
I have found the problem and fixed it. WIll be in a rpi-update in the near future.
👍👍👍

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5285
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: After upgrade To buster Composite output stop working

Tue Jul 02, 2019 2:56 pm

Fix is in latest rpi-update firmware.
Will appear in apt firmware soon.

hippy
Posts: 5588
Joined: Fri Sep 09, 2011 10:34 pm
Location: UK

Re: After upgrade To buster Composite output stop working

Tue Jul 02, 2019 5:37 pm

rpi-update worked for me. Composite output now appearing on the display. Not tested further than that. Many thanks for the fix.

msmmbl
Posts: 7
Joined: Thu Jun 27, 2019 2:25 pm

Re: After upgrade To buster Composite output stop working

Wed Jul 03, 2019 1:44 am

After rpi-update, I can see the "Under-voltage" sign in my composite screen. But screen is Black and desktop not see.
vnc says

Code: Select all

7月 03 09:06:01 raspberrypi vncserver-x11[489]: ServerManager: Server started
7月 03 09:06:02 raspberrypi vncserver-x11[489]: ConsoleDisplay: Cannot find a running X server on vt1
7月 03 09:06:02 raspberrypi vncserver-x11[489]: ConsoleDisplay: Found running X server (pid=663, binary=/usr/lib/xorg/Xorg)
7月 03 09:06:06 raspberrypi vncserver-x11[489]: Connections: connected: 192.168.11.194::44552 (TCP)
7月 03 09:06:06 raspberrypi vncserver-x11[489]: session started: user pi permissions f
7月 03 09:06:06 raspberrypi vncserver-x11[489]: Connections: authenticated: 192.168.11.194::44552 (TCP), as pi (f permissions)
7月 03 09:06:07 raspberrypi vncserver-x11[489]: AgentInitCheck: no response from agent
7月 03 09:06:12 raspberrypi vncserver-x11[489]: Agent: SServerAgent: Unknown parameter 'UseXFixes'
7月 03 09:06:12 raspberrypi vncserver-x11[489]: Agent: SServerAgent: Unknown parameter 'CaptureMethod'
7月 03 09:09:47 raspberrypi vncserver-x11[489]: AgentInitCheck: agent comms failure
7月 03 09:09:52 raspberrypi vncserver-x11[489]: AgentInitCheck: no response from agent
/var/log/Xorg.0.log

Code: Select all

[    16.312] 
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
[    16.312] Build Operating System: Linux 4.15.0-48-generic armv8l Raspbian
[    16.312] Current Operating System: Linux raspberrypi 4.19.56-v7+ #1242 SMP Wed Jun 26 17:31:47 BST 2019 armv7l
[    16.312] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 bcm2708_fb.fbwidth=640 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=PARTUUID=afa6b674-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
[    16.312] Build Date: 05 June 2019  12:49:54PM
[    16.312] xorg-server 2:1.20.4-1+rpt1 (https://www.debian.org/support) 
[    16.313] Current version of pixman: 0.36.0
[    16.313] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[    16.313] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    16.313] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jul  3 09:06:01 2019
[    16.325] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    16.366] (==) No Layout section.  Using the first Screen section.
[    16.366] (==) No screen section available. Using defaults.
[    16.366] (**) |-->Screen "Default Screen Section" (0)
[    16.366] (**) |   |-->Monitor "<default monitor>"
[    16.383] (==) No device specified for screen "Default Screen Section".
	Using the first device section listed.
[    16.384] (**) |   |-->Device "Allwinner A10/A13 FBDEV"
[    16.384] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[    16.384] (==) Automatically adding devices
[    16.384] (==) Automatically enabling devices
[    16.384] (==) Automatically adding GPU devices
[    16.384] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    16.384] (WW) The directory "/usr/share/fonts/X11/misc" does not exist.
[    16.384] 	Entry deleted from font path.
[    16.384] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[    16.384] 	Entry deleted from font path.
[    16.384] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[    16.384] 	Entry deleted from font path.
[    16.384] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[    16.384] 	Entry deleted from font path.
[    16.384] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist.
[    16.385] 	Entry deleted from font path.
[    16.385] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[    16.385] 	Entry deleted from font path.
[    16.385] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[    16.385] 	Entry deleted from font path.
[    16.385] (==) FontPath set to:
	built-ins
[    16.385] (==) ModulePath set to "/usr/lib/xorg/modules"
[    16.385] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[    16.385] (II) Loader magic: 0x1fcf80
[    16.385] (II) Module ABI versions:
[    16.385] 	X.Org ANSI C Emulation: 0.4
[    16.385] 	X.Org Video Driver: 24.0
[    16.385] 	X.Org XInput driver : 24.1
[    16.385] 	X.Org Server Extension : 10.0
[    16.389] (++) using VT number 7

[    16.390] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[    16.391] (II) no primary bus or device found
[    16.391] (II) LoadModule: "glx"
[    16.481] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    17.037] (II) Module glx: vendor="X.Org Foundation"
[    17.037] 	compiled for 1.20.4, module version = 1.0.0
[    17.037] 	ABI class: X.Org Server Extension, version 10.0
[    17.037] (II) LoadModule: "fbturbo"
[    17.038] (II) Loading /usr/lib/xorg/modules/drivers/fbturbo_drv.so
[    17.081] (II) Module fbturbo: vendor="X.Org Foundation"
[    17.081] 	compiled for 1.20.3, module version = 0.5.1
[    17.081] 	Module class: X.Org Video Driver
[    17.081] 	ABI class: X.Org Video Driver, version 24.0
[    17.081] (II) FBTURBO: driver for framebuffer: fbturbo
[    17.092] (WW) Falling back to old probe method for fbturbo
[    17.093] (II) Loading sub module "fbdevhw"
[    17.093] (II) LoadModule: "fbdevhw"
[    17.094] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[    17.115] (II) Module fbdevhw: vendor="X.Org Foundation"
[    17.115] 	compiled for 1.20.4, module version = 0.0.2
[    17.116] 	ABI class: X.Org Video Driver, version 24.0
[    17.116] (II) FBTURBO(0): using /dev/fb0
[    17.116] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[    17.117] (II) FBTURBO(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[    17.117] (==) FBTURBO(0): Depth 24, (==) framebuffer bpp 32
[    17.117] (==) FBTURBO(0): RGB weight 888
[    17.117] (==) FBTURBO(0): Default visual is TrueColor
[    17.117] (==) FBTURBO(0): Using gamma correction (1.0, 1.0, 1.0)
[    17.117] (II) FBTURBO(0): hardware: BCM2708 FB (video memory: 1200kB)
[    17.117] (DB) xf86MergeOutputClassOptions unsupported bus type 0
[    17.117] (**) FBTURBO(0): Option "fbdev" "/dev/fb0"
[    17.117] (**) FBTURBO(0): Option "SwapbuffersWait" "true"
[    17.118] (II) FBTURBO(0): processor: Unknown
[    17.118] (II) FBTURBO(0): checking modes against framebuffer device...
[    17.118] (II) FBTURBO(0): checking modes against monitor...
[    17.118] (II) FBTURBO(0): Virtual size is 640x480 (pitch 640)
[    17.118] (**) FBTURBO(0):  Built-in mode "current"
[    17.119] (==) FBTURBO(0): DPI set to (96, 96)
[    17.119] (II) Loading sub module "fb"
[    17.119] (II) LoadModule: "fb"
[    17.119] (II) Loading /usr/lib/xorg/modules/libfb.so
[    17.144] (II) Module fb: vendor="X.Org Foundation"
[    17.145] 	compiled for 1.20.4, module version = 1.0.0
[    17.145] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    17.217] (II) FBTURBO(0): using backing store heuristics
[    17.238] (II) FBTURBO(0): can't load 'g2d_23' kernel module
[    17.238] (II) FBTURBO(0): failed to enable the use of sunxi display controller
[    17.238] (II) FBTURBO(0): No sunxi-g2d hardware detected (check /dev/disp and /dev/g2d)
[    17.238] (II) FBTURBO(0): G2D hardware acceleration can't be enabled
[    17.238] (II) FBTURBO(0): enabled fbdev copyarea acceleration
[    17.239] (==) FBTURBO(0): Backing store enabled
[    17.292] (==) FBTURBO(0): DPMS enabled
[    17.292] (II) FBTURBO(0): failed to enable hardware cursor
[    17.292] (II) FBTURBO(0): no 3D acceleration because the driver has been compiled without libUMP
[    17.292] (II) FBTURBO(0): if this is wrong and needs to be fixed, please check ./configure log
[    17.300] (II) Initializing extension Generic Event Extension
[    17.302] (II) Initializing extension SHAPE
[    17.305] (II) Initializing extension MIT-SHM
[    17.307] (II) Initializing extension XInputExtension
[    17.320] (II) Initializing extension XTEST
[    17.322] (II) Initializing extension BIG-REQUESTS
[    17.324] (II) Initializing extension SYNC
[    17.329] (II) Initializing extension XKEYBOARD
[    17.332] (II) Initializing extension XC-MISC
[    17.335] (II) Initializing extension SECURITY
[    17.338] (II) Initializing extension XFIXES
[    17.340] (II) Initializing extension RENDER
[    17.343] (II) Initializing extension RANDR
[    17.348] (II) Initializing extension COMPOSITE
[    17.359] (II) Initializing extension DAMAGE
[    17.361] (II) Initializing extension MIT-SCREEN-SAVER
[    17.363] (II) Initializing extension DOUBLE-BUFFER
[    17.365] (II) Initializing extension RECORD
[    17.366] (II) Initializing extension DPMS
[    17.368] (II) Initializing extension Present
[    17.370] (II) Initializing extension DRI3
[    17.370] (II) Initializing extension X-Resource
[    17.372] (II) Initializing extension XVideo
[    17.374] (II) Initializing extension XVideo-MotionCompensation
[    17.374] (II) Initializing extension SELinux
[    17.374] (II) SELinux: Disabled on system
[    17.374] (II) Initializing extension GLX
[    17.376] (II) AIGLX: Screen 0 is not DRI2 capable
[    21.406] (II) IGLX: Loaded and initialized swrast
[    21.407] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[    21.407] (II) Initializing extension XFree86-VidModeExtension
[    21.409] (II) Initializing extension XFree86-DGA
[    21.411] (II) Initializing extension XFree86-DRI
[    21.417] (II) Initializing extension DRI2
[    21.857] (II) config/udev: Adding input device (unnamed) (/dev/input/event0)
[    21.857] (**) (unnamed): Applying InputClass "libinput keyboard catchall"
[    21.857] (II) LoadModule: "libinput"
[    21.858] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[    22.012] (II) Module libinput: vendor="X.Org Foundation"
[    22.012] 	compiled for 1.20.3, module version = 0.28.2
[    22.012] 	Module class: X.Org XInput Driver
[    22.013] 	ABI class: X.Org XInput driver, version 24.1
[    22.013] (II) Using input driver 'libinput' for '(unnamed)'
[    22.013] (**) (unnamed): always reports core events
[    22.013] (**) Option "Device" "/dev/input/event0"
[    22.013] (**) Option "_source" "server/udev"
[    22.120] (EE) client bug: Invalid path /dev/input/event0
[    22.121] (EE) libinput: (unnamed): Failed to create a device for /dev/input/event0
[    22.123] (EE) PreInit returned 2 for "(unnamed)"
[    22.124] (II) UnloadModule: "libinput"
[    22.477] (II) config/udev: Adding input device vnc-relpointer (/dev/input/mouse1)
[    22.477] (II) No input driver specified, ignoring this device.
[    22.477] (II) This device may have been added with another device file.
[    22.554] (II) config/udev: Adding input device vnc-relpointer (/dev/input/event2)
[    22.554] (**) vnc-relpointer: Applying InputClass "libinput pointer catchall"
[    22.554] (II) Using input driver 'libinput' for 'vnc-relpointer'
[    22.554] (**) vnc-relpointer: always reports core events
[    22.554] (**) Option "Device" "/dev/input/event2"
[    22.554] (**) Option "_source" "server/udev"
[    22.562] (EE) client bug: Invalid path /dev/input/event2
[    22.562] (EE) libinput: vnc-relpointer: Failed to create a device for /dev/input/event2
[    22.564] (EE) PreInit returned 2 for "vnc-relpointer"
[    22.564] (II) UnloadModule: "libinput"
[    22.648] (II) config/udev: Adding input device vnc-abspointer (/dev/input/mouse0)
[    22.648] (II) No input driver specified, ignoring this device.
[    22.648] (II) This device may have been added with another device file.
[    22.668] (II) config/udev: Adding input device vnc-keyboard (/dev/input/event0)
[    22.668] (**) vnc-keyboard: Applying InputClass "libinput keyboard catchall"
[    22.668] (II) Using input driver 'libinput' for 'vnc-keyboard'
[    22.668] (**) vnc-keyboard: always reports core events
[    22.669] (**) Option "Device" "/dev/input/event0"
[    22.669] (**) Option "_source" "server/udev"
[    22.691] (II) event0  - vnc-keyboard: is tagged by udev as: Keyboard
[    22.691] (II) event0  - vnc-keyboard: device is a keyboard
[    22.692] (II) event0  - vnc-keyboard: device removed
[    22.730] (**) Option "config_info" "udev:/sys/devices/virtual/input/input3/event0"
[    22.731] (II) XINPUT: Adding extended input device "vnc-keyboard" (type: KEYBOARD, id 6)
[    22.731] (**) Option "xkb_model" "pc105"
[    22.731] (**) Option "xkb_layout" "cn"
[    22.731] (WW) Option "xkb_variant" requires a string value
[    22.731] (WW) Option "xkb_options" requires a string value
[    22.930] (II) event0  - vnc-keyboard: is tagged by udev as: Keyboard
[    22.930] (II) event0  - vnc-keyboard: device is a keyboard
[    22.932] (II) config/udev: Adding input device (unnamed) (/dev/input/js0)
[    22.932] (II) No input driver specified, ignoring this device.
[    22.933] (II) This device may have been added with another device file.
[    22.934] (II) config/udev: Adding input device (unnamed) (/dev/input/event1)
[    22.934] (**) (unnamed): Applying InputClass "libinput pointer catchall"
[    22.934] (II) Using input driver 'libinput' for '(unnamed)'
[    22.934] (**) (unnamed): always reports core events
[    22.934] (**) Option "Device" "/dev/input/event1"
[    22.935] (**) Option "_source" "server/udev"
[    22.935] (EE) client bug: Invalid path /dev/input/event1
[    22.935] (EE) libinput: (unnamed): Failed to create a device for /dev/input/event1
[    22.935] (EE) PreInit returned 2 for "(unnamed)"
[    22.935] (II) UnloadModule: "libinput"
[    22.965] (II) config/udev: removing device vnc-keyboard
[    22.966] (II) event0  - vnc-keyboard: device removed
[    23.001] (II) UnloadModule: "libinput"
[    27.472] (II) config/udev: Adding input device vnc-abspointer (/dev/input/js0)
[    27.473] (II) No input driver specified, ignoring this device.
[    27.473] (II) This device may have been added with another device file.
[    27.513] (II) config/udev: Adding input device vnc-relpointer (/dev/input/mouse1)
[    27.513] (II) No input driver specified, ignoring this device.
[    27.513] (II) This device may have been added with another device file.
[    27.566] (II) config/udev: Adding input device vnc-abspointer (/dev/input/mouse0)
[    27.566] (II) No input driver specified, ignoring this device.
[    27.567] (II) This device may have been added with another device file.
[    27.613] (II) config/udev: Adding input device vnc-keyboard (/dev/input/event0)
[    27.613] (**) vnc-keyboard: Applying InputClass "libinput keyboard catchall"
[    27.613] (II) Using input driver 'libinput' for 'vnc-keyboard'
[    27.613] (**) vnc-keyboard: always reports core events
[    27.613] (**) Option "Device" "/dev/input/event0"
[    27.614] (**) Option "_source" "server/udev"
[    27.625] (II) event0  - vnc-keyboard: is tagged by udev as: Keyboard
[    27.625] (II) event0  - vnc-keyboard: device is a keyboard
[    27.626] (II) event0  - vnc-keyboard: device removed
[    27.670] (**) Option "config_info" "udev:/sys/devices/virtual/input/input6/event0"
[    27.670] (II) XINPUT: Adding extended input device "vnc-keyboard" (type: KEYBOARD, id 6)
[    27.670] (**) Option "xkb_model" "pc105"
[    27.670] (**) Option "xkb_layout" "cn"
[    27.670] (WW) Option "xkb_variant" requires a string value
[    27.670] (WW) Option "xkb_options" requires a string value
[    27.676] (II) event0  - vnc-keyboard: is tagged by udev as: Keyboard
[    27.676] (II) event0  - vnc-keyboard: device is a keyboard
[    27.679] (II) config/udev: Adding input device vnc-relpointer (/dev/input/event2)
[    27.679] (**) vnc-relpointer: Applying InputClass "libinput pointer catchall"
[    27.679] (II) Using input driver 'libinput' for 'vnc-relpointer'
[    27.680] (**) vnc-relpointer: always reports core events
[    27.680] (**) Option "Device" "/dev/input/event2"
[    27.680] (**) Option "_source" "server/udev"
[    27.743] (II) event2  - vnc-relpointer: is tagged by udev as: Mouse
[    27.743] (II) event2  - vnc-relpointer: device is a pointer
[    27.744] (II) event2  - vnc-relpointer: device removed
[    27.841] (**) Option "config_info" "udev:/sys/devices/virtual/input/input8/event2"
[    27.842] (II) XINPUT: Adding extended input device "vnc-relpointer" (type: MOUSE, id 7)
[    27.843] (**) Option "AccelerationScheme" "none"
[    27.844] (**) vnc-relpointer: (accel) selected scheme none/0
[    27.844] (**) vnc-relpointer: (accel) acceleration factor: 2.000
[    27.844] (**) vnc-relpointer: (accel) acceleration threshold: 4
[    27.848] (II) event2  - vnc-relpointer: is tagged by udev as: Mouse
[    27.849] (II) event2  - vnc-relpointer: device is a pointer
[    27.853] (II) config/udev: Adding input device vnc-abspointer (/dev/input/event1)
[    27.853] (**) vnc-abspointer: Applying InputClass "libinput pointer catchall"
[    27.853] (II) Using input driver 'libinput' for 'vnc-abspointer'
[    27.856] (**) vnc-abspointer: always reports core events
[    27.857] (**) Option "Device" "/dev/input/event1"
[    27.857] (**) Option "_source" "server/udev"
[    27.862] (II) event1  - vnc-abspointer: is tagged by udev as: Mouse
[    27.863] (II) event1  - vnc-abspointer: device is a pointer
[    27.864] (II) event1  - vnc-abspointer: device removed
[    27.960] (**) Option "config_info" "udev:/sys/devices/virtual/input/input7/event1"
[    27.960] (II) XINPUT: Adding extended input device "vnc-abspointer" (type: MOUSE, id 8)
[    27.961] (**) Option "AccelerationScheme" "none"
[    27.961] (**) vnc-abspointer: (accel) selected scheme none/0
[    27.961] (**) vnc-abspointer: (accel) acceleration factor: 2.000
[    27.961] (**) vnc-abspointer: (accel) acceleration threshold: 4
[    27.965] (II) event1  - vnc-abspointer: is tagged by udev as: Mouse
[    27.966] (II) event1  - vnc-abspointer: device is a pointer
[   215.803] (II) config/udev: removing device vnc-relpointer
[   215.804] (II) event2  - vnc-relpointer: device removed
[   215.873] (II) UnloadModule: "libinput"
[   215.943] (II) config/udev: removing device vnc-abspointer
[   215.944] (II) event1  - vnc-abspointer: device removed
[   215.991] (II) UnloadModule: "libinput"
[   216.134] (II) config/udev: removing device vnc-keyboard
[   216.134] (II) event0  - vnc-keyboard: device removed
[   216.201] (II) UnloadModule: "libinput"
[   625.475] (II) FBTURBO(0): FBIOBLANK: Invalid argument (Screen blanking not supported by kernel - disabling)
if I uncomment hdmi_force_hotplug=1, hdmi and vnc works fine.

maazl2
Posts: 4
Joined: Sun Jun 30, 2019 5:06 pm

Re: After upgrade To buster Composite output stop working

Wed Jul 03, 2019 9:15 pm

The fix brought back the console video output as well as the X screen.
But I think video overlay is still broken. Neither omxplayer nor vdr show any video.

vdr/rpihddevice shows an error at initialization:

Code: Select all

Jul  3 23:03:26 raspi vdr: [2446] initializing plugin: rpihddevice (1.0.4): HD Ausgabegerät für Raspberry Pi
Jul  3 23:03:26 raspi vdr: [2446] rpihddevice: failed to get display information!
Omxplayer shows no error. It just does not play anything. You can seek within the video but time is stopped.

msmmbl
Posts: 7
Joined: Thu Jun 27, 2019 2:25 pm

Re: After upgrade To buster Composite output stop working

Thu Jul 04, 2019 5:33 am

msmmbl wrote:
Wed Jul 03, 2019 1:44 am
After rpi-update, I can see the "Under-voltage" sign in my composite screen. But screen is Black and desktop not see.
vnc says

Code: Select all

7月 03 09:06:01 raspberrypi vncserver-x11[489]: ServerManager: Server started
7月 03 09:06:02 raspberrypi vncserver-x11[489]: ConsoleDisplay: Cannot find a running X server on vt1
7月 03 09:06:02 raspberrypi vncserver-x11[489]: ConsoleDisplay: Found running X server (pid=663, binary=/usr/lib/xorg/Xorg)
7月 03 09:06:06 raspberrypi vncserver-x11[489]: Connections: connected: 192.168.11.194::44552 (TCP)
7月 03 09:06:06 raspberrypi vncserver-x11[489]: session started: user pi permissions f
7月 03 09:06:06 raspberrypi vncserver-x11[489]: Connections: authenticated: 192.168.11.194::44552 (TCP), as pi (f permissions)
7月 03 09:06:07 raspberrypi vncserver-x11[489]: AgentInitCheck: no response from agent
7月 03 09:06:12 raspberrypi vncserver-x11[489]: Agent: SServerAgent: Unknown parameter 'UseXFixes'
7月 03 09:06:12 raspberrypi vncserver-x11[489]: Agent: SServerAgent: Unknown parameter 'CaptureMethod'
7月 03 09:09:47 raspberrypi vncserver-x11[489]: AgentInitCheck: agent comms failure
7月 03 09:09:52 raspberrypi vncserver-x11[489]: AgentInitCheck: no response from agent
/var/log/Xorg.0.log

Code: Select all

[    16.312] 
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
[    16.312] Build Operating System: Linux 4.15.0-48-generic armv8l Raspbian
[    16.312] Current Operating System: Linux raspberrypi 4.19.56-v7+ #1242 SMP Wed Jun 26 17:31:47 BST 2019 armv7l
[    16.312] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 bcm2708_fb.fbwidth=640 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=PARTUUID=afa6b674-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
[    16.312] Build Date: 05 June 2019  12:49:54PM
[    16.312] xorg-server 2:1.20.4-1+rpt1 (https://www.debian.org/support) 
[    16.313] Current version of pixman: 0.36.0
[    16.313] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[    16.313] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    16.313] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jul  3 09:06:01 2019
[    16.325] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    16.366] (==) No Layout section.  Using the first Screen section.
[    16.366] (==) No screen section available. Using defaults.
[    16.366] (**) |-->Screen "Default Screen Section" (0)
[    16.366] (**) |   |-->Monitor "<default monitor>"
[    16.383] (==) No device specified for screen "Default Screen Section".
	Using the first device section listed.
[    16.384] (**) |   |-->Device "Allwinner A10/A13 FBDEV"
[    16.384] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[    16.384] (==) Automatically adding devices
[    16.384] (==) Automatically enabling devices
[    16.384] (==) Automatically adding GPU devices
[    16.384] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    16.384] (WW) The directory "/usr/share/fonts/X11/misc" does not exist.
[    16.384] 	Entry deleted from font path.
[    16.384] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[    16.384] 	Entry deleted from font path.
[    16.384] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[    16.384] 	Entry deleted from font path.
[    16.384] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[    16.384] 	Entry deleted from font path.
[    16.384] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist.
[    16.385] 	Entry deleted from font path.
[    16.385] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[    16.385] 	Entry deleted from font path.
[    16.385] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[    16.385] 	Entry deleted from font path.
[    16.385] (==) FontPath set to:
	built-ins
[    16.385] (==) ModulePath set to "/usr/lib/xorg/modules"
[    16.385] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[    16.385] (II) Loader magic: 0x1fcf80
[    16.385] (II) Module ABI versions:
[    16.385] 	X.Org ANSI C Emulation: 0.4
[    16.385] 	X.Org Video Driver: 24.0
[    16.385] 	X.Org XInput driver : 24.1
[    16.385] 	X.Org Server Extension : 10.0
[    16.389] (++) using VT number 7

[    16.390] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[    16.391] (II) no primary bus or device found
[    16.391] (II) LoadModule: "glx"
[    16.481] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    17.037] (II) Module glx: vendor="X.Org Foundation"
[    17.037] 	compiled for 1.20.4, module version = 1.0.0
[    17.037] 	ABI class: X.Org Server Extension, version 10.0
[    17.037] (II) LoadModule: "fbturbo"
[    17.038] (II) Loading /usr/lib/xorg/modules/drivers/fbturbo_drv.so
[    17.081] (II) Module fbturbo: vendor="X.Org Foundation"
[    17.081] 	compiled for 1.20.3, module version = 0.5.1
[    17.081] 	Module class: X.Org Video Driver
[    17.081] 	ABI class: X.Org Video Driver, version 24.0
[    17.081] (II) FBTURBO: driver for framebuffer: fbturbo
[    17.092] (WW) Falling back to old probe method for fbturbo
[    17.093] (II) Loading sub module "fbdevhw"
[    17.093] (II) LoadModule: "fbdevhw"
[    17.094] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[    17.115] (II) Module fbdevhw: vendor="X.Org Foundation"
[    17.115] 	compiled for 1.20.4, module version = 0.0.2
[    17.116] 	ABI class: X.Org Video Driver, version 24.0
[    17.116] (II) FBTURBO(0): using /dev/fb0
[    17.116] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[    17.117] (II) FBTURBO(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[    17.117] (==) FBTURBO(0): Depth 24, (==) framebuffer bpp 32
[    17.117] (==) FBTURBO(0): RGB weight 888
[    17.117] (==) FBTURBO(0): Default visual is TrueColor
[    17.117] (==) FBTURBO(0): Using gamma correction (1.0, 1.0, 1.0)
[    17.117] (II) FBTURBO(0): hardware: BCM2708 FB (video memory: 1200kB)
[    17.117] (DB) xf86MergeOutputClassOptions unsupported bus type 0
[    17.117] (**) FBTURBO(0): Option "fbdev" "/dev/fb0"
[    17.117] (**) FBTURBO(0): Option "SwapbuffersWait" "true"
[    17.118] (II) FBTURBO(0): processor: Unknown
[    17.118] (II) FBTURBO(0): checking modes against framebuffer device...
[    17.118] (II) FBTURBO(0): checking modes against monitor...
[    17.118] (II) FBTURBO(0): Virtual size is 640x480 (pitch 640)
[    17.118] (**) FBTURBO(0):  Built-in mode "current"
[    17.119] (==) FBTURBO(0): DPI set to (96, 96)
[    17.119] (II) Loading sub module "fb"
[    17.119] (II) LoadModule: "fb"
[    17.119] (II) Loading /usr/lib/xorg/modules/libfb.so
[    17.144] (II) Module fb: vendor="X.Org Foundation"
[    17.145] 	compiled for 1.20.4, module version = 1.0.0
[    17.145] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    17.217] (II) FBTURBO(0): using backing store heuristics
[    17.238] (II) FBTURBO(0): can't load 'g2d_23' kernel module
[    17.238] (II) FBTURBO(0): failed to enable the use of sunxi display controller
[    17.238] (II) FBTURBO(0): No sunxi-g2d hardware detected (check /dev/disp and /dev/g2d)
[    17.238] (II) FBTURBO(0): G2D hardware acceleration can't be enabled
[    17.238] (II) FBTURBO(0): enabled fbdev copyarea acceleration
[    17.239] (==) FBTURBO(0): Backing store enabled
[    17.292] (==) FBTURBO(0): DPMS enabled
[    17.292] (II) FBTURBO(0): failed to enable hardware cursor
[    17.292] (II) FBTURBO(0): no 3D acceleration because the driver has been compiled without libUMP
[    17.292] (II) FBTURBO(0): if this is wrong and needs to be fixed, please check ./configure log
[    17.300] (II) Initializing extension Generic Event Extension
[    17.302] (II) Initializing extension SHAPE
[    17.305] (II) Initializing extension MIT-SHM
[    17.307] (II) Initializing extension XInputExtension
[    17.320] (II) Initializing extension XTEST
[    17.322] (II) Initializing extension BIG-REQUESTS
[    17.324] (II) Initializing extension SYNC
[    17.329] (II) Initializing extension XKEYBOARD
[    17.332] (II) Initializing extension XC-MISC
[    17.335] (II) Initializing extension SECURITY
[    17.338] (II) Initializing extension XFIXES
[    17.340] (II) Initializing extension RENDER
[    17.343] (II) Initializing extension RANDR
[    17.348] (II) Initializing extension COMPOSITE
[    17.359] (II) Initializing extension DAMAGE
[    17.361] (II) Initializing extension MIT-SCREEN-SAVER
[    17.363] (II) Initializing extension DOUBLE-BUFFER
[    17.365] (II) Initializing extension RECORD
[    17.366] (II) Initializing extension DPMS
[    17.368] (II) Initializing extension Present
[    17.370] (II) Initializing extension DRI3
[    17.370] (II) Initializing extension X-Resource
[    17.372] (II) Initializing extension XVideo
[    17.374] (II) Initializing extension XVideo-MotionCompensation
[    17.374] (II) Initializing extension SELinux
[    17.374] (II) SELinux: Disabled on system
[    17.374] (II) Initializing extension GLX
[    17.376] (II) AIGLX: Screen 0 is not DRI2 capable
[    21.406] (II) IGLX: Loaded and initialized swrast
[    21.407] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[    21.407] (II) Initializing extension XFree86-VidModeExtension
[    21.409] (II) Initializing extension XFree86-DGA
[    21.411] (II) Initializing extension XFree86-DRI
[    21.417] (II) Initializing extension DRI2
[    21.857] (II) config/udev: Adding input device (unnamed) (/dev/input/event0)
[    21.857] (**) (unnamed): Applying InputClass "libinput keyboard catchall"
[    21.857] (II) LoadModule: "libinput"
[    21.858] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[    22.012] (II) Module libinput: vendor="X.Org Foundation"
[    22.012] 	compiled for 1.20.3, module version = 0.28.2
[    22.012] 	Module class: X.Org XInput Driver
[    22.013] 	ABI class: X.Org XInput driver, version 24.1
[    22.013] (II) Using input driver 'libinput' for '(unnamed)'
[    22.013] (**) (unnamed): always reports core events
[    22.013] (**) Option "Device" "/dev/input/event0"
[    22.013] (**) Option "_source" "server/udev"
[    22.120] (EE) client bug: Invalid path /dev/input/event0
[    22.121] (EE) libinput: (unnamed): Failed to create a device for /dev/input/event0
[    22.123] (EE) PreInit returned 2 for "(unnamed)"
[    22.124] (II) UnloadModule: "libinput"
[    22.477] (II) config/udev: Adding input device vnc-relpointer (/dev/input/mouse1)
[    22.477] (II) No input driver specified, ignoring this device.
[    22.477] (II) This device may have been added with another device file.
[    22.554] (II) config/udev: Adding input device vnc-relpointer (/dev/input/event2)
[    22.554] (**) vnc-relpointer: Applying InputClass "libinput pointer catchall"
[    22.554] (II) Using input driver 'libinput' for 'vnc-relpointer'
[    22.554] (**) vnc-relpointer: always reports core events
[    22.554] (**) Option "Device" "/dev/input/event2"
[    22.554] (**) Option "_source" "server/udev"
[    22.562] (EE) client bug: Invalid path /dev/input/event2
[    22.562] (EE) libinput: vnc-relpointer: Failed to create a device for /dev/input/event2
[    22.564] (EE) PreInit returned 2 for "vnc-relpointer"
[    22.564] (II) UnloadModule: "libinput"
[    22.648] (II) config/udev: Adding input device vnc-abspointer (/dev/input/mouse0)
[    22.648] (II) No input driver specified, ignoring this device.
[    22.648] (II) This device may have been added with another device file.
[    22.668] (II) config/udev: Adding input device vnc-keyboard (/dev/input/event0)
[    22.668] (**) vnc-keyboard: Applying InputClass "libinput keyboard catchall"
[    22.668] (II) Using input driver 'libinput' for 'vnc-keyboard'
[    22.668] (**) vnc-keyboard: always reports core events
[    22.669] (**) Option "Device" "/dev/input/event0"
[    22.669] (**) Option "_source" "server/udev"
[    22.691] (II) event0  - vnc-keyboard: is tagged by udev as: Keyboard
[    22.691] (II) event0  - vnc-keyboard: device is a keyboard
[    22.692] (II) event0  - vnc-keyboard: device removed
[    22.730] (**) Option "config_info" "udev:/sys/devices/virtual/input/input3/event0"
[    22.731] (II) XINPUT: Adding extended input device "vnc-keyboard" (type: KEYBOARD, id 6)
[    22.731] (**) Option "xkb_model" "pc105"
[    22.731] (**) Option "xkb_layout" "cn"
[    22.731] (WW) Option "xkb_variant" requires a string value
[    22.731] (WW) Option "xkb_options" requires a string value
[    22.930] (II) event0  - vnc-keyboard: is tagged by udev as: Keyboard
[    22.930] (II) event0  - vnc-keyboard: device is a keyboard
[    22.932] (II) config/udev: Adding input device (unnamed) (/dev/input/js0)
[    22.932] (II) No input driver specified, ignoring this device.
[    22.933] (II) This device may have been added with another device file.
[    22.934] (II) config/udev: Adding input device (unnamed) (/dev/input/event1)
[    22.934] (**) (unnamed): Applying InputClass "libinput pointer catchall"
[    22.934] (II) Using input driver 'libinput' for '(unnamed)'
[    22.934] (**) (unnamed): always reports core events
[    22.934] (**) Option "Device" "/dev/input/event1"
[    22.935] (**) Option "_source" "server/udev"
[    22.935] (EE) client bug: Invalid path /dev/input/event1
[    22.935] (EE) libinput: (unnamed): Failed to create a device for /dev/input/event1
[    22.935] (EE) PreInit returned 2 for "(unnamed)"
[    22.935] (II) UnloadModule: "libinput"
[    22.965] (II) config/udev: removing device vnc-keyboard
[    22.966] (II) event0  - vnc-keyboard: device removed
[    23.001] (II) UnloadModule: "libinput"
[    27.472] (II) config/udev: Adding input device vnc-abspointer (/dev/input/js0)
[    27.473] (II) No input driver specified, ignoring this device.
[    27.473] (II) This device may have been added with another device file.
[    27.513] (II) config/udev: Adding input device vnc-relpointer (/dev/input/mouse1)
[    27.513] (II) No input driver specified, ignoring this device.
[    27.513] (II) This device may have been added with another device file.
[    27.566] (II) config/udev: Adding input device vnc-abspointer (/dev/input/mouse0)
[    27.566] (II) No input driver specified, ignoring this device.
[    27.567] (II) This device may have been added with another device file.
[    27.613] (II) config/udev: Adding input device vnc-keyboard (/dev/input/event0)
[    27.613] (**) vnc-keyboard: Applying InputClass "libinput keyboard catchall"
[    27.613] (II) Using input driver 'libinput' for 'vnc-keyboard'
[    27.613] (**) vnc-keyboard: always reports core events
[    27.613] (**) Option "Device" "/dev/input/event0"
[    27.614] (**) Option "_source" "server/udev"
[    27.625] (II) event0  - vnc-keyboard: is tagged by udev as: Keyboard
[    27.625] (II) event0  - vnc-keyboard: device is a keyboard
[    27.626] (II) event0  - vnc-keyboard: device removed
[    27.670] (**) Option "config_info" "udev:/sys/devices/virtual/input/input6/event0"
[    27.670] (II) XINPUT: Adding extended input device "vnc-keyboard" (type: KEYBOARD, id 6)
[    27.670] (**) Option "xkb_model" "pc105"
[    27.670] (**) Option "xkb_layout" "cn"
[    27.670] (WW) Option "xkb_variant" requires a string value
[    27.670] (WW) Option "xkb_options" requires a string value
[    27.676] (II) event0  - vnc-keyboard: is tagged by udev as: Keyboard
[    27.676] (II) event0  - vnc-keyboard: device is a keyboard
[    27.679] (II) config/udev: Adding input device vnc-relpointer (/dev/input/event2)
[    27.679] (**) vnc-relpointer: Applying InputClass "libinput pointer catchall"
[    27.679] (II) Using input driver 'libinput' for 'vnc-relpointer'
[    27.680] (**) vnc-relpointer: always reports core events
[    27.680] (**) Option "Device" "/dev/input/event2"
[    27.680] (**) Option "_source" "server/udev"
[    27.743] (II) event2  - vnc-relpointer: is tagged by udev as: Mouse
[    27.743] (II) event2  - vnc-relpointer: device is a pointer
[    27.744] (II) event2  - vnc-relpointer: device removed
[    27.841] (**) Option "config_info" "udev:/sys/devices/virtual/input/input8/event2"
[    27.842] (II) XINPUT: Adding extended input device "vnc-relpointer" (type: MOUSE, id 7)
[    27.843] (**) Option "AccelerationScheme" "none"
[    27.844] (**) vnc-relpointer: (accel) selected scheme none/0
[    27.844] (**) vnc-relpointer: (accel) acceleration factor: 2.000
[    27.844] (**) vnc-relpointer: (accel) acceleration threshold: 4
[    27.848] (II) event2  - vnc-relpointer: is tagged by udev as: Mouse
[    27.849] (II) event2  - vnc-relpointer: device is a pointer
[    27.853] (II) config/udev: Adding input device vnc-abspointer (/dev/input/event1)
[    27.853] (**) vnc-abspointer: Applying InputClass "libinput pointer catchall"
[    27.853] (II) Using input driver 'libinput' for 'vnc-abspointer'
[    27.856] (**) vnc-abspointer: always reports core events
[    27.857] (**) Option "Device" "/dev/input/event1"
[    27.857] (**) Option "_source" "server/udev"
[    27.862] (II) event1  - vnc-abspointer: is tagged by udev as: Mouse
[    27.863] (II) event1  - vnc-abspointer: device is a pointer
[    27.864] (II) event1  - vnc-abspointer: device removed
[    27.960] (**) Option "config_info" "udev:/sys/devices/virtual/input/input7/event1"
[    27.960] (II) XINPUT: Adding extended input device "vnc-abspointer" (type: MOUSE, id 8)
[    27.961] (**) Option "AccelerationScheme" "none"
[    27.961] (**) vnc-abspointer: (accel) selected scheme none/0
[    27.961] (**) vnc-abspointer: (accel) acceleration factor: 2.000
[    27.961] (**) vnc-abspointer: (accel) acceleration threshold: 4
[    27.965] (II) event1  - vnc-abspointer: is tagged by udev as: Mouse
[    27.966] (II) event1  - vnc-abspointer: device is a pointer
[   215.803] (II) config/udev: removing device vnc-relpointer
[   215.804] (II) event2  - vnc-relpointer: device removed
[   215.873] (II) UnloadModule: "libinput"
[   215.943] (II) config/udev: removing device vnc-abspointer
[   215.944] (II) event1  - vnc-abspointer: device removed
[   215.991] (II) UnloadModule: "libinput"
[   216.134] (II) config/udev: removing device vnc-keyboard
[   216.134] (II) event0  - vnc-keyboard: device removed
[   216.201] (II) UnloadModule: "libinput"
[   625.475] (II) FBTURBO(0): FBIOBLANK: Invalid argument (Screen blanking not supported by kernel - disabling)
if I uncomment hdmi_force_hotplug=1, hdmi and vnc works fine.
after fresh install raspbian, now vnc works. But when I turn on VNC "direct capture mode", it stop work again.

drogenbob
Posts: 1
Joined: Mon Oct 15, 2012 12:05 pm

Re: After upgrade To buster Composite output stop working

Thu Jul 04, 2019 7:41 am

I had the same problem. After a fresh install of Raspbian Buster there was no composite output.
A rpi-update and reboot fixed the issue in the first place, but after completing the initial setup wizard and especially the recommended update-procedure within this wizard, the issue was the same after a reboot.
Another rpi-update was not possible (says everything is up-to-date).

The only thing that worked for me was to do another fresh install, rpi-update and skip the update-wizard.
I'm sorry that I can't provide any logs, but I needed it in a usable state as quick as possible.

jamesh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 23076
Joined: Sat Jul 30, 2011 7:41 pm

Re: After upgrade To buster Composite output stop working

Thu Jul 04, 2019 9:12 am

drogenbob wrote:
Thu Jul 04, 2019 7:41 am
I had the same problem. After a fresh install of Raspbian Buster there was no composite output.
A rpi-update and reboot fixed the issue in the first place, but after completing the initial setup wizard and especially the recommended update-procedure within this wizard, the issue was the same after a reboot.
Another rpi-update was not possible (says everything is up-to-date).

The only thing that worked for me was to do another fresh install, rpi-update and skip the update-wizard.
I'm sorry that I can't provide any logs, but I needed it in a usable state as quick as possible.
That is expected behaviour. rpi-update just pulls in a prerelease version of the firmware, whilst the Wizard uses apt update/upgrade, which has the older firmware (until it's updated with new firmware - which it will be after we are happy with it), and will overwrite the rpi-update install.
Principal Software Engineer at Raspberry Pi (Trading) Ltd.
Contrary to popular belief, humorous signatures are allowed. Here's an example...
"My grief counseller just died, luckily, he was so good, I didn't care."

klricks
Posts: 6499
Joined: Sat Jan 12, 2013 3:01 am
Location: Grants Pass, OR, USA
Contact: Website

Re: After upgrade To buster Composite output stop working

Fri Jul 12, 2019 12:46 am

Composite now works on my 3B+ after installing today's upgrade:

Code: Select all

sudo apt update
sudo apt upgrade
Unless specified otherwise my response is based on the latest and fully updated Raspbian Buster w/ Desktop OS.

maazl2
Posts: 4
Joined: Sun Jun 30, 2019 5:06 pm

Re: After upgrade To buster Composite output stop working

Fri Jul 12, 2019 8:20 pm

klricks wrote:
Fri Jul 12, 2019 12:46 am
Composite now works on my 3B+ after installing today's upgrade:

Code: Select all

sudo apt update
sudo apt upgrade
Including video overlay with omxplayer?
For me omxplayer starts but without any video output. Same for vdr. Both use video overlay for output.

X starts correctly with graphics. But the mpv player just hogs the CPU at roughly 1 frame per second - obviously not accelerated. Sound is OK. Seems that access to the video decoder hardware is still broken.

Return to “Raspbian”