--- Log for 20.08.120 Server: kornbluth.freenode.net Channel: #rockbox --- Nick: logbot_ Version: Dancer V4.16 Started: 22 days and 10 hours ago 00.24.18 Quit ac_laptop (Ping timeout: 256 seconds) 00.33.41 *** Saving seen data "./dancer.seen" 01.46.23 Join Huntereb [0] (~Huntereb@174.226.10.189) 02.31.14 # amdj: percussive maintenance doesn't fix removed EFI entries. (no clue how that happened) 02.33.44 *** No seen item changed, no save performed. 02.42.30 # there are some truly terrible EFI firmwares out there. one vendor (the name escapes me) has an entire product line that won't boot anything unless the entry friendly name (which is ignored, because it doesn't display them in a menu anyway) is "Microsoft Boot Manager". 02.43.17 # (or "Windows Boot Manager" or whatever the name is given by the Windows installer) 02.43.59 # wow. this is usually good it just wiped the hard drive boot entries for some unknown reason (first time in 5 years it's happened on this system) 02.52.54 # then there was that time that Samsung laptops permanently bricked themselves and wouldn't boot anything at all if the EFI Boot Manager NVRAM configuration was >50% full. 03.28.56 Join johnb2 [0] (~johnb2@p5b3af13d.dip0.t-ipconnect.de) 04.23.13 # __BILGUS: Thinking of the manual - I wasn't sure if MULTIBOOT was documented- I looked at the manual of clip+. It says that you can specify /mybuild/ in the redirect file. I thought you had disabled that. It works for me on some players as I still have the intermediate version of the BL on them. It does definitely NOT work on the e200 (it's complaining about incomplete installation, missing .rockbox directory). 04.24.16 # I personally like it a lot since I can use the same SDcard in multiple players. 04.32.22 Quit Huntereb (Ping timeout: 246 seconds) 04.33.48 *** Saving seen data "./dancer.seen" 04.36.27 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 05.10.14 Join J_Darnley [0] (~J_Darnley@d51A44418.access.telenet.be) 05.10.25 Quit jdarnley (Ping timeout: 265 seconds) 05.28.20 Join jdarnley [0] (~J_Darnley@d51A44418.access.telenet.be) 05.29.47 Quit J_Darnley (Ping timeout: 240 seconds) 06.33.49 *** Saving seen data "./dancer.seen" 07.04.36 # <__BILGUS> johnb it actually depends on the firmware 07.05.27 # <__BILGUS> the multiboot patch on my gerrit handles root redirection but it never got completely finished 07.05.42 # <__BILGUS> its still the eventual plan 07.06.05 # But as of today, the manual is wrong? 07.06.17 # <__BILGUS> and you did check the current 2662 works? 07.06.37 # yes, if it is in / 07.06.39 # <__BILGUS> suppose but it will still boot it 07.06.55 # <__BILGUS> just the firmware will get confused 07.07.52 # yes, but weird effects for the "cursor line", text being displayed. Probably if I create a /.rockbox manually it is happy. 07.08.10 # <__BILGUS> indeed 07.08.14 # But might run into issues if I change the player (nvram ?). 07.09.14 # I remember the discussions on G#1613 07.09.16 # Gerrit review #1613 at http://gerrit.rockbox.org/r/1613 : Multiboot Firmware Root Redirect - Do Not Push by William Wilgus 07.09.55 # <__BILGUS> I think itd boot /rfghhhhgf/boot.sansa but without redirection itd do writes to /.rockbox 07.10.38 # Yep, we had seen that in the early experiments. 07.10.43 # <__BILGUS> which makes it a bit hard to do multiple players off one card 07.11.36 # <__BILGUS> I keep hoping sevakis will finish the root redirect stuff 07.11.39 # As for your gerrit version of the redirect, I was fine with it ;-) It was working for me. 07.12.23 # <__BILGUS> tbh I might just put it in Its the version I ran for a year or two with no issue 07.12.53 # <__BILGUS> the redirect stuff is REALLY slick 07.12.53 # I would be in favour of this, too. 07.14.19 # <__BILGUS> sounds like a plan I'll try to get it done before the next release 07.14.33 # Thanks 07.14.52 # <__BILGUS> 2662 i'm gonna push here shortly before I leave for the day 07.16.06 # Build Server message: New build round started. Revision da19072, 280 builds, 11 clients. 07.16.19 # The manual will have the redirect filename automatically, right? I was thinking whether the commit message needs more information, but if the manual has it ... 07.16.40 # <__BILGUS> uhhh I think you need to define them 07.16.56 # <__BILGUS> but we can revisit once we see what shows up 07.17.24 # ok 07.19.01 # <__BILGUS> yeah \opt{clipzip}{\renewcommand*{\redirectext}{clipzip}} 07.19.47 # <__BILGUS> so yours whould be something like \opt{e200}{\renewcommand*{\redirectext}{e200}} 07.20.03 # <__BILGUS> assuming it uses e200 as the player tag 07.20.14 # <__BILGUS> (first one) 07.20.35 # probably more like sansae200 07.20.54 # <__BILGUS> yeah whatever it uses as the player tag in the manual 07.20.57 # I can have a look 07.23.40 # <__BILGUS> it looks like there are several other players that now have the possibility of multiboot c200 and some samsungs iriver and vibe500? 07.24.20 # <__BILGUS> wonder how many are actually feasible 07.25.31 # In order to re-use the large SDcards with my music collection on different player, I would love to see the redirect (some subdir) to work also for hosted devices like Xduoo x3ii. 07.26.29 # RB is already loaded from the SD, but only from root. 07.28.12 # <__BILGUS> root redirect would allow that but it'd still need to have multiboot or some other mechanism to define taht 07.28.57 # <__BILGUS> but no reason it has to be done in the bootloader on those 07.29.02 Quit pamaury (Ping timeout: 260 seconds) 07.30.03 # <__BILGUS> herte soon ill have an x3 hopefully they shar e a similar backend 07.30.54 # Build Server message: Build round completed after 887 seconds. 07.30.58 # Build Server message: Revision da19072 result: All green 07.31.01 # <__BILGUS> woo 07.31.37 # We tested enough before, heh? ;-) 07.33.17 # <__BILGUS> just hoping the other players compiled on my other pc I usually run a whole build round on the bigger stuff 07.33.58 # <__BILGUS> 'on the road this laptop takes as long for a single build 07.44.10 Quit johnb2 (Ping timeout: 246 seconds) 08.05.54 Join petur [0] (~petur@77.77.179.66) 08.05.54 Quit petur (Changing host) 08.05.54 Join petur [0] (~petur@rockbox/developer/petur) 08.20.04 Quit __BILGUS (Ping timeout: 245 seconds) 08.33.52 *** Saving seen data "./dancer.seen" 09.00.04 Join johnb2 [0] (~johnb2@p5b3af13d.dip0.t-ipconnect.de) 09.06.53 Join massiveH [0] (~massiveH@ool-18e4e82f.dyn.optonline.net) 09.23.22 Quit akaWolf (Ping timeout: 260 seconds) 10.10.01 # Bilgus: as for the manual, you were right, it is just that line. 10.10.47 # exit 10.10.51 Quit johnb2 (Quit: Nettalk6 - www.ntalk.de) 10.22.22 Quit massiveH (Quit: Leaving) 10.28.09 Join akaWolf [0] (~akaWolf@akawolf.org) 10.32.46 Join xlinka [0] (51639436@cpc160247-nrth4-2-0-cust53.8-4.cable.virginm.net) 10.33.55 *** Saving seen data "./dancer.seen" 10.35.09 Quit xlinka (Remote host closed the connection) 11.32.11 Quit petur (Quit: Connection reset by beer) 12.33.56 *** Saving seen data "./dancer.seen" 13.24.22 Join johnb2 [0] (~johnb2@p5b3af13d.dip0.t-ipconnect.de) 13.48.13 Quit johnb2 (Ping timeout: 264 seconds) 14.04.38 Join lebellium [0] (~lebellium@89-92-253-148.hfc.dyn.abo.bbox.fr) 14.33.59 *** Saving seen data "./dancer.seen" 15.04.54 Join __Bilgus_ [0] (41ba23be@65.186.35.190) 15.13.08 # Build Server message: New build round started. Revision 0459bfe, 280 builds, 12 clients. 15.17.37 Quit akaWolf (Ping timeout: 264 seconds) 15.19.51 Join akaWolf [0] (~akaWolf@akawolf.org) 15.28.21 # Build Server message: Build round completed after 913 seconds. 15.28.23 # Build Server message: Revision 0459bfe result: All green 15.35.03 Quit Rower () 15.35.16 # Build Server message: New build round started. Revision 71846b0, 280 builds, 12 clients. 15.43.45 Join skeeball [0] (~skeeball4@69.167.11.69) 15.45.15 # I just installed Rockbox 3.15 on a Sansa Clip Zip. When I try to connect it to my computer running Linux Debian 10) 15.45.37 # it mounts, but the file manager lags and doesn't load anything 15.45.55 # Running 'ls' in bash doesn't load anything and it just times out 15.46.18 # Basically, I can't access the file system through USB. I would appreciate some help. Thanks. 15.50.39 # Build Server message: Build round completed after 923 seconds. 15.50.41 # Build Server message: Revision 71846b0 result: All green 16.00.49 Join skeeball2 [0] (~skeeball4@2603:9000:6a01:ff13::1000) 16.01.06 # skeeball: what's in the kernel logs? 16.01.17 # The kernel logs? 16.01.23 # of the debian system 16.01.31 # skeeball: I'm not sure how to get those... 16.01.35 # 'dmesg' 16.02.35 Quit skeeball (Ping timeout: 240 seconds) 16.02.43 # speachy: One sec, I'm looking through them 16.03.45 # speachy: I see a lot of '[65689.792267] FAT-fs (sdd): Directory bread(block 2151) failed" 16.04.01 # speachy: It repeats for a bunch of different blocks 16.04.03 # I'd suspect a flaky cable 16.04.31 # speachy: Really? I guess the cable is old and I haven't used it for anything for a long time. 16.05.10 # the miniusb cable I use craps out if I bump it the wrong way 16.05.10 # Here is what it prints after '[65689.792267] FAT-fs (sdd): Directory bread(block 2151) failed" 16.05.23 # [65698.215271] sd 6:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE 16.05.34 # [65698.215272] sd 6:0:0:0: [sdd] tag#0 Sense Key : Medium Error [current] 16.05.37 # it fails to read the device so tries to issue resets 16.05.43 # [65698.215274] sd 6:0:0:0: [sdd] tag#0 Add. Sense: Unrecovered read error 16.05.49 # [65698.215275] sd 6:0:0:0: [sdd] tag#0 CDB: Read(10) 28 00 00 00 08 68 00 00 01 00 16.05.59 # [65698.215276] print_req_error: critical medium error, dev sdd, sector 2152 16.06.06 # Then it just repeats for a different block 16.06.27 # speachy: So you still think probably just a bad cable and not a bigger problem with the device? 16.13.23 # most likely. AFAIK there are no issues with the clip zip. 16.14.30 # speachy: I got a different cable (that I think works), now dmesg is telling me a I should run fsck 16.14.42 # [66120.002919] sd 7:0:0:0: [sde] Attached SCSI removable disk 16.14.48 # [66120.593563] FAT-fs (sde): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. 16.15.12 # Maybe b/c didn't unmount properly when I took it out? 16.16.34 # Working on that now, then I'll see if that helps 16.19.21 Quit __Bilgus_ (Remote host closed the connection) 16.34.01 *** Saving seen data "./dancer.seen" 16.44.48 # Having issues with fsck. Rockbox would normally be on a Fat32 partition, right? 16.50.37 Quit lebellium (Quit: Leaving) 17.03.36 Quit skeeball2 (Quit: Leaving) 17.35.21 Quit Rondom (Remote host closed the connection) 17.35.33 Join Rondom [0] (~rondom@modo.nonmodosedetiam.net) 18.05.35 Join ac_laptop [0] (~ac_laptop@186.2.247.129) 18.17.46 Join __Bilgus [0] (41ba23be@65.186.35.190) 18.21.55 Quit ac_laptop (Ping timeout: 240 seconds) 18.34.02 *** Saving seen data "./dancer.seen" 18.38.35 Join MrZeus [0] (~MrZeus@05467834.skybroadband.com) 18.48.01 Quit __Bilgus (Remote host closed the connection) 19.07.12 # Build Server message: New build round started. Revision 31fc46d, 280 builds, 11 clients. 19.08.20 Join __Bilgus [0] (41ba23be@65.186.35.190) 19.23.28 # Build Server message: Build round completed after 977 seconds. 19.23.30 # Build Server message: Revision 31fc46d result: All green 19.23.31 # Build Server message: New build round started. Revision 5ef28cc, 280 builds, 11 clients. 19.29.56 # <__Bilgus> Johnb can you try your new bootloader with the current head and also the firmware we now have root redirect after the 3rd build round completes 19.39.14 # __Bilgus, I worry that the "any dir as root" patch might have adverse interactions with the hacks embodied in the hosted target code to achieve much the same thing 19.41.07 # Build Server message: Build round completed after 1056 seconds. 19.41.08 # Build Server message: Revision 5ef28cc result: 795 errors 256 warnings 19.41.09 # Build Server message: New build round started. Revision bd74405, 280 builds, 10 clients. 19.41.10 # <__Bilgus> i think it all worked before but if there are issues I'll ifdef out the redirect 19.41.29 # ouch, that's a lot of red 19.41.31 # <__Bilgus> 256 warnings lol 19.42.01 # broke on simulator and hosted builds. :D 19.42.44 # <__Bilgus> eww its nasty too at first glance 19.43.02 # <__Bilgus> might have to revert these and do a little more work 19.43.19 # guess I was more correct than I realized.. 19.43.54 # <__Bilgus> suppose thats what happens when I let stuff sit for 2 years 19.44.36 # most of the bootloader warnings can probably be fixed with a single commit. And I think fixing the simulator targets will probably fix nearly all of the hosted issues too. 19.46.19 # Build Server message: Build round completed after 310 seconds. 19.46.20 # Build Server message: Revision bd74405 result: 1810 errors 508 warnings 19.46.26 # gah, it's worse. :) 19.47.12 # that's the largest score I've seen in some time. everything failed except for checkwps and manunals. :) 19.54.20 Quit Tsesarevich (Ping timeout: 244 seconds) 19.55.15 # <__Bilgus> working on it lol 19.57.37 Join Tsesarevich [0] (Tsesarevic@fluxbuntu/founder/joejaxx) 20.34.04 *** Saving seen data "./dancer.seen" 20.37.12 # <__Bilgus> nope its getting to be too much stuff to fix while head is broken 20.49.25 Quit MrZeus (Ping timeout: 240 seconds) 21.14.31 Join ac_laptop [0] (~ac_laptop@186.2.247.129) 21.59.15 # Build Server message: New build round started. Revision f850bbb, 280 builds, 10 clients. 21.59.32 # * __Bilgus sigh 22.02.51 # hey, it happens. :/ 22.03.01 # just glad it wasn't me this time... 22.03.58 # <__Bilgus> I swear I rebase that damn thing an compiled it multiple times 22.05.08 # <__Bilgus> its hopelessly broken for the moment it'll need the path functions broken out by application [SIM, NATIVE, HOSTED] 22.05.11 # acutally.. it might have been a bogus .depend thing 22.05.44 # I routinely do a 'make dep && make zip' prior to anything I push now 22.06.05 # <__Bilgus> hmm make dep? 22.08.24 # I wonder if it might not be worth moving from a monolithic .depend to per-file .depend instead. there are plusses and minuses 22.09.45 # that or maybe it was the deep state sabotaging your build 22.09.49 # or bunnies. yes, bunnies. 22.10.43 # <__Bilgus> doubtful more like it was probably before the rocker stuff 22.11.03 # <__Bilgus> and I haven't touched it since or if I did its on my home pc 22.11.29 # <__Bilgus> I vaguely remember doing so but who knows at this point 22.14.08 # Build Server message: Build round completed after 893 seconds. 22.14.09 # Build Server message: Revision f850bbb result: All green 22.34.08 *** Saving seen data "./dancer.seen" 22.52.26 Quit ac_laptop (Ping timeout: 258 seconds) 23.03.11 Quit paulk-leonov (Ping timeout: 246 seconds) 23.04.15 Join paulk-leonov [0] (~paulk-leo@vpn-0-22.aquilenet.fr) 23.28.14 Quit TheSeven (Ping timeout: 244 seconds) 23.28.38 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven)