Installation woes (networking and clock)

shadogamon · 2011-06-19 18:44:37

After a near perfect installation and getting wicd working I tried loading up the broadcom-wl driver. Immedietly after loading none of the networking is working.
these are my network controllers

09:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8040 PCI-E Fast Ethernet Controller (rev 13)
0c:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)

and 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", any other value will result
#   in the hardware clock being left untouched (useful for virtualization)
# 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="en_US.UTF-8"
HARDWARECLOCK="UTC"
TIMEZONE="America/New_York"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
#
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
#
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(wl)

# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="Archtop"

# 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
# 
# DHCP:     Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#

#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
INTERFACES=(!eth0 !wlan0)

# 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.d
#
# This now requires the netcfg package
#
#NETWORKS=(main)

# -----------------------------------------------------------------------
# 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 dbus hal !network wicd netfs crond alsa kdm)

is anything amiss?

If further information is needed please point me to it.

karol · 2011-06-19 19:04:41

eth0="dhcp"
INTERFACES=(!eth0 !wlan0)

I'm not sure if it makes sense.

What exactly isn't working: are the modules loaded, can you load them manually, can you ping stuff?

Edit: Oh wait, are you saying you're running an up to date system and managing your network with wicd? Because your rc.conf uses still the old settings.

Last edited by karol (2011-06-19 19:07:59)

tomk · 2011-06-19 19:08:43

Also, not directly related, but your rc.conf is out of date - read the news, have a look at rc.conf.pacnew and make any necessary changes.

karol · 2011-06-19 19:15:12

The title says you have some problems with the clock - what are they?

shadogamon · 2011-06-19 19:30:42

karol wrote:

eth0="dhcp"
INTERFACES=(!eth0 !wlan0)
I'm not sure if it makes sense.
What exactly isn't working: are the modules loaded, can you load them manually, can you ping stuff?
Edit: Oh wait, are you saying you're running an up to date system and managing your network with wicd? Because your rc.conf uses still the old settings.

Yeah I believe the modules are loaded I get nothing in terms of connection. loading them manually works, but the card is not recognised

tomk wrote:

Also, not directly related, but your rc.conf is out of date - read the news, have a look at rc.conf.pacnew and make any necessary changes.

I'll try that that and get back to you.

karol wrote:

The title says you have some problems with the clock - what are they?

It refuses to be corrected (to time-zone there is an 8 hour discrepancy) and I cant set to NTP cause of networking problems

Last edited by shadogamon (2011-06-19 19:32:14)

karol · 2011-06-19 19:37:22

https://wiki.archlinux.org/index.php/Br … ot_show_up

As for the clock, please post the output of

date
hwclock --debug

Last edited by karol (2011-06-19 19:41:17)

shadogamon · 2011-06-20 03:06:14

hwclock from util-linux 2.19.1
Using /dev interface to clock.
Last drift adjustment done at 1308400413 seconds after 1969
Last calibration done at 1308400413 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2011/06/19 22:47:58
Hw clock time : 2011/06/19 22:47:58 = 1308523678 seconds since 1969
Sun 19 Jun 2011 06:47:58 PM EDT  -0.871148 seconds

that seems correct. must be a KDE problem...

updated 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", any other value will result
#   in the hardware clock being left untouched (useful for virtualization)
# 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="en_US.UTF-8"
HARDWARECLOCK="UTC"
TIMEZONE="America/New_York"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
#
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
#
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(wl)

# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="Archtop"

# Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
#
# Wired network setup
#   - interface: name of device (required)
#   - address: IP address (leave blank for DHCP)
#   - netmask: subnet mask (ignored for DHCP)
#   - gateway: default route (ignored for DHCP)
# 
# Static IP example
# interface=eth0
# address=192.168.0.2
# netmask=255.255.255.0
# gateway=192.168.0.1
#
# DHCP example
# interface=eth0
# address=
# netmask=
# gateway=

interface=eth0
address=
netmask=
gateway=

# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"

# Enable these netcfg profiles at boot-up. These are useful if you happen to
# need more advanced network features than the simple network service
# supports, such as 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.d
#
# This requires the netcfg package
#
#NETWORKS=(main)

# -----------------------------------------------------------------------
# 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=(hwclock syslog-ng dbus hal !network wicd netfs crond alsa kdm)

Is this ok now?

admiralspark · 2011-06-20 04:23:53

When using the broadcom WL driver, you need to blacklist the brcm80211 driver or it will continue to load first. 'lsmod | grep brcm' to check for it. Also, blacklisting b43 and ssb helps me.
To do it in the new setup, follow the instructions as per here, adding

blacklist brcm80211
blacklist b43
blacklist ssb

to /etc/modprobe.d/modprobe.conf

karol · 2011-06-20 09:38:15

admiralspark wrote:

When using the broadcom WL driver, you need to blacklist the brcm80211 driver or it will continue to load first. 'lsmod | grep brcm' to check for it. Also, blacklisting b43 and ssb helps me.
To do it in the new setup, follow the instructions as per here, adding
blacklist brcm80211
blacklist b43
blacklist ssb
to /etc/modprobe.d/modprobe.conf

[OT=slightly]
I already told OP to check https://wiki.archlinux.org/index.php/Br … ot_show_up but this part of the wiki is still using rc.conf for blacklisting. If you know which modules need to be blacklisted, could you please update it?
[/OT]

admiralspark · 2011-06-21 03:25:31

[OT] I'd be glad to! [/OT]

OP, did you ever get this resolved? I still wouldn't use NTP even after networking is set up correctly, you can set the system clock just fine and use UTC (unless you dual-boot, which would be the cause of the original problem)

Arch Linux

#1 2011-06-19 18:44:37

Installation woes (networking and clock)

#2 2011-06-19 19:04:41

Re: Installation woes (networking and clock)

#3 2011-06-19 19:08:43

Re: Installation woes (networking and clock)

#4 2011-06-19 19:15:12

Re: Installation woes (networking and clock)

#5 2011-06-19 19:30:42

Re: Installation woes (networking and clock)

#6 2011-06-19 19:37:22

Re: Installation woes (networking and clock)

#7 2011-06-20 03:06:14

Re: Installation woes (networking and clock)

#8 2011-06-20 04:23:53

Re: Installation woes (networking and clock)

#9 2011-06-20 09:38:15

Re: Installation woes (networking and clock)

#10 2011-06-21 03:25:31

Re: Installation woes (networking and clock)

Board footer