Ubuntu
alsa-driver package

Webcam sound and video not detected Ubuntu 16.04

Asked by trigeek

I am running XUbuntu 16.04 on 2 disks on the same hp Pavilion 64 bit AMD desktop. One drive is a 2 tB WD hard drive, the second is a Seagate 2 tB SSD. The HDD recognizes the webcam sound and video perfectly but when I boot from the SSD, there is no sound or video device detected.

Here is the output from the command wget -O alsa-info.sh http://www.alsa-project.org/alsa-info.sh && chmod +x ./alsa-info.sh && ./alsa-info.sh, as suggested on the web page https://help.ubuntu.com/community/SoundTroubleshootingProcedure

more /tmp/alsa-info.txt.B0A1oY36cF
upload=true&script=true&cardinfo=
!!################################
!!ALSA Information Script v 0.4.64
!!################################

!!Script ran on: Sat Feb 18 01:27:45 UTC 2017

!!Linux Distribution
!!------------------

Ubuntu 16.04.2 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 16.04.2 LTS" NAME="Ubuntu" I
D=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.2 LTS" HOME_URL="http://www.ubuntu.com/" SUPPORT_
URL="http://help.ubuntu.com/" BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/" UBUNTU_CODENAME=xe
nial

!!DMI Information
!!---------------

Manufacturer: Hewlett-Packard
Product Name: p7-1247c
Product Version:
Firmware Version: 7.16
Board Vendor: PEGATRON CORPORATION
Board Name: 2ACD

!!ACPI Device Status Information
!!---------------

/sys/bus/acpi/devices/PNP0103:00/status 15
/sys/bus/acpi/devices/PNP0C01:00/status 15
/sys/bus/acpi/devices/PNP0C02:00/status 15
/sys/bus/acpi/devices/PNP0C0C:00/status 11
/sys/bus/acpi/devices/PNP0C0F:00/status 11
/sys/bus/acpi/devices/PNP0C0F:01/status 11
/sys/bus/acpi/devices/PNP0C0F:02/status 11
/sys/bus/acpi/devices/PNP0C0F:03/status 11
/sys/bus/acpi/devices/PNP0C0F:04/status 11
/sys/bus/acpi/devices/PNP0C0F:05/status 11
/sys/bus/acpi/devices/PNP0C0F:06/status 11
/sys/bus/acpi/devices/PNP0C0F:07/status 11
/sys/bus/acpi/devices/PNP0C0F:08/status 11
/sys/bus/acpi/devices/PNP0C0F:09/status 11
/sys/bus/acpi/devices/PNP0C0F:0a/status 11
/sys/bus/acpi/devices/PNP0C0F:0b/status 11
/sys/bus/acpi/devices/PNP0C0F:0c/status 11
/sys/bus/acpi/devices/PNP0C0F:0d/status 11
/sys/bus/acpi/devices/PNP0C0F:0e/status 11
/sys/bus/acpi/devices/PNP0C0F:0f/status 11
/sys/bus/acpi/devices/PNP0C0F:10/status 11
/sys/bus/acpi/devices/PNP0C0F:11/status 11
/sys/bus/acpi/devices/PNP0C0F:12/status 11
/sys/bus/acpi/devices/PNP0C0F:13/status 11
/sys/bus/acpi/devices/PNP0C0F:14/status 11
/sys/bus/acpi/devices/PNP0C0F:15/status 11
/sys/bus/acpi/devices/PNP0C0F:16/status 11
/sys/bus/acpi/devices/PNP0C0F:17/status 11
/sys/bus/acpi/devices/PNP0C0F:18/status 11
/sys/bus/acpi/devices/PNP0C0F:19/status 11
/sys/bus/acpi/devices/PNP0C0F:1a/status 11
/sys/bus/acpi/devices/PNP0C0F:1b/status 11
/sys/bus/acpi/devices/PNP0C0F:1c/status 11
/sys/bus/acpi/devices/PNP0C0F:1d/status 11
/sys/bus/acpi/devices/PNP0C0F:1e/status 11
/sys/bus/acpi/devices/PNP0C0F:1f/status 11
/sys/bus/acpi/devices/PNP0C0F:20/status 11
/sys/bus/acpi/devices/PNP0C0F:21/status 11
/sys/bus/acpi/devices/PNP0C0F:22/status 11
/sys/bus/acpi/devices/PNP0C0F:23/status 11
/sys/bus/acpi/devices/PNP0C0F:24/status 11
/sys/bus/acpi/devices/PNP0C0F:25/status 11
/sys/bus/acpi/devices/PNP0C0F:26/status 11
/sys/bus/acpi/devices/PNP0C0F:27/status 11
/sys/bus/acpi/devices/device:0f/status 15
/sys/bus/acpi/devices/device:10/status 15
/sys/bus/acpi/devices/device:12/status 15

!!Kernel Information
!!------------------

Kernel release: 3.16.0-24-generic
Operating System: GNU/Linux
Architecture: x86_64
Processor: x86_64
SMP Enabled: Yes

!!ALSA Version
!!------------

Driver version:
Library version: 1.1.0
Utilities version: 1.1.0

!!Loaded ALSA modules
!!-------------------

!!Sound Servers on this system
!!----------------------------

Pulseaudio:
      Installed - Yes (/usr/bin/pulseaudio)
      Running - Yes

!!Soundcards recognised by ALSA
!!-----------------------------

!!PCI Soundcards installed in the system
!!--------------------------------------

00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD] FCH Azalia Controller (rev 01)

!!Advanced information - PCI Vendor/Device/Subsystem ID's
!!-------------------------------------------------------

00:14.2 0403: 1022:780d (rev 01)
 Subsystem: 103c:2acd

!!Modprobe options (Sound related)
!!--------------------------------

snd_pcsp: index=-2
snd_usb_audio: index=-2
snd_atiixp_modem: index=-2
snd_intel8x0m: index=-2
snd_via82xx_modem: index=-2
snd_atiixp_modem: index=-2
snd_intel8x0m: index=-2
snd_via82xx_modem: index=-2
snd_usb_audio: index=-2
snd_usb_caiaq: index=-2
snd_usb_ua101: index=-2
snd_usb_us122l: index=-2
snd_usb_usx2y: index=-2
snd_cmipci: mpu_port=0x330 fm_port=0x388
snd_pcsp: index=-2
snd_usb_audio: index=-2

!!Loaded sound module options
!!---------------------------

!!ALSA Device nodes
!!-----------------

...back 1 page
!!Sound Servers on this system
!!----------------------------

Pulseaudio:
      Installed - Yes (/usr/bin/pulseaudio)
      Running - Yes

!!Soundcards recognised by ALSA
!!-----------------------------

!!PCI Soundcards installed in the system
!!--------------------------------------

00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD] FCH Azalia Controller (rev 01)

!!Advanced information - PCI Vendor/Device/Subsystem ID's
!!-------------------------------------------------------

00:14.2 0403: 1022:780d (rev 01)
 Subsystem: 103c:2acd

!!Modprobe options (Sound related)

...back 1 page
/sys/bus/acpi/devices/device:12/status 15

!!Kernel Information
!!------------------

Kernel release: 3.16.0-24-generic
Operating System: GNU/Linux
Architecture: x86_64
Processor: x86_64
SMP Enabled: Yes

!!ALSA Version
!!------------

Driver version:
Library version: 1.1.0
Utilities version: 1.1.0

!!Loaded ALSA modules
!!-------------------

!!Sound Servers on this system
root@civet:~#

This is extremely puzzling, especially in view of different behavior on different instances on the same computer!

I would appreciate suggestions/help.

Kevin

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu alsa-driver Edit question
Assignee:
No assignee Edit question
Solved by:
trigeek
Solved:
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#1

Why are you logging in to the desktop as root, or running the alsa-info.sh script with sudo?

Revision history for this message
trigeek (kjaspan) said : 		#2

The instructions said to log into a root terminal. How could the user
affect the results?

On Sat, Feb 18, 2017 at 4:39 AM, actionparsnip <
<email address hidden>> wrote:

> Your question #465662 on alsa-driver in Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/465662
>
> Status: Open => Needs information
>
> actionparsnip requested more information:
> Why are you logging in to the desktop as root, or running the alsa-
> info.sh script with sudo?
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/465662
>
> You received this question notification because you asked the question.
>

--
sent from my 64 bit AMD quad core hp Pavilion desktop
running Ubuntu Linux 16.04

Revision history for this message
trigeek (kjaspan) said : 		#3

I beg your pardon - it said log in to a Terminal Console, which I construed
to mean root.

On Sat, Feb 18, 2017 at 8:22 AM, Kevin Jaspan <email address hidden> wrote:

> The instructions said to log into a root terminal. How could the user
> affect the results?
>
> On Sat, Feb 18, 2017 at 4:39 AM, actionparsnip <question465662@answers.
> launchpad.net> wrote:
>
>> Your question #465662 on alsa-driver in Ubuntu changed:
>> https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/465662
>>
>> Status: Open => Needs information
>>
>> actionparsnip requested more information:
>> Why are you logging in to the desktop as root, or running the alsa-
>> info.sh script with sudo?
>>
>> --
>> To answer this request for more information, you can either reply to
>> this email or enter your reply at the following page:
>> https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/465662
>>
>> You received this question notification because you asked the question.
>>
>
>
>
> --
> sent from my 64 bit AMD quad core hp Pavilion desktop
> running Ubuntu Linux 16.04
>

--
sent from my 64 bit AMD quad core hp Pavilion desktop
running Ubuntu Linux 16.04

Revision history for this message
trigeek (kjaspan) said : 		#4

Just for comparison, here is the output of running the same command on the instance running off the hard disk, sda8:

http://www.alsa-project.org/db/?f=d56405be1bb39a079c8c756ccbd1665694eabda8

Kevin

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#5

That output has an ALSA driver version. This is good.

Ubuntu is geared around using the user and sudo rather than root. Users have different access to root's and is how the OS is setup to run and be used.

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#6

Do you see yourself in cheese? It's an application you can run. Should be in a default install

Revision history for this message
trigeek (kjaspan) said : 		#7

I do not see myself in Cheese - it says no device found. In Skype for Linux alpha it says "No microphone detected". This is on the SSD instance, /dev/sdb9.

To give a bit more background I built the SSD instance over 2 years ago - I think it had 14.04 at the time and could not boot from it. I just reinstalled the HDD instance because I mysteriously was running out of space, having used over 350Gb, though I could not find where the huge files were that were filling up the space. I then upgraded the SSD instance to 15.04 and then 16.04. Somewhere during that process, which also involved using Boot Repair to write Grub2 in the right partitions, I found I was able to boot from the SSD. Originally sound and video were not working on the SSD instance when it had 14.04 on it.

Anyway, is it possible to reload the Alsa drivers with apt-get?

Thanks.

Revision history for this message
trigeek (kjaspan) said : 		#8

Here's another piece of information: When I bought the SSD I had intended to use it as the primary drive and the HDD as backup. I cloned the HDD to the SSD, without installing Ubuntu, as I also wanted to use Windows on it (not that I use Windows more than 1% of the time). So, could I have caused the problem by not doing a fresh install of Ubuntu on the SSD?

Revision history for this message
trigeek (kjaspan) said : 		#9

This is weird. Here is the output from lsusb, which shows the webcam and a headset I've just plugged in. Neither Cheese not pulseaudio volume control recognizes those devices. How could that be?

lsusb
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 006: ID 1058:1021 Western Digital Technologies, Inc. Elements Desktop (WDBAAU)
Bus 001 Device 005: ID 046d:081b Logitech, Inc. Webcam C310
Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 003: ID 0461:4dd7 Primax Electronics, Ltd
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 028: ID 046d:0a01 Logitech, Inc. USB Headset
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 006 Device 002: ID 0461:4d0f Primax Electronics, Ltd HP Optical Mouse
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#10

Just because the system sees the hardware doesn't mean it can be used. Your OS needs to be configured. Have you never done a clean install of Windows and had devices in device manager with question marks (meaning it needs a driver)? Same thing.

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#11

If you run:

sudo modprobe uvcvideo usbvideo gspca_main

Then launch cheese, is it OK? If so, we can make it permanent.

Source: https://wiki.ubuntu.com/SkypeWebCams

Revision history for this message
trigeek (kjaspan) said : 		#12

I ran that and here was the result:

modprobe uvcvideo usbvideo gspca_main
modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/3.16.0-24-generic/modules.dep.bin'
modprobe: FATAL: Module uvcvideo not found in directory /lib/modules/3.16.0-24-generic

Revision history for this message
Manfred Hampl (m-hampl) said : 		#13

RE: is it possible to reload the Alsa drivers with apt-get?

see Step 1, item #1C. in https://help.ubuntu.com/community/SoundTroubleshootingProcedure
What output do you get for that command?

Revision history for this message
trigeek (kjaspan) said : 		#14

I ran it (again, as I think I ran it a couple of days ago) and Cheese still says no device found, pavucontrol says no input or output devices found. I can send a copy of the output of the command, 272 lines long, but I don't see a way to attach it except place it inline.

Revision history for this message
trigeek (kjaspan) said : 		#15

So, would removal of all those items installed as suggested by you, Manfred, followed by a reinstall be worth while or should I do a completely fresh reinstall of Xubuntu 16.04? That's a drastic step for me as it's about 8 hours of effort reinstalling all my applications afterwards.

Revision history for this message
Manfred Hampl (m-hampl) said : 		#16

The purpose of that command is reinstalling the packages related to sound.
What is the output of running that command?
You can either paste the output into this question document, or to http://pastebin.ubuntu.com and provide the link.

Revision history for this message
trigeek (kjaspan) said : 		#17

sudo apt-get update;sudo apt-get dist-upgrade; sudo apt-get install pavucontrol linux-sound-base alsa-base alsa-utils lightdm ubuntu-desktop linux-image-`uname -r` libasound2; sudo apt-get -y --reinstall install linux-sound-base alsa-base alsa-utils lightdm ubuntu-desktop linux-image-`uname -r` libasound2; killall pulseaudio; rm -r ~/.pulse*; ubuntu-support-status; sudo usermod -aG `cat /etc/group | grep -e '^pulse:' -e '^audio:' -e '^pulse-access:' -e '^pulse-rt:' -e '^video:' | awk -F: '{print $1}' | tr '\n' ',' | sed 's:,$::g'` `whoami`
[sudo] password for kevin:
Ign:1 http://dl.google.com/linux/chrome/deb stable InRelease
Ign:2 http://linux.dropbox.com/ubuntu wily InRelease
Hit:3 http://dl.google.com/linux/chrome/deb stable Release
Get:4 http://linux.dropbox.com/ubuntu wily Release [6,596 B]
Hit:5 http://us.archive.ubuntu.com/ubuntu xenial InRelease
Get:6 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB]
Hit:7 http://ppa.launchpad.net/danielrichter2007/grub-customizer/ubuntu xenial InRelease
Hit:8 http://archive.canonical.com/ubuntu utopic InRelease
Get:9 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease [102 kB]
Get:10 http://us.archive.ubuntu.com/ubuntu xenial-security InRelease [102 kB]
Hit:13 https://repo.skype.com/deb stable InRelease
Get:14 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [474 kB]
Get:15 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages [465 kB]
Get:16 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 DEP-11 Metadata [306 kB]
Get:17 http://us.archive.ubuntu.com/ubuntu xenial-updates/main DEP-11 64x64 Icons [188 kB]
Get:18 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages [398 kB]
Get:19 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe i386 Packages [393 kB]
Get:20 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 DEP-11 Metadata [133 kB]
Get:21 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe DEP-11 64x64 Icons [162 kB]
Get:22 http://us.archive.ubuntu.com/ubuntu xenial-updates/multiverse amd64 DEP-11 Metadata [2,520 B]
Get:23 http://us.archive.ubuntu.com/ubuntu xenial-backports/main amd64 DEP-11 Metadata [3,324 B]
Get:24 http://us.archive.ubuntu.com/ubuntu xenial-security/main amd64 DEP-11 Metadata [68.1 kB]
Get:25 http://us.archive.ubuntu.com/ubuntu xenial-security/main DEP-11 64x64 Icons [47.6 kB]
Get:26 http://us.archive.ubuntu.com/ubuntu xenial-security/universe amd64 DEP-11 Metadata [32.1 kB]
Get:27 http://us.archive.ubuntu.com/ubuntu xenial-security/universe DEP-11 64x64 Icons [37.0 kB]
Fetched 3,022 kB in 2s (1,390 kB/s)
Reading package lists... Done
N: Ignoring file '50unattended-upgrades.ucf-dist' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  linux-headers-4.4.0-63 linux-headers-4.4.0-63-generic
  linux-image-4.4.0-63-generic linux-image-extra-4.4.0-63-generic
The following packages will be upgraded:
  libpq5 linux-generic linux-headers-generic linux-image-generic linux-libc-dev
  snap-confine snapd
