-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| 2009/3/10 Andy Green :
|>
uImage-2.6.28-oe1+gitr34240a1c06ae36180dee695aa25bbae869b2aa26-r3-om-gta02.bin
|>
|> Well it's from Jan 5th.
|>
|> If you're feeling adventurous (you can b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I've just flashed Qi, 2.6.28 and FSO 5.1.
Is there a git hash associated with this "2.6.28" kernel at all?
| When the FR resumes, the screen goes white and then slowly fades to black.
- -Andy
-BEGIN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Il giorno lun, 09/03/2009 alle 23.48 +0200, Timo Juhani Lindfors ha
| scritto:
|> "Pietro \"m0nt0\" Montorfano" writes:
|>> Sooo, how it's that possible?? Why can't we simply patch the driver
|>> which make
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi, i've bought a 4GB uSD and i've partitioned it to try and test a lot
| of distro, done 10 partitions (1 for kernel and 1 extended for logical
| partitions) booted and only 7 partitions shown, no prob
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| 2009/3/9 Andy Green mailto:a...@openmoko.com>>
|
| [...]
| What does the "noise" look like, is it also the top-down block of
static
| "random" pixels described
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I'm experiencing read/write error on my 8GB SD card Kingston C08G
| SDC4/8GB 07 (wiki reports this card shoud work!) with 2.6.28 shr-testing
| kernel and with 2.6.24 from 2008.12, followed some times by NSOD
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|> Does hwclock also show the correct date?
|
|>> hwclock otoh shows the correct
|>> time.
|
|
|> Which kernel version are you
|> running?
|
| 2.6.28-20090105.git69b2aa26
|
|> At least the andy-tracking branc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Mon, Mar 02, 2009 at 12:32:51PM +0100, arne anka wrote:
|> when i resume the fr, the time zhone shows (and the date command) is
the
|> one when the fr suspended (ie, suspending the fr at 16:43 and
resumin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Feb 24, 2009 2:31am, Andy Green wrote:
| > Suspend and resume on 2.6.24 only works by luck, it's not telling us
| much.
|
| OK. You are saying that with uBoot+2.6.24, it wasn't suspendi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| 2009/2/22 Jeffrey Ratcliffe :
|> The only other thing I did around the same time was to replace uBoot
with Qi.
|
| To test this, I booted into NOR, thereby using uBoot, and then booted
| the 2.4.24 image aga
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|> Maybe, but the actual error here is to do with the "format" of the jffs2
|> partition. It can be broken in kernel but I think we would have heard
|> about it before, 2.6.28 is "old" now in kernel terms.
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|> Dunno what you can do about it, but the guy who owns the process for
|> generating the jffs2 image for Debian may get a hint from this to change
|> how he generates it. jffs2 mount should be a few seconds
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|> It seems that it takes a long long while to mount the jffs2 partition
|> you have. The first thing "CPU 0 stall" is just a comment that you seem
|> to be stuck for two minutes, then the second thing is a d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| i just found out that 2.6.28 is avaliable in debian and immediately
| upgraded -- booting now shows a lot of weird messages jiffs2 related,
| from which i can't make anything.
| [21474543.18] RCU dete
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Rename the file from checkroot.sh to checkroot, and it achieves the same
| effect (it is run in a shell instead of being sourced).
|
| As I said previously, this was an upstream OE bug which made it's way
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Wed, Feb 11, 2009 at 12:11 AM, Marc Bantle wrote:
|
|> Until current rootfs' get fixed, I dropped the 'ro' option in
|> the boot options.
|
| Thanks to all of you for you help. But I tried something else
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Yes, I suspect that the first message ("dbugfs dir creation failed") is
| coming from the android kernel and that the power_supply message was
| appearing before qi -- I think I'm just now noticing it becau
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi, all:
|
| Just flashed qi (GTA02), and I get the flash, the vibration, and then this
| message:
|
| s3c2410_udc: debugfs dir creation failed -19
| power_supply bat: driver failed to report `status' proper
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| My install of FSO M5 is not on a SD card.
|
| As I said, all my problems where related to the fact I was using Qi,
| instead of uBoot.
It's not immediately obvious how Qi can trash the GSM connection and
l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
[4.965000] AR6000 connected event on freq 2437 with bssid listenInterval=100, beaconInterval = 100, beaconIeLen = 22
assocReqLen=59 assocRespLen =59
[4.965000] Network: Infrastructure
looks OK
| e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|> I got verification message from the OpenMoko Trac and publish this bug
|> report under the Ticket #2227.
Thanks.
- -Andy
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using Gn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|> In my FSO M5-equiped FR eth0 visible by iwconfig and my WiFi points
|> successfully scaned by iwlist.
|
| Since the previous Jan 5th basis I understood the kernel had, there are
| relatively few patches.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|> r...@om-gta02:~# ifup eth0
|> WPA: Configuring Interface
|> ioctl[SIOCSIWENCODEEXT]: Operation not supported
|> ioctl[SIOCSIWENCODEEXT]: Operation not supported
|> ioctl[SIOCSIWENCODEEXT]: Operation not su
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|
| just restore those .state files from whatever package they come from
| (don't recall) -- I git the same issue with that mixer -- better never
| click 'save' on the first tab ;)
|
| Thank you, Mr. Halchenko
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| 2009/2/1 Jeffrey Ratcliffe :
|> shutdown now
|
| Figured it out. This should be:
|
| /etc/init.d/halt stop
Or shutdown -h now
- -Andy
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| 2009/1/31 Andy Green :
|> So need to remove what you have in partition 1, and add a kernel named
|> /boot/uImage-GTA02.bin into partition 2 (since that's your rootfs),
|> which should be ext2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I bought myself an 8Gb uSD and installed Debian on it, but it wouldn't
| boot. u-boot simply said it couldn't find the uImage.bin, which is in
| /dev/mmcblk0p1, with the rest in /dev/mmcblk0p2.
|
| I read th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|
| Mike Montour wrote:
|> If you program the PCF50633 as:
|> - charger enabled
|> - 100mA current limit
|> - do not wake on USB insertion (avoids the brownout issue)
|>
|> then it will have the behaviou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I also tried installing Qi last night, for qi the red aux light blinks
once,
| and I get a black screen on the phone but the back light is on.
|
| with u-boot i just get the same black screen.
| This phone w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|>> The only thing that helped was removing and reloading the ohci_hcd
module,
|>> but that obviously only works with a kernel which has this one built
as a
|>> module.
|> Somebody on some list said that doing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi there!
|
| Recently I got myself a usb keyboard for my freerunner, and it works quite
| nicely after putting the fr into host mode like described in the wiki.
Well,
| except for one little thing: It only
-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 th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I'm done talking to you, Andy. If you have anything to say that isn't
| Openmoko's selfishness, I'm going to listen to you.
Fine: please post back on the support list when you have some specific
support is
-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 it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I agree with this whole thread of Openmoko's fatal mistake of moving on
| to GTA03 with GTA02 still being unstable and unusable as a primary
| phone. If GTA02 gets left behind in the dust without ever worki
-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 j
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| For instance, about the echo problem, one of the developers for
| OpenMoko stated "Since there are different hw versions out there (a5,
| a6, a7), it's impossible to provide one alsa state file that suits a
-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 y
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|> 2.6.28-rc andy-tracking kernels. Starting next week the root
|> filesystems will be adapted for these kernels and we start to provide
|> packages for them.
| Next week, not as of NOW. Clearly, the point
-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 w
-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 S
-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 boo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Then I've tried with Om 2008.9. After flashing it to FreeRunner I've
got it
| working by SSH. But the display was still empty (black and no light, I
| mean).
|
| What can I do to understand where's the prob
-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...
|
| Myster
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| right now had a totla freeze when trying to execute a local script in
| flash -- and could see the notice again when rebooting:
|
| JFFS2 notice (700):check_node_data: wrong data CRC in data node at: read
|
-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
|> | enteri
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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. This seems to be the more reasonable approach for
| saving power while LCM disabled anyway, and it mig
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi
|
| I just bought a Freerunner - however, I can't see the device of the
| mmc/microSD!
Someone else reported similar trouble and fixed it by adding some paper
to make the uSD card press down on to the co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I almost think that it's the battery that went mad temporarily (see
The batteries do have a "safety cutoff" feature that disconnects the
actual battery part from the terminals at the top of the battery. T
-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 susp
-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 rapid
-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 ant
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Armin ranjbar wrote:
> On Tue, 23 Sep 2008 21:28:45 +0100
> Andy Green <[EMAIL PROTECTED]> wrote:
>
> Well ,
> no such line in printenv
>
> when i try to setenv exactly your line , ill get 'Error: Bad gzipped
>
-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, a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Risto H. Kurppa wrote:
|> Hi!
|>
|> Some months ago we had this GPS time to first fix issue that was
|> handled with a software fix. However the new Freerunners ship with the
|> hardware fix (you can see a s
-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 had
-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
| proble
-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 p
-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" ke
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lucas Charron wrote:
> [2.25] mmc_set_power(power_mode=0, vdd=0
>
> In reading other mailing lists, the 6 "Error after cmd" are normal and
> just part of the startup. However, after that, glamo should detect my SD
> card.
Right, when it sets
-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
-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
| beli
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Everything boots and works properly while powered on. All my distros
| I've used work properly. The problem is when I shut down the device, it
| starts clicking, until I press power button again which then
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Sander van Grieken noticed (1) "that these partitions have to be in the
| beginning of the SD card.
| I wasn't able to boot from partitions starting at the 7GB mark."
|
| Any ideas much appreciated !
I kno
-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 wa
-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 bee
-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 nothin
-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:
|> | 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 batte
-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:
|> I take it from Your reply that I (i.e. the average FR user) should be
able to
|> see the battery status on the indicator?!
| If you are indeed using a CC battery, then something is broken. I heard
| about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Sunday 21 September 2008 18:51:48 Olivier Berger wrote:
|> Hi.
|>
|> Looking at http://downloads.openmoko.org/releases/Om2008.8-update/ I
|> can see gta02v5_and_up-u-boot.bin which looks to me like the mo
-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 an
-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:
| mmcblk0: mmc0:b360 USD 7070656KiB
| mmcblk0:<6>glamo-mci glamo-mci.0: Error after cmd: 0x8310
...
|> glamo_mci.sd_max_clk=1000
|
| This did help, I followed instructions at
| http://docs.openmoko.org
-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:
| http://wiki.openmoko.org/wiki/Flashing_the_Neo
-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:<6>glamo-mci glamo-mci.0:
| Error
-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 -->
ht
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| --- "Neng-Yu Tu (Tony Tu)" <[EMAIL PROTECTED]> wrote:
|> These is marker from factory SMT line for
|> distinguish 900/1800/1900 and
|> 850/1800/1900 phones, not fired :)
|
| thanks! that's a definite releif.
-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 dun
-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 re
-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
-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 anythi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Is it possible to create another small partition of 1 MB size and put
| grub into it? My hope is to have the kernel again within the partition
| like in the good old days (at least for the SD-card) and not i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I have completely drained my battery to the point where the Freerunner
| will not boot and hence I cannot charge it.
|
|>From the Wiki:
|
|> Make sure that the battery never discharges completely. This is an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Am Freitag 15 August 2008 schrieb sparky mat:
|> I noticed the 'Official Debian port' section on the debian page in the
|> wiki. Wow! That's cool!
|>
|> Has someone tried this? If so, can someone update the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Fri, Aug 15, 2008 at 11:12:58AM +0100, Andy Green wrote:
|
|> I use Debian in runlevel 3 at the moment, I noticed the initscripts are
|> pretty slow. Are there alternative initscript systems
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi,
|
| Am Mittwoch, den 13.08.2008, 22:49 +0200 schrieb Jay Vaughan:
|>> I also added a short description on how to get GPS working on Debian:
|>> http://wiki.openmoko.org/wiki/Debian#GPS
|>
|> rockin', i'm
-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
-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:
| 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
|>> 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,
|
|
| 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 wa
-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
-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 F
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I've noticed that I have to manually turn the volume up after each call
| I make with the 2008.2 image. Other than that, calls under 2008.2 work
| fine.
I guess it pulls a canned ALSA state file out each
-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 t
-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:
| 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:
|> 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 e
1 - 100 of 191 matches
Mail list logo
