[gentoo-user] OT: wlan0 is sssloooow

[gentoo-user] OT: wlan0 is sssloooow

[Sergio Polini]

Scenario:
- I have a HAG (Home Access Gateway, which embodies an ADSL modem) 
installed by my provider;
- the HAG has three RJ45 ports; when a PC is connected to one of 
theese ports, it gets an IP address via DHCP;
- I have connected a Belkin wireless rooter to one of theese ports;
- I connect my PC to another port, and/or to the wireless router (by 
running modprobe ndiswrapper; then /etc/init.d/net.wlan0 is ran by 
ifplugs - at least, this is what I can guess ;-).

When I run Windows, my wireless connection is "normal", but when I run 
Gentoo there are strange delays. For example, a simple ping is fast 
under Windows, very slow under Gentoo. I have to stop net.wlan0 to 
get "normal" pings again.

As far as I can understand, it is a matter of metric.
When I only connect my PC to the wireless router, I can see:

a) under Windows (the output is in Italian, but I'm sure you can read 
it - using a fixed font may help ;-):

> route PRINT
============================================================
Elenco interfacce
0x1 ........................... MS TCP Loopback interface
0x2 ...00 16 d3 09 2d 17 ...... NVIDIA nForce Networking
0x3 ...00 14 a5 e1 d2 b9 ...... WLAN Broadcom 802.11a/b/g
============================================================
============================================================
Route attive:
Indirizzo rete           Mask     Gateway   Interfac. Metric
        0.0.0.0         0.0.0.0 192.168.2.1 192.168.2.2 25
      127.0.0.0       255.0.0.0   127.0.0.1   127.0.0.1  1
    192.168.2.0   255.255.255.0 192.168.2.2 192.168.2.2 25
    192.168.2.2 255.255.255.255   127.0.0.1   127.0.0.1 25
  192.168.2.255 255.255.255.255 192.168.2.2 192.168.2.2 25
      224.0.0.0       240.0.0.0 192.168.2.2 192.168.2.2 25
255.255.255.255 255.255.255.255 192.168.2.2           2  1
255.255.255.255 255.255.255.255 192.168.2.2 192.168.2.2  1
Gateway predefinito:       192.168.2.1
============================================================
Route permanenti:
  Nessuno

b) under Gentoo:

b.1) fast:

sergio ~ # route -n
Kernel IP routing table
Destination Gateway     Genmask       Flags Metric Ref Use Iface
192.168.2.0 0.0.0.0     255.255.255.0 U     2000   0     0 wlan0
127.0.0.0   0.0.0.0     255.0.0.0     U     0      0     0 lo
0.0.0.0     192.168.2.1 0.0.0.0       UG    2000   0     0 wlan0

b.1) very slow:

sergio ~ # route
Kernel IP routing table
Destination Gateway     Genmask       Flags Metric Ref Use Iface
192.168.2.0 *           255.255.255.0 U     2000   0     0 wlan0
loopback    *           255.0.0.0     U     0      0     0 lo
default     192.168.2.1 0.0.0.0       UG    2000   0     0 wlan0

I can just notice an astonishing difference between metrics: 25 under 
Windows, 2000 (!) under Linux.

I've tried "route del default" and then "route add default gw 
192.168.2.1 metric 0", but the wireless connection was still slow.
"Slow" means, for example, that if I use my browser and go 
to "www.google.com", "Looking for www.google.com" lasts too mach.

Any hints?
Thanks
Sergio
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OT: wlan0 is sssloooow

[Richard Fish]

On 11/26/06, Sergio Polini <sp_rm_it@yahoo.it> wrote:
> I can just notice an astonishing difference between metrics: 25 under
> Windows, 2000 (!) under Linux.

The absolute value of an interface metric is meaningless, they only
matter in relation to other interface metrics active at the time.
They are used to decide between interfaces when a host can be reached
through more than one interface.  So for example, if you have a dialup
connection as well as broadband, you would want the broadband
connection to have a lower metric than the dialup so that it is the
'preferred' interface.

What do "ifconfig wlan" and "iwconfig wlan" report for the fast and
slow states?  And the host that you are pinging, is a remote internet
host or something local (like 192.168.2.1)?

-Richard
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OT: wlan0 is sssloooow

[Sergio Polini]

Richard Fish:
> On 11/26/06, Sergio Polini <sp_rm_it@yahoo.it> wrote:
> > I can just notice an astonishing difference between metrics: 25
> > under Windows, 2000 (!) under Linux.
>
> The absolute value of an interface metric is meaningless, they only
> matter in relation to other interface metrics active at the time.
> They are used to decide between interfaces when a host can be
> reached through more than one interface.  So for example, if you
> have a dialup connection as well as broadband, you would want the
> broadband connection to have a lower metric than the dialup so that
> it is the 'preferred' interface.

Thanks for your answer.
My pings (perhaps all DNS lookups) are slow even if connect my PC to 
both the wireless router and the cable, i.e. when there are both 
a "fast" (metric 0) and a "slow" (metric 2000) interface.

> What do "ifconfig wlan" and "iwconfig wlan" report for the fast and
> slow states?

Fast (i.e. normal ;-) state happens only when net.wlan0 is stopped.
When I start net.wlan0:

sergio ~ # ifconfig wlan0
wlan0  Link encap:Ethernet  HWaddr 00:14:A5:E1:D2:B9
       inet addr:192.168.2.2  Bcast:192.168.2.255 Mask:255.255.255.0
       UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
       RX packets:16 errors:0 dropped:0 overruns:0 frame:0
       TX packets:93 errors:0 dropped:0 overruns:0 carrier:0
       collisions:0 txqueuelen:1000
       RX bytes:2742 (2.6 Kb)  TX bytes:10200 (9.9 Kb)
       Interrupt:20 Memory:c3000000-c3004000

sergio ~ # iwconfig wlan0
wlan0  IEEE 802.11g  ESSID:"mynet"
    Mode:Managed  Frequency:2.462 GHz  Access Point: 00:17:3F:0C:19:12
    Bit Rate=54 Mb/s   Tx-Power:32 dBm
    RTS thr:off   Fragment thr:off
    Encryption key:XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XX
    Security mode:restricted
    Power Management:off
    Link Quality:100/100  Signal level:-48 dBm  Noise level:-256 dBm
    Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
    Tx excessive retries:1  Invalid misc:168   Missed beacon:0

> And the host that you are pinging, is a remote 
> internet host or something local (like 192.168.2.1)?

Remote internet hosts (f.i., google) and local.
BTW, I can't ping 192.168.2.1, i.e. the wireless router. But I can 
under Windows!

Thanks
Sergio
-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Screen(s) found, but none have a usable configuration

[burmata]

Xorg 7.1 + ati-drivers 8.29.6 
I just install ati-drivers using guide in gentoo-wiki. 
Result is: "Screen(s) found, but none have a usable configuration"
So please help :)) 



############
#Xorg.0.log
############


X Window System Version 7.1.1
Release Date: 12 May 2006
X Protocol Version 11, Revision 0, Release 7.1.1
Build Operating System: UNKNOWN 
Current Operating System: Linux localhost 2.6.18-gentoo-r3 #3 PREEMPT
Mon Nov 27 01:13:18 EET 2006 i686
Build Date: 26 November 2006
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Nov 27 01:48:41 2006
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Simple Layout"
(**) |-->Screen "aticonfig-Screen[0]" (0)
(**) |   |-->Monitor "Monitor"
(**) |   |-->Device "aticonfig-Device[0]"
(**) |-->Input Device "Mouse1"
(**) |-->Input Device "Keyboard1"
(**) FontPath set to:
	/usr/share/fonts/misc/,
	/usr/share/fonts/Type1/,
	/usr/share/fonts/100dpi/,
	/usr/share/fonts/75dpi/