7 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 78.2 MB of archives.
After this operation, 297 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libpq5 amd64 9.5.6-0ubuntu0.16.04 [78.2 kB]
Get:2 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 linux-image-4.4.0-63-generic amd64 4.4.0-63.84 [21.8 MB]
Get:3 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 linux-image-extra-4.4.0-63-generic amd64 4.4.0-63.84 [36.0 MB]
Get:4 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 linux-generic amd64 4.4.0.63.67 [1,790 B]
Get:5 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 linux-image-generic amd64 4.4.0.63.67 [2,434 B]
Get:6 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 linux-headers-4.4.0-63 all 4.4.0-63.84 [9,984 kB]
Get:7 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 linux-headers-4.4.0-63-generic amd64 4.4.0-63.84 [782 kB]
Get:8 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 linux-headers-generic amd64 4.4.0.63.67 [2,410 B]
Get:9 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 linux-libc-dev amd64 4.4.0-63.84 [839 kB]
Get:10 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 snapd amd64 2.22.3 [8,741 kB]
Get:11 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 snap-confine amd64 2.22.3 [41.5 kB]
Fetched 78.2 MB in 13s (5,804 kB/s)
N: Ignoring file '50unattended-upgrades.ucf-dist' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension
(Reading database ... 592497 files and directories currently installed.)
Preparing to unpack .../libpq5_9.5.6-0ubuntu0.16.04_amd64.deb ...
Unpacking libpq5:amd64 (9.5.6-0ubuntu0.16.04) over (9.5.5-0ubuntu0.16.04) ...
Selecting previously unselected package linux-image-4.4.0-63-generic.
Preparing to unpack .../linux-image-4.4.0-63-generic_4.4.0-63.84_amd64.deb ...
Done.
Unpacking linux-image-4.4.0-63-generic (4.4.0-63.84) ...
Selecting previously unselected package linux-image-extra-4.4.0-63-generic.
Preparing to unpack .../linux-image-extra-4.4.0-63-generic_4.4.0-63.84_amd64.deb ...
Unpacking linux-image-extra-4.4.0-63-generic (4.4.0-63.84) ...
Preparing to unpack .../linux-generic_4.4.0.63.67_amd64.deb ...
Unpacking linux-generic (4.4.0.63.67) over (4.4.0.62.65) ...
Preparing to unpack .../linux-image-generic_4.4.0.63.67_amd64.deb ...
Unpacking linux-image-generic (4.4.0.63.67) over (4.4.0.62.65) ...
Selecting previously unselected package linux-headers-4.4.0-63.
Preparing to unpack .../linux-headers-4.4.0-63_4.4.0-63.84_all.deb ...
Unpacking linux-headers-4.4.0-63 (4.4.0-63.84) ...
Selecting previously unselected package linux-headers-4.4.0-63-generic.
Preparing to unpack .../linux-headers-4.4.0-63-generic_4.4.0-63.84_amd64.deb ...
Unpacking linux-headers-4.4.0-63-generic (4.4.0-63.84) ...
Preparing to unpack .../linux-headers-generic_4.4.0.63.67_amd64.deb ...
Unpacking linux-headers-generic (4.4.0.63.67) over (4.4.0.62.65) ...
Preparing to unpack .../linux-libc-dev_4.4.0-63.84_amd64.deb ...
Unpacking linux-libc-dev:amd64 (4.4.0-63.84) over (4.4.0-62.83) ...
Preparing to unpack .../snapd_2.22.3_amd64.deb ...
Warning: Stopping snapd.service, but it can still be activated by:
  snapd.socket
Unpacking snapd (2.22.3) over (2.22.2) ...
Preparing to unpack .../snap-confine_2.22.3_amd64.deb ...
Unpacking snap-confine (2.22.3) over (2.22.2) ...
Processing triggers for libc-bin (2.23-0ubuntu5) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up libpq5:amd64 (9.5.6-0ubuntu0.16.04) ...
Setting up linux-image-4.4.0-63-generic (4.4.0-63.84) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
The link /initrd.img is a dangling linkto /boot/initrd.img-4.4.0-62-generic
The link /vmlinuz is a dangling linkto /boot/vmlinuz-4.4.0-62-generic
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-63-generic /boot/vmlinuz-4.4.0-63-generic
N: Ignoring file '50unattended-upgrades.ucf-dist' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension
N: Ignoring file '50unattended-upgrades.ucf-dist' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension
N: Ignoring file '50unattended-upgrades.ucf-dist' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-63-generic /boot/vmlinuz-4.4.0-63-generic
update-initramfs: Generating /boot/initrd.img-4.4.0-63-generic
run-parts: executing /etc/kernel/postinst.d/pm-utils 4.4.0-63-generic /boot/vmlinuz-4.4.0-63-generic
run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 4.4.0-63-generic /boot/vmlinuz-4.4.0-63-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 4.4.0-63-generic /boot/vmlinuz-4.4.0-63-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.4.0-63-generic /boot/vmlinuz-4.4.0-63-generic
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.4.0-63-generic
Found initrd image: /boot/initrd.img-4.4.0-63-generic
Found linux image: /boot/vmlinuz-3.16.0-24-generic
Found initrd image: /boot/initrd.img-3.16.0-24-generic
Found linux image: /boot/vmlinuz-3.16.0-23-generic
Found initrd image: /boot/initrd.img-3.16.0-23-generic
Found linux image: /boot/vmlinuz-3.13.0-39-generic
Found initrd image: /boot/initrd.img-3.13.0-39-generic
Found linux image: /boot/vmlinuz-3.11.0-20-generic
Found initrd image: /boot/initrd.img-3.11.0-20-generic
Found linux image: /boot/vmlinuz-3.11.0-19-generic
Found initrd image: /boot/initrd.img-3.11.0-19-generic
Found linux image: /boot/vmlinuz-3.11.0-18-generic
Found initrd image: /boot/initrd.img-3.11.0-18-generic
Found linux image: /boot/vmlinuz-3.11.0-17-generic
Found initrd image: /boot/initrd.img-3.11.0-17-generic
Found linux image: /boot/vmlinuz-3.11.0-15-generic
Found initrd image: /boot/initrd.img-3.11.0-15-generic
Found linux image: /boot/vmlinuz-3.11.0-14-generic
Found initrd image: /boot/initrd.img-3.11.0-14-generic
Found linux image: /boot/vmlinuz-3.11.0-13-generic
Found initrd image: /boot/initrd.img-3.11.0-13-generic
Found linux image: /boot/vmlinuz-3.8.0-32-generic
Found initrd image: /boot/initrd.img-3.8.0-32-generic
Found linux image: /boot/vmlinuz-3.8.0-31-generic
Found initrd image: /boot/initrd.img-3.8.0-31-generic
Found linux image: /boot/vmlinuz-3.8.0-30-generic
Found initrd image: /boot/initrd.img-3.8.0-30-generic
Found linux image: /boot/vmlinuz-3.8.0-29-generic
Found initrd image: /boot/initrd.img-3.8.0-29-generic
Found linux image: /boot/vmlinuz-3.8.0-27-generic
Found initrd image: /boot/initrd.img-3.8.0-27-generic
Found linux image: /boot/vmlinuz-3.8.0-26-generic
Found initrd image: /boot/initrd.img-3.8.0-26-generic
Found linux image: /boot/vmlinuz-3.8.0-25-generic
Found initrd image: /boot/initrd.img-3.8.0-25-generic
Found linux image: /boot/vmlinuz-3.8.0-23-generic
Found initrd image: /boot/initrd.img-3.8.0-23-generic
Found linux image: /boot/vmlinuz-3.8.0-22-generic
Found initrd image: /boot/initrd.img-3.8.0-22-generic
Found linux image: /boot/vmlinuz-3.8.0-21-generic
Found initrd image: /boot/initrd.img-3.8.0-21-generic
Found linux image: /boot/vmlinuz-3.5.0-28-generic
Found initrd image: /boot/initrd.img-3.5.0-28-generic
Found linux image: /boot/vmlinuz-3.2.0-33-generic
Found initrd image: /boot/initrd.img-3.2.0-33-generic
Found Windows 10 (loader) on /dev/sda1
Found Windows 10 (loader) on /dev/sda2
Found Ubuntu 16.04.2 LTS (16.04) on /dev/sda7
Found Ubuntu 16.04.1 LTS (16.04) on /dev/sda8
Found Windows 8 (loader) on /dev/sdb1
Found Windows 10 (loader) on /dev/sdb2
Found Ubuntu 14.10 (14.10) on /dev/sdb7
Found Windows 7 (loader) on /dev/sdg1
Found Windows 7 (loader) on /dev/sdg3
Found Ubuntu 11.04 (11.04) on /dev/sdg5
done
Setting up linux-image-extra-4.4.0-63-generic (4.4.0-63.84) ...
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-63-generic /boot/vmlinuz-4.4.0-63-generic
N: Ignoring file '50unattended-upgrades.ucf-dist' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension
N: Ignoring file '50unattended-upgrades.ucf-dist' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension
N: Ignoring file '50unattended-upgrades.ucf-dist' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-63-generic /boot/vmlinuz-4.4.0-63-generic
update-initramfs: Generating /boot/initrd.img-4.4.0-63-generic
run-parts: executing /etc/kernel/postinst.d/pm-utils 4.4.0-63-generic /boot/vmlinuz-4.4.0-63-generic
run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 4.4.0-63-generic /boot/vmlinuz-4.4.0-63-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 4.4.0-63-generic /boot/vmlinuz-4.4.0-63-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.4.0-63-generic /boot/vmlinuz-4.4.0-63-generic
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.4.0-63-generic
Found initrd image: /boot/initrd.img-4.4.0-63-generic
Found linux image: /boot/vmlinuz-3.16.0-24-generic
Found initrd image: /boot/initrd.img-3.16.0-24-generic
Found linux image: /boot/vmlinuz-3.16.0-23-generic
Found initrd image: /boot/initrd.img-3.16.0-23-generic
Found linux image: /boot/vmlinuz-3.13.0-39-generic
Found initrd image: /boot/initrd.img-3.13.0-39-generic
Found linux image: /boot/vmlinuz-3.11.0-20-generic
Found initrd image: /boot/initrd.img-3.11.0-20-generic
Found linux image: /boot/vmlinuz-3.11.0-19-generic
Found initrd image: /boot/initrd.img-3.11.0-19-generic
Found linux image: /boot/vmlinuz-3.11.0-18-generic
Found initrd image: /boot/initrd.img-3.11.0-18-generic
Found linux image: /boot/vmlinuz-3.11.0-17-generic
Found initrd image: /boot/initrd.img-3.11.0-17-generic
Found linux image: /boot/vmlinuz-3.11.0-15-generic
Found initrd image: /boot/initrd.img-3.11.0-15-generic
Found linux image: /boot/vmlinuz-3.11.0-14-generic
Found initrd image: /boot/initrd.img-3.11.0-14-generic
Found linux image: /boot/vmlinuz-3.11.0-13-generic
Found initrd image: /boot/initrd.img-3.11.0-13-generic
Found linux image: /boot/vmlinuz-3.8.0-32-generic
Found initrd image: /boot/initrd.img-3.8.0-32-generic
Found linux image: /boot/vmlinuz-3.8.0-31-generic
Found initrd image: /boot/initrd.img-3.8.0-31-generic
Found linux image: /boot/vmlinuz-3.8.0-30-generic
Found initrd image: /boot/initrd.img-3.8.0-30-generic
Found linux image: /boot/vmlinuz-3.8.0-29-generic
Found initrd image: /boot/initrd.img-3.8.0-29-generic
Found linux image: /boot/vmlinuz-3.8.0-27-generic
Found initrd image: /boot/initrd.img-3.8.0-27-generic
Found linux image: /boot/vmlinuz-3.8.0-26-generic
Found initrd image: /boot/initrd.img-3.8.0-26-generic
Found linux image: /boot/vmlinuz-3.8.0-25-generic
Found initrd image: /boot/initrd.img-3.8.0-25-generic
Found linux image: /boot/vmlinuz-3.8.0-23-generic
Found initrd image: /boot/initrd.img-3.8.0-23-generic
Found linux image: /boot/vmlinuz-3.8.0-22-generic
Found initrd image: /boot/initrd.img-3.8.0-22-generic
Found linux image: /boot/vmlinuz-3.8.0-21-generic
Found initrd image: /boot/initrd.img-3.8.0-21-generic
Found linux image: /boot/vmlinuz-3.5.0-28-generic
Found initrd image: /boot/initrd.img-3.5.0-28-generic
Found linux image: /boot/vmlinuz-3.2.0-33-generic
Found initrd image: /boot/initrd.img-3.2.0-33-generic
Found Windows 10 (loader) on /dev/sda1
Found Windows 10 (loader) on /dev/sda2
Found Ubuntu 16.04.2 LTS (16.04) on /dev/sda7
Found Ubuntu 16.04.1 LTS (16.04) on /dev/sda8
Found Windows 8 (loader) on /dev/sdb1
Found Windows 10 (loader) on /dev/sdb2
Found Ubuntu 14.10 (14.10) on /dev/sdb7
Found Windows 7 (loader) on /dev/sdg1
Found Windows 7 (loader) on /dev/sdg3
Found Ubuntu 11.04 (11.04) on /dev/sdg5
done
Setting up linux-image-generic (4.4.0.63.67) ...
Setting up linux-headers-4.4.0-63 (4.4.0-63.84) ...
Setting up linux-headers-4.4.0-63-generic (4.4.0-63.84) ...
Setting up linux-headers-generic (4.4.0.63.67) ...
Setting up linux-generic (4.4.0.63.67) ...
Setting up linux-libc-dev:amd64 (4.4.0-63.84) ...
Setting up snap-confine (2.22.3) ...
Setting up snapd (2.22.3) ...
Processing triggers for libc-bin (2.23-0ubuntu5) ...
N: Ignoring file '50unattended-upgrades.ucf-dist' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package linux-image-3.16.0-24-generic is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

