Red HatThis forum is for the discussion of Red Hat Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Originally posted by regorbro Thank you Thetargos, the gcc32 compilation worked with intel8x0.
I'm not ready to try to install kernel 2.6.x yet, especially if I am still having troubles with something as basic as sound.
Believe me, it's easier than it appers to be... but take your time and learn at your own pace... that's the best advice I can give you... It took me about 6 years of using Linux before I even attempted to install source packages! I was quite happy with RPMs, that's maybe why I don't see those packages as bad as other people think they are... in fact they're quite efficient. Anyway, just take all the time you need before attempting to (re)-compile a kernel...
Distribution: Red Hat Linux 9, Fedora Core 1, *Fedora Core 2*
Posts: 74
Rep:
Thats right take your time. I've been using Redhat 9 with the 2.4 kernel for about 6months(thats how long i've known Linux =P) and I recompiled the 2.6.0 kernel *sucessfully* after 3 failed attempts =). It runs as like a beauty. But unfortunately I too am having some ALSA difficulties. But what the heck? I will polish 'em out in a week or two =).
@Thetargos: I'm runnig RH9, with kernel 2.4.20-30.9, and I tried to compile the drivers with the CC="gcc32" option, but it then returns the error:
Code:
checking for gcc... gcc32
checking for C compiler default output file name... configure: error: C compiler cannot create executables
See `config.log' for more details.
My config.log gives the following output:
Code:
configure:1306: checking for gcc
configure:1332: result: gcc32
configure:1576: checking for C compiler version
configure:1579: gcc32 --version </dev/null >&5
./configure: line 1: gcc32: command not found
configure:1582: $? = 127
configure:1584: gcc32 -v </dev/null >&5
./configure: line 1: gcc32: command not found
configure:1587: $? = 127
configure:1589: gcc32 -V </dev/null >&5
./configure: line 1: gcc32: command not found
configure:1592: $? = 127
configure:1615: checking for C compiler default output file name
configure:1618: gcc32 conftest.c >&5
./configure: line 1: gcc32: command not found
configure:1621: $? = 127
configure: failed program was:
| /* confdefs.h. */
|
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:1660: error: C compiler cannot create executables
See `config.log' for more details.
Me, as a newbie, would say that gcc32 isn't installed or cannot be found??
In your case, RH9 uses gcc 3.2.3 as the primary gcc command, so no need for you specify it, that line is only needed for Fedora system, whose kernel is compiled with gcc 3.2.3 (gcc32 command), but has the 3.3.2 (gcc command) installed by default, hence the need to specify
So all you need to do is simply ./configure <options> && make && make install, that should be all
My rehat doesn't see my adio card which is a soundmax ditial audio onboard. I have read so much but I can't seem to get it even after the long brilliant tut on this page.....sorry. therefore I will post stuff for my particular situation.
Distro: Redhat 9
kernel: 2.4.20-30.9
alsa driver/lib/utils version 1.04
pentium p4p800 2.8 ghz.
Soundmax digital audio card.
....continued
When I try to install the alsa kernel module this is the message:
[root@www alsa]# rpm -ivh kernel-module-alsa-0.9.8-1.fr_2.4.20_20.9.i686.rpm
warning: kernel-module-alsa-0.9.8-1.fr_2.4.20_20.9.i686.rpm: V3 DSA signature: NOKEY, key ID e42d547b
error: Failed dependencies:
alsa-driver >= 0.9.0 is needed by kernel-module-alsa-0.9.8-1.fr_2.4.20_20.9
So I try to install the alsa driver first, before lib, modules etc... and this is what happens
[root@www alsa-driver-1.0.4]# [root@www alsa]# ./configure --with-cards=intel8x0 --with-sequencer=yes;make;make install
bash: [root@www: command not found
make all-deps
make[1]: Entering directory `/home/sr1201/applications/alsa/alsa-driver-1.0.4'
make[1]: Nothing to be done for `all-deps'.
make[1]: Leaving directory `/home/sr1201/applications/alsa/alsa-driver-1.0.4'
Please, run the configure script as first...
rm -f /snd*.*o /persist.o /isapnp.o
make[1]: Entering directory `/home/sr1201/applications/alsa/alsa-driver-1.0.4/acore'
Makefile:6: /home/sr1201/applications/alsa/alsa-driver-1.0.4/Makefile.conf: No such file or directory
make[1]: *** No rule to make target `/home/sr1201/applications/alsa/alsa-driver-1.0.4/Makefile.conf'. Stop.
make[1]: Leaving directory `/home/sr1201/applications/alsa/alsa-driver-1.0.4/acore'
make: *** [install-modules] Error 1
[root@www alsa-driver-1.0.4]# bash: ./configure: No such file or directory
bash: bash:: command not found
[root@www alsa-driver-1.0.4]# make: *** No targets specified and no makefile found. Stop.
bash: make:: command not found
[root@www alsa-driver-1.0.4]# make: *** No rule to make target `install'. Stop.
some more info!
PCI devices found:
Bus 0, device 0, function 0:
Host bridge: PCI device 8086:2570 (Intel Corp.) (rev 2).
Prefetchable 32 bit memory at 0xf8000000 [0xfbffffff].
Bus 0, device 1, function 0:
PCI bridge: PCI device 8086:2571 (Intel Corp.) (rev 2).
Master Capable. Latency=64. Min Gnt=8.
Bus 0, device 29, function 0:
USB Controller: PCI device 8086:24d2 (Intel Corp.) (rev 2).
IRQ 10.
I/O at 0xef00 [0xef1f].
Bus 0, device 29, function 1:
USB Controller: PCI device 8086:24d4 (Intel Corp.) (rev 2).
IRQ 3.
I/O at 0xef20 [0xef3f].
Bus 0, device 29, function 2:
USB Controller: PCI device 8086:24d7 (Intel Corp.) (rev 2).
IRQ 5.
I/O at 0xef40 [0xef5f].
Bus 0, device 29, function 3:
USB Controller: PCI device 8086:24de (Intel Corp.) (rev 2).
IRQ 10.
I/O at 0xef80 [0xef9f].
I know I am doing somethin wrong with with the config file and more so if you have some guidance it will be highly appreciated!
This line is the problem, you are already in the correct directory (the first [root@www alsa-driver-1.0.4]#) there's no need to rewrite it (the second [root@www alsa]#), just issue the commands without it!
alias eth0 8139too
alias eth1 8139too
alias usb-controller ehci-hcd
alias usb-controller1 usb-uhci
alias ieee1394-controller ohci1394
Is all as it should be here before I begin?
See that I should put the following into my modules.conf:
# ALSA portion
alias char-major-116 snd
alias snd-card-0 snd-intel8x0
# module options should go here
# OSS/Free portion
alias char-major-14 soundcore
alias sound-slot-0 snd-card-0
# card #1
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
After that I will try to install again.
If it's OK Thetargos, I will keep it coming if it's ok.
Yeah, all seems right... Just do you see any Multimedia controller or other things that actually lists the card when you do an /sbin/lspci or cat /proc/pci?? I ask this becuase in the other dump you posted, there's no such information, just to be sure, you may want to check your BIOS settings to make sure the card is enabled in BIOS (I had some experiences with some nForce MoBos [same sound chip] that after a crash disable some devices).
About your sound support, as long as you're using a RH/Fedora built kernel, you have that compiled as a module, you may make sure by doing an:
Code:
ls /lib/modules/`uname -r`/kernel/drivers/sound/soundcore*
You may replace the `uname -r` with your kenrel's actual version (2.4.20-30.9, for instance).
No problem, that's why we are here, to help each other
Ok, everything looks just right to me... in theory (assuming you already installed the lib, utils, oss) packages, all you have to do is build the kernel modules (drivers)... just make sure you edit modules.conf before so the drivers load right after you build them (also make sure you build the devices with the ./snddevices script). Then just run alsamixer and tweak away!
well as I said .... a couple of more questions. Sorry for all the dump but I gather it's better giving you too much then too litlle info.
question 1)
I am editing the modules.conf.
Original conf:
alias eth0 8139too
alias eth1 8139too
alias usb-controller ehci-hcd
alias usb-controller1 usb-uhci
alias ieee1394-controller ohci1394
OKEY...so I open the file and paste inn the rest and it looks like this:
alias eth0 8139too
alias eth1 8139too
alias usb-controller ehci-hcd
alias usb-controller1 usb-uhci
alias ieee1394-controller ohci1394LSA portion
alias char-major-116 snd
alias snd-card-0 snd-intel8x0
# module options should go here
# OSS/Free portion
alias char-major-14 soundcore
alias sound-slot-0 snd-card-0
# card #1
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
----
then ESC
I press shift + q and I assume it is saved. I close the window and still assume the new conf file is all good.
I check the modules.conf again and the changes are not made. Isn't it enough to do shift +q? I read about the wq! but tell me my friend...am I suppose to type this wq! in the file?
question 2)
When installing alsa-lib-1.0.4 all goes smotth in the install until the the end where I get the message checking for gcc... no
checking for cc... no
checking for cc... no
checking for cl... no
configure: error: no acceptable C compiler found in $PATH
See `config.log' for more details.
I thought rh 9 had all this checked from the box. What can I do about it?
If you want the log file say to.....
(ofcourse the same results to installing alsa-utils and alsa-oss)
Cheers.
sr
alias eth0 8139too alias eth1 8139too alias usb-controller ehci-hcd alias usb-controller1 usb-uhci alias ieee1394-controller ohci1394
Hmm.... no GCC?? Just grab your CD1 and open redhat-config-packages, install the development tools...
As for the first question with vi, use :x (esc, colon, x) instead of shift+q, shift+q will exit witout saving! while x will do so saving. Just make sure you open the file as root!
Ok... Just another quick tip, you said you used apt-get, right? install synaptic and ask for the development packages (in graphical mode, quite convinent). Just ask for gcc and it will install the rest
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.