deba5er wrote:Would the sound modules be hard to replace with free kernelloader modules? Is the coding difficulty high or nigh on impossible? ;-)
Currently RTE SBIOS need to be loaded by kernelloader to get sound working. I added code to TGE SBIOS. In theory it should do the same as RTE, but it is not working and I don't know what is wrong. So this also need to be fixed.
My plan was not to use free modules. I wanted to use the modules from rom1:, but I detected that these modules are incompatible with RTE SBIOS. So when some day my TGE SBIOS will work with RTE modules, it will not be compatible with rom1: modules.
I think reverse engineering of sdrdrv.irx is more difficult than the TGE SBIOS sound functions or dmarelay.irx. dmarelay.irx include debug symbols. sdrdrv.irx doesn't include debug symbols. You can easily reverse engineer 80% in a short time. When you have reverse engineered with accuracy of 99.99% the module will not work. It will only work when you reverse engineer 100%.
So why use the PS2 sound drivers at all? Just bang on the hardware directly. Enough is known about the SPU2 that the driver isn't needed anymore. Even if every last bit isn't completely understood, it's well enough understood for basic drivers for linux.
I can see where writing from scratch would be a daunting task, even if the SPU is well documented. Are there versions of sdrdrv.irx with debug symbols? Early releases, etc? Googling sdrdrv.irx produces plenty of hits.
Well, you can look at the sound library some guy wrote for the original SPU on the PSX, then look at the includes for the SPU2 that are part of PCSX2. That would be a good place to start.
Tried to load via AR Media Player but it hangs up at step 3. (select kernel usb stick!) All files (kernel 1.0, vmlinux, vmlinux.devfs, initrd.gz and blackrhino_baseimage-1.0.tar.gz) are on the stick but it doesn t load...
I also tried this with kernel 1.8... the same
If I would try to burn a DVD-R/CD-R what burn program do I need?
Note: You can t buy the Linux-Kit anymore. www.linuxplay.com doesn t existist anylonger. Sonyś technical support told me, its now an linux exclusive thing.
Questions are a burden to others, answers a prison for oneself
Riff M-33 wrote:Tried to load via AR Media Player but it hangs up at step 3. (select kernel usb stick!) All files (kernel 1.0, vmlinux, vmlinux.devfs, initrd.gz and blackrhino_baseimage-1.0.tar.gz) are on the stick but it doesn t load..
Note:I got some problems with the keyboard when using this version.
You can copy kernel and initrd on a PS2 memory card using a program like LaunchELF. The kernel can be compressed with gzip to get more files on a memory card. The tar archive can be read from USB directly, because Linux supports more USB hardware than the kernelloader.
Riff M-33 wrote:
If I would try to burn a DVD-R/CD-R what burn program do I need?
This is a pre-configured PS2-Linux (hdd/NTSC) installation with initial password "changeme".
It mingetty autoboots into X-Windows (NTSC configured), Fluxbox 0.9.14 window manager, right click for app menus. Fox Toolkit 1.6.34 apps, Xmms 1.2.11 music player, Feh 1.3.4 image viewer, conky 1.6.1 system monitor, latest openssl/openssh included, along with most importantly Dillo Browser 0.8.6 with tabs/internationalization/download progress bar.
Don't know if this is useful to folks, but the distro is <150MB and might save folks a lot of compiling ;-)
im using PS Two Slim SCPH 90006CB
i tried kloader 1.9, enable "PS Two Slim" option, using all kernels one by one,
if i use standard initrd its working, but my usb keyboard cant type anything
if i use initrd usb its not working, got error message "USB device not accepting new address"
finally, i got it working on testing version kloader and kernel
but it cant set ip, eth0 not detected..
I also have the slim PS2 and got stuck at the missing network device just like you. Mega Man then suggested trying to find some patched network drivers. Found a few, but not a single one addressing this problem. However, tried them, but neither did help.
citronalco, is yours can mount usb drive?
mine cannot mount anything, it display error in module
im using testing version kernel, and its only 1 mb in size,
i believe its not full functionality, maybe network driver is missing
@cosmito - I have no way to test PAL configurations, but prior to booting you may edit the /usr/local/bin/win* scripts (changing NTSC to PAL). You might need to add margins if you can't tune your TV output for displayable image (the example shows margins of 5 pixels):
export TV_MARGIN_X=5
export TV_MARGIN_Y=5
After this things *should* work, but if they don't, comment out the last line in /home/adent/.bash_profile (one of the win scripts), so that you can troubleshoot the problem outside of the graphical interface.
citronalco wrote:@bee7:
On May 7th Mega Man posted some more details about USB mass storage, so creating device nodes with mknod might be sufficient (see page 5).
The network interface is not functional with the PS2 slim.
i tried this:
cd /dev
mknod sda b 8 0
mknod sda1 b 8 1
cd ..
mkdir mnt
cd mnt
mkdir flashdisk1
mount -t vfat /dev/sda /mnt/flashdisk1
result:
modprobe: modprobe: Can't open dependencies file /lib/modules/2.4.17_mv121/modules.dep (No such file or directory)
mount: /dev/sda is not a valid block device
mount -t vfat /dev/sda1 /mnt/flashdisk1
result:
modprobe: modprobe: Can't open dependencies file /lib/modules/2.4.17_mv121/modules.dep (No such file or directory)
mount: /dev/sda1 is not a valid block device
i open file 2.4.17_mvl21-kernel-modules.tar.gz, cant find modules.dep inside it
i've found the way to modify initrd.img file by mounting it to linux in my pc, should i copy all file in 2.4.17_mvl21-kernel-modules.tar.gz to initrd image?
i tried command depmod too:
depmod: Can't open /lib/modules/2.4.17_mv121/modules.dep for writing
i see another version in modules directory:
2.2.21-pre1-xr7, and there is modules.dep in it, i think it finds modules.dep in wrong version
cannot include it into initrd img,size too big, its 2mb total, initrd only have freespace 824KB after the old module deleted. anything i unused that i can remove it?
@bee7 - In my configuration, my vmlinux (kernel) and initfs.gz are located in BWLINUX directory on my memory card 0 (as seen for uLaunchElf). Linux might be trying to mount /mnt/mc00 which using Megaman's kernel mounts the BWLINUX directory. If it doesn't exist, you get an error like you noted. It would seem your boot still is trying to find something (kernel maybe) on the memory card. If you have room on your card, try creating the BWLINUX directory in uLaunchElf, then place the vmlinux (kernel) in that directory before attempting to run Megaman's kernelloader.
sorry if this is the wrong thread, but i've been struggling trying to run linux through this great bootloader...
i've got a 79001 slim ntsc slim ps2 with a 4gb usb thumb drive and usb keyboard...
the problem is that regardless of the kernel (or bootloader) i use, neither the usb drive nor the keyboard are detected... if i try the usb-boot initrd then it detects both devices, but then it endlessly loops trying to install them... the error is this one:
usb.c: USB new device connect on bus 1/2, assigned device number 1
usb_control/bulk_msg: timeout
usb-ohci.c: unlink URB timeout
usb.c: USB device not accepting new address=1 (error=-145)
usb.c: USB new device connect on bus 1/2, assigned device number 2
usb_control/bulk_msg: timeout
usb-ohci.c: unlink URB timeout
usb.c: USB device not accepting new address=2 (error=-145)
usb.c: USB new device connect on bus 1/2, assigned device number 3
usb_control/bulk_msg: timeout
usb-ohci.c: unlink URB timeout
usb.c: USB device not accepting new address=3 (error=-145)
and so on, ad infinitum...
i tried enabling and disabling every module, both the standard and specially patched 1.8 and 1.9 versions of the bootloader, several kernel versions (even the IRQ patched one) to no avail, the behaviour is always the same (when using a standard initrd the devices arent detected and when using the 'usb-boot' initrd the devices installation fail)
i also tried everything else mentioned in this thread, to no avail
luncheonticket wrote:sorry if this is the wrong thread, but i've been struggling trying to run linux through this great bootloader...
i've got a 79001 slim ntsc slim ps2 with a 4gb usb thumb drive and usb keyboard...
the problem is that regardless of the kernel (or bootloader) i use, neither the usb drive nor the keyboard are detected... if i try the usb-boot initrd then it detects both devices, but then it endlessly loops trying to install them... the error is this one:
usb.c: USB new device connect on bus 1/2, assigned device number 1
usb_control/bulk_msg: timeout
usb-ohci.c: unlink URB timeout
usb.c: USB device not accepting new address=1 (error=-145)
usb.c: USB new device connect on bus 1/2, assigned device number 2
usb_control/bulk_msg: timeout
usb-ohci.c: unlink URB timeout
usb.c: USB device not accepting new address=2 (error=-145)
usb.c: USB new device connect on bus 1/2, assigned device number 3
usb_control/bulk_msg: timeout
usb-ohci.c: unlink URB timeout
usb.c: USB device not accepting new address=3 (error=-145)
and so on, ad infinitum...
i tried enabling and disabling every module, both the standard and specially patched 1.8 and 1.9 versions of the bootloader, several kernel versions (even the IRQ patched one) to no avail, the behaviour is always the same (when using a standard initrd the devices arent detected and when using the 'usb-boot' initrd the devices installation fail)
i also tried everything else mentioned in this thread, to no avail
This version still includes some debug output, which could make it a little bit slow. You need also to select the special interrupt handling modules for slim PSTwo.