| 00:14.01 | *** join/#openezx agd5f (n=alex@c-69-143-4-28.hsd1.va.comcast.net) |
| 01:26.18 | *** join/#openezx Guest94977 (n=root@222.212.174.188) |
| 01:26.32 | Guest94977 | quit |
| 01:30.27 | *** join/#openezx luoqq (n=chatzill@125.69.72.130) |
| 02:05.22 | *** join/#openezx flyhorse|linux (n=flyhorse@116.18.254.50) |
| 03:10.42 | *** join/#openezx arne_ (i=nobody@dslc-082-082-085-188.pools.arcor-ip.net) |
| 05:20.36 | *** join/#openezx l403 (n=l@85.132.159.239) |
| 05:32.12 | *** join/#openezx shoragan (n=shoragan@debian/developer/shoragan) |
| 05:35.20 | *** join/#openezx marex (n=marex@vasut.kolej.mff.cuni.cz) |
| 05:55.24 | *** join/#openezx pleemans (n=toi@116.54-246-81.adsl-static.isp.belgacom.be) |
| 06:16.14 | *** join/#openezx parmaster (i=par@dipole.idlepattern.com) |
| 06:39.11 | *** join/#openezx ao2 (n=u@2001:1418:117:0:0:0:0:1) |
| 07:25.17 | *** join/#openezx methril|work (n=Methril@213.27.233.98) |
| 08:14.55 | Hopscotch | good morning |
| 08:27.10 | *** join/#openezx alain2210 (n=alain@AMontsouris-151-1-50-93.w82-123.abo.wanadoo.fr) |
| 08:36.41 | ao2 | hi |
| 08:51.19 | *** join/#openezx gmzhuo (n=gmzhuo@118.112.226.153) |
| 08:51.32 | gmzhuo | Hi all |
| 09:07.00 | ao2 | hi gmzhuo, have you already seen we have some E6 code now? :) (even if barely needed) |
| 09:07.09 | ao2 | I mean from Motorola |
| 09:11.17 | gmzhuo | Yes,I have seen it,and compiled one for e6,but because of battery,still not test ist |
| 09:11.21 | gmzhuo | test it |
| 09:49.02 | *** join/#openezx gDD (n=gDD@125.116.19.76) |
| 10:11.45 | gmzhuo | the kernel compiled from e6 is realy runable |
| 10:15.11 | ao2 | ah good gmzhuo |
| 10:16.00 | ao2 | I've seen that E6 can also be used as a webcam thanks to device UVC support, I didn't know that. |
| 10:17.55 | gmzhuo | I have used it as webcam for a long time ago |
| 10:18.01 | gmzhuo | :) |
| 10:19.13 | gmzhuo | Oh,my body temperature is 39C now :( |
| 10:20.38 | gmzhuo | got serious enteritis |
| 10:29.26 | *** join/#openezx florian_kc (n=fuchs@port-217-146-132-69.static.qsc.de) |
| 10:40.49 | *** join/#openezx trod (n=trod@59.163.114.3) |
| 10:45.20 | trod | I have --enable-debug and --enable-blob-debug while compiling gen-blob and flashed on rokr e6, where would the debug info from gen-blob be logged when I boot it? |
| 10:56.52 | alain2210 | Hello |
| 10:57.18 | alain2210 | trod: I think you need to use gen-blob via boot-usb. |
| 10:57.32 | alain2210 | Hence you see the debug message on the screen of the host. |
| 10:58.09 | alain2210 | But for having debug, I remember that you have to set #define DEBUG in the code. |
| 11:02.36 | trod | alain2210: okay, I will try with boot_usb and see, also will check for #define in gen-blob code and change it accordingly |
| 11:05.54 | alain2210 | Sorry for the debug line, I have made a confusion with boot_usb |
| 11:06.27 | alain2210 | you can have debug messages also on the screen. |
| 11:07.40 | trod | I guess I missed the #define earlier, compiling now |
| 11:08.43 | alain2210 | there is one commented in usb_ctl.c |
| 11:09.25 | trod | yes, I uncommented, compiled |
| 11:09.53 | alain2210 | and some #define debug print elsewhere. |
| 11:10.37 | trod | actually WyrM was suggesting that my sd card has a problem and thought of checking the debug log from gen-blob to assert it |
| 11:10.38 | alain2210 | I have only use debug on boot_usb. |
| 11:13.22 | *** join/#openezx sabrod (n=sab@lns-bzn-37-82-253-46-98.adsl.proxad.net) |
| 11:13.31 | trod | no debug messages from gen-blob on screen, its the usual debug info from kernel |
| 11:21.59 | *** join/#openezx flo_lap (n=fuchs@port-217-146-132-69.static.qsc.de) |
| 11:53.12 | *** join/#openezx darion76 (n=darion76@94-248-2-209.dynamic.peoplenet.ua) |
| 12:01.19 | alain2210 | trod: I can't help. sorry. |
| 12:17.39 | *** join/#openezx gDD (n=gDD@125.116.19.76) |
| 13:29.16 | alain2210 | trod: now I remember : for gen-blob, the messages are on the screen but you need to put the screen on. |
| 13:40.17 | trod | alain2210: screen on? are we talking about handset screen |
| 13:41.22 | alain2210 | yes handset screen. |
| 13:41.56 | alain2210 | I have add some print and it was working. |
| 13:42.43 | trod | but the screen is on, probably my eyes might have missed the messages, anyway to check the messages after the boot |
| 13:43.17 | alain2210 | you can add as in genblob some while(1) to stop after the thing you want to see. |
| 13:43.26 | alain2210 | it is not elegant, but works. |
| 13:43.54 | trod | but I need to understand gen-blob code to know where its failing to load from sd card |
| 13:45.07 | alain2210 | i don't understand, it fails in what sense ? |
| 13:45.44 | trod | gen-blob after flashed on handset and when I select a kernel from boot menu it fails with a message "failed to load /boot/zImage" |
| 13:46.23 | trod | I fsck.msdos the sd card and it showed no errors, I can use the same sd card on host and it mounts fine |
| 13:46.41 | alain2210 | so you can put some print in the source code to see where it stops, isn't it ? |
| 13:48.14 | trod | yes I can, but I should know where exactly I need to put print statements in source code. I am new to gen-blob and don't yet understand the code base |
| 13:49.06 | alain2210 | I have no precise answer since I do not know well the code. |
| 13:49.27 | alain2210 | I would say "about" the failed to load message... |
| 13:49.44 | trod | was expecting that if gen-blob fails to boot a kernel then it might log some descriptive message as part of DEBUG |
| 13:53.28 | alain2210 | the file boot_mode.c is very interesting. |
| 13:53.53 | alain2210 | do you get the "Loading " sentence ? (with size read) ? |
| 13:54.12 | trod | checking |
| 13:55.18 | alain2210 | and the "read .. bytes" "booting" ? |
| 13:56.26 | trod | I think its because of if(!lcd) and following printf statement :) you hit the bull's eye |
| 13:56.43 | trod | "cannot load kernel from..." |
| 13:57.52 | alain2210 | but the lcd should be already on. |
| 13:58.11 | alain2210 | you get the "cannot load kernel" ? |
| 13:58.49 | trod | well....that is the only place in code where we get "Cannot load from:" string, so lcd is still 0, there is lcd++ in the code, |
| 13:59.48 | alain2210 | i'm lost. |
| 14:00.17 | alain2210 | what is your processus for booting ? |
| 14:00.23 | alain2210 | using the menu ? |
| 14:01.37 | alain2210 | you can add EnableLCD_8bit_active() to put on the screen. |
| 14:02.39 | trod | I powerup the handset with powerkey + vol- and I am presented with bootmenu by gen-blob, then I select a kernel from the menu list |
| 14:03.24 | trod | only way printf at 307 gets called is if lcd = 0 |
| 14:03.34 | alain2210 | so the screen is on. |
| 14:04.20 | alain2210 | so lcd is 1. |
| 14:04.59 | alain2210 | after selecting a kernel, what do you do/see ? |
| 14:05.30 | trod | "Loading /boot/zImage..." followed by "Cannot load kernel from: /boot/zImage" |
| 14:06.56 | alain2210 | you do not get the "read ... bytes" and "booting" before "Cannot...." |
| 14:06.58 | alain2210 | ? |
| 14:07.06 | *** join/#openezx LoneStar (n=xinzhen@114.92.170.203) |
| 14:07.16 | trod | oppps my bad there aren't parenthesis for if...so if(!lcd) is only for EnableLCD_8bit_Active() function |
| 14:07.31 | trod | yes I don't see any read..bytes or booting |
| 14:08.03 | trod | that means size is not . 0 |
| 14:08.07 | trod | > |
| 14:08.12 | alain2210 | so it could be "file_fat_read" that does not work. |
| 14:08.26 | alain2210 | yes the size is 0 in your case. |
| 14:09.07 | alain2210 | so the file is fat.c |
| 14:09.36 | trod | yes checking do_fat_read |
| 14:10.00 | alain2210 | you should add some printf in this function to see where is the problem. |
| 14:10.39 | alain2210 | or uncomment the #define FAT_DPRINT printf |
| 14:10.45 | trod | there is already one FAT_DPRINT |
| 14:10.48 | trod | yes that |
| 14:23.04 | trod | guess I messed up flashing again :( I did append the needed offset...powerkey+vol- switches off the phone after hellomoto logo |
| 14:24.09 | trod | and the size is 72k which is under 128K limit mentioned in wiki |
| 14:28.30 | trod | on the second thought may be gen-blob is okay, cos powerkey + vol+ brings up usb ready |
| 14:31.09 | alain2210 | are you sure that the default kernel of the sd/tf card is good ? |
| 14:31.51 | alain2210 | you say that you get the hellomoto logo ? |
| 14:32.01 | alain2210 | in what case ? |
| 14:33.19 | trod | alain2210: powerkey + vol- shows hellomoto logo and switches off which powerkey + vol+ brings up hellomoto logo followed by "usb ready" |
| 14:33.55 | alain2210 | on my e680, I get a black screen. |
| 14:33.59 | trod | I am sure the default kernel of sd card is good as I boot fine last time before I messed up the phone |
| 14:34.14 | alain2210 | with white letters. |
| 14:35.02 | alain2210 | it could depend on the phone. |
| 14:35.59 | alain2210 | and what genblob is saying with FAT_DPRINT on ? |
| 14:36.22 | trod | gen-blob switches off even before it shows boot menu |
| 14:38.15 | alain2210 | So I may confuse between the various version of genblob. |
| 14:39.24 | alain2210 | I reading a very recent version. |
| 14:39.51 | trod | alain2210: guess what gen-blob with FAT_DPRINT on just refuses to show boot menu while gen-blob without FAT_DPRINT shows the boot menu :) |
| 14:40.21 | alain2210 | ? |
| 14:41.14 | trod | may be I am too confusing, let me explain. I compiled gen-blob without any debug switches on,flashed it and it shows boot menu fine |
| 14:41.27 | alain2210 | yes |
| 14:42.01 | trod | but if I compile gen-blob with FAT_DPRINT on or any other DEBUG on it just switches off after showing hellomoto logo, no boot menu |
| 14:42.42 | alain2210 | if I understand, you put the phone on, with power+vol + and get usb ready. |
| 14:43.02 | alain2210 | then you send genblob (with debug) with boot_usb ? |
| 14:43.20 | alain2210 | pushing again to vol+ ? |
| 14:44.41 | alain2210 | s/to/on/ |
| 14:44.58 | *** join/#openezx tombhadAC (n=tombhad@pD95DF552.dip.t-dialin.net) |
| 14:45.22 | trod | I put the phone on with camera+power mbm flash mode, then boot_usb setflag usb, boot_usb gen-blob 0 and then flash |
| 14:45.51 | alain2210 | you need not reflashing everytime. |
| 14:46.36 | alain2210 | and with this, you cannot get the menu. |
| 14:46.42 | trod | but we are trying to find out why after flashing gen-blob it is not able to boot kernel from sd card on fat partition |
| 14:47.22 | trod | I mean after showing the boot menu why is it failing to boot from fat partition on sd card |
| 14:47.52 | alain2210 | there is a lot of problem. perhaps it simpler to verify that genblob with debug is working before flashing it. |
| 14:48.22 | trod | yes, that sounds simpler than flashing everytime |
| 14:48.32 | alain2210 | and quicker |
| 14:48.34 | alain2210 | and safer. |
| 14:58.41 | trod | alain2210: the debug enabled gen-blob boots a kernel from host pc just fine. Unfrotunately can't check the kernel on sd card as my host pc doesn't have a card holder slot |
| 14:59.24 | alain2210 | trod: you can by a external reader, it is cheap. |
| 14:59.45 | alain2210 | I have one. that's very usefull. |
| 15:00.16 | alain2210 | above i forgot "buy"..... you can buy. |
| 15:01.10 | trod | actually I have one on my laptop and I gotta go home to check it..still at workplace :) |
| 15:01.21 | alain2210 | understood. |
| 15:01.45 | sabrod | hi all. |
| 15:02.15 | trod | hi sabrod |
| 15:02.36 | alain2210 | so with debug and vol+ (or - i'm never sure) pushed, do you get the menu ? |
| 15:02.42 | alain2210 | hello sabrod. |
| 15:02.48 | sabrod | trod: Can't it be the fragmentation of the file "zImage"? |
| 15:03.39 | trod | sabrod: that is what we were trying to assert, suspecting something wrong with sd card, but fsck.msdos shows its good and mounts fine on my host |
| 15:04.16 | sabrod | heh... fsck is not a defrag tool :) |
| 15:05.19 | sabrod | it could explain why it draws the menu, and then for a booting a zImage, it bug. |
| 15:05.43 | trod | ohh, can you suggest how to defrag, my bad I didn't know that I should defrag fat partition |
| 15:05.46 | sabrod | Because menu.lst is small, it's probably not fragmented. |
| 15:06.28 | alain2210 | there is a windows tools to defrag. |
| 15:06.33 | sabrod | I don't know, windows? |
| 15:07.09 | sabrod | Note that is could be better to erase the part and recreate it, (maybe bigger) . |
| 15:07.10 | alain2210 | fsck.msdos does not speak about fragmentation ? |
| 15:07.18 | trod | oho windows...admin privileges needed here to do defrag |
| 15:07.29 | alain2210 | fsck.ext2 gives informations. |
| 15:07.45 | sabrod | then use fdsk/mkdosfs |
| 15:07.52 | sabrod | fdisk/mkdosfs |
| 15:07.57 | trod | sabrod: I did erase and recreate partition before and it didn't workout |
| 15:08.13 | sabrod | Ah... |
| 15:08.15 | trod | yes exactly fdisk and mkdosfs |
| 15:08.31 | alain2210 | so again, what says gen-blob debug ? |
| 15:09.13 | sabrod | Because most SD does wear levelling in hardware, I don't know if it's very relevent to speak about fragmentation... |
| 15:09.29 | trod | alain2210: gen-blob debug text scrolled too fast, couldn't make out, not even sure whether the messages were from gen-blob :) |
| 15:12.10 | alain2210 | ok. but where they can come from else ? |
| 15:12.44 | alain2210 | so you have to put little printf to find the problem point. |
| 15:13.14 | alain2210 | s/little/few/ |
| 15:13.46 | trod | and sleep() along with printf |
| 15:18.20 | alain2210 | if they are few, you do not need sleep. |
| 15:18.30 | alain2210 | they can be all on the screen. |
| 15:19.12 | trod | alain2210: where do FAT_DPRINT print the message on phone screen right? |
| 15:19.58 | trod | when I boot a kernel the messages from kernel erase off the gen-blob's messages from the screen |
| 15:20.34 | alain2210 | trod: yes bu you have said that the kernel was not booting.... |
| 15:20.47 | alain2210 | so you can read the genblob messages. |
| 15:21.37 | alain2210 | the printf for only few FAT_DPRINT since there are too much. |
| 15:22.06 | trod | oh no, the kernel boots fine when we go the mbm flash mode way(camerakey+power->mbm flash mode -> boot_usb gen-blob 0) but it fails to boot kernel on flashing to handset |
| 15:23.55 | alain2210 | so the printf messages are only useful when the kernel does not load. |
| 15:24.07 | alain2210 | and they can be read in this case. |
| 15:25.15 | trod | the boots properly if I don't flash the debug version of gen-blob(using boot_usb) |
| 15:25.45 | trod | I think we are looking at 2 different things :) |
| 15:28.52 | alain2210 | it boots using the menu ? and the kernel on the flash card ? |
| 15:29.34 | trod | gen-blob DEBUG version doesn't even show the boot menu, it just switches off |
| 15:29.42 | trod | after flashing on the phone |
| 15:34.17 | trod | I have to try a couple of things on my laptop, defrag fat partition on sd card, try to capture debug messages from FAT_DPRINT |
| 15:34.34 | trod | will join back in a couple of hours |
| 15:34.48 | trod | alain2210: thanks a lot for your time and patience :) |
| 15:59.24 | *** join/#openezx sabro1 (n=sab@lns-bzn-37-82-253-46-98.adsl.proxad.net) |
| 17:51.41 | *** join/#openezx marex (n=marex@vasut.kolej.mff.cuni.cz) |
| 18:08.19 | WyrM | trod: "failed to load /boot/zImage" or seeing the boot menu means that the mmc is recognized. |
| 18:09.06 | WyrM | trod: if you enable debug, you need to assert that you enable the LCD before any debug message, otherwise it will just turn-off the phone. |
| 18:09.20 | WyrM | err, trod not here. ;) |
| 18:25.49 | *** join/#openezx trod (n=trod@122.169.152.166) |
| 18:25.55 | WyrM | trod: hi |
| 18:25.59 | trod | WyrM: hi |
| 18:26.04 | WyrM | trod: "failed to load /boot/zImage" or seeing the boot menu means that the mmc is recognized. |
| 18:26.08 | WyrM | trod: if you enable debug, you need to assert that you enable the LCD before any debug message, otherwise it will just turn-off the phone. |
| 18:26.14 | trod | sorry yesterday I slept while I kept handset for charging |
| 18:26.59 | WyrM | trod: you don't need debug at all. |
| 18:27.08 | trod | WyrM: that makes sense, that is why debug version of gen-blob always failed |
| 18:27.20 | WyrM | trod: as mmc and the FAT layer are both working (you can see the boot menu). |
| 18:27.36 | WyrM | what size is your fat partition on card? |
| 18:27.43 | trod | 600MB |
| 18:27.55 | WyrM | I would just delete the partition and create it again. |
| 18:28.05 | WyrM | its easier than defraging. |
| 18:28.14 | WyrM | gen-blob can't deal with fragmented files. |
| 18:28.34 | trod | WyrM: I did it again and again, 10 min ago I deleted the partition and created a new fat32 |
| 18:28.40 | trod | still the problem persists |
| 18:28.58 | WyrM | it can read the menu.lst, but not the zImage? |
| 18:29.22 | trod | yes the openezx kernel |
| 18:29.32 | trod | it reads default zImage and switches off |
| 18:29.46 | WyrM | why it reads the default zImage? |
| 18:30.04 | WyrM | the flash we did yesterday disables the default zImage on the mmc card. |
| 18:30.04 | trod | well can't say it reads but it switches off without any message |
| 18:30.13 | WyrM | it will read default from flash. |
| 18:30.37 | WyrM | so, your phone is not booting again? |
| 18:30.59 | trod | no no, everything is fine now..oh god somehow I am confusing everyone today |
| 18:31.25 | trod | its about gen-blob(flashed) that refuses to boot from sd card |
| 18:31.45 | WyrM | yeah, I understand this. |
| 18:32.12 | WyrM | but what do you do to cause the turnoff case? |
| 18:32.13 | trod | default boot is fine, gen-blob shows menu with powerkey+vol - and usb ready for powerkey+vol+ |
| 18:32.31 | WyrM | and if you don't press any button? |
| 18:32.40 | WyrM | it boots to the motorola firmware, correct? |
| 18:32.43 | trod | when I select one of the kernel from boot menu showed by gen-blob and the default kernel from sd card switches off |
| 18:32.54 | trod | WyrM: yes motorola firmware is intact |
| 18:32.58 | WyrM | ok. |
| 18:33.02 | trod | it is performing flawlessly |
| 18:33.06 | WyrM | then there is no "default" kernel ;) |
| 18:33.18 | WyrM | the default kernel is on your flash. |
| 18:33.28 | WyrM | please, pastebin your menu.lst |
| 18:33.38 | trod | yes that would be much clear |
| 18:33.40 | trod | 1 min |
| 18:34.00 | WyrM | and gen-blob that you are using, you compiled yourself? or it's the version on people.openezx.org/wyrm/ ? |
| 18:34.26 | trod | gen-blob I compiled from source today, will share it in a moment |
| 18:34.49 | WyrM | trod: then send me the output of "svn diff" too, please. |
| 18:35.00 | trod | sure |
| 18:39.37 | trod | WyrM: http://pastebin.com/m313260d6 menu.lst |
| 18:41.12 | trod | WyrM: http://pastebin.com/m306cbf0c svn diff of gen-blob |
| 18:44.45 | WyrM | trod: don't try to boot the motorola 2.4 kernel from the boot menu. |
| 18:44.59 | trod | okay |
| 18:45.07 | WyrM | it doesn't work on gen2 phones, because the kernel expects the LCD to be initialized by MBM. |
| 18:45.31 | WyrM | gen-blob will mess with the Frame Buffer configuration and the 2.4 kernel will not work. |
| 18:45.46 | trod | okay, I will take out the default entry from menu.lst |
| 18:46.39 | WyrM | trod: the changes on gen-blob, to enable printf on the fat driver... |
| 18:46.48 | WyrM | looks ok. |
| 18:47.06 | WyrM | but you don't need it anyway ;) |
| 18:47.17 | trod | okay |
| 18:47.24 | WyrM | nothing usefull on the debug. |
| 18:47.39 | WyrM | I was thinking that you had problems with the MMC driver, not with the FAT. |
| 18:48.50 | trod | last we spoke you were about to give me a debug version of gen-blob when I got dropped. I thought I might try myself for a debug version of gen-blob :) seems that I messed up more than solve |
| 18:49.02 | WyrM | everything seems ok, it should be booting.. |
| 18:50.01 | WyrM | yeah, I was going to send you a gen-blob with some debug printks on the mmc driver. |
| 18:50.09 | WyrM | but you don't seem to need it. :) |
| 18:51.15 | trod | WyrM: windows doesn't recognize the partitions on sd card, it simply asks me to format full 2GB though fat32 is of 600MB, is something wrong with sd card |
| 18:51.50 | WyrM | trod: yeah, certainly something is wrong on your sd partition layout. |
| 18:52.06 | WyrM | some (most) sds came with a non-standard partition layout. |
| 18:52.15 | WyrM | with a partition table inside another.. |
| 18:52.44 | trod | can you recommend a standard sd card suitable for this motorola phones, what normally people here use |
| 18:52.52 | WyrM | eg, a single partition, and inside this partition another partition table.. |
| 18:52.55 | *** join/#openezx pleemans (n=toi@d54C2AAB7.access.telenet.be) |
| 18:53.07 | WyrM | your card is ok. |
| 18:53.20 | WyrM | but you need to recreate the partitions. |
| 18:53.30 | WyrM | what have you used to partition it previously? |
| 18:53.53 | trod | fdisk |
| 18:54.08 | trod | or precisely cfdisk :) |
| 18:54.17 | WyrM | trod: delete all partitions with fdisk. |
| 18:54.26 | trod | okay |
| 18:54.34 | WyrM | remove the card from the card reader, then insert it again. |
| 18:54.57 | WyrM | it will probably recognize a partition even after you deleted them all. ;) |
| 18:56.46 | WyrM | if it does, delete it again, and repeat until you insert the card and no partitions are recognized. |
| 18:57.05 | WyrM | then create the partitions, VFAT on the first, EXT2 on the second. |
| 18:57.27 | WyrM | and mkfs.vfat on the first partition and setup /boot/ |
| 18:57.34 | trod | okay |
| 19:00.58 | trod | WyrM: don't see VFAT in known paritions types in fdisk |
| 19:02.28 | trod | should that be FAT32 |
| 19:05.51 | WyrM | trod: yes |
| 19:06.58 | trod | okay |
| 19:10.32 | trod | WyrM: same problem, loading /boot/zImage ... Cannot load kernel from: /boot/zImage |
| 19:18.34 | WyrM | trod: weird. |
| 19:19.40 | WyrM | just a min. |
| 19:24.05 | WyrM | trod: "loading /boot/zImage ..." |
| 19:24.21 | WyrM | or "loading /boot/zImage..." ? |
| 19:24.40 | WyrM | note the space between zImage and ... |
| 19:25.08 | WyrM | whitespaces shouldn't matter, but I have no other clues. ;) |
| 19:26.39 | trod | WyrM: its "Loading /boot/zImage ..." with a space |
| 19:26.54 | WyrM | trod: this is wrong. :) |
| 19:27.02 | WyrM | the code is: |
| 19:27.10 | WyrM | if (lcd) printf("Loading %s...\n", kernel); |
| 19:27.14 | WyrM | no space. |
| 19:27.26 | WyrM | remove the whitespace after the kernel name on your menu.lst. |
| 19:28.05 | trod | okay |
| 19:32.54 | trod | WyrM: sorry it was such a silly mistake on my part, I don't know how I overlooked that space, It boots perfectly |
| 19:33.13 | WyrM | well, the whitespace should be ignored. |
| 19:33.23 | WyrM | not your mistake. ;) |
| 19:53.33 | WyrM | ao2: im looking at the can't enter boot menu gen-blob bug on a780 now. |
| 19:53.53 | WyrM | weird, I can't reproduce the bug if I add a printk to is_key_press_down() :/ |
| 19:54.35 | *** join/#openezx trod (n=trod@122.169.135.223) |
| 19:57.30 | ao2 | yes, WyrM I also could aoid the bug by adding some additional EnableLCD_8bit_active(); |
| 19:57.39 | ao2 | s/aoid/avoid/ |
| 20:10.05 | ao2 | but it was not a solution |
| 20:35.37 | *** join/#openezx trod_ (n=trod@122.169.135.223) |
| 20:44.17 | trod_ | any idea what is root's password for Angstrom-minimal-openmoko-image-glibc-ipk-2007.12-a780.rootfs. Can't ssh with blank password |
| 20:45.12 | *** join/#openezx florian (n=fuchs@f049036036.adsl.alicedsl.de) |
| 21:34.40 | WyrM | ao2: weird. |
| 21:35.28 | WyrM | if instead of vol-, I press the jog button it works. |
| 21:37.02 | WyrM | some keys are detected correctly, others aren't. |
| 21:40.40 | WyrM | ao2: seems to be some kind of hardware issue. |
| 21:41.07 | WyrM | we need some delay after enabling the keypad controller for it to recognize all keys. |
| 22:13.39 | CIA-18 | OpenEZX: 03wyrm * r2464 10/trunk/src/blob/gen-blob/src/blob/ (boot_modes.c keypad.c mmc.c): |
| 22:13.39 | CIA-18 | OpenEZX: fix keypad for a780 when gen-blob is flashed |
| 22:13.39 | CIA-18 | OpenEZX: error msgs for mmc failure |
| 22:25.39 | ao2 | WyrM, thanks |
| 22:39.09 | sabrod | Ah! I though it was normal, on my a780, I had only the jog dial to navigate the menu... :) |
| 22:40.09 | sabrod | seen his first boot menu a few weeks before, only... |
| 22:57.54 | WyrM | sabrod: no, it should use vol-. |
| 22:58.21 | WyrM | jog press works because some other phone has the vol- at the same position in the keypad matrix. |
| 22:58.49 | WyrM | the latest version also fix a bug on the mmc driver. |
| 22:59.07 | sabrod | Hehe, I didn't know... it's somewhat strange boths ao2 and your changes corrected the stuff! |
| 22:59.10 | WyrM | that would cause a freeze while the LCD is still off case no MMC card is inserted. |
| 22:59.39 | WyrM | sabrod: its because the problem is timing. |
| 23:00.00 | sabrod | Ok... :) |
| 23:00.10 | WyrM | it only happens with gen-blob flashed, and at the very beginning of a hardware poweron. |
| 23:00.43 | WyrM | since the keys detections is the first thing that gen-blob does, it was not working. |
| 23:02.35 | sabrod | Cool! in fact I was wondering why it was so hard to press the VR key to boot a kernel, while we were selecting it with the jog dial... :) |
| 23:03.00 | sabrod | I was at the limit before asking you to correct the keys definitions :p |
| 23:03.27 | ao2 | 'night |
| 23:03.57 | sabrod | night ao2, will go there tomorrow morning. |
| 23:05.13 | sabrod | (wiki isn't the source of the lost space on trod's menu.lst ;-) ) |
| 23:05.49 | WyrM | sabrod: now I added " around the file name case it fails. ;) |
| 23:05.52 | sabrod | Good catch, btw! |
| 23:06.20 | sabrod | Ha, cool! |
| 23:06.32 | WyrM | heh, space is valid on filenames for vfat. |
| 23:06.44 | WyrM | so we should not ignore whitespaces. :) |
| 23:07.03 | sabrod | Right... |
| 23:07.18 | WyrM | sabrod: do you have locked ezx phones? |
| 23:07.40 | sabrod | Yes I think I have 2 ;) |
| 23:07.42 | WyrM | don't you want to do some research on how the AP firmware implements the locking? |
| 23:07.56 | WyrM | you may become famous. lol |
| 23:08.08 | sabrod | But I could plce an ad and have a ton :) |
| 23:08.13 | WyrM | the one that can unlock a1200 without test point. |
| 23:08.40 | sabrod | I really could ? :) |
| 23:08.46 | WyrM | do you think that the workaround that scotsman posted on motorolafans really works? |
| 23:08.56 | WyrM | I have no locked phones, so I can't test it. |
| 23:09.27 | WyrM | if his workaroung works, then motorola is very stupid, and its very easy to unlock ezx phones. |
| 23:09.33 | sabrod | I will try with an a910, or maybe an a780 (if it's locked) |
| 23:09.36 | WyrM | s/ng/nd/ |
| 23:13.12 | sabrod | Will that a1200 "motoasst", works on a780 or a910? |
| 23:13.34 | sabrod | I'm downloading it... |
| 23:13.57 | WyrM | sabrod: yeah, probably. |
| 23:14.22 | sabrod | Hum, you are optimistic! :) |
| 23:17.27 | WyrM | sabrod: if BP works on openezx with your a910, then you can use OpenEZX to test too. |
| 23:17.38 | WyrM | its easier. |
| 23:19.44 | WyrM | btw, I need to finish mux cleanup. |
| 23:20.15 | WyrM | but pcap-regulator is more fun ATM, now that I have info on all the voltages! |
| 23:25.47 | sabrod | It's so nice for your E680 board! :p |
| 23:26.34 | sabrod | Btw, it's maybe to feed a well known latin american motorola linux developer that they released that... |
| 23:26.58 | sabrod | ( to keep you busy while they violate GPL on A1600 :) |
| 23:27.04 | sabrod | ) |
| 23:27.46 | sabrod | OpenEZX is problematic in fact I think we should stop all :D |
| 23:29.06 | sabrod | It is making the motorola phones so cool!! They should won billions on us... (damn I wait until may 5, to launch my april's fool) |
| 23:30.41 | sabrod | Ok, so I understand better... I make work BP on my A910i, it could be a matter of locked BP? |
| 23:30.55 | sabrod | My a780 is in fact unlocked... |
| 23:33.48 | WyrM | sabrod: no, bp on a910 is probably just something worng on openezx. |
| 23:35.22 | sabrod | well, sure... |
| 23:36.44 | sabrod | I know there a lot :D |
| 23:49.48 | tmzt | WyrM: you're working on a vreg implementation? |
| 23:49.56 | WyrM | tmzt, yes |