Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
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.
Click Here to receive this Complete Guide absolutely free.
I need a help, the system remains frozen. I am hopeless ;-(
I have a USB Belkin G+ F5D7051 wireless adapter with Broadcom bcm4320 chip. I load win driver with ndiswrapper 1.47 in openSUSE 10.3.
The driver was installed correctly and hardware is present.
If run 'ndiswrapper -ma', the system booting returns 'Kernel panic - not syncing...', in other case, if run 'modprobe ndiswrapper' to turn the device, the system remains frozen when device is detect.
I have read that the kernel of Linux manage the usb energy, some devices need more energy and the kernel blocks it. I have added this line in the file /etc/udev/rules.d/99-custom.rules or .../05-udev-early.rules, but the problem is not resolved.
Please, someone knows of this?, I am patient but have to solve the problem of a third person to which I have to return him the computer as soon as possible.
I have observed that from time to time opens the nautilus window of the usb-storages, as if resumed the usb electrical sockets, perhaps be this the problem?, where the configuration hardware of the usb's can be modified in openSUSE?
Thanks in advance.
Last edited by dissident_goodchild; 11-30-2007 at 07:07 AM.
Reason: info added
1) Some (older) versions of ndiswrapper are incompatible with kernel versions after 2.6.21
2) Fedora automatically installs the FOSS b43 driver for Broadcom chipsets. If SUSE also does this, or installs the older bcm43xx driver, and you then install ndiswarpper, you could be trying to run two different drivers for the same hardware. Check ps -e | grep b43 to see if you've got any of the b43 drivers running.
Edit: And, since the b43 drivers are available, you could junk ndiswrapper and go with the FOSS solution.
Last edited by PTrenholme; 11-30-2007 at 09:54 AM.
Well, yes, it's possible that NMI could be your problem. What (if anything) do your log files, especially /var/log/messages, tell you?
Have you run a memchk to verify that you have no memory problems? One of the more common causes of "random" system freeze is bad memory.
Another common problem is a failing disk drive. Is your problem system's drive S.M.A.R.T., and are you running smartd to catch those messages?
Another common cause, and, I think, more likely in your case, is an apparent system freeze caused by a kernel "wait" for an interrupt from a network device. Those "waits," however, usually time-out after thirty to sixty seconds, although I've seen some systems where the time-out was defaulted to 300 seconds. Have you tried waiting for 5 to 10 minutes when the system seems "frozen" to see if it "thaws" and, hopefully, produces an error message that can point you in the correct direction?
I have expected to an hour but the system did not leave the comma.
I tested with the mentioned NMI but did not solve anything.
I am going to verify everything that you explain me. The truth is that the disk does some very rare sounds... but yes it is clear that the failure produces it the adaptor Belkin, if I do not plug in the adaptor the system does not freeze.
Memchk is not available. Smartd is running, How catching I those messages?
Your answer is very satisfactory because you have centered it in the possible causes, thanks.
Last edited by dissident_goodchild; 11-30-2007 at 06:25 PM.
Reason: language correction
I'm puzzled about one thing: Why, in your first dmsg output above, did udev rename the device as wlan2? Is it possible that the computer you're using has a "built-in" Atheros WiFi device? Did you ever try the computer without a WiFi card in the slot?
I saw wlan2 name. It is a computer of a third person, I had to utilize my usb D-Link to connect to internet and to be able to seek helps (wlan1). Also I installed the Belkin (wlan2) and perhaps therefore appears like wlan2, although I opt more by the process "force persistent names" of the system.
Belkin has left me a bad taste in one's mouth, because I am not sure if is a problem of the adapter or I know not to run.