nchancock

Anyone know if this release fixed the infamous "Black Windows Bug"? That is the only thing holding me back from the beryl/Xgl scene :(

You've probably already tried this, but try removing and reinstalling the driver. I remember once when I upgraded ndiswrapper, I had to to that to get it to auto-configure itself correctly :) Hope that helps.

First off, how come you're rolling your own WINE? I'm almost positive there's a binary (rpm) for mandriva. Second, the OpenGL headers are probably contained in a package called libmesa-dev or something similar. Just install that and you should be fixed. If not, then you need to dig around in the config script and find out what files it's looking for so you can install them/point the configger at them. Have Fun!

The effects offered with AIGLX/beryl are truly stunning. Unfortunately, the NVIDIA 1.0-9626 driver keeps me from using it due to the "Black Windows Bug." Basically, when I have more than one window open at a time, they start to go completely black on me. It has to due with the way the nvidia driver handles texture memory (or the lack of it as the case may be.) Once they fix that, though ....

Here's mine: 1. Ubuntu 2. Fedora 3. Debian 4. Mandriva Not bad, that's how my own list kinda came out with just experimenting...

Right. So last week my Dapper install started acting really funny in that it would run for about an hour and then get R E A L L Y S L O W. It wouldn't crash and the system monitor showed the cpu idling at 1-2 percent with full memory available. The only way to fix the issue was to restart the whole thing, but an hour or so later it would start again. So ... I thought that it might be the fault of Xgl/compiz, so I switched it off and uninstalled it and went back to Metacity. Didn't fix the issue. So then I thought, well maybe its the NVIDIA driver, and I uninstalled that and went back to the nv driver. No dice. Then I was thinking, well maybe my install is FUBAR from my kids yanking the power cord out of the wall, so I backed up my data, wiped the drive and started fresh. A clean dapper install ran like a champ ... ... until I installed the 686 kernel. After that the trouble started again. Dirty bass-masters. So what's the deal? The 686 kernel ran fine for more than a year -- just recently have I had this problem. Is this a sign of the immenent demise of my MOBO or some such? Have I angered the kernel gods? BTW, I tried installing older versions of the 686 kernel, didn't help. [moved from Laptops by spinynorman]

Check the output in /var/log/Xorg.0.log to see what is causing your X not to start/crash. Generally it has to do with your display options and the like.

This option has to be changed with the compiz config thingy. Doesn't it come with 4 desktops by default?

Speaking of nvidia drivers, did anyone see this on slashdot today? Root Exploit For NVIDIA Closed-Source Linux Driver :o

Two questions, is the bcm43xx modules loaded (lsmod | grep bcm43xx)? And ... did the card work correctly with ndiswrapper? I had a similar problem with the bcm43xx driver in the new ubuntu. I have a Broadcom chipset for my laptop's wireless and I had a devil of a time getting it to work with the bcm43xx driver. I had to install fw-cutter and cut the firmware from the windows drivers, which I screwed up, and then resorted to installing a package with all the known firmwares in it. Once I did get the thing working, it was only able to connect at 11 Mbps ... v e r y s l o w. So I decided to dump the bcm43xx and stick with the ndiswrapper. If you decide to do that, here's how. 1) unload the bcm43xx module; sudo rmmod bcm43xx 2) add it to modprobe.d's blacklist to ensure that it is never loaded again, even by accident. sudo gedit /etc/modprobe.d/blacklist add a line at the bottom that reads "blacklist bcm43xx" 3) install the ndiswrapper-utils package sudo apt-get install ndiswrapper-utils 4) change the ID for your wireless nic to wlan0 instead of the default eth1 sudo gedit /etc/iftab change "eth1" to "wlan0" and then run sudo /etc/init.d/networking restart 5) after that it's a pretty much standard ndiswrapper setup, which you can find countless tutorials here and on other sites. I found that ndiswrapper worked MUCH better for my card, and until they work some more of the kinks out of the bcm43xx driver, I am gonna stick with it. Good Luck! Nate

