Cumulative repo for Slacware ARM

sndwvs · 07-21-2024, 05:52 AM

Quote:

Originally Posted by saxa

Hi @sndwvs , many thanks. Is this an already installed image ? If so I will have a try also , many thanks.

yes, this is a pre-installed system.

glorsplitz · 07-21-2024, 09:07 AM

just curious, anyone know, lemaker is defunct, this looks like successor ?

sndwvs · 07-21-2024, 09:32 AM

Quote:

Originally Posted by glorsplitz

just curious, anyone know, lemaker is defunct, this looks like successor ?

yes, bananpi.org (SinoVoip Co.) is the official website, this is the official store.

drmozes · 07-21-2024, 12:14 PM

Quote:

Originally Posted by saxa

Hi @glorsplitz, ok I got your point, I should recheck these setenv parameters I set up. I.

In addition to the Kernel cmdline settings, you need to configure U-Boot to load the FTD, Kernel and initrd from the MMC.

See section '5.0 Booting the Slackware ARM OS' of the installation guide: your system seems to be configured to boot from USB, so you need to edit those settings and use mmc instead (or whatever U-boot refers to the MMC as, if it's not 'mmc' - your previous log files from the 14.2 installation probably have the correct settings contained within them), and ensure you have it pointing to the correct partition on the MMC as well (e.g. 0:2).
Once you've edited the bootcmd_dtb and bootcmd_slk variables, saveenv and reset. You'll get there eventually ;-)

saxa · 07-21-2024, 02:48 PM

@drmozes, ok so I wrongly tought that mmc is usb. Thanks for the tips, will try few things and hopefully succeed.

saxa · 07-22-2024, 02:00 AM

Hi, ok I got it to boot by adjusting the 2 lines below, but now I still got an error as seems it does not found the / partition. and kernel panics at the end.
Do I have to recreate the initrd maybe ?

Code:

setenv bootcmd_dtb 'ext4load mmc 0:2 ${fdt_addr} /boot/dtb/${DTB} ; fdt addr ${fdt_addr} 0x40000'
setenv bootcmd_slk 'mmc reset;mmc reset;mmc scan ; run bootcmd_dtb ; ext4load mmc 0:2 ${kernel_addr_r} /boot/zImage-armv7 ; ext4load mmc 0:2 ${ramdisk_addr_r} /boot/initrd-armv7'
saveenv ; reset

Is this because the initrd points to some other location ?

Any idea on how to solve this ?

drmozes · 07-22-2024, 02:52 AM

Quote:

Originally Posted by saxa

Hi, ok I got it to boot by adjusting the 2 lines below, but now I still got an error as seems it does not found the / partition. and kernel panics at the end.
Do I have to recreate the initrd maybe ?

Code:

setenv bootcmd_dtb 'ext4load mmc 0:2 ${fdt_addr} /boot/dtb/${DTB} ; fdt addr ${fdt_addr} 0x40000'
setenv bootcmd_slk 'mmc reset;mmc reset;mmc scan ; run bootcmd_dtb ; ext4load mmc 0:2 ${kernel_addr_r} /boot/zImage-armv7 ; ext4load mmc 0:2 ${ramdisk_addr_r} /boot/initrd-armv7'
saveenv ; reset

Is this because the initrd points to some other location ?

Any idea on how to solve this ?

You can remove 'mmc reset' since it the mmc command doesn't take 'reset' as a parameter. The resetting was for the SCSI and USB buses, since U-Boot often failed whilst the storage was busy spinning up.

In the U-Boot config you should change the 'root=' boot configuration to 'root=LABEL=SLKroot' and savenv again - it'll probably work then.

If not, you will need to add 'slkpbs' (without quotes) to the U-Boot 'bootargs' variable, saveenv and boot again.
It'll boot into the preboot shell. Exit stages 1 & 2 and poke around the system at stage 3. If you can figure out what's wrong with it, you can fix it up there and then exit stage 3 into the OS.

saxa · 07-22-2024, 03:13 AM

Ok, I modified as per your suggestion, if I got it correctly. But unfortunately I end up still without a finished boot.

See attached log.

drmozes · 07-22-2024, 04:34 AM

Quote:

Originally Posted by saxa

Ok, I modified as per your suggestion, if I got it correctly. But unfortunately I end up still without a finished boot.

See attached log.

Add slkpbs to the Kernel cmdline, quit stage 1 and poke around stage 2 and see if you can find whether /dev/mmcblk* exists.
In the previous message I said there were 3 stages -- but not in the version of the module loader contained within the original Kernel package (the kernel in /patches contains a later version)

