You are not logged in.
(the periods continue a long ways mixed with some symbols)
/* XPM */
static char * grub_splash_xpm[] = {
"640 480 15 1",
" c None",
". c #331B0B",
"+ c #3A1C0A",
"@ c #44200B",
"# c #52270C",
"$ c #632E0C",
"% c #6F310E",
"& c #79370F",
"* c #8D4011",
"= c #9F4813",
"- c #AB4C10",
"; c #B85214",
"> c #C2570E",
", c #CB5B16",
"' c #D66115",
"................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................",
Offline
I see file corruption on your end.
You should see this:
[c]ls -la /boot/grub[/c]
[c]total 452
drw------- 2 root root 4096 Jan 20 02:18 .
drw------- 3 root root 4096 Jan 20 02:17 ..
-rw------- 1 root root 197 Jan 20 02:18 default
-rw------- 1 root root 15 Jan 20 02:18 device.map
-rw------- 1 root root 11736 Jan 20 02:18 e2fs_stage1_5
-rw------- 1 root root 10788 Jan 20 02:18 fat_stage1_5
-rw------- 1 root root 10036 Jan 20 02:18 ffs_stage1_5
-rw------- 1 root root 9972 Jan 20 02:18 iso9660_stage1_5
-rw------- 1 root root 11488 Jan 20 02:18 jfs_stage1_5
-rw------- 1 root root 474 Jan 20 02:18 menu.lst
-rw------- 1 root root 10104 Jan 20 02:18 minix_stage1_5
-rw------- 1 root root 14516 Jan 20 02:18 ntfs_stage1_5
-rw------- 1 root root 12488 Jan 20 02:18 reiserfs_stage1_5
-rw------- 1 root root 65367 Jan 20 02:18 splash.xpm.gz
-rw------- 1 root root 512 Jan 20 02:18 stage1
-rw------- 1 root root 214078 Jan 20 02:18 stage2
-rw------- 1 root root 10312 Jan 20 02:18 ufs2_stage1_5
-rw------- 1 root root 9684 Jan 20 02:18 vstafs_stage1_5
-rw------- 1 root root 12732 Jan 20 02:18 xfs_stage1_5[/c]
Offline
Should I see that opening from windows ?
I lost the ability to boot to Slitaz.
I bought 2 new usb sticks.
Used LiLi to install Slitaz 4.0
Booted perfectly on older (5 years) Pentium system
Wouldn't boot on newer (1 year) Atom system
After trying this and that with both sticks (Atom is my target system)
Now I get boot error on Pentium
and endless periods going down screen on Atom (redoing install as first one)
I've had similar many times before (Slitaz and other distros)
It's like the sticks go bunk, but they're too new for that.
???????????????
Offline
Should I see that opening from windows?
You installed slitaz to the stick using LiLi running on windows.
Windows wrote the files and should read and list them properly.
The easiest way to start with slitaz is to use a dedicated computer without windows.
Mixing windows and linux is more trouble than pure linux.
Test flash drive in windows with ChkFlsh.
It may destroy any data on the drive so copy it off before the test.
Offline
Eeeeerrrrrrrgggggg .....
I'll try CD and hope for better luck.
If I simply burn Slatz 4.0 iso to CD
it should boot up on Atom system ?
Then use install app to install to SSD ?
Offline
O.K.
I have installed Slitaz 4.0 on HD of Atom system from CD
(using install tool) ........... All is well !
BUT !
When I install to USB from same CD (again with install tool)
all appears OK but PC fails to boot from it.
Ignores it and goes on to HD .
??????????
GRUB on both HD and USB says "Default"
Offline
Start from HD
Insert your USB stick
Open a terminal; become root and post result of [c]fdisk -l[/c]
Did you configure your bios to boot from USB?
Offline
Thank You.....Yes BIOS set to boot USB first (I do it all the time)
[attachment=27774,1301]
Offline
OK; wanted to be sure the USB stick had the boot flag.
You said that PC fails to boot from USB; no message? (like [c]More than one active partiton[/c] or something else...)
Of course, you've installed GRUB on your USB stick; post the contain of /boot/grub/menu.lst of the stick.
Offline
No message ....... It's like it is not there
I depended on the installer tool for GRUB
[attachment=27784,1303]
Offline
On a second (older) PC it at least tries to boot. I get :
Booting Slitaz GNU(Linux)(cooking)(Kernal vmlinuz-2.6.37-slitaz)
filesystem type is ntfs, partition type 0x07
kernal /boot/vmlinuz-2.6.37-slitaz root= /dev/sdb1 quiet
Error 15: file not found
Press any key to continue..._
Offline
Hi hitsware,
Your menu.lst is correct. I thought as your computer starts on HD, GRUB was not or bad installed on the MBR of the stick. But if GRUB starts on an older PC...
Error 15: file not found
GRUB doesn't find /boot/vmlinuz-2.6.37-slitaz
On an old PC, probably the HD is hda and not sda. In this case your stick is sda and not sdb anymore.
Replace in menu.lst [c]root (hd1,0)[/c] by [c]root (hd0,0)[/c] and try to boot again on the old PC.
Offline
Thank You Ceel for the time ..... 
I get same message
Right .... The usb slots are different on this PC
I can map them ... ??
What does the h numbers have to do with it ?
Shouldn't everything be on the usb ?
I want it to act like a HD ....
Offline
What does the h numbers have to do with it ?
Forget it; it was my biggest stupidity of the day, it's time I eat something...
GRUB identifies all disks as "hd" so regardless the type of the HD, ide or sata, it will always be hd0 and the USB... hd1. It doesn't change anything, it was really stupid!
Well. GRUB starts, that's the good thing. It doesn't find /boot/vmlinuz-2.6.37-slitaz because
- vmlinuz-2.6.37-slitaz doesn't exist but if you install SliTaz with TazPanel, I don't see why it wouldn't exist
- the stick is not recognize as the second disk
If you can run the live CD on the older PC try the command fdisk -l so we can see what are the disks on it
Offline
Just a thought: what about yours usb system file format? Is it ext2/3 or fat32?
Offline
@ toto ...... ext3 ......... I want the usb stick to be persistent and work on any PC
I may try ext2 .... any differance you think ?
At one time I had Slitaz boot on both PCs with FAT32 but evedently there is no simple
way to get persistence . (keep a couple of apps (Wine and Minicom))
The installer worked so well with the HD, I'm surprised at the complication with the
stick .............
[attachment=27798,1304]
Offline
OK hitsware,
According to your las post, there are 3 HD on the computer: sda, sdb and sdc. So, on this PC GRUB sees your USB key as the 4th HD.
To make your it booting on it you have to replace (hd1,0) by (hd3,0) and GRUB will find vmlinuz-2.6.37-slitaz.
If it works on this computer, this means your key is OK and your initial problem comes from the Atom.
But, to boot on Atom you'll have to modify the menu.lst again. I propose to create a second entry in your menu.lst; copy paste the lines below in it. In this way you'll be able to boot on the old PC as well as on the Atom (as soon as we'll have find where the problem is on Atom of course)
# /boot/grub/menu.lst: GRUB boot loader configuration.
# By default, boot the first entry.
default 0
# Boot automatically after 8 seconds.
timeout 8
# Change the colors.
color yellow/brown light-green/black
# Graphical splash image.
splashimage=/boot/grub/splash.xpm.gz
# For booting SliTaz from Atom
title SliTaz 4.0 (kernel 2.6.37) full install on USB stick, from Atom
root (hd1,0)
kernel /boot/vmlinuz-2.6.37-slitaz root=/dev/sdb1 quiet
# For booting SliTaz from old PC
title SliTaz 4.0 (kernel 2.6.37) full install on USB stick, from old PC
root (hd3,0)
kernel /boot/vmlinuz-2.6.37-slitaz root=/dev/sdd1 quiet
Offline
> According to your las post,
> there are 3 HD on the computer:
> sda, sdb and sdc.
2 HD ..... sdc is Slax on a USB stick
that I booted from to get into Linux
to access the info .......
Offline
Then
# For booting SliTaz from old PC
title SliTaz 4.0 (kernel 2.6.37) full install on USB stick, from old PC
root (hd2,0)
kernel /boot/vmlinuz-2.6.37-slitaz root=/dev/sdc1 quiet
Offline
At least something different
Now I get:
GRUB4DOS 0.4.4 2012-04-09, memory 572k/2020M menu end: 0x4918A
[ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a
device/filename. ]
grub>
Then if I enter 'boot' I get:
kernal must be loaded before booting
Offline
Hello hitsware,
I've made a mistake: when starting GRUB from a USB stick, the stick will always be seen as hd0 by GRUB. The good syntaxes for menu.lst in /boot/grub of the stick is
[c]
# /boot/grub/menu.lst: GRUB boot loader configuration.
# By default, boot the first entry.
default 0
# Boot automatically after 8 seconds.
timeout 8
# Change the colors.
color yellow/brown light-green/black
# Graphical splash image.
splashimage=/boot/grub/splash.xpm.gz
# For booting SliTaz from Atom
title SliTaz 4.0 (kernel 2.6.37) full install on USB stick, from Atom
root (hd0,0)
kernel /boot/vmlinuz-2.6.37-slitaz root=/dev/sdb1 rootdelay=5 quiet
# For booting SliTaz from old PC
title SliTaz 4.0 (kernel 2.6.37) full install on USB stick, from old PC
root (hd0,0)
kernel /boot/vmlinuz-2.6.37-slitaz root=/dev/sdc1 rootdelay=5 quiet
[/c]
Note I've added an instruction [c]rootdelay=5[/c]. This lets time to the kernel to find the stick or you could have a kernel panic at boot.
Offline
O.K. ... Thanks again ! ... I'll try that ....
I think there may be a problem that since default is '0'
the old PC will try to use the Atom script ?
It would be nice if the default could be 'boot SliTaz from any PC'
Offline
[c]default 0[/c] in menu.lst means that GRUB will boot with the first entry (SliTaz 4.0 (kernel 2.6.37) full install on USB stick, from Atom) if you don't hit a key within the 8 seconds ([c]timeout 8[/c]) after the menu displays.
To point automatically the second entry of the menu change [c]default 0[/c] to [c]default 1[/c]
To increase/decrease the time to start automatically, change the value of [c]timeout 8[/c]. To suppress the automatic start, comment the line with #:[c]# timeout 8[/c]
To start SliTaz on the old PC, select SliTaz 4.0 (kernel 2.6.37) full install on USB stick, from old PC with the [Down] key.
You cannot start SliTaz with the same entry on the 2 computers because their hardware are different: Atom has only 1 HD, sda for the kernel, so the stick will be sdb. The old computer has 2 HD, sda and sdb, so the stick will be sdc for the kernel; that's why you need 2 entries in menu.lst.
Offline
(Old PC) Only the Atom entry shows up....counts down......then does nothing
(Atom PC) Same as before....ignores USB and boots from HD
Seems we're getting nowhere
Maybe there is a reason no one suggests
full install to USB ? Though the TazPanel sorta implies it will work ...
(As do some Ubuntu (but then that's with Ubuntu) forum inputs.) ????
Are you trying any of the advices you are helping me with ?
Offline
Yes you can do a full install on USB. I've done my first full install (SliTaz 3.0) on a 1GB stick a few years ago and install SliTaz 4.0 on a 2GB stick in 2012 April.
I now use this last key pricipally to boot SliTaz on my professional computer; I'm not authorized to install anything on it so I use the boot loader of the key to launch frugal install. Here is my menu.lst:
[c]
default=0
title SliTaz rolling 19/01/2014 (kernel 3.2.53, frugal install on sda2)
kernel (hd1,1)/frugal/rolling/vmlinuz-3.2.53-slitaz rw root=/dev/null kmap=fr-latin1 vga=normal
initrd (hd1,1)/frugal/rolling/rootfs4.gz (hd1,1)/frugal/rolling/rootfs3.gz (hd1,1)/frugal/rolling/rootfs2.gz (hd1,1)/frugal/rolling/rootfs1.gz
title SliTaz 4.0 core (kernel 2.6.37, frugal install on sda2)
kernel (hd1,1)/frugal/4.0/bzImage rw root=/dev/null kmap=fr-latin1 vga=normal nomodeset sound=noconf screen=text
initrd (hd1,1)/frugal/4.0/core/rootfs.gz
title SliTaz 4.0 (kernel 2.6.37, full install on sdb1 from S752)
root(hd0,0)
kernel /boot/vmlinuz-2.6.37-slitaz root=/dev/sdb1 kmap=fr-latin1 vga=normal rootdelay=5 nomodeset screen=text
title SliTaz 4.0 loram (kernel 2.6.37, frugal install on sda2)
kernel (hd1,1)/frugal/4.0/bzImage rw root=/dev/null kmap=fr-latin1 vga=normal nomodeset sound=noconf screen=text
initrd (hd1,1)/frugal/4.0/loram/rootfs.gz
title SliTaz 4.0 core (kernel 2.6.37, from iso on sda2)
map --mem --heads=0 --sectors-per-track=0 (hd1,1)/frugal/4.0/core/slitaz-4.0-core.iso (hd32)
map --hook
kernel (hd32)/boot/bzImage rw root=/dev/null vga=normal
initrd (hd32)/boot/rootfs.gz
title SliTaz 3.0 Xorg (kernel 2.6.30.6, frugal install on sda2)
kernel (hd1,1)/frugal/3.0/vmlinuz-2.6.30.6-slitaz rw root=/dev/null kmap=fr-latin1 vga=normal
initrd (hd1,1)/frugal/3.0/rootfs.gz
title SliTaz 2.0 (kernel 2.6.25.5, frugal install on sda2)
kernel (hd1,1)/frugal/2.0/vmlinuz-2.6.25.5-slitaz rw root=/dev/null kmap=fr-latin1 vga=normal
initrd (hd1,1)/frugal/2.0/rootfs.gz
title SliTaz 1.0 (kernel 2.5.24.2, frugal install on sda2)
kernel (hd1,1)/frugal/1.0/vmlinuz-2.5.24.2-slitaz rw root=/dev/null kmap=fr-latin1 vga=normal
initrd (hd1,1)/frugal/1.0/rootfs.gz
[/c]
The entry SliTaz 4.0 (kernel 2.6.37, full install on sdb1 from S752) runs SliTaz 4.0 full install on the USB stick (SliTaz 4.0 does not like recent hardware; with the Fujitsu Notebook S752, I've had to add options [c]nomodeset[/c] and [c]screen=text[/c] to be able to boot).
Other entries allow me to boot the last rolling or flavours in frugal mode; files are on my HD sda2.
On the Atom, I think the problem does not come from your stick but from the PC. It ignores USB like if in the boot order HD was before USB ports
Offline
[ Generated in 0.018 seconds, 7 queries executed - Memory usage: 1.6 MiB (Peak: 1.77 MiB) ]