realtek r8169 and intel iwl1945, working ok in kubuntu 8.04.1, arch no

luuuciano · 2008-08-05 20:44:39

Hi!

I started writing in this thread http://bbs.archlinux.org/viewtopic.php? … 66#p398766
about that strange issue with the network in a dell vostro notebook...

I can not make it work ok in arch, but I have tried using a kubuntu livecd and the lan and wifi was working ok...

I am not too much techie, so I do not know what to do... I love arch, I use it on my desktop...
So, I want to install it on the notebook...

TIA, and sorry for the bad english

luuuciano · 2008-08-06 02:00:25

something strange is that Network works ok when I use the installation arch cd...
the network do not fail...
then I install it, configure it, reboot......

network fail...

ozar · 2008-08-06 02:35:18

Are you sure your network settings are correct in the /etc/rc.conf file?

luuuciano · 2008-08-06 03:07:21

ozar wrote:

Are you sure your network settings are correct in the /etc/rc.conf file?

here 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"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# 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="es_AR.utf8"
HARDWARECLOCK="localtime"
USEDIRECTISA="no"
TIMEZONE="America/Argentina/Cordoba"
KEYMAP="la-latin1"
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=(r8169 ipw3945 iwl3945 snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore)
# 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="eugenia"
# 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
#
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
INTERFACES=(eth0)
# 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 network netfs crond)

here the mkinitcpio.conf

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES="pata_acpi ata_generic scsi_mod ahci ata_piix"
# BINARIES
# This setting includes, into the CPIO image, and additional
# binaries a given user may wish. This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT overwritten is already added)
# BINARIES are dependancy parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in anyway. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options,
# like so:
# FILES="/etc/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'modload' may be used in place of 'udev', but is not recommended
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
# This setup specifies all modules in the MODULES setting above.
# No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
#
# This setup will autodetect all modules for your system and should
# work as a sane default
# HOOKS="base udev autodetect pata scsi sata filesystems"
#
# This is identical to the above, except the old ide subsystem is
# used for IDE devices instead of the new pata subsystem.
# HOOKS="base udev autodetect ide scsi sata filesystems"
#
# This setup will generate a 'full' image which supports most systems.
# No autodetection is done.
# HOOKS="base udev pata scsi sata usb filesystems"
#
# This setup assembles an pata raid array with an encrypted root FS.
# Note: See 'mkinitcpio -H raid' for more information on raid devices.
# HOOKS="base udev pata raid encrypt filesystems"
#
# This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev usb lvm2 filesystems"
HOOKS="base udev autodetect pata scsi sata usb keymap
filesystems"

luuuciano · 2008-08-06 04:12:26

and then I tried with a fixed ip, configured it in the router and changed the rc.conf to the following...
the bootup error go away, but there is no net... no acces to internet...
I do not know why....

#
# /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"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# 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="es_AR.utf8"
HARDWARECLOCK="localtime"
USEDIRECTISA="no"
TIMEZONE="America/Argentina/Cordoba"
KEYMAP="la-latin1"
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=(r8169 ipw3945 iwl3945 snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore)
# 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="eugenia"
# 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
#
eth0="eth0 192.168.0.34 netmask 255.255.255.0 broadcast 192.168.0.255"
#eth0="dhcp"
INTERFACES=(eth0)
# 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 network netfs crond)

Last edited by luuuciano (2008-08-06 17:42:28)

Top_se · 2008-08-06 16:49:45

Huhu!

Are you trying to setup a wired or a wireless connection?

Can you please run:
$ ifconfig -a
and tell us what the output is?

If there is no eth0 listed it`s likely to be a driver-issue ... Did you take special care to install drivers for your network-card(s) while installing arch?

Which error-msg did go away after using a static-ip?

Sorry if you posted these infos already in the other thread, but it`s very confusing to post the same problem in 2 threads ...

Top_se

luuuciano · 2008-08-06 17:17:37

Top_se wrote:

