#archlinux32 | Logs for 2022-08-06

Back
[00:02:16] -!- jonathon has quit [Quit: No, you]
[00:05:49] -!- jonathon has joined #archlinux32
[01:52:59] -!- GNUtoo has quit [Remote host closed the connection]
[01:53:25] -!- GNUtoo has joined #archlinux32
[01:54:58] -!- drathir_tor has quit [Read error: Connection reset by peer]
[01:55:33] -!- drathir_tor has joined #archlinux32
[01:57:52] -!- GNUtoo has quit [Remote host closed the connection]
[01:58:27] -!- GNUtoo has joined #archlinux32
[03:03:42] -!- drathir_tor has quit [Remote host closed the connection]
[03:04:13] -!- drathir_tor has joined #archlinux32
[03:17:38] -!- drathir_tor has quit [Remote host closed the connection]
[03:18:02] -!- drathir_tor has joined #archlinux32
[03:34:50] -!- sunshavi has quit [Ping timeout: 255 seconds]
[04:05:26] -!- ejjdhfjsu has joined #archlinux32
[04:56:00] <KillerWasp> hello, i'm try read the PKGBUILD files used in archlinux32, but all jump to archlinux, which's not for 32 bits processors:
[04:56:12] <KillerWasp> http://archlinux32.org
[04:56:13] <phrik> Title: Arch Linux 32 - dumb 2.0.3-3.2 (pentium4) (at archlinux32.org)
[04:56:18] <KillerWasp> https://github.com
[04:56:44] <KillerWasp> arch=(x86_64)
[05:18:59] -!- sunshavi has joined #archlinux32
[06:59:55] <KillerWasp> hello
[06:59:58] <KillerWasp> $ glxinfo
[06:59:58] <KillerWasp> name of display: :0
[06:59:58] <KillerWasp> Error: couldn't find RGB GLX visual or fbconfig
[07:00:11] <KillerWasp> i don't understand what happened with mesa (or opengl)
[07:00:29] <KillerWasp> something are broken
[07:03:09] <KillerWasp> i guess is xf86-video-vesa
[07:03:48] <KillerWasp> or xorg-xwayland with wayland
[08:15:06] <KillerWasp> anyone here can open and show "glxinfo"? from mesa-utils
[08:15:15] <KillerWasp> i get this:
[08:15:16] <KillerWasp> name of display: :0
[08:15:16] <KillerWasp> Error: couldn't find RGB GLX visual or fbconfig
[08:25:06] <bill-auger> is that causing any real problem? - eg: does glxgears work?
[08:31:24] <KillerWasp> bill-auger: yes, i give the error a line before that you. :/
[08:32:24] <KillerWasp> and for glxgears: Error: couldn't get an RGB, Double-buffered visual
[08:33:11] <bill-auger> are you trying to so this in a VM? openGL does not work so great in VMs
[08:33:23] <KillerWasp> bill-auger: no, is all in the real system
[08:33:35] <bill-auger> then why dont you have a real video driver installed
[08:33:52] <bill-auger> if you have a real graphics card, then you dont need to use VESA
[08:33:56] <KillerWasp> bill-auger: how to check if all the files are correct installed?
[08:34:15] <KillerWasp> i guess some files are corrupted
[08:35:25] <bill-auger> most likely you should use one of xf86-video-intel xf86-video-ati xf86-video-amdgpu or xf86-video-nouveau
[08:36:56] <bill-auger> if you have the proper driver installed, check `lspci -v` to see which 'lernel driver is in use'
[08:37:53] <bill-auger> i dont know anything about wayland - that is likely adding an extra complication - i would also try using X instead
[08:38:58] <KillerWasp> bill-auger: Everything was working fine until recently, I think 1 week at least. Maybe after the last update. Something must be broken.
[08:39:19] <bill-auger> i would cjeck dmesg then
[08:39:36] <bill-auger> and the X11 log, or whatever is the wayland log file
[09:15:50] -!- oaken-source has quit [Ping timeout: 240 seconds]
[09:32:04] -!- ejjdhfjsu has quit [Remote host closed the connection]
[09:38:11] -!- abaumann has joined #archlinux32
[09:38:12] <buildmaster> Hi abaumann!
[09:38:12] <buildmaster> !rq abaumann
[09:38:13] <phrik> buildmaster: <abaumann> sane approach to dependency management: there is none, the recommended installation set is FULL
[09:39:00] <abaumann> new toolchain and glibc 2.36 break things, libarchive for instance - also upstream (enum fsconfig_command, struct mount_attr, redeclarations).
[09:39:23] <abaumann> bsd string functions breaking older packages like xdm
[09:40:58] <abaumann> mesa or mesa-amber, I think, the older the card, the better it is to install mesa-amber, as mesa start to drop old cards. I agree, using VESA is not really a good idea, those drivers break a lot lately. Wayland: I'm not even aware of that it works on Arch32..
[09:46:29] -!- rogue_cheddar has joined #archlinux32
[09:59:49] <abaumann> #include <bsd/stdlib.h>
[10:38:23] -!- abaumann has quit [Quit: leaving]
[10:49:27] -!- rogue_cheddar has quit [Quit: WeeChat 3.6]
[11:50:39] <KillerWasp> that's sad. forcing through the drivers to discard things due to lack of maintenance in the most windows style. T_T
[11:59:00] -!- GNUtoo has quit [Remote host closed the connection]
[11:59:20] -!- GNUtoo has joined #archlinux32
[12:18:20] -!- GNUtoo has quit [Remote host closed the connection]
[12:18:41] -!- GNUtoo has joined #archlinux32
[12:31:52] -!- drathir_tor has quit [Ping timeout: 268 seconds]
[12:36:28] -!- drathir_tor has joined #archlinux32
[13:02:26] <KillerWasp> journalctl now show all the logs and not the last sesion logs...
[13:17:52] -!- drathir_tor has quit [Remote host closed the connection]
[13:18:18] -!- drathir_tor has joined #archlinux32
[15:03:42] -!- jonathon has quit [Quit: No, you]
[15:04:01] -!- jonathon has joined #archlinux32
[15:04:58] -!- GNUtoo has quit [Remote host closed the connection]
[15:10:15] -!- GNUtoo has joined #archlinux32
[18:27:43] -!- drathir_tor has quit [Remote host closed the connection]
[18:28:24] -!- drathir_tor has joined #archlinux32
[19:00:42] -!- drathir_tor has quit [Remote host closed the connection]
[19:06:11] -!- drathir_tor has joined #archlinux32
[20:33:30] -!- ejjdhfjsu has joined #archlinux32
[20:52:13] -!- ejjdhfjsu has quit [Remote host closed the connection]
[23:44:45] -!- drathir_tor has quit [Remote host closed the connection]
[23:55:16] -!- drathir_tor has joined #archlinux32