Bug#550534: firmware-iwlwifi: iwlagn 0000:03:00.0: Microcode SW error detected., Restarting 0x82000000.
Hi everyone, I have the same problems, too. Debian squeeze runs on a Lenovo R61 with the following WLAN-NIC: 03:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61) uname -a Linux NBOOK 2.6.30-2-686 #1 SMP Fri Dec 4 00:53:20 UTC 2009 i686 GNU/Linux iwconfig wlan0 wlan0 IEEE 802.11abgn ESSID:tztztz Mode:Managed Frequency:2.462 GHz Access Point: xyzyzy Bit Rate=54 Mb/s Tx-Power=15 dBm Retry min limit:7 RTS thr:off Fragment thr:off Encryption key:blablabla Power Management:off Link Quality=70/70 Signal level=-27 dBm Noise level=-96 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 The WLAN-connection is secured with WPA-PSK. Before a new installation with squeeze I have used Debian stable with the default packages of the stable-branch. (firmware-iwlwifi-0.14). This installation runs daily without any problems about one year. About that past 12 months I have never lost the WLAN-connection. But after I have made a complete new installation with a squeeze-installation-CD the problem occurs. The problem couldn' t be reconstruct for example with more sessions at the same time or full bandwith downloads. Sending a kind of keep-alive by a ping to my access-point in a cronjob every minute doesn't fix the problem. I have made a downgrade and a upgrade to firmware-iwlwifi-0.14 (lenny) or firmware-iwlwifi-017 (0.17~bpo50+1_all) and firmware-iwlwifi-0.22 (sid) but unfortunately without any positive improvements. I think its rather a combination with and the firmware-iwlwifi (0.18) linux-image-2.6.30-2-686 (6.30-8squeeze1) packages. Greetings -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#487843: proftpd missing : after PID in the Logfile
Package: proftpd Version: 1.3.0-19 When proftpd protocols events in the logfile for example: /var/log/proftpd.log, the : isn't printed after the pid. Logfile: Jun 24 15:29:21 SERVER proftpd[28374] SERVER It should be: Jun 24 15:29:21 SERVER proftpd[28374]: SERVER Reason: I analyze automatically the proftpd-Logfile and the scanner doesn't work because he needs the : after the PID. Thanks a lot Joachim Krais -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#451230: linux-image-2.6-s390 / qeth - HSI-interface doesn't come up after reboot
severity 451230 normal tags 451230 moreinfo s390 never had automatic setup of devices. Please show your configuration. The debian installer sets up a configuration in /etc/sysconfig/hardware which lists all hardware devices which are used during the installation. Bastian --- Our HSI-NIC is integrated in the path /etc/sysconfig/hardware with config-ccw-0.0.0800. The only content in this file is: CCWGROUP_CHANS=(0.0.0800 0.0.0801 0.0.0802) Is this correct that the file has only one line? Excursion: == Sorry, we didn't describe our environment sufficiently. We running our Linux servers under Z/VM in different LPARs. The NICs and other hardware (DASDs) are defined in Z/VM for every guest (Linux). The physical hardware adapters so are mapped in virtual addresses. We aren't running Linux natively on a LPAR. We use these Linux-servers in a productive environment. At maintenance work (for example by a power on reset) we load the Linux guests from one LPAR (which will be maintained) to another LPAR. So we have the need that it works well. In SLES9 the HSI-NIC comes up while rebooting the linux-server by IPL from the Z/VM an we have our network connectivity. But we aren't happy about SLES10 and so we are looking for an alternative distribution. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#451224: linux-kernel-headers: qeth - HSI-interface doesn't come up after reboot
Package: linux-kernel-headers Version: 2.6.18 Severity: grave Hello together, we downloaded Debian4.0 and Debian4.0R1 and detected a bug with the network-interface. This bug exists in both releases. We use it on zSeries [architecture is s390]. The problem: If we reboot the system, the HSI network-interface won't automatically come up. We have to set them up manually in z/VM with echo 1 /sys/bus/ccwgroup/drivers/qeth/VIRTUAL_ADR_OF_DEVICE/online and modify the default-route, IP-address of the network-interface and reload the ssh daemon. Now we can connect again with putty. Our solution is a workaround: = We append /etc/init.d/network with the echo command at following position: ### END INIT INFO PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin ### Our workaround echo 1 /sys/bus/ccwgroup/drivers/qeth/VIRTUAL_ADR_OF_DEVICE/online [ -x /sbin/ifup ] || exit 0 Now the qeth Device comes up at (re)boot automatically and we can connect with putty to the server. Our question: = Is it possible to fix this problem? We use a lot of z/Linux servers with more than one network-interface and our workaround is not very efficient :-) Thanks a lot! Joachim Krais -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#451230: linux-image-2.6-s390 / qeth - HSI-interface doesn't come up after reboot
Package: linux-image-2.6-s390 Version: 2.6.18 Severity: grave Hello together, we downloaded Debian4.0 and Debian4.0R1 and detected a bug with the network-interface. This bug exists in both releases. We use it on zSeries [architecture is s390]. The problem: If we reboot the system, the HSI network-interface won't automatically come up. We have to set them up manually in z/VM with echo 1 /sys/bus/ccwgroup/drivers/qeth/VIRTUAL_ADR_OF_DEVICE/online and modify the default-route, IP-address of the network-interface and reload the ssh daemon. Now we can connect again with putty. Our solution is a workaround: = We append /etc/init.d/network with the echo command at following position: ### END INIT INFO PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin ### Our workaround echo 1 /sys/bus/ccwgroup/drivers/qeth/VIRTUAL_ADR_OF_DEVICE/online [ -x /sbin/ifup ] || exit 0 Now the qeth Device comes up at (re)boot automatically and we can connect with putty to the server. Our question: = Is it possible to fix this problem? We use a lot of z/Linux servers with more than one network-interface and our workaround is not very efficient ;-) Thanks a lot! Joachim Krais -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
