[haiku-bugs] Re: [Haiku] #14999: Ryzen 5 2400G on B450 chipset with M.2 NVMe SSD (tracking ticket)
- From: "Haiku" <trac@xxxxxxxxxxxx>
- To: undisclosed-recipients: ;
- Date: Tue, 09 Apr 2019 21:26:09 -0000
#14999: Ryzen 5 2400G on B450 chipset with M.2 NVMe SSD (tracking ticket)
-----------------------------------------+----------------------------
Reporter: taos | Owner: nobody
Type: bug | Status: closed
Priority: normal | Milestone: Unscheduled
Component: - General | Version: R1/Development
Resolution: duplicate | Keywords:
Blocked By: 9910, 14787, 15000, 15001 | Blocking:
Has a Patch: 0 | Platform: All
-----------------------------------------+----------------------------
Comment (by waddlesplash):
Screen preferences shows that "framebuffer" is used with a resolution of
1600 x 1200 instead of the native 3840 x 2160 (it's not possible to change
any settings)
EFI GOP can't change the screen resolution after boot. If you write a
screenmode to the "VESA settings file", the EFI loader will attempt to
change to that mode before initializing graphics output. (This is enough
for me to get 1366x768 native panel res on my laptop.)
listimage | grep drivers for some reasons shows both /dev/graphics/vesa
and /dev/graphics/radeon_hd
This may mean there is a semi-supported Radeon HD device but
initialization fails. The "framebuffer" driver is provided by the VESA
driver also, so that's what's actually being used here.
the Intel I211-AT is recognized as /dev/net/ipro1000 and is stuck at
"configuring" - at least for me, it doesn't work - although it should
according to #14516 (anything you want me to check?)
Syslog shows that it's sending DHCP requests and receiving nothing. Why
that is, is unclear. It could be that there is a driver bug, or yet
another net_server bug, or all of the above. Likely that means the driver
has at least detected a cable plugged in though.
bluetooth controller is not found by Bluetooth preferences
Bluetooth is usually dependent on the WiFi driver initializing the
controller with firmware; so naturally that won't work. But currently the
Bluetooth driver tries to access it before this occurs even on systems
which handle this properly; so there's work to be done here in general.
The bluetooth system wasn't included on the beta due to how experimental
it is.
--
Ticket URL: <
https://dev.haiku-os.org/ticket/14999#comment:6>
Haiku <
https://dev.haiku-os.org>
The Haiku operating system.
Other related posts:
