 |
Loading Firmware [Solved] |
 |
Posted: Sun May 22, 2005 1:11 pm |
|
|
| Troy |
|
|
| |
| Joined: 21 May 2005 |
| Posts: 10 |
|
|
|
 |
 |
 |
|
At what point is the firmware for the HD3000 suppose to be loaded? On my Gentoo/2.6.12-rc4-mm2 system it does not load until I execute azap or similar app even though the dvb-cx88 module is already loaded. The reason I ask is because I'm have trouble getting Mythtv to recognize the HD3000 card and thought maybe this may be part of it. Thanks!
-Troy |
|
Last edited by Troy on Wed May 25, 2005 10:56 pm; edited 1 time in total |
|
|
|
 |
Re: Loading Firmware |
 |
Posted: Mon May 23, 2005 8:21 am |
|
|
| HDTV buff |
|
|
| |
| Joined: 02 Mar 2005 |
| Posts: 114 |
| Location: Maryland, USA |
|
|
 |
 |
 |
|
| Troy wrote: | At what point is the firmware for the HD3000 suppose to be loaded? On my Gentoo/2.6.12-rc4-mm2 system it does not load until I execute azap or similar app even though the dvb-cx88 module is already loaded. The reason I ask is because I'm have trouble getting Mythtv to recognize the HD3000 card and thought maybe this may be part of it. Thanks!
-Troy |
Firmware is loaded on first use. Or to be more precise the first use of the particular frequency type.
During testing, I called azap with cable and antenna frequecies. Each time I "switched" from cable to air (or vice versa), it prompted the loading of firmware.
To answer your question, the firmware got nothing to do with the card not being recognized. It only loads when it is "used" for the first time.
You can force a load by tuning using azap before you use MythTV.
There are a couple gentoo users on this forum. Maybe they can help in finding out your problem with mythtv.
-HDTV Buff |
|
|
|
|
 |
 |
Try v4l card... |
 |
Posted: Mon May 23, 2005 9:00 am |
|
|
| HydraSwitch |
|
|
| |
| Joined: 18 May 2005 |
| Posts: 19 |
|
|
|
 |
 |
 |
|
| I've had better success setting the card type to whatever that generic v4l card type is.... NOT the pcHDTV-3000 as you think should work. For me, this is adequate - I'm only trying to record NTSC at the moment. |
|
|
|
|
 |
Re: Loading Firmware |
 |
Posted: Mon May 23, 2005 9:42 am |
|
|
| Troy |
|
|
| |
| Joined: 21 May 2005 |
| Posts: 10 |
|
|
|
 |
 |
 |
|
| HDTV buff wrote: | | Troy wrote: | At what point is the firmware for the HD3000 suppose to be loaded? On my Gentoo/2.6.12-rc4-mm2 system it does not load until I execute azap or similar app even though the dvb-cx88 module is already loaded. The reason I ask is because I'm have trouble getting Mythtv to recognize the HD3000 card and thought maybe this may be part of it. Thanks!
-Troy |
Firmware is loaded on first use. Or to be more precise the first use of the particular frequency type.
During testing, I called azap with cable and antenna frequecies. Each time I "switched" from cable to air (or vice versa), it prompted the loading of firmware.
To answer your question, the firmware got nothing to do with the card not being recognized. It only loads when it is "used" for the first time.
You can force a load by tuning using azap before you use MythTV.
There are a couple gentoo users on this forum. Maybe they can help in finding out your problem with mythtv.
-HDTV Buff |
Thank you! This is exactly what I wanted to know.... I have heard other people claim that the firmware was loaded when the module is loaded but in my case it happens just as you explained. Are you using the DVB driver and Mythtv? |
|
|
|
|
 |
 |
Re: Loading Firmware |
 |
Posted: Mon May 23, 2005 11:30 am |
|
|
| Scott Larson |
|
|
| |
| Joined: 15 Oct 2003 |
| Posts: 713 |
| Location: Portland, OR |
|
|
 |
 |
 |
|
| Troy wrote: | | Thank you! This is exactly what I wanted to know.... I have heard other people claim that the firmware was loaded when the module is loaded but in my case it happens just as you explained. |
Yeah, that was me. I forgot that QAM and ATSC require different firmware. I was never able to get QAM to work very well so I haven't used it much. |
|
|
|
|
 |
