HELP WANTED: R1/beta5 boot & hardware testing!

Thanks, will try and report back

rEFind offers legacy BIOS boot only on Macs that actually support it. Apple removed the CSM-BIOS support starting from 2015 MacBooks. I’m not sure about iMac Mid-2015. Currently it’s not listed to support Windows 7 (which was the last Windows version that required legacy mode support), but it used to be listed before, so I’d say it’s worth to give it a try, maybe also with RefindPlus which provides some additional Mac-specific features and fixes.

Yeahh , but that’s not the reasonable thing. Instead it would be useful at least to adapt to the new APUs , in my rx580 with CSM enabled(if disabled does not work) works correctly as it should be , except for some games .

No Success on 2015 iMac, 2010 and 2017 are working

Tried Microsoft surface 3 (no pro). Boots off external USB stick with frame buffer in native resolution, no sound, no network and no internal storage access. So the same behaviour as when I last tested, but, now the internal SD card is seen (used for data storage), partitions are recognized including names, but otherwise hangs/fails/ does nothing.

This is improvement all in all, but would be nice if the internal card would be usable of course.

Oh: 64 bit, UEFI, and trackpad and keyboard work nicely. Did not test the touchscreen yet though.

It seems that some providers don’t allow accessing wasabi servers. I know that there are workarounds but if next candidate could have a mirror elsewhere, it would probably allow to more people to test it.

Not until we have some signature system in place, so the mirrors can be trusted to contain packages that are indeed built by the Haiku and Haikuports infrastructure.

I think this was about the ISO download,not the packages.
For the actual releases,we already have mirrors and this isn’t a issue since people can compare the hashes,but for previews this is probably too much.
I personally don’t have issues downloading from Wasabi and I never directly heard from anyone who has… :thinking:

Speaking of packages,there was at least one mirror in the past (which is still accessible): Index of /haiku/haikuports/
Unfortunately it stopped updating in April,so I had to go back to official servers.
Speed was about the same,but I could take some load (and traffic costs) off Haikus servers so I happily used it.

What I’d really love to see for package delivery in the future is a system like Parabolas Pacman2Pacman: Pacman2Pacman - ParabolaWiki
Haiku would be a perfect fit for it,since it doesn’t extract and then delete package files,but instead they’re stored forever so they could be shared with other users.
Torrents have verification and load balancing and all built-in,so we wouldn’t have to worry about signatures,maintaining a list of mirrors,finding enough volunteers for mirroring,…
Seeding should be opt-in,of course (maybe asked on first boot or on first package install),I think we would still find enough people who would accept to share their unused bandwidth.

Yes, it was only about the next release candidate iso.

The problem I had was DNS lookup - I normally rely on my gateway router for DNS, but had to add another DNS service to get to the wasabi address. I didn’t think this was about a provider not allowing access, just some referral breakage.

Yes, it is a DNS problem. Usually people are using their providers DNS and don’t necessary know how to change that or can’t for different reasons.

Won’t boot on any computer I have, stops on the bootdisk icon. I tried several downloads and checked the hash before burning the dvds. :frowning:

Tested on two machines (USB stick installation).

  1. Fujitsu LifeBook A Series: Intel i5-2450M (2.5 GHz, 2x2 threads), Intel HD Graphics 3000.
    Everything seems to work fine, as it used to work in beta4 nightlys. Custom OpenGL applications and libraries work as expected. Wifi won’t work at boot because Network settings aren’t saved. This is a well-known old bug, I used the workaround found here which partially works (Network settings window pops up, I still have to select WPA/WPA2 security - but at least I don’t have to type the SSID and password every time I boot the system).
    I don’t really have anything else to report about this installation, since I have yet to find anything going wrong.
  2. Dell Precision T3500: Intel Xeon W3550 (3.07 GHz, 4x2 threads), Nvidia Quadro 2000 (GF106GL).
    This machine is more powerful than the laptop above but Haiku doesn’t work properly here. It boots, and applications I tried just as above work as well - when I manage to run them. And I say “when I manage to run them” because there are frequent “hiccups”: the system stalls pretty much everywhere (when moving the mouse, typing on Terminal, etc). It eventually recovers, only to stall again in a few seconds or, if I am lucky, a minute later. Those delays seem unpredictable, not related to a specific user action. In the end the system hangs when I try to shut it down (the shutdown window appears but nothing happens). I experienced similar behavior in nightlys. I am not sure what should I try to figure out what’s going on.

File a bug report in Trac, and attach a syslog. :wink:

1 Like

12 posts were split to a new topic: Haiku image

9 posts were merged into an existing topic: Haiku names

Is there a newer test candidate/release candidate than the one at the top of this thread? I would like to test it on my Thinkpad T410.

No, You can use these test images and update afterwards however.

1 Like

Report on my Thinkpad T410, keyboard works, display works, brightness keys work. Unfortunately WiFi still doesn’t work (I did run install-wifi-firmwares.sh, but that did not help). I am surprised about WiFi, this would be a perfect laptop for Haiku otherwise.

Which Wifi chip does it have?
install-wifi-firmwares.sh is only needed/helpful for very old chips where the license of the firmware forbids redistribution in the Haiku image.
All newer chips,if supported at all,are supposed to work out of the box.
Maybe your chip is unsupported,or maybe it’s just some bug that can be fixed.
Haiku takes network drivers from FreeBSD and OpenBSD,so we could look if one of them supports your Wifi chip if you say which it is.