Problems with bcm4318 wlan card on debian unstable (linux kernel 2.6.24)

2008-04-21 Thread Александър Емилов Годумов
I have a broadcom bcm4318 wireless lan card on an Acer Travelmate 2492
notebook. The problem i have with it is that since the introduction of
the new b43 driver i cannot get it work (before b43 i used ndiswrapper
and it worked fine). What i want to do is to set up an ad-hoc wireless
networ. Apparrently however b43 fails to set the wireless mode (which i
want to be ad-hoc) and also fails to set the essid. It does not appear
to have problems setting the wep key (at least i get no errors about
this). Here is some relevant information:

06:02.0 Network controller: Broadcom Corporation BCM4318 [AirForce One
54g] 802.11g Wireless LAN Controller (rev 02)
Subsystem: AMBIT Microsystem Corp. TravelMate 2410
Flags: bus master, fast devsel, latency 64, IRQ 21
Memory at d0002000 (32-bit, non-prefetchable) [size=8K]
Kernel driver in use: b43-pci-bridge
Kernel modules: ssb

debian:/home/hellfire# uname -r
2.6.24-1-686

debian:/home/hellfire# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet static
pre-up iptables-restore  /etc/iptables/iptables
hwaddress ether 00:16:36:A4:64:85
netmask 255.255.255.252
gateway 192.168.0.1
address 192.168.0.2
auto eth0

allow-hotplug wlan0
iface wlan0 inet static
address 172.16.0.1
netmask 255.255.0.0
wireless-mode Ad-Hoc
wireless-key s:x
wireless-essid Debian
auto wlan0

I must also point out that i have installed the correct firmware
(4.80.53.0) - when i installed b43-fwcutter it automatically downloaded
it and that ndiswrapper worked fine with the above mentioned interfaces
file. Also this is the exact error i get - i get it at startup when my
network initializes or when i restart the networking script

debian:/home/hellfire# /etc/init.d/networking restart
Reconfiguring network interfaces...Error for wireless request Set
Mode (8B06) :
SET failed on device wlan0 ; Invalid argument.
Error for wireless request Set ESSID (8B1A) :
SET failed on device wlan0 ; Invalid argument.
if-up.d/mountnfs[eth0]: waiting for interface wlan0 before doing NFS
mounts
done.

As a result iwlist scan cannot find the network i have tried to create.
It does hoever find other networks if they are present. Here is what
iwconfig and ifconfig say about wlan0:

debian:/home/hellfire# iwconfig
wmaster0  no wireless extensions.

wlan0 IEEE 802.11g  ESSID:Debian  
  Mode:Ad-Hoc  Frequency:2.412 GHz  Cell: 1A:B2:3F:BA:96:EC   
  Tx-Power=27 dBm   
  Retry min limit:7   RTS thr:off   Fragment thr=2346 B   
  Encryption key:6465-7473-6B69-7370-6F6D-656E-6A
  Link Quality:0  Signal level:0  Noise level:0
  Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
  Tx excessive retries:0  Invalid misc:0   Missed beacon:0

debian:/home/hellfire# ifconfig
wlan0 Link encap:Ethernet  HWaddr 00:16:cf:9c:5e:d1  
  inet addr:172.16.0.1  Bcast:172.16.255.255  Mask:255.255.0.0
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:85 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:0 (0.0 B)  TX bytes:12774 (12.4 KiB)

wmaster0  Link encap:UNSPEC  HWaddr
00-16-CF-9C-5E-D1-00-00-00-00-00-00-00-00-00-00  
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)



And finally here is what dmesg says:

debian:/home/hellfire# dmesg | grep b43
input: b43-phy0 as /class/input/input11
Registered led device: b43-phy0:tx
Registered led device: b43-phy0:rx
Registered led device: b43-phy0:radio


debian:/home/hellfire# dmesg | grep wlan0
Unknown InputIN=wlan0 OUT= MAC= SRC=172.16.0.1 DST=224.0.0.251 LEN=140
TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=120 
Unknown InputIN=wlan0 OUT= MAC= SRC=172.16.0.1 DST=224.0.0.251 LEN=140
TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=120 
Unknown InputIN=wlan0 OUT= MAC= SRC=172.16.0.1 DST=224.0.0.251 LEN=140
TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=120 
Unknown InputIN=wlan0 OUT= MAC= SRC=172.16.0.1 DST=224.0.0.251 LEN=128
TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=108 
Unknown InputIN=wlan0 OUT= MAC= SRC=172.16.0.1 DST=224.0.0.251 LEN=136
TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=116 
Unknown InputIN=wlan0 OUT= MAC= SRC=172.16.0.1 DST=224.0.0.251 LEN=136
TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=116 
Unknown InputIN=wlan0 OUT= MAC= 

Re: Problems with BCM4318 (Wireless LAN PCI Adapter WL-138G V2 )

2008-02-10 Thread Michael Buesch
On Sunday 10 February 2008 04:22:06 Pedro P wrote:
 
 Hi,
 
 My name is Javier and I'm a new in Linux. I have a problem with my wireless 
 card Broadcom
  (WL-138G V2). The firmware is installed but I can't connect  card. Also 
 NetworkManager
 doesn't detect wireless card.
 Can You help me?
 Regards,
 Javier
 
 Specifications of my system: (lsmod and dmesg)
 -
 [EMAIL PROTECTED]:~ lsmod
 Module  Size  Used by
 nls_iso8859_1   8192  1
 nls_cp437   9856  1
 vfat   16128  1
 fat52380  1 vfat
 iptable_filter  6912  0
 ip_tables  16324  1 iptable_filter
 ip6table_filter 6784  0
 ip6_tables 17476  1 ip6table_filter
 x_tables   18308  2 ip_tables,ip6_tables
 arc46016  2
 ipv6  268152  20
 ecb 7552  2
 blkcipher  10116  1 ecb
 ieee80211_crypt_wep 9088  1
 af_packet  29064  4
 cpufreq_conservative11272  0
 snd_pcm_oss50432  0
 snd_mixer_oss  20096  1 snd_pcm_oss
 cpufreq_userspace   8704  0
 snd_seq54452  0
 snd_seq_device 12172  1 snd_seq
 cpufreq_powersave   5888  0
 acpi_cpufreq   13192  0
 speedstep_lib   9220  0
 microcode  15372  0
 apparmor   40736  0
 loop   21636  0
 dm_mod 56880  0
 iTCO_wdt   14372  0
 intel_agp  27156  0
 i2c_i801   12560  0
 iTCO_vendor_support 7812  1 iTCO_wdt
 usb_storage80780  1
 parport_pc 40764  0
 agpgart35764  1 intel_agp
 parport37832  1 parport_pc
 cdc_ether   9984  0
 bcm43xx   419548  0
 firmware_class 13568  2 microcode,bcm43xx
 i2c_core   27520  1 i2c_i801
 rtc_cmos   12064  0
 snd_hda_intel 272796  1
 snd_pcm82564  2 snd_pcm_oss,snd_hda_intel
 snd_timer  26756  2 snd_seq,snd_pcm
 snd58164  9
 snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_hda_intel,snd_pcm,snd_timer
 soundcore  11460  1 snd
 snd_page_alloc 13960  2 snd_hda_intel,snd_pcm
 usbnet 21768  1 cdc_ether
 rtc_core   23048  1 rtc_cmos
 sr_mod 19492  0
 rtc_lib 7040  1 rtc_core
 cdrom  37020  1 sr_mod
 ieee80211softmac   34432  1 bcm43xx
 button 12432  0
 ieee80211  35400  2 bcm43xx,ieee80211softmac
 ieee80211_crypt 9728  2 ieee80211_crypt_wep,ieee80211
 ide_core  122948  1 usb_storage
 atl1   35980  0
 mii 9344  2 usbnet,atl1
 sg 37036  0
 sd_mod 31104  5
 ehci_hcd   34956  0
 uhci_hcd   27024  0
 usbcore   123372  6 usb_storage,cdc_ether,usbnet,ehci_hcd,uhci_hcd
 edd12996  0
 ext3  131848  1
 mbcache12292  1 ext3
 jbd68148  1 ext3
 fan 9220  0
 ata_piix   21380  2
 libata136776  1 ata_piix
 scsi_mod  140376  5 usb_storage,sr_mod,sg,sd_mod,libata
 thermal19848  0
 processor  40744  2 acpi_cpufreq,thermal
 
 [EMAIL PROTECTED]:~ dmesg
 
 
 bcm43xx: Number of cores: 4
 bcm43xx: Core 0: ID 0x800, rev 0xd, vendor 0x4243
 bcm43xx: Core 1: ID 0x812, rev 0x9, vendor 0x4243
 bcm43xx: Core 2: ID 0x804, rev 0xc, vendor 0x4243
 bcm43xx: Core 3: ID 0x80d, rev 0x7, vendor 0x4243
 bcm43xx: PHY connected
 eth1: register 'cdc_ether' at usb-:00:1d.1-1, CDC Ethernet Device, 
 00:11:e3:b3:50:7a
 usbcore: registered new interface driver cdc_ether
 bcm43xx: Detected PHY: Analog: 3, Type 2, Revision 7
 bcm43xx: Detected Radio: ID: 8205017f (Manuf: 17f Ver: 2050 Rev: 8)
 bcm43xx: Radio turned off
 bcm43xx: Radio turned off
 Linux agpgart interface v0.102 (c) Dave Jones
 parport_pc 00:06: reported by Plug and Play ACPI
 parport0: PC-style at 0x378 (0x778), irq 7, dma 3 
 [PCSPP,TRISTATE,COMPAT,EPP,ECP,DMA]
 Initializing USB Mass Storage driver...
 scsi4 : SCSI emulation for USB Mass Storage devices
 usb-storage: device found at 4
 usb-storage: waiting for device to settle before scanning
 iTCO_vendor_support: vendor-support=0
 scsi5 : SCSI emulation for USB Mass Storage devices
 usb-storage: device found at 2
 usb-storage: waiting for device to settle before scanning
 usbcore: registered new interface driver usb-storage
 USB Mass Storage support registered.
 ACPI: PCI Interrupt :00:1f.3[B] - GSI 19 (level, low) - IRQ 19
 iTCO_wdt: Intel TCO WatchDog Timer Driver v1.01 (21-Jan-2007)

