Bug 62382

Summary:	'wi' driver Netgear MA311 (PCI) Prism 2.5, VIA Apollo chipset mobo, 'wi' crash during boot
Product:	Base System	Reporter:	Murray Baker <murray_baker>
Component:	i386	Assignee:	freebsd-i386 (Nobody) <i386>
Status:	Closed FIXED
Severity:	Affects Only Me
Priority:	Normal
Version:	4.9-RELEASE
Hardware:	Any
OS:	Any

Description Murray Baker 2004-02-05 11:50:16 UTC

      During boot 'wi' detects Prism 2.5, then has varying symptoms.
* kernel page fault
* incorrect firmware version[s], eg 0.0.0 instead of 1.0.1 and 1.3.5
* incorrect firmware ID, 'Lucent' detected instead of Intersil.
* microuptime going backwards

It did boot once, then 'wicontrol' locked the machine solid.

Mobo is 'noname', chipset is labelled 'VXpro' but IDs as VIA apollo.
CPU is IDT WInchip.

A 'closed source os' seems to work correctly on same HW. Driver and WLAN
util seem to run ok, firmware updater worked ok. (I have not attempted
WLAN networking with this os.)

4.9 GENERIC on a notebook with D-Link DWL-650, also Prism 2.5, boots ok
and doesn't show these problems.

How-To-Repeat:       Same combination of HW?

Comment 1 murray_baker 2004-02-11 13:06:57 UTC

I have diagnosed and solved the problem.

PCI 2.1 mobo does not supply 3.3V power reqd by MA311.
(3.3V power mandatory on PCI 2.2 mobo, optional on PCI 2.1.)

Sufficient power was supplied by parasitic paths to get the MA311
partially working. I successfully ran the firmware upgrade flasher
on this mobo. Confusing!

MA311 is now in another mobo which does supply 3.3V power and I have
had the WLAN working. FreeBSD 4.9-REL at both ends.

Murray Baker.

Comment 2 Simon L. B. Nielsen freebsd_committer

2004-02-14 12:04:21 UTC

State Changed
From-To: open->closed

Submitter has resolved the issue which was hardware related. 

Thanks for letting us know what the real problem was.