Beyond the usual bricking your Kuro type concerns there shouldn't be anything to worry about. When i did it i made sure i got it working with the RAM build of u-boot first. When i used the flash version there were no problems.

OK, I think I'm very close. I did get the "Try out the RAM build of u-boot" to work thanks to the section "If you are not running 2.4.x kernels". It's the "Install u-boot into FLASH" that I may need some clarification. Since I do boot with a different kernel via loader.o, I need to do these last 2 sections in EM mode. It isn't clear how to do the flash piece in EM mode so I sorta winged it. Of course it didn't work.

What I did after the RAM piece worked, I went through the steps here again but instead of using the u-boot-hg.ram.bin in

I'm now in the final stages. It all seems to have worked from what I can tell. The last thing it talks about is the need to update the /etc/fstab Before doing this, the instructions state that you should boot the old kernel from flash again via

Code:

run flboot

This always boots up in the 2.4 EM mode flavor. It than talks about how the fstab should look using /dev/sda# instead of /dev/hda#. Do I really need to have it in EM to do this? Could I just boot up with the latest kernel to make the change?

Also, what I have on my list is quite different than what the example shows:

Are the mount points /proc and /dev/pts needed? Should the options for partitions 1 and 3 just be default or should I leave them the way they are?

I don't fully comprehend why hda needs to be changed to sda....I know it's because of the whole IDE to PATA change but if hda wouldn't work, how am I able to see hda1 and launch apps from it without making any changes to the fstab?

you just need to change the hda to sda, since this is the identifier for the drive.

and as for you booting with the hda working, when you boot the new kernel it will automatically (by default) mount the root as sda1 as its part of the kernel boot parameters (i think)
It will try to remount / as hda1 but since that device doesnt exist , it will not complete that task but you will notice that your /mnt will not have mounted either.

When I did the ram test i just watched the output to the netcat and it didnt look like it errored, it found the kernel and seamed to load it, so I was happy enough to flash it.

Who is online

Users browsing this forum: No registered users and 1 guest

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum