Current-Users archive

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

Re: amd64 radeondrmkms near-invisble text

On Mon, 23 Feb 2015, Masanobu SAITOH wrote:

>  Perhaps the problem is the same as my machines' problem reported in:
>  The cursor is bridght but others are very dark. It's too dark
> to read even if I gazing the text.

Yes, that seems to be the same.  My Dell PowerEdge 2950 behaves the
same way.

NetBSD 7.99.5 (GENERIC) #222: Fri Feb 20 06:13:41 CST 2015
total memory = 8191 MB
avail memory = 7934 MB
Dell Inc. PowerEdge 2950
radeon0 at pci15 dev 13 function 0: ATI Technologies ES1000 (rev. 0x02)
drm: initializing kernel modesetting (RV100 0x1002:0x515E 0x1028:0x01B2).
drm: register mmio base: 0xfc1f0000
drm: register mmio size: 65536
radeon0: info: VRAM: 128M 0x00000000D0000000 - 0x00000000D7FFFFFF (16M used)
radeon0: info: GTT: 512M 0x00000000B0000000 - 0x00000000CFFFFFFF
drm: Detected VRAM RAM=80M, BAR=128M
drm: RAM width 16bits DDR
Zone  kernel: Available graphics memory: 2829174 kiB
Zone   dma32: Available graphics memory: 2097152 kiB
drm: radeon: 16M of VRAM memory ready
drm: radeon: 512M of GTT memory ready.
drm: GART: num cpu pages 131072, num gpu pages 131072
drm: PCI GART of 512M enabled (table at 0x000000004490A000).
radeon0: info: WB disabled
radeon0: info: fence driver on ring 0 use gpu addr 0x00000000b0000000 and cpu addr 0x0xffff800096e36000
drm: Supports vblank timestamp caching Rev 2 (21.10.2013).
drm: Driver supports precise vblank timestamp query.
radeon0: interrupting at ioapic0 pin 19 (radeon)
drm: radeon: irq initialized.
drm: Loading R100 Microcode
drm: radeon: ring at 0x00000000B0001000
drm: ring test succeeded in 1 usecs
drm: ib test succeeded in 0 usecs
drm: Radeon Display Connectors
drm: Connector 0:
drm:   VGA-1
drm:   DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60 0x60
drm:   Encoders:
drm:     CRT1: INTERNAL_DAC1
radeondrmkmsfb0 at radeon0
radeon0: info: registered panic notifier
radeondrmkmsfb0: framebuffer at 0xffff800097237000, size 1024x768, depth 8, stride 1024
wsdisplay0 at radeondrmkmsfb0 kbdmux 1: console (default, vt100 emulation), using wskbd0
wsmux1: connecting to wsdisplay0
wskbd1: connecting to wsdisplay0
wskbd2: connecting to wsdisplay0

Odd thing I discovered about the HP DL380 G5:  If "/dev/console" exists
on the root filesystem (ffs or nfs), the kernel panics with "cnopen: no
console device".  If "/dev" is run-time-populated tmpfs, radeondrmkmsfb
attaches and provides a working (although almost invisibly dim) console.

|/"\ John D. Baker, KN5UKS               NetBSD     Darwin/MacOS X
|\ / jdbaker[snail]mylinuxisp[flyspeck]com    OpenBSD            FreeBSD
| X  No HTML/proprietary data in email.   BSD just sits there and works!
|/ \ GPGkeyID:  D703 4A7E 479F 63F8 D3F4  BD99 9572 8F23 E4AD 1645

Home | Main Index | Thread Index | Old Index