** Also affects: elementaryos
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/644898
Title:
required kernel toshiba support not enabled
Status
Same experience as #40 after installing updates on 16.04 today.
I already have the workaround from #4 applied.
The workaround from #35 appears to still work, thankfully.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
http
I can confirm that this bug affects me as well with -29, but not with -24.
I tried the 03131102 mainline kernel, but the DKMS step failed for nvidia-337
with that one.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https
The bug still occurs (and the posted workaround still applies) with
kernel 3.13.0-24.47.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
I had the same issue on a server that has been running Ubuntu 12.04 LTS
without a single problem for over two years.
After upgrading to linux-image-3.2.0-64-generic on the system with a
Supermicro X9SCM mainboard, two HighPoint RocketU 1144A USB 3.0
controllers and at least one USB 3.0 disk attach
I observed the udevd loop with only one Western Digital My Passport 0748
2TB USB 3.0 disk connected.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1328984
Title:
[Dell PowerEdge R510] R
Missed comment #9. :-|
The workaround is still required in 14.04, using nvidia-337 from
ppa:xorg-edgers.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1243897
Title:
[MacBookPro10,1] b
I experienced this problem as well, with 340.24-0ubuntu1~xedgers14.04.1.
Disabling the FXAA setting in nvidia-settings and restarting X worked around it
for me.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
ht
FWIW, it looks like the windows drivers at
http://www.killernetworking.com/support/driver-downloads contain patch
and ramp files that look like they should match (at least, the names are
correct). However, the binary format doesn't appear to match the other
patch and ramp files (e.g. the last 8 byt
I got this after accidentally starting the bluetooth service while playing
audio via a2dp.
The hackaround from #4 worked for me.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1490349
Tit
I was using 310 in 13.04 (and possibly 304 before that; can't remember)
- in that case, the brightness control worked intermittently for each
suspend/resume cycle. The behavior has become consistent in 13.10;
unfortunately, it's consistently the "not responding" case.
I can't even get X to start (
Re: #7
Yes!
Is this something that's safe to put into a startup script for now, or should I
just run it when I need to?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1243897
Title:
Ma
Public bug reported:
After upgrade from 13.04 to 13.10, setting the screen brightness has no
effect (either via the hotkeys, "Brightness & Lock" settings, or via
/sys/devices/pnp0/00:07/backlight/gmux_backlight/brightness ).
I'm using nvidia driver 319.32-0ubuntu7.
I've tried Option "RegistryDwor
The nvidia driver wrapper doesn't build with that kernel (make.log
attached).
** Attachment added: "DKMS make log for nvidia 319.32-0ubuntu7"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1243897/+attachment/3890088/+files/make.log
** Tags added: kernel-unable-to-test-upstream
** Cha
14 matches
Mail list logo
