<sr105>
In linux is there any way to guarantee that all data has been written to the microSD card?
<sr105>
will a simple "sync" do it?
<jduck>
it should, but safely dismounting is a good idea too
<buZz>
'safe dismount' does sync, then umount
<sr105>
Well, I want to make sure my data is written in case of a power failure
<sr105>
but I want to keep the device mounted in case I want to use it further
asterick has quit [Quit: Leaving...]
emilepetrone has joined #cubieboard
emilepetrone has quit [Remote host closed the connection]
chihchun_afk is now known as chihchun
KiSM has joined #cubieboard
sr105 is now known as sr105|away
bitxiao has joined #cubieboard
<bitxiao>
ls
<bitxiao>
hi
<bitxiao>
大家好
[7] has quit [Disconnected by services]
TheSeven has joined #cubieboard
verysoftoiletppr has joined #cubieboard
KiSM has quit [Read error: Connection reset by peer]
<shogunx>
hello all. trying to config a sata disk on a cubie
KiSM has joined #cubieboard
KiSM has quit [Max SendQ exceeded]
<shogunx>
modprobe sw_ahci_platform produces some info in dmesg, but the last statement is ata1: SATA link down (SStatus 0 SControl 300)
<shogunx>
not sure what entry in /dev to access or create as necessary to partition, format, and mount this device.
<shogunx>
any ideas?
<shogunx>
running debian sid, btw. upgraded from testing.
<shogunx>
thanx in advance. will check scrollback occasionally.
\\Mr_C\\ has quit []
lawrence88 has joined #cubieboard
kaspter has joined #cubieboard
verysoftoiletppr has quit []
bitxiao has quit [Quit: Page closed]
<user_2>
shogunx, be sure to have at least 2A powersupply. second, do 'dmesg | grep sd' to verify the sistem correctly recognize the disk. (let say it is 'sda' then do the usual 'fsck sda' to do partition and mkfs to format it
Cy-Gor has quit [Quit: Leaving]
shineworld has joined #cubieboard
Yaku321 has joined #cubieboard
ellab has joined #cubieboard
arod has joined #cubieboard
n01|away is now known as n01
<suhanc>
bye
suhanc has quit [Quit: Ex-Chat]
user_2 has quit [Ping timeout: 256 seconds]
Martix has joined #cubieboard
shineworld has quit [Quit: Leaving]
eebrah|away is now known as eebrah
<rymate1234>
I can't wait to buy my cubie
<Yaku321>
and then you can´t wait to recieve it :P
<BigWhoop[DE]>
and then you break it and weep bitterly
<lawrence88>
mine all still work
<lawrence88>
one has been on for months now
<lawrence88>
since feb
<lawrence88>
still ok
bigx has quit [Ping timeout: 264 seconds]
user_2 has joined #cubieboard
<BigWhoop[DE]>
mine too
Martix has quit [Ping timeout: 252 seconds]
bigx has joined #cubieboard
uizex1 has joined #cubieboard
err404 has joined #cubieboard
kludge` has quit [Ping timeout: 256 seconds]
<wooy>
shogunx: had similar problem with my custom debian image. Then I found out I didnt have auto loading of kernel modules enabled.
kludge` has joined #cubieboard
Swat- has quit [Ping timeout: 248 seconds]
Martix has joined #cubieboard
Martix_ has joined #cubieboard
Martix has quit [Ping timeout: 260 seconds]
chihchun is now known as chihchun_afk
user_2 has quit [Ping timeout: 264 seconds]
chihchun_afk is now known as chihchun
niftylettuce has quit [Ping timeout: 260 seconds]
prassel has joined #cubieboard
corvusNBT has joined #cubieboard
KiSM has joined #cubieboard
ricardocrudo has joined #cubieboard
chihchun is now known as chihchun_afk
tinti has joined #cubieboard
emilepetrone has joined #cubieboard
backb0ne has joined #cubieboard
Undertasker has joined #cubieboard
<shogunx>
user_2 no sda in dmesg. that was the first thing I looked at. the modules loads, but the disk is not recognized, nor is there a /dev/sda in /dev and I can't get /dev/MAKEDEV to make one
<shogunx>
wooy I should put the kernel module in /etc/modules then, and reboot?
<shogunx>
or do I need to pass something else to the kernel?
Cy-Gor has joined #cubieboard
uizex1 has quit [Quit: REALITY.SYS Corrupted: Re-boot universe? (Y/N/Q)]
h0cin has joined #cubieboard
RafaelK has joined #cubieboard
KiSM has quit [Quit: Leaving]
\\Mr_C\\ has joined #cubieboard
KiSM has joined #cubieboard
fuwei has joined #cubieboard
<shogunx>
yep... /etc/modules add of the appropriate kernel module = no good
<shogunx>
wooy what was your solution?
diegocarrera has joined #cubieboard
datagutt has joined #cubieboard
datagutt has quit [Remote host closed the connection]
A124 has quit [Read error: Operation timed out]
datagutt has joined #cubieboard
ganbold_ has joined #cubieboard
niftylettuce has joined #cubieboard
Undertasker has quit [Quit: Leaving.]
Undertasker1 has joined #cubieboard
Undertasker1 has quit [Read error: Connection reset by peer]
Undertasker has joined #cubieboard
Yaku321 has quit [Disconnected by services]
Yaku-noob has joined #cubieboard
bigx has quit [Remote host closed the connection]
Undertasker has quit [Read error: Connection reset by peer]
Undertasker has joined #cubieboard
A124 has joined #cubieboard
err404 has quit [Read error: Connection reset by peer]
eebrah is now known as eebrah|away
<bfree>
shogunx: sounds more likely you have power problems which are causing the drive to fall over. maybe a pastebin of all the messages when you load the sw_ahci_platform will make that clearer. what sort of drive are you using and how are you powering it?
<shogunx>
transcend ts32gssd360 32gb ssd 5V @ .4A
<shogunx>
powered via the pins provided, but i can put it across a larger 5v rail if necessary
<shogunx>
cubie is powered from a 2A usb charger that came with a nexus 7
nils_2_ has joined #cubieboard
nils_2 has quit [Ping timeout: 264 seconds]
RafaelK has quit [Quit: Leaving.]
<bfree>
shogunx: setup sounds reasonable (guessing the nexus 7 charger isn't a fake chinese special), but if you can externally power the ssd I'd try that to narrow it down a little
nils_2_ is now known as nils_2
<shogunx>
the lack of /dev/sda make sense to me as a problem.
<CubieFAQ>
serial-port: There is one USB-serial cable in the cubieboard package. The four color lines of the cable are: White, Black, Red, Green. The definition of the lines are: RED +5v, BLACK GND, GREEN RX, WHITE TX. Connect the black one to GND pin on the board, GREEN one to RX pin, WHITE one to TX pin. The rich package contains the serial cable.
<mnemoc>
in the case of mainline u-boot, the entry point is the sunxi-current branch of u-boot-sunxi
uizex1 has quit [Quit: On the other hand, you have different fingers.]
<`26>
by partial, do you mean that I can just grab mainline linux and uboot, configure them appropriately, put them on a SD card (along with userspace stuff) and get a working system?
<`26>
and by "working" I mean "serial debugging port works and ethernet works"
<mnemoc>
no mmc support on mainline linux yet
<mnemoc>
but you can boot an initramfs
`26 has quit [Remote host closed the connection]
<mnemoc>
you are welcomed to join the linux-sunxi community and colaborate
niftylettuce has quit [Ping timeout: 256 seconds]
<mnemoc>
meh
`26 has joined #cubieboard
<`26>
(sorry, connection died)
<`26>
mnemoc: thanks. (I read your reply off the irc logs)
<mnemoc>
`26: #linux-sunxi is just around the corner ;-)
<mnemoc>
but that wiki page summarizes the current status of linux's sunxi-next
niftylettuce has joined #cubieboard
Martix has quit [Ping timeout: 256 seconds]
<`26>
mnemoc: I'm asking because I'm really looking for it getting official debian support.