[Current version dev thread] - Usage of SliTaz 4.0 / rolling

SliTaz Forum » English Support » Live and installation

[Current version dev thread] - Usage of SliTaz 4.0 / rolling

(485 posts) (13 voices)

Started 1 year ago by shann
Latest reply from shann
This topic is not a support question

Tags:

No tags yet.

« Previous 1…293031…33 Next »

alanyih

offline

Administrator

Hi shann,

i recheck iso on my space, both base64/core64 have
mirror point to people and not local, maybe you have previous iso :/ ?

> slitaz-current-core64.iso 2024-Jul-04 14:25:37 90.3M

-rw-r--r-- 1 root root 88004608 Jul 4 02:43 slitaz-current-core64.iso

MENU TITLE SliTaz GNU/Linux - current 20240703

root@slitaz:~# ls -l
total 104656
-rw-r--r-- 1 root root 19159040 Jul 2 21:39 slitaz-current-base64.iso
-rw-r--r-- 1 root root 88004608 Jul 4 02:43 slitaz-current-core64.iso

root@slitaz:~# mount -o loop slitaz-current-core64.iso /media/cdrom
mount: /media/cdrom: WARNING: source write-protected, mounted read-only.

root@slitaz:~# head -5 /media/cdrom/boot/isolinux/isolinux.cfg
UI vesamenu.c32
PROMPT 0
TIMEOUT 80

MENU TITLE SliTaz GNU/Linux - current 20240703

root@slitaz:~# mkdir rootfs ; cd rootfs

root@slitaz:~/rootfs# lzma d /media/cdrom/boot/rootfs.gz -so | cpio -idm
652351 blocks

root@slitaz:~/rootfs# ls -l

total 12
drwxr-xr-x    2 root     root          1920 Jul  7 06:41 bin
drwxr-xr-x    7 root     root          2640 Jul  7 06:41 dev
drwxr-xr-x   25 root     root          1460 Jul  7 06:41 etc
drwxr-xr-x    2 root     root            40 Jul  2 10:17 home
-rwxr-xr-x    1 root     root          9050 Jul  1 15:38 init
drwxr-xr-x    5 root     root          1740 Jul  7 06:41 lib
lrwxrwxrwx    1 root     root             3 Jul  7 06:41 lib64 -> lib
drwxr-xr-x    5 root     root           100 Jul  7 06:41 media
drwxr-xr-x    2 root     root            40 Jul  2 10:17 mnt
drwxr-xr-x    2 root     root            40 Jul  2 10:17 proc
drwxr-x---    2 root     root           120 Jul  7 06:41 root
drwxr-xr-x    2 root     root            40 Jul  2 10:17 run
drwxr-xr-x    2 root     root          1920 Jul  7 06:41 sbin
drwxr-xr-x    2 root     root            40 Jul  2 10:17 sys
drwxrwxrwt    2 root     root            40 Jul  2 10:17 tmp
drwxr-xr-x    9 root     root           200 Jul  7 06:41 usr
drwxr-xr-x   11 root     root           220 Jul  7 06:41 var

root@slitaz:~/rootfs# cat var/lib/tazpkg/mirror
/home/slitaz/packages-incoming/

Posted 4 months ago #

shann

offline
Administrator

Hi alanyih,

strange :(, of course new iso i pushed yesterday to have uefi boot (syslinux bios / grub2 uefi) have right mirror.

Posted 4 months ago #
shann

offline
Administrator

Hi,

I update x64 iso to use last kernel 5.10, 5.10.221.

Also need to patch aufs code vfsub.c and hfsnotify.c, infact vfs_rename struct change to renamedata and fsnotify_alloc_group now required two args instead one (change on 5.10.220)
Good pratical exercise, infact i started to learn C language ;)

