Adding memory to cache card

[chrishowell]

Hi,

I've been given a 512MB DIMM to use with my cache card.

How exactly do I know that this memory is working as it was 3rd hand. I've looked in the Tivo Web Plus info page but I can't see anything that says that the cache card has some memory.

Cheers,

Chris

[petestrash]

When the TiVo boot the cachecard has a splash screen that takes a couple of minutes to get though while it caches.

It will tell you how much memory it sees.

Peter.

[chrishowell]

Hi,

I'm getting a silicon dust cachecard splash screen that says:

ERROR: Driver failed to load
ERROR: No information in kernel log

[petestrash]

It's not loading any cache into memory then.

The cachecard is a little picky when it comes to which ram it works with. check the compatibilities with the Silicon Dust sites.

also look in the kernel log in /var/log. Look for messages with cachectl or cachecard in them and post back here.

Peter.

[chrishowell]

Hi,

I've tried both lots of memory that I was given. Neither of them worked and the splash screen was showing longer, numeric errors.

I was also watching the lights on the cache card and the cache light doesn't come on.

With or without the extra RAM, I have always had the errror:

"ERROR: Driver failed to load"

Please can you advise how I can view the Kernel log? I've connected to the Tivo and can view one page of the log but not sure how to see the rest.

[pjpete]

I think from memory this happened to me as well. I ended up taking off the cachecard and just giving the contacts a bit of a clean on the TiVo motherboard. I also had to do the chop of the rubber foot as well as it was buckling the board where the cachecard sits in. (chop off the lug on the rubber foot and silicon the foot to the bottom of the case so the lug does not poke through)

[Edited by Petestrash] Also, just reload the drivers again from the Install CD. I finally remembered I had to do it in order because I buggered it up first time.. [do not do this if you are using OzTiVo 1.6 or higher, it may not boot again!!]

[Edited by pjpete]I actually meant to re-image the whole thing and reload the drivers, as per the instructions below, kind of wrote it a bit wrong. But yes you are right, don't do this on the new version :)
Add the appropriate amount of Hard Disks
Re-Image the drives
Then add the network card drivers last

Not sure of any further help until you post the kernel log.

[petestrash]

you will get the "ERROR: Driver failed to load" message whenever no ram is detected, this is normal and usually only applies to the cache driver. The network driver should still load fine.

Have you checked with silicon dust that your ram is compatible?

The easist way to view the log is to use the log function of TWP. Other then that, just scroll up in telnet. or use 'cat /var/log/kernel | more' to step through it.

Peter

[chrishowell]

Doh, completely forgot to use TWP.

