Fatdog is very nice, nice work, i just want to report two things but i don't really know if they are fatdog related problems or not

I have a mk802 with 1g ram, it's booting fine but htop says only 490mb as avaiable memory, is this expected?

I have 2 tvs, when i plug the stick on the first one fatdog boots straight to x right away without any problem, but on the other tv it takes a lot of time, it seems like xorg is probing many different resolutions without sucess, sometines i see for a few seconds distorted images. But after a long very long wayting i finally get X to work and the tv reports the image as 1280x720p. 720p is the same resolution my first tv reports so what may be the problem with my other tv?

FatdogArm meta-distribution can be used for any ARM platform/device capable of ARMv7-A, VFPv3-d32 and NEON. There are images available for Mele A1000 and OLPC XO-4 (XO-4 image is still on the way); and in the future there may be images for Cubieboard2 too.

Please check the release notes for more details.

tuna1 wrote:

Hi

Fatdog is very nice, nice work,

Thanks.

Quote:

i just want to report two things but i don't really know if they are fatdog related problems or not

I have a mk802 with 1g ram, it's booting fine but htop says only 490mb as avaiable memory, is this expected?

You will need to find a script.bin for your 1G mk802; otherwise only 512MB is recognised (and a few megs are taken for video buffer etc). Please try the attached script.bin and tell me whether it works - otherwise, please see the release notes for details.

Quote:

I have 2 tvs, when i plug the stick on the first one fatdog boots straight to x right away without any problem, but on the other tv it takes a lot of time, it seems like xorg is probing many different resolutions without sucess, sometines i see for a few seconds distorted images. But after a long very long wayting i finally get X to work and the tv reports the image as 1280x720p. 720p is the same resolution my first tv reports so what may be the problem with my other tv?

The Mele image is configured to do EDID readout before setting the resolution; if you TV doesn't support EDID, it may end up taking quite a while for the operation to time-out. If you know what resolution to set, look at the "video" line in uEnv.txt and remove the EDID word, ie change from:

FatdogArm meta-distribution can be used for any ARM platform/device capable of ARMv7-A, VFPv3-d32 and NEON. There are images available for Mele A1000 and OLPC XO-4 (XO-4 image is still on the way); and in the future there may be images for Cubieboard2 too.

Please check the release notes for more details.

tuna1 wrote:

Hi

Fatdog is very nice, nice work,

Thanks.

Quote:

i just want to report two things but i don't really know if they are fatdog related problems or not

I have a mk802 with 1g ram, it's booting fine but htop says only 490mb as avaiable memory, is this expected?

You will need to find a script.bin for your 1G mk802; otherwise only 512MB is recognised (and a few megs are taken for video buffer etc). Please try the attached script.bin and tell me whether it works - otherwise, please see the release notes for details.

Quote:

I have 2 tvs, when i plug the stick on the first one fatdog boots straight to x right away without any problem, but on the other tv it takes a lot of time, it seems like xorg is probing many different resolutions without sucess, sometines i see for a few seconds distorted images. But after a long very long wayting i finally get X to work and the tv reports the image as 1280x720p. 720p is the same resolution my first tv reports so what may be the problem with my other tv?

The Mele image is configured to do EDID readout before setting the resolution; if you TV doesn't support EDID, it may end up taking quite a while for the operation to time-out. If you know what resolution to set, look at the "video" line in uEnv.txt and remove the EDID word, ie change from:

Removing eid worked. Thank you!
I tryed your script.bin but no sucess, the avaiable memory is the same and worst, cpu use is always at 20%, with your original script.bin cpu use is very low.I will read your release notes but i'm not very skilled...

I tryed your script.bin but no sucess, the avaiable memory is the same and worst, cpu use is always at 20%, with your original script.bin cpu use is very low.I will read your release notes but i'm not very skilled...

I tryed your script.bin but no sucess, the avaiable memory is the same and worst, cpu use is always at 20%, with your original script.bin cpu use is very low.I will read your release notes but i'm not very skilled...

Sorry, I made you belive i had a mk802 1gb but what i have is a mk802ii, you tryed to help me but that was not possible with my mistake. but there is one good thing with this, i started reading about this and after some time i was able to build my mk802ii script.bin from the link you gave me. The cpu load is now working just fine but still no acess to the full memory. I tryed adding mem=1024 but when i do that it won't boot
Sorry again and thank you, today you helped me learn a few things

Sorry, I made you belive i had a mk802 1gb but what i have is a mk802ii, you tryed to help me but that was not possible with my mistake. but there is one good thing with this, i started reading about this and after some time i was able to build my mk802ii script.bin from the link you gave me. The cpu load is now working just fine but still no acess to the full memory. I tryed adding mem=1024 but when i do that it won't boot
Sorry again and thank you, today you helped me learn a few things

I think I may have to build a custom version of u-boot for you. This is the general problem with ARM platforms - the crucial part (bootloader, kernel) can seldom be shared _________________Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread.

Sorry, I made you belive i had a mk802 1gb but what i have is a mk802ii, you tryed to help me but that was not possible with my mistake. but there is one good thing with this, i started reading about this and after some time i was able to build my mk802ii script.bin from the link you gave me. The cpu load is now working just fine but still no acess to the full memory. I tryed adding mem=1024 but when i do that it won't boot
Sorry again and thank you, today you helped me learn a few things

I think I may have to build a custom version of u-boot for you. This is the general problem with ARM platforms - the crucial part (bootloader, kernel) can seldom be shared

Okay, this is a version of uboot for mk802ii. Install it by doing

Code:

dd if=uboot-mk802ii.bin of=/dev/XXX bs=1024 seek=8

where /dev/XXX is your SD Card device (make sure you don't point to your harddisk or your harddisk data will be destroyed beyond repair - since you have already dd-ed the image I suppose you already know about this).

I have received a Cubieboard2 from someone who shall remain anonymous (thank you!).
The board arrived yesterday, and I've got FatdogArm running on it today; here is the mugshot.
It still require a few tweaks, but in general it's running great.

Sorry, I made you belive i had a mk802 1gb but what i have is a mk802ii, you tryed to help me but that was not possible with my mistake. but there is one good thing with this, i started reading about this and after some time i was able to build my mk802ii script.bin from the link you gave me. The cpu load is now working just fine but still no acess to the full memory. I tryed adding mem=1024 but when i do that it won't boot
Sorry again and thank you, today you helped me learn a few things

I think I may have to build a custom version of u-boot for you. This is the general problem with ARM platforms - the crucial part (bootloader, kernel) can seldom be shared

Okay, this is a version of uboot for mk802ii. Install it by doing

Code:

dd if=uboot-mk802ii.bin of=/dev/XXX bs=1024 seek=8

where /dev/XXX is your SD Card device (make sure you don't point to your harddisk or your harddisk data will be destroyed beyond repair - since you have already dd-ed the image I suppose you already know about this).

This is a mid to large sized project 4+ hours for/on RasPI without your dccs.

One of the few clean, large, cross platform projects,
I use it a lot for complex math rendering and engineering work (weird hobby, most likely the only NON Phd playing in this field, so shhhh I'm like Howard from the Big Bang Theory )

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 vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum