Robin
many thanks, @seaken64 for your answers and all the others for your explanation. My “fu” in understanding Engish expressions has grown a wee bit again :), as well as my antiX-fu.
For sure I had read the sources you had linked to before asking here, as well as many other pages found on the internet dealing with the 304 legacy driver on debian buster based systems. Allways finding instructions “do this and that”.
But let my centre the patches I mentioned. Following the course of action you observed while installing the driver (which isn’t that much different from the way I performed as it seems to be at first glance) I’m quite sure you don’t have the patches applied at all. You obviously have simply installed the version as present in antiX 17.4.1 from stretch repostitory in your 19.3 and set the packages to “hold”. So I really wonder what are the patches good for, and whether you observe any malefunction.
I can state at least, that the antiX 19.3 system runs rock stable and also fast now on this noteboook (with nvidia go 6600 GPU). So once I’ve tested everything I need for everyday usage I’ll step over from 17.4.1 finally.
(The vdpau1 stuff is probably a multimedia thing, used by spaceFM file manager mandatory for some cloudy reason, and I was able to sort this out by properly reinstalling the correspondent lib simply)
Anybody around who can tell us what these patches are good for (and whether seaken64 should better apply them also)?
so long
Robin
- This reply was modified 5 years, 5 months ago by Robin.
Windows is like a submarine. Open a window and serious problems will start.