Messages relating to Cachecard:
Jan 1 00:00:44 (none) kernel: cachecard: driver version 20050218
Jan 1 00:00:44 (none) kernel: cachecard: updated tlb entry 2 to 1M
Jan 1 00:00:44 (none) kernel: cachecard: 0000000a 00000000 00000100 00000200
Jan 1 00:00:44 (none) kernel: cachecard: 00000300 00000400 00000500 00000600
Jan 1 00:00:44 (none) kernel: cachecard: 00000700 00000800 00000900 00000a00
Jan 1 00:00:44 (none) kernel: cachecard: 00000b00 00000c00 00000d00 00000e00
Jan 1 00:00:44 (none) kernel: cachecard: 00000f00 00001000 00001100 00001200
Jan 1 00:00:44 (none) kernel: cachecard: 00001300 00001400 00001500 00001600
Jan 1 00:00:44 (none) kernel: cachecard: 00001700 00001800 00001900 00001a00
Jan 1 00:00:44 (none) kernel: cachecard: 00001b00 00001c00 00001d00 00001e00
Jan 1 00:00:44 (none) kernel: cachecard: 00001f00 00002000 00002100 00002200
Jan 1 00:00:44 (none) kernel: cachecard: 00002300 00002400 00002500 00002600
Jan 1 00:00:44 (none) kernel: cachecard: 00002700 00002800 00002900 00002a00
Jan 1 00:00:44 (none) kernel: cachecard: 00002b00 00002c00 00002d00 00002e00
Jan 1 00:00:44 (none) kernel: cachecard: 00002f00 00003000 00003100 00003200
Jan 1 00:00:44 (none) kernel: cachecard: 00003300 00003400 00003500 00003600
Jan 1 00:00:44 (none) kernel: cachecard: 00003700 00003800 00003900 00003a00
Jan 1 00:00:44 (none) kernel: cachecard: 00003b00 00003c00 00003d00 00003e00
Jan 1 00:00:44 (none) kernel: cachecard: 0000000a 00004000 00004100 00004200
Jan 1 00:00:44 (none) kernel: cachecard: 00004300 00004400 00004500 00004600
Jan 1 00:00:44 (none) kernel: cachecard: 00004700 00004800 00004900 00004a00
Jan 1 00:00:44 (none) kernel: cachecard: 00004b00 00004c00 00004d00 00004e00
Jan 1 00:00:44 (none) kernel: cachecard: 00004f00 00005000 00005100 00005200
Jan 1 00:00:44 (none) kernel: cachecard: 00005300 00005400 00005500 00005600
Jan 1 00:00:44 (none) kernel: cachecard: 00005700 00005800 00005900 00005a00
Jan 1 00:00:44 (none) kernel: cachecard: 00005b00 00005c00 00005d00 00005e00
Jan 1 00:00:44 (none) kernel: cachecard: 00005f00 00006000 00006100 00006200
May 18 13:38:10 (none) kernel: cachecard: 00006300 00006400 00006500 00006600
May 18 13:38:10 (none) kernel: cachecard: 00006700 00006800 00006900 00006a00
May 18 13:38:10 (none) kernel: cachecard: 00006b00 00006c00 00006d00 00006e00
May 18 13:38:10 (none) kernel: cachecard: 00006f00 00007000 00007100 00007200
May 18 13:38:10 (none) kernel: cachecard: 00007300 00007400 00007500 00007600
May 18 13:38:10 (none) kernel: cachecard: 00007700 00007800 00007900 00007a00
May 18 13:38:10 (none) kernel: cachecard: 00007b00 00007c00 00007d00 00007e00
May 18 13:38:10 (none) kernel: cachecard: error: cachecard/sram not found!
May 18 13:38:10 (none) kernel: /lib/modules/cachecard.o: init_module: Device or resource busy
May 18 13:38:10 (none) kernel: Starting Cachecard
Jan 1 00:00:45 (none) kernel: cachecard: driver version 20050218
Jan 1 00:00:45 (none) kernel: cachecard: updated tlb entry 2 to 1M
Jan 1 00:00:45 (none) kernel: cachecard: 0000000a 00000000 00000100 00000200
Jan 1 00:00:45 (none) kernel: cachecard: 00000300 00000400 00000500 00000600
Jan 1 00:00:45 (none) kernel: cachecard: 00000700 00000800 00000900 00000a00
Jan 1 00:00:45 (none) kernel: cachecard: 00000b00 00000c00 00000d00 00000e00
Jan 1 00:00:45 (none) kernel: cachecard: 00000f00 00001000 00001100 00001200
Jan 1 00:00:45 (none) kernel: cachecard: 00001300 00001400 00001500 00001600
Jan 1 00:00:45 (none) kernel: cachecard: 00001700 00001800 00001900 00001a00
Jan 1 00:00:45 (none) kernel: cachecard: 00001b00 00001c00 00001d00 00001e00
Jan 1 00:00:45 (none) kernel: cachecard: 00001f00 00002000 00002100 00002200
Jan 1 00:00:45 (none) kernel: cachecard: 00002300 00002400 00002500 00002600
Jan 1 00:00:45 (none) kernel: cachecard: 00002700 00002800 00002900 00002a00
Jan 1 00:00:45 (none) kernel: cachecard: 00002b00 00002c00 00002d00 00002e00
Jan 1 00:00:45 (none) kernel: cachecard: 00002f00 00003000 00003100 00003200
Jan 1 00:00:45 (none) kernel: cachecard: 00003300 00003400 00003500 00003600
Jan 1 00:00:45 (none) kernel: cachecard: 00003700 00003800 00003900 00003a00
Jan 1 00:00:45 (none) kernel: cachecard: 00003b00 00003c00 00003d00 00003e00
Jan 1 00:00:45 (none) kernel: cachecard: 0000000a 00004000 00004100 00004200
Jan 1 00:00:45 (none) kernel: cachecard: 00004300 00004400 00004500 00004600
Jan 1 00:00:45 (none) kernel: cachecard: 00004700 00004800 00004900 00004a00
Jan 1 00:00:45 (none) kernel: cachecard: 00004b00 00004c00 00004d00 00004e00
Jan 1 00:00:45 (none) kernel: cachecard: 00004f00 00005000 00005100 00005200
Jan 1 00:00:45 (none) kernel: cachecard: 00005300 00005400 00005500 00005600
Jan 1 00:00:45 (none) kernel: cachecard: 00005700 00005800 00005900 00005a00
Jan 1 00:00:45 (none) kernel: cachecard: 00005b00 00005c00 00005d00 00005e00
Jan 1 00:00:45 (none) kernel: cachecard: 00005f00 00006000 00006100 00006200
Jan 1 00:00:45 (none) kernel: cachecard: 00006300 00006400 00006500 00006600
Jan 1 00:00:45 (none) kernel: cachecard: 00006700 00006800 00006900 00006a00
Jan 1 00:00:45 (none) kernel: cachecard: 00006b00 00006c00 00006d00 00006e00
Jan 1 00:00:45 (none) kernel: cachecard: 00006f00 00007000 00007100 00007200
Jan 1 00:00:45 (none) kernel: cachecard: 00007300 00007400 00007500 00007600
Jan 1 00:00:45 (none) kernel: cachecard: 00007700 00007800 00007900 00007a00
Jan 1 00:00:45 (none) kernel: cachecard: 00007b00 00007c00 00007d00 00007e00
Jan 1 00:00:45 (none) kernel: cachecard: error: cachecard/sram not found!
Jan 1 00:00:45 (none) kernel: /lib/modules/cachecard.o: init_module: Device or resource busy
May 18 13:40:50 (none) kernel: Starting Cachecard
Jan 1 00:00:45 (none) kernel: cachecard: driver version 20050218
Jan 1 00:00:45 (none) kernel: cachecard: updated tlb entry 2 to 1M
Jan 1 00:00:45 (none) kernel: cachecard: 0000000a 0000000a 0000000a 0000000a
Jan 1 00:00:45 (none) kernel: cachecard: error: cachecard/sram not found!
Jan 1 00:00:45 (none) kernel: /lib/modules/cachecard.o: init_module: Device or resource busy
Jan 1 00:00:45 (none) kernel: Starting Cachecard

