Направљене поруке на форуму
-
Чланци
-
Mislim da vec jeste… Sad cu stoprvi put da prekompajliram kernel pa cu da vidim.
Evo ti fglrx-install.log neznam na koji drugi mislis…[Message] Kernel Module : Trying to install a precompiled kernel module.
[Message] Kernel Module : Precompiled kernel module version mismatched.
[Message] Kernel Module : Found kernel module build environment, generating kernel module now.
ATI module generator V 2.0
==========================
initializing…
cleaning…
patching ‘highmem.h’…
probing for VMA API version…
doing script based build for kernel 2.4.x and similar
compiling ‘./agpgart_be.c’…
compiling ‘./agp3.c’…
compiling ‘./i7505-agp.c’…
compiling ‘./nvidia-agp.c’…
compiling ‘./firegl_public.c’…
firegl_public.c:3492: warning: initialization from incompatible pointer type
firegl_public.c:3493: warning: initialization from incompatible pointer type
firegl_public.c:3494: warning: initialization from incompatible pointer type
firegl_public.c:3495: warning: initialization from incompatible pointer type
firegl_public.c:3496: warning: initialization from incompatible pointer type
firegl_public.c:3497: warning: initialization from incompatible pointer type
firegl_public.c:3498: warning: initialization from incompatible pointer type
firegl_public.c:3499: warning: initialization from incompatible pointer type
firegl_public.c:3501: warning: initialization from incompatible pointer type
firegl_public.c:3511: warning: function declaration isn’t a prototype
firegl_public.c: In function `__ke_agp_allocate_memory_phys_list’:
firegl_public.c:3841: warning: passing arg 3 of pointer to function makes integer from pointer without a cast
firegl_public.c: In function `__ke_agp_bind_memory’:
firegl_public.c:3880: warning: passing arg 1 of pointer to function from incompatible pointer type
firegl_public.c: In function `__ke_agp_unbind_memory’:
firegl_public.c:3893: warning: passing arg 1 of pointer to function from incompatible pointer type
linking of fglrx kernel module…
duplicating results into driver repository…
done.
==============================
– creating symlink
– recreating module dependency list
– trying a sample load of the kernel modules
Warning: loading /lib/modules/2.4.31Nesha_Ati/kernel/drivers/char/drm/fglrx.o will taint the kernel: non-GPL license – Proprietary. (C) 2002 – ATI Technologies, Starnberg, GERMANY
See http://www.tux.org/lkml/#export-tainted for information about tainted modules
Module fglrx loaded, with warnings
done.[/list][/list][/code]xorg.conf mi je indentican kao tvoj bar u delu za graficku kartu… agpgart koristim interni iz kernela. hotplug skriptu ne koristim! agpgart mi se dize kroz rc.modules a fglrx.o pokrecem kada se sistem ucita. Naglasio sam da je agpgart unused, ne verujem da je to ok??? mozda gresim?! Inace nekad sam koristio ati-7500 64Mb i nisam imao problema. Sad za ove nove ati-je ne znam! Poslacu veceras moj xorg.log pa pogledaj… Sta mislis kada bi trebalo da ucitavam module? Imam neki osecaj da je stos u tome! I da li moduli trebaju da mi budu unused? Nije mi jasno… Da pokusam da aktiviram hotlug??? Sta bi dobio time?
Uradio sam i taj Windows restart!!! Zaboravio sam da navedem da sam pokrenuo fglrxconfig… On je napravio neki njegov xorg.conf u kome jedan driver vga a drugi fglrx:
# Graphics device section
# **********************************************************************# Any number of graphics device sections may be present
# Standard VGA Device:
Section “Device”
Identifier “Standard VGA”
VendorName “Unknown”
BoardName “Unknown”# The chipset line is optional in most cases. It can be used to override
# the driver’s chipset detection, and should not normally be specified.# Chipset “generic”
# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.Driver “vga”
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn’t present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# installed.# BusID “PCI:0:10:0”
# VideoRam 256
# Clocks 25.2 28.3
EndSection
# === ATI device section ===
Section “Device”
Identifier “ATI Graphics Adapter”
Driver “fglrx”
# ### generic DRI settings ###
# === disable PnP Monitor ===
#Option “NoDDC”
# === disable/enable XAA/DRI ===
Option “no_accel” “no”
Option “no_dri” “no”
# === misc DRI settings ===
……………………..Pokusao sam da remujem Strandard vga device da bi mu ostao samo fglrx zapravo da koristi ati device…. Ali dobijam istu stvar. Sta je sa agpgart modulom? A i fglrx.o je ponekad unused. Nije mi jasno…
Inace kada pokrenem ati-*.run ne dobijem instalaciju u grafickom okruzenju. Verovatno zato sto teram kao root@slack. U koliko pokrenem ati-*run kao user otvorimi se instalacija u X-u ali javlja mi da moram da budem super-user…
Evo vam deo mog xorg.conf-a… Jel trebam nesto da zamenim?
Ne znam u cemu je problem?! /dev/shm imam u fstab-u. I naravno da sam isao u /lib/modules/fglrx i odradio make.sh i make_install.sh.
Kad se make_install.sh zavrsi dobijem nesto kao: modul je ucital ali fglrx.o nije pod GPL licencom… Tako nesto… Nije ni bitno.evo ga lsmod:
fglrx 374728 0
agpgart 20344 0 (unused)
Ne znam da li je to ok?U /etc/X11/xorg.conf sam za driver skinuo onaj njegov “vga” i ostavio samo fglrx medjutim ista stvar…
Dobijam samo ovo:
nenad@slack:~$ fglrxinfo
Xlib: extension “GLX” missing on display “:0.0”.
Xlib: extension “GLX” missing on display “:0.0”.
Error: couldn’t find RGB GLX visual!nenad@slack:~$ glxgears
Xlib: extension “GLX” missing on display “:0.0”.
glxgears: Error: couldn’t get an RGB, Double-buffered visual.Sta sad? Kako? Gde?
Mislim da to zavisi od fajlova koje imas na disku… I naravno fajl systema.
I na kraju kakva je razlika? Sta dobijas sa 256, ili 8?A sta je sa mojim problemom? Zasto gubim dma kad k3b zavrsi posao?
readahead = 256 (on) Koji je to disk?
Kod mene je readahead = 8 (on) i na ata i sata disku. Sta predstavlja readhed?Da je ostavljen kao kao /dev/sda onda bi konsultovao sdparm, pa bi se možda iz toga moglo zaključiti šta ne valja.
Nego kažeš readahead=8 (on) koliki bi trebalo da je, verovatno ne prolazi -c1
System je na /dev/hda (ide-ata). Kada se system instalira on (sata) disk vidi kao (sda). i hdparm za /dev/sda javlja:
multcount = 16 (on)
IO_support = 1 (16-bit)
unmaskirq = 1 (on)
using_dma = 1 (off)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 8 (on)
geometry = 36483/255/63, sectors = 300090728448, start = 0Da bi mi disk radio sa “IO_support 32Bit” i koristio “dma” ucito sam modul “sata_nv.o” i jos jedan “sata_nesto.o”. Tako sam dobio cuveni “hde” Neznam sad koji tacno ubacio sam ga u kernel. Neznam sta te tacno interesuje sa “fdisk /dev/sda” ?
System je na /dev/hda (ide-ata). Kada se system instalira on (sata) disk vidi kao (sda). i hdparm za /dev/sda javlja:
multcount = 16 (on)
IO_support = 1 (16-bit)
unmaskirq = 1 (on)
using_dma = 1 (off)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 8 (on)
geometry = 36483/255/63, sectors = 300090728448, start = 0Da bi mi disk radio sa “IO_support 32Bit” i koristio “dma” ucito sam modul “sata_nv.o” i jos jedan “sata_nesto.o”. Tako sam dobio cuveni “hde” Neznam sad koji tacno ubacio sam ga u kernel. Neznam sta te tacno interesuje sa “fdisk /dev/sda” ?
