This bug was marked as a duplicate of bug #182716 as that bug also
necessitated the removal of that config option. It was closed FIX
RELEASED by the upload replicated below:
linux (2.6.24-12.19) hardy; urgency=low
* Re-upload of -12.18 to fix build failures
* Fixup binary-custom configs
*
** Also affects: linux (Ubuntu Hardy)
Importance: Undecided
Status: New
** Also affects: ndiswrapper (Ubuntu Hardy)
Importance: Undecided
Status: New
--
Conflict between Ndiswrapper and ssb
https://bugs.launchpad.net/bugs/188621
You received this bug notification because you
** Changed in: ndiswrapper (Ubuntu Hardy)
Status: New = Won't Fix
--
Conflict between Ndiswrapper and ssb
https://bugs.launchpad.net/bugs/188621
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: ndiswrapper (Ubuntu Hardy)
Status: Won't Fix = Invalid
--
Conflict between Ndiswrapper and ssb
https://bugs.launchpad.net/bugs/188621
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
As this bug was reported and fixed in Hardy I have nominated it there
and moved it FIX RELEASED. As the bug no longer existed in Intrepid and
later am moving the development task INVALID.
** Changed in: linux (Ubuntu Hardy)
Status: New = Fix Released
** Changed in: linux (Ubuntu Hardy)
This STILL is present in Ubuntu Intrepid (2.6.27-9). In my case b44
(wired connection) loads ssb before ndiswrapper (wifi). Blacklisting ssb
does not work because then wired connections fail, and update-initramfs
-u does nothing for me.
However, A far easier fix to the issue for end users is to
Agreed, I tend to recommend adding scripts to /etc/rc.local, as it is a
touch simpler, however creating a new init script is equally valid. This
bug is due to the initramd set up that Ubuntu uses, as explained in my
earlier post. For update-initramfs to actually do anything, it needs a
change in
If blacklisting ssb doesn't work for you then run sudo update-initramfs -u
See bug #227158 for details.
--
Conflict between Ndiswrapper and ssb
https://bugs.launchpad.net/bugs/188621
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
Assignee: (unassigned) = Ubuntu Kernel Team (ubuntu-kernel-team)
Status: Incomplete = Triaged
** Tags added: linux-2.6.27
--
Conflict between Ndiswrapper and ssb
https://bugs.launchpad.net/bugs/188621
You received this
This issue is still present in 2.6.27-2-generic. I've attached some test
output (removing ndiswrapper, loading ssb then reloading ndiswrapper)
which shows the device being claimed by the ssb module.
As an aside, it appears that the module `pcspkr' has been compiled into
this kernel. I tend to
It appears I hadn't posted my earlier findings on this bug report
either.
At least in my case, ssb was part of the initrd by default due to a
desire for eth0 to be up immediately (presumably for a network boot, if
desired). This requires b44 to be in the initrd which in turn requires
ssb to be
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
Hi everyone,
Would anyone care to confirm this is still an issue with the latest
Alpha for the upcoming Intrepid Ibex 8.10 -
http://www.ubuntu.com/testing. Please let us know your results.
Thanks.
** Changed in: linux (Ubuntu)
Status: New = Incomplete
--
Conflict between Ndiswrapper
** This bug is no longer a duplicate of bug 182716
bcm4306, bcm4309, bcm4311, bcm4312 with b43 : Authentication with AP doesn't
work.
--
Conflict between Ndiswrapper and ssb
https://bugs.launchpad.net/bugs/188621
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 182716 ***
https://bugs.launchpad.net/bugs/182716
Sorry, the packages are NDISGTK and ndiswrapper-utils-1.9
--
Conflict between Ndiswrapper and ssb
https://bugs.launchpad.net/bugs/188621
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 182716 ***
https://bugs.launchpad.net/bugs/182716
I make ndiswrapper works with a broadcom wirelles board with a following
procedure on a clean install of hardy
First, install the packages ndis and ndiswrapper-utils-1.9
Second, install driver from broadcom
*** This bug is a duplicate of bug 182716 ***
https://bugs.launchpad.net/bugs/182716
And I forgot to say that the free drivers for broadcom has to be
blacklisted by adding these lines on /etc/modprobe.d/blacklist
blacklist bcm43xx
blacklist b43
blacklist b43legacy
blacklist b44
--
Conflict
*** This bug is a duplicate of bug 182716 ***
https://bugs.launchpad.net/bugs/182716
confirmed for me too on hardy Rc.
Card :4312 rev 1
b43 works but with ultra low rates (1 mb/s) and i'm 1 meter away from my AP.
ndiswrapper won't launch.
--
Conflict between Ndiswrapper and ssb
*** This bug is a duplicate of bug 182716 ***
https://bugs.launchpad.net/bugs/182716
The workaround on rc is to load ndiswrapper BEFORE ssb. When is ssb
loaded on boot? Is there a clean way to make ndiswrapper loaded before
ssb?
--
Conflict between Ndiswrapper and ssb
*** This bug is a duplicate of bug 182716 ***
https://bugs.launchpad.net/bugs/182716
Conffirmed on Hardy Release Candidate at least for me
--
Conflict between Ndiswrapper and ssb
https://bugs.launchpad.net/bugs/188621
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 182716 ***
https://bugs.launchpad.net/bugs/182716
The duplicate status is wrong. The bug this is linked to is about an
authentication problem having nothing to do with ssb or ndiswrapper. This bug
and the following bugs seem awfully similar:
*** This bug is a duplicate of bug 182716 ***
https://bugs.launchpad.net/bugs/182716
I have tried this and other different work arounds. Neither ndiswrapper
nor the b43 driver are working on my Compaq R4125US laptop with Broadcom
4318 chip. Since I don't have access to a wired lan I've had
*** This bug is a duplicate of bug 182716 ***
https://bugs.launchpad.net/bugs/182716
My workaround for this bug is to create an init.d script (similar to the
original posters) with:
#!/bin/bash
rmmod b43 # Unloads the bad b43 driver
rmmod b44 # Unloads the ethernet driver temporarily since
*** This bug is a duplicate of bug 182716 ***
https://bugs.launchpad.net/bugs/182716
The bug 197558 seems to be the same.
--
Conflict between Ndiswrapper and ssb
https://bugs.launchpad.net/bugs/188621
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 182716 ***
https://bugs.launchpad.net/bugs/182716
Same bug here.
--
Conflict between Ndiswrapper and ssb
https://bugs.launchpad.net/bugs/188621
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
*** This bug is a duplicate of bug 182716 ***
https://bugs.launchpad.net/bugs/182716
I can confirm the problem with an Hardy Heron upgraded from Gutsy,
loading ndiswrapper before ssb solves the problem but it is only a
workaround.
--
Conflict between Ndiswrapper and ssb
*** This bug is a duplicate of bug 182716 ***
https://bugs.launchpad.net/bugs/182716
Sorry, I got this reference from a forum thread. Didn't know it was a
dupe. What's the original? Why hasn't this been resolved as a dupe of
it?
--
Conflict between Ndiswrapper and ssb
*** This bug is a duplicate of bug 182716 ***
https://bugs.launchpad.net/bugs/182716
Adam have you noticed the link at the top that says This bug is a duplicate of
...? Haven't noticed the message stamped above the textbox that says:
Remember, this bug report is a duplicate. Comment here
*** This bug is a duplicate of bug 182716 ***
https://bugs.launchpad.net/bugs/182716
Honestly? Nope. I actually went and looked specifically for such a thing
after reading your last message, and it either wasn't there or wasn't
noticeable. I see the one above the comment box now, but it still
*** This bug is a duplicate of bug 182716 ***
https://bugs.launchpad.net/bugs/182716
Hi all. We have this same issue on Mandriva (I'm encountering it on my
personal system and trying to figure it out; I'm not a kernel hacker,
just bashing away as best I can).
I have half of it figured out.
*** This bug is a duplicate of bug 182716 ***
https://bugs.launchpad.net/bugs/182716
Okay, further research. On Mandriva, ohci_hcd is apparently loaded on
all systems in the initrd, due to a change in mkinitrd. I suspect this
is the same in Ubuntu.
Basically this boils down to:
*** This bug is a duplicate of bug 182716 ***
https://bugs.launchpad.net/bugs/182716
and maybe stop to write into a duplicate bug report and instead use the
original one wdyt?
--
Conflict between Ndiswrapper and ssb
https://bugs.launchpad.net/bugs/188621
You received this bug notification
*** This bug is a duplicate of bug 182716 ***
https://bugs.launchpad.net/bugs/182716
the same problem, i am using:
Ubuntu Hardy (development branch) with 2.6.24-7-generic x86_64 and ndiswrapper
1.51, with the bash script the wireless card work fine.
--
Conflict between Ndiswrapper and ssb
*** This bug is a duplicate of bug 182716 ***
https://bugs.launchpad.net/bugs/182716
The same thing happened to me updating to kernel 2.6.24, on Suse 10.3 -
ndiswrapper 1.51. I also can work around it by unloading and reloading
modules.
--
Conflict between Ndiswrapper and ssb
Thanks for taking your time and reporting this bug.
Could you please paste the output of dmesg (when it doesn't work i.e. you
didn't reload the modules and when it works (when you have reloaded the
modules)).
--
Conflict between Ndiswrapper and ssb
https://bugs.launchpad.net/bugs/188621
You
I am having the same problem and can confirm the above commands worked
for me too. I don't know how to add this script to start up so I had to
sudo each of the above commands in terminal and then I get my network
up. I have attached my dmesg before running. Can you tell me how to
add this to
Sorry about the double post. I figured out how to add the script and I
have attached the output files requested. Let me know if you require
anything more.
** Attachment added: dmesg_after_fix
http://launchpadlibrarian.net/11744720/dmesg_after_fix
** Changed in: ndiswrapper (Ubuntu)
*** This bug is a duplicate of bug 182716 ***
https://bugs.launchpad.net/bugs/182716
It looks like this is ssb's fault and not ndiswrapper's (though this is only a
vague guess).
Do you still have a gutsy-installation at hand? If you do, try the latest
ndiswrapper with the gutsy kernel.
**
*** This bug is a duplicate of bug 182716 ***
https://bugs.launchpad.net/bugs/182716
Well I can confirm that yesterday using Gutsy ndiswrapper was working
fine. I had used the ndiswrapper 1.51 not the new 1.52 though. In
order to try it on gutsy unfortunately I would need to install it
*** This bug is a duplicate of bug 182716 ***
https://bugs.launchpad.net/bugs/182716
For MasterAslan:
1) U must create a file in /etc/init.d/ndiswrapper:
sudo nano /etc/init.d/ndiswrapper
1.a) and paste in it this text:
#! /bin/sh
### BEGIN INIT INFO
# Provides: ndiswrapper
#
*** This bug is a duplicate of bug 182716 ***
https://bugs.launchpad.net/bugs/182716
I have install ndiswrapper 1.51 with modules 2.6.24-5-generic
--
Conflict between Ndiswrapper and ssb
https://bugs.launchpad.net/bugs/188621
You received this bug notification because you are a member of
41 matches
Mail list logo
