Linux On My Samsung

'kadrach' pid='375' dateline='1237130156' wrote: I did not try your packages but your guides on jaunty - using (several) atkh5 versions, I was able to load a driver and find networks, but never able to connect (syslog: timeout for dhcpdiscover).

I am also experiencing quite a lot of kernel panics, no idea why.

I've just installed jaunty on another partition to test it, and I'm unable to use the latest 'linux-backports-modules'. I got lot of errors in my dmesg when trying to load the ath5k module, I think there something wrong on the deb package that needs to be fixed (after all, it's all a work in progress). I'll test again in a few days.

'kadrach' pid='375' dateline='1237130156' wrote: Another thing: What would be the best way to disable automatic loading of BT/Webcam modules? Currently, they're always on after boot, and I have to disable them after every reboot. Rather than doing so, I'd like to have to specifically enable them.

You can add the modules into the /etc/modprobe.d/blacklist file, in order to avoid them to be loaded at boot time.
Open the file in your editor and paste these lines in it:

Many thanks for maintaining this repository. This made my setup a great deal easier on my new NC10. Cheers!

Hi'
Works great with Gnome, but is there any way to make it as great with Kubuntu ?
/Ib

Hi, I'm sure thats possible

Right now, voRia's packages contain key mappings for metacity (.gconf key bindings, anyway). If you install the packages from the repository and remap the keys in KDE, it should work just fine (If hotkeys in KDE4 are fixed, haven't checked in ages). Also, the KDE4 compositor had performance issues in early versions, not something you want on a netbook

There is no differences between ubuntu and kubuntu packages, so I don't see why they should not work (apart for any KDE bug that I'm not aware of)... to be sure, If anyone tests the repository with kubuntu let us know how it works.

As kadrach said, you can use the scripts but you will have to manually map them to combination keys.

Thank's for the reply's.

Tried it on KDE 4.1 and KDE 4.2. Fresh installs. No succes.

So I have been testing :-)
Not tried the Metacity trick, but will.

I'l be back !

BTW: Have absolutely no performance degrading in KDE 4.2.
Think KDE is more organized on small screens, but havent used it since SuSE 9.

Done many installs on the NC10 (first week):
XP(1), Windows 7(2), Ubuntu(2), Kubuntu(4)

What kind of problems do you have with kde? what is working and what is not? (FN keys, audio, thouchpad, etc)

List of working Fn-keys:
+Esc
+F6
+F10
+F11
+PgUp
+PgDn
+Left (volume down)
+Right (volume up)

So prettymuch the same, as with standard Ubuntu, without your repos... :-)

Hmmm...
Saturday 16:00
Done openSUSE 11.1: That was an awful experience..
Nothing worked, and it dreadfully slow !!!

Right now, I'm trying LinuxMint...
Working Key's are like shown up above !

---
Saturday 20:54
Having found out, how to ad repo's and souch in Mint, I upgraded with you'r repos.
Brightness now works !!!

And thats all, that happened extra.
Other Fn-key's are like shown above.

---
Have to admit, that I'm about to go back to Kubuntu.
I still prefer it on a small screen like on the NC10.
But Mint is really so much better than regular Ubuntu, when it comes to menu organisazition. Ubuntu should pick them up, seriously.
And then the colors...
Mint's got more style.

Anyhow, I'm going back to Kubuntu.
Killing all power savings, so that screenbrightness is at a constant max.
Then time, hopefully works for me, as I'm not quite sure how to begin solving the problem myself...

'MrPingo' pid='508' dateline='1237564073' wrote: List of working Fn-keys:
+Esc
+F6
+F10
+F11
+PgUp
+PgDn
+Left (volume down)
+Right (volume up)

So prettymuch the same, as with standard Ubuntu, without your repos... :-)

Nice to know... then you can try to install the 'nc10-scripts' package from my repo, then manually bind the included scripts to the respective keys.

I'l do that.

The included filelist (.sh) is:
usr/bin/cputemp.sh
usr/bin/btonoff.sh
usr/bin/wconoff.sh
usr/bin/wlonoff.sh
usr/bin/cpuscaling.sh
usr/bin/lcdonoff.sh
usr/share/
usr/share/gconf/
usr/share/gconf/defaults/
usr/share/gconf/defaults/10_nc10-scripts

Do they all require tweaking

Just looked in the Mint, and no of the files seems to exist....(?)

Well, installing Kubuntu know and giving it a try.

What you actually need is the lcdonoff.sh script (for enabling the FN-F5 key) and the wlonoff.sh script (for enabling the FN-F9 key). All the other scripts are less important or not important at all, so you can avoid them.

The lcdonoff.sh and wlonoff.sh scripts does not need any tweaking, they should just work on KDE too. All you need to do is to copy them somewhere (my advice is /usr/local/bin), then bind them to the respective keys. I don't know how to do that in KDE but I think there should be an option in system preferences to do that.

For the FN-Up and FN-Down keys I don't know why they don't work with KDE. Both keys are correctly mapped from HAL, so I think it's a KDE related problem, not only for NC10.

I'm starting to work on Ubuntu Jaunty and I'm adding various packages on my repository.
The instructions to use it are the same as for Intrepid, the only difference is that these lines must be used: I would appreciate feedbacks from the users that will use it.

Hi, first I have to tell you how wonderful is your job on our sammy !
Thanks a lot for this !

I'm running a dual boot XP / Jaunty.

I have installed your jaunty packages.
Honestly, i'm a real noob on Ubuntu (and on Linux), so I didn't notice any changes.
And the only package which seems helpful in my case (the nc10-scripts with wifi and BT oN/off, processor downclock etc) doesn't exist (yet?).

So i'm a bit disapointed, but if you want me to try something to help you upgrading your jaunty package, pm me, i'll be glad to help.

Cya

Welcome

The nc10-scripts package for jaunty is on my repository, are you sure that the repository was correctly added and enabled?
You can follow the instructions on the main post, the only difference is that you have to use these lines instead: