Issue metadata
Sign in to add a comment
|
Acer Chromebook R13 fails to recognize SD Card after Chrome Update
Reported by
mgwright...@gmail.com,
Sep 21 2017
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS aarch64 9592.96.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.114 Safari/537.36 Platform: 9592.96.0 (Official Build) stable-channel elm Steps to reproduce the problem: 1. Insert SD Card 2. Chromebook fails to recognize cards; instructs to format card 3. Attempt to format card fails 4. SD card works fine in a Windows 10 computer What is the expected behavior? Expect to load SD Card and routinely store, access, move, manipulate files. What went wrong? After the most recent update to Chrome OS, Chromebook fails to recognize SD Card. Recent hardware diagnostics at Acer's repair center in Texas indicated that hardware is functioning properly. Did this work before? Yes The version immediately prior to Version 60.0.3112.114 (Official Build) (32-bit) Chrome version: 60.0.3112.114 Channel: stable OS Version: 9592.96.0 Flash Version: 27.0.0.130 I like this Chromebook, but my Internet research indicates that SD card recognition problems date back to at least 2014 and include other brands of Chromebooks, e.g. Samsung. It is time for a reliable fix for this problem.
,
Apr 3 2018
Hmm, so I think this cost me several hours, while I wondered why Recovery didn't work when run from an SD card...now that I've recovered via USB, I can see that for the SD card I have, at least, I see this when I plug in SD: [ 52.639868] vmc: ramp_delay not set [ 52.658415] mmc1: host does not support reading read-only switch, assuming write-enable [ 52.668720] mtk-msdc 11240000.mmc: phase: [map:ffffe7ff] [maxlen:19] [final:22] [ 52.673108] mtk-msdc 11240000.mmc: phase: [map:fff8003f] [maxlen:13] [final:25] [ 52.675134] mtk-msdc 11240000.mmc: phase: [map:fffffdff] [maxlen:22] [final:21] [ 52.676985] mtk-msdc 11240000.mmc: phase: [map:f0fe007f] [maxlen:7] [final:2] [ 52.677028] mmc1: new ultra high speed SDR104 SDHC card at address aaaa [ 52.681610] mmcblk1: mmc1:aaaa SP32G 29.7 GiB [ 52.682818] mmcblk1: error -84 sending stop command [ 52.944007] vmc: ramp_delay not set [ 52.967683] mtk-msdc 11240000.mmc: phase: [map:ffffe7ff] [maxlen:19] [final:22] [ 52.973028] mtk-msdc 11240000.mmc: phase: [map:fff8007f] [maxlen:13] [final:25] [ 52.975628] mtk-msdc 11240000.mmc: phase: [map:fffffdff] [maxlen:22] [final:21] [ 52.977575] mtk-msdc 11240000.mmc: phase: [map:f0fe00ff] [maxlen:8] [final:2] [ 52.977930] mmcblk1: error -84 sending stop command [ 52.977955] blk_update_request: I/O error, dev mmcblk1, sector 0 [ 52.977977] Buffer I/O error on dev mmcblk1, logical block 0, async page read [ 52.988880] mtk-msdc 11240000.mmc: phase: [map:ffffe7ff] [maxlen:19] [final:22] [ 52.994383] mtk-msdc 11240000.mmc: phase: [map:fff8007f] [maxlen:13] [final:25] [ 52.997171] mtk-msdc 11240000.mmc: phase: [map:fffffdff] [maxlen:22] [final:21] [ 53.000495] mtk-msdc 11240000.mmc: phase: [map:f0fe007f] [maxlen:7] [final:2] [ 53.000799] mmcblk1: error -84 sending stop command [ 53.000824] blk_update_request: I/O error, dev mmcblk1, sector 0 [ 53.000845] Buffer I/O error on dev mmcblk1, logical block 0, async page read [ 53.011942] mtk-msdc 11240000.mmc: phase: [map:ffffe7ff] [maxlen:19] [final:22] [ 53.017117] mtk-msdc 11240000.mmc: phase: [map:fff8007f] [maxlen:13] [final:25] [ 53.019744] mtk-msdc 11240000.mmc: phase: [map:fffffdff] [maxlen:22] [final:21] [ 53.022512] mtk-msdc 11240000.mmc: phase: [map:f0fe007f] [maxlen:7] [final:2] [ 53.022816] mmcblk1: error -84 sending stop command [ 53.022843] blk_update_request: I/O error, dev mmcblk1, sector 0 [ 53.022862] Buffer I/O error on dev mmcblk1, logical block 0, async page read [ 53.023008] mmcblk1: unable to read partition table [ 53.039738] mtk-msdc 11240000.mmc: phase: [map:ffffe7ff] [maxlen:19] [final:22] [ 53.045445] mtk-msdc 11240000.mmc: phase: [map:fff8007f] [maxlen:13] [final:25] [ 53.047455] mtk-msdc 11240000.mmc: phase: [map:fffffdff] [maxlen:22] [final:21] [ 53.049317] mtk-msdc 11240000.mmc: phase: [map:f0fe00ff] [maxlen:8] [final:2] [ 53.050270] mmcblk1: error -84 sending stop command [ 53.050300] blk_update_request: I/O error, dev mmcblk1, sector 62333824 [ 53.061322] mtk-msdc 11240000.mmc: phase: [map:ffffe7ff] [maxlen:19] [final:22] [ 53.067099] mtk-msdc 11240000.mmc: phase: [map:fff8007f] [maxlen:13] [final:25] [ 53.068909] mtk-msdc 11240000.mmc: phase: [map:fffffdff] [maxlen:22] [final:21] [ 53.071318] mtk-msdc 11240000.mmc: phase: [map:f8fe00ff] [maxlen:8] [final:2] [ 53.085725] mmcblk1: error -84 sending stop command [ 53.085762] blk_update_request: I/O error, dev mmcblk1, sector 62333824 [ 53.085785] Buffer I/O error on dev mmcblk1, logical block 7791728, async page read Probably worth bisecting, given the OP suggests this used to work.
,
Apr 3 2018
,
Apr 3 2018
Hmm, well my situation at least doesn't seem to be a regression; it hasn't worked as far back as M58: CHROMEOS_RELEASE_BUILDER_PATH=elm-release/R58-9334.72.0 I'm using a SanDisk Extreme PRO 32GB MicroSDHC V30. Works great (and really fast) on several other Chromebooks.
,
Jun 4 2018
Switching off and on multiple times gets the SD card working until the next off/on cycle. I'm on current dev channel but experienced this behaviour in stable for months now. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by rohi...@chromium.org
, Nov 3 2017