public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: green <greenfreedom10@gmail.com>
To: Linux-OMAP List <linux-omap@vger.kernel.org>
Subject: Re: N810: external mmc died?
Date: Wed, 29 Jul 2009 13:12:31 -0600	[thread overview]
Message-ID: <20090729191231.GO7597@swansys> (raw)
In-Reply-To: <20090729182948.GN7597@swansys>

[-- Attachment #1: Type: text/plain, Size: 2080 bytes --]

I'll try again, the message was botched up somehow with ^M everywhere...


I was working on moving Debian's root from internal mmc (because it still 
doesn't work with linux-omap) to external mmc, running standard Maemo and 
connected by USB to the MMC cards (with the cards mounted), when suddenly the 
N810 reset.  I have no idea why, but now external MMC does not work.

I have been using this card for a while and have not had any problems with it; 
it surely can also be considered still nearly 'new'.

I reflashed Maemo with the latest RX-44_DIABLO_5.2008.43-7_PR_COMBINED_MR0_ARM 
(and checked md5sum) and now I get the following from dmesg with either an open 
or close of the external MMC slot.

[ 2292.843750] menelaus 1-0072: Setting voltage 'VMMC' to 3100 mV (reg 0x0a, val 0xf8)
[ 2292.953125] menelaus 1-0072: Setting voltage 'VMMC' to 3000 mV (reg 0x0a, val 0xb8)
[ 2295.320312] menelaus 1-0072: Shutting off 'VMMC'

No device ever shows up in /dev, only mmcblk0 (the internal MMC).  When I 
connect by USB to the MMC cards, I see in the logs on my Debian system:

kernel: scsi 43:0:0:0: Direct-Access     Nokia    N810              031 PQ: 0 ANSI: 2
kernel: scsi 43:0:0:1: Direct-Access     Nokia    N810              031 PQ: 0 ANSI: 2
kernel: sd 43:0:0:0: [sdb] 3932160 512-byte hardware sectors: (2.01 GB/1.87 GiB)
kernel: sd 43:0:0:0: [sdb] Write Protect is off
kernel: sd 43:0:0:0: [sdb] Mode Sense: 0f 00 00 00
kernel: sd 43:0:0:0: [sdb] Assuming drive cache: write through
kernel: sd 43:0:0:0: [sdb] 3932160 512-byte hardware sectors: (2.01 GB/1.87 GiB)
kernel: sd 43:0:0:0: [sdb] Write Protect is off
kernel: sd 43:0:0:0: [sdb] Mode Sense: 0f 00 00 00
kernel: sd 43:0:0:0: [sdb] Assuming drive cache: write through
kernel: sdb: sdb1
kernel: sd 43:0:0:0: [sdb] Attached SCSI removable disk
kernel: sd 43:0:0:0: Attached scsi generic sg1 type 0
kernel: sd 43:0:0:1: [sdc] Attached SCSI removable disk
kernel: sd 43:0:0:1: Attached scsi generic sg2 type 0

No information about the external MMC.

Thanks for any hints.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-07-29 19:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-29 18:29 N810: external mmc died? green
2009-07-29 19:12 ` green [this message]
2009-07-29 20:29   ` green
2009-08-11 16:57     ` green

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090729191231.GO7597@swansys \
    --to=greenfreedom10@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox