| 00:11.03 | dnix | hem, how to start manually an X session in familiar? |
| 00:11.20 | dnix | I would like to start matchbox at startup :( |
| 00:19.58 | psokolovsky | dnix: /etc/init.d/gpe-dm start |
| 00:20.52 | dnix | I would like to no install gtk |
| 00:22.33 | dnix | Ihave a h3630 and I want to have a small X in rom and opie in my cf card |
| 00:22.33 | psokolovsky | then why you need X at all? |
| 00:22.33 | psokolovsky | dnix: that's useless |
| 00:22.33 | dnix | why? |
| 00:22.33 | psokolovsky | no, you tell why ;-) |
| 00:22.49 | dnix | a min X will grant to me access to my data and if I want to use the apps, then I switch to opie |
| 00:22.54 | dnix | looks logic |
| 00:24.10 | psokolovsky | X grants access to data?? well, good luck, I personally don't understand you. X is GUI server, not data access framework. |
| 00:25.03 | dnix | yeah, but with a min X I can type inside my console commands to do ssh, configure wifi etc etc (this is what I mean for access data) |
| 00:27.21 | psokolovsky | whoa! cool! the you'd better know how to start X in the configuration you need. there's no startx. to run X server, run Xfbdev. still, look into gpe-dm for standard params to it. |
| 00:27.35 | psokolovsky | (still, it's wastage, why don't stick to opie sole?) |
| 00:28.12 | dnix | because it's no granted that the cf card stay always mounted :( |
| 00:29.19 | psokolovsky | dnix: then, stop wasting your time, join 2.6 port team, and make sure that kernel will behave the way you need ;-) |
| 00:29.34 | dnix | I would really like if only I was able to write something usefull! |
| 00:29.48 | dnix | I would also help to port familiar to h6300 |
| 00:29.51 | dnix | etc etc |
| 00:29.57 | dnix | but I'm not a good C coder :( |
| 00:30.35 | dnix | but if you want I can try to get more involved |
| 00:31.45 | *** join/#handhelds orospakr (n=orospakr@bas4-ottawa23-1177611383.dsl.bell.ca) |
| 00:31.56 | dnix | uhm... how to solve this: update-rc.d: /etc/init.d/opie: file does not exist |
| 00:32.26 | psokolovsky | dnix: if you want ;-) |
| 00:32.45 | psokolovsky | dnix: you apparently have opie not installed (or some important package) |
| 00:33.20 | dnix | yeah, as I want to put all the qt thing in my cf card, I've started from a console image |
| 00:33.35 | dnix | created a dest opie /media/cf in ipkg |
| 00:33.40 | dnix | and now installing |
| 00:34.12 | dnix | anyway, I would be interest in try to do something usefull |
| 00:34.38 | *** join/#handhelds mithro (n=tim@lester.mithis.com) |
| 00:42.08 | dnix | hehehe |
| 00:42.10 | dnix | solved... |
| 00:42.37 | psokolovsky | dnix: one not overcomplex, but utterly useful task you could do is to make defconfigman support for h3600... |
| 00:42.43 | psokolovsky | dnix: good for you ;-) |
| 00:43.20 | dnix | psokolovsky: if somebody teach to me how to do it I would be pleased! |
| 00:44.03 | psokolovsky | dnix: see http://defconfigman.sf.net . Check out from SVN. Do like other machines do. Voila. |
| 00:44.23 | dnix | ok! |
| 00:56.55 | mzb | psokolovsky: now have a 2.4 device to add to the testing pool :) |
| 00:57.20 | mzb | serial power-adapter mod works with it too (bonus!) |
| 00:57.45 | mzb | so I think I'll add my pics+instructions to a new wiki page |
| 00:58.24 | mzb | (I didn't get definitive results on hx4700, but this confirms that the mod works on devices other than h2200) |
| 01:04.12 | dnix | hem, why in distro there isn't familiar? |
| 01:16.00 | dnix | ok, good night, tomorrow I will play with defconfigman :-D |
| 01:16.04 | *** part/#handhelds dnix (n=denix@gra94-5-82-226-239-102.fbx.proxad.net) |
| 01:25.49 | *** join/#handhelds noclouds (n=mhfan@218.22.26.90) |
| 01:44.36 | *** join/#handhelds emte_ (n=emte@d64-180-45-14.bchsia.telus.net) |
| 02:38.04 | *** join/#handhelds ricmm (i=ricmm@201.208.134.108) |
| 02:52.34 | *** join/#handhelds kb7sqi (n=kb7sqi@cpe-075-183-106-019.triad.res.rr.com) |
| 03:08.32 | *** join/#handhelds kb7sqi (n=kb7sqi@cpe-075-183-106-019.triad.res.rr.com) |
| 03:25.24 | *** join/#handhelds mithro (n=tim@lester.mithis.com) |
| 03:31.00 | *** join/#handhelds LeedsHK (i=1000@pcd415219.netvigator.com) |
| 04:14.21 | *** join/#handhelds emte__ (n=emte@d64-180-45-14.bchsia.telus.net) |
| 04:19.48 | *** join/#handhelds aquadran (i=aquadran@scummvm/undead/aquadran) |
| 04:27.53 | *** join/#handhelds Seth_F (n=hunterkl@host-65-125-48-97.clearviewcatv.net) |
| 04:32.01 | mzb | new wiki page created to power connector mod: http://www.handhelds.org/moin/moin.cgi/HpIpaqPowerAdapterMod |
| 04:58.19 | *** join/#handhelds emte (n=emte@d64-180-45-14.bchsia.telus.net) |
| 04:59.30 | *** join/#handhelds hvontres|home (n=hvontres@adsl-75-35-103-170.dsl.sndg02.sbcglobal.net) |
| 05:34.07 | *** join/#handhelds goxboxlive (n=goxboxli@176.84-48-210.nextgentel.com) |
| 05:35.36 | *** join/#handhelds emte_ (n=emte@d64-180-45-14.bchsia.telus.net) |
| 05:53.05 | *** join/#handhelds sadeness_ (n=LamersIn@nat1.rlan.ru) |
| 06:02.10 | *** join/#handhelds zap (n=zap@16.170.249.ozerki.net) |
| 06:45.29 | *** join/#handhelds hvontres|home (n=hvontres@adsl-75-35-103-170.dsl.sndg02.sbcglobal.net) |
| 06:53.30 | *** join/#handhelds bluelightning (n=blueligh@125-237-74-233.jetstream.xtra.co.nz) |
| 06:57.57 | bluelightning | hi mzb |
| 06:58.03 | bluelightning | did your h5550 arrive safely? |
| 06:58.44 | bluelightning | heh just got your email this second :) |
| 07:01.13 | mzb | bluelightning: cool ;) |
| 07:01.24 | mzb | any hints on getting battery into learning state? |
| 07:01.47 | bluelightning | not really, I have to admit that I didn't use it a lot |
| 07:02.01 | bluelightning | it was given to me in exchange for some PC fixing work I did for someone |
| 07:02.07 | mzb | I'm currently on serial console, all services stopped, and everything (!) but h5400_asic unloaded |
| 07:02.09 | mzb | ah |
| 07:02.25 | mzb | can't get it to go below 3823 mV |
| 07:02.46 | mzb | then it just dies |
| 07:03.08 | mzb | I've done a full charge (?) and discharge (twice?) |
| 07:03.09 | bluelightning | there is this page: http://handhelds.org/moin/moin.cgi/battery_20learning_20_28hp55xx_29 |
| 07:03.36 | mzb | yes, I've been using that |
| 07:03.46 | bluelightning | ah ok |
| 07:03.55 | mzb | keep getting this: |
| 07:03.57 | mzb | root@h5550:~# cat /proc/asic/battery |
| 07:03.58 | mzb | Unable to read DS2760 battery monitor |
| 07:04.14 | mzb | I have seen the real thing ... but not sure how/when |
| 07:05.01 | mzb | unplugging the power when fully charged (says something around 4200 mV?) then gives me 9995 mV !!! |
| 07:05.22 | mzb | and it's just died again |
| 07:05.24 | mzb | hmmm |
| 07:05.27 | bluelightning | doh :( |
| 07:05.32 | bluelightning | not sure I can help I'm afraid... you might try one of the kernel hackers who are working on 2.6 for the h5000 series, perhaps they have a better idea of how it should work |
| 07:05.49 | mzb | can you plug in the battery while it's running on power? |
| 07:06.04 | mzb | ok np ... I'll fiddle/investigate/etc ;) |
| 07:06.05 | bluelightning | IIRC the battery has to be connected for it to even power up |
| 07:06.57 | bluelightning | or, you can short two terminals apparently, but I don't remember which, and I imagine shorting the wrong ones would be extraordinarily bad (TM) |
| 07:06.58 | mzb | yes, dead right :( |
| 07:07.54 | mzb | yes it would be (a short would cause excessive drain) ... you should load it with some resistors, and then monitor it down to a certain voltage ... |
| 07:08.34 | mzb | hmmm ... yes, might have to do it "the hard way" ;) |
| 07:08.57 | mzb | everything else seems pretty ok ... although haven't been able to change volume (oh dear;) |
| 07:09.59 | mzb | multimeter time! |
| 07:11.02 | *** join/#handhelds Chicken (n=Alex@pD9E32529.dip.t-dialin.net) |
| 07:17.01 | mzb | I'm guessing at 3.7V nominal, it's a 3 cell pack ... so I was going to discharge it down to 3V, but it's only reading 2.62 ... *sigh* :) |
| 07:17.46 | mzb | hmmm ... a challenge! |
| 07:39.50 | *** join/#handhelds niv_one_three (n=niv@82.166.207.32) |
| 07:45.54 | mzb | this is confusing me: Unable to read DS2760 battery monitor |
| 07:46.12 | mzb | I'll have to have a look at the source and see what's going on ... another time |
| 07:46.45 | mzb | time to do computer stuff for family :( |
| 07:46.47 | mzb | bbl |
| 07:55.04 | mzb | bluelightning: what was the problem with the old battery? Wouldn't hold a charge, or chip blown? |
| 07:55.50 | bluelightning | It wouldn't hold any charge at all, as soon as you took the battery off it powered down |
| 07:56.27 | bluelightning | erm, I mean as soon as you took the AC off... heh |
| 07:58.38 | mzb | bluelightning: I'm guessing the replacement battery doesn't use the ds2760 (or something?) ... just wondering if it's worth trying to recover the old battery (I've learned a few crude tricks from Dad over the years;) |
| 07:59.05 | mzb | I might open this one up at some stage and investigate |
| 07:59.23 | bluelightning | unfortunately I threw away the old one, so I can't give you that :( |
| 07:59.33 | mzb | ok, np :) |
| 07:59.36 | bluelightning | it had a very hard life so I figured it was totally dead |
| 07:59.39 | mzb | it's strange, because I have seen asic battery info on occasion |
| 08:00.35 | bluelightning | I've certainly heard of cheap replacement batteries not having the proper chips in them |
| 08:00.40 | mzb | sometimes you can shock cells back into life ... flicking 12V car battery across the cells (dangerous!) sometimes "burns" them |
| 08:00.54 | bluelightning | yes I've heard of doing that with nicads |
| 08:01.04 | *** join/#handhelds Marex (n=Marex@85.132.236.161) |
| 08:01.04 | bluelightning | my dad blew up two car battery chargers doing that :/ |
| 08:01.29 | bluelightning | in fact they weren't really chargers they were proper power supplies |
| 08:01.30 | mzb | heh ... yeah charger can't handle the current |
| 08:02.10 | mzb | has to be big lead-acid battery ... and only "millisecond" contact (you don't want the cells to explode!;) |
| 08:02.23 | bluelightning | I'll keep that in mind :) |
| 08:03.06 | mzb | then lot's of charge/discharge cycles (only take down to 1V per cell) |
| 08:03.20 | mzb | sometimes worth the effort ... depends on the battery, I guess |
| 08:03.32 | bluelightning | I guess safety glasses would be desirable for such an operation :) |
| 08:03.47 | mzb | heh ... you'd want a body suit! :) |
| 08:05.46 | mzb | I'll try leaving this on charge overnight to bring it back to normal levels and try a few more experiments ... might not be worth it in the long run, but it's occurred to me that monitoring battery status during ramdiskrescue extraction would probably be a pretty good idea |
| 08:06.09 | mzb | I'm being summoned to pull my finger out ... must go ... talk to you later |
| 08:17.03 | *** join/#handhelds noclouds (n=mhfan@218.22.26.90) |
| 08:18.28 | *** join/#handhelds emte_ (n=emte@d64-180-45-14.bchsia.telus.net) |
| 08:22.24 | *** join/#handhelds mithro (n=tim@ppp246-117.static.internode.on.net) |
| 08:35.06 | *** join/#handhelds emte_ (n=emte@d64-180-45-14.bchsia.telus.net) |
| 08:39.09 | mzb | # modprobe h3600_asic_battery learn_voltage=4000 |
| 08:39.15 | mzb | after a while: |
| 08:39.20 | mzb | <PROTECTED> |
| 08:39.21 | mzb | yay! |
| 08:40.05 | mzb | hmmm: Jan 1 01:15:25 h5550 user.warn kernel: h3600_asic_battery_update: canceling learning |
| 08:40.10 | mzb | heh |
| 08:40.17 | mzb | bugger ... has to wait |
| 08:59.49 | *** join/#handhelds mmp (n=mmp@adsl-d124.84-47-51.t-com.sk) |
| 09:24.20 | *** join/#handhelds zecke (n=ich@91.64.161.147) |
| 09:35.12 | *** join/#handhelds goxboxlive (n=goxboxli@176.84-48-210.nextgentel.com) |
| 09:57.45 | *** join/#handhelds zybl0re_ (n=zybl0re@S010600112f8c4e0a.gv.shawcable.net) |
| 10:11.41 | *** join/#handhelds zybl0re (n=zybl0re@S010600112f8c4e0a.gv.shawcable.net) |
| 10:29.34 | *** join/#handhelds pgfeller (n=pgfeller@170.156.78.83.cust.bluewin.ch) |
| 10:33.11 | *** join/#handhelds mr_nice (n=mr_nice@p54A9F628.dip.t-dialin.net) |
| 10:58.31 | *** join/#handhelds dnix (n=denix@gra94-5-82-226-239-102.fbx.proxad.net) |
| 10:59.11 | dnix | hi all |
| 11:05.28 | *** join/#handhelds \homer (n=flo@dslb-084-059-097-127.pools.arcor-ip.net) |
| 11:11.59 | *** join/#handhelds mr (n=mr_nice@p54a9df78.dip.t-dialin.net) |
| 11:27.28 | *** join/#handhelds pgfeller (n=pgfeller@29.166.78.83.cust.bluewin.ch) |
| 11:33.56 | *** join/#handhelds mr_nice (n=mr_nice@p54A9DC83.dip.t-dialin.net) |
| 11:37.42 | *** join/#handhelds vovkav (n=Andrey@1269.ostrov.net) |
| 11:44.29 | *** part/#handhelds vovkav (n=Andrey@1269.ostrov.net) |
| 12:00.09 | *** join/#handhelds \homer (n=flo@dslb-084-059-097-127.pools.arcor-ip.net) |
| 12:04.28 | *** join/#handhelds hardwalker (n=hardwalk@125-229-196-168.dynamic.hinet.net) |
| 12:10.02 | *** join/#handhelds dariballdesk (n=dariball@p54b1d5a0.dip.t-dialin.net) |
| 12:26.52 | *** join/#handhelds Marex-notebook (n=marex@85.132.236.161) |
| 12:28.57 | *** join/#handhelds jg (n=jg@c-24-218-178-107.hsd1.ma.comcast.net) |
| 12:56.47 | *** join/#handhelds Marex (n=Marex@85.132.236.161) |
| 13:52.17 | *** join/#handhelds Chicken (n=Alex@pD9E32529.dip.t-dialin.net) |
| 14:08.44 | *** join/#handhelds agd5f (n=alex@c-69-143-17-173.hsd1.va.comcast.net) |
| 14:08.58 | *** join/#handhelds reenoo (n=r@p5489E89B.dip.t-dialin.net) |
| 14:09.56 | *** join/#handhelds emte (n=emte@d64-180-45-14.bchsia.telus.net) |
| 14:27.06 | *** join/#handhelds orospakr (n=orospakr@132.213.238.4) |
| 14:33.02 | *** join/#handhelds wolog (n=wolog@brusc.guerrier.com) |
| 14:34.05 | *** join/#handhelds jg (n=jg@c-24-218-178-107.hsd1.ma.comcast.net) |
| 15:00.15 | *** join/#handhelds thaytan (n=jan@core.fluendo.com) |
| 15:25.38 | *** join/#handhelds mzb (n=ubernut@ppp108-88.static.internode.on.net) |
| 15:26.09 | *** mode/#handhelds [+o mzb] by ChanServ |
| 15:30.41 | *** join/#handhelds vovkav (n=Andrey@1269.ostrov.net) |
| 15:33.20 | *** join/#handhelds mmp (n=mmp@158.195.16.153) |
| 15:44.45 | *** join/#handhelds zap (n=zap@16.170.249.ozerki.net) |
| 16:15.12 | *** join/#handhelds jg (n=jg@c-24-218-178-107.hsd1.ma.comcast.net) |
| 16:37.08 | *** join/#handhelds emte_ (n=emte@d64-180-45-14.bchsia.telus.net) |
| 17:03.15 | *** join/#handhelds dfox (n=dfox@r5cv25.net.upc.cz) |
| 17:09.44 | *** join/#handhelds mmp (n=mmp@TheWide.ubyt.sdjls.uniba.sk) |
| 17:12.32 | *** join/#handhelds chazco (n=chazco@AC9FBC75.ipt.aol.com) |
| 17:15.24 | *** join/#handhelds yann (n=dwitch@nan92-1-81-57-214-146.fbx.proxad.net) |
| 17:16.05 | *** part/#handhelds chazco (n=chazco@AC9FBC75.ipt.aol.com) |
| 17:29.44 | *** join/#handhelds Seeraa (n=dennis@195.158.181.64) |
| 17:33.10 | *** part/#handhelds vovkav (n=Andrey@1269.ostrov.net) |
| 17:41.52 | *** join/#handhelds goxboxlive (n=goxboxli@176.84-48-210.nextgentel.com) |
| 18:01.11 | *** join/#handhelds mmp_ (n=mmp@TheWide.ubyt.sdjls.uniba.sk) |
| 18:36.33 | *** join/#handhelds gremlin[it] (n=gremlin@217.201.15.92) |
| 18:48.01 | *** join/#handhelds exastra (n=go@c-24-21-152-246.hsd1.mn.comcast.net) |
| 18:48.54 | *** part/#handhelds exastra (n=go@c-24-21-152-246.hsd1.mn.comcast.net) |
| 18:49.17 | *** join/#handhelds exastra (n=go@c-24-21-152-246.hsd1.mn.comcast.net) |
| 20:14.52 | *** join/#handhelds avkig (i=ariel@gateway/tor/x-c971a7681781c777) |
| 20:15.15 | *** join/#handhelds emte (n=emte@d64-180-45-14.bchsia.telus.net) |
| 20:18.00 | *** join/#handhelds BabelO (n=Fabrice@lun34-2-82-238-28-28.fbx.proxad.net) |
| 20:18.08 | BabelO | hi |
| 20:25.51 | *** join/#handhelds goxboxlive (n=goxboxli@176.84-48-210.nextgentel.com) |
| 20:30.23 | *** part/#handhelds dnix (n=denix@gra94-5-82-226-239-102.fbx.proxad.net) |
| 20:34.21 | *** join/#handhelds dnix (n=denix@gra94-5-82-226-239-102.fbx.proxad.net) |
| 20:36.16 | *** join/#handhelds zybl0re (n=zybl0re@S010600112f8c4e0a.gv.shawcable.net) |
| 20:38.16 | *** join/#handhelds Disconnect (n=dis@c-68-48-132-97.hsd1.md.comcast.net) |
| 20:38.26 | *** join/#handhelds ricmm (n=ricmm@201.208.134.108) |
| 20:39.34 | *** join/#handhelds Jakkes (n=root@h208015.upc-h.chello.nl) |
| 20:41.48 | Jakkes | dir |
| 20:46.02 | *** join/#handhelds \homer (n=flo@dslb-084-059-097-127.pools.arcor-ip.net) |
| 20:52.14 | *** join/#handhelds unique311 (n=unique31@ool-457ae2a6.dyn.optonline.net) |
| 20:54.08 | Marex | aquadran, ping |
| 20:54.14 | Marex | aquadran, hi, are you around? |
| 20:56.31 | aquadran | Marex: yes |
| 20:57.23 | Marex | aquadran, I found out, that on PalmTC 2 INput GPIOs and 3 OUTput GPIOs has something to do with WiFi |
| 20:57.33 | Marex | dont you think its a bit too less? |
| 20:58.13 | aquadran | Marex: heh, i'm not ported of PalmTC :) |
| 20:58.34 | Marex | aquadran, youre working on mypal 716 |
| 20:58.40 | aquadran | yes |
| 20:58.50 | Marex | which is nearly the same ;] we talked about it some time ago |
| 20:58.58 | aquadran | ah, right |
| 20:59.26 | Marex | hmm ... but still ... I cant find any other gpios :] |
| 20:59.52 | Marex | I think those two inputs may be for 2 sockets ... |
| 21:00.30 | Marex | and those three outputs ... hmm ... wifi power, reset, add ? |
| 21:02.51 | aquadran | Marex: i don't know, it might be done differenlty. mypal wifi use more gpo pins |
| 21:03.31 | Marex | aquadran, thats why Im curious about it, but there arent any more :-/ |
| 21:04.05 | aquadran | Marex: mypal have two input. each one for each slot. card ready |
| 21:05.00 | Marex | aquadran, which I doubt is important on TC since it has only one slot with wifi |
| 21:05.07 | Marex | you cant plug CF card into TC |
| 21:05.09 | aquadran | Marex: 6 output for cf slot2(wifi) |
| 21:05.21 | aquadran | but two of them are for wifi chipset |
| 21:05.43 | aquadran | POWER 1.8V and POWER_N 3.3V |
| 21:05.59 | aquadran | that have from wifi module specs |
| 21:06.06 | Marex | I looked at that driver ... yeah |
| 21:06.42 | aquadran | mypal seems have some lowlevel control of cf slots |
| 21:06.50 | aquadran | what for so many pins |
| 21:06.52 | aquadran | ? |
| 21:07.19 | *** join/#handhelds mmp (n=mmp@TheWide.ubyt.sdjls.uniba.sk) |
| 21:07.22 | Marex | hmm ... Ill try trusting those three pins are some power, reset and something ;] |
| 21:07.46 | aquadran | Marex: how use pins i found from dissassembly original driver |
| 21:07.47 | Marex | but I still havent found out why both of those two inputs are on when wifi is on |
| 21:08.06 | Marex | aquadran, :] ok |
| 21:08.10 | aquadran | wifi chipset doesn't have reset pin |
| 21:09.07 | Marex | cf slot does have, doesnt it< |
| 21:09.08 | Marex | ? |
| 21:09.19 | aquadran | yes |
| 21:10.06 | Marex | aquadran, well ... I got to those five gpios by dumping all gpios with wifi on and off ... |
| 21:10.09 | Marex | hmm ... |
| 21:10.33 | aquadran | Marex: it might be handled by hardware, and you might need only simply power on and reset |
| 21:10.49 | aquadran | Marex: i did same way :) |
| 21:11.18 | Marex | Ill just try all possible permutations and see :b |
| 21:11.30 | Marex | it wont take long I guess ... there are 27 of them |
| 21:11.51 | aquadran | heh, it started work for me by trying combinations :] |
| 21:12.11 | aquadran | but at least i have some dissassembly info |
| 21:12.40 | Marex | hmm ... me and objdump ... two enemies :b |
| 21:14.54 | *** join/#handhelds broken_star (n=broken_s@pD9E07924.dip.t-dialin.net) |
| 21:15.00 | broken_star | hello everyone |
| 21:15.11 | broken_star | thought to try my luck on this channel |
| 21:15.18 | broken_star | anyoneonly? |
| 21:15.31 | broken_star | online* |
| 21:20.49 | Marex | broken_star, nah :b |
| 21:21.07 | broken_star | hi Marex |
| 21:21.14 | Marex | hi broken_star |
| 21:21.27 | broken_star | so i take u r an expert on familiar? |
| 21:21.29 | broken_star | :) |
| 21:22.16 | mmp | broken_star: just ask question:) |
| 21:22.40 | broken_star | i finally managed to install familiar on my iPAQ and made it to run properly, but now i have a weird problem for some time |
| 21:22.49 | broken_star | and this is the brightness of the display |
| 21:22.56 | broken_star | it has become very very dark now |
| 21:23.18 | broken_star | and no matter how much i try to put it high, it stays the same, :( |
| 21:23.57 | broken_star | it happened after the iPAQ woke up from suspend mode, i have restarted it couple of times but no luck |
| 21:24.10 | broken_star | could someone pls tell where might be the problem? |
| 21:24.54 | broken_star | ohhhhhhh |
| 21:26.24 | broken_star | and now just when i am typing, i touched the screen and the display is back to its normal. very strange indeed! thanx for ur time guys |
| 21:27.00 | Marex | heh |
| 21:40.26 | *** join/#handhelds joss193 (n=joss193@dhcp-18-128.cable.infonet.ee) |
| 21:40.51 | joss193 | hi, tffs as a partition identifier, someone aware of this type.. |
| 21:41.14 | joss193 | seems there is tffs subdir in device catalogue rather than mtd/ |
| 21:48.02 | aquadran | Marex: heh, i like this. just enter channel, ask question and shortly exit without chance anyone wrote answer :) |
| 21:48.53 | Marex | aquadran, as I never seen it ;] |
| 21:49.06 | Marex | aquadran, but its fun :b |
| 21:49.33 | aquadran | Marex: i saw such thing quite a lot :) |
| 21:49.40 | Marex | aquadran, I feel like Im close to pcmcia |
| 21:49.59 | Marex | ah ... dang :D |
| 21:50.20 | Marex | very interesting ... I killed the device |
| 21:50.47 | joss193 | Marex: refering to me? |
| 21:50.59 | aquadran | Marex: it's rather difficult ... |
| 21:51.55 | Marex | I felt like I was getting close :b |
| 21:52.03 | Marex | joss193, nah ;] |
| 21:52.19 | joss193 | ok any of you guys can tell me one of two, where can i find the configuration of kernel, or two.. possible to overwrite the cramfs image, if the partition is there? |
| 21:52.44 | joss193 | seems here that upon every reboot, the files are renerated again, regarldless that some indeed have rw even |
| 21:52.55 | joss193 | seems like it extracts it from a flash always |
| 21:53.35 | joss193 | possible to overwrite this image without logging to bootloader via jtag and serial cable? |
| 21:54.42 | aquadran | joss193: it would be easier for us if you mention what pda it is ? :) |
| 21:55.08 | joss193 | aquadran: it is samsung i858 with mizi |
| 21:55.28 | aquadran | so it's not officiay supported |
| 21:55.44 | joss193 | yeah, but it is well bundled with linux here.. |
| 21:56.18 | aquadran | joss193: does it have linux originaly ? |
| 21:56.32 | joss193 | aquadran: yeah..this one that i am having really has.. |
| 21:56.45 | joss193 | i mean this one that i have access to |
| 21:57.24 | joss193 | but this is first one i have touched also..and it seems that all of the filesystem is regened upon every reboot |
| 21:57.45 | joss193 | want to do some changes here, like modyfying fstab and such and commit those to flash |
| 21:57.58 | joss193 | for instance change the filesystem type for sd cards |
| 21:58.43 | aquadran | joss193: to where it extract files from flash ? |
| 21:58.46 | aquadran | to ram ? |
| 21:58.52 | joss193 | aquadran: i think so.. |
| 21:59.07 | joss193 | aquadran: but i am not that convienient or sure about it |
| 21:59.21 | joss193 | but it seems like it, at leasst cramfs should refer to this procedure |
| 22:01.01 | joss193 | aquadran: but this is just a usr dir that has this.. |
| 22:01.02 | aquadran | does that linux have some sources for generating image ? |
| 22:01.16 | joss193 | aquadran: yeah i have a utility for that |
| 22:01.34 | joss193 | which should generate an image suitable for their bootloader |
| 22:01.48 | aquadran | joss193: check bootparam cmdline |
| 22:02.07 | joss193 | aquadram: yeah, but i do not have a serial cable |
| 22:02.19 | joss193 | aquadram: i have only usb ether connection.. |
| 22:02.50 | joss193 | aquadram: in other words, howto to check this |
| 22:02.51 | joss193 | ? |
| 22:02.54 | aquadran | joss193: i mean cat /proc/cmdline |
| 22:03.21 | joss193 | yeah ram is there |
| 22:03.25 | joss193 | initrd=0xa1000000,2m root=/dev/ram0 mem=60m console=dummy0 |
| 22:03.45 | joss193 | aquadram: this refers to what? |
| 22:04.06 | aquadran | i think it refer where initrd is in ram |
| 22:04.20 | aquadran | 2m size at 0xa1000000 |
| 22:04.54 | joss193 | aquadram: yeah, but initrd is not in question at the moment.. |
| 22:05.07 | aquadran | bootloader load kernel image and initrd into ram from flash |
| 22:05.10 | joss193 | aquadram: since i have not found the kernel configuration file to rebuild this image |
| 22:05.31 | aquadran | 2.4 or 2.6 kernel ? |
| 22:05.35 | joss193 | 2.4 here.. |
| 22:05.40 | joss193 | 2.4.25 |
| 22:06.16 | joss193 | and armvtel5 or something should be the arm core |
| 22:06.29 | aquadran | look into /boot/config* maybe there is |
| 22:06.48 | aquadran | if /boot exit |
| 22:06.50 | joss193 | have no such dir at all |
| 22:07.13 | aquadran | so kernel and initrd is indeed in flash |
| 22:07.47 | joss193 | aquadran: yeah but i can not reproduce this exaclty if i am missing the configure, or can i |
| 22:07.49 | aquadran | so you propably can't get config from pda |
| 22:08.17 | joss193 | aquadram: can this be rebuilt from modules.dep or some other sources put together? |
| 22:08.34 | *** join/#handhelds ricmm (i=ricmm@201.208.134.108) |
| 22:09.16 | joss193 | ok nontheless..this is not the issue here...seems i have the utility to overwrite the image in flash at least |
| 22:09.20 | aquadran | joss193: from modules.dep you can get list of modules |
| 22:09.37 | joss193 | yeah, but not those that have been build into zimage yes? |
| 22:09.48 | aquadran | yes |
| 22:09.58 | joss193 | that is what i thiugh, perhaps stringing the zimage, might work, but ..ah nevermind |
| 22:10.45 | joss193 | so the question, where can i get the load address for filesystem image in the flash memory? |
| 22:11.00 | *** join/#handhelds \\homer (n=flo@dslb-084-059-100-212.pools.arcor-ip.net) |
| 22:11.37 | aquadran | joss193: bootloader know this |
| 22:12.06 | aquadran | joss193: you have utility, so you don't need to know |
| 22:12.16 | joss193 | aquadran: you think that only bootleader knows this? |
| 22:12.35 | joss193 | aquadran: hmm, this utility takes the device as parameter i think |
| 22:13.00 | aquadran | joss193: what filesytem you mean ? initrd ? |
| 22:13.05 | joss193 | but it do not have files, seems that physical character devices of discs are at /dev/rd/ |
| 22:13.19 | joss193 | aqudran: no root filesystem and home and usr |
| 22:14.10 | aquadran | joss193: that should be in initrd files as it boot from root=/dev/ram0 first |
| 22:14.39 | joss193 | ok, can i grep those locations out+ |
| 22:14.40 | aquadran | check /sbin/initrd if it is script or binary |
| 22:14.54 | aquadran | err /sbin/init |
| 22:15.23 | joss193 | binary |
| 22:15.54 | aquadran | so you should have in /etc/rc0.d ,... |
| 22:16.29 | aquadran | check in /etc/inittab what is default level |
| 22:16.41 | aquadran | for ex. id:2:initdefault: |
| 22:16.43 | joss193 | only thing i have is at init.d/rc.S |
| 22:17.02 | aquadran | so check it what is inside this script |
| 22:17.11 | aquadran | it's always first script |
| 22:17.24 | joss193 | ::sysinit:/etc/init.d/rcS |
| 22:17.31 | joss193 | indeed it is, and this is the first |
| 22:17.39 | joss193 | and this one is a script |
| 22:17.55 | joss193 | which has those partitions marked there..which to mount, same as mount shows |
| 22:18.47 | *** join/#handhelds exastra (n=go@c-24-21-152-246.hsd1.or.comcast.net) |
| 22:19.13 | joss193 | aquadran: you think that fstab is generated from that script? |
| 22:19.22 | joss193 | by that . |
| 22:19.23 | *** part/#handhelds exastra (n=go@c-24-21-152-246.hsd1.or.comcast.net) |
| 22:20.20 | joss193 | doc.o wonder what is that module for |
| 22:20.30 | aquadran | it's driver for flash |
| 22:22.47 | *** join/#handhelds emte (n=emte@d64-180-45-14.bchsia.telus.net) |
| 22:22.56 | joss193 | ok. |
| 22:23.23 | joss193 | Seems that this script mentions all but the actual very root / itself |
| 22:23.40 | joss193 | home is even extracted from tgz file..:) |
| 22:23.48 | aquadran | he |
| 22:26.08 | joss193 | aquadran: which indicates that /dev/root is mounted elswhere.. |
| 22:26.24 | joss193 | and also this script does not reveal thos flash addresses |
| 22:26.48 | joss193 | perhaps there is a utility to do that |
| 22:28.36 | aquadran | do you have /proc/mtd ? |
| 22:29.54 | aquadran | joss193: if home is extracted initrd might be /dev/root |
| 22:30.50 | joss193 | no funny thing i do not have that proc/mtd |
| 22:30.50 | aquadran | maybe it mount rest /usr,.. |
| 22:30.50 | joss193 | aquadran: no initrd is not /dev/root |
| 22:30.50 | joss193 | root filesstem is |
| 22:31.00 | joss193 | which is linked to /dev/rd/0 |
| 22:31.16 | joss193 | initrd is /dev/rd/initrd |
| 22:31.22 | aquadran | rd is initrd |
| 22:31.32 | joss193 | rd means initrd? |
| 22:31.40 | aquadran | rd mean ramdisk |
| 22:32.02 | joss193 | aquadran: which means that root filesystem should be on ramdisk? |
| 22:32.10 | aquadran | possible |
| 22:32.26 | joss193 | this filesystem can be modified, and has ext3 filesystem |
| 22:32.27 | aquadran | at least part of it (base) |
| 22:32.46 | joss193 | but it really forgats the changes after each reboot |
| 22:33.13 | aquadran | so initrd |
| 22:33.42 | joss193 | cat /dev/rd/initrd |
| 22:33.42 | joss193 | cat: /dev/rd/initrd: No such device |
| 22:33.52 | joss193 | allthough it clearly is there.. |
| 22:34.00 | aquadran | you can't cat |
| 22:34.32 | aquadran | but you could with dd |
| 22:34.32 | joss193 | dev/root on / type ext2 (rw) |
| 22:34.46 | joss193 | i could extract the contents with dd? |
| 22:35.12 | joss193 | heh perhaps, i could just rewrite the /dev/root with new image than? |
| 22:35.30 | aquadran | only that which is in ram :) |
| 22:35.55 | aquadran | so do you have /pro/mtd ? |
| 22:36.04 | aquadran | /proc/mtd |
| 22:36.29 | joss193 | aquadram: no |
| 22:36.43 | aquadran | or mtd command ? |
| 22:36.48 | joss193 | nop |
| 22:36.52 | joss193 | nwither is there |
| 22:36.55 | joss193 | is'nt |
| 22:37.00 | joss193 | isn't |
| 22:37.31 | aquadran | what you have when you type 'mount' ? |
| 22:38.04 | joss193 | 6lines ok? |
| 22:38.09 | joss193 | pastebin.. |
| 22:38.09 | aquadran | ok |
| 22:38.56 | joss193 | http://pastebin.ca/516993 |
| 22:39.45 | aquadran | software you have on /dev/tffs/disc0/part1 on /usr type cramfs (ro) |
| 22:39.59 | joss193 | aquadran: yeah.. |
| 22:40.24 | joss193 | aquadran: but i do not know, where it is on the flash |
| 22:40.34 | joss193 | aquadran: and it is ro |
| 22:40.55 | joss193 | ah one line left out |
| 22:41.13 | joss193 | none on /dev/shm/T-flash type supermount (rw,noatime,dev=/dev/mmc/disc0/part1,fs=vfat,tray_lock=never,--,shortname=winnt,iocharset=utf8) |
| 22:41.32 | joss193 | this is needed to be changed to ext3..but it is renerated upon every reboot:) |
| 22:41.59 | aquadran | joss193: you you can replace cramfs on /dev/tffs/disc0/part1 |
| 22:42.18 | joss193 | aquadran: with what? |
| 22:42.24 | joss193 | at etc/fstab? |
| 22:42.49 | aquadran | /etc/fstab is from initrd |
| 22:43.19 | *** part/#handhelds BabelO (n=Fabrice@lun34-2-82-238-28-28.fbx.proxad.net) |
| 22:43.48 | joss193 | ok those..are from flash partitions? but why only read-only? |
| 22:43.57 | aquadran | joss193: do you have more in /dev/tffs/disc0/ except partX ? |
| 22:44.14 | joss193 | disc0 is the only occurance |
| 22:44.24 | joss193 | part1 part2 part3 there |
| 22:44.40 | aquadran | so /dev/tffs/disc0/part1 is like /dev/hda1 |
| 22:44.42 | joss193 | and disc also |
| 22:44.54 | joss193 | aquadran: yeah.. |
| 22:45.50 | joss193 | but it is cramfs and at /usr |
| 22:46.10 | joss193 | how can i tell it not to be cramfs, instead something else, i think i can not |
| 22:46.20 | aquadran | joss193: you could replace by using 'dd' dd if=new_cramfs_file of=/dev/tffs/disc0/part1 but you must be sure to know if you still can restore software if something goes wrong |
| 22:47.07 | joss193 | and i could also use an overlay filesystem.. |
| 22:47.14 | aquadran | joss193: in /etc/fstab, but changes are lost after reboot |
| 22:47.34 | joss193 | aquadran: yeah indeed... |
| 22:47.39 | *** part/#handhelds rmoravcik (n=rmoravci@pc-3s0zt5w2e4y0vzmhnrzq3a21zqajzfw.users.student.utc.sk) |
| 22:47.42 | joss193 | aquadran: how come i not lost the changes? |
| 22:47.46 | aquadran | joss193: so you need replace initrd |
| 22:48.04 | aquadran | with your own changes in initrd |
| 22:48.43 | joss193 | aquadran:ok how can i do this, can't i just replace that /dev/root part , which is the root filesystem? |
| 22:48.52 | aquadran | joss193: do you have more in /dev/tffs/ ? |
| 22:49.12 | aquadran | joss193: initrd is on flash |
| 22:49.19 | aquadran | with kernel |
| 22:49.20 | joss193 | part3 part2 part1 disc0 |
| 22:49.26 | joss193 | this is the contents.. |
| 22:50.15 | aquadran | joss193: you said you have utility |
| 22:50.28 | joss193 | so i need to have access to bootloader to change that? |
| 22:50.50 | joss193 | aquadran: yeah but this says something weird, if i point it to /dev/rd/0 |
| 22:50.51 | aquadran | propably |
| 22:51.45 | aquadran | joss193: do you have /dev/mtd ? |
| 22:51.58 | joss193 | nop |
| 22:52.32 | aquadran | joss193: look into /sbin dir if you have some commands with names flash or doc |
| 22:52.40 | joss193 | this is the thing they do not seem to use mtd config, to renerate those partitions |
| 22:52.46 | aquadran | or /usr/sbin /usr/bin |
| 22:53.37 | aquadran | i think you should have ability to replace kernel and initrd for software upgrade/fixes |
| 22:54.18 | joss193 | by kernel you mean root filesystem? or just the zimage? |
| 22:54.25 | aquadran | image |
| 22:54.44 | joss193 | aquadran: ok but this one is not needed yet actually..step by step |
| 22:54.56 | joss193 | i only want to change /etc/fstab contents |
| 22:55.17 | aquadran | this only mean change initrd in flash |
| 22:55.49 | joss193 | ok, so intrd image should carry this file? |
| 22:56.05 | joss193 | hmm.. |
| 22:56.16 | joss193 | no i can not find such commands |
| 22:56.22 | joss193 | mizi only give imagewrite |
| 22:56.39 | joss193 | http://www.mizi.com/developer/s3c2410x/Linuette_chap_6_en.htm |
| 22:56.55 | joss193 | and somewhere should be a utility called bon |
| 22:57.01 | joss193 | which i have not found |
| 22:57.18 | joss193 | http://www.mizi.com/developer/s3c2410x/index.html |
| 22:57.51 | aquadran | imagewrite use mtd |
| 22:58.20 | aquadran | it seems mtd is not used |
| 22:58.48 | joss193 | aquadran:indeed.. |
| 22:58.56 | joss193 | so this can be a problem here:( |
| 22:59.09 | joss193 | http://www.mizi.com/developer/s3c2410x/Linuette_chap_6_en.htm#chap_f_e |
| 22:59.50 | aquadran | joss193: does samsung don't have any software upgrades ? |
| 23:00.13 | joss193 | aquadran: i do not know much about that..only thing i have is this site |
| 23:00.15 | aquadran | mtd seems not exist in kernel |
| 23:00.58 | aquadran | dmesg tell you anything usefull ? if you have dmesg command :) |
| 23:03.17 | joss193 | tffs: partition 0x1 size 0x4f18000 start offset 0x2000 |
| 23:03.17 | joss193 | tffs: partition 0x2 size 0x276000 start offset 0x4f1a000 |
| 23:03.18 | joss193 | tffs: partition 0x3 size 0x23be000 start offset 0x5190000 |
| 23:04.09 | joss193 | but those are not a problem...you said them contents can be overwritten with dd |
| 23:04.21 | joss193 | thins is with this initrd partitions |
| 23:04.55 | joss193 | dev/rd/initrd and /dev/rd/0 which is linked to /dev/root |
| 23:05.01 | aquadran | none of them have initrd |
| 23:05.02 | joss193 | but there are lots of those |
| 23:05.19 | joss193 | yeah those rd/X have those |
| 23:05.49 | aquadran | joss193: initrd and kernel might be also on diffrent flash chip |
| 23:06.28 | joss193 | aquadran: hm ok, dd their contents i can only reach to this part, which is written to ram? |
| 23:07.06 | joss193 | what happens if i do dd if=someimage of=/root/dev ? |
| 23:07.22 | joss193 | what happens if i do dd if=someimage of=/dev/root (as /dev/rd/0) ? |
| 23:07.39 | joss193 | perhaps it writes this to flash? |
| 23:08.00 | aquadran | joss193: you overwrite current filesystem, but it's in ram only |
| 23:08.57 | joss193 | aquadran: ah, which means that it will diisapear those changes after reboot again.. |
| 23:08.57 | aquadran | nope it's not connected to flash. bootloader load initrd into ram from flash and tell to kernel where is it by command line params |
| 23:09.04 | joss193 | well that tends to be sad, since this runlevel script is there at /etc/also |
| 23:09.48 | joss193 | aquadram: yeah...but those tffs partitions are flash partitions? |
| 23:10.00 | aquadran | yes |
| 23:10.28 | joss193 | one question does not that cramfs refer that it is used from ram? |
| 23:11.04 | joss193 | or it is just a silly filesystem name..intented to be used on ram drive, but used with flash here? |
| 23:11.58 | joss193 | aquadram: in that case since settings have (rw) should those changes there be available adter reboot? |
| 23:12.11 | aquadran | joss193: yes |
| 23:12.53 | joss193 | yes for both questions then, ok..so intrd also manages that, weather those partitions are rw or ro |
| 23:13.02 | joss193 | will do a test then... |
| 23:13.12 | mzb | cramfs is a ro fs, and iirc it was designed by Linux himself (or am I confusing it with something similiar?) |
| 23:13.23 | mzb | s/Linux/Linus/ |
| 23:13.24 | aquadran | cramfs might work like initrd but readlonly, and seem directly from flash partition |
| 23:14.11 | mzb | slightly better compression than initrd too |
| 23:14.33 | mzb | so joss193, to answer one of your questionsm it's not just a silly name |
| 23:15.28 | joss193 | mzb:yeah those are flash partitions, and indeed. those that carry rw can write also , those changes are there after reboot |
| 23:15.38 | aquadran | joss193: i see you have some free space on that flash about 10MB so initrd and kernel maybe is hidden in flash |
| 23:15.44 | joss193 | but software partition comes with ro |
| 23:16.03 | joss193 | df -h output? |
| 23:16.55 | joss193 | http://pastebin.ca/517083 |
| 23:17.26 | joss193 | usr is full as full:) |
| 23:17.51 | mzb | joss193: I was simply referring to your question about cramfs, not partitions. ie. partition != filesystem |
| 23:18.17 | joss193 | mzb: cramfs is filesystem as i understand, no? |
| 23:19.11 | joss193 | mzb: partition is just a reference of a stack of blocks? |
| 23:19.19 | joss193 | -? |
| 23:20.01 | joss193 | nevermind..the problem is how to change this flag of usr partition ro to rw, and contents of initrd then:( |
| 23:20.43 | aquadran | joss193: you can't cramfs is itself readonly from what i know |
| 23:21.19 | aquadran | or i messing with squashfs |
| 23:21.20 | mzb | absolutely |
| 23:21.22 | joss193 | aquadran: ah this does not even matter most, dev/root is more important..since that carries a path directives |
| 23:21.42 | joss193 | and other bootup info |
| 23:21.54 | joss193 | and this runlevel script.. |
| 23:22.55 | joss193 | aquadran: so lets just remind something, you think that this rootfilesystem is also half on ram and half on flash as bootloader says this, correct? |
| 23:23.46 | joss193 | aquadran: so that can mean, that init script changes are written to the flash while fstab are not |
| 23:23.52 | mzb | this should tell you everything you need to know: # cat /proc/mounts |
| 23:23.52 | joss193 | can this be so even? |
| 23:24.02 | mzb | (assuming you have proc mounted) |
| 23:25.14 | joss193 | rootfs / rootfs rw 0 0 |
| 23:25.16 | joss193 | /dev/root / ext2 rw 0 0 |
| 23:25.24 | joss193 | those are the ones at question |
| 23:26.11 | mzb | that would tend to indicate that your root is writable .. what else are you asking? |
| 23:28.18 | joss193 | mzb: yeah but this is only writable to ramdisk, which is flushed at boottime this is the problem here |
| 23:28.18 | mzb | if you compared those entries to a live linux system, I think you'd see something similar |
| 23:28.19 | joss193 | mzb: dev/root is a symlink to those rd dirs that should indicate a ramdisk usage |
| 23:28.19 | joss193 | mzb: and not there is a ramdisk and also a rootfs / what is that line for? |
| 23:29.21 | mzb | if you read my last msg ... you will see that a normal linux system has one too: I can't tell you what it's for. |
| 23:29.57 | joss193 | mzb:yeah but that is the problem, that root that carries the bootime options is really not changable |
| 23:30.29 | mzb | rootfs / rootfs rw 0 0 |
| 23:30.32 | joss193 | like those flash sectors where this information is stored are hidden or such |
| 23:30.38 | mzb | /dev/hda7 / ext3 rw,data=ordered 0 0 |
| 23:30.42 | aquadran | joss193: you need find out if your bootloader can replace initrd |
| 23:30.47 | mzb | that is NOT the problem |
| 23:31.24 | joss193 | aquadran: as this mizi tutorial shows they use mtd which is not actual here..:( |
| 23:32.03 | joss193 | mzb: it is writable and i know fstab contents..but it is writable on ram |
| 23:32.04 | aquadran | joss193: does it refer to that pda ? |
| 23:32.24 | mzb | joss193: you are saying that you can create a file on the root system (ie: # touch /me), and then when you reboot "me" is not there? |
| 23:32.28 | joss193 | aquadran: well that is the thing, i guess not, but i assumed..it is |
| 23:32.45 | *** join/#handhelds jg (n=jg@c-24-218-178-107.hsd1.ma.comcast.net) |
| 23:32.46 | joss193 | i think i519 and i858 have other initrd's |
| 23:33.00 | joss193 | assumed it was |
| 23:33.40 | joss193 | think this board and tutorial there describes procedures for i519 which is slightly different |
| 23:35.55 | mzb | ah, just saw your command line, now I get it .... you'd need to create another initrd and (be able to) write it back to flash at 0xa1000000,2m |
| 23:36.10 | joss193 | aquadran: and there does not seem to be a way to just dissasable the intrd to see..where those hidden partitions are, or sectors that include this data.... |
| 23:36.23 | mzb | _or_ be able to change your command line and boot from something else |
| 23:36.40 | joss193 | mzb: correct, but using what utilities? |
| 23:36.51 | mzb | dd and gzip come to mind |
| 23:37.29 | mzb | # dd if=/dev/ram0 bs=1M count=2 of=myinitrd.gz |
| 23:37.31 | joss193 | mzb: ok seems i can not replace the bootparameters with initrd itself.. |
| 23:39.39 | mzb | might work, but the block size might be all wrong |
| 23:39.54 | joss193 | mzb: how to find out the real one? |
| 23:39.54 | mzb | dunno |
| 23:39.55 | mzb | then you: # gunzip myinitrd.gz |
| 23:39.55 | mzb | # mkdir myinitrd-mnt |
| 23:39.55 | mzb | # mount -o loop myinitrd myinitrd-mnt |
| 23:39.55 | joss193 | mzb: go ahead was planning to do that.. |
| 23:39.58 | joss193 | the thing is, how can i write this to position you refered, and where did you get a value for this |
| 23:40.07 | mzb | you _can_ make changes to the mounted loopback, but it won't compress as well doing it that way ... it's better to copy the whole dir into a new one a compress a new initrd with gzip -9 |
| 23:40.29 | aquadran | joss193: bootparams are passed when kernel start execute |
| 23:40.29 | mzb | from your command line |
| 23:40.40 | joss193 | ok so intrd or zimage hold them? |
| 23:41.34 | joss193 | i know where to pass those with grub, but do not know how with embedded |
| 23:41.34 | mzb | in theory, you *should* be able to shove the recompressed initrd back into the same place while running ... but you'll find out very quickly that if you don't get it right you've got a brick |
| 23:41.49 | aquadran | joss193: it might be fixed int zimage kernel or bootloader as default |
| 23:41.57 | dnix | nite |
| 23:41.59 | *** part/#handhelds dnix (n=denix@gra94-5-82-226-239-102.fbx.proxad.net) |
| 23:42.11 | mzb | the command line tells me that your initrd is 2MB is size starting at certain location ... I'd say the bootloader gets the kernel from a different section of flash |
| 23:42.25 | mzb | (up to 2MB in size) |
| 23:42.57 | joss193 | mzb: yeah but it takes it from ram.. |
| 23:43.22 | joss193 | and if i put it back there, and switch off the phone, the initial is taken again |
| 23:43.22 | aquadran | mzb: that might be in at the end of flash as from begining partitions are placed |
| 23:44.30 | joss193 | mzb: you have a way to sniff those intrid real flash borders where this is loaded by bootloader? |
| 23:44.50 | joss193 | aquadram: i think it is before those three partitions |
| 23:45.01 | mzb | joss193: your cmdline seems to suggest it's taking it from flash, doesn't it? ... or are you suggesting that the bootloader get's the initrd from somewhere else and loads it into ram for the linux kernel? Seems like a lot of effort for little gain |
| 23:45.16 | aquadran | joss193: nope, it's only 0x2000, which is IPL |
| 23:45.27 | joss193 | IPL? |
| 23:45.45 | joss193 | mzb: i thought so..since rd aquadran said is a ramdisk device |
| 23:46.02 | aquadran | doc early bootloader which load second bootloader |
| 23:46.28 | joss193 | dev/root is a symlink to /dev/rd/0 |
| 23:46.45 | joss193 | which holds this / and it seems this comes from ram |
| 23:46.54 | aquadran | 0xa0000000 is ram |
| 23:47.06 | mzb | <PROTECTED> |
| 23:47.35 | joss193 | mzb: ok, so how to put this zimage to place then? |
| 23:47.37 | aquadran | doc is from 0x0 |
| 23:47.45 | mzb | diff? |
| 23:48.29 | joss193 | mzb: you think if i dd the changed zimage back to ram0 it does load a new one after reboot? |
| 23:48.29 | mzb | no |
| 23:48.37 | aquadran | it's not compatible with this info, first partition is 0x4f18000 size and have /usr |
| 23:48.43 | joss193 | i think i need a program that can sniff the location after address to do that |
| 23:49.12 | joss193 | but the thing is i am missing kernel devices for those.. |
| 23:49.24 | joss193 | else it should be easy and obvious |
| 23:50.04 | joss193 | mzb: so you suggest? |
| 23:50.05 | aquadran | joss193: consider also this if you change something wrong, you are not able boot and fix it |
| 23:50.19 | joss193 | aquadran: i know that.. |
| 23:50.30 | mzb | I'd suggest you find a mizi list/channel :) |
| 23:51.02 | joss193 | aquadran: but i will do that, if there is a way to dump the borders of the zimage flash locations |
| 23:51.30 | joss193 | aquadran: sinze i assume that bootlader is the same for those devices..at least i know that.. |
| 23:51.50 | aquadran | joss193: i'm not sure if you understand me. flashing from linux is way one thing |
| 23:51.58 | aquadran | you need do that from bootloader |
| 23:52.29 | joss193 | aquadran: yeah that is what i thought..since kernel just do not see those locations:( |
| 23:52.31 | mzb | can't he use this imagewrite utility? (still sounds like dangerous option;) |
| 23:52.49 | aquadran | kernel not support mtd |
| 23:52.59 | joss193 | mzb: i have no serial cable here |
| 23:53.13 | aquadran | or no mtd partitions defined in kernel driver |
| 23:53.23 | mzb | trying to make life hard(er) for yourself? :) |
| 23:53.39 | joss193 | mzb: eh? |
| 23:53.49 | joss193 | mzb: well i just do not have one.. |
| 23:54.07 | joss193 | mzb: should buy, but i do not know which could work.. |
| 23:54.16 | joss193 | mzb: that usbserial is ment for what |
| 23:54.28 | mzb | well, even if you _were_ able to change the root image in flash, if you had a problem (likely) you wouldn't be able to fix/debug |
| 23:54.38 | mzb | "dev suicide" |
| 23:54.40 | joss193 | plug this connection to hosts usb and generate a serial emulation device? |
| 23:55.16 | joss193 | mzb: well with jtag calble and serial this can be done only |
| 23:55.29 | joss193 | mzb: this can wake up a dead board |
| 23:55.59 | aquadran | joss193: but without proper setup info that will be useless |
| 23:56.33 | joss193 | aquadran: yeah..i opened the device, this not easy by any means |
| 23:57.11 | mzb | hmm ... well setting up a jtag and using it will be 1000000x harder than just opening the unit |
| 23:57.48 | joss193 | mzb: i have no jtag cable as well |
| 23:58.02 | aquadran | joss193: heh, i mean how data should be placed on flash. if you overwrite you lost chance to get information |
| 23:58.37 | joss193 | mzb: should i be able to emulate serial to host when it is connected via usb cable? |
| 23:58.38 | aquadran | and source of data to restore |
| 23:59.15 | aquadran | joss193: anyway, i'm going to sleep |
| 23:59.17 | aquadran | nite |
| 23:59.19 | joss193 | mzb: or this usbserial is ment for connections that involve connectors |
| 23:59.44 | joss193 | usb to serial converters it is..nevermind |