(==) RgbPath set to "/usr/share/X11/rgb"
(==) ModulePath set to "/usr/lib/xorg/modules"
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or
directory)
(II) No APM support in BIOS or kernel
(II) Module ABI versions:
	X.Org ANSI C Emulation: 0.3
	X.Org Video Driver: 1.0
	X.Org XInput driver : 0.6
	X.Org Server Extension : 0.3
	X.Org Font Renderer : 0.5
(II) Loader running on linux
(II) LoadModule: "bitmap"
(II) Loading /usr/lib/xorg/modules/fonts/libbitmap.so
(II) Module bitmap: vendor="X.Org Foundation"
	compiled for 7.1.1, module version = 1.0.0
	Module class: X.Org Font Renderer
	ABI class: X.Org Font Renderer, version 0.5
(II) Loading font Bitmap
(II) LoadModule: "pcidata"
(II) Loading /usr/lib/xorg/modules/libpcidata.so
(II) Module pcidata: vendor="X.Org Foundation"
	compiled for 7.1.1, module version = 1.0.0
	ABI class: X.Org Video Driver, version 1.0
(--) using VT number 7

(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 1106,3189 card 1458,5000 rev 80 class 06,00,00
hdr 00
(II) PCI: 00:01:0: chip 1106,b198 card 0000,0000 rev 00 class 06,04,00
hdr 01
(II) PCI: 00:0f:0: chip 1106,0571 card 1458,5002 rev 06 class 01,01,8a
hdr 00
(II) PCI: 00:10:0: chip 1106,3038 card 1458,5004 rev 81 class 0c,03,00
hdr 80
(II) PCI: 00:10:1: chip 1106,3038 card 1458,5004 rev 81 class 0c,03,00
hdr 80
(II) PCI: 00:10:2: chip 1106,3038 card 1458,5004 rev 81 class 0c,03,00
hdr 80
(II) PCI: 00:10:3: chip 1106,3038 card 1458,5004 rev 81 class 0c,03,00
hdr 80
(II) PCI: 00:10:4: chip 1106,3104 card 1458,5004 rev 86 class 0c,03,20
hdr 80
(II) PCI: 00:11:0: chip 1106,3227 card 1458,5001 rev 00 class 06,01,00
hdr 80
(II) PCI: 00:11:5: chip 1106,3059 card 1458,a002 rev 60 class 04,01,00
hdr 00
(II) PCI: 00:12:0: chip 1106,3065 card 1458,e000 rev 78 class 02,00,00
hdr 00
(II) PCI: 01:00:0: chip 1002,5961 card 1458,4018 rev 01 class 03,00,00
hdr 80
(II) PCI: 01:00:1: chip 1002,5941 card 1458,4019 rev 01 class 03,80,00
hdr 00
(II) PCI: End of PCI scan
(II) Host-to-PCI bridge:
(II) Bus 0: bridge is at (0:0:0), (0,0,1), BCTRL: 0x0008 (VGA_EN is
set)
(II) Bus 0 I/O range:
	[0] -1	0	0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) Bus 0 non-prefetchable memory range:
	[0] -1	0	0x00000000 - 0xffffffff (0x0) MX[B]
(II) Bus 0 prefetchable memory range:
	[0] -1	0	0x00000000 - 0xffffffff (0x0) MX[B]
(II) PCI-to-PCI bridge:
(II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x000c (VGA_EN is
set)
(II) Bus 1 I/O range:
	[0] -1	0	0x0000c000 - 0x0000c0ff (0x100) IX[B]
	[1] -1	0	0x0000c400 - 0x0000c4ff (0x100) IX[B]
	[2] -1	0	0x0000c800 - 0x0000c8ff (0x100) IX[B]
	[3] -1	0	0x0000cc00 - 0x0000ccff (0x100) IX[B]
(II) Bus 1 non-prefetchable memory range:
	[0] -1	0	0xe0000000 - 0xe1ffffff (0x2000000) MX[B]
(II) Bus 1 prefetchable memory range:
	[0] -1	0	0xd8000000 - 0xdfffffff (0x8000000) MX[B]
(II) PCI-to-ISA bridge:
(II) Bus -1: bridge is at (0:17:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is
set)
(--) PCI:*(1:0:0) ATI Technologies Inc RV280 [Radeon 9200] rev 1, Mem @
0xd8000000/26, 0xe1000000/16, I/O @ 0xc000/8
(--) PCI: (1:0:1) ATI Technologies Inc RV280 [Radeon 9200] (Secondary)
rev 1, Mem @ 0xdc000000/26, 0xe1010000/16
(II) Addressable bus resource ranges are
	[0] -1	0	0x00000000 - 0xffffffff (0x0) MX[B]
	[1] -1	0	0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) OS-reported resource ranges:
	[0] -1	0	0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
	[1] -1	0	0x000f0000 - 0x000fffff (0x10000) MX[B]
	[2] -1	0	0x000c0000 - 0x000effff (0x30000) MX[B]
	[3] -1	0	0x00000000 - 0x0009ffff (0xa0000) MX[B]
	[4] -1	0	0x0000ffff - 0x0000ffff (0x1) IX[B]
	[5] -1	0	0x00000000 - 0x000000ff (0x100) IX[B]
(II) PCI Memory resource overlap reduced 0xd0000000 from 0xd7ffffff to
0xcfffffff
(II) Active PCI resource ranges:
	[0] -1	0	0xe2001000 - 0xe20010ff (0x100) MX[B]
	[1] -1	0	0xe2000000 - 0xe20000ff (0x100) MX[B]
	[2] -1	0	0xd0000000 - 0xcfffffff (0x0) MX[B]O
	[3] -1	0	0xe1010000 - 0xe101ffff (0x10000) MX[B](B)
	[4] -1	0	0xdc000000 - 0xdfffffff (0x4000000) MX[B](B)
	[5] -1	0	0xe1000000 - 0xe100ffff (0x10000) MX[B](B)
	[6] -1	0	0xd8000000 - 0xdbffffff (0x4000000) MX[B](B)
	[7] -1	0	0x0000e800 - 0x0000e8ff (0x100) IX[B]
	[8] -1	0	0x0000e400 - 0x0000e4ff (0x100) IX[B]
	[9] -1	0	0x0000e000 - 0x0000e01f (0x20) IX[B]
	[10] -1	0	0x0000dc00 - 0x0000dc1f (0x20) IX[B]
	[11] -1	0	0x0000d800 - 0x0000d81f (0x20) IX[B]
	[12] -1	0	0x0000d400 - 0x0000d41f (0x20) IX[B]
	[13] -1	0	0x0000d000 - 0x0000d00f (0x10) IX[B]
	[14] -1	0	0x0000c000 - 0x0000c0ff (0x100) IX[B](B)
(II) Active PCI resource ranges after removing overlaps:
	[0] -1	0	0xe2001000 - 0xe20010ff (0x100) MX[B]
	[1] -1	0	0xe2000000 - 0xe20000ff (0x100) MX[B]
	[2] -1	0	0xd0000000 - 0xcfffffff (0x0) MX[B]O
	[3] -1	0	0xe1010000 - 0xe101ffff (0x10000) MX[B](B)
	[4] -1	0	0xdc000000 - 0xdfffffff (0x4000000) MX[B](B)
	[5] -1	0	0xe1000000 - 0xe100ffff (0x10000) MX[B](B)
	[6] -1	0	0xd8000000 - 0xdbffffff (0x4000000) MX[B](B)
	[7] -1	0	0x0000e800 - 0x0000e8ff (0x100) IX[B]
	[8] -1	0	0x0000e400 - 0x0000e4ff (0x100) IX[B]
	[9] -1	0	0x0000e000 - 0x0000e01f (0x20) IX[B]
	[10] -1	0	0x0000dc00 - 0x0000dc1f (0x20) IX[B]
	[11] -1	0	0x0000d800 - 0x0000d81f (0x20) IX[B]
	[12] -1	0	0x0000d400 - 0x0000d41f (0x20) IX[B]
	[13] -1	0	0x0000d000 - 0x0000d00f (0x10) IX[B]
	[14] -1	0	0x0000c000 - 0x0000c0ff (0x100) IX[B](B)
