-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| When performing a 'nand erase rootfs' I get the following:
|
|
| GTA02v5 # nand erase rootfs
|
| NAND erase: device 0 offset 0x96, size 0xf6a
| Skipping bad block at
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi Andy,
|
| Thanks for a feedback -- I just want to mention again that those are
| pure qtopia images -- both kernel and rootfs and without any consecutive
| opkg upgrades, so I guess there should be no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|
|
| Jim wrote:
| Read the Wiki: http://wiki.openmoko.org/wiki/Booting_from_SD
|
| Make sure the kernel you're using has ext3 built into it. Using ext2 has
| been suggested for the microSD because it will
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| * arne anka [EMAIL PROTECTED] [2008-07-30 12:18 +0200]:
| I've tried with several host machines, unfortunately it didn't change
| anything.
| different in respect to kernel-major/minor/patchlevel and/or usb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hey Tim,
|
| no it's not overkill or no is the glamo driver able to read that
fast?
| Are you involved with or knowledgeable of how the glamo drive works?
| I'm not.
I have that not very marketable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| arne anka wrote:
|
| what gives
| df -h
| ?
|
| Indeed, thanks for the tip. It seems that it is still mounted at
| /media/mmcblk0p1 but it is no longer accessible at /media/card (which
| it was before
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|
| Oh well, I should have bought a slower card. At least it won't be a
| limiting factor.
| I'll compare speeds I get with your 3M bytes/sec. anyway.
|
| I was meaning 12 megabits /sec
| By 12MB/s I was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Andy Green wrote:
| Someone was saying they will look at XGlamo and I don't think you're the
| only one seeing some shakiness.
|
| Well, I'll use Xfbdev until there will be something of new in XGlamo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| My FR's SDHC card's partition table became corrupted recently. Any
| ideas why? I'm using a sandisk 8GB SDHC. This happened over the
| weekend, and it's been since I reformatted the card monday morning.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| This may seem trivial, but I can't seem to find anything on how to do
| this directly.
|
| Is there an easy way to pull my existing fs flash image OFF my phone
| so I can save the current config? I want to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi,
|
| in the most recent kernel, USB networking is no longer compiled in, but
| compiled as a module. I think that's generally a good thing, the problem
| is that the upgrade path seems to be broken: I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Has there been any changes to charging? (modules needed?) For todays
| kernel I cant get USB charging above 100ma.
Last charger-related patches went in over a week ago, it'd be bad if we
stuck charging
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| ~ - binning the finegrained module packaging and having the modules
| all
| inside the kernel package
|
| nope.
|
| ~ - if not, making some modules dependencies of the kernel package
|
| yes.
|
| ~ - doing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi,
|
| The openmoko neo gta02 hangs frequently. I'v upgraded the software but
| no use. It is happening mostly during calls, working with address
| book, or any other software. Then I have to remove to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| The strategy above allows us to easily add and remove packages while
| maintaining stable end-user systems. Until the dust settles on the
But so does a single kernel package that includes the modules.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi again.
|
| I'd also like to see such a page about the battery issues.
| I mean that stuff with flat battery, possible workarounds that work
| right now. And what will be/could be fixed in the future
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| i am i bit at loss with the current state of avaliable updates (server
| glitches, 404, checksums instead of dates and kernel images/modules).
| - what u-boot is recommended
Tomorrow's U-Boot is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| # opkg install kernel-module-g-ether kernel-module-cdc-ether
| # depmod
| I did not follow the full discussion on the kernel list. Does this mean
| you
| are not able to connect via Ethernet over USB unless
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Sunday, 3. August 2008 04:33:11 Andy Green wrote:
| Liek so much else, that's just waiting on someone saying DO IT. What
| else is it waiting on precisely?
|
| Correct me if I'm wrong:
| Our booting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| How about sidestepping the issue and have standard rescue kernel thats
| monolithic? - could even be recommended practise to have it on the SD
| card ready to go (like a dual boot). Doesnt need to be the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| after opkg upgrade from ssh, i get the infinite irq error messages
| scrolling away. I followed
| http://www.mail-archive.com/support@lists.openmoko.org/msg00068.html but
| to no effect. If i restart X I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| pcf50633_irq: entering(irq=53, pcf=c7d34c00): scheduling work
| pcf50633_work: INT1=0x00 INT2=0x00 INT3=0x40 INT4=0x00 INT5=0x00
| ADCRDY ===
Is something sitting polling the voltage on the battery using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I am happy to try anything, but i can't find a how-to for altering
| loglevel or disabling tty0. I don't have a debug board, if that makes
| any difference.
Both of these can be done on the kernel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Could someone point to these valid u-boot*.bin files please ?
|
http://buildhost.openmoko.org/daily/freerunner/200808/20080804/uboot-gta02v5-latest.bin
| and got a message displayed advertising some april
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Thank you very much, I will play with those when i can connect again (i
| reflashed the root filesystem, which has the freerunner working as new
| again, but now i have lost usb0 on the host laptop).
:-/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I've configured WiFi on a fresh FSO image the same way I had on a 2008.2
| image--by creating a wpa_supplicant.conf file and editing
| /etc/network/interfaces. This configuration worked on the 2008.2 image
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| NAND read: mtdparts variable not set, see 'help mtdparts'
Environment is uninitialized somehow.
Run
dynpart
saveenv
at the U-Boot prompt see if that helps.
- -Andy
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| So obviously, the version on u-boot's prompt is not meaningful,
| then... :(
|
| Should I file a bug report ?
Yes, it's telling you about the upstream git version / date I guess, but
we don't intend to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Andy Green escreveu:
| Somebody in the thread at some point said:
| | I've configured WiFi on a fresh FSO image the same way I had on a
2008.2
| | image--by creating a wpa_supplicant.conf file and editing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I can wget files hosted on the local side of the router, cannot wget
| anything external. ping -s 4096 192.168.1.1 http://192.168.1.1 still
| works.
Props to Cesar then, looks like he had the right idea.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| # strings current-uboot.bin | grep git
| U-Boot 1.3.2+gitr18+64eb10cab8055084ae25ea4e73b66dd03cc1a0cb (Aug 4
2008 - 02:33:52)
| Neo1973 Bootloader U-Boot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Ever since I flashed the latest firmware from
| http://buildhost.openmoko.org/daily/freerunner/200808/20080805/ , the
| led light stays light after boot.
|
| The files I used are :
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Gta02v5 is the mass-production version.
Yes that one is good for A6 too when they come. A6 is same as A5 except
for very minor changes in components.
| I took the plunge and flashed the 'fore mentioned
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| 2008/8/5 Joerg Reisenweber [EMAIL PROTECTED]:
| Only thing you may try for now is changing GSM-provider, as it seems
to be
| very clear the issue is to be found on some GSM-networks, and not (or
less)
| on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| 2008/8/5 Andy Green [EMAIL PROTECTED]:
| Do they say the buzzing is consistent, or it comes and goes?
|
| I've not asked in any detail. What frequency of coming and going has
| been reported? Are we talking
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I've found the daily u-boot images at
| http://buildhost.openmoko.org/daily/freerunner/200808/20080805/
|
| Which one do I use? There are 3 versions for the gta02v5 - what is the
| difference?
I guess this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Just a note, on the skelephone that I use I replaced the GSM antenna
| with a short length of patch wire, it still works (and some guy was
| complaining normal GTA02 is for hardcore hackers). I guess if I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Am Mi 6. August 2008 schrieb Andy Green:
| Somebody in the thread at some point said:
|
| | Just a note, on the skelephone that I use I replaced the GSM antenna
| | with a short length of patch wire
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I had this problem when I put obexftp into the startup for my bluez.
Turns out it doesn't auto-background, so it was hanging there just
after the startup. Happily, I was able to ssh in, fix it, and kill
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Feydreva [EMAIL PROTECTED] writes:
|
| yeah, it turns off at one point... but it s not consistent...
|
| Well, it may be consistent to the fact that the phone eventually drops
| charging at one time even
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I changed the kernel name based on something I read stating it had to be
| called uImage.bin (is that wrong?)
It needs to match whatever you called it on the kernel commandline in
U-Boot, our ones use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| The problem I now have is that I am unable to get usb0 recognized as an
| interface by ifconfig.
|
| The command:
| ifconfig usb0 192.168.0.200
|
| results in
| SIOCSIFADDR: No such device
| usb0: ERROR
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Aug 6 11:25:36 ubuntu kernel: [ 926.860809] cdc_acm 3-1:1.0:
ttyACM0: USB
| ACM device
| It seems the device is detected just as it is powering down.
Powering down or rebooting into U-Boot?
- -Andy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| You are right that I did not extract the rootfs, but that is because 1)
| I do not know how to extract the rootfs and 2) none of the various
| instructions on the wiki (which are inconsistent) worked for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Andy Green wrote:
|
| setenv bootcmd mmcinit \; ext2load mmc 2 0x3200 uImage.bin \;
| setenv bootargs \${mtdparts} rootfstype=ext2 root=/dev/mmcblk0p2
| console=ttySAC2,115200 loglevel=4 init=/sbin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| DFU this into the kernel partition and you should be good for
Debian, I
| use these kernels with it myself all day.
|
|
| How do I DFU this into the microSD's kernel paritition?
Sorry I was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I understand that the usb tether drivers were moved out as kernel
| modules. However, for the Debian port to work, I need them as part of
| the kernel. Can someone point me to how I can re-compile the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi,
|
| After flashing 200808 with kernel and rootfs from 20080806, I have no
| usb and no working wifi.
| Wifi connects, the wireless AP says so. but a quick nmap of my
| network show no new IP picked up
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Following the instructions at :
| http://wiki.openmoko.org/wiki/Debian#Get_touchscreen_working , I was
| able to get touchscreen to work as a mouse. But, the cursor is way off
| from where I am touching. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Doesn't make any sense to me either... can you md5sum the broken
copy
| before overwriting it?
|
|
| Ok. Will do that the next time I get it. Also, I was using the ASU
| kernel so far. Switched to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| 1. klogd went very busy and dmesg got full of
| evbug.c: Event. Dev: NULL, Type: 0, Code: 0, Value: 0
| evbug.c: Event. Dev: NULL, Type: 2, Code: 0, Value: 54
| evbug.c: Event. Dev: NULL, Type: 2, Code: 1,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| How can I tell/make sure my Freerunner is actually charging?
| There is what appears to be a lightning bolt in the top right corner,
| but that's there whether it's plugged in or not.
|
| And, since it goes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Sry I misread your post. Knowing if it's charging or not goes with the
command:
|
| cat /sys/devices/platform/bq2700-battery.0/power_supply/bat/status
|
| Also here the bug is responsilbe for no gui-view of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi.
|
| I've been using my FreeRunner quite a lot since I got it and yesterday
| evening I played with USB host mode (the goal was to use a normal USB
| keyboard in the terminal). However, I reported my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| You can work around it with another battery that has charge;
| externally
| charging you battery with external charger; or the not recommended but
| I did it and there was no smoke in my case provide
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi andy-
| |
| | Is it possible that this issue happened with the neo1973 as well, by
| | any chance? I have a neo1973 that also refuses to power on no matter
| | what I do with it .. maybe I should use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I flashed the latest build (2008.8.11) from
| http://buildhost.openmoko.org/daily/freerunner/
|
| USB networking is gone. Glamo doesn't seem to be installed by default
| either. And, Om2008.8 doesn't update
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|
| What does that actually mean, both gone (what appears on host dmesg
| when you plug it in) and Glamo doesn't seem installed by default...
| you mean XGlamo?
|
|
| Yes, XGlamo doesn't seem to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|
| Fine -- I don't think the issue comes from that direction if you have
| usb0 up on your host. I guess it is somehow network interface
| config issue.
|
|
| As in, network config issue on the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I have somewhere between 400 and 800 mb of openstreetmap data on the SD
| card. (As reported by du -hs; many of the files are 4KB...)
I guess it is a pathological filesystem for this thing, but still I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hello,
|
|
| I did the same update as Thomas here :
http://lists.openmoko.org/pipermail/support/2008-August/000900.html
| And now I miss the modules g-ether and cdc-ether.
|
| His solution:
| My solution
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
| To what are you referring? Did you see that in the linked qtopia code?
| no. i think you said that -- umount/mount on suspend/resume was a
| workaround except when resuming from gsm event. am i wrong?
| Oh, yes. That is what it seemed like.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hello all--
|
| I was wondering, is there some sort of application that will let me
| manually fade the openmoko screen to black? Similar to a screen saver?
| Thanks!
What are you, some kind of Goth? :-)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|
|/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/backlight/pcf50633-bl/brightness
Wow thunderbird thought it knew better... that's actually a greater-than
symbol not a pipe symbol.
- -Andy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Andy Green wrote:
| Somebody in the thread at some point said:
| | Hello all--
| |
| | I was wondering, is there some sort of application that will let me
| | manually fade the openmoko screen to black
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| The usb modem is recognised succesfully by the kernel, just simply
| configure ppp to get it connecting to the net.
| I tried with the huawei 270 modem and I succesfully connected but I
| can't ping
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Sun, Aug 31, 2008 at 6:41 PM, Andy Green [EMAIL PROTECTED] wrote:
| Sometimes when I use it on normal laptop, I get bogus DNS in UK.
|
| You mean like if you use
|host somedomain.com
| on your Linux
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hello dear all,
|
| My new FR (DateCode 20080725) is suspected to having bad NAND blocks:
| It had been suffering kernel panics etc. after as soon as I reflashed it
| with Om2008.8 on 20080831. Subsequent
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| now where is the function read? and what does this function? I can't
find anything in the sam7dfu.c and in the included files, there is even
no function read.
| Only one file I can't check because I dunno
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| man 2 read
|
| on a Linux box, read() is part of C standard library.
| thanks for answer ;)
|
| but I get on my Ubuntu
| man 2 read
| No manual entry for read in section 2
|
You can see it here --
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| [3.165000] mmcblk0: mmc0:b368 SMI 498176KiB
That's the good part above, it talked to the card and got information
out of it (512MB card).
| [3.17] mmcblk0:6glamo-mci glamo-mci.0:
| Error
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hello,
|
| I've tried to upgrade software on my Freerunner, but when I'am trying
to enter
| DFU mode it doesn't work. I'am booting from NOR as described here:
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| mmcblk0: mmc0:b360 USD 7070656KiB
| mmcblk0:6glamo-mci glamo-mci.0: Error after cmd: 0x8310
...
| glamo_mci.sd_max_clk=1000
|
| This did help, I followed instructions at
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi xiangfu:
|
| i receive a new debug board and the serial console is work.
| yesterday i try to use openocd but it is not work.
|
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| The problem is that sometimes when Linux tries to access the sd card,
| the card isn't ready yet and the first read doesn't get any data. After
| the first successful read in a session everything's gravy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| After a recent reboot, the system never came back. Pushing the power
button
| causes nothing to happen. I don't even seem to get into uboot(no logo
screen). I
| don't have a debug board. I do not have a sim
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| | After a recent reboot, the system never came back. Pushing the power
| button
| | causes nothing to happen. I don't even seem to get into uboot(no logo
| screen).
|
| See if this helps: pull the battery,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Saturday 20 September 2008 02:07:51 Armin ranjbar wrote:
| after Upgrading to om2008-update , it seems to i lost my 'splash' image ,
| today i have tried to write down om2008.9 splash by
| dfu-util -a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Michael + Andy,
| I haven't had it plugged in since I had the problem a couple days
ago. so I am
| pretty certain the back up battery is empty. I tried just powering it
up now
| that I've waited and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| @Andy, here some outputs:
|
| [EMAIL PROTECTED]:~#
| cat /sys/devices/platform/bq27000-battery.0/power_supply/bat/current_now
| cat: read error: Timer expired
Something's broken somewhere... there have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| After letting the phone charge over night the battery voltage has dropped
| significantly. I'm starting to suspect the battery or else the
charging circuitry.
|
| which brings me to 2 questions:
| 1) If I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I was thinking of switching to the latest Om2008.9 from OM2007.2
| because Om2008.9 resumes a lot quicker from suspend. However, the
| battery life with Om2008.9 is greatly reduced. This leads me to
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| if it is - you are victim of the qpe halted suspend before it ever
got to the
| kernel bug. ompower is stuck waiting for apm -s to return
(indicating resume)
| at which time it will turn the light back on.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Timo Jyrinki wrote:
2008/10/1 Andy Green [EMAIL PROTECTED]:
fixed this tonight on another tree and will update stable with it later
or tomorrow.
Just as a clarification, isn't the stable kernel tree only actually
available in the unstable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Fri, Oct 3, 2008 at 2:00 PM, Andy Green [EMAIL PROTECTED] wrote:
| In the factory, SD card is used for production, so it is 100% tested
| (and fairly unlikely to die).
|
| As in, in the phone, or put
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Just a quick addition to the power topic -
|
| I compiled and ran powertop on the phone yesterday. I know there's
been some
| previous discussion of using tickless kernels on the freerunner (and the
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi all,
| I have my freerunner since around a month, and sound has always worked.
| As I've got FDOM in the flash, I tried to install the raster image,
| along with FSO. very nice peace of work !
| but I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| As I said some days ago in a discussion about flashing via dfu-util or
| doing it after having booted from SD, I did it several times now during
| the last 2 days, and it works great. Another advantage is,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| How do I tell the FR to use the external antenna instead of the
| internal? Nothing about that in the wiki.
As folks already said it's automatic: it detects the current eaten by
the LNA in the external
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi,
|
| I get huge stalls with accelerometers if using the current kernel in
| testing or self-compiled stable branch kernel. Eg. in accelgame or
| opendoom, the fps is ca. 1-3, sometimes a few frame
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Timo Jyrinki wrote:
| 2008/11/6 Michael Zanetti [EMAIL PROTECTED]:
| What do you mean with working fine now? Are they working as they
were always
| or are they now really working (no crashes on suspend or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Am Do 4. Dezember 2008 schrieb Andy Green:
| Somebody in the thread at some point said:
|
| | Further plans: modify driver to take down the complete LCM via LDO6
| instead of
| | entering deep_suspend
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| That did it, allright.
|
| I never thought to try it, since the instructions said to check the
| dmesg (which told me to use qi-s3c2410-master_2ad3ce6ff57753e3.udfu) or
| to use the 6410 image...
|
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| How about the NOR U-Boot, this has been quite reliable in bringing up
| backlight in my experience? What happens with backlight if you hold
| down AUX during powerup to get into NOR U-Boot?
| When I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi everybody,
|
| I have been using Freerunner as a daily phone for some months now, and
| yesterday it suddenly stopped registering the GSM network. It was
| working fine in the morning, sending/receiving
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi,
|
| For instance, the Openmoko GPS signal level is bummed because of a
| hardware fault, also there are merely quirks to solve them. The
... which was worked around in kernel once the aggressor signal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Yeah, If I were going to file it a ticket, it would be this: 'Make
| Openmoko work all the time, in all these scenarios'. I'm sure my ticket
Well, every day I have to figure out what to spend time on, if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I clearly don't blame the developers here myself. I blame Openmoko's
| selfish management (probably it's board of directors or C*Os) for
| this. I am sure that a developer who talks back against this will
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| The website of Openmoko's launch will tell you when the Openmoko
| Freerunner was released.
| My bills will tell you when I have purchased the Freerunner.
| My Freerunner is available to prove the bugs in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| A quick thought...if Openmoko feels the hardware of GTA02 is inadequate
| to even bother making it a stable phone, should there not be some sort
| of recall and free replacement with a GTA03.
Yes. That
1 - 100 of 126 matches
Mail list logo
