No, it would not be worth it. All that is wrong is that the devices got renamed somewhere around 2.6.21
To fix your problem, do the folliowing. First, from the kboot: prompt, type "sh". When you are in a shell, follow these steps:
Code:
mount -o remount /dev/sda1 /mnt/root
chroot /mnt/root
cd /etc
mv fstab fstab.old
sed -e 's/sda/ps3da/g' <fstab.old >fstab
Press control-D to exit the chroot shell and type these last few commands:
Code:
mount -o remount,ro /dev/sda1 /mnt/root
sync
reboot
If you're saying that the problem is that the Ubuntu scripts already did the above modifications to your fstab and you're using an old kernel, then simply invert the sed command to do the opposite:
Code:
sed -e 's/ps3da/sda/g' <fstab.old >fstab
FWIW, I'm using the latest 2.6.22-rc5 kernel from Geoff's git tree with a couple of minor patches and it's great. It now reboots reliably and I've got my bluetooth controllers working under Linux. Not long until my python-ps3 project has a standard base CD image...
