felner@inf.ethz.ch (Tomas Felner) (03/09/89)
Today I updated Minix ST 1.1 with the official diffs posted by Johan Stevenson some months ago and with the kernel diffs (rs232, midi, tape, mouse, screen, etc.) posted by Howard Johnson recently. After recompiling all the stuff the minix.img didn't work at all. After having spent several hours following wrong directions, I found that the problem seems to be caused by /usr/lib/cv. I had the same problems as reported by Howard shortly after the official patches by Johan. One compiled version with all the flags 'HAVE...' in h/const.h disabled worked finally, but only after I converted kernel.out to kernel.mix by using the OLD /usr/lib/cv ! Using the new one resulted in a damaged version. The other parts (mm & fs) I could convert with the new version. I even got messages like 'corrupted file system' when booting with a version where the filesystem is converted by the old 'cv' (I had to use the new one in this case). Now I have enabled all 'HAVE...' except 'HAVETAPE' and 'HAVEDISKCLOCK'. In this configuration, the kernel must be converted with the old 'cv', the other two parts with the new one; then the system boots, loads the ram disk (or harddisk root), but then it just hangs ! If I use another configuration with the old and new 'cv', I just get 'sig'-messages when booting and it hangs again. After having spent several hours with this, I feel pretty frustrated and annoyed about it. Did anyone else have this problems ? What configurations do you have ? Is 'cv' damaged ?? Any suggestions ? - Tomas BTW: 'cv' is ok, at least as far as the checksum is concerned.
hcj@lzaz.ATT.COM (HC Johnson) (03/13/89)
In article <86@inf.ethz.ch>, felner@inf.ethz.ch (Tomas Felner) writes: > Today I updated Minix ST 1.1 with the official diffs posted by Johan > Stevenson some months ago and with the kernel diffs (rs232, midi, tape, > mouse, screen, etc.) posted by Howard Johnson recently. After > recompiling all the stuff the minix.img didn't work at all. After having > spent several hours following wrong directions, I found that the > problem seems to be caused by /usr/lib/cv. I had the same problems as > reported by Howard shortly after the official patches by Johan. > I only use the old cv. Its limitations haven't hit me yet, and the new one, doesn't do the big kernel correctly. Agreed. I suggest that if you cant build a working kernel thay you: 1. make sure that you increase the size of the stack (chmem +20000) of sttools/build. Besides just failing, walking on this stack will change the code in minix.img. BAD! 2. Start simple. One of the goals of addind the HAVE switches in h/const.h is that you can turn them ALL OFF. This produces the original kernel. Try it; then add in features one at a time. Thats how I check it. Howard C. Johnson ATT Bell Labs att!lzaz!hcj hcj@lzaz.att.com