Damn Small Linux will not connect

Printable View

Show 30 post(s) from this thread on one page

10-15-2008
willgrass

Damn Small Linux will not connect

I am unable to connect Damn Small Linux 4.2.5 to my Bthomehub router. I have tried what I have in the below text but to no avail; maybe I am going the wrong way here.
As I know little of Linux I am getting desperate so for any information I would be grateful.

Beaver Terminal
Lspci
00:00.0 HOST BRIDGE: INTEL CORPORATION 82830 830 CHIPSET HOST (REV 02)
00:01.0 PCI BRIDGE: INTEL CORPORATION 82830 830 CHIPSET AGP BRIDGE (REV 02)
00:1D.0 USB CONTROLLER: INTEL CORPORATION 8201CA/CAM USB CONTROLLER #1 (REV 01)
00:1E.0 PCI BRIDGE: INTEL CORPORATION 82801 MOBILE PCI BRIDGE (REV 41)
00:1F.0 ISA BRIDGE: INTEL CORPORATION 82801CAM ISA BRIDGE (LPC) (REV 01)
00:1F.1 IDE INTERFACE: INTEL CORPORATION 82801CAM IDE U100 CONTROLLER (REV 01)
00:1F.5 MULTIMEDIA AUDIO CONTROLLER: INTEL CORPORATION 82801CA/CAM AC’97 AUDIO
CONTROLLER (REV 01)
00:IF.6 MODEM: INTEL CORPORATION 82801CA/ CAM AC’97 MODEM CONTROLLER (REV 01)
01:00.0 VGA COMPATIBLE CONTROLLER: ATI TECHNOLOGIES INC RADEON MOBILITY M6 LY
02::00.0 ETRHERNET CONRTOLLER: 3COM CORPORATION 3C905C – TX/TX - M (TORNADO) (REV 78)
02:01.0 CARDBUS BRIDGE: TEXAS INSTRUMENTS PCI1420 PC CARD CARDBUS CONTROLLER
02:01.1 CARDBUS BRIDGE: TEXAS INSTRUMENTS PCI1420 PC CARD CARDBUS CONTROLLER
04:00:0 NETWORK CONTROLLER: RALINK RT2500 802.11G CARDBUS/MINI-PCI (REV 01)

prism2 setup

device wlan0 Left as it is
channel 11 Already in the box don’t know if it is correct. Tried 1and 6
sid BThomeHub-7D1C My router model
wep 47:38:db:a8:83 This is my Key Number but not sure about how to do hex maybe I am wrong here.
10-16-2008
weatherkid

Let me get a few thing from you first before I do anything.

Post the output of these commands

Code:

lspci uname -r lsusb

Also list your DSL version and your computer make and model. Info on the card could help too.
10-16-2008
willgrass

Thanks for the reply.

This is information is what I have and I think the card info is there but I will give you what I see on it UDUP 54MBPS /11MBP5
WIRELESS LAN CARD IEEE802. 11B/G MODEL NUMBER GN-WMKG. THE COMUTER IS A DELL LATITUDE.
I got the lspci uname r lsusb information up on the screen but as there is quite a lot I will type it and send it tomorrow as I cant see how it can be copy and paste. the DSL Version is 4.2.5

DNS Suffix Search list :home

Ethernet adapter local area connection

Media state media disconnected
Description 3Com 3c920 Intergrated fast Ethernet
Controller <3C905C-TX Compatible>
Physical addresss 00-06-5B-37-1E-6A

Ethernet adapter wireless network connection

Connection –specific DNS suffix home
Description gigabyte WMKG crardbus WLAN card
Physical address 00-0F-EA-EB-88-DE
Dhcp enabled Yes
Autoconfiguration enabled Yes
IP address 192.168.1.66
Subnet mask 255.255.255.0
Default gateway 192.168.1.254
DHCP server Same
DNS servers Same
Lease obtained 11 Oct. 08 12-27-33
Lease expires 12 Oct 08 12-27-33

I got this from ipconfig /all. In windows

iconfig

wep encryption is on

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:2 ERRORS:0 DROPPED:0 OVERRUNS:0 FRAME:0
TX PACKETS:2 ERRORS:0 DROPPED:0 OVERRUNS:0 CARRIER:0
COLLISIONS:0 TEXQUEUELEN:0
RX BYTES:100 (100.0 B) TX BYTES:100.0 (100.0B)

iconfig -a
etho LINK ENCAP:ETHERNET HWADDR 00:06:5B:37:1E:6A
BROADCAST MULTICAST MTU:1500 METRIC:1
RX PACKETS:0 ERRORS:0 DROPPED:0 OVERRUNS:0 FRAME:0
INTRUPTED:11 BASE ADDRESS:0XEC80
TX PACKETS:6 ERRORS:0 DROPPED:0 OVERRUNS:0 CARRIER:6
COLLISIONS:0 TEXQUEUELEN:1000
RX BYTES:0 (0.0 B) TX BYTES:2052. (2.0 KIB)