/home/slitaz/wok/linux64-aufs/source/linux64-aufs-20220912/fs/aufs/vfsub.c: In function 'vfsub_rename':
/home/slitaz/wok/linux64-aufs/source/linux64-aufs-20220912/fs/aufs/vfsub.c:420:19: error: passing argument 1 of 'vfs_rename' from incom
err = vfs_rename(src_dir, src_dentry, dir, path->dentry,
^~~~~~~
In file included from ./include/linux/security.h:29,
from /home/slitaz/wok/linux64-aufs/source/linux64-aufs-20220912/fs/aufs/vfsub.c:25:
./include/linux/fs.h:1822:16: note: expected 'struct renamedata *' but argument is of type 'struct inode *'
int vfs_rename(struct renamedata *);
^~~~~~~~~~~~~~~~~~~
/home/slitaz/wok/linux64-aufs/source/linux64-aufs-20220912/fs/aufs/vfsub.c:420:8: error: too many arguments to function 'vfs_rename'
err = vfs_rename(src_dir, src_dentry, dir, path->dentry,
^~~~~~~~~~
In file included from ./include/linux/security.h:29,
from /home/slitaz/wok/linux64-aufs/source/linux64-aufs-20220912/fs/aufs/vfsub.c:25:
./include/linux/fs.h:1822:5: note: declared here
int vfs_rename(struct renamedata *);
^~~~~~~~~~
cc1: some warnings being treated as errors

/home/slitaz/wok/linux64-aufs/source/linux64-aufs-20220912/fs/aufs/hfsnotify.c: In function 'au_hfsn_init_br':
/home/slitaz/wok/linux64-aufs/source/linux64-aufs-20220912/fs/aufs/hfsnotify.c:241:10: error: too few arguments to function 'fsnotify_a
group = fsnotify_alloc_group(&au_hfsn_ops);
^~~~~~~~~~~~~~~~~~~~
In file included from ./include/linux/fsnotify.h:15,
from /home/slitaz/wok/linux64-aufs/source/linux64-aufs-20220912/fs/aufs/inode.h:28,
from /home/slitaz/wok/linux64-aufs/source/linux64-aufs-20220912/fs/aufs/aufs.h:49,
from /home/slitaz/wok/linux64-aufs/source/linux64-aufs-20220912/fs/aufs/hfsnotify.c:23:
./include/linux/fsnotify_backend.h:598:31: note: declared here
extern struct fsnotify_group *fsnotify_alloc_group(
^~~~~~~~~~~~~~~~~~~~
make[2]: *** [scripts/Makefile.build:286: /home/slitaz/wok/linux64-aufs/source/linux64-aufs-20220912/fs/aufs/hfsnotify.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [Makefile:1832: /home/slitaz/wok/linux64-aufs/source/linux64-aufs-20220912/fs/aufs] Error 2
make[1]: Leaving directory '/home/slitaz/wok/linux64-aufs/source/linux64-aufs-20220912/linux-5.10.221'
make: *** [Makefile:43: fs/aufs/aufs.ko] Error 2

Also need to check for merge receipt updated x86_64 to wok-current, no yet.

Posted 4 months ago #
Saipul

offline
Member
Hi Shann
I'm getting error when boot from Harddrive after fresh install to Harddrive. Syslinux boot, complaining about missing "vesamenu.c32" in /boot/syslinux directory.
Copy/paste "vesamenu.c32" and other (except syslinux.cfg) fix the issue...

And I see /var/log/Xorg.0.log after installing radeon drivers for HD7870, radeon_drv.so missing depends "libgbm.so.1"
Attachments
Xorg.0.log (44.3 KB, 33 downloads) 4 months old
Posted 4 months ago #
shann

offline
Administrator

Hi Saipul,

good catch for miss libgbm, seem i forget it when i check that deps is ok for core iso :(
I update xorg-server, libglamoregl.so need it also.
People space is up to date.

For syslinux, i don't use it only grub2, let's me check if tazint need tweak to ensure that syslinux boot work as expected.

Posted 4 months ago #
shann

offline
Administrator

Saipul,

After check on qemu, seem on rootfs we don't have /boot/isolinux, tazinst check on /boot but none on cdrom device himself.

Let's me do patch for search on $SOURCE_ROOT/boot instead /boot.

EDIT: i rebuild current64 iso, are updated on my space

Posted 4 months ago #
Saipul

offline
Member

Hi Shann, thanks for the update...
Now currently downloading the new iso and I'll report back soon...

Posted 4 months ago #
Saipul

offline
Member
Hi Shann
After fresh install and reboot. Starting to boot and look boot process, I see that message from e2fsck can't resolve my Harddrive with "UUID". So I change to "/dev/sda1" and e2fsck can resolve. And two boot log I have been upload.

And for my Radeon HD7870 after configuring with "tazx" and rebooting. Start booting until the end of "Welcome to your box", after that seem to be freezing with radeon driver.
"messages, Xorg.0.log" and "installed_packages.txt" upload.
Attachments
messages.txt (48.1 KB, 39 downloads) 4 months old
installed_packages.txt (3.4 KB, 39 downloads) 4 months old
Xorg.0.log (26.3 KB, 32 downloads) 4 months old
boot-with_sda1.log (4.4 KB, 36 downloads) 4 months old
boot-with_uuid.log (4.2 KB, 36 downloads) 4 months old
Posted 4 months ago #
shann

offline
Administrator
Hi Saipul,

Not sure that e2fsck support UUID.

Concerning freeze of Xorg, sad to read this :(.
On my side for Tuxedo that use Ryzen 7 with Vega, if i use tazx with amdgpu Xorg failed but if i check, xorg.d/60-Device.conf have amdgpu and if restart slim, xorg work.

Maybe impacted but on kernel we have this for AMDGPU / RADEON

tux@slitaz:~$ zcat /proc/config.gz |grep AMDGPU
CONFIG_DRM_AMDGPU=m
CONFIG_DRM_AMDGPU_SI=y
CONFIG_DRM_AMDGPU_CIK=y
CONFIG_DRM_AMDGPU_USERPTR=y

i found this thread talk about option to pass on linux cmdline to use amdgpu and not radeon, on your case maybe do reverse radeon.si_support=1 amdgpu.si_support=0 ?
radeon.si_support=0 amdgpu.si_support=1
https://community.amd.com/t5/drivers-software/radeon-hd-7870-ghz-edition-under-ubuntu-kubuntu-20-04-local/td-p/456229
Attachments
Xorg.0.log (23.8 KB, 37 downloads) 4 months old
Posted 4 months ago #
shann

offline
Administrator

I rebuild iso and kernel.
Infact i see that /proc/cpuinfo report 8cpus 4c/8t, but my ryzen 7 4800H should have 8c/16t.
After check, remain default CONFIG_NR_CPUS=8, i adjust it to 64.

Also below roadmap i plan :

"Need to remain KISS and Light !"

- Reduce size of current live
=> infact need at least 768Mo to boot, it's bad (my fault also, we have libwebkit/webkitgtk to deal with tazpanel and other web apps, it's on my todo to have tazpanel as apps)

- Media Keyboard support

- Display support
=> HDMI, ...

- Accessibility
=> display, voice, typing, ...

- Kids usage
=> gcompris, tuxmath, ...

- School usage
=> apps, tool managment, ...

- Work usage
=> IDE, VPN, virtulization/container, ...

- Audio/Video
=> microphone, webcam, ...

And another big subject, purpose wayland version

Posted 4 months ago #
gibor

offline
Moderator

@Shann

Not sure that e2fsck support UUID.

On my system work...

tux@slitaz:~$ blkid
/dev/mmcblk1p1: UUID="25c0cf06-f3a3-4a2d-bf8d-81fe01a67ec6" BLOCK_SIZE="4096" TYPE="ext3" PARTUUID="700f978d-01"
/dev/mmcblk2p2: UUID="08596b98-1776-445f-a99a-69b92ead6356" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="root" PARTUUID="bc92391a-1b03-994d-9cde-8c47b10e28c7"
/dev/mmcblk2p1: LABEL="NO_LABEL" UUID="DC58-6730" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="e259e40c-cdd0-a841-88b3-2c5e08f62cd8"
tux@slitaz:~$ cat /etc/rcS.conf | grep CHECK_FS
# /etc/fstab. Example: CHECK_FS="/dev/hda5 /dev/hdb1"
CHECK_FS='UUID="08596b98-1776-445f-a99a-69b92ead6356"'

Posted 4 months ago #
shann

offline
Administrator

Hi Gibor,

Infact i reinstall my miniserver with current64 (previous current with linux64).

I test also for CHECK_FS, infact if i use UUID= same error :(

^[[1;36mChecking filesystem: UUID="95aab605-b2e1-481a-a051-24b91a38800c"^[[0;39m
e2fsck: Unable to resolve 'UUID="95aab605-b2e1-481a-a051-24b91a38800c"'

But e2fsck command seem ok with UUID :( strange ?!

root@eretria:~# grep UUID /etc/rcS.conf
CHECK_FS='UUID="95aab605-b2e1-481a-a051-24b91a38800c"'
root@eretria:~# e2fsck -p UUID="95aab605-b2e1-481a-a051-24b91a38800c"
/dev/nvme0n1p1 is mounted.
e2fsck: Cannot continue, aborting.

ok with disk /dev

^[[1;36mChecking filesystem: /dev/nvme0n1p1^[[0;39m
/dev/nvme0n1p1: clean, 7730/327680 files, 85195/1310720 blocks

root@eretria:~# slitaz

SliTaz GNU/Linux
================================================================================
Release : current64
Architecture : x86_64
Kernel : 5.10.221-slitaz64
Machine type : x86_64
Home path : /home/slitaz
Configs : /etc/slitaz
Main config : /etc/slitaz/slitaz.conf
Log files : /var/log/slitaz
Packages DB : /var/lib/tazpkg
Installed : 53 packages
Mirror : http://people.slitaz.org/~shann/slitaz-current64-stuff/packages/
System date : Wed Jul 10 13:24:57 Europe 2024
--------------
Boot options : BOOT_IMAGE=/boot/vmlinuz-5.10.221-slitaz64 root=/dev/nvme0n1p1 ro
================================================================================

root@eretria:~# cat /proc/cpuinfo |grep AMD
vendor_id : AuthenticAMD
model name : AMD Ryzen 3 3200U with Radeon Vega Mobile Gfx
vendor_id : AuthenticAMD
model name : AMD Ryzen 3 3200U with Radeon Vega Mobile Gfx
vendor_id : AuthenticAMD
model name : AMD Ryzen 3 3200U with Radeon Vega Mobile Gfx
vendor_id : AuthenticAMD
model name : AMD Ryzen 3 3200U with Radeon Vega Mobile Gfx
root@eretria:~# free -m
total used free shared buff/cache available
Mem: 14015 77 13923 0 14 13825
Swap: 0 0 0
root@eretria:~# df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 4.8G 91.6M 4.7G 2% /
tmpfs 6.8G 192.0K 6.8G 0% /run
tmpfs 6.8G 192.0K 6.8G 0% /var/run
devtmpfs 6.8G 0 6.8G 0% /dev
tmpfs 6.8G 0 6.8G 0% /dev/shm
tmpfs 6.8G 0 6.8G 0% /var/lock
/dev/nvme0n1p2 910.9G 468.0K 906.3G 0% /home

Posted 4 months ago #
shann

offline
Administrator

I test HDMI with my TV, it's work also send sound on HDMI (thanks pavucontrol ;)).

lxrandr don't know HDMI-A-0 but xrandr yes.

tux@slitaz:~$ xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
eDP connected primary 1920x1080+0+0 344mm x 194mm
1920x1080 60.04*+
1680x1050 60.04
1280x1024 60.04
1440x900 60.04
1280x800 60.04
1280x720 60.04
1024x768 60.04
800x600 60.04
640x480 60.04
HDMI-A-0 connected
3840x2160 60.00 + 50.00 59.94 30.00 25.00 24.00 29.97 23.98
4096x2160 60.00 50.00 59.94 30.00 25.00 24.00 29.97 23.98
1920x1200 60.00
1920x1080 60.00 50.00 59.94 30.00 25.00 24.00 29.97 23.98
1600x1200 60.00
1680x1050 60.00
1280x1024 60.02
1440x900 60.00
1280x960 60.00
1280x800 60.00
1280x720 60.00 50.00 59.94
1024x768 60.00
800x600 60.32
720x576 50.00
720x480 60.00 59.94
640x480 60.00 59.94

xrandr --output HDMI-A-0 --right-of eDP --auto

Posted 4 months ago #
gibor

offline
Moderator

add UUID entry in /etc/fstab

Processing /etc/init.d/rcS...
Mounting proc filesystem...[70G[ [1;32mOK[0;39m ]
Checking filesystem on : UUID="08596b98-1776-445f-a99a-69b92ead6356"
/dev/mmcblk1p2: clean, 324821/942080 files, 3506059/3768247 blocks
Remounting rootfs read/write...

Posted 4 months ago #
shann

offline
Administrator

thanks gibor for test and feedback :)

Good news and bad :/, i would like install SliTaz Current64 on my brother laptop ASUS.
sound, hdmi ok, but wireless not work, i add rtw88 driver and firmware but error about rfe4 isn't supported

[ 8.694896] rtw_8821ce 0000:02:00.0: enabling device (0000 -> 0003)
[ 8.808629] rtw_8821ce 0000:02:00.0: Firmware version 24.1.0, H2C version 12
[ 8.830737] rtw_8821ce 0000:02:00.0: rfe 4 isn't supported
[ 8.830881] rtw_8821ce 0000:02:00.0: failed to setup chip efuse info
[ 8.830884] rtw_8821ce 0000:02:00.0: failed to setup chip information

Seem related to our kernel version, added to 5.16.
https://bugzilla.kernel.org/show_bug.cgi?id=212435

Maybe try if can backport this commit to 5.10, or maybe time to check add 6.x branch
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b789e3fe7047296be0ccdbb7ceb0b58856053572

Posted 4 months ago #

RSS feed for this topic

« Previous 1…293031…33 Next »

Reply »

You must log in to post.

[Current version dev thread] - Usage of SliTaz 4.0 / rolling

Attachments

Attachments

Attachments

Reply »