<rennj>
VMware is working very closely with its OEM partners. All major OEM server vendors today support options such as an M.2, BOSS, NVMe, SATA with a high-endurance boot device in their current generation of servers. In addition, OEM server vendors have agreed to stop supporting USB/SD card-based boot device with servers having the newer generation of CPU platforms such as Sapphire Rapids and Genoa.
<jessicah>
augiedoggie_: ooh, try the second one first, I'm pretty sure the first one was incorrect
<augiedoggie_>
i grabbed the last one from the trac ticket
<augiedoggie_>
is that ok?
<jessicah>
yep
<augiedoggie_>
gimme a minute to reboot
<rennj>
have agreed to stop supporting USB/SD card-based boot device is as the kids say problematic
<rennj>
at-least for server motherboards
<jessicah>
augiedoggie_: do you happen to have one disk with MBR partition style rather than GPT?
<jessicah>
I'm pretty sure that's the issue with andreasdr[m]'s system
<Not-8690>
[haikuports/haikuports] Begasus d304e84 - ktexteditor, revbump for new libgit2 (#6984)
woffs has joined #haiku
eroux_ has quit []
eroux has joined #haiku
HaikuUser has joined #haiku
HaikuUser has quit [Read error: Connection reset by peer]
freddietilley has joined #haiku
BrunoSpr has joined #haiku
BrunoSpr has quit []
eroux has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
eroux has joined #haiku
HaikuUser has joined #haiku
<HaikuUser>
Hi am working on a video review for Haiku i3 with 4Gb of RAM, 128Gb SSD but the CPU particularly CPU1 seems to be hitting 100% all the time. Any ideas? I'm running Haiku Beta 3 with the latest updates
<ermo[m]>
does it happen on nightly?
BrunoSpr has joined #haiku
BrunoSpr has quit []
<HaikuUser>
I'm using stable at the moment but can try the nightly build
<HaikuUser>
Downloading hrev56168 now and will give it a try
HaikuUser has quit [Quit: Vision[]: i've been blurred!]
<ermo[m]>
fwiw, I'm on nightly with a Q9400+HD6450+128 GB SSD and don't see the 100% core thing.
<ermo[m]>
and 4GB of RAM as it happens
<ermo[m]>
it's quite the comfortable spec
<rennj>
i3 could be anything..old or new..
<rennj>
i had i5 intel crapship before this 2015 amd laptop
<rennj>
i5 was 2 cores/4 threads..now i got 4cores/4threads...
<rennj>
soon 8cores/16thread ryzen apu...
<rennj>
Core™ i3-530 Processor 2010
<rennj>
yeah that junk...
<itanium686>
i have a 4 core ryzen 8GB ram 256 ssd and amd gfx in a AIO hp everyting work on beta 3 even the sound
<rennj>
nice...
<rennj>
my 4core/4thread amd a10 apu but i have 16GB of ram and 500GB ssd...2015 tech
<rennj>
hp craptop pavilion was $400..i added the ram and ssd and removed the gen1 m.2 wifi/bluetooth card
<itanium686>
okey always nice with more ram beta 3 seams to leak memory
<rennj>
7 year old laptop still rocking
<itanium686>
thats a good thing with haiku its fast on older computers
<itanium686>
too
<rennj>
22TB to ssd ...and it and laptop have 6years poweron hours
<rennj>
nah i run linux and vmware-vmx
<rennj>
haiku would run this craptop into ground
<rennj>
i would never run haiku on baremetal.
MajorBiscuit has joined #haiku
<rennj>
vm only
<itanium686>
okey i run haiku direct on my compuer
<jason123santa>
I have haiku on my desktop
<rennj>
yeah how is the temp of cpu/fans..how fast is ther wifi/ethernet..what is the disk access speeds..how long of uptime
HaikuUser has joined #haiku
<rennj>
haiku will live in a vm..cause it does not have superior drivers for the hardware
HaikuUser has quit []
<itanium686>
temps is good fans work good wifi dont work run with cabel ,uptime now is not so loong its leak memory so need reboot at the end of the day
<Begasus>
nah, no YT for me, at least not a lot (this laptop can't handle it mostly) :)
<rennj>
bah pasteboard
<rennj>
they lost their db
<rennj>
weak sauce
<Begasus>
it's like with us breeders, there was a database going back a LONG way so you could check the blood line for a dog, wen't offline a few years ago :/
<rennj>
i test some stuff on these vm..freebsd,openbsd,solaris,linux
<rennj>
a school in Bath, Michigan was rigged with explosives in a brutal act that stunned the town
tuaris has joined #haiku
<Begasus>
nielx[m], is rust not that much optimized for x86_64? building cargo-c in x86_gcc2 takes a bit over 2 hours here, on x86_64 it takes a few hours more ...
itanium686 has joined #haiku
itanium686 has quit [Quit: Vision[]: i've been blurred!]
<ermo[m]>
Begasus: the more optimisations the compiler looks for, the longer it generally takes to compile. Does the x86_64 version of rust using a later gcc version enable LTO by chance?
<ermo[m]>
s/rust/cargo-c/
<ermo[m]>
I'd wager that by comparison, gcc-2 isn't very advanced vs. gcc-<whatever version Haiku uses>...
<ermo[m]>
whether or not that translates to the rust compiler is ofc a different matter
itanium686 has joined #haiku
eroux has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
matt1 has joined #haiku
Begasus has quit [Ping timeout: 480 seconds]
Begasus_64 has quit [Ping timeout: 480 seconds]
x10z has joined #haiku
x10z has quit []
<matt1>
10 PRINT "HELLO HAIKU"
<matt1>
HELLO HAIKU
<matt1>
;0)
<matt1>
ops ...
<matt1>
after 10 PRINT ... put a RUN ...
<matt1>
;0)
<ermo[m]>
o_O
<matt1>
hi, ermo[m]
freddietilley has quit [Quit: WeeChat 3.5]
x10z has joined #haiku
talos has joined #haiku
Begasus has joined #haiku
<matt1>
hi Begasus
matt1 has left #haiku [#haiku]
xet7 has quit [Remote host closed the connection]
itanium686 has quit [Quit: Vision[]: i've been blurred!]
itanium686 has joined #haiku
kescher has quit [Quit: Bye]
kescher has joined #haiku
matt1 has joined #haiku
mmu_man has quit [Ping timeout: 480 seconds]
MajorBiscuit has quit [Ping timeout: 480 seconds]
<matt1>
is there a tutorial to install Haiku on usb pen in uefi mode ?
matt1 has left #haiku [#haiku]
KapiX has joined #haiku
ClaudioM has joined #haiku
mmu_man has joined #haiku
begasus_ has joined #haiku
<waddlesplash>
jason123santa: can you confirm that your system that currently KDLs boots if you blacklist the "nvidia" graphics driver
<jason123santa>
> jason123santa: can you confirm that your system that currently KDLs boots if you blacklist the "nvidia" graphics driver
<jason123santa>
How do I backlist it?
<jason123santa>
though I am not home to test anything
<waddlesplash>
using the bootloader options
<jason123santa>
Where would I find those options?
<waddlesplash>
go into bootloader -> "Select safe mode options" -> "Disable system components" -> go to path "add-ons/kernel/drivers/bin", find "nvidia" and select it, "Esc" to go all the way back out and "Continue booting"
<waddlesplash>
get to the bootloader by holding SHIFT before the bootsplash appears
Begasus has quit [Ping timeout: 480 seconds]
<jason123santa>
I will try when I get home
<jason123santa>
if I disable the graphics then I will out get any output though
<nekobot>
[haiku/haiku] 5797a8dec595 - graphics/nvidia: Fix another instance of missing READ/WRITE protection flags.
x10z has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
vdamewood has quit [Quit: Life beckons.]
<mbrumbelow[m]>
waddlesplash: Are the Wi-Fi changes going to all be in hrev56168? It looks like one other change did not get into the latest image.
<waddlesplash>
all the new OpenBSD stuff is introduced in hrev56168, yes.
<waddlesplash>
images will be a bit useless for testing this in the near future however
<waddlesplash>
because they won't contain the needed firmware, we need to sync packages for that
<waddlesplash>
you'll have to upgrade the intel_wifi_firmwares+wpa_supplicant packages on an existing install to test the new wifi stuff
x10z has joined #haiku
matt1 has joined #haiku
matt1 has quit [Quit: matt1]
m199 has joined #haiku
<mbrumbelow[m]>
Is there a timeframe you are thinking of to make those available? I would like to begin testing on my physical hardware asap. I have a few NUC’s and laptops that are Wi-Fi 6.
<waddlesplash>
patience, young grasshopper...
<waddlesplash>
PulkoMandy and I are iterating through testing the driver on his hardware already
<waddlesplash>
the fix in hrev56169 came from that, and it looks like we've discovered a bug in the driver itself and a potential workaround
HaikuUser has joined #haiku
HaikuUser has quit []
B2IA has quit [Quit: Vision[]: i've been blurred!]
cebulon has joined #haiku
B2IA has joined #haiku
B2IA has quit [Ping timeout: 480 seconds]
KapiX has quit [Quit: KapiX]
mmu_man has quit [Ping timeout: 480 seconds]
ClaudioM has quit [Quit: leaving]
Anarchos has joined #haiku
<jessicah>
andreasdr[m]: don't forget to test haiku loader for me :)
<jessicah>
see attached file in your ticket
<Anarchos>
jessicah i encountered funny things while playing with haiku_loader
<Anarchos>
a striking 'boot loader death land'...
<jessicah>
:p
<Anarchos>
never saw this one before
<jessicah>
yes, I've seen that once or twice
<Anarchos>
but i was doing nasty things : repairing pxe boot ...
<jessicah>
it's extremely rare
* Anarchos
is very proud to be in the activity report for that
<Anarchos>
jessicah yes, i built the haiku_loader.pxe_ia32 with debug symbols, and bam, boot loader death land shines in qemu...
Gaspare has joined #haiku
<jessicah>
possibly size was too big or something like that
<Anarchos>
if i have time i will do it on bare metal and take a photo for a blog entry :)
<jessicah>
it's in the first stage loader I think, probably in mbr.S or something
<jessicah>
it's been a while since I've played with that code
<PulkoMandy>
I think it's later than that, it's the equivalent of KDL for the bootloader, if there is an unhandled fault or the like
<PulkoMandy>
the code for the bootloader is simple enough that this rarely happens
<Anarchos>
anyway, i was able to install haiku on a machine through a pxe boot, was really fun
<Anarchos>
though i could do it for 32bits but still unable for 64 bits
<waddlesplash>
Vidrep_64: looks like the fw task may have gotten stuck. I'll see if I can find anything here, otherwise I may need you to poke around in KDL
<jason123santa>
waddlesplash, it boots up fine with the driver backlisted
<Vidrep_64>
I have another PC with WiFi. May as well update and see what happens with that one too.
<jason123santa>
the kernel error is related to the nvidia graphics
<Vidrep_64>
atheroswifi is working after updating. That's good news
<waddlesplash>
idualwifi should be the only thing affected
<waddlesplash>
jason123santa: good. so tonight's update should fix it then, I made another change
Vidrep_64 has quit [Quit: Vision[]: i've been blurred!]
<jason123santa>
Yeah I added a screenshot if you want to see what the kernel error is
<jason123santa>
> idualwifi should be the only thing affected
<jason123santa>
> jason123santa: good. so tonight's update should fix it then, I made another change