Hello Guest, if you are reading this it means you have not registered yet. Please take a second, Click here to register, and in a few simple steps you will be able to enjoy our community and use our OpenViX support section.
Page 1 of 4 123 ... LastLast
Results 1 to 15 of 60

Thread: VU+ stuck at 'Starting...'

  1. #1
    danishdude's Avatar
    Title
    Member
    Join Date
    Oct 2010
    Posts
    75
    Thanks
    33
    Thanked 7 Times in 6 Posts

    VU+ stuck at 'Starting...'

    Yesterday my box went belly-up suddenly. After a restart all i got was "Starting..."
    No picture on tv...nothing.

    Bring forth ye 'ol RS232-cable...<plug> - and lets see what it says - if anything. And yes - its breathing, albeit barely:

    Code:
      Normal   0x00000000 -> 0x00010000
    Movable zone start PFN for each node
    early_node_map[1] active PFN ranges
        0: 0x00000000 -> 0x00010000
    PERCPU: Embedded 7 pages/cpu @81203000 s4384 r8192 d16096 u32768
    Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
    Kernel command line: bmem=112M ubi.mtd=0 root=ubi0:rootfs rootfstype=ubifs rw console=ttyS0,115200n8 rootflags=sync
    PID hash table entries: 1024 (order: 0, 4096 bytes)
    Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
    Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
    Primary instruction cache 32kB, VIPT, 2-way, linesize 64 bytes.
    Primary data cache 64kB, 4-way, VIPT, cache aliases, linesize 64 bytes
    Memory: 138032k/262144k available (5534k kernel code, 124112k reserved, 1192k data, 248k init, 0k highmem)
    Hierarchical RCU implementation.
    NR_IRQS:128
    Detected MIPS clock frequency: 404 MHz (202.493 MHz counter)
    Console: colour dummy device 80x25
    Calibrating delay loop... 403.45 BogoMIPS (lpj=201728)
    pid_max: default: 32768 minimum: 301
    Mount-cache hash table entries: 512
    SMP: Booting CPU1...
    CPU revision is: 0002a044 (Brcm4380)
    FPU revision is: 00130001
    Primary instruction cache 32kB, VIPT, 2-way, linesize 64 bytes.
    Primary data cache 64kB, 4-way, VIPT, cache aliases, linesize 64 bytes
    SMP: CPU1 is running
    Brought up 2 CPUs
    NET: Registered protocol family 16
    PCI2.3->SDRAM window: 512 MB
    bio: create slab <bio-0> at 0
    SCSI subsystem initialized
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    usbcore: registered new device driver usb
    Advanced Linux Sound Architecture Driver Version 1.0.24.
    PCI: found device 14e4:8602 on SATA bus, slot 0 (irq 42)
    pci 0000:01:00.0: BAR 5: assigned [mem 0x10510000-0x10510fff]
    pci 0000:01:00.0: BAR 5: set to [mem 0x10510000-0x10510fff] (PCI address [0x10510000-0x10510fff])
    pci 0000:01:00.0: BAR 6: assigned [mem 0x10511000-0x105117ff pref]
    Bluetooth: Core ver 2.16
    NET: Registered protocol family 31
    Bluetooth: HCI device and connection manager initialized
    Bluetooth: HCI socket layer initialized
    Bluetooth: L2CAP socket layer initialized
    cfg80211: Calling CRDA to update world regulatory domain
    Switching to clocksource upg
    NET: Registered protocol family 2
    IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
    TCP established hash table entries: 8192 (order: 4, 65536 bytes)
    TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
    TCP: Hash tables configured (established 8192 bind 8192)
    TCP reno registered
    UDP hash table entries: 128 (order: 0, 4096 bytes)
    UDP-Lite hash table entries: 128 (order: 0, 4096 bytes)
    NET: Registered protocol family 1
    RPC: Registered named UNIX socket transport module.
    RPC: Registered udp transport module.
    RPC: Registered tcp transport module.
    RPC: Registered tcp NFSv4.1 backchannel transport module.
    fuse init (API version 7.17)
    msgmni has been set to 269
    io scheduler noop registered
    io scheduler cfq registered (default)
    Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    serial8250.0: ttyS0 at MMIO 0x10400b00 (irq = 22) is a 16550A
    console [ttyS0] enabled, bootconsole disabled
    console [ttyS0] enabled, bootconsole disabled
    serial8250.0: ttyS1 at MMIO 0x10400b40 (irq = 66) is a 16550A
    serial8250.0: ttyS2 at MMIO 0x10400b80 (irq = 67) is a 16550A
    loop: module loaded
    brcm-pm: enabling sata clocks
    PCI: Enabling device 0000:01:00.0 (0000 -> 0003)
    scsi0 : sata_brcmstb
    scsi1 : sata_brcmstb
    ata1: SATA max UDMA7 mmio m4096@0x10510000 port 0x10510000 irq 42
    ata2: SATA max UDMA7 mmio m4096@0x10510000 port 0x10510100 irq 42
    Broadcom STB NAND controller (BrcmNand Controller)
    bcmemac: Broadcom STB 10/100 EMAC driver v3.0
    bcmemac: registered interface #0 at 0x10080000 as 'eth0' (00:1d:ec:01:aa:a5)
    bcmemac: not registering interface #1 at 0x10090000 (no PHY detected)
    usbcore: registered new interface driver zd1201
    ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    brcm-pm: enabling usb clocks
    ehci-brcm ehci-brcm.0: Broadcom STB EHCI
    ehci-brcm ehci-brcm.0: new USB bus registered, assigned bus number 1
    ehci-brcm ehci-brcm.0: irq 62, io mem 0x10480300
    ehci-brcm ehci-brcm.0: USB 0.0 started, EHCI 1.00
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 2 ports detected
    ehci-brcm ehci-brcm.1: Broadcom STB EHCI
    ehci-brcm ehci-brcm.1: new USB bus registered, assigned bus number 2
    ehci-brcm ehci-brcm.1: irq 57, io mem 0x10480500
    ehci-brcm ehci-brcm.1: USB 0.0 started, EHCI 1.00
    hub 2-0:1.0: USB hub found
    hub 2-0:1.0: 2 ports detected
    ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
    ohci-brcm ohci-brcm.0: Broadcom STB OHCI
    ohci-brcm ohci-brcm.0: new USB bus registered, assigned bus number 3
    ohci-brcm ohci-brcm.0: irq 63, io mem 0x10480400
    hub 3-0:1.0: USB hub found
    hub 3-0:1.0: 2 ports detected
    ohci-brcm ohci-brcm.1: Broadcom STB OHCI
    ohci-brcm ohci-brcm.1: new USB bus registered, assigned bus number 4
    ohci-brcm ohci-brcm.1: irq 64, io mem 0x10480600
    hub 4-0:1.0: USB hub found
    hub 4-0:1.0: 2 ports detected
    ata1: SATA link down (SStatus 4 SControl 300)
    Initializing USB Mass Storage driver...
    usbcore: registered new interface driver usb-storage
    USB Mass Storage support registered.
    mousedev: PS/2 mouse device common for all mice
    i2c /dev entries driver
    lirc_dev: IR Remote Control driver registered, major 254
    IR NEC protocol handler initialized
    IR RC5(x) protocol handler initialized
    IR RC6 protocol handler initialized
    IR JVC protocol handler initialized
    IR Sony protocol handler initialized
    IR RC5 (streamzap) protocol handler initialized
    IR MCE Keyboard/mouse protocol handler initialized
    IR LIRC bridge handler initialized
    Bluetooth: Generic Bluetooth USB driver ver 0.6
    usbcore: registered new interface driver btusb
    usbcore: registered new interface driver usbhid
    usbhid: USB HID core driver
    ALSA device list:
      No soundcards found.
    TCP cubic registered
    NET: Registered protocol family 17
    Bluetooth: HIDP (Human Interface Emulation) ver 1.2
    lib80211: common routines for IEEE802.11 drivers
    EBI CS0: setting up NAND flash (primary)
    mtd->oobsize=0, mtd->eccOobSize=0
    NAND_CS_NAND_XOR=00000001
    B4: NandSelect=40000101, nandConfig=55042200, chipSelect=0
    brcmnand_read_id: CS0: dev_id=ecf10095
    After: NandSelect=40000101, nandConfig=55042200
    Block size=00020000, erase shift=17
    NAND Config: Reg=55042200, chipSize=128 MB, blockSize=128K, erase_shift=11
    busWidth=1, pageSize=2048B, page_shift=11, page_mask=000007ff
    BrcmNAND mfg ec f1 Samsung K9F1G08U0A 128MB on CS0
    
    
    Found NAND on CS0: ACC=d3000000, cfg=55042200, flashId=ecf10095, tim1=4232222d, tim2=00000d94
    BrcmNAND version = 0x0201 128MB @00000000
    B4: NandSelect=40000101, nandConfig=55042200, chipSelect=0
    brcmnand_read_id: CS0: dev_id=ecf10095
    After: NandSelect=40000101, nandConfig=55042200
    Found NAND flash on Chip Select 0, chipSize=128MB, usable size=128MB, base=0
    brcmnand_scan: B4 nand_select = 40000101
    brcmnand_scan: After nand_select = 40000101
    page_shift=11, bbt_erase_shift=17, chip_shift=27, phys_erase_shift=17
    Brcm NAND controller version = 2.1 NAND flash size 128MB @18000000
    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
    Creating 7 MTD partitions on "brcmnand.0":
    0x000000000000-0x000007600000 : "rootfs"
    0x000007600000-0x000007a00000 : "kernel"
    0x000007a00000-0x000007c00000 : "boot"
    0x000007c00000-0x000007d00000 : "cfe"
    0x000007d00000-0x000007d80000 : "mac"
    0x000007d80000-0x000007e00000 : "env"
    0x000007e00000-0x000007f00000 : "nvm"
    UBI: attaching mtd0 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:       101
    UBI: attached mtd0 to ubi0
    UBI: MTD device name:            "rootfs"
    UBI: MTD device size:            118 MiB
    UBI: number of good PEBs:        943
    UBI: number of bad PEBs:         1
    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: 943
    UBI: number of PEBs reserved for bad PEB handling: 9
    UBI: max/mean erase counter: 2/0
    UBI: image sequence number:  1367958133
    UBI: background thread "ubi_bgt0d" started, PID 44
    UBIFS: parse sync
    UBIFS: recovery needed
    UBIFS: recovery completed
    UBIFS: mounted UBI device 0, volume 0, name "rootfs"
    UBIFS: file system size:   116690944 bytes (113956 KiB, 111 MiB, 919 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:12.
    Freeing unused kernel memory: 248k freed
    INIT: version 2.86 booting
    Please wait: booting...
    Root filesystem already rw, not remounting
    Configuring update-modules.
    procmk_init
    dvb_bcm7335: module license 'Proprietary' taints kernel.
    Disabling lock debugging due to kernel taint
    DVB: registering new adapter (bm750)
    CPU 0 Unable to handle kernel paging request at virtual address 00000004, epc == c07d4df0, ra == c06d06c4
    Oops[#1]:
    Cpu 0
    $ 0   : 00000000 10008700 c07d4df0 c0ad0000
    $ 4   : 00000000 884b5b80 00000000 00000000
    $ 8   : 00000004 802b914c 00000000 00000000
    $12   : 88c4cc00 00000000 00000200 00002711
    $16   : 881aca00 88da398c 00000000 00000001
    $20   : 88da3994 00000002 00000005 c06cf910
    $24   : 00000000 802b9060
    $28   : 88da2000 88da3918 c06cf960 c06d06c4
    Hi    : 00000000
    Lo    : 00000000
    epc   : c07d4df0 NEXUS_I2c_GetRegHandle+0x0/0x30 [dvb_bcm7335]
        Tainted: P
    ra    : c06d06c4 NEXUS_Tuner_Open3440_impl+0x74/0x340 [dvb_bcm7335]
    Status: 10008703    KERNEL EXL IE
    Cause : 00800008
    BadVA : 00000004
    PrId  : 0002a044 (Brcm4380)
    Modules linked in: dvb_bcm7335(P+) procmk
    Process modprobe (pid: 229, threadinfo=88da2000, task=88fa4988, tls=7713b490)
    Stack : c0707010 c0708004 00000000 c06f4740 00000002 c0ad0dcc 00000003 00000001
            88da398c c0ad0dd0 00000003 00000001 88da3994 c06ced24 c0ae0000 10008701
            8777d680 00000026 88da398c 88da39a4 88da398c c06c4208 88da3a6c 8777df80
            c0adb3c0 88da39e0 8843fa00 00000000 00000003 00000000 00000064 000186a0
            87770001 00000000 00000000 00000001 01000100 00000100 000000bc 00000001
            ...
    Call Trace:
    [<c07d4df0>] NEXUS_I2c_GetRegHandle+0x0/0x30 [dvb_bcm7335]
    [<c06d06c4>] NEXUS_Tuner_Open3440_impl+0x74/0x340 [dvb_bcm7335]
    [<c06ced24>] NEXUS_Tuner_Open3440+0x28/0x48 [dvb_bcm7335]
    [<c06c4208>] NEXUS_Platform_InitFrontend+0x23c/0x584 [dvb_bcm7335]
    [<c06c2e5c>] NEXUS_Platform_Init+0x710/0x7c4 [dvb_bcm7335]
    [<c0b540d8>] bcm7335_init+0xd8/0x854 [dvb_bcm7335]
    [<80001450>] do_one_initcall+0x40/0x1f8
    [<800726e0>] sys_init_module+0x174/0x14a0
    [<8000e9fc>] stack_done+0x20/0x40
    
    
    
    
    Code: 24020008  03e00008  24020008 <8c830004> 10a30008  24820064  50a00006  24820008  3c02c0ad
    ---[ end trace df588688b6a9d423 ]---
    Anyone have an idea what went wrong around the kernel paging leading to Oops[#1]?

    I've been trying to refresh images. Including new fresh ViX (first with the bootloader and then the image), and afterwards trying with a standard VU+ Duo image from the manufacturer (v7.0).

    Still no tv for me - so would really appreciate it, if any of you experts could cast a working spell
    VU+ Uno
    R.I.P., dead VU+ Duo
    Fixed Triax 78cm @ 0.8W & 4.8E


  2. #2
    Zartmy's Avatar
    Title
    Member
    Join Date
    Aug 2011
    Location
    Sweden
    Posts
    88
    Thanks
    14
    Thanked 23 Times in 19 Posts
    UBI: attaching mtd0 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: 101
    UBI: attached mtd0 to ubi0
    UBI: MTD device name: "rootfs"
    UBI: MTD device size: 118 MiB
    UBI: number of good PEBs: 943
    UBI: number of bad PEBs: 1
    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: 943
    UBI: number of PEBs reserved for bad PEB handling: 9
    I think the highlighted bit indicates that the internal flash memory is damaged.

    Only strange thing i see (not counting the kernel crash ). Someone problary have a better answear...
    Not native english speaker, bare with me...

  3. The Following User Says Thank You to Zartmy For This Useful Post:

    danishdude (02-03-12)

  4. #3
    danishdude's Avatar
    Title
    Member
    Join Date
    Oct 2010
    Posts
    75
    Thanks
    33
    Thanked 7 Times in 6 Posts
    Quote Originally Posted by Zartmy View Post
    I think the highlighted bit indicates that the internal flash memory is damaged.

    Only strange thing i see (not counting the kernel crash ). Someone problary have a better answear...
    Damn...*hmm*
    Thanks for the swift reply, Zartmy.

    I am about to try with VTi...just for kicks.

    If anyone has an idea, please chime in. I have time to get it in for repair tomorrow. Sadly, it's just over one year old - and the shop only gives one year warranty
    VU+ Uno
    R.I.P., dead VU+ Duo
    Fixed Triax 78cm @ 0.8W & 4.8E


  5. #4
    danishdude's Avatar
    Title
    Member
    Join Date
    Oct 2010
    Posts
    75
    Thanks
    33
    Thanked 7 Times in 6 Posts
    Nope...VTi is a no-go too.
    Apparently flashmemory-management insists on writing to the faulty PEB each time. It just puzzles me why there are 9 in reserve, if these cant be invoked when one goes bad!?

    I will hand it over for repair. *bugger*
    VU+ Uno
    R.I.P., dead VU+ Duo
    Fixed Triax 78cm @ 0.8W & 4.8E


  6. #5
    Zartmy's Avatar
    Title
    Member
    Join Date
    Aug 2011
    Location
    Sweden
    Posts
    88
    Thanks
    14
    Thanked 23 Times in 19 Posts
    Well, it might aswell be faulty memory or something else. I think the filesystem UBIFS uses the reserve ones when it detects an error. Your problem is that the flashtool used when applying the image is writing the UBIFS image over the broken memory, so the ubi filesystem is broken the first time it boots. But still i am no expert in nand memory nor ubifs, I might be out cycling... (hmm is that expression valid in english?)
    Last edited by Zartmy; 02-03-12 at 23:43. Reason: fixed UBI to UBIFS
    Not native english speaker, bare with me...

  7. The Following User Says Thank You to Zartmy For This Useful Post:

    danishdude (12-03-12)

  8. #6
    danishdude's Avatar
    Title
    Member
    Join Date
    Oct 2010
    Posts
    75
    Thanks
    33
    Thanked 7 Times in 6 Posts
    Quote Originally Posted by Zartmy View Post
    Well, it might aswell be faulty memory or something else. I think the filesystem UBIFS uses the reserve ones when it detects an error. Your problem is that the flashtool used when applying the image is writing the UBIFS image over the broken memory, so the ubi filesystem is broken the first time it boots. But still i am no expert in nand memory nor ubifs, I might be out cycling... (hmm is that expression valid in english?)
    Makes perfect sense - and so does your cycling
    VU+ Uno
    R.I.P., dead VU+ Duo
    Fixed Triax 78cm @ 0.8W & 4.8E


  9. #7

    Title
    Senior Member
    Join Date
    May 2011
    Posts
    150
    Thanks
    60
    Thanked 8 Times in 7 Posts
    How does nand get damaged like that? Is there anything in particular you should avoid

  10. #8
    Zartmy's Avatar
    Title
    Member
    Join Date
    Aug 2011
    Location
    Sweden
    Posts
    88
    Thanks
    14
    Thanked 23 Times in 19 Posts
    Quote Originally Posted by 75mak View Post
    How does nand get damaged like that? Is there anything in particular you should avoid
    ESD Electric Discharge, wear and tear - nand flash and most flash memory has a finit number of write/erase cycles, read more on wikipedia http://en.wikipedia.org/wiki/Flash_memory#NAND_flash

    Unless your inside your box doing stuff, like replacing the harddrive often, i dont think there is much you can do.
    Not native english speaker, bare with me...

  11. #9
    danishdude's Avatar
    Title
    Member
    Join Date
    Oct 2010
    Posts
    75
    Thanks
    33
    Thanked 7 Times in 6 Posts
    It's just a shame, that a box only 16 months old already dies like that.
    No excessive work been done on it. Only installed a harddrive, and flashed new images on it when they appeared. Typically a few months apart.
    I am used to work with sensitive hardware like this (ESD) - so i guess i've just been unlucky.
    VU+ Uno
    R.I.P., dead VU+ Duo
    Fixed Triax 78cm @ 0.8W & 4.8E


  12. #10
    danishdude's Avatar
    Title
    Member
    Join Date
    Oct 2010
    Posts
    75
    Thanks
    33
    Thanked 7 Times in 6 Posts
    The poor sick Duo has now been turned in for repair.
    Two dudes behind the counter didnt know sh** about Linux-receivers, and the fact that i produced a log showing the exact error. Oh no - it has to go to the distributor, who will test it for errors and so on...only to come up with the exact same diagnosis i left documented in the box.
    So, instead of getting the mainboard exhanged immediately (or a replacement receiver), i will have to wait for the whole circus to rev up and take its turns. *sigh*
    So, no receiver for me the next two/three/four weeks.

    It's hard being a knowledgeable consumer

    I even considered buying a Solo as a replacement, and sell it again, when the other one came back. Or sell the Duo, when it has been repaired (i actually dont use the dual-tuners - so no need-to-have). The Solo, with it's interchangeable tuners could come in handy, if i, in the future, go from DVB-S to DVB-C.

    #GoodthingidontwatchTHATmuchtv-otherwiseiwouldhavegonecrazy

    Other than that...good morning from Scandinavia
    VU+ Uno
    R.I.P., dead VU+ Duo
    Fixed Triax 78cm @ 0.8W & 4.8E


  13. #11
    danishdude's Avatar
    Title
    Member
    Join Date
    Oct 2010
    Posts
    75
    Thanks
    33
    Thanked 7 Times in 6 Posts
    16 months old - and the shop washes it's hands, and tells me i have to handle the problem myself, contacting the distributor directly (Digital Nordic Sweden) - as the warranty ran out four months ago. At the same time, they tell me i shouldnt get my hopes up, as i need to provide futher proof to the problem.(!!?) Apparently the serial-dump, showing the exact problem, is not enough - if you ask them.
    What else do they want? What else can i do? Beats me...*sigh*

    Just ordered a new Uno instead (NOT a the same shop )
    Now...what to do with the 'old' Duo. Will it blend? Can it burn?

    (Four months out of warranty...*arrrrgh*)
    VU+ Uno
    R.I.P., dead VU+ Duo
    Fixed Triax 78cm @ 0.8W & 4.8E


  14. #12

    Title
    Senior Member
    Join Date
    Oct 2010
    Location
    Berkshire
    Posts
    9,697
    Thanks
    1,039
    Thanked 4,385 Times in 2,257 Posts
    whats is the serial dump
    im curious to see if its a fixable error


    edit: sorry i see it post 1
    PM HELP WILL BE IGNORED PLEASE POST HERE IN FORUM AS IT BENEFITS EVERYONE
    NO CARD SHARING TALK WILL BE TOLERATED, LAN OR WAN! IN OPEN FORUM OR PM


    IF THE POSTS HELP PLEASE CLICK THANKS OR ADD TO REP ↓

  15. #13
    danishdude's Avatar
    Title
    Member
    Join Date
    Oct 2010
    Posts
    75
    Thanks
    33
    Thanked 7 Times in 6 Posts
    Quote Originally Posted by silverfox0786 View Post
    whats is the serial dump
    im curious to see if its a fixable error
    edit: sorry i see it post 1
    Looking forward to hear your input (output, actually)
    VU+ Uno
    R.I.P., dead VU+ Duo
    Fixed Triax 78cm @ 0.8W & 4.8E


  16. #14

    Title
    Senior Member
    Join Date
    Oct 2010
    Location
    Berkshire
    Posts
    9,697
    Thanks
    1,039
    Thanked 4,385 Times in 2,257 Posts
    i dont think that PEB is your issue but i may be wrong

    you do have a bad PEB thats true but

    then you get 9 PEBS handled for that issue

    if those 9 PEBS couldnt handle it then this is the sort of output you would have gotten

    "UBI warning: cannot reserve enough PEBs for bad PEB
    handling, reserved 0, need 20"


    then there is also this that makes me wonder


    Code:
    Found NAND flash on Chip Select 0, chipSize=128MB, usable size=128MB, base=0

    then there si this

    Code:
    UBIFS: recovery needed
    UBIFS: recovery completed

    and here is your problem

    a faulty tuner card

    Code:
    dvb_bcm7335: module license 'Proprietary' taints kernel.
    Disabling lock debugging due to kernel taint
    PM HELP WILL BE IGNORED PLEASE POST HERE IN FORUM AS IT BENEFITS EVERYONE
    NO CARD SHARING TALK WILL BE TOLERATED, LAN OR WAN! IN OPEN FORUM OR PM


    IF THE POSTS HELP PLEASE CLICK THANKS OR ADD TO REP ↓

  17. The Following User Says Thank You to silverfox0786 For This Useful Post:

    danishdude (16-03-12)

  18. #15
    danishdude's Avatar
    Title
    Member
    Join Date
    Oct 2010
    Posts
    75
    Thanks
    33
    Thanked 7 Times in 6 Posts
    You NERD!

    ...and thats meant in a positive way.
    You have any idea if theres a fix - or do i need to have the entire tuner replaced?
    (Why didnt i read more into Linux at an early age!? *hehe*)
    VU+ Uno
    R.I.P., dead VU+ Duo
    Fixed Triax 78cm @ 0.8W & 4.8E


Page 1 of 4 123 ... LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.