Mk2 not recognizing 4MB upgrade

Posted by: Glen_L

Mk2 not recognizing 4MB upgrade - 13/09/2004 19:38

Since Mark brought it up here, I guess now is as good a time as any to mention my Mk2 is not recognizing the extra 4 MB Stu installed several months ago.

I honestly don't need the extra memory; I'm still running the original 10GB hard drive . But I recently installed emphatic and having some extra cache would be nice. The boot log and Ctrl-T memory diagnostic results are below, let me know what else is required.

Edit to add: running 2.00 final developer and Hijack v410.

Code:
If there is anyone present who wants to upgrade the flash, let them speak now,

hda: hda1 < hda5 hda6 > hda2 hda3 hda4
or forever hold their peace...it seems not. Let fly the Penguins of Linux!
RAMDISK: Loading 320 blocks [1 disk] into ram disk... done.

e000 v1.04
Copying kernel...
Calling linux kernel...time reached, running e
Uncompressing Linux..................................... done, booting the kerne
VFS: Mounted root (ext2 filesystem).
em
l.-p
Linux version 2.2.17-rmk5-np17-empeg52-hijack-v410 ([email protected]) (gcc versioning to unmount old root ... okay
2.95.3 20010315 (release)) #2 We
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.iserfs but got error 19
empeg-car player (hardware revision 7, serial number 90000980) 12MB DRAMd to mount /dev/hdc4 but got error 6
Command line: mem=12mrtitions (possibly al
Calibrating delay loop... 207.67 BogoMIPS
Remounting first
Memory: 10952k/12M available (984k code, 20k reserved, 328k data, 4k init)ting second music partition read-only
Dentry hash table entries: 2048 (order 2, 16k)
Press 'q' now to go into development mode
Buffer cache hash table entries: 16384 (order 4, 64k)
hijack: remove
Based upon Swansea University Computer Society NET3.039
khttpd: listening on
NET4: Linux TCP/IP 1.0 for NET4.0
kftpd: listening on port 21
IP Protocols: ICMP, UDP, TCPg non-standard cache size 74
TCP: Hash tables configured (ehash 16384 bhash 16384)
player.cpp : 385:empeg-car 2.00 2
IrDA (tm) Protocols for Linux-2.2 (Dag Brattli)
Prolux 4 empeg car - 2.1434 Mar
Starting kswapd v 1.5
SA1100 serial driver version 4.27 with no serial options enabled (priority -1)
e2fsc
ttyS00 at 0xf8010000 (irq = 15) is a SA1100 UART
ttyS01 at 0xf8050000 (irq = 17) is a SA1100 UAR
empeg dsp audio initialised
Starting pl
empeg dsp mixer initialised: US/Pacific
empeg dsp initialisedting config.ini
empeg audio-in initialised, CS4231A revision a0che size 74 (adjustment 10)
empeg remote control/panel button initialised. : 385:empeg-car 2.00 2003/04/01.
empeg usb initialised, PDIUSBD12 id 1012Prolux 4 empeg car - 2.1434 Mar 26 2003
empeg state support initialised 0089/88c1 (save to d0004680).
If there is anyone present who wants to upgrade the
empeg RDS driver initialised
empeg power-pic driver initialised (first boot)

Probing primary interface...
Calling linu
hda: IBM-DJSA-210, ATA DISK drive
Uncompressing Linux.............
hda: IBM-DJSA-210, ATA DISK driveting the kerne
hda: IBM-DJSA-210, ATA DISK drive
l.

hda: IBM-DJSA-210, ATA DISK driveeg52-hijack-v410 ([email protected])
hda: IBM-DJSA-210, ATA DISK drive
hda: IBM-DJSA-210, ATA DISK drive010315 (release)) #2 Wed Aug 4 00
ide0 at 0x000-0x007,0x038 on irq 6
hda: IBM-DJSA-210, 9590MB w/384kB Cache, CHS=19485/16/63
Checking for extra DRA
empeg-flash driver initialized0000: wrote ffffffff, read ef1
smc chip id/revision 0x3349
NetWinder
smc9194.c:v0.12 03/06/96 by Erik Stahlman ([email protected]
RAMDISK: ext2 filesystem found at block 0served, 328k data, 4k init)
RAMDISK: Loading 320 blocks [1 disk] into ram disk... done.
Dentry hash table entries: 2048 (order 2, 16k)
EXT2-fs warning: checktime reached, running e2fsck is recommended: 16384 (order 4, 64k)
VFS: Mounted root (ext2 filesystem).ies: 4096 (order 2, 16k)
empeg-pump v0.03 (19980601)
Mounting proc
Mounting first music partition
Tried to mount /dev/hda4 as reiserfs but got error 19
Mounting second music partition
Tried to mount /dev/hdc4 but got error 6
Error mounting partitions (possibly already mounted)
Remounting first music partition read-only
Remounting second music partition read-only
No secondary hard disk
Press 'q' now to go into development mode. You Have Zero Seconds To ComStarting
player
Timezone: US/Pacific
Hijack: intercepting config.ini

opening display...
hijack: removed menu entry: "Serial Port Assignment"
khttpd: listening on port 80
kftpd: listening on port 21
Using non-standard cache size 74 (adjustment 10)
emphatic v2.04 (built Aug 17 2004 21:05:49) running as pid 12
player.cpp : 385:empeg-car 2.00 2003/04/01.
Prolux 4 empeg car - 2.1434 Mar 26 2003
Vcb: 0x404ad000



Also, here is the memory test diagnostic results:

Code:
empeg-car bootstrap v1.00 20000601 ([email protected])

Probing primary interface...
If there is anyone present who wants to upgrade the flash, let them speak now,
hda: IBM-DJSA-210, ATA DISK drive
0140 testing ic 4 (4-7mb, high word)
0150 testing ic 19 (8-11mb, low word)
0160 testing ic 32 (8-11mb, high word)
01f0 ram test done
0200 ide detect
0210 command issued
0220 drive id IBM-DJSA-210
02f0 ide ok
0300 dsp/i2c test
03f0 dsp/i2c ok
0400 temperature detect
0410 temperature is 38
04f0 temperature ok
0500 usb detect
0510 usb rev 1012
05f0 usb ok
0600 ethernet detect
0610 ethernet rev 334b
06f0 ethernet ok
0700 cs4231 detect
0710 cs4231 rev a0
07f0 cs4231 ok
00f0 tests complete

Posted by: schofiel

Re: Mk2 not recognizing 4MB upgrade - 13/09/2004 20:13

The standard RAM test will only test out the standard amount of RAMon teh machine: it does not look to see if there is more.

Also, the standard V2 kernel/player app will only enable the standard amount of RAM after boot. You should get hold of 2.1 which will enable the new stuff.

You should install HiJack (about 400-odd) and get to the HiJack menu. Have a look at the Vital Signs entry and it will tell you how much it finds.
Posted by: pgrzelak

Re: Mk2 not recognizing 4MB upgrade - 13/09/2004 20:17

It was hijack 410, but that may not have code to support the Mark2. Try 413. Also, your boot log did not have any mention of extra memory tests - that is why I suspect it was never checked.
Posted by: Glen_L

Re: Mk2 not recognizing 4MB upgrade - 13/09/2004 20:29

Wow, thanks for the fast replies. Okay, I just upgraded to V413 and checked the vitals, it says 12MB there. I guess I need the new 2.01 image to be sure. Anyone mind sharing it or is there a moratorium on posting it as well as v3a8?
Posted by: mlord

Re: Mk2 not recognizing 4MB upgrade - 13/09/2004 21:23

Hi, I'm the Hijack dude.

The boot log you posted is missing this message:

Checking for extra DRAM:

I wonder where it has gotten to.. it really should be there if you are using one of my Hijack kernels (and the version info said you were, but..).

Post a new v413 log for us. Thanks.
Posted by: genixia

Re: Mk2 not recognizing 4MB upgrade - 13/09/2004 21:51

Quote:
Checking for extra DRA
empeg-flash driver initialized0000: wrote ffffffff, read ef1


It was there, but got 'hyperterminaled'. It looks like at least one of the chips isn't happy, for whatever reason.

Edit: Fixed a broken end-quote tag.
Posted by: Glen_L

Re: Mk2 not recognizing 4MB upgrade - 13/09/2004 23:24

Indeed it did get "hyperterminaled". I installed Teraterm 2.3 and got this:

Code:
If there is anyone present who wants to upgrade the flash, let them speak now,
or forever hold their peace...it seems not. Let fly the Penguins of Linux!

e000 v1.04
Copying kernel...
Calling linux kernel...
Uncompressing Linux..................................... done, booting the kerne
l.
Linux version 2.2.17-rmk5-np17-empeg52-hijack-v413 ([email protected]) (gcc version
2.95.3 20010315 (release)) #2 Tue Aug 17 18:05:30 EDT 2004
Processor: Intel StrongARM-1100 revision 11
Checking for extra DRAM:
c0c00000: wrote ffffffff, read ef1ba9f0
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.
empeg-car player (hardware revision 7, serial number 90000980) 12MB DRAM
Command line: mem=12m
Calibrating delay loop... 207.67 BogoMIPS
Memory: 10952k/12M available (984k code, 20k reserved, 328k data, 4k init)
Dentry hash table entries: 2048 (order 2, 16k)
Buffer cache hash table entries: 16384 (order 4, 64k)
Page cache hash table entries: 4096 (order 2, 16k)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
TCP: Hash tables configured (ehash 16384 bhash 16384)
IrDA (tm) Protocols for Linux-2.2 (Dag Brattli)
Starting kswapd v 1.5
SA1100 serial driver version 4.27 with no serial options enabled
ttyS00 at 0xf8010000 (irq = 15) is a SA1100 UART
ttyS01 at 0xf8050000 (irq = 17) is a SA1100 UART
ttyS02 at 0xf8030000 (irq = 16) is a SA1100 UART
Signature is 67706d65 'empg'
Tuner: loopback=1, ID=-1
Scheduling custom logo.
empeg display initialised.
empeg dsp audio initialised
empeg dsp mixer initialised
empeg dsp initialised
empeg audio-in initialised, CS4231A revision a0
empeg remote control/panel button initialised.
empeg usb initialised, PDIUSBD12 id 1012
empeg state support initialised 0089/88c1 (save to d0004980).
empeg RDS driver initialised
empeg power-pic driver initialised (first boot)
RAM disk driver initialized: 16 RAM disks of 4096K size
empeg single channel IDE
Probing primary interface...
hda: IBM-DJSA-210, ATA DISK drive
hda: IBM-DJSA-210, ATA DISK drive
hda: IBM-DJSA-210, ATA DISK drive
hda: IBM-DJSA-210, ATA DISK drive
hda: IBM-DJSA-210, ATA DISK drive
hda: IBM-DJSA-210, ATA DISK drive
ide0 at 0x000-0x007,0x038 on irq 6
hda: IBM-DJSA-210, 9590MB w/384kB Cache, CHS=19485/16/63
empeg-flash driver initialized
smc chip id/revision 0x3349
smc9194.c:v0.12 03/06/96 by Erik Stahlman ([email protected])

SMC9194: SMC91C94(r:9) at 0x4008000 IRQ:7 INTF:TP MEM:6144b MAC 00:02:d7:12:03:d
4
Partition check:
hda: hda1 < hda5 hda6 > hda2 hda3 hda4
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 320 blocks [1 disk] into ram disk... done.
EXT2-fs warning: checktime reached, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
empeg-pump v0.03 (19980601)
Press Ctrl-A to enter pump...ԕjչѕɽсɁѕɕ)5chang
e_root: old root has d_count=1
Trying to unmount old root ... okay
Freeing unused kernel memory: 4k init
empeg init 0.8
I see this is a developer image!
Mounting proc
Mounting first music partition
Tried to mount /dev/hda4 as reiserfs but got error 19
Mounting second music partition
Tried to mount /dev/hdc4 but got error 6
Error mounting partitions (possibly already mounted)
Remounting first music partition read-only
Remounting second music partition read-only
No secondary hard disk
Press 'q' now to go into development mode. You Have Zero Seconds To ComStarting
player
Timezone: US/Pacific
Hijack: intercepting config.ini

opening display...
hijack: removed menu entry: "Serial Port Assignment"
khttpd: listening on port 80
kftpd: listening on port 21
Using non-standard cache size 74 (adjustment 10)
emphatic v2.04 (built Aug 17 2004 21:05:49) running as pid 12
player.cpp : 385:empeg-car 2.00 2003/04/01.
Prolux 4 empeg car - 2.1434 Mar 26 2003
Vcb: 0x404ad000

