Skip navigation.
Home
MEPIS
Now Shipping Version 8.0
Home » MEPIS Forums » SUPPORT » Install MEPIS

No Sound or wireless for me with Mepis 6.0-4(64)

Submitted by SteveDean on Mon, 01/29/2007 - 02:25

I Started using Mepis on 01/01/06. I love it! I now have a Gateway laptop MX6453 install worked fine, but No sound or Wireless. I have tried everything I could find. I am not a code talker. I have seen some real complicated "fixes" that did nothing other than breaking other stuff. I just moved from 6.0 to 6.0-4(64) because I read that the wireless issues were fixed; well... not mine. [sigh] Any ideas?
- Steve Dean

‹ 6.5 beta 5 - if I install this, will synaptic get me to 6.5 release, buy updating via synaptic? Best way to do it ›
»

it would help if you could

Submitted by carlops on Mon, 01/29/2007 - 03:46.

it would help if you could supply us with a list of hardware. Use the command lspci in console and post the output.

Newbie or not Newbie, there's always a question

»

lspci on my Gateway MX6453

Submitted by SteveDean on Tue, 01/30/2007 - 17:07.

This is the lspci on my Gateway MX6453.

0000:00:00.0 Host bridge: ATI Technologies Inc RS480 Host Bridge (rev 10)
0000:00:01.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge
0000:00:04.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge
0000:00:05.0 PCI bridge: ATI Technologies Inc: Unknown device 5a37
0000:00:13.0 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller (rev 80)
0000:00:13.1 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller (rev 80)
0000:00:13.2 USB Controller: ATI Technologies Inc IXP SB400 USB2 Host Controller (rev 80)
0000:00:14.0 SMBus: ATI Technologies Inc IXP SB400 SMBus Controller (rev 83)
0000:00:14.1 IDE interface: ATI Technologies Inc Standard Dual Channel PCI IDE Controller ATI (rev 80)
0000:00:14.2 Audio device: ATI Technologies Inc SB450 HDA Audio (rev 01)
0000:00:14.3 ISA bridge: ATI Technologies Inc IXP SB400 PCI-ISA Bridge (rev 80)
0000:00:14.4 PCI bridge: ATI Technologies Inc IXP SB400 PCI-PCI Bridge (rev 80)
0000:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
0000:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
0000:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
0000:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
0000:01:05.0 VGA compatible controller: ATI Technologies Inc RS482 [Radeon Xpress 200M]
0000:02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8038 PCI-E Fast Ethernet Controller (rev 14)
0000:05:00.0 Network controller: Broadcom Corporation Dell Wireless 1390 WLAN Mini-PCI Card (rev 01)
0000:08:09.0 CardBus bridge: Texas Instruments PCIxx12 Cardbus Controller
0000:08:09.1 FireWire (IEEE 1394): Texas Instruments PCIxx12 OHCI Compliant IEEE 1394 Host Controller
0000:08:09.2 Mass storage controller: Texas Instruments 5-in-1 Multimedia Card Reader (SD/MMC/MS/MS PRO/xD)

»

Let's start with wireless.

Submitted by carlops on Tue, 01/30/2007 - 17:46.

Let's start with wireless. It looks to be a broadcom chipset, renowned for their trouble causing capabilities...

Look here http://www.mepis.org/docs/en/index.php/Any_card_using_the_Broadcom_43xx_chipset

If you can't work your way through, someone here can surely help you along. I do not have a broadcom, so I don't know the exact details...

Once wireless works, continue with the sound...

Newbie or not Newbie, there's always a question

»

Ok I just put a few hours into this... [sigh]

Submitted by SteveDean on Wed, 01/31/2007 - 00:10.

Ok I started with the wifi and well the only install disk that came with my Gateway is a single reinstall for the whole Op-Sys. The only file I can get from Gateway download is a .exe file. So I used WinRar to open it and get a .ini file. No good. How do I get the correct .ini file?

This is what is installed when I use "ndiswrapper -i"

bcmwl5 driver present
lsbcmnds driver present
lstinds driver present
mrv8knt driver present
wlipnds driver present

I don't want to break my lan or I cant talk to you. Smiling So, what can I safely remove?
Thanks,
-Steve

»

See if you can get the

Submitted by carlops on Wed, 01/31/2007 - 03:23.

See if you can get the driver here: http://support.gateway.com/support/drivers/dlcenter.asp

EDIT:
According to a google search, the driver can be downloaded from dell here

