not a support question
Aleksej
offlineCoder-hobbyist
Hi there,
> cook is no more synchronized with mirror
Cook of the SliTaz Next never synchronized with the mirror in the automatic mode (like you can see in the Cook of the SliTaz Rolling). I always transferred files manually (if I recall correctly, with something like rsync).
alanyih
offlineAdministrator
@kultex
root@slitaz:/home/tux/Downloads# tazpkg -i tazlito-523.tazpkg
/usr/libexec/tazpkg/install: line 428: can't open tazlito-523.tazpkg: no such file
Try:
root@slitaz:~# tazpkg -i /home/tux/Downloads/tazlito-523-any.tazpkg --forced
Installation of package "tazlito"
================================================================================
SliTaz Live Tool
--------------------------------------------------------------------------------
Copying package... [ Done ]
Extracting package... [ Done ]
Remember modified packages... [ Done ]
Saving configuration files... [ Done ]
Installing package... [ Done ]
Removing all tmp files... [ Done ]
Update system databases... [ Done ]
================================================================================
Package "tazlito" (523) is installed.
root@slitaz:~# tazlito | head -n 3
SliTaz Live Tool - Version: 523
kultex
offlineKey Master
I all the time get the error installing with forced or without, but it installs correct - I checked
but no luck to boot - it ends up all the time with an init error - does not find the init (Error2)
Pascal, do you have an idea? The problem is, I can only work and test frugal from stick, when I am in the train and have some free time. Should I upload the created rootfs.gz?
And tazusb ends all the time with a hex-code error
Ceel
offlineAdministrator
@ kultex
Here is the link to download my justX flavour ISO:
https://send.firefox.com/download/2b5c71460f62412a/#shHnEzGk_0fNkGfa03L8uw
(will expire on 2019-12-14 00:00).
I think I'll have time to pack the LXlauncher flavour tomorrow.
next64-justx+.md5.txt (0.1 KB, 319 downloads) 5 years old
kultex
offlineKey Master
@Ceel thx very much, but please can you add linux-ethernet to the flavor - I dont care justX or LXlauncher
Like this its quite unuseable
Ceel
offlineAdministrator
@kultex
Yes, you're right. I suppressed it and linux-wireless too because I did a copy of the Next64 repository on my HD; it saves time when using tazlito.
This one should be better: https://send.firefox.com/download/6ffcc42542c86f9f/#gdY6YgoHA1Cj2kK7-gZJuw
next64-justx+.md5.txt (0.1 KB, 336 downloads) 5 years old
kultex
offlineKey Master
strange, I thought I already wrote an answer....
your iso has exact the same errors as the iso from alanyih
how do you make your iso?
with which tazlito commands?
Ceel
offlineAdministrator
@ kultex
tazlito clean-distro
tazlito gen-distro my.list
Then changing some conf files (ie mirror)
In /home/slitaz/next64/distro/rootfs
find . -print | cpio -o -H newc | lzma e -si -so > ../rootfs.gz
cp -a the rootfs.gz in /home/slitaz/next64/distro/rootcd/boot
tazlito gen-iso
What are the errors?
I didn't test the ISO in Live mode, only the rootfs.gz in frugal; I just keep one 64bit computer here, and it's a UEFI. however, I'll try to creat a USB Live during the week.
kultex
offlineKey Master
I use tazlito writeiso lzma - creates the rootfs.gz and then, there are errors
but the iso does not boot - ends with init error - error 2 - cant find init
EDIT: and you run it from cooking or next?
Ceel
offlineAdministrator
tazlito-492 from Next64 in full installation
Ceel
offlineAdministrator
I made a LiveUSB with tazusb on a FAT32 USB key:
tazusb gen-iso2usb next64-justx+.iso /dev/sdb1
Then, in the Live, I
# refind_linux.conf # # CONFIGURATION FILE FOR rEFInd TO BOOT FROM THE SLITAZ LINUX KERNEL (>= 3.30) # "Next64" "ro root=/dev/null kmap=fr-latin1 initrd=/boot/rootfs.gz"
In Setup Secure boot= Disabled and Boot priority order= USB HDD
At boot when rEFInd displays its menu, select the device and hit [Enter], next64-justx+ boots without any errors; only the same issue than boot in frugal from rootfs.gz, I'm quite sure something is missing in my ISO but I don't find what :(
I'm going to try to find a non-UEFI computer at work to see if the Live boots correctly from Syslinux.
I don't understand why there are errors at boot in Live and not in frugal.
kultex
offlineKey Master
thx - I used tazusb writefs lzma - and my stick is ext4
I will try tomorrow gen-iso2usb
+ by the way - netsurf 3.9 is unuseable in next - to many segfaults
kultex
offlineKey Master
There are no errors in Live booting
I have booted your iso in Live mode from the stick, but the modified rootfs.gz, produced by tazusb and tazlito and replacing the original rootfs.gz, produce the kernel panic.
I hope, thats clear now - I am in non-UEFI mode / from my stick I can boot now 6 different linux from syslinux.....
it would be just cool, if I could remaster from the booted LIVE SliTaz next, whenever I do some changes / like I always did...
alanyih
offlineAdministrator
startx VS. slim login manager
startx
tux@slitaz:~$ cat .xsession
# ~/.xsession: Start X window session manually on your system (startx).
#
. $HOME/.config/slitaz/applications.conf
Xorg &
#xterm &
#xpad &
exec $WINDOW_MANAGER
tux@slitaz:~$ ps
[..]
2091 root 0:00 /sbin/getty 115200 38400 9600 4800 2400 ttyS0
2149 messageb 0:00 /usr/bin/dbus-daemon --system
2153 tux 0:00 /usr/bin/openbox --startup /usr/lib/openbox/openbox-autos
2155 root 0:00 /usr/libexec/Xorg
2178 tux 0:00 pcmanfm --desktop
2179 tux 0:00 lxpanel --profile slitaz
2183 tux 0:00 dbus-launch --sh-syntax --exit-with-session
2184 tux 0:00 /usr/bin/dbus-daemon --syslog --fork --print-pid 5 --prin
2195 tux 0:00 /usr/libexec/menu-cache/menu-cached /home/tux/.cache/menu
2213 tux 0:00 sakura --sync --geometry 80x24 -t SliTaz next64
2215 tux 0:00 gnome-pty-helper
2216 tux 0:00 /bin/sh
2217 tux 0:00 ps
tux@slitaz:~$ pstree -p
init(1)-+-dbus-daemon(2149)
|-dbus-daemon(2184)
|-dbus-launch(2183)
|-getty(2087)
|-getty(2088)
|-getty(2089)
|-getty(2090)
|-getty(2091)
|-httpd(1945)
|-klogd(1463)
|-lxpanel(2179)-+-{gmain}(2187)
| `-{menu-cache-io}(2196)
|-menu-cached(2195)---{gmain}(2198)
|-pcmanfm(2178)-+-{gmain}(2188)
| |-{pool}(2222)
| `-{pool}(2223)
|-sakura(2213)-+-gnome-pty-helpe(2215)
| |-sh(2216)---pstree(2221)
| `-{gmain}(2214)
|-sh(2084)
|-sh(2083)---openbox(2153)---Xorg(2155)---{InputThread}(2169)
|-syslogd(1442)
|-udevd(1350)
`-udhcpc(2005)
tux@slitaz:~$
VS.
slim login manager
tux@slitaz:~$ cat .xinitrc
# ~/.xinitrc: Executed by Slim/LXDM login manager to startx X session.
# You can use F1 with Slim to change your window manager or configure
# it permanently with your personal applications.conf file.
#
. $HOME/.config/slitaz/applications.conf
tazbox mkmenu
[ "$1" ] && WINDOW_MANAGER="$1"
EXEC="exec ck-launch-session dbus-launch --sh-syntax --exit-with-session"
LOG="/dev/null" ; X=$LOG ; ERR=$X
case "$WINDOW_MANAGER" in
openbox|lxde*|icewm*|xfce4|compiz|karmen|dwm|fluxbox*|razor*|mate*)
$EXEC ${WINDOW_MANAGER%-session}-session ;;
enlightenment)
$EXEC enlightenment_start ;;
kde) $EXEC startkde ;;
lxqt) $EXEC startlxqt ;;
*) $EXEC $WINDOW_MANAGER ;;
esac 2>>$ERR >>$X
tux@slitaz:~$ ps
PID USER TIME COMMAND
1 root 0:13 init
[..]
2007 root 0:00 /sbin/udhcpc -b -T 1 -A 12 -i eth0 -p /var/run/udhcpc.eth
2039 messageb 0:00 /usr/bin/dbus-daemon --system
2148 root 0:00 /usr/bin/slim -d
2154 root 0:00 /usr/libexec/Xorg -auth /var/run/slim.auth vt07
2163 root 0:00 /usr/sbin/console-kit-daemon --no-daemon
2169 polkitd 0:00 /usr/lib/polkit-1/polkitd --no-debug
2174 tux 0:00 ck-launch-session dbus-launch --sh-syntax --exit-with-ses
2217 tux 0:00 /usr/bin/openbox --startup /usr/lib/openbox/openbox-autos
2220 tux 0:00 dbus-launch --sh-syntax --exit-with-session openbox-sessi
2221 tux 0:00 /usr/bin/dbus-daemon --syslog --fork --print-pid 6 --prin
2234 tux 0:00 /usr/lib/gvfsd
2239 tux 0:00 /usr/lib/gvfsd-fuse /var/run/user/1000/gvfs -f -o big_wri
2252 tux 0:00 pcmanfm --desktop
2253 tux 0:00 lxpanel --profile slitaz
2264 tux 0:00 /usr/lib/gvfsd-metadata
2271 tux 0:00 /usr/libexec/menu-cache/menu-cached /var/run/user/1000/me
2279 tux 0:00 /usr/lib/gvfs-udisks2-volume-monitor
2283 root 0:00 /usr/libexec/udisks2/udisksd
2309 tux 0:00 /usr/lib/gvfs-gphoto2-volume-monitor
2314 tux 0:00 /usr/lib/gvfs-mtp-volume-monitor
2319 tux 0:00 /usr/lib/gvfsd-trash --spawner :1.1 /org/gtk/gvfs/exec_sp
2325 root 0:00 /sbin/getty 38400 tty1
2326 root 0:00 /sbin/getty 38400 tty2
2327 root 0:00 /sbin/getty 38400 tty3
2328 root 0:00 /sbin/getty 38400 tty4
2329 root 0:00 /sbin/getty 38400 tty5
2330 root 0:00 /sbin/getty 38400 tty6
2331 root 0:00 /sbin/getty 115200 38400 9600 4800 2400 ttyS0
2346 tux 0:00 sakura --sync --geometry 80x24 -t SliTaz next64
2349 tux 0:00 gnome-pty-helper
2350 tux 0:00 /bin/sh
2354 tux 0:00 ps
tux@slitaz:~$ pstree -p
init(1)-+-console-kit-dae(2163)-+-{console-kit-dae}(2167)
| |-{gdbus}(2166)
| |-{gmain}(2164)
| `-{vt_thread_start}(2170)
|-dbus-daemon(2039)
|-dbus-daemon(2221)
|-dbus-launch(2220)
|-getty(2325)
|-getty(2326)
|-getty(2327)
|-getty(2328)
|-getty(2329)
|-getty(2330)
|-getty(2331)
|-gvfs-gphoto2-vo(2309)-+-{gdbus}(2312)
| `-{gmain}(2310)
|-gvfs-mtp-volume(2314)-+-{gdbus}(2317)
| `-{gmain}(2315)
|-gvfs-udisks2-vo(2279)-+-{gdbus}(2281)
| `-{gmain}(2280)
|-gvfsd(2234)-+-gvfsd-trash(2319)-+-{gdbus}(2321)
| | `-{gmain}(2320)
| |-{gdbus}(2236)
| `-{gmain}(2235)
|-gvfsd-fuse(2239)-+-{gdbus}(2244)
| |-{gmain}(2243)
| |-{gvfs-fuse-sub}(2249)
| |-{gvfsd-fuse}(2241)
| `-{gvfsd-fuse}(2242)
|-gvfsd-metadata(2264)-+-{gdbus}(2266)
| `-{gmain}(2265)
|-httpd(1933)
|-klogd(1465)
|-lxpanel(2253)-+-{gdbus}(2258)
| |-{gmain}(2257)
| `-{menu-cache-io}(2272)
|-menu-cached(2271)-+-{gdbus}(2277)
| `-{gmain}(2276)
|-pcmanfm(2252)-+-{gdbus}(2256)
| |-{gmain}(2255)
| |-{pool}(2358)
| `-{pool}(2359)
|-polkitd(2169)-+-{gdbus}(2178)
| |-{gmain}(2177)
| |-{polkitd}(2180)
| `-{polkitd}(2182)
|-sakura(2346)-+-gnome-pty-helpe(2349)
| |-sh(2350)---pstree(2357)
| |-{gdbus}(2348)
| `-{gmain}(2347)
|-slim(2148)-+-Xorg(2154)---{InputThread}(2161)
| `-ck-launch-sessi(2174)---openbox(2217)-+-{gdbus}(2232)
| `-{gmain}(2231)
|-syslogd(1444)
|-udevd(1352)
|-udhcpc(2007)
`-udisksd(2283)-+-{cleanup}(2306)
|-{gdbus}(2286)
|-{gmain}(2284)
`-{probing-thread}(2287)
tux@slitaz:~$
Ceel
offlineAdministrator
@ kultex,
OK, clear.
I think I found where the problem comes from : in /usr/bin/tazusb, add lib64 at line 486.
for dir in /bin /etc /init /sbin /var /dev /lib /lib64 /root /usr /opt
Now the rootfs.gz I rebuild with tazusb boots without kernel panic.
Maybe there will be other lines to modify; I just have a look at the writefs function.
And maybe in others scripts too.
You must log in to post.
