Beiträge von tavik
-
-
I will try that on Friday but I would think Debian.org/Debian should work
I guess you are aware of this
post -
-
-
Hi,
I use etcher and install from USB to SSD.
I am using this file.Trying sudo apt-mark unhold Linux-image-amd64 leads to Linux-image-amd64 was already not hold.
-
of course. here you go
OMV-Extras --> upgrade
Reading package lists...
Building dependency tree...
Reading state Information...
Calculating upgrade...
The following packages have been kept back:
linux-image-amd64
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Fertig...OMV-Extras --> dist-upgrade
Reading package lists...
Building dependency tree...
Reading state Information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Fertig... -
As you can probably guess, I am not a seasoned linux user.
When given suggestions how to fix a certain problem, I tend to stick to the steps laid out. Since the solution relied on aptitude, I did not second guess it.Completely reinstalled OMV this morning.
Backports are enabled.
upgrade lead to
The following packages have been kept back:
linux-image-amd64 -
So I checked for more recent kernel versions via
sudo apt-get install aptitude
sudo aptitude update
aptitude search linux-imagesudo aptitude update ran into errors concerning the File "/usr/lib"python3.5/weakref.py"
I checked the forum, read some suggestions concerning solutions but I remain puzzled that a fixed bug comes up in fresh installation of OMV. The ISO was released this month!The most recent image I was offered with out the -dbg extension was 4.19.0-0.bpo.5-amd64
When I try to install this image, I get
Error! Your kernel headers for kernel 4.19.0-0.bpo.5-amd64 cannot be found.I did that.
After I updated the headers, the kernel update once more provoked the exceptions concerning weakref.py.
I applied the fix mentioned here:
Python 3.5 issue during apt-Afterwards
sudo aptitude install linux-image-4.19.0-0.bpo.5-amd64
workedI reinstalled Virtualbox via GUI.
Warning concerning character device /dev/vboxdrv remains.Suggestions?
-
-
Thank you ryecoaaron,
sudo dpkg-reconfigure virtualbox-dkms
results inModule build for kernel 4.19.0-0.bpo.4-amd64 was skipped since the kernel headers for this kernel does not seem to be installed.
sudo modprobe vboxdrv
results inmodprobe: FATAL: Module vboxdrv not found in directory /lib/modules/4.19.0-0bpo.4-amd64
Any other suggestions are highly appreciated!
Since I failed to identify recent threads on the subject, please feel free to suggest threads that are of relevance for this kind of problem.
regards
-
Hallo zusammen,
ich habe einen HP Microserver neu mit OMV aufgesetzt. Das aktuell verfügbare Image 4.1.22 lässt sich relativ problemlos installieren. Auch der Upload und die Installation von OMV-Extras bereitete keine Schwierigkeiten.
Die Installation von Virtualbox-Plugin ist da schon etwas anderes.Es lassen sich keine virtuellen starten.
Google hilft. Das Problem kündigt sich schon im Log der Plugin-Installation an:WARNING: The character device /dev/vboxdrv does not exist.
Please install the virtualbox-dkms package and the appropriateheaders, most likely linux-headers-amd64.You will not be able to start VMs until this problem is fixed.
Mich würde zunächst interessieren, ob dieses Verhalten bei einer neuen Installation von OMV im Zusammenhang mit einer Plugin-Installation aus einem OMV-Extras heraus zu erwarten ist.
Hat jemand eine hinreichend einfache Empfehlung für mich, wie zu verfahren ist?
Wenn ich das richtig sehe, verwendet OMV 4.1.22 die Kernelversion 4.19.0-0.bpo.4-amd64.
Hiermit scheint Virtualbox nicht klar zu kommen.Für Tipps wäre ich sehr dankbar.