0

I have a new HP laptop. Ubuntu 18.04 installs fine apart from "No WiFi Adaptor found". I have looked at Realtek Semiconductor RTL8723DE Device d723 issue and followed the instructions there ("There is new information on this device"), but get the same error message that others report, namely:

$ sudo dkms install rtl8723de/5.1.1.8_21285.20171026_COEX20170111-1414 Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area... 'make' all KVER=4.15.0-22-generic...(bad exit status: 2) ERROR (dkms apport): binary package for rtl8723de: 5.1.1.8_21285.20171026_COEX20170111-1414 not found Error! Bad return status for module build on kernel: 4.15.0-22-generic (x86_64) Consult /var/lib/dkms/rtl8723de/5.1.1.8_21285.20171026_COEX20170111-1414/build/make.log for more information.

I also tried the second suggestion on that page ("You may use the driver hosted at Larry Finger..."). That all installed, but made no difference to "No Wifi Adaptor found".

Here's what the (groovy!) Ubuntu wireless info script says about my setup: https://paste.ubuntu.com/p/5KNtV5qzzz/

Hoping someone can help.

  • Notice it doesn't say kernel module in use: rtl8723de, did you do a dkms remove and uninstall for the first version you tried? – Jeremy31 May 30 '18 at 21:47
  • @pomsky yes I have tried rebooting since then, but see no change. – Marcus Frean Jun 02 '18 at 20:48
  • @Jeremy31 Clarification: do you suggest I remove dkms and then retry the first answer given at https://askubuntu.com/questions/983251/realtek-semiconductor-rtl8723de-device-d723-issue ? – Marcus Frean Jun 02 '18 at 20:50
  • Actually is Secure Boot disabled? Check mokutil --sb-state – Jeremy31 Jun 02 '18 at 21:50
  • @Jeremy31 Secure Boot is enabled. – Marcus Frean Jun 05 '18 at 21:02
  • Go into BIOS/UEFI settings and disable it so that the module can actually load – Jeremy31 Jun 05 '18 at 22:02
  • I have done this, but now Ubuntu doesn't boot - it just brings up Windows10. – Marcus Frean Jun 06 '18 at 07:15
  • @Jeremy31 I don't understand why my disabling Secure Boot messed with Dual Booting into Ubuntu, but it did. So I see two options: I could try to re-enable Secure Boot (doesn't solve the original problem), or could start anew with an Ubuntu iso. Would you agree? Thanks. – Marcus Frean Jun 11 '18 at 10:35
  • There is a way to sign the module yourself so it will load with secure boot enabled but I haven't tried it – Jeremy31 Jun 11 '18 at 11:29

0 Answers0