|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Nick Holland (nick
holland-consulting.net)Date: Mon Apr 02 2001 - 22:16:47 CDT
see http://www.openbsd.org/mail.html
I draw your attention to the description of the Tech
list.
"Please direct 'new user' and installation-related questions to misc."
My test is "If I can answer it, it belongs on Misc
", not sure that
this helps anyone else, though. 8-)
Anyway...onward to your problem...
"Tim K." wrote:
>
> Hi all,
>
> Well, I took the plunge this weekend,& tried to load OpenBSD 2.8 on an old
> P-100 that I have laying around, & as you can tell by the subject line, it
> was not a complete success. To begin with, I was following the instructions
> located on OpenBSD's site at:
>
> http://www.openbsd.org/faq/faq4.html
>
> In addition, I wish to set this up as a server, I have no need to maintain
> DOS compatibility, nor to dual-boot. (IOW, I don't care if I blow all of
> the current info on the HD away!) ;~) AFAIK, this eliminates the "1st 1024
> cylinders" issue... (I hope someone will let me know if I'm wrong...)
You are correct.
> First, I was able to use rawrite only for the 1st image that I downloaded
> (floppy28.fs). Any other image that I tried to create (floppyB28.fs or
> floppyC28.fs) returned an error that said that rawrite was unable to find
> the files - even though they were in the same directory as the original file
> that it *did* write. I tried it using the exact case of the file names,
> then in a case-insensitive manner, then using explicit paths, all with no
> difference. Strange... I guess my next step will be to try downloading all
> of it again, & again attempt to create the images, this time on a different
> system. Anyone have any other thoughts?
floppyB28.fs
^^^^^^^^^
123456789
The problem is under Windows 9x, your "DOS" file name was probably
something like:
floppy~1.fs
^^^^^^^^
12345678
rawrite is a DOS app, so you have to give it DOS names...
Do it from a DOS window, things will be clear...er.
But as you say next, floppy28.fs is the one you probably need/want
anyway. Nice of you to try to use the others first, though. 8-)
> In actuality, the inability to create the other images wouldn't have been
> an issue if the following hadn't been a problem... When I attempted to boot
> the from the floppy that *was* successfully created, after presenting me
> with a boot: > prompt for a couple of seconds, it would continue with the
> normal boot process. All went OK until it (apparently) tried to access the
> HD, then it simply timed out. The relevant dmesg section is below:
<very slightly off topic rant>
No such thing as "relevant dmesg _section_" -- the issue is how things
interoperate...how ALL things interoperate. Though, I will forgive
you for snipping the dmesg, as I assume you had to type it in by hand,
I do recognize that is a pain, and you got lucky as I do think you
included what we needed to diagnose the problem. 8-)
</very slightly off topic rant>
> wd0 at pciide channel 0 drive 0 <WDC AC38400L>
> wd0: can use 16-bit PIO mode 4
> wd0: 16-sector PIO, LBA, 8063 MB 16383 cyl, 16 hds, 63 sectors 16514064
> sect.
> pciide0: channel 0 interrupting at IRQ 14
> atapiscsi0 at pciide0 channel 1
> scsi bus 0 at atapiscsi0: 2 targets
> pciide0:1:0: device timeout, c_bcount=0, c_skip=0
> pciide0:1:0: device timeout, c_bcount=0, c_skip=0
> pciide0:1:0: device timeout, c_bcount=0, c_skip=0
Looks like you have the CD-ROM and the drive on the same channel.
Looks like in this case, they aren't playing nice together under
OpenBSD. Some pairings work, some don't -- typically a new HD with an
old CD-ROM will give you problems. Put your CD-ROM on the secondary
channel, problem should go away.
> That last line just repeated until I canceled the install attempt. Just
> FYI, there's nothing special about this system except for the fact that I've
> upgraded the HD, & therefore it has the translation software (EZ-Drive?)
> that allows one to run the larger HD. FWIW, I tried running the install
> both with & without using the translation software, the failure was
> identical in each case.
yeah, but don't use the translation software. OpenBSD can handle
things by itself.
> I'm fairly certain that RH 7 has the updated lilo, I certainly would have
> thought that the latest versions of *BSD would have accounted for this as
> well... (???) I also have a strong preference to use BSD on this system
> (it's intended to be a firewall for my home broadband connection, & I
> already have one Linux box), but I guess I can go back to Linux if need
> be... I'd prefer to get this working though, as I'd like to learn BSD.
>
> Any relevant thoughts, suggestions, advice would be very much appreciated.
Let us know how things go.
Nick.
-- http://www.holland-consulting.net/
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]