Recent Posts

Hello. I decided to revisit Raid 1 which has been in IPCop SVN for some time. I embedded the md module in the kernel (you HAVE to do this on a Cobalt for any drivers needed for root) and enabled the recommended autodetect function which helps a lot where the driver is ALWAYS loaded. A Normal PC IPCop has everything as a loadable module so it is only there when a raid 1 array is really used. With build 4889 in Raid, I simply set boot and root to md0 via serial console in the rom boot menu. I have it running on a Raq 550 as we speak. On my test 3000 series, whether raid or single drive it boots the kernel and gets as far as mounting root read only and then it fails when init starts so this performs the same in raid or single, this is mentioned elsewhere. I hope to get the userspace issue on the slower hardware figured out soon.

One of the gotchas is with System Status and System Information pages in the admin web gui. It looks for /proc/mdstat and then instructs it to act on it. In the case of the raid driver ALWAYS being there, mdstat ALWAYS exists whether md0 and md1 exist or not. On a single drive, this breaks the hard drive info section of these two pages. This is not a big deal to fix in itself.

Hello all! I had been keeping and regularly building from, a parallel Cobalt Friendly branch of IPCop 2.0svn which at 1.9.15 is beta. Somewhere in the pre 1.9.15 revisions, specifically revision r4719, it no longer ran on the few 3000 series that I tried it on but runs fine on the Raq 550.  To clarify, it will boot on the 3000 series up to when init starts and then I get the error:
______________snip______________________________
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly on device 3:1.
Freeing unused kernel memory: 156k freed
INIT: version 2.88 booting
Kernel panic - not syncing: Attempted to kill init!

_______________________________________________

Now, 1.9.15 is r4889 and I have uploaded an iso image to install on either a donor machine or VMWare, a 512MB flash image and the diff from svn file.

I am going to debug init as root is mounted read only at this stage which leaves us with the serial console so this is the only output we can have.

While contemplating that, I am in the process of trying raid1 on two flash drives no less. The Cobalts have always been able to boot up to md devices. The only problem is that when the md module is embedded in the kernel as are the ide drivers for ali and serverworks chipsets, system information loses it's ability to read drive info when using non raid.

After two days of tinkering at night I have a raq4 running debian lenny with several kernels working from 2.6.26 to 2.6.28.  Stay tuned for some info about disk images and stuff for anyone who wants to take a shortcut and use a disk image to get the heavy lifting already done.   

Hi, I have an RAQ3 and would like to install Debian Lenny on it, would you be able to help please.

Thank You,

Alex.

You possibly could have a flashrom chip with bad blocks. You can indeed but pre-programmed rom chips from http://www.raqware.com or more specifically http://store.raqware.com/product_info.php?products_id=45&osCsid=b6885299b6e6ce6a31db0da7961c2586.

I have a few units that need it here as well. It's considerably more expensive to send the unit in and have them do it but that service is available.

I should also mention that I meant to reply to you last week but my browser crashed while trying to submit my reply and I left for work after that.

Okay folks, i had a very bad outcome from a serial flash attempt.

To my credit, the rom image onboard before the flash attempt was broken to begin with.

I followed the flash via serial instructions from http://wiki.parvi.org/index.php/ROM_Flash_without_OS_Guide and things failed miserably after the "write_eeprom 0" was issued.

Short of it is, i need a hand from everyone on how to reflash the eeprom, as it is blank now. It is the AMD flash chip and I hope someone can help me. (preferably without removing the chip from the board if possible!)

The unit shows a bar of filled blocks on the upper line of the LCD and no lights come on whatsoever. (status on front left or mini-LEDs beside serial port on the back as well)

I believe the unit is not dead as-per-say, but just needs RAQCop ROM flashed onto it, as i have no other flash file to use.

Any help would be appreciated!!

**EDIT**: just read the post http://raqcop.com/forum/index.php/topic,27.0.html and this is what i have ended up with as well.

Any idea who in Canada does the repairs, preferably in Toronto (905/416/647 area codes) or surrounding area?

Psst, hey Dave, you wanna buy this perfectly good unit that has an empty flash for cheap? i swear it's a genuine Cobalt, yeah, i swear it! LOLOL!!! or might someone know how i can go about buying a preloaded flash EEPROM chip and i can do the solderwork myself with a bit of patience?

Out of ideas at the moment. 

OK, I resetted the CMOS, but it didn't change anything. Some more ideas?

No, I didn't. How can I do this? Just by taking out the CMOS-battery for a short time?

Hold the E button down while powering up and watch the lcd, it will tell you that the cmos is reset. I've had to do this at times with changes such as upping the ram to 1GB.

No, I didn't. How can I do this? Just by taking out the CMOS-battery for a short time?

Did you do a cmos reset after changing processors?