Vlado Posted May 12, 2018 Posted May 12, 2018 To Igor Bit not understand why new 5.44 for nanoPC T3 plus not run. I see only first boot screen and then black always ???
Tido Posted May 12, 2018 Posted May 12, 2018 1 hour ago, Vlado said: not understand why new 5.44 for nanoPC T3 plus not run. SUITABLE FOR TESTING (WIP) are devices which we’re currently working on but they are not ready! These images are suitable for developers and experienced users. They are not very well tested but they might work without any problems. Your help to improve this situation is greatly appreciated.
Igor Posted May 13, 2018 Posted May 13, 2018 On 5/12/2018 at 2:51 PM, Vlado said: Bit not understand why new 5.44 for nanoPC T3 plus not run. Are you holding a boot key? Images should work. I'll check them again when I am back to the office.
Igor Posted May 14, 2018 Posted May 14, 2018 On 5/12/2018 at 2:51 PM, Vlado said: To Igor Bit not understand why new 5.44 for nanoPC T3 plus not run. I see only first boot screen and then black always ??? I upload new images, tested today. Except for those few noted issues, board performs nice.
Vlado Posted May 19, 2018 Author Posted May 19, 2018 On 5/15/2018 at 2:22 AM, Igor said: I upload new images, tested today. Except for those few noted issues, board performs nice. I tried run 39 ver. for M3 and it works. But all versions for T3plus wont work. ??? After u-boot screen always black screen with blinking cursor.
Igor Posted May 19, 2018 Posted May 19, 2018 29 minutes ago, Vlado said: But all versions for T3plus wont work. ??? With the image for M3? Yes, that is normal. it does not work. Image for T3+ works only on T3+ Please drop URL to the image which you tried?
Vlado Posted May 19, 2018 Author Posted May 19, 2018 1 minute ago, Igor said: With the image for M3? Yes, that is normal. it does not work. Image for T3+ works only on T3+ Please drop URL to the image which you tried? I work with T3+ board. So, on T3plus board image for M3 ver 39 run. on T3plus board image for T3+ not run.
Igor Posted May 19, 2018 Posted May 19, 2018 11 minutes ago, Vlado said: I tried all img. for T3+ That is strange. I am highly confident that both found here: https://www.armbian.com/nanopc-t3-plus/ has been tested. I can test them again later in the evening. Currently out of office. Can you make a PCB photo and/or get revision number.
Igor Posted May 19, 2018 Posted May 19, 2018 2 hours ago, Vlado said: After u-boot screen always black screen with blinking cursor. That is normal. How long did you wait until declare it doesn't work. It takes 17s from power on until I get a login prompt (Sandisk Ultra Class 10/average SD card). I agree that we should set some verbose output by default but hey, Rome was not built in a day. Bootlog:http://ix.io/1aP5 This image: https://dl.armbian.com/nanopct3plus/Ubuntu_bionic_next.7z
Vlado Posted May 19, 2018 Author Posted May 19, 2018 Just not understood why img. for M3 work and for T3+ not ??? I used same SD card. For T3+ resizing partition not happened.
Igor Posted May 19, 2018 Posted May 19, 2018 21 minutes ago, Vlado said: Just not understood why img. for M3 work and for T3+ not ??? They have different bootloader bl1 and adjusted u-boot to support 2G memory. If you don't have 2G of memory or memory has some different configuration, which is extremely unlikely, than this can make troubles. The rest is the same. I know that T3+ image doesn't boot on 1G boards (M3 for example). Your board looks the same, but I did a picture to double check. How do you power the board? I use lab PSU 5V / 5A Running low on ideas. This is serial console log - try to catch something on yours: Spoiler [ I2C_WriteByte nack returned I2C Device Address Write Abitration Error I2C_WriteByte nack returned I2C Device Address Write Abitration Error I2C_WriteByte nack returned I2C Device Address Write Abitration Error I2C_WriteByte nack returned I2C Device Address Write Abitration Error Wakeup Sub CPU 1234567 CPU Wakeup done! WFI is expected. CPU0 is Master! U-Boot 2016.01-armbian (May 14 2018 - 13:21:42 +0200) DRAM: 2 GiB MMC: NEXELL DWMMC: 0, NEXELL DWMMC: 1 loaded from SD, getting env from MMC 1 *** Warning - bad CRC, using default environment MIPI: display.0 HDMI: display.0, preset 0 (1280 * 720) HDMI: phy ready... LCD: [HDMI] dp.0.1 1220x680 16bpp FB:0x46000000 In: serial Out: vga Err: vga Hit any key to stop autoboot: 0 1202 bytes read in 20 ms (58.6 KiB/s) ## Executing script at 49000000 Boot script loaded from SD card 140 bytes read in 16 ms (7.8 KiB/s) 47325 bytes read in 28 ms (1.6 MiB/s) Loading DTB 7901313 bytes read in 363 ms (20.8 MiB/s) 15140872 bytes read in 669 ms (21.6 MiB/s) ## Loading init Ramdisk from Legacy Image at 49000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 7901249 Bytes = 7.5 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 48000000 Booting using the fdt blob at 0x48000000 Loading Ramdisk to bd7dc000, end bdf65041 ... OK Using Device Tree in place at 0000000048000000, end 000000004800e8dc Starting kernel ... Loading, please wait... starting version 237 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Will now check root file system ... fsck from util-linux 2.31.1 [/sbin/fsck.ext4 (1) -- /dev/mmcblk2p1] fsck.ext4 -a -C0 /dev/mmcblk2p1 /dev/mmcblk2p1: clean, 34335/438016 files, 257050/1900644 blocks done. done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... done. Welcome to Ubuntu 18.04 LTS! [ OK ] Reached target Swap. [ OK ] Reached target System Time Synchronized. [ OK ] Started Forward Password Requests to Wall Directory Watch. [ OK ] Created slice System Slice. [ OK ] Listening on udev Kernel Socket. [ OK ] Listening on udev Control Socket. [ OK ] Listening on Journal Audit Socket. [ OK ] Listening on Syslog Socket. [ OK ] Listening on Journal Socket. Starting Nameserver information manager... Mounting POSIX Message Queue File System... Starting Restore / save the current clock... Mounting Huge Pages File System... Starting Set the console keyboard layout... Mounting Kernel Debug File System... [ OK ] Listening on /dev/initctl Compatibility Named Pipe. [ OK ] Started Dispatch Password Requests to Console Directory Watch. [ OK ] Started ntp-systemd-netif.path. [ OK ] Created slice system-serial\x2dgetty.slice. [ OK ] Set up automount Arbitrary Executab…rmats File System Automount Point. [ OK ] Reached target Local Encrypted Volumes. [ OK ] Created slice User and Session Slice. [ OK ] Reached target Slices. [ OK ] Reached target Remote File Systems. [ OK ] Listening on fsck to fsckd communication Socket. Starting Remount Root and Kernel File Systems... [ OK ] Listening on Journal Socket (/dev/log). Starting udev Coldplug all Devices... Starting Create list of required st…ce nodes for the current kernel... Starting Load Kernel Modules... [ OK ] Mounted POSIX Message Queue File System. [ OK ] Started Restore / save the current clock. [ OK ] Mounted Huge Pages File System. [ OK ] Started Set the console keyboard layout. [ OK ] Mounted Kernel Debug File System. [ OK ] Started Remount Root and Kernel File Systems. [ OK ] Started Create list of required sta…vice nodes for the current kernel. [ OK ] Started Load Kernel Modules. [ OK ] Started Nameserver information manager. [ OK ] Reached target Network (Pre). Starting Apply Kernel Variables... Mounting Kernel Configuration File System... Starting Create Static Device Nodes in /dev... Starting Load/Save Random Seed... [ OK ] Mounted Kernel Configuration File System. [ OK ] Started Apply Kernel Variables. [ OK ] Started udev Coldplug all Devices. [ OK ] Started Load/Save Random Seed. [ OK ] Started Create Static Device Nodes in /dev. Starting udev Kernel Device Manager... [ OK ] Reached target Local File Systems (Pre). Mounting /tmp... [ OK ] Mounted /tmp. [ OK ] Reached target Local File Systems. Starting Raise network interfaces... Starting Set console font and keymap... Starting Armbian enhanced Log2Ram... [ OK ] Started udev Kernel Device Manager. [ OK ] Started Set console font and keymap. [ OK ] Found device /dev/ttySAC0. [ OK ] Reached target Sound Card. [ OK ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch. [ OK ] Started Armbian enhanced Log2Ram. Starting Journal Service... [ OK ] Started Raise network interfaces. Starting Load/Save RF Kill Switch Status... [ OK ] Started Load/Save RF Kill Switch Status. [ OK ] Started Journal Service. Starting Flush Journal to Persistent Storage... [ OK ] Started Flush Journal to Persistent Storage. Starting Create Volatile Files and Directories... [ OK ] Started Create Volatile Files and Directories. [ OK ] Started Entropy daemon using the HAVEGE algorithm. Starting Network Name Resolution... Starting Update UTMP about System Boot/Shutdown... Starting Network Time Synchronization... [ OK ] Started Update UTMP about System Boot/Shutdown. [ OK ] Started Network Name Resolution. [ OK ] Reached target Host and Network Name Lookups. [ OK ] Started Network Time Synchronization. [ OK ] Reached target System Initialization. [ OK ] Started Daily Cleanup of Temporary Directories. [ OK ] Started Daily apt download activities. [ OK ] Started Daily apt upgrade and clean activities. [ OK ] Started resolvconf-pull-resolved.path. [ OK ] Reached target Paths. [ OK ] Started Discard unused blocks once a week. [ OK ] Started Message of the Day. [ OK ] Reached target Timers. [ OK ] Listening on D-Bus System Message Bus Socket. [ OK ] Reached target Sockets. [ OK ] Reached target Basic System. Starting resolvconf-pull-resolved.service... Starting LSB: Armbian gathering hardware information... Starting Initializes zram swaping... Starting System Logging Service... Starting Dispatcher daemon for systemd-networkd... Starting LSB: Load kernel modules needed to enable cpufreq scaling... [ OK ] Started Set the CPU Frequency Scaling governor. [ OK ] Started ntp-systemd-netif.service. Starting Save/Restore Sound Card State... Starting Login Service... [ OK ] Started D-Bus System Message Bus. Starting Network Manager... Starting WPA supplicant... Starting Resets System Activity Data Collector... [ OK ] Started Regular background program processing daemon. [ OK ] Started System Logging Service. [ OK ] Started resolvconf-pull-resolved.service. [ OK ] Started Initializes zram swaping. [ OK ] Started Resets System Activity Data Collector. [ OK ] Started Save/Restore Sound Card State. [ OK ] Started Login Service. [ OK ] Started WPA supplicant. [ OK ] Started LSB: Load kernel modules needed to enable cpufreq scaling. Starting LSB: set CPUFreq kernel parameters... [ OK ] Started LSB: set CPUFreq kernel parameters. Starting LSB: Set sysfs variables from /etc/sysfs.conf... [ OK ] Started LSB: Set sysfs variables from /etc/sysfs.conf. Starting Hostname Service... [ OK ] Started Dispatcher daemon for systemd-networkd. [ OK ] Started Hostname Service. [ OK ] Started Network Manager. Starting Network Manager Script Dispatcher Service... Starting Network Manager Wait Online... [ OK ] Reached target Network. Starting Permit User Sessions... [ OK ] Started Unattended Upgrades Shutdown. Starting OpenBSD Secure Shell server... [ OK ] Started Permit User Sessions. [ OK ] Started Network Manager Script Dispatcher Service. Starting Set console scheme... [ OK ] Started Set console scheme. [ OK ] Created slice system-getty.slice. [ OK ] Started OpenBSD Secure Shell server. Starting Authorization Manager... [ OK ] Started Authorization Manager. [ OK ] Started LSB: Armbian gathering hardware information. [ OK ] Started Network Manager Wait Online. [ OK ] Reached target Network is Online. Starting /etc/rc.local Compatibility... [ OK ] Started /etc/rc.local Compatibility. [ OK ] Started Getty on tty1. [ OK ] Started Serial Getty on ttySAC0. Ubuntu 18.04 LTS nanopct3plus ttySAC0
Vlado Posted May 19, 2018 Author Posted May 19, 2018 ok, I will try to catch something on serial at Monday.
Igor Posted May 19, 2018 Posted May 19, 2018 3 minutes ago, Vlado said: ok, I will try to catch something on serial at Monday. OK and check PCB. I've moved related posts to a separate thread.
Vlado Posted May 19, 2018 Author Posted May 19, 2018 PCB is same. FriendlyArm img. 2GB RAM 32bit work OK. So 2GB !!! PSU 2.4A 1
Vlado Posted May 20, 2018 Author Posted May 20, 2018 It is log from UART for different img. I think problems in new bootloader, because all other imgs. work OK. Or maybe I have trouble with MPU? In this case, why do all the other images work? Armbian_5.44.180509_Nanopim3_Debian_stretch_next_4.14.39.txt Armbian_5.44.180510_Nanopct3plus_Ubuntu_xenial_next_4.14.40_desktop.txt Debian_stretch_next_4.14.40.txt
Vlado Posted June 11, 2018 Author Posted June 11, 2018 Hi Igor, can you give me answer about my case? If you need more info I am ready give to you. Last time I tried run with 3A PSU. Situation not change.
Vlado Posted June 11, 2018 Author Posted June 11, 2018 maybe it can help? https://patchwork.kernel.org/patch/9698397/https://archlinuxarm.org/forum/viewtopic.php?f=23&t=7161http://lkml.iu.edu/hypermail/linux/kernel/1805.3/04456.htmlhttps://patches.linaro.org/patch/36259/
Igor Posted June 12, 2018 Posted June 12, 2018 8 hours ago, Vlado said: maybe it can help? I have no interest nor resources to deal more with this board. https://docs.armbian.com/Process_Contribute/
constantius Posted September 10, 2018 Posted September 10, 2018 I have downloaded 5.59 Nanopi T3 plus Ubuntu bionic, kernel 4.14.69. When i press boot button on my Nanopi T3 ( without plus ) nothing is happens.
Igor Posted September 10, 2018 Posted September 10, 2018 14 minutes ago, constantius said: I have downloaded 5.59 Nanopi T3 plus Ubuntu bionic, kernel 4.14.69. When i press boot button on my Nanopi T3 ( without plus ) nothing is happens. You need to hold the button and power on. You should see bootloader welcome but then it takes some time to see something(login prompt) on the screen ... T3 without plus was confirmed working a few days ago. Also, install to eMMC.
constantius Posted September 10, 2018 Posted September 10, 2018 I hold boot button 3-4 minutes. No bootloader welcome screen. Only black monitor.
Igor Posted September 10, 2018 Posted September 10, 2018 6 minutes ago, constantius said: I hold boot button 3-4 minutes. No bootloader welcome screen. Only black monitor. 1. You need to hold boot button, power the board and then you can immediately release the button. Bootloader show logo for about 1 second. If your monitor is not fast enough you can easily miss it. 2. Then you need to wait a few minutes that SD card is resized. I can't tell exactly how long ... my 32GB Samsung EVO needs almost 3minutes to resize. There is nothing on the screen in that time ... yes, this we need to change. 3. Images are tested and they 100% work.
aitek Posted October 24, 2018 Posted October 24, 2018 Armbian_5.59_Nanopct3plus_Ubuntu_bionic_next_4.14.69_desktop cannot work ! and the log this: U-Boot 2016.01-armbian (Sep 10 2018 - 09:37:35 +0200) DRAM: 2 GiB MMC: NEXELL DWMMC: 0, NEXELL DWMMC: 1 loaded from SD, getting env from MMC 1 *** Warning - bad CRC, using default environment MIPI: display.0 HDMI: display.0, preset 0 (1280 * 720) HDMI: phy ready... LCD: [HDMI] dp.0.1 1220x680 16bpp FB:0x46000000 In: serial Out: serial Err: serial Hit any key to stop autoboot: 0 ** File not found /boot.scr ** ## Executing script at 40000000 Wrong image format for "source" command 1264 bytes read in 20 ms (61.5 KiB/s) ## Executing script at 40000000 Boot script loaded from SD card 1 75 bytes read in 16 ms (3.9 KiB/s) 47325 bytes read in 28 ms (1.6 MiB/s) Loading DTB 8152304 bytes read in 376 ms (20.7 MiB/s) 15845384 bytes read in 701 ms (21.6 MiB/s) ## Loading init Ramdisk from Legacy Image at 49000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 8152240 Bytes = 7.8 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 48000000 Booting using the fdt blob at 0x48000000 Loading Ramdisk to bd79e000, end bdf644b0 ... OK Loading Device Tree to 00000000bd78f000, end 00000000bd79d8dc ... OK Starting kernel ... Loading, please wait... starting version 237 [ 1.793000] Internal error: Oops: 96000005 [#1] SMP [ 1.793000] Modules linked in: [ 1.795000] CPU: 4 PID: 227 Comm: udevadm Not tainted 4.14.69-s5p6818 #194 [ 1.802000] Hardware name: nexell soc (DT) [ 1.806000] task: ffffffc07d90cf80 task.stack: ffffff8009b10000 [ 1.812000] PC is at kernfs_fop_open+0x1f8/0x39c [ 1.817000] LR is at kernfs_fop_open+0x1ec/0x39c [ 1.821000] pc : [<ffffff80082cfae4>] lr : [<ffffff80082cfad8>] pstate: a00001c5 [ 1.829000] sp : ffffff8009b13b60 [ 1.832000] x29: ffffff8009b13b60 x28: 0000000000000000 [ 1.837000] x27: ffffff8008ebd660 x26: ffffff8008ebd608 [ 1.843000] x25: ffffffc071c30b80 x24: ffffff8008ebd648 [ 1.848000] x23: ffffffc072036900 x22: ffffff8008ebd000 [ 1.853000] x21: ffffff8008a8a190 x20: ffffffc07244d500 [ 1.859000] x19: ffffffc07d96af00 x18: 0000007fb24d7a70 [ 1.864000] x17: 0000007fb24465e8 x16: ffffff8008245328 [ 1.869000] x15: 0000000000000000 x14: 0000000000000021 [ 1.874000] x13: 6b6c632d6f697067 x12: 2f73726576697264 [ 1.875000] usb 1-1: New USB device found, idVendor=05e3, idProduct=0610 [ 1.875000] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 1.875000] usb 1-1: Product: USB2.0 Hub [ 1.877000] hub 1-1:1.0: USB hub found [ 1.877000] hub 1-1:1.0: 4 ports detected [ 1.905000] x11: 0000000000000030 x10: 0101010101010101 [ 1.910000] x9 : 0000000000000000 x8 : ffffffc07244d500 [ 1.916000] x7 : 0000000000000000 x6 : 000000000000003f [ 1.921000] x5 : 0000000000000040 x4 : 0000000000000000 [ 1.926000] x3 : 0000000000000000 x2 : 0000000000000000 [ 1.932000] x1 : 0000000000000004 x0 : 0000000000002000 [ 1.937000] Process udevadm (pid: 227, stack limit = 0xffffff8009b10000) [ 1.944000] Call trace: [ 1.946000] Exception stack(0xffffff8009b13a20 to 0xffffff8009b13b60) [ 1.952000] 3a20: 0000000000002000 0000000000000004 0000000000000000 0000000000000000 [ 1.960000] 3a40: 0000000000000000 0000000000000040 000000000000003f 0000000000000000 [ 1.968000] 3a60: ffffffc07244d500 0000000000000000 0101010101010101 0000000000000030 [ 1.976000] 3a80: 2f73726576697264 6b6c632d6f697067 0000000000000021 0000000000000000 [ 1.984000] 3aa0: ffffff8008245328 0000007fb24465e8 0000007fb24d7a70 ffffffc07d96af00 [ 1.992000] 3ac0: ffffffc07244d500 ffffff8008a8a190 ffffff8008ebd000 ffffffc072036900 [ 1.999000] 3ae0: ffffff8008ebd648 ffffffc071c30b80 ffffff8008ebd608 ffffff8008ebd660 [ 2.007000] 3b00: 0000000000000000 ffffff8009b13b60 ffffff80082cfad8 ffffff8009b13b60 [ 2.015000] 3b20: ffffff80082cfae4 00000000a00001c5 ffffff8009b13b50 ffffff8008a52024 [ 2.023000] 3b40: 0000007fffffffff ffffffc07244d500 ffffff8009b13b60 ffffff80082cfae4 [ 2.031000] [<ffffff80082cfae4>] kernfs_fop_open+0x1f8/0x39c [ 2.036000] [<ffffff8008243fc4>] do_dentry_open+0x224/0x328 [ 2.042000] [<ffffff8008244e20>] vfs_open+0x54/0x84 [ 2.047000] [<ffffff8008256f34>] path_openat+0x520/0xfd4 [ 2.052000] [<ffffff8008258a1c>] do_filp_open+0x5c/0xd8 [ 2.057000] [<ffffff800824523c>] do_sys_open+0x140/0x208 [ 2.062000] [<ffffff8008245338>] SyS_openat+0x10/0x18 [ 2.067000] Exception stack(0xffffff8009b13ec0 to 0xffffff8009b14000) [ 2.074000] 3ec0: ffffffffffffff9c 0000007fe4e91d38 0000000000080001 0000000000000000 [ 2.082000] 3ee0: 000000556685f637 0000007fe4e91d61 000000007665752f 00000000746e6576 [ 2.090000] 3f00: 0000000000000038 632d6f6970672f73 702f7375622f7379 2f6d726f6674616c [ 2.097000] 3f20: 2f73726576697264 6b6c632d6f697067 0000000000000021 0000000000000000 [ 2.105000] 3f40: 00000055668a0dc0 0000007fb24465e8 0000007fb24d7a70 0000007fb24d6000 [ 2.113000] 3f60: 0000007fe4e91d38 0000000000000003 0000007fe4e91d38 00000055668a0000 [ 2.121000] 3f80: 0000007fe4e92e71 000000556685e128 0000007fe4e92e71 000000557cd04cd0 [ 2.129000] 3fa0: 0000000000000001 0000007fe4e91c70 00000055668201b8 0000007fe4e91c70 [ 2.136000] 3fc0: 0000007fb244664c 0000000080000000 ffffffffffffff9c 0000000000000038 [ 2.144000] 3fe0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 [ 2.152000] [<ffffff80080832c0>] el0_svc_naked+0x34/0x38 [ 2.153000] usb 1-1.1: new low-speed USB device number 3 using exynos-ehci [ 2.164000] Code: 941e094c f9402660 b40004c0 f9800011 (885f7c01) [ 2.170000] ---[ end trace fda0636dece83245 ]--- [ 2.175000] note: udevadm[227] exited with preempt_count 1 Segmentation fault Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems [ 2.238000] usb 1-1.1: New USB device found, idVendor=04f3, idProduct=0103 [ 2.239000] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 2.253000] input: HID 04f3:0103 as /devices/platform/c0000000.soc/c0030000.ehci/usb1/1-1/1-1.1/1-1.1:1.0/0003:04F3:0103.0001/input/input0 [ 2.261000] hid-generic 0003:04F3:0103.0001: input,hidraw0: USB HID v1.10 Keyboard [HID 04f3:0103] on usb-c0030000.ehci-1.1/input0 [ 2.277000] input: HID 04f3:0103 as /devices/platform/c0000000.soc/c0030000.ehci/usb1/1-1/1-1.1/1-1.1:1.1/0003:04F3:0103.0002/input/input1 [ 2.285000] hid-generic 0003:04F3:0103.0002: input,hidraw1: USB HID v1.10 Device [HID 04f3:0103] on usb-c0030000.ehci-1.1/input1 [ 2.361000] usb 1-1.3: new low-speed USB device number 4 using exynos-ehci [ 2.445000] usb 1-1.3: New USB device found, idVendor=093a, idProduct=2510 [ 2.446000] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 2.453000] usb 1-1.3: Product: USB OPTICAL MOUSE [ 2.458000] usb 1-1.3: Manufacturer: PIXART [ 2.468000] input: PIXART USB OPTICAL MOUSE as /devices/platform/c0000000.soc/c0030000.ehci/usb1/1-1/1-1.3/1-1.3:1.0/0003:093A:2510.0003/input/input2 [ 2.476000] hid-generic 0003:093A:2510.0003: input,hidraw2: USB HID v1.11 Mouse [PIXART USB OPTICAL MOUSE] on usb-c0030000.ehci-1.3/input0 [ 11.395000] random: crng init done so sad...
Igor Posted October 24, 2018 Posted October 24, 2018 5 minutes ago, aitek said: Armbian_5.59_Nanopct3plus_Ubuntu_bionic_next_4.14.69_desktop cannot work ! Have you try to boot more than once & from different SD cards?
aitek Posted October 24, 2018 Posted October 24, 2018 yes, i have try to boot many times. and try Stretch and Bionic, but can't boot
Recommended Posts