On Sat 22 Apr 2017 at 11:56:27 -0500, Richard Owlett wrote:
On 04/22/2017 06:47 AM, Brian wrote:
On Wed 19 Apr 2017 at 15:16:52 -0500, Richard Owlett wrote:
On 04/19/2017 02:31 PM, Brian wrote:
As I have detailed elsewhere,
https://lists.debian.org/debian-user/2017/04/msg00578.html
the card becomes visible to GRUB with its nativedisk command. The OP has
a reader which does not show an SD disk in GRUB and does not boot from
it. Perhaps he could take some time to see whether this command does
anything for him.
I just received my USB SD card reader this afternoon. Attempting to
reproduce the results of your ...msg00578 is on my TODO list. I'll not have
time for Debian until Monday. I did have the opportunity to do a quickie
Thanks for considering testing. However, it is likely not to work for
you because your 5-in-1 appparently is a Ricoh reader on the PCI bus.
You can check this with 'lspci'. Failure is also indicated by the
presence of 'root=/dev/mmcblk0p1' in your grub.cfg. AFAICT, GRUB does
not have modules for SD/MMC devices, so nativedisk would have nothing
to load to drive the device.
Monday came early - IOW the project I was working on collapsed and I needed
a break.
I attempted to run the tests you described in Paragraph 4 of
.../msg00578.html.
My notes are:
with no usb devices present, I get
(ahci) (ahci0,msdosXX) (ahci1)
where XX maches the partions on my "hard disk" {it is actually a
solid state drive which was manufactured to be a plugin replacement
for original mechanical dive (aka 'spinning rust'}.
I have no experience with SSD but am with you up to here.
I don't know what (ahci1) is.
Neither do I.
Repeating above with empty card reader I get:
(ahci) (ahci0,msdosXX) (usb0a) (usb0b) (ahci1)
I assume 'nativedisk' has been run prior to getting this output. GRUB
now sees USB devices. They can only have come from the card reader.
I repeated the above with the SD card plugged into a USB card reader
getting:
(ahci) (ahci0,msdosXX) (usb0a) (usb0a,msdos1) (usb0b) (ahci1)
When not using "nativedisk" in the second case I get:
(hd0) (hd0,msdosXX) (hd1) (hd1,msdos1)
I'd take that to be the SSD disk and whatever is in the reader. (hd1)
has a partition. In principle, it could be booted from.
I'll not attempt "Edit /etc/grub.d/40_custom to have ..."
When I spoke of "5-in-1 reader" I was using your description in
https://lists.debian.org/debian-user/2017/04/msg00505.html
IOW, I was referring to the reader which is inbuilt into the Lenovo. Are
these data for when your recently purchased USB reader has been used? If
not, there is some thinking to be done.