Debian Configuration :: No Automatic Update Of The Kernel?
Nov 1, 2010
I've just installed debian sid and see that I've the kernel 2.6.32. I was a bit surprise as on ubuntu I had the 2.6.35 and debian sid is supposed to be more up to date that ubuntu (maybe I'm wrong).So I checked what were the packages available :
mart@mart-laptop:~$ uname -a
Linux mart-laptop 2.6.32-5-686-bigmem #1 SMP Sat Oct 30 23:25:58 UTC 2010 i686 GNU/Linux
mart@mart-laptop:~$ sudo aptitude search ^linux-image
I'm recompiling my kernel on a dell latitude c600 running lenny as I type, and it's taking forever, so far upward of 4 hours.I think I'm getting drivers for ever piece of computing hardware since the univac So I googled "a kernel conf creator" and got [URL]... Its a nice, clean method for finding what hardware your using... you just run lspci cpuinfo make xconfig and put in all the info yourself. So I was thinking: this is exactly the kind of dull, repetitive behavior that computers were made for. Is there a program that can find my hardware info, and make the.config itself, with very little user input?Or should I reinstall debian on another partition and steal the .config from it? Or should I man it up and do it myself?
After an automatic update from Debian I get the following error while starting a root terminal: An error occurred while loading or saving configuration information for gnome-terminal. Some of your configuration settings may not work properly. Failed to contact configuration server: the most common cause is a missing or misconfigured D-bus session bus daemon.
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".
Is there a way to get the matching Linux kernel headers automatic on a regular kernel update via the Ubuntu packed manager? Every time I get a new kernel I must do an aptitude install linux-headers-`uname -r`
Squeeze's latest update has upgraded my kernel from 2.6.32-3-686 to 2.6.32-5-686.My wireless stopped working and then I realised that I had to rebuild the wifi modules. I had followed this earlier.URL...For this new kernel, which I step of the process should I repeat? Rebuild module? Or just do a modprobe?
As a follow-on to something Telemachos said in another post:
Quote:
Originally Posted by Telemachos
You can see what kernels you have installed - to check if you have a virtual kernel and to clean up - by running this command:
Code:
If you've been installing kernel-headers along with the kernels (say to build modules for graphics or wireless), you should remove those when you remove the corresponding kernel. The command to search for those is parallel:
Code:
I would have thought that removing a given kernel package would trigger the removal of the older kernel headers. Can someone confirm that is, or is not, the behavior? I ask this because it seemed to me that the older kernel header packages were indeed removed when I removed some older kernel packages.
For example, the linux kernels I have installed are:
Code:
Also, the linux-headers packages I have installed are:
Code:
So, when I get around to removing the linux-image-2.6.25-2-amd64 package like this:
Code:
I would expect apt-get to automatically also remove linux-headers-2.6.25-2-amd64 and linux-headers-2.6.25-2-common. Is that what will happen, or do I need to explicitly state all three packages on the apt-get remove command?
After running a large update and rebooting a few weeks ago, I found that my internet connection had stopped working. My internal network still worked fine though, so it I know it's not the card itself or its configuration. After a bit of trial and error I discovered that simply running dhclient brings the connection up again, so it appears that something is interfering with the initial dhcp update to my ISP (or something like that; I'm no expert in this area. ) My usual policy in cases like this is to wait through two or three updates in the hopes that it's just a temporary problem, but it's been a while now and subsequent updates haven't fixed it.
I've tried looking around, but I can't come up with search criteria specific enough to narrow it down to my specific situation. I'm not even sure where to begin looking to diagnose the problem, nor do I know which package update(s) could've affected it. I'm not sure what might be useful, but here's the relevant entry in /etc/network/interfaces. I have it configured with a static internal address, with my router as the gateway.
my friend updated kernel today and it "stopped working" and I was asked to fix it he is new to linux, and I don't have physical access to that notebook from what I know main problems are:
1. no network devices exist (except for loopback) 2. sound card driver is missing (nVidia MCP79) 3. in grub menu after choosing new kernel uname -r sais the old one's version
wifi card is atheros, but I don't know specific model.
I do not know if this is really something I should worry about. I am running Debian testing on my laptop (HP Pavillon dv6). Today, the aptitude update---aptitude upgrade gave me a new kernel (2.6.39). However, if I boot with that kernel, I get a warning (do not know if that is the way I should call this) telling me that the machine failed to get the i915 symbols so turbo graphics will be disabled.I have not done any serious test, but at first sight I do not notice any difference performance-wise with respect to the previous kernel. what am I supposed to do to fix this?
When I try to run programs from root terminal I get the error
Code: Select allQDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. No protocol specified kate: cannot connect to X server :0
I found a solution: I do Code: Select allxhost SI:localuser:root
but I have to do it after each reboot. I tried to put this command in rc.local but it did'nt work. How to do this auto?
I have configured a RaLink wireless card to connecto to an 802.1x network. I connect by selecting the network, and the i give the credentials(username/password). How do i configure Debian to automatically connect to this network when a session begins?
I have some issues concerning so called "11-minutes-mode" - RTC update"11-minutes-mode" definition In hwclock man page we can read:"Automatic Hardware Clock Synchronization By the KernelYou should be aware of another way that the Hardware Clock is kept synchronized in some systems. The Linux kernel has a mode wherein it copies the System Time to the Hardware Clock every 11 minutes. This is a good mode to use when you are using something sophisticated like ntp to keep your System Time synchronized. (ntp is a way to keep your System Time synchronized either to a time server somewhere on the network or to a radio clock hooked up to your system. See RFC 1305).
This mode (we'll call it "11 minute mode") is off until something turns it on. The ntp daemon xntpd is one thing that turns it on. You can turn it off by running anything, including hwclock --hctosys, that sets the System Time the old fashioned way. To see if it is on or off, use the command adjtimex --print and look at the value of "status". If the "64" bit of this number (expressed in binary) equal to 0, 11 minute mode is on. Otherwise, it is off. If your system runs with 11 minute mode on, don't use hwclock --adjust or hwclock --hctosys. You'll just make a mess. It is acceptable to use a hwclock --hctosys at startup time to get a reasonable System Time until your system is able to set the System Time from the external source and start 11 minute mode. Here are my questions:1 . How to check if "11-minutes-mode" is on/off ?The output of adjtimex -p looks like this:
How can I change the automatic fsck execution at boot time to be above 30 boots? I reboot the system sometimes 3 to 4 times a day. Intel 3 GHz, tower, i386 lenny vmlinuz-2.6.31-686
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 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 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.)
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?
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?
I have maked a new kernel (version is 2.6.24.7) in debian system which kernel is 2.6.26, and then when i start the new kernel which is 2.6.24.7, it tells me that:
