LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > slarm64
User Name
Password
slarm64 This forum is for the discussion of slarm64.

Notices


Reply
  Search this Thread
Old 06-07-2023, 12:10 PM   #16
sndwvs
Senior Member
 
Registered: Aug 2014
Posts: 1,966

Original Poster
Rep: Reputation: Disabled

Quote:
Originally Posted by SCerovec View Post
I tried to build it and it errs out that a clk comparison will always yield true in the build logs?
Am i of so bad luck to run it on a "update & break" day?
need error log
 
Old 06-07-2023, 03:22 PM   #17
SCerovec
Senior Member
 
Registered: Oct 2006
Location: Cp6uja
Distribution: Slackware on x86 and arm
Posts: 2,487
Blog Entries: 2

Rep: Reputation: 992Reputation: 992Reputation: 992Reputation: 992Reputation: 992Reputation: 992Reputation: 992Reputation: 992
Post

Quote:
Originally Posted by sndwvs View Post
need error log
There, it's as far as I've got...
Attached Files
File Type: log build.log (30.9 KB, 5 views)
 
Old 06-08-2023, 12:17 PM   #18
sndwvs
Senior Member
 
Registered: Aug 2014
Posts: 1,966

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by SCerovec View Post
There, it's as far as I've got...
fixed
 
1 members found this post helpful.
Old 06-09-2023, 02:18 AM   #19
SCerovec
Senior Member
 
Registered: Oct 2006
Location: Cp6uja
Distribution: Slackware on x86 and arm
Posts: 2,487
Blog Entries: 2

Rep: Reputation: 992Reputation: 992Reputation: 992Reputation: 992Reputation: 992Reputation: 992Reputation: 992Reputation: 992
Post

I was so close...

The img is some 3.3GB long?
Attached Files
File Type: log build.log (111.1 KB, 3 views)

Last edited by SCerovec; 06-09-2023 at 02:20 AM. Reason: error
 
Old 06-09-2023, 02:27 AM   #20
SCerovec
Senior Member
 
Registered: Oct 2006
Location: Cp6uja
Distribution: Slackware on x86 and arm
Posts: 2,487
Blog Entries: 2

Rep: Reputation: 992Reputation: 992Reputation: 992Reputation: 992Reputation: 992Reputation: 992Reputation: 992Reputation: 992
I suspect the generic behavior of tunefs triggers a break despite the error is benign?
 
Old 06-09-2023, 10:54 PM   #21
sndwvs
Senior Member
 
Registered: Aug 2014
Posts: 1,966

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by SCerovec View Post
I suspect the generic behavior of tunefs triggers a break despite the error is benign?
tune2fs 1.47.0 (5-Feb-2023) everything worked correctly.
Code:
|----------- delimiter ----------- "create" "filesystem" -----------|
mke2fs 1.47.0 (5-Feb-2023)
64-bit filesystem support is not enabled.  The larger fields afforded by this feature enable full-strength checksumming.  Pass -O 64bit to rectify.
Discarding device blocks: done                            
Creating filesystem with 307200 1k blocks and 76912 inodes
Filesystem UUID: 40c24d37-bb62-4f86-a10d-65f2bed6ff49
Superblock backups stored on blocks: 
	8193, 24577, 40961, 57345, 73729, 204801, 221185

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done 

mke2fs 1.47.0 (5-Feb-2023)
64-bit filesystem support is not enabled.  The larger fields afforded by this feature enable full-strength checksumming.  Pass -O 64bit to rectify.
Discarding device blocks: done                            
Creating filesystem with 1232640 4k blocks and 308256 inodes
Filesystem UUID: 7f83708d-cf10-4929-98bc-4c9f0cb01a6c
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done 

tune2fs 1.47.0 (5-Feb-2023)
tune2fs 1.47.0 (5-Feb-2023)
|----------- delimiter ----------- "tune" "filesystem" -----------|
tune2fs 1.47.0 (5-Feb-2023)
tune2fs 1.47.0 (5-Feb-2023)
e2fsck 1.47.0 (5-Feb-2023)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
linuxroot: 11/308256 files (0.0% non-contiguous), 21764/1232640 blocks
 
