по поводу броадком вроде разобрался, а вот че делать с ралинком 3090, нашел пакетик на ауре
aur/rt3090 2.4.0.1_20101110-1
но yourt не собирает его :
==> Запускается build()...
/tmp/yaourt-tmp-psl/aur-rt2860-firmware/./PKGBUILD: line 14: cd: /tmp/yaourt-tmp-psl/aur-rt2860-firmware/src/RT2860_Firmware_V26: Нет такого файла или каталога
    Преждевременный выход...
==> ERROR: Makepkg was unable to build rt2860-firmware.
==> Restart building rt2860-firmware ? [y/N]

==> Continue building rt3090 ? [Y/n]
==> --------------------------------
==> 
==> Building and installing package
==> Install or build missing dependencies for rt3090:
Пароль: 
ошибка: 'kernel26<2.6.36': не удалось найти или прочитать пакет
Dependencies kernel26>=2.6.35 kernel26<2.6.36
Придется ждать пока кто то соберет пакетик под новое ядро. А пока попробую покапать офсай ралинка
Вот тут есть дравишки на ралинк наш >> http://www.ralinktech.com/support.php?s=2 сейчас собираю make`ом посмотрим что выйдет…
nobus так у меня broadcom-wl только на HP ProBook 4515s.
[[email protected] ~]$ hwdetect --show-net
NET    : sky2 bluetooth rfkill wl lib80211
[[email protected] ~]$ lspci | grep -i net 
02:00.0 Ethernet controller: Marvell Technology Group Ltd. Device 436c (rev 10)
06:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g (rev 01)

на eeepc 1015P
[[email protected] ~]$ hwdetect --show-net
NET    : atl1c mac80211 rfkill rt2800lib rt2800pci rt2x00lib rt2x00pci cfg80211
[[email protected] ~]$ lspci | grep -i net
01:00.0 Ethernet controller: Atheros Communications Atheros AR8132 / L1c Gigabit Ethernet Adapter (rev c0)
02:00.0 Network controller: RaLink RT3090 Wireless 802.11n 1T/1R PCIe
А сейчас прошли коры повеселее, подключил к eeepc провод с инетом, и мой большой (HP ProBook 4515s) поймал вайфай, теперь самое интересное, выдерживаю шнур из еееПС и вафай отваливает и на большом! Причем работает вайфай только на НР!!! коры какие то…. не че не понимаю, в Винде вайфай работает одновременно на обоих ноутах без проблем! так что вина ну не как не роутера! =))) Не че не понимаю =)))))
пробовал поставить wicd и wifi-radar оба при попытке подключится виснут, запрещал демон networmanagera в rc.conf, и хоть бы хны…
Вот еще кстати :

$ sudo iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

eth1 IEEE 802.11bg ESSID:“” Nickname:“”
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power:24 dBm
Retry min limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=5/5 Signal level=0 dBm Noise level=-91 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Блин в чем проблема может быть? неужели в ядре?
В общем 2а ноута с Арчем, HP ProBook 4515s с Броадком, стоят дровишки broadcom-wl из aur, и eeepc.
Вчера обновилось ядро и куча всего с ним, метров 200 вроде как, так вот после этого отвалилось многое, каталист дравишки, компиз на обоих ноутах и куча еще всего, все настроил кроме сети, пришлось дравишки обновить и на вайфаи, так в общем пользуюсь networkmanager в gnome, сеть видит, нажимаю подключится, он думает думает и не как не может подключится, потом вылезает окошко с выбором типа шифрования и с вводом ключа, причем до обнавления на обоих компах все работало отлично! а теперь не на одном по воздуху не могу подключится…
Вайфай беру с роутера Dlink - DIR-320 c опенврт прошивкой на борту, под виндой все тип топ работает, по кабелю в линухе тоже все отлично.
Откатываться на старое ядро + нетворкманагер не хочется…
Кто что посоветует?
Пытался менять тип шифрования и т.п. без полезно, совсем без шифрования и пароля точка доступа не хочет работать.
=) Вот его то у меня и не было, спасибо!

Вопрос решен.
В общем сильно не пинайте но не как могу понять как настроить сеть между Роутером (D-LINK DIR-320 + HDD) + Большим ноутом (Минт Дебиан Едишен) и Нетбуке с Арчем.
На роутере линуХ стоит ну и самба в общем там, так как дома еще и стационариник с Виндой стоит, вобщем Винда и Минт работают нормально (там настроек то…) а вот в арче я не как не могу понять что не так настраиваю.
Подробнее о Арче, пинг на другой ноут идет нормально :
[[email protected] ~]ping 192.168.1.186 -I wlan0
PING 192.168.1.186 (192.168.1.186) from 192.168.1.247 wlan0: 56(84) bytes of data.
64 bytes from 192.168.1.186: icmp_seq=1 ttl=64 time=4.16 ms
64 bytes from 192.168.1.186: icmp_seq=2 ttl=64 time=99.0 ms
64 bytes from 192.168.1.186: icmp_seq=3 ttl=64 time=3.92 ms
64 bytes from 192.168.1.186: icmp_seq=4 ttl=64 time=40.2 ms
По ssh тоже и все работает прекрасно.

