00:47 | Coburn | [09:43:54] [20:40:15] using ssh, if you have not touched the keyboard for 2 secs, it takes 2-3 secs to wake up |
00:47 | Coburn | Yes. Observed same behaviour |
00:48 | Coburn | However, mosh (mobile shell) doesn't do it |
04:37 | Coburn | Could someone please brief me on what kernels there are available for the CuBox? I want to keep a record of what versions |
04:37 | Coburn | at the moment, I know the following |
04:38 | Coburn | 2.6.37 = marvell kernel, buggy optical out, factory ubuntu 9.04 kernel |
04:38 | Coburn | 3.5.3 = GeeXbox kernel (until recently?) |
04:38 | Coburn | 3.5.7: Most common |
04:38 | Coburn | 3.6.x (?): Experimental |
04:38 | Coburn | 3.7 (?): Experimental |
04:39 | Coburn | If you can tell me what kernels exist for it, I can write it up |
09:02 | jnettlet | Coburn|Away, dbsx, you may also be running into a problem with entropy gathering. I found that modern kernels are broken and most ARM machines aren't generating enough entropy for random and urandom. So when you go to open a program, or do anything with SSL or SSH you are going to get lag while randomness is generated. The best solution is to use rngd to transfer randomness from the dovefb HWRNG to /dev/urandom. |
09:05 | jnettlet | you can take a look by catting /proc/sys/kernel/random/entropy_avail A healthy system will have between 3500 and 4000 bytes. Most modern kernels are sitting around < 200 bytes all the time so anytime anything that needs randomness is run the kernel and SOC have to generate it. The worst part about that is there are lots of locks in the generation code for security so everything on a single core CPU gets blocked while this is happening |
11:43 | dbsx | jnettlet: what you say is correct, but this is not the problem we obeserve. |
22:02 | RandomPixels | hello |
22:06 | RandomPixels | i just found out something strange on my cubox |
22:06 | RandomPixels | when doing a df -h |
22:06 | RandomPixels | i see /dev/mmcblk0p1 19M 4.7M 13M 27% /media/b7233519-a78b-436e-8d14-35549e802180 |
22:35 | RandomPixels | rabeeh, i need some small help regarding flashing u-boot |
22:35 | RandomPixels | or anyone |
22:47 | RandomPixels | hello again |
22:59 | dbsx | RandomPixels: What do you wish to know? |
23:00 | RandomPixels | i tried the Mac OSX approach listed here http://www.solid-run.com/mw/index.php/Flashing_U-Boot#OS_X |
23:01 | dbsx | V1 or V2 cubox |
23:01 | RandomPixels | v1 or v2 ? |
23:02 | RandomPixels | hmmm, i think it's v2 as far as i remember |
23:02 | dbsx | and |
23:02 | RandomPixels | downloaded files, disconnected cubox |
23:02 | RandomPixels | Connect the USB cable to the OS X computer -> i do that |
23:02 | RandomPixels | i ran screen /dev/tty.usbserial 115200 |
23:02 | RandomPixels | and it only shows a blinking cursos |
23:03 | RandomPixels | cursor * |
23:04 | dbsx | Did you power up before or after issuing the screen command? |
23:05 | RandomPixels | power up -> you mean inserting the power cable ? |
23:05 | RandomPixels | i thought it gets power from USB |
23:05 | dbsx | I mean the cubox power |
23:06 | RandomPixels | it doesn't have a power switch |
23:07 | RandomPixels | wait for it |
23:08 | dbsx | ok. Read the windows instructions above the Mac instructions, add steps 11 onwards to the end of the instructions |
23:11 | RandomPixels | Cannot exec 'sx': No such file or directory |
23:13 | dbsx | So now you are out my comfort zone. Find out how to get 'sx' (xmodem) installed on your Mac. |
23:13 | RandomPixels | okey, thanks |
23:36 | RandomPixels | i'm back |
23:36 | RandomPixels | Sending Downloads/u-boot-cubox_hynix_cubox_uart.bin, 2651 blocks: Give your local XMODEM receive command now. |
23:39 | RandomPixels | Timeout on sector ACK |
23:39 | RandomPixels | :) |
23:39 | RandomPixels | just doesn't want to go :) |
23:43 | RandomPixels | now i see the CuBox >> |
23:43 | RandomPixels | prompt |
23:57 | dbsx | RandomPixels: once you get CuBox >> you should be OK. From there you can load your new spi.bin |
23:57 | RandomPixels | fatload usb 0:1 0x200000 myfile.bin ? |
23:58 | dbsx | yep , |