[Kernel-packages] [Bug 1798071] Re: Suspension fails and re-login screen is black
Suspension is handled by the kernel, not by artwork (and it's buggy depending on the hardware). Similarly, my guess is that any graphical issues you had are related to the kernel modules, as well. Either way, it doesn't seem like this is going anywhere, so Incomplete it is. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: lubuntu-artwork ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1798071 Title: Suspension fails and re-login screen is black Status in linux package in Ubuntu: Incomplete Bug description: Hello, i am experiencing couple of bugs on Lubuntu 16.04 LTS while it being installed and used on my old Dell D600 laptop. Bugs: 1) When trying to suspend PC (Start menu, Logout, Suspend) it very often happen that suspension is not realized and it just locks the session. When i attempt suspend again, the same and on the logout menu i see: GDBus.Error:org.freedesktop.login1.OperationInProg ress: There's already a shutdown or sleep operation in progress To fix it i have to login and execute "sudo pkill -f suspend" which almost instantly suspend the PC. More detailed explanation with error message too: https://internetlifeforum.com/showthread.php?t=10600 2) sometimes when i get back to PC and awake it, screen is locked, the screen stays black even i move mouse or type on keyboard, but when i move mouse, then type password, hit enter, screen start showing image (logged in desktop). │Linux: Linux version 4.4.0-138-generic (buildd@lgw01-amd64-037) ││Build: (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.10) ) ││Release : 4.4.0-138-generic ││Version : #164-Ubuntu SMP Wed Oct 3 15:02:00 UTC 2018 ││cpuinfo: model name : Intel(R) Pentium(R) M processor 1.60GHz Computer: Dell D600 (https://www.dell.com/downloads/us/products/latit/d600_spec.pdf) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1794922] Re: lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci 0000:00:a.7: dma_direct_map_sg: overflow 0x000000016e3f3000+2048 of device mask ffffffff" repeats
18.10 is no longer supported.
** Changed in: linux (Ubuntu)
Status: Confirmed => Won't Fix
--
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/1794922
Title:
lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci :00:a.7:
dma_direct_map_sg: overflow 0x00016e3f3000+2048 of device mask
" repeats
Status in linux package in Ubuntu:
Won't Fix
Status in linux package in Debian:
Fix Released
Bug description:
-- Background --
Testing the x86 (32bit) ISO image on various machines.
After zsync download, the thumb-drive is tested ("check disk for
defects") & passes; and worked fine on two systems today (dell d610 &
hp dx6120), however
-- Issue --
dell 755 (desktop) & hp dc7700 (small form factor) it just sits at
lubuntu plymouth screen.
switching to messages, it's just the following repeating
// on dell 755
"ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x00016e3f3000+2048
of device mask "
// on hp dc7700
"ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x000162317000+2048
of device mask "
NOTE: I can't copy/paste from systems, as it never completes boot; I
left it >30mins (on 755) & it just kept repeating message. I've
manually typed it; so typo's could have been made.
A discussion on #lubuntu-devel provided a possible cause (Thank you
Walter!) -
---
guiverc: lyorian:
http://debian.2.n7.nabble.com/Bug-908924-dma-direct-map-sg-overflow-on-USB-access-after-upgrade-to-kernel-4-18-td4387757.html
seems like it's a usb issue of some kind with 4.18
---
This fits because whilst I do my testing mostly on d610 & t43 (no
issues today), I'd tested Lubuntu 18.10 before on the dell 755 with no
issues. My last test was also long enough ago to be on 4.17 kernel
(suspicion)
---
// on hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
[ 99.99] ehci-pci :00:1d.0:dma_direct_map_sg: overflow
0x000223ad7000+2048 of device mask
errors on booting 'live' (see #16) for real
BUT
the same ISO works fine on same box when a virtual machine (Virtual box on a
GNU/Linux host and "Type: Linux Version: Ubuntu (32-bit)" virtual machine)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794922/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829805] Re: Lubuntu Eoan Daily Image fails to boot after install on KVM
The fix is now released. Spinning up a new ISO as we speak. calamares-settings-ubuntu (1:19.10.2) eoan; urgency=medium * Fix initramfs job failing. Thanks to TJ for the fix! (LP: #1829805) * Move before_bootloader_mkdirs process before initramfs. * Workaround bug in update-initramfs::get_sorted_versions() with shellprocess. -- Walter Lapchynski Wed, 19 Jun 2019 19:32:14 -0700 ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Fix Released ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Critical ** Changed in: initramfs-tools (Ubuntu) Assignee: (unassigned) => Walter Lapchynski (wxl) -- 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/1829805 Title: Lubuntu Eoan Daily Image fails to boot after install on KVM Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Bug description: Context: The live environment appears to function properly and install proceeds as expected with no noticeable errors. Expected results: After a system reboot the virtual machine enters the graphical environment Actual Results: After rebooting the virtual machine a kernel panic error screen appears. I will attempt to attach the screenshot after submitting this bug report. The collected data is from the live environment as the installed environment will not boot. lubuntu@lubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Eoan Ermine (development branch) Release:19.10 Codename: eoan lubuntu@lubuntu:~$ apt-cache policy grub2 grub2: Installed: (none) Candidate: 2.02+dfsg1-12ubuntu2 Version table: 2.02+dfsg1-12ubuntu2 500 500 cdrom://Lubuntu 19.10 _Eoan Ermine_ - Alpha amd64 (20190519) eoan/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu eoan/universe amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CasperVersion: 1.407 CurrentDesktop: LXQt Date: Tue May 21 00:30:39 2019 LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190519) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1829805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829805] Re: Lubuntu Eoan Daily Image fails to boot after install on KVM
We got a potential fix thanks to TJ that seems to be working wonderfully from what I can ascertain: https://phab.lubuntu.me/D15 Download the raw diff, cd /etc/calamares, sudo patch --strip 2 < /path/to/diff, and install like normal. Done! -- 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/1829805 Title: Lubuntu Eoan Daily Image fails to boot after install on KVM Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Bug description: Context: The live environment appears to function properly and install proceeds as expected with no noticeable errors. Expected results: After a system reboot the virtual machine enters the graphical environment Actual Results: After rebooting the virtual machine a kernel panic error screen appears. I will attempt to attach the screenshot after submitting this bug report. The collected data is from the live environment as the installed environment will not boot. lubuntu@lubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Eoan Ermine (development branch) Release:19.10 Codename: eoan lubuntu@lubuntu:~$ apt-cache policy grub2 grub2: Installed: (none) Candidate: 2.02+dfsg1-12ubuntu2 Version table: 2.02+dfsg1-12ubuntu2 500 500 cdrom://Lubuntu 19.10 _Eoan Ermine_ - Alpha amd64 (20190519) eoan/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu eoan/universe amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CasperVersion: 1.407 CurrentDesktop: LXQt Date: Tue May 21 00:30:39 2019 LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190519) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1829805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816394] Re: Ubuntu 19.04 qa:test - suspended system resumed without audio (i fixed via add of pavucontrol)
OH! Interesting. Three more questions: 1. Before installing/trying pavucontrol what else did you try? 2. When you resume with no audio and have pavucontrol installed already, if you go to the profile selection tab, is it in the "off" state? 3. Am I correct that you tested this and had it occur in both Lubuntu and Ubuntu? Did you test with any other flavors? -- 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/1816394 Title: Ubuntu 19.04 qa:test - suspended system resumed without audio (i fixed via add of pavucontrol) Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 19.04 QA-Test (LIVE x86_64) Dell optiplex d755, (c2d-e8300, 8gb, Radeon HD 2400 PRO/XT) Two dell displays, left is landscape, right is portrait This live test had two packages added: `vim` & `ubuntu-restricted- extras` Background: I added ubuntu-restricted-extras so I could run requested test on this system which had me streaming videos from utube - it was required to get around H264 errors (vim because I can't cope with other editors & added `multiverse` to my sources. Issue: With firefox streaming ABC News 24 (local AU news) I suspended machine. Waited Awoke machine - everything resumed as expected .. Some circling was apparent on firefox before picture resumed, however no sound. I was unable to fix it using any tools installed - to fix I `sudo apt install pavucontrol`, went to Configuration (or last tab) and Profile=Off on the drop-down menu, then returned to Profile=AnalogStereo Duplex. This is something I do on occasion for this machine on installed system or other machines I use. This is really a minor issue, & may not be an issue on an installed system (though I come across it semi-regularly & just live with it). In regular use I pause/stop sound & know this makes this almost a non- issue (almost never happens when sound isn't playing). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-power-manager 3.30.0-2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CasperVersion: 1.402 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 18 11:01:59 2019 LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816394] Re: Ubuntu 19.04 qa:test - suspended system resumed without audio (i fixed via add of pavucontrol)
What are you doing with pavucontrol that "fixes" it? With that last comment, it's clear it's not the installation that solves the problem. You're doing something with the program but I'm not sure what. Also you said that you tried several things to fix it that didn't work. What were they? ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1816394 Title: Ubuntu 19.04 qa:test - suspended system resumed without audio (i fixed via add of pavucontrol) Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 19.04 QA-Test (LIVE x86_64) Dell optiplex d755, (c2d-e8300, 8gb, Radeon HD 2400 PRO/XT) Two dell displays, left is landscape, right is portrait This live test had two packages added: `vim` & `ubuntu-restricted- extras` Background: I added ubuntu-restricted-extras so I could run requested test on this system which had me streaming videos from utube - it was required to get around H264 errors (vim because I can't cope with other editors & added `multiverse` to my sources. Issue: With firefox streaming ABC News 24 (local AU news) I suspended machine. Waited Awoke machine - everything resumed as expected .. Some circling was apparent on firefox before picture resumed, however no sound. I was unable to fix it using any tools installed - to fix I `sudo apt install pavucontrol`, went to Configuration (or last tab) and Profile=Off on the drop-down menu, then returned to Profile=AnalogStereo Duplex. This is something I do on occasion for this machine on installed system or other machines I use. This is really a minor issue, & may not be an issue on an installed system (though I come across it semi-regularly & just live with it). In regular use I pause/stop sound & know this makes this almost a non- issue (almost never happens when sound isn't playing). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-power-manager 3.30.0-2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CasperVersion: 1.402 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 18 11:01:59 2019 LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1794922] Re: lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci 0000:00:a.7: dma_direct_map_sg: overflow 0x000000016e3f3000+2048 of device mask ffffffff" repeats
So you have EHCI enabled on the virtual machines? Without it, they're
not testing similar conditions
Based on an earlier comment I should point out that if you look at those kernel
messages and ignore the timestamp (equivalent of `dmesg --notime`), you note
they all start with "ehci-pci," which is a reference to the kernel driver for
the 2.0 version of USB:
https://github.com/torvalds/linux/blob/master/drivers/usb/host/ehci-pci.c
By default EHCI is not enabled in VirtualBox, even with the extension
pack that is required to support it installed. Given that the problem
seems to be related to EHCI, this will need to be selected first.
With that in place, if there is no fail, it also may be related to the
specific USB device you have. You should plug it in ("add a filter" in
VB parlance) to the virtual machine.
If that still fails to fail, you might want to try to boot from the USB but
that's a little trickier:
https://askubuntu.com/questions/693719/how-to-boot-from-a-usb-drive-in-virtualbox
I'll note that bug I mentioned before seems to point at this as the fix:
https://lkml.org/lkml/2018/10/14/62
I still suspect the kernel as it seems that the test you did to confirm
it's not the kernel you performed on a 64 bit kernel. The symptoms seem
to suggest 32 bit, as does that patch.
--
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/1794922
Title:
lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci :00:a.7:
dma_direct_map_sg: overflow 0x00016e3f3000+2048 of device mask
" repeats
Status in linux package in Ubuntu:
Confirmed
Status in linux package in Debian:
Unknown
Bug description:
-- Background --
Testing the x86 (32bit) ISO image on various machines.
After zsync download, the thumb-drive is tested ("check disk for
defects") & passes; and worked fine on two systems today (dell d610 &
hp dx6120), however
-- Issue --
dell 755 (desktop) & hp dc7700 (small form factor) it just sits at
lubuntu plymouth screen.
switching to messages, it's just the following repeating
// on dell 755
"ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x00016e3f3000+2048
of device mask "
// on hp dc7700
"ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x000162317000+2048
of device mask "
NOTE: I can't copy/paste from systems, as it never completes boot; I
left it >30mins (on 755) & it just kept repeating message. I've
manually typed it; so typo's could have been made.
A discussion on #lubuntu-devel provided a possible cause (Thank you
Walter!) -
---
guiverc: lyorian:
http://debian.2.n7.nabble.com/Bug-908924-dma-direct-map-sg-overflow-on-USB-access-after-upgrade-to-kernel-4-18-td4387757.html
seems like it's a usb issue of some kind with 4.18
---
This fits because whilst I do my testing mostly on d610 & t43 (no
issues today), I'd tested Lubuntu 18.10 before on the dell 755 with no
issues. My last test was also long enough ago to be on 4.17 kernel
(suspicion)
---
// on hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
[ 99.99] ehci-pci :00:1d.0:dma_direct_map_sg: overflow
0x000223ad7000+2048 of device mask
errors on booting 'live' (see #16) for real
BUT
the same ISO works fine on same box when a virtual machine (Virtual box on a
GNU/Linux host and "Type: Linux Version: Ubuntu (32-bit)" virtual machine)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794922/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1794922] Re: lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci 0000:00:a.7: dma_direct_map_sg: overflow 0x000000016e3f3000+2048 of device mask ffffffff" repeats
And did the virtual machine test fail?
--
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/1794922
Title:
lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci :00:a.7:
dma_direct_map_sg: overflow 0x00016e3f3000+2048 of device mask
" repeats
Status in linux package in Ubuntu:
Confirmed
Status in linux package in Debian:
Unknown
Bug description:
-- Background --
Testing the x86 (32bit) ISO image on various machines.
After zsync download, the thumb-drive is tested ("check disk for
defects") & passes; and worked fine on two systems today (dell d610 &
hp dx6120), however
-- Issue --
dell 755 (desktop) & hp dc7700 (small form factor) it just sits at
lubuntu plymouth screen.
switching to messages, it's just the following repeating
// on dell 755
"ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x00016e3f3000+2048
of device mask "
// on hp dc7700
"ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x000162317000+2048
of device mask "
NOTE: I can't copy/paste from systems, as it never completes boot; I
left it >30mins (on 755) & it just kept repeating message. I've
manually typed it; so typo's could have been made.
A discussion on #lubuntu-devel provided a possible cause (Thank you
Walter!) -
---
guiverc: lyorian:
http://debian.2.n7.nabble.com/Bug-908924-dma-direct-map-sg-overflow-on-USB-access-after-upgrade-to-kernel-4-18-td4387757.html
seems like it's a usb issue of some kind with 4.18
---
This fits because whilst I do my testing mostly on d610 & t43 (no
issues today), I'd tested Lubuntu 18.10 before on the dell 755 with no
issues. My last test was also long enough ago to be on 4.17 kernel.
I'll add `lshw` files for the two failed systems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794922/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1794922] Re: lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci 0000:00:a.7: dma_direct_map_sg: overflow 0x000000016e3f3000+2048 of device mask ffffffff" repeats
Sorry to repeat myself if I'm doing so but there's a lot to scroll
through here (feel free to summarize your findings by editing the
description), but does this occur with a 64 bit image?
--
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/1794922
Title:
lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci :00:a.7:
dma_direct_map_sg: overflow 0x00016e3f3000+2048 of device mask
" repeats
Status in linux package in Ubuntu:
Confirmed
Status in linux package in Debian:
Unknown
Bug description:
-- Background --
Testing the x86 (32bit) ISO image on various machines.
After zsync download, the thumb-drive is tested ("check disk for
defects") & passes; and worked fine on two systems today (dell d610 &
hp dx6120), however
-- Issue --
dell 755 (desktop) & hp dc7700 (small form factor) it just sits at
lubuntu plymouth screen.
switching to messages, it's just the following repeating
// on dell 755
"ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x00016e3f3000+2048
of device mask "
// on hp dc7700
"ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x000162317000+2048
of device mask "
NOTE: I can't copy/paste from systems, as it never completes boot; I
left it >30mins (on 755) & it just kept repeating message. I've
manually typed it; so typo's could have been made.
A discussion on #lubuntu-devel provided a possible cause (Thank you
Walter!) -
---
guiverc: lyorian:
http://debian.2.n7.nabble.com/Bug-908924-dma-direct-map-sg-overflow-on-USB-access-after-upgrade-to-kernel-4-18-td4387757.html
seems like it's a usb issue of some kind with 4.18
---
This fits because whilst I do my testing mostly on d610 & t43 (no
issues today), I'd tested Lubuntu 18.10 before on the dell 755 with no
issues. My last test was also long enough ago to be on 4.17 kernel.
I'll add `lshw` files for the two failed systems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794922/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795092] Re: xubuntu 18.10 daily image (x86) fails to boot - initramfs
Thanks for all the testing, Chris. It leaves me a little baffled. That said, to Joseph et al, two questions: 1. This seems to be the same messages from 1794922 but slightly different symptoms. Should they be considered as the same? 2. With the kernel apparently working in Bionic, that suggests some sort of regression in some component outside the kernel that is calling on the USB. What might be likely candidates? -- 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/1795092 Title: xubuntu 18.10 daily image (x86) fails to boot - initramfs Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: x86 daily image (32bit) XUBUNTU 18.10 - booted & ran fine on dell latitude d610 - booted & ran fine on ibm thinkpad t43 fails on - hp dc7700 small form factor desktop - dell 755 desktop - lenovo thinkpad x201 I don't get the "try xubuntu / install xubuntu" screen, instead it eventually drops to "BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu4) built-in shell (ash) Enter 'help' for a list of built-in commands (initramfs) Unable to find a medium containing a live file system Note: I typed the messages in so typos may exist I suspect it's the same issue as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794922 where Walter (wxl) gave a possible link to http://debian.2.n7.nabble.com/Bug-908924-dma-direct-map-sg-overflow- on-USB-access-after-upgrade-to-kernel-4-18-td4387757.html I've been testing xubuntu 18.10 daily images for awhile (but not logging on qa-tracker - my bad, sorry!!!) without issue on t43 & d610, and only rarely booting on other boxes (like 755/dc7700/..) It may have been ~15-20 days since last tested on dell 755; but it worked fine back then (& prior) but due to my QA-tracking omission, we can't be exact - sorry again! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1794922] Re: lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci 0000:00:a.7: dma_direct_map_sg: overflow 0x000000016e3f3000+2048 of device mask ffffffff" repeats
Maybe installing in a virtual machine might be good idea?
--
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/1794922
Title:
lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci :00:a.7:
dma_direct_map_sg: overflow 0x00016e3f3000+2048 of device mask
" repeats
Status in linux package in Ubuntu:
Confirmed
Status in linux package in Debian:
Unknown
Bug description:
-- Background --
Testing the x86 (32bit) ISO image on various machines.
After zsync download, the thumb-drive is tested ("check disk for
defects") & passes; and worked fine on two systems today (dell d610 &
hp dx6120), however
-- Issue --
dell 755 (desktop) & hp dc7700 (small form factor) it just sits at
lubuntu plymouth screen.
switching to messages, it's just the following repeating
// on dell 755
"ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x00016e3f3000+2048
of device mask "
// on hp dc7700
"ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x000162317000+2048
of device mask "
NOTE: I can't copy/paste from systems, as it never completes boot; I
left it >30mins (on 755) & it just kept repeating message. I've
manually typed it; so typo's could have been made.
A discussion on #lubuntu-devel provided a possible cause (Thank you
Walter!) -
---
guiverc: lyorian:
http://debian.2.n7.nabble.com/Bug-908924-dma-direct-map-sg-overflow-on-USB-access-after-upgrade-to-kernel-4-18-td4387757.html
seems like it's a usb issue of some kind with 4.18
---
This fits because whilst I do my testing mostly on d610 & t43 (no
issues today), I'd tested Lubuntu 18.10 before on the dell 755 with no
issues. My last test was also long enough ago to be on 4.17 kernel.
I'll add `lshw` files for the two failed systems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794922/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1794922] Re: lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci 0000:00:a.7: dma_direct_map_sg: overflow 0x000000016e3f3000+2048 of device mask ffffffff" repeats
Also let's check Xubuntu and netboot, too. They both have i386 images.
--
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/1794922
Title:
lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci :00:a.7:
dma_direct_map_sg: overflow 0x00016e3f3000+2048 of device mask
" repeats
Status in linux package in Ubuntu:
Incomplete
Status in linux package in Debian:
Unknown
Bug description:
-- Background --
Testing the x86 (32bit) ISO image on various machines.
After zsync download, the thumb-drive is tested ("check disk for
defects") & passes; and worked fine on two systems today (dell d610 &
hp dx6120), however
-- Issue --
dell 755 (desktop) & hp dc7700 (small form factor) it just sits at
lubuntu plymouth screen.
switching to messages, it's just the following repeating
// on dell 755
"ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x00016e3f3000+2048
of device mask "
// on hp dc7700
"ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x000162317000+2048
of device mask "
NOTE: I can't copy/paste from systems, as it never completes boot; I
left it >30mins (on 755) & it just kept repeating message. I've
manually typed it; so typo's could have been made.
A discussion on #lubuntu-devel provided a possible cause (Thank you
Walter!) -
---
guiverc: lyorian:
http://debian.2.n7.nabble.com/Bug-908924-dma-direct-map-sg-overflow-on-USB-access-after-upgrade-to-kernel-4-18-td4387757.html
seems like it's a usb issue of some kind with 4.18
---
This fits because whilst I do my testing mostly on d610 & t43 (no
issues today), I'd tested Lubuntu 18.10 before on the dell 755 with no
issues. My last test was also long enough ago to be on 4.17 kernel.
I'll add `lshw` files for the two failed systems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794922/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1794922] Re: lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci 0000:00:a.7: dma_direct_map_sg: overflow 0x000000016e3f3000+2048 of device mask ffffffff" repeats
I note the linked report is 32 bit as well. Can you confirm this does
NOT occur on a 64 bit machine? Be very careful if you're using a 64 bit
machine that it's more likely to not have an EHCI controller. Roughly
speaking, EHCI is 2.0-level USB while xHCI is 3.0 (UHCI being 1.0, which
requires some additional memory hardware to support 64 bit FWIW). Since
the errors relate to EHCI, this is going to be crucial. `lspci | grep
HCI` should help out in that regard. It also might be good to check a 32
bit kernel on a 64 bit machine if you can get that test out of the way.
It is possible this may affect other controller architectures, but I
doubt it. On the other hand, EHCI can handle 1.0 and 2.0 devices and
will likely downgrade a 3.0 device to 2.0 speeds. If it's possible,
checking all those different ones will likely prove helping in
understanding the scope of the problem.
** Tags removed: cosmic
** Tags added: lubuntu
--
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/1794922
Title:
lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci :00:a.7:
dma_direct_map_sg: overflow 0x00016e3f3000+2048 of device mask
" repeats
Status in linux package in Ubuntu:
Incomplete
Status in linux package in Debian:
Unknown
Bug description:
-- Background --
Testing the x86 (32bit) ISO image on various machines.
After zsync download, the thumb-drive is tested ("check disk for
defects") & passes; and worked fine on two systems today (dell d610 &
hp dx6120), however
-- Issue --
dell 755 (desktop) & hp dc7700 (small form factor) it just sits at
lubuntu plymouth screen.
switching to messages, it's just the following repeating
// on dell 755
"ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x00016e3f3000+2048
of device mask "
// on hp dc7700
"ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x000162317000+2048
of device mask "
NOTE: I can't copy/paste from systems, as it never completes boot; I
left it >30mins (on 755) & it just kept repeating message. I've
manually typed it; so typo's could have been made.
A discussion on #lubuntu-devel provided a possible cause (Thank you
Walter!) -
---
guiverc: lyorian:
http://debian.2.n7.nabble.com/Bug-908924-dma-direct-map-sg-overflow-on-USB-access-after-upgrade-to-kernel-4-18-td4387757.html
seems like it's a usb issue of some kind with 4.18
---
This fits because whilst I do my testing mostly on d610 & t43 (no
issues today), I'd tested Lubuntu 18.10 before on the dell 755 with no
issues. My last test was also long enough ago to be on 4.17 kernel.
I'll add `lshw` files for the two failed systems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794922/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1794922] Re: lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci 0000:00:a.7: dma_direct_map_sg: overflow 0x000000016e3f3000+2048 of device mask ffffffff" repeats
** Package changed: ubuntu => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Bug watch added: Debian Bug tracker #908924
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908924
** Also affects: linux (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908924
Importance: Unknown
Status: Unknown
--
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/1794922
Title:
lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci :00:a.7:
dma_direct_map_sg: overflow 0x00016e3f3000+2048 of device mask
" repeats
Status in linux package in Ubuntu:
Incomplete
Status in linux package in Debian:
Unknown
Bug description:
-- Background --
Testing the x86 (32bit) ISO image on various machines.
After zsync download, the thumb-drive is tested ("check disk for
defects") & passes; and worked fine on two systems today (dell d610 &
hp dx6120), however
-- Issue --
dell 755 (desktop) & hp dc7700 (small form factor) it just sits at
lubuntu plymouth screen.
switching to messages, it's just the following repeating
// on dell 755
"ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x00016e3f3000+2048
of device mask "
// on hp dc7700
"ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x000162317000+2048
of device mask "
NOTE: I can't copy/paste from systems, as it never completes boot; I
left it >30mins (on 755) & it just kept repeating message. I've
manually typed it; so typo's could have been made.
A discussion on #lubuntu-devel provided a possible cause (Thank you
Walter!) -
---
guiverc: lyorian:
http://debian.2.n7.nabble.com/Bug-908924-dma-direct-map-sg-overflow-on-USB-access-after-upgrade-to-kernel-4-18-td4387757.html
seems like it's a usb issue of some kind with 4.18
---
This fits because whilst I do my testing mostly on d610 & t43 (no
issues today), I'd tested Lubuntu 18.10 before on the dell 755 with no
issues. My last test was also long enough ago to be on 4.17 kernel.
I'll add `lshw` files for the two failed systems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794922/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1734147]
>Installed Ubuntu 17.10.1 yesterday and can longer boot into USB or >CDROM. Dot One doesn't even load the module that caused this problem. That said, this should be a different bug. Please file a separate one. Thanks! -- @wxl | polka.bike C563 CAC5 8BE1 2F22 A49D 68F6 8B57 A48B C4F2 051A -- 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/1734147 Title: corrupted BIOS due to Intel SPI bug in kernel Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Bug description: An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI drivers results in a serial flash that is read only in Intel Broadwell and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set. Symptoms: * BIOS settings cannot be saved * USB Boot impossible * EFI entries read-only. --- Fix: The issue was fixed in kernel version 4.13.0-21 by configuring the kernel so it is not compiled with Intel SPI support. But previous affected machines still suffered from a broken BIOS. Repair: If you still can boot into Ubuntu, you can recover your BIOS with the following steps: 1. Boot into Ubuntu 2. Download http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 3. Install the downloaded package: $ sudo dpkg -i linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 4. Make sure the kernel is installed without any error. Once installed, reboot. 5. At grub, choose the newly installed kernel. You can choose the "recovery" mode. 6. Reboot and go to BIOS settings to confirm your BIOS has been recovered. 7. In case your BIOS is not recovered, reboot to the new kernel, then reboot *once again* to the new kernel, do not enter BIOS settings before the reboot. After the second reboot, check BIOS. 8. If your BIOS issue remains, download another kernel from http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb, and use dpkg to install it, then repeat steps 4 to 6. After your BIOS is fixed, the kernel packages you just installed are no longer needed, you can remove it by running 'sudo dpkg -r linux- image-4.15.0-041500rc6-generic'. The patch used to build the linux v4.15 kernel in step 8 can be found at https://goo.gl/xUKJFR. --- Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Affected Machines: Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Yoga 3 11" Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you)) Acer TravelMate B113 Acer Swift SF314-52 (Fixed by 4.14.9) Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G Dell Inspiron 15-3531 Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM HP 14-r012la --- Affected serial flash devices by manufacturer part number, JEDEC ID (SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c) /* ESMT */ f25l32pa, 0x8c2016 f25l32qa, 0x8c4116 f25l64qa, 0x8c4117 /* GigaDevice */ gd25q16, 0xc84015 gd25q32, 0xc84016 gd25lq32, 0xc86016 gd25q64, 0xc84017 gd25lq64c, 0xc86017 gd25q128, 0xc84018 gd25q256, 0xc84019 /* Winbond */ w25q16dw, 0xef6015 w25q32dw, 0xef6016 w25q64dw, 0xef6017 w25q128fw, 0xef6018 --- Original Description: Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
You can look at the manifest for the kernel: $ wget --quiet -O - http://cdimage.ubuntu.com/artful/daily-live/20180105.1/artful-desktop-amd64.manifest | grep ^linux- | grep -E 'image|headers|generic|signed' linux-generic 4.13.0.21.22 linux-headers-4.13.0-21 4.13.0-21.24 linux-headers-4.13.0-21-generic 4.13.0-21.24 linux-headers-generic 4.13.0.21.22 linux-image-4.13.0-21-generic 4.13.0-21.24 linux-image-extra-4.13.0-21-generic 4.13.0-21.24 linux-image-generic 4.13.0.21.22 linux-signed-generic4.13.0.21.22 linux-signed-image-4.13.0-21-generic4.13.0-21.24 linux-signed-image-generic 4.13.0.21.22 If you read the description above, you find: "Fix: The issue was fixed in kernel version 4.13.0-21 by configuring the kernel so it is not compiled with Intel SPI support." Looking on Launchpad for the linux source package (try !upkg linux in DuckDuckGo), you can see 4.13.0-21.24 is in security for artful. Looking at its [info page][1] one finds a changelog entry: " * Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models (LP: #1734147) - [Config] CONFIG_SPI_INTEL_SPI_PLATFORM=n" That being said, this kernel does NOT load the SPI drivers at all and will not suffer from this bug. Do note that linux-*-generic packages are from a different source package (linux-meta) and as such has a slightly different version number. [1]: https://launchpad.net/ubuntu/+source/linux/4.13.0-21.24 -- 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/1734147 Title: corrupted BIOS due to Intel SPI bug in kernel Status in Linux: Unknown Status in linux package in Ubuntu: Fix Committed Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Bug description: An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI drivers results in a serial flash that is read only in Intel Broadwell and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set. Symptoms: * BIOS settings cannot be saved * USB Boot impossible * EFI entries read-only. --- Fix: The issue was fixed in kernel version 4.13.0-21 by configuring the kernel so it is not compiled with Intel SPI support. But previous affected machines still suffered from a broken BIOS. Repair: If you still can boot into Ubuntu, you can recover your BIOS with the following steps: 1. Boot into Ubuntu 2. Download http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 3. Install the downloaded package: $ sudo dpkg -i linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 4. Make sure the kernel is installed without any error. Once installed, reboot. 5. At grub, choose the newly installed kernel. You can choose the "recovery" mode. 6. Reboot and go to BIOS settings to confirm your BIOS has been recovered. 7. In case your BIOS is not recovered, reboot to the new kernel, then reboot *once again* to the new kernel, do not enter BIOS settings before the reboot. After the second reboot, check BIOS. 8. If your BIOS issue remains, download another kernel from http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb, and use dpkg to install it, then repeat steps 4 to 6. After your BIOS is fixed, the kernel packages you just installed are no longer needed, you can remove it by running 'sudo dpkg -r linux- image-4.15.0-041500rc6-generic'. The patch used to build the linux v4.15 kernel in step 8 can be found at https://goo.gl/xUKJFR. --- Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Affected Machines: Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you)) Acer TravelMate B113 Acer Swift SF314-52 (Fixed by 4.14.9) Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G Dell Inspiron 15-3531 Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM HP 14-r012la --- Affected serial flash devices by manufacturer part number, JEDEC ID (SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c) /* ESMT */ f25l32pa, 0x8c2016 f25l32qa, 0x8c4116 f25l64qa, 0x8c4117 /* GigaDevice */
[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
** Description changed: - Description: An update to linux kernel on Ubuntu 17.10 that enabled the - intel-spi-* drivers made Insyde BIOS unusable. Main issues were Settings - being not stored, USB Boot impossible and EFI entries read-only. + An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI + drivers results in a serial flash that is read only in Intel Broadwell + and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set. - Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous + Symptoms: + * BIOS settings cannot be saved + * USB Boot impossible + * EFI entries read-only. + + --- + + Fix: The issue was fixed in kernel version 4.13.0-21 by configuring the + kernel so it is not compiled with Intel SPI support. But previous affected machines still suffered from a broken BIOS. Repair: If you still can boot into Ubuntu, you can recover your BIOS with the following steps: 1. Boot into Ubuntu 2. Download http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 3. Install the downloaded package: $ sudo dpkg -i linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 4. Make sure the kernel is installed without any error. Once installed, reboot. 5. At grub, choose the newly installed kernel. You can choose the "recovery" mode. 6. Reboot and go to BIOS settings to confirm your BIOS has been recovered. 7. In case your BIOS is not recovered, reboot to the new kernel, then reboot *once again* to the new kernel, do not enter BIOS settings before the reboot. After the second reboot, check BIOS. 8. If your BIOS issue remains, download another kernel from http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb, and use dpkg to install it, then repeat steps 4 to 6. After your BIOS is fixed, the kernel packages you just installed are no longer needed, you can remove it by running 'sudo dpkg -r linux- image-4.15.0-041500rc6-generic'. --- Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Affected Machines: Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you)) Acer TravelMate B113 Acer Swift SF314-52 (Fixed by 4.14.9) Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G Dell Inspiron 15-3531 (not fixed by 4.14.9) Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM HP 14-r012la --- + Affected serial flash devices by manufacturer part number, JEDEC ID (SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c) + /* ESMT */ +f25l32pa, 0x8c2016 +f25l32qa, 0x8c4116 +f25l64qa, 0x8c4117 + /* GigaDevice */ +gd25q16, 0xc84015 +gd25q32, 0xc84016 +gd25lq32, 0xc86016 +gd25q64, 0xc84017 +gd25lq64c, 0xc86017 +gd25q128, 0xc84018 +gd25q256, 0xc84019 + /* Winbond */ +w25q16dw, 0xef6015 +w25q32dw, 0xef6016 +w25q64dw, 0xef6017 +w25q128fw, 0xef6018 + + --- + Original Description: Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! -- 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/1734147 Title: corrupted BIOS due to Intel SPI bug in kernel Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Bug description: An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI drivers results in a serial flash that is read only in Intel Broadwell and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set. Symptoms: * BIOS settings cannot be saved * USB Boot impossible * EFI entries read-only. --- Fix: The issue was fixed in kernel version 4.13.0-21 by
[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
** Summary changed: - Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models + corrupted BIOS due to Intel SPI bug in kernel -- 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/1734147 Title: corrupted BIOS due to Intel SPI bug in kernel Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Bug description: Description: An update to linux kernel on Ubuntu 17.10 that enabled the intel-spi-* drivers made Insyde BIOS unusable. Main issues were Settings being not stored, USB Boot impossible and EFI entries read- only. Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous affected machines still suffered from a broken BIOS. Repair: If you still can boot into Ubuntu, you can recover your BIOS with the following steps: 1. Boot into Ubuntu 2. Download http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 3. Install the downloaded package: $ sudo dpkg -i linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 4. Make sure the kernel is installed without any error. Once installed, reboot. 5. At grub, choose the newly installed kernel. You can choose the "recovery" mode. 6. Reboot and go to BIOS settings to confirm your BIOS has been recovered. 7. In case your BIOS is not recovered, reboot to the new kernel, then reboot *once again* to the new kernel, do not enter BIOS settings before the reboot. After the second reboot, check BIOS. 8. If your BIOS issue remains, download another kernel from http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb, and use dpkg to install it, then repeat steps 4 to 6. After your BIOS is fixed, the kernel packages you just installed are no longer needed, you can remove it by running 'sudo dpkg -r linux- image-4.15.0-041500rc6-generic'. --- Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Affected Machines: Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you)) Acer TravelMate B113 Acer Swift SF314-52 (Fixed by 4.14.9) Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G Dell Inspiron 15-3531 (not fixed by 4.14.9) Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM HP 14-r012la --- Original Description: Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Amidst all the noise here, I thought it might be good to summarize some things and perhaps get them confirmed. Affected distros: * Ubuntu * Antergos and if the kernel bug attached is the same as this one: * Arch * Fedora Note: every distro with the right kernel has the potential for the problem, even though they do not display the symptoms. They may have turned it off, but the problem lies waiting in the kernel, not unlike some recessive genetic disease. The kernels: * 4.10 is ok * highest version is in zesty-proposed: 4.10.0-43.47 * 4.11-4.13.0-17 is not ok * highest version is in artful main: 4.13.0-22.25 * 4.13.0-21.24 avoids creating the problem by refusing to compile the kernel with CONFIG_SPI_INTEL_SPI_PLATFORM set * highest version is in artful-proposed: 4.13.0-22.25 * bionic main is still 4.13.0-17.20! * 4.14.9 Ubuntu mainline fixes the problem, it seems * this includes the following relevant commits: * don't touch SPI-NOR write protection bit d9018976cdb6eefc62a7ba79a405f6c9661b08a7 (see kernel bug report) * this is for the LPC bridge of the Intel I/O Controller hub (southbridge) which provides access to, e.g. BIOS ROM * note this only seems to affect Intel Haswell and Broadwell, see drivers/mfd/lpc_ich.c for PCI IDs * off-by-one fix 9d63f17661e25fd28714dac94bdebc4ff5b75f09 * this DOES NOT include the kernel compilation config change found in 4.13.0-21.24 * for some reason this doesn't work for everyone, so perhaps there's another issue at play Affected serial flash devices by manufacturer part number, JEDEC ID (SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c) /* ESMT */ f25l32pa, 0x8c2016 f25l32qa, 0x8c4116 f25l64qa, 0x8c4117 /* GigaDevice */ gd25q16, 0xc84015 gd25q32, 0xc84016 gd25lq32, 0xc86016 gd25q64, 0xc84017 gd25lq64c, 0xc86017 gd25q128, 0xc84018 gd25q256, 0xc84019 /* Winbond */ w25q16dw, 0xef6015 w25q32dw, 0xef6016 w25q64dw, 0xef6017 w25q128fw, 0xef6018 Note: considering the author of intel-spi the device driver feels that these are the problem children, based on a characteristic they have, the fact that there's Insyde BIOS or not probably has no bearing on whether or not a device is affected. Finally, a question: any way to figure out the JEDEC ID of the serial flash without having to load the module? -- 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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Bug description: Description: An update to linux kernel on Ubuntu 17.10 that enabled the intel-spi-* drivers made Insyde BIOS unusable. Main issues were Settings being not stored, USB Boot impossible and EFI entries read- only. Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous affected machines still suffered from a broken BIOS. Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into Linux and BIOS should be restored to a working state. --- Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Affected Machines: Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10) Acer TravelMate B113 Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G Dell Inspiron 15-3531 (not fixed by 4.14.9) Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM --- Original Description: Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1283003] Re: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates
Currently, on Lubuntu Trusty, I have no problems with Skullcandy Hesh 2 and: * kernel 3.13.0-63-generic #103 * pulseaudio 1:4.0-0ubuntu11.1+kxstudio1 (I did not test with the standard Canonical version, sorry) * bluez 4.101-0ubuntu13.1 * blueman 1.23-git201403102151-1ubuntu though I will note it's not always as seamless as I would like. I've discovered elsewhere people suggesting that the adapter is turned on after pulse does its check for bluetooth adapters. That leaves you two choices: 1. pactl load-module module-bluetooth-discover && pulseaudio -k (note actually sending a KILL signal to the daemon may get it unstuck if it's not behaving) 2. remove the conditional from /etc/pulse/default.pa regarding loading module-bluetooth-discover neither of which are particularly elegant, but oh well. This and similar issues are ultimately an aesthetic issue, though, and deserve a separate bug report, as this more general one has brown extensive enough. From my experience, audio sink service (A2DP) *IS* possible with current versions. I'm inclined to call this fixed, unless I hear otherwise from folks. -- 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/1283003 Title: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates Status in Blueman: New Status in blueman package in Ubuntu: Fix Released Status in bluez package in Ubuntu: Confirmed Status in gnome-bluetooth package in Ubuntu: Confirmed Bug description: Hi, I found a bug in Ubuntu 14.04 ! I tried to pair a bluetooth stereo headset (A2DP compatible). The pairing process goes well, but after that I can't select it on the audio preferences. When I select it, it only shows the last selected item options and don't do anything. (he should switch to the headset output). I must mention that it worked very well on Ubuntu 12.04. This bug can be in the bluetooth stack or in unity-control-center or maybe pulseaudio. I actually have no idea. To manage notifications about this bug go to: https://bugs.launchpad.net/blueman/+bug/1283003/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1377878] Re: PPC - GUI freezes except for mouse pointer
Workarounds exist, so low. ** Changed in: linux (Ubuntu) Importance: Medium = Low -- 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/1377878 Title: PPC - GUI freezes except for mouse pointer Status in The Linux Kernel: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: During the installation the computer freezes completely except for the mouse pointer. And even that is stuck with whatever shape it happened to have at the time it froze. The steps I have to cause the freeze are run Ubiquity to start the installation open a terminal, run Ubuntu-bug and let it launch Firefox. It will freeze every time then. Even the consoles (ctrl-alt-f1 etc) are unavailable. What kind of information can I collect and how? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1377878/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1422675] Re: No installable kernel was found in the defined APT sources
Why don't you `apport-collect ` in the alternate then?1 -- 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/1422675 Title: No installable kernel was found in the defined APT sources Status in linux package in Ubuntu: Confirmed Bug description: I tried to install from the Ubuntu Vivid 32-bit mini.iso into a computer with Pentium M http://www.cnet.com/laptops/lenovo- thinkpad-t42-2373/4507-3121_7-31155666.html and booted the installer with the forcepae boot option. This made the installer start and work until it should get the kernel. Then it stopped with the following message No installable kernel was found in the defined APT sources ... Continue the installation without installing a kernel? I checked if this is a PAE issue ... and yes, it is. Forcepae makes the installer work, but later on, during installation, it refuses to manage the [PAE] kernel. I tested, and it works in a computer with CPU with a built-in PAE flag. And the trusty mini.iso can install in the same computer with Pentium M, so this is a regression. At 'ctrl+alt+F4' it complains that the kernels found are not usable on 486. But forcepae should allow it. And the same kernels work when installed with the corresponding daily Lubuntu Vivid desktop iso file. -o- This bug is reported from another computer, because I don't know how to report it from the mini.iso system. So you should disregard the collected data, that I might not be able to remove. ProblemType: Bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1422675/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1221995] Re: 0a12:0001 Bluetooth Dongle (Cambridge Silicon Radio, Ltd) doesn't work with 3.11 or 3.13 kernels
No luck on linux-generic-lts-utopic on Lubuntu Trusty. Weird. -- 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/1221995 Title: 0a12:0001 Bluetooth Dongle (Cambridge Silicon Radio, Ltd) doesn't work with 3.11 or 3.13 kernels Status in linux package in Ubuntu: Confirmed Bug description: SRU Justification: Impact: Bluetooth device stopped working. Device support regression. Fix: Upstream, f9f462faa02777f497eb25255683a94e0c054de6 Testcase: Comment #10 Original Description: Bluetooth device stopped working after upgrading ubuntu to 13.10. ~$ lsusb: Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) ~$ hciconfig hci0: Type: BR/EDR Bus: USB BD Address: 00:1B:10:00:0F:46 ACL MTU: 1017:8 SCO MTU: 64:0 DOWN RX bytes:457 acl:0 sco:0 events:16 errors:0 TX bytes:68 acl:0 sco:0 commands:16 errors:0 ~$ hcitool dev Devices: device simply doesnt appear on bluetooth manager. blueman UI is broken. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-4-generic 3.11.0-4.9 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jorge 1954 F pulseaudio /dev/snd/controlC0: jorge 1954 F pulseaudio Date: Fri Sep 6 22:32:45 2013 HibernationDevice: RESUME=UUID=707ce71f-40a6-4fc3-b0a1-d24329b1c781 IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: MEGAWARE MW-H61M-2H MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic root=UUID=3480d68a-ee68-452e-b349-a2398ce3da52 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.11.0-4-generic N/A linux-backports-modules-3.11.0-4-generic N/A linux-firmware1.113 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-08-23 (15 days ago) dmi.bios.date: 08/28/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 MW dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MW-H61M-2H dmi.board.vendor: MEGAWARE dmi.board.version: v1.3 - 17/07/2012 - MWX dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MEGAWARE dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5MW:bd08/28/2012:svnMEGAWARE:pnMW-H61M-2H:pvrv1.3-17/07/2012-MWX:rvnMEGAWARE:rnMW-H61M-2H:rvrv1.3-17/07/2012-MWX:cvnMEGAWARE:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: MW-H61M-2H dmi.product.version: v1.3 - 17/07/2012 - MWX dmi.sys.vendor: MEGAWARE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1221995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1221995] Re: 0a12:0001 Bluetooth Dongle (Cambridge Silicon Radio, Ltd) doesn't work with 3.11 or 3.13 kernels
I didn't have a chance to test that last night but I tried the same hardware on a Kubuntu Trusty with 3.13.0-40-generic and had no problem. Worked right out of the box. Are we *sure* this is a kernel issue? -- 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/1221995 Title: 0a12:0001 Bluetooth Dongle (Cambridge Silicon Radio, Ltd) doesn't work with 3.11 or 3.13 kernels Status in linux package in Ubuntu: Confirmed Bug description: SRU Justification: Impact: Bluetooth device stopped working. Device support regression. Fix: Upstream, f9f462faa02777f497eb25255683a94e0c054de6 Testcase: Comment #10 Original Description: Bluetooth device stopped working after upgrading ubuntu to 13.10. ~$ lsusb: Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) ~$ hciconfig hci0: Type: BR/EDR Bus: USB BD Address: 00:1B:10:00:0F:46 ACL MTU: 1017:8 SCO MTU: 64:0 DOWN RX bytes:457 acl:0 sco:0 events:16 errors:0 TX bytes:68 acl:0 sco:0 commands:16 errors:0 ~$ hcitool dev Devices: device simply doesnt appear on bluetooth manager. blueman UI is broken. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-4-generic 3.11.0-4.9 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jorge 1954 F pulseaudio /dev/snd/controlC0: jorge 1954 F pulseaudio Date: Fri Sep 6 22:32:45 2013 HibernationDevice: RESUME=UUID=707ce71f-40a6-4fc3-b0a1-d24329b1c781 IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: MEGAWARE MW-H61M-2H MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic root=UUID=3480d68a-ee68-452e-b349-a2398ce3da52 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.11.0-4-generic N/A linux-backports-modules-3.11.0-4-generic N/A linux-firmware1.113 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-08-23 (15 days ago) dmi.bios.date: 08/28/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 MW dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MW-H61M-2H dmi.board.vendor: MEGAWARE dmi.board.version: v1.3 - 17/07/2012 - MWX dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MEGAWARE dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5MW:bd08/28/2012:svnMEGAWARE:pnMW-H61M-2H:pvrv1.3-17/07/2012-MWX:rvnMEGAWARE:rnMW-H61M-2H:rvrv1.3-17/07/2012-MWX:cvnMEGAWARE:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: MW-H61M-2H dmi.product.version: v1.3 - 17/07/2012 - MWX dmi.sys.vendor: MEGAWARE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1221995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1221995] Re: 0a12:0001 Bluetooth Dongle (Cambridge Silicon Radio, Ltd) doesn't work with 3.11 or 3.13 kernels
@inaddy, which kernel are you suggesting to test from where? i can't find it in the ppa or anywhere in the repos, but i have the hardware and the same problem on 3.13.0-43-generic in trusty. -- 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/1221995 Title: 0a12:0001 Bluetooth Dongle (Cambridge Silicon Radio, Ltd) doesn't work with 3.11 or 3.13 kernels Status in linux package in Ubuntu: Confirmed Bug description: SRU Justification: Impact: Bluetooth device stopped working. Device support regression. Fix: Upstream, f9f462faa02777f497eb25255683a94e0c054de6 Testcase: Comment #10 Original Description: Bluetooth device stopped working after upgrading ubuntu to 13.10. ~$ lsusb: Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) ~$ hciconfig hci0: Type: BR/EDR Bus: USB BD Address: 00:1B:10:00:0F:46 ACL MTU: 1017:8 SCO MTU: 64:0 DOWN RX bytes:457 acl:0 sco:0 events:16 errors:0 TX bytes:68 acl:0 sco:0 commands:16 errors:0 ~$ hcitool dev Devices: device simply doesnt appear on bluetooth manager. blueman UI is broken. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-4-generic 3.11.0-4.9 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jorge 1954 F pulseaudio /dev/snd/controlC0: jorge 1954 F pulseaudio Date: Fri Sep 6 22:32:45 2013 HibernationDevice: RESUME=UUID=707ce71f-40a6-4fc3-b0a1-d24329b1c781 IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: MEGAWARE MW-H61M-2H MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic root=UUID=3480d68a-ee68-452e-b349-a2398ce3da52 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.11.0-4-generic N/A linux-backports-modules-3.11.0-4-generic N/A linux-firmware1.113 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-08-23 (15 days ago) dmi.bios.date: 08/28/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 MW dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MW-H61M-2H dmi.board.vendor: MEGAWARE dmi.board.version: v1.3 - 17/07/2012 - MWX dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MEGAWARE dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5MW:bd08/28/2012:svnMEGAWARE:pnMW-H61M-2H:pvrv1.3-17/07/2012-MWX:rvnMEGAWARE:rnMW-H61M-2H:rvrv1.3-17/07/2012-MWX:cvnMEGAWARE:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: MW-H61M-2H dmi.product.version: v1.3 - 17/07/2012 - MWX dmi.sys.vendor: MEGAWARE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1221995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1245159] Re: [MacBookPro8, 2] Laptop keyboard activity and touchpad movements often interpreted as clicks
since it is part of the default settings, are you sure that tap to click isn't part of the issue? perhaps the touchpad is too sensitive? -- 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/1245159 Title: [MacBookPro8,2] Laptop keyboard activity and touchpad movements often interpreted as clicks Status in linux package in Ubuntu: Triaged Bug description: On a MacBookPro8,2, the track pad often fires off a click even when it is not pressed. This can happen when typing on the keyboard (not touching the trackpad) or when actually using the mouse but not clicking. Such events make it fairly unsafe to use GUI applications that do not have an undo function for each possible action. Nothing seems to make the false clicks more or less likely to happen. WORKAROUND: Use external keyboard and mouse. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Sun Oct 27 12:51:50 2013 InstallationDate: Installed on 2013-10-17 (10 days ago) InstallationMedia: Lubuntu 13.10 Saucy Salamander - Release amd64+mac (20131016) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Apple Inc. MacBookPro8,2 MarkForUpload: True ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=140e28f3-4795-466b-9ea0-3264746c9186 ro quiet splash vt.handoff=7 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied dmesg: write failed: Broken pipe DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-10-17 (10 days ago) InstallationMedia: Lubuntu 13.10 Saucy Salamander - Release amd64+mac (20131016) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Apple Inc. MacBookPro8,2 MarkForUpload: True Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=140e28f3-4795-466b-9ea0-3264746c9186 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1377878] Re: PPC - GUI freezes except for mouse pointer
Actually, Boris was right. Lars I recommend you read the PPC FAQ. The graphics section makes it quite clear that there's no mechanism in place to determine the appropriate graphics settings for your particular hardware: https://wiki.ubuntu.com/PowerPCFAQ#Configure_graphics Furthermore, if such a mechanism could exist, PPC is ultimately unsupported. We, as the Lubuntu community, are supporting it, but we don't have the resources to dedicate to innovating for PPC. Lastly, keep in mind that what works for Radeon might create problems for Nvidia. That being said, really, if we have a workaround, it's fixed. ** Changed in: linux (Ubuntu) Status: Confirmed = Invalid -- 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/1377878 Title: PPC - GUI freezes except for mouse pointer Status in “linux” package in Ubuntu: Invalid Bug description: During the installation the computer freezes completely except for the mouse pointer. And even that is stuck with whatever shape it happened to have at the time it froze. The steps I have to cause the freeze are run Ubiquity to start the installation open a terminal, run Ubuntu-bug and let it launch Firefox. It will freeze every time then. Even the consoles (ctrl-alt-f1 etc) are unavailable. What kind of information can I collect and how? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1377878/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1377878] Re: PPC - GUI freezes except for mouse pointer
Is there anyone that video=ofonly radeon.agpmode=-1 doesn't work for? If not, then we can call this invalid. Unfortunately, these parameters are not appropriate to every kind of ppc machine, so it doesn't make sense to make them the default. We just kind of have to know this stuff. -- 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/1377878 Title: PPC - GUI freezes except for mouse pointer Status in “linux” package in Ubuntu: Confirmed Bug description: During the installation the computer freezes completely except for the mouse pointer. And even that is stuck with whatever shape it happened to have at the time it froze. The steps I have to cause the freeze are run Ubiquity to start the installation open a terminal, run Ubuntu-bug and let it launch Firefox. It will freeze every time then. Even the consoles (ctrl-alt-f1 etc) are unavailable. What kind of information can I collect and how? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1377878/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 633983] Re: Can't boot amd64 live cd on Mac (EFI)
amd64+mac images are gone as of 14.10: https://wiki.ubuntu.com/UtopicUnicorn/ReleaseNotes#Boot.2C_installation_and_post-install file a new bug if you have the latest firmware updates and the amd64 images don't work. ** Changed in: linux (Ubuntu) Status: Incomplete = Invalid ** Changed in: syslinux (Ubuntu) Status: Confirmed = Invalid -- 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/633983 Title: Can't boot amd64 live cd on Mac (EFI) Status in Ubuntu CD image build software: Unknown Status in Release Notes for Ubuntu: Fix Released Status in “casper” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Invalid Status in “syslinux” package in Ubuntu: Invalid Status in “casper” source package in Maverick: Invalid Status in “linux” source package in Maverick: Invalid Status in “syslinux” source package in Maverick: Invalid Bug description: Previous release livecd's were bootable by holding down option while the cd was in the drive and selecting the Windows cd. Trying this with the Meerkat beta desktop livecd image (md5sum verified) I just get two numbers (1. and 2.) which look like they should be labeling some text but there is no text visible and the message to select CD-ROM boot type. Typing either a 1 or a 2 doesn't do anything. Googling revealed that some Windows beta iso images had the same problem booting on Macs; apparently in this case it was an issue that the Windows version had EFI support (and so didn't use the BIOS fallback) but was assuming a newer version of EFI. There were some other posts which claimed that it was that the iso image was generated incorrectly (something having to do with ISO9660 versions). Unfortunately, even though I develop software for a living, there is nothing I can do to help debug this (except try newer versions) since once I get to that message, everything seems unresponsive. The upshot is that a useful thing which I did frequently in older versions (i.e. boot the 64bit desktop livecd on this macbook) no longer works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/633983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1377878] Re: PPC - GUI freezes except for mouse pointer
@adam does this affect all ppc radeon cards? if so, that kills a lot of computers we wanted to support! can you link me to archives of your upstream inquiries? -- 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/1377878 Title: PPC - GUI freezes except for mouse pointer Status in “linux” package in Ubuntu: Confirmed Bug description: During the installation the computer freezes completely except for the mouse pointer. And even that is stuck with whatever shape it happened to have at the time it froze. The steps I have to cause the freeze are run Ubiquity to start the installation open a terminal, run Ubuntu-bug and let it launch Firefox. It will freeze every time then. Even the consoles (ctrl-alt-f1 etc) are unavailable. What kind of information can I collect and how? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1377878/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1377878] Re: PPC - GUI freezes except for mouse pointer
do you guys have this problem in 14.04.1? -- 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/1377878 Title: PPC - GUI freezes except for mouse pointer Status in “linux” package in Ubuntu: Confirmed Bug description: During the installation the computer freezes completely except for the mouse pointer. And even that is stuck with whatever shape it happened to have at the time it froze. The steps I have to cause the freeze are run Ubiquity to start the installation open a terminal, run Ubuntu-bug and let it launch Firefox. It will freeze every time then. Even the consoles (ctrl-alt-f1 etc) are unavailable. What kind of information can I collect and how? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1377878/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1363180] Re: utopic alternate install CD doesn't boot
On Fri, Oct 3, 2014 at 6:38 PM, Fritz Hudnut este.el@gmail.com wrote: OK, with today's daily 10/3 powerpc I was able to get passed the Yaboot boot screen, in both my iMac 800 and my iBook, so that's the good news. that means this one's fixed. the iMac I just used the live video=ofonly??? the semi default boot parameter and eventually got to a black screen . . . I would need to be reminded on what the boot parameters for the iMac are . . . . for fixing general issues with ppc, refer to this: https://wiki.ubuntu.com/PowerPCFAQ (there are many paragraphs of discussion about proper boot parameters and different options for different graphics chips) however, this may still be an issue: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1371651 However, on the iBook, which I might actually try the install on, I used live-nosplash-powerpc video=radeonfb: 1024x768-32@60 . . . . And that got me to a clean resolution GUI desktop!!! the fix that i have seen for the blank GUI is quiet splash but perhaps the nosplash fixed it in this case? -- 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/1363180 Title: utopic alternate install CD doesn't boot Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Utopic: Fix Released Bug description: During testing for PPC 14.10 alternate install CD on iBook G4 the process got as far as the Yaboot window boot prompt . . . entering various commands resulted in response: claim error, can't allocate e0 at 0 x c200; claim error, can't allocate kernel memory. Built 20140826.1 No further testing could be done. --- AcpiTables: AlsaDevices: total 0 crw-rw---T+ 1 root audio 116, 1 Sep 1 2014 seq crw-rw---T+ 1 root audio 116, 33 Sep 1 2014 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. AplayDevices: aplay: device_list:252: no soundcards found... ApportVersion: 2.0.1-0ubuntu17.7 Architecture: powerpc ArecordDevices: arecord: device_list:252: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 42.846793] eth0: no IPv6 routers present [ 42.904664] input: Mouseemu virtual keyboard as /devices/virtual/input/input5 [ 42.915426] input: Mouseemu virtual mouse as /devices/virtual/input/input6 [ 101.468774] init: network-manager main process (963) killed by TRAP signal [ 101.469044] init: network-manager main process ended, respawning DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=111ee215-f0ae-4fb1-ad99-30a4e7f280df Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard Bus 002 Device 003: ID 05ac:0220 Apple, Inc. Aluminum Keyboard (ANSI) Bus 002 Device 004: ID 047d:1029 Kensington Mouse*in*a*Box Optical Elite MarkForUpload: True Package: linux (not installed) PciMultimedia: ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 OFfb NVDA,NVMac ProcKernelCmdLine: root=UUID=98ab2c76-e668-4d8d-a684-d30381117f49 ro quiet splash ProcVersionSignature: Ubuntu 3.2.0-68.102-powerpc-smp 3.2.62 RelatedPackageVersions: linux-restricted-modules-3.2.0-68-powerpc-smp N/A linux-backports-modules-3.2.0-68-powerpc-smp N/A linux-firmware1.79.16 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: precise Uname: Linux 3.2.0-68-powerpc-smp ppc UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare sudo tape video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1363180/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1363180] Re: utopic alternate install CD doesn't boot
@Fritz it's apparently not fixed for Lars but we need others to confirm that. Please include your report. Final release is due on the 23rd, btw. -- 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/1363180 Title: utopic alternate install CD doesn't boot Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Utopic: Fix Released Bug description: During testing for PPC 14.10 alternate install CD on iBook G4 the process got as far as the Yaboot window boot prompt . . . entering various commands resulted in response: claim error, can't allocate e0 at 0 x c200; claim error, can't allocate kernel memory. Built 20140826.1 No further testing could be done. --- AcpiTables: AlsaDevices: total 0 crw-rw---T+ 1 root audio 116, 1 Sep 1 2014 seq crw-rw---T+ 1 root audio 116, 33 Sep 1 2014 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. AplayDevices: aplay: device_list:252: no soundcards found... ApportVersion: 2.0.1-0ubuntu17.7 Architecture: powerpc ArecordDevices: arecord: device_list:252: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 42.846793] eth0: no IPv6 routers present [ 42.904664] input: Mouseemu virtual keyboard as /devices/virtual/input/input5 [ 42.915426] input: Mouseemu virtual mouse as /devices/virtual/input/input6 [ 101.468774] init: network-manager main process (963) killed by TRAP signal [ 101.469044] init: network-manager main process ended, respawning DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=111ee215-f0ae-4fb1-ad99-30a4e7f280df Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard Bus 002 Device 003: ID 05ac:0220 Apple, Inc. Aluminum Keyboard (ANSI) Bus 002 Device 004: ID 047d:1029 Kensington Mouse*in*a*Box Optical Elite MarkForUpload: True Package: linux (not installed) PciMultimedia: ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 OFfb NVDA,NVMac ProcKernelCmdLine: root=UUID=98ab2c76-e668-4d8d-a684-d30381117f49 ro quiet splash ProcVersionSignature: Ubuntu 3.2.0-68.102-powerpc-smp 3.2.62 RelatedPackageVersions: linux-restricted-modules-3.2.0-68-powerpc-smp N/A linux-backports-modules-3.2.0-68-powerpc-smp N/A linux-firmware1.79.16 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: precise Uname: Linux 3.2.0-68-powerpc-smp ppc UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare sudo tape video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1363180/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 633983] Re: Can't boot amd64 live cd on Mac (EFI)
regarding chris' bug about removing the images, there are several very relevant comments there, including some discussion about firmware updates which is not mentioned here. -- 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/633983 Title: Can't boot amd64 live cd on Mac (EFI) Status in Ubuntu CD image build software: Unknown Status in Release Notes for Ubuntu: Fix Released Status in “casper” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Incomplete Status in “syslinux” package in Ubuntu: Confirmed Status in “casper” source package in Maverick: Invalid Status in “linux” source package in Maverick: Invalid Status in “syslinux” source package in Maverick: Invalid Bug description: Previous release livecd's were bootable by holding down option while the cd was in the drive and selecting the Windows cd. Trying this with the Meerkat beta desktop livecd image (md5sum verified) I just get two numbers (1. and 2.) which look like they should be labeling some text but there is no text visible and the message to select CD-ROM boot type. Typing either a 1 or a 2 doesn't do anything. Googling revealed that some Windows beta iso images had the same problem booting on Macs; apparently in this case it was an issue that the Windows version had EFI support (and so didn't use the BIOS fallback) but was assuming a newer version of EFI. There were some other posts which claimed that it was that the iso image was generated incorrectly (something having to do with ISO9660 versions). Unfortunately, even though I develop software for a living, there is nothing I can do to help debug this (except try newer versions) since once I get to that message, everything seems unresponsive. The upshot is that a useful thing which I did frequently in older versions (i.e. boot the 64bit desktop livecd on this macbook) no longer works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/633983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
