Bug#673705: [Pkg-utopia-maintainers] Bug#673705: Bug#673705: network-manager: Network Manager doesn't connect to wifi (greyed out) when device cannot report signal strength
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sorry for the ambiguity. I filed a bug against the kernel in Debian about this problem. Here it is: 673703: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673703 Anyhow they said it was a hardware/firmware issue and that they wouldn't fix it themselves. They forwarded the issue upstream, to linux-wireless. On 05/20/2012 11:43 PM, Michael Biebl wrote: On 20.05.2012 23:36, Gennady N. Uraltsev wrote: 02:02.0 Network controller: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04) and the driver is the kernel module ipw2100 I already told them about this and they say it is a hardware/firmware ^ who is them? limitation and they aren't sure it is fixable. I thought this was kernel/driver issue and affected drivers were ipw2100/ipw2200 CCing Dan, maybe he can his insight on this issue. On 05/20/2012 11:06 PM, Michael Biebl wrote: On 20.05.2012 22:55, Gennady N. Uraltsev wrote: There are many cards that have this problem, and I do not see any reason to Which card and driver do you use? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPugW4AAoJEO4X3lPe3Y0xEA8P/32gZVko9cxq+9JGHNVnuBoQ quYSfu0RmekTw5jKMaaFe/nfRJFqgPZA6Smv6Z/bKps0hf36UmPMJQJ2Oi/ZOxKi uTgK3CJ5BuZpy9BUrRSOhjdxhLE5eHEI99VLDPehoQ2fio0AzwfKmc1ZtPMh8985 c5G1cqm4loiULEfF+jtjD7+rnDAm8BhyqS0JfVbhSCgJopr0QMpm7YhvTPb2/JeL TyG/Jodt6eRYENjclIqmmEghgCucm95EV8fw3FjWIWbeG4o4IHgE5aU8FkGBqeUu ecJr1Yby3FcQeFsYadivxqOqGc5g9Va5A0gaRPhYk6WATFgJTaWX2WmDUdVX5BZD 7TukNIn3B+scLAtMf9x0XVwkcAZzSr6VLog47TjdNckdzIvgSlnMxHw/yfjcxjU4 V0jvbsjDGxdo+yy+hlPk2L7GHUNAN+WV/UKNKKT1bhR4iYvypF3rd9cfP8v2QGTl kZvmH80HWLbWSNRlUKX2J4ebF/fJMToi8UBEDAu2rHx7FGkNtAn/m09eJDmVj3C0 89zM/ME82bq9l7DKOt+f+CTrGz/tbcOX8C2siEH3QtWvwdw7/nT+uraEig1CsaAp vfakRaYkWzVqFLn95hRi1qQ3jDDsRpFvitRPXfPYF/Ck9+wfLQCK2+//KmGXPxSQ /dbKMN1jvF4kfUZS+KLV =rd3h -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#673703: linux-image-3.2.0-2-686-pae: module ipw2100 doesn't report signal strength
Package: linux-2.6 Version: 3.2.17-1 Severity: important Tags: upstream The ipw2100 module fails to report signal strength. With a Intel 2100 3B mini card this makes it impossible to use standard tools for wireless. As a matter of fact roaming decisions and many others of standard software are based on these values. To illustrate what I am talking about. The command #iwlist eth1 scan outputs: eth1 Scan completed : Cell 01 - Address: 02:18:F8:7A:4E:5E ESSID:eduroam Protocol:IEEE 802.11bg Mode:Master Frequency:2.412 GHz (Channel 1) Encryption key:on Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s 11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s 48 Mb/s; 54 Mb/s Quality:64 Signal level:0 Noise level:0 IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : 802.1x Extra: Last beacon: 248ms ago Cell 02 - Address: 02:18:39:D4:13:B3 ESSID:eduroam Protocol:IEEE 802.11bg Mode:Master Frequency:2.412 GHz (Channel 1) Encryption key:on Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s 11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s 48 Mb/s; 54 Mb/s Quality:35 Signal level:0 Noise level:0 IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : 802.1x Extra: Last beacon: 252ms ago Look at the field labeled signal level I do not know how related is the line that sometimes appears in syslog: wpa_supplicant[1826]: bgscan simple: Failed to enable signal strength monitoring Should I file the bug somewhere else? Signal strength monitoring on other wifi cards like usb ones works flawlessly... -- Package-specific info: ** Version: Linux version 3.2.0-2-686-pae (Debian 3.2.17-1) (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-5) ) #1 SMP Sun May 13 07:51:23 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-2-686-pae root=UUID=5a0ffa6d-f75b-430d-af8d-a77bfe7214e8 ro quiet ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [7.603608] pcmcia_socket pcmcia_socket0: cs: memory probe 0xa000-0xa0ff: clean. [7.603652] pcmcia_socket pcmcia_socket0: cs: memory probe 0x6000-0x60ff: clean. [7.603695] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff: [7.604118] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x100-0x3af: excluding 0x170-0x177 0x1f0-0x1f7 0x2f8-0x2ff 0x370-0x377 [7.605167] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x3e0-0x4ff: excluding 0x3f0-0x3ff 0x4d0-0x4d7 [7.605614] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x820-0x8ff: clean. [7.605989] pcmcia_socket pcmcia_socket1: cs: IO port probe 0xc00-0xcf7: clean. [7.606403] pcmcia_socket pcmcia_socket1: cs: memory probe 0x0c-0x0f: excluding 0xc-0xc 0xdc000-0xf [7.606446] pcmcia_socket pcmcia_socket1: cs: memory probe 0xa000-0xa0ff: clean. [7.606489] pcmcia_socket pcmcia_socket1: cs: memory probe 0x6000-0x60ff: clean. [7.606532] pcmcia_socket pcmcia_socket1: cs: IO port probe 0xa00-0xaff: clean. [7.607649] clean. [7.649423] lib80211: common routines for IEEE802.11 drivers [7.649428] lib80211_crypt: registered algorithm 'NULL' [7.818737] libipw: 802.11 data/management/control stack, git-1.1.13 [7.818742] libipw: Copyright (C) 2004-2005 Intel Corporation jketr...@linux.intel.com [7.906101] snd_intel8x0m :00:1f.6: PCI INT B - Link[LNKB] - GSI 5 (level, low) - IRQ 5 [7.906126] snd_intel8x0m :00:1f.6: setting latency timer to 64 [7.958170] snd_intel8x0 :00:1f.5: PCI INT B - Link[LNKB] - GSI 5 (level, low) - IRQ 5 [7.958206] snd_intel8x0 :00:1f.5: setting latency timer to 64 [7.967983] ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, git-1.2.2 [7.967987] ipw2100: Copyright(c) 2003-2006 Intel Corporation [7.968149] ipw2100 :02:02.0: PCI INT A - Link[LNKC] - GSI 11 (level, low) - IRQ 11 [7.968982] ipw2100: Detected Intel PRO/Wireless 2100 Network Connection [8.380944] cfg80211: failed to add phy80211 symlink to netdev! [8.884045] intel8x0_measure_ac97_clock: measured 55399 usecs (2669 samples) [8.884050] intel8x0: clocking to 48000 [9.030209] cfg80211: World regulatory domain updated: [9.030215] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [
Bug#673705: network-manager: Network Manager doesn't connect to wifi (greyed out) when device cannot report signal strength
Package: network-manager Version: 0.9.4.0-4 Severity: normal If a wireless network card isn't able to report signal strength Network Manager no longer allows connectiong to wifi networks. This was not so in previous versions. All available wireless networks are greyed out. This is due to the fact that the wifi adapter doesn't know how to report signal strength. Connecting through other adapters (external USB) is possible. In particular #iwlist eth1 scan eth1 Scan completed : Cell 01 - Address: 02:18:F8:7A:4E:5E ESSID:eduroam Protocol:IEEE 802.11bg Mode:Master Frequency:2.412 GHz (Channel 1) Encryption key:on Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s 11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s 48 Mb/s; 54 Mb/s Quality:64 Signal level:0 Noise level:0 IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : 802.1x Extra: Last beacon: 248ms ago and /var/log/syslog has the following line: wpa_supplicant[1826]: bgscan simple: Failed to enable signal strength monitoring There are many cards that have this problem, and I do not see any reason to grey out wifi networks that are reported by iwlist eth1 scan. If a network is reported one can want to try to connect to it. Greying out is useless, IMHO. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages network-manager depends on: ii adduser3.113+nmu2 ii dbus 1.5.12-1 ii dpkg 1.16.3 ii isc-dhcp-client4.2.2.dfsg.1-5 ii libc6 2.13-32 ii libdbus-1-31.5.12-1 ii libdbus-glib-1-2 0.98-1 ii libgcrypt111.5.0-3 ii libglib2.0-0 2.32.3-1 ii libgnutls262.12.19-1 ii libgudev-1.0-0 175-3.1 ii libnl-3-2003.2.7-2 ii libnl-genl-3-200 3.2.7-2 ii libnl-route-3-200 3.2.7-2 ii libnm-glib40.9.4.0-4 ii libnm-util20.9.4.0-4 ii libpolkit-gobject-1-0 0.105-1 ii libuuid1 2.20.1-4 ii lsb-base 4.1+Debian4 ii udev 175-3.1 ii wpasupplicant 1.0-2 Versions of packages network-manager recommends: ii crda 1.1.2-1 ii dnsmasq-base 2.61-1 ii iptables 1.4.13-1.1 ii modemmanager 0.5.2.0-1 ii policykit-1 0.105-1 ii ppp 2.4.5-5.1 Versions of packages network-manager suggests: ii avahi-autoipd 0.6.31-1 -- Configuration Files: /etc/NetworkManager/NetworkManager.conf changed: [main] plugins=ifupdown,keyfile no-auto-default=00:0d:60:89:e5:28, [ifupdown] managed=false -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#673705: [Pkg-utopia-maintainers] Bug#673705: network-manager: Network Manager doesn't connect to wifi (greyed out) when device cannot report signal strength
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 02:02.0 Network controller: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04) and the driver is the kernel module ipw2100 I already told them about this and they say it is a hardware/firmware limitation and they aren't sure it is fixable. On 05/20/2012 11:06 PM, Michael Biebl wrote: On 20.05.2012 22:55, Gennady N. Uraltsev wrote: There are many cards that have this problem, and I do not see any reason to Which card and driver do you use? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPuWP0AAoJEO4X3lPe3Y0x8U4P/jt+3uLpm+WyXgLs/7si8S/T WwZ66Rdf/CTEFxx7yBYKefY8ym0P0JDtakpo71ckn6jVkY8/2cBFizU5cNLkWQIF juAndmvy/7p/NBLvFkx3F8k8kD+JP6wk2HZx+XuQzDQopAQtp1/vcnSmdUfWSkTU rNFP9xCcTIbPksFFhIz9XO/7cWFlsUEvwCsgxiXlViMf5Bt+vMd9acFdJlK6WnZ1 FvOtSXIwv+TfQvC4yMzuK5QRDFnckY6ecnU4Kif8O2JOiZRJvl/R/6vROAgFmuvj 4RWuU1Vm1qSJEHxVP1uouBrrU/6vpX6qLF4RrshuYNaRkWxiY2D0054xjZX+ETq+ CgEw9CASjfmMRuH35OUia19y3D7q+v923Iwyd23WWLUGMGjl+BaA7+M+3xlD/7M9 eRAn5vA4+H+lqaITNkDGLGavJakWH7BYBrtrXZhUDeKWK/NX6BEGLOH22Xzrtkjm XgyRuwhu0p0Q0ZlY4WM3vxT63CHmmuO7QghAvtJaslDPOSFBu+d7jJ8GU/Jt//CR UdP22zoqEl0nzEcpQIcUvexpM2LbQg5OR1vk3yP6IQFiVOeR1dO5lxuXwUBEVPOe 91T6eAkqRZuqgcgOF6v+yQCSCVEOTGj0nppvywlzjaE14DcKF9/RSmWkp4sjDNkw 5lBsIOqWVF9UDXUpmVgC =rnK/ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#664725: Info received (linux-image-3.2.0-2-rt-686-pae: Real-time kernel freezes immediately at boot most of the time)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello everyone, Sorry for the delay but I have not yet found a way to get the debug messages. I disabled the quiet option but there are some problems with saving the debug messages. Netconsole starts too late and I do not have a serial port. I will try to take a photo and to copy the info that gets displayed. However I wanted to tell you that I found out that the problem disappears if the grub option set gfxpayload=keep is removed, aka the framebuffer mode is not used. Will write more about this tomorrow. BTW I upgraded the kernel to the latest one available in sid: Package: linux-image-3.2.0-2-rt-686-pae New: yes State: installed Automatically installed: yes Version: 3.2.14-1 and the problem is still there. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPhhq4AAoJEO4X3lPe3Y0xlrYQANon/yxooIHjAZanAdA+7juz Lt9NOWAr9jAiNGoG9EQq2Xp6eBYle4ludC/rOKN9U45ZPip7cpUklB7lZ5wGvJZ+ TWe098RZ/cDNq/oTTjHfN7wmgu31ldLkMGYJQi42DIr94DAWlGKgEDqB8e3egiaD 3NGn9r0iO2v9oc5xIoBOyCVgHJZqFecemWBrNZHeBOZUMENTHihvWoa3W08bw/PG pTIhK3sHTnM4tgzvW1Y8416TkXYQoGXuN76vAFgMqKjS9la02QWxHxDJ998hG9GR LDLDnQMNFLY8OEiBZ6kZvJO6f7zenLp395ta41ptAPnJEVox/FrPVwIzANOl2dV9 HAaAoOzqLbbjYkL7lKotb9nvXBZ3Gktyab4acmjNCHTKNfEU1anxbdD75Lfwx5oe JfWrFxqY7yYj2KUTmGlH+AXLks90oSicPwI91W2SG0Ewz+E4BCMcZs+r7spRSGOx umDX1E5Psy0RWgVuzJaiAg3fD1PuY8LNyuOx7gHC6kuw/AhceB0nNB1fj4nI5/ae 6IBvD6XZSKha8Xir7qcsPRuchibk4Psv8s3+y3EPTpUzSvkP0Ryvb2q4AWmbeH+D mJtwePSYQSRhPGxE6rKze1D4jlCoa0H4BXbUrTI4gnQNmAXcqvI3YQ7TDLl1Tt4X nnYntJCRvL1U2wJXLzJI =8WDT -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#667729: network-manager-gnome: Protected wireless networks are greyed out. Unable to connect through applet.
Package: network-manager-gnome Version: 0.9.4.1-1 Severity: important When clicking on the nm applet the wireless networks whose signal is present are presented in a list but all the entries for protected networks are greyed out and thus unclickable. The only way I found to connect to a protected network is to manually go to Edit Connections and add a wireless connection with the correct SSID and password. This does NOT make the list entry clickable, no matter what settings one chooses for the option make available to all users. Finally, after setting up a connection this way, from root I do: /etc/init.d/network-manager restart then the network-manager restarts and by default connects to the wireless network. However this is a very dirty workaround and because of this network- manager is essentially unusable for managing wireless networks. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages network-manager-gnome depends on: ii dbus-x11 1.5.12-1 ii dpkg 1.16.2 ii gconf-service3.2.3-4 ii gconf2 3.2.3-4 ii gnome-icon-theme 3.4.0-2 ii libatk1.0-0 2.4.0-2 ii libc62.13-27 ii libcairo-gobject21.12.0-2 ii libcairo21.12.0-2 ii libdbus-1-3 1.5.12-1 ii libdbus-glib-1-2 0.98-1 ii libfontconfig1 2.8.0-3.1 ii libfreetype6 2.4.9-1 ii libgconf-2-4 3.2.3-4 ii libgdk-pixbuf2.0-0 2.26.0-2 ii libglib2.0-0 2.32.0-3 ii libgnome-bluetooth8 3.2.2-1 ii libgnome-keyring03.4.0-1 ii libgtk-3-0 3.2.3-1 ii libnm-glib-vpn1 0.9.4.0-3 ii libnm-glib4 0.9.4.0-3 ii libnm-gtk0 0.9.4.1-1 ii libnm-util2 0.9.4.0-3 ii libnotify4 0.7.5-1 ii libpango1.0-01.30.0-1 ii network-manager 0.9.4.0-3 ii policykit-1-gnome0.105-2 Versions of packages network-manager-gnome recommends: ii gnome-bluetooth3.2.2-1 ii iso-codes 3.34-1 ii libpam-gnome-keyring [libpam-keyring] 3.2.2-2 ii mobile-broadband-provider-info 20120402-1 ii notification-daemon0.7.4-1 ii xfce4-notifyd [notification-daemon]0.2.2-1 Versions of packages network-manager-gnome suggests: ii network-manager-openvpn-gnome 0.9.4.0-1 ii network-manager-pptp-gnome 0.9.4.0-2 ii network-manager-vpnc-gnome 0.9.4.0-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#667729: [Pkg-utopia-maintainers] Bug#667729: network-manager-gnome: Protected wireless networks are greyed out. Unable to connect through applet.
This is the output of ck-list-sessions: Session6: unix-user = '1000' realname = 'Gennady N. Uraltsev' seat = 'Seat1' session-type = '' active = TRUE x11-display = ':0' x11-display-device = '/dev/tty7' display-device = '' remote-host-name = '' is-local = TRUE on-since = '2012-04-06T12:42:41.925371Z' login-session-id = '' On 04/06/2012 02:20 PM, Michael Biebl wrote: On 06.04.2012 12:08, Gennady N. Uraltsev wrote: When clicking on the nm applet the wireless networks whose signal is present are presented in a list but all the entries for protected networks are greyed out and thus unclickable. The only way I found to connect to a protected network is to manually go to Edit Connections and add a wireless connection with the correct SSID and password. This does NOT make the list entry clickable, no matter what settings one chooses for the option make available to all users. Finally, after setting up a connection this way, from root I do: /etc/init.d/network-manager restart then the network-manager restarts and by default connects to the wireless network. However this is a very dirty workaround and because of this network- manager is essentially unusable for managing wireless networks. What's the output of ck-list-sessions? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#664725: linux-image-3.2.0-2-rt-686-pae: Real-time kernel freezes immediately at boot most of the time
Package: linux-2.6 Version: 3.2.10-1 Severity: important Tags: lfs When trying to boot the 3.2.0-2-rt-686 kernel on my machine it freezes most of the time. In particular just after grub finishes loading the kernel and the initrd and proceeds to boot the kernel the message Loading Linux or something of that sort appears, the cursor blinks a couple of times (so far everything as usual) but then the cursor stops blinking and disappears completely and the system is completely unresponsive. Caps Lock, alt+sysrq+... and other keys don't have any effect. Normally, the message that appears immediately after this on my pc, when a normal kernel is run, is a debug message from udev (I think) described in: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654282 but that is NOT fatal and is present on all kernels (even the non rt ones). However in this case nothing of the sort is displayed. This problem seems very similar to the one in bug report 63269: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663269 that has been said to be fixed. As a matter of fact I have noticed one difference: with version 3.2.10-1 (current), if I load a normal, non-rt kernel first then restart my pc and load the rt kernel the machine usually starts and doesn't hang and works perfectly, while normally (for example running the rt kernel for two times in a row) causes the machine to freeze. On the other hand, with version 3.2.9-1 there was absolutely nothing to be done to make the machine boot with the rt-kernel. This strange behaviour makes me suspect that something may depend on the way grub is booting the kernel (maybe some options that persist across boots). However I have no idea how to debug this. If someone gives me some hints I would be willing to provide any additional information. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information not available ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 82855PM Processor to I/O Controller [8086:3340] (rev 03) Subsystem: IBM Thinkpad T40 series [1014:0529] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Region 0: Memory at d000 (32-bit, prefetchable) [size=256M] Capabilities: access denied Kernel driver in use: agpgart-intel 00:01.0 PCI bridge [0604]: Intel Corporation 82855PM Processor to AGP Controller [8086:3341] (rev 03) (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- TAbort- MAbort- SERR- PERR- INTx- Latency: 96 Bus: primary=00, secondary=01, subordinate=01, sec-latency=64 I/O behind bridge: 3000-3fff Memory behind bridge: c010-c01f Prefetchable memory behind bridge: e000-e7ff Secondary status: 66MHz+ FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR- BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- 00:1d.0 USB controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 [8086:24c2] (rev 01) (prog-if 00 [UHCI]) Subsystem: IBM ThinkPad [1014:052d] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 11 Region 4: I/O ports at 1800 [size=32] Kernel driver in use: uhci_hcd 00:1d.1 USB controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 [8086:24c4] (rev 01) (prog-if 00 [UHCI]) Subsystem: IBM ThinkPad [1014:052d] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin B routed to IRQ 11 Region 4: I/O ports at 1820 [size=32] Kernel driver in use: uhci_hcd 00:1d.2 USB controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 [8086:24c7] (rev 01) (prog-if 00 [UHCI]) Subsystem: IBM ThinkPad [1014:052d] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin C routed to IRQ 11 Region 4: I/O ports at 1840 [size=32] Kernel driver in use: uhci_hcd 00:1d.7
