*** This bug is a duplicate of bug 2037490 ***
https://bugs.launchpad.net/bugs/2037490
Same here on DELL R710 with PERC 6/iR (SAS1068E), Ubuntu 23.10, kernel
6.5.0-17-generic
scsi host4: ioc1: LSISAS1068E B3, FwRev=00192f00h, Ports=1, MaxQ=266, IRQ=30
[ 958.168137]
Hi!
Same here. I'm using ASUS UX533FD (Asus zenbook 15) with ubuntu 22.04.3
(LTS). Same pattern seen, but it happen (approx) each 3 times that I
suspend my laptop. Is really annoying.
Anyone found a workaround for this issue?
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 2009243 ***
https://bugs.launchpad.net/bugs/2009243
Another one affected, works ok with 5.19.32, but no sound with 5.19.35
nor 5.19.38.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.19
*** This bug is a duplicate of bug 1909005 ***
https://bugs.launchpad.net/bugs/1909005
Is there any clue to what the problem is?
It's still a problem in my machine.
Kubuntu
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.2 LTS"
Hello there, i have seen this exact problem on my Acer Aspire A515-52G
as well, so decided to come here and confirm the issue.
Currently running: Ubuntu 22.04.2 LTS
- Kernel 5.19.0-32-generic
>From what i recall, the issue persisted through Ubuntu 22.10 as well.
--
You received this bug
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1987964/+attachment/5612083/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected jammy
** Description changed:
Ubuntu 22.04 LTS (Kernel updated to version 5.18.19) has chronic read-
only crashes when using Samsung KLUFG8RHDA-B2D1, the UFS of Samsung
Galaxy Book S (Intel) - SAMSUNG ELECTRONICS CO., LTD. 767XCL
- And
Hi,
```uname -r```
5.13.0-40-generic
Issue still ongoing.
--
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/1882388
Title:
Touchpad recognised as generic mouse
Status in linux package
-in devices), as the screens continue to operate
normally and receiving notifications from applications, such as Slack.
The /var/log/kern.log gets flooded with messages like:
Feb 15 13:40:12 fernando-ThinkPad-T430s kernel: [ 516.556167] pci_bus :04:
Allocating resources
Feb 15 13:40:13 fernando
Just updated my laptop (Ubuntu 20.04.3 LTS) from 5.13.0-27-generic to
5.13.0-28-generic and have the same issue (stuck in max brightness).
On 5.13.0-27-generic, brightness adjust works fine.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
*** This bug is a duplicate of bug 1916950 ***
https://bugs.launchpad.net/bugs/1916950
Thank you to all who worked on this. It has been fixed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Is anyone looking into this? It has been a long time with this bug open
and I'd like to know if I can help (testing or something, I am not very
savvy...)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi,
```uname -r```
5.4.0-58-generic
Issue still ongoing.
Now, with the workaround
```sudo modprobe -r psmouse && sudo modprobe psmouse´´´
It still works, after typing several times the same command, but I
noticed some things:
1.- Mouse gets idle sometimes and changes to generic mouse after
*** This bug is a duplicate of bug 1872159 ***
https://bugs.launchpad.net/bugs/1872159
Same bug, Acer Aspire V-Nitro vn7-792G-79LX intel + Nvidia Graphics
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi,
```uname -r```
5.4.0-53-generic
Issue still ongoing
--
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/1882388
Title:
Touchpad recognised as generic mouse
Status in linux package in
```ùname -r```
5.4.0-48-generic
Issue still ongoing
--
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/1882388
Title:
Touchpad recognised as generic mouse
Status in linux package in
I had to delete the mainstream kernel as I was having a horrible screen
tearing (my graphic card was not supported).
I left the kernel parameter "dyndbg='file drivers/input/mouse/* +p'"
and, although the issue still exists, it reduces the frequency of times
I need to use the "modprobe"
Is there anything else I can do?
I know Lenovo has an ubuntu forum, but hey are not very responsive...
--
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/1882388
Title:
Touchpad recognised
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+attachment/5392822/+files/dmesg
--
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/1882388
I suspended my laptop during the night; when I logged in again, the
touchpad worked for a while, but eventually got back as a generic mouse
(still mainline kernel).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
So, with my usual kernel version, 5.4.0.40-generic, adding that line
(exactly as it was written, including spaces, " and ' ) during boot ('e'
-editing the grub), the touchpad works, but after the laptop goes idle
or the screen is locked, it goes back as a generic mouse.
The trick of disconnecting
It was working for a while, but after the laptop goes idle or the screen
is locked, the touchpad goes back as a generic mouse; the trick of
disconnecting and connecting it back with ```modprobe psmouse``` keeps
working though...
--
You received this bug notification because you are a member of
It is using oem2.inf
I add the line at boot, by editing the grub and adding it at the end of
the line which starts with 'linux', and I don't want to get to excited,
but so far, so good...
** Attachment added: "dmesg"
Sorry, I uninstalled the updated kernel; should I install it again?
Where do I configure that line? during 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/1882388
Title:
Touchpad
** Attachment added: "deviceManager_1"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+attachment/5392299/+files/deviceManager_1.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "deviceManager_3.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+attachment/5392301/+files/deviceManager_3.png
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of
** Attachment added: "deviceManager_2"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+attachment/5392300/+files/deviceManager_2.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "deviceManager"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+attachment/5392298/+files/deviceManager_0.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
kernel-bug-exists-upstream
--
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/1882388
Title:
Touchpad recognised as generic mouse
Status in linux package in Ubuntu:
Confirmed
Bug
Just tried it this afternoon.
The issue is not fixed; I'm not seeing any difference...
I'm still using the new kernel (5.8.0-050800-generic); Should I delete
it?
Any other test?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Thanks for that.
I have a nVidia GeForce GTX 960M graphic card.
I am using proprietary drivers; I didn't need to do anything, it was
automatically installed when I first installed Ubuntu 20.04.
I've read on the page you sent me before, that I need to remove the
nVidia drivers before installing
Hi,
same issue here for Lenovo ideaPad Y700:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388
My touchpad suddenly stops being recognised as such and it's identified
as a generic mouse.
I have to disconnect it and connect it back again several times until is
recognised again as a
UPDATE:
`uname -r
5.4.0-40-generic
`
Touchpad is still getting disconnected randomly and identified as
generic mouse, and I have to use several times:
```sudo modprobe -r psmouse && sudo modprobe psmouse```
until is recognised again.
If you point me towards an info page I will try the mainline
```
Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)]
⎜ ↳ ETPS/2 Elantech Touchpad id=14 [slave pointer (2)]
```
--
You received this bug notification because you are
Diffiult to say, as it is both in the name:
85ln02af.exe
Touchpad Driver (Elan, Synaptics, ALPS)
Synaptics_19.3.10.38_ELAN_11.4.92.1_ALPS_8.201.1611.252
Last Modified Date: 03 Nov 2017
Original Publish Date: 26 Jan 2016
Document ID: DS105106
Manufacturer:
Elan, Synaptics, ALPS
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1882388
Title:
Touchpad recognised as generic mouse
Status in linux
** Attachment added: "acpidump"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+attachment/5389441/+files/acpidump.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
With what options? How I do that?
--
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/1882388
Title:
Touchpad recognised as generic mouse
Status in linux package in Ubuntu:
Incomplete
** Description changed:
I've just re-installed 20.04 (dual boot/windows 10) on my Lenovo
ideapadY700. My laptop recognises touchpad as mouse. I have no other
mouse plugged.
Touchpad firmware: 2ul001af
Lenovo ideapad700-15ISK BIOS version: CDCN54WW
I'm new in Ubuntu and I don't
HI,
I have the similar issue but I don't know if the proposed patch here
will help me, as my laptop is a Lenovo ideapadY700-15ISK:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388
I'm pretty new to Ubuntu, so I don't want to try anything new until I
have confirmation, as I had to
** Description changed:
I've just re-installed 20.04 (dual boot/windows 10) on my Lenovo
ideapadY700. My laptop recognises touchpad as mouse. I have no other
mouse plugged.
+
+ Touchpad firmware: 2ul001af
+ Lenovo ideapad700-15ISK BIOS version: CDCN54WW
I'm new in Ubuntu and I don't
I have realised that if I restart the mouse twice in a row, the touchpad
is recognised as such and starts working for a period of time.
```sudo modprobe -r psmouse```
```sudo modprobe psmouse```
Then, it is recognised back as a generic mouse and stops working.
--
You received this bug
I have similar issue on my Lenovo ideapad Y700-17ISK; Ubuntu 20.04
I have since 2 or 3 times the correct touchpad recognised, but after a
short time, it changes to PS/2 Generic Mouse, and I have no
functionalities at all.
I have a different bug, reported, as I don't know if the issue it's the
** Summary changed:
- Touchpad recognised as Logitech mouse
+ Touchpad recognised as generic mouse
--
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/1882388
Title:
Touchpad recognised as
** Tags added: elantech lenovo
** Tags added: ideapad touchpad
--
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/1882388
Title:
Touchpad recognised as Logitech mouse
Status in linux
Public bug reported:
I've just re-installed 20.04 (dual boot/windows 10) on my Lenovo
ideapadY700. My laptop recognises touchpad as mouse. I have no other
mouse plugged.
I'm new in Ubuntu and I don't know much...
```uname -a```
```Linux nando-Lenovo 5.4.0-33-generic #37-Ubuntu SMP Thu May 21
Public bug reported:
Bug
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-171-generic 4.4.0-171.200
ProcVersionSignature: Ubuntu 4.4.0-176.206-generic 4.4.211
Uname: Linux 4.4.0-176-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.23
Architecture: amd64
Date: Fri Jun 5
Hello everyone. The problem still here using Dell 7567, even in Ubuntu
20.04 kernel 5.4. But, following the suggestion of @danielgrebe in
another bug report, I was able to boot after switching PTT Security off
in BIOS. Thank you.
Font: https://bugs.launchpad.net/ubuntu/+source/intel-
For Dell 7567, still not working.
Last Kernel working: 5.0.0-36
I've tried: from 5.3.0-26 to 5.3.0-40
More info:
$ dmesg |grep microcode
[0.00] microcode: microcode updated early to revision 0xca, date =
2019-10-03
[0.197485] mce: [Hardware Error]: PROCESSOR 0:906e9 TIME
This bug supposedly was fixed in the linux 5.3.0-26.28. But for me, in
my Dell 7567 isn't working.
I'm using 5.0.0-36 for now and it's working.
Font: https://launchpad.net/ubuntu/+source/linux/5.3.0-26.28
--
You received this bug notification because you are a member of Kernel
Packages,
5.3.0-26 does not work on my Dell 7567
I'm using 5.0.0-36 for now:
Linux alvaro-7567 5.0.0-36-generic #39-Ubuntu SMP Tue Nov 12 09:46:06 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
I've solved it. Upgrading, with the Ukuu utility to kernel 4.20, the touchpad
is recognized and working! GREAT!!!
I don't know how to close the bug.
** Changed in: linux (Ubuntu)
Status: Incomplete => Opinion
** Changed in: linux (Ubuntu)
Status: Opinion => Fix Released
--
You
Public bug reported:
Since I have this laptop a Clevo GK5CN5Z the touchpad is not detected, but an
USB mouse yes.
In Windows 10 is working.
I've installed Ubuntu 18.10 that has linux kernel 4.18.0-13-generic.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810146/+attachment/5225954/+files/Xorg.0.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "devices"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810146/+attachment/5225953/+files/devices
--
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/1810146
@Alberto: Is there any chance that this work-around works without gdm3?
I'm using ubuntu-server 18.04 and this my laptop configuration:
➜ ~ inxi -G
Graphics: Card-1: Intel HD Graphics 5500
Card-2: NVIDIA GK208M [GeForce 920M]
Display Server: X.Org 1.19.6 driver: intel
@perryhelionsemail, well, now that you suggested that, I realize that as I'm
using the privative nvidia-driver-390, if the problem is actually related to
that, there's nothing the open source community could do.
I will switch to the nouveau driver and see if the problem persists (and if it
I'm having the exact same problem in a clean installation of Ubuntu 18.04.
I'm on a Lenovo Legion Y720. Even suspending by command or by closing the lid,
it hangs. I can see a dash blinking in top left of the screen. In that stage,
the laptop is not completely dead: the numlock button stills
The problem has been solved.
I have read information from Ubuntu forums and found that the problem was that
"sudo modprobe wl" couldn't work because the Secure boot in BIOS.
After disabling the Secure Boot, I was able to run "sudo modbprobe wl" and
wi-fi begun work.
In reality I run the command:
Public bug reported:
The Linux STA driver from bcmwl-kernel source is not working.
I'm using a USB-wi-fi adapter instead.
Ubuntu 18.04 LTS
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic
oth: RFCOMM TTY layer initialized
[ 44.556248] Bluetooth: RFCOMM socket layer initialized
[ 44.556252] Bluetooth: RFCOMM ver 1.11
[ 609.719015] Bluetooth: hci0 command 0x0c52 tx timeout
journalctl -b | grep Bluetooth
Ago 26 21:30:51 fernando-K46CB kernel: usb 1-1.1: Product: Blueto
socket layer initialized
[ 44.556252] Bluetooth: RFCOMM ver 1.11
[ 609.719015] Bluetooth: hci0 command 0x0c52 tx timeout
journalctl -b | grep Bluetooth
Ago 26 21:30:51 fernando-K46CB kernel: usb 1-1.1: Product: Bluetooth USB Host
Controller
Ago 26 21:31:00 fernando-K46CB kernel
Package: linux-image-4.4.0-79-generic (not installed)
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fernando 2867 F
-generic (not installed)
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fernando 1468 F pulseaudio
Date: Wed May 17 06:14:10
I have a new laptop Asus UX360UAK with this issue too: soft lockup CPU
stuck for XX seconds
--
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/1530405
Title:
NMI watchdog: BUG: soft lockup
I was experimenting similar behaviour using kernel 4.6.0 x86_64 (linux
mint + cinnamon).
After upgrading to 4.8.0-040800-generic x86_64 seems fine now.
Regards
Luis F. Heckler
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Upgraded BIOS to A13 and problem dissapear.
Checked all BIOS changelogs between versions and no one has information about
wifi interface, but problem appears to bo solved.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
With some routers, my wifi connection drops and restarts with the
following error:
May 23 20:12:00 neftali kernel: [ 1262.463055] iwlwifi :02:00.0: Queue 16
stuck for 1 ms.
May 23 20:12:00 neftali kernel: [ 1262.463066] iwlwifi :02:00.0: Current SW
read_ptr 244
Warm CPU
The problem was that the CPU in my computer was going warm because too little
air flow.
The reason for bad air flow was dirt on the cooling channels (between the
wings) of the metal temperature sink.
After taking it out and cleaning it with a vacuum cleaner, the temperature went
down
I was able to consistently reproduce this issue in Debian Wheezy by setting up
two Dell PowerEdge R620 servers directly connected and doing constant scp
transfer of large files back and forth while also setting the interface up &
down in a loop until it breaks (while [ true ]; do ip link set
I've the same laptop and I make it work by using the following flag in
/etc/default/grub
GRUB_CMDLINE_LINUX=i8042.noloop=1
This post gave me the solution:
http://forum.novatech.co.uk/archive/index.php/t-26251.html
After that you have to recreate the boot grub entry (I'm on ArchLinux:
Although this is bug was repported for 12.10, I am having this same
problem with [Xu|U]buntu 14.04. This started to show up about three
months ago, I can't recall exactly what kernel version.
The machine is the same model as the original of this bug repport (LG R590 5700)
$ uname -a
Linux
After two reboots the problem disappeared and has not returned. Is lshw
the card now shows like this:
*-generic
description: Unassigned class
product: RTS5227 PCI Express Card Reader
vendor: Realtek Semiconductor Co., Ltd.
physical
Public bug reported:
After upgrading today, the card reader stopped working.
lshw:
...
*-generic UNCLAIMED
description: Unassigned class
product: RTS5227 PCI Express Card Reader
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
I've just tested with 3.17
uname -a
Linux 34282-34282 3.17.0-031700-generic #201410060605 SMP Mon Oct 6 10:07:09
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
It doesn't show as 0%. But I can't find a way to read the percentage as
well.
** Attachment added: upower.txt
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
** Summary changed:
- 05ac:8286 [MacBookPro10,1] mouse battery indicator shows 0%
+ Apple Magic Mouse battery indicator shows 0%
--
You received this bug notification because you are a member of Kernel
Packages, which is
it from
resuming properly.
ApportVersion: 2.14.7-0ubuntu2
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: fernando 2348 F pulseaudio
/dev/snd/controlC0: fernando 2348 F pulseaudio
Date: Sun Sep 28 09:00:08 2014
DuplicateSignature: suspend
:23:00.0 failed with error -5
[ 226.396311] ixgbe: probe of :23:00.1 failed with error -5
I contacted Intel developers and they responded:
Hey Fernando,
We (ixgbe) only returns EIO (error 5) for a couple of reasons.
1) When we fail to io map (ioremap)
2) If the eeprom
No bluez-simple-agent 'solution' for me. cinnamon-bluetooth useless.
Blueman useless. All options greyed out. bluetooth-wizard useless.
Bluewho useless. Mint 17 64bit fresh install. Microsoft Sculp Mobile
keyboard + working universal bluetooth dongle.
Traceback (most recent call last):
File
Intel developers and they responded:
Hey Fernando,
We (ixgbe) only returns EIO (error 5) for a couple of reasons.
1) When we fail to io map (ioremap)
2) If the eeprom checksum is incorrect.
3) If the MAC address from the checksum is invalid
Reasons 2 and 3 are related to the NIC's
:22:00.0 failed with error -5
[ 226.396092] ixgbe: probe of :22:00.1 failed with error -5
[ 226.396203] ixgbe: probe of :23:00.0 failed with error -5
[ 226.396311] ixgbe: probe of :23:00.1 failed with error -5
I contacted Intel developers and they responded:
Hey Fernando
Noticed the same issue. Firefox (20.0+build1-0ubuntu0.10.04.3) hangs
when clicking any menu item. Rhythmbox (0.12.8-0ubuntu7) has the same
problem. Chrome (google-chrome-stable 27.0.1453.110-r202711) does not
load any window.
When booting with 2.6.32.60-generic everything works.
--
You
*** This bug is a duplicate of bug 1327300 ***
https://bugs.launchpad.net/bugs/1327300
Kernel 2.6.32-62.125 seems to fix the problem, at least for Firefox and
Chrome.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
] ixgbe: probe of :23:00.0 failed with error -5
[ 226.396311] ixgbe: probe of :23:00.1 failed with error -5
I contacted Intel developers and they responded:
Hey Fernando,
We (ixgbe) only returns EIO (error 5) for a couple of reasons.
1) When we fail to io map (ioremap)
2
: probe of :23:00.0 failed with error -5
[ 226.396311] ixgbe: probe of :23:00.1 failed with error -5
I contacted Intel developers and they responded:
Hey Fernando,
We (ixgbe) only returns EIO (error 5) for a couple of reasons.
1) When we fail to io map (ioremap)
2
[ 226.396203] ixgbe: probe of :23:00.0 failed with error -5
[ 226.396311] ixgbe: probe of :23:00.1 failed with error -5
I contacted Intel developers and they responded:
Hey Fernando,
We (ixgbe) only returns EIO (error 5) for a couple of reasons.
1) When we fail to io map (ioremap
Fernando,
We (ixgbe) only returns EIO (error 5) for a couple of reasons.
1) When we fail to io map (ioremap)
2) If the eeprom checksum is incorrect.
3) If the MAC address from the checksum is invalid
Reasons 2 and 3 are related to the NIC's eeprom so if they worked with
another system
with error -5
[ 226.396203] ixgbe: probe of :23:00.0 failed with error -5
[ 226.396311] ixgbe: probe of :23:00.1 failed with error -5
I contacted Intel developers and they responded:
Hey Fernando,
We (ixgbe) only returns EIO (error 5) for a couple of reasons.
1) When we fail
[ 226.396092] ixgbe: probe of :22:00.1 failed with error -5
[ 226.396203] ixgbe: probe of :23:00.0 failed with error -5
[ 226.396311] ixgbe: probe of :23:00.1 failed with error -5
I contacted Intel developers and they responded:
Hey Fernando,
We (ixgbe) only returns EIO
[ 226.396092] ixgbe: probe of :22:00.1 failed with error -5
[ 226.396203] ixgbe: probe of :23:00.0 failed with error -5
[ 226.396311] ixgbe: probe of :23:00.1 failed with error -5
I contacted Intel developers and they responded:
Hey Fernando,
We (ixgbe) only returns EIO (error 5
with error -5
[ 226.396092] ixgbe: probe of :22:00.1 failed with error -5
[ 226.396203] ixgbe: probe of :23:00.0 failed with error -5
[ 226.396311] ixgbe: probe of :23:00.1 failed with error -5
I contacted Intel developers and they responded:
Hey Fernando,
We (ixgbe
: unity
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.6.2-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fernando 2007 F pulseaudio
DistroRelease: Ubuntu 13.04
InstallationDate: Installed
COMMAND
/dev/snd/controlC0: fernando 2007 F pulseaudio
DistroRelease: Ubuntu 13.04
InstallationDate: Installed on 2012-06-10 (169 days ago)
InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120606.2)
MachineType: Dell Inc. Vostro V131
MarkForUpload: True
Package
with error -5
[ 226.396092] ixgbe: probe of :22:00.1 failed with error -5
[ 226.396203] ixgbe: probe of :23:00.0 failed with error -5
[ 226.396311] ixgbe: probe of :23:00.1 failed with error -5
I contacted Intel developers and they responded:
Hey Fernando,
We (ixgbe) only
[ 226.396092] ixgbe: probe of :22:00.1 failed with error -5
[ 226.396203] ixgbe: probe of :23:00.0 failed with error -5
[ 226.396311] ixgbe: probe of :23:00.1 failed with error -5
I contacted Intel developers and they responded:
Hey Fernando,
We (ixgbe) only returns EIO (error
] ixgbe: probe of :22:00.1 failed with error -5
[ 226.396203] ixgbe: probe of :23:00.0 failed with error -5
[ 226.396311] ixgbe: probe of :23:00.1 failed with error -5
I contacted Intel developers and they responded:
Hey Fernando,
We (ixgbe) only returns EIO (error 5
] ixgbe: probe of :22:00.1 failed with error -5
[ 226.396203] ixgbe: probe of :23:00.0 failed with error -5
[ 226.396311] ixgbe: probe of :23:00.1 failed with error -5
I contacted Intel developers and they responded:
Hey Fernando,
We (ixgbe) only returns EIO (error 5
:
Hey Fernando,
We (ixgbe) only returns EIO (error 5) for a couple of reasons.
1) When we fail to io map (ioremap)
2) If the eeprom checksum is incorrect.
3) If the MAC address from the checksum is invalid
Reasons 2 and 3 are related to the NIC's eeprom so if they worked with
another
with error -5
[ 226.396203] ixgbe: probe of :23:00.0 failed with error -5
[ 226.396311] ixgbe: probe of :23:00.1 failed with error -5
I contacted Intel developers and they responded:
Hey Fernando,
We (ixgbe) only returns EIO (error 5) for a couple of reasons.
1) When we fail
** Changed in: linux (Ubuntu)
Status: Expired = Confirmed
--
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/947697
Title:
Atheros AR9285 Wireless on Ubuntu 12.04 is slow, unstable
1 - 100 of 116 matches
Mail list logo
