SliTaz Forum
You are not logged in.
I did that. There were two lines: a short one that ended with "hd0,0"; and a long one, with Slitaz version I think, etc, that ended with hda1.
I don't think I changed anything, but one time it booted into SliTaz. The same problem with the screen remained; so I ran those 3 commends to fix the screen, which didn't fix it right away, rebooted; and it didn't boot into SliTaz anymore; only the screen turned off while the computer is on, every time.
Offline
Sounds like you did edit the grub boot line, it won't stay that way after a reboot, it needs to be changed once you are up & running, in your actual installation.
At a rough guess I'd say you probably altered the first grub boot line to read hd1,0 & the second to hdb1.
So give it another go, this time when you get logged in, as the root operator, change the grub config file (/boot/grub/grub.lst) before doing anything else. Then do whatever you need to sort your screen.
That way at least you will be able to boot back in.
I'm sure I didn't change something deliberate as that. I just clicked "e" and entered each option; maybe clicked Enter while in there; something like that.
I already tried booting, many times; tried to delete the first entry etc. Nothing worked.
I don't have the file "grub.lst"; maybe you meant "/mnt/sdb1/boot/grub/menu.lst".
I can view and change those files from Puppy.
Here's what this file says:
# /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/hdb1
#
title SliTaz GNU/Linux (cooking) (Kernel vmlinuz-2.6.37-slitaz)
root (hd0,0)
kernel /boot/vmlinuz-2.6.37-slitaz root=/dev/hdb1 quiet
Offline
Yes sorry, menu.lst is what I meant.
I just installed 4.0-core to an 'image' file to use with qemu & had to change hd1,0 to hd0,0 to get it to boot properly.
(The /dev/hdd1 is, presumably, just the directory slitaz uses as /.)
Sorry for the confusion, using SliTaz only occasionally now, some times I forget the differences with my regular distro.
So what can I do?
Offline
Well, I think you can use your 'Puppy' to change the (installed slitaz) /boot/grub/menu.lst line to read hd0,0 - that should let you boot into slitaz.
Then you will need to carry out the lines of code to fix your screen as before, only this time around it should get saved & be there when you log back in the next time.
All these commands need to be run as the root user, (with an internet connection), in a terminal & press enter after each command.
tazpkg get-install linux-agp
tazpkg get-install linux-drm
tazhw setup ati
After that I think you will need to reboot for them to take effect.
I hope that gets you up & running.
To edit the grub menu hit the e key with slitaz entry highlighted
Change
kernel /boot/vmlinuz-2.6.37-slitaz root=/dev/hdb1 quiet
to this
kernel /boot/vmlinuz-2.6.37-slitaz root=/dev/hdb1 nomodeset screen=1024x768
To try these temporary settings hit the b key
Offline
Right now - the problem is not the screen; it's that I cannot boot into the OS. And I already ran those commends, the one time I was able to boot.
In the file "menu.lst" - I changed the line to "kernel /boot/vmlinuz-2.6.37-slitaz root=/dev/hdb1 nomodeset screen=1024x768".
Now it continued to boot, longer than it took it to turn off the screen, before; and then it was stack with the last line saying something like "Requesting information from the kernel...).
So I think we can understand from that, that it does have something to do with this line. Maybe it needs to be changed to something else.
Offline
On my image file installation, the grub boot screen has
root (hd0,0)
kernel /boot/vmlinuz-2.6.37-slitaz root=/dev/hdd1 quiet
& that works OK for me, (first hard drive).
So I think maybe you will need
root (hd1,0)
kernel /boot/vmlinuz-2.6.37-slitaz root=/dev/hdd1 nomodeset screen=1024x768
as you are running from the second hard drive.
When I change it to "hd1,0" - there's an error of not finding the file; whereas usually - it starts to run the line which are part of the booting process; but in the middle, maybe when it needs to boot into some GUI - instead, the screen switches off.
I didn't try to change "hdb1" to "hdd1"; was that a misspell or should I try that? In "menu.lst", it says in a few places "hdb1".
Offline
I think I would give it a try changing root=/dev/hdd1 at the grub boot stage, & if it works, then change it in /boot/grub/menu.lst - my install would normally have been root=/dev/sda1 but if I put that in (or /dev/hda1) it won't boot.
"hdd1" didn't work.
What I tried to say before, judging by the text running and the time it takes - that seems close to how much it takes when it does boot - it seems that SliTaz goes through the boot process, and either fails at the end, or maybe more in the middle. Maybe it does boot; but only the screen turns off.
So I think it does find the right disk; because it starts to boot. When the disk is wrong - it doesn't start to boot.
Offline
Did you try what mojo said - nomodeset
Yes; and I wrote what happened. :-)
Offline
Well in that case, I'm out of ideas, sorry.
Alright; maybe someone will have an idea. Thank you.
Offline
Hello MrAccident,
Can I try to help you to boot?
I read this thread and saw something that seems wrong to me in your /boot/grub/menu.lst (your post http://forum.slitaz.org/topic/slitaz-40-doesnt-recognize-my-screen/page/2#post-30319 ). The entry to boot SliTaz is[c]
# For booting SliTaz from : /dev/hdb1
#
title SliTaz GNU/Linux (cooking) (Kernel vmlinuz-2.6.37-slitaz)
root (hd0,0)
kernel /boot/vmlinuz-2.6.37-slitaz root=/dev/hdb1 quiet[/c]
For me, if [c]root (hd0,0) [/c]then in the kernel line you should have [c]root=/dev/hda1[/c].
If the file system is really installed on the first partition of the second hard disk ([c]root=/dev/hdb1[/c]) then the first line should be [c]root (hd1,0)[/c].
If this doesn't work I suggest you boot from the LiveCD in SliTaz base, log in as root (root then password=root), type [c]fdisk -l [/c]and post the output of the command.
Offline
Hi Ceel.
Tried those options. The only thing that gets me anywhere is: (hd0,0) and hdb1; otherwise it's some error.
The last time I tried to boot - I got to a text based login screen which said something like:
"Welcome to SliTaz...
login:"
I don't know what to write there; so I wrote "root". Then there was a line with "password:"; I wrote root again. Then some more text and another line where I need to write something (sorry, don't remember what it said exactly. I can check again if needed); I just wrote something; and it started to write things about my mouse etc.
Anyway, here's the result of "fdisk -l":
Disk /dev/hdb: 320.0 GB, 320071851520 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hdb1 38656 38837 1459200 83 Linux
/dev/hdb2 2 38655 310488255 f Win95 Ext'd (LBA)
/dev/hdb3 38837 38914 613376 82 Linux swap
/dev/hdb5 * 2 38655 310488223+ 7 HPFS/NTFS
Partition table entries are not in disk order
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 1008 8089600 83 Linux
Partition 1 does not end on cylinder boundary
/dev/sda2 1084 121602 968058000 5 Extended
Partition 2 does not end on cylinder boundary
/dev/sda3 1008 1084 613376 82 Linux swap
/dev/sda5 1084 121602 968057968+ 7 HPFS/NTFS
Partition table entries are not in disk order
Offline
So you have 2 HD
[*]a 320 GB: /dev/hdb (why not hda??? may be because where it is connected on your main board); I suppose it is an internal HD. Is it this one where you've installed SliTaz?
[*]and a 1000 GB: /dev/sda that I suppose to be an external drive, connected to a USB port and where you've installed Puppy. Right?
I can see each of them have a boot partition. How does your computer boot?
[*]you ask in your bios setting to boot on USB first?
[*]you use a multiboot menu pressing a key (ie: [F12]) at power on?
[*]or you just wait for the GRUB menu?
What's the model of your computer and how many RAM do you have?
When SliTaz boots in console mode and you have this message on screen
[c]Welcome to SliTaz...
login:[/c]
you can log in
- as tux user: type [c]tux [/c]then hit [Enter] or
- as super user: type [c]root [/c]then enter the password [c]root [/c]and hit [Enter]
But this will not start SliTaz in graphic mode; it'll allow you to access to the command line.
Offline
Yes - SliTaz is on hdb - 320G; internal, IDE.
Puppy is on sda, 1000 GB drive, internal, Sata.
I didn't really learn how to boot two OSs; maybe should have; so I'm trying new OSs on hdb, where the computer boots by default, after the installation; and I boot Puppy by F8 - boot menu; same with booting from CD.
BIOS boots HD I guess. I can't tell it which one to boot, right?
Specs:
Processor - AMD Athlon(tm) II X3 435 Processor: 800.00MHz;
RAM - 2G
(anything else?)
So yeah, SliTaz booted in console mode; didn't since then.
Offline
OK. I don't like to have 2 boot partitions on a same system; for tests:
[*]boot from your Live CD
[*]open GParted: Applications > System Tools > GParted Partitions Editor (password is root)
[*]select /dev/sda1 device
[*]click on Partiton > Manage Flags
[*]uncheck boot flag and [Close]
After this, probably you won't be able to boot from sda but you'll just have to check the boot flag again
Now we are sure that you'll boot from hdb using /boot/grub/menu.lst from hdb1.
If on /dev/hdb1 your /boot/grub/menu.lst is like this:[c]
# /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/hdb1
#
title SliTaz GNU/Linux (cooking) (Kernel vmlinuz-2.6.37-slitaz)
root (hd0,0)
kernel /boot/vmlinuz-2.6.37-slitaz root=/dev/hdb1 quiet[/c]
it should boot in SliTaz now.
Eject the LiveCD, reboot and tell me what happens.
Offline
There was a flag on sdb5; I've removed it, and have put one on sdb1. There wasn't a flag anywhere on sda.
When I tried to boot with "quite" in the end of the line - the screen shuts-off (the original problem). When I boot with "nomodeset screen=1024x768" in the end - it goes through many lines with a green "OK" at the end; but halts after the last lines, which are:
Executing all initialization scripts...
Parsing kernel cmdline for SliTaz live option...
_
(it's a blinking underscore at the end)
Oh; something I've noticed, but forgot to mention before - roughly 40to30% of the time - when I boot SliTaz from the CD - the screen shuts-off just like with the installed version. I think it happens right when it needs to start the window that asks which language I want to choose.
Offline
Well, this is a little confusing:
character * in output of the [c]fdisk -l [/c]command signals the bootable partitions; so[c]
/dev/hdb5 * 2 38655 310488223+ 7 HPFS/NTFS [/c]=> hdb5 was a bootable partition (did you make a typo when writing sdb5 and sdb1 or is like this that GParted indentified your partitions?)
and[c]
/dev/sda1 * 1 1008 8089600 83 Linux [/c]=> sda1 is a bootable partition...
Anyway. We can say GRUB finds the kernel and the kernel finds its file system if you can see lines with green OK. Your problem seems to be the graphic card and it's far to be my speciality.
The [c]quiet [/c]instruction is not important, you can suppress it.
Try to boot with [c]kernel /boot/vmlinuz-2.6.37-slitaz root=/dev/hdb1 nomodeset [/c] and anything else after; this is the only way I found to boot SliTaz 5.0-rc2 on my Acer and have a correct display.
Offline
With "nomodeset screen=1024x768" - I had the green "OK"s; with "quiet" - the screen would switch-off.
Yeah, I see now in the previous page here, that there were "*" besides sdb5 and sda1. So maybe I did take them off both partitions, with GParted in the live-CD. Anyway, now I checked with "fdisk -l" in Puppy; and the "*" is only besides sdb1.
BTW - Puppy boots after I choose it in the boot menu.
Thank you for your help.
Offline
[ Generated in 0.015 seconds, 7 queries executed - Memory usage: 1.59 MiB (Peak: 1.77 MiB) ]