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

[Leonardo]

for Dell 1490 with XP:

- download driver and NOT run Setup.exe; u must install driver by Control Panel -> System etc etc and select c:\dell directory

Ok, then I have a problem. The new revision of GMA950 driver have artifact with external VGA display... Mysticus can you post old pkg from 1.0 installation package?

[jay zee]

Hi Mysticus C* and all other contributors,

happy new year and a big THANKS! to all of you - here's one happy camper that, using your work, managed to run 10.5.6 on his NC10.

Let me quickly add to this thread and describe how I managed to set everything up and where I'm at right now.

1. Initial install
I used msiwindosx.iso to install 10.5.4 using the ddmac method. This worked out of the box using the default settings. One thing that was great back then was that it had the resolution (1024x600) right up front.

2. Apple setup loop
yes, I saw it, too :-) After doing some research I can confirm from my observations that apple setup expects *any* network adapter. If it doesn't find one, it simply restarts itself. If you have Bluetooth installed this means you have a network adapter and you probably won't see the problem. If you only have the stock NC10 WLAN & LAN interface, you're hosed. For me, it worked to boot into single-user mode (-s on the boot prompt, then fsck & mnt) and then touch /var/db/.AppleSetupDone -- this got me past all the setup hassle

3. WLAN
I spent way too many hours trying to get the stock WLAN card to work. Using the hints from many forums on the web I managed to get it working several times using a hacked Atheros kext and KisMAC to set the card into passive mode. In the end, however, this turned out to be more frustrating than anything else because it wouldn't work reliably. So I bought a random BCM4311-based card (checked eBay) and it worked out of the box. No need to mention that this got rid of the setup loop problem, too (see above).

To run the BCM4311 under XP I found this site and chose the latest driver package, installed it using the device manager and it just works.

4. Upgrade to 10.5.6
I screwed my previously installed 10.5.5 so I decided to do an upgrade straight from my clean 10.5.4 using apple's (fixed) Combo Updater and Mysticus C*'s install package (just make sure you install Mysticus' NC10 install *after* the Combo Update but *before* restarting). That worked perfectly fine. Digging through the posts I found the way to recover the trackpad prefpane by installing the trackpadfull installer from Mysticus C*'s rapidshare site. This also spared me so much trouble -- Mysticus, thanks again for making it so easy for us.

5. Display brightness
That was actually the killer app itself -- whoever went through the registers of the graphics card - nice work! Installed CHUD, Quicksilver and followed the setup guide to set up the brightness scripts. Using the latest NC10 updater, the newest brightness icons were already installed. While setting up the QS hotkeys I ran into the issue that the increase/decrease scripts timed out on me. Adding some debug dialogs I found that scripting the Keychain would fail and never return so I never got to the point where I could allow keychain access. The only thing that could fix this was to manually start the Keychain Scripting Access. Strangely I only had to do this once, upon the first run -- now everything works right after logging into the system.

6. BIOS update
Well *sigh* never change a running system. I did it anyway and upgraded to Samsungs 04CA BIOS and here's what I came up with.

6.1 EDB - I can confirm that the BIOS update magically disables the EDB to without any user intervention. So, whoever does the BIOS upgrade, you need to re-enter the BIOS and re-enable the EDB.

6.2 Brightness (again)
After the BIOS update, the brightness scripts wouldn't work anymore. So I toyed around with the reggie_se tool and found that the PCI Device IDs seem to have changed with the update. So, to re-enable the brightness scripts, simply change the PCI-Device ID in /Library/Scripts/change-brightness from 16 to 15 and adjusting the brightness will work again (see below for a remaining sleep-related problem)

CODE

# diff change-brightness change-brightness.mysticus
8c8
< PCIDEVICE=15
---
> PCIDEVICE=16

7. USB
USB mounting/unmounting works fine (besides the know issue that USB mounts wouldn't unmount before going to sleep). Also I use a HUAWEI UMTS stick which works just fine.

8. Sound
output works just fine (besides the known issue that the headphone out won't work although CHUD is installed). Thanks for the hint that one needs to change the output device in the sound pref panel from headphone to speaker manually! No luck with sound input though - I was hoping to be able to use Skype (the webcam works, too, btw!) but this is pointless if there's only one-way audio. Does anyone know about plans to port sound input (from the mic or line-in)?

9. Remote Disc
About having the NC10 use a remote disc offered by another Mac: I found these instructions on another forum -- after a reboot I had the remote discs back.

CODE

defaults write com.apple.NetworkBrowser EnableODiskBrowsing -bool true
defaults write com.apple.NetworkBrowser ODSSupported -bool true

10. Not working at all
* wired LAN - hopefully someone feels obliged to port the driver at some point
* sleep when on power (though I've read that it's a known issue it's not really a blocker -- I only need sleep mode when I'm without power)
* sound input (see above)

11. Still has me puzzled
* changing brightness after waking up *
After waking up from sleep, the display brightness is turned down. Changing the brightness again won't work anymore. Again I played with reggie_se and found that the display controller's PCI Device ID has changed to 14 - changing the script to write to ID 14 will then, of course, re-enable the brightness setting with Quicksilver. All subsequent sleep/waking cycles will leave the display controller device ID at 14.
Could this be related to the BIOS upgrade? Is there anyway we can have the display controller stick to the same PCI ID all the time? Or can we find the display controller by other means that won't change upon sleep?

* speedstep *
Is proper powermanagement in place? sorry for asking so bluntly but I think that the fan is blowing way more often than when I had the genericpowermanagement.kext in place (or when running XP, for that matter). Are there any issues with that? I would be curious to hear other's opinions - I've read adam's notes about power consumption but they went largely unnoticed.

* touch screens *
I'm tempted to get me a touch screen - I saw the offer from a seller on eBay - has anyone bought from them yet? And who has registered for the free giveaway yet?

* retrofitting bluetooth *
having a NC without bluetooth I'm thinking about retrofitting a module. I've seen some pretty whacky approaches at a german NC10 site where they do quite some soldering to get 5V from other parts of the mainboard so they can connect a disassembled module taken from a BT dongles. However, I'd like to use a module that would fit on the slot on the mainboard. Any hints who might sell those modules?

That's my 2c for today - thanks again to anyone who has contributed time and effort into this thread. This is a great project!

Cheers,
jay zee

[abirch]

for Dell 1490 with XP:

- download driver and NOT run Setup.exe; u must install driver by Control Panel -> System etc etc and select c:\dell directory

Ok, then I have a problem. The new revision of GMA950 driver have artifact with external VGA display... Mysticus can you post old pkg from 1.0 installation package?

Well shoot. I'm still having problems. I may or may not have installed the wrong 1490 drivers or something, but I can't get straight now. First thing I need to do is completely remove any old drivers. How do I do that?

Second, when I download the dell drivers from the link above (German site), I get a file called R202478.exe. When I run the .exe, it installs a folder called C:/Dell/Drivers and then the dell installer fails. OK, so then I go to Add Hardware Wizard and then when I go to "Have Disk" it asks me to navigate to the .inf file, so when I go to the Dell folder, there are 4 choices: Driver, Driver_jpn, Driver_row, and x64. Which .inf to I pick?

So anyway, thanks for the help, folks.

[DJKwai]

6. BIOS update
Well *sigh* never change a running system. I did it anyway and upgraded to Samsungs 04CA BIOS and here's what I came up with.

6.1 EDB - I can confirm that the BIOS update magically disables the EDB to without any user intervention. So, whoever does the BIOS upgrade, you need to re-enter the BIOS and re-enable the EDB.

6.2 Brightness (again)
After the BIOS update, the brightness scripts wouldn't work anymore. So I toyed around with the reggie_se tool and found that the PCI Device IDs seem to have changed with the update. So, to re-enable the brightness scripts, simply change the PCI-Device ID in /Library/Scripts/change-brightness from 16 to 15 and adjusting the brightness will work again (see below for a remaining sleep-related problem)

Jay Zee-
You are clearly way more advanced than I am on the programming side, but I thought I would let you know that I had updated the bios to 04CA before doing a complete msiwindos86x re-install and update to 10.5.6 and I had no EDB problem and the brightness script worked fine. (I had to reinstall after bricking the 10.5.5 upgrade and realized I only needed the 10.5.6 combo plus the mysticus fix).

[adamcarter]

Well shoot. I'm still having problems. I may or may not have installed the wrong 1490 drivers or something, but I can't get straight now. First thing I need to do is completely remove any old drivers. How do I do that?

Second, when I download the dell drivers from the link above (German site), I get a file called R202478.exe. When I run the .exe, it installs a folder called C:/Dell/Drivers and then the dell installer fails. OK, so then I go to Add Hardware Wizard and then when I go to "Have Disk" it asks me to navigate to the .inf file, so when I go to the Dell folder, there are 4 choices: Driver, Driver_jpn, Driver_row, and x64. Which .inf to I pick?

So anyway, thanks for the help, folks.

first you are just navigating to the enclosing folder. Pick driver, Driver jpn is japanese I think, and driver x64 is for a 64 bit processor or 64 bit XP/Vista which I am sure you are not running.

just pick the "driver" folder and it will find it just find.

[epinephrin]

hello folks,
i installed my dell dw 1490 today and it does not work right now.
How can i install the dw1490 card on mac os x?



hello folks,
i installed my dell dw 1490 today and it does not work right now.
How can i install the dw1490 card on mac os x?

[Bdogzzz]

Hi all...I would like to say thanks to everyone who has put so much time and effort into this project. I have successfully been running XP and OSX flawlessly because of all of the helpful information. I have been quiet for sometime as the knowlge base is very through in this post but I have a couple questions with DDMAC. I am using ddmac to dual boot OSX and it works great. My question is if I have to keep the NC10 OSX iso on my C: drive after it has been mounted to the bootable partion? I'd like to move the iso to an external hard drive if it is possible to free up space on my xp partition. Also is it possible to tripple boot using ddmac? I have a copy of windows 7b that I'd like to try out.

Thanks!

[adamcarter]

Hey mysticus or anyone around, I never tried my earphones port. but I did just now, doesnt work and yes I selected sound output as headphones...
Anybody know when voodoo is gonna release the driver version of gold

correction to your faq's numlock works, but led light doesnt when on thats all....and I can live with that.

[jay zee]

I had updated the bios to 04CA before doing a complete msiwindos86x re-install and update to 10.5.6 and I had no EDB problem and the brightness script worked fine. (I had to reinstall after bricking the 10.5.5 upgrade and realized I only needed the 10.5.6 combo plus the mysticus fix).

DJKwai,

thanks for your response - that's very interesting. Are you saying that the brightness scripts still work for you, even after you sent the NC10 to sleep and woke it up again?

Cheers,
jay zee

[srcshelton]

6.2 Brightness (again)
After the BIOS update, the brightness scripts wouldn't work anymore. So I toyed around with the reggie_se tool and found that the PCI Device IDs seem to have changed with the update. So, to re-enable the brightness scripts, simply change the PCI-Device ID in /Library/Scripts/change-brightness from 16 to 15 and adjusting the brightness will work again (see below for a remaining sleep-related problem)

CODE

# diff change-brightness change-brightness.mysticus
8c8
< PCIDEVICE=15
---
> PCIDEVICE=16

You could also try replacing that line with:

CODE

(( PCIDEVICE = $( sudo reggie_se -D PentiumM -x 2>&1 | grep "Display controller: " | cut -d. -f 1 ) ))

... which will cause the script to take longer to execute (because reggie_se has to interrogate the hardware each time the script is called), but has the benefit that it will always work, regardless of BIOS version or whether the machine has been put to sleep at any point.

[SilSha]

Hi,

I have installed this Distro and it works very good out of the box.
But I have a problem with the system-language.
If I set the language to german, the preferences and the finder are not set to german. Most options are in english and only a few are in german.
Other programms are ok.
I did not have this problem with iDeneb 1.3.
So what can I do?

[abirch]

Well, I've tried everything to get my Dell 1490 card working in XP. Tried several different drivers, uninstalling and reinstalling, etc. Every time, I get this message:

Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)

So I guess my options now are to reinstall windows XP or maybe get a different card (Dell 1390)?

[camdenbloke]

Well, I've tried everything to get my Dell 1490 card working in XP. Tried several different drivers, uninstalling and reinstalling, etc. Every time, I get this message:

Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)

So I guess my options now are to reinstall windows XP or maybe get a different card (Dell 1390)?

I recently bought a Dell 1505 from ebay and used the broadcom drivers mentioned a page or two back on this thread and it worked fine in XP, if that's any help.

[G4-Flo]

Hi,

I have installed this Distro and it works very good out of the box.
But I have a problem with the system-language.
If I set the language to german, the preferences and the finder are not set to german. Most options are in english and only a few are in german.
Other programms are ok.
I did not have this problem with iDeneb 1.3.
So what can I do?

Please read the thread, the solution is mentioned more than once!

[abirch]

I recently bought a Dell 1505 from ebay and used the broadcom drivers mentioned a page or two back on this thread and it worked fine in XP, if that's any help.

Can someone check their driver for a definitive driver version that works? Thanks.

[SilSha]

Please read the thread, the solution is mentioned more than once!

Sorry I found nothing.
Can you point out the right posting for me.
Thx.

[-benir]

@SilSha

take a look here!

[SilSha]

Thx

I will try it.
I was a bit confused, because I found a lot of different german language packges and I did not know which one is the best to use

[G4-Flo]

Thx

I will try it.
I was a bit confused, because I found a lot of different german language packges and I did not know which one is the best to use

Try the link benir posted. It can never be wrong to use the latest one.

[jay zee]

CODE

(( PCIDEVICE = $( sudo reggie_se -D PentiumM -x 2>&1 | grep "Display controller: " | cut -d. -f 1 ) ))

sweet idea - could've come up with that myself =8) Anyway, I was figuring that this would be fighting the symptoms so I compared the output of reggie_se -x before and after the first sleep. Here's the sdiff, dump1 being before, dump2 after sleep:

CODE

nc10:~ jzee$ sdiff  dump1 dump2
. 4.6.1 (227)                            . 4.6.1 (227)

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

... meaning that somehow the OS loses grip of PCI-bridge RP01?

Does anyone have a clue why this could be? It 100% reproducible on my machine. Thanks for any hints!

Cheers,
jzee