[Kernel-packages] [Bug 1804028] Re: Surface Go - QCA6174 wifi card not correctly recognized and therefore not working
Launchpad has imported 8 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1651779. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2018-11-20T19:42:11+00:00 fedora_45sg wrote: Description of problem: After booting, the wifi card is not properly recognized. Version-Release number of selected component (if applicable): firmware version can be seen in dmesg output. "[ 4.242132] ath10k_pci :01:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 168c:3370 [ 4.242138] ath10k_pci :01:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [ 4.243006] ath10k_pci :01:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [ 4.308059] ath10k_pci :01:00.0: failed to fetch board data for bus=pci,vendor=168c,device=003e,subsystem-vendor=168c,subsystem-device=3370 from ath10k/QCA6174/hw3.0/board-2.bin [ 4.309354] ath10k_pci :01:00.0: board_file api 1 bmi_id N/A crc32 ed5f849a" How reproducible: Insert usb-pen, boot Fedora 29 Workstation, open terminal, get dmesg output Steps to Reproduce: 1. Boot 2. get dmesg output Actual results: dmesg output: Wifi/bluetooth card not properly recognized and therefore not working Expected results: Wifi/bluetooth working. Additional info: I added some more results here: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1804028 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/1804028/comments/7 On 2018-11-20T22:18:44+00:00 fedora_45sg wrote: In the .zip from https://www.killernetworking.com/killersupport/item /killer-drivers-inf in the file ./Killer-Ethernet- Wireless_INF/Production/Windows10-x64/11AC/netathr10x.inf I finally found one matching subsystem-device=3370 entry, which leads to: " %ATHR.DeviceDesc.6320_3% = ATHR_DEV_OS63_988x_TX8.ndi, PCI\VEN_168C_003E_3370168C_32; WiFi Only SKU " about this special .ndi there are some entrys later: " [ATHR_DEV_OS63_988x_TX8.ndi.NTamd64] Characteristics = 0x84 BusType = 5 AddReg = atheros_os63.reg, atheros11n.reg, smpsDynamic.reg, qca_utf.reg, D0PC.reg, roam.reg, wmmac.reg, FW_3X.reg, BD_TX8.reg, enableTxbfee.reg, wowEnable.reg, ForceWowSleep.reg, fastDlBinary.reg, enableSmbios.reg, Ch1213_options_SingleSKU.reg CopyFiles = atheros.CopyFiles, atheros_FW_3X.CopyFiles, atheros_BD_TX8.CopyFiles, service.CopyFiles *IfType = 71; IF_TYPE_IEEE80211 *MediaType = 16; NdisMediumNative802_11 *PhysicalMediaType = 9 ; NdisPhysicalMediumNative802_11 Include = machine.inf, netvwifibus.inf Needs = VWiFiBus.CopyFiles [ATHR_DEV_OS63_988x_TX8.ndi.NTamd64.Services] AddService = Qcamain10x64, 2, atheros.Service, atheros.EventLog Include= netvwifibus.inf Needs = VWiFiBus.Services AddService = QcomWlanSrv, 0x0800, wlanService [ATHR_DEV_OS63_988x_TX8.ndi.NTamd64.HW] AddReg = MSI.reg Include = netvwifibus.inf Needs = PciASPMOptIn.Hw, VWiFiBus.PnPFilterRegistration.Hw, PciD3ColdSupported.Hw " I am just a bit confused because it just says "Wifi Only SKU" and I know from the Windows Device Manager that also bluetooth is done with the same chip, see https://www.reddit.com/r/Surface/comments/9386l7/surface_go_wifi_qualcomm_qca61x4a/e3bbi1b/ but maybe there are two different build-in, one for wifi and one for bluetooth? Anyway, from the quote there is one interesting line: " CopyFiles = atheros.CopyFiles, atheros_FW_3X.CopyFiles, atheros_BD_TX8.CopyFiles, service.CopyFiles " It seems that there exist just one file with "TX8" in it: "eeprom_ar6320_3p0_TX8_clpc.bin" I copied the .bin file as board.bin to /lib/firmware/ath10k/QCA6174/hw3.0/ and it finally works! Wifi is directly working and no error messages anymore in dmesg! :-) So eeprom_ar6320_3p0_TX8_clpc.bin, or the informations of that .bin file have to be added to https://wireless.wiki.kernel.org/en/users/drivers/ath10k/boardfiles and this should be a clean solution, because the subsystem-device=3370 ID is matching. Can someone please double check if this is the correct solution which could go upstream? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/1804028/comments/8 On 2018-11-20T22:41:25+00:00 fedora_45sg wrote: Did some additional tests with "eeprom_ar6320_3p0_TX8_clpc.bin": The copied and renamed as board.bin file also works with the latest firmware-6.bin from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/plain/ath10k/QCA6174/hw3.0/ and also with the one from
[Kernel-packages] [Bug 1806867] Re: Increase DVB_MAX_ADAPTERS from 8 to 16 in kernel config
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1806867 Title: Increase DVB_MAX_ADAPTERS from 8 to 16 in kernel config Status in linux package in Ubuntu: Expired Bug description: I installed 12 dvb adapters in my setup and noticed, that the DVB_MAX_ADAPTERS is still limited to 8 instead of 16. This bug has been reported and confirmed in earlier versions of Ubuntu. ProblemType: Bug Description: Ubuntu 18.04.1 LTS Release: 18.04 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: 4.15.0-42-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 :~$ cat lspci-vnvn.log 00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller [8086:29c0] Subsystem: Red Hat, Inc QEMU Virtual Machine [1af4:1100] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [90] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+ RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM L0s, Exit Latency L0s <64ns, L1 <1us ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk- DLActive+ BWMgmt- ABWMgmt- SltCap: AttnBtn+ PwrCtrl+ MRL- AttnInd+ PwrInd+ HotPlug+ Surprise+ Slot #0, PowerLimit 0.000W; Interlock+ NoCompl- SltCtl: Enable: AttnBtn+ PwrFlt- MRL- PresDet- CmdCplt+ HPIrq+ LinkChg- Control: AttnInd Off, PwrInd On, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet- LinkState- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported ARIFwd+ DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled ARIFwd- LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [60] MSI: Enable+ Count=1/2 Maskable+ 64bit- Address: fee0 Data: 4021 Masking: 0002 Pending: Capabilities: [40] Subsystem: Intel Corporation 7500/5520/5500/X58 I/O Hub PCI Express Root Port 0 [8086:] Capabilities: [100 v2] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr- CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn- Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.1 PCI bridge [0604]: Intel Corporation 7500/5520/5500/X58 I/O Hub PCI Express Root Port 0 [8086:3420] (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
[Kernel-packages] [Bug 1800446] Re: kidle_inject constantly running
I suggest, disable thermald service first. #systemctl diable thermald then reboot Then on a window #thermald --loglevel=info --no-daemon And do your regular work, When you experience slow down, copy paste output of the thermald and attach. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1800446 Title: kidle_inject constantly running Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: Confirmed Bug description: Computer boots up fine, but as soon as any process causes a single spike in CPU, `kidle_inject` starts and it just won't stop. Even after 1 hour of idling, with low temperatures, no fan, it’s still making this computer unresponsive. I disabled `kidle_inject` process by creating a file `/etc/modprobe.d /blacklist-power.conf` with the following content: ``` blacklist intel_powerclamp blacklist intel_rapl ``` Then I restarted computer. Since then, my computer is not unresponsive anymore, and I use it to work all the time. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: williamivanski 5974 F pulseaudio /dev/snd/controlC1: williamivanski 5974 F pulseaudio Date: Mon Oct 29 08:05:09 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=1c6d4273-ae09-412d-9488-78ab7ba2fc4b InstallationDate: Installed on 2015-09-23 (1131 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LG Electronics 13Z940-G.BK71P1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=42b637c4-2da3-4c1a-a62d-b4beb93b8243 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-23 (5 days ago) dmi.bios.date: 09/04/2014 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 13Z940FF dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: White Tip Mountain dmi.board.vendor: LG Electronics dmi.board.version: FAB3 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: LG Electronics dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr13Z940FF:bd09/04/2014:svnLGElectronics:pn13Z940-G.BK71P1:pvr0.1:rvnLGElectronics:rnWhiteTipMountain:rvrFAB3:cvnLGElectronics:ct9:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: 13Z940-G.BK71P1 dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800446/+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 1763975] Re: DP1.2 daisy-chain flickering
Just wondering if there is any update on this? -- 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/1763975 Title: DP1.2 daisy-chain flickering Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: New Bug description: Hi all, I have a NUC7i7BNH with the latest BIOS (0062) running Ubuntu 18.04 (uname -r = 4.15.0-15-generic). I have the NUC connected via USB-C to DisplayPort, to an Avocent SV340D KVM, then to a Dell U2415 which has DP1.2 enabled and is daisy-chainged to another Dell U2415 (DP1.2 disabled on the second monitor as per Dell instructions). I am getting flickering whereby randomly display1 or display2 turn black and then back on again. When I disable DP1.2 on the display1, and therefore get a duplicate display (as opposed to extended) on display2, I get no flickering at all. The same setup yields no flickering when running from a Windows 10 box, so don't think it is the monitors. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 14 12:52:24 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:5927] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2068] InstallationDate: Installed on 2018-04-01 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180401) MachineType: Intel Corporation NUC7i7BNH ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BNKBL357.86A.0062.2018.0222.1644 dmi.board.name: NUC7i7BNB dmi.board.vendor: Intel Corporation dmi.board.version: J31145-307 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrBNKBL357.86A.0062.2018.0222.1644:bd02/22/2018:svnIntelCorporation:pnNUC7i7BNH:pvrJ31153-308:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-307:cvnIntelCorporation:ct3:cvr2: dmi.product.family: Intel NUC dmi.product.name: NUC7i7BNH dmi.product.version: J31153-308 dmi.sys.vendor: Intel Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763975/+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 1809843] Re: sky2 ethernet card link not up after suspend
Thank you for your response, this seems to do the trick. I was worried that disabling MSI would decrease networking performance, but a simple iperf3 test comparison showed no difference. Long term it seems that this should be handled in the kernel driver code (according to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921/comments/34). -- 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/1809843 Title: sky2 ethernet card link not up after suspend Status in linux package in Ubuntu: Confirmed Bug description: Issue is as described by the user 'kris' in #1798921 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921). Sometimes when bringing my laptop up from suspended state my Ethernet card shows link connection and activity via port LEDs but ethtool indicates the link is not up. This does not happen every time I resume from suspend, about one in 5 times. When it does happen, the following additional message is present in my dmesg output: [ 686.804877] do_IRQ: 1.37 No irq handler for vector The lspci -vvnn output for the Ethernet card is: 02:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd. 88E8057 PCI-E Gigabit Ethernet Controller [11ab:4380] (rev 10) Subsystem: Acer Incorporated [ALI] 88E8057 PCI-E Gigabit Ethernet Controller [1025:028e] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921/comments/34, in the hopes that this specific card will be added to the relevant MSI quirks table. If I do not suffer from the same issue as kris in the above linked issue, I will be happy to provide any additional information, test fixes etc. I would like to avoid using the 'pci=nomsi,noaer' workaround he mentioned if possible. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: maridius 2260 F...m pulseaudio /dev/snd/controlC0: maridius 2260 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=0840edd3-6052-4916-bcc2-4c5b13edb862 InstallationDate: Installed on 2015-09-01 (1212 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Gateway P-79 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=ad05ff21-9786-4f03-8641-85f2f416363d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-42.45+PHC-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 09/30/2009 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 79.07.00 dmi.board.name: Godzilla-N10 dmi.board.vendor: Gateway dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Gateway dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr79.07.00:bd09/30/2009:svnGateway:pnP-79:pvr0100:rvnGateway:rnGodzilla-N10:rvrRev:cvnGateway:ct10:cvrN/A: dmi.product.name: P-79 dmi.product.version: 0100 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809843/+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 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69
Had this with nvidia graphics drivers after installing and then removing proprietary drivers downloaded from nvidia website. I could not log in at all at first boot. If you see nvidia modules loaded, make sure that you select an xorg session on the login screen (not wayland) if you this control presented to you. lsmod| grep nvidia nvidia_uvm794624 0 nvidia_drm 40960 13 nvidia_modeset 1040384 1 nvidia_drm nvidia 17285120 653 nvidia_uvm,nvidia_modeset ipmi_msghandler 102400 2 ipmi_devintf,nvidia drm_kms_helper172032 2 nvidia_drm,i915 drm 458752 13 drm_kms_helper,nvidia_drm,i915 Alternatively, just set WaylandEnable to false (and restart gdm). cat /etc/gdm3/custom.conf # ... [daemon] # Uncoment the line below to force the login screen to use Xorg WaylandEnable=false # ... I also suspect that /etc/X11/xorg.conf generated by nvidia-xconfig (which I ran during driver installation from the website) was causing issues. Steps I performed from a VT session: 1) sudo apt purge 'nvidia*' 2) reboot 3) sudo rm /etc/X11/xorg.conf 4) sudo apt install nvidia-driver- nvidia-dkms- nvidia-settings nvidia-prime 5) reboot I also have 11-nvidia-prime.conf file at /usr/share/X11/xorg.conf.d which is generated by ubuntu-drivers-common: cat /usr/share/X11/xorg.conf.d/11-nvidia-prime.conf # DO NOT EDIT. AUTOMATICALLY GENERATED BY gpu-manager Section "OutputClass" Identifier "Nvidia Prime" MatchDriver "nvidia-drm" Driver "nvidia" Option "AllowEmptyInitialConfiguration" Option "IgnoreDisplayDevices" "CRT" Option "PrimaryGPU" "Yes" ModulePath "/x86_64-linux-gnu/nvidia/xorg" EndSection dpkg -l | grep ubuntu-drivers-common ii ubuntu-drivers-common 1:0.5.2.2 https://github.com/tseliot/ubuntu-drivers- common/blob/bionic/share/hybrid/gpu-manager.c#L1359-L1375 ** Attachment added: "nvidia-x-server-settings-graphics-ppa-415-hwe-4.18-bionic.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785964/+attachment/5239177/+files/nvidia-x-server-settings-graphics-ppa-415-hwe-4.18-bionic.png -- 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/1785964 Title: Unable to unlock the desktop session: systemd-logind: got pause for 13:69 Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Confirmed Bug description: When this issue happens, you won't be able to unlock your desktop session (VT works fine). This happened twice today for me, one is after a suspend, one is just a screen lock. Not sure what is the trigger yet. Syndrome: On the login screen after typing the correct password, you will see a small circle keep spinning and that's it. I need to restart my computer to get it back to normal. In the syslog this error message looks fishy: Aug 8 10:44:57 Leggiero gnome-shell[2118]: g_array_unref: assertion 'array' failed This is part of the syslog fetching from a VT after a GUI unlock attempt (session 24 is the desktop login attempt): Aug 8 10:44:42 Leggiero systemd[1]: Started Session 24 of user sam. Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 226:0 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) AIGLX: Resuming AIGLX clients after VT switch Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): EDID vendor "AUO", prod id 4204 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Printing DDC gathered Modelines: Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Modeline "1366x768"x0.0 76.20 1366 1404 1426 1590 768 771 777 798 +hsync -vsync (47.9 kHz eP) Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Modeline "1366x768"x0.0 76.20 1366 1404 1426 1988 768 771 777 798 +hsync -vsync (38.3 kHz e) Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:78 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - Dell WMI hotkeys: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - Dell WMI hotkeys: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:66 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2 - Sleep Button: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2 - Sleep Button: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:79 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - Integrated_Webcam_HD: Integrate: is tagged by udev as: Keyboard Aug 8
[Kernel-packages] [Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69
nvidia-xconfig -generated xorg.conf looked like this https://paste.ubuntu.com/p/4hRVzHmbJV/ -- 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/1785964 Title: Unable to unlock the desktop session: systemd-logind: got pause for 13:69 Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Confirmed Bug description: When this issue happens, you won't be able to unlock your desktop session (VT works fine). This happened twice today for me, one is after a suspend, one is just a screen lock. Not sure what is the trigger yet. Syndrome: On the login screen after typing the correct password, you will see a small circle keep spinning and that's it. I need to restart my computer to get it back to normal. In the syslog this error message looks fishy: Aug 8 10:44:57 Leggiero gnome-shell[2118]: g_array_unref: assertion 'array' failed This is part of the syslog fetching from a VT after a GUI unlock attempt (session 24 is the desktop login attempt): Aug 8 10:44:42 Leggiero systemd[1]: Started Session 24 of user sam. Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 226:0 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) AIGLX: Resuming AIGLX clients after VT switch Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): EDID vendor "AUO", prod id 4204 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Printing DDC gathered Modelines: Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Modeline "1366x768"x0.0 76.20 1366 1404 1426 1590 768 771 777 798 +hsync -vsync (47.9 kHz eP) Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Modeline "1366x768"x0.0 76.20 1366 1404 1426 1988 768 771 777 798 +hsync -vsync (38.3 kHz e) Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:78 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - Dell WMI hotkeys: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - Dell WMI hotkeys: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:66 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2 - Sleep Button: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2 - Sleep Button: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:79 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - Integrated_Webcam_HD: Integrate: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - Integrated_Webcam_HD: Integrate: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:68 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4 - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4 - AT Translated Set 2 keyboard: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:67 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3 - Power Button: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3 - Power Button: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:71 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7 - AlpsPS/2 ALPS GlidePoint: is tagged by udev as: Touchpad Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7 - AlpsPS/2 ALPS GlidePoint: device is a touchpad Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:72 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8 - DELL Wireless hotkeys: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8 - DELL Wireless hotkeys: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) libinput: PixArt Microsoft USB Optical Mouse: SetProperty on 286 called but device is disabled. Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: This driver cannot change properties on a disabled device Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:65 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event1 - Power Button: is tagged
Re: [Kernel-packages] [Bug 1815808] Re: Thunderbolt Ethernet high-traffic exception
I tried what you suggested. Ethtool reported no changes in configuration when I turned off receive offload. It reported substantial changes when I turned off transmit offload. After turning off transmit offload, transmit rate dropped from 930 Mb/s to abut 660 Mb/s, although I did not see a big CPU hit. Receive speeds were not affected by turning off receive offload. gene-pc:~$ sudo ethtool --offload eth0 rx off gene-pc:~$ sudo ethtool --offload eth0 tx off Actual changes: tx-checksumming: off tx-checksum-ipv4: off tx-checksum-ipv6: off tcp-segmentation-offload: off tx-tcp-segmentation: off [requested on] tx-tcp6-segmentation: off [requested on] gene-pc:~$ Unfortunately, after doing this, I have had great difficulty reproducing the crash, and I do not know why. Here's what changed: I did a routine apt update, but I did not get a new kernel. I installed ethtool, and did the command you suggested. After doing that, the system refused to crash either transmit or receive. So I rebooted, this time did not run ethtool, and the system again refused to crash. Previously I could reproduce the crash in about 30 seconds. Now I cannot reproduce the crash after over an hour. An hour of transmit, and an hour of receive. And an hour bidirectional. I do not know why. One problem here is that I test at home and at work, with the same computer, but with a different TB-10 dock, monitor, keyboard, mouse. Previous to my bug report, I had never seen the problem at home. The bug report I sent was from work. Since receiving your request for information, I cannot readily reproduce the problem either at home or at work. Except once. I did see a crash at home when *I unplugged/plugged in a keyboard while the test was going on*. I have attached three lsusb outputs: - usb.work →At work, system healthy. - usb.home → At home, system healthy. - usb.failed → At home, after the crash where I moved the keyboard What else can I do to help diagnose the problem? On Thu, Feb 14, 2019 at 11:05 PM Anthony Wong wrote: > ** Changed in: linux (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1815808 > > Title: > Thunderbolt Ethernet high-traffic exception > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > Running iperf3 on Dell XP-15 with TB-10 Thunderbolt dock causes a > kernel exception and ethernet failure after about 30 seconds. > > Easy to reproduce. Connect to another machine via Gig-E and run > iperf3 in either direction until the problem occurs. Should run 900+ > Mb in either direction. On one occasion I also lost the USB ports. > However the display continues to work. > > > # uname -a > Linux hauser 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC > 2019 x86_64 x86_64 x86_64 GNU/Linux > # apt install iperf3 > # iperf3 -s > > > # apt install iperf3 > # iperf3 -c my-machine -t 1000 # send to my machine > # iperf3 -c my-machine -t 1000 -R # receive data from my machine > > When the bitrate drops to zero, look in syslog for the exception. > > Note: Until recently the TB-10 Ethernet would not receive full speed. > (prior to -43 kernel) Did not see this problem before the Ethernet > performance increased. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: linux-image-4.15.0-45-generic 4.15.0-45.48 > ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 > Uname: Linux 4.15.0-45-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.20.9-0ubuntu7.5 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: gene 1994 F pulseaudio > CurrentDesktop: ubuntu:GNOME > Date: Wed Feb 13 13:54:28 2019 > HibernationDevice: RESUME=UUID=d15ecb23-8691-42a1-9909-a56f934b536c > InstallationDate: Installed on 2018-11-19 (86 days ago) > InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 > (20180725) > MachineType: Dell Inc. XPS 15 9570 > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic > root=UUID=a73e2d3e-5ce3-4130-917d-d116c1316153 ro net.ifnames=0 > mem_sleep_default=deep > RelatedPackageVersions: >linux-restricted-modules-4.15.0-45-generic N/A >linux-backports-modules-4.15.0-45-generic N/A >linux-firmware 1.173.3 > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 12/25/2018 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 1.7.0 > dmi.board.name: 02MJVY > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 10 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvr1.7.0:bd12/25/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn02MJVY:rvrA00:cvnDellInc.:ct10:cvr: >
[Kernel-packages] [Bug 1795453] Re: [SRU] IO's are issued with incorrect Scatter Gather Buffer
** Changed in: linux (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- 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/1795453 Title: [SRU] IO's are issued with incorrect Scatter Gather Buffer Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Bug description: [Impact] We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect Scatter Gather Buffer address . i.e OS is sending the IO with 64 bit Scatter Gather Buffer address , such that if we add the length with buffer address then it causes the roll over . Here is the data we captured in our driver (Printed the SGE details which was sent by OS) sgl_ptr->Address = f000 [14547.313240] sgl_ptr->Length = 1000 [14547.313241] sge_count = 18 [14547.313242] cmd->index = 9d9 Note : This issue is observed only when virtualization is enabled Product : Broadcom (LSI) Megaraid H840 controller [Test Case] Steps found in comment #60 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795453/comments/60 [Regression Potential] The patches in Comment #59 have been accepted upstream. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795453/comments/59 [Other Info] Product : Broadcom (LSI) Megaraid H840 controller --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 12 16:35 seq crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R7415 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.18.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 09/07/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.2 dmi.board.vendor: Dell Inc. dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R7415 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 12 16:35 seq crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R7415 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.18.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True
[Kernel-packages] [Bug 1813873] Re: Userspace break as a result of missing patch backport
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1813873 Title: Userspace break as a result of missing patch backport Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Released Bug description: Hi, The most recent set of Ubuntu kernels applied a variety of tty patches including: https://github.com/torvalds/linux/commit/c96cf923a98d1b094df9f0cf97a83e118817e31b But have not applied the more recent https://github.com/torvalds/linux/commit/d3736d82e8169768218ee0ef68718875918091a0 patch. This second patch is required to prevent a rather serious regression where userspace applications reading from stdin can receive EAGAIN when they should not. I will try to link correspondence from the mailing list archives once they are available, but for now if you have access to the linux- console mailing list you can find discussion under the thread "Userspace break? read from STDIN returns EAGAIN if tty is "touched"". I would appreciate it if this could be examined soon as it is a regression on userspace. Thanks Michael Good: 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 Bad: 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813873/+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 549741] Re: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages
** Tags removed: cosmic wayland-session ** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/549741/+attachment/5239110/+files/WifiSyslog.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/549741/+attachment/5239109/+files/UdevDb.txt ** Attachment removed: "PulseList.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/549741/+attachment/5239108/+files/PulseList.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/549741/+attachment/5239106/+files/ProcInterrupts.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/549741/+attachment/5239105/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/549741/+attachment/5239107/+files/ProcModules.txt ** Attachment removed: "ProcCpuinfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/549741/+attachment/5239104/+files/ProcCpuinfo.txt ** Attachment removed: "Lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/549741/+attachment/5239103/+files/Lsusb.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/549741/+attachment/5239102/+files/Lspci.txt ** Attachment removed: "IwConfig.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/549741/+attachment/5239101/+files/IwConfig.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/549741/+attachment/5239100/+files/CurrentDmesg.txt ** Attachment removed: "CRDA.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/549741/+attachment/5239099/+files/CRDA.txt ** Attachment removed: "AlsaInfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/549741/+attachment/5239098/+files/AlsaInfo.txt -- 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/549741 Title: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages Status in linux package in Ubuntu: Invalid Bug description: hi Running Ubuntu Lucid amd64 on a Dell Latitude 131L (AMD chips), updated twice a day at the moment. Linux seems not to recognize the keyboard in my laptop well. Starting early in the boot process (well before X kicks in) I see error messages on the screen. The same messages then swamp the logs. A sample: = [19667.508573] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19667.508580] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.588701] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19668.588712] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.600223] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19668.600230] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.717801] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19669.717811] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.729365] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19669.729373] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.825302] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19670.825313] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.835700] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19670.835707] atkbd.c: Use 'setkeycodes e00d ' to make it known. = This goes on every second until shut down. It's been there for a while now, but I haven't made -or found- a bug report about it yet. I did some googling and it seems related to not-so-standard handling of hotkeys (which you would find on a laptop) by the bios. However, I have not found a solution. It is possible to 'shut up' the messages by assigning e00d to an unused keycode, but that is just hiding the symptom. Also that kills the screen saver / blackout and it breaks my repeating keys, so not an option really. WORKAROUND: - shutdown the pc - Remove both battery and AC - push the 'on' switch several times - Plug the battery and AC back in --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of PLAYBACK Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas
[Kernel-packages] [Bug 549741] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/549741/+attachment/5239107/+files/ProcModules.txt -- 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/549741 Title: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages Status in linux package in Ubuntu: Invalid Bug description: hi Running Ubuntu Lucid amd64 on a Dell Latitude 131L (AMD chips), updated twice a day at the moment. Linux seems not to recognize the keyboard in my laptop well. Starting early in the boot process (well before X kicks in) I see error messages on the screen. The same messages then swamp the logs. A sample: = [19667.508573] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19667.508580] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.588701] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19668.588712] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.600223] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19668.600230] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.717801] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19669.717811] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.729365] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19669.729373] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.825302] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19670.825313] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.835700] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19670.835707] atkbd.c: Use 'setkeycodes e00d ' to make it known. = This goes on every second until shut down. It's been there for a while now, but I haven't made -or found- a bug report about it yet. I did some googling and it seems related to not-so-standard handling of hotkeys (which you would find on a laptop) by the bios. However, I have not found a solution. It is possible to 'shut up' the messages by assigning e00d to an unused keycode, but that is just hiding the symptom. Also that kills the screen saver / blackout and it breaks my repeating keys, so not an option really. WORKAROUND: - shutdown the pc - Remove both battery and AC - push the 'on' switch several times - Plug the battery and AC back in --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of PLAYBACK Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1529 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xc000 irq 16' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:14f12bfa,14f100c3,0009 HDA:83847690,102801f6,00102201' Controls : 6 Simple ctrls : 4 CheckboxSubmission: 41a9dc4bbc2c91d7f7445d204c57c74b CheckboxSystem: d00f84de8a555815fa1c4660280da308 DistroRelease: Ubuntu 10.04 HibernationDevice: RESUME=UUID=f83c27ce-b7e6-4250-967c-1920bb543ba0 InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' MachineType: Dell Inc. Latitude 131L Package: linux (not installed) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic root=UUID=46062d1f-f00c-4276-9ff1-541279640a93 ro single nomodeset ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 Regression: No RelatedPackageVersions: linux-firmware 1.33 Reproducible: Yes Tags: lucid TestedUpstream: Yes Uname: Linux 2.6.32-17-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 05/30/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.1 dmi.board.name: 0PM607?? dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.4.1:bd05/30/2006:svnDellInc.:pnLatitude131L:pvrNotSpecified:rvnDellInc.:rn0PM607??:rvr:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Latitude 131L dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of
[Kernel-packages] [Bug 549741] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/549741/+attachment/5239110/+files/WifiSyslog.txt -- 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/549741 Title: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages Status in linux package in Ubuntu: Invalid Bug description: hi Running Ubuntu Lucid amd64 on a Dell Latitude 131L (AMD chips), updated twice a day at the moment. Linux seems not to recognize the keyboard in my laptop well. Starting early in the boot process (well before X kicks in) I see error messages on the screen. The same messages then swamp the logs. A sample: = [19667.508573] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19667.508580] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.588701] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19668.588712] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.600223] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19668.600230] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.717801] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19669.717811] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.729365] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19669.729373] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.825302] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19670.825313] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.835700] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19670.835707] atkbd.c: Use 'setkeycodes e00d ' to make it known. = This goes on every second until shut down. It's been there for a while now, but I haven't made -or found- a bug report about it yet. I did some googling and it seems related to not-so-standard handling of hotkeys (which you would find on a laptop) by the bios. However, I have not found a solution. It is possible to 'shut up' the messages by assigning e00d to an unused keycode, but that is just hiding the symptom. Also that kills the screen saver / blackout and it breaks my repeating keys, so not an option really. WORKAROUND: - shutdown the pc - Remove both battery and AC - push the 'on' switch several times - Plug the battery and AC back in --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of PLAYBACK Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1529 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xc000 irq 16' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:14f12bfa,14f100c3,0009 HDA:83847690,102801f6,00102201' Controls : 6 Simple ctrls : 4 CheckboxSubmission: 41a9dc4bbc2c91d7f7445d204c57c74b CheckboxSystem: d00f84de8a555815fa1c4660280da308 DistroRelease: Ubuntu 10.04 HibernationDevice: RESUME=UUID=f83c27ce-b7e6-4250-967c-1920bb543ba0 InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' MachineType: Dell Inc. Latitude 131L Package: linux (not installed) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic root=UUID=46062d1f-f00c-4276-9ff1-541279640a93 ro single nomodeset ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 Regression: No RelatedPackageVersions: linux-firmware 1.33 Reproducible: Yes Tags: lucid TestedUpstream: Yes Uname: Linux 2.6.32-17-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 05/30/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.1 dmi.board.name: 0PM607?? dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.4.1:bd05/30/2006:svnDellInc.:pnLatitude131L:pvrNotSpecified:rvnDellInc.:rn0PM607??:rvr:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Latitude 131L dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of
[Kernel-packages] [Bug 549741] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/549741/+attachment/5239108/+files/PulseList.txt -- 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/549741 Title: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages Status in linux package in Ubuntu: Invalid Bug description: hi Running Ubuntu Lucid amd64 on a Dell Latitude 131L (AMD chips), updated twice a day at the moment. Linux seems not to recognize the keyboard in my laptop well. Starting early in the boot process (well before X kicks in) I see error messages on the screen. The same messages then swamp the logs. A sample: = [19667.508573] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19667.508580] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.588701] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19668.588712] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.600223] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19668.600230] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.717801] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19669.717811] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.729365] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19669.729373] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.825302] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19670.825313] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.835700] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19670.835707] atkbd.c: Use 'setkeycodes e00d ' to make it known. = This goes on every second until shut down. It's been there for a while now, but I haven't made -or found- a bug report about it yet. I did some googling and it seems related to not-so-standard handling of hotkeys (which you would find on a laptop) by the bios. However, I have not found a solution. It is possible to 'shut up' the messages by assigning e00d to an unused keycode, but that is just hiding the symptom. Also that kills the screen saver / blackout and it breaks my repeating keys, so not an option really. WORKAROUND: - shutdown the pc - Remove both battery and AC - push the 'on' switch several times - Plug the battery and AC back in --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of PLAYBACK Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1529 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xc000 irq 16' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:14f12bfa,14f100c3,0009 HDA:83847690,102801f6,00102201' Controls : 6 Simple ctrls : 4 CheckboxSubmission: 41a9dc4bbc2c91d7f7445d204c57c74b CheckboxSystem: d00f84de8a555815fa1c4660280da308 DistroRelease: Ubuntu 10.04 HibernationDevice: RESUME=UUID=f83c27ce-b7e6-4250-967c-1920bb543ba0 InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' MachineType: Dell Inc. Latitude 131L Package: linux (not installed) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic root=UUID=46062d1f-f00c-4276-9ff1-541279640a93 ro single nomodeset ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 Regression: No RelatedPackageVersions: linux-firmware 1.33 Reproducible: Yes Tags: lucid TestedUpstream: Yes Uname: Linux 2.6.32-17-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 05/30/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.1 dmi.board.name: 0PM607?? dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.4.1:bd05/30/2006:svnDellInc.:pnLatitude131L:pvrNotSpecified:rvnDellInc.:rn0PM607??:rvr:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Latitude 131L dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of PLAYBACK
[Kernel-packages] [Bug 549741] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/549741/+attachment/5239109/+files/UdevDb.txt -- 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/549741 Title: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages Status in linux package in Ubuntu: Invalid Bug description: hi Running Ubuntu Lucid amd64 on a Dell Latitude 131L (AMD chips), updated twice a day at the moment. Linux seems not to recognize the keyboard in my laptop well. Starting early in the boot process (well before X kicks in) I see error messages on the screen. The same messages then swamp the logs. A sample: = [19667.508573] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19667.508580] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.588701] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19668.588712] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.600223] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19668.600230] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.717801] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19669.717811] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.729365] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19669.729373] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.825302] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19670.825313] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.835700] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19670.835707] atkbd.c: Use 'setkeycodes e00d ' to make it known. = This goes on every second until shut down. It's been there for a while now, but I haven't made -or found- a bug report about it yet. I did some googling and it seems related to not-so-standard handling of hotkeys (which you would find on a laptop) by the bios. However, I have not found a solution. It is possible to 'shut up' the messages by assigning e00d to an unused keycode, but that is just hiding the symptom. Also that kills the screen saver / blackout and it breaks my repeating keys, so not an option really. WORKAROUND: - shutdown the pc - Remove both battery and AC - push the 'on' switch several times - Plug the battery and AC back in --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of PLAYBACK Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1529 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xc000 irq 16' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:14f12bfa,14f100c3,0009 HDA:83847690,102801f6,00102201' Controls : 6 Simple ctrls : 4 CheckboxSubmission: 41a9dc4bbc2c91d7f7445d204c57c74b CheckboxSystem: d00f84de8a555815fa1c4660280da308 DistroRelease: Ubuntu 10.04 HibernationDevice: RESUME=UUID=f83c27ce-b7e6-4250-967c-1920bb543ba0 InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' MachineType: Dell Inc. Latitude 131L Package: linux (not installed) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic root=UUID=46062d1f-f00c-4276-9ff1-541279640a93 ro single nomodeset ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 Regression: No RelatedPackageVersions: linux-firmware 1.33 Reproducible: Yes Tags: lucid TestedUpstream: Yes Uname: Linux 2.6.32-17-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 05/30/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.1 dmi.board.name: 0PM607?? dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.4.1:bd05/30/2006:svnDellInc.:pnLatitude131L:pvrNotSpecified:rvnDellInc.:rn0PM607??:rvr:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Latitude 131L dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of PLAYBACK
[Kernel-packages] [Bug 549741] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/549741/+attachment/5239106/+files/ProcInterrupts.txt -- 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/549741 Title: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages Status in linux package in Ubuntu: Invalid Bug description: hi Running Ubuntu Lucid amd64 on a Dell Latitude 131L (AMD chips), updated twice a day at the moment. Linux seems not to recognize the keyboard in my laptop well. Starting early in the boot process (well before X kicks in) I see error messages on the screen. The same messages then swamp the logs. A sample: = [19667.508573] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19667.508580] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.588701] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19668.588712] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.600223] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19668.600230] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.717801] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19669.717811] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.729365] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19669.729373] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.825302] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19670.825313] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.835700] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19670.835707] atkbd.c: Use 'setkeycodes e00d ' to make it known. = This goes on every second until shut down. It's been there for a while now, but I haven't made -or found- a bug report about it yet. I did some googling and it seems related to not-so-standard handling of hotkeys (which you would find on a laptop) by the bios. However, I have not found a solution. It is possible to 'shut up' the messages by assigning e00d to an unused keycode, but that is just hiding the symptom. Also that kills the screen saver / blackout and it breaks my repeating keys, so not an option really. WORKAROUND: - shutdown the pc - Remove both battery and AC - push the 'on' switch several times - Plug the battery and AC back in --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of PLAYBACK Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1529 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xc000 irq 16' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:14f12bfa,14f100c3,0009 HDA:83847690,102801f6,00102201' Controls : 6 Simple ctrls : 4 CheckboxSubmission: 41a9dc4bbc2c91d7f7445d204c57c74b CheckboxSystem: d00f84de8a555815fa1c4660280da308 DistroRelease: Ubuntu 10.04 HibernationDevice: RESUME=UUID=f83c27ce-b7e6-4250-967c-1920bb543ba0 InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' MachineType: Dell Inc. Latitude 131L Package: linux (not installed) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic root=UUID=46062d1f-f00c-4276-9ff1-541279640a93 ro single nomodeset ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 Regression: No RelatedPackageVersions: linux-firmware 1.33 Reproducible: Yes Tags: lucid TestedUpstream: Yes Uname: Linux 2.6.32-17-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 05/30/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.1 dmi.board.name: 0PM607?? dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.4.1:bd05/30/2006:svnDellInc.:pnLatitude131L:pvrNotSpecified:rvnDellInc.:rn0PM607??:rvr:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Latitude 131L dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of
[Kernel-packages] [Bug 549741] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/549741/+attachment/5239102/+files/Lspci.txt -- 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/549741 Title: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages Status in linux package in Ubuntu: Invalid Bug description: hi Running Ubuntu Lucid amd64 on a Dell Latitude 131L (AMD chips), updated twice a day at the moment. Linux seems not to recognize the keyboard in my laptop well. Starting early in the boot process (well before X kicks in) I see error messages on the screen. The same messages then swamp the logs. A sample: = [19667.508573] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19667.508580] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.588701] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19668.588712] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.600223] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19668.600230] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.717801] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19669.717811] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.729365] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19669.729373] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.825302] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19670.825313] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.835700] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19670.835707] atkbd.c: Use 'setkeycodes e00d ' to make it known. = This goes on every second until shut down. It's been there for a while now, but I haven't made -or found- a bug report about it yet. I did some googling and it seems related to not-so-standard handling of hotkeys (which you would find on a laptop) by the bios. However, I have not found a solution. It is possible to 'shut up' the messages by assigning e00d to an unused keycode, but that is just hiding the symptom. Also that kills the screen saver / blackout and it breaks my repeating keys, so not an option really. WORKAROUND: - shutdown the pc - Remove both battery and AC - push the 'on' switch several times - Plug the battery and AC back in --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of PLAYBACK Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1529 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xc000 irq 16' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:14f12bfa,14f100c3,0009 HDA:83847690,102801f6,00102201' Controls : 6 Simple ctrls : 4 CheckboxSubmission: 41a9dc4bbc2c91d7f7445d204c57c74b CheckboxSystem: d00f84de8a555815fa1c4660280da308 DistroRelease: Ubuntu 10.04 HibernationDevice: RESUME=UUID=f83c27ce-b7e6-4250-967c-1920bb543ba0 InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' MachineType: Dell Inc. Latitude 131L Package: linux (not installed) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic root=UUID=46062d1f-f00c-4276-9ff1-541279640a93 ro single nomodeset ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 Regression: No RelatedPackageVersions: linux-firmware 1.33 Reproducible: Yes Tags: lucid TestedUpstream: Yes Uname: Linux 2.6.32-17-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 05/30/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.1 dmi.board.name: 0PM607?? dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.4.1:bd05/30/2006:svnDellInc.:pnLatitude131L:pvrNotSpecified:rvnDellInc.:rn0PM607??:rvr:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Latitude 131L dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of PLAYBACK Hardware
[Kernel-packages] [Bug 549741] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/549741/+attachment/5239101/+files/IwConfig.txt -- 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/549741 Title: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages Status in linux package in Ubuntu: Invalid Bug description: hi Running Ubuntu Lucid amd64 on a Dell Latitude 131L (AMD chips), updated twice a day at the moment. Linux seems not to recognize the keyboard in my laptop well. Starting early in the boot process (well before X kicks in) I see error messages on the screen. The same messages then swamp the logs. A sample: = [19667.508573] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19667.508580] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.588701] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19668.588712] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.600223] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19668.600230] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.717801] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19669.717811] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.729365] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19669.729373] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.825302] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19670.825313] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.835700] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19670.835707] atkbd.c: Use 'setkeycodes e00d ' to make it known. = This goes on every second until shut down. It's been there for a while now, but I haven't made -or found- a bug report about it yet. I did some googling and it seems related to not-so-standard handling of hotkeys (which you would find on a laptop) by the bios. However, I have not found a solution. It is possible to 'shut up' the messages by assigning e00d to an unused keycode, but that is just hiding the symptom. Also that kills the screen saver / blackout and it breaks my repeating keys, so not an option really. WORKAROUND: - shutdown the pc - Remove both battery and AC - push the 'on' switch several times - Plug the battery and AC back in --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of PLAYBACK Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1529 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xc000 irq 16' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:14f12bfa,14f100c3,0009 HDA:83847690,102801f6,00102201' Controls : 6 Simple ctrls : 4 CheckboxSubmission: 41a9dc4bbc2c91d7f7445d204c57c74b CheckboxSystem: d00f84de8a555815fa1c4660280da308 DistroRelease: Ubuntu 10.04 HibernationDevice: RESUME=UUID=f83c27ce-b7e6-4250-967c-1920bb543ba0 InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' MachineType: Dell Inc. Latitude 131L Package: linux (not installed) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic root=UUID=46062d1f-f00c-4276-9ff1-541279640a93 ro single nomodeset ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 Regression: No RelatedPackageVersions: linux-firmware 1.33 Reproducible: Yes Tags: lucid TestedUpstream: Yes Uname: Linux 2.6.32-17-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 05/30/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.1 dmi.board.name: 0PM607?? dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.4.1:bd05/30/2006:svnDellInc.:pnLatitude131L:pvrNotSpecified:rvnDellInc.:rn0PM607??:rvr:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Latitude 131L dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of PLAYBACK
[Kernel-packages] [Bug 549741] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/549741/+attachment/5239105/+files/ProcCpuinfoMinimal.txt -- 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/549741 Title: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages Status in linux package in Ubuntu: Invalid Bug description: hi Running Ubuntu Lucid amd64 on a Dell Latitude 131L (AMD chips), updated twice a day at the moment. Linux seems not to recognize the keyboard in my laptop well. Starting early in the boot process (well before X kicks in) I see error messages on the screen. The same messages then swamp the logs. A sample: = [19667.508573] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19667.508580] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.588701] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19668.588712] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.600223] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19668.600230] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.717801] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19669.717811] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.729365] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19669.729373] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.825302] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19670.825313] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.835700] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19670.835707] atkbd.c: Use 'setkeycodes e00d ' to make it known. = This goes on every second until shut down. It's been there for a while now, but I haven't made -or found- a bug report about it yet. I did some googling and it seems related to not-so-standard handling of hotkeys (which you would find on a laptop) by the bios. However, I have not found a solution. It is possible to 'shut up' the messages by assigning e00d to an unused keycode, but that is just hiding the symptom. Also that kills the screen saver / blackout and it breaks my repeating keys, so not an option really. WORKAROUND: - shutdown the pc - Remove both battery and AC - push the 'on' switch several times - Plug the battery and AC back in --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of PLAYBACK Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1529 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xc000 irq 16' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:14f12bfa,14f100c3,0009 HDA:83847690,102801f6,00102201' Controls : 6 Simple ctrls : 4 CheckboxSubmission: 41a9dc4bbc2c91d7f7445d204c57c74b CheckboxSystem: d00f84de8a555815fa1c4660280da308 DistroRelease: Ubuntu 10.04 HibernationDevice: RESUME=UUID=f83c27ce-b7e6-4250-967c-1920bb543ba0 InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' MachineType: Dell Inc. Latitude 131L Package: linux (not installed) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic root=UUID=46062d1f-f00c-4276-9ff1-541279640a93 ro single nomodeset ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 Regression: No RelatedPackageVersions: linux-firmware 1.33 Reproducible: Yes Tags: lucid TestedUpstream: Yes Uname: Linux 2.6.32-17-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 05/30/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.1 dmi.board.name: 0PM607?? dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.4.1:bd05/30/2006:svnDellInc.:pnLatitude131L:pvrNotSpecified:rvnDellInc.:rn0PM607??:rvr:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Latitude 131L dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices:
[Kernel-packages] [Bug 549741] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/549741/+attachment/5239100/+files/CurrentDmesg.txt -- 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/549741 Title: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages Status in linux package in Ubuntu: Invalid Bug description: hi Running Ubuntu Lucid amd64 on a Dell Latitude 131L (AMD chips), updated twice a day at the moment. Linux seems not to recognize the keyboard in my laptop well. Starting early in the boot process (well before X kicks in) I see error messages on the screen. The same messages then swamp the logs. A sample: = [19667.508573] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19667.508580] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.588701] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19668.588712] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.600223] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19668.600230] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.717801] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19669.717811] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.729365] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19669.729373] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.825302] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19670.825313] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.835700] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19670.835707] atkbd.c: Use 'setkeycodes e00d ' to make it known. = This goes on every second until shut down. It's been there for a while now, but I haven't made -or found- a bug report about it yet. I did some googling and it seems related to not-so-standard handling of hotkeys (which you would find on a laptop) by the bios. However, I have not found a solution. It is possible to 'shut up' the messages by assigning e00d to an unused keycode, but that is just hiding the symptom. Also that kills the screen saver / blackout and it breaks my repeating keys, so not an option really. WORKAROUND: - shutdown the pc - Remove both battery and AC - push the 'on' switch several times - Plug the battery and AC back in --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of PLAYBACK Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1529 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xc000 irq 16' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:14f12bfa,14f100c3,0009 HDA:83847690,102801f6,00102201' Controls : 6 Simple ctrls : 4 CheckboxSubmission: 41a9dc4bbc2c91d7f7445d204c57c74b CheckboxSystem: d00f84de8a555815fa1c4660280da308 DistroRelease: Ubuntu 10.04 HibernationDevice: RESUME=UUID=f83c27ce-b7e6-4250-967c-1920bb543ba0 InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' MachineType: Dell Inc. Latitude 131L Package: linux (not installed) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic root=UUID=46062d1f-f00c-4276-9ff1-541279640a93 ro single nomodeset ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 Regression: No RelatedPackageVersions: linux-firmware 1.33 Reproducible: Yes Tags: lucid TestedUpstream: Yes Uname: Linux 2.6.32-17-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 05/30/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.1 dmi.board.name: 0PM607?? dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.4.1:bd05/30/2006:svnDellInc.:pnLatitude131L:pvrNotSpecified:rvnDellInc.:rn0PM607??:rvr:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Latitude 131L dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of
[Kernel-packages] [Bug 549741] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/549741/+attachment/5239104/+files/ProcCpuinfo.txt -- 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/549741 Title: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages Status in linux package in Ubuntu: Invalid Bug description: hi Running Ubuntu Lucid amd64 on a Dell Latitude 131L (AMD chips), updated twice a day at the moment. Linux seems not to recognize the keyboard in my laptop well. Starting early in the boot process (well before X kicks in) I see error messages on the screen. The same messages then swamp the logs. A sample: = [19667.508573] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19667.508580] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.588701] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19668.588712] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.600223] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19668.600230] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.717801] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19669.717811] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.729365] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19669.729373] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.825302] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19670.825313] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.835700] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19670.835707] atkbd.c: Use 'setkeycodes e00d ' to make it known. = This goes on every second until shut down. It's been there for a while now, but I haven't made -or found- a bug report about it yet. I did some googling and it seems related to not-so-standard handling of hotkeys (which you would find on a laptop) by the bios. However, I have not found a solution. It is possible to 'shut up' the messages by assigning e00d to an unused keycode, but that is just hiding the symptom. Also that kills the screen saver / blackout and it breaks my repeating keys, so not an option really. WORKAROUND: - shutdown the pc - Remove both battery and AC - push the 'on' switch several times - Plug the battery and AC back in --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of PLAYBACK Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1529 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xc000 irq 16' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:14f12bfa,14f100c3,0009 HDA:83847690,102801f6,00102201' Controls : 6 Simple ctrls : 4 CheckboxSubmission: 41a9dc4bbc2c91d7f7445d204c57c74b CheckboxSystem: d00f84de8a555815fa1c4660280da308 DistroRelease: Ubuntu 10.04 HibernationDevice: RESUME=UUID=f83c27ce-b7e6-4250-967c-1920bb543ba0 InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' MachineType: Dell Inc. Latitude 131L Package: linux (not installed) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic root=UUID=46062d1f-f00c-4276-9ff1-541279640a93 ro single nomodeset ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 Regression: No RelatedPackageVersions: linux-firmware 1.33 Reproducible: Yes Tags: lucid TestedUpstream: Yes Uname: Linux 2.6.32-17-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 05/30/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.1 dmi.board.name: 0PM607?? dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.4.1:bd05/30/2006:svnDellInc.:pnLatitude131L:pvrNotSpecified:rvnDellInc.:rn0PM607??:rvr:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Latitude 131L dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of
[Kernel-packages] [Bug 549741] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/549741/+attachment/5239103/+files/Lsusb.txt -- 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/549741 Title: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages Status in linux package in Ubuntu: Invalid Bug description: hi Running Ubuntu Lucid amd64 on a Dell Latitude 131L (AMD chips), updated twice a day at the moment. Linux seems not to recognize the keyboard in my laptop well. Starting early in the boot process (well before X kicks in) I see error messages on the screen. The same messages then swamp the logs. A sample: = [19667.508573] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19667.508580] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.588701] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19668.588712] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.600223] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19668.600230] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.717801] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19669.717811] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.729365] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19669.729373] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.825302] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19670.825313] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.835700] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19670.835707] atkbd.c: Use 'setkeycodes e00d ' to make it known. = This goes on every second until shut down. It's been there for a while now, but I haven't made -or found- a bug report about it yet. I did some googling and it seems related to not-so-standard handling of hotkeys (which you would find on a laptop) by the bios. However, I have not found a solution. It is possible to 'shut up' the messages by assigning e00d to an unused keycode, but that is just hiding the symptom. Also that kills the screen saver / blackout and it breaks my repeating keys, so not an option really. WORKAROUND: - shutdown the pc - Remove both battery and AC - push the 'on' switch several times - Plug the battery and AC back in --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of PLAYBACK Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1529 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xc000 irq 16' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:14f12bfa,14f100c3,0009 HDA:83847690,102801f6,00102201' Controls : 6 Simple ctrls : 4 CheckboxSubmission: 41a9dc4bbc2c91d7f7445d204c57c74b CheckboxSystem: d00f84de8a555815fa1c4660280da308 DistroRelease: Ubuntu 10.04 HibernationDevice: RESUME=UUID=f83c27ce-b7e6-4250-967c-1920bb543ba0 InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' MachineType: Dell Inc. Latitude 131L Package: linux (not installed) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic root=UUID=46062d1f-f00c-4276-9ff1-541279640a93 ro single nomodeset ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 Regression: No RelatedPackageVersions: linux-firmware 1.33 Reproducible: Yes Tags: lucid TestedUpstream: Yes Uname: Linux 2.6.32-17-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 05/30/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.1 dmi.board.name: 0PM607?? dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.4.1:bd05/30/2006:svnDellInc.:pnLatitude131L:pvrNotSpecified:rvnDellInc.:rn0PM607??:rvr:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Latitude 131L dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of PLAYBACK Hardware
[Kernel-packages] [Bug 549741] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/549741/+attachment/5239099/+files/CRDA.txt -- 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/549741 Title: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages Status in linux package in Ubuntu: Invalid Bug description: hi Running Ubuntu Lucid amd64 on a Dell Latitude 131L (AMD chips), updated twice a day at the moment. Linux seems not to recognize the keyboard in my laptop well. Starting early in the boot process (well before X kicks in) I see error messages on the screen. The same messages then swamp the logs. A sample: = [19667.508573] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19667.508580] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.588701] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19668.588712] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.600223] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19668.600230] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.717801] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19669.717811] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.729365] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19669.729373] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.825302] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19670.825313] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.835700] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19670.835707] atkbd.c: Use 'setkeycodes e00d ' to make it known. = This goes on every second until shut down. It's been there for a while now, but I haven't made -or found- a bug report about it yet. I did some googling and it seems related to not-so-standard handling of hotkeys (which you would find on a laptop) by the bios. However, I have not found a solution. It is possible to 'shut up' the messages by assigning e00d to an unused keycode, but that is just hiding the symptom. Also that kills the screen saver / blackout and it breaks my repeating keys, so not an option really. WORKAROUND: - shutdown the pc - Remove both battery and AC - push the 'on' switch several times - Plug the battery and AC back in --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of PLAYBACK Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1529 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xc000 irq 16' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:14f12bfa,14f100c3,0009 HDA:83847690,102801f6,00102201' Controls : 6 Simple ctrls : 4 CheckboxSubmission: 41a9dc4bbc2c91d7f7445d204c57c74b CheckboxSystem: d00f84de8a555815fa1c4660280da308 DistroRelease: Ubuntu 10.04 HibernationDevice: RESUME=UUID=f83c27ce-b7e6-4250-967c-1920bb543ba0 InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' MachineType: Dell Inc. Latitude 131L Package: linux (not installed) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic root=UUID=46062d1f-f00c-4276-9ff1-541279640a93 ro single nomodeset ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 Regression: No RelatedPackageVersions: linux-firmware 1.33 Reproducible: Yes Tags: lucid TestedUpstream: Yes Uname: Linux 2.6.32-17-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 05/30/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.1 dmi.board.name: 0PM607?? dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.4.1:bd05/30/2006:svnDellInc.:pnLatitude131L:pvrNotSpecified:rvnDellInc.:rn0PM607??:rvr:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Latitude 131L dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of PLAYBACK Hardware
[Kernel-packages] [Bug 549741] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/549741/+attachment/5239098/+files/AlsaInfo.txt -- 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/549741 Title: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages Status in linux package in Ubuntu: Invalid Bug description: hi Running Ubuntu Lucid amd64 on a Dell Latitude 131L (AMD chips), updated twice a day at the moment. Linux seems not to recognize the keyboard in my laptop well. Starting early in the boot process (well before X kicks in) I see error messages on the screen. The same messages then swamp the logs. A sample: = [19667.508573] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19667.508580] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.588701] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19668.588712] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.600223] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19668.600230] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.717801] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19669.717811] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.729365] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19669.729373] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.825302] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19670.825313] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.835700] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19670.835707] atkbd.c: Use 'setkeycodes e00d ' to make it known. = This goes on every second until shut down. It's been there for a while now, but I haven't made -or found- a bug report about it yet. I did some googling and it seems related to not-so-standard handling of hotkeys (which you would find on a laptop) by the bios. However, I have not found a solution. It is possible to 'shut up' the messages by assigning e00d to an unused keycode, but that is just hiding the symptom. Also that kills the screen saver / blackout and it breaks my repeating keys, so not an option really. WORKAROUND: - shutdown the pc - Remove both battery and AC - push the 'on' switch several times - Plug the battery and AC back in --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of PLAYBACK Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1529 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xc000 irq 16' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:14f12bfa,14f100c3,0009 HDA:83847690,102801f6,00102201' Controls : 6 Simple ctrls : 4 CheckboxSubmission: 41a9dc4bbc2c91d7f7445d204c57c74b CheckboxSystem: d00f84de8a555815fa1c4660280da308 DistroRelease: Ubuntu 10.04 HibernationDevice: RESUME=UUID=f83c27ce-b7e6-4250-967c-1920bb543ba0 InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' MachineType: Dell Inc. Latitude 131L Package: linux (not installed) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic root=UUID=46062d1f-f00c-4276-9ff1-541279640a93 ro single nomodeset ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 Regression: No RelatedPackageVersions: linux-firmware 1.33 Reproducible: Yes Tags: lucid TestedUpstream: Yes Uname: Linux 2.6.32-17-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 05/30/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.1 dmi.board.name: 0PM607?? dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.4.1:bd05/30/2006:svnDellInc.:pnLatitude131L:pvrNotSpecified:rvnDellInc.:rn0PM607??:rvr:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Latitude 131L dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of PLAYBACK
[Kernel-packages] [Bug 549741] Re: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages
ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugene 1974 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=7824e0a4-dd46-461a-a5fc-97a61d2fae5a MachineType: Dell Inc. Inspiron 1501 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=ae9b9898-729f-4cdc-9d2a-adc0fa9fcc07 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.175.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: wayland-session cosmic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-09-29 (139 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/07/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.3 dmi.board.name: 0UW744 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.6.3:bd12/07/2007:svnDellInc.:pnInspiron1501:pvrNotSpecified:rvnDellInc.:rn0UW744:rvr:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 1501 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. ** Tags added: cosmic wayland-session -- 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/549741 Title: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages Status in linux package in Ubuntu: Invalid Bug description: hi Running Ubuntu Lucid amd64 on a Dell Latitude 131L (AMD chips), updated twice a day at the moment. Linux seems not to recognize the keyboard in my laptop well. Starting early in the boot process (well before X kicks in) I see error messages on the screen. The same messages then swamp the logs. A sample: = [19667.508573] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19667.508580] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.588701] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19668.588712] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.600223] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19668.600230] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.717801] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19669.717811] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.729365] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19669.729373] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.825302] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19670.825313] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.835700] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19670.835707] atkbd.c: Use 'setkeycodes e00d ' to make it known. = This goes on every second until shut down. It's been there for a while now, but I haven't made -or found- a bug report about it yet. I did some googling and it seems related to not-so-standard handling of hotkeys (which you would find on a laptop) by the bios. However, I have not found a solution. It is possible to 'shut up' the messages by assigning e00d to an unused keycode, but that is just hiding the symptom. Also that kills the screen saver / blackout and it breaks my repeating keys, so not an option really. WORKAROUND: - shutdown the pc - Remove both battery and AC - push the 'on' switch several times - Plug the battery and AC back in --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of PLAYBACK Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1529 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xc000 irq 16' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:14f12bfa,14f100c3,0009 HDA:83847690,102801f6,00102201'
[Kernel-packages] [Bug 549741] Re: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages
Tom Louwrier, this report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/549741/comments/82 regarding you no longer have the hardware. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find. ** Changed in: linux (Ubuntu) Status: Incomplete => 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/549741 Title: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages Status in linux package in Ubuntu: Invalid Bug description: hi Running Ubuntu Lucid amd64 on a Dell Latitude 131L (AMD chips), updated twice a day at the moment. Linux seems not to recognize the keyboard in my laptop well. Starting early in the boot process (well before X kicks in) I see error messages on the screen. The same messages then swamp the logs. A sample: = [19667.508573] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19667.508580] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.588701] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19668.588712] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.600223] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19668.600230] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.717801] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19669.717811] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.729365] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19669.729373] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.825302] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19670.825313] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.835700] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19670.835707] atkbd.c: Use 'setkeycodes e00d ' to make it known. = This goes on every second until shut down. It's been there for a while now, but I haven't made -or found- a bug report about it yet. I did some googling and it seems related to not-so-standard handling of hotkeys (which you would find on a laptop) by the bios. However, I have not found a solution. It is possible to 'shut up' the messages by assigning e00d to an unused keycode, but that is just hiding the symptom. Also that kills the screen saver / blackout and it breaks my repeating keys, so not an option really. WORKAROUND: - shutdown the pc - Remove both battery and AC - push the 'on' switch several times - Plug the battery and AC back in --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of PLAYBACK Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1529 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xc000 irq 16' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:14f12bfa,14f100c3,0009 HDA:83847690,102801f6,00102201' Controls : 6 Simple ctrls : 4 CheckboxSubmission: 41a9dc4bbc2c91d7f7445d204c57c74b CheckboxSystem: d00f84de8a555815fa1c4660280da308 DistroRelease: Ubuntu 10.04 HibernationDevice: RESUME=UUID=f83c27ce-b7e6-4250-967c-1920bb543ba0 InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' MachineType: Dell Inc. Latitude 131L Package: linux (not installed) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic root=UUID=46062d1f-f00c-4276-9ff1-541279640a93 ro single nomodeset ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 Regression: No RelatedPackageVersions: linux-firmware 1.33 Reproducible: Yes Tags: lucid TestedUpstream: Yes Uname: Linux 2.6.32-17-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 05/30/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.1 dmi.board.name: 0PM607??
[Kernel-packages] [Bug 549741] Re: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages
hi guys, Well now, that is one old bug I reported. The 'powerd down, remove battery, restart it all' workaround didn't quite fix it for me but it was no big deal otherwise. And since the laptop had died since then I have no problem if we close this bug. cheers Tom -- 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/549741 Title: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages Status in linux package in Ubuntu: Incomplete Bug description: hi Running Ubuntu Lucid amd64 on a Dell Latitude 131L (AMD chips), updated twice a day at the moment. Linux seems not to recognize the keyboard in my laptop well. Starting early in the boot process (well before X kicks in) I see error messages on the screen. The same messages then swamp the logs. A sample: = [19667.508573] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19667.508580] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.588701] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19668.588712] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.600223] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19668.600230] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.717801] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19669.717811] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.729365] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19669.729373] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.825302] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19670.825313] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.835700] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19670.835707] atkbd.c: Use 'setkeycodes e00d ' to make it known. = This goes on every second until shut down. It's been there for a while now, but I haven't made -or found- a bug report about it yet. I did some googling and it seems related to not-so-standard handling of hotkeys (which you would find on a laptop) by the bios. However, I have not found a solution. It is possible to 'shut up' the messages by assigning e00d to an unused keycode, but that is just hiding the symptom. Also that kills the screen saver / blackout and it breaks my repeating keys, so not an option really. WORKAROUND: - shutdown the pc - Remove both battery and AC - push the 'on' switch several times - Plug the battery and AC back in --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of PLAYBACK Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1529 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xc000 irq 16' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:14f12bfa,14f100c3,0009 HDA:83847690,102801f6,00102201' Controls : 6 Simple ctrls : 4 CheckboxSubmission: 41a9dc4bbc2c91d7f7445d204c57c74b CheckboxSystem: d00f84de8a555815fa1c4660280da308 DistroRelease: Ubuntu 10.04 HibernationDevice: RESUME=UUID=f83c27ce-b7e6-4250-967c-1920bb543ba0 InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' MachineType: Dell Inc. Latitude 131L Package: linux (not installed) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic root=UUID=46062d1f-f00c-4276-9ff1-541279640a93 ro single nomodeset ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 Regression: No RelatedPackageVersions: linux-firmware 1.33 Reproducible: Yes Tags: lucid TestedUpstream: Yes Uname: Linux 2.6.32-17-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 05/30/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.1 dmi.board.name: 0PM607?? dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.4.1:bd05/30/2006:svnDellInc.:pnLatitude131L:pvrNotSpecified:rvnDellInc.:rn0PM607??:rvr:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Latitude 131L dmi.product.version: Not Specified dmi.sys.vendor:
[Kernel-packages] [Bug 549741] Re: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages
Eugene Savelov, RedHat bug 454131 was opened and closed by you (not someone who represents upstream or RedHat): https://bugzilla.redhat.com/show_activity.cgi?id=454131 Despite this, regarding a way forward here on Launchpad, if you want your problem addressed, it will help immensely if you use Ubuntu with the computer the problem is reproducible with and file a new report via a terminal to provide necessary debugging logs: ubuntu-bug linux Please feel free to subscribe me to it. -- 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/549741 Title: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages Status in linux package in Ubuntu: Incomplete Bug description: hi Running Ubuntu Lucid amd64 on a Dell Latitude 131L (AMD chips), updated twice a day at the moment. Linux seems not to recognize the keyboard in my laptop well. Starting early in the boot process (well before X kicks in) I see error messages on the screen. The same messages then swamp the logs. A sample: = [19667.508573] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19667.508580] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.588701] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19668.588712] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.600223] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19668.600230] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.717801] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19669.717811] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.729365] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19669.729373] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.825302] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19670.825313] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.835700] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19670.835707] atkbd.c: Use 'setkeycodes e00d ' to make it known. = This goes on every second until shut down. It's been there for a while now, but I haven't made -or found- a bug report about it yet. I did some googling and it seems related to not-so-standard handling of hotkeys (which you would find on a laptop) by the bios. However, I have not found a solution. It is possible to 'shut up' the messages by assigning e00d to an unused keycode, but that is just hiding the symptom. Also that kills the screen saver / blackout and it breaks my repeating keys, so not an option really. WORKAROUND: - shutdown the pc - Remove both battery and AC - push the 'on' switch several times - Plug the battery and AC back in --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of PLAYBACK Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1529 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xc000 irq 16' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:14f12bfa,14f100c3,0009 HDA:83847690,102801f6,00102201' Controls : 6 Simple ctrls : 4 CheckboxSubmission: 41a9dc4bbc2c91d7f7445d204c57c74b CheckboxSystem: d00f84de8a555815fa1c4660280da308 DistroRelease: Ubuntu 10.04 HibernationDevice: RESUME=UUID=f83c27ce-b7e6-4250-967c-1920bb543ba0 InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' MachineType: Dell Inc. Latitude 131L Package: linux (not installed) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic root=UUID=46062d1f-f00c-4276-9ff1-541279640a93 ro single nomodeset ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 Regression: No RelatedPackageVersions: linux-firmware 1.33 Reproducible: Yes Tags: lucid TestedUpstream: Yes Uname: Linux 2.6.32-17-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 05/30/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.1 dmi.board.name: 0PM607?? dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias:
[Kernel-packages] [Bug 549741] Re: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages
below article confirms the similarity of the hardware of Dell Vostro 1000, Dell Latitude 131L, Dell Inspiron 1501 which exhibit the issue discussed in this bugreport https://mikebeach.org/2011/04/24/kernel-atkbd-c-unknown-key-released-messages-on-linux/ -- 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/549741 Title: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages Status in linux package in Ubuntu: Incomplete Bug description: hi Running Ubuntu Lucid amd64 on a Dell Latitude 131L (AMD chips), updated twice a day at the moment. Linux seems not to recognize the keyboard in my laptop well. Starting early in the boot process (well before X kicks in) I see error messages on the screen. The same messages then swamp the logs. A sample: = [19667.508573] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19667.508580] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.588701] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19668.588712] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.600223] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19668.600230] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.717801] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19669.717811] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.729365] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19669.729373] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.825302] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19670.825313] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.835700] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19670.835707] atkbd.c: Use 'setkeycodes e00d ' to make it known. = This goes on every second until shut down. It's been there for a while now, but I haven't made -or found- a bug report about it yet. I did some googling and it seems related to not-so-standard handling of hotkeys (which you would find on a laptop) by the bios. However, I have not found a solution. It is possible to 'shut up' the messages by assigning e00d to an unused keycode, but that is just hiding the symptom. Also that kills the screen saver / blackout and it breaks my repeating keys, so not an option really. WORKAROUND: - shutdown the pc - Remove both battery and AC - push the 'on' switch several times - Plug the battery and AC back in --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of PLAYBACK Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1529 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xc000 irq 16' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:14f12bfa,14f100c3,0009 HDA:83847690,102801f6,00102201' Controls : 6 Simple ctrls : 4 CheckboxSubmission: 41a9dc4bbc2c91d7f7445d204c57c74b CheckboxSystem: d00f84de8a555815fa1c4660280da308 DistroRelease: Ubuntu 10.04 HibernationDevice: RESUME=UUID=f83c27ce-b7e6-4250-967c-1920bb543ba0 InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' MachineType: Dell Inc. Latitude 131L Package: linux (not installed) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic root=UUID=46062d1f-f00c-4276-9ff1-541279640a93 ro single nomodeset ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 Regression: No RelatedPackageVersions: linux-firmware 1.33 Reproducible: Yes Tags: lucid TestedUpstream: Yes Uname: Linux 2.6.32-17-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 05/30/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.1 dmi.board.name: 0PM607?? dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.4.1:bd05/30/2006:svnDellInc.:pnLatitude131L:pvrNotSpecified:rvnDellInc.:rn0PM607??:rvr:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Latitude 131L dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc.
[Kernel-packages] [Bug 1806437] Re: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)
Me also on a Lenovo X1 6 Gen on Debian 9: dmesg => [2.611547] thinkpad_acpi: ThinkPad ACPI Extras v0.26 [2.611547] thinkpad_acpi: http://ibm-acpi.sf.net/ [2.611548] thinkpad_acpi: ThinkPad BIOS N23ET59W (1.34 ), EC unknown [2.611549] thinkpad_acpi: Lenovo ThinkPad X1 Carbon 6th, model 20KG004JFR [2.612073] thinkpad_acpi: radio switch found; radios are enabled [2.612262] thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver [2.612263] thinkpad_acpi: Disabling thinkpad-acpi brightness events by default... [2.613667] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked [2.614639] thinkpad_acpi: rfkill switch tpacpi_wwan_sw: radio is unblocked [2.617173] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) [2.617398] acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) [2.617460] acpi PNP0C14:04: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) -- 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/1806437 Title: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, dmesg: [ 15.390738] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2769 F pulseaudio /dev/snd/pcmC0D0p: caravena 2769 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 12:49:26 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (0 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806437/+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 1752165] Re: TB16 dock freezes X on hotplug when used with external displays
The problem still persists for me with Kernel 4.18.0-15-generic on Ubuntu 18.10. I'm using a Lenovo Thinkpad T480 with a Nvidia MX150. -- 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/1752165 Title: TB16 dock freezes X on hotplug when used with external displays Status in Dell Sputnik: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Precision 5520 with Quadro GPU. Latest Ubuntu 16.04, kernel Linux REDACTED 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux, latest BIOS 1.7.0 released 12/15/2017. If it can be of any help, I can get this tested on an XPS 9560 (GTX 1050) too. Steps to reproduce: 1. Plug in monitors into DP and miniDP on the dock. In my case, DP-to-DVI cables are used, but I doubt that it matters. 2. Ubuntu 16.04 GNOME + nVidia drivers with PRIME. 3. Select nVidia GPU in PRIME settings, reboot if needed. 4. Either boot with the dock connected or connect it after booting into user session. 5. Set up monitors if necessary. At this point everything should be working fine. 6. Disconnect the dock, give it a moment to adjust to the new window layout etc. 7. Re-connect the dock. Within a few seconds laptop screen should freeze and external monitors should remain blank, as if not connected. 8. Disconnect the dock. Within a few seconds laptop screen should unfreeze. There is a small chance that it won't if you repeat this procedure multiple times. Errors in dmesg indicate that i915 driver is somehow involved: [ 328.966128] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 328.967848] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF B idle bit [ 329.048839] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 329.050547] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit The kernel logs are flooded with these between steps 7 and 8 above. This behaviour does not occur when Intel GPU is selected in PRIME settings or when nouveau is used. However, nouveau performance leaves a lot to be desired, particularly with 3D acceleration in Windows 10 VMs. I have tried nvidia_drm.modeset=1 in boot options, but it doesn't make any difference. Other reports that may be related: https://devtalk.nvidia.com/default/topic/989704/linux/plugging-a -docking-station-w-two-monitors-into-a-quadro-m1000m-laptop-crashes- hangs-the-whole-machine/ - same error messages https://www.reddit.com/r/Dell/comments/5nas3t/tb16_dock_with_5510_ubuntulinux/ddzjlu8/?st=je63h7lw=40bf8189 - "Connecting and disconnecting the TB16 sometimes freeze the laptop." https://www.dell.com/community/Sputnik/TB16-Dock-Linux-Support/m-p/5109128/highlight/true#M7466 - "Hot-plugging the screen does not work." --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gboiko 2491 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=08bba264-8658-442f-995d-6a745925ac6c InstallationDate: Installed on 2017-10-01 (149 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:24a1 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic root=/dev/mapper/ubuntu--gnome--vg-root ro ipv6.disable=1 net.ifnames=0 biosdevname=0 nvidia_drm.modeset=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-36-generic N/A linux-backports-modules-4.13.0-36-generic N/A linux-firmware 1.170 Tags: xenial Uname: Linux 4.13.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/15/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0R6JFH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/15/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:
[Kernel-packages] [Bug 225926] Re: Microphones on Compaq F750US not Working
Bug report did not expire due to assignment No reply to request for information No comments for over 9 years so closing ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => 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/225926 Title: Microphones on Compaq F750US not Working Status in alsa-driver package in Ubuntu: Invalid Status in linux package in Ubuntu: Expired Bug description: I have Ubuntu 8.04 on a Compaq F750US. 'lspci | grep -i audio' reports a Nvidia MCP67 REVa1 device. The Gnome Sound Recorder 2.22.0 does not record via the internal nor external microphones. I can provide any information you need, just ask. I can try things and restore my partition if it doesn't work or screws things up. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu. > Ubuntu 8.04 > 'uname -r' reports: 2.6.24-16-generic > 'lspci | grep -i audio' reports: Nvidia Corporation MCP67 High Definition Audio (rev a1) 2) The version of the package you are using, via 'apt-cache policy packagename' or by checking in Synaptic. > Assuming "Alsa" here, Synaptic Package Mgr reports: * alsa-base 1.0.16-0ubuntu4 * alsa-utils 1.0.15-3ubuntu2 * gstreamer0.10-alsa0.10.18-3 3) What you expected to happen > I was hoping my test sound would be recorded. 4) What happened instead > Nada. No sound played back whatsoever. And, I do have sound playing if I play a movie or sound file. 2008-07-24: Is anyone looking into this? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/225926/+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 549741] Re: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages
Contacted Tom, hope he confirms. As I own similar hardware (AMD-based DELL notebook of the same architecture, Inspiron 1501), still running ubuntu fine (up to 18.10 now) with the above mentioned workaround. Actually similar bug raised by me is closed on redhat side https://bugzilla.redhat.com/show_bug.cgi?id=454131 . As the hardware is quite old (more than 12 years old!) no-one will bother to reproduce or fix it, hence the only way forward is just to close it. Here is my System Information Manufacturer: Dell Inc. Product Name: Inspiron 1501 Version: Not Specified Serial Number: BZX583J UUID: 44454C4C-5A00-1058-8035-C2C04F38334A Wake-up Type: Power Switch SKU Number: Not Specified Family: Not Specified -- 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/549741 Title: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages Status in linux package in Ubuntu: Incomplete Bug description: hi Running Ubuntu Lucid amd64 on a Dell Latitude 131L (AMD chips), updated twice a day at the moment. Linux seems not to recognize the keyboard in my laptop well. Starting early in the boot process (well before X kicks in) I see error messages on the screen. The same messages then swamp the logs. A sample: = [19667.508573] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19667.508580] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.588701] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19668.588712] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.600223] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19668.600230] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.717801] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19669.717811] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.729365] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19669.729373] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.825302] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19670.825313] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.835700] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19670.835707] atkbd.c: Use 'setkeycodes e00d ' to make it known. = This goes on every second until shut down. It's been there for a while now, but I haven't made -or found- a bug report about it yet. I did some googling and it seems related to not-so-standard handling of hotkeys (which you would find on a laptop) by the bios. However, I have not found a solution. It is possible to 'shut up' the messages by assigning e00d to an unused keycode, but that is just hiding the symptom. Also that kills the screen saver / blackout and it breaks my repeating keys, so not an option really. WORKAROUND: - shutdown the pc - Remove both battery and AC - push the 'on' switch several times - Plug the battery and AC back in --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of PLAYBACK Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1529 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xc000 irq 16' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:14f12bfa,14f100c3,0009 HDA:83847690,102801f6,00102201' Controls : 6 Simple ctrls : 4 CheckboxSubmission: 41a9dc4bbc2c91d7f7445d204c57c74b CheckboxSystem: d00f84de8a555815fa1c4660280da308 DistroRelease: Ubuntu 10.04 HibernationDevice: RESUME=UUID=f83c27ce-b7e6-4250-967c-1920bb543ba0 InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' MachineType: Dell Inc. Latitude 131L Package: linux (not installed) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic root=UUID=46062d1f-f00c-4276-9ff1-541279640a93 ro single nomodeset ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 Regression: No RelatedPackageVersions: linux-firmware 1.33 Reproducible: Yes Tags: lucid TestedUpstream: Yes Uname: Linux 2.6.32-17-generic x86_64 UserGroups: adm admin
[Kernel-packages] [Bug 549741] Re: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages
Eugene Savelov, having a WORKAROUND on different hardware, and an unconfirmed assumption of root cause, doesn't cause this report to be Invalid. For more on Status, please see: https://wiki.ubuntu.com/Bugs/Status Despite this, given Tom Louwrier is the original reporter, if he would like to close this, its up to him. ** Changed in: linux (Ubuntu) Importance: Medium => Low ** Changed in: linux (Ubuntu) Status: Invalid => 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/549741 Title: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages Status in linux package in Ubuntu: Incomplete Bug description: hi Running Ubuntu Lucid amd64 on a Dell Latitude 131L (AMD chips), updated twice a day at the moment. Linux seems not to recognize the keyboard in my laptop well. Starting early in the boot process (well before X kicks in) I see error messages on the screen. The same messages then swamp the logs. A sample: = [19667.508573] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19667.508580] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.588701] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19668.588712] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.600223] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19668.600230] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.717801] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19669.717811] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.729365] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19669.729373] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.825302] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19670.825313] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.835700] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19670.835707] atkbd.c: Use 'setkeycodes e00d ' to make it known. = This goes on every second until shut down. It's been there for a while now, but I haven't made -or found- a bug report about it yet. I did some googling and it seems related to not-so-standard handling of hotkeys (which you would find on a laptop) by the bios. However, I have not found a solution. It is possible to 'shut up' the messages by assigning e00d to an unused keycode, but that is just hiding the symptom. Also that kills the screen saver / blackout and it breaks my repeating keys, so not an option really. WORKAROUND: - shutdown the pc - Remove both battery and AC - push the 'on' switch several times - Plug the battery and AC back in --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of PLAYBACK Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1529 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xc000 irq 16' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:14f12bfa,14f100c3,0009 HDA:83847690,102801f6,00102201' Controls : 6 Simple ctrls : 4 CheckboxSubmission: 41a9dc4bbc2c91d7f7445d204c57c74b CheckboxSystem: d00f84de8a555815fa1c4660280da308 DistroRelease: Ubuntu 10.04 HibernationDevice: RESUME=UUID=f83c27ce-b7e6-4250-967c-1920bb543ba0 InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' MachineType: Dell Inc. Latitude 131L Package: linux (not installed) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic root=UUID=46062d1f-f00c-4276-9ff1-541279640a93 ro single nomodeset ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 Regression: No RelatedPackageVersions: linux-firmware 1.33 Reproducible: Yes Tags: lucid TestedUpstream: Yes Uname: Linux 2.6.32-17-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 05/30/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.1 dmi.board.name: 0PM607?? dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias:
[Kernel-packages] [Bug 549741] Re: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages
** Description changed: hi Running Ubuntu Lucid amd64 on a Dell Latitude 131L (AMD chips), updated twice a day at the moment. Linux seems not to recognize the keyboard in my laptop well. Starting early in the boot process (well before X kicks in) I see error messages on the screen. The same messages then swamp the logs. A sample: = [19667.508573] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19667.508580] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.588701] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19668.588712] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19668.600223] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19668.600230] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.717801] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19669.717811] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19669.729365] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19669.729373] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.825302] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [19670.825313] atkbd.c: Use 'setkeycodes e00d ' to make it known. [19670.835700] atkbd.c: Unknown key released (translated set 2, code 0x8d on isa0060/serio0). [19670.835707] atkbd.c: Use 'setkeycodes e00d ' to make it known. = This goes on every second until shut down. It's been there for a while now, but I haven't made -or found- a bug report about it yet. I did some googling and it seems related to not-so-standard handling of hotkeys (which you would find on a laptop) by the bios. However, I have not found a solution. It is possible to 'shut up' the messages by assigning e00d to an unused keycode, but that is just hiding the symptom. Also that kills the screen saver / blackout and it breaks my repeating keys, so not an option really. - If there is anything I should do to provide more information, please let - me know. + WORKAROUND: - shutdown the pc + - Remove both battery and AC + - push the 'on' switch several times + - Plug the battery and AC back in - cheers - Tom - --- + --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: - List of PLAYBACK Hardware Devices - card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] -Subdevices: 1/1 -Subdevice #0: subdevice #0 + List of PLAYBACK Hardware Devices + card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] + Subdevices: 1/1 + Subdevice #0: subdevice #0 Architecture: amd64 ArecordDevices: - List of CAPTURE Hardware Devices - card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] -Subdevices: 1/1 -Subdevice #0: subdevice #0 + List of CAPTURE Hardware Devices + card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] + Subdevices: 1/1 + Subdevice #0: subdevice #0 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: thomas 1529 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: thomas 1529 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: - Card hw:0 'SB'/'HDA ATI SB at 0xc000 irq 16' -Mixer name : 'SigmaTel STAC9200' -Components : 'HDA:14f12bfa,14f100c3,0009 HDA:83847690,102801f6,00102201' -Controls : 6 -Simple ctrls : 4 + Card hw:0 'SB'/'HDA ATI SB at 0xc000 irq 16' + Mixer name : 'SigmaTel STAC9200' + Components : 'HDA:14f12bfa,14f100c3,0009 HDA:83847690,102801f6,00102201' + Controls : 6 + Simple ctrls : 4 CheckboxSubmission: 41a9dc4bbc2c91d7f7445d204c57c74b CheckboxSystem: d00f84de8a555815fa1c4660280da308 DistroRelease: Ubuntu 10.04 HibernationDevice: RESUME=UUID=f83c27ce-b7e6-4250-967c-1920bb543ba0 InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' MachineType: Dell Inc. Latitude 131L Package: linux (not installed) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic root=UUID=46062d1f-f00c-4276-9ff1-541279640a93 ro single nomodeset ProcEnviron: - LANGUAGE=en_GB:en - LANG=en_GB.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_GB:en + LANG=en_GB.UTF-8 + SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 Regression: No RelatedPackageVersions: linux-firmware 1.33 Reproducible: Yes Tags: lucid TestedUpstream: Yes Uname: Linux 2.6.32-17-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 05/30/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.1 dmi.board.name: 0PM607?? dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version:
[Kernel-packages] [Bug 1813873] Re: Userspace break as a result of missing patch backport
The kernel in -proposed solves the problem, I've tested it ! I don't know how to add the flag "verification-done-bionic" to this bug though. -- 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/1813873 Title: Userspace break as a result of missing patch backport Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Released Bug description: Hi, The most recent set of Ubuntu kernels applied a variety of tty patches including: https://github.com/torvalds/linux/commit/c96cf923a98d1b094df9f0cf97a83e118817e31b But have not applied the more recent https://github.com/torvalds/linux/commit/d3736d82e8169768218ee0ef68718875918091a0 patch. This second patch is required to prevent a rather serious regression where userspace applications reading from stdin can receive EAGAIN when they should not. I will try to link correspondence from the mailing list archives once they are available, but for now if you have access to the linux- console mailing list you can find discussion under the thread "Userspace break? read from STDIN returns EAGAIN if tty is "touched"". I would appreciate it if this could be examined soon as it is a regression on userspace. Thanks Michael Good: 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 Bad: 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813873/+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 549741] Re: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/549741
Title:
[Dell Latitude 131L] keyboard not recognized properly; logs fill up
with messages
Status in linux package in Ubuntu:
Invalid
Bug description:
hi
Running Ubuntu Lucid amd64 on a Dell Latitude 131L (AMD chips),
updated twice a day at the moment.
Linux seems not to recognize the keyboard in my laptop well. Starting early
in the boot process (well before X kicks in) I see error messages on the
screen. The same messages then swamp the logs. A sample:
=
[19667.508573] atkbd.c: Unknown key released (translated set 2, code 0x8d on
isa0060/serio0).
[19667.508580] atkbd.c: Use 'setkeycodes e00d ' to make it known.
[19668.588701] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on
isa0060/serio0).
[19668.588712] atkbd.c: Use 'setkeycodes e00d ' to make it known.
[19668.600223] atkbd.c: Unknown key released (translated set 2, code 0x8d on
isa0060/serio0).
[19668.600230] atkbd.c: Use 'setkeycodes e00d ' to make it known.
[19669.717801] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on
isa0060/serio0).
[19669.717811] atkbd.c: Use 'setkeycodes e00d ' to make it known.
[19669.729365] atkbd.c: Unknown key released (translated set 2, code 0x8d on
isa0060/serio0).
[19669.729373] atkbd.c: Use 'setkeycodes e00d ' to make it known.
[19670.825302] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on
isa0060/serio0).
[19670.825313] atkbd.c: Use 'setkeycodes e00d ' to make it known.
[19670.835700] atkbd.c: Unknown key released (translated set 2, code 0x8d on
isa0060/serio0).
[19670.835707] atkbd.c: Use 'setkeycodes e00d ' to make it known.
=
This goes on every second until shut down.
It's been there for a while now, but I haven't made -or found- a bug report
about it yet. I did some googling and it seems related to not-so-standard
handling of hotkeys (which you would find on a laptop) by the bios. However, I
have not found a solution.
It is possible to 'shut up' the messages by assigning e00d to an unused
keycode, but that is just hiding the symptom. Also that kills the screen saver
/ blackout and it breaks my repeating keys, so not an option really.
If there is anything I should do to provide more information, please
let me know.
cheers
Tom
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: thomas 1529 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'SB'/'HDA ATI SB at 0xc000 irq 16'
Mixer name : 'SigmaTel STAC9200'
Components : 'HDA:14f12bfa,14f100c3,0009
HDA:83847690,102801f6,00102201'
Controls : 6
Simple ctrls : 4
CheckboxSubmission: 41a9dc4bbc2c91d7f7445d204c57c74b
CheckboxSystem: d00f84de8a555815fa1c4660280da308
DistroRelease: Ubuntu 10.04
HibernationDevice: RESUME=UUID=f83c27ce-b7e6-4250-967c-1920bb543ba0
InstallationMedia: Error: [Errno 13] Permission denied:
'/var/log/installer/media-info'
MachineType: Dell Inc. Latitude 131L
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic
root=UUID=46062d1f-f00c-4276-9ff1-541279640a93 ro single nomodeset
ProcEnviron:
LANGUAGE=en_GB:en
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
Regression: No
RelatedPackageVersions: linux-firmware 1.33
Reproducible: Yes
Tags: lucid
TestedUpstream: Yes
Uname: Linux 2.6.32-17-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 05/30/2006
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.4.1
dmi.board.name: 0PM607??
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnDellInc.:bvr2.4.1:bd05/30/2006:svnDellInc.:pnLatitude131L:pvrNotSpecified:rvnDellInc.:rn0PM607??:rvr:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Latitude 131L
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog]
[Kernel-packages] [Bug 549741] Re: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages
For me, this problem is fixed by turning off the power, removing the
battery and plugging in everything back. After powering on notebook the
error is gone. I have AMD-based DELL Insipron 1501, assuming this is
some sort of firmware bug of keyboard controller, and needs to be done
once a year or so.
--
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/549741
Title:
[Dell Latitude 131L] keyboard not recognized properly; logs fill up
with messages
Status in linux package in Ubuntu:
Incomplete
Bug description:
hi
Running Ubuntu Lucid amd64 on a Dell Latitude 131L (AMD chips),
updated twice a day at the moment.
Linux seems not to recognize the keyboard in my laptop well. Starting early
in the boot process (well before X kicks in) I see error messages on the
screen. The same messages then swamp the logs. A sample:
=
[19667.508573] atkbd.c: Unknown key released (translated set 2, code 0x8d on
isa0060/serio0).
[19667.508580] atkbd.c: Use 'setkeycodes e00d ' to make it known.
[19668.588701] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on
isa0060/serio0).
[19668.588712] atkbd.c: Use 'setkeycodes e00d ' to make it known.
[19668.600223] atkbd.c: Unknown key released (translated set 2, code 0x8d on
isa0060/serio0).
[19668.600230] atkbd.c: Use 'setkeycodes e00d ' to make it known.
[19669.717801] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on
isa0060/serio0).
[19669.717811] atkbd.c: Use 'setkeycodes e00d ' to make it known.
[19669.729365] atkbd.c: Unknown key released (translated set 2, code 0x8d on
isa0060/serio0).
[19669.729373] atkbd.c: Use 'setkeycodes e00d ' to make it known.
[19670.825302] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on
isa0060/serio0).
[19670.825313] atkbd.c: Use 'setkeycodes e00d ' to make it known.
[19670.835700] atkbd.c: Unknown key released (translated set 2, code 0x8d on
isa0060/serio0).
[19670.835707] atkbd.c: Use 'setkeycodes e00d ' to make it known.
=
This goes on every second until shut down.
It's been there for a while now, but I haven't made -or found- a bug report
about it yet. I did some googling and it seems related to not-so-standard
handling of hotkeys (which you would find on a laptop) by the bios. However, I
have not found a solution.
It is possible to 'shut up' the messages by assigning e00d to an unused
keycode, but that is just hiding the symptom. Also that kills the screen saver
/ blackout and it breaks my repeating keys, so not an option really.
If there is anything I should do to provide more information, please
let me know.
cheers
Tom
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: thomas 1529 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'SB'/'HDA ATI SB at 0xc000 irq 16'
Mixer name : 'SigmaTel STAC9200'
Components : 'HDA:14f12bfa,14f100c3,0009
HDA:83847690,102801f6,00102201'
Controls : 6
Simple ctrls : 4
CheckboxSubmission: 41a9dc4bbc2c91d7f7445d204c57c74b
CheckboxSystem: d00f84de8a555815fa1c4660280da308
DistroRelease: Ubuntu 10.04
HibernationDevice: RESUME=UUID=f83c27ce-b7e6-4250-967c-1920bb543ba0
InstallationMedia: Error: [Errno 13] Permission denied:
'/var/log/installer/media-info'
MachineType: Dell Inc. Latitude 131L
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic
root=UUID=46062d1f-f00c-4276-9ff1-541279640a93 ro single nomodeset
ProcEnviron:
LANGUAGE=en_GB:en
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
Regression: No
RelatedPackageVersions: linux-firmware 1.33
Reproducible: Yes
Tags: lucid
TestedUpstream: Yes
Uname: Linux 2.6.32-17-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 05/30/2006
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.4.1
dmi.board.name: 0PM607??
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnDellInc.:bvr2.4.1:bd05/30/2006:svnDellInc.:pnLatitude131L:pvrNotSpecified:rvnDellInc.:rn0PM607??:rvr:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Latitude 131L
dmi.product.version: Not Specified
dmi.sys.vendor: Dell
[Kernel-packages] [Bug 1816081] Re: linux-azure: 4.18.0-1011.11 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 phase: Testing phase-changed: Saturday, 16. February 2019 11:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff - verification-testing: Pending -- Ready -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1816081 Title: linux-azure: 4.18.0-1011.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 phase: Testing phase-changed: Saturday, 16. February 2019 11:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1816081/+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 1816080] Re: linux-azure: 4.18.0-1011.11~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: New => Fix Released ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1816081 phase: Promote to Proposed phase-changed: Saturday, 16. February 2019 08:17 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel stakeholder-signoff: Pending -- waiting for signoff - verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1816080 Title: linux-azure: 4.18.0-1011.11~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1816081 phase: Promote to Proposed phase-changed: Saturday, 16. February 2019 08:17 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel stakeholder-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1816080/+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 1814734] Re: linux-gcp: 4.15.0-1028.29 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1814726 phase: Promote to Proposed phase-changed: Friday, 15. February 2019 10:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1028 regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1814734 Title: linux-gcp: 4.15.0-1028.29 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1814726 phase: Promote to Proposed phase-changed: Friday, 15. February 2019 10:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1028 regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814734/+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 1778011] Re: SRU: PRIME Power Saving mode draws too much power
I observed the same behaviour as Adrian S.. Selecting Intel keeps the Nvidia card powered and the fan spinning. Installing and using bbswitch manually works. I can't make it working powering off the card at boot time :( Therefore I have to do it manually every time I boot my notebook. MX150, Ubuntu 18.04.2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in HWE Next: New Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in sddm package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-prime source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Released Status in sddm source package in Bionic: Confirmed Status in ubuntu-drivers-common source package in Bionic: Fix Released Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic- proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390 /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia- ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+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 1816080] Re: linux-azure: 4.18.0-1011.11~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1816081 phase: Promote to Proposed phase-changed: Saturday, 16. February 2019 08:17 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + snap-release-to-beta: Pending -- snap not in 18/beta channel + snap-release-to-edge: Pending -- snap not in 18/edge channel + stakeholder-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1816080 Title: linux-azure: 4.18.0-1011.11~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1816081 phase: Promote to Proposed phase-changed: Saturday, 16. February 2019 08:17 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1816080/+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 1816081] Re: linux-azure: 4.18.0-1011.11 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Fix Released ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 - phase: Promote to Proposed - phase-changed: Saturday, 16. February 2019 08:09 UTC + phase: Testing + phase-changed: Saturday, 16. February 2019 11:38 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + stakeholder-signoff: Pending -- waiting for signoff + verification-testing: Pending -- Ready -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1816081 Title: linux-azure: 4.18.0-1011.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 phase: Testing phase-changed: Saturday, 16. February 2019 11:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Pending -- Ready To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1816081/+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 1814734] Re: linux-gcp: 4.15.0-1028.29 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1814726 phase: Promote to Proposed phase-changed: Friday, 15. February 2019 10:41 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages copies requested + automated-testing: Ongoing -- testing in progress + promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1028 + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + snap-release-to-beta: Pending -- snap not in 18/beta channel + snap-release-to-edge: Pending -- snap not in 18/edge channel + verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1814734 Title: linux-gcp: 4.15.0-1028.29 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1814726 phase: Promote to Proposed phase-changed: Friday, 15. February 2019 10:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1028 regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814734/+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 1816081] Re: linux-azure: 4.18.0-1011.11 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 phase: Promote to Proposed phase-changed: Saturday, 16. February 2019 08:09 UTC reason: - promote-to-proposed: Ongoing -- packages copies requested + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1816081 Title: linux-azure: 4.18.0-1011.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 phase: Promote to Proposed phase-changed: Saturday, 16. February 2019 08:09 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1816081/+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 1816080] Re: linux-azure: 4.18.0-1011.11~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1816081 phase: Promote to Proposed phase-changed: Saturday, 16. February 2019 08:17 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1816080 Title: linux-azure: 4.18.0-1011.11~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1816081 phase: Promote to Proposed phase-changed: Saturday, 16. February 2019 08:17 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1816080/+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 1816081] Re: linux-azure: 4.18.0-1011.11 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 phase: Promote to Proposed phase-changed: Saturday, 16. February 2019 08:09 UTC reason: - promote-to-proposed: Ongoing -- packages copied but not yet published to -proposed + promote-to-proposed: Ongoing -- packages copies requested -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1816081 Title: linux-azure: 4.18.0-1011.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 phase: Promote to Proposed phase-changed: Saturday, 16. February 2019 08:09 UTC reason: promote-to-proposed: Ongoing -- packages copies requested To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1816081/+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 1816081] Re: linux-azure: 4.18.0-1011.11 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 phase: Promote to Proposed phase-changed: Saturday, 16. February 2019 08:09 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Ongoing -- packages copied but not yet published to -proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1816081 Title: linux-azure: 4.18.0-1011.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 phase: Promote to Proposed phase-changed: Saturday, 16. February 2019 08:09 UTC reason: promote-to-proposed: Ongoing -- packages copied but not yet published to -proposed To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1816081/+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 1816080] Re: linux-azure: 4.18.0-1011.11~18.04.1 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1816081 phase: Promote to Proposed phase-changed: Saturday, 16. February 2019 08:17 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1816080 Title: linux-azure: 4.18.0-1011.11~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1816081 phase: Promote to Proposed phase-changed: Saturday, 16. February 2019 08:17 UTC reason: promote-to-proposed: Ongoing -- review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1816080/+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 1816080] Re: linux-azure: 4.18.0-1011.11~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1816080 Title: linux-azure: 4.18.0-1011.11~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1816081 phase: Promote to Proposed phase-changed: Saturday, 16. February 2019 08:17 UTC reason: promote-to-proposed: Ongoing -- review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1816080/+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 1816222] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1816222 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** 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/1816222 Title: After updating to 18.04.2 and kernel 4.18.0-15.16 boot stalls Status in linux package in Ubuntu: Incomplete Bug description: I upgraded my 18.04.1 to 18.04.2 and then opted for the HWE stack. My laptop is unable to go past the loading screen with 4.18.0-15.16 but boots normally with the 4.15.x drivers. In safe mode I can boot with 4.18 but just only the main monitor is detected. I used UKUU to trie 4.20.x and other kernels but none of them booted. The laptop is Dell Inspiron 7567 with Intel HD630 and NVIDIA 1050Ti with the default drivers (NVIDIA proprietary driver never worked on this laptop). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816222/+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 1816222] Re: After updating to 18.04.2 and kernel 4.18.0-15.16 boot stalls
The b -- 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/1816222 Title: After updating to 18.04.2 and kernel 4.18.0-15.16 boot stalls Status in linux package in Ubuntu: Incomplete Bug description: I upgraded my 18.04.1 to 18.04.2 and then opted for the HWE stack. My laptop is unable to go past the loading screen with 4.18.0-15.16 but boots normally with the 4.15.x drivers. In safe mode I can boot with 4.18 but just only the main monitor is detected. I used UKUU to trie 4.20.x and other kernels but none of them booted. The laptop is Dell Inspiron 7567 with Intel HD630 and NVIDIA 1050Ti with the default drivers (NVIDIA proprietary driver never worked on this laptop). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816222/+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 1816222] [NEW] After updating to 18.04.2 and kernel 4.18.0-15.16 boot stalls
Public bug reported: I upgraded my 18.04.1 to 18.04.2 and then opted for the HWE stack. My laptop is unable to go past the loading screen with 4.18.0-15.16 but boots normally with the 4.15.x drivers. In safe mode I can boot with 4.18 but just only the main monitor is detected. I used UKUU to trie 4.20.x and other kernels but none of them booted. The laptop is Dell Inspiron 7567 with Intel HD630 and NVIDIA 1050Ti with the default drivers (NVIDIA proprietary driver never worked on this laptop). ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bionic boot -- 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/1816222 Title: After updating to 18.04.2 and kernel 4.18.0-15.16 boot stalls Status in linux package in Ubuntu: Incomplete Bug description: I upgraded my 18.04.1 to 18.04.2 and then opted for the HWE stack. My laptop is unable to go past the loading screen with 4.18.0-15.16 but boots normally with the 4.15.x drivers. In safe mode I can boot with 4.18 but just only the main monitor is detected. I used UKUU to trie 4.20.x and other kernels but none of them booted. The laptop is Dell Inspiron 7567 with Intel HD630 and NVIDIA 1050Ti with the default drivers (NVIDIA proprietary driver never worked on this laptop). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816222/+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 1814555] Re: Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)
Inspiron 7567 has Intel HD 630 and NVIDIA 1050Ti. NVIDIA propr. driver never worked for me. I used UKUU and tried a few kernels past 4.18.x and none of them worked. I had to uninstall them and I use 4.15, which lets the laptop to boot normally. Although I have noticed a few graphical glitches after installing 18.04.2 HWE. -- 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/1814555 Title: Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot) Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: Fix Released Bug description: Today my Ubuntu (18.10) did an auto-upgrade to 4.18.0-14-generic, requested a reboot, and was unable to boot. After the "Starting Load/Save RF Kill Switch Status..." line it is waiting forever. (Or/and doing something behind the scenes. After a while, even the HDD indicator led go out.) This is a permanent error, so kernel 4.18.0-14 does NOT boot. I was able to boot with kernel 4.18.0-13. (By pressing Shift when grub starts.) My configuration is "nothing fancy", possibly-except the locale (ISO-8859-2, hu and en), Xcfe4, gdm3, gnome-screensaver. I have already upgraded to the latest packages. (sudo apt-get dist-upgrade) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814555/+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 1799305] Re: No desktop after reboot when using nvidia graphics on 18.10
NVIDIA drivers don't work for me on 18.04 at all. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1799305 Title: No desktop after reboot when using nvidia graphics on 18.10 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: I upgraded from 18.04 to 18.10 and now the desktop does not start after a reboot. The console output ends with "Starting GNOME Display Manager". I cannot switch VTs, my keyboard and mouse are unresponsive though RESUIB sequence works to reboot. If I remote login using ssh, I can run "systemctrl restart gdm3" and I get a working login screen and can continue as expected. If I remove my nvidia drivers the desktop starts as expected after reboot. Examining /var/log/syslog appears to show the nvidia driver failing to load correctly; see below. In the failed state "systemctl status gdm3" shows: ● gdm.service - GNOME Display Manager Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor preset: enabled) Active: active (running) since Mon 2018-10-22 22:06:38 BST; 16min ago Process: 1877 ExecStartPre=/usr/lib/gdm3/gdm-wait-for-drm (code=exited, status=0/SUCCESS) Process: 1723 ExecStartPre=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS) Main PID: 1880 (gdm3) Tasks: 3 (limit: 4915) Memory: 5.7M CGroup: /system.slice/gdm.service └─1880 /usr/sbin/gdm3 Oct 22 22:06:35 hagrid systemd[1]: Starting GNOME Display Manager... Oct 22 22:06:38 hagrid systemd[1]: Started GNOME Display Manager. Oct 22 22:06:44 hagrid gdm-launch-environment][2108]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0) Oct 22 22:06:54 hagrid gdm3[1880]: Child process -2634 was already dead. Oct 22 22:06:54 hagrid gdm3[1880]: Child process -2634 was already dead. root@hagrid:/var/log# grep 2634 syslog Oct 22 22:06:54 hagrid gdm3: Child process -2634 was already dead. Oct 22 22:06:54 hagrid gdm3: Child process -2634 was already dead. . . . This is a section from syslog: Oct 22 22:06:53 hagrid systemd[1]: Starting NVIDIA Persistence Daemon... Oct 22 22:06:53 hagrid nvidia-persistenced: Verbose syslog connection opened Oct 22 22:06:53 hagrid systemd[1]: Started NVIDIA Persistence Daemon. Oct 22 22:06:54 hagrid nvidia-persistenced: Now running with user ID 123 and group ID 129 Oct 22 22:06:54 hagrid [2750]: meta_kms_resources_init failed: Calling drmModeGetResources() failed, assuming we have no outputs Oct 22 22:06:54 hagrid gnome-session[2664]: gnome-session-binary[2664]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Oct 22 22:06:54 hagrid nvidia-persistenced: Started (2865) Oct 22 22:06:54 hagrid [2750]: Failed to create backend: No GPUs with outputs found Oct 22 22:06:54 hagrid nvidia-persistenced: device :01:00.0 - registered Oct 22 22:06:54 hagrid gnome-session-binary[2664]: Unrecoverable failure in required component org.gnome.Shell.desktop Oct 22 22:06:54 hagrid nvidia-persistenced: Local RPC service initialized Oct 22 22:06:54 hagrid systemd[1]: Stopping NVIDIA Persistence Daemon... Oct 22 22:06:54 hagrid kernel: [ 86.847749] virbr0: port 1(virbr0-nic) entered blocking state Oct 22 22:06:54 hagrid kernel: [ 86.847753] virbr0: port 1(virbr0-nic) entered listening state Oct 22 22:06:54 hagrid gnome-session-binary[2664]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Oct 22 22:06:54 hagrid systemd[1]: Stopped NVIDIA Persistence Daemon. Oct 22 22:06:54 hagrid nvidia-persistenced: Received signal 15 Oct 22 22:06:54 hagrid nvidia-persistenced: Socket closed. Oct 22 22:06:54 hagrid nvidia-persistenced: PID file unlocked. Oct 22 22:06:54 hagrid systemd[1]: user-runtime-dir@121.service: Unit not needed anymore. Stopping. Oct 22 22:06:54 hagrid nvidia-persistenced: PID file closed. Oct 22 22:06:54 hagrid systemd[1]: Stopping User Manager for UID 121... Oct 22 22:06:54 hagrid nvidia-persistenced: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced Oct 22 22:06:54 hagrid systemd[2507]: Stopping D-Bus User Message Bus... Oct 22 22:06:54 hagrid nvidia-persistenced: Shutdown (2865) Oct 22 22:06:54 hagrid systemd[2507]: Stopped target Default. Oct 22 22:06:54 hagrid systemd[2507]: Stopped D-Bus User Message Bus. Oct 22 22:06:54 hagrid gdm3: Child process -2634 was already dead. Description: Ubuntu 18.10 Release: 18.10 nvidia-driver-390: Installed: 390.87-0ubuntu1 Candidate: 390.87-0ubuntu1 Version table: *** 390.87-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu cosmic/restricted amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nvidia-driver-390 390.87-0ubuntu1
[Kernel-packages] [Bug 1799305] Re: No desktop after reboot when using nvidia graphics on 18.10
I tried a few versions a few times but I can only use nouveau driver -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1799305 Title: No desktop after reboot when using nvidia graphics on 18.10 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: I upgraded from 18.04 to 18.10 and now the desktop does not start after a reboot. The console output ends with "Starting GNOME Display Manager". I cannot switch VTs, my keyboard and mouse are unresponsive though RESUIB sequence works to reboot. If I remote login using ssh, I can run "systemctrl restart gdm3" and I get a working login screen and can continue as expected. If I remove my nvidia drivers the desktop starts as expected after reboot. Examining /var/log/syslog appears to show the nvidia driver failing to load correctly; see below. In the failed state "systemctl status gdm3" shows: ● gdm.service - GNOME Display Manager Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor preset: enabled) Active: active (running) since Mon 2018-10-22 22:06:38 BST; 16min ago Process: 1877 ExecStartPre=/usr/lib/gdm3/gdm-wait-for-drm (code=exited, status=0/SUCCESS) Process: 1723 ExecStartPre=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS) Main PID: 1880 (gdm3) Tasks: 3 (limit: 4915) Memory: 5.7M CGroup: /system.slice/gdm.service └─1880 /usr/sbin/gdm3 Oct 22 22:06:35 hagrid systemd[1]: Starting GNOME Display Manager... Oct 22 22:06:38 hagrid systemd[1]: Started GNOME Display Manager. Oct 22 22:06:44 hagrid gdm-launch-environment][2108]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0) Oct 22 22:06:54 hagrid gdm3[1880]: Child process -2634 was already dead. Oct 22 22:06:54 hagrid gdm3[1880]: Child process -2634 was already dead. root@hagrid:/var/log# grep 2634 syslog Oct 22 22:06:54 hagrid gdm3: Child process -2634 was already dead. Oct 22 22:06:54 hagrid gdm3: Child process -2634 was already dead. . . . This is a section from syslog: Oct 22 22:06:53 hagrid systemd[1]: Starting NVIDIA Persistence Daemon... Oct 22 22:06:53 hagrid nvidia-persistenced: Verbose syslog connection opened Oct 22 22:06:53 hagrid systemd[1]: Started NVIDIA Persistence Daemon. Oct 22 22:06:54 hagrid nvidia-persistenced: Now running with user ID 123 and group ID 129 Oct 22 22:06:54 hagrid [2750]: meta_kms_resources_init failed: Calling drmModeGetResources() failed, assuming we have no outputs Oct 22 22:06:54 hagrid gnome-session[2664]: gnome-session-binary[2664]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Oct 22 22:06:54 hagrid nvidia-persistenced: Started (2865) Oct 22 22:06:54 hagrid [2750]: Failed to create backend: No GPUs with outputs found Oct 22 22:06:54 hagrid nvidia-persistenced: device :01:00.0 - registered Oct 22 22:06:54 hagrid gnome-session-binary[2664]: Unrecoverable failure in required component org.gnome.Shell.desktop Oct 22 22:06:54 hagrid nvidia-persistenced: Local RPC service initialized Oct 22 22:06:54 hagrid systemd[1]: Stopping NVIDIA Persistence Daemon... Oct 22 22:06:54 hagrid kernel: [ 86.847749] virbr0: port 1(virbr0-nic) entered blocking state Oct 22 22:06:54 hagrid kernel: [ 86.847753] virbr0: port 1(virbr0-nic) entered listening state Oct 22 22:06:54 hagrid gnome-session-binary[2664]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Oct 22 22:06:54 hagrid systemd[1]: Stopped NVIDIA Persistence Daemon. Oct 22 22:06:54 hagrid nvidia-persistenced: Received signal 15 Oct 22 22:06:54 hagrid nvidia-persistenced: Socket closed. Oct 22 22:06:54 hagrid nvidia-persistenced: PID file unlocked. Oct 22 22:06:54 hagrid systemd[1]: user-runtime-dir@121.service: Unit not needed anymore. Stopping. Oct 22 22:06:54 hagrid nvidia-persistenced: PID file closed. Oct 22 22:06:54 hagrid systemd[1]: Stopping User Manager for UID 121... Oct 22 22:06:54 hagrid nvidia-persistenced: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced Oct 22 22:06:54 hagrid systemd[2507]: Stopping D-Bus User Message Bus... Oct 22 22:06:54 hagrid nvidia-persistenced: Shutdown (2865) Oct 22 22:06:54 hagrid systemd[2507]: Stopped target Default. Oct 22 22:06:54 hagrid systemd[2507]: Stopped D-Bus User Message Bus. Oct 22 22:06:54 hagrid gdm3: Child process -2634 was already dead. Description: Ubuntu 18.10 Release: 18.10 nvidia-driver-390: Installed: 390.87-0ubuntu1 Candidate: 390.87-0ubuntu1 Version table: *** 390.87-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu cosmic/restricted amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nvidia-driver-390
[Kernel-packages] [Bug 1816081] Re: linux-azure: 4.18.0-1011.11 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 phase: Promote to Proposed phase-changed: Saturday, 16. February 2019 08:09 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1816081 Title: linux-azure: 4.18.0-1011.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 phase: Promote to Proposed phase-changed: Saturday, 16. February 2019 08:09 UTC reason: promote-to-proposed: Ongoing -- review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1816081/+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 1816080] Re: linux-azure: 4.18.0-1011.11~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1816081 - phase: Holding before Promote to Proposed - phase-changed: Friday, 15. February 2019 19:33 UTC + phase: Promote to Proposed + phase-changed: Saturday, 16. February 2019 08:17 UTC reason: - promote-to-proposed: Holding -- master bug not ready for proposed + promote-to-proposed: Pending -- ready for review -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1816080 Title: linux-azure: 4.18.0-1011.11~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1816081 phase: Promote to Proposed phase-changed: Saturday, 16. February 2019 08:17 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1816080/+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 1816081] Re: linux-azure: 4.18.0-1011.11 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1816081 Title: linux-azure: 4.18.0-1011.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 phase: Promote to Proposed phase-changed: Saturday, 16. February 2019 08:09 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1816081/+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 1816081] Re: linux-azure: 4.18.0-1011.11 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-cosmic ** Tags added: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 - phase: Holding before Promote to Proposed - phase-changed: Friday, 15. February 2019 17:05 UTC + phase: Promote to Proposed + phase-changed: Saturday, 16. February 2019 08:09 UTC reason: - promote-to-proposed: Holding -- another kernel is currently pending in proposed + promote-to-proposed: Pending -- ready for review -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1816081 Title: linux-azure: 4.18.0-1011.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 phase: Promote to Proposed phase-changed: Saturday, 16. February 2019 08:09 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1816081/+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 1816081] Re: linux-azure: 4.18.0-1011.11 -proposed tracker
** Tags added: kernel-unblock-ppa -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1816081 Title: linux-azure: 4.18.0-1011.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 phase: Promote to Proposed phase-changed: Saturday, 16. February 2019 08:09 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1816081/+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
