Bug#465278: appletouch failure still present with linux-image-2.6.32-trunk-powerpc
Package: linux-2.6 Version: 2.6.32-1 Severity: normal All, I can confirm appletouch failure on resume is still an issue with current kernels. Mark -- Package-specific info: ** Version: Linux version 2.6.32-trunk-powerpc (Debian 2.6.32-1) (wa...@debian.org) (gcc version 4.3.4 (Debian 4.3.4-6) ) #1 Mon Dec 7 20:54:08 UTC 2009 ** Command line: root=/dev/hda3 ro ** Not tainted ** Kernel log: [ 89.923896] radeonfb :00:10.0: restoring config space at offset 0x1 (was 0x2b0, writing 0x2b7) [ 89.923953] b43-pci-bridge 0001:10:12.0: restoring config space at offset 0x4 (was 0x0, writing 0x80084000) [ 89.923966] b43-pci-bridge 0001:10:12.0: restoring config space at offset 0x3 (was 0x0, writing 0x1000) [ 89.923979] b43-pci-bridge 0001:10:12.0: restoring config space at offset 0x1 (was 0x0, writing 0x6) [ 89.926085] ohci_hcd 0001:10:1b.0: restoring config space at offset 0x1 (was 0x210, writing 0x212) [ 89.926131] ohci_hcd 0001:10:1b.1: restoring config space at offset 0x1 (was 0x210, writing 0x212) [ 89.926178] ehci_hcd 0001:10:1b.2: restoring config space at offset 0x1 (was 0x210, writing 0x2100012) [ 89.941872] radeonfb (:00:10.0): resuming from state: 2... [ 90.649704] agpgart-uninorth :00:0b.0: putting AGP V2 device into 4x mode [ 90.649719] radeonfb :00:10.0: putting AGP V2 device into 4x mode [ 91.833675] eth0: resuming [ 91.898014] PHY ID: 4061e4, addr: 0 [ 93.162797] hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4 [ 93.167860] adb: starting probe task... [ 93.169840] hda: UDMA/100 mode selected [ 93.172562] hdc: host max PIO4 wanted PIO255(auto-tune) selected PIO4 [ 93.172701] hdc: MWDMA2 mode selected [ 93.192932] adb devices: [2]: 2 c4 [7]: 7 1f [ 93.197909] ADB keyboard at 2, handler 1 [ 93.197916] adb: finished probe task... [ 93.601673] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10) [ 93.645236] Restarting tasks ... done. [ 94.222604] agpgart-uninorth :00:0b.0: putting AGP V2 device into 4x mode [ 94.222620] radeonfb :00:10.0: putting AGP V2 device into 4x mode [ 94.222729] [drm] Num pipes: 1 [ 108.373268] PM: Syncing filesystems ... done. [ 108.710960] [drm] Num pipes: 1 [ 109.035052] Freezing user space processes ... (elapsed 0.04 seconds) done. [ 109.078025] Freezing remaining freezable tasks ... (elapsed 0.61 seconds) done. [ 109.691113] Suspending console(s) (use no_console_suspend to debug) [ 109.730713] btusb_intr_complete: hci0 urb deadcb00 failed to resubmit (1) [ 109.731682] btusb_bulk_complete: hci0 urb deadc480 failed to resubmit (1) [ 109.732681] btusb_bulk_complete: hci0 urb deadcc80 failed to resubmit (1) [ 110.149261] eth0: suspending, WakeOnLan disabled [ 110.225768] radeonfb (:00:10.0): suspending for event: 2... [ 110.225829] agpgart-uninorth :00:0b.0: disabling AGP on device :00:10.0 [ 110.225863] agpgart-uninorth :00:0b.0: disabling AGP on bridge [ 110.725476] radeonfb :00:10.0: restoring config space at offset 0xc (was 0x0, writing 0x90020001) [ 110.725497] radeonfb :00:10.0: restoring config space at offset 0x6 (was 0x0, writing 0x9000) [ 110.725510] radeonfb :00:10.0: restoring config space at offset 0x5 (was 0x1, writing 0x401) [ 110.725522] radeonfb :00:10.0: restoring config space at offset 0x4 (was 0x8, writing 0x9808) [ 110.725534] radeonfb :00:10.0: restoring config space at offset 0x3 (was 0x0, writing 0xff08) [ 110.725547] radeonfb :00:10.0: restoring config space at offset 0x1 (was 0x2b0, writing 0x2b7) [ 110.725603] b43-pci-bridge 0001:10:12.0: restoring config space at offset 0x4 (was 0x0, writing 0x80084000) [ 110.725616] b43-pci-bridge 0001:10:12.0: restoring config space at offset 0x3 (was 0x0, writing 0x1000) [ 110.725630] b43-pci-bridge 0001:10:12.0: restoring config space at offset 0x1 (was 0x0, writing 0x6) [ 110.727734] ohci_hcd 0001:10:1b.0: restoring config space at offset 0x1 (was 0x210, writing 0x212) [ 110.727780] ohci_hcd 0001:10:1b.1: restoring config space at offset 0x1 (was 0x210, writing 0x212) [ 110.727826] ehci_hcd 0001:10:1b.2: restoring config space at offset 0x1 (was 0x210, writing 0x2100012) [ 110.743508] radeonfb (:00:10.0): resuming from state: 2... [ 111.451338] agpgart-uninorth :00:0b.0: putting AGP V2 device into 4x mode [ 111.451353] radeonfb :00:10.0: putting AGP V2 device into 4x mode [ 112.635303] eth0: resuming [ 112.699648] PHY ID: 4061e4, addr: 0 [ 114.857567] hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4 [ 114.862359] adb: starting probe task... [ 114.863318] hda: UDMA/100 mode selected [ 114.865972] hdc: host max PIO4 wanted PIO255(auto-tune) selected PIO4 [ 114.866109] hdc: MWDMA2 mode selected [ 114.888174] adb devices: [2]: 2 c4 [7]: 7 1f [ 114.893168] ADB keyboard at 2, handler 1 [ 114.893176] adb: finished probe task... [
Re: Bug#520763: hwclock: NVRAM flat battery sets date to 1904
On Sunday 17 May 2009 03:18:10 Jörg Sommer wrote: I would much more prefer to get prompted for the correct time, because with a wrong time fsck fail due to the last fsck is in the future. But I don't know how to do prompting in init scripts correctly. I did think about this, but didn't go this way for a couple of reasons. . I just want to get the time/date into the correct year so that things like kdm/ gdm will startup. Otherwise the user is presented with a console login which doesn't pass the WAF. I have been asked a number of times by the other half over the phone what does she do when the screen is black and just says $ with a flashing cursor :-( . I have ntpdate set so when the network interface is brought up, we then sync to exact time. Much more precise than asking the user the time. . I don't think you are allowed to block for input with the init.d scripts. That said I can see merit in asking the user the time, especially if you aren't going to connect to the network soon.. And to guess if the hardware clock is wrong I think we can look at the installation time of the module directory of the kernel. /boot/vmlinux-$(uname -r) is possible, too. Yes, I'm surprised that a warning isn't set off if the time is set to the date before the kernel was complied. Mark signature.asc Description: This is a digitally signed message part.
hwclock: NVRAM flat battery sets date to 1904
retitle 520763 hwclock: NVRAM flat battery sets date to 1904
severity important
tags 520763 patch
thanks
This is a common problem on powerpc ibook's once the NVRAM battery goes flat.
Apparently this has been discussed with upstream:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/23426/comments/18
Mark
This patch is a quick hack, but you get the idea:
--- hwclockfirst.sh.orig2009-05-16 14:26:54.0 +1000
+++ hwclockfirst.sh 2009-05-16 14:23:11.0 +1000
@@ -38,6 +38,12 @@
. /lib/lsb/init-functions
verbose_log_action_msg() { [ $VERBOSE = no ] || log_action_msg $@; }
+if `/sbin/hwclock | /bin/grep -q 1904`; then
+ log_warning_msg NVRAM Battery Clock flat (date 1904)
+ log_action_msg Setting hwclock date to 2009-5-16
+ hwclock --set --date 2009-5-16
+fi
+
[ $GMT = -u ] UTC=yes
case $UTC in
no|) GMT=--localtime
signature.asc
Description: This is a digitally signed message part.
suspend/ resume with kernel 2.4.26??
Can I query what people are using for suspend resume on powerpc with kernel 2.4.26? I have an ibook G4 and since the introduction of 2.4.2x I find that neither apm/ acpi nor are the tools available to support these actions. The last 'good' kernel was 2.4.18. Am I alone, or are others on powerpc seeing similar issues? Mark signature.asc Description: This is a digitally signed message part.
Bug#465278: Mouse freeze fixed in linux-2.6 (2.6.24-4)
Package: linux-image-2.6.24-1-powerpc Followup-For: Bug #465278 I am seeing the mouse freeze issue has gone away with 2.6.24-4. Anyone else getting the same results. Mark -- Package-specific info: ** Version: Linux version 2.6.24-1-powerpc (Debian 2.6.24-4) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080114 (prerelease) (Debian 4.1.2-19)) #1 Mon Feb 11 12:53:42 CET 2008 ** Command line: root=/dev/hda3 ro ** Not tainted ** Kernel log: usb 2-1: configuration #1 chosen from 1 choice cdc_acm 2-1:1.8: ttyACM0: USB ACM device usbcore: registered new interface driver cdc_acm drivers/usb/class/cdc-acm.c: v0.25:USB Abstract Control Model driver for USB modems and ISDN adapters usbcore: registered new interface driver cdc_ether usb 2-1: bad CDC descriptors usbcore: registered new interface driver rndis_host usb 2-1: USB disconnect, address 7 usb 2-1: new full speed USB device using ohci_hcd and address 8 usb 2-1: configuration #1 chosen from 1 choice scsi0 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 8 usb-storage: waiting for device to settle before scanning usb-storage: device scan complete scsi 0:0:0:0: Direct-Access NokiaS60 1.0 PQ: 0 ANSI: 0 Driver 'sd' needs updating - please use bus_type methods sd 0:0:0:0: [sda] 996352 512-byte hardware sectors (510 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00 sd 0:0:0:0: [sda] Assuming drive cache: write through sd 0:0:0:0: [sda] 996352 512-byte hardware sectors (510 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00 sd 0:0:0:0: [sda] Assuming drive cache: write through sda: sd 0:0:0:0: [sda] Attached SCSI removable disk usb 2-1: USB disconnect, address 8 usb 2-1: new full speed USB device using ohci_hcd and address 9 usb 2-1: configuration #1 chosen from 1 choice scsi1 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 9 usb-storage: waiting for device to settle before scanning usb-storage: device scan complete scsi 1:0:0:0: Direct-Access NokiaS60 1.0 PQ: 0 ANSI: 0 sd 1:0:0:0: [sda] 996352 512-byte hardware sectors (510 MB) sd 1:0:0:0: [sda] Write Protect is off sd 1:0:0:0: [sda] Mode Sense: 03 00 00 00 sd 1:0:0:0: [sda] Assuming drive cache: write through sd 1:0:0:0: [sda] 996352 512-byte hardware sectors (510 MB) sd 1:0:0:0: [sda] Write Protect is off sd 1:0:0:0: [sda] Mode Sense: 03 00 00 00 sd 1:0:0:0: [sda] Assuming drive cache: write through sda: sd 1:0:0:0: [sda] Attached SCSI removable disk usb 2-1: USB disconnect, address 9 usb 2-1: new full speed USB device using ohci_hcd and address 10 usb 2-1: configuration #1 chosen from 1 choice cdc_acm 2-1:1.8: ttyACM0: USB ACM device usb 2-1: bad CDC descriptors wlan0_rename: deauthenticate(reason=3) ADDRCONF(NETDEV_UP): eth0: link is not ready input: b43-phy0 as /class/input/input19 Registered led device: b43-phy0:tx Registered led device: b43-phy0:rx Registered led device: b43-phy0:radio ADDRCONF(NETDEV_UP): wlan0_rename: link is not ready wlan0_rename: Initial auth_alg=0 wlan0_rename: authenticate with AP 00:13:10:17:be:4d wlan0_rename: RX authentication from 00:13:10:17:be:4d (alg=0 transaction=2 status=0) wlan0_rename: authenticated wlan0_rename: associate with AP 00:13:10:17:be:4d wlan0_rename: RX AssocResp from 00:13:10:17:be:4d (capab=0x401 status=0 aid=1) wlan0_rename: associated wlan0_rename: switched to short barker preamble (BSSID=00:13:10:17:be:4d) ADDRCONF(NETDEV_CHANGE): wlan0_rename: link becomes ready IN= OUT=wlan0_rename SRC=202.81.78.134 DST=202.83.82.162 LEN=76 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=123 DPT=123 LEN=56 IN= OUT=wlan0_rename SRC=202.81.78.134 DST=210.9.136.13 LEN=87 TOS=0x00 PREC=0x00 TTL=64 ID=54391 DF PROTO=TCP SPT=38307 DPT=143 WINDOW=2003 RES=0x00 ACK PSH URGP=0 IN= OUT=wlan0_rename SRC=192.168.1.205 DST=203.2.193.67 LEN=61 TOS=0x00 PREC=0x00 TTL=64 ID=55149 DF PROTO=UDP SPT=59595 DPT=53 LEN=41 IN= OUT=wlan0_rename SRC=192.168.1.205 DST=202.135.30.4 LEN=61 TOS=0x00 PREC=0x00 TTL=64 ID=55149 DF PROTO=UDP SPT=49503 DPT=53 LEN=41 IN= OUT=wlan0_rename SRC=192.168.1.205 DST=203.2.193.67 LEN=61 TOS=0x00 PREC=0x00 TTL=64 ID=55170 DF PROTO=UDP SPT=60325 DPT=53 LEN=41 IN= OUT=wlan0_rename SRC=192.168.1.205 DST=202.135.30.4 LEN=61 TOS=0x00 PREC=0x00 TTL=64 ID=55170 DF PROTO=UDP SPT=49248 DPT=53 LEN=41 IN= OUT=wlan0_rename SRC=192.168.1.205 DST=203.2.193.67 LEN=61 TOS=0x00 PREC=0x00 TTL=64 ID=55172 DF PROTO=UDP SPT=39660 DPT=53 LEN=41 IN= OUT=wlan0_rename SRC=192.168.1.205 DST=202.135.30.4 LEN=61 TOS=0x00 PREC=0x00 TTL=64 ID=55172 DF PROTO=UDP SPT=44625 DPT=53 LEN=41 IN= OUT=wlan0_rename SRC=192.168.1.205 DST=203.2.193.67 LEN=80 TOS=0x00 PREC=0x00 TTL=64 ID=55192 DF PROTO=UDP SPT=55141 DPT=53 LEN=60 IN= OUT=wlan0_rename SRC=192.168.1.205 DST=202.135.30.4 LEN=80 TOS=0x00 PREC=0x00 TTL=64 ID=55192 DF PROTO=UDP SPT=59996 DPT=53 LEN=60 IN= OUT=wlan0_rename SRC=192.168.1.205 DST=203.2.193.67
Bug#387903: [powerpc] bcm43xx module (802.11) wireless issues with 2.6.17-9 - iBook G4
Package: linux-image-2.6.17-2-powerpc Version: 2.6.17-9 Severity: important Since upgrading to 2.6.17-9, running on an ibook G4 with the Broadcomm 4318 wireless there are issues with the kernel supplied bcm43xx module. Reverting to 2.6.17-8 (from testing) and the bcm43xx module operates as expected. The problems I am seeing with -9 include, not being able to associate with an access point, or when I am associated the connection is unreliable and drops out. bcm43xx is a new module in the kernel and I anticipate these are some teething issues, but wanted to let people know which versions of the kernel I have found to work. Can anyone else from debian-powerpc confirm or otherwise issues with bcm43xx and 2.6.17-9 version of the kernel. I find that the 2.6.16 kernel support for the bcm43xx isn't great, but did have success with 2.6.15 kernels and the no defunt bcm43xx-source package. Mark 0001:10:12.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02) -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-powerpc Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages linux-image-2.6.17-2-powerpc depends on: ii initramfs-tools [linux-initra 0.79 tools for generating an initramfs ii mkvmlinuz 23 create a kernel to boot a PowerPC ii module-init-tools 3.2.2-3tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.12-18 Yet Another mkInitRD linux-image-2.6.17-2-powerpc recommends no packages. -- debconf information: shared/kernel-image/really-run-bootloader: true linux-image-2.6.17-2-powerpc/postinst/create-kimage-link-2.6.17-2-powerpc: true linux-image-2.6.17-2-powerpc/preinst/initrd-2.6.17-2-powerpc: linux-image-2.6.17-2-powerpc/preinst/lilo-initrd-2.6.17-2-powerpc: true * linux-image-2.6.17-2-powerpc/preinst/already-running-this-2.6.17-2-powerpc: linux-image-2.6.17-2-powerpc/preinst/abort-overwrite-2.6.17-2-powerpc: linux-image-2.6.17-2-powerpc/prerm/removing-running-kernel-2.6.17-2-powerpc: true linux-image-2.6.17-2-powerpc/postinst/really-run-bootloader-2.6.17-2-powerpc: true linux-image-2.6.17-2-powerpc/preinst/elilo-initrd-2.6.17-2-powerpc: true linux-image-2.6.17-2-powerpc/postinst/depmod-error-2.6.17-2-powerpc: false linux-image-2.6.17-2-powerpc/postinst/kimage-is-a-directory: linux-image-2.6.17-2-powerpc/preinst/abort-install-2.6.17-2-powerpc: linux-image-2.6.17-2-powerpc/postinst/old-dir-initrd-link-2.6.17-2-powerpc: true linux-image-2.6.17-2-powerpc/postinst/old-system-map-link-2.6.17-2-powerpc: true linux-image-2.6.17-2-powerpc/postinst/bootloader-test-error-2.6.17-2-powerpc: linux-image-2.6.17-2-powerpc/preinst/overwriting-modules-2.6.17-2-powerpc: true linux-image-2.6.17-2-powerpc/postinst/bootloader-error-2.6.17-2-powerpc: linux-image-2.6.17-2-powerpc/preinst/bootloader-initrd-2.6.17-2-powerpc: true linux-image-2.6.17-2-powerpc/postinst/old-initrd-link-2.6.17-2-powerpc: true linux-image-2.6.17-2-powerpc/preinst/lilo-has-ramdisk: linux-image-2.6.17-2-powerpc/prerm/would-invalidate-boot-loader-2.6.17-2-powerpc: true linux-image-2.6.17-2-powerpc/preinst/failed-to-move-modules-2.6.17-2-powerpc: linux-image-2.6.17-2-powerpc/postinst/depmod-error-initrd-2.6.17-2-powerpc: false -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RM: bcm43xx
Rene, I understand why bcm43xxx has been removed from the debian archive. However I would like to raise the point that I actually get better results with the last bcm43xxx modules which were in unstable and 2.6.16, rather than 2.6.17, which crashes on me.. Also I note that the target kernel for etch beta 3 installer is 2.6.16 http://lists.debian.org/debian-powerpc/2006/06/msg00219.html Mark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RM: bcm43xx
On Wednesday 05 July 2006 22:09, Mark Purcell wrote: However I would like to raise the point that I actually get better results with the last bcm43xxx modules which were in unstable and 2.6.16, rather than 2.6.17, which crashes on me.. Sorry, s/2.6.16/2.6.15/ Mark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#376965: bcm43xx: ASSERTION FAILED (radio_attenuation 10)
Package: linux-image-2.6.17-1-powerpc
Version: 2.6.17-2
Severity: minor
File:
/lib/modules/2.6.17-1-powerpc/kernel/drivers/net/wireless/bcm43xx/bcm43xx.ko
In debian-powerpc, I stated I was having some issues with the airport
driversi in the 2.6.17 kernel.
Here is the bug report to followup on these issues:
There are a number of issues with the bcm43xx driver, most/ all of which
have nothing todo with the Debian packaging, but are rather functions of
the maturity of the driver.
The driver doesn't appear to function well at 54Mbps, but gives good
results when forced down to 11Mbps.
To force 11Mbps I use the following network/interfaces:
$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo eth1
iface lo inet loopback
iface eth1 inet static
address 192.168.1.200
network 192.168.1.0
netmask 255.255.255.0
gateway 192.168.1.150
broadcast 192.168.1.255
post-up iwconfig eth1 rate 11M
post-up iwconfig eth1 essid pos
When coming out of hibernation mode, unfortunatly the driver
defaults back to 54Mbs, which doesn't work well. Initially, I
thought the above network/interfaces would be sufficient to reset
to 11Mbps after sleep, but it would appear the it isn't so I had to do
futher modifications:
--- /usr/lib/powersave/scripts/sleep_helper_functions 2006-05-26
22:16:19.0 +0100
+++ /usr/lib/powersave/scripts/sleep_helper_functions.ibook
2006-05-19 08:34:21.0 +0100
@@ -496,6 +496,7 @@
echo $LSMOD_LOG
echo Restarting services: $LSMOD_LOG
+/etc/init.d/networking restart 21 | awk '{print ## $0}'
$LSMOD_LOG
### S t a r t S e r v i c e s (but not hotplug or
boot.hotplug) ##
if [ $SERVICES_TO_RESTART -a -s ${STATE}.resume ]; then
for X in `tac ${STATE}.resume | awk '/^stopped:/ { if
(($2!=hotplug)($2!=boot.hotplug)) print $2 }'`; do
Note that this isn't a conffile so everytime powersaved is upgraded
this change needs to be made.
Finially now that we have migrated to the native kernel bcm43xx, it
reports the following errors on loading. The Call Trace's scare me a
bit, but performance seems OK:
$ dmesg
[...]
Uniform CD-ROM driver Revision: 3.20
bcm43xx driver
PCI: Enabling device 0001:10:12.0 (0004 - 0006)
bcm43xx: Chip ID 0x4318, rev 0x2
bcm43xx: Number of cores: 4
bcm43xx: Core 0: ID 0x800, rev 0xd, vendor 0x4243, enabled
bcm43xx: Core 1: ID 0x812, rev 0x9, vendor 0x4243, disabled
bcm43xx: Core 2: ID 0x804, rev 0xc, vendor 0x4243, enabled
bcm43xx: Core 3: ID 0x80d, rev 0x7, vendor 0x4243, enabled
bcm43xx: PHY connected
bcm43xx: Detected PHY: Version: 3, Type 2, Revision 7
bcm43xx: Detected Radio: ID: 8205017f (Manuf: 17f Ver: 2050 Rev: 8)
bcm43xx: Radio turned off
bcm43xx: Radio turned off
ieee1394: Host added: ID:BUS[0-00:1023] GUID[001451fffe21844e]
[...]
bcm43xx: PHY connected
bcm43xx: Radio turned on
bcm43xx: ASSERTION FAILED (radio_attenuation 10) at:
drivers/net/wireless/bcm43xx/bcm43xx_phy.c:1485:bcm43xx_find_lopair()
bcm43xx: WARNING: Writing invalid LOpair (low: 49, high: 64, index: 130)
Call Trace:
[C1E4FC20] [C00078AC] show_stack+0x54/0x174 (unreliable)
[C1E4FC50] [E2511CA8] bcm43xx_phy_lo_adjust+0x2f0/0x310 [bcm43xx]
[C1E4FC70] [E2509050] bcm43xx_radio_set_txpower_bg+0x288/0x29c [bcm43xx]
[C1E4FC90] [E2510B9C] bcm43xx_phy_initb6+0x75c/0x8b8 [bcm43xx]
[C1E4FCB0] [E2512814] bcm43xx_phy_initg+0x130/0xe60 [bcm43xx]
[C1E4FD20] [E2513C3C] bcm43xx_phy_init+0x6f8/0x730 [bcm43xx]
[C1E4FD40] [E2503C8C] bcm43xx_wireless_core_init+0x880/0x1084 [bcm43xx]
[C1E4FDD0] [E250551C] bcm43xx_init_board+0x2d8/0x610 [bcm43xx]
[C1E4FE00] [C01A99BC] dev_open+0x64/0xc8
[C1E4FE20] [C01A8AC4] dev_change_flags+0x70/0x148
[C1E4FE40] [C01F1CBC] devinet_ioctl+0x288/0x6b0
[C1E4FEA0] [C01F2360] inet_ioctl+0xac/0xe0
[C1E4FEB0] [C019D640] sock_ioctl+0x230/0x26c
[C1E4FED0] [C0088400] do_ioctl+0x38/0x84
[C1E4FEE0] [C00887DC] vfs_ioctl+0x390/0x3c4
[C1E4FF10] [C0088878] sys_ioctl+0x68/0x98
[C1E4FF40] [C0010A24] ret_from_syscall+0x0/0x40
--- Exception: c01 at 0xff649f4
LR = 0xffed25c
bcm43xx: ASSERTION FAILED (radio_attenuation 10) at:
drivers/net/wireless/bcm43xx/bcm43xx_phy.c:1485:bcm43xx_find_lopair()
bcm43xx: WARNING: Writing invalid LOpair (low: 49, high: 64, index: 130)
Call Trace:
[C1E4FC60] [C00078AC] show_stack+0x54/0x174 (unreliable)
[C1E4FC90] [E2511CA8] bcm43xx_phy_lo_adjust+0x2f0/0x310 [bcm43xx]
[C1E4FCB0] [E25133E0] bcm43xx_phy_initg+0xcfc/0xe60 [bcm43xx]
[C1E4FD20] [E2513C3C] bcm43xx_phy_init+0x6f8/0x730 [bcm43xx]
[C1E4FD40] [E2503C8C] bcm43xx_wireless_core_init+0x880/0x1084 [bcm43xx]
[C1E4FDD0] [E250551C] bcm43xx_init_board+0x2d8/0x610 [bcm43xx]
[C1E4FE00] [C01A99BC] dev_open+0x64/0xc8
[C1E4FE20] [C01A8AC4] dev_change_flags+0x70/0x148
[C1E4FE40] [C01F1CBC] devinet_ioctl+0x288/0x6b0
[C1E4FEA0] [C01F2360] inet_ioctl+0xac/0xe0
[C1E4FEB0] [C019D640]
Fwd: Bug#147320: kmerlin: Cannot authenticate in PPC (Apple iBook)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 As I don't have PPC hardware I can't confirm this bug. Could I ask if anyone running powerpc has been able to get kmerlin running. If not could I ask that you try with kmerlin-1.0, so I can progress this bug. Thanks, Mark - -- Forwarded Message -- Subject: Bug#147320: kmerlin: Cannot authenticate in PPC (Apple iBook) Date: Sat, 18 May 2002 01:49:41 +0200 From: Ricardo Galli [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] Package: kmerlin Version: 1.0-1 Severity: important kmerlin doesn't work in PPC platform. It fails in authentication, altough there is no problem from a i386 (Sid also) and the same adsl connection (the router does nat). Create new connection to: Server: messenger.hotmail.com Port:1863 Host found! Sending protocol Sending server policy Sending initial Authentication Connecting to new Server: Server: 64.4.12.79 Port: 1863 Host found! Sending protocol Sending server policy Sending initial Authentication Sending response Authentication Idle detection enabled: true Timer: 15 set connected to: false Connection to MSN server closed! Idle detection enabled: true Timer: 15 set connected to: false Regards, - -- System Information Debian Release: 3.0 Architecture: powerpc Kernel: Linux sofi 2.4.19-pre7-ben0 #1 Sat May 4 16:23:54 CEST 2002 ppc Locale: LANG=es_ES, LC_CTYPE=es_ES Versions of packages kmerlin depends on: ii kdelibs3 4:2.2.2-13 KDE core libraries (runtime files) ii libc6 2.2.5-6GNU C Library: Shared libraries an ii libfam0 2.6.6.1-4 client library to control the FAM ii libjpeg62 6b-5 The Independent JPEG Group's JPEG ii libpng2 1.0.12-3 PNG library - runtime ii libqt23:2.3.1-22 Qt GUI Library (runtime version). ii libstdc++2.10-glibc2.21:2.95.4-9 The GNU stdc++ library ii xlibs 4.1.0-16 X Window System client libraries ii zlib1g1:1.1.4-1 compression library - runtime - --- -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE85dbwoCzanz0IthIRAlgVAJ9NgqbcGQvNxgLVssbm5YMvfNiC8ACfYoKS KNOc63R6MUW3vBB2H7pKOY0= =N83b -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
