LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices


Reply
  Search this Thread
Old 07-02-2002, 03:42 PM   #1
RCarter
LQ Newbie
 
Registered: Jun 2002
Distribution: RedHat 7.2
Posts: 7

Rep: Reputation: 0
Question Compiling and installing a new kernel in RedHat7.2


I'm using RedHat7.2 kernel version 2.4.7 with the GRUB loader and I'm trying to change to kernel version 2.4.2. I downloaded the source from www.kernel.org: linux-2.4.2.tar.gz; and saved it to /usr/src. Then I ran the following from that directory:

tar -xvzf linux-2.4.2.tar.gz
cd /usr/src/linux
make mrproper
make oldconfig
make dep
make clean
make bzImage
make modules
make modules_install
make install

However, exiting the make install with an error 1 and 2 (whatever that means).

Anyway, going a bit further I copied the /usr/src/linux/arch/i386/boot/vmlinuz* to the /boot directory with a separate name from the old one and modified the grub.conf file and added an entry for the new kernel.

When rebooting I was offered the choice to run the old kernel 2.4.7 and the new one 2.4.2 with the latter not installing and the former running fine.

I'm probably not performing some necessary steps, although I have no idea what they might be. Anyone have any idea?
 
Old 07-02-2002, 11:07 PM   #2
mlp68
Member
 
Registered: Jun 2002
Location: NY
Distribution: Gentoo,RH
Posts: 332

Rep: Reputation: 32
Did you perhaps already have a kernel sitting in /usr/src/linux and you untar'ed the new one over it?
You don't mntion any configuration, did you configure the kernbel at all? (with make xconfig or make config?)

Why are you going back to such an old kernel? It has lots of problems, bugs, etc.

Have a look at gthe kernel-howto. Pretty good.

Martin
 
Old 07-03-2002, 06:25 AM   #3
Phonics3k
Member
 
Registered: Jun 2002
Location: Wales, UK
Distribution: Gentoo 2005.1
Posts: 213

Rep: Reputation: 30
you do not need to do make bzImage if u do make install coz the only diff between them is that make bzImage does not move the file when make install does.

I would use the newest kernel source to: kernel 2.4.18 at the time of me writing this
 
Old 07-03-2002, 03:21 PM   #4
RCarter
LQ Newbie
 
Registered: Jun 2002
Distribution: RedHat 7.2
Posts: 7

Original Poster
Rep: Reputation: 0
I did not see the /usr/src/linux until after I did the tar. There was a /usr/src/linux2.4 and /usr/src/redhat. And the old kernel 2.4.7 is working fine, so I guess I didn't do any damage yet.

I read somewhere that doing make oldconfig was sufficient for the configuration?

So I'm guessing that running the make install was a mistake then? I'm pretty sure that make bzImage went fine. I'm going to give it another go.

The reason I need the 2.4.2 is an ADSL network adapter from ITeX. The only working drivers for this adapter seem to work in 2.4.2 only. I thought I'd try and install them anyway - following the logic that if it works in a lower version, it must work with a higher one. But no. So I'm left with this.
 
Old 07-06-2002, 07:57 PM   #5
RCarter
LQ Newbie
 
Registered: Jun 2002
Distribution: RedHat 7.2
Posts: 7

