[Bug 2056585] [NEW] Asus Vivobook Go E1404FA - snd_intel_hda not detecting built-in microphone - ALC897 / ALC256
Public bug reported: [Impact] Built-in microphone of the laptop is not detected and thus does not work. [Fix] None identified so far. [Test Case] Have Ubuntu 22.04 LTS installed on an Asus Vivobook Go E1404FA, using the 6.5 HWE kernel. Open the Sound settings and set the device "Family 17h [...]" to stereo duplex: The builtin speakers work but the internal microphone does not show up. Checking dmesg for snd-hda-intel shows nothing under inputs for the device. The follow module options for snd-hda-intel have no effect: model=auto model=laptop-amic [Where problems could occur] Likely in hardware detection for the snd-hda-intel module [Other Info] mittebam@duchesse:~$ cat /proc/version_signature Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13 mittebam@duchesse:~$ lspci | grep Audio 03:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device 1640 03:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor (rev 6f) 03:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller mittebam@duchesse:~$ sudo dmidecode -H 0x0032 # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 3.5.0 present. Table at 0xBACE6000. Handle 0x0032, DMI type 41, 11 bytes Onboard Device Reference Designation: Realtek ALC256 Type: Sound Status: Enabled Type Instance: 1 Bus Address: :03:00.6 mittebam@duchesse:~$ sudo dmesg | grep snd [6.284080] snd_pci_acp6x :03:00.5: enabling device ( -> 0002) [6.416621] snd_hda_intel :03:00.1: enabling device ( -> 0002) [6.417219] snd_hda_intel :03:00.1: Handle vga_switcheroo audio client [6.417431] snd_hda_intel :03:00.6: enabling device ( -> 0002) [6.438262] snd_hda_intel :03:00.1: bound :03:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) [6.450675] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC897: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [6.450685] snd_hda_codec_realtek hdaudioC1D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [6.450690] snd_hda_codec_realtek hdaudioC1D0:hp_outs=1 (0x1b/0x0/0x0/0x0/0x0) [6.450693] snd_hda_codec_realtek hdaudioC1D0:mono: mono_out=0x0 [6.450696] snd_hda_codec_realtek hdaudioC1D0:inputs: mittebam@duchesse:~$ lsb_release -rd Description:Ubuntu 22.04.4 LTS Release:22.04 mittebam@duchesse:~$ apt-cache policy linux-image-generic-hwe-22.04 linux-image-generic-hwe-22.04: Installed: 6.5.0.25.25~22.04.12 Candidate: 6.5.0.25.25~22.04.12 Version table: *** 6.5.0.25.25~22.04.12 500 500 http://nl.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://nl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages mittebam@duchesse:~$ apt-cache policy linux-generic-hwe-22.04 linux-generic-hwe-22.04: Installed: 6.5.0.25.25~22.04.12 Candidate: 6.5.0.25.25~22.04.12 Version table: *** 6.5.0.25.25~22.04.12 500 500 http://nl.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://nl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages mittebam@duchesse:~$ apt-cache policy firmware-sof-signed firmware-sof-signed: Installed: 2.0-1ubuntu4.5 Candidate: 2.0-1ubuntu4.5 Version table: *** 2.0-1ubuntu4.5 500 500 http://nl.archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages 500 http://nl.archive.ubuntu.com/ubuntu jammy-updates/restricted i386 Packages 100 /var/lib/dpkg/status 2.0-1ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu jammy/restricted amd64 Packages 500 http://nl.archive.ubuntu.com/ubuntu jammy/restricted i386 Packages ** Affects: linux-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "lspci_vnvn.log" https://bugs.launchpad.net/bugs/2056585/+attachment/5754121/+files/lspci_vnvn.log ** Package changed: linux (Ubuntu) => linux-hwe-6.5 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056585 Title: Asus Vivobook Go E1404FA - snd_intel_hda not detecting built-in microphone - ALC897 / ALC256 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2056585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1377653] Re: HDMI sound output not detected / NVIDIA optimus laptop
This bug needs to be moved from the alsa-driver/pulseaudio thread and moved to either nouveau or nvidia packages. The issue why this is not fixed as far as I can figure out is because the address modified with the setpci command is not documented by nvidia and thus cannot be added to the official drivers. You do not want to have any dirty hacks that are based on rumours/forum-posts only in production-level drivers. as a side note: #19+#24 is still needed on ubuntu 18.04 for the audio device to show up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1377653 Title: HDMI sound output not detected / NVIDIA optimus laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1377653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1377653] Re: HDMI sound output not detected / NVIDIA optimus laptop
@WinEunuchs2Unix Cool, good to hear this also works for older nVidia cards and on older Ubuntu versions! Your suggestion to adjust the paths to /usr/local/bin/ is a good one, I had the test script in /root/ and didn't bother to move it yet ;) The screen flickering - do you notice this as well if you set the laptop to boot discrete mode (ie: nVidia only, IGP disabled)? I did not notice any flickering during boot on my laptop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1377653 Title: HDMI sound output not detected / NVIDIA optimus laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1377653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1377653] Re: HDMI sound output not detected / NVIDIA optimus laptop
I have a very useful update on the Skylake/nvidia GTX1060 case where the HDMI Audio device does not show up in lspci. Based on information found on the NVidia Developer forum, I was able to get my HDMI audio device show up in Ubuntu 17.10 as per my posting there: https://devtalk.nvidia.com/default/topic/1024022/linux/gtx-1060-no- audio-over-hdmi-only-hda-intel-detected-azalia/post/5216905/#5216905 Crossposting the information here so affected people can try this as well: Create the file "/etc/systemd/system/fix-hdmi-audio.service" as per below: [Unit] Description=nVidia HDMI Audio Fixer Before=systemd-logind.service display-manager.service After=module-init-tools.service [Service] Type=oneshot ExecStart=/root/fix-hdmi-audio.sh [Install] WantedBy=multi-user.target Create the file "/root/fix-hdmi-audio.sh" as per below (Note, adjust the PCI device paths to the PCI ID of the PCIe Bride and NVidia card): #!/bin/sh setpci -s 01:00.0 0x488.l=0x200:0x200 rmmod nvidia-uvm nvidia-drm nvidia-modeset nvidia sh -c 'echo 1 > /sys/bus/pci/devices/:01:00.0/remove' sh -c 'echo 1 > /sys/bus/pci/devices/:00:01.0/rescan' modprobe nvidia nvidia-modeset nvidia-drm nvidia-uvm And then execute the following commands (as root) to make it do this at boot: chmod +x /root/fix-hdmi-audio.sh systemctl enable fix-hdmi-audio.service After each reboot, I now see the HDMI audio device on my laptop: fludizz@tongerlo:~$ lspci | grep "PCIe Controller\|NVIDIA" 00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07) 01:00.0 VGA compatible controller: NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller (rev a1) fludizz@tongerlo:~$ aplay -l | grep NVidia card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0] card 1: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1] card 1: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1377653 Title: HDMI sound output not detected / NVIDIA optimus laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1377653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1377653] Re: HDMI sound output not detected / NVIDIA optimus laptop
I am not sure this is an alsa-specific bug. Looks to be more of an issue with the Nvidia card and the way it handles HDMI audio. This also affects a BTO 15CL76 notebook (I7-6700HQ / GTX1060) set in DISCRETE mode. No HDMI audio device shows up at all. The active nvidia driver (as of writing) is nvidia_367. No bbswitch/bumblebee installed as Hybrid mode is disabled. Suggestions on the nvidia forum are to shutdown your X environment and then run the following commands as root: https://devtalk.nvidia.com/default/topic/609790/linux/no-hdmi-sound-w -optimus-in-linux/ rmmod nvidia echo 1 > /sys/bus/pci/devices/\:00\:01.0/remove echo 1 > /sys/bus/pci/rescan This also had no effects - the Nvidia device comes back online but without the audio device showing up. Here's the output of lspci -H 1: fludizz@tongerlo:~$ sudo lspci -H 1 00:00.0 Host bridge: Intel Corporation Sky Lake Host Bridge/DRAM Registers (rev 07) 00:01.0 PCI bridge: Intel Corporation Sky Lake PCIe Controller (x16) (rev 07) 00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31) 00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31) 00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA Controller [AHCI mode] (rev 31) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #1 (rev f1) 00:1c.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #5 (rev f1) 00:1c.6 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #7 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #9 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31) 00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31) 00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31) 01:00.0 VGA compatible controller: NVIDIA Corporation Device 1c60 (rev a1) 6d:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5287 (rev 01) 6d:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 12) 6e:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a) 6f:00.0 Non-Volatile memory controller: Intel Corporation Device f1a5 (rev 03) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1377653 Title: HDMI sound output not detected / NVIDIA optimus laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1377653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322471] Re: nvidia-173 173.14.39-0ubuntu3: nvidia-173 kernel module failed to build
*** This bug is a duplicate of bug 1289440 *** https://bugs.launchpad.net/bugs/1289440 The bug has been fixed in the newer nvidia graphics drivers (304 and 311) but it is still not fixed in the 173 package: Loading new nvidia-173-173.14.39 DKMS files... First Installation: checking all kernels... Building only for 3.16.0-39-generic Building for architecture x86_64 Building initial module for 3.16.0-39-generic Error! Bad return status for module build on kernel: 3.16.0-39-generic (x86_64) Consult /var/lib/dkms/nvidia-173/173.14.39/build/make.log for more information. Setting up nvidia-settings (331.20-0ubuntu8) ... Processing triggers for initramfs-tools (0.103ubuntu4.2) ... update-initramfs: Generating /boot/initrd.img-3.16.0-39-generic This driver is needed for even older hardware (e.g. NV17GL) that is not supported by the 'legacy' 304 driver. ** Attachment added: /var/lib/dkms/nvidia-173/173.14.39/build/make.log https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-173/+bug/1322471/+attachment/4408785/+files/make.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322471 Title: nvidia-173 173.14.39-0ubuntu3: nvidia-173 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-173/+bug/1322471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 992411] Re: network-manager: Please don't Depend on dnsmasq-base
Sorry for the bump but dnsmasq is still enabled by default and cannot be removed without removing network-manager. I ran into the issue where dnsmasq introduced a security problem when running VPN connections. For security reasons all DNS traffic was supposed to be flowing to the DNS server pushed by the VPN Server. This used to work before dnsmasq was made the default. With dnsmasq enabled, it sends the DNS request completely at random to the various DNS server the system has learned, including those from the public network (DHCP). This not only leaks information, it also breaks resolving hosts on the other end of the VPN because dnsmasq responds with NXDOMAIN if the query for a VPN-connected hostname happened to have ended up in the public DNS. After commenting out the line dns=dnsmasq in /etc/NetworkManager/NetworkManager.conf DNS is properly enforced again and behaving completely predictable. I wish to remove dnsmasq from my client systems as well because of this security leak. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/992411 Title: network-manager: Please don't Depend on dnsmasq-base To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/992411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 613872] Re: md raid5 set inaccessible after some time.
Sorry, I have migrated away from md-raid in favor of hardware raid at the time of this bug and have not rebuild any system to use md-raid since. With hardware raid and the same disks the problem does not occur. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/613872 Title: md raid5 set inaccessible after some time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/613872/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 989817] Re: Cannot change bluetooth device name
I can confirm Carroarmato0 his solution indeed works :) I was able to change the hostname as well using the file /var/lib/bluetooth/[MACaddress]/config -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/989817 Title: Cannot change bluetooth device name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/989817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 887484] Re: empathy not connect to msn, no cam, no avatar, not work
Today after upgrading python-papyon to the latest version (0.5.5-1ubuntu1.4) the issue is resolved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/887484 Title: empathy not connect to msn,no cam,no avatar,not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/887484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 887484] Re: empathy not connect to msn, no cam, no avatar, not work
I can confirm telepathy does not want to connect to MSN... This started a few weeks ago, I'm running ubuntu 11.04, with telepathy-butterfly 0.5.15-1. It does not show any errors, it just stays in Connecting... state indefinitely. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/887484 Title: empathy not connect to msn,no cam,no avatar,not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/887484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 772207] Re: version 173.14.30 is buggy for GeForce FX 5200
Same problem here using a Nvidia Quadro FX 880M card. Driver is activated but not currently in use. Using glxgears, it said it did about 4000 fps on the command line but on the display the gears are only moving at about 1 frame every 5 seconds. glxinfo states direct rendering is enabled. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/772207 Title: version 173.14.30 is buggy for GeForce FX 5200 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 538256] Re: Screen brightness not controllable on Lenovo Ideapad S10-3, U350, and Z360
I'm running Ubuntu 11.04 on a Lenovo ThinkPad W510 (Nvidia Quadro FX 880M graphics card). - setpci does nothing - using /proc/acpi tables to adjust display brightness doesn't work - Using /sys/class/backlight/... also doesn't work All of the above still aren't working if I pass the acpi_backlight=vendor kernel option in grub. All this does is locking the brightness to max. If I kill X and work on the CLI, the brightness setting DOES work! It's only under gnome that I cannot adjust the brightness. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/538256 Title: Screen brightness not controllable on Lenovo Ideapad S10-3, U350, and Z360 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 613872] Re: md raid5 set inaccessible after some time.
Sorry for the bump but maybe something to keep in mind with this issue. Some reading up on the internet has gotten me on a different track about the loss of the RAID Arrays in my old setup: It seems starting with kernels newer then 2.6.24 there might be a change in the timers mdadm uses to declare a disk dead or alive. This is possible related to ERC/CCTL/TLER settings: The time a drive is allowed to use to recover from a read error (e.g. bad sector). Normal consumer disks have these ERC/CCTL/TLER setting disabled by default (or don't have it at all) causing them to take up to a minute to respond again to the OS. With ERC/CCTL/TLER enabled, a disk will respond to the OS/RAID driver again after a specified amount of time (e.g. 7 seconds). The RAID driver then sees the drive is still alive and corrects the data using the data on other drives. Could it be that mdadm's disk timers have been changed causing newer kernels to drop groups of disks from the array? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/613872 Title: md raid5 set inaccessible after some time. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 715331] Re: e1000e / Intel 82577LM Gbit NIC Jumbo Frames not working.
Installed 2.6.38-999-generic AMD64 kernel and tried setting MTU. Here are the results: root@brand:~# uname -a Linux brand 2.6.38-999-generic #201102260905 SMP Sat Feb 26 09:10:54 UTC 2011 x86_64 GNU/Linux root@brand:~# ifconfig eth0 mtu 4078 root@brand:~# ifconfig eth0 mtu 4079 SIOCSIFMTU: Invalid argument root@brand:~# ifconfig eth0 mtu 9000 SIOCSIFMTU: Invalid argument I cannot set any MTU above 4078. ** Tags removed: needs-upstream-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/715331 Title: e1000e / Intel 82577LM Gbit NIC Jumbo Frames not working. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 715331] Re: e1000e / Intel 82577LM Gbit NIC Jumbo Frames not working.
OK, did some more research on this MTU value, it turns out the 82577LM controller is limited to 4k Jumbo frames. Tried it again in the current stable release kernel and I can set the MTU to 4078 using the normal kernel as well. Not a bug, a hardware limitation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/715331 Title: e1000e / Intel 82577LM Gbit NIC Jumbo Frames not working. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 715331] [NEW] e1000e / Intel 82577LM Gbit NIC Jumbo Frames not working.
Public bug reported: I have a Lenovo ThinkPad W510 running Ubuntu 10.10 (completely up-to- date with the repo's). Recently I tried enabling Jumbo Frames on the Intel 82577LM Gigabit ethernet controller which resides in this laptop. According to the Intel website, this device supports Jumbo Frames however I cannot enable it. I'm running AMD64 kernel package linux- image-2.6.35-25-generic. Link to Intel's product information: http://ark.intel.com/Product.aspx?id=35652 Output when trying to set the MTU: root@brand:~# ifconfig eth0 mtu 9000 SIOCSIFMTU: Invalid argument ethtool output: root@brand:~# ethtool -i eth0 driver: e1000e version: 1.0.2-k4 firmware-version: 0.12-1 bus-info: :00:19.0 root@brand:~# ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on MDI-X: off Supports Wake-on: pumbag Wake-on: g Current message level: 0x0001 (1) Link detected: yes ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: linux-image-2.6.35-25-generic 2.6.35-25.44 Regression: No Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10 Uname: Linux 2.6.35-25-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fludizz2180 F pulseaudio /dev/snd/pcmC0D0c: fludizz2180 F...m pulseaudio /dev/snd/seq:timidity 1735 F timidity CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf262 irq 55' Mixer name : 'Conexant CX20585' Components : 'HDA:14f15069,17aa218b,00100302' Controls : 6 Simple ctrls : 4 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xcdefc000 irq 16' Mixer name : 'Nvidia GPU 0a HDMI/DP' Components : 'HDA:10de000a,10de0101,00100100' Controls : 16 Simple ctrls : 4 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 6MHT35WW-1.10' Mixer name : 'ThinkPad EC 6MHT35WW-1.10' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Tue Feb 8 18:57:08 2011 HibernationDevice: RESUME=UUID=3cd836b5-12c5-4c19-806f-3d63474aae4d InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) MachineType: LENOVO 43194NG ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-25-generic root=UUID=9b6346be-8b2f-4886-8ad8-1370882e80c8 ro quiet vga=794 ProcEnviron: LANGUAGE=en PATH=(custom, no user) LANG=en_GB.utf8 SHELL=/bin/bash RelatedPackageVersions: linux-firmware 1.38.3 SourcePackage: linux dmi.bios.date: 04/19/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET54WW (1.17 ) dmi.board.name: 43194NG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET54WW(1.17):bd04/19/2010:svnLENOVO:pn43194NG:pvrThinkPadW510:rvnLENOVO:rn43194NG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 43194NG dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kernel-net maverick needs-upstream-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/715331 Title: e1000e / Intel 82577LM Gbit NIC Jumbo Frames not working. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 715331] Re: e1000e / Intel 82577LM Gbit NIC Jumbo Frames not working.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/715331 Title: e1000e / Intel 82577LM Gbit NIC Jumbo Frames not working. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 454747] Re: NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out
I don't manually reset the device. This is done automatically, after the reset it renegotiaties the NIC speed too 100 full duplex and resumes operation. It might be that I also experience loss but my network load is so low it isn't noticeable. I've bypassed the problem as well now by removing the RAID card I had to free the only PCI slot in the machine and placed a Intel dualport GBit nic. Then I proceded to blacklist the via_rhine module (for some reason the BIOS does not allow me to hard-disable the two onboard nics) and I have had no more issues since then. I will keep my subscription to this bug open because I might start testing multicasting and vlan's and intend to use seperate nics for seperate purposes. I do believe I'm affected by the same bug (Same sequence of events followed by a hard reset and the netdev watchdog dump in the logs) but perhaps due to configuration differences (or even different firmware/build revisions of the NIC) it was not fatal in my system. -- NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out https://bugs.launchpad.net/bugs/454747 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 454747] Re: NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out
Hmm, I have the same issue, however I do not have the option of adding additional LAN cards. However the bug is not 'fatal' for my server (Ubuntu 10.04LTS), it recovers without issues after the nic reset occurs. Can't even detect packet loss when it happens! I did notice this bug happening to the idle interface as well (the system has two onboard Via Rhine interfaces (Via LT15000AG)) and seems to be unrelated to network load as my server hardly has any. By the way this bug seems to have been present since at least 8.04LTS (2.6.24) and even before that on Debian Etch (2.6.20), I also had the same issue on their kernels. Bit strange that this bug (Which I can trace back to about 2002 using google) still has not been fixed... -- NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out https://bugs.launchpad.net/bugs/454747 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 613872] Re: md raid5 set inaccessible after some time.
Took less then 24 hours this time. However I did manage to capture dmesg output this time. See the attachment for the full log, here's the snippet how it goes wrong: mdadm detects a drive timeout (these soft hangs of the hard drives have been present ever since day one and never caused any issues). mdadm fails the drive and tries to keep the raid drive running on 3 disks. But this reset/hang of the disks seems to happen controller wide, thus it fails the next drive until it has no drives left and fails the array with an uncorrectable error message. Then the I/O write errors occur and the system fails. Is mdadm to strict in drive timing? Is the sata controller driver to strict? Where does this go wrong? Any idea's? ** Attachment added: dmesg output http://launchpadlibrarian.net/53435676/dmesg.txt -- md raid5 set inaccessible after some time. https://bugs.launchpad.net/bugs/613872 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 613872] Re: md raid5 set inaccessible after some time.
Ok, the problem occurred again... However for some reason it did not capture the errors on the USB drive. I did happen to have a console open at the time and managed to get the response from a dmesg output. It was swamped with the following text: [358579.557869] metapage_write_end_io: I/O error [358579.559914] metapage_write_end_io: I/O error [358579.562155] metapage_write_end_io: I/O error [358614.526341] metapage_write_end_io: I/O error Again no other errors captured because the data is lost and the system is now no longer able to boot. Just hanging after the filesystem check occurs... I'll start rebuilding the system *again* using the old Ubuntu 8.04LTS version... The last known good version. -- md raid5 set inaccessible after some time. https://bugs.launchpad.net/bugs/613872 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 613872] Re: md raid5 set inaccessible after some time.
Managed to get the system up and running again. Had to reassemble all mdadm raid arrays using a live CD. After reassembling all arrays I rebooted back into the operating system and had to reboot three times to get it to work again. First reboot, it prompted it noticed a size change from 0 to human unreadble high number for /dev/md0, it did a fsck and then hung. Rebooted the system using crtl+alt+del. This prompted the system to reboot cleanly luckily, and unmounted the newly discovered /dev/md0. At this reboot, the same steps where repeated for the swap volume (/dev/md1). Last reboot was for the /var/ volume (/dev/md2). The system is now back up and running and probably will go down again in a few days... It seems mdadm lost it's config in the original system and it was trying to boot the system using /dev/sda1 (as it did find the / filesystem) instead of /dev/md0. After reconstruction using the live CD, the bootlog also showed the RAID arrays and their printouts again. One other thing I did as a precaution is trashing the contents of the /var/ folder on the /dev/md0 array. It somehow made a lock and run file in there (probably when it lost the RAID5 set containing /var/). I think the bug is not necesarily in the kernel but could be in mdadm, since I manually had to reassemble the arrays using a live CD. -- md raid5 set inaccessible after some time. https://bugs.launchpad.net/bugs/613872 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 613872] [NEW] md raid5 set inaccessible after some time.
Public bug reported: Binary package hint: linux-image-2.6.32-24-generic-pae I upgraded from Ubuntu 8.04LTS to 10.04LTS last weekend, the system has been running fine untill today. For some reasons the webserver/mysql server stopped responding and I checked the console and noticed it being flooded by input/output errors. I managed to type dmesg and that was filled with this information as well. By now all services that had a reference to /var/ (Which is mounted on /dev/md2, a raid5 set based on 4 disks) had stopped. After typing reboot the system came back up normally and mdadm started a resync of the raid5 set. No dataloss on the raid set detected. I immediately checked all the logs under /var/log and noticed they all stopped at the point the input/output errors started flooding the console. The errors that flooded the console did not end up in the dmesg logs probably because the /dev/md2 raidset was completely unavailable at the moment this occurred. The problem seems similar to the one I reported here: https://bugzilla.kernel.org/show_bug.cgi?id=11328#c48 This issue was NOT present under Ubuntu 8.04 with the 2.6.24 kernel, it was present under Debian Lenny with the 2.6.26 kernel. And unfortunately this bug seems to be present at the 2.6.32 kernel as well... The system has been running for about a year on 8.04LTS without any issues. System information: - Via Epia LT15000AG (Via CenterHaul Esther CPU, CX700 chipset), 1GB RAM - SiI3124 PCI-X sata controller - 2x Via Rhine II onboard NIC (VT6102) - 4x Samsung Spinpoint 160GB SATA hard drive connected to the SiI3124 controller. These drives are configured as follows: - /dev/md0 is a 4 disk RAID1 set containing the '/' filesystem. - /dev/md1 is a 4 disk RAID5 set used as swap. - /dev/md2 is a 4 disk RAID5 set used as the '/var/' filesystem. The system is running Ubuntu 10.04 LTS configured for only LTS packages and completely up to date (Except for the new kernel image that was ready for download this morning). I will attempt to create a photograph of the console if the error occurs again. Only thing I can get out of the dmesg log is the know bug that has been with the kernel since 2002 for the Via Rhine ethernet adapters. I've added a USB drive to the system and set up two sessions, one to tail the kernel log and one to tail dmesg. Both are dumping the output to a 512MB flash drive, this should be enough to capture the events preceding the issues. It is OK to consider this bug report incomplete until I managed to capture some logs. Attached lspci -vvv and dmesg output from the last boot. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- md raid5 set inaccessible after some time. https://bugs.launchpad.net/bugs/613872 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 613872] Re: md raid5 set inaccessible after some time.
** Attachment added: lspci -vvv output http://launchpadlibrarian.net/53108844/lspci_vvv.txt -- md raid5 set inaccessible after some time. https://bugs.launchpad.net/bugs/613872 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 613872] Re: md raid5 set inaccessible after some time.
Dmesg output from last boot. ** Attachment added: dmesg output http://launchpadlibrarian.net/53108878/dmesg.txt -- md raid5 set inaccessible after some time. https://bugs.launchpad.net/bugs/613872 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
