-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| by the way...should I bugreport or is there others things to try such as
| the SD strength?
This problem is bigger than access to your SD Card, it is basically
issue of stability communicating with whole
by the way...should I bugreport or is there others things to try such as
the SD strength?
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| and a screen like a tv without antenna...
| i reboot
That doesn't sound good at all. If you ever see juddery or noisy screen
thing then SD Card communication is totally corrupted.
It's juddering about
Have you seen this screen corruption thing before or is this the first
time?
It's the first time that i've got a tv-like corruption
But one night i kept it on and connected to the power trough the power
adapter
and there was also a corruption...a little bit like when a CRT monitor has
the wrong
How did you do this, from kernel commandline or by changing module
parameter after boot completed?
- -Andy
echo
cd /sys/module/glamo_mci/parameters
echo 1000 sd_max_clk
___
Openmoko community mailing list
community@lists.openmoko.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| How did you do this, from kernel commandline or by changing module
| parameter after boot completed?
| echo
| cd /sys/module/glamo_mci/parameters
| echo 1000 sd_max_clk
I don't think this is enough,
If you can amend the kernel commandline in U-Boot to have
~ glamo_mci.sd_max_clk=1000
then the change will have effect from the first time the card is looked
at in Linux and I guess it will work around it.
I just ordered a bunch of 8GB cards to see if I can reproduce this and
finally
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| glamo_mci.sd_max_clk=1000 rootfstype=jffs2 root=/dev/mtdblock6
| console=ttySAC2,115200 console=tty0 loglevel=8 regular_boot
|
dmesg | grep glamo
after boot.
$ cat dmesg | grep glamo
Kernel command line: glamo_mci.sd_max_clk=1000 rootfstype=jffs2
root=/dev/mtdblock6 console=ttySAC2,115200 console=tty0 loglevel=8
regular_boot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| glamo3362 glamo3362.0: Glamo core now 49119232Hz CPU / 81887232Hz Memory)
The kernel is not from the last week or so? It should have 89MHz PLLB
on the Glamo now not 81MHz.
| glamo-mci glamo-mci.0:
On Fri, Sep 19, 2008 at 03:53:36PM +0100, Andy Green wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| glamo3362 glamo3362.0: Glamo core now 49119232Hz CPU / 81887232Hz Memory)
The kernel is not from the last week or so? It should have
The kernel is not from the last week or so? It should have 89MHz PLLB
on the Glamo now not 81MHz.
the kernel is from FSO milestone III...otherwise the wifi would have not
worked
i ran a new install with logread -f log2.txt and here are the logs:
Sep 19 17:25:27 om-gta02 daemon.notice modprobe:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| The kernel is not from the last week or so? It should have 89MHz PLLB
| on the Glamo now not 81MHz.
| the kernel is from FSO milestone III...otherwise the wifi would have not
| worked
Sorry, what's broken
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Fri, Sep 19, 2008 at 03:53:36PM +0100, Andy Green wrote:
| -BEGIN PGP SIGNED MESSAGE-
| Hash: SHA1
|
| Somebody in the thread at some point said:
|
| | glamo3362 glamo3362.0: Glamo core now
Sorry, what's broken with Wifi in later kernels?
no not the later kenrel...I was told that the kernel from om2008.8
couldn't make wifi work...and i tried without success so I updated kenrel
This looks like your /lib/modules doesn't match your kernel?
yes it doesn't i didn't bother updating it
That's where insanity sets in 5 minutes later.
Mabe it's the debian installer that is responsible...i am testing it
without the debian installer copying files:
/dev/mmcblk0p23.8G 1.2G 2.4G 33% /media/mmcblk0p2
actually it's doing dd if=/dev/urandom of=./random
at the
This is just another SD corruption data point, and a partial one,
since I'm afraid I've lost any detailed logs.
I am running Qtopia on flash, and Debian on the SD card. Two days ago
I found that booting into Debian failed at the point of trying to
mount the rootfs; the last message was Kernel
Hello,
I've bought a MMBGR04GUACY-NA and its adapter...
but the card produce I/O errors in dmesg...
I was using the kernel from FSO milestone 3
if I remember well it does the same with 2008.8
I've tried lowering sd_max_clk to the 1000
I've tried increasing the drive strength to 3
I'd really
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hello,
| I've bought a MMBGR04GUACY-NA and its adapter...
| but the card produce I/O errors in dmesg...
| I was using the kernel from FSO milestone 3
| if I remember well it does the same with 2008.8
|
|
19 matches
Mail list logo
