• @naobsd

    Doing dd for every kernel update seems highly destructive.
    dd if=boot.img of=/dev/mmcblk0p1 conv=sync,fsync seek=ROCK2SQUARE????$((0x2000????+0xc000?????))

    I am also noting here we still have a separate partition for boot.
    It would be most convenient to have the boot partition and the / partition to be the same.
    Is it absolutely necessary they be different?
    Could we simply have the boot img also contain the entire rootfs and point it to the current rootfs
    located in /dev/mmcblk0p2? Then let grub2 boot image selection. The intel-based grub2 expects all kernels to reside in /boot. The grub2 configuration is held within /boot/grub holding a list of available kernels sitting on the one and only / partition at the location /boot.
    Using this technique, dd is no longer necessary. The boot happens and always points to the same partition and always points to I believe grub2 on the "/" partition which then loads and runs the desired kernel. It's also convenient to have grub2 provide a list of different kernels because if the latest installed kernel is a flaky alpha and fails to boot, simply rebooting and selecting another kernel within the grub2 menu brings up the system without issue and provides an easy way of repairing the system without having to reflash the entire emmc which is currently the only option ROCKCHIP/RADXA propose.

    That brings another question: grub2 for rockchip kernels. Are there any people working on this?

  • Ok, i figured out wifi, here a short guide

    wget http://build.radxa.com/rabian/nightly/rock_pro/150902/rockdev/modules/lib/modules/3.0.36+/kernel/drivers/net/wireless/rtl8723au_lwfinger/8723au.ko install -p -m 644 8723au.ko /lib/modules/3.0.36+/kernel/drivers/net/wireless/ depmod -a sudo modprobe 8723au ifconfig

    update: unfortuntely that is not enough, im no able to list the wireless networks around me but find myself unable to bring wpa_supplicant up

    wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf -ddddd root@kali wpa_supplicant v2.3 random: Trying to read entropy from /dev/random Successfully initialized wpa_supplicant Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'default' ctrl_interface 'N/A' bridge 'N/A' Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf' Reading configuration file '/etc/wpa_supplicant.conf' ctrl_interface='/var/run/wpa_supplicant' Line: 2 - start of a new network block ssid - hexdump_ascii(len=11): 50 61 72 61 64 69 73 65 4e 65 74 ParadiseNet PSK (ASCII passphrase) - hexdump_ascii(len=15): [REMOVED] PSK (from passphrase) - hexdump(len=32): [REMOVED] Priority group 0 id=0 ssid='ParadiseNet' nl80211: Could not add multicast membership for vendor events: -2 (No such file or directory) rfkill: initial event: idx=0 type=2 op=0 soft=1 hard=0 nl80211: Remove monitor interface: refcount=0 netlink: Operstate: ifindex=5 linkmode=0 (kernel-control), operstate=6 (IF_OPER_UP) nl80211: Set mode ifindex 5 iftype 2 (STATION) nl80211: Failed to set interface 5 to mode 2: -19 (No such device) wlan0: Failed to initialize driver interface Failed to add interface wlan0 wlan0: Cancelling scan request wlan0: Cancelling authentication timeout

    Can someone help?

  • please use sudo su as user rock, root password is random by default.

  • @iandrei

    You can either:

    1). replace the rock pro with rock from us, and buy the lcd for rock pro from us.

    2). use the hdmi display from your link.

    it depends on you. 1) is more expensive but you have touch input. 2) is more flexible since hdmi display is universal.

  • posted in Android by DayWalker

  • @hipboi
    Hi , I am unable to use GPIO j12p33 can u help me in this ?

    As when I am using same code for j12p31 it's working but same code is not working for pin j12p33 and j12p37 . One difference that I found is these two pins has MUX. Functions as compared to j12p31

  • posted in Linux by marcmateumateus

    @ulgenanil said:


    Yes, this option is enabled, i have also tried to compile the kernel with this option as a module, but the same result
    This is my .config (just the SPI part):
    //# CONFIG_SPI_DEBUG is not set
    //# SPI Master Controller Drivers
    //# CONFIG_SPI_ALTERA is not set
    //# CONFIG_SPI_BITBANG is not set
    //# CONFIG_SPI_GPIO is not set
    //# CONFIG_SPI_OC_TINY is not set
    //# CONFIG_SPI_PXA2XX_PCI is not set
    //# CONFIG_SPI_XILINX is not set
    //# CONFIG_RK_SPIM_TEST is not set
    //# CONFIG_LCD_USE_SPIM_CONTROL is not set
    //# CONFIG_SPI_DESIGNWARE is not set
    //# SPI Protocol Masters
    //# CONFIG_SPI_TLE62X0 is not set

    PD: I have added the '//' in the text in order to preview it correctly

  • I've spent pretty much my entire day trying to unbrick my old MK802IV ... bless this conversation here for saving the day.

    I had to use the registry hack mentioned on that linked page to get the Rockchip USB to be seen in Windows 10 (same for 8.1 I understand)

    From Zarek over on that site (in case the link ever breaks in the future) -

    *I too have experienced this problem recently, and unfortunately the solution described here doesn't worked for me .

    But I solved the problem by editing directly the Windows registry.

    I share my solution, I hope this can serve someone:
    1- Install the driver provided with the firmware
    2- Connect the X7 with the reset manipulations
    3- At this state, Windows 8.1 detects the device, but indicate an error 43
    4- Edit the Windows registry (in command line: regedit)
    5- Go to HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/usbflags/2207310B0100
    The device number (last part) may be different, but I think it is the same for all Minix Neo X7.
    6- Add a new DWORD 32bit value, with the name SkipBOSDescriptorQuery and the value 1
    7- At this state the device may be correctly detected by Windows. Redo the reset manipulations if necessary.
    8- Add the line in the config.ini file of the flashing tool as describe in the previous message: SUPPORTLOWUSB=TRUE
    9- Flash your device

    This method tell to Windows to not check the USB BOS descriptor. It is not well contruct within USB's standard and this is only check since Windows 8.1. This is why this problem doesn't occur in previous Windows versions.

    Note that I had to redo the reset step several times. Indeed, the device would disconnect after a few minutes.

    I hope this will save you waste of time on this :)*

    (The stuff between the asterisks above is supposed to be italicized to help it stand out as a quote since there is no quote function here it appears, but it doesn't seem to be working)

    The above config.ini statements worked great for me for RK BatchTool, but I was trying to flash linuxium which isn't supported by it, and adding those commands to any of the files in RK Android Tool does NOT work. What DID work, which I found on some foreign language site that I couldn't understand, but was at least able to pick config lines out of is setting -


    in the setting.ini file for RK Batch Tool!

    Thought I was going to be throwing this thing in the garbage and buying a Pi! Thanks for saving me ~$100!

  • Gonna try this source: https://github.com/olegk0/rk3x_kernel_3.0.36

    Failed too: same errors

  • Still very bad support for radxa products

  • I checked and the antenna matches.

    In dmesg sometimes i'm getting "fw download fail" at boot.

  • posted in Linux by hipboi

    audio is still very weak though, i thought the rock pro had an amplifier compared to the rock...

  • Thanks i'll try

  • solved!
    it is really the problem of the Windows linebreaks in the source files, why-ever it became a problem only now and seemingly only for me.

    my fix, in case anyone else runs into the same errors:
    install "dos2unix" binary, e.g.

    sudo apt-get install dos2unix

    write a script e.g. named d2u.sh, make it executable and place it above the source directory (into the directory in which you gave the "git clone" command), with the following content:

    #! /bin/bash set -x for i in $(find -type f) do dos2unix -o $i done

    the set -x part is to see what is happening.

    run it with ./d2u.sh from the same directory


  • @hipboi - my ssid is just letters and numbers no spaces, special characters, etc.

Internal error.

Oops! Looks like something went wrong!