IRC log for #openezx on 20090618

00:10.01*** join/#openezx gDD (n=gDD@unaffiliated/gdd)
00:21.55*** join/#openezx bartv (n=bart@thisnet.xs4all.nl)
01:42.11anaishi
01:44.30*** join/#openezx gDD_mobilE (n=gDD@unaffiliated/gdd)
02:28.15*** join/#openezx gDD (n=gDD@unaffiliated/gdd)
02:42.13*** join/#openezx johanbr (n=j@blk-7-129-240.eastlink.ca)
03:09.55*** join/#openezx arne__ (i=nobody@dslc-082-082-086-044.pools.arcor-ip.net)
03:37.45*** join/#openezx flyhorse|linux (n=flyhorse@116.18.189.2)
03:44.53*** join/#openezx TheTrash (i=unices@82-170-225-106.ip.telfort.nl)
05:05.58*** join/#openezx marex (n=marex@vasut.kolej.mff.cuni.cz)
05:37.27*** join/#openezx marex (n=marex@vasut.kolej.mff.cuni.cz)
06:38.31*** join/#openezx ao2 (n=u@2001:1418:117:0:0:0:0:1)
06:40.16*** join/#openezx pleemans (n=toi@d51A49C45.access.telenet.be)
06:58.06anaisif./boot_usb zImage-xxxx <machid> "<optionals commandline parameters in quotes>" <initrd>
06:58.16anaishow about this initrd
06:58.21anaisparameter
07:01.57anais./boot_usb gen-blob 0 means to use gen-blob parameter to boot the system???????
07:02.57tmztuh?
07:03.06tmztthat loads gen-blob
07:03.29anaisthen i should put the boot dir on the first SD partion
07:03.29tmztwhich doesn't care about mach-id
07:03.48anaismachid is 1470 is right
07:04.24anaisat present the SD partion there is no boot dir and no menu.list
07:04.42anaiswhether this is also one problem?
07:04.52tmztI don't really know
07:05.33tmzthave you flashed gen-blob?
07:06.21anaisthis is my step 1../boot_usb setflag usb
07:06.35anais2../boot_usb gen-blob 0  
07:06.50anais3 ./boot_usb zImage-xxxx <machid> "<optionals commandline parameters in quotes>" <initrd>
07:07.14anaisgen-blob should be flashed into nand flash?
07:08.03tmztthat doesn't flash it
07:08.16anaisyes, just run in ram
07:08.17tmztbut it allows you to boot your own kernel
07:08.28tmztyou need to talk to WyrM
07:08.50anaiswo, but openezx kernel support SD startup???????????
07:09.31anaisafter the kernel startup .the log show cannot open /dev/mmcblkp02
07:10.03anaisthen seem to need pass mtdblk0...............7 as parameter
07:10.10anaisthen kernel panic
07:17.47ao2anais, can you pate your actual step 3?
07:18.16ao2also, run "./boot_usb" alone to see the machids
07:18.46ao2a1200 is 1742
07:19.01anaisoh iam sorry i am use 1742
07:19.06anaisjust type wrong
07:19.18anaisok i give my step 3
07:19.19ao2so try "./boot_usb zImage-xxxx 1742" as step 3 with no parameters
07:19.48anaiskernel dont know rootfs location?
07:20.08ao2it is in CONFIG_CMDLINE in ezx_defconfig anyway
07:35.06anais"console=tty1 root=/dev/mmcblk0p2 rootfstype=ext2 rootdelay=1 ip=192.168.0.202:192.168.0.200:192.168.0.200:255.255.255.0 debug"
07:35.11anaisoi
07:35.30anaisok i will use your method, now i partion new sdCARD
08:31.15*** join/#openezx ade|desk (n=ade|desk@195.153.131.254)
08:59.03*** join/#openezx pleemans (n=toi@d51A49C45.access.telenet.be)
09:24.57*** join/#openezx marex (n=marex@vasut.kolej.mff.cuni.cz)
09:45.10*** join/#openezx florian (n=fuchs@port-217-146-132-69.static.qsc.de)
10:05.46*** join/#openezx FeLLa (n=46241@mnhm-590d8fcb.pool.einsundeins.de)
10:12.39anaiskernel panic , pls append a correct "root="
10:12.52anaisthen a list mtdblk
10:18.56ao2kernel panic is about VFS, like can't find rootfs? or about device?
10:19.10ao2please copy the exact message
10:33.09*** join/#openezx gDD_mobilE (n=gDD@unaffiliated/gdd)
10:39.03*** join/#openezx anais (n=huzhangl@59.173.2.76)
10:41.46*** join/#openezx gDD_mobilE (n=gDD@unaffiliated/gdd)
11:24.19anais<4>[   92.291296] VFS: Cannot open root device "mmcblk0p2" or unknown-block(0,0)
11:24.24anaisall move up
11:24.34*** join/#openezx huzhangliandroid (n=huzhangl@59.173.2.76)
11:24.48anais<4>[   92.291296] VFS: Cannot open root device "mmcblk0p2" or unknown-block(0,0)
11:26.08WyrMhi
11:26.31WyrManais: have you built this kernel yourself? or are you using one that I compiled?
11:26.40anaisyes,
11:26.55WyrMcan you please try with the zImage on http://people.openezx.org/wyrm/images/latest/ ?
11:27.32anaisthen plan to use nfs, but this SD card should be ok
11:27.38anaisyes
11:27.44anaisi use the lastedst
11:27.54anaisyour lastest
11:28.08WyrMand my kernel doesn't recognizes the sd card?
11:28.08anaisi could give the kernel to you
11:28.14anaisyes
11:28.27anaiswhich type SD card you use?
11:28.46WyrM2gb sandisk.
11:28.57anais<3>[   91.637496] mmc0: error -110 whilst initialising MMC card
11:29.09WyrMhum.
11:29.40WyrMwell, try another card. :)
11:29.53WyrMthe linux kernel doesn't work with all cards.
11:30.24anaishttp://pastebin.ca/1464743
11:30.40anaisi have tried ScanDISK card
11:30.56anaisthe above the kernel message
11:30.59anaislin
11:31.01anaislink
11:31.16anaisanother question
11:31.26WyrM<6>[   91.277407] Waiting 1sec before mounting root device...
11:31.39WyrMmaybe your card is just slow.
11:31.41anaisi should make dir in the first partion and menu.list
11:31.52WyrMin this case, rootdelay=3 may help.
11:32.46WyrMnah, forget what I said.
11:32.57WyrMchanging rootdelay will not help.
11:32.58WyrM:/
11:33.56anaisya
11:34.15anaiswhat do you suggest for next debug
11:34.30anaisi have tried two kinds of disk
11:34.30WyrMtry another card. :)
11:35.22anaismmcblk0p2 major minor
11:35.43anaisthere is a1200 rootfs existing???
11:35.45anaisen
11:35.49WyrMtry another card.
11:35.55WyrMits not a rootfs problem.
11:36.05WyrMand changing the block device will not help either.
11:36.39WyrMwhat brand is your card?
11:36.55anaismmc4.3
11:37.14anaisthe most newest mmc protocol
11:37.30WyrMits a micro MMC card?
11:37.35anaisyes
11:37.39WyrMnever seen one of these.
11:37.55WyrMI only tested with micro SD cards.
11:38.04WyrMbut the kernel should work with MMC too.
11:38.17WyrMgen-blob will not, its SD only.
11:38.25anaissorry , THIS IS sd card
11:38.30anaismake sure
11:39.02anaismystep 1. ./boot_usb setflag usb  
11:39.04anais2
11:39.14anais./boot_usb gen-blob
11:39.28anais./boot_usb zImage-xxxx <machid>
11:39.44anaishow about these tree steps
11:40.03anais./boot_usb zImage-xxxx <machid> "<optionals commandline parameters in quotes>" <initrd>
11:40.18anaisinitrd is means, it is necesary?
11:40.23WyrMeverything _is_ correct on the pastebin you sent.
11:40.34WyrMbut your card doesn't work.
11:40.47tmztdid kernel report the card?
11:40.50WyrMso, my suggestion is _try_another_card_ !
11:41.00anaiswhether i should in the first partion Fat 16 mkdir boot
11:41.08anaisand create menu.list file
11:41.22anaisbut i dong use gen-blob menu
11:41.49WyrMtmzt: no, the kernel can't read the card partition table.
11:42.14tmztand doesn't see the block device?
11:42.19tmztmmcblk0
11:42.23WyrMno
11:42.28tmztodd
11:42.48WyrM<3>[   91.637496] mmc0: error -110 whilst initialising MMC card
11:43.00tmztI see
11:43.39tmztit's not gpio or mtype, must be the card
11:43.43tmztmakes snse
11:43.52WyrManais: gen-blob may work with this card.
11:44.03WyrMits more tolerant than the kernel.
11:44.15WyrMyou will see the boot menu, etc..
11:44.33WyrMbut the kernel will not be able to mount the rootfs from the card either. :(
11:44.40anaisso i should mkdir boot dir in first partion
11:44.47anaisflash gen-blob
11:45.00anaisyes
11:45.04WyrMyou don't need to flash gen-blob to test.
11:45.12WyrMyou can just send it to RAM.
11:45.13anaisat last the kernel still cannot acces s mmc
11:45.22anaishow to see the menu
11:45.35WyrMif you _don't_ "setflag usb", then it will search for the card.
11:45.36anaisjust mkdir in the FAT16 PARTION
11:45.51anaisEN
11:46.01anaisnow i will try
11:46.03anaiswait
11:47.15anaisreally cannot accces card
11:47.19anaiscmd41 error
11:47.32anaiscannot find mmc card
11:49.37*** join/#openezx lclaudio (n=lclaudio@201.21.176.254)
11:49.59*** join/#openezx marex (n=marex@vasut.kolej.mff.cuni.cz)
11:51.05anaisjust i talk with our hardware engineer,
11:51.13anaisthis is really micro MMC card
11:51.19anaiswyrm is right
11:51.30WyrMgen-blob can't work with micro MMC.
11:51.31tmztbut linux should support it
11:51.34WyrMthe kernel should.
11:51.42tmztless genblob is confusing itu
11:51.47tmztunless
11:52.00tmztby sending it sd cmds
11:52.19WyrMtmzt: no, if you "setflag usb" then gen-blob will do nothing to the card.
11:52.21tmztif you remove it and reinster does kernel detect it?
11:52.23WyrMnot even power it up.
11:52.25tmztok
11:52.38tmztand kernel will? we know it's powered
11:53.40WyrMyes, the kernel will power it up.
11:53.52WyrMI checked the dmesg on pastebin.
11:53.58WyrMand the regulator driver is loaded.
11:54.17WyrMI can't see the actual powerup, because REGULATOR_DEBUG is not enabled.
11:54.36WyrMbut if the code wasn't changed, then it should work ok.
11:56.13anaiszImage cannot be modified
11:56.29WyrMof course it can ;)
11:59.03anais6>[   88.490270] regulator: VAUX3: 1200 <--> 3600 mV
11:59.05anais<6>[   88.501802] regulator: V6: 2475 <--> 2775 mV
11:59.15WyrMyep.
11:59.24WyrMthe MMC is connected to VAUX3.
12:00.03WyrMyou can enable regulator debug to see when the kernel changes the VAUX3 regulator.
12:00.17WyrMthis is just the probe message that shows the min and max voltages.
12:01.08anaisbeijing time 8:00 pm , good night, thank you wyrm, tmzt, ao2 all here
12:01.10anaisgood night
12:01.19WyrManais: good night.
12:03.44tmztisbpower negotiation different for mmc?
12:04.07WyrMtmzt: no.
12:04.36WyrMIIRC, power and clock negotiation is common.
12:05.15tmztok
12:07.03*** join/#openezx l403 (n=l@85.132.159.239)
12:17.51*** join/#openezx gmzhuo (n=gmzhuo@118.114.149.107)
12:24.38*** join/#openezx gDD (n=gDD@unaffiliated/gdd)
12:43.03gmzhuoWyrM,congratulate,pcap is in mainline now:)
12:43.15WyrMgmzhuo: thanks :)
12:43.25WyrMnow, all the other subdrivers. ;)
12:48.34WyrMI have to go.
12:48.56WyrMI will be back before Monday. Bye!
13:06.01*** join/#openezx gDD_ (n=gDD@unaffiliated/gdd)
13:35.21*** join/#openezx johanbr (n=j@blk-7-129-240.eastlink.ca)
13:48.30*** join/#openezx gDD (n=gDD@unaffiliated/gdd)
14:09.55*** join/#openezx dragon (n=chatzill@221.220.97.83)
14:10.20*** join/#openezx huzhangliandroid (n=huzhangl@59.173.2.76)
14:19.46*** join/#openezx dragon (n=chatzill@221.220.97.83)
14:21.55dragonhello
14:22.27ao2hi Andy
14:22.43Andy:)
14:23.49Andywhen I run:./boot_usb read 0xA0000 1048576 backup-of-kernel-partition, I got a weird problem
14:25.46Andy./boot_usb read 0xA0000 1048576 backup-of-kernel-partition
14:25.47Andy$Id: boot_usb.c 2462 2009-04-12 22:55:17Z ao2 $
14:25.49AndySerching for EZX phone: Generic Blob found.
14:25.50AndyDownloading:     FAILED: download failed
14:26.14Andyhave you ever seen that?
14:28.19ao2maybe because of timeout
14:28.25*** join/#openezx gDD_ (n=gDD@unaffiliated/gdd)
14:29.13Andydo you have any suggestions? ao2
14:29.27lclaudioao2, quite nice your minimal-fso RootFS image :)
14:29.27ao2two tests, try to double USB_TIMEOUT, try on another computer
14:29.42lclaudioao2, I saw python there and got happy :)
14:29.59ao2lclaudio, I just built it, it is from OpenEmbedded :)
14:30.12ao2but thanks
14:30.34lclaudioao2, and was playing with fonts to get some rest for my eyes (i.e. "consolechars -f /tmp/lat1-08.psfu")
14:30.42lclaudioao2, :)
14:30.50Andyhow to double USB_TIMEOUT?
14:31.20AndyI'm not sure if usbnet works
14:31.26ao2Andy, I suggest to try also on another computer because my main PC has some usb problems with ezx phones
14:31.52ao2Andy, usbnet? it is not related to that issue anyway.
14:32.23*** join/#openezx gDD__ (n=gDD@unaffiliated/gdd)
14:32.30Andysorry, I mean usb interface, not usbnet:)
14:33.11Andywhen the phone enters gen-blob USB mode or unplug/plug the USB cable, dmesg output:
14:33.13Andy[  884.836686] usb 2-2: USB disconnect, address 4
14:33.14Andy[ 1118.136555] usb 2-2: new full speed USB device using uhci_hcd and address 5
14:33.16Andy[ 1118.311724] usb 2-2: configuration #1 chosen from 1 choice
14:33.27AndyI don't see messages such as:
14:33.29Andyusb0: register usbnet at usb-0000:00:10.2-2, pseudo-MDLM (BLAN) device, 8e:36:06:d5:16:9d
14:33.30Andyit seems usb doesn't work.
14:34.12ao2gen-blob doen't give usbnet, so it's normal you get no "register usbnet" method
14:34.18ao2*message
14:35.00Andyah...I see
14:35.54ao2Andy, to increase USB_TIMEOUT edit boot_usb.c, change its, value to the old one doubled, recompile boot-usb, and retry
14:36.22Andyokay, I'll try that
14:37.27ao2but really the current value should be enough
14:41.33Andyao2, it doesn't work
14:41.46AndyI still get the same error
14:43.13*** join/#openezx acassis (n=Alan@200.251.188.130)
14:47.41ao2you could try to uncomment the DEBUG line in boot_usb.c, recompile, rerun, and paste the output in pastebin.ca
14:49.00Andyokay
14:55.21Andysorry, ao2, what's pastebin.ca? I'm a newbie :P
15:12.24ao2Andy, it is a web site where you can paste a text snippet and then you give the relative url here, just to avoid flooding the irc channel
15:21.17Andyao2, plz see http://pastebin.ca/1464953
15:22.42ao2Andy, is your battery fully charged?
15:22.56Andyi think so
15:23.40ao2after Download failed, is there any disconnect message in dmesg?
15:23.58ao2does the phone turn off?
15:26.15*** join/#openezx Andy (n=chatzill@221.220.97.83)
15:26.23Andyi'm back
15:26.49ao2<ao2> after Download failed, is there any disconnect message in dmesg?
15:26.49ao2<ao2> does the phone turn off?
15:27.16Andylet me check
15:29.06Andyno
15:29.22Andythere is no any extra messages in dmesg
15:32.59ao2and the phne stays on
15:33.53Andyyes
15:34.30ao2ok, I am analyzing the debug log (some hex values are characters printed in hex)
15:36.49Andy:)
15:45.47ao2Andy, it looks like gen-blob is not right
15:45.51ao2did you load gen-blob from USB of flash?
15:46.10Andyfrom USB
15:46.27ao2let me try loading it from usb then
15:46.33Andyvia boot_usb gen-blob 0
15:46.41Andyokay
15:46.44*** join/#openezx gDD (n=gDD@unaffiliated/gdd)
15:51.00ao2Andy, where did you get your gen-blob from?
15:51.15ao2it replies with wrong data, for example, you get a:
15:51.26ao2Andy's
15:51.26ao2RX(15):  02 52 06 00 4e 1e 53 56 6e 2d 67 65 6f 62 03
15:51.26ao2R   N  S V n - g e o b
15:51.32ao2while you should get:
15:51.41ao2ao2's
15:51.41ao2RX(15):  02 52 53 56 4e 1e 67 65 6e 2d 62 6c 6f 62 03
15:51.41ao2R S V N  g e n - b l o b
15:52.04Andyhi
15:52.11ao2I can send you the gen-blb I am using if you want
15:52.30ao2I just compiled it from latest svn code
15:52.30AndyI got it from svn co http://svn.openezx.org/trunk/src/blob/gen-blob
15:52.39ao2ok, that is it
15:52.59Andyok, send it to me, plz
15:53.01ao2so check your usb, it might get corrupted on upload
15:53.08Andylongzhi@gmail.com
15:53.14Andythanks a lot
15:54.05ao2ok, http://people.openezx.org/ao2/tmp/gen-blob-for-Andy
15:54.43Andy:)
15:54.55AndyI'll try it right now
16:01.28AndyGreat, it works
16:01.37Andythank you, ao2
16:01.49ao2you're welcome
16:02.40AndyI compiled the gen-blob by myself
16:02.44ao2now it would be great if you find out what was wrong with your build, maybe some wrong instruction on the wiki?
16:03.19Andymaybe
16:04.09AndyI follow the guide line on http://wiki.openezx.org/Dual_boot
16:05.07Andyso weird
16:07.25Andyactually, I compiled it according to EZX_README shipped with gen-blob
16:08.10Andyagainst the lastest openezx kernel, ezx/current branch
16:13.44*** join/#openezx johanbr (n=j@blk-7-129-240.eastlink.ca)
16:13.47Andyao2, can you show me your building config?
16:14.42ao2what toolchain?
16:15.00AndyI use codesourcery
16:16.07ao2that could be the difference, I use OE, and I think I followed the same steps documented in the wiki
16:16.42ao2if you have some time try out openembedded, otherwise just enjoy openezx :P
16:17.32AndyI wanted to use OE, but I can't find angstrom, do you have it?
16:18.27AndyI cant' find angstrom-2007.9-test-20071017-arm-linux-gnueabi-toolchain.tar.bz2
16:23.07ao2I built it from source sorry, I don't have a tarball around
16:27.37Andyao2, how could I get the source? I can't find it
16:28.14ao2openembedded.net
16:28.38ao2it is much more than just a toolchain builder
16:30.57Andyyou mean you don't use angstrom, but just OE? right?
16:32.21*** part/#openezx ade|desk (n=ade|desk@195.153.131.254)
16:34.04gmzhuoAndy,OE will build your toolchain,and it will cost so many time:)
16:41.51Andygmzhuo, I'd like to if I can use OE without angstrom.
16:42.02Andygmzhuo, I'd like to know if I can use OE without angstrom.
16:42.24gmzhuoyes,you can
16:42.29*** join/#openezx pleemans (n=toi@d54C2AAB7.access.telenet.be)
16:43.16gmzhuoOE will download toolchain source and compiled it for you,
16:44.13Andyah... I see
16:44.20Andythanks
16:44.49gmzhuoAndy,where are you from"
16:44.50Andygood night
16:45.00AndyI'm from China
16:52.12*** join/#openezx gDD_mobilE (n=gDD@unaffiliated/gdd)
16:53.08*** join/#openezx huzhangliandroid (n=huzhangl@59.173.2.76)
17:03.31*** join/#openezx johanbr (n=j@blk-7-129-240.eastlink.ca)
18:09.02*** join/#openezx tmzt (n=tmzt@76.211.2.11)
18:23.12*** join/#openezx florian (n=fuchs@f049021248.adsl.alicedsl.de)
18:37.36*** join/#openezx stefan_schmidt (n=stefan@p5B034861.dip.t-dialin.net)
18:52.26*** join/#openezx johanbr (n=j@JBrannlund2.MathStat.Dal.Ca)
18:56.09*** join/#openezx anais (n=huzhangl@59.173.2.76)
19:09.28*** join/#openezx tmzt_ (n=tmzt@adsl-69-221-132-47.dsl.akrnoh.ameritech.net)
19:58.44*** join/#openezx FeLLa (n=46241@mnhm-590d8fcb.pool.einsundeins.de)
23:19.54CIA-15OpenEZX: 03Antonio Ospite <ospite@studenti.unina.it> 07ezx/current * r9145a79519 10openezx/drivers/leds/leds-lp3944.c: Change email, for consistency.
23:20.05CIA-15OpenEZX: 03Antonio Ospite <ospite@studenti.unina.it> 07ezx/current * r664e412e2b 10openezx/ (drivers/leds/leds-lp3944.c include/linux/leds-lp3944.h): Remove some private fields from platform data.

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.