<kallisti5[m]>
Yeah, there are some bugs in rust on haiku at the moment. If you search those errors you'll probably find some bug reports I've opened for various crates
<kallisti5[m]>
Sorry. Late at night here. I can help a little more in the morning
coolcode1613_mac has joined #haiku
coolcoder613_mac has quit [Ping timeout: 480 seconds]
coolcode1613_mac has left #haiku [#haiku]
coolcode1613_mac has joined #haiku
coolcoder613eb has joined #haiku
coolcoder613eb has left #haiku [#haiku]
coolcoder613 has quit [Remote host closed the connection]
coolcoder613 has joined #haiku
mr_lou has joined #haiku
coolcoder613 has quit [Quit: Vision[]: i've been blurred!]
tombhadAC has quit [Quit: Vision[]: i've been blurred!]
rockfans has quit [Remote host closed the connection]
<coolcoder613>
Needs linux?
erysdren has joined #haiku
<coolcoder613>
I do have a bare metal linux install on this laptop, have never booted into it though
<nielx[m]>
in theory you could build rust from Haiku, but only on 64 bit with a lot of RAM
<coolcoder613>
I've got 8GB, does that qualify?
<nielx[m]>
you could try
<coolcoder613>
Would linux be faster?
<nielx[m]>
I'd say get it working first, then worry about speed
<coolcoder613>
I mean faster to build
<nielx[m]>
in my experience BFS is slow in comparison to modern file systems, and given the fact that you'll be doing a lot of reads and writes, it is almost certain that Linux will cross-compile faster
* coolcoder613
does not find any recent changes in nielx/rust
<nielx[m]>
You do have to think about what next then though. If you want to install it in /boot/system, you need to create a package.
<nielx[m]>
I have been able to build from (almost) vanilla source for a while now
<nielx[m]>
in the repo I pinged over I sent the 1.73.0 patch I am testing now
<coolcoder613>
Once the build finishes, you can upload it to rust-on-haiku.com, right?
<nielx[m]>
yes, and I'll update the haikuports recipe
<coolcoder613>
Which repo?
<nielx[m]>
but it will take about 2 days if things go right ;-)
<nielx[m]>
the one I sent earlier in the chat
<coolcoder613>
Oh, you have the patches there
<coolcoder613>
What about cross compiling from macOS, m1 macs \are quite fast
<coolcoder613>
--build-arg RUST_REV=?
<nielx[m]>
1.73.0
<coolcoder613>
Its building on my mac...
<nielx[m]>
cool!
<coolcoder613>
not rust-haiku-1.73.0
<coolcoder613>
actually, could you paste the whole podman build command?
<nielx[m]>
the 32 bit one is in the builds.md file
<nielx[m]>
you can tweak it for 64 bit
<coolcoder613>
What about SOURCE_FIXUP_SCRIPT, RUST_REPO?
<nielx[m]>
look at builds.md
KapiX has joined #haiku
freddietilley has joined #haiku
catcream_ has quit [Ping timeout: 480 seconds]
<coolcoder613_mac>
TEP 10/18: RUN python3 pkgman.py add-repo ${HAIKUPORTS_URL} && python3 pkgman.py install ${INSTALL_PACKAGES}
<coolcoder613_mac>
Error: building at STEP "RUN python3 pkgman.py add-repo ${HAIKUPORTS_URL} && python3 pkgman.py install ${INSTALL_PACKAGES}": while running runtime: exit status 139
KapiX has quit [Quit: KapiX]
<coolcoder613>
Apparently.... it doesnt like arm64
<nielx[m]>
too bad
<coolcoder613>
OK, booting into linux...
coolcoder613 has quit [Quit: Vision[]: i've been blurred!]
<coolcoder613_mac>
And... Not a bootable partition
<coolcoder613_mac>
Ok, that could be the swap i was trying to boot from
<coolcoder613_mac>
Still not a bootable partition :(
hightower3 has joined #haiku
razetime has joined #haiku
hightower2 has quit [Ping timeout: 480 seconds]
Begasus has joined #haiku
<Begasus>
g'morning peeps
<nielx[m]>
coolcoder613_mac: managed to get beyond the previous failure, but then another failure in cargo popped up. Re-running the build to work past that
<Begasus>
g'morgen nielx[m], wb :)
<nielx[m]>
goedemorgen, thx!
<Begasus>
worning on bumping rust I gather?
<nielx[m]>
It looks like I am. Was not planning to, but one finds oneself stuck in the middle of those things
<Begasus>
if it makes it build rav1e I'll buy you a beer (or a coffee) next time we meet :)
<nielx[m]>
I don't exactly recall what the issue was there, but I doubt it :-)
<Begasus>
well ... actually got it build with cargo, the cargo-c part still fails
<Begasus>
and that's the part we need :)
<Begasus>
looking into grpc I guess we are in a chain to update other packages for that ... protobuf .... abseil-cpp ... :/
<nielx[m]>
going AFK
<coolcoder613_mac>
Linux is installing....
* coolcoder613_mac
wishes linux would install half as fast as haiku
<thaflo>
did you try it putting it in .../drivers/bin ?
humdinger has joined #haiku
<realtaraharris>
yeah, but the instructions say to create a symbolic link, which is fine, but I'm not sure if I need to do that, too
<Begasus>
afk
<OscarL>
AFAIK, placing a drivers's binary in "drivers/bin" (+ symlink under the relevant "drivers/dev" category) is for only needed for drivers using the legacy API.
<OscarL>
I usually stick to (simple) drivers using the older API, just to make my life easier, so you'll want to wait for the real devs to show up and guide you.
<OscarL>
Instructions on how to build/install your custom "haiku.hkpg" (taken from the IRC logs, thanks waddlesplash!):
<OscarL>
jam -q -jN @nightly-raw haiku.hpkg
<OscarL>
pkgman install path/to/built/haiku.hpkg
<OscarL>
In any case, wish you luck on your testing, realtaraharris. Gotta bolt now.
<realtaraharris>
thanks!
OscarL has quit [Quit: Gone with the wind]
<PulkoMandy>
The ACPI display driver is not a display driver (yes, I know that's very confusing)
<PulkoMandy>
When I tested it I added it to haiku.hpkg
<PulkoMandy>
You can do this in build/jam/packages/haiku, I think uncommenting the line starting with "AddNewDriversToPackage display …"
<realtaraharris>
yeah, I found that
<PulkoMandy>
When I tested it on my machine, the acpi nodes that this is supposed to handle were not there at all
<PulkoMandy>
So the driâer just did nothing
<realtaraharris>
so I'm on an x86_64 host, and I want to build the whole thing for x86_64, and I haven't been able to build the whole tree
<realtaraharris>
the instructions on the website make it look like I have to use cross-compilation, but that's clearly wrong
<PulkoMandy>
That's correct, if you want to build everythiing you have to use the "cross" compiler (same instructions as on Linux)
<PulkoMandy>
Because the compiler shipped with Haiku can't build 32 bit executables,eand we need that to build the BIOS bootloader
<realtaraharris>
aha! someone on here yesterday told me wrong!
<PulkoMandy>
Without that, I think you should still be able to build just the haiku package (jam -q haiku.hpkg), but I have not tried that
freddietilley has quit [Quit: WeeChat 4.0.2]
<Begasus>
still pretty clean on the static libraries :)
* humdinger
is idle: BRB
mmu_man has quit [Ping timeout: 480 seconds]
mmu_man has joined #haiku
tuaris has joined #haiku
Begasus_32 has quit [Quit: Vision[]: Gone to the dogs!]
realtaraharris has quit [Quit: Vision[]: i've been blurred!]
walkingdisaster has quit [Quit: Vision[]: i've been blurred!]
<nekobot>
[haiku/haiku] 208006054c41 - kernel/vm: put pages in order on the clear page queue
<Begasus>
zdykstra, icu74.1 :)
realtaraharris has joined #haiku
realtaraharris is now known as Guest5187
Guest5187 is now known as realtaraharris
jmairboeck has joined #haiku
erysdren has quit [Quit: Konversation terminated!]
<Begasus>
closing down, cu peeps!
Begasus has quit [Quit: Vision[]: i've been blurred!]
<nielx[m]>
Rust 1.73.0 just finished building...
tombhadAC has joined #haiku
realtaraharris has quit [Quit: Vision[]: i've been blurred!]
realtaraharris has joined #haiku
realtaraharris has left #haiku [#haiku]
realtaraharris has joined #haiku
mr_lou has quit [Quit: Leaving]
<realtaraharris>
so after rebooting with my own haiku.hpkg installed, the configure script for the cross-compiler breaks
<realtaraharris>
when I run it, I get:
<realtaraharris>
checking build system type... x86_64-unknown-haiku_buildhost
<realtaraharris>
...
<realtaraharris>
configure: error: in `/boot/home/haiku/generated.x86_64/cross-tools-x86_64-build/binutils':
<realtaraharris>
configure: error: C compiler cannot create executables
<realtaraharris>
I really hate reaching for a second machine, but I think I'm just going to keep having a bad time if I don't
<nielx[m]>
what's the output in config.log?
<realtaraharris>
`/boot/system/develop/tools/bin/../lib/gcc/x86_64-unknown-haiku/13.2.0/../../../../x86_64-unknown-haiku/bin/ld: cannot find crti.o: No such file or directory`
<realtaraharris>
same error for start_dyn.o, init_term_dyn.o
<nielx[m]>
Is the haiku_devel package loaded?
<jmairboeck>
realtaraharris: you are probably missing a matching haiku_devel package. You can boot back into an older state and build and install that as well
<jmairboeck>
just add haiku_devel.hpkg to the jam command building haiku.hpkg to get both
<realtaraharris>
ok, easy enough :joy:
realtaraharris has quit [Quit: Vision[]: i've been blurred!]
jmairboeck has quit [Quit: Konversation terminated!]
kona has left #haiku [#haiku]
coolcoder613_32 has joined #haiku
<coolcoder613_32>
Good morning
<coolcoder613_32>
Rust finished, nielx[m]?
vdamewood has joined #haiku
mmu_man has quit [Ping timeout: 480 seconds]
nephele has joined #haiku
mmu_man has joined #haiku
tqh has quit [Remote host closed the connection]
Vidrep_64 has joined #haiku
Vidrep_64 has quit []
arti has quit []
<coolcoder613_32>
nielx[m]: Do you have a recipe for Rust 1.73.0?
Lunovus has joined #haiku
<Lunovus>
Hi there
<Lunovus>
I got a problem with Haiku not booting due to the intel_extreme driver
<Lunovus>
Works if I disable the package or boot with safe video driver
<Lunovus>
VESA driver works ok so far
B2IA has quit [Quit: Vision[]: i've been blurred!]
<Lunovus>
But I don't know why Haiku is not using the NVidia driver instead, utilizing my NVidia GFX card
B2IA has joined #haiku
<Lunovus>
The VESA driver is using my NVidia card to display things
<Lunovus>
I'll probably create a bug report later when I find the time
<Lunovus>
I find it just strange that I got a problem with the intel driver, stopping boot and install without extra settings, and the system not using the NVidia driver instead
<coolcoder613_32>
Are you sure there is a driver for your card?
<Lunovus>
Well is saw an NVidia driver in the packages
<coolcoder613_32>
For what card(s)?
<Lunovus>
No idea ;-)
<Lunovus>
My card is a GTX 1070
<Lunovus>
Are problems with the intel_extreme driver common?
<Lunovus>
Should I maybe try a nightlie?
<coolcoder613_32>
No idea here, try googling around?
<Lunovus>
Intel GFX is UHD Graphics 630 inside a i7 8700k
<Lunovus>
Have found some problems with it in the forums from years ago
<Lunovus>
It's just those problems may hit a lot of other people
<Lunovus>
People not as computer-smart as me..
<coolcoder613_32>
Not a lot of those people use Haiku ;)
<Lunovus>
But they could :-)
<x512[m]>
> GTX 1070
<Lunovus>
If it would boot, that is..
<x512[m]>
Too old for Nvidia open GPU driver.
<Lunovus>
No support for older cards?
<Lunovus>
I mean NVidia older cards
<coolcoder613_32>
I have a GeForce 210
OscarL has joined #haiku
<coolcoder613_32>
And... VESA
HaikuUser has joined #haiku
HaikuUser has quit []
<Lunovus>
VESA works, but I'D prefer a "real" NVidia driver
<Lunovus>
Apart from that intel_extreme driver preventing Haiku to boot
<OscarL>
Haiku's nvidia driver only supports old cards :-) (TNT to GeForce FX 7000 / Quadro)
<Lunovus>
Huh, so the card ain't too old, but too new?
<coolcoder613_32>
We dont have graphics acceleration, so all you would get over vesa is resolutions
<x512[m]>
Turing+ Nvidia GPU support is planned.
<OscarL>
your's... yes, same as my GT 1030.
<x512[m]>
But not yet.
<Lunovus>
Resolutions are fine with VESA, works OK with my 4k display
<coolcoder613_32>
Then there isn't much of a point to have a driver
<x512[m]>
Nvidia open GPU + NVK in theory allows to have hardware acceleration on Turing+ cards.
<OscarL>
I'd be happy with just working video overlays :-)
<coolcoder613_32>
You're the expert, x512[m] ;-)
<Lunovus>
OK, I'll file a bug report after I tried a nightly
<Lunovus>
Got another problem with a Synaptics touchpad on a laptop, but I'll probably add that to a post about that in the forum
<Lunovus>
Thanks for infos guys & gals :-)
realtaraharris has joined #haiku
<coolcoder613_32>
I enabled x86_gcc2 for Digger, and it works!
<coolcoder613_32>
It /was/ ported to unix in 2002, I guess...
<realtaraharris>
is there a tool that will list the files wrapped up inside an .hpkg?
<coolcoder613_32>
`package list`
<realtaraharris>
yay thanks!
<coolcoder613_32>
Whatcha working on?
<nephele>
Lunovus: the nvidia driver is for very old cards only
<nephele>
If you have one of those laptops with two gpus chances are you need intel_extreme working regardless, because usually the display is attached to it, and not the nvidia card
<Lunovus>
Yeah, got that
<Lunovus>
Have to check on my laptop, it has Intel and Radeon inside, hang on a sec
<nephele>
coolcoder613_32: the driver also gives better support, and backlight control etc
<coolcoder613_32>
backlight control... that would be nice
<nephele>
(My laptop doesn't have a working touchpad in haiku :g)
<Lunovus>
Laptop uses Intel driver
<coolcoder613_32>
(My touchpad works, but it is a really bad one)
<Lunovus>
Touchpad works, but it has buttons under the pad on the bottom for left & right click
<Lunovus>
If I use them, and move my finger on the pad, the mouse pointer jumps into the lower left edge of the screen
<coolcoder613_32>
(And now my battery is half-in, half-out, so I can only use it plugged in)
<Lunovus>
So I can't really use that "Brightness" slider in the screen prefs window
<Lunovus>
My battery has about 2 hrs. power, and it's a new one
<Lunovus>
I should have bought the more expensive option from eBay :-/
<coolcoder613_32>
Lunovus: You don't have a USB mouse you can use?
<Lunovus>
I can, but a better working touchpad would be, err, better :-)
<coolcoder613_32>
What kind of laptop is it? How good is the touchpad?
<Lunovus>
HP pavilion dv7
<Lunovus>
Some Synaptics stuff, can't compare to other touchpads
<coolcoder613_32>
My MacBook has a really good touchpad, so I never use a mouse, but on most laptops, I find it very hard to work without a mouse.
<Lunovus>
Would prefer a trackpoint, but it was cheap too buy used
<Lunovus>
Mouse works better, and the "Brightness" slider works too :-)
<Lunovus>
Strange string here in the "Screen" app:
<Lunovus>
Display is listed as "DO NOT USE - AUO 17.2"
<Lunovus>
Is that a string from the driver or the hardware?
<nephele>
the driver
<nephele>
you can ignore the do not use thing
<coolcoder613_32>
Why is it there then?
<Lunovus>
Hopefully ;-)
<nephele>
it is corrected in the nightly, basically we have these strings from a database, which includes the DO NOT USE part as a warning to manufacturers, to no longer use this ID
<nephele>
but, obviously screens exist that already use the ID :)
<nephele>
so waddlesplash already fixed this in the nightlies
<Lunovus>
*gg*
<nephele>
As for the touchpad, open a ticket :)
<Lunovus>
I probably add to that existing thread in the forum, and ask for a program to display the input events from the touchpad
<Lunovus>
Lt_Henry in the forum seems to have one
<Lunovus>
Written maybe, or is there a program I can download somewhere?
<coolcoder613_32>
My recipe for Rust 1.73.0 (fill in the cecksum if you are on 64-bit) https://0x0.st/Hy4I.0.recipe
realtaraharris has quit [Quit: Vision[]: i've been blurred!]
<nephele>
the forum doesn't help at all for bug reports...
<Lunovus>
If I had a program to display the events generated by the device, maybe I could look how to fix this myself
<nephele>
Not sure what your point is, I asked in that topic also to open a ticket and there was no response to that. if you don't even open a ticket I don't see how you expect anything to ever get fixed
<nephele>
If you want help in fixing it you can ask on the ticket, or just ask here right now ;)
<Lunovus>
I hope it's not the device itself that generates the "false" events
<Lunovus>
I now officially ask this to be fixed :-)
<nephele>
anyhow, all input events in Haiku go through the input_server in Haiku
<Lunovus>
So, is there a debug-tool to display all those events
<Lunovus>
?
<coolcoder613_32>
there is /var/log/syslog
<Lunovus>
Oookay, so is there a tool to filter the events in there in realtime, so I can find the ones I'm interested in?
<nephele>
Lunovus: If it is PS2 you can use the advice from PulkoMandy in the ticket you linked
<coolcoder613_32>
It is called grep
<nephele>
well, if you use the syslog you can use grep
<coolcoder613_32>
:)
<nephele>
not the nicest thing, sadly we don't have a central system logging tool that could just attach to servers :(