* [Buildroot] Still "Can't open /dev/tty1[2,3]", Please HELP @ 2008-09-01 1:57 Steven Woody 2008-09-02 0:58 ` Hamish Moffatt 0 siblings, 1 reply; 6+ messages in thread From: Steven Woody @ 2008-09-01 1:57 UTC (permalink / raw) To: buildroot After guess and guess and build and burn, my rootfs still can not boot, it always get "Can't open /dev/tty1[2,3...]" after kernel loaded just load it. I attached the full boot message and my buildroot .config, I hope, with best regards, someone could help me. Thanks in advance. - narke -------------- next part -------------- A non-text attachment was scrubbed... Name: .config Type: application/octet-stream Size: 16747 bytes Desc: not available Url : http://lists.busybox.net/pipermail/buildroot/attachments/20080901/3f3e1450/attachment-0002.obj -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: bootmsg.txt Url: http://lists.busybox.net/pipermail/buildroot/attachments/20080901/3f3e1450/attachment-0002.txt ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] Still "Can't open /dev/tty1[2,3]", Please HELP 2008-09-01 1:57 [Buildroot] Still "Can't open /dev/tty1[2,3]", Please HELP Steven Woody @ 2008-09-02 0:58 ` Hamish Moffatt 2008-09-02 1:39 ` Steven Woody 0 siblings, 1 reply; 6+ messages in thread From: Hamish Moffatt @ 2008-09-02 0:58 UTC (permalink / raw) To: buildroot On Mon, Sep 01, 2008 at 09:57:49AM +0800, Steven Woody wrote: > After guess and guess and build and burn, my rootfs still can not > boot, it always get "Can't open /dev/tty1[2,3...]" after kernel loaded > just load it. I attached the full boot message and my buildroot > .config, I hope, with best regards, someone could help me. I couldn't work out where your target_skeleton and device table are coming from based on your config. Do you have a device table, and does it have those /dev/tty1,2,3,4 devices? Maybe you could post the output of the build process. > VFS: Mounted root (cramfs filesystem) readonly. > Freeing init memory: 84K > mkdir: cannot create directory '/dev/pts': Read-only file system > mount: mounting devpts on /dev/pts failed: No such file or directory Your inittab is obviously trying to make directories in a read-only file system which isn't going to work. Not that it's related. Hamish -- Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au> ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] Still "Can't open /dev/tty1[2,3]", Please HELP 2008-09-02 0:58 ` Hamish Moffatt @ 2008-09-02 1:39 ` Steven Woody 2008-09-02 6:24 ` Emil Kruper 0 siblings, 1 reply; 6+ messages in thread From: Steven Woody @ 2008-09-02 1:39 UTC (permalink / raw) To: buildroot On Tue, Sep 2, 2008 at 8:58 AM, Hamish Moffatt <hamish@cloud.net.au> wrote: > I couldn't work out where your target_skeleton and device table are > coming from based on your config. Do you have a device table, and does > it have those /dev/tty1,2,3,4 devices? The problem had gone away after I add udev to the packages. I am not sure whether the absence of udev is really the reason that cause the previous "can't open /dev/tty?" problems. But I still like to know what you mentioned 'device table'. I want to ask, what is and where is the 'device table'? I dont find the concepts in buildroot on-line doucments. Thanks. > > Maybe you could post the output of the build process. > >> VFS: Mounted root (cramfs filesystem) readonly. >> Freeing init memory: 84K >> mkdir: cannot create directory '/dev/pts': Read-only file system >> mount: mounting devpts on /dev/pts failed: No such file or directory > > Your inittab is obviously trying to make directories in a read-only file > system which isn't going to work. Not that it's related. > Yes, you are right. I did not notice it at first time. But it was corrected. You may see in my another post, I now can get the login prompt, and my problem switchs to "Why I can not login". I hope I can get your help in that thread. Best Regards, narke ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] Still "Can't open /dev/tty1[2,3]", Please HELP 2008-09-02 1:39 ` Steven Woody @ 2008-09-02 6:24 ` Emil Kruper 2008-09-02 10:27 ` Steven Woody 0 siblings, 1 reply; 6+ messages in thread From: Emil Kruper @ 2008-09-02 6:24 UTC (permalink / raw) To: buildroot >But I still like to know what you mentioned 'device table'. I want to >ask, what is and where is the 'device table'? I dont find the >concepts in buildroot on-line doucments. Thanks. Have a look at target/generic/device_table.txt and target/generic/mini_device_table.txt. You define by the buildroot config which file is used to generate the targets device table. Best regards Emil Kruper Von: buildroot-bounces at uclibc.org [mailto:buildroot-bounces at uclibc.org]Im Auftrag von Steven Woody Gesendet: Dienstag, 2. September 2008 03:40 An: buildroot at uclibc.org Betreff: Re: [Buildroot] Still "Can't open /dev/tty1[2,3]", Please HELP On Tue, Sep 2, 2008 at 8:58 AM, Hamish Moffatt <hamish@cloud.net.au> wrote: > I couldn't work out where your target_skeleton and device table are > coming from based on your config. Do you have a device table, and does > it have those /dev/tty1,2,3,4 devices? The problem had gone away after I add udev to the packages. I am not sure whether the absence of udev is really the reason that cause the previous "can't open /dev/tty?" problems. But I still like to know what you mentioned 'device table'. I want to ask, what is and where is the 'device table'? I dont find the concepts in buildroot on-line doucments. Thanks. > > Maybe you could post the output of the build process. > >> VFS: Mounted root (cramfs filesystem) readonly. >> Freeing init memory: 84K >> mkdir: cannot create directory '/dev/pts': Read-only file system >> mount: mounting devpts on /dev/pts failed: No such file or directory > > Your inittab is obviously trying to make directories in a read-only file > system which isn't going to work. Not that it's related. > Yes, you are right. I did not notice it at first time. But it was corrected. You may see in my another post, I now can get the login prompt, and my problem switchs to "Why I can not login". I hope I can get your help in that thread. Best Regards, narke _______________________________________________ buildroot mailing list buildroot at uclibc.org http://busybox.net/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] Still "Can't open /dev/tty1[2,3]", Please HELP 2008-09-02 6:24 ` Emil Kruper @ 2008-09-02 10:27 ` Steven Woody 2008-09-02 11:29 ` Steven Woody 0 siblings, 1 reply; 6+ messages in thread From: Steven Woody @ 2008-09-02 10:27 UTC (permalink / raw) To: buildroot On Tue, Sep 2, 2008 at 2:24 PM, Emil Kruper <e.krueper@solcon-systemtechnik.de> wrote: >>But I still like to know what you mentioned 'device table'. I want to >>ask, what is and where is the 'device table'? I dont find the >>concepts in buildroot on-line doucments. Thanks. > > Have a look at target/generic/device_table.txt and > target/generic/mini_device_table.txt. sorry for the stupid ... I append the exact file with the folllowing line /usr/local d 755 0 0 - - - - - to ensure the target/generic/device_table.txt really works. But after full build, I don't find /usr/local under the root. So,,, what 'device_table.txt' should I go to use? > You define by the buildroot config which file is used to generate the > targets device table. Where is the definition for the target device table file name? Thanks. > > Best regards > > Emil Kruper > > Von: buildroot-bounces at uclibc.org > [mailto:buildroot-bounces at uclibc.org]Im Auftrag von Steven Woody > Gesendet: Dienstag, 2. September 2008 03:40 > An: buildroot at uclibc.org > Betreff: Re: [Buildroot] Still "Can't open /dev/tty1[2,3]", Please HELP > > > On Tue, Sep 2, 2008 at 8:58 AM, Hamish Moffatt <hamish@cloud.net.au> wrote: > >> I couldn't work out where your target_skeleton and device table are >> coming from based on your config. Do you have a device table, and does >> it have those /dev/tty1,2,3,4 devices? > > The problem had gone away after I add udev to the packages. I am not > sure whether the absence of udev is really the reason that cause the > previous "can't open /dev/tty?" problems. > > But I still like to know what you mentioned 'device table'. I want to > ask, what is and where is the 'device table'? I dont find the > concepts in buildroot on-line doucments. Thanks. > >> >> Maybe you could post the output of the build process. >> >>> VFS: Mounted root (cramfs filesystem) readonly. >>> Freeing init memory: 84K >>> mkdir: cannot create directory '/dev/pts': Read-only file system >>> mount: mounting devpts on /dev/pts failed: No such file or directory >> >> Your inittab is obviously trying to make directories in a read-only file >> system which isn't going to work. Not that it's related. >> > > Yes, you are right. I did not notice it at first time. But it was > corrected. > > You may see in my another post, I now can get the login prompt, and my > problem switchs to "Why I can not login". I hope I can get your help > in that thread. > > Best Regards, > narke > _______________________________________________ > buildroot mailing list > buildroot at uclibc.org > http://busybox.net/mailman/listinfo/buildroot > > _______________________________________________ > buildroot mailing list > buildroot at uclibc.org > http://busybox.net/mailman/listinfo/buildroot > ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] Still "Can't open /dev/tty1[2,3]", Please HELP 2008-09-02 10:27 ` Steven Woody @ 2008-09-02 11:29 ` Steven Woody 0 siblings, 0 replies; 6+ messages in thread From: Steven Woody @ 2008-09-02 11:29 UTC (permalink / raw) To: buildroot On Tue, Sep 2, 2008 at 6:27 PM, Steven Woody <narkewoody@gmail.com> wrote: > On Tue, Sep 2, 2008 at 2:24 PM, Emil Kruper > <e.krueper@solcon-systemtechnik.de> wrote: >>>But I still like to know what you mentioned 'device table'. I want to >>>ask, what is and where is the 'device table'? I dont find the >>>concepts in buildroot on-line doucments. Thanks. >> >> Have a look at target/generic/device_table.txt and >> target/generic/mini_device_table.txt. > > sorry for the stupid ... I append the exact file with the folllowing line > /usr/local d 755 0 0 - - > - - - > to ensure the target/generic/device_table.txt really works. But after > full build, I don't find /usr/local under the root. So,,, what > 'device_table.txt' should I go to use? > >> You define by the buildroot config which file is used to generate the >> targets device table. > > Where is the definition for the target device table file name? Thanks. > sorry, Emil, for this problem, I found what mattered is target/generaic/mini_device_table.txt instead of target/generic/device_table.txt. Please focus on my another thread and be kindly to help me resolve the "can not login" or "getty exited" problem. Thanks. ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2008-09-02 11:29 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2008-09-01 1:57 [Buildroot] Still "Can't open /dev/tty1[2,3]", Please HELP Steven Woody 2008-09-02 0:58 ` Hamish Moffatt 2008-09-02 1:39 ` Steven Woody 2008-09-02 6:24 ` Emil Kruper 2008-09-02 10:27 ` Steven Woody 2008-09-02 11:29 ` Steven Woody
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox