lhebui
Bonjour,
je n'arrive pas à configurer mysql pour mythtv.
Je ne comprends pas trop le howto de fedora la-dessus ...
"6.2 Setting up the initial database
This step is only required on the system maintaining the database, which may or may not be one of your MythTV boxes. If the database is on a non-MythTV machine you'll need to copy the database/mc.sql file to it.
To setup the initial MySQL databases:
$ cd database
Mandriva and Red Hat Linux/Fedora Core
$ mysql -u root < mc.sql"
il me répond qu'il ne connaît pas mc.sql et je suis d'accord avec lui car je ne sais pas où est ce fichier !
De plus, il faut donner les droits à mythtv pour mysql, je suis d'accord mais l'exemple est très laconique pour moi ...
For a more secure setup, you can restrict which machines or subnets have access. If you have a complete DNS system operational, you could do the following:
$ mysql -u root mythconverg
mysql> grant all on mythconverg.* to mythtv@"%.mydomain.com" identified by "mythtv";
mysql> flush privileges;
Déja, il ne connaît pas mythconverg.
De plus, mydomain.com correspond à quoi ? à mon nom de domaine ?
Bref, un tas de questions pour le béotien que je suis.
lhebui
Ca y est !!!!
J'ai trouvé où se trouve mc.sql. Il se trouve à /usr/share/doc/mythtv/database.
J'ai fait la manip préconisée : $ mysql -u root < mc.sql
Cela a fonctionné et j'arrive maintenant à lancer mythtv.
Bon, j'en suis à la config ...
lhebui
Maintenant, j'essaie de charger les chaines.
J'ai mis ma carte en video analogique et en dvb 3.x.
Que cela soit dans les 2 configs, il n'arrive pas à charger le grab_fr comme si la liaison internet n'existait pas alors que le cmd fonctionne très bien en ligne de commande.
Quoi faire, je ne sais plus. Pourtant, il reconnaît bien la puce de ma carte nova-t, c.a.d. connexant ...
lhebui
Bon, jessaie toujours d'arriver à bout de la config de mythtv avec ma nova-t et j'ai trouvé un tuto intéressant mais je ne trouve pas par exemple /etc/modules.conf, comme quoi je me trouve devant le mur de mon ignorance ...
Voici le texte :
Last time when we were testing the card we manually loaded the DVB driver modules. Now we want them to load each time the machine starts or the DVB card is used. This can either be done by editing the /etc/modules.conf file or by manually running a script to insert the correct modules.
For the moment we'll use a script while we get everything working. If you haven't already done so run make install in the build-2.4 directory where the DVB driver source is located followed by depmod -a.
Now take the insmod.sh script and make a copy of it. Remove all the lines that refer to frontend chips that you don't have on your card(s) or to types of cards you don't have in your system. In my case I'm left with one of the Grundig frontends and the TDA10045 frontend. Both my cards a Nova-T models so I also need the modules for a PCI budget card plus the core DVB modules. One of the cards has a CAM interface connector and needs a slightly different module.
This gives me the following:
#!/bin/sh
#
# Load DVB Modules
#
modprobe v4l1-compat
modprobe v4l2-common
modprobe video-buf
modprobe dvb-core
modprobe grundig_29504-401
modprobe tda1004x
modprobe saa7146
modprobe saa7146_vv
modprobe ttpci-eeprom
modprobe dvb-ttpci-budget
modprobe dvb-ttpci-budget-ci
If you're using the 2.6 kernel the names have changed slightly. The last two lines become:
modprobe budget
modprobe budget-ci
Now arrange for this script to be executed as root towards the end of your boot sequence. It mythbackend is started automatically it needs to be run before the backend starts. Details of how to do this vary according to distribution. In many cases it can be placed in /etc/init.d and symlinked from /etc/rc5.d/S99localdvb. Consult the documentation for your Linux system for the correct way to do this.
Now reboot the machine. Run /sbin/lsmod and check that the modules listed above are present. Also run dmesg and check that they were loaded and the drivers registered adapters and frontends correctly. If everything worked during testing there should be no problems now because the process is essentially the same.
Now start the mythtv backend manually if it doesn't auto start on your setup.
Quelqu'un sait-il ?
