[Çözüldü] G3 ppc Xorg.conf ayarı kaydedemiyorum

Başlatan efsaneci300, 23 Mayıs 2013 - 14:21:15

« önceki - sonraki »

0 Üyeler ve 1 Ziyaretçi konuyu incelemekte.

Yazdır
Aşağı git Sayfa1
Kullanıcı Eylemleri

efsaneci300

23 Mayıs 2013 - 14:21:15 Son düzenlenme: 22 Haziran 2013 - 19:59:19 if
merhabalar arkadaşlar.
elimde bir adet G3 Powerpc makina var. içine Ubuntu 10.04 kurdum. kurulum esnasında olduğu gibi kurunca da ekran yarım olarak çıkıyor.
ben de gerekli xorg.conf düzenini buldum ve düzenledim.(xorg.conf ve bak dosyasını oluşturdum). buraya kadar sıkıntım yok ama bu ayarları başlangıçta ekrana uyarı geliyor ve düşük çözünürlükte tut deyince normal olarak başlıyor. ama xorg.conf dosyasını siliyor ve yedeğe atıyor. sonraki başlangıçta yarım ekrana geri dönüyor. bu ayarları nasıl tutabilirim?
yardımlarınızı bekliyorum... :-\ :-\ :-\ :-\

heartsmagic

#1
23 Mayıs 2013 - 14:49:04
Düşük çözünürlükte tut seçeneğinden başka bir öneri sunmuyor mu sana?
Hayattan çıkarı olmayanların, ölümden de çıkarı olmayacaktır.
Hayatlarıyla yanlış olanların ölümleriyle doğru olmalarına imkân var mıdır?

Böylece yalan, dünyanın düzenine dönüştürülüyor.

efsaneci300

#2
23 Mayıs 2013 - 15:13:07 Son düzenlenme: 28 Mayıs 2013 - 19:33:52 if
hocam bu seçenekler çıkıyor.


Mesaj tekrarı yüzünden mesajınız birleştirildi. Bu mesajın gönderim tarihi : 23 Mayıs 2013, 15:37:54


Alıntı yapılan: heartsmagic - 23 Mayıs 2013 - 14:49:04
Düşük çözünürlükte tut seçeneğinden başka bir öneri sunmuyor mu sana?
yaptım hocam uyguluyor fakat reboot ettiğimde yarım ekrana geri dönüyor ve xorg.conf dosyasını sıfırlıyor .
ya bu menü çıkmadan default olarak yaptığım ayarlamaları uygulamanın bir yolu yok mu?

[eklenti yönetici tarafından silindi]

heartsmagic

#3
24 Mayıs 2013 - 11:51:31
Bu durumda ortada bir sıkıntı var ki sistem uyarı basıyor diye düşünmekteyim. Yaptığın ayarların doğru olduğuna emin miyiz?
Hayattan çıkarı olmayanların, ölümden de çıkarı olmayacaktır.
Hayatlarıyla yanlış olanların ölümleriyle doğru olmalarına imkân var mıdır?

Böylece yalan, dünyanın düzenine dönüştürülüyor.

efsaneci300

#4
24 Mayıs 2013 - 17:48:42 Son düzenlenme: 28 Mayıs 2013 - 19:34:30 if
Alıntı yapılan: heartsmagic - 24 Mayıs 2013 - 11:51:31
Bu durumda ortada bir sıkıntı var ki sistem uyarı basıyor diye düşünmekteyim. Yaptığın ayarların doğru olduğuna emin miyiz?
hocam yaptığım şu ki /etc/X11/xorg.conf dosyasını oluşturdum ve Ubuntu.org forumundan G3 makinam için olan ayar dosyalarını düzenledim ve ekran çözünürlüğü tam olarak oturdu. Başlangıçta da sorunsuz olarak açılıyor. fakat bu uyarı geldikten sonra Xorg sorunsuz çalışıyorken yeniden başlatınca yarım ekran haline gelip bu ayarlar çıkmadan devam ediyor. GDMyi kaldırsam olur mu acaba. bunu yapan o olabilir mi ???


Mesaj tekrarı yüzünden mesajınız birleştirildi. Bu mesajın gönderim tarihi : 24 Mayıs 2013 - 17:50:03

yani bu ayarlar da sorunsuz çalışıyor ama reboot edince fıs


Mesaj tekrarı yüzünden mesajınız birleştirildi. Bu mesajın gönderim tarihi : 24 Mayıs 2013, 17:58:27

belki benm gibi olup da sorun olmayan vardır arkadaşlar.xorg.conf dosyasına yazdığım kod da bu:
Kod Seç
Section "Files"
FontPath "/usr/share/X11/fonts/misc"
FontPath "/usr/share/X11/fonts/cyrillic"
FontPath "/usr/share/X11/fonts/100dpi/:unscaled"
FontPath "/usr/share/X11/fonts/75dpi/:unscaled"
FontPath "/usr/share/X11/fonts/Type1"
FontPath "/usr/share/X11/fonts/CID"
FontPath "/usr/share/X11/fonts/100dpi"
FontPath "/usr/share/X11/fonts/75dpi"
        # paths to defoma fonts
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID"
EndSection

Section "Module"
Load "GLcore"
Load "i2c"
Load "bitmap"
Load "ddc"
Load "dri"
Load "extmod"
Load "freetype"
Load "glx"
Load "int10"
Load "type1"
Load "vbe"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc104"
Option "XkbLayout" "us,th"
# Option "XkbVariant" "nodeadkeys"
# Option "XkbOptions" "lv3:lwin_switch"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
# Option "Device" "/dev/input/mice"
# Option "Protocol" "ImPS/2"
# Option "Emulate3Buttons" "true"
# Option "ZAxisMapping" "4 5"
EndSection

#Section "InputDevice"
# Identifier "Synaptics Touchpad"
# Driver "synaptics"
# Option "SendCoreEvents" "true"
# Option "Device" "/dev/psaux"
# Option "Protocol" "auto-dev"
# Option "HorizScrollDelta" "0"
#EndSection

Section "Device"
Identifier "ATI Technologies, Inc. Rage Mobility M3 (AGP)"
Driver "ati"
BusID "PCI:0:16:0"
Option "UseFBDev" "false"
Option "SWcursor" "true"
Option "ForcePCIMode" "true"
# Option "XAANoOffscreenPixmaps"

EndSection

Section "Monitor"
Identifier "Standardbildschirm"
Option "DPMS"
HorizSync 28-51
VertRefresh 43-60
EndSection

Section "Screen"
Identifier "Default Screen"
Device "ATI Technologies, Inc. Rage Mobility M3 (AGP)"
Monitor "Standardbildschirm"
DefaultDepth 24
SubSection "Display"
Depth 1
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 4
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 15
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
# InputDevice "Synaptics Touchpad"
Option "AIGLX" "true"
EndSection

Section "DRI"
Mode 0666
EndSection

heartsmagic

#5
28 Mayıs 2013 - 15:34:31
Yani bir kere başlatıyorsun işe yarıyor, bir sonraki başlangıçta mı bozuluyor ayar?
Hayattan çıkarı olmayanların, ölümden de çıkarı olmayacaktır.
Hayatlarıyla yanlış olanların ölümleriyle doğru olmalarına imkân var mıdır?

Böylece yalan, dünyanın düzenine dönüştürülüyor.

if

#6
28 Mayıs 2013 - 19:36:53
@efsaneci300,
Kod Seç
lspci | grep VGA
cat /var/log/Xorg.0.log çıktılarına bakayım.

İletilerinizi yazım kuralları çerçevesinde yazarsanız memnun olurum.

efsaneci300

#7
29 Mayıs 2013 - 14:03:14
Alıntı yapılan: heartsmagic - 28 Mayıs 2013 - 15:34:31
Yani bir kere başlatıyorsun işe yarıyor, bir sonraki başlangıçta mı bozuluyor ayar?
aynen öyle oluyor hocam. kusuruma bakmayın sınavlarım dolayısı ile gec cevap veriyorum.
:-\ :-\
Alıntı yapılan: if - 28 Mayıs 2013 - 19:36:53
@efsaneci300,
Kod Seç
lspci | grep VGA
cat /var/log/Xorg.0.log çıktılarına bakayım.

