sony vaio z1 sp: no 'link up' using ndis

[email protected] (Torben Jaeger)
Newsgroups gmane.os.freebsd.devel.hardware,gmane.os.freebsd.current,gmane.os.freebsd.devel.mobile
Message-ID <[email protected]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

hi all,

testing ndis and all seems quite pretty, but .....

i can't get any 'link up' message.

1st of all some information:

FreeBSD vaio.jicken.de 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Mon Jan 26
19:26:35 CET 2004     [email protected]:/usr/obj/usr/src/sys/VAIO  i386

making ndis and loading kernel modules seems to be no problem:

Jan 28 05:38:40 vaio kernel: ndis0: <Intel(R) PRO/Wireless LAN 2100 3B
Mini PCI
Adapter> mem 0xd0201000-0xd0201fff irq 9 at device 11.0 on pci2
Jan 28 05:38:40 vaio kernel: can't re-use a leaf (ESS_ID)!
Jan 28 05:38:40 vaio kernel: ndis0: NDIS API version: 5.1
Jan 28 05:38:41 vaio kernel: ndis0: 802.11 address: 00:04:23:49:31:26
Jan 28 05:38:41 vaio kernel: ndis0: 11b rates: 11Mbps 2Mbps 1Mbps

the interface shows up in ifconfig:

ndis0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
~        ether 00:04:23:49:31:26
~        media: IEEE 802.11 Wireless Ethernet autoselect
~        status: no carrier
~        ssid ""
~        channel 1 authmode OPEN powersavemode OFF powersavesleep 100
~        wepmode OFF weptxkey 1

setting channel and ssid via ifconfig results in kernel panic. sorry,
no debugging compiled in to serve more information.
but it looks similar to other panics in the list, sth like that:

Fatal trap 12: page fault while in kernel mode
fault virtual address    = 0x0
fault code        = supervisor write, page not present

before panic'ing theres a message 'ndis0: link up'. also seen some
messages while playing around 'ndis0: failed to get bssid'.
also panic'ing when starting dhclient on ndis0 before up'ing the
interface manually.

any ideas what to test next? its an intel pro/wireless which is
reported to be working in other notebooks.

attached sysctl hw.ndis as attachment if there are some parameters to
tweak.

any paper which is describing the difference between ess_id, ssid,
bssid? or any paper which is describing all parameters? sysctl does
not show any further information than the key name.

hoping someone can help ....

thx in advance

torben
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFAF0QKq6Fy8gFIMs0RAuNFAJwPs+Iu+VsmV9VAcSb8fMR6P+cwqwCcDsJ9
a+nkJoEpc13iHAL4Bhd9rtQ=
=v36b
-----END PGP SIGNATURE-----

