You are not logged in.
will later give the usrmerge package a test and see how it goes, like what can possibly go wrong?
Just FYI: the conversion is not reversible.
i.e. using linux - problems should be expected
No, not really.
I have an AMD card that functions perfectly under Linux thanks to the efforts of the (paid!) AMD developers who have open sourced their graphics stack (apart from the firmware) and contribute actively to Linux development.
In Windows I cannot use the open source amdgpu driver so I have to use AMDGPU-PRO instead and the performance is *terrible*, especially in respect of power consumption and temperature management. The blobby driver is shit.
Devian devs must just add it to repo
And I'm sure they will. Eventually.
Starting threads here and over at forums.debian.net will not get the attention of the NVIDIA driver Debian maintainers and it will not speed the update in any way. In particular forums.debian.net is almost entirely a user-based forum with very few Debian developers visiting.
Yes but if the ABI isn't supported then problems should be expected.
Devuan aren't going to patch the kernel to fix a problem introduced by NVIDIA. That would be ridiculous.
There are some markers for it:
https://blogs.blackberry.com/en/2022/06 … nux-threat
^ See the "Indicators of Compromise (IoCs)" section for details.
Anyway this is aimed at banks and suchlike so I don't think desktop users have to worry too much.
^ I can disable vsync in all my games under Wayland and have the framerate exceed the refresh rate. I can also screen capture with no problems. Those are the only concrete problems I can glean from that article and they're both now fixed.
Counter opinion from the original developer of wlroots (one of the three main Wayland compositors available):
Wayland Misconceptions Debunked
EDIT: and since when did having an opinion count as "shilling"? FFS... ![]()
Head_on_a_Stick wrote:The proprietary drivers are not part of the official Devuan release either.
Why? Devuan not supported any proprietary drivers!?
Because the source code is not available. The drivers are available from the non-free component of the repositories as a convenience for users but that component is not considered part of the official release.
There is also this:
[ 44.886] (II) LoadModule: "nvidia" [ 44.887] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so [ 45.134] (II) Module nvidia: vendor="NVIDIA Corporation" [ 45.134] compiled for 4.0.2, module version = 1.0.0 [ 45.134] Module class: X.Org Video Driver [ 45.134] ================ WARNING WARNING WARNING WARNING ================ [ 45.134] This server has a video driver ABI version of 25.2 that this driver does not officially support. Please check http://www.nvidia.com/ for driver updates or downgrade to an X server with a supported driver ABI. [ 45.134] =================================================================
Have you tried nouveau?
I'll get my coat...
The proprietary drivers are not part of the official Devuan release either.
This is Debian issue
Not really. Even if you are correct the proprietary drivers are not part of the official distribution.
How to fix?
Ask NVIDIA to stop being such a bunch of twats. Or buy a graphics card from a manufacturer that doesn't hate the open source community.
This is not a Devuan problem, it is an NVIDIA problem.
This install has been a rolling upgrade since at least as far back as Squeeze.
Well I've just installed a fresh chimaera system (from the netinstall with just the standard utilities) and dovecot stops and restarts normally there so perhaps you have some outdated configuration files that are causing problems.
Head_on_a_Stick wrote:I notice that systemd uses socket activation for dovecot.service, perhaps that has something to do with it.
Not sure what you're getting at here, I have no systemd anything anywhere socket activated or otherwise.
I meant that perhaps dovecot relies on socket activation to be restarted correctly. Probably not though given that it seems to work (or run, at least) in a fresh Devuan system.
Sorry Ogus1975, I was just joking.
Entering the error message into a search engine throws up https://bugs.kde.org/show_bug.cgi?id=425271 so this is a known bug.
The suggested workaround is given here but it's rubbish.
Check the X.Org log. If you're using GDM I think it will be under ~/.local/share/xorg/ or /var/log/ otherwise. ~/.xsession-errors might also have some clues.
If you have xserver-xorg-video-intel installed then try removing that package to force modesetting instead, which is reported to be less buggy.
^ I think the OP just wants a text editor. EMACS seems a bit excessive for that sort of thing... ![]()
Possibly relevant:
https://github.blog/2022-06-08-sunsetting-atom/
I recommend ed as a replacement ![]()
ED IS THE TRUE PATH TO NIRVANA! ED HAS BEEN THE CHOICE OF EDUCATED AND IGNORANT ALIKE FOR CENTURIES! ED WILL NOT CORRUPT YOUR PRECIOUS BODILY FLUIDS!! ED IS THE STANDARD TEXT EDITOR! ED MAKES THE SUN SHINE AND THE BIRDS SING AND THE GRASS GREEN!!
Well I have no idea about OS X (it is my least favourite operating system by some margin) but apparently a decent emulator can be run on it:
https://wiki.qemu.org/Hosts/Mac
Be sure to apply the -accel hvf option to achieve near bare metal performance.
EDIT: see also https://stackoverflow.com/questions/668 … erator-hvf
For running Devuan on the M1 bare metal see https://dev1galaxy.org/viewtopic.php?id=3956.
Which VM is this? If the installer is booted virtually then it can only see the virtual hardware so M1 support in the kernel isn't important.
Did you verify the integrity of the image?
I've deleted Windows. Thank fuck. What a *terrible* operating system — I could only use the AMDGPU-PRO drivers for my card and they gave a worse frame rate than amdgpu and ran the card at least 20°C hotter. And there's no PRIMARY selection mechanism, which was even more irritating. Edge scrolling for the touchpad is also now impossible in Windows unless you write your own driver. Wtf?
Managed to get Assetto Corsa working again by following this guide:
https://gist.github.com/ANBAL534/8057b5 … 627e550ba0
If that breaks again in the future I now have a working WINE prefix for the game saved in my Google Drive, PM me if you want a copy.
I marked the thread as SOLVED because I have some promising leads.
Any chance you could share them here? I'm sure other people who might face the same problem would find them useful.