All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Smirnov <huge@ax.ru>
To: linux-dvb@linuxtv.org
Subject: [linux-dvb] hvr4000-dvb firmware loading issue
Date: Sat, 26 Apr 2008 10:02:21 +0100	[thread overview]
Message-ID: <4812EF9D.2030000@ax.ru> (raw)

Experiencing issue with Hauppauge HVR4000 not loading firmware even 
though it was doing this on another system using same firmware file and 
same version of HVR source :(

Background:
    HVR4000 card
Kernel:
    2.6.24.5 vanilla
Source from:
    hvr4000-dvb

modprobe cx88_dvb
loads ok, expected messages appear in the syslog

md5sum /lib/firmware/dvb-fe-cx24116.fw
2f0d3966e8ef44ac971cfa98d536aaaf  /lib/firmware/dvb-fe-cx24116.fw

when doing dvbscan I'm getting this:

==> /var/log/messages <==
Apr 26 10:35:59 boxer kernel: cx24116: cx24116_initfe()
Apr 26 10:35:59 boxer kernel: cx24116: cx24116_set_tone(1)
Apr 26 10:35:59 boxer kernel: cx24116: cx24116_cmd_execute()
Apr 26 10:35:59 boxer kernel: cx24116: cx24116_firmware_ondemand()
Apr 26 10:35:59 boxer kernel: cx24116: cx24116: read reg 0x20, value 0x00
Apr 26 10:35:59 boxer kernel: cx24116: cx24116_cmd_execute: 0x00 == 0x22
Apr 26 10:35:59 boxer kernel: cx24116: cx24116: cx24116_writereg: write 
reg 0x00, value 0x22
Apr 26 10:35:59 boxer kernel: cx24116: cx24116_cmd_execute: 0x01 == 0x00
Apr 26 10:35:59 boxer kernel: cx24116: cx24116: cx24116_writereg: write 
reg 0x01, value 0x00
Apr 26 10:35:59 boxer kernel: cx24116: cx24116: cx24116_writereg: write 
reg 0x1f, value 0x01
Apr 26 10:35:59 boxer kernel: cx24116: cx24116: read reg 0x1f, value 0x01
Apr 26 10:36:00 boxer last message repeated 63 times
Apr 26 10:36:00 boxer kernel: cx24116_cmd_execute() Firmware not responding




_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

                 reply	other threads:[~2008-04-26 10:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4812EF9D.2030000@ax.ru \
    --to=huge@ax.ru \
    --cc=linux-dvb@linuxtv.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.