microSD card only detected at boot (CELES, other Braswell models maybe)

[ramseyrt]

Hello,

I just installed and updated a bare metal install of Gallium on my Samsung Chromebook 3. I'm unable to see my MicroSD card (working card pulled from my Raspberry Pi) using fdisk -l.

To perform the bare metal install of Gallium, I updated my firmware using MrChromebox's RW_Legacy and full ROM firmware. I installed Gallium using the Gallium ISO written to my USB flash drive using Rufus. The Gallium installation went well and post-install OS updates installed without an issue.

uname -a Linux chromebook 4.16.13-galliumos #1 SMP PREEMPT Tue Jun 19 04:21:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 2 On-line CPU(s) list: 0,1 Thread(s) per core: 1 Core(s) per socket: 2 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 76 Model name: Intel(R) Celeron(R) CPU N3060 @ 1.60GHz Stepping: 4 CPU MHz: 1166.432 CPU max MHz: 2480.0000 CPU min MHz: 480.0000 BogoMIPS: 3200.00 Virtualization: VT-x L1d cache: 24K L1i cache: 32K L2 cache: 1024K NUMA node0 CPU(s): 0,1 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch epb pti ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat

lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 2232:1073 Silicon Motion Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

lspci 00:00.0 Host bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SoC Transaction Register (rev 35) 00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 35) 00:0b.0 Signal processing controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller (rev 35) 00:10.0 SD Host controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series MMC Controller (rev 35) 00:12.0 SD Host controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SD Controller (rev 35) 00:14.0 USB controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series USB xHCI Controller (rev 35) 00:1b.0 Audio device: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller (rev 35) 00:1c.0 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Express Port #1 (rev 35) 00:1c.2 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Express Port #3 (rev 35) 00:1f.0 ISA bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCU (rev 35) 02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)

lsmod Module Size Used by rfcomm 81920 16 hid_logitech_hidpp 36864 0 hid_logitech_dj 24576 0 hid_generic 16384 0 usbhid 57344 0 hid 135168 4 hid_generic,usbhid,hid_logitech_dj,hid_logitech_hidpp ccm 20480 6 cmac 16384 1 bnep 24576 2 lz4 16384 2 lz4_compress 32768 1 lz4 zram 28672 1 intel_rapl 24576 0 intel_powerclamp 16384 0 coretemp 16384 0 kvm_intel 184320 0 nls_iso8859_1 16384 1 kvm 700416 1 kvm_intel arc4 16384 2 irqbypass 16384 1 kvm crct10dif_pclmul 16384 0 crc32_pclmul 16384 0 ghash_clmulni_intel 16384 0 pcbc 16384 0 snd_soc_sst_cht_bsw_rt5645 20480 2 iwlmvm 421888 0 joydev 24576 0 mac80211 921600 1 iwlmvm aesni_intel 188416 6 aes_x86_64 20480 1 aesni_intel crypto_simd 16384 1 aesni_intel snd_hda_codec_hdmi 61440 1 glue_helper 16384 1 aesni_intel cryptd 28672 3 crypto_simd,ghash_clmulni_intel,aesni_intel iwlwifi 319488 1 iwlmvm snd_hda_intel 49152 1 snd_soc_rt5645 147456 2 snd_soc_sst_cht_bsw_rt5645 snd_intel_sst_acpi 16384 1 snd_intel_sst_core 65536 1 snd_intel_sst_acpi snd_soc_sst_atom_hifi2_platform 110592 3 snd_intel_sst_core uvcvideo 106496 0 snd_hda_codec 147456 2 snd_hda_intel,snd_hda_codec_hdmi snd_soc_rt5640 118784 0 btusb 53248 0 snd_soc_acpi 16384 2 snd_soc_sst_cht_bsw_rt5645,snd_intel_sst_acpi snd_soc_rl6231 16384 2 snd_soc_rt5640,snd_soc_rt5645 snd_soc_acpi_intel_match 20480 1 snd_intel_sst_acpi btrtl 16384 1 btusb btbcm 16384 1 btusb videobuf2_vmalloc 16384 1 uvcvideo snd_hwdep 16384 1 snd_hda_codec videobuf2_memops 16384 1 videobuf2_vmalloc snd_seq_midi 16384 0 snd_soc_core 270336 4 snd_soc_rt5640,snd_soc_sst_cht_bsw_rt5645,snd_soc_sst_atom_hifi2_platform,snd_soc_rt5645 btintel 20480 1 btusb videobuf2_v4l2 28672 1 uvcvideo snd_hda_core 90112 3 snd_hda_intel,snd_hda_codec,snd_hda_codec_hdmi snd_seq_midi_event 16384 1 snd_seq_midi cfg80211 729088 3 iwlmvm,iwlwifi,mac80211 videobuf2_common 49152 2 uvcvideo,videobuf2_v4l2 snd_pcm_oss 61440 0 snd_rawmidi 40960 1 snd_seq_midi snd_compress 24576 1 snd_soc_core snd_mixer_oss 28672 1 snd_pcm_oss snd_pcm_dmaengine 16384 1 snd_soc_core bluetooth 622592 43 btrtl,btintel,bnep,btbcm,rfcomm,btusb videodev 204800 3 uvcvideo,videobuf2_common,videobuf2_v4l2 media 45056 2 uvcvideo,videodev snd_pcm 135168 11 snd_pcm_oss,snd_hda_intel,snd_hda_codec,snd_pcm_dmaengine,snd_hda_core,snd_soc_rt5640,snd_soc_sst_cht_bsw_rt5645,snd_soc_sst_atom_hifi2_platform,snd_hda_codec_hdmi,snd_soc_rt5645,snd_soc_core snd_seq 81920 2 snd_seq_midi_event,snd_seq_midi ecdh_generic 24576 2 bluetooth snd_seq_device 16384 3 snd_seq,snd_rawmidi,snd_seq_midi lpc_ich 28672 0 snd_timer 36864 2 snd_seq,snd_pcm shpchp 40960 0 processor_thermal_device 16384 0 intel_soc_dts_iosf 16384 1 processor_thermal_device cros_ec_core 16384 0 mfd_core 16384 2 lpc_ich,cros_ec_core snd 98304 20 snd_compress,snd_pcm_oss,snd_hda_intel,snd_hwdep,snd_mixer_oss,snd_seq,snd_hda_codec,snd_timer,snd_soc_sst_atom_hifi2_platform,snd_rawmidi,snd_hda_codec_hdmi,snd_seq_device,snd_soc_core,snd_pcm atmel_mxt_ts 36864 0 soundcore 16384 1 snd int3403_thermal 16384 0 8250_dw 16384 0 int340x_thermal_zone 16384 2 int3403_thermal,processor_thermal_device int3400_thermal 16384 0 acpi_thermal_rel 16384 1 int3400_thermal mac_hid 16384 0 sch_fq_codel 20480 5 ip_tables 28672 0 x_tables 40960 1 ip_tables autofs4 49152 2 btrfs 1310720 0 xor 24576 1 btrfs zstd_decompress 94208 1 btrfs zstd_compress 184320 1 btrfs xxhash 16384 2 zstd_compress,zstd_decompress raid6_pq 122880 1 btrfs dm_mirror 28672 0 dm_region_hash 16384 1 dm_mirror dm_log 16384 2 dm_mirror,dm_region_hash i915 1634304 17 mmc_block 45056 3 i2c_algo_bit 16384 1 i915 drm_kms_helper 188416 1 i915 syscopyarea 16384 1 drm_kms_helper sysfillrect 16384 1 drm_kms_helper sysimgblt 16384 1 drm_kms_helper fb_sys_fops 16384 1 drm_kms_helper drm 446464 8 i915,drm_kms_helper sdhci_pci 36864 0 cqhci 28672 1 sdhci_pci sdhci 53248 1 sdhci_pci drm_panel_orientation_quirks 16384 1 drm video 45056 1 i915

[16amattice]

Try following :

Type:

dmesg | tail -20 command to check the last few lines. Now insert the drive. Again type

dmesg | tail -20 if system is able to get the drives serial number and assigns device name like /dev/sdx means the device is detected.

Then try to mount it with various mount types if not sure of the partition type.

mount -t /dev/sdx /path/to/any/empty/folder You can also skip the -t part, the mount will try to guess it.

This is better than lsblk way...:

Execute lsblk before connecting the SD card, then once connected execute lsblk again. If there is new entry, then you can see the device name with the mount point (if mounted), like /media/user1/BX5GB in following snippet.

└─sdb1 8:5 0 4G 0 part [/media/user1/BX5GB] If there isn't any mount point there you have to mount the drive to any local folder with mount command mentioned earlier.

If the partition details are corrupted e.g. Corrupted MBR.. You can try recovery with some softwares like testdisk or something.

For testdisk -

execute the testdisk with superuser privileges (this is necessary as we're going to write the partitioning info) sudo apt-get install testdisk sudo testdisk Now, choose choose logging (create is default). Next screen will show you the disks attached to your system and their total size

Here select the correct disk that needs to be fixed (your memory card say /dev/sdx).

On next screen there are options for partition type like [Intel/PC | EFI GPT | Humax | Apple |....]. You can choose one that s suitable for your card. for MBR partitioning it's Intel/PC.

Now select Analyse. This will take you to analyze screen You will first have an option of [Quick Search] select it and let the application search the partitions If you are satisfied with the current search press Enter to continue (though you may choose to change the partition type detected). Now you have two options: [write] or [Deeper Search]. So at this point, if you are satisfied with the current partition info select [Write] which writes the partition info to disk and you can now remove and attach it again to see content. OR You can click [Deeper Search] for more analyzing more damaged partitions and write the detected partition scheme on the disk and you are able to see the content now. This was again in case of reading the SD card. If you just want to recover the content... you have an option of using the photo-recovery, which comes with the testdisk package. and recover the media to some other partition as target. You'll get most of your files, but there won't be any directory structure that you were using earlier.

[ramseyrt]

Hello 16amattice,

Thanks for the response! I did as you asked and performed the "dmesg | tail -20", installed my MicroSD card, and then performed "dmesg | tail -20" again. The output of the command didn't change after installing the MicroSD card. I took the same MicroSD card and installed it in an IOGear USB media reader which I then inserted into my Chromebook's USB port. Here's the updated output from the "dmesg -l" command:

[ 460.210666] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd [ 460.239496] usb 2-1: New USB device found, idVendor=0bda, idProduct=0316 [ 460.239514] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 460.239528] usb 2-1: Product: USB3.0-CRW [ 460.239537] usb 2-1: Manufacturer: Generic [ 460.239547] usb 2-1: SerialNumber: 20120501030900000 [ 460.302812] usb-storage 2-1:1.0: USB Mass Storage device detected [ 460.305623] scsi host0: usb-storage 2-1:1.0 [ 460.305857] usbcore: registered new interface driver usb-storage [ 460.311349] usbcore: registered new interface driver uas [ 461.346536] scsi 0:0:0:0: Direct-Access Generic- SD/MMC 1.00 PQ: 0 ANSI: 6 [ 461.349716] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 462.299618] sd 0:0:0:0: [sda] 31116288 512-byte logical blocks: (15.9 GB/14.8 GiB) [ 462.300201] sd 0:0:0:0: [sda] Write Protect is off [ 462.300219] sd 0:0:0:0: [sda] Mode Sense: 2f 00 00 00 [ 462.300478] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 462.303696] sda: sda1 sda2 [ 462.306161] sd 0:0:0:0: [sda] Attached SCSI removable disk

Next, I ran "fdisk -l" to see if the partitions showed up properly:

Disk /dev/sda: 14.9 GiB, 15931539456 bytes, 31116288 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xbd98648d

Device Boot Start End Sectors Size Id Type /dev/sda1 8192 96663 88472 43.2M c W95 FAT32 (LBA) /dev/sda2 98304 9420799 9322496 4.5G 83 Linux

I then opened GParted and re-partitioned the MicroSD card for a single NTFS partition, which I used to copy the code snippits above to my Windows PC.

When I took the newly formatted MicroSD card and inserted it into the MicroSD slot, I did not see any change to the "dmesg" output. Based on the activities and output above, the MicroSD card is in great shape. I know that the port is physically Ok as it works in the native ChromeOS.

Any ideas on what to do next?

Thanks!

Rob

[16amattice]

Ok so based on this I can suggest a few more things, since you said the sd card itself is perfectly working we can try some things based more on the computer side.

First I would try booting the PC with the SD card in the slot and seeing if it shows up.

If not then I would try rescanning the PCI:

sudo su -l echo 1 > /sys/bus/pci/rescan

Ok and if those don't work we have to do some more investigation work:

1) Verify that Ubuntu knows about your SD card slot and what to do with it 2) Verify that Ubuntu knows you inserted something 3) Verify that Ubuntu understands the filesystem on the thing you inserted.

1) Check the outputs of these commands: sudo lspci -v -nn sudo lsusb sudo lshw

2) Then run the following command before inserting the SD card and a few seconds after inserting it: ls -la /dev/sd* This command lists all of the hard drives, CDs, DVDs, floppies, SD cards, etc that Ubuntu knows about. (These are called Block Devices).

Ideally you will see a few entries on the second run that you don't see on the first. For example:

$ls -la /dev/sd* brw-rw---- 1 root disk 8, 0 2012-01-14 11:27 /dev/sda brw-rw---- 1 root disk 8, 16 2012-01-14 11:27 /dev/sdb brw-rw---- 1 root disk 8, 32 2012-01-14 11:27 /dev/sdc brw-rw---- 1 root disk 8, 33 2012-01-14 11:27 /dev/sdc1 brw-rw---- 1 root disk 8, 34 2012-01-14 11:27 /dev/sdc2 brw-rw---- 1 root disk 8, 35 2012-01-14 11:27 /dev/sdc3 brw-rw---- 1 root disk 8, 36 2012-01-14 11:27 /dev/sdc4 brw-rw---- 1 root disk 8, 37 2012-01-14 11:27 /dev/sdc5

(Now insert the SD card)

$ls -la /dev/sd* brw-rw---- 1 root disk 8, 0 2012-01-14 11:27 /dev/sda brw-rw---- 1 root disk 8, 16 2012-01-14 11:27 /dev/sdb brw-rw---- 1 root disk 8, 32 2012-01-14 11:27 /dev/sdc brw-rw---- 1 root disk 8, 33 2012-01-14 11:27 /dev/sdc1 brw-rw---- 1 root disk 8, 34 2012-01-14 11:27 /dev/sdc2 brw-rw---- 1 root disk 8, 35 2012-01-14 11:27 /dev/sdc3 brw-rw---- 1 root disk 8, 36 2012-01-14 11:27 /dev/sdc4 brw-rw---- 1 root disk 8, 37 2012-01-14 11:27 /dev/sdc5 brw-rw---- 1 root disk 8, 64 2012-01-14 11:28 /dev/sdd See that extra one at the end /dev/sdd that is the SD card.

3) Check that Ubuntu understands the filesystem on the drive. I would bet it is either Fat32 or NTFS. You can check if your copy of Ubuntu understands those filesystems (it should) by running this command: cat /proc/filesystems

In this list vfat is Fat32 and (for all intents and purposes) fuse is NTFS. **Note: this list is not extensive.

A better way is to simply try to mount the SD card manually. Run the following commands in order until one works (replace the X in /dev/sdX1 with the letter from step 2):

