00:29 | heap_ | hi |
00:29 | heap_ | anybody alive? does anybody have any experience with cuboxi + esata + port multiplier? |
01:55 | heap_ | how is it with cuboxi4 esata multiplier? any spec for it? |
01:56 | heap_ | how many drives it supports? |
09:52 | danilo7 | hello everyone |
09:53 | danilo7 | I've bricked my cubox 1st gen (doesn't boot anymore, no red led)....the procedure to unbrick it is not online anymore...anyone could help me? |
10:18 | danilo7 | is there anybody in here? |
10:22 | vpeter | danilo7: When somene around with this knowledge I'm sure it will help you. You must be patiend - this is not 24/7 hotline :) |
10:23 | danilo7 | thanks for answering vpeter, I was wondering if this channel was just full of bots |
10:23 | danilo7 | I'll wait :( though I've been waiting already for weeks trying to contact Solidrun by email, forum, twitter, facebook ... |
10:27 | vpeter | danilo7: Doesn't they have some official channel for customers? |
10:28 | danilo7 | i dunno...i've tried all the other ways and had no answer...today I found this channel on the wiki |
10:28 | rabeeh | danilo7: hi |
10:29 | rabeeh | i'v saw the request about that |
10:29 | rabeeh | we got the files to download.solid-run.com/pub a while a go |
10:29 | danilo7 | oh thanks rabeeh |
10:29 | danilo7 | yea I've seen you restored the repo |
10:29 | Girhes | does anybody know where I could get some info about the developers of the cubox openelec port? |
10:29 | rabeeh | the wiki and forums are off since it we had an attack on our site that came from either those two |
10:30 | danilo7 | cause last time I tried to use the cubox installer (on my cubox 1st gen with Marvell Armada) |
10:30 | danilo7 | so there's no way I could get the unbricking procedure? :( |
10:30 | danilo7 | I've bricked it |
10:30 | danilo7 | and I don't remember how to unbrick it |
10:31 | vpeter | Girhes: #openelec |
10:31 | danilo7 | is it possible to have a pdf or something like that? |
10:32 | dz0ny | waybackmachine.com ? |
10:34 | Girhes | vpeter thanks. I need to know if they will ever support switching the screen to 3d mode automatically |
10:34 | vpeter | Girhes: I think you should ask this in #kodi. |
10:35 | vpeter | Because this function is inside Kodi software. |
10:38 | Girhes | I've already tried at the kodi forum. They said the raspberry port has patches for that functionality but they don't think it would be implemented for the cubox (although I don't know how much official this answer was.. :) |
10:39 | vpeter | Girhes: Then they are soc specific patches? Try asking this user fritsch in #openelec. |
10:40 | vpeter | Sometimes he is here also I think. |
10:42 | danilo7 | rabbeh: is it impossible to have a copy of the unbricking procedure before you sanitize your website? |
10:42 | dz0ny | danilo7: waybackmachine.com cmon |
10:44 | Girhes | vpeter I'm not sure how they implemented it and if it could be done on a cubox at all |
10:44 | Girhes | I checked a few debug logs and on the pi they send a HDMI mode change command to the display |
10:45 | Girhes | not sure however if it depends on the hardware |
10:45 | danilo7 | dz0ny: what is that?? |
10:45 | dz0ny | http://archive.org/web/ |
10:46 | dz0ny | you enter address an you could get site from year 2007 if you wish :) |
10:46 | dz0ny | they archive web sites |
10:47 | danilo7 | tried that (and also the google cache)....all I get is "Hrm. Wayback Machine doesn't have that page archived. Want to search for all archived pages under " |
10:47 | Girhes | nice find |
10:48 | Girhes | http://web.archive.org/web/20130406104445/http://www.solid-run.com/mw/index.php/Unbricking_CuBox |
10:48 | danilo7 | Girhes and dz0ny you are my heroes! |
10:49 | vpeter | Girhes: Can you show me the patches if you know where they are? |
10:51 | Girhes | vpeter: unfortunately I don't know, thats why I'm looking after the devs. I would be happy to try to port this since the menu on my tv is a mess and I don't have a separate 3d button to switch modes :) |
10:52 | Girhes | Or maybe I could make an addon that sends remote button presses to the tv to switch into 3d and back |
10:55 | danilo7 | thanks again guys! tonight I'll try to fix my device |
11:02 | S_Hennig | Hi everyone! Still fighting with a hummingboard that plays dead. Is there a way to read the fuse setting when the system does not boot? I fear that I might have received a SoM where the fuses are not burned. |
11:21 | Girhes | vpeter I just pulled the sources and found the difference. The magic is done in the call SetNativeResolution() in xbmc/windowing/egl - the raspberry and the imx driver use different ways to set the resolution. |
11:22 | vpeter | Girhes: This is not my area :) |
11:39 | heap_ | hi, anyone on this http://www.solid-run.com/community/post17661.html#p17661 ? |
12:02 | vpeter | I'm looking for a (micro) SD card reader which writes more than 10-15 MB/s with fast UHS cards. Any suggestions? I bought one USB 3.0 but speed is the same as with older 2.0 :( |
12:04 | Humpelstilzchen | heap_: seen this? http://www.solid-run.com/community/topic366-10.html |
12:19 | cbxbiker61 | vpeter, buy a kingston adapter, it works great |
12:50 | heap_ | Humpelstilzchen: yeah, but there is no clear answer to it ;-( |
12:56 | Humpelstilzchen | heap_: not? |
13:06 | heap_ | Humpelstilzchen: can you see it? they discuss different enclosure |
13:06 | heap_ | and CBS or FIS |
13:11 | heap_ | Humpelstilzchen: im just confused |
13:15 | rabeeh | CuBox is FIS based switching |
13:15 | rabeeh | CuBox-i is CBS |
13:23 | heap_ | rabeeh: thanks, but do i need to buy enclosure which support specific switching? |
13:23 | heap_ | the icycube enclosure has 4 bays, one esata port. If i connect cubox-i over this esata port, can i see all 4 drives separately>? |
13:24 | heap_ | is there any performance drawback? |
13:28 | vpeter | cbxbiker61: Any specific model? |
13:29 | vpeter | I just tested one other. It works great when reading - 40 MB/s. But writing is slow. |
13:50 | cbxbiker61 | vpeter, i have the simple model that looks like a fat usb stick it has a standard SD slot on one side and a micro on the other |
13:51 | cbxbiker61 | and it is fast for both read/write connected to usb3 |
13:52 | cbxbiker61 | my high-spec sandisk micro-sd's were testing above their rated speed |
13:53 | vpeter | Thanks. Will try to find a model from this description. |
13:53 | cbxbiker61 | yeah, a lot of shady vendors are really messing up usb3 by not using proper chips |
13:59 | vpeter | cbxbiker61: MobileLite G4 ? http://www.cameramemoryspeed.com/images/kingston-mobilelite-g4-card.jpg |
14:01 | cbxbiker61 | yes |
14:04 | heap_ | any on this CBS vs FIS? |
16:02 | MarcusVinter | jnettlet, did you get my message yesterday? |
16:14 | MarcusVinter | Does anyone know why flashing my custom u-boot image over the top of an existing working one will stop the kernel from loading? |
16:15 | MarcusVinter | I have a working image ready to go, but I have some customizations that I made in the u-boot source. i complied u-boot and I'm attempting to write the new u-boot over the top of the old one. seek=42 for the u-boot seek=1 for SPL. Can anyone help? |
16:18 | MarcusVinter | Here's a console output: http://pastebin.com/Cj0R0tsE |
16:28 | Artox | MarcusVinter, I dont see an error there |
16:32 | rabeeh | MarcusVinter: no error in that message |
16:33 | rabeeh | if the u-boot sizes are almost the same then there would be no issue replacing the older with newer |
16:33 | Artox | It shouldnt even matter if they were different, right? |
16:35 | rabeeh | nop; it shouldn't matter |
16:35 | rabeeh | but if the new u-boot is 5MByte then it would :) |
16:35 | Artox | true |
16:36 | MarcusVinter | Let me see, because I put a bigger image in for the splash screen, that could be the cause. |
16:37 | MarcusVinter | U-boot.img is 991K SPL is 31K |
16:38 | MarcusVinter | The original image was a pre-built one as far as I can remember. |
16:38 | MarcusVinter | Linaro |
16:38 | rabeeh | huge ! |
16:38 | rabeeh | original should be around 250KByte |
16:39 | MarcusVinter | we have a 1024x768 splash screen, that must be why. |
16:40 | MarcusVinter | yeah the image is 770k :P |
16:40 | MarcusVinter | as oppose to your 5.5K image. |
16:41 | MarcusVinter | the .bmp image that is. |
16:41 | MarcusVinter | solidrun.bmp |
16:41 | MarcusVinter | But the full image doesn't exceed 5MB :/ |
16:47 | MarcusVinter | Any ideas? |
16:48 | rabeeh | 5MB is only an example :) |
16:48 | rabeeh | i'm not sure you can really do 1024x768; i suggest to start with same image size and then moving it up |
16:48 | rabeeh | i'm pretty sure that you are overriding something there; maybe the environment variable or even first partition |
16:48 | MarcusVinter | I'll attempt it with the original solidrun.bmp, and see if that works. |
17:35 | MarcusVinter | Overwriting it using the original bmp seems to be working correctly. Our bigger u-boot must be overwriting something :/ |
17:35 | MarcusVinter | Is there any way to find how much space I have to use? Or is it more trial and error? |
17:48 | MarcusVinter | ls |
17:57 | MarcusVinter | If I'm looking in the right place, it looks like it is curently "bootm 10800000 12800000" |
18:28 | MarcusVinter | Anyone know the page size for the nand flash? |
18:28 | MarcusVinter | for the sd card* |
18:29 | MarcusVinter | I guess it depends, ill try find it :( |
18:45 | MarcusVinter | i was wondering if its possible to write the full image I backed up that is working at an offset, so that I can erase the SPL and u-boot and move the kernel address so that when I write the bigger u-boot and SPL there will be space without overwriting. |
18:56 | dz0ny | MarcusVinter: you should be able to change loadaddr load kernel there and change kernel magic boot location value correspond to that |
18:56 | dz0ny | imho you are overwriting uboot in memory with kernel |
18:57 | MarcusVinter | How can I find the kernel address? :P |
18:57 | dz0ny | cat .config | grep boot |
18:57 | dz0ny | cat .config | grep magic |
18:58 | dz0ny | you should spot it quickly :) |
18:58 | dz0ny | the problem is that kernel expects itself on specific address range and will scan for magic value in that space |
18:58 | dz0ny | if it can find it it wont boot |
18:59 | MarcusVinter | If I move the kernel further back, how would I find the new address? :( |
18:59 | dz0ny | its set during compile time in kernel :) |
19:00 | dz0ny | remebr its range not precise location :) |
19:01 | dz0ny | MarcusVinter: https://github.com/dz0ny/snappy-cubox-i/blob/master/snappy_defaults/boot/boot.scr#L20 this is what i did to load kernel from uImage |
19:01 | dz0ny | sorry zImage |
19:02 | dz0ny | backawards logic |
19:02 | MarcusVinter | How did you calculate the address initrd_addr=0x12800000? |
19:03 | dz0ny | random |
19:03 | dz0ny | well not random |
19:03 | dz0ny | just moved it further from anything else |
19:05 | MarcusVinter | So I could offset it when I write it by the address 0x12800000, and use 0x256000000>? |
19:06 | dz0ny | well you will still need to change kernel magic range thingy |
19:06 | MarcusVinter | Yeah, and the magic range will detect anything nearby the address? |
19:06 | dz0ny | can't you just squze that bmp under 1MB |
19:06 | dz0ny | kernel has special value |
19:07 | dz0ny | on boot it will scan taht range and boot itself |
19:07 | MarcusVinter | I don't know a better way to compress the 8-bit bmp :/ its 1024x768 in size. |
19:07 | dz0ny | so in short yes |
19:07 | MarcusVinter | and 770K. |
19:08 | dz0ny | MarcusVinter: make it smaller and upscale it programmatically ? :) |
19:09 | dz0ny | imho you will just create problems with moving around kernel in ram space |
19:09 | MarcusVinter | I can try :P |
19:09 | MarcusVinter | I'm not sure how. |
19:09 | MarcusVinter | I'll try figure it out though :P |
22:27 | heap_ | anyone using icycube? |
22:27 | heap_ | with cuboxi |