Not running N64 ROMs?
#11
How did you got it working?

Aside of this, dmesg doesn't look to contain wrong things.
For daemon, I will take a look when back home, it is a bit big to run thru with the phone :S
Reply
#12
(11-05-2019, 05:29 PM)Porcinus Wrote: How did you got it working?

Aside of this, dmesg doesn't look to contain wrong things.
For daemon, I will take a look when back home, it is a bit big to run thru with the phone :S

I just meant that I was able to get the WiFi working so that I could attach those files here. Thanks for checking!
Reply
#13
Ok,
Your daemon.log file contain too much parasite information...
Here is a now procedure to test, this will not solve the problem but can help a lot:
Using Putty, connect thru SSH and run following command to clean daemon.log contain : 'sudo cat /dev/null > /var/log/daemon.log'
Once done, try to start a non working N64 game, wait 10sec once the screen is black then using WinSCP, recover /var/log/daemon.log and post its contain here please.
Reply
#14
(11-08-2019, 02:52 AM)Porcinus Wrote: Ok,
Your daemon.log file contain too much parasite information...
Here is a now procedure to test, this will not solve the problem but can help a lot:
Using Putty, connect thru SSH and run following command to clean daemon.log contain : 'sudo cat /dev/null > /var/log/daemon.log'
Once done, try to start a non working N64 game, wait 10sec once the screen is black then using WinSCP, recover /var/log/daemon.log and post its contain here please.

I get '-bash: /var/log/daemon.log: Permission denied' when I try to run that command Sad

EDIT: Really not sure what I did, but N64 roms work now! Super Smash and Super Mario are both running great! Obviously there's a little bit of lag but for the most part it's doable. Thanks for all the help!
Reply
#15
Ho, with 'sudo' before the command, it shouldn't happen :/
Another way to try : sudo sh -c 'cat /dev/null > /var/log/daemon.log'

If it still not work, just start a non working N64 game, wait 10sec once the screen is black then, recover /var/log/daemon.log and post it via the way you used the first time.
It will still be a big file but this time, I will know where to look Smile
Reply
#16
I have retake a look at the whole post and there is a missing question, did you try to change the default emulator (via pressing A will the game is starting)?
From what I remember, my is set to the one with "auto".
Reply
#17
(11-13-2019, 05:34 PM)Porcinus Wrote: I have retake a look at the whole post and there is a missing question, did you try to change the default emulator (via pressing A will the game is starting)?
From what I remember, my is set to the one with "auto".

I tried all of the emulators available and it wasn't working for a long time. Now it works, not sure why.
Reply
#18
That weird but well, if it work, it work Smile
Reply
#19
Hey, sorry to hijack this post but I am having a similar problem and I'm trying to get any info that can help me figure this out.

I was initially able to see an N64 rom play on the screen perfectly fine. Then, while it was on, I plugged it into an HDMI and it seemed like it detected it but did not send the image to the TV so I shut it down and tried turning it back on while being plugged into the TV. This time the retropie menu was mirrored both on the screen and the TV. When I selected the N64 emulator the entire image and sound were now present only on the TV (the screen remained black for this).

But now, every time I run the emulator it defaults to sending the image to the HDMI. I can plug it into the TV while the screen is black and I'll see and hear the rom playing on the TV. I hadn't changed the emulator options prior to this, so unfortunately I don't know if there were different values prior to this.

These are the options I see enabled now:

System: n64
Emulator: mupen64plus-auto
Video mode: 1024x768 @ 60 Hz 4:3, clock: 65MHz progressive
ROM: Legend of Zelda, The Ocarina of Time


After entering the emulator I see an error in the daemon.log saying that there was a DMA channel collision:

retropie fbcpFilledNoSleep[380]: DMA channel collision! DMA channel 1 was expected to be assigned to our peripheral 7, but something else has assigned it to peripheral 17!

From my very limited understanding, I think it initially tried to use the screen through SPI (peripheral 7) but something else assigned it to HDMI (peripheral 17).

Is there an easy way to revert whatever configuration was assigned when I plugged it into the TV?

Attached is the daemon.log after the emulator is started. (Edit: might not have permissions to attach files yet, here's the file: https://filebin.net/tj4z5diw0ua1kvtc)

PS: I have the latest CM3 image installed (Freeplay_CM3_19110701) with the FastNoSleepFilled LCD driver selected.

Thanks in advance!
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)