| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,505
» Latest member: wonghammer
» Forum threads: 16,202
» Forum posts: 116,911
Full Statistics
|
| Latest Threads |
beta release of a Linux m...
Forum: General Discussion of PinePhone Pro
Last Post: coryholl
1 hour ago
» Replies: 1
» Views: 486
|
beta release of a Linux m...
Forum: General Discussion on PinePhone
Last Post: coryholl
1 hour ago
» Replies: 1
» Views: 829
|
beta release of a Linux m...
Forum: General Discussion on PineTab
Last Post: coryholl
1 hour ago
» Replies: 1
» Views: 622
|
Giving away a Pinebook Pr...
Forum: Pinebook Hardware and Accessories
Last Post: tuxifan
Yesterday, 04:16 AM
» Replies: 3
» Views: 1,389
|
Goolge banning Sideloaded...
Forum: General Discussion of PinePhone Pro
Last Post: zetabeta
08-27-2025, 11:59 AM
» Replies: 1
» Views: 879
|
What's stopping you from ...
Forum: General Discussion of PinePhone Pro
Last Post: teekay
08-26-2025, 11:48 PM
» Replies: 8
» Views: 1,395
|
Pinephone (Pro) Keyboard ...
Forum: PinePhone Accessories
Last Post: zetabeta
08-26-2025, 06:06 AM
» Replies: 3
» Views: 2,725
|
keyboard pogo pins part n...
Forum: General Discussion on PineTab
Last Post: starpp
08-26-2025, 04:34 AM
» Replies: 0
» Views: 953
|
google will take control ...
Forum: General
Last Post: zetabeta
08-25-2025, 03:14 PM
» Replies: 22
» Views: 10,514
|
Booting Issues
Forum: PineNote Software
Last Post: serenopolveroso
08-25-2025, 11:14 AM
» Replies: 19
» Views: 6,141
|
|
|
| tftpboot: efi_load_pe: Invalid DOS Signature |
|
Posted by: wirr - 05-17-2018, 11:24 AM - Forum: Linux on Rock64
- Replies (4)
|
 |
Hi all, I'm looking for help with tftp boot from SPI flash.
Booting from flash works fine, the rock boards load their pxelinux.0 from tftp. Then for some reason the bootloader seems to ignore my 'fdt /dtb' entry and requests /dtb/rockchip/rk3328-rock64.dtb.
After successfully loading this file it throws the following error:
Filename 'dtb/rockchip/rk3328-rock64.dtb'.
Load address: 0x1f00000
Loading: ####
1.8 MiB/s
done
Bytes transferred = 56922 (de5a hex)
## Starting EFI application at 02000000 ...
efi_load_pe: Invalid DOS Signature
## Application terminated, r = 9223372036854775806
Can someone provide any insight on why this happens and how to fix it?
Thanks!
For the sake of completeness here's my pxelinux.0:
default rock64-kernel-4.4
prompt 0
timeout 3
menu title Boot options
label rock64-kernel-4.4
kernel /Image
initrd /initrd.img
fdt /dtb
append earlycon=uart8250,mmio32,0xff130000 rw root=/dev/nfs nfsroot=${serverip}:/data/rootfs/rock64-1 rootwait init=/sbin/init mtdparts=spi32766.0:32k(system),4064k(loader),3840k(reserved),256k(vendor),4M(uboot),4M(atf)
|
|
|
|
| 3.5" HAT-style LCD available? |
|
Posted by: ElRobbo - 05-17-2018, 06:32 AM - Forum: Rock64 Hardware and Accessories
- Replies (3)
|
|
I ran into a problem with my Rock64 recovering from a power outage recently, and had to unravel it from its installation, plug it into a TV and reboot it there to diagnose.
The RPis have things like these screens available, often with a nice case to go with.
Does anyone have any experience with those or others? The drivers for those seem to be pre-built binaries specifically for the Rpi, so I doubt it would work.
Thanks,
R
I suppose I could just download the drivers and try them, see if they barf w/out hardware attached...
|
|
|
|
| approaches to safely trying custom kernels |
|
Posted by: pkivolowitz - 05-16-2018, 07:18 PM - Forum: Linux on Rock64
- No Replies
|
|
Hi All,
I am coaching two undergrads through a summer research experience doing a deep dive into Linux kernel hacking.
I expect we're going to break the kernel a whole lot. My first task is to master recovering from this gracefully.
Leveraging dim memory from the last time I did something like this (a VAX 11/780 with Berkeley Unix), multiple kernel images could reside on disk (including a known good image). The boot loader could be instructed which to load.
I suspect the process on the Rock64 is similar... Would you be willing to comment if I'm on the right track:
- add USB UART to board.
- ensure U-Boot is flashed
- boot into U-Boot ... select kernel image... boot
Does the FLASH come with U-Boot already present?
Thank you a lot - I am happy to answer any questions you might have about our project (introduce a multiple personality disorder into Ubuntu).
|
|
|
|
| Ubuntu password not working |
|
Posted by: joemassimino - 05-15-2018, 09:01 AM - Forum: Ubuntu
- Replies (4)
|
|
The first image I loaded on my R18 LTS board was Ubuntu 16.04.3 LTS. It loads fine, but the login credentials say to use ubuntu for the username, and ubuntu again for the password. Bu that does not work.
I tried rebooting the board several times, and I'm not a Newbie either. I expect that nobody is going to know why the passwords don't work, because support never re[plied when I asked them.
The first two lines that come to the screen are numbers with the words Trace.Call after them. What is that about, is the image notifying someone that I am using it? I'm not new to Linux, so that had to be added by whoever created the image.
In any case, has anyone any ideas about the Passwords for ubuntu not working?
Joe
|
|
|
|
| RFLink connected to /dev/ttyUSB0 not working |
|
Posted by: ulysse132 - 05-15-2018, 08:19 AM - Forum: Linux on Rock64
- Replies (9)
|
|
Hello,
I've build my own RFLink using an arduino. It work very well on RPi.
But I have problem to make it work on Rock64. It worked this morning but after a restart (sudo reboot), it didn't work anymore.
Domoticz is configured to connect to RFLink via /dev/ttyUSB0.
After the restart, I have this error :
Quote:Error: RFLink: Error opening serial port!
I have no idea to solve it. Could you please help me ?
I use ayufan's latest stable version of xenial linux.
On RPi, the solution was to add
to /boot/config.txt but there isn't any config.txt file.
Thanks a lot !
|
|
|
|
| unable to switch usb3 ports on |
|
Posted by: cglhu - 05-14-2018, 12:15 PM - Forum: Rock64 Hardware and Accessories
- Replies (6)
|
|
Hi all,
I have a problem with the usb3 ports. I run an arch linux installation on a rock64. I followed the instructions in this thread
https://forum.pine64.org/showthread.php?tid=5001
and that helped me to get usb2 ports working. But I can't do the same thing for the usb3 ports (toggle the right gpio to switch the regulator for usb3 on). Mostly I don't know, which gpio port belongs to the usb3 regulator.
Maybe someone can give me a hint.
Thanks in advance and
Best regards,
Christoph
|
|
|
|
| Some problems with kernel module und device tree.. |
|
Posted by: Osiander - 05-14-2018, 02:32 AM - Forum: General
- No Replies
|
 |
Hello guys,
I'm developing a kernel driver for a MOST NIC and have got some problems by reading the chip configuration from device tree.
Here is the configuration:
Code: &i2c2 {
pinctrl-names = "default";
pinctrl-0 = <&i2c2_pins_a>;
status = "okay";
os8104: os8104@41 {
compatible = "smsc,os8104";
reg = <0x41>;
master = <0>;
bypass = <0>;
gpio_reset = <&pio 8 17>; /* PI17 */
gpio_int = <&pio 8 16>; /* PI16 */
gpio_aint = <&pio 8 19>; /* PI19 */
gpio_error = <&pio 8 18>; /* PI18 */
};
};
My NIC (os8104) is connected to i2c-2.
And here is the corresponding code in LKM:
Code: static int os8104_probe(struct i2c_client *client, const struct i2c_device_id *id) {
struct device_node *dn;
int rc;
int master = 0, bypass = 0;
struct os8104 *priv;
dn = of_find_node_by_name(NULL, os8104_driver.driver.name);
if (dn == NULL) {
return -ENODEV;
}
rc = of_property_read_u32(dn, "master", &master);
pr_err("rc = %d, master = %11d\n", rc, master);
rc = of_property_read_u32(dn, "bypass", &bypass);
pr_err("rc = %d, bypass = %11d\n", rc, bypass);
priv = devm_kzalloc(&client->dev, sizeof(*priv), GFP_KERNEL);
if (!priv) {
return -ENOMEM;
}
priv->adapter = to_i2c_adapter(client->dev.parent);
priv->client = client;
priv->mode = val;
priv->gpio_reset = of_get_named_gpio(dn, "gpio_reset", 0);
priv->gpio_int = of_get_named_gpio(dn, "gpio_int", 0);
priv->gpio_aint = of_get_named_gpio(dn, "gpio_aint", 0);
priv->gpio_error = of_get_named_gpio(dn, "gpio_error", 0);
return 0;
}
If I'm loading the module, the function of_find_node_by_name find my os8104 node, then I'm able to read the both properties (master and bypass).
But, if I do an of_get_named_gpio(dn, "gpio_reset", 0), I get for each of four gpio-properties
Quote:[ 1610.330108] OF: /soc@01c00000/i2c@01c2b400/os8104@41: arguments longer than property
in dmesg.
Any ideas?
Kernel version is 4.14.39 and SBC is a BananaPRO (Allwinner A20 SoC).
Many thanks. 
|
|
|
|
| Screen flickering when playing multiple videos with rkximagesink |
|
Posted by: matwey - 05-14-2018, 02:10 AM - Forum: Linux on Rock64
- Replies (2)
|
|
Hello,
I am running gstreamer-rockchip-extra on Rock64 SBC (RK3328) with the following software. - Linux kernel 4.4.120-rockchip-ayufan-209
- gstreamer-rockchip-extra 1.10
- gstreamer-rockchip 1.10-5ayufan12
- librockchip-mpp1 1.4.0-1ayufan3-2
I try to run two H264 video simultaneously as the following:
Code: gst-launch-1.0 uridecodebin uri=file:///home/rock64/big_buck_bunny_480p_h264.mov ! rkximagesink
I see constant flickering in both windows. It seems that every other frame is replaced by black rectangle.
Short video explaining what I see is available at https://transfer.sh/j1PII/gst-rockchip.mp4
Here is initial github issue:
https://github.com/rockchip-linux/gstrea...a/issues/2
But people at #rockchip-linux IRC channel said that they do not reply at github and I have to report it here.
|
|
|
|
|
