Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.os.linux.ubuntu    |    I preferred Xubuntu, seemed a bit faster    |    134,474 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 134,263 of 134,474    |
|    Paul to Paul    |
|    Re: Well that was interesting    |
|    31 Mar 25 04:56:14    |
      From: nospam@needed.invalid              On Mon, 3/31/2025 4:39 AM, Paul wrote:       > On Mon, 3/31/2025 3:27 AM, Davey wrote:       >> Booted up this morning, Ubuntu 22.04, In was using Firefox last night       >> until I went to bed. This morning, all I could get was the spinning       >> wheel, then nothing. Repeatedly.       >> Tried 'firefox' from the command line, was told it didn't exist, but       >> could be installed by 'sudo apt install firefox'.       >> So what happened to the previous version?       >> It installed firefox snapd, and luckily, all my previous tabs are still       >> there.       >> But the terminal shows unhappiness:       >> 08:15:47.118: Not loading module "atk-bridge": The functionality is       >> provided by GTK natively. Please try to not load it. libva info: VA-API       >> version 1.20.0 libva info: Trying to open       >> /snap/firefox/5917/gnome-platform/usr/lib/x86_64-linux-gnu/dr       /iHD_drv_video.so       >> libva info: Found init function __vaDriverInit_1_20 libva info:       >> va_openDriver() returns 0 ^CExiting due to channel error.       >> Exiting due to channel error.       >> Exiting due to channel error.       >> Exiting due to channel error.       >> Exiting due to channel error.       >>       >> It did not finish the installation on its own, it left it hanging at       >> 'Exiting due to channel error'.The 'unhappiness' means nothing to me.       >> Channel error? Who he?       >>       >       > It could be that the line:       >       > /snap/firefox/5917/gnome-platform/usr/lib/x86_64-linux-gnu/dri       iHD_drv_video.so       >       > is erroneous. The software doing that, may be trying iHD first, in preference       > to i965. Something like this before running it, may cause the driver       > logic to stop trying iHD at all, and trying the driver your hardware       > really uses.       >       > export LIBVA_DRIVER_NAME=i965       >       > A person doing that, was getting this from inxi -F. And in their       > opinion, the i965 would be a better choice than iHD.       >       > Graphics:       > Device-1: Intel 3rd Gen Core processor Graphics vendor: Hewlett-Packard       > driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0166       > Display: x11 server: X.Org 1.20.9 compositor: compton driver: intel       > unloaded: modesetting alternate: fbdev,vesa display ID: :0.0 screens: 1       > Screen-1: 0 s-res: 1366x768 s-dpi: 99 s-size: 352x198mm (13.9x7.8")       > s-diag: 404mm (15.9")       > Monitor-1: LVDS1 res: 1366x768 hz: 60 dpi: 112 size: 310x170mm (12.2x6.7")       > diag: 354mm (13.9")       > OpenGL: renderer: Mesa DRI Intel HD Graphics 4000 (IVB GT2)       > v: 4.2 Mesa 20.1.8 compat-v: 3.0 direct render: Yes       >       > What is supposed to happen, apparently, is some piece of code tries       > iHD first, and when that fails, it is supposed to try i965. Doing the       > Export above, tries to get it to use the second one immediately.       >       > *******       >       > At some previous point in time, hardware acceleration was broken,       > and Firefox users frequently had to find some preference (Configuration       Editor?)       > to turn off hardware acceleration. Then it should stop trying for things       > like the item above. If you can't get Firefox open, you can look for       > prefs.js and edit with a text editor (that's the file that corresponds       > to Configuration Editor).       >       > The reason you might want it to use vaapi, is to reduce the loading on       > the CPU, when playing a video. It's really hard on the CPU, to have       > all the graphics operations go to fallback code. You need like a quad core,       > to keep up.       >       > Paul       >              This example, shows what happens when the graphics hardware is too new.       At least we get to see the calls being made, in this example.              https://discourse.ubuntu.com/t/problems-with-intel-iris-xe-gpu-h       rdware-video-acceleration-in-22-04/34849              $ vainfo       libva info: VA-API version 1.14.0       libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so       libva info: Found init function __vaDriverInit_1_14       libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed       libva info: va_openDriver() returns 1       libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so       libva info: Found init function __vaDriverInit_1_10       libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed       libva info: va_openDriver() returns -1       vaInitialize failed with error code -1 (unknown libva error),exit               Paul              --- SoupGate-DOS v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca