Bug#879624: xorg: After upgrade to buster: system doesnt start x-server anymore but stop reacting
Package: xserver-xorg Followup-For: Bug #879624 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I have an Acer Aspire One D270. Graphics driver was a problem from the beginning but after sometime in 2013, the problems went away and the laptop functioned smoothly. I use a stripped down version of the Debian testing OS without any display-manager. I log into the console and use startx to start an Xmonad session. Everything was fine till linux kernel 4.13. Two weeks back, I upgraded to linux kernel 4.14.0-3. I cannot make X work under the new kernel. It works fine with the old kernel. In the new kernel, I get till the console login screen. Everything works fine in the console. However, as soon I run startx, the screen goes black with the backlight at its brightest. Nothing comes on the screen. Trying to switch to console useing Ctrl-Alt-Fn doesn't work for any n=2,3,4,5,6. The only way is to reboot. I use Ctrl-Alt-F2 followed by Ctrl-Alt-Delete. * What exactly did you do (or not do) that was effective (or ineffective)? I created an /etc/X11/xorg.conf using Xorg -configure. It crashed but it created an xorg.conf.new nevertheless. I manually set the driver to "modesetting". * What was the outcome of this action? It works sometimes after a lot of reboots. But not always. I cannot figure out if there is some pattern as the number of times it works is very few compared to the number of times it doesn't work. *** End of the template - remove these template lines *** -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Apr 24 2017 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 274 Jan 18 17:41 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller [8086:0be1] (rev 09) Xorg X server configuration file status: -rw-r--r-- 1 root root 2017 Feb 4 13:37 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: --- Section "ServerLayout" Identifier "X.org Configured" Screen 0 "Screen0" 0 0 InputDevice"Mouse0" "CorePointer" InputDevice"Keyboard0" "CoreKeyboard" EndSection Section "Files" ModulePath "/usr/lib/xorg/modules" FontPath "/usr/share/fonts/X11/misc" FontPath "/usr/share/fonts/X11/cyrillic" FontPath "/usr/share/fonts/X11/100dpi/:unscaled" FontPath "/usr/share/fonts/X11/75dpi/:unscaled" FontPath "/usr/share/fonts/X11/Type1" FontPath "/usr/share/fonts/X11/100dpi" FontPath "/usr/share/fonts/X11/75dpi" FontPath "built-ins" EndSection Section "Module" Load "glx" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/input/mice" Option "ZAxisMapping" "4 5 6 7" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName"Monitor Model" EndSection Section "Device" ### Available Driver options are:- ### Values: : integer, : float, : "True"/"False", ### : "String", : " Hz/kHz/MHz", ### : "%" ### [arg]: arg optional #Option "ShadowFB" # [] #Option "DefaultRefresh"# [] #Option "ModeSetClearScreen"# [] Identifier "Card0" Driver "modesetting" BusID "PCI:0:2:0" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor"Monitor0" SubSection "Display" Viewport 0 0 Depth 1 EndSubSection SubSection "Display" Viewport 0 0 Depth 4 EndSubSection SubSection "Display" Viewport 0 0 Depth 8 EndSubSection SubSection "Display" Viewport 0 0 Depth 15 EndSubSection SubSection "Display" Viewport 0 0 Depth 16 EndSubSection SubSection "Display" Viewport 0 0 Depth 24 EndSubSection EndSection /etc/X11/xorg.conf.d does not exist. /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 4.14.
Bug#843837: libxft-dev: Xft/Xft.h header incorrectly includes ft2build.h
Hi Graham, Sorry for the delayed reply. On Wednesday, 31 January 2018 5:23 PM, Graham Inggs wrote: > I saw this message in bug #887595 [1] and thought it would be relevant here: > > On Tue, Jan 23, 2018 at 11:56:38AM +, Hugh McMaster wrote: >> Also note that the Freetype2 developers no longer recommend using >> #include >> in source files (which was the intent of my patch). The following should be >> used instead: >> #include >> #include FT_FREETYPE_H >> >> Developers would then use either freetype-config or pkg-config to >> obtain the cflags etc. > > Hugh, do you have a reference for the above? The freetype-2.8 API reference shows this #include usage. Look at the documentation provided with libfreetype6-dev in /usr/share/doc/libfreetype6/documentation.html, particulary Tutorial #1 and Example #1. Freetype-2.9 (the most recent upstream version) also has this information. See [1] for information on freetype2's header inclusion scheme and [2] for the tutorial. [1] https://www.freetype.org/freetype2/docs/reference/ft2-header_inclusion.html [2] https://www.freetype.org/freetype2/docs/tutorial/step1.html [3] https://anonscm.debian.org/cgit/collab-maint/motif.git/tree/debian/patches/fix_ac_find_xft.patch
Bug#889483: marked as done (libegl1 package disables amdgpu direct rendering)
Your message dated Sun, 4 Feb 2018 15:31:55 +0200 with message-id <845a1caa-a251-e832-eb2a-c72fd2a6a...@debian.org> and subject line Re: Bug#889483: libegl1 package disables amdgpu direct rendering has caused the Debian Bug report #889483, regarding libegl1 package disables amdgpu direct rendering to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 889483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889483 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libegl1 Version: 1.0.0-2 The presence of this package disables 2d and 3d hardware acceleration of the Mesa amdgpu driver: [ 6.245] (EE) AMDGPU(0): eglGetDisplay() failed [ 6.245] (EE) AMDGPU(0): glamor detected, failed to initialize EGL. [ 6.452] (II) AMDGPU(0): Front buffer pitch: 7680 bytes [ 6.452] (==) AMDGPU(0): DRI3 disabled [ 6.452] (==) AMDGPU(0): Backing store enabled [ 6.452] (WW) AMDGPU(0): Direct rendering disabled [ 6.452] (II) AMDGPU(0): 2D and 3D acceleration disabled [ 6.452] (==) AMDGPU(0): DPMS enabled [ 6.452] (==) AMDGPU(0): Silken mouse enabled [ 6.453] (II) AMDGPU(0): RandR 1.2 enabled, ignore the following RandR disabled message. [ 6.489] (--) RandR disabled [ 6.491] (II) SELinux: Disabled on system [ 6.491] (II) AIGLX: Screen 0 is not DRI2 capable [ 6.491] (EE) AIGLX: reverting to software rendering [ 6.499] (II) IGLX: enabled GLX_MESA_copy_sub_buffer [ 6.500] (II) IGLX: Loaded and initialized swrast [ 6.500] (II) GLX: Initialized DRISWRAST GL provider for screen 0 Many Debian buster mesa packages can not install with Oibaf ppa Mesa packages any more, because depends versions use = instead of >=. This happened about 26.1.2018. xfce@ryzen5pc:~$ inxi -bM System:Host: ryzen5pc Kernel: 4.15.0-rc8+ x86_64 bits: 64 Desktop: Xfce 4.12.4 Distro: Debian GNU/Linux buster/sid Machine: Device: desktop Mobo: ASUSTeK model: PRIME B350M-K v: Rev X.0x serial: N/A UEFI [Legacy]: American Megatrends v: 3401 date: 12/04/2017 CPU: 6 core AMD Ryzen 5 1600 Six-Core (-MT-MCP-) speed/max: 2727/3375 MHz Graphics: Card: Advanced Micro Devices [AMD/ATI] Baffin [Polaris11] Display Server: x11 (X.Org 1.19.6 ) drivers: modesetting,ati,radeon,amdgpu (unloaded: fbdev,vesa) Resolution: 1920x1080@60.00hz OpenGL: renderer: llvmpipe (LLVM 5.0, 128 bits) version: 3.3 Mesa 17.3.3 Network: Card: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller driver: r8169 Drives:HDD Total Size: 256.1GB (66.9% used) Info: Processes: 242 Uptime: 7 min Memory: 737.0/7976.9MB --- End Message --- --- Begin Message --- On 03.02.2018 21:20, fin4478 fin4478 wrote: > Package: libegl1 > Version: 1.0.0-2 > > The presence of this package disables 2d and 3d hardware acceleration > of the Mesa amdgpu driver: > > [ 6.245] (EE) AMDGPU(0): eglGetDisplay() failed > [ 6.245] (EE) AMDGPU(0): glamor detected, failed to initialize EGL. > > [ 6.452] (II) AMDGPU(0): Front buffer pitch: 7680 bytes > [ 6.452] (==) AMDGPU(0): DRI3 disabled > [ 6.452] (==) AMDGPU(0): Backing store enabled > [ 6.452] (WW) AMDGPU(0): Direct rendering disabled > [ 6.452] (II) AMDGPU(0): 2D and 3D acceleration disabled > [ 6.452] (==) AMDGPU(0): DPMS enabled > [ 6.452] (==) AMDGPU(0): Silken mouse enabled > [ 6.453] (II) AMDGPU(0): RandR 1.2 enabled, ignore the following RandR > disabled message. [ 6.489] (--) RandR disabled > [ 6.491] (II) SELinux: Disabled on system > [ 6.491] (II) AIGLX: Screen 0 is not DRI2 capable > [ 6.491] (EE) AIGLX: reverting to software rendering > [ 6.499] (II) IGLX: enabled GLX_MESA_copy_sub_buffer > [ 6.500] (II) IGLX: Loaded and initialized swrast > [ 6.500] (II) GLX: Initialized DRISWRAST GL provider for screen 0 > > Many Debian buster mesa packages can not install with Oibaf ppa Mesa > packages any more, because depends versions use = instead of >=. This > happened about 26.1.2018. You can't mix non-glvnd mesa from a random ppa with Debian.--- End Message ---
Bug#889483: libegl1 disables amdgpu drm with Buster mesa
Reopen this bug, the log file shows that this bug is for Debian Buster Mesa.
Bug#889483: libegl1 disables amdgpu drm with Buster mesa
On 04.02.2018 15:50, fin4478 fin4478 wrote: > Reopen this bug, the log file shows that this bug is for Debian Buster > Mesa. No, you've messed up your system and it doesn't have a matching libgbm1 etc installed anymore. You need to fix it yourself.
Bug#889561: Mention what to do when xrandr lists modes that it then cannot find
Package: xserver-xorg Version: 1:7.7+19 Severity: wishlist File: /usr/share/doc/xorg/howto/use-xrandr.txt.gz X-Debbugs-Cc: Cyril Brulebois /usr/share/doc/xorg/howto/use-xrandr.txt.gz should discuss the proper thing to do when #882444 (xrandr lists modes that it then cannot find) happens.
Bug#889564: xrandr lists modes that it then cannot find
Package: libxrandr2 Version: 2:1.5.1-1 X-Debbugs-Cc: Cyril Brulebois Maybe libxrandr2 is the right place for me to report #882444 (xrandr lists modes that it then cannot find). I'm not sure.
Bug#889483: libegl1 disables amdgpu drm with Buster mesa
On 04.02.2018 17:44, fin4478 fin4478 wrote: > > You have messed my system. Too bad that there is no dssi zynfx synth in > Manjaro Linux, i would like to switch to it get rid of uhbuntu&nvidia > people. Tryin siduction next > > Arch linux user had this same bug in summer 2017, now you put it to > Debian, thank you very much fir wasting my work for several days. I just > made a public Debian testing Xfce distribution with Oipaf ppa and you > broke it and my computer. Debian switched to GLVND in August, Ubuntu will follow soon. You can't mix a non-glvnd mesa git build (from a ppa) with Debian, or you'll break it and need to fix it by hand. Is it too hard to understand?
Re: Request for newer mesa,llvm packages in stretch backports
Hi all, My (first) upload to mentors is online (@ https://mentors.debian.net/package/llvm-toolchain-5.0). Can someone sponsor me ? If it is OK, I can start the packaging of other sources and upload them. Regards, Jérémy 2018-02-01 10:50 GMT+01:00 Andreas Boll : > Hi, > > On Sun, Jan 28, 2018 at 08:37:17PM +0100, Jérémy Viès wrote: > > Hi all, > > > > I'd like to give a help. > > I backport for my own the mesa stack and its dependencies. > > Thanks for offering help! > > > > > Until mesa 17.3.2, I had no issue with the following packages, just > > recompiling the sources from sid: > > llvm-toolchain-5.0 > > libclc > > libdrm > > wayland-protocols > > libglvnd > > mesa > > > > But since a few days, at least llvm-toolchain-5.0 needs an updated quilt > > (0.63-8.2) that does not build out of the box on stretch. > > If someone knows what is the quilt update about, I can try to patch > debian > > build of llvm-toolchain to only depend on quilt from stretch. > > Yeah, I've bumped the quilt dependency in mesa-17.3.3-1. But it looks like > Gianfranco has already uploaded that quilt version to backports [1]. Thanks > Gianfranco! > > > > > I dit not tried to backport vulkan as I do not use it for now, but it > > backported straight forward at jessie time. > > > > Regards, > > Jérémy > > > > So the next step would be to find a DD for sponsoring the llvm upload. > The best way for this is to prepare and upload the backport of > llvm-toolchain-5.0 to mentors [2]. > > For the other packages we want to have the backports to be prepared in > the VCS. See also the branches for jessie-backports. I'll look into this > task. > > > Thanks, > Andreas > > [1] https://ftp-master.debian.org/backports-new.html > [2] https://mentors.debian.net/ >
