| 09:18 | R0nd | how can I set up vnc server to connect to the "desktop session"? |
| 09:45 | mk01 | put into into xrc file |
| 09:45 | mk01 | into YOURs home dir |
| 09:46 | mk01 | then programs put there will be started ONCE session for you is opened |
| 09:46 | mk01 | if you want to access GREETER via VNC |
| 09:46 | mk01 | it is not possible |
| 09:46 | R0nd | hmm got it |
| 09:48 | mk01 | but you can allow greeter to other machines via xcmb (or what is the name of it) ... |
| 09:48 | mk01 | literally broadcast x greeter |
| 09:48 | mk01 | what is your client OS ? |
| 09:49 | R0nd | I'm using xrdp + windows rdp client |
| 09:50 | mk01 | ach ok |
| 09:50 | mk01 | but |
| 09:50 | mk01 | there is a way |
| 09:50 | mk01 | if we speak about Cubox and Xorg video driver on FB |
| 09:51 | mk01 | you can run FB vncserver (not x11) |
| 09:51 | R0nd | FB? |
| 09:51 | mk01 | framebuffer |
| 10:03 | R0nd | mk01_: can you give me a link? doesn't look like there's a debian package for it |
| 10:04 | mk01_ | http://xbian.brantje.com/pool/stable/main/x/xbian-package-vnc-server/xbian-package-vnc-server_1.1.0_armhf.deb |
| 10:04 | R0nd | cool, thanks |
| 10:05 | mk01_ | if there are XBian specific dependencies making impossible installing for you |
| 10:05 | mk01_ | just unpack with dpkg -x |
| 10:05 | CurlyMo | or just use XBian :) |
| 10:13 | kivutar | with LK 3.14.14, I get a segfault 0x769e92b0 in gcoHAL_QueryChipCount () from /usr/lib/libGAL.so when launching a 3D app |
| 10:15 | mk01_ | missing galcore |
| 10:19 | kivutar | mk01_, I have the /usr/lib/libGAL.so and all |
| 10:19 | kivutar | or you mean that galcore can be missing in my kernel? |
| 10:19 | mk01_ | missing driver in kernel |
| 10:19 | mk01_ | libGAL crashing on that call because there is no such function available |
| 10:20 | mk01_ | kivutar |
| 10:20 | kivutar | mk01_, do you know which modules are needed? |
| 10:20 | mk01_ | in Drivers -> Graphics -> GalCore |
| 10:21 | mk01_ | it probably got Un-checked with your config migration from 3.10. |
| 10:21 | mk01_ | it happened to me as well |
| 10:21 | kivutar | thanks :) |
| 10:21 | mk01_ | welcome |
| 10:22 | kivutar | mk01_, in Device Drivers -> Graphic Support? |
| 10:23 | mk01_ | yes |
| 10:23 | kivutar | I don't have GalCore listed here |
| 10:23 | mk01_ | Vivante ? |
| 10:23 | kivutar | neither |
| 10:23 | R0nd | mk01_: I get "mmap: Invalid argument" when launching imx-vncserver, should I supply any arguments> |
| 10:25 | mk01_ | Vivante GCCore |
| 10:25 | mk01_ | Rond what distro you have ? |
| 10:25 | R0nd | debian jessie |
| 10:25 | mk01_ | HM |
| 10:26 | mk01_ | ach |
| 10:26 | mk01_ | check for deoendencies like libvncclient, libvncserver |
| 10:26 | mk01_ | in original package |
| 10:26 | mk01_ | install them |
| 10:27 | kivutar | ok I had to check drm |
| 10:27 | kivutar | thanks |
| 10:27 | mk01_ | libc6, libvncserver0, zlib1g, libjpeg8, libgcrypt11, libgnutls26, libgcc1, libgpg-error0, libtasn1-3-dev, libp11-kit-dev |
| 10:28 | mk01_ | kivutar: ah so latest Jnettlets updates changed to IMX drm including it's HDMI and FB ? |
| 10:29 | mk01_ | R0nd: libc6, libvncserver0, zlib1g, libjpeg8, libgcrypt11, libgnutls26, libgcc1, libgpg-error0, libtasn1-3-dev, libp11-kit-dev |
| 10:30 | R0nd | mk01_: apparently it wants xbian-package-firmware |
| 10:32 | mk01_ | check lib depends |
| 10:33 | mk01_ | "ldd /usr/local/sbin/imx-vncserver" |
| 10:33 | mk01_ | or just take our source and compile |
| 10:33 | R0nd | bbl lunch |
| 10:33 | mk01_ | it barelly has 2kb |
| 10:33 | mk01_ | the source |
| 10:34 | jnettle | 10:34 * jnettlet doesn't want to here any complaints from people using -drm. That is a purely dev based branch |
| 11:12 | rabeeh | the -drm tree is experimental. please no one uses that unless he has all the source code. |
| 11:15 | bencoh | "unless he has all the source code" ? |
| 11:25 | dv__ | bencoh: some parts are in another git repo |
| 12:09 | R0nd | mk01: I've built imx-vncserver from source, but it still throws mmap: Invalid argument |
| 12:11 | mk01 | then only kernel difference is in the question |
| 12:12 | mk01 | since I rewrote it to work with imx6 framebuffer and put as default package into XBian (1 year) never had such issue |
| 12:12 | mk01 | even reported by user |
| 12:13 | mk01 | can you try |
| 12:13 | mk01 | starting it before you start greeter ? |
| 12:14 | mk01 | so it get's on to framebuffers as first before possible locks by others ? |
| 12:16 | R0nd | mk01: what's the best way to do that? linux noob here |
| 12:18 | FoXMaN | hello |
| 15:31 | sobel | can anyone recommend a reliable distribution to help me figure out whether my cubox-i is bricked |
| 15:32 | deniska | hm, I don't think it's that easy to brick cubox-i |
| 15:33 | sobel | yeah, i don't either, and i don't suspect it's soft-bricked. i have never seen it boot and i want to correctly rule out the possibility that it will boot at all before i toss it |
| 15:33 | deniska | well, debian and ubuntu images from the site worked for me |
| 15:33 | sobel | the spdif port gets lit up, and i see a dim red light near the SD card |
| 15:33 | deniska | I use arch although it has more tedious installation process |
| 15:34 | sobel | cool, i'll probably try deb then |
| 15:34 | R0nd | spdif isn't supposed to stay lit up normally |
| 15:36 | sobel | so i should expect to see it go out once the kernel takes control of the hardware |
| 15:37 | jnettlet | sobel, does the front LED light up? |
| 15:38 | deniska | sobel: connect it through mini usb port to pc |
| 15:38 | sobel | jnettlet: there's a dim red light in the middle of the front panel, top right corner of the HDMI plug. that lights up. |
| 15:38 | deniska | and see if anything will happen in serial console |
| 15:38 | sobel | deniska: oh? it's a USB serial port? i can try that |
| 15:39 | jnettlet | sobel, the front isn't near the sdcard that is the back. Does the front LED come on? |
| 15:40 | sobel | oh...opposite side of the SD card? no. |
| 15:40 | sobel | should it be near the IR window? |
| 15:40 | jnettlet | inside the ir window |
| 15:40 | sobel | yeah. no. sounds like i have a brick. |
| 15:40 | sobel | thx |
| 15:40 | jnettlet | then your device is fine, but the CBi can't read u-boot from the sdhc card properly |
| 15:40 | jnettlet | sobel, you can't brick these devices. |
| 15:40 | jnettlet | it is impossible |
| 15:40 | sobel | not softbricked |
| 15:41 | sobel | a brick is a rectangular prism |
| 15:41 | jnettlet | you just didn't write whatever image you downloaded properly to the sdhc card, or the image is bogus |
| 15:41 | sobel | my cubox meets the description, i'm not describing having ruined it by use. i'm pretty sure it started this way. |
| 15:42 | sobel | are directions for writing cubox SD cards very different from say, raspberry pi cards? |
| 15:42 | joelbaby | i doubt you can brick a cubox. |
| 15:42 | jnettlet | I am certain the sdhc that shipped with it worked |
| 15:42 | joelbaby | sobel > yes. |
| 15:42 | sobel | i didn't order any SD card with this thing |
| 15:42 | joelbaby | there are very specific things you need to do to prepare the SD card. |
| 15:42 | joelbaby | if you don't use an image. |
| 15:42 | sobel | i would love it if i've simply done it wrong |
| 15:42 | joelbaby | you've done it wrong. |
| 15:42 | sobel | URL please? |
| 15:43 | joelbaby | do you want an image for xbmc? |
| 15:43 | sobel | i can follow directions, but it very much sounds like i did not find good directions |
| 15:43 | joelbaby | what do you want your cubox to run? |
| 15:44 | sobel | joelbaby: i think that would be a good start. i am working with openelec and volumio on my rpi to figure out which one of those i like better, and was hoping to do the same trial with the cubox |
| 15:44 | joelbaby | ok. well geexbox and openelec are both available. |
| 15:45 | joelbaby | try geexbox first: http://download.geexbox.org/snapshots/geexbox-xbmc-imx6-cuboxi/latest/binaries.cuboxi/ |
| 15:45 | sobel | joelbaby: if i can make volumio work on the cubox too, that'd be hip. today i just want to see it boot anything. |
| 15:45 | joelbaby | are you using windows or linux to prepare the SD card? |
| 15:45 | sobel | os x |
| 15:45 | sobel | so, dd more or less like i would under linux |
| 15:46 | joelbaby | how big is your micro sd card, and what class is it? what is the number in the little circle? |
| 15:46 | sobel | 8GB, class 4 |
| 15:47 | joelbaby | http://www.solid-run.com/wiki/Flash_an_image |
| 15:47 | joelbaby | look at the flash_an_image instructinos, and use the image in the geexbox link. |
| 15:48 | joelbaby | class 4 card will work. but class 10 is better (something that can read/write at 20MB/s). |
| 15:48 | joelbaby | class 4 is limisted to about 5MB/s. |
| 15:49 | kivutar | rabeeh, got LK3.14.14 working for lakka, but OpenELEC just switched to 3.14.17 yesterday |
| 15:49 | sobel | yeah, i've experienced the wide performance differences of SD cards already. i have a P* brand class 10 card that writes at a good 160K/s |
| 15:49 | sobel | avoid P*. their branding tries to emulate Patriot. |
| 15:49 | joelbaby | 160K/s .... it must be broken. |
| 15:50 | sobel | it was the cheapest Fry's had |
| 15:50 | joelbaby | you mean 0.16MB/s ? |
| 15:51 | joelbaby | it cannot be a class 10 card, because they need to do 10MB/s. |
| 15:51 | joelbaby | minimum |
| 15:51 | sobel | 1782579200 bytes transferred in 10020.680561 secs (177890 bytes/sec) |
| 15:51 | sobel | pure shit |
| 15:51 | sobel | broken at best |
| 15:51 | joelbaby | take it back, and ask for you 25cents back. |
| 15:52 | sobel | right? not worth the gas until i'm going there for something else anyway |
| 15:52 | joelbaby | samsung, kingston, sandisk all make good cards. |
| 15:52 | sobel | hindsight=20/20. i'll hit walgreens for camera memory next time. |
| 15:52 | joelbaby | buy it on ebay or amazon or newegg. postage is not high on an micro sd card. |
| 15:53 | sobel | duracell also makes a properly performing class 10 card. |
| 15:53 | joelbaby | well don't put that dogshit card into your cubox because it wont work. |
| 15:54 | joelbaby | the class 4 should be fine. |
| 15:54 | sobel | which of those geexbox files do i want? the img or the slightly larger tar? |
| 15:55 | joelbaby | well, on a Mac i'm not sure. On a PC you would use the img.xz and then use an sd card image writer. |
| 15:55 | joelbaby | the .tar is more for linux systems using that make-sdcard.sh script. |
| 15:56 | joelbaby | also ... to get to your first question ... |
| 15:56 | joelbaby | if you use an image, then the special stuff that needs to be on the SD card will be put there for you. |
| 15:56 | sobel | unxz... geeze, another zip program? |
| 15:57 | joelbaby | If you don't use an image, then you have to do special writes to the first sectors of the SD card. |
| 15:57 | sobel | looks like i need to use or port or reverse-engineer the linux script |
| 15:58 | sobel | thanks, i'll probably be back after the image downloads and i get it loaded up or fail |
| 15:58 | joelbaby | in the instructions it says use Win32 disk imager |
| 15:58 | joelbaby | on a mac, there must be a similar utility. |
| 15:59 | sobel | there is but i hate learning a GUI then having no automation tools. dd works well enough when i can get accurate directions. |
| 15:59 | sobel | os x isn't weird anymore |
| 16:00 | joelbaby | try that: http://alltheware.wordpress.com/2012/12/11/easiest-way-sd-card-setup/ |
| 16:00 | joelbaby | seems like someone with an rpi and a mac had the same problems. |
| 16:01 | joelbaby | if you can use dd, then follow the instructions here: http://www.solid-run.com/wiki/Flash_an_image |
| 16:01 | sobel | that's strange, as i have no trouble with rpi images written from my mac |
| 16:01 | joelbaby | first part of that link is for windows, then scroll down for linux |
| 16:01 | sobel | yeah, i will |
| 16:01 | joelbaby | also get an extra micro sd card, so you can try different images |
| 16:02 | sobel | will be back... gonna go eat and stuff before an SD card starts to look tasty |
| 16:02 | joelbaby | you need to switch them and its frustrating, cos you have to remove the HDMI cable. |
| 16:02 | joelbaby | with 2 cards, you can switch between images more easily. |
| 16:02 | sobel | yeah, i hear that. i have 6 cards already. i'm not that new to embedded dev. |
| 16:02 | joelbaby | you can test the speed of your sd card like this: |
| 16:02 | joelbaby | cd to your card |
| 16:03 | sobel | just hitting a couple bumps with cubox imaging. sounds like i can solve it with procedure though. |
| 16:03 | joelbaby | then "dd if=/dev/zero of=test BS=1K COUNT=1M" |
| 16:03 | sobel | i hit ^T during dd to get perf data |
| 16:03 | sobel | which ammortizes the initial buffer load across the entire job, but it's close enough for estimation |
| 16:04 | joelbaby | http://www.solid-run.com/wiki/Flash_an_image |
| 16:04 | sobel | food. bout to eat an SD card. back later. :) |
| 16:04 | joelbaby | i just scrolled a little further down, and it has OS X instructinos too. |
| 16:04 | joelbaby | bye |
| 16:59 | sobel | still no boot light. i think i have a bad cubox. |
| 17:00 | sobel | i installed the Prolific usb-serial device driver, and it didn't recognize the cubox |
| 17:08 | rabeeh | sobel: Prolific? |
| 17:09 | sobel | rabeeh: PL-2303 |
| 17:09 | sobel | http://www.solid-run.com/archive/mw/index.php/Serial_console |
| 17:09 | rabeeh | you have the older CuBox and not CuBox-i |
| 17:09 | rabeeh | you do know that - right? |
| 17:10 | sobel | maybe.. i have model I1-300-D |
| 17:11 | sobel | http://www.solid-run.com/wp-content/uploads/2014/06/SolidRun_UM_Cubox-i.v-2.0.pdf says my model is a "Cubox-i" |
| 17:12 | rabeeh | so you don't have any serial console access |
| 17:13 | sobel | oic. so v1 and v2 aren't revisions of Cubox-i |
| 17:13 | rabeeh | ? |
| 17:13 | rabeeh | which v1 and v2? |
| 17:13 | rabeeh | those are probably for the older CuBox |
| 17:13 | rabeeh | CuBox and CuBox-i are completely different products |
| 17:13 | sobel | ok |
| 17:15 | sobel | i really want this (or any) cubox to work for me.. the hardware trashes raspberry pi where it counts the most |
| 17:16 | rabeeh | sobel: what are you trying to achieve; i see lots of issues above that are fixed |
| 17:16 | rabeeh | where are you stuck now? |
| 17:19 | sobel | rabeeh: haven't yet successfully booted any image. the SD cards i've tried all boot my rpi so i don't suspect the cards. |
| 17:19 | rabeeh | have you flashed an image correctly? if yes what is the exact url? |
| 17:20 | sobel | http://www.solid-run.com/wiki/Flash_an_image |
| 17:20 | sobel | the process was unremarkable. that's like every other use of dd to prepare an image on an SD card. |
| 17:22 | sobel | no boot LED, spdif port is lights up, no HDMI signal. |
| 17:22 | sobel | attempting to burn the geexbox image from http://download.geexbox.org/snapshots/geexbox-xbmc-imx6-cuboxi/latest/binaries.cuboxi/ |
| 17:28 | rabeeh | sobel: did you unxz that image? |
| 17:28 | rabeeh | specifically this one - http://download.geexbox.org/snapshots/geexbox-xbmc-imx6-cuboxi/latest/binaries.cuboxi/geexbox-devel-20140831-re61347d.cuboxi.img.xz |
| 17:28 | rabeeh | i.e. wget http://download.geexbox.org/snapshots/geexbox-xbmc-imx6-cuboxi/latest/binaries.cuboxi/geexbox-devel-20140831-re61347d.cuboxi.img.xz |
| 17:28 | rabeeh | unxz geexbox-devel-20140831-re61347d.cuboxi.img.xz |
| 17:28 | rabeeh | and then dd that image? |
| 17:31 | sobel | yeah, i unxz to get geexbox-devel-20140831-re61347d.cuboxi.img |
| 17:32 | sobel | then sudo dd bs=4096 if=geexbox-devel-20140831-re61347d.cuboxi.img of=/dev/rdisk1 |
| 17:34 | Artox | I just want to throw in there is xzcat too |
| 17:34 | sobel | i actually used The Unarchiver |
| 17:34 | Arto | 17:34 * Artox xzcat img.xz | sudo dd of=/dev/sdX |
| 17:34 | Artox | which saves you the space on hd, and the unpack time |
| 17:35 | sobel | i guess there was something wrong with using gzip |
| 18:31 | joelbaby | i actually used The Unarchiver |
| 18:31 | joelbaby | hmmmm |
| 18:35 | dv__ | "The Unarchiver" |
| 18:35 | dv__ | sounds like a movie |
| 18:35 | dv__ | in theaters now |
| 18:35 | joelbaby | sobel. question. after the image is written to sd card with dd - do you eject the card before removing it? |
| 18:36 | joelbaby | dv__ i just finished watching edge of tomorrow |
| 18:45 | rabeeh | eject and give it a hug |
| 18:48 | hste_ | rabeeh: I did read it as: eject and give it a bug :) |
| 18:51 | R0nd | I got my cubox a hard drive :) |
| 18:54 | R0nd | it's clicking for some reason |
| 18:56 | iz | R0nd: try sudo hdparm -B 255 /dev/sdwhatever |
| 18:56 | iz | or try 254 |
| 18:58 | joelbaby | r0nd is it clicking a lot? |
| 18:59 | joelbaby | mine did, until i upgraded the power supply. |
| 18:59 | joelbaby | to the cubox |
| 18:59 | rabeeh | joelbaby: oh; so your hard drive issues are gone? |
| 18:59 | joelbaby | rabeeh, as i explained in the forums. I had to use a 3Amp (i got 4A) power supply. |
| 19:00 | joelbaby | the reason is that on a cubox-i2Ultra 2A is not enough |
| 19:00 | rabeeh | oh ! |
| 19:00 | rabeeh | i completely forgot that you are on CBi2u |
| 19:00 | joelbaby | also, I think it is because your smoothing capacitors in your current limiter circuit are too small. |
| 19:00 | rabeeh | so; it's not capacitors issues then :) |
| 19:01 | joelbaby | as per the specifications |
| 19:01 | joelbaby | no ... i think the capacitors being too small are the reason i need a bigger supply |
| 19:01 | rabeeh | joelbaby: those specs are written to cover their asxx |
| 19:01 | R0nd | joelbaby: yeah, it's just clicking continuously |
| 19:01 | rabeeh | they are not |
| 19:01 | joelbaby | r0nd disconnect it, you will kill your HDD |
| 19:01 | R0nd | okay shutting down |
| 19:02 | joelbaby | R0nd plug your HDD into a powered USB hub, or get a bigger power supply for the cubox-i |
| 19:02 | R0nd | gonna try to power it from a separate source |
| 19:02 | joelbaby | rabeeh ... did you try bigger capacitors? |
| 19:02 | joelbaby | when i mean 'bigger' its like 120uF ... so that's pretty tiny |
| 19:02 | joelbaby | but still bigger than the 22uF you put in. |
| 19:03 | R0nd | I think that did the trick |
| 19:03 | joelbaby | rabeeh because what happens i when you start up a USB HDD with high internal CAPACITANCE ... you need more juice to get it started. |
| 19:04 | joelbaby | rabeeh it is the internal capacitance of the HDD causing the problems i think |
| 19:04 | joelbaby | rabeeh which is quite clearly explained in the specifications of the current limiter chip. |
| 19:04 | rabeeh | joelbaby: as i previously told ya i tried several drives and all worked |
| 19:04 | joelbaby | with what power supply rabeeh? |
| 19:04 | joelbaby | what amp? |
| 19:04 | rabeeh | 3A |
| 19:04 | rabeeh | :) |
| 19:04 | joelbaby | right now do it with a 2A |
| 19:05 | joelbaby | and then see what happens |
| 19:05 | joelbaby | and then explain why your device that uses 1A, plus a HDD that uses 0.5A can't run off a 2A power supply. |
| 19:05 | joelbaby | rabeeh because you were specifying 2A PSU for anyone with Cubox-i, i2, and i2ultra. |
| 19:06 | rabeeh | joelbaby: but this is not your case |
| 19:06 | joelbaby | rabeeh i had a cubox-i2ultra. |
| 19:06 | rabeeh | your case was even simpler; without heavy workload (i.e. system consumption is << 1A) it doesn't work for you |
| 19:06 | rabeeh | this leaves 1A + to the drive |
| 19:06 | joelbaby | rabeeh and with a 2Amp power supply (which solid run specified) it CANNOT power the USB HDD |
| 19:07 | R0nd | do I need to do something manually? can't see the hdd in /dev/disk |
| 19:07 | joelbaby | and it looks like r)nd had the same problem just now. |
| 19:07 | R0nd | it's spinning alright now |
| 19:07 | joelbaby | rabeeh because on spin up you need more current |
| 19:07 | rabeeh | R0nd: which CuBox-i are you running? |
| 19:07 | dv_ | 19:07 * dv__ never used usb hdds which didnt have their own power supply |
| 19:07 | rabeeh | joelbaby: that's not true !!! |
| 19:07 | R0nd | rabeeh: cubox-i 2ex |
| 19:07 | joelbaby | rabeeh i've measured the current. |
| 19:08 | rabeeh | electronics discharge the internal capacitors on first touch with the vbus; this i can understand |
| 19:08 | joelbaby | directly within the USB hub |
| 19:08 | R0nd | and the hdd is a 2.5" connected via esata and powered from a 1A usb adaptor |
| 19:08 | dv__ | R0nd: what kernel ? |
| 19:08 | R0nd | 3.0.35 |
| 19:08 | joelbaby | rabeeh if you get one of those USB current measurers then you will see that a drive initially pulls ore than 500mA before settling back. |
| 19:09 | dv_ | 19:09 * dv__ remembers having problems with that kernel version and esata |
| 19:09 | R0nd | couldn't manage to update kernel on debian due to my linux noobishness |
| 19:09 | joelbaby | rabeeh and that current can only come from stored charge, if the current limiter truly limits to 500mA |
| 19:09 | dv__ | or was it 3.10.30 ? |
| 19:09 | dv__ | gah, its a long time ago |
| 19:09 | rabeeh | joelbaby: the current limiter shuts down it's transistors around 650mA to 700mA |
| 19:10 | joelbaby | rabeeh ... ok. well current doesn't get that high |
| 19:10 | dv__ | R0nd: gotta run to the mall now, I'll check my dmesg output later to see if there is any esata log that you should also see |
| 19:10 | rabeeh | joelbaby: you should understand how the design work |
| 19:10 | joelbaby | rabeeh but you gotta stop telling people to get 2A power supplies if they are going to run USB HDD |
| 19:10 | joelbaby | because it doesn't work. |
| 19:10 | rabeeh | in the recommendation of the current limiter manufacturer they don't know what other components are on the board |
| 19:10 | joelbaby | but 3A PSU is ok. |
| 19:10 | rabeeh | we have at least 7-8 22uF capacitors before the current limiter to back it up |
| 19:11 | rabeeh | from all sort of circuitries (microsom, LDOs, dc-dc, wifi). they all use 22uF on the 5V rail |
| 19:11 | joelbaby | rabeeh ... if you're not going to try the manufacturers recomendation of capacitance |
| 19:11 | joelbaby | rabeeh ... then could you at least inform customers to get a 3A supply? |
| 19:12 | rabeeh | no. i don't work like this. i fully work on engineering failures and then i would recommend |
| 19:12 | rabeeh | first i need to see it to fail; and not upon a hunch... please understand me joelbaby !!! |
| 19:12 | joelbaby | so you prefer to see people like r0nd with his clicking drive |
| 19:12 | joelbaby | and me too |
| 19:13 | joelbaby | before you accept that a 2A supply is not enough? |
| 19:13 | rabeeh | joelbaby: no; i don't like seeing that |
| 19:13 | rabeeh | i would like to reproduce and sort it from it's root causes. |
| 19:13 | joelbaby | ok, so get a 2A power supply |
| 19:13 | joelbaby | and try it |
| 19:13 | rabeeh | ok. |
| 19:13 | joelbaby | because you haven't tried that |
| 19:13 | rabeeh | which drive? the WD one? |
| 19:13 | joelbaby | yet you tell ppl that a 2A supply is ok. |
| 19:13 | joelbaby | i'll send you one to israel |
| 19:13 | rabeeh | ok |
| 19:14 | joelbaby | its just an old(ish) usb2.0 drive. |
| 19:14 | rabeeh | joelbaby: i'll PM you |
| 19:14 | joelbaby | even that won't spin up |
| 19:14 | joelbaby | ok |
| 19:14 | rabeeh | which brand is it first? |
| 19:14 | joelbaby | Acer or Asus |
| 19:14 | joelbaby | i think Acer |
| 19:15 | joelbaby | just a 3yr old simple 640Mb USB2.0 drive. |
| 19:16 | joelbaby | rabeeh but you could just plug a 2A supply into a cubox-i2ultra and see what happens when you connect a drive |
| 19:16 | joelbaby | because you are testing with a 3A supply, but telling us that 2A is sufficient. |
| 19:16 | rabeeh | which distro? firmware? |
| 19:16 | rabeeh | or just u-boot is good enough? |
| 19:17 | joelbaby | i think it went wrong in u-boot |
| 19:17 | joelbaby | at some point i messed around with the console cable, thinking it might be geexbox going wrong |
| 19:17 | joelbaby | and it would say scsi disk spinning up |
| 19:17 | joelbaby | ............................. |
| 19:17 | joelbaby | ............................. |
| 19:18 | joelbaby | and die |
| 19:19 | joelbaby | anyway PM me if you like, or I'll try and video it going wrong so you can see |
| 19:19 | joelbaby | i'll give you a youtube link or something. |
| 19:22 | malte | debian@debian-imx6:~$ lsusb |
| 19:22 | malte | Bus 002 Device 003: ID 1058:1042 Western Digital Technologies, Inc. |
| 19:22 | malte | 2A on HBi2EX |
| 19:23 | jnettlet | joelbaby, I have tested usb 5400rpm 2.5" driver run from a i4p with a 1.5A power supply. it works |
| 19:23 | malte | my one is a WD 1TB 2,5 |
| 19:26 | joelbaby | jnettlet, malte i think it is the internal capacitance of the drive circuitry which causes the issue. but I can send a drive to rabeeh for him to play with. |
| 19:32 | malte | i got an sata to usb adapter |
| 19:32 | malte | and few old sata drives here,shall i test them too? |
| 19:34 | R0nd | oh, my bad |
| 19:34 | R0nd | my esata cable wasn't plugged in too well |
| 19:34 | R0nd | haha |
| 21:22 | R0nd | what's the most efficient network share to use on cubox? I'm getting 2MB/s write over scp/sshfs and 5MB/s over samba |
| 21:23 | R0nd | I'd like to go faster please :) |
| 21:40 | FoXMaN | R0nd: which kernel? |
| 22:04 | R0nd | FoXMaN: 3.0.35 |
| 22:05 | mk01 | generally it is NFS for *unix |
| 22:06 | mk01 | you should get close to 60MB/s with cubox |
| 22:09 | R0nd | sounds good enough, gonna try it tomorrow |
| 22:09 | R0nd | thanks everyone, see ya |
| 23:13 | metrem | hi all, anybody have already try to build xbmc on a hummingboard-iex2 with xbianonpi patchrun ? |
| 23:13 | kivutar | is sgtl5000 supposed to work with kernels like 3.10, 3.14.14 or 3.14.17(openelec)? |
| 23:14 | metrem | i try to have xbmc (i am on debian wheezy + kernel 3.14.14) |
| 23:25 | mk01 | what is the sgtl5000 ? |