Monte troubles.

[Chiun]

Background info:
SA S2 Tivo 60 gig

Problem: I get to the second screen and it keeps rebooting. I also get no feedback from my hyperterminal screen.

I already did the oblivious stuff of checking the jumper and cables.

I've gone through this three times and the same thing keeps happening.
I must be doing something wrong from needo's guide (http://www.superhero.org/tivo/). I never got any errors that I wasn't supposed to get (I did the one about the 4 meg kernel being written to 2 meg partition).

The following command has five spaces.
/cdrom/bootpage -P "root=/dev/hda7 BASH_ENV=\`mount\$IFS-n\$IFS/dev/hda14\$IFS/mnt;echo\$IFS/mnt/runmonte\`" -C /dev/hdc

I edited the rc.sysinit file correctly.
/bin/bash</dev/ttyS2&>/dev/ttyS2&
is at the bottom of the file.
I changed the netfilter thing to disable.

Am I supposed to chmod something other than the runmonte file? I did a chmod 777 on it before I did anything with it.

Any thing else I can check?

[Chiun]

This has got me flabergasted. I even tried to monte 3.0 to 3.2 but that even hangs on the second screen. It seems to hang just a little bit longer right before it reboots.

I think the next thing to try is just trying to get 3.0, by itself to boot and see if that is my problem.

I'm 75% sure my Tivo came with 3.0 because I remember two major upgrades since I've had it.


Any advice is alway welcome.

[devnull]

Pull the drive and look in /var/logs.

Looking through kernel and messages should show you *something*.

gary

[Chiun]

Its a start. Thanks.

[Chiun]

I don't seem to have any log files or even log directory.
Only thing in /var is /utils

This is for the 3.0 to 3.2 monte

[needo]

Originally posted by Chiun
I don't seem to have any log files or even log directory.
Only thing in /var is /utils

This is for the 3.0 to 3.2 monte

Sounds like a kernel incompatibility off the top of my head. What kernel are you using explicitly. (I need the filename it was when you downloaded it.) If you want to PM me the information that is fine.

[David Bought]

Originally posted by devnull
Pull the drive and look in /var/logs.

Looking through kernel and messages should show you *something*.

gary

He probably can't see any logs because klogd isn't running when the kernel starts up, and it probably never starts up if the box keeps rebooting itself. Also the empty /var is indicative of the real /var (/dev/hda9) never getting mounted.

If you are having problems with monte you need to start it by hand from the serial shell with the "console=2,115200 dsscon=true" kernel parameters, instead of begging for help on the forums when you have no actual symptoms to describe. Right now he's flying blind and that's not going to help him solve his problem.

[devnull]

[i]Originally posted by Chiun/i]
I don't seem to have any log files or even log directory.
Only thing in /var is /utils

Don't forget that /var/log gets mouned from /dev/hda9.

There *is* a small var dir with very few directories on your root partition (hda4 or hda7), but that gets mounted over with /dev/hda9.

gary

[DblDamage]

The rebooting problem sounds like the killinitrd never took.

I'm not sure of the differences between the SAS2 and the HDVR2, but I used the killinitrd-s2-v3.x.gz file instead of the v4.0 on my DTivo.

I noticed needo's instructions call for using v4.0.

What have you got to lose?

DblDamage

[Chiun]

Originally posted by DblDamage
The rebooting problem sounds like the killinitrd never took.

I'm not sure of the differences between the SAS2 and the HDVR2, but I used the killinitrd-s2-v3.x.gz file instead of the v4.0 on my DTivo.

I noticed needo's instructions call for using v4.0.

What have you got to lose?

DblDamage

With the 3.0 to 3.2 monte, I used the killinitrd-s2-v3.x. I could not get a successful patch of the kernel without it.

[Chiun]

One thing that just came to mind: when I do a genromfs of the kmonte.o monte and runmonte files I get this on output

0+1 files in
0+1 files out

Every other time this type of output comes up, the numbers are on the left side and the 0 is on the right. Does that mean anything?

[DblDamage]

Can you post the contents of your runmonte file? There should still be a copy in /mnt/c/img

Dbldamage

