Samsung NC10 UK revision, Updates / Installation / Modding etc, stuff will be here Options

[vrozen]

@Timo1981


I tried your script. It sets the byte in the PCI device, and I can get its value, but sadly this has no effect on the brightness of my screen. I'm stuck using the 'shades' program Update: Hooray it works!!!

@MysticusC

Great forum, thx very much for your patience and NC10 Leopard tinkering

@All

I installed 2GB of Kingston Value RAM PC6400 (underclocked) memory (18 Euros) and I ordered a Dell 1490 in Honkong via ebay (15 Euros including shipping costs). The Dell 1390 they sent me works fine so far...

[RealRooster]

for 10.5.6 update, dsdt patch didnt seem necessary (rtc is working just fine looks like it?)

updating is easy, just download the 10.5.6 delta update. install, dont restart,
install nc10 update package with only nc10 selected (no need for update fix before restart!), it will bring back all the functions after restart

After the update I lost all output devices, so no sound at all at the moment.
I was using the test sound update, could that be a reason?

Are there other ones with sound problems?
Except the sound, everything else is working fine.

[vrozen]

I ran the manual 10.5.6 delta update and then (before rebooting) the NC10 1.1 installer. Everything is still working the way it was (including sound).

[ Mysticus C*]

After the update I lost all output devices, so no sound at all at the moment.
I was using the test sound update, could that be a reason?

Are there other ones with sound problems?
Except the sound, everything else is working fine.

have you tried to reinstall the test hda package again?

because that one is being replaced by update...

[RealRooster]

have you tried to reinstall the test hda package again?

because that one is being replaced by update...

Yep, that did the trick.
Now everything is working again. Thanks.

[ Mysticus C*]

Yep, that did the trick.
Now everything is working again. Thanks.

have you tried the mic jack? in input/second internal mic...? and if yes, how is it?

[G4-Flo]

Hey guys,

after updating to 10.5.6 I found out that the brightness is changing wether it's on battery or on cable.

If you start your NC10 with powercable or just wake up from sleep, you have the normal brightness.
But if you start with battery or wake up, the brightness is reduced just like on real macbooks in energysaving-mode.

Well, you can't adjust brightness and the brightness doesn't change if the NC10 is working and for e.g. you plug it on power, but it's cool that the brightness is changing anyway.

Maybe the we can adjust brightness one day by the functionkeys...

[mudzilla]

I too have updated to 10.5.6 with no problems, doing as Mysticus C* suggested, install update, re-install NC10 drivers.

Sound out thru speakers works fine, no new/other inputs or outputs are shown. I've not tried the patch yet.

Brightness of the screen does as posted above, if the power is removed during sleep, the screen is at half brightness when awakening.

[Flakk]

You are running xp on the NC10 currently? If you are then I'm just perplexed as it was my knowledge that xp runs upon NTFS which can handle 4gb+ filesize, and regarding your install partition that should be fat32 definately otherwise you will not be able to install osx on it at all. You should ideally have 4 partitions in total, 1) samsung recovery, 2) XP, 3) around 5-6gb for ddmac installation and 4) the remainder that you shall install osx onto. both the 3 and 4 should be fat32, however 3 should be a logical drive (shown how to do it in pages 4 through to 22 of the guide from the first post in this thread. - http://forum.insanelymac.com/index.php?showtopic=137314)
try that out and let us know how it goes.

just found the bookmark i used to help install it for me

http://forums.msiwind.net/mac/how-install-...-dvd-t4701.html

read that guide helps explain it.

Actually no joy. Can't get it to work. I found something about changing the partition type to 0xAF, which I tried but it didn't help. Does anyone have any ideas?

thanks for any help.

[rudog]

Hi Mysticus, I've just tried to go upto 10.5.6 and now get a Chain Booting Error on selection of OSX in boot menu
Is there any way to recover from this?

[srcshelton]

I decided to take the plunge and install the 10.5.6 update (stop sniggering, you there at the back!) and predictably it wasn't quite plain sailing:

Wifi still works, Graphics is now no longer set to full brightness (which is an improvement), a customised SystemConfiguration is no longer needed for battery information to appear (hurrah!).

The downside is that, as a few people have touched on so far, PS2 is broken. I have tried both ApplePS2Controller.kext and AppleACPIPS2Nub.kext, and neither load correctly.

Fixed it... whilst 10.5.5 is happy with AppleACPIPS2Nub or ApplePS2Controller, 10.5.6 requires both kexts to be active at the same time - with both loaded, everything is fine!

Additionally, 10.5.6 no longer seems to require a custom SystemConfiguration bundle in order to access battery information so it is now possible to run OSX with custom kexts loaded from an EFI partition without changing anything from the installation on the main partition.

[srcshelton]

I've written a little script to interface "reggie_se" which in turn is used to set display brightness. I'm running a retail install on my NC10 so I had to look a bit deeper into the method posted by RealRooster.

Please feel free to download & try.

Hmm - when I run this on 10.5.6, reggie_se returns "ERROR: no target device specified". Running 'sudo reggie_se -D PCI -i 16 -r -a 0xF4 -B 8' results in the same error.