Самба в арче как я понял в одном пакете и клиент и сервер, как понял по вики то особо сильно настраивать не нужно:

/etc/samba/smb.conf
[global]
# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
   workgroup = WORKGROUP
# server string is the equivalent of the NT Description field
   server string = %h server
# Security mode. Defines in which mode Samba will operate. Possible 
# values are share, user, server, domain and ads. Most people will want 
# user level security. See the Samba-HOWTO-Collection for details.
   security = user
# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
;   hosts allow = 192.168.1. 192.168.2. 127.
# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
   load printers = yes
# you may wish to override the location of the printcap file
;   printcap name = /etc/printcap
# on SystemV system setting printcap name to lpstat should allow
# you to automatically obtain a printer list from the SystemV spool
# system
;   printcap name = lpstat
# It should not be necessary to specify the print system type unless
# it is non-standard. Currently supported print systems include:
# bsd, cups, sysv, plp, lprng, aix, hpux, qnx
;   printing = cups
# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
;  guest account = pcguest
# this tells Samba to use a separate log file for each machine
# that connects
   log file = /var/log/samba/%m.log
# Put a capping on the size of the log files (in Kb).
   max log size = 50
# Use password server option only with security = server
# The argument list may include:
#   password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
# or to auto-locate the domain controller/s
#   password server = *
;   password server = <NT-Server-Name>
# Use the realm option only with security = ads
# Specifies the Active Directory realm the host is part of
;   realm = MY_REALM
# Backend to store user information in. New installations should 
# use either tdbsam or ldapsam. smbpasswd is available for backwards 
# compatibility. tdbsam requires no further configuration.
;   passdb backend = tdbsam
# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting.
# Note: Consider carefully the location in the configuration file of
#       this line.  The included file is read at that point.
;   include = /usr/local/samba/lib/smb.conf.%m
# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
;   interfaces = 192.168.12.2/24 192.168.13.2/24 
# Browser Control Options:
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
;   local master = no
# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
;   os level = 33
# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
;   domain master = yes 
# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
;   preferred master = yes
# Enable this if you want Samba to be a domain logon server for 
# Windows95 workstations. 
;   domain logons = yes
# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
;   logon script = %m.bat
# run a specific logon batch file per username
;   logon script = %U.bat
# Where to store roving profiles (only for Win95 and WinNT)
#        %L substitutes for this servers netbios name, %U is username
#        You must uncomment the [Profiles] share below
;   logon path = \\%L\Profiles\%U
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
;   wins support = yes
# WINS Server - Tells the NMBD components of Samba to be a WINS Client
#	Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
;   wins server = w.x.y.z
# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one	WINS Server on the network. The default is NO.
;   wins proxy = yes
# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The default is NO.
   dns proxy = no 
# These scripts are used on a domain controller or stand-alone 
# machine to add or delete corresponding unix accounts
;  add user script = /usr/sbin/useradd %u
;  add group script = /usr/sbin/groupadd %g
;  add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
;  delete user script = /usr/sbin/userdel %u
;  delete user from group script = /usr/sbin/deluser %u %g
;  delete group script = /usr/sbin/groupdel %g
#============================ Share Definitions ==============================
[homes]
   comment = Home Directories
   browseable = no
   writable = yes
# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
;   comment = Network Logon Service
;   path = /usr/local/samba/lib/netlogon
;   guest ok = yes
;   writable = no
;   share modes = no
# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
;    path = /usr/local/samba/profiles
;    browseable = no
;    guest ok = yes
# NOTE: If you have a BSD-style print system there is no need to 
# specifically define each individual printer
[printers]
   comment = All Printers
   path = /var/spool/samba
   browseable = no
# Set public = yes to allow user 'guest account' to print
   guest ok = no
   writable = no
   printable = yes
