Welcome, Guest |
You have to register before you can post on our site.
|
Forum Statistics |
» Members: 29,473
» Latest member: Samliams
» Forum threads: 16,196
» Forum posts: 116,880
Full Statistics
|
|
|
cedar_ve driver not able to allocate memory |
Posted by: ajellisuk - 11-19-2021, 05:59 AM - Forum: General Discussion on PineCube
- Replies (14)
|
 |
Hello
I have been trying to make use of the h264 encoder by obtaining the source code for the cedar_ve driver from here:
https://github.com/uboborov/sunxi-cedar-mainline
I have successfully built the driver, but when I try and load it the driver fails with the error in the kernel log:
Quote:[ 110.831285] sunxi-cedar 1c0e000.video-engine: could not assign reserved memory, ret: -22
I have checked the device tree to ensure that it is consistent with the sources in the above git repository.
I'm not sure why the driver is not able to allocate the needed memory. I have tried setting the CMA pool both from the boot parameters by adding:
Quote:setenv bootargs "${bootargs} cma=60M"
to boot.cmd and rebuilding before rebooting.
I have also tried adding this to my device tree:
Code: reserved-memory {
#address-cells = <1>;
#size-cells = <1>;
ranges;
/* Address must be kept in the lower 256 MiBs of DRAM for VE. */
cma_pool: cma@44000000 {
compatible = "shared-dma-pool";
size = <0x6000000>;
alloc-ranges = <0x4a000000 0x6000000>;
reusable;
linux,cma-default;
};
};
I updated the video engine entry in the deivce tree to that it referenced the cma_pool entry:
Code: ve: video-engine@01c0e000 {
compatible = "allwinner,sunxi-cedar-ve";
reg = <0x01c0e000 0x1000>,
<0x01c00000 0x10>,
<0x01c20000 0x800>;
memory-region = <&cedar_buf>;
syscon = <&syscon>;
clocks = <&ccu CLK_BUS_VE>, <&ccu CLK_VE>,
<&ccu CLK_DRAM_VE>;
clock-names = "ahb", "mod", "ram";
resets = <&ccu RST_BUS_VE>;
interrupts = <GIC_SPI 58 IRQ_TYPE_LEVEL_HIGH>;
allwinner,sram = <&ve_sram 1>;
};
But I still get the same error.
Has anyone successfully managed to get the cedar_ve driver to work on a pine cube? Is there a set of instructions that someone could point me to that will help me resolce this issue.
Andrew
|
|
|
setting a fixed Mac address on a PineCube |
Posted by: ajellisuk - 11-19-2021, 04:59 AM - Forum: General Discussion on PineCube
- Replies (3)
|
 |
Hello
I have got a PineCube running Armbian, and is also using Uboot 2021.07-armbian.
I have found that the mac address keeps changing, and consequently the ip address keeps changing too. This is a real nuiscence.
I have looked for a soltution to this problem, and found some ideas on the One64 forum. Unforutnately the suggestions there didn't work for me on the PineCube.
I have tried adding these to /boot/boot.cmd (no both at once)
Code: setenv bootargs "${bootargs} ethaddr=7e:50:d1:01:57:68"
setenv bootargs "${bootargs} mac_addr=7e:50:d1:01:57:68"
If I do
Quote:cat /proc/cmdline
I can see that the parameters are passed to the kernel, but are not being acted upon.
I have also tried adding these to /boot/armbianEnv.txt
Code: mac_addr=7e:50:d1:01:57:68
ethaddr=7e:50:d1:01:57:68
Again not both at once.
Can someone please tell me what I need to do to get the mac address to remain the same on subsequent boots.
Thanks in advance
Andrew
|
|
|
Help how to mount SD-Card |
Posted by: chadwick - 11-19-2021, 04:09 AM - Forum: PostmarketOS on PinePhone
- Replies (8)
|
 |
Hi All,
On a linux desktop, one way to access your device is to edit the "/etc/fstab" to mount your device permanently so you can access it.
Reading postmarketOS's wiki about fstab, it told you to activate "rc-update" and the localmount service, which is the command:
Code: sudo rc-update add localmount default
And to check whether the service is running:
Code: rc-service localmount status
While blkid will return nothing, I use "sudo fdisk -l" to identify the UUID of the SD-Card, which gives:
Code: Disk /dev/mmcblk0: 59.48 GiB, 63864569856 bytes, 124735488 sectors
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: Disk /dev/mmcblk0: 59.48 GiB, 63864569856 bytes, 124735488 sectors
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: DC11BA49-9C6F-4BC0-B775-E39576550622
Device Start End Sectors Size Type
/dev/mmcblk0p1 2048 1050623 1048576 512M EFI System
/dev/mmcblk0p2 1050624 124733439 123682816 59G Microsoft basic data
Device Start End Sectors Size Type
/dev/mmcblk0p1 2048 1050623 1048576 512M EFI System
/dev/mmcblk0p2 1050624 124733439 123682816 59G Microsoft basic data
Therefore, I edit my fstab to looks like the following:
Code: UUID=DC11BA49-9C6F-4BC0-B775-E39576550622 /home/user/SDCard vfat defaults 0 0
On a reboot it did not give me anything in the folder. Upon the failure, I tried to mount the SDcard by using the mount command, which return error:-
Code: sudo mount -t vfat -o ro /dev/mmcblk0p2 ~/SDCard
mount: /home/user/SDCard: wrong fs type, bad option, bad superblock on /dev/mmcblk0p2, missing codepage or helper program, or other error.
My question is, is there something wrong with what I did or anything that I might not have been aware of?
Cheers.
Chadwick
|
|
|
Phone suddenly unusable |
Posted by: TRS-80 - 11-18-2021, 06:51 PM - Forum: Mobian on PinePhone
- Replies (6)
|
 |
