Gamecube x86 64

leo_kendall · 2017-01-29T23:19:14+00:00

how do you setup the game cube emulator. I placed a few iso roms into the right folder and when i click on them the screen goes black then back to the mai...

Retrotrigger

nadenislamarre I Tried Another Card A GT730 This Time, The Emulators Won't Load With This Card Same Black Screen And Then Returns To The UI
Link To The Recalbox Support File Below:-
http://www.mediafire.com/file/4exewu247xmlthh/recalbox-support-20170211224013.tar.gz

nadenislamarre

Retrotrigger you cannot load the gamecube with your card, it is OpenGL version string: 2.1, version 3 is required.
leo_kendall the file glxinfo.txt is empty in your targz, i don't know why, but according to your error, i guess that's the same issue.

For each computer :
DISPLAY=:0.0 glxinfo | grep "OpenGL version string"
will give your the opengl version supported.
for dreamcast, version 3.1 is required. for gamecube/wii, it is at least 3.0 i think.

i will display it in the next release in the menu.

leo_kendall

GPU: OGL ERROR: Need OpenGL version 3.
GPU: Does your video card support OpenGL 3?
http://www.mediafire.com/file/5y9amill15hxv94/recalbox-support-20170212034731.tar.gz

iMouse

nadenislamarre I think the problem relates to the Mesa driver not properly detecting the card's OpenGL capabilities. Cards such as my AMD Radeon HD 8490 and Retrotrigger's GT 730 both support OpenGL 4.x+ and should not have any issue running Dolphin, but are being reported as only supporting OpenGL 2.1.

I found this post that possibly could explain why Mesa is detecting some AMD cards (and possibly others) as only supporting OpenGL 2.1. Could a change like this be rolled into the driver to support additional cards?

http://superuser.com/questions/964099/correct-opengl-version-on-a-notebook-with-two-amd-gpus

leo_kendall

same as my cards, in windows they support opengl and work fine with emulators. the gt730 supports 4.4 opengl.
http://www.geforce.com/hardware/desktop-gpus/geforce-gt-730/specifications

nadenislamarre

very nice found !
it's yet an other time related to patents...
however the option doesn't exist anymore in mesa3d (or i didn't search at the correct place).
i found something similar, see below.
Unfortunatly, by mistake i broke my x86_64 compilation. i'm launching a build for this night.
i'll need you for tests while i've not this bug, but it will help a lot of people, for sure.

dnl
dnl potentially-infringing-but-nobody-knows-for-sure stuff
dnl
AC_ARG_ENABLE([texture-float],
[AS_HELP_STRING([--enable-texture-float],
[enable floating-point textures and renderbuffers @<:@default=disabled@:>@])],
[enable_texture_float="$enableval"],
[enable_texture_float=no]
)
if test "x$enable_texture_float" = xyes; then
AC_MSG_WARN([Floating-point textures enabled.])
AC_MSG_WARN([Please consult docs/patents.txt with your lawyer before building Mesa.])
DEFINES="$DEFINES -DTEXTURE_FLOAT_ENABLED"
fi

iMouse

nadenislamarre Thanks for taking a look at this! I'll absolutely test when the new build is available.

morin1400

I am not able to download the beta version can you help me ?
http://batocera-linux.xorhub.com/upgrades/x86_64/beta/last/

nadenislamarre

i've done the build this night.
i've to upload. i'll do it tonight here :
http://batocera-linux.xorhub.com/upgrades/x86_64/beta/last/

