Nate Bargmann wrote:
Package: madwifi-source
Version: 0.svn20051110-1
Severity: wishlist
I decided to try the madwifi-source this evening and am at a bit of a
loss on how to proceed. I followed the instructions I've used in the
past at http://www.marlow.dk/site.php/tech/madwifi and performed
michel Xhaard wrote:
Le Vendredi 13 Janvier 2006 05:35, Brad Sawatzky a écrit :
Strange my original spca5xx-20051212 include on top of the
spca50x.h file ?
#ifdef __KERNEL__
#include
#include
#include
#include
#include
Are you sure you are using the right source code ?
Precisely
Jean-Marc Ranger wrote:
Hi Kel,
Due to a recently arrived ipw2200, I'm loosing some interest in
continuing to package the adm8211 code for Debian. Are you interessed
in taking the ownership of the ITP bug in Debian ?
Jean-Marc
The in-kernel wireless code is too turbulent right now, an
Graham wrote:
Package: madwifi-source
Version: 2005
I've built the module against the Debian "official" kernel
2.6.14-2-686 (version 2.6.14-7).
I have a ThinkPad A22p and an Enterasys Networks PCMCIA a/b/g card. I
will attach the output of "lspci -vvv".
When I click "scan for networks" in
Graham wrote:
It may be related to the inability of this module to do background
scanning, or it could just be a plain old bug in the code. Try using the
basic wireless-tools and refrain from using the graphical apps, and see
if you can reproduce this instability.
Hi Kel,
I'm just gettin
Graham wrote:
Hi Kel,
Thank you for the links.
Well, in my experience these gui apps for configuring wireless on linux
really cause more trouble than they are worth.
Maybe, but:
1. You and I are fine with console based configuration tools, but many
people, including the owner of th
Hi,
http://kanotix.com/files/debian/acerhk/
That package was made by your's truly for the Kanotix project.
Although I am not officially involved with debian, I currently
co-maintain some other module packages (spca5xx and madwifi) on alioth.
If a developer would like to sponsor and co-maintai
Hi,
Package for these drivers are here:-
http://kanotix.com/files/debian/pool/main/a/adm8211/
I also track the experimental new version that depends on the common
ieee80211 stack (>=2.6.14) here:-
ftp://debian.tu-bs.de/project/kanotix/experimental/pool/main/a/adm8211/
If you would like to u
Package: wnpp
Severity: wishlist
Hi,
http://kanotix.com/files/debian/pool/main/r/rt2570/
Above are packages I developed as part of the Kanotix project.
If there is any interest in them to be in debian (alongside the existing rt2400
& rt2500 packages), feel free to contact me concerning these
Jean-Marc Ranger wrote:
Hi Kel,
I'll definitely have a look at what you did. I'm fairly new at Debian
packaging, so I sure can learn from what you did.
My version of the 20050620 driver is available at
http://web.ncf.ca/jmranger/adm8211/ if you're interessed to have a
look. It was discus
Bill Wohler wrote:
Package: madwifi-source
Version: 0.svn20051110-1
Severity: normal
Thanks for packaging madwifi.
/usr/share/doc/madwifi-source/README.Debian is missing a step. If I
create an /etc/network/interfaces stanza of
iface eth1 inet dhcp
wireless_essid my-SSID
wi
Bill Wohler wrote:
Kel Modderman <[EMAIL PROTECTED]> wrote:
The README would better use ath0 as an example instead of eth1.
Yes, that would clear things up a lot. I thought perhaps I was missing
something. I have been using ath0.
"ifrename"; install i
Paul Brossier wrote:
for info, i tried earlier versions of spca5xx from
http://mxhaard.free.fr/spca50x/Download/?M=D and found out that the last
version compiling on -powerpc64 is spca5xx-20050601
[EMAIL PROTECTED]:~/spca5xx-20050601$ make
Building SPCA5XX driver for 2.5/2.6 kernel.
Remembe
Hi,
By the time I saw this, there were a volley of replies to this first
attempt at contact.
Stephen Birch wrote:
>Hi Kel and Itay
>
>One of the packages I have been planning for Debian is the spca5xx
>package for which I filed a ITP some time back. Since I believed my
>NM application was short
/debian/changelog
--- spca5xx-20050906.1-current/debian/changelog2005-09-25
20:20:56.0 +1000
+++ spca5xx-20050906.1-new/debian/changelog2005-09-25
20:20:18.0 +1000
@@ -1,3 +1,11 @@
+spca5xx (20050906.1-2) UNRELEASED; urgency=low
+
+ [Kel Modderman]
+ * Move staging
Hey Otavio,
Otavio Salvador wrote:
>Kel Modderman <[EMAIL PROTECTED]> writes:
>
>
>
>>Otavio, I did some more thinking about the recent revamp of the rules,
>>and i'd like to propose a small optimisation.
>>
>>
>
>I agree with all this
On Sunday 31 December 2006 20:46, Samuel Mimram wrote:
> Package: gspca-source
> Severity: wishlist
>
> Hi,
>
> Could you please package the 1.00.11 version of gspca which addds
> support for the zc0321 chipsets?
Sure. Will do so as soon as I can.
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAI
On Tuesday 26 December 2006 00:45, Junichi Uekawa wrote:
> Package: madwifi-source
> Version: 1:0.9.2+r1842.20061207-3
> Tags: patch
>
>
> Hi,
>
> I needed Linux 2.6.20 support; attached is a dpatch file for support.
>
Thanks. proski (Pavel Roskin) from upstream has claimed this very task. I was
On Monday 22 January 2007 23:31, Maik Zumstrull wrote:
> As of now, for no reason I can see, the dropouts have stopped.
>
> I have neither changed my WPA and ifupdown configuration nor upgraded
> directly related packages; but still, the problem is gone. I assume
> this is due to some package updat
tags 407936 - patch
thanks
On Monday 22 January 2007 23:52, Ivan Zaera Avellon wrote:
> Package: wpasupplicant
> Version: 0.5.5-4
> Severity: normal
> Tags: patch
>
>
> When wpasupplicant is launched from /etc/wpa_supplicant/functions.sh it
> tries to use flag -W, which is supposed to make it wait
Hi,
On Sunday 07 January 2007 23:03, tom schorpp wrote:
> Package: madwifi-source
> Version: 1:0.9.2+r1842.20061207-2
> Severity: important
>
> Jan 7 11:35:17 tom3 kernel: BUG: unable to handle kernel NULL pointer
> dereference at virtual address 0005
> Jan 7 11:35:17 tom3 kernel: printing
On Tuesday 23 January 2007 10:18, thomas schorpp wrote:
> Kel Modderman wrote:
> > Hi,
> >
> > On Sunday 07 January 2007 23:03, tom schorpp wrote:
> >>Package: madwifi-source
> >>Version: 1:0.9.2+r1842.20061207-2
> >>Severity: important
> >&g
On Tuesday 23 January 2007 20:31, Ivan Zaera Avellon wrote:
> Hi Kel:
>
> It's OK for me to send you my configuration, but I need to know what you
> want exactly.
Your configuration looks fine.
buzzard:/home/kel#
wpa_supplicant -W -ieth1 -Dwext -c/etc/wpa_supplicant/wpa_supplicant-dummy.conf
-d
On Tuesday 12 December 2006 03:17, Thomas Esselen wrote:
> Package: wpasupplicant
> Version: 0.5.5-3
> Severity: important
>
> Hi,
>
> please upgrade to a 0.6.0 snapshot since EAP-TTLS and encrypted passwords
> for the tunnelled identity do not work with earlier releases:
>
> * fixed EAP-PE
Hi Henning,
On Thursday 14 December 2006 20:33, Henning Glawe wrote:
> I have configured a roaming wpa configuration on my laptop using
>
> allow-hotplug wlan0
> iface wlan0 inet manual
> wpa-driver wext
> wpa-roam /etc/wpa_supplicant.conf
>
> in /etc/network/interfaces.
>
>
On Thursday 14 December 2006 22:19, Thomas Kallenberg wrote:
> Could this be a driver issue? I have the same problem and I'm using the
> madwifi-svn driver with wpasupplicant driver from unstable and
> network-manager from etch.
It is almost 100% likely to be an issue with the madwifi driver.
>
>
Hi Eduard,
On Saturday 16 December 2006 18:37, Eduard Bloch wrote:
> I just discovered that current wpa_supplicant just segfaults if the
> specified interface is not available at all. Here the log and strace
> log, as executed by ifup:
>
> ifup eth1=kpax
> ioctl[SIOCSIWPMKSA]: No such device
> ioc
Hi Eduard,
On Saturday 16 December 2006 19:14, Eduard Bloch wrote:
> I just hat to swear once again about wpa_supplicant. After consolidation
> of my config some weeks ago I have kept "wpa-essid" directions there,
> and I assumed that they are correct because nothing complained. However,
> it does
On Monday 18 December 2006 07:39, Kel Modderman wrote:
>For this reason, I changed the bug title.
Didn't change it, becasue we may still yet have bright ideas ;-)
Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
severity 403301 important
thanks
Hi Matteo,
Lowered severity, this does not meet grave bug criteria, IMHO. The package
works fine with supported devices and did not cause you any harm.
On Saturday 16 December 2006 11:50, Matteo Croce wrote:
> Package: wpasupplicant
> Version: 0.5.5-4
> Severity
Hi,
> $ sudo wpa_supplicant -c/etc/wpa_supplicant/wpa_supplicant.conf -Dwext
> -ifoo0 ioctl[SIOCSIWPMKSA]: No such device
> ioctl[SIOCSIWMODE]: No such device
> Could not configure driver to use managed mode
> ioctl[SIOCGIFFLAGS]: No such device
> Could not set interface 'foo0' UP
> ioctl[SIOCGIWR
Hi Maik,
On Tuesday 19 December 2006 21:45, Maik Zumstrull wrote:
> Package: wpasupplicant
> Version: 0.5.5-4
>
> When using wpa_supplicant in roaming mode on current Debian madwifi
> (see attachment: package-versions), the connection drops every thirty
> seconds or so.
MadWifi sucks a bit in cer
Package: trac
Version: 0.10-3
Severity: normal
I was struck by a baffling problem described at
http://trac.edgewall.org/ticket/3984
Summary: it is impossible to attach anything to the trac system with the
combination of trac 0.10 and python 2.4.4. Attempting to do so would
cause the following err
at is
+responsible for copying required upstream contents into debian module
+source tarball staging area.
+
+ -- Kel Modderman <[EMAIL PROTECTED]> Sun, 12 Nov 2006 12:21:59 +1000
+
unionfs (1.3.20061029.0124+debian-1) unstable; urgency=low
* New upstream snapshot:
Hi Ian,
On Monday 13 November 2006 03:20, Ian MacDonald wrote:
> Package: madwifi-source
> Version: 1:0.9.2+r1784.20061027-1
> Severity: important
>
> The following is from the buildlog after executing #m-a a-i madwifi
>
> dh_testroot
> dh_clean
> /usr/bin/make -C /usr/src/modules/madwifi clean \
On Friday 01 December 2006 21:30, Bastian Blank wrote:
> tags 400752 moreinfo
> thanks
>
> On Wed, Nov 29, 2006 at 01:17:20AM +1000, Kel Modderman wrote:
> > Package: linux-modules-extra-2.6
> > Severity: wishlist
> > Tags: patch
> >
> > Please consider in
On Sunday 03 December 2006 12:11, Andreas Henriksson wrote:
> I can't reproduce your problem with spca5xx-source. How are you
> building?
>
> I've tried building the spca5xx-source in an unstable amd64 pbuilder,
> then installing the spca5xx-source package and building that with
> module-assistant
tags 400752 moreinfo
thanks
On Monday 04 December 2006 01:33, Gerrit Jan Baarda wrote:
> Package: wpasupplicant
> Version: 0.5.5-2
> Severity: important
>
> After upgrading to 0.5.5-3 my laptop (IPW2200) will not cannect to the
> WLAN anymore.
>
> Here's the output of ifup/down:
>
>
> wpa_sup
tags 401441 moreinfo
thanks
Errm, helps when i use the correct bug number for manipulating tags (and
luckily the tag i sent to the worng bug report was not unrelevant).
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
tags 401413 patch
thanks
Hi Torquil,
On Sunday 03 December 2006 21:19, Torquil Macdonald Sørensen wrote:
> I am trying to connect to a wired network with IEEE8021X authentication.
Ok. Something I admit to having very little experience with.
> Thus I have no wpa-ssid line in /etc/network/interfa
On Friday 20 October 2006 20:41, Per Olofsson wrote:
> Kel Modderman:
> > Try something like:
> >
> > for x in $INTERFACES; do
> > if test -x /sbin/wpa_action && \
> > wpa_action $x check; then
> > wpa_action $x stop
&g
On Tuesday 05 December 2006 10:30, Przemyslaw Bruski wrote:
> Package: wpasupplicant
> Version: 0.5.5-2
> Severity: normal
>
> Currently, wpasupplicant is stopped before unmountnfs.sh script is run.
> This means that the network connection for NFS mounts may be gone by the
> time we try to unmount
On Wednesday 06 December 2006 08:25, Przemyslaw Bruski wrote:
> Hi Kel,
>
> > Of course you are right. However, sendsigs is run at sequence number 20,
> > and it kills the wpa_supplicant process.
>
> Not anymore - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=367944.
> The maintainers have moved
On Wednesday 06 December 2006 12:20, Sam Morris wrote:
> Package: wpasupplicant
> Version: 0.5.6-0
> Severity: wishlist
>
> Version 0.5.6 is available. I built an updated package that seems to work
> fine by simply uupdating and then removing the (incorporated-upstream)
> patch 'patch 11_erroneous_
On Saturday 09 December 2006 06:33, Gerrit Jan Baarda wrote:
> Op maandag 4 december 2006 02:49, schreef Kel Modderman:
> > Not very helpful ouput.
> >
> > Please show your /etc/network/interfaces configuration, and output
> > of 'ifup --verbose ethX' where e
On Saturday 09 December 2006 08:00, Matt Brown wrote:
> The fix described in the third post is incorrect. The backported patches
> applied in -3 have already reordered this part of the code so that it
> works correctly with madwifi.
>
> Unfortunately that backport missed the final component of the
> > Package: gspca-source
> > Severity: wishlist
> >
> > Hi,
> >
> > Could you please package the 1.00.11 version of gspca which addds
> > support for the zc0321 chipsets?
>
> Sure. Will do so as soon as I can.
>
New upstream has been prepared in pkg-spca5xx SVN on svn.d.o. A package will
be loca
On Wednesday 10 January 2007 06:12, Torsten Werner wrote:
> Hi,
>
>
> the bug report is now almost 90 days old. Do you plan to package the
> newer driver?
What, this one?
http://packages.debian.org/unstable/graphics/gspca-source
I guess #392759 can be closed . . .
Thanks, Kel.
--
To UNSUBSC
On Tuesday 09 January 2007 11:30, Kel Modderman wrote:
> > > Package: gspca-source
> > > Severity: wishlist
> > >
> > > Hi,
> > >
> > > Could you please package the 1.00.11 version of gspca which addds
> > > support for the zc03
On Saturday 25 November 2006 20:51, Fathi Boudra wrote:
> There's something new in dmesg like "changing interface name":
> ndiswrapper version 1.28 loaded (preempt=no,smp=yes)
> ndiswrapper: driver sis163u (TRENDnet,11/20/2005,5.1.1039.1050) loaded
> wlan0: vendor: 'Wireless Driver'
> wlan0: ethern
On Sunday 26 November 2006 00:45, Marc Haber wrote:
>> This looks like it would be an artifact of the problem you reported as
>> #386090. I don't think I can answer this with any integrity without further
>> information, as addressed on your previous bug report.
>
>I think that all information re
ephen Birch <[EMAIL PROTECTED]>
-Kel Modderman <[EMAIL PROTECTED]>
-Otavio Salvador <[EMAIL PROTECTED]>
-Itay Ben-Yaacov <[EMAIL PROTECTED]>
-
-This package is licenced under the terms of the GNU General Public Licence.
-
-On Debian systems, the complete text of the GNU GPL
was debianized by Kel Modderman <[EMAIL PROTECTED]> on
+Wed, 4 Oct 2006 12:35:59 +1000.
+
+It was downloaded from http://mxhaard.free.fr/download.html
+
+Upstream Author: Michel Xhaard <[EMAIL PROTECTED]>
+
+The following files contain multiple copyright holders:
+
+decoder/gs
debianized by Erik Rigtorp <[EMAIL PROTECTED]> on
+Mon, 23 Feb 2004 17:48:38 +0100.
+
+This package is currently maintained by Andres Salomon <[EMAIL PROTECTED]>
+and Kel Modderman <[EMAIL PROTECTED]> as of Oct. 2006.
+
+It was downloaded from http://ndiswrapper.sourceforge.net/
+
+Th
On Sunday 29 October 2006 13:31, Nathaniel W. Filardo wrote:
> According to http://madwifi.org/ticket/925 this is fixed in r1755.
Yeah, I was the one who tested and applied the patch.
Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PR
On Tuesday 17 October 2006 01:22, martin f krafft wrote:
> Package: wpasupplicant
> Version: 0.5.5-2
> Severity: normal
>
> If I use ifupdown integration, wpa_supplicant starts up nicely as
> expected. It associates with the AP and then dhclient (called by
> ifup) tries to get a lease. However, if
On Monday 30 October 2006 11:50, Michael Biebl wrote:
> Package: wpasupplicant
> Version: 0.5.5-2
> Severity: normal
>
> I tried the new modes of wpa_supplicant using /e/n/i.
> Using "wpa-conf /path/to/config" works fine but unfortunately blocks the
> boot process. But when I use the new roaming mo
Hi,
This is causing wpasupplicant to FTBFS (wpagui requires libqt4-dev). I'd love
to do some finishing touches to wpasuppliant before etch, but cannot while
this is blocking it.
Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTE
On Wednesday 01 November 2006 02:22, Michael Biebl wrote:
> See also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=342887
>
> Maybe we should add #342887 as blocker for this bug?
Looks like that is exactly why you have problems, interesting (and damn
frustrating!). Please do add that report as
On Thursday 02 November 2006 08:55, Piotr Roszatycki wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Piotr Roszatycki <[EMAIL PROTECTED]>
>
> * Package name: rt73
> Upstream author : Paul Lin <[EMAIL PROTECTED]>
> Version : 1.0.3.6
> * URL :
> http://www.ralinktech.
Package: hostapd
Version: 1:0.5.5-3
Severity: grave
Justification: renders package unusable
The subtle changes between 0.5.5-2 and 0.5.5-3 have exposed a
showstopping bug when used in conjunction with certain madwifi driver
versions (specifically 0.9.2+r1784.20061027-1 currently in debian).
This
On Tuesday 14 November 2006 08:43, Kel Modderman wrote:
> Package: hostapd
> Version: 1:0.5.5-3
> Severity: grave
> Justification: renders package unusable
>
> The subtle changes between 0.5.5-2 and 0.5.5-3 have exposed a
> showstopping bug when used in conjunction with c
On Thursday 16 November 2006 05:38, Anand Kumria wrote:
> I use the ipw2200 driver (from 2.6.18-rc2) and with the following in
> /etc/network/interface I can intermittedly associate but never get an IP
> address allocation via DHCP:
>
> iface wlan0 inet dhcp
> wpa-ssid MyWiFi
> wpa-
On Wednesday 07 February 2007 20:11, Max Alekseyev wrote:
> I've tried to use the proposed patch with the released Linux kernel 2.6.20
> from kernel.org While it does help to build the madwifi modules, they do
> not work properly. Namely, I get the following error when the modules
> start:
>
> wifi
tags 410113 moreinfo
thanks
On Thursday 08 February 2007 05:28, Torsten Werner wrote:
> Package: gspca-source
> Version: 01.00.12-1
> Severity: normal
>
> Hi,
>
> it does not build any more.
>
Attach some build output/proof please?
# Build the module
/usr/bin/make -C /home/kel/src/modules/gspca
On Thursday 08 February 2007 19:56, Kai Weber wrote:
> Package: ndiswrapper-source
> Version: 1.30-1
> Severity: wishlist
>
> Hello,
>
> a new upstream version for ndiswrapper is available: 1.37. This version
> fixes incompatibilty with kernel version 2.6.20, and the annoying hang,
> when devicenam
Hi Neil,
Is ndiswrapper still unstable for you? or #332668 still valid?
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hi Graham,
I am wondering, is the current madwifi still unstable as hell for you? Is this
bug still valid?
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hi Andrea,
Is this also the case with:
http://users.tpg.com.au/sigm/debian/ndis/
http://users.tpg.com.au/sigm/debian/ndis/ndiswrapper_1.37-1.dsc
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Monday 22 January 2007 23:52, Ivan Zaera Avellon wrote:
> Package: wpasupplicant
> Version: 0.5.5-4
> Severity: normal
> Tags: patch
>
>
> When wpasupplicant is launched from /etc/wpa_supplicant/functions.sh it
> tries to use flag -W, which is supposed to make it wait until the wpa_cli
> attache
sanity checking for
the other many requirements for using wpa_supplicant in IBSS mode.
* Update XS-Vcs-* fields in control file, add Vcs-Browser token.
* Move debian spcific ifupdown sh glue into debian/ifupdown/.
- -- Kel Modderman <[EMAIL PROTECTED]> Sun, 4 Mar 2007 14:06:46 +1000
+ -
On Sunday 04 March 2007 16:17, Kel Modderman wrote:
> Hi Michael,
>
> On Saturday 03 March 2007 12:22, Michael Biebl wrote:
> > Hi,
> >
> > you will also very likely need the attached patch:
> > Debian does not use pam_console but uses group membership to contro
On Sunday 04 March 2007 21:17, Kel Modderman wrote:
> On Sunday 04 March 2007 16:17, Kel Modderman wrote:
> > Hi Michael,
> >
> > On Saturday 03 March 2007 12:22, Michael Biebl wrote:
> > > Hi,
> > >
> > > you will also very likely need the attached
On Monday 05 March 2007 01:05, Michael Biebl wrote:
> >
> > Ok. How would the sequnce number of the wpa_supplicant event.d scriplet
> > be determined?
>
> NetworkManager 0.7.x is currently the only application I know of, which
> uses the D-Bus interface of wpa_supplicant. It runs at 25, so, yeah,
On Monday 05 March 2007 18:57, Michael Biebl wrote:
> > To suggest an answer to my pesky questions above, would could ship a
> > conffile similar to this now, but disabled, and when networkmanager 0.7.X
> > is in the archive "flip the switch" and upload new wpasupplicant with
> > conffile set to a
On Wednesday 28 February 2007 08:45, Patrick Büker wrote:
> Package: wpasupplicant
> Version: 0.5.5-2
>
>
> I get the message on one box running etch and madwifi.
>
> Sometimes I get a connection but then looses connection with
> CTRL-EVENT-DISCONNECT - Disconnect event - remove keys
This bug repo
On Wednesday 07 March 2007 02:01, Bernhard wrote:
> Package: wpasupplicant
> Version: 0.5.5-2
> Severity: minor
>
> The package wpasupplicant should depend to the wireless-tools.
>
> >From my side, it makes no sense to install wpasupplicant without
>
> wireless-tools.
I will make wireless-tools a
On Friday 15 December 2006 18:19, Henning Glawe wrote:
> On Fri, Dec 15, 2006 at 01:33:12PM +1000, Kel Modderman wrote:
> > > the problem is, at least in my case, that the link is _down_
> > > afterwards, so wpasupplicant is not able to scan further. This seems to
> > &
Hi Bernhard,
On Saturday 17 March 2007 16:47, Bernhard wrote:
> Hello,
>
> This bugreport stays at "more information needed".
> Which additional information is needed?
>
> Please let me know.
This bug report caught me by surprise, it seems that is was transferred over
here from another package.
Hi Brian,
On Monday 26 March 2007 15:15, Brian Cox wrote:
> Package: wpasupplicant
> Version: 0.5.5-4
> Severity: normal
>
>
> This package's init script, /etc/init.d/wpa-ifupdown, is configured to
> start rather than stop during runlevels 0 and 6. This is especially
> perplexing since the init s
Hi,
On Wednesday 28 March 2007 20:28, Michel Xhaard wrote:
> >
> >
> > Attached patch fixed my build problems on ARM.
> >
> > I suggest to forward this upstream, too. Dollar signs in variable names
> > are not such a good idea, IHMO.
> >
> >
> > HTH, Uwe.
>
> Uwe,
> Thanks for the patch, i will F
On Sunday 01 April 2007 19:52, Bernhard wrote:
> Hello, Kel
>
> On my system, the WPA Supplicant is started manually in /etc/interfaces.
> My configuration of the network interface is shown in the following lines:
>iface eth2 inet dhcp
>pre-up wpa_supplicant -ieth2 -Dwext
> -c/etc/wpa_suppl
Hi Riccardo,
On Saturday 24 February 2007 21:28, Riccardo Setti wrote:
> Package: wpasupplicant
> Version: 0.5.5-4
> Severity: wishlist
> Tags: patch
>
> hello,
>
> please add this patch in the next upload of wpasupplicant, it adds
> support for use wpasupplicant via dbus.
Patch applied.
>
> wpa
On Thursday 15 March 2007 21:32, [EMAIL PROTECTED] wrote:
> Package: madwifi-source
> Version: 1:0.9.2+r1842.20061207-2
> Severity: normal
>
> Other folks have reported success with the same laptop "Acer TravelMate
> 2310". lspci output for the device is:
>
> 00:0b.0 Ethernet controller: Atheros Co
On Friday 16 March 2007 00:17, Joshua N Pritikin wrote:
> I found this thread which looks promising:
>
> http://thread.gmane.org/gmane.linux.drivers.madwifi.user/11599
>
> I know binary drivers suck but you could at least suggest that I look
> upstream if you don't know what to do.
That is just co
severity 419057 wishlist
thanks
Hi Subhashis,
On Saturday 14 April 2007 00:19, Subhashis Roy wrote:
> Package: ndiswrapper-source
> Version: 1.28-1
> Severity: grave
> Justification: renders package unusable
...when used with stuff outside of what is in etch.
This is not a grave shortcoming of
On Wednesday 11 April 2007 08:49, giggz wrote:
> Package: wpasupplicant
> Version: 0.6.0~cvs20070224-2
> Severity: normal
>
> Hi,
>
> Since a recent update, I have this message during the boot :
> Starting system message bus :Dbus Unknown group "netdev" in message bus
> configuration file So I have
On Friday 13 April 2007 23:07, Bernhard wrote:
> Hello, Kel
>
>
> I have changed my configuration in /etc/network/interfaces.
> The modified network configuration is in the attachement.
>
> After reboot, i have started the wpa supplicant in a root terminal:
>wpa_supplicant -Dwext -ieth2
> -c/et
Restoring CC's to bug + list.
On Saturday 14 April 2007 09:03, giggz wrote:
> I saw that there was a similar bug for avahi-daemon (#385495 for
> example). And a patch from dhcdb was given :
>
> --8<---cut here---start->8---
> --- avahi-daemon.postinst 2006
On Monday 02 April 2007 00:47, Anders Boström wrote:
> Package: madwifi-source
> Version: 1:0.9.2+r2156.20070225-1
> Severity: important
>
> After upgrade to 2.6.20.2 and madwifi 1:0.9.2+r2156.20070225-1, my
> computer hang during boot, at module load of the madwifi modules.
>
> Ctrl-C breaks up th
Hi Bernhard,
On Friday 06 April 2007 04:39, Bernhard wrote:
> Hello, Kel
>
> I have tested it with my Notebook again.
>
> My new configuration of the network interface is shown in the following
> lines:
>iface eth2 inet dhcp
>wpa-ssid mynetworkessid
>wpa-psk mysecretpassword
>wirel
On Monday 28 August 2006 00:29, Celejar wrote:
> Wireless card is Trendware TEW443-PI. Chipset is Atheros AR5212 802.11abg
> NIC (rev 01). pciid is 168c:0013. Kernel is 2.6.12-1-386. 'madwifi-source'
> is 0.svnr1697.0.9.2-1.
>
> 'modprobe ath_pci autocreate=ap'; here's dmesg:
> > ath_hal: 0.9.17.2
Hi Loic and Aurel,
On Monday 21 August 2006 21:20, Loïc Minier wrote:
> On Mon, Aug 21, 2006, Kel Modderman wrote:
> > Loic contacted me on IRC with a proposal to split the tools into an own
> > source package that would enter contrib, and thus be autobuilt. Is this
> > som
On Monday 04 September 2006 00:28, Carlos Moffat wrote:
> On Sun, 2006-09-03 at 16:06 +0200, Loïc Minier wrote:
> > Hi,
> >
> > On Sun, Sep 03, 2006, Carlos Moffat wrote:
> > > I have two interfaces coming up: wifi0 and ath0. Both are up, as far as
> > > I can tell. Both have the same name
On Sunday 03 September 2006 22:41, Loïc Minier wrote:
> Hi,
>
> On Fri, Sep 01, 2006, Carlos Moffat wrote:
> > Just to check, I tried madwifi-ng-{source,tools} r1587 from
> > snapshot.debian.net. That one didn't work either. I had to go back to
> > r1500 to be able to connect again. I hope
On Wednesday 06 September 2006 03:32, Andreas Janssen wrote:
> Package: hostapd
> Version: 1:0.5.5-1
> Severity: serious
> Justification: Policy 3.5
>
>
> hostapd 0.5.5 needs init script functions that are not available
> in older versions of lsb-base. Running a backport on Sarge
> results in:
>
>
On Wednesday 06 September 2006 05:24, Andreas Janssen wrote:
> The missing functions log_action_begin and log_action_end were
> introduced in lsb-base 3.0-6.
Ok, thanks. wpasupplicant packaging has been updated accordingly.
Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "
On Thursday 07 September 2006 17:37, Michel Xhaard wrote:
> Le Mercredi 6 Septembre 2006 05:54, Brad Sawatzky a écrit :
> > Package: spca5xx-source
> > Version: 20060501-1
> > Severity: important
> > Tags: patch
> >
> >
> > Some v4l header information got shuffled around in kernel 2.6.18. The
> >
On Tuesday 03 October 2006 11:46, Chip Salzenberg wrote:
> Package: madwifi-source
> Version: 1:0.9.2+r1710.20060914-1
> Severity: grave
> Justification: renders package unusable
>
> The drivers seem to build OK for kernel 2.6.16-2-686, but when I try to
> actually use them, I get a raft of "disagr
Package: powersaved
Version: 0.14.0-2
Severity: wishlist
Currently, powersaved has ipw2200 in a suspend blacklist, and it is
removed from kernel space before suspend and reinserted after resume. I
believe this is needlessly causing headaches for the end user, as
ipw2200 has supported suspend/resum
1 - 100 of 750 matches
Mail list logo
