Hi all,
I'm having a problem with 2.6.0-test9 and DRI. dmesg tells me:
[drm] Initialized radeon 1.9.0 20020828 on minor 0
[drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held
[drm:radeon_unlock] *ERROR* Process 4113 using kernel context 0
the process listed is (of course) X. but there's more interesting stuff
in my X logs:
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 6, (OK)
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 6, (OK)
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 6, (OK)
drmGetBusid returned ''
(II) RADEON(0): [drm] created "radeon" driver at busid "PCI:1:5:0"
(II) RADEON(0): [drm] added 8192 byte SAREA at 0xf893b000
(II) RADEON(0): [drm] mapped SAREA 0xf893b000 to 0x423ef000
(II) RADEON(0): [drm] framebuffer handle = 0xf0000000
(II) RADEON(0): [drm] added 1 reserved context for kernel
(WW) RADEON(0): [agp] AGP not available
(II) RADEON(0): [drm] removed 1 reserved context for kernel
(II) RADEON(0): [drm] unmapping 8192 bytes of SAREA 0xf893b000 at
0x423ef000
(II) RADEON(0): Memory manager initialized to (0,0) (1280,6553)
(II) RADEON(0): Reserved area from (0,1024) to (1280,1026)
(II) RADEON(0): Largest offscreen area available: 1280 x 5527
(II) RADEON(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
Scanline Image Writes
Offscreen Pixmaps
Setting up tile and stipple cache:
32 128x128 slots
32 256x256 slots
16 512x512 slots
(II) RADEON(0): Acceleration enabled
(==) RADEON(0): Backing store disabled
(==) RADEON(0): Silken mouse enabled
(II) RADEON(0): Using hardware cursor (scanline 1026)
(II) RADEON(0): Largest offscreen area available: 1280 x 5523
(II) RADEON(0): Direct rendering disabled
of particular worry to me, though i'm not a kernel hacker, is the line
[agp] AGP not available. and of course at the end it tells me in no
uncertain terms that it's disabling DRI :-/. I know this worked in
2.4.x but i haven't used it in a long time (been using 2.5 since 2.5.64)
and i don't know if it ever worked there (I'm just getting around to
setting it back up again - i don't game much)
anyway, some more information:
this is a 2-cpu machine, AMD MP2000+'s on a Tyan Tiger MPX board
(AMD-760MPX chipset ) 4xAGP, Radeon AIW (the original one, so i suspect
7200. certainly r200, which afaik requires no proprietary drivers at all
for dri to work. Perhaps it is an smp issue? anyway, here's my kernel
config:
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
CONFIG_STANDALONE=y
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSCTL=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_KALLSYMS=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_OBSOLETE_MODPARM=y
CONFIG_KMOD=y
CONFIG_X86_PC=y
CONFIG_MK7=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_USE_3DNOW=y
CONFIG_SMP=y
CONFIG_PREEMPT=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_TSC=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_P4THERMAL=y
CONFIG_EDD=y
CONFIG_HIGHMEM4G=y
CONFIG_HIGHMEM=y
CONFIG_HIGHPTE=y
CONFIG_MTRR=y
CONFIG_HAVE_DEC_LOCK=y
CONFIG_PM=y
CONFIG_SOFTWARE_SUSPEND=y
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_FAN=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
CONFIG_ACPI_DEBUG=y
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y
CONFIG_PCI=y
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_NAMES=y
CONFIG_HOTPLUG=y
CONFIG_PCMCIA=y
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_MISC=y
CONFIG_PARPORT=y
CONFIG_PARPORT_PC=y
CONFIG_PARPORT_PC_CML1=y
CONFIG_PARPORT_PC_FIFO=y
CONFIG_PARPORT_1284=y
CONFIG_PNP=y
CONFIG_BLK_DEV_FD=y
CONFIG_BLK_DEV_LOOP=y
CONFIG_LBD=y
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_BLK_DEV_IDECD=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_GENERIC=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
CONFIG_IDEDMA_PCI_AUTO=y
CONFIG_BLK_DEV_ADMA=y
CONFIG_BLK_DEV_AMD74XX=y
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_IDEDMA_AUTO=y
CONFIG_SCSI=m
CONFIG_SCSI_PROC_FS=y
CONFIG_NET=y
CONFIG_PACKET=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IPV6_SCTP__=y
CONFIG_NETDEVICES=y
CONFIG_DUMMY=m
CONFIG_NET_ETHERNET=y
CONFIG_MII=m
CONFIG_NET_VENDOR_3COM=y
CONFIG_VORTEX=m
CONFIG_NET_PCI=y
CONFIG_E100=y
CONFIG_NET_PCMCIA=y
CONFIG_PCMCIA_PCNET=y
CONFIG_INPUT=y
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_CORE=y
CONFIG_UNIX98_PTYS=y
CONFIG_PRINTER=y
CONFIG_I2C=m
CONFIG_I2C_AMD756=m
CONFIG_I2C_AMD8111=m
CONFIG_I2C_SENSOR=m
CONFIG_SENSORS_W83781D=m
CONFIG_HW_RANDOM=y
CONFIG_AGP=m
CONFIG_AGP_AMD=m
CONFIG_AGP_VIA=m
CONFIG_DRM=y
CONFIG_DRM_RADEON=m
CONFIG_VIDEO_DEV=m
CONFIG_VIDEO_SELECT=y
CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_SOUND=y
CONFIG_SND=m
CONFIG_SND_SEQUENCER=m
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_EMU10K1=m
CONFIG_USB=m
CONFIG_USB_DEVICEFS=y
CONFIG_USB_BANDWIDTH=y
CONFIG_USB_EHCI_HCD=m
CONFIG_USB_OHCI_HCD=m
CONFIG_USB_HID=m
CONFIG_USB_HIDINPUT=y
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_JBD=y
CONFIG_FS_MBCACHE=y
CONFIG_FS_POSIX_ACL=y
CONFIG_AUTOFS4_FS=y
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_UDF_FS=y
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_NTFS_FS=m
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_DEVFS_FS=y
CONFIG_DEVFS_MOUNT=y
CONFIG_DEVPTS_FS=y
CONFIG_TMPFS=y
CONFIG_RAMFS=y
CONFIG_NFS_FS=y
CONFIG_NFSD=y
CONFIG_LOCKD=y
CONFIG_EXPORTFS=y
CONFIG_SUNRPC=y
CONFIG_SMB_FS=y
CONFIG_MSDOS_PARTITION=y
CONFIG_SMB_NLS=y
CONFIG_NLS=y
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_ISO8859_1=y
CONFIG_DEBUG_SPINLOCK_SLEEP=y
CONFIG_FRAME_POINTER=y
CONFIG_X86_EXTRA_IRQS=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
CONFIG_CRC32=y
CONFIG_X86_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_TRAMPOLINE=y
CONFIG_PC=y
I apologize wholeheartedly if this is a simple misconfiguration issue on
my part. this is my first post to the list.
thanks everyone and great work as always.
-Aubin
On Sun, 23 Nov 2003, Aubin LaBrosse wrote:
> Hi all,
>
> I'm having a problem with 2.6.0-test9 and DRI. dmesg tells me:
>
> [drm] Initialized radeon 1.9.0 20020828 on minor 0
> [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held
> [drm:radeon_unlock] *ERROR* Process 4113 using kernel context 0
For my curiosity, can you try compiling the Radeom/drm and AGP driver into
the kernel?
> anyway, some more information:
>
> this is a 2-cpu machine, AMD MP2000+'s on a Tyan Tiger MPX board
> (AMD-760MPX chipset ) 4xAGP, Radeon AIW (the original one, so i suspect
> 7200. certainly r200, which afaik requires no proprietary drivers at all
> for dri to work. Perhaps it is an smp issue? anyway, here's my kernel
> config:
I just tried test9-mm5 with a radeon 9000 on an smp machine with the
desired results.
On Sun, 2003-11-23 at 13:15, Zwane Mwaikambo wrote:
> On Sun, 23 Nov 2003, Aubin LaBrosse wrote:
>
> > Hi all,
> >
> > I'm having a problem with 2.6.0-test9 and DRI. dmesg tells me:
> >
> > [drm] Initialized radeon 1.9.0 20020828 on minor 0
> > [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held
> > [drm:radeon_unlock] *ERROR* Process 4113 using kernel context 0
>
> For my curiosity, can you try compiling the Radeom/drm and AGP driver into
> the kernel?
I have done it both ways with the same results, sorry, should have
mentioned that...
>
> > anyway, some more information:
> >
> > this is a 2-cpu machine, AMD MP2000+'s on a Tyan Tiger MPX board
> > (AMD-760MPX chipset ) 4xAGP, Radeon AIW (the original one, so i suspect
> > 7200. certainly r200, which afaik requires no proprietary drivers at all
> > for dri to work. Perhaps it is an smp issue? anyway, here's my kernel
> > config:
>
> I just tried test9-mm5 with a radeon 9000 on an smp machine with the
> desired results.
I will give -mm5 a shot (this was with stock 2.6.0-test9, i haven't
gotten into applying the -bk patches as soon as they hit, yet) Though
I'm not sure -mm5 has any patches specific to DRI or agp, but it's
definitely worth a shot. thanks Zwane.
-Aubin
> of particular worry to me, though i'm not a kernel hacker, is the line
> [agp] AGP not available.
Did you modprobe the amd-k7-agp module as well as agpgart ?
Dave
On Sun, 2003-11-23 at 14:37, Dave Jones wrote:
> > of particular worry to me, though i'm not a kernel hacker, is the line
> > [agp] AGP not available.
>
> Did you modprobe the amd-k7-agp module as well as agpgart ?
>
> Dave
>
sigh. sorry Dave - got it with that module. though i swear it didn't
work either when compiled into the kernel (as that was my first test,
though that was with 2.6.0-test9 and not -mm5 that i am running now.
anyway, problem solved, sorry for the noise and thanks for your help
guys
-Aubin
On Sun, 23 Nov 2003, Aubin LaBrosse wrote:
> > > [drm] Initialized radeon 1.9.0 20020828 on minor 0
> > > [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held
> > > [drm:radeon_unlock] *ERROR* Process 4113 using kernel context 0
> >
> > For my curiosity, can you try compiling the Radeom/drm and AGP driver into
> > the kernel?
>
> I have done it both ways with the same results, sorry, should have
> mentioned that...
Ok let me double check things here, my radeon 9000 is also R200 so we
should be hitting the same code paths.
> > I just tried test9-mm5 with a radeon 9000 on an smp machine with the
> > desired results.
>
> I will give -mm5 a shot (this was with stock 2.6.0-test9, i haven't
> gotten into applying the -bk patches as soon as they hit, yet) Though
> I'm not sure -mm5 has any patches specific to DRI or agp, but it's
> definitely worth a shot. thanks Zwane.
As far as i know it shouldn't make any difference, but being on the same
tree doesn't hurt for now.
Good luck,
Zwane
That make it ... work...
why was it not documented somewhere??
TMC
On Sun, Nov 23, 2003 at 07:37:24PM +0000, Dave Jones wrote:
> > of particular worry to me, though i'm not a kernel hacker, is the line
> > [agp] AGP not available.
>
> Did you modprobe the amd-k7-agp module as well as agpgart ?
>
> Dave
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Tomasz M. Ciolek
*******************************************************************************
email: tmc at dreamcraft dot com dot au
*******************************************************************************
GPG Key ID: 0x41C4C2F0 Key available on http://www.pgp.net
*******************************************************************************
Everything falls under the law of change;
Like a dream, a phantom, a bubble, a shadow,
like dew of flash of lightning.
You should contemplate like this.
On Sat, Nov 29, 2003 at 08:24:25PM +1100, Tomasz Ciolek wrote:
> That make it ... work...
>
> why was it not documented somewhere??
For 2.4 -> 2.6 transition, the definitive document is at
http://www.codemonkey.org.uk/docs/post-halloween-2.6.txt
This, and many other changes are all there.
Dave