* reconfiguring sound after kernel upgrade
@ 2005-02-28 5:17 bj
2005-02-28 17:27 ` Eric Bambach
0 siblings, 1 reply; 4+ messages in thread
From: bj @ 2005-02-28 5:17 UTC (permalink / raw)
To: linux-newbie
Hi !
I am using Red Hat 8.0 .
When I installed it , it had kernel 2.4.18-14 .
I downloaded and did a rpm -uvh .
Currently is has kernel version 2.4.20-30.8 legacy .
Now as I try to re-install sound by install the following , I get library
error .
I have downloaded and unzipped the below files.
alsa-driver-1.0.8
alsa-lib-1.0.8
alsa-oss-1.0.8
alsa-tools-1.0.8
alsa-utils-1.0.8
oss
Now when I run make command it gives the following error.
cd alsa-driver-1.0.8
./configure -->no error
./make ----> the following error
make[1]: *** No rule to make target
`/lib/modules/2.4.18-14/build/include/linux/config.h', needed by
`memalloc.o'. Stop.
make: *** [compile] Error 1
Running ls command on my /lib/modules gives the following :-
2.4.18-14
2.4.18-19.8.0uml
2.4.20-30.8.legacy
2.4.20-30.8.legacybigmem
2.4.20-30.8.legacyBOOT
2.4.20-30.8.legacysmp
I guess each directory is for the each kernel rpm I ran .
How do I point to make to the library of 2.3.20-30.8 legacy and successfully
install my alsa driver .
Thanks in advance.
cheers,
bj
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: reconfiguring sound after kernel upgrade
2005-02-28 5:17 reconfiguring sound after kernel upgrade bj
@ 2005-02-28 17:27 ` Eric Bambach
2005-03-01 5:21 ` bj
0 siblings, 1 reply; 4+ messages in thread
From: Eric Bambach @ 2005-02-28 17:27 UTC (permalink / raw)
To: bhamal; +Cc: linux-newbie
On Sunday 27 February 2005 11:17 pm, bj wrote:
> Hi !
--snip--
> cd alsa-driver-1.0.8
> ./configure -->no error
> ./make ----> the following error
>
> make[1]: *** No rule to make target
> `/lib/modules/2.4.18-14/build/include/linux/config.h', needed by
> `memalloc.o'. Stop.
> make: *** [compile] Error 1
It looks like you are running 2.4.18 kernel version and trying to compile
programs for another vesion. Boot into your 2.4.20 legacy kernel and try
again.
Uname -a will show you what you are currently running.
The problem is that the configure scripts detect your currently running kernel
when you want to compile for a different one. The simplest way to fix this is
to boot into the new kernel so the configure scripts can detect *THAT*
version.
Oops, I also just saw another problem. You must make sure that a kernel is
CONFIGURED at that directory. You will need to install not only the kernel
binary RPMS, but make sure you install the source along with it. It cant find
config.h because you havent ran make menuconfig or similiar in that directory
and generated the config files for alsa to use.
HTH
--snip--
> Thanks in advance.
>
> cheers,
> bj
--
----------------------------------------
--EB
> All is fine except that I can reliably "oops" it simply by trying to read
> from /proc/apm (e.g. cat /proc/apm).
> oops output and ksymoops-2.3.4 output is attached.
> Is there anything else I can contribute?
The latitude and longtitude of the bios writers current position, and
a ballistic missile.
--Alan Cox LKML-December 08,2000
----------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: reconfiguring sound after kernel upgrade
2005-02-28 17:27 ` Eric Bambach
@ 2005-03-01 5:21 ` bj
2005-03-01 18:44 ` Eric Bambach
0 siblings, 1 reply; 4+ messages in thread
From: bj @ 2005-03-01 5:21 UTC (permalink / raw)
To: eric; +Cc: linux-newbie
-----Original Message-----
From: linux-newbie-owner@vger.kernel.org
[mailto:linux-newbie-owner@vger.kernel.org]On Behalf Of Eric Bambach
Sent: Monday, February 28, 2005 11:13 PM
To: bhamal@wlink.com.np
Cc: linux-newbie@vger.kernel.org
Subject: Re: reconfiguring sound after kernel upgrade
On Sunday 27 February 2005 11:17 pm, bj wrote:
> Hi !
--snip--
> cd alsa-driver-1.0.8
> ./configure -->no error
> ./make ----> the following error
>
> make[1]: *** No rule to make target
> `/lib/modules/2.4.18-14/build/include/linux/config.h', needed by
> `memalloc.o'. Stop.
> make: *** [compile] Error 1
It looks like you are running 2.4.18 kernel version and trying to compile
programs for another vesion. Boot into your 2.4.20 legacy kernel and try
again.
Uname -a will show you what you are currently running.
The problem is that the configure scripts detect your currently running
kernel
when you want to compile for a different one. The simplest way to fix this
is
to boot into the new kernel so the configure scripts can detect *THAT*
version.
Oops, I also just saw another problem. You must make sure that a kernel is
CONFIGURED at that directory. You will need to install not only the kernel
binary RPMS, but make sure you install the source along with it. It cant
find
config.h because you havent ran make menuconfig or similiar in that
directory
and generated the config files for alsa to use.
HTH
--snip--
> Thanks in advance.
>
> cheers,
> bj
--
----------------------------------------
--EB
> All is fine except that I can reliably "oops" it simply by trying to read
> from /proc/apm (e.g. cat /proc/apm).
> oops output and ksymoops-2.3.4 output is attached.
> Is there anything else I can contribute?
The latitude and longtitude of the bios writers current position, and
a ballistic missile.
--Alan Cox LKML-December 08,2000
Hi !
Thank you for the prompt reply .
The result of uname -a is as follows:-
Linux home 2.4.20-30.8.legacy #1 Fri Feb 20 17:47:48 PST 2004 i686 i686 i386
GNU/Linux.
I did boot into the new kernel that is 2.4.20-30.8.legacy .
my "ls -la /boot " gives the following .
I am suprised at the result of the make command of the alsa sound.
ANy new ideas ?
I plan to do a ivh on the rpm instead of uvh (upgrade) of the kernel
Below is the result of 'ls -la /boot'
total 22048
drwxr-xr-x 3 root root 4096 Feb 25 10:49 .
drwxr-xr-x 19 root root 4096 Mar 1 09:15 ..
-rw-r--r-- 1 root root 5824 Sep 5 2002 boot.b
-rw-r--r-- 1 root root 612 Sep 5 2002 chain.b
-rw-r--r-- 1 root root 38724 Dec 12 2002
config-2.4.18-19.8.0uml
-rw-r--r-- 1 root root 44762 Feb 20 2004
config-2.4.20-30.8.legacy
-rw-r--r-- 1 root root 44855 Feb 20 2004
config-2.4.20-30.8.legacybigmem
-rw-r--r-- 1 root root 54321 Feb 20 2004
config-2.4.20-30.8.legacyBOOT
-rw-r--r-- 1 root root 44814 Feb 20 2004
config-2.4.20-30.8.legacysmp
drwxr-xr-x 2 root root 4096 Feb 4 23:02 grub
-rw-r--r-- 1 root root 133424 Feb 4 23:00
initrd-2.4.20-30.8.legacybigmem.img
-rw-r--r-- 1 root root 125898 Feb 4 23:01
initrd-2.4.20-30.8.legacyBOOT.img
-rw-r--r-- 1 root root 130032 Feb 4 22:59
initrd-2.4.20-30.8.legacy.img
-rw-r--r-- 1 root root 132904 Feb 4 23:02
initrd-2.4.20-30.8.legacysmp.img
-rw-r--r-- 1 root root 473 Feb 25 10:49 kernel.h
-rw-r--r-- 1 root root 23108 Sep 6 2002 message
-rw-r--r-- 1 root root 21282 Sep 6 2002 message.ja
lrwxrwxrwx 1 root root 30 Feb 4 22:59 module-info ->
module-info-2.4.20-30.8.legacy
-rw-r--r-- 1 root root 15436 Dec 12 2002
module-info-2.4.18-19.8.0uml
-rw-r--r-- 1 root root 15438 Feb 20 2004
module-info-2.4.20-30.8.legacy
-rw-r--r-- 1 root root 15438 Feb 20 2004
module-info-2.4.20-30.8.legacybigmem
-rw-r--r-- 1 root root 15438 Feb 20 2004
module-info-2.4.20-30.8.legacysmp
-rw-r--r-- 1 root root 640 Sep 5 2002 os2_d.b
lrwxrwxrwx 1 root root 29 Feb 25 10:49 System.map ->
System.map-2.4.20-30.8.legacy
-rw-r--r-- 1 root root 342101 Dec 12 2002
System.map-2.4.18-19.8.0uml
-rw-r--r-- 1 root root 519482 Feb 20 2004
System.map-2.4.20-30.8.legacy
-rw-r--r-- 1 root root 545075 Feb 20 2004
System.map-2.4.20-30.8.legacybigmem
-rw-r--r-- 1 root root 329824 Feb 20 2004
System.map-2.4.20-30.8.legacyBOOT
-rw-r--r-- 1 root root 545040 Feb 20 2004
System.map-2.4.20-30.8.legacysmp
-rw-r--r-- 1 root root 3175842 Feb 20 2004
vmlinux-2.4.20-30.8.legacy
-rw-r--r-- 1 root root 3543628 Feb 20 2004
vmlinux-2.4.20-30.8.legacybigmem
-rw-r--r-- 1 root root 2121837 Feb 20 2004
vmlinux-2.4.20-30.8.legacyBOOT
-rw-r--r-- 1 root root 3539492 Feb 20 2004
vmlinux-2.4.20-30.8.legacysmp
lrwxrwxrwx 1 root root 26 Feb 4 22:59 vmlinuz ->
vmlinuz-2.4.20-30.8.legacy
-rwxr-xr-x 1 root root 2496380 Dec 12 2002
vmlinuz-2.4.18-19.8.0uml
-rw-r--r-- 1 root root 1122342 Feb 20 2004
vmlinuz-2.4.20-30.8.legacy
-rw-r--r-- 1 root root 1208342 Feb 20 2004
vmlinuz-2.4.20-30.8.legacybigmem
-rw-r--r-- 1 root root 852938 Feb 20 2004
vmlinuz-2.4.20-30.8.legacyBOOT
-rw-r--r-- 1 root root 1206648 Feb 20 2004
vmlinuz-2.4.20-30.8.legacysmp
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: reconfiguring sound after kernel upgrade
2005-03-01 5:21 ` bj
@ 2005-03-01 18:44 ` Eric Bambach
0 siblings, 0 replies; 4+ messages in thread
From: Eric Bambach @ 2005-03-01 18:44 UTC (permalink / raw)
To: bhamal; +Cc: linux-newbie
On Monday 28 February 2005 11:21 pm, bj wrote:
> -----Original Message-----
> From: linux-newbie-owner@vger.kernel.org
> [mailto:linux-newbie-owner@vger.kernel.org]On Behalf Of Eric Bambach
> Sent: Monday, February 28, 2005 11:13 PM
> To: bhamal@wlink.com.np
> Cc: linux-newbie@vger.kernel.org
> Subject: Re: reconfiguring sound after kernel upgrade
>
> On Sunday 27 February 2005 11:17 pm, bj wrote:
> > Hi !
>
> --snip--
>
> > cd alsa-driver-1.0.8
> > ./configure -->no error
> > ./make ----> the following error
> >
> > make[1]: *** No rule to make target
> > `/lib/modules/2.4.18-14/build/include/linux/config.h', needed by
> > `memalloc.o'. Stop.
> > make: *** [compile] Error 1
>
> It looks like you are running 2.4.18 kernel version and trying to compile
> programs for another vesion. Boot into your 2.4.20 legacy kernel and try
> again.
> Uname -a will show you what you are currently running.
>
> The problem is that the configure scripts detect your currently running
> kernel
> when you want to compile for a different one. The simplest way to fix this
> is
> to boot into the new kernel so the configure scripts can detect *THAT*
> version.
>
> Oops, I also just saw another problem. You must make sure that a kernel is
> CONFIGURED at that directory. You will need to install not only the kernel
> binary RPMS, but make sure you install the source along with it. It cant
> find
> config.h because you havent ran make menuconfig or similiar in that
> directory
> and generated the config files for alsa to use.
>
> HTH
>
> --snip--
>
> > Thanks in advance.
> >
> > cheers,
> > bj
>
> Hi !
>
> Thank you for the prompt reply .
>
> The result of uname -a is as follows:-
>
> Linux home 2.4.20-30.8.legacy #1 Fri Feb 20 17:47:48 PST 2004 i686 i686
> i386 GNU/Linux.
>
> I did boot into the new kernel that is 2.4.20-30.8.legacy .
Ok that was my initial suspicion. But since you are booting into the new
kernel there is one more possibility.
> my "ls -la /boot " gives the following .
>
> I am suprised at the result of the make command of the alsa sound.
>
> ANy new ideas ?
Yes. See below.
> I plan to do a ivh on the rpm instead of uvh (upgrade) of the kernel
The real problem I believe is you need to get the kernel SOURCES. Either
install the appropriate rpm ( I dont use RPM distributions, but there should
be the file you installed, for example kernel-2.4.20-30.8.legacy.rpm and a
kernel-2.4.20-30.8.legacy.srpm or kernel-2.4.20-30.8.legacy-source.rpm.)
Install a source rpm ( your best bet) and run make menuconfig from
the /usr/src/linux-[version] directory.
If you can't find an rpm you can try the vanilla sources at www.kernel.org but
it will be anywhere from slightly to vastly different from a RedHat patched
kernel and you will have to configure it manually rather than having
everything pre-configured by RedHat.
> Below is the result of 'ls -la /boot'
This is not relevant. If you can boot the kernel, you have it installed
correctly. Again, you have the BINARY installed just fine, you need the
SOURCES so you can make "out-of-tree" modules.
>
> total 22048
> drwxr-xr-x 3 root root 4096 Feb 25 10:49 .
> drwxr-xr-x 19 root root 4096 Mar 1 09:15 ..
> -rw-r--r-- 1 root root 5824 Sep 5 2002 boot.b
> -rw-r--r-- 1 root root 612 Sep 5 2002 chain.b
> -rw-r--r-- 1 root root 38724 Dec 12 2002
> config-2.4.18-19.8.0uml
> -rw-r--r-- 1 root root 44762 Feb 20 2004
> config-2.4.20-30.8.legacy
> -rw-r--r-- 1 root root 44855 Feb 20 2004
> config-2.4.20-30.8.legacybigmem
> -rw-r--r-- 1 root root 54321 Feb 20 2004
> config-2.4.20-30.8.legacyBOOT
> -rw-r--r-- 1 root root 44814 Feb 20 2004
> config-2.4.20-30.8.legacysmp
> drwxr-xr-x 2 root root 4096 Feb 4 23:02 grub
> -rw-r--r-- 1 root root 133424 Feb 4 23:00
> initrd-2.4.20-30.8.legacybigmem.img
> -rw-r--r-- 1 root root 125898 Feb 4 23:01
> initrd-2.4.20-30.8.legacyBOOT.img
> -rw-r--r-- 1 root root 130032 Feb 4 22:59
> initrd-2.4.20-30.8.legacy.img
> -rw-r--r-- 1 root root 132904 Feb 4 23:02
> initrd-2.4.20-30.8.legacysmp.img
> -rw-r--r-- 1 root root 473 Feb 25 10:49 kernel.h
> -rw-r--r-- 1 root root 23108 Sep 6 2002 message
> -rw-r--r-- 1 root root 21282 Sep 6 2002 message.ja
> lrwxrwxrwx 1 root root 30 Feb 4 22:59 module-info ->
> module-info-2.4.20-30.8.legacy
> -rw-r--r-- 1 root root 15436 Dec 12 2002
> module-info-2.4.18-19.8.0uml
> -rw-r--r-- 1 root root 15438 Feb 20 2004
> module-info-2.4.20-30.8.legacy
> -rw-r--r-- 1 root root 15438 Feb 20 2004
> module-info-2.4.20-30.8.legacybigmem
> -rw-r--r-- 1 root root 15438 Feb 20 2004
> module-info-2.4.20-30.8.legacysmp
> -rw-r--r-- 1 root root 640 Sep 5 2002 os2_d.b
> lrwxrwxrwx 1 root root 29 Feb 25 10:49 System.map ->
> System.map-2.4.20-30.8.legacy
> -rw-r--r-- 1 root root 342101 Dec 12 2002
> System.map-2.4.18-19.8.0uml
> -rw-r--r-- 1 root root 519482 Feb 20 2004
> System.map-2.4.20-30.8.legacy
> -rw-r--r-- 1 root root 545075 Feb 20 2004
> System.map-2.4.20-30.8.legacybigmem
> -rw-r--r-- 1 root root 329824 Feb 20 2004
> System.map-2.4.20-30.8.legacyBOOT
> -rw-r--r-- 1 root root 545040 Feb 20 2004
> System.map-2.4.20-30.8.legacysmp
> -rw-r--r-- 1 root root 3175842 Feb 20 2004
> vmlinux-2.4.20-30.8.legacy
> -rw-r--r-- 1 root root 3543628 Feb 20 2004
> vmlinux-2.4.20-30.8.legacybigmem
> -rw-r--r-- 1 root root 2121837 Feb 20 2004
> vmlinux-2.4.20-30.8.legacyBOOT
> -rw-r--r-- 1 root root 3539492 Feb 20 2004
> vmlinux-2.4.20-30.8.legacysmp
> lrwxrwxrwx 1 root root 26 Feb 4 22:59 vmlinuz ->
> vmlinuz-2.4.20-30.8.legacy
> -rwxr-xr-x 1 root root 2496380 Dec 12 2002
> vmlinuz-2.4.18-19.8.0uml
> -rw-r--r-- 1 root root 1122342 Feb 20 2004
> vmlinuz-2.4.20-30.8.legacy
> -rw-r--r-- 1 root root 1208342 Feb 20 2004
> vmlinuz-2.4.20-30.8.legacybigmem
> -rw-r--r-- 1 root root 852938 Feb 20 2004
> vmlinuz-2.4.20-30.8.legacyBOOT
> -rw-r--r-- 1 root root 1206648 Feb 20 2004
> vmlinuz-2.4.20-30.8.legacysmp
>
HTH
--
----------------------------------------
--EB
> All is fine except that I can reliably "oops" it simply by trying to read
> from /proc/apm (e.g. cat /proc/apm).
> oops output and ksymoops-2.3.4 output is attached.
> Is there anything else I can contribute?
The latitude and longtitude of the bios writers current position, and
a ballistic missile.
--Alan Cox LKML-December 08,2000
----------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2005-03-01 18:44 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-02-28 5:17 reconfiguring sound after kernel upgrade bj
2005-02-28 17:27 ` Eric Bambach
2005-03-01 5:21 ` bj
2005-03-01 18:44 ` Eric Bambach
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox