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).

Notice: Only Gecko based browsers prior to FF4 support the multipart/mixed "server push" method used by this log reader to auto-update. Since you do not appear to use such a browser, this page will simply show the current log, and not automatically update.

#rockbox log for 2016-12-27

00:00:19[Saint]Bilgus:
00:00:19[Saint]1 - ready access to parts
00:00:19[Saint]2 - lack of access (for most people) to a hot air and/or reflow station
00:00:43[Saint]it is literally less expensive to replace the whole unit.
00:02:17[Saint]Even if we assume that one can find the exact same model of NAND storage, most distributors aren't even going to want to consider talking to you unless you're buying tens of thousands of units.
00:17:08 Join Bilgus_ph [0] (~Bilgus_ph@108.115.127.71)
00:18:33Bilgus_phNone of those sound insurmountable though and it doesn't have to be the same model just proper pinout or something close enough to tweak
00:19:59Bilgus_phNot to say easy but something fun to try
00:38:02[Saint]that would be a very expensive lesson in how to fuck shit up.
00:39:30[Saint]the bootloader expects to see specific hardware, unless you managed to find a pinned package for this NAND and then added a ZIF pin connector to the board your development would take a VERY long time.
00:40:34[Saint]since you'll be having to do the weird spoopy magic not really understood in any capacity low-level restore every time you fucked up the bootloader.
00:50:59 Quit Bilgus_ph (Ping timeout: 248 seconds)
01:00
01:04:01 Quit ender` (Quit: Anti-intellectualism has been a constant thread winding its way through our political and cultural life, nurtured by the false notion that democracy means that 'my ignorance is just as good as your knowledge.'— Isaac Asimov)
01:16:04 Part robertd1
01:34:17 Join naleo [0] (~naleo@unaffiliated/naleo)
01:42:08 Quit Rondom (Remote host closed the connection)
01:42:50 Join Rondom [0] (~rondom@modo.nonmodosedetiam.net)
01:53:22 Quit naleo (Ping timeout: 258 seconds)
01:54:35***Saving seen data "./dancer.seen"
02:00
02:04:44shrizzaUgh, iPod it is then huh.
02:05:06shrizzaDoesn't sit well with me but if it is the most servicable device.
02:05:52[Saint]They're not.
02:06:08shrizzaWhat is then?
02:06:10[Saint]But it is the most serviceable and readily available device.
02:06:55[Saint]Presumably serviceability isn't interesting to you if you can't actually acquire the device.
02:08:56shrizzaStill curious to hear what remarkable device you have in mind though.
02:11:13shrizzaI'm down to two Sansa Clips and one of them has slowly dying flash.
02:11:28[Saint]Why must they be remarkable?
02:11:52shrizzaWell you said they were difficult to acquire. That sounds remarkable to me.
02:12:08[Saint]Not particularly. Just old.
02:12:26[Saint]Or expensive.
02:12:28[Saint]Or both.
02:12:46shrizzaBut it's serviceable right?
02:13:01shrizzaOr are the parts also remarkable in that way.
02:14:39Bilguswell that kinda sucks, I'm good with hardware onlr mediocre with software
02:16:26[Saint]Where "it" == ?
02:16:26[Saint]My alternate suggestions are multiple, from the "ancient and/or expensive and/or plain impossible to acquire" series we have:
02:16:26[Saint]Archos Jukebox/Ondio/Recorder
02:16:26DBUGEnqueued KICK [Saint]
02:16:26[Saint]iRiver H3*
02:16:26[Saint]Gigabeat F/S/X
02:17:03[Saint]From the "just plain expensive as fuck" series we have:
02:17:32[Saint]iBasso DX90
02:17:32[Saint]HifiMan HM60* and HM801
02:19:18[Saint]Personally, I think the DX90 is a fucking nice player and I use mine fairly regularly.
02:19:48BilgusI saw where you had said the pi zero needed a fuckton of ancillary hardware to be worth anything and that is the same conclusion I came to researching it not to mention it won't be 'small' anymore
02:20:01[Saint]It is foolishly expensive, but well engineered and engineered from largely available or readily interchangeable internals.
02:20:16[Saint]Bilgus: right
02:20:48[Saint]I tried to make it work but you have to bolt on so much crap to it to get it to be even vaguely functional it isn't even funny.
02:21:43Bilgus$400 for 8gb and 8hr battery life damn
02:22:05shrizzaRockboxable that DX90?
02:22:45Bilgusby user replacable battery does that mean swap on the go?
02:24:04shrizzaDamn two microsd slots?
02:24:11[Saint]you're actually largely better off using any other raspi model and just removing the network controller (save a few hundred mA), and removing the Ethernet port and the block of four USB A ports in favor of replacing the USB jack with just two micro USB ports, and de-mounting (and optionally re-tinning) the GPIO header.
02:24:37[Saint]Then you get something that's about the same form factor as a full size iPod and can carry a decent LCD on it.
02:24:48Bilguswhat about sound though
02:24:55[Saint]I have been working on and off on making something like this for quite some time now.
02:25:17BilgusI'd be willing to do it as long as it sounds good
02:26:15[Saint]Bilgus: If you were willing to sacrifice another ~10mm in thickness (I know it's a lot..) you could do some software fuckery to flip the GPIO ports around a bit and then mount something like one of the many HiFiBerry Raspi DAC options to it.
02:26:33[Saint]I have a HiFiBerry Digi+ and a couple of others myself.
02:27:06[Saint]FOr just pissing around as an SDL Rockbox player I don't really care about the thickness /that/ much though.
02:27:59BilgusI'd be willing to roll my own board with some other stuff on it to save half that
02:28:06[Saint]So I kept the GPIO header on the board, but I removed the ethernet jack and the network controller of a raspi 3, and swapped the 4-port USB header for a 2-port USB header.
02:28:30 Quit paulk-collins (Quit: Leaving)
02:29:14[Saint]It has the HiFiBerry Digi+ DAC on it, and a tiny little RTC module sandwiched between the DAC and the Pi board.
02:29:41Bilgus-> community
02:34:44 Quit munch (Excess Flood)
02:36:49 Join munch [0] (pls@gateway/shell/elitebnc/x-akjpnixjhlnitmeo)
02:39:55 Join PurlingNayuki [0] (~Thunderbi@2001:da8:215:4ff:a9df:48fa:8d64:6153)
02:45:25 Quit alexweissman (Remote host closed the connection)
02:46:16 Quit PurlingNayuki (Ping timeout: 245 seconds)
02:58:42 Join Saratoga [0] (47e27552@gateway/web/freenode/ip.71.226.117.82)
02:59:56SaratogaBilgus_ph: it's a weird nand with integrated SD controller on package, they apparently made up to 16 GB versions and they're in tons of stuff, but no data sheet and I haven't seen them for sale individually
03:00
03:00:16SaratogaIt's tsop so in theory it could be soldered
03:00:48SaratogaBut without a data sheet or even pinout it's hard to find a compatible part
03:01:55[Saint]Yeah I'll bet.
03:03:07 Quit shamus (Quit: chaos reigns within reflect repent and reboot order shall return)
03:03:58 Join idonob [0] (~Owner@static-173-212-139-201.ptr.terago.net)
03:06:33 Quit Senj_ (Ping timeout: 268 seconds)
03:08:15Bilgusthat kinda sucks Saratoga
03:12:20 Quit idonob (Quit: the thing broke :()
03:12:38 Join idonob [0] (~Owner@static-173-212-139-201.ptr.terago.net)
03:13:57 Join doppler [0] (~doppler@unaffiliated/doppler)
03:16:57 Quit ZincAlloy (Quit: Leaving.)
03:48:40 Quit Corwin_3085 (Quit: Page closed)
03:54:37***Saving seen data "./dancer.seen"
03:55:46 Join alexweissman [0] (~alexweiss@2601:143:8001:e5f1:f975:f900:d706:b80e)
04:00
04:00:28 Quit alexweissman (Ping timeout: 245 seconds)
04:04:51 Quit aptzero (Quit: Leaving.)
04:06:50 Quit idonob (Ping timeout: 256 seconds)
04:09:45 Join idonob [0] (~Owner@static-173-212-139-201.ptr.terago.net)
04:28:24 Join naleo [0] (~naleo@unaffiliated/naleo)
04:36:47 Join alexweissman [0] (~alexweiss@2601:143:8001:e5f1:cdb6:43:642:4df2)
04:43:41 Quit alexweissman (Remote host closed the connection)
05:00
05:07:25 Quit Saratoga (Ping timeout: 260 seconds)
05:09:52 Join alexweissman [0] (~alexweiss@2601:143:8001:e5f1:f0c6:958a:87f4:8cca)
05:11:38 Quit alexweissman (Remote host closed the connection)
05:24:51 Join treaki__ [0] (~treaki@p5B11CBBC.dip0.t-ipconnect.de)
05:29:01 Quit treaki_ (Ping timeout: 268 seconds)
05:33:36 Quit naleo (Remote host closed the connection)
05:36:12 Join PurlingNayuki [0] (~Thunderbi@2001:da8:215:4ff:b13d:1daa:8560:633d)
05:40:28 Quit PurlingNayuki (Ping timeout: 245 seconds)
05:42:21 Join edhelas [0] (~edhelas@145.133.43.230)
05:54:40***Saving seen data "./dancer.seen"
06:00
06:09:56 Quit edhelas (Ping timeout: 248 seconds)
06:58:53 Quit [7] (Ping timeout: 258 seconds)
06:59:11 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven)
07:00
07:01:57 Join alexweissman [0] (~alexweiss@pool-108-51-84-48.washdc.fios.verizon.net)
07:05:47 Join edhelas [0] (~edhelas@149-210-220-39.colo.transip.net)
07:19:27 Quit edhelas (Quit: Leaving.)
07:35:00 Join PurlingNayuki [0] (~Thunderbi@2001:da8:215:4ff:49e1:6b68:33a8:7177)
07:39:13 Quit PurlingNayuki (Ping timeout: 245 seconds)
07:52:33 Quit alexweissman (Remote host closed the connection)
07:54:41***Saving seen data "./dancer.seen"
08:00
08:24:28 Join parchd [0] (~parchd@unaffiliated/parchd)
08:27:34 Join ender` [0] (krneki@foo.eternallybored.org)
09:00
09:03:11 Join alexweissman [0] (~alexweiss@pool-108-51-84-48.washdc.fios.verizon.net)
09:07:49 Quit alexweissman (Ping timeout: 264 seconds)
09:54:45***Saving seen data "./dancer.seen"
10:00
10:08:59 Quit idonob (Ping timeout: 268 seconds)
10:19:11 Quit krnlyng (Ping timeout: 252 seconds)
10:34:38 Join krnlyng [0] (~liar@178.114.23.167.wireless.dyn.drei.com)
10:35:50 Join johnb2 [0] (~johnb2@p5B296410.dip0.t-ipconnect.de)
10:36:51johnb2Bilgus: I grabbed the latest version and will test during the coming days.
10:43:48 Join paulk-aldrin [0] (~paulk@armstrong.paulk.fr)
10:58:00 Quit johnb2 (Ping timeout: 250 seconds)
11:00
11:06:44 Join johnb2 [0] (~johnb2@p5B296410.dip0.t-ipconnect.de)
11:48:54 Join cohokiller673 [0] (nightmarej@c-24-22-103-176.hsd1.wa.comcast.net)
11:49:31 Quit cohokiller673 (Client Quit)
11:49:39 Join cohokiller673 [0] (cohokiller@c-24-22-103-176.hsd1.wa.comcast.net)
11:53:05 Quit fIorz_ (Ping timeout: 246 seconds)
11:54:03 Join skapazzo [0] (~skapazzo@151.9.205.1)
11:54:49***Saving seen data "./dancer.seen"
12:00
12:09:48 Join PurlingNayuki [0] (~Thunderbi@2001:da8:215:4ff:7d64:9ee3:a41a:5e0f)
12:14:12 Quit PurlingNayuki (Ping timeout: 245 seconds)
12:24:47 Join lebellium_z3c [0] (~AndChat73@80.215.135.240)
12:25:40 Join rela_ [0] (~x@p200300764D68AA00A0B011247A05BFD0.dip0.t-ipconnect.de)
12:28:52 Quit rela (Ping timeout: 260 seconds)
12:33:40 Join robertd1 [0] (~root@201.242.214.237)
12:34:39 Quit robertd1 (Client Quit)
12:36:47 Quit parchd (Ping timeout: 250 seconds)
12:38:38 Join robertd1 [0] (~root@201.242.214.237)
12:40:04 Quit johnb2 (Ping timeout: 268 seconds)
12:43:25 Join johnb2 [0] (~johnb2@p5B296410.dip0.t-ipconnect.de)
12:52:51 Quit lebellium_z3c (Quit: Bye)
12:53:14 Join lebellium_z3c [0] (~AndChat73@ren77-h01-176-151-188-9.dsl.sta.abo.bbox.fr)
12:54:20 Join AndChat|736049 [0] (~AndChat73@80.215.135.240)
12:57:48 Quit lebellium_z3c (Ping timeout: 260 seconds)
12:58:27 Quit johnb2 (Ping timeout: 250 seconds)
12:58:35 Join johnb2 [0] (~johnb2@p5B296410.dip0.t-ipconnect.de)
13:00
13:04:10 Quit AndChat|736049 (Quit: Bye)
13:05:32 Join lebellium [0] (~chatzilla@ren77-h01-176-151-188-9.dsl.sta.abo.bbox.fr)
13:05:58 Quit johnb2 (Ping timeout: 268 seconds)
13:10:07 Quit [Saint] (Remote host closed the connection)
13:11:44 Join aptzero [0] (~Adium@96-95-20-86-static.hfc.comcastbusiness.net)
13:11:55 Join [Saint] [0] (~sinner@rockbox/staff/saint)
13:15:19 Quit [Saint] (Read error: Connection reset by peer)
13:17:31 Join [Saint] [0] (~sinner@rockbox/staff/saint)
13:20:01 Quit aptzero (Ping timeout: 265 seconds)
13:20:25 Join johnb2 [0] (~johnb2@p5B296410.dip0.t-ipconnect.de)
13:36:32 Join parchd [0] (~parchd@unaffiliated/parchd)
13:41:23 Quit johnb2 (Quit: Nettalk6 - www.ntalk.de)
13:54:51***Saving seen data "./dancer.seen"
13:58:12 Quit [Saint] (Ping timeout: 248 seconds)
14:00
14:04:32 Join [Saint] [0] (~sinner@rockbox/staff/saint)
14:27:12 Quit [Saint] (Read error: Connection reset by peer)
14:27:27 Join [Saint] [0] (~sinner@rockbox/staff/saint)
14:34:20 Join ZincAlloy [0] (~Adium@2a02:8108:8b80:1700:5534:931a:51c6:78c9)
15:00
15:05:06 Join xcfw [0] (~xcfw@147.30.19.231)
15:05:08xcfwhi
15:05:58xcfwI have an issue with my clip+, it's look like bricked, and when I'm connecting it to PC it shows as a disk with 30.6 MB which need to be formatted
15:06:18xcfwIs there anybodu who can help me to unbrick?
15:08:37 Quit rela_ (Quit: Leaving)
15:08:53 Join rela [0] (~x@pdpc/supporter/active/rela)
15:25:36BilgusI think that means the flash has died no expert though, someone with more info will be along but you might try this http://www.cgsecurity.org/wiki/TestDisk
15:26:15Bilgusxcfw: also I don't think windows will format successfully
15:29:10xcfwI have completely read the unbrick manuals, but afraid, that I could do something less dangerous to the sansa I love very much
15:32:10 Join JanC_ [0] (~janc@lugwv/member/JanC)
15:32:54xcfwBilgus: big thanks
15:33:25 Quit JanC (Killed (niven.freenode.net (Nickname regained by services)))
15:33:25 Nick JanC_ is now known as JanC (~janc@lugwv/member/JanC)
15:36:14xcfwtestdisk is asking for patiotion type, could you indicate a proper for sansa clip+ 8G internal memory?
15:38:31xcfwI have chosen GPT type
15:54:54***Saving seen data "./dancer.seen"
16:00
16:00:01 Join fs-bluebot_ [0] (~fs-bluebo@xd9beb5f0.dyn.telefonica.de)
16:01:55 Quit fs-bluebot (Ping timeout: 248 seconds)
16:02:16 Quit bluebrother (Ping timeout: 246 seconds)
16:04:06 Join bluebrother [0] (~dom@rockbox/developer/bluebrother)
16:05:13BilgusI wanna say it is fat 32 but ill check
16:08:27Bilgusyep fat 32
16:09:04gevaertspartition table type will be mbr, not gpt
16:09:19gevaertsThat's irrelevant for the 30MB thing though...
16:10:16xcfwgevaerts do you know the way peopel went, when they meet this issue, according to the logs of this ch there was succesiful stories
16:13:22Bilguswhat did TD show as your media size when you selected the disk?
16:14:04 Join PurlingNayuki [0] (~Thunderbi@114.255.40.10)
16:14:48xcfwCHS 3 255 63 - sector size=512
16:15:19 Quit PurlingNayuki (Read error: Connection reset by peer)
16:15:21Bilgusbtw my clip show CHS of 478/255/63 Sector size = 512
16:15:40 Join PurlingNayuki [0] (~Thunderbi@114.255.40.10)
16:16:24 Join Horrorca1 [0] (~unknown@sol-vpnnode.sotecware.net)
16:17:01Bilgusbut this is a 4gb though so i think yours should be 2x the cylinders
16:17:48xcfwthat is the case, there is a big chance that flash memory corrupted, but I hope to restore it with something like hp drive key boot utility, or maybe somebody from here could help me and show the path
16:17:57Bilgusunder the menu geometry you should be able to force it and then plug/unplug and run TD again
16:19:02BilgusIve successfully used TD to recover flash drives with this issue never had the need on a clip+ though
16:21:21Bilgusthere is a 50/50 chance the data is still intact
16:22:09xcfwdo I need to write MBR code?
16:23:47BilgusI don't remember try without and try with if it doesn't work
16:32:37xcfwis there any hidden partitions, or could bad memory stop sansa booting? Is there any firmware specific partition on a flash? I mean what if I will delete all the partitions data, then try to create new fat32 partition and then mkfs to this flash?
16:33:03xcfwcan I brick more my bricked device and win a double brick sansa?
16:35:16BilgusI've tried low level formatting ( in the loosest sense of the term) the internal memory on the sansa and it didn't hurt it a bit but there isn't really enough info about this problem for me and I suspect anyone else to tell you definitively..
16:36:18Bilgusnot to mention is it because the original fw is corrupt or is it that the disk is in some way and the OF is just shitting itself
16:38:40gevaertsxcfw: all I know is https://www.rockbox.org/wiki/SansaAMSUnbrick
16:38:49gevaertsFormatting that is almost certainly a mistake
16:39:29BilgusI imagine you can probably move the partition boundaries past the bad areas if you can get in and find them
16:40:19gevaertsForget partitions. This is a recovery mode, not some part of the actual storage
16:41:38gevaertsTrying to treat it as a disk and putting partition tables on it or formatting it is a good way to make sure it won't be recoverable (if it still is, which I doubt. I don't remember any actual verified success stories...)
16:41:43BilgusI don't think I'd try screwing with shorting the nand till you have exhausted every other option
16:42:44gevaertsWhat other options are there?
16:43:58CtcpIgnored 1 channel CTCP requests in 0 seconds at the last flood
16:43:58*gevaerts believes that all cases of seeing 4MB or 32MB "disks" are caused by failed hardware
16:44:00BilgusIt already has partition tables on it I can't see adding the right sizes back would hurt it but hey let him try the recovery mode and if it still works he can try everything else no worries
16:44:31gevaertsBilgus: what you're seeing in this sort of case is *not* the flash
16:44:56gevaertsIt's interpreted by the recovery firmware, so yes, putting the wrong stuff there *can* hurt
16:45:03Bilguslike I said I'm no expert with the clip+ AFAICT is it uses some funky SW disk control
16:45:49Bilgusor should I say FW disk control
16:45:55gevaertsWhat does that mean?
16:47:05Bilgusas in not hardware but instead in the firmware
16:47:20gevaertsThe clips all use an SD interface on the flash
16:47:44Bilgusthough I suppose it could be said every flash based storage does the same
16:50:06BilgusI say go for it and try 'recovery mode' Its not going to work any worse after
16:55:17Bilgusgevaerts: what do those pins actually map to the nand enable line?
16:55:25gevaertsNo idea
16:55:36*gevaerts isn't an AMS sansa expert at all
16:56:35gevaertsAll I know is that with recovery modes, just trying something and assuming it can't hurt tends to be destructive
16:58:05BilgusIdk i've had pretty good success with start with the least invasive and move on to the more desperate even resorted to shorting the nand 2x in the last 10 years
16:58:48 Join alexweissman [0] (~alexweiss@pool-108-51-84-48.washdc.fios.verizon.net)
16:59:03gevaertsTrue, but knowing how invasive something is can be tricky
17:00
17:00:31BilgusWell if we are dealing with a reserved area what If he took a good image and copied it over to his
17:01:32 Quit parchd (Ping timeout: 268 seconds)
17:03:45gevaertsI'm not sure we actually know what the 32MB thing is. It seems likely that it's a RAM image
17:04:17gevaertshmm, no, probably not...
17:07:31xcfwok now I know more
17:07:51Bilgusbeing that TD showed 3 cylinders instead of the 956 I suspect should be showing it sounds a lot like a corrupted drive
17:08:07xcfwfirst - I can connect sansa in MSC mode according to the sandisk support pages, just pressing the central button while plugging it
17:09:13xcfwsecond, after continously plugging and unplugging the device I saw a rockbox started and working, then I turned device off and tryed to restart - no result (happyness for a minute - very sad)
17:10:26xcfwI have a thought that sansa is in recover mode, so I am on the way to try to dd new image onto it
17:10:51Bilgushmm if you can get into RB that sounds promising any way to boot from the card directly gevaerts?
17:11:58gevaertsNot without a modified bootloader, which you almost certainly won't be able to install with the player in this state, and which won't load most of the time anyway
17:12:37gevaertsWhat you're saying sounds to me like probably a bad contact somewhere
17:13:08gevaertsi.e. if you hold it *just* right it can read the flash, otherwise it can't
17:13:54gevaertsNo amount of writing firmware to it is going to fix that
17:17:01 Join johnb3 [0] (~johnb3@p5B296410.dip0.t-ipconnect.de)
17:18:12Bilguswell it is RoHS compliant which isn't exactly known for being great maybe barring all else try reflowing the damn thing
17:19:29Bilgusill bbiab and investigate a bit more xcfw let us know how it goes
17:19:41johnb3Regarding booting from SD: Mihael (+Saratoga ?) had provided a modified bootloader respectively the patch for clip+ and fuzev2. This one boots from SD if the internal storage cannot be mounted. I can upload it if you want me to.
17:20:14xcfwit's 4 year old player and I have spent best 4 years of my life with it, that's why I hope for best so much...
17:20:47johnb3Of course you have to be able to flash the bootloader ...
17:21:00xcfwwhen I try to ceonnect the player in MSC mode, then windows says that it's uknown device =(
17:21:16 Quit johnb3 (Client Quit)
17:21:57 Join dfkt [0] (~dfkt@unaffiliated/dfkt)
17:22:11xcfwcould you indicate is the pressing of central button while connecting sansa to PC will enable recovery mode? I mean is MSC and recovery is the same?
17:26:17 Quit xcfw ()
17:26:25 Join xcfw [0] (~xcfw@147.30.19.231)
17:27:26 Quit xcfw (Client Quit)
17:29:32 Join Saratoga [0] (47e27552@gateway/web/freenode/ip.71.226.117.82)
17:29:50SaratogaMsc is the normal disk mode
17:30:37 Quit PurlingNayuki (Ping timeout: 258 seconds)
17:30:55SaratogaThe problem with a bootloader to boot from the SD card is that the bootloader is stored on the internal memory so it at least has to working well enough to read the bootloader
17:31:15SaratogaIf it's dead there is no bootloader
17:45:31 Join Senj_ [0] (~Senji@85.187.103.250)
17:54:56***Saving seen data "./dancer.seen"
17:55:03 Quit alexweissman (Remote host closed the connection)
17:59:06Guest32488fwiw, it's not uncommon with dying mmc that the first few k are still usable (if it's spotted with random errors rather than dying all at once)
18:00
18:00:11BilgusI do wonder if the sansa have a reserve area to replace bad blocks
18:12:59 Join alexweissman [0] (~alexweiss@pool-108-51-84-48.washdc.fios.verizon.net)
18:32:53 Join xcfw [0] (~xcfw@147.30.19.231)
18:32:58xcfwhi2all
18:33:11xcfwI have loaded sansa OF
18:33:38xcfwmy problem is due to some contact issue, which I need to find
18:34:18xcfwI have disassembled case, then put much ethanol on the player and then dryed by fan
18:34:25xcfwnow it seems working
18:35:23xcfwso is there any advice what i need to do now for loading the os from tf card instead of internal memory, I mean is there a way to use my sansa without internal memory at all
18:36:01xcfwsomebody told me about the forked bootloader, with external load of RB
18:42:19 Quit Bilgus (Ping timeout: 260 seconds)
18:42:55 Join Bilgus [0] (ae6611d9@gateway/web/freenode/ip.174.102.17.217)
18:51:27xcfwafter turning off the rockbox and reloading into OF and then operating with flash somewhere in 15 minutes it stuck and then I had to turn off and try to restart the player, now it's look like brick again
19:00
19:04:52Bilgusdid you try the recovery mode
19:05:08Bilgus(shorting out the two contacts?)
19:10:23 Join Bilgus_ [0] (ae6611d9@gateway/web/freenode/ip.174.102.17.217)
19:12:04 Quit Bilgus (Ping timeout: 260 seconds)
19:22:48xcfwno
19:23:28xcfwthere is a big chance that my HW is somehow wrong
19:26:33Bilgus_well once you've exhausted all other options let me know and we will try forcing it
19:49:23xcfwbut what about accidental load of the rockbox does anybody have any thoughts?
19:54:59***Saving seen data "./dancer.seen"
19:55:25 Quit alexweissman (Remote host closed the connection)
19:59:36 Join naleo [0] (~naleo@unaffiliated/naleo)
20:00
20:08:45 Quit Bilgus_ (Quit: Page closed)
20:11:38 Join Bilgus [0] (ae6611d9@gateway/web/freenode/ip.174.102.17.217)
20:21:55BilgusI just dumped the image on my clip+ size of file was 31.5 MB (31,457,280 bytes)
20:22:15 Nick Guest32488 is now known as alexbobp (~alex@testificate.xen.prgmr.com)
20:26:55BilgusI realize that is the size of the file that I specified to dump but pretty interesting that it is really close to size xcfw has on his
20:28:50 Join PurlingNayuki [0] (~Thunderbi@114.255.40.10)
20:33:01 Quit PurlingNayuki (Ping timeout: 250 seconds)
20:35:41 Join ulmutul [0] (~chatzilla@x4d09a77a.dyn.telefonica.de)
21:00
21:07:59 Join alexweissman [0] (~alexweiss@pool-108-51-84-48.washdc.fios.verizon.net)
21:08:25ulmutulI'd like to push some patches in the next days. Can someone please review the following:
21:08:26ulmutulg#1404 g#1405 g#1406 g#1407
21:08:32fs-bluebot_3Gerrit review #1404 at http://gerrit.rockbox.org/r/1404 : 3Midi Player: give button actions meaningful names by Sebastian Leonhardt
21:08:32fs-bluebot_3Gerrit review #1405 at http://gerrit.rockbox.org/r/1405 : 3Midi Player: fix playback of buffer remains when seeking by Sebastian Leonhardt
21:08:33fs-bluebot_3Gerrit review #1406 at http://gerrit.rockbox.org/r/1406 : 3Midi Player: fix premature stopping of audio buffer playback by Sebastian Leonhardt
21:08:34DBUGEnqueued KICK fs-bluebot_
21:08:34fs-bluebot_3Gerrit review #1407 at http://gerrit.rockbox.org/r/1407 : 3Midiplay: only boost cpu in sensible code parts by Sebastian Leonhardt
21:12:27 Quit alexweissman (Ping timeout: 250 seconds)
21:17:49gevaertsulmutul: I hadn't noticed the octave-per-line pattern, to be honest
21:18:04gevaertsI agree that that probably trumps the 80 characters per line rule
21:18:39CtcpIgnored 1 channel CTCP requests in 0 seconds at the last flood
21:18:39*gevaerts now thinks it should be properly formatted as a table
21:30:10ulmutulAnd also g#1291 and g#1292
21:30:12fs-bluebot_3Gerrit review #1291 at http://gerrit.rockbox.org/r/1291 : 3pacbox: clean-up screen size code by Sebastian Leonhardt
21:30:12fs-bluebot_3Gerrit review #1292 at http://gerrit.rockbox.org/r/1292 : 3pacbox for small screens, up to 75x96 by Sebastian Leonhardt
21:43:08gevaertsulmutul: feel free to push g#489 as well if you feel like it (or make more adjustments to it...). I'm not going to push it now to avoid merge conflicts with your other changes, but you obviously don't have that problem :)
21:43:10fs-bluebot_3Gerrit review #489 at http://gerrit.rockbox.org/r/489 : 3midi: Recalculate (and rename) the note frequency table. by Frank Gevaerts
21:45:49ulmutulOk, I'll do :)
21:50:46 Part robertd1
21:55:02***Saving seen data "./dancer.seen"
22:00
22:02:21 Join hoshi [0] (~hoshi@acgd185.neoplus.adsl.tpnet.pl)
22:02:30hoshiHi pamaury!
22:02:37hoshiHow nwz progress is going?
22:05:18lebelliumpamaury is not here as you can see
22:09:47 Join JanC_ [0] (~janc@lugwv/member/JanC)
22:10:57 Quit JanC (Ping timeout: 250 seconds)
22:11:02 Nick JanC_ is now known as JanC (~janc@lugwv/member/JanC)
22:11:07Bilgusxcfw what OS are you using Windows or Linux or which are you more comfortable in if you have both
22:16:50xcfwboth, arch, gentoo and win7x64
22:17:51 Quit xcfw (Read error: Connection reset by peer)
22:30:21 Join PurlingNayuki [0] (~Thunderbi@114.255.40.10)
22:34:48 Quit PurlingNayuki (Ping timeout: 264 seconds)
22:37:00 Join parchd [0] (~parchd@unaffiliated/parchd)
22:51:31Bilguswell anyways xcfw if you ever make it back could you dd the drive and post the file somewhere or use a disk hex editor and paste the results somewhere on win HxD hex editor will allow you to open a disk (https://mh-nexus.de/en/hxd/), and on Linux active @ disk editor will allow you to open disks (http://disk-editor.org/)
23:00
23:10:06 Quit paulk-aldrin (Remote host closed the connection)
23:16:32 Quit amiconn (Quit: No Ping reply in 64 seconds.)
23:16:41 Join amiconn [0] (~amiconn@rockbox/developer/amiconn)
23:17:30 Join JanC_ [0] (~janc@lugwv/member/JanC)
23:18:40 Quit hoshi (Quit: Leaving...)
23:18:43 Quit Rower (Write error: Broken pipe)
23:18:44 Quit JanC (Remote host closed the connection)
23:18:44 Nick JanC_ is now known as JanC (~janc@lugwv/member/JanC)
23:19:14 Join Rower [0] (husvagn@d83-183-134-99.cust.tele2.se)
23:19:20 Quit puckipedia (Excess Flood)
23:19:38 Join puckipedia [0] (puck@puckipedia.com)
23:20:49 Quit parchd (Ping timeout: 246 seconds)
23:25:58 Join paulk-collins [0] (~paulk@armstrong.paulk.fr)
23:40:40 Quit ZincAlloy (Quit: Leaving.)
23:46:39 Quit skapazzo (Quit: leaving)
23:55:03***Saving seen data "./dancer.seen"

Previous day | Next day