When I build the kernel 2.6.30 source, the rpm package is very big and needed or root filesystem 800-900 Mb. I use "make rpm" as described in Configure, Build and Install a Custom Linux Kernel - openSUSE.
I'm new to linux and recently installed openSUSE 11.1 on my Lenovo Thinkpad SL500. So far it's great... only problem is the hotkeys and brightness control don't work. Digging around online I found this "experimental" driver that purportedly works fine, but I have no idea how to compile, install, or otherwise use it. Here... tetromino's lenovo-sl-laptop at master - GitHub I'm not sure what to do with the makefile and C file provided. For example, what do I do with this instruction...
"To enable the brightness control, load the module with the "control_backlight=1" module parameter (i.e. insmod lenovo-sl-laptop.ko control_backlight=1 )" I know someone on here will be able to explain how to do this in a "computer engineering for chemists" language! I'm comfortable enough working in the terminal with commands, but have found no real straightforward explanation of how to do so (only "programming" experience is MATLAB m file writing).
I am trying to build a custom kernel but I couldn't. Here are the steps to reproduce it: 1. Set Up an RPM Build Environment as its is explained in [URL] 2. Then follow the instructions in [URL] 3. When I try to install the kernel source rpm I get the following error:
[matias@Centos ~]$ rpm -i [URL warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root . . . warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root error: unpacking of archive failed on file /home/matias/rpmbuild/SOURCES/linux-2.6.18.tar.bz2;4ba24901: cpio: read
I used make-kpkg to build the 3.0.0 source debian wheezy on a dual 3.4GHz Xeon/L1-16k/L2-1mb/800Mhz bus with 4GB PC2-3200 ECC ram and Ultra 320 SCSI, using CONCURRENCY_LEVEL=4 (2 hyperthreading cpus=4 cores). The build was slower than molasses in January! Top reported cpu usage total between 10% and 25%. Why won't the build use the amount of machine it has available. One footnote: I wasn't using swap space. It literally took over an hour to build the deb kernel package.
My notebook from 2003 is at least three times faster building the 3.0.0 debian kernel source. Is it possible that this might cause improvement: make -j4 KDEB_PKGVERSION=version deb-pkg
Could amd64 vs. i386 have some influence? Could the small processor caches on the XEON cpus have an effect. The 64-bit machine absolutely flies doing everything else. I'm miffed! I've used debian since woody, although I am not an expert, but I'm no slouch!
I just rebuild the kernel for slackware 13, everything works, but root file system which is ext3 is mounted as ext2. Normally I've build ext3, ext4 and so on as modules, not in the kernel... but if I do this, then the kernel mounts the file system as ext2, which is build in the kernel. I also modified rc.modules so I can make sure that ext3,ext4,jbd are loaded, but it doesnt work.
i need to install openSUSE 11.2 from an USB stick. I followed this article SuSE install from USB drive - openSUSE using the openSUSE-11.2-NET-i586.iso. Unfortunately the kernel provided in this image doesn't load on my target as it needs a few extra modules for its chipset.
Thus i copied our custom kernel (which is verified to run on the target) and its initrd to the usb stick and i also created a new entry in the syslinux.config. The kernel loads, but then it can't find the root device.Does anybody know, how i need to configure the initrd to make the USB stick the root device?
If you can access Suse Studio here is thlink to the buildLFS Host - SUSE GalleryGoogle hasn't been friendly and neither has a search on these forums, I don't know which man to read so a finger in the right dirrection (preferably not the middle) would be nice as far as that goesRight now the yast live installer trips up at %84 while saving the boot loader configuration and displays a popup that says �An error occurred during initrd creation. /sbin/mkinitrd: illegal optionI then press enter to acknowledge the message and the installation continues without a hitch.
When I go to boot up (no other os installed) grub says it cant find the file initrd-2.6.34.7-0.5-defaultIf you boot the live cd again you can mount the boot partition and you�ll find a broken symlink called initrd that islooking for the missing file above.Like I said above, if it an obvious fix, all I need is some direction, I don't mind reading. (been doing that all day)If you need more specifics Id be happy to supply, I'm just not sure whats relevant and don't want to bloat the post.
I'm trying to install some wireless drivers, but apparently I don't have a /lib/modules/<kernel>/build directory, which is causing the Makefile to throw an error. Is there a specific place I should point the Makefile at?
We have an appliance with image being installed from CD/DVD installation This appliance image is based on CentOS 4.7 kernel/installer/etc. Everything works fine, we ship this product for about 2 years. Recently I had to move it (port everything) to CentOS 5.5 Everything went fine and it works fine except one minor thing )) We can't install it from CD/DVD image yet. Actually it start fine, finds kickstart file, creates partitions correctly, copies install image to harddrive, but fails the next step when it tries to install RPM's
The message we get:
Quote: the file termcap-5.5-1.20060701.1.noarch.rpm cannot be opened. This is due to a missing file, a corrupt package or corrupt media. Please verify your installation source. If you exit your system will be left in an inconsistent state that will likely require re-installation"
After troubleshooting the lockup problem on my installation of Lucid, I want to wipe the thing and reinstall. I have an integrated Broadcom wireless chipset that I want to integrate the firmware into the new Lucid install disc, along with Nvidia's 180.06 drivers for my GeForce4 440 Go (yes, it's an old machine). I need to build this from XP though, since my current Lucid install is to the point of unusable.
Is there any good way to do that? With XP builds you can use nLite to slipstream just about anything into a clean XP install, including all available hotfixes, extra drivers and a few applications. Is there a similar program for building Ubuntu installs that can do that as well? Also, if I download a new ISO of Lucid to build from, will it have all the current updates integrated, or it be up to me to do it? Edit: just realized I posted this under the wrong topic.
I've a problem running jessie on a XEN supervisor; my running kernel and the installed kernel image differ, because the host system forces the kernel at boot time. Current loaded kernel is
Code: Select all$ uname -r 3.18.12
But I'm not able to install this version from the standard repository.
Code: Select all# apt-cache search linux-image linux-headers-3.16.0-4-amd64 - Header-Dateien für Linux 3.16.0-4-amd64 linux-image-3.16.0-4-amd64 - Linux 3.16 für 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) linux-image-amd64-dbg - Debugging symbols for Linux amd64 configuration (meta-package) nvidia-kernel-3.16.0-4-amd64 - NVIDIA binary kernel module for Linux 3.16.0-4-amd64 linux-image-2.6.32-5-xen-amd64 - Linux 2.6.32 for 64-bit PCs, Xen dom0 support
Now I'm facing issues loading kernel modules for iptables, because the module path does not exist. Is there an easy way to install a proper kernel image from the standard repositories?
I am building a series of custom kernels...for one of them i am using a kernel that is older than my currently installed ones.
I am using rpm to install this kernel and it will not install, period. i don't get why i can't install this....what does it matter that i am installing an older kernel? and why is fedora/rpm designed to not let me do this?
Code:
There should be an easy way to get around this, but i haven't figured it out yet. i've googled around, no luck. i bounce between kernel versions all the time without problems on my system, so why is rpm setup for strict versions on a kernel? and is there no way around this, and i just have to delete all three of those kernels, i don't really want to. 2 of them are awesome and i shouldn't have to build them again, that would be complete crap! and i wouldn't have this problem on my debian setup, so why fedora? (i generally think fedora is better)
That's it guys. I have successfully installed the proprietary ati drivers in past 6.34 and 6.35 kernels but not in latest .6.36. I'm wondering if this have something to do with compatibility or not.
Installation log shows me some errors I can't recognize:
This is from Centos 5.5 so I apologize to anyone who may be offended.I installed my system and it came with kernel 2.6.18-194.el5. I installed the src.rpm of this kernel with rpm, patched, and built it. Then I did a yum -y install kernel.i686 which installed kernel-2.6.18-194.32.1.el5.centos.plus.src.rpm. Since this was a yum install, why doesn't this new kernel version show in the BUILD and SPEC directory?
I need to install Ubuntu on approximately 50-60 netbooks. None of them have CD drives, and I don't want to have to install them individually, walking around with a USB stick. I figured the fastest way to install on so many machines is to use a combination of apt-cacher (http://www.debuntu.org/how-to-set-up...ith-apt-cacher) and netbooting. I have successfully booted one machine to test, but as soon as the kernel comes up, support for the network interface is gone. Specifically, the "atl1c" module is not included on the netboot initrd image. Also, I would like to try to use preseeding, and I need to get that onto the initrd as well.
So, to summarize my question: How can I create a custom install kernel and initrd? I have a feeling it's related to the "debian-installer" category in the package repository, but I have not found any good documentation about doing this.
I'm in the process of making my own build using SUSE Studio build service. I was hoping if someone would kindly tell me about kernel-firmware, what it does and if it is absolutely necessary because I noticed that it is not selected for you by default. Any other useful firmware that I may need. I have already included the b43-firmware, ar9170-firmware, bluez-firmware, and ivtv-firmware in my build based on openSUSE 11.4.
I am having trouble in configuring xorg.conf. I am running Suse 11.3 desktop on my PC. Also, I have one onboard nvidia graphics 6150SE and I have put one nvidia 8400GS 512Mb in the 16X PCIe slot for the additional seat...
So kindly tell me what should I do now or what things are missing ?? For any further info abt my PC plz tell me to post outputs(specify the commands for the same..)
I followed The Perfect Server - Debian Lenny on howtoforge website. (Just changed some instructions to fit Sqeeze) * I did not install Control Panel, just software like LAMPP & Mail Servers - SMTP(SSL+AUTH) + POP(SSL) + IMAP(SSL).When I installed PHP it installed it with Suhosin Patch, but that patch was giving me a headache with some web scripts that I write for myself. So I decided to compile it for myself. Here is how I done it:
I know how to get root access in iConnect and ssh into it. I wanted to know whether we can install any applications on it using the package manager and what package manager it supports, like apt(debian based) or is it based on some other distribution.
I'm trying to install the nVidia driver for a fresh Installation of OpenSUSE 11.4 (32-bit) but I'm running into some issues. I followed the instructions (SDB:NVIDIA the hard way - openSUSE) using the driver binary mentioned in the workaround link (NVIDIA DRIVERS 256.53 Certified) but the installer fails while building the kernel module with the following errors:
Code: nvidia-installer log file '/var/log/nvidia-installer.log' creation time: Sun Mar 13 17:32:56 2011
scanning them with Avast! and Malwarebytes Anti-Malware or by running registry cleaners like Ccleaner.However, I think it would be cool to have a Live system that I could boot from my flashdrive that I could have programs installed to do all this with.It would be cool if I could use Puppy Linux, since it loads and runs from RAM, which gives a huge speed boost when compared to running a live version of a distro like Ubuntu, but I don't really know my way around Puppy, or how to make my own "pupplet". Also, from what I could tell, Puppy Linux didn't have a package manager like Pacman or Aptitude.Here's a list of programs I would like to have a Linux alternative to use:-Avast! Anti-virus-Ccleaner (registry cleaner)-Malwarebytes Anti-Malware/Superantispyware (malware/spyware cleaner)-Perhaps also a Defrag program like Defraggle
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'm running CentOS 5.3 and would like to know what the "best" or "proper" method is to build a custom kernel using the generic kernel sources from kernel.org. Most of the references I've found talk about modifying the current CentOS kernel using the RPM way. I really want to have the latest kernel due to some important security issues that haven't been addressed in the current CentOS 5.3 kernel.
Just spent three whole days barking up the wrong tree, solving Fedora 11 and Fedora 12 boot failures because the correct hypothesis was illogical: installation did not update/modify the initrd.
The first couple of times I installed Fedora 11 on the HighPoint Technologies RocketRaid 2640x4, the installation inserted my "custom" driver module (rr26xx) into the initrd, permanently, so that the system booted off the controller card for which the custom driver was inserted. (I yelled about this success in this thread: [url]
My most recent installs of BOTH F11 and F12 on the RocketRaid failed to properly set up the boot. It turns out that the "rr2640" module I "slipstreamed" into the installation process was *NOT* permanently added to the initrd by anaconda. (F12 gave me "no root device found boot has failed, sleeping forever", on boot; F11 hung also, without such error, I presume, during the init script execution). Because of limited resources and time, I only know for sure the module was missing from the F11 initrd, and am ASSUMING the same was the case with F12.
The only difference between the successful installs and the ones with failed boot is that the successful installs were made on a single-drive (JBOD) mode on the controller; whereas, the failed ones were placed on RAID 5. But, AFAIK, the created logical device for the card is "/dev/sda", in both cases, and the kernel can not distinguish between the two cases (or can it?). Thus, the inconsistency cost me a lot of time, and is still inexplicable to me.
Question: What is the best way to deal with custom drivers, today? There are custom spins, and many tools, like isomaster. Stupid question: Is there a way to modify the initrd inside an installer ISO -- be it for CD/DVD/USBboot drive -- beefing the init RAM disk with whatever modules you'd like, for the boot process (using, say, isomaster)?
And what makes anaconda understand that a module must be added to the initrd ? How can one force anaconda to do so?
How does moving to dracut as the initrd tool affect any/all of the above?
I'm in love with my Opensuse 11.2. Love my KDE 4.4. The only thing I miss from my Ubuntu installation, is the ability to use Boxee. I would be more than willing to compile Boxee from source. I only have 2 problems with that:
1) I don't know where I can find all the build-deps or what they are for that matter to build Boxee.
2) I'm running on a Netbook. Yes, my measly Intel Atom is no fun for compiling and building.
What are my options/what can I do to get Boxee up and running on 11.2? I've tried searching on build service for an RPM, but I think due to legal restrictions, Boxee can't be on there.
looking for LIBEVENT... configure: error: Package requirements (libevent >= 2.0.10) were not met: In order to build transmission 2.21.I need libeventnew version of transmission,I need to build libevent-dev >= 2.0.10 and installed first.But I can't get any information about building development files for libevent.
A few days ago yast did update my computer to a new kernel-desktop 2.6.31.12-0.1.1.
My mainboard is an ASUS P4P800-VM with Intel ICH5 chipset. This new kernel is not able, to poweroff my computer. Older kernels were able to poweroff the computer.
How can I roll back to the older kernel? Yast does only offer the recent kernel.
In /boot there are only files of the recent kernel.
ASUS P4P800 Intel Pentium 4 HT, 3000 MHz, Frontside 800 MHz/Cache 1 MB 3 GB Ram AGP nVidia 7600GS/512 MB, nVidia driver 190.53, installed from yast. PCI WLan TP-Link 951N (Atheros chipset, WLan N, driver ath9 was automatically installed)