Summary: | sys-kernel/genkernel-next-68 - ./scripts/gen_initramfs_list.sh: Cannot open '/usr/share/v86d/initramfs' | ||
---|---|---|---|
Product: | Gentoo Hosted Projects | Reporter: | Juergen Rose <rose> |
Component: | genkernel-next | Assignee: | Ettore Di Giacinto (RETIRED) <mudler> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | lxnay, tsmksubc |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Juergen Rose
2018-01-17 18:42:40 UTC
sys-apps/v86d has been removed from portage. see https://forums.gentoo.org/viewtopic-t-1066432.html?sid=1d7d9ee964b21aad269e5e58951be84f Regardless, it should only look for v86d if SPLASH is enabled (but not plymouth). Also people still using fbsplash will also most likely be using v86d from bug or overlay; although the wiki page implies v86d is only needed for uvesa (and not needed for intel/radeon/nvidia framebuffers) I'm not sure that's true, as I still saw errors during boot about "can't start /sbin/v86d..." So *if* we can get plymouth and genkernel-next cleaned up then maybe we can just drop support for fbsplash/v86d but that time isn't quite here yet. IMHO we should probably just add a fixed v86d back to the tree for now. Package removed. |