# This one is useful for people to share files
;[tmp]
;   comment = Temporary file space
;   path = /tmp
;   read only = no
;   public = yes
# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
;   comment = Public Stuff
;   path = /home/samba
;   public = yes
;   writable = no
;   printable = no
;   write list = @staff
# Other examples. 
#
# A private printer, usable only by fred. Spool data will be placed in fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
;[fredsprn]
;   comment = Fred's Printer
;   valid users = fred
;   path = /homes/fred
;   printer = freds_printer
;   public = no
;   writable = no
;   printable = yes
# A private directory, usable only by fred. Note that fred requires write
# access to the directory.
;[fredsdir]
;   comment = Fred's Service
;   path = /usr/somewhere/private
;   valid users = fred
;   public = no
;   writable = yes
;   printable = no
# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %U option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
;  comment = PC Directories
;  path = /usr/pc/%m
;  public = no
;  writable = yes
# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.
;[public]
;   path = /usr/somewhere/else/public
;   public = yes
;   only guest = yes
;   writable = yes
;   printable = no
# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
;[myshare]
;   comment = Mary's and Fred's stuff
;   path = /usr/somewhere/shared
;   valid users = mary fred
;   public = no
;   writable = yes
;   printable = no
;   create mask = 0765

но вот не как не могу сделать чтобы в Наутилусе во вкладке СЕТЬ у меня появился хоть какой нибудь из компов, причем не видно не одного не винду не соседей не линь
через лайф флешку отгрузился. сделал fsck -f <раздел> все заработало, тока руганулся на Gconf и gdm был страшным (без темы), ща обновлюсь посмотрим что дальше будет
ls / -la
итого 80
drwxr-xr-x 20 root root  4096 Окт 18 02:40 .
drwxr-xr-x 20 root root  4096 Окт 18 02:40 ..
drwxr-xr-x  2 root root  4096 Окт 17 14:51 bin
drwxr-xr-x  3 root root  4096 Окт 14 11:42 boot
drwx------  3 root root  4096 Окт 15 14:41 .dbus
drwxr-xr-x 16 root root  5240 Окт 18 02:05 dev
drwxr-xr-x 71 root root  4096 Окт 18 02:05 etc
drwxr-xr-x  4 root root  4096 Окт 13 19:12 home
-?????????  ? ?    ?        ?            ? .ismount-test-file
drwxr-xr-x  9 root root  4096 Окт 15 12:49 lib
drwx------  2 root root 16384 Окт 13 19:03 lost+found
drwxr-xr-x  6 root root  4096 Окт 18 02:02 media
drwxr-xr-x  5 root root  4096 Окт 16 12:07 mnt
drwxr-xr-x  4 root root  4096 Окт 15 00:13 opt
dr-xr-xr-x 92 root root     0 Окт 18  2010 proc
drwxr-x--- 12 root root  4096 Окт 18 02:46 root
drwxr-xr-x  2 root root  4096 Окт 17 22:44 sbin
drwxr-xr-x  4 root root  4096 Сен 19 04:58 srv
drwxr-xr-x 12 root root     0 Окт 18  2010 sys
d?????????  ? ?    ?        ?            ? tmp
drwxr-xr-x 10 root root  4096 Окт 16 11:49 usr
drwxr-xr-x 15 root root  4096 Окт 15 17:11 var

df -h
Файловая система      Разм  Исп  Дост  Исп% смонтирована на
udev                   10M  168K  9,9M   2% /dev
/dev/sda1             9,7G  5,0G  4,2G  55% /
shm                  1004M     0 1004M   0% /dev/shm
/dev/sda4             119G  7,5G  106G   7% /home
А можно пару слов о смысле дублирования /tmp куда-то еще?
Проверить хотелось будет ли монтировать.
Ну и fstab и mtab тоже посмотреть мона?
Конечно, вот :
fstab
#  
# /etc/fstab: static file system information
#
# <file system>        <dir>         <type>    <options>          <dump> <pass>
devpts                 /dev/pts      devpts    defaults            0      0
shm                    /dev/shm      tmpfs     nodev,nosuid        0      0
#/dev/cdrom             /media/cd   auto    ro,user,noauto,unhide   0      0
#/dev/dvd               /media/dvd  auto    ro,user,noauto,unhide   0      0
#/dev/fd0               /media/fl   auto    user,noauto             0      0
/dev/sda1 / ext3 defaults 0 1
/dev/sda4 /home ext3 defaults 0 1

mtab
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
udev /dev devtmpfs rw,nosuid,relatime,size=10240k,nr_inodes=218533,mode=755 0 0
/dev/sda1 / ext3 rw,relatime,errors=continue,barrier=0,data=writeback 0 0
devpts /dev/pts devpts rw 0 0
shm /dev/shm tmpfs rw,nosuid,nodev 0 0
/dev/sda4 /home ext3 rw 0 0
/dev/sdb1 /media/flash vfat rw 0 0