Re: hdsploader causes Ooops in kernel 2.6.8.1 and AMD64

Re: hdsploader causes Ooops in kernel 2.6.8.1 and AMD64

[thewade]

> On Fri, 2004-09-10 at 21:51, thewade wrote:
> > Hello,
> > 
> > Im trying to solve my own problem, which is getting the hammerfall to 
> > work on my AMD64 laptop running Fedora Core 3 test 1 and the standard 
> > kernel 2.6.8.1.
> > 
> > On boot I get Found hammerfall dsp: no multiface or digiface
> connected: 
> > waiting for firmware even when the multiface is connected.
> 
> Are you sure Linux sees the hammerfall (1394 support enabld, etc)?  What
> does dmesg say about it?
> 
> The Oops is certainly a bug and should be fixed.
> 
> Lee

Linux Kernel Card Services
  options:  [pci] [cardbus] [pm]
ACPI: PCI interrupt 0000:00:09.0[A] -> GSI 17 (level, low) -> IRQ 17
Yenta: CardBus bridge found at 0000:00:09.0 [1584:3005]
Yenta: ISA IRQ mask 0x02b8, PCI irq 17
Socket status: 30000820
ACPI: PCI interrupt 0000:00:09.1[A] -> GSI 17 (level, low) -> IRQ 17
Yenta: CardBus bridge found at 0000:00:09.1 [1584:3005]
Yenta: ISA IRQ mask 0x02b8, PCI irq 17
Socket status: 30000006
PCI: Enabling device 0000:02:00.0 (0080 -> 0082)
ACPI: PCI interrupt 0000:02:00.0[A] -> GSI 17 (level, low) -> IRQ 17
Hammerfall-DSP: no Digiface or Multiface connected!
card initialization pending : waiting for firmware

I figure this pertains to the cardbus. If you need more let me know.
Thanks for the help!
-thewade


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM. 
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php

Re: hdsploader causes Ooops in kernel 2.6.8.1 and AMD64

[Lee Revell]

On Tue, 2004-09-14 at 23:29, thewade wrote:
> Ive made no success on solving my kernel Oops/hdsploader problem. Ive
> posted a bug in the kernel bugzilla (http://bugzilla.kernel.org/show_bug.cgi?id=3388).
> 
> Is there any value to using an earlier kernel release (like 2.6.4 which
> works on my other pIII laptop)? 
> 

Absolutely.  If it works with a previous kernel, we can narrow down the
search to the things that changed between those releases.

> I imagine that an earlier release would have the same x86-64 bug though,
> right?
> 

Only one way to find out...

> Is there eom way to dtermine if it was a kernel problem or a hdsploader
> problem?
> 

Anytime you get an Oops it is by definition a kernel problem.

> Should I post a bug in the alsa bugtracker?
> 

Yes.  People are not blowing you off, it's just that there aren't many
ALSA developers, and even fewer that have the same hardware.  I am sure
you will get a response soon.

Lee



-------------------------------------------------------
This SF.Net email is sponsored by: thawte's Crypto Challenge Vl
Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam
Camcorder. More prizes in the weekly Lunch Hour Challenge.
Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m

hdsploader causes Ooops in kernel 2.6.8.1 and AMD64

[thewade]

Ive made no success on solving my kernel Oops/hdsploader problem. Ive
posted a bug in the kernel bugzilla (http://bugzilla.kernel.org/show_bug.cgi?id=3388).

Is there any value to using an earlier kernel release (like 2.6.4 which
works on my other pIII laptop)? 

I imagine that an earlier release would have the same x86-64 bug though,
right?

Is there eom way to dtermine if it was a kernel problem or a hdsploader
problem?

Should I post a bug in the alsa bugtracker?

Thanks for the help!
-thewade


-------------------------------------------------------
This SF.Net email is sponsored by: thawte's Crypto Challenge Vl
Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam
Camcorder. More prizes in the weekly Lunch Hour Challenge.
Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m

Re: hdsploader causes Ooops in kernel 2.6.8.1 and AMD64

[thewade]

> On Fri, 2004-09-10 at 21:51, thewade wrote:
> > Hello,
> > 
> > Im trying to solve my own problem, which is getting the hammerfall to 
> > work on my AMD64 laptop running Fedora Core 3 test 1 and the standard 
> > kernel 2.6.8.1.
> > 
> > On boot I get Found hammerfall dsp: no multiface or digiface
> connected: 
> > waiting for firmware even when the multiface is connected.
> 
> Are you sure Linux sees the hammerfall (1394 support enabld, etc)?  What
> does dmesg say about it?
> 
> The Oops is certainly a bug and should be fixed.
> 
> Lee

So I was looking at the hdsploader.c code and I dont know enough about coding on linux to track down the error very far, but the error has to happen somewhere in the following three functions as the last bit of output I get is:
printf(\"Upload firmware for card %s\\n\", card_name);
Then I get killed on my xterm and Oops in my syslog.

So the error has to be in one of these:
-snd_hwdep_open(&hw, card_name, SND_HWDEP_OPEN_DUPLEX)
-snd_hwdep_ioctl(hw, SNDRV_HDSP_IOCTL_GET_VERSION, &version)
-read_bin_file(code, DATAPATH \"/multiface_firmware.bin\")

I bet its one of the first two. Is there any way that the hw variable is the problem? Is the error in the hw variable, or is it in one of the alsa headers?

Thanks for the help,
-thewade


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM. 
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php

Re: hdsploader causes Ooops in kernel 2.6.8.1 and AMD64

[Lee Revell]

On Fri, 2004-09-10 at 21:51, thewade wrote:
> Hello,
> 
> Im trying to solve my own problem, which is getting the hammerfall to 
> work on my AMD64 laptop running Fedora Core 3 test 1 and the standard 
> kernel 2.6.8.1.
> 
> On boot I get Found hammerfall dsp: no multiface or digiface connected: 
> waiting for firmware even when the multiface is connected.

Are you sure Linux sees the hammerfall (1394 support enabld, etc)?  What
does dmesg say about it?

The Oops is certainly a bug and should be fixed.

Lee






-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM. 
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php

hdsploader causes Ooops in kernel 2.6.8.1 and AMD64

[thewade]

Hello,

Im trying to solve my own problem, which is getting the hammerfall to 
work on my AMD64 laptop running Fedora Core 3 test 1 and the standard 
kernel 2.6.8.1.

On boot I get Found hammerfall dsp: no multiface or digiface connected: 
waiting for firmware even when the multiface is connected. If I run 
hdsploader I get a kernel Ooops (Ive posted it here before so Ill safe 
you the lines to look at).

When looking at the code I obviously get as far as:
printf(\"Upload firmware for card %s\\n\", card_name);
in hdsploader.c but to look further I need to know something about:
snd_hwdep_t *hw;
as the error either happens in:
-snd_hwdep_open
-snd_hwdep_ioctl
-read_bin_file

snd_hwdep_type_t is:
/** HwDep handle type */
typedef enum _snd_hwdep_type {
        /** Kernel level HwDep */
        SND_HWDEP_TYPE_HW,
        /** Shared memory client HwDep (not yet implemented) */
        SND_HWDEP_TYPE_SHM,
        /** INET client HwDep (not yet implemented) */
        SND_HWDEP_TYPE_INET
} snd_hwdep_type_t;
But I dont know what any of the values are.

I havent programmed c in a LONG time so I dont know how effective I 
will be. i thank you for whatever help you can give me.

-thewade


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM. 
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php