[nas-2000] Re: Serial cable connection
- From: Dennis Suchomsky <dennis@xxxxxxxxxxxxxxxxx>
- To: nas-2000@xxxxxxxxxxxxx
- Date: Sat, 11 Aug 2007 20:57:08 +0200
Am Samstag, den 11.08.2007, 19:52 +0200 schrieb philipp Wehrheim:
>
> Dennis Suchomsky wrote:
> > Am Samstag, den 11.08.2007, 19:04 +0200 schrieb philipp Wehrheim:
> >> Dennis Suchomsky wrote:
> >>> Am Samstag, den 11.08.2007, 18:55 +0200 schrieb philipp Wehrheim:
> >>>> Dennis Suchomsky wrote:
> >>>>> Am Samstag, den 11.08.2007, 18:33 +0200 schrieb philipp Wehrheim:
> >>>>>> Dennis Suchomsky wrote:
> >>>>>>> Am Samstag, den 11.08.2007, 18:12 +0200 schrieb philipp Wehrheim:
> >>>>>>>> Dennis Suchomsky wrote:
> >>>>>>>>> OK one more thing....
> >>>>>>>>> I can't send Output therefore i can't interupt the Boot progress.
> >>>>>>>> do you want to save the hole output of the bootprocess?
> >>>>>>>> you can enable minicom-logging and then simply scroll back to the
> >>>>>>>> relevant parts
> >>>>>>>>
> >>>>>>> No sorry the Problem is that when I hit ctrl+C the NAS doesn't recieve
> >>>>>>> the command.
> >>>>>> you want to send CRTL+c to the bootloader?
> >>>>>>
> >>>>>> The rc-scripts starts when
> >>>>>>
> >>>>>> Mounting proc filesystem...
> >>>>>>
> >>>>>> is printed so after that point you should be able to press/send CRTL+c
> >>>>> Yes but Im not. I Just tried to send the command from a file but this
> >>>>> doesn't work either.
> >>>> how can you send the signal from a file I dont really get what you are
> >>>> trying to do?
> >>> minicom has an option to paste in commands from a file...
> >>> I simple try to interupt the boot process to add usb support. But
> >>> somehow nothing happens when I press ctrl+C when the system asks me to
> >>> do...
> >>> Is it possible that one wire of the serial cable is not connected or
> >>> something like that?
> >> well maybe.
> >> Ok please try this:
> >>
> >> - connect the serial with the nas
> >> - start minicom
> >> - power on the nas
> >> - watch and do nothing while the nas boots up
> >> - now ssh to the nas and login as user root
> >> - next try to press CRTL-c or what ever
> >> - do you get an error in the ssh terminal?
> > Everything works fine till here
> >
> >> - what dose dmes tells you?
> > see attached file
> >
> >> - what are the last lines of "cat /var/log/messages"?
> > root@nas:~ # cat /var/log/messages
> > Jan 1 02:30:36 nas syslog.info syslogd started: BusyBox v1.00-rc3
> > (2006.12.01-02:09+0000)
> > Aug 11 17:35:28 nas syslog.info syslogd started: BusyBox v1.00-rc3
> > (2006.12.01-02:09+0000)
> > Aug 11 17:35:28 nas cron.notice crond[962]: crond 2.3.2 dillon, started,
> > log level 8
> > Aug 11 17:35:29 nas daemon.crit thttpd[968]: socket :: - Address family
> > not supported by protocol
> > Aug 11 17:35:29 nas daemon.notice thttpd[968]: thttpd/2.25b 29dec2003
> > starting on port 80
> > Aug 11 17:35:29 nas daemon.warn thttpd[968]: started as root without
> > requesting chroot(), warning only
> > Aug 11 17:36:34 nas authpriv.info dropbear[1015]: Warning: Reading the
> > random source seems to have blocked. If you experience problems, you
> > probably need to find a better entropy source.
> > Aug 11 17:36:38 nas authpriv.info dropbear[1015]: Child connection from
> > 192.168.2.16:2453
> > Aug 11 17:36:47 nas authpriv.warn dropbear[1015]: bad password attempt
> > for 'root' from 192.168.2.16:2453
> > Aug 11 17:36:50 nas authpriv.warn dropbear[1015]: bad password attempt
> > for 'root' from 192.168.2.16:2453
> > Aug 11 17:36:55 nas authpriv.notice dropbear[1015]: password auth
> > succeeded for 'root' from 192.168.2.16:2453
> >
>
> looks all good as far as i can see.
>
> dose the bootloader response to your keyboard input?
No
>
>
> >>>>>>>>> Sorry for bothering you so often but I promise Im going to write a
> >>>>>>>>> Howto
> >>>>>>>>> for the Wiki out of this ;)
> >>>>>>>>> bye
> >>>>>>>>> Dennis
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>
>
Other related posts:
