LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Solaris / OpenSolaris (https://www.linuxquestions.org/questions/solaris-opensolaris-20/)
-   -   Status of Wireless Card support in OSOL 10 (https://www.linuxquestions.org/questions/solaris-opensolaris-20/status-of-wireless-card-support-in-osol-10-a-816848/)

Alexvader 06-28-2010 01:37 PM
Status of Wireless Card support in OSOL 10
 
Hi Forum,

Is there any prospect of Wifi Broadcom BCM 4312 being supported in a near future...?

BRGDS

Alex

lupusarcanus 06-28-2010 02:55 PM
I always thought the old BCM43xx required b43-fwcutter even on Linux boxes.

jlliagre 06-28-2010 03:51 PM
Did you try the NDIS wrapper or the Murayama run driver (or neither) ?

Alexvader 06-29-2010 12:52 PM
Hi jlliagre,

thanks for your reply :)

I did not try any of these...

Murayama run Driver is more stable than NDIS...?

Does it run for 64 bits...?

AFAIK NDIS is not very stable according to forums...

In Slackare or Arch I can create a kernel module, wl.ko, and load it at boot time...

Can't i do something different in (Open)Solaris...?

BRGDS

Alex

jlliagre 06-29-2010 08:18 PM
Quote:
Originally Posted by Alexvader (Post 4018458)
Murayama run Driver is more stable than NDIS...?
I have no experience with either, I use different hardware.
Quote:
Does it run for 64 bits...?
Yes.
Quote:
AFAIK NDIS is not very stable according to forums...
No idea. Here is the place to start if you want to explore that way: http://hub.opensolaris.org/bin/view/Community+Group+laptop/ndis
Quote:
In Slackare or Arch I can create a kernel module, wl.ko, and load it at boot time...

Can't i do something different in (Open)Solaris...?
There is no need to build (recompile) the drivers with Solaris as the kernel device driver interface is stable, unlike Linux. Outside that, the idea is similar. Follow instructions in the readme bundled with the driver. Here is the "run" one: http://homepage2.nifty.com/mrym3/taiyodo/run-0.0.6.tar.gz

Alexvader 07-16-2010 06:02 PM
Hi Jlliagre

Seems that release 134 of OpenSolaris runs in my HP Pavilion allright only thing for which there is no driver is the broadcom thing...

According to the readme in Murayama run driver

Quote:
1. Introduction

This is the ralink RT287x/RT307x usb2.0 to 802.11n wifi driver for Solaris.
It is distributed under the BSD license.

2. Specification of the driver

File name of the driver:
/kernel/drv/run

Special file name:
/dev/runN (where N is a unit number, typcally 0 for first device)
For example
% ifconfig run0

Tested OS version
solaris nevada 124
As run driver requires new usb and 802.11 framework of OpenSolaris.

Tested chips and usb devices
RT3070, Planex communications GW-USMicroN
RT3070, Logitex LAN-W150N/U2PSP
RT3070, Buffalo WLI-UC-GN
RT3070, Planex communications GW-USMini2N
RT2870, Planex communications GW-US300MiniS

3. Preparing for installation

(1) extract distributed source and binary files.
# gunzip -cd run-x.x.x.tar.gz | tar xf -

(2) Add hostname for the NIC device into the /etc/hosts file

(3) Making binaries (required for sparc platforms only)
If you want to test or install run on sparc, you need to make
sparc binaries using Forte C compiler or gcc 3.x.x. Do the following
operations before testing or installation:

(for sparc 64bit kernel with Sun C compilers)
% cd /.../run-x.x.x
% rm Makefile
% ln -s Makefile.sparcv9_suncc Makefile
% rm obj
% ln -s sparcv9 obj
% /usr/ccs/bin/make

(for sparc 32bit kernel with Sun C compilers)
% cd /.../run-x.x.x
% rm Makefile
% ln -s Makefile.sparc_suncc Makefile
% rm obj
% ln -s sparc obj
% /usr/ccs/bin/make

(for sparc 64bit kernel with gcc3)
% cd /.../run-x.x.x
% rm Makefile
% ln -s Makefile.sparcv9_gcc Makefile
% rm obj
% ln -s sparcv9 obj
% /usr/ccs/bin/make

(for sparc 32bit kernel with gcc)
% cd /.../run-x.x.x
% rm Makefile
% ln -s Makefile.sparc_gcc Makefile
% rm obj
% ln -s sparc obj
% /usr/ccs/bin/make

4. Installation

(1) goto the directory of distributed files.
# cd ..../run-x.x.x

(2) register the run driver with solaris.
# /usr/ccs/bin/make install
# ./adddrv.sh

(3) install your usb device to the PC.

(4) set up the network port
# ifconfig runN plumb ( where N is unit number, typcally 0 for first device)
# ifconfig -a ( you will see an entry for run0, ensure ethernet address is correct)
# wificonfig scan (check the nic receive beacon signal)
# wificonfig connect ESSID
# ifconfig runN HOSTNAME
# ifconfig runN ( ensure IP address is correct)
# ifconfig runN up ( and then you can test with ping, telnet, ftp ...)

5. Troubleshooting

Q. The system does not boot after the driver is installed.
A. Uninstall the usb device and reboot solaris. Then, unregister the driver:
# rem_drv run

Q. Solaris boots, but the network interface does not work.
A. Is the network interface running?

Execute 'ifconfig -a'. If you see an entry for runN, the driver is loaded
and working correctly.
Please check the configuration of the network interface.


Is an ethernet cable connected properly?

Please check if the network interface is receiving packets.
% snoop -P -d runN

If Solaris panics during you test, please send me the following information:
(1) /var/adm/messages

(2) Output of prtconf -pv when the usb device is inserted in a usb slot.

(3) Output of prtconf -vD when the usb device is inserted in a usb slot.

(4) Output of mdb
Solaris core dump consists of unix.N and vmcore.N which are created in
/var/crash/YOUR-HOST-NAME/ .

Execute 'mdb -k unix.N vmcore.N' and type the following subcommands.
$c (stack trace back will be printed)
::msgbuf (last messages are printed)
::threadlist -v (stack traves for all thread in the kernel)
^D (To quit mdb, type control-D)
My wifi card is not connected through USB...

How should i add the driver to my x86 OpenSolaris...?

There are only references to SPARC builds....

jlliagre 07-17-2010 07:45 AM
Quote:
Originally Posted by Alexvader (Post 4035831)
How should i add the driver to my x86 OpenSolaris...?
A good start would be to follow the installation instructions you posted.
Quote:
There are only references to SPARC builds....
That's because building the driver is not required for x86. It's already delivered in binary form.


All times are GMT -5. The time now is 05:13 AM.