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 | 20 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 3 of 6 — ← Prev page 1 2 [3] 4 5 6 Next page →
| From | Pascal Hambourg <pascal@plouf.fr.eu.org> |
|---|---|
| Date | 2017-04-18 20:40 +0200 |
| Message-ID | <txGcG-140-29@gated-at.bofh.it> |
| In reply to | #180223 |
Le 17/04/2017 à 21:05, Brian a écrit : > On Mon 17 Apr 2017 at 08:48:50 +0000, Curt wrote: > >> On 2017-04-17, David Wright <deblis@lionunicorn.co.uk> wrote: >>> >>> Oddly, this ancient laptop (Acer) has a slot that makes the SD card >>> look like a /dev/sdX disk, and the BIOS is happy to boot from it. >> >> I have an Acer X1430 with an internal "Multi-in-1 Media Card Reader" for >> which an SD card inserted into the reader is recognized by the kernel as >> as a /dev/sdX disk. > > You have to be careful here to distinguish between what the OS can > recognise and what GRUB can see. The kernel will be using the Multimedia > Card device drivers to detect the device Not always. If the card reader identifies itself as a generic USB mass storage device, then the kernel will use the same drivers as for USB drives and assign the same kind of name /dev/sd*. It seems that in this case, most BIOS recognize it and can boot from it. I guess that the kernel will use MMC device drivers only if the card reader identifies itself as a native SD/MMC card reader.
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-04-18 21:20 +0200 |
| Message-ID | <txGPo-1wE-15@gated-at.bofh.it> |
| In reply to | #180249 |
On Tue 18 Apr 2017 at 20:32:38 +0200, Pascal Hambourg wrote: > Le 17/04/2017 à 21:05, Brian a écrit : > >On Mon 17 Apr 2017 at 08:48:50 +0000, Curt wrote: > > > >>On 2017-04-17, David Wright <deblis@lionunicorn.co.uk> wrote: > >>> > >>>Oddly, this ancient laptop (Acer) has a slot that makes the SD card > >>>look like a /dev/sdX disk, and the BIOS is happy to boot from it. > >> > >>I have an Acer X1430 with an internal "Multi-in-1 Media Card Reader" for > >>which an SD card inserted into the reader is recognized by the kernel as > >>as a /dev/sdX disk. > > > >You have to be careful here to distinguish between what the OS can > >recognise and what GRUB can see. The kernel will be using the Multimedia > >Card device drivers to detect the device > > Not always. If the card reader identifies itself as a generic USB mass > storage device, then the kernel will use the same drivers as for USB drives > and assign the same kind of name /dev/sd*. It seems that in this case, most > BIOS recognize it and can boot from it. > > I guess that the kernel will use MMC device drivers only if the card reader > identifies itself as a native SD/MMC card reader. Seems reasonable and sensible. However, my main point was that the kernel identifying a card as a /dev/sdX disk does not imply it will necessarily be visible to GRUB and bootable by it. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Pascal Hambourg <pascal@plouf.fr.eu.org> |
|---|---|
| Date | 2017-04-19 00:20 +0200 |
| Message-ID | <txJDz-3bW-11@gated-at.bofh.it> |
| In reply to | #180254 |
Le 18/04/2017 à 21:14, Brian a écrit : > > However, my main point was that the kernel > identifying a card as a /dev/sdX disk does not imply it will necessarily > be visible to GRUB and bootable by it. If the card reader is idendified as /dev/sdX, then it probably behaves as a generic USB mass storage device and most BIOS can see it.
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-04-19 00:30 +0200 |
| Message-ID | <txJNf-3f2-7@gated-at.bofh.it> |
| In reply to | #180258 |
On Wed 19 Apr 2017 at 00:12:15 +0200, Pascal Hambourg wrote: > Le 18/04/2017 à 21:14, Brian a écrit : > > > >However, my main point was that the kernel > >identifying a card as a /dev/sdX disk does not imply it will necessarily > >be visible to GRUB and bootable by it. > > If the card reader is idendified as /dev/sdX, then it probably behaves as a > generic USB mass storage device and most BIOS can see it. A card in one of the slots of my card reader is identified as /dev/sdc1. The reader itself is seen by lsusb. The BIOS doesn't see it and does not have an option to boot from it. So I suppose my reader is not "most BIOS". What is it behaving as? -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Pascal Hambourg <pascal@plouf.fr.eu.org> |
|---|---|
| Date | 2017-04-19 20:40 +0200 |
| Message-ID | <ty2Ge-6Qx-19@gated-at.bofh.it> |
| In reply to | #180259 |
Le 19/04/2017 à 00:27, Brian a écrit : > On Wed 19 Apr 2017 at 00:12:15 +0200, Pascal Hambourg wrote: > >> Le 18/04/2017 à 21:14, Brian a écrit : >>> >>> However, my main point was that the kernel >>> identifying a card as a /dev/sdX disk does not imply it will necessarily >>> be visible to GRUB and bootable by it. >> >> If the card reader is idendified as /dev/sdX, then it probably behaves as a >> generic USB mass storage device and most BIOS can see it. > > A card in one of the slots of my card reader is identified as /dev/sdc1. > The reader itself is seen by lsusb. The BIOS doesn't see it and does not > have an option to boot from it. So I suppose my reader is not "most > BIOS". What is it behaving as? How does lsusb identify the card reader ? What driver/module does it use ? "lsusb -t" will tell both. If it uses usb-storage and the BIOS can boot from a USB device, then it surprises me that the BIOS cannot see and boot it when it contains a card with proper contents.
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-04-19 21:40 +0200 |
| Message-ID | <ty3Ci-7ov-13@gated-at.bofh.it> |
| In reply to | #180290 |
On Wed 19 Apr 2017 at 20:39:35 +0200, Pascal Hambourg wrote:
> Le 19/04/2017 à 00:27, Brian a écrit :
> >On Wed 19 Apr 2017 at 00:12:15 +0200, Pascal Hambourg wrote:
> >
> >>Le 18/04/2017 à 21:14, Brian a écrit :
> >>>
> >>>However, my main point was that the kernel
> >>>identifying a card as a /dev/sdX disk does not imply it will necessarily
> >>>be visible to GRUB and bootable by it.
> >>
> >>If the card reader is idendified as /dev/sdX, then it probably behaves as a
> >>generic USB mass storage device and most BIOS can see it.
> >
> >A card in one of the slots of my card reader is identified as /dev/sdc1.
> >The reader itself is seen by lsusb. The BIOS doesn't see it and does not
> >have an option to boot from it. So I suppose my reader is not "most
> >BIOS". What is it behaving as?
>
> How does lsusb identify the card reader ? What driver/module does it use ?
> "lsusb -t" will tell both.
root@test:~# lsusb
Bus 006 Device 002: ID 0644:0200 TEAC Corp. All-In-One Multi-Card Reader CA200/B/S
root@test:~# lsusb -t
/: Bus 07.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
|__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M
/: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/4p, 480M
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/3p, 12M
|__ Port 1: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 1: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
All external USB devices were disconnected, apart from the keyboard.
> If it uses usb-storage and the BIOS can boot from a USB device, then it
> surprises me that the BIOS cannot see and boot it when it contains a card
> with proper contents.
GRUB's 'ls' command shows
(hd0) (hd0,msdos5) (hd0,msdos1) (fd0)
when a CF card with Stretch on it is inserted before booting. (hd0) is a
SATA disk.
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. His feedback (and that of others) would be
appreciated, The opinion about the inability to boot from an internal
card reader appears in need of revision.
(As an aside; I *can* boot the CF card from the reader in my printer!).
--
Brian.
[toc] | [prev] | [next] | [standalone]
| From | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| Date | 2017-04-19 22:20 +0200 |
| Message-ID | <ty4eZ-7QW-11@gated-at.bofh.it> |
| In reply to | #180294 |
On 04/19/2017 02:31 PM, Brian wrote: > On Wed 19 Apr 2017 at 20:39:35 +0200, Pascal Hambourg wrote: > >> Le 19/04/2017 à 00:27, Brian a écrit : >>> On Wed 19 Apr 2017 at 00:12:15 +0200, Pascal Hambourg wrote: >>> >>>> Le 18/04/2017 à 21:14, Brian a écrit : >>>>> >>>>> However, my main point was that the kernel >>>>> identifying a card as a /dev/sdX disk does not imply it will necessarily >>>>> be visible to GRUB and bootable by it. >>>> >>>> If the card reader is idendified as /dev/sdX, then it probably behaves as a >>>> generic USB mass storage device and most BIOS can see it. >>> >>> A card in one of the slots of my card reader is identified as /dev/sdc1. >>> The reader itself is seen by lsusb. The BIOS doesn't see it and does not >>> have an option to boot from it. So I suppose my reader is not "most >>> BIOS". What is it behaving as? >> >> How does lsusb identify the card reader ? What driver/module does it use ? >> "lsusb -t" will tell both. > > root@test:~# lsusb > Bus 006 Device 002: ID 0644:0200 TEAC Corp. All-In-One Multi-Card Reader CA200/B/S > > root@test:~# lsusb -t > /: Bus 07.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M > /: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M > |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M > /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/4p, 480M > /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M > /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M > /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M > /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M > |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/3p, 12M > |__ Port 1: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 12M > |__ Port 1: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 12M > |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M > > All external USB devices were disconnected, apart from the keyboard. > >> If it uses usb-storage and the BIOS can boot from a USB device, then it >> surprises me that the BIOS cannot see and boot it when it contains a card >> with proper contents. > > GRUB's 'ls' command shows > > (hd0) (hd0,msdos5) (hd0,msdos1) (fd0) > > when a CF card with Stretch on it is inserted before booting. (hd0) is a > SATA disk. > > 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 test. A few days ago I had re-installed Debian to the SD card along with installing GRUB2 to the MBR of the SD card. The first tings I did were: power off the laptop remove the SD card from the reader which BIOS does not see inserted into the new USB SD card reader powered on the laptop at the BIOS prompt selected to boot from an alternate device at the appropriate sub-menu chose the USB SD card reader (appeared as /dev/sdb1) booted with no apparent problem or error messages Will run your tests Monday. > His feedback (and that of others) would be > appreciated, The opinion about the inability to boot from an internal > card reader appears in need of revision. > > (As an aside; I *can* boot the CF card from the reader in my printer!). >
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-04-22 13:50 +0200 |
| Message-ID | <tz1I5-2k8-11@gated-at.bofh.it> |
| In reply to | #180296 |
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. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| Date | 2017-04-22 19:00 +0200 |
| Message-ID | <tz6y5-5h0-7@gated-at.bofh.it> |
| In reply to | #180389 |
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 don't know what (ahci1) is.
>
> Repeating above with empty card reader I get:
> (ahci) (ahci0,msdosXX) (usb0a) (usb0b) (ahci1)
>
> 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'll not attempt "Edit /etc/grub.d/40_custom to have ..."
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-04-22 20:10 +0200 |
| Message-ID | <tz7DQ-69b-1@gated-at.bofh.it> |
| In reply to | #180399 |
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.
--
Brian.
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-04-22 20:20 +0200 |
| Message-ID | <tz7Nv-6cn-3@gated-at.bofh.it> |
| In reply to | #180401 |
On Sat 22 Apr 2017 at 19:00:50 +0100, Brian wrote: > 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. All you have to do is 1. Boot with the SD card in a slot of the Lenovo's reader. 2. Use the c key at the GRUB prompt and type 'ls'. Provide us with the output. 3. Issue the command 'nativedisk' and provide the output of 'ls' again. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| Date | 2017-04-22 20:40 +0200 |
| Message-ID | <tz86R-6is-9@gated-at.bofh.it> |
| In reply to | #180401 |
On 04/22/2017 01:00 PM, Brian wrote:
> 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.
>
Any line containing "(ahci)" was after having used "nativedisk".
Any line containing "(hd0)" was after *NOT* having used "nativedisk".
The only time the SD card was seen was when the USB reader was used.
All lines followed a power off/on cycle to force identical starting
conditions.
My reference to "5-in-1 reader" was reference to
https://www.cnet.com/products/lenovo-thinkpad-t510/specs/ .
I have no means to verify CNET's statement.
I'd place more trust in my statement in
https://lists.debian.org/debian-user/2017/04/msg00729.html saying:
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)
Side question
When interrupting the grub menu by typing C, is there any functional
equivalent of using the "script" command in a terminal window?
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-04-22 21:10 +0200 |
| Message-ID | <tz8zV-6He-31@gated-at.bofh.it> |
| In reply to | #180403 |
On Sat 22 Apr 2017 at 13:34:41 -0500, Richard Owlett wrote: > On 04/22/2017 01:00 PM, Brian wrote: > > > >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. > > Any line containing "(ahci)" was after having used "nativedisk". > Any line containing "(hd0)" was after *NOT* having used "nativedisk". That makes things clearer. > The only time the SD card was seen was when the USB reader was used. That is exactly the information wanted. When the card is on the PCI bus GRUB does not see it; on the USB bus it does. It fits the lspci info you give below. > All lines followed a power off/on cycle to force identical starting > conditions. > > My reference to "5-in-1 reader" was reference to > https://www.cnet.com/products/lenovo-thinkpad-t510/specs/ . > I have no means to verify CNET's statement. > > I'd place more trust in my statement in > https://lists.debian.org/debian-user/2017/04/msg00729.html saying: > 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) > Side question > When interrupting the grub menu by typing C, is there any functional > equivalent of using the "script" command in a terminal window? I'm afraid not. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2017-04-22 23:30 +0200 |
| Message-ID | <tzaLn-81z-3@gated-at.bofh.it> |
| In reply to | #180403 |
On Sat 22 Apr 2017 at 13:34:41 (-0500), Richard Owlett wrote:
> On 04/22/2017 01:00 PM, Brian wrote:
> >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.
> >
>
> Any line containing "(ahci)" was after having used "nativedisk".
> Any line containing "(hd0)" was after *NOT* having used "nativedisk".
> The only time the SD card was seen was when the USB reader was used.
> All lines followed a power off/on cycle to force identical starting
> conditions.
>
> My reference to "5-in-1 reader" was reference to
> https://www.cnet.com/products/lenovo-thinkpad-t510/specs/ .
> I have no means to verify CNET's statement.
>
> I'd place more trust in my statement in
> https://lists.debian.org/debian-user/2017/04/msg00729.html saying:
> 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)
That looks about right. I'd be interested to know what the BIOS can
see, ie before Grub has loaded. I would predict you can see the USB
but not the MMC/SD card slot. (Note that you will probably need to
insert something in them to stand _any_ chance of seeing any of them.)
BTW did you notice that the webpage gave the battery life as 7.8 sec!
Cheers,
David.
[toc] | [prev] | [next] | [standalone]
| From | Doug <dmcgarrett@optonline.net> |
|---|---|
| Date | 2017-04-15 21:30 +0200 |
| Message-ID | <twByp-2cM-3@gated-at.bofh.it> |
| In reply to | #180159 |
On 04/15/2017 10:28 AM, David Wright wrote: > On Sat 15 Apr 2017 at 11:05:12 (+0200), Pascal Hambourg wrote: >> Le 15/04/2017 à 02:37, David Wright a écrit : >>> Of course, an SD card can be >>> made to look like a USB stick just by sticking it in a card reader. >> I guess you mean "in a USB-to-SD card adapter", which translates a >> SD card into a USB mass storage device (/dev/sd*). > Yes, you guess correctly. Writing 40 years ago, I would use those same > words to describe a washing-machine sized object for reading punched > cards. Nowadays, if you type "card reader" into google, you will be > proffered several more sophisticated ones than mine, together with > some different varieties of credit card reader. > >> A SD card reader such as the one the OP has just exposes the SD card >> as what it is, a SD/MMC card (/dev/mmcblk*). > I assumed that the OP, writing about a laptop, had no card reader, > and was inserting the SD card directly into the computer. > > As it happens, if you do this with the ancient laptop I'm typing on, > it has the functionality of a card reader built into it and you get > a /dev/sd*, and that can be boot an SD card directly. > > Cheers, > David. > > It turns out that there are two kinds of cards that look the same, but on a Dell laptop I have, one kind won't be recognized and the other works. I don't remember which is which, or what they are called. One is SD, the other something else. Of course, I found out the hard way, but it really doesn't matter, since I don't need to use the laptop for that. --doug
[toc] | [prev] | [next] | [standalone]
| From | Pascal Hambourg <pascal@plouf.fr.eu.org> |
|---|---|
| Date | 2017-04-15 22:20 +0200 |
| Message-ID | <twCkN-2Jg-1@gated-at.bofh.it> |
| In reply to | #180179 |
Le 15/04/2017 à 21:24, Doug a écrit : > > It turns out that there are two kinds of cards that look the same, but > on a Dell laptop I have, one kind won't be recognized and the other > works. I don't remember > which is which, or what they are called. One is SD, the other something > else. MMC, SDHC, SDXC ?
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-04-15 13:10 +0200 |
| Message-ID | <twtKx-5Pq-1@gated-at.bofh.it> |
| In reply to | #180148 |
On Fri 14 Apr 2017 at 20:02:11 -0400, songbird wrote: > what i would do for grins is unplug the > devices other than the SSD and the installation > media and then do a base system (simple install > - not expert) and see what the installer does > detect and writes in the fstab and grub menu > (it may even boot). you may then use those This is cargo cult. simple install=some control of d-i. expert install=total control of d-i. In both cases the OP does not want to install a boot loader to the device. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | songbird <songbird@anthive.com> |
|---|---|
| Date | 2017-04-15 16:10 +0200 |
| Message-ID | <twwyK-7vz-5@gated-at.bofh.it> |
| In reply to | #180154 |
Brian wrote: > songbird wrote: > >> what i would do for grins is unplug the >> devices other than the SSD and the installation >> media and then do a base system (simple install >> - not expert) and see what the installer does >> detect and writes in the fstab and grub menu >> (it may even boot). you may then use those > > This is cargo cult. thus my expression "for grins". ;) i noticed my own lack of previous comprehension as i thought all along the OP was putting things on an SSD device and not a SD chip. my SD reader is on a USB header device with many other things. maybe grub needs something provided by the modules: usbms, ehci, uhci or ohci? these can be tested at the command line and then doing ls -l to see if the device shows up or not... > simple install=some control of d-i. > expert install=total control of d-i. > > In both cases the OP does not want to install a boot loader to the > device. dd can get rid of it easily enough. i think the possible confusion for a more ancient machine may be cleared up enough to get workable bits. how we get to workable bits may be a different route, but in the end if they work we have gotten to the cheese in this particular maze of twisty-turny passages even if they all look alike (1's and 0's). songbird
[toc] | [prev] | [next] | [standalone]
| From | Pascal Hambourg <pascal@plouf.fr.eu.org> |
|---|---|
| Date | 2017-04-15 19:30 +0200 |
| Message-ID | <twzGi-YI-15@gated-at.bofh.it> |
| In reply to | #180157 |
Le 15/04/2017 à 15:55, songbird a écrit : > > maybe grub needs something provided by the > modules: > > usbms, ehci, uhci or ohci? Be careful if you're going to use driver modules (USB, PATA, AHCI...) to get direct access to a device. It disables access to *all* devices through the BIOS, including the device GRUB was booted from and reads its own files.
[toc] | [prev] | [next] | [standalone]
| From | Pascal Hambourg <pascal@plouf.fr.eu.org> |
|---|---|
| Date | 2017-04-15 19:30 +0200 |
| Message-ID | <twzGi-YI-11@gated-at.bofh.it> |
| In reply to | #180154 |
Le 15/04/2017 à 12:44, Brian a écrit : > > simple install=some control of d-i. > expert install=total control of d-i. Expert install gives more control, but is far from granting total control. The Debian installer still has many automated actions that you cannot control even in expert mode.
[toc] | [prev] | [next] | [standalone]
Page 3 of 6 — ← Prev page 1 2 [3] 4 5 6 Next page →
Back to top | Article view | linux.debian.user
csiph-web