This bug needs to be moved from the alsa-driver/pulseaudio thread and
moved to either nouveau or nvidia packages.
The issue why this is not fixed as far as I can figure out is because
the address modified with the setpci command is not documented by nvidia
and thus cannot be added to the official
@WinEunuchs2Unix
Cool, good to hear this also works for older nVidia cards and on older Ubuntu
versions!
Your suggestion to adjust the paths to /usr/local/bin/ is a good one, I
had the test script in /root/ and didn't bother to move it yet ;)
The screen flickering - do you notice this as well if
I have a very useful update on the Skylake/nvidia GTX1060 case where the
HDMI Audio device does not show up in lspci. Based on information found
on the NVidia Developer forum, I was able to get my HDMI audio device
show up in Ubuntu 17.10 as per my posting there:
https://devtalk.nvidia.com/default
I am not sure this is an alsa-specific bug. Looks to be more of an issue
with the Nvidia card and the way it handles HDMI audio. This also
affects a BTO 15CL76 notebook (I7-6700HQ / GTX1060) set in DISCRETE
mode. No HDMI audio device shows up at all. The active nvidia driver (as
of writing) is nvid
*** This bug is a duplicate of bug 1289440 ***
https://bugs.launchpad.net/bugs/1289440
The bug has been fixed in the newer nvidia graphics drivers (304 and
311) but it is still not fixed in the 173 package:
Loading new nvidia-173-173.14.39 DKMS files...
First Installation: checking all kernel
Sorry, I have migrated away from md-raid in favor of hardware raid at
the time of this bug and have not rebuild any system to use md-raid
since. With hardware raid and the same disks the problem does not occur.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
I can confirm Carroarmato0 his solution indeed works :) I was able to
change the hostname as well using the file
/var/lib/bluetooth/[MACaddress]/config
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989
I can confirm telepathy does not want to connect to MSN... This started
a few weeks ago, I'm running ubuntu 11.04, with telepathy-butterfly
0.5.15-1.
It does not show any errors, it just stays in "Connecting..." state
indefinitely.
--
You received this bug notification because you are a member o
Today after upgrading python-papyon to the latest version
(0.5.5-1ubuntu1.4) the issue is resolved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/887484
Title:
empathy not connect to msn,no cam,no a
Sorry for the bump but dnsmasq is still enabled by default and cannot be
removed without removing network-manager.
I ran into the issue where dnsmasq introduced a security problem when
running VPN connections. For security reasons all DNS traffic was
supposed to be flowing to the DNS server pushed
Sorry for the bump but maybe something to keep in mind with this issue.
Some reading up on the internet has gotten me on a different track about
the loss of the RAID Arrays in my old setup:
It seems starting with kernels newer then 2.6.24 there might be a change
in the timers mdadm uses to declare
Installed 2.6.38-999-generic AMD64 kernel and tried setting MTU. Here
are the results:
root@brand:~# uname -a
Linux brand 2.6.38-999-generic #201102260905 SMP Sat Feb 26 09:10:54 UTC 2011
x86_64 GNU/Linux
root@brand:~# ifconfig eth0 mtu 4078
root@brand:~# ifconfig eth0 mtu 4079
SIOCSIFMTU: Invali
OK, did some more research on this MTU value, it turns out the 82577LM
controller is limited to 4k Jumbo frames. Tried it again in the current
stable release kernel and I can set the MTU to 4078 using the normal
kernel as well.
Not a bug, a hardware limitation.
--
You received this bug notificat
Public bug reported:
I have a Lenovo ThinkPad W510 running Ubuntu 10.10 (completely up-to-
date with the repo's). Recently I tried enabling Jumbo Frames on the
Intel 82577LM Gigabit ethernet controller which resides in this laptop.
According to the Intel website, this device supports Jumbo Frames
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/715331
Title:
e1000e / Intel 82577LM Gbit NIC Jumbo Frames not working.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu
Same problem here using a Nvidia Quadro FX 880M card.
"Driver is activated but not currently in use."
Using glxgears, it said it did about 4000 fps on the command line but on
the display the gears are only moving at about 1 frame every 5 seconds.
glxinfo states direct rendering is enabled.
--
Y
I'm running Ubuntu 11.04 on a Lenovo ThinkPad W510 (Nvidia Quadro FX 880M
graphics card).
- setpci does nothing
- using /proc/acpi tables to adjust display brightness doesn't work
- Using /sys/class/backlight/... also doesn't work
All of the above still aren't working if I pass the acpi_backlight=
I don't manually reset the device. This is done automatically, after the
reset it renegotiaties the NIC speed too 100 full duplex and resumes
operation. It might be that I also experience loss but my network load
is so low it isn't noticeable.
I've bypassed the problem as well now by removing the
Public bug reported:
Binary package hint: linux-image-2.6.32-24-generic-pae
I upgraded from Ubuntu 8.04LTS to 10.04LTS last weekend, the system has
been running fine untill today. For some reasons the webserver/mysql
server stopped responding and I checked the console and noticed it being
flooded
** Attachment added: "lspci -vvv output"
http://launchpadlibrarian.net/53108844/lspci_vvv.txt
--
md raid5 set inaccessible after some time.
https://bugs.launchpad.net/bugs/613872
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
Dmesg output from last boot.
** Attachment added: "dmesg output"
http://launchpadlibrarian.net/53108878/dmesg.txt
--
md raid5 set inaccessible after some time.
https://bugs.launchpad.net/bugs/613872
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Ok, the problem occurred again... However for some reason it did not
capture the errors on the USB drive. I did happen to have a console open
at the time and managed to get the response from a dmesg output. It was
swamped with the following text:
[358579.557869] metapage_write_end_io: I/O error
[3
Managed to get the system up and running again. Had to reassemble all
mdadm raid arrays using a live CD. After reassembling all arrays I
rebooted back into the operating system and had to reboot three times to
get it to work again.
First reboot, it prompted it noticed a size change from 0 to for
Took less then 24 hours this time. However I did manage to capture dmesg
output this time. See the attachment for the full log, here's the
snippet how it goes wrong:
mdadm detects a drive timeout (these soft hangs of the hard drives have
been present ever since day one and never caused any issues)
Hmm, I have the same issue, however I do not have the option of adding
additional LAN cards. However the bug is not 'fatal' for my server
(Ubuntu 10.04LTS), it recovers without issues after the nic reset
occurs. Can't even detect packet loss when it happens! I did notice this
bug happening to the i
Public bug reported:
[Impact]
Built-in microphone of the laptop is not detected and thus does not work.
[Fix]
None identified so far.
[Test Case]
Have Ubuntu 22.04 LTS installed on an Asus Vivobook Go E1404FA, using the 6.5
HWE kernel.
Open the Sound settings and set the device "Family 17h [...
26 matches
Mail list logo
