| 00:00.30 | Maxdamantus | actually, the block device wouldn't disappear if it's mounted .. it would just result in IO errors, if the mechanism isn't software-controlled. |
| 00:00.31 | r00t|eeepc | it's not magnetic i think, but a light reflection thing, shared with the lens cover? |
| 00:00.54 | r00t|eeepc | and, it triggers a script that umounts the card |
| 00:00.54 | *** join/#maemo useretail (useretail_@gateway/shell/elitebnc/x-htdyvauefilchnzw) |
| 00:01.01 | r00t|eeepc | just as is done when you connect as usb-storage |
| 00:02.20 | Maxdamantus | Okay, so you can presumably just remove that functionality if you didn't want to use the SD card as something you'd normally remove at will. |
| 00:03.21 | r00t|eeepc | actually what would be the point of a non software-controlled mechanism that disconnects the card when the cover is open? might aswell just wait for the user to disconnect the card by pulling it out |
| 00:05.56 | Maxdamantus | Dunno. Maybe if the slot were fiddly and it were likely that the card would be powered off and on rapidly while being inserted. |
| 00:06.24 | Maxdamantus | but even in that case, there are probably better ways to handle it. |
| 00:08.00 | Maxdamantus | also: http://forum.dailymobile.net/index.php?topic=20949.0 |
| 00:08.06 | Maxdamantus | seems to be a magnet. |
| 00:26.18 | *** join/#maemo konelix (~konelix@190.148.50.247) |
| 00:28.59 | *** join/#maemo githogori (~githogori@c-50-152-210-24.hsd1.ca.comcast.net) |
| 00:39.41 | *** join/#maemo triggerhappy (~quassel@112.209.8.22) |
| 00:40.11 | *** join/#maemo int_ua (~int_ua@ip-602f.proline.net.ua) |
| 00:45.16 | int_ua | http://talk.maemo.org/showpost.php?p=1408340&postcount=1087 |
| 00:45.34 | int_ua | PLEASE HELP! My life could depend on it |
| 01:01.12 | *** join/#maemo robbiethe1st (~robbiethe@50-52-50-249.cral.id.frontiernet.net) |
| 01:04.01 | *** join/#maemo Herbstbert (~Herbstber@drms-4d0dede0.pool.mediaWays.net) |
| 01:25.39 | *** join/#maemo MohammadAG (~MohammadA@Maemo/community/contributor/MohammadAG) |
| 01:35.26 | DocScrutinizer05 | rmmod adp1653 -- watch out, may break camera! |
| 01:35.48 | Maxdamantus | Though he left. |
| 01:36.01 | DocScrutinizer05 | use carton and chewing gum, or black sticky tape! cover the LED "lens" window |
| 01:36.17 | DocScrutinizer05 | yes, but he might check chanlog |
| 01:36.48 | DocScrutinizer05 | I guess it's a bit of trouble to stay online all the time while in a civil war |
| 01:37.29 | DocScrutinizer05 | Kiev might become the new Tien nan men square |
| 01:37.34 | DocScrutinizer05 | this night |
| 01:38.19 | Maxdamantus | tbh, in that situation, I'd probably just shortcircuit the LED with solder. |
| 01:38.28 | DocScrutinizer05 | aaahyes |
| 01:38.32 | DocScrutinizer05 | with solder |
| 01:38.47 | Maxdamantus | though I don't know how difficult that is; I don't have a device yet. |
| 01:39.31 | DocScrutinizer05 | it's for sure too difficult to do it in the street, while everybody trowing rocks and stones and smash stuff around you |
| 01:40.05 | DocScrutinizer05 | I just hope he'll survive |
| 01:40.26 | Maxdamantus | in that case, I'd at least remove the module from the filesystem and reboot. |
| 01:40.29 | DocScrutinizer05 | and the revolution will survive and conquer |
| 01:40.44 | DocScrutinizer05 | rmmod might break camera |
| 01:40.59 | Maxdamantus | permanently? |
| 01:41.01 | DocScrutinizer05 | I had no time to check |
| 01:41.23 | DocScrutinizer05 | no, but at least for two boots, plus editing |
| 01:41.26 | Maxdamantus | or just lose access to it, because it's also the actual camera driver |
| 01:41.59 | Maxdamantus | ah, not the camera driver, but might control the camera in some way. |
| 01:42.16 | DocScrutinizer05 | the cam-ui app or v4l2 might blow chunks when flashlight not available in /sys or /dev |
| 01:44.29 | DocScrutinizer05 | moves over to TV, check NTV and CNN etc |
| 01:51.42 | DocScrutinizer05 | :-S zilch |
| 01:52.41 | *** join/#maemo xjiujiu (~xjiujiu@218.77.14.202) |
| 01:52.50 | DocScrutinizer05 | http://www.theaustralian.com.au/news/world/ukraine-police-storm-kiev-protester-barricades-killing-5/story-e6frg6so-1226808228511 |
| 02:04.38 | *** join/#maemo githogori (~githogori@c-50-156-58-163.hsd1.ca.comcast.net) |
| 02:12.34 | *** join/#maemo xjiujiu (~xjiujiu@218.77.14.202) |
| 02:18.09 | DocScrutinizer05 | http://rt.com/news/kiev-protest-clashes-updates-862/ hmm |
| 02:18.54 | *** join/#maemo Humpelstilzchen (erik@e179199049.adsl.alicedsl.de) |
| 02:20.30 | *** join/#maemo hubutm20 (~hubutm20@79.113.82.14) |
| 02:25.53 | *** join/#maemo xjiujiu (~xjiujiu@218.77.14.202) |
| 02:29.03 | *** join/#maemo povbot_ (~supybot@office.pov.lt) |
| 02:31.48 | *** join/#maemo xjiujiu (~xjiujiu@218.77.14.202) |
| 02:40.10 | *** join/#maemo xjiujiu (~xjiujiu@218.77.14.202) |
| 02:48.32 | *** join/#maemo xjiujiu (~xjiujiu@218.77.14.202) |
| 02:50.32 | *** join/#maemo mschlens_ (~mschlens@p5DC1664C.dip0.t-ipconnect.de) |
| 02:56.21 | *** join/#maemo xjiujiu (~xjiujiu@218.77.14.202) |
| 02:57.29 | *** join/#maemo amizraa (~amizraa@gateway/tor-sasl/amizraa) |
| 02:57.43 | *** join/#maemo xjiujiu (~xjiujiu@218.77.14.202) |
| 02:59.46 | *** join/#maemo spaak (~Adium@s529d269a.adsl.online.nl) |
| 03:03.28 | *** join/#maemo triggerhappy (~quassel@122.54.171.111) |
| 03:11.04 | *** join/#maemo xjiujiu (~xjiujiu@218.77.14.202) |
| 03:13.56 | *** join/#maemo githogori (~githogori@c-50-156-58-163.hsd1.ca.comcast.net) |
| 03:16.53 | *** join/#maemo xjiujiu (~xjiujiu@218.77.14.202) |
| 03:26.12 | *** join/#maemo xjiujiu (~xjiujiu@218.77.14.202) |
| 03:32.05 | *** join/#maemo xjiujiu (~xjiujiu@218.77.14.202) |
| 03:34.04 | *** join/#maemo githogori (~githogori@c-50-156-58-163.hsd1.ca.comcast.net) |
| 03:48.28 | *** join/#maemo xjiujiu (~xjiujiu@218.77.14.202) |
| 04:01.27 | *** join/#maemo lxp1 (~lxp@188-22-250-229.adsl.highway.telekom.at) |
| 04:01.51 | *** join/#maemo xjiujiu (~xjiujiu@218.77.14.202) |
| 04:02.54 | *** join/#maemo uen| (~uen@p5DCB172E.dip0.t-ipconnect.de) |
| 04:08.14 | *** join/#maemo xjiujiu (~xjiujiu@218.77.14.202) |
| 04:17.43 | *** join/#maemo xjiujiu (~xjiujiu@218.77.14.202) |
| 04:22.57 | *** join/#maemo SAiF (~root@59.96.200.17) |
| 04:30.30 | *** join/#maemo maybeHere (~cl@p5B161427.dip0.t-ipconnect.de) |
| 04:34.02 | *** join/#maemo xjiujiu (~xjiujiu@218.77.14.202) |
| 04:43.22 | *** join/#maemo xjiujiu (~xjiujiu@218.77.14.202) |
| 04:46.09 | *** join/#maemo fuz_ (nobody@vau75-10-88-164-23-88.fbx.proxad.net) |
| 04:51.16 | *** join/#maemo xjiujiu (~xjiujiu@218.77.14.202) |
| 04:55.49 | *** join/#maemo sunny_s (~sunny_s@business-092-079-020-027.static.arcor-ip.net) |
| 05:00.56 | *** join/#maemo Aggese (~Durand@ghs/durand) |
| 05:44.33 | *** join/#maemo eMHa (~mh@nat.de.netviewer.com) |
| 06:09.14 | *** join/#maemo VDVsx (~VDVsx@192.194.199.34) |
| 06:27.45 | *** join/#maemo cehteh (~cehteh@pipapo.org) |
| 06:29.33 | *** part/#maemo cehteh (~cehteh@pipapo.org) |
| 06:39.58 | *** join/#maemo darkschneider (~gab@93-32-49-60.ip32.fastwebnet.it) |
| 06:40.54 | *** join/#maemo trx (ns-team@devbin/founder/trx) |
| 06:43.42 | *** join/#maemo fuz_ (nobody@vau75-10-88-164-23-88.fbx.proxad.net) |
| 07:35.46 | *** join/#maemo till (till@vispillo.org) |
| 07:37.55 | Maxdamantus | Are all physical keys on the N900 ones the software sees? |
| 07:38.09 | Maxdamantus | so running `xev` should show a keycode for each one? |
| 07:38.51 | Maxdamantus | (as opposed to what happens on a lot of laptop keyboards, where the `fn` button modifies what keys are sent and is not itself seen) |
| 07:40.50 | *** join/#maemo Agge (~Durand@ghs/durand) |
| 07:43.50 | DocScrutinizer05 | that depends, either side |
| 07:44.05 | Maxdamantus | either side? |
| 07:44.08 | *** join/#maemo croppa (~stuart@14.14.233.220.static.exetel.com.au) |
| 07:44.14 | DocScrutinizer05 | yeah, on laptop as well |
| 07:44.45 | Maxdamantus | Well, pretty much all laptops have a special fn key. |
| 07:44.54 | DocScrutinizer05 | on N900 all kbd keys and the volume +/- keys are genuine "keys", with keycode and all |
| 07:44.58 | Maxdamantus | a lot of them also use it as speciial modifier the OS doesn't see. |
| 07:45.00 | Maxdamantus | Okay |
| 07:45.20 | DocScrutinizer05 | the power and cam are buttons |
| 07:45.28 | Maxdamantus | (eg, as a numpad that overlays iopjklbnm or something. |
| 07:45.30 | Maxdamantus | ) |
| 07:45.53 | DocScrutinizer05 | well, that's highly depending on laptop hardware |
| 07:46.59 | Maxdamantus | Yeah, as I said, pretty much all of them have the `fn` key .. probably most of them have at least a few such uses as modifiers for normal keys, which aren't seen by the software. |
| 07:47.01 | DocScrutinizer05 | but yes, many laptops process this sort of stuff in the keyboard MCU |
| 07:47.20 | Maxdamantus | my Aspire One uses `fn` for home/end/pgup/pgdown |
| 07:48.05 | Maxdamantus | and it's not up to the OS to figure out that fn+up = home .. the keyboard sends the normal keycode for home over its PS/2 interface. |
| 07:48.41 | Maxdamantus | er, fn+pgup = home |
| 07:49.36 | *** join/#maemo Aggese (~Durand@ghs/durand) |
| 07:50.12 | Maxdamantus | where it could, if it weren't for the screen brightness controls, which are independent of the OS, have just been another key that OSes treated as modifiers when configured properly. |
| 07:50.39 | Maxdamantus | (and other similar things, like enable/disable touchpad, switch display output, ..) |
| 07:51.50 | *** join/#maemo LauRoman (~LauRoman@5-14-92-51.residential.rdsnet.ro) |
| 07:53.50 | *** join/#maemo eijk_ (~eijk@e178198087.adsl.alicedsl.de) |
| 08:08.01 | *** join/#maemo FlameReaper (~assassin@203.106.176.203) |
| 08:10.18 | *** join/#maemo OkropNick (kuba@host-n2-75-80.telpol.net.pl) |
| 08:27.04 | *** join/#maemo jmlich (jmlich@nat/redhat/x-svnzajtapmcjnxfr) |
| 08:30.47 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 08:32.09 | *** join/#maemo povbot (~supybot@office.pov.lt) |
| 08:36.17 | *** join/#maemo useretail (useretail_@gateway/shell/elitebnc/x-dtokwmhibgsithgu) |
| 08:38.15 | *** join/#maemo Kabouik (~quassel@147.99.218.243) |
| 08:43.51 | *** join/#maemo triggerhappy (~quassel@110.55.154.135) |
| 08:44.49 | *** join/#maemo SAiF (~root@59.96.207.31) |
| 08:47.28 | *** join/#maemo rcg_ (~rcg@fhffm1223.nat.fh-frankfurt.de) |
| 08:47.28 | *** join/#maemo rcg (~rcg@fhffm1223.nat.fh-frankfurt.de) |
| 08:48.26 | *** join/#maemo Kabouik (~quassel@147.99.218.243) |
| 09:08.28 | *** join/#maemo jmlich (jmlich@nat/redhat/x-jrqhurcineankxck) |
| 09:09.43 | *** join/#maemo Humpelstilzchen (erik@e179199049.adsl.alicedsl.de) |
| 09:11.20 | *** join/#maemo triggerhappy (~quassel@110.55.154.135) |
| 09:11.20 | *** join/#maemo FlameReaper (~assassin@203.106.176.203) |
| 09:11.20 | *** join/#maemo till (till@vispillo.org) |
| 09:11.20 | *** join/#maemo lxp1 (~lxp@188-22-250-229.adsl.highway.telekom.at) |
| 09:12.35 | *** join/#maemo triggerhappy (~quassel@122.54.171.111) |
| 09:13.56 | *** join/#maemo till- (till@vispillo.org) |
| 09:14.14 | *** join/#maemo FlameReaper (~assassin@sp-176-203.tm.net.my) |
| 09:14.42 | *** join/#maemo lxp (~lxp@188-22-250-229.adsl.highway.telekom.at) |
| 09:21.41 | *** join/#maemo Gatta_Negra (~SailCat@89.190.196.121) |
| 09:32.42 | *** join/#maemo sequantz (~sequantz@194.11.24.44) |
| 09:35.08 | *** join/#maemo r00t_ (~r00t@89.204.139.179) |
| 09:35.38 | r00t_ | is this still around somewhere? http://talk.maemo.org/showthread.php?t=66713 |
| 09:36.10 | r00t_ | (n900 recovery system to be loaded into ram via flasher) |
| 09:37.42 | *** join/#maemo KhertanAtwork (~KhertanAt@nax2.naxos-fr.net) |
| 09:42.48 | *** join/#maemo mbs1337 (~mbs1337@93-167-25-140-dynamic.dk.customer.tdc.net) |
| 09:57.22 | *** join/#maemo dhbiker (~dhbiker@95.87.145.172) |
| 10:02.26 | *** join/#maemo eijk_ (~eijk@e178198087.adsl.alicedsl.de) |
| 10:08.17 | *** join/#maemo dhbiker (~dhbiker@95.87.145.172) |
| 10:14.52 | *** join/#maemo r00t_ (~r00t@82.113.98.168) |
| 10:18.25 | *** join/#maemo r00t__ (~r00t@31-18-97-120-dynip.superkabel.de) |
| 10:19.22 | *** join/#maemo natsukao (~natsukao@dynamic-adsl-94-37-181-133.clienti.tiscali.it) |
| 10:19.25 | natsukao | hi |
| 10:19.44 | natsukao | for noia 770 the datasheets: http://www.s-manuals.com/phone/nokia_n770 |
| 10:20.19 | natsukao | and much more on http://www.s-manuals.com/phone/nokia |
| 10:20.52 | natsukao | for nokia 770 the datasheets: http://www.s-manuals.com/phone/nokia_n770 |
| 10:21.33 | natsukao | so anyone is free to open it and to watch how is did it, or to hack it |
| 10:21.47 | natsukao | happy hacking |
| 10:21.53 | natsukao | :-) |
| 10:23.12 | *** join/#maemo lufu (~user@2001:62a:4:410:224:d7ff:fe05:d2c) |
| 10:24.18 | natsukao | is there a way tro charge the battery of nokia 770 with the usb ? |
| 10:34.24 | *** join/#maemo mvp (~mvp@h196.natout.aau.dk) |
| 10:36.07 | *** join/#maemo Kabouik_ (~quassel@147.99.218.243) |
| 10:38.22 | *** join/#maemo r00t__ (~r00t@31-18-97-120-dynip.superkabel.de) |
| 10:38.38 | *** join/#maemo LinuxCode (~LinuxCode@fedora/LinuxCode) |
| 10:50.19 | TTilus | sshing in my n900 with key auth is not working |
| 10:50.52 | *** join/#maemo eijk (~eijk@e178198087.adsl.alicedsl.de) |
| 10:52.31 | TTilus | ssh -vvv user@nokikana gives http://pastie.org/private/wrqiwlrl3ofqkabhlcp3w |
| 10:53.39 | Maxdamantus | How did you try setting it up? |
| 10:55.01 | TTilus | im moving my stuff over to "new" device, previous stopped charging |
| 10:55.14 | TTilus | new device is freshly flashed and working |
| 10:55.45 | TTilus | installed openssh and copied /home/user/.ssh over from the old one |
| 10:56.13 | TTilus | pw authenticated login works |
| 10:56.40 | Maxdamantus | and you can't ssh out from the new phone? |
| 10:56.47 | Maxdamantus | (the issue isn't sshing into it?) |
| 10:56.47 | TTilus | in |
| 10:56.57 | TTilus | and i can ssh both in and out |
| 10:57.04 | Maxdamantus | in will require you set it up again on the machine you want to connect from. |
| 10:57.09 | TTilus | only inbound key auth fails |
| 10:57.25 | Maxdamantus | unless you copied the keys from sshd itself |
| 10:57.26 | Maxdamantus | which will be in /etc somewhere. |
| 10:57.37 | Maxdamantus | /etc/ssh |
| 10:57.57 | Maxdamantus | I suspect it'll work if you just copy /etc/ssh from the old device to the new one and restart sshd. |
| 10:58.49 | TTilus | uh oh, why would i need the host key of old n900? |
| 10:59.05 | TTilus | or do you mean copying over the conf? |
| 10:59.23 | *** join/#maemo bef0rd (~bef0rd@186.154.48.46) |
| 10:59.29 | *** join/#maemo bef0rd (~bef0rd@unaffiliated/beford) |
| 11:00.19 | Maxdamantus | Hmm .. dunno, maybe it shouldn't. |
| 11:00.37 | TTilus | does n900 openssh server log somewhere? |
| 11:00.46 | TTilus | it might provide some clue |
| 11:02.06 | *** join/#maemo r00t|d430 (~r00t@31-18-97-120-dynip.superkabel.de) |
| 11:05.05 | TTilus | don't really know what was up, but setting password for user made key auth work :D |
| 11:05.41 | natsukao | if i upload a shell script in my e-mail, and i try to send it, whe trhe nokia will try to download it, it will be opened as a file text that a shell script, how to solve this problem ? |
| 11:08.41 | *** join/#maemo lizardo (lizardo@nat/indt/x-dkcyyazwwmsfgkjs) |
| 11:09.03 | TTilus | what would you want it to do? (i.e. what's the problem) |
| 11:09.13 | r00t|d430 | natsukao: you expect the email client to _execute_ the script when you open it? |
| 11:09.40 | natsukao | i upload the shell script in the email |
| 11:09.52 | Ashley` | <r00t|d430> natsukao: you expect the email client to _execute_ the script when you open it? |
| 11:10.08 | Ashley` | I dont think it'd be good behavior :P |
| 11:10.13 | natsukao | then i downloaded with nokia 770, but i don't see the shell script but the source code |
| 11:10.18 | r00t|d430 | ashley: ask microsoft ;) |
| 11:10.27 | Ashley` | r00t|d430, :D |
| 11:10.45 | r00t|d430 | natsukao: with a shell script, there is no difference between the script or it's source... |
| 11:10.49 | TTilus | natsukao: shell script _is_ a text file |
| 11:11.03 | TTilus | natsukao: do you want to run it on your 770? |
| 11:11.19 | natsukao | how to start a shell script on shell ? |
| 11:11.25 | natsukao | yes, correct |
| 11:11.33 | r00t|d430 | sh /path/to/file.sh |
| 11:11.46 | r00t|d430 | (or chmod +x and without 'sh') |
| 11:11.47 | natsukao | thanks |
| 11:12.37 | *** join/#maemo till (till@vispillo.org) |
| 11:15.22 | *** join/#maemo dos1 (~dos@unaffiliated/dos1) |
| 11:17.40 | natsukao | correct, now works |
| 11:17.45 | natsukao | thans |
| 11:18.42 | natsukao | when i uploaded the shell script the proprieties were changed from a simple file text in *.html |
| 11:19.56 | natsukao | and so chmod +x could not works, then i found this little error, i removed *.html and then i did chmod +x namefile ad pushed the key enter |
| 11:20.12 | natsukao | then sh wargames |
| 11:22.24 | r00t|d430 | the filename (or extension) is irrelevant, you can execute it even when it's named .html |
| 11:22.36 | r00t|d430 | as long as the content wasn't actually html-formatted |
| 11:22.53 | natsukao | it is only a shell script http://pastebin.com/3A5h2QbJ |
| 11:23.16 | r00t|d430 | trying to execute an html file as a script usually creates lots of junk files, due to all the redirection symbols ;) |
| 11:24.53 | natsukao | but i nver saved as *.html it was changed from mail.riseup.net such as from gmail |
| 11:25.08 | r00t|d430 | who cares, really? |
| 11:25.26 | natsukao | i got a little problem with nokia 770, i an't insert MMC card |
| 11:26.01 | natsukao | so for me was necessary to upload from the laptop and to download from the nokia 770 |
| 11:26.04 | r00t|d430 | you mean, it's not detected when you insert it? |
| 11:26.18 | natsukao | nokia 770, can't works without mmc card |
| 11:26.23 | r00t|d430 | why not juse use scp or obex or something? |
| 11:26.50 | natsukao | no, it is not that the problem, the fact is not that does not close |
| 11:27.19 | natsukao | and so it means, to left it 1 month to the nokia, only for this stupid thing, |
| 11:30.03 | r00t|d430 | why is this not on maemo.org? REAL recovery mode for n900, without requiring a bootable rootfs... http://archive.is/lP093 |
| 11:30.54 | *** join/#maemo andre__ (~andre__@wikimedia/aklapper) |
| 11:35.25 | *** join/#maemo Veggen (~vegard@engen.priv.no) |
| 11:47.54 | *** join/#maemo shentey (~shentey@g225083172.adsl.alicedsl.de) |
| 11:56.34 | *** join/#maemo kov (~kov@debian/developer/kov) |
| 11:58.15 | *** join/#maemo lufu (~user@2001:62a:4:410:224:d7ff:fe05:d2c) |
| 12:01.44 | *** join/#maemo KhertanAtwork (~KhertanAt@nax2.naxos-fr.net) |
| 12:05.04 | *** join/#maemo SAiF (~root@117.217.128.54) |
| 12:28.37 | *** join/#maemo bef0rd (~bef0rd@unaffiliated/beford) |
| 12:38.34 | *** join/#maemo hbib (~wurmel@pD9E0C0EF.dip0.t-ipconnect.de) |
| 12:42.01 | *** join/#maemo triggerhappy (~quassel@112.209.8.22) |
| 12:50.44 | *** join/#maemo dvoid (~quassel@h66n14-sde-a31.ias.bredband.telia.com) |
| 13:15.39 | *** join/#maemo hubutm20 (~hubutm20@79.113.82.213) |
| 13:17.47 | *** join/#maemo bef0rd (~bef0rd@unaffiliated/beford) |
| 13:26.30 | Ashley` | hm. |
| 13:26.40 | Ashley` | I reflashed my n900 |
| 13:26.51 | Ashley` | updated, installed cssu-testing |
| 13:27.00 | Ashley` | installed u-boot (first time) |
| 13:27.10 | Ashley` | (u-boot-flasher package) |
| 13:27.25 | Ashley` | and kernel-cssu-bootimg |
| 13:27.45 | Ashley` | and when I boot my n900 and select cssu kernel (or default one) |
| 13:28.29 | Ashley` | it loads the kernel, etc etc, then it says "starting kernel", and after few-fewteen (fewteen xD) seconds it turns off |
| 13:28.49 | Ashley` | i can reflash only kernel from flasher-3.5, and it boots normally |
| 13:28.58 | Ashley` | what did I do wrong? |
| 13:29.14 | TTilus | is updating time from gsm network supposed to work with n900? |
| 13:29.18 | TTilus | pr1.3 |
| 13:30.00 | TTilus | as far as i remember my previous n900 had sync working |
| 13:30.04 | r00t|d430 | TTilus: never worked for me with any carrier |
| 13:30.14 | r00t|d430 | or any phone for that matter |
| 13:30.34 | TTilus | so ntpd it is then... |
| 13:30.45 | Ashley` | It works for me I think |
| 13:30.56 | Ashley` | Poland, Orange |
| 13:31.14 | Ashley` | (but with latest cssu-t) |
| 13:32.06 | TTilus | ok, maybe ntpd only after upgrading to cssu, which im about to do |
| 13:32.40 | r00t|d430 | ashley: what you did wrong: you are using a system that provides no diagnostic messages during boot... |
| 13:40.39 | *** join/#maemo beford (~frod@unaffiliated/beford) |
| 13:55.57 | Ashley` | r00t|d430, what can I do? is there any flag or something for "debug mode"? |
| 13:56.51 | r00t|d430 | ashley: i don't know... |
| 13:57.02 | r00t|d430 | ashley: serial console, good luck ;) |
| 14:08.28 | Ashley` | :/ |
| 14:09.01 | KhertanAtwork | TTilus, was working for me with orange and free, not with SFR |
| 14:09.06 | Ashley` | I guess u-boot is not for me :f |
| 14:09.14 | KhertanAtwork | ... depends on carrier ... some didn't respect gsm protocol |
| 14:37.12 | Ashley` | Is there any alternative to u-boot? |
| 14:45.14 | *** join/#maemo at1as (~at1as@kurios.r4780y.com) |
| 14:52.25 | TTilus | KhertanAtwork: ok, good to know |
| 15:04.18 | *** join/#maemo till (till@vispillo.org) |
| 15:15.25 | *** join/#maemo FReaper (~assassin@sp-176-203.tm.net.my) |
| 15:19.18 | *** join/#maemo Dynamit (~Mohamed@84-55-71-22.customers.ownit.se) |
| 15:26.48 | *** join/#maemo shentey (~shentey@wlan-141-23-99-29.tubit.tu-berlin.de) |
| 15:33.09 | *** join/#maemo hbib1 (~wurmel@pD9E3C4C3.dip0.t-ipconnect.de) |
| 15:34.24 | *** join/#maemo r00t_ (~r00t@89.204.137.88) |
| 15:35.22 | *** join/#maemo shentey_ (~shentey@wlan-141-23-99-29.tubit.tu-berlin.de) |
| 15:40.13 | *** join/#maemo valerius (~user@95.153.170.220) |
| 15:41.13 | *** join/#maemo valeriusL (~valerius@185.3.32.105) |
| 15:41.14 | *** join/#maemo FlameReaper (~assassin@sp-176-203.tm.net.my) |
| 15:47.33 | *** join/#maemo ruskie (ruskie@sourcemage/mage/ruskie) |
| 15:50.35 | *** join/#maemo till (till@vispillo.org) |
| 15:53.47 | *** join/#maemo shentey__ (~shentey@wlan-141-23-99-29.tubit.tu-berlin.de) |
| 15:54.17 | *** join/#maemo githogori (~githogori@c-50-156-58-163.hsd1.ca.comcast.net) |
| 15:55.12 | *** join/#maemo heroux (~heroux@50708181.static.ziggozakelijk.nl) |
| 15:56.25 | *** join/#maemo githogori (~githogori@c-50-156-58-163.hsd1.ca.comcast.net) |
| 15:56.29 | *** join/#maemo hxka (~hxka@176.14.100.214) |
| 15:57.00 | hxka | freemangordon: Hello |
| 15:57.26 | hxka | freemangordon: How SR will work if one enables VDD1 but not VDD2? |
| 16:08.55 | *** join/#maemo valerius (~user@185.3.32.105) |
| 16:09.20 | *** join/#maemo shentey (~shentey@wlan-141-23-99-29.tubit.tu-berlin.de) |
| 16:23.47 | *** join/#maemo r00t_ (~r00t@89.204.153.124) |
| 16:29.22 | freemangordon | hxka: VDD2 doesn't get controlled by SR :) |
| 16:29.35 | freemangordon | VDD2 is L3 interconnect IIRC |
| 16:29.49 | freemangordon | voltage that is |
| 16:31.19 | hxka | So it's useless then? |
| 16:32.37 | Ashley` | yay |
| 16:32.57 | freemangordon | hxka: hmm? why is that? |
| 16:32.58 | Ashley` | I downloaded pali's kernel pack with pr1.3 kernel with framebuffer |
| 16:33.08 | freemangordon | if you enable it, the VDD2 lotage is controlled |
| 16:33.17 | freemangordon | *voltage |
| 16:33.31 | Ashley` | and I can see why it doesn't work with u-boot |
| 16:33.31 | freemangordon | hxka: I am not sure I get you right |
| 16:33.32 | hxka | freemangordon: I meant it's useless to enable only VDD1 |
| 16:34.00 | freemangordon | no, why? VDD1 is MPU/DSP voltage |
| 16:34.15 | freemangordon | but ofc it is better to have both enabled |
| 16:34.31 | hxka | Oh, thanks |
| 16:35.16 | hxka | Another question: is there any benefit in lowering the voltages in k-p-s profile if both VDD1 and VDD2 are enabled anyway? |
| 16:39.01 | *** join/#maemo shentey (~shentey@wlan-141-23-99-29.tubit.tu-berlin.de) |
| 16:41.19 | Ashley` | Hm |
| 16:41.50 | hxka | Also, I reported earlier that my N900 is unstable on any frequency above 600 MHz. That turned out to be not true: it's only unstable if VDD2 is enabled. |
| 16:42.33 | Ashley` | I think that I "hm" too much xD |
| 16:44.33 | sixwheeledbeast | Maxdamantus: the back cover does have a magnet to control mounting and unmounting /media/mmc1 |
| 16:44.44 | *** join/#maemo shamus (~shmaus@ip-206-192-193-180.marylandheights.ip.cablemo.net) |
| 16:45.06 | *** join/#maemo raccoon_ (user@ghs/raccoon) |
| 16:49.04 | sixwheeledbeast | hxka: I believe you shouldn't adjust voltages if using SR, this will make the device unstable. Either use SR or "legacy mode" like ideal, starving etc... not both. |
| 16:49.57 | *** join/#maemo heroux (~heroux@5070835B.static.ziggozakelijk.nl) |
| 16:50.27 | freemangordon | hxka: you should not touch the voltages when using SR |
| 16:50.49 | hxka | freemangordon: Thanks, that's what I thought |
| 16:51.26 | freemangordon | hxka: BTW I did not fix SR VDD2 calibrations the unlike those for VDD1, maybe this is the reason |
| 16:51.41 | *** join/#maemo NIN101 (~core@n900.quitesimple.org) |
| 16:51.45 | *** join/#maemo shentey (~shentey@wlan-141-23-99-29.tubit.tu-berlin.de) |
| 16:51.59 | hxka | freemangordon: Can I help somehow with this? |
| 16:52.10 | freemangordon | hxka: yep, just a minute to check something |
| 16:52.16 | hxka | Sure |
| 16:52.56 | freemangordon | could you gimme the output of "cat /sys/power/efuse_vdd2" |
| 16:53.06 | freemangordon | Gatta_Negra: hi! |
| 16:53.14 | freemangordon | how's your hal sensor? |
| 16:53.58 | Ashley` | http://ix.io/a4Q <-- this is what I get when I boot a kernel from u-boot |
| 16:54.12 | kerio | which kernel is this? |
| 16:54.15 | Ashley` | after a few seconds device turn's off |
| 16:54.21 | Ashley` | stock with framebuffer |
| 16:54.26 | Ashley` | from pali's pack |
| 16:54.43 | freemangordon | ashley: do you pass atags from u-boot to the kernel? |
| 16:54.44 | Ashley` | http://atrey.karlin.mff.cuni.cz/~pali/u-boot-images_2012.04-1.tar.gz |
| 16:54.46 | Ashley` | from there |
| 16:55.08 | freemangordon | hxka: did you see ^^^ about /sys/... ? |
| 16:55.12 | kerio | mh |
| 16:55.14 | hxka | freemangordon: http://paste.kde.org/p2760daa5 |
| 16:55.17 | freemangordon | thanks |
| 16:55.18 | kerio | pali's not online so idk |
| 16:55.27 | Ashley` | freemangordon, I don't know, I use bootmenu.d/*.item from this pack |
| 16:55.36 | kerio | ask freemangordon, he's usually our surrogate Pali |
| 16:56.04 | Ashley` | there is "ITEM_REUSEATAGS="1"" in there |
| 16:56.11 | freemangordon | hmm, weird |
| 16:56.21 | *** part/#maemo Ashley` (me@unaffiliated/ashley/x-5226587) |
| 16:56.36 | *** join/#maemo Ashley` (me@unaffiliated/ashley/x-5226587) |
| 16:56.38 | Ashley` | oops |
| 16:56.43 | *** join/#maemo shentey (~shentey@wlan-141-23-99-29.tubit.tu-berlin.de) |
| 16:56.52 | Ashley` | I accidendaly parted |
| 16:57.07 | *** join/#maemo VDVsx (~VDVsx@a88-114-88-95.elisa-laajakaista.fi) |
| 16:57.15 | freemangordon | Ashley`: : wait, you should use u-boot from repos afaik |
| 16:57.25 | Ashley` | u-boot is from repos |
| 16:57.44 | Ashley` | I just got kernel with framebuffer consolle from that thread, to see what's going on |
| 16:57.55 | Gatta_Negra | freemangordon, no progress |
| 16:58.01 | freemangordon | Gatta_Negra: :( |
| 16:58.06 | freemangordon | why is that? |
| 16:58.18 | Gatta_Negra | i am having construction works and repair works at the apartment so i did not have any time to deal with it |
| 16:58.25 | freemangordon | oh, I see |
| 16:58.32 | Gatta_Negra | i am even moving back to htc until better times |
| 16:58.46 | freemangordon | oh, htc is better? |
| 16:58.53 | Gatta_Negra | no, just faster |
| 16:58.57 | freemangordon | heh |
| 16:58.58 | Gatta_Negra | <PROTECTED> |
| 16:59.04 | Gatta_Negra | <PROTECTED> |
| 16:59.30 | Gatta_Negra | but i love my n900 and i will keep it for future experiments |
| 16:59.39 | freemangordon | kerio: could you give the output from "cat /sys/power/efuse_vdd2" |
| 16:59.39 | Gatta_Negra | it can work without sim card also |
| 17:00.02 | kerio | freemangordon: k one sec |
| 17:00.04 | freemangordon | Gatta_Negra: what is that HTC does but n900 doesn't? out of curiosity |
| 17:00.46 | kerio | freemangordon: 009aceef 009a94b3 00aac695 |
| 17:02.23 | freemangordon | hxka: kerio: yeah, the same shit like with VDD1 calibrations :( |
| 17:02.31 | kerio | wut |
| 17:02.48 | freemangordon | the third calibration value is one and the same on every device |
| 17:03.05 | kerio | ok whatevs |
| 17:03.07 | freemangordon | 00aac695 |
| 17:03.36 | freemangordon | well, I guess I should make another patch |
| 17:06.11 | Ashley` | freemangordon, any idea? (with that u-boot) :/ |
| 17:07.25 | freemangordon | hmm, no. so you can't boot any kernel with u-boot installed? |
| 17:09.03 | Ashley` | yup |
| 17:09.25 | Ashley` | kernel-power kernel-cssu, nokia kernel |
| 17:10.06 | Ashley` | it hangs up at "starting kernel..." and shut's down after a few seconds |
| 17:10.43 | Ashley` | (with that kernel with framebuffer it shows kernel panic, and shuts down after few seconds) |
| 17:13.54 | freemangordon | Ashley`: the only thing I can think of is that your rootfs is screwed somehow. |
| 17:14.48 | freemangordon | Ashley`: you you somehow managed to install some wrong version of u-boot |
| 17:14.58 | freemangordon | *or* you |
| 17:15.01 | *** join/#maemo robotanarchy (~robotanar@g228082173.adsl.alicedsl.de) |
| 17:16.17 | Ashley` | I've flashed that rootfs today (with emmc ofc) |
| 17:16.42 | Ashley` | and it boots and works fine without u-boot |
| 17:17.06 | Ashley` | I've tried uboot from extras and extras-devel (aren't they the same version?) |
| 17:17.10 | Ashley` | brb |
| 17:17.43 | freemangordon | Ashley`: what HW revision is your device? |
| 17:18.44 | Ashley` | 2101 |
| 17:19.37 | *** join/#maemo dos11 (~dos@unaffiliated/dos1) |
| 17:19.51 | freemangordon | same as mine |
| 17:19.55 | Ashley` | hi, dos11 :) |
| 17:20.41 | freemangordon | Ashley`: I'm afraid you'll have to wait for Pali to appear |
| 17:21.18 | Ashley` | oh, okay. Thanks :) |
| 17:22.34 | Ashley` | freemangordon, what's his nickname here? (so my xchat can notify me when he come) |
| 17:22.51 | freemangordon | its Pali, but he is MIA |
| 17:23.34 | Ashley` | MIA? |
| 17:23.42 | Ashley` | What does that mean? :s |
| 17:24.00 | hxka | Missing In Action |
| 17:24.05 | Ashley` | Oh. |
| 17:29.02 | freemangordon | yeah, his laptop is in repairing for the last ~2 months :( . at least I hope this is still the reason |
| 17:30.52 | DocScrutinizer05 | ((<TTilus> uh oh, why would i need the host key of old n900?)) either that, or you edit (or just delete) ~/.ssh/known_hosts on your PC you try to connect to N900 from |
| 17:32.02 | DocScrutinizer05 | you also might have to reset known_hosts on N900 |
| 17:33.07 | DocScrutinizer05 | aaah, you failed with password entry on N900. Yes that's another reason |
| 17:34.34 | *** join/#maemo fuz_ (nobody@vau75-10-88-164-23-88.fbx.proxad.net) |
| 17:35.25 | *** join/#maemo bef0rd (~bef0rd@unaffiliated/beford) |
| 17:37.00 | *** join/#maemo BCMM (~user@unaffiliated/bcmm) |
| 17:39.21 | *** join/#maemo dos11 (~dos@77-253-198-199.adsl.inetia.pl) |
| 17:39.30 | *** join/#maemo dos11 (~dos@unaffiliated/dos1) |
| 17:41.20 | *** join/#maemo trx (ns-team@devbin/founder/trx) |
| 17:42.03 | *** join/#maemo trx (ns-team@devbin/founder/trx) |
| 17:42.17 | Ashley` | freemangordon, I've found something |
| 17:42.21 | Ashley` | freemangordon, http://mg.pov.lt/maemo-ssu-irclog/%23maemo-ssu.2012-07-19.log.html#t2012-07-19T15:08:15 |
| 17:44.17 | DocScrutinizer05 | Ashley`: install correct modules |
| 17:46.52 | *** join/#maemo stef_204 (~kvirc@unaffiliated/stef-204/x-384198) |
| 17:46.58 | *** join/#maemo scoobertron (~tom@93.186.147.22) |
| 17:47.25 | freemangordon | DocScrutinizer05: he has a different problem |
| 17:47.33 | freemangordon | the modules are in place |
| 17:47.36 | DocScrutinizer05 | she, but... yeah, maybe |
| 17:47.53 | freemangordon | she? ok :) |
| 17:48.21 | DocScrutinizer05 | aah, nope. He |
| 17:48.47 | freemangordon | DocScrutinizer05: the same problem with kernel failing to mount rootfs after u-boot, -ENODEV |
| 17:49.17 | DocScrutinizer05 | or maybe she. Dank, is Ashley` same as ashley? |
| 17:49.23 | DocScrutinizer05 | dnag even |
| 17:49.36 | Ashley` | she, and nope :P |
| 17:49.49 | Ashley` | I don't even know who ashley is :P |
| 17:49.57 | DocScrutinizer05 | joe phenix |
| 17:50.06 | DocScrutinizer05 | jack |
| 17:50.10 | DocScrutinizer05 | whatever |
| 17:50.11 | Ashley` | (I still don't know xD) |
| 17:50.30 | DocScrutinizer05 | our wiki maintainer |
| 17:51.31 | *** join/#maemo kwtm (~kwtm@173.200.183.221) |
| 17:52.46 | joga | heh some days ago got a spare n900 and, well, gf came back from a trip with a dislocated usb connector on hers, nice timing |
| 17:52.58 | DocScrutinizer05 | aynway, yes it seems I missed some details in your problem report. It's a nasty thing in uBoot that sometimes causes uBoot to fail epically. Dunno if it's related to uBoot version or whatever |
| 17:52.59 | joga | bah, just got it tweaked for my work use :p |
| 17:53.13 | joga | will borrow it to her anyway until I get the connector fixed |
| 17:53.31 | joga | (if possible) |
| 17:53.33 | DocScrutinizer05 | prolly an incompatibility between uBoot fake memory config reported to kernel, and actual hardware in device |
| 17:54.12 | DocScrutinizer05 | joga: |
| 17:54.15 | DocScrutinizer05 | ~usbfix |
| 17:54.15 | infobot | extra, extra, read all about it, usbfix is http://talk.maemo.org/showthread.php?t=75920 - and **NEVER** use epoxy (unless you want to seal your device for underwater) |
| 17:54.54 | DocScrutinizer05 | it's always possible, just sometimes not exactly easy |
| 17:58.07 | *** join/#maemo vakkov_ (~vakko@84.54.169.189) |
| 17:58.20 | joga | yeah, need to do some research and open the thing at least first |
| 17:58.40 | joga | no rush so I'll just set up the spare for her first |
| 18:05.06 | Ashley` | hm... |
| 18:05.14 | Ashley` | is there kexec for maemo? |
| 18:05.50 | joga | I can't find "Copy from SIM card" in contacts again :F |
| 18:06.25 | joga | it's in phone mode, showing reception, pin given and in contacts there's just sync from other device, import from new account and import contacts (file/folder) |
| 18:06.45 | joga | though I did enter phone mode only after it was booted |
| 18:07.02 | hxka | Ashley`: Yeah, in kernel-power |
| 18:07.25 | hxka | And there is kexec-tools package in extras-testing and devel |
| 18:07.31 | hxka | Didn't test it though |
| 18:08.02 | Ashley` | oh, I see. Thanks. |
| 18:12.35 | hxka | joga: try pkill osso-addressbook |
| 18:12.45 | Ashley` | Is there any alternative to u-boot? :P |
| 18:12.55 | joga | hxka, ah, probably would've helped, reboot did at least |
| 18:14.26 | DocScrutinizer05 | Ashley`: not really |
| 18:14.48 | Ashley` | :c |
| 18:15.05 | DocScrutinizer05 | Ashley`: OTOH yiu actually don't need uBoot except for nitdroid and that's .... not needed either |
| 18:15.23 | Ashley` | i want to boot archlinux :P |
| 18:15.29 | DocScrutinizer05 | ooh |
| 18:15.57 | Ashley` | (I have it in chroot... had (reflash), but watchdoge doesn't like pacman) |
| 18:16.16 | DocScrutinizer05 | your problem AFAIK is with your RAM banks hw config |
| 18:16.34 | Ashley` | is it fixable somehow? |
| 18:16.49 | DocScrutinizer05 | well, probably in uBoot it actually is fixable |
| 18:18.03 | DocScrutinizer05 | or just maybe you actually got a bad block in your kernel partition |
| 18:19.40 | DocScrutinizer05 | I don't know how NOLO/stock-kernel is handling bad blocks, but somehow they are supposed to do |
| 18:20.20 | *** join/#maemo raandoom (~raandoom@178.170.206.11) |
| 18:20.37 | DocScrutinizer05 | alas all this is pretty obscure, thanks to NOLO being a blob |
| 18:20.41 | Ashley` | can I check somehow if I've got bad blocks? |
| 18:21.53 | DocScrutinizer05 | err yep, there is some way to check. Seems your link you posted refers to a IRC chat that relates to it |
| 18:22.43 | DocScrutinizer05 | another possible approach is to cat /dev/mtd<kernel> and compare to the content supposed to be there |
| 18:25.13 | DocScrutinizer05 | mtd_utils seem to have some useful functions |
| 18:26.41 | *** join/#maemo t3st3r (~t3st3r@gateway/tor-sasl/t3st3r) |
| 18:27.06 | DocScrutinizer05 | mtdinfo /dev/mtd3 |
| 18:27.13 | DocScrutinizer05 | doesn't show bad blocks |
| 18:29.13 | DocScrutinizer05 | Eraseblock size: 131072 bytes, 128.0 KiB |
| 18:29.15 | DocScrutinizer05 | Amount of eraseblocks: 16 (2097152 bytes, 2.0 MiB) |
| 18:29.55 | Ashley` | I'll just give up, meh. |
| 18:30.01 | DocScrutinizer05 | one bad block might already suffice to reduce available space below the threshold where uBoot(+kernel) fits. even when bad blocks are handled correctly |
| 18:31.18 | DocScrutinizer05 | Ashley`: could you please do a `cat /dev/mtd3 >kerneldump.bin` and provide that file somewhere for analysis? |
| 18:31.21 | Ashley` | okay |
| 18:32.04 | DocScrutinizer05 | ooh wait, you can't get that done except in rescueOS, since when you flash uBoot it doesn't boot any normal kernel anymore, right? |
| 18:32.31 | Ashley` | i can boot it from flasher-3.5 |
| 18:32.50 | DocScrutinizer05 | well, a dump of stock kernel NAND partition will help too. It still should indicate if there are bad blocks |
| 18:33.07 | Ashley` | I'm on kp52 now |
| 18:33.09 | DocScrutinizer05 | Ashley`: right, you can load kernel to RAM |
| 18:33.09 | hxka | Apparently there is nandtest to check if blocks are bad |
| 18:33.21 | DocScrutinizer05 | hxka: NOOOOOO! |
| 18:33.42 | DocScrutinizer05 | STAY AWAY FROM NANDTEST! |
| 18:34.08 | Ashley` | DocScrutinizer05, http://ashley.re/kernel.bin |
| 18:34.12 | DocScrutinizer05 | it's a sure way to semi-brick your N900 |
| 18:34.21 | DocScrutinizer05 | Ashley`: thanks |
| 18:34.27 | Ashley` | it is 2.6.28.10-power52 |
| 18:34.42 | hxka | Well, OBVIOUSLY you'll have to reflash kernel after that |
| 18:34.42 | Ashley` | i think |
| 18:35.45 | DocScrutinizer05 | hxka: yeah, or reflash CAL after accidentally erasing the config partition |
| 18:36.36 | DocScrutinizer05 | nandtest doesn't know about partitions afaik |
| 18:37.02 | hxka | Oh wait |
| 18:37.09 | hxka | <PROTECTED> |
| 18:37.18 | DocScrutinizer05 | good luck! |
| 18:37.35 | Ashley` | DocScrutinizer05, can I disable watchdog somehow? |
| 18:37.41 | DocScrutinizer05 | yes |
| 18:37.44 | DocScrutinizer05 | flasher |
| 18:38.08 | DocScrutinizer05 | --no-foobarwd |
| 18:38.13 | DocScrutinizer05 | or sth like that |
| 18:38.28 | DocScrutinizer05 | there are 3(?) different wds |
| 18:38.35 | *** join/#maemo at1as (~at1as@kurios.r4780y.com) |
| 18:39.20 | Ashley` | DocScrutinizer05, but it's not persistent, yep? |
| 18:39.24 | hxka | flasher --set-rd-flags=no-omap-wd,no-ext-wd,no-lifeguard-reset |
| 18:39.40 | hxka | also --enable-rd-mode |
| 18:40.00 | Ashley` | Because watchdog is rebooting my phone when I try to pacman -S whatever |
| 18:40.00 | *** join/#maemo mavhc (~mavhc@cpc65310-basf8-2-0-cust204.12-3.cable.virginmedia.com) |
| 18:40.13 | hxka | Ashley`: it's persistent until you run flasher with --disable-rd-mode |
| 18:41.02 | DocScrutinizer05 | Ashley`: it is persistent |
| 18:41.04 | *** join/#maemo florian (~fuchs@sign-4db6b041.pool.mediaWays.net) |
| 18:41.04 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 18:41.06 | Ashley` | but, Is it good to run phone in that r&d mode all the time? |
| 18:41.37 | DocScrutinizer05 | no |
| 18:41.44 | hxka | Well, it drains your battery because of constant kb backlight |
| 18:41.56 | DocScrutinizer05 | it eats more battery, and watchdogs are for there a reason |
| 18:42.29 | Ashley` | I dont like random reboots :f |
| 18:42.49 | DocScrutinizer05 | kb backlight is not constant but signalling SoC clock etc. And it can get disabled via a sysfs node |
| 18:43.12 | DocScrutinizer05 | but there is other stuff that's enabled in R&D mode, like uart3 (serial console) |
| 18:43.29 | *** join/#maemo ArGGu^^ (~ArGGu^^@a88-112-166-127.elisa-laajakaista.fi) |
| 18:43.43 | Ashley` | I just want to install packages in arch chroot without reboots |
| 18:43.53 | *** join/#maemo konelix (~konelix@190.148.61.155) |
| 18:44.14 | DocScrutinizer05 | hmm, that's a problem with swap hogging CPU |
| 18:44.25 | DocScrutinizer05 | aiui |
| 18:46.41 | DocScrutinizer05 | a ulimit for pacman might already help |
| 18:47.00 | ShadowJK | Not exactly hogging cpu |
| 18:47.39 | ShadowJK | Just that the cpu has nothing to do. |
| 18:47.39 | ShadowJK | As code isn't coming in from storage fast enough |
| 18:47.41 | t3st3r | OMAP seems to have slow I/O. |
| 18:47.50 | ShadowJK | Not particulary |
| 18:48.05 | t3st3r | when it swaps, whole system works slowly and getting unresponsive. |
| 18:48.27 | ShadowJK | Because the storage is slow |
| 18:48.31 | DocScrutinizer05 | well, that's a property of... *every* system |
| 18:48.45 | t3st3r | [22:47:34] <DocScrutinizer05> a ulimit for pacman might already help <- yep, it would just crash or malfunction due to lack of RAM :) |
| 18:49.03 | DocScrutinizer05 | then pacman is defect |
| 18:49.19 | t3st3r | swap suxx on every system but on n900 it can be so bad it would cause watchdog reboot :D |
| 18:49.55 | ShadowJK | ashley; dunno what kind of setup you have, but, if you're running on MicroSD, get a fast one, I recommend Samsung Pro, Sandisk Extreme (available in two speed grades, the slower rated one is faster), or Sandisk Ultra android edition |
| 18:50.00 | DocScrutinizer05 | no, on N900 you *have* a wd that reboots, while other usual PCs don't |
| 18:50.16 | Ashley` | ShadowJK, I don't have microsd :P |
| 18:50.22 | ShadowJK | Don't use ext2, it's uber slow on flash. ext4 is preferrable |
| 18:50.31 | t3st3r | [22:49:57] <DocScrutinizer05> then pacman is defect <- no, that's how memory allocation failures are looking :) |
| 18:50.40 | ShadowJK | echo 8192 > /sys/block/mmcblk0/queue/nr_requests |
| 18:50.48 | DocScrutinizer05 | t3st3r: I'm no noob |
| 18:50.56 | ShadowJK | Speeds up IO quite alot IME |
| 18:50.59 | *** join/#maemo darkschneider (~gab@93-32-37-160.ip31.fastwebnet.it) |
| 18:51.28 | DocScrutinizer05 | when pacman fails with malloc when no 512MB+ of memory available, then pacman *is* broken in my book |
| 18:51.32 | t3st3r | DocScrutinizer05> in fact PC can have watchdog too. But it both more rare to have watchdog on PC and it's harder to make it swapping SO badly. |
| 18:51.34 | ShadowJK | t3st3r; I have swap on microsd, I've never experienced watchdog reboot due to swapstorm :) |
| 18:51.40 | b1101 | can someone help me with dbus-scripts. I'm trying to make someplayer skip to next track with zoom keys. The latest cssu update broke it |
| 18:51.46 | ShadowJK | And I've sometimes been up to gig of swap in use :s |
| 18:51.52 | DocScrutinizer05 | t3st3r: thanks, never heard of that¡ |
| 18:51.58 | t3st3r | [22:51:15] <ShadowJK> Don't use ext2, it's uber slow on flash. ext4 is preferrable <- are there recent kernels for n900 to run it safely? |
| 18:52.42 | t3st3r | DocScrutinizer05> IIRC N900 is really paranoid about watchdogs: 2 watchdogs + some software monitor. |
| 18:52.54 | DocScrutinizer05 | so? |
| 18:53.04 | ShadowJK | t3st3r; also PC even with slow laptop harddrive has 100+ IOPS performance, the N900 emmc is <10, cheap SD cards around 1. SSDs 10,000 or more. |
| 18:53.34 | ShadowJK | t3st3r; kernel-power has backported ext4 |
| 18:53.48 | DocScrutinizer05 | b1101: what's zoom keys? |
| 18:53.56 | t3st3r | ShadowJK> as I told I got impression OMAP I/O is "quite slow". Though idea with fast SD could work I guess. |
| 18:53.57 | *** join/#maemo xes (~xes@unaffiliated/xes) |
| 18:54.06 | b1101 | the volume key |
| 18:54.25 | t3st3r | but still, i/o with SD or eMMC tend to cause CPU load. |
| 18:54.32 | ShadowJK | t3st3r; my Asus tablet with nvidia tegra has "slower I/O" than N900 :) |
| 18:54.52 | DocScrutinizer05 | a particularly funny idea to abuse volume keys for something other than volume control during mp3 playback |
| 18:54.55 | DocScrutinizer05 | but well |
| 18:55.01 | b1101 | DocScrutinizer05, http://talk.maemo.org/showthread.php?t=70405&page=52 the last post. I have no idea what to do with those things |
| 18:55.43 | t3st3r | ShadowJK> oh, really? :D |
| 18:56.18 | ShadowJK | t3st3r; the big issue is that writing anything takes seconds in the worst case, and there's loads of little writes going on all the time... the worst case scenario becomes more likely the more stuff is going on simultaneously, which also creates greater memory pressure, so stuff is constantly waiting for some piece of code to get read in, but first needs to wait for the write to complete |
| 18:57.02 | ShadowJK | t3st3r; yes, that tablet has a slower emmc than N900.. |
| 18:58.05 | *** join/#maemo Aggese (~Durand@ghs/durand) |
| 18:58.10 | ShadowJK | Quad core, but the cores mostly idle, and nothing happens in browser, browser having first written url history then checking disk cache blocked until adding the url to url history completes |
| 18:59.34 | t3st3r | ShadowJK> I guess in worst case it's infamous bug 12309 could kick in. |
| 18:59.36 | povbot | 04Bug https://bugs.maemo.org/12309 menu icon not graphical |
| 18:59.48 | ShadowJK | Roughly speaking, a 8 megabyte write takes just as long as a 4 kilobyte write, updating a database file involves something like minimum 4 such 4k writes, which works out to the equivalent of writing a 32 megabyte file... |
| 18:59.51 | t3st3r | bot, you lame :P |
| 19:00.26 | t3st3r | flash is block device... |
| 19:00.38 | ShadowJK | It pretends to be a block device |
| 19:01.34 | t3st3r | It is actually a block device. Minimum write unit is page (several kb). But sometimes it takes erase of large block (hundreds Kb or more). |
| 19:01.39 | DocScrutinizer05 | ~wiki erasepage |
| 19:02.04 | *** join/#maemo KhertanAtwork (~KhertanAt@nax2.naxos-fr.net) |
| 19:02.06 | ShadowJK | t3st3r; the emmc in my asus tablet has 8M erase block |
| 19:02.11 | t3st3r | Some advanced controllers with more than 1 IC attached can operate on "erase groups", these are even more. |
| 19:02.37 | ShadowJK | 4M, 6M, 8M and 12M "effective" erase blocks are thee norm now |
| 19:02.46 | t3st3r | Maybe more than 1 flash IC attached and controller haves erase group width 8Mb? |
| 19:02.56 | ShadowJK | possibly |
| 19:03.51 | ShadowJK | From my point of view it's not much of a difference whether it's 2x4M grouped together or 1x8M, the net result is the same, worst case the emmc does 8M read-modify-write for every request |
| 19:03.57 | DocScrutinizer05 | I don't see how all this factoid-tossing is helping Ashley` |
| 19:04.54 | ShadowJK | nr_requests bigger and swap on uSD should sort out ashley |
| 19:04.55 | t3st3r | DocScrutinizer05> to be honest I don't see how to help with it at all. Maybe fast SDHC with swap on it could improve it a bit? |
| 19:04.57 | DocScrutinizer05 | b1101: I don't know |
| 19:05.55 | t3st3r | also maybe thumb build would help? More RAM for programs after all. |
| 19:05.57 | DocScrutinizer05 | t3st3r: thanks! |
| 19:06.19 | ShadowJK | Larger queue size helped me, I saw an increase in average request size as reported by iostat, which means less read-modify-write type write amplification on the emmc, which means higher net throughput :D |
| 19:06.58 | t3st3r | ShadowJK> is this tunable system-wide? |
| 19:07.14 | ShadowJK | It's per block device |
| 19:07.46 | t3st3r | ahh then it looks like nice thing to try to select better blocking for flash devices. |
| 19:08.28 | *** join/#maemo hubutm20 (~hubutm20@79.113.82.213) |
| 19:08.43 | DocScrutinizer05 | Ashley`: after t3st3r stopped discussing basics with ShadowJK, I suggest you ask ShadowJK what he suggests to improve the watchdog timeout problem |
| 19:08.46 | ShadowJK | With modern kernel we'd use the flash aware I/O scheduler, and the flash friendly filesystem (f2fs) :) |
| 19:09.06 | ShadowJK | <ShadowJK> Don't use ext2, it's uber slow on flash. ext4 is preferrable |
| 19:09.17 | ShadowJK | <ShadowJK> echo 8192 > /sys/block/mmcblk0/queue/nr_requests |
| 19:09.59 | t3st3r | [23:09:40] <ShadowJK> With modern kernel we'd use the flash aware I/O scheduler, and the flash friendly filesystem (f2fs) :) <- I wonder if it possible on n900 :D |
| 19:10.03 | Ashley` | thanks, i'll try (i need to install arch again - i was reflashing my device today) |
| 19:11.07 | t3st3r | as for ext2/3 you can try to hint it to use stride supposedly equal to erase block of card. |
| 19:11.22 | DocScrutinizer05 | *sigh* |
| 19:11.24 | ShadowJK | Before I changed that tunable, large highspeed file transfers were basically impossible for me |
| 19:11.25 | t3st3r | and it could be "ext3 minus journal". |
| 19:11.45 | t3st3r | ShadowJK> what kernel you use for ext4? |
| 19:11.55 | DocScrutinizer05 | :-S |
| 19:12.03 | t3st3r | in 2.6.28 it was experimental/unsafe oO |
| 19:12.10 | ShadowJK | t3st3r; ext wouldn't allow it, but I wanted to try run with gigantic journal, on the order of 32g journal on 64g card |
| 19:12.27 | ShadowJK | t3st3r; power52, it has backported ext4 fixes |
| 19:12.50 | t3st3r | oh, really? So it haves less scary ext4? |
| 19:13.04 | DocScrutinizer05 | RLY |
| 19:13.22 | ShadowJK | yes |
| 19:13.45 | ShadowJK | I think Estel runs ext4 /home |
| 19:14.05 | ShadowJK | me too lazy to edit startup scripts and only have it on uSD |
| 19:14.21 | ShadowJK | (and a bunch of speed critical stuff from /home on uSD and symlinked) |
| 19:14.55 | t3st3r | because originally there was a lot of bugs fixed, up to total volume blow-up. |
| 19:15.01 | ShadowJK | ya |
| 19:15.31 | DocScrutinizer05 | that's why we got backports of a working version |
| 19:15.35 | t3st3r | and I only dared to use Ext4 at about 2.6.38 or so... |
| 19:15.56 | ShadowJK | It's not a fair comparison, but I've blown up the ext3 on $home about 5 times, and ext4 on uSD 0 times |
| 19:16.20 | t3st3r | I havent blown up any EXTs because I'm careful :) |
| 19:16.31 | DocScrutinizer05 | heads out |
| 19:18.23 | *** join/#maemo nox- (noident@freebsd/developer/nox) |
| 19:18.32 | ShadowJK | btw, I think the misconception that I/O is busywait comes from the myriad of cpu monitors that treat all not-idle cpu time as busy, and shows widget claiming cpu is fully utilized :) |
| 19:21.00 | *** join/#maemo mavhc (~mavhc@cpc65310-basf8-2-0-cust204.12-3.cable.virginmedia.com) |
| 19:21.16 | ShadowJK | Despite my optimized setup, the typic web browsing session for me is 20-30% cpu wa, meaning that the cpu was idling despite processes wanting to run, as i/o the process depends on is in progress |
| 19:21.38 | *** join/#maemo eMHa (~mh@HSI-KBW-37-49-78-45.hsi14.kabel-badenwuerttemberg.de) |
| 19:22.41 | ShadowJK | Or in other words, 30% of websurfing system load consists on waiting for the emmc and uSD to do their job :/ |
| 19:25.52 | DocScrutinizer05 | ShadowJK: I wasn't to suggest cpu was busy-waiting. Hogged meant something different than busy in my staement |
| 19:28.46 | DocScrutinizer05 | the real problem I think is [swapd] not doing preemption |
| 19:29.21 | Ashley` | DocScrutinizer05, what you're going to do with that kernel.bin from me? |
| 19:29.47 | DocScrutinizer05 | maybe I find time to compare it to a "sane" image |
| 19:30.23 | Ashley` | ah... one thing... |
| 19:30.48 | Ashley` | You wanted me to do that dump with u-boot flashed into nand? |
| 19:31.47 | ShadowJK | It's kinda funny how much my finetuning of my N800 has changed over the years, as I've continously upgraded the SD cards in it |
| 19:32.11 | ShadowJK | I wonder if it's already past the point where the SD cards have more CPU power than the N800 itself :) |
| 19:32.29 | ShadowJK | DocScrutinizer05; what do you mean by preemption? |
| 19:32.55 | DocScrutinizer05 | I mean kernel can't run [wd] |
| 19:34.10 | ShadowJK | Well it would run it if it was still in ram |
| 19:34.50 | DocScrutinizer05 | yeah, not sure if a 'normal' (even kernel) process is supposed to block kernel from multitasking |
| 19:34.55 | *** join/#maemo arcean (~arcean@apn-31-2-38-88.dynamic.gprs.plus.pl) |
| 19:35.22 | t3st3r | waiting for the emmc and uSD to do their job :/ <- means it could theoretically be 30% faster at same horsepower :) |
| 19:35.34 | DocScrutinizer05 | then otoh sw-reset (wd) could as well be the dsme one, or whoknowswhat |
| 19:35.57 | ShadowJK | this is backupmenu's watchdog software: |
| 19:36.05 | ShadowJK | ( while true ; do echo x ; sleep 1 ; done ) > $dev 2>/dev/null < /dev/null & |
| 19:36.42 | ShadowJK | I wonder what process does the equivalent in fremantle... mce? |
| 19:36.44 | DocScrutinizer05 | yeah, that's how all watchdogs work |
| 19:36.51 | DocScrutinizer05 | dsme |
| 19:36.57 | *** join/#maemo unclouded (~neil@2001:4428:200:80fc:7e05:7ff:fe0d:d421) |
| 19:37.21 | DocScrutinizer05 | and another one is embedded in kernel I guess |
| 19:37.33 | DocScrutinizer05 | disclaimer: AFAIK |
| 19:38.00 | DocScrutinizer05 | Ashley`: don't worry |
| 19:38.27 | ShadowJK | So if dsme isn't in ram when its timer expires, and there's heavy I/O going on, it probably doesn't make it back in time |
| 19:38.47 | DocScrutinizer05 | :nod: |
| 19:38.56 | DocScrutinizer05 | though dsme should be ram-locked |
| 19:39.25 | DocScrutinizer05 | (dunno how that's done but I know it is possible and used in maemo a lot) |
| 19:39.33 | *** join/#maemo mvp_ (~mvp@80-62-116-39-mobile.dk.customer.tdc.net) |
| 19:40.08 | Ashley` | DocScrutinizer05, http://talk.maemo.org/showthread.php?t=68125 |
| 19:40.16 | Ashley` | DocScrutinizer05, there is something about ramlocking |
| 19:40.23 | ShadowJK | might be intentional, when a relatively small thing like dsme doesn't respond quickly enough, the UI responds even slower, so intentionally let it reboot? |
| 19:45.58 | ShadowJK | 319M swap in use on N800 :) |
| 19:52.28 | *** join/#maemo ZogG_laptop (~ZogG_lapt@funtoo/user/ZogG) |
| 20:16.47 | t3st3r | ShadowJK> do you have N800? |
| 20:16.58 | t3st3r | that old tablet from Nokia? |
| 20:17.25 | ShadowJK | I have a N800, N810, 4 broken N900, 2 working N900 |
| 20:18.10 | *** join/#maemo shentey (~shentey@g225173074.adsl.alicedsl.de) |
| 20:18.26 | Ashley` | <ShadowJK> <ShadowJK> echo 8192 > /sys/block/mmcblk0/queue/nr_requests |
| 20:18.42 | ShadowJK | oh |
| 20:18.44 | Ashley` | can't create /sys/block/.../nr_requests: Read only filesystem |
| 20:18.54 | ShadowJK | missing an iosched in that path somewhere |
| 20:19.21 | ShadowJK | /sys/block/mmcblk0/queue/nr_requests |
| 20:19.31 | ShadowJK | hm |
| 20:19.36 | ShadowJK | looks identical :P |
| 20:19.55 | ShadowJK | Look around in /sys/block/mmcblk0/ for it? |
| 20:20.05 | Ashley` | there is io_shed |
| 20:20.13 | Ashley` | iosched* |
| 20:20.26 | Ashley` | but there isn't nr_requests |
| 20:20.43 | Ashley` | (also, I can't for example change sheduler) |
| 20:20.46 | ShadowJK | what kernel is this |
| 20:20.51 | Ashley` | (i could some time ago...) |
| 20:20.52 | Ashley` | kp52 |
| 20:21.18 | ShadowJK | same here |
| 20:21.39 | ShadowJK | You dont want anything except cfq anyway |
| 20:22.39 | Ashley` | (i was just testing something with scheduler) |
| 20:22.49 | Ashley` | (anyway, it was in /sys, and it wasn't ro...) |
| 20:22.57 | Ashley` | brb... |
| 20:23.14 | ShadowJK | I have in /sys/block/mmcblk*/queue/ : hw_sector_size max_hw_sectors_kb nomerges read_ahead_kb scheduler iosched max_sectors_kb nr_requests rq_affinity |
| 20:23.25 | ShadowJK | is mmcblk1 present in /sys and more populated? |
| 20:24.08 | Ashley` | oh, wait |
| 20:24.17 | Ashley` | there isnt mmcblk0 |
| 20:24.24 | Ashley` | there is mmcblk0p* |
| 20:24.27 | Ashley` | brb |
| 20:26.11 | Ashley` | uh |
| 20:26.13 | Ashley` | nope |
| 20:26.15 | Ashley` | sorry |
| 20:26.20 | ShadowJK | mmcblk0p is different |
| 20:26.26 | Ashley` | i forgot about -d switch |
| 20:26.39 | Ashley` | and i did ls /sys/block/mmc* |
| 20:27.00 | Ashley` | instead ls -d /sys/block/mmc* |
| 20:27.02 | Ashley` | :P |
| 20:27.11 | *** join/#maemo valeriusL (~valerius@85.26.183.72) |
| 20:28.07 | gregoa | 37 |
| 20:28.17 | gregoa | *sigh* |
| 20:31.39 | *** join/#maemo messerting (~messertin@cm-84.209.22.230.getinternet.no) |
| 20:34.01 | *** join/#maemo valerius (~user@85.26.183.72) |
| 20:36.53 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 20:43.14 | hxka | Ashley`: That's why tab completion exists |
| 20:52.21 | *** join/#maemo Mike11 (~Mike@unaffiliated/mike11) |
| 20:54.35 | *** join/#maemo LauRoman (~LauRoman@5-14-92-51.residential.rdsnet.ro) |
| 21:04.05 | hxka | Ashley`: I checked your kernel.bin, it's ok |
| 21:05.17 | Ashley` | oh, thanks |
| 21:05.53 | Ashley` | But it means that I still dont know what causes the problem :f |
| 21:14.18 | *** join/#maemo SmilyOrg (Smily@89.142.254.252) |
| 21:20.49 | *** join/#maemo APTX_ (~APTX@unaffiliated/aptx) |
| 21:27.03 | *** join/#maemo BCMM (~BCMM@unaffiliated/bcmm) |
| 21:28.01 | DocScrutinizer05 | probably your memory hw architecture then |
| 21:28.25 | DocScrutinizer05 | my initial suspition |
| 21:28.51 | DocScrutinizer05 | suspicion* |
| 21:29.46 | *** part/#maemo mkaindl (~mkaindl@ama-dablam.markus-kaindl.de) |
| 21:29.51 | DocScrutinizer05 | could somebody check a x86-linux "bug" I seem to encounter? |
| 21:30.10 | *** join/#maemo mkaindl (~mkaindl@ama-dablam.markus-kaindl.de) |
| 21:31.46 | xes | bug? |
| 21:33.19 | DocScrutinizer05 | in X11 make your kbd numlock LED shine. (I.E. set numlock). Then switch to console (ctrl-alt-F1). switch back to X11 (usually alt-F7). watch numlock LED. press SHIFT-key-> LED off. press capslock ->numlock+capslock LED on. (press capslock again to unlock capslock) |
| 21:34.45 | DocScrutinizer05 | can you reproduce this or is it just me? |
| 21:35.54 | xes | i suppose it's just you . ...Going to console the numlock led remains in the same condition |
| 21:35.55 | hxka | I can reproduce it |
| 21:36.35 | DocScrutinizer05 | xes: yes |
| 21:38.56 | DocScrutinizer05 | hxka: thanks |
| 21:39.19 | DocScrutinizer05 | I guess it's a bug in kbd LED control driver |
| 21:40.20 | DocScrutinizer05 | at least finally I managed to find how to reproduce it. Before it drove me nuts at times |
| 21:40.41 | xes | DocScrutinizer05: sorry, can't reproduce (kde 4.11.5, kernel 3.12.8) |
| 21:42.25 | DocScrutinizer05 | kde 4.8.5 (4.8.5) "release 2" |
| 21:42.57 | DocScrutinizer05 | kernel 3.4.63-2.44-desktop |
| 21:43.01 | xes | ..but i remember that the kde version of fedora 17 had some strange numlock issue (kde 4.9.?) |
| 21:43.26 | *** join/#maemo r00t_ (~r00t@dyndsl-095-033-125-195.ewe-ip-backbone.de) |
| 21:43.46 | DocScrutinizer05 | 4.8.5 seems close enough to 4.9 |
| 21:43.58 | *** join/#maemo mvp_ (~mvp@80-62-116-229-mobile.dk.customer.tdc.net) |
| 21:45.46 | xes | could be related: https://bugs.kde.org/show_bug.cgi?id=183308 |
| 21:45.48 | povbot | 04Bug 183308: was not found. |
| 21:46.24 | *** join/#maemo githogori_ (~githogori@c-50-156-58-163.hsd1.ca.comcast.net) |
| 21:47.03 | xes | https://bugs.kde.org/show_bug.cgi?id=183308#c31 |
| 21:47.04 | povbot | 04Bug 183308: was not found. |
| 21:50.45 | *** join/#maemo beford (~frod@unaffiliated/beford) |
| 22:00.56 | DocScrutinizer05 | rather exactly my issue than just related |
| 22:08.35 | jaska | <PROTECTED> |
| 22:08.38 | jaska | hmmm. |
| 22:09.33 | *** join/#maemo kraft (kraft@gateway/shell/blinkenshell.org/x-kmpjdcxwijnspjdr) |
| 22:11.54 | DocScrutinizer05 | hmm? |
| 22:12.02 | jaska | i dont remember it growing that big |
| 22:12.12 | DocScrutinizer05 | err |
| 22:13.24 | DocScrutinizer05 | user 1766 0.0 0.2 3936 536 ? Ss 2013 0:00 /usr/bin/hildon-status-menu |
| 22:13.25 | DocScrutinizer05 | user 1768 0.2 3.1 98240 7620 ? Ssl 2013 248:12 /usr/bin/hildon-status-menu |
| 22:13.46 | jaska | ah ok. was just remembering wrong then as i updated my ancient cssu |
| 22:16.47 | Maxdamantus | the numlock should change as you switch between the console and Xorg, if it's in a different state in both. |
| 22:17.33 | Maxdamantus | each console can have the locks in different states. |
| 22:19.15 | Maxdamantus | remembers writing programs that read and wrote to devices in /dev/input/* to make the lights make funny patterns as you typed. |
| 22:23.10 | Maxdamantus | ah, nvm, didn't understand the problem at first. |
| 22:38.25 | *** join/#maemo bef0rd (~bef0rd@unaffiliated/beford) |
| 22:43.09 | r00t_ | DocScrutinizer05: did you know http://archive.is/lP093 (http://wiki.meego.com/ARM/N900/Using_Rescue_Initrd), an n900 rescue system to be loaded into ram via flasher? |
| 22:43.39 | DocScrutinizer05 | hmm? |
| 22:43.51 | r00t_ | you can boot it even if your rootfs is shot |
| 22:43.58 | DocScrutinizer05 | ~rescueos |
| 22:43.58 | infobot | somebody said rescueos was http://n900.quitesimple.org/rescueOS/ |
| 22:44.39 | r00t_ | "This project is _NOT_ the meego rescue initrd." |
| 22:44.39 | r00t_ | k |
| 22:45.18 | DocScrutinizer05 | http://n900.quitesimple.org/rescueOS/documentation.txt |
| 22:45.42 | r00t_ | that's what i copied from, yes |
| 22:46.39 | *** join/#maemo valeriusL (~valerius@85.26.186.207) |
| 22:47.17 | r00t_ | anyway, thanks... should have found that earlier |
| 22:48.47 | DocScrutinizer05 | wow, wiki.meego.com still exists? thought they nukes meego.com completely |
| 22:48.54 | DocScrutinizer05 | nuked* |
| 22:49.24 | r00t_ | that url is a copy of that one page |
| 22:49.31 | DocScrutinizer05 | aaah |
| 22:51.12 | DocScrutinizer05 | sorry, I'm a tad grumpy |
| 22:51.33 | DocScrutinizer05 | thanks for letting us know, anyway |
| 22:52.51 | r00t_ | i was just wondering why i did not run into that (or rescueos) earlier... seems a bit underdocumented |
| 22:53.19 | DocScrutinizer05 | hmm yeah, rescueOS for sure could use some more PR |
| 22:53.37 | DocScrutinizer05 | nin101 is a shy sissi ;-P |
| 22:54.21 | DocScrutinizer05 | ~factinfo rescueos |
| 22:54.21 | infobot | rescueos -- created by DocScrutinizer05 <~HaleBopp@openmoko/engineers/joerg> at Sun Sep 2 16:57:34 2012 (508 days); last modified at Thu Aug 29 14:08:40 2013 by kerio!~kerio@Maemo/community/contributor/kerio; it has been requested 49 times, last by DocScrutinizer05, 10m 23s ago. |
| 22:54.26 | DocScrutinizer05 | hmm |
| 22:54.52 | r00t_ | the meego reascue image has the cute advatange of not having a keyboard map, and having usb networking but no single network client or server |
| 22:55.07 | kerio | lol |
| 22:55.26 | DocScrutinizer05 | yeah |
| 22:55.29 | DocScrutinizer05 | ;-P |
| 22:55.35 | DocScrutinizer05 | extremely useful |
| 22:55.50 | r00t_ | the only special characters you can type are <>., cursor keys and enter |
| 22:56.03 | DocScrutinizer05 | :nod: |
| 22:56.14 | DocScrutinizer05 | absolutely sufficient, no? X-P |
| 22:56.21 | r00t_ | yeah :D |
| 22:56.21 | kerio | sshd<RET> |
| 22:56.29 | DocScrutinizer05 | ooh, i guess you have <tab> |
| 22:56.30 | r00t_ | kerio, as i said, no clients or servers |
| 22:56.34 | r00t_ | no tab either |
| 22:56.39 | kerio | ...oh |
| 22:56.58 | r00t_ | and busybox has a - in it's name, so you can't call applets that are not symlinked (like telnetd?) |
| 22:57.21 | r00t_ | well, i guess rescueos is a bit better, will try |
| 22:57.38 | DocScrutinizer05 | ctrl-i ? |
| 22:57.56 | DocScrutinizer05 | rescueos is awesome, I heard |
| 22:57.59 | r00t_ | good one |
| 22:59.40 | DocScrutinizer05 | on maemo.cloud-7 there's an older version that still uses a kernel compatible with the stock maemo kernel |
| 23:00.05 | DocScrutinizer05 | nin101 thought it's leete to go for new kernel |
| 23:00.08 | DocScrutinizer05 | iirc |
| 23:00.31 | r00t_ | thanks, will try... |
| 23:00.33 | r00t_ | later |
| 23:06.08 | *** join/#maemo sil_ (~sil@dialup-62-11-104-233.clienti.tiscali.it) |
| 23:07.21 | DocScrutinizer05 | http://maemo.cloud-7.de/NIN101_N900_rescue_os/nin101.uni.cx/n900-new/206.253.166.96/N900/rescueOS/CHANGELOG |
| 23:13.03 | *** join/#maemo Kabouik (~quassel@23.114.95.79.rev.sfr.net) |
| 23:16.34 | DocScrutinizer05 | ShadowJK: nice -20 swapoff /dev/mmcblk1p2 && #<-- does that really work? (the nice -20) |
| 23:16.54 | r00t^home | i like how rescueos contains 'fdformat' |
| 23:17.05 | DocScrutinizer05 | lol |
| 23:17.34 | DocScrutinizer05 | messybox-paua, eh? |
| 23:18.21 | r00t^home | well, at least all applets are linked, unlike on the meego initrd |
| 23:23.12 | DocScrutinizer05 | ShadowJK: actually my mind boggles form those 5 scriptlines in http://enivax.net/jk/n900/reswap.sh.txt |
| 23:23.58 | DocScrutinizer05 | swapon /dev/mmcblk0p3 >/dev/null 2>&1 || echo cow |
| 23:24.00 | DocScrutinizer05 | nice -20 swapoff /dev/mmcblk1p2 && |
| 23:24.01 | DocScrutinizer05 | iostat -md mmcblk0p2 | grep mmcblk0p2 | awk '{print $6}' >/root/reswap.stat |
| 23:24.03 | DocScrutinizer05 | /home/user/swapon -p 10 /dev/mmcblk1p2 && |
| 23:24.04 | DocScrutinizer05 | nice -20 swapoff /dev/mmcblk0p3 && |
| 23:24.06 | DocScrutinizer05 | swapon /dev/mmcblk0p3 |
| 23:24.19 | DocScrutinizer05 | ------ last two lines are especially mindboggling |
| 23:25.41 | DocScrutinizer05 | without the last line it might make sense |
| 23:28.41 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 23:33.31 | DocScrutinizer05 | ShadowJK: aiui you rely on nice -20 blocking the parent script from execution until the background process finished? |
| 23:39.54 | *** join/#maemo grinsekatze (~andreas@potyomkin.org) |
| 23:39.54 | *** join/#maemo grinsekatze (~andreas@unaffiliated/grinsekatze) |
| 23:54.53 | *** join/#maemo shamus (~shmaus@ip-206-192-193-180.marylandheights.ip.cablemo.net) |