(This may be because I've disabled the on-board LAN adapter in the BIOS, which may be shuffling PCI devices around... might this affect the value '16'? How was this value originally determined?

[tiomo1981]

Stuart, you're right. Disabling your on-board would probably change the order of device numbers.

In order to find out your right device number run:

CODE

sudo reggie_se -D PentiumM -x

Which will give your the following output:

CODE

. 4.6.1 (227)

PCI Devices
  0. Host PCI bridge: AppleACPIPCI (0:0:0:0)
  1.  VGA-compatible controller: GFX0 (0:0:2:0)
  2.  Multimedia device: HDEF (0:0:27:0)
  3.  PCI-PCI bridge: RP01 (0:0:28:0)
  4.   Network controller: PXS1 (0:2:0:0)
  5.  PCI-PCI bridge: RP03 (0:0:28:2)
  6.   Ethernet controller: PXS3 (0:3:0:0)
  7.  USB UHCI controller: USB1 (0:0:29:0)
  8.  USB UHCI controller: USB2 (0:0:29:1)
  9.  USB UHCI controller: USB3 (0:0:29:2)
10.  USB UHCI controller: USB4 (0:0:29:3)
11.  USB2 EHCI controller: USB7 (0:0:29:7)
12.  PCI-PCI bridge: PCIB (0:0:30:0)
13.  PCI-ISA bridge: LPCB (0:0:31:0)
14.  IDE controller: SATA (0:0:31:2)
15.  SMBus controller: SBUS (0:0:31:3)
16.  Display controller: display (0:0:2:1)
17.  Host PCI bridge: pci8086,27ac (0:0:0:0)

You are looking for the number of "Display controller: display". Change the device number in the script to this number and it should work.

[RealRooster]

I've written a little script to interface "reggie_se" which in turn is used to set display brightness. I'm running a retail install on my NC10 so I had to look a bit deeper into the method posted by RealRooster.

Thanks for the script, good work indeed.
I made two additional scripts in order to use your script for increasing (set + 25) and decreasing (set -25) the brightness level and assigned those to the arrow keys by using Quicksilver application's triggering method. Now I can adjust the brightness by keyboard shortcuts and it works like a charm.

Of course the brightness level adjustment is not showed on the HUD as it is with the volume control, but this is good enough for me (at least in this point).

[mudzilla]

Thanks for the script, good work indeed.
I made two additional scripts in order to use your script for increasing (set + 25) and decreasing (set -25) the brightness level and assigned those to the arrow keys by using Quicksilver application's triggering method. Now I can adjust the brightness by keyboard shortcuts and it works like a charm.

Of course the brightness level adjustment is not showed on the HUD as it is with the volume control, but this is good enough for me (at least in this point).

Brilliant. Mind sharing them, and how you tied them to Quicksilver? That'll do me fine for now!

[tiomo1981]

Thanks for the script, good work indeed.
I made two additional scripts in order to use your script for increasing (set + 25) and decreasing (set -25) the brightness level and assigned those to the arrow keys by using Quicksilver application's triggering method. Now I can adjust the brightness by keyboard shortcuts and it works like a charm.

Of course the brightness level adjustment is not showed on the HUD as it is with the volume control, but this is good enough for me (at least in this point).

Good thinking! That's actually exactly what I did. Almost like the real deal except for the display of the current brightness level.

Could people who updated to 10.5.6 please share which version of AppleIntelGMA950.kext & AppleIntelIntegratedFramebuffer.kext they're using?

The update brough version 1.5.36.25 and my old 10.5.5 drivers are 1.5.30 if I remember right. My NC10 doesn't want to wake up from sleep anymore and when clicking on the "Graphics" tab in System Profiler my NC10 crashes and I have to hold the power button to shut it down.

When I tried the new drivers it wouldn't load because of the missing device ID. I patched the drivers but I would get stuck on the blue screen (no cursor & no login window). Any help is greatly appreciated.

Thanks to Stuart's finding I have the keyboard & touchpad working.

There is also something that is slightly annoying me: 1 out of 3 boots the system would stop booting waiting for the boot media. I think it's related to AppleIntelPIIXATA.kext. Has anyone else ever had this issue?

I'm on a retail install using an EFI partition with efi_boot 6.1

[ Mysticus C*]

timo: it is a framebuffer issue

i did same things as you did, system in blue screen and stucks there though i know the system responds! because it shutdowns and keyboard works etc...it just doesnt bring the desktop...

if you use the framebuffer from my packages, you can use evertyhing just fine... but you will need to patch out the brightness issue again can be slightly trouble finding the 55 in the right place u ll need haglebeef's longer method but still trouble...

i m testing the 10.5.6 gma kext patched (binary and plist)+ fb from my packages (note that it is not my fb patch at all, i grabbed it from somewhere else... people dont give credit so i dunno who made it originaly, but guess maybe dense?)

==============================
UPDATE NEWS:
==============================
some help arrived from voodoo teams. They made working port of bsd drivers which works with 99% of current hda's in the market (claimed) and in current state: internal speaker working, headphone working, internal mic/line in is coded but disabled at the moment... I m invited to test drive, so will report back... As claimed within few weeks it will be equal to applehda driver

also asked dense if he can provide me the natit for the fb issue not spitting display out put (probably because of the display panel registy (i dont know the details but guessing it has to do with edid data that provides the display information) this issue is probably due to fb driver reading the edid data from display directly or feed by the efi issue? as in older fb driver in my package, i think it reads it directly from display, and probably changed to get it or fed by efi?

[rudog]

Hi Mysticus, I've just tried to go upto 10.5.6 and now get a Chain Booting Error on selection of OSX in boot menu.
Is there any way to recover from this?

[rex41e]

Hey I just want to say a big thank you to all of you here. reading your posts have allowed me to install mac osx on my nc-10 and its the best thing that has ever happened to me. Mysticus keep up the work, your making the nc-10 become a beast. thanks.

[ Mysticus C*]

Hi Mysticus, I've just tried to go upto 10.5.6 and now get a Chain Booting Error on selection of OSX in boot menu.
Is there any way to recover from this?

delete your ddmac partition? and reapply it if you had ddmac earlier... update should not cause that kind of error though...