1 |
Andrew Savchenko <bircoph@g.o> wrote: |
2 |
|
3 |
> On Wed, 15 Jun 2016 09:41:07 -0400 covici@××××××××××.com wrote: |
4 |
> > Neil Bothwick <neil@××××××××××.uk> wrote: |
5 |
> > |
6 |
> > > On Wed, 15 Jun 2016 08:42:45 -0400, covici@××××××××××.com wrote: |
7 |
> > > |
8 |
> > > > > > But the manual and the html pages constantly talk about the grub |
9 |
> > > > > > command or rather the grub interactive command, and they usually |
10 |
> > > > > > call it grub, maybe it has a different name. |
11 |
> > > > > |
12 |
> > > > > That's the GRUB interactive shell, that you get to from the boot menu |
13 |
> > > > > (press c) or get dropped into it if there is no grub.cfg file. |
14 |
> > > > > |
15 |
> > > > |
16 |
> > > > hmmm, I thought you could do it from the console as well, for certain |
17 |
> > > > commands. |
18 |
> > > |
19 |
> > > The commands that show up in "qlist grub" can be run from a standard |
20 |
> > > shell. The GRUB interactive shell is different, with its own set of |
21 |
> > > commands. You really need to read the online manual or the info pages |
22 |
> > > again. The man pages explain the individual commands, but only the full |
23 |
> > > manual shows how it all fits together. |
24 |
> > > |
25 |
> > > Why are you looking to switch from Lilo to GRUB now? If Lilo works, stick |
26 |
> > > with it. If it is because you have EFI hardware, I'd skip GRUB and go |
27 |
> > > straight to Gummiboot or systemd-boot. |
28 |
> > |
29 |
> > Well, I am trying to use the nvidia driver which conflicts with uvesafb |
30 |
> > frame buffer, so it seems. It used to work fine, but not it does not |
31 |
> > work anymore and the only solutions I have found was a couple of grub |
32 |
> > parameters which gives you a higher resolution and passes it on to |
33 |
> > linux. It would not be as good as the uvesafb, but at least it would be |
34 |
> > better than 80x25. I use the console a lot and only use gnome |
35 |
> > sometimes, but I don't want to have to reboot into a different kernel |
36 |
> > just to use gnome. |
37 |
> |
38 |
> You can pass any kernel parameters using lilo as well. |
39 |
> |
40 |
> Also it should be possible to use uvesafb and nvidia driver without |
41 |
> kernel switch, at least this is possible with fbcon: as described |
42 |
> in [1], it is possible to unbind framebuffer console and use text |
43 |
> vga console, then you should be able to unload uvesafb module and |
44 |
> load nvidia propietary blob. |
45 |
> |
46 |
> [1] https://www.kernel.org/doc/Documentation/fb/fbcon.txt |
47 |
|
48 |
But, if I compile uvesafb as a module, as opposed to having it built |
49 |
into the kernel, I can never activate the frame buffer, I always get |
50 |
/dev/fb0 no such file or directory when trying to use fbset. If I could |
51 |
do that, and get the correct mode, that would also solve my problem. |
52 |
|
53 |
-- |
54 |
Your life is like a penny. You're going to lose it. The question is: |
55 |
How do |
56 |
you spend it? |
57 |
|
58 |
John Covici |
59 |
covici@××××××××××.com |