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 5 of 6 — ← Prev page 1 2 3 4 [5] 6 Next page →
| From | Pascal Hambourg <pascal@plouf.fr.eu.org> |
|---|---|
| Date | 2017-04-19 20:30 +0200 |
| Message-ID | <ty2wy-6N4-13@gated-at.bofh.it> |
| In reply to | #180262 |
Le 19/04/2017 à 09:46, GiaThnYgeia a écrit : > > Question: You have a system with everything on a HD /dev/sda, you use > /dev/sdb a live disk to boot and install debian on /dev/sdc including > the grub on /dev/sdc > You unplug the live disk and reboot, what will grub do by default, what > systems will it show, by default? It depends which GRUB boots. If it's the GRUB on the hard disk that was /dev/sda during the installation, it will show the same systems as before the installation, i.e. it won't show the new system until you run update-grub to update its menu. If it's the GRUB on the device that was sdc during the installation, it will show all present systems that os-prober can detect. > I did not specify whether there is grub installed on /dev/sda or not, so > there are two variations. Indeed. > I suspect based on Bios settings the system > will either go to hd or to usb to boot, You did not mention previously that /dev/sdc was a USB device. > and that will be sda The boot order in the BIOS has no effect on the device discovery and naming in the Linux system. Also, most of the times USB devices lose the discovery race against ATA devices due to extra delay. So hda will probably always be the hard disk regardless of the boot device.
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2017-04-22 00:20 +0200 |
| Message-ID | <tyP4e-2YW-11@gated-at.bofh.it> |
| In reply to | #180288 |
On Wed 19 Apr 2017 at 20:25:46 (+0200), Pascal Hambourg wrote: > Le 19/04/2017 à 09:46, GiaThnYgeia a écrit : > > > >Question: You have a system with everything on a HD /dev/sda, you use > >/dev/sdb a live disk to boot and install debian on /dev/sdc including > >the grub on /dev/sdc > >You unplug the live disk and reboot, what will grub do by default, what > >systems will it show, by default? > > It depends which GRUB boots. > > If it's the GRUB on the hard disk that was /dev/sda during the > installation, it will show the same systems as before the > installation, i.e. it won't show the new system until you run > update-grub to update its menu. > > If it's the GRUB on the device that was sdc during the installation, > it will show all present systems that os-prober can detect. > > >I did not specify whether there is grub installed on /dev/sda or not, so > >there are two variations. > > Indeed. > > >I suspect based on Bios settings the system > >will either go to hd or to usb to boot, > > You did not mention previously that /dev/sdc was a USB device. > > >and that will be sda > > The boot order in the BIOS has no effect on the device discovery and > naming in the Linux system. Also, most of the times USB devices lose > the discovery race against ATA devices due to extra delay. So hda > will probably always be the hard disk regardless of the boot device. I've seen just one instance reported where an externally connected USB drive got /dev/sda whereas the internal mSATA got /dev/sdb. This was from someone who was about to dd copy the drive (which is why they checked). Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | Pascal Hambourg <pascal@plouf.fr.eu.org> |
|---|---|
| Date | 2017-04-22 15:50 +0200 |
| Message-ID | <tz3Ae-3tb-27@gated-at.bofh.it> |
| In reply to | #180378 |
Le 22/04/2017 à 00:11, David Wright a écrit : > On Wed 19 Apr 2017 at 20:25:46 (+0200), Pascal Hambourg wrote: >> >> The boot order in the BIOS has no effect on the device discovery and >> naming in the Linux system. Also, most of the times USB devices lose >> the discovery race against ATA devices due to extra delay. So hda >> will probably always be the hard disk regardless of the boot device. > > I've seen just one instance reported where an externally connected > USB drive got /dev/sda whereas the internal mSATA got /dev/sdb. Yes, I just got a report of a case where the internal SATA drives was sdb and sdc, and sda was probably the internal all-in-one card reader. But I never observed such a case myself. > This was from someone who was about to dd copy the drive (which is > why they checked). Hehe, we all know that sd* names are not reliable.
[toc] | [prev] | [next] | [standalone]
| From | songbird <songbird@anthive.com> |
|---|---|
| Date | 2017-04-12 21:00 +0200 |
| Message-ID | <tvvEJ-85z-5@gated-at.bofh.it> |
| In reply to | #180007 |
Pascal Hambourg wrote:
> Le 12/04/2017 à 17:14, Richard Owlett a écrit :
>>
>> Whether initiated after power-on OR a restart the observed sequence is:
>> 1. Appearance of the Grub2 menu with a choice of 4 instances of Debian.
>> 2. Select instance installed on the SD card.
>> 3. Screen clears, this message appears against the Debian 8 background.
>> error: no such device: 380e2a6d-f851-4fd1-9db2-869a0982b511.
>> Press any key to continue ...
>> 4. Otherwise the instance of Debian on the SD card boots routinely.
>
> This is a GRUB error message which cannot find the UUID specified in a
> "search" command.
>
> In order to investigate, can you
> - report the menu entry code for the SD card system in
> /boot/grub/grub.cfg (the one from the system on the hard drive owning
> GRUB, not the one on the SD card) ;
yep!
> - while the SD card is inserted, in the GRUB menu press "c" to enter a
> GRUB shell and report the result of the "ls" command.
also, check that the mount points exist for
the file system.
you may think you've installed things to one
location only to later find you've actually
put them someplace else...
another thing you can do is construct your own
menu entry and put it in /etc/grub.d/40_custom file
here is an example from when i was playing around
last week (you may need to insmod something else(s)
to get the efi, ssd, ext4, whatever partition table
type you use, etc. going): [and only use the lines from
between the ====='s] adjust as needed/desired. :)
oh and of course, check your partition tables on the
devices to make sure they're actually what you expect.
======
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry "Count to three before launching..." {
echo "1..."
sleep 1
echo "2..."
sleep 1
echo "3..."
sleep 1
set linux_gfx_mode=
export linux_gfx_mode
load_video
insmod gzio
insmod part_msdos
insmod ext2
insmod usb
insmod fat
set root='hd0,msdos1'
echo 'Loading Linux 4.9.0-1-686-pae ...'
linux /boot/vmlinuz-4.9.0-1-686-pae ro root=LABEL=ROOT_007
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-4.9.0-1-686-pae
}
======
and then run update-grub to get your new menu.
songbird
[toc] | [prev] | [next] | [standalone]
| From | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| Date | 2017-04-13 18:00 +0200 |
| Message-ID | <tvPk6-514-29@gated-at.bofh.it> |
| In reply to | #180017 |
On 04/12/2017 01:49 PM, songbird wrote:
> Pascal Hambourg wrote:
>> Le 12/04/2017 à 17:14, Richard Owlett a écrit :
>>>
>>> Whether initiated after power-on OR a restart the observed sequence is:
>>> 1. Appearance of the Grub2 menu with a choice of 4 instances of Debian.
>>> 2. Select instance installed on the SD card.
>>> 3. Screen clears, this message appears against the Debian 8 background.
>>> error: no such device: 380e2a6d-f851-4fd1-9db2-869a0982b511.
>>> Press any key to continue ...
>>> 4. Otherwise the instance of Debian on the SD card boots routinely.
>>
>> This is a GRUB error message which cannot find the UUID specified in a
>> "search" command.
>>
>> In order to investigate, can you
>> - report the menu entry code for the SD card system in
>> /boot/grub/grub.cfg (the one from the system on the hard drive owning
>> GRUB, not the one on the SD card) ;
>
> yep!
>
>
>> - while the SD card is inserted, in the GRUB menu press "c" to enter a
>> GRUB shell and report the result of the "ls" command.
>
> also, check that the mount points exist for
> the file system.
>
> you may think you've installed things to one
> location only to later find you've actually
> put them someplace else...
I do not understand those 2 questions.
Gparted displays what I expect to see.
All partitions are mountable using the "Places" menu on MATE's panel.
>
> another thing you can do is construct your own
> menu entry and put it in /etc/grub.d/40_custom file
I don't see that being informative for this problem.
>
> here is an example from when i was playing around
> last week (you may need to insmod something else(s)
> to get the efi, ssd, ext4, whatever partition table
> type you use, etc. going): [and only use the lines from
> between the ====='s] adjust as needed/desired. :)
>
> oh and of course, check your partition tables on the
> devices to make sure they're actually what you expect.
>
???
See comment re your 1st 2 questions.
> ======
> #!/bin/sh
> exec tail -n +3 $0
> # This file provides an easy way to add custom menu entries. Simply type the
> # menu entries you want to add after this comment. Be careful not to change
> # the 'exec tail' line above.
>
> menuentry "Count to three before launching..." {
>
> echo "1..."
> sleep 1
> echo "2..."
> sleep 1
> echo "3..."
> sleep 1
>
> set linux_gfx_mode=
> export linux_gfx_mode
> load_video
> insmod gzio
> insmod part_msdos
> insmod ext2
> insmod usb
> insmod fat
>
> set root='hd0,msdos1'
>
> echo 'Loading Linux 4.9.0-1-686-pae ...'
> linux /boot/vmlinuz-4.9.0-1-686-pae ro root=LABEL=ROOT_007
> echo 'Loading initial ramdisk ...'
> initrd /boot/initrd.img-4.9.0-1-686-pae
> }
> ======
>
> and then run update-grub to get your new menu.
>
>
> songbird
>
>
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-04-14 20:00 +0200 |
| Message-ID | <twdFL-43B-9@gated-at.bofh.it> |
| In reply to | #180069 |
On Thu 13 Apr 2017 at 10:58:10 -0500, Richard Owlett wrote: > On 04/12/2017 01:49 PM, songbird wrote: > > > > another thing you can do is construct your own > >menu entry and put it in /etc/grub.d/40_custom file > > I don't see that being informative for this problem. Quite the opposite; this is a very useful suggestion. Imagine that update-grub didn't give you something workable. You would (or should) be glad of the opportunity to roll your own. I do it all the time with removable devices. In your case, if grub-install had given you a "root=" line in a stanza it is possible you would not be booting the SD card. A 40_custom file needn't have it in. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| Date | 2017-04-14 20:50 +0200 |
| Message-ID | <twesa-4Ay-9@gated-at.bofh.it> |
| In reply to | #180138 |
On 04/14/2017 12:33 PM, Brian wrote: > On Thu 13 Apr 2017 at 10:58:10 -0500, Richard Owlett wrote: > >> On 04/12/2017 01:49 PM, songbird wrote: >>> >>> another thing you can do is construct your own >>> menu entry and put it in /etc/grub.d/40_custom file >> >> I don't see that being informative for this problem. > > Quite the opposite; this is a very useful suggestion. Imagine that > update-grub didn't give you something workable. You would (or should) > be glad of the opportunity to roll your own. I do it all the time with > removable devices. > > In your case, if grub-install had given you a "root=" line in a stanza > it is possible you would not be booting the SD card. A 40_custom file > needn't have it in. > I'll add it to my TODO list. I've never attempted to edit /etc/grub.d/40_custom file or its cousins. I've just received some need documentation for something I'm doing for someone else. Anyone have a few spare 100 hour days ;/
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-04-14 19:50 +0200 |
| Message-ID | <twdw5-404-11@gated-at.bofh.it> |
| In reply to | #180002 |
On Wed 12 Apr 2017 at 10:14:59 -0500, Richard Owlett wrote: > On 04/12/2017 07:39 AM, songbird wrote: > > > > - the bios may not be set correctly to find the device. > > I do not see how the bios might be involved. > Grub2 has been installed to the MBR of /dev/sda . > The only known reference to Grub2 is in the instance of Debian residing on > /dev/sda1 . Everything GRUB knows about devices comes from what the BIOS tells it. They are more than just good friends. :) It appears from 'ls' at a GRUB prompt that your GRUB does not know about your SD card. Booting takes place but GRUB takes its time to think about what it should do about not finding something it has been told to search for. In the end, it decides to go ahead, but in some cases it wouldn't. That would dispel your present mood of happiness. While we are it it: your update-grub stanza does not contain a line with set root=" in it. Could this possibly be a copy and paste error? I ask because the line is present on Jessie and testing when the device is a USB stick. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| Date | 2017-04-14 20:40 +0200 |
| Message-ID | <tweit-4wE-1@gated-at.bofh.it> |
| In reply to | #180137 |
On 04/14/2017 12:24 PM, Brian wrote:
> On Wed 12 Apr 2017 at 10:14:59 -0500, Richard Owlett wrote:
>
>> On 04/12/2017 07:39 AM, songbird wrote:
>>>
>>> - the bios may not be set correctly to find the device.
>>
>> I do not see how the bios might be involved.
>> Grub2 has been installed to the MBR of /dev/sda .
>> The only known reference to Grub2 is in the instance of Debian residing on
>> /dev/sda1 .
>
> Everything GRUB knows about devices comes from what the BIOS tells it.
> They are more than just good friends. :)
>
> It appears from 'ls' at a GRUB prompt that your GRUB does not know about
> your SD card. Booting takes place but GRUB takes its time to think about
> what it should do about not finding something it has been told to search
> for. In the end, it decides to go ahead, but in some cases it wouldn't.
> That would dispel your present mood of happiness.
>
> While we are it it: your update-grub stanza does not contain a line with
> set root=" in it. Could this possibly be a copy and paste error? I ask
> because the line is present on Jessie and testing when the device is a
> USB stick.
>
Just to eliminate any source of copy errors, here is the full contents
of grub.cfg created just prior to my most recent post
(https://lists.debian.org/debian-user/2017/04/msg00468.html). It refers
to the 2 new installs I mentioned in that post.
<begin paste>
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1
--hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1
8fe2965b-01ed-4227-9155-bc3e47ddf077
else
search --no-floppy --fs-uuid --set=root
8fe2965b-01ed-4227-9155-bc3e47ddf077
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
set timeout=-1
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1
--hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1
8fe2965b-01ed-4227-9155-bc3e47ddf077
else
search --no-floppy --fs-uuid --set=root
8fe2965b-01ed-4227-9155-bc3e47ddf077
fi
insmod png
if background_image /usr/share/images/desktop-base/lines-grub.png; then
set color_normal=white/black
set color_highlight=black/white
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class
gnu --class os $menuentry_id_option
'gnulinux-simple-8fe2965b-01ed-4227-9155-bc3e47ddf077' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1
--hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1
8fe2965b-01ed-4227-9155-bc3e47ddf077
else
search --no-floppy --fs-uuid --set=root
8fe2965b-01ed-4227-9155-bc3e47ddf077
fi
echo 'Loading Linux 3.16.0-4-686-pae ...'
linux /boot/vmlinuz-3.16.0-4-686-pae
root=UUID=8fe2965b-01ed-4227-9155-bc3e47ddf077 ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.16.0-4-686-pae
}
submenu 'Advanced options for Debian GNU/Linux' $menuentry_id_option
'gnulinux-advanced-8fe2965b-01ed-4227-9155-bc3e47ddf077' {
menuentry 'Debian GNU/Linux, with Linux 3.16.0-4-686-pae' --class
debian --class gnu-linux --class gnu --class os $menuentry_id_option
'gnulinux-3.16.0-4-686-pae-advanced-8fe2965b-01ed-4227-9155-bc3e47ddf077' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1
--hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1
8fe2965b-01ed-4227-9155-bc3e47ddf077
else
search --no-floppy --fs-uuid --set=root
8fe2965b-01ed-4227-9155-bc3e47ddf077
fi
echo 'Loading Linux 3.16.0-4-686-pae ...'
linux /boot/vmlinuz-3.16.0-4-686-pae
root=UUID=8fe2965b-01ed-4227-9155-bc3e47ddf077 ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.16.0-4-686-pae
}
menuentry 'Debian GNU/Linux, with Linux 3.16.0-4-686-pae (recovery
mode)' --class debian --class gnu-linux --class gnu --class os
$menuentry_id_option
'gnulinux-3.16.0-4-686-pae-recovery-8fe2965b-01ed-4227-9155-bc3e47ddf077' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1
--hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1
8fe2965b-01ed-4227-9155-bc3e47ddf077
else
search --no-floppy --fs-uuid --set=root
8fe2965b-01ed-4227-9155-bc3e47ddf077
fi
echo 'Loading Linux 3.16.0-4-686-pae ...'
linux /boot/vmlinuz-3.16.0-4-686-pae
root=UUID=8fe2965b-01ed-4227-9155-bc3e47ddf077 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.16.0-4-686-pae
}
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Debian GNU/Linux (8.6) (on /dev/mmcblk0p1)' --class gnu-linux
--class gnu --class os $menuentry_id_option
'osprober-gnulinux-simple-e57b2c64-74ec-4184-af71-d807e07f07dd' {
insmod part_msdos
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root
e57b2c64-74ec-4184-af71-d807e07f07dd
else
search --no-floppy --fs-uuid --set=root
e57b2c64-74ec-4184-af71-d807e07f07dd
fi
linux /boot/vmlinuz-3.16.0-4-686-pae
root=UUID=e57b2c64-74ec-4184-af71-d807e07f07dd ro quiet
initrd /boot/initrd.img-3.16.0-4-686-pae
}
submenu 'Advanced options for Debian GNU/Linux (8.6) (on
/dev/mmcblk0p1)' $menuentry_id_option
'osprober-gnulinux-advanced-e57b2c64-74ec-4184-af71-d807e07f07dd' {
menuentry 'Debian GNU/Linux (on /dev/mmcblk0p1)' --class gnu-linux
--class gnu --class os $menuentry_id_option
'osprober-gnulinux-/boot/vmlinuz-3.16.0-4-686-pae--e57b2c64-74ec-4184-af71-d807e07f07dd'
{
insmod part_msdos
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root
e57b2c64-74ec-4184-af71-d807e07f07dd
else
search --no-floppy --fs-uuid --set=root
e57b2c64-74ec-4184-af71-d807e07f07dd
fi
linux /boot/vmlinuz-3.16.0-4-686-pae
root=UUID=e57b2c64-74ec-4184-af71-d807e07f07dd ro quiet
initrd /boot/initrd.img-3.16.0-4-686-pae
}
menuentry 'Debian GNU/Linux, with Linux 3.16.0-4-686-pae (on
/dev/mmcblk0p1)' --class gnu-linux --class gnu --class os
$menuentry_id_option
'osprober-gnulinux-/boot/vmlinuz-3.16.0-4-686-pae--e57b2c64-74ec-4184-af71-d807e07f07dd'
{
insmod part_msdos
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root
e57b2c64-74ec-4184-af71-d807e07f07dd
else
search --no-floppy --fs-uuid --set=root
e57b2c64-74ec-4184-af71-d807e07f07dd
fi
linux /boot/vmlinuz-3.16.0-4-686-pae
root=UUID=e57b2c64-74ec-4184-af71-d807e07f07dd ro quiet
initrd /boot/initrd.img-3.16.0-4-686-pae
}
menuentry 'Debian GNU/Linux, with Linux 3.16.0-4-686-pae (recovery
mode) (on /dev/mmcblk0p1)' --class gnu-linux --class gnu --class os
$menuentry_id_option
'osprober-gnulinux-/boot/vmlinuz-3.16.0-4-686-pae-root=UUID=e57b2c64-74ec-4184-af71-d807e07f07dd
ro single-e57b2c64-74ec-4184-af71-d807e07f07dd' {
insmod part_msdos
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root
e57b2c64-74ec-4184-af71-d807e07f07dd
else
search --no-floppy --fs-uuid --set=root
e57b2c64-74ec-4184-af71-d807e07f07dd
fi
linux /boot/vmlinuz-3.16.0-4-686-pae
root=UUID=e57b2c64-74ec-4184-af71-d807e07f07dd ro single
initrd /boot/initrd.img-3.16.0-4-686-pae
}
}
menuentry 'Debian GNU/Linux (8.6) (on /dev/sda6)' --class gnu-linux
--class gnu --class os $menuentry_id_option
'osprober-gnulinux-simple-fa0b46ca-f75a-44a3-959e-d4a7f490c099' {
insmod part_msdos
insmod ext2
set root='hd0,msdos6'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos6
--hint-efi=hd0,msdos6 --hint-baremetal=ahci0,msdos6
fa0b46ca-f75a-44a3-959e-d4a7f490c099
else
search --no-floppy --fs-uuid --set=root
fa0b46ca-f75a-44a3-959e-d4a7f490c099
fi
linux /boot/vmlinuz-3.16.0-4-686-pae
root=UUID=fa0b46ca-f75a-44a3-959e-d4a7f490c099 ro quiet
initrd /boot/initrd.img-3.16.0-4-686-pae
}
submenu 'Advanced options for Debian GNU/Linux (8.6) (on /dev/sda6)'
$menuentry_id_option
'osprober-gnulinux-advanced-fa0b46ca-f75a-44a3-959e-d4a7f490c099' {
menuentry 'Debian GNU/Linux (on /dev/sda6)' --class gnu-linux --class
gnu --class os $menuentry_id_option
'osprober-gnulinux-/boot/vmlinuz-3.16.0-4-686-pae--fa0b46ca-f75a-44a3-959e-d4a7f490c099'
{
insmod part_msdos
insmod ext2
set root='hd0,msdos6'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos6
--hint-efi=hd0,msdos6 --hint-baremetal=ahci0,msdos6
fa0b46ca-f75a-44a3-959e-d4a7f490c099
else
search --no-floppy --fs-uuid --set=root
fa0b46ca-f75a-44a3-959e-d4a7f490c099
fi
linux /boot/vmlinuz-3.16.0-4-686-pae
root=UUID=fa0b46ca-f75a-44a3-959e-d4a7f490c099 ro quiet
initrd /boot/initrd.img-3.16.0-4-686-pae
}
menuentry 'Debian GNU/Linux, with Linux 3.16.0-4-686-pae (on
/dev/sda6)' --class gnu-linux --class gnu --class os
$menuentry_id_option
'osprober-gnulinux-/boot/vmlinuz-3.16.0-4-686-pae--fa0b46ca-f75a-44a3-959e-d4a7f490c099'
{
insmod part_msdos
insmod ext2
set root='hd0,msdos6'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos6
--hint-efi=hd0,msdos6 --hint-baremetal=ahci0,msdos6
fa0b46ca-f75a-44a3-959e-d4a7f490c099
else
search --no-floppy --fs-uuid --set=root
fa0b46ca-f75a-44a3-959e-d4a7f490c099
fi
linux /boot/vmlinuz-3.16.0-4-686-pae
root=UUID=fa0b46ca-f75a-44a3-959e-d4a7f490c099 ro quiet
initrd /boot/initrd.img-3.16.0-4-686-pae
}
menuentry 'Debian GNU/Linux, with Linux 3.16.0-4-686-pae (recovery
mode) (on /dev/sda6)' --class gnu-linux --class gnu --class os
$menuentry_id_option
'osprober-gnulinux-/boot/vmlinuz-3.16.0-4-686-pae-root=UUID=fa0b46ca-f75a-44a3-959e-d4a7f490c099
ro single-fa0b46ca-f75a-44a3-959e-d4a7f490c099' {
insmod part_msdos
insmod ext2
set root='hd0,msdos6'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos6
--hint-efi=hd0,msdos6 --hint-baremetal=ahci0,msdos6
fa0b46ca-f75a-44a3-959e-d4a7f490c099
else
search --no-floppy --fs-uuid --set=root
fa0b46ca-f75a-44a3-959e-d4a7f490c099
fi
linux /boot/vmlinuz-3.16.0-4-686-pae
root=UUID=fa0b46ca-f75a-44a3-959e-d4a7f490c099 ro single
initrd /boot/initrd.img-3.16.0-4-686-pae
}
}
menuentry 'Debian GNU/Linux (8.6) (on /dev/sda7)' --class gnu-linux
--class gnu --class os $menuentry_id_option
'osprober-gnulinux-simple-80d5963a-80b8-408c-8514-dbd0f15b9aed' {
insmod part_msdos
insmod ext2
set root='hd0,msdos7'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos7
--hint-efi=hd0,msdos7 --hint-baremetal=ahci0,msdos7
80d5963a-80b8-408c-8514-dbd0f15b9aed
else
search --no-floppy --fs-uuid --set=root
80d5963a-80b8-408c-8514-dbd0f15b9aed
fi
linux /boot/vmlinuz-3.16.0-4-686-pae
root=UUID=80d5963a-80b8-408c-8514-dbd0f15b9aed ro quiet
initrd /boot/initrd.img-3.16.0-4-686-pae
}
submenu 'Advanced options for Debian GNU/Linux (8.6) (on /dev/sda7)'
$menuentry_id_option
'osprober-gnulinux-advanced-80d5963a-80b8-408c-8514-dbd0f15b9aed' {
menuentry 'Debian GNU/Linux (on /dev/sda7)' --class gnu-linux --class
gnu --class os $menuentry_id_option
'osprober-gnulinux-/boot/vmlinuz-3.16.0-4-686-pae--80d5963a-80b8-408c-8514-dbd0f15b9aed'
{
insmod part_msdos
insmod ext2
set root='hd0,msdos7'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos7
--hint-efi=hd0,msdos7 --hint-baremetal=ahci0,msdos7
80d5963a-80b8-408c-8514-dbd0f15b9aed
else
search --no-floppy --fs-uuid --set=root
80d5963a-80b8-408c-8514-dbd0f15b9aed
fi
linux /boot/vmlinuz-3.16.0-4-686-pae
root=UUID=80d5963a-80b8-408c-8514-dbd0f15b9aed ro quiet
initrd /boot/initrd.img-3.16.0-4-686-pae
}
menuentry 'Debian GNU/Linux, with Linux 3.16.0-4-686-pae (on
/dev/sda7)' --class gnu-linux --class gnu --class os
$menuentry_id_option
'osprober-gnulinux-/boot/vmlinuz-3.16.0-4-686-pae--80d5963a-80b8-408c-8514-dbd0f15b9aed'
{
insmod part_msdos
insmod ext2
set root='hd0,msdos7'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos7
--hint-efi=hd0,msdos7 --hint-baremetal=ahci0,msdos7
80d5963a-80b8-408c-8514-dbd0f15b9aed
else
search --no-floppy --fs-uuid --set=root
80d5963a-80b8-408c-8514-dbd0f15b9aed
fi
linux /boot/vmlinuz-3.16.0-4-686-pae
root=UUID=80d5963a-80b8-408c-8514-dbd0f15b9aed ro quiet
initrd /boot/initrd.img-3.16.0-4-686-pae
}
menuentry 'Debian GNU/Linux, with Linux 3.16.0-4-686-pae (recovery
mode) (on /dev/sda7)' --class gnu-linux --class gnu --class os
$menuentry_id_option
'osprober-gnulinux-/boot/vmlinuz-3.16.0-4-686-pae-root=UUID=80d5963a-80b8-408c-8514-dbd0f15b9aed
ro single-80d5963a-80b8-408c-8514-dbd0f15b9aed' {
insmod part_msdos
insmod ext2
set root='hd0,msdos7'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos7
--hint-efi=hd0,msdos7 --hint-baremetal=ahci0,msdos7
80d5963a-80b8-408c-8514-dbd0f15b9aed
else
search --no-floppy --fs-uuid --set=root
80d5963a-80b8-408c-8514-dbd0f15b9aed
fi
linux /boot/vmlinuz-3.16.0-4-686-pae
root=UUID=80d5963a-80b8-408c-8514-dbd0f15b9aed ro single
initrd /boot/initrd.img-3.16.0-4-686-pae
}
}
menuentry 'Debian GNU/Linux (8.6) (on /dev/sdb1)' --class gnu-linux
--class gnu --class os $menuentry_id_option
'osprober-gnulinux-simple-fc15bc26-df3c-42d4-a646-c903ffc188b6' {
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1
--hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1
fc15bc26-df3c-42d4-a646-c903ffc188b6
else
search --no-floppy --fs-uuid --set=root
fc15bc26-df3c-42d4-a646-c903ffc188b6
fi
linux /boot/vmlinuz-3.16.0-4-686-pae
root=UUID=fc15bc26-df3c-42d4-a646-c903ffc188b6 ro quiet
initrd /boot/initrd.img-3.16.0-4-686-pae
}
submenu 'Advanced options for Debian GNU/Linux (8.6) (on /dev/sdb1)'
$menuentry_id_option
'osprober-gnulinux-advanced-fc15bc26-df3c-42d4-a646-c903ffc188b6' {
menuentry 'Debian GNU/Linux (on /dev/sdb1)' --class gnu-linux --class
gnu --class os $menuentry_id_option
'osprober-gnulinux-/boot/vmlinuz-3.16.0-4-686-pae--fc15bc26-df3c-42d4-a646-c903ffc188b6'
{
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1
--hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1
fc15bc26-df3c-42d4-a646-c903ffc188b6
else
search --no-floppy --fs-uuid --set=root
fc15bc26-df3c-42d4-a646-c903ffc188b6
fi
linux /boot/vmlinuz-3.16.0-4-686-pae
root=UUID=fc15bc26-df3c-42d4-a646-c903ffc188b6 ro quiet
initrd /boot/initrd.img-3.16.0-4-686-pae
}
menuentry 'Debian GNU/Linux, with Linux 3.16.0-4-686-pae (on
/dev/sdb1)' --class gnu-linux --class gnu --class os
$menuentry_id_option
'osprober-gnulinux-/boot/vmlinuz-3.16.0-4-686-pae--fc15bc26-df3c-42d4-a646-c903ffc188b6'
{
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1
--hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1
fc15bc26-df3c-42d4-a646-c903ffc188b6
else
search --no-floppy --fs-uuid --set=root
fc15bc26-df3c-42d4-a646-c903ffc188b6
fi
linux /boot/vmlinuz-3.16.0-4-686-pae
root=UUID=fc15bc26-df3c-42d4-a646-c903ffc188b6 ro quiet
initrd /boot/initrd.img-3.16.0-4-686-pae
}
menuentry 'Debian GNU/Linux, with Linux 3.16.0-4-686-pae (recovery
mode) (on /dev/sdb1)' --class gnu-linux --class gnu --class os
$menuentry_id_option
'osprober-gnulinux-/boot/vmlinuz-3.16.0-4-686-pae-root=UUID=fc15bc26-df3c-42d4-a646-c903ffc188b6
ro single-fc15bc26-df3c-42d4-a646-c903ffc188b6' {
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1
--hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1
fc15bc26-df3c-42d4-a646-c903ffc188b6
else
search --no-floppy --fs-uuid --set=root
fc15bc26-df3c-42d4-a646-c903ffc188b6
fi
linux /boot/vmlinuz-3.16.0-4-686-pae
root=UUID=fc15bc26-df3c-42d4-a646-c903ffc188b6 ro single
initrd /boot/initrd.img-3.16.0-4-686-pae
}
}
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/30_uefi-firmware ###
### END /etc/grub.d/30_uefi-firmware ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply
type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
<end paste>
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-04-15 12:50 +0200 |
| Message-ID | <twtrc-5tU-3@gated-at.bofh.it> |
| In reply to | #180139 |
On Fri 14 Apr 2017 at 13:33:40 -0500, Richard Owlett wrote:
> On 04/14/2017 12:24 PM, Brian wrote:
> >
> >Everything GRUB knows about devices comes from what the BIOS tells it.
> >They are more than just good friends. :)
> >
> >It appears from 'ls' at a GRUB prompt that your GRUB does not know about
> >your SD card. Booting takes place but GRUB takes its time to think about
> >what it should do about not finding something it has been told to search
> >for. In the end, it decides to go ahead, but in some cases it wouldn't.
> >That would dispel your present mood of happiness.
> >
> >While we are it it: your update-grub stanza does not contain a line with
> >set root=" in it. Could this possibly be a copy and paste error? I ask
> >because the line is present on Jessie and testing when the device is a
> >USB stick.
>
> Just to eliminate any source of copy errors, here is the full contents of
> grub.cfg created just prior to my most recent post
> (https://lists.debian.org/debian-user/2017/04/msg00468.html). It refers to
> the 2 new installs I mentioned in that post.
Thank you.
> ### BEGIN /etc/grub.d/30_os-prober ###
> menuentry 'Debian GNU/Linux (8.6) (on /dev/mmcblk0p1)' --class gnu-linux
> --class gnu --class os $menuentry_id_option
> 'osprober-gnulinux-simple-e57b2c64-74ec-4184-af71-d807e07f07dd' {
> insmod part_msdos
> insmod ext2
> if [ x$feature_platform_search_hint = xy ]; then
> search --no-floppy --fs-uuid --set=root
> e57b2c64-74ec-4184-af71-d807e07f07dd
> else
> search --no-floppy --fs-uuid --set=root
> e57b2c64-74ec-4184-af71-d807e07f07dd
> fi
> linux /boot/vmlinuz-3.16.0-4-686-pae
> root=UUID=e57b2c64-74ec-4184-af71-d807e07f07dd ro quiet
> initrd /boot/initrd.img-3.16.0-4-686-pae
> }
Definitely no "set root=" line. We will have to give GRUB credit for
knowing what it is doing. The absence of this line probably accounts for
your previous successful booting. With such a line you would possibly
have got "cannot get C/H/S values" as an error message. This throws
booting back to the GRUB menu.
Now for a big "but". :)
Your previous 'Debian GNU/Linux (8.6) (on /dev/mmcblk0p1)' stanza had
linux /boot/vmlinuz-3.16.0-4-686-pae root=/dev/mmcblk0p1
This one has
linux /boot/vmlinuz-3.16.0-4-686-pae root=UUID=e57b2c64-74ec-4184-af71-d807e07f07dd ro quiet
The UUID has changed (I think you said you had done this) but the kernel
now looks for init using the UUID rather than on /dev/mmcblk0p1. How did
you manage to get something significantly different?
And, more to the point, is there booting from the card without any error
messages?
--
Brian.
[toc] | [prev] | [next] | [standalone]
| From | songbird <songbird@anthive.com> |
|---|---|
| Date | 2017-04-15 16:10 +0200 |
| Message-ID | <twwyJ-7vz-1@gated-at.bofh.it> |
| In reply to | #180153 |
Brian wrote: ... > And, more to the point, is there booting from the card without any error > messages? ... and as additional info you can adjust some things in grub via editing /etc/default/grub (and running update-grub) if you don't like how the menu is being generated. songbird
[toc] | [prev] | [next] | [standalone]
| From | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| Date | 2017-04-15 19:00 +0200 |
| Message-ID | <twzdf-zg-11@gated-at.bofh.it> |
| In reply to | #180153 |
On 04/15/2017 05:24 AM, Brian wrote:
> On Fri 14 Apr 2017 at 13:33:40 -0500, Richard Owlett wrote:
>
>> On 04/14/2017 12:24 PM, Brian wrote:
>>>
>>> Everything GRUB knows about devices comes from what the BIOS tells it.
>>> They are more than just good friends. :)
>>>
>>> It appears from 'ls' at a GRUB prompt that your GRUB does not know about
>>> your SD card. Booting takes place but GRUB takes its time to think about
>>> what it should do about not finding something it has been told to search
>>> for. In the end, it decides to go ahead, but in some cases it wouldn't.
>>> That would dispel your present mood of happiness.
>>>
>>> While we are it it: your update-grub stanza does not contain a line with
>>> set root=" in it. Could this possibly be a copy and paste error? I ask
>>> because the line is present on Jessie and testing when the device is a
>>> USB stick.
>>
>> Just to eliminate any source of copy errors, here is the full contents of
>> grub.cfg created just prior to my most recent post
>> (https://lists.debian.org/debian-user/2017/04/msg00468.html). It refers to
>> the 2 new installs I mentioned in that post.
>
> Thank you.
>
>> ### BEGIN /etc/grub.d/30_os-prober ###
>> menuentry 'Debian GNU/Linux (8.6) (on /dev/mmcblk0p1)' --class gnu-linux
>> --class gnu --class os $menuentry_id_option
>> 'osprober-gnulinux-simple-e57b2c64-74ec-4184-af71-d807e07f07dd' {
>> insmod part_msdos
>> insmod ext2
>> if [ x$feature_platform_search_hint = xy ]; then
>> search --no-floppy --fs-uuid --set=root
>> e57b2c64-74ec-4184-af71-d807e07f07dd
>> else
>> search --no-floppy --fs-uuid --set=root
>> e57b2c64-74ec-4184-af71-d807e07f07dd
>> fi
>> linux /boot/vmlinuz-3.16.0-4-686-pae
>> root=UUID=e57b2c64-74ec-4184-af71-d807e07f07dd ro quiet
>> initrd /boot/initrd.img-3.16.0-4-686-pae
>> }
>
> Definitely no "set root=" line. We will have to give GRUB credit for
> knowing what it is doing. The absence of this line probably accounts for
> your previous successful booting. With such a line you would possibly
> have got "cannot get C/H/S values" as an error message. This throws
> booting back to the GRUB menu.
>
> Now for a big "but". :)
>
> Your previous 'Debian GNU/Linux (8.6) (on /dev/mmcblk0p1)' stanza had
>
> linux /boot/vmlinuz-3.16.0-4-686-pae root=/dev/mmcblk0p1
>
> This one has
>
> linux /boot/vmlinuz-3.16.0-4-686-pae root=UUID=e57b2c64-74ec-4184-af71-d807e07f07dd ro quiet
>
> The UUID has changed (I think you said you had done this) but the kernel
> now looks for init using the UUID rather than on /dev/mmcblk0p1. How did
> you manage to get something significantly different?
During the first install of Debian to the SD card I allowed the
installer to create a single partition filling the whole card. The
primary purpose of that install was a brute force determination of
whether or not my individual machine could read/write an SD card. The
machine was a replacement for a different used machine purchased from
the vendor. My accepting the SD card was dependent on that test.
I had reinstalled Debian to a more reasonably sized partition. That
would explain a changed UUID. During the reinstall I experimented with
installing grub to the MBR of the SD card. No grub was installed the
first time.
>
> And, more to the point, is there booting from the card without any error
> messages?
>
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-04-15 19:30 +0200 |
| Message-ID | <twzGi-YI-5@gated-at.bofh.it> |
| In reply to | #180163 |
On Sat 15 Apr 2017 at 11:52:09 -0500, Richard Owlett wrote: > On 04/15/2017 05:24 AM, Brian wrote: > > > >Now for a big "but". :) > > > >Your previous 'Debian GNU/Linux (8.6) (on /dev/mmcblk0p1)' stanza had > > > > linux /boot/vmlinuz-3.16.0-4-686-pae root=/dev/mmcblk0p1 > > > >This one has > > > > linux /boot/vmlinuz-3.16.0-4-686-pae root=UUID=e57b2c64-74ec-4184-af71-d807e07f07dd ro quiet > > > >The UUID has changed (I think you said you had done this) but the kernel > >now looks for init using the UUID rather than on /dev/mmcblk0p1. How did > >you manage to get something significantly different? > > During the first install of Debian to the SD card I allowed the installer to > create a single partition filling the whole card. The primary purpose of > that install was a brute force determination of whether or not my individual > machine could read/write an SD card. The machine was a replacement for a > different used machine purchased from the vendor. My accepting the SD card > was dependent on that test. > > I had reinstalled Debian to a more reasonably sized partition. That would > explain a changed UUID. During the reinstall I experimented with installing > grub to the MBR of the SD card. No grub was installed the first time. The UUID change is understandable. But hey - you've altered the ground rules! Now, it seems, you are exploring booting from the card itself rather than from GRUB on a hard disk. > >And, more to the point, is there booting from the card without any error > >messages? Did you overlook this question? You have said your machine does not offer booting from an SD card. Your answer will be interesting. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| Date | 2017-04-15 20:10 +0200 |
| Message-ID | <twAiZ-1r9-3@gated-at.bofh.it> |
| In reply to | #180166 |
On 04/15/2017 12:24 PM, Brian wrote: > On Sat 15 Apr 2017 at 11:52:09 -0500, Richard Owlett wrote: > >> On 04/15/2017 05:24 AM, Brian wrote: >>> >>> Now for a big "but". :) >>> >>> Your previous 'Debian GNU/Linux (8.6) (on /dev/mmcblk0p1)' stanza had >>> >>> linux /boot/vmlinuz-3.16.0-4-686-pae root=/dev/mmcblk0p1 >>> >>> This one has >>> >>> linux /boot/vmlinuz-3.16.0-4-686-pae root=UUID=e57b2c64-74ec-4184-af71-d807e07f07dd ro quiet >>> >>> The UUID has changed (I think you said you had done this) but the kernel >>> now looks for init using the UUID rather than on /dev/mmcblk0p1. How did >>> you manage to get something significantly different? >> >> During the first install of Debian to the SD card I allowed the installer to >> create a single partition filling the whole card. The primary purpose of >> that install was a brute force determination of whether or not my individual >> machine could read/write an SD card. The machine was a replacement for a >> different used machine purchased from the vendor. My accepting the SD card >> was dependent on that test. >> >> I had reinstalled Debian to a more reasonably sized partition. That would >> explain a changed UUID. During the reinstall I experimented with installing >> grub to the MBR of the SD card. No grub was installed the first time. > > The UUID change is understandable. But hey - you've altered the ground > rules! Now, it seems, you are exploring booting from the card itself > rather than from GRUB on a hard disk. I considered a safe test as the BIOS does not list it as a possible boot device. Among other goodies I've ordered an USB SD card reader. We'll know more in ~1 week. > >>> And, more to the point, is there booting from the card without any error >>> messages? > > Did you overlook this question? You have said your machine does not > offer booting from an SD card. Your answer will be interesting. > Thought I'd answered it elsewhere. It's on the menu that exists due to the grub on MBR of /dev/sda . There is an fschk error of some sort that flies by too fast. Otherwise, runs from SD card.
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-04-15 21:00 +0200 |
| Message-ID | <twB5n-1Jn-1@gated-at.bofh.it> |
| In reply to | #180172 |
On Sat 15 Apr 2017 at 13:08:30 -0500, Richard Owlett wrote: > On 04/15/2017 12:24 PM, Brian wrote: > > > >Did you overlook this question? You have said your machine does not > >offer booting from an SD card. Your answer will be interesting. > > Thought I'd answered it elsewhere. Nope. There has been no mention of booting *directly* *from* the SD card until this subthread. > It's on the menu that exists due to the grub on MBR of /dev/sda . So - the card is in its slot on your machine. You do 'update-grub'. There is now an entry in GRUB's menu. That is fine. This is what you are booting from? Your grub.cfg looks similar to what you posted before? If GRUB has been installed to the MBR of the SD card it has absolutely no bearing on the existence of the entry in GRUB's menu. It may as well not be there when GRUB on the MBR of /dev/sda constructs its grub.cfg. > There is an fschk error of some sort that flies by too fast. > Otherwise, runs from SD card. I like "simple"; I'm lost. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2017-04-15 23:40 +0200 |
| Message-ID | <twDAd-3sC-5@gated-at.bofh.it> |
| In reply to | #180175 |
On Sat 15 Apr 2017 at 19:57:32 (+0100), Brian wrote: > On Sat 15 Apr 2017 at 13:08:30 -0500, Richard Owlett wrote: > > > On 04/15/2017 12:24 PM, Brian wrote: > > > > > >Did you overlook this question? You have said your machine does not > > >offer booting from an SD card. Your answer will be interesting. > > > > Thought I'd answered it elsewhere. > > Nope. There has been no mention of booting *directly* *from* the SD card > until this subthread. > > > It's on the menu that exists due to the grub on MBR of /dev/sda . > > So - the card is in its slot on your machine. You do 'update-grub'. > There is now an entry in GRUB's menu. That is fine. This is what you are > booting from? Your grub.cfg looks similar to what you posted before? > > If GRUB has been installed to the MBR of the SD card it has absolutely > no bearing on the existence of the entry in GRUB's menu. It may as well > not be there when GRUB on the MBR of /dev/sda constructs its grub.cfg. > > > There is an fschk error of some sort that flies by too fast. > > Otherwise, runs from SD card. > > I like "simple"; I'm lost. One can avoid all this messing about with Grub by just copying a netinst ISO onto the SD card instead of a USB stick. But then you need, as I've pointed out just now, to insert the SD card into the slot _before_ booting, _and_ entering the CMOS Setup Menu to make sure the device has highest booting priority. (This is irrespective of how you wrote the SD card.) Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-04-16 00:30 +0200 |
| Message-ID | <twEmB-40M-1@gated-at.bofh.it> |
| In reply to | #180185 |
On Sat 15 Apr 2017 at 16:30:29 -0500, David Wright wrote: > On Sat 15 Apr 2017 at 19:57:32 (+0100), Brian wrote: > > On Sat 15 Apr 2017 at 13:08:30 -0500, Richard Owlett wrote: > > > > > On 04/15/2017 12:24 PM, Brian wrote: > > > > > > > >Did you overlook this question? You have said your machine does not > > > >offer booting from an SD card. Your answer will be interesting. > > > > > > Thought I'd answered it elsewhere. > > > > Nope. There has been no mention of booting *directly* *from* the SD card > > until this subthread. > > > > > It's on the menu that exists due to the grub on MBR of /dev/sda . > > > > So - the card is in its slot on your machine. You do 'update-grub'. > > There is now an entry in GRUB's menu. That is fine. This is what you are > > booting from? Your grub.cfg looks similar to what you posted before? > > > > If GRUB has been installed to the MBR of the SD card it has absolutely > > no bearing on the existence of the entry in GRUB's menu. It may as well > > not be there when GRUB on the MBR of /dev/sda constructs its grub.cfg. > > > > > There is an fschk error of some sort that flies by too fast. > > > Otherwise, runs from SD card. > > > > I like "simple"; I'm lost. > > One can avoid all this messing about with Grub by just copying a > netinst ISO onto the SD card instead of a USB stick. > > But then you need, as I've pointed out just now, to insert the > SD card into the slot _before_ booting, _and_ entering the CMOS > Setup Menu to make sure the device has highest booting priority. > (This is irrespective of how you wrote the SD card.) 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. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2017-04-20 04:20 +0200 |
| Message-ID | <ty9Ro-35a-1@gated-at.bofh.it> |
| In reply to | #180187 |
On Sat 15 Apr 2017 at 23:21:33 (+0100), Brian wrote: > On Sat 15 Apr 2017 at 16:30:29 -0500, David Wright wrote: > > > On Sat 15 Apr 2017 at 19:57:32 (+0100), Brian wrote: > > > On Sat 15 Apr 2017 at 13:08:30 -0500, Richard Owlett wrote: > > > > > > > On 04/15/2017 12:24 PM, Brian wrote: > > > > > > > > > >Did you overlook this question? You have said your machine does not > > > > >offer booting from an SD card. Your answer will be interesting. > > > > > > > > Thought I'd answered it elsewhere. > > > > > > Nope. There has been no mention of booting *directly* *from* the SD card > > > until this subthread. I think this was answered in 632231ab-5b9f-f22d-0c92-0207280233e9@cloud85.net which is https://lists.debian.org/debian-user/2017/04/msg00468.html in the other subthread. > > > > It's on the menu that exists due to the grub on MBR of /dev/sda . > > > > > > So - the card is in its slot on your machine. You do 'update-grub'. > > > There is now an entry in GRUB's menu. That is fine. This is what you are > > > booting from? Your grub.cfg looks similar to what you posted before? > > > > > > If GRUB has been installed to the MBR of the SD card it has absolutely > > > no bearing on the existence of the entry in GRUB's menu. It may as well > > > not be there when GRUB on the MBR of /dev/sda constructs its grub.cfg. > > > > > > > There is an fschk error of some sort that flies by too fast. > > > > Otherwise, runs from SD card. > > > > > > I like "simple"; I'm lost. > > > > One can avoid all this messing about with Grub by just copying a > > netinst ISO onto the SD card instead of a USB stick. > > > > But then you need, as I've pointed out just now, to insert the > > SD card into the slot _before_ booting, _and_ entering the CMOS > > Setup Menu to make sure the device has highest booting priority. > > (This is irrespective of how you wrote the SD card.) > > 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. AFAICT cards that can boot appear later 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 $ whereas those that can't 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. 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. ¹ By boot, I mean read the boot sector from the MBR or PBR of a device. ² vice versa really. Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | Pascal Hambourg <pascal@plouf.fr.eu.org> |
|---|---|
| Date | 2017-04-20 08:00 +0200 |
| Message-ID | <tydih-4ZP-1@gated-at.bofh.it> |
| In reply to | #180303 |
Le 20/04/2017 à 04:10, David Wright a écrit : > > AFAICT cards that can boot appear later 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 I had the same impression, but it is not always true according to Brian's counterexample.
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2017-04-20 17:20 +0200 |
| Message-ID | <tym2e-29R-19@gated-at.bofh.it> |
| In reply to | #180311 |
On Thu 20 Apr 2017 at 07:51:47 (+0200), Pascal Hambourg wrote: > Le 20/04/2017 à 04:10, David Wright a écrit : > > > >AFAICT cards that can boot appear later 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 > > I had the same impression, but it is not always true according to > Brian's counterexample. What Brian was demonstrating (not every card that appears as USB can be seen in the CMOS and boot) is not what interests me. The example I would be interested in seeing is the opposite, an SD card that appears as mmcblk to linux but is also visible in the CMOS screens and is therefore likely bootable. If so, how is it described in the CMOS—you rarely see this sort of stuff well documented. IOW how is a card like this one described in the CMOS? $ 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 $ (To give myself the best chance of answering this, I now leave an SD card in my laptop in case I ever manage to get into the CMOS again.) Cheers, David.
[toc] | [prev] | [next] | [standalone]
Page 5 of 6 — ← Prev page 1 2 3 4 [5] 6 Next page →
Back to top | Article view | linux.debian.user
csiph-web