Original Poster
Rep: Reputation: 0
Partial success. I went through the same steps but skipped the last part (make install). Then I copied the bzImage and renamed it and edited the grub.conf accordingly. However with the exception of initrd (that was the reason I couldn't boot the 2.4.2 before); I just used the old reference (i.e. from the working kernel). Anyway, the damn thing runs with only a couple of failed operations at start up - but I've lost the sound, and the printer, and ... Guess I'll be keeping my eye on: LinuxQuestions.org Forums > Linux - Software > New kernel question.
 
Old 07-06-2002, 08:14 PM   #6
neo77777
LQ Addict
 
Registered: Dec 2001
Location: Brooklyn, NY
Distribution: *NIX
Posts: 3,704

Rep: Reputation: 56
Open the Makefile in kernel source tree
there you'll see the first lines look something like this

VERSION = 2
PATCHLEVEL = 5
SUBLEVEL = 24
EXTRAVERSION =

then in order to create initrd for it
use
in my case
/sbin/mkinitrd /boot/initrd-2.5.24.img 2.5.24
in yours
/sbin/mkinitrd-2.4.2-EXTRAVERSION(if any).img 2.4.2-EXTRAVERSION(if any)
this step can be performed no earlier than make modules, so I'd suggest to do it right after you compiled modules for your kernel

Last edited by neo77777; 07-06-2002 at 08:16 PM.
 
Old 07-06-2002, 09:03 PM   #7
RCarter
LQ Newbie
 
Registered: Jun 2002
Distribution: RedHat 7.2
Posts: 7

Original Poster
Rep: Reputation: 0
Thanks, I'll give it a try.

Anyway, while booting the error messages I get are something like this:

mounting local filesystem: fs type ext3 not supported by kernel ..

And running depmod -a (with the ouput in /var/spool/mail/root):

###################### LogWatch End #########################

From root Sun Jul 7 00:09:20 2002
Return-Path: <root@localhost.localdomain>
Received: (from root@localhost)
by localhost.localdomain (8.11.6/8.11.6) id g6709KX01608
for root; Sun, 7 Jul 2002 00:09:20 GMT
Date: Sun, 7 Jul 2002 00:09:20 GMT
From: root <root@localhost.localdomain>
Message-Id: <200207070009.g6709KX01608@localhost.localdomain>
To: root@localhost.localdomain
Subject: LogWatch for localhost.localdomain



################## LogWatch 2.1.1 Begin #####################


--------------------- ModProbe Begin ------------------------

Can't locate these modules:
tmpfs: 6 Time(s)
eth0: 2 Time(s)
ext3: 6 Time(s)
ppp0: 7 Time(s)
vfat: 1 Time(s)

**Unmatched Entries**
modprobe: Can't locate module char-major-108: 28 Time(s)
modprobe: Can't locate module char-major-6: 3 Time(s)
modprobe: Can't locate module net-pf-16: 4 Time(s)
modprobe: Can't locate module net-pf-16 : 6 Time(s)
modprobe: Can't locate module sound-service-0-0: 7 Time(s)
modprobe: Can't locate module sound-service-0-3: 2 Time(s)
modprobe: Can't locate module sound-slot-0: 5 Time(s)


---------------------- ModProbe End -------------------------



--------------------- sendmail Begin ------------------------

2961 bytes transferred
1 messages sent

**Unmatched Entries**

NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: cannot bind: Cannot assign requested address
daemon MTA: problem creating SMTP socket
NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: cannot bind: Cannot assign requested address
daemon MTA: problem creating SMTP socket
NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: cannot bind: Cannot assign requested address
daemon MTA: problem creating SMTP socket
NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: cannot bind: Cannot assign requested address
daemon MTA: problem creating SMTP socket
NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: cannot bind: Cannot assign requested address
daemon MTA: problem creating SMTP socket
NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: cannot bind: Cannot assign requested address
daemon MTA: problem creating SMTP socket
NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: cannot bind: Cannot assign requested address
daemon MTA: problem creating SMTP socket
NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: cannot bind: Cannot assign requested address
daemon MTA: problem creating SMTP socket
NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: cannot bind: Cannot assign requested address
daemon MTA: problem creating SMTP socket
NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: cannot bind: Cannot assign requested address
daemon MTA: problem creating SMTP socket
NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: cannot bind: Cannot assign requested address
daemon MTA: problem creating SMTP socket
NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: server SMTP socket wedged: exiting
NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: cannot bind: Cannot assign requested address
daemon MTA: problem creating SMTP socket
NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: cannot bind: Cannot assign requested address
daemon MTA: problem creating SMTP socket
NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: cannot bind: Cannot assign requested address
daemon MTA: problem creating SMTP socket
NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: cannot bind: Cannot assign requested address
daemon MTA: problem creating SMTP socket
NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: cannot bind: Cannot assign requested address
daemon MTA: problem creating SMTP socket
NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: cannot bind: Cannot assign requested address
daemon MTA: problem creating SMTP socket
NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: cannot bind: Cannot assign requested address
daemon MTA: problem creating SMTP socket
NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: cannot b
 
Old 07-06-2002, 10:05 PM   #8
RCarter
LQ Newbie
 
Registered: Jun 2002
Distribution: RedHat 7.2
Posts: 7

Original Poster
Rep: Reputation: 0
The first lines of the makefile:

version = 2
patchlevel = 4
sublevel = 2
extraversion =

Now, regarding your recommendation, I'm doing exactly what? Running that as a command (results in nothing) or adding that to the makefile? My first Linux steps are installing a new Kernel in order to get the internet going. It doesn't get much better than that.
 
Old 07-07-2002, 12:05 AM   #9
mlp68
Member
 
Registered: Jun 2002
Location: NY
Distribution: Gentoo,RH
Posts: 332

Rep: Reputation: 32
The initrd is for somewhat special advanced applications, such as pre-loading stuff you need *before* you can even get at the boot disk, such as pre-loading a SCSI or a RAID driver. The initial redhat installation does that because it's easier to maintain a huge variety in hardware ( I think that's why).