(II) OS-reported resource ranges after removing overlaps with PCI:
	[0] -1	0	0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
	[1] -1	0	0x000f0000 - 0x000fffff (0x10000) MX[B]
	[2] -1	0	0x000c0000 - 0x000effff (0x30000) MX[B]
	[3] -1	0	0x00000000 - 0x0009ffff (0xa0000) MX[B]
	[4] -1	0	0x0000ffff - 0x0000ffff (0x1) IX[B]
	[5] -1	0	0x00000000 - 0x000000ff (0x100) IX[B]
(II) All system resource ranges:
	[0] -1	0	0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
	[1] -1	0	0x000f0000 - 0x000fffff (0x10000) MX[B]
	[2] -1	0	0x000c0000 - 0x000effff (0x30000) MX[B]
	[3] -1	0	0x00000000 - 0x0009ffff (0xa0000) MX[B]
	[4] -1	0	0xe2001000 - 0xe20010ff (0x100) MX[B]
	[5] -1	0	0xe2000000 - 0xe20000ff (0x100) MX[B]
	[6] -1	0	0xd0000000 - 0xcfffffff (0x0) MX[B]O
	[7] -1	0	0xe1010000 - 0xe101ffff (0x10000) MX[B](B)
	[8] -1	0	0xdc000000 - 0xdfffffff (0x4000000) MX[B](B)
	[9] -1	0	0xe1000000 - 0xe100ffff (0x10000) MX[B](B)
	[10] -1	0	0xd8000000 - 0xdbffffff (0x4000000) MX[B](B)
	[11] -1	0	0x0000ffff - 0x0000ffff (0x1) IX[B]
	[12] -1	0	0x00000000 - 0x000000ff (0x100) IX[B]
	[13] -1	0	0x0000e800 - 0x0000e8ff (0x100) IX[B]
	[14] -1	0	0x0000e400 - 0x0000e4ff (0x100) IX[B]
	[15] -1	0	0x0000e000 - 0x0000e01f (0x20) IX[B]
	[16] -1	0	0x0000dc00 - 0x0000dc1f (0x20) IX[B]
	[17] -1	0	0x0000d800 - 0x0000d81f (0x20) IX[B]
	[18] -1	0	0x0000d400 - 0x0000d41f (0x20) IX[B]
	[19] -1	0	0x0000d000 - 0x0000d00f (0x10) IX[B]
	[20] -1	0	0x0000c000 - 0x0000c0ff (0x100) IX[B](B)
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
	compiled for 7.1.1, module version = 1.0.0
	Module class: X.Org Server Extension
	ABI class: X.Org Server Extension, version 0.3
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
	compiled for 7.1.1, module version = 1.0.0
	Module class: X.Org Server Extension
	ABI class: X.Org Server Extension, version 0.3
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension DPMS
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "freetype"
(II) Loading /usr/lib/xorg/modules/fonts/libfreetype.so
(II) Module freetype: vendor="X.Org Foundation & the After X-TT
Project"
	compiled for 7.1.1, module version = 2.1.0
	Module class: X.Org Font Renderer
	ABI class: X.Org Font Renderer, version 0.5
(II) Loading font FreeType
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions/libdri.so
(II) Module dri: vendor="X.Org Foundation"
	compiled for 7.1.1, module version = 1.0.0
	ABI class: X.Org Server Extension, version 0.3
(II) Loading sub module "drm"
(II) LoadModule: "drm"
(II) Loading /usr/lib/xorg/modules/linux/libdrm.so
(II) Module drm: vendor="X.Org Foundation"
	compiled for 7.1.1, module version = 1.0.0
	ABI class: X.Org Server Extension, version 0.3
(II) Loading extension XFree86-DRI
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions/libglx.so
(II) Module glx: vendor="X.Org Foundation"
	compiled for 7.1.1, module version = 1.0.0
	ABI class: X.Org Server Extension, version 0.3
(==) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "fglrx"
(II) Loading /usr/lib/xorg/modules/drivers/fglrx_drv.so
(II) Module fglrx: vendor="FireGL - ATI Technologies Inc."
	compiled for 7.1.0, module version = 8.29.6
	Module class: X.Org Video Driver
	ABI class: X.Org Video Driver, version 1.0
(II) LoadModule: "mouse"
(II) Loading /usr/lib/xorg/modules/input/mouse_drv.so
(II) Module mouse: vendor="X.Org Foundation"
	compiled for 7.1.1, module version = 1.1.1
	Module class: X.Org XInput Driver
	ABI class: X.Org XInput driver, version 0.6
(II) LoadModule: "kbd"
(II) Loading /usr/lib/xorg/modules/input/kbd_drv.so
(II) Module kbd: vendor="X.Org Foundation"
	compiled for 7.1.1, module version = 1.1.0
	Module class: X.Org XInput Driver
	ABI class: X.Org XInput driver, version 0.6
(II) ATI Radeon/FireGL: The following chipsets are supported:
	RADEON 9600 (RV350 4150), RADEON 9600 SE (RV350 4151),
	RADEON 9600 PRO (RV360 4152), RADEON 9600 (RV350 4E51),
	MOBILITY RADEON 9600/9700 (M10/M11 4E50),
	MOBILITY RADEON 9500 (M11 4E52), MOBILITY RADEON 9550 (M12 4E56),
	RADEON 9500 (R300 4144), RADEON 9600 TX (R300 4146),
	FireGL Z1 (R300 4147), RADEON 9700 PRO (R300 4E44),
	RADEON 9500 PRO/9700 (R300 4E45), RADEON 9600 TX (R300 4E46),
	FireGL X1 (R300 4E47), RADEON 9800 SE (R350 4148),
	RADEON 9500 (R350 4149), RADEON 9550 (RV350 4153),
	FireGL T2 (RV350 4154), RADEON 9600 (RV351 4155),
	RADEON 9800 PRO (R350 4E48), RADEON 9800 (R350 4E49),
	RADEON 9800 XT (R360 4E4A), FireGL X2-256/X2-256t (R350 4E4B),
	MOBILITY FireGL T2/T2e (M10/M11 4E54), RADEON X300/X550 (RV370 5B60),
	RADEON X600 (RV380 5B62), RADEON X550 (RV370 5B63),
	FireGL V3100 (RV370 5B64), FireMV 2200 (RV370 5B65),
	MOBILITY RADEON X300 (M22 5460), MOBILITY RADEON X300 (M22 5461),
	MOBILITY RADEON X600 SE (M24 5462), MOBILITY FireGL V3100 (M22 5464),
	RADEON X600/X550 Series (RV380 3E50), FireGL V3200 (RV380 3E54),
	MOBILITY RADEON X600 (M24 3150), FireMV 2400 (RV380 3151),
	MOBILITY RADEON X300 (M22 3152), MOBILITY FireGL V3200 (M24 3154),
	RADEON X800 (R420 4A48), RADEON X800 PRO (R420 4A49),
	RADEON X800 SE (R420 4A4A), RADEON X800 XT (R420 4A4B),
	RADEON X800 (R420 4A4C), FireGL X3-256 (R420 4A4D),
	MOBILITY RADEON 9800 (M18 4A4E), RADEON X800 SE (R420 4A4F),
	RADEON X800 XT Platinum Edition (R420 4A50),
	RADEON X800 VE (R420 4A54), RADEON X800 (R423 5548),
	RADEON X800 GTO (R423 5549),
	RADEON X800 XT Platinum Edition (R423 554A),
	RADEON X800 GT (R423 554B), RADEON X800 XT (R423 5D57),
	FireGL V7100 (R423 5550), FireGL V5100 (R423 5551),
	MOBILITY RADEON X800 XT (M28 5D48), MOBILITY FireGL V5100 (M28 5D49),
	MOBILITY RADEON X800 (M28 5D4A), RADEON X800 XL (R430 554D),
	RADEON X800 GT (R430 554E), RADEON X800 GTO (R430 554F),
	RADEON X850 XT Platinum Edition (R480 5D4D),
	RADEON X800 GTO (R480 5D4F), FireGL V7200 (R480 5D50),
	RADEON X850 XT (R480 5D52), RADEON X850 (R481 4B48),
	RADEON X850 XT (R481 4B49), RADEON X850 SE (R481 4B4A),
	RADEON X850 PRO (R481 4B4B),
	RADEON X850 XT Platinum Edition (R481 4B4C),
	MOBILITY FireGL V5000 (M26 564A), MOBILITY FireGL V5000 (M26 564B),
	FireGL V5000 (RV410 5E48), RADEON X700 XT (RV410 5E4A),
	RADEON X700 PRO (RV410 5E4B), RADEON X700 SE (RV410 5E4C),
	RADEON X700 (RV410 5E4D), RADEON X700/X550 Series (RV410 5E4F),
	MOBILITY RADEON X700 (M26 5652), MOBILITY RADEON X700 (M26 5653),
	MOBILITY RADEON X700 XL (M26-XC 564F),
	RADEON 9000/9100 IGP Series (RS300 5834),
	RADEON 9000 PRO/9100 PRO IGP (RS350 7834),
	MOBILITY RADEON 9000 IGP (RL300MB 7835),
	MOBILITY RADEON 9000/9100 IGP (RS300M 5835),
	RADEON XPRESS 200 (RS400 5A41), RADEON XPRESS 200M (RS400 5A42),
	RADEON XPRESS 200 (RS480 5954), RADEON XPRESS 200M (RS480 5955),
	RADEON XPRESS 200 (RS482 5974), RADEON XPRESS 200M (RS482 5975),
	RADEON XPRESS 200 (RC410 5A61), RADEON XPRESS 200M (RC410 5A62),
	RADEON X1800 (R520 7100), MOBILITY RADEON X1800 XT (M58 7101),
	MOBILITY RADEON X1800 (M58 7102), MOBILITY FireGL V7200 (M58 7103),
	FireGL V7200 (R520 7104), FireGL V5300 (R520 7105),
	MOBILITY FireGL V7100 (M58 7106), RADEON X1800 Series (R520 7108),
	RADEON X1800 Series (R520 7109), RADEON X1800 Series (R520 710A),
	RADEON X1800 Series (R520 710B), RADEON X1800 Series (R520 710C),
	FireGL V7300 (R520 710E), FireGL V7350 (R520 710F),
	RADEON X1300 PRO (RV505 7143), RADEON X1300 (RV505 7147),
	MOBILITY RADEON X1300 (M52 714B), MOBILITY RADEON X1300 (M52 714C),
	RADEON X1300 Series (RV505 715F), RADEON X1600 Series (RV515 7140),
	RADEON X1300 Series (RV515 7142), MOBILITY FireGL (M54 GL 7144),
	MOBILITY RADEON X1400 (M54 7145), RADEON X1300 Series (RV515 7146),
	MOBILITY RADEON X1300 (M52 7149), MOBILITY RADEON X1300 (M52 714A),
	RADEON X1300 Series (RV515 714D), RADEON X1300 Series (RV515 714E),
	FireGL V3300 (RV515 7152), RADEON X1300 Series (RV515 715E),
	RADEON X1300 (RV516 7180), RADEON X1600 Series (RV516 7181),
	RADEON X1300 (RV516 7183), MOBILITY RADEON X1450 (M64P 7186),
	RADEON X1300 (RV516 7187), MOBILITY RADEON X1350 (M62P 718B),
	MOBILITY RADEON X1350 (M62CSP 718C),
	MOBILITY RADEON X1450 (M64CSP 718D),
	MOBILITY RADEON X1350 (M62S 7196), RADEON X1900 (R580 7240),
	RADEON X1900 (R580 7243), RADEON X1900 (R580 7244),
	RADEON X1900 (R580 7245), RADEON X1900 (R580 7246),
	RADEON X1900 (R580 7247), RADEON X1900 (R580 7248),
	RADEON X1900 (R580 7249), RADEON X1900 (R580 724A),
	RADEON X1900 (R580 724B), RADEON X1900 (R580 724C),
	RADEON X1900 (R580 724D), FireStream 2U (R580 724E),
	FireStream 2U (R580 724F), RADEON X1600 Series (RV530 71C0),
	RADEON X1600 Series (RV530 71C2), MOBILITY FireGL V5200 (M56 71C4),
	MOBILITY RADEON X1600 (M56 71C5),
	RADEON X1600 Series (RV530 LE 71C6),
	RADEON X1600 Series (RV530 VE 71CE), FireGL V3400 (RV530 71D2),
	MOBILITY RADEON X1700 (M66-XT 71D6), FireGL V5200 (RV530 71DA),
	RADEON X1600 Series (RV530 SE 71DE), RADEON X1600 XT (RV535 XT 71C1),
	MOBILITY FireGL V5250 (M66GL 71D4),
	MOBILITY RADEON X1700 (M66-P 71D5), FireGL V7400 (RV570 GL 728C),
	RADEON Xpress 1200 (RS600 7941), RADEON Xpress 1200 (RS600 7942)
(II) Primary Device is: PCI 01:00:0
(II) ATI Proprietary Linux Driver Version Identifier:8.29.6
(II) ATI Proprietary Linux Driver Release Identifier: LGDr8.29g1
                          
(II) ATI Proprietary Linux Driver Build Date: Sep 19 2006 16:28:13
(II) ATI Proprietary Linux Driver Build Information:
autobuild-rel-r6-8.29.1.1.2.3-driver-lnx-x86-x86_64-294118
(--) Assigning device section with no busID to primary device
(WW) fglrx: No matching Device section for instance (BusID PCI:1:0:1)
found
(--) Chipset (null) found
(II) resource ranges after xf86ClaimFixedResources() call:
	[0] -1	0	0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
	[1] -1	0	0x000f0000 - 0x000fffff (0x10000) MX[B]
	[2] -1	0	0x000c0000 - 0x000effff (0x30000) MX[B]
	[3] -1	0	0x00000000 - 0x0009ffff (0xa0000) MX[B]
	[4] -1	0	0xe2001000 - 0xe20010ff (0x100) MX[B]
	[5] -1	0	0xe2000000 - 0xe20000ff (0x100) MX[B]
	[6] -1	0	0xd0000000 - 0xcfffffff (0x0) MX[B]O
	[7] -1	0	0xe1010000 - 0xe101ffff (0x10000) MX[B](B)
	[8] -1	0	0xdc000000 - 0xdfffffff (0x4000000) MX[B](B)
	[9] -1	0	0xe1000000 - 0xe100ffff (0x10000) MX[B](B)
	[10] -1	0	0xd8000000 - 0xdbffffff (0x4000000) MX[B](B)
	[11] -1	0	0x0000ffff - 0x0000ffff (0x1) IX[B]
	[12] -1	0	0x00000000 - 0x000000ff (0x100) IX[B]
	[13] -1	0	0x0000e800 - 0x0000e8ff (0x100) IX[B]
	[14] -1	0	0x0000e400 - 0x0000e4ff (0x100) IX[B]
	[15] -1	0	0x0000e000 - 0x0000e01f (0x20) IX[B]
	[16] -1	0	0x0000dc00 - 0x0000dc1f (0x20) IX[B]
	[17] -1	0	0x0000d800 - 0x0000d81f (0x20) IX[B]
	[18] -1	0	0x0000d400 - 0x0000d41f (0x20) IX[B]
	[19] -1	0	0x0000d000 - 0x0000d00f (0x10) IX[B]
	[20] -1	0	0x0000c000 - 0x0000c0ff (0x100) IX[B](B)
(II) fglrx(0): pEnt->device->identifier=0x81fe3e8
(II) resource ranges after probing:
	[0] -1	0	0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
	[1] -1	0	0x000f0000 - 0x000fffff (0x10000) MX[B]
	[2] -1	0	0x000c0000 - 0x000effff (0x30000) MX[B]
	[3] -1	0	0x00000000 - 0x0009ffff (0xa0000) MX[B]
	[4] -1	0	0xe2001000 - 0xe20010ff (0x100) MX[B]
	[5] -1	0	0xe2000000 - 0xe20000ff (0x100) MX[B]
	[6] -1	0	0xd0000000 - 0xcfffffff (0x0) MX[B]O
	[7] -1	0	0xe1010000 - 0xe101ffff (0x10000) MX[B](B)
	[8] -1	0	0xdc000000 - 0xdfffffff (0x4000000) MX[B](B)
	[9] -1	0	0xe1000000 - 0xe100ffff (0x10000) MX[B](B)
	[10] -1	0	0xd8000000 - 0xdbffffff (0x4000000) MX[B](B)
	[11] 0	0	0x000a0000 - 0x000affff (0x10000) MS[B]
	[12] 0	0	0x000b0000 - 0x000b7fff (0x8000) MS[B]
	[13] 0	0	0x000b8000 - 0x000bffff (0x8000) MS[B]
	[14] -1	0	0x0000ffff - 0x0000ffff (0x1) IX[B]
	[15] -1	0	0x00000000 - 0x000000ff (0x100) IX[B]
	[16] -1	0	0x0000e800 - 0x0000e8ff (0x100) IX[B]
	[17] -1	0	0x0000e400 - 0x0000e4ff (0x100) IX[B]
	[18] -1	0	0x0000e000 - 0x0000e01f (0x20) IX[B]
	[19] -1	0	0x0000dc00 - 0x0000dc1f (0x20) IX[B]
	[20] -1	0	0x0000d800 - 0x0000d81f (0x20) IX[B]
	[21] -1	0	0x0000d400 - 0x0000d41f (0x20) IX[B]
	[22] -1	0	0x0000d000 - 0x0000d00f (0x10) IX[B]
	[23] -1	0	0x0000c000 - 0x0000c0ff (0x100) IX[B](B)
	[24] 0	0	0x000003b0 - 0x000003bb (0xc) IS[B]
	[25] 0	0	0x000003c0 - 0x000003df (0x20) IS[B]
(II) Setting vga for screen 0.
(II) fglrx(0): === [atiddxPreInit] === begin, [s]
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/lib/xorg/modules/libvgahw.so
(II) Module vgahw: vendor="X.Org Foundation"
	compiled for 7.1.1, module version = 0.1.0
	ABI class: X.Org Video Driver, version 1.0
