[Bug 1140581] New: Raspberry pi touchscreen unusable
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581 Bug ID: 1140581 Summary: Raspberry pi touchscreen unusable Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs@forge.provo.novell.com Reporter: vatprc_cyq@outlook.com QA Contact: xorg-maintainer-bugs@forge.provo.novell.com Found By: --- Blocker: --- I have a WaveShare 3.5in GPIO RPi LCD(A),According wiki: HCL:Raspberry Pi3 LCD follow steps modified extraconfig.txt added dtoverlay=rpi-display ,but at reboot,the touchscreen is Blank screen only,but backlight is on. Run dmesg|grep screen output: suse-pi:~ # dmesg |grep screen [ 28.907749] ads7846 spi0.1: touchscreen, irq 79 [ 28.908498] input: ADS7846 Touchscreen as /devices/platform/soc/3f204000.spi/spi_master/spi0/spi0.1/input/input0 It show kernel is identified the touchscreen,but no display output. output: dmesg|grep gpu [ 29.844885] vc4-drm soc:gpu: bound 3f902000.hdmi (ops vc4_hdmi_ops [vc4]) [ 29.845227] vc4-drm soc:gpu: bound 3f806000.vec (ops vc4_vec_ops [vc4]) [ 29.845467] vc4-drm soc:gpu: bound 3f004000.txp (ops vc4_txp_ops [vc4]) [ 29.845586] vc4-drm soc:gpu: bound 3f400000.hvs (ops vc4_hvs_ops [vc4]) [ 29.846304] vc4-drm soc:gpu: bound 3f206000.pixelvalve (ops vc4_crtc_ops [vc4]) [ 29.846992] vc4-drm soc:gpu: bound 3f207000.pixelvalve (ops vc4_crtc_ops [vc4]) [ 29.847685] vc4-drm soc:gpu: bound 3f807000.pixelvalve (ops vc4_crtc_ops [vc4]) [ 29.871458] vc4-drm soc:gpu: bound 3fc00000.v3d (ops vc4_v3d_ops [vc4]) [ 29.874539] [drm] Initialized vc4 0.0.0 20140616 for soc:gpu on minor 0 [ 29.939148] vc4-drm soc:gpu: fb0: DRM emulated frame buffer device -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c1
--- Comment #1 from Chaoyang Qin
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c2
Stefan Dirsch
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
Matthias Brugger
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c3
Matthias Brugger
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
Matthias Brugger
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c6
Nicolas Patricio Saenz Julienne
Oh. I would be fine with Nicolas taking the bug. ;-)
It's indeed a kernel issue. All these SPI displays use a staging driver subsystem called "fbtft" which adds support for small TFT LCD displays. We do support it, but there seems to be an issue during the probe: [ 28.902379] fb_ili9341 spi0.0: Failed to request reset-gpios GPIO:-2 [ 28.902636] fb_ili9341: probe of spi0.0 failed with error -2 I'll look into it. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c7
--- Comment #7 from Nicolas Patricio Saenz Julienne
I have a WaveShare 3.5in GPIO RPi LCD(A),According wiki: HCL:Raspberry Pi3 LCD follow steps modified extraconfig.txt added dtoverlay=rpi-display ,but at reboot,the touchscreen is Blank screen only,but backlight is on.
Was that the only overlay you where using? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c8
--- Comment #8 from Chaoyang Qin
(In reply to Chaoyang Qin from comment #0)
I have a WaveShare 3.5in GPIO RPi LCD(A),According wiki: HCL:Raspberry Pi3 LCD follow steps modified extraconfig.txt added dtoverlay=rpi-display ,but at reboot,the touchscreen is Blank screen only,but backlight is on.
Was that the only overlay you where using?
dtoverlay=rpi-display According HCL... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c9
--- Comment #9 from Chaoyang Qin
(In reply to Chaoyang Qin from comment #0)
I have a WaveShare 3.5in GPIO RPi LCD(A),According wiki: HCL:Raspberry Pi3 LCD follow steps modified extraconfig.txt added dtoverlay=rpi-display ,but at reboot,the touchscreen is Blank screen only,but backlight is on.
Was that the only overlay you where using?
3 Total: 2 at config.txt is stock configuration: dtoverlay=upstream dtoverlay=upstream-aux-interrupt And..add a overlay at extraconfig.txt according HCL: dtoverlay=rpi-display -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c10
--- Comment #10 from Nicolas Patricio Saenz Julienne
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c11
--- Comment #11 from Chaoyang Qin
Chaoyang Qin, could you add 'dynamic_debug.verbose=8 dyndbg="module gpiolib* +mfp"' to the kernel command line parameters and provide the dmesg output.
How to add this? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c12
--- Comment #12 from Nicolas Patricio Saenz Julienne
(In reply to Nicolas Patricio Saenz Julienne from comment #10)
Chaoyang Qin, could you add 'dynamic_debug.verbose=8 dyndbg="module gpiolib* +mfp"' to the kernel command line parameters and provide the dmesg output.
How to add this?
Install the 'yast2-bootloader' package. If you have a graphical user interface available you can open the yast application, select the bootloader editor, navigate to "Kernel Parameters" and add the options in the "Optional Kernel Command Line Parameter" dialog. If you don't have access to a graphical interface just run 'yast2 bootloader' on your terminal, and follow the instructions above. If you can't seem to edit it yourself please provide the contents of /boot/grub2/grub2.cfg and I'll edit it myself for you. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c13
--- Comment #13 from Chaoyang Qin
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c14
--- Comment #14 from Chaoyang Qin
(In reply to Chaoyang Qin from comment #11)
(In reply to Nicolas Patricio Saenz Julienne from comment #10)
Chaoyang Qin, could you add 'dynamic_debug.verbose=8 dyndbg="module gpiolib* +mfp"' to the kernel command line parameters and provide the dmesg output.
How to add this?
Install the 'yast2-bootloader' package.
If you have a graphical user interface available you can open the yast application, select the bootloader editor, navigate to "Kernel Parameters" and add the options in the "Optional Kernel Command Line Parameter" dialog.
If you don't have access to a graphical interface just run 'yast2 bootloader' on your terminal, and follow the instructions above.
If you can't seem to edit it yourself please provide the contents of /boot/grub2/grub2.cfg and I'll edit it myself for you.
OK added in yast see attachment -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c15
--- Comment #15 from Nicolas Patricio Saenz Julienne
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c16
--- Comment #16 from Nicolas Patricio Saenz Julienne
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c17
--- Comment #17 from Chaoyang Qin
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c18
--- Comment #18 from Chaoyang Qin
Hi Chaoyang Qin I prepared a kernel with a possible fix. Could you install it and test it?
https://download.opensuse.org/repositories/home:/nsaenzjulienne:/fbtft-fix/ ARM/aarch64/kernel-default-5.1.16-1.1.g1127809.aarch64.rpm
Note that after installing it's important to make sure you select the appropiate kernel in the Grub menu, it should be similar to the name of the RPM.
Also, please provide the dmesg output. Still blank screen in all time,dmesg log uploaded.
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c19
--- Comment #19 from Nicolas Patricio Saenz Julienne
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c20
--- Comment #20 from Nicolas Patricio Saenz Julienne
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c21
--- Comment #21 from Chaoyang Qin
Chaoyang Qin, I found an issue in my previous fix, please try this kernel.
https://download.opensuse.org/repositories/home:/nsaenzjulienne:/fbtft-test/ ARM/aarch64/kernel-default-5.1.16-1.1.g2c539b1.aarch64.rpm
still unusable,dmesg attached -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c22
--- Comment #22 from Chaoyang Qin
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c23
--- Comment #23 from Nicolas Patricio Saenz Julienne
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c24
--- Comment #24 from Chaoyang Qin
Hi Chaoyang Qin please test this one:
https://download.opensuse.org/repositories/home:/nsaenzjulienne:/fbtft-test/ ARM/aarch64/kernel-default-5.1.16-2.1.g598180e.aarch64.rpm
Thanks for your patience.
Still unusable,but screen change to black,and a white strip is scanning left to right. dmesg -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c25
--- Comment #25 from Chaoyang Qin
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c26
--- Comment #26 from Nicolas Patricio Saenz Julienne
From the logs I take that the frame-buffer device was created in /dev/fb1.
I suggest testing it using one of the following options: https://github.com/notro/fbtft/wiki/Framebuffer-use If you installed a desktop GUI (xfce, kde, gnome, etc...) I suggest to try the first option (the X Server one). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c27
--- Comment #27 from Chaoyang Qin
From the logs I take that the frame-buffer device was created in /dev/fb1.
I suggest testing it using one of the following options: https://github.com/notro/fbtft/wiki/Framebuffer-use
If you installed a desktop GUI (xfce, kde, gnome, etc...) I suggest to try the first option (the X Server one).
Emmmm....unable find package install xserver-xorg-video-fbdev And after Create file: /usr/share/X11/xorg.conf.d/99-fbdev.conf with this ,and reboot system stucked at [OK]Reached target Graphical Interface. Starting Update UTMP about System Runlevel Changes ... [OK]Started Update UTMP about System Runlevel Changes. The screen is same black and white strip. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c28
--- Comment #28 from Nicolas Patricio Saenz Julienne
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c29
--- Comment #29 from Chaoyang Qin
Chaoyang Qin Undo the X11 config and try the "Image Viewer" test (https://github.com/notro/fbtft/wiki/Framebuffer-use#image-viewer)
file deleted. And this test fails: suse-pi:~ # fbi -d /dev/fb1 -T 1 -noverbose -a Mystery-100x100.jpg using "文泉驿等宽正黑,文泉驛等寬正黑,WenQuanYi Zen Hei Mono-16", pixelsize=16.67 file=/usr/share/fonts/truetype/wqy-zenhei.ttc And screen still no output. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c30
--- Comment #30 from Nicolas Patricio Saenz Julienne
(In reply to Nicolas Patricio Saenz Julienne from comment #28)
Chaoyang Qin Undo the X11 config and try the "Image Viewer" test (https://github.com/notro/fbtft/wiki/Framebuffer-use#image-viewer)
file deleted. And this test fails: suse-pi:~ # fbi -d /dev/fb1 -T 1 -noverbose -a Mystery-100x100.jpg using "文泉驿等宽正黑,文泉驛等寬正黑,WenQuanYi Zen Hei Mono-16", pixelsize=16.67 file=/usr/share/fonts/truetype/wqy-zenhei.ttc
And screen still no output.
After running the test you get no new output in dmesg right? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c31
--- Comment #31 from Chaoyang Qin
(In reply to Chaoyang Qin from comment #29)
(In reply to Nicolas Patricio Saenz Julienne from comment #28)
Chaoyang Qin Undo the X11 config and try the "Image Viewer" test (https://github.com/notro/fbtft/wiki/Framebuffer-use#image-viewer)
file deleted. And this test fails: suse-pi:~ # fbi -d /dev/fb1 -T 1 -noverbose -a Mystery-100x100.jpg using "文泉驿等宽正黑,文泉驛等寬正黑,WenQuanYi Zen Hei Mono-16", pixelsize=16.67 file=/usr/share/fonts/truetype/wqy-zenhei.ttc
And screen still no output.
After running the test you get no new output in dmesg right?
ATTACHED -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c32
--- Comment #32 from Chaoyang Qin
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c33
--- Comment #33 from Nicolas Patricio Saenz Julienne
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c34
--- Comment #34 from Nicolas Patricio Saenz Julienne
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c35
--- Comment #35 from Chaoyang Qin
Hi Chaoyang Qin, there was still a fix to be done. Keep in mind that the display driver is in the staging tree and the quality is not assured.
Please install this kernel: https://download.opensuse.org/repositories/home:/nsaenzjulienne:/fbtft-test/ ARM/aarch64/kernel-default-5.1.16-3.1.g598180e.aarch64.rpm
And use the overlay I'll attach following this message. To do so you have to: copy the file into '/boot/efi/overlays', and replace dtoverlay=rpi-display with dtoverlay=waveshare35a in your config.txt.
Screen go black ,and imageview test show load failed. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c36
--- Comment #36 from Chaoyang Qin
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c37
--- Comment #37 from Nicolas Patricio Saenz Julienne
(In reply to Nicolas Patricio Saenz Julienne from comment #33)
Hi Chaoyang Qin, there was still a fix to be done. Keep in mind that the display driver is in the staging tree and the quality is not assured.
Please install this kernel: https://download.opensuse.org/repositories/home:/nsaenzjulienne:/fbtft-test/ ARM/aarch64/kernel-default-5.1.16-3.1.g598180e.aarch64.rpm
And use the overlay I'll attach following this message. To do so you have to: copy the file into '/boot/efi/overlays', and replace dtoverlay=rpi-display with dtoverlay=waveshare35a in your config.txt.
Screen go black ,and imageview test show load failed.
Please try the X11 test: https://github.com/notro/fbtft/wiki/Framebuffer-use#x-server Apart from running startx, also try restarting the device after creating the configuration file. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c38
--- Comment #38 from Chaoyang Qin
(In reply to Chaoyang Qin from comment #35)
(In reply to Nicolas Patricio Saenz Julienne from comment #33)
Hi Chaoyang Qin, there was still a fix to be done. Keep in mind that the display driver is in the staging tree and the quality is not assured.
Please install this kernel: https://download.opensuse.org/repositories/home:/nsaenzjulienne:/fbtft-test/ ARM/aarch64/kernel-default-5.1.16-3.1.g598180e.aarch64.rpm
And use the overlay I'll attach following this message. To do so you have to: copy the file into '/boot/efi/overlays', and replace dtoverlay=rpi-display with dtoverlay=waveshare35a in your config.txt.
Screen go black ,and imageview test show load failed.
Please try the X11 test: https://github.com/notro/fbtft/wiki/Framebuffer-use#x-server
Apart from running startx, also try restarting the device after creating the configuration file.
Still unable,X server not init? dmesg output stopped at 43 sec -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c39
--- Comment #39 from Nicolas Patricio Saenz Julienne
(In reply to Nicolas Patricio Saenz Julienne from comment #37)
(In reply to Chaoyang Qin from comment #35)
(In reply to Nicolas Patricio Saenz Julienne from comment #33)
Hi Chaoyang Qin, there was still a fix to be done. Keep in mind that the display driver is in the staging tree and the quality is not assured.
Please install this kernel: https://download.opensuse.org/repositories/home:/nsaenzjulienne:/fbtft-test/ ARM/aarch64/kernel-default-5.1.16-3.1.g598180e.aarch64.rpm
And use the overlay I'll attach following this message. To do so you have to: copy the file into '/boot/efi/overlays', and replace dtoverlay=rpi-display with dtoverlay=waveshare35a in your config.txt.
Screen go black ,and imageview test show load failed.
Please try the X11 test: https://github.com/notro/fbtft/wiki/Framebuffer-use#x-server
Apart from running startx, also try restarting the device after creating the configuration file.
Still unable,X server not init? dmesg output stopped at 43 sec
Still black output? did you see a console output on the display while booting? If not, let's try something more drastic, do: cat /dev/urandom > /dev/fb1 You should see random colored pixels. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c40
--- Comment #40 from Chaoyang Qin
(In reply to Chaoyang Qin from comment #38)
(In reply to Nicolas Patricio Saenz Julienne from comment #37)
(In reply to Chaoyang Qin from comment #35)
(In reply to Nicolas Patricio Saenz Julienne from comment #33)
Hi Chaoyang Qin, there was still a fix to be done. Keep in mind that the display driver is in the staging tree and the quality is not assured.
Please install this kernel: https://download.opensuse.org/repositories/home:/nsaenzjulienne:/fbtft-test/ ARM/aarch64/kernel-default-5.1.16-3.1.g598180e.aarch64.rpm
And use the overlay I'll attach following this message. To do so you have to: copy the file into '/boot/efi/overlays', and replace dtoverlay=rpi-display with dtoverlay=waveshare35a in your config.txt.
Screen go black ,and imageview test show load failed.
Please try the X11 test: https://github.com/notro/fbtft/wiki/Framebuffer-use#x-server
Apart from running startx, also try restarting the device after creating the configuration file.
Still unable,X server not init? dmesg output stopped at 43 sec
Still black output? did you see a console output on the display while booting?
If not, let's try something more drastic, do:
cat /dev/urandom > /dev/fb1
You should see random colored pixels.
yep,see random pixels,but HDMI output also only a line is blinking after started X server output... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c41
--- Comment #41 from Chaoyang Qin
(In reply to Chaoyang Qin from comment #38)
(In reply to Nicolas Patricio Saenz Julienne from comment #37)
(In reply to Chaoyang Qin from comment #35)
(In reply to Nicolas Patricio Saenz Julienne from comment #33)
Hi Chaoyang Qin, there was still a fix to be done. Keep in mind that the display driver is in the staging tree and the quality is not assured.
Please install this kernel: https://download.opensuse.org/repositories/home:/nsaenzjulienne:/fbtft-test/ ARM/aarch64/kernel-default-5.1.16-3.1.g598180e.aarch64.rpm
And use the overlay I'll attach following this message. To do so you have to: copy the file into '/boot/efi/overlays', and replace dtoverlay=rpi-display with dtoverlay=waveshare35a in your config.txt.
Screen go black ,and imageview test show load failed.
Please try the X11 test: https://github.com/notro/fbtft/wiki/Framebuffer-use#x-server
Apart from running startx, also try restarting the device after creating the configuration file.
Still unable,X server not init? dmesg output stopped at 43 sec
Still black output? did you see a console output on the display while booting?
If not, let's try something more drastic, do:
cat /dev/urandom > /dev/fb1
You should see random colored pixels.
But.. type reboot in SSH, a while later,HDMI output restored,and showing rebooting, the 3.5 display still remain this.... new dmesg output attached Note:rm /usr/share/X11/xorg.conf.d/99-fbdev.conf and HDMI output restored normal. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c42
--- Comment #42 from Chaoyang Qin
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c43
--- Comment #43 from Nicolas Patricio Saenz Julienne
yep,see random pixels,but HDMI output also only a line is blinking after started X server output...
Could you provide the X11 logs when booting with 99-fbdev.conf? If starting manually you should see them, if not they should be in /var/log/Xorg.0.log or ~/.local/share/xorg/Xorg.0.log. Also, what GUI are you using? (xfce, gnome, kde, etc...) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c44
--- Comment #44 from Chaoyang Qin
(In reply to Chaoyang Qin from comment #40)
yep,see random pixels,but HDMI output also only a line is blinking after started X server output...
Could you provide the X11 logs when booting with 99-fbdev.conf? If starting manually you should see them, if not they should be in /var/log/Xorg.0.log or ~/.local/share/xorg/Xorg.0.log.
Also, what GUI are you using? (xfce, gnome, kde, etc...)
With xfce log attached -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c45
--- Comment #45 from Chaoyang Qin
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c47
--- Comment #47 from Chaoyang Qin
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c48
--- Comment #48 from Chaoyang Qin
Did you have the HDMI port connected while testing? If yes could you rest without it, and provide the X11 logs.
Sorry for delay... new log attached. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c49
--- Comment #49 from Nicolas Patricio Saenz Julienne
(In reply to Nicolas Patricio Saenz Julienne from comment #46)
Did you have the HDMI port connected while testing? If yes could you rest without it, and provide the X11 logs.
Sorry for delay...
No worries :)
new log attached.
Just to be clear this was with '/usr/share/X11/xorg.conf.d/99-fbdev.conf' enabled right? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c50
--- Comment #50 from Chaoyang Qin
(In reply to Chaoyang Qin from comment #48)
(In reply to Nicolas Patricio Saenz Julienne from comment #46)
Did you have the HDMI port connected while testing? If yes could you rest without it, and provide the X11 logs.
Sorry for delay...
No worries :)
new log attached.
Just to be clear this was with '/usr/share/X11/xorg.conf.d/99-fbdev.conf' enabled right?
Yep.. conf contains: suse-pi:/usr/share/X11/xorg.conf.d # cat 99-fbdev.conf Section "Device" Identifier "myfb" Driver "fbdev" Option "fbdev" "/dev/fb1" EndSection -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581#c51
--- Comment #51 from Chaoyang Qin
(In reply to Nicolas Patricio Saenz Julienne from comment #49)
(In reply to Chaoyang Qin from comment #48)
(In reply to Nicolas Patricio Saenz Julienne from comment #46)
Did you have the HDMI port connected while testing? If yes could you rest without it, and provide the X11 logs.
Sorry for delay...
No worries :)
new log attached.
Just to be clear this was with '/usr/share/X11/xorg.conf.d/99-fbdev.conf' enabled right?
Yep.. conf contains: suse-pi:/usr/share/X11/xorg.conf.d # cat 99-fbdev.conf Section "Device" Identifier "myfb" Driver "fbdev" Option "fbdev" "/dev/fb1" EndSection
Delete and recrate it New log: [ 64.551] X.Org X Server 1.20.5 X Protocol Version 11, Revision 0 [ 64.551] Build Operating System: openSUSE SUSE LINUX [ 64.551] Current Operating System: Linux suse-pi 5.1.16-3.g598180e-default #1 SMP Thu Jul 11 10:05:18 UTC 2019 (598180e) aarch64 [ 64.551] Kernel command line: BOOT_IMAGE=/boot/Image-5.1.16-3.g598180e-default root=UUID=62f6f70d-4e36-40e6-954d-da84cccad79e loglevel=3 splash=silent plymouth.enable=0 swiotlb=512 cma=300M console=ttyS0,115200n8 console=tty root=UUID=62f6f70d-4e36-40e6-954d-da84cccad79e rw dynamic_debug.verbose=8 "dyndbg=module gpiolib* +mfp" [ 64.552] Build Date: 30 May 2019 12:00:00PM [ 64.552] [ 64.552] Current version of pixman: 0.36.0 [ 64.552] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 64.552] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 64.553] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Jul 20 23:14:05 2019 [ 64.628] (==) Using config directory: "/etc/X11/xorg.conf.d" [ 64.629] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 64.658] (==) No Layout section. Using the first Screen section. [ 64.658] (==) No screen section available. Using defaults. [ 64.658] (**) |-->Screen "Default Screen Section" (0) [ 64.658] (**) | |-->Monitor "<default monitor>" [ 64.660] (==) No device specified for screen "Default Screen Section". Using the first device section listed. [ 64.660] (**) | |-->Device "myfb" [ 64.660] (**) | |-->GPUDevice "kms gfx" [ 64.660] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 64.660] (==) Automatically adding devices [ 64.660] (==) Automatically enabling devices [ 64.660] (==) Automatically adding GPU devices [ 64.660] (==) Max clients allowed: 256, resource mask: 0x1fffff [ 64.691] (WW) The directory "/usr/share/fonts/Type1/" does not exist. [ 64.691] Entry deleted from font path. [ 64.691] (WW) The directory "/usr/share/fonts/100dpi" does not exist. [ 64.691] Entry deleted from font path. [ 64.746] (WW) The directory "/usr/share/fonts/cyrillic" does not exist. [ 64.746] Entry deleted from font path. [ 64.748] (WW) The directory "/usr/share/fonts/misc/sgi" does not exist. [ 64.748] Entry deleted from font path. [ 64.750] (==) FontPath set to: /usr/share/fonts/misc:unscaled, /usr/share/fonts/75dpi:unscaled, /usr/share/fonts/ghostscript/, /usr/share/fonts/truetype/, built-ins [ 64.750] (==) ModulePath set to "/usr/lib64/xorg/modules" [ 64.750] (WW) Ignoring unrecognized extension "XFree86-DGA" [ 64.750] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 64.750] (II) Loader magic: 0xaaaab21dfce0 [ 64.750] (II) Module ABI versions: [ 64.750] X.Org ANSI C Emulation: 0.4 [ 64.750] X.Org Video Driver: 24.0 [ 64.750] X.Org XInput driver : 24.1 [ 64.750] X.Org Server Extension : 10.0 [ 64.755] (++) using VT number 7 [ 64.755] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [ 64.761] (II) xfree86: Adding drm device (/dev/dri/card0) [ 64.771] (II) no primary bus or device found [ 64.771] falling back to /sys/devices/platform/soc/soc:gpu/drm/card0 [ 64.772] (II) LoadModule: "glx" [ 64.780] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so [ 64.972] (II) Module glx: vendor="X.Org Foundation" [ 64.972] compiled for 1.20.5, module version = 1.0.0 [ 64.972] ABI class: X.Org Server Extension, version 10.0 [ 64.973] (II) LoadModule: "fbdev" [ 64.974] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so [ 64.979] (II) Module fbdev: vendor="X.Org Foundation" [ 64.979] compiled for 1.20.4, module version = 0.5.0 [ 64.979] Module class: X.Org Video Driver [ 64.979] ABI class: X.Org Video Driver, version 24.0 [ 64.979] (II) LoadModule: "modesetting" [ 64.980] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so [ 64.988] (II) Module modesetting: vendor="X.Org Foundation" [ 64.988] compiled for 1.20.5, module version = 1.20.5 [ 64.988] Module class: X.Org Video Driver [ 64.988] ABI class: X.Org Video Driver, version 24.0 [ 64.988] (II) FBDEV: driver for framebuffer: fbdev [ 64.988] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 65.018] (WW) Falling back to old probe method for fbdev [ 65.018] (II) Loading sub module "fbdevhw" [ 65.018] (II) LoadModule: "fbdevhw" [ 65.021] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so [ 65.029] (II) Module fbdevhw: vendor="X.Org Foundation" [ 65.029] compiled for 1.20.5, module version = 0.0.2 [ 65.029] ABI class: X.Org Video Driver, version 24.0 [ 65.033] (II) FBDEV(0): using /dev/fb1 [ 65.045] (II) modeset(G0): using drv /dev/dri/card0 [ 65.045] (EE) Fatal server error: [ 65.046] (EE) Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices [ 65.046] (EE) [ 65.046] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 65.046] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 65.046] (EE) [ 65.104] (EE) Server terminated with error (1). Closing log file. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
Nicolas Patricio Saenz Julienne
http://bugzilla.opensuse.org/show_bug.cgi?id=1140581
Stefan Dirsch
participants (1)
-
bugzilla_noreply@novell.com