You are not logged in.
Pages: 1
I'm doing an FTP install, my second of the day, and the result has been the same both times. FAILURE!!!!
I'm booting and installing from the CD, (i've tried both the CD and the ftp install and had this problem both times). I prepare the hard drive, select packages, install packages, install kernel, etc etc etc. I reboot and everything is fine.
I go through a few more things to get it looking the way I like it, and boot again. Everything is fine.
I do pacman -S alsa-driver, it downloads and installs fine.
I add snd-cs4236 to MODULES() in the rc.conf and the appropriate changes to modules.conf and reboot. It gets to the point where it's loading modules and I get this:
Unable to handle kernel NULL pointer dereference at virtual address 00000060
some other stuff that means nothing to me.
Process modprobe (pid: 68, stackpage=e7389000_
more stuff
(0)Kernel panic: Aiee, killing interrupt handler!
In interrupt handler - no syncing
I'm pretty sure I'm doing this right, since it's worked fine in the past. Any ideas?
Offline
hmmm.... try rebuilding alsa-driver from ABS so that you can be sure it's completely compatible with your kernel. (although I think that the alsa-driver package is fine if you are installing the basic kernel -- it's still worth a try)
once you install it all and have rebooted w/o alsa, do the following:
> abs
> cd /var/abs/multimedia/alsa-driver
> makepkg
once that compiles without errors,
> pacman -A alsa-driver-<ver>.tar.gz
> depmod -a
and since you have problems with it stopping booting, before you add it to your rc.conf, try typing
> modprobe snd-cs4236
and make sure that works without errors before adding it to your startup.
Hapy.
Offline
That's good advice, unfortunately I've got problems doing that too. The configure goes ok but the build fails on pdaudiocf.c after multiple errors and warnings.
I've tried makepkg on alsa-driver several times in the past and have never been successful, for one reason or another.
So instead I do pacman -S alsa-driver, which works, then depmod -a which gives me
Unresolved symbols in /lib/modules/2.4.22/kernel/drivers/atm/he.o
Unresolved symbols in /lib/modules/2.4.22/kernel/drivers/i2c/scx200i2c.o
Neither of those modules are related to sound (are they?) so I go on with modprobe snd-cs4236 and it blows up again in exactly the same way.
Like I said, this isn't the first time I've tried this today. Any other ideas?
Offline
you have modules.conf and rc.conf loading your modules? that could a problem right there.
Unable to handle kernel NULL pointer dereference at virtual address 00000060
some other stuff that means nothing to me.
well those messages may mean something to somebody else so if you can provide these messages perhaps someone else can decipher them.
AKA uknowme
I am not your friend
Offline
Why would using modules.conf and rc.conf be a problem? Isn't that the way it's supposed to be done?
I'd be happy to submit all of the messages, is there anyway to get a log?
Offline
well if you are using both modules.conf and rc.conf, and this just a guess, then i would assume that there is anattempt to double load the modules. personally i just use rc.conf.
as for logging the errors ... i don't know if there is a way or not...anyone?
AKA uknowme
I am not your friend
Offline
Oh, I see what you're saying. Maybe I should clear that up. The module is being loaded in rc.conf, MODULES=(snd-cs4236). At least it will be when this problem is resolved, right now MODULES is empty and I'm loading snd-cs4236 from the command line so I can still boot.
The contents of modules.conf is alias commands only, just what is needed to get alsa working and all straight from www.alsa-project.org
Offline
ah ok i just wanted to be sure. to me it sounds like a bad module possibly because it seems to relate strictly to when you try and load your soundcard module.
my next(stupid) question would be, if yopur card is supported, have you tested how everything works using just OSS? this would indeed narrow the scope of your problems.
AKA uknowme
I am not your friend
Offline
Yes, I have. Or I think I have.
I switched to the cs4232 module (that's the OSS module, isn't it?) and it works fine. I can use aumix to set levels etc.
Offline
Yeah I don't really know what is up with alsa-driver package. Is this package really in working condition? I know I always get errors rebuilding it (unless I modify the PKGBUILD) and I've heard others have the same problem.
The way that I modify my PKGBUILD file is to add an additional line to the ./configure, so that it only builds my sound cards module.
Maybe it will work for you you I think it goes like this:
--with-cards="cmipci"
is what I think I use. you could use
--with-cards="cs4236"
or play around with it until you find the right one.
I guess that means that for me the build blows up while trying to make certain soundcard modules.
either way it would be good to know if my system is just strange or others have this problem as well.
Hapy.
Offline
actually yes the package works just fine. about all you usually have to make sure of is that you are using an alsa package that relates to your kernel version. if you install from the iso then just add the current alsa package without upgrading the kernel as well likely it wil not work.
AKA uknowme
I am not your friend
Offline
loooking through the alsa modules i see that that driver exists under the isa section of the alsa modules. perhaps there is another module that you need to load along with your driver?
i don't really know but i thought i would brainstorm that out loud.
do you have another linux you can check the configs with?
have you looked for answers on the alsa homepage? (likely you have but just thought i would throw that out too)
AKA uknowme
I am not your friend
Offline
I've never had any luck building the alsa-driver package either, although I'll probably keep trying.
Let's keep a couple of things in mind, too. First I'm doing an FTP install and the problem persists. So I can't see how there would be a problem with the version of alsa-driver/kernel.
Second, I've always used cs4236 with the alsa-driver packages and never had to install any other module. This is a very new problem.
Offline
Not like I have a lot to contribute, but I've built the alsa-driver many many times.
I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal
Offline
well my only other suggestion is that you contact the maintainer of the package and see if there are any tricks that you may have to do in order to build the alsa package. on very rare occasions there are instances of pkgbuilds that require so extra work that the PKGBUILD cannot provide.
(another consideration is perhaps you are not loading the snd module?)
AKA uknowme
I am not your friend
Offline
snd module should be loaded when snd-cs* is loaded. modprobe should be handling that. I can give assistance building alsa-driver if you don't fee like bugging apeiro. Send me an email (jason@archlinux.org), we can handle it there.
I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal
Offline
If I wasn't loading the snd module, why did this never happen before?
Offline
(HUGE sigh)
Well, I managed to build alsa-driver by modifying the PKGBUILD to include --with-cards=cs4236 --with-sequencer=yes, straight out of the alsa-project web site.
Now, not only is modprobe snd-cs4236 causing the same problem, but my network module isn't loading. The error log is reporting
Invalid dependency /lib/modules/2.4.22/kernel/sound/acore/seq/snd-seq-
uglier and uglier
Offline
It's not getting any prettier.
I started with a brand new, fresh FTP install this morning. Then I recompiled the kernel, turning off a bunch of stuff I don't need (PPP, FDDI, ISDN, like that).
That went well, so I tried rebuilding alsa-driver, which ran to completion for the first time. I thought I was on the right track, but alas I was mislead.
modprobe snd-cs4236 gives me EXACTLY the same error I was getting last week.
Here's the full error,
Unable to handle kernel NULL pointer dereference at virtual address 00000060
*pde=00000000
Oops: 0000
CPU: 0
EIP: 0010:[<e8a3c8c3>] Not tainted
EFLAGS: 00010092
eax: 00000000 ebx: e6900aff ecx: e68a7afc edx: 000000535
esi: 00000000 edi: e66b86a0 ebp: 00000005 esp: e65e5e08
ds: 0018 es: 0018 ss: 0018
Process modprobe (pid: 147, stackpage=e65e5000)
There's lots more, Stack and Call Trace and Code, with a lot of memory addresses.
After that the whole thing locks up and I have to reboot.
Does that help any, or should I just give up?
Offline
I'm still not able to get alsa to work, although oss has been working fine. Could this have anything to do with gcc 3.3.1? The kernel suggests using an earlier version when building, 2.9.5 I think.
Any chance that's the problem?
Offline
nope alsa builds and works fine with 3.3.1.
AKA uknowme
I am not your friend
Offline
I wasn't thinking about alsa. I was wondering if the kernel being built with 3.3.1 is the problem?
Shows how desperate I am to solve this, doesn't it.
Offline
News on the alsa front.
I recently did a full LinuxFromScratch install and I'm having the same problem with alsa. Very strange.
Anyway I posted the error to alsa-users and I'm working with one of the developers in getting it resolved. Apparently this is a known problem is isapnp.
Thanks for all the input.
Offline
Pages: 1