(II) fglrx(0): PCI bus 1 card 0 func 0
(**) fglrx(0): Depth 24, (--) framebuffer bpp 32
(II) fglrx(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
(==) fglrx(0): Default visual is TrueColor
(==) fglrx(0): RGB weight 888
(II) fglrx(0): Using 8 bits per RGB (8 bit DAC)
(==) fglrx(0): Gamma Correction for I is 0x06419064
(==) fglrx(0): Gamma Correction for II is 0x06419064
(==) fglrx(0): Buffer Tiling is ON
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Loading /usr/lib/xorg/modules/libint10.so
(II) Module int10: vendor="X.Org Foundation"
	compiled for 7.1.1, module version = 1.0.0
	ABI class: X.Org Video Driver, version 1.0
(II) fglrx(0): Primary V_BIOS segment is: 0xc000
(EE) fglrx(0): Chipset 0x5961 is not recognized
(EE) fglrx(0): PreInitConfig failed
SetVBEMode failed
(EE) fglrx(0): PreInit failed
(II) fglrx(0): === [atiddxPreInit] === end
(II) UnloadModule: "fglrx"
(II) UnloadModule: "int10"
(II) Unloading /usr/lib/xorg/modules/libint10.so
(II) UnloadModule: "vgahw"
(II) Unloading /usr/lib/xorg/modules/libvgahw.so
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found






############
xorg.conf
############


#    Option "SampleRate"	"150"
# Mouse wheel mapping.  Default is to map vertical wheel to buttons 4 &
5,
# horizontal wheel to buttons 6 & 7.   Change if your mouse has more
than
# ############3 buttons and you need to map the wheel to different
button ids to avoid
# conflicts.
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
#    Option "Emulate3Buttons"
#    Option "Emulate3Timeout"    "50"
# ChordMiddle is an option for some 3-button Logitech mice
#    Option "ChordMiddle"
	Identifier  "Mouse1"
	Driver      "mouse"
	Option	    "Protocol" "IMPS/2"	# IntelliMouse PS/2
	Option	    "Device" "/dev/input/mice"
# When using XQUEUE, comment out the above two lines, and uncomment
	Option	    "ZAxisMapping" "4 5 6 7"
# Emulate3Buttons is an option for 2-button mice
EndSection

Section "Monitor"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
#    HorizSync	30-64         # multisync
#    HorizSync	31.5, 35.2    # multiple fixed sync frequencies
#    HorizSync	15-25, 30-50  # multiple ranges of sync frequencies
# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
	Identifier   "My Monitor"
	HorizSync    30.0 - 130.0
	VertRefresh  50.0 - 160.0
	ModeLine     "1600x1200_99.00" 277.6 1600 1728 1904 2208 1200 1201
1204 1270 -hsync +vsync
EndSection

Section "Monitor"
	Identifier   "aticonfig-Monitor[0]"
	Option	    "VendorName" "ATI Proprietary Driver"
	Option	    "ModelName" "Generic Autodetecting Monitor"
	Option	    "DPMS" "true"
EndSection

Section "Device"

# The chipset line is optional in most cases.  It can be used to
override
# the driver's chipset detection, and should not normally be specified.
#    Chipset	"generic"
# The Driver line must be present.  When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module.  Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this
section.
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for.  When this line isn't present, a device
# section can only match up with the primary video device.  For PCI
# devices a line like the following could be used.  This line should
not
# normally be included unless there is more than one video device
# intalled.
#    BusID      "PCI:0:10:0"
#    VideoRam	256
#    Clocks	25.2 28.3
	Identifier  "Standard VGA"
	Driver      "vga"
	VendorName  "Unknown"
	BoardName   "Unknown"
EndSection

Section "Device"

    #VideoRam    65536
    # Insert Clocks lines here if appropriate
	Identifier  "* Generic VESA compatible"
	Driver      "vesa"
EndSection

Section "Device"
	Identifier  "aticonfig-Device[0]"
	Driver      "fglrx"
EndSection

Section "Screen"
	Identifier "Screen 1"
	Device     "* Generic VESA compatible"
	Monitor    "My Monitor"
	DefaultDepth     24
	SubSection "Display"
		Viewport   0 0
		Depth     8
		Modes    "1280x1024" "1024x768" "800x600" "640x480"
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     16
		Modes    "1280x1024" "1024x768" "800x600" "640x480"
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     24
		Modes    "1600x1200" "1024x768" "800x600" "640x480"
	EndSubSection
EndSection

Section "Screen"
	Identifier "aticonfig-Screen[0]"
	Device     "aticonfig-Device[0]"
	Monitor    "aticonfig-Monitor[0]"
	DefaultDepth     24
	SubSection "Display"
		Viewport   0 0
		Depth     24
		Modes    "1600x1200" "1280x1024" "1024x768"
	EndSubSection
EndSection






-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Screen(s) found, but none have a usable configuration

[Richard Fish]

On 11/26/06, burmata@dir.bg <burmata@dir.bg> wrote:
> (--) PCI:*(1:0:0) ATI Technologies Inc RV280 [Radeon 9200] rev 1, Mem @
> 0xd8000000/26, 0xe1000000/16, I/O @ 0xc000/8
> (--) PCI: (1:0:1) ATI Technologies Inc RV280 [Radeon 9200] (Secondary)

[snip]

> (II) ATI Radeon/FireGL: The following chipsets are supported:

[snip bunch of supported cards, Radeon 9200/RV280 not listed]

> (EE) fglrx(0): Chipset 0x5961 is not recognized
> (EE) fglrx(0): PreInitConfig failed

Apparently ati-drivers-8.29.6 does not support the Radeon 9200.  You
should probably use the opensource 'radeon' driver instead.  Replace
fglrx with radeon in VIDEO_CARDS in /etc/make.conf, and "emerge
--oneshot xorg-server".  That should bring in xf86-video-ati, and you
can then replace the fglrx driver in xorg.conf with radeon.

FYI, the radeon driver offers full 3D support for the 9200 if you
enable the right kernel drivers also.

-Richard
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Screen(s) found, but none have a usable configuration

[burmata]

thanks 

On Sun, 26 Nov 2006 15:31:30 -0700
 "Richard Fish" <bigfish@asmallpond.org> wrote:
> On 11/26/06, burmata@dir.bg <burmata@dir.bg> wrote:
> > (--) PCI:*(1:0:0) ATI Technologies Inc RV280 [Radeon 9200] rev 1,
> Mem @
> > 0xd8000000/26, 0xe1000000/16, I/O @ 0xc000/8
> > (--) PCI: (1:0:1) ATI Technologies Inc RV280 [Radeon 9200]
> (Secondary)
> 
> [snip]
> 
> > (II) ATI Radeon/FireGL: The following chipsets are supported:
> 
> [snip bunch of supported cards, Radeon 9200/RV280 not listed]
> 
> > (EE) fglrx(0): Chipset 0x5961 is not recognized
> > (EE) fglrx(0): PreInitConfig failed
> 
> Apparently ati-drivers-8.29.6 does not support the Radeon 9200.  You
> should probably use the opensource 'radeon' driver instead.  Replace
> fglrx with radeon in VIDEO_CARDS in /etc/make.conf, and "emerge
> --oneshot xorg-server".  That should bring in xf86-video-ati, and you
> can then replace the fglrx driver in xorg.conf with radeon.
> 
> FYI, the radeon driver offers full 3D support for the 9200 if you
> enable the right kernel drivers also.
> 
> -Richard
> -- 
> gentoo-user@gentoo.org mailing list
> 

 Best regards!
_______________________
 
Blagovest Shtarkelov
Customer Support Officer
Info-center Dir.bg
139 Vitosha St., 1408 Sofia
Phone: + 359 [2] 953 08 38
Phone: + 359 [2] 953 28 38
Fax: +359 [2]  953 27 90
GSM gate: +359 0887 261 987
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OT: wlan0 is sssloooow

[Richard Fish]

On 11/26/06, Sergio Polini <sp_rm_it@yahoo.it> wrote:
> My pings (perhaps all DNS lookups) are slow even if connect my PC to
> both the wireless router and the cable, i.e. when there are both
> a "fast" (metric 0) and a "slow" (metric 2000) interface.
>
> > What do "ifconfig wlan" and "iwconfig wlan" report for the fast and
> > slow states?
>
> Fast (i.e. normal ;-) state happens only when net.wlan0 is stopped.
> When I start net.wlan0:

Are both wired and wireless enabled?  Your original posting doesn't
show any records for eth0.  In the 'slow' state, what is the output of
'ifconfig -a' and route?

-Richard
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OT: wlan0 is sssloooow

[Sergio Polini]

Richard Fish:
> On 11/26/06, Sergio Polini <sp_rm_it@yahoo.it> wrote:
> > My pings (perhaps all DNS lookups) are slow even if connect my PC
> > to both the wireless router and the cable, i.e. when there are
> > both a "fast" (metric 0) and a "slow" (metric 2000) interface.
> >
> > > What do "ifconfig wlan" and "iwconfig wlan" report for the fast
> > > and slow states?
> >
> > Fast (i.e. normal ;-) state happens only when net.wlan0 is
> > stopped. When I start net.wlan0:
>
> Are both wired and wireless enabled?  Your original posting doesn't
> show any records for eth0.  In the 'slow' state, what is the output
> of 'ifconfig -a' and route?

Hi Richard!
Here are three cases.

Cases #1 - Cold boot, only wire enabled

sergio ~ # ifconfig -a
eth0  Link encap:Ethernet  HWaddr 00:16:D3:09:2D:17
   inet addr:XX.XXX.XXX.250  Bcast:255.255.255.255  Mask:255.255.248.0
   UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
   RX packets:1728 errors:0 dropped:0 overruns:0 frame:0
   TX packets:1408 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:1000
   RX bytes:917612 (896.1 Kb)  TX bytes:165737 (161.8 Kb)
   Interrupt:16

gre0  Link encap:UNSPEC
   HWaddr 00-00-00-00-00-00-CF-A2-00-00-00-00-00-00-00-00
   NOARP  MTU:1476  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:0
   RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

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:19 errors:0 dropped:0 overruns:0 frame:0
   TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:0
   RX bytes:1119 (1.0 Kb)  TX bytes:1119 (1.0 Kb)

sergio ~ # route
Kernel IP routing table
Destination  Gateway      Genmask       Flags Metric Ref Use Iface
23.252.112.0 *            255.255.248.0 U     0      0     0 eth0
loopback     *            255.0.0.0     U     0      0     0 lo
default      23.252.112.1 0.0.0.0       UG    0      0     0 eth0

NB: gre0 should be there because of an error in my kernel .config:
CONFIG_NET_IPGRE=y
;-)
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OT: wlan0 is sssloooow

[Sergio Polini]

Richard Fish:
> On 11/26/06, Sergio Polini <sp_rm_it@yahoo.it> wrote:
> > My pings (perhaps all DNS lookups) are slow even if connect my PC
> > to both the wireless router and the cable, i.e. when there are
> > both a "fast" (metric 0) and a "slow" (metric 2000) interface.
> >
> > > What do "ifconfig wlan" and "iwconfig wlan" report for the fast
> > > and slow states?
> >
> > Fast (i.e. normal ;-) state happens only when net.wlan0 is
> > stopped. When I start net.wlan0:
>
> Are both wired and wireless enabled?  Your original posting doesn't
> show any records for eth0.  In the 'slow' state, what is the output
> of 'ifconfig -a' and route?
>
> -Richard

Sorry, I pressed "Send Mail" instead of "Save in Drafts Folder" ;-)
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OT: wlan0 is sssloooow

[Sergio Polini]

