Thread: [Ndiswrapper-general] Loading via pcmcia cardmanager
Status: Beta
Brought to you by:
pgiri
From: Oliver F. <ol...@fa...> - 2004-03-16 14:13:52
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi list, I have one 'problem' with the loading of the ndiswrapper module: if i set the 'wlan0' alias in the modules.conf, than the ndiswrapper module is loaded before the pcmcia card services are ready and it seems, that the driver doesn't find the hardware. I must unload the ndiswrapper module and reload it again, to start the driver successfully. Or i remove the wlan0 alias from modules.conf. But than i must load the module always by hand. Both is not like plug'n'play. Is there a known way to let the pcmcia cardmanager load the ndiswrapper module if it detects a card that is unsupported by the native drivers? My system is Mandrake 9.2 - -- Mit freundlichen Gr=FCssen, Oliver Friedrich -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFAVwrnJL9YbV++5+wRAt6+AJ4mAgEj0AI+slbNlvqltCOmQxoWQwCfUkVq UcrCw+Wswu9uqZhkX51bZzE=3D =3Dtusx -----END PGP SIGNATURE----- |
From: <az...@se...> - 2004-03-16 14:27:54
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Oliver Friedrich wrote: | I have one 'problem' with the loading of the ndiswrapper module: | if i set the 'wlan0' alias in the modules.conf, than the ndiswrapper | module is loaded before the pcmcia card services are ready and it seems= , | that the driver doesn't find the hardware. I must unload the ndiswrappe= r | module and reload it again, to start the driver successfully. Mayby to make a script that is run _after_ pcmcia is a solution? Regards, - -- ~ .''`. Torbj=F6rn Svensson, azoff (at) se (dot) linux (dot) org ~ : :' : 7EB9 2DC5 61AE DAB5 7099 BAC6 798E E39A DBDB 0CFD ~ `. `' http://azoff.homeip.net:8080/ | http://azoff.tty0.org ~ `-- http://www.se.linux.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFAVw7feY7jmtvbDP0RAgejAJ9jEq/MGNQS3M/8e1kN97Dodo6yCgCgoY5s fJXKiPs2XLl11ouxcusxzUI=3D =3Dl+AB -----END PGP SIGNATURE----- |
From: Oliver F. <ol...@fa...> - 2004-03-16 16:52:21
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Torbj=F6rn Svensson schrieb: | Oliver Friedrich wrote: | | I have one 'problem' with the loading of the ndiswrapper module: | | if i set the 'wlan0' alias in the modules.conf, than the ndiswrapper | | module is loaded before the pcmcia card services are ready and it see= ms, | | that the driver doesn't find the hardware. I must unload the ndiswrap= per | | module and reload it again, to start the driver successfully. | | Mayby to make a script that is run _after_ pcmcia is a solution? That will not (allways) work in my case. If i load the ndiswrapper module without the card present in the pcmcia slot, it is not possible to insert the card later and use it. I must then first unload the ndisdriver and load it again with the card present. And this allways happens if i want to transfer big amount of data and use my 3com 100mbit LAN card and want to change later. But there must be a way to insert the wlan later ... If i'm right, the 'driverloader' from Linuxant supports it to insert the wlan hardware after boot. But if this works over the cardmanager, i don't know ... - -- Mit freundlichen Gr=FCssen, Oliver Friedrich -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFAVzCNJL9YbV++5+wRAr6xAJ9j4L/HZC9gSCzhQTeU4rqoZxjOfgCbB4JH LASUBJPpkna2ggoa8+8LHVI=3D =3DnfdZ -----END PGP SIGNATURE----- |
From: <az...@se...> - 2004-03-16 17:32:12
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Oliver Friedrich wrote: | But there must be a way to insert the wlan later ... | If i'm right, the 'driverloader' from Linuxant supports it to insert th= e | wlan hardware after boot. But if this works over the cardmanager, i | don't know ... ndiswrapper is designed to register the card upon modprobing. If the card aint there, then it can't be registered. The only thing I could think of is to make an endless loop that checkes for new hardware, but it is not a good thing to have a kernel-module to do this, atleast I don't think so. Regards, - -- ~ .''`. Torbj=F6rn Svensson, azoff (at) se (dot) linux (dot) org ~ : :' : 7EB9 2DC5 61AE DAB5 7099 BAC6 798E E39A DBDB 0CFD ~ `. `' http://azoff.homeip.net:8080/ | http://azoff.tty0.org ~ `-- http://www.se.linux.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFAVzoLeY7jmtvbDP0RAuB4AKCGHUif0PCt5g347PNAkdDAN2oi6gCgw2Bl fay0dRHI43Xs62kNpmvkgM8=3D =3DVky3 -----END PGP SIGNATURE----- |
From: Oliver F. <ol...@fa...> - 2004-03-16 23:11:21
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Torbj=F6rn Svensson schrieb: | Oliver Friedrich wrote: | | But there must be a way to insert the wlan later ... | | If i'm right, the 'driverloader' from Linuxant supports it to insert = the | | wlan hardware after boot. But if this works over the cardmanager, i | | don't know ... | | ndiswrapper is designed to register the card upon modprobing. If the | card aint there, then it can't be registered. The only thing I could | think of is to make an endless loop that checkes for new hardware, but | it is not a good thing to have a kernel-module to do this, atleast I | don't think so. Because of this it would be a good idea to use the pcmcia cardmanager to load the ndiswrapper if a new network card is inserted. This would be the optimum. - -- Mit freundlichen Gr=FCssen, Oliver Friedrich -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFAV4kzJL9YbV++5+wRApzVAJ0V+DgbJiOXudJZRL53/EXJCzv/PwCfYswN 8N/8Wk4g5MU6s4SoZ8NSCys=3D =3DT7nR -----END PGP SIGNATURE----- |
From: <az...@se...> - 2004-03-16 23:19:48
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Oliver Friedrich wrote: | Because of this it would be a good idea to use the pcmcia cardmanager t= o | load the ndiswrapper if a new network card is inserted. This would be | the optimum. Yes, it would be. But if you don't whant it to get loaded by default then= ? Regards, - -- ~ .''`. Torbj=F6rn Svensson, azoff (at) se (dot) linux (dot) org ~ : :' : 7EB9 2DC5 61AE DAB5 7099 BAC6 798E E39A DBDB 0CFD ~ `. `' http://azoff.homeip.net:8080/ | http://azoff.tty0.org ~ `-- http://www.se.linux.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFAV4uMeY7jmtvbDP0RAvIcAJ9TBD8XZ7xFfSHq1YdbPVvqRa8I/ACgsq69 Eui8Ini1+J9dh4RR6jlsX0k=3D =3DDP+L -----END PGP SIGNATURE----- |
From: Oliver F. <ol...@fa...> - 2004-03-16 23:35:29
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Torbj=F6rn Svensson schrieb: | Oliver Friedrich wrote: | | Because of this it would be a good idea to use the pcmcia cardmanager= to | | load the ndiswrapper if a new network card is inserted. This would be | | the optimum. | | Yes, it would be. But if you don't whant it to get loaded by default th= en? What do you mean? With the cardmanager this would be work like this: The system is booted and the pcmcia services are started. this is in the most cases true for all laptops. After some time the user inserts a pcmcia card and the cardmanager searches for the right driver and loads it. The same would happen if the card was in the slot at boot time. After the start of the pcmcia services the driver for the card would be loaded. If i don't want to load a special driver for some hardware (in this case i want the ndiswrapper module to load if some unknown hardware is inserted), then i wouldn't search for a automatic solution ;) - -- Mit freundlichen Gr=FCssen, Oliver Friedrich -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFAV48sJL9YbV++5+wRAjCxAKCGXbWO9AnxP1cpr3gdOxlhbrTBAQCgmump +mKQAU6XJXWxu/l3nznZ0P8=3D =3D68kZ -----END PGP SIGNATURE----- |
From: <az...@se...> - 2004-03-16 23:50:55
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Oliver Friedrich wrote: | With the cardmanager this would be work like this: | The system is booted and the pcmcia services are started. this is in th= e | most cases true for all laptops. | After some time the user inserts a pcmcia card and the cardmanager | searches for the right driver and loads it. | | The same would happen if the card was in the slot at boot time. After | the start of the pcmcia services the driver for the card would be loade= d. | | If i don't want to load a special driver for some hardware (in this cas= e | i want the ndiswrapper module to load if some unknown hardware is | inserted), then i wouldn't search for a automatic solution ;) What will you do I you have a broken ndiswrapper and/or windowsdriver, then the kernel would get a panic and that's not good ;) Maybe I'm just to negative on this, but I think that it wouln't automaticly load a driver. Atleast not the kernel module. If you want this, then a user-space tool would be a solution if you can't set cardmanager to _not_ insert the modul if user don't want to. Btw, I have very litle experiense with cardmanager, so I could have got it hole wrong. Regards, - -- ~ .''`. Torbj=F6rn Svensson, azoff (at) se (dot) linux (dot) org ~ : :' : 7EB9 2DC5 61AE DAB5 7099 BAC6 798E E39A DBDB 0CFD ~ `. `' http://azoff.homeip.net:8080/ | http://azoff.tty0.org ~ `-- http://www.se.linux.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFAV5LXeY7jmtvbDP0RAomrAKCScuuBMthVW3fPT+uWfifzG9aR9wCcCgiY NvAEEmmGAyKeuvC/nAEvhG8=3D =3D5MsW -----END PGP SIGNATURE----- |
From: Oliver F. <ol...@fa...> - 2004-03-17 10:33:17
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Torbj=F6rn Svensson schrieb: | Oliver Friedrich wrote: | | With the cardmanager this would be work like this: | | The system is booted and the pcmcia services are started. this is in = the | | most cases true for all laptops. | | After some time the user inserts a pcmcia card and the cardmanager | | searches for the right driver and loads it. | | | | The same would happen if the card was in the slot at boot time. After | | the start of the pcmcia services the driver for the card would be loaded. | | | | If i don't want to load a special driver for some hardware (in this c= ase | | i want the ndiswrapper module to load if some unknown hardware is | | inserted), then i wouldn't search for a automatic solution ;) | | | What will you do I you have a broken ndiswrapper and/or windowsdriver, | then the kernel would get a panic and that's not good ;) | Maybe I'm just to negative on this, but I think that it wouln't | automaticly load a driver. Atleast not the kernel module. Ok, that's a point, but before you use the a automatism like this you would test the components, i think. And if it has happend, you could use the interactive startup of the bootup script and make shure, that the pcmcia services are not loaded ... normaly not a big thing | If you want | this, then a user-space tool would be a solution if you can't set | cardmanager to _not_ insert the modul if user don't want to. You mean something like the 'ndiswrapper' program that is used to add, list and remove the windows drivers, but as a deamon? This program could check, if it has a driver for the inserted hardware and load (if needed) the ndiswrapper module or could add a windows driver to a allready running ndiswrapper module (like loadndisdriver seems to do it). | | Btw, I have very litle experiense with cardmanager, so I could have got | it hole wrong. Me, too. But it was my first thought to make it over this way ... - -- Mit freundlichen Gr=FCssen, Oliver Friedrich -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFAWClvJL9YbV++5+wRAvq1AKCKS9R9mqlPoHMtteaoOw++6ag5pQCghvxK B8cSP4aIcThGA/IdHZiNr/Y=3D =3DcaEL -----END PGP SIGNATURE----- |
From: Luca C. <lu...@pc...> - 2004-03-17 10:57:47
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, on 03/17/04 11:33, Oliver Friedrich wrote: > Torbjörn Svensson schrieb: > | Oliver Friedrich wrote: > | | With the cardmanager this would be work like this: > | | The system is booted and the pcmcia services are started. this is in > the > | | most cases true for all laptops. > | | After some time the user inserts a pcmcia card and the cardmanager > | | searches for the right driver and loads it. > | | > | | The same would happen if the card was in the slot at boot time. After > | | the start of the pcmcia services the driver for the card would be > loaded. > | | > | | If i don't want to load a special driver for some hardware (in this > case > | | i want the ndiswrapper module to load if some unknown hardware is > | | inserted), then i wouldn't search for a automatic solution ;) AFAIK this is what the PCMCIA + Hotplug do: you insert a card, the hotplug searches for a driver and loads it > your card is configured. http://linux-hotplug.sourceforge.net > You mean something like the 'ndiswrapper' program that is used to add, > list and remove the windows drivers, but as a deamon? This program could > check, if it has a driver for the inserted hardware and load (if needed) > the ndiswrapper module or could add a windows driver to a allready > running ndiswrapper module (like loadndisdriver seems to do it). IMHO having another daemon when there's a general tool (the hotplug subsystem) is not a good solution. Thx, bye, Gismo / Luca -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Debian - http://enigmail.mozdev.org iD8DBQFAWC8eVAp7Xm10JmkRArgtAJ0V8hlf9jRVG/wElTm57C6cr4lnbwCcCSxG 6ZachD/VJqUEnRXVNuzHfL4= =w7RK -----END PGP SIGNATURE----- |
From: Oliver F. <ol...@fa...> - 2004-03-18 13:26:29
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Luca Capello schrieb: | Hello, | | on 03/17/04 11:33, Oliver Friedrich wrote: | |>>Torbj=F6rn Svensson schrieb: |>>| Oliver Friedrich wrote: |>>| | With the cardmanager this would be work like this: |>>| | The system is booted and the pcmcia services are started. this is = in |>>the |>>| | most cases true for all laptops. |>>| | After some time the user inserts a pcmcia card and the cardmanager |>>| | searches for the right driver and loads it. |>>| | |>>| | The same would happen if the card was in the slot at boot time. Af= ter |>>| | the start of the pcmcia services the driver for the card would be |>>loaded. |>>| | |>>| | If i don't want to load a special driver for some hardware (in thi= s |>>case |>>| | i want the ndiswrapper module to load if some unknown hardware is |>>| | inserted), then i wouldn't search for a automatic solution ;) | | AFAIK this is what the PCMCIA + Hotplug do: you insert a card, the hotp= lug | searches for a driver and loads it > your card is configured. | http://linux-hotplug.sourceforge.net | | |>>You mean something like the 'ndiswrapper' program that is used to add, |>>list and remove the windows drivers, but as a deamon? This program cou= ld |>>check, if it has a driver for the inserted hardware and load (if neede= d) |>>the ndiswrapper module or could add a windows driver to a allready |>>running ndiswrapper module (like loadndisdriver seems to do it). | | IMHO having another daemon when there's a general tool (the hotplug subsystem) | is not a good solution. | Ok, than we are back at the start of this discussion ;) How to tell the cardmanager (i think, part of the hotplug subsystem) to load the ndiswrapper module or signal an already loaded ndiswrapper module to load a new windows driver if needed? Perhaps the last point is not complicated to implement, because it seems, that the ndiswrapper recognizes the reinsert of an already loaded card and reinit the formerly loaded driver. Does the ndiswrapper get a general notification by the kernel that new hardware was detected or does the kernel only notifify the specific module for this hardware if loaded? If it is a general notification, than ndiswrapper could check, if it has a windows driver for it and load it additionally to an already initilized driver ... - -- Mit freundlichen Gr=FCssen, Oliver Friedrich -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFAWaOGJL9YbV++5+wRArwpAJkB7VkMgJwiYWgqqEH25azflup3KgCfaajH LqHr0YuSsnBGkPOr/5CFbm4=3D =3DS9K3 -----END PGP SIGNATURE----- |
From: Pontus F. <pon...@ta...> - 2004-03-18 14:20:54
|
On Thu, 2004-03-18 at 14:26, Oliver Friedrich wrote: > Ok, than we are back at the start of this discussion ;) > How to tell the cardmanager (i think, part of the hotplug subsystem) to > load the ndiswrapper module or signal an already loaded ndiswrapper > module to load a new windows driver if needed? A normal kernel module knows what driver it supports and declares this in the source. This information is used to create a /lib/modules/`uname -r`/modules.pcimap file which the hotplug-scripts can use to find the correct module for some pci-device. The problem is that ndiswrapper does not know in advance which cards it will support because we dynamically load the windows drivers. However you can manually edit the pcimap file if you feel like it. There are probably other smarter ways do do this but I leave that for somebody else to investigate. > > Perhaps the last point is not complicated to implement, because it > seems, that the ndiswrapper recognizes the reinsert of an already loaded > card and reinit the formerly loaded driver. > Does the ndiswrapper get a general notification by the kernel that new > hardware was detected or does the kernel only notifify the specific > module for this hardware if loaded? If it is a general notification, > than ndiswrapper could check, if it has a windows driver for it and load > it additionally to an already initilized driver ... Upon module loading ndiswrapper loads all installed drivers. After this we register with the PCI-subsystem as usual so as soon as a hotpluggable card (for example cardbus) is inserted we get notified the normal way. Pontus |
From: Oliver F. <ol...@fa...> - 2004-03-18 18:08:33
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Pontus Fuchs schrieb: | On Thu, 2004-03-18 at 14:26, Oliver Friedrich wrote: | | |>Ok, than we are back at the start of this discussion ;) |>How to tell the cardmanager (i think, part of the hotplug subsystem) to |>load the ndiswrapper module or signal an already loaded ndiswrapper |>module to load a new windows driver if needed? | | | A normal kernel module knows what driver it supports and declares this | in the source. This information is used to create a /lib/modules/`uname | -r`/modules.pcimap file which the hotplug-scripts can use to find the | correct module for some pci-device. The problem is that ndiswrapper doe= s | not know in advance which cards it will support because we dynamically | load the windows drivers. However you can manually edit the pcimap file | if you feel like it. There are probably other smarter ways do do this | but I leave that for somebody else to investigate. | | |>Perhaps the last point is not complicated to implement, because it |>seems, that the ndiswrapper recognizes the reinsert of an already loade= d |>card and reinit the formerly loaded driver. |>Does the ndiswrapper get a general notification by the kernel that new |>hardware was detected or does the kernel only notifify the specific |>module for this hardware if loaded? If it is a general notification, |>than ndiswrapper could check, if it has a windows driver for it and loa= d |>it additionally to an already initilized driver ... | | | Upon module loading ndiswrapper loads all installed drivers. After this | we register with the PCI-subsystem as usual so as soon as a hotpluggabl= e | card (for example cardbus) is inserted we get notified the normal way. | Ok, so the only left would be to load the ndiswrapper if a card is inserted and ndiswrapper is not running. I have tried it with 0.5+CVS: if i load the ndiswrapper module without a card present i can't insert the card at a later moment. In the dmesg i can read, that ndiswrapper loads all windows drivers [i have the drivers for my D-Link DWL-G650+ and for a Linksys 802.11g card installed] but it seems, that it deletes all devices (perhaps because it has not found them physically). If i now insert the card, ndiswrapper makes nothing, but the module is loaded. Can this behaviour be changed or is this impossible because of kernel restrictions? - -- Mit freundlichen Gr=FCssen, Oliver Friedrich -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFAWeWkJL9YbV++5+wRAovWAJ9iJRKkCAvaMaI5/IHe2PPxxKDOGwCffA9V PWhAHy/mrLsS0IflWps0n7g=3D =3DDvcJ -----END PGP SIGNATURE----- |
From: Cristiano De M. <dem...@na...> - 2004-03-19 15:09:06
|
Hi, download and install murasaki (http://www.dotaster.com/~shuu/linux/murasaki/) then add a line like this to /etc/murasaki/murasaki.pcimap: ndiswrapper <vendor_id> <device_id> 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 if you know <vendor_id> and <device_id> of your=20 WiFi card, otherwise starting first time murasaki service it will suggest you in /var/log/syslog the correct line to add to /etc/murasaki/murasaki.pcimap C. On Thu, 2004-03-18 at 15:20, Pontus Fuchs wrote: > On Thu, 2004-03-18 at 14:26, Oliver Friedrich wrote: >=20 > > Ok, than we are back at the start of this discussion ;) > > How to tell the cardmanager (i think, part of the hotplug subsystem) to > > load the ndiswrapper module or signal an already loaded ndiswrapper > > module to load a new windows driver if needed? >=20 > A normal kernel module knows what driver it supports and declares this > in the source. This information is used to create a /lib/modules/`uname > -r`/modules.pcimap file which the hotplug-scripts can use to find the > correct module for some pci-device. The problem is that ndiswrapper does > not know in advance which cards it will support because we dynamically > load the windows drivers. However you can manually edit the pcimap file > if you feel like it. There are probably other smarter ways do do this > but I leave that for somebody else to investigate. >=20 > >=20 > > Perhaps the last point is not complicated to implement, because it > > seems, that the ndiswrapper recognizes the reinsert of an already loade= d > > card and reinit the formerly loaded driver. > > Does the ndiswrapper get a general notification by the kernel that new > > hardware was detected or does the kernel only notifify the specific > > module for this hardware if loaded? If it is a general notification, > > than ndiswrapper could check, if it has a windows driver for it and loa= d > > it additionally to an already initilized driver ... >=20 > Upon module loading ndiswrapper loads all installed drivers. After this > we register with the PCI-subsystem as usual so as soon as a hotpluggable > card (for example cardbus) is inserted we get notified the normal way. >=20 > Pontus >=20 >=20 >=20 >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcli= ck > _______________________________________________ > Ndiswrapper-general mailing list > Ndi...@li... > https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general --=20 Cristiano De Michele E-mail: cristiano.demichele@phys.uniroma= 1.it Department of Physics Tel. : +39064457131 University of Rome "La Sapienza" Fax : +39064463158 Piazzale Aldo Moro 2 I-00185 Roma - Italy =09 |
From: Luca C. <lu...@pc...> - 2004-03-19 15:50:29
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, on 03/19/04 16:07, Cristiano De Michele wrote: > download and install murasaki > (http://www.dotaster.com/~shuu/linux/murasaki/) > then add a line like this to /etc/murasaki/murasaki.pcimap: > ndiswrapper <vendor_id> <device_id> 0x00000000 0x00000000 > 0x00000000 0x00000000 0x00000000 IIRC the same could be done configuring PCMCIA service man pcmcia Thx, bye, Gismo / Luca -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Debian - http://enigmail.mozdev.org iD8DBQFAWxayVAp7Xm10JmkRAjRJAJ9KU6E5SkwHlGCcYFCR/5vhil69IACeIhyp dFPi7NxXLr2ewvIMkjzxp2g= =trVc -----END PGP SIGNATURE----- |