Informations and Installation Instructions for MiniDVBLinux 1.0.x ================================================================= I. Structure ----------- The MiniDVBLinux is based on the Busybox and the 2.6.x Kernel from the gentoo Distribution and has a modular structure. That means it is possible to change the configuration and implement new drivers, funtions, etc. without reconfiguration of main image. Files description: Systems files Image.gz - image of the root file system. root=/dev/ram vmlinuz - kernel vmlinuz.config - kernel configuration file addons - folder for the additional DVBLinux modules linild.com - linux loader Configurations files etc - folder for configurations files etc\rc.config - main configuration file. linux.bat - startup file to load the MiniDVBLinux linux.set - startup configuration file explanation of the variables in the configuration files (linux.set) vga - Framebuffer video mode (read Framebuffer-HOTO) sys_dir - path to DVBLinux files. Default is /mnt/hda5/vdr (VDR folder on Drive D:) conf_dir - path to folder with DVBLinux configurations files. Default is /mnt/hda5/vdr/etc logs - Logging. Logs=1 loging on. Logs=0 logging off. apm - Kernel support for Advanced Power Manadement. Default ist off acpi - Kernel support for Advanced Configuration and Power Interface. Default ist off II. Installation ---------------- 1. Connect TV-out of DVB-s card to your TV. 2. boot computer from CD (You can use a modified rc.config. Copy it to floppy and insert this floppy during linux boot) 3. try out and enjoy MiniDVBLinux or, 4. follow the instructions on your TV and install the VDR alternative (HD Version) 1. Connect TV-out of DVB-s card to yours TV. 2. Start computer in DOS mode. 3. Unzip files to drive C: (or wherever you wish, just change the configuration files accordingly) 4. Edit file linux.set. Params sys_dir and conf_dir must point to folders with DVBLinux system and configurations files. 5. edit rc.config 6. start linux.bat remarks to the changes of the configuration files: the linux.bat, linux.set, rc.config or the lilo.conf have to be adapted to the partitioning of your harddisk. Therefore here are some remarks for linuxnewbies. With linux there are no driveletters as with DOS or windows. The different partitions are labeld as a path in the following order: MASTER SLAVE IDE PRIMARY /dev/hda /dev/hdb IDE SECONDARY /dev/hdc /dev/hdd Now lets assume the first harddisk ist connected to the 1. IDE channel wich would be standard in most computers. /dev/hda1 first primary partition /dev/hda2 second primary partition /dev/hda3 third primary partition /dev/hda4 fourth primary/or extended partition /dev/hda5 first logical drive in the extended partition So for users of an Activy with pre-installed Win98 embedded or the Datacargo GUI you have to take the following into account: Usually an Activy is partitioned in the following manner. The harddisk is connected to the first IDE channel as a master drive. That means this drive would be labled /dev/hda1 in a linux environment. The first primary partition is of about 500 MB size, formatted with FAT and set to "hidden". This is the place where the image of the operrating system (windows98 SE embedded) resides, which is needed for the eventual recovery process. The second primary partition is of about 200 MB size, formatted with FAT and is labled "prog". This drive is used for booting and is the drive c:\. The windows OS and all installed applications are located there. This drive would be labled /dev/hda2 in linux. The next partition would be drive d:\. Here is the rest of the Activy Harddisk space located and this partition is labled "data". Because this is the first logival drive in an extended partition, this partition is defined as /dev/hda5 and NOT as /dev/hda3 in linux! If you want to see all this graphicly, just take a look at your harddrive partition magic. So please change the linux.bat and the linux.set according to your specific partitioning of your harddrive. Otherwise VDR would use c:\ where there are only 2GB FAT available. Not very much for some recording....All other parameters in the configuration files are hopefully pretty obvious.. III. Description of the boot process ----------------------------------- 1. when booting from DOS: change to the VDR folder and start the linux.bat this batch file calls the linld.com wich loads the linux kernel. 2. the kernel is loaded and the root filesystem (root.img.gz) is decompressed and mounted to /dev/ram. 3. init starts the bootscript /etc/init.d/rc.sysinit. 4. rc.sysinit mounts the drive with VDR (vdr_dev) to /mnt/system. 5. rc.sysinit copys the file rc.config to /etc/rc.config and executes it. If you boot from CD, rc.sysinit trys to copy rc.config from /dev/fd0 (floppy). 6. rc.sysinit creates the temporary file temp.img (Size of this file TMP_DRV_SIZE in rc.config), creates a minix file system on it and mounts it to /usr. 7. rc.sysinit installs all modules/addons (the order is according to the alphabet) in the following manner: - decompresses the first addon and starts the installtion script /tmp/install - delets /tmp/* - decompresses the second addon and starts the installtion script /tmp/install - delets /tmp/* - and so forth....... 8. rc.sysinit starts the VDR (EXEC_CMD in rc.config) the video drive /VD_DEV in rc.config) is mounted by the VDR addon. The VDR addon also links the video folder (VD_PTH in rc.config) to /mnt/video. If VD_DEV is not defined, VD_DEV will be set to vdr_dev. IV. Networkconfiguration ------------------------ 1. If you use an Activy, then use the file 01DVBLinux-X.X.X_activy-x.tgz If you use a regular computer, then use the file 01DVBLinux-X.X.X_landrv-x.tgz 2. To change network driver, you must change the parameter NET_DRV in the rc.config file. Example: NET_DRV="ne irq=0x5 port=0x300" 3. IP adress Configuration IP_ADR - IP adress NET_MASK - Subnet Mask DEF_GW - Default gateway DNS_SRV - DNS Server Example: IP_ADR=192.168.1.2 NET_MASK=255.255.255.0 DEF_GW=192.168.1.1 DNS_SRV=192.168.1.1 V. Module/addons ---------------- 1. DVBLinux install all (*.tgz) modules from the ADDONS folder automaticly. Delete or save to another place all not used addons from this folder. It should be taken care that all modules wich contain VDR plugins, match the appropiate VDR version. 2. You can change boot sequens of ADDONS if you rename it. 3. Some addons are kernel or hardware depended (030DVBLinux-X.X.X_activy.tgz, 030DVBLinux-X.X.X_landrv.tgz, etc) 4. 030DVBLinux-X.X.X_activy.tgz contains the Activy RemoteControl configuration script and LAN Driver and Network config. If you are using a regular PC instead of an Activy you must delete this file! 6. If you want to specify additional parameters for vdr, edit VDR_CMD in rc.config Example: VDR_CMD="vdr -v /video1" 7. If you don't want to use the default smb.conf with 04DVBLinux-X.X.X_smbd.tgz addons, then copy another one to /video folder. 8. If you don't want use ACPI Power management, delete 06DVBLinux-X.X.X_acpid.tgz from ADDONS folder, and change in linux.set apm=off to apm=on. ______________________WWW.ACTIVY300.1XU.DE______________________ ______________________WWW.minidvblinix.org______________________ Thank to all contributors, whose programs are used in MiniDVBLinux Thanks to all people who helped with the MInilinux project Thanks to all boardmembers for searching bugs and the suggestions Egor: developer/maintainer of the MiniDVBLinux claus: co-work on DVBLinux and developer/maintainer of VDR addons Jerome: maintainer and webadmin of www.activy300.1xu.de