Newbie or not Newbie, there's always a question

»

Driver

Submitted by SteveDean on Wed, 01/31/2007 - 11:26.

Well this is what I have now.

Installed ndis drivers:
bcmwls.ini invalid driver!
lsbcmnds driver present
lstinds driver present
mrv8knt driver present
wlipnds driver present

Note the "invalid driver!" Grrrrr.....

»

did you blacklist the

Submitted by carlops on Wed, 01/31/2007 - 11:52.

did you blacklist the module??

Newbie or not Newbie, there's always a question

»

this is my blacklist file

Submitted by SteveDean on Wed, 01/31/2007 - 20:59.

The following is my blacklist file. Note the last entry. Did I do it correct? BTW the link you sent me to was the only one that explained how to blacklist. Many instructions say to do it, but not how to. While this exercise has been frustrating at times, I have to admit that I am learning a lot. I am realizing something that should have been obvious. 20 years of working through windows issues has made me very comfortable with it. While flawless would be nice, I am finding that working through my few issues during my year with Linux/Mepis has made me a much better user. And this issue is no exception, but my moral would have been broken without your kind help. Thank you so much for helping me.

# This file lists those modules which we don't want to be loaded by
# alias expansion, usually so some other driver will be loaded for the
# device instead.

# evbug is a debug tool that should be loaded explicitly
blacklist evbug

# these drivers are very simple, the HID drivers are usually preferred
blacklist usbmouse
blacklist usbkbd

# replaced by e100
blacklist eepro100

# replaced by tulip
blacklist de4x5

# causes no end of confusion by creating unexpected network interfaces
blacklist eth1394

# snd_intel8x0m can interfere with snd_intel8x0, doesn't seem to support much
# hardware on its own (Ubuntu bug #2011, #6810)
blacklist snd_intel8x0m

# causes failure to suspend on HP compaq nc6000 (Ubuntu: #10306)
blacklist i2c_i801

blacklist snd_hda_intel

# Interferes with wlan0
blacklist bcm43xx

»

Broadcom 64-bit

Submitted by mdmarmer on Wed, 01/31/2007 - 22:22.

OK you have 1390 rev 01

It appears to be Broadcom 4311 chipset, pciid: 14e4:4311 (rev 01, subsys 1028:0007)

I think you can check this in lspci -vv
(that's 2 vees)

You need a 64-bit driver

The driver is usually called bcmwl5.inf or bcmwl5a.inf
It appears you have tried to install bcmwls.ini into ndiswrapper which is not a driver file at all.

The .sys (usually bcmwl564.sys) needs to be in the same folder with the driver when you run the command

ndiwrapper -i filename.inf

filename.sys is the firmware. You need both.

A valid response to ndiswrapper -l is
driver present, hardware present
or similar

If you can find a 64-bit Gateway driver you may use that.

Try this driver (I hope it's 64-bit) It may be simplest to unpack in Windows as it's .exe
http://ftp.us.dell.com/network/R140747.EXE

You can also unpack it this way in Linux
unzip -a R140747.EXE

If you install a correct 32-bit driver in a 64-bit environment, ndiswrapper won't know the difference -- but it won't work.

I would also get the latest BIOS update from the Gateway site and update the BIOS

Mike

Use the wiki http://www.mepis.org/docs
great forum http://www.mepislovers.com

»

Hey! One step closser!

Submitted by SteveDean on Thu, 02/01/2007 - 01:18.

I got it to install!!! The driver came from Gateway and I believe runs 64 bit. This is my set up now.

root@3[etc]# ndiswrapper -l
Installed ndis drivers:
bcmwl5 driver present, hardware present
lsbcmnds driver present
lstinds driver present
mrv8knt driver present
wlipnds driver present

OK, step closer, but still will not find the hardware. Should I take out some of the drivers? Remember I need to keep the lan stuff to talk to you.

Here is my "lspci -vv"
0000:00:00.0 Host bridge: ATI Technologies Inc RS480 Host Bridge (rev 10)
Subsystem: Gateway 2000: Unknown device 0367
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Latency: 64

0000:00:01.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Latency: 64
Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
I/O behind bridge: 00009000-00009fff
Memory behind bridge: c0100000-c01fffff
Prefetchable memory behind bridge: 00000000c8000000-00000000cff00000
BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B-
Capabilities: [44] #08 [a803]
Capabilities: [b0] #0d [0000]

0000:00:04.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Latency: 0, Cache Line Size: 0x08 (32 bytes)
Bus: primary=00, secondary=02, subordinate=04, sec-latency=0
I/O behind bridge: 0000a000-0000afff
Memory behind bridge: c0200000-c02fffff
BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] #10 [0141]
Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/0 Enable+
Address: fee00000 Data: 40c9
Capabilities: [b0] #0d [0000]
Capabilities: [b8] #08 [a803]

0000:00:05.0 PCI bridge: ATI Technologies Inc: Unknown device 5a37 (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Latency: 0, Cache Line Size: 0x08 (32 bytes)
Bus: primary=00, secondary=05, subordinate=07, sec-latency=0
Memory behind bridge: c0300000-c03fffff
BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] #10 [0141]
Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/0 Enable+
Address: fee00000 Data: 40d1
Capabilities: [b0] #0d [0000]
Capabilities: [b8] #08 [a803]

0000:00:13.0 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller (rev 80) (prog-if 10 [OHCI])
Subsystem: Gateway 2000: Unknown device 0367
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Latency: 64, Cache Line Size: 0x10 (64 bytes)
Interrupt: pin A routed to IRQ 225
Region 0: Memory at c0004000 (32-bit, non-prefetchable) [=4K]
Capabilities: [d0] Message Signalled Interrupts: 64bit- Queue=0/0 Enable-
Address: 00000000 Data: 0000

0000:00:13.1 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller (rev 80) (prog-if 10 [OHCI])
Subsystem: Gateway 2000: Unknown device 0367
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Latency: 64, Cache Line Size: 0x10 (64 bytes)
Interrupt: pin A routed to IRQ 225
Region 0: Memory at c0005000 (32-bit, non-prefetchable) [=4K]
Capabilities: [d0] Message Signalled Interrupts: 64bit- Queue=0/0 Enable-
Address: 00000000 Data: 0000

0000:00:13.2 USB Controller: ATI Technologies Inc IXP SB400 USB2 Host Controller (rev 80) (prog-if 20 [EHCI])
Subsystem: Gateway 2000: Unknown device 0367
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Latency: 64, Cache Line Size: 0x10 (64 bytes)
Interrupt: pin A routed to IRQ 225
Region 0: Memory at c0006000 (32-bit, non-prefetchable) [=4K]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Bridge: PM- B3+
Capabilities: [d0] Message Signalled Interrupts: 64bit- Queue=0/0 Enable-
Address: 00000000 Data: 0000

0000:00:14.0 SMBus: ATI Technologies Inc IXP SB400 SMBus Controller (rev 83)
Subsystem: Gateway 2000: Unknown device 0367
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Region 0: I/O ports at 8400 [=16]
Region 1: Memory at fed00000 (32-bit, non-prefetchable) [=1K]
Capabilities: [b0] #08 [a802]

0000:00:14.1 IDE interface: ATI Technologies Inc Standard Dual Channel PCI IDE Controller ATI (rev 80) (prog-if 82 [Master PriP])
Subsystem: Gateway 2000: Unknown device 0367
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Latency: 0
Interrupt: pin A routed to IRQ 217
Region 0: I/O ports at
Region 1: I/O ports at
Region 2: I/O ports at
Region 3: I/O ports at
Region 4: I/O ports at 8410 [=16]
Capabilities: [70] Message Signalled Interrupts: 64bit- Queue=0/0 Enable-
Address: 00000000 Data: 0000

0000:00:14.2 Audio device: ATI Technologies Inc SB450 HDA Audio (rev 01)
Subsystem: ATI Technologies Inc SB450 HDA Audio
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- SERR- Latency: 64, Cache Line Size: 0x08 (32 bytes)
Interrupt: pin A routed to IRQ 10
Region 0: Memory at c0000000 (64-bit, non-prefetchable) [=16K]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [60] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000

0000:00:14.3 ISA bridge: ATI Technologies Inc IXP SB400 PCI-ISA Bridge (rev 80)
Subsystem: Gateway 2000: Unknown device 0367
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Latency: 0

0000:00:14.4 PCI bridge: ATI Technologies Inc IXP SB400 PCI-PCI Bridge (rev 80) (prog-if 01 [Subtractive decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Latency: 64
Bus: primary=00, secondary=08, subordinate=0c, sec-latency=64
I/O behind bridge: 00002000-00002fff
Memory behind bridge: c0400000-c04fffff
Prefetchable memory behind bridge: 88000000-89ffffff
BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-

0000:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [80] #08 [2101]

0000:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-

0000:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-

0000:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [f0] #0f [0010]

0000:01:05.0 VGA compatible controller: ATI Technologies Inc RS482 [Radeon Xpress 200M] (prog-if 00 [VGA])
Subsystem: Gateway 2000: Unknown device 0367
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Latency: 255 (2000ns min), Cache Line Size: 0x08 (32 bytes)
Interrupt: pin A routed to IRQ 50
Region 0: Memory at c8000000 (32-bit, prefetchable) [=128M]
Region 1: I/O ports at 9000 [=256]
Region 2: Memory at c0100000 (32-bit, non-prefetchable) [=64K]
Expansion ROM at c0120000 [disabled] [=128K]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8038 PCI-E Fast Ethernet Controller (rev 14)
Subsystem: Gateway 2000: Unknown device 0367
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Latency: 0, Cache Line Size: 0x08 (32 bytes)
Interrupt: pin A routed to IRQ 233
Region 0: Memory at c0200000 (64-bit, non-prefetchable) [=16K]
Region 2: I/O ports at a000 [=256]
Capabilities: [48] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [50] Vital Product Data
Capabilities: [5c] Message Signalled Interrupts: 64bit+ Queue=0/1 Enable+
Address: 00000000fee00000 Data: 40e9
Capabilities: [e0] #10 [0011]

0000:05:00.0 Network controller: Broadcom Corporation Dell Wireless 1390 WLAN Mini-PCI Card (rev 01)
Subsystem: Broadcom Corporation: Unknown device 0465
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Latency: 0, Cache Line Size: 0x08 (32 bytes)
Interrupt: pin A routed to IRQ 11
Region 0: Memory at c0300000 (32-bit, non-prefetchable) [=16K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=2 PME-
Capabilities: [58] Message Signalled Interrupts: 64bit- Queue=0/0 Enable-
Address: 00000000 Data: 0000
Capabilities: [d0] #10 [0011]

0000:08:09.0 CardBus bridge: Texas Instruments PCIxx12 Cardbus Controller
Subsystem: Gateway 2000: Unknown device 0367
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Latency: 168, Cache Line Size: 0x20 (128 bytes)
Interrupt: pin A routed to IRQ 185
Region 0: Memory at c0404000 (32-bit, non-prefetchable) [=4K]
Bus: primary=08, secondary=09, subordinate=0c, sec-latency=176
Memory window 0: 88000000-89fff000 (prefetchable)
Memory window 1: 8a000000-8bfff000
I/O window 0: 00002000-000020ff
I/O window 1: 00002400-000024ff
BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt+ PostWrite+
16-bit legacy interface ports at 0001

0000:08:09.1 FireWire (IEEE 1394): Texas Instruments PCIxx12 OHCI Compliant IEEE 1394 Host Controller (prog-if 10 [OHCI])
Subsystem: Gateway 2000: Unknown device 0367
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Latency: 64 (750ns min, 1000ns max), Cache Line Size: 0x08 (32 bytes)
Interrupt: pin B routed to IRQ 177
Region 0: Memory at c0405000 (32-bit, non-prefetchable) [=2K]
Region 1: Memory at c0400000 (32-bit, non-prefetchable) [=16K]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME+

0000:08:09.2 Mass storage controller: Texas Instruments 5-in-1 Multimedia Card Reader (SD/MMC/MS/MS PRO/xD)
Subsystem: Gateway 2000: Unknown device 0367
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Latency: 64 (1750ns min, 1000ns max), Cache Line Size: 0x08 (32 bytes)
Interrupt: pin A routed to IRQ 11
Region 0: Memory at c0406000 (32-bit, non-prefetchable) [=4K]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

»

OK, now try to get it working with mutilities

Submitted by mdmarmer on Thu, 02/01/2007 - 20:47.

OK, now try to get it working with mutilities

http://www.mepis.org/docs/en/index.php/Mepis_Utilities

Should have mentioned that step last night.

Configure wlan0 and Wireless

Click Start at Boot, Apply and OK at each tab.

Turn off encryption first, get it working,then add encryption later

If you have problems your driver may not be a 64-bit driver.

Mike

»

Tried that. [sigh]

Submitted by SteveDean on Fri, 02/02/2007 - 19:58.

I tried that.

Wireless interfaces:

Wifi0
Status: Does not exist

wlan0
Status: Does not exist

Sorry, I must be missing something. And of course the utilities are different in the new version of Mepis, so most of the documentation is not as use full as it would be if they had left the interface the same.

»

Did you try command line?

Submitted by mdmarmer on Fri, 02/02/2007 - 21:40.

Sometimes it helps to type in a root konsole
ndiswrapper -m
and reboot

Try this:

modprobe ndiswrapper
iwconfig
iwconfig wlan0 essid YOURESSID channel YOURCHANNEL#
dhclient wlan0

http://www.mepis.org/docs/en/index.php/Command_line_utilities

Mike

»

That didn't work eather

Submitted by SteveDean on Mon, 02/05/2007 - 06:46.

The problem is that my computer will not recognize the wireless exists at all in Mepis. As you can see in the discussion above I have loaded the driver. Arrrrggggg..... I have to be missing something really simple and stupid.

Here is what I did. Thanks for all the help.

root@1[etc]# modprobe ndiswrapper
root@1[etc]# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

sit0 no wireless extensions.

root@1[etc]# iwconfig wlan0 essid Dean channel 11
Error for wireless request "Set ESSID" (8B1A) :
SET failed on device wlan0 ; No such device.
root@1[etc]# dhclient wlan0
Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

SIOCSIFADDR: No such device
wlan0: ERROR while getting interface flags: No such device
wlan0: ERROR while getting interface flags: No such device
Bind socket to interface: No such device

»

Did you do the ndiswrapper -m step?

Submitted by JimCockfield on Mon, 02/05/2007 - 09:15.

I didn't notice you saying you did the ndiswrapper -m step mentioned.

Try it first so that it creates what modprobe needs. You may need to remove ndiswrapper first so that it installs with the correct configuration If it locks up on you, reboot and try again.

su
modprobe -r ndiswrapper
ndiswrapper -m
modprobe ndiswrapper

Then, see if your wireless shows up:

iwconfig

If so, you can configure it.

Jim C.

»

64-bit driver?

Submitted by mdmarmer on Mon, 02/05/2007 - 19:38.

I suspect your driver is 32-bit

Try the Dell driver I suggested early on

Try this driver (I hope it's 64-bit) It may be simplest to unpack in Windows as it's .exe
http://ftp.us.dell.com/network/R140747.EXE

You can also unpack it this way in Linux
unzip -a R140747.EXE

Mike

»

Here is what happened

Submitted by SteveDean on Wed, 02/07/2007 - 01:11.

Here is what happened.

root@1[steve]# modprobe -r ndiswrapper
root@1[steve]# ndiswrapper -m
modprobe config already contains alias directive

root@1[steve]# modprobe ndiswrapper
root@1[steve]# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

sit0 no wireless extensions.

I am downloading the Dell driver now.

»

Still no go

Submitted by SteveDean on Thu, 02/15/2007 - 01:15.

Well I gave up and just tried 6.5. That was a disaster. Now back to this version. Perhaps we could get the sound working since the wifi doesn't like me. Sad
- Steve

»

Why not try the 32 bits

Submitted by carlops on Thu, 02/15/2007 - 04:10.

Why not try the 32 bits version? It may well be that the issues you are having are 64 bit related....

Newbie or not Newbie, there's always a question

»

32 bit tried

Submitted by SteveDean on Thu, 02/15/2007 - 12:35.

I tried 6.5 32, 6.5 64 and they just didn't work. Tried 6.0-4 64 with the results posted in this string. Tried 6.0-4 32 and seemed to get the same results as the 64. I have now gone back to 6.0-i386, but no wifi. [sigh] I had sound when I first put 6.0-i386 on this a few months ago, before 6.0-4. So I should be able to get it back some how. It does at least say it recognises my sound card. Wifi was no go on any of them.

One thing this has shown me is that with the seperate partitions that Mepis uses we can just install and reinstall at will with out loosing anything. Try that with a windows install. Each install took 10 to 15 min and only about 5 min of my attention. It was easy and all issues from the not so stable 6.5 dissapeared with a fresh 6.0. I can't imagine trying to reinstall an older vertion of windows, to get a comp back to a working state, while keeping everything. In the past when people posted "why not try installing ____" I could think of one big reason not to, my experance with windows installs! While still with the 'no wifi issue' I now know how much safer my data is from system breaks on linux than windows.

Any ideas about my sound?
- Steve

»

not really....

Submitted by carlops on Thu, 02/15/2007 - 15:03.

SteveDean wrote:

Any ideas about my sound?
- Steve

Assuming you tried every trick in the wiki.... nope... sorry. If you haven't, that would be the place to start,

Newbie or not Newbie, there's always a question

»

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.