linux-source-2.6.22 (2.6.22-13.40) gutsy; urgency=low
[Amit Kucheria]
* Enable CONFIG_VM86 for LPIA
- LP: #146311
* Update configuration files
* Disable MSI by default
* Add mmconf documentation
* Update configuration files
[Bartlomiej Zolnierkiewicz]
* ide-disk: workaround
linux-source-2.6.22 (2.6.22-13.40) gutsy; urgency=low
[Amit Kucheria]
* Enable CONFIG_VM86 for LPIA
- LP: #146311
* Update configuration files
* Disable MSI by default
* Add mmconf documentation
* Update configuration files
[Bartlomiej Zolnierkiewicz]
* ide-disk: workaround
Gutsy commit 8dedc62d72d630b6278420dad36652bfc7fd99b1.
** Changed in: linux-source-2.6.22 (Ubuntu)
Importance: Undecided => Medium
Status: Confirmed => Fix Committed
Target: None => ubuntu-7.10-rc
--
[prism2.5] doesn't associate for network-manager with hostap_cs
https://bugs.la
Looks pretty solidly like a kernel issue
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: New => Confirmed
--
[prism2.5] doesn't associate for network-manager with hostap_cs
https://bugs.launchpad.net/bugs/571
Ensuring that the kernel sends events on both the wifi and wlan
interface seems to make network-manager happy. I'll submit a patch.
--
[prism2.5] doesn't associate for network-manager with hostap_cs
https://bugs.launchpad.net/bugs/57146
You received this bug notification because you are a member
On Tue, 2007-09-25 at 15:18 +, Matthew Garrett wrote:
> and n-m never sees the association. I suspect that this is due to the
> event coming from wifi0 rather than wlan2. I'll take a quick look at
> this, but right now I lean towards blaming the kernel.
Does it behave any differently for you i
16:10:15.022391 wifi0Scan request completed
16:10:17.431952 wifi0New Access Point/Cell address:Not-Associated
16:10:17.476782 wlan2Set Mode:Managed
16:10:17.486940 wlan2Set Frequency:2.427 GHz (Channel 4)
16:10:17.498810 wlan2Set ESSID:"6bFair"
16:10:17.513736 wifi0
** Changed in: network-manager (Ubuntu)
Status: In Progress => Confirmed
--
[prism2.5] doesn't associate for network-manager with hostap_cs
https://bugs.launchpad.net/bugs/57146
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
The wext driver should be used with current versions of hostap but that
doesn't appear to be the problem. There is some interaction between the
driver and the firmware that is failing in some cases now. Probably the
next step would be to go back to versions of the kernel that worked and
compare t
Andrew,
the link is broken now ...
anyway, what was the outcome of this? Should NM use wext driver?
- Alexander
--
[prism2.5] doesn't associate for network-manager with hostap_cs
https://bugs.launchpad.net/bugs/57146
You received this bug notification because you are a member of Ubuntu
Bugs,
Thread begins here:
http://lists.shmoo.com/pipermail/hostap/2007-August/015927.html
--
[prism2.5] doesn't associate for network-manager with hostap_cs
https://bugs.launchpad.net/bugs/57146
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubu
On Sat, Aug 11, 2007 at 10:41:35PM -, Andrew Jorgensen wrote:
> . . . be good to contact the hostap devs and see if they think it
> should be working. Or at what firmware revision it should work. They
> may have a workaround or a clue about where the bug may be in the
> driver.
>
Would you
. . . be good to contact the hostap devs and see if they think it
should be working. Or at what firmware revision it should work. They
may have a workaround or a clue about where the bug may be in the
driver.
--
[prism2.5] doesn't associate for network-manager with hostap_cs
https://bugs.launc
Unfortunately I've tried the other card in the same machine against the
same networks. It does appear to be an issue between the driver and the
firmware. It would probably
--
[prism2.5] doesn't associate for network-manager with hostap_cs
https://bugs.launchpad.net/bugs/57146
You received this
On Wed, Aug 08, 2007 at 04:00:56AM -, Andrew Jorgensen wrote:
> On one of my systems I am enjoying a fully working network-manager
> system now! Even WPA2 is working perfectly. Oddly, though, on the
> other system I tested on I, like Michael, had no luck at all. I will
> test again on that s
BTW: I found a debian bug report re: the udev rule, too:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=365777
Of course this is related to how prism2_srec works, but it may be
confusing wpa_supplicant or something else, too.
--
[prism2.5] doesn't associate for network-manager with hostap_cs
No, my laptop's hardware's apparently hosed. The flasher program can't
communicate with it anymore.
I also have a PCMCIA card that has the prism2 hardware. I successfully
updated that card's firmware to 1.7.4 and it does seem to work fairly
well with network manager now (previously it had a really
sorry that irepeated my question ... just ignore that post:
... can someone confirm for now that the udev rule is wrong?
--
[prism2.5] doesn't associate for network-manager with hostap_cs
https://bugs.launchpad.net/bugs/57146
You received this bug notification because you are a member of Ubuntu
still present in 0.6.5-0ubuntu9 ?
--
[prism2.5] doesn't associate for network-manager with hostap_cs
https://bugs.launchpad.net/bugs/57146
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
You should be able to just flash it again with the correct firmware in
most cases.
I guess others will take that as a warning not to try flashing the
firmware. I'm very sorry to hear that it didn't go well for you.
Incidentally - I did retest my other card - it's an older hardware
version and ha
BTW: anyone know how to reflash the card if you flashed only the primary
firmware without the secondary?
--
[prism2.5] doesn't associate for network-manager with hostap_cs
https://bugs.launchpad.net/bugs/57146
You received this bug notification because you are a member of Ubuntu
Bugs, which is th
Ugh... hosed my card when I bungled the firmware upgrade :-(
--
[prism2.5] doesn't associate for network-manager with hostap_cs
https://bugs.launchpad.net/bugs/57146
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs m
OK, I found out that part of my problem was due to some udev rules that
had been generated back when the orinoco_pci driver was default. When
the hostap_pci driver loaded, udev forced the card to be named eth*,
rather than wlan*, which confuses the hostap_* and prism2_* programs.
I still have some
Hm... anyone have step-by-step instructions that work on gutsy? The
instructions there don't seem to work (prism2_srec claims that it wants
the PRISM2_NON_VOLATILE_DOWNLOAD and PRISM2_DOWNLOAD_SUPPORT to be
enabled, which do appear to be set in the gutsy kernel driver. Also, the
standalone hostap-d
It's rather involved but described well here (requires the hostap-utils
package):
http://linux.junsun.net/intersil-prism/
--
[prism2.5] doesn't associate for network-manager with hostap_cs
https://bugs.launchpad.net/bugs/57146
You received this bug notification because you are a member of Ubuntu
Here's the info from my non-working system:
[EMAIL PROTECTED]:~$ sudo hostap_diag eth1
Host AP driver diagnostics information for 'eth1'
NICID: id=0x8013 v1.0.0 (PRISM II (2.5) Mini-PCI (SST parallel flash))
PRIID: id=0x0015 v1.1.0
STAID: id=0x001f v1.4.9 (station firmware)
--
[prism2.5] doesn't
How does one go about updating the firmware on the hostap device?
--
[prism2.5] doesn't associate for network-manager with hostap_cs
https://bugs.launchpad.net/bugs/57146
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-b
On one of my systems I am enjoying a fully working network-manager
system now! Even WPA2 is working perfectly. Oddly, though, on the
other system I tested on I, like Michael, had no luck at all. I will
test again on that system and will try upgrading the card's firmware as
well since I know that
I'm not having any better luck with the latest network-manager (
0.6.5-0ubuntu9 ). It doesn't seem to respect roaming/non-roaming mode.
Is there any particular additional information I can provide that will
be of help?
--
[prism2.5] doesn't associate for network-manager with hostap_cs
https://bu
can you try with latest gutsy network-manager please?
--
[prism2.5] doesn't associate for network-manager with hostap_cs
https://bugs.launchpad.net/bugs/57146
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
Hmm, unfortunately at the moment neither works (gutsy, updated today) ,
although using the wext driver it times out faster.
--
[prism2.5] doesn't associate for network-manager with hostap_cs
https://bugs.launchpad.net/bugs/57146
You received this bug notification because you are a member of Ubunt
On Tue, Jul 31, 2007 at 02:16:50PM -, Andrew Jorgensen wrote:
> Does network-manager make the decision about which wpa-supplicant
> backend to use?
>
Yes it does ... what driver should be used ?
currently we have a few special cases. maybe we need another special
case ... or just use default
ok ... currently investigating.
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Alexander Sack
Status: New => In Progress
--
[prism2.5] doesn't associate for network-manager with hostap_cs
https://bugs.launchpad.net/bugs/57146
You received this bug notification beca
And, BTW, when I manually configure eth1 with the network-admin
adminstrative dialog, the connection works, and sudo ifup eth1 and sudo
ifdown eth1 do work fine:
Aug 2 13:03:10 localhost dhclient: There is already a pid file
/var/run/dhclient.eth1.pid with pid 134812041
Aug 2 13:03:10 localhost
Here's what happens when I load the hostap_pci driver with network-
manager loaded:
** Attachment added: "syslog lines related to hostap_pci and network-manager"
http://launchpadlibrarian.net/8669777/syslog%20lines%20during%20networkmanager%20connect.txt
--
[prism2.5] doesn't associate for
** Tags added: gutsy-regression
--
[prism2.5] doesn't associate for network-manager with hostap_cs
https://bugs.launchpad.net/bugs/57146
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
This is also problematic on my Thinkpad T30's internal miniPCI wireless
card. Orinoco_pci worked like a charm... it would be nice if orinoco_*
were included, even if those drivers were blacklisted by default.
--
[prism2.5] doesn't associate for network-manager with hostap_cs
https://bugs.launchpa
Ugh, my bad - hostap was integrated into the main kernel a while back
and the version numbers don't line up. I don't know what's causing this
stupid bug then. If one of the Ubuntu kernel devs wants me to mail them
a prism 2.5 pcmcia card I'd be happy to.
--
[prism2.5] doesn't associate for netw
I also want to add that this bug will be much more serious if the
orinoco_cs is not added back into the kernel package. Fixing this, on
the other hand, will make prism 2.5 chipsets work perfectly for most
people, including with network-manager.
--
[prism2.5] doesn't associate for network-manager
I believe I've found the reason that this bug still exists in gutsy:
The driver is version 0.4.4 (an unstable version released 2005-08-21)
while wpa-supplicant is version 0.6.0 (latest devel release). Wireless-
extensions support was added to the hostap driver in version 0.4.5
(2005-09-25). Updat
Does network-manager make the decision about which wpa-supplicant
backend to use?
--
[prism2.5] doesn't associate for network-manager with hostap_cs
https://bugs.launchpad.net/bugs/57146
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubunt
** Changed in: linux-source-2.6.20 (Ubuntu)
Sourcepackagename: linux-source-2.6.20 => network-manager
** Changed in: linux-source-2.6.17 (Ubuntu)
Status: Confirmed => Rejected
--
[prism2.5] doesn't associate for network-manager with hostap_cs
https://launchpad.net/bugs/57146
--
ubuntu-b
I've tried that I think, and it didn't help. I thought we had already
determined that the problem was that network-manager / wpa-supplicant
was choosing the wrong back-end driver.
--
[prism2.5] doesn't associate for network-manager with hostap_cs
https://launchpad.net/bugs/57146
--
ubuntu-bugs
What happens if you try setting the essid when the card is up? I haven't
had any problems with hostap_cs and my prism 2 using network-manager,
but I'm not using WEP or WPA.
--
[prism2.5] doesn't associate for network-manager with hostap_cs
https://launchpad.net/bugs/57146
--
ubuntu-bugs mailing
Bug 78037 may be informative. The workaround is:
sudo ifconfig [interface] down
sudo iwconfig [interface] essid [essid] key [key]
sudo ifconfig [interface] up
sudo dhclient3 [interface]
This just worked for me using WEP through both rt2500 and prism54 cards
in Feisty (bug 82711). Something like i
Reinhard, you're probably right that it's just not using the right
driver backend. My /etc/network/interfaces specifies the hostap driver
backend. Changing this to the wext driver backend causes it to exhibit
the same behavior as nm.
Using kernel package 2.6.20.5.1 (x86) on a Dell Latitude C600.
err, I'm not sure if I have understood you correctly. Can
associate/connect using the wpa- stanzas with 2.6.20? If it doesn't work
with NM, it might be that the driver backend algorithm is borked in
network manager. In order to fix that, please attach a working
/etc/network/interfaces to this bug.
Yes, I tried it with 2.6.20-5. There seems to be some progress as the
wpa- options in /etc/network/interfaces works now (as they did in the
dapper live-cd but not in edgy) but network-manager still isn't working.
That might make that a new bug. I'll let you decide that and I'll be
happy to help
** Summary changed:
- [prism2.5] doesn't associate
+ [prism2.5] doesn't associate for network-manager with hostap_cs
--
[prism2.5] doesn't associate for network-manager with hostap_cs
https://launchpad.net/bugs/57146
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu
49 matches
Mail list logo
