Bug 15885 - esssolo1 not found
Summary: esssolo1 not found
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
(Show other bugs)
Version: 7.0
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: Michael K. Johnson
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-08-09 19:11 UTC by Stephen John Smoogen
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-08-09 20:31:42 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Stephen John Smoogen 2000-08-09 19:11:57 UTC
esssolo module not found.

The esssolo module is not available for sndconfig. This breaks the 390E and
other IBM thinkpads

(Confirmed in pinstripe)

Comment 1 Bill Nottingham 2000-08-09 20:11:49 UTC
? It should be the esssolo1 module, and it's in the current
kernel package, and the ones in pinstripe.

Comment 2 Stephen John Smoogen 2000-08-09 20:31:40 UTC
Ok here is what sndconfig put in after a pinstripe upgrade

alias parport_lowlevel parport_pc
alias sound-slot-0 esssolo1
alias usb-controller uhci

However insmod complained it didnt exist. I can see it in
/lib/modules/2.2.16-17/misc though so I was smoking some crack...   sorry it is
saying device busy/not found

/lib/modules/2.2.16-17/misc/esssolo1.o: init_module: Device or resource
busy                                       
/lib/modules/2.2.16-17/misc/esssolo1.o: insmod     
/lib/modules/2.2.16-17/misc/esssolo1.o failed         
/lib/modules/2.2.16-17/misc/esssolo1.o: insmod sound-slot-0 
failed                                                       

So this looks to be something else...

Comment 3 Bill Nottingham 2000-08-09 20:50:58 UTC
Conflict with the uhci driver; switching to usb-uhci fixes this, and we do that
automatically in the latest packages.


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