Richard Fish:
> On 11/26/06, Sergio Polini <sp_rm_it@yahoo.it> wrote:
> > My pings (perhaps all DNS lookups) are slow even if connect my PC
> > to both the wireless router and the cable, i.e. when there are
> > both a "fast" (metric 0) and a "slow" (metric 2000) interface.
> >
> > > What do "ifconfig wlan" and "iwconfig wlan" report for the fast
> > > and slow states?
> >
> > Fast (i.e. normal ;-) state happens only when net.wlan0 is
> > stopped. When I start net.wlan0:
>
> Are both wired and wireless enabled?  Your original posting doesn't
> show any records for eth0.  In the 'slow' state, what is the output
> of 'ifconfig -a' and route?

I apologize for my error.
However....

Case #1 - Cold boot, only wire enabled
--------------------------------------
(without CONFIG_NET_IPGRE)
net.eth0 in default runlevel.

sergio ~ # ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:16:D3:09:2D:17
  inet addr:XX.XXX.XXX.250  Bcast:255.255.255.255  Mask:255.255.248.0
  UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:20 errors:0 dropped:0 overruns:0 frame:0
  TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:1578 (1.5 Kb)  TX bytes:1669 (1.6 Kb)
  Interrupt:16

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:19 errors:0 dropped:0 overruns:0 frame:0
  TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:1119 (1.0 Kb)  TX bytes:1119 (1.0 Kb)

sergio ~ # route
Kernel IP routing table
Destination  Gateway      Genmask       Flags Metric Ref Use Iface
23.252.112.0 *            255.255.248.0 U     0      0     0 eth0
loopback     *            255.0.0.0     U     0      0     0 lo
default      23.252.112.1 0.0.0.0       UG    0      0     0 eth0

sergio ~ # cat /etc/resolv.conf
# Generated by dhcpcd for interface eth0
search fastwebnet.it
nameserver 213.156.54.80
nameserver 213.156.54.81

NB: route and ping www.google.com are fast.

Case #2 - Cold boot, only wireless enabled
------------------------------------------
net.eth0 deleted from default runlevel.
After modprobe ndiswrapper and /etc/init.d/net.wlan0 start:

sergio ~ # ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:16:D3:09:2D:17
   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:16

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:19 errors:0 dropped:0 overruns:0 frame:0
   TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:0
   RX bytes:1119 (1.0 Kb)  TX bytes:1119 (1.0 Kb)

wlan0     Link encap:Ethernet  HWaddr 00:14:A5:E1:D2:B9
   inet addr:192.168.2.2  Bcast:192.168.2.255  Mask:255.255.255.0
   UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
   RX packets:11 errors:0 dropped:0 overruns:0 frame:0
   TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:1000
   RX bytes:1483 (1.4 Kb)  TX bytes:1922 (1.8 Kb)
   Interrupt:20 Memory:c3000000-c3004000

sergio ~ # route
Kernel IP routing table
Destination Gateway     Genmask       Flags Metric Ref Use Iface
192.168.2.0 *           255.255.255.0 U     2000   0     0 wlan0
loopback    *           255.0.0.0     U     0      0     0 lo
default     192.168.2.1 0.0.0.0       UG    2000   0     0 wlan0

sergio ~ # cat /etc/resolv.conf
# Generated by dhcpcd for interface wlan0
search Belkin
nameserver 192.168.2.1
nameserver 213.156.54.80
nameserver 213.156.54.81

NB: ping www.google.com is slow, ping 192.168.2.1 is either too much 
slow or blocked ;-) But works under Windows.
route is slow, route -n is fast.

Case #3 - Cold boot, wire and wireless enabled
----------------------------------------------
net.eth0 in default runlevel.
After modprobe ndiswrapper:

sergio ~ # ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:16:D3:09:2D:17
  inet addr:XX.XXX.XXX.250  Bcast:255.255.255.255  Mask:255.255.248.0
  UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:18 errors:0 dropped:0 overruns:0 frame:0
  TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:1559 (1.5 Kb)  TX bytes:1795 (1.7 Kb)
  Interrupt:16

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:19 errors:0 dropped:0 overruns:0 frame:0
  TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:1119 (1.0 Kb)  TX bytes:1119 (1.0 Kb)

wlan0     Link encap:Ethernet  HWaddr 00:14:A5:E1:D2:B9
  inet addr:192.168.2.2  Bcast:192.168.2.255  Mask:255.255.255.0
  UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:4 errors:0 dropped:0 overruns:0 frame:0
  TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:834 (834.0 b)  TX bytes:1316 (1.2 Kb)
  Interrupt:20 Memory:c3000000-c3004000

sergio ~ # route
Kernel IP routing table
Destination  Gateway      Genmask       Flags Metric Ref Use Iface
192.168.2.0  *            255.255.255.0 U     2000   0     0 wlan0
23.252.112.0 *            255.255.248.0 U     0      0     0 eth0
loopback     *            255.0.0.0     U     0      0     0 lo
default      23.252.112.1 0.0.0.0       UG    0      0     0 eth0
default      192.168.2.1  0.0.0.0       UG    2000   0     0 wlan0

sergio ~ # cat /etc/resolv.conf
# Generated by dhcpcd for interface wlan0
search Belkin
nameserver 192.168.2.1
nameserver 213.156.54.80
nameserver 213.156.54.81

NB: ping www.google.com is slow, ping 192.168.2.1 is either too much 
slow or blocked.
route is slow, route -n is fast.

Thank for your patience.
Sergio
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OT: wlan0 is sssloooow

[Hans de Hartog]

Sergio Polini wrote:
<snip>
> default      23.252.112.1 0.0.0.0       UG    0      0     0 eth0
> default      192.168.2.1  0.0.0.0       UG    2000   0     0 wlan0
<snip>
I didn't follow this thread completeley but having two default routes
is definitly the cause of slow (or even unworkable) networking.

I would write a script that is run at bootlevel to determine if
you have eth0 or wlan0 or both and change things at the default
level accordingly (including dhcp, iptables, routing and maybe
other things as well).
I did this on several machines and laptops. If the existence of
wlan0 depends on a pcmcia card you can simply test it at bootlevel
with ifconfig. If wlan0 is always existing (e.g. by a pci-nic) but
you don't want to use it, you might create different ways of
booting the system (with or without wlan0) by suffixing your
kernelcommand in grub.conf with wlan0 or not and in your script
test with "grep wlan0 /proc/commandline" (or something like that).

Regards,
Hans.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OT: wlan0 is sssloooow

[Richard Fish]

On 11/27/06, Sergio Polini <sp_rm_it@yahoo.it> wrote:
> NB: ping www.google.com is slow, ping 192.168.2.1 is either too much
> slow or blocked.
> route is slow, route -n is fast.

Ok, two things to try.  First, remove the 192.168.2.1 nameserver from
resolve.conf.  That "nameserver" may be broken and unable to resolve
names on the internet.  This should help the "ping www.google.com"
case.

Second, does "ping -I wlan0 192.168.2.1" work better?

Oh, one last thing....you don't have any firewall rules enabled,
right?  (iptables --list)

-Richard
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OT: wlan0 is sssloooow [99% SOLVED]

[Sergio Polini]

Richard Fish:
> Ok, two things to try.  First, remove the 192.168.2.1 nameserver
> from resolve.conf.  That "nameserver" may be broken and unable to
> resolve names on the internet.  This should help the "ping
> www.google.com" case.

Yes, I've already said that, but.... you are great! ;-)
I read your message this morning quickly, when I was going to work, 
and didn'understand it.
Then I've spoken to a colleague of mine, a true network guru, a very 
capable ethical hacker, and I've understood! (I suppose....)
My wireless router:
a) runs a (WAN) DHCP client to get its IP address and the IP addresses 
of my provider's nameservers;
b) it get those IP addresses to send them to me when I run a DHCP 
client; my wireless router runs a (LAN) DHCP server too, but it is 
*not* a nameserver;
c) my DHCP client was configured as usual, i.e. "replace 
my /etc/resolv.conf"; I've added