It may be that the module required to support mmc on the Banana Pi simply isn't loaded, so you can modprobe it.

saxa · 07-22-2024, 05:22 AM

Excuse my ignorance, what exactly is slkpbs ? I simply add this as a parameter or how ?
If I run the installer I can see 2 partitions with fdisk -l one /dev/mmcblk0p1 and /dev/mmcblk0p2.

About stage 1,2 or 3 how they are defined ? Stage 1 is after pressing the power button, stage 2 is what exactly ?

drmozes · 07-22-2024, 05:43 AM

Quote:

Originally Posted by saxa

Excuse my ignorance, what exactly is slkpbs ?

Slackware pre-boot shell. It's just a way to open a shell within the OS initrd for troubleshooting and development.

At the u-boot console:

Quote:

I simply add this as a parameter or how ?

Code:

setenv bootargs "${slkconsole} ${bootcmd_generic} root=LABEL=SLKroot waitforroot=3 rootfstype=ext4 slkpbs"
saveenv;reset

Quote:

About stage 1,2 or 3 how they are defined ? Stage 1 is after pressing the power button, stage 2 is what exactly ?

You can read about it here.

saxa · 07-22-2024, 06:51 AM

@drmozes, ok all clear thanks, but how do I view the contents of the files in there ? I never used ash. Is there some kind of cat or similar command ?
How am I supposed to see something in the files ?

drmozes · 07-22-2024, 08:08 AM

Quote:

Originally Posted by saxa

@drmozes, ok all clear thanks, but how do I view the contents of the files in there ? I never used ash. Is there some kind of cat or similar command ?
How am I supposed to see something in the files ?

The initrd is a small OS, similar to the installer but with a smaller tool set.
Just boot it with slkpbs and you'll see for yourself.

saxa · 07-22-2024, 08:47 AM

this is where I am right now:

Code:

[  386.795068] RPC: Registered named UNIX socket transport module.
[  386.801100] RPC: Registered udp transport module.
[  386.805835] RPC: Registered tcp transport module.
[  386.810560] RPC: Registered tcp NFSv4.1 backchannel transport module.
[  387.007321] FS-Cache: Netfs 'nfs' registered for caching
Stage 2 of 2: Post module loading
Development shell opening.
Exit shell to proceed to the next stage in the module loading
process.

Development shell opening
Module variables are prefixed with 'MOD_'
Note: You cannot edit the variables here, only view.

/bin/ash: can't access tty; job control turned off
Pre-boot shell (2/2): # 
Pre-boot shell (2/2): # ls
await_device             load_kernel_modules      rootdev
bin                      load_kernel_modules.scr  rootfs
dev                      luksdev                  run
etc                      lukskey                  sbin
init                     mnt                      sys
initrd-name              proc                     usr
keymap                   resumedev                wait-for-root
lib                      root
Pre-boot shell (2/2): # help
Built-in commands:
------------------
        . : [ [[ alias bg break cd chdir command continue echo eval exec
        exit export false fg getopts hash help history jobs kill let
        local printf pwd read readonly return set shift source test times
        trap true type ulimit umask unalias unset wait
Pre-boot shell (2/2): # exit
mdadm: No arrays found in config file or automatically
[  432.863867] urandom_read: 3 callbacks suppressed
[  432.863899] random: vgchange: uninitialized urandom read (4 bytes read)
mount: can't find /mnt in /etc/fstab
ERROR:  No /sbin/init found on rootdev (or not mounted).  Trouble ahead.
        You can try to fix it. Type 'exit' when things are done.

/bin/sh: can't access tty; job control turned off
/ # ls
await_device             load_kernel_modules      rootdev
bin                      load_kernel_modules.scr  rootfs
dev                      luksdev                  run
etc                      lukskey                  sbin
init                     mnt                      sys
initrd-name              proc                     usr
keymap                   resumedev                var
lib                      root                     wait-for-root
/ # help
Built-in commands:
------------------
        . : [ [[ alias bg break cd chdir command continue echo eval exec
        exit export false fg getopts hash help history jobs kill let
        local printf pwd read readonly return set shift source test times
        trap true type ulimit umask unalias unset wait
/ #

But to be honest I have no idea on how to inspect these files without a cat or some kind of editor command.

saxa · 07-22-2024, 08:52 AM

Ups, sorry, I see now I have a vim there