Next: , Previous: Introduction, Up: Top


2 Installation

2.1 Preparation

KSWv4lcmn package should be installed into your system ahead of this package installation.

Backup of /etc/* is highly recommended.

[Solaris 8 only] Confirm that shared memory segment is larger than 6.1MB. Example:

     % sysdef | grep SHMMAX
      33554432	max shared memory segment size (SHMMAX)

This example shows that system reserves 33554432 bytes (=32MB) for shared memory segment; that's enough size. If this size is smaller than limit, edit or add line to /etc/system like this:

     set shmsys:shminfo_shmmax=0x2000000

See System V Shared Memory in the "Solaris Tunable Parameters Reference Manual" at http://docs.sun.com.

2.2 Hardware Installation

Shutdown machine and plug capture card into vacant PCI slot of workstation/PC. 32bit slot and 33MHz PCI clock is preferred (Bt8x8 works on 33MHz/32-bit bus). Beware not to skewed or shallowly plugged. Connect audio cable and antenna cable.

After boot up, verify device recognition of kernel. Run /opt/KSWv4lcmn/sbin/report-v4l script to do it.

Example (Sun Blade 100):

     % /opt/KSWv4lcmn/sbin/report-v4l
     Solaris release... 5.9
     Machine architecture... sun4u
     Hardware architecture... SUNW,Sun-Blade-100
     Searching device node for Bt8x8...
       video                  109e 0350    -    -
     Searching aliases for bt848x driver...
     Searching major device number for bt848x...
     Searching for installed instances of bt848x node...
     Searching naming rules of special files for bt848x...
     Searching for kernel module for bt848x...
     Searching device node for SAA713x...
     Searching aliases for saa713x driver...
     Searching major device number for saa713x...
     Searching for installed instances of saa713x node...
     Searching naming rules of special files for saa713x...
     Searching for kernel module for saa713x...
     Searching special files...
     %

Look for result of “Searching device node for Bt8x8”. it shows one device node instance named “video” with PCI vendor ID 0x109e and PCI device ID 0x0350. (Following two hyphens mean “no PCI subsystem ID and no PCI subsystem device ID”, they are not so impotant in this stage)

On x86 system, you will find device named “pcixxxx,yyyy” where xxxx is PCI (subsystem) vendor and PCI device (PCI subsystem) ID.

2.3 Package Installation

There are two ways for package installation: using distributed package file, or creating user's private package file from source code.

2.3.1 Installation by distirbuted package file

Our project distribute package files at download site at http://sourceforge.net. Third parties may distribute original or modified package files.

Package file has .pkg.gz or .pkg suffix, say KSWxxx.pkg.gz for example, gain root priviledge and install it as follows:

     # gzip -d KSWxxx.pkg.gz
     # pkgadd -d KSWxxx.pkg all

2.3.2 Installation using source code

You can create your own package file and install it. Source code is distributed as tar.gz file normarlly.

     % gzip -dc xxx.tar.gz | tar xf -
     % cd xxx-x.y.z
     % sh configure.sh
     % make
     % make package
     % ls */pkg-*/*.pkg
     # pkgadd -d xxx/pkg-xxx/xxx.pkg

configure.sh script can accept several options. Run sh configure.sh --help for details.

2.3.3 Verification of Driver Installation

At this stage, driver should work with default operationg paramter. Run /opt/KSWv4lcmn/sbin/report-v4l script again.

Example:

     % /opt/KSWv4lcmn/sbin/report-v4l
     Solaris release... 5.9
     Machine architecture... sun4u
     Hardware architecture... SUNW,Sun-Blade-100
     Searching device node for Bt8x8...
       video                  109e 0350    -    -
     Searching aliases for bt848x driver...
       bt848x "pci109e,36f"
       bt848x "pci109e,36e"
       bt848x "pci109e,351"
       bt848x "pci109e,350"
     Searching major device number for bt848x...
       bt848x 198
     Searching for installed instances of bt848x node...
       "/pci@1f,0/pci@5/video@2" 0 "bt848x"
     Searching naming rules of special files for bt848x...
     Searching for kernel module for bt848x...
       219 780ba000  20683 198   1  bt848x (Bt8x8 video grabber )
     Searching device node for SAA713x...
     Searching aliases for saa713x driver...
     Searching major device number for saa713x...
     Searching for installed instances of saa713x node...
     Searching naming rules of special files for saa713x...
     Searching for kernel module for saa713x...
     Searching special files...
       256359    0 crw-rw-rw-   1 root     other    198,   0 Aug 31 18:22 /devices/pci@1f,0/pci@5/video@2:video
       1209906    1 lrwxrwxrwx   1 root     other          39 Aug 28 22:57 /dev/video0 -> ../devices/pci@1f,0/pci@5/video@2:video

Result of “Searching aliases for bt848x driver...” and “Searching major device number for bt848x...” show that driver is registered correctly to the system.

“Searching for installed instances of bt848x node...” and “Searching for kernel module for bt848x...” show that current kernel loads bt848x driver. If you don't use driver for a while, kernel will unload driver temporarily. This is normal behavior.

The files shown in the result of “Searching special files...” are device files for application.