: [EMAIL PROTECTED]
Sent: Wednesday, December 21, 2005 12:43 PM
Subject: Problem booting FreeBSD from cboot FreeBSD from cdrom using grubdrom
using grub
Hi,
I'm trying to make an iso image that will boot FreeBSD using GRUB boot
loader.
Grub will boot /boot/loader and the loader will boot /boot
On Tuesday 20 December 2005 11:43 pm, Tony wrote:
Hi,
I'm trying to make an iso image that will boot FreeBSD using GRUB boot
loader.
Grub will boot /boot/loader and the loader will boot /boot/kernel. It
goes well on my disk, but when I try to make a livecd, it fails. I spend
some time
From: Tony [EMAIL PROTECTED]
I'm trying to make an iso image that will boot FreeBSD using GRUB boot
loader.
Then the kernel starts, but when the kernel try to mount the root fs, it
stops. I have the follow line in my /etc/fstab
/dev/acd0c / cd9660 ro 0
John Baldwin [EMAIL PROTECTED] wrote:
On Tuesday 20 December 2005 11:43 pm, Tony wrote:
Hi,
I'm trying to make an iso image that will boot FreeBSD using GRUB boot
loader.
Grub will boot /boot/loader and the loader will boot /boot/kernel. It
goes well on my disk, but when I try
Hi,
I'm trying to make an iso image that will boot FreeBSD using GRUB boot
loader.
Grub will boot /boot/loader and the loader will boot /boot/kernel. It
goes well on my disk, but when I try to make a livecd, it fails. I spend
some time figuring out that /boot/loader does not probe cd it
Hi all,
Today I wanted to upgrade mysql-4.0.17 to mysql-4.0.18 in
FreeBSD-5.2-CURRENT and got error below.
I did updated FreeBSD on March 3 2004 using cvsup.
I used following options to compile mysql from ports collection:
make WITH_CHARSET=cp1251 WITH_LINUXTHREADS=yes BUILD_STATIC=yes install
Hi,
I installed FreeBSD 5.2 and updated using cvsup on Dell Poweredge 1600SC.
However still FreeBSD doesn't recognize network card. It has onboard Intel
Pro/1000 MT card.
What should I do in order to use this onboard Intel PRO/1000 card? I
checked Intel web site and found only
em driver for
On Mon, 16 Feb 2004, Ganbold wrote:
Hi,
I installed FreeBSD 5.2 and updated using cvsup on Dell Poweredge 1600SC.
However still FreeBSD doesn't recognize network card. It has onboard Intel
Pro/1000 MT card.
What should I do in order to use this onboard Intel PRO/1000 card? I
checked Intel
Hi,
Following is the output of pciconf -lv command:
[EMAIL PROTECTED]:0:0:class=0x06 card=0x chip=0x00171166
rev=0x32 hdr=0x00
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
device = 'CMIC-SL'
class= bridge
subclass = HOST-PCI
[EMAIL
problem in FreeBSD 5.2-current
Hi,
Following is the output of pciconf -lv command:
[EMAIL PROTECTED]:0:0:class=0x06 card=0x chip=0x00171166
rev=0x32 hdr=0x00
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
device = 'CMIC-SL'
class= bridge
to point out the obvious but there's no EM controller there?
Steve
- Original Message -
From: Ganbold [EMAIL PROTECTED]
To: Mike Silbersack [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Monday, February 16, 2004 10:45 AM
Subject: Re: Intel PRO/1000 MT onboard network card problem in FreeBSD
Hi,
Ganbold wrote on Mon, Feb 16, 2004 at 06:45:39PM +0800:
[..]
[EMAIL PROTECTED]:4:0: class=0x02 card=0x9207103c chip=0x1213 rev=0x10
hdr=0x00
vendor = 'Accton Technology Corporation'
device = 'EN-1207D Fast Ethernet Adapter'
class= network
subclass =
Yes I installed Realtek card because FreeBSD doesn't recognize onboard card.
It has onboard TP connector same as Redhat machine has.
Ganbold
At 07:37 PM 16.02.2004, you wrote:
Hi,
Ganbold wrote on Mon, Feb 16, 2004 at 06:45:39PM +0800:
[..]
[EMAIL PROTECTED]:4:0: class=0x02
If that's the case doesn't look like its being detected. Is it disabled in the bios?
Steve
- Original Message -
From: Ganbold [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, February 16, 2004 12:05 PM
Subject: Re: Intel PRO/1000 MT onboard network card problem in FreeBSD
On Mon, 16 Feb 2004, Daniel Lang wrote:
Hi,
Ganbold wrote on Mon, Feb 16, 2004 at 06:45:39PM +0800:
[..]
[EMAIL PROTECTED]:4:0: class=0x02 card=0x9207103c chip=0x1213 rev=0x10
hdr=0x00
vendor = 'Accton Technology Corporation'
device = 'EN-1207D Fast Ethernet
On Mon, 16 Feb 2004, Ganbold wrote:
Hi,
Following is the output of pciconf -lv command:
As others have pointed out, the problem isn't in the em driver, since the
card isn't even showing up in pciconf. Either it's somehow not enabled,
or FreeBSD isn't detecting the PCI bridge that the card
Hi Mike and all,
I found the problem with the Intel PRO/1000 card. I looked in the BIOS and
it says NO MAC address!
I even reset BIOS but no results. It seems like onboard Intel card is
broken or malfunctioning.
I told the owner to change Dell server to another.
Thanks for all who tried to
Okay, this is not really intended as a flame, but kinda necessary, given the
current situation in the FreeBSD camp.
Let's see, some weeks ago a couple of people dropped their ports
maintainership, why did this happen? Sergey dropped his ports because David
O'Brien is an asshole. Yes, no news,
Bill H., is that you?
On Tue, Jun 18, 2002 at 08:39:57AM +, Bill Flamerola wrote:
Okay, this is not really intended as a flame, but kinda necessary, given the
current situation in the FreeBSD camp.
[...useless stuff...]
--
Bosko Milekic
[EMAIL PROTECTED]
[EMAIL PROTECTED]
To
Please ignore the rhetoric from the anonymous poster...
Thanks developers for good work.
tomdean
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
At 08:39 AM 6/18/2002 +, Bill Flamerola wrote:
Okay, this is not really intended as a flame, but kinda necessary, given
the current situation in the FreeBSD camp.
OMG R U SERIOUS? Thx for the warning, I'll ditch FreeBSD and load NetBSD
right now.
On 18 Jun 2002 at 10:21, Christopher Schulte wrote:
At 08:39 AM 6/18/2002 +, Bill Flamerola wrote:
Okay, this is not really intended as a flame, but kinda necessary, given
the current situation in the FreeBSD camp.
OMG R U SERIOUS? Thx for the warning, I'll ditch FreeBSD and load
* Randall Hamilton [EMAIL PROTECTED] [020618 04:13] wrote:
right...
and to bring all these VILE people to public knowledge...you use a hotmail
addr and a name that we are supposed to see as 'witty' or 'clever'.
please don't take the silence from the people on the respeced boards you
--- Bill Flamerola [EMAIL PROTECTED] wrote:
I'm talking to you, fucking Hiten Pandya, damned asshole. And I'm talking
to you, stupid Alfred Perlstein. Alfred is an interesting person. He seems
I know this address of yours is shit, but I know you read this list.
I think you are making nice
Lets stop the thread now please.
Hiten Pandya wrote:
--- Bill Flamerola [EMAIL PROTECTED] wrote:
I'm talking to you, fucking Hiten Pandya, damned asshole. And I'm talking
to you, stupid Alfred Perlstein. Alfred is an interesting person. He seems
I know this address of yours is shit,
On Tue, 18 Jun 2002, Alfred Perlstein wrote:
All I really have to say about the matter is that nothing says lack of
genitalia like an anonymous hotmail account. :)
You have a way with words there, Alfred.
To add insult to injury nothing says lack of grey matter like:
X-Originating-IP:
At 02:39 AM 6/18/2002, Bill Flamerola wrote:
Okay, this is not really intended as a flame, but kinda necessary, given the current
situation in the FreeBSD camp.
Let's see, some weeks ago a couple of people dropped their ports maintainership, why
did this happen? Sergey dropped his ports
At 13:48 18/06/2002 -0600, Brett Glass wrote:
At 02:39 AM 6/18/2002, Bill Flamerola wrote:
[snip]
You actually make some good points about the nastiness of some people
in the FreeBSD community.
I don't understand this. Where does all this nastiness happen?
Maybe it's on -core. I don't
On 30-Oct-00 David O'Brien wrote:
On Fri, Oct 27, 2000 at 01:24:17PM -0700, Matt Dillon wrote:
I think that the days of the 'dangerously dedicated partition' are
numbered.
Not quite. We don't do slices on the Alpha -- in fact our slice code
royally screws the Alpha users as it
On Fri, Oct 27, 2000 at 01:10:56PM +0200, Robert Nordier wrote:
Just doing the disklabel -w -r followed by the disklabel -B is creating
a dangerously dedicated disk,
Actually this is a "fully dedicated" disk. (made to look like a 50MB or
so disk to M$ products)
Sysinstall is used to create a
In message [EMAIL PROTECTED], Matt Dillon
writes:
:I think there is more there than anyone wants to find out. Can you commit
:your fixes to make disklabel label virgin slices please?
:
:John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
Yah, it's done. I'll forward merge
On Fri, Oct 27, 2000 at 01:24:17PM -0700, Matt Dillon wrote:
I think that the days of the 'dangerously dedicated partition' are
numbered.
Not quite. We don't do slices on the Alpha -- in fact our slice code
royally screws the Alpha users as it isn't nicely layered and thus hard
to
On Mon, 30 Oct 2000, John Baldwin wrote:
On 30-Oct-00 David O'Brien wrote:
On Fri, Oct 27, 2000 at 01:24:17PM -0700, Matt Dillon wrote:
I think that the days of the 'dangerously dedicated partition' are
numbered.
Not quite. We don't do slices on the Alpha -- in fact our
I've messed with these a lot and I'm pretty sure that the bios is trying
to be 'compatible' with the geometry information it finds on the disk,
Theoretically, if you set up a disk with one brand X disk controller,
you'll get a different fake CHS mapping than you would with a brand Y
controller.
David O'Brien wrote:
On Fri, Oct 27, 2000 at 01:10:56PM +0200, Robert Nordier wrote:
Just doing the disklabel -w -r followed by the disklabel -B is creating
a dangerously dedicated disk,
Actually this is a "fully dedicated" disk. (made to look like a 50MB or
so disk to M$ products)
Well, for one thing, 99% of the PC architecture assumes that the first
track is reserved for the MBR so to speak, so putting boot1 in the MBR
is already bogus.
but boot one replaces the MBR with better code and an fdisk table. It
does it have a 'bogus' fdisk table in it already. The only
On 30-Oct-00 Matthew Jacob wrote:
On Mon, 30 Oct 2000, John Baldwin wrote:
On 30-Oct-00 David O'Brien wrote:
On Fri, Oct 27, 2000 at 01:24:17PM -0700, Matt Dillon wrote:
I think that the days of the 'dangerously dedicated partition' are
numbered.
Not quite. We don't do
In message [EMAIL PROTECTED], John Baldwin writes:
On 28-Oct-00 Cy Schubert - ITSD Open Systems Group wrote:
In message [EMAIL PROTECTED], Matt Dillon
writes:
:Do you have dangerously dedicated mode on by chance? Some
:SCSI BIOS's _will_ crash with this if you use dangerously
I know I'm getting into this late but I can reliably reproduce this
problem. I ran into it about 3 months ago when using a custom PXE-based
installer for our SCSI boxes. I even annoyed -hackes and got John Baldwin
to help me decode the register dumps. The IP does end up in the SCSI BIOS
On Fri, 27 Oct 2000, Paul Saab wrote:
Mike Smith ([EMAIL PROTECTED]) wrote:
:I'm just curious. How many disks are in this box? We saw something
:similar here at work and it turned out that there were multiple disklabels
:on the other disks and for somereason it was confusing the
On 27-Oct-00 Robert Nordier wrote:
around the broken bioses I use. I just might start using program posted
in this thread that lets you do labels right in lieu of anything else, or
perhaps I'll fix disklabel to work right as was suggeseted elsewhere.
Don't sysinstall work in a script
: After fdisk creating partitions try,
:
: dd if=/dev/zero of=/dev/da0s1 count=16
:
:Hmm. Isn't the only thing that's suppose to really work is
:
:dd if=/dev/zero of=/dev/da0 count=16
:
:(which doesn't always work on Alpha yet)
:
:I'm missing some context, so forgive me if this is a stupid
Ah, the joys of fdisk and disklabels. I've learned more in the last
two days then I ever really wanted to find out :-)
# clear out feldercarp at the base of the
# disk and create a real slice for freebsd. Install
# the MBR.
#
dd if=/dev/zero
On 28-Oct-00 Cy Schubert - ITSD Open Systems Group wrote:
In message [EMAIL PROTECTED], Matt Dillon
writes:
:Do you have dangerously dedicated mode on by chance? Some
:SCSI BIOS's _will_ crash with this if you use dangerously
:dedicated mode.
Yup.
The real question is: Ok,
In message [EMAIL PROTECTED], Matt Dillon
writes:
I think that the days of the 'dangerously dedicated partition' are
numbered. It has obviously caused much more havoc then people have
realized. We don't have time to fix it for the current release, but I
took a good hard
Cool idea. I will add a -z option to the disklabel code and submit it to the
author if thats OK with everyone else?
--
Jamie Heckford
Chief Network Engineer
Psi-Domain - Innovative Linux Solutions. Ask Us How.
===
email: [EMAIL PROTECTED]
web:
On 28-Oct-00 Matt Dillon wrote:
: After fdisk creating partitions try,
:
: dd if=/dev/zero of=/dev/da0s1 count=16
:
:Hmm. Isn't the only thing that's suppose to really work is
:
:dd if=/dev/zero of=/dev/da0 count=16
:
:(which doesn't always work on Alpha yet)
:
:I'm missing some context, so
In message [EMAIL PROTECTED], Matt Dillon
writes:
:Do you have dangerously dedicated mode on by chance? Some
:SCSI BIOS's _will_ crash with this if you use dangerously
:dedicated mode.
Yup.
The real question is: Ok, so if I can't use dangerously dedicated
mode, then how
John Baldwin writes:
On 28-Oct-00 Cy Schubert - ITSD Open Systems Group wrote:
In message [EMAIL PROTECTED], Matt Dillon
writes:
:Do you have dangerously dedicated mode on by chance? Some
:SCSI BIOS's _will_ crash with this if you use dangerously
:dedicated mode.
Yup.
On 28-Oct-00 Matt Dillon wrote:
: I think you are specifying the wrong arguments to disklabel; I
: seem to rememebr a -w/-W distinction...
:
:Nope.
:
: In any case, I'm running with a disklabel inside a DOS partition
: on all but one box of mine, and always have been. I installed
: 4.1 on my
:I have a bunch boxes based on the L440GX+ intel motherboard that get
:confused by 'dangerously dedicated' labels. If you want real fun, dd
:boo0 from 3.4 onto the first block of any hard disk in your system and
:you will be unable to boot _any_ device in your system as the bios gets a
:wedgie
Fred Clift wrote:
Why not edit the partition table after boot1 gets installed?
Because you can never make it valid. By keeping it the same set of
illegal values, at least the system can recognise it.
What do you mean it can't be made valid? fdisk -u and a few keystrokes
Robert Nordier [EMAIL PROTECTED] writes:
o Don't use dangerously dedicated mode.
I'd love to but the tools for automated installs in non-dedicated mode
dont really exist in a supported way. One of the things that was pointed
out in the thread is that disklabel doesn't work inside an
Thanks for the program.
I think, however, that the proper solution is to make disklabel work
with slices. We shouldn't need three programs to label a disk...
if fdisk and disklabel can't do the job then our distribution is broken.
I am going to spend some time
On 27-Oct-00 Terry Lambert wrote:
Thanks for the program.
I think, however, that the proper solution is to make disklabel work
with slices. We shouldn't need three programs to label a disk...
if fdisk and disklabel can't do the job then our distribution is broken.
Why not edit the partition table after boot1 gets installed?
Because you can never make it valid. By keeping it the same set of
illegal values, at least the system can recognise it.
What do you mean it can't be made valid? fdisk -u and a few keystrokes
later and I have a valid
: I think you are specifying the wrong arguments to disklabel; I
: seem to rememebr a -w/-W distinction...
:
:Nope.
:
: In any case, I'm running with a disklabel inside a DOS partition
: on all but one box of mine, and always have been. I installed
: 4.1 on my laptop that way.
:
:Sysinstall can
If you do a hexdump on boot0 and the first sector of your disk, you'll see
that boot0 has been copied onto your disk, broken partition table and
all. If you then run fdisk on the disk and put in the 'right' number of
sectors and let it automatically recalculate everything else, you'll get a
On Fri, 27 Oct 2000, Robert Nordier wrote:
Just doing the disklabel -w -r followed by the disklabel -B is creating
a dangerously dedicated disk, which your BIOS apparently doesn't like.
(See the first hex dump you did, where boot1 has ended up in the MBR.)
That's why installing boot
On Fri, 27 Oct 2000, Fred Clift wrote:
If you do a hexdump on boot0 and the first sector of your disk, you'll see
that boot0 has been copied onto your disk, broken partition table and
a typo/thinko -- replace boot0 here with boot1
--
Fred Clift - [EMAIL PROTECTED] -- Remember: If brute
On 27-Oct-00 Matt Dillon wrote:
:I have a bunch boxes based on the L440GX+ intel motherboard that get
:confused by 'dangerously dedicated' labels. If you want real fun, dd
:boo0 from 3.4 onto the first block of any hard disk in your system and
:you will be unable to boot _any_ device in your
So let me see if I get this -- the recommended way to install is to have
fdisk slices, and inside (one of) those slices have FreeBSD
lables. However, right now, other than using the program posted in this
thread, getting creative with dd is the only way to set up lables
like that in an
Mike Smith ([EMAIL PROTECTED]) wrote:
:I'm just curious. How many disks are in this box? We saw something
:similar here at work and it turned out that there were multiple disklabels
:on the other disks and for somereason it was confusing the loader.
:We dd'd the bad sections off and
I was testing the PXE stuff and booting one of the boxes regularly.
All of a sudden every time I reboot I get:
...
BIOS drive A: is disk0
int= err= efl=00030246 eip=1d29
eax= ebs=0390 ecx= edx=
esi=8db7 edi=1c09
:
: :I'm just curious. How many disks are in this box? We saw something
: :similar here at work and it turned out that there were multiple disklabels
: :on the other disks and for somereason it was confusing the loader.
: :We dd'd the bad sections off and everything worked.
:
:Are you sure
:Danny Braniss ([EMAIL PROTECTED]) wrote:
: In message [EMAIL PROTECTED]you write:
: }This is really weird. I have two valinux rackmount boxes, duel cpu's.
: }
: }I was testing the PXE stuff and booting one of the boxes regularly.
: }All of a sudden every time I reboot I get:
: }
:
Matt Dillon wrote:
:
: Raw data on disk after 'disklabel -w -r da0 auto; disklabel -B da0 auto'
:
:If you added "auto" after the "disklabel -B", that may be your problem.
:
:--
:Robert Nordier
type-o. No auto for the -B still blows up the dos partition
table.
Just doing
: # optional dd if you are paranoid
: # dd if=/dev/zero of=/dev/da0 bs=32k count=4
: fdisk -I da0
: disklabel -w -r da0s1 auto
:
: That's much preferable to having to use sysinstall if all you want to
: do is initialize a label on a slice.
:
:Yes, this is
This is really weird. I have two valinux rackmount boxes, duel cpu's.
I was testing the PXE stuff and booting one of the boxes regularly.
All of a sudden every time I reboot I get:
...
BIOS drive A: is disk0
int= err= efl=00030246 eip=1d29
eax=
On 28-Oct-00 Matt Dillon wrote:
: # optional dd if you are paranoid
: # dd if=/dev/zero of=/dev/da0 bs=32k count=4
: fdisk -I da0
: disklabel -w -r da0s1 auto
:
: That's much preferable to having to use sysinstall if all you want to
: do is initialize a label on
Matt Dillon wrote:
Raw data on disk after 'disklabel -w -r da0 auto; disklabel -B da0 auto'
If you added "auto" after the "disklabel -B", that may be your problem.
--
Robert Nordier
[EMAIL PROTECTED]
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
:I'm just curious. How many disks are in this box? We saw something
:similar here at work and it turned out that there were multiple disklabels
:on the other disks and for somereason it was confusing the loader.
:We dd'd the bad sections off and everything worked.
:
:paul
I've got one IDE
:I'm just curious. How many disks are in this box? We saw something
:similar here at work and it turned out that there were multiple disklabels
:on the other disks and for somereason it was confusing the loader.
:We dd'd the bad sections off and everything worked.
Are you sure it's
On 27-Oct-00 Matt Dillon wrote:
This is really weird. I have two valinux rackmount boxes, duel cpu's.
I was testing the PXE stuff and booting one of the boxes regularly.
All of a sudden every time I reboot I get:
...
BIOS drive A: is disk0
int= err=
On 27-Oct-00 Matt Dillon wrote:
:Danny Braniss ([EMAIL PROTECTED]) wrote:
: In message [EMAIL PROTECTED]you write:
: }This is really weird. I have two valinux rackmount boxes, duel cpu's.
: }
: }I was testing the PXE stuff and booting one of the boxes regularly.
: }All of a sudden
:
: I was testing the PXE stuff and booting one of the boxes regularly.
: All of a sudden every time I reboot I get:
:
: ...
: BIOS drive A: is disk0
:
: int= err= efl=00030246 eip=1d29
: eax= ebs=0390 ecx= edx=
: esi=8db7
On 27-Oct-00 Matt Dillon wrote:
The real question is: Ok, so if I can't use dangerously dedicated
mode, then how do I create a disklabel on a normal partition? Everything
I try using fdisk and disklabel fails. fdisk will create a normal
freebsd-dedicated dos partition,
Raw data on disk after 'disklabel -w -r da0 auto; disklabel -B da0 auto'
00f0 66 8b 46 08 52 66 0f b6 d9 66 31 d2 66 f7 f3 88 |f.F.Rf...f1.f...|
0100 eb 88 d5 43 30 d2 66 f7 f3 88 d7 5a 66 3d ff 03 |...C0.fZf=..|
0110 00 00 fb 77 44 86 c4 c0 c8 02 08 e8 40 91 88 fe
On Fri, Oct 27, 2000 at 12:46:05AM -0700, Matt Dillon wrote:
This is really weird. I have two valinux rackmount boxes, duel cpu's.
I was testing the PXE stuff and booting one of the boxes regularly.
All of a sudden every time I reboot I get:
...
BIOS drive A: is disk0
:
: disklabel -w -r da0s1 auto(label it)
:
:Disklabel can not label slices. For a project I had to work on receently
:I hacked up a slicelabel tool that used libdisk (which can handle slices)
:to initialize the disklabels in slices. The code for the slicelabel
:command is quite
-- Forwarded by Satcha Benitez/Milwaukee/RA/Rockwell on
06/16/2000 10:55 AM ---
Satcha Benitez
06/16/2000 10:33 AM
To: [EMAIL PROTECTED]
cc:
Subject: Problem installing FreeBSD 4.0
Hi,
My name is Satcha Benitez and I'm trying to install FreeBSD
Hello,
I have some problem with Apache. I have few Apache modules (written by
me), they are working with mySQL databases and based on Apache C API.
They works perfectly well at my FreeBSD 2.2.8-STABLE with Apache 1.3.9 and
mySQL 3.22.25.
When I upgrade my system to FreeBSD 3.3-STABLE
On Wed, 15 Sep 1999 10:06:59 MST, Mike Smith wrote:
Actually, as with many such cases, the floppy disk driver turned out to
be flakey. We resolved this via private mail.
Driver, or drive? The BIOS is the driver at this point in time.
Argh! Thanks. I meant the floppy drive.
Ciao,
On Wed, 15 Sep 1999 10:06:59 MST, Mike Smith wrote:
Actually, as with many such cases, the floppy disk driver turned out to
be flakey. We resolved this via private mail.
Driver, or drive? The BIOS is the driver at this point in time.
Argh! Thanks. I meant the floppy drive.
Ciao,
On Tue, 14 Sep 1999 15:53:03 -0400, John Baldwin wrote:
FreeBSD write "zf_read: error".
Your mfsroot floppy has a bad sector. Try a different floppy.
Actually, as with many such cases, the floppy disk driver turned out to
be flakey. We resolved this via private mail.
Something to keep
FreeBSD write "zf_read: error".
Your mfsroot floppy has a bad sector. Try a different floppy.
Actually, as with many such cases, the floppy disk driver turned out to
be flakey. We resolved this via private mail.
Driver, or drive? The BIOS is the driver at this point in time.
--
On Tue, 14 Sep 1999 15:53:03 -0400, John Baldwin wrote:
FreeBSD write zf_read: error.
Your mfsroot floppy has a bad sector. Try a different floppy.
Actually, as with many such cases, the floppy disk driver turned out to
be flakey. We resolved this via private mail.
Something to keep in
FreeBSD write zf_read: error.
Your mfsroot floppy has a bad sector. Try a different floppy.
Actually, as with many such cases, the floppy disk driver turned out to
be flakey. We resolved this via private mail.
Driver, or drive? The BIOS is the driver at this point in time.
--
\\
On 13-Sep-99 Tolyar wrote:
Hello All.
I try install FreeBSD on HP Vectra VA/200DT - Pentium Pro/128Mb-RAM/
Quantum Fireball CR 4.3Gb/CirrusLogic5446PCI PCI/NE2000.
When I try install FreeBSD (I'm tried
3.2-release/3.3-19990909-rc/snapshot-4.0-19990827-current)
i have some trouble. On
On 13-Sep-99 Tolyar wrote:
Hello All.
I try install FreeBSD on HP Vectra VA/200DT - Pentium Pro/128Mb-RAM/
Quantum Fireball CR 4.3Gb/CirrusLogic5446PCI PCI/NE2000.
When I try install FreeBSD (I'm tried
3.2-release/3.3-19990909-rc/snapshot-4.0-19990827-current)
i have some trouble. On
Hello All.
I try install FreeBSD on HP Vectra VA/200DT - Pentium Pro/128Mb-RAM/
Quantum Fireball CR 4.3Gb/CirrusLogic5446PCI PCI/NE2000.
When I try install FreeBSD (I'm tried
3.2-release/3.3-19990909-rc/snapshot-4.0-19990827-current)
i have some trouble. On second floppy (mfsroot.flp) before
Hello All.
I try install FreeBSD on HP Vectra VA/200DT - Pentium Pro/128Mb-RAM/
Quantum Fireball CR 4.3Gb/CirrusLogic5446PCI PCI/NE2000.
When I try install FreeBSD (I'm tried
3.2-release/3.3-19990909-rc/snapshot-4.0-19990827-current)
i have some trouble. On second floppy (mfsroot.flp) before
92 matches
Mail list logo
