x64 system running 18.04.20 doesn't work too well

[ShamanMogz]

@Substring My hard drive is now 3TB.

• When I started out I was using a 0.5TB hard drive on 18.03.30
• I upgraded that drive to 18.04.20 using the inbuilt UI in recalbox
  Then the problems started to happen
• I then changed drives to 3TB and used a fresh 18.04.20 image

Is there a maximum HDD that is supported?

[Substring]

@shamanmogz you make me search real deep ...
Recalbox uses a MBR partition table, not GPT. This limits the numver of sectors to 2^32, which is around 2TB.

Going to GPT may not be a good idea yet.

[ShamanMogz]

@Substring Ok I will roll back to my 0.5TB drive for now unless you think I can partition my 3TB to give me 2x 1.5TB internal shares.

[Substring]

@shamanmogz why do you need that much space ? If it's fully loaded es will be real slow probably.

And no, we could eventually have a 2TB internal share, but nothing more, the last TB would be wasted

[voljega]

@substring for a full collection of all systems, 2TB is not enough

[ShamanMogz]

@substring It's more to do with i have a 3TB HDD kicking around so why not use it. I'm flashing the 0.5TB as I type.

[Substring]

@shamanmogz you would be a good guinea pig for some advanced logging i've been working on. Would you agree to give a try to it ? You'd just need to change the updates.type value in recalbox.conf, make the upgrade and report some logs

[ShamanMogz]

@Substring yeah i'm cool with that. is there a better way to do this rather than using forum posts?

[Substring]

@shamanmogz discord ?

[ShamanMogz]

@Substring sure, just installing it. Note i don't have a mic on this system - i can get hold of one in a few days, but for now it's just text chat. What's your server?

[Substring]

@shamanmogz we've advertised it some days ago. No need for a mic

By the way, we can do anneasier way : run bash -x /etc/init.d/S11share start and give me the output please

[ShamanMogz]

@substring said in x64 system running 18.04.20 doesn't work too well:

bash -x /etc/init.d/S11share start

Note: I'm back on a 0.5 TB drive and it's running ok

Using username "root".
root@recalbox's password:
# bash -x /etc/init.d/S11share start
+ test start = stop
+ test start '!=' start
+ SHARECONFFILE=/boot/recalbox-boot.conf
++ /recalbox/scripts/recalbox-part.sh share_internal
+ INTERNALDEVICE=/dev/sda3
++ cat /boot/recalbox-boot.conf
++ grep sharedevice=
++ head -n1
++ cut -d= -f2
+ SHAREDEVICE=INTERNAL
+ [[ 0 -ne 0 ]]
+ [[ INTERNAL == '' ]]
+ INTERNALDEVICETYPE=ext4
++ getMaxTryConfig /boot/recalbox-boot.conf
++ SHARECONFFILE=/boot/recalbox-boot.conf
+++ grep -E '^[ \t]*sharewait[ \t]*=' /boot/recalbox-boot.conf
+++ sed -e 's+^[ \t]*sharewait[ \t]*=++'
++ X=
++ echo ''
++ grep -qE '^[0-9][0-9]*$'
++ echo 7
+ MAXTRY=7
+ NTRY=0
+ test -e /dev/sda3
+ RMODE=INTERNAL
+ echo INTERNAL
+ grep -qE '^DEV '
+ MODE=INTERNAL
+ case "${MODE}" in
+ /recalbox/scripts/recalbox-mount.sh ext4 1 /dev/sda3 /recalbox/share
mount: mounting /dev/sda3 on /recalbox/share failed: Device or resource busy
+ mount -t tmpfs -o size=128M tmpfs /recalbox/share
+ ls /var/run/usbmount.delay
+ read RULE
+ touch /var/run/recalbox.share.mounted
+ logpath=/recalbox/share/system/logs
+ for bootlogfile in '/tmp/logappend-*.*'
++ echo '/tmp/logappend-*.*'
++ sed 's|/tmp/logappend-||'
+ destfile='*.*'
+ cat '/tmp/logappend-*.*'
/etc/init.d/S11share: line 289: /recalbox/share/system/logs/*.*: No such file or                                                                          directory
+ rm '/tmp/logappend-*.*'
rm: can't remove '/tmp/logappend-*.*': No such file or directory

[Substring]

@shamanmogz d**n my bad. Reboot it then

cd /
/etc/init.d/S31emulationstation stop
/etc/init.d/S92virtualgamepads stop
bash -x /etc/init.d/S11share start

[ShamanMogz]

@substring I just realised that although I changed the update option in the UI after a power cycle it hasn't persisted (so my last set of test results was invalid). Maybe I should change the updates.type value in the recalbox.conf file itself? If you agreem what should that value be?

Also on a different note, I have 4x 2GB ram sticks kicking about. I tried to add them in but Recalbox refuses to boot. Is there a max ram limitation (i have a 64 bit processor and am using the 64 bit build). Actually on that note, how do I know if my GT 710 graphics card has been installed properly?

lastly sorry for the delay - was away for the long weekend.

[Substring]

@shamanmogz i'm on holidays for now, ping me in a week for such a delicate topic

[SylGaud]

@shamanmogz said in x64 system running 18.04.20 doesn't work too well:

My system is a 64bit core 2 DUO (E6750) with a GT710 and 4GBs of RAM, 3TB HDD

Hi Shamanmogz,
I intend to buy a MSI GT 710 1GD3H LP --> according to what you say, GT710 works fine with RecalBox ?

Thanks

[SylGaud]

Well, the GT 710 works with RecalBox.
A bit laggy with Wii and GameCube (I use a 5 year-old compaq Elite, maybe I could tweak a bit) but it works.

[SylGaud]

@Substring
Hi, I'd like to add my experience with the GT 710 on this page: https://github.com/recalbox/recalbox-os/wiki/PC-compatibility-(EN)
do I have to create an account, or use the pull request? (or simplier: I tell you my feedback and you paste it^^)

Thanks

[voljega]

@sylgaud it's just a wiki, you only need an account

[SylGaud]

GT 710 isn't properly seen.
I've tested Wii and GameCube with the GT 710 under Windows 10 --> perfectly smooth, filtered etc...

So GT710 not yet compatible with RB.