Memory options for RAQ4i/Velociraptor 1100

[tsmalmbe]

I've read that 1Gig is the current maximum for RAQ4i and Velociraptor 1100. Can I run memory with better specs than PC 100? How about ECC, will that work?

Just to narrow down the correct search words for ebay

[Davesworld]

Not ECC  and yes pc133 usually works fine. I tried to run 2 1GB sticks but each bank only sees 512MB.

[tsmalmbe]

Just read on the Strongbolt forum that 2x512 results in 880MB of usable memory due to some ROM-issue. From a normal server point of view, I understa nd that more memory is better. But what does RAQCOP do with the extra memory? What can I gain?

[Davesworld]

It's not a rom issue, it's the way that Strongbolt compiled their kernel without highmem support.  I have a 2.6.28 replacement kernel for Strongbolt 1.x systems that will run on all Cobalt machines up through the XTR and provide Samba and NFS support since I use my XTR's as raid 5 file servers. Keep in mind that Strongbolt itself is really an installer for Centos plus BlueQuartz and a kernel that will run it on a Cobalt. It is also the installer that you pay for, not the OS and James has the installer encrypted as well. With a properly compiled kernel for a Raq3/4 Qube3, here is what you see in dmesg with a gig of ram, This is from my 1.4.23 test build:

Linux version 2.4.37-cobalt (root@linux-s2mf) (gcc version 3.3.3) #1 Mon Apr 13 02:00:32 GMT 2009
BIOS-provided physical RAM map:
 BIOS-e801: 0000000000000000 - 000000000009f000 (usable)
 BIOS-e801: 0000000000100000 - 0000000040000000 (usable)
128MB HIGHMEM available.
896MB LOWMEM available.

And for some proc info:

root@raqcop:~ # cat /proc/cobalt/raminfo
0 [SDRAM]: 512 MB
1 [SDRAM]: 512 MB

root@raqcop:~ # cat /proc/meminfo
        total:    used:    free:  shared: buffers:  cached:
Mem:  1059106816 145543168 913563648        0  3657728 37617664
Swap:        0        0        0
MemTotal:      1034284 kB
MemFree:        892152 kB
MemShared:           0 kB
Buffers:          3572 kB
Cached:          36736 kB
SwapCached:          0 kB
Active:          18804 kB
Inactive:        21552 kB
HighTotal:      131072 kB
HighFree:         9288 kB
LowTotal:       903212 kB
LowFree:        882864 kB
SwapTotal:           0 kB
SwapFree:            0 kB

Any further questions?

[tsmalmbe]

Firstly a note on differences in sb and raqcop: i do realize how the sb model works. I tihnk 40€ is not much for a clear and easy install, and indeed i would gladly also pay the raqcop team for a smooth install (remember, i already fried one raptor during a rom-update which cost me more than 40€!). I believe in free software but also to pay for services (that provide real added value).

now regarding the memory issues: i don't know how much these projects co-operate or discuss (for instance firebolt), but I did contact J with a question regarding the memory and kernel compilation (no quote or reference to this forum!). 

[tsmalmbe]

and of course: thank you for your detailed answer!

[Davesworld]

Firstly a note on differences in sb and raqcop: i do realize how the sb model works. I tihnk 40€ is not much for a clear and easy install, and indeed i would gladly also pay the raqcop team for a smooth install (remember, i already fried one raptor during a rom-update which cost me more than 40€!). I believe in free software but also to pay for services (that provide real added value).

now regarding the memory issues: i don't know how much these projects co-operate or discuss (for instance firebolt), but I did contact J with a question regarding the memory and kernel compilation (no quote or reference to this forum!). 

Out of curiousity I tried Firebolt. It's basically Clark Connect using the Strongbolt Server kernel. You really cannot compare Clark Connect with IPCop. IPCop is a hardened dedicated firewall/router whereas Clark Connect is a server with the firewall enabled. The 2.6 rom kernel they use is based on my friend Chris's work from a year ago long before he had the boot code updated for the 2.6 kernel. In order to get the thing to boot, SB wound up using kexec which requires some libraries to actually exist on the drive before it will boot anything. All this was to get usb boot but the trouble to get to that point in the first place is klunky.

I reverted my test box back to rom 2.10.3 and continued to use it as one of my cop test boxes. After playing with it for over a year, Chris seems to be abandoning further work on the 2.6 kernel rom. The issue with non self initting pci cards not working on a raq wound up being a design shortcut by the cobalt designers back when. Other than most wifi cards, it's not a real problem for us using it the way we use it.

