Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #179998 > unrolled thread
| Started by | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| First post | 2017-04-12 13:20 +0200 |
| Last post | 2017-05-04 19:20 +0200 |
| Articles | 11 on this page of 111 — 11 participants |
Back to article view | Back to linux.debian.user
Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-12 13:20 +0200
Re: Possibly erroneous "device not present" message during boot songbird <songbird@anthive.com> - 2017-04-12 14:50 +0200
Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-12 17:20 +0200
Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-12 19:20 +0200
Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-12 20:40 +0200
Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-12 21:10 +0200
Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-13 13:50 +0200
Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-13 17:50 +0200
Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-13 19:40 +0200
Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-13 20:10 +0200
Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-14 01:20 +0200
Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-14 19:10 +0200
Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-14 20:40 +0200
Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-15 18:40 +0200
Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-15 20:10 +0200
Re: Possibly erroneous "device not present" message during boot songbird <songbird@anthive.com> - 2017-04-15 20:20 +0200
Re: customized Grub (was: Possibly erroneous "device not present...) Felix Miata <mrmazda@earthlink.net> - 2017-04-15 21:00 +0200
Re: customized Grub (was: Possibly erroneous "device not present...) Brian <ad44@cityscape.co.uk> - 2017-04-15 21:20 +0200
Re: customized Grub Richard Owlett <rowlett@cloud85.net> - 2017-04-15 22:40 +0200
Re: customized Grub Curt <curty@free.fr> - 2017-04-16 11:40 +0200
Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-15 00:10 +0200
Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-17 21:10 +0200
Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-18 00:10 +0200
Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-18 00:40 +0200
Re: Possibly erroneous "device not present" message during boot Lisi Reisz <lisi.reisz@gmail.com> - 2017-04-18 00:50 +0200
Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-18 20:50 +0200
Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-18 20:50 +0200
Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-18 21:30 +0200
Re: Possibly erroneous "device not present" message during boot songbird <songbird@anthive.com> - 2017-04-15 02:20 +0200
Re: Possibly erroneous "device not present" message during boot David Wright <deblis@lionunicorn.co.uk> - 2017-04-15 02:50 +0200
Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-15 11:10 +0200
Re: Possibly erroneous "device not present" message during boot David Wright <deblis@lionunicorn.co.uk> - 2017-04-15 16:40 +0200
Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-15 19:20 +0200
Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-15 20:20 +0200
Re: Possibly erroneous "device not present" message during boot David Wright <deblis@lionunicorn.co.uk> - 2017-04-15 23:20 +0200
Re: Possibly erroneous "device not present" message during boot David Wright <deblis@lionunicorn.co.uk> - 2017-04-15 23:00 +0200
Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-16 00:00 +0200
Re: Possibly erroneous "device not present" message during boot David Wright <deblis@lionunicorn.co.uk> - 2017-04-17 03:40 +0200
Re: Possibly erroneous "device not present" message during boot Curt <curty@free.fr> - 2017-04-17 10:50 +0200
Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-17 21:10 +0200
Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-18 20:40 +0200
Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-18 21:20 +0200
Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-19 00:20 +0200
Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-19 00:30 +0200
Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-19 20:40 +0200
Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-19 21:40 +0200
Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-19 22:20 +0200
Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-22 13:50 +0200
Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-22 19:00 +0200
Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-22 20:10 +0200
Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-22 20:20 +0200
Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-22 20:40 +0200
Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-22 21:10 +0200
Re: Possibly erroneous "device not present" message during boot David Wright <deblis@lionunicorn.co.uk> - 2017-04-22 23:30 +0200
Re: Possibly erroneous "device not present" message during boot Doug <dmcgarrett@optonline.net> - 2017-04-15 21:30 +0200
Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-15 22:20 +0200
Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-15 13:10 +0200
Re: Possibly erroneous "device not present" message during boot songbird <songbird@anthive.com> - 2017-04-15 16:10 +0200
Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-15 19:30 +0200
Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-15 19:30 +0200
Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-15 19:50 +0200
Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-15 21:10 +0200
Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-15 21:40 +0200
Re: Possibly erroneous "device not present" message during boot David Wright <deblis@lionunicorn.co.uk> - 2017-04-15 03:40 +0200
Re: Possibly erroneous "device not present" message during boot GiaThnYgeia <GiaThnYgeia@openmailbox.org> - 2017-04-17 23:20 +0200
Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-18 00:30 +0200
Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-16 16:40 +0200
Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-16 17:10 +0200
Re: Possibly erroneous "device not present" message during boot David Wright <deblis@lionunicorn.co.uk> - 2017-04-13 19:40 +0200
Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-13 21:10 +0200
Re: Possibly erroneous "device not present" message during boot songbird <songbird@anthive.com> - 2017-04-12 21:30 +0200
Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-13 13:50 +0200
Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-12 21:30 +0200
Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-13 17:20 +0200
Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-13 18:30 +0200
Re: Possibly erroneous "device not present" message during boot GiaThnYgeia <GiaThnYgeia@openmailbox.org> - 2017-04-17 22:50 +0200
Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-18 21:00 +0200
Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-18 21:50 +0200
Re: Possibly erroneous "device not present" message during boot The Wanderer <wanderer@fastmail.fm> - 2017-04-19 05:50 +0200
Re: Possibly erroneous "device not present" message during boot GiaThnYgeia <GiaThnYgeia@openmailbox.org> - 2017-04-19 09:50 +0200
Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-19 20:30 +0200
Re: Possibly erroneous "device not present" message during boot David Wright <deblis@lionunicorn.co.uk> - 2017-04-22 00:20 +0200
Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-22 15:50 +0200
Re: Possibly erroneous "device not present" message during boot songbird <songbird@anthive.com> - 2017-04-12 21:00 +0200
Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-13 18:00 +0200
Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-14 20:00 +0200
Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-14 20:50 +0200
Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-14 19:50 +0200
Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-14 20:40 +0200
Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-15 12:50 +0200
Re: Possibly erroneous "device not present" message during boot songbird <songbird@anthive.com> - 2017-04-15 16:10 +0200
Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-15 19:00 +0200
Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-15 19:30 +0200
Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-15 20:10 +0200
Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-15 21:00 +0200
Re: Possibly erroneous "device not present" message during boot David Wright <deblis@lionunicorn.co.uk> - 2017-04-15 23:40 +0200
Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-16 00:30 +0200
Re: Possibly erroneous "device not present" message during boot David Wright <deblis@lionunicorn.co.uk> - 2017-04-20 04:20 +0200
Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-20 08:00 +0200
Re: Possibly erroneous "device not present" message during boot David Wright <deblis@lionunicorn.co.uk> - 2017-04-20 17:20 +0200
Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-22 15:00 +0200
Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-22 15:40 +0200
Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-22 15:50 +0200
Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-22 16:00 +0200
Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-22 16:50 +0200
Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-27 18:20 +0200
Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-23 21:50 +0200
Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-24 20:40 +0200
Re: Possibly erroneous "device not present" message during boot David Wright <deblis@lionunicorn.co.uk> - 2017-04-24 22:20 +0200
Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-25 15:10 +0200
Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-05-04 19:20 +0200
Page 6 of 6 — ← Prev page 1 2 3 4 5 [6]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-04-22 15:00 +0200 |
| Message-ID | <tz2NQ-2XA-23@gated-at.bofh.it> |
| In reply to | #180303 |
On Wed 19 Apr 2017 at 21:10:36 -0500, David Wright wrote: > On Sat 15 Apr 2017 at 23:21:33 (+0100), Brian wrote: > > > > Nobody in this thread, apart from the OP, has a Lenovo and an SD card. > > He is in the best position to test and report on this suggestion. Less > > than twenty minutes work. > > Frustratingly, I can't test this hypothesis, but I'm getting the > impression that whether a PC can boot¹ directly from an SD card in > the PC's SD slot depends² on how the card eventually appears on > the bus. I'll do the testing for you. :) I have an oldish laptop (Turion based) with a full-sized SD slot. An SD adapter with a micro SD card in it does not appear as > $ ls -l /dev/disk/by-id/ [edited] > usb-General_Combo_CardMMC_SD_000012345678-0:0 -> ../../sdb > usb-General_Combo_CardMMC_SD_000012345678-0:0-part1 -> ../../sdb1 > usb-General_Combo_CardMMC_SD_000012345678-0:0-part2 -> ../../sdb2 > $ cat /sys/bus/usb/devices/1-4:1.0/uevent > DEVTYPE=usb_interface > DRIVER=usb-storage > PRODUCT=1025/5d/16b > TYPE=0/0/0 > INTERFACE=8/6/80 > MODALIAS=usb:v1025p005Dd016Bdc00dsc00dp00ic08isc06ip50in00 > $ but does appear as > $ ls -l /dev/disk/by-id/ > mmc-SE32G_0x0109e2ec -> ../../mmcblk0 > mmc-SE32G_0x0109e2ec-part1 -> ../../mmcblk0p1 > $ cat /sys/bus/mmc/devices/mmc0\:aaaa/uevent > DRIVER=mmcblk > MMC_TYPE=SD > MMC_NAME=SE32G > MODALIAS=mmc:block > $ > > My guess from this is that the former SD card is connected to the > USB bus whereas the latter is connected to a different bus. The > likely candidate from what I've read is the PCIe bus. Good guess. brian@laptop:~$ lspci | grep CardBus 00:10.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller Also (without the card inserted): brian@laptop:~$ lsmod | grep mmc mmc_core 91803 3 sdhci,tifm_sd,sdhci_pci With the card inserted: brian@laptop:~$ lsmod | grep mmc mmc_block 30466 2 mmc_core 91803 4 mmc_block,sdhci,tifm_sd,sdhci_pci tifm_sd is the Texas Instruments FlashMedia SD driver. > My next guess is that the USB bus (sorry about the tautology) can > be run by the OS-less PC (obviously), whereas the other bus can't. > The trade-off is that a PCIe bus would give a much greater speed. This laptop only offers booting from CD and HD. GRUB's nativedisk module will get it booting from USB but, because of the bus the SD controller is on and GRUB having no modules for mmc, it will not boot from the SD card. There are quite a few complaints from users about machines not booting from SD cards in internal readers. My guess is that, when it is possible, the reader is always on the USB bus. My second guess is that aren't any machines which boot from a reader on the PCI bus. Maybe it is too complex to implement; maybe it will come in time. It took a fair amount of time after the introduction of USB for it to become a common, reliable booting process. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Pascal Hambourg <pascal@plouf.fr.eu.org> |
|---|---|
| Date | 2017-04-22 15:40 +0200 |
| Message-ID | <tz3qx-3py-11@gated-at.bofh.it> |
| In reply to | #180391 |
Le 22/04/2017 à 14:50, Brian a écrit : > On Wed 19 Apr 2017 at 21:10:36 -0500, David Wright wrote: >> >> My guess from this is that the former SD card is connected to the >> USB bus whereas the latter is connected to a different bus. The >> likely candidate from what I've read is the PCIe bus. > > Good guess. > > brian@laptop:~$ lspci | grep CardBus > 00:10.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller Err, what is the relationship between a CardBus (formerly PCMCIA) adapter and a SD card reader ? Aren't you confusing with something like this : 0b:00.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 13) Kernel driver in use: sdhci-pci (taken on my own ThinkPad, but what the heck, it does not have any SD card slot !)
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-04-22 15:50 +0200 |
| Message-ID | <tz3Ad-3tb-17@gated-at.bofh.it> |
| In reply to | #180392 |
On Sat 22 Apr 2017 at 15:35:33 +0200, Pascal Hambourg wrote: > Le 22/04/2017 à 14:50, Brian a écrit : > >On Wed 19 Apr 2017 at 21:10:36 -0500, David Wright wrote: > >> > >>My guess from this is that the former SD card is connected to the > >>USB bus whereas the latter is connected to a different bus. The > >>likely candidate from what I've read is the PCIe bus. > > > >Good guess. > > > > brian@laptop:~$ lspci | grep CardBus > > 00:10.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller > > Err, what is the relationship between a CardBus (formerly PCMCIA) adapter > and a SD card reader ? > > Aren't you confusing with something like this : More than likely. Thanks. > 0b:00.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host > Adapter (rev 13) > Kernel driver in use: sdhci-pci > > (taken on my own ThinkPad, but what the heck, it does not have any SD card > slot !) Any better? brian@laptop:~$ lspci | grep Texas 00:10.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller 00:10.2 FireWire (IEEE 1394): Texas Instruments OHCI Compliant IEEE 1394 Host Controller 00:10.3 Mass storage controller: Texas Instruments PCIxx21 Integrated FlashMedia Controller 00:10.4 SD Host controller: Texas Instruments PCI6411/6421/6611/6621/7411/7421/7611/7621 Secure Digital Controller -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Pascal Hambourg <pascal@plouf.fr.eu.org> |
|---|---|
| Date | 2017-04-22 16:00 +0200 |
| Message-ID | <tz3JT-3zd-9@gated-at.bofh.it> |
| In reply to | #180393 |
Le 22/04/2017 à 15:45, Brian a écrit : > On Sat 22 Apr 2017 at 15:35:33 +0200, Pascal Hambourg wrote: > >> 0b:00.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host >> Adapter (rev 13) >> Kernel driver in use: sdhci-pci >> >> (taken on my own ThinkPad, but what the heck, it does not have any SD card >> slot !) > > Any better? > > brian@laptop:~$ lspci | grep Texas > 00:10.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller > 00:10.2 FireWire (IEEE 1394): Texas Instruments OHCI Compliant IEEE 1394 Host Controller > 00:10.3 Mass storage controller: Texas Instruments PCIxx21 Integrated FlashMedia Controller > 00:10.4 SD Host controller: Texas Instruments PCI6411/6421/6611/6621/7411/7421/7611/7621 Secure Digital Controller These 4 devices appear to be "functions" inside the same TI chip. Looking again at my laptop, which has a PC-Card/CardBus slot : 0b:00.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev 8d) 0b:00.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 13) The SD card adapter is also in the same Ricoh chip as the CardBus adapter. It seems to be quite common.
[toc] | [prev] | [next] | [standalone]
| From | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| Date | 2017-04-22 16:50 +0200 |
| Message-ID | <tz4wi-44M-11@gated-at.bofh.it> |
| In reply to | #180393 |
On 04/22/2017 08:45 AM, Brian wrote: > On Sat 22 Apr 2017 at 15:35:33 +0200, Pascal Hambourg wrote: > >> Le 22/04/2017 à 14:50, Brian a écrit : >>> On Wed 19 Apr 2017 at 21:10:36 -0500, David Wright wrote: >>>> >>>> My guess from this is that the former SD card is connected to the >>>> USB bus whereas the latter is connected to a different bus. The >>>> likely candidate from what I've read is the PCIe bus. >>> >>> Good guess. >>> >>> brian@laptop:~$ lspci | grep CardBus >>> 00:10.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller >> >> Err, what is the relationship between a CardBus (formerly PCMCIA) adapter >> and a SD card reader ? >> >> Aren't you confusing with something like this : > > More than likely. Thanks. > >> 0b:00.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host >> Adapter (rev 13) >> Kernel driver in use: sdhci-pci >> >> (taken on my own ThinkPad, but what the heck, it does not have any SD card >> slot !) > > Any better? > > brian@laptop:~$ lspci | grep Texas > 00:10.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller > 00:10.2 FireWire (IEEE 1394): Texas Instruments OHCI Compliant IEEE 1394 Host Controller > 00:10.3 Mass storage controller: Texas Instruments PCIxx21 Integrated FlashMedia Controller > 00:10.4 SD Host controller: Texas Instruments PCI6411/6421/6611/6621/7411/7421/7611/7621 Secure Digital Controller > On the Lenovo ThinkPad T510 which started this thread I ran lspci as root. I believe the relevant lines are: 0d:00.0 SD Host controller: Ricoh Co Ltd MMC/SD Host Controller (rev 01) 0d:00.1 System peripheral: Ricoh Co Ltd R5U2xx (R5U230 / R5U231 / R5U241) [Memory Stick Host Controller] (rev 01)
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-04-27 18:20 +0200 |
| Message-ID | <tAUj7-338-7@gated-at.bofh.it> |
| In reply to | #180396 |
On Sat 22 Apr 2017 at 09:43:25 -0500, Richard Owlett wrote: > On 04/22/2017 08:45 AM, Brian wrote: > > > >Any better? > > > > brian@laptop:~$ lspci | grep Texas > > 00:10.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller > > 00:10.2 FireWire (IEEE 1394): Texas Instruments OHCI Compliant IEEE 1394 Host Controller > > 00:10.3 Mass storage controller: Texas Instruments PCIxx21 Integrated FlashMedia Controller > > 00:10.4 SD Host controller: Texas Instruments PCI6411/6421/6611/6621/7411/7421/7611/7621 Secure Digital Controller > > > > On the Lenovo ThinkPad T510 which started this thread I ran lspci as root. I > believe the relevant lines are: > 0d:00.0 SD Host controller: Ricoh Co Ltd MMC/SD Host Controller (rev 01) > 0d:00.1 System peripheral: Ricoh Co Ltd R5U2xx (R5U230 / R5U231 / R5U241) > [Memory Stick Host Controller] (rev 01) I think only the sdhci, sdhci_pci and mmc* modules are required to make this card visible to the installer and available for partitioning. (The output of 'lsmod' would be the place to look for confirmation). The installer's initrd contains these modules so the card would be seen. You were doubly fortunate at the store. Having the right kind of card reader made it possible to install Debian on the card. Having the kernels on card and hard disk identical made it possible for the OS on the card to boot. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-04-23 21:50 +0200 |
| Message-ID | <tzvG9-4lo-7@gated-at.bofh.it> |
| In reply to | #179998 |
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? :) -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-04-24 20:40 +0200 |
| Message-ID | <tzR3X-26a-3@gated-at.bofh.it> |
| In reply to | #180424 |
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. 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. 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. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2017-04-24 22:20 +0200 |
| Message-ID | <tzSCL-37e-29@gated-at.bofh.it> |
| In reply to | #180453 |
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.
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-04-25 15:10 +0200 |
| Message-ID | <tA8o9-57M-1@gated-at.bofh.it> |
| In reply to | #180454 |
On Mon 24 Apr 2017 at 15:10:16 -0500, David Wright wrote: > On Mon 24 Apr 2017 at 19:37:22 (+0100), Brian wrote: > > > > 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? No. Hard disk and CD are the only offerings. That's with the card in the slot when the machine is started. > > 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? I would not. But your remark caused *me* to react by taking a closer look at the modules loaded on Jessie. brian@laptop:~$ lsmod | grep mmc mmc_block 30466 0 mmc_core 91803 4 mmc_block,sdhci,tifm_sd,sdhci_pci brian@laptop:~$ lsmod | grep tifm tifm_sd 17060 0 tifm_7xx1 12769 0 tifm_core 13113 2 tifm_7xx1,tifm_sd mmc_core 91803 4 mmc_block,sdhci,tifm_sd,sdhci_pci 'rmmod tifm_7xx1' causes /dev/mmcblk01p to disappear. Booting without it present leads to no device file. Stating the obvious, the card will not work without the tifm_7xx1 module. In the installer tifm_7xx1 should be in /lib/modules/,,,,./drivers/misc/. It is not present. > Is there an mmc driver in that installation moduoles screen? No. > 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.) In the installer environment that number does not change when the card is taken out and pushed back in. In the Jessie environment it changes all the time, card in or out. > > 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? It very much looks like an installer bug. It is present on Stretch and Jessie. The hardware: brian@laptop:~$ lspci | grep Texas 00:10.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller 00:10.2 FireWire (IEEE 1394): Texas Instruments OHCI Compliant IEEE 1394 Host Controller 00:10.3 Mass storage controller: Texas Instruments PCIxx21 Integrated FlashMedia Controller 00:10.4 SD Host controller: Texas Instruments PCI6411/6421/6611/6621/7411/7421/7611/7621 Secure Digital Controller -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-05-04 19:20 +0200 |
| Message-ID | <tDsA2-6wT-5@gated-at.bofh.it> |
| In reply to | #180460 |
On Tue 25 Apr 2017 at 14:09:15 +0100, Brian wrote: > On Mon 24 Apr 2017 at 15:10:16 -0500, David Wright wrote: > > > On Mon 24 Apr 2017 at 19:37:22 (+0100), Brian wrote: > > > > > > 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? > > No. Hard disk and CD are the only offerings. That's with the card in the > slot when the machine is started. > > > > 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? > > I would not. But your remark caused *me* to react by taking a closer > look at the modules loaded on Jessie. > > brian@laptop:~$ lsmod | grep mmc > mmc_block 30466 0 > mmc_core 91803 4 mmc_block,sdhci,tifm_sd,sdhci_pci > brian@laptop:~$ lsmod | grep tifm > tifm_sd 17060 0 > tifm_7xx1 12769 0 > tifm_core 13113 2 tifm_7xx1,tifm_sd > mmc_core 91803 4 mmc_block,sdhci,tifm_sd,sdhci_pci > > 'rmmod tifm_7xx1' causes /dev/mmcblk01p to disappear. Booting without it > present leads to no device file. Stating the obvious, the card will not > work without the tifm_7xx1 module. > > In the installer tifm_7xx1 should be in /lib/modules/,,,,./drivers/misc/. > It is not present. > > > Is there an mmc driver in that installation moduoles screen? > > No. > > > 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.) > > In the installer environment that number does not change when the card > is taken out and pushed back in. In the Jessie environment it changes > all the time, card in or out. > > > > 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? > > It very much looks like an installer bug. It is present on Stretch and > Jessie. > > The hardware: > > brian@laptop:~$ lspci | grep Texas > 00:10.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller > 00:10.2 FireWire (IEEE 1394): Texas Instruments OHCI Compliant IEEE 1394 Host Controller > 00:10.3 Mass storage controller: Texas Instruments PCIxx21 Integrated FlashMedia Controller > 00:10.4 SD Host controller: Texas Instruments PCI6411/6421/6611/6621/7411/7421/7611/7621 Secure Digital Controller We have a happy ending: http://metadata.ftp-master.debian.org/changelogs/main/l/linux/linux_4.9.25-1_changelog linux (4.9.25-1) unstable; urgency=medium * udeb: Add tifm_7xx1 to mmc-modules (Closes: #861195) The modicum of help wasn't wasted. Kudos to everyone who participated in this thread. :) -- Brian.
[toc] | [prev] | [standalone]
Page 6 of 6 — ← Prev page 1 2 3 4 5 [6]
Back to top | Article view | linux.debian.user
csiph-web