[devnull]

Originally posted by Chiun
One thing that just came to mind: when I do a genromfs of the kmonte.o monte and runmonte files I get this on output

0+1 files in
0+1 files out

Every other time this type of output comes up, the numbers are on the left side and the 0 is on the right. Does that mean anything?

This is the same output I get for my genromfs. Are you really seeing nothing in /dev/hda9?

gary

[Chiun]

Originally posted by DblDamage
Can you post the contents of your runmonte file? There should still be a copy in /mnt/c/img

Dbldamage

This is what is in my runmonte file (http://alt.org/forum/index.php?t=msg&th=74#msg_num_6)

[Chiun]

Originally posted by devnull
This is the same output I get for my genromfs. Are you really seeing nothing in /dev/hda9?

gary

My var dir. is on hda8. Me being the linux newb that I am forgot to specify that it was an ext2 partiton.

I can see the entire partition now.

Should I post the "kernel" and "messages" files?

[Chiun]

This is my kernel log.
------------------------------
Jul 29 08:57:38 (none) kernel: Configuring network...
Jul 29 08:57:38 (none) kernel: usb.c: registered new driver usbdevfs
Jul 29 08:57:38 (none) kernel: usb.c: registered new driver hub
Jul 29 08:57:38 (none) kernel: usb-ohci.c: USB OHCI at membase 0xb4000000, IRQ 5
Jul 29 08:57:38 (none) kernel: usb-ohci.c: usb-00:0d.0, PCI device 1095:0670
Jul 29 08:57:39 (none) kernel: usb.c: new USB bus registered, assigned bus number 1
Jul 29 08:57:39 (none) kernel: hub.c: USB hub found
Jul 29 08:57:39 (none) kernel: hub.c: 2 ports detected
Jul 29 08:57:39 (none) kernel: hub.c: USB new device connect on bus1/1, assigned device number 2
Jul 29 08:57:39 (none) kernel: usb.c: USB device 2 (vend/prod 0x864/0x4102) is not claimed by any active driver.
Jul 29 08:57:44 (none) kernel: usb.c: USB disconnect on device 1
Jul 29 08:57:44 (none) kernel: usb.c: USB disconnect on device 2
Jul 29 08:57:44 (none) kernel: usb.c: USB bus 1 deregistered
Jul 29 08:57:45 (none) kernel: usb.c: deregistering driver usbdevfs
Jul 29 08:57:45 (none) kernel: usb.c: deregistering driver hub
Jul 29 08:57:45 (none) kernel: Network device not found
Jul 29 08:57:45 (none) kernel: Checking for additional disk...
Jul 29 08:57:45 (none) kernel: Starting EventSwitcher...
Jul 29 08:57:46 (none) kernel: Not going to start Test service with NULL executable
Jul 29 08:57:46 (none) kernel: Not going to start Epg Manager (/tvbin/EpgManager isn't an existing executable)
Jul 29 08:57:46 (none) kernel: Not going to start thttpd (/tvbin/thttpd isn't an existing executable)
Jul 29 08:57:46 (none) kernel: Not going to start DmComponent (/tvbin/DmComponent isn't an existing executable)
Jul 29 08:57:46 (none) kernel: Not going to start Falcon (/tvbin/falcon isn't an existing executable)
Jul 29 08:57:46 (none) kernel: Not going to start IdlComponent (/tvbin/idl-component isn't an existing executable)
Jul 29 08:57:48 (none) kernel: Start fan control...
Jul 29 08:57:48 (none) kernel: Terminal temp: 71
Jul 29 08:57:48 (none) kernel: Critical temp: 62
Jul 29 08:57:48 (none) kernel: Logging temp: 60
Jul 29 08:57:48 (none) kernel: Target temp: 50
Jul 29 08:57:49 (none) kernel: Scanning for phase2 repair scripts
Jul 29 08:57:50 (none) kernel: Checking for database conversions...
Jul 29 08:57:52 (none) kernel: Checking new software installation
Jul 29 08:57:52 (none) kernel: SwSystem 3.2-01-2-1F0 is already active, nothing to do.
Jul 29 08:57:52 (none) kernel: Scanning for phase3 repair scripts
Jul 29 08:57:52 (none) kernel: Starting Services.
Jul 29 08:57:53 (none) kernel: Scanning for phase4 repair scripts
Jul 29 08:57:53 (none) kernel: rc.sysinit is complete
Jul 29 08:57:53 (none) kernel: MCP startup complete
Jul 29 08:58:07 (none) kernel: Initialize with 1 live caches
Jul 29 08:58:09 (none) kernel: Microcode version 00035
Jul 29 08:58:09 (none) kernel: Bus services started.
Jul 29 08:58:11 (none) kernel: do_page_fault() #2: sending SIGSEGV to myworld for illegal read access from
Jul 29 08:58:11 (none) kernel: 00000010 (epc == 007d4764, ra == 007d4760)
Jul 29 08:58:11 (none) kernel: Tmk Fatal Error: Thread ContextMgr event handler <142> died due to signal 11
Jul 29 08:58:11 (none) kernel: pc 0x7d4764 status 0x80019413 cause 0x000008 bva 00000000 hi 00000000 lo 0x000b00
Jul 29 08:58:11 (none) kernel: R00 0x00000000 R01 0x90019400 R02 0x00000000 R03 0x00000001
Jul 29 08:58:11 (none) kernel: R04 0x7fff7480 R05 0xfffffff1 R06 0x00000000 R07 0xfffffff1
Jul 29 08:58:11 (none) kernel: R08 0x00000001 R09 0x00000010 R10 0x00000000 R11 0x72636573
Jul 29 08:58:11 (none) kernel: R12 0x2e682900 R13 0x7fff71c0 R14 0x80f6fef0 R15 0x80a34b80
Jul 29 08:58:11 (none) kernel: R16 0x7f6f409c R17 0x7fff7520 R18 0x00000001 R19 0x00000000
Jul 29 08:58:11 (none) kernel: R20 0x00000000 R21 0x00000000 R22 0x00000000 R23 0x7f6f03a4
Jul 29 08:58:11 (none) kernel: R24 0x00000000 R25 0x007fbdb8 R26 0x00000000 R27 0x00000000
Jul 29 08:58:11 (none) kernel: R28 0x10038fc0 R29 0x7fff7450 R30 0xfffffff1 R31 0x007d4760
Jul 29 08:58:11 (none) kernel: F00 0xffffffffffffffff F02 0xffffffffffffffff
Jul 29 08:58:11 (none) kernel: F04 0xffffffffffffffff F06 0xffffffffffffffff
Jul 29 08:58:11 (none) kernel: F08 0xffffffffffffffff F10 0xffffffffffffffff
Jul 29 08:58:11 (none) kernel: F12 0xffffffffffffffff F14 0xffffffffffffffff
Jul 29 08:58:11 (none) kernel: F16 0xffffffffffffffff F18 0xffffffffffffffff
Jul 29 08:58:11 (none) kernel: F20 0xffffffffffffffff F22 0xffffffffffffffff
Jul 29 08:58:11 (none) kernel: F24 0xffffffffffffffff F26 0xffffffffffffffff
Jul 29 08:58:11 (none) kernel: F28 0xffffffffffffffff F30 0xffffffffffffffff
Jul 29 08:58:11 (none) kernel: csr 00000000 eir 0x005410

[Chiun]

This is my messages log.

Jul 29 08:57:38 (none) syslogd 1.3-3: restart.
Jul 29 08:57:49 (none) Stats: == System startup resource statistics ==
Jul 29 08:57:49 (none) Stats: ++ System build version numbers ++
Jul 29 08:57:49 (none) Stats: b-3-0-mr @81771 2002.05.08-1536 release-mips BROADBAND BROADBAND_BACKDOOR DB_CHANNEL_FROM_URI DB_SECURITY_POLICY_QUERY DCT_SERIAL DEVENV_AVR DEVENV_MIPS DEVENV_PPC DEVENV_X86 DSS_SERIAL IRBLAST MACROVISION MYWORLD_TRUE_COLOR NIELSENLOGGING PERF_LOGGER STANDALONE STRONG_CRYPTO T2KSOURCE US_CABLE_AUTO_DETECT
Jul 29 08:57:49 (none) Stats: 3.0.S7a-01-2 3.0-01-2
Jul 29 08:57:49 (none) Stats:
Jul 29 08:57:49 (none) Stats: eeprom device 0x0bf0 not supported
Jul 29 08:57:49 (none) Stats: eeprom device 0x0bf0 not supported
Jul 29 08:57:50 (none) Stats: IR version Microcode version 00035.
Jul 29 08:57:50 (none) Stats: System Serial Number: 140000080295606
Jul 29 08:57:50 (none) Stats: Linux version 2.4.4-TiVo-3.0 (build@buildmaster12) (gcc version 3.0) #11 Wed May 8 15:40:02 PDT 2002
Jul 29 08:57:50 (none) Stats: ++ Memory usage ++
Jul 29 08:57:50 (none) Stats: total: used: free: shared: buffers: cached:
Jul 29 08:57:50 (none) Stats: Mem: 24911872 22695936 2215936 0 6389760 11538432
Jul 29 08:57:50 (none) Stats: Swap: 67104768 8192 67096576
Jul 29 08:57:50 (none) Stats: MemTotal: 24328 kB
Jul 29 08:57:50 (none) Stats: MemFree: 2164 kB
Jul 29 08:57:50 (none) Stats: MemShared: 0 kB
Jul 29 08:57:50 (none) Stats: Buffers: 6240 kB
Jul 29 08:57:50 (none) Stats: Cached: 11268 kB
Jul 29 08:57:50 (none) Stats: Active: 16140 kB
Jul 29 08:57:50 (none) Stats: Inact_dirty: 180 kB
Jul 29 08:57:50 (none) Stats: Inact_clean: 1188 kB
Jul 29 08:57:50 (none) Stats: Inact_target: 388 kB
Jul 29 08:57:50 (none) Stats: HighTotal: 0 kB
Jul 29 08:57:50 (none) Stats: HighFree: 0 kB
Jul 29 08:57:50 (none) Stats: LowTotal: 24328 kB
Jul 29 08:57:50 (none) Stats: LowFree: 2164 kB
Jul 29 08:57:50 (none) Stats: SwapTotal: 65532 kB
Jul 29 08:57:50 (none) Stats: SwapFree: 65524 kB
Jul 29 08:57:50 (none) Stats: ++ CPU info ++
Jul 29 08:57:50 (none) Stats: cpu^I^I^I: MIPS
Jul 29 08:57:50 (none) Stats: cpu model^I^I: R5432 V3.0
Jul 29 08:57:50 (none) Stats: system type^I^I: TiVo UMA P0 board
Jul 29 08:57:50 (none) Stats: BogoMIPS^I^I: 201.93
Jul 29 08:57:50 (none) Stats: byteorder^I^I: big endian
Jul 29 08:57:50 (none) Stats: unaligned accesses^I: 0
Jul 29 08:57:50 (none) Stats: wait instruction^I: no
Jul 29 08:57:50 (none) Stats: microsecond timers^I: yes
Jul 29 08:57:50 (none) Stats: extra interrupt vector^I: no
Jul 29 08:57:50 (none) Stats: hardware watchpoint^I: yes
Jul 29 08:57:50 (none) Stats: spurious interrupts^I: 180
Jul 29 08:57:50 (none) Stats: ++ Module info ++
Jul 29 08:57:50 (none) Stats: brcmdrv-rb 526672 0
Jul 29 08:57:50 (none) Stats: therm 1488 0
Jul 29 08:57:50 (none) Stats: fan 1968 0
Jul 29 08:57:50 (none) Stats: ideturbo 5232 1
Jul 29 08:57:50 (none) Stats: kfirm 103344 0 (unused)
Jul 29 08:57:50 (none) Stats: tvinput 10432 0 (unused)
Jul 29 08:57:50 (none) Stats: tivoconfig 960 0 (unused)
Jul 29 08:57:50 (none) Stats: fpga 1728 0
Jul 29 08:57:50 (none) Stats: i2c 11872 0 [therm tvinput]
Jul 29 08:57:50 (none) Stats: ++ Device info ++
Jul 29 08:57:50 (none) Stats: Character devices:
Jul 29 08:57:50 (none) Stats: 1 mem
Jul 29 08:57:50 (none) Stats: 2 pty
Jul 29 08:57:50 (none) Stats: 3 ttyp
Jul 29 08:57:50 (none) Stats: 4 ttyS
Jul 29 08:57:50 (none) Stats: 5 cua
Jul 29 08:57:50 (none) Stats: 10 misc
Jul 29 08:57:50 (none) Stats: 30 bcm7030stb
Jul 29 08:57:50 (none) Stats: 90 fpga
Jul 29 08:57:50 (none) Stats: 91 tivoconfig
Jul 29 08:57:50 (none) Stats: 95 kfir
Jul 29 08:57:50 (none) Stats: 96 input
Jul 29 08:57:50 (none) Stats: 97 fan
Jul 29 08:57:50 (none) Stats: 99 i2c
Jul 29 08:57:50 (none) Stats: 108 ppp
Jul 29 08:57:50 (none) Stats: 162 raw
Jul 29 08:57:50 (none) Stats:
Jul 29 08:57:50 (none) Stats: Block devices:
Jul 29 08:57:50 (none) Stats: 1 ramdisk
Jul 29 08:57:50 (none) Stats: 3 ide0
Jul 29 08:57:50 (none) Stats: ++ Network device info ++
Jul 29 08:57:50 (none) Stats: Inter-| Receive | Transmit
Jul 29 08:57:50 (none) Stats: face |bytes packets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier compressed
Jul 29 08:57:50 (none) Stats: lo: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

[Chiun]

It seems the monte is working because at the beginning of the messages log, it says it's using 3.0 and then in the kernel log, it says its using 3.2.

What is causing that signal 11 to happen? I've been researching it but nothing much has helped. Besides the fact that it is either a software or hardware problem. ;)

[Chiun]

I went through the whole process again. But this time I did a clear and delete of 3.2 and then worked from there.

This time I got a signal -2, but it also involved the ContextMgr.

It seems to be revolving around that, but I can't pinpoint what is causing it to flop.

[devnull]

Originally posted by Chiun
Jul 29 08:58:11 (none) kernel: do_page_fault() #2: sending SIGSEGV to myworld for illegal read access from
Jul 29 08:58:11 (none) kernel: 00000010 (epc == 007d4764, ra == 007d4760)
Jul 29 08:58:11 (none) kernel: Tmk Fatal Error: Thread ContextMgr event handler <142> died due to signal 11


So this is definitely not good. I haven't seen (not that I've been looking much) anything that would lead to this.

This makes me wonder as well, especially because of the area of the log it's in (very near the top where you'd be calling monte)

Jul 29 08:57:49 (none) Stats: 3.0.S7a-01-2 3.0-01-2
Jul 29 08:57:49 (none) Stats:
Jul 29 08:57:49 (none) Stats: eeprom device 0x0bf0 not supported
Jul 29 08:57:49 (none) Stats: eeprom device 0x0bf0 not supported


I'll have to take a look at some logs when I get home.


gary

[devnull]

Originally posted by Chiun
This is what is in my runmonte file (http://alt.org/forum/index.php?t=msg&th=74#msg_num_6)

MuscleNerd's runmonte depends on bootpage. Did you remember to copy that to /sbin?

newboot=/dev/hda$(/sbin/bootpage -a /dev/hda)


gary

[MuscleNerd]

/sbin/bootpage should already be there on any normal TiVo distribution.

(More detail: There are two versions of bootpage you're likely to see; the TiVo version and one written by subuni to run on x86 boxes -- although it can also be compiled to run on TiVo.)

[devnull]

Originally posted by MuscleNerd
/sbin/bootpage should already be there on any normal TiVo distribution.

(More detail: There are two versions of bootpage you're likely to see; the TiVo version and one written by subuni to run on x86 boxes -- although it can also be compiled to run on TiVo.)

D'oh! You're right. Too early in the morning.

:eek:

gary