| 01:03.27 | *** join/#maemo tm (~sinnlos@unaffiliated/tm) |
| 01:45.42 | *** join/#maemo Natch (~Natch@c-b471e255.014-297-73746f25.bbcust.telenor.se) |
| 02:43.59 | *** join/#maemo dotcomma (~dotnick@42.119.146.98) |
| 02:45.44 | dotcomma | hey,can someone help me with my n900? |
| 02:45.59 | dotcomma | it only boots in r&d mode |
| 02:46.21 | dotcomma | despite after being reflashed twice |
| 02:47.41 | dotcomma | booting in normal mode would end up in five dots for 10 secs then reboot |
| 02:54.31 | *** join/#maemo ecloud_ (quassel@nat/qt/x-gnlkyqvjeuevylze) |
| 02:54.31 | *** join/#maemo FalconSpy (falconspy@unaffiliated/falconspy) |
| 02:59.48 | *** join/#maemo ced117 (~ced117@opensuse/member/ced117) |
| 02:59.48 | *** join/#maemo L29Ah (~L29Ah@unaffiliated/l29ah) |
| 02:59.48 | *** join/#maemo ashley (ashley@MediaWiki/Jack-Phoenix) |
| 02:59.48 | *** join/#maemo niceplace (~nplace@118.146.119.74.wiredns.net) |
| 02:59.48 | *** join/#maemo xray256_ (~xray256@79-73-168-10.dynamic.dsl.as9105.com) |
| 02:59.48 | *** join/#maemo teotwaki (~teotwaki@home.wedrop.it) |
| 03:00.07 | *** join/#maemo ced117 (~ced117@ghost.ced117.net) |
| 03:00.08 | *** join/#maemo ced117 (~ced117@opensuse/member/ced117) |
| 04:10.22 | *** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 05:03.58 | Maxdamantus | dotcomma: I suspect it's not meant to be disabled by just reflashing. You probably have to use `--disable-rd-mode`. |
| 05:04.38 | Maxdamantus | dotcomma: ie, run `flasher_3.5 --disable-rd-mode` and plug in the N900 while it's off. |
| 05:05.16 | Maxdamantus | Oh, nvm, misunderstood the problem. |
| 05:06.23 | Maxdamantus | So that behaviour probably means the watchdog is rebooting the device. |
| 05:08.07 | *** join/#maemo sunshavi (~user@190.236.255.122) |
| 05:29.07 | *** join/#maemo snibeti (~billy@2406:3400:21e:bf90:11b2:4710:b890:599c) |
| 05:29.31 | *** part/#maemo snibeti (~billy@2406:3400:21e:bf90:11b2:4710:b890:599c) |
| 05:54.54 | *** join/#maemo infobot (ibot@96-86-209-99-static.hfc.comcastbusiness.net) |
| 05:54.54 | *** topic/#maemo is Welcome to #maemo http://maemo.org/intro/ | "firmware" see ~lf (or ~tabletsdev ~combined ~emmc ~flasher) sdk: ~sb | http://wiki.maemo.org/Community_Council | Source: http://wiki.maemo.org/Sources | Chanlog: http://mg.pov.lt/maemo-irclog http://maemo.cloud-7.de/irclogs/freenode/_maemo/latest.log.html | #maemo-ssu is where the (few) devels and maintainers of the maemo-future meet |
| 05:54.54 | *** mode/#maemo [+v infobot] by ChanServ |
| 06:11.22 | *** join/#maemo inz (inz@inz.fi) |
| 06:42.34 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 06:54.56 | sixwheeledbeast | ~bootloop |
| 06:54.56 | infobot | extra, extra, read all about it, bootloop is when your device has broken rootfilesystem, so during reboot it fails on some service startup or kernel module load and thus reboots. This *drains* battery! And you can't reflash to stop bootloop when battery is drained. Recharge your battery by other means before reflashing. E.g. using ~rescueOS. Or external charger or BL-5J compatible other device. |
| 06:55.47 | sixwheeledbeast | is flashing definitely completed? |
| 06:57.55 | KotCzarny | ~flatbat |
| 06:57.58 | KotCzarny | ~flatbatt |
| 06:58.48 | KotCzarny | ~flatbatrecover |
| 06:58.48 | 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) |
| 06:58.56 | KotCzarny | also might come handy |
| 07:03.21 | *** join/#maemo norayr (~inky@141.136.76.72) |
| 07:08.49 | *** join/#maemo lukedashjr (~luke-jr@unaffiliated/luke-jr) |
| 08:13.02 | *** join/#maemo dotcomma (~dotnick@42.119.146.98) |
| 08:19.33 | dotcomma | sixwheeledbeast:flashing completed just fine and normally,but the phone still bootlooped |
| 08:20.10 | sixwheeledbeast | see above maybe flat battery? what makes you think rdmode is on? |
| 08:20.36 | dotcomma | about batteries,I have 3 and have all charged them via a Lumia 520 |
| 08:22.02 | dotcomma | I enabled rd mode after looking up threads on the forum |
| 08:22.58 | sixwheeledbeast | are you flashing both the emmc and the rootfs? |
| 08:23.07 | dotcomma | yes |
| 08:23.46 | dotcomma | i got the phone in that state so i guess it's a hardware problem then |
| 08:24.12 | KotCzarny | define 'bootloop' |
| 08:24.16 | KotCzarny | there are few different kinds |
| 08:24.22 | KotCzarny | how far does it boot? |
| 08:24.25 | sixwheeledbeast | maybe but I would assume there is something else |
| 08:24.34 | KotCzarny | no 5dots, 5dots, desktop |
| 08:24.36 | Maxdamantus | So just to be clear, it basically works fine as long as R&D mode is enabled? |
| 08:24.36 | sixwheeledbeast | especially if you get to five dots |
| 08:24.58 | dotcomma | 5 dots moving for 10 seconds,then froze and reboot |
| 08:25.09 | Maxdamantus | Seems fairly feasible to me that for whatever reason, the watchdog is triggering a reboot. |
| 08:25.12 | KotCzarny | once i had a 'bootloop' because because /home/user wasnt accessible |
| 08:25.18 | Maxdamantus | Since afaik that's normally disabled in R&D mode. |
| 08:25.36 | dotcomma | it works just fine minus charging and battery indicator |
| 08:25.42 | dotcomma | in r&d |
| 08:26.11 | Maxdamantus | Mm. I think one of the two watchdogs has to do with charging. |
| 08:26.11 | sixwheeledbeast | also if batteries are tired when the modem starts you have a lot more load. |
| 08:27.20 | sixwheeledbeast | ~bootreason |
| 08:27.20 | infobot | [bootreason] cat /proc/bootreason also see https://wiki.maemo.org/Troubleshooting_boot_issues#Reporting_reboot_issues for details |
| 08:27.33 | sixwheeledbeast | that would show if watchdog? |
| 08:28.09 | dotcomma | the phone's reporting 1 bar and 1/1mAh too which makes me think it's hardware |
| 08:28.30 | KotCzarny | maybe bad batteries/contacts? |
| 08:29.10 | dotcomma | they all work on the 520 and are all Nokia new old stock so nah |
| 08:29.37 | KotCzarny | battery contacts in phone? |
| 08:30.04 | KotCzarny | you can get battery info in terminal |
| 08:30.10 | sixwheeledbeast | even if they work it's load at boot that hasn't been ruled out |
| 08:30.14 | KotCzarny | wouldnt be half bad if you pastebin'ed it |
| 08:30.40 | KotCzarny | there is a possibility that charging circuit is fried too |
| 08:32.43 | KotCzarny | ~bc2900 |
| 08:32.48 | KotCzarny | ~bc2700 |
| 08:32.50 | KotCzarny | ~bc2700.sh |
| 08:32.53 | KotCzarny | hrm |
| 08:33.54 | KotCzarny | ~listkeys bq27 |
| 08:34.03 | Maxdamantus | dotcomma: might be worth showing your kernel messages (`dmesg`) after booting in R&D mode, since that's easy to obtain. |
| 08:34.50 | Maxdamantus | (reading /proc/bootreason would probably require modifying some init scripts to log it, or loading a rescue system on reboot) |
| 08:34.51 | KotCzarny | ~bq27 |
| 08:34.51 | infobot | rumour has it, bq27 is http://maemo.cloud-7.de/maemo5/usr/local/sbin/ bq27*, or http://maemo.cloud-7.de/maemo5/patches_n_tools/ |
| 08:35.00 | KotCzarny | ~bq27200 |
| 08:35.01 | infobot | from memory, bq27k-detail is http://maemo.cloud-7.de/maemo5/usr/local/sbin/bq27k-detail2, or ~bq27 |
| 08:35.35 | KotCzarny | http://maemo.cloud-7.de/maemo5/usr/local/sbin/bq27200.sh |
| 08:36.17 | KotCzarny | infobot: #maemo bq27 is also http://wiki.maemo.org/N900_Hardware_Charge_Meter |
| 08:36.17 | infobot | okay, KotCzarny |
| 08:36.22 | KotCzarny | ~bq27 |
| 08:36.22 | infobot | well, bq27 is http://wiki.maemo.org/N900_Hardware_Charge_Meter |
| 08:36.34 | KotCzarny | darn. |
| 08:36.47 | KotCzarny | infobot: forget #maemo bq27 |
| 08:36.47 | infobot | i forgot #maemo bq27, KotCzarny |
| 08:36.56 | KotCzarny | infobot: bq27 is also http://wiki.maemo.org/N900_Hardware_Charge_Meter |
| 08:36.56 | infobot | okay, KotCzarny |
| 08:36.59 | KotCzarny | ~bq27 |
| 08:37.00 | infobot | i guess bq27 is http://maemo.cloud-7.de/maemo5/usr/local/sbin/ bq27*, or http://maemo.cloud-7.de/maemo5/patches_n_tools/, or http://wiki.maemo.org/N900_Hardware_Charge_Meter |
| 08:37.20 | sicelo | <PROTECTED> |
| 08:37.32 | sicelo | at least i wouldn't search bq27 alone |
| 08:38.07 | KotCzarny | feel free to fix that, i was having trouble remembering which controller model it was |
| 08:38.08 | KotCzarny | :) |
| 08:41.34 | KotCzarny | also, seems those might be compatible with any bq27x00 controller |
| 08:42.17 | dotcomma | monitoring with lshal -m gave me charging status=error,probably there's my issue since RD mode should still have working charging and indicator right? |
| 08:42.32 | KotCzarny | lshall probably uses dbus approximation |
| 08:42.47 | KotCzarny | bq script will inquire battery controller directly |
| 08:43.08 | KotCzarny | and when you switch batteries capacity is 100% wrong, because it wasnt calibrated |
| 08:45.01 | *** join/#maemo florian_kc (~florian_k@Maemo/community/contributor/florian) |
| 08:46.22 | KotCzarny | rd mode probably just disables watchdog, it doesnt prevent charging |
| 08:47.00 | KotCzarny | i bet that something is wrong with battery controller in your n900 |
| 08:55.03 | dotcomma | https://talk.maemo.org/showpost.php?p=1181666&postcount=130 this completely fits what I have |
| 08:55.59 | dotcomma | probably previous owner used a dodgy charger and fried the sense circuit |
| 08:56.06 | KotCzarny | yup, part of the battery controller fried |
| 08:58.07 | dotcomma | I'll try finding a broken touch/lock code n900 around my area then probably |
| 08:58.31 | KotCzarny | there is a plenty with broken usb |
| 08:58.58 | KotCzarny | although that doesnt help if you cant solder tiny part |
| 08:59.15 | KotCzarny | broken lcd might be also a good one to swap |
| 08:59.25 | KotCzarny | because it's easiest to just swap whole display part |
| 08:59.53 | KotCzarny | or you can hack around and maybe you can get it to charge |
| 09:00.02 | dotcomma | I got this for free from a phone shop saying "what do you know it's another untested but turns out to be dead n900" |
| 09:00.09 | KotCzarny | seeing the guy in that thread managed to do it with restarting bmi |
| 09:00.31 | KotCzarny | free is always nice |
| 09:00.34 | KotCzarny | :) |
| 09:00.51 | dotcomma | voltages do go up when i check so it works for the time being I guess |
| 09:01.24 | KotCzarny | check that battery script i've pasted earlier |
| 09:02.26 | dotcomma | n900s with toast baseband/bootloop are more common than working ones somehow |
| 09:02.53 | dotcomma | well it's Vietnam,what did you expect |
| 09:03.08 | KotCzarny | that's because modem chip gets desoldered from heavy presses on keyboard |
| 09:03.20 | KotCzarny | if you can reflow it, it will go back to life |
| 09:04.03 | dotcomma | sounds like the iPhone 4 to me,lol |
| 09:04.10 | KotCzarny | :) |
| 09:06.11 | dotcomma | I just heard sad news,my local phone shop threw a N9 screen instead of a dead Lumia 800 screen on accident,whoops |
| 09:06.44 | KotCzarny | arent those the same? |
| 09:06.50 | dotcomma | the screens for the N9 are starting to get harder to find it seems |
| 09:06.54 | KotCzarny | i thought they only differ in software |
| 09:07.04 | dotcomma | technically,yes |
| 09:07.47 | dotcomma | the 800 have the extra display space blocked by the printed keys |
| 09:07.58 | dotcomma | on the glass |
| 09:08.15 | dotcomma | and no front camera cutout |
| 09:10.49 | *** join/#maemo peetah (~peetah@cha92-9-82-236-202-86.fbx.proxad.net) |
| 10:27.43 | *** join/#maemo norayr (~inky@141.136.76.72) |
| 11:26.15 | *** join/#maemo florian (~florian_k@Maemo/community/contributor/florian) |
| 11:53.22 | *** join/#maemo Kabouik (~Kabouik@51.15.231.56) |
| 11:55.22 | *** join/#maemo Kabouik (~Kabouik@51.15.231.56) |
| 12:22.00 | *** join/#maemo Natch (~Natch@c-b471e255.014-297-73746f25.bbcust.telenor.se) |
| 14:53.07 | *** join/#maemo Vajb (~Vajb@91-158-49-42.elisa-laajakaista.fi) |
| 15:33.27 | *** join/#maemo florian (~florian_k@Maemo/community/contributor/florian) |
| 15:41.57 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 17:00.07 | *** join/#maemo Kilroo (~Kilroo@71.71.105.78) |
| 18:20.02 | *** join/#maemo mp107 (uid383093@gateway/web/irccloud.com/x-zllejgxubshtasfa) |
| 18:33.58 | *** join/#maemo drathir_tor (~drathir@gateway/tor-sasl/drathir) |
| 19:16.32 | *** join/#maemo L29Ah (~L29Ah@unaffiliated/l29ah) |
| 19:27.40 | *** join/#maemo L29Ah (~L29Ah@unaffiliated/l29ah) |
| 19:36.18 | *** join/#maemo luke-jr (~luke-jr@unaffiliated/luke-jr) |
| 19:59.12 | *** join/#maemo norayr (~inky@141.136.77.148) |
| 22:33.53 | *** join/#maemo norayr (~inky@141.136.77.148) |
| 22:34.50 | *** join/#maemo norayr (~inky@141.136.77.148) |
| 23:03.02 | brolin_empey | I found a strange behaviour apparently involving caching in all of Vivaldi, Firefox, and IE 11 on Windows 10 but I do not know if the developers would consider it a bug. |
| 23:12.36 | brolin_empey | Basically, I have a test version of a static Web site generated by Jekyll used to preview the static build of the Web site before publishing the build to the public Web site. I am using a name-based HTTP virtual host with apache2 on Debian GNU+Linux 7.0 for x86-32 but I do not know if that is relevant. The build of the Web site from Tuesday had the Products and About pages at /products/ and /about/ . I had browsed to/loaded all of the pages of the small |
| 23:12.36 | brolin_empey | Web site in Vivaldi, Firefox, and IE 11 on Windows 10. Now the build of the Web site from today (Friday) has the Products and About pages at /products and /about and /products/ and /about/ now return a 404 Not Found status. The problem is that these three Web browsers keep requesting /products/ and /about/ with the trailing slash even though the pages in the current build of the Web site link to /products and /about without the trailing slash, which means |
| 23:12.36 | brolin_empey | a Web browser that had already loaded these two pages in the build of the Web site from Tuesday can no longer access these two pages even though a Web browser that loads the Web site for the first time today, at least Vivaldi for Android, can access these two pages. |
| 23:35.59 | brolin_empey | Apparently the antiquated final version of Vivaldi for Windows XP correctly loads the /products and /about pages when loading the Web site for the first time today. I mean today is the first time that the Web site has been loaded; English is too grammatically ambiguous. |
| 23:41.10 | brolin_empey | Actually, the Web site had been loaded before today but it did not matter because only / had been loaded so the URIs for the Products and About pages had not been accessed. |