February 4, 2009 at 9:52 am #160982jezMember
Ive started a Linux Faq thread here.
As I’m not a user I wondered if anyone could point out a few useful threads or questions (and the answer!) that should be in it?February 4, 2009 at 11:34 am #182458AlfiharParticipant
The first thing I thought of, (which actually applies to Windows and any other OS’s as well) is that the NC10 has a 32bit processor and so can only run 32bit operating systems.
If you are downloading/installing a Linux distribution make sure it’s the 32bit version.February 22, 2009 at 7:11 pm #182457XyroxMember
What doesn’t work?
This vary a bit depending on which distribution you use, but generally these seem to be the common problems:
– Fn keys don’t work. Some keys, such as Fn-Up/Down to adjust brightness, don’t send a signal when released thus appearing as if they’re held down all the time.
Workaround: For the time being, you can use another keyboard shortcut (for example Win-Up instead of Fn-Up).
Fix: This is fixed in recent kernel releases.
– Still, some Fn keys don’t work, including Backlight toggle. WiFi toggle and power profile toggle.
Workaround: You can write your own script to switch on/off wireless and/or bluetooth.
Fix: A fix to toggle the wireless on/off might be included in the kernel. More information here.
– Speakers aren’t muted when you plug in headphones.
Fix: Fixed in newer versions of ALSA.
Hm, I guess that’s it. I can’t get multitouch to work either, but I don’t know if I’m alone or if it’s a common problem.
Other Linux users – please correct me if anything is wrong, and feel free to add anything to the list that I’ve missed.
jez – you can use the text as it is if you want, but you probably want to refine it since my English.. well, guess I don’t even have to explain. =PFebruary 23, 2009 at 10:14 am #182456jezMember
Thanks Xyrox. I’ll see if anyone else comments and then add this in 🙂February 23, 2009 at 10:17 am #182460TCMuffinMember
The wireless adapter doesn’t work out of the box with Ubuntu 8.10, but does with the beta release of 9.04.February 28, 2009 at 5:04 pm #182459AlfiharParticipant
Just thought of a rather obvious one (well two) to add:-
1) Never run a command if you don’t know what it does.
Always be cautious when someone tells you to run a command or download and run a script. Especially if told to run it as root.
2) If you want to find out what a command does you can view the man pages by entering “man”, space, and then the name of the command. For example:-Code:man ls
This will display information on the “ls” or list directory command. Press Up and Down to scroll, q to exit.
- You must be logged in to reply to this topic.