On 2023-05-29 01:18, attilio semenzato wrote:
It worked! Thanks again. it's been a beautiful experience. Now I have two new questions (if this is the trend, the questions will grow exponentially :) ). 1. When I changed the compilation option CONFIG_DRM_I915 using make menuconfig, I used a search functionality given by the program. In the results of the search the option appeared in a record, and I remember that a field was "prompt". The question is: how are all these options organized and, in particular, what is the meaning of prompt? Is there a way to study the structure and the interdependence of the different options? 2. Now startx starts and I can see xterm windows as I asked in ~/.xinitrc, but I don't see any mouse pointer or, if i3 window manager is called, I see a mouse pointer in the center of the screen but I can't move it with touchpad. Where would I search the reason of this? Another kernel compilation option?
Hey, sorry for the slow response, been very busy lately. Regarding question 1, I believe the meaning of "prompt" is the text with which menuconfig prompts you for a given option. For example, the prompt for CONFIG_DRM is "Prompt: Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)" which matches the text you see in the menu. As for how they're organized, I couldn't answer that, there's probably a long history of kernel development in that answer. :) Regarding question 2, touchpads can be challenging to get working because there are many different types and interfaces. With that said, the solution here is likely similar to the original issue. That is to say, a kernel option or multiple kernel options is/are missing. Check the outputs of 'lspci' and 'lsusb' to see if there's something that looks like your touchpad there. Then maybe we can figure out which kernel options are needed. Mine, for example, is an "ETPS/2 Elantech Touchpad" as seen by the kernel/syslog and required some weird things I wouldn't have expected like CONFIG_X86_INTEL_LPSS. Hope this helps. Regards, Matt