Hi,
I have Debian running on my Freerunner and have the package
linux-image-2.6.29-openmoko-gta02 installed. Nevertheless the active kernel
is 2.6.24. So it seems the kernel from the package is not used. How to
change this? Is the bootloader configuration documented somewhere?
According to http:/
On Sun, 28 Jun 2009 00:15:22 +0200, Jens Seidel wrote:
> I have Debian running on my Freerunner and have the package
> linux-image-2.6.29-openmoko-gta02 installed. Nevertheless the active kernel
> is 2.6.24. So it seems the kernel from the package is not used. How to
> change this?
deanna:~# ll /
which boot manager and what medium do you boot from?
in case of u-boot, the current kernel has to be flashed to the matching
flash partition. take the uimage from he kernel package and dfu-util it.
with qi you need to check if the name of the file matches the name qi
expects (when booting fr
> which boot manager and what medium do you boot from?
> in case of u-boot, the current kernel has to be flashed to the matching
> flash partition. take the uimage from he kernel package and dfu-util it.
U-boot is very flexible, and may boot from almost anywhere.
Including a file on ext2 filesyst
On Sun, Jun 28, 2009 at 12:36:49AM +0200, gregor herrmann wrote:
> On Sun, 28 Jun 2009 00:15:22 +0200, Jens Seidel wrote:
> > I have Debian running on my Freerunner and have the package
> > linux-image-2.6.29-openmoko-gta02 installed. Nevertheless the active kernel
> > is 2.6.24. So it seems the ke
On Mon, Jun 29, 2009 at 10:52:59AM +0200, arne anka wrote:
> which boot manager and what medium do you boot from?
uboot, I don't know from what medium I boot from, that's part of
the question. Debian is installed on the SD card, /boot is an a
separated partition /dev/mmcblk0p1 and of type ext3.
>
which boot manager and what medium do you boot from?
uboot, I don't know from what medium I boot from, that's part of
the question. Debian is installed on the SD card, /boot is an a
separated partition /dev/mmcblk0p1 and of type ext3.
well, looking into the u-boot env should solve that mystery
On Mon, 29 Jun 2009 12:07:38 +0200, Jens Seidel wrote:
> > Note the symlink "uImage.bin -> $actual_kernel"
> Thanks, this symlink was missing.
> Lets see whether it boots now all the time, at least once it worked and
I'm glad it worked!
> now
> I'm updating it via aptitude ...
Updating from on
> nikita pointed out that u-boot is csapable to boot kernels from
> elsewhere, but iirc the only location used on the fr has been mtd3, at
> least with the commonly used u-boot env.
No.
I don't remember how exactly I configured bootloader after installing
Debian - it was half-a-year-ago - but I d
"Nikita V. Youshchenko" writes:
> Could someone please explain me what is so wrong with u-boot, so people
> wrote qi?
I'm am personally using Qi at the moment _only_ because it does not
talk to glamo and I want to help in debugging glamo problem.
Other reasons that I've heard:
1) it has not bee
On Mon, Jun 29, 2009 at 03:31:40PM +0400, Nikita V. Youshchenko wrote:
> > nikita pointed out that u-boot is csapable to boot kernels from
> > elsewhere, but iirc the only location used on the fr has been mtd3, at
> > least with the commonly used u-boot env.
>
> No.
I agree :-)
> I don't remembe
elsewhere, but iirc the only location used on the fr has been mtd3, at
least with the commonly used u-boot env.
No.
you're right. now i remember issues with u-boot, debian and the kernel in
the fat partition of my sd card.
___
Smartphones-userlan
On Monday 29 June 2009, Nikita V. Youshchenko wrote:
> P.S.
> Could someone please explain me what is so wrong with u-boot, so people
> wrote qi?
> My many-year experience of using and porting u-boot on wide range of
> embedded hardware is extremely positive...
Ultimately I suppose the reason is a
13 matches
Mail list logo
