On Fri, 16 Feb 2007 13:52:44 -0500 Frank Edwards <[EMAIL PROTECTED]> dijo:
> From John Jason Jordan <[EMAIL PROTECTED]>: > > Compaq R3240, Ubuntu Edgy amd64 > > I also have an R3240, but I'm running 32-bit Kubuntu because I sick of > fighting with browser plugins. :( I use 64-bit primarily because I want to learn Linux and I figured a baptism by fire would be the best way. At the same time, I use this computer for school, so I need to keep it working. But I am happy to report that with Edgy amd64 I have 64-bit Firefox working with Flash 9 and Adobe Reader 7.08 (Linux) plugins. It takes a bit of fiddling, but it can now be done. > I don't use rsync to the flash drives ... it reads the entire file and > calculates checksums, then updates only the portions that need updating. > This means 100% of the file must be read and then some X% must be > written. I've figured it's probably faster to just write 100% and be > done with it. Note that this could hurt the lifetime of the flash > memory, though (they are write-cycle limited). I haven't done any > real-world simulations of this to determine the trade-offs. I have a couple flash drives and I've never had a problem them. But all I generally use them for is to copy a file to the drive so I can put the drive on a computer at the university when I need to print something there. I just drag and drop with Nautilus. > > [ 42.278295] usbcore: registered new driver ndiswrapper > > > > So it appears that there may be a problem with ACPI. I am wondering if > > the USB driver uses an IRQ that is being shared with something else. I > > haven't tried pci=assign-busses or pci=routeirq yet because I thought > > I'd ask here first if anyone else has encountered similar problems. > > However, I _have_ had lockups using the ndiswrapper module, which I > noticed you also have installed (it's lucky that you included that > line!). I never had a problem under 64-bit SUSE when I grabbed the > source for ndiswrapper and built it myself, but I have sporadic lockups > whenever I use the wireless under 32-bit Kubuntu. I have not looked into > this in detail yet, since I haven't *needed* the wireless, but I will > likely start on this problem in the next week or two, as I start > traveling again (hotels like wireless, since the infrastructure for it is > easier than wired (sigh)). Ubuntu Hoary amd64 was the first OS I seriously used on this computer, although I briefly tried a couple others first. I liked Ubuntu because it was so much more plug and play than the others. However, it took me a week to learn how to get ndiswrapper working. Once I had it configured it worked totally reliably. But it broke when I upgraded to Breezy, and again when I upgraded to Dapper, and yet again when I upgraded to Edgy. At one time I posted a how-to on our wiki, partly for the benefit of others, and partly so I would know where I left the instructions for the next time an upgrade broke ndiswrapper. However, the upgrade to Edgy required something slightly different. The instructions on this Ubuntu page work: http://ubuntuforums.org/showthread.php?t=340689&highlight=broadcom+4306http://ubuntuforums.org/showthread.php?t=340689&highlight=broadcom+4306 However, that probably won't work if you have a 32-bit OS. I should also mention that the new bcm43xx driver that is supposed to work with our Broadcom 4306 chips sucks. If you can even get it working, the speed is only 11 MB/s. With ndiswrapper and the bandwidth at the university I get great speed. > Try the "assign-busses" and let us know if that solves the problem. If it > doesn't, I'd try leaving out the ndiswrapper and see if that helps. > > PS: Have you used ndiswrapper on all of your previous installs as well? > Has it always been from a binary repository, ie. have you ever built it > from source? You can install it from Synaptic. But this last time around I installed version 1.34 because the only one in the repositories was 1.18. The instructions on the Ubuntu forum link above explain how to install it. If I recall correctly, for Dapper I just used 1.18 from the repositories, but all other times I did a make-install. I've never had a lockup when using the wireless, and I've occasionally used it heavily, so I'm inclined to think the problem is not in ndiswrapper. I think I'll try the pci=assign-busses first. If that makes no difference I 'll try disabling ndiswrapper. Thanks for the observations and suggestions. _______________________________________________ LinuxR3000 mailing list [email protected] http://lists.pcxperience.com/cgi-bin/mailman/listinfo/linuxr3000 Wiki at http://prinsig.se/weekee/
