Jammet
Creatures
Coffee. ♪ Good.
Posts: 31
|
Post by Jammet on May 4, 2018 14:27:37 GMT
Part of me wants to mess around with the Mini and try all this, but then again, I sorta like having it in it's original form. Still holding out for that ominous update. But that is some beautiful work you're putting into this.
|
|
|
|
Post by jj0 on May 4, 2018 15:32:38 GMT
Part of me wants to mess around with the Mini and try all this, but then again, I sorta like having it in it's original form. Still holding out for that ominous update. But that is some beautiful work you're putting into this. Come on, go ahead and join us at the dark side ;-) |
|
|
|
Post by ch1ller on May 4, 2018 15:57:21 GMT
Part of me wants to mess around with the Mini and try all this, but then again, I sorta like having it in it's original form. Still holding out for that ominous update. But that is some beautiful work you're putting into this. Be honest.... How many of the installed games do u play/like? I caught myself just playing about 3-4 Games till now... Paradroid, Deflector, Boulderdash... Most of the installed Games are not really my Games... Using USB Stick iss even with one possible d82 File a Pain in the Ass.. Should get better with another Update... but when? Naaa, for me was sure to mod the c64 mini before even having it... Hopefully a russian Nerd will find an easier Way of modding it but until then i also dont want to wait or to miss playing the Games i like  And still its a fuss with the Joystick(settings)... Sometimes work, sometimes not... Think its even more into it than just defining Keys to the Buttons... Or many Joysticks not even recognized.. also good u can add them yourself and not have to buy new ones. But as long you can try yourself and try to fix things or add things its just great. <3 Have to thank Retro Games for giving us this possibility at all... |
|
|
|
Post by spinal on May 4, 2018 19:09:25 GMT
I noticed that during the boot up, I think it actually checks for a ds card. I wonder if adding a slot in the space provided and using the same method as usb would mean that once the file system is backed up we could do away with the serial connection completely.
|
|
Jammet
Creatures
Coffee. ♪ Good.
Posts: 31
|
Post by Jammet on May 6, 2018 1:03:52 GMT
I'm fine with waiting a wee bit longer until the firmware upgrade enables me to load up just about anything at will. So no worries. You're right about the games on it, of course. My selection would be QUITE different.  |
|
|
|
Post by tomxp411 on May 8, 2018 23:19:27 GMT
Part of me wants to mess around with the Mini and try all this, but then again, I sorta like having it in it's original form. Still holding out for that ominous update. But that is some beautiful work you're putting into this. What you need is a second Mini - one to mod and one to keep virgin. |
|
|
|
Post by spinal on May 10, 2018 20:21:19 GMT
Does anyone have any ideas for removing the need for the serial connection after the software is copied to usb? I have been tempted to try to substitute the serial adaptor with an arduino, have it monitor the serial output, interrupt it and send the command to boot from usb. Not sure how well it would work though.
Unless any linux users know how to permanently change the boot path to the usb?
|
|
|
|
Post by spinal on May 11, 2018 19:13:25 GMT
OK, I seem to have killed something, I can boot from USB no problem, but when I boot normally I just get a black screen.
Here is my serial output...
HELLO! BOOT0 is starting!
boot0 version : 3.0.0
dram size =256
current block is 2 and last block is 10.
current block is 3 and last block is 10.
current block is 4 and last block is 10.
current block is 5 and last block is 10.
current block is 6 and last block is 10.
current block is 7 and last block is 10.
sum=0x4c7f5fd3
src_sum=0x4c7f5fd3
The file stored in start block 2 is perfect.
Ready to disable icache.
Jump to secend Boot.
[ 0.179]
U-Boot 2011.09-rc1 (Dec 10 2017 - 17:25:12) Retro Games Ltd
[ 0.186]version: 1.1.0
[ 0.189]pmbus: ready
[ 0.294]PMU: AXP209
[ 0.297]PMU: AXP20x found
[ 0.300]PMU: bat ratio = 100
[ 0.303]after set, dcdc2 =1400mv
[ 0.307]PMU: dcdc2 1400
[ 0.309]PMU: pll1 912 Mhz
boot_clock = 912
dcdc2_vol = 1400
[ 0.317]after set, dcdc2 =1400mv
dcdc3_vol = 1250
ldo2_vol = 3000
ldo3_vol = 2800
ldo4_vol = 2800
power_start = 0
storage_type = -1
find power_sply to end
fel key old mode
run key detect
no key found
no key input
dram_para_set start
dram_para_set end
[ 0.352]DRAM: 256 MiB
relocation Offset is: 05b19000
user_gpio config
user_gpio ok
DRV_DISP_Init: opened
[ 0.592]fetch script data boot_disp.output_type fail
[ 0.597]fetch script data boot_disp.output_mode fail
[ 0.602]fetch script data boot_disp.auto_hpd fail
[ 0.607]lcd0_para.lcd_used=0
workmode = 0
[ 0.612]NAND: NAND_UbootInit
NAND_UbootInit start
NB1 : enter NAND_LogicInit
nand : get id_number_ctl fail, 20019
nand : get CapacityLevel fail, 4fb9e3a5
not burn nand partition table!
NB1 : nftl num: 1
init nftl: 0
NB1 : NAND_LogicInit ok, result = 0x0
[ 1.073]sunxi flash init ok
fail to find part named env
Using default environment
In: serial
Out: serial
Err: serial
--------fastboot partitions--------
-total partitions:3-
-name- -start- -size-
boot : 1000000 1000000
rootfs : 2000000 7000000
UDISK : 9000000 0
-----------------------------------
base bootcmd=run setargs_nand boot_normal
bootcmd set setargs_nand
key 0
recovery key high 6, low 4
cant find fstbt value
no misc partition is found
to be run cmd=run setargs_nand boot_normal
the part isn't exist
board_status_probe
[ 1.130]pre sys mode
[ 1.132]Hit any key to stop autoboot: 0
read boot or recovery all
[ 1.855]sunxi flash read :offset 1000000, 11548769 bytes OK
[ 1.870]ready to boot
[ 1.872][mmc]: MMC Device 2 not found
[ 1.876][mmc]: mmc not find,so not exit
NAND_UbootExit
NB1 : NAND_LogicExit
[ 1.880]
Starting kernel ...
[ 1.061206] [hdmi]hdmi module init
[ 1.066465] ##fb init:w=1280,h=720,fbmode=0
root=/dev/nandb
insmod nand.ko return 0
e2fsck /dev/nandb return 0
mount /dev/nandb return 0
RedQuark One
and if I interrupt the boot, and type printenv, I get the following...
redquark#printenv
baudrate=115200
boot_fastboot=fastboot
boot_normal=sunxi_flash read 40007800 boot;boota 40007800
boot_recovery=sunxi_flash read 40007800 recovery;boota 40007800
bootcmd=run setargs_nand boot_normal
bootdelay=3
console=ttyS0,115200
fastboot_key_value_max=0x8
fastboot_key_value_min=0x2
init=/init
loglevel=8
nand_root=/dev/nandb
partitions=boot@nanda:rootfs@nandb:UDISK@nandc
recovery_key_value_max=0x13
recovery_key_value_min=0x10
setargs_nand=setenv bootargs console=${console} root=${nand_root} init=${init} loglevel=${loglevel} partitions=${partitions} mem=256M quiet
stderr=serial
stdin=serial
stdout=serial
Environment size: 651/131068 bytes
Is this different from other peoples?
|
|
|
|
Post by jj0 on May 11, 2018 20:43:52 GMT
Does anyone have any ideas for removing the need for the serial connection after the software is copied to usb? I have been tempted to try to substitute the serial adaptor with an arduino, have it monitor the serial output, interrupt it and send the command to boot from usb. Not sure how well it would work though. Unless any linux users know how to permanently change the boot path to the usb? As we can't access the u-boot section of the nand (it isn't exposed by the nand.ko driver) we can't change the default nand_root. However you can make it somewhat easier. The following method remounts the /usr/share/the64
/var/lib/the64directories from the ones on the nand to the ones on the USB stick root filesystem. If the USB stick isn't inserted at boot time then the ones on the nand will still be used. You need to have the USB stick inserted before powering on and you can only remove it after you've powered off. So you lose the option to remove the USB stick on the fly to change the THEC64-drive8.d64. Step 1: Copy the nandb root filesystem to a USB stick partition 2 as covered in the first post. You don't actually need the entire root filesystem, only the two thec64 directories and their subdirectories, so if you're feeling adventurous you can only copy these and modify the following instructions accordingly. Step 2: Login as root and create a directory to mount the 2nd partition on: mount -o remount,rw /
mkdir /mnt2Step 3: Edit /etc/fstab, adding the red lines: # <file system> <mount pt> <type> <options> <dump> <pass>
/dev/root / ext2 rw,noauto 0 1
/dev/sda2 /mnt2 ext4 rw,nofail 0 0
/mnt2/usr/share/the64 /usr/share/the64 none bind,nofail 0 0
/mnt2/var/lib/the64 /var/lib/the64 none bind,nofail 0 0
proc /proc proc defaults 0 0
devpts /dev/pts devpts defaults,gid=5,mode=620 0 0
tmpfs /dev/shm tmpfs mode=0777 0 0
tmpfs /tmp tmpfs mode=1777 0 0
tmpfs /run tmpfs mode=0755,nosuid,nodev 0 0
sysfs /sys sysfs defaults 0 0
They don't need to be where I put them, the can also be at the end so you could add them by: cat >>/etc/fstab
<ENTER>
/dev/sda2 /mnt2 ext4 rw,nofail 0 0
/mnt2/usr/share/the64 /usr/share/the64 none bind,nofail 0 0
/mnt2/var/lib/the64 /var/lib/the64 none bind,nofail 0 0
<CTRL-D>but please make a backup of /etc/fstab first. Step 4: Add an /etc/init.d startup script to ensure the directories are mounted: cat >/etc/init.d/S98mountusb
mount -a
<CTRL>-D
chmod a+x /etc/init.d/S98mountusbEdit 16th May: The above works fine but more properly should be: cat >/etc/init.d/S98mountusb
#!/bin/sh
mount -a
<CTRL>-D
chmod a+x /etc/init.d/S98mountusbYou could even try if this works from a FAT32 partition which would make it easier to add game snapshots from Windows |
|
|
|
Post by jj0 on May 11, 2018 20:46:58 GMT
OK, I seem to have killed something, I can boot from USB no problem, but when I boot normally I just get a black screen. Here is my serial output...
and if I interrupt the boot, and type printenv, I get the following...
Is this different from other peoples? It looks the same to me except for an probably unimportant difference. I have: nand : get id_number_ctl fail, c0003
nand : get CapacityLevel fail, 4fb9e361
Do you still get a login prompt? If you login can you start the64 manually? What happens if you boot from the USB stick? |
|
|
|
Post by spinal on May 12, 2018 18:16:01 GMT
booting from usb stick works fine. How would I start the64 manually? from prompt?
- I have nanda, nandb and nandc backed up. Can I restore them somehow?
Trying to run the64 from promt gives the following -
# the64
Init base system
Error: eglInitialize() failed
Error: failed to create program!
|
|
|
|
Post by jj0 on May 12, 2018 19:23:21 GMT
booting from usb stick works fine. How would I start the64 manually? from prompt? - I have nanda, nandb and nandc backed up. Can I restore them somehow? Trying to run the64 from promt gives the following -
# the64
Init base system
Error: eglInitialize() failed
Error: failed to create program!
Well you could start a lengthy troubleshooting process, the 'Error: eglInitialize() failed' has something to do with the graphics. So maybe you inadvertently removed some graphics libraries You could compare the directories and files on your USB stick to what's on the nandb root. You might even discover something new! You could also do an 'lsmod' and see if the mali module is loaded. But the easiest way would be to restore nandb from your backup. Just boot from the USB stick (with a copy of nandb on it in the / directory). Then load the the nand driver and copy the nand backup over the entire nandb: insmod /lib/modules/3.4.39/nand.ko
dd if=/nandb of=/dev/nandb
syncThen you can reboot and check if this resolves the problem. It's probably wise to make a backup of your USB stick first. And maybe also of your current nandb. Note I haven't actually tried this myself so it is at your own risk... |
|
|
|
Post by spinal on May 13, 2018 10:31:21 GMT
mali is listed but used by 0, on usb though, it's used by 5.
OK, fixed...
Having almost no clue how to use linux at all, I guessed.
Having used the following to backup the nandb file system to my (still working) usb drive -
dd if=/dev/nandb of=/dev/sda2
And as I could boot from the USB drive without any issues I simply reversed the process...
dd if=/dev/sda2 of=/dev/nandb
Now my C64 boots again, with the slight difference that one of the game covers is upside down, I switched it so I could tell if usb booting had truly worked :-P
|
|
|
|
Post by ch1ller on May 13, 2018 22:34:34 GMT
To add e.g. the much-coveted Speedlink Pro, add the following line to /usr/share/the64/ui/data/gamecontrollerdb.txt:
030000000b0400003365000000010000,Speed-Link Competition Pro,a:b1,b:b5,x:b6,y:b7,back:b3,start:b2,lefttrigger:b0,righttrigger:b4,leftx:a0,lefty:a1,platform:Linux,
Thx Dude Just found a Speedlink-USB in one of my Cupboards *g* Totally forgot i had that one... |
|
|
|
Post by spinal on May 15, 2018 10:00:11 GMT
Can someone explain how the joystick mappings work? I'm finding it confusing as hell trying to create a joystick manually. I can only assume that tha,b,x,y,back,start etc map to xbox controller buttons, but then how do I translate this to a non-xbox controller that I only have button numbers for?
My DIY joystick has up,down,left,right working fine, but when it comes to buttons 1,2,3,4,5,6,7,8 I can not for the life of me figure out how to map them correctly.
|
|
|
|
Post by spinal on May 15, 2018 10:40:35 GMT
Does anyone have any ideas for removing the need for the serial connection after the software is copied to usb? I have been tempted to try to substitute the serial adaptor with an arduino, have it monitor the serial output, interrupt it and send the command to boot from usb. Not sure how well it would work though. Unless any linux users know how to permanently change the boot path to the usb? As we can't access the u-boot section of the nand (it isn't exposed by the nand.ko driver) we can't change the default nand_root. However you can make it somewhat easier. The following method remounts the /usr/share/the64
/var/lib/the64directories from the ones on the nand to the ones on the USB stick root filesystem. If the USB stick isn't inserted at boot time then the ones on the nand will still be used. You need to have the USB stick inserted before powering on and you can only remove it after you've powered off. So you lose the option to remove the USB stick on the fly to change the THEC64-drive8.d64. Step 1: Copy the nandb root filesystem to a USB stick partition 2 as covered in the first post. You don't actually need the entire root filesystem, only the two thec64 directories and their subdirectories, so if you're feeling adventurous you can only copy these and modify the following instructions accordingly. Step 2: Login as root and create a directory to mount the 2nd partition on: mount -o remount,rw /
mkdir /mnt2Step 3: Edit /etc/fstab, adding the red lines: # <file system> <mount pt> <type> <options> <dump> <pass>
/dev/root / ext2 rw,noauto 0 1
/dev/sda2 /mnt2 ext4 rw,nofail 0 0
/mnt2/usr/share/the64 /usr/share/the64 none bind,nofail 0 0
/mnt2/var/lib/the64 /var/lib/the64 none bind,nofail 0 0
proc /proc proc defaults 0 0
devpts /dev/pts devpts defaults,gid=5,mode=620 0 0
tmpfs /dev/shm tmpfs mode=0777 0 0
tmpfs /tmp tmpfs mode=1777 0 0
tmpfs /run tmpfs mode=0755,nosuid,nodev 0 0
sysfs /sys sysfs defaults 0 0
They don't need to be where I put them, the can also be at the end so you could add them by: cat >>/etc/fstab
<ENTER>
/dev/sda2 /mnt2 ext4 rw,nofail 0 0
/mnt2/usr/share/the64 /usr/share/the64 none bind,nofail 0 0
/mnt2/var/lib/the64 /var/lib/the64 none bind,nofail 0 0
<CTRL-D>but please make a backup of /etc/fstab first. Step 4: Add an /etc/init.d startup script to ensure the directories are mounted: cat >/etc/init.d/S98mountusb
mount -a
<CTRL>-D
chmod a+x /etc/init.d/S98mountusbYou could even try if this works from a FAT32 partition which would make it easier to add game snapshots from Windows That doesn't seem to have worked.
redquarkone login: +HELLO! BOOT0 is starting!
boot0 version : 3.0.0
dram size =256
current block is 2 and last block is 10.
current block is 3 and last block is 10.
current block is 4 and last block is 10.
current block is 5 and last block is 10.
current block is 6 and last block is 10.
current block is 7 and last block is 10.
sum=0x4c7f5fd3
src_sum=0x4c7f5fd3
The file stored in start block 2 is perfect.
Ready to disable icache.
Jump to secend Boot.
[ 0.179]
U-Boot 2011.09-rc1 (Dec 10 2017 - 17:25:12) Retro Games Ltd
[ 0.186]version: 1.1.0
[ 0.189]pmbus: ready
[ 0.294]PMU: AXP209
[ 0.297]PMU: AXP20x found
[ 0.300]PMU: bat ratio = 100
[ 0.303]after set, dcdc2 =1400mv
[ 0.307]PMU: dcdc2 1400
[ 0.309]PMU: pll1 912 Mhz
boot_clock = 912
dcdc2_vol = 1400
[ 0.317]after set, dcdc2 =1400mv
dcdc3_vol = 1250
ldo2_vol = 3000
ldo3_vol = 2800
ldo4_vol = 2800
power_start = 0
storage_type = -1
find power_sply to end
fel key old mode
run key detect
no key found
no key input
dram_para_set start
dram_para_set end
[ 0.352]DRAM: 256 MiB
relocation Offset is: 05b19000
user_gpio config
user_gpio ok
DRV_DISP_Init: opened
[ 0.592]fetch script data boot_disp.output_type fail
[ 0.597]fetch script data boot_disp.output_mode fail
[ 0.602]fetch script data boot_disp.auto_hpd fail
[ 0.607]lcd0_para.lcd_used=0
workmode = 0
[ 0.612]NAND: NAND_UbootInit
NAND_UbootInit start
NB1 : enter NAND_LogicInit
nand : get id_number_ctl fail, 20019
nand : get CapacityLevel fail, 4fb9e3a5
not burn nand partition table!
NB1 : nftl num: 1
init nftl: 0
NB1 : NAND_LogicInit ok, result = 0x0
[ 1.171]sunxi flash init ok
fail to find part named env
Using default environment
In: serial
Out: serial
Err: serial
--------fastboot partitions--------
-total partitions:3-
-name- -start- -size-
boot : 1000000 1000000
rootfs : 2000000 7000000
UDISK : 9000000 0
-----------------------------------
base bootcmd=run setargs_nand boot_normal
bootcmd set setargs_nand
key 0
recovery key high 6, low 4
cant find fstbt value
no misc partition is found
to be run cmd=run setargs_nand boot_normal
the part isn't exist
board_status_probe
[ 1.228]pre sys mode
[ 1.230]Hit any key to stop autoboot: 0
read boot or recovery all
[ 1.953]sunxi flash read :offset 1000000, 11548769 bytes OK
[ 1.968]ready to boot
[ 1.970][mmc]: MMC Device 2 not found
[ 1.974][mmc]: mmc not find,so not exit
NAND_UbootExit
NB1 : NAND_LogicExit
[ 1.978]
Starting kernel ...
[ 1.061628] [hdmi]hdmi module init
[ 1.066881] ##fb init:w=1280,h=720,fbmode=0
root=/dev/nandb
insmod nand.ko return 0
e2fsck /dev/nandb return 0
mount /dev/nandb return 0
RedQuark One
redquarkone login:
I followed your steps exactly. |
|
|
|
Post by jj0 on May 15, 2018 10:58:07 GMT
If you login and type 'mount' do you see any mounts to /mnt2?
|
|
|
|
Post by streuti on May 15, 2018 16:05:52 GMT
To add e.g. the much-coveted Speedlink Pro, add the following line to /usr/share/the64/ui/data/gamecontrollerdb.txt:
030000000b0400003365000000010000,Speed-Link Competition Pro,a:b1,b:b5,x:b6,y:b7,back:b3,start:b2,lefttrigger:b0,righttrigger:b4,leftx:a0,lefty:a1,platform:Linux,
Thx Dude Just found a Speedlink-USB in one of my Cupboards *g* Totally forgot i had that one... I don't know much about Linux. I bought the PL2303HX and successfully connected the c64 Mini to the notebook. Thanks for the Fantastic Guides here. My Speedlink Competition Pro also works now after adding the line above. And I successfully added commodore International Soccer (for me a must have) to the carousel. Now here's my first question: I don't play most of the games of the carousel. Would the C64 Mini blame me if I delete completely the carousel games and exchange them for others? What problems should I expect? Second question: Can I permanently switch off this annoying background music by modifying the Firmware. |
|
|
|
Post by spinal on May 15, 2018 16:20:52 GMT
If you login and type 'mount' do you see any mounts to /mnt2? Nope...
login[738]: root login on 'ttyS0'
# mount
rootfs on / type rootfs (rw)
none on /dev type devtmpfs (rw,relatime,size=51708k,nr_inodes=12927,mode=755)
proc on /proc type proc (rw,relatime)
/dev/nandb on / type ext4 (ro,noatime,nodiratime,nobarrier,noauto_da_alloc,data=ordered)
proc on /proc type proc (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw,relatime,mode=777)
tmpfs on /tmp type tmpfs (rw,relatime)
tmpfs on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
sysfs on /sys type sysfs (rw,relatime)
|
|
|
|
Post by jj0 on May 15, 2018 16:28:04 GMT
Thx Dude Just found a Speedlink-USB in one of my Cupboards *g* Totally forgot i had that one... I don't know much about Linux. I bought the PL2303HX and successfully connected the c64 Mini to the notebook. Thanks for the Fantastic Guides here. My Speedlink Competition Pro also works now after adding the line above. And I successfully added commodore International Soccer (for me a must have) to the carousel. Now here's my first question: I don't play most of the games of the carousel. Would the C64 Mini blame me if I delete completely the carousel games and exchange them for others? What problems should I expect? Second question: Can I permanently switch off this annoying background music by modifying the Firmware. You're welcome :-) You can safely remove any games you don't want to see in the carousel. I've actually removed most of the games. However each upgrade seems to create the .tgs files again so if you apply an upgrade you will need to remove the files again. For switching off the background music I would suggest creating or finding a small .wav file with silence and using that to replace the standard .wav file which (if I remember correctly is in the games/ui directory?). |
|
Jammet
Creatures
Coffee. ♪ Good.
Posts: 31
|
Post by Jammet on May 15, 2018 23:15:36 GMT
I think when you plug in generic gamepads and configure them in Windows 10, checking their properties, you can press buttons on them, and the OS will tell you what number the button is.
Alternatively you can find out what hid it is, in the usb of /dev, and cat /dev/thatdevice while pressing buttons to see what they do.
|
|
|
|
Post by streuti on May 16, 2018 5:08:21 GMT
Can someone explain how the joystick mappings work? I'm finding it confusing as hell trying to create a joystick manually. I can only assume that tha,b,x,y,back,start etc map to xbox controller buttons, but then how do I translate this to a non-xbox controller that I only have button numbers for? My DIY joystick has up,down,left,right working fine, but when it comes to buttons 1,2,3,4,5,6,7,8 I can not for the life of me figure out how to map them correctly. Maybe someone can start a post including a collection of needed different Joystick Mappings. |
|
|
|
Post by jj0 on May 16, 2018 18:21:15 GMT
If you login and type 'mount' do you see any mounts to /mnt2? Nope...
login[738]: root login on 'ttyS0'
# mount
rootfs on / type rootfs (rw)
none on /dev type devtmpfs (rw,relatime,size=51708k,nr_inodes=12927,mode=755)
proc on /proc type proc (rw,relatime)
/dev/nandb on / type ext4 (ro,noatime,nodiratime,nobarrier,noauto_da_alloc,data=ordered)
proc on /proc type proc (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw,relatime,mode=777)
tmpfs on /tmp type tmpfs (rw,relatime)
tmpfs on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
sysfs on /sys type sysfs (rw,relatime)
Hmmm... Some other things to check: - Is the USB stick inserted directly into ta USB port of he C64Mini? If I use a USB hub it doesn't work. - Is it the only USB stick inserted, otherwise it might not be /dev/sda - What are the partitions on the USB stick? # fdisk -l /dev/sd?
Disk /dev/sda: 30.7 GB, 30752000000 bytes
64 heads, 32 sectors/track, 29327 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Device Boot Start End Blocks Id System
/dev/sda1 2 3341 3420160 c Win95 FAT32 (LBA)
Partition 1 does not end on cylinder boundary
/dev/sda2 3342 29328 26610066 83 Linux
Partition 2 does not end on cylinder boundary
- What does fstab look like, assuming you use the 2nd partition on the USB stick and have copied nandb to it it should be like: # cat /etc/fstab
# <file system> <mount pt> <type> <options> <dump> <pass>
/dev/root / ext2 rw,noauto 0 1
/dev/sda2 /mnt2 ext4 rw,nofail 0 0
/mnt2/usr/share/the64 /usr/share/the64 none bind,nofail 0 0
/mnt2/var/lib/the64 /var/lib/the64 none bind,nofail 0 0
proc /proc proc defaults 0 0
devpts /dev/pts devpts defaults,gid=5,mode=620 0 0
tmpfs /dev/shm tmpfs mode=0777 0 0
tmpfs /tmp tmpfs mode=1777 0 0
tmpfs /run tmpfs mode=0755,nosuid,nodev 0 0
sysfs /sys sysfs defaults 0 0
- Does the mnt2 directory exist?: # ls -lisa / | grep mnt
183 4 drwxr-xr-x 2 root root 4096 Jun 24 2017 mnt
2 4 drwxr-xr-x 18 root root 4096 Jan 1 00:02 mnt2
- Does the S98mountusb script exist and is it executable? # ls -lisa /etc/init.d/S98*
1214 4 -rwxr-xr-x 1 root root 65 Jan 1 2000 /etc/init.d/S98mountusb
# cat /etc/init.d/S98mountusb
mount -a
- What happens if you do a manual mount? # mount -a
# mount
rootfs on / type rootfs (rw)
none on /dev type devtmpfs (rw,relatime,size=51708k,nr_inodes=12927,mode=755)
proc on /proc type proc (rw,relatime)
/dev/nandb on / type ext4 (rw,noatime,nodiratime,nobarrier,noauto_da_alloc,data=ordered)
proc on /proc type proc (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw,relatime,mode=777)
tmpfs on /tmp type tmpfs (rw,relatime)
tmpfs on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
sysfs on /sys type sysfs (rw,relatime)
/dev/sda2 on /mnt2 type ext4 (rw,relatime,data=ordered)
/dev/sda2 on /usr/share/the64 type ext4 (rw,relatime,data=ordered)
/dev/sda2 on /var/lib/the64 type ext4 (rw,relatime,data=ordered)
That's about all I can think of right now. |
|
huijaa
Creatures
Now I have two TheC64Mini!
Posts: 11
|
Post by huijaa on May 16, 2018 18:47:05 GMT
Here is the controllers from the gamecontrollerdb.txt file on the mini. I got this file about gamecontrollerdb.txt. Just i can research it. I must have to mod my C64Mini to change gamecontrollerdb.txt for my USB Gamepad Ninento SNES Controller. |
|
|
|
Post by spinal on May 16, 2018 20:49:09 GMT
Hmmm... Some other things to check: - Is the USB stick inserted directly into ta USB port of he C64Mini? If I use a USB hub it doesn't work. - Is it the only USB stick inserted, otherwise it might not be /dev/sda - What are the partitions on the USB stick? - USB stick directly - Yes - Only USB stick - Yes - Partitions --
# fdisk -l /dev/sd?
Disk /dev/sda: 15.5 GB, 15514730496 bytes
255 heads, 63 sectors/track, 1886 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 1828 14678586 b Win95 FAT32
/dev/sda2 * 1828 1887 472064 83 Linux
- What does fstab look like
# cat /etc/fstab
# <file system> <mount pt> <type> <options> <dump> <pass>
/dev/root / ext2 rw,noauto 0 1
proc /proc proc defaults 0 0
devpts /dev/pts devpts defaults,gid=5,mode=620 0 0
tmpfs /dev/shm tmpfs mode=0777 0 0
tmpfs /tmp tmpfs mode=1777 0 0
tmpfs /run tmpfs mode=0755,nosuid,nodev 0 0
sysfs /sys sysfs defaults 0 0
/dev/sda2 /mnt2 ext4 rw,nofail 0 0
/mnt2/usr/share/the64 /usr/share/the64 none bind,nofail 0 0
/mnt2/var/lib/the64 /var/lib/the64 none bind,nofail 0 0
/dev/sda2 /mnt2 ext4 rw,nofail 0 0
/mnt2/usr/share/the64 /usr/share/the64 none bind,nofail 0 0
/mnt2/var/lib/the64 /var/lib/the64 none bind,nofail 0 0
#
- Does the mnt2 directory exist?:
# ls -lisa / | grep mnt
185 4 drwxr-xr-x 2 root root 4096 Jun 24 2017 mnt
1261 4 drwxr-xr-x 2 root root 4096 Jan 1 00:00 mnt2
#
- Does the S98mountusb script exist and is it executable?
# ls -lisa /etc/init.d/S98*
1262 0 -rwxr-xr-x 1 root root 0 Jan 1 00:01 /etc/ini t.d/S98mountusb
#
I tried to redo the last part of your guid again and got this -
# cat >/etc/init.d/S98mountusb
-sh: can't create /etc/init.d/S98mountusb: Read-only file system
#
|
|
|
|
Post by darbyram on May 16, 2018 20:58:45 GMT
Spinal..cant you not make it writable? then try cat >/etc/init.d/S98mountusb
|
|
|
|
Post by jj0 on May 16, 2018 21:23:52 GMT
Spinal..cant you not make it writable? then try cat >/etc/init.d/S98mountusb Exactly. Also, perhaps do a 'killall -9 the64' to ensure the emulator isn't running and maybe making the filesystem readonly again. |
|
|
|
Post by spinal on May 17, 2018 5:43:47 GMT
killall: bad signal name ''
|
|
|
|
Post by ch1ller on May 17, 2018 8:41:33 GMT
Can someone explain how the joystick mappings work? I'm finding it confusing as hell trying to create a joystick manually. I can only assume that tha,b,x,y,back,start etc map to xbox controller buttons, but then how do I translate this to a non-xbox controller that I only have button numbers for? My DIY joystick has up,down,left,right working fine, but when it comes to buttons 1,2,3,4,5,6,7,8 I can not for the life of me figure out how to map them correctly. Have a look here: thec64community.online/post/592/threadAnd If you do not know which button has which value, you can connect it to a Windows PC and look up the GameController settings. Very important .. Under Linux, the value is one lower. If it shows button 3 then it's button 2 (b2).  |
|
|
|
Post by spinal on May 17, 2018 9:13:22 GMT
Can someone explain how the joystick mappings work? I'm finding it confusing as hell trying to create a joystick manually. I can only assume that tha,b,x,y,back,start etc map to xbox controller buttons, but then how do I translate this to a non-xbox controller that I only have button numbers for? My DIY joystick has up,down,left,right working fine, but when it comes to buttons 1,2,3,4,5,6,7,8 I can not for the life of me figure out how to map them correctly. Have a look here: thec64community.online/post/592/threadAnd If you do not know which button has which value, you can connect it to a Windows PC and look up the GameController settings. Very important .. Under Linux, the value is one lower. If it shows button 3 then it's button 2 (b2). Would you believe, it was my coding on the joystick end, rather than on the c64 end. I have it all sorted out now. At some point, I'll add a post about adding a c64 zipstick to the c64mini, with only minor soldering and a cheap arduino clone. |
|