Re: Problems with BCM4318 (Wireless LAN PCI Adapter WL-138G V2 )

2008-02-10 Thread Larry Finger
Pedro P wrote:
 Hi,
 
 My name is Javier and I'm a new in Linux. I have a problem with my wireless 
 card Broadcom
  (WL-138G V2). The firmware is installed but I can't connect  card. Also 
 NetworkManager
 doesn't detect wireless card.
 Can You help me?
 Regards,
 Javier
 
 Specifications of my system: (lsmod and dmesg)
 bcm43xx   419548  0

The b43 driver works much better than bcm43xx. Please get and configure kernel 
version 2.6.24.1. You 
will need new firmware as well.

Larry

___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev


Problems with BCM4318 (Wireless LAN PCI Adapter WL-138G V2 )

2008-02-02 Thread Pedro P

My name is Javier and I'm a new in Linux and I have a problem with my wireless 
card (Asus
WL-138G V2) Chipset: BCM4318 PCI.
I think that SUSE 10.30 must automaticly configure card but it can't make it.
KNetwork Manager doesn't detect any wireless net. My router accept dchp and 
wireless need
a password.
Only I can navigate with cable USB and not with wireless card.

Can you help me to configure wireless card?.
Thanks,
Javier

Tecnichal information about my sistem:
-
Linux: openSUSE 10.30

My computer (Tower):

AMIBIOS (American Megatrends, Inc)
version: 0506
Build Date: 08/06/07
Processor:
Type: Intel (R) Core (TM) 2 Quad CPU Q6600 @4
Speed: 2400 MHz
Count: 4
System Memory:
Usable Size: 2048 MB


The technical especifications for my Wireless Card are:

Card: Asus WL-138G V2, 54mbps
Chipset: BCM4318 PCI
PCI ID: 14e4:4318


Wireless LAN PCI Adapter WL-138G V2
Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller
[14e4:4318] (rev 02)
-
Ya.com ADSL 24h + Llamadas Nacionales y Locales 24h + Llamadas a MÓVILES.
Desde 9,95 €/mes+IVA. http://acceso.ya.com/ADSLllamadas/3mbvoz/
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev


Re: Problems with BCM4318 (Wireless LAN PCI Adapter WL-138G V2 )

2008-02-02 Thread David Cohen
Hi,

You'll be glad I am the one who answers that :-D

You need to send more accurate information about your system:
*Kernel version (just type 'uname -r' command)

*There are 2 possible drivers for your wifi card:
 - if your kernel version is = 2.6.23, probably your are using bcm43xx module
 - if it is = 2.6.24(-rc or not), problably you are using b43 module
Type lsmod | grep bcm43xx or lsmod | grep b43 (depending on your
module) and send the result

*Type dmesg and capture the debug information your module has written

*And finally: Did you install any bcm43xx-fwcutter or b43-fwcutter
package that downloaded any firmware?

Br,

David


On Feb 2, 2008 7:17 PM, Pedro P [EMAIL PROTECTED] wrote:

 My name is Javier and I'm a new in Linux and I have a problem with my 
 wireless card (Asus
 WL-138G V2) Chipset: BCM4318 PCI.
 I think that SUSE 10.30 must automaticly configure card but it can't make it.
 KNetwork Manager doesn't detect any wireless net. My router accept dchp and 
 wireless need
 a password.
 Only I can navigate with cable USB and not with wireless card.

 Can you help me to configure wireless card?.
 Thanks,
 Javier

 Tecnichal information about my sistem:
 -
 Linux: openSUSE 10.30

 My computer (Tower):

 AMIBIOS (American Megatrends, Inc)
 version: 0506
 Build Date: 08/06/07
 Processor:
 Type: Intel (R) Core (TM) 2 Quad CPU Q6600 @4
 Speed: 2400 MHz
 Count: 4
 System Memory:
 Usable Size: 2048 MB


 The technical especifications for my Wireless Card are:

 Card: Asus WL-138G V2, 54mbps
 Chipset: BCM4318 PCI
 PCI ID: 14e4:4318


 Wireless LAN PCI Adapter WL-138G V2
 Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN 
 Controller
 [14e4:4318] (rev 02)
 -
 Ya.com ADSL 24h + Llamadas Nacionales y Locales 24h + Llamadas a MÓVILES.
 Desde 9,95 €/mes+IVA. http://acceso.ya.com/ADSLllamadas/3mbvoz/

 ___
 Bcm43xx-dev mailing list
 Bcm43xx-dev@lists.berlios.de
 https://lists.berlios.de/mailman/listinfo/bcm43xx-dev


___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev


Re: Problems with BCM4318 (Wireless LAN PCI Adapter WL-138G V2 )

2008-02-02 Thread gavron
Awesome response.

E

PS There's the old tale about the monkeys in a cage.  You put bananas up 
in the center and give them a chair. Eventually one gets on the chair, 
and you use a firehose on them.  After a time as soon as any monkey goes 
toward the chair the others pull him down.. wanting to not get the 
firehose treatment.  Replace some monkeys.  Repeat.  After a time NO 
monkey will let ANY monkey go for the bananas but they don't actually 
know why... they've learned that all the other monkeys want to stop it 
so it must be a bad thing.  That's human nature.  It's an AWESOME 
THING when a person who earlier had issues with his driver and got them 
fixed is now able to help another person.  That's the opposite of the 
monkey thing.  Well done.  Oh sorry for ranting, so I moved it to the PS 
in hopes I don't get flamed ;)

