deavmi has quit [Read error: Connection reset by peer]
BrunoSpr has joined #haiku
deavmi has joined #haiku
deavmi_ has quit [Read error: Connection reset by peer]
BrunoSpr has quit [Quit: Vision[]: Ich wurde ausgebleicht!]
haiku_example has joined #haiku
<haiku_example>
hewo
<haiku_example>
i have a doubt
<haiku_example>
does haiku need pae
<haiku_example>
in order
<haiku_example>
to work
<haiku_example>
PAE (CPU)
julienxx has joined #haiku
andreasdr has joined #haiku
<andreasdr>
Hi, if anyone is interested regarding RADEONDRM Haiku port the AMD RadeonHD 6970 I bought does not work with RADEONDRM OpenBSD and does not work with RADEONDRM NetBSD. Damn. I ordered now a 6870. In a OpenBSD forum there was a statement that it should work. Lets see. :)
Maturion has quit [Ping timeout: 480 seconds]
<haiku_example>
uhm
<haiku_example>
so
<haiku_example>
does haiku work on VERY old CPUs
<haiku_example>
without PAE
andreasdr has quit [Remote host closed the connection]
Coldfirex has quit [Remote host closed the connection]
<humdinger>
Heh. there's a string in Terminal "ANSI bright black color".
<humdinger>
what's that? :)
<humdinger>
dark grey?
<_Dario_>
yes, I had the same question, when translating it into spanish
<_Dario_>
I always believed that there weren't "bright" version of white and black
<humdinger>
:)
<humdinger>
Also, does the setting actually work?
<humdinger>
it's in the "Color" pop up menu. There "Text under cursor" works, but setting any ANSI color, I don't see anything change...
<nephele[m]>
ANSI color settings work fine for me
<nephele[m]>
if you have colored output from a compiler or something you can live adjust the slider to see it doing something
<nephele[m]>
I think the "bright" variants are used for the inversion when you select something like
<nephele[m]>
black bg green fg => bright green bg; bright black fg
<nephele[m]>
or something along those lines
<humdinger>
gotta run. back later...
* humdinger
is idle: BRB
<nephele[m]>
eh, my testing doesn't seem to match that though :g
dburkart has joined #haiku
_Dario_ has quit [Quit: Vision[]: i've been blurred!]
Coldfirex has joined #haiku
cocobean has joined #haiku
roiredX has joined #haiku
<roiredX>
good day
ClaudioM has joined #haiku
countryboy has left #haiku [#haiku]
<Coldfirex>
Howdy
<Coldfirex>
I am trying to use EFI on a laptop and have booted off a nightly. DriveSetup sees my HD but does not give me the option to create a partition as required. Ideas?
<Coldfirex>
NM, I had to go to Disk-> Initialize GUID Partition map and now its an option
B2IA has quit [Quit: Vision[0.10.3]: i've been blurred!]
<roiredX>
Coldfirex, do you have uefi activated on the bios?
B2IA has joined #haiku
<Coldfirex>
Yes. I got past that but now I need to copy bootx64.efi to the efi partition I created, but I have no idea where it is. It isnt on the anyboot iso it appears
tuaris has joined #haiku
<Coldfirex>
supposedly I need to mount the efi partition of the anyboot, and then copy the file from there
<B2IA>
(AGMS) Coldfirex, I think the EFI and other boot files are also made available in system/data somewhere.
<Coldfirex>
there is a haiku_loader.efi but the instructions dont mention that file
<B2IA>
(AGMS) That's the file, might need to rename it, and copy it to the EFI partition in the appropriate directory.
<zdykstra>
most machines look for BOOTX64.EFI by default, if memory serves
B2IA has quit [Remote host closed the connection]
<zdykstra>
otherwise you'll have to add a specific EFI boot entry for that file
B2IA has joined #haiku
<B2IA>
(AGMS) Yes, so that's what you rename it to.
<humdinger>
wrt to the ANSI colors in Terminal. I'm not sure how they should work. All the original entries in that menu control specific objects to color, like "text under cursor", "Background" etc.
<humdinger>
you choose one and then set the color in with the mixer below.
<humdinger>
what does chooseing "ANSI greeen" do?
<Coldfirex>
Thanks. I am using that, but it leaves out a few details (which I intend to add once I get it working)
<humdinger>
Color everything green? makes no sense...
roiredX has quit [Quit: Vision[]: i've been blurred!]
deavmi has quit [Ping timeout: 480 seconds]
tqh has joined #haiku
xxoREZoxx has joined #haiku
xxoREZoxx has quit []
B2IA has quit [Quit: Vision[0.10.3]: i've been blurred!]
<Coldfirex>
got it going
<Coldfirex>
looks like Im stuck at 1024x768 with EFI and VESA. That sounds familiar. Is there a workaround?
<Diver>
Coldfirex: make sure ~/config/settings/kernel/drivers/vesa doesn't set the mode in EFI mode
<Diver>
also try to enable CSM in UEFI
B2IA has joined #haiku
<Coldfirex>
Diver: I only have a kernel text file there (clean install btw)
<Diver>
i mean if you booted in vesa mode and started Screen it could have written vesa settings file which will be used in efi mode too
<Coldfirex>
ah. I did run Screen, but nothing written
<Coldfirex>
I will check CSM next
<Coldfirex>
wait doesnt that just try to switch me back to legacy/bios instead of efi mode?
<nephele[m]>
yes, that boot is in 32bit color space
<kallisti5[m]>
(8 * 4)
<nephele[m]>
I should add that it looks perfectly fine if the screen isn't updating much, but if a lot of redraws happen, like moving qt apps or something it becomes quite bad
<kallisti5[m]>
you're welcome, let me know if you have any more questions
<kallisti5[m]>
:-D the logs look fine. it's doing everything it should at face value... obviously it's broken though if you're seeing scrambled video
<kallisti5[m]>
your card is one of these? [Radeon HD 6450/7450/8450 / R5 230 OEM]
<nephele[m]>
HD6450 1G DDR3 PCI-E HDMI/DVI-D/VGA
<nephele[m]>
thats what the label sais on the card
<tqh>
do you run any other OS as well and is it better there?
<nephele[m]>
Ubuntu runs fine on the same machine, but i think it is running in a higher color space than 32bit
<kallisti5[m]>
Hm. I have a Radeon HD 5450 plugged into my riscv64 board. It's working fine
<nephele[m]>
6450, not 5450
<kallisti5[m]>
i know, but really similar generation
<nephele[m]>
I don't know much about how similar cards are, just making sure you haven't misread :)
<kallisti5[m]>
nephele: you want to try a patch to fix it?
<nephele[m]>
Oh, certainly I would like to aquire the skills for it, but I don't know where to start investigating really
<nephele[m]>
or do you mean you have a patch for me to build and try? I could do that too :)
<kallisti5[m]>
try that one minus the riscv64 guards
ClaudioM has quit [Quit: leaving]
<nephele[m]>
Okay
<kallisti5[m]>
err. just change #ifdef __riscv to #if 1
<kallisti5[m]>
I saw a similar scrambled result on my Unmatched with this card + hdmi
<kallisti5[m]>
as soon as I appled X512's fix, it resolves it
<kallisti5[m]>
maybe we have some app_server bug which is triggered at that resolution
<kallisti5[m]>
it's not a guarantee.. but an "interesting experiment"
<Coldfirex>
no CSM option in the bios which is a version from this year. :(
<nephele[m]>
Okay
<nephele[m]>
I should really find a shorthand for jam -q -j12 @nightly-anyboot haiku.hpkg haiku_devel.hpkg
<nephele[m]>
Maybe a target that automatically installs haiku.hpkg and haiku_devel.hpkg on a sucessfull build would be neat, that is 95% of builds I do :D
JakeSays has quit [Ping timeout: 480 seconds]
<nephele[m]>
kallisti5: still broken with that, with #if 1
<nephele[m]>
On a side note, the card also initializes the display with 100% white screen... which really hurts my eyes, is that driver specific? I suppose I'll file a bug there aswell (does that before the desktop eventually comes up)
<Coldfirex>
I disable Intel SGX and TPM in the bios and now I am stuck at 1366x768 which is an improvement :)
rodolphoeck has quit [Quit: gone]
jesse_blue has quit [Remote host closed the connection]
boistordu_ex has quit [Remote host closed the connection]
illwieckz has quit [Ping timeout: 480 seconds]
ilya has quit []
euandreh has quit [Remote host closed the connection]
euandreh has joined #haiku
Babaj has quit [Ping timeout: 480 seconds]
pengphei has joined #haiku
boistordu_ex has joined #haiku
illwieckz has joined #haiku
<Coldfirex>
Does anyone know the gist of whats wrong with our HDA sound driver?
AlienSoldier has joined #haiku
pengphei has quit [Quit: pengphei]
pengphei has joined #haiku
pengphei has quit [Remote host closed the connection]
<AlienSoldier>
one thing that would be nice to add to the screen pref is the choice between VESA and native driver. It would prevent the not obvious need to blacklist the driver and allow the OS to remember it at next boot.
<kallisti5[m]>
oh, you can use vesa on every boot pretty easily
<kallisti5[m]>
option 1: Disable the radeon_hd driver in the haiku package on every boot via the package config file
<kallisti5[m]>
option 2: Set fallback_video to true in the kernel config
<AlienSoldier>
but it is not as discoverable for a new user
<kallisti5[m]>
In fairness, that's not an issue unique to us. Such a setting isn't discoverable on Linux, Windows, OS X
euandreh has quit [Ping timeout: 480 seconds]
<kallisti5[m]>
Linux is adjusting the kernel arguments to modeset=0. Windows is.. no idea, uninstalling the driver?
<kallisti5[m]>
Theoretically, a setting like that couldn't technically be in the screen preflet as things are designed today
<AlienSoldier>
what i would like is o be able to change that driver live.
<AlienSoldier>
*to
<kallisti5[m]>
technically we also have a video driver fallback key sequence
<AlienSoldier>
especially if we are to have a d3 driver in the future, eing able to easilly revert might be nice as it will probably be a bumpy road.
<kallisti5[m]>
been years since I tried it though
<AlienSoldier>
*3d
<Coldfirex>
framebuffer in Screen means I am not using vesa correct?
<AlienSoldier>
right now i have a regression on my interl driver. If i put it full time VESA i won't know when the regression is fixed. I currently need a reboot to test that.
<kallisti5[m]>
that's the vesa driver being a framebuffer
<kallisti5[m]>
aka.. you booted UEFI and got a framebuffer instead of bios vesa
<kallisti5[m]>
it's from the vesa driver, but the screen resolution is set by the bootloader
<kallisti5[m]>
you'll likely only have one video mode available (the native one)
<Coldfirex>
which seems slower\les smooth than vesa to me. Is that also accurate?
<AlienSoldier>
there was a framebuffer app for R5, i wonder if that is compatible with how haiku work right now.
<Coldfirex>
I believe so
<kallisti5[m]>
Coldfirex: shouldn't be slower
<AlienSoldier>
i guess that app was made for demo coder in mind
<Coldfirex>
I jut noticed tearing or something when dragging windows around
<AlienSoldier>
tearing could also happen with native driver in haiku, sadly
<AlienSoldier>
tearing make the OS look bad.
<kallisti5[m]>
patches welcome :-)
<AlienSoldier>
at least it's half less bad now that i have almost no sound skiping
dcatt has joined #haiku
<AlienSoldier>
still have some sound skipping that seem to happen from heavy virtual memory use.
<dcatt>
I get that issue when plugging in a USB flashdrive
<dcatt>
is it possible to prioritize certain pricess like media?
<dcatt>
*processes*
<AlienSoldier>
i guess that not everything is fully DMA
<AlienSoldier>
you can when coding the app or with process controller. Not by app signature i think.
<dcatt>
oh ok
<AlienSoldier>
you set it with a weight number that is asociated to a certain term (low, high real time etc...)
<dcatt>
I was just looking
<AlienSoldier>
a bit like on the amiga
<dcatt>
I remember that feature
<dcatt>
I guess making the operating system automagically managing that is asking too much
<dcatt>
so I have Audacious playing internet radio and made the steam realtime priority and now it's time to test what happens when plugging in an USB flashdrive
<Coldfirex>
wish I could just have sound
<dcatt>
sound is important
<dcatt>
darn, mounting a USB flashdrive killed the audio with no return
<dcatt>
I'll see if I can recover by a simple stop start
<AlienSoldier>
all auio orjust the stream?
<dcatt>
the app is still functional and the stream is playing, but no audio
<dcatt>
darn, I quit, restarted the app and clicked play and still no audio