Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Sat 18 Nov 2017, 12:10
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
FatdogArm Beta1/2/3/4- 16 April 2016
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 33 of 34 [499 Posts]   Goto page: Previous 1, 2, 3, ..., 31, 32, 33, 34 Next
Author Message
InRong

Joined: 09 Jan 2017
Posts: 7

PostPosted: Thu 19 Jan 2017, 12:00    Post subject:  

Not had much time, however....

I have managed to get somewhere.... Just not a full solution...

I have used the debian bluez-5 package, and made sure it is fully patched. This allows me to connect the bluetooth, however it is not loading the firmware

root:~# hciattach /dev/ttyAMA0 bcm43xx-3wire 921600 noflow -
bcm43xx_init
Set Controller UART speed to 921600 bit/s
Flash firmware /lib/firmware/brcm/BCM43430A1.hcd
Initialization timed out.
root:~# hciconfig
root:~# hciattach /dev/ttyAMA0 bcm43xx-3wire 921600 noflow -
bcm43xx_init
Patch not found, continue anyway
Set Controller UART speed to 921600 bit/s
Device setup complete
root:~# hciconfig
hci0: Type: Primary Bus: UART
BD Address: E0:76:D0:DE:EE:2B ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING PSCAN
RX bytes:978 acl:0 sco:0 events:41 errors:0
TX bytes:1541 acl:0 sco:0 commands:41 errors:0

The second hciattach connects it, but it is not healthy. It will then connect through the default soundcard settings, and produces sounds in a stuttering fashion before stopping

Is this a case if nothing else supporting bluez5 properly? I suspect not at this point, and will keep trying to get the firmware upload working
Back to top
View user's profile Send private message 
TeX Dog

Joined: 06 Jul 2016
Posts: 341

PostPosted: Thu 19 Jan 2017, 12:37    Post subject:  

did you try and copy other distros overlay directory the are semi independent of kernel version OpenElec appears to me to be most compatible ( grapping non X relayed software )
Back to top
View user's profile Send private message 
InRong

Joined: 09 Jan 2017
Posts: 7

PostPosted: Mon 23 Jan 2017, 08:12    Post subject:  

I seem to have messed it all up somewhere, and now it totally fails on every attempt....

I will have to save off the useful bits and delete my save file. Am I correct in thinking that that will take me back mostly to a fresh install in effect?

That will also limit any confusion over what I did and didn't do..
Back to top
View user's profile Send private message 
Olle

Joined: 25 Oct 2016
Posts: 10

PostPosted: Fri 17 Mar 2017, 05:16    Post subject: Re: arm64
Subject description: raspberry pi 3
 

Olle wrote:
Maybe useful to have devuan_jessie_1.0.0-beta2_arm64_raspi3 as a benchmark for the eventual future FatDogArm64?


Hi guys,
Found this https://github.com/bamarni/pi64/releases
Tried the first and second release but got no sound.

Happy linuxing! Olle
Back to top
View user's profile Send private message 
TeX Dog

Joined: 06 Jul 2016
Posts: 341

PostPosted: Sat 18 Mar 2017, 11:34    Post subject:  

They seem to be making some good headway, The Official builders working with ARM have stated they only wish to maintain 32bit builds, but with the results of some effort in the communities around 64bitness and some very logical arguments, and now tested real world on the board results (30% increase raw speed), those same official guys unofficially cheering on the communities effort.
Looks like the real reason was 32bit internal GPU DMA-pipeline issues, that looked real ugly to those with advanced internal builder knowledge. But others have made good and not too drastic work-rounds and methods based on the hard 4G memory boundary. turned a hardware limitation into a bit fix solution that looks like a solid solution with very little code overhead/changes.
The 4G memory bounds is the end of 32bit space, all 64bit memory related pointers will naturally be only 32bit ignoring the top RAM address bit.
Can't follow exactly but best I can tell the top bit-set/cleared is used as a flag that the pointers are from 64bit space kernel, that any 32-64bit conversion needs to be done.


New thinking is with the Pi3 and newer v Pi2B based on the same chip move to 64bit , it would make a 32bit step backward to PiZero-Pi+ as one 32 bit kernel and PiB2v2, pi3 and future as 64bit kernel. It would press old first gen. PiB2+ back to lowest common 32bit kernel.
That seems like a real solution and keeps only two kernel versions supported which is already currently just two based on different ARM versions.
Next two to be based on 32/64 versions, if no other issues come as they are actively and with now some interest from the official group providing feedback, making forward looking patches to kernel to make GPU work seemlessly regardless of kernel bit size.

