Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Have used Yellow Dog, thinking Mandrake for X86 System
Posts: 46
Rep:
can't access tty; job control turned off
Ok I've just finished a gentoo install and it appears that the bootloader and kernel are working ie. im booting and there arent any kernel error messages, the problem is this - after the boot up ticks along nicely i run into this error message
/bin/sh: can't access tty; job control turned off
1st - what does this mean? - ive looked around and i think it means that the terminal isnt working.
2nd - what would cause it?
3rd - how do i fix it?
after the error message i get a built in shell called ash and it has a few commands - like kill, cp, cd, ls etc. but nothing usefull and i can't access any of the programs that i know are on there - what can i do?
1. Yes, that's pretty much it.
2. On several newer systems, using the "Enhanced PCI access mode" setting in your computer's BIOS (or something to the same effect) will cause this. I have no idea why, but disabling it is a good start. Also, a misconfigured 2.6 series kernel will also generate similar errors. You will want the options
CONFIG_UNIX98_PTYS=y, CONFIG_UNIX98_PTY_COUNT=256 and CONFIG_DEVPTS_FS=y when configuring your kernel to have proper virtual (and actual) console access.
3. goto 2
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.