belfastraven

Members
  • Content Count

    15
  • Joined

  • Last visited

  1. belfastraven

    Ayfan's Rockchip 4.20.0 tag

    Thanks everyone for checking on this. In my case, I have narrowed the problematic devices down to USB storage devices (all are USB3--don't have any 2's). I've tested with the samsung T1, a WD Passport HD, a Sandisk USB stick--in no cases are they recognized by the rock64 on 4.20 On a RockPro64 (3399) with the 4.20 kernel. they are all powered on and recognized when I plug them in. I notice that the uas module is not loaded on the rock64 I boot the device with one of those plugged in. I tried force loading it using initramfs, and it loads, but the device(s) is still not available. As I mentioned before, I was actually booting from the Samsung t1 on the 4.19 kernel. If any one want to see logs--I have a great number of them :-). If noone else is seeing this, though, I just keep trying to figure out what is broken. thanks again.
  2. belfastraven

    Ayfan's Rockchip 4.20.0 tag

    thanks. I did try device in the bottom usb2 port and it still got no power. I'm going to try it on a powered hub to see if it is somehow a powersupply issue. I didn't notice any change in the device tree that would cause this.... .
  3. belfastraven

    Ayfan's Rockchip 4.20.0 tag

    Is any one else having problems with USB3 devices on rock64 with the 4.20 kernel? U-boot seems to recognize that the device (a Samsung T1 ssd) is there but once I get the kernel starting message there is no power to the device. I can boot the that device on the 4.19-rc4 kernel.
  4. FWIW, with my working hardware module, this is where the device enumerates. /sys/bus/sdio/devices/mmc1:0001:1 wlan0 show up in that directory tree. and there is this entry in the device tree: &mmc1 { pinctrl-names = "default"; pinctrl-0 = <&mmc1_pins>; vmmc-supply = <&reg_dldo4>; vqmmc-supply = <&reg_eldo1>; mmc-pwrseq = <&wifi_pwrseq>; non-removable; bus-width = <4>; status = "okay"; }; I just compiled a dtb with the bluetooth node, and will see what else it takes to make bluetooth work. vlad59 gave a lot of helpful information in his last post, also. I know that the wifi driver and firmware were loaded automatically at boot, once the hardware module was recognized. I notice that Bluetooth enabling can be done in armbian-config, but am not sure what has to be in place for that to work.
  5. Yes, I just tried another pine64 sdio adapter and device is now working. I don't know how I managed to kill the first one.. 5.433718] r8723bs: module is from the staging directory, the quality is unknown, you have been warned. [ 5.481983] RTL8723BS: module init start [ 5.481994] RTL8723BS: rtl8723bs v4.3.5.5_12290.20140916_BTCOEX20140507-4E40 [ 5.481997] RTL8723BS: rtl8723bs BT-Coex version = BTCOEX20140507-4E40 [ 5.522202] RTL8723BS: rtw_ndev_init(wlan0) [ 5.524817] RTL8723BS: module init ret =0 [ 10.488627] rtl8723bs: acquire FW from file:rtlwifi/rtl8723bs_nic.bin [ 14.397509] RTL8723BS: rtw_set_802_11_connect(wlan0) fw_state = 0x00000008 [ 14.535050] RTL8723BS: start auth [ 14.537783] RTL8723BS: auth success, start assoc [ 14.548427] RTL8723BS: rtw_cfg80211_indicate_connect(wlan0) BSS not found !! [ 14.548446] RTL8723BS: assoc success [ 14.558911] RTL8723BS: send eapol packet [ 14.580272] RTL8723BS: send eapol packet [ 14.618036] RTL8723BS: set pairwise key camid:4, addr:92:3b:ad:ad:a7:34, kid:0, type:AES [ 14.618588] RTL8723BS: set group key camid:5, addr:92:3b:ad:ad:a7:34, kid:1, type:AES I haven't checked bluetooth yet. It isn't defined in the megous linux DTS, but from Anarsouls-- Defined here in Anarsouls DTS /* On Wifi/BT connector, with RTS/CTS */ &uart1 { pinctrl-names = "default"; pinctrl-0 = <&uart1_pins>, <&uart1_rts_cts_pins>; status = "okay"; bluetooth { compatible = "realtek,rtl8723bs-bt"; reset-gpios = <&r_pio 0 4 GPIO_ACTIVE_LOW>; /* PL4 */ device-wake-gpios = <&r_pio 0 5 GPIO_ACTIVE_HIGH>; /* PL5 */ host-wake-gpios = <&r_pio 0 6 GPIO_ACTIVE_HIGH>; /* PL6 */ firmware-postfix = "pine64"; }; };
  6. Yes--and there isn't an overlay for it either. I'm looking around to see if I can find a dt somewhere which has a node for it... I'm very new to dt's :-)
  7. Re Pine64 WiFi. Using a USB Wifi adapter, WiFi is fine. The Wifi/bluetooth module told by Piine64 is not working. I can load the driver, but the SDIO device is not being enumerated. Still looking into the issue...
  8. Pine64+ is booting fine, Ethernet (wired isfine), still working investigating getting wireless (r8723bs) to work. Not sure about HDMI yet.
  9. Have been testing on a pineh64. kernel and uboot seem to be fine, but something is wrong with the device tree-- The original armbian build (the 4.18 rc7-(-from icenowy, I believe--booted), but no updates after that worked. I recompiled her tree from her 86-integrate-2-ugly branch and am booting fine (both from sd and eemc) I originally noticed a complaint about the simplefb node not being found, but after adding that node, I still got the same kernel oops. Before that oops, the boot logs look the same.... I'm hoping someone can see what is wrong. I'm afraid I'm really out of my element here. console_pine64h6.txt
  10. belfastraven

    Rock64 boot from SSD/HDD (attached via USB)

    I have not tried this with an armbiasn build, but am successfull using Ayufan's from a Samsung portable SSD attached via USB3 port, I had to use SPI flash for u-boot and enable a rootdelay (I am using 90 right now which is much longer than it needs to be) That would be one of the bootargs in the boot.cmd file, I would think. Not sure if can be added from armbianEnv.txt I know that rootwait is already one of the boot args, but I think that perhaps that rootdelay is perhaps called at a different point in startup. FWIW
  11. belfastraven

    problem booting pine64+ after 9/7 update (mainline)

    see the last post in this thread for a fix
  12. belfastraven

    pine64-mainline- won't boot after upgrade

    OK--I found a post in another thread from zador.blood.stained. which explains that the ftdname will now have allwinner/prepended to it .. So probably the best fix is to edit the boot.cmd file to remove the allwinner/ from the load command, and then recompile boot.cmd. This works for me. It seems that boot.cmd hasn't been getting updated since that change was made.
  13. belfastraven

    pine64-mainline- won't boot after upgrade

    Sorry--I didn't see this before I posted. I believe there is a bad definition somewhere of ftdfile (see my post on this same subject see this line File not found /boot/dtb/allwinner/allwinner/sun50i-a64-pine64-plus.dtb * with duplicate of Allwinner? look at the load line from the boot.cmd. I could not find where ftdfile was defined I got the system to boot by copying the allwinner directory into itself-- that way load will find the files (and overlays if they are being used)
  14. I have a feeling this was caused by a p[roblem with the definition of ftdfile variable: line from boot.cmd: load ${devtype} 0 ${fdt_addr_r} ${prefix}dtb/allwinner/${fdtfile} from the serial output: File not found /boot/dtb/allwinner/allwinner/sun50i-a64-pine64-plus.dtb ** note the duplication of Allwinner. Since I couldn't find where it was defined , I just copied the allwinner directory into itself.....:-) which fixed the problem. Perhaps someone could look into this? thanks.
  15. belfastraven

    Pine64: Not booting with vanilla kernel

    Newby question: should I put an apt-mark hold on u-boot after flashing over it? Main Line kernel is booting fine now but apt-get upgrade shows an upgrade for u-boot. I wasn't sure whether or not that was a fix or still the broken one. IS there a repository I should be monitoring for the fix? thanks.