A 'Live Cd' or Only a Command Line Prompt

SliTaz Forum » English Support » Live and installation

A 'Live Cd' or Only a Command Line Prompt

(5 posts) (3 voices)

Started 13 years ago by plumtreed
Latest reply from Anonymous
This topic is not a support question

Tags:

No tags yet.

plumtreed

offline
Member

Implications were that the recent cooking release was a 'Live CD' which suggests to me that it would boot to a GUI type desktop but I get to a command line prompt.

I get to a boot screen but should I expect to proceed from there to a working desktop????

Posted 13 years ago #
Trixar_za

offline
Key Master

The better questions would be "Which flavour of cooking did you download?", "Have you downloaded a working copy?" and "What kind of system are you running?"

Here's the trick. Go to where you downloaded the iso in your terminal (if your using Linux) and type md5sum slitaz-cooking.iso and compare the 'code' it generates with the one found @ http://mirror.slitaz.org/iso/cooking/slitaz-cooking.md5 (just open it with a text editor) - if they don't match then you have a bad iso download. Also make sure the iso you have is 31MB in size.

And yes, it IS a LiveCD. Just because it drops you into command line because of some error or issue, doesn't mean it's not.

Posted 13 years ago #
plumtreed

offline
Member

Thanks for the reply, actually md5sum checks OK and it is 31mb in size, tried burning a few different times, using cdrw, but it still goes wrong.

Your confirmation that I should get to the desktop allows me to work on a solution.

Posted 13 years ago #
plumtreed

offline
Member

OK, I can now get it to boot to my laptop but same cd won't boot to eeePC.

Posted 13 years ago #
Anonymous

offline
Unregistered

Have you tried the advice: http://doc.slitaz.org/en:guides:xorg-xvesa ?

On my acer aspire laptop Slitaz stable 3.0 booted to a command prompt and to fix it I had to install the proper drivers for my video card. I used tazx and then tazhw detect-pci while logged in as root, and then I logged out of root (CTRL-D, i think or exit) and then logged in as tux and executed startx. It went thru the tazx dialog again I suppose to configure Xorg for the user tux and booted into the GUI. I had a problem with my wireless but that is another story.

Anyway it is worth a try. And for the record there are various logs created at boot up stored in /var/log you may want to look thru to see if you can spot the source of the error if tazx does not work. You can do this at the command prompt by cd /var/log to change to that directory and then ls to see what files are located there and then use nano to open the various files. Log files have an extension of .log so for example to open slim.log use nano slim.log. Good luck :)

Posted 13 years ago #

RSS feed for this topic

Reply

You must log in to post.