SliTaz Forum
You are not logged in.
Hey guys,
been trying to get a working persistent frugal install with the slitaz-5.0-rc2-iso for the last few days now.
Actually Im trying to add a couple programs to slitaz and customise the desktop, then have it all running in ram.
Theres no trouble installing to hdd, nor with my "vanilla" frugal.
i have experienced several problems "updating the frugal install" though.
First Scenario
I boot up vanilla frugal, make changes (updating packages is necessary at this point, otherwise the generated rootfs.gz caused kernel panic), and write a new rootfs.gz. now when I boot up the new frugal install with the new rootfs.gz I cant mount my ext3 partition (with my slitaz hdd install) with PCMan.
I mount via terminal, also gives me errors.
Then I try again via PCMan, and it works.
Any ideas whats the cause of this?
Also, when making a new rootfs.gz from this frugal install, (ie. added another piece of software, want to save it) and trying to boot it gives me some init errors.
-> not good, I need it to keep some changes without breaking.
Second Scenario
When doing a full hdd install, booting up into it, making changes (also updating pckgs), write new rootfs.gz, and booting up with that, i can only log in as root ("failed to excexute login command" otherwise).
When adding home=/dev/sda4 to the grub menu entry, it automatically mounts the entire ext3 filesystem to /home/ which i find strange. my experience with this up to now was finding the home/tux/ folder of the frugal in the root of my hdd partition.
i am writing a new rootfs.gz with "tazusb writefs none (i prefer not to compress for faster booting). tried the other two (lzma/gzip) but it doesnt change the issue. also tried the tazlito writeiso command. In my experience, it does the same apart from saving the output at different locations.
one would have thought it would be easiest generating a new rootfs.gz from a hdd install cause you can take your time configuring before you do so.
I read about ticking a checkbox somewhere when logging out after "enabling persistency mode". couldnt find any..
This is quite nerve-racking, as I'm not sure it might be another bug with tazusb/tazlito (the amount of hours i spent trying around until i came up with updating the packages!) or if im doing something wrong.
Anyone able to tell me a "best way" of making a custom bootable slitaz?
thanks in advance! Ill try around with the rolling iso from Sept. 7th next
Offline
I found rolling to be better than rc2 in general, so might be the way to go.
thanks fatmac!
re-creating (actually re-using) the rootfs.gz was no probem coming from the live rolling iso.
ill give it a go coming from a hdd install with rolling.
Offline
cant boot my new rootfs.gz created from a hdd install with rolling.. some kernel panic telling me about no proper ntfs being found.
->possible bug?
I'll stick to booting my frugal and re-writing my rootfs after every change 
i have another question concerning frugal slitaz:
when attaching an external screen to my laptop it shows an exact copy of whats seen on the laptop screen, including screen resolution.
the external one is bigger than my laptop screen and displays a black border on the right and bottom.
lxrandr doesnt recognize the plugged in screen at all, only mentions "default".
using a hdd install no border is displayed.
any thoughts on this?
Offline
bumping the topic here, cause its not working anymore (getting the kernel panic again with the ntfs error).
- whats the best way to make persistent changes on a frugal install of slitaz 5.0 rolling?
Offline
cant even get it to work with the rolling from September 7th like i could a few posts earlier..
here is the message i get after trying to use a newly-made rootfs.gz
[attachment=34371,1693]
could it be that it depends on the bzImage file? or some specific kernel parameters in grub?
this is very nerve-racking.
are there any slitaz 5.0 rolling persistent-frugal users here that could help me out by sharing their setups?
Offline
Did you have an NTFS filesystem mounted when you created your filesystem?
(Best I can do is suggest you re read the manual and work your way through line by line.)
no i didnt. i umount everything when writing the rootfs.gz.
i cant find a manual entry for keeping things persistent, only for a frugal install.
are you currently using a frugal install? if so, could you tell me your persisntency procedure?
Offline
are you currently using a frugal install?
Yes, I do: frugal install on sda1 and persistence on sda5. My entry in menu.lst:
# Boot SliTaz 5.0 - frugal install
#
title SliTaz 5.0 rolling 21/09/2014 - frugal install (kernel 3.2.53)
kernel (hd0,0)/boot/vmlinuz-3.2.53-slitaz rw root=/dev/null kmap=fr-latin1 nomodeset home=cb58a50f-6401-4f41-8cf3-409ec78a9f38
initrd (hd0,0)/boot/rootfs1409214.gz (hd0,0)/boot/rootfs1409213.gz (hd0,0)/boot/rootfs1409212.gz (hd0,0)/boot/rootfs1409211.gz
My HD (partitions appears "hd" and not "sd" because the [c]blkid [/c] command has been launched from SliTaz 4.0)
ceel@SliTaz:~$ blkid
/dev/hda5: UUID="cb58a50f-6401-4f41-8cf3-409ec78a9f38" TYPE="ext2"
/dev/hda1: UUID="e7133cab-f2bf-4686-b952-0b3bc0b14580" TYPE="ext3"
/dev/hda2: UUID="371fe7cb-5af6-49a3-95a2-e7eda59580a2" TYPE="swap"
/dev/hda3: UUID="36e30815-1a3f-469d-9e0c-3b6721d83f70" TYPE="ext2"
/dev/hda6: UUID="5234-C546" TYPE="vfat"
/dev/hda7: UUID="07A423B95696C36A" TYPE="ntfs"
ceel@SliTaz:~$
The partition where your /home is must be ext formated.
Offline
@K3nn3th
Look at top-right corner of your picture.
size 0x2e5020 is wrong
you forgot to update RC2 bzImage.
With any september-rolling size should be 0x2c0bd0
> could it be that it depends on the bzImage file?
This was the first you had to check.
Really it depends - "bzImage file" is linux kernel.
Offline
@az_ua: you have an eagle eye! it did the trick. i had accidentally kept the old one backuped during one of my reformattings.
@Ceel: I understand you have your home folder mounted to sda5. do you do persistent system changes, too? e.g. installing packages etc. how do you handle this?
I also see youre not using a bzImage file and are using three rootfs.gz's. Are there advantages?
thanks for taking your time, guys!
Offline
@K3nn3th
There is no /boot when running slitaz live frugal, only with a full install.
Updating files located in /boot such as the kernel on live install requires the user to manually move them from /boot to /home/boot before shut down.
[c]tazusb writefs[/c] will still need to be run to save other files from the tazpkg that install to locations other than /boot.
The kernel in linux-3.2.53.tazpkg is /boot/vmlinuz-3.2.53-slitaz
The kernel in persistent frugal install is /home/boot/bzImage
bzImage is a hard link to vmlinuz-3.2.53-slitaz created by tazlito when it builds the live cd iso.
tazusb copy_cdrom_files() uses the bzImage so it is kernel version agnostic.
To update the kernel on live frugal install with home=
[c]# tazpkg recharge[/c]
[c]# tazpkg -gi linux --forced[/c]
[c]# mv /home/boot/bzImage /home/boot/bzImage.old[/c]
[c]# cp /boot/vmlinuz-3.2.53-slitaz /home/boot/bzImage[/c]
I find it easier to rename the old bzImage and copy/rename the new kernel rather than copy /boot/vmlinuz-3.2.53-slitaz to /home/boot and edit the boot menu to change bzImage to vmlinuz-3.2.53-slitaz
Either way works.
Any files from tazpkgs that install to /boot such as syslinux have to be manually moved to /home/boot the same way.
Offline
@K3nn3th
do you do persistent system changes, too? e.g. installing packages etc. how do you handle this?
Not really. Frugal is for tests only; I use persistence for my notes and to store packages because sometime I go somewhere where I have no internet. When I want to save a configuration I create a new rootfs with tazusb writefs.
I also see youre not using a bzImage file and are using three rootfs.gz's. Are there advantages?
No. That's only for practical reasons. Concerning kernel, I have several versions of SliTaz installed (full and frugal); it's the way I found to distinguish the different versions. Concerning rootfs, the computer I use for tests has only a 20GB HD; to limit space on disk I store only 4in1 ISOs. This allows me to boot as well as core or gtk-only or justX or base simply editing the initrd line at boot.
Offline
Thanks for the clarification.
Another strange thing:
I boot up a new frugal rolling, which does not have the firmware for my wifi card yet.
After installing it through tazpanel (wifi-rtfirmware) via ethernet, configuring the wifi config, rewriting rootfs.gz and booting with it, only wifi seems to work.
My ethernet permanently has "disconnected" as status. even when i disable wifi and replug the eth cable.
Might this have something to do with having the eth cable plugged in (active connection) whie writing the rootfs.gz?
Yet another question: Anyone had any success connecting an external screen and using it as an extended desktop?
Offline
@K3nn3th
Slitaz network script configures one adapter.
If you require a second adapter on boot you can script it in /etc/init.d/local.sh
This brings up ethernet adapter with eth1 alias with static address 192.168.0.1
[c]ifconfig eth1 192.168.0.1 up[/c]
This feature speeds up connecting to different access points or switching between ethernet and wifi adapter but your still limited to one adapter.
Different connections can be pre-configured by either manually editing a copy of /etc/network.conf or configuring the connection in tazpanel and copy/rename /etc/network.conf to another location.
The different connection can be using a different adapter or a different configuration on an adapter.
Connecting to a different wifi access point or using ethernet adapter instead of wifi adapter.
Networking is restarted using the alternate configuration.
# /etc/init.d/network.sh restart alternate network configuration
More info: http://doc.slitaz.org/en:guides:network-script
Offline
@mojo: thanks a lot for your answers!
Now my only trouble..:
Anyone had any success connecting an external screen and using it as an extended desktop?
i found a nice method at http://forum.slitaz.org/topic/arandr-multi-screen-tool but its not working.
xrandr GUI only lists "Default Monitor" and doesnt let me change anything.
should i create a seperate thread for this?
Offline
Actually im having trouble with the wifi again 
as described before, i installed the wifi-firmware (rtl8192se), re-wrote rootfs.gz and booted from it.
WiFi worked fine.
then i rebooted the same rootfs.gz, and he-presto, the wifi device isnt found.
Although nothing was changed in the rootfs!
The following commands
su
modprobe -r rtl8192se
modprobe rtl8192se
make the Wifi adapter visible again, can detect my wifi network etc.
but once im connected, midori doesnt load anything..
edit: seems to work after having restarted my internet router.
obviously the module is not loaded properly at startup.
is there a way to automatically re-load the module at startup?
Offline
I am not an expert but you are jumping to a non obvious conclusion.
Do the symptoms you mention reproduce when you boot over again and again ?
Offline
@K3nn3th
Verify rtl8192se module is loading on boot.
[c]lsmod[/c] <= is rtl8192se listed ?
If not then add it to /etc/rcS LOAD_MODULES=
Reboot and verify it's loading.
If it is autoloading but still not initializing:
Add
[c]modprobe -r rtl8192se && modprobe rtl8192se[/c]
to /etc/init.d/local.sh
If it still doesn't initialize on boot:
Post any errors related to rtl8192se wifi driver, driver firmware load in /var/log/messages , /var/log/dmesg.log , /var/log/boot.log
Offline
thanks mojo.
behaviour wasn't the same every time i booted... strange.
I'm trying to set up a way to switch to an available wifi network (when im hooked up with ethernet) with configs i have with this menu tutorial:
http://doc.slitaz.org/en:guides:network-script
doesn't seem to work though. can anyone help me out on this? i'm confused about the open box menu part.
Offline
If I understand correctly what you are trying to do, you are ethernet-connected and want to activate wifi instead
You cannot have both at the same time as slitaz supports only one of them at any given time.
From what I remember it has been a pain in the a** until i found the right procedure, which was to use the slitaz panel, go to network, stop the ethernet (maybe it is called disable) then go the wifi page and enable wifi. If you do not first disable the ethernet connection, starting wifi normally fails, and it is hard to realise you should disable the ehternet (because if it was obious you would have done it in the first place)
It might differ slightly because i do not use this config anymore but once you found the right procedue it will work constantly and effortlessly.
Offline
@cristophe: thanks for the reply! I was in a hurry last night, sorry i didn't explain clearer.
I have:
- several variations of the network.conf file, for different networks stored in /home/tux/.network/.
- set up sudo to allow tux to run /etc/init.d/network.sh without a password
- a little shortcut in my applications menu ("Switch to Ethernet") which runs "sudo /etc/init.d/network.sh restart /home/tux/.network/ethernet" with no problems.
-> When I'm connected to WiFi at home, but i want to switch to ethernet for speed and stability reasons, this allows me to do it without TazPanel and passwords etc. Great!
Now, to do this the other way around (switching from my ethernet conection back to WiFi) its not quite as simple, because i have several WiFi configs, and only one can be active at once.
Instead of manually making a menu entry for every Wifi network i want to use (or will be using in the furture), i want to automate it.
The openbox menu in the bottom of this article ( http://doc.slitaz.org/en:guides:network-script ) seems to be automatically constructed through the script, with an entry for every file in the specified folder (renamed the /etc/network to /home/tux/.network/). This is exactly what im looking for.
but i cant get it to work.. i dont know where thi openbox menu can be found, the right-click menu on desktop didnt seem to change after reconfiguring..
Offline
Basically, you are trying to construct an automated script to switch wifi network.
With all respect due to the person who wrote the script you mention, I have no idea that it was well tested and will not break if run twice, or if it fits your need. (From what you say, it seems not)
Before doing that and copying other's scripts (where you have no idea if the configurations or intended use are even comparable, not even the same) I would make sure i have a robust manual procedure, then mimic that with a script....
I doubt in any case that it will be any faster than manually entering the password when switching network, if you add up all debug time. Where would be the fun if it was straightforward, I get that, too.... 
Offline
@mojo: it says ERROR: Module is in use when trying to remove and add it during boot
i got a small script just run whenever it doesn work to un- and re-load the rtl8192se module.
any nicer workarounds?
@cristophe: the script is for a pipe menu in openbox. its only supposed to output the same command multiple times wach with a parameter according to a single filename. its not working though.. the problem is the scripts only not writing the data in the xml-format opnbox wants it in
in the long run it would save me loads of time. (2 clicks instead of entering user info etc)
Offline
A quick bump on this topic, cause im still having some issues with my frugal installs.
maybe someone has any advice on this:
1) my wifi module(rtl8192se) still isnt loaded correctly at startup. i always have to manually modprobe -r rtl8192se and reactivate it manually in order to get it to work.
actually, with the current rolling release i cant get it to work at all.
2) 3rd-party software like sublime-text-3 or chrome are installed to /opt/. is there a way to include /opt/ into tazusb's packaging? its a bit annoying having to move the files to a system dir thats included and manually changing the desktop files.
3) Every now and then my sudo command stops working. it would not let me type a password (it somehow jumps to the next line) and i have to force-reinstall sudo to get it running again. (annoying when using sudo in scripts)
4) I'm still having trouble with the size of my rootfs.gz files. I would like to use uncompressed ones to speed up boot time, but at approx. 500 mb i get an error saying the initramfs is too large.
Is this bootloader related?
help is greatly appreciated!
Offline
[ Generated in 0.018 seconds, 7 queries executed - Memory usage: 1.6 MiB (Peak: 1.77 MiB) ]