the current beta file is corrupted at 6mb on the website (i've stopped the upload when i saw it was too long, i redo it tonight).

nadenislamarre

upload done.

This beta includes the mesa flag to test + the following changes if you're instested to test too :

Upgrade several emulators
Fix the autosave function
Fix randomly blinking black borders on x86*
New logo
Backup from the system menu
- backup is from internal to external, external to external or external to internal
- backup are differential : if you redo a backup, it will change only changed files
- you can use the backup as an external device
- to restore, boot on the backup, and restore on the internal device
Better video card support on x86*
Several minor fixes

sly

Hi nadenislamarre,
First, Thanks for your good work!

I have a nvidia GTX860M (and cannot activate the cpu-onboard intel gpu) in my box Alienware Alpha.

Maybe could you check my recalbox debug file? : https://1fichier.com/?ypn1iwobfo

If you can have a look, an easy tweak is possible maybe by you. It would be awesome if this gpu could be used for Wii/Gamecube/PSP emulation.

Thanks

Regards,

Puritan007

sly hi sly, I've just grabbed an Alienware alpha used for cheap and I'm having a horrible time getting controlers to work in windows so I grabbed batocera on a usb stick but it won't boot so I wondered what settings you changed in bios to allow the thing to boot? Or do you use a thumb drive? Thank you.

nadenislamarre

can you try the above beta to check if that's better please ?

sly

Actually I tried, the last one (v5.3.0 2017/02/14 07:43)
It's still very laggy on the UI sadly, and then I quickly uploaded the recalbox-support.sh output :-)

But I got this output message for information: "Unable to init SDL: No available video device"

/recalbox/scripts/recalbox-support.sh

Unable to init SDL: No available video device
/recalbox/share/saves/recalbox-support-20170214211630.tar.gz

you will probably will have more details in this gz file.

Feel free to ask me any command output or tests in the coming hours

sly

In my dmesg I have:

[ 6.323008] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input8
[ 7.106745] [TTM] Zone kernel: Available graphics memory: 4059194 kiB
[ 7.106746] [TTM] Zone dma32: Available graphics memory: 2097152 kiB
[ 7.106746] [TTM] Initializing pool allocator
[ 7.106751] [TTM] Initializing DMA pool allocator
[ 7.106777] nouveau 0000:01:00.0: DRM: VRAM: 2048 MiB
[ 7.106778] nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
[ 7.106780] nouveau 0000:01:00.0: DRM: TMDS table version 2.0
[ 7.106782] nouveau 0000:01:00.0: DRM: DCB version 4.0
[ 7.106783] nouveau 0000:01:00.0: DRM: DCB outp 01: 02000f62 00020010
[ 7.106784] nouveau 0000:01:00.0: DRM: DCB conn 00: 00001061
[ 7.106789] nouveau 0000:01:00.0: DRM: BIOS FP mode: 1024x768 (65000kHz pixel clock)
[ 7.122802] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 7.122802] [drm] Driver supports precise vblank timestamp query.
[ 7.245780] nouveau 0000:01:00.0: DRM: MM: using COPY for buffer copies
[ 7.443888] nouveau 0000:01:00.0: DRM: allocated 1920x1080 fb: 0x60000, bo ffffa07e53bbc000
[ 7.443955] fbcon: nouveaufb (fb0) is primary device
[ 7.924620] Console: switching to colour frame buffer device 240x67
[ 7.925913] nouveau 0000:01:00.0: fb0: nouveaufb frame buffer device
[ 7.946657] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 0

Maybe this can help to understand what is happening

nadenislamarre

ok, in fact, i didn't understood that you interface was slow.
in your case, the nvidia drivers won't load with the message : Unknown chipset: NV117
you're not the first one with this case. For the moment i don't know what this error mean.

sly

addition:
Feb 14 21:06:01 RECALBOX user.info kernel: [ 5.730401] fb: switching to nouveaufb from EFI VGA
Feb 14 21:06:01 RECALBOX user.info kernel: [ 5.730868] nouveau 0000:01:00.0: NVIDIA GM107 (117120a2)
Feb 14 21:06:01 RECALBOX user.info kernel: [ 5.803756] nouveau 0000:01:00.0: bios: version 82.07.32.40.78
Feb 14 21:06:01 RECALBOX user.info kernel: [ 5.805148] nouveau 0000:01:00.0: fb: 2048 MiB GDDR5

sly

Ok thank you.
I will search and update if any findings.

I'm confident In the future an explanation and solution will be found.

Keep up your good work.

Regards,

sly

Apparently only the proprietary Nvidia drivers can drive such "recent" nvidia cards.

Is there a way to Install the proprietary Nvidia drivers on your release ?

I know you cannot add it to batocera img, GPL Violation.

nadenislamarre

ok, i got a talk with the nouveau linux driver,
so, good news. i've some new changes to do, but it should work at the end,
let me time to present you a new buid.

so to resume the talk :

<imirkin> looks like it did fall back to modesetting as i expected
imirkin> [1044093.486] (EE) AIGLX: reverting to software rendering
<imirkin> which makes sense... glamor didn't get initialized for some reason
<imirkin> i don't suppose you built xorg without glamor for some reason?
imirkin> glamor is the generic accel layer that implements EXA using GL
imirkin> also make sure that mesa is compiled with egl support
<imirkin> (and gbm as well)
it looks like glamor is not enabled because i've not enabled BR2_PACKAGE_LIBEPOXY
imirkin> ok... libepoxy is a tiny lib
imirkin> which makes writing GL code slightly more palatable
<susan34> so, i will add BR2_PACKAGE_LIBEPOXY to enable glamor, and that should work. i'm building it and let the people tries. thanks a lot.
<imirkin> double-check your mesa build config
<imirkin> to ensure that egl and gbm are enabled
<imirkin> coz glamor won't work without that

nadenislamarre

sly: you cannot install nvidia drivers easyly. it requires several things like some dev tools.

« Previous Page Next Page »