İletilerinizi yazım kuralları çerçevesinde yazarsanız memnun olurum.
hım hocam çok özür diliyorum.
kodları deneyince de şu sonucu aldım:
Kod Seç
(II) LoadModule: "fbdev"
(II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
(II) Module fbdev: vendor="X.Org Foundation"
compiled for 1.7.6, module version = 0.4.1
ABI class: X.Org Video Driver, version 6.0
(II) R128: Driver for ATI Rage 128 chipsets:
ATI Rage 128 Mobility M3 LE (PCI), ATI Rage 128 Mobility M3 LF (AGP),
ATI Rage 128 Mobility M4 MF (AGP), ATI Rage 128 Mobility M4 ML (AGP),
ATI Rage 128 Pro GL PA (PCI/AGP), ATI Rage 128 Pro GL PB (PCI/AGP),
ATI Rage 128 Pro GL PC (PCI/AGP), ATI Rage 128 Pro GL PD (PCI),
ATI Rage 128 Pro GL PE (PCI/AGP), ATI Rage 128 Pro GL PF (AGP),
ATI Rage 128 Pro VR PG (PCI/AGP), ATI Rage 128 Pro VR PH (PCI/AGP),
ATI Rage 128 Pro VR PI (PCI/AGP), ATI Rage 128 Pro VR PJ (PCI/AGP),
ATI Rage 128 Pro VR PK (PCI/AGP), ATI Rage 128 Pro VR PL (PCI/AGP),
ATI Rage 128 Pro VR PM (PCI/AGP), ATI Rage 128 Pro VR PN (PCI/AGP),
ATI Rage 128 Pro VR PO (PCI/AGP), ATI Rage 128 Pro VR PP (PCI),
ATI Rage 128 Pro VR PQ (PCI/AGP), ATI Rage 128 Pro VR PR (PCI),
ATI Rage 128 Pro VR PS (PCI/AGP), ATI Rage 128 Pro VR PT (PCI/AGP),
ATI Rage 128 Pro VR PU (PCI/AGP), ATI Rage 128 Pro VR PV (PCI/AGP),
ATI Rage 128 Pro VR PW (PCI/AGP), ATI Rage 128 Pro VR PX (PCI/AGP),
ATI Rage 128 GL RE (PCI), ATI Rage 128 GL RF (AGP),
ATI Rage 128 RG (AGP), ATI Rage 128 VR RK (PCI),
ATI Rage 128 VR RL (AGP), ATI Rage 128 4X SE (PCI/AGP),
ATI Rage 128 4X SF (PCI/AGP), ATI Rage 128 4X SG (PCI/AGP),
ATI Rage 128 4X SH (PCI/AGP), ATI Rage 128 4X SK (PCI/AGP),
ATI Rage 128 4X SL (PCI/AGP), ATI Rage 128 4X SM (AGP),
ATI Rage 128 4X SN (PCI/AGP), ATI Rage 128 Pro ULTRA TF (AGP),
ATI Rage 128 Pro ULTRA TL (AGP), ATI Rage 128 Pro ULTRA TR (AGP),
ATI Rage 128 Pro ULTRA TS (AGP?), ATI Rage 128 Pro ULTRA TT (AGP?),
ATI Rage 128 Pro ULTRA TU (AGP?)
(II) FBDEV: driver for framebuffer: fbdev
(II) Primary Device is: PCI 00@00:10:0
(WW) Falling back to old probe method for fbdev
(II) Loading sub module "fbdevhw"
(II) LoadModule: "fbdevhw"
(II) Loading /usr/lib/xorg/modules/linux/libfbdevhw.so
(II) Module fbdevhw: vendor="X.Org Foundation"
compiled for 1.7.6, module version = 0.0.2
ABI class: X.Org Video Driver, version 6.0
(II) R128(0): PCI bus 0 card 16 func 0
(II) R128(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
(==) R128(0): Depth 24, (--) framebuffer bpp 32
(II) R128(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
(==) R128(0): Default visual is TrueColor
(II) R128(0): VGAAccess option set to FALSE, VGA module load skipped
(==) R128(0): RGB weight 888
(II) R128(0): Using 8 bits per RGB (8 bit DAC)
(**) R128(0): Using framebuffer device
(II) Loading sub module "fbdevhw"
(II) LoadModule: "fbdevhw"
(II) Reloading /usr/lib/xorg/modules/linux/libfbdevhw.so
(--) R128(0): Chipset: "ATI Rage 128 Mobility M3 LF (AGP)" (ChipID = 0x4c46)
(--) R128(0): Linear framebuffer at 0x94000000
(--) R128(0): MMIO registers at 0x90000000
(II) R128(0): Option "Display" ignored (framebuffer device determines display type)
(--) R128(0): VideoRAM: 8192 kByte (128-bit SDR SGRAM 1:1)
(WW) R128(0): Failed to read PCI ROM!
(WW) R128(0): Video BIOS not found!
(II) R128(0): Primary Display == Type 2
(WW) R128(0): Can't determine panel dimensions, and none specified.
Disabling programming of FP registers.
(II) R128(0): PLL parameters: rf=2950 rd=59 min=12500 max=25000; xclk=10500
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Module "ddc" already built-in
(==) R128(0): Using gamma correction (1.0, 1.0, 1.0)
(II) R128(0): <default monitor>: Using default hsync range of 31.50-37.90 kHz
(II) R128(0): <default monitor>: Using default vrefresh range of 50.00-70.00 Hz
(WW) R128(0): Unable to estimate virtual size
(II) R128(0): Clock range:  12.50 to 250.00 MHz
(II) R128(0): Not using default mode "640x350" (vrefresh out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "320x175" (unknown reason)
(II) R128(0): Not using default mode "640x400" (vrefresh out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "320x200" (unknown reason)
(II) R128(0): Not using default mode "720x400" (vrefresh out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "360x200" (unknown reason)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "320x240" (unknown reason)
(II) R128(0): Not using default mode "640x480" (vrefresh out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "320x240" (unknown reason)
(II) R128(0): Not using default mode "640x480" (vrefresh out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "320x240" (unknown reason)
(II) R128(0): Not using default mode "640x480" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "320x240" (unknown reason)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "400x300" (unknown reason)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "400x300" (unknown reason)
(II) R128(0): Not using default mode "800x600" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "400x300" (unknown reason)
(II) R128(0): Not using default mode "800x600" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "400x300" (unknown reason)
(II) R128(0): Not using default mode "800x600" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "400x300" (unknown reason)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "1024x768" (unknown reason)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "512x384" (unknown reason)
(II) R128(0): Not using default mode "1024x768" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "512x384" (unknown reason)
(II) R128(0): Not using default mode "1024x768" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "512x384" (unknown reason)
(II) R128(0): Not using default mode "1024x768" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "512x384" (unknown reason)
(II) R128(0): Not using default mode "1024x768" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "512x384" (unknown reason)
(II) R128(0): Not using default mode "1152x864" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "576x432" (unknown reason)
(II) R128(0): Not using default mode "1280x960" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "640x480" (unknown reason)
(II) R128(0): Not using default mode "1280x960" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "640x480" (unknown reason)
(II) R128(0): Not using default mode "1280x1024" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "640x512" (unknown reason)
(II) R128(0): Not using default mode "1280x1024" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "640x512" (unknown reason)
(II) R128(0): Not using default mode "1280x1024" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "640x512" (unknown reason)
(II) R128(0): Not using default mode "1600x1200" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "800x600" (unknown reason)
(II) R128(0): Not using default mode "1600x1200" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "800x600" (unknown reason)
(II) R128(0): Not using default mode "1600x1200" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "800x600" (unknown reason)
(II) R128(0): Not using default mode "1600x1200" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "800x600" (unknown reason)
(II) R128(0): Not using default mode "1600x1200" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "800x600" (unknown reason)
(II) R128(0): Not using default mode "1792x1344" (insufficient memory for mode)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "896x672" (unknown reason)
(II) R128(0): Not using default mode "1792x1344" (insufficient memory for mode)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "896x672" (unknown reason)
(II) R128(0): Not using default mode "1856x1392" (insufficient memory for mode)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "928x696" (unknown reason)
(II) R128(0): Not using default mode "1856x1392" (insufficient memory for mode)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "928x696" (unknown reason)
(II) R128(0): Not using default mode "1920x1440" (insufficient memory for mode)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "960x720" (unknown reason)
(II) R128(0): Not using default mode "1920x1440" (insufficient memory for mode)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "960x720" (unknown reason)
(II) R128(0): Not using default mode "832x624" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "416x312" (unknown reason)
(II) R128(0): Not using default mode "1152x864" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "576x432" (unknown reason)
(II) R128(0): Not using default mode "1152x864" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "576x432" (unknown reason)
(II) R128(0): Not using default mode "1152x864" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "576x432" (unknown reason)
(II) R128(0): Not using default mode "1152x864" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "576x432" (unknown reason)
(II) R128(0): Not using default mode "1152x864" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "576x432" (unknown reason)
(II) R128(0): Not using default mode "1152x864" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "576x432" (unknown reason)
(II) R128(0): Not using default mode "1360x768" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "680x384" (unknown reason)
(II) R128(0): Not using default mode "1360x768" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "680x384" (unknown reason)
(II) R128(0): Not using default mode "1400x1050" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "700x525" (unknown reason)
(II) R128(0): Not using default mode "1400x1050" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "700x525" (unknown reason)
(II) R128(0): Not using default mode "1400x1050" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "700x525" (unknown reason)
(II) R128(0): Not using default mode "1400x1050" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "700x525" (unknown reason)
(II) R128(0): Not using default mode "1440x900" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "720x450" (unknown reason)
(II) R128(0): Not using default mode "1600x1024" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "800x512" (unknown reason)
(II) R128(0): Not using default mode "1680x1050" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "840x525" (unknown reason)
(II) R128(0): Not using default mode "1680x1050" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "840x525" (unknown reason)
(II) R128(0): Not using default mode "1680x1050" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "840x525" (unknown reason)
(II) R128(0): Not using default mode "1680x1050" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "840x525" (unknown reason)
(II) R128(0): Not using default mode "1680x1050" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "840x525" (unknown reason)
(II) R128(0): Not using default mode "1920x1080" (hsync out of range)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "960x540" (unknown reason)
(II) R128(0): Not using default mode "1920x1200" (insufficient memory for mode)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "960x600" (unknown reason)
(II) R128(0): Not using default mode "1920x1440" (insufficient memory for mode)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "960x720" (unknown reason)
(II) R128(0): Not using default mode "2048x1536" (insufficient memory for mode)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "1024x768" (unknown reason)
(II) R128(0): Not using default mode "2048x1536" (insufficient memory for mode)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "1024x768" (unknown reason)
(II) R128(0): Not using default mode "2048x1536" (insufficient memory for mode)
(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument
(II) R128(0): Not using default mode "1024x768" (unknown reason)
(--) R128(0): Virtual size is 800x600 (pitch 800)
(**) R128(0): *Default mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz
(II) R128(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz)
(**) R128(0): *Default mode "800x600": 36.0 MHz, 35.2 kHz, 56.2 Hz
(II) R128(0): Modeline "800x600"x56.2   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz)
(**) R128(0): *Default mode "640x480": 25.2 MHz, 31.5 kHz, 59.9 Hz
(II) R128(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz)
(==) R128(0): DPI set to (96, 96)
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules/libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 1.7.6, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(II) Loading sub module "xaa"
(II) LoadModule: "xaa"
(II) Loading /usr/lib/xorg/modules/libxaa.so
(II) Module xaa: vendor="X.Org Foundation"
compiled for 1.7.6, module version = 1.2.1
ABI class: X.Org Video Driver, version 6.0
(II) Loading sub module "shadowfb"
(II) LoadModule: "shadowfb"
(II) Loading /usr/lib/xorg/modules/libshadowfb.so
(II) Module shadowfb: vendor="X.Org Foundation"
compiled for 1.7.6, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) R128(0): Page flipping disabled
(!!) R128(0): For information on using the multimedia capabilities
of this adapter, please see http://gatos.sf.net.
(II) UnloadModule: "fbdev"
(II) Unloading /usr/lib/xorg/modules/drivers/fbdev_drv.so
(II) UnloadModule: "fbdevhw"
(--) Depth 24 pixmap format is 32 bpp
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: node name is /dev/dri/card0
drmOpenByBusid: Searching for BusID pci:0000:00:10.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 9, (OK)
drmOpenByBusid: drmOpenMinor returns 9
drmOpenByBusid: drmGetBusid reports pci:0000:00:10.0
(II) [drm] loaded kernel module for "r128" driver.
(II) [drm] DRM interface version 1.3
(II) [drm] DRM open master succeeded.
(II) R128(0): [drm] Using the DRM lock SAREA also for drawables.
(II) R128(0): [drm] framebuffer handle = 0x94000000
(II) R128(0): [drm] added 1 reserved context for kernel
(II) R128(0): X context handle = 0x1
(II) R128(0): [drm] installed DRM signal handler
(II) R128(0): [agp] Mode 0x07000201 [AGP 0x106b/0x0027; Card 0x1002/0x4c46]
(II) R128(0): [agp] 8192 kB allocated with handle 0x00000001
(II) R128(0): [agp] ring handle = 0x00000000
(II) R128(0): [agp] Ring mapped at 0x48857000
(II) R128(0): [agp] ring read ptr handle = 0x00101000
(II) R128(0): [agp] Ring read ptr mapped at 0x48028000
(II) R128(0): [agp] vertex/indirect buffers handle = 0x00102000
(II) R128(0): [agp] Vertex/indirect buffers mapped at 0x48958000
(II) R128(0): [agp] AGP texture map handle = 0x00302000
(II) R128(0): [agp] AGP Texture map mapped at 0x48b58000
(II) R128(0): [drm] register handle = 0x90000000
(II) R128(0): [dri] Visual configs initialized
(II) R128(0): CCE in BM mode
(II) R128(0): Using 8 MB AGP aperture
(II) R128(0): Using 1 MB for the ring buffer
(II) R128(0): Using 2 MB for vertex/indirect buffers
(II) R128(0): Using 5 MB for AGP textures
(II) R128(0): Memory manager initialized to (0,0) (800,2416)
(II) R128(0): Reserved area from (0,600) to (800,602)
(II) R128(0): Largest offscreen area available: 800 x 1814
(II) R128(0): Reserved back buffer from (0,602) to (800,1202)
(II) R128(0): Reserved depth buffer from (0,1202) to (800,1803)
(II) R128(0): Reserved depth span from (0,1802) offset 0x57fd00
(II) R128(0): Reserved 640 kb for textures at offset 0x75f800
(II) R128(0): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
8x8 mono pattern filled rectangles
Indirect CPU to Screen color expansion
Solid Lines
Dashed Lines
Setting up tile and stipple cache:
24 128x128 slots
(II) R128(0): Acceleration enabled
(==) R128(0): Backing store disabled
(==) R128(0): Silken mouse enabled
(II) R128(0): Using hardware cursor (scanline 7212)
(II) R128(0): Largest offscreen area available: 800 x 610
(==) R128(0): DPMS enabled
(II) R128(0): [DRI] installation complete
(II) R128(0): [drm] Added 128 16384 byte vertex/indirect buffers
(II) R128(0): [drm] Mapped 128 vertex/indirect buffers
(II) R128(0): [drm] dma control initialized, using IRQ 48
(II) R128(0): Direct rendering enabled
(==) RandR enabled
(II) Initializing built-in extension Generic Event Extension
(II) Initializing built-in extension SHAPE
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension BIG-REQUESTS
(II) Initializing built-in extension SYNC
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-MISC
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) AIGLX: Screen 0 is not DRI2 capable
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 10, (OK)
drmOpenByBusid: Searching for BusID pci:0000:00:10.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 10, (OK)
drmOpenByBusid: drmOpenMinor returns 10
drmOpenByBusid: drmGetBusid reports pci:0000:00:10.0
(II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
(II) AIGLX: Loaded and initialized /usr/lib/dri/r128_dri.so
(II) GLX: Initialized DRI GL provider for screen 0
(II) XKB: reuse xkmfile /var/lib/xkb/server-B20D7FC79C7F597315E3E501AEF10E0D866E8E92.xkm
(II) config/udev: Adding input device PowerMac Beep (/dev/input/event4)
(II) No input driver/identifier specified (ignoring)
(II) config/udev: Adding input device Macintosh mouse button emulation (/dev/input/event0)
(**) Macintosh mouse button emulation: Applying InputClass "evdev pointer catchall"
(II) LoadModule: "evdev"
(II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
(II) Module evdev: vendor="X.Org Foundation"
compiled for 1.7.6, module version = 2.3.2
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 7.0
(**) Macintosh mouse button emulation: always reports core events
(**) Macintosh mouse button emulation: Device: "/dev/input/event0"
(II) Macintosh mouse button emulation: Found 3 mouse buttons
(II) Macintosh mouse button emulation: Found relative axes
(II) Macintosh mouse button emulation: Found x and y relative axes
(II) Macintosh mouse button emulation: Configuring as mouse
(**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
(**) Macintosh mouse button emulation: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Macintosh mouse button emulation" (type: MOUSE)
(II) Macintosh mouse button emulation: initialized for relative axes.
(II) config/udev: Adding input device Macintosh mouse button emulation (/dev/input/mouse0)
(II) No input driver/identifier specified (ignoring)
(II) config/udev: Adding input device ADB keyboard (/dev/input/event1)
(**) ADB keyboard: Applying InputClass "evdev keyboard catchall"
(**) ADB keyboard: always reports core events
(**) ADB keyboard: Device: "/dev/input/event1"
(II) ADB keyboard: Found keys
(II) ADB keyboard: Configuring as keyboard
(II) XINPUT: Adding extended input device "ADB keyboard" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "tr"
(II) XKB: reuse xkmfile /var/lib/xkb/server-A27DF63AF07B0BF4D15EF70AE51C833E34D0812D.xkm
(II) config/udev: Adding input device ADB Powerbook buttons (/dev/input/event2)
(**) ADB Powerbook buttons: Applying InputClass "evdev keyboard catchall"
(**) ADB Powerbook buttons: always reports core events
(**) ADB Powerbook buttons: Device: "/dev/input/event2"
(II) ADB Powerbook buttons: Found keys
(II) ADB Powerbook buttons: Configuring as keyboard
(II) XINPUT: Adding extended input device "ADB Powerbook buttons" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "tr"
(II) config/udev: Adding input device PMU (/dev/input/event3)
(**) PMU: Applying InputClass "evdev keyboard catchall"
(**) PMU: always reports core events
(**) PMU: Device: "/dev/input/event3"
(II) PMU: Found keys
(II) PMU: Configuring as keyboard
(II) XINPUT: Adding extended input device "PMU" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "tr"
(II) config/udev: Adding input device Microsoft Microsoft® Nano Transceiver v2.0 (/dev/input/mouse1)
(II) No input driver/identifier specified (ignoring)
(II) config/udev: Adding input device Microsoft Microsoft® Nano Transceiver v2.0 (/dev/input/js0)
(II) No input driver/identifier specified (ignoring)
(II) config/udev: Adding input device Microsoft Microsoft® Nano Transceiver v2.0 (/dev/input/event7)
(**) Microsoft Microsoft® Nano Transceiver v2.0: Applying InputClass "evdev keyboard catchall"
(**) Microsoft Microsoft® Nano Transceiver v2.0: always reports core events
(**) Microsoft Microsoft® Nano Transceiver v2.0: Device: "/dev/input/event7"
(II) Microsoft Microsoft® Nano Transceiver v2.0: Found 1 mouse buttons
(II) Microsoft Microsoft® Nano Transceiver v2.0: Found scroll wheel(s)
(II) Microsoft Microsoft® Nano Transceiver v2.0: Found relative axes
(II) Microsoft Microsoft® Nano Transceiver v2.0: Found absolute axes
(II) Microsoft Microsoft® Nano Transceiver v2.0: Found x and y absolute axes
(II) Microsoft Microsoft® Nano Transceiver v2.0: Found keys
(II) Microsoft Microsoft® Nano Transceiver v2.0: Configuring as mouse
(II) Microsoft Microsoft® Nano Transceiver v2.0: Configuring as keyboard
(**) Microsoft Microsoft® Nano Transceiver v2.0: YAxisMapping: buttons 4 and 5
(**) Microsoft Microsoft® Nano Transceiver v2.0: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Microsoft Microsoft® Nano Transceiver v2.0" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "tr"
(EE) Microsoft Microsoft® Nano Transceiver v2.0: failed to initialize for relative axes.
(WW) Device 'Microsoft Microsoft® Nano Transceiver v2.0' has 37 axes, only using first 36.
(II) Microsoft Microsoft® Nano Transceiver v2.0: initialized for absolute axes.
(II) config/udev: Adding input device Microsoft Microsoft® Nano Transceiver v2.0 (/dev/input/event6)
(**) Microsoft Microsoft® Nano Transceiver v2.0: Applying InputClass "evdev pointer catchall"
(**) Microsoft Microsoft® Nano Transceiver v2.0: Applying InputClass "evdev keyboard catchall"
(**) Microsoft Microsoft® Nano Transceiver v2.0: always reports core events
(**) Microsoft Microsoft® Nano Transceiver v2.0: Device: "/dev/input/event6"
(II) Microsoft Microsoft® Nano Transceiver v2.0: Found 9 mouse buttons
(II) Microsoft Microsoft® Nano Transceiver v2.0: Found scroll wheel(s)
(II) Microsoft Microsoft® Nano Transceiver v2.0: Found relative axes
(II) Microsoft Microsoft® Nano Transceiver v2.0: Found x and y relative axes
(II) Microsoft Microsoft® Nano Transceiver v2.0: Found absolute axes
(II) Microsoft Microsoft® Nano Transceiver v2.0: Found keys
(II) Microsoft Microsoft® Nano Transceiver v2.0: Configuring as mouse
(II) Microsoft Microsoft® Nano Transceiver v2.0: Configuring as keyboard
(**) Microsoft Microsoft® Nano Transceiver v2.0: YAxisMapping: buttons 4 and 5
(**) Microsoft Microsoft® Nano Transceiver v2.0: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Microsoft Microsoft® Nano Transceiver v2.0" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "tr"
(II) Microsoft Microsoft® Nano Transceiver v2.0: initialized for relative axes.
(WW) Microsoft Microsoft® Nano Transceiver v2.0: ignoring absolute axes.
(II) config/udev: Adding input device Microsoft Microsoft® Nano Transceiver v2.0 (/dev/input/event5)
(**) Microsoft Microsoft® Nano Transceiver v2.0: Applying InputClass "evdev keyboard catchall"
(**) Microsoft Microsoft® Nano Transceiver v2.0: always reports core events
(**) Microsoft Microsoft® Nano Transceiver v2.0: Device: "/dev/input/event5"
(II) Microsoft Microsoft® Nano Transceiver v2.0: Found keys
(II) Microsoft Microsoft® Nano Transceiver v2.0: Configuring as keyboard
(II) XINPUT: Adding extended input device "Microsoft Microsoft® Nano Transceiver v2.0" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "tr"
(WW) ADB keyboard: unable to handle keycode 464

efsaneci300

#9
18 Haziran 2013 - 20:29:34
Alıntı yapılan: if - 29 Mayıs 2013 - 17:34:26
Bir de bunu[1] deneyin.

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=57;filename=xorg.conf;att=1;bug=484015
hocam çok teşekkür ederim sorun çözüldü. artık uyarı çıkmıyor.

heartsmagic

#10
19 Haziran 2013 - 11:45:07
Çözülen başlıklarımız için: cozuldukonusu
Hayattan çıkarı olmayanların, ölümden de çıkarı olmayacaktır.
Hayatlarıyla yanlış olanların ölümleriyle doğru olmalarına imkân var mıdır?

Böylece yalan, dünyanın düzenine dönüştürülüyor.
Yazdır
Yukarı git Sayfa1
Kullanıcı Eylemleri