| 00:04 | chron0 | _rmk_: I think it's the kernel, I've compiled https://github.com/SolidRun/linux-imx6 now and it booted perfectly |
| 00:05 | chron0 | however 3.0 isn't really sweet :) |
| 04:28 | Dacto | anyone using esata and getting failed commadn: 'WRITE DMA EXT'? |
| 06:44 | Fishscene | Greetings. I assume this is a channel for solidrun cubox? |
| 06:45 | Fishscene | If So, I received my cubox in the mail today, and I've plugged in a keyboard, but pressing a key does not let me halt the boot process. |
| 06:46 | Fishscene | I've tried 2 different USB keyboards, in USB slots 1 and 2, but there's no indication the USB keyboards are being initialized at boot time. |
| 07:00 | jnettlet | Fishscene, is it a wireless keyboard? |
| 07:00 | Fishscene | Both are bog-standard wired USB keyboards. |
| 07:00 | jnettlet | you need to use the second port down |
| 07:00 | Fishscene | One is a Dell keyboard, the other a full-sized Apple keyboard. I've tried both the first and the second ports for both keyboards. |
| 07:01 | jnettlet | It is also possible you have an older version of u-boot and need to upgrade it. |
| 07:02 | Fishscene | How do I upgrade it? The information I've found on the wiki is slightly confusing. (sorry for asking for a bit of hand-holding here..) |
| 07:05 | jnettlet | what distro do you plan on running on it? |
| 07:05 | Fishscene | Let's go with GeeXboX for now. I eventually plan on running IPfire, but wanted to check out the media capabilities first. |
| 07:05 | Fishscene | If I can get GeeXboX on it, I'm sure I can get IPFire on it :) |
| 07:05 | Fishscene | I'm using: http://www.solid-run.com/mw/index.php/Flashing_U-Boot |
| 07:06 | jnettlet | Fishscene, just grab the nightly Geexbox builds. They have the latest u-boot included in them. |
| 07:07 | jnettlet | The forums have a lot of the answers you are looking for. http://imx.solid-run.com/forums/viewtopic.php?f=7&t=335 |
| 07:07 | DHowett | Are the cubox-i power adapters compatible with the original cubox/pro adapters? 5.5mm/2.1mm, center positive, 5v? |
| 07:08 | jnettlet | it depends on the model you are running and the amps |
| 07:09 | DHowett | hm |
| 07:09 | jnettlet | sorry I can't remember what the original cubox-i power adapter ships with. I have way too many little power bricks plugged in around me |
| 07:09 | DHowett | I'm thinking about putting together a battery backup for the cubox pro, but couldn't find specs on its power requiremenets. Then again, I could go upstairs and look at the adapter |
| 07:09 | DHowett | In fact, that would be smarter than having had bothered you ;P |
| 07:09 | DHowett | (thanks!) |
| 07:43 | Fishscene | huh. Followed that forum post you linked jnettlet: Everything went well until I plugged power in. No display output at all. Reverting.. |
| 07:43 | jnettlet | Fishscene, which model do you have? |
| 07:44 | Fishscene | Model: l4P-300-D. If I recall, it was the top-tier cubox |
| 07:44 | Fishscene | cubox pro* |
| 07:45 | jnettlet | cubox or cubox-i? |
| 07:45 | jnettlet | there is a big difference |
| 07:46 | jnettlet | oh l4p-300-d...cubox-i |
| 07:46 | jnettlet | when getting support make sure to be clear about that. |
| 07:46 | Fishscene | CuBox-i4Pro. Sorry about not mentioning that earlier. :S |
| 07:47 | jnettlet | do you have a spare USB -> microUSB cable around? You can plug that in to the bottom microusb port and get a terminal |
| 07:47 | jnettlet | there is a bug in the u-boot hdmi code such that it won't sync with some monitors that are very strict about their timings |
| 07:47 | Fishscene | Yes. I have that connected already, although I've been having trouble getting putty to recognize anything at all. I'm working on that right now. |
| 07:48 | jnettlet | Fishscene, 115200 8n1 and make sure hardware flow control is disabled |
| 07:48 | Fishscene | I don't even know if I just have to have the unit on, or if I have to be in the BIOS, or what, there's no information on what conditions are needed to talk over the serial connection to it. |
| 07:49 | jnettlet | you just turn it on. U-boot loads the serial driver and enables a console on the port |
| 07:50 | jnettlet | but here are the debugging rules. If the side light on the spdif turns on but the front LED doesn't illuminate that means that the box can't load u-boot from your SD card. |
| 07:50 | jnettlet | if the front-light comes on u-boot has loaded and you should get a serial console. |
| 07:51 | jnettlet | hdmi may or may not work at this point. |
| 07:51 | Fishscene | Gotchya. I'm working on getting it up and running, standby... |
| 08:11 | Fishscene | test |
| 08:12 | jnettlet | got it |
| 08:14 | Fishscene | Sorry, I was disconnected I guess for a bit. Ok so, I'm following the instructions to the letter here: http://www.solid-run.com/mw/index.php?title=Unbricking_CuBox (Windows portion). Current status: SPDIF light is on, no front light. I'm on step 3. The file never transfers. The transfer box just disappears after a little bit, no messages ever show up on the console. |
| 08:15 | Fishscene | I can feel that I'm pressing down on the boot-select push button, so I don't think that's the problem.. |
| 08:15 | jnettlet | yes, that is the wrong document. Like I said you have a Cubox-i not a Cubox |
| 08:16 | jnettlet | completely different systems |
| 08:17 | jnettlet | the firmware for the Cubox-i is completely contained on the SDHC card which gets flashed when you transfer most of the images to the sdhc card with either dd or winImage |
| 08:26 | Fishscene | bbl. My computer is acting weird. Need to reboot |
| 08:46 | Fishscene | Well, I'm at a complete standstill. My USB cardreader died. Thank you for your assistance though. I *should* be able to handle things from here on out. |
| 08:47 | Fishscene | I suspect the image writer somehow attempted to write to the cardreader firmware (I didn't know that was even possible), so I essentially bricked my cardreader :( |
| 10:38 | _rmk_ | jnettlet: seems like it would be a good idea to put on the cubox wiki pages something which says "Not for the Cubox-i series" |
| 10:39 | jnettlet | _rmk_, we definitely need a better method of distinction |
| 10:40 | _rmk_ | lots of people seem to try that "unbricking" page with their cubox-i's |
| 10:41 | jnettlet | luckily it doesn't do anything bad |
| 13:24 | matoking | I think someone here mentioned a week or so ago that there's a bug in kernel which has an effect on Wi-Fi upload speeds |
| 13:24 | matoking | Has the problem already been fixed in the github.com/SolidRun/linux-imx6 repository? |
| 13:27 | matoking | The kernel I'm currently using is what debian-jessi comes with, which according to uname -r is 3.0.35-g0f2006c-dirty |
| 14:07 | rabeeh | dv_: HB is not being sold |
| 14:07 | rabeeh | it's in rev 2.0 status and production will be rev 2.1 |
| 14:23 | matoking | Hmmm |
| 14:23 | matoking | I compiled the latest kernel in SolidRun's repository and it seemingly stopped my HDD that was plugged in via USB from working |
| 14:24 | matoking | Got plenty of I/O errors |
| 14:24 | matoking | Either that or I misunderstood somethg |
| 14:39 | LangeOortjes | I am using the tiny installer image which boots to the message "Please press enter to active this console. " However, there for me everything stops. No matter what button I press, the console won't activate. Am I missing something? |
| 15:02 | LangeOortjes | Works via serial console though, using that instead :) |
| 15:02 | LangeOortjes | who needs a monitor anyway |
| 15:12 | xraxor | what HW are you using ? |
| 15:16 | matoking | Is there a good reason to update the kernel? |
| 15:16 | matoking | I compiled the newest kernel in SolidRun's repository but I got a lot of I/O errors in /dev/sda which is the USB HDD I have plugged in and working as the root filesystem |
| 15:17 | matoking | It failed to boot and I couldn't SSH into it |
| 15:17 | matoking | I replaced the uImage in the SD card, but was there something else I might've needed to do |
| 15:17 | matoking | ? |
| 17:01 | whitepyro | hmm |
| 20:17 | jmontleon | _rmk_, I am getting the mmc errors in 3.14 again trying to boot the i4pro. Does the MX6QDL_PAD_KEY_ROW1_SD2_VSELECT 0x1f071 line need to be added in somewhere? Looks like the file layout has changed substantially so not sure where if so |
| 20:18 | jmontleon | mmc1: -110 whilst initializing card. |
| 20:19 | _rmk_ | it's in there |
| 20:19 | _rmk_ | pinctrl_cubox_i_usdhc2_aux: cubox-i-usdhc2-aux { |
| 20:19 | _rmk_ | fsl,pins = < |
| 20:19 | _rmk_ | MX6QDL_PAD_GPIO_4__GPIO1_IO04 0x1f071 |
| 20:19 | _rmk_ | MX6QDL_PAD_KEY_ROW1__SD2_VSELECT 0x1b071 |
| 20:19 | _rmk_ | >; |
| 20:19 | _rmk_ | }; |
| 20:20 | _rmk_ | oh. |
| 20:21 | _rmk_ | jmontleon: best comment out the support for UHS-1 |
| 20:21 | _rmk_ | in arch/arm/boot/dts/imx6qdl-cubox-i.dtsi, find the &usdhc2 { |
| 20:22 | _rmk_ | and add in there: "no-1-8-v;" |
| 20:23 | jmontleon | ah, right. I remember now. I don't know what I was just looking at. I see the MX6QDL_PAD_KEY_ROW1__SD2_VSELECT line too |
| 20:23 | jmontleon | thanks |
| 20:25 | _rmk | 20:25 * _rmk_ still thinks 3.14 should be called something like M.PI |
| 20:26 | jmontleon | I'm sold, but then I don't have much weight in that conversation :) |
| 21:27 | crypt0s | So how do I get the GPU driver installed on Cubox-i? |
| 21:27 | crypt0s | as in: which one do I download and from where? |
| 21:28 | crypt0s | I got confused looking it up online if I was supposed to get some blob from freescale or not |
| 21:32 | xraxor | crypt0s |
| 21:32 | xraxor | what distro? |
| 21:47 | crypt0s | xraxor: Gentoo |
| 21:47 | crypt0s | xraxor: I compiled the kernel from 3.13.1 using the config from the ubuntu prebuilt from solidrun |
| 23:08 | crypt0s | the DDOS is causing hella netsplits :P |
| 23:09 | crypt0s | Anyone on-chan know how to set up the Video Acceleration? |
| 23:28 | crypt0s | OK so I at least know now that I need to somehow get the vivante kernel module |