Old 06-10-2023, 02:31 PM   #23
SCerovec
Senior Member
 
Registered: Oct 2006
Location: Cp6uja
Distribution: Slackware on x86 and arm
Posts: 2,487
Blog Entries: 2

Rep: Reputation: 992Reputation: 992Reputation: 992Reputation: 992Reputation: 992Reputation: 992Reputation: 992Reputation: 992
Quote:
Originally Posted by sndwvs View Post
tune2fs 1.47.0 (5-Feb-2023) everything worked correctly.
Code:
|----------- delimiter ----------- "create" "filesystem" -----------|
mke2fs 1.47.0 (5-Feb-2023)
64-bit filesystem support is not enabled.  The larger fields afforded by this feature enable full-strength checksumming.  Pass -O 64bit to rectify.
Discarding device blocks: done                            
Creating filesystem with 307200 1k blocks and 76912 inodes
Filesystem UUID: 40c24d37-bb62-4f86-a10d-65f2bed6ff49
Superblock backups stored on blocks: 
	8193, 24577, 40961, 57345, 73729, 204801, 221185

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done 

mke2fs 1.47.0 (5-Feb-2023)
64-bit filesystem support is not enabled.  The larger fields afforded by this feature enable full-strength checksumming.  Pass -O 64bit to rectify.
Discarding device blocks: done                            
Creating filesystem with 1232640 4k blocks and 308256 inodes
Filesystem UUID: 7f83708d-cf10-4929-98bc-4c9f0cb01a6c
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done 

tune2fs 1.47.0 (5-Feb-2023)
tune2fs 1.47.0 (5-Feb-2023)
|----------- delimiter ----------- "tune" "filesystem" -----------|
tune2fs 1.47.0 (5-Feb-2023)
tune2fs 1.47.0 (5-Feb-2023)
e2fsck 1.47.0 (5-Feb-2023)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
linuxroot: 11/308256 files (0.0% non-contiguous), 21764/1232640 blocks
How come mine works different?
 
Old 06-10-2023, 02:55 PM   #24
sndwvs
Senior Member
 
Registered: Aug 2014
Posts: 1,966

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by SCerovec View Post
How come mine works different?
my all builds go on arm device
 
Old 06-10-2023, 06:27 PM   #25
SCerovec
Senior Member
 
Registered: Oct 2006
Location: Cp6uja
Distribution: Slackware on x86 and arm
Posts: 2,487
Blog Entries: 2

Rep: Reputation: 992Reputation: 992Reputation: 992Reputation: 992Reputation: 992Reputation: 992Reputation: 992Reputation: 992
Post

I run everything on the Rock 5.
I run it on -current after a thorough update.
and i do:
Code:
 git fetch 
git pull
before a build.
I always try to build for ROCK 5 and kernel next.
I only pick "clean", "download", "compile" and "core" as target.

here my next failed build log:
Attached Files
File Type: log build.log (186.6 KB, 2 views)
 
Old 06-11-2023, 03:15 AM   #26
sndwvs
Senior Member
 
Registered: Aug 2014
Posts: 1,966

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by SCerovec View Post
I run everything on the Rock 5.
I run it on -current after a thorough update.
and i do:
Code:
 git fetch 
git pull
before a build.
I always try to build for ROCK 5 and kernel next.
I only pick "clean", "download", "compile" and "core" as target.

here my next failed build log:
fixed
 
Old 06-11-2023, 05:22 AM   #27
SCerovec
Senior Member
 
Registered: Oct 2006
Location: Cp6uja
Distribution: Slackware on x86 and arm
Posts: 2,487
Blog Entries: 2

Rep: Reputation: 992Reputation: 992Reputation: 992Reputation: 992Reputation: 992Reputation: 992Reputation: 992Reputation: 992
Question

Code:
|info| create       partition
|info| create       filesystem
|info| tune         filesystem
|err | details      /home/cest/src/images_build_kit/build/source/build.log
bash-5.2#
A-ha

(here log)

What I see is happening IMHO is, once the filesystem has been remedied the script should re-check it and then attempt mounting it - the mounting operation being the only point of failure that should result exiting the script?

During my time with various fskings there were always too vocal exits for whatever trivial reasons...
Attached Files
File Type: log build.log (111.1 KB, 1 views)

Last edited by SCerovec; 06-11-2023 at 01:02 PM. Reason: why log failed to upload?
 
Old 06-17-2023, 04:48 PM   #28
SCerovec
Senior Member
 
Registered: Oct 2006
Location: Cp6uja
Distribution: Slackware on x86 and arm
Posts: 2,487
Blog Entries: 2

Rep: Reputation: 992Reputation: 992Reputation: 992Reputation: 992Reputation: 992Reputation: 992Reputation: 992Reputation: 992
Arrow

Code:
  CC      arch/arm64/kernel/asm-offsets.s
In file included from ./arch/arm64/include/asm/kvm_host.h:36,
                 from ./include/linux/kvm_host.h:45,
                 from arch/arm64/kernel/asm-offsets.c:16:
./include/kvm/arm_arch_timer.h:53:8: error: redefinition of ‘struct arch_timer_offset’
   53 | struct arch_timer_offset {
      |        ^~~~~~~~~~~~~~~~~
./include/kvm/arm_arch_timer.h:30:8: note: originally defined here
   30 | struct arch_timer_offset {
      |        ^~~~~~~~~~~~~~~~~
./include/kvm/arm_arch_timer.h:61:8: error: redefinition of ‘struct arch_timer_vm_data’
   61 | struct arch_timer_vm_data {
      |        ^~~~~~~~~~~~~~~~~~
./include/kvm/arm_arch_timer.h:43:8: note: originally defined here
   43 | struct arch_timer_vm_data {
      |        ^~~~~~~~~~~~~~~~~~
make[1]: *** [scripts/Makefile.build:114: arch/arm64/kernel/asm-offsets.s] Error 1
make: *** [Makefile:1287: prepare0] Error 2
|err | details      /home/cest/src/images_build_kit/build/source/build.log
and the log:

On Slackwareaarch64-current

HTH
Attached Files
File Type: log build.log (51.3 KB, 1 views)
 
Old 06-17-2023, 05:08 PM   #29
SCerovec
Senior Member
 
Registered: Oct 2006
Location: Cp6uja
Distribution: Slackware on x86 and arm
Posts: 2,487
Blog Entries: 2

Rep: Reputation: 992Reputation: 992Reputation: 992Reputation: 992Reputation: 992Reputation: 992Reputation: 992Reputation: 992
Arrow

Code:
  CC      arch/arm64/kvm/hyp/nvhe/../aarch32.nvhe.o
  CC      arch/arm64/kernel/vdso.o
  CC      arch/arm64/kvm/hyp/nvhe/../vgic-v2-cpuif-proxy.nvhe.o
  AS      arch/arm64/kvm/hyp/nvhe/../entry.nvhe.o
  CC      ipc/syscall.o
  CC      kernel/locking/semaphore.o
  CC      fs/quota/quota.o
  CC      kernel/sched/deadline.o
  CC      fs/proc/base.o
  CC      mm/interval_tree.o
  CC      fs/iomap/seek.o
  CC      mm/list_lru.o
In file included from ./include/linux/rculist.h:10,
                 from ./include/linux/pid.h:5,
                 from ./include/linux/sched.h:14,
                 from kernel/locking/semaphore.c:30:
In function '__list_add',
    inlined from 'list_add_tail' at ./include/linux/list.h:100:2,
    inlined from '__down_common' at kernel/locking/semaphore.c:209:2:
./include/linux/list.h:70:20: warning: storing the address of local variable 'waiter' in '((struct list_head *)sem)[2].prev' [-Wdangling-pointer=]
error, forbidden warning:list.h:70
   70 |         next->prev = new;
      |         ~~~~~~~~~~~^~~~~
kernel/locking/semaphore.c: In function '__down_common':
kernel/locking/semaphore.c:207:33: note: 'waiter' declared here
  207 |         struct semaphore_waiter waiter;
      |                                 ^~~~~~
kernel/locking/semaphore.c:204:59: note: 'sem' declared here
  204 | static inline int __sched __down_common(struct semaphore *sem, long state,
      |                                         ~~~~~~~~~~~~~~~~~~^~~
make[2]: *** [scripts/Makefile.build:273: kernel/locking/semaphore.o] Error 1
make[1]: *** [scripts/Makefile.build:516: kernel/locking] Error 2
make[1]: *** Waiting for unfinished jobs....
  CC      fs/iomap/swapfile.o
  CC      ipc/ipc_sysctl.o
is the partial snip of the log from failed legacy kernel build attempt
 
Old 06-17-2023, 10:19 PM   #30
sndwvs
Senior Member
 
Registered: Aug 2014
Posts: 1,966

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by SCerovec View Post
Code:
  CC      arch/arm64/kvm/hyp/nvhe/../aarch32.nvhe.o
  CC      arch/arm64/kernel/vdso.o
  CC      arch/arm64/kvm/hyp/nvhe/../vgic-v2-cpuif-proxy.nvhe.o
  AS      arch/arm64/kvm/hyp/nvhe/../entry.nvhe.o
  CC      ipc/syscall.o
  CC      kernel/locking/semaphore.o
  CC      fs/quota/quota.o
  CC      kernel/sched/deadline.o
  CC      fs/proc/base.o
  CC      mm/interval_tree.o
  CC      fs/iomap/seek.o
  CC      mm/list_lru.o
In file included from ./include/linux/rculist.h:10,
                 from ./include/linux/pid.h:5,
                 from ./include/linux/sched.h:14,
                 from kernel/locking/semaphore.c:30:
In function '__list_add',
    inlined from 'list_add_tail' at ./include/linux/list.h:100:2,
    inlined from '__down_common' at kernel/locking/semaphore.c:209:2:
./include/linux/list.h:70:20: warning: storing the address of local variable 'waiter' in '((struct list_head *)sem)[2].prev' [-Wdangling-pointer=]
error, forbidden warning:list.h:70
   70 |         next->prev = new;
      |         ~~~~~~~~~~~^~~~~
kernel/locking/semaphore.c: In function '__down_common':
kernel/locking/semaphore.c:207:33: note: 'waiter' declared here
  207 |         struct semaphore_waiter waiter;
      |                                 ^~~~~~
kernel/locking/semaphore.c:204:59: note: 'sem' declared here
  204 | static inline int __sched __down_common(struct semaphore *sem, long state,
      |                                         ~~~~~~~~~~~~~~~~~~^~~
make[2]: *** [scripts/Makefile.build:273: kernel/locking/semaphore.o] Error 1
make[1]: *** [scripts/Makefile.build:516: kernel/locking] Error 2
make[1]: *** Waiting for unfinished jobs....
  CC      fs/iomap/swapfile.o
  CC      ipc/ipc_sysctl.o
is the partial snip of the log from failed legacy kernel build attempt
fixed
 
1 members found this post helpful.
  


Reply

Tags
radxa team, rk3588, rockchip, slackware, slarm64


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Rock PI 4 RK3399 (aarch64) sndwvs Slackware - ARM 100 12-07-2021 09:25 AM
[SOLVED] Rock Pi E RK3328 (aarch64) sndwvs Slackware - ARM 10 12-07-2021 09:23 AM
[SOLVED] Rock Pi S RK3308 (aarch64) sndwvs Slackware - ARM 22 12-07-2021 09:22 AM
[SOLVED] ROCK 3 RK3568 (slarm64, aarch64) sndwvs Slackware - ARM 7 12-07-2021 09:16 AM
Rock Linux -- does it rock ?? rolando Linux - Distributions 2 10-10-2004 01:52 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > slarm64

All times are GMT -5. The time now is 10:20 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration