IRC channel logs
2024-10-27.log
back to list of logs
<almuhs>i've just found a new game which works in Hurd: freeciv <almuhs>meanwhile, compiling wesnoth, i have this error <almuhs>/usr/include/boost/asio/signal_set_base.hpp:66:21: error: ‘SA_NOCLDWAIT’ was not declared in this scope; did you mean ‘SA_NOCLDSTOP’? <almuhs> 66 | no_child_wait = BOOST_ASIO_OS_DEF(SA_NOCLDWAIT), <damo22>hmm i think gfx console is working 100% <damo22>somehow the console isnt being configured to maximum dimension <almuhs>i use xrandr to change the xorg resolution <almuhs>but i don't know how to change the console resolution <damo22>no i mean i wrote a gfx console driver for hurd console <damo22>something is configuring the console to be 80x25 <damo22>/bin/console with -d vga now has framebuffer support <almuhs>i think that this is necessary to a future hardware acceleration <damo22>its needed so we have a console when EGA text mode is not set as the video mode <damo22>because there is no graphical console <almuhs>Xorg can a framebuffer driver. Maybe you can connect it to your driver <damo22>the framebuffer can be reused from grub <damo22>but vesa can pass through the existing mode <damo22>so no modesetting needs to occur <almuhs>i refered to package xserver-xorg-video-fbdev, which currently doesn't works <damo22>coreboot sets up the intel gpu as a framebuffer and uses seabios which has SeaVGABIOS : that exposes the existing framebuffer as a VESA device <damo22>but now i have reused the grub framebuffer in multiboot table to pass through to hurd console <almuhs>i have researched about opengl bug. I found that, some years ago, there was some games which showed the same error than we have now in wesnoth and others <damo22>so the steps are coreboot -> gfxinit -> seavga VESA -> grub -> X or hurd console <almuhs>maybe it's necessary to compile the games with a specific flag? <damo22>software rasteriser driver for opengl <damo22>there may be a way to force that mode <almuhs>but, why it works with some games but not with others? <almuhs>i tried to forced OpenGL indirect, but then the DE doesn't boots <damo22>you can force it inside X terminal <almuhs>pasteboard doesn't works, so I'm searching how to see the image <almuhs>Xlib: sequence lost ... and a failure in X_GlxIsDirect <damo22>then you can pipe commands into | pastebinit to paste it to paste.debian <damo22>wow my console works! startx and then kill the xserver returns to graphical console! <almuhs>i had to remember how to redirect error output using a pipe <almuhs>with verbose options I get the same <damo22>ok so you need to enable indirect glx <almuhs>i tried to enable in xorg.conf, but then the DE didn't start <almuhs>Section "ServerFlags" Option "AllowIndirectGLX" "on" Option "IndirectGLX" "on" EndSection <almuhs>i don't know how to set in the console <damo22>i think the correct flag is +iglx <almuhs>but, where can i apply this flag? <damo22>(II) IGLX: Loaded and initialized swrast <damo22>(II) GLX: Initialized DRISWRAST GL provider for screen 0 <almuhs>in anywhere i have to indicate the DE <almuhs>or i have to set a value in xorg.conf <almuhs>now Xorg is broken. Even don't boot with startx <almuhs>this afternoon i got the same, but i don't remember how i solved it <damo22>its not broken, it is on but no drawing is occurring <damo22>21103 frames in 5.1 seconds = 4145.972 FPS <damo22>16280 frames in 5.0 seconds = 3256.000 FPS <damo22>but it doesnt appear on the screen <almuhs>so, where can be the problem now? <almuhs>now the games doesn't show glx error, but due to i can only run the command from ssh, i can't see in the screen <almuhs>pruebas@debian-hurd:~$ glxinfo -display :0 <almuhs>Xlib: sequence lost (0x10014 > 0x16) in reply type 0x0! <almuhs>Xlib: sequence lost (0x10019 > 0x1b) in reply type 0x0! <almuhs>Xlib: sequence lost (0x1001e > 0x20) in reply type 0x0! <almuhs>Xlib: sequence lost (0x10023 > 0x25) in reply type 0x0! <almuhs>Xlib: sequence lost (0x10028 > 0x2a) in reply type 0x0! <almuhs>direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose) <almuhs>Xorg is fixed, but we need to fix the DE configuration to support it <damo22>yeah so the game is working but its not displaying anything... <almuhs>yeah. because i can get a menu or terminal in the desktop <almuhs>i don't know if, from ssh, i can redirect the image to the display <almuhs>yes, i use that to start openbox <almuhs>but, if i enable indirect, openbox doesn't load <damo22>it shouldnt need anything to write to the framebuffer, just its address and w h <almuhs>but not today: 6:35 AM in Spain, i have to go sleep <damo22>#0 __strlen_sse2_bsf () at ../sysdeps/i386/i686/multiarch/strlen-sse2-bsf.S:49 <damo22>#1 0x01be6d9a in ?? () from /lib/i386-gnu/libxkbcommon.so.0 <damo22>#2 0x01be8c1f in xkb_keymap_mod_get_index () from /lib/i386-gnu/libxkbcommon.so.0 <damo22>#3 0x01bea9d2 in xkb_state_mod_names_are_active () from /lib/i386-gnu/libxkbcommon.so.0 <damo22>#4 0x01bc1c3b in execute_action (keycode=107) at ../../console-client/xkb/xkb.c:118 <damo22>when i press delete key i get segfault <damo22>youpi: i think i found a bug in libxkbcommon0 state.c: <damo22> const char *str = va_arg(ap, const char *); <damo22> idx = xkb_keymap_mod_get_index(state->keymap, str); <damo22>somehow str == 0x0, but it does not break, it continues to call xkb_keymap_mod_get_index with a NULL str <damo22>process_keypress_event (keycode_t keycode) <azert>damo22: did you fix the 80x25 problem? On vga I think it is hardcoded define VGA_DISP_WIDTH, that should be a variable <azert>Also, do you display the mouse pointer? <damo22>i did make the VGA_DISP_WIDTH detected <damo22>but something else is restricting the width and height <damo22>azert: is it legitimate to pass "blah" as a vararg? <azert>I don’t understand the question <azert>vararg is syntactic sugar for passing as many parameters as one wants <damo22>xkb_state_mod_names_are_active(struct xkb_state *state, enum xkb_state_component type, enum xkb_state_match match, ...) <damo22>the 4th argument is a const string <azert>Do you mean is it legitimate to pass a string literal as a vararg? <azert>That would be passing a pointer <damo22>its strange because the pointer is NULL <damo22> const char *str = va_arg(ap, const char *); <damo22> idx = xkb_keymap_mod_get_index(state->keymap, str); <azert>It’s probably gdb that is confused <damo22>i dont think it is, its definitely calling the xkb function with a null pointer <azert>Can you check the stack directly? <damo22>actually, how do i inspect the 4th arg <damo22>#3 0x01bea9d2 in xkb_state_mod_names_are_active (state=0x2003af10, type=XKB_STATE_MODS_EFFECTIVE, match=XKB_STATE_MATCH_ALL) <azert>x86 passes them all on the stack <damo22>but its supposed to be a pointer to a const string <azert>When you declare a literal string on the stack, it may be not a pointer <azert>Try adding an explicit char* = string in the caller <azert>So you pass the actual pointer <damo22>i worked hard on this to get it over the line and mailed in, i actually go back to work tomorrow, ive been on holiday