tempestuous

Group: Members
Posts: 259
Joined: Aug. 2004 |
 |
Posted: Oct. 01 2005,03:24 |
 |
maxwas, M$ Window$ has indoctrinated us into relying on automatic stuff. I suggest you take control and set up things manually - ndiswrapper -i /path/to/my/drivers/myinffile.inf
Now to backup: open /home/dsl/filetool.lst in a text editor, list all files in /etc/ndiswrapper (don't include the leading /), and save. In the DSLpanel, press Backup/Restore, and Backup the files to your chosen device (probably hda2). When you boot from floppy, add the boot parameter "restore=hda2"
I could help you automate this by modifying /etc/lilo.conf, and then boot DSL from the Windows bootloader ... but I don't know how you have LILO set up at the moment and it could overwrite your MasterBootRecord ... so I won't go there.
Kenspank, DSL is probably detecting your MA111 and loading the native Linux driver for it - prism2_usb. Run "lsmod" to confirm.
Why would you want to use ndiswrapper when this better driver is ready to use?
The prism2 driver family (linux-wlan-ng) does not support the Linux wireless extensions interface, that's why iwconfig can't see the wlan0 interface. Configuration is achieved from the DSLpanel > Prism2.
|