Posted by: wfaulk

Re: Mk2 not recognizing 4MB upgrade - 13/09/2004 23:26

I think a better term would be "hyperterminated".
Posted by: Glen_L

Re: Mk2 not recognizing 4MB upgrade - 13/09/2004 23:45

As genixia pointed out, from

Checking for extra DRAM:
c0c00000: wrote ffffffff, read ef1ba9f0

it seems it is not properly recognizing the 12MB-16MB block. I'm thinking there are a few possibilities:

- The installed memory was bad to begin with. Hugo, who sent Stu the chips to install, mentioned somewhere that they had a high fail rate. I'm not sure if they were tested pre-install.

- Something might have gone wrong with the install. It was the first (only?) Mk2 upgrade that Stu had done. He posted a pic here, and more details are scattered about that lengthy thread.

- I don't remember reading about any other Mk2 memory upgrade successes, so maybe there is something else that still needs to be worked out for Mk2s specifically in Hijack. I know it's a long shot, but it's what I'm hoping for given the alternative of being out my player for a week or two with the shipping turnaround to Stu.

If anyone has any other ideas, I'd appreciate it...
Posted by: SE_Sport_Driver

Re: Mk2 not recognizing 4MB upgrade - 13/09/2004 23:49

Quote:
- I don't remember reading about any other Mk2 memory upgrade successes, so maybe there is something else that still needs to be worked out for Mk2s specifically in Hijack. I know it's a long shot, but it's what I'm hoping for given the alternative of being out my player for a week or two with the shipping turnaround to Stu.


I think Paul Grzelak's player is a Mk2.
Posted by: mlord

Re: Mk2 not recognizing 4MB upgrade - 14/09/2004 00:19

Mmm.. the photo shows the correct chip select -- Stu had that backwards at first, but the photo you linked to shows ping 121 == RAS3 == correct for Mk2.

I doubt that a bad chip is causing this.. usually only one bit would be incorrect on a bad chip, whereas here it looks like none of the data lines are being driven on the failed test. Mmm..

In any event, don't send it back to Stu -- it really needs to go to genixia or myself, who have the capability to debug the issue more thoroughly. I'm just a tad way too busy right now, but perhaps in October..

Cheers
Posted by: genixia

Re: Mk2 not recognizing 4MB upgrade - 14/09/2004 00:56

Quote:
I think Paul Grzelak's player is a Mk2.

No, all of Paul's players that have been upgraded are Mk2a. I'm not aware of any successfully upgraded Mk2 players yet. I suppose it's entirely possible that someone has one but has kept quiet about it (and I guess we should ping Hugo since he has a Mk2), but it AFAIK this is unchartered territory still.
Posted by: Glen_L

Re: Mk2 not recognizing 4MB upgrade - 14/09/2004 01:02

Thanks Mark, there's no big rush, it's actually doing pretty well with only 12MB. I'll ask genixia about taking a look after the Cincinnati meet. If he's not up to it you can take a shot in October when you have time.

Thanks again...
Posted by: genixia

Re: Mk2 not recognizing 4MB upgrade - 14/09/2004 01:20

Quote:
As genixia pointed out, from

Checking for extra DRAM:
c0c00000: wrote ffffffff, read ef1ba9f0

it seems it is not properly recognizing the 12MB-16MB block. I'm thinking there are a few possibilities:

- The installed memory was bad to begin with. Hugo, who sent Stu the chips to install, mentioned somewhere that they had a high fail rate. I'm not sure if they were tested pre-install.

- Something might have gone wrong with the install. It was the first (only?) Mk2 upgrade that Stu had done. He posted a pic here, and more details are scattered about that lengthy thread.

- I don't remember reading about any other Mk2 memory upgrade successes, so maybe there is something else that still needs to be worked out for Mk2s specifically in Hijack. I know it's a long shot, but it's what I'm hoping for given the alternative of being out my player for a week or two with the shipping turnaround to Stu.

If anyone has any other ideas, I'd appreciate it...


No, you've pretty much covered the bases.

At first glance, the error seems to indicate a problem with the RAS line, although as Mark has noted, the photo looks correct. If the RAS line came loose at the CPU then I'd expect to see this kind of error. Basically neither chip appears to be answering the CPU. It would be unusual for that to be caused by other soldering issues as it would require identical soldering defects on each chip.

