| View previous topic :: View next topic |
| Author |
Message |
tjfriese
n00b
Joined: 06 May 2003
Posts: 62
Location: Calgary, Alberta, Canada
|
 Posted: Wed Jun 15, 2005 12:11 am Post subject: No network |
 |
|
Hello all,
I have got my Marvell Yukon network card working through a driver that another forum poster sent me. When it is loaded the card shows up as eth0. If I boot my laptop with the wireless turned on, the wireless card is not detected and so the wired card shows up as eth0, otherwise, if the wireless is turned off, the wired card shows up as eth1.
I can go through net-setup eth1 and enter all the correct information, however, at that point I don't have a connection to the net. I can't even ping my router as I get back destination host unreachable errors.
Does anyone have any suggestions?
Thanks,
Tim |
|
| Back to top |
|
 |
stealthy
Tux's lil' helper
Joined: 08 Aug 2002
Posts: 118
Location: ONTARIO CANADA
|
| Posted: Wed Jun 15, 2005 4:49 pm Post subject: |
|
|
I am not sure if I follow your question correctly.
When you boot up with wireless card turned ON wireless card isn't detected
when you boot up with wireless card turned OFF wireless card is detected, are you sure you got your ON/OFF switch right?
Anyhow easiest way to solve this problem is make sure that sk98lin (module for your marvell Yukon NIC) is the first line
in your
| Quote: | | /etc/modules.autoload.d/kernel-2.6 |
file
That way, system will load that driver first.
_________________
All your Gentoo are belong to us. |
|
| Back to top |
|
|
tjfriese
n00b
Joined: 06 May 2003
Posts: 62
Location: Calgary, Alberta, Canada
|
| Posted: Wed Jun 15, 2005 4:55 pm Post subject: |
|
|
| stealthy wrote: | I am not sure if I follow your question correctly.
When you boot up with wireless card turned ON wireless card isn't detected
when you boot up with wireless card turned OFF wireless card is detected, are you sure you got your ON/OFF switch right?
Anyhow easiest way to solve this problem is make sure that sk98lin (module for your marvell Yukon NIC) is the first line
in your
| Quote: | | /etc/modules.autoload.d/kernel-2.6 |
file
That way, system will load that driver first. |
Thanks for your reply. You did get that right. When I boot with the wireless switch off, the wireless card is detected. If I then turn it on, it gives me power errors. This is all during the install.
When I go to configure the Marvell Yukon I do the following:
ifconfig eth1 192.168.0.5 broadcast 192.168.0.255 netmask 255.255.255.0
route add default gw 192.168.0.1
Sometimes the second comand gives me a SIOCADDRT: no such device error.
However, after configuring the network like that I'm always unable to ping my router, and when I add my nameservers I can't ping anything like google or yahoo. |
|
| Back to top |
|
|
jakubc
Tux's lil' helper
Joined: 21 Jan 2005
Posts: 138
Location: Prague <- Czech Republic <- Europe <- World...
|
| Posted: Wed Jun 15, 2005 8:20 pm Post subject: |
|
|
hi,
are you sure you're loading the driver? please post the following when you are hooked up:
| Code: | iwconfig
ifconfig
ls -l /etc/init.d/net* (just to see how you're linking the scripts)
uncommented lines in /etc/conf.d/net & /etc/conf.d/wireless
and the relevant stats of the AP too...
|
this will flesh out the problem letting more people into the picture...
_________________
Regards,
Jakub Cerny |
|
| Back to top |
|
|
tjfriese
n00b
Joined: 06 May 2003
Posts: 62
Location: Calgary, Alberta, Canada
|
| Posted: Wed Jun 15, 2005 9:04 pm Post subject: |
|
|
| jakubc wrote: | hi,
are you sure you're loading the driver? please post the following when you are hooked up:
| Code: | iwconfig
ifconfig
ls -l /etc/init.d/net* (just to see how you're linking the scripts)
uncommented lines in /etc/conf.d/net & /etc/conf.d/wireless
and the relevant stats of the AP too...
|
this will flesh out the problem letting more people into the picture... |
I hope this helps a little. I am trying to get networking up for an install. I have the exact same setup working just fine in Windows XP, so it's not the ip addresses or anything like that. eth0 is an Intel Pro/Wireless 2200 ABG (ipw2200). lsmod shows it as loading the correct module. eth1 is a Marvell Yukon. The live CD does not come with a working module for it so I've been using a module that another forum member e-mailed to me (sk98lin).
Here is the output from ifconfig and iwconfig:
iwconfig -a:
| Code: |
eth0 Link encap:Ethernet HWaddr 00:0E:35:EB:13:96
inet addr:192.168.0.4 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST 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:1
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:11 Base address:0x4000 Memory:b000b000-b000bfff
eth1 Link encap:Ethernet HWaddr 00:A0:D1:BE:3D:CD
inet addr:192.168.0.5 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST 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.0 b) TX bytes:0 (0.0 b)
Interrupt:11 Memory:bc000000-0
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:27 errors:0 dropped:0 overruns:0 frame:0
TX packets:27 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2512 (2.4 Kb) TX bytes:2512 (2.4 Kb)
|
iwconfig:
| Code: |
eth0 unassociated ESSID:""XXX""
Mode:Managed Channel=0 Access Point: 00:00:00:00:00:00
Bit Rate=0 kb/s Tx-Power=20 dBm
RTS thr:off Fragment thr:off
Encryption key:XXX Security mode:open
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
|
ping -c 3 192.168.0.1:
| Code: |
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
From 192.168.0.5 icmp_seq=1 Destination Host Unreachable
From 192.168.0.5 icmp_seq=2 Destination Host Unreachable
From 192.168.0.5 icmp_seq=3 Destination Host Unreachable
--- 192.168.0.1 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 1999ms
, pipe 3
|
I have my access point set for wpa-psk. It's a D-Link DI-624.
This is a fairly new Toshiba M40 laptop. I have Suse 9.3 installed on it currently and the wired network card works just fine. I have had no luck getting wireless to work in Suse 9.3 though.
Randomly I seem to get "network not connected" errors when I run net-setup. And I also get random "SIOCADDRT: no such device" errors when I run "route add default gw 192.168.0.1".
Thanks,
Tim |
|
| Back to top |
|
|
zonk
Apprentice
Joined: 23 May 2005
Posts: 176
|
| Posted: Wed Jun 15, 2005 9:31 pm Post subject: |
|
|
for now, you should turn off wpa and even wep. get it working first, then add security. so try turning it off in your router.
then bring down the hardwired interface to rule out confusion with
then restart the wireless card with
| Code: | ifconfig eth0 down
ifconfig eth0 up |
then try to associate the card
| Code: | iwconfig eth0 key off
iwconfig eth0 essid "yournetworkid"
dhcpcd eth0 |
does that help? |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
