GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Doing anything administrative is a PITA with Ubuntu, but it's default configuration is perfect for what I do at work all day. The only complaint I have about it is the weird
Quote:
SIOCSIFFLAGS: Resource temporarily unavailable
thing it likes to do with wlan0 after a whole lot of "suspend/hibernate and wake" cycles. The only fix that I've found is to physically pull the battery out of the laptop for a few seconds. But except for installing nmap I can't think of anything that I needed on this laptop that wasn't ready to go in the first 15 minutes of the install being completed. It doesn't get me excited the way my slack boxes do, but it serves it's purpose 100% and lets me focus on my job instead of having to second guess my tools the way everyone else at work (I haven't won a single convert to linux, even though they'll want me to use my laptop to troubleshoot!) has to with their windows machines.
Doing anything administrative is a PITA with Ubuntu, but it's default configuration is perfect for what I do at work all day. The only complaint I have about it is the weird
thing it likes to do with wlan0 after a whole lot of "suspend/hibernate and wake" cycles. The only fix that I've found is to physically pull the battery out of the laptop for a few seconds. But except for installing nmap I can't think of anything that I needed on this laptop that wasn't ready to go in the first 15 minutes of the install being completed. It doesn't get me excited the way my slack boxes do, but it serves it's purpose 100% and lets me focus on my job instead of having to second guess my tools the way everyone else at work (I haven't won a single convert to linux, even though they'll want me to use my laptop to troubleshoot!) has to with their windows machines.
I have noticed that error usually occurs when a task is attempted to configure or set the device as a normal user. You need to be root to set or configure the device. Now, if this is just happening randomly; that is kinda weird.
Last edited by lupusarcanus; 03-15-2010 at 11:36 PM.
Googling seems to suggest it's fairly common. It's something that happens rarely, maybe every 2 or 3 weeks or less, and it always seems to happen when I've been suspending and waking a lot and when the laptop comes back up, the wireless doesn't follow. It is weird, but except for having to power down, it's not the end of the world. I don't really use the wireless that much anyway, or at least not compared to the ethernet.
Or here. Nowthen, children, I want you all to repeat after me: "Dependencies are not a problem with Slackware." If we all say that ten times, the whole Slackware "has no package-management and dependency-checking" myth will disappear.
I'm going nuts here trying to find a way to once and for all stop my speakers from picking up radio! It's ever so faint, but it gets to me...
I've tried moving the speakers, moving the power cord, unplugging other analog audio-related things (e.g. line in, microphone), none of which seem to help! I guess that's what I get for having cheap speakers
@ MrCode -- peobably the best solution will be to replace all the wires connecting the speakers to the computer, using decent shielded cables, and make sure that the shield is actually grounded to the computer, and that the motherboard is properly installed & grounded..
The cost & time involved may not be practical though -- getting better speakers would perhaps be easier, *IF* the problem is simply cheapo speaker wires & connectors.
FWIW, I too have cheapo speakers, but I don't get any radio but then again, I live in the sticks, so radio signals are perhaps less prevalent.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.