1 |
Hello again, Peter. |
2 |
|
3 |
On Sat, Dec 31, 2022 at 15:47:01 +0000, Peter Humphrey wrote: |
4 |
> Hello Alan, |
5 |
> On Saturday, 31 December 2022 14:08:43 GMT you wrote: |
6 |
|
7 |
> > What I'm thinking here is that you might be installing a font which is |
8 |
> > bigger than the 8x16 standard that you appear to be booting with. To |
9 |
> > check this, would you please do: |
10 |
|
11 |
> > # file /lib/rc/console/font |
12 |
|
13 |
> > , which should return a message like: |
14 |
|
15 |
> > /lib/rc/console/font: Linux/i386 PC Screen Font v1 data, 256 characters, |
16 |
> > Unicode directory, 8x16 |
17 |
|
18 |
> > What is the size of this font, here (where it says 8x16 for my font)? |
19 |
> > The reason I ask is, I've got a horrible suspicion that one of the C |
20 |
> > functions which copies screen data when the screen size is changed can |
21 |
> > only copy to a same sized or (possibly) _bigger_ screen (i.e. with a |
22 |
> > smaller font). If this is indeed the case, it might explain why you're |
23 |
> > seeing a hang, here. |
24 |
|
25 |
> I think you've put your finger on it: |
26 |
|
27 |
> $ file /lib/rc/console/font |
28 |
> /lib/rc/console/font: Linux/i386 PC Screen Font v2 data, 256 characters, |
29 |
> Unicode directory, 22x11 |
30 |
|
31 |
> I use consolefont="ter-122n" from the terminus-font package. It's a long time |
32 |
> since I was able to read a high-resolution screen in its native resolution. |
33 |
|
34 |
> Is there some way I can get the UEFI BIOS to boot with that font, or a larger |
35 |
> one? Or perhaps let the system boot without setting a font and then changing |
36 |
> it later? |
37 |
|
38 |
Probably, but it would be better if I just fixed the bug(s) in my changes to |
39 |
the kernel. Changing font size is something one should be able to do. |
40 |
|
41 |
> Neither of those looks easy to do. I'd better have a good root through the |
42 |
> BIOS options to start with. |
43 |
|
44 |
A happy new year to you (and everybody else here), and give me somewhere |
45 |
between a few hours and a few days, and this bug should get fixed. |
46 |
|
47 |
Again, thanks for such effective testing! |
48 |
|
49 |
> -- |
50 |
> Regards, |
51 |
> Peter. |
52 |
|
53 |
-- |
54 |
Alan Mackenzie (Nuremberg, Germany). |