<nekobot>
[haiku/haiku] 946fa9e85e1f - Terminal: Adjust indentation for kColorTable.
<nekobot>
[haiku/haiku] 939b20db334e - Terminal: Add new files to DoCatalogs.
LinuxUser has quit [Remote host closed the connection]
x10z has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Yonle has quit [Remote host closed the connection]
<jessicah>
ah derp, forgot about the catalog rules
UbhayAnand[m] has joined #haiku
mmu_man has quit [Ping timeout: 480 seconds]
Yonle has joined #haiku
illwieckz_ has joined #haiku
x10z has joined #haiku
illwieckz has quit [Ping timeout: 480 seconds]
xet7 has quit [Remote host closed the connection]
x10z has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
x10z has joined #haiku
x10z has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
x10z has joined #haiku
Tekk has joined #haiku
<Tekk>
Hey, how do I get logs for the wifi stack? I get random disconnects, not sure if it's the firmware crashing or what.
<Tekk>
The usual trick of "look at what the posix layer would guess it is" doesn't work, and I don't see any obvious candidates in the menus
<Tekk>
nvm, found it.
<waddlesplash>
basically everything is in /var/log/syslog
<waddlesplash>
from the kernel+drivers, anyway. so wifi is in there
<Tekk>
Mhm. I hadn't thought to just scrounge around. Don't think it's Haiku's fault so much as a 20 year old wifi chip :D
<waddlesplash>
intel 2100/2200?
<Tekk>
Mhm.
<Tekk>
(Well, *sort of* in that there's no pcmcia support but it's hard to blame people for not wasting their time on drivers for that...)
<waddlesplash>
yeah, I think the FreeBSD drivers are a bit rotted out here, not sure anyone else really uses them anymore
<waddlesplash>
for the intel 2100/220 that is
<Tekk>
Seems to reconnect fast-ish enough. Just a little annoying since sometimes when it happens vision drops without telling me.
<waddlesplash>
well, you can check the logs for errors
<waddlesplash>
firmware crashes should be logged, yes
<Tekk>
yeah, when I looked it was stuff about the station moving out of range. No fw crash.
dby has joined #haiku
<waddlesplash>
it's possible the driver is reporting the firmware value incorrectly
<waddlesplash>
if you don't get such behavior on another OS, that seems probable
<waddlesplash>
I think FreeBSD refactored these old drivers "blindly" during the FreeBSD 9 -> 10 transition
<Tekk>
Probably just some failed channel negotiation or something. I'd probably poke at the router side first if it's enough to annoy me.
<Tekk>
This laptop's single-booting haiku
<waddlesplash>
these things are so old they probably support 802.11a/b only?
<waddlesplash>
or do they at least support a/b/g
<waddlesplash>
modern WiFi routers that support 802.11ac often throw 802.11a/b/g to the curb in favor of 802.11n/ac
<waddlesplash>
at least my home AP has options for prioritizing n/ac traffic, or even outright turning off a/b/g mode
<Tekk>
2003, so I'd have to check. I also have my router configured to be old in some aspects for an old Latitude D400 I had, which took some doing. I probably just need to go through the dance for this particular Thinkpad. Wifi's always touchy on old laptops.
<waddlesplash>
well, and it's even touchier with the really old FreeBSD drivers for this hardware :)
<Tekk>
True c:
<Tekk>
At least this works though. Annoyingly I don't think I've gotten the OS to boot on any computer I've tried from this decade or last. Just happy i can play around with it for the first time since the early 2010s
<waddlesplash>
really? weird
<waddlesplash>
I have a ThinkPad from 2015 and a custom Ryzen desktop from 2020, Haiku runs great on both
<Tekk>
Mhm. Thinkpad T480 and my desktop just hang forever on boot. I wanna say I fund some other laptop and I actually got a kernel panic on b4
<waddlesplash>
admittedly I selected the hardware for the Ryzen desktop kind of carefully
<Tekk>
found some other laptop*
<waddlesplash>
hang where?
<waddlesplash>
i.e. at what icon
<Tekk>
Hm
<Tekk>
Gimme a sec, still have the USB around.
<waddlesplash>
kernel panic may or may not be meaningful. if it's just "panic no boot partitions!" then that's a pretty generic problem, could be anything
<waddlesplash>
requires reading syslog to see what really went wrong, and try to work from there
<waddlesplash>
thankfully following my USB fixes and korli's device_manager work, that's getting rarer and rarer
<Tekk>
Now watch it make a liar out of me and boot in an instant...
<nekobot>
[haiku/haiku] 218a511cd418 - drivers/network/{ether,wlan}: Drop FreeBSD versions from Jamfiles.
<nekobot>
[haiku/haiku] 984e2e527bad - openbsd_network: Move ifq_*_oactive wrappers to a common header.
<waddlesplash>
looks like I should probably add another OpenBSD-esque function to the FreeBSD layer, and then rewrite all the bus_dmamem_* functions in openbsd_network/.../bus.h
<waddlesplash>
that'd allow me to delete a bunch of #ifdef __FreeBSD_version, and really ease porting of new drivers
<waddlesplash>
oh well, tomorrow's problem
<bjorkintosh>
interesting. so haiku's drivers piggy back off openbsd's drivers?
<bjorkintosh>
that's rather clever.
<waddlesplash>
I mean, we've used FreeBSD's ethernet and WiFi drivers for like 15 years
<waddlesplash>
that's not new. what is new is that I have a second "shim" layer to run OpenBSD drivers, as well
<waddlesplash>
that was mostly completed about a year ago
<bjorkintosh>
I wondered how haiku had so much hardware support.
<waddlesplash>
it's only for network drivers
<bjorkintosh>
so basically, if it works with openbsd or freebsd, it works with haiku?
<waddlesplash>
all other drivers besides network ones are our own work
<bjorkintosh>
oh i see.
<waddlesplash>
no, there's more limitations. it only works with PCI(e), and select USB drivers (not all)
<bjorkintosh>
audio, graphics, bluetooth, usb ...
<bjorkintosh>
oh.
<waddlesplash>
audio, usb is all us
<waddlesplash>
bluetooth is also all us, but it doesn't really work, so are we couting it?
<bjorkintosh>
I need to learn how that sort of wand is waved.
<waddlesplash>
graphics is technically all us too
<waddlesplash>
but, we'll see if that part lasts or not
<waddlesplash>
also it's only the absolute lowest level of network drivers, i.e. just talking to the hardware, where we borrow from FreeBSD/OpenBSD
<waddlesplash>
everything above that (TCP, sockets, etc.) is also all Haiku code
<waddlesplash>
(and we still have a few native network drivers anyway, e.g. virtio-net)
<Tekk>
waddlesplashseems like after the box with the maple leaf in front of it, before the IC on the T480.
<waddlesplash>
after, as in, that lights up but nothing after it does?
<Tekk>
Mhm
<waddlesplash>
"Mhm" = yes?
<Tekk>
Yes.
<waddlesplash>
ok, that's the "disks" stage
<Tekk>
Could get confused by the little Intel RST drive in there.
<waddlesplash>
try waiting a few minutes. if it still doesn't do anything, reboot, and get into the bootloader menu
<waddlesplash>
you can do this by either (EFI) spamming spacebar, or (legacy BIOS) holding "SHIFT"
<waddlesplash>
once in there, choose "Select debug options", then activate "Enable on screen debug output" and "Disable onscreen paging"
<waddlesplash>
then back out and "Continue booting". hopefully when it hangs, there will be relevant log information on the screen that can be captured
<waddlesplash>
but, I'm headed out for the night, so if you do get something, either just post it here, or if it looks actually helpful and not ambiguous, just fine a ticket and attach the picture