David Cohen wrote:
 Hi,

 You'll be glad I am the one who answers that :-D

 You need to send more accurate information about your system:
 *Kernel version (just type 'uname -r' command)

 *There are 2 possible drivers for your wifi card:
  - if your kernel version is = 2.6.23, probably your are using bcm43xx 
 module
  - if it is = 2.6.24(-rc or not), problably you are using b43 module
 Type lsmod | grep bcm43xx or lsmod | grep b43 (depending on your
 module) and send the result

 *Type dmesg and capture the debug information your module has written

 *And finally: Did you install any bcm43xx-fwcutter or b43-fwcutter
 package that downloaded any firmware?

 Br,

 David


 On Feb 2, 2008 7:17 PM, Pedro P [EMAIL PROTECTED] wrote:
   
 My name is Javier and I'm a new in Linux and I have a problem with my 
 wireless card (Asus
 WL-138G V2) Chipset: BCM4318 PCI.
 I think that SUSE 10.30 must automaticly configure card but it can't make it.
 KNetwork Manager doesn't detect any wireless net. My router accept dchp and 
 wireless need
 a password.
 Only I can navigate with cable USB and not with wireless card.

 Can you help me to configure wireless card?.
 Thanks,
 Javier

 Tecnichal information about my sistem:
 -
 Linux: openSUSE 10.30

 My computer (Tower):

 AMIBIOS (American Megatrends, Inc)
 version: 0506
 Build Date: 08/06/07
 Processor:
 Type: Intel (R) Core (TM) 2 Quad CPU Q6600 @4
 Speed: 2400 MHz
 Count: 4
 System Memory:
 Usable Size: 2048 MB


 The technical especifications for my Wireless Card are:

 Card: Asus WL-138G V2, 54mbps
 Chipset: BCM4318 PCI
 PCI ID: 14e4:4318


 Wireless LAN PCI Adapter WL-138G V2
 Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN 
 Controller
 [14e4:4318] (rev 02)
 -
 Ya.com ADSL 24h + Llamadas Nacionales y Locales 24h + Llamadas a MÓVILES.
 Desde 9,95 €/mes+IVA. http://acceso.ya.com/ADSLllamadas/3mbvoz/

 ___
 Bcm43xx-dev mailing list
 Bcm43xx-dev@lists.berlios.de
 https://lists.berlios.de/mailman/listinfo/bcm43xx-dev


 
 ___
 Bcm43xx-dev mailing list
 Bcm43xx-dev@lists.berlios.de
 https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
   
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev


Re: Problems with BCM4318 (Wireless LAN PCI Adapter WL-138G V2 )

2008-02-02 Thread David Cohen
Hi,

On Feb 2, 2008 8:11 PM,  [EMAIL PROTECTED] wrote:
 Awesome response.

 E

 PS There's the old tale about the monkeys in a cage.  You put bananas up
 in the center and give them a chair. Eventually one gets on the chair,
 and you use a firehose on them.  After a time as soon as any monkey goes
 toward the chair the others pull him down.. wanting to not get the
 firehose treatment.  Replace some monkeys.  Repeat.  After a time NO
 monkey will let ANY monkey go for the bananas but they don't actually
 know why... they've learned that all the other monkeys want to stop it
 so it must be a bad thing.  That's human nature.  It's an AWESOME
 THING when a person who earlier had issues with his driver and got them
 fixed is now able to help another person.  That's the opposite of the
 monkey thing.  Well done.  Oh sorry for ranting, so I moved it to the PS
 in hopes I don't get flamed ;)

I know this old tale also. And I know other very old tale about open
source mailing list, where people once could ask and someone else just
answer. :)

Regards,

David

