You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!

Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.

If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.

Having a problem logging in? Please visit this page to clear all LQ-related cookies.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

Ok, I figured I would set up a virtual machine to play around with some of my wireless stuff. I have the usb adapter mentioned in the title and have some wierd stuff happening when I try to use it. In the virtual machine I have a fresh Slack64 13 install and no other packages added (except the guest additions). I have usb enabled with

Code:

none /proc/bus/usb usbfs devgid=83,devmode=664 0 0

in /etc/fstab on the host machine. When I try to bring up the wlan0 in the virtual machine with ifconfig wlan0 up, I get

Code:

SIOCSIFFLAGS: Connection timed out

I can bring it up just fine in my host machine. It seems it has something to do with being able to load the firmware into the device. After I enable it in the virtual machine, I also get

@ Kenichi Kato: Yes, I connected it via the usb devices. That's when I get the dmesg errors.

@ vociz: Yes, it is installed. It is a fresh Slack64 13.0 (full) install. It works fine in the host machine also running Slack64 13.0.

edit: Just thought of something. Could it be that the host os is loading the firmware when the device is plugged in, and that is keeping the guest from loading it and keeping it from working? I guess I'll try to blacklist the module(s) for it on the host os. I'll give it a shot when I get home.

# This is for the smc ezconnect
blacklist zd1211rw
blacklist mac80211
blacklist cfg80211

in /etc/modprobe.d/blacklist.conf. I unplugged the adapter, modprobe -r'd the modules in question, then plugged it back in. The host system is not doing anything whatsoever with the adapter. Fired up my Slack64 13 vm, same results as before. So, it looks like it's not a matter of the host os loading the firmware into the device.

edit: Seems this is a Linux only thing. I fired up my XP vm, and the smc adapter worked. Kernel bug?