Messages for cachectl:

May 18 13:38:10 (none) kernel: cachectl: Driver version: xxxxxxxx/20050218
May 18 13:38:10 (none) kernel: cachectl: ERROR: Driver failed to load
May 18 13:38:10 (none) kernel: cachectl: ERROR: No information in kernel log
Jan 1 00:00:45 (none) kernel: cachectl: Driver version: xxxxxxxx/20050218
Jan 1 00:00:45 (none) kernel: cachectl: ERROR: Driver failed to load
Jan 1 00:00:45 (none) kernel: cachectl: Driver version: xxxxxxxx/20050218
Jan 1 00:00:45 (none) kernel: cachectl: ERROR: Driver failed to load

[petestrash]

It still looks to me that it doesn't like your Ram.

Your driver is the latest version.

A good kernel log should look something like this:

May 17 12:54:36 (none) kernel: Splash the screen...
May 17 12:54:36 (none) kernel: cachecard: driver version 20050218
May 17 12:54:36 (none) kernel: cachecard: updated tlb entry 2 to 1M
May 17 12:54:36 (none) kernel: cachecard: found 2 chip groups
May 17 12:54:36 (none) kernel: cachecard: found 4 banks
May 17 12:54:36 (none) kernel: cachecard: found 8192 rows
May 17 12:54:36 (none) kernel: cachecard: found 1024 cols
May 17 12:54:36 (none) kernel: cachecard: memory found: 512 MB
May 17 12:54:36 (none) kernel: cachecard: csum table size = 4MB
May 17 12:54:36 (none) kernel: cachecard: sdram cache size = 508MB
May 17 12:54:36 (none) kernel: cachecard: mappable size = 1016MB
May 17 12:54:36 (none) kernel: cachecard: driver loaded successfully
May 17 12:54:36 (none) kernel: cachectl: Driver version: 20050218/20050218
May 17 12:54:36 (none) kernel: cachectl: 512MB DIMM detected
May 17 12:54:36 (none) kernel: cachectl: Found partition 0:10 (512MB)
May 17 12:54:36 (none) kernel: cachectl: Found partition 0:12 (0MB)
May 17 12:54:36 (none) kernel: cachectl: Found partition 1:2 (0MB)
May 17 12:54:36 (none) kernel: cachectl: 513MB database detected
May 17 12:54:36 (none) kernel: cachectl: Writing.... 0% .... 25% .... 50% .... 75% .... 100% cachectl:
May 17 12:54:36 (none) kernel: cachectl: Verifying... 0% .... 25% .... 50% .... 75% .... 100% cachectl:
May 17 12:54:36 (none) kernel: cachecard: zone[0] = 0:10 (512MB)
May 17 12:54:36 (none) kernel: cachecard: zone[1] = 0:12 (0MB)
May 17 12:54:36 (none) kernel: cachecard: zone[2] = 1:2 (0MB)
May 17 12:54:36 (none) kernel: cachectl: Caching.... 0% .... 25% .... 50% .... 75% .... 100% cachectl:

