SliTaz Forum
You are not logged in.
Hi all,
We just released SliTaz 5.0 RC2 with more than 500 commits from RC1 and we fixed almost all bugs. Please report any issue and feedback on this thread.
Official announce: http://www.slitaz.org/en/news/#d20140519
ISO image: http://mirror.slitaz.org/iso/5.0/slitaz-5.0-rc2.iso
Since Pascal and me are in Paris to handle SliTaz stall at SolutionsLinux, we coded together all the weekend and this monday to make RC2 append. http://www.solutionslinux.fr/
Hope you will enjoy!
- Christophe
Offline
Thanks for your effort to fix bugs. I'll burn a CD and test New Slitaz today and tomorrow.
OBS: The Slitaz official website is off. (I could only access the forum using Google search)
Offline
Virtual Machine: Unlike SliTaz 4.0, the failure of 'startx' is still there .
Please see the following log for details.
http://snipurl.com/28xi9uh
Offline
Así como la anterior RC tenía algunos problemas, esta probada muy rápidamente en
dos ordenadores de sobremesa (uno de 13 años y el otro de 7), han ido perfecto y funcionando con fluidez todo (sonido, particiones, video, lan y eth...)
Así que muchas gracias porque hacéis un sistema fiable, rápido, seguro, amigable,
austero, minimalista y lo más importante funcional.
Saludos.
Offline
Offline
Thanks, Trixar_za. Tried it on a real system and there were no problems. Since SliTaz 4 ( and earlier versions) VM worked, the expectation is for it to continue to function in the new release too.
"/var/log/Xorg.0.log" from SliTaz4 VM is here
-- http://paste.slitaz.org/?a2e7c78f625f7d2f#Stpf8iZ9n55pvhfcaazhoDlIH+iNKBhteSqm9/x6uJ0=
Offline
They may add it later. I just think some bugs might crop up that relate more to the VM than SliTaz considering how picky xorg is on which systems it runs well on.
Offline
I'm sorry to say that the mouse-pointer is still vanishing after some minutes
log out/in solve it for some min.
(nvidia FX5200, MoBo chipset SIS 735)
Desktop Effects: fade works but no shadows.
moving around the Task manager window (could be any other)
results in 100% cpu usage. Slitaz 4 = 30%
oops..now we have tooltips popping up on files and folders,displaying the name ??
Offline
Tested RC2.
Thank you Slitaz team: all issues from RC1 were solved.
Finally I can recover my files from my HD, saving them into a UBS key, before formatting the HD. Slitaz saved my life!
I'll learn how to work on Linux and abandon Windows... Win drives me crazy!
Offline
RC2 VM works as expected on Oracle VirtualBox . Thanks. http://paste.slitaz.org/?3e142c9badfa5c31#YjgeaK2UWerK7nwl3rw1C/MDmnsPghZkfCpgWldD2NI=
[attachment=30120,1497]
Offline
RC2 didn't work properly under qemu, just got X & an xterm, with only a few programs in the default menu.
But on creating a pendrive, it booted up & looks OK on this machine I'm on, posting from it now.
Hi fatmac,
RC2 didn't work properly under qemu, just got X & an xterm, with only a few programs in the default menu.
Seems like you boot justX flavor, not core. SliTaz 4-in-1 flavor boots one of 4 flavor depending on existing RAM size. Check available RAM size in the Qemu settings.
Offline
Hi guys, have tried the last version of prerelese, and not connect on my system if the name network wireless contain the space characters at end.
Unusual metod anyway, but on my network have putted the space on name, why more distro are affected this bug. On another words the system are on virtual mode more security...
Offline
@Aleksej
Just gave it another go under qemu, selected UK keymap, then let it boot. It only loaded 4 & 3 sqashfs.
If I select 'core live' it loads all 4 squashfs, but hangs at 'Trying to unpack rootfs image as initramfs...' with the cursor blinking under 'rootfs'.
If I select 'GTK only' it loads 4,3,& 2 squashfs, but then hangs, same place, but with the cursor under 'image'.
If I select 'Just X' it loads 4 & 3 squashfs, & starts up.
I have figured it out, it is qemu's fault.
By using 'qemu-system-i386 -cdrom slitaz-5.0-rc2.iso -boot d', qemu is not giving enough ram by default.
With the ram set to 512mb, all is OK.
Sorry to have intimated that there was anything wrong with the distro, I love it.
Awesome WM doesn't work. It is compiled as to not require LGI, but it is however a hardcoded runtime dependency, so even if built without it, it will still require LGI to run.
Offline
Hi necrophcodr,
Please wait me more, I need to make a break.
I have successfully run awesome on my SliTaz.
Really, it needs lgi (I've compiled it), and needs some folders replacement in the awesome package, and needs pango typelibs.
Note: http://awesome.naquadah.org/wiki/Awesome_3.4_to_3.5#New_Runtime-Only_Dependency
Offline
Hi necrophcodr,
It's here! 
New created packages you'll find in the mirror soon. Until that please download them from cooker server:
http://cook.slitaz.org/cooker.cgi?download=lgi-0.7.2.tazpkg
http://cook.slitaz.org/cooker.cgi?download=awesome-3.5.1.tazpkg
How to install and run — in short
Manually install lgi, then awesome using packages above.
Log out. In the SLiM press repeatedly F1 to change session to “awesome”; enter your username and password. Log to awesome WM.
Tested on SliTaz-5.0-RC2, and it runs and works. But it is a new software for me, and I can't figure out is it works fine or not.
Offline
HI
Just booted 5.0 RC-2
1. # alsactl init (not working in boot scripts):
Processing: /etc/init.d/system.sh
alsactl: init:1758: No soundcards found...
2. Pcmanfm crashes on ejecting/unmounting disks - buggy???
3. Date sets to UTC in SliTaz Config Dialogs -> set system date from the web
4. <hr /> tags in SliTaz Panel -> Hardware -> Detect PCI and USB hardware
Regards
Offline
Hi Paul,
4. Fixed: http://hg.slitaz.org/tazpanel/rev/6adca10ef270
We need to remember to "up" tazpanel before 5.0 release.
Offline
Hi Aleksej
I just tried your changes and I'm still getting <hr /> tags
Though:
$(tazhw detect-pci)
$(tazhw detect-usb)
Fixes for me?
Thanks
Offline
Hi Paul,
Yep, strange…
[*]Open “tazpanel:82” in the TazWeb. Go to “Hardware → Detect PCI & USB”. Our “<hr />” here.
[*]Right click on page. Reload. “<hr />” still here.
[*]Move cursor to address bar, press “Enter” (so URL is http://tazpanel:82/hardware.cgi?detect ). Now “<hr />” are gone and substitutes with “--------”. So strange.
Your proposition without “htmlize” produces plain ”>” symbol, it is no good and should be substituted by “>” html entity. Although most web browsers correctly recognizes ”>” as “>”, it produces not html compliant html code.
This is not an elegant but it works:
[c]<pre>$(tazhw detect-pci | htmlize | sed 's|<hr />|<hr />|g')</pre>[/c]
Offline
Hi, noted Trixar's comment earlier but just for the record, with RC-2 running as a Virtual Box guest, I noticed that the eth0 does not come up automatically.
/var/log/boot.log states.
configuring loopback....
ifconfig : SIOCGIFFLAGS: No such device
Starting udhcpc client on: eth0...
udhcpc: SIOCGIFINDEX: No such device
However, can bring up the network via Tazpanel or via '/etc/initd/network.sh start' without any problem.
Offline
Tested 5.0 RC-2, booted from CD as "SliTaz Live":
ALSACTL init produces an error msg during boot-up
- Processing: /etc/init.d/system.sh
- alsactl: init:1758: No soundcards found...
PCManFM crashes when unmounting a drive (hdd, usb, flash ...)
PCManFM run as root doesn't show any drives in the Places pane.
MOUNT POINT for internal and external drives used to be /media.
Now only cdrom is mounted in /media. Everything else gets
mounted in /run/media/tux.
KERNEL PANIC with tazlito generated ISOs (tazlito writeiso lzma)
- Freeing unused kernel memory: 592k freed
- Failed to open /proc/filesystems: No such file or directory
- Usb 1-6: new high-speed USB device number 2 using ehci_hcd
- Failed to open /proc/filesystems: No such file or directory
- NTFS signature missing.
- Failed to mount '/dev/loop0': Invalid argument
- The device '/dev/loop0' doesn't seem to have a valid NTFS.
- Maybe the wrong device is used? Or the whole disk instead of a
- partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
- Kernel panic - not syncing: Attempted to kill init!
- Pid: 1, comm: init not tainted 3.2.53-slitaz #4
- Call Trace: ... ... ...
Paul has already reported some of this.
Offline
............................REQUEST................................................
From document below :
"Each of these writes everything to a 'rootfs.gz' archive to be loaded the next time you boot."
It would be so neat if the 'writefs' command automaticaly saved the system .
Not 'persistence' per se, but 'persistence on demand' ....
I.E....If you install an app (or change some settings)and then do 'tazusb writefs' the app and settings would would be there on next boot and would be on any further usb's
made from that system ......
Generate your own LiveUSB media
To generate your own LiveUSB media, first you need to login as root with su and locate your usb storage device using the command:
# fdisk -l # normally /dev/sdb1
Then format and label your device (Warning: this will erase all data, make sure you specify the right device):
# tazusb format /dev/sdb1
And finally generate your LiveUSB media device:
# tazusb gen-liveusb /dev/sdb1
And that's all you need to do, you can now boot SliTaz from usb media (providing your computer bios supports this method).
Maintaining system settings
When you finish your LiveUSB session, make sure you maintain your installed packages, system settings, etc, by backing up the entire current filesystem with one the following commands:
fast compression, average filesize:
# tazusb writefs gzip
slow compression, smaller filesize:
# tazusb writefs lzma
no compression, larger filesize:
# tazusb writefs none
Each of these writes everything to a 'rootfs.gz' archive to be loaded the next time you boot.
Offline
Tazndis installed but not working; all dependencies are available and i've also installed both ndiswrapper and ndiswrapper-utils with related deps. No luck, after inserting root password it doesn't come up.
I'm willing to use slitaz on a Presario R3000 but if i can't get it to work wirelessly it's unusable for me.
Offline
[ Generated in 0.017 seconds, 7 queries executed - Memory usage: 1.59 MiB (Peak: 1.77 MiB) ]