| Author |
Message |
Kevin Nathan
*nix forums Guru
Joined: 24 Mar 2005
Posts: 2026
|
 Posted: Sun Feb 06, 2005 7:46 pm Post subject:
Re: Hit the proverbial brick wall
|
|
|
On Sun, 06 Feb 2005 19:57:17 GMT
Thomas Davie <tdavie@rediffmail.com> wrote:
| Quote: | thanks for the reply!
|
Sorry I couldn't help more; I know how frustrating it is to be so close!
Broadcom is the culprit here, being *very* unresponsive to the Linux
community. Maybe the next version of SUSE will do better -- after all,
my TI card was unsupported in 9.1 (except for ndiswrapper) but 9.2 has
it covered.
At least you have it on the desktop box! :-)
--
Kevin Nathan (Arizona, USA)
Open standards. Open source. Open minds.
The command line is the front line.
Linux 2.6.8-24.11-default
1:42pm up 1 day 1:38, 9 users, load average: 0.61, 0.58, 0.54 |
|
| Back to top |
|
 |
Thomas Davie
*nix forums beginner
Joined: 03 Feb 2005
Posts: 12
|
| Posted: Sun Feb 06, 2005 7:00 pm Post subject:
Re: Hit the proverbial brick wall
|
|
|
John Kelly <john@noemail.com> wrote in news:sO6dnW8aMZn39pvfRVn-
hw@pipex.net:
| Quote: | I think wireless is one of the most common stumbling blocks at the
moment for Linux users and until the card manufacturers either provide
linux drivers or else open up the information necessary to write a
driver, the situation will remain.
Cheers anyway.
John
|
Not a problem, and agin you help is much appreciated. It waa/is a hobby,
and I will return to it at some point. At the moment. I'll turn my
attention to a real clunker I've got (Xerox 860 IPS that I rescued from a
realty company that was going to discard it....really old, but comes with
a built in track pad mouse and 8n inch floppies from aeons ago!).
regards.
Tom |
|
| Back to top |
|
|
Thomas Davie
*nix forums beginner
Joined: 03 Feb 2005
Posts: 12
|
| Posted: Sun Feb 06, 2005 6:57 pm Post subject:
Re: Hit the proverbial brick wall
|
|
|
Kevin Nathan <knathan@project54.com> wrote in
news:20050206120001.18f6e208@efreet.linux:
| Quote: | On Sun, 06 Feb 2005 18:37:28 GMT
Thomas Davie <tdavie@rediffmail.com> wrote:
I have concluded that SuSE/Linux is just not for me if I can't get it
working properly with this much effort.
Can you return that card and get one that has a supported chipset?
'ndiswrapper' is only a bandage until real drivers are written. For
example, I went through that kind of mess with my NetGear WG311 on
SUSE 9.1. Then I upgraded to 9.2, where there is now an 'acx_pci'
module and all I had to do was download the firmware (via YaST). So a
card based on TI ACX100 or ACX111 is now supported along with others
like prism and atheros . . .
|
Nope; it's an internal mini PCI card, and it is supported under
ndiswrapper. It is something that I am doing wrong  Just don't know
what (scratches head and sips another beer).
I'm not in any hurry to use SuSE. I just thought it was time to learn
something new about computers and decided that it was time to try Linux
on my laptop. Now, on one of my desktops it's a different matter
entirely. Works without a single hitch. I'll just go back to WinXP until
anither version comes along or until I by anothre laptop with internal
wirless that is supported.
thanks for the reply!
Tom |
|
| Back to top |
|
|
John Kelly
*nix forums Guru Wannabe
Joined: 20 Feb 2005
Posts: 158
|
| Posted: Sun Feb 06, 2005 6:10 pm Post subject:
Re: Hit the proverbial brick wall
|
|
|
Thomas Davie wrote:
| Quote: |
Continuing, rmmod ndiswrapper did not appear to do anything. It was at
this opint that the little Homer SImpson voice started to say 'a beer
would be good right about now'.
|
Yes, I sympathise... quite often the problem with Linux is just finding
that last little piece of information to complete all the work. Not
easy if you're not sure of what you are doing.
In any case, I would be trying to identify the files required for this
interface under ndiswrapper to get to the point where modprobe
ndiswrapper and ndiswrapper -l returned something meaningful.
I think wireless is one of the most common stumbling blocks at the
moment for Linux users and until the card manufacturers either provide
linux drivers or else open up the information necessary to write a
driver, the situation will remain.
Cheers anyway.
John |
|
| Back to top |
|
|
Kevin Nathan
*nix forums Guru
Joined: 24 Mar 2005
Posts: 2026
|
| Posted: Sun Feb 06, 2005 6:00 pm Post subject:
Re: Hit the proverbial brick wall
|
|
|
On Sun, 06 Feb 2005 18:37:28 GMT
Thomas Davie <tdavie@rediffmail.com> wrote:
| Quote: | I have concluded that SuSE/Linux is just not for me if I can't get it
working properly with this much effort.
|
Can you return that card and get one that has a supported chipset?
'ndiswrapper' is only a bandage until real drivers are written. For
example, I went through that kind of mess with my NetGear WG311 on SUSE
9.1. Then I upgraded to 9.2, where there is now an 'acx_pci' module and
all I had to do was download the firmware (via YaST). So a card based on
TI ACX100 or ACX111 is now supported along with others like prism and
atheros . . .
--
Kevin Nathan (Arizona, USA)
Open standards. Open source. Open minds.
The command line is the front line.
Linux 2.6.8-24.11-default
11:53am up 23:49, 8 users, load average: 0.78, 0.68, 0.59 |
|
| Back to top |
|
|
Thomas Davie
*nix forums beginner
Joined: 03 Feb 2005
Posts: 12
|
| Posted: Sun Feb 06, 2005 5:37 pm Post subject:
Hit the proverbial brick wall
|
|
|
John Kelly <john@noemail.com> wrote in news:C5WdnRpPxrY7wZvfRVn-
og@pipex.net:
| Quote: | It seems pretty comprehensive. If you work through that one step at a
time it should help you fix or at least pinpoint any problems with
ndiswrapper and getting connected to your router.
Let us know how far down the page you get ...
John
|
I went to that page, and started to work through everything there. It is
of course pretty demoralizing when you have no idea what you are doing
and just following instructions (it is appreciated nonetheless). The
firsts thing I noted was that I had three directories under ndiswrapper
for my card, and they were all empty. Not sure if they were supposed to
be or not. So I put the driver and the inf files in all three.
lsmod | grep ndiswrapper doesn't do anything, nor does modprobe
ndiswrapper, although it did on thursday night (?).
Continuing, rmmod ndiswrapper did not appear to do anything. It was at
this opint that the little Homer SImpson voice started to say 'a beer
would be good right about now'. The trouble is that so much information
is being presented when I go to the command line that I just do not know
what is pertinent and what is not. I'm very sure that I have missed
something which would allow someone to easily diagnose where I screwed
up, but....So, I thank you and everyone else very heartily for your help,
but I have concluded that SuSE/Linux is just not for me if I can't get it
working properly with this much effort.
regards
Tom |
|
| Back to top |
|
|
John Kelly
*nix forums Guru Wannabe
Joined: 20 Feb 2005
Posts: 158
|
| Posted: Sun Feb 06, 2005 5:07 pm Post subject:
Re: Second go at getting Wireless to work in SuSe and close to giving up.
|
|
|
Thomas Davie wrote:
| Quote: |
Mode: Managed Frequency:2.462 GHz Access Point: 00:00:00:00:00:00
Tx excessive retries: 0 Invalid misc:81 Missed beacon:0
I'm stumped (obviously ). At first I thought it was because I had the
wrong windows drivers, although I took these right from the system32
directory....
thanks for your help.
Tom
|
Tom, I don't use ndiswrapper but have you looked at the following page -
http://ndiswrapper.sourceforge.net/phpwiki/index.php/Troubleshooting
It seems pretty comprehensive. If you work through that one step at a
time it should help you fix or at least pinpoint any problems with
ndiswrapper and getting connected to your router.
Let us know how far down the page you get ...
John |
|
| Back to top |
|
|
Thomas Davie
*nix forums beginner
Joined: 03 Feb 2005
Posts: 12
|
| Posted: Sun Feb 06, 2005 2:25 pm Post subject:
Re: Second go at getting Wireless to work in SuSe and close to giving up.
|
|
|
John Kelly <john@noemail.com> wrote in
news:-tSdnYT31oNlapjfRVn-uQ@pipex.net:
| Quote: | Thomas Davie wrote:
and tail -50 /var/log/messages gives
an ungodly long message which I have absolutely no hope of typing in
on this second computer I am using to post (DOS box),
:-)
Sorry I didn't realise you couldn't cut and paste into your posts.
The ipv6 message isn't an issue. It was more what was happening when
it tried to bring up wlan0 I was interested in. No errors?
What is the output of iwconfig? That should show the correct SSID
etc... Does it?
|
The tail -50 /var/log/messages only gives 2 warnings, neither of which I
think is pertinent. 1) No PST tables matching the cpuid which may be
indicative of a broken bios (it most assuredly isn't), and 2) when
starting the firewall, it warns me that no interface is active.
Running iwconfig does not pick up my SSID (and my router is set to
broadcast at the moment, and at 100% power). Here are 2 interesting
lines from the output;
Mode: Managed Frequency:2.462 GHz Access Point: 00:00:00:00:00:00
Tx excessive retries: 0 Invalid misc:81 Missed beacon:0
I'm stumped (obviously ). At first I thought it was because I had the
wrong windows drivers, although I took these right from the system32
directory....
thanks for your help.
Tom |
|
| Back to top |
|
|
John Kelly
*nix forums Guru Wannabe
Joined: 20 Feb 2005
Posts: 158
|
| Posted: Sun Feb 06, 2005 9:57 am Post subject:
Re: Second go at getting Wireless to work in SuSe and close to giving up.
|
|
|
Thomas Davie wrote:
| Quote: | and tail -50 /var/log/messages gives
an ungodly long message which I have absolutely no hope of typing in on
this second computer I am using to post (DOS box),
|
:-)
Sorry I didn't realise you couldn't cut and paste into your posts. The
ipv6 message isn't an issue. It was more what was happening when it
tried to bring up wlan0 I was interested in. No errors?
What is the output of iwconfig? That should show the correct SSID
etc... Does it? |
|
| Back to top |
|
|
Thomas Davie
*nix forums beginner
Joined: 03 Feb 2005
Posts: 12
|
| Posted: Sun Feb 06, 2005 9:42 am Post subject:
Re: Second go at getting Wireless to work in SuSe and close to giving up.
|
|
|
John Kelly <johnk.dev.null@gmail.com> wrote in
news:Dt2dnbroPe_yXZjfRVn-rw@pipex.net:
| Quote: | You have no IP address allocated and no routes set up whatsoever. Run
the following two commands and then post the output...
|
I figured out that I was getting no IP address assigned by assigning
myself a static IP address which showed up, but alas, this did nothign.
Here is the output from /etc/init.d/network/restart
shutting down network interfaces:
eth0 device: Broadcomm Corporation BCM4401 100Base-t (rev02)
eth0 configuration: eth-id-00:03:25:08:b3:63
wlan0 device: Broadcomm Corporation BCM4306 802.11 b/g wireless
Contorller (rev 02)
Shutting down service network
Hint: you may set up mandatory devices in /etc/sysconfig/network/config
Setting up etwork interfaces
lo
lo IP address: 127.0.0.1/8
eth0 device: Broadcomm Corporation BCM4401 100Base-T (rev 01)
eth0 configuration: eth-id-00:03:25:08:b3:63
eth0 Startmode is 'off'
wlan0 device: Broadcomm Corporation BCM4306 802.11 b/g Wireless LAN
Controller (rev 02)
wlan0 warning: using no encryption
wlan0 (DHCP).....no IP address yet...backgrounding
Setting up network service
SuSEfirewall2: Warning no interface active
SuSEfirewall2: Firewall rules successfully set from
/etc/sysconfig/SuSEfirewall2
and tail -50 /var/log/messages gives
an ungodly long message which I have absolutely no hope of typing in on
this second computer I am using to post (DOS box), however one line may
be of interest....
linus kernel: wlan0: no IPv6 routers present
In interpreted this (perhaps incorrectly) to mean that I have my routing
configuration set up incorrectly.
Thanks for reading my posts and helping.
Tom |
|
| Back to top |
|
|
JohnK
*nix forums Guru Wannabe
Joined: 24 Feb 2005
Posts: 143
|
| Posted: Sun Feb 06, 2005 5:59 am Post subject:
Re: Second go at getting Wireless to work in SuSe and close to giving up.
|
|
|
Thomas Davie wrote:
| Quote: | Here are the results of ifconfig when logged in as root. I've not listed
the results for eth0 or lo, but please let me know if you want them....
wlan0 Link encap:Ethernet HWaddre 00:90:96:61:FE:0F
inet6 addr: fe80: :290:fe61:fe0f/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX Packets:0 errors:0 dropped:0 overruns:0 frame:0
TX Packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0b) TX bytes:2950 (2.8Kb)
Interrupt:10 Memory:d0004000-d0005fff
Running netstat -r gives the following;
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
thanks for reading my posts.
Tom
You have no IP address allocated and no routes set up whatsoever. Run |
the following two commands and then post the output...
/etc/init.d/network restart
tail -50 /var/log/messages
That might show what errors you are encountering. E.g. Mine looks like
this (etho is a disconnected rj45 LAN port and eth1 is the wireless) -
| Quote: | # /etc/init.d/network restart
Shutting down network interfaces:
eth0 device: Intel Corp. 82801CAM (ICH3) PRO/100 VE (LOM) Ethernet Controller (rev 42)
eth0 configuration: eth-id-00:d0:59:22:22:3e done
eth1 device: 3Com Corporation 3com 3CRWE154G72 [Office Connect Wireless LAN Adapter] (rev 01)
eth1 configuration: wlan-id-00:0f:cb:22:22:2a done
Shutting down service network . . . . . . . . . . . . . done
Setting up network interfaces:
lo
lo IP address: 127.0.0.1/8 done
eth0 device: Intel Corp. 82801CAM (ICH3) PRO/100 VE (LOM) Ethernet Controller (rev 42)
eth0 configuration: eth-id-00:d0:59:22:22:3e
eth0 is controlled by ifplugd done
eth1 device: 3Com Corporation 3com 3CRWE154G72 [Office Connect Wireless LAN Adapter] (rev 01)
eth1 configuration: wlan-id-00:0f:cb:22:22:2a
eth1 (DHCP) . . . . . no IP address yet... backgrounding. waiting
Setting up service network . . . . . . . . . . . . . . done
|
(eth1 is eventually leased an IP address successfully) and the messages...
| Quote: | # tail -50 /var/log/messages
Feb 6 06:33:05 suselinux dhcpcd[5742]: terminating on signal 15
Feb 6 06:33:05 suselinux dhcpcd-hook: Skipping 'ifdown $INTERFACE -o dhcp' call
Feb 6 06:33:07 suselinux dhcpcd[6216]: terminating on signal 15
Feb 6 06:33:07 suselinux kernel: eth1: islpci_close ()
Feb 6 06:33:12 suselinux ifup: No configuration found for cipsec0
Feb 6 06:33:12 suselinux ifplugd(eth0)[6668]: ifplugd 0.25 initializing.
Feb 6 06:33:12 suselinux ifplugd(eth0)[6668]: Using interface eth0/00:D0:59:22:22:3E with driver <e100> (version: 3.0.27-k2-NAPI)
Feb 6 06:33:12 suselinux ifplugd(eth0)[6668]: Using detection mode: SIOCETHTOOL
Feb 6 06:33:12 suselinux ifplugd(eth0)[6668]: Initialization complete, link beat not detected.
Feb 6 06:33:12 suselinux kernel: eth1: islpci_open()
Feb 6 06:33:12 suselinux kernel: eth1: resetting device...
Feb 6 06:33:12 suselinux kernel: eth1: uploading firmware...
Feb 6 06:33:12 suselinux kernel: eth1: firmware uploaded done, now triggering reset...
Feb 6 06:33:19 suselinux modify_resolvconf: Service dhcpcd modified /etc/resolv.conf. See info block in this file
Feb 6 06:33:22 suselinux kernel: eth0: no IPv6 routers present
Feb 6 06:33:23 suselinux kernel: eth1: no IPv6 routers present
Feb 6 06:36:37 suselinux ifplugd(eth0)[6668]: Exiting.
Feb 6 06:36:39 suselinux dhcpcd[6873]: terminating on signal 15
Feb 6 06:36:39 suselinux kernel: eth1: islpci_close ()
Feb 6 06:36:39 suselinux modify_resolvconf: restored /etc/resolv.conf.saved.by.dhcpcd.eth1 to /etc/resolv.conf
Feb 6 06:36:41 suselinux ifplugd(eth0)[7399]: ifplugd 0.25 initializing.
Feb 6 06:36:41 suselinux ifplugd(eth0)[7399]: Using interface eth0/00:D0:59:22:22:3E with driver <e100> (version: 3.0.27-k2-NAPI)
Feb 6 06:36:41 suselinux ifplugd(eth0)[7399]: Using detection mode: SIOCETHTOOL
Feb 6 06:36:41 suselinux ifplugd(eth0)[7399]: Initialization complete, link beat not detected.
Feb 6 06:36:41 suselinux kernel: eth1: islpci_open()
Feb 6 06:36:41 suselinux kernel: eth1: resetting device...
Feb 6 06:36:41 suselinux kernel: eth1: uploading firmware...
Feb 6 06:36:41 suselinux kernel: eth1: firmware uploaded done, now triggering reset...
Feb 6 06:36:48 suselinux modify_resolvconf: Service dhcpcd modified /etc/resolv.conf. See info block in this file
Feb 6 06:36:52 suselinux kernel: eth1: no IPv6 routers present
Feb 6 06:39:48 suselinux ifplugd(eth0)[7399]: Exiting.
Feb 6 06:39:51 suselinux dhcpcd[7604]: terminating on signal 15
Feb 6 06:39:51 suselinux kernel: eth1: islpci_close ()
Feb 6 06:39:51 suselinux modify_resolvconf: restored /etc/resolv.conf.saved.by.dhcpcd.eth1 to /etc/resolv.conf
Feb 6 06:39:52 suselinux ifplugd(eth0)[8111]: ifplugd 0.25 initializing.
Feb 6 06:39:52 suselinux ifplugd(eth0)[8111]: Using interface eth0/00:D0:59:22:22:3E with driver <e100> (version: 3.0.27-k2-NAPI)
Feb 6 06:39:52 suselinux ifplugd(eth0)[8111]: Using detection mode: SIOCETHTOOL
Feb 6 06:39:52 suselinux ifplugd(eth0)[8111]: Initialization complete, link beat not detected.
Feb 6 06:39:53 suselinux kernel: eth1: islpci_open()
Feb 6 06:39:53 suselinux kernel: eth1: resetting device...
Feb 6 06:39:53 suselinux kernel: eth1: uploading firmware...
Feb 6 06:39:53 suselinux kernel: eth1: firmware uploaded done, now triggering reset...
Feb 6 06:40:00 suselinux modify_resolvconf: Service dhcpcd modified /etc/resolv.conf. See info block in this file
Feb 6 06:40:04 suselinux kernel: eth1: no IPv6 routers present |
|
|
| Back to top |
|
|
Thomas Davie
*nix forums beginner
Joined: 03 Feb 2005
Posts: 12
|
| Posted: Sun Feb 06, 2005 1:16 am Post subject:
Re: Second go at getting Wireless to work in SuSe and close to giving up.
|
|
|
Thomas Davie <tdavie@rediffmail.com> wrote in
news:Xns95F4C47477ED8tdavie7mtsnet@63.223.5.254:
| Quote: | I haven't tried disabling the onboard ethernet, but I will check this
link and have a go!
thanks for reading/replying.
Tom
|
Nope, no effect.
Tom |
|
| Back to top |
|
|
Thomas Davie
*nix forums beginner
Joined: 03 Feb 2005
Posts: 12
|
| Posted: Sun Feb 06, 2005 12:18 am Post subject:
Re: Second go at getting Wireless to work in SuSe and close to giving up.
|
|
|
I haven't tried disabling the onboard ethernet, but I will check this link
and have a go!
thanks for reading/replying.
Tom |
|
| Back to top |
|
|
Thomas Davie
*nix forums beginner
Joined: 03 Feb 2005
Posts: 12
|
| Posted: Sun Feb 06, 2005 12:17 am Post subject:
Re: Second go at getting Wireless to work in SuSe and close to giving up.
|
|
|
"JohnK" <johnk.dev.null@gmail.com> wrote in news:1107532480.584990.228410
@c13g2000cwb.googlegroups.com:
| Quote: | I followed those instructions to a T, but no luck.
What do ifconfig and netstat -r say? Please post the output to the
group...
|
Here are the results of ifconfig when logged in as root. I've not listed
the results for eth0 or lo, but please let me know if you want them....
wlan0 Link encap:Ethernet HWaddre 00:90:96:61:FE:0F
inet6 addr: fe80: :290:fe61:fe0f/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX Packets:0 errors:0 dropped:0 overruns:0 frame:0
TX Packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0b) TX bytes:2950 (2.8Kb)
Interrupt:10 Memory:d0004000-d0005fff
Running netstat -r gives the following;
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
thanks for reading my posts.
Tom |
|
| Back to top |
|
|
sktsee
*nix forums addict
Joined: 25 Apr 2005
Posts: 55
|
| Posted: Fri Feb 04, 2005 3:53 pm Post subject:
Re: Second go at getting Wireless to work in SuSe and close to giving up.
|
|
|
Thomas Davie wrote:
[snip]
| Quote: | I did find a reference which I printed out stating that my specific
wireless card was supported in Ndiswrapper, and I followed those
instructions to a T, but no luck.
This is the reference
http://ndiswrapper.sourceforge.net/phpwiki/index.php/Suse%20Professional%
209.2
And, under this heading
http://ndiswrapper.sourceforge.net/phpwiki/index.php/List
here is the entry for my card
Card: Dell Truemobile? 1300 minipci 54mbps
Chipset: Broadcom BCM4306
pciid: 14E4:4320
Driver: http://ftp.us.dell.com/network/R81433.EXE
Other: Works with WEP and WPA with either CCMP/AES or TKIP ciphers.
The INF file for this card specifies it should use 802.11b mode
(upto 11Mbps) in Ad-Hoc mode. If you want to use 802.11g mode in
Ad-Hoc mode, you need to change the setting IBSSGmode in the .conf
files in the driver directory to 2.
So, as you can see, I think that my laptop should be working. Several
people have claimed it does. But after 10 months of failure......
tganks
Tom
|
I ran across this link from another forum I was browsing. Don't know how
good the instructions are since I don't use wireless, but it is more
oriented to manual installation which might helpful in troubleshooting your
problem.
http://nextgen.no-ip.org/~andrew/ndiswrapper/index.html
Since you already have ndiswrapper installed, you probably could just jump
to, say, step 11 and proceed from there. One thing the author recommends is
to disable your on-board ethernet interface while using your wireless card.
Don't know if you've already tried that yet, but it could be worth a shot.
good luck,
sktsee |
|
| Back to top |
|
|
Google
|
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
Forum index
»
*nix
»
Linux
»
Distributions
»
Suse
