gmane.linux.drivers.ndiswrapper.general

Re: (no subject)

boywhp w — 2012-01-01T01:26:44

good job!!!

------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox_______________________________________________
Ndiswrapper-general mailing list
Ndiswrapper-general< at >lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general

(no subject)

Giridhar Pemmasani — 2011-12-31T20:39:29

Stable version 1.57 has been released (took lot longer than expected, as Pavel Roskin kept fixing it!). Following is short summary of changes:

* Added support for Linux 2.6.35 - Linux 3.1
* Kernels as old as 2.6.14 are now supported
* IW_AUTH_MFP implemented
* Reserve stack before copying arguments when calling from Windows to Linux
  on x86_64
* Fixed a kernel panic if there are many devices for one driver and one
  fails to initialize
* Fixed a kernel panic with Marvell USB if ndiswrapper is reloaded
* Fixed support for AVM Fritz USB
* Loading drivers with unknown symbols is disallowed, it's a certain crash
* Fixed procfs registration if the network device is renamed
* Added more function stubs
* Build system improved
* Code cleanup, fixed many warnings, style issues and typos

Giri------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox_______________________________________________
Ndiswrapper-general mailing list
Ndiswrapper-general< at >lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general

Re: Any way to run 32 bit ndiswrapper on 64-bit Linux system?

Pavel Roskin — 2011-09-15T19:11:49

Hello!

On Thu, 15 Sep 2011 13:31:48 -0400
Mark _ <mark_aok< at >hotmail.com> wrote:


I think it should be possible to run ndiswrapper in a 32-bit virtual
machine using a device exported by the host.  The virtual machine could
have another network interface and act as a router with NAT for the
host.


The is no ia32-libs equivalent for the kernel.  All the kernel code
is supposed to run in the same CPU mode.


Let's consider the possibilities.

If ndiswrapper is 32-bit, another wrapper between ndiswrapper and the
kernel would be needed to change the CPU mode and translate the code.
The kernel may assume that all kernel code is 64-bit.  Some changes may
be needed to account for that.  Essentially, it would be a project to
load 32-bit modules into a 64-bit kernel.  My estimate is that it would
be an effort compared to writing ndiswrapper itself.  It's hard for
me to imagine any benefits for any other modules.

If ndiswrapper is 64-bit and runs the Windows driver natively in the
kernel mode, it would need to switch the mode in the interfaces between
Windows and Linux functions.  Those interfaces are already written in
assembler, so different versions would be needed that would switch the
CPU mode. ndiswrapper will need to be compiled with special flags so
that Windows types are defined as they would be on 32-bit Windows.
Again, there is a problem with the kernel preempting 32-bit kernel code.
That may be tricky to solve.

ndiswrapper could be changed to run Windows code in userspace like a
process.  Then ndiswrapper would need to incorporate support for a new
executable format.  ndiswrapper would need to handle exceptions from
the Windows code trying to access privileged operations, such as
writing to ports.  When running 32-bit drivers, ndiswrapper would need
to provide compatibility versions of all functions called by the
driver.  The kernel would have no problem preempting 32-bit
userspace.  This approach may be useful to make ndiswrapper more
acceptable for users, even without considering 32-bit support on 64-bit
kernels. It's something that could be attempted, but the effort would
be significant.

ndiswrapper could include an emulator for i386 architecture and run
drivers in the emulator.   That would make ndiswrapper useful on
non-x86 architectures, such as ARM.  On the other hand, it could make
ndiswrapper slower.  Also, bringing an emulator to the kernel code
would not be taken with enthusiasm by the kernel folks.

