Hi,
after runnig a d-u on the 12th of Feb which installed kernel 3.19 I couldn't start X.
Kernel 3.18-3 worked fine. I then removed the kernel 3.19 with the kernel-remover and since then 3.19 wouldn't show with d-u. So. I'm kind of stuck with kernel 3.18-3.
What do I have to do so the newest kernels will show up with a d-u?
System: Host: rebel Kernel: 3.18-3.towo.1-siduction-amd64 x86_64 (64 bit gcc: 4.9.2)
Desktop: Xfce 4.10.2 (Gtk 2.24.18) Distro: siduction 14.1.0 Indian Summer - xfce - (201411230427)
thanks in advance and kind regards
It should be sufficient to reinstall the metapackages linux-image-siduction-amd64 and linux-headers-siduction-amd64 which pull the rest.
hello Miho,
perhaps you need an updated driver package from one of our experimental/non-free sections.
In general siduction is a good place for users of proprietary drivers.
# LC_MESSAGES=C apt-cache policy nvidia-driver
nvidia-driver:
Installed: 346.47-0.siduction.3
Candidate: 346.47-0.siduction.3
Version table:
346.47-1.siduction.1 0
1 http://packages.siduction.org/extra/ experimental/non-free amd64 Packages
*** 346.47-0.siduction.3 0
500 http://packages.siduction.org/user/ experimental/non-free amd64 Packages
100 /var/lib/dpkg/status
343.36-1 0
1 http://http.debian.net/debian/ experimental/non-free amd64 Packages
340.76-0.siduction.1 0
500 http://ftp.spline.de/pub/siduction/fixes/ unstable/non-free amd64 Packages
340.65-2 0
500 http://http.debian.net/debian/ unstable/non-free amd64 Packages
Those repos are not listed on http://packages.siduction.org/ (http://packages.siduction.org/), because they are unofficial.
(*** means, that i use it anyway.)
greetings
musca
Thanks for your prompt replies!
Got kernel 3.19 running and will see if newer kernels get pulled by d-u.
I also tried the nvidia-driver (346.47...) from experimental-repo, unfortunately the same issue as mentioned here (http://forum.siduction.org/index.php?topic=4758.0) struck. So I reverted back to the nvidia-driver from fixes-repo cause I need opencl.
best regards