<nekobot>
[haiku/haiku] 710016817ca1 - tests/qemu: Fix network on riscv64 test vm
humdinger has joined #haiku
<Begas_VM>
'lo humdinger :)
<humdinger>
hi ho!
<zdykstra>
hola humdinger, Begas_VM, PulkoMandy
<humdinger>
hiya zdykstra
<Begas_VM>
hi zdykstra :)
<Udi>
Is there a way to turn off the screen when laptop lid is closed?
<Begas_VM>
never tried it actually
<humdinger>
just tried it.
<Begas_VM>
heh
<humdinger>
it seems to do here.
<Begas_VM>
on/off/on/off? ;)
<humdinger>
my laptops screen is kinda loose. I won't flap it around too much...
<Begas_VM>
k, same here on/off .... :)
<Udi>
my dell stays on. wonder if something in bios
<humdinger>
not much to tweak in my BIOS
<humdinger>
noting ouput to syslog when closing/opening the lid
<humdinger>
intel_extreme driver here
vector1dev[m]1 has joined #haiku
CPYou has quit [Quit: leaving]
CPYou has joined #haiku
CPYou has quit [Quit: Lost terminal]
CPYou has joined #haiku
CPYou has quit []
humdinger has quit [Quit: Vision[]: Oi with the poodles already!!]
<pairisto[m]>
Quick question, how do I get the driver in src/add-ons/kernel/drivers/network/tun to build into the OS? Does it need the HaikuInstall section or something else?
<nekobot>
[haiku/haiku] 5676ddf7cac8 - repo/riscv64: Bump HaikuPorts build-packages for riscv64
<korli>
pairisto[m]: you need to use "AddDriversToPackage net : tun ;" in build/jam/packages/Haiku or possibly AddDriversToHaikuImage net : tun ; in build/jam/UserBuildConfig
<korli>
I think AddDriversToHaikuImage is outdated though
gouchi has joined #haiku
gouchi has quit [Remote host closed the connection]
tomxcd has joined #haiku
<pairisto[m]>
nothing else though, I don't need to use jam in the drivers directory itself?
<tomxcd>
hello
<pairisto[m]>
hello
<vector1dev[m]1>
hello
Diver has quit [Quit: Leaving.]
<Udi>
does anyone know how to get nmap working?
<zard>
hello
<zard>
(actually, goodbye)
<vector1dev[m]1>
lol
zard has quit [Quit: leaving]
B2IA has quit [Remote host closed the connection]
DKnoto has quit [Quit: Leaving]
DKnoto has joined #haiku
B2IA has joined #haiku
<korli>
pairisto[m]: atm the driver is named tun_config, can be renamed to "<driver>tun" when you prefer, then use that with AddDriversToPackage net : <driver>tun ;
<pairisto[m]>
could I just name it tun or does it need to be <driver>tun?
<korli>
the network module is already named "tun", they need to be different
<botifico>
[haiku/infrastructure] kallisti5 2f8fe36 - concourse: riscv64 images are now nightly instead of minimum!
Begasus has quit [Quit: Leaving]
robxnano[m] has quit [Quit: Client limit exceeded: 20000]
<pairisto[m]>
got it, but now when I build I get util/list.h: No such file or directory I already tried adding UsePrivateHeaders kernel to the jamfile but then it complained about atomic so i am not sure where to go from there?
<PulkoMandy>
It is probably easier to debug this if you put your work in progress changes on gerrit or some other git host so we can look into it
jmairboeck has quit [Quit: Konversation terminated!]
<pairisto[m]>
one sec, gotta make sure the code doesn't revert back to before I changed it
<PulkoMandy>
I think you need to use UsePrivateKernelHeaders ;
<PulkoMandy>
This will include arch-specific headers in addition to the ones in headers/private/kernel
korli has quit [Quit: Page closed]
CPYou has joined #haiku
tomxcd has quit [Quit: Leaving]
mmu_man has joined #haiku
CPYou has quit [Remote host closed the connection]
CPYou has joined #haiku
CPYou has quit [Remote host closed the connection]
CPYou has joined #haiku
<pairisto[m]>
thank you, that works!
<pairisto[m]>
though there might be a new problem but I'll deal with it when I get there
dqk has joined #haiku
dqk_ has quit [Ping timeout: 480 seconds]
<pairisto[m]>
question, what would then be its name? When I call ifconfig tun inet 10.10.10.10 255.255.255.0 up it keeps failing on the open function (code on gerrit) and I think its under a different name? either that or thats not how device drivers are called to open
<pairisto[m]>
* question, what would then be its name? When I call ifconfig tun inet 10.10.10.10 255.255.255.0 up it keeps failing on the open function (code on gerrit in tun.cpp) and I think its under a different name? either that or that's not how device drivers are called to open
<pairisto[m]>
* question, what would then be its name? When I call ifconfig tun inet 10.10.10.10 255.255.255.0 up it keeps failing on the open function with File or directory not found (code on gerrit in tun.cpp) and I think its under a different name? either that or that's not how device drivers are called to open
Evan[m] has quit [Quit: Client limit exceeded: 20000]
<pairisto[m]>
I also already tried passing it the TUN_MODULE_NAME
<x512[m]>
pairisto: Can you run `ls -l /boot/system/add-ons/kernel/network/devices`?
<x512[m]>
Can you try to add some debug output in tun_init() function?
<pairisto[m]>
* you can add it to build/jam/images/definitions/minimum under SYSTEM_NETWORK_DEVICES and build it with jam -q tun and the module will be there
<pairisto[m]>
tun_init is fine, the interface gets made normally through ifconfig tun inet create which calls tun_init() but when I run up with ifconfig and it goes into the tun_up function, it doesn't think that their is a driver by that name that can be opened there. When I invoke up in ifconfig it gives me the error ifconfig: Setting flags failed: No such file or directory
<pairisto[m]>
I know that the driver is on the system because I had the init_hardware function within src/add-ons/kernel/drivers/network/tun/driver.c it set to return B_OK which made an interface on start up, so I set it to return B_INTERFACE_ERROR_BASE so that it wouldn't. But I need to be able t call it and not have it start upon startup
<pairisto[m]>
* you can add tun to build/jam/images/definitions/minimum under SYSTEM_NETWORK_DEVICES and build it with jam -q tun and the module will be there
<pairisto[m]>
is there a way to list all drivers that were built with the system?
<x512[m]>
tree /boot/system/add-ons/kernel
AlaskanEmily has joined #haiku
<pairisto[m]>
So it is there in /boot/system/add-ons/kernel/drivers/bin
<x512[m]>
No entries in /dev/net. No patches to network code except enable tun add-on install.
<x512[m]>
In theory /dev/net entry is not needed.
<pairisto[m]>
well the issue with that is that I need a way of writing data to and from this interface to a program that sits in-between it and the internet (ala OpenVPN). It needs to be able to write and read data to and from an interface in order to actually work so having the module open, close, read, and write to a driver is needed
<pairisto[m]>
OpenVPN uses read and write syscalls so that is another reason why a driver is needed
<x512[m]>
Can you point OpenVPN code that interacts with TUN?