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