Jump to content
Read the Funtoo Newsletter: Summer 2023 ×

onli

Members
  • Posts

    38
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by onli

  1. Hey, not sure about this at all, but this might be a dbus error. Is dbus working in general? If you are using a Window Manager, are you wrapping its launch script with dbus-launch?

     

    I'm using dunst on my Funtoo desktop, so in general it can work.

     

    Edit: Seeing your log only know it seems like dbus is indeed running and I'm on the wrong track.

  2. Since the last update, whenever I see a video it gets flickery. That is not the usual flicker where it very shortly fades to black or something, no, it gets stuck. A small portion of the video loops back and forth in abrupt intervals. Actually looks kind of funny.

     

    I'm using a Hd 7950, FF 50.0, glxinfo says:

    Extended renderer info (GLX_MESA_query_renderer):
        Vendor: X.Org (0x1002)
        Device: AMD TAHITI (DRM 2.43.0 / 4.5.2-1, LLVM 3.8.1) (0x679a)
        Version: 12.0.3
        Accelerated: yes
        Video memory: 3072MB
        Unified memory: no
        Preferred profile: core (0x1)
        Max core profile version: 4.1
        Max compat profile version: 3.0
        Max GLES1 profile version: 1.1
        Max GLES[23] profile version: 3.0
    OpenGL vendor string: X.Org
    OpenGL renderer string: Gallium 0.4 on AMD TAHITI (DRM 2.43.0 / 4.5.2-1, LLVM 3.8.1)
    OpenGL core profile version string: 4.1 (Core Profile) Mesa 12.0.3

    I think that should be the relevant info, but please just say if something is missing, I'd add it.

     

    I have no idea how to debug that and found no similar bug, does maybe someone have an idea how to tackle this one?

  3. A kernel upgrade seems to have solved this. I used the recommended debian-sources before, which set me on 3.19.3. Now funtoo runs with debian-sources 4.2.6 from the masked version, and since then I had no freeze despite trying to provoke it. Still a bit early to be 100% sure, but I'm at 99%, so I'll call it solved already.

     

    Putting this in a separate post in the hope I can mark it as solved this way.

  4. I don't think so. It states the contrary in https://wiki.gentoo.org/wiki/Radeon#Driver:

    Portage uses the VIDEO_CARDS variable for enabling support for various graphics cards. Setting VIDEO_CARDS to the value of radeon (see the feature matrix) will pull in the correct driver:

    FILE /etc/portage/make.conf
    
    VIDEO_CARDS="radeon"

     

    radeonsi gets only mentioned in the feature matrix, where for the older cards it is stuff like r600 that would get included automatically, wouldn't it?
  5. I described in http://forums.funtoo.org/topic/905-installing-x-with-radeon-driver-lead-to-llvmpiped-slow-x/that I had to enable the radeonsi driver. Before, I already used the desktop for several hours and it was stable (but too slow). It is not the only thing that changed though, still in the process of installing what is needed and finding my way around. That is getting hard: I'm experiencing complete system freezes that take down the whole system. The only thing I can do then is to use the magic sysrec keys to make a emergency remount and then reboot.

     

    The last line in the log is this:

    Mar 12 23:35:59 [kernel] [ 4352.046372] radeon 0000:01:00.0: bo ffff8800736e6400 va 0x000000de0e conflict with (bo ffff880288729000 0x000000de10 0x000000de12)

    But I found nothing with that that would help me.

     

    I'll of course provide whatever files and information that are necessary. Would be very happy about suggestions what to do now. Thanks in advance, and sorry for writing this a bit rushed, I guess it is obvious why ;)

     

    Edit: It might be related to firefox. I realized that all crashes happen when using FF. Strange enough, hardware-acceleration on or off changes nothing, I would've expected the error to be there. I installed Qupzilla, used this a while and until now saw no further crashes ? though they might still appear. Qupzilla sadly has rendering issues, I'm compiling chromium now? Would still appreciate any hints and tips how to workaround, properly debug and report this.

     

    Edit2: It's not firefox alone, it's GTK. All GTK programs I tested cause these freezes ? Firefox, geany and pinentry-gnome. I thought that chromium was an anomaly, but no, they forked GTK (Aura?) with the focus on how the gpu rendering is done, which explains why that works.

  6. I have a Radeon 7950. I think my question is whether it is a known bug, just something I did wrong or something I should report elsewhere?

     

    Following the installation doc in the wiki, I added radeon as VIDEO_CARD to my make.conf. When later installing X, I had to add glamor. When X then started it claimed to have DRI, but did not use the radeon driver but rather the mesa llvmpipe solution, which is as far as I udnerstand only cpu powered? In any case, it was unbearably slow. I then stumbled upon http://forums.funtoo.org/topic/850-cant-start-x-as-a-regular-user/ because If ound the same debug output when starting X:

    gbm: failed to open any driver (search paths /usr/lib64/dri)
    gbm: Last dlopen error: /usr/lib64/dri/radeonsi_dri.so: cannot open shared object file: No such file or directory
    failed to load driver: radeonsi
    EGL_MESA_drm_image required.

    Note that the xorg.0.log did not contain that error.

     

    The solution was to add radeonsi to VIDEO_CARD and to let emerge rebuild with --newuse.

×
×
  • Create New...