@The Solutor. This is very strange you don't see DN, the log shows DN started and output the lines. I bet something is wrong with the timer interrupts/wake up or so. Does F12 work and bring up OSD?
I added new diagnostic logs in the new release bundle.
gsos wrote on Today, 15:41:@The Solutor. This is very strange you don't see DN, the log shows DN started and output the lines.
And not just DN, MC/NC/VC all the same they look started but they aren't visible
I bet something is wrong with the timer interrupts/wake up or so. Does F12 work and bring up OSD?
Yeah I thought that could be the secondary monitor (say output redirected there with an unsupported resolution) so I tried with a single monitor connected, and even swapped them.
No change.
About f12 I think no/not visible, but I'm not sure, I'll recheck and update this message, ASAP
EDIT
I confirm no F12 popoup
superfury wrote on Today, 13:50:Apparently there's no ISO image anymore on the releases to use? I only see USB stuff there and raw files?
I added a .iso again!
@gsos
New round, using the updated image, new klog (whit hopefully useful info at the end)
VME enabled
SYSCALL enabled
[96mRetroOS Rust Kernel[0m
Paging: PAE (64-bit entries)
CPU supports Long Mode (64-bit)
Long mode tables set up
Identity mapping removed
NX (No-Execute) protection enabled
PAT: Write-Combining slot enabled (framebuffer)
Hardening kernel:
.text: 0xc0b00000-0xc0bde000 (pages 789248-789470): R-X
.rodata: 0xc0bde000-0xc0c07000 (pages 789470-789511): R-- NX
.data: 0xc0c07000-0xc0c84000 (pages 789511-789636): RW- NX
Kernel hardening complete
kernel_phys: 0x100000
Physical memory: 0x8ca0 pages free
Memory regions: 24
Available: 0x0 - 0x8f000
Available: 0x90000 - 0xa0000
Available: 0x100000 - 0xa200000
Available: 0xa20a000 - 0xb000000
Available: 0xb020000 - 0x4968c000
Available: 0x4ac0c000 - 0x5e000000
Available: 0x100000000 - 0x35f340000
fbcon: boot LFB 1440x900 pitch=5888 bpp=32 R16/8 G8/8 B0/8 addr=0xa0000000
fbcon: format accepted, native_blit=true
HPET: no ACPI table found; using timer fallback
IRQ: PIC
Clock: stable TSC 3593071261 Hz
IRQ: PIT
xHCI: probing 01:00.0
xHCI: scratchpad buffers allocated: 31
xHCI: running (slots=127 ports=22) at 01:00.0
xHCI: no keyboard found
xHCI: no mouse found
xHCI: probing 0a:00.3
xHCI: scratchpad buffers allocated: 2
xHCI: running (slots=64 ports=8) at 0a:00.3
xHCI: port 2 speed 1 class 0 keyboard=true mouse=false
xHCI: port 3 speed 1 class 224 keyboard=false mouse=false
xHCI: keyboard ready (slot 1 port 2 ep 1 mps 😎 at 0a:00.3
xHCI: no mouse found
xHCI: probing 0a:00.4
xHCI: scratchpad buffers allocated: 2
xHCI: running (slots=64 ports=2) at 0a:00.4
xHCI: no keyboard found
xHCI: no mouse found
IRQ: keyboard
IRQ: mouse probe
IRQ: mouse unavailable
Interrupts initialized
Stack guards at 0xc0c07000 (kernel) 0xc0c7f000 (arch)
[92mHello from Rust kernel![0m
SELFTEST PIT counting=1 samples=01FE 02F8 03E4 004A 0260 0478 01E4 03FC
SELFTEST PIC master IRR(seen)=00000001 IMR=11111000 IRQ0_pending=1 IRQ0_masked=0
SELFTEST APIC none (pure-PIC machine, INTR direct)
SELFTEST CPU vendor=AuthenticAMD family=15 tsc_deadline=0 x2apic_cap=0 invtsc=1
SELFTEST CPUID.15H unavailable (maxleaf=0xd)
SELFTEST CPUID.16H unavailable
SELFTEST IRQ0 delivery count=0 IF=1 PIC IRR=00 ISR=00 IMR=F8
Ring1 entered, paging + interrupts + syscall setup complete
Heap base: 0xc0c84000
RetroOS kernel retroos-1-gfb6651a0
Storage: nvme0n1 (244198 MB)
Storage: ahci0p0 (476940 MB)
Block devices initialized
hda: amp pin gain=0x0 dac gain=0x4a
hda: state pinctl=0x40 eapd=0x0 pinamp=0x0 dacamp=0x4a pinpwr=0x0 dacpwr=0x0 pinsel=0x0
hda: selected 0a:00.6 codec=0x14f15098 pin=nid31 dac=nid16
hda: path len=2 score=5016 nodes=1f>10>00>00>00>00 conn=0,0,0,0,0
Platform: host=Metal vga_passthrough=false firmware=Substitute audio=EmulatedHda hostfs=false debug=Debugcon
[91mDisk writes: PERSISTENT[0m — pass `ram-overlay` to protect the disk
Threading initialized
Filesystems: scanning partition tables...
Filesystems: 5 partition(s) found
Filesystems: probing ext4/FAT volumes...
Filesystems: 2 supported partition(s)
Multiboot ext4 (32 MB, volatile RAM) → /
FAT C: (330 MB) from disk → /home/retroos/
C: backing volume 1 (nvme0n1) directory /
boot runtime → C:\RETROOS (read-only)
C:\CONFIG: disk files before boot defaults; C:\TEMP: RAM
DOS E: → /disk1 (FAT partition, 199 MB, read-only)
DOS C: maps to /home/retroos/
Loading kernel symbols (244956 bytes)
Loaded 2773 function symbols
ISA PnP: no Sound Blaster found; trying legacy DSP discovery
Audio: EmulatedHda (SB_AUDIO=native)
Loading General MIDI bank...
midi: no ULTRASND under the C: root — General MIDI silent
General MIDI bank load complete
hda: stream RUN sdctl=0x00100002 cbl=32768 lvi=63 fmt=0x0011 lpib=0
DOS: installing substitute BIOS (vga_passthrough=false)
UMA: EMS frame at D0000, UMB 64KB free
Welcome to RetroOS! F12 opens the host monitor.
Starting home/retroos/CONFIG/NC/NC.EXE...
Boot log saved to C:\KLOG.TXT
boot launch: releasing console
boot launch: console released
boot launch: loading home/retroos/CONFIG/NC/NC.EXE
boot launch: file loaded (3772 bytes)
boot launch: constructing program thread
[gus] ULTRASND base=240 irq=5 dma=3
[mpu] MPU-401 at 330
boot launch: program thread ready (tid=1)
boot launch: display adopted
event_loop entered, tid=1
[gus] ULTRASND base=240 irq=5 dma=3
[mpu] MPU-401 at 330
The Norton Commander Versione 5.0,
Copyright (C) 1986 - 1995 della Symantec Corporation.
CLOCK: no event-loop clock sample for 250 ms (8192 loop passes)
IRQ0 delivery stalled: count=0 IF=1 PIC IRR=01 ISR=00 IMR=F8
Okay yes, something on these systems is different. PIC has a pending irq0 (IRR=1) and IF=1 and irq0 is unmasked (IMR=F8 irqs 0,1,2 are open) yet it's not delivered count=0. So apparently PIC is not hooked up to the CPU in the default config. I'll investigate tonight.
gsos wrote on Today, 17:28:Okay yes, something on these systems is different. PIC has a pending irq0 (IRR=1) and IF=1 and irq0 is unmasked (IMR=F8 irqs 0,1,2 are open) yet it's not delivered count=0. So apparently PIC is not hooked up to the CPU in the default config. I'll investigate tonight.
In the meantime i noticed that you implemented my suggestion of hybrid UEFI/BIOS boot, so I tried to boot via CSMWrap.
Using the native bios option I reach the filemanager screen !! (Norton Commander is configured ATM),
Using the VBE option, it's the same as UEFI.
I can't say a lot more because, in CSMwrap case I have no working keyboard , just like on the N100 machine.
Whatever I wasn't able to boot the system a single time via CSMWrap with older releases, the ones that worked in UEFI mode.