PS: I hope you didn't get flamed yet... you can still consider those beaches. :)



 David Cohen wrote:
  Hi,
 
  You'll be glad I am the one who answers that :-D
 
  You need to send more accurate information about your system:
  *Kernel version (just type 'uname -r' command)
 
  *There are 2 possible drivers for your wifi card:
   - if your kernel version is = 2.6.23, probably your are using bcm43xx 
  module
   - if it is = 2.6.24(-rc or not), problably you are using b43 module
  Type lsmod | grep bcm43xx or lsmod | grep b43 (depending on your
  module) and send the result
 
  *Type dmesg and capture the debug information your module has written
 
  *And finally: Did you install any bcm43xx-fwcutter or b43-fwcutter
  package that downloaded any firmware?
 
  Br,
 
  David
 
 
  On Feb 2, 2008 7:17 PM, Pedro P [EMAIL PROTECTED] wrote:
 
  My name is Javier and I'm a new in Linux and I have a problem with my 
  wireless card (Asus
  WL-138G V2) Chipset: BCM4318 PCI.
  I think that SUSE 10.30 must automaticly configure card but it can't make 
  it.
  KNetwork Manager doesn't detect any wireless net. My router accept dchp 
  and wireless need
  a password.
  Only I can navigate with cable USB and not with wireless card.
 
  Can you help me to configure wireless card?.
  Thanks,
  Javier
 
  Tecnichal information about my sistem:
  -
  Linux: openSUSE 10.30
 
  My computer (Tower):
 
  AMIBIOS (American Megatrends, Inc)
  version: 0506
  Build Date: 08/06/07
  Processor:
  Type: Intel (R) Core (TM) 2 Quad CPU Q6600 @4
  Speed: 2400 MHz
  Count: 4
  System Memory:
  Usable Size: 2048 MB
 
 
  The technical especifications for my Wireless Card are:
 
  Card: Asus WL-138G V2, 54mbps
  Chipset: BCM4318 PCI
  PCI ID: 14e4:4318
 
 
  Wireless LAN PCI Adapter WL-138G V2
  Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN 
  Controller
  [14e4:4318] (rev 02)
  -
  Ya.com ADSL 24h + Llamadas Nacionales y Locales 24h + Llamadas a MÓVILES.
  Desde 9,95 €/mes+IVA. http://acceso.ya.com/ADSLllamadas/3mbvoz/
 
  ___
  Bcm43xx-dev mailing list
  Bcm43xx-dev@lists.berlios.de
  https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
 
 
 
  ___
  Bcm43xx-dev mailing list
  Bcm43xx-dev@lists.berlios.de
  https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
 

___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev


Re: Problems with bcm4318

2006-04-30 Thread Michael Buesch
On Sunday 30 April 2006 06:33, Matej Cepl wrote:
 Hi,
 
 I have upgraded my kernel to 2.6.17-rc3 (on Debian/unstable) and 
 found that native driver (THANKS!!!) works just on every other 
 reboot. So, for example attached /var/log/messages contains 
 couple of oopses and other problems.
 
 Can anybody help me to make my native driver working reliably or 
 do I have to just have ndiswrapper as a backup and wait for the 
 next version of kernel?

Wait for 2.6.18-rc

-- 
Greetings Michael.


pgpw1nEIdL5ot.pgp
Description: PGP signature


Problems with bcm4318

2006-04-29 Thread Matej Cepl
Hi,

I have upgraded my kernel to 2.6.17-rc3 (on Debian/unstable) and 
found that native driver (THANKS!!!) works just on every other 
reboot. So, for example attached /var/log/messages contains 
couple of oopses and other problems.

Can anybody help me to make my native driver working reliably or 
do I have to just have ndiswrapper as a backup and wait for the 
next version of kernel?

Best,

Matěj
-- 
GPG Finger: 89EF 4BC6 288A BF43 1BAB  25C3 E09F EF25 D964 84AC
http://www.ceplovi.cz/matej/blog/, Jabber: [EMAIL PROTECTED]
23 Marion St. #3, (617) 876-1259, ICQ 132822213
 
He can compress the most words into the smallest idea of any man
I know.
  -- Abraham Lincoln


bcm4318.tar.bz2
Description: application/tbz


pgpSyFfmuarLE.pgp
Description: PGP signature