_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "[email protected]"
ndis (text/plain, 2.9 KB)
hw.ndis0.AdapterModel: PRO/Wireless LAN 2100 3B Mini PCI Adapter
hw.ndis0.CardType: 2
hw.ndis0.DriverDesc: Intel(R) PRO/Wireless 7100 LAN Card Driver
hw.ndis0.ESS_ID: <empty>
hw.ndis0.EnumPropPages32: W20NCPA.dll,AddWirelessPPToNCPA
hw.ndis0.NetType: WLAN
hw.ndis0.Adhoc_TxPower: 16
hw.ndis0.BSSMode: 1
hw.ndis0.BTCoexistence: 1
hw.ndis0.ChannelB: 11
hw.ndis0.ChannelBDefault: 11
hw.ndis0.ChannelMaskB: 34815
hw.ndis0.Diversity: 0
hw.ndis0.EncryptionKey1: 
hw.ndis0.EncryptionKey2: 
hw.ndis0.EncryptionKey3: 
hw.ndis0.EncryptionKey4: 
hw.ndis0.EncryptionKeyId: 1
hw.ndis0.Ess_TxPower: 0
hw.ndis0.FragmentationThreshold: 0
hw.ndis0.LongPreamble: 0
hw.ndis0.MBIT_1: 1
hw.ndis0.MBIT_2: 1
hw.ndis0.MBIT_5_5: 1
hw.ndis0.MBIT_11: 1
hw.ndis0.MUAuthenticationMode: 1
hw.ndis0.MUEncryptionAlgorithm: 1
hw.ndis0.PortType: 1
hw.ndis0.PowerIndex: 6
hw.ndis0.Provider: Intel
hw.ndis0.RadioEnable: 1
hw.ndis0.TxPower: 40
hw.ndis0.WEPKeyFormat: 1
hw.ndis0.BandMode: 4
hw.ndis0.ChannelA: 0
hw.ndis0.ChannelADefault: 0
hw.ndis0.ChannelMaskA: 0
hw.ndis0.CLSGUID: {2BC8F0A7-DC4E-4889-8375-C2151F70C331}
hw.ndis0.IBSSBandMode: 4
hw.ndis0.MBIT_6: 0
hw.ndis0.MBIT_9: 0
hw.ndis0.MBIT_12: 0
hw.ndis0.MBIT_18: 0
hw.ndis0.MBIT_24: 0
hw.ndis0.MBIT_36: 0
hw.ndis0.MBIT_48: 0
hw.ndis0.MBIT_54: 0
hw.ndis0.Environment: 1
hw.ndis0.NdisVersion: 0x00050001
hw.ndis0.BusType: 5
hw.ndis0.InterruptNumber: 9
hw.ndis0.DebugFlag: UNSET
hw.ndis0.ForceFail: UNSET
hw.ndis0.CPULock: UNSET
hw.ndis0.beaconInterval: UNSET
hw.ndis0.BCScan: UNSET
hw.ndis0.FWTxQueueTimeout: UNSET
hw.ndis0.FWScanKeepAliveTimeout: UNSET
hw.ndis0.StealthEnable: UNSET
hw.ndis0.AtimWindow: UNSET
hw.ndis0.Mandatory_BSS_ID: UNSET
hw.ndis0.MSDUTxRates: UNSET
hw.ndis0.MaxFrameSize: UNSET
hw.ndis0.TBDNumberPower: UNSET
hw.ndis0.RBDNumberPower: UNSET
hw.ndis0.MaxNumBDPerPacket: UNSET
hw.ndis0.RTS_Threshold: UNSET
hw.ndis0.FastPSP: UNSET
hw.ndis0.MaxPSP: UNSET
hw.ndis0.StationName: UNSET
hw.ndis0.PCCardPacketFilter: UNSET
hw.ndis0.ProfileName: UNSET
hw.ndis0.IntlRoaming: UNSET
hw.ndis0.Support8021x: UNSET
hw.ndis0.AssociatingTimeout: UNSET
hw.ndis0.EmptyListScanPeriod: UNSET
hw.ndis0.IdleListScanPeriod: UNSET
hw.ndis0.AcceptPortTypeCmdTimeout: UNSET
hw.ndis0.IntlTimeout: UNSET
hw.ndis0.LostAssociationTimeout: UNSET
hw.ndis0.ScanListValidPeriod: UNSET
hw.ndis0.NonAssocScanListValidPeriod: UNSET
hw.ndis0.DCScanListValidPeriod: UNSET
hw.ndis0.NonAssocScanTrigger: UNSET
hw.ndis0.NonAssocScanDelta: UNSET
hw.ndis0.EmptyListMaxPeriod: UNSET
hw.ndis0.IdleListMaxPeriod: UNSET
hw.ndis0.SweepTableRequestTimeout: UNSET
hw.ndis0.LostAssocDirectScanDelay: UNSET
hw.ndis0.AssociatingDirectScanDelay: UNSET
hw.ndis0.UseMACinEEPROM: UNSET
hw.ndis0.UseEEPROMParameters: UNSET
hw.ndis0.D0StandbyDisabled: UNSET
hw.ndis0.OEMNicType: 0
hw.ndis0.RadioEnableHW: 1
hw.ndis0.Version11aFW: 0.08.071
hw.ndis0.Version11bFW: 0.08.071
hw.ndis0.Version11aUc: 0.0.0.0
hw.ndis0.Version11bUc: 00000001
hw.ndis0.VersionEEPROM: 3
hw.ndis0.PBANumber: C25851001
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.