2009/1/21 Micha Feigin <mi...@post.tau.ac.il>

> On Tue, 20 Jan 2009 23:17:57 +0800
> "Umarzuki Mochlis" <umarz...@gmail.com> wrote:
>
> ...
>
> > > > >> Looks from this thread
> > > > >> http://ubuntuforums.org/showthread.php?t=790778
> > > > >> that the driver may be problematic, he recommends using
> ndiswrapper.
> > > see
> > > > >> if
> > > > >> that makes iwlist work for you
> > > > >>
> > > > >
> > > > > when i got to the last step to load the .inf file, it says i didn't
> > > install
>
> Just thought about it, did you make sure that the original module (the one
> that
> is supposed to be blacklisted) is not loaded? Otherwise it will claim the
> wireless card first and it's not ndiswrapper that is in control for the
> test
>
> ...
>

I gues it is not. please take a look

Module                  Size  Used by
ppp_deflate             9216  0
zlib_deflate           23960  1 ppp_deflate
zlib_inflate           18944  1 ppp_deflate
bsd_comp                9600  0
ppp_async              13056  1
crc_ccitt               6528  1 ppp_async
ppp_generic            27816  7 ppp_deflate,bsd_comp,ppp_async
slhc                   10112  1 ppp_generic
binfmt_misc            13580  1
fglrx                2025780  25
vboxnetflt             85868  0
option                 17408  1
usbserial              36720  4 option
ppdev                  11656  0
parport_pc             31016  0
lp                     14724  0
parport                41776  3 ppdev,parport_pc,lp
ipv6                  288328  24
vboxdrv              1684268  1 vboxnetflt
loop                   19468  0
joydev                 14848  0
psmouse                42268  0
pcspkr                  7040  0
uvcvideo               55560  0
serio_raw               9860  0
compat_ioctl32         12288  1 uvcvideo
i2c_piix4              13072  0
videodev               35840  2 uvcvideo,compat_ioctl32
usbhid                 45792  0
snd_hda_intel         434904  7
i2c_core               27936  1 i2c_piix4
v4l1_compat            17284  2 uvcvideo,videodev
hid                    41792  1 usbhid
usb_storage            94528  0
ff_memless              9224  1 usbhid
snd_pcm                81672  3 snd_hda_intel
snd_seq                54304  0
snd_timer              25744  4 snd_pcm,snd_seq
snd_seq_device         11668  1 snd_seq
jmb38x_ms              13060  0
memstick               15792  1 jmb38x_ms
snd                    63688  15
snd_hda_intel,snd_pcm,snd_seq,snd_timer,snd_seq_device
soundcore              12064  1 snd
snd_page_alloc         13072  2 snd_hda_intel,snd_pcm
battery                16904  0
video                  24212  0
output                  7808  1 video
wmi                    11712  0
ac                      9352  0
button                 11680  0
shpchp                 34080  0
pci_hotplug            32056  1 shpchp
evdev                  14208  8
ext3                  125072  1
jbd                    51240  1 ext3
mbcache                12804  1 ext3
ide_pci_generic         9220  0 [permanent]
sg                     36448  0
sd_mod                 29376  3
sr_mod                 19652  0
cdrom                  37928  1 sr_mod
atiixp                  8324  0 [permanent]
ide_core              128284  2 ide_pci_generic,atiixp
ata_generic            10116  0
ahci                   33036  2
libata                165472  2 ata_generic,ahci
scsi_mod              160760  5 usb_storage,sg,sd_mod,sr_mod,libata
ehci_hcd               36108  0
dock                   14112  1 libata
r8169                  31492  0
ohci_hcd               25092  0
sdhci                  19460  0
mmc_core               52448  1 sdhci
thermal                22688  0
processor              42304  1 thermal
fan                     9352  0
thermal_sys            17728  4 video,thermal,processor,fan


Now I'm not too sure whether my wifi card is 4315 or 4312

09:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g
[14e4:4315] (rev 01)

>
> > > > >
> > > > did that, still iwlist eth1 scan produced the same output as before
> > > >
> > >
> > > does iwconfig say that you are still getting eth1 as the wireless
> > > interface?
> > > changing drivers can change the interface name
> > >
> >
> > yes it does
> >
>
> [...]
>
>
> --
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmas...@lists.debian.org
>
>


-- 
Regards,

Umarzuki Mochlis
http://gameornot.net

Reply via email to