FatdogArm Beta1/2/3/4- 16 April 2016

Message

don570 · #466 Post by **don570** » Sat 10 Dec 2016, 21:38

Testing out the new kernel in my raspi2 board.

I have found that I have the same problem with my sound stuttering every couple of seconds. I never have this problem with kernels that
are compiled for the board like Barryk.

_____________________________________________

Olle · #467 Post by **Olle** » Thu 05 Jan 2017, 10:48

jamesbond wrote: As for 64-bit - well, with only 1GB RAM

Sorry for cross posting from "Quirky Xerus 8.1.4 for Raspberry Pi2 and 3"

I tried this during X-mas:

devuan_jessie_1.0.0-beta2_arm64_raspi3.img.xz as found in

https://files.devuan.org/devuan_jessie_beta/embedded/

Nice! Fun!
Could Devuan be a base for 64bit FatDogArm for Pi3?

Swap might help the low memormy.

Best wishes for 2017! Olle

jamesbond · #468 Post by **jamesbond** » Thu 05 Jan 2017, 15:19

Olle - unlikely. FatdogArm is compiled from scratch, I don't use existing distros as the base.

Olle · #469 Post by **Olle** » Thu 05 Jan 2017, 19:36

jamesbond wrote:Olle - unlikely. FatdogArm is compiled from scratch, I don't use existing distros as the base.

and you make a fine distro of it! Fatdog64 is happily running in my x86_64 boxes. Thanks for your work!

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

InRong · #470 Post by **InRong** » Mon 09 Jan 2017, 18:13

Hi,

Just found FatDogArm, and love the concept. I have installed Beta5 on a Pi2 with a RedBear IOT_phat that basicaly gives Pi3 chipset WLan and BlueTooth.

Was hoping (far fetched idea I know.... lol) to have had the Pi3 bluetooth available. Do you have any idea if you will have time to look into this soon, or any pointers as to what needs doing... Or where to look to attempt to add it myself.

I can confirm that the WLAN is working in this setup lovely, and so far it all works fine except the bluetooth I had hope for ;-(

don570 · #471 Post by **don570** » Tue 10 Jan 2017, 00:13

To Inrong....

Try BarryK's Quirky Xerus version
http://murga-linux.com/puppy/viewtopic.php?t=108132

He was apparently able to get his bluetooth devices to work.

_________________________________________________________

InRong · #472 Post by **InRong** » Tue 10 Jan 2017, 16:30

Cheers Don570,

I will look at this. The main issue is I will be powering the PI from the BT speaker (will be a pi Zero eventually) so PupMode2 is not ideal. However lets see if I can make a hybrid.

I will let you all know how I get on.....

jamesbond · #473 Post by **jamesbond** » Tue 10 Jan 2017, 17:14

Pi3 bluetooth seems simple enough. I just need to build the correct version of hciattach (read: Broadcom's mangled version of that thing). Some other people have fished the info out of Raspi guy's hands (you need to be very very very very nice and patient to this guy or he won't play ball), so it's just a matter of (finding) the time to do so.

InRong · #474 Post by **InRong** » Sat 14 Jan 2017, 18:39

Would be excellent if you find the time.

I have tried the simple solution of building the latest blueZ5 with the patches and it does not quite work on mine. I am sure there will be other issues with using 5 not 4, but thought I would try 1 step at a time.

I tried to download the source package for blueZ-4.101 from your ibiblio archive but it kept failing -550 error, was it my end or theirs? I am sure the major parts of the patches can be hand inserted.

I will keep playing..

don570 · #475 Post by **don570** » Sat 14 Jan 2017, 18:56

I am getting 404 'not found error' as well

http://distro.ibiblio.org/fatdog/arm/so ... 62e.tar.gz

______________________________________

ally · #476 Post by **ally** » Sun 15 Jan 2017, 01:17

http://archive.org/download/Puppy_Linux ... rmhf-1.tbz

InRong · #477 Post by **InRong** » Mon 16 Jan 2017, 13:14

Cheers for the thought ally, don't suppose you have found the source code file though

jamesbond · #478 Post by **jamesbond** » Mon 16 Jan 2017, 15:25

bluez4 (and any other version of bluez) is available here: https://www.kernel.org/pub/linux/bluetooth/.

bluez-tools source - that was a mistake on my part, I have corrected the access, it should work now.

InRong · #479 Post by **InRong** » Tue 17 Jan 2017, 21:24

Thanks jamesbond,

I grabbed the bluez4-101 from the fatdog64 sources. I have patched it, and it is getting closer, but won't yet install the firmware. Tried the 10-bluetooth-imx6 and that looked promising, but is for differing arch so not immediately correct...

I will keep trying

TeX Dog · #480 Post by **TeX Dog** » Tue 17 Jan 2017, 21:41

please leave build notes I really need a worjking blutooth keyboard. I know the one I have works perfectly with FatDog64 and confused as all get out why using same tools it doesn't work in RPi in puppylinux world, everybody elses OS I have tried works.
I do not want to jump ship..

InRong · #481 Post by **InRong** » Thu 19 Jan 2017, 16:00

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

TeX Dog · #482 Post by **TeX Dog** » Thu 19 Jan 2017, 16:37

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 )

InRong · #483 Post by **InRong** » Mon 23 Jan 2017, 12:12

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..

Olle · #484 Post by **Olle** » Fri 17 Mar 2017, 09:16

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

TeX Dog · #485 Post by **TeX Dog** » Sat 18 Mar 2017, 15:34

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.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

FatdogArm Beta1/2/3/4- 16 April 2016

arm64

Pi3 bluetooth

Re: arm64