WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: new install 4.7.6 stops at text screen when booting  (Read 17303 times)

aus9

  • Guest
Re: new install 4.7.6 stops at text screen when booting
« Reply #15 on: May 06, 2013, 08:04:34 PM »
EDIT OP does not have a persistent home so home stuff removed from reply

ahhh I think I can spot some  issues as he has a series of commands which I believe he is forced to use root powers

He creates mydata.tgz in the build. It might be better he leaves that out.

ejames82

When you get a chance could you do me a favour and look at your permissions pls,

Code: [Select]
ls -al /mnt/sda2

(should return  drwxr-xr-x  3 root root    4096 Mar  3 08:17 home/)
(should return drwxrwxr-x  4 tc   staff   4096 Apr 28 14:04 tce/)

The reason is because tc must have the ability to download TCZs, and they go to tce/optional

IMHO your commands can not complete the process until you boot up to console

suggest you then

Code: [Select]
sudo su
chown -R tc:staff  /mnt/sda2/tce

You may need to check your permissions in tce/optional but one hopes they are good

then try
Code: [Select]
su tc
startx
« Last Edit: May 06, 2013, 09:04:45 PM by aus9 »

Offline ejames82

  • Full Member
  • ***
  • Posts: 183
Re: new install 4.7.6 stops at text screen when booting
« Reply #16 on: May 06, 2013, 08:06:25 PM »
that's quite alright gerald_clark.  you're a good guy.  :)
backup...backup...backup

aus9

  • Guest
Re: new install 4.7.6 stops at text screen when booting
« Reply #17 on: May 06, 2013, 08:14:55 PM »
One hopes so

I won't edit above now that you have replied so quickly

pls delete mydata.tgz with
Code: [Select]
sudo -rf /mnt/sda2/tce/mydata.tgz

when you can get a graphical screen up, you can create a backup file by using the control panel
click on mount tool to select sda2
click on backup/restore to backup

Offline ejames82

  • Full Member
  • ***
  • Posts: 183
Re: new install 4.7.6 stops at text screen when booting
« Reply #18 on: May 06, 2013, 08:20:55 PM »
I am on it aus9.  I have commandeered my wifes computer.  shuffling between the two.

have that info in a few.
backup...backup...backup

Offline ejames82

  • Full Member
  • ***
  • Posts: 183
Re: new install 4.7.6 stops at text screen when booting
« Reply #19 on: May 06, 2013, 08:44:26 PM »
/mnt/sda2 ls -la

drwxr-xr-x   root root  .
drwxrwxr-x    root staff  ..
drwxr-xr-x   root root  boot
drwx------   root root   lost + found
drwxrwxr-x   tc   staff   tce

should the tce directory be owned by tc?

there is no /mnt/sda2/home

I figured I would let you see this before I go on with the rest of your instructions, aus9. 
this is a fresh install.  if something goes wrong, I can always reinstall, so not a big deal.  it only takes me about 10 minutes to get to where I was before.
backup...backup...backup

aus9

  • Guest
Re: new install 4.7.6 stops at text screen when booting
« Reply #20 on: May 06, 2013, 08:58:35 PM »
Hi

boot folder is fine
lost and found is fine
tce folder is fine by me

OOPS I have persistent home and opt.....thats a leakage error from me about home

Quote
should the tce directory be owned by tc

yes, this is the reason why as user=tc you can run commands like....tce-load -w  something.tcz, if you did not have permission to create new entries there.....the command would bork

Others, feel free to chip in if I am misleading OP

Offline ejames82

  • Full Member
  • ***
  • Posts: 183
Re: new install 4.7.6 stops at text screen when booting
« Reply #21 on: May 06, 2013, 09:20:21 PM »
/mnt/sda2/tce/optional    dr-xrwxr-x

this did not work:
sudo -rf /mnt/sda2/tce/mydata.tgz

but this did:

sudo rm /mnt/sda2/tce/mydata.tgz
is that sufficient?

just to let you know, I am at the desktop now, but I am not able to use appbrowser
fatal error   tce directory is not writable
backup...backup...backup

Offline ejames82

  • Full Member
  • ***
  • Posts: 183
