|
Post by gurce on Jan 28, 2019 9:33:12 GMT
Cool, was able to boot into the ramfs! The only gotchya I seem to have is my fairly old USB-to-LAN adapter doesn't seem to be getting recognised. dmesg says: usb 2-1.1.3: new full-speed USB device number 9 using sw-ehci usb 2-1.1.3: New USB device found, idVendor=050d, idProduct=0121 usb 2-1.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 2-1.1.3: Product: USB To LAN Converter usb 2-1.1.3: Manufacturer: ADMtek usb 2-1.1.3: SerialNumber: 0001 When I do "lsusb", it is listed as:
Bus 002 Device 009: ID 050d:0121 Belkin Components F5D5050 100Mbps Ethernet
Gee, even my Windows 10 doesn't seem to recognise this device anymore, even when I try let Windows try to find a driver online.
Still, if there's any hope, JJ, let me know Otherwise I'll bite the bullet and buy a new one.
Gee, even Belkin's site only offers limited driver support, only up to Windows Vista 32-bit
|
|
|
Post by jj0 on Jan 28, 2019 10:54:22 GMT
Cool, was able to boot into the ramfs! The only gotchya I seem to have is my fairly old USB-to-LAN adapter doesn't seem to be getting recognised. dmesg says: usb 2-1.1.3: new full-speed USB device number 9 using sw-ehci usb 2-1.1.3: New USB device found, idVendor=050d, idProduct=0121 usb 2-1.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 2-1.1.3: Product: USB To LAN Converter usb 2-1.1.3: Manufacturer: ADMtek usb 2-1.1.3: SerialNumber: 0001 When I do "lsusb", it is listed as:
Bus 002 Device 009: ID 050d:0121 Belkin Components F5D5050 100Mbps Ethernet
Gee, even my Windows 10 doesn't seem to recognise this device anymore, even when I try let Windows try to find a driver online.
Still, if there's any hope, JJ, let me know Otherwise I'll bite the bullet and buy a new one.
Gee, even Belkin's site only offers limited driver support, only up to Windows Vista 32-bit
You can try this module. Put it on a USB drive and then after you are in the command prompt (and have mounted the USB drive to /mnt) do 'insmod -f /mnt/pegasus.ko". If it works I'll include it in the mythical next release.
|
|
|
Post by jj0 on Jan 28, 2019 11:02:13 GMT
If you would be so kind to give me a hint on the correct syntax to DELETE all the games in the NAND (just the delete commando/line) I will do that and post the scripts for others here later tonight. [/quote] Assuming you have the nandb rootfs mounted at /mnt that would be an 'rm' with options 'recursively' and 'folders': rm -rf /mnt/usr/share/the64/games/* Note this will delete everything in the games folder including the subfolders but keeps the games folder. If instead you want to delete the games folder as well: rm -rf /mnt/usr/share/the64/games
Be careful with typo's, the rm -rf command is ruthless.
|
|
|
Post by kugelblitz on Jan 28, 2019 11:13:16 GMT
If you would be so kind to give me a hint on the correct syntax to DELETE all the games in the NAND (just the delete commando/line) I will do that and post the scripts for others here later tonight. Assuming you have the nandb rootfs mounted at /mnt that would be an 'rm' with options 'recursively' and 'folders': rm -rf /mnt/usr/share/the64/games/* Note this will delete everything in the games folder including the subfolders but keeps the games folder. If instead you want to delete the games folder as well: rm -rf /mnt/usr/share/the64/games
Be careful with typo's, the rm -rf command is ruthless. [/quote] Thank you - Scripts are already online! :-)
|
|
|
Post by bronze on Jan 28, 2019 11:44:24 GMT
Hi ya, thanks for the scripts! I have an issue thou. I got into FEL mode, I've backed up the nand, and used your script to backup the original games with no issues. I then used the "overwrite game to carousel" script which seemed to work fine, but I have a black screen on boot up now My question, I had not yet changed the root password could this be an issue? I also have not changed read/write protections? So wondering if this could be the cause? any advice appreciated.
|
|
|
Post by kugelblitz on Jan 28, 2019 12:36:24 GMT
Hello Bronze, I had this problem once too but it was based on a defective .TSG file (I was experimenting on adding Castles of Dr Creep). When I removed that .tsg file the Mini booted fine.
|
|
|
Post by bronze on Jan 28, 2019 13:02:25 GMT
Cool, I'll try that, I was doing just that with Bruce lee 2 Just so I'm understanding this right, can I in theory simply boot into FEL mode and use your scripts to change the games, without having to change permissions etc? Or have a missed something? (was looking for a quick streamlined way of changing the games)...I know a bit of Linux from playing with raspberry pi's but have to learn as I go normally.
|
|
|
Post by kugelblitz on Jan 28, 2019 13:53:01 GMT
Cool, I'll try that, I was doing just that with Bruce lee 2 Just so I'm understanding this right, can I in theory simply boot into FEL mode and use your scripts to change the games, without having to change permissions etc? Or have a missed something? (was looking for a quick streamlined way of changing the games)...I know a bit of Linux from playing with raspberry pi's but have to learn as I go normally. That what I did yesterday night. Never touched SSH or FTP at all. Just started FEL Mode with the USB stick in the Mini (it needs to be there at boottime!). While the scripts are doing their thing, the Mini will display a static C64-like screen. When they are done you see the command prompt. Once you see the command prompt, you can safely turn off the C64 for reboot (or reboot via the command line).
|
|
|
Post by bronze on Jan 29, 2019 2:23:49 GMT
Hi guys, Glenn here, need some help, it appears I've messed something up!
Using FEL mode last night, I used Kugelblitz's scripts, backed everything up, and put a new set of games on the mini (all previously made by other members here except one game). The mini failed to boot, thought it may have been my game creation attempt and removed it this morning and restored all original games previously backed up...still black screen no boot.
Any ideas?
Upon entering FEL mode now as the U-boot launch screen appears on the mini, I now have an error showing - "loading environment from FAT... ** bad device mmc 1 ** anyone know what this is?
Also I have backed up nand A and B, I know how to copy them but not the command/s to restore them via usb, if someone could enlighten me please.
Thanks
Glenn
|
|
|
Post by kugelblitz on Jan 29, 2019 8:18:06 GMT
Hi guys, Glenn here, need some help, it appears I've messed something up! Using FEL mode last night, I used Kugelblitz's scripts, backed everything up, and put a new set of games on the mini (all previously made by other members here except one game). The mini failed to boot, thought it may have been my game creation attempt and removed it this morning and restored all original games previously backed up...still black screen no boot. Any ideas? Upon entering FEL mode now as the U-boot launch screen appears on the mini, I now have an error showing - "loading environment from FAT... ** bad device mmc 1 ** anyone know what this is? Also I have backed up nand A and B, I know how to copy them but not the command/s to restore them via usb, if someone could enlighten me please. Thanks Glenn Autsch! Sorry about that - but if you restored all the original games and you still have a black screen I am at a loss. For me the only reason why it would not boot was a defective .TSG file (saved with the wrong encoding) that was easily fixed. But your description sounds different, especially as you can't even FEL boot anymore.
|
|
|
Post by jj0 on Jan 29, 2019 9:05:31 GMT
Hi guys, Glenn here, need some help, it appears I've messed something up! Using FEL mode last night, I used Kugelblitz's scripts, backed everything up, and put a new set of games on the mini (all previously made by other members here except one game). The mini failed to boot, thought it may have been my game creation attempt and removed it this morning and restored all original games previously backed up...still black screen no boot. Any ideas? Upon entering FEL mode now as the U-boot launch screen appears on the mini, I now have an error showing - "loading environment from FAT... ** bad device mmc 1 ** anyone know what this is? Also I have backed up nand A and B, I know how to copy them but not the command/s to restore them via usb, if someone could enlighten me please. Thanks Glenn Autsch! Sorry about that - but if you restored all the original games and you still have a black screen I am at a loss. For me the only reason why it would not boot was a defective .TSG file (saved with the wrong encoding) that was easily fixed. But your description sounds different, especially as you can't even FEL boot anymore. The 'bad device mmc 1' is normal, the Mini doesn't have an SD-card slot. To restore nandb after FEL boot: insmod -f /opt/nand.ko dd if=<path to your nandb backup> of=/dev/nandb
|
|
|
Post by bronze on Jan 29, 2019 10:07:56 GMT
Thanks for the response jj0 I'll give it a go after dinner! kugelblitz all good, I can still boot into FEL, I too am at a loss as to why it isn't booting, your scripts seen solid, hopefully restoring nandb will sort it out Luck would have it I have two mini's so still able to play! this one is the tinker lol.
|
|
|
Post by kugelblitz on Jan 29, 2019 12:25:21 GMT
Thanks for the response jj0 I'll give it a go after dinner! kugelblitz all good, I can still boot into FEL, I too am at a loss as to why it isn't booting, your scripts seen solid, hopefully restoring nandb will sort it out Luck would have it I have two mini's so still able to play! this one is the tinker lol. Most likely one of the files you added is just broken. It is VERY important that the .TSG files are saved with pure UTF-8 encoding, some editors (Windows Notepad) mangle this (it becomes UTF-8 BOM) and then the Mini stays black. Also make sure that all graphic files have the right dimensions. The carousel code is not very forgiving. It doesn't need to be, as it never was meant for outside editing, so you have to be very careful when you add stuff. If the carousel does not get data the way it wants, it does not show errors or hints, it just stays black.
|
|
|
Post by gurce on Jan 29, 2019 21:11:57 GMT
Gee, even my Windows 10 doesn't seem to recognise this device anymore, even when I try let Windows try to find a driver online.
Still, if there's any hope, JJ, let me know Otherwise I'll bite the bullet and buy a new one.
Gee, even Belkin's site only offers limited driver support, only up to Windows Vista 32-bit
You can try this module. Put it on a USB drive and then after you are in the command prompt (and have mounted the USB drive to /mnt) do 'insmod -f /mnt/pegasus.ko". If it works I'll include it in the mythical next release.
Thanks JJ! I tried the pegasus module, and my USB-to-LAN adapter now works! I tried elinks too, working also, but seems like the number of rows isn't right, it only reaches halfway down the screen.
Also, the edges of my screen are a little clipped. I think somebody else in this thread had this prob too, so I'll have a read of what you suggested back then and see if I can get it sorted.
But all the same, this has been cool and fun, thanks for making this!!
|
|
|
Post by jj0 on Jan 29, 2019 21:16:28 GMT
You can try this module. Put it on a USB drive and then after you are in the command prompt (and have mounted the USB drive to /mnt) do 'insmod -f /mnt/pegasus.ko". If it works I'll include it in the mythical next release.
Thanks JJ! I tried the pegasus module, and my USB-to-LAN adapter now works! I tried elinks too, working also, but seems like the number of rows isn't right, it only reaches halfway down the screen.
Also, the edges of my screen are a little clipped. I think somebody else in this thread had this prob too, so I'll have a read of what you suggested back then and see if I can get it sorted.
But all the same, this has been cool and fun, thanks for making this!! You're welcome. You can change the #rows and #columns with 'stty rows <rows> cols <cols>; reset'. But mobluse had similar issues with full screen not working.
|
|
|
Post by crispin on Jan 30, 2019 4:23:50 GMT
Just to warn you guys, if you are adding new software at Mini: space is limited. If I got it right, fresh Mini has around 24MB free (PAL), or less (NTSC). Save game slots are eating space too - have in mind for future. After I installed Paolo's game set (14>11MB) and Midnight Commander (5MB), I left with only 6,6MB of free space. Then I made ti 7MB. You can gain 0,4MB more (or even more for NTSC), by recompressing original games (lossless). More about it here (updated). Before: root@redquarkone:/$ df -h Filesystem Size Used Available Use% Mounted on none 68.9M 62.3M 6.6M 90% /dev /dev/nandb 68.9M 62.3M 6.6M 90% / After: root@redquarkone:/$ df -h Filesystem Size Used Available Use% Mounted on none 68.9M 61.9M 7.0M 90% /dev /dev/nandb 68.9M 61.9M 7.0M 90% /
|
|
|
Post by bronze on Feb 3, 2019 3:13:53 GMT
Hi guys, getting back to you after replacing my nandb with the backup etc... Long story short restoring nand and original games did nothing, still black screen on boot, FEL mode still works fine. Thought ok, I'll have a look at the file system etc...and I've found or more to the point not found - "the64" program in the file list, it's just gone, the games folders don't show up either. This is with having nand mounted and unmounted. The files are not hidden are they? If not, it appears they have been wiped? Glenn
|
|
|
Post by jj0 on Feb 3, 2019 18:10:13 GMT
Hi guys, getting back to you after replacing my nandb with the backup etc... Long story short restoring nand and original games did nothing, still black screen on boot, FEL mode still works fine. Thought ok, I'll have a look at the file system etc...and I've found or more to the point not found - "the64" program in the file list, it's just gone, the games folders don't show up either. This is with having nand mounted and unmounted. The files are not hidden are they? If not, it appears they have been wiped? Glenn This is weird. Especially if you have restored the nandb backup. Could it be that the nand driver wasn't loaded when you restored nandb? Or that you haven't loaded the nand driver and/or mounted nandb when you are looking for 'the64'Â and/or the games directory?
|
|
|
Post by crispin on Feb 4, 2019 0:11:36 GMT
Strange. I have new & old backup of nanda & nandb if it could help, but not sure is it compatible now. Just for restoring missing folders, it is not a big problem imho. bronze : Too bad that you don't have MC there, you could compare it easily. ctrl + "." (dot) for hide/unhide iirc.
|
|
|
Post by bronze on Feb 4, 2019 9:25:22 GMT
Ok I've included a screenshot of mounting the nandb and the file list at root. As you can see when I list the mnt folder the nandb is there.
From what I've gathered the nandb once mounted is basically a folder which can then be opened and contains "the64" and game folders...is this right? or I'm I not getting it? The nandb comes up green, and I don't seem to be able to access it.
I do have another mini, so I could use the nand from it if the backup is corrupted.
At work tonight again, so quick post, jj0 maybe, I was still getting my head around it at the beginning, I'll try restoring the nand again tomorrow, when I'm finally on days off!
Guys let me know what I could post that extra eyes could mull over and I will.
Thanks
Attachments:
|
|
|
Post by jj0 on Feb 4, 2019 11:01:32 GMT
Ok I've included a screenshot of mounting the nandb and the file list at root. As you can see when I list the mnt folder the nandb is there. From what I've gathered the nandb once mounted is basically a folder which can then be opened and contains "the64" and game folders...is this right? or I'm I not getting it? The nandb comes up green, and I don't seem to be able to access it.
I do have another mini, so I could use the nand from it if the backup is corrupted. At work tonight again, so quick post, jj0 maybe, I was still getting my head around it at the beginning, I'll try restoring the nand again tomorrow, when I'm finally on days off! Guys let me know what I could post that extra eyes could mull over and I will. Thanks
nandb is the entire linux root filesystem of the Mini. So if you mount it at /mnt and do a 'ls /mnt' you should see something like: bin dev etc init lib lost+found media mnt opt proc root run sbin sys tmp usr var
However, yours seems to look like a Windows (fat-formatted) filesystem (as it has a 'System Volume Information' directory on it) with a file nandb on it. The nandb file is probably your nandb backup that you copied to an empty USB drive? What probably happened is that you restored the contents of the USB drive - that you have your nandb backup on - to /dev/nandb instead of the content of the nandb file on that usb drive. So you probably did something like 'dd if=/dev/sda1 of=/dev/nandb'. What you can do to repair this should be: - Reboot the Mini in FEL mode, with the USB drive that has the nandb backup file on it inserted
- Execute:
mount /dev/sda1 /mnt insmod -f /opt/nand.ko dd if=/mnt/nandb of=/dev/nandb sync reboot
Hopefully this should restore your Mini to its former working glory.
|
|
|
Post by bronze on Feb 5, 2019 3:10:18 GMT
jj0 you are a legend, thanks mate! all restored and working as normal
Now to try adding some games
|
|
|
Post by bronze on Feb 5, 2019 3:45:41 GMT
And also happy to report, have successful connection via FTP, test games copied across and working as they should! Happy days, thanks everyone for the help, loving this forum and the mini
|
|
|
Post by crispin on Feb 7, 2019 6:26:38 GMT
- root password is 'manicminerrules!'
Is it generic one, as it is described here: linux-sunxi.org/Retro_Games_Ltd_RGL001#Default_root_passwordI need a favour. Could someone send me original Mini menu-sounds, those at /usr/share/the64/ui/sounds/ ? I replaced them with "quieter menu-sounds" of gurce ( fb post). just realised that I don't have backup ( I made backup of already changed sounds, before last fw update). Not that I need it, but just in case. Btw I don't need music, just: ding, flip, menu_open & menu_close wavs.
|
|
|
Post by jj0 on Feb 7, 2019 8:15:08 GMT
|
|
|
Post by crispin on Feb 7, 2019 8:18:05 GMT
Thanks a lot! edit: jj0 , I moved our offtopic posts to new " Adding attachments using Cloudinary" thread (and hide related stuff here). edit2: - to copy this info again: I managed to clean this forum a bit, mostly this two hot topics: FEL and UART mod. Guys, please don't be angry because I edited your posts! I did only three things, mostly: 1.) Hide parts of gigant console dumpings, just not needed parts. So, not deleted, just turned to "spoiler"; 2.) deleted not needed empty lines here and there; 3.) highlighted and made bold: solutions to problems and important achievements.
|
|
|
Post by wigyori on Feb 12, 2019 23:38:29 GMT
Hi jj0, In the FEL log it looks like you've built an u-boot 2018.05 - did you use the mainline repo without modifications, and the standard a20-olinuxino-micro defconfig, or did you have to do any changes? (Apart from removing the SATA and VGA support from the config. ) Thanks, -w-
|
|
|
Post by jj0 on Feb 13, 2019 13:18:09 GMT
Hi jj0, In the FEL log it looks like you've built an u-boot 2018.05 - did you use the mainline repo without modifications, and the standard a20-olinuxino-micro defconfig, or did you have to do any changes? (Apart from removing the SATA and VGA support from the config. ) Thanks, -w- I used the mainline repo without modifications, but I don't remember what config I started with. Probably A20-OLinuXino-Lime_defconfig as I happen to have one of them but then I disabled almost everything. I've attached my .config in case it's useful for you. Attachments:.config (28.78 KB)
|
|
|
Post by mobluse on Feb 21, 2019 11:30:15 GMT
Hi jj0, In the FEL log it looks like you've built an u-boot 2018.05 - did you use the mainline repo without modifications, and the standard a20-olinuxino-micro defconfig, or did you have to do any changes? (Apart from removing the SATA and VGA support from the config. ) Thanks, -w- I used the mainline repo without modifications, but I don't remember what config I started with. Probably A20-OLinuXino-Lime_defconfig as I happen to have one of them but then I disabled almost everything. I've attached my .config in case it's useful for you. The terminal emulation in the current FEL-mode hack doesn't work with the Nano editor, as I demonstrated in my video above. Does the Linux in A20-OLinuXino-Lime also not work with Nano? In my experience there has never been any problem before with terminal emulation in real Linux. Is this terminal emulation in A20-OLinuXino-Lime some new project?
|
|
|
Post by jj0 on Feb 22, 2019 14:48:53 GMT
I used the mainline repo without modifications, but I don't remember what config I started with. Probably A20-OLinuXino-Lime_defconfig as I happen to have one of them but then I disabled almost everything. I've attached my .config in case it's useful for you. The terminal emulation in the current FEL-mode hack doesn't work with the Nano editor, as I demonstrated in my video above. Does the Linux in A20-OLinuXino-Lime also not work with Nano? In my experience there has never been any problem before with terminal emulation in real Linux. Is this terminal emulation in A20-OLinuXino-Lime some new project? There is something weird happening in the combination of Nano and Yaft (the framebuffer terminal emulator that I've used in the FEL hack). This has no relation to the A20-OLinuXino-Lime default Linux distro.
|
|