[Kernel-packages] [Bug 2020917] Re: ethtool -m produces unreadable output for devices managed by the Intel ice driver
As suggested, this is indeed a bug in the ice kernel driver and not ethtool. Fixed by: commit 84cba1840e68430325ac133a11be06bfb2f7acd8 Author: Petr Oros Date: Wed Mar 1 21:47:07 2023 +0100 ice: copy last block omitted in ice_get_module_eeprom() ** Package changed: ethtool (Ubuntu) => linux (Ubuntu) -- 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/2020917 Title: ethtool -m produces unreadable output for devices managed by the Intel ice driver Status in linux package in Ubuntu: Incomplete Bug description: We have a Supermicro X12SDV-8C-SP6F motherboard with a pair of SFP28 ports managed by an Intel E823-L for SFP controller. On this machine the SFP28 ports are eno3 and eno4. When asking ethtool for information about the installed SFP modules, we get this unhelpful output on Ubuntu Server 22.04 LTS: sudo ethtool --module-info eno3 Offset Values -- -- 0x: 03 04 07 20 00 00 02 00 00 00 00 06 67 02 0a 64 0x0010: 00 00 00 00 46 53 20 20 20 20 20 20 20 20 20 20 0x0020: 20 20 20 20 00 00 1b 21 53 46 50 2d 31 30 47 4c 0x0030: 52 2d 33 31 20 20 20 20 41 20 20 20 05 1e 00 d3 0x0040: 00 3a 00 00 46 32 30 33 30 33 32 32 36 38 39 20 0x0050: 20 20 20 20 32 32 30 34 30 32 20 20 68 fa 02 f1 0x0060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 I suspect this is the same bug that was reported by Red Hat here (access requires a Red Hat account): https://access.redhat.com/solutions/6999793 This patch in netdev seems relevant: https://lore.kernel.org/netdev/20230228204139.2264495-1-po...@redhat.com/T/ If I understand that patch correctly, this might a netdev issue that was exposed by a change in ethtool. If that's the case, then it's possible this shouldn't be classified as an ethtool bug, but I figured I'd start here. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ethtool 1:5.16-1 ProcVersionSignature: Ubuntu 5.15.0-72.79-generic 5.15.98 Uname: Linux 5.15.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri May 26 17:29:58 2023 ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: ethtool UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020917/+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 1874444] Re: Bionic ubuntu ethtool doesn't check ring parameters boundaries
This can't be fixed in ethtool, it has to be fixed in the kernel. ** Package changed: ethtool (Ubuntu) => linux (Ubuntu) -- 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/187 Title: Bionic ubuntu ethtool doesn't check ring parameters boundaries Status in linux package in Ubuntu: New Bug description: Upstream linux kernel implemented ring parameter boundaries check in commit: 37e2d99b59c4 ("ethtool: Ensure new ring parameters are within bounds during SRINGPARAM") (see link https://patchwork.ozlabs.org/project/netdev/patch/1515420026-11970-2 -git-send-email-tar...@mellanox.com/) Due to this commit, the community doesn't allow ring parameter boundary checks in driver code. The Bionic ubuntu kernel does not include this patch. And some network drivers rely on this patch for boundary checking of ring params. This causes bugs in case a ringparam was given an illegal value. Reproduction steps in AWS: 1. Create new c5.4xlarge instance with the ubuntu 18.04 official ami (uses the ENA network driver) and update to latest kernel using apt-get dist-upgrade and reboot for the new kernel to load. 2. Run ethtool -g ens5 output: Ring parameters for ens5: Pre-set maximums: RX: 16384 RX Mini: 0 RX Jumbo: 0 TX: 1024 Current hardware settings: RX: 1024 RX Mini: 0 RX Jumbo: 0 TX: 1024 3. Change the tx ring size to a legal number within boundaries - works! 4. Change the tx ring size to an illegal number such as 2048 with the command - sudo ethtool -G ens5 tx 2048. Expected behavior - operation not allowed Actual behavior - causes a crash of the driver since boundaries are not checked by ethtool. Proposed fix - include the above commit 37e2d99b59c4 ("ethtool: Ensure new ring parameters are within bounds during SRINGPARAM") in bionic (and probably other ubuntu releases as well) More data about the machine where the bug occured: ubuntu@ip-172-31-80-28:~/bionic$ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 ubuntu@ip-172-31-80-28:~/bionic$ uname -r 4.15.0-1065-aws To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/187/+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 1538773] Re: Default WoL settings override BIOS and cause battery drain while powered off.
** Package changed: ethtool (Ubuntu) => linux (Ubuntu) -- 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/1538773 Title: Default WoL settings override BIOS and cause battery drain while powered off. Status in linux package in Ubuntu: New Bug description: Similar issue and same fix as : http://akuederle.com/fix-battery- drain/ Wake on lan is disabled in BIOS yet Ubuntu default shutdown forces it enabled, causing unintended battery drain while powered off ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ethtool 1:3.16-1 ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6 Uname: Linux 4.2.0-25-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jan 27 17:11:08 2016 Dependencies: gcc-5-base 5.2.1-22ubuntu2 libc6 2.21-0ubuntu4 libgcc1 1:5.2.1-22ubuntu2 InstallationDate: Installed on 2016-01-20 (7 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ethtool UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1538773/+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 1500717] Re: ethtool -t option is failing for shiner-t in Ubuntu 14.04
Self-tests are implemented in the driver, not in ethtool. Assuming that this is an in-tree driver, I'm reassigning to linux. If the driver is out-of-tree then I don't think it's an Ubuntu issue at all. ** Package changed: ethtool (Ubuntu) => linux (Ubuntu) -- 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/1500717 Title: ethtool -t option is failing for shiner-t in Ubuntu 14.04 Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Rajeshkumar S- 2015-01-27 05:21:43 == ---Problem Description--- ethtool -t option is failing for shiner-t interface ---uname output--- 3.16.0-29-generic #39-Ubuntu SMP Tue Dec 16 20:53:59 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8286-42A /10D6B9T ---Steps to Reproduce--- Configure the interfaces of the of shiner-t adapter. Invoke ethtool with -t option for the shiner-t interface ( eth22 and eth20 in this test system [9.3.189.142]) It fails on the below test as root@powerio-le21:~# ethtool -t eth22 The test result is FAIL The test extra info: register_test (offline)0 memory_test (offline) 0 int_loopback_test (offline)0 ext_loopback_test (offline)0 nvram_test (online)1 interrupt_test (online)0 link_test (online) 0 the dmesg output during the event is [348306.120281] bnx2x 0003:0a:00.0 eth22: using MSI-X IRQs: sp 441 fp[0] 461 ... fp[7] 472 [348306.222325] bnx2x 0003:0a:00.0 eth22: NIC Link is Up, 1 Mbps full duplex, Flow control: none [348307.088285] bnx2x 0003:0a:00.0 eth22: using MSI-X IRQs: sp 441 fp[0] 461 ... fp[7] 472 [348313.363674] bnx2x 0003:0a:00.0 eth22: NIC Link is Up, 1 Mbps full duplex, Flow control: ON - receive & transmit root@powerio-le21:~# Userspace tool common name: ethtool The userspace tool has the following bit modes: 64 bit Userspace rpm: - Userspace tool obtained from project website: na *Additional Instructions for rajeshkum...@in.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach ltrace and strace of userspace application. == Comment: #4 - Rajeshkumar S - 2015-04-08 04:36:56 == Brian, I have a system that is available right now exhibiting this failure for Mason adapter from Qlogic eth1 and eth2 are the interfaces corresponding to the ports of the Qlogic's Mason adapter. The issue is reproducible now also wii01:~ # ethtool -t eth1 The test result is FAIL The test extra info: Loopback test (offline) -5 wii01:~ # echo $? 2 wii01:~ # ethtool -t eth2 The test result is FAIL The test extra info: Loopback test (offline) -5 == Comment: #15 - Guilherme Guaglianoni Piccoli - 2015-09-28 10:00:18 == (In reply to comment #14) > Mirror on Launchpad The mirror is requested because there's a need to involve QLogic - since they have no access to LTC bugzilla, we NEED to mirror this bug to Launchpad so we can discuss there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500717/+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 880316] Re: Link not detected / cable seems unplugged with jme - JMicron JMC250 Gigabit Ethernet Controller
Here's a patch with the changes relating to link management in the vendor driver version 1.0.5. Totally untested, but it applies and compiles against Linux 4.0. Don't ask me for help; I'm only uploading this to save time for anyone else who wants to work on the bug. ** Patch added: jme: link management changes from OOT version 1.0.8.5 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/880316/+attachment/4397673/+files/0001-jme-link-management-changes-from-OOT-version-1.0.8.5.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/880316 Title: Link not detected / cable seems unplugged with jme - JMicron JMC250 Gigabit Ethernet Controller Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to install Ubuntu on a Shuttle XS35GTV2. The installer can't set up the network connection. I've tried Ubuntu 10.04 32 and 64 bit netinstall, minimal and server, Ubuntu 11.10 32 bit netinstall. The Debian Squeeze 64 bit netinstall installer has no problem. (I've now installed openELEC which has no problems too) I was able to install Ubuntu 10.04 64 bit server but only without network connection. I then could load the jme module: # modprobe jme # depmod -a without errors. But I can't get eth0 running. The output of lspci is: 02:00.5 Ethernet controller: JMicron Technology Corp. JMC250 PCI Express Gigabit Ethernet Controller (rev 03) 03:00.0 Network controller: Realtek Semiconductor C., Ltd Device 8176 (rev 01) # lshw -C network *-network DISABLED description: Ethernet interface product: JMC250 PCI Express Gigabit Ethernet Controller vendor: JMicron Technology Corp. physical id: 0.5 bus info: pci@:02:00.5 logical name: eth0 version: 03 serial: 80:ee:73:1f:ef:df size: 10MB/s capacity: 1GB/s width: 32 bits clock: 33MHz capabilities: pm pciexpress msix msi bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=off broadcast=yes driver=jme driverversion=1.0.5 duplex=half latency=0 link=no multicast=yes port=MII speed=10MB/s resources: irq:17 memory:feaf4000-feaf7fff ioport:dc00(size=128) ioport:d800(size=256) *-network UNCLAIMED description: Network controller product: Realtek Semiconductor Co., Ltd. vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: latency=0 resources: ioport:e800(size=256) memory:febfc000-febf I've posted my problem at the Ubuntu users mailing list: http://www.linux-archive.org/ubuntu-user/588603-jme-module-missing-netboot-installation.html Edit: Unfortunately I couldn't reassign it as it has nothing to do with gnome-nettools (see post #1). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/880316/+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 880316] Re: Link not detected / cable seems unplugged with jme - JMicron JMC250 Gigabit Ethernet Controller
I had a look at what JMicron's driver does differently from the version included with Linux. It appears that it periodically checks for link failure after autonegotiation and then automatically tries renegotiating with only lower speed(s) enabled. So this is faulty hardware that can't maintain a 1000BASE-T link with some link partners. But since it works with others, disabling 1000BASE-T operation completely would cause a regression for some users. -- 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/880316 Title: Link not detected / cable seems unplugged with jme - JMicron JMC250 Gigabit Ethernet Controller Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to install Ubuntu on a Shuttle XS35GTV2. The installer can't set up the network connection. I've tried Ubuntu 10.04 32 and 64 bit netinstall, minimal and server, Ubuntu 11.10 32 bit netinstall. The Debian Squeeze 64 bit netinstall installer has no problem. (I've now installed openELEC which has no problems too) I was able to install Ubuntu 10.04 64 bit server but only without network connection. I then could load the jme module: # modprobe jme # depmod -a without errors. But I can't get eth0 running. The output of lspci is: 02:00.5 Ethernet controller: JMicron Technology Corp. JMC250 PCI Express Gigabit Ethernet Controller (rev 03) 03:00.0 Network controller: Realtek Semiconductor C., Ltd Device 8176 (rev 01) # lshw -C network *-network DISABLED description: Ethernet interface product: JMC250 PCI Express Gigabit Ethernet Controller vendor: JMicron Technology Corp. physical id: 0.5 bus info: pci@:02:00.5 logical name: eth0 version: 03 serial: 80:ee:73:1f:ef:df size: 10MB/s capacity: 1GB/s width: 32 bits clock: 33MHz capabilities: pm pciexpress msix msi bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=off broadcast=yes driver=jme driverversion=1.0.5 duplex=half latency=0 link=no multicast=yes port=MII speed=10MB/s resources: irq:17 memory:feaf4000-feaf7fff ioport:dc00(size=128) ioport:d800(size=256) *-network UNCLAIMED description: Network controller product: Realtek Semiconductor Co., Ltd. vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: latency=0 resources: ioport:e800(size=256) memory:febfc000-febf I've posted my problem at the Ubuntu users mailing list: http://www.linux-archive.org/ubuntu-user/588603-jme-module-missing-netboot-installation.html Edit: Unfortunately I couldn't reassign it as it has nothing to do with gnome-nettools (see post #1). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/880316/+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 1395269] Re: ethtool -t eth0 offline loses routing table
This is not ethtool's decision. Maybe the driver is taking the interface down and up. ** Package changed: ethtool (Ubuntu) = linux (Ubuntu) -- 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/1395269 Title: ethtool -t eth0 offline loses routing table Status in “linux” package in Ubuntu: Incomplete Bug description: ethtool -t eth0 offline does the tests, but leaves the routing table with only the entry for the local network. I had to sudo route add default gw 10.0.0.1, in my case. The online test didn't do this. Ubuntu 14.04, ethtool 1:3.13-1 Linux tesla 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ethtool -i eth0: driver: e1000e version: 2.3.2-k firmware-version: 1.1-0 bus-info: :00:19.0 relevant kernel log: [637008.472410] e1000e :00:19.0 eth0: offline testing starting [637009.077985] e1000e :00:19.0 eth0: testing unshared interrupt [637022.468941] e1000e :00:19.0: irq 45 for MSI/MSI-X [637022.572094] e1000e :00:19.0: irq 45 for MSI/MSI-X [637022.572257] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [637037.432893] e1000e: eth0 NIC Link is Up 10 Mbps Full Duplex, Flow Control: Rx/Tx [637037.433003] e1000e :00:19.0 eth0: Link Speed was downgraded by SmartSpeed [637037.433005] e1000e :00:19.0 eth0: 10/100 speed: disabling TSO [637037.433035] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [637037.982611] net_ratelimit: 3 callbacks suppressed [637037.982623] IPv4: martian source 10.0.0.17 from 80.73.161.44, on dev eth0 [637037.982628] ll header: : 00 19 d1 11 b4 9b 00 03 6d 11 34 1b 08 00m.4... (the martian packets are from TCP connections that my router is still NATing to this machine, even though without its routing table, it's not happy to see them.) And yes, my e1000e is autonegotiating to 10baseT/Full on the same cables and switch that still works at 1000baseT with another machine, hence running self-tests... I thought this machine used to run at 1000baseT, weird if I went 5 years without noticing my desktop being slow. Not what this bug report is about, though. The e1000e hardware is on a DG965WH Intel mobo (ICH8 / g965 graphics, first-gen core2) 00:19.0 Ethernet controller: Intel Corporation 82566DC Gigabit Network Connection (rev 02) Subsystem: Intel Corporation Device 0001 Flags: bus master, fast devsel, latency 0, IRQ 45 Memory at e030 (32-bit, non-prefetchable) [size=128K] Memory at e0324000 (32-bit, non-prefetchable) [size=4K] I/O ports at 20e0 [size=32] Capabilities: [c8] Power Management version 2 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Kernel driver in use: e1000e $ ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Full 100baseT/Full 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Speed: 10Mb/s Duplex: Full Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on MDI-X: on (auto) Cannot get wake-on-lan settings: Operation not permitted Current message level: 0x0007 (7) drv probe link Link detected: yes Appears to be the same problem as someone reported to Redhat a while ago, which got marked as fixed for the igb driver https://bugzilla.redhat.com/show_bug.cgi?format=multipleid=661976 Not very useful info in their BTS, because the bug that it's a dup of is now flagged private, so nobody can even look at it. Possibly this is a per-driver thing, unless the right fix is to have ethtool save/restore the routing table entries for that iface. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ethtool 1:3.13-1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Sat Nov 22 03:00:35 2014 Dependencies: gcc-4.9-base 4.9.1-0ubuntu1 libc6 2.19-0ubuntu6.3 libgcc1 1:4.9.1-0ubuntu1 multiarch-support 2.19-0ubuntu6.3 SourcePackage: ethtool UpgradeStatus: Upgraded to trusty on 2014-07-14 (130 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1395269/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1218691] Re: Possible missing firmware /lib/firmware/radeon/KAVERI
KAVERI firmware is now included in linux-firmware.git -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1218691 Title: Possible missing firmware /lib/firmware/radeon/KAVERI Status in “linux-firmware” package in Ubuntu: Triaged Status in Debian GNU/Linux: New Bug description: When updating the kernel today to 3.11.0-4-generic I saw the same warning messages I saw when I upgraded to 3.11.0-3-generic update-initramfs: Generating /boot/initrd.img-3.11.0-4-generic W: Possible missing firmware /lib/firmware/radeon/KAVERI_sdma.bin for module radeon W: Possible missing firmware /lib/firmware/radeon/KAVERI_rlc.bin for module radeon W: Possible missing firmware /lib/firmware/radeon/KAVERI_mec.bin for module radeon W: Possible missing firmware /lib/firmware/radeon/KAVERI_ce.bin for module radeon W: Possible missing firmware /lib/firmware/radeon/KAVERI_me.bin for module radeon W: Possible missing firmware /lib/firmware/radeon/KAVERI_pfp.bin for module radeon Further digging found bug 1183777 As mentioned in that bug, I did contact the named person: Hi, I'm still seeing the errors for KAVERI firmwares being missing in the latest kernel : phillw@piglet:~$ uname -a Linux piglet 3.11.0-3-generic #8-Ubuntu SMP Fri Aug 23 16:49:15 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux As the 1st Beta is creeping up fast, do you need this raising as a new bug? Regards, Phill. The reply is: As far as I can tell, the KAVERI firmware (and hardware) is not publicly available yet, so that's not a bug with the linux-firmware package. If you want to file a new bug about the warning messages, please file it against the linux (kernel) package. Until the firmware is available, I'm not really sure what the fix for that would be, other than removing/commenting out the relevant Kaveri lines in the radeon kernel code. Please find attached bug report as requested. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-4-generic 3.11.0-4.9 ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6 Uname: Linux 3.11.0-3-generic x86_64 ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: phillw 1965 F lxpanel CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Fri Aug 30 02:37:54 2013 HibernationDevice: RESUME=UUID=d98ac0ad-5c96-4382-8195-23b44e056358 InstallationDate: Installed on 2013-06-29 (61 days ago) InstallationMedia: Lubuntu 13.10 Saucy Salamander - Alpha amd64 (20130628) MachineType: Packard Bell EasyNote LJ71 MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-3-generic root=UUID=69c7aa0f-ccd0-4ac4-8930-e6f0efda9e6b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-3-generic N/A linux-backports-modules-3.11.0-3-generic N/A linux-firmware1.113 SourcePackage: linux StagingDrivers: zram UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2009 dmi.bios.vendor: Packard Bell dmi.bios.version: V1.03 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: EasyNote LJ71 dmi.board.vendor: Packard Bell dmi.board.version: V1.03 dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell dmi.chassis.version: V1.03 dmi.modalias: dmi:bvnPackardBell:bvrV1.03:bd09/22/2009:svnPackardBell:pnEasyNoteLJ71:pvrV1.03:rvnPackardBell:rnEasyNoteLJ71:rvrV1.03:cvnPackardBell:ct10:cvrV1.03: dmi.product.name: EasyNote LJ71 dmi.product.version: V1.03 dmi.sys.vendor: Packard Bell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1218691/+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