My phone was purchased as KDE Community Edition, but after initial distro-hopping, I settled into Mobian stable.
At that time phone calls would drop some times, but most of the time they did work. I was more or less happy with it as a daily driver (in terms of a phone, anyway).
4G worked, even VoLTE worked (to my surprise!).
Then, maybe a week ago, I changed a couple things at the same time:
- I upgraded Mobian to Bookworm.
- I changed my SIM and carrier.
- I may have even bent one of SIM pins in the process (not sure though, maybe not).
2. From a T-Mobile MVNO (Walmart Family Mobile) to MetroPCS (now Metro by T-Mobile).
3. Yes I realize this fact makes other troubleshooting difficult if not impossible.
What I did not change:
- I never changed any firmware from stock.
- I never changed kernel from default.
Ever since then, I can barely make phone calls. They often drop right away, or a few to several seconds into the call. Some times I can complete a phone call. But it's basically unusable now.
One thing I have noticed, is that the phone seems to want to change from 4G to 3G when making a call now.
So, I have been reading up on firmware and other things, and I am not sure what I should do next? Any advice / help will be greatly appreciated.
|
|
|
Failure day 1 |
Posted by: Shadowarez - 11-18-2021, 06:45 PM - Forum: General Discussion on Pinecil
- No Replies
|
 |
Was so excited to finally get my hands on one of these they were being scalped and outa stock for nearly 6 months straight.
When I was finally able to buy I bought 2 the pine desktop power station the usb C cable extra tips the stand the works.
It gets here I proceed to use the USB C cable it powers on I go to attempt first project it will not heat up past 23 c max temp 35c.
1 checked out YT videos on this from every video iv seen they plug it in click the - button and there off to the rceztit heats up and it's going.
2. This sits at 23 c no matter what I try doesn't bother heating up so I thought maybe one of the pine device's has failed so I ordered a labtop brick with voltage control.
3. Waited 3 weeks for it to arrive test it same result will not heat up at all powers on bit won't heat up like every video I seen on this.
Anyone else have this issue?
|
|
|
Issues with External Display After Recent Update |
Posted by: reundo - 11-18-2021, 06:37 PM - Forum: General Discussion on Pinebook Pro
- No Replies
|
 |
I have recently started using my Pinebook Pro with a Dell usb-c dock and 4k external display. After updating the computer this evening (it had been a week or two) and plugging it back into the dock after restarting it my bluetooth stopped working and about the right third of the external display is showing only static (built-in display still works without issues). I was never able to get it to boot properly attached to the dock, I have always had to plug it back in after logging in.
After fiddling with the bluetooth and several restarts, it's working again. However, the external display is still showing static on the right side. I have tested another laptop with the dock and external display and there are no issues.
Any thoughts or suggestions? Anything else I can troubleshoot or test? My first thought is a hardware issue (I have used the usb-c ports only a handful of times so far), but it seems weird that it started just after an update. I would really like to get it working with my external display again. It makes the experience so much better.
|
|
|
Android SDK download |
Posted by: keaton - 11-18-2021, 06:23 PM - Forum: Android on Quartz64
- Replies (2)
|
 |
where else can i download the SDK? the direct from pine64 is limiting me to 163Kb/s and now it keeps failing at 19GB. saying it will take me 6days to download and i have a 1Gb/s internet connection.
also facing the same problem for the linux SDK....
is there a GIT hub for this?
|
|
|
Run From SD Card |
Posted by: keaton - 11-18-2021, 03:04 PM - Forum: Android on Quartz64
- Replies (1)
|
 |
hello,
how can I run from only the SD card? the images i found are eMMC only and I do not have one.
My goal is to get the CSI port up and running with my work products. I need the ability to send i2c commands via GPIO header to other devices that we manufacture.
end target of this is to show other tier1 manufactures our parts with a mock car head unit.
Currently downloading the android SDK from pine but it is slow to get. 233Kb/s
|
|
|
How to recover static libraries through jumpdrive |
Posted by: pineuser0 - 11-18-2021, 11:15 AM - Forum: Arch Linux on PinePhone
- Replies (4)
|
 |
A while ago my pinephone had seemed to had have wifi, bluetooth, gsettings, and various other services disabled that I've addressed in my most recent few threads.
I currently have the phone connected to a pc through jumpdrive and have the / directory accessible. How can I recover the installation of arch-phosh.
|
|
|
|