QNAP NAS Community Forum

by **ybot** » Sat Oct 22, 2011 8:44 am

@chomp!
Firstly let me state that copying headers around in the build environment is wrong, I have just worked out you can pass these to configure and it should work correctly.

Try the following configure line (I'm in the process of updating this to the howto)

Code: Select all: ./configure -I /usr/local/mysql/include/mysql -L /usr/local/mysql/lib/mysql --opensource -confirm-license -release -prefix /opt/Qt-4.7.3 -reduce-relocations -qt-libtiff -qt-libpng -qt-libmng -sql-mysql-plugin -no-multimedia -nomake tools -nomake examples -nomake demos -nomake docs

by **ybot** » Sat Oct 22, 2011 8:57 am

@vinsanity

Thanks for the feedback. I am working on a ipkg for Qt currently (if anyone has a ipkg build environment setup please test qt-473.mk here http://pastebin.com/FErwmUd1). From there I will see how I can get MythTV in so it correctly depends on Qt and other ipkg packages. Then it will be testing these ipkgs. I will post my results.

by **ybot** » Sun Oct 23, 2011 11:56 am

I have an arm (cs08q1armel) version of the qt ipkg available, it's about 25MB. I'm currently working out ipkg tools '-check' issues something about qmake and rpath???

by **fergalom** » Fri Oct 28, 2011 12:14 am

ybot,

back again on the the mythtv and almost there.

Got my hauppage win nova-t usb stick the other day and trying to get the modules to load but not having much luck.
The following is how I am loading the modules which I copied from the relevant folders after "make modules"
I have tried insmod also with the same result from dmesg.

Code: Select all: depmod -a modprobe firmware_class modprobe dibx000_common modprobe dib3000mc modprobe dvb-core modprobe dvb-usb modprobe dvb-usb-dibusb-common modprobe dvb-usb-nova-t-usb2 modprobe mt2060 modprobe dvb-pll

Code: Select all: [/share/HDA_DATA/.qpkg/Optware/lib/modules/2.6.33.2/kernel/drivers/media/dvb/dvb-usb] # modprobe dvb-core [/share/HDA_DATA/.qpkg/Optware/lib/modules/2.6.33.2/kernel/drivers/media/dvb/dvb-usb] # modprobe dvb-usb FATAL: Error inserting dvb_usb (/opt/lib/modules/2.6.33.2/kernel/drivers/media/dvb/dvb-usb/dvb-usb.ko): Unknown symbol in module, or unknown parameter (see dmesg) [/share/HDA_DATA/.qpkg/Optware/lib/modules/2.6.33.2/kernel/drivers/media/dvb/dvb-usb] # dmesg er has exited, flushing export cache [47353.340000] dvb_usb: Unknown symbol i2c_del_adapter [47353.350000] dvb_usb: Unknown symbol i2c_add_adapter [47693.690000] dvb_pll: Unknown symbol i2c_transfer [47702.210000] dvb_usb: Unknown symbol i2c_del_adapter [47702.220000] dvb_usb: Unknown symbol i2c_add_adapter [47761.640000] dib0070: Unknown symbol i2c_transfer [47866.370000] i2c_core: Unknown symbol __i2c_board_list [47866.370000] i2c_core: Unknown symbol __i2c_first_dynamic_bus_num [47866.380000] i2c_core: Unknown symbol __i2c_board_lock [48313.550000] i2c_core: Unknown symbol __i2c_board_list [48313.560000] i2c_core: Unknown symbol __i2c_first_dynamic_bus_num [48313.560000] i2c_core: Unknown symbol __i2c_board_lock [48779.530000] i2c_core: Unknown symbol __i2c_board_list [48779.540000] i2c_core: Unknown symbol __i2c_first_dynamic_bus_num [48779.550000] i2c_core: Unknown symbol __i2c_board_lock [55826.760000] i2c_core: Unknown symbol __i2c_board_list [55826.770000] i2c_core: Unknown symbol __i2c_first_dynamic_bus_num [55826.780000] i2c_core: Unknown symbol __i2c_board_lock [55826.820000] dibx000_common: Unknown symbol i2c_del_adapter [55826.820000] dibx000_common: Unknown symbol i2c_add_adapter [55826.830000] dibx000_common: Unknown symbol i2c_transfer [55838.820000] i2c_core: Unknown symbol __i2c_board_list [55838.830000] i2c_core: Unknown symbol __i2c_first_dynamic_bus_num [55838.840000] i2c_core: Unknown symbol __i2c_board_lock [55838.880000] dibx000_common: Unknown symbol i2c_del_adapter [55838.880000] dibx000_common: Unknown symbol i2c_add_adapter [55838.890000] dibx000_common: Unknown symbol i2c_transfer [55838.910000] dib3000mc: Unknown symbol dibx000_init_i2c_master [55838.910000] dib3000mc: Unknown symbol dibx000_get_i2c_adapter [55838.920000] dib3000mc: Unknown symbol dibx000_exit_i2c_master [55838.930000] dib3000mc: Unknown symbol i2c_transfer [55852.370000] i2c_core: Unknown symbol __i2c_board_list [55852.380000] i2c_core: Unknown symbol __i2c_first_dynamic_bus_num [55852.390000] i2c_core: Unknown symbol __i2c_board_lock [55852.430000] dvb_usb: Unknown symbol i2c_del_adapter [55852.440000] dvb_usb: Unknown symbol i2c_add_adapter [55859.710000] i2c_core: Unknown symbol __i2c_board_list [55859.710000] i2c_core: Unknown symbol __i2c_first_dynamic_bus_num [55859.720000] i2c_core: Unknown symbol __i2c_board_lock [55859.760000] dibx000_common: Unknown symbol i2c_del_adapter [55859.760000] dibx000_common: Unknown symbol i2c_add_adapter [55859.770000] dibx000_common: Unknown symbol i2c_transfer [55859.800000] dib3000mc: Unknown symbol dibx000_init_i2c_master [55859.800000] dib3000mc: Unknown symbol dibx000_get_i2c_adapter [55859.810000] dib3000mc: Unknown symbol dibx000_exit_i2c_master [55859.820000] dib3000mc: Unknown symbol i2c_transfer [55859.850000] mt2060: Unknown symbol i2c_transfer [55859.850000] dvb_pll: Unknown symbol i2c_transfer [55859.870000] dvb_usb: Unknown symbol i2c_del_adapter [55859.880000] dvb_usb: Unknown symbol i2c_add_adapter [55859.910000] dvb_usb_dibusb_common: Unknown symbol dvb_usb_nec_rc_key_to_event [55859.920000] dvb_usb_dibusb_common: Unknown symbol dvb_usb_generic_rw [55859.920000] dvb_usb_dibusb_common: Unknown symbol dvb_pll_attach [55859.930000] dvb_usb_dibusb_common: Unknown symbol mt2060_attach [55859.930000] dvb_usb_dibusb_common: Unknown symbol dib3000mc_attach [55859.940000] dvb_usb_dibusb_common: Unknown symbol dib3000mc_set_config [55859.950000] dvb_usb_dibusb_common: Unknown symbol dib3000mc_get_tuner_i2c_master [55859.960000] dvb_usb_dibusb_common: Unknown symbol dib3000mc_pid_control [55859.960000] dvb_usb_dibusb_common: Unknown symbol dvb_usb_generic_write [55859.970000] dvb_usb_dibusb_common: Unknown symbol dib3000mc_pid_parse [55866.670000] i2c_core: Unknown symbol __i2c_board_list [55866.680000] i2c_core: Unknown symbol __i2c_first_dynamic_bus_num [55866.690000] i2c_core: Unknown symbol __i2c_board_lock [55866.730000] dvb_usb: Unknown symbol i2c_del_adapter [55866.740000] dvb_usb: Unknown symbol i2c_add_adapter [55866.770000] dibx000_common: Unknown symbol i2c_del_adapter [55866.770000] dibx000_common: Unknown symbol i2c_add_adapter [55866.780000] dibx000_common: Unknown symbol i2c_transfer [55866.800000] dib3000mc: Unknown symbol dibx000_init_i2c_master [55866.800000] dib3000mc: Unknown symbol dibx000_get_i2c_adapter [55866.810000] dib3000mc: Unknown symbol dibx000_exit_i2c_master [55866.820000] dib3000mc: Unknown symbol i2c_transfer [55866.850000] mt2060: Unknown symbol i2c_transfer [55866.850000] dvb_pll: Unknown symbol i2c_transfer [55866.870000] dvb_usb_dibusb_common: Unknown symbol dvb_usb_nec_rc_key_to_event [55866.870000] dvb_usb_dibusb_common: Unknown symbol dvb_usb_generic_rw [55866.880000] dvb_usb_dibusb_common: Unknown symbol dvb_pll_attach [55866.890000] dvb_usb_dibusb_common: Unknown symbol mt2060_attach [55866.890000] dvb_usb_dibusb_common: Unknown symbol dib3000mc_attach [55866.900000] dvb_usb_dibusb_common: Unknown symbol dib3000mc_set_config [55866.910000] dvb_usb_dibusb_common: Unknown symbol dib3000mc_get_tuner_i2c_master [55866.920000] dvb_usb_dibusb_common: Unknown symbol dib3000mc_pid_control [55866.920000] dvb_usb_dibusb_common: Unknown symbol dvb_usb_generic_write [55866.930000] dvb_usb_dibusb_common: Unknown symbol dib3000mc_pid_parse [55867.020000] dvb_usb_nova_t_usb2: Unknown symbol dibusb_pid_filter_ctrl [55867.020000] dvb_usb_nova_t_usb2: Unknown symbol dibusb_i2c_algo [55867.030000] dvb_usb_nova_t_usb2: Unknown symbol dibusb2_0_streaming_ctrl [55867.040000] dvb_usb_nova_t_usb2: Unknown symbol dibusb_dib3000mc_tuner_attach [55867.050000] dvb_usb_nova_t_usb2: Unknown symbol dvb_usb_generic_rw [55867.050000] dvb_usb_nova_t_usb2: Unknown symbol dibusb_dib3000mc_frontend_attach [55867.060000] dvb_usb_nova_t_usb2: Unknown symbol dibusb2_0_power_ctrl [55867.070000] dvb_usb_nova_t_usb2: Unknown symbol dibusb_pid_filter [55867.070000] dvb_usb_nova_t_usb2: Unknown symbol dvb_usb_device_init [55867.080000] dvb_usb_nova_t_usb2: Unknown symbol dvb_usb_device_exit [55867.090000] dvb_usb_nova_t_usb2: Unknown symbol dibusb_read_eeprom_byte [55877.230000] i2c_core: Unknown symbol __i2c_board_list [55877.230000] i2c_core: Unknown symbol __i2c_first_dynamic_bus_num [55877.240000] i2c_core: Unknown symbol __i2c_board_lock [55877.280000] mt2060: Unknown symbol i2c_transfer [56000.290000] i2c_core: Unknown symbol __i2c_board_list [56000.300000] i2c_core: Unknown symbol __i2c_first_dynamic_bus_num [56000.310000] i2c_core: Unknown symbol __i2c_board_lock [56000.350000] dvb_pll: Unknown symbol i2c_transfer [56116.180000] i2c_core: Unknown symbol __i2c_board_list [56116.190000] i2c_core: Unknown symbol __i2c_first_dynamic_bus_num [56116.200000] i2c_core: Unknown symbol __i2c_board_lock [59268.560000] i2c_core: Unknown symbol __i2c_board_list [59268.570000] i2c_core: Unknown symbol __i2c_first_dynamic_bus_num [59268.580000] i2c_core: Unknown symbol __i2c_board_lock [59268.620000] dvb_usb: Unknown symbol i2c_del_adapter [59268.630000] dvb_usb: Unknown symbol i2c_add_adapter [/share/HDA_DATA/.qpkg/Optware/lib/modules/2.6.33.2/kernel/drivers/media/dvb/dvb-usb] #

Perhaps you could outline how you loaded your modules for your tuner.

Thanks
F

by **ybot** » Fri Oct 28, 2011 12:36 pm

@fergalom

I think you are missing the i2c device module

Code: Select all: I2C support (I2C) [M/n/y/?] m

after 'make modules' should give you the module i2c-core.ko which is required to be loaded before the dvb-usb module (hence why you see the unknown symbol messages). You should find this module in 'linux-2.6.33.2/drivers/i2c'.

Good luck!

PS I also have the following startup script for when I reboot the system

http://wiki.qnap.com/wiki/Running_Your_ ... at_Startup

Code: Select all: [/share/HDA_DATA/.qpkg/autorun] # cat autorun.sh #!/bin/sh # additional lib path echo "/opt/lib" >> /etc/ld.so.conf ldconfig # create dvb devices /share/HDA_DATA/.qpkg/autorun/dvb-devices # set correct locale (remove incorrect) #localedef -f UTF-8 -i en_AU en_AU.utf8 #localedef --delete-from-archive en_US.utf8 # load kernel modules insmod /lib/modules/others/i2c-core.ko insmod /lib/modules/others/dvb-core.ko insmod /lib/modules/others/dvb-usb.ko insmod /lib/modules/others/dvb-usb-af903x.ko # start mythbackend #mythbackend &

by **fergalom** » Fri Oct 28, 2011 5:18 pm

Thanks for that, will try it now shortly.

Just very quickly, does this line /share/HDA_DATA/.qpkg/autorun/dvb-devices refer to a scipt dvb-devices?
The rest of the script I understand.
F

by **ybot** » Fri Oct 28, 2011 8:26 pm

@fergalom

Yep, it is another script in the same directory that creates the dvb devices (because the kernel boots without them, and I'm not quite sure of the correct way of providing them automatically through /dev instantiation).

Code: Select all: [/share/HDA_DATA/.qpkg/autorun] # cat dvb-devices #!/bin/bash function create_adapter() { local nr="$1" major="$2" minor="$3" mkdir /dev/dvb/adapter${nr} mknod /dev/dvb/adapter${nr}/video${nr} c $major $(( $minor )) mknod /dev/dvb/adapter${nr}/audio${nr} c $major $(( $minor +1 )) mknod /dev/dvb/adapter${nr}/frontend${nr} c $major $(( $minor +3 )) mknod /dev/dvb/adapter${nr}/demux${nr} c $major $(( $minor +4 )) mknod /dev/dvb/adapter${nr}/dvr${nr} c $major $(( $minor +5 )) mknod /dev/dvb/adapter${nr}/ca${nr} c $major $(( $minor +6 )) mknod /dev/dvb/adapter${nr}/net${nr} c $major $(( $minor +7 )) mknod /dev/dvb/adapter${nr}/osd${nr} c $major $(( $minor +8 )) } mkdir /dev/dvb create_adapter 0 212 0 create_adapter 1 212 64 create_adapter 2 212 128 create_adapter 3 212 192 chmod 755 /dev/dvb/adapter* chmod 660 /dev/dvb/adapter*/*

by **fergalom** » Fri Oct 28, 2011 11:17 pm

Hmmmm,

I've refollowed the guide to the letter for compiling modules but I cannot seem to insmod i2c-core.ko which does get created as the file modification date/time is current.

Code: Select all: [/share/Qdownload/mythlab/linux-2.6.33.2] # insmod /share/HDA_DATA/.qpkg/Optware/lib/modules/2.6.33.2/kernel/drivers/i2c/i2c-core.ko insmod: error inserting '/share/HDA_DATA/.qpkg/Optware/lib/modules/2.6.33.2/kernel/drivers/i2c/i2c-core.ko': -1 Unknown symbol in module [/share/Qdownload/mythlab/linux-2.6.33.2] # insmod drivers/i2c/i2c-core.ko insmod: error inserting 'drivers/i2c/i2c-core.ko': -1 Unknown symbol in module [/share/Qdownload/mythlab/linux-2.6.33.2] #

I'm using a TS-119 which maybe is a factor? Not sure, time for more googling.

F

by **ybot** » Fri Oct 28, 2011 11:58 pm

@fergalom

Hmm, that is annoying. Can you get anymore information regarding the missing symbol? what does dmesg say? If the referring functions are not required (logging/etc), you can just comment it out in the kernel module source and recompile (not really the best idea, but at least a plan f).

by **fergalom** » Sat Oct 29, 2011 12:11 am

dmesg output below. Afraid this is starting to get outside my very limited knowledge of linux

Code: Select all: [/share/Qdownload/mythlab/linux-2.6.33.2] # dmesg [ 32.750000] usbcore: registered new interface driver uvcvideo [ 32.750000] USB Video Class driver (v0.1.0) [ 35.210000] kjournald starting. Commit interval 5 seconds [ 35.220000] EXT3-fs (md9): using internal journal [ 35.220000] EXT3-fs (md9): mounted filesystem with writeback data mode [ 37.790000] active port 0 :139 [ 37.800000] active port 1 :445 [ 37.800000] active port 2 :20 [ 39.960000] EXT2-fs (mtdblock5): warning: mounting unchecked fs, running e2fsck is recommended [ 45.950000] md: bind<sda2> [ 45.960000] raid1: raid set md1 active with 1 out of 1 mirrors [ 45.970000] md1: detected capacity change from 0 to 542769152 [ 47.010000] md1: unknown partition table [ 47.520000] kjournald starting. Commit interval 5 seconds [ 47.530000] EXT3-fs (sda3): using internal journal [ 47.540000] EXT3-fs (sda3): mounted filesystem with ordered data mode [ 49.110000] Adding 530040k swap on /dev/md1. Priority:-1 extents:1 across:530040k [ 61.340000] eth0: stopped [ 68.950000] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory [ 68.960000] NFSD: starting 90-second grace period [ 71.950000] eth0: link down [ 71.950000] eth0: started [ 75.070000] eth0: link up, full duplex, speed 1 Gbps [ 90.950000] eth0: stopped [ 90.980000] eth0: link down [ 90.980000] eth0: started [ 94.110000] eth0: link up, full duplex, speed 1 Gbps [ 103.610000] nfsd: last server has exited, flushing export cache [ 109.660000] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory [ 109.670000] NFSD: starting 90-second grace period [ 113.490000] active port 0 :139 [ 113.500000] active port 1 :445 [ 113.500000] active port 2 :20 [ 120.230000] nfsd: last server has exited, flushing export cache [ 123.890000] EXT2-fs (mtdblock5): warning: mounting unchecked fs, running e2fsck is recommended [ 136.100000] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory [ 136.110000] NFSD: starting 90-second grace period [ 141.130000] TARGET_CORE[0]: Loading Generic Kernel Storage Engine: v3.5.0 on Linux/armv5tel on 2.6.33.2 [ 141.130000] TARGET_CORE[0]: Initialized ConfigFS Fabric Infrastructure: v3.5.0 on Linux/armv5tel on 2.6.33.2 [ 141.150000] SE_PC[0] - Registered Plugin Class: TRANSPORT [ 141.150000] PLUGIN_TRANSPORT[1] - pscsi registered [ 141.160000] PLUGIN_TRANSPORT[4] - iblock registered [ 141.160000] PLUGIN_TRANSPORT[5] - rd_dr registered [ 141.170000] PLUGIN_TRANSPORT[6] - rd_mcp registered [ 141.170000] PLUGIN_TRANSPORT[7] - fileio registered [ 141.170000] SE_PC[1] - Registered Plugin Class: OBJ [ 141.180000] PLUGIN_OBJ[1] - dev registered [ 141.180000] CORE_HBA[0] - Linux-iSCSI.org Ramdisk HBA Driver v3.1 on Generic Target Core Stack v3.5.0 [ 141.190000] CORE_HBA[0] - Attached Ramdisk HBA: 0 to Generic Target Core TCQ Depth: 256 MaxSectors: 1024 [ 141.200000] CORE_HBA[0] - Attached HBA to Generic Target Core [ 141.210000] RAMDISK: Referencing Page Count: 8 [ 141.210000] CORE_RD[0] - Built Ramdisk Device ID: 0 space of 8 pages in 1 tables [ 141.220000] rd_dr: Using SPC_PASSTHROUGH, no reservation emulation [ 141.230000] rd_dr: Using SPC_ALUA_PASSTHROUGH, no ALUA emulation [ 141.230000] CORE_RD[0] - Activating Device with TCQ: 0 at Ramdisk Device ID: 0 [ 141.320000] Vendor: QNAP Model: RAMDISK-DR Revision: 3.1 [ 141.320000] Type: Direct-Access ANSI SCSI revision: 05 [ 141.330000] T10 VPD Unit Serial Number: 1234567890:0_0 [ 141.350000] T10 VPD Page Length: 38 [ 141.350000] T10 VPD Identifer Length: 34 [ 141.350000] T10 VPD Identifier Association: addressed logical unit [ 141.360000] T10 VPD Identifier Type: T10 Vendor ID based [ 141.360000] T10 VPD ASCII Device Identifier: QNAP [ 141.380000] CORE_RD[0] - Added LIO DIRECT Ramdisk Device ID: 0 of 8 pages in 1 tables, 32768 total bytes [ 141.600000] Initiate iscsi target log successfully. [ 141.600000] Linux-iSCSI.org iSCSI Target Core Stack v3.5.0 on Linux/armv5tel on 2.6.33.2 [ 141.610000] <<<<<<<<<<<<<<<<<<<<<< BEGIN FABRIC API >>>>>>>>>>>>>>>>>>>>>> [ 141.620000] Initialized struct target_fabric_configfs: dec80c00 for iscsi [ 141.620000] <<<<<<<<<<<<<<<<<<<<<< END FABRIC API >>>>>>>>>>>>>>>>>>>>>> [ 141.630000] LIO_TARGET[0] - Set fabric -> lio_target_fabric_configfs [ 141.690000] iscsi_allocate_thread_sets:206: ***OPS*** Spawned 4 thread set(s) (8 total threads). [ 141.690000] TARGET_CORE[iSCSI]: Allocated Discovery se_portal_group_t for endpoint: None, Portal Tag: 1 [ 141.700000] CORE[0] - Allocated Discovery TPG [ 141.710000] Loading Complete. [ 141.770000] iscsi_log_rcv_msg: get log pid = 4101. [ 228.700000] usbcore: registered new interface driver usbserial [ 228.700000] usbserial: USB Serial Driver core [ 228.960000] USB Serial support registered for pl2303 [ 229.020000] usbcore: registered new interface driver pl2303 [ 229.030000] pl2303: Prolific PL2303 USB to serial adaptor driver [ 229.990000] nfsd: last server has exited, flushing export cache [ 241.740000] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory [ 241.750000] NFSD: starting 90-second grace period [ 246.440000] warning: process `pic_raw' used the deprecated sysctl system call with 8.1.2. [ 250.330000] Set Adpater:port=0:0 standby to 120 (600 secs). [ 250.650000] rule type=2, num=0 [ 252.300000] EXT2-fs (mtdblock5): warning: mounting unchecked fs, running e2fsck is recommended [ 266.440000] Loading iSCSI transport class v2.0-871. [ 267.500000] iscsi: registered transport (tcp) [ 269.920000] warning: `proftpd' uses 32-bit capabilities (legacy support in use) [ 1177.480000] i2c_core: Unknown symbol __i2c_board_list [ 1177.490000] i2c_core: Unknown symbol __i2c_first_dynamic_bus_num [ 1177.490000] i2c_core: Unknown symbol __i2c_board_lock [19223.360000] i2c_core: Unknown symbol __i2c_board_list [19223.370000] i2c_core: Unknown symbol __i2c_first_dynamic_bus_num [19223.380000] i2c_core: Unknown symbol __i2c_board_lock [19302.240000] i2c_core: Unknown symbol __i2c_board_list [19302.250000] i2c_core: Unknown symbol __i2c_first_dynamic_bus_num [19302.260000] i2c_core: Unknown symbol __i2c_board_lock [19504.280000] i2c_dev: Unknown symbol i2c_get_adapter [19504.290000] i2c_dev: Unknown symbol i2c_master_recv [19504.290000] i2c_dev: Unknown symbol i2c_smbus_xfer [19504.300000] i2c_dev: Unknown symbol i2c_register_driver [19504.300000] i2c_dev: Unknown symbol i2c_verify_client [19504.310000] i2c_dev: Unknown symbol i2c_put_adapter [19504.320000] i2c_dev: Unknown symbol i2c_transfer [19504.320000] i2c_dev: Unknown symbol i2c_del_driver [19504.330000] i2c_dev: Unknown symbol i2c_master_send [20086.960000] i2c_core: Unknown symbol __i2c_board_list [20086.970000] i2c_core: Unknown symbol __i2c_first_dynamic_bus_num [20086.980000] i2c_core: Unknown symbol __i2c_board_lock [20233.870000] i2c_core: Unknown symbol __i2c_board_list [20233.880000] i2c_core: Unknown symbol __i2c_first_dynamic_bus_num [20233.890000] i2c_core: Unknown symbol __i2c_board_lock [20238.990000] i2c_core: Unknown symbol __i2c_board_list [20239.000000] i2c_core: Unknown symbol __i2c_first_dynamic_bus_num [20239.010000] i2c_core: Unknown symbol __i2c_board_lock [20684.420000] i2c_core: Unknown symbol __i2c_board_list [20684.430000] i2c_core: Unknown symbol __i2c_first_dynamic_bus_num [20684.440000] i2c_core: Unknown symbol __i2c_board_lock [22136.910000] i2c_core: Unknown symbol __i2c_board_list [22136.920000] i2c_core: Unknown symbol __i2c_first_dynamic_bus_num [22136.920000] i2c_core: Unknown symbol __i2c_board_lock [22790.330000] i2c_core: Unknown symbol __i2c_board_list [22790.340000] i2c_core: Unknown symbol __i2c_first_dynamic_bus_num [22790.350000] i2c_core: Unknown symbol __i2c_board_lock [/share/Qdownload/mythlab/linux-2.6.33.2] #

by **ybot** » Sat Oct 29, 2011 7:40 pm

@fergalom

It is on the border of my kernel knowledge too. However, I have the following lines in the .config file for the kernel

Code: Select all: CONFIG_I2C=m CONFIG_I2C_BOARDINFO=y CONFIG_I2C_COMPAT=y CONFIG_I2C_CHARDEV=m CONFIG_I2C_HELPER_AUTO=y

make sure it is the same, do a make distclean to be sure, enable all the relevant options (make sure you choose modules over built-in).

by **chomp!** » Wed Nov 02, 2011 8:22 am

Hey ybot,

It feels like I'm really close.. after I compile mythtv, I get the following:

Code: Select all: [~] # mythbackend mythbackend: error while loading shared libraries: libmythtv-0.24.so.0: cannot open shared object file: No such file or directory

However, if I look in /opt/lib everything is there....

Code: Select all: [/opt] # find . -name "libmythtv*" ./lib/libmythtv-0.24.so.0.24.0 ./lib/libmythtv-0.24.so ./lib/libmythtv-0.24.so.0.24 ./lib/libmythtv-0.24.so.0

Am I missing something painfully obvious here?

by **chomp!** » Wed Nov 02, 2011 11:45 pm

Howdy folks, was able to get it to work by doing the following:
http://blog.**.com/2007/10/h ... inuxs.html

edited /etc/ld.so.conf

to include: /opt/lib

reran /sbin/ldconfig

now mythtv runs.

by **fergalom** » Thu Nov 03, 2011 6:20 am

Couple of things I thought others might find useful on this topic, given ybot has been so helpful, finally got mythbackend and mythtv-setup running. :-)

To get the i2c-core.ko module to work, you will need to follow this post
http://forum.qnap.com/viewtopic.php?p=194182#p202235

Once all the moudles are compiled, I ran

Code: Select all: make install

which makes it easier to load the correct modules in the right order using modprobe as per the link to a post below

I have a Hauppage Win Nova-t usb stick, I follow the folloing post to get the correct modules to load and load the firmware.
http://forum.qnap.com/viewtopic.php?p=194182#p208102

X11 Forwarding

edit sshd_config file in /etc/ssh enable X11forwarding twice in the file

Code: Select all: X11Forwarding yes

restart the ssh daemon through the Qnap web admin interface to enable these changes

I'm on windows vista, I installed Xming (an X server for Windows):
http://sourceforge.net/projects/xming/

Edit the X0.hosts file (C:/program files/Xming) and add the ip address of your mythbackend (QNAP) machine

With XLaunch: open an X window, leave all options as-is with the display set at 0

log in to your Qnap box on your windows cliënt with Putty - after enabling X11 forwarding to your windows client in your putty session. (Connection > SSH > X11 > enable X11 forwarding + X display location = localhost:0)

in the Putty CLI you need to export the ip address of your windows machine

Code: Select all: export DISPLAY=win-vista-ip:0.0 mythtv-setup

You should now see the mythtv-setup page.

by **ybot** » Thu Nov 03, 2011 9:20 am

@chomp!

Good to see you resolved your own issue. I did the same, however I found over reboot I was again losing the correct ldconfig settings that allowed mythbackend to start automatically. Is this not a problem for you? I wonder why?
I added http://wiki.qnap.com/wiki/How_to_instal ... ot_scripts to programmatically work around this issue.

@fergalom

!!! woot !!!
If you have no objections I will add those instructions and references to the howto page. Congrats, please comment on the performance giving your machine/network specs (http://wiki.qnap.com/wiki/How_to_instal ... erformance).

QNAP NAS Community Forum

MythTV Backend Scheduler

Re: MythTV Backend Scheduler

Re: MythTV Backend Scheduler

Re: MythTV Backend Scheduler

Re: MythTV Backend Scheduler

Re: MythTV Backend Scheduler

Re: MythTV Backend Scheduler

Re: MythTV Backend Scheduler

Re: MythTV Backend Scheduler

Re: MythTV Backend Scheduler

Re: MythTV Backend Scheduler

Re: MythTV Backend Scheduler

Re: MythTV Backend Scheduler

Re: MythTV Backend Scheduler

Re: MythTV Backend Scheduler

Re: MythTV Backend Scheduler

Who is online