View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 53 posts ] 
Go to page 1, 2, 3, 4  Next

Print view Previous topic   Next topic  
Author Message
Search for:
PostPosted: Sun Sep 09, 2007 5:41 pm 
Offline
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location: Arlington, MA
Don't Panic! :-) The Hitchhiker's Guide to KnoppMyth R5F27

This is a very long post which covers everything from pre through post install issues and fix ups. Do not let this frighten you off. It's long because I tried to write it at a "drunken monkey" level of detail, with the intent that you can cut & paste the example commands shown directly from this posting into a shell window on your KnoppMyth box. Please scroll down and look at the bold headings to get a feel for what it covers... If you're looking for something specific please use your browsers page search feature. Also, please read through the "Known Changes" and "Known Issues" sections, for various potential "gotchas" before you install or upgrade. They often point you to steps that you need to do to avoid problems.

These posts were originally an upgrade guide, and that is still the main focus, but most of the setup hints and the information under "Known Issues" and "Known Changes" still apply for a fresh install.

This is also intended to be a supplement to Cecil's Pamphlet and change list rather than a replacement. As a result it tends to skip issues they cover, so don't forget to review those before you start.

Finally, a note on the color coding used here, red is used for file system objects (files, directories, ...), green is used for sample commands (partial or complete), indigo is used for GUI menu paths, and text in blue is a link to another posting/thread or web page.

ALL THE COMMANDS SHOWN HERE MUST BE RUN AS ROOT! - See this wiki page for instructions on how to BecomeRoot.

Known Changes

There are a number of changes with consequences which may bite you on an upgrade, especially from a version older than R5E50, or which may affect old documentation.

    1) Backup and Restore changes:

      1.1) The backup format has changed versus the one used in KnoppMyth versions before R5C7. Use the manual conversion process described under "Phase 0" item #1 below to ensure that your backup will work as intended.

      1.2) The default compression format of the backup has changed versus R5C7 and later. The restore script will auto-detect the correct compression type if you don't confuse it by having copies of /myth/backup/savedfiles.tar* and/or /myth/backup/mythconverg.sql* with different compression types. This includes uncompressed versions, but not the version numbered files (i.e. /myth/backup/*.[1-9]). See the command described under "Phase 0" item #1.4 below to ensure that you don't have conflicting names.

      Note that this also means that any custom scripts or examples which extract things from the backup need to be changed to match. For tar archives this means using the options zxvf to extract .tar.gz files from the backup rather than using jxvf for .tar.bz2, for other files this means using the gzip command rather than bzip2.

      1.3) For versions using the new style backup (R5C7 and later) there are certain things which should be removed from your custom /myth/backup/restore.list before upgrading. These can replace modern versions with out of date versions:
      Code:
      ./etc/webmin/miniserver.conf
      ./etc/lvm/lvm.conf

      The builtin restore list contains the following files and directories, they should also be removed from your personal list:
      Code:
      ./root
      ./home
      ./etc/mythtv/modules
      ./etc/lirc
      ./etc/htdigest
      ./etc/apache2/apache2.conf
      ./var/www/mythweb/.htaccess
      ./etc/X11/xorg.conf
      ./etc/asound.conf
      ./etc/default/aumix
      ./var/lib/alsa/asound.state
      ./etc/mplayer/mplayer.conf
      ./etc/localtime
      ./etc/timezone

      Please note that the /myth/backup/backup.list and /myth/backup/restore.list files are optional and don't exist unless you created them.

    2) X Server and Desktop changes:

      2.1) The switch from the XFree86 to the x.org X server used in R5D1 and before means merging customizations (such as mode lines) from the old file (/etc/X11/XF86Config-4) to the new one (/etc/X11/xorg.conf). Pay particular attention to the "Monitor" section. Do not simply copy over the whole file. There are some options in the old one that will give the new server serious indigestion. Some rules of thumb:
        1) In your "Monitor" section copy over the Modeline entries, along with your HorizSync and VertRefresh settings.
        2) You can probably copy the "Screen" section across pretty much intact.
        3) Be extra careful around Option lines in your "Device" section and Load lines in your "Module" section since this is where the worst incompatibilities are.
      You may also need to tweak some of your nvidia-settings to work better with the new server.

      2.2) GDM is gone and won't be coming back. Rather than using "/etc/init.d/gdm restart" to restart the frontend from the command line you can now use "pkill xinit". To stop X entirely you can drop to single user mode using "telinit 1" at the console and then kill xinit using the command described above.

      2.3) The use of DisplaySize to get a particular DPI value has been superseded, at least for the nVidia driver, by the following settings in your Monitor section:
      Code:
              Option "UseEdidDpi" "FALSE"
              Option "DPI" "100 x 100"

      In older versions you also had to fix the arguments passed to the X server in /etc/X11/xinit/xserverrc but this is no longer an issue. See this thread for more discussion - http://mysettopbox.tv/phpBB2/viewtopic.php?t=13219

      2.4) If you have problems with the x.org server starting up on the first boot off the hard disk PLEASE check your logfiles before posting questions about:
      Quote:
      INIT: Id "c7" respawning too fast: disabled for 5 minutes
      the fixes are generally simple configuration or driver install issues. For the Nvidia driver, compatibility is determined using information from their website, which is not always complete. As a result it's not uncommon to have to force the driver install. E.g. for newer cards:
      Code:
      install-nvidia-debian.sh 1.0.9755 -force

      for older cards especially MX4 or MX2 family:
      Code:
      install-nvidia-debian.sh 1.0.7185 -force

      Search the forums or the wiki for more detailed instructions.

      2.5) There are still some newer Nvidia motherboard graphics that aren't supported. If you have a motherboard with a Nvidia Nforce 630a chipset with builtin GeForce 7025 or 7050 graphics you need a driver which is not yet available in KnoppMyth.

      2.6) For the Savage/S3 video chips try changing all references to "s3" in xorg.conf to "savage" as per squiffy's post in this thread titled "FIXED! - INIT: Id "c7" respawning too fast: disabled".

      2.7) For VIA embedded video chips like the CLE266 see this thread titled "R5F27 install display issues" for some setup changes you may need to make. In particular, note that the driver name has changed.

    3 ) Serial port changes:

      3.1) The serial mouse setup in the default xorg.conf file can cause the X server to grab and lock the serial port, which can make it inaccessible for other uses. Removing or commenting out that InputDevice section in your /etc/X11/xorg.conf and restarting X will free it up.

    4) The switch to udev for hot-pluggable devices may cause some of the device names to change, especially USB devices.

      4.1) The lirc device has changed from "/dev/lirc" or "/dev/usb/hiddev0" to "/dev/lirc0". This should be taken care of by the "lirc-reconfig.sh" script which is run during setup.

      4.2) For audio you may have to run alsaconf, and change "/dev/dsp0" to "/dev/dsp" in the setup.

      4.3) Switching to udev also means that removable storage devices (CDs, USB drives, ...) should be pretty much "plug and play" with no extra setup required, however, the default mount points may have changed as a result. For example my USB thumbdrive is now automatically mounted on "/media/usbdisk" when it is plugged in. A second drive gets mounted as /media/usbdisk-1 and so on.

    5) IVTV driver changes:

      5.1) R5F27 uses version 1.1.0 of the ivtv driver, which would not normally be compatible with the 2.6.18 kernel being used, however, Cecil has built using the whole modern suite of modern v4l2 drivers and utilities. Due to interface differences between the 1.x.x and the 0.10.x branches you cannot mix and match, as a result, attempting an "upgrading" to the latest 0.10.x driver will break your system.

      5.2) The newer drivers have input names and numbering which conform to the latest V4L2 interface standard. If you are upgrading from a version older than R5E50 the DB configuration contains references to the obsolete names. You must follow the "Post Install Setup" directions below. Failure to do this will cause all sorts of bizarre and mysterious errors.

      5.3) The module options for the ivtv drivers have also changed a great deal, even versus R5E50. The KM upgrade scripts try to clean out the most common obsolete options, but there are just too many possible options and too many places people can hide them. If you see an error due to an invalid ivtv module option in your logfiles you'll need to hunt for them under /etc.

      5.4) With the new version of the ivtv drivers many settings which you used to be able to adjust with ivtvctl, must now be done using the v4l2-ctl utility. Run it with the --help option for a complete list of the command options. The /etc/init.d/set_ivtv_params script can be used to force normal defaults at startup for cards which come up with strange ones. It can also be customized for users who need nonstandard initialization. To enable it at boot time use:
      Code:
      update-rc.d set_ivtv_params defaults


      5.5) The new drivers also mean changes to the PVR-350 output.

        5.5.1) If you have a large black box covering most of the center of the screen you may need to add the following line to your /etc/mythtv/modules/ivtv file as per the IVTV Troubleshooting page:
        Code:
        options ivtv-fb osd_compat=1

        Please see the IVTV troubleshooting page linked above for details.

        5.5.2) The frame buffer module name has changed from "ivtv-fb" to "ivtvfb". Check /etc/mythtv/modules/ivtv and ensure that it contains the correct name. See this post for more discussion: http://mysettopbox.tv/phpBB2/viewtopic.php?t=16412

        5.5.3) If your TV output works during install and stops after the first boot it may be the old framebuffer device shift gotcha. Check your /etc/X11/xorg.conf and make sure that the "fbdev" option is pointing to the right device. There's a good write up in this thread. http://mysettopbox.tv/phpBB2/viewtopic.php?t=16423

      5.6) The new drivers also require new firmware, even versus R5E50. If you have problems, make sure you've shut the machine down (powered off and unplugged) for 1-2 minutes to force the old firmware to be cleared.

    6) Remote access changes:

      6.1) For improved security, direct ssh access as the "mythtv" and "root" users and for users with blank passwords has been disabled in /etc/ssh/sshd_config. For ssh access as root you must login as user created during phase 1 installation, run "su - root", and provide the root password.

      6.2) IE interoperability with digest authentication can now be achieved by running the following command:
      Code:
      ToggleWebSecurity.sh -all

      If security is already enabled, you may need to run it twice to first toggle it off, and then back on. IE should actually work without any changes for a new install, the only place where this may be an issue is for an upgrade.

      6.3) Freenx was replaced with VNC for remote desktop access. The VNC password is preconfigured to "mythtv" and can be changed by editing the -passwd value in the command that starts x11vnc in the /home/mytht/.fluxbox/apps file. There's no way to do this topic justice here so I'll have to refer you to the x11vncHowTo page on the wiki.

      6.4) When setting up mysql for a MBE/SBE/FE multi-machine configuration (LinHES), the /etc/mysql/my.cnf file no longer contains a 'skip-networking' line to comment out. Instead, you can either comment out the bind-address line or change it to your machines primary IP address (this requires static IP address assignments). If you have multiple active network interfaces, change the IP address to that of the NIC facing your other machines.

    7) Other changes to included software modules and packages:

      7.1) Some of the theme names have changed versus pre-R5E50 builds, often in subtle ways. In particular I'm aware that Isthmus (with an upper case "I") is now spelled isthmus (with a lower case "i"). If you are not seeing any OSD information while watching live or recorded TV this is most likely the problem. Simply go into the setup menus and pick a different OSD theme. If you have a theme which won't even let you get to the menus see this thread - "Picking a new theme from the command line"

      7.2) The full kernel source is no longer included, however, the kernel headers needed to compile modules are. I have personally compiled both ivtv and nVidia drivers using these. Cecil has also made the full kernel source available via this thread - "So you want the kernel source..." but you really shouldn't need it.

      7.3) Cecil has taken a more conservative approach on codecs in recent releases. So far everything I've tried has just worked, however, if you encounter some old video, in a format that used to work but doesn't any more, see this posting for details on installing extra codecs - HowTo: Update mplayer & install new CODECs

      7.4) MythArchive has replaced MythBurn. MythArchive has a full blown GUI which can be accessed under Optical Disks -> Archive Files from the main menu. The old MythWeb interface has been removed. If you are upgrading from an older version (R5D1 or before) you may need to manually create the "archiveitems" table. See this thread for details. http://mysettopbox.tv/phpBB2/viewtopic.php?t=15163

      7.5) The atscscan and dvbscan utilities have been replaced with a single unified scan program.

      7.6) RRD improvements. 1) The MBFan monitoring should now work if mbmon works for your motherboard. You may need to twiddle the numbering where indicated in the script. 2) The UPS monitoring should now work for an APC UPS which is connected via a USB cable. To enable this run the setup_apcupsd.sh script.

      7.7) Using ALSA AC3 pass through with an SPDIF output now requires using a different device name. See this thread for details - http://mysettopbox.tv/phpBB2/viewtopic.php?t=16581

