lampra
-
Posts
169 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by lampra
-
-
Here is the output
-
In my case, I have nothing connected to opi pc except of ethernet and power. I just run ssh daemon and nothing else.
I installed the latest kernel 3.4.111.
When logged in with ssh, reboot command does not work. Init 6 works some times but not always.
-
I have noticed that when using the Armbian_5.05_Orangepih3_Debian_jessie_3.4.110 on orangepi pc or after updating the kernel from this topic,
shutdown -r and reboot does not work, it shuts down the machine. Sometimes init 6 reboots the machine but not always.
PS: During the installation of the CMA enabled .deb it complained about not finding the led and after boot, green and red leds are off.
-
I connect the ssd to my cubietruck using:
root@cubietruck:~# dmesg | grep -i ASM [ 4.129952] usb 2-1: Product: ASMT1051 [ 4.129962] usb 2-1: Manufacturer: asmedia [ 7.187667] scsi 1:0:0:0: Direct-Access ASMT 2115 0 PQ: 0 ANSI: 6
The output of armbianmonitor is:
root@cubietruck:~# armbianmonitor -d + exec Examining /dev/sda with GUID 2A896D94-7E05-4651-9295-45619E10CAB9 (accessible through S.M.A.R.T.) Disk not configured for monitoring. We were able to extract the following information: GUID: 2A896D94-7E05-4651-9295-45619E10CAB9 hddtemp: will work CRC attribute: 199 LCC Attribute: If you want to monitor the disk please add to /etc/armbianmonitor/disks.conf: 2A896D94-7E05-4651-9295-45619E10CAB9:INTENSO SSD 128GB:::199: Debug output has been collected at the following URL: http://sprunge.us/ChRJ Please post the URL in the Armbian forum where you've been asked for.
Here is the link: http://sprunge.us/ChRJ
PS: Any tip on how to boot armbian on this ssd using mainline kernel would be welcomed. I have read tkaiser 's sunxi wiki page regarding ASMEDIA 1051 (here). I can boot with 3.4 kernel. How do I disabled ASM1051 blacklisting in armbian?
-
Regarding armbianmonitor, do you need results only for orange-pi or I can send for cubietruck also?
-
Update: It seems to me that it is a hardware/kernel issue.
I see that the chip of the StarTech.com USB 3.0 to 2.5†SATA is ASMedia ASM1051.
As described here http://linux-sunxi.org/USB/UAS, ASM1051 is blacklisted on the mainline kernel.
Booting legacy kernel works fine.
-
Hi, I tried UUID and PARTUUID but none of them works. Maybe this is a U-BOOT issue.
root@cubietruck:/home/lampra# grep -a --null-data U-Boot /dev/mmcblk0 U-Boot U-Boot SPL 2015.07-armbian-sun7i (Oct 11 2015 - 15:34:22)
I will post a question at the sunxi irc
-
Hi,
I used Armbian_4.5_Cubietruck_Ubuntu_trusty_4.2.3 as sd card image. Later I moved it to a sata connected ssd and upgraded to 4.2.6 kernel.
As I needed a second drive I bought a : StarTech.com USB 3.0 to 2.5†SATA III Hard Drive Adapter Cable w/ UASP – SATA to USB 3.0 Converter for SSD / HDD
This usb to sata works fine with the ssd. The second drive is a 5v 2.5†SATA and the usb current is not enough so it is connected to the sata on cubietruck. On the second usb i have connected a usb to ethernet adapter.
Trying to boot results to kernel panic (& something about no init) and cubietruck reboots.
I am wondering if I need to change anything eg boot.cmd arguments to get the system running at this setup.
Thank you
-
To my understanding, if needed ie if the date command produces errors, the hwclock could probably be set by a script asking the user to confirm or input the current date/time. Reboot the system and then start first run.
In my case the date command produced errors (which i do not remember exactly) and the hwclock was set at year 1949.
Alternatively set the root password to expire immediately at the end of first run (not at first login) in order for the user to be able to set the hwclock manually and reboot the system. Then start again firstrun.
-
Finally solved, my problem was also hwclock as described in post 31.
I was able to solve it using my image to set hwclock.
After that, 12.7.15, 4.1.2 Trusty image works like a charm.
Strangely, with other images using kernel 3.4 hwclock seemed correct.
Thank you
-
ok here are my findings from the latest build.
I used the 12.7.15, 4.1.2 Trusty image.
The image starts booting the kernel, after 3 messages (i.e. brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO 3166 code) hangs for some minutes (2-3), then continues with firstrun and then stops with the cursor blinking.
I tried ttys2 and i was able to login and change the root password. So far no network connection. Using top, i saw that fping consumes all the cpu. Killing fping causes reboot. After reboot, boot is fine (except of the delay probably caused by brcmfmac) but impossible to login as root as it does not accept the old or the new password. The same happens if at first boot a new user is added.
-
Hi sorry for the delay, I used u-boot provided with the kernel (from danand.de) which is 2015.07 rc3 dirty
-
It's doesn't work for me too.
Can you set wrong date to hwclock and try boot again?
I didn't try this approach. I started from the beginning to build one image with 4.1 precompiled kernel from http://danand.de and ubuntu core rootfs.
I successfully booted CT but it does not connect to the network.
So if Igor's image needs network at the first boot maybe this is one cause of the problem.
-
Hi,
doesn't work for me. My hwclock if fine and still i can't boot images with kernel 4.0.5 or 4.1.
Both stop at runlevel 2 after enabling ramlog. Sadly i do not have a serial cable to provide more info.
Debian-3.8-wheezy-3.4.107 boots fine
-
@cibomato: As I wrote earlier Ubuntu-3.9-4.0.5 and Debian-3.9-jessie-4.0.5 doesn't boot on my Cubietruck.
I also tested Debian-4.0-wheezy-4.1.0 which also does not boot. I tried also by cutting the power but no results.
-
Hi,
Same problem here on Cubietruck with Ubuntu-3.9-4.0.5. It doesn't boot.
Debian-3.9-jessie-4.0.5 also doesn't boot. Hangs after enabling ramlog. Before that i get a message that it failed to bring up eth0.
Reboot command
in Allwinner sunxi
Posted
I tried 3 different cards but no luck.
Then, I connected opi pc to hdmi tv and reboot started working.
Even if hdmi is detached from the tv and attached to opi pc, reboot works.
Detaching hdmi from opi pc again causes reboot to stop working.