dhcpcd_toynet="-R -h sergio"
               ^^

to /etc/conf.d/wireless and restarted /etc/init.d/net.wlan0.
Now... there is no line "nameserver 192.168.2.1" in 
my /etc/resolv.conf and ping www.google.com is fast ;-)

BTW: This evening I've started running Windows at first. ipconfig /all 
showed three nameservers, and 192.168.2.1 was the first one.
However, when I ran nslookup, the message was clear: 192.168.2.1 is 
not a nameserver. Why the difference between fast (Windows) and slow 
(my previous Gentoo box) Internet pings? Perhaps because the Windows 
timeout is short: 2 seconds. I do not know how to eventually set such 
a timeout in Linux....

> Second, does "ping -I wlan0 192.168.2.1" work better?

Nope. ping <-I wlan0 or -n> 192.168.2.1 is still blocked.
Well, it's just a nuisance, but I'll keep looking for a solution.
Any hints would be greately appreciated ;-)
That's not strange, because:

sergio ~ # nmap -sS -O -PI -PT 192.168.2.1

Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2006-11-28 
22:21 CET
Interesting ports on 192.168.2.1:
Not shown: 1678 closed ports
PORT     STATE    SERVICE
80/tcp   open     http
4662/tcp filtered edonkey
MAC Address: 00:17:3F:0C:19:12 (Belkin)
Device type: broadband router
Running: Netgear embedded
OS details: Netgear Wireless router or Netgear FM114P/REPOTEC IP515H 
Router & Print Server

Nmap finished: 1 IP address (1 host up) scanned in 4.834 seconds

i.e., port 7 (Echo) looks closed. Does Windows' ping (which works) 
speak eDonkey? (very OT question ;-)

> Oh, one last thing....you don't have any firewall rules enabled,
> right?  (iptables --list)

Right. I wish to configure my real (wire and wireless connection to my 
ISP) and virtual (VMWare) networks, and then enable iptables.

Thanks a lot, as usual ;-)
Sergio

PS: I wish to thank Thomas Sjolshagen (private message) and Hans de 
Hartog too. If one doesn't feel lonely when he tries to solve a 
problem, well.... that helps a lot! My English is poor, but I hope 
that you understand what I mean ;-)
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OT: wlan0 is sssloooow [100% SOLVED]

[Sergio Polini]

Yes, it was OT and very few of you are interested ;-)
However, somebody would like to know who the killer was.

The original subject was "wlan0 is sssloooow [99% SOLVED]" because  
pinging the Belkin F5D7230-4 wireless router worked from Windows but 
not from Linux.
The answer is: because Windows sends ICMP messages with 32 bytes of 
data, Linux sends them with 56 bytes of data.
Moreover, Linux IP datagrams have the DF (don't fragment) bit set, 
Windows ones have not.
On Linux, ping -s 15 192.168.2.2 works.

Cheers
Sergio
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OT: wlan0 is sssloooow [100% SOLVED]

[Mick]

[-- Attachment #1: Type: text/plain, Size: 802 bytes --]

On Monday 11 December 2006 20:56, Sergio Polini wrote:
> Yes, it was OT and very few of you are interested ;-)
> However, somebody would like to know who the killer was.
>
> The original subject was "wlan0 is sssloooow [99% SOLVED]" because
> pinging the Belkin F5D7230-4 wireless router worked from Windows but
> not from Linux.
> The answer is: because Windows sends ICMP messages with 32 bytes of
> data, Linux sends them with 56 bytes of data.
> Moreover, Linux IP datagrams have the DF (don't fragment) bit set,
> Windows ones have not.
> On Linux, ping -s 15 192.168.2.2 works.

How did you ever find this out?!  I'll know that's another thing to test when 
an access point is playing up.  I wonder why belkin is set up this way.

Thanks for sharing.  :-)

-- 
Regards,
Mick

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] OT: wlan0 is sssloooow [100% SOLVED]

[Sergio Polini]

Mick:
> On Monday 11 December 2006 20:56, Sergio Polini wrote:
> > Yes, it was OT and very few of you are interested ;-)
> > However, somebody would like to know who the killer was.
> >
> > The original subject was "wlan0 is sssloooow [99% SOLVED]"
> > because pinging the Belkin F5D7230-4 wireless router worked from
> > Windows but not from Linux.
> > The answer is: because Windows sends ICMP messages with 32 bytes
> > of data, Linux sends them with 56 bytes of data.
> > Moreover, Linux IP datagrams have the DF (don't fragment) bit
> > set, Windows ones have not.
> > On Linux, ping -s 15 192.168.2.2 works.
>
> How did you ever find this out?!

I used two "tools": Douglas Comer, "Internetworking with TCP/IP", and 
Wireshark (former ethereal).
I'm still installing my new laptop, f.i., I've not yet setup a 
firewall. My former firewall was based on the "Iptables Tutorial" by 
Oskar Andreasson, but I didn't understand all the details. So I've 
started studying, i.e. reading Comer and looking at frames, 
datagrams, etc. by Wireshark.
I needed that. For example, I had used nmap to look for an echo port 
on the Belkin router, but ping, i.e. ICMP, doesn't know anything 
about ports!
As to the ping problem, I started a Windows virtual machine by VMware 
Player, then Wireshark both in the Linux "real" machine and in the 
virtual one, then pinged the Belkin router. Looking at the output 
produced by the Linux Wireshark and by the virtual Windows one, there 
were just two differences: the DF bit, and the data field length in 
the ICMP messages.

> I'll know that's another thing to test when an access point
> is playing up. I wonder why belkin is set up this way.

I think that a router should send ICMP messages such as "fragmentation 
needed and DF set" (Type 3, , Code 4) and "time to live exceeded in 
transit" (Type 11, , Code 0), but Belkin does not (traceroute, and 
tracert, 192.168.2.1 print stars).
The Belkin 54G wireless router, F5D7130, had serious security holes:
http://www.governmentsecurity.org/archive/t15618.html
My model, F5D7230, is more secure. Eventually too much ;-)

> Thanks for sharing.  :-)

Alan McKinnon:
> I'm very glad you did post this update as here in the office we had
> this very problem three weeks ago. One morning every non-Windows
> host in our building suddenly could not see past the gateway, could
> not ping it and was essentially off-air. We eventually tracked it
> down to one of these Belkin wireless routers, but never figured out
> why it was doing what it did.
>
> Now we do know, so thanks for the heads-up!

I must thank all of you. Gentoo would not be such an attractive system 
without the continuous support by all of you.

Sergio
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OT: wlan0 is sssloooow [100% SOLVED]

[Alan McKinnon]

On Monday 11 December 2006 22:56, Sergio Polini wrote:
> Yes, it was OT and very few of you are interested ;-)
> However, somebody would like to know who the killer was.
>
> The original subject was "wlan0 is sssloooow [99% SOLVED]" because
> pinging the Belkin F5D7230-4 wireless router worked from Windows but
> not from Linux.
> The answer is: because Windows sends ICMP messages with 32 bytes of
> data, Linux sends them with 56 bytes of data.
> Moreover, Linux IP datagrams have the DF (don't fragment) bit set,
> Windows ones have not.
> On Linux, ping -s 15 192.168.2.2 works.

I'm very glad you did post this update as here in the office we had this 
very problem three weeks ago. One morning every non-Windows host in our 
building suddenly could not see past the gateway, could not ping it and 
was essentially off-air. We eventually tracked it down to one of these 
Belkin wireless routers, but never figured out why it was doing what it 
did. 

Now we do know, so thanks for the heads-up!

alan

-- 
gentoo-user@gentoo.org mailing list