deffrag__ has quit [Remote host closed the connection]
deffrag__ has joined #cubieboard
tat has joined #cubieboard
tat_ has joined #cubieboard
fossxplorer has quit [Ping timeout: 252 seconds]
tat__ has joined #cubieboard
tat has quit [Ping timeout: 252 seconds]
tat_ has quit [Ping timeout: 252 seconds]
popolon has quit [Quit: Quitte]
imRance has joined #cubieboard
deffrag__ has quit [Remote host closed the connection]
deffrag__ has joined #cubieboard
deffrag has joined #cubieboard
deasy has quit [Quit: Nom d'un quark, c'est Edmonton !]
deffrag__ has quit [Ping timeout: 255 seconds]
mherweg has quit [Ping timeout: 250 seconds]
payne has joined #cubieboard
D0pamine has quit [Remote host closed the connection]
DV has quit [Ping timeout: 245 seconds]
DV__ has quit [Ping timeout: 276 seconds]
DV has joined #cubieboard
TheSeven has quit [Ping timeout: 252 seconds]
TheSeven has joined #cubieboard
bizarro_1 has quit [Quit: Leaving]
JohnDoe_71Rus has joined #cubieboard
DV__ has joined #cubieboard
DV__ has quit [Ping timeout: 240 seconds]
DV__ has joined #cubieboard
weltall has quit [Ping timeout: 256 seconds]
weltall has joined #cubieboard
weltall has quit [Excess Flood]
weltall has joined #cubieboard
DV__ has quit [Ping timeout: 252 seconds]
DV__ has joined #cubieboard
red723 has joined #cubieboard
tat has joined #cubieboard
tat__ has quit [Ping timeout: 252 seconds]
redhair_ has joined #cubieboard
redhair_ has quit [Client Quit]
john3213 has joined #cubieboard
john3213 has left #cubieboard [#cubieboard]
deffrag has quit []
_massi_ has joined #cubieboard
DV has quit [Ping timeout: 240 seconds]
shineworld has joined #cubieboard
sassmann has joined #cubieboard
DV has joined #cubieboard
DV__ has quit [Ping timeout: 258 seconds]
DV__ has joined #cubieboard
DV has quit [Ping timeout: 252 seconds]
DV__ has quit [Remote host closed the connection]
DV has joined #cubieboard
DV__ has joined #cubieboard
tat has quit [Remote host closed the connection]
fossxplorer has joined #cubieboard
DV has quit [Ping timeout: 240 seconds]
red723 has quit [Ping timeout: 252 seconds]
DV has joined #cubieboard
lerc has quit [Ping timeout: 245 seconds]
blsd has quit [Remote host closed the connection]
tat has joined #cubieboard
niklare has joined #cubieboard
shineworld2 has joined #cubieboard
shineworld has quit [Ping timeout: 252 seconds]
lerc has joined #cubieboard
D0pamine has joined #cubieboard
fossxplorer has quit [Remote host closed the connection]
fossxplorer has joined #cubieboard
rz2k has joined #cubieboard
shineworld2 is now known as shineworld
niklare has quit [Remote host closed the connection]
nighty-_ has joined #cubieboard
popolon has joined #cubieboard
popolon has joined #cubieboard
popolon has quit [Changing host]
old-papa has quit [Quit: —I-n-v-i-s-i-o-n— 3.3 (November '11)]
enrico_ has joined #cubieboard
shineworld has quit [Quit: Sto andando via]
ssvb has quit [Quit: Leaving]
D0pamine has quit [Remote host closed the connection]
ssvb has joined #cubieboard
mherweg has joined #cubieboard
deasy has joined #cubieboard
blsd has joined #cubieboard
imRance has quit [Read error: Connection reset by peer]
Freyr_ has joined #cubieboard
Freyr has quit [Ping timeout: 276 seconds]
OutOfLine has joined #cubieboard
tat has quit [Remote host closed the connection]
tat has joined #cubieboard
tat has quit [Remote host closed the connection]
D0pamine has joined #cubieboard
payne has quit [Remote host closed the connection]
D0pamine has quit [Remote host closed the connection]
D0pamine has joined #cubieboard
DV has quit [Ping timeout: 252 seconds]
DV has joined #cubieboard
Thorn has joined #cubieboard
maribu has joined #cubieboard
<maribu>
ssvb: Thank you for helping me yesterday. Sorry that it took so long to be back online again - the kernel package of my distro rendert my cubietruck almost unuseable, so I had to compile my own kernel package first.
<maribu>
I think my cubietruck is generally running stable now, with slightly slower CPU clock. But running lima-memtester still shuts my cubietruck immediatly off.
<maribu>
Personally I would say this is not about hardware, but about the drivers. Till now libGLESv2.so and libEGL.so form mesa where used, not mali specific librarys
bizarro_1 has joined #cubieboard
<ssvb>
maribu: the lima-memtester program does not depend on anything from the userland, it only needs the mali.ko kernel module
<ssvb>
maribu: what is your kernel version?
<maribu>
3.4.86 from linux-sunxi with patched bcmdhd module
<ssvb>
ok, this should be fine
<ssvb>
older kernel versions used to have problems with mali on the systems with 2GB of RAM (such as cubietruck), but this has been resolved
<maribu>
can I run lima-memtester while X running?
<ssvb>
yes
<ssvb>
it will surely mess up the picture on screen, but everything else should be fine
<maribu>
hmm...
<ssvb>
I mean, the lima-memtester and the X server will be updating the picture on screen without knowing anything about each other
<maribu>
it might be important: I'm using your fbturbo driver for acceleration.
<ssvb>
so expect flicker, parts of the desktop showing through and then getting overwritten by the spinning cube again
<ssvb>
the choice of the used Xorg driver does not matter
<maribu>
I could test what happens when I unload sunxi_cedar_mod kernel module
<maribu>
brb
maribu has quit [Quit: Verlassend]
shineworld has joined #cubieboard
D0pamine has quit [Remote host closed the connection]
maribu has joined #cubieboard
<maribu>
ssvb: Looks like this has gone wrong somehow. My cubietruck is still booting, but there's no hdmi signal any more. I'll try a linare image
<ssvb>
maribu: what have you done to break it?
D0pamine has joined #cubieboard
<maribu>
lima-memtester from virtial terminal (no X running) and unloaded cedar and bcmdhd kernel modules
vali has joined #cubieboard
<vali>
hi guys
<vali>
anyone around ?
<maribu>
Also I have chagend script.bin to provide 3 framebuffers ("fb0_framebuffer_num = 3" instead of "fb0_framebuffer_num = 2")
<maribu>
But I changed this back, still no hdmi output :-(
<maribu>
Still I'm not completely convinced that my cubietruck really broke. So I'll try out a fresh lubuntu nand image to check if I just misconfigured something
<maribu>
Hi vali!
<vali>
anyone here using USB to Serial convertors ? I have an issue with mine, it seems that it's refusing any kind of communication over ttyUSB0
JohnDoe_71Rus has quit [Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org]
<maribu>
usbserial might be compiled into the kernel. Have you tried "zcat /proc/config.gz | grep CONFIG_USB_SERIAL="?
<vali>
no
<vali>
CONFIG_USB_SERIAL=y
<vali>
seems compiled
ricardocrudo has joined #cubieboard
D0pamine has quit [Remote host closed the connection]
<maribu>
"y" means compiled into kernel, "m" means compiled as module. So this is not the problem.
<maribu>
What kernel version are you using?
<vali>
3.4.79-sun7i
<maribu>
current version at https://github.com/linux-sunxi/linux-sunxi is 3.4.86. You might have been using a more current kernel version with newer version the ftdio_sio kernel module
<vali>
just using the one in cubian
<maribu>
You could try if you can build the ftdio_sio module from the current kernel at linux-sunxi against the kernel you're using
<ssvb>
maribu: with "fb0_framebuffer_num = 3" you need to be sure to have enough memory reserved for the framebuffer
<vali>
maribu -> /root/ftdi_sio/ftdi_sio.c:2487:32: error: ‘struct usb_serial_port’ has no member named ‘delta_msr_wait’
<ssvb>
maribu: this is not very failsafe and foolproof
tat has joined #cubieboard
<maribu>
ssvb: This wouldn't do permanent damage, would it?
<ssvb>
maribu: no, just the system becomes unbootable until you revert the script.bin changes
<maribu>
ssvb: I have done this. It booted fine with both setting, I just don't get hdmi ouput
<ssvb>
maribu: still in your case, some sort of a hardware defect in your cubietruck is not out of question
<ssvb>
maribu: the symptoms are rather unusual and it might be just gradually dying
<maribu>
ssvb: It looks this way :-( I hope the warrenty covers this :-( But I'll try lubuntu first. Maybe I have done something silly without noticing it
<maribu>
vali: Looks like ftdi_sio from current kernel is not comptible out of the box with the cubian kernel
<vali>
seems so
<vali>
where could I download the latest ?
tat has quit [Remote host closed the connection]
<maribu>
vali: I don't know if there is a current kernel package for cubian provided. You could still compile one from the github sources yourself
<vali>
just did..
<vali>
I will see if it works..
<vali>
reboot
<maribu>
vali: Huh? So fast? Crosscompiled from a super computer ;-) ?
<vali>
no, just compiled the module
<maribu>
ahh
<vali>
[ 19.403704] usb 1-1.3: FTDI USB Serial Device converter now attached to ttyUSB0
<jelly>
tha magic of having correct linux-headers available
<vali>
now to see if it works..
<vali>
nah, still zero
<jelly>
vali: does the usb-serial module work when you connect it to a PC and access the same serial device?
<vali>
yep
cart has joined #cubieboard
<jelly>
good
<maribu>
vali: You have succesfully compiled the ftdi_sio module from the current github linux-sunxi kernel, correct?
<vali>
yep
twave has quit [Read error: Connection reset by peer]
<vali>
and it's the same situation for now
Mantichora has quit [Quit: leaving]
<vali>
the device is seen, etc but not working
Mantichora has joined #cubieboard
<vali>
I was thinking it has something to do with stty
<vali>
but this settings worked with the previous kernel, etc
<vali>
and cannot find any setting that could trigger this
<cart>
i have a question, i have lubuntu-nand version in my cubietruck, and i want to change to cubian, i've made cubian sdcard, but how do i make cubietruck boot from my sdcard?
twave has joined #cubieboard
<vali>
cart it should work out of the box
<cart>
but my cubietruck still boot to lubuntu
<vali>
aaaaa
<vali>
I guess you have to erase the nand partition
<cart>
maybe..., but i'm running windows now...
<cart>
aaaaaaaaaaa
<vali>
well...this usb to serial is a complete party stinker
<cart>
a.....i reboot again then it boot to cubian
<wiak>
hmm did you try switching around rx and tx?
<wiak>
its a bit funky on my system
<wiak>
in linux i have to use rx on tx but in windows i have to do tx on rx lol
<wiak>
and you also have to sudo screen /dev/ttyUSB0
<wiak>
and you also have to sudo screen 115200 /dev/ttyUSB0
<wiak>
use 115200 baudrate
<vali>
stty -F /dev/ttyUSB0 -cstopb -parenb -parity raw speed 2400
<vali>
this is what I use
<vali>
the strange thing is that interceptty is not getting what I'm sending to the tty
<vali>
why is that ?
shineworld has quit [Quit: Leaving]
tat has joined #cubieboard
mherweg1 has joined #cubieboard
mherweg1 has quit [Client Quit]
tat has quit [Remote host closed the connection]
mherweg has quit [Ping timeout: 250 seconds]
seppel has joined #cubieboard
cart has quit [Quit: Page closed]
gzamboni has quit [Read error: No route to host]
tat has joined #cubieboard
gzamboni has joined #cubieboard
rz2k has quit []
rundfunk has quit [Ping timeout: 240 seconds]
smccarthy has joined #cubieboard
rundfunk has joined #cubieboard
sassmann has quit [Ping timeout: 240 seconds]
maribu_ has joined #cubieboard
qermit has joined #cubieboard
<maribu_>
ssvb: I've solved both problems now. Both are the result of me being stupid :-(
<maribu_>
ssvb: 1st problem: No hdmi output. I have editit uEnv.txt with vim, which appearently thinks uEnv.txt is a normal text file and auto breaks lines
<maribu_>
ssvb: So the part of the kernel cmdline which enables hdmi output was striped of the another line
<maribu_>
ssvb: 2nd problem: It was a power problem. So power supply is ok, but the usb-cable was too cheap and too long
<maribu_>
ssvb: with a shorter usb-cable there is enough power for cpu and gpu running both at the same time
<maribu_>
ssvb: I'm sorry that I wasted your time with such stupid problems :-(
shineworld has joined #cubieboard
<ssvb>
maribu_, it's good to know that you have resolved all the problems
<ssvb>
now you probably want to increase the cpu and dram clock speed again for better performance
<maribu_>
already did ;-)
<maribu_>
Thank you very much for you help :-)
<ssvb>
you are welcome :-)
<ssvb>
and it's a good idea to keep lima-memtester running for a while (at least for a few hours, or even better - overnight), just to be sure that everything is ok at the high dram and cpu clock speeds
<maribu_>
ok, my cubietruck will be busy tonight ;-)
mogurakun has joined #cubieboard
ohama has quit [Remote host closed the connection]
ohama has joined #cubieboard
maribu_ has quit [Remote host closed the connection]
twave has quit [Quit: Leaving]
twave has joined #cubieboard
datagutt has joined #cubieboard
froy has quit [Remote host closed the connection]
mherweg has joined #cubieboard
maribu has quit [Remote host closed the connection]
D0pamine has quit [Ping timeout: 258 seconds]
froy has joined #cubieboard
TheSeven has quit [Ping timeout: 245 seconds]
TheSeven has joined #cubieboard
D0pamine has joined #cubieboard
mherweg has quit [Quit: Leaving.]
popolon has quit [Quit: Quitte]
syeekick has joined #cubieboard
seppel has quit [Quit: Leaving]
RA3OR has quit [Ping timeout: 265 seconds]
enrico_ has quit [Quit: Bye]
<jelly-home>
vali: what kind of device are you connecting to?
<jelly-home>
(also, did you try a serial terminal tool like minicom)
RA3OR has joined #cubieboard
_massi_ has quit [Remote host closed the connection]