[4.1-Unstable] Bug reports
-
I have done all Update to 4.1, then i pressed one more time the "Check Update" button and it installs another one, after the Update was done, i got an Kernel Panic Error on boot
Is this issue known?
-
@sevenx I guess your updates type was set back to stable. Can you mount your sd card on a linux and check ?
-
Hi all, I'm testing the last 4.1 unstable on rpi3 and I can't solve the 'retroarch square' bug.
I tried to remove the ~/configs/retroarch/retroarchcustom.cfg and Recalbox generates it again, I restarted the system but I have the same problem. I know other people solve this bug, could you please tel me the extact procedure? Thanks all and sorry for my english -
@jthemad If your're using custom configs, you should manually add the required line. And your english is just fine
-
@Substring hi! Thanks for your answer..
I don't understand what do you mean with 'add the line manually'.. I deleted config file and Recalbox generated a new one, where am I wrong? What do you mean with custum config? Another issue I found: with Xbox 360 controller wired, I can't exit to main menu (hotkey + start). I tried to configure again the keys but same problem. With another pad all ok. I was using the same Xbox controller with 4.0.2 and all was working fine..
anyway great work with this release, waiting for stable release..
thank you -
@jthemad All apologies, what i said doesn't work in the case of an upgrade from 4.0
So add to your retroarcCustom.cfg :menu_driver = rgui video_font_path = /recalbox/share_init/system/.emulationstation/themes/recalbox/data/ubuntu_condensed.ttf
This will restore retroarch as before
Regardnig your xbox pad : was this pad the 1st player ? The xbox 360/one driver changed in 4.1, you do need to reconfigure your pad. Was your pad the 1st player ? HK is not used on players others than the 1st
-
@Substring thanks again.. ok I'll try to add the lines later.. regarding the controller I tried to set player1 and it doesn't work, tried to set default same issues. Looking in cfg file I noticed that I have controllers.xboxdrv.enabled=0, could it be the problem? (I had the same setting in 4.0.2 and it worked)
-
@jthemad no more xboxdrv on 4.1, as i already said
-
@Substring you said it changed, not it is not used in 4.1. However I have the line i wrote in 4.1 recalbox.conf file.. controllers.xboxdrv.enabled=0
Section D2 -
@jthemad nevermind the line, it's not used anymore
-
@Substring ok I'll try reset the keys but I think there is a bug with this controller.. I'll let you know.. hi
-
@Substring I had the same issue with the square bug, and those lines did the job allright. Thank you !
It might be worth adding the info in the first post. -
@Mercvtio there is a much faster way to solve it, but the fix is done, needs some testing
-
@Substring said in [4.1-Unstable] Bug reports:
can't update with a USB key from 4.0.1 to 4.1 : yeah, that's a major problem, we're investigating on that
Is this still a problem? Just updated from 4.0.2 to 4.1 with USB attached HDD (system on HDD). No problem so far, everything worked like it should. Even the MAXTRY entry works now without modification - great job!
-
@peterpan123123 hi, what is your fs ? Fat32/NTFS/ext4 ?
-
@rockaddicted ext4
-
@peterpan123123 Ok this bug only affect devices formated on fat32
-
Hi there,
I have a bug with 2 dreamcast games : PowerStone2 et Shenmue. (DELETED BY MODERATION: DO NOT MAKE REFERENCE TO ANY SOURCE).
These 2 games only display a black screen.
I'm using these bios :e10c53c2f8b90bab96ead2d368858623 dc_boot.bin
0a93f7940c455905bea6e392dfde92a4 dc_flash.binAnyone have the same issue ?
-
@Substring said in [4.1-Unstable] Bug reports:
@jthemad no more xboxdrv on 4.1, as i already said
What does this mean? No use of xbox controller att all?
-
@starmagoo said in [4.1-Unstable] Bug reports:
@Substring said in [4.1-Unstable] Bug reports:
@jthemad no more xboxdrv on 4.1, as i already said
What does this mean? No use of xbox controller att all?
That mean we are using the kernel driver,
xpad
, no more the standalone driverxboxdrv
.
This driver is no more maintains since more 1 year, and is no more working on new linux kernels.