I have the rom source code here and will attempt to make one. I see no gain by using a 2.6 kernel rom when the one we have will boot even the latest 2.6 kernel anyway. It makes more sense to make an updated 2.4 kernel rom, use the e100 driver and split the xtr and 3000 series into separate roms and use the saved space for usb storage.

As far as installer goes, I have gotten as far as getting a Raq to boot and start the IPCop installer. Since I used bfn, it uses the rom kernel. I had not tried bfnn yet, this one has to be done via serial console but you need one anyway if you want to set the ip that it boots to so you don't have to mess with your dhcp settings in your firewall device. Ultimately I want people to be able to hook a serial console to it, set a few things in the rom menu and install over the internet. The standard netboot via lcd menu actually uses bfn which uses the rom kernel, IPCop's installer assumes you have IPCop's installer kernel version so when it gets to where you choose cd or net, it can't find drivers and it does not know you are already running a kernel that supports the hardware.

As far as comparing SB to anything, you can't. SB is the installer NOT the os. The os is centos plus bluequartz and in firebolt it the os is clark connect. This is the reason why their installer is very good but I have had to make my own kernel to use on my SB server installs on my XTRs. The majority of their work was on the installer and the proof is in the painless ease of how it works. Of course any of us can take the nfsroot-x86 environment of one of the original Cobalt restore discs and go with it and modify but yes, it's not a small project. 

[tsmalmbe]

Well, that was an answer with a capital A. Very well put I think.

btw, I think I will be using the SB installer to upgrade my ROM's.

[tsmalmbe]

The SB installer worked nicely (although the docs were not easy to navigate) to upgrade both of my units.

The new ROM is not behaving nicely with the memory I had installed when I got the unit (Kingston 256MB 133MHz). I got kernel panics and lots of ugly stuff. Switching to a couple of 128MB 100MHz resolved my situation.

Hints in specific memory chips that work greatly appreciated!

[Davesworld]

The SB installer worked nicely (although the docs were not easy to navigate) to upgrade both of my units.

The new ROM is not behaving nicely with the memory I had installed when I got the unit (Kingston 256MB 133MHz). I got kernel panics and lots of ugly stuff. Switching to a couple of 128MB 100MHz resolved my situation.

Hints in specific memory chips that work greatly appreciated!

What exactly did you install? I only know what will run with both the 2.10.3 rom and my kernel for Raqcop and I cannot vouch for anyone elses third party Rom, kernel and so forth. I've used a lot of sticks with the raqs and qubes, even two 1GB sticks and they worked fine but only 512MB per bank is seen. This may be a limitation of the chipset. Whoever compiles the kernel has to have highmem enabled or you won't get a full 1GB usable as a small portion of the 1GB is highmem on these devices. Also, the rom has to support it as well and the 2.10.3 certainly does. I hadn't had any that don't run yet from the 512MB sticks I have tried thus far. I have never seen a pc133 non registered 256MB dimm that won't run these as of yet. I DO know however that ECC sticks will NOT work. Standard pc133 non registered non ecc is a starting point. I believe there are some weird memory layouts on rare sticks that may cause problems but I can't imagine Kingston making any of them.

[tsmalmbe]

i only upgraded the room. Now when i put in my kingston chips in order A-B i can see 512MB and the unit is unstable and behaves differently on each startup, sometimes boots with 512 sometimes with 256. This is all while i'm holding down the s-key, so nothing is installed yet.

if i choose to put the memory in B-A order, i only see 256MB and it is a bit more stable.

with PC100 there are no probs.

[Davesworld]

Ok so which rom?

[tsmalmbe]

the one from the latest sb1 install cd. Will check once i get home.

[tsmalmbe]

cobalt-2.10.3-ext3-1M.rom

[Davesworld]

Ok that's the right Rom. Actually the Ali Aladdin V that the 3000 series use does have layout limitations as far as that goes as most chipsets did and still do so you could well have come across an arrangement that is unstable but is actually seen. I think a good starting point since so many live outside the US and may not want to pay the price for something like this is to go to a memory reseller online and tell their configurator what you have, it will tell you that 512MB is the maximum but with the 2.10.3 rom this is no longer true at all:

http://www.raqport.com/store/merchant.mvc?Screen=PROD&Store_Code=R&Product_Code=P1512MB133

The specs are there to give an idea.