Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

DRMKMS: NetBSD-current 201501242100 (7.99.4) and ATI Radeon HD 5450



Hi,

I tried out the GENERIC kernel of current-201501242100. The good news is that the KMS seems to work:
...
match_bootwedge: unable to read block 65 of dev dk6 (5)
boot device: sd2
root on sd2a dumps on sd2b
root file system type: ffs
kern.module.path=/stand/amd64/7.99.4/modules
drm: initializing kernel modesetting (CEDAR 0x1002:0x68F9 0x1787:0x2291).
drm: register mmio base: 0xfea20000
drm: register mmio size: 131072
drm kern info: ATOM BIOS: CEDAR
radeon0: info: VRAM: 2048M 0x0000000000000000 - 0x000000007FFFFFFF (2048M used)
radeon0: info: GTT: 1024M 0x0000000080000000 - 0x00000000BFFFFFFF
drm: Detected VRAM RAM=800M, BAR=256M
drm: RAM width 64bits DDR
Zone  kernel: Available graphics memory: 11587444 kiB
Zone   dma32: Available graphics memory: 2097152 kiB
drm: radeon: 2048M of VRAM memory ready
drm: radeon: 1024M of GTT memory ready.
drm: Loading CEDAR Microcode
drm: Internal thermal controller with fan control
drm: radeon: dpm initialized
drm: GART: num cpu pages 262144, num gpu pages 262144
drm: PCIE GART of 1024M enabled (table at 0x000000000025D000).
radeon0: info: WB enabled
radeon0: info: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0x0xffff80023ccddc00 radeon0: info: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0x0xffff80023ccddc0c radeon0: info: fence driver on ring 5 use gpu addr 0x000000000005c418 and cpu addr 0x0xffff80023c8dc418
drm: Supports vblank timestamp caching Rev 2 (21.10.2013).
drm: Driver supports precise vblank timestamp query.
radeon0: interrupting at ioapic1 pin 0 (radeon)
drm: radeon: irq initialized.
drm: ring test on 0 succeeded in 1 usecs
drm: ring test on 3 succeeded in 1 usecs
drm: ring test on 5 succeeded in 1 usecs
drm: UVD initialized successfully.
drm: ib test on ring 0 succeeded in 0 usecs
drm: ib test on ring 3 succeeded in 0 usecs
drm: ib test on ring 5 succeeded
drm: Radeon Display Connectors
drm: Connector 0:
drm:   HDMI-A-1
drm:   HPD2
drm:   DDC: 0x6440 0x6440 0x6444 0x6444 0x6448 0x6448 0x644c 0x644c
drm:   Encoders:
drm:     DFP1: INTERNAL_UNIPHY1
drm: Connector 1:
drm:   DVI-D-1
drm:   HPD4
drm:   DDC: 0x6460 0x6460 0x6464 0x6464 0x6468 0x6468 0x646c 0x646c
drm:   Encoders:
drm:     DFP2: INTERNAL_UNIPHY
drm: Connector 2:
drm:   VGA-1
drm:   DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438 0x643c 0x643c
drm:   Encoders:
drm:     CRT1: INTERNAL_KLDSCP_DAC1
radeondrmkmsfb0 at radeon0
radeon0: info: registered panic notifier
radeondrmkmsfb0: framebuffer at 0xffff80023ceff000, size 2560x1440, depth 32, stride 10240 wsdisplay0 at radeondrmkmsfb0 kbdmux 1: console (default, vt100 emulation), using wskbd0
wsmux1: connecting to wsdisplay0
wsdisplay0: screen 1 added (default, vt100 emulation)
wsdisplay0: screen 2 added (default, vt100 emulation)
wsdisplay0: screen 3 added (default, vt100 emulation)
wsdisplay0: screen 4 added (default, vt100 emulation)
...

The radeondrmkmsfb0 driver is correctly initialize and a big consolescreen of 2560x1440 correctly appears.

Unfortunately "X -configure" fails to detect any card.
The RADEON driver shortly lists the supported chipsets
but does not go on with the initialization.

Compiling GENERIC with "radeondrm* at drm?" fails
due to macro redefinitions. (with radeondrm in 7.99.1 the
Xserver was able to initialize the radeon driver).

Both Xservers find the card in the PCI bus as:
7.99.1:
[ 52.580] (--) PCI:*(1:1:0:0) 1002:68f9:1787:2291 rev 0, Mem @ 0xd0000000/268435456, 0xfea20000/131072, I/O @ 0x0000e000/256, BIOS @ 0x????????/131072

7.99.4:
[ 655.185] (--) PCI:*(1:1:0:0) 1002:68f9:1787:2291 rev 0, Mem @ 0xd0000000/268435456, 0xfea20000/131072, I/O @ 0x0000e000/256, BIOS @ 0x????????/131072

Is there anything else I need to chant as magic words?

Best regards,
  Frank


Home | Main Index | Thread Index | Old Index