I resized hda1 (drive0), resized hda2 (extended partition), moved hda5 (root) into the <128G section. I was unable to move hda6 (rio partition) because parted couldn't recognize the partition type.

I'm going to fire up the central and see if anything changed.

You are right about the partition mounting though. I checked fstab, and it's empty.

It's booting!!! After boot, the system recognizes the entire disk. Mounting swap succeeds and it's in the last space on the drive.

Ok, from this, I can draw the following conclusions:
1. The kernel in flash doesn't support >128G drives.
2. The stock kernel on the HDD does.

Is there a way to move the rio partition, or create it earlier on the drive? If I can move it, I can add the largest partition on the end of the disk without changing the partition numbers of the existing partiitions.

With that bit of information, I'm pretty sure I can get this 100% working, one way or another. I attached my boot log for those interested.

I may be able to create the new partition and then use "dd" to do a raw copy...

http://www.sysdesign.ca/guides/partitions.html

Could anyone let me what's failing on line 433 of player.cpp? Maybe someone in Cambridge?

I'm also looking into the drive errors. Apparently, I may have to compile a kernel yet.

--------------------------------
Permanent section: 0x0x22d6248..0x0x22d7324 (mlocking 8K)
jupiter 1.10-rc1 (build 23) 2002/11/19.
hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hda: drive_cmd: error=0x04 { DriveStatusError }
E !! player.cpp 433: MainThread::Init failed!

I'm compling try #2 of the kernel now. Apparently, what I thought would be loaded was pretty far off from what is actually loaded in the stock kernel. I also found what seems to be a fix for that specific HDD error. Interestingly, this may also allow for hooking up external USB drives, because that was the error encountered when trying to do so in the past.

More to come...

Kernel #4 is looking better. The partition table is now recognized, there's no more HDD errors, and I'm getting root to mount, and I think I have nearly all the same drivers loading (in addition to others). /dev/hda1, the reiserfs partition is failing to mount, I'll have to take a look at that tomorrow.

I have to say, doing this without the benefit of LILO or grub is a serious pain.

Also, if anyone tries to compile a kernel, use the source on the 1.10 cdrom image. I couldn't get earlier kernels to compile at all...

Thanks for the effort you are putting into this. I don`t have the time to do this kind of research on my Central.

Heh, I'm not sure I do either.

Well, here's my lastest attempt. I'm going to attach my kernel log, if anyone has comments, I'd be glad to hear them.

Ok, here's my problem... The SCSI generic driver is attaching to the HDD. I can mount the reiserfs disk using the SCSI emulated name but not as /dev/hda1. I have used SCSI generic support extensively in the past and never had this problem. Does anyone have any insight into this issue? SCSI generic is required to support cd burning under Linux.

hda: ST3300631A, ATA DISK drive
hdb: CD-W58E, ATAPI CD/DVD-ROM drive
ide0 at 0xf7000000-0xf7000007,0xf7000038 on irq 6
hda: 586072368 sectors (300069 MB) w/16384KiB Cache, CHS=581421/255/63
Partition check:
/dev/ide/host0/bus0/target0/lun0: p1 p2 < p5 p6 p7 p8 >
...
SCSI subsystem driver Revision: 1.00
scsi0 : SCSI host adapter emulation for IDE ATAPI devices
Vendor: TEAC Model: CD-W58E Rev: 1.0A
Type: CD-ROM ANSI SCSI revision: 02
Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
sr0: scsi3-mmc drive: 32x/32x writer cd/rw xa/form2 cdda tray
cdrom: entering register_cdrom
Uniform CD-ROM driver Revision: 3.12
cdrom_init finishes
cdrom: drive "/dev/sr0" registered
...
Tried to mount /dev/hda1 as reiserfs but got error 2
No primary hard disk

----------------------------------------------------------------
Edit: Apparently, the problem was caused by devfs being compiled into the kernel. The /dev files should be copied from the original directory by using "cp -dpR /dev/* /destination".

Ok, my 120G HDD is most certainly failing. It's time for a new HDD for the central. I may pick up this line of research again when I get the new HDD. Does anyone have a suggestion for how to get this done, or is everyone rocking out with their iPods? Thanks!

I have some RAM chips that I suspect are compatible with the central. The chips are marked with:

IC42S16400-6T
PB2645111 0307

I also have the datasheets for both the stock chip (listed above in this thread) and the suspected compatible chip. Could one of you hardware gurus take a peek and let me know if you think the chips are compatible?

Edit: I checked the form factor and the pin out, and they seem to be the same.

Stock chip datasheet.

Hyndai Korea
HY57V651620B
0028B P TC-7

Edit: added markings from stock RAM chip

I forgot to add... These IC RAM chips are from a Linksys WRT56G router, among others. Thus, they are generally available, and in most cases, for the cost of shipping a bricked router.

Ok, I have two RAM chips that I desoldered from the router. I have 2 questions.

1. If the chips are compatible and soldered on the board, will the machine be able to boot normally with no code changes? Obviously I wouldn't expect the additional RAM to be recognized.
2. Do you think the RAM will work?

If the Central is anything like the Empeg, then changes to the Kernel would be needed to recognize the extra RAM exists, and changes to the player code would be needed in order to do something useful with that RAM, such as cache and database space.

I soldered a surface mount amd486-133 onto a board that had a amd486-66 chip to attempt to gain some facility with a soldering iron. I'm going to test it tomorrow and if it works, I'll solder the RAM chips on the central. If it doesn't work, I think I need more practice with the soldering iron.