Bug#567212: marked as done (rt73usb with 2.6.32-trunk kernel)
Your message dated Sat, 13 Jul 2013 00:50:45 +0200 with message-id 20130712225044.GA4722@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #567212, regarding rt73usb with 2.6.32-trunk kernel to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 567212: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567212 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.32-trunk-686 Version: 2.6.32-5 Debian Squeeze I use Edimax EW-7318USg usb wifi adapter with rt73 chipset - i use default rt73usb driver that is built in kernel and standard firmware from non-free repository package: firmware-ralink (0.22) - on new 2.6.32 trunk kernel, connection is very unstable - i can connect to my access point but i get disconnected periodicly in about 6 to 10 seconds and get connected again afer about 4 seconds. This process repeats itself continously. I use WPAPSK autentication TKIP encryption in managed mode - with wpa_supplicant - encryption works but i guess becouse of such frequent disconnetions dhclient can't get IP and i can't connect to internet. On previous 2.6.30 kernel and same configuration, everything works fine and connection is stable. scanning with iwlist works on both kernels but on 2.6.32-trunk takes 2 times longer. I assume that problem is some collision in kernel modules or in driver. best regards Dawid ---End Message--- ---BeginMessage--- Hi, your bug has been filed against the linux-2.6 source package and was filed for a kernel older than the recently released Debian 7.x / Wheezy with a severity less than important. We don't have the ressources to reproduce the complete backlog of all older kernel bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy or a more recent kernel from testing or unstable, please reopen the bug by sending a mail to cont...@bugs.debian.org with the following three commands included in the mail: reopen BUGNUMBER reassign BUGNUMBER src:linux thanks Cheers, Moritz---End Message---
Re: trunk kernel?
hello, On Fri, Jan 07, 2011 at 10:57:53AM +0330, Nima Azarbayjany wrote: Can someone explain to me what is a trunk kernel? Are they safe to install? I would like to have the newly added 2.6.37 kernel in experimental in my Squeeze box. Is that a wise thing to do? Are there any risks involved? trunk only means that the abi is not guaranteed, so on upgrade you need to recompile any external modules. Otherwise it should just install fin in squeeze. Happy day -- maks -- 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/20110107125257.gx20...@vostochny.stro.at
trunk kernel?
Hi, Can someone explain to me what is a trunk kernel? Are they safe to install? I would like to have the newly added 2.6.37 kernel in experimental in my Squeeze box. Is that a wise thing to do? Are there any risks involved? Thanks. Nima -- 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/4d26c079.9020...@gmail.com
Bug#567212: rt73usb with 2.6.32-trunk kernel
On Thu, 2010-01-28 at 01:01 +0100, Dawid wrote: Package: linux-image-2.6.32-trunk-686 Version: 2.6.32-5 Debian Squeeze I use Edimax EW-7318USg usb wifi adapter with rt73 chipset - i use default rt73usb driver that is built in kernel and standard firmware from non-free repository package: firmware-ralink (0.22) - on new 2.6.32 trunk kernel, connection is very unstable - i can connect to my access point but i get disconnected periodicly in about 6 to 10 seconds and get connected again afer about 4 seconds. This process repeats itself continously. I use WPAPSK autentication TKIP encryption in managed mode - with wpa_supplicant - encryption works but i guess becouse of such frequent disconnetions dhclient can't get IP and i can't connect to internet. Please follow-up using 'reportbug -N 567212', which will include more information about your system. If you cannot do that then at least send a copy of the kernel log from 2.6.32-5. On previous 2.6.30 kernel and same configuration, everything works fine and connection is stable. [...] Were you using the rt73usb driver (from Debian kernel packages) or the rt73 driver (from rt73-source or from Ralink)? Ben. -- Ben Hutchings You can't have everything. Where would you put it? signature.asc Description: This is a digitally signed message part
Bug#567212: rt73usb with 2.6.32-trunk kernel
Package: linux-image-2.6.32-trunk-686 Version: 2.6.32-5 Debian Squeeze I use Edimax EW-7318USg usb wifi adapter with rt73 chipset - i use default rt73usb driver that is built in kernel and standard firmware from non-free repository package: firmware-ralink (0.22) - on new 2.6.32 trunk kernel, connection is very unstable - i can connect to my access point but i get disconnected periodicly in about 6 to 10 seconds and get connected again afer about 4 seconds. This process repeats itself continously. I use WPAPSK autentication TKIP encryption in managed mode - with wpa_supplicant - encryption works but i guess becouse of such frequent disconnetions dhclient can't get IP and i can't connect to internet. On previous 2.6.30 kernel and same configuration, everything works fine and connection is stable. scanning with iwlist works on both kernels but on 2.6.32-trunk takes 2 times longer. I assume that problem is some collision in kernel modules or in driver. best regards Dawid
Re: r4021 - trunk/kernel
On Mon, Aug 22, 2005 at 11:59:51AM +0200, Sven Luther wrote: Ok, this is a mess, so we probably need to hold a little flamewar about how we want the tree organized or something, before we start moving stuff back and fort. I believe that the trunk is for main development, and it is important that we keep the version we are actually using in trunk, and not the next version as the linux-2.6.13-rcsomething. Also, i am not overly convinced about the branch stuff, especially for main branches where we are going to work on, and not some obscure stuff only some will want to play with. Furthermore, now that the kernel subdir is going to be emptied of its content, in favour of the single linux-2.6 package, we could as well move linux-2.6 into the toplevel. So, my proposal was to have : /trunk/linux-2.6 - main 2.6 kernel being uploaded to sid I liked that, I always hated the enormous hierachies in the old repository. /trunk/linux-2.6-experimental - the experimental version. SVN allows branches to reside anywhere freely, including under /trunk, right? In that case this is okay, just make sure it really is a branch so merges work fine. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: r3297 - in trunk/kernel/source/kernel-source-2.6.11-2.6.11/debian: . patches patches/series
On Tue, Jun 14, 2005 at 09:37:08AM +0200, Christoph Hellwig wrote: On Tue, Jun 14, 2005 at 09:32:37AM +0200, Sven Luther wrote: Christoph, why in hell do you CC me on costa.debian.org and not use my @debian.org adress :) I just did an reply to the commit mail.. Yeah, guessed such, maybe alioth/svn/whatever should be fixed to be more smart about this. Because i am trying to build kernels that work for ppc64 boxes, as nobody is helping me out on this, i do what i can. Notice that this is stuff worked on by Cajus, who apparently managed to get some IBM boxes donated to the augsbourg university on behalf of the debian project, Altough i guess nobody else knew about it, and i just recently found out about that. Actually i should have added it to a a branch or something though. That said, it is just a driver, if you don't enable it, you will never see it :) And i am perfectly happy to drop it as not needed once i have a successfull report on logical partitioned working, which is currently failing, as reported by David Gaya, and his gentoo kernel worked. See the ppc64 mailing lists for that. + * Added patch for IBM eServer i/pSeries Virtual SCSI Target Driver from +Dave Boutcher [EMAIL PROTECTED], needed for ppc64 boxes with virtual +partitions, Thanks to Cajus Pollmeier for providing it. +(Sven Luther) And no, it's totally not needed for these systems to work. Ok, fine, what should be used then instead ? Can you provide your enlightnement on what is needed here, and maybe comment on the above mentioned failure ? The link seems to be : http://lists.alioth.debian.org/pipermail/debian-ppc64-devel/2005-June/000123.html that mail is to 90% a big base64 blob, people are too stupid to configure their mailers these days :P Hehe, indeed. Well, i forwarded you the more usefull mail, altough i don't remember where the gentoo .config file is, i can investigate this lter if needed, unless you have an insight. BTW, we should have access to logical partitions at the augsbour uni now, so this could be tested there, if you feel like this, i will not be able to in the next 2 weeks. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: r3297 - in trunk/kernel/source/kernel-source-2.6.11-2.6.11/debian: . patches patches/series
Christoph Hellwig schrieb: On Tue, Jun 14, 2005 at 09:23:49AM +0200, maximilian attems wrote: + * Added patch for IBM eServer i/pSeries Virtual SCSI Target Driver from i' curious to know what is needed? As the code and explanation says it's needed for vio targets, aka if you want to run multiple OS instances on a single system, and you absolutely want to run vio on some of the instances and run the server under debian linux (by default it runs AIX or OS/400), which lacks the infrastructure for this server anyway. Hi Christoph, *. I'm not really sure if i did understand that correctly. Do you think that the virtual i/o server for pSeries (i.e. IBM OpenPower) MUST run under AIX? That's not true. We have the virtual i/o server and the LPARs (virtual partitions) on OpenPower 720 both running under Debian. No need for any other (curious) operating system/kernel! And if the patch is neccessary for the virtual i/o server (driver: ibmvscsis), then the patch is neccessary for us. Harald -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: r2230 - in trunk/kernel/source/kernel-source-2.6.10-2.6.10/debian: . patches patches/series
+ static int __init init_ext3_fs(void)
+ {
+ int err = init_ext3_xattr();
++
++/* fix for oops */
++printk(KERN_ERR [%d] init_ext3_fs(), err = %d\n, __LINE__, err);
urgg, this is not a fix but a hack. Should look more like:
/* ugly hack to work around compiler bug */
#ifdef __alpha__
printk(KERN_DEBUG [%d] init_ext3_fs(), err = %d\n, __LINE__, err);
#endif
Re: r2230 - in trunk/kernel/source/kernel-source-2.6.10-2.6.10/debian: . patches patches/series
* Christoph Hellwig wrote:
+ static int __init init_ext3_fs(void)
+ {
+ int err = init_ext3_xattr();
++
++ /* fix for oops */
++ printk(KERN_ERR [%d] init_ext3_fs(), err = %d\n, __LINE__, err);
urgg, this is not a fix but a hack. Should look more like:
/* ugly hack to work around compiler bug */
#ifdef __alpha__
printk(KERN_DEBUG [%d] init_ext3_fs(), err = %d\n, __LINE__, err);
#endif
Indeed... updated for 2.6.8 and 2.6.10, thanks.
Norbert
Re: r2215 - in trunk/kernel/source/kernel-source-2.6.10-2.6.10/debian/patches: . series
* Christoph Hellwig wrote: +- smbfs-overflow-fixes.dpatch ++ smbfs-overflow-fixes-2.dpatch The new patch doesn't apply: -- 2.6.10-3 fully applied. smbfs-overflow-fixes.dpatch OK (-) smbfs-overflow-fixes-2.dpatch OK (+) 1 out of 2 hunks FAILED -- saving rejects to file drivers/ide/pci/generic.c.rej modular-ide.dpatch FAIL (-) make: *** [binary-indep] Error 1 Norbert
Re: r2215 - in trunk/kernel/source/kernel-source-2.6.10-2.6.10/debian/patches: . series
* Norbert Tretkowski wrote: * Christoph Hellwig wrote: +- smbfs-overflow-fixes.dpatch ++ smbfs-overflow-fixes-2.dpatch The new patch doesn't apply: -- 2.6.10-3 fully applied. smbfs-overflow-fixes.dpatch OK (-) smbfs-overflow-fixes-2.dpatch OK (+) 1 out of 2 hunks FAILED -- saving rejects to file drivers/ide/pci/generic.c.rej modular-ide.dpatch FAIL (-) make: *** [binary-indep] Error 1 D'uh... too late already... problem is in modular-ide.dpatch of course. Norbert
Re: r1087 - trunk/kernel/source/kernel-source-2.6.8-2.6.8/debian
+# Upstream deletes our debian directory. Bastards. +sed 's#rm -rf $(objtree)/debian/#test -f $(objtree)/debian/official || rm -rf $(objtree)/debian/#' scripts/package/Makefile scripts/package/Makefile.ouch +mv scripts/package/Makefile.ouch scripts/package/Makefile Yikes! It's bad enough we have to modify the upstream tree for firmware removals but please don't randomly change Makefiles.
Re: r1087 - trunk/kernel/source/kernel-source-2.6.8-2.6.8/debian
On Sat, 14 Aug 2004 13:53:36 +0200, Christoph Hellwig wrote: +# Upstream deletes our debian directory. Bastards. +sed 's#rm -rf $(objtree)/debian/#test -f $(objtree)/debian/official || rm -rf $(objtree)/debian/#' scripts/package/Makefile scripts/package/Makefile.ouch +mv scripts/package/Makefile.ouch scripts/package/Makefile Yikes! It's bad enough we have to modify the upstream tree for firmware removals but please don't randomly change Makefiles. I'm not convinced we can do this through a dpatch. The problem is, dpatch must first be run on the source before we can do a proper make clean. If you've just downloaded the kernel-source package, and run a debuild on it, it will start by cleaning; this will nuke the debian subdirectory, and cause confusion/annoyance. We could just modify the Makefile in diff.gz, but then it wouldn't be overly clear that the change is necessary. I think the best solution is just to modify the orig.tar.gz, and get it accepted upstream for 2.6.9 so we don't have to resort to such things.
Re: r1087 - trunk/kernel/source/kernel-source-2.6.8-2.6.8/debian
On Sat, Aug 14, 2004 at 03:27:52PM -0400, Andres Salomon wrote: I'm not convinced we can do this through a dpatch. The problem is, dpatch must first be run on the source before we can do a proper make clean. If you've just downloaded the kernel-source package, and run a debuild on it, it will start by cleaning; this will nuke the debian subdirectory, and cause confusion/annoyance. We could just modify the Makefile in diff.gz, but then it wouldn't be overly clear that the change is necessary. I think the best solution is just to modify the orig.tar.gz, and get it accepted upstream for 2.6.9 so we don't have to resort to such things. Umm, again, debian has the concept of a .orig.gz and a diff.gz and we shouldn't mess with .orig.gz unless we can't redistribute it. Given that I can easily build a kernel even without that fix I can't see how it's criticial in any way.
Re: r1087 - trunk/kernel/source/kernel-source-2.6.8-2.6.8/debian
On Sat, 14 Aug 2004 22:17:17 +0200, Christoph Hellwig wrote: [...] Umm, again, debian has the concept of a .orig.gz and a diff.gz and we shouldn't mess with .orig.gz unless we can't redistribute it. Normally I'd agree, but the orig.tar.gz isn't upstream's anyways. We're still modifying it. So, orig.tar.gz isn't the actual upstream source, it's our modified source. Obviously, we want as few changes as possible in orig.tar.gz, but the only other alternative is in the diff.gz; and if we do that, there's the potential for changes to get lost/forgotten about (since our changes to upstream source are all dpatches and the prune-non-free script). I think the best place for this is in orig.tar.gz; I just mailed the patch to Andrew, so hopefully we won't have to worry about this for 2.6.9. Given that I can easily build a kernel even without that fix I can't see how it's criticial in any way. This could be considered a FTBFS bug, which is RC. If this was a normal package, being built on buildds, then the clean rule would be run after the package was unpacked.
Re: r973 - in trunk/kernel/source/kernel-source-2.6.7-2.6.7/debian: . patches
Hi, Sven Luther writes: Modified: trunk/kernel/source/kernel-source-2.6.7-2.6.7/debian/patch es/marvell-pegasos.dpatch Let me re-iterate: You must never, ever change dpatch files that have already made it into uploads. Otherwise, you will certainly break kernel-tree. See debian/README.NMU, step 3. Anyway. If you want this and kernel-patch-powerpc built and uploaded, drop me an email and I'll do it tonight. Regards, Jens. -- J'qbpbe, le m'en fquz pe j'qbpbe! Le veux aimeb et mqubib panz je pézqbpbe je djuz tqtaj!
Re: r973 - in trunk/kernel/source/kernel-source-2.6.7-2.6.7/debian: . patches
On Thu, Aug 05, 2004 at 03:52:47PM +0200, Jens Schmalzing wrote: Hi, Sven Luther writes: Modified: trunk/kernel/source/kernel-source-2.6.7-2.6.7/debian/patch es/marvell-pegasos.dpatch Let me re-iterate: You must never, ever change dpatch files that have already made it into uploads. Otherwise, you will certainly break kernel-tree. See debian/README.NMU, step 3. Yeah, thanks, i had forgotten about this, will fix it later today. Now, you didn't want the powerpc patch to make use of the kernel-tree facility, so what is the real interest of doing it this way ? Anyway. If you want this and kernel-patch-powerpc built and uploaded, drop me an email and I'll do it tonight. Let's wait one more day to be sure that other things don't come up. Friendly, Sven Luther
Re: r973 - in trunk/kernel/source/kernel-source-2.6.7-2.6.7/debian: . patches
Hi, Sven Luther writes: Yeah, thanks, i had forgotten about this, will fix it later today. It's already fixed. Let's wait one more day to be sure that other things don't come up. Fair enough. Regards, Jens. -- J'qbpbe, le m'en fquz pe j'qbpbe! Le veux aimeb et mqubib panz je pézqbpbe je djuz tqtaj!