Take a look at popcornmixs' flurry of related posts and he has caught the 64bit bandwagon and GPU related 'fixes' needed to make it happen.
Back to top
View user's profile Send private message 
bogan down under

Joined: 05 Sep 2017
Posts: 4

PostPosted: Tue 05 Sep 2017, 09:00    Post subject:  

On my new odroid ux4
It will not boot, no bluelight to show boot is hapening.

After mucking around I got 'DD' to DDdo something but it didnt work

dd if=xu4-uboot.bin of=/dev/mnt/sdb1 bs=1024 seek=8
dd: failed to open ‘/dev/mnt/sdb1’: No such file or directory

then changed to the SD slot in my laptop

dd if=xu4-uboot.bin of=/dev/mnt/mmcblk0p1 bs=1024 seek=8
dd: failed to open ‘/dev/mnt/mmcblk0p1’: No such file or directory

then i removed /dev

# dd if=xu4-uboot.bin of=/mnt/mmcblk0p1 seek=1
dd: failed to open ‘/mnt/mmcblk0p1’: Is a directory

Then I the penny droped that I need to call the SDcard '0'

# dd if=xu4-uboot.bin of=/mnt/mmcblk0p0 seek=1
1262+0 records in
1262+0 records out
646144 bytes (646 kB) copied, 0.0620188 s, 10.4 MB/s

But wont boot, no blue light to show boot is doing its bit.
In the read me in the kernel package

from the readme in the kernel package

dd if=u2-uboot.bin of=sdcard seek=1
NB: First partition must be at least 1.5MB from sector 0 (sector 3072).

In the INSTALL file in release notes is this'

dd if=uboot-xxx.bin of=/dev/your_sdcard_device bs=1024 seek=8

Can someone who has fatdog arm working give me a 'DD' that works.

I need more help with the first sector bit also.
In GParted when opened the box with 'free space preceeding MiB' is at '1'
first of all what is MiB so i understand what it means.

Make a new partition on your SD Card, type FAT32, starting on sector 2048 (or 1MB boundary)

sectors arent mentioned in gparted.

when gparted is opened, MiB is on '1' already, is it then on the 1mb boundary already? or do i need to put 2 in the box to be on the 1 mb boundary?


android installed with 'etcher' works on it but no thanks, a smart phone OS on roller skates, opps. with keyboard and mouse for the teenagers and facebook.
Fatdog and Quirky from BK is all I want, fatdog first choice thanks.
Back to top
View user's profile Send private message 
don570


Joined: 10 Mar 2010
Posts: 4755
Location: Ontario

PostPosted: Tue 05 Sep 2017, 17:02    Post subject:  

Sorry , I know nothing about dd and gparted, however have
you looked at at simpler install of fatdog arm using some berryboot files
and then load the fatdog arm kernel.

Read HERE

and download the zip file and read James Bond's instructions about changing a kernel.

http://lightofdawn.org/wiki/wiki.cgi/-wiki/FatdogArm/00-WikiIndex

Quote:
These days, in addition to the Mele, FatdogArm is known to run on:

Allwinner A20 / Cubieboard
Odroid-U2, Odroid-U3, Odroid-XU3, Odroid-XU4
OLPC XO-1.75
OLPC XO-4 Touch
Pandora
Cubox-i i2 and i4pro
Google Nexus 7 (2012 edition)
Raspberry Pi 2
Back to top
View user's profile Send private message 
bogan down under

Joined: 05 Sep 2017
Posts: 4

PostPosted: Wed 06 Sep 2017, 19:55    Post subject:  

hello don570
I think I am using the berriboot files but with JB's kernel It is
'odroid xu3 kernel'
Correction I have your 6 pages saved and your fd-arm.sfs is 198 mb, JB,s is 236 mb.
JB has a ux4 that works, I just cant do the Disk Destroying bit.
I have both yours and JB's opened up if I take out all your berriboot and copy in xu3- kernel will I still have to DD.
I will give your 198 gb a try if you tell me what to take out of your berri boot and what to put in from xu3- kernel, would it work?
Back to top
View user's profile Send private message 
don570


Joined: 10 Mar 2010
Posts: 4755
Location: Ontario

PostPosted: Wed 06 Sep 2017, 20:31    Post subject:  

Quote:
SFS packages

An SFS package is a file that contains a compressed filesystem (squashfs). Upon "installation" the contents of this filesystem will be merged with the rest of your filesystem but it is never copied or expanded; the content will be de-compressed on-demand when you use the applications contained in the package.