Anjuta hasn't been updated since time immemorial. I found that it worked alright, but several of the features needed work. You could try the Kdevelop suite or that one thats written in Java ( i forget what its called ) or monodevelop. Or you could just use vim or nano or something. Good Luck!

Sweet! Dear Jagwah, This christmas I would like a shiny new silver shovel for face smacking. I have been ever so good. Love nchancock

Best bet would be to try running PowerISO with wine and then converting it to ISO format. Then you could burn it from linux with any number of utilities. Then you should go find the tosser that made a .daa image and smack them in the face with a shovel. Honestly, what is wrong with plain old ISO?

okay here's the situatiion... Say I started a prcess from the command line as such: sudo ./my_process & and then closed the terminal window. Then later I wanted to open another window and "de-background" that process so that I could pass it commands (like ctrl-c, etc...) or snag its output, what would be the command? I know that I could use kill -SIG*** <process id> but that's not exactly what I want to do. Any help would be appreciated. :)

Ubuntu Desktop is a meta-package that, as far as I know, can be safely removed. I have removed it on my box without consequences. You might also want to check out this site: http://www.cs.cornell.edu/~djm/ubuntu/ They've got all kinds of Ubuntu tips and tricks.

This may or may not be really bad ... :mellow: I just hit ctrl-c when that message pops up. I doesn't seem to harm anything and the computer boots just fine after that. Dirty hack, but it works for the small number of times that I have the computer off the ethernet.

Maybe we should start over ... su <enter root password> ndiswrapper -l <--------- this will show you what drivers are installed. ndiswrapper -e <driver name> And then follow this guide: Ndiswrapper: Suse Install

If you're sure that you installed the right package from the Suse disk (I don't know what that would be as I don't use SUSE), it should be available from the command line. Example: ndiswrapper -i /path/to/windows/inf will install the windows driver for the wireless card. If it doesn't work, make sure ndiswrapper is installed with: find / -name ndiswrapper If that doesn't work, then you installed the wrong package.

The tar.gz should have a set of install instructions in it. If not then "BAD FORM!" to the package distributors. Anyway failing that the websites should have installation instructions on there somewhere (I know that gnome-look and KDE-look both do. Another thing you can try is opening up the theme manager and draggin'-and-droppin' the tar.gz into the list of themes. This works on Gnome, maybe KDE has implemented the same functionality... Nate

Giving up already? Its your choice I guess, but if you keep at it some, I think you'll have better luck. Either that or try Linspire ... they're aimed at complete noobs. Very hands-off but less so than Windows. Once you get the feel for the environment and how to use basic tools like a package manager and the command line interface, you'll be well on your way to being a guru. Nate

For Matlab, there would be no point to virtualization ... they have versions for both linux and window$. I found that the linux version ran faster, at least or what I was using it for.

You have opened the age old debate between the two camps. Now let the flamewar betwixt the KDE fanboys and the Gnome fanbots commence! :)

just to clarify, to check what modules are loaded type "lsmod | more" at the commandline.

google is your friend... http://www.linux-on-laptops.com/compaq.html http://groundstate.ca/TC1000/ http://linux-tablet-pc.dhs.org/

Not hard at all, I got it set up in just a few minutes. The only trick was that since I was using open key mode, I had to use "sudo iwconfig wlan0 key open ###########" instead of without the 'open' part. Other than that, it was just: 1) install the deb from synaptic 2) get the driver from hp 3) sudo ndiswrapper -i /path/to/driver/inf 4) sudo ndiswrapper -l 5) sudo ndiswrapper -m 6) sudo modprobe ndiswrapper 7) sudo iwconfig ... no problems at all and I have a Broadcom at that. I'm actually excited for the 2.6.17 kernel branch that has the bcmxx driver in the kernel itself. I think it will make things a lot easier for people coming to Linux for the first time. No more dinking around with ndiswrapper, the installer should config it without any intervention. Nice for newbs. EDIT: one thing I should mention ... ndiswrapper doesn't play nice with the smp kernel. I had to go to the non-smp kernel to stop the lock-ups. Bummer. Write back with issues. :) Nate