As such, Im closing it since theres not much to discuss.
]]>I do know 64 bit Windows 7's rather buggy as it has spotty driver support compared to Linux
]]>But it does not bother me that much , anyway.
]]>Is this method still the best way to upgrade to 64 bit, or would it just be easier if I downloaded the 64 bit install disk and did it that way?
]]>Me and you are running the same hardware and I agree about BMPanel.
Tint2 does include its own useful tray now (might give it a try) if you like it. I personally went and stuck with tint2. I think lxpanel had a few graphical glitches.
You also are going to run into problems with your headphone jack if we have near identical Realtek HD Audio Codec ACxxx. It doesn't seem to get a sound level amplification.
I have found no fix so far.
]]>EDIT: I now have lxpanel 0.4.1 working perfectly. :D
]]>I've used the 9.04.01 installer on top of an Ubuntu 9.04 minimal install with much success!
This install is on an ASUS M50Vm-X1 laptop. There are a few caveats with this model which require additional setup for GNU/Linux in general, but these things aren't really #!'s fault, so I'll leave that part out.
(If anyone is interested I could provide a how-to since it really is a pain to figure these things out by yourself.)
There were some hiccups, however...
As mentioned elsewhere on the forums, there seems to be a problem with the Crunchbang GDM theme which causes GDM to hang most of the time while it is loading. Switching to another theme fixes this problem.
With the nfs-client tools installed (I believe the nfs-common package leaves the server out, although I could be mistaken), the system hangs while attempting to load the nfs module. At this point one can switch to a different terminal and uninstall nfs to force the system to continue loading, but this is certainly not a fix. This is a severe problem for me as I map a large hard-drive to this laptop for all of my music/movies/data/etc.
My only qualm with this version of Crunchbang is the inclusion of bmpanel by default. It is simply too ugly. Lxpanel would have been my first choice if version 0.4 were available in the repos (refer to this for the bug I am referring to).
I used corenominal's "Howto replace lxpanel with tint2 & trayer" how-to, which resulted in a much more aesthetically pleasing desktop. :)
I have two complaints about this setup:
1. I can't figure out how to force trayer to sit behind windows that collide with it. I couldn't find anything which would alter this behavior in the man page.
2. The clock doesn't count seconds. It always stays at "00".
Other than these relatively minor problems (with the exclusion of the nfs thing), this is definitely the most solid OS I've managed to get running on this hardware. I can finally utilize all 4GB of RAM!!!
Obligatory screenshot:
snazzy, eh?
My System Specs:
Asus P6T Deluxe v2 mobo.
Nvidia GTX 285
Intel Core i7 920
6 Gb RAM
2x 1TB Caviar Black HDD
Dualbooting Windows 7 and #!.
Problems I encountered:
1. As mentioned by others, Pcmanfm was not mounting my ntfs partition. Thunar also would not do this. For those who don't know how to/want to muck around in their fstab, the simple fix is to use ntfs-config.
sudo apt-get install ntfs-configThen alt-F2 and run ntfs-config. From there, the GUI is fairly self-explanatory.
2. Internet browsing was slow/unusable. I know this isn't my connection because my laptop was running on the wireless faster than this box would run on ethernet. Also doesn't seem to be browser specific as both firefox and elinks were painfully slow. I did have a sizable file copy operation going on in the background so that could be related. Still htop confirmed that system resources were not running above 10% anywhere. If this problem persists, I'll have to switch to a 32-bit install...
]]>Don t hesitate to delete this posts :-)
]]>http://crunchbanglinux.org/forums/topic … -included/
http://crunchbanglinux.org/forums/topic … partition/
I am not able to identify if this is an 32 or 64bit problem or pcmanfm or 9.04 or whatever.
So maybe someone else could check this behavior on its PC as well to identify the error (or am I the error - OSI layer 8 error).