I still think you are using either incompatible or faulty ram.

For the third time I will suggest "Have you checked with silicon dust that your ram is compatible?"

Peter

[chrishowell]

For the third time I will suggest "Have you checked with silicon dust that your ram is compatible?"

Peter

Sorry, for not answering. Yes, I have checked against the specification. I will check again.

[petestrash]

And what did it say about your style of ram?

Also what version Cachecard are you using? Before V2.2 cards are even less compatible.

[petestrash]

You might also want to try logging a fault ticket with silicon dust (http://www.silicondust.com/wiki/tickets). Include your kernel log messages.

Peter

[chrishowell]

And what did it say about your style of ram?

It says:

Cachecard compatibility
The cachecard supports both 32Mx8 and 64Mx4 based DIMMs.
All 32Mx8 based DIMMs will work.
All 64Mx4 based DIMMs the follow the JEDEC standard for DQM wiring will work (99% of 64Mx4 based DIMMs).

The two sets of RAM I was given appear to comply with this so I can only assume that they are faulty. I'm taking them back today.


Also what version Cachecard are you using? Before V2.2 cards are even less compatible.

I have v2.2

[petestrash]

They used to maintain a list of known sticks that did not work, but this seems to have disappeared from the site.

It's unlikely you have 2 faulty sticks, try opening a ticket first.

Peter.

[chrishowell]

They used to maintain a list of known sticks that did not work, but this seems to have disappeared from the site.

It's unlikely you have 2 faulty sticks, try opening a ticket first.

Peter.

I could only find some very generic info in the FAQ and what I posted before was from their forum. They referred to JEDEC information that they had but I can't access that site to get the info.

I've logged a case but the ticket system has no reference to CacheCard in any category - do they still support it?

[petestrash]

A lot of the Support info that used to be there is not on the new site. They have even purged selected posts.

The FAQ on 9th tee is basically the same as years ago, with promises of more answer to come, but they never did.

The cachecard is still sold by 9th tee and your are still supposed to contact silicon dust for support. But I think Jaffa is more interested in HDhomerun these days.

I know when I got my first V1.2 Cachecard I had to try a few different sticks before I found one that worked. Most of these issues should have been resolved by v2.2.

Unforurtunately I don't really have much else to offer. As pjpete said, make sure that the card is fully seated. It can seem it is fully seated, but can actually go further.

As well as cutting the pin for the foot, I also untwist the board supports so it can be lifted when inserting the card.

Peter

[chrishowell]

Hi,

I did get a response from support. This is what they said:

"The log indicates that the DIMM does not support CL2 operation.

Usually CL2 vs CL3 does not matter as DIMMs that say CL3 still support CL2, just not at 133MHz. The Tivo FSB is slower so running a CL3 rated DIMM in CL2 mode is not an issue.

It is rare but some CL3 DIMMs do not support CL2 operation at all. This is the problem you are seeing here."

I'll talk to the person who supplied the RAM and try and get some CL3 from him.

Cheers,

Chris

[petestrash]

I'm glad you received a sensible response.

Hopefully you can sort it out with your supplier.

To clarify Jaffa's response, you currently have CL3 (slower) which does not support CL2 (Faster) even at TiVo's slow 27mhz.

You need either:
1. Any PC66/100/133 CL2 which supports a 27mhz Front Side Bus
2. Any PC133 CL3 that supports CL2 at a Front Side Bus Speed of 27mhz

Peter.