Debian Configuration :: Address Prior To Building The Latest Kernel (2.6.33.4)?
May 13, 2010
Got this while installing the kernel development tools on my Squeeze system being used as a router/firewall. Setting up update-inetd (4.36) ... Setting up cvs (1:1.12.13-12) ... Ignoring install-info called from maintainer script The package cvs should be rebuilt with new debhelper to get trigger support Ignoring install-info called from maintainer script The package cvs should be rebuilt with new debhelper to get trigger support Setting up autopoint (0.17-11) ...
Is that an issue that I need to address prior to building the latest kernel (2.6.33.4)?
I upgraded my kernel in my Debian Lenny to version 2.6.32-bpo.4-amd64 to fix a problem with a software and ALSA-related issues. The thing is that now, when I boot, eth1 is not enabled and I have to "load" (I guess) the driver each time. To do this, I go to the folder where all the files for the drivers are and I run:
modprobe lib80211 and then insmod wl.ko
That I got from the readme file. That gets the wireless working perfectly again, but when I reboot the wireless is dead again and I have to run the commands above again. I imagine that what I should do is to build the driver again, for my new kernel. However, according to the readme file, before I need to install linux-headers-generic and build-essential. With build-essential, it says it's already the newest version, and with the linux-headers, I don't know which one should I install for my kernel! I thought it would be the linux-headers-2.6.32-bpo.4-xen-amd64, but when I tried that, this is what happened:
debian:/home/hernan/Programas/hybrid_wl# apt-get install linux-headers-2.6.32-bpo.4-xen-amd64 Reading package lists... Done Building dependency tree
[code]....
So the warning says something about the MODULE_LICENSE being missing... how to build the driver again to make it load each time I boot?
For quite a long time now, I haven't even needed to re-install video drivers most of the time. However, ever since version 2.6.36-0.dmz.4, they haven't been. I booted my system after installing that kernel, re-installed the video drivers, and when that didn't work, completely removed them and re-installed them, and it still didn't work. Well, I was told that the installation was successful but even after restarting it appeared that they weren't working. I installed 2.6.36-0.dmz.5 today and the same problem persists. I tried an older kernel version (2.6.36-4 something) and they worked fine.
This may sound ridiculous, but after installing Debian 5 (from CD 1) in my laptop, ASUS UL80VT, it fails to detect the Ethernet device. The device is "Atheros AR8131 PCI-E Ethernet Controller". I guess the problem comes with the old kernel of version 5. I was intending to compile the latest kernel anyway. But the problem is is there any heads up i need to download the kernel and trying to compile it? Is there anyone who uses Debian on UL80VT. If there is, does it works okay?In short I want to compile the latest kernel, hoping it will fix the Ethernet device. There are installers available with the latest kernel. But I want to do it on my own.
The latest in experimental is 1.1... the stable by upstream is 1.2 and the latest unstable is 1.3. So is there a repository where I can get the latest unstable automatically?
I need address of ftp server that has the latest .iso of Debian testing (weekly build).unfortunately, cdimage.debian.org/cdimage/weekly-builds/ is useless to me as it does NOT support ACTIVE FTP.
I'm trying to build the kernel module for dvbhdhomerun. The problem is the linux kernel headers provided by Debian do not have the dvb header files. Trying to set up my own kernel source tree to use is not working out so well.
I'm following the instructions in the Debian section here: [URL] ....
My first try compiled, but the modules ender up under /lib/modules/3.2.51/extra instead of /lib/modules/3.2.0-4-amd64/extra. Why?
I tried to start over, but noticed this while running apt-get source linux-image-3.2.0-4-amd64:
Code: Select allReading package lists... Done Building dependency tree    Reading state information... Done Picking 'linux' as source package instead of 'linux-image-3.2.0-4-amd64' NOTICE: 'linux' packaging is maintained in the 'Svn' version control system at: svn://svn.debian.org/svn/kernel/dists/trunk/linux/
[Code] ....
The failure to verify the signature has me concerned, but beyond that, what do I do about the different version number when compiling and installing the kernel modules?
Apparently, the wireless adapter Realtek 8171 uses the rtl8192se driver, which is currently available only as source from Realtek's website. Is building a driver equal to building a package? Should I follow the same cautions, say these ones?
How do I force recompilation of the kernel .deb packages. After a small change I make to the sources without having to clean the sources and recompile the whole kernel again?
Code: Select all$ fakeroot make -f debian/rules.gen setup_i386_none_686 $ fakeroot make -f debian/rules.gen binary-arch_i386_none_686 binary-indep
Calling the second command again does not recompile the modified code, just recreates the .deb packages.
If I use:
Code: Select all$ make -f debian/rules clean before the build command, then it will recompile everything which takes ages.
How can I force recompilation of the files/objects I changed (and dependencies)?
I use this guide: [URL] .... ('Building only a single kernel variant' section)
I am running Lenny and using VirtualBox OSE 1.6.6. In order to try squeeze I installed it in a VM. I tried to install Guest Additions also, but i get this error:
VirtualBox 1.6.6 Guest Additions installation Building the VirtualBox Guest Additions kernel module... Building the shared folder support kernel module... Unable to build the kernel module.
I checked what /var/log/vboxadd-install.log had to say:
/usr/src/linux-headers-2.6.32-5-common/include/net/neighbour.h:115: error: variably modified a at file scope /tmp/vbox.0/utils.c: In function 'sf_path_from_dentry:
[code].....
I tried with 3 versions of the kernel 2.6.32-5-686,2.6.32-5-484,2.6.32-3-686 but I cannot get it to work using any of them. Also I tried to install version 2.6.30-2-686 but I couldn't since synaptic said that it Depends: linux-kbuild-2.6.30 but it is not installable.
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.
Since an Aptitude upgrade to my Debian Squeeze operating system (using video driver NVIDIA-Linux-x86-195.36.24) some weeks ago, which installed linux kernel 2.6-32-5-686, grub has been giving me two boot options (in addition to MS Windows). I expect that this is quite normal so far ...
However, if I try to boot using this new kernel, rather than kernel 2.6-32-3-686, I can only get the command line interface. Everything seems to work after boot with the new kernel, except (although the system seems to load kdm successfully) I cannot start X. Booting with the old kernel still takes me to the desktop as normal (I've set KDE to automatically bypass kdm, as I'm the only user of this standalone PC), and because of this I've been slow to address the issue with kernel 2.6-32-5-686, but since the problem doesn't seem to be going away with more recent upgrades, I suppose a request to the forum is the only way to go:
So, is the problem I'm having the same as was addressed in this thread? If not, would I only need to reinstall the same NVIDIA video driver so that it recognises the new kernel? If not, would installing NVIDIA-Linux-x86-256.35 solve the problem, and would I have to deinstall the old video driver first? Finally, if and when I solve the problem, can I safely deinstall the old 2.6-32-3-68 kernel?
I'm trying to install the latest version of Clamav (0.95.3), but I'm getting the following error messages in Synaptic after adding the recommended repository to my sources:
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".
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 installed squeeze on virtualbox on arch linux.After squeeze is booted up, ifconfig says no ip address is given to eth0.I tried ifdown/up eth0, then an ip address was properly given.Does anyone have the same problem or know how to solve this?The network of virtualbox is set to bridged adapter.The host os has only eth0, no br0 and wiredly connected to a wifi router which has the dhcpd.
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 ubuntu on my laptop recently and would like to have trim support. (Because I have a ssd drive (crucial c-300 256gb). The current kernel that I am using is the 2.6.32 (standard lucid kernel I believe). Unfortunately TRIM support is only available from 2.6.33 and up. So I thought I'd install a new kernel using this howto:
I am thinking about upgrading, again, from Wheezy to Jessie. When I had Jessie installed, prior to a crash, I noticed that some of the Gnome games in Jessie are not as esthetically pleasing as they were in Wheezy. Also, some of the games (eg. mines) were slower and seemed to use a lot more CPU resources. So my questions are:
1. If I pin those programs that I want to keep will that also pin the dependencies for those programs? 2. If those dependencies are pinned, how might that impact other programs, in Jessie, that might depend on later packages? 3.If I don't pin those programs that I want to keep is it possible to install those programs from Wheezy after I upgrade to Jessie, without causing issues with Jessie?
I got the Raspberry pi 2 Model B. I flashed my sdcard with raspberian Jessie kernel 4.1 (latest).Also tried wheezy and NOOBS, same behavior.With a ethernet cable (known working), I tried connecting my Pi to my home router, and I got a invalid ip address 169.254.xxx.xxx, and therefore no linkup. I got the same results by connecting my Pi directly to my modem (wired).
I know that /etc/dhcpd.conf is the new /etc/network/interfaces for network configurations.So I tried the debug option, and I noticed that the router doesn't seems to response to the DISCOVER command from the Pi (dhcp v4 protocol).Here's a dump of by /var/log/syslog | grep dhcp
Code: Select allDec 28 12:00:02 raspberrypi systemd[1]: Starting dhcpcd on all interfaces... Dec 28 12:00:02 raspberrypi dhcpcd[349]: version 6.7.1 starting Dec 28 12:00:02 raspberrypi dhcpcd[349]: udev: starting Dec 28 12:00:02 raspberrypi dhcpcd[349]: dev: loaded udev Dec 28 12:00:02 raspberrypi dhcpcd[349]: eth0: disabling kernel IPv6 RA support
[code]...
ANd if i use raspbian flesh out of installation, I get this when i run
dhcpcd -k dhcpcd eth0 eth0: probing for an IPv4ALL address eth0: using IPv4ALL address 169.154.202.224
Seems like my home router TP-link (default setup) doesn't send a response to the dhcp request.
My sources list for updates is a bit wonky as in needs the correct uk repositories listed, for Lenny main, could someone point me to where I can find the uk repositories so I can enter then in the software sources option from the menu?
This is embarrassing. I can't get a wireless address from my router with dhclient. The distribution is sid/lxde/liquorix kernel with no network manager on /dev/sdb1.
root@sid:/home/jheaton5# dhclient -4 -v wlan0 Internet Systems Consortium DHCP Client 4.1.1-P1 Copyright 2004-2010 Internet Systems Consortium.
I'm running gnome desktop on squeeze system. When I boot my system seems to be using my internet modem as its dhcp server. The rest of the machines on my lan are correctly using my router for that purpose. As a result, what happens then is that my debian machine frequently gets a duplicate ip address assigned to it. I would like to specify to my debian computer that I want it to use the specific fixed ip address of my router for dhcp purposes.
location where I can download Debian 5.0.0 or any Debian 5 prior to 5.0.8? I've checked some of the archive sites but they seem to only go up to Debian 4.
i have the basic knowledge of networking. a week ago i installed debian Lenny version on an old pentium 3. in addition i installed a ddclient configured it according to many tutorials.i searched google a few days but didnt find my case. i ran the folowing command :
Hey guys. I have a client computer PXE booting from my host computer and it is supposed to give the client the ip address 172.16.0.100 however instead it gives it the ip address 172.16.0.208.
I have this set up working with two other computers and there is no noticeable difference other than mac addresses for the network card.
Here is an extract from my '/etc/dhcp3/dhcpd.conf' file...
I have quadruple checked the mac address of the client and it is definitely "00:07:E9:32:16:81" so why is it not giving it the IP address that I have specified?
I want to configure multiple virtual ethernet interfaces over a single physical ethernet interface (eth0) and for each virtual interface the MAC address must be unique and the IP address must be Static.Finally all the virtual interfaces must be able to communicate both internally and externally and the traffic should be captured using wireshark.
I need to have such kind of setup to communicate devices individually using one physical ethernet device.
Because I was fiddling with few kernel modules like MACVLAN and MACVTAP and successfully enabled those modules and rebuild kernel. Using macvlan and macvtap I can configure virtual interfaces with unique mac address and static IPs but while capturing packets using wireshark interfaces behave weirdly.
For example say on HOST machine I have 1 physical interface and created 3 virtual interfaces as shown below.
First from above interfaces I started pinging eth0 internally from host machine in which it worked as usually.
Second I did same externally from other machine which is connected to the same network of Host machine, and this did work as usually.
Third I pinged first virtual interface veth0 both internally and externally and this also works and after that I did check source and destination MAC address using wireshark tool-where both showed up there respective MAC address.
Now triggers the issue, where I pinged second virtual interface same like I did for first one, but this time ping was success and where as in wireshark tool the MAC address for veth0 is picked by veth1. This is where I got stuck and this issue happened for all the remaining virtual interfaces.
I couldn't see any virtual interface showing their respective MAC address, as of the remaining except the first virtual interface has been picking the first veth0 mac address.