Your problem is easier. Run "make xconfig", and at the top of the right row of buttons you should see "Filesystems". Click on that and enable ext3 file system support. If that's disabled, go back to the main GUI, click on "Code maturity level options", and check "Prompt for development and/or incomplete drivers" - because ext3 is still tagged "experimental", it won't show you that unless you ask for the experimental stuff. You cannot build ext3 as a module but MUST compile it in the kernel (the Y option) - remember that the kernel already needs ext3 support in order to get at the disk in the first place ( I guess that's how we got into initrd's here). That will take care of the ext3 problem.

Then I see that eth0 shows up in the missing modules list. If you build that ADSL card driver, you must tell the system about it in /etc/modules.conf. There must be an entry
alias eth0 <whatever the driver name is>
mine reads
alias eth0 8139too
because I have such a card.

The rest seems to be some soundcard stuff - run sndconfig which *may* add the missing entries. You should have an idea what sound card you have, and then enable, build and install the driver (enable in the GUI right row 3rd entry).

Why don't you post the /etc/modules.conf file, the output of lsmod, and the output of
ifconfig -a
Then it's easier to get you more specific answers. What is the name of that driver?

Martin
 
Old 07-07-2002, 02:00 PM   #10
RCarter
LQ Newbie
 
Registered: Jun 2002
Distribution: RedHat 7.2
Posts: 7

Original Poster
Rep: Reputation: 0
Martin, thanks for spending time on this.

Following your recommendations, I went straight to step 1 (tar, etc.) and the make xconfig: Going into Filesystems, I couldn't find any reference to ext3 support, however I enabled kernel automounter, dos fat, umsdos and the vfat. So on the upside, I can now run: mount -t vfat /dev/hdax /mnt/winx. But I'm still booting kernel 2.4.2 with the same error messages as before.

Also, I followed your recommendation on the "Code maturity level options".

But I guess the whole thing is probably related to the grub.conf file, which looks like this:

=====================================

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,1)
# kernel /vmlinuz-version ro root=/dev/hda3
# initrd /initrd-version.img
#boot=/dev/hda2
default=0
timeout=10
splashimage=(hd0,1)/grub/splash.xpm.gz
password --x
title Red Hat Linux (2.4.7-10)
root (hd0,1)
kernel /vmlinuz-2.4.7-10 ro root=/dev/hda3
initrd /initrd-2.4.7-10.img
title Red Hat Linux (2.4.2)
root (hd0,1)
kernel /bzImage-2.4.2 ro root=/dev/hda3
initrd /initrd-2.4.7-10.img
title DOS
rootnoverify (hd1,0)
chainloader +1