sudo mount /dev/sdX1 /mnt sudo mount -t vfat /dev/sdX1 /mnt sudo mount -t ntfs /dev/sdX1 /mnt sudo mount -t msdos /dev/sdX1 /mnt No output means it worked, and you should be able to navigate to your SD card with nautilus at /mnt. If none of them worked, try plugging your SD card into a windows machine and running chkdsk on it, or verify the filesystem type.

Get back to me with some of these results :)

[ramseyrt]

Hello 16amattice,

Thanks again for the support! So, when I boot the Chromebook with the MicroSD card installed, the MrChromebox boot firmware sees the drive. Gallium also sees the drive, as shown below. I can mount the drive and reliably read and write files to it. However, when I unmount and physically eject the drive, it does not show as being removed from the system (umount works but it still shows up in fdisk and lsblk).

When I boot the system without the MicroSD card installed, then insert the card and perform the "echo 1 > /sys/bus/pci/rescan" command, it does not show up.

So, the card is detected when it's installed during boot but the system doesn't seem to be able to interact with it once booted.

lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 1 119M 0 disk └─sda1 8:1 1 117M 0 part mmcblk0 179:0 0 14.7G 0 disk ├─mmcblk0p1 179:1 0 512M 0 part /boot/efi └─mmcblk0p2 179:2 0 14.2G 0 part / mmcblk0boot0 179:8 0 4M 1 disk mmcblk0boot1 179:16 0 4M 1 disk mmcblk1 179:24 0 14.9G 0 disk └─mmcblk1p1 179:25 0 14.9G 0 part zram0 252:0 0 5.7G 0 disk [SWAP]

fdisk -l Disk /dev/mmcblk1: 14.9 GiB, 15931539456 bytes, 31116288 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x023d4022

Device Boot Start End Sectors Size Id Type /dev/mmcblk1p1 2048 31115263 31113216 14.9G 7 HPFS/NTFS/exFAT

Thanks again for your help!

Rob

[16amattice]

I haven't encountered this error before so I will try to give the best advice I can. I do not believe this is as much a GalliumOS error as it is a hardware error but lets look into some more solutions.

So if the partitions were not created in linux maybe its an exFAT file system. I would see:

sudo dd if=/dev/mmcblk0p1 bs=16 count=1 | hd

and if the first few bytes are 'EXFAT', then install the fuse-based exfat.

sudo apt-get install exfat-fuse exfat-utils

And then mount manually if the GUI won't automatically recognize it.

If that doesn't work try this:

Remove any SD card. Launch the Terminal.

sudo apt-get install --reinstall udisks2

Afterwards close the terminal and restart the pc.

I will keep researching into this, but this is one weird issue I have not seen before.

[ramseyrt]

Hello 16amattice,

Your continued interest in helping is appreciated!

Let me clarify the current MicroSD behavior:

• When I boot the system with the MicroSD card installed, I can see it with "fdisk -l" and lsblk (Both of these provide information on raw devices regardless of the filesystem that might be on them)

