| 00:07:55 | jhMikeS | Ummm...did android actually reconfigure? That one makes no sense. |
| 00:15:58 | __builtin | jhMikeS: Seems like a fluke to me. |
| 00:16:32 | pamaury | jhMikeS: are you sure you got the conditional right? |
| 00:18:05 | jhMikeS | it was the same warning all around. if I got it wrong nothing should build clean. |
| 00:27:26 | | Quit pamaury (Ping timeout: 248 seconds) |
| 00:28:53 | | Quit petur (Remote host closed the connection) |
| 00:32:39 | | Quit ender` (Quit: When you try to teach them to fish, they become upset, because you are very clearly communicating to them that you will not be handing them a fish every day.) |
| 00:53:33 | | Quit lebellium_ (Quit: Leaving) |
| 01:00 |
| 01:10:42 | | Join robertd1 [0] (~root@186-88-142-98.genericrev.cantv.net) |
| 01:17:34 | *** | Saving seen data "./dancer.seen" |
| 01:32:30 | | Quit munch (Changing host) |
| 01:32:30 | | Join munch [0] (pls@unaffiliated/munch) |
| 01:32:30 | | Quit munch (Changing host) |
| 01:32:30 | | Join munch [0] (pls@gateway/shell/elitebnc/x-ggvvzubfwpanibgx) |
| 02:00 |
| 02:23:26 | | Quit dys (Ping timeout: 240 seconds) |
| 02:26:09 | | Quit ZincAlloy (Quit: Leaving.) |
| 03:00 |
| 03:10:16 | jhMikeS | Bilgus: pictureflow is crashing in get_context_map. I'm thinking likely b10c0e5? |
| 03:17:36 | *** | Saving seen data "./dancer.seen" |
| 03:19:45 | | Quit _meg (Ping timeout: 260 seconds) |
| 03:20:37 | | Join _meg [0] (~notsure@211.25.203.45) |
| 04:00 |
| 04:28:09 | fs-bluebot_ | Build Server message: New build round started. Revision 8be4074, 273 builds, 13 clients. |
| 04:31:48 | | Join duo8 [0] (~ZNC-SRV-H@117.1.168.40) |
| 04:43:21 | fs-bluebot_ | Build Server message: Build round completed after 911 seconds. |
| 04:43:22 | fs-bluebot_ | Build Server message: Revision 8be4074 result: 1 errors 0 warnings |
| 05:00 |
| 05:17:39 | *** | Saving seen data "./dancer.seen" |
| 05:18:05 | | Join tico-tico [0] (05651a63@gateway/web/freenode/ip.5.101.26.99) |
| 05:19:51 | tico-tico | Hi, everybody. For some time Clip+ bootloader won't compile with error "[ERR] Packed data (134492 bytes) doesn't fit in the firmware (134136 bytes)". Is that something known? Sansa Clip+ v1 - Firmware version: 01.02.18, arm-elf-eabi-gcc (GCC) 4.4.4. |
| 05:36:13 | jhMikeS | yes, it's known and there was (is?) someone addressing that. |
| 05:39:03 | tico-tico | thanks for info, jhMikeS. |
| 05:48:11 | | Quit tico-tico (Quit: Page closed) |
| 05:57:10 | fs-bluebot_ | Build Server message: New build round started. Revision 6ee3b6f, 273 builds, 13 clients. |
| 06:00 |
| 06:07:44 | | Quit tchan (Quit: WeeChat 1.6) |
| 06:07:55 | | Quit TheSeven (Ping timeout: 255 seconds) |
| 06:09:31 | fs-bluebot_ | Build Server message: Build round completed after 741 seconds. |
| 06:09:32 | fs-bluebot_ | Build Server message: Revision 6ee3b6f result: All green |
| 06:38:05 | | Quit krabador (Ping timeout: 260 seconds) |
| 06:38:08 | | Join krabador_ [0] (~krabador@unaffiliated/krabador) |
| 06:43:56 | | Quit krabador_ (Quit: Leaving) |
| 07:00 |
| 07:00:16 | | Quit JanC (Remote host closed the connection) |
| 07:00:42 | | Join JanC [0] (~janc@lugwv/member/JanC) |
| 07:05:23 | | Quit JanC (Ping timeout: 246 seconds) |
| 07:09:08 | | Join JanC [0] (~janc@lugwv/member/JanC) |
| 07:11:36 | | Join tchan [0] (~tchan@lunar-linux/developer/tchan) |
| 07:11:37 | | Quit MrBismuth (Read error: Connection reset by peer) |
| 07:12:41 | | Join MrBismuth [0] (~ArcMrBism@2602:306:8325:a300:1426:998c:b44b:81fb) |
| 07:17:42 | *** | Saving seen data "./dancer.seen" |
| 07:32:26 | | Quit CrashBash-Kun (Ping timeout: 240 seconds) |
| 09:00 |
| 09:17:43 | *** | Saving seen data "./dancer.seen" |
| 09:30:47 | | Join dys [0] (~dys@tmo-108-55.customers.d1-online.com) |
| 09:32:26 | | Join TheSeven [0] (~quassel@rockbox/developer/TheSeven) |
| 10:00 |
| 10:20:38 | | Join ender` [0] (krneki@foo.eternallybored.org) |
| 10:23:11 | | Join JannF [0] (~jann@HSI-KBW-046-005-019-085.hsi8.kabel-badenwuerttemberg.de) |
| 10:29:09 | | Join amofiuhr_ [0] (~amofiuhr_@ip150-155-64-186.ct.co.cr) |
| 10:31:50 | | Join lebellium [0] (~hexchat@89-93-177-206.hfc.dyn.abo.bbox.fr) |
| 10:33:19 | | Quit jhMikeS (Ping timeout: 268 seconds) |
| 10:36:05 | amofiuhr_ | I recently updated to lubuntu 17:10 and tried running Rockbox Utility. I got garbled text (see here: https://imgur.com/a/AlJhm ). anyone know what the problem might be? |
| 10:40:40 | | Join jhMikeS [0] (~jethead71@d192-24-173-177.try.wideopenwest.com) |
| 10:45:18 | | Quit jhMikeS (Ping timeout: 255 seconds) |
| 11:00 |
| 11:17:44 | *** | Saving seen data "./dancer.seen" |
| 11:18:18 | | Quit amofiuhr_ (*.net *.split) |
| 11:31:54 | | Quit JannF (Ping timeout: 268 seconds) |
| 11:33:27 | | Join pamaury [0] (~pamaury@rockbox/developer/pamaury) |
| 11:55:23 | | Join PurlingNayuki [0] (~Thunderbi@2001:da8:215:4ff:650a:70d9:e947:701b) |
| 12:00 |
| 12:01:52 | | Quit PurlingNayuki (Ping timeout: 250 seconds) |
| 12:02:00 | | Join PurlingNayuki1 [0] (~Thunderbi@2001:da8:215:4ff:477:a40c:1009:3300) |
| 12:04:22 | | Nick PurlingNayuki1 is now known as PurlingNayuki (~Thunderbi@2001:da8:215:4ff:477:a40c:1009:3300) |
| 12:16:03 | | Join Bilgus_ph [0] (41ba23be@gateway/web/freenode/ip.65.186.35.190) |
| 12:25:08 | Bilgus_ph | Jhmikes it is possible maybe a pointer issue, there really isn`t much going on there... |
| 12:48:18 | | Quit Bilgus_ph (Ping timeout: 260 seconds) |
| 13:00 |
| 13:02:26 | | Join b0hoon [0] (05acea1d@gateway/web/freenode/ip.5.172.234.29) |
| 13:17:46 | *** | Saving seen data "./dancer.seen" |
| 13:18:40 | | Part hicks_ ("http://quassel-irc.org - Chat comfortably. Anywhere.") |
| 13:19:18 | | Join ZincAlloy [0] (~Adium@2a02:8108:8b80:1700:fcf7:8534:8ae4:49b8) |
| 13:19:56 | | Quit copper (Quit: ZNC - http://znc.in) |
| 13:20:41 | | Join copper [0] (~copper@unaffiliated/copper) |
| 13:56:25 | | Quit ZincAlloy (Quit: Leaving.) |
| 13:56:35 | | Join ZincAlloy [0] (~Adium@2a02:8108:8b80:1700:fcf7:8534:8ae4:49b8) |
| 14:00 |
| 14:09:24 | | Quit ZincAlloy (Quit: Leaving.) |
| 14:09:34 | | Join ZincAlloy [0] (~Adium@2a02:8108:8b80:1700:fcf7:8534:8ae4:49b8) |
| 14:25:48 | | Quit dys (Ping timeout: 255 seconds) |
| 14:33:11 | | Join robertd11 [0] (~root@186-90-60-46.genericrev.cantv.net) |
| 14:36:25 | | Quit robertd1 (Ping timeout: 260 seconds) |
| 15:00 |
| 15:10:36 | | Join chrivers [0] (~chrivers@home.houseofawesome.dk) |
| 15:11:33 | chrivers | evening folks. I just used RockboxInstaller to put newest stable rockbox on my SansaFuzeV2. It had been running the previous stable for a long time without any trouble. |
| 15:12:01 | chrivers | After flash, it offered to reboot, which I accepted. At this point, it seemed to hang, so I let it sit for a little while |
| 15:12:32 | chrivers | When it finally rebooted, I got "ATA error: -2" |
| 15:12:39 | chrivers | (and "Press ON to debug") |
| 15:12:48 | chrivers | drives do not present over USB |
| 15:13:29 | chrivers | I've powered the device off, and followed the guide to do recovery |
| 15:14:06 | chrivers | the battery (+)-pin is desoldered, and I've bridged the recovery jumper pads with solder |
| 15:14:19 | chrivers | but even so, I still get ATA error -2 |
| 15:15:05 | chrivers | I can just make out "Loading Rockbox 3.14" (or however it says it), so it's definitely loading rockbox 3.14 at least a few percent |
| 15:15:12 | chrivers | which makes it all the more strange |
| 15:15:17 | chrivers | Ideas? :) |
| 15:17:38 | chrivers | correction, it says "Boot Ver. 4.0" for a few jiffies, then "Ver. 3.14", both at the bottom of the screen |
| 15:17:50 | *** | Saving seen data "./dancer.seen" |
| 15:25:33 | | Quit _meg (Ping timeout: 240 seconds) |
| 15:26:21 | | Join _meg [0] (~notsure@211.25.203.45) |
| 15:43:59 | | Join ernestask [0] (~ernestask@78-56-62-157.static.zebra.lt) |
| 15:49:10 | pamaury | chrivers: maybe Bilgus can help you, he has worked a lot on sansas recently |
| 15:54:01 | | Join jhMikeS [0] (~jethead71@d192-24-173-177.try.wideopenwest.com) |
| 15:54:01 | chrivers | thx |
| 15:54:21 | chrivers | Bilgus: If you have time and ideas, I'm all ears |
| 15:54:51 | chrivers | does the rockbox bootloader (Ver. 4.0) react to any key presses? Is there any way to interrupt the normal boot? |
| 16:00 |
| 16:01:35 | pamaury | chrivers: generally speaking the only way to interrupt normal boot is a) press a special key to boot the original firmware, b) plug USB to enable bootloader usb mode (I don't know if this enabled on the fuze v2) |
| 16:09:12 | chrivers | it seems boot-to-orig is enabled with "hold left on boot" from rockbox bootldr |
| 16:09:19 | chrivers | (according to rb manual) |
| 16:09:29 | chrivers | but this is stated to only work with the battery |
| 16:10:11 | chrivers | and I'm a bit careful about soldering back and forth too many times |
| 16:14:09 | chrivers | I can't even get it register as a proper USB device.. it's really strange |
| 16:15:33 | chrivers | waaaaaat... I let it idle in the "Debug GPIO" screen for a while, fiddled with the buttons, and then it suddenly said "Scanning disk".. something is up |
| 16:26:27 | chrivers | "PANIC" mount: 0 pc 30051318 sp: 300D5E58 |
| 16:26:43 | chrivers | (followed by "bt end", which I assume means end of backtrace) |
| 16:33:20 | chrivers | and at one point I got it to say "Error reading playlist", as well as "Installation complete"... however, it's still bricky :-/ |
| 16:34:33 | chrivers | and I notice that GPIOD seems to be flapping wildly. some of the high bits seem pretty random, even when I don't touch anything. Is this expected? Or is it just static noise on a floating gate? |
| 16:37:01 | | Quit _meg (Ping timeout: 255 seconds) |
| 16:40:15 | | Join _meg [0] (~notsure@211.25.203.45) |
| 17:00 |
| 17:08:36 | | Quit jhMikeS (Read error: Connection reset by peer) |
| 17:09:06 | | Join jhMikeS [0] (~jethead71@d192-24-173-177.try.wideopenwest.com) |
| 17:15:03 | | Join Guest56968 [0] (~ac@75-239-190-109.dsl.ovh.fr) |
| 17:15:17 | Guest56968 | I screwed up |
| 17:16:19 | Guest56968 | I wanted to install a new version of rockbox, I probably pulled the plug without dismouting the device, and now I can't reinstall nor deinstall rockbox |
| 17:16:41 | Guest56968 | I can still mount/dismount the device though |
| 17:17:51 | *** | Saving seen data "./dancer.seen" |
| 17:23:54 | Guest56968 | http://g01.rhizogen.es/~ac/bugs/rockbox/rockbox_log_install_3.14_fail.log |
| 17:26:03 | Guest56968 | maybe if I try to delete all files by hand and then reinstall on top of that ? |
| 17:35:33 | pamaury | Guest56968: you should at least mention which device you have |
| 17:36:01 | Guest56968 | pamaury: of course. sansa fuze v2 |
| 17:37:08 | pamaury | if you pulled the plug with dismounting, maybe you should first run fsck on the drive, to make sure there are no errors |
| 17:52:53 | | Part b0hoon |
| 18:00 |
| 18:09:19 | | Quit duo8 (Ping timeout: 248 seconds) |
| 18:10:23 | | Join duo8 [0] (~ZNC-SRV-H@117.7.213.232) |
| 18:15:14 | chrivers | Guest56968: wait, sansa fuze v2? I just flashed that today, and my device bricked.. I can't even mount the drives though :-/ |
| 18:15:47 | * | chrivers wonders if maybe Sansa Fuze v2 firmware is b0rked |
| 18:21:37 | Guest56968 | pamaury, chrivers : I ran fsck and it found some errors, I've now reinstalled v3.14 successfully |
| 18:21:45 | Guest56968 | I'll try to install the dev version again |
| 18:22:11 | Guest56968 | seems to work |
| 18:24:31 | pamaury | chrivers: yours sound more like a bad flash, a very common problem on sansa devices |
| 18:32:59 | Bilgus | I'm pretty sure johnb has fuzev2 he has been testing with probably just coincidence.. chrivers are you on linux? |
| 18:34:29 | Bilgus | Guest569968 you might want to put the multiboot bootloader on there while the going is good |
| 18:34:32 | chrivers | Bilgus: I am, yes |
| 18:34:55 | Guest56968 | Bilgus: multiboot bootloader ? |
| 18:34:58 | Bilgus | on the forum under unsupported builds I have some pre-compiled |
| 18:35:01 | chrivers | Bilgus: are you here a bit later? dinner is ready here :) |
| 18:35:14 | Bilgus | yeah I'll be around chrivers |
| 18:35:28 | chrivers | Bilgus: awesome, talk later |
| 18:36:46 | Bilgus | you'll want to follw the directions for your device, you don't need the firmware for now but just the bootloader |
| 18:37:13 | Bilgus | unless ofc you want to run your install from the sd card to save the internal flash from wear |
| 18:37:58 | Guest56968 | does that mean there's a bootloader that allows you to have multiple instances of rockbox on your device ? nice :) |
| 18:38:27 | Guest56968 | idk if I would make use of it but I like the idea |
| 18:44:14 | Bilgus | it does but its more for when your flash goes readonly |
| 18:44:33 | Bilgus | or you know to prolong its life |
| 18:45:20 | Guest56968 | hum ok |
| 18:45:26 | Guest56968 | has it already happened ? |
| 18:45:47 | Guest56968 | that someone keeps his DAP long enough for the NAND to wear out ? |
| 18:46:43 | pamaury | Guest56968: sure, plenty of sansa fuze/clip/clip+ have died because of that |
| 19:00 |
| 19:17:54 | *** | Saving seen data "./dancer.seen" |
| 19:18:27 | Guest56968 | I would have thought that the battery would wear out before the NAND does |
| 19:20:00 | pamaury | Guest56968: it does but people change batteries ;) |
| 19:21:06 | pamaury | and Sansa's flash is exceptionally bad it seems |
| 19:25:12 | | Join amofiuhr_ [0] (~amofiuhr_@ip150-155-64-186.ct.co.cr) |
| 19:30:25 | Guest56968 | pamaury: can you change the battery of a sansa ? |
| 19:31:44 | pamaury | Guest56968: yes, it involves a little of soldering I think but nothing hard, also the devices are relatively easy to disassemble |
| 19:33:34 | Guest56968 | pamaury: ok thanks for the info |
| 19:34:35 | [Saint] | Reassembly on the other hand... |
| 19:34:50 | [Saint] | Looking at you, FuzeV2 wheel ribbon. |
| 19:35:36 | [Saint] | You need to be an expert at Operation for that one. |
| 19:39:03 | | Join CrashBash-Kun [0] (~CrashBash@unaffiliated/crashbash-kun) |
| 19:40:01 | | Join dys [0] (~dys@tmo-113-120.customers.d1-online.com) |
| 19:53:27 | Guest56968 | :P |
| 19:58:39 | chrivers | Bilgus: I'm back.. still there? :) |
| 20:00 |
| 20:00:08 | Bilgus | yep |
| 20:00:47 | [Saint] | Bilgus is furniture now. He couldn't leave if he wanted to. |
| 20:00:57 | [Saint] | The trick is making him think it's his idea. |
| 20:01:05 | Bilgus | so run me through this you used the rb utility to install 3.14 and now you recieved ATA error? what version were you running before? |
| 20:01:43 | Bilgus | I think Charlton Heston died like 10 years ago.. |
| 20:02:23 | chrivers | correct, I used newest rb utility to install 3.14, and I used 3.13 before that |
| 20:03:36 | Bilgus | well it could very well be that your device doesn't like the voltage scaling I can't remember if it was enabled on FUZE V2 brb |
| 20:08:20 | Bilgus | chrivers can are you seeing errors in the bootloader or is it only after it loads the firmware |
| 20:09:26 | chrivers | it says "Boot Ver. 4.0" for a few jiffies, then "Ver. 3.14", both at the bottom of the screen, and then "ATA error" |
| 20:10:35 | chrivers | I'm getting ready to connect it back up to the computer now |
| 20:10:43 | chrivers | Bilgus: any ideas for recovery methods? |
| 20:10:48 | Bilgus | ok well that does point towards the firmware and AFAICT voltage scling wasn't enabled in 3.13 so it is probably an issue of the voltage being too low, now you said something about not having the battery connected |
| 20:11:09 | chrivers | oh, not having the battery connected was way later in the debugging process |
| 20:11:47 | Bilgus | ah ok I was going to say it could part of the problem causing voltage droop |
| 20:11:56 | chrivers | I tried following the recovery method in the wiki, which calls for disconnecting the battery, and putting a solder bridge on some pads |
| 20:12:22 | [Saint] | We need to hide that better. |
| 20:12:26 | Bilgus | I don't think you need recovery if you are seeing the loading screen your bootloader is fine |
| 20:12:40 | chrivers | [Saint]: please, hide it less :D |
| 20:12:53 | [Saint] | The disclaimer makes it kinda clear that it's not something Joe User should even consider. |
| 20:12:53 | chrivers | Bilgus: alright, then I'm all ears on ideas for recovery. so far, nothing works |
| 20:13:00 | Bilgus | what I need you to try is turn off the device and hold the 'up?' button while plugging usb |
| 20:13:04 | [Saint] | Most users make it worse assuming they need to do that. |
| 20:13:09 | [Saint] | Most often they don't. |
| 20:13:30 | Bilgus | It might also be the select button I'm not overly familar with the fuzev2 |
| 20:13:46 | chrivers | I'm pretty sure I've tried every button so far, but hang on, I'll try again :) |
| 20:13:52 | chrivers | the pdf manual calls for holding Left |
| 20:13:54 | Bilgus | basically we are looking for it to say Firmware not found plug USB |
| 20:13:57 | chrivers | (which also does nothing) |
| 20:14:11 | Bilgus | let me look in the source brb |
| 20:14:16 | chrivers | sure, thx |
| 20:14:23 | chrivers | I'll put the thing together meanwhile |
| 20:14:46 | Bilgus | or if you can get into the OF |
| 20:15:38 | Bilgus | [Saint] it says contact us what more can we do? |
| 20:17:19 | [Saint] | While that is a fair argument....end users man. |
| 20:17:21 | Bilgus | chrivers it should be hold select button while plugging usb |
| 20:20:20 | | Join this_is_a_nick [0] (~amofiuhr_@ip150-155-64-186.ct.co.cr) |
| 20:20:20 | | Quit amofiuhr_ (Read error: Connection reset by peer) |
| 20:22:17 | chrivers | [Saint]: Should I feel included in the "end users" group..? |
| 20:24:13 | Bilgus | chrivers are you able to get into the OF? or is it failing as well? |
| 20:24:28 | chrivers | trying as we speak, just a sec :) |
| 20:25:18 | chrivers | so, battery disconnected. holding Select. plugging in USB. No difference |
| 20:25:29 | chrivers | Same with Menu (the little button in the corner) |
| 20:25:53 | chrivers | Would this only work with the battery connected? |
| 20:26:11 | Bilgus | maybe? the OF is a pretty unforgiving bitch |
| 20:26:32 | chrivers | it doesn't try to boot the oF |
| 20:26:36 | chrivers | as far as I can tell |
| 20:26:46 | chrivers | and nothing registered on usb |
| 20:27:44 | Bilgus | http://forums.rockbox.org/index.php/topic,52058.0.html |
| 20:28:02 | Bilgus | ok grab the build for your device in that post.. |
| 20:28:10 | Bilgus | put it on a sdcard |
| 20:28:35 | chrivers | sure, sec |
| 20:28:53 | chrivers | and thanks for taking the time to help :) |
| 20:29:06 | Bilgus | next grab a decent usb power brick like 1.0 A or better and plug the device in to that instead |
| 20:29:25 | chrivers | right, going to get that |
| 20:35:21 | chrivers | ok, I have the fuzev2 .rockbox dir in the root of partition 1, on an sdcard with a standard msdos partition table, fat32 on the partition |
| 20:35:46 | chrivers | the sd card is synced and in the fuze, and I have a 2.1A power source (no data connection). Should I just power it up? |
| 20:37:51 | Bilgus | yes |
| 20:38:28 | chrivers | Same result: Boot Ver. 4.0 -> Ver 3.14 -> ATA error |
| 20:38:33 | Bilgus | whta we are going to try to do is boot then in the sdcard run that other version of rockbox.sansa |
| 20:39:42 | Bilgus | well hmm if we can't get into either the OF, USB or OF we might have to do the recovery method |
| 20:39:55 | Bilgus | sorry OF, USB or RB |
| 20:40:23 | chrivers | Alright, and that's by jumpering the pins between the 0402 smds? |
| 20:40:34 | chrivers | at least they feel that freaking small.. :D |
| 20:41:27 | Bilgus | yeah have a look on the pics and make sure 10x you have the right ones and are looking at the proper picture |
| 20:41:32 | chrivers | sure |
| 20:41:35 | chrivers | I was preparing it earlier |
| 20:41:45 | chrivers | and it's definitely the right board |
| 20:41:45 | Bilgus | you really don't need a solder jumper |
| 20:42:22 | Bilgus | a small screwdriver works better because after it boots it needs to not be shorted anymore |
| 20:42:55 | chrivers | but it's ok if it is shorted while booted? |
| 20:44:16 | Bilgus | basically it makes the device freak out when the flash is not accessible and it loads a special mode with usb and then we unshort it and access the flash again |
| 20:44:30 | chrivers | ah, right |
| 20:44:35 | chrivers | I'll get on it :) |
| 20:49:51 | chrivers | so the idea is to short it while it's booting, and that should interrupt normal boot? |
| 20:51:21 | Bilgus | you will hold it shorted while you plug usb you will hear the usb connect on your pc and then unshort it |
| 20:51:40 | chrivers | I'll try some more times |
| 20:51:45 | chrivers | no luck the first 4 times |
| 20:52:19 | Bilgus | its a bit finicky but be doubly sure you are shorting the right place |
| 20:53:09 | Bilgus | it could also be coated with conformal coating I suppose but I doubt it so you might try scraping at it |
| 20:54:09 | chrivers | I'm sure I'm hitting the right place, but so far I've tried like 6 times with no change |
| 20:55:19 | Bilgus | several things to try.. different port on pc, different cable, different pc |
| 20:55:40 | chrivers | proprietary cable :( |
| 20:55:52 | chrivers | tried a bunch of different usb ports |
| 20:56:00 | chrivers | I'll try a different pc |
| 20:56:32 | Bilgus | hold on did you ever connect the battery back? |
| 20:56:49 | chrivers | nope, still hanging |
| 20:56:52 | chrivers | I can do that |
| 20:57:07 | chrivers | powers on fine over just usb, seemingly |
| 20:57:12 | Bilgus | yeah Ive always had the battery connected |
| 20:57:15 | chrivers | but I can understand if that makes it do Weird |
| 20:57:21 | chrivers | alright, I'll try that |
| 20:58:08 | Bilgus | If we can't get into 'recovery mode' I'd say its got hardware issues |
| 21:00 |
| 21:01:13 | chrivers | here's what I don't understand - isn't the "ATA error" a message from rockbox/ |
| 21:01:14 | chrivers | ? |
| 21:01:36 | chrivers | battery is connected again |
| 21:03:20 | Bilgus | it just means it wasn't able to read/write the flash |
| 21:03:41 | Bilgus | like it tries 50x and if it errors out it panics |
| 21:04:14 | chrivers | so at least it was able to load the part of the code that says that.. and shouldn't that part be able to recover, somehow? |
| 21:04:58 | Bilgus | as for why it could be the flash has gone bad, voltage is too low (flash is getting old).. it could also be a purely mechanical issue |
| 21:05:28 | Bilgus | well in theory yes since you have the bootloader we should be able to get into it and change the code |
| 21:05:45 | chrivers | it's certainly not a completely new player any more, but it did happen during/right after the upgrade from 3.13 to 3.14, so a hardware issue is not my prime suspect |
| 21:05:46 | Bilgus | but if you can't get into usb mode how can we do that |
| 21:06:13 | Bilgus | could you try holding select and plugging usb again now that the battery is connected |
| 21:06:22 | chrivers | sure thing |
| 21:06:35 | Bilgus | its much easier to do things from within rockbox than in raw mode |
| 21:07:39 | Bilgus | also try Of again now the battery is connected |
| 21:08:58 | chrivers | well hello there.. holding Up while booting (and holding for a while) eventually goes to a grey screen that says "Installation complete"! |
| 21:09:05 | | Join CrashBash-Kun_ [0] (~CrashBash@unaffiliated/crashbash-kun) |
| 21:09:24 | Bilgus | great |
| 21:09:30 | chrivers | toggle wheel doesn't work |
| 21:09:43 | | Quit CrashBash-Kun_ (Client Quit) |
| 21:09:45 | chrivers | but the home button at least wakes it |
| 21:09:49 | chrivers | I'll check if usb is on |
| 21:10:11 | Bilgus | so you want to start rockbox.sansa from the sd card |
| 21:10:23 | chrivers | Manufacturer: Rockbox.org / SerialNumber: 3A8B651490CF10D0C00000000 |
| 21:10:30 | chrivers | so USB is not toast |
| 21:10:36 | chrivers | but then 3-9.2: can't set config #1, error -110 |
| 21:10:40 | chrivers | maybe a voltage problem |
| 21:10:49 | Bilgus | It most assuredly is |
| 21:10:53 | chrivers | hang on, I'll get my in-line usb power meter |
| 21:11:06 | Bilgus | the build I gave you has higher defaults |
| 21:11:20 | Bilgus | you need to get that onto the device |
| 21:11:26 | chrivers | any ideas for how? |
| 21:11:56 | Bilgus | if you keep pressing a button does it work properly |
| 21:11:59 | Bilgus | ?? |
| 21:12:03 | jhMikeS | Bilgus: it's something like that. it's the ldr instruction that faults. |
| 21:12:40 | Bilgus | jhMikeS i'll try it on my fuze+ and see if I can replicate its kinda odd though |
| 21:13:28 | jhMikeS | Exact behavior depends on target. Goes from doing nothing, to crash to lockup depending. |
| 21:13:43 | chrivers | Bilgus: not every time.. it booted into kind-of-sort-of working firmware |
| 21:13:53 | chrivers | but the jog wheel and select button was dead |
| 21:14:03 | chrivers | and usb wouldn't configure with the host |
| 21:14:25 | Bilgus | that sounds very odd chrivers is this OF or rockbox? |
| 21:14:34 | chrivers | Bilgus: rockbox |
| 21:14:40 | chrivers | vanilla stable 3.14 |
| 21:14:46 | chrivers | from today |
| 21:15:10 | chrivers | installed with rbutil, as per official instructions. it ought to be 100% by the book |
| 21:15:27 | fs-bluebot_ | Build Server message: New build round started. Revision cd3ea08, 273 builds, 14 clients. |
| 21:15:43 | Bilgus | so wait no select button, you can even browse menus then? |
| 21:16:37 | chrivers | Bilgus: if you mean "can't even", then yes. I literally can't even |
| 21:17:08 | chrivers | Maybe-losing my fuze is almost worth it, just to make that pun |
| 21:17:56 | *** | Saving seen data "./dancer.seen" |
| 21:18:21 | Bilgus | did you install a new bootloader as well? |
| 21:18:40 | chrivers | not today no |
| 21:18:49 | chrivers | the utility said it's only required the first time |
| 21:19:24 | Bilgus | ok theen the bootloader should be able to start the OF |
| 21:19:57 | Bilgus | or pick up the select button to enable usb mode if not its a hardware issue |
| 21:19:57 | | Join petur [0] (~petur@rockbox/developer/petur) |
| 21:20:12 | chrivers | ok, so 1) hold pwr for 15 seconds to force pwr off 2) disconnect USB 3) power up while holding Up for ~ 10 seconds <−− this seems to boot into the half-dead firmware mode |
| 21:20:41 | | Quit ernestask (Quit: ernestask) |
| 21:20:52 | chrivers | bus voltage is holding at 4.82V |
| 21:20:55 | chrivers | 100ma |
| 21:22:06 | Bilgus | its Left button to boot OF for your device |
| 21:22:28 | chrivers | on the second attempt, rockbox connects two disks ("Internal Storage" and "SD Card Slot") over USB |
| 21:22:33 | chrivers | no more usb but errors |
| 21:22:52 | chrivers | but neither of these 2 virtual disks are present |
| 21:23:11 | chrivers | in the same sense as an empty flash card reader |
| 21:23:45 | chrivers | I can select different "USB Keypad Modes" using the Menu button |
| 21:23:55 | chrivers | Multimedia, Presentation, etc |
| 21:24:04 | | Quit atsampson (Quit: kernel) |
| 21:24:07 | chrivers | can I get into mass storage mode from here? |
| 21:24:56 | Bilgus | type sudo fdisk -l |
| 21:24:56 | chrivers | disconnecting USB gave another panic - pc 30051318, sp 300D5E58 |
| 21:25:00 | chrivers | that's actually the same as before |
| 21:25:23 | chrivers | Bilgus: they're readable |
| 21:25:31 | chrivers | *not readable :-/ |
| 21:25:50 | Bilgus | whats the actual message? |
| 21:26:18 | chrivers | sudo file -Ls /dev/sdf: /dev/sdf: writable, no read permission |
| 21:26:18 | fs-bluebot_ | Build Server message: Build round completed after 650 seconds. |
| 21:26:19 | fs-bluebot_ | Build Server message: Revision cd3ea08 result: 5 errors 0 warnings |
| 21:26:28 | chrivers | (same for /dev/sde) |
| 21:26:38 | chrivers | "writable" is a red herring, btw |
| 21:27:04 | Bilgus | no read permission thats an odd one sure sounds like a corrupted partition |
| 21:27:49 | Bilgus | ok lets back track and try 'recovery mode' again |
| 21:28:02 | chrivers | not exactly, it's the "Media not present" state from the SCSI layer |
| 21:28:25 | chrivers | it's the same behaviour as a usb flash card reader, when there's no flash cards in it |
| 21:28:42 | chrivers | so it just means the fuze isn't offering access to the partition |
| 21:29:16 | chrivers | sure, what should I try? |
| 21:29:17 | jhMikeS | weird, no build logs are visible on the last one |
| 21:29:29 | Bilgus | shorting the pins while plugging usb |
| 21:29:46 | chrivers | sure, I can try again |
| 21:29:56 | chrivers | Can you tell me what I'm looking for? |
| 21:29:58 | Bilgus | jhmikes I tried pictureflow on my fuze+ and no issue at all I'll try the clipzip next |
| 21:30:18 | Bilgus | we need the device to connect remove the sd card first |
| 21:30:30 | Bilgus | then it should connect on usb plug |
| 21:30:43 | Bilgus | no disk though it'll be a RAW device |
| 21:30:53 | jhMikeS | and c200-v2 actually does build fine, so....more build farm glitches |
| 21:30:59 | Bilgus | fdisk should give you a message about no valid partition |
| 21:31:16 | Bilgus | probably still on sdf |
| 21:31:31 | Bilgus | then we will continue from there |
| 21:34:38 | Bilgus | JhMikeS no issue on the clipzip or clip+ could you try passing NULL to get_custom_action? |
| 21:36:17 | Bilgus | maybe its related to #ifndef USE_CORE_PREVNEXT |
| 21:36:58 | jhMikeS | I checked clip-v1 and gigabeast so far (no action on the former, bad things on the latter) |
| 21:38:50 | Bilgus | https://github.com/Rockbox/rockbox/blob/365a0050384692b9b308de2d83b7d951e63d567c/apps/plugins/pictureflow/pictureflow.c#L753 |
| 21:39:22 | Bilgus | could you change that to return NULL; and see it it stops crashing? |
| 21:40:15 | chrivers | Bilgus: I tried a bunch more times, it doesn't seem to have any effect what so ever |
| 21:40:26 | chrivers | I'm sometimes getting this from the kernel: 3-9.2: Device not responding to setup address. |
| 21:40:34 | chrivers | as well as usb 3-9.2: can't set config #1, error -110 |
| 21:41:12 | Bilgus | chrivers the recovery mode bypasses rockbox and the OF it is literally the processor its self |
| 21:41:31 | Bilgus | if you can't connect there either Its the hardware |
| 21:41:41 | chrivers | holy dingus |
| 21:41:44 | chrivers | finally |
| 21:41:46 | chrivers | 12 tries |
| 21:41:50 | chrivers | got connection to /dev/sde |
| 21:42:15 | jhMikeS | Bilgus: sure |
| 21:42:18 | | Join atsampson [0] (~ats@cartman.offog.org) |
| 21:42:43 | Bilgus | chrivers ok fdisk -l say no valid partition then? |
| 21:42:49 | Bilgus | sudo.. |
| 21:42:51 | chrivers | I mounted it and everything |
| 21:42:57 | chrivers | doing a backup now, for good measure |
| 21:43:56 | jhMikeS | Bilgus: will this kill all keys because the problem only happens when selecting an album to browse |
| 21:45:21 | chrivers | Bilgus: so now I have access to the internal storage for the device. what's a good move from here/ |
| 21:45:32 | chrivers | I feel like an fsck would be a fine idea for starters |
| 21:45:35 | chrivers | just to make sure |
| 21:45:58 | jhMikeS | Bilgus: I guess it does. Now I can't do anything. :\ |
| 21:49:28 | Bilgus | chrivers yes and I was going to say do a back up first |
| 21:50:08 | Bilgus | no be very careful you can wipe out the whole device in this mode normally the first 8 mb or so is hidden from you |
| 21:50:13 | Bilgus | NOW* |
| 21:50:28 | chrivers | sure |
| 21:54:18 | | Join lebellium_xz1c [0] (~AndChat51@89-93-177-206.hfc.dyn.abo.bbox.fr) |
| 21:54:23 | | Quit lebellium_xz1c (Client Quit) |
| 21:55:12 | chrivers | Bilgus: could/should I just unzip the beta fuzev2 firmware on top of the existing .rockbox in internal storage? |
| 21:55:42 | chrivers | it's running fs check now, seems fine so far |
| 21:55:58 | Bilgus | oh did it actually give you a workable drive? |
| 21:56:02 | chrivers | oh yes |
| 21:56:05 | Bilgus | Color me amazed |
| 21:56:06 | chrivers | after 12 tries :) |
| 21:56:38 | chrivers | I was surprised too |
| 21:56:41 | Bilgus | yeah you should be able to do that but just in case rename it and copy the new one to the drive |
| 21:56:44 | chrivers | I was ready to salvage it for components |
| 21:58:15 | Bilgus | as in rename the current one .rockbox.old |
| 21:58:59 | chrivers | roger |
| 22:00 |
| 22:05:48 | Bilgus | JHmikeS I think I see the issue |
| 22:28:43 | | Join JannF [0] (~jann@HSI-KBW-046-005-019-085.hsi8.kabel-badenwuerttemberg.de) |
| 22:35:57 | | Quit JannF (Ping timeout: 248 seconds) |
| 22:48:33 | [Saint] | chrivers: you have a FuzeV2 yeah? |
| 22:48:39 | chrivers | bilgus: just wanted to give you a post mortem |
| 22:48:45 | chrivers | [Saint]: yeah |
| 22:48:54 | [Saint] | I wasn't joking with my remark about the wheel ribbon. Perhaps you didn't see it. |
| 22:49:09 | [Saint] | You need to be a qualified brain surgeon to get that back in right. |
| 22:49:14 | chrivers | [Saint]: I did.. and I know it's a real piece of work |
| 22:49:39 | chrivers | the first 5 times or so went ok, but it seems it gained a hairline fracture in 2 places, from the repeated movement |
| 22:49:55 | Bilgus | :/ |
| 22:49:56 | [Saint] | I guess I should add a note to the wiki to say *AT ALL COSTS TRY NOT TO DISCONNECT THIS*. |
| 22:50:00 | chrivers | so while I actually have a bootable fuze now after hw recovery (thanks bilgus!), I also have a dead fuze |
| 22:50:21 | chrivers | [Saint]: reconnecting it wasn't a problem for me |
| 22:50:33 | chrivers | it wasn't easy, but I made it work |
| 22:50:50 | chrivers | but having this tiny flex cable move even slightly, will make it crack internally |
| 22:51:16 | Bilgus | If its a double ended ribbon you could replace it if not it is possible to solder new ones on |
| 22:51:18 | [Saint] | The fragile nature is one problem, the placement another entirely. |
| 22:51:33 | chrivers | Bilgus: I'm considering it |
| 22:51:43 | [Saint] | I would guess yours doesn't actually have a crack causing the issue. It's almost definitely misaligned. |
| 22:51:44 | chrivers | Bilgus: I took the jog wheel apart. it's certainly possible |
| 22:52:00 | chrivers | but it's something like 16 wires in the span of 10mm |
| 22:52:13 | chrivers | I'm not sure my time and sanity is that cheap |
| 22:52:28 | [Saint] | The tolerances between "works fine" and "masquerades as hardware issues" are incredibly small. |
| 22:52:29 | chrivers | [Saint]: it's absolutely certainly a crack, I can see it |
| 22:52:41 | Bilgus | might be worth it to buy a brick for parts |
| 22:53:58 | [Saint] | Oh, I'm not saying it's not cracked as well. That's usually going to show up as intermittent or outright failure though. |
| 22:54:13 | Bilgus | if the crack is far enough towards the end you can sometimes cut them off and attach to a splint |
| 22:54:37 | Bilgus | basically remake the plug end |
| 22:54:58 | chrivers | Bilgus: I thought about it, but the contacts pads are 2-row molded into the end, so it's not possible |
| 22:55:22 | Bilgus | that sucks −− sorry to hear it |
| 22:55:48 | chrivers | yeah, it's a bit of a downer... wasted the best part of a sunday too |
| 22:55:53 | chrivers | but thanks a lot for the help; |
| 22:55:56 | chrivers | i appreciate it |
| 22:56:05 | [Saint] | With conversations like this as reference it night be more clear to some why I call these things Happy Meal toys. |
| 22:56:08 | chrivers | btw, the firmware you linked to boots up perfectly |
| 22:56:15 | [Saint] | They're basically disposable. |
| 22:56:42 | chrivers | which means, that *possibly* the 3.14 stable fw for fuzev2 is going to brick between 0 and 100% of users |
| 22:56:49 | [Saint] | I don't regard then as a high enough quality player to risk my sanity over. |
| 22:56:58 | [Saint] | I reserve that for early generation iPods. |
| 22:57:22 | [Saint] | iPod Mini...looking at you, buddy. |
| 22:57:34 | [Saint] | Fucking ribbons made of porcelain and prayers. |
| 22:57:49 | [Saint] | Look at them wrong and they fracture. |
| 22:58:48 | [Saint] | chrivers: to be fair that should always be regarded as true. |
| 22:59:10 | chrivers | [Saint]: I think you know what I mean |
| 22:59:15 | [Saint] | It's not known if we've encountered every single possible hardware variant combination |
| 22:59:25 | [Saint] | No guarantees are ever given. |
| 22:59:29 | chrivers | if not, let me rephrase: |
| 23:00 |
| 23:00:21 | chrivers | I'm trying to offer the information, that perhaps the newest stable (3.14) for fuzev2 bricks people's players |
| 23:01:05 | [Saint] | Yes. And I'm saying that should always be regarded as true with devices with no dedicated recovery method. |
| 23:01:12 | [Saint] | Such as these. |
| 23:01:55 | [Saint] | There's a tiny subset of devices where we can say as long as the software doesn't do actual physical damage, you're good. The AMS players aren't in this category. |
| 23:02:04 | chrivers | I'm not in a mood to argue semantics, you're completely missing the point |
| 23:02:24 | | Join almog1006 [0] (051c8f77@gateway/web/freenode/ip.5.28.143.119) |
| 23:02:25 | [Saint] | The "unbrick" method isn't understood *at all*. |
| 23:03:41 | [Saint] | That's for all intents and purposes luck and magic. No clue what purpose that mode serves or if there's a standardized way to interface with it. |
| 23:04:34 | chrivers | I don't know who you're arguing with |
| 23:04:53 | chrivers | Bilgus: thanks for the help.. I think I'll keep the fuze parts, and see if I can buy a broken one as parts |
| 23:05:07 | chrivers | maybe a frankensteinian fuze will emerge |
| 23:06:27 | Bilgus | generally you wouldn't have to use recovery mode and could get into usb bootloader so wouldn't be a brick |
| 23:07:08 | Bilgus | but chrivers I am aware of the voltage scaling issues and will push that default voltage patch once I get it all figured out |
| 23:07:23 | chrivers | Bilgus: awesome, thanks :) |
| 23:08:12 | chrivers | Bilgus: I wonder, is there a way to (easily) mod rockbox to use the menu button only? Maybe something like shuffle always on, long-press=play/pause, short-press=next ? |
| 23:08:17 | chrivers | it'd be better than nothing |
| 23:08:29 | Bilgus | yes completely possible |
| 23:10:03 | chrivers | would I have to compile a custom version, or can I just edit some config files? |
| 23:10:12 | [Saint] | The former. |
| 23:10:19 | Bilgus | chrivers go into the debug menu and the io portion and see if you have anything at all that is working |
| 23:10:33 | chrivers | Bilgus: ..how :) |
| 23:10:35 | Bilgus | you should see the gpios bounce on and off |
| 23:10:42 | [Saint] | He can't. |
| 23:10:43 | Bilgus | duh :/ |
| 23:11:01 | Bilgus | ok you have a power button/hold and a home button to use? |
| 23:11:09 | chrivers | yes |
| 23:11:12 | chrivers | they work |
| 23:11:26 | chrivers | and I can't remember if it's fancy enough to detect button press on headset? |
| 23:11:34 | [Saint] | I think on these the hold button actually depowers the other buttons? |
| 23:11:36 | chrivers | if it is, that'd probably work too |
| 23:11:43 | Bilgus | doubt we support it even if it did |
| 23:11:49 | chrivers | fair enough |
| 23:11:53 | [Saint] | I think I can see the logic of using hold as a modifier but I'm not sure it can be done here. |
| 23:12:15 | Bilgus | let me have a look and see what we are working with |
| 23:12:36 | | Quit shmibs (Quit: leaving =o) |
| 23:12:37 | chrivers | that would be great |
| 23:12:53 | chrivers | I have to get some sleep, right about now.. or an hour ago, if possible ;) |
| 23:13:19 | chrivers | but I'll stay logged in here - let me know if you get any crazy ideas, I'm all ears |
| 23:13:55 | | Join shmibs [0] (~shmibs@shmibbles.me) |
| 23:15:22 | Bilgus | the hold button is not a actual lockout we check its position |
| 23:15:45 | Bilgus | so yes we can do it but It'll be a few days before I get to it |
| 23:16:22 | Bilgus | it'll be home button does movement and hold button selects I suppose |
| 23:16:35 | chrivers | haha, it's pretty crazy :D |
| 23:17:06 | chrivers | I think the only real solution is to get a broken player for parts |
| 23:17:11 | Bilgus | maybe something with the length of press or number of presses or something IDK yet |
| 23:17:36 | chrivers | well, I'd be content with just having a player in constant shuffle mode |
| 23:17:50 | chrivers | then I can load a new set of MP3s if I want to listen to something else |
| 23:18:00 | *** | Saving seen data "./dancer.seen" |
| 23:18:59 | Bilgus | that is possible through the config file if you want to edit it |
| 23:19:07 | chrivers | well now we're talking |
| 23:19:27 | chrivers | then I can use it like that, until the replacement part arrives |
| 23:19:39 | Bilgus | maybe we can set party mode |
| 23:23:17 | Bilgus | in the .rb directory you should have a file config.cfg if not which is probable create a file and put 'party mode: on |
| 23:23:18 | Bilgus | ' 'start in screen: wps' |
| 23:23:36 | Bilgus | each on a separate line no spaces after and no ' |
| 23:24:16 | Bilgus | as for actually starting a file give me a second to figure that out |
| 23:25:11 | Bilgus | being that we don't have a playlist made we can't get a CRC to resume any files.. |
| 23:26:09 | chrivers | oh, is that how files are resumed? interesting :) |
| 23:26:51 | | Quit lebellium (Quit: Leaving) |
| 23:26:52 | chrivers | yep, now it says "nothing to resume", so it's clearly different |
| 23:29:12 | Bilgus | we have an option to start pictureflow so it could probably be tweaked to do what we want but i'll have to get to it tomorrow |
| 23:30:03 | chrivers | no worries, you've done a lot already :) |
| 23:30:10 | chrivers | egads, I really must be getting to bed |
| 23:30:22 | chrivers | thanks for the help - I'll idle here for a bit |
| 23:30:28 | * | chrivers says goodnight all |
| 23:36:27 | jhMikeS | Bilgus: what's happening is the context searching is somehow calling get_context_map with the value 0x00000002 |
| 23:36:59 | jhMikeS | if I filter the invalid value and return NULL nothing crashes |
| 23:37:25 | jhMikeS | can still navigate but no album selection, still calls with 0x00000002 on pressing select |
| 23:38:03 | Bilgus | yeah its not picking up on it being null its supposed to fall through to the builtin contexts but instead its grabbing the invalid memory |
| 23:39:44 | Bilgus | it's totally my change that is causing it but I need to figure out how to best handle it |
| 23:43:48 | | Quit ZincAlloy (Quit: Leaving.) |
| 23:44:33 | jhMikeS | I think I see it. The callback is set upon calling get_custom_action but when the context actually changes away to the internal one, the pointer isn't updated |
| 23:45:21 | jhMikeS | so, then you know the rest.... |
| 23:49:40 | Bilgus | exactly.. |
| 23:52:21 | Bilgus | jhMikeS, it turns out the original action system does exactly the same |
| 23:52:52 | Bilgus | There needs to be a chained context on the end of that list |
| 23:53:12 | Bilgus | or maybe a simple NULL |
| 23:53:20 | jhMikeS | it had a flag test that was removed |
| 23:54:08 | Bilgus | it only does it on a button press not in the menu |
| 23:54:27 | | Quit almog1006 (Ping timeout: 260 seconds) |
| 23:55:08 | | Join krabador [0] (~krabador@unaffiliated/krabador) |
| 23:56:05 | Bilgus | on an invalid button press ** |
| 23:57:21 | Bilgus | but in my mind this should be handled in the action system to fit in to falls through to the internal mapping |
icon identifies that the person is a core developer (has commit access).