I did some poking around to see if I could figure out the root cause. I
found there are a whole lot of differences between doing a fresh install
of 16.04 and upgrading from 14.04 to 16.04 in terms of how the system is
actually setup, so a quick let's try to find the one thing off was not
going to
A baseline test I did was to update both a VM with a fresh install of
Ubuntu 16.04 and my laptop where I upgraded from 14.04 to 16.04. With
both systems up to date (March 25th, 2017) I tried to install the the
latest Nvidia 375 drivers. It installed on the VM (though it is kind of
worthless here)
Scott, I tried the same things and got more or less the same result.
The older drivers compile, but the machine crashes early in boot. If I
remember correctly, this was the case all the way up to 364. Anything
above, and I tried all the way up to 375, and it won't compile. I
suspect the older dr
I spent some time going through posts and trying various things. The
best I can reckon from all information gathered so far is something
about the upgrade process from 14.04 to 16.04 trips things up for the
Nvidia driver build. If Ubuntu 16.04 is installed from scratch, people
report it works, bu
Public bug reported:
The default selected nvidia driver 367 does not work in Ubuntu 16.04
64-bit. Hangs on build. Ran killall make in order to get updates to
complete.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: nvidia-367 (not installed)
ProcVersionSignature: Ubuntu 4.4.0-47.68-g
[solved] I seem to have found and fixed the problem and so have some
confirmation I was on the right track in my previous post. Specifically
in file common.c line 3328 I changed:
if (ioctl(s, ioctl_cmd, &req)) {
debug_printf(LOG_NOTICE, FNAME, "failed to %s an address on %s: %s",
I made some headway in figuring this out. One thing I did not
understand was T1 and T2 time and so was looking at the logs at the
vltime hour mark. The proper place to be looking for the first error
was at the T1 mark when the renew operation takes place. At this point
the following happens in t
I noticed going through the avahi docs that this is used by Apple
apparently. Also Cox says there is a compatibility issue with the Apple
Airport Extreme and IPv6 failing after a day with the resolution being
restart the device. My issue is the IPv6 update for the subnet fails
after 24 hours or s
Got distracted for a bit, but finally got some testing done. It looks
like I was only partially right in that the display formatter was wrong,
so now I am seeing the correct time displayed. There is still something
going wrong with the dhcpv6 subnet update. Will have to spend more time
to proper
I have found evidence that the wide-dhcpv6 version in Ubuntu 14.04 at least was
written on a 32-bit architecture and never properly redesigned for a 64-bit
compilation. The evidence for this found in the source code goes as follows:
1. Consistent use of the printf formatter %ul for 32-bit int fi
If it helps, I have been documenting my setup in a templated format
here: http://ubuntuforums.org/showthread.php?t=2279612
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1559741
Title:
wide-dhcpv6 cl
No. As I am understanding the linked documentation, if you are setting
up a wide-dhcpv6 server, this can be specified. However seeing I am not
an ISP, but instead a customer, I am relegated to being a client and
specifying these parameters do not seem to be an option for the client.
Especially wi
Public bug reported:
This is on Ubuntu 14.04 LTS 64-bit with the last update done on
03/09/2016.
I setup wide-dhcpv6 client on my home network to grab IPv6 addresses
from my ISP. The /128 address for my firewall is fine and after 24
hours I see in the logs the address just for this external inte
I need to multiplex on a USB sound device and this doesn't seem to work
with the ALSA / OSS tangle, plus it really helps to control the volume
levels of each application. However with Pulsaudio having broken mic
support across the board (tried three different devices and even more
are listed on th
I figured out a way to get things working. I completely de-installed
the -16 kernel and modules and such and re-installed from the command
prompt `apt-get install kernel-generic`
--
latest kernel(2.6.20-16.28) update gives boot problems
https://bugs.launchpad.net/bugs/117314
You received this bu
I recently ran the update from 6.10 to 7.04 and on first boot I had options
between kernel 2.6.20-16-generic and 2.6.20-15-386.
Kernel 2.6.20-15-386 works fine.
Kernel 2.6.20-16-generic does not boot at all. By default on the splash screen
I get a thin sliver on the progress bar and after leavin
16 matches
Mail list logo
