Bug#726398: linux: Fail to work with USB wifi dongle TP-Link TL-WN725N V2 (USB id 0bda:8179)
Package: src:linux Version: 3.2.51-1 Severity: normal Tags: upstream Dear Maintainer, I just bought a USB wifi dongle and it fail to work with the Linux kernel in Debian Stable/Wheezy. lsusb show this information about the device: Bus 001 Device 010: ID 0bda:8179 Realtek Semiconductor Corp. A similar device is mentioned in URL: http://bugs.debian.org/584945/ , which was reported solved a while back. I suspect this was version 1 of the dongle, using a different chipset. According to URL: http://www.elinux.org/RPi_USB_Wi-Fi_Adapters version 1 of the TL-WN725N dongle should work out of the box in Linux, while version 2 require manual driver installation, see URL: http://www.raspberrypi.org/phpBB3/viewtopic.php?f=26t=29752 for the details. So there is source out there to get this working with Linux. I hope to test it later today. But I was hoping this dongle would work out of the box with Debian stable, or at least with the next stable (Jessie). Can you add the driver to the kernel package to make this happen? -- Package-specific info: ** Version: Linux version 3.2.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.46-1+deb7u1 ** Command line: BOOT_IMAGE=/vmlinuz-3.2.0-4-amd64 root=/dev/mapper/minervavg-root ro quiet ** Not tainted ** Kernel log: [212873.001694] xhci_hcd :00:14.0: power state changed by ACPI to D0 [212873.016030] xhci_hcd :00:14.0: power state changed by ACPI to D0 [212873.016102] xhci_hcd :00:14.0: power state changed by ACPI to D0 [212873.016106] xhci_hcd :00:14.0: power state changed by ACPI to D0 [212873.016116] xhci_hcd :00:14.0: setting latency timer to 64 [212877.872066] xhci_hcd :00:14.0: power state changed by ACPI to D3 [212877.972041] ehci_hcd :00:1a.0: power state changed by ACPI to D3 [212878.001352] xhci_hcd :00:14.0: power state changed by ACPI to D0 [212878.016033] xhci_hcd :00:14.0: power state changed by ACPI to D0 [212878.016094] xhci_hcd :00:14.0: power state changed by ACPI to D0 [212878.016098] xhci_hcd :00:14.0: power state changed by ACPI to D0 [212878.016105] xhci_hcd :00:14.0: setting latency timer to 64 [212881.232082] wlan0: no IPv6 routers present [212882.872051] xhci_hcd :00:14.0: power state changed by ACPI to D3 [213292.363651] ehci_hcd :00:1a.0: power state changed by ACPI to D0 [213292.376119] ehci_hcd :00:1a.0: power state changed by ACPI to D0 [213292.376226] ehci_hcd :00:1a.0: power state changed by ACPI to D0 [213292.376236] ehci_hcd :00:1a.0: power state changed by ACPI to D0 [213292.376257] ehci_hcd :00:1a.0: setting latency timer to 64 [213292.376453] ehci_hcd :00:1d.0: power state changed by ACPI to D0 [213292.392076] ehci_hcd :00:1d.0: power state changed by ACPI to D0 [213292.392185] ehci_hcd :00:1d.0: power state changed by ACPI to D0 [213292.392195] ehci_hcd :00:1d.0: power state changed by ACPI to D0 [213292.392217] ehci_hcd :00:1d.0: setting latency timer to 64 [213292.392369] xhci_hcd :00:14.0: power state changed by ACPI to D0 [213292.408079] xhci_hcd :00:14.0: power state changed by ACPI to D0 [213292.408197] xhci_hcd :00:14.0: power state changed by ACPI to D0 [213292.408208] xhci_hcd :00:14.0: power state changed by ACPI to D0 [213292.408225] xhci_hcd :00:14.0: setting latency timer to 64 [213292.408298] ehci_hcd :00:1d.0: power state changed by ACPI to D3 [213292.524610] usb 1-1.2: USB disconnect, device number 10 [213294.816130] xhci_hcd :00:14.0: power state changed by ACPI to D3 [213296.852134] ehci_hcd :00:1a.0: power state changed by ACPI to D3 [213433.146825] ehci_hcd :00:1a.0: power state changed by ACPI to D0 [213433.160080] ehci_hcd :00:1a.0: power state changed by ACPI to D0 [213433.160187] ehci_hcd :00:1a.0: power state changed by ACPI to D0 [213433.160197] ehci_hcd :00:1a.0: power state changed by ACPI to D0 [213433.160218] ehci_hcd :00:1a.0: setting latency timer to 64 [213433.160397] ehci_hcd :00:1d.0: power state changed by ACPI to D0 [213433.176063] ehci_hcd :00:1d.0: power state changed by ACPI to D0 [213433.176159] ehci_hcd :00:1d.0: power state changed by ACPI to D0 [213433.176167] ehci_hcd :00:1d.0: power state changed by ACPI to D0 [213433.176185] ehci_hcd :00:1d.0: setting latency timer to 64 [213433.176306] xhci_hcd :00:14.0: power state changed by ACPI to D0 [213433.192043] xhci_hcd :00:14.0: power state changed by ACPI to D0 [213433.192105] xhci_hcd :00:14.0: power state changed by ACPI to D0 [213433.192108] xhci_hcd :00:14.0: power state changed by ACPI to D0 [213433.192116] xhci_hcd :00:14.0: setting latency timer to 64 [213433.192171] ehci_hcd :00:1d.0: power state changed by ACPI to D3 [213433.380541] usb 1-1.2: new high-speed USB device number 11 using ehci_hcd [213433.473962] usb 1-1.2: New USB device found, idVendor=0bda, idProduct=8179 [213433.473965]
Bug#726398: linux: Fail to work with USB wifi dongle TP-Link TL-WN725N V2 (USB id 0bda:8179)
Petter Reinholdtsen p...@hungry.com writes: I just bought a USB wifi dongle and it fail to work with the Linux kernel in Debian Stable/Wheezy. lsusb show this information about the device: Bus 001 Device 010: ID 0bda:8179 Realtek Semiconductor Corp. A similar device is mentioned in URL: http://bugs.debian.org/584945/ , which was reported solved a while back. I suspect this was version 1 of the dongle, using a different chipset. According to URL: http://www.elinux.org/RPi_USB_Wi-Fi_Adapters version 1 of the TL-WN725N dongle should work out of the box in Linux, while version 2 require manual driver installation, see URL: http://www.raspberrypi.org/phpBB3/viewtopic.php?f=26t=29752 for the details. So there is source out there to get this working with Linux. I hope to test it later today. Just FYI: This driver is also in staging, starting with v3.12-rc1: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/staging/rtl8188eu Bjørn -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87siw2pu73@nemi.mork.no
Bug#726398: linux: Fail to work with USB wifi dongle TP-Link TL-WN725N V2 (USB id 0bda:8179)
On Tue, Oct 15, 2013 at 14:08 +0200, Petter Reinholdtsen wrote: Dear Maintainer, I just bought a USB wifi dongle and it fail to work with the Linux kernel in Debian Stable/Wheezy. lsusb show this information about the device: Bus 001 Device 010: ID 0bda:8179 Realtek Semiconductor Corp. But I was hoping this dongle would work out of the box with Debian stable, or at least with the next stable (Jessie). Can you add the driver to the kernel package to make this happen? Hi Petter, That device should work with kernel 3.10, module rtl8188ee.ko. Upstream commits: f0eb856...8b138d4 So there is source out there to get this working with Linux. I hope to test it later today. I think the Jessie kernel will already support it. Regards, Steve -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131015141252.ga5...@s.cotton.clara.co.uk
Bug#726398: linux: Fail to work with USB wifi dongle TP-Link TL-WN725N V2 (USB id 0bda:8179)
Steve Cotton st...@s.cotton.clara.co.uk writes: On Tue, Oct 15, 2013 at 14:08 +0200, Petter Reinholdtsen wrote: Dear Maintainer, I just bought a USB wifi dongle and it fail to work with the Linux kernel in Debian Stable/Wheezy. lsusb show this information about the device: Bus 001 Device 010: ID 0bda:8179 Realtek Semiconductor Corp. But I was hoping this dongle would work out of the box with Debian stable, or at least with the next stable (Jessie). Can you add the driver to the kernel package to make this happen? Hi Petter, That device should work with kernel 3.10, module rtl8188ee.ko. I doubt that. r(tl)8188ee is a PCI-E chip and driver. The USB version is r(tl)8188eu. See http://wireless.kernel.org/en/users/Drivers/rtl819x for the full overview. Bjørn -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87d2n6pps0@nemi.mork.no
Bug#726398: linux: Fail to work with USB wifi dongle TP-Link TL-WN725N V2 (USB id 0bda:8179)
On Tue, Oct 15, 2013 at 16:33 +0200, Bjørn Mork wrote: Steve Cotton st...@s.cotton.clara.co.uk writes: That device should work with kernel 3.10, module rtl8188ee.ko. I doubt that. r(tl)8188ee is a PCI-E chip and driver. The USB version is r(tl)8188eu. See http://wireless.kernel.org/en/users/Drivers/rtl819x for the full overview. Bjørn Sorry for incorrect information. Bjørn is correct. (I guess it's better to confirm this in the BTS log than not to). Steve -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131015151622.ga7...@s.cotton.clara.co.uk
Bug#726398: linux: Fail to work with USB wifi dongle TP-Link TL-WN725N V2 (USB id 0bda:8179)
Control: found -1 3.10.11-1 [Steve Cotton] Sorry for incorrect information. Bjørn is correct. (I guess it's better to confirm this in the BTS log than not to). Yes, I tested it on Jessie too, so I can confirm that it do not work there either. Trying to tag this in the BTS meta information. -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131015152423.gr15...@ulrik.uio.no
Processed: Re: Bug#726398: linux: Fail to work with USB wifi dongle TP-Link TL-WN725N V2 (USB id 0bda:8179)
Processing control commands: found -1 3.10.11-1 Bug #726398 [src:linux] linux: Fail to work with USB wifi dongle TP-Link TL-WN725N V2 (USB id 0bda:8179) Marked as found in versions linux/3.10.11-1. -- 726398: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726398 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.b726398.138185066915679.transcr...@bugs.debian.org
Processed: tagging 695241
Processing commands for cont...@bugs.debian.org: tags 695241 + pending Bug #695241 [linux] linux: Add basic arm64 support Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 695241: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695241 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.138187948830579.transcr...@bugs.debian.org
Bug#695241: linux: Add basic arm64 support
On Mon, 2013-10-14 at 03:38 +0100, Wookey wrote: +++ Ben Hutchings [2013-10-13 19:20 +0100]: diff -urN origs/linux-3.10.11/debian/changelog build/linux-3.10.11/debian/changelog --- origs/linux-3.10.11/debian/changelog2013-09-10 14:13:17.0 +0100 +++ build/linux-3.10.11/debian/changelog2013-10-11 04:05:57.380980848 +0100 @@ -1,3 +1,9 @@ +linux (3.10.11-1~arm64) UNRELEASED; urgency=low + + * Add arm64 packaging + + -- woo...@debian.org Sat, 05 Oct 2013 02:24:25 +0100 + linux (3.10.11-1) unstable; urgency=low * New upstream stable update: This should be targetted at 3.11 (trunk in svn). Hmm. I was working off latest released package in unstable as that's the one I get to dowload and build. What do I need to do to 'target trunk in svn'? (e.g. where is it?) There is a standard place to find this information... [...] But we don't have an initramfs yet. klibc is not yet ported to arm64 so initramfs doesn't work, so we can't use it. Once klibc arm64 is in debian, I agree this setting is not needed for a distro kernel. It's also really useful with a model which is all we have to build on currently. [...] This is going nowhere. I'm not adding a config that looks like this - use of an initramfs is mandatory. (mips has been grandfathered in for now.) I'm adding just the linux-libc-dev package like you originally requested. Ben. -- Ben Hutchings Lowery's Law: If it jams, force it. If it breaks, it needed replacing anyway. signature.asc Description: This is a digitally signed message part
Bug#726463: linux-image-3.10-3-amd64: System randomly freezes completely, needs hard reboot
Package: src:linux
Version: 3.10.11-1
Severity: important
Hello kernel maintainers,
I'm experiencing random freezes on my laptop running sid with recent
kernels (3.10+, see below). It happens a couple of minutes to several
hours after booting, under no particular charge, and blocks completely
the screen, the mouse and the keyboard (no tty switching possible, no
magic keys). It leaves no information in /var/log/{messages,syslog}.
I experienced the problem both under X11 or in text console (with xdm
stopped), although the freeze seems to take longer to appear in text
mode (?). At first I suspected the network, but I had the machine freeze
when connected to the wired network, to a Wi-Fi network, or even
completely disconnected with the interfaces down.
This machine was freshly reinstalled on wheezy in early September and
upgraded to sid right after. I still have the 3.2 kernel from wheezy
installed (linux-image-3.2.0-4-amd64 3.2.46-1+deb7u1), and the machine
is perfectly stable when I run it. When I upgraded to sid, the most
recent kernel was linux-image-3.10-2-amd64, with wich I had the problem,
and it was later upgraded to linux-image-3.10-3-amd64 (3.10.11-1) with
no improvement. I also tried the 3.11 version from experimental
(linux-image-3.11-trunk-amd64 3.11-1~exp1) and the problem is still
present. However, a 3.11.4 kernel compiled from the official sources
works perfectly, so the problem might be caused by a Debian patch.
Note that this problem is likely unrelated to #711453, since the machine
has never rebooted by itself after a freeze.
In case that matters, this system is installed on LUKS + LVM + ext4 with
an unencrypted /boot (ext3).
I'd be happy to help diagnosing this bug but don't really know where to
start, so if you have any advice or request, feel free to tell me.
Cheers,
Matteo
-- Package-specific info:
** Version:
Linux version 3.10-3-amd64 (debian-kernel@lists.debian.org) (gcc version 4.7.3
(Debian 4.7.3-7) ) #1 SMP Debian 3.10.11-1 (2013-09-10)
** Command line:
BOOT_IMAGE=/vmlinuz-3.10-3-amd64 root=/dev/mapper/sysvg-rootlv ro quiet
** Not tainted
** Kernel log:
[ 16.950740] cfg80211: Calling CRDA to update world regulatory domain
[ 16.998729] [drm] Memory usable by graphics device = 2048M
[ 16.998737] i915 :00:02.0: setting latency timer to 64
[ 17.024422] i915 :00:02.0: irq 46 for MSI/MSI-X
[ 17.024434] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[ 17.024436] [drm] Driver supports precise vblank timestamp query.
[ 17.024503] vgaarb: device changed decodes:
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[ 17.044717] Non-volatile memory driver v1.3
[ 17.127837] ACPI: Battery Slot [BAT0] (battery present)
[ 17.130217] microcode: CPU0 sig=0x10676, pf=0x80, revision=0x60c
[ 17.228335] ath5k :03:00.0: registered as 'phy0'
[ 17.236019] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit
banging on pin 5
[ 17.276797] psmouse serio1: alps: Unknown ALPS touchpad: E7=10 00 64, EC=10
00 64
[ 17.277689] thinkpad_acpi: ThinkPad ACPI Extras v0.24
[ 17.277691] thinkpad_acpi: http://ibm-acpi.sf.net/
[ 17.277693] thinkpad_acpi: ThinkPad BIOS 6DET28WW (1.05 ), EC 7XHT21WW-1.03
[ 17.277694] thinkpad_acpi: Lenovo ThinkPad X200, model 7459WKU
[ 17.297754] thinkpad_acpi: detected a 8-level brightness capable ThinkPad
[ 17.297910] thinkpad_acpi: radio switch found; radios are disabled
[ 17.298001] thinkpad_acpi: This ThinkPad has standard ACPI backlight
brightness control, supported by the ACPI video driver
[ 17.298003] thinkpad_acpi: Disabling thinkpad-acpi brightness events by
default...
[ 17.300484] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is
blocked
[ 17.303039] thinkpad_acpi: Standard ACPI backlight interface available, not
loading native one
[ 17.303162] thinkpad_acpi: Console audio control enabled, mode: monitor
(read only)
[ 17.304836] input: ThinkPad Extra Buttons as
/devices/platform/thinkpad_acpi/input/input9
[ 17.343554] iTCO_vendor_support: vendor-support=0
[ 17.348824] fbcon: inteldrmfb (fb0) is primary device
[ 17.350924] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10
[ 17.350949] iTCO_wdt: Found a ICH9M-E TCO device (Version=2, TCOBASE=0x1060)
[ 17.351010] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[ 17.388826] platform microcode: firmware: agent aborted loading
intel-ucode/06-17-06 (not found?)
[ 17.30] microcode: CPU1 sig=0x10676, pf=0x80, revision=0x60c
[ 17.425391] platform microcode: firmware: agent aborted loading
intel-ucode/06-17-06 (not found?)
[ 17.425492] microcode: Microcode Update Driver: v2.00
tig...@aivazian.fsnet.co.uk, Peter Oruba
[ 17.667183] psmouse serio1: trackpoint: IBM TrackPoint firmware: 0x0e,
buttons: 3/3
[ 17.687550] input: TPPS/2 IBM TrackPoint as
/devices/platform/i8042/serio1/input/input10
[ 17.819781] ath: EEPROM regdomain: 0x67
[ 17.819782] ath: EEPROM indicates we should expect