=======================================

What follows "title Red Hat Linux (2.4.2)" is something I added to the file. Regarding the "initrd /initrd-2.4.7-10.img", I tried running "initrd /initrd-2.4.2.img", but that resulted in a failed boot. However, running like this and selecting 2.4.2 at boot time, it boots with the above error messages. I guess ignorance is bliss, but I know I'm doing something wrong here. The folder /boot, only contains 2 items though: bzImage and the kernel. Seems like there's some read/write protection involved - which is a good thing I guess, since kernel 2.4.7 is running perfectly through all this.

The /etc/modules.conf looks like this:

====================================

alias parport_lowlevel parport_pc
alias eth0 ne2k-pci
alias sound-slot-0 via82cxxx_audio
post-install sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -L >/dev/null 2>&1 || :
pre-remove sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -S >/dev/null 2>&1 || :
alias usb-controller usb-uhci

==================================

The name of the card is AC97 Audio Controller (it's on the motherboard, manufactured by VIA Technologies, and the driver is via82cxxx-audio -> and I have Creative Ensoniq AudioPCI97 (ES1371) enabled in xconfig).

Anyway, running "sndconfig" returned the following:

====================================

ERROR: No Sound Modules found

You don't seem to be running a kernel with modular
sound enabled. (soundcore.o was not found in the
module search path).
To use sndconfig, you must be running a kernel with
modular sound, such as the kernel shipped with Red Hat
Linux or a 2.2 or greater kernel.

======================================

Funny thing with Ismod: there's no such file or command. ?

Anyway, ifconfig -a returned the following:

===================================

[root@localhost root]# ifconfig -a
lo Link encap:Local Loopback
LOOPBACK MTU:16192 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

[root@localhost root]#

=====================================

Now, regarding the ADSL, I managed to complete the following (with a partially failed boot under 2.4.2) steps provided by the manufacturer - http://www.itexinc.com/ (who have, by the way, been extreemely helpful in not answering any e-mails):

==================================

GS-P200X Linux for RFC1483


Notices on the Linux:

· This driver supports only Linux Kernel v.2.4.2.
(Check the Linux kernel version by typing ‘cat /proc/version’)
· Make sure there is no other ADSL related driver software installed in the system.
· Select Gnome or KDE workstation during the Linux OS installation.
· The minimum display resolution needs to be 800 * 600.


Driver Installation / Configuration:

1. Install the Linux driver for RFC1483.
a. Log in to Linux as root user.
b. Driver file format is itex1483-<version>.o, which version is identified for which Linux kernel being executed.
For example, if the kernel version is 2.2.14, use itex1483-2.2.14.o. If the kernel version is 2.4.2, use itex1483-2.4.2.o, and so forth.
c. Copy it to local directory from floppy diskette, CDROM drive.
If the Linux 1483 driver is in floppy diskette, execute ‘mount /mnt/floppy’.
If the Linux 1483 driver is in CDROM, execute ‘mount /mnt/cdrom’.
Then, copy it to local directory, say /tmp.
‘cp /mnt/<cdrom or floppy>/itex1483-2.2.14.o /tmp’

2. Write your own installation script (itex-up) or just issue commands manually step by step as below to load the driver.
a. insmod -f itex1483-2.2.14.o vpi=8 vci=35 framing=1
b. ifconfig eth1 192.168.2.133 netmask 255.255.255.0 broadcast 192.168.2.255

Change the values in bold above. (vpi, vci, framing, eth#, ip address, netmask)
Framing (encapsulation):
0 LLC routed
1 LLC bridge (default)

Note: Please make sure which number of eth# interface is available for GS-P200X driver. You can check out this by running ifconfig command or simply doing a visual inspection to see how many Ethernet cards (e.g. n) are installed in the system already. Then the next available number for GS-P200X NIC will be n+1.

3. Check whether the driver was loaded successfully or not by executing ‘lsmod’. You also can use ‘dmesg’ command to see what the message the driver dump.

4. Observe the modem connection status.
GS-P200X provides a customized utility which is also called ‘ifconfig’. You can have the following commands to monitor the DSL line status. This is the same as the one Linux provided except some GS-P200X functions added.

./ifconfig eth1 rate ; get the DSL modem status & rate information
./ifconfig eth1 disconnect ; disconnect the DSL line
./ifconfig eth1 connect ; handshake with the default mode: ANSI T1.413 issue2
./ifconfig eth1 connect dmt ; handshake with the ITU G.dmt mode
./ifconfig eth1 connect lite ; handshake with the ITU G.lite mode
./ifconfig eth1 version ; get the driver module version & compile date

Note: Before you want to re-connect, make sure you’ve already disconnected the DSL modem.
Once you load the driver module, it will handshake automatically with the ANSI mode.

5. Configure the GS-P200X RFC1483 device.
a. Use ifconfig to change the IP address just like ethernet device.
b. For example: ifconfig eth1 192.168.2.134

6. PPPoE protocol configuration (optional).
Download Roaring Penguin PPPoE client package from http://www.roaringpenguin.com/pppoe/. Refer to the package installation guide to install PPPoE RPM package. Locate adsl-setup, adsl-start, adsl-stop script files under PPPoE package installation directory.
a. Run adsl-setup script file to setup PPPoE client network parameters.
b. Run adsl-start script file to start PPPoE session.
c. Run adsl-stop script file to stop PPPoE session.

7. End-to-End connection test (optional).
Run Ping, FTP, Web Browsing, Streaming Video tests to verify the driver performance and stability. RedHat 6.2 has built-in FTP client. For Web Browsing test, you need setup Proxy server in RFC 1483 server to forward HTTP requests. For Streaming Video test, download and install RealPlayer and RealServer in client and server sides, respectively.



Remove the driver module:

1. Run ‘ifconfig eth1 down’
2. Run ‘rmmod itex1483-2.2.14’ depending on what you have loaded (see lsmod).

============================================


Everything went according to plan, up to and including running the software from roaringpenguin. However, the program is asking for an internet reference (as a connection point - e.g. [www.]serviceprovider.com - skipping the "www"), whereas I'm provided with a phone number from my service provider. But that's a problem for another day.
 
Old 07-13-2002, 10:39 PM   #11
RCarter
LQ Newbie
 
Registered: Jun 2002
Distribution: RedHat 7.2
Posts: 7

Original Poster
Rep: Reputation: 0
Anyway, I just installed kernel 2.4.16 following the directions and instructions included above. Went pretty much according to plan (including the ext3, which was included in the xconfig menu this time). The soundcard was just a question of selecting the proper options in xconfig (- speaking of which: make oldconfig does not return a satisfactory result). With the exception of the initrd.* file (I haven't been able to find the damn thing - (find . -name 'initrd*' -print ... returns nothing)). Keeping the old reference seems to work fine though, moving up. Why fix it if it ain't broken? The lesson: hell, I don't know; if you're downgrading, you're up shit creek? Anyway, thanks to all who took part. Have a nice day?
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
compiling installing kernel modules Wordan Linux - Software 3 11-02-2005 08:22 AM
Installing (Compiling?) the new 2.6.1 kernel LilGryphMaster Linux - Newbie 9 01-31-2004 10:45 PM
Compiling and Installing Kernel under SuSE 9 bschneider Linux - Newbie 6 12-19-2003 10:46 AM
Compiling and Installing Linux Kernel 2.4.18 kramk2 Linux - Software 4 09-04-2003 08:01 PM
Installing RedHat7 CropA Linux - Software 7 07-03-2001 11:42 AM


All times are GMT -5. The time now is 02:55 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration