DaemonForums  

Go Back   DaemonForums > OpenBSD > OpenBSD General

OpenBSD General Other questions regarding OpenBSD which do not fit in any of the categories below.

Reply
 
Thread Tools Display Modes
  #1   (View Single Post)  
Old 14th November 2010
Svejk Svejk is offline
New User
 
Join Date: Nov 2010
Posts: 3
Thanked 0 Times in 0 Posts
Default Bug in libdrm with intel 865G chipset.

Greetings.

I've recently loaded OpenBSD 4.8 on an old box (HP D330, intel 865G chipset, integrated video) they gave away at work. The point of using OpenBSD is to learn about aspects of computing that I've always taken for granted. So far, that's happening. Nothing important depends on getting it working, and I have no deadlines. I'm doing my best to RTFM and rely on my own abilities, small as they are at the moment.

I've installed XFCE from packages. However, it appears to lock up after a short period of use. After reading and googling, I think I've located the trouble, which seems to be a bug in libdrm. It appears to be fixed in the libdrm put out by the linuxintelgraphics.com people, but that's outside the OpenBSD project. Looking for some advice on best way to proceed.

First, the dmesg, just for reference.

Code:
OpenBSD 4.8 (GENERIC.MP) #359: Mon Aug 16 09:16:26 MDT 2010
    deraadt@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel(R) Pentium(R) 4 CPU 3.20GHz ("GenuineIntel" 686-class) 3.20 GHz
cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,CNXT-ID,xTPR
real mem  = 3212341248 (3063MB)
avail mem = 3149815808 (3003MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 08/07/08, BIOS32 rev. 0 @ 0xeb0e0, SMBIOS rev. 2.3 @ 0xfd4aa (59 entries)
bios0: vendor Hewlett-Packard version "786B2 v2.44" date 08/07/2008
bios0: Hewlett-Packard HP d330 uT(DC579AV)
acpi0 at bios0: rev 0
acpi0: sleep states S0 S1 S3 S4 S5
acpi0: tables DSDT FACP SSDT SSDT SSDT SSDT SSDT SSDT SSDT APIC SSDT ASF! SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT
acpi0: wakeup devices PCI0(S4) HUB_(S4) COM1(S4) COM2(S4) USB1(S3) USB2(S3) USB3(S3) USB4(S3) EUSB(S3) PBTN(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 199MHz
ioapic0 at mainbus0: apid 1 pa 0xfec00000, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 1
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 5 (HUB_)
acpicpu0 at acpi0
acpibtn0 at acpi0: PBTN
bios0: ROM list: 0xc0000/0xa000! 0xca000/0x1000 0xcb000/0x1000 0xe0c00/0x9400!
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82865G Host" rev 0x02
vga1 at pci0 dev 2 function 0 "Intel 82865G Video" rev 0x02
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
intagp0 at vga1
agp0 at intagp0: aperture at 0xf0000000, size 0x8000000
inteldrm0 at vga1: apic 1 int 16 (irq 5)
drm0 at inteldrm0
uhci0 at pci0 dev 29 function 0 "Intel 82801EB/ER USB" rev 0x02: apic 1 int 16 (irq 5)
uhci1 at pci0 dev 29 function 1 "Intel 82801EB/ER USB" rev 0x02: apic 1 int 19 (irq 10)
uhci2 at pci0 dev 29 function 2 "Intel 82801EB/ER USB" rev 0x02: apic 1 int 18 (irq 10)
ehci0 at pci0 dev 29 function 7 "Intel 82801EB/ER USB2" rev 0x02: apic 1 int 23 (irq 11)
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb0 at pci0 dev 30 function 0 "Intel 82801BA Hub-to-PCI" rev 0xc2
pci1 at ppb0 bus 5
bge0 at pci1 dev 2 function 0 "Broadcom BCM5782" rev 0x03, BCM5705 A3 (0x3003): apic 1 int 20 (irq 5), address 00:0d:9d:da:0f:cd
brgphy0 at bge0 phy 1: BCM5705 10/100/1000baseT PHY, rev. 2
em0 at pci1 dev 9 function 0 "Intel PRO/1000GT (82541GI)" rev 0x05: apic 1 int 18 (irq 10), address 00:1b:21:18:79:1b
em1 at pci1 dev 10 function 0 "Intel PRO/1000GT (82541GI)" rev 0x05: apic 1 int 21 (irq 11), address 00:1b:21:18:7b:ba
ichpcib0 at pci0 dev 31 function 0 "Intel 82801EB/ER LPC" rev 0x02
pciide0 at pci0 dev 31 function 2 "Intel 82801EB SATA" rev 0x02: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility
atapiscsi0 at pciide0 channel 0 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: <HP, DVD Writer 1260d, KH25> ATAPI 5/cdrom removable
wd0 at pciide0 channel 0 drive 1: <WDC WD1600AAJS-60M0A0>
wd0: 16-sector PIO, LBA48, 152627MB, 312581808 sectors
cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
wd0(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 5
auich0 at pci0 dev 31 function 5 "Intel 82801EB/ER AC97" rev 0x02: apic 1 int 17 (irq 10), ICH5 AC97
ac97: codec id 0x41445374 (Analog Devices AD1981B)
ac97: codec features headphone, 20 bit DAC, No 3D Stereo
audio0 at auich0
usb1 at uhci0: USB revision 1.0
uhub1 at usb1 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb2 at uhci1: USB revision 1.0
uhub2 at usb2 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb3 at uhci2: USB revision 1.0
uhub3 at usb3 "Intel UHCI root hub" rev 1.00/1.00 addr 1
isa0 at ichpcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pmsi0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pmsi0 mux 0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
mtrr: Pentium Pro MTRR support
softraid0 at root
root on wd0a swap on wd0b dump on wd0b
umass0 at uhub0 port 6 configuration 1 interface 0 " Patriot Memory" rev 2.00/1.10 addr 2
umass0: using SCSI over Bulk-Only
scsibus1 at umass0: 2 targets, initiator 0
sd0 at scsibus1 targ 1 lun 0: <, Patriot Memory, PMAP> SCSI0 0/direct removable
sd0: 7640MB, 512 bytes/sec, 15646720 sec total
sd0 detached
scsibus1 detached
umass0 detached
syncing disks... 
OpenBSD 4.8 (RAMDISK_CD) #89: Mon Aug 16 09:24:20 MDT 2010
    deraadt@i386.openbsd.org:/usr/src/sys/arch/i386/compile/RAMDISK_CD
cpu0: Intel(R) Pentium(R) 4 CPU 3.20GHz ("GenuineIntel" 686-class) 3.20 GHz
cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,CNXT-ID,xTPR
real mem  = 3212341248 (3063MB)
avail mem = 3152891904 (3006MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 08/07/08, BIOS32 rev. 0 @ 0xeb0e0, SMBIOS rev. 2.3 @ 0xfd4aa (59 entries)
bios0: vendor Hewlett-Packard version "786B2 v2.44" date 08/07/2008
bios0: Hewlett-Packard HP d330 uT(DC579AV)
acpi0 at bios0: rev 0
acpi0: sleep states S0 S1 S3 S4 S5
acpi0: tables DSDT FACP SSDT SSDT SSDT SSDT SSDT SSDT SSDT APIC SSDT ASF! SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT
acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 199MHz
ioapic0 at mainbus0: apid 1 pa 0xfec00000, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 1
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 5 (HUB_)
bios0: ROM list: 0xc0000/0xa000! 0xca000/0x1000 0xcb000/0x1000 0xe0c00/0x9400!
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82865G Host" rev 0x02
vga1 at pci0 dev 2 function 0 "Intel 82865G Video" rev 0x02
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
uhci0 at pci0 dev 29 function 0 "Intel 82801EB/ER USB" rev 0x02: apic 1 int 16 (irq 5)
uhci1 at pci0 dev 29 function 1 "Intel 82801EB/ER USB" rev 0x02: apic 1 int 19 (irq 10)
uhci2 at pci0 dev 29 function 2 "Intel 82801EB/ER USB" rev 0x02: apic 1 int 18 (irq 10)
ehci0 at pci0 dev 29 function 7 "Intel 82801EB/ER USB2" rev 0x02: apic 1 int 23 (irq 11)
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb0 at pci0 dev 30 function 0 "Intel 82801BA Hub-to-PCI" rev 0xc2
pci1 at ppb0 bus 5
bge0 at pci1 dev 2 function 0 "Broadcom BCM5782" rev 0x03, BCM5705 A3 (0x3003): apic 1 int 20 (irq 5), address 00:0d:9d:da:0f:cd
brgphy0 at bge0 phy 1: BCM5705 10/100/1000baseT PHY, rev. 2
em0 at pci1 dev 9 function 0 "Intel PRO/1000GT (82541GI)" rev 0x05: apic 1 int 18 (irq 10), address 00:1b:21:18:79:1b
em1 at pci1 dev 10 function 0 "Intel PRO/1000GT (82541GI)" rev 0x05: apic 1 int 21 (irq 11), address 00:1b:21:18:7b:ba
ichpcib0 at pci0 dev 31 function 0 "Intel 82801EB/ER LPC" rev 0x02
pciide0 at pci0 dev 31 function 2 "Intel 82801EB SATA" rev 0x02: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility
atapiscsi0 at pciide0 channel 0 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: <HP, DVD Writer 1260d, KH25> ATAPI 5/cdrom removable
wd0 at pciide0 channel 0 drive 1: <WDC WD1600AAJS-60M0A0>
wd0: 16-sector PIO, LBA48, 152627MB, 312581808 sectors
cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
wd0(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 5
"Intel 82801EB/ER AC97" rev 0x02 at pci0 dev 31 function 5 not configured
usb1 at uhci0: USB revision 1.0
uhub1 at usb1 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb2 at uhci1: USB revision 1.0
uhub2 at usb2 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb3 at uhci2: USB revision 1.0
uhub3 at usb3 "Intel UHCI root hub" rev 1.00/1.00 addr 1
isa0 at ichpcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
rd0: fixed, 3800 blocks
softraid0 at root
root on rd0a swap on rd0b dump on rd0b
syncing disks... 
OpenBSD 4.8 (GENERIC) #136: Mon Aug 16 09:06:23 MDT 2010
    deraadt@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Pentium(R) 4 CPU 3.20GHz ("GenuineIntel" 686-class) 3.20 GHz
cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,CNXT-ID,xTPR
real mem  = 3212341248 (3063MB)
avail mem = 3149840384 (3003MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 08/07/08, BIOS32 rev. 0 @ 0xeb0e0, SMBIOS rev. 2.3 @ 0xfd4aa (59 entries)
bios0: vendor Hewlett-Packard version "786B2 v2.44" date 08/07/2008
bios0: Hewlett-Packard HP d330 uT(DC579AV)
acpi0 at bios0: rev 0
acpi0: sleep states S0 S1 S3 S4 S5
acpi0: tables DSDT FACP SSDT SSDT SSDT SSDT SSDT SSDT SSDT APIC SSDT ASF! SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT
acpi0: wakeup devices PCI0(S4) HUB_(S4) COM1(S4) COM2(S4) USB1(S3) USB2(S3) USB3(S3) USB4(S3) EUSB(S3) PBTN(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 199MHz
ioapic0 at mainbus0: apid 1 pa 0xfec00000, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 1
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 5 (HUB_)
acpicpu0 at acpi0
acpibtn0 at acpi0: PBTN
bios0: ROM list: 0xc0000/0xa000! 0xca000/0x1000 0xcb000/0x1000 0xe0c00/0x9400!
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82865G Host" rev 0x02
vga1 at pci0 dev 2 function 0 "Intel 82865G Video" rev 0x02
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
intagp0 at vga1
agp0 at intagp0: aperture at 0xf0000000, size 0x8000000
inteldrm0 at vga1: apic 1 int 16 (irq 5)
drm0 at inteldrm0
uhci0 at pci0 dev 29 function 0 "Intel 82801EB/ER USB" rev 0x02: apic 1 int 16 (irq 5)
uhci1 at pci0 dev 29 function 1 "Intel 82801EB/ER USB" rev 0x02: apic 1 int 19 (irq 10)
uhci2 at pci0 dev 29 function 2 "Intel 82801EB/ER USB" rev 0x02: apic 1 int 18 (irq 10)
ehci0 at pci0 dev 29 function 7 "Intel 82801EB/ER USB2" rev 0x02: apic 1 int 23 (irq 11)
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb0 at pci0 dev 30 function 0 "Intel 82801BA Hub-to-PCI" rev 0xc2
pci1 at ppb0 bus 5
bge0 at pci1 dev 2 function 0 "Broadcom BCM5782" rev 0x03, BCM5705 A3 (0x3003): apic 1 int 20 (irq 5), address 00:0d:9d:da:0f:cd
brgphy0 at bge0 phy 1: BCM5705 10/100/1000baseT PHY, rev. 2
em0 at pci1 dev 9 function 0 "Intel PRO/1000GT (82541GI)" rev 0x05: apic 1 int 18 (irq 10), address 00:1b:21:18:79:1b
em1 at pci1 dev 10 function 0 "Intel PRO/1000GT (82541GI)" rev 0x05: apic 1 int 21 (irq 11), address 00:1b:21:18:7b:ba
ichpcib0 at pci0 dev 31 function 0 "Intel 82801EB/ER LPC" rev 0x02
pciide0 at pci0 dev 31 function 2 "Intel 82801EB SATA" rev 0x02: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility
atapiscsi0 at pciide0 channel 0 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: <HP, DVD Writer 1260d, KH25> ATAPI 5/cdrom removable
wd0 at pciide0 channel 0 drive 1: <WDC WD1600AAJS-60M0A0>
wd0: 16-sector PIO, LBA48, 152627MB, 312581808 sectors
cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
wd0(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 5
auich0 at pci0 dev 31 function 5 "Intel 82801EB/ER AC97" rev 0x02: apic 1 int 17 (irq 10), ICH5 AC97
ac97: codec id 0x41445374 (Analog Devices AD1981B)
ac97: codec features headphone, 20 bit DAC, No 3D Stereo
audio0 at auich0
usb1 at uhci0: USB revision 1.0
uhub1 at usb1 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb2 at uhci1: USB revision 1.0
uhub2 at usb2 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb3 at uhci2: USB revision 1.0
uhub3 at usb3 "Intel UHCI root hub" rev 1.00/1.00 addr 1
isa0 at ichpcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pmsi0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pmsi0 mux 0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
mtrr: Pentium Pro MTRR support
softraid0 at root
root on wd0a swap on wd0b dump on wd0b
The box is not connected to a network, and other than adding the joe editor (okay, I'm a weenie and don't want to learn vi right now) and XFCE, I've not done anything to the box. I configured XFCE by adding a line to sudoers and implementing dbus in rc.local, both per instructions in the XFCE packages.

X worked out of the box, and I didn't need an xorg.conf file.

XFCE seems to load up fine, but will lock up after being used for a short time (< 5 minutes), particularly if I'm doing something like scrolling quickly through a large text file. Both keyboard and mouse freeze. Ctl-Alt-Bksp goes to a black screen, which tends to stay black for a long time (sorry, haven't timed it exactly). IF, however, I Ctl-F2 to a different screen then Ctl-F1 back, I have a page with error messages right away.

Here is a truncated Xorg.0.log, edited to show only the relevant error, since this post is pretty long.

Code:
[1113060.483] (WW) intel(0): i830_uxa_prepare_access: gtt bo map failed: Input/output error
[1113060.484] (EE) intel(0): Failed to submit batch buffer, expect rendering corruption or even a frozen display: Input/output error.
[1113072.510] (II) UnloadModule: "mouse"
[1113072.510] (II) UnloadModule: "kbd"
[1113072.709] (II) intel(0): xf86UnbindGARTMemory: unbind key 2
[1113072.709] 
Fatal server error:
[1113072.709] DRM_I915_LEAVEVT failed: Unknown error: -5
[1113072.709] 
[1113072.709] 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[1113072.709] Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[1113072.709] 
[1113072.966] 
FatalError re-entered, aborting
[1113072.966] DRM_I915_LEAVEVT failed: Unknown error: -5
[1113072.966]
Googling the error messages indicates that this is probably bug 25554 over at Freedesktop Bugzilla (sorry no link, not allowed yet), which they seem to think is actually in libdrm. The ANNOUNCE for libdrm 2.4.18 references this bug as fixed. The Xenocara 4.8 version of libdrm (from the Makefile.inc in source) seems to be 2.4.15 . The same behavior has been reported with other (graphical) programs, and on other (linux) platforms.

I've gone over to intellinuxgraphics.org and grabbed their latest stable libdrm release, which is 2.4.22 . The README in that package says:

Code:
libdrm - userspace library for drm

This  is libdrm,  a userspace  library for  accessing the  DRM, direct
rendering  manager, on  Linux,  BSD and  other  operating systes  that
support the  ioctl interface.  The library  provides wrapper functions
for the  ioctls to avoid  exposing the kernel interface  directly, and
for chipsets with drm memory manager, support for tracking relocations
and  buffers.   libdrm  is  a  low-level library,  typically  used  by
graphics drivers  such as the Mesa  DRI drivers, the  X drivers, libva
and  similar projects.  New  functionality in  the kernel  DRM drivers
typically requires  a new  libdrm, but a  new libdrm will  always work
with an older kernel.

Compiling
---------

libdrm  is  a  standard  autotools  packages and  follows  the  normal
configure, build  and install steps.   The first step is  to configure
the package, which is done by running the configure shell script:

	./configure

By default, libdrm  will install into the /usr/local/  prefix.  If you
want  to  install   this  DRM  to  replace  your   system  copy,  pass
--prefix=/usr and  --exec-prefix=/ to configure.  If  you are building
libdrm  from a  git checkout,  you first  need to  run  the autogen.sh
script.  You can  pass any options to autogen.sh  that you would other
wise  pass to configure,  or you  can just  re-run configure  with the
options you need once autogen.sh finishes.

Next step is to build libdrm:

	make

and once make finishes successfully, install the package using

	make install

If you are install into a system location, you will need to be root to
perform the install step.
Based on the first paragraph, I'm guessing that there's a chance it will run on OpenBSD.

I actually did grab the source for Xenocara and looked at libdrm in that tree. Yep, it's different. If I'm reading correctly, it's v. 2.4.15 . It also has only an intel subdirectory (probably not the right term), where the 2.4.22 version above has several (nouveau, radeon, etc.).

Anyway, that's why I think it's a problem in libdrm.

These seem to be the practical solutions:

1. Work around the bad libdrm by using a supported graphics card rather than the integrated graphics. I've found an older ATI-based card that ought to work based on the man page for the relevant driver, but don't have it in hand yet. If I just want a working system this is probably simplest.

2. Try to compile the new libdrm code into my system. This would be the way of adventure, learning, self-help and probably lots of pain. But not necessarily a bad thing, since this is a learning experience and if I hose the installation somehow, I'll just reinstall and try something else (falling back to solution 1 if need be).

3. Submit the bug to the OpenBSD project and hope for the best. I might should do this anyway, but since the devs don't work for me, it might take a while. Since I don't pay them, I'm not complaining about it.

So after all that, what am I asking -you- ?

1. Per 3 above, should I submit this as a bug to OpenBSD ? Not really a "solution" for the here-and-now, but would it be the responsible thing to do or just an annoyance since they probably update libdrm on their own schedule anyway?

2. Bearing in mind that I've never compiled anything in my life, but have the luxury of being able to play rat in a Skinner box, is it reasonable to think that compiling the 2.4.22 code from intellinuxgraphics.org might work? If yes,

a) should I compile that code standalone and install it into the existing system, or

b) should I cut the code into the Xenocara tree and compile it in a modular way from there? The Xenocara README says

Code:
If you have installed the full Xenocara X sets on your system, you
don't need to build all of Xenocara to patch one element. You can go
to any module sub-directory and run 'make build' from there.
There's no doubt in my mind that there's more reading to do before I am able to successfully compile anything, but at this point I'm wondering if it's reasonable to try it.

I am not asking about the supported card opton. It would probably get graphics up and running most quickly, but I doubt I'd learn anything from it.

Lots of talk for two questions, but context does help. Any other suggestions or words of wisdom would be gratefully received.

Oh, and in keeping with longstanding tradition, I emit the cry of the clueless n00b: PLEASE HELP!

Sorry, I promise I'll never do that again.

regards,

Svejk
Reply With Quote
  #2   (View Single Post)  
Old 14th November 2010
ocicat ocicat is offline
Administrator
 
Join Date: Apr 2008
Posts: 2,873
Thanked 190 Times in 160 Posts
Default

Quote:
Originally Posted by Svejk View Post
Looking for some advice on best way to proceed.
First of all, welcome to our community.

Because of the lead time required to manufacture/duplicate CD's, the code to OpenBSD 4.8 was tagged (frozen) in CVS back at the beginning of August. However, the project developers continue to work at the head of the source tree. This raises two points:
  • While the OpenBSD developers will be interested in errors found in OpenBSD-release (the code tagged in August...), the first question they will ask is what is the corresponding behavior seen at the head of the tree (-current). Before raising the flag of "bug", the immediate question to answer is whether ongoing work -current has already resolved this problem. Since most likely the developers don't have your hardware, the best immediate action you can take is to install a snapshot of -current yourself to verfiy whether the same behavior exists.

    If you are unclear as to the differences in OpenBSD's flavors (-release, -stable, & -current), study Section 5.1 of the official FAQ.
  • Note that this community is predominantly enthusiasts & hobbyists who have no official connection to the OpenBSD project. As such, we can make recommendations as to what course of action should be followed, & we may only have a working knowledge of the code involved. As such, we can make educated guesses if we don't know the exact issue.
Quote:
I actually did grab the source for Xenocara and looked at libdrm in that tree.
The way the XOrg Foundation is currently structured, each project is responsible for tweaking X to its own needs (OpenBSD's implementation of X is known as Xenocara...). How another project deals with DRM is of marginal value to OpenBSD.
Quote:
...should I submit this as a bug to OpenBSD ?
Two more points to consider:
  • If you do submit a report, study the information found on the reporting page:

    http://www.openbsd.org/report.html

    ...as you will see a faster response if you thoroughly explain the problem.
  • ...& part of doing the legwork should be installing -current to verify the behavior.
Quote:
...should I compile...
Many Linux projects give the illusion that compiling resolves problems. While compiling may need to done by someone at some point (even if indirectly by installing a snapshot of -current...), the OpenBSD project tends to focus on understanding the problem before blindly jumping into activities which are time-consuming. Bluntly, the answer to your question is that discussing compilation at this time is premature. Verifying on -current is time better spent.
Reply With Quote
  #3   (View Single Post)  
Old 14th November 2010
Svejk Svejk is offline
New User
 
Join Date: Nov 2010
Posts: 3
Thanked 0 Times in 0 Posts
Default

Quote:
First of all, welcome to our community.
Thank you. Pleasure to be here.

You recommend:

Quote:
While the OpenBSD developers will be interested in errors found in OpenBSD-release (the code tagged in August...), the first question they will ask is what is the corresponding behavior seen at the head of the tree (-current). Before raising the flag of "bug", the immediate question to answer is whether ongoing work -current has already resolved this problem. Since most likely the developers don't have your hardware, the best immediate action you can take is to install a snapshot of -current yourself to verfiy whether the same behavior exists.
I did check -current via Web CVS, and libdrm was last touched three months ago, and has the same version number that I do. I infer from that that -current would show the same behavior. Installing a snapshot would certainly be a valuable learning experience, but it seems a bit premature for me, and not likely to contribute to a solution of the immediate problem. Have I misunderstood something?

Oh, and as to "bug" ... the impression I have is that the bug is not in code written by the OpenBSD devs, but code written by someone else and ported to OpenBSD. I assume that a version upgrade in due course will fix it. For the record, I do not expect the devs to accomodate me by doing this ahead of whatever the regular schedule might be (or, indeed, at all if it's not a priority for them).

Quote:
Many Linux projects give the illusion that compiling resolves problems. While compiling may need to done by someone at some point (even if indirectly by installing a snapshot of -current...), the OpenBSD project tends to focus on understanding the problem before blindly jumping into activities which are time-consuming.
If I have interpreted the information in my original post properly (and if not, I would be glad of correction on specific points I've misunderstood), OpenBSD ports libdrm in from somewhere else (not sure if it's freedesktop or intellinuxgrapics), and the problem has been understood and solved by one of those projects. I understand that the development process has lag time, and I'm certainly not asking anyone to give my problem any priority, just looking tor things that I myself might do.

Now, playing with code rather than just putting in a video card is rather ... adventurous, perhaps? But is it wrong, under the circumstances?

Quote:
Verifying on -current is time better spent.
If the code in -current hasn't changed, is that still so? If so, how so?

Again, though I certainly need to learn to build a system from -current at some point, I don't see how that is less time-consuming, under the circumstances, than learning to compile some specific driver ... though of course there are no guarantees about that either.

Not intending to argue, just trying to understand. Thanks for your observations.

regards,

Svejk
Reply With Quote
  #4   (View Single Post)  
Old 14th November 2010
BSDfan666 BSDfan666 is offline
Real Name: N/A, this is the interweb.
Helpful companion
 
Join Date: Apr 2008
Location: Ontario, Canada
Posts: 2,223
Thanked 193 Times in 184 Posts
Default

Xenocara updates and other "experimental" things do go on in the snapshots before being committed to the public CVS tree.

As was previously stated, Xenocara is a "pick-and-choose" collection of the now modular X11R7 release from X.Org and contains OpenBSD specific patches that may or may not be in the upstream vanilla sources.

If you want to help, you could attempt to isolate the change that fixes your issue and apply it to the version of the libdrm in OpenBSD, posting a patch to tech@ or perhaps sending it to the primary Xenocara developer (Matthieu Herrb/matthieu@).

Alternatively, just email him and explain your situation.. maybe he can further assist you.
Reply With Quote
  #5   (View Single Post)  
Old 14th November 2010
Svejk Svejk is offline
New User
 
Join Date: Nov 2010
Posts: 3
Thanked 0 Times in 0 Posts
Default

Ah. I see that I have not read enough, nor carefully enough. I'll come back after I've studied more.

Thanks for the replies.

regards,

Svejk
Reply With Quote
  #6   (View Single Post)  
Old 14th November 2010
ocicat ocicat is offline
Administrator
 
Join Date: Apr 2008
Posts: 2,873
Thanked 190 Times in 160 Posts
Default

Quote:
Originally Posted by Svejk View Post
Installing a snapshot would certainly be a valuable learning experience, but it seems a bit premature for me, and not likely to contribute to a solution of the immediate problem. Have I misunderstood something?
The developers would prefer a patch which would fix the problem as it would indicate that you thoroughly understand the issue. However, the first question any developer will ask ask is "Does this run on -current?". If you submitted a patch developed solely on -release, this still leaves the above question very open.

From the developers' standpoint, -release or -stable is secondary. Most developers never run anything other than -current.
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Hardware nVidia closing chipset division? Carpetsmoker News 3 10th October 2009 01:52 PM
wpi firmware Intel eula plouk NetBSD General 7 4th July 2009 04:14 AM
OpenBSD 4.4 and Intel DRM Nightweaver OpenBSD General 8 19th October 2008 07:34 PM
Intel 775 MB For 20$ revzalot OpenBSD General 2 22nd July 2008 06:17 AM
Intel 4965 Business_woman FreeBSD Installation and Upgrading 9 2nd July 2008 02:49 PM


All times are GMT. The time now is 04:07 AM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content copyright © 2007-2010, the authors
Daemon image copyright ©1988, Marshall Kirk McKusick