N: Ignoring file '50unattended-upgrades.ucf-dist' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension
E: Package 'linux-image-3.16.0-24-generic' has no installation candidate
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package linux-image-3.16.0-24-generic is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

N: Ignoring file '50unattended-upgrades.ucf-dist' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension
E: Package 'linux-image-3.16.0-24-generic' has no installation candidate
Support status summary of 'civet':

You have 11 packages (0.4%) supported until February 2022 (5y)
You have 2166 packages (76.4%) supported until April 2021 (5y)
You have 259 packages (9.1%) supported until April 2019 (3y)

You have 67 packages (2.4%) that can not/no-longer be downloaded
You have 332 packages (11.7%) that are unsupported

Run with --show-unsupported, --show-supported or --show-all to see more details
kevin@civet:~$

Revision history for this message
Manfred Hampl (m-hampl) said : 		#18

You should do some cleanup.

1. sudo rm /etc/apt/apt.conf.d/50unattended-upgrades.ucf-dist

2. reboot your system.
After restart, what is the output of the command
uname -a
?
It should contain 4.4.0-63-generic (which is the correct kernel version for xenial; you were still running 3.16.0-24 which is a version for Ubuntu 14.10 utopic - obsolete since July 2015!)

3. What is the output of the command
cat -n /etc/apt/sources.list

Revision history for this message
trigeek (kjaspan) said : 		#19

I ran the rm

uname -a
Linux civet 3.16.0-24-generic #32-Ubuntu SMP Tue Oct 28 13:07:32 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
so that's Ubuntu 14.04

cat -n /etc/apt/sources.list
     1 # deb cdrom:[Ubuntu 14.10 _Utopic Unicorn_ - Release amd64 (20141022.1)]/ utopic main restricted
     2
     3 # See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
     4 # newer versions of the distribution.
     5 deb http://us.archive.ubuntu.com/ubuntu/ xenial main restricted
     6 deb-src http://us.archive.ubuntu.com/ubuntu/ xenial main restricted
     7
     8 ## Major bug fix updates produced after the final release of the
     9 ## distribution.
    10 deb http://us.archive.ubuntu.com/ubuntu/ xenial-updates main restricted
    11 deb-src http://us.archive.ubuntu.com/ubuntu/ xenial-updates main restricted
    12
    13 ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
    14 ## team. Also, please note that software in universe WILL NOT receive any
    15 ## review or updates from the Ubuntu security team.
    16 deb http://us.archive.ubuntu.com/ubuntu/ xenial universe
    17 deb-src http://us.archive.ubuntu.com/ubuntu/ xenial universe
    18 deb http://us.archive.ubuntu.com/ubuntu/ xenial-updates universe
    19 deb-src http://us.archive.ubuntu.com/ubuntu/ xenial-updates universe
    20
    21 ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
    22 ## team, and may not be under a free licence. Please satisfy yourself as to
    23 ## your rights to use the software. Also, please note that software in
    24 ## multiverse WILL NOT receive any review or updates from the Ubuntu
    25 ## security team.
    26 deb http://us.archive.ubuntu.com/ubuntu/ xenial multiverse
    27 deb-src http://us.archive.ubuntu.com/ubuntu/ xenial multiverse
    28 deb http://us.archive.ubuntu.com/ubuntu/ xenial-updates multiverse
    29 deb-src http://us.archive.ubuntu.com/ubuntu/ xenial-updates multiverse
    30
    31 ## N.B. software from this repository may not have been tested as
    32 ## extensively as that contained in the main release, although it includes
    33 ## newer versions of some applications which may provide useful features.
    34 ## Also, please note that software in backports WILL NOT receive any review
    35 ## or updates from the Ubuntu security team.
    36 deb http://us.archive.ubuntu.com/ubuntu/ xenial-backports main restricted universe multiverse
    37 deb-src http://us.archive.ubuntu.com/ubuntu/ xenial-backports main restricted universe multiverse
    38
    39 deb http://us.archive.ubuntu.com/ubuntu/ xenial-security main restricted
    40 deb-src http://us.archive.ubuntu.com/ubuntu/ xenial-security main restricted
    41 deb http://us.archive.ubuntu.com/ubuntu/ xenial-security universe
    42 deb-src http://us.archive.ubuntu.com/ubuntu/ xenial-security universe
    43 deb http://us.archive.ubuntu.com/ubuntu/ xenial-security multiverse
    44 deb-src http://us.archive.ubuntu.com/ubuntu/ xenial-security multiverse
    45
    46 ## Uncomment the following two lines to add software from Canonical's
    47 ## 'partner' repository.
    48 ## This software is not part of Ubuntu, but is offered by Canonical and the
    49 ## respective vendors as a service to Ubuntu users.
    50 deb http://archive.canonical.com/ubuntu utopic partner
    51 # deb-src http://archive.canonical.com/ubuntu utopic partner
    52

