greg@suntan.viewlogic.com (Gregory Larkin) (05/29/91)
Hi there, I posted a question about readclock(1) not working yesterday, and I think I've gotten a little closer to the solution, but I just hit a really big problem!! My system did not have a /dev/port device, so readclock(1) could not get the system time. "OK", I thought, "I'll just create the device". I did: (from the makedev.sh script) mknod /dev/port b 1 4 0 chmod 600 /dev/port chown bin /dev/port chgrp sys /dev/port Is this OK? I then typed: "readclock", hoping it would give me a system time. Well, it hung the machine!! Not even CTRL-ALT-DEL would reboot it, either! I powered down and rebooted, but since readclock(1) is in my /etc/rc file, the boot gets to certain point and dies. The only thing I can think of is that the battery backup for the clock could be dead. I do seem to remember that when the PC is booted to DOS, the time is all screwed up every time. Could this cause the hang? Any ideas, folks? If you have any ideas, I'd love to hear them.. I'm going to be out of luck until I solve this! Back to DOS, I guess... :-((((( Thanks, -- Greg Larkin (ASIC Engineer)|"This is a fragile ball we are living on; Viewlogic Systems, Inc. |it's a miracle and we are destroying it.." 293 Boston Post Road West |Peter Garrett, Midnight Oil Marlboro, MA 01752 (greg@Viewlogic.COM)
Fred Wiersma <SRONCH%HLERUL2.BITNET@vm.biu.ac.il> (06/09/91)
> Hi there, > > I posted a question about readclock(1) not working yesterday, and I > think I've gotten a little closer to the solution, but I just hit a > really big problem!! > > My system did not have a /dev/port device, so readclock(1) could not > get the system time. "OK", I thought, "I'll just create the device". > > I did: (from the makedev.sh script) > > mknod /dev/port b 1 4 0 > chmod 600 /dev/port > chown bin /dev/port > chgrp sys /dev/port > > Is this OK? > > I then typed: "readclock", hoping it would give me a system time. Well, > it hung the machine!! Not even CTRL-ALT-DEL would reboot it, either! I tried the same, with the same results. When I ran Minix 1.3, readclock worked fine, but since I run Minix 1.5, readclock does not work anymore. Some time ago I looked in the source, but nothing much seems to have changed in readclock. > I powered down and rebooted, but since readclock(1) is in my /etc/rc > file, the boot gets to certain point and dies. > > The only thing I can think of is that the battery backup for the clock > could be dead. I do seem to remember that when the PC is booted to DOS, > the time is all screwed up every time. Could this cause the hang? My battery is fine, so that's probably not the cause. > Any ideas, folks? No, anyone else? > If you have any ideas, I'd love to hear them.. I'm going to be out of > luck until I solve this! Back to DOS, I guess... :-((((( > > Thanks, > Ditto. > > -- > Greg Larkin (ASIC Engineer)|"This is a fragile ball we are living on; > Viewlogic Systems, Inc. |it's a miracle and we are destroying it.." > 293 Boston Post Road West |Peter Garrett, Midnight Oil > Marlboro, MA 01752 (greg@Viewlogic.COM) Fred Wiersma SRONCH@HLERUL2 (EARN/BITNET)
Don Chapman <DCHAPMAN@utkvx.utk.edu> (06/09/91)
Try mknod /dev/port c 1 4. That works for me. Don Chapman <dchapman@utkvx.utk.edu>