Results 1 to 4 of 4

Thread: Help! Monte is killing 2 of my HDVR2!

  1. #1
    Join Date
    Oct 2003
    Posts
    90

    Help! Monte is killing 2 of my HDVR2!

    After many days of searching, learning and asking. I finally get d70's Monte working. I get Bash, telenet, Ftp and Tivoweb. I was very happy when I finally get the wireless ethernet to work .... until tonight.
    It happens to one of the HDVR2 running on a 3.1.0 (not the b) and I was watching a program I record earlier that day. All the sudden, the picture froze and then it shut down and return to the powering up screen and it just stuck there. I take the HDVR2 to the computer, plug in the serial cable and this is the message I got:

    IDE drive(0): Disk not responding to device selection
    read_sector device_select failed
    IDE drive(1): Disk not responding to device selection
    read_sector device_select failed
    IDE drive(0): Disk not responding to device selection
    read_sector device_select failed
    autoboot failed to read boot sector
    Initializing USB ethernet
    Device on dev=13 fnc=1 port=0
    init there is no device
    Ram size = 64
    Service number is 1510000A045C866.
    What is password?

    Does that mean I had a bad drive? I just got that from Weaknees (upgrad 160g drive). Does it mean everything is gone? What is the next step? Format the drive and start over?

    The 2nd HDVR2 has a different problem. After checking everything is fine at the computer, telenet, wireless ethernet etc are all working, I plug in the satellite feed and that is where the problem arise. After acquiring the data screen (for the guide), it show about 95% and then it jump to live tv for about 5 second, the picture went black and return back to the Welcome, powering up screen and then it goes in circle:
    Powering up .... Almost there ... Acquiring data .... live tv (5 sec) ... blackout ... Powering up .....
    The interesting thing is that as long as I avoid watching live tv and watch the record program, the HDVR2 will not go in that cycle.
    Oh, I still got my wireless telenet access and tivoweb as long as I don't watch live tv. I am really stump.

    After nearly 1 week and I thought I was done, it looks like I might have to start all over again. Someone please give me some suggestion!

  2. #2
    Join Date
    Oct 2003
    Posts
    90
    One more thing, I check the kernel log on the 2nd HDVR2 and this might be the cause of it but I have no idea what it means:

    Oct 30 09:19:06 (none) kernel: oslink: 01 00 00 Access Card: Inserted Tuner[0]: Not Locked Tuner[1]: Not Locked
    Oct 30 09:19:06 (none) kernel: oslink: 01 01 00 Access Card: Inserted Tuner[0]: Locked Tuner[1]: Not Locked
    Oct 30 09:19:26 (none) kernel: oslink: 01 00 00 Access Card: Inserted Tuner[0]: Not Locked Tuner[1]: Not Locked
    Oct 30 09:19:27 (none) kernel: oslink: 01 01 00 Access Card: Inserted Tuner[0]: Locked Tuner[1]: Not Locked
    Oct 30 09:19:40 (none) kernel: ApgManager Transition from state FAST_LOAD to PREP_SETUP
    Oct 30 09:19:45 (none) kernel: ApgManager Transition from state PREP_SETUP to EXPRESSION_EVALUATION
    Oct 30 09:20:03 (none) kernel: ApgManager Transition from state EXPRESSION_EVALUATION to STEADY_STATE
    Oct 30 09:20:47 (none) kernel: do_page_fault() #2: sending SIGSEGV to myworld for illegal read access from
    Oct 30 09:20:47 (none) kernel: 00000010 (epc == 0085c8bc, ra == 0085c8b8)
    Oct 30 09:20:47 (none) kernel: Tmk Fatal Error: Thread ContextMgr event handler <176> died due to signal 11
    Oct 30 09:20:47 (none) kernel: pc 0x85c8bc status 0x8001bc13 cause 0x000008 bva 0x7fbfee44 hi 00000000 lo 0x000400
    Oct 30 09:20:47 (none) kernel: R00 0x00000000 R01 0x9001bc00 R02 0x00000089 R03 0x00000002
    Oct 30 09:20:47 (none) kernel: R04 0x7fff74b8 R05 0x00000282 R06 0x00000089 R07 0x00000282
    Oct 30 09:20:47 (none) kernel: R08 0x00000001 R09 0x00000010 R10 0x00000000 R11 0x7265736f
    Oct 30 09:20:47 (none) kernel: R12 0x75726365 R13 0x7fff71f8 R14 0x808e5ef0 R15 0x80871480
    Oct 30 09:20:47 (none) kernel: R16 0x00000020 R17 0x7fff7560 R18 0x00000000 R19 0x00000000
    Oct 30 09:20:47 (none) kernel: R20 0x00000000 R21 0x00000000 R22 0x00000000 R23 0x7f703e2c
    Oct 30 09:20:47 (none) kernel: R24 0x00000000 R25 0x008844f8 R26 0x652f7265 R27 0x00000000
    Oct 30 09:20:47 (none) kernel: R28 0x10043e50 R29 0x7fff7488 R30 0x00000282 R31 0x0085c8b8
    Oct 30 09:20:47 (none) kernel: F00 0x4024000000000000 F02 0x000000000000000a
    Oct 30 09:20:47 (none) kernel: F04 0xffffffffffffffff F06 0xffffffffffffffff
    Oct 30 09:20:47 (none) kernel: F08 0xffffffffffffffff F10 0xffffffffffffffff
    Oct 30 09:20:47 (none) kernel: F12 0xffffffffffffffff F14 0xffffffffffffffff
    Oct 30 09:20:47 (none) kernel: F16 0xffffffffffffffff F18 0xffffffffffffffff
    Oct 30 09:20:47 (none) kernel: F20 0xffffffffffffffff F22 0xffffffffffffffff
    Oct 30 09:20:47 (none) kernel: F24 0xffffffffffffffff F26 0xffffffffffffffff
    Oct 30 09:20:47 (none) kernel: F28 0xffffffffffffffff F30 0xffffffffffffffff
    Oct 30 09:20:47 (none) kernel: csr 0x000004 eir 0x005410
    Oct 30 09:20:47 (none) kernel: 85c8bc 6fef80 6fc2b8 81f044 83dc84 83df9c 6e8644 6ed208 76ede0 d0ea88 d3d6f0 d59608 oslink: 01 07 01 Access Card: Inserted Tuner[0]: Locked Tuner[1]: Locked
    Oct 30 09:20:48 (none) kernel: oslink: 01 07 07 Access Card: Inserted Tuner[0]: Locked Tuner[1]: Locked
    Oct 30 09:20:49 (none) kernel: oslink: 01 07 01 Access Card: Inserted Tuner[0]: Locked Tuner[1]: Locked
    Oct 30 09:20:50 (none) kernel: oslink: 01 07 00 Access Card: Inserted Tuner[0]: Locked Tuner[1]: Not Locked
    Oct 30 09:20:50 (none) kernel: oslink: 01 07 07 Access Card: Inserted Tuner[0]: Locked Tuner[1]: Locked
    Oct 30 09:23:01 (none) kernel: Checking for additional disk

    Any idea?

  3. #3
    Join Date
    May 2002
    Posts
    314
    This isn't a monte issue.

    Your hard drive is failing.

  4. #4
    Join Date
    Oct 2003
    Posts
    90
    Thanks for the reply. I suspect it is my hard drive but this line:
    Oct 30 09:20:47 (none) kernel: Tmk Fatal Error: Thread ContextMgr event handler <176> died due to signal 11

    I have been doing search on the ContextMgr but didn't find much information which throw me off on the hard drive failure. I will just have to get a new drive and start over again.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •