jbuckley2004

Whoa! That was a great idea, scarecrow. When I run glxgears I get something like the error I noticed running google-earth: Xlib: extension "GLX" missing on display ":1.0". Error: couldn't get an RGB, Double-buffered visual I'm not sure what I'm looking for yet, but I think you're right. The nvidia driver isn't properly configured. I'll be exploring this, but if you have any further suggestions for me to try, I'd be appreciative. More - Ok, that was weird. II first tried to see what I could futz with in the NVIDIA Server Settings (available from the list of systems applications), and nothing seemed to be relevant. Then I went into the MCC, hardware and the X graphical server. I poked around, but changed nothing, then hit the "test" button. The display showed me that it was fine, and I hit ok before the 15 second timer expired. But the driver didn't recover. I just a colorful but random display of nothing. On reboot, it failed to start x, so I tried manually, and it told me the driver was not found. The driver was still on my drive, however, so I logged in as root and re-installed it successfully, and I was able to come up normally. But I'm back to where I was, with google-earth and glxgears telling me that the Xlib is missing the extension GLX on display ":1.0". Next trick - I'm going to turn off Matisse and see what happens.

Thanks for this, Scoonma. I looked, and found the same locked symbolic link. I removed the .googleearth directory and re-installed (oh - noticed that the .googleearth directory doesn't appear until after I run at least once), but the same thing came up - it doesn't know that the graphics card is known.

I had Google-Earth installed and working with Mandriva 2006 Free. When I updated to Spring 2007 One, I kept the home partition, where G-E had been installed, and otherwise did a complete install. I noticed that the Google-Earth app is now supplied with the distribution. That's cool, but now when I tried to run it, I get the error/warning that reads "Google Earth is unable to identify your graphics card. This is most likely because the driver for your graphics card has not been installed..." The link given by G-E only states that the latest driver should be installed. Hum! The MCC correctly identifies my card (Nvidia 5200 FX), and the latest driver *was* installed. In fact, I'm running Matisse nicely right now, thank you very much. I've already un-installed and re-installed both G-E and the nvidia driver to no effect (the same message comes up). Can anyone tell me how to proceed? Perhaps there's a G-E configuration somewhere that needs updating? Thanks in advance for any info. More - I just notices that when I start it from the command line, I get the message "Xlib: extension "GLX" missing on display ":1.0"." about a million times.

Has anyone using wireless broadband installed 2007.1 One yet? I'm curious to know (before I try it) if they've included ndiswrapper on the live version, so that I can use my Atheros card to get the full install. Thanks.

I had cups (and hplip) installed successfully once, so I know this can be done on my setup. I seem to be having a problem now with either CUPS-1.2.4 or with PrinterDrake. When cups is installed and I bring up printerdrake from the MCC, it immediately starts looking for the default printer. It doesn't find it, because there is none, locally anyway, and printerdrake seems to hang. The log shows: 15:21:37 printerdrake[6887]: modified file /etc/sysconfig/printing 15:21:38 printerdrake[6887]: running: /etc/rc.d/init.d/cups status 15:21:38 printerdrake[6887]: running: /sbin/chkconfig --del cups 15:21:38 printerdrake[6887]: running: update-alternatives --display lpr 15:21:38 printerdrake[6887]: symlinked file /usr/bin/lpr-cups to /etc/alternatives/lpr 15:21:38 printerdrake[6887]: running: update-alternatives --display lpq 15:21:38 printerdrake[6887]: symlinked file /usr/bin/lpq-cups to /etc/alternatives/lpq 15:21:38 printerdrake[6887]: running: update-alternatives --display lprm 15:21:38 printerdrake[6887]: symlinked file /usr/bin/lprm-cups to /etc/alternatives/lprm 15:21:38 printerdrake[6887]: running: update-alternatives --display lp 15:21:38 printerdrake[6887]: symlinked file /usr/bin/lp-cups to /etc/alternatives/lp 15:21:38 printerdrake[6887]: running: update-alternatives --display cancel 15:21:38 printerdrake[6887]: symlinked file /usr/bin/cancel-cups to /etc/alternatives/cancel 15:21:38 printerdrake[6887]: running: update-alternatives --display lpstat 15:21:38 printerdrake[6887]: symlinked file /usr/bin/lpstat-cups to /etc/alternatives/lpstat 15:21:38 printerdrake[6887]: running: update-alternatives --display accept 15:21:38 printerdrake[6887]: symlinked file /usr/sbin/accept-cups to /etc/alternatives/accept 15:21:38 printerdrake[6887]: running: update-alternatives --display disable 15:21:38 printerdrake[6887]: symlinked file /usr/sbin/disable-cups to /etc/alternatives/disable 15:21:38 printerdrake[6887]: running: update-alternatives --display enable 15:21:38 printerdrake[6887]: symlinked file /usr/sbin/enable-cups to /etc/alternatives/enable 15:21:38 printerdrake[6887]: running: update-alternatives --display lpc 15:21:38 printerdrake[6887]: symlinked file /usr/sbin/lpc-cups to /etc/alternatives/lpc 15:21:38 printerdrake[6887]: running: update-alternatives --display lpmove 15:21:38 printerdrake[6887]: symlinked file /usr/sbin/lpmove-cups to /etc/alternatives/lpmove 15:21:38 printerdrake[6887]: running: update-alternatives --display reject 15:21:38 printerdrake[6887]: symlinked file /usr/sbin/reject-cups to /etc/alternatives/reject 15:24:48 printerdrake[6887]: running: lpstat -l -p -v 15:28:02 printerdrake[6887]: running: lpstat -l -p -v 15:31:11 printerdrake[6887]: running: lpstat -l -p -v 15:34:20 printerdrake[6887]: running: lpstat -l -p -v 15:35:51 printerdrake[6887]: running: lpstat -l -p -v 15:39:39 last message repeated 3 times 15:42:48 printerdrake[6887]: running: lpstat -l -p -v which shows me that although everything seems frozen, it isn't. Note that lpstat is being re-run every three minutes, but not returning anything. Between the second and third running of lpstat above, the configuration screen did update, but was still effectively frozen after that. If I try this when cups isn't installed, then it dutifully installs it and gets stuck at the same place. What I think I'd like to do is to tell printerdrake to not look for a default printer, but let me configure cups to find it on a networked machine. How can I do this? Thanks

Thanks for the come-back, SoulSe. Trying to connect to localhost:631 using https: returns the same error-page as before, using http: My cups.conf file reads (in toto): <!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN" "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd"> <busconfig> <!-- Only root can send this message --> <policy user="root"> <allow send_interface="com.redhat.PrinterSpooler"/> </policy> <!-- Allow any connection to receive the message --> <policy context="default"> <allow receive_interface="com.redhat.PrinterSpooler"/> </policy> </busconfig> (This is in /etc/dbus-1/system.d/) Hope there's a clue in there, somewhere.

I've been trying to get remote printing going using Mandriva 2007 Free. As I did successfully just last month, I installed CUPS and hplip, but I've run into a new problem. The first time I entered the MCC and tried to set up the printer queue, I recall getting a dialog that asked me to select search for remote or local printers. I inadvertently selected "local printers" (at least, I think I did), and it never found one, and I don't think I exited the MCC 'gracefully'. From that point on, I've been unable to get back to that dialog, and all I see is a "please wait" message and a search that apparently never terminates. From the browser, when I go to http://localhost:631, I get "Firefox can't establish a connection to the server at localhost:631. The site could be temporarily unavailable or too busy. Try again in a few moments." If I select 'print' from the menu, firefox (and any application that I try to print from) freezes. Any suggestions on how to proceed? Thanks in advance

Thanks for the replies. Tyme, I started with cups 1.2.4, and because there was an earlier version available, took your suggestion and tried it with cups 1.2.3. It installed, but hplip 1.7.2 still complained that it wasn't. So I removed all the cups versions and libraries and re-installed the later version, but as I expected, that didn't work either. I start to believe that there's a bug in the hplip-1.7.2.run script, which prevents it from recognizing that cups is installed (and incidentally, it correctly found that cups-devel was not installed, and was able to install that image. Go figure.). So, Greg, I took your advice - you'd think that I would have looked in the repos for hplip *first*. I didn't see version 1.6.12, but version 1.6.9 just installed. Hopefully, that will get me going with printing in just a bit. Appreciate the help.

Just three weeks ago I successfully installed the printer drivers I needed using the hplip-1.7.1.run executable, and was happily printing on a remote hp printer on my wife's windows box. For other reasons I re-installed Mandriva 2007, got everything else up to snuff, and tried to re-installed the HP driver. Found that there's a new installer, hplip-1.7.2.run. I re-installed CUPS and follows, is the proof: When I execute hplip-1.7.2.run, it unpacks, starts, verifies the environment, and tells me that cups (required) is not installed. It tries, and fails, to install it from the available media (which had been set up by easy-urpmi, btw). So I check that cups is installed (it is, according to the MCC), rinse, repeat, and I even turn on the CUPS system service. The installer still comes back saying that cups is not installed, and that it can't install it. (And for what it's worth, the old installer, hplip-1.7.1.run, now fails with the terse message "extraction failed"). Has anyone else experienced (and hopefully solved) this problem? Thanks in advance

You may want to try here http://nextgen.no-ip.org/~andrew/linux/ndi...nfo10-32bit.php There are several issues going on at once, not the least of which is that your Belkin wireless (probably) uses a Broadcom chip. Broadcom's support for Linux (of any flavor) has been - well - disappointing. There are *no* Linux drivers for the Broadcom chip sets provided by the manufacturers (someone will correct me if I'm wrong about the number!), but I understand that people have successfully used ndiswrapper to make a workable Linux driver. Usually people can use ndiswrapper with the windows driver that comes with their hardware. But in the case of Broadcom chip sets someone usually has to make a specific use driver, or perhaps a set of drivers. The one that works for you may depend upon your laptop and/or the Linux kernel you're using. It's not exactly easy. It's do-able, but may take some self-education and patience. The easiest solution is to give up on Belkin and invest in another brand, one with better support. The better solution (probably) is to read-up and see how others have gotten it to work. Think of it like getting under the hood of your "409" in 1966 and "suping it up". There are lots of people able and willing to help when you have specific questions.

I had such a hard time getting my linux box (Mandriva 2007 free) to detect and access the printer on my wife's win2k box (via a wireless router) that I thought I would describe the mistakes I made and the steps necessary to get the setup working. I went through the following sources to find the information: perhaps some of it will help you too - http://www.biz1.net/cifs_help.htm - all about CIFS http://www.liv.ac.uk/csd/mobile/myfilestore/cifs.htm - more CIFS details http://samba.anu.edu.au/cifs/docs/what-is-smb.html - just what is samba, anyway? http://www.microsoft.com/mind/1196/cifs.asp - The reasons MS has made this so damn difficult... http://learn.clemsonlinux.org/wiki/Samba_client - If you want to do it the old-fashioned way... http://www.linux-foundation.org/en/OpenPri...tabase/MainPage - where to find drivers http://www.linuxquestions.org/linux/answer...nter_using_CUPS - This describes a different configuration, but can be helpful! First of all, it's necessary to have administrator access on the windows box. You'll need to do a couple of things: 1) from start->setup->printer, right click on the printer and select sharing. If it isn't already, make the printer a shared device (check the box) and under the 'sharing' tab give it a name or note the default name. Write it down; you'll need it exactly as written, case sensitive (and if you're giving it a name, it's easiest by far to not use spaces or some special characters. KISS). 2) optional, but highly recommended: from the control panel create an account (users&passwords) with the lowest level of privelges possible and NO password. We'll be letting the linux box 'log into' this account remotely, later (and evermore) to get to the printer. Although you can get to it from any account that is password protected (including the administrator), becasue of a bug in printerdrake, the password is sent over the air in the clear. Broadcasting your password for the administrator account is not a particularly good idea, right? 3) If you don't know it, get the ip of the windows box. From start->programs->accessories bring up the command prompt. From there, type >ipconfig and get the ip address. It's probably something like 192.168.1.2. 4) In theory you should be able to use the name of the windows box (assigned at installation) in place of the ip above (I believe you can find it by right clicking on 'My Computer', properties and digging around a bit), but was totally unable to get it working using that name. Big Mistake #1: If you have a firewall running on the windows box, make sure it's configured to allow the printer to be seen. You have a firewall on your windows box, right? Ok, you're done on the windows box. Assuming the printer is working there, it's good to go. On the Linux box you will need to install drivers and CUPS next. I discovered that the printer I was using (an HP Office Jet) has very good linux support, (as does Epson, I hear) and has linux drivers available from many sources. If you need to find yours, start with http://www.linuxprinting.org - I installed the latest version of lpijs (the driver for my hp printer) using the on-screen directions. This failed the first time because (Big Mistake #2) CUPS needs to be installed first. CUPS has a few dependencies, and when all was said and done the cups packages installed were: cups-1.2.4-1.mdv2007.0 cups-common-1.2.4-1.1mdv2007.0 cups-drivers-2007-6mdv2007.0 gutenprint-cups-5.0.0-2mdv2007.0 libcups2-1.2.4-1.1mdv2007.0 libcups2-devel-1.2.4-1.1mdv2007.0 libgnomecups-0.2.2-3mdv2007.0 libgnomecups-1.0_1-0.2.2-3mdv2007.0 The packages on your system may be slightly different, of course, if you're not using Mandriva 2007.0 free, and I'm not 100% sure that all the above are necessary. But it appears they are sufficient. Now I went back and installed the driver for the printer successfully. It is, btw, a command line operation, but it is very straight forward (so don't be afraid, newbies!) Big Mistake #3 - CUPS service is NOT started automatically. It's necessary to turn on the system service via the MCC [star/kicker]->system->configuration->configure your computer->(root password)->system->Enable or disable a system service. The CUPS entries are the eighth and ninth ones on the list, in my set up anyway. You probably want to check "on boot" for CUPS and "start", and check "start when requested" for CUPS lpd. If you do not start the service then you will get the error "Connection to CUPS Servicer failed." when you select the print option from most any application, like an editor. From here there are several ways to get the linux box talking to the printer via the windows box, and I went down many unnecessary paths. I'll describe two ways to get to where you want to go. For Mandriva users, the printerdrake tool works fine now (or, at least it did for me) once I ignored the 'host name' entry and provided an IP for the host machine instead. From the top: [star/kicker]->system->configuration->configure your computer->(enter root password)(select Hardware)(select Set up the printer(s), the print job queues...). Using the Drake tool: Select Configure CUPS from the tool bar or menu. Select the check box "Automatically find available printers on remote machines" and click Ok. Click on the Add Printer icon and select the appropriate check box - for me it was "Auto-detect printers connected to machines running Microsoft Windows" Big Mistake #4: The search *will* return something, even if it's only a generic name that is in reality a 'dummy' file attached to your linux box. Be sure it also returns the correct printer attached to the correct IP address, that is, the IP of your windows box that you found above. (If it doesn't, make sure that your printer is really accessible through the network [is the windows box running??? - I suggest here using ping to be sure that there is some network connectivity]. Select that printer. For me, printerdrake correctly identified the printer, it's make and model and located the driver I had installed earlier. Big Mistake #5: It says "success", but you're not good to go just yet. There is authentication information you may need to provide. If you do not, then if you look in the right place, the smb logs or the CUPS web-based tool's job information tab, you will see the error message "Unable to connect with CIFS host." when you try to print. From Printerdrake, select the tab "Configured on this machine" (isn't this confusing? I thought it was configured on the *other* machine, but nooooo....) and highlight the printer line. Click the edit icon. Select the Printer Connection Type line and Do it! Select the Printer on SMB/Windows server check box. Big Mistake #6: The SMB Printer Options information has to be correct (e.g. the share name hpoffice is *not* the same as HPoffice and it's definitely not the same as "HP Office"), but not all of it is necessary. I think there is a bug here, too. The share name (see above - you wrote it down, right?) is required. The user name and password for the account you set up is required (there is an information box here that says the password is broadcast in the clear, so please please please use something other than the administrator account, and now you know why the password-less, powerless account on the windows box is a better choice). The SMB server host should be the name of your windows box, but I just could not get that to be recognized. Authentication failed for me until I left it blank and used the SMB server IP (the IP of the windows box) instead. I left Workgroup blank with no problem. If you're successful, you should be able to print a test page - it's one of the options. Congratulations! You're done. Using web-based CUPS administrator tool: From your browser, go to http://localhost:631/ The Common UNIX Printing System configuration tool comes up. I found the interface a little confusing at first, but not too bad once you get used to it. Across the top are tabs for home (the page you're looking at), administration, and helpfully, jobs and printers. If you've configured your printer already using something like the above instructions, click on the printers tab and see if the information there looks right. In particular, the device URI should be the be the IP and sharename that you entered into printerdrake before. The make and model should be correct, as discovered automagically by printerdrake. If you haven't set up the configuration, click on the administration tab and then select Add Printer. The first time you do this it will ask for the root login - use root for the id and the linux root password. For Name, use the share name (exactly!) that was used on the Windows box in Step 1 up top, location and description are free-form entries for you to use. It then wants the same information that printerdrake asks for; I suspect smb://localhost/yourexactsharename or smb://192.168.1.(?)/yourexactsharename (where (?) completes the IP of your windows box) works, but did not for me for reasons stated below. Click continue, and select your printer, make and model from the list. If your drivers were successfully installed before, then you will have an indication that you can use CUPS. But I have NOT been able to find where to enter the authentication (windows account name and password) in this web-based interface. If someone can find it, please tell us! Without a proper authentication, when you try to print you'll soon see a message that reads "Unable to connect with CIFS host (retrying in 60 sec.) when you click on the printer tab. This was, unfortunately, my only clue (at first) that it was CIFS authentication that was failing. I found it very handy to check the status of print jobs, and easy to clear away all my mistakes building in the printer queue, by clicking on the jobs tab and deleting all jobs. Hope this helps.

Thanks, Michael. It's working now, but I'm not exactly sure why It wasn't before. Oddly, the USB ports are NOT working through the keyboard (they used to, when I was using Mandriva 2006 - I suspect that might be a driver issue), and it doesn't seem to matter if I select legacy keyboard or not in the BIOS. For the curious, though, I noticed that one of the 4 ports was ECHI, and when I plugged the thumb drive into it, then it the automount came up immediately. So I thought to myself "Self, maybe you just never tried that port before. They all look the same to you, ya know." ;> I was even more surprised to find that after that, the thumb drive worked in *all* the ports in the back of the box. I don't believe in magic, but sometimes, ya gotta wonder.

I recently replaced a ASUS P3F MB with a Gigabyte K8NS Ultra, and am using an AMD 3800+ and a very old ATI 7000 graphics card that the motherboard is running at 1x. The OS is Mandriva 2007 free, the 32 bit version, not the 64 bit version. The only functionality I seem to have lost in the upgrade is my USB ports, sort of. The Dell keyboard works through the USB ports without complaint, but my memorex traveldrive and Scandisk cruzer mini aren't recognized. dmesg returns usb 2-4.2: new full speed USB device using ohci_hcd and address 4 usb 2-4.2: not running at top speed; connect to a high speed hub usb 2-4.2: no configuration chosen from 1 choice when I plug the drives into the keyboard's USB ports, but returns nothing when they're plugged directly into the ports in the back of the case. The hardware configuration from the MCC shows me two OHCI Host controlers, one EHCI host controller and one keyboard hub, all of which have Media Class as Hub|Unused. The keyboard hub seems to be identified correctly as the Dell keyboard. I guess I have several questions: How can I begin to trouble-shoot this? and Is this a USB driver problem? Are there other Nvidia drivers available, or Is there some manual config I should do? Is there a BIOS setting that I'm missing? (Most of the relevant settings for the USB are defaults, but I changed one to USB legacy keyboard, which seemed to solve a small earlier problem that I had with the lilo). Any help is appreciated.

Lando - thanks much. That worked! Hellfried, maybe you've already figured this out, but no, you don't have to copy the whole thing. The beginning of the firefox shell script is 50 or 60 lines that start with #. They are comments. The very next thing is a subscript called moz_piz_startstop_scripts(), which is what Lando copied to show us where to add the line: export XLIB_SKIP_ARGB_VISUALS=1 (see it at the bottom?). Just find the section he showed us, and add the one line where he did. It works.

Yeah - I had the same symptoms, tried the suggested update to the firefox shell, and got the same results - it still doesn't work. So I did a little investigation. First off, the firefox troubleshooting suggests running it in safe-mode: >./firefox-bin -safe-mode but that only generated the error: error while loading shared libraries: libmozjs.so: cannot open shared object file: No such file or directory Odd, 'cause the lib libmozjs.so is in the same directory, with 755 privileges. There's additional information at the MozillaZine knowledge base http://kb.mozillazine.org/Knowledge_Base under "frequently encountered issues/firefox crashes". The exact line is "Plugins thay may cause Firefox to crash if not updated include: Macromedia Flash" Arrrggg!!! It seems that 2.0 requires, at least indirectly, the flash 8. Does Not Exist for Linux. Ugly. If anyone can suggest the next step, I'm all ears!

Ah, thanks, Scarecrow. But I did install CUPS and a working ppd profile. I think I hit on the cause of my problem though - the firewall on the win2k box on, and doing its job. Doh!

My wife's win2k box has a usb printer (HP Officejet g55) mounted as shared. We are on a common wireless router. I'd like to print to her printer from my linux box, running Mandriva 2007. Once, about a year ago I succeeded in setting up smb4k and cups to allow me to print files to her box and printer, so I know it can be done, but since re-installing (twice) and upgrades to Mandriva 2006 and 2007, I haven't been able to print anything but .ps files. So far... Smb4k 'sees' my wife's win2k box and the printer (I see the correct group name and her hostname and even the printer name), but the printer is not mounted. From the MCC, when I try to add the printer, the auto-detection fails (I checked to be sure I have the IP/hostname correct). Like I said, smb4k never shows the printer as mounted, and if I try to mount it manually an error occurs that says it can't find the disk size (!). But two days ago, when I was very tired, I did something and was able to mount it, which is the one time I was able to print a file. I noticed on right-clicking the highlighted printer in smb4k that there is another mount option, but it is greyed out. I've trying using the browser to go to smb://myhost/631, but that goes over the same ground as the Mandriva tool, with the same results. Now there's a lot going on here, and the problem may be in smb4k or networking, or cups configuration (software) or understanding Mandriva, so if this is better placed in another forum, I understand that! Thanks for any help.

I had very good luck with the drivers and firmware that I found here http://www.houseofcraig.net/indx.php - his instructions are excellent. Just follow the link (acs100) at the left of his page.

rogerh Thanks for the tip, but it doesn't seem to have worked. I have this vague memory that at install time I configured the ATI card to use 64 bit color. KDE tells me now that it was at 16 bit. Changing it back and forth gave me some pretty florescent backgrounds, but did not change the cursor (it's still transparent) when I rebooted. I also have a vague memory Mandrake/Mandriva has perennially had difficulties in changing the graphics "on-the-fly" and one has to go through the re-install to change it. ARG!

I'm trying to understand the meaning of the graphical indication of signal strength given by kwireless monitor in 2006 Free. I've been noticing the indication as I browse is two red bars for my own router in the other room, and consistantly one bar for both of my neighbors (one of whom I know is three doors down). But much to my surprise the other neighbor is suddenly coming in and the signal strength indication is five bars (!!!) and shown in green. Huh? Does anyone know what the green is all about? iwlist ath0 scan shows that he's using two frequencies (not adjacent to mine, fortunately) and the signal level was given as -1 dBm (my own is at -73 dBm). Again, huh? I understand that using two frequencies means he's got a late-generation router, but how is he/she/it blasting me with a 94/94 quality at such a high level? Am I reading kwirelessmonitor incorrectly? Is Eschelon after me? ;> Thanks

I'm having the exact same problem (can't see the semi-transparent mouse cursors) with an old ATI 7000 card in Mandriva 2006 Free. I've successfully installed new icons (the shapes change), and I've edited the index.theme file so that it inherits KDE-Classic, but nothing changes that transparent color. Is this a driver issue? Anyone able to change the color or their curors, like, to red-glass? thanks.

Many thanks, Gents. Worked like a champ. Aomighty, I have a question, though. Changing the auto-suspend time and invoking realplayer through soundwrapper seems to accomplish what I intended. But I see no reference to artsdsp anywhere (yet, except indirectly, now that i know KDE is using it for system sounds). In other words, I didn't route realplayer through artsdsp to start with, but I think that's what you meant. Am I confused about something else now? Or am I reading what you posted incorrectly? Again, thanks for any clarification (and thanks for the answers). J

I'm not certain how to catogorized this problem. I'm using a SB 16 sound card with ALSA, and often listen to streaming audio (and vidio) and straming MP3 using RealPlayer under 2005 LE. Works fine. But after 6 months, I just discovered how to turn on system sounds. Cute. Love 'em. But when they're on I can't connect to the streaming audio without a 'device busy' error from RealPlayer. Sigh. I realize that the system can only play from one process at a time, but doesn't an application (as an example) release the sound device when it's done? Am I missing something here, or is it *not* possible to even have system sounds turned on and use RealPlayer (and I imagine, Timidity, Kaffine, etc) at the same time? Advice or pointers to any HowTos are appreciated! [moved from Software by spinynorman]

Mike, You're obviously way ahead of where I thought you were. Sorry! I think the way to proceed is to show us the results of ifconfig and iwconfig. Can you set the rate or the channel? You might try ifconfig wlan0 up followed by iwlist wlan0 scan to see if the card can hear anything. I'm not too up on ndiswrapper (so I'm afraid I can't help much), but it's possible that a different version will work for you, even if the one given with 2005LE doesn't. Of course, there may be a later one too. The trick is to find a driver that ndiswrapper can use with your chipset, and it's not always the driver that came with your card. Sometimes you have to dig to find one that works. Good Luck

Why, yes, I have. Using it to write to you here, actually ;> I'll outline, briefly, what I did (as I remember it) to get the card working, but please know that I really don't know exactly how to help just yet. There's a difference between someone new to computers and someone new to Linux and someone with a little experience in Linux/Unix and a Guru so please try not to be too frustrated here. The general rule of thumb is: "the most specific questions will get the most direct ansers". First, some preparation. You need to install pci-utils. If the command lspci (part of pci-utils) returns something like "command not found", then it's not installed by default. Also, you'll need the "gcc" command and "make" command to be available, so if gcc --version and make --version return "command not found", install them too. If you're with me so far... Please verify that you have the same version of the DWL-G510 card that I have. Mine is version B. The way to find out is to start a console session and type the command lspci at the prompt. If one of the lines looks like "00:0a.0 Ethernet controller: Atheros Communications, Inc.: Unknown device 001a (rev 01)", then we're in business. It's an Atheros chipset. To find the specific driver you need, first notice in that line the four hex digits, "001a (rev 01)". Next, in the consol session type lspci -n and find that same group. For me, it comes out near the end, and the full line reads: 00:0a.0 Class 0200: 168c:001a (rev 01) That 168c:001a is the important thing. It's used to identify the driver you'll need. If you find this line (or something real close), we're doing good. If you go to http://madwifi.sourceforge.net/ , you'll see all about the MadWiFi driver for the Atheros chip sets. The page http://madwifi.sourceforge.net/dokuwiki/do...patibility_list will show you if your chipset is compatible with the madwifi driver, and if you really have the same card that I have. Ok. I'll stop here for now, and let you read the madwifi faq. Basically, you will download their source (as a tar-ball), compile and make and install the driver. It's really almost as simple as that. But damn, it's intimidating the first time. There is an alternative, which is to use ndiswrapper to "wrap" the windows driver you have (it came on the cd with the card) in code so that Linux can deal with it. Plenty of people seem to do well with that approach. But since you have to do the same thing with ndiswrapper that you'll be doing with the madwifi driver, the extra layer seems problamatic to me. Besides, I reallly have to admit, the madwifi driver really works well for me. I had more frustrations with what came *after* all that. You'll fnd that Mandriva doesn't automatically install some network stuff that you'll need either. It's ok - it's there on the installation disks. We'll get to it later.