Intel have released more microcode updates to replace the ones they rolled back:
https://downloadcenter.intel.com/download/27591/Linux-Processor-Microcode-Data-File?v=t
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Intel have released the fixed microcode -
https://downloadcenter.intel.com/download/27591/Linux-Processor-
Microcode-Data-File?v=t
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741282
Title:
spectr
The proposed package fails to install but does manage to build.
This is the install log:
i915
leith@leith-xps:~$ sudo apt-get install bcmwl-kernel-source
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically instal
*** This bug is a security vulnerability ***
Public security bug reported:
According to http://nvidia.custhelp.com/app/answers/detail/a_id/4611 the
NVIDIA driver needs to be updated to 384.111 to fix the Spectre
vulnerabilities in the NVIDIA kernel modules (along with the upcoming
Kernel security
** Description changed:
According to http://nvidia.custhelp.com/app/answers/detail/a_id/4611 the
NVIDIA driver needs to be updated to 384.111 to fix the Spectre
vulnerabilities in the NVIDIA kernel modules (along with the upcoming
Kernel security patches).
I think this update should b
The buggy version I have:
linux-image-4.4.0-108-generic/xenial-security,now 4.4.0-108.131 amd64
[installed,automatic]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741934
Title:
Kernel trace with
What exact package version do I need for this fix?
My system auto-updated to the buggy kernel and crashed in the same
location as the original reporter.
For reference the system:
Motherboard: Asus P9D-I
BIOS: Version 1801
CPU: Intel(R) Xeon(R) CPU E3-1220 v3 @ 3.10GHz
--
You received this bug n
@jsalisbury are you sure the fixed version has been uploaded? Still not
getting any new kernel to replace the currently installed buggy one via
apt update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Thank you @jsalisbury. Sorry for my misunderstanding with the status
label.
I will keep an eye out for when the update arrives and I will just avoid
rebooting the server until then.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
For completeness here is a copy of the boot log I get (which I captured
over good ol RS232 port).
For reference the system:
Motherboard: Asus P9D-I
BIOS: Version 1801
CPU: Intel(R) Xeon(R) CPU E3-1220 v3 @ 3.10GHz
** Attachment added: "kernel boot log"
https://bugs.launchpad.net/ubuntu/+sourc
That looks like the same error I got after upgrading my server. I had to
reboot it and use the advanced boot options in GRUB to go back to the
old kernel.
It appears to the same issue as in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741934
--
You received this bug notification because
*** This bug is a security vulnerability ***
Public security bug reported:
Intel have finally released the updated microcode for the Spectre bug.
See https://downloadcenter.intel.com/download/27431/Linux-Processor-
Microcode-Data-File?v=t
>From the release note:
Intel Processor Microcode Packag
Should note the list seems to compare well with the only other list of
Spectre microcode versions I am aware of on
https://wiki.gentoo.org/wiki/Project:Security/Vulnerabilities/Meltdown_and_Spectre
** Also affects: intel
Importance: Undecided
Status: New
--
You received this bug notifi
@mdeslaur it seems that your package has one extra microcode compared to the
file on intel.com:
sig 0x000506c9, pf_mask 0x03, 2017-03-25, rev 0x002c, size 16384
According to https://packages.qa.debian.org/i/intel-
microcode/news/20180110T100610Z.html that file was removed compared to
the "unoffic
Ah I see, sorry for the confusion.
Just verified that the microcode.dat file in your PPA is identical to
the one on intel.com
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742364
Title:
Updated mi
Hi Saxon,
Do you know if this has been reported to NVIDIA?
Leith
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741807
Title:
NVIDIA Spectre attack fixes
To manage notifications about this bug go
Tried another test. In the monitor settings menu under Display there is
a option called "DP 1.2", by default it is set to Enabled. If I set it
to Disabled I get the PIP behaviour - Ubuntu detects the correct native
resolution and the image appears.
If I set it back to Enabled the bug comes back.
I have noticed some interesting behaviour when I use the Picture in
Picture mode on the screen.
With PIP turned off, I get the above issue with no output at the native
resolution.
If I enable PIP mode with my Android phone plugged into the MHL port
Ubuntu redetects the screen - and sets the nativ
Public bug reported:
Following on from https://answers.launchpad.net/ubuntu/+source/xserver-
xorg-video-intel/+question/270926
When I plug a Dell U3414W screen into my Dell XPS 13 9343 display port
the screen does not turn on when I enable it's native 3440 x 1440 in the
display settings.
Lower r
Public bug reported:
I installed fglrx via jockey (Alternative Drivers).
On reboot I got the message that X was running in low graphics mode.
Looking at the xserver log I can see there was a crash in fglrx_drv.so.
I tried fglrx-updates and it had the same crash.
I am running Ubuntu 14.04 x64 w
Google has several hits for swlDrmAllocateOffscreenMem+0xe so it looks
like I am not the only one finding this crash.
Can fglrx-updates be switched to a newer driver release? Perhaps ATI
have fixed this crash in a later version.
--
You received this bug notification because you are a member of U
Possibly the same as
https://bugs.launchpad.net/ubuntu/+source/x11-utils/+bug/1278097
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1400013
Title:
fglrx_drv.so crashes with HD 5450
To manage notifi
Is this issue related to the issue I am having with the Intel 7260 WiFi
on Ubuntu 14.04 Server?
I have found that on 11n mode the connection is very slow.
The latency to WiFi router varies wildly between 1 to 100ms. Also using
SSH over the connection is very laggy and slow.
If I disable 11n mode
I'm on 14.04 Server and I am having the same problem with a Huawei
E1762.
It was working fine until I installed the nut package (for my UPS) then
it would not modeswitch on boot which caused my wvdial configuration in
/etc/interfaces to fail to connect to the Internet at boot.
Unplugging and repl
I also had this problem with clonezilla-live-2.2.3-25-amd64.iso on
Ubuntu 14.04 64 bit.
However it successfully created a bootable Ubuntu Server 14.04
installation disk on the same USB drive.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
This should be increased for dual-stack at least.
What happens if IPv6 get configured first? Only leaves for one IPv4
address later.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/118930
Title:
Reso
Public bug reported:
I booted up the Ubuntu Server ARM64 installer USB stick on my Bananapi
BPI-R3 board which has a Mediatek MT7986 SoC CPU.
I used the device tree from
https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/mediatek/mt7986a-bananapi-
bpi-r3.dts and with U-boot's boote
I tested the Ubuntu 24.04 Server installer and that has the same issue -
the CONFIG_NET_VENDOR_MEDIATEK is not configured in it's 6.8 kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069001
Titl
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069001
Title:
Missing Mediatek Ethernet drivers
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069001
Title:
Missing Mediatek Ethernet drivers
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-
I re-compiled the Ubuntu 6.8 kernel with the Mediatek net module
enabled.
However I ran into problems with the MDIO port which was preventing the
mt7530-mdio driver from setting up the MT7531 switch chip on the board.
I was seeing errors like:
[ 17.353755] mt7530-mdio mdio-bus:1f: failed to rea
31 matches
Mail list logo
