|
|
Post by darbyram on Jun 14, 2018 20:07:21 GMT
Did you go through the additional stuff after editing the fstab? not saying it will work as it did not for me.
cat >/etc/init.d/S98mountusb
#!/bin/sh
mount -a
<CTRL>-D
chmod a+x /etc/init.d/S98mountusb
I will try again myself this weekend to try and get it too work.
|
|
|
|
Post by spinal on Jun 15, 2018 6:28:22 GMT
Did you go through the additional stuff after editing the fstab? not saying it will work as it did not for me. cat >/etc/init.d/S98mountusb #!/bin/sh mount -a <CTRL>-D chmod a+x /etc/init.d/S98mountusb I will try again myself this weekend to try and get it too work. It will boot from ext4 fine, but it's a complete pain to work with on windows. Only fat32 wont work. |
|
|
|
Post by jj0 on Jun 17, 2018 12:39:35 GMT
Did you go through the additional stuff after editing the fstab? not saying it will work as it did not for me. cat >/etc/init.d/S98mountusb #!/bin/sh mount -a <CTRL>-D chmod a+x /etc/init.d/S98mountusb I will try again myself this weekend to try and get it too work. Try a 'mount -a' at the commandline, see if it gives an error message. |
|
|
|
Post by darbyram on Jun 17, 2018 21:50:45 GMT
No, for that you need /dev/sda1 /mnt2 vfat rw,nofail 0 0Doesn't work at all. Don't know if this reveals anything or not...
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.298]PMU: AXP20x found
[ 0.300]PMU: bat ratio = 100
[ 0.304]after set, dcdc2 =1400mv
[ 0.307]PMU: dcdc2 1400
[ 0.310]PMU: pll1 912 Mhz
boot_clock = 912
dcdc2_vol = 1400
[ 0.318]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
Hdmi_dvi_enable is NULL
Hdmi_get_input_csc is NULL
workmode = 0
[ 0.649]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.247]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.304]power trigger
[ 1.307]Hit any key to stop autoboot: 0
read boot or recovery all
[ 2.029]sunxi flash read :offset 1000000, 11548769 bytes OK
[ 2.044]ready to boot
[ 2.047][mmc]: MMC Device 2 not found
[ 2.050][mmc]: mmc not find,so not exit
NAND_UbootExit
NB1 : NAND_LogicExit
[ 2.055]
Starting kernel ...
[ 0.991157] rtc_hw_init(416) err: set clksrc to external losc failed! rtc time will be wrong
[ 1.000697] sunxi_rtc_gettime(34): err, losc_err_flag is 1
[ 1.075408] [hdmi]hdmi module init
[ 1.080972] ##fb init:w=1280,h=720,fbmode=0
[ 1.097391] sunxi_rtc_gettime(34): err, losc_err_flag is 1
[ 1.103714] sunxi-rtc sunxi-rtc: hctosys: unable to read the hardware clock
root=/dev/nandb
insmod nand.ko return 0
e2fsck /dev/nandb return 0
mount /dev/nandb return 0
RedQuark One
redquarkone login:
Wont work for me too Spinal, went back to ext4 and all is ok again. maybe its the usb device that may be the problem or how it is formatted? |
|
|
|
Post by jj0 on Jun 20, 2018 19:20:56 GMT
Wont work for me too Spinal, went back to ext4 and all is ok again. maybe its the usb device that may be the problem or how it is formatted? It would appear that there is no /dev/sda1, for some reason this is created by the64 in /tmp/usbdrive. However it is easily created in /dev:# ls -l /dev/sda*
brw-rw---- 1 root root 8, 0 Jan 1 00:08 /dev/sda
brw-rw---- 1 root root 8, 2 Jan 1 00:08 /dev/sda2
# mount -o remount,rw /
# mknod /dev/sda1 b 8 1
# ls -l /dev/sda*
brw-rw---- 1 root root 8, 0 Jan 1 00:08 /dev/sda
brw-r--r-- 1 root root 8, 1 Jan 1 00:07 /dev/sda1
brw-rw---- 1 root root 8, 2 Jan 1 00:08 /dev/sda2
# mount /dev/sda1 /mnt2
# ls /mnt2
usr
var
#
After this it should work. |
|
|
|
Post by darbyram on Jun 21, 2018 6:12:55 GMT
Wont work for me too Spinal, went back to ext4 and all is ok again. maybe its the usb device that may be the problem or how it is formatted? It would appear that there is no /dev/sda1, for some reason this is created by the64 in /tmp/usbdrive. However it is easily created in /dev: # ls -l /dev/sda*
brw-rw---- 1 root root 8, 0 Jan 1 00:08 /dev/sda
brw-rw---- 1 root root 8, 2 Jan 1 00:08 /dev/sda2
# mount -o remount,rw /
# mknod /dev/sda1 b 8 1
# ls -l /dev/sda*
brw-rw---- 1 root root 8, 0 Jan 1 00:08 /dev/sda
brw-r--r-- 1 root root 8, 1 Jan 1 00:07 /dev/sda1
brw-rw---- 1 root root 8, 2 Jan 1 00:08 /dev/sda2
# mount /dev/sda1 /mnt2
# ls /mnt2
usr
var
#
After this it should work. Getting this error.. # ls -l /dev/sda* brw-rw---- 1 root root 8, 0 Jan 1 1970 /dev/sda brw-r--r-- 1 root root 8, 1 Jan 1 1970 /dev/sda1 brw-rw---- 1 root root 8, 2 Jan 1 1970 /dev/sda2 # mount /dev/sda1 /mnt2 mount: mounting /dev/sda1 on /mnt2 failed: Invalid argument
# Any thoughts as to why? EDIT.... I remembered i messed a little with the fat format, put back to normal and all is good....Thankyou it works  |
|
|
|
Post by spinal on Jun 21, 2018 15:30:11 GMT
I get...
# ls -l /dev/sda*
brw-rw---- 1 root root 8, 0 Jan 1 1970 /dev/sda
brw-r--r-- 1 root root 8, 1 Jan 1 1970 /dev/sda1
brw-rw---- 1 root root 8, 2 Jan 1 00:02 /dev/sda2
brw-rw---- 1 root root 8, 5 Jan 1 1970 /dev/sda5
# mount /dev/sda1 /mnt2
mount: mounting /dev/sda1 on /mnt2 failed: No such file or directory
|
|
|
|
Post by jj0 on Jun 21, 2018 20:46:46 GMT
I get...
# ls -l /dev/sda*
brw-rw---- 1 root root 8, 0 Jan 1 1970 /dev/sda
brw-r--r-- 1 root root 8, 1 Jan 1 1970 /dev/sda1
brw-rw---- 1 root root 8, 2 Jan 1 00:02 /dev/sda2
brw-rw---- 1 root root 8, 5 Jan 1 1970 /dev/sda5
# mount /dev/sda1 /mnt2
mount: mounting /dev/sda1 on /mnt2 failed: No such file or directory
It's a bit surprising to see /dev/sda5. But 'No such file or directory' suggests that either the USB stick doesn't have a 1st partition or that /mnt2 doesn't exist. What do the following show? fdisk -l /dev/sda and ls -lisa /mnt* |
|
|
|
Post by spinal on Jun 22, 2018 6:36:50 GMT
# fdisk -l /dev/sda
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
# ls - lisa /mnt*
ls: -: No such file or directory
ls: lisa: No such file or directory
/mnt:
#
|
|
|
|
Post by jj0 on Jun 22, 2018 13:15:29 GMT
# fdisk -l /dev/sda
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
# ls - lisa /mnt*
ls: -: No such file or directory
ls: lisa: No such file or directory
/mnt:
#
Sorry, there shouldn't be a space between the '-' and the command options, my bloody autotype added a space after the '-' again :-(. So it's: fdisk -l /dev/sda and ls -lisa /mnt* However form the output you provided it looks like have no /mnt2 directory. This can be fixed by: mkdir /mnt2 |
|
|
|
Post by spinal on Jun 22, 2018 15:19:58 GMT
Still not working, I don't know if I missed a step or not...
# fdisk -l /dev/sda
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
#
# ls -lisa /mnt*
/mnt:
total 8
185 4 drwxr-xr-x 2 root root 4096 Jun 24 2017 .
2 4 drwxr-xr-x 20 root root 4096 Jan 1 1970 ..
/mnt2:
total 8
1262 4 drwxr-xr-x 2 root root 4096 Jan 1 1970 .
2 4 drwxr-xr-x 20 root root 4096 Jan 1 1970 ..
#
I think a start-to-finish tutorial is required...
|
|
|
|
Post by darbyram on Jun 22, 2018 20:27:23 GMT
Still not working, I don't know if I missed a step or not...
# fdisk -l /dev/sda
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
#
# ls -lisa /mnt*
/mnt:
total 8
185 4 drwxr-xr-x 2 root root 4096 Jun 24 2017 .
2 4 drwxr-xr-x 20 root root 4096 Jan 1 1970 ..
/mnt2:
total 8
1262 4 drwxr-xr-x 2 root root 4096 Jan 1 1970 .
2 4 drwxr-xr-x 20 root root 4096 Jan 1 1970 ..
#
I think a start-to-finish tutorial is required... Strange its not working. i just followed a through the original steps. try this mount -o remount, rw /killall -9 the64edit the fstab reflecting sda1. then.. cat >/etc/init.d/S98mountusb
#!/bin/sh
mount -a
<CTRL>-D
chmod a+x /etc/init.d/S98mountusb
mknod /dev/sda1 b 8 1
mount /dev/sda1 /mnt2
ls /mnt2
reboot |
|
|
|
Post by spinal on Jun 23, 2018 19:08:58 GMT
Strange its not working. i just followed a through the original steps. try this mount -o remount, rw /killall -9 the64edit the fstab reflecting sda1. then.. cat >/etc/init.d/S98mountusb
#!/bin/sh
mount -a
<CTRL>-D
chmod a+x /etc/init.d/S98mountusb
mknod /dev/sda1 b 8 1
mount /dev/sda1 /mnt2
ls /mnt2
reboot Perfect! (almost) Thanks. Only issue now is that the font doesn't load and it crashes when I try to exit a game. [edit] In fact, it crashes when I do anything other than load a game, menus crash. -- I have the full file list copied to my usb, not just the two required folders. |
|
|
|
Post by darbyram on Jun 23, 2018 20:28:41 GMT
Strange its not working. i just followed a through the original steps. try this mount -o remount, rw /killall -9 the64edit the fstab reflecting sda1. then.. cat >/etc/init.d/S98mountusb
#!/bin/sh
mount -a
<CTRL>-D
chmod a+x /etc/init.d/S98mountusb
mknod /dev/sda1 b 8 1
mount /dev/sda1 /mnt2
ls /mnt2
reboot Perfect! (almost) Thanks. Only issue now is that the font doesn't load and it crashes when I try to exit a game. [edit] In fact, it crashes when I do anything other than load a game, menus crash. -- I have the full file list copied to my usb, not just the two required folders. Not sure what would cause that. usb?, corrupted files? I just have the usr and var directories on mine |
|
|
|
Post by henkiepenkie on Jul 3, 2018 14:59:04 GMT
hi, after typing boot it ends with sd 0:0:0:0: [sda] Assuming drive cache: write through wait / ready. wait / ready. wait / ready. and this keeps going for ever. what did i do wrong  Here is a complete clip of what i did: HELLO! BOOT0 is starting!
boot0 version : 3.0.0
dram size =256
nand block 2 is bad
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.
current block is 8 and last block is 10.
sum=0x63c13c11
src_sum=0x63c13c11
The file stored in start block 3 is perfect.
Ready to disable icache.
Jump to secend Boot.
[ 0.180]
U-Boot 2011.09-rc1 (Apr 02 2018 - 11:17:04) Retro Games Ltd
[ 0.187]version: 1.1.0
[ 0.190]pmbus: ready
[ 0.295]PMU: AXP209
[ 0.298]PMU: AXP20x found
[ 0.301]PMU: bat ratio = 100
[ 0.304]after set, dcdc2 =1400mv
[ 0.308]PMU: dcdc2 1400
[ 0.310]PMU: pll1 912 Mhz
boot_clock = 912
dcdc2_vol = 1400
[ 0.318]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
0x73
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.593]fetch script data boot_disp.output_type fail
[ 0.598]fetch script data boot_disp.output_mode fail
[ 0.603]fetch script data boot_disp.auto_hpd fail
[ 0.608]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, c0003
nand : get CapacityLevel fail, 4fb9e371
not burn nand partition table!
NB1 : nftl num: 1
init nftl: 0
NB1 : NAND_LogicInit ok, result = 0x0
[ 0.855]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
[ 0.912]pre sys mode
[ 0.914]Hit any key to stop autoboot: 0
redquark#setenv nand_root / dev / sda
redquark#boot
read boot or recovery all
[ 56.709]sunxi flash read :offset 1000000, 11549374 bytes OK
[ 56.724]ready to boot
[ 56.727][mmc]: MMC Device 2 not found
[ 56.730][mmc]: mmc not find,so not exit
NAND_UbootExit
NB1 : NAND_LogicExit
[ 56.735]
Starting kernel ...
[ 0.991785] rtc_hw_init(416) err: set clksrc to external losc failed! rtc time will be wrong
[ 1.001453] sunxi_rtc_gettime(34): err, losc_err_flag is 1
[ 1.076353] [hdmi]hdmi module init
[ 1.081847] ##fb init:w=1280,h=720,fbmode=0
[ 1.098095] sunxi_rtc_gettime(34): err, losc_err_flag is 1
[ 1.105846] sunxi-rtc sunxi-rtc: hctosys: unable to read the hardware clock
root=/
wait / ready
wait / ready
wait / ready
[ 3.741499] sd 0:0:0:0: [sda] No Caching mode page present
[ 3.747617] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 3.758504] sd 0:0:0:0: [sda] No Caching mode page present
[ 3.764669] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 3.775878] sd 0:0:0:0: [sda] No Caching mode page present
[ 3.782039] sd 0:0:0:0: [sda] Assuming drive cache: write through
wait / ready
wait / ready
wait / ready
|
|
|
|
Post by jj0 on Jul 5, 2018 9:39:06 GMT
hi, after typing boot it ends with sd 0:0:0:0: [sda] Assuming drive cache: write through wait / ready. wait / ready. wait / ready. and this keeps going for ever. what did i do wrong <SNIP> redquark#setenv nand_root / dev / sda redquark#boot <SNIP> root=/ wait / ready wait / ready wait / ready Two things: You can see that it looks for root=/, not root=/dev/sda which is what you are trying to set nand_boot to. This is because you've used spaces after each /. Also, are you sure you actually mean /dev/sda? This can be OK if your entire USB-stick is a filesystem, but not if it has a partitiontable. Then it needs to be /dev/sda1 or /dev/sda2 or whatever partition you have prepared. |
|
|
|
Post by henkiepenkie on Jul 5, 2018 19:19:17 GMT
Ok i should have known that (ijust cop/pasted those lines from this page) Sorry for being an idiot, but now the next problem has come up. / # mount /dev/nandb/mnt mount: can't find /dev/nandb/mnt in /etc/fstab |
|
|
|
Post by darbyram on Jul 5, 2018 22:10:47 GMT
Ok i should have known that (ijust cop/pasted those lines from this page) Sorry for being an idiot, but now the next problem has come up. / # mount /dev/nandb/mnt mount: can't find /dev/nandb/mnt in /etc/fstab |
|
|
|
Post by henkiepenkie on Jul 6, 2018 17:23:23 GMT
ok, its obvious i've got no idea what i'm doing I wil have to get more familiar with linux. and maybe somebody could remove all the extra spaces in this guide haha. Thanx again. |
|
|
|
Post by mick157 on Jul 19, 2018 22:56:39 GMT
Hi guys, wondering if someone might be able to help. I'm following the steps and get stuck at entering a new root password. It seems like it already has one. Is there any probs with this method on the latest firmware? Is there anyway to reset the password? Any help would be much appreciated ☺ Attachments:
|
|
|
|
Post by darbyram on Jul 20, 2018 18:00:01 GMT
Hi guys, wondering if someone might be able to help. I'm following the steps and get stuck at entering a new root password. It seems like it already has one. Is there any probs with this method on the latest firmware? Is there anyway to reset the password? Any help would be much appreciated ☺ you need to interrupt the boot process by pressing "s" on your keyboard as you power the mini. |
|
|
|
Post by mick157 on Jul 20, 2018 22:27:00 GMT
Hi guys, wondering if someone might be able to help. I'm following the steps and get stuck at entering a new root password. It seems like it already has one. Is there any probs with this method on the latest firmware? Is there anyway to reset the password? Any help would be much appreciated ☺ you need to interrupt the boot process by pressing "s" on your keyboard as you power the mini. As you can see in the photo, I've done just that  It's logging in I'm having issues with. When it comes time to choose a password, I enter my choice and it says incorrect login. 😕 |
|
|
|
Post by jj0 on Jul 21, 2018 11:09:19 GMT
you need to interrupt the boot process by pressing "s" on your keyboard as you power the mini. As you can see in the photo, I've done just that It's logging in I'm having issues with. When it comes time to choose a password, I enter my choice and it says incorrect login. 😕 From the photo it looks like you are in the normal login prompt. If it tells you the password is incorrect even if earlier in the process you used the 'passwd' command to change it then the change didn't work. This could be because in the guide in the starting post some Linux commands that use directory names are written with a space after each '/' which isn't correct. E.g. setenv nand_root / dev / sdashould be setenv nand_root /dev/sda etcetera. So maybe you can try again taking this into account? I've PM'd @spannernick asdking him to edit the post. |
|
|
|
Post by mick157 on Jul 22, 2018 21:48:41 GMT
As you can see in the photo, I've done just that It's logging in I'm having issues with. When it comes time to choose a password, I enter my choice and it says incorrect login. 😕 From the photo it looks like you are in the normal login prompt. If it tells you the password is incorrect even if earlier in the process you used the 'passwd' command to change it then the change didn't work. This could be because in the guide in the starting post some Linux commands that use directory names are written with a space after each '/' which isn't correct. E.g. setenv nand_root / dev / sdashould be setenv nand_root /dev/sda etcetera. So maybe you can try again taking this into account? I've PM'd @spannernick asdking him to edit the post. Thanks jj0 but I didn't use spaces to begin with. I'd assumed they weren't supposed to be there. I'll have another shot at it today just incase I missed something in the guide. |
|
|
|
Post by mick157 on Jul 23, 2018 1:36:26 GMT
I think the password is set but it's saying it's incorrect when I try to log in. Is there some way to retrieve my login details? It's unlikely, but perhaps I've set an confirmed my password with a typo in it?
If I just wait until the next firmware update, will I be able to set a new root password again?
|
|
|
|
Post by jj0 on Jul 25, 2018 9:38:30 GMT
I think the password is set but it's saying it's incorrect when I try to log in. Is there some way to retrieve my login details? It's unlikely, but perhaps I've set an confirmed my password with a typo in it? If I just wait until the next firmware update, will I be able to set a new root password again? Previous firmware updates have only updated the emulator software and game files so it's likely a new firmware update will not change the password. It's still likely that something went wrong with the password change so your best bet is to try it again. |
|
|
|
Post by jj0 on Jul 25, 2018 10:10:18 GMT
I think the password is set but it's saying it's incorrect when I try to log in. Is there some way to retrieve my login details? It's unlikely, but perhaps I've set an confirmed my password with a typo in it? If I just wait until the next firmware update, will I be able to set a new root password again? Previous firmware updates have only updated the emulator software and game files so it's likely a new firmware update will not change the password. It's still likely that something went wrong with the password change so your best bet is to try it again. For some reason I keep getting blocked by Cloudflare when I add a step by step log to basically set an empty password. It seems to be triggered by using the pathname to the shadow file. So see below for a log of a slightly modified process that ends up with an empty root password. Except that where it says xxxxxx you have to type shadow.  The 'grep' lines are to check if the copy was successful. After stopping the boot process by pressing 's' type: redquark#setenv nand_root /dev/nanda
redquark#bootNote I use nanda instead of sda1, so you don't need to insert an USB drive. After the reboot copy the existing shadow file (which has an empty password for root) to nandb: # grep root /etc/xxxxxx
root::10933:0:99999:7:::
# mount /dev/nandb /mnt
59.075693 EXT4-fs (nandb): couldn't mount as ext3 due to feature incompatibilities
59.129630 EXT4-fs (nandb): couldn't mount as ext2 due to feature incompatibilities
# cp /etc/xxxxxx /mnt/etc/xxxxxx
# grep root /mnt/etc/xxxxxx
root::10933:0:99999:7:::
# umount /mnt
#Then after switching off and on you can just login as root without password:
RedQuark One redquarkone login: root
login726: root login on 'ttyS0'
# |
|
|
|
Post by gurce on Aug 4, 2018 11:48:04 GMT
Heya guys, I got my hands on a UART converter this week, so I'm giving these steps a try this weekend. Just as other users commented in prior posts, some of the extra white-spaces in the given steps are a little confusing, but I think I'll be savvy enough to figure the commands out, fingers crossed. And agreed, at some stage, the steps should be updated to remove the whitespaces. I think I can understand why spannernick won't be able to update these steps as yet, as I recall he got the power/gnd connections back-to-front and fried the comms connection, so he hasn't been able to give these steps a try and verify which spaces need to be removed where. So I'll log my steps as I go, in an effort to refine this document. I'll probably initially share the updated doc via the gurce.net/c64mini wiki, doing my best to credit one and all involved in the effort thus far. At some stage, we can push the content there to a public wiki hosted elsewhere if you like, so others in the community can contribute to updating such documents together. |
|
|
|
Post by gurce on Aug 4, 2018 13:37:55 GMT
Making slow, steady progress through the steps. I'm now at a stage where the penny is dropping that the walkthrough given here is for a path that will permanently add games to the nand flash. JJ mentioned there was an alternate path, of playing these extra games from the USB stick instead, he shared this link to another thread in here: thec64community.online/thread/4/modding-thec64-mini?page=7I'll mull over the steps there too, as it is the path I'm preferring. Thought I'd better cross-reference the link in here too, in-case others also prefer this path. |
|
|
|
Post by gurce on Aug 4, 2018 15:46:02 GMT
Wow, got it working, new games running off my usb stick! Thanks for all involved in sharing what you had: jj, chiller, spannernick and paolo (hope I didn't miss anyone! Oops, yep, I did, Stuart Duncan for sharing his initial findings on the linux-sunxi site, that seemed to get this whole ball rolling!) I'll try contribute some updated docs after I recover with some sleep!  |
|
