Fedora 에서 소스를 가지고 VLC 설치

from Info/Tools 2009/04/16 02:08 view 88126
yum install vlc 를 하면 되기도 하지만 vlc 를 변경 하고자 할때 소스 를 통해 설치 해보자.
핵심은 libxxx-devel 을 깔아야 된다는거.

http://www.videolan.org/ 에서 소스를 다운 받는다.

./configure 를 하면 libmad 가 없다고 뜬다.
yum install libmad
yum install libmad-devel

liabavcodec 없다고 뜨면
yum install ffmpeg
yum install ffmpeg-devel

liba52 가 없다고 뜨면
http://liba52.sourceforge.net/ 에서 소스를 다운받고 설치.

혹시라도 make install 도중 relink 어쩌고 저쩌고 에러가 뜨면 전에 수행한 make 과정이 남아있는 거므로
make clean 을 수행한후 다시 진행해보면 된다.
gdb vlc 를 수행 시키기 위한 방법. 그냥은 안되네..

1. http://www.live555.com/liveMedia/public/  메뉴얼 보고서 live 깔고 다른건 yum install xx 를 통해 깔자.

2. debug 를 위한 configure .. , yum install faad2*, libdca* 과 같은 라이브러리가 필요하기도 함.

./configure --enable-x11 --enable-xvideo --disable-gtk --enable-sdl --enable-ffmpeg --with-ffmpeg-mp3lame --enable-mad --enable-libdvbpsi --enable-a52 --enable-dca --enable-libmpeg2 --enable-dvdnav --enable-faad --enable-vorbis --enable-ogg --enable-theora --enable-faac--enable-mkv --enable-freetype --enable-fribidi --enable-speex --enable-flac --enable-livedotcom --with-livedotcom-tree=/usr/lib/live --enable-caca --enable-skins --enable-skins2 --enable-alsa --disable-kde--disable-qt --enable-wxwindows --enable-ncurses --enable-release --enable-debug

Tag | , ,
윈도우에서 듀얼 모니터를 쓸때 윈도우창을 편하게 관리하는 울트라몬을 그놈에서도 따라할수 있었다..
양쪽화면에 실행창을 따로 관리 할 수 있어 편리하다.

Just add a a panel to each monitor you want, and add to that panel a window list. That’s it.

1.) Right click on anywhere on the launchbar, click “New Panel”
2.) Drag that to any monitor.
3.) Right click on that panel, and click “Add to Panel”
4.) Select “Window List” under Desktop and Windows
5.) Click Add.
6.) Click Close, and you’re done.


삼성(DB-A75) 컴에 Fedora 10설치

from Info/OS 2009/03/18 14:09 view 21391
새로운 컴에 페도라10 설치 할려고 했더니 ..세상에~ 커널패닉이 발생한다. 아마도 그래픽 쪽 드라이버 문제인듯.

에러발생 : end trace 4eaa2a86a8e2da22

 리눅스 CD 넣고 설치선택 화면에서 TAB키를 눌러서 vm-img 어쩌고 저쩌고 뒤에 한칸띄어서

noapic nolapic acpi=off 를 뒤에 추가한뒤에 설치한다.

xwindow 설치가 아니므로 기본설치 능력이 필요하다.

여기서 wget 을 통해 드라이버를 다운받은 후 http://www.nvidia.com/object/linux_display_ia32_180.29.html
1. wget http://us.download.nvidia.com/XFree86/Linux-x86/180.29/NVIDIA-Linux-x86-180.29-pkg1.run
2. sh NVIDIA-Linux-x86-180.29-pkg1.run
3. /etc/inittab -> id:5:initdefault:

adduser 와 패스워드를 추가해주고 init5 그래픽모드로 다시 재부팅해주면 그놈이 나타남!!

참고링크 : http://forums.virtualbox.org/viewtopic.php?f=3&t=14902&start=0
Tag | ,

Fedora GDM 자동 로그인 설정

from Info/OS 2009/02/28 09:51 view 20042
-_-..우분투는 시스템메뉴에 있던게 왜 페도라엔 없을까...

Fedora Core 9 에 있는 GDM 2.22 버전 설정내용
[root@serahero ~]# vi /etc/gdm/custom.conf
# GDM configuration storage
TimedLogin=사용자 계정명





