You are not logged in.
Pages: 1
Hi archers, I' ve a little problem with my laptop wireless card
My lappy has a broadcom card, and I' ve used the wiki to set the connection
I' ve also installed gnome-network-manager.
When I boot, network manager load but It doesn' t connect to the network also if It find it.... If I click the icon of network-manager my wifi-network is in the list, but I cannot connect to
The only way is to select "connect to a new network" in the network-manager menu and retype the ESSID of my wireless network
Any idea?
Sorry for my english
Last edited by Crazypu (2007-03-30 08:42:36)
Offline
This is a shot
The network "belkin54g" appear but I cannot connect to
I' ve to choose "Create a new wireless network"
This is my rc.conf:
#
# /etc/rc.conf - Main Configuration for Arch Linux
#
#
# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="it_IT@euro"
HARDWARECLOCK="localtime"
TIMEZONE="Europe/Rome"
KEYMAP=it
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
#
# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# Scan hardware and load required modules at bootup
MOD_AUTOLOAD="yes"
# Module Blacklist - modules in this list will never be loaded by udev
MOD_BLACKLIST=()
#
# Modules to load at boot-up (in this order)
# - prefix a module with a ! to blacklist it
#
MODULES=(8139too mii bcm43xx fglrx)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
#
# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
HOSTNAME="archlappy"
#
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available
# interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
#
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
#
lo="lo 127.0.0.1"
eth0="dhcp"
eth1="dhcp"
wlan_eth1="eth1 essid belkin54g"
WLAN_INTERFACES=(eth1)
INTERFACES=(lo eth0 eth1)
#
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
#
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network-profiles
#
#NET_PROFILES=(template1)
#
# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng !network netfs crond hal alsa dhcdbd networkmanager
gdm)
# End of file
Offline
bcm43xx is ouful. use ndiswrapper instead
Offline
I second that. ndiswrapper > bcm43xx
I am a gated community.
Offline
Ok .... I' ll try ndiswrapper
I' ve just to install it and blacklist the bcm43xx module?
Offline
Yep, you might want to uninstall it as well, I remember my box would connect, but would always on startup wait for two minutes and cough up 'Network...[FAIL]...module bcm43xx not found' or whatever, even though I blacklisted it, so if that happens, uninstall it.
It was funny how six months ago ndiswrapper and broadcom cards were horrible, and everyone wanted the bcm43xx, and now that it is out it sucks, and the ndiswrapper guys managed to get it to work well.
Offline
I second that. ndiswrapper > bcm43xx
false
ndiswrapper!=bcm43xx
bcm43xx is an open source driver
ndiswrapper - wrapper for windows drivers
Offline
Same problem with ndiswrapper too
I' ve installed it, blacklisted bcm43xx, but I' ve the same problem....
I really don't know what to do
Offline
Blame Broadcom, not drivers.
P.S. I use bcm43xx
IRC: Stalwart @ FreeNode
Skype ID: thestalwart
WeeChat-devel nightly packages for i686
Offline
P.S. I use bcm43xx
Can you share your network configuration in rc.conf?
Offline
Stalwart wrote:P.S. I use bcm43xx
Can you share your network configuration in rc.conf?
INTERFACES=(lo)
I connect manually using wpa_supplicant, ifconfig and dhclient. I need to reaload module and ifconfig down/up to make it associate. Pretty buggy, but ndis isn't much better for me - also disconnects all the time
IRC: Stalwart @ FreeNode
Skype ID: thestalwart
WeeChat-devel nightly packages for i686
Offline
hm... ndis with bcm4311 works perfectly =\
2 Crazypu - try manual connect without network-manager
Offline
The problem is that it' s my wife' s lappy..... so she would like everything works like windows
Is there another way to auto-connect without network-manager?
Last edited by Crazypu (2007-03-31 06:30:03)
Offline
The problem is that it' s my wife' s lappy.....
so she would like everything works like windows
Is there another way to auto-connect without network-manager?
I used to patch wpa_supplicant to make it run dhclient on successfull connect, but it didn't work well because i need to perform voodoo dances after each disconnect, otherwise card doesn't associate
Last edited by Stalwart (2007-03-31 08:30:57)
IRC: Stalwart @ FreeNode
Skype ID: thestalwart
WeeChat-devel nightly packages for i686
Offline
Pages: 1