View previous topic :: View next topic |
Author |
Message |
virtguru Tux's lil' helper
Joined: 14 Aug 2010 Posts: 148 Location: The Greatest Country in the World
|
Posted: Wed Jul 19, 2017 8:14 am Post subject: v86d removal in a month #606154 |
|
|
hey just noticed that v86d is being removed in a month no maintainer most likely due to #606154
So what options do nvidia users have that rely on this running some older stuff ? |
|
Back to top |
|
|
ExecutorElassus Veteran
Joined: 11 Mar 2004 Posts: 1435 Location: Berlin, Germany
|
Posted: Wed Jul 19, 2017 8:41 am Post subject: |
|
|
or, for that matter, I get the following error on kernel compilation:
Code: | # make -j9 && make -j9 modules_install
CHK include/config/kernel.release
CHK include/generated/uapi/linux/version.h
CHK scripts/mod/devicetable-offsets.h
CHK include/generated/utsrelease.h
CHK include/generated/timeconst.h
CHK include/generated/bounds.h
CHK include/generated/asm-offsets.h
CALL scripts/checksyscalls.sh
./scripts/gen_initramfs_list.sh: Cannot open '/usr/share/v86d/initramfs'
make[1]: *** [usr/Makefile:55: usr/initramfs_data.cpio.gz] Error 1
make: *** [Makefile:1016: usr] Error 2
make: *** Waiting for unfinished jobs....
|
I think that's a holdover from NeddySeagoon's instructions for migrating udev a few years back, but I'm not sure how to update it. Any suggestions?
Cheers,
EE |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54096 Location: 56N 3W
|
Posted: Wed Jul 19, 2017 8:58 am Post subject: |
|
|
ExecutorElassus,
v86d is used by the uvesafb driver on 64 bit systems.
v86d going away is going to break uvesafb, which is popular with nvidia-drivers users for a framebuffer console.
It will not interfere with nvidia-drivers working as intended and it not related to udev.
For several years now nvidia-drivers has issued dire warnings about the use of framebuffer consoles not being supported but in practice, providing the framebuffer does not take control of the GPU, it seems to work.
With uvesafb no longer available, VESA framebuffer, Simple Framebuffer or for UEFI users, EFI Framebuffer are possible replacements. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
ExecutorElassus Veteran
Joined: 11 Mar 2004 Posts: 1435 Location: Berlin, Germany
|
Posted: Wed Jul 19, 2017 9:08 am Post subject: |
|
|
Hi Neddy,
thanks for your reply. Do VESA framebuffer, Simple framebuffer, and or the EFI framebuffer provide for a high-resolution console during bootup? Maybe I'm just ignorant, but as far as I can tell that's the only thing I have it for.
Second, what about that failure in generating the initramfs? Is that part of the udev migration tutorial you posted a few years back? Is there an alternative to generating the initramfs that doesn't depend on v86d.
Cheers,
EE |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54096 Location: 56N 3W
|
Posted: Wed Jul 19, 2017 9:34 am Post subject: |
|
|
ExecutorElassus,
I don't have any UEFI equipment to practice on.
Simple framebuffer needs something to set it up before its used, the kernel uses whatever it finds. I've not tried it on AMD/Intel hardware but it on a Raspberry Pi it does 1920x1080, which is as good as it gets on a Pi. There, its set up by the boot loader.
vesafb only supports vesa modes. You pass parameters to it in the normal way. See the handbook.
What that means depends on your hardware.
I guess that v86d is a part of the user space that gives the uvesa driver its name. Being userspace, it goes into the initrd, so making the initrd fails. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
ExecutorElassus Veteran
Joined: 11 Mar 2004 Posts: 1435 Location: Berlin, Germany
|
Posted: Wed Jul 19, 2017 10:45 am Post subject: |
|
|
Hi Neddy,
so, in this case (using proprietary nVidia drivers) I would/should have the following lines in my grub.cfg file:
Code: |
# Use simpleFB
video=simplefb
# Set resolution and color depth
GRUB_GFXMODE=1920x1200x32
# Keep resolution when loading the kernel
GRUB_GFXPAYLOAD_LINUX=keep
|
To allow the kernel to compile the initramfs, should I change the framebuffer support to simplefb in the kernel config? Or is there some other place to do that?
Cheers,
EE |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54096 Location: 56N 3W
|
Posted: Wed Jul 19, 2017 10:59 am Post subject: |
|
|
ExecutorElassus,
You will need to change the kernel from uvesa to simple but I don't know how to set it up on AMD/Intel.
I don't use grub2 either. My bootloader just works, so I don't see any reason to upgrade it. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
swimmer Veteran
Joined: 15 Jul 2002 Posts: 1330 Location: Netherlands
|
Posted: Wed Jul 19, 2017 4:20 pm Post subject: |
|
|
Hi, I also noticed that v86d will go away soon and I started to play around with the options mentioned above. At the end I stuck with the simplest solution for my setup (which is syslinux and NO UEFI): using vesafb with in the kernel cmdline gives me a solid 1600x1200 resolution in the console. :happy:
HTH
swimmer |
|
Back to top |
|
|
Shibotto Apprentice
Joined: 19 Jun 2015 Posts: 155 Location: CET/CEST
|
Posted: Mon Jul 24, 2017 8:44 am Post subject: |
|
|
My hardware: Sony Vaio VPCS11E7E, Nvidia 310M with legacy proprietary driver, so no nvidia-modeset.
Without v86d/uvesafb after X starts I can't use TTYs anymore, so this deprecation is seriously a problem for me. What happens if I ctrl+alt+f1 from a X session is fairly odd, but to summarize the screen strongly flashes and gradually dims to lowest brightness, instead of a TTY prompt I get a black/gray corrupted pattern. I can write in it and it works, although I can't see a thing, and I can even go back to X without a problem.
This was not a regression at some point, it has been acting like this since I bought it in 2010. I always thought (maybe I am wrong?) these strong flashes could damage my screen in the long term, so I was happy when I found uvesafb. Can you suggest me other framebuffers that could solve this problem? I would be glad to test them, though I need time as it heavily breaks my workflow. |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54096 Location: 56N 3W
|
Posted: Mon Jul 24, 2017 9:45 am Post subject: |
|
|
Shibotto,
When my system was new, in 2009, I used nvidia-drivers with vesafb (no u) underneath.
Once nvidia-drivers dropped support for my card, I switched to nouveau.
vesafb only supports the vesa modes that your video card knows about.
Wide screen modes (other than 4:3) were added to the vesa standard rather late in the day, so it may not be a good fit for your screen. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
Shibotto Apprentice
Joined: 19 Jun 2015 Posts: 155 Location: CET/CEST
|
Posted: Wed Aug 02, 2017 8:02 am Post subject: |
|
|
NeddySeagoon wrote: | Shibotto,
When my system was new, in 2009, I used nvidia-drivers with vesafb (no u) underneath.
Once nvidia-drivers dropped support for my card, I switched to nouveau.
vesafb only supports the vesa modes that your video card knows about.
Wide screen modes (other than 4:3) were added to the vesa standard rather late in the day, so it may not be a good fit for your screen. |
I tried vesafb on another distro, in order not to break my Gentoo, but same result. Right now widescreen or resolution in general is my last concern, I would be happy just to see the TTYs. I know with nouveau things work, but I'd rather delay that as much as possible, since it halves my battery life. |
|
Back to top |
|
|
ExecutorElassus Veteran
Joined: 11 Mar 2004 Posts: 1435 Location: Berlin, Germany
|
Posted: Thu Aug 03, 2017 6:43 pm Post subject: |
|
|
Update: it turns out the lines of code I posted previously are supposed to go in /etc/default/grub, and used by grub2-mkconfig to build /boot/grub/grub.cfg. However, I have never been able to get this method to work for my setup (I have / on a vg, and all my other subdirectories including /usr and /var are also on volume groups inside a RAID array). grub2-mkconfig consistently misidentifies the root, and then can't boot.
On the side, is there a way to fix this?
But back to the matter at hand: what is the syntax for editing /boot/grub/grub.cfg directly to include the correct framebuffer settings? Or rather, what lines would I have in there so that the console doesn't revert to some ugly 800x600 default when booting?
Cheers,
EE |
|
Back to top |
|
|
Shibotto Apprentice
Joined: 19 Jun 2015 Posts: 155 Location: CET/CEST
|
Posted: Sat Aug 12, 2017 5:36 pm Post subject: |
|
|
Is there an alternative daemon to v86d for uvesafb? I don't really mind about the resolution, I just want my TTYs. |
|
Back to top |
|
|
JohnBlbec Guru
Joined: 08 Feb 2003 Posts: 306
|
Posted: Sun Aug 20, 2017 2:47 pm Post subject: |
|
|
i'm not happy reading a resolution to remove v86d as i haven't found a solution how to replace uvesafb for old nvidia. v86d was buggy, yes, but it provides me a good resolution in my console and i haven't been expecting more. i'd rather use buggy v86d because i can't work w/o it :-( |
|
Back to top |
|
|
DaggyStyle Watchman
Joined: 22 Mar 2006 Posts: 5909
|
Posted: Tue Dec 19, 2017 6:54 pm Post subject: |
|
|
Greetings,
I'm using v86d and uvesafb as part of my project in conjunction with fbcondecor, after v86d will be removed, I assume that uvesafb will follow soon.
from this thread I understand that vesafb should work, in that case, how can I replace uvesafb with vesafb? _________________ Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein |
|
Back to top |
|
|
DaggyStyle Watchman
Joined: 22 Mar 2006 Posts: 5909
|
Posted: Thu Dec 28, 2017 3:35 pm Post subject: |
|
|
got it to work, did the same as said in the tutorial, disabled uvesafb, made sure vesafb ad sysfb are disabled.
removed v86d, added the correct resolution via gurb using vga and it worked. _________________ Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein |
|
Back to top |
|
|
virtguru Tux's lil' helper
Joined: 14 Aug 2010 Posts: 148 Location: The Greatest Country in the World
|
Posted: Sat Dec 30, 2017 9:27 pm Post subject: |
|
|
DaggyStyle wrote: | got it to work, did the same as said in the tutorial, disabled uvesafb, made sure vesafb ad sysfb are disabled.
removed v86d, added the correct resolution via gurb using vga and it worked. |
hey Daggystyle , Ive tried this and still cannot get a decent tty resolution. Would you share your config ? Also which tutorial were you following ?
Thanks. |
|
Back to top |
|
|
hurricane Tux's lil' helper
Joined: 15 Jul 2004 Posts: 107
|
Posted: Tue Jan 09, 2018 3:12 am Post subject: Oh boy, what a mess. |
|
|
I have a 2560×1440 display, and obviously want to use it too.
It seems there is no mode above 1600×1200 (or 1600×900 for 16:9) available for my GTX 295. :/
And I can’t use nouveau, because the developers don’t know how to set the fan on a dual GPU card with just one fan, and so the fan is always much louder than with the nvidia driver. (I would have to send the card to them. Which I may, if I replace it some day. But until then … what do I do?) |
|
Back to top |
|
|
solamour l33t
Joined: 21 Dec 2004 Posts: 698 Location: San Diego, CA
|
|
Back to top |
|
|
virtguru Tux's lil' helper
Joined: 14 Aug 2010 Posts: 148 Location: The Greatest Country in the World
|
Posted: Wed Jan 17, 2018 7:15 pm Post subject: |
|
|
solamour , unfortunately no.
For some reason grub hangs at black screen if I edit the options in /etc/default/grub and rebuild grub.cfg
GRUB_GFXMODE=1920x1080x32
GRUB_GFXPAYLOAD_LINUX=keep |
|
Back to top |
|
|
solamour l33t
Joined: 21 Dec 2004 Posts: 698 Location: San Diego, CA
|
Posted: Wed Jan 17, 2018 8:24 pm Post subject: |
|
|
virtguru wrote: | solamour , unfortunately no.
For some reason grub hangs at black screen if I edit the options in /etc/default/grub and rebuild grub.cfg
GRUB_GFXMODE=1920x1080x32
GRUB_GFXPAYLOAD_LINUX=keep |
What I ended up doing was to replaced all the settings described in https://wiki.gentoo.org/wiki/Uvesafb (i.e. "Userspace VESA VGA graphics support", "Initramfs source file(s)", "video=uvesafb:1024x768-32,mtrr:3,ywrap", etc.) with the following.
Code: | Device Drivers
Graphics support
Frame buffer Devices
AMD Geode family framebuffer support (FB_GEODE)
# Need to be in-kernel (not module) to see penguin.
AMD Geode LX framebuffer support (FB_GEODE_LX)
GRUB_CMDLINE_LINUX_DEFAULT="video=lxfb:800x600-32"
|
I used "FB_GEODE_LX", simply because that's what I have. If you have an AMD/NVIDEA/Intel graphic card, I think Direct Rendering Manager (https://wiki.gentoo.org/wiki/Framebuffer) would be a better choice.
I have another machine whose graphic card was not listed in "Device Drivers -> Graphics support -> Frame buffer Devices" section, so I used VESA instead.
Code: | Device Drivers
Graphics support
Frame buffer Devices
VESA VGA graphics support (FB_VESA)
GRUB_GFXMODE=800x600x32
GRUB_GFXPAYLOAD_LINUX=keep
|
__
sol |
|
Back to top |
|
|
DaggyStyle Watchman
Joined: 22 Mar 2006 Posts: 5909
|
Posted: Sat Jan 20, 2018 2:10 pm Post subject: |
|
|
virtguru wrote: | DaggyStyle wrote: | got it to work, did the same as said in the tutorial, disabled uvesafb, made sure vesafb ad sysfb are disabled.
removed v86d, added the correct resolution via gurb using vga and it worked. |
hey Daggystyle , Ive tried this and still cannot get a decent tty resolution. Would you share your config ? Also which tutorial were you following ?
Thanks. |
do you see vesafb print in dmesg? try passing ask via grub and select the proper mode. _________________ Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein |
|
Back to top |
|
|
MaDDeePee Guru
Joined: 18 Aug 2004 Posts: 386 Location: Germany
|
Posted: Thu Mar 29, 2018 4:23 pm Post subject: |
|
|
I'm stuck with this, too.
i was runnging 2x gtx 1070 with initramfs and uvesafb.
what way should i go now? |
|
Back to top |
|
|
solamour l33t
Joined: 21 Dec 2004 Posts: 698 Location: San Diego, CA
|
Posted: Wed May 30, 2018 7:43 pm Post subject: |
|
|
MaDDeePee wrote: | I'm stuck with this, too.
i was runnging 2x gtx 1070 with initramfs and uvesafb.
what way should i go now? |
Have you figured out using Framebuffer with GTX 1070? I don't have any graphic cards manufactured in the last few years, but I've always thought using either "x11-drivers/xf86-video-nouveau" or "x11-drivers/nvidia-drivers" would be enough.
__
sol |
|
Back to top |
|
|
MaDDeePee Guru
Joined: 18 Aug 2004 Posts: 386 Location: Germany
|
Posted: Wed May 30, 2018 8:04 pm Post subject: |
|
|
solamour wrote: | MaDDeePee wrote: | I'm stuck with this, too.
i was runnging 2x gtx 1070 with initramfs and uvesafb.
what way should i go now? |
Have you figured out using Framebuffer with GTX 1070? I don't have any graphic cards manufactured in the last few years, but I've always thought using either "x11-drivers/xf86-video-nouveau" or "x11-drivers/nvidia-drivers" would be enough.
__
sol |
Hello,
yes - thanks.
https://forums.gentoo.org/viewtopic-t-1079196-highlight-.html |
|
Back to top |
|
|
|