i386 platform install fdisk sadness

i386 platform install fdisk sadness

Post by cl.. » Sun, 29 Aug 1999 04:00:00


I have run into a problem with both openBSD and netBSD when trying to
install on my new Gateway PC -- the disk is an ATA >8GB; here's what I've
done, trying to dual-boot with the existing win95.  I'm booting from current
snapshots of both O/Ss (trying to support my bleeding edge hardware after

There was one huge partition.  I split it almost in half with fips.  All OK.
Now there's two partitions, win95 on number zero, nothing on number one.

openBSD's fdisk couldn't handle the end sector of partition number one,
which is 16434432, said it was out of range, and 'fixed' it by saying the
end is at C/H/S = 2/254/63, or in edit mode, as sector 8401995.

netBSD seemed to handle everything fine, and set up the disklabel and
fsck'd.  I stopped before completing the full install, rebooted, and somehow
it had killed the table entry for partition zero (c:\ didn't exist, win95
would not boot through the boot menu).  I recovered by using restorrb (part
of fips) to re-write the backup of the boot record.

After reading the openBSD docs on the limitations of the PC BIOS, I'm unsure
of the solution here.  My drive is 8-point-something GB, so now what?
Here's what pfdisk says:

geometry 1023 255 63 (cyls heads sectors)
#  ID  First(cyl)  Last(cyl)  Name  # start, length (sectors)
1  12      0        499       unkno # 63, 8032437
2  12    500       1026       unkno # 8032500, 8466255
# note:  last(2): phys=(2,254,63) logical=(1026,254,63)
3   0      0          0       empty # 0, 0
4   0      0          0       empty # 0, 0
active: 1

Here's another issue: why is the win95 partition labelled as Unknown?  It
has id 0xC; I expected *BSD to recognize it.

Kudos to those who helped me out on my last install problem.  After this, it
gets easier, right?


1. Installing on i386 platform with 3COM 3c905c network card, help?

dmesg is your friend here. su to root and type: dmesg | more
here's my dmesg:
xl0 at pci0 dev 10 function 0 "3Com 3c905 100Base-TX" rev 0x00:
irq 11 address 00:60:97:b2:a4:ec
xl0: autoneg complete, link status good (half-duplex, 10Mbps)

Haven't figured out how to go to full-duplex yet

According to http://www.openbsd.org/i386.html it is.
Supported Ethernet cards;
3Com 3c9xx, including the 3c905B (newer version), 3c905C, and 3c905B-FX
(100Mbit ethernet over fiber) (xl)

I tried RedHat 5.1, 5.2 and 6.0 on i386 and it works like a charm.

Both at work and home my 3c905 cards work great

Haven't tried NetBSD yet. Waiting for the 1.4 CD

All code sucks, but BSD code sucks less.
--Theo de Raadt

2. can get rid of file system error

3. opening a *.dbf file on unix software ?

4. Downloading RH7...So many types: 7.0-i386...7.0-i386-respin...7.0-ja-i386

5. unresolved symbol installing sarge

6. Is the CDROM images for all platforms or only i386?

7. Terminal session under Sol 2.2 ?

8. what happened to i386 cross-platform compatibility?

9. Porting linux to i386 but non-pc platform

10. fix wrong uptime on non-i386 platforms

11. Running i386 software on ia64 platform?

12. fdisk (1.6 i386) "Invalid system disk"