00:14 | mhoney | 14.04 please |
00:14 | mhoney | lets not waiste time with 12.04 |
00:16 | dv_ | yeah |
00:18 | shakesoda | I almost forgot that 14.04 was due |
00:49 | CuBox_i4 | the main thing is HDMI is only smallest resolution on this linero ubuntu from the wiki have to use [alt] f7 to see bottom of settings scteens in xchat |
00:50 | CuBox_i4 | screens* |
00:51 | CuBox_i | 00:51 * CuBox_i4 with mouse slide |
01:01 | Tenkawa | greetings all |
01:02 | Tenkawa | anyone made gpu patches for 3.14 yet? |
01:05 | dv_ | no, thats still far away |
01:05 | dv_ | everybody is still busy moving the GPU, VPU, IPU support to 3.10 |
01:10 | Tenkawa | dv_: bummer |
01:10 | dv_ | yeah, its a lot of work sifting through all of these patches |
01:10 | Tenkawa | would be nice to get some better transcoding speed |
01:19 | Tenkawa | havent gotten wireless card to show up in 3.14 yet either |
01:20 | Tenkawa | not quite sure why brcmfmac isnt working |
01:31 | Tenkawa | oh well |
01:31 | Tenkawa | bbl.. cheers all |
03:19 | DZII | Hello All |
03:19 | mk01 | hey |
03:22 | mhoney | hi |
03:22 | DZII | how do you get wifi wroking in Ubuntu? |
03:22 | DZII | working |
03:23 | mk01 | what cubox-i kernel you use ? |
03:23 | DZII | 3.0.35 |
03:24 | mk01 | there was wifi working out of the box, wasn't it ? |
03:24 | DZII | nope |
03:25 | mk01 | so "ifconfig wlan0" or "iwconfig wlan0" is not showing the device ? |
03:27 | DZII | for ifconfig - wlan0: error fetching interface information: Device not found |
03:28 | DZII | for iwconfig wlan0 - wlan0 No such device |
03:28 | mk01 | isn't maybe just firmware missing ? |
03:29 | mk01 | directory /lib/firmware/brcm |
03:29 | mk01 | and few files inside |
03:30 | DZII | what location is it should it be in |
03:31 | mk01 | directly under root as you see it |
03:31 | mk01 | so "ls -la /lib/firmware/brcm" should return bunch of files |
03:32 | DZII | no that was not there by default i did make a dr and put firmware in the dir but still same |
03:36 | mk01 | what firmware? where did you take it? |
03:37 | DZII | tried http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/tree/brcm |
03:38 | mk01 | yes, that is it |
03:38 | mk01 | but actually |
03:38 | mk01 | I miss .txt files there |
03:38 | mk01 | (which are mandatory) |
03:39 | gwolf | mk01: Sorry to jump in late here -- I can confirm that, using that kernel, and even without /lib/firmware/brcm even existing, wireless works (although the range is quite crappy) |
03:39 | gwolf | I use Debian, but made the install using that precise kernel |
03:41 | mk01 | gwolf: not late, just right. although us two proving "it just works" wont help DZII :) |
03:41 | gwolf | mk01: You are right, and I am tired, that's why I probably didn't add anything of value |
03:42 | gwolf | (...And I should apologize for it! :-| ) |
03:42 | mk01 | gwolf: no problem. |
03:42 | DZII | wel gwolf you even have images posted also i reid it still no wifi |
03:42 | DZII | tried |
03:42 | mk01 | DZII: can you upload your dmesg to pastebin or so ? |
03:42 | gwolf | DZII: Which model of CuBox-i do you have? |
03:42 | gwolf | IIRC only the 2 and 4 have wireless |
03:42 | DZII | CuBox-i4Pro |
03:43 | gwolf | I don't have the CuBox here with me, so I cannot really test (and I'm using a much different kernel)... But, can you do a <> and tell us what you have there? |
03:45 | gwolf | (that path gives me the right information even with 2.6.32 kernels, so should work for you) |
03:45 | DZII | http://pastebin.com/LKtzPPtn |
03:46 | gwolf | DZII: on the path I told you? |
03:47 | DZII | that just shows eth0 |
03:48 | gwolf | DZII: Your dmesg does show *something* about the card, at least -- Lines 287-291 are wireless-related (and appear just after bluetooth) |
03:48 | gwolf | hmh... And have you tried any other kernel? Any other distribution? |
03:48 | gwolf | Only eth0? (I guess it *does* have the local link, lo) |
03:49 | DZII | yes the prebuilt ubuntu stock as is and upgraded to 12.04 Debian and your image |
03:49 | mk01 | gwolf: nope, this is just part of cfg80211 subsystem |
03:49 | gwolf | And it also does not show using my image? :-| |
03:50 | gwolf | That means basically that... my ability to help is severely limited :-] |
03:50 | DZII | no this one is not yours |
03:50 | gwolf | But it did work with the other image? |
03:50 | DZII | no |
03:51 | mk01 | could it be that RFKILL switch is on ? I don't recall now if RFKILL will "hide" the card completely or just make it not work ... |
03:51 | gwolf | mk01: I doubt rfkill will survive a shutdown |
03:52 | gwolf | mk01: Besides, IIRC, when I call rfkill on my laptop, the interface still appears, but does not work |
03:52 | mk01 | gwolf: ok |
03:53 | mk01 | gwolf: indeed, just tested it |
03:53 | mk01 | it just does not work but remains visible |
03:54 | mk01 | this means my ability to help is severely limited now ;-) |
03:54 | mk01 | last guess |
03:54 | mk01 | SPL & uboot ? |
03:55 | gwolf | right, uboot can show network devices |
03:59 | CuBox_i4 | DZII here is ifconfig screenshot of linero ubuntu with wireless |
03:59 | CuBox_i4 | http://wiki.sugarlabs.org/go/File:Ifconfig.png |
04:05 | DZII | I have tried network manager and adding eth0 and wlan0 into interface file still nothing for me |
04:06 | gwolf | DZII: Of course :( Network Manager works some layers above. If the kernel does not see the interface, there is little to do |
04:07 | gwolf | ... And being the kernel really monolithic (modules cannot be loaded/unloaded, it's all compiled in), there |
04:07 | gwolf | is not much playground space |
04:12 | DZII | gwolf your headless image is nice but i could not get mono to install |
04:12 | gwolf | oh? why? |
04:13 | gwolf | (I mean... Why would you ever want to install mono? ;-) ) |
04:13 | DZII | for headless server i run a couple programs with mono |
04:14 | gwolf | right. What happened when you tried to install mono? It should just work(TM) |
04:15 | DZII | said it could not find something cant remember what it was now |
04:15 | gwolf | right :( Well... Anyway, it's time for me to go home... Finally |
04:15 | gwolf | :) |
04:15 | gwolf | Just a quick question for mk01 and the other regular dwellers of this channel... |
04:16 | gwolf | Are there binary images of a newer kernel available? I remember seeing something about a 3.10.x, but it needed me to setup&compile, and I'm too lazy (and my SD is too slow) |
04:16 | gwolf | (and I don't want to set up cross-compiling) |
04:17 | gwolf | I remember vorlon (@debian) said he was able to boot with a 3.13 kernel, but with many missing functionalities... |
04:17 | mk01 | gwolf: 3.10.30 is quite ok |
04:17 | gwolf | mk01: Do you have a link to get it from? :) |
04:18 | mk01 | only issue is DRIDRM not compatible with DRI2/3 so Vivante DRI driver is not working |
04:18 | gwolf | mk01: I want to set up my machine as a home NAS -- And I want to do it with btrfs. But the btrfs devs do insist on a kernel as recent as possible |
04:18 | mk01 | but accelerated FB 2D works ok |
04:18 | gwolf | mk01: I don't even have a HDMI monitor ;-) |
04:18 | mk01 | ok |
04:19 | mk01 | BTRFS is ok there, ... although I merged some P1 Jan patches |
04:19 | mk01 | and for Images ... don't want to tell bullshit. simply don't know |
04:20 | gwolf | ok :) I'll see what I do once I get home |
04:20 | mk01 | but can offer you with the .deb we use for XBian on cubox |
04:20 | gwolf | ...but I'm tired today, so it won't be today |
04:20 | gwolf | yes, that would be very nice! :D |
04:20 | mk01 | latest SPL & uboot.img included, as well as firmwares & working BT |
04:21 | mk01 | just to unpack & deploy manually - because .deb has some dependencies to XBian |
04:21 | gwolf | OK, I'll download and check it out |
04:21 | gwolf | perfect |
04:21 | mk01 | but I suppose this is no problem to you |
04:21 | gwolf | right :) Thanks! |
04:21 | mk01 | wait |
04:21 | mk01 | will post link |
04:21 | mk01 | http://xbian.brantje.com/pool/devel/main/x/xbian-package-kernel-6q/ |
04:22 | mk01 | http://xbian.brantje.com/pool/devel/main/x/xbian-package-kernel-6q/xbian-package-kernel-6q_1.3.8-13_armhf.deb |
04:22 | gwolf | Perfect! |
04:22 | gwolf | OK, tomorrow the CuBox-i comes to work, and I'll play with it. |
04:23 | mk01 | and don't be affraid of BTRFS, with the merged upstream I will soon migrate Cubox-i Xbian's back to BTRFS for all users |
04:23 | gwolf | Right. and have backups just in case ;-) |
04:23 | mk01 | I run 2x500MB raid0 for 3w with no single problem |
04:24 | mk01 | with powering off hard on daily basis |
04:24 | gwolf | Wow. Well, I got an external 1TB drive, *way* larger than my machine. Too expensive to get smaller+cheaper drives. |
04:24 | gwolf | s/cheaper/cheaper (on electricity)/ |
04:24 | gwolf | anyway, gotta go now. Thanks for the info! |
04:24 | mk01 | you are welcone |
04:24 | mk01 | welcome |
04:30 | satellit_e | Found this http://elinux.org/BeagleBoardUbuntu#Wi-Fi_Networking_.28command_line.29 |
04:30 | satellit_e | for ideas |
04:32 | mk01 | satellit_e: DZII is one step before that actually. until wlan0 get's recognised on system level, no config, tool, whatsoever will change the situation :-/ |
04:32 | CuBox_i4 | k |
06:43 | ralix | morning |
06:44 | cbxbiker61__ | morning |
09:56 | mk01 | guten morgen ... jnettlet are you present ? |
10:05 | jnettlet | mk01, yeah I am around |
10:05 | jnettlet | well for a little bit. |
10:14 | mk01 | jnettlet: just easy, thanks ... I pulled yesterday the DTS stuff. and lost HDMI output. |
10:15 | jnettlet | mk01, yeah, that is not ready for use. I am trying to fix that up this weekend. |
10:15 | mk01 | jnettlet: it is my mess or related ? |
10:15 | mk01 | jnettlet: no big deal, this info solved it, thanks |
10:16 | jnettlet | mk01, nope. Just revert it. I am trying to sort out the fbdev driver so it can use the same device-tree setup as the KMS driver |
10:16 | jnettlet | just revert the last patch for now. |
10:18 | mk01 | jnettlet: will do. yes. that's why I said that the info is enough. just wasn't sure as the build server triggered kernel rebuild and found Cubox "dead". |
10:18 | jnettlet | mk01, for anything stable you should use SolidRun's fork. |
10:19 | jnettlet | I will only send stable merge requests to rabeeh |
10:19 | mk01 | ah, there is one? you see, I'm a bit late with infos now. |
10:20 | jnettlet | yes I had rabeeh fork it for this reason. |
10:20 | jnettlet | https://github.com/SolidRun/linux-linaro-stable-mx6 |
10:22 | jnettle | 10:22 * jnettlet has to go now. |
10:22 | mk01 | nice weekend |
10:23 | jnettlet | ttyl |
10:27 | davorin | hmm..normal lately geexbox build won't run on cbi-1? |
10:28 | davorin | actually xbmc won't run as it can't find a display... |
11:20 | jnettlet | davorin, I will be testing geexbox this weekend. will take a look. I thought that was sorted out. |
11:35 | davorin | hmm...and my i4p is dead again...blank screen |
11:37 | davorin | glad i tested it before shipping to customer (o; |
11:37 | davorin | someone already tested the hb2? |
11:37 | davorin | works with current arch distro? |
11:38 | jnettlet | davorin, I think rabeeh is the only one that has worked on the hb2 so far. |
11:41 | davorin | ah okay...i will just try several distros then and see whta happens... |
11:41 | davori | 11:41 * davorin is curious about the soldered msata port... |
11:43 | davorin | guess i need to stick a heatsink on the usom-i4 first before trying on the hb2 |
11:47 | jnettlet | davorin, as far as I know rabeeh is not support the i4's on the HB platform. |
11:55 | davorin | hmm..he didn't mention anything... |
11:55 | davorin | have only the usom-i2 and usom-i4p to test... |
11:57 | jnettlet | I think it is mostly due to heat problems. The CBi's are a more controlled environment. |
11:58 | jnettlet | there is no reason it shouldn't work, just don't be shocked if it hits thermal limits. |
11:58 | davorin | ah that he mentioned... |
11:58 | davorin | he doesn't know yet how to solve the problem (o; |
11:59 | davorin | is the cpu temp accessible via filesystem? |
12:05 | jnettlet | davorin, yeah it is exposed under the /sys filesystem |
12:32 | davorin | hmm...cat /sys/devices/virtual/thermal/thermal_zone0/temp |
12:33 | davorin | 41950 |
12:33 | davorin | seems it changed a little |
12:33 | davorin | before it just returned an integer reflecting the real temperature |
13:07 | jnettlet | davorin, yes that was actually incorrect for the kernel. It is supposed to exposed via millidegrees celsius |
13:07 | jnettlet | so 41.9 degrees |
13:08 | davorin | wow...millidegrees... ;-) |
17:38 | ths1 | Hello, i received cubox-i4 two month ago and i'm not able to use because there is many problem with DVI screen. I don't know what to do, is there anyone can help us? We would be disappointed to have to sell ... |
17:40 | ths1 | we hoped to use with debian |
17:40 | ths1 | like a desktop computer |
17:41 | jnettlet | ths1, I am working on DVI patches right now. Hang in there. |
17:46 | davorin | is there anything you don't work on? ;-) |
17:47 | jnettlet | I only work on things that are broken. Yesterday I wrote a patch for the ElementaryOS gala window manager because the way they transitioned between workspaces was annoying me :-P |
17:48 | davorin | you know anything regarding cec support? |
17:49 | jnettlet | I have patches that fix CEC in my queue |
17:49 | jnettlet | although it is more of a workaround. There are some serious problems in the libcec that need to be addressed. |
17:49 | davorin | hate to use a mouse in my living room (o; |
17:50 | jnettlet | your universal remote isn't good enough? |
17:50 | davorin | wanna use my tv's remote for that |
17:50 | ths1 | jnettlet: thank, how many time you think ? |
17:51 | davorin | two weeks....what was the name of the movie? |
17:51 | jnettlet | ths1, if nothing explodes I will be releasing a new kernel by the end of the weekend that should have support fo rit |
17:51 | jnettlet | The Money Pit |
17:51 | jnettlet | Tom Hanks and Shelley Long |
17:52 | davorin | right ;-) |
17:52 | davorin | hmm...wasn't aware i.mx6 can do 2160p |
17:53 | davorin | "The Ampe A10 is powered by a 1.2 GHz quad-core Freescale i.MX6 processor. That�s an ARM Cortex-A9 chip with 1MB of L2 cache, and Vivante GC2000 graphics with support for 3D hardware acceleration and 2160p HD video playback." |
17:54 | ths1 | jnettlet: cool !!! how to find tutorial to learn how install it ? |
17:55 | jnettlet | ths1, check the forums. I am pretty sure there is documentation on using the 3.10.30 kernel there. Unfortunately I am relying on others to do the documentation |
17:55 | jnettlet | davorin, I can't remember if it is hdmi or lvds that can do that resolution. I do remember one can, the other can't |
17:56 | davorin | will find out.... |
17:56 | davorin | said 4k monitors are out of stock atm |
17:56 | davorin | just got a 2560x1600 today for my win7 machine for doing pcbs |
17:57 | davorin | and hb2 has both on board to test... |
17:57 | davorin | though i assume there is no code yet in submarine for lvds support |
17:59 | jnettlet | davorin, it should just need the device-tree entries. the LVDS channel works for both my and upstream KMS kernels. It has been tested on the Novena boards |
17:59 | davorin | ah great... |
18:00 | davori | 18:00 * davorin needs to search where he put his lvds display... |
18:00 | davorin | though regular, cheap tvs have also lvds panels inside...like haier tv from china |
18:01 | jnettlet | yep. Most LCD's/Plasma up until a year ago were LVDS. Now they are slowly switching to eDP |
18:07 | davorin | ah the Dell U2414QM is on stock |
18:14 | davorin | hard to find a 2160p movie which is not pr0n on giganews (o; |
18:52 | davorin | ah..adobe media encoder supports 2160p and higher |
19:20 | DZII | Hello All |
19:20 | coin3d | hi |
22:32 | coin3d | rabeeh: is it possible to make the cubox-i wifi interface listen to channel 12 and 13? |
22:33 | coin3d | i've set up the german region code, iw list shows the wifi device and channel 12 and 13 possible, but when i scan for my wifi network, it doesnt show up |
22:33 | coin3d | i've plugged in a usb wifi stick now which works on channel 13 |
22:42 | cbxbiker61__ | coin3d, i don't have my cubox-i's yet, check your log to see if it's trying to use an external wireless regulatory domain... |
22:43 | cbxbiker61__ | it probably should be, since the same hardware is being used world-wide, and then you have to set your location appropriately |