JB> do you have FAT as your /boot partition? It turned out that that is a
JB> bad idea when managing the kernel with dpkg. You can either
JB> * Reformat it as ext2, adjust /etc/fstab, adjust uBoot env and
JB> re-install kernel package
JB> * Remove the kernel package and manually download and inst
It turned out to be quite simple in the end.
Flashed QT on the FR, booted that, and followed Marian's tips on
installing the mwester kernel from a while back.
Then reinstalled fso-gta02 and things were fine again :-)
Paul
--
Anger repressed can poison a relationship as surely
as the cruelest
Hello arne
> am i right in assuming that you
> a) are running debian from sd card and
> b) have /boot as separate fat partition
Looks like I have to go this way. The info on the Debian page to set the
1st partition of the SD to EXT2 and updating uBoot requires some
fso-util packages on the local
Thanks, everyone, for the tips.
I'll look into changing the FAT partition to EXT2, as that seems to be
the big problem-maker.
Paul
--
Be a friend to thyself, and others will be so too.
-Thomas Fuller
http://www.nlpagan.net
Running on Mandriva Linux 2008 and Ubuntu 8.10
__
> Would someone know a nice way to get the FR running again?
am i right in assuming that you
a) are running debian from sd card and
b) have /boot as separate fat partition
?
if so, unmount /boot, run
apt-get -f install
this should fix any half installed packages
afterwards copy the files in /boot
Hi,
Am Sonntag, den 23.11.2008, 11:38 +0100 schrieb Paul:
> I must admit I had just started the upgrade command and went off to do
> different things...
>
> What I recall seeing at the end was the mention of a problem making a
> backup link to uImage.bin after which the upgrade exited with code
2008/11/23 Paul <[EMAIL PROTECTED]>:
> I must admit I had just started the upgrade command and went off to do
> different things...
I've seen this too. But in my case I was OK again after a reboot.
Neil
___
Openmoko community mailing list
community@
Michele Renda wrote:
> It happent to me too, some months ago.
>
> It is possible to solve the problem in different ways,
> you can try to boot with a "non debian" image, download the install.sh
> script, and do only
> the stages: mount, kernel (in this way it reinstall only the kernel)
>
> I don't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It happent to me too, some months ago.
It is possible to solve the problem in different ways,
you can try to boot with a "non debian" image, download the install.sh script,
and do only
the stages: mount, kernel (in this way it reinstall only the kern
I must admit I had just started the upgrade command and went off to do
different things...
What I recall seeing at the end was the mention of a problem making a
backup link to uImage.bin after which the upgrade exited with code 1.
The SSH session was still fine, the GUI on the FR itself had die
10 matches
Mail list logo
