Boot goes fine until the kernel is loaded. Once the kernel is loaded, boot continues, however only the very bottom line is showing kernel messages...the rest of the screen still "looks" like loader. Except that everything is working perfectly I don't know much about freebsd, but I would be more than happy to provide all data that is needed to solve this bug How-To-Repeat: buy a D2700DC motherboard (from intel) plug a disk with freebsd on it. Plug a screen and boot.
Just to add a few more details, this also happens (unsurprisingly) on a D2500. Testing with my D2500CC, I can confirm the issue occurs on both 9.0 and 8.2, and both in i386 and amd64. Also, interestingly, I can't get a very vanilla (GENERIC kernel and almost no configuration) install to even boot with a serial console and terminal. The only changes I made were adding "-Dh -S115200" to /boot.config and setting up a serial tty in /etc/ttys. The board repeatedly hangs (not a panic) after printing "Setting hostuuid", and if I disable hostid in rc.conf, it will repeatedly hang after printing "Envtropy harvesti" (sic)--coincidentally the exact same number of printed characters. It does still respond to interrupt though, as I can toggle Num Lock and it does recognize pressing the power button or plugging/unplugging USB devices. Let me know if you need any testing as I would love to get this board up and running.
I found an old PCI graphics card and did a bit more testing on the board. Firstly, though I definitely have the same display corruption as reported in this pr, I also have a issue with the serial console/terminal--or possibly with just serial interfaces in general--that I don't believe is related to the graphics issue, as it still occurs when using a PCI graphics card. However, I don't think I can entirely disable the integrated GPU, even when there is a PCI card plugged in, so I can't say for sure. So, in short, while I can confirm the graphics issue detailed in this pr, I think the serial issue is unrelated and I'll submit a separate pr for it.
On my D2500CC with current bios it only happens with 9.0R/amd64. I can successfully boot 9.0/i386 with minimal (single character) graphics corruption that can be worked around by switching syscons to 640x480. Unfortunately serial console goes blank as soon as kernel begins execution (both i386 and amd64). Trying to use conscontrol or "sysctl kern.console" gives "Device not configured". With 8.1R/amd64 serial console works but hangs during startup as noted above.
Correction: lack of serial console seems to be specific only to mfsBSD liveusb image. I've also observed that if you move mouse around the screen or select everything then contents will update (assuming moused is running).
Hello, Recently I got a new Acer D270 with an Intel Atom N2600 CPU, and have the exact same issue as the original reporter mentioned. Is there any update on this or fix/workaround? I'm having this issue with 9.0-RELEASE amd64. Any feedback is much appreciated. Thanks and regards, Marin -- Marin Atanasov Nikolov dnaeon AT gmail DOT com daemon AT unix-heaven DOT org http://www.unix-heaven.org/
I was able to make my screen working with : vidcontrol MODE_27 vidcontrol -f iso I'm not sure how to put that into rc.conf
Just in case that's useful for this bug : freebsd-test16# vidcontrol -i mode mode# flags type size font window linear = buffer = --------------------------------------------------------------------------= ---- 0 (0x000) 0x00000001 T 40x25 8x8 0xb8000 32k 32k = 0x00000000 32k 1 (0x001) 0x00000001 T 40x25 8x8 0xb8000 32k 32k = 0x00000000 32k 2 (0x002) 0x00000001 T 80x25 8x8 0xb8000 32k 32k = 0x00000000 32k 3 (0x003) 0x00000001 T 80x25 8x8 0xb8000 32k 32k = 0x00000000 32k 4 (0x004) 0x00000003 G 320x200x2 C 8x8 0xb8000 32k 32k = 0x00000000 32k 5 (0x005) 0x00000003 G 320x200x2 C 8x8 0xb8000 32k 32k = 0x00000000 32k 6 (0x006) 0x00000003 G 640x200x1 C 8x8 0xb8000 32k 32k = 0x00000000 32k 13 (0x00d) 0x00000003 G 320x200x4 4 8x8 0xa0000 64k 64k = 0x00000000 256k 14 (0x00e) 0x00000003 G 640x200x4 4 8x8 0xa0000 64k 64k = 0x00000000 256k 16 (0x010) 0x00000003 G 640x350x2 2 8x14 0xa0000 64k 64k = 0x00000000 128k 18 (0x012) 0x00000003 G 640x350x4 4 8x14 0xa0000 64k 64k = 0x00000000 256k 19 (0x013) 0x00000001 T 40x25 8x14 0xb8000 32k 32k = 0x00000000 32k 20 (0x014) 0x00000001 T 40x25 8x14 0xb8000 32k 32k = 0x00000000 32k 21 (0x015) 0x00000001 T 80x25 8x14 0xb8000 32k 32k = 0x00000000 32k 22 (0x016) 0x00000001 T 80x25 8x14 0xb8000 32k 32k = 0x00000000 32k 23 (0x017) 0x00000001 T 40x25 8x16 0xb8000 32k 32k = 0x00000000 32k 24 (0x018) 0x00000001 T 80x25 8x16 0xb8000 32k 32k = 0x00000000 32k 26 (0x01a) 0x00000003 G 640x480x4 4 8x16 0xa0000 64k 64k = 0x00000000 256k 27 (0x01b) 0x00000003 G 640x480x4 4 8x16 0xa0000 64k 64k = 0x00000000 256k 28 (0x01c) 0x00000003 G 320x200x8 P 8x8 0xa0000 64k 64k = 0x00000000 64k 30 (0x01e) 0x00000001 T 80x50 8x8 0xb8000 32k 32k = 0x00000000 32k 32 (0x020) 0x00000001 T 80x30 8x16 0xb8000 32k 32k = 0x00000000 32k 34 (0x022) 0x00000001 T 80x60 8x8 0xb8000 32k 32k = 0x00000000 32k 37 (0x025) 0x00000003 G 320x240x8 V 8x8 0xa0000 64k 64k = 0x00000000 256k 112 (0x070) 0x00000000 T 80x43 8x8 0xb8000 32k 32k = 0x00000000 32k 113 (0x071) 0x00000001 T 80x43 8x8 0xb8000 32k 32k = 0x00000000 32k freebsd-test16# vidcontrol -i adpater vidcontrol: getting active vty: Inappropriate ioctl for device freebsd-test16# cat adapter=20 fb0: vga0, type:VGA (5), flags:0x7007f initial mode:24, current mode:27, BIOS mode:3 frame buffer window:0xa0000, buffer size:0x40000 window size:0x10000, origin:0x0 display start address (0, 0), scan line width:80 reserved:0x0
I can also confirm that running: vidcontrol MODE_27 vidcontrol -f iso ...on the console fixes the issue, at least on my D2500CC. Thanks.
I also updated the machine in question to 9.1-PRERELEASE (synced shortly after 9.1-RC1 became available), and the default console appears to work now without any need to change modes via vidcontrol. Many thanks to the devs for all their hard work.
For bugs matching the following criteria: Status: In Progress Changed: (is less than) 2014-06-01 Reset to default assignee and clear in-progress tags. Mail being skipped