Known Issues

There are also a handful of known issues, mostly minor and with known work arounds:

    1) There is a known false alarm with the restore scripts sanity checking. See this thread for more details. http://mysettopbox.tv/phpBB2/viewtopic.php?t=15246

    2) There is some kind of bug in the mythtv-setup utility (one of the MythTV modules) which can produce bogus entries in the cardinput table. If you get an error about "Card 0 (type) is set to start on channel 2, which does not exist.", see the "Post Install Setup" section below.

    3) If the mythtv backend process doesn't appear to come up after an upgrade or install (one symptom is an empty recordings list), running /etc/init.d/mythtv-backend restart as root should get it back. You can also do this using the Alt-3 key shortcut from the GUI desktop. See the following posting on the 4th page of this thread for a permanent fix. http://knoppmyth.net/phpBB2/viewtopic.php?p=106245#106245

    4) There is a known IVTV driver issue with some PVR-150 and PVR-500 cards glitching (tearing, pixellation) when using the default 480x480 recording profile and VBI encoding. Using a 720x480 capture resolution and/or turning off VBI is strongly recommended for these cards. If you change the capture resolution, don't forget to adjust your recording bit rates to match or image quality may suffer. You can find these settings under Utilities/Setup -> Setup -> TV Settings -> Recording Profiles -> MPEG-2 Encoders. You need to change all of the profiles, including Default and Live TV. You can also adjust your bit rates here for the higher resolution. For more details, see the postings by ethernut in this thread - http://mysettopbox.tv/phpBB2/viewtopic.php?t=13097.

    5) If you are using a Hauppauge remote with the IR sensor dongle connected directly to the card and it only works sporadically you may need to disable the ir_kbd_i2c module as described below. The ir_kbd_i2c and lirc_i2c modules simply do not play together nicely, with ir_kbd_i2c stealing events from lirc_i2c, and must occasionally be forcibly separated.

    -> If you are not using a capture card which depends on the saa7134 module (typically DVB, HDTV and some other cards) you can either skip loading of the driver or remove it completely. Search your dmesg output for saa7134 to be sure:
    Code:
    dmesg | grep saa7134

    The following chunk from my personal post install tweaks script comments out the loading of various dvb modules which happens whether you need them or not:
    Code:
    # Stop it from loading the dvb stuff which drags in the IR keyboard stuff
    sed -si.orig -e 's/^\(modprobe dvb-bt8xx\)/#\1/' \
                 -e 's/^\(modprobe saa7134-dvb\)/#\1/' \
                 -e 's/^\(modprobe cx88-dvb\)/#\1/' \
        /etc/init.d/KnoppMyth-tv
    reboot

    This is usually good enough, but I ended up deleting the driver because something else seemed to trigger the loading of those things regardless. :?
    Code:
    rm -f /lib/modules/2.6.18-chw-13/kernel/drivers/media/video/ir-kbd-i2c.ko

    --> If you do have a capture card that requires the saa7134 driver and thus the ir_kbd_i2c driver, your options look like this:
      1) Avoid this combination of hardware. Not ideal.
      2) Don't use the PVR card connection in system with a 7134 based card. Replace it with something like the StreamZap sensor. Basically solving the problem by tossing a little money at it.
      3) Dummy out the guts of the ir_kbd_i2c driver or figure out how to remove the references to it in the saa7134 driver. This is the "sweat equity" approach. There is some coverage on it here: http://mysettopbox.tv/phpBB2/viewtopic.php?t=16400 marc.aronson has made a patched version of the driver module available on the wiki.
    6) The udev hardware detection can result in unstable device name assignments. The biggest problems people typically have with this is in systems with multiple different capture cards. Search for the writeup that bruce_s01 did on pinning down the device assignments. I don't think we've had a report of this problem in quite a while now, so I may remove this entry.

    7) The new Nvidia drivers don't play nicely with some older chips (Especially MX4 series). Please do all the usual diagnostics first, but if you have a persistent failure, especially on a card that worked with older versions, see the wiki troubleshooting page for directions on how to install the older drivers from an R5F1 CD.

    8 ) If you have an "ATI Remote Wonder" RF remote control, you need to use the dragon kernel mod for it to work properly. See this thread for directions: http://knoppmyth.net/phpBB2/viewtopic.php?t=17810

Hints for Upgrading or Installing

This information is intended to apply equally whether you're doing an "Auto Upgrade" or a manual upgrade. Much of it also applies you're doing a fresh install.

Please note, Auto Upgrade only works if you originally did an Auto Install. If you did a manual install you need to do a manual upgrade. The important distinction between auto and manual install here has to do almost entirely with your disk layout, and in particular if your root partition and swap are in the "expected" locations. Whether you've manually added new software or patches on top of that original install generally doesn't matter. On the other hand, if you had started with an auto install, done all the device name fixups required, and moved the disk to a different location on the IDE bus, auto upgrade wouldn't work. See this post for more details about the expected disk layout - http://mysettopbox.tv/phpBB2/viewtopic.php?p=96417 See the Pamphlet for details on doing a manual upgrade.

Phase 0 - Before you upgrade:

A lot of the information below depends on which version you're upgrading from. If you've forgotten which release you're currently running, you can find out using the following command:
Code:
cat /etc/KnoppMyth-version

For more on this topic see this post on "KnoppMyth version naming".

    1) Make a backup using the mythbackup script and verify that it worked. In more recent versions, like R5D1, the verification is done automatically as part of the backup. In older versions you must do it manually, as described in the detailed steps below. Please note, the less time between when you make the backup and when you do the upgrade, the better. If the delay is more than a couple hours, you should redo the verification step to make sure that the backup is still current. You can't do a successful upgrade without a valid and up to date backup.

      1.1) As root, run the backup command:
      Code:
      mythbackup

      1.2) If (and only if) you are upgrading from a version of KnoppMyth before R5C7, you must manually convert your old style backup into a new style backup by archiving all of /etc /root and /home. To do this run the following commands as root:
      Code:
      cd /
      tar zcvf /myth/backup/savedfiles.tar.gz ./etc ./root ./home

      The leading ./ on these three directory names is important. Don't forget it, or your backup/restore won't work properly!

      If you are upgrading from version R5C7 or later please skip this step.

      1.3) Check that the backup worked! If you are upgrading from:
        - R5F1, R5E50, R5D1 - The check is done automatically, you can double check using /usr/local/bin/checkbackup
        - R5C7 and earlier versions - Get the check_backup.sh script which can be found on the MythBackupAndRestoreHowTo page on the wiki. Note that you may need to make a simple change to the tar commands in that script, as described under Known Changes item 1.2 above, to match the actual compression types of your backup files.
      If there is an error in the backup, please report the messages produced by the checkbackup script.

      1.4) You should also run the following command to check that you don't have multiple compression formats for a given backup filename which will cause confusion later:
      Code:
      ls -l /myth/backup/savedfiles.tar* /myth/backup/mythconverg.sql* |
       sed '/\.[0-9]$/d'

      It's OK if the savedfiles.tar and mythconverg.sql compression (or lack thereof) are different, however, the files should both show the same current date. On my system it produces these healthy results:
      Code:
      root@black2:/# ls -l /myth/backup/savedfiles.tar* /myth/backup/mythconverg.sql* | sed '/\.[0-9]$/d'
      -rw------- 1 root root 13715983 Dec 30 14:20 /myth/backup/mythconverg.sql.gz
      -rw------- 1 root root  7958370 Dec 30 14:21 /myth/backup/savedfiles.tar.gz
    See the "Taking advantage of the enhanced backup and restore scripts" posting for more information on using backup and restore. Also see the "Known Changes" section above for more things to beware of.

    2) Make a list of any add ons you've installed or extra configuration you've done while you've still got the old install to refer to.

    3) Make a note of your current hostname. This is very important, since changing the hostname can make various DB entries keyed by hostname useless. The following command will print your hostname:
    Code:
    hostname

Phase 1 - When you boot from the CD:

    1) Pick the appropriate boot options. Remember case matters!

      1.1) Always use the "testcd" option in your boot command as shown in the examples below, or use the "Check Media" option on the main menu, especially if this is first time you've used a given CD with a particular machine. If the validation fails do not continue the upgrade!

      1.2) Using the "tv" option on your boot command is strongly recommended. Otherwise the install defaults to a potentially unreadable 1280x1024 resolution. This is one of those "more is not always better" cases. ;-) For example:
      Code:
      tv testcd

      1.3) If (and only if) the installer hangs probing for SCSI devices boot using the "noscsi" options. For example:
      Code:
      tv noscsi testcd

      1.4) If your motherboard has the Intel ICH8 chipset, add the the "intelfix" option to enable support for this new chipset. The installer takes care of the rest. For example:
      Code:
      tv intelfix testcd

    2) Do not use the name "mythtv" when prompted to create a user account. The mythtv user is already created automatically. Don't forget to make a note of that user name and the passwords you pick for that user and the administrator (root) accounts.

    3) Make sure you use the same hostname (machine name) when doing an upgrade! Look at the notes you made before the upgrade and enter that name when prompted. Using a different hostname will cause a number of nasty problems with various tables in the DB, particularly the settings table, which uses the hostname as one of its keys. Changing the hostname is a project beyond the scope of these hints.

Phase 2 - After the install from the CD and reboot

Phase 2a. Before entering the root password to start the setup dialogs:

To do any of these tasks you'll need to switch to an alternate virtual console using Ctrl-Alt-F1 and login there as root.

    1) If you're using LVM with the standard volume group name of "vg" use the recreate_lvm.sh script to restore it. Otherwise you'll need to edit the script to use the "right" volume group name for you system. This is a nondestructive operation and only gets the system to recognize what is already there. You can also create an lvm volume group during an install by using the create_lvm.sh script. Search the wiki for "LVM" for more details.

    2) If you have some other nonstandard disk arrangement you may need to correct your /etc/fstab and mount the updated partitions. Especially /myth! The restore will fail if it can't find the /myth/backup directory.

    3) If X isn't working out of the box, you may need to merge certain setting from your old working XF86Config-4 into the new /etc/X11/xorg.conf. It's also not uncommon to have to force the Nvidia driver install. Please see the "Known Changes" section above for more details.

    4) Do any other fixups that you need to complete before the Phase 2b Setup Dialogs run.
When you have completed any tweaks, use Alt-F7 to switch back to the GUI desktop virtual console screen.

2b. Setup dialogs:

    1) For new installs make sure you get the timezone right. This is easy to screw up and will lead to really annoying problems with your program guide at the very least. If you botch this see the ProgramGuideIsOff page on the wiki. For upgrades this should be restored automatically..

    2) If there is an error in the restore, please check the logfile /var/log/restore.log and report the messages after the line that says "Sanity checking your restore..."

    3) Make a note of the passwords you pick.

Phase 3 - Post install setup:

    1) IVTV driver (Hauppauge PVR and compatibles cards) configuration:

      1.1) If you are upgrading from a version of KnoppMyth before R5E50, and you have a PVR card, you must drop all of your card definitions and recreate them! This is necessary because the version of the ivtv driver included in this release uses different input names and numbering to conform to the standard V4L2 interface, and the DB configuration contains stale references to the obsolete names. If you do not do this, you will see all sorts of bizarre and mysterious errors.

        1.1.1) Stop the backend using the Alt-2 hot key from the GUI.
        1.1.2) Run mythtv-setup using Alt-S from the GUI.
        1.1.3) Select "2. Capture cards" and clear all of your capture card settings by choosing the option to "(Delete all capture cards)" there.
        1.1.4) Still under "2. Capture cards" recreate the entries for all your cards using the "(New capture card)" option there.
        1.1.5) Back on the main mythtv-setup menu select "4. Input connections" and reestablish the correct mappings from capture card input to video source there.
        1.1.6) Exit mythtv-setup.
        1.1.7) Restart the backend using Alt-3 from the GUI
      The directions for GettingBackIntoMytTVsetup and the configuration walk through on the BlackScreenWatchingTV troubleshooting page on the wiki may also be helpful when redoing this
      configuration.

      1.2) If you are getting errors/warnings when you try to exit mythtv-setup along the lines of "Card 0 (type) is set to start on channel 2, which does not exist.", you may need to manually delete the offending rows in the cardinput table. These are generally rows with the cardid = 0. If the following commands show a cardid (especially 0) in the cardinput table which is not listed in the capturecard table you should remove all references to it:
      Code:
      root@black2:~# mysql mythconverg -e "select cardid, videodevice, defaultinput from capturecard"
      +--------+-------------+--------------+
      | cardid | videodevice | defaultinput |
      +--------+-------------+--------------+
      |      1 | /dev/video0 | Tuner 1      |
      |      2 | /dev/video1 | Tuner 1      |
      +--------+-------------+--------------+
      root@black2:~# mysql mythconverg -e "select cardid, sourceid, inputname from cardinput"
      +--------+----------+-----------+
      | cardid | sourceid | inputname |
      +--------+----------+-----------+
      |      1 |        1 | Tuner 1   |
      |      2 |        1 | Tuner 1   |
      +--------+----------+-----------+

      As far as I can tell, valid cardid and sourceid values now start from 1 rather than 0. To remove the offending records:
      Code:
      mysql mythconverg -e "delete from cardinput where cardid=0"


      1.3) You may also need to update your ivtv module options to work with the new drivers. The KM upgrade scripts try to fix the most common obsolete options, but there are just too many possible options and too many places people can hide them to get everything. Remember you need to reboot for these changes to take effect! See this sticky thread for more details - IvyTV not working with new releases

      1.4) Just to be on the safe side, shutdown and power off your machine (unplug it if necessary to make sure it's really off) for 1-2 minutes to make sure that the old firmware is cleared and the new firmware will be uploaded to the card.

    2) Redo any add ons or extra configuration that you noted earlier. (Check first to make sure that it hasn't already been added as a new standard feature.) For example:

      2.1) Restoring your NFS setup (If you have a .bz2 for your backup file rather than .gz use jxvf instead of zxvf in the tar command below.):
      Code:
      mv /etc/exports /etc/exports.orig
      cd /
      tar zxvf /myth/backup/savedfiles.tar.gz ./etc/exports
      /etc/init.d/nfs-common restart
      /etc/init.d/nfs-kernel-server restart
      update-rc.d nfs-common defaults
      update-rc.d nfs-kernel-server defaults


      2.2) Restoring your webmin setup. This assumes that your LAN is using the 192.168.1.0/255.255.255.0 private network IP range. If you are using a different range (e.g. 192.168.0.0/255.255.255.0) correct the "allow" line below accordingly.
      Code:
      echo "allow=127.0.0.1 192.168.1.0" >>/etc/webmin/miniserv.conf
      /usr/share/webmin/changepass.pl /etc/webmin root YOURPASSWORDHERE
      /etc/init.d/webmin restart
      update-rc.d webmin defaults

      This may not work until you reboot.

      2.3) Restoring your lirc setup. To recover any LIRC customizations you've made from your backup:

        2.3.1) You must have run the lirc-reconfig.sh script during the Phase 2b setup. If you skipped it or don't remember, run it now and choose the appropriate settings.

        2.3.2) Due to the udev and other changes noted above, restoring your old /etc/lirc/hardware.conf is not recommended. If you do, you must make sure that the DEVICE and MODULES settings are correct.

        2.3.3) Restore your old files from the backup, make any device name corrections needed, and reboot. (If you have a .bz2 for your backup file rather than .gz use jxvf instead of zxvf in the tar command below.):
        Code:
        mv /etc/lirc/lircd.conf /etc/lirc/lircd.conf.orig
        mv /home/mythtv/.mythtv/lircrc /home/mythtv/.mythtv/lircrc.orig
        cd /
        tar zxvf /myth/backup/savedfiles.tar.gz ./etc/lirc/lircd.conf ./home/mythtv/.mythtv/lircrc
        reboot


        2.3.4) This post contains details about tweaking your lirc configuration: Understanding LIRC configuration

    3) Be very careful about doing apt-get install to add extra packages, even though the /etc/apt/sources.list is pointing to the stable repository. Do not attempt to do an apt-get upgrade or an apt-get dist-upgrade, this is almost guaranteed to roach your system. When using apt-get:

      3.1) Don't ever use the -y option.

      3.2) Always review the list of packages it wants to add or remove.

      3.3) If in doubt say "no".

    4) Optimizing your DB. See this post for a script which can be used to reduce your DB latency: A DB performace utility - optimize_db.sh

OBTW - As Cecil said in the R5D1 thread:
cesman wrote:
Let's not turn this into my upgrade didn't work thread.

Please. The hints threads are supposed to be a central reference to solutions worked out elsewhere. That way when we refer people to them they can actually find the information they need instead of wading through 12 pages of random and irrelevant postings. In pursuit of that goal, I will not answer questions in this thread which do not involved an update/correction/clarification/additional information/... on the upgrade hints posting, and would request that others do the same. On the other hand, if I've botched something above and you have a correction or clarification, don't be shy!

Before posting questions please search the forums and see the TroubleShooting pages on the wiki to make sure it's not a greater or lesser FAQ.

Many thanks to the testers and all other the folks who've worked through the early installs and upgrades to provide the solutions listed here. ;-)


Last edited by tjc on Tue Feb 05, 2008 7:41 pm, edited 25 times in total.


Top
 Profile  
 
PostPosted: Wed Sep 12, 2007 12:51 am 
Offline
Joined: Sat Mar 18, 2006 3:21 pm
Posts: 70
Location: West Fargo, ND
Quote:
5) IVTV driver changes:

    5.1) R5F27 uses version 1.1.0 of the ivtv driver, which would not normally be compatible with the 2.6.18 kernel being used, however, Cecil has built using the whole modern suite of modern v4l2 drivers and utilities. Due to interface differences between the 1.x.x and the 0.10.x branches you cannot mix and match, as a result, attempting an "upgrading" to the latest 0.10.x driver will break your system.

A link to where he mentions this would be nice.

Quote:
6.4) When setting up mysql for a MBE/SBE/FE multi-machine configuration (LinHES), the /etc/mysql/my.cnf file no longer contains a 'skip-networking' line to comment out. Instead, you can either comment out the bind-address line or change it to your machines primary IP address (this requires static IP address assignments). If you have multiple active network interfaces, change the IP address to that of the NIC facing your other machines.

Actually you can set bind-address = 0.0.0.0 to listen on all interfaces.

Quote:
6) The udev hardware detection can result in unstable device name assignments. The biggest problems people typically have with this is in systems with multiple different capture cards. Search for the writeup that bruce_s01 did on pinning down the device assignments. I don't think we've had a report of this problem in quite a while.

Link please?

Quote:
2.2) Restoring your webmin setup. This assumes that your LAN is using the 192.168.1.0/255.255.255.0 private network IP range. If you are using a different range (e.g. 192.168.0.0/255.255.255.0) correct the "allow" line below accordingly.
Code:
echo "allow=127.0.0.1 192.168.1.0" >>/etc/webmin/miniserv.conf
/usr/share/webmin/changepass.pl /etc/webmin root YOURPASSWORDHERE
/etc/init.d/webmin start

update-rc.d webmin defaults

This may not work until you reboot.

I think that a
Code:
/etc/init.d/webmin stop
before that
Code:
/etc/init.d/webmin start
would mitigate the need for a reboot.

Quote:
3) Be very careful about doing apt-get install to add extra packages, even though the /etc/apt/sources.list is pointing to the stable repository.

Is etch the current stable? I've been out of the Debian loop for awhile.

Quote:
3.2) Always review the list of packages it wants to add or remove.

REALLY good advice. This will area should save you tons of time on reinstalls.
I've always considered using
Code:
apt-get -d install
a fairly safe bet.


Top
 Profile  
 
PostPosted: Wed Sep 12, 2007 5:35 pm 
Offline
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location: Arlington, MA
ayourk wrote:
Quote:
Cecil has built using ...

A link to where he mentions this would be nice.

You'll just have to take my word for it as a matter of "insider knowledge". While the discussions exist they are not publicly available.
ayourk wrote:
Quote:
Search for the writeup that bruce_s01 did

Link please?

Searching for "udev" with bruce_s01 as the author turns up a grand total of 5 threads:
http://mysettopbox.tv/phpBB2/viewtopic.php?t=16189
http://mysettopbox.tv/phpBB2/viewtopic.php?t=13882 ***
http://mysettopbox.tv/phpBB2/viewtopic.php?t=13824
http://mysettopbox.tv/phpBB2/viewtopic.php?t=13520 ***
http://mysettopbox.tv/phpBB2/viewtopic.php?t=13294
The two key threads are the ones marked with stars, the other three all link to one or both of the others.

ayourk wrote:
Quote:
Code:
/etc/init.d/webmin start
...
This may not work until you reboot.

I think that a
Code:
/etc/init.d/webmin stop
before that
Code:
/etc/init.d/webmin start
would mitigate the need for a reboot.

While I'm normally a big advocate of using "restart", webmin is not running by default on a vanilla install, it has an odd init script which produces a disconcerting warning message if you stop when it's not running that I really didn't want to explain, and due to convoluted dependencies even if you stop and start it, it generally doesn't work until you reboot. This is often the case with complex dependency chains. The lircd stack is another great example of this, while I could explain the exact sequence of stop these applications, stop these daemons, unload this module, load that module, restart these daemons, restart these applications, ... Sometimes it's faster and easier all around to just say "reboot".


Top
 Profile  
 
PostPosted: Wed Sep 12, 2007 6:47 pm 
Offline
Joined: Sat Mar 18, 2006 3:21 pm
Posts: 70
Location: West Fargo, ND
There seems to be some XMLTV issues that are not yet covered here, but are covered here.


Top
 Profile  
 
 Post subject:
PostPosted: Wed Sep 12, 2007 7:24 pm 
Offline
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location: Arlington, MA
We've got a separate list for stuff which the patcher will fix.

See this post by human for details: http://mysettopbox.tv/phpBB2/viewtopic.php?t=16709


Last edited by tjc on Sun Sep 30, 2007 9:23 am, edited 1 time in total.


Top
 Profile  
 
 Post subject:
PostPosted: Wed Sep 12, 2007 11:29 pm 
Offline
Joined: Tue Jan 18, 2005 2:07 am
Posts: 1530
Location: California
FYI -- The names of the IVTV options that control buffer sizes have changed. If you previously had an options statement that looked something like this:
Code:
options ivtv yuv_buffers=8 mpg_buffers=32 vbi_buffers=8 pcm_buffers=8

you should change it to this:
Code:
options enc_yuv_buffers=8 enc_mpg_buffers=32 enc_vbi_buffers=8 enc_pcm_buffers=8


Last edited by marc.aronson on Thu Sep 13, 2007 11:18 pm, edited 1 time in total.


Top
 Profile  
 
 Post subject:
PostPosted: Wed Sep 12, 2007 11:39 pm 
Offline
Joined: Fri Jul 29, 2005 1:22 am
Posts: 232
Location: SF East Bay, CA
These installation/upgrade hints & tips are terrific! I have two suggests to help guide the newbies ...

Since I don't get into the box that often (last time I started an installation was Aug 16, 2006) .. it would really help if there was a list of installation scripts .. so you could go back an re-install a piece that didn't go right.

A little over a week ago, I started my upgrade to R5F1 .. and wouldn't you know it.. I answered the very first question wrong! (DHCP Broadcast? yes/no) because I keep forgetting that, if I really want a static IP address, then I want to answer "no". There may not be a script for network configuration.. I haven't found one! (I've got this down manually pretty good.)

In another case, the installation process tells me about a restart script.. and before I get pen in hand.. it's gone! .. so a list outside the box would be real nice. (I think that was the "which remote are you using".. which I also "guessed" wrong.. then searched all over to find the script.

I did catch "run config_bootsplash.sh to configure the bootsplash .. just as soon as I can figure out what it is and if I need it!

It would also be nice if there was some kind of indication if you should be in as "root" or as "mythtv" to make configuration changes. some are "obvious" while some are not. Why leave it to chance? (Trust me.. I'll get it wrong!)

Again, you guys do a fabulous job! Thank you! Thank you! Thank you!

_________________
// Brian - Hardware:
ASUS P5P800 - P4 3Ghz, 500 GB PATA HD
ASUS P5K-V - P4 Core2 Duo, 500 GB SATA HD
Hauppauge PVR-350, IR Blaster, Comcast Digital Cable
http://tech.groups.yahoo.com/group/KnoppMyth/
KnoppMyth R5F27 >> R5.5


Top
 Profile  
 
 Post subject:
PostPosted: Thu Sep 13, 2007 12:18 am 
Offline
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location: Arlington, MA
BluesBrian wrote:
it would really help if there was a list of installation scripts .. so you could go back an re-install a piece that didn't go right.

See /usr/local/bin where almost all of these things live.
Code:
ls -al /usr/local/bin/ | more

Most of the scripts have fairly obvious names.
BluesBrian wrote:
There may not be a script for network configuration.. I haven't found one!

This an FAQ with a widely publicized answer.
Code:
netcardconfig --force

There's just too much ground to cover for the hints to repeat every single configuration thing you might need to do to the machine.

BluesBrian wrote:
which remote are you using".. which I also "guessed" wrong.. then searched all over to find the script.

Another FAQ, and both the wiki and the threads that the hint refer you to for details cover using:
Code:
lirc-reconfig.sh

BluesBrian wrote:
It would also be nice if there was some kind of indication if you should be in as "root" or as "mythtv" to make configuration changes.

All of the actions in the hint should be run as root and it's restated regularly. Maybe adding a screaming blue banner to that effect will help..


Top
 Profile  
 
 Post subject:
PostPosted: Thu Sep 13, 2007 7:31 am 
Offline
Joined: Mon Jan 30, 2006 1:18 pm
Posts: 86
Location: Dayton, Ohio
tjc wrote:
BluesBrian wrote:
It would also be nice if there was some kind of indication if you should be in as "root" or as "mythtv" to make configuration changes.

All of the actions in the hint should be run as root and it's restated regularly. Maybe adding a screaming blue banner to that effect will help..


Is it possible, as it is/was in DOS, to set the command prompt to display the user (e.g. C:\windows [root]: )? The old way in DOS used ANSI commands, from what I remember (such as prompt $p$g to display user and directory). If it is indeed possible, I'd find that helpful to me as well...


Top
 Profile  
 
 Post subject:
PostPosted: Thu Sep 13, 2007 7:54 am 
Offline
Joined: Wed Nov 16, 2005 8:55 pm
Posts: 1381
Location: Farmington, MI USA
Harbinger wrote:
tjc wrote:
BluesBrian wrote:
It would also be nice if there was some kind of indication if you should be in as "root" or as "mythtv" to make configuration changes.

All of the actions in the hint should be run as root and it's restated regularly. Maybe adding a screaming blue banner to that effect will help..


Is it possible, as it is/was in DOS, to set the command prompt to display the user (e.g. C:\windows [root]: )? The old way in DOS used ANSI commands, from what I remember (such as prompt $p$g to display user and directory). If it is indeed possible, I'd find that helpful to me as well...
Unless you changed it on your system, the prompt already includes the user (and root's prompt ends with a pound sign (#)):
myth7@myth7:~$ --> "regular" user
root@myth7:~# --> root


Top
 Profile  
 
 Post subject:
PostPosted: Thu Sep 13, 2007 8:35 am 
Offline
Joined: Fri Jul 29, 2005 1:22 am
Posts: 232
Location: SF East Bay, CA
slowtolearn wrote:
Harbinger wrote:
tjc wrote:
BluesBrian wrote:
It would also be nice if there was some kind of indication if you should be in as "root" or as "mythtv" to make configuration changes.

All of the actions in the hint should be run as root and it's restated regularly. Maybe adding a screaming blue banner to that effect will help..


Is it possible, as it is/was in DOS, to set the command prompt to display the user (e.g. C:\windows [root]: )? The old way in DOS used ANSI commands, from what I remember (such as prompt $p$g to display user and directory). If it is indeed possible, I'd find that helpful to me as well...
Unless you changed it on your system, the prompt already includes the user (and root's prompt ends with a pound sign (#)):
myth7@myth7:~$ --> "regular" user
root@myth7:~# --> root

Good suggestions, but slightly off the point.. and actually "whoami" and "pwd" (Where am I?) are commonly typed in commands. My suggestion was more to the point of "who should I be?" but we could also add "where should I be?" .. when running a script. For some users, "screaming blue banner" might be useful .. I'll have to remember to plug in my speakers for the next upgrade/installation! .. I will, after all, be qualified to participate in IHOP's "senior day" promotion, next year.

Sadly, in Linux land,
Quote:
ls -al /usr/local/bin/ | more
is often passed off as user documentation.


Top
 Profile  
 
 Post subject:
PostPosted: Thu Sep 13, 2007 10:28 am 
Offline
Joined: Wed Nov 16, 2005 8:55 pm
Posts: 1381
Location: Farmington, MI USA
BluesBrian wrote:
slowtolearn wrote:
Harbinger wrote:
tjc wrote:
BluesBrian wrote:
It would also be nice if there was some kind of indication if you should be in as "root" or as "mythtv" to make configuration changes.

All of the actions in the hint should be run as root and it's restated regularly. Maybe adding a screaming blue banner to that effect will help..


Is it possible, as it is/was in DOS, to set the command prompt to display the user (e.g. C:\windows [root]: )? The old way in DOS used ANSI commands, from what I remember (such as prompt $p$g to display user and directory). If it is indeed possible, I'd find that helpful to me as well...
Unless you changed it on your system, the prompt already includes the user (and root's prompt ends with a pound sign (#)):
myth7@myth7:~$ --> "regular" user
root@myth7:~# --> root

Good suggestions, but slightly off the point..
Perfectly on point for Harbinger's question...


Top
 Profile  
 
 Post subject:
PostPosted: Thu Sep 13, 2007 11:24 am 
Offline
Joined: Fri Jul 29, 2005 1:22 am
Posts: 232
Location: SF East Bay, CA
slowtolearn wrote:
Perfectly on point for Harbinger's question...

.. and the reason that I added the
Quote:
(Who am I?) "whoami" and (Where am I?) "pwd" commands


Top
 Profile  
 
 Post subject:
PostPosted: Thu Sep 13, 2007 11:24 am 
Offline
Joined: Thu Sep 30, 2004 11:29 am
Posts: 2419
Location: Mechanicsburg, PA
BluesBrian, the types of things you talked about will likely be addressed in an upcoming redesign, so don't give up hope :)

_________________
KnoppMyth R5.5
MythiC Dragon v2.0
Join the KnoppMyth Frappr!


Top
 Profile  
 
 Post subject:
PostPosted: Thu Sep 13, 2007 1:18 pm 
Offline
Joined: Wed Oct 12, 2005 7:54 am
Posts: 88
Human wrote:
BluesBrian, the types of things you talked about will likely be addressed in an upcoming redesign, so don't give up hope :)


Redesign of what? This guide or KM?


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 53 posts ] 
Go to page 1, 2, 3, 4  Next



All times are UTC - 6 hours




Who is online

Users browsing this forum: No registered users and 2 guests


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 post attachments in this forum

Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu