General :: Configuration Of New Kernel For Redhat?
Feb 18, 2011how to install new own kernel in Redhat 5. Can i install Debian kernel in redhat ?
View 2 Replieshow to install new own kernel in Redhat 5. Can i install Debian kernel in redhat ?
View 2 RepliesHow to upgrade kernel in redhat linux 5 ?
View 2 Replies View RelatedHow to configure repository in my standalone system to resolve dependencies so that i will not have to install all the rpms in my system by typing rpm -ivh and the name of rpm.
View 4 Replies View RelatedI use Redhat 2 server, the server suddenly can't boot now , it goes to the grub> mode, it can't boot to Redhat kernel
View 5 Replies View RelatedI cant mount a directory on red hat 5 from red hat 4 using fstab.I keep getting permission denied.I mount directories on the same red hat 5 sys from other red hat 5 and 2 old HPUX systems using fstab.When I try to telnet to it i get "no route to host."
View 3 Replies View RelatedMy company support a client with an old Redhead server " Linux version 2.6.9-5.ELsmp [URL] (gcc version 3.4.3 20041212 (Red Hat 3.4.3-9.EL4)) #1 SMP Wed Jan 5 19:30:39 EST 2005" My IT department wants to move this old server to a VMware machine and I'm trying to check if this project can fly. Me my self never worked on an old Linux server there for my first question is can I upgrade the kernel with the command yum -y install kernel..... and when I'm done I'm still going to have the old kernel just in case?
View 1 Replies View RelatedI have the pirated redhat 5 in my notebook. Now I need to do yum configuration. But for this we need the baseurl. I don't know the baseurls for downloading some important packages.
View 3 Replies View RelatedInstallation of CVS on Redhat linux
Installing CVS on Redhat Linux Redhat Enterprise 4.0
The following steps give simple steps to install CVS software on Redhat Enterprise Linux 4.0.
1) Download the tarball cvs-1.11.1p1.tar.gz
2) Run "gunzip cvs-1.11.1p1.tar". You will get file called cvs-1.11.1p1.tar.
3) Then extract this file using command
"tar -xvf cvs-1.11.1p1.tar".
4) Then go to directory cvs-1.11.1p1.
5) There you will find a file called INSTALL. Read it once carefully.
6) Now run the command "./configure."
7) Build it using the command "make".
8) Install binaries/documentation using command "make install".
9) Now open file called /etc/services and add the following lines.
Cvspserver 2401/tcp # CVS client/server operations
cvspserver 2401/udp # CVS client/server operations
10) Open file called /etc/xinetd.conf and add the following lines to that file.
service cvspserver
{
Port = 2401
socket_type = stream
protocol = tcp
wait = no
user = root
passenv =
server = /opt/bin/cvs
server_args = --allow-root=/home/cvs -f pserver
env = HOME=/home/cvs
log = /var/log/cvslog
}
11) Space on both sides of = in the above file is a must.
12) Restart xinetd services by running command " services xinted restart "
13) Check whether CVS is running on the port 2401 by using the following command "nmap IP |grep 2401". If the CVS server is running correctly it will give output as "2401/tcp open cvspserver ".
It doesn't output like "2401/tcp open cvspserver"
how to setup ftps & sftp in RHEL 5.4 Server.
View 4 Replies View RelatedI have had Linux running in our product that has several serial ports.(Another Ethernet to Serial port translator). It has been running OK for about 6 years, using kernel 2.6.11, then 2.6.18. Now I just got 2.6.39.1 running and suddenly I get these "I/O Possible" messages and my programs shutdown. I found elsewhere that the cure for this is to put a "signal(SIGIO, SIG_IGN)" call to stop this signal from crashing the program. This works, but I would really like to know the reason that this started happening in the first place.
Could there possibly be a 'config' option I missed that causes this? It just surprises me that the kernel writers would implement something that has such a large impact on the existing code base, causing anyone using serial ports, or anything else that might trigger a SIGIO, to have to edit, recompile, and redistribute their programs.
How to change the kernel behavior, short of going in and hacking the kernel. Or at least an idea as to why they would have changed the default behavior.
I am writing a C program (recovery utility) that needs to run at boot. I have found my way into this (booting a kernel) and now I want to configure the kernel so that it doesn't take a lot of space and compile fast so that I can edit the source afterwards and make it run my program on the kernel's startup.for the least size. The only thing this program needs is reading and writing files in all of the local hard disks (and some standard libraries such as stdio.h and stdlib.h) so I can keep the kernel simple by removing a lot of stuff such as networking, encryption algorithms and others. What would be the best configuration for this, so that it is really small in size? Should I simply start a new configuration and then only select things that I need, or should I take the "default" configuration and start removing things? What options are a MUST to make the kernel run?
View 1 Replies View Relatedyum installation and configuration in details on Redhat / Centos 5.0
View 1 Replies View Relatedhow to install redhat 6 beta kernel source rpm under CentOS 5.5? I just download the kernel source rpm-- kernel-2.6.32-19.el6.src.rpm. And I tried run "rpm -i ", it was failure. The error message is "error: unpacking of archive failed on file /home/xliang/rpmbuild/SOURCES/Fedora-KVM-allow-userspace-to-adjust-kvmclock-offset.patch;4bf439e4: cpio: MD5 sum mismatch"
View 7 Replies View RelatedHow to troubleshoot curropted Grub configuration in Redhat Enterprice Linux 5.
View 2 Replies View RelatedI have looked at the GNU GRUB Manual 1.99 at [URL] but I cannot find an explanation of what the kernel entry / command in the grub.conf file means. I get what's the meaning of that entry but where is described what it actually is and what are proper.
I suppose this entry / command was actual in GRUB Legacy, but I cannot find where it is described...
I accidentally deleted my .config for my kernel configuration on Linux, and seem to remember there was a way to retrieve the kernel configuration via the proc filesystem somehow. Is this still possible, and if so how would I do it?
View 1 Replies View RelatedI 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?
View 12 Replies View RelatedI 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".
View 1 Replies View RelatedI 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.
View 2 Replies View RelatedI 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 had Windows XP working. I then put in a new hard disk and installed Redhat 5 on it. rom then i could only boot into Redhat. Further, everyting is very slow. Anothe rproblem is that Redhat does not see my netwrok so I cannot get onto the Internet. I need to have the choice of booting into XP or Redhat.
View 2 Replies View RelatedRight now i have a HP DL 180 Server with 130 Gb Hard Disk & 8 Gb ram after Raiding0+1. i want to configure Domain Controller Server for my office for 200 to 300 Users. what should the partition size must be mentioned in my 130 Gb Hard Disk, is that going to be Sufficient for ME ?
i am bit confused about /Usr /Var /Boot partitions, as i need to manage perfectly in 130 GB
if i go with 4 Gb swap and remaining for " / " is that will be fine ? should i need to specify partition sizes separately for / tmp /var / usr ..
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?
View 5 Replies View RelatedI 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)
[Code] .....
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:
View 1 Replies View RelatedMy girlfriend got a 'new' (second hand) laptop, a HP Compaq 6715s. When I tried to install Debian on it, the install went immensely slow - glacial, even. It was a very minimal install but it tooks hours to get to nowhere.
I found out online that this was because of a problem between the current kernel and the hard drive (or HD bus, something hardware-y to do with the disk) which meant file operations were extremely slow. I thought "easy, patiently install Debian and then install newer kernel". Except that after six hours, the install wasn't even halfway.
So I install Arch Linux with the 2.6.35 kernel: no problems with the drive speed at all. After a lot of researching (I only played around with Arch once, more than a year ago) I got the system into a usable state. But now wlan0 has suddenly disappeared, together with some other problems - and a usable laptop wasn't exactly what I had in mind, it was supposed to be awesome (or at least good). Which, with Debian, it would be
So... is it possible to make a Debian installation use a later version of a kernel? I'd want to install Debian with the 2.6.35 kernel, not install Debian and then afterwards update the kernel (because I don't have 24 hours to install an OS, if it'll ever even install).
I've found some stuff online but it might well have been written in the Cyrillic alphabet. All I understand, I think, is that in theory it's possible.
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.