Re: Sandisk 16GB SDHC not mountable

2010-10-03 Thread Christian Rüb
Thanks for offering help.

2010-10-02 01:28:02 Alfa21:
 2010-10...@20:04 Christian Rüb
 
  I partitioned my 16GB SDHC (class 2) card
 
 have you tried to use it as raw storage? (no filesystem)
 
 cat plaintextfile.txt  /dev/mmcblk0p1
 less -f /dev/mmcblk0p1

I could not read it back, but using /dev/mmcblk0 it showed up somewhere near 
the beginning (it was cat to /dev/mmcblk0p1 though)

 you should be able to read your contents of the original input file.
 if you fail to less it on the FR, try the second command on your PC.

showed up at partition start

 
 try the same directly on /dev/mmcblk0 but this will destroy all your data on 
 uSD (partition table Co.)

I saw the contents only once and about at the same place when catting it to 
/dev/mmcblk0p1 (Freerunner)
Once at the beginning and once about where 1 partitions starts (PC).


 have you tried with a whole different fs, like fat32?

same result :( (Freerunner)
On my PC FAT32 and ext3 work ...

Note that I booted using Qi and system is on NAND (kernel 2.6.29)

Christian

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: Sandisk 16GB SDHC not mountable

2010-10-03 Thread Christian Rüb
 Thanks for offering help.
 
 2010-10-02 01:28:02 Alfa21:
  2010-10...@20:04 Christian Rüb
  
   I partitioned my 16GB SDHC (class 2) card
  
  have you tried to use it as raw storage? (no filesystem)
  
  cat plaintextfile.txt  /dev/mmcblk0p1
  less -f /dev/mmcblk0p1
 
 I could not read it back, but using /dev/mmcblk0 it showed up somewhere near 
 the beginning (it was cat to /dev/mmcblk0p1 though)
 
  you should be able to read your contents of the original input file.
  if you fail to less it on the FR, try the second command on your PC.
 
 showed up at partition start
 
  
  try the same directly on /dev/mmcblk0 but this will destroy all your data 
  on uSD (partition table Co.)
 
 I saw the contents only once and about at the same place when catting it to 
 /dev/mmcblk0p1 (Freerunner)
 Once at the beginning and once about where 1 partitions starts (PC).
 
 
  have you tried with a whole different fs, like fat32?
 
 same result :( (Freerunner)
 On my PC FAT32 and ext3 work ...
 
 Note that I booted using Qi and system is on NAND (kernel 2.6.29)
 
 Christian

I now get all sort of weird behaviour:
I created ext2 on 1st partition on FR, then tried a fsck and got many short 
read errors, after that the partition table was gone.
I repartioned, created ext3 and after that could not even access SD card in any 
way.
dmesg gave a lot of:
[  244.985000] end_request: I/O error, dev mmcblk0, sector 169
[  244.995000] glamo-mci glamo-mci.0: Error after cmd: 0x8120
[  244.995000] mmcblk0: error -110 sending read/write command, response 0x0, 
card status 0x400b00
[  244.995000] end_request: I/O error, dev mmcblk0, sector 170
[  245.01] glamo-mci glamo-mci.0: Error after cmd: 0x8120
[  245.01] mmcblk0: error -110 sending read/write command, response 0x0, 
card status 0x400b00

Now even fdisk does not find the card anymore. As from the wiki I thought the 
card would work :(

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: Sandisk 16GB SDHC not mountable

2010-10-03 Thread Gennady Kupava
Hi, Christian,

В Вск, 03/10/2010 в 13:11 +0200, Christian Rüb пишет:

 [  244.995000] mmcblk0: error -110 sending read/write command, response 0x0, 
 card status 0x400b00
 [  244.995000] end_request: I/O error, dev mmcblk0, sector 170
 [  245.01] glamo-mci glamo-mci.0: Error after cmd: 0x8120

You can try to add something like glamo_mci.sd_max_clk=1500 to you
kernel options. Try different values until your card will start working.

Gennady.




___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: Sandisk 16GB SDHC not mountable

2010-10-03 Thread Alfa21
2010-10...@11:16 Christian Rüb

  cat plaintextfile.txt  /dev/mmcblk0p1
  less -f /dev/mmcblk0p1
 
 I could not read it back, but using /dev/mmcblk0 it showed up somewhere near 
 the beginning (it was cat to /dev/mmcblk0p1 though)

mmh... maybe less is not installed by default, sorry :P
ok, near the beginning maybe after the 512 stuff of mbr and the partition table 
if p1 is at the beginning of your device, it's ok and regular thing.
(you'd imagine your device as a long tape with one thing after each other)

strange you are not able to read the p1 but only the whole device

 
  you should be able to read your contents of the original input file.
  if you fail to less it on the FR, try the second command on your PC.
 
 showed up at partition start

right

 I saw the contents only once and about at the same place when catting it to 
 /dev/mmcblk0p1 (Freerunner)
 Once at the beginning and once about where 1 partitions starts (PC).

right, once at the beginning of the whole device and one where was the 
beginning of the old p1
(data remains there until overwritten with new data, usually it's never cleared)

 same result :( (Freerunner)
 On my PC FAT32 and ext3 work ...

also with fat32 directly on whole device? (no partition table)

 Note that I booted using Qi and system is on NAND (kernel 2.6.29)

sorry but I do not know if 2-4-2 or default change anything, I use qi too but 
the plain one and with 8GB uSD.

 Now even fdisk does not find the card anymore. As from the wiki I thought the 
 card would work :(

me too.. I was about to buying a 16GB one! :P
btw, maybe you should clear your uSD...

dd if=/dev/zero of=/dev/mmcblk0 bs=512 count=2048

WARNING: THIS COMMAND IS REALLY DESTRUCTIVE!!!
(this will totally blank the first 1MB on your device, so mbr, partitions, some 
data Co.)
double check the of= value before return!!!

try to build all your tables on a real PC instead of FR

-- 
ALFA21 IS PROVIDED AS IS AND WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR 
IMPLIED.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: qtmoko v27

2010-10-03 Thread Gand'
Since i moved to the v27, my touchscreen is kind of weird ... I can't draw a
straight line, and when i keep the stylus on the screen, it draws a tiny
star (more or less 9mm²) It makes the docked keyboard pretty unusable as
when press a key, one of the surrounding key often responds ...
-- 
  Gand'

On Tue, Sep 28, 2010 at 11:52 AM, Patryk Benderz patryk.bend...@esp.plwrote:

 [cut]
  Also it can compare only system clock with RTC, so we always assume that
  system time is correct. Calypso time - do we need it at all?
 Maybe to correct drifting RTC?
 --
 Patryk LeadMan Benderz
 Linux Registered User #377521
 ()  ascii ribbon campaign - against html e-mail
 /\  www.asciiribbon.org   - against proprietary attachments


 ___
 Openmoko community mailing list
 community@lists.openmoko.org
 http://lists.openmoko.org/mailman/listinfo/community

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: Sandisk 16GB SDHC not mountable

2010-10-03 Thread Christian Rüb
Hi Gennady,

thanks for your suggestions.

  [  244.995000] mmcblk0: error -110 sending read/write command, response 
  0x0, card status 0x400b00
  [  244.995000] end_request: I/O error, dev mmcblk0, sector 170
  [  245.01] glamo-mci glamo-mci.0: Error after cmd: 0x8120
 
 You can try to add something like glamo_mci.sd_max_clk=1500 to you
 kernel options. Try different values until your card will start working.

Tried these and also showing results:
1500 - partition skipped (led + vib)
500 - red led forever
16373000 - red led forever

Now I got newest Qi from SHR-U and tried these settings which also gave me 
nothing but a red LED :(

I already read in some of the older ML threads, but I am getting really 
frustrated here.

Christian

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: Sandisk 16GB SDHC not mountable

2010-10-03 Thread Christian Rüb
forgot one line im my last mail...


  [  244.995000] mmcblk0: error -110 sending read/write command, response 
  0x0, card status 0x400b00
  [  244.995000] end_request: I/O error, dev mmcblk0, sector 170
  [  245.01] glamo-mci glamo-mci.0: Error after cmd: 0x8120
 
 You can try to add something like glamo_mci.sd_max_clk=1500 to you
 kernel options. Try different values until your card will start working.

Tried these and also showing results:
1500 - partition skipped (led + vib)
500 - red led forever
16373000 - red led forever

Now I got newest Qi from SHR-U and tried these settings which also gave me 
nothing but a red LED :(

glamo_mci.sd_max_clk=500 rootwait loglevel=8

I already read in some of the older ML threads, but I am getting really 
frustrated here.

Christian

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: qtmoko v27

2010-10-03 Thread Ole Carlsen
Den 03-10-2010 14:08, Gand' skrev:
 Since i moved to the v27, my touchscreen is kind of weird ... I can't
 draw a straight line, and when i keep the stylus on the screen, it draws
 a tiny star (more or less 9mm²) It makes the docked keyboard pretty
 unusable as when press a key, one of the surrounding key often responds ...
 --
Gand'

That was also one of the things that Radek mentioned when releasing it:

--
I have been testing 2.6.34 kernel for one week now and to me it looks ok.
There can be issues with SD card [6], the touchscreen driver is missing
filtering so it's a bit jittery and i think accelerometers are somehow 
strange now.
--

As a work-around, for the keyboard, I have rotated my screen 90 degrees 
and now I don't hit the wrong key very often anymore. I would though 
prefer the possibility to personally decide the size of my keyboard.

-- 
Ole @ Carlsen-web.dk

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: Sandisk 16GB SDHC not mountable

2010-10-03 Thread Christian Rüb
Alfa21:
 2010-10...@11:16 Christian Rüb
 
   cat plaintextfile.txt  /dev/mmcblk0p1
   less -f /dev/mmcblk0p1
  
  I could not read it back, but using /dev/mmcblk0 it showed up somewhere 
  near the beginning (it was cat to /dev/mmcblk0p1 though)
 
 mmh... maybe less is not installed by default, sorry :P
 ok, near the beginning maybe after the 512 stuff of mbr and the partition 
 table if p1 is at the beginning of your device, it's ok and regular thing.
 (you'd imagine your device as a long tape with one thing after each other)

less is installed ;-) I just could not read back what I wrote in. I.e. i catted 
/etc/hosts but got back only garbage. But as i catted it into the device (not 
the partition) I could read the contents back from somewhere near (but not at!) 
the beginning.
So this differs from my PC results

 
 strange you are not able to read the p1 but only the whole device
 
  
   you should be able to read your contents of the original input file.
   if you fail to less it on the FR, try the second command on your PC.
  
  showed up at partition start
 
 right
 
  I saw the contents only once and about at the same place when catting it to 
  /dev/mmcblk0p1 (Freerunner)
  Once at the beginning and once about where 1 partitions starts (PC).
 
 right, once at the beginning of the whole device and one where was the 
 beginning of the old p1
 (data remains there until overwritten with new data, usually it's never 
 cleared)
 
  same result :( (Freerunner)
  On my PC FAT32 and ext3 work ...
 
 also with fat32 directly on whole device? (no partition table)
 
  Note that I booted using Qi and system is on NAND (kernel 2.6.29)
 
 sorry but I do not know if 2-4-2 or default change anything, I use qi too but 
 the plain one and with 8GB uSD.
 
  Now even fdisk does not find the card anymore. As from the wiki I thought 
  the card would work :(
 
 me too.. I was about to buying a 16GB one! :P
 btw, maybe you should clear your uSD...
 
 dd if=/dev/zero of=/dev/mmcblk0 bs=512 count=2048

cleared

 WARNING: THIS COMMAND IS REALLY DESTRUCTIVE!!!
 (this will totally blank the first 1MB on your device, so mbr, partitions, 
 some data Co.)
 double check the of= value before return!!!
 
 try to build all your tables on a real PC instead of FR

Trying a fs on the whole device did not help either.

It seems like writing onto the card works (partitioning, creating fs) but 
reading does not (fsck, mount).

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: Sandisk 16GB SDHC not mountable

2010-10-03 Thread Gennady Kupava
В Вск, 03/10/2010 в 14:38 +0200, Christian Rüb пишет:

   [  244.995000] mmcblk0: error -110 sending read/write command, response 
   0x0, card status 0x400b00
   [  244.995000] end_request: I/O error, dev mmcblk0, sector 170
   [  245.01] glamo-mci glamo-mci.0: Error after cmd: 0x8120
  
  You can try to add something like glamo_mci.sd_max_clk=1500 to you
  kernel options. Try different values until your card will start working.
 
 Tried these and also showing results:
 1500 - partition skipped (led + vib)
 500 - red led forever
 16373000 - red led forever

Strange. Are you booting from usd or NAND? if from nand how can it
hang? 

Would be interesting to see kernel logs. 


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: Help from Always Innovating ?

2010-10-03 Thread Joshua Judson Rosen
Alfa21 freerun...@my.is.it writes:
 2010-09...@00:16 Chuck Norris
 
  I've asked them about missing this feature.
  Here are answer:
  
  We do not have a 3G or GSM option because we do not want to force a
  subscription on customers.  Instead we want to focus on using wifi and
  free Skype calls.
 
 force subscription?!
 LOL... maybe they do not know what actually the word option means?
 fool or fail? ;)

Well, `not wanting to force subscriptions' is actually the right answer
if it would have been an `either/or' choice.

More probably, it's because it's just not viable to include it in a
device that size at that price-range--there have been in-depths
discussions about this as it pertained to the FreeRunner, previously;
they're probably still applicable.

As far as the full-sized tablet goes, you could look into getting a
UMTS/HSDPA/whatever USB stick to connect to one of those internal USB ports.
I've seen ones that may be small enough for as low as $50 US, though
it's not obvious how well they'd work from inside the tablet.

-- 
Don't be afraid to ask (λf.((λx.xx) (λr.f(rr.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: Help from Always Innovating ?

2010-10-03 Thread Timo Juhani Lindfors
Joshua Judson Rosen roz...@geekspace.com writes:
 it's not obvious how well they'd work from inside the tablet.

Just add an external antenna?


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: Help from Always Innovating ?

2010-10-03 Thread Maksim 'max_posedon' Melnikau
On 10/3/10, Joshua Judson Rosen roz...@geekspace.com wrote:
 As far as the full-sized tablet goes, you could look into getting a
 UMTS/HSDPA/whatever USB stick to connect to one of those internal USB ports.
 I've seen ones that may be small enough for as low as $50 US, though
 it's not obvious how well they'd work from inside the tablet.
Do you know such sticks which can provide *voice* communication?
E.g. most of such usb dongles only provides data(internet), sometimes
SMS but not voice/calls.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: Help from Always Innovating ?

2010-10-03 Thread Timo Juhani Lindfors
Maksim 'max_posedon' Melnikau maxpose...@gmail.com writes:
 Do you know such sticks which can provide *voice* communication?

Huawei E169 at least does with asterisk.




___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: Sandisk 16GB SDHC not mountable

2010-10-03 Thread jeremy jozwik
On Sun, Oct 3, 2010 at 5:11 AM, Gennady Kupava g...@bsdmn.com wrote:
 Strange. Are you booting from usd or NAND? if from nand how can it
 hang?

 Would be interesting to see kernel logs.

and so begins the might fall of the freerunner sd card reader...

life i bitter without one...

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: Sandisk 16GB SDHC not mountable

2010-10-03 Thread Gennady Kupava
Hi, Jeremy,

В Вск, 03/10/2010 в 08:18 -0700, jeremy jozwik пишет:
 On Sun, Oct 3, 2010 at 5:11 AM, Gennady Kupava g...@bsdmn.com wrote:
  Strange. Are you booting from usd or NAND? if from nand how can it
  hang?
 
  Would be interesting to see kernel logs.
 
 and so begins the might fall of the freerunner sd card reader...

I think possible something just terrible wrong in kernel driver. From my
point of view it is worth to investigate, may be we can get x4 uSD
speedup.

 life i bitter without one...

Every thing has it's proper usage. FR is for learn, hack and
experiments. Life depends on how you look to it ;)

Gennady




___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: Sandisk 16GB SDHC not mountable

2010-10-03 Thread Jan Vlug
 I have problems with my uSD as well since 2.6.32
See this ticket:  http://docs.openmoko.org/trac/ticket/2364
I had no time to test the suggestion in this ticket yet.

Best regards,
Jan.

On 10/02/2010 08:04 PM, Christian Rüb wrote:
 Hi,

 I partitioned my 16GB SDHC (class 2) card, so I had a 512MB ext3 primary 
 partition as /dev/mmcblk0p1, but Qi would not boot from it.
 So I booted my NAND system (older SHR-U, 1.6.29 kernel) which shows me 
 correct partition with fdisk -l but would not mount it.

 I recreated the filesystem with mkfs.ext3 on freerunner but it still would 
 not mount it. fsck could not even check the fs:
 e2fsck -f -C0 /dev/mmcblk0p1 
 e2fsck 1.41.9 (22-Aug-2009)
 e2fsck: Superblock invalid, trying backup blocks...
 e2fsck: Bad magic number in super-block while trying to open /dev/mmcblk0p1

 The superblock could not be read or does not describe a correct ext2
 filesystem.  If the device is valid and it really contains an ext2
 filesystem (and not swap or ufs or something else), then the superblock
 is corrupt, and you might try running e2fsck with an alternate superblock:
 e2fsck -b 8193 device

 Trying the fsck suggestion to use an alternate superblock did not help either.

 I then created a partition and filesystem over the whole disk, but same 
 result. No chance to even check the filesystem.

 I also tried to switch back from Qi with glamo 242 to the old one - still no 
 success.

 In my 2 card readers the card does work though.

 Does anyone of you have any ideas?

 Thanks,
  Christian

 ___
 Openmoko community mailing list
 community@lists.openmoko.org
 http://lists.openmoko.org/mailman/listinfo/community

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: Help from Always Innovating ?

2010-10-03 Thread Chuck Norris
 03.10.2010 21:05, Joshua Judson Rosen пишет:
 Alfa21 freerun...@my.is.it writes:
 2010-09...@00:16 Chuck Norris
 I've asked them about missing this feature.
 Here are answer:

 We do not have a 3G or GSM option because we do not want to force a
 subscription on customers.  Instead we want to focus on using wifi and
 free Skype calls.
 force subscription?!
 LOL... maybe they do not know what actually the word option means?
 fool or fail? ;)
 Well, `not wanting to force subscriptions' is actually the right answer
 if it would have been an `either/or' choice.

 More probably, it's because it's just not viable to include it in a
 device that size at that price-range--there have been in-depths
 discussions about this as it pertained to the FreeRunner, previously;
 they're probably still applicable.

 As far as the full-sized tablet goes, you could look into getting a
 UMTS/HSDPA/whatever USB stick to connect to one of those internal USB ports.
 I've seen ones that may be small enough for as low as $50 US, though
 it's not obvious how well they'd work from inside the tablet.

last answer from Always Innovating to me was:

Thank you for your feedback.  We are aware that many customers wish to
have a GSM option available, and we do our best to satisfy as many
customers as possible.  Unfortunately, we currently do not have any
plans to release a version of the Mini Book with GSM capabilities.  If
that possibility opens up to us in the future, we will be sure to make
note of it on our website.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community