I’m up and running thanks to a friend that helped me set up a dual boot Suse and XP. Now comes the fun part. My router keeled over and died, so I bought a new one. (I’m on Comcast internet) An Asus RT-N13U which I thought was plug and play. Yeah, right! I got it programmed with my iPhone, but for some reason I can’t get good access through it to the computer. It takes up to 10 minutes to even notice that I clicked on a link. By pass the router, and it runs at @56K equivalent (which I can live with for now)
I have no clue how to fix this.
I got it programmed with my iPhone, but for some reason I can’t get good access through it to the computer. It takes up to 10 minutes to even notice that I clicked on a link. By pass the router, and it runs at @56K equivalent (which I can live with for now)
I have no clue how to fix this.
I’m not familiar with this brand of router. Hopefully, someone who is familiar with it will drop by. I can’t imagine why it would work so slowly. Are you connecting via a wireless connection, or via ethernet port? I’m guessing the former connectivity (although it would be nice if you stated that explicitly). If so, how far way is your computer from the router? Interference (from neighbours) perhaps?
Post details about your computer’s wireless card. One way is to post the output of this terminal command
/usr/sbin/hwinfo --netcard
More questions are bound to follow.
Welcome carnuck.
Hopefully we will be able to help you. The first post asking for more information is allready above. But one thing you could at least have told out of yourself is which level of openSUSE you are using. Also, while you say “I clicked a link”, I assume you are using a Desktop. Please tell what desktop (KDE, Gnome, other). And that click, is that everywhere, or from a particular application/browser?
Also from your post I guess, but I am not quite sure, that before you installed the new router, everything worked as expected, is that assumption correct?
Sorry I double posted. I added an ASUS wireless router to my system after my old Netgear died (5 years isn’t too bad). Now Linux runs v e r y slow through it when hooked up through the ethernet. When I bypass the router, it runs fine. I’m temporarily using a wireless card that I fluked out and got set up on the first try (did I mention I’m a total newbie to Linux?) Any ideas whether software or hardware is the problem? I don’t like waiting 4-7 minutes for a link to finally pop up and I need the router for the others here to use. It doesn’t seem to matter if anyone is using bandwidth or not as to length of time for loading. The router is less than a foot from the tower. (Lenovo with a Marvel ethernet card).
It works fine without the ASUS router and did so before the Netgear router died too. Running SUSE
jim@linux-gmaa:~> /usr/sbin/hwinfo --netcard
28: PCI 200.0: 0200 Ethernet controller
[Created at pci.318]
Unique ID: rBUF.+xyi2yrFHU2
Parent ID: M71A.xQGmJdQgly5
SysFS ID: /devices/pci0000:00/0000:00:07.0/0000:02:00.0
SysFS BusID: 0000:02:00.0
Hardware Class: network
Model: “Marvell 88E8071 PCI-E Gigabit Ethernet Controller”
Vendor: pci 0x11ab “Marvell Technology Group Ltd.”
Device: pci 0x436b “88E8071 PCI-E Gigabit Ethernet Controller”
SubVendor: pci 0x17aa “Lenovo”
SubDevice: pci 0x3030
Revision: 0x16
Driver: “sky2”
Driver Modules: “sky2”
Device File: eth0
Memory Range: 0xfebfc000-0xfebfffff (rw,non-prefetchable)
I/O Ports: 0xe800-0xe8ff (rw)
Memory Range: 0xfebc0000-0xfebdffff (ro,non-prefetchable,disabled)
IRQ: 25 (53751 events)
HW Address: 00:16:17:fa:1e:6b
Link detected: yes
Module Alias: “pci:v000011ABd0000436Bsv000017AAsd00003030bc02sc00i00”
Driver Info #0:
Driver Status: sky2 is active
Driver Activation Cmd: “modprobe sky2”
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #10 (PCI bridge)
38: USB 00.0: 0282 WLAN controller
[Created at usb.122]
Unique ID: wkjR.uOhHm6bjrZ1
Parent ID: k4bc.MrJLBLcWB9F
SysFS ID: /devices/pci0000:00/0000:00:13.5/usb1/1-5/1-5:1.0
SysFS BusID: 1-5:1.0
Hardware Class: network
Model: “NetGear NETGEAR WG111v3”
Hotplug: USB
Vendor: usb 0x0846 “NetGear, Inc.”
Device: usb 0x4260 “NETGEAR WG111v3”
Revision: “2.00”
Serial ID: “C43DC77FEBAA”
Driver: “rtl8187”
Driver Modules: “rtl8187”
Device File: wlan0
Features: WLAN
Speed: 480 Mbps
HW Address: c4:3d:c7:7f:eb:aa
Link detected: no
WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 14
WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472 2.484
WLAN encryption modes: WEP40 WEP104 TKIP CCMP
WLAN authentication modes: open sharedkey wpa-psk wpa-eap
Module Alias: “usb:v0846p4260d0200dc00dsc00dp00icFFiscFFipFF”
Driver Info #0:
Driver Status: rtl8187 is active
Driver Activation Cmd: “modprobe rtl8187”
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #30 (Hub)
jim@linux-gmaa:~> ^C
jim@linux-gmaa:~>
On 11/04/2011 09:24 PM, carnuck wrote:
>
> Sorry I double posted. I added an ASUS wireless router to my system
> after my old Netgear died (5 years isn’t too bad). Now Linux runs v e r
> y slow through it when hooked up through the ethernet. When I bypass the
> router, it runs fine. I’m temporarily using a wireless card that I
> fluked out and got set up on the first try (did I mention I’m a total
> newbie to Linux?) Any ideas whether software or hardware is the
> problem? I don’t like waiting 4-7 minutes for a link to finally pop up
> and I need the router for the others here to use. It doesn’t seem to
> matter if anyone is using bandwidth or not as to length of time for
> loading. The router is less than a foot from the tower. (Lenovo with a
> Marvel ethernet card).
Your slow wired network may be due to a faulty cable or a bad port on the
router. Try different ports and cables. You might also try setting the port
parameters with ethtool.
From your posting, I think wireless is working just fine. Is that correct?
Sorry. I didn’t know there was a reply. For some reason I’m not getting notifications even though I’m subscribed. The wireless works fine with the laptops (Mac, iPhone and HP) and sort of okay with the desktop (it has USB1 ports still so it’s slow, but not as slow as direct connected) Using either cable bypassing the router and the tower works fine. I guess I need to learn the ethtool next.