참고링크 : http://dnmouse.webs.com/autologin.html

Fedora Network Manger(고정IP사용)

from Info/Tools 2009/02/27 12:27 view 53809
cmd #1

/etc/init.d/NetworkManager stop
(NetworkManager 해지, network 체크)
(고정아이피및, DNS추가)
(network 사용 체크, 사용하고자 하는 고정IP 체크)
service network restart
init 6

cmd #2
ping sendto: Network is unreachable 이 발생했을 때 이런 방법으로 해결..

Edit /etc/sysconfig/network-scripts/ifcfg-eth0 (or whatever device)

IPADDR=*insert IP address here"
NETMASK=*insert netmask here*
NETWORK=*insert network address here*
BROADCAST=*insert broadcast address here*
GATEWAY=_insert gateway address here*
ONBOOT="yes" = interface will be active at boot time.
       "no"  = interface will NOT be active at boot time.

.If you have X-Windows set up, you can also use RH's "Network Configurator" (/usr/bin/netcfg) which actually writes to these files.
Additionally, after editing the file, do a "ifup eth0" to activate it and ifdown eth0 to deactivate it.

NetworkManager #1

NetworkManager provides automatic network detection and configuration for the system. Once enabled, the NetworkManager service also monitors the network interfaces, and may automatically switch to the best connection at any given time. Applications that include NetworkManager support may automatically switch between on-line and off-line modes when the system gains or loses network connectivity.

These facilities are most useful for modern laptops, where the user may move between wireless networks, and plug in to a variety of wired networks, but NetworkManager also provides features that are relevant to workstations. Current versions of NetworkManager support modem connections, and certain types of VPN. Development of these features is ongoing.

NetworkManager requires Fedora to have drivers for the wired and wireless interfaces on the computer. Many manufacturers of modems and wireless devices provide limited support for Linux. You may need to install additional drivers or firmware on your Fedora system in order to activate these interfaces.

Drivers first
NetworkManager may only work with network interfaces once the relevant drivers are correctly installed on your system. Reboot your system after installing a new firmware or a new driver in order to ensure that the changes take effect.

Enabling NetworkManager on Fedora

Command line way

The installation process for Fedora automatically provides NetworkManager. To enable it, enter the following commands in a terminal window:

1. Set the main service to automatically start on boot: su -c '/sbin/chkconfig --level 345 NetworkManager on' 1. Start the service: su -c '/sbin/service NetworkManager start

For each su command, enter the root password at the prompt.

Graphical Way

Start the system-config-services program, enter your root password and activate the NetworkManager service for runlevel 5.

Gnome-specific information

The NetworkManager tray icon automatically appears on your desktop once the services are started. If the NetworkManager service is active, then the tray icon appears each time that you log in to your desktop.

NetworkManager also stores any encryption keys in the gnome-keyring manager. If your are prompted to enter the keyring password after login, then keep reading. If your login password & the keyring password are the same, then there is a tool built to open the keyring for you on login. The package is called pam_keyring. To configure your system first install pam_keyring with yum:

su -c 'yum -y install pam_keyring'

Second you'll need to modify your /etc/pam.d/gdm file.

su -c 'gedit /etc/pam.d/gdm'

Add the following lines

auth    optional    pam_keyring.so try_first_pass
session optional pam_keyring.so

The order in which this lines are placed in this file are important, here is a copy from a working system

auth required pam_env.so
auth optional pam_keyring.so try_first_pass <---
auth include system-auth
account required pam_nologin.so
account include system-auth
password include system-auth
session optional pam_keyinit.so force revoke
session include system-auth
session required pam_loginuid.so
session optional pam_console.so
session optional pam_keyring.so <---

Now reboot your computer. After login the keyring will be unlocked for you. If your keyring password is different from your login password, don't worry, there is a tool available to change it.

su -c 'yum -y install gnome-keyring-manager gnome-keyring pam_keyring

Once you have installed pam_keyring and gnome-keyring, you will need to log out and back on. Then you can run

/usr/libexec/pam-keyring-tool -c

to change the default password. Alternatively you can now change a password through gnome-keyring-manager. Download and install gnome-keyring-manager. Then highlight the keyring and select Change Keyring Password from the Keyring menu of gnome-keyring-manager.

KDE specific information

To control NetworkManager by a system tray applet you need to install and start the program knetworkmanager of the same named package. The keys to the different networks are stored automatically in KDE's password storage system kwalletmanager.

Further Information

Retrieved from "https://fedoraproject.org/wiki/Tools/NetworkManager"

NetworkManager #2

Fedora 10 uses NetworkManager by default. The primary settings for any network devices will be automatically selected at installation time. Since there is no screen for selecting networking options, most devices will default to using DHCP.

Using NetworkManager has greatly improved networking for many wireless and some less common devices (mobile broadband, GSM, etc.), it may still have problems with some configurations. NetworkManager development and integration into Fedora is still an ongoing effort.

NOTE: The following steps do NOT apply to all users. NetworkManager is highly recommended for Laptop users, especially using wireless with security.

Disabling NetworkManager and Enabling network Service

On machines with a fixed networking device and a fixed IP address (e.g. desktop, server, appliance), it might be more practical to disable NetworkManager and use the older network service. Additionally users requiring virtual device types (bridging, bonding, or VLANs) will also need to use the network service.

Note that the Fedora 10 installer disables the network service by default. To switch to using the network service:

First disable NetworkManager and prevent it from automatically loading:

[mirandam@charon ~]$ sudo /etc/init.d/NetworkManager stop
Stopping NetworkManager daemon: [ OK ]

[mirandam@charon ~]$ sudo /sbin/chkconfig --level 35 NetworkManager off

Next, configure your network settings:

[mirandam@charon ~]$ sudo system-config-network

You should have an eth0 device already showing. To configure the IP settings click on Edit. Do not forget to set DNS on the DNS tab (if you're using fixed IP's). Make sure the eth0 is selected as Active. Then File > Save and quit.

Next, enable the service and make sure it loads at next boot:

[mirandam@charon ~]$ sudo /etc/init.d/network start
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]

[mirandam@charon ~]$ sudo /sbin/chkconfig --level 35 network on

While it may be possible to re-activate your network without a reboot, it may be recommended to reboot.

Startup Applications Requiring Network

Some applications require the network to be initialized during boot. If you are using NetworkManager and having these problems, edit /etc/sysconfig/network as 'root' and add the following line:

[mirandam@charon ~]$ sudo su -c 'echo NETWORKWAIT=1 >> /etc/sysconfig/network'

Some related information can be found on the Fedora Wiki.

Fedora 배포 사이트외 패키지를 받자.

from Info/OS 2009/02/20 10:31 view 17091

코덱이랑 등등 찾을 수 없어 헤매던중 찾은 정보.

/* 09.2.20 조금 버그가 있는 거 같다 -_ㅡ 페도라가 패닉이 되는 상태 발생.... */

다음 사이트에 접속하여 파일을 다운로드 받습니다. 버전에 맞는 걸 골라서~!


다운로드 받은 파일을 rpm -Uivh freshrpmsxxx.rpm명령으로 설치하시고

아래 명령들을 수행하세요.

일반적으로 페도라 배포 사이트에는 없는 패키지들을 설치.

Tag | ,
링크 : 1. http://www.thinkwiki.org/wiki/Installation_instructions_for_the_ThinkPad_X200
         2.F10 and xorg intel driver: solved

에러 해결 #1 : 링크2에 설치 법대로 inter driver 를 깔다가 에러 나는경우 yum install xorg-x11-server-dev*

./configure: line 21484: syntax error near unexpected token `XINERAMA,’
./configure: line 21484: `XORG_DRIVER_CHECK_EXT(XINERAMA, xineramaproto)’

However after installing ‘xorg-x11-server-devel-1.5.3-6.fc10.i386′ it worked correctly.

// Fedora10 경우에도 /etc/X11/xorg.conf 에 설정함..
ㅜ_ㅜ 위 링크에 전부 설명 되어있다. 괜히 찾아 돌아다니지 말자..

Ubuntu(우분투) 에서 필요한 설정 몇가지..

1. 듀얼모니터(dual monitor) 설정


With 8.10 things don't work well if you stick with the "preconfigured" xorg.conf settings: the default resolution is only 1074x768 and the highest setting that the laptop display is capable of (1280x800) doesn't even show up in the System -> Preferences -> Screen Resolution applet. To make matters worse, VGA output is a royal pain.

