So as a compare here is th info from my board,
[nsollars@archrock ~]$ lsusb -vv
Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Couldn't open device, some information will be missing
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB
I have a usb3 to sata drive, il run some speed tests and get the
information for you using this later kernel.
Il dig up what the dtc/dtb used is also ( most likely itle be pretty default )
Nige
On Thu, Nov 28, 2019 at 9:51 AM aghart...@gmail.com wrote:
>
> Hi all,
>
> About USB3, seem that
Hi all,
About USB3, seem that Fedora w/kernel 5.3.7-301 see usb 3 port as usb
1.1
See below, the first BUS row is very clear.
lsusb -vvv
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Device Descriptor:
bLength 18
bDescriptorType 1
Hi Benson,
see below
Il 28/11/19 13:19, Benson Muite ha scritto:
On 11/28/19 2:37 PM, aghart...@gmail.com wrote:
Hi Benson,
I'm really new in Pagure.
So am I. It seemed ok, once uploaded an ssh key, could then use
command line git interface. Web interface seems limited compared to
On 11/28/19 2:37 PM, aghart...@gmail.com wrote:
Hi Benson,
I'm really new in Pagure.
So am I. It seemed ok, once uploaded an ssh key, could then use command
line git interface. Web interface seems limited compared to
Gitlab/Github, but it is better integrated with Fedora infrastructure.
On 11/28/19 2:37 PM, aghart...@gmail.com wrote:
Hi Benson,
I'm really new in Pagure.
So am I. It seemed ok, once uploaded an ssh key, could then use command
line git interface. Web interface seems limited compared to
Gitlab/Github, but it is better integrated with Fedora infrastructure.
On 11/27/19 5:00 PM, Nigel Sollars wrote:
Well done!,
I was waiting to see how this one went. in the meantime Arch pushed
out a 5.4.0-1 kernel,
archrock 5.4.0-1-ARCH #1 SMP
[ 0.00] Linux version 5.4.0-1-ARCH (builduser@leming) (gcc
version 8.3.0 (GCC)) #1 SMP Tue Nov 26 02:44:10
Already to 5.4.0?!?! WO-HA!
Now I'm playing with rock64, some feedbacks:
* USB3 port seems not working.
* I have some problem with df-update and " The operation would result
in removing the following protected packages: systemd-udev"still
investigate.
I'll keep you up-to-date.
Well done!,
I was waiting to see how this one went. in the meantime Arch pushed out a
5.4.0-1 kernel,
archrock 5.4.0-1-ARCH #1 SMP
[0.00] Linux version 5.4.0-1-ARCH (builduser@leming) (gcc version
8.3.0 (GCC)) #1 SMP Tue Nov 26 02:44:10 UTC 2019
[0.00] Machine model: Pine64
OH GUYS! WHAT A BEAUTIFUL DAY!
Finally I've found the solution!
So,*_first for all SPI flash should be ERASED_*: fedora aarch64 does
not have spi boot images (at 2019-11-27). To erase spi follow this link:
Interesting thing.
Following Your idea, i've dowloaded the spi boot
https://github.com/ayufan-rock64/linux-u-boot/releases/download/2017.09-rockchip-ayufan-1065-g95f6152134/u-boot-flash-spi-rock64.img.xz
After decompressing it, if I do a 'cfdisk u-boot-flash-spi-rock64.img' I
can see sectors
Could you not grab the uboot and what nots from Ayufan,
https://github.com/ayufan-rock64/linux-u-boot
( perhaps build and test ), my original build ( current ) used this method..
Nige
On Thu, Nov 14, 2019 at 8:51 AM aghart...@gmail.com wrote:
>
> I'm seriously thinking that the problem is how
I'm seriously thinking that the problem is how u-boot images are created.
I've searched inside usr/share/uboot/rockpro64-rk3399/ of sd-card, same
chip manufacturer. FYI all series of 3399 have same content (rock960,
rock-pi-4, roc, puma, orangepi, etc.. see usr/share/uboot filder).
The
I've found this thread:
http://u-boot.10912.n7.nabble.com/help-with-serial-on-the-rockchip64-td384563.html
Seems seek value for dd are correct.
sudo dd if=idbloader.img of=/dev/mmcblk0 seek=64
sudo dd if=u-boot.itb of=/dev/mmcblk0 seek=16384
The question is if idbloader was built dorm mmc or
I can tell you I have disabled the SPI Flash ( 128mb iirc ) and give
SPI control back to SPIDEV as I am using this board in conjunction
with a 915Mhz LoraWan Concentrator / Gateway board IC980a
Nige
On Wed, Nov 13, 2019 at 8:00 AM aghart...@gmail.com wrote:
>
> Many Thanks!
>
> Here my minicom
Many Thanks!
Here my minicom output
CTRL-A Z for help | 150 8N1 | NOR | Minicom 2.7.1 | VT102 | Offline
| ttyUSB0
Thanks again,
Agharta
Il 13/11/19 13:58, Nigel Sollars ha scritto:
Yes the output I gave you in my first post is a Rock64 4GB with a 64GB
eMMC running Arch Linux. I can
Yes the output I gave you in my first post is a Rock64 4GB with a 64GB
eMMC running Arch Linux. I can get you all the info you need when I
get back to the house.
Nige
On Wed, Nov 13, 2019 at 7:55 AM aghart...@gmail.com wrote:
>
> Hi all,
>
> Many thanks Nigel, but nope.
>
> This is the output:
Hi all,
Many thanks Nigel, but nope.
This is the output:
C`Ek�kh[j�C4Mkj_C6�n�4��Vj-[mC`�d[�6��K��RV%���]��UեUQR(�(��U*U�U��L�\� �ꨊ婪ժ�)U�UQQ
Q�ժw�UUQQQ���U�(J�*�(�U*�e�E���
U� �WE���i���+� �
�UU(�UU�i+�*��*���Uj�*�E�*�J���BZ���U��.�ծ�(���U��UTQQ���i-���U��UTQQ�%��(��u,�U��
On 11/13/19 2:29 AM, Nigel Sollars wrote:
Serial console / uart setup,
150 8n1
Thanks Nigel.
Nige
Agharta, Please let us know if it works, and if so can you contribute to
the Pagure repository?
On Tue, Nov 12, 2019 at 2:08 PM agharta agharta wrote:
Hi Benson,
No, unfortunately
Serial console / uart setup,
150 8n1
Nige
On Tue, Nov 12, 2019 at 2:08 PM agharta agharta wrote:
>
> Hi Benson,
>
> No, unfortunately seems not working.
>
> I've tried with seek (16348, 64, 512, etc). No luck.
>
> I think the problem is related how to boot images are builded.
>
> Should I
Hi Benson,
No, unfortunately seems not working.
I've tried with seek (16348, 64, 512, etc). No luck.
I think the problem is related how to boot images are builded.
Should I write sidbloader.img?
Following Your link about ARMv8, i see at row 3:
dd if=$PREFIX/usr/share/uboot/$TARGET/spl.img
Hi Benson,
No, unfortunately seems not working.
I've tried with seek (16348, 64, 512, etc). No luck.
I think the problem is related how to boot images are builded and 'what'
to write into sdcard.
Should I write sidbloader.img or not? How are sidbloader.img and
u-boot.itb builded? Does
Hi Agharta,
Thanks for the update. Responses below. Hope you are successful.
Benson
On 11/11/19 7:09 PM, aghart...@gmail.com wrote:
Hi Benson,
You helped me a lot!!!
Following Your suggestion, I've investigate over $TARGET and $MEDIA.
After writing sdcard with pine64-lts, inside
Hi Benson,
You helped me a lot!!!
Following Your suggestion, I've investigate over $TARGET and $MEDIA.
After writing sdcard with pine64-lts, inside usr/share/uboot/ (of
sdcard) i can see rock64-rk3328 (my sbc), rockpro64-rk3399 and many
other sbc not listed into arm-image-installer folder
Hi Agharta,
I used an earlier Fedora release on Banana pro (after first using Fedora
combined with a different kernel). It worked ok, but took a bit of time
for the Arm image to support Banana pro.
On 11/11/19 4:04 PM, aghart...@gmail.com wrote:
Hi Benson
a) Yes, but I can't specify
Hi Nige,
Thank Your for Your feedback.
I hope your testimony is useful for the realization of a precise guide
in Fedora about that.
Many thanks again.
Agharta
Il 09/11/19 12:40, Nigel Sollars ha scritto:
Hi,
So my rock64 is running Arch on a 64G eMMC ( Self built uboot / dtc's
) since
Hi Benson
a) Yes, but I can't specify Rock64 as --target parameter.
/"A number of Pine64 boards are supported, but you might use as a bass
to get something for rock64" /Can You explain me how? Is it possibile
without manual recompilation, etc...? (see why in b) and c) )/
/
b) Yes, an
Hi,
So my rock64 is running Arch on a 64G eMMC ( Self built uboot / dtc's
) since there was no guide / install path back then )), most likely
you have to dd uboot/boot loader manually try the arch install guide
steps to do that.
I would imagine Fedora would be good for SBC;s as they very much
On 11/9/19 10:44 AM, agharta agharta wrote:
Hi Benson,
Yes, i've successfully installed CentOs 7, take a look at this link
https://wiki.pine64.org/index.php/ROCK64_Software_Release#CentOS-7_Community_Build_Image_.5BmicroSD_Boot.5D
But CentOs 7 does not support PHP 7x for aarch64: i need to
Hi Benson,
Yes, i've successfully installed CentOs 7, take a look at this link
https://wiki.pine64.org/index.php/ROCK64_Software_Release#CentOS-7_Community_Build_Image_.5BmicroSD_Boot.5D
But CentOs 7 does not support PHP 7x for aarch64: i need to install
nextcloud and PHP 7+ is required.
So,
On 11/7/19 11:53 AM, agharta agharta wrote:
Hi Peter,
Thank you for your support.
Currently I'm trying to write fedora to sd card with this command:
fedora-arm-image-installer --addconsole
--image=Fedora-Minimal-31-1.9.aarch64.raw.xz
--media=/dev/sdd --resizefs
So, at the end the tool tells
> Hi Peter,
> Thank you for your support.
>
> Currently I'm trying to write fedora to sd card with this command:
> fedora-arm-image-installer --addconsole
> --image=Fedora-Minimal-31-1.9.aarch64.raw.xz
> --media=/dev/sdd --resizefs
>
> So, at the end the tool tells me:
>
> = No U-boot will
Hi Peter,
Thank you for your support.
Currently I'm trying to write fedora to sd card with this command:
fedora-arm-image-installer --addconsole
--image=Fedora-Minimal-31-1.9.aarch64.raw.xz --media=/dev/sdd --resizefs
So, at the end the tool tells me:
= No U-boot will be written.
= No
> Hi all,
> I hope I wrote in the right place.
You are.
> I've see that Fedora 31 now supports Rock64 sbc.
It does.
> I've not found any guide to setup a sd card or any how-to boot Fedora 31
> with it.
I still need to update the documentation.
> In addition, Hdmi does not works form me,
34 matches
Mail list logo
