<buZz>
why doesnt dd work? it works on every other SD image?
<tkaiser>
buZz: And in case you're trying it with OPi Zero then there's also a great chance that powering is insufficient.
<buZz>
are you referring to > Raw images can be written with Etcher (all OS).
<buZz>
a) it mentions 'raw' which comes back in nothing else
<buZz>
b) it says 'can'
<tkaiser>
buZz: dd doesn't do a verify, I stopped to listen when people tell 'I burned image with WinDiskImager/dd'
<buZz>
heh, ok , so you assume i need verification?
<buZz>
its a nanopi m1 btw :)
<tkaiser>
buZz: I had many occassions where dd happily burned garbage while Etcher either reported errors while writing or later when doing the verify.
<tkaiser>
buZz: Did FriendlyELEC ship a Micro USB cable with the board?
<buZz>
cool, i had zero such experiences , but i'll play along and try this etcher thingy
<MoeIcenowy>
tkaiser: so do you still prefer to use 672MHz by default?
<buZz>
no, but i used a known 1A capable usb cable
<buZz>
what suprised me most was that the nanopim1 image provided only has a single partition
<tkaiser>
MoeIcenowy: Nope, I would prefer a sane value from the beginning. In case DRAM reliability testing will ever happen we can increase the value later (let's do it this time the other way around as usual: starting with stupid unreliable values for no reason)
<buZz>
whereas friendlyarm's have two partitions
<tkaiser>
buZz: We're dealing with ARM boards and not VideoCore IV boards. Only Rasperries need a FAT partition since their primitive main processor can't deal with anything else
<buZz>
hmhm k, it just came across as weird
<buZz>
so 'why etcher' is just because dd wasnt nice to you in history? :P
<buZz>
then i still dont see why dd wouldnt work
<MoeIcenowy>
oh the official NanoPi NEO2 case is so weird... it have even no reserved holes for UART...
<KotCzarny>
wtf, 'dd burned garbage' for fox sake, it's just using os to write blocks, not some eeprom flasher, *grmlbl*
<buZz>
yeah i dont get it either :P
<tkaiser>
buZz: The reason we 'recommend' Etcher is that no one wants to waste his time with stupid support calls that are all just caused by bad OS images. Burning tools that don't do a verify are crap. Period.
<buZz>
i use dd all the time for filesystem images, havent gotten bad bytes ever
<KotCzarny>
otoh if card needs more preparing it might worth mentioning
<buZz>
anyway i'll try installing that website-dd you recommend
<KotCzarny>
buzz, remember that on first boot armbian does some housekeeping and might be unresponsive
<buZz>
KotCzarny: it gave no output on HDMI at all
<KotCzarny>
got your uart cable ?
<buZz>
hmm somewhere, i could dig it up
<tkaiser>
Folks, just continue so but don't ask why stuff doesn't work. I really don't care when people write garbage to SD cards. But please don't complain later and blame the software.
<buZz>
i waited for ~10 minutes :P
<KotCzarny>
afair armbian doesnt have hdmi-dvi fix on most of the fex files (if you use legacy kernel)
<buZz>
> Legacy 3.4.113
<KotCzarny>
tkaiser, if one's card is SO bad that os level writes result in badblocks, then yeah, no app will help
<KotCzarny>
buzz: are you using hdmi-dvi adapter?
<vpeter>
Few days back I meet user who wrote image with dd. Program was successful but write speed were crazy high. It reported that everything has been written but system didn't boot. I always though that in such case dd would just fail but seems I was wrong :(
<buZz>
KotCzarny: no, a motorola lapdock with hdmi input
<KotCzarny>
vpeter: writing to the wrong device or cheap-ass usb-sd adapter might result in that
<KotCzarny>
buzz, hrm. got another allwinner board with uart? you can use it too as a serial console
<vpeter>
KotCzarny: Maybe. But in this case sd card was dead.
<tkaiser>
vpeter: dd is unreliable crap, you need a verify if you rely on this tool. But no one does it since all people are so smart that they blindly trust in unreliable tools. Same with WinDiskImager
<buZz>
KotCzarny: i'm just playing dumb and following tkaiser's hate ;)
<KotCzarny>
vpeter, yeah, no etcher would help in that case and similarly dd wasnt at fault
<KotCzarny>
buZz: oh, have fun then, not interrupting then ;)
<buZz>
^_^
<buZz>
i have some weird website app now flashing a sd card
<tkaiser>
25% of 'Armbian doesn't work' threads in Armbian's mist shitty suv forum (H2/H3) are related to this.
<buZz>
tkaiser: so most odds this isnt the problem then?
<KotCzarny>
tkaiser, bad/cheap hardware (power/sdcard) is the fault then, not dd
<tkaiser>
buZz: If you know how to deal with dd and are able to use sync/md5 later then dd is fine. But no one does this.
<KotCzarny>
tkaiser, that's because in normal use cases one could rely on hw to write without badblocks
<KotCzarny>
hehe
<buZz>
we'll see :P its done now
<tkaiser>
KotCzarny: What a waste of time as usual. Bye
Andy-D_ has quit [Remote host closed the connection]
libv_ has joined #linux-sunxi
Andy-D has joined #linux-sunxi
libv has quit [Ping timeout: 240 seconds]
cnxsoft has quit [Quit: cnxsoft]
libv_ is now known as libv
Putti has quit [Remote host closed the connection]
Putti has joined #linux-sunxi
ykchavan has joined #linux-sunxi
Gerwin_J has quit [Quit: Gerwin_J]
Gerwin_J has joined #linux-sunxi
dave0x6d has joined #linux-sunxi
quard has quit [Quit: Leaving]
scream has joined #linux-sunxi
kloczek has joined #linux-sunxi
kloczek has quit [Remote host closed the connection]
libv_ has joined #linux-sunxi
kloczek has joined #linux-sunxi
libv has quit [Ping timeout: 255 seconds]
lkcl has quit [Ping timeout: 260 seconds]
The_Loko has quit [Quit: Leaving]
Gerwin_J has quit [Quit: Gerwin_J]
kloczek has quit [Remote host closed the connection]
IgorPec has quit [Ping timeout: 258 seconds]
kloczek has joined #linux-sunxi
wzyy2 has quit [Read error: No route to host]
lkcl has joined #linux-sunxi
f0xx has quit [Ping timeout: 240 seconds]
netlynx has quit [Quit: Ex-Chat]
Ntemis has quit [Remote host closed the connection]
ykchavan_ has joined #linux-sunxi
ykchavan has quit [Ping timeout: 260 seconds]
arete74 has quit [Ping timeout: 255 seconds]
arete74 has joined #linux-sunxi
terra854 has quit [Quit: Connection closed for inactivity]
hazar has joined #linux-sunxi
Andy-D_ has joined #linux-sunxi
<hazar>
Hi, I'm trying to get I2S output on Allwinner R8 (actually an NTC GR8). I managed to get a signal but the MCLK (master clock) is needs to be inverted, others seems correct. Can anyone assist or redirect me to the right direction? Thanks.
Andy-D has quit [Ping timeout: 268 seconds]
IgorPec has joined #linux-sunxi
JohnDoe_71Rus has quit [Quit: KVIrc KVIrc Aria 4.9.2, revision: git-7099-gca80ee628, build type: debug, sources date: 20160102, built on: 2017-03-12 14:49:35 UTC git-7099-gca80ee628 http://www.kvirc.net/]
Andy-D__ has joined #linux-sunxi
IgorPec has quit [Ping timeout: 240 seconds]
mozzwald has quit [Ping timeout: 240 seconds]
Andy-D_ has quit [Ping timeout: 252 seconds]
lkcl has quit [Ping timeout: 258 seconds]
mozzwald has joined #linux-sunxi
scream has quit [Remote host closed the connection]