<rennj>
The USB audio device has multichannel (5:1) support. This is disabled by default though, the multi=on parameter turns it on.
<rennj>
qemu has an internal audio mixer, for mixing audio streams from multiple devices into one output stream. The internal mixer can also do resampling and format conversion if needed. With the pulseaudio backend we don't need it as the pulseaudio daemon can handle all this for us. Also the internal mixer is limited to mono and stereo, it can't handle multichannel (5:1) sound data. So we use mixing-engine=off to turn off the internal mixer.
srnp has joined #haiku
<rennj>
ooof qemu so many options
srnp has quit []
<rennj>
wonder if virt-manager is any better than cli
<nekobot>
[haiku/haiku] 95682340fbda - lgtm yml: remove buildtools archive after unzip it.
countryboy has joined #haiku
e1z0 has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
e1z0 has joined #haiku
e1z0 has quit []
countryboy has left #haiku [#haiku]
<Anarchos>
who used vim recently on haiku ?
<jmairboeck>
Anarchos: I use it regularly (in the terminal)
<Anarchos>
jmairboeck when i do :version it says -python -python3 but i have python installed
<Anarchos>
jmairboeck btw i made a pull request to BeTeX on HaikuArchives
<jmairboeck>
it is probably not built with python support
<Anarchos>
jmairboeck the recipe says it is compiled with python support
HaikuUser2 has joined #haiku
HaikuUser2 is now known as mrentropyvcs
<Anarchos>
jmairboeck you can also clone my BeTeX clone repo if you want
countryboy has joined #haiku
<jmairboeck>
I don't really use TeX myself any more that much (since finishing university). Initially, I just wanted to have Lilypond on Haiku, but that needs MetaFont to build, and I saw that there was only an old, disabled recipe and thought if I could do better and build something current :) But If I'll need it, I will check it out.
<jmairboeck>
I used mostly Kile as my Latex editor before (KDE on Linux)
Diver has quit [Quit: Leaving.]
beaglejoe has joined #haiku
<Anarchos>
jmairboeck metafont was built by the texlive package , no ?
<jmairboeck>
yes, metafont is part of texlive
<Anarchos>
mf --version --> Metafont 2.71828182 (TeX Live 2021/Haiku)
countryboy has left #haiku [#haiku]
Diver has joined #haiku
KapiX has joined #haiku
tbcr has joined #haiku
Animortis has joined #haiku
AlwaysLivid has joined #haiku
<Animortis>
quit
<Animortis>
oop
Animortis has quit [Quit: leaving]
aakashi2001 has joined #haiku
gouchi has joined #haiku
aakashi2001 has quit [Remote host closed the connection]
aakashi2001 has joined #haiku
KapiX has quit [Quit: KapiX]
jmairboeck has quit [Quit: Konversation terminated!]
<waddlesplash>
copy and paste everything after the $ into a Terminal, on Haiku of course. it will take some time
<dfergfla[m]>
ok
<dfergfla[m]>
will do
<dfergfla[m]>
it's running now, thanks
BrunoSpr has quit [Quit: Vision[0.10.3]: i've been shreederd!]
BrunoSpr has joined #haiku
<dfergfla[m]>
I would like to ask a general question about nighties. I moved from Beta 3 to the nightly builds last week. I do know that nightlies are going to be less stable. I am currently experiencing a crash when trying to play youtube videos, like all of them. Also when loading www.yahoo.com the Web+ will crash before the page fully loads. Is this something that is just going on with web+ from the nightlies right now, or do I need to open an
<dfergfla[m]>
issue ticket? Thanks :)
<dfergfla[m]>
waddlesplash: the cloning is done. I assume I need to compile it now. So what do?
<PulkoMandy>
it's probably a known issue but it only affects x86_64, I don't have a 64bit install around, and as far as I know, no one else is currently working on fixing it
<dfergfla[m]>
OK
<BrunoSpr>
Diver.. after installing vlc via Terminal it is now available in HaikuDepot, but not before
<dfergfla[m]>
Thanks
<PulkoMandy>
seems everyone is fine with the web browser crashing on half the websites in the world, somehow :/
<nephele[m]>
dfergla: please check the issue tracker and then file a ticket if there is none
<nephele[m]>
PulkoMandy: I must be visiting the other half :g
<dfergfla[m]>
nephele: will do
<dfergfla[m]>
so... I need to compile this thing Waddlesplash had me download.... Can someone guide me though that please.
<nephele[m]>
While yes, there are known issues in nightlies, but they are known so much people don't open tickets because it's known, and then stuff never gets fixed because the devs didn't know about it :P
lelldorin has joined #haiku
<nephele[m]>
waddlesplash made you download the haiku source tree, you also need to download the haiku buildtools next to it, ill link you to the building haiku guide in a moment
<PulkoMandy>
nephele[m], I think we know very well that wasm and youtube are two easy ways to crash webpositive, we should fix these first
<dfergfla[m]>
nephele: got it. I will log a ticket
<nephele[m]>
WASM i do know about, yeah, for youtube i have little idea why it crashes there
<nephele[m]>
(as i basically never use that site :g)
lelldorin has quit []
<dfergfla[m]>
Ok, .. I have followed the link. I am not a developer and have only very, very limited knowledge. So, here is where I am at. ..
<dfergfla[m]>
If I understand this correctly, I am running a nightly so I went to the link for Compling for X86_64 as it mentions that nightlies have dev stuff included... at least that is how I understood it.
<dfergfla[m]>
I ran "mkdir generated.x86_64; cd generated.x86_64"
<dfergfla[m]>
and than was fine. The next line: ./configure --cross-tools-source ../buildtools --build-cross-tools x86_64
<dfergfla[m]>
fails with no such file or directory
<dfergfla[m]>
not sure what it is missing
<waddlesplash>
nephele[m]: no, he doesn't
<dfergfla[m]>
I am currently in terminal in the generated x86_64 directory
<waddlesplash>
dfergfla[m]: run this command instead
<waddlesplash>
$ ../configure
<waddlesplash>
no arguments
<dfergfla[m]>
ok
<dfergfla[m]>
hmm same
<dfergfla[m]>
This folder is empty, I feel I have missed something...
<nephele[m]>
waddlesplash: if you want to build an image you need the buildtools anyhow :)
<waddlesplash>
are you in generated.x86_64 in a subdirectory of `haiku`
<waddlesplash>
nephele[m]: we're only building haiku.hpkg
<nephele[m]>
which needs the buildtools
<waddlesplash>
nope
<nephele[m]>
yes it does
<waddlesplash>
you only need buildtools on x64 for bootloader
<nephele[m]>
because the bootloader gets copied into the image now...
<waddlesplash>
everything else, system tools work ok
<dfergfla[m]>
hang on I think may have found it.
<waddlesplash>
nephele[m]: nope, it's put in haiku_loader.hpkg
<nephele[m]>
it's in data/platform_loaders in haiku.hpkg no?
<waddlesplash>
that's new to me if so, it should just be in haiku_loader.hpkg
<waddlesplash>
maybe the EFI loader is in there?
<dfergfla[m]>
Ok, got farther. I wasn't in the Haiku source directory
<dfergfla[m]>
now I
<nephele[m]>
the change is somewhat recent before beta3, i'll check if its only efi :)
<dfergfla[m]>
I'm getting "Python interpreter is required" can I get that from Haiku Depot?
<waddlesplash>
nephele[m]: that's a silly idea. why do we have them there instead of haiku_loader.hpkg?
<waddlesplash>
the BIOS loader is useless by itself, at least EFI isn't
<nephele[m]>
Something something beeing able to copy the EFI loader from an installation? I don't know for sure, you'll have to ask kallisti5 :)
<waddlesplash>
...
<kallisti5[m]>
All compiled loaders are in data/platform_loaders on installed systems to make them available to users
ClaudioM has quit [Quit: leaving]
<dfergfla[m]>
waddlesplash: Ok that has completed successfully
lelldorin has joined #haiku
<waddlesplash>
kallisti5[m]: it isn't obvious what that folder is, I do like /system/boot/loaders better like you commented. and secondly, all loaders save EFI are useless to users due to how they work
<waddlesplash>
kallisti5[m]: what was wrong with putting them in haiku_loader.hpkg, exactly? that package is also more easily readable by other packages
<kallisti5[m]>
Can't because of the bios_ia32 loader
<waddlesplash>
in $near_future, I would like to switch us to Zstd compression for real, which will require a bootloader update. if the loaders are in haiku_loader.hpkg, which is uncompressed, then the loaders can update themselves!
<waddlesplash>
that sounds improbable
<kallisti5[m]>
It looks for the 'first file' inside haiku_loader.hpkg
lelldorin has quit []
<waddlesplash>
ok, so make sure that the bios loader is the first file?
<waddlesplash>
... isn't the .PackageInfo the first file? so how does this work now
<kallisti5[m]>
Not currently possible
<waddlesplash>
sounds like we should fix that instead of doing this then
<kallisti5[m]>
I tired it, there's no guarantee of ordering
<waddlesplash>
that sounds bad from a determinism perspective
<waddlesplash>
are you sure the files aren't just added in reverse order or something?
<kallisti5[m]>
That's as far as I got. The mbr has limited space for parsing a hpkg
<kallisti5[m]>
Ideally it would look based on file name in the hpkg
<kallisti5[m]>
But, no code room for that
<dfergfla[m]>
waddlesplash: ok, now have "Configured Successfully"
<waddlesplash>
kallisti5[m]: first file in the hpkg is fine, we can find a way to guarantee that I'm sure
<kallisti5[m]>
It could be reverse order or something.. who knows. I pretty much exhausted my time and interest looking at it, so implemented a half measure for R1/beta3
* waddlesplash
adds a TODO list item
<waddlesplash>
fair enough, I'll work on it at some point
<kallisti5[m]>
I think we're all in agreement on the 'right' solution though
<waddlesplash>
dfergfla[m]: open this file: build/jam/packages/Haiku -- and Find for "AddFilesToPackage data platform_loaders"
<waddlesplash>
dfergfla[m]: add a "#" at the beginning of the line containing that
<nephele[m]>
waddlesplash: see, i was right ;)
<waddlesplash>
nephele[m]: yes, I'd missed we'd added all loaders
<dfergfla[m]>
Ok now have "# AddFilesToPackage data platform_loaders: haiku_loader.$(bootTarget):"
<waddlesplash>
good
<waddlesplash>
go back to your Terminal, should still be in generated.x86_64
<dfergfla[m]>
yes
<waddlesplash>
run (replacing CORES with however many cores you have): $ jam -q -jCORES @nightly-raw haiku.hpkg
<dfergfla[m]>
starting build....
<dfergfla[m]>
lots of stuff scrolling... hope this works.
<dfergfla[m]>
Question for anyone. After an update one night a few nights ago. My wireless connection has stopped automatically connecting at login. If I click on my network, it will login. Without me having to put in a password etc. How can I get the automatic connection at boot to work again?
<nephele[m]>
dfergfla: there is an open ticket about this, it seems for some users autoconnect works but for others it doesn't, but nobody determined the cause yet
gouchi has joined #haiku
<waddlesplash>
dfergfla[m]: "it's a mystery". it randomly works or doesn't for me and has for years
<nephele[m]>
for some SSID's it always works for me, and for others it never works for me, so i suspect this is related somehow, but i am not sure :)
<kallisti5[m]>
it "worked for me", but then nightly builds had no guarantee of order of loaders in the package. It might be possible to explicitly look for the bios_ia32 loader first... but it all still feels a bit "squishy" with a big impact if it goes wrong
<nephele[m]>
Should probably make a "fake" wifi driver to test such stuff
<PulkoMandy>
I would start by adding some tracing to wpa_supplicant and have it do something else than just show the password window whenever connection fails
<dfergfla[m]>
Ok, it was just weird. It worked... then it didn't. I do a clean install it will work again.. then sometime later it will just stop.
<PulkoMandy>
(that's how it handles errors currently as far as I can tell'
<waddlesplash>
kallisti5[m]: >Makes the system unbootable on my gcc2 BIOS machine.
<waddlesplash>
kallisti5[m]: ... the efi loader won't even be in the package on 32bit
<waddlesplash>
so, something else went wrong here
<dfergfla[m]>
Boy the fans on my little laptop sound like Jet Engines... building Haiku is hard work for this old girl. :)
<nephele[m]>
I don't even know is this is an wpa_supplicant error, it does not pop up a "wrong password" prompt for instance on setups where it does not autoconnect
<Coldfirex>
Are we talking about the wpa_supplicant in haikuarchives?
<nephele[m]>
Uhh, we are talking about wpa_supplicant for wifi connections
<waddlesplash>
there's only one and it's at haiku/wpa_supplicant not HA
<dfergfla[m]>
nephele: So.. If I do a clean install and setup my wireless it all works fine. Autoconnect at login and everything. Then as soon as I run Software Updater it will break. At first it will prompt me for a password and tells me my security is "open" It's not It's "WPA/2" I click on on this dialog.. then a new dialog comes up, with my network, WPA/2 and my password in it. It will tell me my password is wrong. I don't change a single
<dfergfla[m]>
thing. I just click OK. One of two things happens here. It will either connect, or it give me another round of the two dialog boxes, then connect. If I go into /system/setting/network and remove the "Wireless" file in there. The dialogs will stop and all I have to do is click on my network in the list and it connects. If I open the file "Wireless" I can see "network Electrabase" listed. Which is my wireless.
<dfergfla[m]>
See, it's weird.
<dfergfla[m]>
If I put the "wireless" file back. It goes back to the dialog things again.
<nephele[m]>
That is what pulkomandy ment above with it opening a password box on errors
<nephele[m]>
Maybe you could put a description on the bugtracker? it sounds like you have a differentish issue, maybe the settings file gets corupted or something wierd
<dfergfla[m]>
Will do.
<Coldfirex>
sory, meant HaikuPorts, cuz its there too
mrentropyvcs has quit [Quit: Vision[0.10.3]: i've been blurred!]
<dfergfla[m]>
waddlesplash: Ok, Mr Waddlespalsh. It would seem it is done.
beaglejoe has quit [Quit: Leaving]
* nephele[m]
is still amused at iOS email shortening "Mr. Waddlesplash" to "Mr." and then putting it infornt of other participants in the mailing list thread
<waddlesplash>
LOL
<waddlesplash>
dfergfla[m]: open this file: src/add-ons/kernel/bus_managers/ps2/ps2_common.h -- and go to line 33, and removethe "//" in front of it
<waddlesplash>
dfergfla[m]: then re-run the same jam command as before
<dfergfla[m]>
Ok like 33 now reads "#define TRACE_PS2
<dfergfla[m]>
building again...
<dfergfla[m]>
waddlesplash: Okl, that appears to be done.. last line in the terminal reads "...updated 779 target(s)"
<waddlesplash>
just a few lines before that, it will have a full path that ends in .../haiku.hpkg
<waddlesplash>
copy that full path, and do: $ pkgman install <path>
<waddlesplash>
this will install the just-built package
<BrunoSpr>
hi all; texstudio does not open here on 32bit nightly. TexStudio does not open on Haiku 32bit nightly hrev.55378
<dfergfla[m]>
Ok I have a like that reads ".... objects/haiku/x86_64/packages/haiku.pkg" I copied everything from the "/" over and have "pkgman install /haiku/x86_64/packages/haiku.pkg" and I get the error "*** Failed to find a match for /haiku/z86_64....."
<nephele[m]>
you copied a part of the path or so? I don't think /haiku/x86_64 exists
<dfergfla[m]>
no it doesn't but that is what is in the line.
<dfergfla[m]>
I'm trying find haiku.pkg but can't seem to find it.
<nephele[m]>
it's in ../generated/ somewhere
<nephele[m]>
but the line should tell you, it looks like you only copied a part of it
BrunoSpr has quit [Quit: Vision[0.10.3]: i've been shreederd!]
<dfergfla[m]>
When I look in the "generated.x86_64" folder there isn't a folder called "packaging" in there and I can't find haiku.pkg
netpositive has quit [Ping timeout: 480 seconds]
<dfergfla[m]>
When I do a search for "haiku.pkg" nothing comes up.
<dfergfla[m]>
hang on... it helps if I search for hpkg and pkg
Maturion has quit [Read error: Connection reset by peer]
<waddlesplash>
dfergfla[m]: you need the entire path.
<waddlesplash>
objects/haiku...
gouchi has quit [Remote host closed the connection]
<dfergfla[m]>
I think I got it. It says to reboot... wish me luck
Maturion has joined #haiku
<dfergfla[m]>
ok, I'm rebooted
<dfergfla[m]>
waddlesplash: Are there any particular test cases you need me to run though?
<waddlesplash>
no, just upload your syslog to the ticket
<waddlesplash>
PulkoMandy is the one who commeted before, hopefully he can glance at it
netpositive has joined #haiku
<waddlesplash>
I will at least read through it
<dfergfla[m]>
ok
<dfergfla[m]>
Do I need to uninstall this or will the next update just over write it?
<waddlesplash>
it will get overwritten
<dfergfla[m]>
ok, thanks
<dfergfla[m]>
Thanks for your help. I do hope this can be worked out.
gouchi has joined #haiku
<dfergfla[m]>
ummm small issue. I can connect my wireless but Webpositve will not load any pages at all. I get an error "Operation not supported"
<dfergfla[m]>
So I tried putting in my USB and mouning it so I could copy the log. My USB mounts but as read only. I am not given the option to mount it as read/write like I normally do.
<dfergfla[m]>
So, I have the log.. but can't seem to get it where it needs to go.
<waddlesplash>
just copy the log to your desktop
<dfergfla[m]>
yes the log is on the desktop.
<waddlesplash>
and reboot into an older state, probably somehow the build you made is a little broken
<dfergfla[m]>
OK, do I use the "space" bar during boot for that?
netpositive has quit [Ping timeout: 480 seconds]
jezek2 has quit [Read error: Connection reset by peer]
jezek2 has joined #haiku
<waddlesplash>
spam spacebar under EFI, yes
<dfergfla[m]>
Ok, I'm in the Haiku Boot Loader... now what?
gouchi has quit [Remote host closed the connection]
jmairboeck_ has quit [Quit: Konversation terminated!]
<dfergfla[m]>
I found an other way... thanks
Animortis has joined #haiku
gouchi has joined #haiku
<waddlesplash>
dfergfla[m]: sorry I forgot to ask ... did you click the touchpad buttons a bunch just before copying the syslog?
_Dario_ has quit [Quit: Vision[0.10.3]: i've been blurred!]
gouchi has quit [Remote host closed the connection]
<dfergfla[m]>
waddlesplash: yep
<dfergfla[m]>
I would like to ask a general question for anyone here. I am getting ready to build a new PC. Primarily for Linux. I hope for it to be Haiku compatible also. Anyone here have a Haiku box that is using a relatively new micro ATX mobo? Intel or AMD is fine.
<dfergfla[m]>
I want to really start working with Haiku as much as I can and I need to run it on something other than my old laptop.
Animortis has joined #haiku
AlwaysLivid has quit [Quit: “I was also caught by absence in all its forms.”, -- Paul Éluard ]
<nekobot>
[haiku/haiku] 4a7039147253 - arm: make sure fdt bus_mananger is added for arm
<Coldfirex>
any built in sound files on the anyboot iso to test audio?
<Vidrep_64>
I got my Gigabyte BRIX all set up with LibreELEC, so now I can repurpose my old ASUS EeeBox for Haiku
<Coldfirex>
nice
<Vidrep_64>
I think Haiku would make a nice HTPC if we could get OpenVPN working and polish up our streaming implementation
<Coldfirex>
booo. I cant drag windows using the touchpad. Is that a current limitation?
<Vidrep_64>
It's surprisingly good considering we don't have any hardware acceleration
<Coldfirex>
Might as well shoot straight for wireguard imo
<Coldfirex>
though I know we have other subsystem work before that
<Vidrep_64>
There's a lot of pie-in-the-sky stuff on everyones wishlist
<Coldfirex>
indeed
<Coldfirex>
hence why Im teaching myself c++ so I can help some day
<Vidrep_64>
I've been around this project long enough to know what realistic expectations are
<Vidrep_64>
If you shop wisely for your hardware, it's not that difficult to use Haiku as a every day OS
<Coldfirex>
easier and easier
<Vidrep_64>
The most obvious impediment is the browser. That would be #1 on my priority list, but not everybody has the time, motivation or skillset to work on it
<Coldfirex>
agreed
<Coldfirex>
hmm trackpad button dont work either
vezhlys has quit [Read error: Connection reset by peer]
<Vidrep_64>
Coldfirex, what kind of laptop?
Coldfirex has quit [Quit: Vision[0.10.3]: i've been blurred!]
Coldfirex has joined #haiku
<tqh>
You don't need to spam spacebar anymore for boot menu, just press one to three times should be enough.
<tqh>
It was fixed a long time ago.
tbcr has quit [Quit: WeeChat 2.8]
bronzie94 has joined #haiku
<Skipp_OSX>
Vidrep_64 I added the Colors! color picker if you can get it to work
<Skipp_OSX>
I can lead you through it. I'm trying to make the install easier but no success so far getting type system to work for me
tqh has quit [Remote host closed the connection]
<Skipp_OSX>
Coldfirex does Trackpad preferences help with the dragging windows?
<Coldfirex>
Skipp_OSX: Not that I could tell. I was able to drag only slightly but not reliably. Maybe because the trackpad buttons didnt work and thats what Im used to holding down to drag
nhtello has quit [Quit: Vision[0.10.3]: i've been blurred!]