#archlinux32 | Logs for 2023-09-06

[01:01:32] -!- titus_livius has joined #archlinux32
[01:01:53] -!- titus_livius has joined #archlinux32
[01:02:13] -!- titus_livius has joined #archlinux32
[01:02:52] -!- mvchtz has joined #archlinux32
[10:56:14] -!- zxrom has joined #archlinux32
[11:15:03] -!- GNUtoo has quit [Read error: Connection reset by peer]
[11:15:03] -!- drathir_tor has quit [Remote host closed the connection]
[11:15:28] -!- GNUtoo has joined #archlinux32
[11:30:28] -!- drathir_tor has joined #archlinux32
[14:46:34] -!- zxrom has quit [Remote host closed the connection]
[14:46:59] -!- zxrom has joined #archlinux32
[17:31:07] -!- mavica has joined #archlinux32
[17:31:41] <mavica> greets from a thinkpad T42
[17:59:50] <mavica> are the vertex glitches here anything i can do about, or are the R100 drivers simply that way, or is my hardware bad? xf86-video-ati and mesa-amber: http://netizen.club
[18:01:34] <mavica> no gpu errors in dmesg or xorg log as far as i can see... DRI is being enabled properly
[18:03:46] <KitsuWhooa> Mesa amber works? Huh
[18:03:55] <mavica> haha
[18:04:08] <mavica> i know i'm trying to milk a rock over here :)
[18:04:23] <KitsuWhooa> Last I checked it wouldn't load because it depended on a long gone llvm
[18:04:35] <KitsuWhooa> And nah, this is what this channel is all about
[18:04:48] <KitsuWhooa> It looks like something probably broke down the line
[18:04:53] <mavica> well, it works insofar as ... loading and running, mainly
[18:05:08] <mavica> some, not all, gl xscreensavers crash
[18:05:32] <mavica> particularly flurry, which works absolutely fine and smooth for a few seconds... then stumbles into a SIGSEGV or a SIGABORT
[18:05:37] <KitsuWhooa> I assume forcing software rendering for glxgears works fine
[18:05:58] <mavica> yes, albeit very slow
[18:06:05] <KitsuWhooa> Maybe check Xorg.log too for anything interesting
[18:06:22] <mavica> no errors or even warnings in xorg log, everything looks smooth as butter over there...
[18:06:44] <KitsuWhooa> I think you might have to try going back versions to see at what point it worked and bisect
[18:07:40] <mavica> i'm an arch newbie (debian/ubuntu is what i mainly used), for the life of me i couldn't find how to find older versions of a package... pacman only shows me latest
[18:08:29] <girls> mavica: that is by design
[18:08:45] <girls> you are not supposed to install older packages, if you really need to, there is the archive
[18:08:57] <girls> but then you really leave support-land :D
[18:09:10] <KitsuWhooa> You usually end up building stuff yourself from the PKGBUILD
[18:09:16] <KitsuWhooa> Which takes forever on an old machine :p
[18:09:17] <mavica> i can't imagine there's a lot of support left if i'm already using mesa-amber
[18:09:40] <mavica> hey... i compiled windowmaker from source, heh (much smaller than mesa, of course)
[18:09:48] <KitsuWhooa> Oooh
[18:10:27] <KitsuWhooa> I've been meaning to try it
[18:10:36] <KitsuWhooa> It definitely looks really nice
[18:10:57] <mavica> works well on old machines
[18:11:00] <KitsuWhooa> But going back, maybe you can use gdb and / or coredumpctl to see where the segvs and abrts come from
[18:11:37] <mavica> hmm... i'm really not experienced in any of that (and i'm not sure how to run flurry directly other than thru xscreensaver)
[18:12:08] <mavica> flurry is the only thing i've seen crash, others either run fine or show similar vertex issues
[18:12:21] <mavica> raver hoop, which is a much newer jwz screensaver than flurry, runs fine...
[18:12:24] <KitsuWhooa> Systemd-coredump should collect a dump which you can then later inspect with gdb
[18:12:39] <KitsuWhooa> I suspect the issue is in mesa though
[18:12:55] <mavica> yeah, the way some things run fine, i think there's some gl mode or something that's glitched
[18:13:15] <KitsuWhooa> Oh. I guess check the gpu opengl version :p
[18:13:26] <KitsuWhooa> Glxgears should work no matter what though
[18:13:31] <mavica> for r100? it's like, gl 1.2 or something haha
[18:13:41] <KitsuWhooa> It did on OpenGL 1.2 on my Savage IX
[18:16:03] <KitsuWhooa> Actually. Wasn't DRI1 removed from the kernel?
[18:16:41] <mavica> i think i did see something that dri1 is disabled, but it loads dri2 in my machine
[18:17:01] <mavica> whether that's a good thing or not for R100... not sure
[18:19:10] <mavica> not a complete dealbreaker though, without a fully functioning GL i can still browse with netsurf and watch NSV streams :D
[18:19:21] <mavica> i'd like to fix this, if possible, but at least this laptop still has use
[18:20:34] <KitsuWhooa> Hmmm
[18:22:42] <KitsuWhooa> Yeah. I think your best bet is to try to build older versions of mesa, see if it works in any of them, and then do a bisect so that someone who knows more about how any of this works might have a chance at fixing it
[18:22:56] <KitsuWhooa> Unless of course you dig into graphics programming, which would be even better :p
[18:23:05] <mavica> haha, i wish, not smart enough for that
[18:23:21] <KitsuWhooa> I don't think it's a kernel issue but it might be worth trying an LTS kernel (and maybe an older one in general)
[18:23:40] <girls> downgrading kernels is a safe bet
[18:24:00] <girls> in the sense, that you won't break much
[18:24:00] <mavica> can you point me at some info how exactly to do that? i've just been following the arch wiki so far
[18:24:28] <girls> well, there's https://archive.archlinux32.org where you find older packages
[18:24:30] <phrik> Title: Index of / (at archive.archlinux32.org)
[18:25:08] * girls are amazed, that the archiving scripts did not break and are happily working
[18:25:58] <girls> the structure and usage is similar to what is described in the archlinux wiki
[18:25:59] <girls> https://archive.archlinux32.org
[18:26:00] <phrik> Title: Index of / (at archive.archlinux32.org)
[18:26:04] <girls> https://wiki.archlinux.org
[18:26:05] <phrik> Title: Arch Linux Archive - ArchWiki (at wiki.archlinux.org)
[18:26:11] <girls> sry, the second link is the right one
[18:26:31] <girls> though, you obviously have to change the url ;)
[18:26:41] <mavica> will take a look and try an LTS kernel, failing that i'll see about older mesa-amber packages
[18:27:20] <mavica> i did see people commented on issues in 21.3.x.. but they claimed it was fixed in 21.3.6 and mesa-amber is currently 21.3.9 on my machine
[18:27:39] <KitsuWhooa> Installing older mesa amber packages will most likely break things
[18:27:48] <KitsuWhooa> This needing to build it yourself
[18:28:04] <KitsuWhooa> Because the older mesa packages will depend on older llvm which won't be found on your system
[18:28:17] <KitsuWhooa> A system upgrade will of course fix it again
[18:28:29] <KitsuWhooa> But it's something to keep in mind about rolling release distributions
[18:44:33] <mavica> hmm https://cateee.net
[18:44:33] <phrik> Title: Linux Kernel Driver DataBase: CONFIG_DRM_LEGACY: Enable legacy drivers (DANGEROUS) (at cateee.net)
[18:46:09] <mavica> seems like this affects other cards that aren't radeon though
[19:48:06] mavica is now known as mavicaway
[19:50:45] mavicaway is now known as mavica
[19:51:10] <mavica> installed and rebooted into linux-lts... now radeon no longer has direct rendering and mesa is sw only
[19:53:47] <sL1pKn07> same here with i915+mesa amber. linux mainline black screen (fails modesetting). linux-lts works. wayland and xorg (this last if install xf86-video-intel)
[19:54:54] <sL1pKn07> sw rendering aparently
[19:55:18] <mavica> the -lts is 5.15.90-1.0-lts, the one i was on 6.1.12-arch1-1.0 had DRI2 working but GL was glitchy
[19:56:04] <sL1pKn07> for me, with 6.x need set 'nomodesetting' to work
[19:56:26] <mavica> on 5.15 AIGLX says screen 0 is not DRI2 capable - xorg's website says R100 has DRI2 support
[19:56:34] <mavica> so, i'm not sure what i did wrong
[19:58:48] <mavica> dmesg says radeon kernel modesetting is enabled
[20:13:59] mavica is now known as mavicaway
[20:18:24] mavicaway is now known as mavica
[20:18:34] <mavica> and booting back into mainline dri2 enables without problems
[20:18:39] <mavica> not sure if i'm missing a package or what
[20:49:48] mavica is now known as mavicaway
[21:08:37] mavicaway is now known as mavica
[21:08:59] <mavica> my kingdom for a decent set of fonts with pixel hinting that aren't only dejavu sans
[21:36:55] mavica is now known as mavicaway
[22:06:01] mavicaway is now known as mavica
[22:07:03] <mavica> i have an interesting issue... my keyboard volume control _does_ work. but i cannot for the life of me see any value changes in pipewire or alsa. so i can change the volume with the keyboard buttons, but i have no idea what it's changing if at all on the OS level
[22:07:29] <mavica> meanwhile alsamixer does work as well, so both things affect my audio's volume