Very Computer

I finally decided I could no longer wait to upgrade to glibc2.1,
October GNOME, and sundry other things... so I crossed my fingers
and did an 'apt-get dist-upgrade' to Debian/unstable (potato).

Most things seem OK, except modutils.

I have two kernels available in LILO, my normal 2.2.6, and an old
2.0.36 I still had kicking around.

My first problem was that it seemed to be trying to load all the
/lib/modules/2.0.36/* modules AND all the /lib/modules/2.2.6/*
modules on bootup (into 2.2.6).  I removed the /lib/modules/2.0.36
tree, and now most of my modules seem to be working, with the
exception of sound.

I have the sound modules in /etc/modules, and they worked perfectly
before the dist-upgrade.  My sound card is a SoundBlaster AWE 64 (ISA).

Now, all I get is
        /lib/modules/2.2.6/misc/sound.o: invalid parameter parm_io
followed by a message that 'insmod sound' failed.

Trying to load sound.o manually with 'modprobe' gets the same thing.

I tried recompiling the kernel, but that made no difference.  (I don't
really see why it would anyway, it's not like I changed either my
hardware or my kernel, and it all worked fine before.)

I have also tried with my old /etc/conf.modules and the newly installed
/etc/modules.conf files; again, it makes no difference.

What/where is this 'parm_io' parameter, and why is it suddenly broken?
I kind of need to get sound working again...

Thanks for any and all help...
-----------------------------------------------------------------
 Alex Taylor                  BA - CIS - University of Guelph

-----------------------------------------------------------------

: Now, all I get is
:       /lib/modules/2.2.6/misc/sound.o: invalid parameter parm_io
: followed by a message that 'insmod sound' failed.

So edit it out of your conf.modules. You have to edit a file under
/etc/modutils/, then run update-modules.

: Trying to load sound.o manually with 'modprobe' gets the same thing.

Of course.

: I tried recompiling the kernel, but that made no difference.  (I don't
: really see why it would anyway, it's not like I changed either my
: hardware or my kernel, and it all worked fine before.)

You reason correctly. But your kernel has changed. In particular, its
modules now take different parameters than they did before.

: I have also tried with my old /etc/conf.modules and the newly installed
: /etc/modules.conf files; again, it makes no difference.

Of course not.

: What/where is this 'parm_io' parameter, and why is it suddenly broken?

In your conf.modules. It isn't broken. Your use of it is.

Peter

Quote:>: Now, all I get is
>:   /lib/modules/2.2.6/misc/sound.o: invalid parameter parm_io
>: followed by a message that 'insmod sound' failed.

>So edit it out of your conf.modules. You have to edit a file under
>/etc/modutils/, then run update-modules.

OK... mind being more specific?  I've already gone through the
/etc/modutils/ files and run update-modules, a couple of times.

I've searched on 'parm_io' in /etc/modules.conf, and it isn't there.

Quote:>: What/where is this 'parm_io' parameter, and why is it suddenly broken?

>In your conf.modules. It isn't broken. Your use of it is.

But I can't find it anywhere...  

It seems every time I upgrade, the modules system changes just enough
to break my previous setup.  <sigh>

Thanks for the advice.
--
--------------------------
Alex Taylor

--------------------------

Yeah, that's been my experience too, but it's not *really* broken. :-)

Try looking for /etc/modules.conf

I'd really like to help, but I'm using pcmcia; yet another level of
abstraction.  Mine all ended up in /etc/pcmcia

find / -type f -name \*string\* -print

--

                            TopQuark Software & Serv. Enquire within.

  Any technology distinguishable from magic is insufficiently advanced.

Quote:>> >: Now, all I get is
>> >:  /lib/modules/2.2.6/misc/sound.o: invalid parameter parm_io
>> >: followed by a message that 'insmod sound' failed.

>> >So edit it out of your conf.modules. You have to edit a file under
>> >/etc/modutils/, then run update-modules.

>> OK... mind being more specific?  I've already gone through the
>> /etc/modutils/ files and run update-modules, a couple of times.

>> I've searched on 'parm_io' in /etc/modules.conf, and it isn't there.

>> >: What/where is this 'parm_io' parameter, and why is it suddenly broken?

>> >In your conf.modules. It isn't broken. Your use of it is.

>> But I can't find it anywhere...  

>> It seems every time I upgrade, the modules system changes just enough
>> to break my previous setup.  <sigh>

>Yeah, that's been my experience too, but it's not *really* broken. :-)

>Try looking for /etc/modules.conf

>I'd really like to help, but I'm using pcmcia; yet another level of
>abstraction.  Mine all ended up in /etc/pcmcia

>find / -type f -name \*string\* -print

I'm afraid I don't follow...

I've gone through the /etc/modules.conf and /etc/modutils/* time and
again, and I still cannot find any hint of what I'm doing wrong.

/usr/doc/modutils and 'man modprobe' aren't much help either.

The only way it is willing to load the sound modules is if I manually
do 'insmod' on soundcore, soundlow, uart401, awe_wave, v_midi, and sb,
one at a time, in that order.

Does anyone know either specifically what's wrong, or at least which
documentation I need?

Thanks...
--
--------------------------
Alex Taylor

--------------------------