| 01:02.57 | *** join/#maemo robinak (~quassel@unaffilated/robink) |
| 01:12.55 | *** join/#maemo Vajb (~Vajb@85-76-48-184-nat.elisa-mobile.fi) |
| 01:19.11 | *** join/#maemo sledges (~sleleiva@unaffiliated/sledgeas) |
| 01:52.43 | *** join/#maemo RzR (~RzR@82.236.136.171) |
| 02:11.24 | *** join/#maemo lobito (~lobito@unaffiliated/lobito) |
| 02:17.44 | *** join/#maemo cyphase (~cyphase@unaffiliated/cyphase) |
| 02:27.36 | *** part/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net) |
| 02:29.21 | *** join/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net) |
| 03:37.35 | *** part/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net) |
| 03:38.40 | *** join/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net) |
| 03:47.47 | *** join/#maemo DarioAlejandro (~root@cpe-67-10-7-12.rgv.res.rr.com) |
| 03:50.51 | *** join/#maemo Oksana (~Wikiwide@Maemo/community/ex-council/Wikiwide) |
| 03:53.41 | *** join/#maemo jon_y (~enforcer@2001:e68:4074:4857:f64d:30ff:fe63:5a5a) |
| 04:01.09 | *** part/#maemo DarioAlejandro (~root@cpe-67-10-7-12.rgv.res.rr.com) |
| 04:01.49 | *** join/#maemo lxp (~lxp@unaffiliated/lxp) |
| 04:03.20 | *** join/#maemo DarioAlejandro (~root@cpe-67-10-7-12.rgv.res.rr.com) |
| 05:05.58 | *** join/#maemo cebreidian (U2FsdGVkX1@ma.sdf.org) |
| 05:10.12 | *** join/#maemo ketas- (~ketas@200-62-46-176.dyn.estpak.ee) |
| 05:14.32 | *** join/#maemo jonwil (~jonwil@27-33-80-219.tpgi.com.au) |
| 05:23.34 | *** join/#maemo DrCode (~DrCode@5.28.134.3) |
| 05:30.57 | *** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 05:49.45 | *** join/#maemo lobito (~lobito@unaffiliated/lobito) |
| 06:40.29 | *** join/#maemo arcean (~arcean@131.228.32.166) |
| 06:44.20 | *** join/#maemo spiiroin (~spiiroin@2001:998:2a:dead:30ce:de3e:1fc7:1a02) |
| 06:45.18 | *** join/#maemo dafox (~dafox@92.69.228.46) |
| 07:02.58 | *** part/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net) |
| 08:02.55 | *** join/#maemo zGrr (~Grr@185.13.106.211) |
| 08:05.23 | zGrr | moin :) |
| 08:17.20 | *** join/#maemo chainsawbike (~chainsawb@unaffiliated/chainsawbike) |
| 08:23.57 | *** join/#maemo Michael_a320 (d31f1b25@gateway/web/freenode/ip.211.31.27.37) |
| 08:26.46 | *** join/#maemo troulouliou_div2 (~troulouli@unaffiliated/troulouliou-div2/x-0271439) |
| 08:39.09 | *** join/#maemo geaaru (~geaaru@host170-152-static.43-88-b.business.telecomitalia.it) |
| 08:50.18 | *** join/#maemo M4rtinK (~M4rtinK@ip-78-45-144-165.net.upcbroadband.cz) |
| 09:20.08 | *** join/#maemo Pali_ (~pali@Maemo/community/contributor/Pali) |
| 09:38.08 | *** join/#maemo jskarvad (jskarvad@nat/redhat/x-fpiiavrdwmdytmyu) |
| 09:38.08 | *** join/#maemo jskarvad (jskarvad@redhat/jskarvad) |
| 09:45.04 | *** join/#maemo Kabouik_ (~kabouik@147.99.218.243) |
| 10:12.27 | *** join/#maemo xorly (~xorly@193.85.203.185) |
| 10:40.55 | *** join/#maemo xorly (~xorly@193.85.203.185) |
| 11:48.21 | *** join/#maemo `0660 (olli@37.16.104.148) |
| 12:24.18 | *** join/#maemo lobito (~lobito@unaffiliated/lobito) |
| 12:28.17 | *** join/#maemo xorly (~xorly@193.85.203.185) |
| 12:33.47 | *** join/#maemo Oksanaa (~Wikiwide@Maemo/community/ex-council/Wikiwide) |
| 12:34.45 | Oksanaa | LEDs work now, for no visible reason. Which package is better, xiph-support or decoders-support? |
| 12:36.24 | KotCzarny | better for what? |
| 12:38.30 | Oksanaa | For tracking and decoding wide variety of audio and video files. So far, I have decoders-support installed, and flac and other audio gets tracked and played, while video gets tracked, but some of it gives "Media format not supported" errors. |
| 12:39.14 | KotCzarny | xiph obviously only means ogg/vorbis/theora |
| 12:39.41 | KotCzarny | i would bet that decoders-support has it ot relies on it |
| 12:40.40 | *** join/#maemo florian_kc (~fuchs@Maemo/community/contributor/florian) |
| 12:41.35 | *** join/#maemo xorly (~xorly@193.85.203.185) |
| 12:43.24 | Oksanaa | Decoders-support relies on ogg-support, which conflicts with xiph-support. And currently, an ogv with theora encoded video gives error video codec not supported error. |
| 12:44.15 | KotCzarny | because probably ogg-support doesnt have video codec support |
| 12:44.58 | KotCzarny | uninstall ogg-support and xiph-support, install decoders-support and see if it plays more formats? |
| 12:45.43 | Oksanaa | Decoders-support depends on ogg-support and is already installed. Ogg-support and xiph-support have identical dependencies. |
| 12:47.02 | Juesto | hey oksanaa |
| 12:47.10 | Juesto | Strange |
| 12:51.17 | *** join/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net) |
| 13:00.34 | Oksanaa | Installing xiph-support seems only to worsen the situation. |
| 13:02.59 | Juesto | Is ffmpeg available? |
| 13:04.35 | KotCzarny | old one |
| 13:04.57 | KotCzarny | i just compile my player with latest libav statically, less hassles |
| 13:08.06 | *** join/#maemo ketas (~ketas@0011-0000-0000-0000-35dc-8408-07d0-2001.dyn.estpak.ee) |
| 13:10.50 | Oksanaa | Installed back ogg-support, still not playing this theora.ogv video. Siberian hitch from Wikimedia Commons. |
| 13:11.02 | Juesto | OGV? |
| 13:11.03 | Juesto | uhm |
| 13:11.08 | Juesto | link of the file? |
| 13:11.14 | KotCzarny | ogg is a container, as in 'avi' |
| 13:11.20 | Juesto | yeah |
| 13:11.25 | KotCzarny | real codec is called vorbis for audio and theora for video |
| 13:11.26 | Juesto | i want to look at the file via media info |
| 13:11.47 | Juesto | oksanaa ^ |
| 13:20.54 | Oksanaa | https://upload.wikimedia.org/wikipedia/commons/transcoded/f/f1/Siberian_hitch.webm/Siberian_hitch.webm.480p.ogv |
| 13:26.18 | Juesto | Oksanaa: since it's transcoded, what about MP4 ? |
| 13:27.08 | Juesto | sigh |
| 13:27.10 | Juesto | its impossible |
| 13:27.12 | Oksanaa | Prefer open codecs |
| 13:27.18 | Juesto | webm or theora only |
| 13:27.27 | Juesto | Does maemo supprot webm? |
| 13:27.58 | Oksanaa | Webm stutters. Ogv is better. It did work before. |
| 13:28.31 | Juesto | vp8/vorbis |
| 13:28.36 | Juesto | Ouch |
| 13:28.45 | Juesto | Oksanaa: What changed? what broke? |
| 13:28.50 | Juesto | when it broke? |
| 13:30.46 | Oksanaa | No Idea. And installing gstreamer0.10-theora doesn't help. |
| 13:31.35 | Juesto | Do you remember what was installed when it was working? |
| 13:31.55 | KotCzarny | try to play it from command line via gstreamer |
| 13:32.08 | Juesto | KotCzarny: is custom compiled ffmpeg for maemo good? |
| 13:32.15 | Juesto | as in, how well your copy works |
| 13:32.39 | Juesto | it is stable enough for other people to use it? |
| 13:32.46 | KotCzarny | juesto: since my player is mainliny audio player, i only enable audio codecs |
| 13:32.53 | KotCzarny | *mainly |
| 13:32.59 | Juesto | Ah |
| 13:33.00 | KotCzarny | and it's stable |
| 13:33.02 | Juesto | well and video? |
| 13:33.11 | KotCzarny | for video i just call gstreamer |
| 13:33.35 | KotCzarny | not that i use it for video, but it was an easy code, so it's there |
| 13:33.43 | Juesto | Ah i see |
| 13:34.42 | KotCzarny | not to mention software decoding video on single core a9@600mhz isnt going to show fireworks |
| 13:35.08 | Juesto | Should she try 360p version? |
| 13:36.12 | *** join/#maemo xorly (~xorly@193.85.203.185) |
| 13:36.15 | KotCzarny | someone should write dsp optimized video codec for vp8/9 and theora, but that's hard even for people knowing assembly |
| 13:37.19 | Oksanaa | KotCzarny: gst-launch ffdemux_ogg /home/user/MyDocs/.videos/Siberian_hitch.webm.480p.ogv |
| 13:37.21 | Oksanaa | <PROTECTED> |
| 13:38.00 | KotCzarny | oksanaa: you can either check gst cheat sheets or try gst123 (i'm using it in oscp so you can grab it from there or compile your own) |
| 13:38.26 | KotCzarny | you have to add proper chains (in/decode/out) |
| 13:42.54 | Juesto | armel assembly specifically right? |
| 13:43.08 | KotCzarny | nope, dsp code |
| 13:43.13 | Juesto | Hm |
| 13:43.18 | Juesto | ah right |
| 13:43.40 | Juesto | isnt there something like mplayer or totem for maemo? |
| 13:43.47 | Juesto | for sapwood/hildon |
| 13:43.55 | KotCzarny | yes, but it uses software decoding |
| 13:43.59 | KotCzarny | ie. cpu |
| 13:44.09 | Juesto | any way to make it use gstreamer? |
| 13:44.20 | Juesto | as in, is CLI accelerated or not? |
| 13:44.48 | KotCzarny | gstreamer doesnt have many modern hw codecs |
| 13:45.32 | Juesto | sighs |
| 13:47.02 | L29Ah | damn n900 doesn't want to boot while being charged from my laptop again |
| 13:47.36 | Juesto | L29Ah: charge a bit then turn it on? |
| 13:47.44 | L29Ah | charging indication stops after a few seconds |
| 13:47.46 | Juesto | does it even charge? |
| 13:47.49 | Juesto | ouch |
| 13:47.50 | L29Ah | how do i tell? |
| 13:48.00 | Juesto | wait..? |
| 13:48.14 | KotCzarny | pulsing amber or green? |
| 13:48.17 | L29Ah | now the charging indication is locked on its maximum brightness |
| 13:48.19 | L29Ah | amber |
| 13:48.26 | KotCzarny | pulsing or constant? |
| 13:48.34 | L29Ah | used to be pulsing, now constant |
| 13:48.42 | KotCzarny | might not be charged at all |
| 13:48.45 | KotCzarny | ~flatbat |
| 13:48.49 | KotCzarny | ~ping |
| 13:48.49 | infobot | ~pong |
| 13:48.53 | Juesto | Rip |
| 13:48.55 | KotCzarny | hrm |
| 13:49.29 | KotCzarny | ~flatbatrecover |
| 13:49.29 | infobot | Remove battery for 1 minute. Insert battery. Plug powered ***NOKIA WALLCHARGER*** to device. Watch steady amber. Let sit and charge. Do NOT try to boot. After 30 min, you got either a) a booted up N900, b) flashing amber which means you can boot, c) steady amber shut off -> start over again with ~flatbatrecover while already searching for a new battery. CAVEAT! Only works when ~rootfs OK (no ~bootloop) |
| 13:49.30 | *** join/#maemo florian_kc (~fuchs@Maemo/community/contributor/florian) |
| 13:50.00 | L29Ah | hooked it into a dumb charger, see same behaviour |
| 13:50.15 | L29Ah | > steady amber |
| 13:50.17 | L29Ah | ok i guess |
| 13:50.22 | Juesto | Tried a proper charger? |
| 13:50.28 | Juesto | ah |
| 13:50.30 | Juesto | hm |
| 13:50.31 | L29Ah | dunno what's a "proper charger" |
| 13:50.41 | KotCzarny | proper charger == original nokia one |
| 13:50.50 | L29Ah | :D |
| 13:50.53 | Juesto | sometimes chargers have more power to charge faster |
| 13:50.55 | Juesto | Lol |
| 13:51.05 | Juesto | voltage* |
| 13:51.08 | Juesto | or whatever |
| 13:51.16 | L29Ah | i doubt n900 supports that |
| 13:51.18 | *** join/#maemo troulouliou_div2 (~troulouli@unaffiliated/troulouliou-div2/x-0271439) |
| 13:51.50 | L29Ah | i can just hook my liion charger wires to my 18650 block but i decided to have a try with usb stuff just in case |
| 13:52.17 | Juesto | be careful |
| 13:59.46 | *** join/#maemo spiiroin (~spiiroin@178-55-78-55.bb.dnainternet.fi) |
| 14:07.09 | joga | heh... I had problems with charging the n900 before from a powerbank using a certain cable... now I couldn't get it to charge anymore after many attempts, and I was outside home, so got the cheapest microusb cable I could find nearby and woo, no problems charging. It also feels a lot less loose than the previous cable so maybe it's just mechanical wear on the old cable or whatever |
| 14:12.30 | *** join/#maemo heroux (sandroco@gateway/shell/insomnia247/x-vtpdmukjdijqykol) |
| 14:20.59 | *** join/#maemo xorly (~xorly@193.85.203.185) |
| 15:18.41 | *** join/#maemo Sigyn (sigyn@freenode/utility-bot/sigyn) |
| 15:19.56 | *** join/#maemo eMHa (~mh@p200300738E17F800267703FFFE6CC360.dip0.t-ipconnect.de) |
| 15:22.20 | *** join/#maemo xorly (~xorly@193.85.203.185) |
| 15:47.38 | *** join/#maemo Vajb (~Vajb@85-76-164-136-nat.elisa-mobile.fi) |
| 16:21.34 | L29Ah | no it didn't charge |
| 16:21.37 | L29Ah | that bastard |
| 16:21.56 | L29Ah | reporting to be charging but not charging |
| 16:23.24 | doppler | :( |
| 16:35.12 | freemangordon | L29Ah: it is charging, but slowly, only 100 mA |
| 16:36.24 | freemangordon | (assuming it is still connected to your laptop USB port) |
| 16:36.53 | L29Ah | it got +10mV in 2h on a 4A*h battery |
| 16:37.05 | L29Ah | (3.40 to 3.41) |
| 16:37.36 | L29Ah | maybe it didn't even charge and it's the battery capacitance recovered from a current surges of starting up n900 |
| 16:37.39 | KotCzarny | maybe that low current isnt able to charge it? |
| 16:37.43 | freemangordon | looks normal for 100 mA charge current to me |
| 16:38.22 | freemangordon | L29Ah: just find 1A wall charger |
| 16:38.23 | L29Ah | 3.40 to 3.41 is like 1% |
| 16:38.44 | freemangordon | how did you measure that voltage? |
| 16:38.46 | L29Ah | i used a wall charger |
| 16:38.55 | L29Ah | probing the battery |
| 16:38.59 | freemangordon | is it 1A or 2.1 A? |
| 16:39.00 | L29Ah | with a multimeter |
| 16:39.17 | *** join/#maemo Oksanaa (~Wikiwide@Maemo/community/ex-council/Wikiwide) |
| 16:39.19 | L29Ah | 1A |
| 16:39.24 | freemangordon | hmm |
| 16:39.51 | freemangordon | could you check with your multimeter if there is a short between D+ and D- ? |
| 16:40.09 | L29Ah | switched to another cable, now it has charged for real |
| 16:40.13 | L29Ah | 3.55V |
| 16:40.24 | KotCzarny | do you have any charge 'doctor' to confirm any usage? |
| 16:40.28 | KotCzarny | hehe |
| 16:40.31 | KotCzarny | figures |
| 16:40.35 | KotCzarny | mark that other cable as bad |
| 16:40.41 | L29Ah | and the former cable works just fine for data |
| 16:41.00 | L29Ah | and it detects the charger somehow over it |
| 16:41.01 | L29Ah | WTF |
| 16:41.06 | L29Ah | what's so bad about the cable? |
| 16:41.13 | freemangordon | contacts? |
| 16:41.19 | KotCzarny | cheap, dumb? |
| 16:41.20 | freemangordon | might be weared |
| 16:41.37 | L29Ah | so they have like 3V worth of drop? |
| 16:42.15 | freemangordon | I doubt bq will wait for 3V drop before stopping the charging |
| 16:42.24 | L29Ah | what microusb cables should i buy from ebay btw? |
| 16:42.37 | KotCzarny | 24avg or less |
| 16:42.46 | L29Ah | they don't specify this as i see |
| 16:42.53 | KotCzarny | then dont buy those |
| 16:42.55 | freemangordon | L29Ah: you'd better buy charger, not cables |
| 16:43.04 | L29Ah | i don't need a charger |
| 16:43.09 | freemangordon | ok |
| 16:43.12 | L29Ah | i need a cable for emergency charging from my laptop |
| 16:43.24 | KotCzarny | then get good data cable |
| 16:43.30 | KotCzarny | 4 wires |
| 16:43.31 | L29Ah | i have a 4A LiIon charger for regular stuff |
| 16:43.31 | freemangordon | L29Ah: it doesn;t work like that |
| 16:43.49 | freemangordon | the most you got over USB is 500 mA |
| 16:43.57 | freemangordon | BUT |
| 16:44.01 | L29Ah | but i did the test to ensure i can charge it a bit in case i'm in a forest with my laptop and a cable |
| 16:44.08 | KotCzarny | fmg, some laptops are fine with much more than 500mA |
| 16:44.16 | freemangordon | you should have the OS booted, iirc, otherwise you got only 100 mA |
| 16:44.41 | freemangordon | KotCzarny: it is not what port can handle, it is what n900 will draw |
| 16:44.47 | freemangordon | *not about |
| 16:44.57 | KotCzarny | fmg, oh |
| 16:45.05 | L29Ah | can it be hacked so it draws 1A in every circumstance? |
| 16:45.24 | freemangordon | L29Ah: yye, you need to short-circuot D+ and D- |
| 16:45.27 | L29Ah | w/o messing with pcb |
| 16:45.30 | L29Ah | :( |
| 16:45.43 | freemangordon | you can rework the canle |
| 16:45.46 | freemangordon | *cable |
| 16:45.58 | L29Ah | i expected a software solution |
| 16:46.39 | L29Ah | i see that n900 boots the kernel even to start charging-blinking stuff |
| 16:46.39 | freemangordon | not sure, maybe there exists such a solution if you use bme replacement |
| 16:46.45 | freemangordon | yes |
| 16:46.49 | freemangordon | oh, well |
| 16:47.11 | freemangordon | NOLO supports charging as well, but iirc it draws 100 mA only |
| 16:47.20 | freemangordon | Pali_: ^^^ ? |
| 16:47.28 | freemangordon | an;t remember the details |
| 16:47.33 | freemangordon | *can't |
| 16:47.51 | Pali_ | DocScrutinizer05 ^ |
| 16:47.55 | freemangordon | :) |
| 17:20.03 | *** join/#maemo dafox (~dafox@92.69.224.179) |
| 17:25.41 | KotCzarny | https://wiki.maemo.org/Talk:Useful_Mobile_URLs |
| 17:25.46 | KotCzarny | spam detected |
| 17:26.09 | KotCzarny | anyone can clean it/block the user? |
| 17:26.18 | KotCzarny | xes? |
| 17:27.59 | KotCzarny | https://wiki.maemo.org/Talk:Task:Defining_maemo |
| 17:28.01 | KotCzarny | ugh |
| 17:28.56 | KotCzarny | quite a lot of spam in talk: |
| 17:29.13 | KotCzarny | all users are unregistered |
| 17:29.20 | sixwheeledbeast | KotCzarny: I'll look |
| 17:29.47 | KotCzarny | https://wiki.maemo.org/Talk:MaemoCommunity_eV |
| 17:29.49 | KotCzarny | etc |
| 17:30.10 | KotCzarny | for easy spotting click history or diffs |
| 17:30.23 | *** join/#maemo jskarvad (jskarvad@nat/redhat/x-slyhatiryvnxmlyx) |
| 17:30.23 | *** join/#maemo jskarvad (jskarvad@redhat/jskarvad) |
| 17:31.05 | KotCzarny | i wonder for how long it went |
| 17:31.43 | KotCzarny | maybe server admin can run some cleanup script (and block posting talk: entries containing links |
| 17:32.24 | xes | https://wiki.maemo.org/index.php?title=Special:RecentChanges&days=60&limit=500 |
| 17:32.39 | KotCzarny | xes, yeah, a lot |
| 17:33.09 | *** join/#maemo troulouliou_div2 (~troulouli@unaffiliated/troulouliou-div2/x-0271439) |
| 17:33.27 | xes | i will check the wiki's anti spam filter,maybe it's not exaclty aligned to the tmo one |
| 17:33.51 | KotCzarny | i think its because wiki allows anonymous posting in talk: pages |
| 17:34.06 | xes | (the tmo one has looonger memory for bad guys) |
| 17:37.20 | sixwheeledbeast | Ok fixed and bliacklisted IP's |
| 17:38.12 | xes | sixwheeledbeast: thanks |
| 17:38.29 | sixwheeledbeast | KotCzarny: Any others? I used to have the time to check for spam on a daily basis but unfortunately not any more. |
| 17:39.04 | sixwheeledbeast | Any spam on the wiki ping me I can sort it. |
| 17:39.08 | sixwheeledbeast | xes: np |
| 17:39.46 | KotCzarny | swb: check all anonymous (ip based) adds |
| 17:41.11 | KotCzarny | https://wiki.maemo.org/Talk:Community_SSU |
| 17:44.42 | sixwheeledbeast | KotCzarny: just done that, I can only check back 30 days and I have just blacklists and rolledback those. |
| 17:45.19 | KotCzarny | i cant get history older than 3 dec 2016 |
| 17:45.48 | sixwheeledbeast | ok 60 days |
| 17:46.32 | sixwheeledbeast | oh I can manually edit the days in the URL |
| 17:46.44 | KotCzarny | but i would advise someone to run some searches on anonymous adds in talk: pages |
| 17:48.05 | sixwheeledbeast | Yep 3 dec is as far back as I can search |
| 17:49.01 | KotCzarny | btw. wmo is missing favicon |
| 17:49.31 | KotCzarny | and favicons make links nicer in bookmarks ;) |
| 17:50.10 | KotCzarny | http://wiki.maemo.org/favicon.ico |
| 17:50.11 | KotCzarny | ;) |
| 17:50.59 | KotCzarny | but its referenced in wmo pages: <link rel="shortcut icon" href="/favicon.ico" /> |
| 17:51.56 | sixwheeledbeast | :nod: I already reported that but NFC what the answer was. |
| 17:52.17 | KotCzarny | just copy it from tmo ? |
| 17:52.31 | KotCzarny | maybe att white T over it to make it distinct |
| 17:52.37 | KotCzarny | *add |
| 18:30.49 | sixwheeledbeast | KotCzarny: should point to href="/skins/monobookmaemo2009/static/maemo_favicon.ico" |
| 19:13.23 | *** join/#maemo BCMM (~BCMM@unaffiliated/bcmm) |
| 19:54.21 | *** join/#maemo shentey (~shentey@x55b3250a.dyn.telefonica.de) |
| 19:55.04 | *** join/#maemo eMHa (~mh@p200300738E2AF700267703FFFE6CC360.dip0.t-ipconnect.de) |
| 19:59.10 | *** join/#maemo Juesto_ (~Zilla@rev190-105-167-002.pccp.net.ar) |
| 20:08.19 | *** join/#maemo ff_ (~ff_@bul88.neoplus.adsl.tpnet.pl) |
| 20:09.13 | ff_ | can n900 use all 90MB/s r/w speed of https://www.sandisk.com/home/memory-cards/microsd-cards/extremeplus-microsd ? |
| 20:09.49 | KotCzarny | nope. your target is a card with highest iops you can get, not sequential speed |
| 20:11.10 | ff_ | and the lowest access time? |
| 20:12.01 | KotCzarny | yes, but getting real (4k r/w) iops benchmarks is tricky |
| 20:12.52 | ff_ | some example? |
| 20:13.43 | ff_ | it's possible make block size bigger then 4k? |
| 20:15.04 | KotCzarny | most noname cards have iops in 0.1-1/s range |
| 20:15.30 | KotCzarny | some samsung evo +/pro manage to get ~100iops |
| 20:17.06 | *** join/#maemo Oksanaa (~Wikiwide@Maemo/community/ex-council/Wikiwide) |
| 20:40.36 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 21:10.22 | *** join/#maemo Vajb (~Vajb@85-76-75-117-nat.elisa-mobile.fi) |
| 21:12.04 | *** join/#maemo jskarvad (~jskarvad@ip4-83-240-109-95.cust.nbox.cz) |
| 21:12.04 | *** join/#maemo jskarvad (~jskarvad@redhat/jskarvad) |
| 21:26.55 | ff_ | you're right http://www.cameramemoryspeed.com/reviews/sd-cards/sandisk-extreme-plus-95-90-mbs-64gb-micro-sdxc-memory-card/ only 3MB/s random write, 700ish iops |
| 21:30.51 | ff_ | ssd are designed for much more iops https://news.samsung.com/global/samsung-introduces-worlds-first-universal-flash-storage-ufs-removable-memory-card-line-up-offering-up-to-256-gigabyte-gb-capacity 40000 iops, but that's not helpful for n900 |
| 21:35.09 | Juesto | Nice! |
| 21:52.49 | *** join/#maemo shentey (~shentey@x55b3250a.dyn.telefonica.de) |
| 22:05.47 | ff_ | with 35000 iops it could works like RAM, so, n900 with extremely expensive 32GB RAM/ROM :) |
| 22:05.58 | L29Ah | 23:15:04]<KotCzarny> most noname cards have iops in 0.1-1/s range |
| 22:05.58 | L29Ah | what |
| 22:29.55 | ff_ | I couldn't be surprised if Chinese people could produce something like that |
| 22:33.41 | ff_ | anyone know speed of microSD data bus in n900? |
| 22:34.07 | ff_ | maybe it's not worth the bother with fast microSD |
| 22:36.22 | Maxdamantus | I'm getting around 12 MB/s read. |
| 22:36.56 | Maxdamantus | I have a feeling that the maximum speed does kind of matter. |
| 22:37.18 | ff_ | what are specs of sd? |
| 22:37.30 | Maxdamantus | iirc I would only get around 4 MB/s on a lower-end Kingston microSD, which was rated at something like 30 MB/s. |
| 22:38.38 | ff_ | speed of read or write? |
| 22:38.45 | Maxdamantus | SanDisk 128GB Ultra® microSDXC⢠UHS-I Class 10 card |
| 22:39.52 | Maxdamantus | SD cards don't really have a particular speed. |
| 22:40.10 | Maxdamantus | It depends on things like how the controller has laid out the data. |
| 22:41.00 | ff_ | with it you get 12MB/s in n900? |
| 22:41.17 | Maxdamantus | Yes. |
| 22:41.22 | Maxdamantus | 236978176 bytes (237 MB) copied, 20.236 s, 11.7 MB/s |
| 22:41.23 | ff_ | and how with write? |
| 22:42.23 | Maxdamantus | write is trickier to test. |
| 22:43.08 | Maxdamantus | can try after remounting with -o sync, I guess. |
| 22:44.20 | ff_ | not pressure, I'm just curious |
| 22:45.23 | Maxdamantus | I'm getting 10.6 MB/s writing to ext4 mounted with -o sync using dd with conv=fsync on |
| 22:45.38 | Maxdamantus | (so that's to a filesystem, not just a block device) |
| 22:45.59 | Maxdamantus | though I'm only writing zeroes, dunno if the card does something special with that. |
| 22:46.54 | Maxdamantus | Well, I imagine the card should handle more than 10.6 MB/s anyway .. it'll at least be pushing that 10.6 MB/s in SDIO packets. |
| 22:47.07 | ff_ | I don't know also, thanks for real data with n900 |
| 22:47.43 | Maxdamantus | The sync options are also going to usually reduce overall throughput |
| 22:48.45 | ff_ | it seems that n900 has 10MB/s speed limit on sd bus |
| 22:48.53 | Maxdamantus | These speeds are all sequential btw, not random. |
| 22:50.27 | ff_ | random should be lower than this 10MB/s cameramemoryspeed.com/reviews/sd-cards/sandisk-extreme-plus-95-90-mbs-64gb-micro-sdxc-memory-card/ |
| 22:51.42 | ff_ | 9MB/s for read and 3MB/s for write if that benchmark is with the same class card |
| 22:55.11 | ff_ | microSDXC UHS-I U3, I'm not sure for that U3 symbol |
| 22:57.34 | *** join/#maemo Oksanaa (~Wikiwide@Maemo/community/ex-council/Wikiwide) |
| 23:34.33 | DocScrutinizer05 | a pty ff_ left. Was absolutely right it doesn't really make sense to bother, since databus is limited to 4bit buswidth * (iirc) 40MHz clockrate max, so 20MB/s |
| 23:35.08 | DocScrutinizer05 | *might* even be just 25MHz |
| 23:35.34 | Oksanaa | Question is, which cards actually work at maximum limit of the databus. |
| 23:38.07 | DocScrutinizer05 | all |
| 23:38.10 | DocScrutinizer05 | :-) |
| 23:38.36 | Maxdamantus | except for my Kingston one. |
| 23:39.21 | DocScrutinizer05 | it's a pretty ancient databus protocol. Recent Ultra card only work since they support legacy protocols, the OMAP3 doesn't support those new speeds |
| 23:39.57 | DocScrutinizer05 | UHS-I and UHS-II are not supported by OMAP3 |
| 23:40.43 | DocScrutinizer05 | for write, the real show stopper is page erase needed to rewrite a block with new data. It can take up to some 100s of MILLIseconds |
| 23:41.12 | DocScrutinizer05 | at very least 10ms |
| 23:41.19 | DocScrutinizer05 | per page erase |
| 23:42.20 | Oksanaa | Is it possible to have faster databus with OMAP3? And what is page erase, is it like going over the card with eraser to be sure that write to card goes well? |
| 23:43.31 | DocScrutinizer05 | yes @ #2 |
| 23:43.51 | DocScrutinizer05 | no @ #1, it's a physical interface that can't do any faster |
| 23:44.39 | DocScrutinizer05 | OMAP has a 4bit and a 8bit storage bus, both with same max clock frequency. In N900 the 8bit is for eMMC |
| 23:44.42 | Oksanaa | Like, would Neo900 be able to have faster databus than N900? |
| 23:44.47 | DocScrutinizer05 | no |
| 23:44.51 | DocScrutinizer05 | alas not |
| 23:45.36 | DocScrutinizer05 | that's also one killer argument why Neo900 must have eMC despite many people would prefer two uSD slots: eMMC supports 8bit |
| 23:46.05 | Oksanaa | About page erase: is it possible to do it beforehand, like use idle time to erase empty blocks on the card so that by the time a write is needed, card already has several blocks ready? |
| 23:46.26 | Maxdamantus | I imagine that's something the card will already do. |
| 23:46.26 | Oksanaa | uSD slot supports only 4bit? |
| 23:46.43 | Maxdamantus | Hosts don't interact with SD cards as flash devices. |
| 23:46.58 | Maxdamantus | That's all stuff that's handled by the computer inside the SD card. |
| 23:47.16 | Oksanaa | Maxdamantus: that would be neat, if it's implemented already. |
| 23:48.39 | *** join/#maemo ketas (~ketas@200-62-46-176.dyn.estpak.ee) |
| 23:49.23 | DocScrutinizer05 | (do it beforehand) that's how all slightly smarter cards work, as long as the OS supports TRUNCATE |
| 23:49.42 | Maxdamantus | TRUNCATE? Do you mean TRIM? |
| 23:50.14 | Maxdamantus | if so, that has nothing no do with SD cards. |
| 23:50.20 | DocScrutinizer05 | the card needs to know which blocks can get erased beforehand, even writing all zeroes to a whole page doesn't automatically tell card "this is no data, this is empty storage free to use" |
| 23:50.38 | Maxdamantus | well, that's not what SD cards typically do. |
| 23:51.01 | DocScrutinizer05 | uSd has only 4 bit data, yes. count the pins on your uSD card ;-) |
| 23:51.16 | DocScrutinizer05 | you need GND, VCC, clock r/w whatnot else |
| 23:51.34 | Maxdamantus | DocScrutinizer05: can you provide a link to some information about this magical "TRUNCATE" thing you're talking about? |
| 23:51.50 | Maxdamantus | or is this another case where you're just saying things about technologies you don't understandL |
| 23:55.21 | DocScrutinizer05 | Oksanaa: https://wiki.debian.org/SSDOptimization |
| 23:55.40 | Maxdamantus | We're talking about SD cards, not SSDs. |
| 23:55.57 | Maxdamantus | SD cards don't have TRIM (or "TRUNCATE" if you like making up names for things) |
| 23:56.17 | DocScrutinizer05 | basically all SSD rationale also applies to SD cards |
| 23:56.35 | Maxdamantus | SD is a completely different protocol. |
| 23:56.44 | Maxdamantus | and it doesn't have anything like TRIM in it. |
| 23:56.51 | DocScrutinizer05 | sorry, DISCARD, not TRUNCATE |
| 23:58.38 | Maxdamantus | apparently it's actually ERASE |