search

phabrics / nme

Next-generation Machine Emulator: This is the OFFICIAL repo for the new tme and will be updated here.
http://phabrics.com
Other
9 stars 1 forks source link

Problem with NME and disks on SunOS #3

Open asmithrsa opened 1 year ago

asmithrsa commented 1 year ago

I am opening this up as a seperate issue since the other issue was resolved. I have been trying to get my disk image backup of my sun server but every time TME interacts with the disk the GTK window completely crashes. Additionally I tried to do a fresh install of SunOS and when you get to the step where the disk is named, GTK also completely crashes. I tried making a couple of changes to the config file such as changing from bwtwo to cgthree and using the "SCSI-3" VME board instead of the "SCSI-2" board but nothing seemed to fix the issue. I also tried changing the disk type to tme-scsi-1 even though I know it should be ACB-4000 but that didn't change anything. I am using the newest version of GTK3 on a Lubuntu VM.

asmithrsa commented 1 year ago

I also tried a fresh install of SunOS but eventually GTK crashes during the disk formatting process.

phabrics commented 1 year ago

Thank you for opening this and making this into a formal issue. It does seem to be more of a GTK issue at this point. There are a couple of options:

  1. Switch to a different GUI type - either sdl (another window) or rfb (vnc server). Simply replace the word on the display line from gtk to one of those. A vnc client would obviously be required to access the vnc display.
  2. Use the console interface. This is obviously less desirable but might tell us if it's crashing without a GUI. The console line can use ptmx pseudoterminal device as documented in the Wiki or set up a device pair yourself. There should be the sample lines in the configuration file to uncomment as needed.
  3. If you're feeling adventurous, you can try the multi-threaded (preemptive multithreading) version. Simply configure with the --enable-threads option. It is still considered experimental and is slower than the single-threaded (cooperative multithreading) version. Otherwise, it should work the same way.
asmithrsa commented 1 year ago

Ok I tried using sdl instead of GTK and the window freezes at the exact same point when the filesystems are being checked. So it seems it's a problem with the emulator.

asmithrsa commented 1 year ago

I also tried configure it with enable-threads. It does get past the checking filesystems but when it gets to the login after some time it says "Spurious level 6 interrupt" and then "panic" it also said "Spurious level 2 interrupt" while it was rebooting. It also is definitely running really slowly. For the short time I was able to try to login, it was not able to read keyboard presses properly. One press would put like 8 of the same key. After rebooting a couple of times it is now frozen on checking filesystems.

phabrics commented 1 year ago

Thank you for doing this. It is a legitimate bug that needs to be fixed. I have assigned it to myself and will begin debugging it ASAP. Hopefully, I can figure out what the problem is. I'll update the issue as soon as I have something.

phabrics commented 1 year ago

The SDL issue with the keyboard is my fault. I assume you are using the head of the github main branch. Unfortunately, I broke it a few days ago with a change I made to decouple the SDL host completely from GTK dependency. It is a work in progress, but I would avoid SDL for now in the main branch.

asmithrsa commented 1 year ago

Hi. I was not using the main branch. I was using the latest release on OSDN so it must be a different issue.