Revision history for this message
trigeek (kjaspan) said : 		#20

lsb_release -r
Release: 16.04
 Why does this say I have xenial when uname -a says it's utopic? I did run the upgrades from utopic to 15 to xenial.

Revision history for this message
Manfred Hampl (m-hampl) said : 		#21

Did you already reboot?
Did you select a specific kernel version from the grub menu?

Revision history for this message
trigeek (kjaspan) said : 		#22

Yes, I rebooted. I select the menu item corresponding to the installation on /dev/sdb9, which is the Ubuntu installation on the SSD. it says: Ubuntu 16.04.2 LTS (16.04) (on /dev/sdb9). I could rather go to the next entry :
Advanced options for Ubuntu 16.04.2 LTS (16.04) (on /dev/sdb9 and select a subentry there but they are all 3.16

Revision history for this message
Manfred Hampl (m-hampl) said : 		#23

I assume that the kernel version problem and your sound/video problem are related, see e.g. the message
modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/3.16.0-24-generic/modules.dep.bin'

I have problems understanding the layout of your systems. How many different Ubuntu installations do you have?

Found Windows 10 (loader) on /dev/sda1
Found Windows 10 (loader) on /dev/sda2
Found Ubuntu 16.04.2 LTS (16.04) on /dev/sda7
Found Ubuntu 16.04.1 LTS (16.04) on /dev/sda8
Found Windows 8 (loader) on /dev/sdb1
Found Windows 10 (loader) on /dev/sdb2
Found Ubuntu 14.10 (14.10) on /dev/sdb7
Found Windows 7 (loader) on /dev/sdg1
Found Windows 7 (loader) on /dev/sdg3
Found Ubuntu 11.04 (11.04) on /dev/sdg5

Which is the one that you are booting?
What is the output of

sudo fdisk -l
df -h
sudo blkid

And finally, lines 50 and 51 of your sources.list file should be corrected from utopic to xenial.

Revision history for this message
trigeek (kjaspan) said : 		#24

Manfred,
Firstly thank you for all your help. Danke schoen.

I have, on SATA1, a 2tB WD disk, which is sda. On it is my primary Windows installation, sda2, and the Ubuntu 16.04 installation I rebuilt from scratch less than 2 weeks ago on sda7.

In the second slot on SATA1 I connected a 2 tB Seagate SSD. On it, on sdb9, is the Ubuntu 16.04 installation I'm having all the trouble with. When I installed the disk over 2 years ago I wanted to have an identical installation to the one on sda7 so I cloned the disk.At that stage I could not boot from it unless I swapped positions on the SATA cable and was having the sound and video problems. After the reinstall on sda7, while I was running Boot Repair, I suddenly found I could boot from either disk, so I upgraded the SSD to 16.04 and found the sound & video problems were still there.

Please ignore all the older versions lying around on the disks. I'm concerned with sdb9.

Here is the fdisk output:
 fdisk -l
Disk /dev/ram0: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram1: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram2: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram3: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram4: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram5: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram6: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram7: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram8: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram9: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram10: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram11: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram12: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram13: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram14: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram15: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x47ba187e

Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 206847 204800 100M 7 HPFS/NTFS/exFAT
/dev/sda2 206848 499918847 499712000 238.3G 7 HPFS/NTFS/exFAT
/dev/sda3 1182609406 3907028991 2724419586 1.3T 5 Extended
/dev/sda5 1182609408 1280265657 97656250 46.6G 83 Linux
/dev/sda6 1478205440 1542199295 63993856 30.5G 82 Linux swap / Solaris
/dev/sda7 2268628992 3907028991 1638400000 781.3G 83 Linux
/dev/sda8 1542201344 2268618751 726417408 346.4G 83 Linux

Partition 3 does not start on physical sector boundary.
Partition table entries are not in disk order.

Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xf6fdb110

Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 2048 206847 204800 100M 7 HPFS/NTFS/exFAT
/dev/sdb2 206848 499918847 499712000 238.3G 7 HPFS/NTFS/exFAT
/dev/sdb3 1182609406 3907028991 2724419586 1.3T 5 Extended
/dev/sdb5 1182609408 1280265657 97656250 46.6G 83 Linux
/dev/sdb6 1478205440 1542199295 63993856 30.5G 82 Linux swap / Solaris
/dev/sdb7 1542201344 1932826343 390625000 186.3G 83 Linux
/dev/sdb8 2724618240 3907028991 1182410752 563.8G 83 Linux
/dev/sdb9 1932826624 2724607999 791781376 377.6G 83 Linux

Partition 3 does not start on physical sector boundary.
Partition table entries are not in disk order.

Disk /dev/sdg: 931.5 GiB, 1000202043392 bytes, 1953519616 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00261ddd

Device Boot Start End Sectors Size Id Type
/dev/sdg1 63 204796619 204796557 97.7G 7 HPFS/NTFS/exFAT
/dev/sdg2 * 204796620 723010251 518213632 247.1G 83 Linux
/dev/sdg3 723011584 1235009535 511997952 244.1G 7 HPFS/NTFS/exFAT
/dev/sdg4 1235011582 1843197951 608186370 290G 5 Extended
/dev/sdg5 1235011584 1644611583 409600000 195.3G 83 Linux

I am logged in to the sda7 installation now so I will reboot and run the blkid command and post it later.

Kevin

Revision history for this message
trigeek (kjaspan) said : 		#25

Here is the blkid output:
 blkid
/dev/sda1: LABEL="SYSTEM" UUID="F49C1AE3CB6928FA" TYPE="ntfs" PARTUUID="47ba187e-01"
/dev/sda2: LABEL="Windows10" UUID="3E1562AEE8601345" TYPE="ntfs" PARTUUID="47ba187e-02"
/dev/sda5: UUID="ba8b676d-604c-7712-c178-2fe538ff9545" TYPE="ext4" PARTUUID="47ba187e-05"
/dev/sda6: UUID="e8e98bcc-c555-1bd7-0ef7-0733b525314c" TYPE="swap" PARTUUID="47ba187e-06"
/dev/sda7: LABEL="Ubuntu primary" UUID="7425e72e-1e3e-754b-e1c1-724f00d33c98" TYPE="ext4" PARTUUID="47ba187e-07"
/dev/sda8: UUID="214e9383-fa91-4dc8-86f8-2c46725011f8" TYPE="ext4" PARTUUID="47ba187e-08"
/dev/sdb1: LABEL="SYSTEM" UUID="F49C1AE3CB6928FA" TYPE="ntfs" PARTUUID="f6fdb110-01"
/dev/sdb2: LABEL="Windows10" UUID="3E1562AEE8601345" TYPE="ntfs" PARTUUID="f6fdb110-02"
/dev/sdb5: UUID="ba8b676d-604c-7712-c178-2fe538ff9545" TYPE="ext4" PARTUUID="f6fdb110-05"
/dev/sdb6: UUID="e8e98bcc-c555-1bd7-0ef7-0733b525314c" TYPE="swap" PARTUUID="f6fdb110-06"
/dev/sdb7: LABEL="DownloadsBackup" UUID="84c12fcc-f006-a2f3-bb0b-e7946f913392" TYPE="ext4" PARTUUID="f6fdb110-07"
/dev/sdb8: UUID="af31156a-d1f8-476b-bb30-a847a1f67e49" TYPE="ext4" PARTUUID="f6fdb110-08"
/dev/sdb9: LABEL="Ubuntu_secondary" UUID="08818da9-3178-4d8e-906e-f777b27bf209" TYPE="ext4" PTTYPE="dos" PARTUUID="f6fdb110-09"
/dev/sdg1: LABEL="SYSTEM" UUID="94A818E1A818C3A0" TYPE="ntfs" PARTUUID="00261ddd-01"
/dev/sdg2: UUID="8f9d4eed-d4f6-4fd5-9fdd-c699bdadeb20" SEC_TYPE="ext2" TYPE="ext3" PARTUUID="00261ddd-02"
/dev/sdg3: LABEL="Windows7" UUID="52C8DCC9C8DCAD0B" TYPE="ntfs" PARTUUID="00261ddd-03"
/dev/sdg5: UUID="3262600a-1bc3-4ad8-baf2-967aa50eeed1" TYPE="ext4" PARTUUID="00261ddd-05"

Revision history for this message
trigeek (kjaspan) said : 		#26

So, should I try to see what happens if I run an upgrade or should I do a fresh install?

Revision history for this message
Manfred Hampl (m-hampl) said : 		#27

1. You have identical UUIDs on sda5/sdb5 and sda6/sdb6.
This is not good, because it is unpredictable which disk you access if you call it by UUID.

2. RE: "So, should I try to see what happens if I run an upgrade or should I do a fresh install?"
I still do not understand what you want to do with all those different systems.

Revision history for this message
trigeek (kjaspan) said : 		#28

I wondered about that. I will change the UUIDs.

The initial reason I installed the SSD was for speed and reliability. I would like to keep a second drive for backup. I had a lot of trouble with the HDD sold with this Dell and also the one on my previous PC, a Dell. So I'm a bit wary of relying too much on an HDD that may not last more than 3 years.

Revision history for this message
trigeek (kjaspan) said : 		#29

Well, I'm stunned!

After rebooting several times in the last few hours to swap between instances, including changing the duplicate UUIDs, I tried the following on a whim:

uname -a
Linux civet 4.4.0-63-generic #84-Ubuntu SMP Wed Feb 1 17:20:32 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
root@civet:~# lsb_release -r
Release: 16.04

I was amazed and looked at pavucontrol and saw it showed audio input and output. I tried Cheese and the camera worked.
I ran:
modprobe uvcvideo usbvideo gspca_main
and there was no error.

Just to do a sanity check I ran df -k and see:
/dev/sdb9 389546740 300034760 69701064 82% /
which means I am running off the SSD.

I tried a Skype test call and, although I could see a response to my voice on the pavucontrol and sounds did emanate from the Skype lady, it did not record my voice. This is neither in Skype for Linux Alpha or the regular Skype 4.3.0.37.

So we're really almost there!

Revision history for this message
trigeek (kjaspan) said : 		#30

Skype works with a USB headset.

Revision history for this message
trigeek (kjaspan) said : 		#31

I unplugged the headset and Skype works without it!!!!

Thanks to you, Manfred, and you too, Andrew for your help and persistence.

I'm closing this issue.

Revision history for this message
Manfred Hampl (m-hampl) said : 		#32

Happy to hear that finally sound and video are working.

Just a final comment:

You could do a cleanup on the installed kernel packages.
There is no need for two dozen versions of the kernel, usually two (the newest one and one for emergency backup purposes) are enough.

sudo apt-get --purge autoremove

might work.

Revision history for this message
trigeek (kjaspan) said : 		#33

I was busy cleaning up last night. I will run that command ASAP.

Once again, thanks Manfred.