Haiku 64bit on Ryzen

Feedback Hardware
9

Just to reiterate Ryzen 3/5/7 is not enough to tell you the core count. You need to know the series also.

Currently the CPU suffixes are U, G , X and no suffix. U (low power mobile APU) and G (desktop APU) so far are all Raven Ridge a single 2-4core CCX + GPU. There is talk of an H series high power APU but it hasn’t showed up yet.

X and no suffix are the desktop parts Summit and Pinnacle Ridge the X denotes extra boost via XFR. Which are 2 CPU CCXs (Core complexes) on a single die.

There is also Threadripper as well which is 2 desktop dies up to 4 dies on Threadripper 2 wired together on a single package with 4 memory channels and 64 pcie lanes. EPYC is 4 dies with up to 32 cores the main difference from threadripper is 8 channel memory and 128 pcie lanes. EPYC has a very similar pinout but doesn’t seem to work in threadripper motherboards, the motherboards for it are also generally very high end server boards as they have to support all that massive amount of IO.

Edit:
Ryzen E series have recently been announced that have lower clocks and much lower power use these are desktop parts. Also I forgot to mention there is also Ryzen GE sereis which is roughly the same as the G series. As well as V series which has partnumbers like V1000 etc… these are embedded versions for the raven ridge core.

1 Like
10

Screenshot_2018-09-10_16-27-06
Screenshot_2018-09-10_16-29-25

Maybe need some updating :wink: This is not that important whatsoever. I really don’t mind so much if the processor is reported as being a Ryzen 5, or 7 or 3, as long as I can use it :smile:
This sys info is what xubuntu 16.04 LTS reports. So most likely I understand they updated the code to “identify” the processor name and model.
Don’t worry about this. Is just some funny thing.

Regards,
RR

11

Good day everyone,

More news on Haiku on Ryzen. This morning I did some more tests and the results are the following:

IMG_20180912_134422523

Previous picture shows Haiku boot log after a failed boot showing a Ryzen 5 2400G with Vega graphics. That is a good thing.

IMG_20180912_135554139

Previous picture shows “About Haiku” showing a Ryzen 7, and also the Haiku Installer ready to install the OS, after booting with all Safe Options ON.
Actually, I downloaded the last nightly (anyboot no-efi) but if you check the “About Haiku” it shows this is the Beta. I presume that this is because I have been using the same USB key for trying to install different versions of Haiku, and Etcher does, well… witchcraft?

Today I could install again the R1 Beta1 (pre-Release for testing only - apologies @extrowerk) , and I tried to grab the boot log onto an USB Key, FAT32 formatted, in order to provide some more insight to the developers, but no success.

Moreover, after installing Haiku, and the installer writing the Boot Record nothing happened. I could not boot the box. And booting out of the USB key only recognized the Haiku on the USB, not the hard drives, and back to the KDL again and again no matter which safe options.

So, I presume I need to format-wipe the USB key, write something, delete it, so the data location is written on so no remains are kept.

Will keep you posted.

Regards,
RR

12

There is no Beta, yet, just tesimages built with beta profile.

13

You can boot on Ryzen with all safe mode options enabled? Hmm … @kallisti5 may want to know that.

14

Good day,

I can boot Haiku Beta Image pre release released by @kallisti5, and I can install Haiku and boot from the hard drive. I did it once, and I broke it.

Actually, I am trying that once every week when I have some spare time at work. I tried with the rolling release (different ‘hrevs’) without success, only succeeded with the pre-release. And not just with all safe mode options enabled, I brought it down to 2: no memory above 4 GB and safe video mode. I used GPT partitioning, did not use the Intel partitioning table.

Problem is, that since that day, I haven’t been able to replicate the same behaviour until this Wednesday morning, when I took the images shown in the previous post. So I presume that after I broke the first successful install, I did more testing which rendered everything unusable (mbr, partition tables, etc. ), so as Vizzini said “when something goes wrong, go back to the beginning” (Iñigo Montoya - The Princess Bride), I reset the box config and leave it as it was before the success, that is Ubuntu installed, up and running with BIOS set to legacy (no UEFI), the wireless keyboard plugged to the box (Haiku does not like this KVM switch model just yet - the one at home works without issues, though is just a KM switch), and Video set to Auto, though I found it does not affect setting fixed VRAM to the safe mode option of “don’t use memory above 4 GB”.

Tomorrow I plan to get a couple of small “clean” usb keys, one for the beta pre release, and another for the boot log, the later just in case it can be recognized by the boot manager so I can save the boot log (no success on this yet).

