Gus Wirth wrote:
Darrel Lawrence wrote:
[snip
Here is the output of lspci. My take here is that the /proc/iomem
and the lspci agree on the memory for the wmp11. For the sound card
the lspci displayed a port in place of a memory address and I can't
figure out how to match it to the iomem output.
[EMAIL PROTECTED]:~$ lspci -v
[snip]
00:0a.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1
(rev 07)
Subsystem: Creative Labs SBLive! 5.1 Model SB0100
Flags: bus master, medium devsel, latency 32, IRQ 7
I/O ports at d000 [size=32]
Capabilities: <access denied>
00:0a.1 Input device controller: Creative Labs SB Live! Game Port
(rev 07)
Subsystem: Creative Labs Gameport Joystick
Flags: bus master, medium devsel, latency 32
I/O ports at d400 [size=8]
Capabilities: <access denied>
00:0b.0 Network controller: Intersil Corporation Prism 2.5 Wavelan
chipset (rev 01)
Subsystem: Linksys WMP11 Wireless 802.11b PCI Adapter
Flags: bus master, medium devsel, latency 32, IRQ 10
Memory at ef001000 (32-bit, prefetchable) [size=4K]
Capabilities: <access denied>
[snip]
This looks almost identical to my system, except I don't have a pci
wireless card. The Sound Blaster card doesn't use mapped memory for
I/O operations. Instead, it uses a DMA (Direct Memory Access) channel
to move data.
I'm running out of things to try. I'm not sure which kernel you are
running, but you can see if the modules have any debug capabilities by
using modinfo like so:
$ modinfo snd_emu10k1
$ modinfo orinoco_pci
On my system (kernel 2.6.20-1.2315.fc5 for Fedora Core 5) neither of
these modules have debugging capabilities.
To try and eliminate as may outside factors as possible, you should
try a minimal test. Try starting in command line mode (no X Window
system), and on one console play a WAV file (because it's basic PCM)
using something simple like "aplay" which is part of alsa-utils, and
on another console use something like wget to retrieve a file. Run top
in a third console to see if anything is eating up the CPU or memory
while the two are interacting.
This may be time to file a formal bug report to see if you can get
some more expert advice. I'm not going to recommend running a kernel
debugger on the newbie list :o
Gus
The kernel I am running:
[EMAIL PROTECTED]:~$ uname -a
Linux Ubuntu 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686
GNU/Linux
[EMAIL PROTECTED]:~$
I ran the modinfo commands and did not see anything that would indicate
to me that they had any debugging capabilities.
I did not run the "aplay"/wget sequence as I haven't figured out how to
get to command line mode other than with a terminal window. Does ubuntu
allow you to boot into command line mode?
Before I take up any more time of the people on this list I want to swap
out the sound card and the wireless card(one at a time) to see how this
changes the problem, if it does. What I will do after that will depend
on the results of the swaps.
In the mean time, thanks for all the help provided so far and I will get
back when I have something substantive to report.
Darreln
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-newbie
