Debian Configuration :: Squeeze: Can't Find Source For 2.6.32-trunk Kernel
Apr 30, 2010
I'm attempting to install ndiswrapper-dkms package. The installation fails due to the following error:Module build for the currently running kernel was skipped since the kernel source for this kernel does not seem to be installed. dpkg reports that the source is installed
[code]....
I've been searching google for the past couple of days but haven't found anything specific. Any ideas to get me going in the right direction?
uname -a reports
Linux debtop 2.6.32-trunk-686 #1 SMP Sun Jan 10 06:32:16 UTC 2010 i686 GNU/Linux
I upgraded testing today on my intel laptop. During the upgrade I got the message that the new kernel would require additional firmware, see attached. Is the solution for this to install the driver from Realtek? [URL] If so, the instructions said to check if the driver was already installed, but what does the output below mean?
I installed linux-image-4.1.0-trunk, when I boot into the kernel there's no wireless available. Dmesg indicates seems like the firmware is loaded, although firmware-iwlwifi is installed: ... [ 11.047031] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-7265D-13.ucode (-2) [ 11.047039] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-7265D-13.ucode failed with error -2
Building Wine-1.3.16 for Squeeze from Source: Since there isn't a good version of Wine in the repositories, I decided to build my own from source. Here it is. read everything. I DID NOT have Wine previously installed. If you do, you'll have to remove it FIRST.
[code]...
With all the dependencies installed you can begin building Wine. From the terminal:
how to install Dropbox for Debian Squeeze from source.Please read everything before you begin. I prepared it as I installed Dropbox for my own system. Please Note: I use sudo, you may have to use root or 'su' from the command line. If you don't know the difference between sudo and su, then you shouldn't try this until you know. At the time I did this, the lastest dropbox version was 0.6.7.
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 installed Debian Squeeze from a net install to a raid 1 array. I have been having a lot of troubles related to being able to write to one or more of the mounted drives - even touch gives me errors.
The most interesting line from dmesg is:
Here is the full output from dmesg:
I found a thread that indicated that this bug was fixed in the next kernel version: 2.6.32-6. I am willing to upgrade the kernel to get rid of my problems. Is a squeeze kernel at 2.6.32-6 or higher available? If so, where? I have not compiled my own kernel, and am not very interested in getting into that.
downgrade my squeeze installation to kernel 2.6.32-29 (I think I have -30 now).
- what is the proper way to downgrade to that version of the kernel (I got my current kernel version when I installed squeeze few days ago and the official repo does not seem to have the -29 version anymore)?
- how to prevent that future automatic updates "upgrade" me again to the non-working version?
Laptop Amilo L1300, installed Debian Squeeze from netinstall from scratch a month ago. Installed Xfce as a DE afterwards.
This laptop usually has problem with: ACPI, Wifi and tons of other stuff usually Kernel related and is really picky about kernel version!
Now - with Lenny it worked without problems, but it had gnome and ext3 so I took a gamble and did a fresh install of Squeeze with Xfce with Ext4 filesystem and overall performance of the computer was faster and more responsive.
For wireless I have to use[url]
It all worked 100% until a week ago (roughly).
I do not use synaptic nor update manager, so I updated the system via terminal (as root of course) "apt-get update" and "apt-get upgrade". And I noticed it will upgrade kernel. I went through the upgrade process, as I thought it's all a 2.6.32-5-686 kernel version and it will not brake anything since it IS a stable branch of Debian and it will not install new kernel. Of course it did not install 2.6.34 or anything like that...
After the update I began experiencing problems, first with mouse pointer, it became invisible and goes back visible and resume from suspend, also wireless randomly disconnects and sometimes won't reconnect to wifi network, as I found out it's all kernel related problems (googled it up). I do not know how to go back to previous kernel version, since in Grub2 menu it only points to one and only kernel version, as I reckon it's the same version but with bugfixes? Or should I say buy UNfixes. I tried using a liquorix kernel 2.6.32 but as he works, has problem with ACPI as I presume since it freezes the system on random occasions.
Please, what EXACT version of kernel was in Squeeze like 3 weeks ago? And how can install that particular version of kernel, since it was the only one that worked besides the one from Lenny.
"uname -r" says: 2.6.32-5-686
That's what it always said.
Is it possible I had, dunno 2.6.32.28 and it was updated to, dunno, 2.6.32.29 or some later one?
I managed to google up this:[url]
And how can I go back to 2.6.32.28 kernel for instance?
I have squeeze with Gnome and 2.6.32-5-686 kernel. Due to problems with graphics card (kernel bugs), I'd like to update the kernel. The problem is, 2.6.32-5-686 seems to be at the moment last kernel for squeeze.Is it any way to update just a kernel and stay with squeeze or I must upgrade squeeze to the testing (wheezy)?
I'm running Debian Squeeze now, just did an upgrade yesterday. I had wl for my wireless and it was all working fine in Lenny. Now that I'm upgraded, wicd can't find anything at all.
I just wanted to know if i download Debian Squeeze linux-source-2.6.32 from packages.debian.org and try and compile it in debian lenny using lenny's packages will the build succeed ?
I am using Lenny kernel version 2.6.26-2-686.I am trying to install some drivers and they need kernel source. I installed kernel source through Synaptic, but the driver installer doesn't find it at the place it expects.
1) Where does Lenny keep the kernel source? 2) Are the kernel sources from Debian and www.kernel.org the same? 3) If I want to download the kernel source manually, where do I get it from?
I've got a fresh install of Squeeze on a 32bit host and I have been unable to boot into XEN/dom0.The Xen Kernel is "linux-image-2.6.32-5-xen-686" (pvops) and Hypervisor is xen-hypervisor-4.0-i386.The system default installed with grub2.It boots quite happily in normal mode, using the above Kernel, but just reboots itself if I try run it as Xen/dom0. (reboots within a second of pressing <enter> ... there is no messages displayed on the screen that I have noticed)The relevant menu (generated by /etc/grub.d/20_linux_xen) entry for running Xen is as below;
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-686 and XEN 4.0-i386' --class debian --class gnu-linux --class gnu --class os --class xen { insmod part_msdos
If I want to compile a kernel from source (from kernel.org), including all the drivers I need regardless of their origin, I would not need any firmware-*.deb packages, right? Do the firmware packages add anything that is not present in the latest kernel?
I installed 2.6.38 from backports. It boots OK, and among the start-up messages it says it has started kdm, but then it offers only a console login prompt, no GUI. I assumed (perhaps optimistically?) that newer kernels would be backward-compatible, and that any dependencies on other software would be enforced by the package mechanisms. Running amd64, Squeeze, KDE.
Squeeze-beta was my first foray into Debian, and I love it. I changed my setup to a rolling setup with testing (Wheezy), and have done that for several months. Lately, I got a new kernel, but it reboots to a terminal rather than GUI (I'm a simple laptop user). I think it's because of the NVIDIA drivers, and here is what I've tried (meanwhile, I'm using the previous kernel):
# apt-get install module-assistant nvidia-kernel-common # m-a auto-install nvidia-kernel${VERSION}-source A blue screen appears that says:
module-assistant error message Bad luck, the kernel headers for the target kernel version could not be found and you did not specify other valid kernel headers to use.
You can try:
module-assistant prepare or apt-get install linux-headers-2.6.38-2-amd64
I have done both, rebooted, and I still get the blue screen. I also see this message:
nvidia-kernel-source was not built successfully, see:
/var/cache/modass/nvidia-kernel-source*buildlog*
...and I have copy/pasted the file below (which omits lines 101-200 because this message is too long then):
I'm always getting a blank console screen after booting a 2.6.32-trunk-amd64 kernel in squeeze. I still can read the line "Loading, please wait ..." in the display for a second - then it's completely black until X windows is starting. When I try switching from the X console to another virtual console (by pressing Ctrl-Alt-F1 e. g.), the complete system freezes. I have to hard reboot then.When I boot the previous 2.6.32-3-amd64 kernel instead, everything is fine as expected, though.There's a line "GRUB_GFXMODE=1024x768x16@60" in /etc/default/grub as well as a line "set gfxpayload=keep" in /etc/grub.d/00_header. So the problem might be framebuffer related in any way. Any ideas what could be tried?The system is a Latitude E6500 with a Mobile 4 Series Chipset Integrated Graphics Controller
So I'm building a custom kernel cuz I want the fbcondecor patch in my kernel. I use the same .config that 2.6.32 debian kernel package comes with. This kernel runs perfectly. I pass --initrd to make-kpkg when building the package but no initrd is built when I install it so I have to make it using "mkinitramfs -o /boot/initrd.img-2.6.33 2.6.33" to get it to boot. Now when I try to build the nvidia drivers it complains it can't find the source. I did build kernel_headers and installed them also the source is in /usr/src/linux. I also tried to specify the path by passing --kernel-source-path= to the nvidia script but no change. What is going on? I've done this fifty times before and never had any problems. Has there been some changes to how debian kernel packages are built? EDIT: Just thought I'd add some info about the steps I took.
Code: tar xjvf linux-2.6.33.tar.bz2 ln -s linux-2.6.33 linux cd linux patch -p1 < ../fbcondecor-0.9.6-2.6.33-rc7.patch cp /boot/config-2.6.32-trunk-686 ./.config
make menuconfig Loaded .config then I removed support for maxtorfb, tile blitting and some sirrusfb thing, nothing thats relevant to my system. Changed cpu from Pentium 4 to Core 2 and added framebuffer decor support from my patch, exited and saved. Then:
[Code]....
EDIT2: I have now tried to build 2.6.32.8 in the same way with the same strange results, anyone have any thoughts as to what I'm doing wrong just throw it at me, I'm getting desperate and running out of ideas. I've checked all the kernel source symlinks and everything looks good.
Hi,I'm using a Dell Lattitude D620 laptop. I just installed the latest kernel 2.6.38 in my Squeeze amd64 :
Output of uname -r 2.6.38-bpo.2-amd64
Now I'm running on new kernel,everything seems fine except my wifi ( now I'm connected through ethernet ). Before I do the process with the guide in http://wiki.debian.org/wl to activate my wifi,I'd like to ask for some advice here,is this latest kernel support my wifi card? If yes,how to activate it?
I have been getting some compile errors here and there and have read that possibly I need to install the kernel-devel package.I am running 2.6.33.4 which I built from source.I have also built and installed the kernel-headers.I cannot find the kernel-devel for 2.6.33.4 anywhere, can I build it myself from the kernel source?
I'm trying to use module-assistant to add the vboxdrv using instructions also found here in the debian forum. However, m-a can't find the linux-headers because it looks for the package linux-headers-2.6.32-5-trunk-686. I attempted to specify were the headers were by using: m-a prepare --kernel-dir /usr/src/linux-headers-2.6.32-5-686/ but also doesn't work. Instead, I get the error: Bad kernel version specification at /usr/bin/m-a line 566. Anyone knows how to work around this? By the way, the reason I am doing this is because when I installed virtualbox (following the instructions in debian wiki) there's no vboxdrv. When I try to modprobe it, I get: FATAL: Module vboxdrv not found.
Below is the recipe I've used to compile dwm from source on Squeeze
su apt-get install devscripts debian-keyring apt-get build-dep dwm exit
It all seems to work, however debuild gave an error about secret keys. Is this a sensible procedure? What happens in the (probably unlikely) event there is another source patch?I've gone to a tiling window manager as the result of the purchase of a wide screen LCD monitor. I like to have some stuff down the right hand side when running Firefox and OpenOffice in the main panes. Any configuration tricks welcome. Modern screens are the wrong shape!
I was trying to install VPN client for my Ubuntu 9.10 64-bit. During the installation process the terminal reads:
"Directory containing linux kernel source code [/lib/modules/2.6.31-21-generic/build]"
On that I pressed enter for the default option (in bold). After a few more steps I reached the following error:
Making module sh: Can't open ./driver_build.sh Failed to make module "cisco_ipsec.ko".
[/lib/modules/2.6.31-21-generic/build] is the location where the installer expects the kernel source to be (I am guessing). So unless I correct the terminal (by providing the location of the kernel source), I think I will keep on getting the same error message.
So to get the kernel source I visited: [URL]From there I copy pasted the command:
