poopnugget142 has quit [Quit: Vision[]: i've been blurred!]
HaikuUser has joined #haiku
HaikuUser has quit []
xet7 has joined #haiku
cassisian has joined #haiku
poopnugget142 has joined #haiku
<poopnugget142>
Hey I attached a usb disc reader to my pc but nothing is poppin up when I put a disk in it or anything is there something I'm supposed to do?
cassisian has quit [Ping timeout: 480 seconds]
<bjorkintosh>
try unplugging it, putting the disc in, and then plugging it in to see if that makes a difference.
<poopnugget142>
I got a huge debug message when I did that saying something about the device not becoming unbusy
Guest14842 has left #haiku [#haiku]
<bjorkintosh>
when in doubt, restart
Guest14842 has joined #haiku
<poopnugget142>
Yeah I tried that for some reason my boot up time is extremely long with this thing plugged in
<poopnugget142>
I'm not sure what should happen though if it does work correctly
<poopnugget142>
oh well if I can't use a cd thing with my computer it's not that big of a deal
cassisian has joined #haiku
OscarL has joined #haiku
<OscarL>
poopnugget142: if your PC has several USB ports, maybe try on different ones. Some may be USB 2.0 and others 3.x, and AFAIK, the latter may be better supported.
<OscarL>
in any case, I think it would be wise to open a ticket about that USB reader not working properly. Usefull info to add to such a ticket would be: the output of the "listdev" command, and a copy of the /var/log/syslog file.
Sid127 has quit [Remote host closed the connection]
Sid127 has joined #haiku
<OscarL>
poopnugget142: normally, after you insert a disc, you should be able to "right-click" on the Desktop, a context menu should appear, and under the "Mount" submenu, you should see your disk, and be able to click on it to mount it.
<OscarL>
that should normally make an icon for that disc (or for a particular "volume", if its a multi-track disc) on Desktop.
<OscarL>
For audio CDs, you should see the list of tracks as .wav files that you could simply copy onto your HDD/SSD (no need for specialized "ripping" software, albeit you could still use those if wanted).
erysdren has joined #haiku
Sid127 has quit [Read error: Connection reset by peer]
OscarL has quit [Remote host closed the connection]
cassisian has quit [Remote host closed the connection]
HaikuUser has joined #haiku
HaikuUser has quit []
AlaskanEmily has quit [Remote host closed the connection]
AlaskanEmily has joined #haiku
cassisian has joined #haiku
cassisian has quit [Ping timeout: 480 seconds]
freddietilley has joined #haiku
freddietilley has quit [Read error: Connection reset by peer]
cassisian has joined #haiku
stux|away has quit []
stux|away has joined #haiku
cassisian has quit [Ping timeout: 480 seconds]
freddietilley has joined #haiku
cassisian has joined #haiku
cassisian has quit [Remote host closed the connection]
pinaraf has joined #haiku
AndrevS has joined #haiku
cassisian has joined #haiku
AlaskanEmily has quit [Remote host closed the connection]
cassisian has quit [Ping timeout: 480 seconds]
coolcoder613 has joined #haiku
coolcoder613_ has quit [Ping timeout: 480 seconds]
cassisian has joined #haiku
cassisian has quit [Ping timeout: 480 seconds]
pol has joined #haiku
<pol>
I have a problem with Drawpile, the current version avilable on HaikuDepot would not allow connecting to server.
<Begasus[m]>
it worked here pol ?
<Begasus[m]>
at least I could host a session and the main developer could join
<Begasus[m]>
if it is with connecting to an external session I could check and talk to him about it
<pol>
Did you compile the newer version without uploading it to HaikuDepot maybe? The screenshot you sent was with version 2 and the highest currently avilable version on HaikuDepot is 1.something.
<Begasus[m]>
2.2.2 should be in the depot
<Begasus[m]>
atleast build finished on buildmasters yesterday
<Begasus[m]>
could you check (if you have it installed)?
Begasus has joined #haiku
nephele has joined #haiku
Sid127 has quit [Read error: Connection reset by peer]
Sid127 has joined #haiku
Guest14842 has left #haiku [#haiku]
Guest14842 has joined #haiku
* nephele
waves
xet7 has quit [Remote host closed the connection]
<Begasus[m]>
Hi nephele
<phschafft>
morning.
<phschafft>
nephele: do you have a few minutes for me today?
<nephele>
sure phschafft
<nephele>
I'm not doing much at the moment, so now is fine too :)
<phschafft>
would like to exchange some thoughts on colour profiles/themes/management as well as user management.
cassisian has joined #haiku
<Begasus[m]>
Hi phschafft
<phschafft>
mau also Begasus[m] :)
cassisian has quit [Ping timeout: 480 seconds]
mmu_man has joined #haiku
<Begasus[m]>
:)
<pol>
What should I check? It works and the new version is even better with custom skins and menu fonts follow system sizes.
<Begasus[m]>
+1
<Begasus[m]>
hosted a session before (hence the link), but that's closed already :)
<Begasus[m]>
afk for a bit
nephele_jabberfr has joined #haiku
<nephele>
drawpile Begasus[m]?
<nephele>
I've used that before on linux and windows, was great fun
cassisian has joined #haiku
Guest14842 has left #haiku [#haiku]
Guest14842 has joined #haiku
cassisian has quit [Ping timeout: 480 seconds]
xet7 has joined #haiku
HaikuUser has joined #haiku
HaikuUser has quit []
Nasina has quit [Read error: Connection reset by peer]
<Begasus[m]>
re
<Begasus[m]>
nephele: we already had it, just updated to latest release now (drawpile*)
<nephele>
very cool Begasus[m]
<Begasus[m]>
current patch also already merged upstream :)
Nasina has joined #haiku
<nephele>
that's really nice
<nephele>
i should try using it on Haiku
<Begasus[m]>
was pleasantly supprised that the host sessions worked, current main devel joined me in a session yesterday and just started drawing :)
<nephele>
that's the nice thing with drawpile indeed
<nephele>
i've not really used public lobbies, just with friends, but it was great fun
<Begasus[m]>
started out with the Haiku leaf as if he done it a lot of times
xet7 has quit [Remote host closed the connection]
<Begasus[m]>
granted, no Haiku icons in the UI, didn't ask if it was possible to change that (looked around a bit in the code but couldn't find some direct hits for it)
* Begasus[m]
checks if it looks different on Qt6.7.2 ...
<Begasus[m]>
same thing, my Qt6.9.0 isn't broken so far :P
Nasina has quit [Read error: Connection reset by peer]
Nasina has joined #haiku
Begasus_32 has joined #haiku
<nephele>
maybe it's setting the Icon theme directly in code
<Begasus[m]>
looking at the config file in settings it might well be so
<nephele>
sadly the Haiku style is not selcted by default
<nephele>
for the icons though, you can probably set it to haiku in code. but keep in mind these are "generic" icons usually, and it's probably set like this to get atleast one consistent icon set
<nephele>
so if you set it to haiku icons you probably also need to adjust the haiku icons for it, and maybe add new ones etc
<Begasus>
it's best not to fiddle too much there, for Tokodon it's already a problem
<Begasus>
when I try to switch to Haiku icons some don't render good
<Begasus>
another thing is that in dark mode the Haiku icon theme doesn't look too well (icons don't show good enough)
AndrevS has quit [Quit: umount /dev/irc]
<Begasus>
but I try to switch to the Haiku icon theme where I can for the users :)
<Begasus[m]>
second one dropping support for < Qt6.8.0 in KDE ...
cassisian has joined #haiku
freddietilley has quit [Ping timeout: 480 seconds]
freddietilley has joined #haiku
cassisian has quit [Ping timeout: 480 seconds]
Molnija has joined #haiku
FreeFull has joined #haiku
<pol>
Somebody have any idea what the "offscreen" thread, part of the app_server, is doing? I see it consume CPU regularlly.
Chain|Q has quit [Quit: [.life.support.system.failure.]]
Chain|Q has joined #haiku
<ilzu[m]>
fancy2209: Did you get the kernel_ppc debug symbols loaded in gdb yet?
<nekobot>
• Begasus (74d0f533): abaddon, revbump for spdlog version (#12472)…
<ilzu[m]>
fancy2209: What we did with yn0ga was to achieve that was that we first used readelf to get kernel_ppc entry point and section list. Then we calculated the delta of entry point and .text section. After that we launched gdb on the bootloader, and set breakpoint to platform_start_kernel. When running and breaking at that point print the variable kernelEntry to get the address where the kernel is loaded, and then subtract the calculated delta from
<ilzu[m]>
that value. Then use that value to offset the symbols in kernel file. Yn0ga had some script in 3rdparty/yn0ga/ to do some parts of this.
Nasina has quit [Read error: Connection reset by peer]
Nasina has joined #haiku
pol has quit [Read error: No route to host]
pol has joined #haiku
Nasina has quit [Read error: Connection reset by peer]
<Begasus[m]>
I knew korli mentioned something about it
<Begasus[m]>
atleast nodejs16 is fine with python3.10
<Begasus[m]>
(build checked on 64bit though)
* OscarL
goes to take a look.
talos has quit [Ping timeout: 480 seconds]
talos6 is now known as talos
<OscarL>
Begasus[m]: the error you posted was the only one you saw for nodejs20 on 32 bits?
<Begasus[m]>
argh :(
<Begasus[m]>
only one I saw yes, but build wasn't completed
<Begasus[m]>
nodejs16 build failed also on buildmaster :/
<OscarL>
if you haven't nuked those nodejs20 sources... you could try adding "(pid_t)" or "(int32_t)" as typecast in that line with the error, might get you further along a bit at least.
<Begasus[m]>
booting the other 32bit install now
<Begasus[m]>
didn't clean the code there (yet)
HaikuUser has joined #haiku
HaikuUser has quit []
begas has joined #haiku
<Begasus>
k, let's check this ...
<Begasus>
crossing fingers ...
<begas>
../src/node_process_object.cc:78:28: error: call of overloaded 'Set(pid_t)' is ambiguous
<OscarL>
"(int32_t)" should then... as it should exactly match one of the candidates: "Set(int32_t)"
BlueSky76 has quit [Quit: WeeChat 3.8]
<OscarL>
pid_t *is* an int32_t in the end in Haiku, but maybe the compiler is just too picky :-)
HaikuUser has joined #haiku
HaikuUser has quit []
<Begasus>
second run ...
<Begasus>
meanwhile ... testing nodejs24 here (re-creating patchset first)
<Begasus>
OscarL does this change behaviour when applied on 64bit?
zardshard has left #haiku [Error from remote client]
zardshard has joined #haiku
<OscarL>
not as far as I can tell from reading Haiku's headers (where pid_t is a typdef of "__haiku_int32", which is a typedef of "__haiku_std_int32", which is a typedef of "int32_t" in the end.
<Begasus>
0_°
<OscarL>
try grepping the nodejs20 sources to see where that "uv_pid_t" type gets defined.
<Begasus>
the laptop is pretty slow already without grep'n now :)
<OscarL>
heh
nephele has quit [Quit: Vision[]: i've been blurred!]
<Begasus>
anything that's not "this" laptop is slow now :P
<Begasus>
and than this guy speaking about 24 cores in krita's room earlier ... :D
<Begasus>
was that correct? then/than? :)
<OscarL>
*then
<Begasus>
bugger ...
<Begasus>
biab
* OscarL
will probably cry next time he has to do an optimized Python build with LTO enabled on this 2 cores Celeron.
bjorkintosh has quit [Ping timeout: 480 seconds]
<Begasus>
heh
<Begasus>
well, progressing ....
<Molnija>
do you need a faster computer
<Begasus>
most faster ones are 64bit only I think
<Molnija>
rip
xet7 has joined #haiku
<Begasus>
at least the ones that a "bit" faster only run 64bit
<Begasus>
but OscarL could use a faster one :)
<Molnija>
only run 64bit, in such a way that a 32 bit OS wouldn't work?
<Molnija>
rip
<Begasus>
still need some 32bit setup to check builds like this for nodejs
<OscarL>
I haven't tried booting Haiku 32 bits on this Celeron N4020 netbook, but I suspect I might need a 32 bits Haiku EFI boot loader for that to work.
<OscarL>
(no BIOS/Legacy/CSM support on this one)
<Begasus>
same on this I guess OscarL, nogo on booting 32bit anyboot image
BlueSky76 has joined #haiku
<Begasus>
hi BlueSky76
freddietilley has quit [Quit: WeeChat 4.6.3]
erysdren has joined #haiku
xet7 has quit [Ping timeout: 480 seconds]
xet7 has joined #haiku
cassisian has quit [Remote host closed the connection]
cassisian has joined #haiku
cassisian has quit [Ping timeout: 480 seconds]
<Begasus[m]>
still busy OscarL :) (slow but still ...)
* OscarL
keeps his fingers crossed (which somehow doesn't makes his typing *worse*).
<Begasus[m]>
lol
<Begasus[m]>
3/4 for the patchset done for nodejs24
<Begasus[m]>
biggest consume is time when it needs to extract/initialize
<OscarL>
you should only need to do that once at least.
<OscarL>
"git reset ORIGIN" should leave you in a sane state to re-apply patchsets if needed.
<Begasus[m]>
I'm doing it on every change/fix
<OscarL>
(possibly adding "git clean" if you also ran some ./configure or something like that)
cassisian has joined #haiku
<Begasus[m]>
as mentioned, should check that on an "easy" patchset first :)
<Begasus[m]>
hp * -c / hp * -b
<OscarL>
ouch :-(
<Begasus[m]>
when I hit something with a smaller source/patchset I'll call in your help
<OscarL>
you don't need to follow my "guide", but you can just run that "git reset ORIGIN" instead of nuking the tree :-)
<Begasus[m]>
don't want to risk to loose it all here and start from scratch :)
<OscarL>
*and do things like you normally do, I mean.
<Begasus[m]>
could try that on the next error
<OscarL>
if you run "hp -e" regularly, you should be safe
<Begasus[m]>
that's the scary part :)
<OscarL>
I usually zip the "currently good" patchset if I'm extra paranoid :-D
<Begasus[m]>
I'll duplicate it before I try that "git reset" :)
* Begasus[m]
pulls OscarL to the chair next to him ....
<Begasus[m]>
OK, duplicated the patchset, extracted, fixed the file, ran "git diff" and copied the changes to the patchset
<Begasus[m]>
do I now run "git reset ORIGIN"?
<OscarL>
"git reset --hard ORIGIN" should leave that tree as if you had just unpacked it and applied the original patchset (it will not contain the new adition you just made to it).
<Begasus[m]>
won't it fail on the same file then?
<Begasus[m]>
ok, that file got indeed reloaded without the changes
<OscarL>
if you are manually editing the patchset, you need to reply it manually via "git am ../../patches/foobar.patchset"
<Begasus[m]>
fatal: previous rebase directory .git/rebase-apply still exists but mbox given.
<OscarL>
or hp *might* re-apply it if you delete the flag for that step (booting VM to check)
<Begasus[m]>
0_°
<OscarL>
under the works dirs... hp leaves a "flag.patchset" empty file after it applies the patchset.
<OscarL>
if it sees that file, it won't re-apply it, AFAIK.
<phschafft>
nekobot: btw. thank you for your good input in our meeting!
<Begasus[m]>
flag.unpack/flag.validate are in there
<OscarL>
no idea why it has that rebase thing going on.
<Begasus[m]>
git reset --hard ORIGIN?
<OscarL>
that should leave it in a sane state.
<OscarL>
"git clean -n" should show you if you have some extra files (without removing them)
<Begasus[m]>
/Opslag/haikuports/net-libs/nodejs/work-24.1.0/sources/node-v24.1.0> git am ../../../patches/nodejs-24.1.0.patchset
<Begasus[m]>
fatal: previous rebase directory .git/rebase-apply still exists but mbox given.
<OscarL>
I try "hp nodejs20" and cancel the build right away, to see if it tries to re-apply the patchset.
<Begasus[m]>
I think I'm going to continue my way here for this, gives me creeps thinking I would have to start all over
<OscarL>
might be that hp -e clears the "flag.patchset" file?
<Begasus[m]>
well "hp * -b" does the same?
<Begasus[m]>
not going to take that risc OscarL :)
<OscarL>
just don't "hp -c" it
<Begasus[m]>
not for this :D
<Begasus[m]>
how do I know what it hits next then?
<OscarL>
not sure what you mean by "hits".
<Begasus[m]>
hmm .... sec
<Begasus[m]>
well, the next error in the patchset that doesn't apply
<OscarL>
if you keep a copy of your patchset (I would even suggest to just commit differen versions on the main HaikuPorts clone, you can always squash/rebase those later on)... loosing work should not be possible.
<OscarL>
keeping track of that is why I stopped doing things manually.
<OscarL>
ok for smaller patchsets, but for larger ones... manually editing is really tedious and error prone.
<OscarL>
in any case... instead of manually editing the patchset... you can just commit the changes you made on the work tree... and then "hp -e" will at least extract those for you without you having to edit the .patchset manually.
<Begasus[m]>
yeah, time consuming, but atleast I don't have to clean now
<OscarL>
before that first "git diff" you did used "git am " I guess?
<OscarL>
wish I was better at explaining things :-(
<Begasus[m]>
that "git am --abort" yes
poopnugget142 has joined #haiku
<poopnugget142>
if an application doesn't have the fullscreen button is there anyway to still fullscreen it?
<OscarL>
Begasus[m]: I try to think of ways of explaining how I would proceed, but I'm affraid I will just confuse you further. :-D
<Begasus[m]>
yeah, good for now, even if it's not the best way OscarL :)
<poopnugget142>
OscarL: I saw your message from yeserday about the disk thank you
HaikuUser has joined #haiku
HaikuUser has quit []
<Begasus[m]>
ps, I was wrong earlier, not yet halfway there :)
<OscarL>
poopnugget142: np. Also... regarding that nice audio player plugin we talked the other day... I was confused, it is not called "Reality" but "Nucleo_NLog_v2". Here a link to it: https://winampheritage.com/skin/nucleo-nlog-v2g/81567
<OscarL>
"Reality" was the name of an earlier skin that also looked a bit like a radio.
<poopnugget142>
oh thanks
<OscarL>
IIRK, QMMS supports those WinAmp plugins (or at least it did in the past)
<OscarL>
*IIRC
<poopnugget142>
hm alright
<OscarL>
"audacious" should too.
<poopnugget142>
I've been trying to get the music out of my cds but it has been pretty difficult thus far
bjorkintosh has joined #haiku
BrunoSpr has quit [Quit: Vision[]: Ich wurde eingeweicht!]
<OscarL>
Not sure if theres any "easy mode" CD ripping tool for Haiku. On BeOS, I just copied the .wav files from the CD to the HDD, and then converted them to .mp3 with whatever tool I had available at the time.
<poopnugget142>
I don't think I'm gonna do it on Haiku now it seems like too much effort for me
<OscarL>
You might want to look up some tutorials online, and possibly try it on whatever other OS you know better.
<OscarL>
on Windows I usually used "Exact Audio Copy", for example.
andreaallegri has joined #haiku
<OscarL>
there's a wide range of tools for CD ripping, from the extremely simple (just put the CD in, hit a button, done), but that leave you no much control over quality settings.
<OscarL>
Others give you so many choices that is easy to get lost unless you're already familiar with all the involved technical terms.
andreaallegri has left #haiku [#haiku]
* OscarL
notices that he wrote "plugins" a couple of times when he ment "WinAmp skins" instead. (getting too sleepy)
cassisian has quit [Ping timeout: 480 seconds]
<Begasus[m]>
already sleepy? :P
<Begasus[m]>
Hare worked fine here poopnugget142
<Begasus[m]>
just need to use the LAME plugin iirc
<Begasus[m]>
biab
cassisian has joined #haiku
pol has joined #haiku
mmu_man has quit [Ping timeout: 480 seconds]
<pol>
I have sometimes a problem with WiFi on this laptop. It goes away after restarting to Windows and connecting there and restarting.
<pol>
Only a little bit of data would be transferred and usually there are timeouts for websites.
<pol>
Could the app_server's "offscreen" thread be somehow related to other applications? For example it's starting to use CPU resources if I enter some websites.
cassisian has quit [Ping timeout: 480 seconds]
* Begasus[m]
has no clue
<Begasus[m]>
OscarL: so far patchset applies :)
<Begasus[m]>
only 1 file remains
<Begasus[m]>
and not that straigt forward :(
<OscarL>
wishing you success.
<Begasus[m]>
not giving up yet, already got this far :)
cassisian has joined #haiku
<Begasus[m]>
32bit build still running, why didn't you fix that? ;)
<OscarL>
next thing you know.... Begasus[m] will be updating the VirtualBox guest additions patchset, single-handlely. (I gave up twice on that one already :-D)
<Molnija>
go and find sleep
<Begasus[m]>
no need for that, so not hunting for it :P
cassisian has quit [Ping timeout: 480 seconds]
<OscarL>
Begasus[m]: when the nodejs20 build finishes (one way or another), try to see what TextSearch finds for "typedef.*\suv_pid_t" (make sure to enable "Regular expresion" option before searching).
<Begasus[m]>
remind me again in the morning ;)
<OscarL>
should help understand why it failed on 32 bits, but worked on 64.
<Begasus[m]>
at this pace it could take a while
AndrevS has joined #haiku
poopnugget142 has quit [Ping timeout: 480 seconds]
cassisian has joined #haiku
begas has quit [Quit: Vision[]: i've been blurred!]
Begasus_32 has quit [Quit: Vision[]: Gone to the dogs!]
<Begasus[m]>
closing some resources on the other one(s)
cassisian has quit [Ping timeout: 480 seconds]
cassisian has joined #haiku
jmairboeck has joined #haiku
<pol>
If you need help building I can power on some computer. I have 32-bit one too.
<kallisti5[m]>
whooooooo. Work is offering a Connectivity benefit. Going to splurge and get a Wifi 7 access point. It'll give me an excuse to look at WPA3 support
xet7 has quit [Remote host closed the connection]
<Begasus[m]>
pol if you could launch a build for nodejs20 on 32bit that would be great :)
Begasus_32 has joined #haiku
<Begasus[m]>
changed line 79 in src/node_process_object.cc
<pol>
I could do that, but first I would have to understand what I'm doing. Do I need more than 2 GB of RAM? Is it taking some long time?
<Begasus[m]>
if resources are spare it will be hard, on the "older" laptop 4xi5 at 2.49GHz and 6GB it's been on it for hours (and that was even restarting where it failed yesterday) :)
<Begasus[m]>
6GB RAM*
cassisian has quit [Remote host closed the connection]
cassisian has joined #haiku
<pol>
But you have to use 32-bit Haiku to build 32-bit apps?
<pol>
Are you using the RAM drive for a build proccess?
<Begasus[m]>
yeah, you can't build 32bit packages on 64bit
<Begasus[m]>
and not usiing RAM drive
<Begasus[m]>
ps, the machine "is" slow, it's not just this build (I mostly try to avoid doing large builds on it)
<Begasus[m]>
but hey, it's running and as long as there are no errors I'll let it go forward (maybe it's finished in the morning) :D
cassisian has quit [Remote host closed the connection]
cassisian has joined #haiku
Begasus has quit [Quit: Vision[]: i've been blurred!]
<Begasus[m]>
k, almost done for today here
<Begasus[m]>
got a bit further with nodejs24, but still errors in the build
<fancy2209[m]>
I am just already trying to do too much at once for someone who has never done OS Dev
<Habbie>
hehe, i also see that
<Habbie>
sometimes that means changing paths makes sense
<Habbie>
so remind me - the powermac status is "logs a few things on framebuffer, then hangs"
<Habbie>
the wii status is "have not tried it yet"
<Habbie>
and the qemu status?
<fancy2209[m]>
fails Intializing Modules
<fancy2209[m]>
at least that's what the docs label the Atom as
<Habbie>
right, and is that because it can't read the filesystem once it switches from relying on OFW for reading?
<fancy2209[m]>
no
<Habbie>
oh btw random note for earlier - you mentioned SDIO and USB. I have a chromebook with Haiku here where Haiku doesn't support the internal (eMMC) storage so I run from USB instead
<fancy2209[m]>
it's because it tries to lookup a page after the page array
<Habbie>
the fffffff makes me wonder if they actually are all before - before 0x0
<fancy2209[m]>
even the ones it went trough
<Habbie>
ah
<fancy2209[m]>
also these addresses line up with x86
<fancy2209[m]>
they shouldn't
<fancy2209[m]>
i think?
<fancy2209[m]>
endianess is still confusing to me
<Habbie>
line up how?
<fancy2209[m]>
like they both start with 80 something
<Habbie>
oh, they do that on x86?
<fancy2209[m]>
i think?
<fancy2209[m]>
i'm probably making issues that don't exist in my head again
<Habbie>
most of my x86 debugging has been in 16 bit memory mode
<Habbie>
so i don't know
<Habbie>
and also, most of an addressing layout is arbitrary
<Habbie>
at least beyond a certain point in the boot sequence
<Habbie>
but, i don't know much here
<Habbie>
i do like that you recognise that you sometimes see problems that turn out not to be problems
<Habbie>
but as i think i said before, worst case you investigate and (1) learn it's not a problem (2) learn a few things in that process
Nasina has quit [Ping timeout: 480 seconds]
<fancy2209[m]>
wait a second
<fancy2209[m]>
how the hell does page find the page
<fancy2209[m]>
that should fail
<fancy2209[m]>
like the Kernel is
<Habbie>
'how the hell' is where learning starts!
<Habbie>
i gotta go. good luck :)
Nasina has joined #haiku
mmu_man has quit [Ping timeout: 480 seconds]
mmu_man has joined #haiku
cassisian has quit [Remote host closed the connection]
frkazoid333 has quit [Ping timeout: 480 seconds]
cassisian has joined #haiku
Nasina has quit [Read error: Connection reset by peer]
Nasina has joined #haiku
Nasina has quit [Read error: Connection reset by peer]
Nasina has joined #haiku
Nasina has quit [Ping timeout: 480 seconds]
<waddlesplash>
fancy2209[m]: that is a 64-bit address. is this really PPC64?
<waddlesplash>
and no it didn't find the page
<waddlesplash>
"address is after end of page array": it's not a real page either way
<waddlesplash>
but the "page" command takes different kinds of addresses depending on args, I think no args and address means "vm_page structure address", which is not what the log is printing
<waddlesplash>
it's printing a physical address
<waddlesplash>
I think you need -p for that
<waddlesplash>
but if this is 32-bit PPC the 64-bit address is wrong anyway