| 06:32 | Dacto | anyone using esata with the cubox-i? |
| 06:49 | jnettlet | Dacto, yes |
| 06:59 | jnettlet | tomlohave-away, recent xbmc builds seem to be broken. They are trying to use glxinfo to test for hardware acceleration on EGL systems. |
| 13:56 | matoking | Jon Nettleton created a repository for a newer 3.10.30 LTS kernel |
| 13:56 | matoking | Does anyone know whether it fixes the poor WiFi performance when I'm uploading files to my Cubox-i? |
| 13:56 | matoking | I'll probably compile the kernel anyway, but it would be nice to have a confirmation :) |
| 14:16 | aplund | matoking: I'm running that kernel on a i4pro, but haven't tested wifi |
| 14:16 | matoking | Hopefully it works just fine |
| 14:16 | matoking | I have no idea how long this 1 GB beast will take to compile |
| 14:17 | matoking | Provided a lot of it is probably irrelevant as long as compiling is concerned |
| 14:17 | matoking | But I don't like waiting :P |
| 14:17 | matoking | Well it isn't 1 GB after all |
| 14:17 | aplund | It seems to build unrelated device tree files |
| 14:17 | aplund | but they failed for me |
| 14:18 | aplund | so I had to patch it |
| 14:18 | matoking | I suppose I don't need to build any kernel modules? |
| 14:18 | aplund | matoking: well.. the defconfig that comes with it does build some modules |
| 14:19 | matoking | @aplund I mean the INSTALL_MOD_PATH= make modules_install part in the wiki |
| 14:19 | matoking | I got an endless list of Y/N prompts about modules I didn't know jack about, so I eventually just aborted it and dumped the uImage on my SD card |
| 14:20 | aplund | you can boot without modules |
| 14:20 | aplund | matoking: ahh, you are using a prebuilt binary |
| 14:20 | aplund | ? |
| 14:20 | matoking | Yes |
| 14:20 | aplund | i.c |
| 14:20 | matoking | I did try compiling some other kernel, but it broke my USB HDD from working |
| 14:21 | matoking | Got a lot of I/O errors and it failed to start pretty much every application it should have started |
| 14:21 | matoking | Hopefully this one will be a lot more easier :/ |
| 14:22 | matoking | I have installed newer kernel versions on my vanilla installation of Linux Mint and they have worked just fine, so I hope it's the same case here |
| 14:43 | matoking | Damn it failed |
| 14:47 | matoking | http://pastebin.com/MdsJp48c anyone know what I should do here? |
| 14:47 | matoking | I tried compiling the newer kernel at github.com/linux4kix/linux-linaro-stable-mx6 but it failed |
| 14:49 | tomlohave-away | matoking: same problem for wifi |
| 14:50 | matoking | @tomlohave-away With which kernel? |
| 14:51 | matoking | If you are using a prebuilt binary it's most likely 3.0.35-g0f2006c-dirty |
| 14:51 | tomlohave-away | 3.10 from jnettlet |
| 14:51 | matoking | Oh |
| 14:51 | matoking | I'm trying to compile a newer version of the kernel but as you can see I've hit a roadblock |
| 14:52 | jnettlet | matoking, is that my 3.10 kernel? |
| 14:52 | jnettlet | don't build a uImage, build a zImage |
| 14:52 | matoking | Oh yeah, it built that just fine |
| 14:52 | matoking | What do I do with it? |
| 14:52 | matoking | U-Boot seems to accept only an uImage file |
| 14:53 | jnettlet | you need to get a new version of U-boot. |
| 14:53 | tomlohave-away | you need to upgrade you uboot |
| 14:53 | matoking | The kernel I'm trying to build is this https://github.com/linux4kix/linux-linaro-stable-mx6/ |
| 14:53 | matoking | Oh snap |
| 14:53 | matoking | Better get to that then |
| 14:53 | tomlohave-away | I have a uboot ready if you want |
| 14:53 | jmontleon | jnettlet, I hit another issue with my build when I looked last night with fsl_spdif - seems they were not limited to the graphics driver. |
| 14:53 | jnettlet | hold on though. You probably need to revert a patch. We ran into some compatibility problems I haven't fixed yet. |
| 14:53 | jnettlet | jmontleon, I have fsl_spdif working fine. |
| 14:53 | jnettlet | and building fine |
| 14:54 | jnettlet | jmontleon, did you start with my cubox-i defconfig? |
| 14:54 | matoking | Okay, I'll try building the U-Boot, the newest version of which I'm assuming is at SolidRun/u-boot-imx6 |
| 14:54 | jnettlet | matoking, actually you need to revert a patch first |
| 14:55 | matoking | @jnettlet Something wrong with the kernel? |
| 14:55 | jnettlet | matoking, no with u-boot. I work on that also |
| 14:55 | jnettlet | matoking, git revert 2d0c4f544da73 |
| 14:55 | jmontleon | jnettlet, I'll give another run with an unaltered copy of your confg in a bit and see if it goes any better |
| 14:55 | matoking | @jnettlet Wouldn't it be better to revert that on the main branch |
| 14:55 | jnettlet | it fixes some early hardware, but breaks some later hardware. We are trying to come up with a better way to manage the errata |
| 14:56 | jnettlet | matoking, I don't have access to the main branch. |
| 14:56 | matoking | Assuming you have access to that repository, that is |
| 14:56 | matoking | Oh |
| 14:56 | jnettlet | and it does work with some hardware |
| 14:56 | jnettlet | I am hoping to come up with a proper patch for it sooner rather than later |
| 14:57 | matoking | I take it the wiki is still sparse on details about the new U-Boot? |
| 14:58 | matoking | Or is it just as easy as swapping uImage for zImage |
| 14:59 | tomlohave-away | matoking: just put zImage on boot, the same for dtb files |
| 14:59 | matoking | Ok, I'll give it a shot |
| 14:59 | jnettlet | matoking, with the latest patches I have made the new u-boot very easy to setup. |
| 14:59 | matoking | Just have to make sure I won't ruin my current installation if something goes wrong :P |
| 15:00 | jnettlet | just put zImage and .dtb into / or /boot of your first partition |
| 15:00 | matoking | Well I've currently made it so that uEnv.txt uses my USB HDD as the root filesystem |
| 15:01 | matoking | With the actual kernel file on the SD card |
| 15:01 | matoking | I don't think that would cause any problems |
| 15:01 | matoking | But if it does, it would be handy to know about it now :P |
| 15:02 | jnettlet | nope won't make a difference |
| 15:03 | matoking | Well the only problem I'm having is that I'm running out of disk space with all the stuff I'm compiling :P |
| 15:03 | matoking | Should've made the Linux partition larger now that I think of it |
| 15:16 | matoking | "Wrong Image Format for bootm command" |
| 15:16 | matoking | I copied the zImage to /boot |
| 15:17 | jnettlet | can you post all the output? |
| 15:17 | matoking | Well that probably means taking a picture of the screen :P |
| 15:17 | jnettlet | that is fine |
| 15:18 | matoking | I'll try one more thing first |
| 15:25 | matoking | @jnettlet http://i.imgur.com/dnE0zVt.jpg |
| 15:27 | jnettlet | matoking, ah you have an environment saved on the mmc card. |
| 15:27 | jnettlet | you will need to reset that so it uses the default. |
| 15:27 | matoking | Wait, what about the .dtb file? I didn't see it anywhere after building |
| 15:28 | jnettlet | oh you did make zImage? |
| 15:28 | matoking | Yes |
| 15:28 | jnettlet | what device is this? |
| 15:29 | matoking | What I'm building with? A 64-bit Linux Mint |
| 15:29 | jnettlet | the type of cubox-i you have? |
| 15:29 | matoking | And if you are talking about the microSD, it's the 4 GB one I got with Cubox-i |
| 15:29 | matoking | Cubox-i4Pro |
| 15:29 | jnettlet | okay so do make imx6q-cubox-i.dtb and then copy arch/arm/boot/dts/imx6q-cubox-i.dtb to your sdcard |
| 15:30 | jnettlet | then when you reboot hit esc to get to the u-boot prompt |
| 15:30 | jnettlet | do env default -a |
| 15:30 | jnettlet | and then saveenv |
| 15:30 | jnettlet | if you want to save your environment then do printenv and you will need to re-add that |
| 15:30 | matoking | Wait, I built the kernel with "make imx_v7_cubox-i_hummingboard_defconfig" |
| 15:31 | matoking | Should I have used a different config? |
| 15:31 | jnettlet | nope that is correct |
| 15:31 | jnettlet | with device-tree the kernel can work on many different hardware configs. The .dtb then tells the kernel the hardware configuration of this specific device. |
| 15:40 | matoking | I've done that but it still fails to boot |
| 15:40 | jnettlet | output please. |
| 15:42 | matoking | @jnettlet It's the same |
| 15:43 | matoking | Except it takes much, much longer for the PHY auto negotiation to timeout |
| 15:43 | matoking | So I suppose saving the environment succeeded |
| 15:43 | jnettlet | matoking, oh you have a uEnv.txt file that is setting things |
| 15:44 | matoking | @jnettlet I changed /boot/uImage to /boot/zImage and that's about it |
| 15:44 | jnettlet | please post the contents of that |
| 15:44 | jnettlet | you don't need that line any longer just let u-boot find the image |
| 15:45 | matoking | bootfile=/boot/zImage |
| 15:45 | matoking | mmcargs=setenv bootargs root=/dev/sda rootwait video=mxcfb0:dev=hdmi consoleblank=0 |
| 15:45 | matoking | So I just get rid of the bootfile line and that should be it? |
| 15:47 | matoking | Alright, it booted to Linux! |
| 15:49 | matoking | Oh wait, it probably just booted the old image |
| 15:52 | matoking | Okay it doesn't boot to the normal Xfde login screen |
| 15:52 | matoking | And it's inaccessible by SSH so wlan0 probably has to be reconfigured |
| 15:54 | matoking | Huh, the wlan0 interface disappeared entirely |
| 15:56 | matoking | And the entire filesystem is read-only for some reason |
| 15:57 | matoking | Yeah this didn't go as planned at all |
| 15:58 | jnettlet | add rw to your kernel commandline for write access |
| 15:58 | jnettlet | do you have the firmware available for you wireless driver? check your logs to make sure it was found and compatible. |
| 15:59 | jnettlet | If you are using an accelerated X driver you will probably need the newer gpu libraries and xorg driver. |
| 15:59 | matoking | Yeah |
| 16:00 | matoking | I'm trying to dump the boot output to the SD card |
| 16:00 | matoking | Success |
| 16:01 | matoking | http://pastebin.com/BSu5usx4 |
| 16:03 | jnettlet | matoking, looks like you built the wifi driver as a module. |
| 16:03 | jnettlet | check your config and set all BRCMxxx=m to BRCMxxx=y |
| 16:04 | matoking | @jnettlet Which config and where? |
| 16:04 | jnettlet | in your kernel directory. |
| 16:04 | jnettlet | the .config |
| 16:05 | matoking | It's /linux-linaro-stable-mx6/arch/arm/configs/imx_v7_cubox-i_hummingboard_defconfig? |
| 16:06 | matoking | I swear if I have to recompile the entire kernel again |
| 16:06 | jnettlet | nope you have already configured your kernel. Now to make changes you can edit the .config in the base of your kernel tree |
| 16:06 | jnettlet | you don't that is what I am telling you. |
| 16:06 | jnettlet | just make the change in the config and run make zImage again and it will just link in the code that changed |
| 16:10 | matoking | Why would the module be disabled in the first place? :/ |
| 16:10 | jnettlet | it isn't disabled, it is a module that you can load separately |
| 16:10 | jnettlet | not all the hardware has wifi cards |
| 16:13 | matoking | Yeah just expected it to work out-of-the-box :P |
| 16:14 | jnettlet | you are compiling a kernel, how out of the box do you want. If you want out of the box wait for a full image to be released. |
| 16:15 | matoking | Well I copied the new zImage over but the wlan0 interface still seems to be non-existent |
| 16:15 | matoking | Yep, it's still missing |
| 16:15 | jnettlet | is there firmware for it on the fs? |
| 16:16 | matoking | Well I'm still trying to get it to boot with write access |
| 16:16 | jnettlet | did you add rw to your kernel commandline? |
| 16:17 | mk01 | matoking: what is output of "ifconfig wlan0" ? |
| 16:17 | matoking | @mk01 I tried iwlist scan and the interface is not listed |
| 16:18 | matoking | @jnettlet And by kernel commandline do you mean the boot parameters |
| 16:18 | jnettlet | matoking, yes |
| 16:21 | matoking | "sda: unknown partition table" |
| 16:22 | matoking | Oh, and the HDMI output disappeared during the boot-up |
| 16:25 | jnettlet | matoking, it will blank and then come back after the hdmi driver is re-initialized |
| 16:25 | jnettlet | let me give you a compiled zIamge that has everything built in. |
| 16:27 | matoking | I'll try getting it to work |
| 16:28 | matoking | Having to pass a kernel parameter to have write access to the filesystem just seems silly, although I can't verify it because the picture still hasn't come up4 |
| 16:28 | jnettlet | but you can ssh into the box? |
| 16:29 | matoking | Nope, the wlan0 interface doesn't come up apparently |
| 16:29 | matoking | And I can't verify it because the signal disappears conveniently just when NetworkManager starts up |
| 16:31 | matoking | It also seems to take much longer for the HDD to be mounted |
| 16:31 | matoking | Or maybe it just means it gives up |
| 16:39 | matoking | I've reached an impasse |
| 16:39 | matoking | The signal never comes back up |
| 16:41 | matoking | @jnettlet Have you uploaded the zImage somewhere? |
| 16:42 | jnettlet | matoking, try this. https://dl.dropboxusercontent.com/u/736509/i4pro/zImage |
| 16:43 | matoking | @jnettlet Did you compile any kernel modules, eg. "make modules"? |
| 16:43 | matoking | I went with just make CUBOX_CONFIG and that was pretty much it |
| 16:43 | jnettlet | no |
| 16:43 | jnettlet | that is pretty much the default |
| 16:45 | matoking | Well it's about 300 KB larger than what I compiled |
| 16:46 | jnettlet | yes because I included the firmware binary blobs for the wifi and the sdma |
| 16:46 | matoking | Well look at that |
| 16:46 | matoking | HDD gets mounted immediately |
| 16:47 | matoking | Screen went blank again but I'll try SSH'ing in case it doesn't come up |
| 16:50 | matoking | Either it's taking its time to boot up or something went wrong, but I still can't SSH into it and the picture still hasn't come up |
| 16:53 | matoking | And from boot output it still doesn't seem to find the wlan0 interface |
| 16:55 | jnettlet | can you post the boot output? |
| 16:57 | matoking | Huh |
| 16:57 | matoking | If I remove the "rm" boot parameter and boot it with read-only file system the video signal doesn't disappear |
| 16:58 | matoking | I can post the output I get with read-only filesystem |
| 16:58 | matoking | For the boot output I get when I boot it with write access I'll have to record a video :P |
| 17:06 | matoking | Hmm, I'm using dmesg but it seems to omit some messages related to NetworkManager and such |
| 17:08 | jnettlet | did you add rm or rw? |
| 17:08 | matoking | @jnettlet This is what I got with http://pastebin.com/KeZP0RDA |
| 17:08 | matoking | @jnettlet If I add rw the screen goes blank during boot-up |
| 17:08 | matoking | @jnettlet If I don't, the signal doesn't disappear but the file system is read-only |
| 17:10 | matoking | Anyway, I haven't had to add the rw kernel parameter to have write access |
| 17:10 | matoking | with the prebuilt Debian image, why is that? |
| 17:11 | jnettlet | bah I forgot the wifi drivers. my bad. I will post another zImage |
| 17:12 | jnettlet | matoking, does it use systemd? |
| 17:13 | jnettlet | okay you can re-download at the same link |
| 17:13 | matoking | @jnettlet What uses systemd? :P |
| 17:13 | jnettlet | matoking, your debian image |
| 17:13 | jnettlet | as the init system |
| 17:14 | matoking | I have no idea |
| 17:14 | matoking | It's that prebuilt debian-jessie image that can be found in the wiki |
| 17:15 | jnettlet | get the new zImage and wifi will work, allthough it is very chatty in the logs |
| 17:17 | matoking | How chatty? |
| 17:17 | matoking | You suppose all the debug messages could cause slowdown? |
| 17:18 | jnettlet | not at all |
| 17:18 | matoking | Alright, the wlan0 interface is back in action it seems :D |
| 17:18 | jnettlet | the OSS driver is still a wip. more patches will come |
| 17:19 | matoking | Well I hope my troubles will incur at least some improvements :P |
| 17:20 | matoking | Awww yes |
| 17:20 | matoking | The signal disappeared but SSH works |
| 17:21 | jnettlet | matoking, do you have a keyboard hooked up to your cubox-i? it could just be the console is blanking |
| 17:22 | matoking | I have a keyboard |
| 17:22 | jnettlet | and if you hit spacebar nothing happens? |
| 17:23 | matoking | My TV comes up with a "No signal" message |
| 17:23 | jnettlet | from your ssh prompt run fbset |
| 17:23 | jnettlet | and check the resolution is supported for your tv |
| 17:24 | jnettle | 17:24 * jnettlet has to walk the dogs. bbl |
| 17:24 | matoking | Upload performance got worse |
| 17:25 | matoking | Starts at 1 MB/s but stutters down to 50 KB/s. If I have a SSH session going on at the same time it becomes very laggy |
| 17:26 | matoking | Better wait for the stable kernel, then |
| 18:49 | gwolf | o/ |
| 18:49 | gwol | 18:49 * gwolf gets ready to fire a question ;-) |
| 18:50 | gwolf | I'm trying to get a Debian-standard kernel to boot... But uboot does not seem to like it |
| 18:51 | gwolf | Now, the file type for my /boot/vmlinuz-3.12-1-armmp is quite odd... |
| 18:51 | gwolf | /boot/vmlinuz-3.12-1-armmp: floppy with old FAT filesystem, Media descriptor 0xfb |
| 22:35 | heap_ | he boys! |
| 22:35 | heap_ | hey* |
| 22:35 | heap_ | could anybody take a look on http://pastie.org/8813295 ? I started X on cuboxpro1 with arch and screen is blank |
| 22:44 | heap_ | + http://pastie.org/8813325 |