Re: amd64 current can't configure a FFSv1 disk (and radeon success!)

[mlh%goathill.org@localhost (MLH)]

Martin Husemann wrote:
> On Sat, Dec 20, 2014 at 06:43:03AM -0500, MLH wrote:
> > > Might this be using an i386 /dev on amd64, which has different minor
> > > offsets for disks?
> 
> They look wrong for amd64 - however that happened.
> 
> > How would I determine that? /dev/ on this drive (wd0) was installed
> > from an amd64 install and I've reinstalled the complete amd64
> > distribution a couple of times since then.
> 
> Make sure you have an up to date /dev/MAKEDEV script (postinstall can
> verify and fix that), then do (as root):
> 
> cd /dev
> rm {r,}wd{0,1}?
> sh MAKEDEV wd0 wd1
> ls -l {r,}wd{0,1}d

That fixed it. Thanks. 

I had used the instructions at netbsd.org for building an install
cd for amd64 but something apparently is wrong with the instructions
for current and it never could access the new (wd0) drive to
partition and install so nothing was installed. I ended up grabbing
a -current amd64 iso install from I think in November and used
that. That cd (from the iso) installed amd64 but apparently didn't
have the updated MAKEDEV script so couldn't access wd1.

BTW, the latest amd64 -current can use my Radeon HD6450 now! I've
been trying to get that to work for over a year.

radeon0 at pci1 dev 0 function 0: vendor 1002 product 6779 (rev. 0x00)

drm: initializing kernel modesetting (CAICOS 0x1002:0x6779 0x1682:0x3200).
drm: register mmio base: 0xfbec0000
drm: register mmio size: 131072
drm kern info: ATOM BIOS: C28506
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: 1414156 kiB
drm: radeon: 2048M of VRAM memory ready
drm: radeon: 1024M of GTT memory ready.
drm: Loading CAICOS Microcode
drm: Internal thermal controller without fan control
drm: GART: num cpu pages 262144, num gpu pages 262144
drm: PCIE GART of 1024M enabled (table at 0x0000000000273000).
radeon0: info: WB enabled
radeon0: info: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0x0xffff800049ecac00
radeon0: info: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0x0xffff800049ecac0c
radeon0: info: fence driver on ring 5 use gpu addr 0x0000000000072118 and cpu addr 0x0xffff800049f92118
drm: Supports vblank timestamp caching Rev 2 (21.10.2013).
drm: Driver supports precise vblank timestamp query.
radeon0: interrupting at ioapic0 pin 16 (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:   HPD4
drm:   DDC: 0x6460 0x6460 0x6464 0x6464 0x6468 0x6468 0x646c 0x646c
drm:   Encoders:
drm:     DFP1: INTERNAL_UNIPHY1
drm: Connector 1:
drm:   DVI-I-1
drm:   HPD1
drm:   DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438 0x643c 0x643c
drm:   Encoders:
drm:     DFP2: INTERNAL_UNIPHY
drm: Connector 2:
drm:   VGA-1
drm:   DDC: 0x6440 0x6440 0x6444 0x6444 0x6448 0x6448 0x644c 0x644c
drm:   Encoders:
drm:     CRT1: INTERNAL_KLDSCP_DAC1
radeondrmkmsfb0 at radeon0
radeon0: info: registered panic notifier
radeondrmkmsfb0: framebuffer at 0xffff80004a5b3000, size 1920x1200, depth 32, stride 7680
wsdisplay0 at radeondrmkmsfb0 kbdmux 1: console (default, vt100 emulation),
using wskbd0
wsmux1: connecting to wsdisplay0
wsdisplay0: screen 4 added (default, vt100 emulation)

And it appears to be pretty stable so far.

HDMI-0 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 518mm x 324mm
DVI-0 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 518mm x 324mm