Haiku x86_64 is a read-only device?

[Luposian]

I recently downloaded the latest Haiku x86_64 (about a week ago) and discovered that, not only are other drivers causing the black screen issue (you have to set "fail safe video" in the Boot Options menu), but it is IMPOSSIBLE to remove them.

Why?

Because, when you try to remove them, Haiku tells you that you can't change a read only device. Yet... I've installed Haiku to my hard drive partition. It's not a CD image. Its a raw image installed to my second hard drive partition! So, why does it think it's on a read-only device?

VESA works perfectly for me. I'd set it to that, permanently, except that I can't remove the other drivers, to do so!

[anevilyak]

What you're seeing are files virtually extracted out of the system package. Those are mounted read-only by definition.

[anevilyak]

To remove a driver nowadays: ​https://www.haiku-os.org/guides/daily-tasks/blacklist-packages

[Luposian]

Replying to anevilyak:

To remove a driver nowadays: ​https://www.haiku-os.org/guides/daily-tasks/blacklist-packages

I followed the page exactly, making sure I had the right case (upper and lower) and everything, and it's not working. I even tried using my network driver (rtl81xx) as an entry and it's still being run/executed/used.

I tried "haiku" (as the example shows) and I tried the super-long haiku package name (without the .hpkg extension). Neither works. The video driver I tried it with still showed up in the directory and the network driver still loads.

Am I doing/typing something wrong, or is this "blacklist" feature, perhaps, not operational in Haiku x86_64?

[jackburton]

Did you correctly blacklist the driver entry ? In your case, that would be

Package haiku {
	EntryBlacklist {
		add-ons/kernel/drivers/bin/rtl81xx
	}

If the package is named haiku, of course. Also, did you try blacklisting in the boot menu ?

[Luposian]

In the latest releases (like the one I got from Haikufiles), what is the package, that contains the video drivers? I can't tell. I assumed, that if "haiku" is the example, then something with the name "haiku" in it, would be the real one, so I tried the really long haiku-named package. But that apparently wasn't it, either.

Yes, I tried black listing in the boot menu and that worked. But you can't make the settings there, stick, can you?

[luroh]

Not sure what's up, a system/settings/packages file with the following content works fine here with x86_64, hrev47196:

Package haiku {
	EntryBlacklist {
		add-ons/kernel/drivers/bin/ipro1000
	}

Perhaps you should attach your system/settings/packages file to this ticket, along with stating what actual revision you are running.

[Luposian]

My sincere apologies... this has been a wasted reopening of this ticket... I apparently had a space between Entry and Blacklist, so it looked like "Entry Blacklist", not EntryBlacklist", as it should. When I removed that space, everything worked perfectly.

How I could have done that, I have no clue. I was certain I was following everything so carefully. Oh, well... ticket closed.

Luposian... meet cast iron pan. Cast iron pan... meet head. Meet forcefully, several times. Lesson learned... I hope. :-D

[Luposian]

Luroh, if you see this... maybe you can help me with another issue I'm having with Haiku x86_64 building Haiku x86_64? My screen blacks out during the Jam! There's also another issue, involving atomic.o. Have you JAM'd Haiku x86_64 from within Haiku x86_64, recently? Those tickets are still open...