Trying to use the remote desktop app to connect the N800 to a winXP profession PC. I can do it under the native system, i.e. Hildon?, I then go into KDE, it connected to the host computer, and give me the menu to type it more info, it then quit and give the above err statement? I get out of KDE and use the rdesktop and it wont connect now. I reboot the N800, and the rdesktop is now able to connect. I have not tried VNC yet.
Freshly flashed N810, installing to internal MMC2.
Files sizes all triple checked.
I put the MMC2 files on a 4 gig card,
stuck it in the MMC1 slot, and tried to install from there.
First file installed fine, made the swap and the image.
Errored out early on the second file.
Log didn't say what it couldn't find.
Your description in the broken installed file, however,
told me something I haven't read anywhere else.
The .BZ2 file has to be on the card you're installing to.
The install was hosed, and the uninstall didn't work.
The internal card was hosed.
Powering up with the USB cable already in beat the locked card problem,
allowing my PC to reformat the borked internal card.
Flash again, copy all four files to MMC2,
and we're off and running.
The instructions do not make it clear that the KDE358.tar file must be named KDE358.tar.bz2! It was downloading to my PC as KDE358.tar.tar which I copied to the sd card at mmc1 on my N810, but when I attempted to install I kept getting an error when trying to install the kde-3.5.8-mmc1.deb file. I tried reflashing and re-downloading but kept getting the same error until I renamed the file to KDE358.tar.bz2 on my mmc1 card. I then got a good install!!
First off -- thanks to penguinbait and and everybody else that fills this forum with quality info. This device would be pretty dull without all their impressive hacking.
If, for some reason, you get a Cannot install package when attempting to install the kde-3.5.8-mmcX.deb package, you probably won't be able to uninstall or install it again. Several people have had to reflash the device.
The above happened to me last night. The reason, as I found out, Windows XP automatically renamed the .tar.bz2 file to .tar.tar (so, this renaming doesn't just happen on Vista. Unfortunately, I didn't realize it had happened until I attempted install of the second package, and got the failed install). Multiple attempts at re-installing/removing/updating were unsuccessful... The only recourse was to exit into terminal and do the following (you probably have to be root):
Make sure the tar.tar file is renamed after you download it. Renaming beforehand resulted in a very small file being downloaded. (260kb or so). And yes, this happens to XP Pro and Home as well as Vista.
I'm a little confused - how is the 128MB of swap enabled if not through Maemo Control Panel? Are you saying that you've added something to the KDE install to automagically enable 128MB of swap for KDE? If so does this mean I can turn it off in Maemo (since I hardly use Maemo anyways)? Or is my set up going to be different because I'm dual booting?
Also, you can get all of the memory/CPU usage details in KMenu -> System -> KSysGuard (I couldn't get your xterm NOKIA:/ command to work). FWIW, I've used KSysGuard a lot in my experiments to attempt to find the optimal KDE set up for me.
