search

klange / toaruos

A completely-from-scratch hobby operating system: bootloader, kernel, drivers, C library, and userspace including a composited graphical UI, dynamic linker, syntax-highlighting text editor, network stack, etc.
https://toaruos.org/
University of Illinois/NCSA Open Source License
6.03k stars 475 forks source link

Can't get the package list #219

Open BlackPhrase opened 2 years ago

BlackPhrase commented 2 years ago

Due to updates in the networking layer, it is currently impossible to get the package list with the msk app (and using the Package Manager as a result) There is an issue with the 'gethostbyname' function, so this should be related to #217 and to #218

toaru_pacman2

toaru_pacman

klange commented 2 years ago

Can you please also post the output of uname -a? Can you try the latest CI artifact build?

BlackPhrase commented 2 years ago

Output from uname -a? You mean version number? That was the latest release on GitHub: https://github.com/klange/toaruos/releases/tag/v1.99.8 The same goes for the previous two releases and, I guess, for all before them (last time I saw them working on 1.10.x) Tested with the latest release from CI - all the remotes timed out, even the local one

klange commented 2 years ago

Can you post the output of nslookup toaruos.org?

klange commented 2 years ago

I just noticed your screenshots are weirdly stretched. Scaling in QEMU can completely destroy runtime performance which may have an impact on network setup or connection. Can you provide your full QEMU command line and qemu-system-x86_64 --version?

I really ought to set up some issue templates to request all of this information from the start on bug reports...

BlackPhrase commented 2 years ago

Can you post the output of nslookup toaruos.org?

toaru-nslookup

I just noticed your screenshots are weirdly stretched. Scaling in QEMU can completely destroy runtime performance which may have an impact on network setup or connection. Can you provide your full QEMU command line and qemu-system-x86_64 --version?

By default, Toaru shows up a display that is ~1.5x bigger than mine so I either need to Zoom Out or open it in Fullscreen mode QEMU emulator version 4.2.0 (v4.2.0-11797-g2890edc853-dirty) And the command line is the one recommended to launch the OS with There was an issue with the kvm arg, so I disabled it, the rest is untouched The same had been done on 1.10.x but things were working fine back then

klange commented 2 years ago

By default, Toaru shows up a display that is ~1.5x bigger than mine so I either need to Zoom Out or open it in Fullscreen mode

I suggest using the set-resolution command to change the screen size to something that fits your display better and then making sure the QEMU window is not doing any scaling. Try sudo set-resolution 1024 768 for example. QEMU's standard display device supports arbitrary resolutions, so whatever fits your screen should work.

There was an issue with the kvm arg, so I disabled it, the rest is untouched

Please note if you're running under TCG (qemu's software backend) I do not support this and it's probably unbearably slow - doubly so if you're on a system with a display resolution under 1440x900 - and if you don't have a host environment with KVM I strongly recommend trying a different virtual machine until you find something with hardware virtualization.

toaru-nslookup

It looks like DNS is working, which means the network stack is working in general but you can't establish a TCP connection to any of my servers. Can you try to fetch various other HTTP resources from other places? Can you tell me a bit about where you are in the world, how you're getting your Internet service, etc.?

BlackPhrase commented 2 years ago

I suggest using the set-resolution command to change the screen size to something that fits your display better and then making sure the QEMU window is not doing any scaling. Try sudo set-resolution 1024 768 for example. QEMU's standard display device supports arbitrary resolutions, so whatever fits your screen should work.

Thanks

Please note if you're running under TCG (qemu's software backend) I do not support this and it's probably unbearably slow - doubly so if you're on a system with a display resolution under 1440x900 - and if you don't have a host environment with KVM I strongly recommend trying a different virtual machine until you find something with hardware virtualization.

Yes, this is the main thing that currently kills the performance, disabled KVM And yes, it's a bit slow but fine for now KVM is a Linux-only thing and I'm testing on Windows, though, there is a KVM for Windows and that is a KVM ported by Google: https://github.com/google/Android-emulator-hypervisor-driver-for-amd-processors And even a special version of QEMU that supports it: https://github.com/qemu-gvm/qemu-gvm I do have a Linux distro installed in dual-boot and probably should try to test it there in my spare time

It looks like DNS is working, which means the network stack is working in general but you can't establish a TCP connection to any of my servers. Can you try to fetch various other HTTP resources from other places? Can you tell me a bit about where you are in the world, how you're getting your Internet service, etc.?

I can tell that 1.10 was working fine on this exact machine with exactly the same QEMU command line And I'm connected via the router, might be worth mentioning But, as I said, previously everything was working fine

klange commented 2 years ago

I'm testing on Windows

Then you should really try VirtualBox or VMware Workstation. QEMU can also use haxm on Windows.

BlackPhrase commented 2 years ago

HAXM is only for Intel processors

klange commented 2 years ago

Then you really should try VirtualBox or VMware Workstation - the experience is actually better with both of them than in QEMU, as they offer automatic guest display sizing which we have support for in ToaruOS. I even finally got around to writing a driver for the audio chipset VMware Workstation emulates. Both are a bit odd to set up with their wizard GUIs, but either way you should be able to get hardware virtualization. Sadly, I can't recommend the other option of trying to run on bare metal if you have an AMD system since it's highly unlikely you have a compatible network card onboard so that won't solve anything (unless you happen to have an e1000e PCIe card installed...)

I can tell that 1.10 was working fine on this exact machine with exactly the same QEMU command line

Hm, 1.10 was a very different network stack on a very different kernel. It also didn't support timing out connections... if it's down to initial TCP handshake, that could be it. I can try adding some options to configure connect timeouts.