Public bug reported:
With LinUX Images/-Extras 4.15.0-22-generic, 4.13.0-43-generic,
4.8.0-58-generic, 4.8.0-56-generic, and 4.4.0-127-generic installed,
sudo dpkg-reconfigure linux-firmware returns the following to Console:
update-initramfs: Generating /boot/initrd.img-4.15.0-22-generic
update-i
apport information
** Package changed: linux (Ubuntu) => linux-firmware (Ubuntu)
** Tags added: apport-collected third-party-packages xenial
** Description changed:
With LinUX Images/-Extras 4.15.0-22-generic, 4.13.0-43-generic,
4.8.0-58-generic, 4.8.0-56-generic, and 4.4.0-127-generic inst
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1773476/+attachment/5144521/+files/ProcEnviron.txt
** Tags removed: apport-collected bionic third-party-packages
--
You received this bug notification because you are a member of Kernel
Packages, which
** Changed in: linux-firmware (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1773476
Title:
linux-firmware 1.157.19 attempts to g
Update: A purge and reinstall of linux-firmware produces same results.
Summary therefore:
Reproducible: Always
Steps to reproduce: sudo apt install (--reinstall) linux-firmware or sudo
dpkg-reconfigure linux-firmware.
Actual results, excepting actually installed Kernel Image packages:
update-
Observed sequence of sbins when software-updater called apt-get upgrade
linux-firmware: Cross-checking initramfs-tools and depmod for any
misbehaviors that might exacerbate what I've observed.
DIOSCOVERED POINT TO INVESTIGATE: Potential for Dependency this Bug on
Bug #701578 "purging a kernel so
** Summary changed:
- linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56,
/boot/initrd.ing-4.8.0 when no corresponding vmlinuz present
+ linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56,
/boot/initrd.img-4.8.0 when no corresponding vmlinuz present
--
Y
I've an emachines®/acer® EL1210-09 (Advance Micro Devices Inc. Athlon
LE-1620 (P/N ADH1620IAA5DH); nVIDIA® nForce® 780a SLI with planar C77 a2
GPU; nVIDIA® GF119 a1 GPU on PCIe 2.0 x16 slot). The system DMesg
predictably detects no EISA resources on probing platform eisa.0, so
EISA.c and related h
This hang on shutdown and/or reboot is NOT confined to portables. I
encountered the issue installing xubuntu™ 18.04-LTS on an
emachines®/acer® EL1210-09 (2.3 GHz Advanced Micro Devices® Athlon®
LE-1620; nVIDIA® nFORCE® 720 chipset; 2 x 2 GiB DDR2 main memory) with a
Shuttle® PSU upgrade (PC631
I encountered this issue installing xubuntu™ 18.04-LTS on an
emachines®/acer® EL1210-09 (2.3 GHz Advanced Micro Devices® Athlon®
LE-1620; nVIDIA® nFORCE® 720 chipset; 2 x 2 GiB DDR2 main memory) with a
Shuttle® PSU upgrade (PC631 in for stock 220W LITEON®) and the
planar C77 geForce® 64-bit GPU
Update: acpi=off only got me to a timestamped kernel message
"reboot:System halted". acpi=force had no effect. Repeating report to
Bug 1776616, which is specifically relevant to Kernel 4.15-n-generic on
xubuntu™ 18.04-LTS.
--
You received this bug notification because you are a member of Kerne
Update: nVIDIA® geForce® driver 340.107 for the C77 GPU (package:
nvidia-340) got to a successful power-down. Be advised that Packages
nvidia-n are to be reserved for nVIDIA® nFORCE® MCP chipsets such as the
MCP78 northbridge my EL1210-09; intel®, AMD®, and VIA® chipsets require
different solutio
Update: Issue worked around with nVIDIA® geForce® driver 340.107 for
C77 GPU in MCP78 northbridge (package:nvidia-340). Repeating report to
Bug 1776616.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
13 matches
Mail list logo
