freak
-
Posts
110 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by freak
-
-
By update I meant and update to the thread not to the system. That was using a fresh install of bionic from the download page.
-
Another update... Fresh install of Bionic... Won't boot with monitor plugged in.
Remove power, Unplug hdmi, replace power, allow time to boot, plug hdmi, system is up and running.
(yes I'm still working on getting you logs Igor but I'll be out of town for the next few days)
-
PM me a shipping address.
-
7 hours ago, Igor said:
There are many kernel hackers out there who are fixing problems for money. You can also just switch faulty hardware. It's your call.
I'll ship you a brand new http://a.co/d/2YbJdo1 and if it turns out to not be a software problem you can keep it. Deal?
-
29 minutes ago, Igor said:
I was waiting for this. A prove that there is nothing wrong with our work. Thank you!
Armbian does not provide support for 3rd party hardware, which are the root of this problem -> a few people can't provide FREE support for all kind of electronic junk on this planet in their spare time. I hope you do understand this?
Without logs, problems are not even officially recognized. That's why I repeat myself like a parrot. Only logs might tell if we can solve the problem quickly or we will just file it.But to be fair... all 85 of my boards were working fine till I ran apt upgrade.
-
I was just giving you an update my friend. I will get your logs.
-
Update: This may have something to do with the resolution. These a mostly connected to 1920x1200 HP monitors often with hdmi to dvi cables (sometimes hdmi both ends) but quite often they only run at 1920x1080. But they work. This "bricked" unit boots fine when connected to a acer G215H 1920x1080 monitor via hdmi/dvi. Connected to an HP z27N via straight hdmi it will not boot.
-
Why "do-release-upgrade -d"? Isn't there a stable release?
-
...and I can re-image the affected boards to fix them. But for the working ones I'd like to upgrade to bionic if I can do that via the command line.
-
Is whatever what was wrong fixed so I can run apt upgrade with bricking the rest of the units?
-
I don't have the usb/ttl adapter but I'll order one. In the meantime I don't mind upgrading to bionic. Can I do it from the command line from the build that I'm at?
-
Power cycling isn't solving it.
-
Thanks I've tried power cycling several times but they still don't boot. I can try again.
-
TTL is ok on those pins?
-
Ok... Not familiar with how to get a serial console. Link to a doc perhaps?
-
I have 85 tinkers running with armbian 5.41 xenial next 4.14.23. Normally I run a script that apt upgrades them all but I run a small batch of them first as a test. Today I ran apt update/upgrade on three of them and they are all bricked. No output to the screen. Can't ping them. Any ideas?
-
Ok I'll see what I can do. Also would like to test on raspberry pi.
-
Works on KDE Neon, Ubuntu Gnome, Win10... I'll test more. I know what the Chromium devs are going to say when I tell them it works everywhere except armbian.
-
...and I should also point out that if you turn on automount in the system settings and let the os mount the stick automatically (wait till the autmount is finished before hitting ctrl+o) Chromium will not crash. So this is something to do with mounting within the "file open" dialog.
-
Actually you don't even need to use my codepen example. Just open Chromium and hit CTRL+O (oh not zero). Browse the usb stick in the dialog. Close the dialog. Crashed.
-
Here's how to duplicate...
Look here... http://ix.io/1lwN
to see what version of armbian I am running and install that version.
Run apt update/upgrade.
Insert a usb drive that has a file system on it (not sure the type of the file system matters) into a usb slot. (do not mount it or have automount turned on)
Open Chromium.
With Chromium go to...
https://codepen.io/anon/pen/EeNLNX
Click the "Browse" button the in preview window on codepen.
When armbian's file dialog comes up click the icon for your usb drive to browse files on that drive.
The usb stick will now automount.
Close the armbian file dialog ( it doesn't matter if you select a file or not)
Chromium is crashed.
-
Uh no... Point it to a camera or usb stick and try to upload a jpg from it. Nothing to do with streaming.
-
Hopefully this helps... http://ix.io/1lwN
-
Using 5.41 with Chromium 68.0... Using <input type="file"> on a web page... If you click a usb camera (probably usb stick as well) and the system mounts the usb (assuming it wasn't mounted already by other means)... after you close the dialog (whether you selected a file or clicked cancel)... chromium is frozen.
HDMI-Monitor bricked tinkers today (next 5.60)
in Tinkerboard
Posted
update again... I connected two tinkers... Installed picocom. Using fresh install of armbian 5.59 4.14.67 I can watch the tinker in question boot just fine over the tty... IF the hdmi cable is not plugged in. With HDMI plugged in it will not boot at all. The boot is not visible through the tty because it's not booting so I cannot get logs.
Next...
Using fresh install of armbian 5.41 4.14.23 on exact same tinker and monitor and cable and power supply, the system boots fine. HOWEVER, if I take this fresh install of 5.41 4.14.23 and run apt update/upgrade the system no longer boots unless you remove the HDMI cable (just like above using 5.59 4.14.67). And as it doesn't even attempt to boot there are no logs to be had. Not sure what to try next.