1 |
On Monday 19 Sep 2016 21:28:25 Mick wrote: |
2 |
> On Monday 19 Sep 2016 13:08:29 Mike Gilbert wrote: |
3 |
|
4 |
--->8 |
5 |
|
6 |
> > The manpage seems to be incorrect; -B/--delete-bootnum does not take |
7 |
> > any argument. Instead, you must specify the entry number using the -b |
8 |
> > option. |
9 |
|
10 |
Or you could say, with hindsight, that the man page is not strictly |
11 |
incorrect, as it doesn't say anything that isn't true. You just have to know |
12 |
how to interpret it before you start. :) |
13 |
|
14 |
> > Try this: |
15 |
> > |
16 |
> > efibootmgr -b 0001 -B |
17 |
|
18 |
That worked a treat - many thanks. Except for this little wrinkle, which I |
19 |
hope is harmless: |
20 |
|
21 |
# efibootmgr -b 0000 -B |
22 |
BootCurrent: 0002 |
23 |
Timeout: 1 seconds |
24 |
No BootOrder is set; firmware will attempt recovery |
25 |
Boot0002* Linux Boot Manager |
26 |
Boot0008 CD/DVD Drive |
27 |
Boot0010* UEFI OS |
28 |
|
29 |
> I recall having a similar problem and this worked last time I tried: |
30 |
> |
31 |
> efibootmgr -b 0002 --delete-bootnum Boot0002 |
32 |
> |
33 |
> where: |
34 |
> |
35 |
> -b 002 |
36 |
> |
37 |
> is the entry I want to modify. |
38 |
> |
39 |
> --delete-bootnum Boot0002 |
40 |
> |
41 |
> is what I want to do to it. I don't remember if specifying "Boot0002" was |
42 |
> necessary, but it worked all the same. I guess you can try first: |
43 |
> |
44 |
> |
45 |
> efibootmgr -b 0001 -B |
46 |
> |
47 |
> as already suggested and see if this does it. Also, before I delete a |
48 |
> boot stub entry, e.g. 0002, I change the boot order to make sure it is |
49 |
> not first: --bootorder 0003,0005,0010,0002 |
50 |
> |
51 |
> but I don't think it is necessary. |
52 |
|
53 |
Hah! Watch this: |
54 |
|
55 |
# efibootmgr --bootorder 0002,0010,0008 |
56 |
Could not set BootOrder: No space left on device |
57 |
|
58 |
I'll do a bit more poking around. |
59 |
|
60 |
-- |
61 |
Rgds |
62 |
Peter |