I tried to build linux-2.6.36 but I got this error message
Code:
I looked into gcc-version.sh but the problem is located somewhere else I thought at first one of the files might have been corrupted and I downloaded the archive again.
I must also say that this happened in different versions of slackware (the distro I use): 12.0, 12.1, 12.2, 13.0, 13.1
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:
[Code]....
I am using Centos 5 with an old kernel. I want to build the latest version for atheros 5K wireless drivers. So i downloaded, and compiled with the ".config" which is already in /boot , and made it ready to run.
However, whenever i try to boot with new kernel, after choosing it from the grub menu, i got the following error. I tried many many .config files but the result was the same.
Here is the screen capture of the error;
I'm trying this process for a week without any success...
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.
I opted to install my Linux Fedora distribution, in a SUN VM (Virtualbox). [URL] I have 2 questions:
My current max res available to select is 1024x768. Can I run at 1920x1200? My display indicated that it is 'Unknown'. I don't know if that is in on the deal, or not...
Second question: When installing VBOXADDITIONS_3.1.2_56127, I am getting the error: Building the VirtualBox Guest Additions kernel modules [FAILED]
If I am displaying the log correctly, it indicates: Makefile:23: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again.. Stop Pictures are located here, in the EVGA Linux forum: [URL] I am new to both Linux, and Fedora.
My mission statement: To run Linux using the Fedora distribution, in a VM window under Windows 7 64bit Ultimate, with the ability for scripting using Bash, with the Perl programming language installed, and use Apache Tomcat to monitor both apps, and various VM installs, on numerous Servers via the internet.
I am trying to build linux kernel I am getting out of space after a while. I unpacked it in /usr/src directory. It seems I have plenty of space. How much space does it need to compile & build kernel. I am using VirtualBox.
root@vinay-VirtualBox:/usr/src/linux-2.6.39.3# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 6.9G 3.2G 3.4G 49% /
none 669M 640K 668M 1% /dev
none 675M 24K 675M 1% /dev/shm
none 675M 96K 675M 1% /var/run
none 675M 0 675M 0% /var/lock
/dev/sr0 39M 39M 0 100% /media/VBOXADDITIONS_4.0.10_72479
I installed openSUSE 11.2 on virtualbox. My host is windows 7. I tried to install the guest additions, but i get an error saying
Code:
Building VirtualBox Guest Additions Kernel Modules...Failed
(Your system does not seem to be set up to build kernel modules)
How should i go about to let my system build kernel modules?
while building a package i got this error. Package name is python-gnomecanvas and i am working in debian.
I am not able to get it correct.
I'm building a 3-node cluster. I have created ocfs filesystems and mounted them on the first two nodes. But while mounting them on the third node , i'm getting this error for 8 of the total luns. all these 8 luns are of 1GB size.
I've unmounted these 8 luns from the other node and tried to mount in the third node ... and then it was working and again the error occurs in the second node. My observation was for some reason these particular luns are not allowing the third node.
mount.ocfs2: Invalid argument while mounting /dev/mapper/voting1 on /voting1. Check 'dmesg' for more information on this error.
dmesg output was :
I'm using RHEL 5.4
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?
I am trying to update my fedora 8 kernel, is there a way to do that? I build the one of kernel.org but when i want to boot it a get a lot of messages like:
mount: cant find /dev/root
I tried to follow the guide at building a custom kernel for fedora, but thats just for the last supported version of the kernel of fedora 8.
I am using FC15.I need a kernel with a different configuration - with the "Preemptible Kernel (Low-Latency Desktop)" option in the Processor Type and features menu. I need this to support my firewire audio device. I would like to build a new kernel RPM from the SRPM so that i can keep a clean system with RPMs for all files, and I don't really want to manually override the kernel bypassing RPM.I am following **exactly** the process described there - I install the SRPM, unpack the source, then use the starting sample config files in the BUILD folder to create a new customised .config file with the new option, then copy this back to the SOURCE folder.
This works perfectly if I make a standard kernel. But I cannot get the process to work if I change the config file. Every time I compile I end up with exactly the standard kernel -- a vanilla i686 kernel, without my custom config.I believe the problem is that when I run rpmbuild to compile the kernel, this process overwrites my config option. I found that there is a script (merge.pl) which creates new config files dyanmically for all kernel options based on fragments in the SOURCE folder. It looks like the script never uses the config file that I am putting into the SOURCE folder.The wiki page suggests using this command to copy my custom config file cp .config ~/rpmbuild/SOURCES/config-`uname -m`
I have an x86 pc and installed lucid these are the details of my distribution version:
I am trying to build a kernel module i am getting the following error:
How to build kernel modules
I'm trying to set up a netbook I purchased that has a lot of more recent hardware, and so I'm having to compile some kernel modules on my own. I've installed Debian on this particular system, and so the version of gcc that was used to compile the kernel is older than the one currently in the repos. Now, I've installed the version I need, but can't remember how to specify building the modules in question with said version.
I've done this in the past, and recall temporarily changing some variable to use the different version, but it's been a while and I just can't remember. Is there an easier way to do this on the fly for any compilation? Or is changing a variable necessary? If there is no way to explicitly specify gcc version used prior to a compilation, could someone remind me of the variable I need to change to use x.x.x version?
Since there was a lot of talk about virtualization I thought I try kvm -- before I used VirtualBox. I took the SlackBuild from SlackBuilds.org and got an error with u8 as type in /usr/include/scsi/scsi.h. (sorry, I don't have the exact error message anymore..) I searched for its definition and I only found __u8 in /usr/include/linux/types.h. Then I searched the web and found a "fix" which says I have to change u8 from /usr/include/scsi/scsi.h to __u8. This problem was solved, but when I run the SlackBuild now it stops at some point and I don't know why. These are the last few lines of output:
CC arm-softmmu/translate.o
CC arm-softmmu/tcg/tcg.o
CC arm-softmmu/tcg/tcg-runtime.o
CC arm-softmmu/fpu/softfloat.o .....
LINK i386-softmmu/qemu
AR arm-softmmu/libqemu.a
LINK arm-softmmu/qemu-system-arm
root@tux:/home/christian/Downloads/kvm#
I put an echo after the make for building kvm and I put an echo after "make install". None of them are printed.
I have builded my kernel through wiki manual, BUT, the kernel-headers rpm-package has not been builded. Now i have only two packages: kernel and kernel-devel. Is that ok? (i think, that it is not ok, because when i build the same version of kernel on x86_64 platform, after rpmbuild command i have kernel, kernel-devel and kernel-headers packages) My CentOS version is 5.2; platform i686; kernel, kernel-headers, kernel-devel packages 2.6.18-92.el5.
View 6 Replies View RelatedDell laptop booting from a USB stick with a CentOS 5.5 minimum installation.
Uncompressing Linux...OK, booting the kernel.
Red Hat nash version 4.2.1.13 starting
sda: assuming drive cache: write through
sda: assuming drive cache: write through
mount: error 6 mounting ext3
mount: error 2 mounting none
switchroot: mount failed: 22
umount /initrd-dev failed: 2
Kernel panic - no syncing: Attempted to kill init!
1. Does minimum installation not drop on a kernel or initrd with ext3 support? I can't imagine that's true, but have to ask.
2. The USB stick is single partition ext3. Maybe there is some limitation specifically related to USB stick booting that requires boot to be FAT16 or FAT32? Except the CentOS 5.5 installer refuses to let me install on either FAT.
3. How can I do the equivalent of lsmod on a linux installation that will not boot? i.e. I have CentOS x86_64 running in VirtualBox, I can plug the USB stick in there, so how do I get information on the USB stick's kernel and initrd if I can't boot from it?
4. Is it possible to rebuild the i386 based initrd on this USB stick, when the computer is not booted from that stick, with a system that's x86_64 based?
System Info:
Dell Latitude i686 Laptop which has run CentOS 5.5 and Fedora 12,13,14 in the past, and boots from Fedora 14 Live CD transferred to a USB stick. So I know USB booting is possible on this machine, and this stick.
The process of creating the stick:
CentOS 5.5 i386 on a USB stick. Old Dell i686 laptop which has previously run CentOS 5.5 installed from DVD, and has successfully booted from this same USB stick holding transferred Fedora 12,13,14 Live CDs. CentOS 5.5 was installed onto the USB drive directly by the CentOS 5.5 DVD installer (running virtualized in VirtualBox 4.02 on Mac OS X 10.6.5.). No errors or complaints during installation.
For whatever reason, the installer did not do some things correctly. First Grub wasn't working correctly, I got that sorted out and have the Grub+CentOS splash screen, it finds vmlinuz and the initrd, and then I get a kernel panic.
Ext3 was built into the kernel and that's why I'm getting this message. I do not know how the installer would have dropped a kernel or initrd during instalation that that don't contain such a basic thing that obviously comes in linux kernel 2.6.18-89 EL.
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?
Supposed I have built customized kernel rpm four times in a row and the latest built kernel failed. If I still have all four kernel.xxx.rpm files, is there any way that I could get back the .config file used for each of those four builds? I really could not recall exactly what changes I had made in .config for each build.
View 3 Replies View RelatedI have a brand new installation of 13.37 but I can't seem to get the nvidia-kernel (64 bit only) Slackbuild from slackbuilds.org to build. I have the nvidia driver installed and working on 13.1 so I am not desperate yet: although I thought that it could just be something with the older Nvidia driver so I waited for the updated release but it fails in the same way.I have uninstalled xf86-video-nouveau and installed xf86-video-nouveau-blacklist-noarch-1.txz from /extra.I have also installed libvdpau from SBo. The nvidia-driver Slackbuild builds fine.I am using the stock 2.6.37.6 huge kernel but have also tried the 2.6.38.4 kernel from /extra and the 2.6.38.7 kernel from Slackware-current.Here is the error message I am seeing:
Code:
root@DarkStar:/home/server/Utils/Packages/Slackware/13.37/64/nvidia-kernel# SRCSUFFIX="-no-compat32" ./nvidia-kernel.SlackBuild
[code]....
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)
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'd like to have a shot at building FBReader 12.1 from source for use within F12 (kernel 2.6.31.9-174.fc12.i686.PAE) but am having problems locating the following .rpm files:
libz and libbz2 -- libraries for zip and bzip2 (de)compression
libfribidi -- for bidirectional text support
lincurl, version >= 7.17 -- for network libraries integration
I've only a small /boot sector and
rpm -qa | grep kernel
kernel-2.6.31.12-174.2.22.fc12.i686
kernel-PAE-devel-2.6.32.9-70.fc12.i686
kernel-PAE-2.6.32.9-70.fc12.i686
kernel-2.6.32.9-67.fc12.i686
abrt-addon-kerneloops-1.0.8-2.fc12.i686
I'm using the PAE kernels, need the devs for nvidia kernel building,can I remove all the non PAE kernels without damage please?
I have a problem with PAE kernel sources and builing nvidia driver. uname -a returns Linux myX 2.6.31.12-174.2.3.fc12.i686.PAE #1 SMP Mon Jan 18 20:06:44 UTC 2010 i686 athlon i386 GNU/Linux
1. I run ./NVIDIA-Linux-x86-173.14.22-pkg1.run and I get an error message that kernel sources cannot be found.
2. My folders: /lib/modules had these two subfolders 2.6.31.5-127.fc12.i686.PAE 2.6.31.12-74.2.3.fc12.i686.PAE so what I did, I run: yum install kernel and got inside /lib/modules this extra 3rd subfolder (no PAE) 2.6.31.12-174.2.3.fc12.i686 On the other hand /usr/src/kernels has one subdirectory (no PAE): 2.6.31.12-174.2.3.fc12.i686
3. Now, when I build nvidia driver, it still gives me the error, that no sources found, so I do
./NVIDIA-Linux-x86-173.14.22-pkg1.run --kernel-source-path /usr/src/kernels/2.6.31.12-174.2.3.fc12.i686 and get an error that this seems to be the incorrect version. And I guess this is true as I have no PAE sources.
4. Further, when I look at
[Code]...
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.
Trying to build C source code using Gcc 2.95.2 and Solaris make for the x86 platform. Got the a following error
/usr/local/bin/gcc -c -D_KERNEL -DSUNDDI -I. -Wall -Wstrict-prototypes
-Wmissing-prototypes hdrcpci2_mini.c
In file included from /usr/include/sys/varargs.h:50,
from /usr/include/sys/systm.h:58,
[Code]....
Is this a gcc compiler problem or due to some missing macros?
I'm trying to port binutils to a new architecture. I have changed and created necessary files for this. The configure commad run succusfuly. but when I tried to run make I find probems. the error msg is:
View 1 Replies View RelatedI am currently working on Debian based Operating System, and my objective is to make a live CD.
I ve followed the specified steps to buid a live CD, and finally I ve made an .iso file too.
Now,I am facing some issues to execute that .iso on Qemu(Virtual Interface),those are:
1. While builing it into an .iso,I skipped the md5sum step, is that mandatory to be built for making a live CD?
And when I am trying to make an MD5SUM using the following command, Its giving me the following error:
Kindly specify me, where exeactly the error in the command for creating the md5sum?
2. While executing the .iso file in Qemu using the following command :
And the I am able to watch the Operating System booting initialization and then when I select the option as "Install as Live CD" Its giving me the following error:
I request who ever reads this thread, please send me some kind of a response.I'll be thankful to them.
I get the following error when i build dspace.
View 1 Replies View Related