<coolcoder613_32>
Got it refurbished, with 8GB of RAM and a SSD.
mmu_man has quit [Ping timeout: 480 seconds]
coolcoder613 has quit [Ping timeout: 480 seconds]
coolcoder613 has joined #haiku
erysdren has joined #haiku
<coolcoder613>
Hi erysdren
<erysdren>
hi
<coolcoder613>
I've got RustPython working properly on DOS!
AD_MOS2 has quit [Read error: Connection reset by peer]
<erysdren>
hell yeah nice
coolcoder613_32 has quit [Ping timeout: 480 seconds]
<erysdren>
so, i guess haiku doesn't support my wifi card under EFI
<erysdren>
but it does under BIOS?
<erysdren>
strange
<coolcoder613>
Does it support on live USB? How is that booting?
<erysdren>
for reference my card is idualwifi7260
<erysdren>
it says "Not a WLAN device!" under EFI but works just fine under BIOS
<erysdren>
Live USB boots under EFI, no internet
<coolcoder613>
And if you boot it with BIOS?
<erysdren>
haven't tried yet, but presumably it works
<erysdren>
my other haiku install in this machine under BIOS works with wifi
<erysdren>
with the same wifi card
<coolcoder613>
Installed from the same USB?
<erysdren>
yeah
<erysdren>
R1 beta4
<erysdren>
I disabled CSM in my UEFI BIOS and now Haiku gets my native monitor resolution instead of being stuck to VESA. but under EFI the networking doesn't work
<coolcoder613>
Did you make any changes in the live enviroment?
<erysdren>
it still works on linux and windows
<erysdren>
no, just installed and then shut down
<erysdren>
do you think a nightly might help?
<coolcoder613>
How can you find out what driver is being used in the BOIS system?
<coolcoder613>
BIOS
<erysdren>
not sure
<erysdren>
im gonna install the latest nightly and see what happens
<coolcoder613>
tesing
<coolcoder613>
How can i find/replace over multiple files from the command line?
bjorkintosh has quit [Ping timeout: 480 seconds]
Maturi0n has joined #haiku
<zdykstra>
sed
<coolcoder613>
I googled it and found that out
hightower4 has joined #haiku
Maturi0n_ has quit [Ping timeout: 480 seconds]
hightower3 has quit [Ping timeout: 480 seconds]
AlienSoldier has joined #haiku
erysdren has quit [Quit: Konversation terminated!]
erysdren has joined #haiku
<coolcoder613>
did it help?
<coolcoder613>
erysdren?
<erysdren>
nope
<erysdren>
couldn't boot the nightly
<erysdren>
lol
<coolcoder613>
What, KDL?
<erysdren>
i was too lazy to write it to a USB, plus qemu and ventoy didnt work
<erysdren>
i'll get around to actually writing it to a usb, i'm just tired right now
<coolcoder613>
What is your hardware?
<erysdren>
Intel Core i5-9600K @ 3.70 GHz
<erysdren>
4x8GB DDR4 RAM
<erysdren>
amd64
* coolcoder613
is salivating
<erysdren>
hehe
<coolcoder613>
my desktop has 3GB of ram and 2 pentiums
<erysdren>
this is a prebuilt machine from 2017 that my parents bought me back when money wasn't so tight
<coolcoder613>
My uncle found my desktop on the street, and gave it to my grandfather, who gave it to me
<coolcoder613>
So at least it was free
<coolcoder613>
The only thing i had to buy was the wifi dongle
<coolcoder613>
My laptop has 8GB of ram and 4 i7s, but that cost me $269 AUD
<coolcoder613>
refurbished
<erysdren>
still bummed that Haiku under EFI doesn't support my network hardware and i have no idea why
<erysdren>
i'll probably write up a whole report of the issues i'm getting and make a post on the haiku forum
<erysdren>
asking for help
<erysdren>
my sound card is still fucked up, but that seems independent of haiku
<erysdren>
it also doesn't work under linux or windows
<coolcoder613>
Is there any way you can see which driver is being used under BIOS?
<erysdren>
i'd have to reinstall a BIOS version and re-enable CSM in my UEFI BIOS
<coolcoder613>
What about BIOS booting the live USB?
<erysdren>
for some reason, when i enable CSM in my UEFI BIOS, it locks the framebuffer driver into only being able to use VESA resolutions
<erysdren>
which is kinda bullshit
<coolcoder613>
No, i think there is the VESA framebuffer and the EFI framebuffer
<coolcoder613>
Which support different resolutions
<erysdren>
the EFI Framebuffer driver is being used under EFI. but it doesn't support the same resolutions as when CSM is disabled
<erysdren>
when CSM is disabled, the EFI framebuffer driver supports my native monitor resolution. when CSM is enabled, it only supports up to 1280x1024
<coolcoder613>
CSM ON == BIOS, CSM OFF == EFI
<erysdren>
right
<erysdren>
regardless, i need networking to work under EFI Haiku
<erysdren>
but i have no idea how to do that
<coolcoder613>
Is there a way you can try and find out what driver is being used in BIOS mode?
<erysdren>
it said VESA last time i checked it
<erysdren>
oh, network driver
<coolcoder613>
yes
<erysdren>
i'll have to reinstall it, reboot and check
<coolcoder613>
What about live USB
<erysdren>
but it probably uses the same driver for the idualwifi7260 or whatever
<erysdren>
i'll have to write out a usb
<coolcoder613>
enable CSM and boot into *same* USB
<erysdren>
it's just gonna take a lot of time and i don't have a lot of patience right now
<erysdren>
regardless i have to write out a live usb
<erysdren>
or i guess i could use a live CD. still got one of those
<coolcoder613>
Yes
<erysdren>
i'll do it when i wake up, i'm exhausted
<erysdren>
cya in a few hours
<coolcoder613>
goodbye
<erysdren>
if you're still on i'll mention you and do the thing
mr_lou has joined #haiku
azazelpy has joined #haiku
azazelpy has quit [Quit: Leaving]
AlienSoldier has quit [Quit: Vision[]: i've been blurred!]
<Begasus>
bugger ... Warning: POLICY WARNING: "/packaging/harfbuzz/lib/libharfbuzz.so.0.60821.0" needs library "libglib-2.0.so.0", but the package doesn't seem to declare that as a requirement
<aa72>
installing haiku with only dezzipping a file ...
<aa72>
after partition + format
<erysdren>
ahh
<aa72>
the zip command must be the haiku zip command
erysdren has quit [Quit: Konversation terminated!]
<aa72>
becouse haiku zip command has inside befs attributes ...
<Begasus>
iirc that only works if the zip is created on a BFS fs
<aa72>
my poor brain ...
<Begasus>
so if you zip it up in Windows it won't have any bfs attributes
<Begasus>
could be wrong though*
<aa72>
yes, but you can build haiku zip command under linux ...
<aa72>
and so boot with linux and zip all the server1
<aa72>
and partition with gparted ...
<aa72>
and format with gparted ...
<Begasus>
reiserfs/ext* etc are not bfs
<aa72>
bfs is opensource as haiku ...
<aa72>
so build bfs under linux
mmu_man has joined #haiku
mmu_man has quit [Ping timeout: 480 seconds]
mr_lou has quit [Ping timeout: 480 seconds]
mmu_man has joined #haiku
<Begasus>
weird, ran the tests earlier on harfbuzz, but now for pango I get (again): /bin/sh: line 1: /packages/pango-1.50.14-1/cmd~meson/bin/meson: No such file or directory
<Begasus>
both use meson/ninja
HaikuUser has joined #haiku
HaikuUser has quit []
bjorkintosh has joined #haiku
wicknix_ has joined #haiku
<Begasus>
k, those should do it ...
wicknix has quit [Ping timeout: 480 seconds]
aa72 has left #haiku [#haiku]
erysdren has joined #haiku
aa72 has joined #haiku
Skipp_OSX has joined #haiku
<aa72>
Skipp_OSX : this time no os x ...
<Skipp_OSX>
I understand
<aa72>
thanks
<aa72>
win 11 + ubuntu + haiku in vm ...
<aa72>
haiku is reinstalling
<aa72>
waiting ...
<Skipp_OSX>
I went on a big redesign of my color pickers to support bi-directional message passing and I'm stuck on ping pong messages right now. I need a better way to determine the message origin than looking at the be:sender
<Skipp_OSX>
be:sender is a BMessenger object attached to the message that is used to determine the origin. However, it's not working right so messages get sent back and forth back and forth forever as the picker receives a color update, then updates sends a message back, which then triggers a new message and it goes between them.
<Skipp_OSX>
Hard to explain
<Skipp_OSX>
It works fine as long as the color picker is the originator of the message, but when it's the recipient, I need to do a better job of making sure not to forward the message back to sender.
aa72 has left #haiku [#haiku]
<Skipp_OSX>
it turns out asynchronous programming designs can be challenging.
<bjorkintosh>
a better conceptual model is required, it appears?
<Skipp_OSX>
I need better message termination handling once the update has been handled.
freddietilley has quit [Quit: WeeChat 4.0.2]
tuaris has joined #haiku
aa72 has joined #haiku
aa72 has left #haiku [#haiku]
aa72 has joined #haiku
<aa72>
Skipp_OSX : try pear os over mac book ... i have tried ... funny ;)
<aa72>
now my mac book is died and i have a veriton + lenovo thinkcentre
<aa72>
about AI : garbage in, garbage out ... ;)
OscarL has joined #haiku
<bjorkintosh>
no no no aa72! Queries In Garbage(?) Out. QIGO!
<aa72>
?
* OscarL
went to write a new script to test pip on all available Python versions... `touch ./test_pip.sh & lpe ./test_pip.sh`... turns out script was already there, but for older Python versions :-D
<bjorkintosh>
aa72, humans are flawless! it's the AIs that are laughably flawed.
<bjorkintosh>
we put in our Queries, and the stupid AI just spits out Garbaage
<zdykstra>
"AI"
<bjorkintosh>
hahah. exactly.
<OscarL>
I like to read it in Spanish... "Ayyy!"
<aa72>
yeaaaa bjorkintosh => we have soul !!! AI NO !!!
<bjorkintosh>
there you go. "AI" is naturally stupid. "Ayyyyy!"
* OscarL
has no soul.
<aa72>
humans with soul can choose ... AI cannot : only run a procedure ...
<nekobot>
[haiku/haiku] 0ec674cdcce6 - Debugger: fix lookup for DWARF5 tag names
cleo has joined #haiku
tqh has quit [Quit: Leaving]
yn0ga has joined #haiku
yn0ga has quit [Quit: Vision[]: i've been blurred!]
<Anarchos>
OscarL it worked
<Anarchos>
OscarL i thought there was a package but no, just download , unzip, add to PATH
<OscarL>
nice :-)
Atomozero has joined #haiku
jmairboeck has quit [Quit: Konversation terminated!]
<Anarchos>
OscarL i find it disturbing not being able to do 'pkgman install cmd:mvn'
HaikuUser has joined #haiku
HaikuUser has quit []
<OscarL>
I guess nobody bothered to write a recipe for it, and as it doesn't seems to need anything other than unzip / put symlink in bin or $PATH... packaging is not strictly needed.
<OscarL>
every new package/recipe adds to maintenance burden, and I guess things are done just when people step up to work on what they miss.
<OscarL>
I remember I only wanted to have pyserial available to do some tests... ended up touching up almost all the Python recipes by now :-D
<coolcoder613_32>
IRC is being flaky, i'll reconnect
coolcoder613_x86 has joined #haiku
<coolcoder613_x86>
Are you familiar with Python?
<OscarL>
If a device works on BIOS/CSM mode but not EFI... that hints to it possibly not being fully initialized/configured. See if it works after booting into Win/Lin, and doing a warm reboot.
<erysdren>
my network card does work in linux and windows, yeh
<erysdren>
i'm talking to you over that very card in linux right now!
<OscarL>
In any case... should log a ticket over dev.haiku-os.org for it, asuming it is not one there already.
<coolcoder613_x86>
erysdren, where does it say not a WLAN device?
<erysdren>
when i try to probe it via ifconfig
<OscarL>
I mean... do a warm-reboot into Haiku (after Win/Lin), and see if it "magically" starts working then.
<OscarL>
In any case... gotta run. Later folks!
<erysdren>
cya
OscarL has quit [Quit: Gone with the wind]
<erysdren>
off topic question, would haiku be considered an "immutable OS"?
<coolcoder613_32>
does it show up when you run `ifconfig`?
<erysdren>
i'm not sure what that means
<erysdren>
coolcoder, yes
<erysdren>
it shows up, but the MAC address is all zeros
<erysdren>
and it can't connect
<coolcoder613_32>
Immutable OS means system files and applications are readonly
<erysdren>
i guess haiku is immutable then
<erysdren>
you can't play with system dir files
<coolcoder613_32>
could you paste the whole output of ifconfig to a pastebin?
<coolcoder613_32>
and what does it show in Network preflet
<erysdren>
how would i get it on the internet? lol
<erysdren>
ok, what i'll do is boot into haiku, log the ifconfig output, and take a screenshot of Network
<erysdren>
and then put it on a usb
<coolcoder613_32>
Paste it into a file on a USB or on linux partition
<erysdren>
what's preflet mean?
<coolcoder613_32>
then reboot into linux
<coolcoder613_32>
preflet is preferences window/app
<erysdren>
ah right
<erysdren>
thanks
<erysdren>
ill be right back, then
<coolcoder613_32>
cya
erysdren has quit [Quit: Konversation terminated!]
<coolcoder613_32>
The idualwifi7260 driver (otherwise known as iwm from FreeBSD) is very flaky; it only supports 802.11a/b/g, not even 802.11n or 802.11ac (which the hardware supports). It also has problems with 5GHz mode. So unfortunately a lot of this is “expected behavior” until FreeBSD updates the driver (which it’s increasingly unclear they will ever do…)
<coolcoder613_32>
<coolcoder613_32>
This may be helpful to anyone having problems with the 7260 or other cards that use the iwm driver from FreeBSD.
<coolcoder613_32>
<coolcoder613_32>
I learned that my access point was configured to only accept connections from clients using 802.11n or newer. The iwm driver does not support the newer protocols, and only works in 802.11b or 802.11g modes. Unfortunately, this is not currently documented in FreeBSD, so I have submitted a patch to update their man page accordingly.
<coolcoder613_32>
<coolcoder613_32>
Once I enabled the legacy modes on my AP, the 7260 began working as expected.
<coolcoder613_32>
<coolcoder613_32>
It should probably be noted that on my Lenovo laptops they only load wifi from a fresh boot, regardless of the OS. Often enough a warm boot results in the wifi chip not coming up.