2009년 5월 31일 일요일
2009년 5월 29일 금요일
Linux에서 사운드 카드 코덱 덤프 받는 방법
alc888_dump.txtUbuntu나 페도라등 리눅스에서 사운드카드 코덱 덤프 받는 방법입니다.
Linux로 부팅하고 난 후, 다음과 같은 명령어를 입력합니다.
<code>cat /proc/asound/card0/codec#1 > ~/Desktop/codec_dump.txt
</code>
2009년 5월 28일 목요일
GTX시리즈 드라이버가 나왔군요.
GTX-2XX 시리즈 드라이버가 드디어 만들어 졌습니다.
GTX-260은 테스트 점검이 끝난 상태이지만, 타 시리즈도 될 수 있게 만들었다는 것이 개발자의 설명이었습니다.
하지만, 이 드라이버를 만들고 난 후 차후의 지원요청에 따른 부담감 때문에 드라이버 개발자가 공개하기를 꺼려하고 있습니다.
다만, 가까운 친구들에게만 공개를 하고 있습니다.
어쨌든 nVidia 계열 GTX시리즈도 이제는 해킨에서 사용할 수 있다는 뉴스입니다.
Ubuntu 9.04를 이용한 Chameleon usb stick 만들기
First of all, I really appreciate Hagar,
If you have any question, visit his original posting and leave your question.
Source : http://www.projectosx.com/forum/index.php?showtopic=314&st=0&#entry1000
This posting is just for Korean who don't read English.
준비물:
- Ubuntu (live CD) 9.04 가 좋을 것 같군요.
- usb stick
- 그리고 인터넷 연결이 되어 있어야 합니다.
usb 를 먼저 꽂고
터미널에서, "sudo -s" 명령어를 입력하고 "pwd" 커맨드를 입력하여 마운트 경로와 현재 경로등을 확인합니다.
(보통 /dev/sdb 디바이스가 USB입니다만, 자신의 환경에 따라 다르고 USB 가 사용할 마운트 포인트는 LinOSX 라는 볼륨명을 이용할 것입니다.)
터미널에서 다음 명령어를 입력하세요.
CODE
fdisk /dev/sdb
기존 파티션을 제거하기 위해 새로운 주 파티션으로 생성을 하는데 타입은 "AF" 타입으로 해주시고, active 시킵니다.
다음과같이 mkfs.hfsplus 커맨드를 이용하여 새로운 hfs+ 파일시스템을 새로이 만듭니다.
CODE
mkfs.hfsplus -v LinOSX -U 0 -G 0 /dev/sdb1
보시다시피 LinOSX 볼륨명으로 권한은 사용자와 그룹이 "0:0" 으로 되어 있습니다.
다음은 chameleon bootloader를 설치하는 과정입니다.:
최신 chameleon 패키지를 다운로드하여 압축을 풉니다. 여기에서 Chameleon2.0RC1-r431
cd 커맨드를 이용하여 i386 들어가서 /dev/sdb1 디바이스가 언마운트되어 있음을 확인합니다. 그리고 다음 명령어를 입력합니다:
CODE
dd if=boot0 of=/dev/sdb bs=440 count=1
dd if=boot1h of=/dev/sdb1
dd if=boot1h of=/dev/sdb1
다음은 usb를 다음명령을 주어 마운트합니다.:
CODE
mkdir /media/LinOSX
mount -t hfsplus -w /dev/sdb1 /media/LinOSX
mount -t hfsplus -w /dev/sdb1 /media/LinOSX
그리고 다음과 같이 명령어를 줍니다. 아주 전형적인 방식이죠. ^ ^:
CODE
touch /media/LinOSX/arse
모두 처리가 잘 진행이 되었다면 이제 드라이버에 root 권한으로 쓸 수 있는 권한이 있습니다. 따라서,
2009년 5월 27일 수요일
New universal Injector for ati and nvidia, and multiple ati cards enabler.
New universal Injector for ati and nvidia, and multiple ati cards enabler.
source form Netkas : http://netkas.org/?p=104#comment-25268
This new kext, is natit 와 aty_init integrated 하나로 통합된 드라이버로서 주로 nvidia 그래픽 카드를 지원하며 특히, video 램크기를 읽어오는 부분을 좀 더 강화시켰습니다.
가능한 nvidia geforce8 시리즈 이상급에서 사용하시기를 권고합니다. 또한, ati cards의 램을 읽어오는 것을 지원합니다만, multiple cards를 위한 바이너리 추가는 진행하지 않았습니다.
MacPro ATI/Nvidia pc 카드 사용자들도 지원합니다. (예를들면, radeon 4890).
카드 상태는 아직 베타이지만, 동작은 잘 되지만 테스트가 필요합니다.
ati 이름으로는 부족하군요. 좀더 좋은 이름이 필요할 것 같은데 혹시 제안하실 거라도?
^ ^
nVidiaNATI Driver
2009년 5월 26일 화요일
Chameleon bootloader with SSDT and DSDT override
First of all, Thanks ab___73.
source : http://www.insanelymac.com/forum/index.php?showtopic=145792&pid=1163564&mode=threaded&start=#entry1163564
This posting will be translate to Korean, that's why ab_73's posting is in here for understanding who duuno english.
Update:
Upload of Release version 1 with source code.
boot1h 와 관련된 파일크기의 제약상 SMBIOS나 /Extras폴더와는 아직 호한이 안된다는 점을 유의해 주세요.
변경사항:
+ load upto 30 SSDT tables.
+ load extra additional SSDT tables.
+ ACPI v1 and v2 and v3 support.
+ source code refined.
SSDT 테이블을 올려주시면 많은 사람들에게 도움이 될것입니다.
가능하면 www.mediafire.com 에 올려주시면 되겠습니다.
다음 부트로더를 다운로드 받으세요.
ssdtboot_chameleon2.zip ( 314.39K ) Number of downloads: 500
Update:
30 SSDT tables을 로딩할 수 있게 소스코드를 수정하였다. 테스트 중에 있으며, 성공하면 이 bootloader 와 소스코드를 공개할 것입니다.tonight.
SMBIOS source code diff를 추가하는 부분에 있어 몇가지 이슈가 있는데, 부트파일의 파일크기 제한과 관련된 것 같군요.
만약 파일크기가 62000bytes 이하에서 bootloader를 운용하게끔 한다면 SMBIOS + DSDT + SSDT 패치를 62700bytes 까지 증가시킬 수 있을 것 같습니다. 부팅시에 /boot0 hang이라는 부팅에러를 겪었다면 이 부분이 해결될 수 있겠군요.
파일 크기 제한과 관련하여 어떤분이라도 좋으니 알고 있으신 분은...^ ^
왜 boot1h 가 단지 <64k boot 파일 이하로 로딩해야 하는 건지...알고 싶습니다!!
-------------------
아주 일반적인 chameleon DSDT override bootloader 를 수정하였는데, 이는 수정된 DSDT 와 SSDT 테이블을 로딩하기 위한 것입니다.
다음과 같은 이점이 있습니다:
+ 컴파일 에러를 이해하고 또, SSDT 테이블 내에서 가끔은 DSDT가 external methods를 레퍼런스 하기도 합니다..
+ Fix Powermanagement.
+ Fix PStates (CPU performance management)
+ Fix CStates (Power Saving managenent)
+ Fix TStates (CPU throttling)
+ View SATA controllers ACPI functions.
이 버전은 디버그 버전입니다. 곧 새로운 버전을 소스코드와 같이 발표할 것입니다.
Chameleon bootloader 와 DSDT 패칭 프로젝트에 관심 가져줘서 고맙군요.
이 bootloader를 이용할려면,
특정 폴더에 압축을 풀고.
Terminal 에서 해당 폴더로 이동합니다.
기존의 bootloader를 다음과 같이 백업합니다.
#sudo cp /boot /boot.bak
사용할 bootloader 를 다음과 같이 복사하여 줍니다.
#sudo cp ssdtboot /boot
SSDT 테이블을 추출하기 위해서는
터미널에서 압축을 풀어놓은 폴더로 이동하여 다음과 같이 실행합니다.
#./getSSDT5.sh
이 명령어는 다음과 같은 디컴파일된 SSDT 테이블을 생성합니다.
SSDT-0.dsl
SSDT-1.dsl
..
SSDT-4.dsl
SSDT Tables의 숫자는 하드웨어 숫자에 기인하므로 숫자에 연연할 필요는 없습니다
텍스트 에디터나 Text Mate를 이용하여 이 화일들을 열어서 수정합니다.
SSDT tables수정하였으면, 터미널에서 다음과 같은 커맨드를 입력하여 컴파일 하여 줍니다.
./iasl -sa SSDT-0.dsl
./iasl -sa SSDT-1.dsl
./iasl -sa SSDT-2.dsl
..
./iasl -sa SSDT-x.dsl
(where x is the table you wish to compile)
컴파일된 파일을 다음과 같은 명령어를 이용하여 최상위 디렉토리에 복사하여 줍니다.
#cp SSDT-x.aml /
(where x is the table you wish to copy)
이 bootloader 를 이용하여 재부팅하고 나면 이미 SSDT 테이블을 로딩하였을 것입니다.
DSDT와 관련하여 다음 글들을 참고합니다.
DSDT Patcher
DSDT BIOS Patcher
다음과 같이 Boot 옵션을 사용할 수 있는데 수정된 것을 사용하는 것 대신에 기본적인 oem SSDT 테이블을 로딩하기 위해 사용할 수 있습니다.
(Use this at darwin boot)
oemSSDT=y
voodoo kernel 에서는 boot 옵션을 다음과 같이 주어 동작되는지 확인하여 봅니다.
kprintf=1 -v
OSX로 부팅하였다면
터미널에서 다음과 같은 명령어를 입력합니다.
#sudo dmesg | grep ACPI
OEM SSDT 테이블 예:
수정 적용된 SSDT 예:
5라인의 변화를 유의하여 보면 (SSDT-4) e.g. 0x7f7f52a2/0x4D7 -> 0x1956000/0x051E
이 주소가 변화된 의미는 수정된 SSDT 성공적으로 로딩된 것입니다.
이제 SSDT 테이블을 공유하여 서로간의 정보를 공유하여 봅시다. www.mediafire.com 에 업로드하여 공유하면 될 것 같군요.
다음 화일이 도움이 될 것 같군요.
[attachment=42483:ssdtboot_chameleon.zip]
Cheers,
AB
Voodoo kernel :
voodoo kernel
ssdtboot_chameleon2.zip ( 314.39K ) Number of downloads: 500Update:
30 SSDT tables을 로딩할 수 있게 소스코드를 수정하였다. 테스트 중에 있으며, 성공하면 이 bootloader 와 소스코드를 공개할 것입니다.tonight.
SMBIOS source code diff를 추가하는 부분에 있어 몇가지 이슈가 있는데, 부트파일의 파일크기 제한과 관련된 것 같군요.
만약 파일크기가 62000bytes 이하에서 bootloader를 운용하게끔 한다면 SMBIOS + DSDT + SSDT 패치를 62700bytes 까지 증가시킬 수 있을 것 같습니다. 부팅시에 /boot0 hang이라는 부팅에러를 겪었다면 이 부분이 해결될 수 있겠군요.
파일 크기 제한과 관련하여 어떤분이라도 좋으니 알고 있으신 분은...^ ^
왜 boot1h 가 단지 <64k boot 파일 이하로 로딩해야 하는 건지...알고 싶습니다!!
-------------------
아주 일반적인 chameleon DSDT override bootloader 를 수정하였는데, 이는 수정된 DSDT 와 SSDT 테이블을 로딩하기 위한 것입니다.
다음과 같은 이점이 있습니다:
+ 컴파일 에러를 이해하고 또, SSDT 테이블 내에서 가끔은 DSDT가 external methods를 레퍼런스 하기도 합니다..
+ Fix Powermanagement.
+ Fix PStates (CPU performance management)
+ Fix CStates (Power Saving managenent)
+ Fix TStates (CPU throttling)
+ View SATA controllers ACPI functions.
이 버전은 디버그 버전입니다. 곧 새로운 버전을 소스코드와 같이 발표할 것입니다.
Chameleon bootloader 와 DSDT 패칭 프로젝트에 관심 가져줘서 고맙군요.
이 bootloader를 이용할려면,
특정 폴더에 압축을 풀고.
Terminal 에서 해당 폴더로 이동합니다.
기존의 bootloader를 다음과 같이 백업합니다.
#sudo cp /boot /boot.bak
사용할 bootloader 를 다음과 같이 복사하여 줍니다.
#sudo cp ssdtboot /boot
SSDT 테이블을 추출하기 위해서는
터미널에서 압축을 풀어놓은 폴더로 이동하여 다음과 같이 실행합니다.
#./getSSDT5.sh
이 명령어는 다음과 같은 디컴파일된 SSDT 테이블을 생성합니다.
SSDT-0.dsl
SSDT-1.dsl
..
SSDT-4.dsl
SSDT Tables의 숫자는 하드웨어 숫자에 기인하므로 숫자에 연연할 필요는 없습니다
텍스트 에디터나 Text Mate를 이용하여 이 화일들을 열어서 수정합니다.
SSDT tables수정하였으면, 터미널에서 다음과 같은 커맨드를 입력하여 컴파일 하여 줍니다.
./iasl -sa SSDT-0.dsl
./iasl -sa SSDT-1.dsl
./iasl -sa SSDT-2.dsl
..
./iasl -sa SSDT-x.dsl
(where x is the table you wish to compile)
컴파일된 파일을 다음과 같은 명령어를 이용하여 최상위 디렉토리에 복사하여 줍니다.
#cp SSDT-x.aml /
(where x is the table you wish to copy)
이 bootloader 를 이용하여 재부팅하고 나면 이미 SSDT 테이블을 로딩하였을 것입니다.
DSDT와 관련하여 다음 글들을 참고합니다.
DSDT Patcher
DSDT BIOS Patcher
다음과 같이 Boot 옵션을 사용할 수 있는데 수정된 것을 사용하는 것 대신에 기본적인 oem SSDT 테이블을 로딩하기 위해 사용할 수 있습니다.
(Use this at darwin boot)
oemSSDT=y
voodoo kernel 에서는 boot 옵션을 다음과 같이 주어 동작되는지 확인하여 봅니다.
kprintf=1 -v
OSX로 부팅하였다면
터미널에서 다음과 같은 명령어를 입력합니다.
#sudo dmesg | grep ACPI
OEM SSDT 테이블 예:
CODE
ACPI: SSDT @ 0x7f7f4440/0x0024 (v001 HP HPQNLP 0x00000001 MSFT 0x0100000E)
ACPI: SSDT @ 0x7f7f4464/0x0326 (v001 HP HPQSAT 0x00000001 MSFT 0x0100000E)
ACPI: SSDT @ 0x7f7f4f9d/0x025F (v001 HP Cpu0Tst 0x00003000 INTL 0x20060317)
ACPI: SSDT @ 0x7f7f51fc/0x00A6 (v001 HP Cpu1Tst 0x00003000 INTL 0x20060317)
ACPI: SSDT @ 0x7f7f52a2/0x04D7 (v001 HP CpuPm 0x00003000 INTL 0x20060317)
ACPI: SSDT @ 0x7f7f4464/0x0326 (v001 HP HPQSAT 0x00000001 MSFT 0x0100000E)
ACPI: SSDT @ 0x7f7f4f9d/0x025F (v001 HP Cpu0Tst 0x00003000 INTL 0x20060317)
ACPI: SSDT @ 0x7f7f51fc/0x00A6 (v001 HP Cpu1Tst 0x00003000 INTL 0x20060317)
ACPI: SSDT @ 0x7f7f52a2/0x04D7 (v001 HP CpuPm 0x00003000 INTL 0x20060317)
수정 적용된 SSDT 예:
CODE
ACPI: SSDT @ 0x7f7f4440/0x0024 (v001 HP HPQNLP 0x00000001 MSFT 0x0100000E)
ACPI: SSDT @ 0x7f7f4464/0x0326 (v001 HP HPQSAT 0x00000001 MSFT 0x0100000E)
ACPI: SSDT @ 0x7f7f4f9d/0x025F (v001 HP Cpu0Tst 0x00003000 INTL 0x20060317)
ACPI: SSDT @ 0x7f7f51fc/0x00A6 (v001 HP Cpu1Tst 0x00003000 INTL 0x20060317)
ACPI: SSDT @ 0x1956000/0x051E (v001 HP CpuPm 0x00003000 INTL 0x20080926)
ACPI: SSDT @ 0x7f7f4464/0x0326 (v001 HP HPQSAT 0x00000001 MSFT 0x0100000E)
ACPI: SSDT @ 0x7f7f4f9d/0x025F (v001 HP Cpu0Tst 0x00003000 INTL 0x20060317)
ACPI: SSDT @ 0x7f7f51fc/0x00A6 (v001 HP Cpu1Tst 0x00003000 INTL 0x20060317)
ACPI: SSDT @ 0x1956000/0x051E (v001 HP CpuPm 0x00003000 INTL 0x20080926)
5라인의 변화를 유의하여 보면 (SSDT-4) e.g. 0x7f7f52a2/0x4D7 -> 0x1956000/0x051E
이 주소가 변화된 의미는 수정된 SSDT 성공적으로 로딩된 것입니다.
이제 SSDT 테이블을 공유하여 서로간의 정보를 공유하여 봅시다. www.mediafire.com 에 업로드하여 공유하면 될 것 같군요.
다음 화일이 도움이 될 것 같군요.
[attachment=42483:ssdtboot_chameleon.zip]
Cheers,
AB
Voodoo kernel :
voodoo kernel
Blogo 1.2.7
Blog 1.2.7
- 블로깅을 위한 Off-Line Editor.
작지만 강력한 툴인것 같군요.
임시로 사용을 해보고 있습니다.
그동안 Ecto를 사용하여 왔었는데 Ecto보다는 조금 더 간단하다고 해야 하나 블로깅을 위해서 갖출것은 다 갖춘 소프트웨어인 것 같군요.
10.5.7로 업그레이드한 후 X11 행걸릴때
X11 행업될때
10.5.7 로 업그레이드한 후에 세개 모두의 화면이 회색배경으로 채워지고 맥윈도우즈나 메뉴에 접근할 수 없는 문제가 생기게 된다.
이런경우는 원격으로 접속혹은 명령을 내려서 X11 을 Kill 명령어를 사용하여 다운시킨다.
그리고 "~/Library/Preferences/org.x.X11.plist" 화일을 열어서 "rootless" 키가 체크되지 않았는지 여부를 확인한다.
만약 체크되지 않았다면 체크하고 plist화일을 저장하면 해결될 것이다.
10.5.7 로 업데이트 되면서 이 값을 리셋하는 것 같다.
그리고 난 후 X11 root mode에서 command-shift-a toggles 을 이용하여 root 모드와 rootless modes로 스위치하여 본다.
2009년 5월 25일 월요일
텍스트 큐브와 티스토리(?)
|
2009년 5월 24일 일요일
Mac Os X on P5E + 8800GT and Q6600
First of all, thanks drmando for this Guide.
Mac Os X on P5E + 8800GT and Q6600ALL YOU NEED IS IN THIS FILE: http://rapidshare.com/files/86007773/drmando.rar
The Bios-Setting
1. AHCI Enabled
If windows vista is already installed you will first have to boot into vista and go to your windows directory and open de regedit.exe. Then go to HKEY_LOCAL_MACHINE\Sysyem\CurrentControlSet\Services\Msahci and change the Start property to "0"
2. Execute disable function = enabled
3. ACPI2 support = Yes
4. Intel speed step = disabled
Now you are ready to install.
The Installation
I used the KALYWAY image to base my installation on
My system:
SATA HD Spinpoint Samsung 500GB
-)2partitions a OSX of 200
Data of the rest
SATA DVD-RW Lite-on 20x
ASUS P5E with an X38Chipset … see asus.com for entire hardware list.
2GB RAM GEIL
NVIDIA 8800GT OC MSI
After having done the bios settings I put in the cd of MAC OS X. I pressed F8 for installation options and put in a "–v" to have terminal view instead of white apple screen in witch you cannot see errors. Loading the GUI of the installation may take a while.
The GUI has loaded, and asks for your languague, choose one and continue. Now go to utilities -) Disk utility and format partition your HD to your will. Be sure to have a Journaled partition as OSX requires one to install onto the rest of the partitions you may choose like HFS or whatever other format you like.
Install the vanilla kernel with patch leave other options for what they are may only cause crash.
Complete the setup and reboot and remove the CD.
WARNING if after reboot you have error 0b NO WORRIES, its just that your partition is not active (YET) in that case just leave the DVD in it and let it time out and you will boot into leopard.
OSX now loads continue till registration then hit windows sign and Q to skip it.
OSX after installation
This is were the tricky part starts. First you have to fill in some info until you come at the registration form. Just press CTRL+Q (some keyboards WIN+Q or ALT+Q) to skip the registration. Mac Os X setup is now complete but graphics are standard, no sound an no networking device!
Solutions follow!
The network adaptor (IF IT'S NOT WORKING YET)
I started with the network adaptor. For my motherboard I need to find the kext or make the kext for a Marvell Yukon 8056 type. There is none … no problem I fix it!
You will need to download following file from rapidshare or from my zip file. gigabyte_ds3-4pack.1.2.dmg wich has the 8053 version of my chip included. I will use that one to make mine. Install the package and then reboot.
Go to the terminal and type following commands:
CODE
cd /System/Library/Extensions <-- changes directory
sudo nano IONetworkingFamily.kext/Contents/PlugIns/AppleYukon.kext/Contents/Info.plist <-- edits file
(find and change: <key>Yukon-88E8053</key>)
(to: <key>Yukon-88E8056</key>) <-- change "53" to "56"
(find and change: <string>Yukon Gigabit Adapter 88E8053</string>)
(to: <string>Yukon Gigabit Adapter 88E8056</string>) <-- change "53" to "56"
(find and change: <string>0x436211AB</string>)
(to: <string>0x436411AB</string>) <-- change "62" to "64"
(press Control-O) <-- saves changes
(press Y and Enter) <-- accepts saving to existing file
(press Control-X) <-- exits nano
sudo chown -R root:wheel IONetworkingFamily.kext <-- repairs permissions
cd /System/Library <-- changes directories
sudo rm -rf Extensions.mkext Extensions.kextcache <-- rebuilds kextcache on reboot
I have had a lot of problems finding the right commandline for the file. If the file is empty its not the right one!!! Google a bit and look around for different variations. These lines worked for me. IONetworkingFamily.kext/Contents/PlugIns/AppleYukon.kext/Contents/Info.plist
Once Opened you will have to change the file like stated above using the CTRL+… key for controlling the edit program with controls stated downside in the box.
Reboot and network will work.
The VGA
I have a 8800 GT OC 512 version of MSI. I looked around on the net and found out this was the easiest of all
Just install the 10.5.2_NVkexts+.pkg included in my zip
The Audio
!UPDATE! ONLY THE BLUE EXIT LINE 2.1 SOUND !!!!
Take the AzaliaAudio.pkg from my zip and install it. Then run following command lines.
Step 1: (backup if you want too) Delete AppleHDA.kext:
sudo rm -rf /System/Library/Extensions/AppleHDA.kext
Step 2: Edit AppleAzaliaAudio.kext for matching codec's proper ID:
sudo nano /System/Library/Extensions/AppleAzaliaAudio.kext/Contents/Info.plist
goto Realtek ALC880/ALC860 Codec Driver key & change the <string> to
<string>0x11d4198b</string>
ctrl + O to save ctrl + X to quit
Step 3: Edit AppleAzaliaController.kext for matching ICH9R HDA interface proper ID:
sudo nano /System/Library/Extensions/AppleAzaliaAudio.kext/Contents/PlugIns/AppleAzaliaController.kext/Contents/Info.plist
find <key>IOPCIPrimaryMatch</key>
change the <string> to
<string>0x293e8086</string>
Step 4: Refresh kext caches
sudo rm /System/Library/Extensions.kextcache
kextcache -k /System/Library/Extensions/
Step 5: Disk Utility>Repair Disk Permissions
Step 6: Reboot
WARNING: in step 4 it might not succeed I just went to that directory and cleared the cache map myself restored my disk and rebooted and it worked fine.
YOU HAVE SUCCEDED!!
Congratulations!! You have successfully done what I have.
Hope this info was handy based mine on lots of posts trough the net, many thanks to those people.
!UPDATE!
I can see from my RS account that my file gets downloaded many times, plz leave some feedback so i can work on fixes. thank you!!
!UPDATE!
Stellar Phoenix Macintosh v3.5
최근에 우분투를 설치할 일이 생겨 여분의 하드디스크를 장착하고 우분투 설치를 하였다.
그런데, 내가 지정한 하드디스크에 설치하는 것이 아니라 순식간에 다른 하드디스크에 설치를 자동으로 해버린것이 아닌가?
더군다나 오랫동안 DSDT 매뉴얼 작업을 해오던 디스크를 날려 버리다니,,,,
분명 두세번의 디스크 확인 작업과정을 거쳤건만.....
어쩔 수 없이 Stellar Phoenix Macintosh로 복구작업을 시작하였다.
물론 이전에 Data Rescue나 Tech Tools를 사용하여 보았지만 효과가 없었다.
Adium
스카이프 AOL, 야후, MSN, FACEBOOK, GTALK, Nateon 을 한 어플리케이션에서 한꺼번에 관리를 할 수 있군요.
거기다 irc 채팅까지 ......
참, 한가지더 Skype 까지 지원이 되죠?
메신저 종합선물세트이군요.
Adium 1.4 beta support Twitter, IRC
Twitter, IRC 를 지원하는 Adium 1.4 beta 가 나왔군요.
FaceBook, .me, AOL, MSN, Yahoo, Gtalk 를 지원한지는 오래이지만, 이번에 나온 베타버전에서는 트위터와 irc까지도 지원하는 군요.
The popular open-source chat client gains support for two much-requested services, a host of other changes and fixes, and a line drawn in the sand for Tiger users.
다음에서 다운로드 받으시면 됩니다.
2009년 5월 23일 토요일
Fat32에서 MAC Journaling으로 파티션 변환하는 방법
하나의 하드디스크에 윈도우즈와 MAC OSX를 설치하려면 어쩔수 없이 MBR 파티션을 이용할 수 밖에 없지만 권장할만한 사항은 아닙니다.
왜냐하면 차후에 GPT+ GUID 방식이 아니라 MBR 파티션 방식이면 이것저것 걸리는 사항이 많더군요. 이를테면 디스크 이미지를 이용한 설치는 Osinstall.Mpkg 등을 수정하여야 MBR 파티션에 설치해야하는등 아픔이 많다.
하지만, 많은 사용자들이 하나의 디스크에 파티션을 나누어 안타깝게도 윈도우즈와 MAC OSX를 설치하여 멀티부팅을 하는게 현실이다.
이러한 경우 윈도우즈에서 FAT32로 파티션 한 다음, 다음그림과 같이 파티션을 설정하여 주면 된다.
설치 DVD등으로 설치 과정에 진입하면 설치할 파티션이 제대로 설정이 안 될 경우가 있다.
이런 경우 다시 한번 MAC Journaling으로 파티션으로 변환하는 방법중의 하나가 그림과 같은 방법이 될 것이다.
설치 과정중에 상단 메뉴의 utility에서 disk utility를 선택하여 다음과 같은 그림으로 진행하면 된다.
2009년 5월 22일 금요일
[謹弔] 노무현 전 대통령 서거! 슬픈 하루입니다.
뭐라 형언할 수 없는 날이군요.
역사상 그나마 깨끗했고 서민적인 분이셨었는데 안타깝습니다.
그날 이후로 많은 일들이 발생하는 군요.
Ubuntu Jaunty Installation Guide for HD 3650 pcie
The Alternatives
Users with ATI cards basically have these options:
- Open Source Drivers These are stable and nice, but currently have poor 3D performance, if any. If you have a Radeon X1k product or earlier, this is your only option.
- The Ubuntu Way Use the restricted-driver management system that comes with Ubuntu to install the drivers.
- Third (Fourth?) Party Installer Use envy/jockey or other installer helper.
- Install the drivers manually Using the installer downloaded from AMD's site via either package based install or direct install.
[edit] Open Source Drivers
By default, Ubuntu will already try to use one of the open source drivers for your hardware. If the feature set and stability work for you, then you don't need to change anything.
The drivers that may be used are
- vesa Lowest common denominator across all graphics vendor, not many features.
- ati Actually a facade that will invoke the radeon driver.
- radeon Driver support all radeon classes of hardware - with limited 3D for newer cards.
- radeonhd An alternate driver support R520 hardware and later.
By default there is no configuration file for X anymore, so X will try to do the right thing.
If you run into stability problems with 3D applications using the radeon/radeonhd drivers, consider trying a more recent kernel. mainline-2.6.29.3 did the trick on a few machines.
There's an ongoing debate about how and if the radeon and radeonhd drivers will be used in the future.
[edit] The Ubuntu way
[edit] Restricted Drivers Manager
- Ubuntu 9.04 (Jaunty) provides a notification saying that there are restricted drivers available
- Go to the Restricted Drivers Manager and enable the "ATI accelerated graphics driver"
- Ubuntu will then install and configure the driver for you
Note that you will be restricted to the drivers for you version of Ubuntu that Canonical deem as stable. This may not give you the latest drivers, but should be safest.
[edit] Installing the drivers manually
- PLEASE READ FIRST!
This portion of the guide works, since I have used it myself. I guess the rest of the guide is broken or it may be because the new driver doesn't support any of the older ATI cards anymore. Which cards does ATI no longer support? The ATI Radeon 9500-9800,X300-X2100,Xpress. See the complete list [1] here.If your card is on that list, you are restricted to the 9.3 driver - however since 9.3 driver doesn't support xorg-xserver 1.6, it will not work with Jaunty! This guide currently is for installing 9.4. !!!SO BE CAREFUL!!!
_______________________________________________
I recommend using copy and paste. However, you can Ctrl + C in your browser but you cannot Ctrl + V in the terminal. When you have copied something simply use Shift + Insert to paste into the terminal or go to the terminals menu, select edit and click paste. This method will ensure there are no typing mistakes and will greatly speed up the install process.
If you are using the x86_64 architecture (64 bit), be sure to install "ia32-libs" before proceeding!
Make sure universe and multiverse are enabled in your repository sources.
[edit] Before you start
Install the necessary programs
| Terminal Command |
|
sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++5 dkms |
[edit] 1. Download the latest Catalyst package.
Download page: Catalyst 9.4. This package contains both the 32-bit and 64-bit driver.
Open a terminal window and switch to the directory you downloaded the installer to. (Example: $ cd Desktop)
Make sure your directory path does not contain spaces
[edit] 2. Create .deb packages.
| Terminal Command |
|
sh ati-driver-installer-9-4-x86.x86_64.run --buildpkg Ubuntu/jaunty |
[edit] 3. Just in case
Write down or remember this series of Alt+PrntScr key combinations, just in case your screen should go black and Ctrl+Alt+F1 and Ctrl+Alt+Backspace doesn't work.
Alt+PrntScr+r, Alt+PrntScr+s, Alt+PrntScr+e, Alt+PrntScr+i, Alt+PrntScr+n, Alt+PrntScr+u, Alt+PrntScr+b
These keypresses will reboot the system safely. To remember the keypresses, remember this nonsensical phrase: "Raising Skinny Elephants Is Never Utterly Boring"
[edit] 4. Install .debs.
Install the debs, depending on if you're on a 32-bit or 64-bit system:
- For 32-bit systems
| Terminal Command |
|
sudo dpkg -i xorg-driver-fglrx_*.deb fglrx-kernel-source_*.deb fglrx-amdcccle_*.deb |
(This may fail due to a missing dpmk. If so install this first. Also check the version numbers (8.561) against the created debs)
- For 64-bit systems
| Terminal Command |
|
sudo dpkg -i xorg-driver-fglrx_*.deb fglrx-kernel-source_*.deb fglrx-amdcccle_*.deb |
Using tab completion can make this command easier.
[edit] 5. Additional 64-bit instructions
If you have a 64 bit install, the above dpkg command may complain that "Errors were encountered while processing: fglrx-amdcccle". This is because of a dependency of the amdccle package on 32 bit libraries. If you receive this error, issue the following command after the above dpkg command, which will force the installation of all of the 32 bit dependencies, and then the amdcccle package:
| Terminal Command |
|
sudo apt-get install -f |
Catalyst 9.4 on 64-bit systems requires the --force-overwrite command in the above dpkg command:
| Terminal Command |
|
sudo dpkg -i --force-overwrite xorg-driver-fglrx_*.deb fglrx-kernel-source_*.deb fglrx-amdcccle_*.deb |
Using tab completion can make this command easier.
[edit] 6. Generate a new /etc/Xorg.conf file
| Terminal Command |
|
sudo aticonfig --initial -f |
in a terminal. If it doesn't give an error you should be good.
[edit] 7. Force use of /etc/Xorg.conf file
Some people find that changes to xorg.conf don't get used by the driver. To force the ati driver to adopt changes made to xorg.conf, type the following command:
| Terminal Command |
|
sudo aticonfig --input=/etc/X11/xorg.conf --tls=1 |
[edit] 8. Test your installation
Finally, reboot the computer and type
| Terminal Command |
|
fglrxinfo |
into the terminal. If the vendor string contains ATI, you have installed the driver successfully. Release 9.4 looks like:
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Radeon HD 4800 Series (This line may be different depending on what graphics card you are using.)
OpenGL version string: 2.1.8591
Please note: Depending on the particular ATI card that you own, you may or may not automatically have all of the relevant driver features enabled. R500 and R600 cards (X1xxx, HD series, and newer) in particular will need TexturedVideo enabled in Xorg.conf (rather than the traditional VideoOverlay) in order to support Xv accelerated video playback.
[edit] HOW TO UPDATE DRIVER
To update your driver to a new version (say 9.3 to 9.4) first disable the current driver through Ubuntu's Hardware Manager or use EnvyNG to remove the driver, then go to synaptic and search for "xorg-driver-fglrx" without the quotes and mark it for "Complete removal" and hit "Apply" then reboot your computer. Now simply repeat steps #1, 2, 4 and finally run these commends in a terminal:
| Terminal Command |
|
sudo aticonfig --initial -f |
and
| Terminal Command |
|
sudo aticonfig --input=/etc/X11/xorg.conf --tls=1 |
then reboot.
It is very important that you COMPLETELY remove the old driver which includes the config files because when upgrading without uninstalling the old driver I noticed even though the new driver installed and worked there were some annoying problems that I experienced but after I completely uninstalled the driver then reinstalled it, it worked perfectly.
[edit] Tweaks
- Add tweaks as needed: http://ubuntuforums.org/showthread.php?t=849422
- Restart X, if it doesn't work, you can use the "vesa", "ati", "radeon" or "radeonhd" driver in the mean time, until you make it work.
- If you downgraded X to make fglrx work: enter synaptic, make sure all packages with "xorg" and "x11" are locked so that you can update and upgrade without worries.
Done! Now run amdcccle, glxgears, warsow etc :)
[edit] Issues
[edit] Installation
There are some system configurations on which none of the installation alternatives work with the latest 9.4 driver (please add; also please add if you got it to work in one of the listed setups):
- Ubuntu 9.04 (x64) on x86_64 with Radeon HD4870X2: Framebuffer error, garbled screen.
- Ubuntu 9.04 (x64) on x86_64 with Radeon HD 3300 (790GX): garbled screen.
[edit] Mesa drivers
If fglrxinfo reports that Indirect rendering by Mesa is in place, even though you have installed ATI driver, you might want to remove Mesa:
- Remove the package xserver-xgl.
sudo apt-get remove xserver-xgl
- Explanation: If you installed this previously in order to make compiz work, it will not allow direct rendering on your display. You can check out if this is what it causing the problem by running
DISPLAY=:0 glxinfo | grep render
- If it returns an ATI renderer, it means that xgl is being displayed indirectly on the display 1. (Taken from [2])
- Warning: This might make your compiz stop working as it is configured to use XGL. A solution might be to run the Envy script in order to configure compiz. Or, if Compiz stopped working due to "Composite" problem, check that the following is set in the /etc/X11/xorg.conf
Section "Extensions"
Option "Composite" "Enable"
EndSection
- Check for AGP and DRI errors in /var/log/Xorg.0.log like these are:
- (EE) fglrx(0): [agp] unable to acquire AGP, error -1023
- (EE) fglrx(0): cannot init AGP
- (EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
- (WW) fglrx(0): * DRI initialization failed! *
- If you have Intel 8285P and E7205 chipsets and AGP not detected then you have to remove the i82875p_edac module and restart a some others:
rmmod i82875p_edac
rmmod fglrx
rmmod intel-agp
rmmod agpgart
modprobe agpgart
modprobe intel-agp
modprobe fglrx
- Blacklist the modules e7xxx_edac so it doesn't start up again when booting - add the following line at the beginning of /etc/modprobe.d/blacklist:
blacklist i82875p_edac
- This has been known to fix issues with -Mesa -AGP -DRI -Google earth and -suspend to RAM (s2ram).
- Explanation: http://openwetware.org/wiki/Computing/Linux/Ubuntu
- Check you are running the correct kernel.
- Explanation: If you're upgrading from Gutsy to Hardy in some instances the Grub bootloader does not get updated and the new kernel is not loaded.
- Run in a terminal:
uname -r
- If the output starts with 2.6.22 or below you are not using the current kernel and the Ati drivers will not load properly.
If this doesn't help, try Ubuntu Gutsy Installation Guide#Verifying, or other links: [3], [4], [5].
[edit] Hang at logout
If you experience hangs when logging out (of X) it is probably due to the /etc/ati/authatieventsd.sh script looking for X authorisation files in the wrong place when it starts up. You can kill the hanging authatieventsd.sh processes from a console tty to allow the shutdown of the X server. This can be fixed permanently with:
sudo mkdir -p /var/lib/xdm/authdir
sudo ln -s /var/run/xauth /var/lib/xdm/authdir/authfiles
If that doesn't work then you can disable atieventsd with this command:
sudo /usr/sbin/update-rc.d -f atieventsd remove
Before the above commands verify that /etc/ati/authatieventsd.sh exists after build and install, if not just do :
(assuming that the installer is in your home directory)
sh ati-driver-installer-8-12-x86.x86_64.run --extract driver
sudo cp ~/driver/packages/Ubuntu/dists/jaunty/replacements/authatieventsd.sh /etc/ati/authatieventsd.sh
(jaunty is to be replaced by the name used at the building stage (intrepid,hardy,8.10,8.04,etc...)
sudo chmod +x /etc/ati/authatieventsd.sh
just reboot login and ctrl+alt+backspace to try
[edit] Suspend/Hibernation
Suspend hibernation works with the latest driver.
For ATI X1400, to get the laptop to wake up from suspend, I had to change the following in /etc/default/acpi-support:
SAVE_VBE_STATE=false
POST_VIDEO=false
ENABLE_LAPTOP_MODE=false
Comment: This is a little surprising, since the comments at the beginning of /etc/default/acpi-support seem to make it quite clear that those settings are ignored unless you add "acpi-support" to SUSPEND_METHODS. --Bewst 23:22, 19 December 2008 (UTC)
For Radeon 3200, to wake up from suspend, I had to add the following lines to /etc/X11/xorg.conf: (This settings is not good option, if you are using compiz-fusion or any other transparency-based thingie. Not working for HD 3850)
Section "Extensions"
Option "Composite" "Disable"
EndSection
Section "ServerFlags"
Option "AIGLX" "off"
EndSection
[edit] Can't remove fglrx with dpkg
If dpkg really-really refuses to remove an older fglrx-package, it might be needed to edit /var/lib/dpkg/diversions and remove a few lines. This is a hack and should be avoided.
[edit] This module/version combo is already installed
If you get this error-message, simply uninstall the previous version before installing the new one with:
| Terminal Command |
|
sudo dkms remove -m fglrx -v 8.522 --all |
[edit] New kernel installed?
I found out that when getting a new kernel the fglrx kernel-module is not installed for your new kernel. You can do that by these simple steps:
| Terminal Command |
|
sudo dkms build -m fglrx -v 8.552 -k `uname -r` |
if amdcccle doesn't work and says Identifier is not a valid word. Use lower case letter in xorg.conf
2009년 5월 21일 목요일
10.5.7 로 업그레이드 하고 난 후 부팅 방법
10.5.7 로 부팅하고 난 후 정상부팅시도를 하면 커널패닉으로 부팅이 안되는 경우가 있습니다.
이런 경우 다음과 같은 방법을 사용하시면 적어도 어떤 드라이버에서 문제가 발생하는 지 알 수 있습니다.
다음 방법은 리테일 DVD 이미지를 사용하였을 경우에만 사용하십시요.
AMD 시스템에서는 그때그때 상황에 따라 다르므로 참고만 하여 주십시요.
Chameleon/XPC 방식의 부트로드일때만 권합니다.
1. 부팅옵션을 "-v -f -s" 를 주어서 싱글유저모드로 부팅한다.
2. "exit"입력하고 엔터를 치면 다시 정상모드로 부팅이 되는 데 이때 화면에 뜨는 로그들을 잘 분석한다. << 이때 특히 Legacy 관련 Kext 로딩시 로그화일들을 유념해서 보아야 하고 부팅이 안되면 Legacy 관련 Kext를 제거하고 부팅시도합니다.
또한, AppleHDA.kext 도 커널패닉에 일조를 하는 경우의 수가 있으니 이 파일도 원본 화일로 돌려 놓고 부팅시도를 합니다.
1. 시스템 상황 파악하기
2. 추가 조치 방안
3. 이미지의 종류
4. 드라이버만 골라 설치하기
5. 관련시스템 설치이력 찾기
2009년 5월 20일 수요일
Windows 7 on Mac with VMware Fusion: A Practical Guide
Windows 7 on Mac with VMware Fusion: A Practical Guide
There’s been a lot of buzz flying around about Microsoft’s next big operating system, Windows 7, which just entered public beta.
As our readers know, a great way to start testing out a new operating system is in a virtual machine, where you can see how it works without having to dedicate a whole physical machine.
Well guess what: this is certainly the case with Windows 7 and VMware Fusion, too. So we wanted to take the time to share best practices on how to make this happen, with screenshots and video of the process to make it nice and easy for you.
Git yer free trial Windows! Six months to see what you think of Windows on Mac!
Another cool thing about the Windows 7 Beta, is that it’s free to use for anyone. That’s right. Anyone can go and download the Windows 7 bits, and get a beta serial key that’s good through July 1st, 2009.
One of the costs associated with running Windows on the Mac is the cost of Windows. And unlike VMware Fusion, which has a fully-functional 30-day trial for anyone to play with, Microsoft doesn’t typically provide trial access to operating systems in a way conducive to playing around in a VMware virtual machine—like an OS disk image, for example.
As such, a lot of Mac users who aren’t recent switchers, haven’t taken the opportunity to play around with the idea of Windows on the Mac, and as a result haven’t seen how fast, stable, and easy it can be. Instead, you get people sitting back and saying “Windows on Mac? Ew!” because they haven’t really had the opportunity to learn any better. They don’t know what they’re missing. Well this is the chance to fix that.
It’s All About the Apps, Baby.
This kind of old-school thinking is a bit of a bummer, as there are tens of thousands of great Windows-only applications that Mac users can’t access without virtualized Windows apps, like Microsoft’s Photosynth on Mac, Worldwide Telescope on Mac, or Microsoft’s new Songsmith on the Mac, not to mention things like Google Chrome on Mac. The list goes on and on, but you get the point. It’s nice to have a balanced Dock!
Not just that, but Windows on the Mac nowadays isn’t your father’s Windows on Mac. This isn’t Virtual PC for Mac, which emulated the Intel chip in software. This isvirtualization, with direct CPU access, and all the speed that entails. Also, this isn’t Mac virtualization of the sort you may have seen in early 2007. The Macs are twice as fast, and the software’s much more mature.
So, we wanted to take the opportunity to show you that Windows 7, like Windows XP, Windows Vista, Windows 98, and pretty much any other Intel-based OS (Linux too!) will run in a VM with VMware Fusion, and give some guidance on how to set things up for best success.
First, The Caveats
Windows 7 beta, both 32-bit and 64-bit, is not supported with VMware Fusion, but many VMware product features appear to work well today including Drag and Drop, Unity, and more. Based on commentary in our VMware Fusion forums, the best experience with Windows 7 beta with Fusion results from the following VMware settings:
- Use the Windows Server 2008 option to create your VM
- Disable 3D Acceleration
- Disabled Shared Folders
We plan to support Windows 7 after it is released.
Next, What You Care About
Because VMware Fusion does not yet support Windows 7, there are some tweaks you’ll have to do.
First, go ahead and download the Windows 7 ISO from Microsoft’s Windows 7 Beta siteand get yourself a beta product key. You can use 32-bit or 64-bit, but we’ve heard that lots of folks are getting better performance out of 64-bit, so this example will assume that. Just download the ISO to your desktop.
Then, you’ll go to create a new virtual machine, the same as you’ve done before via “File>New”:
Next, we’re going to point the New Virtual Machine Assistant at the Windows 7 ISO you just downloaded. Typically, if you just insert a Windows install disk, VMware Fusion automagically recognizes what OS is in it, but in this case, we have to point it at the ISO.
Click “Continue without disk.”
Then, click “Use operating system installation disk image file”:
Just select the ISO in the dialog that pops up:
Next, based on what we’ve seen in our VMware Fusion forums, you have to do a little bit of tweaking.
First, Windows Easy Install will parse the disk image as Windows Vista (either 32 or 64 bit, depending on which ISO you downloaded). Go ahead and change that to Windows Server 2008 (again 32 or 64-bit, depending on which one you downloaded). We’ve heard that it works fine defined as “Vista” too, but this appears to be the best way.
Next, go ahead and take that serial key that was provided to you by Microsoft, and paste it into the Windows Product Key form in Windows Easy Install.
Also, untick “Make your home folder accessible to the virtual machine", as based on reports in our VMware Fusion forums, shared folders aren’t working in Windows 7.
At this point, you should see your final configuration setup, with 1 GB of RAM assigned, and a virtual hard disk that will expand up to 40GB (but will start much smaller). Click “Finish.”
Once you hit “Finish,” Windows Easy Install will be off and running, installing Windows 7. You’ll see some reboots, and VMware Tools will install automatically.
After that’s all finished, you should be able to play around with Windows 7 as you would expect, with the noted exceptions up top. Again, this is not a supported configuration, and there will likely be bugs, as we repeat above from reports in our VMware Fusion forums.
And for those who like movies more, we threw together the one below to help you through the process.
Enjoy, and remember, for those of you who haven’t played around with Windows on your Mac yet because you didn’t quite see the light, this is your opportunity to join the ranks of the truly enlightened who realize that one OS per machine is so 20th century…
Download the free trial of VMware Fusion 2 or buy yourself a copy, and then get yourself the Windows 7 Beta.
피드 구독하기:
글 (Atom)