SEARCH

Enter your search query in the box above ^, or use the forum search tool.

You are not logged in.

#1 2011-05-04 09:44:24

Ranko Kohime
Member
From: Cincinnati, Ohio
Registered: 2010-05-17
Posts: 18

Getting network up and running

I've just dusted off a rather old laptop, and I'm running #! on it, but not without some hangups.

This laptop is an IBM Thinkpad 600E, which has no in-built networking aside from a 56K modem.  I have 2 PCMCIA cards, one is a Linksys WPC11 v3 Wireless card, the other a D-Link DFE-690TXD Ethernet card.

When I plug them in, #! does not automatically set them up in the network manager.

lspci -vv reports that the D-Link is recognized, but not the Linksys.

I'm not sure what my next step would be...

Offline

Help fund CrunchBang, donate to the project!

#2 2011-05-04 18:29:36

vredfreak
Member
Registered: 2011-04-24
Posts: 32

Re: Getting network up and running

I don't know anything about the Linksys, but the D-Link card should use one of the "8139" kernel drivers. Might do a "lsmod | grep 8139" and see if one of them is loaded with the D-Link card plugged in.  Taking a quick look in  /lib/modules/2.6.36-2.dmz.5-liquorix-amd64/kernel/drivers/net/ shows two different "8139" drivers: 8139cp and 8139too.  Your module path may be different depending on kernel version.

Might try booting with the D-Link card already in and see if one of those modules gets loaded.


Me:  I talk to myself
Myself:  Yes, I know.
I:  Both of you shut up!

Offline

#3 2011-05-04 18:44:09

Istvan
#! CrunchBanger
From: Budapest, Hungary
Registered: 2010-02-20
Posts: 148

Re: Getting network up and running

For the Linksys device read this please:
http://linuxwireless.org/en/users/Drivers/orinoco


Ha ezt el tudod olvasni, biztosan nem vagy rövidlátó.

Offline

#4 2011-05-05 08:15:43

Ranko Kohime
Member
From: Cincinnati, Ohio
Registered: 2010-05-17
Posts: 18

Re: Getting network up and running

vredfreak wrote:

Might try booting with the D-Link card already in and see if one of those modules gets loaded.

I didn't even think to reboot.  That got it working, and now it's hot-pluggable.  Sometimes the simplest things...  big_smile

Although, booting with the card in did take out my audio for some reason.  roll

Offline

#5 2011-05-05 10:10:39

vredfreak
Member
Registered: 2011-04-24
Posts: 32

Re: Getting network up and running

Ranko Kohime wrote:

Although, booting with the card in did take out my audio for some reason.  roll

Hmmmm, the only thing I can think of is a driver conflict?  Not sure what the problem is here.  Maybe give the relevant output from "lspci -v" about your audio device.


Me:  I talk to myself
Myself:  Yes, I know.
I:  Both of you shut up!

Offline

#6 2011-05-05 15:43:49

joe772
Member
From: 127.0.0.1
Registered: 2011-04-28
Posts: 33

Re: Getting network up and running

Ranko Kohime wrote:
vredfreak wrote:

Might try booting with the D-Link card already in and see if one of those modules gets loaded.

I didn't even think to reboot.  That got it working, and now it's hot-pluggable.  Sometimes the simplest things...  big_smile

Although, booting with the card in did take out my audio for some reason.  roll

My linux professor made a comment about linux reboots once. He wanted us to note that the only time EVER need to reboot, is when something gets modified with the kernel. aside from that, things like changing runlevels, restarting specific services, etc, will give the desired effect.

Offline

#7 2011-05-05 15:54:57

vredfreak
Member
Registered: 2011-04-24
Posts: 32

Re: Getting network up and running

joe772 wrote:

My linux professor made a comment about linux reboots once. He wanted us to note that the only time EVER need to reboot, is when something gets modified with the kernel. aside from that, things like changing runlevels, restarting specific services, etc, will give the desired effect.

Agreed. And in this case a modprobe command would probably have done the trick, but with multiple possible modules, it is sometimes easier to simply reboot and see which module the OS decides is the correct one.  Color me lazy. big_smile


Me:  I talk to myself
Myself:  Yes, I know.
I:  Both of you shut up!

Offline

#8 2011-05-05 16:08:09

joe772
Member
From: 127.0.0.1
Registered: 2011-04-28
Posts: 33

Re: Getting network up and running

vredfreak wrote:
joe772 wrote:

My linux professor made a comment about linux reboots once. He wanted us to note that the only time EVER need to reboot, is when something gets modified with the kernel. aside from that, things like changing runlevels, restarting specific services, etc, will give the desired effect.

Agreed. And in this case a modprobe command would probably have done the trick, but with multiple possible modules, it is sometimes easier to simply reboot and see  which module the OS decides is the correct one.  Color me lazy. big_smile

Haha. I feel ya. smile I'm actually sitting for my RHCSA tomorrow. I wonder if there gonna have it set up where I need to load some kernel mods tongue

Offline

#9 2011-05-05 20:57:34

Ranko Kohime
Member
From: Cincinnati, Ohio
Registered: 2010-05-17
Posts: 18

Re: Getting network up and running

vredfreak wrote:

Hmmmm, the only thing I can think of is a driver conflict?  Not sure what the problem is here.  Maybe give the relevant output from "lspci -v" about your audio device.

00:06.0 Multimedia audio controller: Cirrus Logic CS 4610/11 [CrystalClear SoundFusion Audio Accelerator] (rev 01)
Subsystem: IBM CS4610 SoundFusion Audio Accelerator
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin A routed to IRQ 9
Region 0: Memory at 50100000 (32-bit, non-prefetchable) [size=4K]
Region 1: Memory at 50000000 (32-bit, non-prefetchable) [size=1M]

Latency: 0

dmesg also pukes out a lot of identical lines concerning AC'97 on startup:

[   18.715157] AC'97 read problem (ACCTL_DCV), reg = 0x2

Offline

#10 2011-05-05 21:13:30

vredfreak
Member
Registered: 2011-04-24
Posts: 32

Re: Getting network up and running

I'm afraid the best I can do for you is the following link (which pertains to debian squeeze):

http://wiki.debian.org/snd-cs46xx

Not sure if that will help though, because it sounds as if it was working before you got the ethernet card loaded.  If that doesn't do you any good, I'm afraid you will have to wait for someone with more knowledge than me to come along and give some advice.


Me:  I talk to myself
Myself:  Yes, I know.
I:  Both of you shut up!

Offline

#11 2011-05-06 19:14:48

Ranko Kohime
Member
From: Cincinnati, Ohio
Registered: 2010-05-17
Posts: 18

Re: Getting network up and running

vredfreak wrote:

I'm afraid the best I can do for you is the following link (which pertains to debian squeeze):

http://wiki.debian.org/snd-cs46xx

Not sure if that will help though, because it sounds as if it was working before you got the ethernet card loaded.  If that doesn't do you any good, I'm afraid you will have to wait for someone with more knowledge than me to come along and give some advice.

Couldn't make out much on that page, unfortunately, but thank you for the link.  smile

Offline

Board footer

Powered by FluxBB

Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.

Debian Logo