| 07:40 | Talendel | Is anyone available to offer some assistance/suggestions, so that I can get my cubox-i4pro to boot? |
| 07:44 | jnettlet | Talendel, how is it not booting? No front LED, kernel panic, any messages or logs output would be useful as well |
| 07:48 | Talendel | jnettlet: No front LED, but the light is visible in the Optical port. Now, I may be doing things wrong, so I want to make sure I have everything in order. |
| 07:49 | Talendel | I had read that I should be able to use a USB drive in the top port, and boot the device from that, to install the OS over the network. Is that not the case with the i4Pro? |
| 07:50 | Talendel | Currently, I have a blank 16GB microSD in the slot, in addition to the USB drive in the top port, ethernet connected, and the serial console cable connected to the usb port, but the serial console does not seem to be coming up, either. |
| 07:50 | jnettlet | Talendel, we currently don't support that no. You should install the OS onto the SDHC card and boot from that. |
| 07:51 | jnettlet | There is no bootloader on the device. You need to have a bootloader installed on the Micro SDHC card |
| 07:52 | Talendel | Ah. Okay. So I should find an already created image and just dump that to the SD, then go from there? |
| 07:52 | jnettlet | Make sure and follow the wiki instructions for the Cubox-i not the Cubox |
| 07:52 | Talendel | Otherwise, the device is fine? |
| 07:52 | jnettlet | that is a good place to start yes |
| 07:52 | jnettlet | yep |
| 07:53 | Talendel | Okay. That's good, at least. I was just reading the wrong instruction set. Please disregard my derp. XD |
| 07:54 | jnettlet | no problem it is a common misunderstanding. |
| 07:58 | Talendel | Well, I'm off to give this a try. Thank you, again! I'm really looking forward to getting this little box running. Take care and be well, all. :) |
| 08:15 | ralix | morning@all |
| 08:15 | jnettlet | morning ralix |
| 08:20 | ralix | I've got a strange error message by my wlan. Is this normal? |
| 08:20 | ralix | brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Oct 25 2011 19:34:12 version 5.90.125.104 |
| 08:20 | ralix | brcmfmac: brcmf_fil_cmd_data: Failed err=-23 |
| 08:20 | ralix | brcmfmac: brcmf_fil_cmd_data: Failed err=-23 |
| 08:20 | ralix | brcmfmac: brcmf_fil_cmd_data: Failed err=-23 |
| 08:20 | ralix | brcmfmac: brcmf_fil_cmd_data: Failed err=-23 |
| 08:30 | jnettlet | ralix, yep happens. I am testing new wifi drivers this morning. |
| 08:32 | jnettlet | ralix, which kernel version are you using? 3.14 still? |
| 08:32 | ralix | The funny thing is, I can log on my Fritz box when I try to log me via ssh, it goes to the password entry does not on .. With a Lan cable everything goes well ... |
| 08:32 | ralix | mom |
| 08:32 | ralix | Linux version 3.10.30-16-ARCH (nobody@root-chroot-copy) (gcc version 4.8.2 20131219 (prerelease) (GCC) ) #1 SMP Thu Apr 24 16:21:42 MDT 2014 |
| 08:34 | ralix | the driver ist from pepedog (http://myplugbox.com/cb/cuboxi-brcm-firmware.tar.gz) |
| 08:34 | ralix | ups the firmware ;) |
| 08:50 | _dab_ | ralix: I get much the same thing with 3.15rc1, but I also get brcmfmac: brcmf_fws_init: failed to set bdcv2 tlv signaling |
| 13:13 | Steffen_ | hey, does one of you know something about the geexbox packages for the cubox? |
| 13:14 | dz0ny | ask and lurk :) |
| 13:14 | jnettlet | Steffen_, what about them? Always best to ask what you want to know directly. |
| 13:15 | Steffen_ | i have a hard disk connected to the esata port and i want to put it to standby after xx minutes |
| 13:15 | Steffen_ | i think the hdparm package is needed to set this up |
| 13:16 | Steffen_ | the package does exist for geexbox (https://github.com/GeeXboX/geexbox/tree/master/packages/hdparm) but its not in the package archive for the cubox |
| 13:16 | jnettlet | Steffen_, I would go on the forums or mailing list and just request it be added to the build |
| 13:17 | Steffen_ | or is there anotthe solidrun forums? |
| 13:17 | Steffen_ | sry, the solid run forums? |
| 13:18 | jnettlet | they are on the SolidRun forums, but Geexbox is a separate development community. |
| 13:19 | rabeeh | Steffen_: hdparm should work |
| 13:19 | jnettlet | we all work closely with SolidRun, but are not necessarily in the forums. |
| 13:19 | rabeeh | as i recall it send scsi passthrough commands to libata then gets passed to the drive itself |
| 13:19 | rabeeh | the controller inside CBi is a standard AHCI controller. |
| 13:19 | jnettlet | rabeeh, the problem is that hdparm isn't being built for Geexbox on for the cubox-i right now. |
| 13:19 | rabeeh | oh ! |
| 13:19 | Steffen_ | its not in the package list : http://download.geexbox.org/snapshots/geexbox-xbmc-imx6-cuboxi/latest/binaries.cuboxi/packages/ |
| 13:22 | Steffen_ | if the box is running 24/7 it would just be nice to put the hdd in standby to save electricity :) |
| 13:51 | rabeeh | Steffen_: yeah; difinetely |
| 14:19 | Steffen_ | rabeeh, is it possible to include the package in the next update? :) |
| 14:44 | jnettlet | All the Brits that were looking for a UK reseller. Good news. http://www.newegg.com/Product/ProductList.aspx?Submit=ENE&DEPA=0&Order=BESTMATCH&Description=cubox-i&N=-1&isNodeId=1 |
| 14:45 | jnettlet | except they are out of stock :-) |
| 16:48 | msalerno | Has anyone successfully bridged eth0 with wlan0? |
| 16:48 | msalerno | in linux |
| 16:50 | wbx | msalerno: should work, but i didn't used it on a cubox, yet |
| 16:51 | msalerno | @wbx, from what I have read, I need to enable WDS on the wireless interface, but from what I have tried, it's not available in the driver |
| 16:51 | msalerno | # iw dev wlan0 set 4addr on |
| 16:51 | msalerno | command failed: Operation not supported (-95) |
| 16:53 | deniska | http://en.wikipedia.org/wiki/Wireless_distribution_system it seems like something unrelated |
| 16:58 | msalerno | deniska: I agree WDS sounds like an odd solution. It was proposed as a solution for not being able to add wlan0 to the bridge |
| 16:59 | msalerno | brctl addif br0 eth0 wlan0 |
| 16:59 | msalerno | can't add wlan0 to bridge br0: Operation not supported |
| 16:59 | mk01 | msalerno: wlan is returning error on switching to PROMISC mode. so bridge will fail |
| 17:00 | msalerno | mk01: So at this time, the only solution is to go with iptables and routing? |
| 17:03 | Buzzer | Are there disadvantages to doing it with iptables? Just curious, since I want to try something like this too at some point |
| 17:05 | wbx | msalerno: wds is when you combine two boxes via wlan to a big wireless cloud |
| 17:05 | wbx | msalerno: f.e. openwrt routers in a house to have wireless on every stage |
| 17:06 | msalerno | Understood. I was just searching the internet for the error I received when I tried to add wlan0 to the bridge. I found that solution a few times. |
| 17:07 | msalerno | Buzzer: There's no real disadvantage to running iptables. I'm just trying to keep the system as minimal as possible |
| 17:09 | wbx | msalerno: but the wlan driver needs to support bridging. (with a feature similar used in WDS.) the broadcom drivers in OpenWrt do that. but I am unsure if the brcmfull mac driver can do that. |
| 17:19 | mk01 | msalerno: netfilter has "TEE" target in PRE/POST ROUTING tables. maybe it would be a better. but never tried .... |
| 18:19 | msalerno | FYI IPTables route between eth0 and wlan0: http://imx.solid-run.com/forums/viewtopic.php?f=8&t=1072&p=7915#p7915 |
| 21:11 | zuse | that's so clear. i build geexbox new from the snapshot from yesterday, and today there was a new snapshot :-) |
| 21:13 | zuse | but seen from the diff, i don't think it will fix my buggy wifi... 8-/ |