Debian Configuration :: Backported Kernel Has Broken Hardware Sensors?
Aug 4, 2011
Having installed the 2.6.32 backport for Lenny, I have suddenly noticed that my Gkrellm doesn't display CPU and MB temperature anymore. Also, the smart sensors are inaccessible. Smartctl cannot access the readings even when run manually in a root terminal. I tried reinstalling lm-sensors and running sensor-detect again but it didn't help. What else needs to be updated to let the backported kernel see the hardware sensors?
I have Debian Squeeze with Gnome "sensors-applet" installed.I have a Nvidia 7300GT GPU whose Thermal Monitoring(Temperature) is Shown fine on "nvidia-settings" GUI. But ,Sensors Applet in Debian shows only CPU temp and if I install hddtemp,it will show hard disk temperatures.
I ended up rebuilding the package from debian source enabling nvidia support.and it worked(with "DEB_BUILD_OPTIONS="--enable-gui --with-nvidia" Has Any Work Around to show nvidia GPU temperature without rebuilding the package ?PS:Below is a screenshot of nvidia GPU temperature showing in the top panel(of Gnome). sensors-applet_nvidia.png (5.5 KiB) Viewed 518 times
Fotoxx requires an updated libgtk2.0 from Lenny-backports (see backports.org), though ufraw built correctly using the older version in Lenny. Ufraw-batch is a suggested package in Fotoxx, which is why I added it...plus Fotoxx seems to be completely missing in Lenny. 32 bit debs only, with the source files and instructions included to easily rebuild your own debs (the safest choice). These are quick builds, and should be OK to build on even old machines or netbooks, for which Fotoxx is a great choice for image editing.[URL]..
I recently installed debian squeeze 32bit on a second partition of my amd athlon 64 X2 dual core machine.Currently it is using linux-image-2.6.32-trunk-686 kernel.But linux-image-2.6.32-trunk-amd64 is available.on the repository.Is it a 64bit kernel or 32bit kernel optimized for amd64 architecture?
I am using DEBIAN 6.0 and I wannna update my kernel from 2.6.32 to 2.6.38. Every time, I do it but after the installation & rebooting into the new kernel it gives me error "UNABLE TO BOOT INTO THE KERNEL".
Yesterday I installed some updates on my Jessie system (I don't remember if the kernel was also updated). After rebooting the system nothing happens after the "Loading intial ramdisk"-message. If I boot in recovery mode the boot stops at the message:
Code: Select allfb: switching to nouveaufb from simple
If I add "nouveau.modeset=0" temporary to the GRUB-entry for the recovery mode, it will boot up in the console-mode.
I was able to get an ethernet connection with "dhclient eth0" and removed the "xserver-xorg-video-nouveau" package. Then I installed it and the removed gnome-desktop again. Before removing it, aptitude said the following to the package:
Code: Select alli A xserver-xorg-video-nouveau
Now it only says:
Code: Select alli xserver-xorg-video-nouveau
But this didn't change my problem. I found a similar case in the internet, but there were no solutions for it: [URL] ....
The next thing I would do, is to install the proprietary nvidia-drivers, but since I have a GTX 960 video card, I would have to use experimental drivers. So I'm afraid to make it more worse trying to install this drivers.
Also I'm not sure if it really is a driver-specific of kernel-specific problem. My kernel is version 3.16.0-4-amd64.
For anyone using Blueman with Testing (Squeeze), todays Python upgrade to version 2.6 stops it from working due to a Blueman bug. This has been fixed in blueman version 1.21-4, which you can install from SID if you don't want to wait the 10 days for the normal migration.
I have a problem with my custom kernel when I want to create the Nvidia kernel module.After this finished I installed the image and headers and created the Nvidia kernel module. Everything worked fine.However, if I remove the linux-source from my home directory then I can't create the kernel module.Even though I have the headers for the kernel installed.
I was using Synaptic to remove unwanted sound & audio programs...it seemed to take out other files that were non-related ?
(1) Now apt-get complains about a "Held Package" and doesn't tell me the pkg name.
(2) Synaptic is broken...error..E: The value 'stable-updates' is invalid for APT::Default-Release as such a release is not available in the sources
E: _cache->open() failed, please report.
stable-updates isn't even in my sources list. I've purged synaptic, and re-installed but remains broken. When you close error msg synaptic disappears ? Therefore can't use synaptic at all.
(3) apt-get says many packages that were available are no longer available...like one of the main repos has disappeared ?
(4) I put the same repos that are working for my brother who is running Debian Jessie also, but didn't improve the number of missing available packages.
deb [URL] ....
deb [URL] ....
How or why things have gone so wrong from just removing unwanted sound pkgs.
To recap problems...apt-get held pkg....broken synaptic....unavailable pkgs.
I'm restoring an old TI Silent 700 terminal [URL] ... and have connected it to an RPi running the debian based Jessie release using a serial converter. After learning more than I wanted to about serial settings and support I now have it interfaced and communicating bidirectionally but have one last hurdle - proper support for a single case (uppercase only) terminal in agetty.
With the -U flag on it seems like the the login name is detected as needing conversion because lowercase login names work - but lower case passwords do not and once I get a bash prompt all input comes in as upper case. So the -U agetty flag only seems to apply to login name and is then forgotten (not passed on to login process or bash?) and various settings in stty like iuclc, xcase, iexten don't seem to work.
I'd really like to get this terminal working with native support but I'll also take a kludge of some kind (I've tried a tr pipe for example).
Here is what I think is the relevant portion of my systemd generator:
Alright, I edited "/etc/default/isc-dhcp-server" and set "eth0" as the only thing listed for interfaces. I also have the code below in "/etc/dhcp/dhcp3/dhcpd.conf" and I even copied it to "/etc/dhcp/dhcpd.conf" for good measure, and I can't get the DHCP server to start. As an intermediate to advanced user, I am under the high assumption that it is broken since everything in the docs has been set. I have googled for two days and cannot find a fix, so before I report it as a broken package, would somebody with more experience with the package chime in?
I hid my wireless setup because it contains my WiFi network info including key. This box is routing, doing DNS resolution, and firewalling just fine. I just cannot get the friggin' DHCP server to start no matter what I try.
Oh, and is it safe to delete "/etc/dhcp" or "/etc/dhcp3"? They appear to be duplicates of each other...
I want to remove a keyring package I installed from a repository that I no longer want to use. However, I cannot remove it:
# apt-get remove -y --force-yes debian-xray-keyring Reading package lists... Done Building dependency tree Reading state information... Done
The following packages will be removed: debian-xray-keyring 0 upgraded, 0 newly installed, 1 to remove and 130 not upgraded. After this operation, 49.2 kB disk space will be freed. (Reading database ... 181076 files and directories currently installed.)
Removing debian-xray-keyring ... gpg: key "AB8F901D" not found: eof gpg: AB8F901D: delete key failed: eof dpkg: error processing debian-xray-keyring (--remove): subprocess installed pre-removal script returned error exit status 2 configured to not write apport reports Errors were encountered while processing: debian-xray-keyring E: Sub-process /usr/bin/dpkg returned an error code (1)
I got a rather big problem since an attempt to upgrade.My debian version is 8.0.I upgraded when apt proposed the change. I did that in two steps, with apt-get upgrade and then apt-get dist-upgrade, with the installation of a new kernel. I moved from 3.2.0-4-686-pae to 3.16.0-4-686-pae.Since the upgrade, I can't boot my system any longer.During the boot sequence, this message appears with a countdown (it's copied by hand) :
Code: Select all(1 of 4) a start job is running for dev-disk-byX2du
At the end of the countdown, the boot sequence starts again, and ends up on an invite to log in as root in rescue mode. I can't connect (maybe due to some azerty/qwerty issue, I got a French keyboard. I tried to type in "qwerty mode", with no success (the password is not prompted)).I can connect with the 3.2 kernel however, selecting it form the grub interface. I can't log in in rescue mode either, but with this kernel the boot sequence goes on and I can log as a regular user or as root, at the end of the boot sequence. There is no X, but the system seems to work.What could I do to make the system boot properly with the new kernel, or to go back to the 3.2 version ?
I have a set of vm's with stable, testing, and sid to keep track of how things are going. When I did an apt-get dist-upgrade with squeeze last week, things seemed to OK (350 package updates) until the end. It didn't seem to like and / or was confused by a kernel dependency.
I am not too concerned yet. Because these are in vm's, I do a snapshot before any significant change. I can futz around with impunity because I have that backup.
I re-booted, and tried the apt-get dist-upgrade again with same results. I think I also tried apt-get -f install.
So I reverted to the snapshot, and will simply try again in the future. I recall that with lenny as testing, the font-desktop was really screwed up for about a period of 6 weeks.
However, just in case someone else runs into this:
1) a re-boot worked, but the failure of apt-get made me nervous enough to revert.
2) waiting for corrections has seemed to work in the past (with a single exception with a 4-disk SCSI software RAID10 update that failed to re-boot lenny successfully after what seemed to be a minor update -- that was on a real system, not a vm. I haven't gotten back to look at that.)
I can't for the life of me get the xsensors to work. I installed lm-sensors, the applet and also xsensors.I followed everything on this guide:URl... Went through it more than twice and a couple of restarts. I just can't figure out what's wrong.When I run "sensors" nothing is found. I ran the sensors configuration and it only found one device to add to /etc/modules. Please see the trace below, I would be very grateful if you can help me find the fix for this! The desktop is an HP Pavilion a730n with a Pentium4 processor.
I would like to use lm-sensors with my new PC.With my old one lm-sensors showed all sensors of CPU, GPU, wattage and Fan.With the new AMD64 (kernel 2.6.32-5 on Debian Squeeze) I get only the temperature of the GPU and the HDD.The only found sensor is "Fintek F71882FG/F71883FG Super IO Sensors"No embedded "AMD [...] thermal sensors" found in sensors-detect How can I fix it?sensors-detect
found a bug in vinagre/vino in Ubuntu 8.04. The bug is documented and has been processed here: [URL] How do I get the fix backported to 8.04? Where do I start? 8.04 is supposed to be supported through April 2011 so I don't think I should have to upgrade to 8.10 - that is why I am using an LTS release.
On Lenny, due to some compatibility issues: kernels before 2.6.26 don't recognize part of my vaio laptop's hardware, while the last drivers of my videocard (version: 260, card: nvidia gt 230m) suffer some incompatibility problem (this is one of the most problematic computers I ever had), so I have to use version 256, which doesn't work with kernels after (perhaps) 2.6.32. So, I suppose I have to check each kernel between that two versions and hope that one of them will be ok. I searched quite deeply over the net but didn't find anything related to debian, except for generic kernels [URL], but as someone told me that it's better if I only install stuff from the stable repository or backports. What can I do? Is there any backports archive or something like that? Otherwise, what should I do?
After I ran sensors-detect, it said that İ needed k10temp module to be compiled, so I searched some forums and got required stuff. However, before compiling it, I added the gnome applet for sensors to the panel, and surprisingly it shows the cpu and motherboard temperatures. How reliable it is? Do I still need to compile k10temp? (I will compile it since I don't want to use a kernel from experimental repo).My kernel is 2.6.32-5-amd64, TestingCPU: AMD Phenom 2 x4 955 BE
I recently bought an AMD R7 360 videocard and I'd like to use the free Radeon driver.
Problem is, PCI-ID 0x665f is not present in Jessie's 3.16 kernel sources. The hardware however is supported, it's just not recognized. So I'll have to get the Debain sources and patch include/drm/drm_pciids.h
From the 4.1rc1 kernel I know what to patch and where.
Debian page that explains how to use the Debian build system for recompiling the current kernel from Debian packages?
Upgraded Wheezy to Jessie, by changing my apt sources to point at stable instead of wheezy. Ran upgrade, and dist-upgrade, all fine etc.
Then tried to update the kernel by installing linux-image-amd64 package .. seemed to work fine, but after a reboot my kernel version still says 3.10.23
What have I missed?
Code: Select allroot@hostname:~# apt-cache search linux-image linux-headers-3.16.0-4-amd64 - Header files for Linux 3.16.0-4-amd64 linux-image-3.16.0-4-amd64 - Linux 3.16 for 64-bit PCs linux-image-3.16.0-4-amd64-dbg - Debugging symbols for Linux 3.16.0-4-amd64 linux-image-amd64 - Linux for 64-bit PCs (meta-package)
I have a MyBookLive where i installed a Debian 2.6 kernel. The system is running fine so far. Because of an error message when apt-get upgrade (udev) i tried to upgrade to 3.16. Here's what i did:
- apt-get install linux-image-xx - apt-get install linux-source-xx - extract the source - copied the old .config from running 2.6 kernel over to the 3.16 directory - make oldconfig - make uImage - make modules - make modules_install - copied uImage to /boot
No error messages because its a headless device - its just not booting up.
I was wondering if anyone can assist me. I am looking to build a server with Debian as the host. When I installed Debian (Squeeze) the default kernel was "2.6.32-3-trunk-amd64". When I tried to install 'Virtualbox' application, I got a failure because I didn't have the 'kernel-headers' installed on my machine. I noticed there are no specific header package the 'trunk' kernel I was using. I have a few questions so I guess I should begin:
Is it safe to remove the 'trunk' kernel and boot my system on just the regular 2.6.32-3-amd64 kernel? Is this OK or not recommended? Please explain whatever is the correct answer. This is my 1st time using a 'Trunk' kernel so I don't know the in's and out's of it.
If I am using Debian 'Testing' for virtualization via 'Vbox', is there a specific kernel I "should" be using?
