No,i'm using a Intel Wireless 2200, but i can connect fine before the RC
version.
El dl 28 de 04 de 2008 a les 22:21 +, en/na HDave va escriure:
> I can confirm this bug on Hardy with wireless device is a Broadcom
> BCM4328 (Vendor = 0x14E4, Product = 0x4328). I am using ndiswrapper
> still..
Alexander,
thanks. I wasn't sure it was correct either - it seemed to be showing
AP_SCAN 1 in the log files, and I thought the replacement should have
changed that to AP_SCAN 2. However, dpkg did seem to do a replacement, and
Synaptic showed an ubuntu2 version before, and an ubuntu4 version
afte
On Tue, Apr 1, 2008 at 8:23 AM, Gene Caldwell <[EMAIL PROTECTED]> wrote:
> wait, matt !
>
> I got the same error at the gpg key but it said fatal error and all further
> processing stopped...I sent an email to Alexander and am waiting now for a
> response. I just sent it 2 minutes agoshould
Alexander,
great instructions. I had to sudo a little bit more, and do an apt-get
update before it would install all the build dependencies. The only other
errors I got were not having your private GPG key to sign the packages! It
would be great if such simple instructions were obvious and ava
Gene,
oops, yes, I meant the reply to you! I've also been using linux for 4
years, and I know enough to figure things out - I don't need step-by-step
instructions (although they certainly help!). Having said that, I use
Ubuntu precisely because it doesn't force me to become an O/S expert - but
I
Alexander,
you are not alone! I happily submitted a bug for the ipw2200 chipset having
used the beta cd, but didn't have the first clue about building branches,
patches or whatever.I actually work in software development - I'm just
not familiar with these tools or procedures, and I don't have
bluej774,
On Tue, Mar 25, 2008 at 06:43:22PM -, bluej774 wrote:
> This bug did not occur for me in Dapper, Edgy, or Gutsy. It is
> occurring in Hardy. I use the ipw3945 driver.
Hardy does not use the ipw3945 driver, but rather the iwl3945 driver. The
issue with iwl3945 connectivity is bug
The branch is right at the top of the bug report web page, not in the
email.
cheers,
Matt.
On Mon, Mar 24, 2008 at 10:42 PM, Gene Caldwell <[EMAIL PROTECTED]>
wrote:
> "
> Alexander Sack wrote 1 hour ago: (permalink)
>
> please test the branch above. instructions on how to get it to your disc
Gene,
On Mon, Mar 24, 2008 at 04:30:48AM -, Gene Caldwell wrote:
> I strongly DISAGREE ! this bug is one bug only.
Well yes, that's certainly how it's being treated in the bug report, and
that's what I'm explaining is a problem. There are many discrete bugs being
discussed in this one bug re
NetworkManager is just a tool to control your network connections. It
assumes that you already have a network/wireless driver installed
correctly, which is either compiled in the kernel or is a kernel
module. So if you are having a trouble with the kernel driver for your
network card, you nee
Gene, the released fix appears to be for the upstream NetworkManager
package in GNOME, not the Ubuntu network-manager package that is linked
to the same bug report. Take a look at the bug page:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/50214
So hopefully that fix will make
On Tuesday 16 October 2007, Christiansen wrote:
> Great work Alexander and others ??, thanks for the well done work on
> this one.
>
> Tested the NM 0.6.5-0ubuntu16 from the repository on a buildin "IBM 11a/b/g
> Wireless LAN Mini PCI Adapter II" (Athero AR5212), a PCMCIA "Netgear
> WG511T" (Athero
On Friday 12 October 2007, Ludovico Fischer wrote:
> Hello, I managed to install the package but it does not work for me at
> the moment. I think though it may not be related directlyto the bug, but
> there seems to be a conflict with my manual setup (it says something
> like 'there is already a pi
Thanks for taking the initiative on this.
I've attached my syslog as requested. I have edited out a bunch of hex
dumps, b/c I don't know what they represent and I don't want to submit
my WPA key. If I edited out something you need, I can get you that
information if you can point me to some docum
On Mon, Aug 27, 2007 at 11:06:18AM -, Matthew Carpenter wrote:
> On Saturday 25 August 2007, Alexander Sack wrote:
> > On Thu, Aug 16, 2007 at 08:19:35AM -, Václav Šmilauer wrote:
^^
> > > I was able to work around this problem by killing
On Saturday 25 August 2007, Alexander Sack wrote:
> On Thu, Aug 16, 2007 at 08:19:35AM -, Václav Šmilauer wrote:
> > I was able to work around this problem by killing NetworkManager and
> > running NetworkManager --no-daemon from root console. Then it associated
> > with the hidden network just
On Thu, Aug 16, 2007 at 08:19:35AM -, Václav Šmilauer wrote:
> I was able to work around this problem by killing NetworkManager and
> running NetworkManager --no-daemon from root console. Then it associated
> with the hidden network just fine. I have to kill NetworkManager and run
> it again (w
On Friday 27 July 2007, clifford wrote:
> Hi guys. Just a suggestion. While I do not have a similar setup to test
> this in at the moment, I did have the same problem on a SuSE laptop
> recently, running kernel 2.6.22.1-default and wireless-tools-29pre10-22.
> Simply running "iwlist scan" seems to
On Thursday 26 July 2007, Alexander Sack wrote:
> On Tue, Jul 17, 2007 at 08:48:32AM -, Witold Krakowski wrote:
> > >>i want to see the fix for the kernel.
> >
> > Me too. The trouble is that the kernel team, the NM team and whoever else
> > doesn't seem to care. This damn fault is here since d
On Tue, Jul 17, 2007 at 06:27:33PM -, SPaul wrote:
> I've run into a similar problem on a laptop running Fiesty running
> 2.6.20-16-generic.
> iwconfig --version says it is Wireless-Tools version 28, compatible with
> v11-v20
> and the kernel is compiled with Wireless Extension v21. The mach
On Tue, Jul 17, 2007 at 08:48:32AM -, Witold Krakowski wrote:
> >>i want to see the fix for the kernel.
> Me too. The trouble is that the kernel team, the NM team and whoever else
> doesn't seem to care. This damn fault is here since dapper. I don't care
> about it too anymore as long as ther
As I already told, I made it work on one of my computers, but I certainly
didn't make any patch.
Ubuntu Kernel Team and Ubuntu NM team should sort it out. That's all. This
bug is here for well over a year and I think it's time to fix it. If the
Ubuntu developers don't care, neither do I.
2007/7/1
On Friday 15 June 2007, Witold Krakowski wrote:
> Recompiling the kernel by yourself certainly not, but there are kernel
> updates every now and then, so these kernels could be recompiled with
> drivers supported by current stable version of Wireless tools. This does
> make sense.
Indeed it does.
23 matches
Mail list logo