• When the OS sees the device, it can be mounted as a FAT32, NTFS, or ext4 filesystem (basically any filesystem I've formatted the drive with that the OS supports, the OS sees properly)

• When I unmount and then eject the MicroSD card, the OS still shows it as available in "fdisk -l" and lsblk (The OS should stop seeing the device when it's physically removed)

• When I boot the system without the MicroSD card installed, I'm unable to get the OS to recognized the card when it's installed (The OS should see the device after it has been physically connected)

So, I don't think I have a filesystem problem. I think I have a hardware detection problem. What's different about the way hardware is detected during boot than the way hardware is detected post boot?

I did install udisks2 and performed a multitude of tests but the behavior described above still exists.

Thanks!

Rob

[16amattice]

Sorry for the late reply the christmas week has kept me very busy. If it is not a problem with the software then it is sadly getting out of my expertise area. You can continue to ask your questions and I can refer you but if it is not about galliumos itself then sadly I am not the right person to ask.

http://flint.cs.yale.edu/feng/cos/resources/BIOS/ This is a good source of many about what happens during BIOS and how your SD card would be detected after boot.

Thanks, Anthony

[ramseyrt]

Hello Anthony,

I've been busy with Christmas and New Years travel also so I haven't been able to work this issue either.

Based on all the trouble-shooting we've done, I believe the running OS/processes are not detecting the Micro SD card's presence properly. I'm not sure if there's a process that regularly scans the USB bus or if there's an electronic switch built into the Micro SD card's slot that triggers an interrupt which adds or removes the MicroSD card from the OS.

If the Micro SD card is installed during boot, the system does sees, and properly handles, the Micro SD card. However, it doesn't detect the removal of the Micro SD card.

So, how does the system scan for hardware changes during boot that is different than the way the system scans for hardware after boot?

On a RedHat system, the anaconda process detects hardware changes during boot. After boot, the hotplug process detects new USB devices. So if I were having this problme on a RedHat system, I'd think hotplug was broken.

Does that make sense?

Thanks agin!

Rob

[16amattice]

The bios page shows hardware scanning at boot but to show how hardware is hqndled once the pc is booted i would take a look here. https://www.technovelty.org/linux/what-actually-happens-when-you-plug-in-a-usb-device.html

[16amattice]

Was there any development on this?

[ramseyrt]

Hello Anthony,

I must have missed your last post. I'm looking it over now.

Thanks,

Rob

[ghost]

I've confirmed this issue; I'll look for the kernel driver and see if we can't get that bad boy included in the next release.

[ramseyrt]

Let me know if there's anything I can do. I'd be happy to test as needed.

[ghost]

There is no missing driver. The slot only gets initialized at boot and it's state (maybe?) never gets updated after that. If you insert a card before boot, that card shows up and works fine. When you remove it, it does not disappear, and when you insert another card, the computer still sees the first one (but is unable to read it, obviously). The issue might affect other Braswell models as well. IRC user mouses told me it is borked on BANON too, but only sometimes.

I also swear mine was working correctly the other day under Manjaro but seeing how I was hotplugging the same card and was careful to unmount it every time I removed it, I could have just dodged the issue in that case. Trying again today under Manjaro presented the same issue.

[Cronocide]

I'm having the same issue on Braswell as well, though it seems to go in and out fine on the live installer image. I'll play with it over the next few days to see if I can reproduce the mounting issue you described.

[Strike-F8]

I'm having a similar issue with my Samsung Chromebook 3. It doesn't detect any SD cards. Not even at boot or in SeaBIOS. I used John Lewis' RW_LEGACY script as Mr. Chromebox's script wouldn't work for me. So maybe it's a firmware issue. Has anyone been able to figure it out? Mr. Chromebox's script is working now that I have Gallium installed so I will try updating my firmware.

[MrChromebox]

I used John Lewis' RW_LEGACY script as Mr. Chromebox's script wouldn't work for me.

huh?

[Strike-F8]

I pasted your ChromeOS Firmware Utility Script in the crosh terminal but I got a permission error. I don't remember the exact wording and I don't have ChromeOS installed anymore. So I tried John Lewis' script and it did work. That was about a month ago. Last night, I updated my firmware with your script using the RW_Legacy method since I haven't had time to back up for the full rom installation. I plan to do that next.

[Amitav64]

I have the same problem on a Intel N3050 running Gallium. However, this probelm does not show up when I run ubuntu or peppermint linux on the same laptop. Perhaps it has to do with the optimizations done on Gallium (eg no watchdog, though I don't know what it means)

[randomodbuild]

Having the same issue here as well, I am on the full UEFI firmware CELES.

[Crsarmv7l]

This is an issue on all distros (tested on gallium, manjaro, and ubuntu). Which is such a shame because literally everything else works fine, and actually Gnome + any distro works fantastically once you get the keyboard working well (If debian based you can just grab the gallium xkb-data). I wonder how google got around the only initialized at boot in order to support hotplug?