marvell wireless not working

i went through the stickies and searched google and the forums and could not come up with a fix for this. im pretty much a noob on linux. suse recognizes my car in the network settings but says that it is not configured.

Marvell Ethernet controller (Not connected)
BusID : 0000:05:00.0
Unable to configure the network card because the kernel device (eth0, wlan0) is not present. This is mostly caused by missing firmware (for wlan devices). See dmesg output for details.

any help would be greatly appreciated.

paintballpimp765 wrote:
> i went through the stickies and searched google and the forums and could
> not come up with a fix for this. im pretty much a noob on linux. suse
> recognizes my car in the network settings but says that it is not
> configured.

Use the stickies in the wireless forum. From them, you will learn how to provide
the data regarding the PCI or USB ID of your device. As the driver is not
loaded, I can say with some certainty that a driver for it is not included in
whatever kernel you are using, but we will have a better idea after you
determine the info.

Larry

02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8038 PCI-E Fast Ethernet Controller (rev 14)
05:00.0 Ethernet controller: Marvell Technology Group Ltd. Device 2a08 (rev 03)

02:00.0 0200: 11ab:4352 (rev 14)
05:00.0 0200: 11ab:2a08 (rev 03)

is that all the info you need? if not let me know thanks

im pretty sure its a driver too but i didnt know where to go about looking for it or anything?

paintballpimp765 wrote:
> 02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8038 PCI-E
> Fast Ethernet Controller (rev 14)
> 05:00.0 Ethernet controller: Marvell Technology Group Ltd. Device 2a08
> (rev 03)
>
> is that all the info you need? if not let me know thanks
>
> im pretty sure its a driver too but i didnt know where to go about
> looking for it or anything?

That device is for wired ethernet and uses the sky2 driver.

You need to relook at the lspci output to locate what wireless device you have.

Larry

no wireless device comes up, i know it works because on the windows side i have no problem with it.

paintballpimp765 wrote:
> no wireless device comes up, i know it works because on the windows side
> i have no problem with it.

It may be a USB device. Does the lsusb command show it? You will need the
usbutils package installed for that command to work.

Larry

the usbutils is already installed and it doesnt come up when i run the usb command. i read something about using ndiswrapper to install the drivers but that was on an ubuntu forum. is there anything like that that i can do?

paintballpimp765 wrote:
> the usbutils is already installed and it doesnt come up when i run the
> usb command. i read something about using ndiswrapper to install the
> drivers but that was on an ubuntu forum. is there anything like that
> that i can do?

The command is ‘lsusb’, not ‘usb’.

You can always use ndiswrapper, and you may have to. It depends on what device
you actually have and whether there is a native driver. Anything relating to
drivers is a kernel, not a distro, matter. The down side of ndiswrapper is that
it installs a Windows driver and gives it complete access to the machine with no
restrictions. If that driver has a bug (think Windows Blue Screen of Death), it
crashes Linux. Depending on how the bug corrupted the kernel, the crash may
appear to have come from an innocent component. For that reason, any non-GPL
licensed code sets a “tainted” flag in the kernel. If you subsequently have a
kernel oops, most developers will not look at your problem until you reproduce
it without ever loading any tainted code.

Larry

yea i used the right command and nothing came up. how would i go about installing a driver with ndiswrapper

paintballpimp765 wrote:
> yea i used the right command and nothing came up. how would i go about
> installing a driver with ndiswrapper

That is covered in the wireless subforum. The essential parts are to install the
ndiswrapper package for your kernel, obtain a suitable Windows driver for your
device. If you are using a 64-bit kernel, you need a 64-bit Windows driver, etc.
In addition, XP drivers tend to work better than Vista ones, just like in the
Microsoft world.

After you have all the parts, configure it the way described in the ndiswrapper
documentation.