Connecting problems: Dell Wireless 1397 (MUCH INFO)

My wireless device is an integrated Dell Wireless 1397 WLAN Mini-Card, I am unsure about the driver I have in use. I am sure I have a driver installed because the configuration screen shows my network. I currently have the computer plugged into my network via CAT 5 but I would like to be able to use the wireless (obviously.) I am using Open SuSE version 11.2 and I have run the updater. I could not see my wireless network before running the updater and I can now so I know that the updates have helped but I am again stuck. I have tried to search the wireless forum and I have tried to tinker with the settings in YaST , but nothing seems to be working. Reading the Welcome page of the wireless forum, I tried the Broadcom chip-set advice:

**bob@linux-t9h2:~/Desktop> sudo /usr/sbin/install_bcm43xx_firmware

We trust you (…)
root’s password:

Downloading b43 firmware

######################################################################## 100.0%

Extracting b43 firmware

This file is recognised as:

ID : FW13

filename : wl_apsta_mimo.o

version : 410.2160

MD5 : cb8d70972b885b1f8883b943c0261a3c

Extracting b43/pcm5.fw

Extracting b43/ucode15.fw

Extracting b43/ucode14.fw

Extracting b43/ucode13.fw

Extracting b43/ucode11.fw

Extracting b43/ucode9.fw

Extracting b43/ucode5.fw

Extracting b43/lp0bsinitvals15.fw

Extracting b43/lp0initvals15.fw

Extracting b43/lp0bsinitvals14.fw

Extracting b43/lp0initvals14.fw

Extracting b43/a0g1bsinitvals13.fw

Extracting b43/a0g1initvals13.fw

Extracting b43/b0g0bsinitvals13.fw

Extracting b43/b0g0initvals13.fw

Extracting b43/lp0bsinitvals13.fw

Extracting b43/lp0initvals13.fw

Extracting b43/n0absinitvals11.fw

Extracting b43/n0bsinitvals11.fw

Extracting b43/n0initvals11.fw

Extracting b43/a0g1bsinitvals9.fw

Extracting b43/a0g0bsinitvals9.fw

Extracting b43/a0g1initvals9.fw

Extracting b43/a0g0initvals9.fw

Extracting b43/b0g0bsinitvals9.fw

Extracting b43/b0g0initvals9.fw

Extracting b43/a0g1bsinitvals5.fw

Extracting b43/a0g0bsinitvals5.fw

Extracting b43/a0g1initvals5.fw

Extracting b43/a0g0initvals5.fw

Extracting b43/b0g0bsinitvals5.fw

Extracting b43/b0g0initvals5.fw

Downloading b43legacy firmware

######################################################################## 100.0%

Extracting b43legacy firmware

This file is recognised as:

ID : FW10

filename : wl_apsta.o

version : 295.14

MD5 : e08665c5c5b66beb9c3b2dd54aa80cb3

Extracting b43legacy/ucode2.fw

Extracting b43legacy/ucode4.fw

Extracting b43legacy/ucode5.fw

Extracting b43legacy/ucode11.fw

Extracting b43legacy/pcm4.fw

Extracting b43legacy/pcm5.fw

Extracting b43legacy/a0g0bsinitvals2.fw

Extracting b43legacy/b0g0bsinitvals5.fw

Extracting b43legacy/a0g0initvals5.fw

Extracting b43legacy/a0g1bsinitvals5.fw

Extracting b43legacy/a0g0initvals2.fw

Extracting b43legacy/a0g1initvals5.fw

Extracting b43legacy/b0g0bsinitvals2.fw

Extracting b43legacy/b0g0initvals5.fw

Extracting b43legacy/b0g0initvals2.fw

Extracting b43legacy/a0g0bsinitvals5.fw

b43 firmware successfully installed.

b43legacy firmware successfully installed.**

After doing so, I disconnected the cat 5 and tried the wireless again with no success…
**
bob@linux-t9h2:~/Desktop> /sbin/lspci

(…)
0c:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g (rev 01)

bob@linux-t9h2:~/Desktop> /sbin/lspci -n

00:00.0 0600: 8086:2a40 (rev 07)

00:01.0 0604: 8086:2a41 (rev 07)

00:1a.0 0c03: 8086:2937 (rev 03)

00:1a.1 0c03: 8086:2938 (rev 03)

00:1a.2 0c03: 8086:2939 (rev 03)

00:1a.7 0c03: 8086:293c (rev 03)

00:1b.0 0403: 8086:293e (rev 03)

00:1c.0 0604: 8086:2940 (rev 03)

00:1c.1 0604: 8086:2942 (rev 03)

00:1c.2 0604: 8086:2944 (rev 03)

00:1c.4 0604: 8086:2948 (rev 03)

00:1d.0 0c03: 8086:2934 (rev 03)

00:1d.1 0c03: 8086:2935 (rev 03)

00:1d.2 0c03: 8086:2936 (rev 03)

00:1d.7 0c03: 8086:293a (rev 03)

00:1e.0 0604: 8086:2448 (rev 93)

00:1f.0 0601: 8086:2919 (rev 03)

00:1f.2 0106: 8086:2929 (rev 03)

00:1f.3 0c05: 8086:2930 (rev 03)

01:00.0 0300: 1002:9552

09:00.0 0200: 11ab:4354 (rev 13)

0c:00.0 0280: 14e4:4315 (rev 01)

bob@linux-t9h2:~/Desktop> /sbin/lspci -v

… (If you need what I omitted, I apologize, please yell at me and I will include all of it.)

09:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8040 PCI-E Fast Ethernet Controller (rev 13)

Subsystem: Dell Device 02aa

Flags: bus master, fast devsel, latency 0, IRQ 30

Memory at f6bfc000 (64-bit, non-prefetchable) [size=16]

I/O ports at ce00 [size=256]

Capabilities: <access denied>

Kernel driver in use: sky2

0c:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g (rev 01)

Subsystem: Dell Wireless 1397 WLAN Mini-Card

Flags: bus master, fast devsel, latency 0, IRQ 17

Memory at f6cfc000 (64-bit, non-prefetchable) [size=16]

Capabilities: <access denied>

Kernel driver in use: b43-pci-bridge

bob@linux-t9h2:~/Desktop> dmesg|less

(…)
15.450971] sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both

15.452244] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

25.403895] BIOS EDD facility v0.16 2004-Jun-25, 1 devices found

25.783271] eth0: no IPv6 routers present

59.555000] bootsplash: status on console 0 changed to on

586.659354] udev: starting version 146

880.867217] sky2 eth0: disabling interface

881.304448] sky2 eth0: enabling interface

881.304953] ADDRCONF(NETDEV_UP): eth0: link is not ready

882.882020] sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both

882.883381] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

893.160244] eth0: no IPv6 routers present

893.192810] sky2 eth0: Link is down.

964.444443] SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.1.101 DST=80.239.156.215 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=27545 DF PROTO=TCP SPT=55026 DPT=80 WINDOW=54 RES=0x

00 ACK FIN URGP=0 OPT (0101080A000A237C48972D3A)

964.444497] SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.1.101 DST=80.239.156.215 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=29267 DF PROTO=TCP SPT=55028 DPT=80 WINDOW=69 RES=0x

00 ACK FIN URGP=0 OPT (0101080A000A237C48972F2D)

964.444540] SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.1.101 DST=80.239.156.215 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=47031 DF PROTO=TCP SPT=55029 DPT=80 WINDOW=54 RES=0x

00 ACK FIN URGP=0 OPT (0101080A000A237C48972FD0)

964.872228] SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.1.101 DST=80.239.156.215 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=29268 DF PROTO=TCP SPT=55028 DPT=80 WINDOW=69 RES=0x

00 ACK FIN URGP=0 OPT (0101080A000A252848972F2D)

964.912268] SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.1.101 DST=80.239.156.215 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=47032 DF PROTO=TCP SPT=55029 DPT=80 WINDOW=54 RES=0x

00 ACK FIN URGP=0 OPT (0101080A000A255048972FD0)

991.408264] SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.1.101 DST=80.239.156.215 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=29273 DF PROTO=TCP SPT=55028 DPT=80 WINDOW=69 RES=0x00 ACK FIN URGP=0 OPT (0101080A000A8CD048972F2D)

1018.800313] SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.1.101 DST=80.239.156.215 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=29274 DF PROTO=TCP SPT=55028 DPT=80 WINDOW=69 RES=0x00 ACK FIN URGP=0 OPT (0101080A000AF7D048972F2D)

1026.547274] SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.1.101 DST=80.239.156.215 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=27552 DF PROTO=TCP SPT=55026 DPT=80 WINDOW=54 RES=0x00 ACK FIN URGP=0 OPT (0101080A000B161348972D3A)

1073.584268] SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.1.101 DST=80.239.156.215 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=29275 DF PROTO=TCP SPT=55028 DPT=80 WINDOW=69 RES=0x00 ACK FIN URGP=0 OPT (0101080A000BCDD048972F2D)

1083.784295] SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.1.101 DST=80.239.156.215 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=47039 DF PROTO=TCP SPT=55029 DPT=80 WINDOW=54 RES=0x00 ACK FIN URGP=0 OPT (0101080A000BF5A848972FD0)

1089.139283] SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.1.101 DST=80.239.156.215 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=27553 DF PROTO=TCP SPT=55026 DPT=80 WINDOW=54 RES=0x00 ACK FIN URGP=0 OPT (0101080A000C0A9348972D3A)

1091.276290] sky2 eth0: disabling interface

1091.705500] sky2 eth0: enabling interface

1091.706004] ADDRCONF(NETDEV_UP): eth0: link is not ready

1203.991476] sky2 eth0: disabling interface

1208.000753] sky2 eth0: enabling interface

1208.002123] ADDRCONF(NETDEV_UP): eth0: link is not ready

1233.255486] sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both

1233.256835] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

1240.488592] RPC: Registered udp transport module.

1240.488601] RPC: Registered tcp transport module.

1240.498132] Slow work thread pool: Starting up

1240.498700] Slow work thread pool: Ready

1240.498747] FS-Cache: Loaded

1240.540982] FS-Cache: Netfs ‘nfs’ registered for caching

1243.502209] eth0: no IPv6 routers present

1298.217968] sky2 eth0: Link is down.

1375.800698] sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both

1703.534115] Uniform Multi-Platform E-IDE driver

1703.538901] ide-cd driver 5.00

1703.549625] ide-gd driver 1.18

1703.566897] st: Version 20081215, fixed bufsize 32768, s/g segs 256

1820.661283] sky2 eth0: disabling interface

1821.572327] sky2 eth0: enabling interface

1821.572889] ADDRCONF(NETDEV_UP): eth0: link is not ready

1823.246862] sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both

1823.248164] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

1833.572249] eth0: no IPv6 routers present

1894.126215] sky2 eth0: disabling interface

1894.567237] sky2 eth0: enabling interface

1894.567736] ADDRCONF(NETDEV_UP): eth0: link is not ready

1896.135321] sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both

1896.136603] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

1906.952247] eth0: no IPv6 routers present

2372.596510] [drm] Resetting GPU

2372.631651] mtrr: no MTRR for e0000000,10000000 found

2372.803463] mtrr: type mismatch for e0000000,10000000 old: write-back new: write-combining

2372.803547] mtrr: type mismatch for e0000000,10000000 old: write-back new: write-combining

2372.884587] mtrr: type mismatch for e0000000,10000000 old: write-back new: write-combining

2372.884757] mtrr: type mismatch for e0000000,10000000 old: write-back new: write-combining

2372.884903] mtrr: type mismatch for e0000000,10000000 old: write-back new: write-combining

2372.900945] [drm] Setting GART location based on new memory map

2372.916642] [drm] Loading RV710 PFP Microcode

2372.916687] [drm] Loading RV710 CP Microcode

2372.931777] [drm] Resetting GPU

2372.931837] [drm] writeback test succeeded in 1 usecs

3535.375395] sky2 eth0: Link is down.

3566.739866] sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both

bob@linux-t9h2:~/Desktop> /usr/sbin/iwconfig

lo no wireless extensions.

eth0 no wireless extensions.[/size][/size][/size]

Even though I know this will not help as I have found the “brick wall” I can not pass, I have included the end of the primer on receiving help.

**bob@linux-t9h2:~/Desktop> sudo /usr/sbin/iwlist scan

root’s password:

lo Interface doesn’t support scanning.

eth0 Interface doesn’t support scanning.
**

I thank anyone in advance for any help you can give, I have read and taken to heart the advice given for receiving help and if any more is needed I will gladly give it. I have a small amount of experience with SuSE Enterprise edition so I can understand some technical stuff but I am best at following specific instructions. Thank you again!

– Bob Ford**

On 12/25/2009 03:26 AM, Bob Ford wrote:
>
> My wireless device is an integrated Dell Wireless 1397 WLAN Mini-Card, I
> am unsure about the driver I have in use. I am sure I have a driver
> installed because the configuration screen shows my network. I currently
> have the computer plugged into my network via CAT 5 but I would like to
> be able to use the wireless (obviously.) I am using Open SuSE version
> 11.2 and I have run the updater. I could not see my wireless network
> before running the updater and I can now so I know that the updates have
> helped but I am again stuck. I have tried to search the wireless forum
> and I have tried to tinker with the settings in YaST , but nothing seems
> to be working. Reading the Welcome page of the wireless forum, I tried
> the Broadcom chip-set advice:

> 0C:00.0 0280: 14E4:4315 (REV 01)

The critical piece of information is the line just above. The 14e4:4315 device
does not work with the b43 driver in openSUSE 11.2. You need to use one of the
following: (1) a 2.6.32 kernel, or (2) the Broadcom wl driver package. Both are
available in the various repos. Use Webpin to find the one that matches your
system. If you choose option 2, you will also need to blacklist ssb.

