Printable View
My nick bothering here because i want emulators in Linux, if anyone can't do it without. If at least ideal SEGA emul would existed, i'm not taking a part in PS2Linux testing now.
PGEN has defects. One of them is that it going slow sometimes and it is hard to fix in-game. Another, some games not working such as Soldiers of Fortune and Gargoyles. And sometimes music is not stereo and some channels are lost.
I'am as rooted retrogamer not accept such treatment to old-game emulator!!!
PicoDrive is using the framebuffer in platform/linux. This was only used for emulating the gp2x environment. I don't think it will run on a normal Linux anymore. You could ask notaz at OpenPandora Boards to get the stuff fixed.
I compiled fluxbox and it was working. It needs some time to start. I didn't connected a mouse, so I couldn't test the mouse:
Attachment 39017
Content of /root/.xinitrc:
#!/bin/sh
exec fluxbox
Started as root user with startx (unchanged Fedora 12 xorg).
I started firefox on my desktop and redirected the display to my PS2:
xhost +192.168.0.130 # On PS2
export DISPLAY=192.168.0.127:0 # On desktop PC
firefox # on desktop PC
Attachment 39018
Fluxbox was compiled native on the fat PS2 with Fedora 12 (gcc (GCC) 4.4.3 20100127 (Red Hat 4.4.3-4), not changed). Cross compiling with a different version can break the build. Fluxbox is using C++. I don't believe that C++ is compatible between different compiler versions (especially when using Fedora).
You will be able to download it from the downloads of this forum.
Ok, now i know that fluxbox works with Xorg, and i guess you have no problem with fonts. Please, launch fluxbox once again with log-file and attach it here.
BTW, Mega Man, did you know, that you are swindler?))) You have fat PS2 and testing all in it. Even compiling - you can do it native!
Why wouldn't you test Xgsx? If you not want to reformat your HDD, then you can test it at least with loop-file and initrd-busy.
Here EXT3 loop-file with system copied from qemu. I compiled Xgsx without ps2spr to it with distcc/mips64r5900el single-float'ed. Then, you can see all that i saw and test everything that i could not.
Also, i have almost same loop-file with Xgsx with ps2spr compiled...
Xgsx can't work with Fedora 12, because Xgsx is already not working with BlackRhino on Linux 2.6. I don't know where the problem is.
Then share your thinks about graphic optimizing.
At the moment, we have kernel that can operating with mipsel 32-bit and mips64el N32 linuxes. In which, we have bad variants of graphic - it just slow.
If not digging the problem in Xgsx or old ps2dev-codes in kernel,
then what? How do you think you can make Xorg faster???
The problem is not the graphic. Xorg alone is fast enough. Even the bad graphic driver is fast enough to play videos, because the hardware is optimized for this. On higher resolution it gets slower, but I don't know if the player application or the driver is responsible for this. Simple PAL or NTSC is fast enough. Fluxbox seemed to be usable, but I couldn't test the mouse. The hard disc improves the performance. USB is slower (12MBit). The main problem is the memory limitation. The PS2 has only 32MByte. This is fine for single tasking like games. This works with much text mode Linux programs. Apple used for the old computers a slow CPU and much memory. The systems seemed to be more usable than others. The only way to get more memory is the PS2 Tool.
I don't have it, but I have a fat PS2. The internal hard disc improves the speed. I think you use network instead, this can be to unstable. You should at least try to use USB. Swap file over network is bad. You could also try to create a Live DVD. The DVD drive can reach a nice speed when the disc is good and readable.
The only way which will work, is to use programs with less memory footprint (e.g. uClibc instead of glibc, change configuration, optimize code for size -Os, use shared libraries instead of static, use framebuffer instead of X11, compile code for r5900 instead of generic MIPS, use busybox instead of full utils like udev, don't use D-Bus, don't use NetworkManager, don't use hald, use ext2 instead of ext3 or ext4, use fluxbox instead of kde, use C instead of C++, disable unused features in the kernel, define videomemory to the minimum, use 16 bit color instead of 32 bit colors, don't use programs with memory leaks, don't use shmfs, verify that initrd memory is freed, sometimes it can also be faster to use the seemingly slow stuff...).
WOW!
So, i think, the single-float compiling should be beginning!
I can fast cross-compile new system for r5900 by your toolchain.Quote:
Originally Posted by Mega Man
Just write here:
1. Which firsts packages needs to be compiled: bash, init, baseutils, etc.
2. Which flags need to be used.
First you need to think about which way you want to go, e.g.:
1. Use build system of Fedora (rpm).
2. Use build system of Debian (deb).
3. Use Build System of an embedded Open Source Linux Distribution like OpenWrt or ELDK. The advantage is that it is prepared to use less resources and it is normally prepared for cross-compiling. Maybe there is stuff missing.
4. Use a system which is prepared for building from source like Gentoo
5. Don't use a build system and make it yourself. Then "Linux From Scratch (LFS)" can help.
The following describes the order:
Построение временной системы
LFS 6.4 uses a similar compiler version: Chapter*5.*Constructing a Temporary System
I am for Fedora and rpms! Using this way, building becomes compareable. We can build and compare how it Fedora programmers did. Besides, i hate sudo...
Don't search pages on Russian more) Translates are sucks! I get used English instructions.
My "PS2 Tool" is qemu+distcc :) I wonder if only qemu can emulate ps2 devices...Quote:
Originally Posted by Mega Man
EDIT:I think, i can try build new r5900 N32 system, but i need to know:Quote:
Originally Posted by Mega Man
1. Need i recompile mips64r5900el-toolchain to based on uClibc?
2. Can i use uClibc instead glibc in new system? If yes, which configuration should i use for uClibc native compiling?
3. Which flags i need to use? You said: "optimize code for size -Os" - so, need i these -Os?
You need to test which combination is working and which combination is faster.