Lspci
00:00.0 HOST BRIDGE: INTEL CORPORATION 82830 830 CHIPSET HOST (REV 02)
00:01.0 PCI BRIDGE: INTEL CORPORATION 82830 830 CHIPSET AGP BRIDGE (REV 02)
00:1D.0 USB CONTROLLER: INTEL CORPORATION 8201CA/CAM USB CONTROLLER #1 (REV 01)
00:1E.0 PCI BRIDGE: INTEL CORPORATION 82801 MOBILE PCI BRIDGE (REV 41)
00:1F.0 ISA BRIDGE: INTEL CORPORATION 82801CAM ISA BRIDGE (LPC) (REV 01)
00:1F.1 IDE INTERFACE: INTEL CORPORATION 82801CAM IDE U100 CONTROLLER (REV 01)
00:1F.5 MULTIMEDIA AUDIO CONTROLLER: INTEL CORPORATION 82801CA/CAM AC’97 AUDIO
CONTROLLER (REV 01)
00:IF.6 MODEM: INTEL CORPORATION 82801CA/ CAM AC’97 MODEM CONTROLLER (REV 01)
01:00.0 VGA COMPATIBLE CONTROLLER: ATI TECHNOLOGIES INC RADEON MOBILITY M6 LY
02::00.0 ETRHERNET CONRTOLLER: 3COM CORPORATION 3C905C – TX/TX - M (TORNADO) (REV 78)
02:01.0 CARDBUS BRIDGE: TEXAS INSTRUMENTS PCI1420 PC CARD CARDBUS CONTROLLER
02:01.1 CARDBUS BRIDGE: TEXAS INSTRUMENTS PCI1420 PC CARD CARDBUS CONTROLLER
04:00:0 NETWORK CONTROLLER: RALINK RT2500 802.11G CARDBUS/MINI-PCI (REV 01)
10-16-2008
weatherkid

Did you try NDISWrapper? You will need the Win98 drivers for how old it is.
10-17-2008
willgrass

Damnt Small Linux wont Connect

Thanks again for the reply.

The computer has fake XP Prof, I didn’t know this for some time after I bought some years ago but know it comes up windows is not genuine all the time. I keep it because it has a lot of software I need that will not work without Useport etc and then I have to still play about with it to have it working. Maybe the software will not work with Linux but I have made my mind up that I want Linux. In have not tried NDISWrapper yet and where would I get theWin98 drivers and where would I download it to?

lsusb
Bus: 001 Device 001: ID0000:0000

uname –r
2.4.31

lspci

00:00.0 HOST BRIDGE: INTEL CORPORATION 82830 830 CHIPSET HOST (REV 02)
00:01.0 PCI BRIDGE: INTEL CORPORATION 82830 830 CHIPSET AGP BRIDGE (REV 02)
00:1D.0 USB CONTROLLER: INTEL CORPORATION 8201CA/CAM USB CONTROLLER #1 (REV 01)
00:1E.0 PCI BRIDGE: INTEL CORPORATION 82801 MOBILE PCI BRIDGE (REV 41)
00:1F.0 ISA BRIDGE: INTEL CORPORATION 82801CAM ISA BRIDGE (LPC) (REV 01)
00:1F.1 IDE INTERFACE: INTEL CORPORATION 82801CAM IDE U100 CONTROLLER (REV 01)
00:1F.5 MULTIMEDIA AUDIO CONTROLLER: INTEL CORPORATION 82801CA/CAM AC’97 AUDIO
CONTROLLER (REV 01)
00:IF.6 MODEM: INTEL CORPORATION 82801CA/ CAM AC’97 MODEM CONTROLLER (REV 01)
01:00.0 VGA COMPATIBLE CONTROLLER: ATI TECHNOLOGIES INC RADEON MOBILITY M6 LY
02::00.0 ETRHERNET CONRTOLLER: 3COM CORPORATION 3C905C – TX/TX - M (TORNADO) (REV 78)
02:01.0 CARDBUS BRIDGE: TEXAS INSTRUMENTS PCI1420 PC CARD CARDBUS CONTROLLER
02:01.1 CARDBUS BRIDGE: TEXAS INSTRUMENTS PCI1420 PC CARD CARDBUS CONTROLLER
04:00:0 NETWORK CONTROLLER: RALINK RT2500 802.11G CARDBUS/MINI-PCI (REV 01)
10-17-2008
weatherkid

Is your card made by Gigabyte? If so here is the drivers for it.

GIGABYTE - Support - Communication - Driver

If not I know this is an odd request put put down the US Patent No. In the meantime I'll ask around and see what people think about an different option.
10-18-2008
willgrass

Sorry but I am unable to find anything concerning Gigabyte or anything about US Patent. Would there be a card I could buy that would help me get connected, I you know of any I would gladly buy to get going.
10-18-2008
waterhead

Hi.

If it is the wireless that you are trying to connect, then this would be the wireless card:

Code:

04:00:0 NETWORK CONTROLLER: RALINK RT2500 802.11G CARDBUS/MINI-PCI (REV 01)

There is a driver for it, but it may not work on DSL.

Main Page - Rt2x00Wiki

Your only option is then to use NDISwrapper. I think that the WinXP driver may work, as I found this on the DSL wiki

Quote:

CWP-854 PCI: Works well with the supplied RT2500.INF driver for XP via ndiswrapper

Found it here:
Verified Wireless Cards - DSL Wiki

You need to find a WinXP driver for that wireless.

The other option is to install a full version of linux that uses the modern 2.6.xx kernel. DSL uses the older 2.4.xx kernel, and wireless support wasn't very mature back then.

Edit: Look at the output of this command, it will list driver modules that are loaded.

Code:

lsmod

The rt2x00 or rt2500 module is what I would look for. If you want to copy and post it, there is a way. Copy the output and past it in a text file. I don't know what text editor program DSL has, but any will do. Save the file and add the ".txt" suffix to the end of the file, so that Windows can open the file. Copy it to a USB drive or CD, and then open it in Windows.
10-19-2008
willgrass

Damn Small Linux will not connect

Thank you, I will try the options you have sent the first one first and so on, as I know little of Linux I will no doubt have to make contact again.

Barrie,
10-19-2008
waterhead

I hope that I didn't confuse you with too much information.

If you want to use the wireless in Damn Small Linux, the only option that you have is to use the NDISwrapper method.

I hope that is a bit more clear.

Show 30 post(s) from this thread on one page