Alright, thank you so much! now to learn how to change the kernal… lol. I may have ‘learned’ SuSE Enterprise, but that class obviously just scratched the surface. Thank you again!

All right, I had a busy few days. I looked around YaST and I think I finally found out how to change the kernel, but before I ruin the install that I have spent a bit of time customizing already I decided I had better ask… I DO change the kernel through the boot-loader right? I found an older version (within 1 digit of the one I was looking for… Hope that will work.) I should just change the kernal loaded in the boot loader to the one I want? or is there another way I missed? Thank you again for all the help!

If it is an rpm packaged version of the kernel, what I typically do is install the new kernel (by installing with “rpm -ivh” , do NOT install with “rpm -Uvh” ) , AND keep the old kernel, so I can roll back if need be. ie do not install with zypper nor with YaST, nor single click install. Install with the rpm command.

You may also want to check you can get kernel-source, kernel-syms and linux-kernel-headers for this new kernel. And typically I will 1st change my graphic driver from using the proprietary driver to either the VESA graphic driver or the openGL graphic driver to ensure a reboot after installing the new kernel will work. Since openSUSE-11.2 now has an automatic probe/configuration of graphic devices, it may be sufficient just to rename any /etc/X11/xorg.conf file one may have created.

My process is to:

    1. make a backup copy of /boot/grub/menu.lst and do any required graphic configuration preparations (if any)
    1. download the new kernel
    1. install the new kernel with
rpm -ivh kernel-package1 kernel-package2 kernel-package3 ..... 
    1. check the edits that the new kernel rpm made to the /boot/grub/menu.lst file to see if they make sense, providing a dual boot to both the old and the new kernel
    1. reboot and select the new kernel on the reboot.

a number of drivers, such as webcam, graphics (noted above to avoid), virtual software can be broken by a new kernel update

I ended up getting Broadcom-wl and blacklisting SSB because I could figure that out, lol. Now I can tell that the device is working, but I am stuck again following the wireless help primer… First off when I enter dmesg|less I can no longer find the wireless device but I am sure its in there because when I run:
bob@linux-lznv:~/Desktop> /usr/sbin/iwconfig

lo no wireless extensions.

eth0 no wireless extensions.

eth1 IEEE 802.11 Access Point: Not-Associated

      Link Quality:5  Signal level:0  Noise level:0

      Rx invalid nwid:0  invalid crypt:0  invalid misc:0

and I was never able to get that before! Now, when I try the next command:

bob@linux-lznv:~/Desktop> sudo /usr/sbin/iwlist

… root pw stuff …]
Usage: iwlist [interface] scanning [essid NNN] [last]

          [interface] frequency 

          [interface] channel 

          [interface] bitrate 

          [interface] rate 

          [interface] encryption 

          [interface] keys 

          [interface] power 

          [interface] txpower 

          [interface] retry 

          [interface] ap 

          [interface] accesspoints 

          [interface] peers 

          [interface] event 

          [interface] auth 

          [interface] wpakeys 

          [interface] genie 

          [interface] modulation 

Where should I go from here? Thank you for the help!:slight_smile:

On 12/29/2009 02:36 PM, Bob Ford wrote:
>
> I ended up getting Broadcom-wl and blacklisting SSB because I could
> figure that out, lol. Now I can tell that the device is working, but I
> am stuck again following the wireless help primer… First off when I
> enter dmesg|less I can no longer find the wireless device but I am sure
> its in there because when I run:

The boot messages from wl are not the same as for b43.

> bob@linux-lznv:~/Desktop> /usr/sbin/iwconfig
>
> lo no wireless extensions.
>
>
>
> eth0 no wireless extensions.
>
>
>
> eth1 IEEE 802.11 Access Point: Not-Associated
>
> Link Quality:5 Signal level:0 Noise level:0
>
> Rx invalid nwid:0 invalid crypt:0 invalid misc:0
>
>
> and I was never able to get that before! Now, when I try the next
> command:
>
> bob@linux-lznv:~/Desktop> sudo /usr/sbin/iwlist
>
> Where should I go from here? Thank you for the help!:slight_smile:

Add “scanning” (or abbreviated as “scan”) to the iwlist command.

If you see your AP in the scan results, you should be able to create a wireless
connection with NetworkManager. If you do not get any scan results, check your
wireless switch. If on, does your BIOS have a “Disable wireless setting”?

SUCCESS! I am connected to my network via wireless! Thank you iwfinger for all your assistance! I knew the wireless was enabled because I have Windows 7 running wireless, but for some reason it wouldn’t work on SUSE. I read your post on Windows and rebooted into SUSE and I received a message that a wireless network was found and after entering my password I was connected to my network! WAHOO! lol Thank you for your assistance once again! lol!