Previous day | Jump to hour: 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 | Next day

Seconds: Show Hide | Joins: Show Hide | View raw
Font: Serif Sans-Serif Monospace | Size: Small Medium Large

Click in the nick column to highlight everything a person has said.
The Logo icon identifies that the person is a core developer (has commit access).

#rockbox log for 2023-12-19

00:27:02 Quit jacobk (Read error: Connection reset by peer)
00:31:18 Join jacobk [0] (
01:16:21sporkDanH: did you try installing the bootloader with rockbox utility?
01:16:30sporkit is supposed to be able to do that
01:17:11DanHspork: yes I did. I noticed that the bootloader changed from 3.10 to something longer and less memorable, so I think I did that right
01:17:25sporklots of information in the forum thread,51844.0.html
01:22:21sporkand no errors of course when trying to install it ?
01:27:57***Saving seen data "./dancer.seen"
01:35:17 Quit sch (Ping timeout: 240 seconds)
01:36:18sporki have always done it the manual way
01:36:22 Quit DanH (Ping timeout: 260 seconds)
01:36:45sporkpatch the firmware, 'upgrade' and see the firmware file is gone
01:40:10 Join sch [0] (
01:40:10 Quit CH23_M (Read error: Connection reset by peer)
01:41:06 Join CH23_M [0] (~CH23@revspace/participant/ch23)
01:43:38 Join DanH [0] (
02:10:45DanHNo errors, it just doesn't seem to boot rockbox from the SD card that I can tell
02:18:35sporkand you have a daily build on your sd card and the redirect file on the sd card as well ?
02:21:54sporkhardest thing for me was to create the rockbox_main.clip+ file
02:22:08sporkthat is not a windows-friendly name
03:06:11 Quit CH23_M (Ping timeout: 252 seconds)
03:06:28 Join CH23_M [0] (~CH23@revspace/participant/ch23)
03:23:40DanHYes, it just occurred to me that there may be something funky with the SD card itself. I think I may try reformatting jt
03:24:36DanHFor example, the SD card doesn't properly eject on Linux
03:25:34DanHI assume the SD card should have a single partition and be formatted fat 32?
03:28:01***Saving seen data "./dancer.seen"
03:34:48 Quit JanC (Ping timeout: 252 seconds)
03:36:11 Quit Piece_Maker (Ping timeout: 245 seconds)
03:37:22 Join JanC [0] (~janc@user/janc)
03:47:43 Quit jacobk (Ping timeout: 268 seconds)
04:32:20buZzaaabbb: the projectname for that esp32 mp3player
04:32:36aaabbbah ok
04:36:51 Join PheralSparky [0] (~Shawn@user/shawn/x-4432647)
05:08:06 Join termac [0] (~termac@user/termac)
05:22:47 Quit CH23_M (Read error: Connection reset by peer)
05:23:10 Join CH23_M [0] (~CH23@revspace/participant/ch23)
05:23:12 Quit braewoods (Remote host closed the connection)
05:23:31 Join braewoods [0] (~braewoods@user/braewoods)
05:27:03 Join braewoods_ [0] (~braewoods@user/braewoods)
05:28:03***Saving seen data "./dancer.seen"
05:28:43 Quit braewoods_ (Read error: Connection reset by peer)
05:28:45 Join braewoods__ [0] (~braewoods@user/braewoods)
05:28:53 Quit braewoods (Ping timeout: 240 seconds)
05:31:38 Join braewoods [0] (~braewoods@user/braewoods)
05:33:17 Quit braewoods__ (Ping timeout: 240 seconds)
05:39:17 Quit braewoods (Remote host closed the connection)
05:39:32 Join braewoods [0] (~braewoods@user/braewoods)
05:42:43 Quit braewoods (Remote host closed the connection)
05:43:02 Join braewoods [0] (~braewoods@user/braewoods)
05:47:26 Quit braewoods (Ping timeout: 245 seconds)
05:50:39 Join braewoods [0] (~braewoods@user/braewoods)
05:54:45 Quit PheralSparky (Quit: Leaving)
06:16:42 Quit braewoods (Remote host closed the connection)
06:17:04 Join braewoods [0] (~braewoods@user/braewoods)
06:19:36 Join braewoods_ [0] (~braewoods@user/braewoods)
06:19:40 Quit braewoods (Read error: Connection reset by peer)
06:21:18 Quit braewoods_ (Remote host closed the connection)
06:21:31 Join braewoods_ [0] (~braewoods@user/braewoods)
06:24:29 Join braewoods [0] (~braewoods@user/braewoods)
06:25:57 Quit braewoods_ (Read error: Connection reset by peer)
07:08:30_bilgusDanH multiboot requires a proper bootloader and a dev version
07:10:30_bilgusin the debug menu under boot data (in a dev version) you will see Boot Volume <0> and CRC: Bad and if its working youd see Boot Volume <1> CRC: OK!
07:28:06***Saving seen data "./dancer.seen"
07:39:39 Quit tertu (Quit: so long...)
07:40:39 Join tertu [0] (~tertu@user/tertu)
07:42:57 Quit braewoods (Remote host closed the connection)
07:43:03 Join braewoods_ [0] (~braewoods@user/braewoods)
08:57:26 Quit martylake (Ping timeout: 245 seconds)
09:00:37 Join martylake [0] (~martylake@
09:08:47 Quit braewoods_ (Remote host closed the connection)
09:09:01 Join braewoods_ [0] (~braewoods@user/braewoods)
09:12:17 Quit braewoods_ (Remote host closed the connection)
09:12:51 Join braewoods [0] (~braewoods@user/braewoods)
09:28:08***Saving seen data "./dancer.seen"
09:42:01 Quit braewoods (Read error: Connection reset by peer)
09:43:32 Join braewoods [0] (~braewoods@user/braewoods)
10:18:47 Quit braewoods (Remote host closed the connection)
10:19:01 Join braewoods [0] (~braewoods@user/braewoods)
10:42:19 Quit sch (Ping timeout: 246 seconds)
10:44:07 Quit DanH (Ping timeout: 255 seconds)
10:58:54 Join DanH [0] (
11:00:49DanH_bilgus: I'm pretty sure I have the bootloader installed correctly and I have the dev version of rockbox
11:28:10***Saving seen data "./dancer.seen"
11:52:27 Join sch [0] (
12:10:23 Join CH23 [0] (~CH23@revspace/participant/ch23)
12:14:27 Quit braewoods (Read error: Connection reset by peer)
12:14:30 Join braewoods_ [0] (~braewoods@user/braewoods)
12:17:06 Join jacobk [0] (
12:17:37 Join braewoods [0] (~braewoods@user/braewoods)
12:19:19 Quit braewoods_ (Ping timeout: 260 seconds)
12:19:47 Quit braewoods (Read error: Connection reset by peer)
12:20:16 Join braewoods [0] (~braewoods@user/braewoods)
12:22:17 Quit braewoods (Read error: Connection reset by peer)
12:22:32 Join braewoods [0] (~braewoods@user/braewoods)
12:25:44 Join braewoods_ [0] (~braewoods@user/braewoods)
12:27:15 Quit braewoods (Ping timeout: 260 seconds)
12:31:36 Quit braewoods_ (Read error: Connection reset by peer)
12:31:58 Join braewoods [0] (~braewoods@user/braewoods)
12:37:38 Quit braewoods (Read error: Connection reset by peer)
12:38:12 Join braewoods [0] (~braewoods@user/braewoods)
12:41:20 Quit braewoods (Remote host closed the connection)
12:41:31 Join braewoods [0] (~braewoods@user/braewoods)
13:04:05 Join lebellium [0] (
13:17:51 Quit jacobk (Ping timeout: 245 seconds)
13:28:11***Saving seen data "./dancer.seen"
14:22:01 Quit yang2 (Ping timeout: 245 seconds)
14:22:38 Join yang2 [0] (
14:24:06 Quit michaelni (Ping timeout: 245 seconds)
14:37:21 Join michaelni [0] (~michael@
15:28:14***Saving seen data "./dancer.seen"
15:38:41 Join Piece_Maker [0] (
16:11:41_bilgusDanH the other issue could be a not truly empty redirect file i'd also try a single / in case windows adds a BOM or a /n or something
16:12:07_bilgusso nothing on the line but / and no return
16:12:43DanHI'm on Linux and I just did `touch rockbox_main.clip+`
16:12:57_bilgusthat should be fine
16:14:12DanHIs it possible that the partition type or partitioning more generally could make the file inaccessible to the bootloader?
16:15:12_bilguswell it could be a bad format yes esp since the current bootloaders are more lenient than the firmware ATM
16:15:40_bilgusbut i'd not epect it to work after booting though
16:16:13DanHOr are there particular parameters that I should be paying attention to/explicitly setting when formating the sd card?
16:16:31DanHYeah, the sd card is accessible after boot
16:16:49_bilgusI see more issues with trying to format in linux since in windows you have to use 3rd party tools
16:17:10DanHIs there a log from the bootloader stored anywhere?
16:17:17_bilguswhat does the boot data read?
16:17:56_bilgusyou can also verify by playing a song from internal shutdown pop sd and see if the song resumes
16:18:17_bilguswhat I usually do is put 3.15 on the internal drive and my dev versions on the SD
16:18:30_bilgusits very apparent its 3.15
16:20:20_bilgus DanH its very minimal because we have targets that compress the OF inorder to piggyback the bootloader
16:21:12DanHI'll have to run that experiment later tonight
16:21:21DanHDon't have it in front of me at the moment
16:24:48_bilgusJust to be sure you have you empty redirect in the root of the SD card and your .rockbox folder is in the root as well in the sense ls shows /rockbox_main.clip+ and ./rockbox
16:25:48DanHSo, anecdotally, I assume booting from SD card makes rockbox more stable, given the age of most clip+ internal flash?
16:26:06DanHMine is currently freezing at unexpected moments
16:31:43_bilguseh are you sure you got the multiboot bootloader on there?
16:32:38DanHI think so?
16:33:18DanHThe version of the bootloader that briefly flashes when it boots is no longer 3.10, but it looks rather like a commit hash from git or something
16:33:47_bilgusthat sounds good
16:35:04_bilgusDanH you can try running your firmware from whatever boots so boot it then go to the sd card and run the .sansa file and see if that works
16:38:50_bilguswhere did you get that bootloader?
16:41:48DanHI did it manually
16:42:01_bilgusI figured thats why I asked
16:42:11DanHWith mkamsboot and a support original firmware version
16:42:24_bilgusoh you built it?
16:42:48_bilgusbecause if you built it then all bets are off
16:43:16DanHI didn't build it
16:43:27DanHJust patched the original firmware file
16:43:43DanHFollowing the instructions in the manual
16:45:45_bilgusIf your freezing issues are because of bad flash then yeah running from SD should be more stable
16:45:56DanHThat is my theory anyway
16:46:38DanHI guess it could also somehow be related to the SD card itself being flaky since I am playing media from it
16:46:40_bilgusif its a RAM issue or power issue no since its still using them
16:47:06_bilguslikely not we run from ram only write infrequently
16:47:27DanHDoes the ram get botched pretty regularly on these?
16:47:53DanH(by ram issue I assume you mean that the ram can become defective)
16:48:32_bilgusonly with physical damage in my experience
16:49:31_bilgushad one that was green and a solder reflow fixed it, it wouldn't do anything but backlight prior
16:49:59DanHGot it
16:50:19_bilgusthe flash is the main part so i've alwasy run from SD and have not had issues yet
16:52:10_bilgusour newer firmware also writes a temporary file now instead of overwrite to help spread writes now too
16:53:00_bilgusmy hope is that will help but I really have no way to say it does
16:53:54DanHI just bought a Samsung high endurance SD card in the hopes that it makes it more resilient
16:54:20_bilgusmore likely to get a fake
16:55:00_bilgusI buy middle ground at local retailers and haven't seen a shit one yet
16:57:56_bilgusthose class 10 are fine
16:59:02_bilgusif you bought local less of a concern likely
17:02:39_bilgusstill if you can run it from the browser off the sd card then it should boot
17:05:58_bilgusDanH if all else fails here is the original one I made
17:07:10_bilgusbut I'd really be sure because if its already flaky why push it
17:09:15_bilgusthe Clip+ (and zip) actually has what appears to be two valid firmware headers in dumps I never did figure out how it decides to use one or the other
17:09:51 Quit CH23_M (Read error: Connection reset by peer)
17:10:23_bilgusI always figured it was there incase an update failed it still had that one and hadn't overwritten the boot record yet
17:10:36 Join CH23_M [0] (~CH23@revspace/participant/ch23)
17:11:26_bilgusI also wonder if you could do multiple upgrades to move the files to a different sector
17:13:12 Quit termac (Ping timeout: 252 seconds)
17:28:15***Saving seen data "./dancer.seen"
17:43:14 Quit lebellium (Quit: Leaving)
18:00:13 Join othello8 [0] (
18:02:44 Quit jjs0077 (Ping timeout: 268 seconds)
18:11:35 Quit othello8 (Quit: othello8)
18:30:46 Join PheralSparky [0] (~Shawn@user/shawn/x-4432647)
18:48:16 Join massiveH [0] (~massiveH@2600:4040:a982:c800:2985:8d19:fca5:4c24)
19:21:48 Join Moriar [0] (
19:28:19***Saving seen data "./dancer.seen"
20:01:46 Quit CH23 (Quit: Leaving)
21:28:20***Saving seen data "./dancer.seen"
21:44:28 Quit massiveH (Quit: Leaving)
22:19:35 Quit Moriar (Quit: Leaving.)
23:28:24***Saving seen data "./dancer.seen"

Previous day | Next day