Δημοσιεύτηκε: 01 Αύγ 2016, 15:49
Τελικά δεν έχει σχέση το ότι απεγκατέστησα τον προηγούμενο πυρήνα πριν κάνω reboot. Πήγα να εγκαταστήσω τον 4.7 και στη άλλη διανομή του ίδιου laptop, και το πρόβλημα υπάρχει και εδώ.
Επίσης κατά την εγκατάσταση πρόσεξα σφάλματα σχετικά με το bcmwl:
Επίσης βρήκα πως υπάρχει ήδη αναφερμένο bug
Launchpad bug: #1595765
Επίσης κατά την εγκατάσταση πρόσεξα σφάλματα σχετικά με το bcmwl:
- Κώδικας: Επιλογή όλων
george@HP-Ubuntu:/tmp$ sudo dpkg -i *.deb
[sudo] password for george:
Selecting previously unselected package linux-headers-4.7.0-040700.
(Ανάγνωση βάσης δεδομένων ... 386090 files and directories currently installed.)
Preparing to unpack linux-headers-4.7.0-040700_4.7.0-040700.201607241632_all.deb ...
Unpacking linux-headers-4.7.0-040700 (4.7.0-040700.201607241632) ...
Selecting previously unselected package linux-headers-4.7.0-040700-generic.
Preparing to unpack linux-headers-4.7.0-040700-generic_4.7.0-040700.201607241632_amd64.deb ...
Unpacking linux-headers-4.7.0-040700-generic (4.7.0-040700.201607241632) ...
Selecting previously unselected package linux-image-4.7.0-040700-generic.
Preparing to unpack linux-image-4.7.0-040700-generic_4.7.0-040700.201607241632_amd64.deb ...
Examining /etc/kernel/preinst.d/
run-parts: executing /etc/kernel/preinst.d/intel-microcode 4.7.0-040700-generic /boot/vmlinuz-4.7.0-040700-generic
Done.
Unpacking linux-image-4.7.0-040700-generic (4.7.0-040700.201607241632) ...
Γίνεται εγκατάσταση linux-headers-4.7.0-040700 (4.7.0-040700.201607241632) ...
Γίνεται εγκατάσταση linux-headers-4.7.0-040700-generic (4.7.0-040700.201607241632) ...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms 4.7.0-040700-generic /boot/vmlinuz-4.7.0-040700-generic
Error! Bad return status for module build on kernel: 4.7.0-040700-generic (x86_64)
Consult /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/make.log for more information.
Γίνεται εγκατάσταση linux-image-4.7.0-040700-generic (4.7.0-040700.201607241632) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.7.0-040700-generic /boot/vmlinuz-4.7.0-040700-generic
run-parts: executing /etc/kernel/postinst.d/dkms 4.7.0-040700-generic /boot/vmlinuz-4.7.0-040700-generic
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/bcmwl-kernel-source.0.crash'
Error! Bad return status for module build on kernel: 4.7.0-040700-generic (x86_64)
Consult /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/make.log for more information.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.7.0-040700-generic /boot/vmlinuz-4.7.0-040700-generic
update-initramfs: Generating /boot/initrd.img-4.7.0-040700-generic
W: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/skl_guc_ver6.bin for module i915
run-parts: executing /etc/kernel/postinst.d/pm-utils 4.7.0-040700-generic /boot/vmlinuz-4.7.0-040700-generic
run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 4.7.0-040700-generic /boot/vmlinuz-4.7.0-040700-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 4.7.0-040700-generic /boot/vmlinuz-4.7.0-040700-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.7.0-040700-generic /boot/vmlinuz-4.7.0-040700-generic
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.7.0-040700-generic
Found initrd image: /boot/initrd.img-4.7.0-040700-generic
Found linux image: /boot/vmlinuz-4.6.3-040603-generic
Found initrd image: /boot/initrd.img-4.6.3-040603-generic
Found linux image: /boot/vmlinuz-4.4.0-31-generic
Found initrd image: /boot/initrd.img-4.4.0-31-generic
Found linux image: /boot/vmlinuz-4.4.0-28-generic
Found initrd image: /boot/initrd.img-4.4.0-28-generic
Found Windows Boot Manager on /dev/sda4@/EFI/Microsoft/Boot/bootmgfw.efi
Found Ubuntu 16.04.1 LTS (16.04) on /dev/sdb2
Adding boot menu entry for EFI firmware configuration
done
Επίσης βρήκα πως υπάρχει ήδη αναφερμένο bug