[Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
@tuxinvader @k3dar7 many thanks for the replies. Yes, I installed packages from mainline. Sorry, I thought this bug report is for mainline packages. Now I did see your PPA through AskUbuntu thread but is it just for "Focal" or from your PPA, I can install kernels in Hirsute too? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
@tuxinvader While trying to install Kernel 5.14.3 (Sep 12, 2021) on Ubuntu MATE 21.04, I ran into similar issue but for libc6 2.34. Error: dpkg: dependency problems prevent configuration of linux- headers-5.14.3-051403-generic: linux-headers-5.14.3-051403-generic depends on libc6 (>= 2.34); however: version of libc6:amd64 on system is 2.33-0ubuntu5. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906131] Re: No rule to make target 'scripts/module.lds' while building out-of-tree modules
Still getting errors with kernel 5.11 RC2 while building wireless driver modules. Though the quick fix still works as detailed in comment #8: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906131/comments/8 Error: 'make' -j12 KVER=5.11.0-051100rc2-generic KSRC=/lib/modules/5.11.0-051100rc2-generic/build...(bad exit status: 2) Error! Bad return status for module build on kernel: 5.11.0-051100rc2-generic (x86_64) Consult /var/lib/dkms/rtl88x2bu/git/build/make.log for more information. ...done. Make.log: DKMS make.log for rtl88x2bu-git for kernel 5.11.0-051100rc2-generic (x86_64) make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/5.11.0-051100rc2-generic/build M=/var/lib/dkms/rtl88x2bu/git/build modules make[1]: Entering directory '/usr/src/linux-headers-5.11.0-051100rc2-generic' CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_cmd.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_security.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_debug.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_io.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_ioctl_query.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_ioctl_set.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_ieee80211.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_mlme.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_mlme_ext.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_mi.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_wlan_util.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_vht.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_pwrctrl.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_rf.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_chplan.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_recv.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_sta_mgt.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_ap.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/mesh/rtw_mesh.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/mesh/rtw_mesh_pathtbl.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/mesh/rtw_mesh_hwmp.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_xmit.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_p2p.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_rson.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_tdls.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_br_ext.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_iol.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_sreset.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_btcoex_wifionly.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_btcoex.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_beamforming.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_odm.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_rm.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_rm_fsm.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_rm_util.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/efuse/rtw_efuse.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/osdep_service.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/os_intfs.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/usb_intf.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/usb_ops_linux.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/ioctl_linux.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/xmit_linux.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/mlme_linux.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/recv_linux.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/ioctl_cfg80211.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/rtw_cfgvendor.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/wifi_regd.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/rtw_android.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/rtw_proc.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/rtw_rhashtable.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/ioctl_mp.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/hal/hal_intf.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/hal/hal_com.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/hal/hal_com_phycfg.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/hal/hal_phy.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/hal/hal_dm.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/hal/hal_dm_acs.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/hal/hal_btcoex_wifionly.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/hal/hal_btcoex.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/hal/hal_mp.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/hal/hal_mcc.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/hal/hal_hci/hal_usb.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/hal/led/hal_led.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/hal/led/hal_usb_led.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/hal/rtl8822b/rtl8822b_halinit.o C
[Bug 1906072] Re: Out-of-tree modules no longer build since 596b0474d3d9 in 5.10-rc1
*** This bug is a duplicate of bug 1906131 *** https://bugs.launchpad.net/bugs/1906131 ** This bug has been marked a duplicate of bug 1906131 No rule to make target 'scripts/module.lds' while building out-of-tree modules -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906072 Title: Out-of-tree modules no longer build since 596b0474d3d9 in 5.10-rc1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1906072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906131] Re: No rule to make target 'scripts/module.lds' while building out-of-tree modules
If anyone come across this looking for a workaround, here's a quick fix I've found on a GitHub repo for RTL8192EU https://github.com/Mange/rtl8192eu-linux- driver/issues/205#issuecomment-736366347 sudo wget https://raw.githubusercontent.com/torvalds/linux/master/scripts/module.lds.S -O /usr/src/linux-headers-5.10.2-051002-generic/scripts/module.lds sudo sed -i '$ d' /usr/src/linux- headers-5.10.2-051002-generic/scripts/module.lds -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906131 Title: No rule to make target 'scripts/module.lds' while building out-of-tree modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906131] Re: No rule to make target 'scripts/module.lds' while building out-of-tree modules
Error-2 for RTL88x2BU: Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area... 'make' -j12 KVER=5.10.2-051002-generic KSRC=/lib/modules/5.10.2-051002-generic/build...(bad exit status: 2) Error! Bad return status for module build on kernel: 5.10.2-051002-generic (x86_64) Consult /var/lib/dkms/rtl88x2bu/git/build/make.log for more information. Make.log: DKMS make.log for rtl88x2bu-git for kernel 5.10.2-051002-generic (x86_64) make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/5.10.2-051002-generic/build M=/var/lib/dkms/rtl88x2bu/git/build modules make[1]: Entering directory '/usr/src/linux-headers-5.10.2-051002-generic' CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_cmd.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_security.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_debug.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_io.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_ioctl_query.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_ioctl_set.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_ieee80211.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_mlme.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_mlme_ext.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_mi.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_wlan_util.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_vht.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_pwrctrl.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_rf.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_chplan.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_recv.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_sta_mgt.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_ap.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/mesh/rtw_mesh.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/mesh/rtw_mesh_pathtbl.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/mesh/rtw_mesh_hwmp.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_xmit.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_p2p.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_rson.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_tdls.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_br_ext.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_iol.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_sreset.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_btcoex_wifionly.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_btcoex.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_beamforming.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_odm.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_rm.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_rm_fsm.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_rm_util.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/efuse/rtw_efuse.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/osdep_service.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/os_intfs.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/usb_intf.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/usb_ops_linux.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/ioctl_linux.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/xmit_linux.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/mlme_linux.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/recv_linux.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/ioctl_cfg80211.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/rtw_cfgvendor.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/wifi_regd.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/rtw_android.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/rtw_proc.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/rtw_rhashtable.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/ioctl_mp.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/hal/hal_intf.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/hal/hal_com.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/hal/hal_com_phycfg.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/hal/hal_phy.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/hal/hal_dm.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/hal/hal_dm_acs.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/hal/hal_btcoex_wifionly.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/hal/hal_btcoex.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/hal/hal_mp.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/hal/hal_mcc.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/hal/hal_hci/hal_usb.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/hal/led/hal_led.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/hal/led/hal_usb_led.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/hal/rtl8822b/rtl8822b_halinit.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/hal/rtl8822b/rtl8822b_mac.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/hal/rtl8822b/rtl8
[Bug 1906131] Re: No rule to make target 'scripts/module.lds' while building out-of-tree modules
I too am getting errors with kernel 5.10.2 while building wireless driver modules: /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 5.10.2-051002-generic Error-1 for RTL8192EU: Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area... 'make' all KVER=5.10.2-051002-generic.(bad exit status: 2) Error! Bad return status for module build on kernel: 5.10.2-051002-generic (x86_64) Consult /var/lib/dkms/rtl8192eu/1.0/build/make.log for more information. Make.log: DKMS make.log for rtl8192eu-1.0 for kernel 5.10.2-051002-generic (x86_64) make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/5.10.2-051002-generic/build M=/var/lib/dkms/rtl8192eu/1.0/build modules make[1]: Entering directory '/usr/src/linux-headers-5.10.2-051002-generic' CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_cmd.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_security.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_debug.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_io.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_ioctl_query.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_ioctl_set.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_ieee80211.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_mlme.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_mlme_ext.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_mi.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_wlan_util.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_vht.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_pwrctrl.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_rf.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_chplan.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_recv.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_sta_mgt.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_ap.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/mesh/rtw_mesh.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/mesh/rtw_mesh_pathtbl.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/mesh/rtw_mesh_hwmp.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_xmit.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_p2p.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_rson.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_tdls.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_br_ext.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_iol.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_sreset.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_btcoex_wifionly.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_btcoex.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_beamforming.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_odm.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_rm.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_rm_fsm.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/efuse/rtw_efuse.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/os_dep/osdep_service.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/os_dep/linux/os_intfs.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/os_dep/linux/usb_intf.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/os_dep/linux/usb_ops_linux.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/os_dep/linux/ioctl_linux.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/os_dep/linux/xmit_linux.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/os_dep/linux/mlme_linux.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/os_dep/linux/recv_linux.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/os_dep/linux/ioctl_cfg80211.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/os_dep/linux/rtw_cfgvendor.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/os_dep/linux/wifi_regd.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/os_dep/linux/rtw_android.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/os_dep/linux/rtw_proc.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/os_dep/linux/rtw_rhashtable.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/os_dep/linux/ioctl_mp.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/hal/hal_intf.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/hal/hal_com.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/hal/hal_com_phycfg.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/hal/hal_phy.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/hal/hal_dm.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/hal/hal_dm_acs.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/hal/hal_btcoex_wifionly.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/hal/hal_btcoex.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/hal/hal_mp.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/hal/hal_mcc.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/hal/hal_hci/hal_usb.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/hal/led/hal_led.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/hal/led/hal_usb_led.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/hal/HalPwrSeqCmd.o CC [M] /var/lib/dkms/
[Bug 1906131] Re: No rule to make target 'scripts/module.lds' while building out-of-tree modules
(2) Error and "make.log" for RTL8192EU: Building module fails on Kernel 5.10 RC6 in Ubuntu MATE Groovy 20.10 with the following error message: admn@um:~/Downloads$ git clone https://github.com/Mange/rtl8192eu-linux-driver; admn@um:~/Downloads$ cd rtl8192eu-linux-driver; admn@um:~/Downloads/rtl8192eu-linux-driver$ sudo dkms add .; Creating symlink /var/lib/dkms/rtl8192eu/1.0/source -> /usr/src/rtl8192eu-1.0 DKMS: add completed. admn@um:~/Downloads/rtl8192eu-linux-driver$ sudo dkms install rtl8192eu/1.0; Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area... 'make' all KVER=5.10.0-051000rc6-generic(bad exit status: 2) Error! Bad return status for module build on kernel: 5.10.0-051000rc6-generic (x86_64) Consult /var/lib/dkms/rtl8192eu/1.0/build/make.log for more information. admn@um:~/Downloads/rtl8192eu-linux-driver$ /var/lib/dkms/rtl8192eu/1.0/build/make.log DKMS make.log for rtl8192eu-1.0 for kernel 5.10.0-051000rc6-generic (x86_64) make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/5.10.0-051000rc6-generic/build M=/var/lib/dkms/rtl8192eu/1.0/build modules make[1]: Entering directory '/usr/src/linux-headers-5.10.0-051000rc6-generic' CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_cmd.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_security.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_debug.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_io.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_ioctl_query.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_ioctl_set.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_ieee80211.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_mlme.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_mlme_ext.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_mi.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_wlan_util.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_vht.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_pwrctrl.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_rf.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_chplan.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_recv.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_sta_mgt.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_ap.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/mesh/rtw_mesh.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/mesh/rtw_mesh_pathtbl.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/mesh/rtw_mesh_hwmp.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_xmit.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_p2p.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_rson.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_tdls.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_br_ext.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_iol.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_sreset.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_btcoex_wifionly.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_btcoex.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_beamforming.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_odm.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_rm.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/rtw_rm_fsm.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/core/efuse/rtw_efuse.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/os_dep/osdep_service.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/os_dep/linux/os_intfs.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/os_dep/linux/usb_intf.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/os_dep/linux/usb_ops_linux.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/os_dep/linux/ioctl_linux.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/os_dep/linux/xmit_linux.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/os_dep/linux/mlme_linux.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/os_dep/linux/recv_linux.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/os_dep/linux/ioctl_cfg80211.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/os_dep/linux/rtw_cfgvendor.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/os_dep/linux/wifi_regd.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/os_dep/linux/rtw_android.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/os_dep/linux/rtw_proc.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/os_dep/linux/rtw_rhashtable.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/os_dep/linux/ioctl_mp.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/hal/hal_intf.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/hal/hal_com.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/hal/hal_com_phycfg.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/hal/hal_phy.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/hal/hal_dm.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/hal/hal_dm_acs.o CC [M] /var/lib/dkms/rtl8192eu/1.0/build/hal/hal_btcoex_wifionly.o CC [M] /var/lib/dkms/rtl8192eu/1.0/
[Bug 1906131] Re: No rule to make target 'scripts/module.lds' while building out-of-tree modules
I too am getting the same error: make[3]: *** No rule to make target 'scripts/module.lds', needed by '/var/lib/dkms/rtl88x2bu/git/build/88x2bu.ko'. Stop., while trying to install wireless drivers for (1) RTL88x2BU and (2) RTL8192EU for Kernel 5.10 RC6 on Ubuntu MATE 20.10 (1) Error and "make.log" for RTL88x2BU: Building module fails on Kernel 5.10 RC6 in Ubuntu MATE Groovy 20.10 with the following error message: root@um:/usr/src/rtl88x2bu-git# sed -i 's/PACKAGE_VERSION="@PKGVER@"/PACKAGE_VERSION="git"/g' /usr/src/rtl88x2bu-git/dkms.conf root@um:/usr/src/rtl88x2bu-git# dkms add -m rtl88x2bu -v git Creating symlink /var/lib/dkms/rtl88x2bu/git/source -> /usr/src/rtl88x2bu-git DKMS: add completed. root@um:/usr/src/rtl88x2bu-git# dkms autoinstall Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area... 'make' -j12 KVER=5.10.0-051000rc6-generic KSRC=/lib/modules/5.10.0-051000rc6-generic/build..(bad exit status: 2) Error! Bad return status for module build on kernel: 5.10.0-051000rc6-generic (x86_64) Consult /var/lib/dkms/rtl88x2bu/git/build/make.log for more information. root@um:/usr/src/rtl88x2bu-git# /var/lib/dkms/rtl88x2bu/git/build/make.log DKMS make.log for rtl88x2bu-git for kernel 5.10.0-051000rc6-generic (x86_64) make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/5.10.0-051000rc6-generic/build M=/var/lib/dkms/rtl88x2bu/git/build modules make[1]: Entering directory '/usr/src/linux-headers-5.10.0-051000rc6-generic' CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_cmd.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_security.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_debug.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_io.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_ioctl_query.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_ioctl_set.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_ieee80211.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_mlme.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_mlme_ext.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_mi.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_wlan_util.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_vht.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_pwrctrl.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_rf.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_chplan.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_recv.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_sta_mgt.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_ap.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/mesh/rtw_mesh.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/mesh/rtw_mesh_pathtbl.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/mesh/rtw_mesh_hwmp.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_xmit.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_p2p.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_rson.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_tdls.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_br_ext.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_iol.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_sreset.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_btcoex_wifionly.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_btcoex.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_beamforming.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_odm.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_rm.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_rm_fsm.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/rtw_rm_util.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/core/efuse/rtw_efuse.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/osdep_service.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/os_intfs.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/usb_intf.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/usb_ops_linux.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/ioctl_linux.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/xmit_linux.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/mlme_linux.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/recv_linux.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/ioctl_cfg80211.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/rtw_cfgvendor.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/wifi_regd.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/rtw_android.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/rtw_proc.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/rtw_rhashtable.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/os_dep/linux/ioctl_mp.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/hal/hal_intf.o CC [M] /var/lib/dkms/rtl88x2bu/git/build/hal/hal_com.o CC [M] /var/lib/dkms/rtl88x2bu
[Bug 1899308] Re: failure to boot groovy daily (again)
@sudodus Using mkusb-dus / usb-pack-efi to prepare the live usb, I was able to boot the "Persistant Live" of Ubuntu MATE Groovy Desktop 20.10 Oct 14, 2020 ISO. Though the system booted fine, and I got to see the desktop screen, I have not actually installed the OS yet as I need to free up a partition for that. Many thanks for all the help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899308 Title: failure to boot groovy daily (again) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899308] Re: failure to boot groovy daily (again)
Hi @sudodus (1) The HP desktop have AMD radeon 290X graphics card. (2) Ubuntu MATE Focal 20.04 with kernel 5.9.0 and 5.8.14 runs just fine on the same HP PVILION eLITE DESKTOP. (3) Yes, as described in my previous post, when I try to boot the system from Ubuntu MATE Groovy desktop Oct 14, 2020 Live USB (prepared either with Etcher or MultiBootUSB), I do NOT get Grub from Live USB at all. Cursor blinks once or twice and immediately I get "installed version" of the Grub from Ubunbtu MATE Focal 20.04 (4) Regarding the "mkusb". Is this the correct PPA to install it from? https://launchpad.net/~mkusb/+archive/ubuntu/ppa Because I just added the PPA (and added the signing key / fingerprint) but afterwards I only get "mkusb" in Synaptic. I can not find "mkusb-dus". Or are they one and same package? (5) I will try once again with mkusb with the settings you've suggested. Thanks alot. - Jags -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899308 Title: failure to boot groovy daily (again) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899308] Re: failure to boot groovy daily (again)
Ubuntu MATE Groovy Oct 14, 2020 daily does not boot on HP Pavilion Elite HPE series Desktop PC. ISO: groovy-desktop-amd64.iso Downloaded from: http://cdimage.ubuntu.com/ubuntu-mate/daily- live/current/ sha256sum: bdf86534a8ef8c353f45a0c82776aaf8b0cc57eac85cc05b9d80b302f9e7cade I flashed/prepared the USB drive using from Ubuntu MATE Focal 20.04 using: (1) Etcher 1.5.109 ( Balena Etcher https://github.com/balena- io/etcher/releases ), and (2) MultiBootUSB 9.2.0 ( https://github.com/mbusb/multibootusb/releases ) Upon reboot, and selecting the USB drive from BIOS's "One-time boot menu" option, cursor blinks once or twice in upper left corner of the screen, and then system displays Ubuntu MATE Focal 20.04 Grub (Grub options are: 2 kernels of Ubuntu MATE Focal and Windows 10). So far I have tried 2 different USB ports. Also, using the same USB drive (prepared through either Etcher or MultiBootUSB) I can boot Ubuntu MATE Focal 20.04 on the same HP desktop just fine. Please let me know, if you want me to run any tests or something. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899308 Title: failure to boot groovy daily (again) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885414] Re: on flavours ubiquity: bootloader failed on /dev/vda
@nrbrtx (Norbert) Ok. Also, just to be extra clear, "Enable EFI" was NOT selected in the VirtualBox settings, and the host machine is also with old-style BIOS (no UEFI at all). #1: Do I have to create two small partitions, (1) EFI system partition, and (2) Reserved BIOS boot area... or just one, EFI system partition? #2: From the link you provided, point #11 says, "Full drive space is allocated for installation" So does manual partitioning (meaning not allocating the full drive space) blocked / not allowed anymore with Ubuntu / Ubuntu MATE 20.10 onward? Thanks alot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885414 Title: on flavours ubiquity: bootloader failed on /dev/vda To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1885414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885414] Re: on flavours ubiquity: bootloader failed on /dev/vda
Bootloader installation still fails with Aug 06, 2020 ISO of Ubuntu MATE Groovy 20.10 in a VirtualBox VM. Host OS: Ubuntu MATE 20.04 VirtualBox Version: VirtualBox-6.1.97-139689-Linux_amd64 Right when I tried to partition manually there were warnings that I never saw up until Ubuntu MATE Focal 20.04 Warning #1: "No EFI System Partition was found. This system will likely not be able to boot successfully, and the installation process may fail. Please go back and add an EFI System Partition, or continue at your own risk". and upon clicking "Continue", installer displayed: Warning #2: "The partition table format in use on your disks normally requires you to create a separate partition for boot loader code. This partition should be marked as a "Reserved BIOS boot area" and should be at leat 1 MB in size. Note that thi is not the same as a partition mounted on /boot. If you do not go back to the partitioning menu and correct this error, boot loader installation may fail later, although it may still be possible to install the boot loader to a partition". I have submitted 2 similar bug reports on July 06, and Aug 01, bug report #1886580 and #1889989. Today, I could not submit bug report from within the installation as Apport kept displaying a message, "Collecting problem information". I waited for 20+ minutes but it did not bring a window from where I can submit a bug report. Here's Imgur album with 7 screenshots: https://imgur.com/a/fgaxBoc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885414 Title: on flavours ubiquity: bootloader failed on /dev/vda To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1885414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886580] Re: Grub fails to install in a VirtualBox installation of Ubuntu MATE Groovy 20.10 July 06, 2020
*** This bug is a duplicate of bug 1885414 *** https://bugs.launchpad.net/bugs/1885414 ** This bug has been marked a duplicate of bug 1885414 on flavours ubiquity: bootloader failed on /dev/vda -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886580 Title: Grub fails to install in a VirtualBox installation of Ubuntu MATE Groovy 20.10 July 06, 2020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1886580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889989] Re: Grub fails to install in a VirtualBox installation of Ubuntu MATE Groovy 20.10 Aug 01, 2020
*** This bug is a duplicate of bug 1885414 *** https://bugs.launchpad.net/bugs/1885414 ** This bug is no longer a duplicate of bug 1886580 Grub fails to install in a VirtualBox installation of Ubuntu MATE Groovy 20.10 July 06, 2020 ** This bug has been marked a duplicate of bug 1885414 on flavours ubiquity: bootloader failed on /dev/vda -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889989 Title: Grub fails to install in a VirtualBox installation of Ubuntu MATE Groovy 20.10 Aug 01, 2020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1889989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889989] Re: Grub fails to install in a VirtualBox installation of Ubuntu MATE Groovy 20.10 Aug 01, 2020
*** This bug is a duplicate of bug 1886580 *** https://bugs.launchpad.net/bugs/1886580 Imgur album with 3 screenshots: https://imgur.com/a/sjMi756 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889989 Title: Grub fails to install in a VirtualBox installation of Ubuntu MATE Groovy 20.10 Aug 01, 2020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1889989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886580] Re: Grub fails to install in a VirtualBox installation of Ubuntu MATE Groovy 20.10 July 06, 2020
Imgur album with 3 screenshots: https://imgur.com/a/sjMi756 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886580 Title: Grub fails to install in a VirtualBox installation of Ubuntu MATE Groovy 20.10 July 06, 2020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1886580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889989] [NEW] Grub fails to install in a VirtualBox installation of Ubuntu MATE Groovy 20.10 Aug 01, 2020
*** This bug is a duplicate of bug 1886580 *** https://bugs.launchpad.net/bugs/1886580 Public bug reported: Grub fails to install in VirtualBox installation of Ubuntu MATE Groovy 20.10 Aug 01, 2020 64-bit. Note: This is a duplicate bug report similar to one filed on July 06, 2020: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1886580 Though I'm trying to install Ubuntu MATE Groovy in a VirtualBox installation, I like to make it clear that, this is a desktop PC with old-style BIOS (No UEFI at all). Ubuntu MATE 20.10 daily live ISO I'm installing from is of Aug 01, 2020 VirtualBox version is: VirtualBox-6.1.97-139665-Linux_amd64, and it runs Ubuntu MATE 20.04 Focal with kernel version 5.7.11 Issue: When I first tried to install it with just two partitions (like I always have up until now), (1) First EXT4 partition of 22GB, and (2) Second SWAP partition of 3GB; installer displayed: Error-1: "No EFI System Partition was found. This system will likely not be able to boot successfully, and the installation process may fail. Please go back and add an EFI System Partition, or continue at your own risk". and upon clicking Continue, it displayed: Error-2: "The partition table format in use on your disks normally requires you to create a separate partition for boot loader code. This partition should be marked as a "Reserved BIOS boot area" and should be at leat 1 MB in size. Note that thi is not the same as a partition mounted on /boot. If you do not go back to the partitioning menu and correct this error, boot loader installation may fail later, although it may still be possible to install the boot loader to a partition". So I went back and created: (1) EFI partition 1GB (2) Reserved BIOS boot area partition 1GB (3) / EXT4 partition 20GB (4) SWAP partition 3GB So even with "EFI" and "biosgrub" partitions, grub fails to install on either SDA/SDA1/SDA2/SDA3 with a message, "Bootloader install failed: Sorry, an error occurred and it was not possible to install the bootloader at the specified location". Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.9 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu43 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.452 Date: Sat Aug 1 08:45:58 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu-MATE 20.10 "Groovy Gorilla" - Alpha amd64 (20200801) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubiquity-20.10.9 ubuntu-mate ** This bug has been marked a duplicate of bug 1886580 Grub fails to install in a VirtualBox installation of Ubuntu MATE Groovy 20.10 July 06, 2020 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889989 Title: Grub fails to install in a VirtualBox installation of Ubuntu MATE Groovy 20.10 Aug 01, 2020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1889989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886580] Re: Grub fails to install in a VirtualBox installation of Ubuntu MATE Groovy 20.10 July 06, 2020
** Description changed: Grub fails to install in VirtualBox installation of Ubuntu MATE Groovy 20.10 July 06, 2020 64-bit. Though I'm trying to install Ubuntu MATE Groovy in a VirtualBox installation, I just like to make it clear that, this is a desktop PC with old-style BIOS (No UEFI at all). VirtualBox version is: VirtualBox-6.1.97-138534-Linux_amd64, and it runs Ubuntu MATE 20.04 Focal just fine (even with Kernel 5.7.7). Issue: When I first tried to install it with just two partitions (like I - always have up until now), (1) First EXT4 partition of 23GB, and (2) - Second SWAP partition of 2GB; installer displays, + always have up until now), + + (1) First EXT4 partition of 23GB, and + (2) Second SWAP partition of 2GB; + + installer displayed: Error-1: No EFI System Partition was found. This system will likely not be able to boot successfully, and the installation process may fail. Please go back and add an EFI System Partition, or continue at your own risk. - and upon clicking continue displays, + and upon clicking "Continue", displayed: Error-2: The partition table format in use on your disks normally requires you to create a separate partition for boot loader code. This partition should be marked as a "Reserved BIOS boot area" and should be at leat 1 MB in size. Note that thi is not the same as a partition mounted on /boot. If you do not go back to the partitioning menu and correct this error, boot loader installation may fail later, although it may still be possible to install the boot loader to a partition. So I went back and created: (1) EFI partition 1GB (2) Reserved BIOS boot area partition 1GB (3) /boot EXT4 partition 1GB (4) / EXT4 partition 22GB Note: I did not create SWAP partition as I could not find a way to create "Extended Partition" using Ubuntu MATE 20.10 installer. So even with "EFI", "biosgrub", and "/boot" partitions, grub fails to install on either SDA/SDA1/SDA2/SDA3/SDA4 with a message, Bootloader install failed: Sorry, an error occurred and it was not possible to install the bootloader at the specified location. Attaching: (1) var/log/syslog (2) Imgur album with screenshots (as I could not attach 16 files in here): https://imgur.com/a/xKf8nNM ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.7 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu42 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-435/libnvidia-gl-435_435.21-0ubuntu7_i386.deb CasperMD5CheckResult: skip CasperVersion: 1.452 Date: Mon Jul 6 13:35:55 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu-MATE 20.10 "Groovy Gorilla" - Alpha amd64 (20200706) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886580 Title: Grub fails to install in a VirtualBox installation of Ubuntu MATE Groovy 20.10 July 06, 2020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1886580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886580] [NEW] Grub fails to install in a VirtualBox installation of Ubuntu MATE Groovy 20.10 July 06, 2020
Public bug reported: Grub fails to install in VirtualBox installation of Ubuntu MATE Groovy 20.10 July 06, 2020 64-bit. Though I'm trying to install Ubuntu MATE Groovy in a VirtualBox installation, I just like to make it clear that, this is a desktop PC with old-style BIOS (No UEFI at all). VirtualBox version is: VirtualBox-6.1.97-138534-Linux_amd64, and it runs Ubuntu MATE 20.04 Focal just fine (even with Kernel 5.7.7). Issue: When I first tried to install it with just two partitions (like I always have up until now), (1) First EXT4 partition of 23GB, and (2) Second SWAP partition of 2GB; installer displays, Error-1: No EFI System Partition was found. This system will likely not be able to boot successfully, and the installation process may fail. Please go back and add an EFI System Partition, or continue at your own risk. and upon clicking continue displays, Error-2: The partition table format in use on your disks normally requires you to create a separate partition for boot loader code. This partition should be marked as a "Reserved BIOS boot area" and should be at leat 1 MB in size. Note that thi is not the same as a partition mounted on /boot. If you do not go back to the partitioning menu and correct this error, boot loader installation may fail later, although it may still be possible to install the boot loader to a partition. So I went back and created: (1) EFI partition 1GB (2) Reserved BIOS boot area partition 1GB (3) /boot EXT4 partition 1GB (4) / EXT4 partition 22GB Note: I did not create SWAP partition as I could not find a way to create "Extended Partition" using Ubuntu MATE 20.10 installer. So even with "EFI", "biosgrub", and "/boot" partitions, grub fails to install on either SDA/SDA1/SDA2/SDA3/SDA4 with a message, Bootloader install failed: Sorry, an error occurred and it was not possible to install the bootloader at the specified location. Attaching: (1) var/log/syslog (2) Imgur album with screenshots (as I could not attach 16 files in here): https://imgur.com/a/xKf8nNM ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.7 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu42 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-435/libnvidia-gl-435_435.21-0ubuntu7_i386.deb CasperMD5CheckResult: skip CasperVersion: 1.452 Date: Mon Jul 6 13:35:55 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu-MATE 20.10 "Groovy Gorilla" - Alpha amd64 (20200706) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubiquity ubiquity-20.10.7 ubuntu-mate ** Attachment added: "var_log_syslog" https://bugs.launchpad.net/bugs/1886580/+attachment/5390297/+files/syslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886580 Title: Grub fails to install in a VirtualBox installation of Ubuntu MATE Groovy 20.10 July 06, 2020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1886580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886580] Re: Grub fails to install in a VirtualBox installation of Ubuntu MATE Groovy 20.10 July 06, 2020
Attaching: (1) var/log/partman.txt ** Attachment added: "var_log_partman.txt" https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1886580/+attachment/5390307/+files/partman.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886580 Title: Grub fails to install in a VirtualBox installation of Ubuntu MATE Groovy 20.10 July 06, 2020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1886580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866372] Re: Plymouth causes update-initramfs to fail
*** This bug is a duplicate of bug 1866377 *** https://bugs.launchpad.net/bugs/1866377 I ran into this bug too on Ubuntu MATE 20.04. After a reboot I was not able to log back in at all. I had to boot the PC through Live-USB, chroot into the system, and applied Joseph C. Sible's workaround, which by the way worked perfectly. Then I run: `update-initramfs -c -k all` and I was able boot back into the system. Just in case if anyone is interested, some of the errors I ran into: /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.5.8-050508-generic cp: cannot create regular file '/var/tmp/mkinitramfs_HrLIsw/usr/share/plymouth/themes/spinner/watermark.png': No such file or directory E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1. update-initramfs: failed for /boot/initrd.img-5.5.8-050508-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 dpkg: error processing package linux-image-unsigned-5.5.8-050508-generic (--configure): installed linux-image-unsigned-5.5.8-050508-generic package post- installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-image- unsigned-5.5.8-050508-generic E: Sub-process /usr/bin/dpkg returned an error code (1) Thanks alot, Joseph. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866372 Title: Plymouth causes update-initramfs to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1866372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817358] Re: Ubuntu 16.04 netboot installation failed during loading of installer component libc6-udeb
I can confirm that installation fails for (upcoming) Ubuntu 19.10 Eoan with Mini ISO that was downloaded from: http://archive.ubuntu.com/ubuntu/dists/eoan/main/installer- amd64/current/images/netboot/ mini.iso2019-08-29 19:3972M sha256sum: B7E8C5AC6ED4C8EE5C6EB6D96060570D3BBDF11CB61DD0561CCE1E6F1EB833FE Error Message: Failed to load installer component. Loading libc6-udeb failed for unknown reasons. Aborting. Though I tried NetBoot installation on Sep 09, the latest Mini ISO available was from Aug 29. On top of the fail installation, I was not able to save debug logs either. I tried one more time with Mini ISO, but this time I pre-partitioned the VM disk (created EXT4 and SWAP partitions) with another Ubuntu Mate Live 19.10 Sep 09 ISO first (which was working just fine), then booted with NetBoot ISO, though installation still failed with the same error message. Screenshots (since installer couldn't let me save debug logs): https://imgur.com/8ZMtfHL https://imgur.com/WhavJS9 https://imgur.com/UAG4h1p Thanks, Jags -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817358 Title: Ubuntu 16.04 netboot installation failed during loading of installer component libc6-udeb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1817358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