Re: Loading Firmware |
 |
Posted: Mon May 23, 2005 11:44 am |
|
|
| HDTV buff |
|
|
| |
| Joined: 02 Mar 2005 |
| Posts: 114 |
| Location: Maryland, USA |
|
|
 |
 |
 |
|
| Troy wrote: | | Thank you! This is exactly what I wanted to know.... I have heard other people claim that the firmware was loaded when the module is loaded but in my case it happens just as you explained. Are you using the DVB driver and Mythtv? |
I am using a plain vanilla kernel 2.6.12-rc2. It is running against a cvs of MythTV from 3/28, I believe. OS is Debian unstable.
I am running the built-in drivers (dvb) that came with the kernel and I am compiling the MythTV against the kernel as the dvb source.
This is the script I use to grab the latest mythtv
| Code: | #Create the directory
rm -fR /usr/src/download/mythtv/cvs.`date '+%F'`
mkdir -p /usr/src/download/mythtv/cvs.`date '+%F'`
cd /usr/src/download/mythtv/cvs.`date '+%F'`
# Get from CVS
echo Password is 'mythtv'
cvs -d :pserver:mythtv@cvs.mythtv.org:/var/lib/mythcvs login
nice -n 19 cvs -z3 -d :pserver:mythtv@cvs.mythtv.org:/var/lib/mythcvs \
checkout mythtv mythplugins nuvexport
MYTHCONF="--enable-dvb \
--dvb-path=/lib/modules/`uname -r`/build/include \
--enable-dvb-eit --enable-opengl-vsync --enable-xvmc"
MYTHLIBCONF="--enable-opengl --enable-fftw \
--enable-sdl --enable-aac --enable-transcode --enable-vcd"
ERROR="no"
# Build Mythtv
[ $ERROR = "no" ] && cd mythtv || ERROR="yes"
[ $ERROR = "no" ] && ./configure $MYTHCONF || ERROR="yes"
[ $ERROR = "no" ] && qmake || ERROR="yes"
[ $ERROR = "no" ] && nice -n 19 make || ERROR="yes"
# Make sure modules can be built (so partial builds can be avoided)
[ $ERROR = "no" ] && cd ../mythplugins || ERROR="yes"
[ $ERROR = "no" ] && ./configure $MYTHLIBCONF || ERROR="yes"
[ $ERROR = "no" ] && qmake || ERROR="yes"
#[ $ERROR = "no" ] && nice -n 19 make || ERROR="yes"
# do not want to build them with old libraries
#[ $ERROR = "no" ] && nice -n 19 make distclean
# Install MythTV and libs (after an uninstall of the older version).
[ $ERROR = "no" ] && make uninstall
[ $ERROR = "no" ] && cd ../mythtv || ERROR="yes"
[ $ERROR = "no" ] && make uninstall
[ $ERROR = "no" ] && make install || ERROR="yes"
# Build myth modules (and install them)
[ $ERROR = "no" ] && cd ../mythplugins || ERROR="yes"
[ $ERROR = "no" ] && ./configure $MYTHLIBCONF || ERROR="yes"
[ $ERROR = "no" ] && qmake || ERROR="yes"
[ $ERROR = "no" ] && nice -n 19 make || ERROR="yes"
[ $ERROR = "no" ] && make install || ERROR="yes"
# Install nuvexport
[ $ERROR = "no" ] && cd ../nuvexport || ERROR="yes"
[ $ERROR = "no" ] && make install || ERROR="yes"
# Restart services
[ $ERROR = "no" ] && killall mythfrontend && sleep 1s
[ $ERROR = "no" ] && killall mythbackend && sleep 3s
[ $ERROR = "no" ] && /bin/su - -c "mythbackend --daemon \
--logfile /var/log/mythtv/mythbackend.log \
--pidfile /var/run/mythtv/mythtv.pid" mythtv
|
-HDTV Buff |
|
|
|
|
 |
 |
Was having similar issues... |
 |
Posted: Mon May 23, 2005 4:49 pm |
|
|
|
But now it seems that I have card/firmware loading:
or51132: Waiting for firmware upload(dvb-fe-or51132-qam.fw)...
or51132: Version: 10001334-17430000 (133-4-174-3)
or51132: Firmware upload complete.
Now, how do I go about actually tuning something? |
|
|
|
|
 |
Re: Loading Firmware |
 |
Posted: Tue May 24, 2005 12:37 pm |
|
|
| Troy |
|
|
| |
| Joined: 21 May 2005 |
| Posts: 10 |
|
|
|
 |
 |
 |
|
| HDTV buff wrote: | | Troy wrote: | | Thank you! This is exactly what I wanted to know.... I have heard other people claim that the firmware was loaded when the module is loaded but in my case it happens just as you explained. Are you using the DVB driver and Mythtv? |
I am using a plain vanilla kernel 2.6.12-rc2. It is running against a cvs of MythTV from 3/28, I believe. OS is Debian unstable.
I am running the built-in drivers (dvb) that came with the kernel and I am compiling the MythTV against the kernel as the dvb source.
This is the script I use to grab the latest mythtv
| Code: | #Create the directory
rm -fR /usr/src/download/mythtv/cvs.`date '+%F'`
mkdir -p /usr/src/download/mythtv/cvs.`date '+%F'`
cd /usr/src/download/mythtv/cvs.`date '+%F'`
# Get from CVS
echo Password is 'mythtv'
cvs -d :pserver:mythtv@cvs.mythtv.org:/var/lib/mythcvs login
nice -n 19 cvs -z3 -d :pserver:mythtv@cvs.mythtv.org:/var/lib/mythcvs \
checkout mythtv mythplugins nuvexport
MYTHCONF="--enable-dvb \
--dvb-path=/lib/modules/`uname -r`/build/include \
--enable-dvb-eit --enable-opengl-vsync --enable-xvmc"
MYTHLIBCONF="--enable-opengl --enable-fftw \
--enable-sdl --enable-aac --enable-transcode --enable-vcd"
ERROR="no"
# Build Mythtv
[ $ERROR = "no" ] && cd mythtv || ERROR="yes"
[ $ERROR = "no" ] && ./configure $MYTHCONF || ERROR="yes"
[ $ERROR = "no" ] && qmake || ERROR="yes"
[ $ERROR = "no" ] && nice -n 19 make || ERROR="yes"
# Make sure modules can be built (so partial builds can be avoided)
[ $ERROR = "no" ] && cd ../mythplugins || ERROR="yes"
[ $ERROR = "no" ] && ./configure $MYTHLIBCONF || ERROR="yes"
[ $ERROR = "no" ] && qmake || ERROR="yes"
#[ $ERROR = "no" ] && nice -n 19 make || ERROR="yes"
# do not want to build them with old libraries
#[ $ERROR = "no" ] && nice -n 19 make distclean
# Install MythTV and libs (after an uninstall of the older version).
[ $ERROR = "no" ] && make uninstall
[ $ERROR = "no" ] && cd ../mythtv || ERROR="yes"
[ $ERROR = "no" ] && make uninstall
[ $ERROR = "no" ] && make install || ERROR="yes"
# Build myth modules (and install them)
[ $ERROR = "no" ] && cd ../mythplugins || ERROR="yes"
[ $ERROR = "no" ] && ./configure $MYTHLIBCONF || ERROR="yes"
[ $ERROR = "no" ] && qmake || ERROR="yes"
[ $ERROR = "no" ] && nice -n 19 make || ERROR="yes"
[ $ERROR = "no" ] && make install || ERROR="yes"
# Install nuvexport
[ $ERROR = "no" ] && cd ../nuvexport || ERROR="yes"
[ $ERROR = "no" ] && make install || ERROR="yes"
# Restart services
[ $ERROR = "no" ] && killall mythfrontend && sleep 1s
[ $ERROR = "no" ] && killall mythbackend && sleep 3s
[ $ERROR = "no" ] && /bin/su - -c "mythbackend --daemon \
--logfile /var/log/mythtv/mythbackend.log \
--pidfile /var/run/mythtv/mythtv.pid" mythtv
|
-HDTV Buff |
This is my config for mythtv .18
| Code: |
./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-altivec --enable-audio-oss --enable-audio-alsa --disable-audio-arts --disable-audio-jack--enable-lirc --enable-joystick-menu --disable-xvmc-vld --enable-dvb --enable-dvb-eit --dvb-path=/usr/include --enable-opengl-vsync --enable-vorbis --enable-xvmc --enable-xv --disable-directfb --enable-x11 --enable-proc-opt --enable-mmx --compile-type=release --disable-distcc
|
Why do you have /lib/modules in the path to build myth with dvb support? Shouldn't that be /usr/include or whatever the path is to the dvb headers? In any case I don't think that is the problem I'm having because i have two other DVB-S cards in this system working perfectly with mythtv. I do have another question, when you go to mythsetup and select your HD3000 card under the DVB section. What info do you get out beside 'Card Name' ? |
|
|
|
|
 |
 |
Re: Loading Firmware |
 |
Posted: Tue May 24, 2005 2:07 pm |
|
|
| HDTV buff |
|
|
| |
| Joined: 02 Mar 2005 |
| Posts: 114 |
| Location: Maryland, USA |
|
|
 |
 |
 |
|
| Troy wrote: | | Why do you have /lib/modules in the path to build myth with dvb support? Shouldn't that be /usr/include or whatever the path is to the dvb headers? In any case I don't think that is the problem I'm having because i have two other DVB-S cards in this system working perfectly with mythtv. I do have another question, when you go to mythsetup and select your HD3000 card under the DVB section. What info do you get out beside 'Card Name' ? |
I use /lib/modules in the path because that allows me to build mythtv against the dvb headers in the kernel.
As of 2.6.12-rc2, dvb is fully merged into the "vanilla" kernel. Therefore, there is no difference in headers between the dvb cvs and the kernel headers (for the purpose of using pchdtv cards).
Also, you should really compile mythtv against the headers you are running. Therefore, unless you are running dvb cvs, you really should not use those headers.
Hardcoding paths in scripts tend to make them sloppy and non-portable. This script will compile correctly, as long as you are using 2.6.12-rc2 or later.
Finally to answer your question. When I select the pcHDTV card under dvb, the only info I get is the name. I believe mine says "PCHDTV_3000". But I could be wrong and I would have to go home to find out.
The mythtv setup screen does not give any other (useful) information.
-HDTV Buff |
|
|
|
|
 |
 |
Re: Loading Firmware |
 |
Posted: Wed May 25, 2005 10:00 pm |
|
|
|
| HDTV buff wrote: | | Troy wrote: | | Why do you have /lib/modules in the path to build myth with dvb support? Shouldn't that be /usr/include or whatever the path is to the dvb headers? In any case I don't think that is the problem I'm having because i have two other DVB-S cards in this system working perfectly with mythtv. I do have another question, when you go to mythsetup and select your HD3000 card under the DVB section. What info do you get out beside 'Card Name' ? |
I use /lib/modules in the path because that allows me to build mythtv against the dvb headers in the kernel.
As of 2.6.12-rc2, dvb is fully merged into the "vanilla" kernel. Therefore, there is no difference in headers between the dvb cvs and the kernel headers (for the purpose of using pchdtv cards).
Also, you should really compile mythtv against the headers you are running. Therefore, unless you are running dvb cvs, you really should not use those headers.
Hardcoding paths in scripts tend to make them sloppy and non-portable. This script will compile correctly, as long as you are using 2.6.12-rc2 or later.
Finally to answer your question. When I select the pcHDTV card under dvb, the only info I get is the name. I believe mine says "PCHDTV_3000". But I could be wrong and I would have to go home to find out.
The mythtv setup screen does not give any other (useful) information.
-HDTV Buff |
I'm not using the cvs-dvb drivers anymore so I guess I'll try your suggestion.
| Code: |
./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-altivec --enable-audio-oss --enable-audio-alsa --disable-audio-arts --disable-audio-jack --enable-lirc --enable-joystick-menu --disable-xvmc-vld --enable-dvb --enable-dvb-eit --dvb-path=/lib/modules/2.6.12-rc4-mm2/build/include --enable-opengl-vsync --enable-vorbis --enable-xvmc --enable-xv --disable-directfb --enable-x11 --enable-proc-opt --enable-mmx --compile-type=release --disable-distcc
WARNING: include the output of ./configure along with
any bug report, when using a processor optimized build.
Warning: DVB location points into kernel (ok if kernel >= 2.6.11)
# Basic Settings
Compile type release
Compiler cache no
DistCC no
Install prefix /usr
CPU x86 (Intel(R) Pentium(R) 4 CPU 2.80GHz)
Big Endian no
MMX enabled yes
Vector Builtins no
# Input Support
Joystick menu yes
lirc support yes
ivtv support yes
FireWire support no
DVB support yes [/lib/modules/2.6.12-rc4-mm2/build/include]
# Sound Output Support
OSS support yes
ALSA support yes
aRts support no
JACK support no
# Video Output Support
x11 support yes
xrandr support yes
xv support yes
XvMC support yes
XvMC VLD support no
OpenGL vsync yes
DirectFB no
|
compiling now; I'll report back shortly and let you know the outcome. Thanks again for your help.
-Troy |
|
|
|
|
 |
 |