As I am no developer, I don’t know what to search for in the boot log in order to provide that info to @kallisti5, that’s the reason to try to get the boot log, and, in case I am able to succeed in the next try, I will get the Syslog too. Knowing what to search for would help to, at least, take a picture of the boot log page.

When I got Haiku to boot this Wednesday morning I saw the Syslog file, in the USB key system, unreadable, but I presume that file has nothing to do with the “real” Syslog. But as I opened the file nothing there, empty, clean, nada. So no point in doing anything with it.

The funny behaviour is that I can get Haiku beta testing pre release to boot and install. Once. If I try again, it fails, jumping to KDL everytime. With the rolling, always KDL no matter what.

I’ll keep testing and reporting.

Regards,
RR

15

Good day,

screenshot3

Here have Haiku preBeta running (BIOS-legacy) on Ryzen 5 2400G, with safe mode (no memory above 4GB, and safe video driver) on…

Haiku sees the 7116 MiB but shows 4596 inaccessible because safe mode settings, though without the safe mode memory setting unset boot jumps to KDL.

Working (with issues).
(Edit 20180919)
Unplugging some USB devices locks the system, either jumping to KDL (i.e.: wacom tablet, USB keys sometimes) or just a lock.
KVM now works, after I plug it into the USB 2.0 port of the Mobo, so no need to plug the Transceiver directly to the box, (UPDATED 20180922: but switching to the other pc makes Haiku lock needing hard reset|<nope|) What happens is that the USB gets a lock, and even plugging the keyboard directly to the box does not do anything, can’t use keyboard nor mouse; but, and this is the important thing, pressing the power button on the box shuts down Haiku normally, which, I presume, means the issue is just related to USB.
Regarding this, if I boot Haiku with the KVM set to the work PC, and wait until Haiku is on the desktop, then switch the KVM to Haiku, it works. It’s when I change back to the work PC when Haiku goes nuts with the USB the moment I switch back to Haiku.

In order to avoid jumping into Boot manager to set safe mode options every time I boot, I modified /boot/home/config/settings/kernel/driver/kernel file uncommenting the safe mode options (4GB limit, and VESA). This I did as there are no haiku core updates in the beta branch. When some system updates come will boot to boot manager to test again:

ScreenshotKernel

The fact that can’t switch (yet) from the work pc to Haiku back and forth makes testing harder, as need to (re)boot everytime.

I have already opened tickets with the log files in TRAC.

Other than that, yesterday I started to set the porting environment (with goals for Godot Engine, Musescore and Octave/w/Gui) as Haiku seems quite stable. VESA driver is not a big deal, though. The 4GB limit might be, but not for now.

NOTE: If you read this post, check the first one of this topic to find out which hardware Haiku 64b is installed on

Regards,
RR

2 Likes
16

hrev52357 may fix MBR booting on Ryzen without the 4GB memory limit; but I don’t have a Ryzen system so I can’t test.

17

I’ll test that out as soon as I can download it :slight_smile:

No dice on my 1700x with 16GB installed. Still had to disable 4GB or it wouldn’t boot I deleted the UEFI partition off my USB drive and rewrite the bootsector from the installer.

I was able to boot by enabling the 4GB limit, disabling the radeon_hd accelerant (crashes during boot with Vega FE), and enabling failsafe video output (don’t think I had to do this before but it kept saying it couldn’t initialize the video output over and over… basically hung) it was either that or setting the video mode to 1366x768 32bit… not sure.

Will test on Ryzen 2500u shortly

Also planning on testing on some old Transmeta hardware for kicks.

18

Good day,

I won’t be able to test on Ryzen until Tuesday 25th. As @cb88 reported can boot from USB key, with safe mode options, I presume it should work.

I will change the repo, from beta branch to rolling/master branch, do the pkgman sync and then update the whole thing. If reboots fine without touching the safe mode options in boot/…/kernel, we are good to go on the rolling. The worst thing that can happen is that box boots to KDL no matter what, then, back to the beginning with hrev52295, and a week delay.

(Edit:: 20180925)
Today I changed branch from beta to rolling/master on the Ryzen box in the repos, without touching the boot config, that is, keeping 4GB limit and the Vesa failsafe options set to TRUE.

Without the 4GB limit Haiku does not boot. It does not even light up the module loading indicator AKA the atom.

Ryzen box updated without issues, and rebooted without issues too. That means, Standard Nightlies work on Ryzen, with MBR boot and GPT partition tables.

Maybe this is due to what has been done in ticket #13370 in Track.

Other than that, still have the issue with plug/unplug keyboard/mouse. When plugging, it works (KVM set to Haiku), after unplug (KVM set to work PC) and re-plug (KVM set to Haiku again), keyboard/mouse don’t work, but system is not locked. It’s like the USB stack went out on holidays. So maybe we need a different ticket for the USB thing, different than the #13370.

Anyway, there has been a lot of improvement since the first day I tried to install Haiku on this box. So, then again, big thanks to the development team!.

Will keep testing and reporting.
Regards,
RR

19

hI can’t boot on my ryzen 5 1600 with ASUS TUF B350M-PLUS Gaming motherboard. No atom icon in red :frowning: Sadly this is with hrev52357 x86 and x86_64. With limit for 4 GB option doesn’t boot either using limit for 4 GB and using VESA driver. :frowning:

MY PC

  • amd ryzen 5 1600
  • asus tuf b35m-plus gaming
  • 32 gb RAM (2400 MHz)
  • Aorus (Gigabyte) AMD Radeon RX 580
  • NVMe for windows one ssd for linux and one (if i can boot for haiku)
20

@zantak Did you enable on screen debugging and disable paging? Where did it stop?

21

nope :frowning:
this is in the menu disable io-apic?
in the atom phase

22

Good day,

@zantak, have you tried with the pre-beta? hrev52295, the one pointed out in the first post baked by @kallisti5?

I was successful with that one installing on my ryzen. I presume you don’t need the safe video because at home I have a RX560 and Haiku deals with it quite ok.

I started with the pre-beta, and it finally worked with those two options Ram limit and Vesa. Today I updated the branch from beta to rolling/master and now hrev52358 works fine with the Ram limit and Vesa too.

No matter what, first run I did was boot Haiku from usb with all safe mode options ON. That way I was able to install Haiku, then rule out the good ones, and ended up with those 2 (Ram+Vesa). As you have a CPU+GPU instead of an APU, situation might be different. Can try that and see if it works (all safe mode options ON).

Regards,
RR

23

Good day,

@waddlesplash, nope. The memory limit is still needed in the hrev52358, at least in here.

Thanks,
RR

1 Like
24

At least nothing works for me, activating all of safe mode options doesn’t boot haiku. What happens ?? :frowning:

25

Good day,

@zantak, I did not pay attention last time. You have already a multiboot box. If you have EFI, most likely, enabled boot for Windows, and also Linux running on EFI mode, then you should try the UEFI bootable image.
What I have used is the plain Anyboot ISO, which boots in MBR mode as this box is 100% Haiku only, so no need to worry about UEFI in my case.
Probably it will work with the UEFI image and you can boot your box though it needs some fiddling as pointed out in the UEFI topic. I have tried an old UEFI iso which never worked for me, maybe because the process I followed wasn’t the right one.

Whatsoever, @kallisti5 reported that the new R1Beta1 release may or may not work on some devices, Ryzen included, so it is a matter of patience and trial/error. You should be aware, at least in my case, to have the keyboard/mouse plugged into a USB 2.0 port, even if you set your BIOS for usb compatibility… At least in my case is needed.

After I got Haiku installed (hrev52295) I haven’t tried to boot with other revs, be them nightly nor beta. Just changed the branch from beta to rolling/master, and the box keeps working fine with the VESA driver, and the memory limit.

In your case, I would try the UEFI ISO following the recommendations stated in

or newer images if available. And remember to turn off Secure Boot, and all the BIOS stuff.

Regards,
RR

26

Just an FYI my AM4 board has onboard PS/2 (apparently its a “gaming” feature for people concerned with USB latency) so I can work in the KDL without USB issues.

Fatal1ty X370 Gaming-ITX/ac

27

Good day,

I will keep this box running on rolling, right now on hrev52379. At this stage, the memory limit is still needed. I just tried right now and there is no way to get passed that, at least in my case.

So as of today, and after a couple of weeks, Haiku is quite stable on this box, taking into account the following:
1- Need the memory limit set to 4GB in order to boot (I’ve already added the Syslog’s to a ticket)
2- Need the VESA graphic driver
3- Unplugging the keyboard/mouse and plugging it again renders the keyboard/mouse useless (I’ve already filed a ticket)
4- There is no sound through HDMI (also no sound through DisplayPort on my home Box, but that is an old A8) maybe related to using the VESA driver?
5- BeCJK does not let me type chinese. Sometimes it looks it works, then it does not. 现在可以,以后不知道. Now it did.
6- Extra keys on the keyboard are useless.

Other than that, everything seems fine. I will keep checking and posting any improvements on Ryzen 5 2400G, and remember this box is running on Anyboot non-UEFI, MBR boot with GPT partition table.

Regards,
RR

28

at least this is impossible on ASUS Mainboards