To use it, download the package from here and move it to the same location as your save file, then go to the System tab in the Control Panel and click on System SFS Loader. Then choose which SFS file to load. You can also use SFS Manager (also in the Control Panel).

An SFS package usually contains a large application (e.g. libreoffice) or contains multiple applications or libraries.



James bond's SFS is bigger because he put in applications for touchscreens
ie a cellphone. He supplied various SFS on his repository for the various
machines and they vary in size.

If you are using odroid maybe this one will work??
http://distro.ibiblio.org/fatdog/arm/sfs/beta2/

___________________________________________________

However I think this one will support all the machines.
http://distro.ibiblio.org/fatdog/arm/images/beta5/fd-arm.sfs

Feel free to open it up and make changes. Laughing
then last step is make a zip file and go thru the installation procedure that I described on my thread.

_____________________________________________________________

You should read Barry k explanation for how Easy works...

http://easyos.info/docs/user/how-easy-works-part-2.html

since fatdog arm boots up much the same when it uses berryboot. (I think ???)

------------------------------------------------------------------
Back to top
View user's profile Send private message 
Mercedes350se

Joined: 16 Apr 2008
Posts: 726

PostPosted: Wed 06 Sep 2017, 20:33    Post subject:  

@bogan down under

https://archive.org/details/Puppy_Linux_Fatdog_Arm_Beta

Have a read of this page - scroll down to the U2 comments ( I know you are using a XU4) and "General Problems".

If you do zero the drive then you will need to use gparted to set the partition boundary again.

Note:

1. You need the /dev/ part of dd because the drive is not mounted, and
2. The drive part of dd should be sda or whatever but not sda1 or whatever

HTH.
Back to top
View user's profile Send private message 
don570


Joined: 10 Mar 2010
Posts: 4755
Location: Ontario

PostPosted: Thu 07 Sep 2017, 14:41    Post subject:  

Instructions were posted here as well
http://distro.ibiblio.org/fatdog/arm/images/beta1/INSTALL

I wonder if my method of putting everything on one fat32 partition is possible with Odroid?? James would know.


Quote:
For Odroid-U2
=============

Requirements:
------------
1. SD Card (at least 512MB) - all data on this SD Card will be erased.
2. The SFS package (fd-arm.sfs).
3. The kernel package (odroid-u2-kernel.tar.gz)

Steps:
------
1. Erase all partition on the SD Card using your favorite partition manager.
2. Make a new partition on your SD Card, type FAT32, starting on sector 10240
(or 5MB boundary); the size can vary but no less than 300MB (512MB is
recommended).
3. Copy fd-arm.sfs to this new partition.
4. Extract the kernel package and copy all the files to the new partition too.
5. "dd" the uboot-xxx.bin to the SD card, like this:
dd if=uboot-xxx.bin of=/dev/your_sdcard_device seek=1
6. You can then delete the uboot-xxx.bin from you SD card.

Note: If you are sure that your SD Card partitioning already meets step 1 and 2
(that is, because you have done this before or because you have installed
earlier alphas of FatdogArm), you can skip 1 and 2.
Back to top
View user's profile Send private message 
bogan down under

Joined: 05 Sep 2017
Posts: 4

PostPosted: Sun 10 Sep 2017, 21:31    Post subject:  

Much fun 'n games
Penny finally droped that my new USB3 card reader with micro SDcard in SD adaptor dont like disk destroyer.

# dd if=xu4-uboot.bin of=/dev/mnt/sdb1 seek=1
dd: failed to open ‘/dev/mnt/sdb1’: No such file or directory
# dd if=xu4-uboot.bin of=/mnt/sdb1 seek=1
dd: failed to open ‘/mnt/sdb1’: Is a directory
# dd if=xu4-uboot.bin of=/dev/mnt/sdb seek=1
dd: failed to open ‘/dev/mnt/sdb’: No such file or directory
# dd if=xu4-uboot.bin of=/mnt/sdb1 seek=1
dd: failed to open ‘/mnt/sdb1’: Is a directory
# dd if=xu4-uboot.bin of=/mnt/sdb seek=1
dd: failed to open ‘/mnt/sdb’: Is a directory
# dd if=xu4-uboot.bin of=/dev/mnt/sdb seek=1
dd: failed to open ‘/dev/mnt/sdb’: No such file or directory
#

Put the micro in adaptor in laptop

# dd if=xu4-uboot.bin of=/mmcblk0p1 seek=1
1262+0 records in
1262+0 records out
646144 bytes (646 kB) copied, 0.0596949 s, 10.8 MB/s

A result but this is the one that dont boot.
So zero the card like sugested by JB, more fun 'n games

# dd if=/dev/zero of=/mnt/mmcblk0p1 bs=4M
dd: error writing ‘/mnt/mmcblk0p1’: No space left on device
91+0 records in
90+0 records out
381173760 bytes (381 MB) copied, 13.3485 s, 28.6 MB/s

This fills up the Savefile, red warning, delete some files, ect.
This builds a file in /mnt that cant be deleted.
So savefile is deleted, never mind, I keep a pristene save file in 2 SD backup cards.

# dd if=/dev/zero of=/mmcblk0p1 bs=4M
dd: error writing ‘/mmcblk0p1’: No space left on device
47+0 records in
46+0 records out
196767744 bytes (197 MB) copied, 6.77734 s, 29.0 MB/s

Same thing, delete savefile, reload pristene savefile.
Then after reading from Benz

You need the /dev/ part of dd because the drive is not mounted

I tried this and DD worked

# dd if=/dev/zero of=?dev/mmcblk0p1 bs=4M

Another penny droped, the magic is /dev/mmcblk0p1
So I tried this, opening urxvt from with in /dev/mnt/mmcblk0p1

# dd if=xu4-uboot.bin of=/dev/mmcblk0p1 seek=1
1262+0 records in
1262+0 records out
646144 bytes (646 kB) copied, 0.0736823 s, 8.8 MB/s
#
The trick is I have to leave out the /mnt bit.

BINGO we have Fatdog Arm

Last edited by bogan down under on Mon 11 Sep 2017, 03:43; edited 1 time in total
Back to top
View user's profile Send private message 
bogan down under

Joined: 05 Sep 2017
Posts: 4

PostPosted: Sun 10 Sep 2017, 21:45    Post subject:  

From Don 570

However I think this one will support all the machines.
http://distro.ibiblio.org/fatdog/arm/images/beta5/fd-arm.sfs

I went there first because I wanted the latest and greatest but only has Pi kernel so left it for a week and went to odroid forum and tried their multiboot but that didnt work for me and the guy that made multiboot has lost interest so I came back to Fatdog.
All along I was following the INSTALL from JB which is the same as you refered to.
Next is Quirky on ux4
Back to top
View user's profile Send private message 
don570


Joined: 10 Mar 2010
Posts: 4755
Location: Ontario

PostPosted: Wed 13 Sep 2017, 18:47    Post subject:  

A good way to find how the filesystem is named is to type 'df'
in terminal.

see image. The right hand column has the mount path.

debian linux uses /mnt/mmcblk0p1
puppy linux uses /mnt/sda1
____________________________________________________
screenshot-filesystem.png
 Description   filesystem
 Filesize   20.6 KB
 Viewed   106 Time(s)

screenshot-filesystem.png

Back to top
View user's profile Send private message 
TwoPuppyPolicy

Joined: 04 Sep 2017
Posts: 3

PostPosted: Mon 18 Sep 2017, 00:49    Post subject: Changing resolution
Subject description: and stupid questions
 

After reading this

# Uncomment only ONE line! Leave all commented for automatic selection.
# Uncomment only the setenv line!

I want to use this resolution

1024x768 without monitor data using generic information

So I uncomment this line

setenv videoconfig "drm_kms_helper.edid_firmware=edid/1024x768.bin"
and change
video=video=HDMI-A-1:1024x768
in uEnv.txt
Nothing happens resolution stays the same.
Resolution stays at 720p 1280x1024.
When loading 1024x768 pops up in yellow bar at buttom of screen but that dont stick, 1280x1024 is loaded and shown in Hardinfo.
1024x768.bin is in /lib/firmware/edid
What else do I have to change in ubuntu-boot.ini

I have bought the battery to keep the time but cant change the time, in control panel set date and time can change the date but changing time the part for the digits is broken, no digits, cant input digits and then the new date dont stick when closing.

Stupid question, I dont know so I am going to ask. I know this is 32 bit, when something dont work can I swipe it from Fatdog 64. I would prefer to have FD64 CPU meter, would it work in Arm.

Uncommenting savefile=none didnt work.
renameing the savefile to increase its size did the trick. Other wise its just like Fatdog!
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 33 of 34 [499 Posts]   Goto page: Previous 1, 2, 3, ..., 31, 32, 33, 34 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Projects
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.2330s ][ Queries: 15 (0.0100s) ][ GZIP on ]