Re: new install 4.7.6 stops at text screen when booting
« Reply #22 on: May 06, 2013, 10:06:52 PM »
I have decided to try core plus 4.7.6
maybe when I am done I will have a better understanding what is supposed to be there and what isn't
jumping from 3.8.4 to 4.7.6 is quite a leap, regardless of how well prepared I thought I was.

thanks to everybody who helped me.
backup...backup...backup

aus9

  • Guest
Re: new install 4.7.6 stops at text screen when booting
« Reply #23 on: May 07, 2013, 12:43:39 AM »
sorry I should have asked what you had for tce/optional so your reply
Quote
/mnt/sda2/tce/optional    dr-xrwxr-x

shows the first string is read (not writeable) execute

if you ever decide to re-investigate this matter, you should be able as user=tc to fix by
Code: [Select]
chmod -R 775 /mnt/sda2/tce

I have editted my reply at the other thread you know I replied to as well as a result of knowing your current permissions
« Last Edit: May 07, 2013, 12:49:01 AM by aus9 »

Offline ejames82

  • Full Member
  • ***
  • Posts: 183
Re: new install 4.7.6 stops at text screen when booting
« Reply #24 on: May 07, 2013, 10:24:18 AM »
aus9,

not a big deal.  I just wanted to have the latest tinycore.  I have been using 3.8.4, but firefox is constantly bothering me about update and I can't find a way to stop it.  I tried to let firefox update itself once, but it was a huge mess that resulted in me reinstalling tinycore.  I thought I would make an effort to use 4.7.6.  I found out alot, and that my command-line skills are still not as good as they need to be. 
also, my effort to use core plus didn't work.  it wouldn't boot up to the OS.  I think that was because I was making a dual-boot.  I think it would have worked if it was just core plus on the hard drive by itself.  I like having many OS's on a system (to a fault).  :)

do you know how to enter boot codes?  I want stuff in my home and opt to survive a reboot and if I need to do this by entering a boot code, I don't know how.

you mentioned earlier using the console.  I am not sure what you mean by this, but I can guess THIS:
explanation of how to get to console in this url below.  basically, it is saying press ctrl + alt + f1.  if this is the case, when do I press it?  when I am on the desktop with no windows or applications running?
http://forum.tinycorelinux.net/index.php/topic,7430.0.html
reply #3
what does the console do?

thanks again aus9   
backup...backup...backup

aus9

  • Guest
Re: new install 4.7.6 stops at text screen when booting
« Reply #25 on: May 07, 2013, 07:57:56 PM »
ok one thing at a time

edit boot if you are the only user of this computer, I assume your wife won't touch it, the computer...giggles
Code: [Select]
sudo chown -R tc:staff /mnt/sda2/boot
cp  /mnt/sda2/boot/grub/menu.list  /mnt/sda2/boot/grub/menu.lst-bak

this is NON-standard but allows us to quickly edit boot codes. Step one.....as per your signature.....create a backup of your existing menu as per last line above

Now duplicate your TC menu so it now reads  (you can now use a standard gui text editor----I use leafpad)

Quote
title   TC nocodes
root    (hd0,1)
kernel  /boot/vmlinuz quiet tce=sda2
initrd  /boot/core.gz

title   TC-codes
root    (hd0,1)
kernel  /boot/vmlinuz quiet tce=sda2 <insert boot codes here>
initrd  /boot/core.gz

refer to http://distro.ibiblio.org/tinycorelinux/faq.html#bootcodes

I will show you mine to give you an idea, lots of people have better ideas. I have a very complicated system that allows me to easily swap from vesa graphics to nVidia closed source graphics.....don't focus on that just see you have multiple menu entries
AND

I rename core as 476 for the version=4.7.6 because when the next version comes out, I create extra menus to try out (say) 4.7.7

AND  my main bootloader is on sda1 and TC is on sda3 but I prefer labels, and so I don't need a /boot/grub on sda3

as you can tell I am a grubby person....giggles

Quote
title NV
kernel /grub/vmlinuz tce=LABEL=partthree home=LABEL=partthree opt=LABEL=partthree waitusb=8:LABEL=partthree snd=/opt/nv.sh lst=nv.lst lang=en_AU.UTF-8
initrd /grub/476.gz

title VESA
kernel /grub/vmlinuz tce=LABEL=partthree home=LABEL=partthree opt=LABEL=partthree waitusb=8:LABEL=partthree snd=/opt/vesa.sh lst=vesa.lst lang=en_AU.UTF-8
initrd /grub/476.gz

title TCB
kernel /grub/vmlinuz  base norestore
initrd /grub/476.gz
[/code]
« Last Edit: May 07, 2013, 11:47:11 PM by aus9 »

aus9

  • Guest
Re: new install 4.7.6 stops at text screen when booting
« Reply #26 on: May 07, 2013, 08:09:44 PM »
if you like the idea of using LABEL then download --as ondemand and load it ---e2fsprogs.tcz while using a live cd not hard drive

Code: [Select]
sudo su
umount /mnt/sda2
e2label /dev/sda2
(returns current value or blank line)

e2label /dev/sda2 Eric
e2label /dev/sda2
Eric

Choose something in place of Eric, labels can be added to un-mounted partitions
there are other commands that will do it, but I like the simplicity of e2label
---assuming its a linux ext2/3/4 partition
« Last Edit: May 07, 2013, 08:16:27 PM by aus9 »

Offline ejames82

  • Full Member
  • ***
  • Posts: 183
Re: new install 4.7.6 stops at text screen when booting
« Reply #27 on: May 07, 2013, 09:51:41 PM »
aus9,

so the boot code task goes something like this:
sudo chown -R tc:staff /mnt/sda2/boot
we don't want to be blocked from doing this by our own OS.

make a backup copy
cp  /mnt/sda2/boot/grub/menu.list  /mnt/sda2/boot/grub/menu.lst-bak


ok, so now if I want my firefox and alsa to survive reboot, should my kernel line have this:
kernel  /boot/vmlinuz quiet tce=sda2

or this?:
kernel  /boot/vmlinuz quiet tce=sda2 tce=home tce=opt


I think I may see the reasoning behind having multiple selections with differing boot codes.  the NV selection is probably when you unplug the 19inch monitor and plug in the big screen ultra plasma.  you probably have resolution of 5000x3000 enabled.  :)

sudo su
umount /mnt/sda2
e2label /dev/sda2
(returns current value or blank line)

e2label /dev/sda2 Eric
e2label /dev/sda2
Eric
here you're verifying that the label 'Eric' took hold

if you like the idea of using LABEL then download --as ondemand and load it ---e2fsprogs.tcz while using a live cd not hard drive
I know how to do this.  follow this up with the blkid command to verify.
a label is a sort of 'name', if you will.  it takes alot of the confusion away, instead of sda1 or sda2 (most confusing).
I think you can also use gparted to add a label.

what about the console subject?  anything to add?

what is that thing for?


thanks aus9.  I think I will try that command-line install of 4.7.6 again tomorrow (the one where everything went wrong yesterday).  when I do, I'll post about how it goes and I hope to hear your advice when you check into the site.
backup...backup...backup

Offline gerald_clark

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 4254
Re: new install 4.7.6 stops at text screen when booting
« Reply #28 on: May 07, 2013, 09:56:38 PM »
tce=sda2 home=sda2 opt=sda2

aus9

  • Guest
Re: new install 4.7.6 stops at text screen when booting
« Reply #29 on: May 08, 2013, 12:02:37 AM »
your "or this" option will give you persistence for home and opt. Please read the wiki and forums on that as I am have to get back to work.

In case you thought I was ignoring you, it was not clear to me, you had succeeded in getting a graphical display up either with this build of TC or the coreplus way.

so if you don't get graphics up, that is called console and means the same as terminal but you can't run any mouse controlled stuff.
like msdos if you are old enough to know such beasts.

some nice person has a wiki entry on alsa so you may elect to read that.

ie  what you put into your onboot.lst determines what is REBOOTED if downloaded into tce/optional
--files you changed, means you put that in your .filetool.lst------but drop the leading /

eg if you change /etc/scooby you add etc/scooby to your filetool.lst
------ alsa also needs a daemon so that goes to a boot up script called bootlocal.sh

Please take your time with the wiki and other forum posts.....you will be rewarded, with good looks, karma and skills, once you understand it.

good luck
« Last Edit: May 08, 2013, 12:05:56 AM by aus9 »