Bug 48222 - modrobe throws error message
modrobe throws error message
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
i586 Linux
medium Severity medium
: ---
: ---
Assigned To: Arjan van de Ven
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2001-07-09 18:32 EDT by Need Real Name
Modified: 2007-04-18 12:34 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-01-24 05:22:03 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2001-07-09 18:32:04 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.75 [de] (X11; U; Linux 2.2.16-22 i686)

Description of problem:
After trying to run a sound sample a error message appears.

How reproducible:

Steps to Reproduce:
1. run sndconfig
2. choose any soundblaster manually
3. after sndconfig tries to run a sample error message appears

Actual Results:  error message:

       Der folgende Fehler ist beim Ausf|hren des Programms    ?
          ? modprobe aufgetreten:                                   ?
          ? /lib/modules/2.4.2-2/kernel/drivers/sound/sb.o:         ?
          ? init_module: No such device                             ?
          ? /lib/modules/2.4.2-2/kernel/drivers/sound/sb.o: insmod  ?
          ? /lib/modules/2.4.2-2/kernel/drivers/sound/sb.o failed   ?
          ? /lib/modules/2.4.2-2/kernel/drivers/sound/sb.o: insmod  ?
          ? sound-slot-0 failed      

Expected Results:  i wanna hear a sample

Additional info:

i had no problems with RedHat 7.0, i've got a IBM Thinkpad 760XD,
soundblaster pro compatible
Comment 1 Need Real Name 2001-08-21 01:44:53 EDT
same problem. my sound card is sound blaster awe32. redhat 7.0 ok, but 7.1 and
Roswel. pls told me if anyone know what to do it.
Comment 2 Bill Nottingham 2002-01-24 00:58:01 EST
That means that it's not loading the module correctly, most likely because the
driver doesn't know about the particular PnP IDs. What does /proc/isapnp look like?

Note You need to log in before you can comment on or make changes to this bug.