The high memory failure rate does concern me. ISTR Hugo quoting something like 1 in 4 failure rate. That would give a 1/16 chance of a Mark1 upgrade having both chips be bad, and a 1/2 chance that one of them is bad. (And for a Mk1 upgrade, a 1/1 chance that one is bad). I hope that Hugo was exaggerating! Of course, it is unlikely that a bad chip would catastrophically fail (which would be required for this failure mode), so it probably isn't this.

(As an aside, this causes concern for Mk1/Mk2 upgrades in general.)

And until we see the first successful Mk2 upgrade reported, we cannot totally rule out software either. However, it does look like it's doing the right thing at this stage. If it was detecting the RAM fine and then falling over, or failing at some nonsensical address then it would be suspect, but c0c00000 is exactly right for the other failure modes...
Posted by: genixia

Re: Mk2 not recognizing 4MB upgrade - 14/09/2004 01:25

Quote:
hyperterminated.


Posted by: Glen_L

Re: Mk2 not recognizing 4MB upgrade - 14/09/2004 02:38

Quote:
The high memory failure rate does concern me. ISTR Hugo quoting something like 1 in 4 failure rate.

Curiosity got the better of me and I dug up the post where Hugo said the failure rate was only about 1/50. I thought it was much higher too; it seems the memory on the chips is more reliable than ours
Posted by: genixia

Re: Mk2 not recognizing 4MB upgrade - 14/09/2004 02:55

LOL. Too true.

I guess that means the odds of both chips failing (in a minor way) is about 1 in 2500, so that pretty much eliminates that being the cause of your problem.

My money is on the RAS wire.
Posted by: Glen_L

Re: Mk2 not recognizing 4MB upgrade - 14/09/2004 04:22

Okay, one other thing I'd like to rule out. In that thread is another post by Hugo with a downloadable e0000 ROM file. Apparently this was required at the time to enable the then-unused memory banks. I assumed this fix was rolled into or superseded by newer versions of Hijack, but then noticed that Hugo planned to put the fix into future releases (ie 2.01?).

I've downloaded and attempted to install it via FTP. My FTP-fu is admittedly weak and I can't tell whether the file was updated or not. The file date (before and after) remained the same, although the command executed successfully. Here's what transpired:

Code:
Connected to 192.168.2.103.
220 Connected.
User (192.168.2.103:(none)):
230 Login okay.
ftp> cd proc
250 "/proc" directory changed
ftp> dir *e000*
200 Okay.
150 Opening data connection.
brw------- 1 0 0 60, 7 Sep 14 05:56 flash_0e000
total 0
226 Okay.
ftp: 78 bytes received in 0.00Seconds 78000.00Kbytes/sec.
ftp> quote site rw
200 Okay.
ftp> put c:\205177-e000.rom flash_0e000
200 Okay.
150 Opening data connection.
226 Okay.
ftp: 1692 bytes sent in 0.00Seconds 1692000.00Kbytes/sec.
ftp> quote site ro
200 Okay.



After rebooting and looking at the boot log the memory write at 0c0000 still failed. I'm really not convinced that the file was overwritten though. I wish I could install the 2.01 developer image to rule this out. Which one of the blue guys should I ask about that?
Posted by: Glen_L

Re: Mk2 not recognizing 4MB upgrade - 14/09/2004 06:33

Well shoot...disregard all this, I finished looking through the big memory upgrade thread and it seems the e000 ROM upgrade was indeed obsoleted by Hijack from v38x on. I guess the RAS line is most likely borked after all.
Posted by: mlord

Re: Mk2 not recognizing 4MB upgrade - 14/09/2004 11:21

Yeah, it's gotta be either the RAS line or software. Probably software, I think. I never did manage to get a cache_flush() and tlb_flush() call to work during the memory probing -- those might be necessary for Mk1/Mk2 probing to work. The Mk2a probing works right now, but breaks whenever I try to tweak it. Really gotta flush them caches to know for sure. Somebody has to look up in the Sa1100 manual for how to do it correctly.

Cheers
Posted by: Glen_L

Re: Mk2 not recognizing 4MB upgrade - 14/09/2004 11:52

