You are not logged in.
Pages: 1
I did a fresh install of Slitaz 4.0's LiveCD and I got a message about the Kernel name not being found.
Is it safe to proceed with the latest kernel not being found?
Ref attached Photo.
Here is the tazinst.log file:
=== Tazinst: start at Mon May 14 08:15:30 UTC 2012 ===
Command: /usr/sbin/tazinst install /var/lib/tazinst.conf
1. Formatting / partition: /dev/sda1 (ext2)
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
244800 inodes, 978944 blocks
48947 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=1002438656
30 block groups
32768 blocks per group, 32768 fragments per group
8160 inodes per group
.
.
.
.
.
.
This filesystem will be automatically checked every 24 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
2. Installing SliTaz on: /dev/sda1
Decoder errorDecoder errorcpio: unsupported cpio format, use newc or crc
Warning: Kernel name not found, falling back to: 2.6.37-slitaz
3. Configuring host name: slitaz
4. Configuring root and default user account: tux
--- menu.lst -------------
# /boot/grub/menu.lst: GRUB boot loader configuration.
#
# By default, boot the first entry.
default 0
# Boot automatically after 8 secs.
timeout 8
# Graphical splash image.
splashimage=/boot/grub/splash.xpm.gz
# Change the colors.
#color yellow/brown light-green/black
# For booting SliTaz from : /dev/sda1
#
title SliTaz GNU/Linux (cooking) (Kernel vmlinuz-2.6.37-slitaz)
root (hd0,0)
kernel /boot/vmlinuz-2.6.37-slitaz root=/dev/sda1 quiet
--- menu.lst -------------
5. Running grub-install on: /dev/sda
Probing devices to guess BIOS drives. This may take a long time.
6. Installation complete. You can now restart (reboot)
=== Tazinst end at Mon May 14 08:17:34 UTC 2012 ===
Why would the title state cooking (title SliTaz GNU/Linux (cooking) (Kernel vmlinuz-2.6.37-slitaz))
since I installed from a Slitaz 4.0 LiveCD?
Also, for some strange reason I can't attach a tazinst.txt file (tazinst.log).
Thanks.
Larry
[attachment=10152,473]
Offline
The only way I was able to get Slitaz 4.0 installed to my 4G Centon USB was by chosing WEB : STABLE,
and by having an Ethernet connection.
I could NOT get a bootable install by chosing LiveCD (Slitaz 4.0 ISO downloaded and Burned to CDR).
That always gave me a Kernel Panic Error.
If I used the cooking version, that gave me the errors with the wrong Repo's and the 82 Update Errors
as noted on another Posting........
Thanks.
Larry
[attachment=10155,477]
Offline
Just for the record, I did a install via LiveCD two days ago and did not experience the problems you have come across. In my case I get the following...
cat /etc/slitaz-release
4.0
uname -r
2.6.37-slitaz
I did have problems with kernel modesetting but that's about all (so far!)
Offline
Tazinst LiveCD to USB flashdrive with no problem: http://forum.slitaz.org/topic/install-slitaz-to-usb-stick-make-it-act-as-harddrive
Optical drives and burned cdr/w can be unreliable.
You could have used the Slitaz-4.0.iso you burned the CDR with as an install source.
Give the installer the absolute path to the iso,and it mounts it.
When you choose web it downloads the iso to /tmp,verifys,and mounts the iso.
Why would the title state cooking (title SliTaz GNU/Linux (cooking) (Kernel vmlinuz-2.6.37-slitaz))
since I installed from a Slitaz 4.0 LiveCD?
The (cooking) part of the menu template should be removed.
Line 864=> http://hg.slitaz.org/slitaz-tools/file/75e873df3022/installer/tazinst
Line 583=> $KERNEL is the variable which is determined by the install source.
Offline
@lkraemer:
Can you launch the 'Check media' entry in the Slitaz 4.0 CD-ROM menu ?
Offline
Bellard,
Well, I am ashamed to say that I got three ERRORS on the Media Check.
ERROR 1000 Sector 6720
ERROR 1000 Sector 6722
ERROR 1000 Sector 6733
So, I've burned a new CDR and it checks good.
THANKS! I never would have thought about doing that.
Larry
Offline
Pages: 1
[ Generated in 0.016 seconds, 7 queries executed - Memory usage: 1.54 MiB (Peak: 1.77 MiB) ]