Ubuntu
linux-source-2.6.17 package

Driver snd_es18xx not loaded for supported ISAPNP device in edgy

Bug #67673 reported by Gabriel Bauman
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned
linux-source-2.6.17 (Baltix)
Invalid
Undecided
Unassigned
linux-source-2.6.17 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

After doing a fresh install of the Edgy beta on my girlfriend's (ancient) desktop, I found that the driver 'snd_es18xx' was not autoloaded at boot time for her ISA ESS Audiodrive sound card.

Dmesg showed:

[17179575.120000] isapnp: Scanning for PnP cards...
[17179575.220000] isapnp: Card 'ESS ES1868 Plug and Play AudioDrive'
[17179575.220000] isapnp: 1 Plug & Play card detected total

Despite that output, the snd_es18xx was not actually autoloaded until I modprobed it. When I did, sound worked great.

In the meantime, adding snd_es18xx to /etc/modules is a functional workaround, but since the kernel correctly detects the card this really shouldn't be needed.

Revision history for this message
heytan (heytan) wrote :

Hi,
I am experiencing the EXACT same problem, with the exact same lines on DMESG, but I was not able to find the right name of the module....
After typing:
modprobe
In the terminal, I have tried (each one at atime, of course..):
snd_ess18xx, snd_ess1868, es18xx, es1868, ess1868
and so on, but for all I got the following message:
FATAL: Module ess18xx not found.
Do you remember the exact name of it?
Hope you can help; I am quite desperate by now....
Thanks in advance,
heytan

Revision history for this message
Kjell Braden (afflux) wrote :

Hardy Heron 8.04 was recently released. It would be helpful if you could test the new release and verify if this is still an issue - http://www.ubuntu.com/getubuntu/download . You should be able to test your bug using the LiveCD. Please let us know your results. Thanks.

Changed in linux-source-2.6.17:
status: New → Won't Fix
Changed in linux:
status: New → Incomplete
Revision history for this message
Gabriel Bauman (gabrielbauman) wrote :

Sorry, I no longer have access to the machine in question and can no longer assist with this bug.

Kjell Braden (afflux)
Changed in linux:
status: Incomplete → Invalid
Revision history for this message
Wayne McDougall (ubuntu-codeworks) wrote :

This is still an issue in Hardy Heron 8.04.2

Revision history for this message
Kjell Braden (afflux) wrote :

Hi, can you please provide the following information?

1. The output of the command "uname -a"
  It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

Thanks in advance.

Changed in linux (Ubuntu):
status: Invalid → Incomplete
Revision history for this message
Wayne McDougall (ubuntu-codeworks) wrote :

uname-a

Linux freepc32 2.6.24-23-generic #1 SMP Mon Jan 26 00:13:11 UTC 2009 i586 GNU/Linux

Revision history for this message
Wayne McDougall (ubuntu-codeworks) wrote :

Dmesg.log attached

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

It would also be good if you could confirm the issue against the most recent Jaunty Jackalope 9.04 release - http://www.ubuntu.com/getubuntu/download . It contians a much newer 2.6.28 based kernel. If the issue remains, if you could then attach a more recent set of dmesg output and lspci -vnvn output against the 9.04 release that would be great. Thanks.

Revision history for this message
dino99 (9d9) wrote :

This version has expired

Changed in linux (Ubuntu):
status: Incomplete → Invalid
Changed in linux-source-2.6.17 (Baltix):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.