To sum up, I don't see any easy solutions.  And of the hard solutions,
the only one that is potentially maintainable (that is, somebody could
be found to keep that code working and fix bugs once it's implemented)
is moving drivers to the userspace.

Any way to run 32 bit ndiswrapper on 64-bitLinux system?

Mark _ — 2011-09-15T17:31:48

Hi,I am wondering if there is any way to run a 32 bit ndiswrapper binary on a 64-bit Linux system?  For example could something like ia32-libs be used?  If not, how much effort would be involved to get this to happen, would this require kernel changes, or just changes to ndiswrapper?Thanks,Mark       ------------------------------------------------------------------------------
Doing More with Less: The Next Generation Virtual Desktop 
What are the key obstacles that have prevented many mid-market businesses
from deploying virtual desktops?   How do next-generation virtual desktops
provide companies an easier-to-deploy, easier-to-manage and more affordable
virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/_______________________________________________
Ndiswrapper-general mailing list
Ndiswrapper-general< at >lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general

Re: Instability after ndiswrapper unloadwithUSB drivers

Pavel Roskin — 2011-08-29T15:16:36

Quoting Pavel Roskin <proski< at >gnu.org>:


The fix was to remove usb_init_urb(), which is wrong to use on URBs  
allocated by usb_alloc_urb().  usb_init_urb() was resetting URB  
refcount from 2 to 1, which caused freeing the URB twice.

The fix has been committed.

Re: Instability after ndiswrapper unloadwithUSB drivers

Pavel Roskin — 2011-08-29T02:12:58

Hello!

This is a follow-up for the previous message.

I think I have the culprit now.  I just don't have a fix.  In some  
cases, a urb can be freed twice.  First it's freed by the Linux USB  
code in usb_deregister() and then it's freed by our kill_all_urbs().   
Freeing a URB twice for the second time leads to decreasing the first  
byte of the freed memory by one.  That's where the reference count is  
located.

I tried a hack in kill_all_urbs() that would prevent freeing URBs with  
refcount 0x6b6b6b6b.  That made the instability disappear.  Of course,  
this hack depends on SLUB debug, and it's still possible that somebody  
would claim and use the freed memory, overwriting the poison before  
kill_all_urbs() gets there.

The fix would require that we call kill_all_urbs() before  
usb_deregister().  Ideally, all URBs associated with a device should  
be removed as soon as the device is disabled.  I tried several  
approaches, but I would get various kernel crashes, usually in a  
worker for some queue.

I checked the code, and it appears that we never cancel any workqueue.  
  Indeed, wrap_cancel_work() is never used.  That alone may be the  
reason.  Also, killed URBs are never removed from  
wrap_urb->complete_list.  There is quite a lot of code that needs to  
be fixed.

Instability after ndiswrapper unload with USBdrivers

Pavel Roskin — 2011-08-27T23:44:36

Hello!

I was too optimistic to write in a recent subversion commit that the  
USB problems in ndiswrapper have been fixed.  I managed to unload  
ndiswrapper several times in a row so I concluded that my fix  
(canceling an IRP before freeing it) was the right fix for the problem.

I still think my fix was correct.  Freeing an irp with a cancel  
routine is not a good idea.  But it wasn't relevant to the actual  
problem.  The actual problem happens if IoCancelIrp() is called  
directly from the Windows driver.  It doesn't happen every time.

As far as I can tell, there are three different problems, and it's not  
clear if they are connected.

1) The freed URB is accessed for writing after being freed.  I believe  
that's the real source of instability after ndiswrapper is unloaded.

2) IoCancelIrp() is called with an IRP that has stack location  
pointing the end of the memory allocated for the IRP.  That leads to  
reading dev_obj from random memory.  Fortunately, ndiswrapper's only  
implementation of cancel_routine doesn't use dev_obj at all.  I have a  
proof that IRP is set to that position in
IofCompleteRequest().  I think that function should be reviewed by  
somebody who knows Windows driver programming.  I have a simple fix  
that simply sends NULL instead of dev_obj in IoCancelIrp().  However,  
that fix doesn't fix the instability.

3) I get an occasional "invalid task" from  
NdisMSetInformationComplete(), which is racing against itself.   
However, it doesn't seem to be related to the instability after  
ndiswrapper unload.

As it stands now, the PCI support is pretty good, but USB support is  
quite unstable.  Maybe it doesn't matter for the end users that much,  
as they are unlikely to unload ndiswrapper.  But since we don't have a  
fix, it's hard to say definitely that the instability would only  
happen on the module unload.

I'll appreciate any help with those issues, as they delay the next release.

Re: 1.57-rc1

Pavel Roskin — 2011-08-22T19:59:01

On Sun, 21 Aug 2011 22:16:38 -0700 (PDT)
Giridhar Pemmasani <pgiri< at >yahoo.com> wrote:


It's not quite true.


This is not my change.  It's from Rene van Paassen.  I didn't even know
what MFP means until I started writing this message (it's management
frame protection).


This is mine, but it only fixed one type of crash.  Unloading
ndiswrapper with Marvell USB can destabilize the system.  I have no fix
for that, and I don't think I'll have it for 1.57.  I know that the
problem happens on both i386 and x64_64.

I'm removing that entry from ChangeLog now.  It's wrong to claim that
something is fixed when in fact it's just a little less broken than it
was.


That's by Dirk Schwendemann.


Some stubs were collected from patches on Sourceforge by different
authors.


Thank you for making the prerelease!

The feedback will be welcome.  Of course, not everything can be fixed
for the release, but maybe there is some simple stuff missing that would
make all the difference for some drivers.

1.57-rc1

Giridhar Pemmasani — 2011-08-22T05:16:38


Pavel Roskin has been working to improve ndiswrapper. In fact, all the changes in this release are by him. Following is short summary of changes:

* Added support for Linux 2.6.35 - Linux 3.1
* Kernels as old as 2.6.14 are now supported
* IW_AUTH_MFP implemented
* Reserve stack before copying arguments when calling from Windows to Linux
  on x86_64
* Fixed a kernel panic if there are many devices for one driver and one
  fails to initialize
* Fixed a kernel panic with Marvell USB if ndiswrapper is reloaded
* Fixed support for AVM Fritz USB
* Loading drivers with unknown symbols is disallowed, it's a certain crash
* Fixed procfs registration if the network device is renamed
* Added more function stubs
* Build system improved
* Code cleanup, fixed many warnings, style issues and typos

Please test this version as changes have been all over the place and if something is broken, it helps to know now than later. We expect to release 1.57 soon (couple of weeks at most).

Thanks,
Giri------------------------------------------------------------------------------
uberSVN's rich system and user administration capabilities and model 
configuration take the hassle out of deploying and managing Subversion and 
the tools developers use with it. Learn more about uberSVN and get a free 
download at:  http://p.sf.net/sfu/wandisco-dev2dev
_______________________________________________
Ndiswrapper-general mailing list
Ndiswrapper-general< at >lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general

Re: BUG: unable to handle kernel pagingrequest

Giridhar Pemmasani — 2011-05-07T17:35:12

l.exe:'IoUnregisterPlugPlayNotification'
l.exe:'IoRegisterPlugPlayNotification'
l.exe:'DbgPrintEx'


Those messages indicate this driver uses some functions not (yet) implemented in 
ndiswrapper.
I believe Atheros has open source driver now. If you have not tried it yet, 
please see if it
supports your device.

Giri------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd_______________________________________________
Ndiswrapper-general mailing list
Ndiswrapper-general< at >lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general

BUG: unable to handle kernel paging request

hymie! — 2011-05-07T11:46:23

Greetings.  I hope I'm doing this correctly.

I have a HP G62-355DX laptop running Linux 2.6.36 from Slackware.

This laptop has PCI Atheros Communications Inc. AR9285 Wireless Network 
Adapter (PCI-Express) (rev 01) network card.  It uses the Linux ath9k
driver, but I'm having problems with it.  Since I've used ndiswrapper
successfully in the past with my old laptop, I thought I'd give it a
try.

I downloaded the SVN trunk for revision 2729.  It compiled and installed
just fine, and the WinXP driver installed as well:

newlaptop-pts/5:/var/log% /usr/sbin/ndiswrapper -l
netathw : driver installed
        device (168C:002B) present (alternate driver: ath9k)

But when I try to modprobe it, I get this error:

May  7 07:11:52 laptop kernel: Disabling lock debugging due to kernel taint
May  7 07:11:52 laptop kernel: ndiswrapper (import:233): unknown symbol: ntoskrn
l.exe:'IoUnregisterPlugPlayNotification'
May  7 07:11:52 laptop kernel: ndiswrapper (import:233): unknown symbol: ntoskrn
l.exe:'IoRegisterPlugPlayNotification'
May  7 07:11:52 laptop kernel: ndiswrapper (import:233): unknown symbol: ntoskrn
l.exe:'DbgPrintEx'
May  7 07:11:52 laptop kernel: BUG: unable to handle kernel paging request at 00
1d8b6c
May  7 07:11:52 laptop kernel: IP: [<001d8b6c>] 0x1d8b6c
May  7 07:11:52 laptop kernel: *pde = 00000000 
May  7 07:11:52 laptop kernel: Oops: 0000 [#1] 
May  7 07:11:52 laptop kernel: last sysfs file: /sys/module/led_class/refcnt

(I've got the whole crash report if you want it)

Did I do something wrong?  Is there any help to be had?  Or do I need to
stick with the problematic ath9k driver?

Thank you very much.

--hymie!    http://lactose.homelinux.net/~hymie    hymie< at >lactose.homelinux.net
-------------------------------------------------------------------------------

------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd

Re: ndiswrapper-kmod-common

Hin-Tak Leung — 2011-03-08T17:24:25


Hmm, that was a bit harsh... I would try to answer the question first before saying 'ask the question somewhere else'. "ndiswrapper(x86-32)" is the 32-bit package. So there were some mismatch about what the initial poster asked for, etc and what the package provides. Anyhow, to run the 64-bit version of ndiswrapper (with a 64-bit kernel) you need the 64-bit version of the windows driver (AFAIK), which is a bit rarer.

In any case, the relevant place the initial poster need to download rpm packages are here:
http://download1.rpmfusion.org/free/fedora/updates/testing/14/x86_64/repoview/ndiswrapper.html

and there abouts.

And problem he might or might not have should be filed with http://www.rpmfusion.org/ (not fedora, since ndiswrapper is not shipped by redhat at all).

Just out of curiosity, what's the wlan hardware which isn't supported by the kernel to resort to ndiswrapper? May be using wireless-testing or compat-wireless (the bleeding-edge wireless part of the kernel) is a better answer to ndiswrapper.



      

------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d

Re: ndiswrapper-kmod-common

Pavel Roskin — 2011-03-07T16:39:37

Distribution specific question should be asked in the distribution 
specific lists or in the bug tracker of the distribution.

This list is about ndiswrapper itself, not about packaging.  You can try 
installing ndiswrapper from the source if your distribution fails to 
provide working packages.

ndiswrapper-kmod-common

Gerald Sloan — 2011-03-05T22:11:15

Hello,

I have been wrestling with the installation of akmod-ndiswrapper on my Fedora 14 64 bit machine. No matter what I do I get stopped by this message
 Failed dependencies:
    ndiswrapper-kmod-common >= 1.56 is needed by akmod-ndiswrapper-1.56-1.fc14.1.x86_64
What can I do? All of the repositories I download from show that 

Provides 

  * ndiswrapper = 1.56-1.fc14
  * ndiswrapper(x86-32) = 1.56-1.fc14
  * ndiswrapper-kmod-common = 1.56

The thing I need is in what I am trying to install...it is getting frustrating.

Jerry

------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d_______________________________________________
Ndiswrapper-general mailing list
Ndiswrapper-general< at >lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general

Need another release

Pavel Roskin — 2010-02-01T23:08:54

Hi, Giri!

We need another release.  It turns out that the i386 compilation was
broken since Linux 2.6.31.  The code assumed that Linux 2.6.31 and newer
export cmpxchg8b() on i386, but it wasn't true for any kernel version.

To anticipate future compile errors, I checked compilation with the
current linux-next branch, which includes changes scheduled for the
future kernels.  Everything was fine for i386 and x86_64.

I made a change to satisfy realtime kernels distributed by Ubuntu.  They
don't have init_MUTEX.

There is one big thing that needs to be done.  It's porting the
configuration from Wireless Extension to cfg80211.  Linux 2.6.33 will
disable wireless extensions unless some old wireless driver is enabled
(e.g. ipw2100).  That will surely result in user complaints.  But that
effort is better done in a separate release.

Re: problen driver USR5421 on linux 64bit

Pavel Roskin — 2010-01-26T18:18:02

That's a Vista driver (NDIS 6).  ndiswrapper only works with Windows XP
and older drivers.


No.  I suggest that you use the rndis_wlan driver from the Linux kernel.

problen driver USR5421 on linux 64bit

sacarde — 2010-01-24T09:09:34

hi,
  I have a usb-key wireless USrobotics 5421

in archlinux 32bit following this:  
http://sourceforge.net/apps/mediawiki/ndiswrapper/index.php?title=US_Robotics_USR805421
all works OK

I have problem installing it on archlinux 64bit
I use this: 
http://www.usr.com/support/5421a/5421a-files/5421-v6.01.19.10x64.exe

but I find only .inf file
and no .sys


can you help me?

thankyou

sacarde< at >tiscali.it


p.s.
http://sourceforge.net/projects/ndiswrapper/forums/forum/323168/topic/3526052/index/page/1


 

------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev

Re: Powerpc architecture

Pavel Roskin — 2010-01-19T20:03:55

No.  Only i386 and x86_64 architectures are supported.

Powerpc architecture

Raymond Norton — 2010-01-19T19:24:31

I have Ubuntu running on a G3 Powerpc, but cannot get the wireless to 
work. Will Ndiswrapper compile and install on a Powerpc?

------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev

Re: how many ethernet card support?

bobl — 2009-10-23T02:40:34

bobl 写道:
Oh, i just use ssh -v, it report the tcp session already established, 
and i write a simple C/S program use tcp, it's also OK. so TCP is OK.

Bob


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Ndiswrapper-general mailing list
Ndiswrapper-general< at >lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general

Re: how many ethernet card support?

bobl — 2009-10-23T02:31:59

Hin-Tak Leung 写道:
Thanks for your reply frist.

In fact, i only want to confirm ndiswrapper can support normal ethernal 
card... so i just do a test...

In my linux system, the BCM5751 work well use tg3 kernel driver. then i 
rmmod the tg3 driver, and use ndiswrapper plus windows driver. then can 
use "ping" but can't use ssh and firefox(http). so i think it's not 
friewall issue, because not change anything.

The different of TCP and ICMP is a good thread, thanks again!

Bob

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Ndiswrapper-general mailing list
Ndiswrapper-general< at >lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general