You are not logged in.
?
apt-cache search nvidia-legacy-340xx
https://pastebin.com/raw/q3D8v15P
root@home:/etc/apt# apt install nvidia-legacy-340xx-kernel-dkms --no-install-recommends
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package nvidia-legacy-340xx-kernel-dkms
root@home:/etc/apt#
sources.list
# deb cdrom:[Devuan GNU/Linux 4.0 chimaera amd64 - desktop 20211012]/ chimaera contrib main non-free
# deb cdrom:[Devuan GNU/Linux 4.0 chimaera amd64 - desktop 20211012]/ chimaera contrib main non-free
deb http://deb.devuan.org/merged chimaera main contrib non-free
deb-src http://deb.devuan.org/merged chimaera main contrib non-free
deb http://pkgmaster.devuan.org/merged chimaera-security main contrib non-free
deb-src http://pkgmaster.devuan.org/merged chimaera-security main contrib non-free
# chimaera-updates, to get updates before a point release is made;
# see https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_updates_and_backports
deb http://deb.devuan.org/merged chimaera-updates main contrib non-free
deb-src http://deb.devuan.org/merged chimaera-updates main contrib non-free
@blackhole reported
nobody knows?
soory, my mistake, i mean what difference between
https://mirror.leaseweb.com/devuan/devuan_chimaera/installer-iso/devuan_chimaera_4.0.0_amd64_desktop.iso 3.5gb
and
https://mirror.leaseweb.com/devuan/devuan_chimaera/installer-iso/devuan_chimaera_4.1_0_amd64_pool1.iso 4.7gb
why so different size?
both using non fefracta installer?
Thanks.
So, may be this script not working on chimaera(stable) because this driver is dropped on stable debian?
But still supported on sid and because working on ceres?
So, no way to make it working on chimaera?
Or just true way is using 340.108 from devuan repo?
But from devuan repo 340.108 is working but not perfectlly installs (nvidia-settings launch only from terminal and i need to delete some modprobe nvidia files because do not want see warnings during booting process)
deepforest wrote:why i cant here do the same?
As HoaS implied in the very first reply to this thread, you can. With the not-refracta bootable install image.
If you insist on using the live image, a workaround has already been suggested.
Complaining about a missing feature in refracta installer achieves nothing. If you really want it, nobody is stopping you from implementing it yourself.
Thank you.
This is non refracta?
https://mirror.leaseweb.com/devuan/devuan_chimaera/installer-iso/
and what difference between
https://mirror.leaseweb.com/devuan/devuan_chimaera/installer-iso/devuan_chimaera_4.0.0_i386_desktop.iso
and
https://mirror.leaseweb.com/devuan/devuan_chimaera/installer-iso/devuan_chimaera_4.1_0_amd64_pool1.iso
?
aluma wrote:1. During installation, formatting is mandatory for the "/" partition and is not allowed without a direct user selection for the /home partition.
I don't understand what you are saying here, but it sounds wrong.
It is not mandatory for the installer to format the chosen partition(s) but it is mandatory for them to have a filesystem if you want them to contain files, and formatting is the default setting.
You can partition and format before running the installer and tell the installer not to format. That's a checkbox in the options menu of the graphical installer and it's a config file setting in the cli installer.
You have the choice to install the entire system to one partition, or you could optionally have separate partitions for /boot and/or /home.
The installer doesn't know what to do with your old home or the user configs it contains. It's up to you to figure out any conflicts caused by mismatched or missing config files caused by sharing a home between two different operating systems.
as usual, on others distros i can use one /home partition for many linux os with separeted user folders, why i cant here do the same?
steve_v the first make offencive to me
i am just ask, have someone experience with script from first post?
and why if it worked on unstable, not working at stable?
driver from script is successfully installed but after, X do not starting.
deepforest wrote:solution for normal distros but not for "knee develop" semi working devuan
ROFL. Devuan not including out-of-tree kernel patches for fossilised proprietary drivers is not a bug. Go hassle Nvidia to fix their trash.
All your threads are this same BS. Vague problem descriptions with insufficient debugging information, pigheaded insistence on doing things some $other_os way, then a bunch of complaining when you inevitably break your install. I'm done trying to help you, you just don't listen.
Bye now, have fun. I await your next reinstall thread with bated breath (and popcorn).
no, its devuan piece of glitch bull shit
deepforest wrote:340.108 driver
You won't get that version to run with a 5.5 or newer kernel without a kernel patch and recompile of the kernel. I believe the release you are running is based on the 5.10 kernel.
Try searching the web for "Linux 5.10 nvidia 340.108"
you read thouse solution with attention? old driver patched for new kernels!
Because following some random blog post and using third-party executable installers rather than the repos is a sure-fire way to mess up your install?
The debian documentation and discussion boards are replete with warnings not to do this, and for good reason.Other than that, if you want help you will need to provide a whole lot more information (with command output and such in code tags, not blurry screenshots) than just "why not working". Nobody here is psychic, and I for one am all out of patience for guessing games.
its not random solution
its fully 100% solution for normal distros but not for "knee develop" semi working devuan
Not. Its again copy all data from previously /home dir, but its not mounted
https://ibb.co/cYDQDHj
https://www.if-not-true-then-false.com/ … dia-guide/
its was worked for me on Ceres but not work now on Chimaera
ps 340.108 driver
Ok. I check. I am reinstall OS via live gui, without any mounted partitions and report.
Devuan 4 Chimaera
Live graphical installation
3 separate partitions
/root
/swap
/home (using for others distros, and have user folders)
After long installation of Devuan 4. OS booted normally but space on /root partition is fully used by "target_home" folder witch contain full copy of separate /home partition?! I am ask what is the mess?! Why installation make unneeded copy of /home to /root partition?!
https://dev1galaxy.org/viewtopic.php?id=5392
i cant express my opinion here!?
Any tool is only as useful as the user controlling it. I think you are pointing the finger in the wrong direction. Take responsibility!!!
Controlling and responsibility over many troubles?
Or get a Windows machine. Now go to a Windows tech help forum and be amazed. Clearly not ready for the desktop!
i am using windows 25years, windows have much less issues compare ti linux, and many issues resolved without support
Seriously, your last whining post was about glitches in Ceres, which is unstable, and is not meant for production use.
Proof?! For my old pc unstable works faster than stable.
You can walk away from Linux any time you like. Every penny will be refunded :-)
Away? I am can not even come close because so many issues.
Look at all my topics here. Only issues! linux NOT READY YET FOR DESKTOP USING!
https://i.ibb.co/H71M5Dj/Screenshot-202 … -Forum.png
debugging info
freeartist@devuan:~$ thunar -q; thunar .
(thunar:5638): GVFS-RemoteVolumeMonitor-WARNING **: 04:48:14.363: remote volume monitor with dbus name org.gtk.vfs.UDisks2VolumeMonitor is not supported
How to fix that?
similar issue
https://bugzilla.redhat.com/show_bug.cgi?id=1585066
syslog
2022-12-08T04:48:01.747635+02:00 devuan dbus-daemon[5510]: [session uid=0 pid=5508] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
manually remove
/var/lib/dpkg/info
libjpeg62-turbo*
how to fix that?
root@devuan:/etc/apt# apt remove --fix-broken install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package install
root@devuan:/etc/apt# apt --fix-broken install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
libjpeg62-turbo
The following packages will be upgraded:
libjpeg62-turbo
1 upgraded, 0 newly installed, 0 to remove and 112 not upgraded.
4 not fully installed or removed.
Need to get 0 B/169 kB of archives.
After this operation, 346 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Reading changelogs... Done
(Reading database ... 388635 files and directories currently installed.)
Preparing to unpack .../libjpeg62-turbo_1%3a2.1.2-1+b1_amd64.deb ...
Unpacking libjpeg62-turbo:amd64 (1:2.1.2-1+b1) over (1:1.3.1-12) ...
dpkg: error processing archive /var/cache/apt/archives/libjpeg62-turbo_1%3a2.1.2-1+b1_amd64.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libjpeg62-turbo/changelog.Debian.gz', which is different from other instances of package libjpeg62-turbo:amd64
Errors were encountered while processing:
/var/cache/apt/archives/libjpeg62-turbo_1%3a2.1.2-1+b1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@devuan:/etc/apt#
no, explain please, feel free its my topic
still on ceres and runit. still can boot, still got network, still got all devices.. (no nvidia sh*t).
and what gives runit compare to sysv?
SOLVED!
previously i am install runit init
now i am move back to sysv init
and now driver installation complete without errors