Do you think installing 2.01 would make a difference? From what I've read, the only changes from 2.00 are extra-memory related...
Posted by: genixia

Re: Mk2 not recognizing 4MB upgrade - 14/09/2004 12:32

No. The two changes in v2.01 are;
  1. Kernel changes to support extra memory. These all came from hijack anyway.
  2. Player software changes to support extra memory. The player software isn't even loaded at this point.
Posted by: JBjorgen

Re: Mk2 not recognizing 4MB upgrade - 14/09/2004 12:35

I'll be bringing my Mk2 and memory (if I receive it from Stu in time) to the Cincinnati meet, so if genixia is willing, we may be able to come up with an upgraded player by then (or at least confirm that it isn't working.)
Posted by: Glen_L

Re: Mk2 not recognizing 4MB upgrade - 14/09/2004 12:49

Great, hope everything works out for you so we'll know one way or the other whether it's a software issue for all Mk2's or a hardware issue for just me.

Thanks again everyone.
Posted by: maczrool

Re: Mk2 not recognizing 4MB upgrade - 15/09/2004 00:06

When are you leaving? We shipped it Monday.

Stu
Posted by: JBjorgen

Re: Mk2 not recognizing 4MB upgrade - 15/09/2004 11:31

23rd. Should be here in plenty of time.
Posted by: Daria

nothing about Mk2s - 15/09/2004 12:54

So does the birthday cake icon mean I should be wishing you happy birthday?
Posted by: genixia

Re: nothing about Mk2s - 15/09/2004 13:19

Yeah, I've still got the icon with multiple candles so I guess that means I should celebrate!
Posted by: genixia

Re: Mk2 not recognizing 4MB upgrade - 08/10/2004 13:48

16MB has been confirmed as working on Mk2 players with hijack v413. It looks like a problem with your install.

Check that you connected the RAS wire to the correct pin on the CPU. It looks like neither of the chips is answering. Remember that on a Mk2 you need to use RAS3 and not RAS1.
Posted by: Glen_L

Re: Mk2 not recognizing 4MB upgrade - 09/10/2004 01:34

Thanks for the reminder. Unfortunately, I may have to put this on the back burner for a bit as I'm helping a friend move and have two birthday parties to attend this weekend.

But, when I have time, I should be able to take a macro shot of the area in question. I'll post it up in this thread when the time comes and figure out where to go from there.
Posted by: Glen_L

Re: Mk2 not recognizing 4MB upgrade - 09/10/2004 05:14

Well, it's been a slow night at work, so with the help of the FAQ I opened up my player and took out the drive tray for a peek at the hardware.

It looks exactly as the picture I linked to earlier in this thread. I thought maybe the wire had come loose from the CPU, but it hasn't. I can't see where or how well the other ends were soldered through the epoxy. Stu mentioned in the old thread that he used Pin 121(RAS3) on the CPU and pin 18 of the RAM chips. Mark confirmed from the picture that pin 121 was used. Is pin 18 correct for Mk2 RAM?
Posted by: mdavey

Re: Mk2 not recognizing 4MB upgrade - 09/10/2004 07:18

Quote:

Stu mentioned in the old thread that he used Pin 121(RAS3) on the CPU and pin 18 of the RAM chips. Mark confirmed from the picture that pin 121 was used. Is pin 18 correct for Mk2 RAM?


Yes, pin 18 on MK2 (pin 14 on MK2a). On MK2, count the gap as three pins. Pin 1 is indicated by a dimple on one corner of the chip. With the board orientated so that dimple is in the top left corner, count the pins down the left-hand side of the chip.

Yes, the RAS hook-up wire goes to pin 121 on the CPU for MK2 or pin 123 for MK2a. With the board orentated the same way as above, pin 105 on the CPU is on the bottom row of pins, far left. Starting at pin 105, count towards the right.

As well as the soldering on the RAS lines, check out the power lines and the OE line.
Posted by: maczrool

Re: Mk2 not recognizing 4MB upgrade - 10/10/2004 13:10

By the way, you are welcome to send the unit back. When we did the install, there was no way to know if the extra RAM was working or not. Now that we have a mechanism for testing the additional RAM, it would be a lot easier to find the problem which is likely just a bad solder joint or two.

Stu