With tonight's d-u I manually updated to kernel 3.16-3.towo-siduction-686. Booting this kernel does end in a terminal, not in X.
3.16-2.towo-siduction-686 still working fine.
which graphics?
which driver?
(proprietary drivers need linux-headers-3.16-3.towo-siduction-686)
Please post your result of:
Quoteinxi -F
Edit: Removed some of the empty lines :)
Note: Obviously here the *working* kernel 3.16-2 is in use:
Quote$ inxi -F
System: Host: lintower Kernel: 3.16-2.towo-siduction-686 i686 (32 bit) Desktop: Fluxbox 1.3.5
Distro: siduction 11.0.5 One Step Beyond - xfce - (201112060028)
Machine: Mobo: N/A model: K8NF4G-SATA2 v: 1.00
Bios: American Megatrends v: P1.20 date: 09/20/2005
CPU: Single core AMD Sempron 2600+ (-UP-) cache: 128 KB clocked at 1607 MHz
Graphics: Card: NVIDIA G84 [GeForce 8600 GT]
Display Server: X.Org 1.16.1 driver: nvidia Resolution: 1680x1050@59.88hz
GLX Renderer: GeForce 8600 GT/PCIe/SSE2/3DNOW! GLX Version: 3.3.0 NVIDIA 340.32
Audio: Card NVIDIA MCP51 AC97 Audio Controller driver: snd_intel8x0
Sound: Advanced Linux Sound Architecture v: k3.16-2.towo-siduction-686
Network: Card: NVIDIA MCP51 Ethernet Controller driver: forcedeth
IF: eth0 state: up speed: 100 Mbps duplex: full mac: 00:13:8f:4b:05:02
Drives: HDD Total Size: 580.1GB (79.4% used)
ID-1: /dev/sda model: WDC_WD5000AVDS size: 500.1GB
ID-2: /dev/sdb model: ST380011A size: 80.0GB
Partition: ID-1: / size: 24G used: 19G (82%) fs: ext3 dev: /dev/sda1
ID-2: /home size: 21G used: 14G (72%) fs: ext3 dev: /dev/sdb9
ID-3: /var size: 9.6G used: 4.0G (44%) fs: ext4 dev: /dev/sda2
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 34.5C mobo: 30.0C gpu: 54C
Fan Speeds (in rpm): cpu: 1757 fan-1: 0 fan-3: 0 fan-5: 0
Info: Processes: 147 Uptime: 3 min Memory: 368.4/1009.0MB Client: Shell (bash) inxi: 2.1.28
And only to be clear, I booted the 3.16-3 kernel twice tonight and now again, with the same outcome, no X, whereas kernel 3.16-2 everytime boots to X. So this is not a system hickup but a real different reproducible behaviour of the 3.16-3 kernel.
dkms status
I am sorry so say, but this thread unfortunately is a "stupid me" thread. I forgot to install the headers which here obviously are needed for the propriatary nvidia driver.
I since years know I have to install image AND headers, and I allways do it this way. It seems I was too tired tonight.
Sorry for the noise, towo, kernel 3.16-3 works perfectly as all your kernels did over the last years.
Thanks.
@micha, I think you do not have this package installed:
root@imerabox:/# apt-cache policy linux-headers-siduction-amd64
linux-headers-siduction-amd64:
Installed: 3.16-7
Candidate: 3.16-7
Version table:
3.17~rc6-3 0
1 http://packages.siduction.org/extra/ experimental/main amd64 Packages
*** 3.16-7 0
500 http://packages.siduction.org/base/ unstable/main amd64 Packages
100 /var/lib/dpkg/status
If you install it, then each kernel upgrade will also pull in the applicable headers package. :)
Dibl, you are right, but I don't have the kernel meta packages installed on purpose because I don't want to pull each kernel. As said, I am totally aware of the packages I have to install and I am managing it since years. It was a stupid oversight this night.
Thanks anyway.
Chill out! We're humans after all!!! ;)