Here's a step-by-step guide to improve the situation if you just want to get the laptop display working properly:

  • First, make sure you've got the latest drivers for your Intel 4500MHD video card:
$ sudo apt-get install xserver-xorg-video-intel
On current 8.10, this step seems unnecessary. You get intel by default, and by this point in the install, you should have already have updated your packages. Mitchell 01:28, 15 December 2008 (CET)
  • Once that's over and done with, open up your xorg.conf file (note: be careful with this file):
$ sudo gedit /etc/X11/xorg.conf
  • Make the part that isn't commented out (i.e. that isn't preceded by a #) look like this:
Section "Monitor"
Identifier "Configured Monitor"

Section "Monitor"
Identifier "HDMI-1"
Option "Ignore" "True"

Section "Monitor"
Identifier "HDMI-2"
Option "Ignore" "True"

Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
DefaultDepth 24
SubSection "Display"
Modes "1280x800" "1024x768"
# The following line was an auto-configuration added by an external VGA projector; you might leave it out to try
# letting the system detect dimensions appropriate for whatever display you happen to use.
Virtual 2432 864

Section "Device"
Identifier "Configured Video Device"
Driver "intel"
Option "monitor-HDMI-1" "HDMI-1"
Option "monitor-HDMI-2" "HDMI-2"

2. Track Point( 스크롤 키 설정 )


Trackpoint scrolling is, as of 12/02/08, not in a good way on 8.10.

There are numerous instructions on the net which don't work for the X200, including instructions here ([How to configure the TrackPoint]).

On the X200, the HAL-based instructions in the last section may work, but only until suspend/resume or VT switching, due to a bug in evdev.

I do have it working, but it is not pretty:

  • Create a patched evdev. The following is based on instructions from the bug report. These instructions will be extremely fragile - they work for me today but could stop working at any point, based on updates to evdev or changes to the bug. The lines below do the following:
    • Set up a work area
    • Download the patch from the bug report
    • Prepare your environment for building evdev
    • Download the evdev sources
    • Patch them
    • Produce a new deb
    • Install it
sudo bash
cd /usr/local/src/
mkdir evdev
cd evdev
wget http://launchpadlibrarian.net/19254960/preinit.diff
apt-get build-dep xserver-xorg-input-evdev
apt-get source xserver-xorg-input-evdev
cd xserver-xorg-input-evdev-2.0.99+git20080912
patch -p1 < ../preinit.diff
debian/rules binary
cd ..
dpkg -i xserver-xorg-input-evdev_2.0.99*.deb
  • Add xinput lines to your .profile; with this patch, the normal HAL method no longer works (though note, I have not tested this with no hal policy for the trackpoint at all, just left the non-working one in place. YMMV).
# TEMPORARY FIX FOR BROKEN EVDEV/HAL for TrackPoint scrolling:
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Wheel Emulation" 8 1
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Wheel Emulation Button" 8 2
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Wheel Emulation Y Axis" 8 4 5
  • reboot your system.

This _should_ enable trackpoint scrolling that will be durable through suspend/resumes.

At some point they will fix the upstream evdev package, and/or adjust other configs. You may see this suddenly stop working after an update (evdev was updated but this fix wasn't in the update); in which case, re-run the steps above to create an updated patched evdev (hopefully). Or the update may carry an upstream fix; latest word in the bug is that the unstable upstream debian packages work out of the box. In which case you should simply come back and reexamine whether the xinput lines in the .profile are still necessary at a later date, or you can use the more canonical HAL profile to control the trackpoint properties.

Using HAL policy

For me this works fine (Ubuntu 8.10):

Create an file /etc/hal/fdi/policy/mouse-wheel.fdi an put the following into it:

<match key="info.product" string="TPPS/2 IBM TrackPoint">
<merge key="input.x11_options.EmulateWheel" type="string">true</merge>
<merge key="input.x11_options.EmulateWheelButton" type="string">2</merge>
<merge key="input.x11_options.YAxisMapping" type="string">4 5</merge>
<merge key="input.x11_options.XAxisMapping" type="string">6 7</merge>
<merge key="input.x11_options.Emulate3Buttons" type="string">true</merge>
<merge key="input.x11_options.EmulateWheelTimeout" type="string">200</merge>

Reboot and scrolling with the trackpoint should work.

Tag | , , ,