On Fri, Nov 19, 1999 at 02:52:13PM -0800, Mike Smith wrote:
The diagnostic is relatively harmless, but it suggests that /etc/fstab
is wrong.
Here is fstab line, please point what is wrong?
/dev/da0s4a / ufs rw,userquota 1 1
I have no idea; it'd
I see this:
Root mount failed: 22
This suggests you may have an old loader, or the loader's parsing of
your /etc/fstab file may be failing. I probably need to add a
diagnostic to it to help us track this down.
Mounting root from ufs:da0s4a
[snip]
Root mount failed: 6
Mounting root
--
---
Bruce Burden[EMAIL PROTECTED] Tandem Computers Inc.
512-432-8944Network Verification 14231 Tandem Blvd.
Auto answer(4 rings) Austin,
Okay, here is the problem:
cc -O -pipe -DGREP -DHAVE_STRING_H=1 -DHAVE_SYS_PARAM_H=1 -DHAVE_UNISTD_H=1
-DHAVE_GETPAGESIZE=1 -DHAVE_MEMCHR=1 -DHAVE_STRERROR=1 -DHAVE_VALLOC=1
-DHAVE_WORKING_MMAP=1 -DHAVE_LIBZ=1 -DHAVE_FTS=1 -I/usr/obj/usr/src/tmp/usr/include
-c
I see this:
Root mount failed: 22
This suggests you may have an old loader, or the loader's parsing of
your /etc/fstab file may be failing. I probably need to add a
diagnostic to it to help us track this down.
Okay, here's another one. I have 3.3-STABLE on wd0s1a, and -current
This suggests you may have an old loader, or the loader's parsing of
your /etc/fstab file may be failing. I probably need to add a
diagnostic to it to help us track this down.
Okay, here's another one. I have 3.3-STABLE on wd0s1a, and -current
(from 18. November) on wd0s1d. I boot
Please wrap your messages to 72 columns like other civilised authors.
No, I do not talking about /etc/fstab, I'm talking about what device
kernel is using to mount root *before* starting /sbin/init (e.g.
"changing root device to ..." in dmesg).
Hmm, the bootblock or the loader might be
I recently tried using dd to transfer a binary image to floppy.
It was the Linux root disk image, color.gz. Basically, dd works
ok with non-gzipped files, but with files in gzip format, it
chokes:
root@lc186 floppies# dd if=color.gz of=/dev/rfd0
dd: /dev/rfd0: Invalid
It appears to have worked. I guess the output block size of 16k
is key for floppies, then. The conv=osync does the padding.
I use 18K (one cylinder) but any multiple of 9k should work well.
No, the block size requirement for floppies is 512 bytes, as it is for
almost any device.
I was giving vinum + softupdates a bit of a workout on 4 really old
SCSI disks (Sun shoeboxes, if you must know) attached to an aha1542B.
The rest of the machine is a Pentium 133 with 64MB of parity ram, a
few more disks, and another aha1542B. It runs -current (about 10 days
old now).
I was
Add Cc: to current...
Hi,
Jeroen Ruigrok/Asmodai [EMAIL PROTECTED] wrote:
www/flashplugin dies under CURRENT's gcc 2.95.2 with:
=== Building for flashplugin-0.4.3
c++ -O2 -pipe -I/usr/X11R6/include -I./Lib -I./Plugin -fpic -fno-rtti
-DXP_UNIX -O2 -DCHECK_TEXT_PLAIN -c ./Lib/bitmap.cc
HEADS UP: (USB only)
Fields have been added to the usb_devinfo struct, so at least
src/usr.sbin/usbdevs needs to be recompiled for the latest and greatest
kernel. Ezload, available in ports/misc/ezload, as well if you use it.
Nick
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
I recently tried using dd to transfer a binary image to floppy.
It was the Linux root disk image, color.gz. Basically, dd works
ok with non-gzipped files, but with files in gzip format, it
chokes:
root@lc186 floppies# dd if=color.gz of=/dev/rfd0
dd: /dev/rfd0: Invalid
On Sun, Nov 21, 1999 at 10:36:32PM +1000, Stephen McKay wrote:
When the system came back up, fsck -p didn't like the vinum volume.
No sweat, I ran it manually. There were many
INCORRECT BLOCK COUNT I=n (4 should be 0)
messages. I assumed this was an artifact of soft updates. The
I just tried to install a 4.0 snap on a machine with a 3com
netcard, this doesn't work, and whats worse I can't make it
work.
The problem is that the ex0 or ie0 driver, I'm not sure which,
hoses the 3com card such that the ep driver cannot read the
serial eeprom.
I used to be able to disable
On Sun, Nov 21, 1999 at 12:51:59AM -0800, Mike Smith wrote:
You're not using the loader, so nothing gets to read /etc/fstab and set
vfs.root.mountfrom. Thus the kernel can't use it to find the root
filesystem. I should probably emit a diagnostic to the effect that it
wasn't set, since in
"Andrey A. Chernov" wrote:
On Sun, Nov 21, 1999 at 12:51:59AM -0800, Mike Smith wrote:
You're not using the loader, so nothing gets to read /etc/fstab and set
^^
vfs.root.mountfrom. Thus the kernel can't use it to find the root
filesystem. I should probably
I just tried to install a 4.0 snap on a machine with a 3com
netcard, this doesn't work, and whats worse I can't make it
work.
The problem is that the ex0 or ie0 driver, I'm not sure which,
hoses the 3com card such that the ep driver cannot read the
serial eeprom.
I used to be able to
On Sun, Nov 21, 1999 at 12:51:59AM -0800, Mike Smith wrote:
You're not using the loader, so nothing gets to read /etc/fstab and set
vfs.root.mountfrom. Thus the kernel can't use it to find the root
filesystem. I should probably emit a diagnostic to the effect that it
wasn't set,
In message [EMAIL PROTECTED], Mike Smith writes:
I just tried to install a 4.0 snap on a machine with a 3com
netcard, this doesn't work, and whats worse I can't make it
work.
The problem is that the ex0 or ie0 driver, I'm not sure which,
hoses the 3com card such that the ep driver cannot
I've been seeing this failure since I tried to rebuild my system
(last built on 10/9/99
I didn't see anything in UPDATING or on this list. I'm wondering if
there's a possible hardware problem -- but it's done it 3 times and
I've cvsup'd three times yesterday and today and started with the
same
I spent about 2 to 3 hours last night futzing with sysinstall and
getting the amr.ko file onto the 4.0 install disk (using the
4.0-19991114 SNAP) I tried adding the amr disks to devices.c in
sysinstall but had no luck.
Bah. I knew I forgot something there. That should just about have
On Sun, 21 Nov 1999, Mike Smith wrote:
I spent about 2 to 3 hours last night futzing with sysinstall and
getting the amr.ko file onto the 4.0 install disk (using the
4.0-19991114 SNAP) I tried adding the amr disks to devices.c in
sysinstall but had no luck.
Bah. I knew I forgot
[moving this off -current]
On Sun, 21 Nov 1999, Alfred Perlstein wrote:
Unfortunatly all the amr systems I have are now in production, I can
not test a new install on them.
The way I did manage to do the install was nfs mounting another
machine's /, /usr, and /var then using
Have any of you been seeing route table leaks in -current? I noticed
this week that cvsup-master.freebsd.org is suffering from them. I
actually had to reboot it because it couldn't allocate any more. From
the "vmstat -m" output:
Memory statistics by type Type Kern
This happens with a kernel/world from today: netscape is unusable.
Most of the time it freezes after a few seconds. Here is the tail of
kdump:
484 communicator-4.7 RET select 0
484 communicator-4.7 CALL old.sigprocmask(0x1,0)
484 communicator-4.7 RET old.sigprocmask 0
484
Hello, FYI,
KAME(IPv6, IPsec, and etc update kit for BSDs, http://www.kame.net)
netinet6 basic part is committed to freebsd-current.
It doesn't yet include several important parts (e.g.no IPsec,
no v6 multcast forwarding, no TCP/UDP for IPv6 yet),
but now it can assigne IPv6 addr automatically
The bridge drivers for sound cards have just been committed.
These drivers will accomodate coming newmidi drivers.
People using Sound Blaster 16/AWE32/AWE64/ViBRA16C/ViBRA16X
should add sbc driver to your kernel config file in addition
to pcm driver, rebuild and reinstall a new kernel. See LINT
28 matches
Mail list logo
