From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] installation on SATYA disk failed
Date: Fri, 24 Jul 2009 10:17:42 -0400 [thread overview]
Message-ID: <04c176a87f40f49c56dc4937e2ad8d8e@quanstro.net> (raw)
In-Reply-To: <3BBB12CF4EFF4040B38542759379E3CD0278F5@XMAIL.asuch.cas.cz>
> This is what I get:
>
> PBS1...
> Plan 9 from Bell Labs
> ELCR:CCL8
> pcirouting: South bridge 8086, 2810 not found
> islba: drive 0x80 extensions version 48.0 cx 0x5
> exgetsize: drive 0x80 info flags 0x0
> bios0: drive 0x80: 1,000,204,886,016 bytes, type 3
> reading drive 0x80 offset 0 into seg: off 0x6000000...biosdiskcall: int 13 op 042 drive 0x80 failed, ah error code 0x80
i don't see those debugging statements on sources,
so clearly i could be misreading this. but assuming
that i'm not confused about what that says,
wouldn't that segment:off be a problem?
as far as i know, 9load only maps 8mb.
> So, I added a second (slave) HD on IDE0, with a small FAT partition, etc., and booted:
> sdB0!dos!9pcflop.gz
> and voila, installer runs, but only up to the '[partdisk]: no disk devices were found on your system. The installation process cannot continue.'
/sys/src/9/pcflop has sdiahci commented out. i would
think at this point we could trade sdmylex and sd53c8xx
for sdiahci. (sadly, it's hard to find 5v pci slots anymore.)
but since you're not on a floppy, you can compile a
kernel with them all in. you don't need to fit in 1.44mb.
- erik
next prev parent reply other threads:[~2009-07-24 14:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-24 10:09 cej
2009-07-24 12:11 ` [9fans] installation on SATA " cej
2009-07-24 15:07 ` erik quanstrom
2009-07-29 9:00 ` cej
2009-07-24 14:17 ` erik quanstrom [this message]
2009-07-26 4:22 ` [9fans] installation on SATYA " geoff
2009-07-26 6:11 ` Bela Valek
2009-07-26 14:08 ` erik quanstrom
2009-07-26 15:16 ` hiro
2009-07-26 19:09 ` Ethan Grammatikidis
2009-07-26 19:51 ` Ethan Grammatikidis
2009-07-26 20:14 ` tlaronde
2009-07-26 11:48 Akshat Kumar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=04c176a87f40f49c56dc4937e2ad8d8e@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).