Phil,
I experienced the exact same problems you have documented below.
I'm using a Sparc5 (170MHz Fujitsu CPU), 32MB RAM, and a ST39175LC disk.
Oh, and this is all over a serial console.
Charles Fultz
fultz
-- "Once you go Slack, you'll never want the hat!"> I'm finally logged in on the install CD (2000-12-08 03:39:37) and have zeroed > out the 2 2gig drives (bye bye OpenBSD, for now). That worked. One of the > drives wasn't recognized by fdisk, but I managed to configure it via custom. > I partitioned the first drive with swap and one / partition, and the second > drive to be /home. > > These are the problems I'm running into already: > > 1. init reports ids 1,2,3 are respawning too fast. Apparently /dev/tty[1-4] > cannot be opened if the console is serial. > > In setup: > > 2. Character output is really messed up, but I suspect this is the fault of > minicom, which messes up things on other stuff, too. I'm looking for a > better term program (but not kermit, please) for the Intel box I am using > to connect to the Sparc serial console. Something that is very transpare > nt > and captures 100% transparent would be preferred. > > 3. I get messages about errors on /dev/tty4. Probably same issue as #1. > > 4. CDROM scan does not find the CDROM in /dev/scd0. So I manually mounted > it at /cd and proceeded with pre-mounted directory. > > 5. Once I get through all the setup input and proceed to install, I get the > following output. Note that some characters are garbled and I think that > minicom and/or the serial port is at fault for that. > > | You cHan't run pkgtoo the rootdisk until you've mounted your Linux > | partitions beneath /mnt. Here are some examples of this: > | > | If your root partition is /dev/hda1, and is using ext2fs, you would type: > | mount /dev/hda1 /mnt -t ext2 > | > | Then, supposing your /usr partition is /dev/hda2, you must do this: > | mount /dev/hda2 /mnt/usr -t ext2 > | > | Please mount your Linux partitions and then run pkgtool again. > | > | /usr/lib/setup/setup: cannot create /mnt/etc/fstab: directory nonexistent > | /usr/lib/setup/setup: cannot create /mnt/etc/fstab: directory nonexistent > | /usr/lib/setup/setup: cannot create /mnt/etc/fstab: directory nonexistent > | /usr/lib/setup/setup: cannot create /mnt/etc/fstab: directory nonexistent > | /usr/lib/setup/setup: cannot create /mnt/etc/fstab: directory nonexistent > | # > > I could not mount /dev/sda1 manually, but after I formatted it manually, > then I could mount it. Perhaps the errors trying to output to tty4 were > causing mke2fs to fail prematurely or not being run at all. > > I symlinked /dev/tty[1-4] to /dev/null. This seemed to allow formatting > to work for the first drive. However, when it went to format the 2nd > drive, the system went crazy alternating between reading the CDROM and > doing some burst if I/O on a HD. Killing setup didn't stop that and soon > the whole machine froze up. BREAK dropped to PROM prompt and I rebooted. > Possibly this wasn't actually format, but may have been getty dealing > with my symlinks. > > I'll pick up on this later today. I may try to change inittab to remove > the entries for tty[1-3] and rebuild the color.gz and ISO and see if that > makes a difference. > > -- > ----------------------------------------------------------------- > | Phil Howard - KA9WGN | Dallas | http://linuxhomepage.com/ | > | phil-nospam@ipal.net | Texas, USA | http://phil.ipal.org/ | > -----------------------------------------------------------------
This archive was generated by hypermail 2b30 : Thu Sep 19 2002 - 11:00:02 PDT