Huhu!
Are you trying to setup a wired or a wireless connection?
Can you please run:
$ ifconfig -a
and tell us what the output is?
If there is no eth0 listed it`s likely to be a driver-issue ... Did you take special care to install drivers for your network-card(s) while installing arch?
Which error-msg did go away after using a static-ip?
Sorry if you posted these infos already in the other thread, but it`s very confusing to post the same problem in 2 threads ...
Top_se

yep, sorry... I have started this one because I thought that I was hijacking the other one
in that thread the problem was solved, but that solution did not work in my case...

my idea was to make wired work, and then make wireless work...

my ifconfig show this:

eth0 Link encap:Ethernet HWaddr 00:21:70:9B:F2:F5
inet addr:192.168.0.34 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:4294967293 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 Base address:0x8000
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: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)

all the modules are installed and running... r8169 iwl3945, the firmware is installed too (I have installed all the base packages)

when I was trying with dhcp the error at startup was:

err, eth0: timed out
warn, eth0: usingIPV4LL address 169.254.154.155

and dmesg showed:

netdev watchdog transmit timed out

then, I tried the static ip thing, and there is not error at startup... but something is wrong...

btw, I did a iwconfig, and it shows this:

lo no wireless extensions.
eth0 no wireless extensions.

so, wifi is not working neither?

I do not know why is working in the kubuntu livecd and not in arch... I love arch, I use it in my desktop... do not want to end using ubuntu on the notebook

peart · 2008-08-06 17:36:06

luuuciano,

You have both ipw3945 and iwl3945 in your MODULES array. The two drivers conflict with each other, leaving you with no wireless. Use only one of the two. I suggest removing all traces of ipw3945 from your system. Also, make sure you have iwlwifi-3945-ucode installed.

Last edited by peart (2008-08-06 17:40:24)

luuuciano · 2008-08-06 18:03:31

weeeeeeeee, peart!
at least I have wifi now!

lets configure it...

luuuciano · 2008-08-06 23:14:29

well, the eth0 continue having errors... but I have wireless at least....

anyway, I have setup statics IP, not dhcp...
and when I do "netcfg2 wpa" it shows a message: Adding gateway 192.168.0.1 failed...
this is the rc.conf http://pastebin.com/d3487d05e
and this the wpa file http://pastebin.com/d7cfc8f01

any idea?

Last edited by luuuciano (2008-08-06 23:49:47)

smartcat99s · 2008-08-07 01:00:07

On my g1s, I just let netcfg2 take care of both the wired and wireless. (I set NETWORKS_EXCLUSIVE="yes" so it would only have wired or wireless)

I think that the static route of the wired is interfering with the wifi gateway, so I'd try removing everything related to eth0/routes from /etc/rc.conf and just use netcfg2 profiles everywhere.

Arch Linux

#1 2008-08-05 20:44:39

realtek r8169 and intel iwl1945, working ok in kubuntu 8.04.1, arch no

#2 2008-08-06 02:00:25

Re: realtek r8169 and intel iwl1945, working ok in kubuntu 8.04.1, arch no

#3 2008-08-06 02:35:18

Re: realtek r8169 and intel iwl1945, working ok in kubuntu 8.04.1, arch no

#4 2008-08-06 03:07:21

Re: realtek r8169 and intel iwl1945, working ok in kubuntu 8.04.1, arch no

#5 2008-08-06 04:12:26

Re: realtek r8169 and intel iwl1945, working ok in kubuntu 8.04.1, arch no

#6 2008-08-06 16:49:45

Re: realtek r8169 and intel iwl1945, working ok in kubuntu 8.04.1, arch no

#7 2008-08-06 17:17:37

Re: realtek r8169 and intel iwl1945, working ok in kubuntu 8.04.1, arch no

#8 2008-08-06 17:36:06

Re: realtek r8169 and intel iwl1945, working ok in kubuntu 8.04.1, arch no

#9 2008-08-06 18:03:31

Re: realtek r8169 and intel iwl1945, working ok in kubuntu 8.04.1, arch no

#10 2008-08-06 23:14:29

Re: realtek r8169 and intel iwl1945, working ok in kubuntu 8.04.1, arch no

#11 2008-08-07 01:00:07

Re: realtek r8169 and intel iwl1945, working ok in kubuntu 8.04.1, arch no

Board footer