Firefox installed from packages on my RaspBerry Pi Zero crashes every time I launch it...

Don't read about the RaspBerry. I stopped using it. I have exchanged it with the Radxa Zero 3W because it's more low profile and it is powerful as the Raspberry Pi 4 (Broadcom BCM2711, Quad core Cortex-A72 (ARM v8) 64-bit SoC @ 1.8GHz VS Quad‑core Arm® Cortex®‑A55 (Armv8) 64‑bit @ 1.6GHz).
 
ZioMario said:
Don't read about the RaspBerry. I stopped using it. I have exchange it with the Radxa Zero 3W because it's more low profile and it is powerful as the Raspberry Pi 4 (Broadcom BCM2711, Quad core Cortex-A72 (ARM v8) 64-bit SoC @ 1.8GHz VS Quad‑core Arm® Cortex®‑A55 (Armv8) 64‑bit @ 1.6GHz).
Click to expand...
Thank you for the tip! Much appreciated :)

I am going to read about it and see if i can offer something helpful. I am not really a hands-off kind of guy. I usually have to have the system to find resolutions. I have spent most of my computing life hands-on. I once repaired a Nintendo-DS handheld system but i wouldn't be able to do that by instruction. LOL. However, maybe another person reading and looking into the problem will help find a resolution...
 
johnjohn said:
Thank you for the tip! Much appreciated :)

I am going to read about it and see if i can offer something helpful. I am not really a hands-off kind of guy. I usually have to have the system to find resolutions. I have spent most of my computing life hands-on. I once repaired a Nintendo-DS handheld system but i wouldn't be able to do that by instruction. LOL. However, maybe another person reading and looking into the problem will help find a resolution...
Click to expand...

The solution is to enable the drm patches on arm64,to be able to use the GPU of the board. Unfortunately these patches work only for a special version of FreeBSD,vers.14-current at commit c9e023541aef. They should be fixed and upgraded to work with FreeBSD 14.3. A developer is needed,I'm not. I asked help to the ML,no one replied. I've emailed the creator of those patches (Emanuel Vadot),he didn't reply at all. No one cares. Maybe because there isn't a real interest to improve the desktop abilities of FreeBSD ?
 
ZioMario said:
The solution is to enable the drm patches on arm64,to be able to use the GPU of the board. Unfortunately these patches work only for a special version of FreeBSD,vers.14-current at commit c9e023541aef. They should be fixed and upgraded to work with FreeBSD 14.3. A developer is needed,I'm not. I asked help to the ML,no one replied. I've emailed the creator of those patches (Emanuel Vadot),he didn't reply at all. No one cares. Maybe because there isn't a real interest to improve the desktop abilities of FreeBSD ?
Click to expand...
ZioMario well, covacat has the patches, so calm down :)

I have a book about writing device drivers for FreeBSD, which i read in my spare time. I am new to this aspect of programming (i am a php programmer). I am learning C and C++ in my sparetime. I've already coded a clock app and i'm working on panel from scratch (while looking at panel source code to guide me along.) But i am a long way off from being useful at this level. I hope to contribute to FreeBSD in the future. I love this system. My Dad used to say: don't just watch, grab a tool and get your hands dirty. I think that it is a good message to anyne using FreeBSD (get your hands dirty).

Also, sometimes it can be extremely difficult to read someone elses code and make sense of it. Honestly. Maybe there is software currently being ported/patched but it could take alot of time. Especially if someone is working in spare time. The open source community often takes a ton of abuse from entitled desktop users, which only leads to more Windows and more Mac (where the developers get paid to make things work and the users get screwed because things just work).

I see that you posted at radxa forums about this and also about the display driver. I also see that noone replied to the display driver. I saw the suggestion to use the FreeBSD amd64 image. Maybe covacat's patches will work and you can Thank covacat for solving the problem. In any event, FreeBSD is naturally ignored by BigTech because BigTech is threatened by 'The Beast'. When more users migrate to 'The Beast', things will be much different... but please try to not pressure developers to make things work. FreeBSD is a great system with a great community and things are getting better everyday with this system. Slow but steady.
 
johnjohn said:
ZioMario well, covacat has the patches, so calm down :)

I have a book about writing device drivers for FreeBSD, which i read in my spare time. I am new to this aspect of programming (i am a php programmer). I am learning C and C++ in my sparetime. I've already coded a clock app and i'm working on panel from scratch (while looking at panel source code to guide me along.) But i am a long way off from being useful at this level. I hope to contribute to FreeBSD in the future. I love this system. My Dad used to say: don't just watch, grab a tool and get your hands dirty. I think that it is a good message to anyne using FreeBSD (get your hands dirty).

Also, sometimes it can be extremely difficult to read someone elses code and make sense of it. Honestly. Maybe there is software currently being ported/patched but it could take alot of time. Especially if someone is working in spare time. The open source community often takes a ton of abuse from entitled desktop users, which only leads to more Windows and more Mac (where the developers get paid to make things work and the users get screwed because things just work).

I see that you posted at radxa forums about this and also about the display driver. I also see that noone replied to the display driver. I saw the suggestion to use the FreeBSD amd64 image. Maybe covacat's patches will work and you can Thank covacat for solving the problem. In any event, FreeBSD is naturally ignored by BigTech because BigTech is threatened by 'The Beast'. When more users migrate to 'The Beast', things will be much different... but please try to not pressure developers to make things work. FreeBSD is a great system with a great community and things are getting better everyday with this system. Slow but steady.
Click to expand...

Nothing to say against covacat. But I'm not sure if its good to don't upgrade for years the drm code,that's a very important key to push FreeBSD to be more user friendly as well as don't give any answer to whom want to ask some questions or wants to collaborate. The code,the efforts should taken into greater consideration for the good of everyone. Someone should push more to add it in the mainline. But what I see is that no serious and senior developer cares too much.
 
I don't know if it is relevant or not,but I suppose that your kernel has been built with the PinebookPRO display in "mind". There is a chance that it will not boot if I use the Jared McNeil UEFi code ? Because I'm using only HDMI "monitors". For this reason I should keep this partition structure intact :

Code: 
Disk /dev/sdf: 119.08 GiB, 127865454592 bytes, 249737216 sectors
Disk model: MassStorageClass
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 07D2637F-2E74-11F0-832C-F1B721F986A1

Dispositivo  Start      Fine   Settori  Size Tipo
/dev/sdf1       64     20479     20416   10M Linux filesystem
/dev/sdf2    20480     30719     10240    5M Linux filesystem
/dev/sdf3   131072    196607     65536   32M EFI System
/dev/sdf4   196608 249737175 249540568  119G FreeBSD UFS

Do you remember it,right ? What I will do is to exchange the kernel dir inside the "sdf4" partition. I will not touch the rest of the sd card,otherwise the UEFI bootloader will break.
 
ZioMario said:
Unfortunately these patches work only for a special version of FreeBSD,vers.14-current at commit c9e023541aef.
Click to expand...
No that is not quite right. I bet these patches lasted a while on the -CURRENT branch of 14.
I have some old -CURRENT files saved if you want I can see if I have any after that commit.
I would think something from a month or two after would be OK.

Didn't I see another programmer making changes a year after that repo was born? Look at latest commits.
I was assuming evadot@ was hoping somebody would take over after he launched this project. He has a very full basket.
He is mister u-boot for us along with major Arm contributions.
 
the (original) drmsubtree patches create a new kernel config file named GENERIC-DRM which supports all the arm64 boards
thats what i built
 
Phishfry said:
No that is not quite right. I bet these patches lasted a while on the -CURRENT branch of 14.
I have some old -CURRENT files saved if you want I can see if I have any after that commit.
I would think something from a month or two after would be OK.
Click to expand...

Man. I want to say that when i tried to compile the code,it didn't compile. So there is something that has not upgraded in the while. I'm sure that it could work,but you should put your hands on the code. I expected that the code was upgraded until 14.2 / 14.3 and that it worked out of the box. Why ? because in my vision it's a piece of code important to improve the multimedia skills of FreeBSD....on arm64. Arm64,the architecture most used for the phones / handheld of today,where FreeBSD should try to improve more.
 
ZioMario said:
Why ? because in my vision it's a piece of code important to improve the multimedia skills of FreeBSD.
Click to expand...
I think many of the early adopters of Arm boards were not interested in multimedia on Arm.

On top of that how many people on the forum even tried to use the Panfrost driver on FreeBSD? Very low numbers.

Maybe evadot@ was ahead of the times but nobody was there to take the baton. He can only wear so many hats at one time.
 
A developer replied on the ML :

Code: 
if you can use RELENG/14.0 you can have a look here :

https://github.com/jsm222/drm-subtree/tree/14

Last time (three weeks ago or smt) I tried it one the pinebook pro mesa
did not pick it up though.
also you can read:

https://freebsdfoundation.org/wp-content/uploads/2022/04/FreeBSD-on-the-Pinebook-Pro.pdf

regards

I hope it is of some help...
 
ZioMario said:
I hope it is of some help...
Click to expand...
Did you try 14.0-RELEASE? Should be simple. Unless drm-subtree was cut right before 14.0-R I would doubt it works. Infact a tree change the next day could have killed the whole thing.
I am just guessing it lasted a month or two.
You never know until you test old versions.
 
Phishfry said:
Did you try 14.0-RELEASE? Should be simple. Unless drm-subtree was cut right before 14.0-R I would doubt it works. Infact a tree change the next day could have killed the whole thing.
I am just guessing it lasted a month or two.
You never know until you test old versions.
Click to expand...

yes. My HDMI monitor didn't turn on. For this reason I created this post :

ZioMario

Post in thread 'Firefox installed from packages on my RaspBerry Pi Zero crashes every time I launch it...'

I don't know if it is relevant or not,but I suppose that your kernel has been built with the PinebookPRO display in "mind". There is a chance that it will not boot if I use the Jared McNeil UEFi code ? Because I'm using only HDMI "monitors". For this reason I should keep this partition structure intact :

Code: 
Disk /dev/sdf: 119.08 GiB, 127865454592 bytes, 249737216 sectors
Disk model: MassStorageClass
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier...
 
In addition,I tried to swap the kernel dir used by the Radxa Zero 3W with the kernel dir produced by covacat. In this case the error is "kernel not found". I will try again,maybe with the sd card where I have installed FreeBSD for the RockPro and not with FreeBSD installed for the radxa zero.
 
It looks like jsm has a repo that was forked to work on 14.0-RELEASE ?

I think he was the person who stepped in and did work on it one year after repo was born. He must have forked it at some point.
 
You must log in or register to reply here.
Back
Top