Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Distribution: Fedora mainly, but I am open to others.
Posts: 273
Original Poster
Rep:
Great... now I'm getting this error after installing Wireshark from a tar.gz
Code:
Can't get pathname of Wireshark: "wireshark" not found in "/usr/bin:/bin".
It won't be possible to capture traffic.
Report this to the Wireshark developers.
Any idea how to remove something after doing a ./configure, make, make install?
Any idea how to check what firmware version of it I'm using? I'm using Fedora 9, 2.6.25.9-76.
Have a look in /lib/firmware, the file name has the version number as part of it.
Quote:
Any idea how to remove something after doing a ./configure, make, make install?
Try make uninstall. Hopefully that will do the trick. By the way, if you install from source, you might have a look at the checkinstall program. It can create RPM files that make life easier. It replaces the make install step.
Quote:
Well, I can load the ipwraw module for my card, load up Wireshark and run it in promiscuous mode without any problems. Running it with the iwl3945 module makes it crash.
To be honest, I'm really starting to believe that Fedora has patched something somewhere to cause this. I never have to touch the ipraw module for anything (although to be honest, wireshark is the only program I use that need promiscuous mode). Without any error messages, I'm just taking random shots and that probably isn't going to help much. What we probably need is someone MUCH more familiar with Fedora than I am. You might ask the mods to move this thread to the Fedora forum or ask on a different forum dedicated to Fedora.
Distribution: Fedora mainly, but I am open to others.
Posts: 273
Original Poster
Rep:
sudo make uninstall worked. Now I know! I have tried posting in Fedoraforum.org, no response whatsoever.
As far as the firmware version... I'm not seeing anything close to iwl3945.fw. The only thing that I can find is a iwl3945.ucode and iwl3945-1.ucode. This is strange.
I'll try a different distro, maybe an Ubuntu live CD and see if it works. I'll do that tonight and post my results.
The problem is you can't count on make uninstall because a LOT of source packages don't have it. That is what really got me using checkinstall (until it broke on Slackware and was more than replaced by src2pkg).
Quote:
As far as the firmware version... I'm not seeing anything close to iwl3945.fw. The only thing that I can find is a iwl3945.ucode and iwl3945-1.ucode. This is strange.
It's possible Fedora renamed it. However, this is a binary blob that nobody can alter, so you could get the newest firmware from the intel wireless site, put it in /lib/firmware and see if that helps. I would back up the existing firmware files just in case you need to roll back and you'll probably have to have only one set of iwl3945 firmware files in /lib/firmware.
Quote:
I'll try a different distro, maybe an Ubuntu live CD and see if it works. I'll do that tonight and post my results.
That wouldn't be a bad idea. When it comes to wireless, Fedora is a notable standout in the Linux world, and not in a good way.
Distribution: Fedora mainly, but I am open to others.
Posts: 273
Original Poster
Rep:
Well... I feel awfully f*cking stupid. I was trying to run Wireshark as sudo, not root, and it would crash. Running it as root (su) appears to have fixed the problem.
However, once running, it's impossible to browse websites, but it does intercept most of the packets it seems. It is a little... jumpy, glitchy... use whatever word you want. Is this normal? Just a side effect of the 3945 driver?
Well... I feel awfully f*cking stupid. I was trying to run Wireshark as sudo, not root, and it would crash. Running it as root (su) appears to have fixed the problem.
That's odd. I mean I do occasionally see a difference between su and sudo, but I use sudo all the time to run wireshark. I'm guessing there is some path or permissions differences between sudo and su that are the cause. Nice pick-up on your part because I wouldn't have guessed this one.
Quote:
However, once running, it's impossible to browse websites, but it does intercept most of the packets it seems. It is a little... jumpy, glitchy... use whatever word you want. Is this normal? Just a side effect of the 3945 driver?
It isn't a side effect of the driver, at least if my rig is any indication. I can run wireshark and browse without any problems. In fact promiscuous mode shouldn't prevent any traffic, otherwise tools like Snort wouldn't be usable. Again, I'm going to guess it is something about the way Fedora handles the driver. It seems to behave differently on your machine than it does on mine.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.