On Mon 24 Apr 2017 at 19:37:22 (+0100), Brian wrote: > On Sun 23 Apr 2017 at 20:46:39 +0100, Brian wrote: > > > On Wed 12 Apr 2017 at 06:18:51 -0500, Richard Owlett wrote: > > > > > Due to circumstances, will note rule out any of hardware, software, or > > > confused operator as underlying cause. > > > > > > BACKGROUND: > > > The hardware is a used Lenovo T510 laptop purchased a couple of months > > > ago. > > > > This machine has an internal card reader. > > > > > Jessie with MATE desktop has been running fine. > > > Yesterday I purchased a Kingston Technology 512GB SD, primarily for > > > backups. > > > > > > As this individual unit had never had an SD card installed, the agreement > > > with the store was if the card did not work in this machine I would not > > > have > > > to purchase it. My acceptance test was to install Jessie using a flash > > > drive > > > with DVD 1 of 13 of Debian 8.6.0. > > > > We suppose the flash drive was a USB stick. > > > > > It was my standard install which does NOT include either a swap partition > > > being activated during install NOR installing a boot loader. > > > > First (and the most important question): was the SD card inserted in a > > slot of the *machine's* internal card reader when installing Debian to > > it? > > > > > I booted into my primary OS and ran update-grub with no problems. > > > I rebooted, choosing the SD card from the Grub2 menu. No apparent problem. > > > Also verified my other Debian installs could read/write the SD card. > > > > > > These tests were performed before leaving the store. > > > > > > THE SYMPTOM: > > > > > > When I got home and booted to the SD card I noticed a message appeared for > > > ~10 seconds reporting that a device was not found giving the UUID of the > > > SD > > > card. > > > > If I had carried out the procedure you describe (something that had not > > been done before) my eyes would have been glued to the screen when the > > OS on the SD card had been booted for the first time. Yet, at the store, > > there was no "device not found" message observed. Did your attention > > wander for the 10 seconds such a message would have been on the screen? :) > > A modicum of reassurance and help is never wasted, particularly for > those users who come to this thread in the future. > > My laptop has a single slotted reader on the PCI bus.
Before booting, can you see the SD card's device in the CMOS screens? > The installer > boots and shows that mmc_core has been loaded. When it gets to the > partitioning stage the SD card is not offered as an option. The > module mmc_block is absent from 'lsmod' and does not appear when the > card is taken out and reinserted. It is not detected. If there's no driver, would you expect the kernel to react? Is there an mmc driver in that installation moduoles screen? It might be hard to spot, but is there a /proc/interrupts file, and does the number of interrupts increase on the appropriate line when you insert and remove the card? How do you find the line. On my laptop with that sort of SD card, 18: 2344 0 IO-APIC-fasteoi mmc0 the 2344 increases by 1 when I take the card out and by many when I reinsert it. I don't know if mmc_core can provide that line in the absense of mmc_block. (Obviously my kernel has both loaded now.) > What is unusual is that the card is detected by a Jessie OS on being > inserted. Is this an installer problem with different hardware (my > laptop's is described in another post) or with the card? Basically, > is an installation to an SD card on a PCI bus a case of hit or miss? > > ALT-F2 at the installer's first screen gives a console. > > lsmod | grep mmc > > indicates whether both modules are loaded and the card is detected. Cheers, David.
