Okay with my wireless device came some Linux drivers which I am trying to install without much success. I have the rpm package in /home/peterpan and I go into shell, switch to su and type rpm -i Prism-3.03.1-1.noarch.rpm and here is the output that I get:
linux-zsc1:/home/peterpan # rpm -i Prism-3.03.1-1.noarch.rpm
Creating symlink /var/lib/dkms/Prism/3.03.1/source ->
/usr/src/Prism-3.03.1
DKMS: add Completed.
Usage: grep [OPTION]… PATTERN [FILE]…
Try `grep --help’ for more information.
/var/tmp/rpm-tmp.93786: line 6: : -gt: unary operator expected
Kernel preparation unnecessary for this kernel. Skipping…
Building module:
cleaning build area…
make KERNELRELEASE=2.6.25.11-0.1-default -C /var/lib/dkms/Prism/3.03.1/build/BinSrc…(bad exit status: 2)
Error! Bad return status for module build on kernel: 2.6.25.11-0.1-default (i586)
Consult the make.log in the build directory
/var/lib/dkms/Prism/3.03.1/build/ for more information.
0
0
Error! Could not locate Prism_A02.ko for module Prism in the DKMS tree.
You must run a dkms build for kernel 2.6.25.11-0.1-default (i586) first.
I don’t have a Prism_A02.ko file, any help would be appreciated
The correct driver for a Dell 1450 USB is p54usb. It comes with
2.6.25-11.0.1-default. It should be loaded when you boot. Check the
output of lsmod.
Larry
…
p54usb 19584 0
…
p54common 16640 1 p54usb
…
firmware_class 13696 3 microcode,dvb_usb,p54usb
mac80211 178324 2 p54usb,p54common
…
usb_storage,dvb_usb_dib0700,dvb_usb,p54usb,usbhid,ehci_hcd,uhci_hcd
…
It’s in there, so what now?
> It’s in there, so what now?
The next step is to obtain the correct firmware file and copy it into
/lib/firmware. Go to http://jbnote.free.fr/prism54usb/index.html and
download a file named 2.5.8.0.arm. Copy it to
/lib/firmware/isl3887usb_bare. Yes, it has to be renamed. Once the
firmware is there, an /usr/sbin/iwconfig command should show the
presence of two new interfaces: wmaster0 and wlan0. In addition, ‘sudo
/usr/sbin/iwlist scan’ should show your AP.
If the above works, then you need to configure the interface. With
YaST, select Network Devices in the left panel and Network Settings in
the right one. Click the Global Options tab and select “User
controlled with NetworkManager” and “Change default route with DHCP”.
Unless you really use IPV6, deselect it. You should now finish this
screen.
At this point log off and log back in to be certain NetworkManager is
started. If you changed the IPV6 setting, then reboot instead.
The rest of this assumes that you are using a KDE desktop. It will be
similar on Gnome, but I’m not sure how different it will be. Using the
KNetworkManager icon, select the “New Connection” item for wlan0. In
the screen that pops up, enter the details of your AP and encryption.
Although the “Connect and Save” button will be active on all screens,
that is a bug that has been fixed in 11.1. As long as Next is active,
keep filling in the screens and pressing it. Be sure to check the
Autoconnect button if you want the wireless to be started at bootup.
As soon as you click on “Connect and Save”, the wireless should start.
If it does not, check the output of the dmesg command for anything
that might be wrong.
Larry
Nevermind, I got it 
Thank you very much for your help!
logarkh wrote:
> Alrighty, thanks for the reply. When I type -iwconfig- it shows the new
> interfaces. I’ve got a little problem with the device not turning on
> though, I plug it in but no lights start to flash! -dmesg- brings up
> the following when I plug it in:
Did you do the configuration? On mine, the LED doesn’t come on until
the interface comes up. With autoconnect enabled, that takes 4-5 seconds.
Does the iwlist command I gave you show the AP?
Larry