10-21-2015, 09:47 AM
@Jerry,
I have a small Atom based PC that is on the opposite side of the house, WiFi on the device was already flaky, it would drop very frequently, 5/6 X a day.
So I did a new driver install, and it would run for 3~4 days, then maybe drop, a re-start of the network manager would fix it.
Given it is not a critical device, I thought I would try the latest kernel. You mention to ignore any errors... are these the errors:
First Error
Second Error:
Third Error:
This is not a Virtualbox Guest, and Virtualbox is not installed.
NOTE:
I decided to roll back to 3.13, because even though it upgraded, and everything appeared to work...
I did not like the "tainting kernel" error in the dmesg log file:
Also there is no SD Card device on this pc.
I now have a workaround for the dropping wifi.
I re-start the network manager daily via cron.
I have a small Atom based PC that is on the opposite side of the house, WiFi on the device was already flaky, it would drop very frequently, 5/6 X a day.
So I did a new driver install, and it would run for 3~4 days, then maybe drop, a re-start of the network manager would fix it.
Given it is not a critical device, I thought I would try the latest kernel. You mention to ignore any errors... are these the errors:
First Error
Code:
Setting up linux-image-linuxlite-4.2.0 (0010) ...
Hmm. There is a symbolic link /lib/modules/4.2.0-linuxlite/build
However, I can not read it: No such file or directory
Therefore, I am deleting /lib/modules/4.2.0-linuxlite/build
Hmm. The package shipped with a symbolic link /lib/modules/4.2.0-linuxlite/source
However, I can not read the target: No such file or directory
Therefore, I am deleting /lib/modules/4.2.0-linuxlite/source
Running depmod.
Second Error:
Code:
Error! Bad return status for module build on kernel: 4.2.0-linuxlite (x86_64)
Consult /var/lib/dkms/virtualbox-guest/4.3.10/build/make.log for more information.
Third Error:
Code:
Error! Bad return status for module build on kernel: 4.2.0-linuxlite (x86_64)
Consult /var/lib/dkms/virtualbox-guest/4.3.10/build/make.log for more information.
This is not a Virtualbox Guest, and Virtualbox is not installed.
NOTE:
I decided to roll back to 3.13, because even though it upgraded, and everything appeared to work...
I did not like the "tainting kernel" error in the dmesg log file:
Code:
[1.312015] sdhci: module verification failed: signature and/or required key missing - tainting kernel
I now have a workaround for the dropping wifi.
I re-start the network manager daily via cron.
Upgrades WIP 2.6 to 2.8 - (6 X 2.6 to 2.8 completed on: 20/02/16 All O.K )
Linux Lite 3.0 Humming on a ASRock N3070 Mobo ~ btrfs RAID 10 Install on 4 Disks
Computers Early days:
ZX Spectrum(1982) , HP-150 MS-DOS(1983) , Amstrad CPC464(1984) , BBC Micro B+64(1985) , My First PC HP-Vectra(1987)
Linux Lite 3.0 Humming on a ASRock N3070 Mobo ~ btrfs RAID 10 Install on 4 Disks

Computers Early days:
ZX Spectrum(1982) , HP-150 MS-DOS(1983) , Amstrad CPC464(1984) , BBC Micro B+64(1985) , My First PC HP-Vectra(1987)