SliTaz Forum
You are not logged in.
Pages: 1
I am looking to install a justx flavor of SliTaz 5.0.RC2 on a ssd but don't seem to be having luck finding it as a standalone iso on SliTaz.org or installing it manually (see next).
I followed "manual by hand instructions" for installing 3.0, decompressing rootfs4 and rootfs3 from the cdrom boot directory (I did this since these are the only 2 decompressed when I boot justx from 5.0 CD Live). Bottom line.. didn't work.. doesn't complete booting with this info...
mount: can't read 'etc/fstab': No such file or directory (my comment: sure I can create it but why in other installs do I not have to create fstab?)
mkdir: can't create directory '/dev': File exists (my comment: must be running a predefined script)
udhcpc: ioctl 0x8933 failed: No such device (my comment: okay.. got me on that one)
Currently defined functions: (my comment: pretty much list all the busybox commands below that line)
/ # (my comment: yep thats a prompt)
Ideas, help (cli instructions are welcome as it helps me learn but I'll take what I can get)?
Thank you all, appreciate having your expertise..
Allen
Offline
Hello allen,
The doc is not realy true for 4.0. When decompressing rootfs4&3.gz, did you use these commands and in this order:[c]
# lzma d rootfs4.gz -so | cpio -id
# lzma d rootfs3.gz -so | cpio -idu
[/c]
I thought I updated the doc but only the french version is right. I'll do it as soon as I'll have time (or may be I'm going to wait for 5.0)
Offline
5.0-rc2 kernel will not boot a full install on a usb flash drive so it likely doesn't work on an sd card.
I would boot a live cd with an internet connection.
Mount the sd card with the install,and cd into the boot folder.
Rename the old kernel or delete it.
Download the rolling kernel.
wget ftp://cook.slitaz.org/linux/taz/linux-3.2.53/fs/boot/vmlinuz-3.2.53-slitaz
If it won't boot with the new kernel chroot into the install and update.
http://forum.slitaz.org/topic/install-slitaz-rc-2-on-a-usb-drive
Offline
Thank you both for your prompt replies.
Ceel...
I tried using the two commands you posted but the same boot condition exist. Since I did not originally use -idu for rootfs3.gz decompression (only -id) should I reformat and start over using the commands you posted?
mojo...
I should have made myself more clear.. the drive is a solid state drive, not and SD card. The drive I am installing to is an ATA flash device as the IDE Primary Master in BIOS. I have successfully installed SliTaz 4.0 to this device before. I can attempt to install from Live CD the entire 5.0.rc2 installation to confirm it will indeed boot from this solid state drive if you suggest I do so. My initial goal was to simply install justx. Again, 4.0 has installed to the ssd drive without any problems. 5.0.rc2 may not.
Again thank you..
Allen
Offline
mojo...
I just installed 5.0.rc2 to the ssd (ATA solid state drive) and it boots without a hiccup. Any way to install justx or base? I want a clean install to build from.
Thank you,
Allen
Offline
Mount the install target partition.
Either loop mount the 5.0-rc2 iso or mount the live cd/live usb to source the required rootfs*.gz.
Base: copy /boot/rootfs4.gz from source to root of the install partition.
JustX: copy /boot/rootfs4.gz and rootfs3.gz from source to root of the install partition.
Change directory to the root of the install partition.
Extract base filesystem
[c]# lzma d rootfs4.gz -so | cpio -id[/c]
Extract additional files required for justX:
[c]# lzma d rootfs3.gz -so | cpio -idu[/c]
After boot cleanup
[c]# rm /rootfs*gz[/c]
Offline
@allen,
I've never test the manual procedure installation with 5.0. Time that I have a look.
I thought mojo was on the right way in his first post because I didn't pay attention at one of your comments
pretty much list all the busybox commands below that line
This is a known problem with SDcard.
I'm not sure that reformating and starting over using the 2 commands will bring something new but you can try.
May be you can try with the last rolling (http://mirror.slitaz.org/iso/rolling/slitaz-rolling.iso because if you succeed to install rc2 and then update you'be closer to rolling than rc2.
I'm going to try partial and entire manual installations tonight with RC2 and rolling and I'll tell you.
Offline
I have no idea what is going on in this thread.
OP is writing about issues with SSD. People are discussing that SD card installations don't work.
Alright, so first of all, SD card installations work just fine. Thing is though, it'll want to boot off of the internal drive instead of the SD card. I'm not sure if this is an issue present when installing to /dev/sdb as a second internal drive, but when installing to /dev/sdb as a SD card (in my case), it'll attempt to boot from /dev/sda.
The reason for this, I believe, is that the installation thinks it is being installed to /dev/sda by default, even if it isn't, and thus writes a wrong configuration file.
However, looking into the GRUB editor (press E when GRUB comes up), it seems the kernel [...] line is using a different root configuration than what would be needed when booting an SD card.
My solution to this was pretty simple. Correct the mistake once in GRUB when booting up, and when the system has fully started, it is useful to make that change permanent by opening /boot/grub/menu.lst, and changing that same line again.
The SD card is likely to be the last device initialized and booted from, however booting from an SD card should be a no-op for most users as it is simply integrated as yet another USB-like device internally on most machines.
Now, it is important to note however that the line
[c]root (hd0,0)[/c]
should NOT be changed. I repeat, it should NEVER CHANGE. That line should stay the same, provided that it works in the first place. It is the
[c]kernel /boot/vmlinuz-3.2.53-slitaz root=/dev/sda1 [...][/c]
line that should be changed.
Furthermore, I'd like to add that I have no idea what partition it is you've installed it to, so your best bet probably is to just try /dev/sdX1, where X is a, then b, c, d, then e, f, and so on, until you've tried as many letters as you have disk drives, USB ports, internal disks, and SD card readers in your computer.
That is, start out with
[c]root=/dev/sda1[/c]
if it doesn't work,
[c]root=/dev/sdb1[/c]
then if it still won't boot correctly, go ahead and try
[c]root=/dev/sdc1[/c]
And continue along the alphabet until it works.
Remember to open the /boot/grub/menu.lst file as root (admin) when the system has booted, and change the same line in that file to the same value.
Offline
Thank you all for your continuous support. First the short of it..
Ceel and mojo.. 5.0.rc2.justx is up and running.
necrophcodr.. you were more close to the fact then you realize. Wish you had posted that 6 hours ago when I was burning the midnight lamp while pulling out my hair (what little I have).
I followed Ceel/mojo instructions.. 2 times and still the same boot persisted: failed to completely boot (see first post). It was seeing that first error message once again: [c]mount: can't read 'etc/fstab': No such file or directory[/c] that frustrated me enough to see if I could, from the basic prompt I was left with, look at the directory/files on the ssd to see if fstab did exist (again this is NOT an SD Card, but a true ATA/IDE solid state drive. It has no adapter, connecting directly to the cpu's IDE port).
Before I continue, in hindsight I should have attempted the following as soon as 5.0.rc2 failed to fully boot...
At the basic prompt I listed the directory/files (ls -a) and it just didn't make sense what I was seeing. It was NOT the typical SliTaz directory, at least not what resulted from decompressing rootfs3&4.. it was missing many directories. Not making sense I identified my devices (blkid) and immediately spotted the problem. As necrophcodr pointed out my menu.lst was incorrectly pointing to the wrong root device (keep reading).
But wait.. the menu.lst file I used was from SliTaz 4.0 that booted on the same computer. I simply copied it over and edited the vmlinuz version. SliTaz 4.0 always booted from /dev/hda1 but now 5.0.rc2 has assigned the boot drive as /dev/sda1. Why?(I asked myself that question but if one of you has the answer, go for it, I'm all ears)?
I was also wondering why the basic busybox prompt? Shouldn't the system/SliTaz simply have failed to boot rather then fall short of fully booting? When time permits I'll step backwards to booting as /dev/hda1 to study why.
Thank you all.. and yes Ceel I will again reinstall using rolling. Hey I'm a pro at it now. 
Allen
Offline
@allen
mkdir: can't create directory '/dev': File exists (my comment: must be running a predefined script)
udhcpc: ioctl 0x8933 failed: No such device (my comment: okay.. got me on that one)
Currently defined functions: (my comment: pretty much list all the busybox commands below that line)
/ # (my comment: yep thats a prompt)
I was also wondering why the basic busybox prompt?
Ref:
http://forum.slitaz.org/topic/question-about-50#post-32863
Offline
@allen,
I first intalled justX on my internal HD from slitaz-5.0-rc2 -> boot=OK
Then as I cannot reproduce your configuration, justX on a USB key -> KO (same as you)
With rolling, justX installed on a USB key -> boot=OK
Mojo is right. It should work if you chroot and update or simply re-install from rolling.
And yes you have to reformat or erase directories on your disk; if you overwrite you'll have other troubles.
Offline
I just can't express how impressed I am with everyone's continued support. You are all outstanding! Thank you!
I have successfully installed 5.0.rolling per Ceel's suggestion. After installing I decided I really didn't need [c]x[/c] and reformatted and re-installed only [c]base[/c] ([c]rootfs4[/c]). All is well but I find when I run [c]tazhw detect-pci[/c] I receive no PCI detected data.. like nothing exist though if I run the same command from Live CD cli I receive a complete printout. Or from [c]base[/c] if I run [c]lspci[/c] I get no human information even with option [c]-v[/c] or [c]-vv[/c]. Is there a simple package I need to install to receive such human information from these important commands?
Please advise If I should have started a new thread for the above question. I'm new to the SliTaz/Linux community and as such would like to maintain protocol if/when required.
Allen
Offline
Hello allen,
I didn't see your last post yesterday evening...
Cool that your justX is now running!
SliTaz 4.0 always booted from /dev/hda1 but now 5.0.rc2 has assigned the boot drive as /dev/sda1. Why?(I asked myself that question but if one of you has the answer, go for it, I'm all ears)?
From kernel 3.2.50, IDE devices are sd and not hd anymore.
http://forum.slitaz.org/topic/testing-iso-with-kernel-3250#post-26776
Offline
@Ceel
From kernel 3.2.50, IDE devices are sd and not hd anymore.
http://forum.slitaz.org/topic/testing-iso-with-kernel-3250#post-26776
Thank you for answering my question. I had wondered why the change from hdx to sdx.
Offline
I have successfully installed 5.0.rolling per Ceel's suggestion. After installing I decided I really didn't need x and reformatted and re-installed only base (rootfs4). All is well but I find when I run tazhw detect-pci I receive no PCI detected data.. like nothing exist though if I run the same command from Live CD cli I receive a complete printout. Or from base if I run lspci I get no human information even with option -v or -vv. Is there a simple package I need to install to receive such human information from these important commands?
Busybox lspci doesn't output human readable information.
Install the standalone version.
[c]# tazpkg -gi pciutils[/c]
Offline
@mojo
Busybox lspci doesn't output human readable information.
Install the standalone version.
[c]# tazpkg -gi pciutils[/c]
Exactly what was needed. Thank you!
Offline
Pages: 1
[ Generated in 0.018 seconds, 7 queries executed - Memory usage: 1.57 MiB (Peak: 1.77 MiB) ]