vix issues/bugs

[art]

PLI running for a week but....

root@tmtwinoesr:/media/hdd# ls
backup crossepg epg.dat imagebackups logs lost+found movie swapfile timeshift
root@tmtwinoesr:/media/hdd# cd logs
root@tmtwinoesr:/media/hdd/logs# ls
Enigma2-01-01-1970_01-00-52.log Enigma2-10-02-2013_13-09-41.log Enigma2-10-02-2013_13-09-51.log enigma2_crash_1359306726.log
Enigma2-01-01-1970_01-01-02.log Enigma2-10-02-2013_13-09-43.log Enigma2-10-02-2013_13-09-53.log enigma2_crash_1359402163.log
Enigma2-04-02-2013_18-45-11.log Enigma2-10-02-2013_13-09-44.log Enigma2-10-02-2013_13-09-54.log enigma2_crash_1359573419.log
Enigma2-08-02-2013_23-20-57.log Enigma2-10-02-2013_13-09-46.log Enigma2-26-01-2013_18-04-32.log enigma2_crash_1360003499.log
Enigma2-08-02-2013_23-21-35.log Enigma2-10-02-2013_13-09-47.log Enigma2-27-01-2013_17-12-25.log enigma2_crash_1360365683.log
Enigma2-09-02-2013_01-42-01.log Enigma2-10-02-2013_13-09-48.log Enigma2-28-01-2013_19-42-55.log enigma2_crash_1360374110.log
Enigma2-10-02-2013_11-53-26.log Enigma2-10-02-2013_13-09-50.log Enigma2-30-01-2013_19-17-17.log

Right this might be the source of my problems:

############################################

Found NAND on CS1: ACC=d3000000, cfg=56052300, flashId=adda1095, tim1=5363444f, tim2=00000fc6
BrcmNAND version = 0x0201 256MB @00000000
B4: NandSelect=50000200, nandConfig=56052300, chipSelect=1
brcmnand_read_id: CS1: dev_id=adda1095
After: NandSelect=50000200, nandConfig=56052300
Found NAND flash on Chip Select 1, chipSize=256MB, usable size=256MB, base=0
brcmnand_scan: B4 nand_select = 50000200
brcmnand_scan: After nand_select = 50000200
page_shift=11, bbt_erase_shift=17, chip_shift=28, phys_erase_shift=17
Brcm NAND controller version = 2.1 NAND flash size 256MB @10000000
ECC layout=brcmnand_oob_bch4_4k
brcmnand_scan: mtd->oobsize=64
brcmnand_scan: oobavail=50, eccsize=512, writesize=2048
brcmnand_scan, eccsize=512, writesize=2048, eccsteps=4, ecclevel=15, eccbytes=3
-->brcmnand_default_bbt
brcmnand_default_bbt: bbt_td = bbt_main_descr
Bad block table Bbt0 found at page 0001ffc0, version 0x01 for chip on CS1
Bad block table 1tbB found at page 0001ff80, version 0x01 for chip on CS1
nand_read_bbt: Bad block at 0x00640000
nand_read_bbt: Bad block at 0x00660000
nand_read_bbt: Bad block at 0x00dc0000
nand_read_bbt: Bad block at 0x01280000
nand_read_bbt: Bad block at 0x01c80000
nand_read_bbt: Bad block at 0x01ca0000
nand_read_bbt: Bad block at 0x02340000
nand_read_bbt: Bad block at 0x07620000
nand_read_bbt: Bad block at 0x07640000
nand_read_bbt: Bad block at 0x07660000
nand_read_bbt: Bad block at 0x080e0000
Creating 4 MTD partitions on "brcmnand.0":
0x000000000000-0x000002d00000 : "tmtwin"
0x000002d00000-0x00000eb00000 : "rootfs"
0x00000eb00000-0x00000f600000 : "bcmdrv"
0x00000f600000-0x00000ff00000 : "nkernel"
UBI: attaching mtd4 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
ata2: SATA link down (SStatus 4 SControl 300)
UBI: max. sequence number: 839
UBI: attached mtd4 to ubi0
UBI: MTD device name: "rootfs"
UBI: MTD device size: 190 MiB
UBI: number of good PEBs: 1516
UBI: number of bad PEBs: 4
UBI: number of corrupted PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 1
UBI: available PEBs: 0
UBI: total number of reserved PEBs: 1516
UBI: number of PEBs reserved for bad PEB handling: 15
UBI: max/mean erase counter: 3/1
UBI: image sequence number: 79428163
UBI: background thread "ubi_bgt0d" started, PID 44
UBIFS: parse sync
UBIFS: mounted UBI device 0, volume 4, name "rootfs"
UBIFS: file system size: 188686336 bytes (184264 KiB, 179 MiB, 1486 LEBs)
UBIFS: journal size: 9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
UBIFS: media format: w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root: 0 bytes (0 KiB)
VFS: Mounted root (ubifs filesystem) on device 0:11.
Freeing unused kernel memory: 236k freed

##### FRONT ID & Version Check #####
[TM-TWIN]
[Front Version = 0 ]
####################################

input: TM-TWIN remote control (native) as /devices/virtual/input/input0
BRCM7335 Infra Red driver (Feb 8 2013-07:53:36)
Linux DVB BCM73xx FPGA CI Driver Release Time (08/02/13 07:53:36)
DVB: registering new adapter (brcm73350)
DVB: registering adapter 0 frontend 0 (BCM7335 DVB-S2)...
DVB: registering new adapter (brcm73351)
DVB: registering adapter 1 frontend 0 (BCM7335 DVB-S2)...
DVB: registering new adapter (brcm7335Dvr2)
DVB: registering new adapter (brcm7335Dvr3)
DVB: registering new adapter (brcm7335Dvr4)
Registering device 'sci', major '238'
Version of smartcard driver: [1.0.0]
usbcore: registered new interface driver ath9k_htc
usbcore: registered new interface driver carl9170
NET: Registered protocol family 10

rtw driver version=v3.3.0_2971.20111128
usbcore: registered new interface driver rtl8192cu
r8712u: module is from the staging directory, the quality is unknown, you have been warned.
usbcore: registered new interface driver r8712u
usbcore: registered new interface driver rt2500usb
usbcore: registered new interface driver rt2800usb
usbcore: registered new interface driver rt73usb
usbcore: registered new interface driver rtl8187
usbcore: registered new interface driver usbserial
USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial Driver core
usbcore: registered new interface driver zd1211rw
EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
Undifined lcd ioctl 1015
eth0: no IPv6 routers present

################################################## #

so the flash has bad blocks which theroretically have been mapped out but how does this affect the new bootloader if it tries to create a bigger partition....I'll give Tony from TM a bell today and see if they can sort me another box.

[art]

Right all sorted thanks to Jony from Technomate. The problem was not following the flash notes "precisely". I've gone a whole week without a crash or reboot. All problems relate to flash not being setup correctly....although I have to say it's somewhat a convoluted process to have the box operate properly. Thanks for those who gave input and help and to the chap who also had problems in this thread...i'll post a more concise set of details later on as im on the notepad at the moment

[nipperlocko]

Hi there, I`m on build 600 but am having several recording problems and wondered am I the only one, my first issue is when 2 recordings are being made and I try to watch a recorded programme from hard drive it hangs forever and never starts, if I`m already watching something off the hard drive ans a programme starts to record it glitch`s and jumps a little,but if a second recording starts it`s unwatchable, I also cannot use permanent timeshift as this causes many problems too, I called technomate and they recommend using the 4D image, is this my only alternative or can this bug be fixed in the next build

[abu baniaz]

If you did not have the issues on previous builds, you can always go back to an older image.

However, it would be handy to submit your debug logs so the developers can get to the bottom of the issue.

[art]

Right all sorted thanks to Jony from Technomate. The problem was not following the flash notes "precisely". I've gone a whole week without a crash or reboot. All problems relate to flash not being setup correctly....although I have to say it's somewhat a convoluted process to have the box operate properly. Thanks for those who gave input and help and to the chap who also had problems in this thread...i'll post a more concise set of details later on as im on the notepad at the moment

Groan...spoke too soon. So it works alright for a week and I reorg the bouquets....now this week enigma has crashed several time and come to it this morning and it's not decoding. I restart CCcam and enigma crashes. Still not decoding so a reboot of the receiver sorts it. I'm fed up with this box BIG style. Not playing with it any more....it's going back to TM.

[art]

...it went back to TM and they replaced the mainboard. Now its sweet as a nut running vix. An apology would have been nice but at least its working and functional.