hipboi_ has quit [Read error: Connection reset by peer]
hipboi_ has joined #cubieboard
jelly has quit [Ping timeout: 245 seconds]
ganbold_ has quit [Ping timeout: 276 seconds]
TheSeven has quit [Ping timeout: 276 seconds]
TheSeven has joined #cubieboard
Gumboot has joined #cubieboard
Gumboot has quit [Read error: Connection reset by peer]
Gumboot has joined #cubieboard
<discopig>
yeah no SATA is a dealbreaker
Gumboot has quit [Read error: Connection reset by peer]
Gumboot has joined #cubieboard
bizarro_1 has quit [Quit: Leaving]
OutOfLine has joined #cubieboard
asie has joined #cubieboard
ganbold_ has joined #cubieboard
ganbold_ has quit [Ping timeout: 276 seconds]
deffrag has joined #cubieboard
Ti_W_B has joined #cubieboard
discopig has quit [Quit: Bye]
discopig has joined #cubieboard
Ti_W_B_ has joined #cubieboard
asie has quit [Remote host closed the connection]
asie has joined #cubieboard
deffrag_ has joined #cubieboard
deffrag has quit [Ping timeout: 245 seconds]
sarwarc has joined #cubieboard
esters has joined #cubieboard
<esters>
Hi, running 1st gen cubieboard with a 2.5" Western Digital 1Tb Red drive with Cubian. So far I am struggling to get hdd working properly, upon writing the disk shuts off and I get error messages in dmesg. Could this be a power issue ? I am using a original samsung 5V 2A power supply. the drive by specification consumes 0.55A. I do not have any other devices connected to the cubieboard. Would it be possible that the barrel plug cord
asie has quit [Quit: I'll probably come back in either 20 minutes or 8 hours.]
numbie has quit [Quit: Leaving]
asie has joined #cubieboard
<iggy>
esters: I don't know about your specific problem, but your question got cut off (fwiw)
<esters>
iggy: the probke
<esters>
problem*
<esters>
is that the connected hdd
<iggy>
I got the gist of it, just the tail end of whatever you were saying was cutoff
<esters>
upon writing either powers off (not visible by fdisk -l) and dmesg spits out multitude I/O error messages
<buZz>
my hdmi on cubie2 switches off on idle, but when i type a key it pops back up
<tat>
it is a cubietruck,
<buZz>
nearly same hardware
<tat>
there is a short comment on igor pecovnik's blog where someone ask's for that, but he just points out that he knows that problem but hasn't got to use the desktop so far
<tat>
that's it
<buZz>
i just run normal native debian btw
<buZz>
no weird custom builds
ohama has quit [Ping timeout: 250 seconds]
<tat>
do you run cubian ?
<buZz>
14:33:30 < buZz> i just run normal native debian btw
<buZz>
14:33:35 < buZz> no weird custom builds
<buZz>
so, no
ohama has joined #cubieboard
<tat>
buZz: where do you get your kernel from ?
<tat>
as i understood, A20 isn't supported by the mainline kernel