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 1 of 6 [1] 2 3 4 5 6 Next page →
| From | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| Date | 2017-04-12 13:20 +0200 |
| Subject | Possibly erroneous "device not present" message during boot |
| Message-ID | <tvotB-3N9-37@gated-at.bofh.it> |
Due to circumstances, will note rule out any of hardware, software, or confused operator as underlying cause. BACKGROUND: The hardware is a used Lenovo T510 laptop purchased a couple of months ago. Jessie with MATE desktop has been running fine. Yesterday I purchased a Kingston Technology 512GB SD, primarily for backups. As this individual unit had never had an SD card installed, the agreement with the store was if the card did not work in this machine I would not have to purchase it. My acceptance test was to install Jessie using a flash drive with DVD 1 of 13 of Debian 8.6.0. It was my standard install which does NOT include either a swap partition being activated during install NOR installing a boot loader. I booted into my primary OS and ran update-grub with no problems. I rebooted, choosing the SD card from the Grub2 menu. No apparent problem. Also verified my other Debian installs could read/write the SD card. These tests were performed before leaving the store. THE SYMPTOM: When I got home and booted to the SD card I noticed a message appeared for ~10 seconds reporting that a device was not found giving the UUID of the SD card. I verified the UUID by checking the fstab file and by using gparted. THE QUESTION: Do I have an actual problem? What should I be checking? TIA
[toc] | [next] | [standalone]
| From | songbird <songbird@anthive.com> |
|---|---|
| Date | 2017-04-12 14:50 +0200 |
| Message-ID | <tvpSF-4v9-1@gated-at.bofh.it> |
| In reply to | #179998 |
Richard Owlett wrote: ... > THE SYMPTOM: > > When I got home and booted to the SD card I noticed a message appeared > for ~10 seconds reporting that a device was not found giving the UUID of > the SD card. > > I verified the UUID by checking the fstab file and by using gparted. > > THE QUESTION: > > Do I have an actual problem? > What should I be checking? - the bios may not be set correctly to find the device. - you may have changed it but not saved it (ditto on the partition table). - you may have the root/boot partitions in fstab wrong (i never use UUIDs but make partition labels instead and use those). - error in preseed file which put something in a different location than intended. - grub may not have done what you expected. songbird
[toc] | [prev] | [next] | [standalone]
| From | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| Date | 2017-04-12 17:20 +0200 |
| Message-ID | <tvsdP-64C-3@gated-at.bofh.it> |
| In reply to | #179999 |
On 04/12/2017 07:39 AM, songbird wrote:
> Richard Owlett wrote:
>
> ...
>> THE SYMPTOM:
>>
>> When I got home and booted to the SD card I noticed a message appeared
>> for ~10 seconds reporting that a device was not found giving the UUID of
>> the SD card.
>>
>> I verified the UUID by checking the fstab file and by using gparted.
>>
>> THE QUESTION:
>>
>> Do I have an actual problem?
>> What should I be checking?
>
> - 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 .
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.
>
> - you may have changed it but not saved it (ditto
> on the partition table).
What may may I have changed and not saved.
The *ONLY* time anything has been to/with/??? the partition &/or
partition was when the Debian Installer created the single partition as
a "Primary partition" and formatted it as ext4.
>
> - you may have the root/boot partitions in
> fstab wrong (i never use UUIDs but make partition
> labels instead and use those).
"fstab" was created by the installer using its defaults.
I agree that UUIDs make no sense for a application such as mine.
I haven't got around to changing things - TODO is lengthening.
>
> - error in preseed file which put something in
> a different location than intended.
No preseed file has been involved. The installation was completely
manual in Expert Mode.
>
> - grub may not have done what you expected.
As likely as moon being "green cheese"? <grin>
I've not had a grub problem since first using it on Squeeze, although
I've often doubted the sanity of some design choices.
Besides a few thousand people use it daily without problems ;/
In theory, I know of the existence of log files. I've never had reason
to investigate them. Which should I preserve, if any?
>
>
> songbird
>
>
[toc] | [prev] | [next] | [standalone]
| From | Pascal Hambourg <pascal@plouf.fr.eu.org> |
|---|---|
| Date | 2017-04-12 19:20 +0200 |
| Message-ID | <tvu5Y-7gS-17@gated-at.bofh.it> |
| In reply to | #180002 |
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) ; - 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.
[toc] | [prev] | [next] | [standalone]
| From | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| Date | 2017-04-12 20:40 +0200 |
| Message-ID | <tvvln-7Yl-1@gated-at.bofh.it> |
| In reply to | #180007 |
On 04/12/2017 12:13 PM, 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) ;
On theory "too much better than too little" I see:
<begin quote>
### 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-380e2a6d-f851-4fd1-9db2-869a0982b511' {
insmod part_msdos
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root
380e2a6d-f851-4fd1-9db2-869a0982b511
else
search --no-floppy --fs-uuid --set=root
380e2a6d-f851-4fd1-9db2-869a0982b511
fi
linux /boot/vmlinuz-3.16.0-4-686-pae root=/dev/mmcblk0p1
initrd /boot/initrd.img-3.16.0-4-686-pae
}
<end quote>
> - 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.
Did not see any way to capture the output. So made manual copy. The
following appeared on a single line.
(hd0) (hd0, msdos9) (hd0, msdos8) (hd0, msdos7) (hd0, msdos6)
(hd0, msdos5) (hd0, msdos1) (hd1) (hd1, msdos1)
Any suggested reading on the "BASH like shell" I just used?
My initial DuckDuckGo search was *NOT* encouraging ;/
If retirement is not for learning, what use is it?
Thank you.
>
>
[toc] | [prev] | [next] | [standalone]
| From | Pascal Hambourg <pascal@plouf.fr.eu.org> |
|---|---|
| Date | 2017-04-12 21:10 +0200 |
| Message-ID | <tvvOp-8oz-1@gated-at.bofh.it> |
| In reply to | #180014 |
Le 12/04/2017 à 20:33, Richard Owlett a écrit :
> On 04/12/2017 12:13 PM, Pascal Hambourg wrote:
>>
>> - 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) ;
>
> On theory "too much better than too little" I see:
> <begin quote>
> ### 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-380e2a6d-f851-4fd1-9db2-869a0982b511' {
> insmod part_msdos
> insmod ext2
> if [ x$feature_platform_search_hint = xy ]; then
> search --no-floppy --fs-uuid --set=root
> 380e2a6d-f851-4fd1-9db2-869a0982b511
> else
> search --no-floppy --fs-uuid --set=root
> 380e2a6d-f851-4fd1-9db2-869a0982b511
> fi
> linux /boot/vmlinuz-3.16.0-4-686-pae root=/dev/mmcblk0p1
> initrd /boot/initrd.img-3.16.0-4-686-pae
> }
> <end quote>
>
>> - 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.
>
> (hd0) (hd0, msdos9) (hd0, msdos8) (hd0, msdos7) (hd0, msdos6)
> (hd0, msdos5) (hd0, msdos1) (hd1) (hd1, msdos1)
Some BIOS expose a removable media only when booting from it, so my
theory was that your BIOS did not expose the SD card and GRUB could not
see it. The result of ls proves me wrong.
Can you also report the output of "ls (hd1,msdos1)" to check what GRUB
sees of the partition on the card ?
> Any suggested reading on the "BASH like shell" I just used?
The GRUB manual at <https://www.gnu.org/software/grub/manual/grub.html>
describes some of the commands, but not all. The shell can display the
command list with "help" and information about a specific command with
"help <command>".
[toc] | [prev] | [next] | [standalone]
| From | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| Date | 2017-04-13 13:50 +0200 |
| Message-ID | <tvLqa-2qX-13@gated-at.bofh.it> |
| In reply to | #180019 |
On 04/12/2017 02:03 PM, Pascal Hambourg wrote: > Le 12/04/2017 à 20:33, Richard Owlett a écrit : >> On 04/12/2017 12:13 PM, Pascal Hambourg wrote: [snip] >>> - 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. >> >> (hd0) (hd0, msdos9) (hd0, msdos8) (hd0, msdos7) (hd0, msdos6) >> (hd0, msdos5) (hd0, msdos1) (hd1) (hd1, msdos1) > > Some BIOS expose a removable media only when booting from it, so my > theory was that your BIOS did not expose the SD card and GRUB could > not see it. The result of ls proves me wrong. > > Can you also report the output of "ls (hd1,msdos1)" to check what GRUB > sees of the partition on the card ? It gives the partitioning description, UUID, and label of the USB flash drive that was plugged in. It is FAT formatted and used to exchange information with my Windows machine. > >> Any suggested reading on the "BASH like shell" I just used? > > The GRUB manual at <https://www.gnu.org/software/grub/manual/grub.html> It was what prompted me to ask ;/ > describes some of the commands, but not all. The shell can display the > command list with "help" and information about a specific command with > "help <command>". > >
[toc] | [prev] | [next] | [standalone]
| From | Pascal Hambourg <pascal@plouf.fr.eu.org> |
|---|---|
| Date | 2017-04-13 17:50 +0200 |
| Message-ID | <tvPaq-4WE-19@gated-at.bofh.it> |
| In reply to | #180059 |
Le 13/04/2017 à 13:40, Richard Owlett a écrit : > On 04/12/2017 02:03 PM, Pascal Hambourg wrote: >> Le 12/04/2017 à 20:33, Richard Owlett a écrit : >>> On 04/12/2017 12:13 PM, Pascal Hambourg wrote: > > [snip] >>>> - 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. >>> >>> (hd0) (hd0, msdos9) (hd0, msdos8) (hd0, msdos7) (hd0, msdos6) >>> (hd0, msdos5) (hd0, msdos1) (hd1) (hd1, msdos1) >> >> Some BIOS expose a removable media only when booting from it, so my >> theory was that your BIOS did not expose the SD card and GRUB could >> not see it. The result of ls proves me wrong. >> >> Can you also report the output of "ls (hd1,msdos1)" to check what GRUB >> sees of the partition on the card ? > > It gives the partitioning description, UUID, and label of the USB flash > drive that was plugged in. It is FAT formatted and used to exchange > information with my Windows machine. USB drive ? Then (hd1) is not the SD card ? If you boot with no USB drive plugged in, there is no (hd1), right ? Then the SD card does not appear as a usable device for GRUB and my twisted theory may still be correct after all. >>> Any suggested reading on the "BASH like shell" I just used? >> >> The GRUB manual at <https://www.gnu.org/software/grub/manual/grub.html> > > It was what prompted me to ask ;/ Sorry, I do not know any better documentation.
[toc] | [prev] | [next] | [standalone]
| From | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| Date | 2017-04-13 19:40 +0200 |
| Message-ID | <tvQSS-6ep-29@gated-at.bofh.it> |
| In reply to | #180067 |
On 04/13/2017 10:48 AM, Pascal Hambourg wrote: > Le 13/04/2017 à 13:40, Richard Owlett a écrit : >> On 04/12/2017 02:03 PM, Pascal Hambourg wrote: >>> Le 12/04/2017 à 20:33, Richard Owlett a écrit : >>>> On 04/12/2017 12:13 PM, Pascal Hambourg wrote: >> >> [snip] >>>>> - 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. >>>> >>>> (hd0) (hd0, msdos9) (hd0, msdos8) (hd0, msdos7) (hd0, msdos6) >>>> (hd0, msdos5) (hd0, msdos1) (hd1) (hd1, msdos1) >>> >>> Some BIOS expose a removable media only when booting from it, so my >>> theory was that your BIOS did not expose the SD card and GRUB could >>> not see it. The result of ls proves me wrong. >>> >>> Can you also report the output of "ls (hd1,msdos1)" to check what GRUB >>> sees of the partition on the card ? >> >> It gives the partitioning description, UUID, and label of the USB flash >> drive that was plugged in. It is FAT formatted and used to exchange >> information with my Windows machine. > > USB drive ? Then (hd1) is not the SD card ? If you boot with no USB > drive plugged in, there is no (hd1), right ? Correct on all counts. IIUC the SD card slot is connected to a USB hub. When not the booted system, it automatically mounted in the same apparent manner as a USB flash drive. > Then the SD card does not > appear as a usable device for GRUB and my twisted theory may still be > correct after all. > >>>> Any suggested reading on the "BASH like shell" I just used? >>> >>> The GRUB manual at <https://www.gnu.org/software/grub/manual/grub.html> >> >> It was what prompted me to ask ;/ > > Sorry, I do not know any better documentation. > >
[toc] | [prev] | [next] | [standalone]
| From | Pascal Hambourg <pascal@plouf.fr.eu.org> |
|---|---|
| Date | 2017-04-13 20:10 +0200 |
| Message-ID | <tvRlT-6FZ-1@gated-at.bofh.it> |
| In reply to | #180092 |
Le 13/04/2017 à 19:33, Richard Owlett a écrit : > On 04/13/2017 10:48 AM, Pascal Hambourg wrote: >> >> USB drive ? Then (hd1) is not the SD card ? If you boot with no USB >> drive plugged in, there is no (hd1), right ? > > Correct on all counts. IIUC the SD card slot is connected to a USB hub. > When not the booted system, it automatically mounted in the same > apparent manner as a USB flash drive. I don't think so, because it appears as /dev/mmcblk0 in grub.cfg, i.e. a MMC/SD card. A USB mass storage device would appear as /dev/sdb or so. >> Then the SD card does not >> appear as a usable device for GRUB and my twisted theory may still be >> correct after all. Ok then, here is my full theory. You're not going to like it. We now know that the BIOS does not expose the SD card so GRUB cannot see it and the search command fails and prints the error message. But then how does the system on the SD card boot ? The purpose of the search command is to set the $root variable value with the device havind the searched UUID. As it fails, the variable remains unmodified and keeps its previous value. The menu entry does not set a default value for $root (which is rather unusual in my experience), so the current value comes from a previous assignement in grub.cfg. It's probably the root device of the system owning GRUB on the hard disk drive. (In GRUB's shell, you can print the $root value with the "set" command, and check that this partition contains a /boot/grub/vmlinuz-3.16.0-4-686-pae file directory with the command "ls /boot/grub".) GRUB uses $root as a default device used in paths which do not specify a device, such as the ones in the linux and initrd commands of the menu entry. By chance, it seems that this location contains the same kernel as the one on the SD card, so GRUB can load and boot it from the hard disk drive. But GRUB passes the SD card partition as the root device root=/dev/mmcblk0p1 to the kernel command line, so the kernel comes from the disk and the root filesystem comes from the SD card. Unlike GRUB, the kernel does not rely on the BIOS to access the SD card. David is right : you don't really boot from the SD card. GRUB is on the HDD. The kernel is on the HDD. Only the root filesystem is on the SD card.
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-04-14 01:20 +0200 |
| Message-ID | <tvWbT-1xv-1@gated-at.bofh.it> |
| In reply to | #180098 |
On Thu 13 Apr 2017 at 20:05:22 +0200, Pascal Hambourg wrote: > David is right : you don't really boot from the SD card. The OP never claimed he was booting from the SD card. He particularly said he did not install GRUB to the card. > GRUB is on the HDD. The kernel is on the HDD. Only the root filesystem is on > the SD card. Yes. That's what the linux line says too. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| Date | 2017-04-14 19:10 +0200 |
| Message-ID | <twcTo-3LV-23@gated-at.bofh.it> |
| In reply to | #180110 |
On 04/13/2017 05:55 PM, Brian wrote:
> On Thu 13 Apr 2017 at 20:05:22 +0200, Pascal Hambourg wrote:
>
>> David is right : you don't really boot from the SD card.
>
> The OP never claimed he was booting from the SD card. He particularly
> said he did not install GRUB to the card.
>
>> GRUB is on the HDD. The kernel is on the HDD. Only the root filesystem is on
>> the SD card.
>
> Yes. That's what the linux line says too.
>
I'll try to clarify some details.
My installation protocol.
1. I always use "Expert" as that way the installer will
do fewer things I'm not aware of.
2. I only install Grub the *first* time I do a Debian install.
By poor design Grub puts the current install first on menu.
When experimenting with configuration as I do, the least
likely install to be functional is the latest.
This requires me to run update-grub on the "good" install.
3. Similarly a swap partition is specified only on the first
install as the installer insists on destroying the UUID of
the existing swap partition. It is simpler to edit only the
fstab of latest install than to edit those for all other
installs each time.
4. All installs in this thread have been done using DVD 1 of
13 of Debian 8.6.0 - thus all intrinsically use the same
kernel.
I've done some additional observations and test installs.
1. The BIOS of the Lenovo T510 can be directed to boot from
the CD/DVD drive, hard disk, or any attached USB flash
drive. It *cannot* be directed to boot from the SD card.
2. I did an install to a USB flash drive including installing
Grub2 to the MBR of that flash drive. When selecting the
SD card from the grub menu I see nothing different.
3. I did a new install to the SD card specifying a different set
of packages and installing grub to the MBR of the SD card.
Once again no behavioral difference.
Does any of this justify a bug report. Especially as I do not
have the bandwidth to do a netinstall of a pre-release version?
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-04-14 20:40 +0200 |
| Message-ID | <tweiu-4wE-11@gated-at.bofh.it> |
| In reply to | #180136 |
On Fri 14 Apr 2017 at 12:05:38 -0500, Richard Owlett wrote: > On 04/13/2017 05:55 PM, Brian wrote: > >On Thu 13 Apr 2017 at 20:05:22 +0200, Pascal Hambourg wrote: > > > >>David is right : you don't really boot from the SD card. > > > >The OP never claimed he was booting from the SD card. He particularly > >said he did not install GRUB to the card. > > > >>GRUB is on the HDD. The kernel is on the HDD. Only the root filesystem is on > >>the SD card. > > > >Yes. That's what the linux line says too. > > I'll try to clarify some details. Your previous descriptions were good; clarification cannot do any harm. > My installation protocol. > 1. I always use "Expert" as that way the installer will > do fewer things I'm not aware of. Very wise. If you are familiar with each stage of the installation you can more more easily spot anomalies. "Expert"=="more control". > 2. I only install Grub the *first* time I do a Debian install. > By poor design Grub puts the current install first on menu. > When experimenting with configuration as I do, the least > likely install to be functional is the latest. > This requires me to run update-grub on the "good" install. That's ok. I tend to be more promiscuous; usually on a whim, like wanting to put a particular entry at the top of GRUB's menu list. When you do 'update-grub' do you still get no "set root=" line for the SD card in the grub.cfg? > 3. Similarly a swap partition is specified only on the first > install as the installer insists on destroying the UUID of > the existing swap partition. It is simpler to edit only the > fstab of latest install than to edit those for all other > installs each time. That's ok too. I often don't bother with a swap partition. Some of my machines have less than 4 GB of disk space. I see space for packages as more important than swap space. > 4. All installs in this thread have been done using DVD 1 of > 13 of Debian 8.6.0 - thus all intrinsically use the same > kernel. Yes. > I've done some additional observations and test installs. > 1. The BIOS of the Lenovo T510 can be directed to boot from > the CD/DVD drive, hard disk, or any attached USB flash > drive. It *cannot* be directed to boot from the SD card. I'm at a disadvantage here. I do not have an SD card. I do not have a USB hub. However, I thought USB sticks and SD cards were the same (or at least similar) when it came to booting. > 2. I did an install to a USB flash drive including installing > Grub2 to the MBR of that flash drive. When selecting the > SD card from the grub menu I see nothing different. Does that not substantiate what I said just now? > 3. I did a new install to the SD card specifying a different set > of packages and installing grub to the MBR of the SD card. > Once again no behavioral difference. I cannot believe your install to the card would be capable of criticism. > Does any of this justify a bug report. Especially as I do not > have the bandwidth to do a netinstall of a pre-release version? I mentioned "bug" in another mail. I wish I hadn't. It is not that bugs in GRUB or the Debian grub package do not arise, but I'd want to know more about SD cards before committing myself. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| Date | 2017-04-15 18:40 +0200 |
| Message-ID | <twyTT-sm-5@gated-at.bofh.it> |
| In reply to | #180140 |
On 04/14/2017 01:19 PM, Brian wrote: > [snip] > >> 2. I only install Grub the *first* time I do a Debian install. >> By poor design Grub puts the current install first on menu. >> When experimenting with configuration as I do, the least >> likely install to be functional is the latest. >> This requires me to run update-grub on the "good" install. > > That's ok. I tend to be more promiscuous; usually on a whim, like > wanting to put a particular entry at the top of GRUB's menu list. > > When you do 'update-grub' do you still get no "set root=" line for the > SD card in the grub.cfg? > [snip] I don't know how many times I've *MIS*read that last sentence ;< Mentally I was correcting non-existent typos, thus totally garbling it. I just spent several hours wandering thru grub files and loosely related documentation. I've ended up at www.gnu.org/software/grub/manual/grub.html#Multi_002dboot-manual-config which says "Currently autogenerating config files for multi-boot environments depends on os-prober and has several shortcomings. ..." I also discovered there that placing a customized grub in its own partition is not only possible, but recommended in some situations. I had read somewhere that that option had expired with grub-legacy. That, although taking much time to understand, will solve a *MESS* of grub problems for me ;/
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-04-15 20:10 +0200 |
| Message-ID | <twAiZ-1r9-1@gated-at.bofh.it> |
| In reply to | #180162 |
On Sat 15 Apr 2017 at 11:35:14 -0500, Richard Owlett wrote: > On 04/14/2017 01:19 PM, Brian wrote: > >[snip] > > > >> 2. I only install Grub the *first* time I do a Debian install. > >> By poor design Grub puts the current install first on menu. > >> When experimenting with configuration as I do, the least > >> likely install to be functional is the latest. > >> This requires me to run update-grub on the "good" install. > > > >That's ok. I tend to be more promiscuous; usually on a whim, like > >wanting to put a particular entry at the top of GRUB's menu list. > > > >When you do 'update-grub' do you still get no "set root=" line for the > >SD card in the grub.cfg? > >[snip] > > I don't know how many times I've *MIS*read that last sentence ;< > Mentally I was correcting non-existent typos, thus totally garbling it. > I just spent several hours wandering thru grub files and loosely related > documentation. > I've ended up at > www.gnu.org/software/grub/manual/grub.html#Multi_002dboot-manual-config > which says "Currently autogenerating config files for multi-boot > environments depends on os-prober and has several shortcomings. ..." > I also discovered there that placing a customized grub in its own partition > is not only possible, but recommended in some situations. I had read > somewhere that that option had expired with grub-legacy. That, although > taking much time to understand, will solve a *MESS* of grub problems for me > ;/ Treading GRUB's byways isn't for me today. Your only problem as far as I am concerned is the one expressed in your first post. Even that is of no great consequence and the visibilty of the message is easily dealt with in a custom GRUB stanza. Adopt the pragmatic approach. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | songbird <songbird@anthive.com> |
|---|---|
| Date | 2017-04-15 20:20 +0200 |
| Message-ID | <twAsF-1uC-1@gated-at.bofh.it> |
| In reply to | #180162 |
Richard Owlett wrote: ... > I don't know how many times I've *MIS*read that last sentence ;< > Mentally I was correcting non-existent typos, thus totally garbling it. > I just spent several hours wandering thru grub files and loosely related > documentation. > I've ended up at > www.gnu.org/software/grub/manual/grub.html#Multi_002dboot-manual-config > which says "Currently autogenerating config files for multi-boot > environments depends on os-prober and has several shortcomings. ..." > I also discovered there that placing a customized grub in its own > partition is not only possible, but recommended in some situations. I > had read somewhere that that option had expired with grub-legacy. That, > although taking much time to understand, will solve a *MESS* of grub > problems for me ;/ i hope so. :) for me the conceptual trouble started ages ago when i thought that "update-grub" and os-prober would go out and find all the other little grubs and get them all in sync. my most recent round of grubismo dealing with the USB stick educated me a little about that misconception and helped me figure out the custom menu entry and chain loading. as usual, i still have much to learn... songbird
[toc] | [prev] | [next] | [standalone]
| From | Felix Miata <mrmazda@earthlink.net> |
|---|---|
| Date | 2017-04-15 21:00 +0200 |
| Subject | Re: customized Grub (was: Possibly erroneous "device not present...) |
| Message-ID | <twB5n-1Jn-3@gated-at.bofh.it> |
| In reply to | #180162 |
Richard Owlett composed on 2017-04-15 11:35 (UTC-0500): ... > I also discovered there that placing a customized grub in its own > partition is not only possible, but recommended in some situations. > I had read somewhere that that option had expired with grub-legacy. That, > although taking much time to understand, will solve a *MESS* of grub > problems for me ;/ If control is what you want on BIOS disks, limit the action of Grub scripts to / filesystems. Let them do whatever they want, but don't bother using them. Install generic MBR code, put Grub Legacy on an active primary partition, never mount it to /boot, and boot using Grub stanzas you build yourself. At least, that's how I've been doing it for over a decade on more than 25 multiboot machines with as many as 30+ distros each, including on a few systems that include Windows 98, XP, 7, 8 or 10. For this purpose, openSUSE's Grub Legacy, in conjunction with Gfxboot, works best. It facilitates editing on the fly at runtime, which makes it very easy to correct any typos made during manual editing of menu.lst. Trying to use Debian's Grub Legacy is a handicap in that its find command hangs on EXT4 filesystems, limiting utility of its shell. Creating symlinks to current kernels and initrds leaves little editing to be required of the master bootloader's menu.lst. https://www.gnu.org/software/grub/manual/legacy/ When the point is reached that Grub Legacy cannot any more boot an installation I expect I'll try Syslinux or anything else that happens to provide promise as a bootloader before considering Grub2 for anything more than learning exercises. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-04-15 21:20 +0200 |
| Subject | Re: customized Grub (was: Possibly erroneous "device not present...) |
| Message-ID | <twBoJ-28z-1@gated-at.bofh.it> |
| In reply to | #180176 |
On Sat 15 Apr 2017 at 14:55:04 -0400, Felix Miata wrote: > Richard Owlett composed on 2017-04-15 11:35 (UTC-0500): > ... > >I also discovered there that placing a customized grub in its own > >partition is not only possible, but recommended in some situations. > I had read somewhere that that option had expired with grub-legacy. That, > >although taking much time to understand, will solve a *MESS* of grub > >problems for me ;/ > > If control is what you want on BIOS disks, limit the action of Grub scripts > to / filesystems. Let them do whatever they want, but don't bother using > them. Install generic MBR code, put Grub Legacy on an active primary > partition, never mount it to /boot, and boot using Grub stanzas you build > yourself. At least, that's how I've been doing it for over a decade on more > than 25 multiboot machines with as many as 30+ distros each, including on a > few systems that include Windows 98, XP, 7, 8 or 10. For this purpose, > openSUSE's Grub Legacy, in conjunction with Gfxboot, works best. It > facilitates editing on the fly at runtime, which makes it very easy to > correct any typos made during manual editing of menu.lst. Trying to use > Debian's Grub Legacy is a handicap in that its find command hangs on EXT4 > filesystems, limiting utility of its shell. > > Creating symlinks to current kernels and initrds leaves little editing to be > required of the master bootloader's menu.lst. > > https://www.gnu.org/software/grub/manual/legacy/ > > When the point is reached that Grub Legacy cannot any more boot an > installation I expect I'll try Syslinux or anything else that happens to > provide promise as a bootloader before considering Grub2 for anything more > than learning exercises. Do you have a clue what this thread is about? Or did you just fancy that a Legacy GRUB driveby posting would perk things up for everyone? -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| Date | 2017-04-15 22:40 +0200 |
| Subject | Re: customized Grub |
| Message-ID | <twCEa-2Qt-1@gated-at.bofh.it> |
| In reply to | #180178 |
On 04/15/2017 02:16 PM, Brian wrote: > On Sat 15 Apr 2017 at 14:55:04 -0400, Felix Miata wrote: >[snip] > > Do you have a clue what this thread is about? Or did you just > fancy that a Legacy GRUB driveby posting would perk things up > for everyone? > Careful ;) By my measurements you post 3 times for every time Felix has since 8/2015. Basically I agree with his post. As to selecting between Grub2 and Grub-legacy I choose a different primary criterion than what he chooses. His criterion is apparently a function of maintainability and reliability. If asked to state *MY* criterion, it would likely reduce to "who won popcon?" ;/ To put things in perspective, "Why chose Debian over MS/Apple/Canonical/etc ?" Debian allows/encourages choice!
[toc] | [prev] | [next] | [standalone]
| From | Curt <curty@free.fr> |
|---|---|
| Date | 2017-04-16 11:40 +0200 |
| Subject | Re: customized Grub |
| Message-ID | <twOOZ-1Zt-5@gated-at.bofh.it> |
| In reply to | #180182 |
On 2017-04-15, Richard Owlett <rowlett@cloud85.net> wrote: >> >> Do you have a clue what this thread is about? Or did you just >> fancy that a Legacy GRUB driveby posting would perk things up >> for everyone? >> > > Careful ;) > By my measurements you post 3 times for every time Felix has > since 8/2015. And you about two times both of them put together (without the redeeming quality of munificence). > Basically I agree with his post. I like my steak rare.
[toc] | [prev] | [next] | [standalone]
Page 1 of 6 [1] 2 3 4 5 6 Next page →
Back to top | Article view | linux.debian.user
csiph-web