Re: Loading Firmware [SOLVED] |
 |
Posted: Wed May 25, 2005 10:54 pm |
|
|
| Troy |
|
|
| |
| Joined: 21 May 2005 |
| Posts: 10 |
|
|
|
 |
 |
 |
|
| Anonymous wrote: | | HDTV buff wrote: | | Troy wrote: | | Why do you have /lib/modules in the path to build myth with dvb support? Shouldn't that be /usr/include or whatever the path is to the dvb headers? In any case I don't think that is the problem I'm having because i have two other DVB-S cards in this system working perfectly with mythtv. I do have another question, when you go to mythsetup and select your HD3000 card under the DVB section. What info do you get out beside 'Card Name' ? |
I use /lib/modules in the path because that allows me to build mythtv against the dvb headers in the kernel.
As of 2.6.12-rc2, dvb is fully merged into the "vanilla" kernel. Therefore, there is no difference in headers between the dvb cvs and the kernel headers (for the purpose of using pchdtv cards).
Also, you should really compile mythtv against the headers you are running. Therefore, unless you are running dvb cvs, you really should not use those headers.
Hardcoding paths in scripts tend to make them sloppy and non-portable. This script will compile correctly, as long as you are using 2.6.12-rc2 or later.
Finally to answer your question. When I select the pcHDTV card under dvb, the only info I get is the name. I believe mine says "PCHDTV_3000". But I could be wrong and I would have to go home to find out.
The mythtv setup screen does not give any other (useful) information.
-HDTV Buff |
I'm not using the cvs-dvb drivers anymore so I guess I'll try your suggestion.
| Code: |
./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-altivec --enable-audio-oss --enable-audio-alsa --disable-audio-arts --disable-audio-jack --enable-lirc --enable-joystick-menu --disable-xvmc-vld --enable-dvb --enable-dvb-eit --dvb-path=/lib/modules/2.6.12-rc4-mm2/build/include --enable-opengl-vsync --enable-vorbis --enable-xvmc --enable-xv --disable-directfb --enable-x11 --enable-proc-opt --enable-mmx --compile-type=release --disable-distcc
WARNING: include the output of ./configure along with
any bug report, when using a processor optimized build.
Warning: DVB location points into kernel (ok if kernel >= 2.6.11)
# Basic Settings
Compile type release
Compiler cache no
DistCC no
Install prefix /usr
CPU x86 (Intel(R) Pentium(R) 4 CPU 2.80GHz)
Big Endian no
MMX enabled yes
Vector Builtins no
# Input Support
Joystick menu yes
lirc support yes
ivtv support yes
FireWire support no
DVB support yes [/lib/modules/2.6.12-rc4-mm2/build/include]
# Sound Output Support
OSS support yes
ALSA support yes
aRts support no
JACK support no
# Video Output Support
x11 support yes
xrandr support yes
xv support yes
XvMC support yes
XvMC VLD support no
OpenGL vsync yes
DirectFB no
|
compiling now; I'll report back shortly and let you know the outcome. Thanks again for your help.
-Troy |
That did it! You rock HDTV buff!!!!!!!!!!!! |
|
|
|
|
 |
pcHDTV Forum Index -> HD-2000/3000 drivers
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
All times are GMT - 7 Hours
Page 1 of 1
|
|
|
|
|