On Thu, Dec 26, 2002 at 11:38:00PM +0100, Jens Rehsack wrote:
> correct me if I'm wrong, but shouldn't be the fdimage tool for creating
> disk images under DOS on the first cd of 5.0-RC2 (and later RELEASE)?
Yes, fdimage is one of many tools that should be included in the
'tools' directory on t
On Mon, 30 Dec 2002, Roderick van Domburg wrote:
> For three days in a row now I have tried installing the most recent 5.0
> snapshots on my Armada V300 from floppies. I have also tried the RC2
> floppies.
I just installed RC2 using a 3C574B with the 'ep' driver; worked just fine
aside from needin
I've seen a few discussions of sysinstall vs disklabels, but this
problem looks a little different.
I sliced up a 37G disk with 4.7-RELEASE on ad0s1, Win2k on ad0s[23]
and ad0s4 empty. I installed grub-0.92, putting the bootloader in
the MBR and config files in ad0s1a. Everything worked fine.
The
I'm sorry, I have realised that nothing in the /dev directory is being
populated in the chroot by the buildworld attempt, so there is
something problematic further down the chain.
I'm an idiot - thanks and sorry for the bother.
On Mon, Dec 30, 2002 at 08:54:14PM -0500, Robert Watson wrote:
>
>
In message: <[EMAIL PROTECTED]>
Michael Ranner <[EMAIL PROTECTED]> writes:
: Am Montag, 30. Dezember 2002 23:10 schrieb Lee Damon:
: > I have the same problems on an IBM T30 with integrated wi running
: > 4.7-STABLE. In fact, I've had this problem since 4.5 (which is where I
: > started
On Mon, Dec 30, 2002 at 10:19:32PM -0500, Brent Verner wrote:
> [2002-12-30 18:53] Kris Kennaway said:
> | I just wanted to share the good news that since updating to matt's
> | vmspace fix (over a week ago), there have been no panics on the bento
> | cluster (21 machines of 3 architectures running
A nullfs mounted target cannot be umounted if another target is
mounted from the same source. Maybe it has something to do with
the LOR in the first umount... I'll see if I can fix this later
in the week if it hasn't already been fixed.
scratch# uname -a
FreeBSD scratch.rcfile.org 5.0-CURRENT
[2002-12-30 18:53] Kris Kennaway said:
| I just wanted to share the good news that since updating to matt's
| vmspace fix (over a week ago), there have been no panics on the bento
| cluster (21 machines of 3 architectures running 5.0-RC, under constant
| heavy load, and despite the close proximity
I was finally able to reproduce this. Here are some offset values:
Dec 30 10:55:07 lizzy kernel: spec_getpages:(md0) I/O read failure: (error=22) b
p 0xce5fb488 vp 0xc41e4708
Dec 30 10:55:07 lizzy kernel: size: 6144, resid: 6144, a_count: 6124, valid: 0x0
Dec 30 10:55:07 lizzy kernel: nread: 0, re
On Mon, Dec 30, 2002 at 06:53:52PM -0800, Kris Kennaway wrote:
> I just wanted to share the good news that since updating to matt's
> vmspace fix (over a week ago), there have been no panics on the bento
> cluster (21 machines of 3 architectures running 5.0-RC, under constant
> heavy load, and desp
In message: <[EMAIL PROTECTED]>
Juli Mallett <[EMAIL PROTECTED]> writes:
: /var/log/messages:Dec 30 17:11:35 luna kernel: wi0: failed to allocate 1594 bytes on
:NIC
:
: Like those?
Those are usually an indication of no interrupts. Memory is allocated
when packets are sent and deallo
I just wanted to share the good news that since updating to matt's
vmspace fix (over a week ago), there have been no panics on the bento
cluster (21 machines of 3 architectures running 5.0-RC, under constant
heavy load, and despite the close proximity of Peter Wemm in the
datacenter for a few hours
On Mon, 30 Dec 2002, Marc Butler wrote:
> I'm currently trying to build CURRENT (DEC 29 2002) within a chroot
> environment under CURRENT (DEC 17 2002). Presently I am stuck on an
> error which appears to be related to /dev/stdout in a chroot environment
> (devfs?).
Could you provide a bit mor
* De: Taavi Talvik <[EMAIL PROTECTED]> [ Data: 2002-12-30 ]
[ Subjecte: Re: My wi(4) ate itself (or Fun with no memory). ]
> On Mon, 30 Dec 2002, M. Warner Losh wrote:
>
> > In message: <[EMAIL PROTECTED]>
> > Juli Mallett <[EMAIL PROTECTED]> writes:
> > : I ran some stuff over
On Mon, 30 Dec 2002, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> Juli Mallett <[EMAIL PROTECTED]> writes:
> : I ran some stuff overnight which exhausted my system's memory fairly well,
> : and was also thrashing around on my network, and I woke up to find that my
> : wi(4
> Date: Mon, 30 Dec 2002 23:06:50 +0100
> From: Christian Brueffer <[EMAIL PROTECTED]>
> Sender: [EMAIL PROTECTED]
>
>
> --x+6KMIRAuhnl3hBn
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
>
> On Mon, Dec 30, 2002 at 11:36:4
suscribe
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I'm currently trying to build CURRENT (DEC 29 2002) within a chroot
environment under CURRENT (DEC 17 2002). Presently I am stuck on an
error which appears to be related to /dev/stdout in a chroot
environment (devfs?).
Specifically writing to /dev/stdout does not work (specifically:
genassym.sh).
On Mon, 30 Dec 2002 [EMAIL PROTECTED] wrote:
> Can you please:
> dd if=/dev/da2 bs=64k | uuencode - foo | mail [EMAIL PROTECTED]
^^
You probably should add count=1 there, otherwise it's going to be a big
email.
-Nate
To Unsubscribe: send mail to [EMAIL PROTECTE
From: "Chuck Robey" <[EMAIL PROTECTED]>
Sent: Monday, December 30, 2002 5:02 PM
> The moral is, I think you need to rebuild/reinstall dri-devel if you're
> running FreeBSD-current.
I have found that it's generally a good idea to rebuild any modules you have
from ports (in my case it's ltmdm and r
Am Montag, 30. Dezember 2002 23:10 schrieb Lee Damon:
> I have the same problems on an IBM T30 with integrated wi running
> 4.7-STABLE. In fact, I've had this problem since 4.5 (which is where I
> started on this system.)
I think the "wi0: timeout in wi_cmd 0x; event status 0x8000"
messages st
Hello,
For three days in a row now I have tried installing the most recent 5.0
snapshots on my Armada V300 from floppies. I have also tried the RC2 floppies.
Unfortunately, the system freezes up solid when it configures ep0. I have a
DHCP server here but manually entering the IP configuration
* De: Christian Brueffer <[EMAIL PROTECTED]> [ Data: 2002-12-30 ]
[ Subjecte: Re: My wi(4) ate itself (or Fun with no memory). ]
> The bad thing is, that the chip is integrated in my notebook so i can't simply
> take it out and back in again :-)
> Is there any other way to reinitialize the
I have the same problems on an IBM T30 with integrated wi running 4.7-STABLE.
In fact, I've had this problem since 4.5 (which is where I started on
this system.)
nomad
> On Mon, Dec 30, 2002 at 11:36:45AM -0800, Juli Mallett wrote:
> > Hey,
> >=20
> > I ran some stuff overnight which exhausted my
To those of you running the radeon.ko dri module from the ports
(ports/graphics/dri-devel) IF YOU'RE RUNNING CURRENT then you might want
to listen up.
I just did a rebuild of the system for the first time in about 6 days, and
my system rebooted immediately when XFree86 attempted loading the
radeon
Am Montag, 30. Dezember 2002 22:58 schrieben Sie:
> * De: Michael Ranner <[EMAIL PROTECTED]> [ Data: 2002-12-30 ]
> [ Subjecte: mount_portalfs broken in 5.0-RC2 ]
>
> > 1.)
> >
> > After mounting the portalfs,
> >
> > # cat /p/tcp/www.jawa.at/21
> > 220 ftp.jawa.at FTP server (ftpd) ready.
>
On Mon, Dec 30, 2002 at 11:36:45AM -0800, Juli Mallett wrote:
> Hey,
>
> I ran some stuff overnight which exhausted my system's memory fairly well,
> and was also thrashing around on my network, and I woke up to find that my
> wi(4) blew up more or less:
>
> wi0: watchdog timeout
> wi0: timeout i
Hello,
as announced on freebsd-hackers a few days ago, I ported the
rfilter/wfilter features of NetBSD's mount_portal to 4.7-p2.
Because the port was very trivial and rfilter/wfilter worked
well on 4.7-p2, I tried to merge the code in 5.0-RC2 mount_portalfs
and discovered, that mount_portalfs did
In message: <[EMAIL PROTECTED]>
Juli Mallett <[EMAIL PROTECTED]> writes:
: I ran some stuff overnight which exhausted my system's memory fairly well,
: and was also thrashing around on my network, and I woke up to find that my
: wi(4) blew up more or less:
:
: wi0: watchdog timeout
: w
It runs fine for me off of a fresh RC2 install. I run KDE 3.0.5 on top of
it.
Tom Veldhouse
- Original Message -
From: "Peter Kostouros" <[EMAIL PROTECTED]>
To: "walt" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, December 30, 2002 3:20 PM
Subject: Re: Trouble building X on f
Hi
It has been mentioned a few times, though not specifically for RC2.
Check the archives for
subjects "X server - undefined symbols" and "XFree 4.2.1 doesn't work
with last CURRENT".
walt wrote:
I've installed RC2 on my new ASUS A7V8X/AthlonXP and the
whole thing went very well except for bu
Tinderbox FAQ: http://people.FreeBSD.org/~mike/tinderbox.html
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
-
On 19-Dec-2002 Matthew Dillon wrote:
> This is a real mess but I finally got it to work. (Note
> to John: both quirk entries are absolutely necessary,
> everything stalls and dies without them).
You might need to lie to umass and tell if to use the UFI or ATAPI
protocols instead of
Hey,
I ran some stuff overnight which exhausted my system's memory fairly well,
and was also thrashing around on my network, and I woke up to find that my
wi(4) blew up more or less:
wi0: watchdog timeout
wi0: timeout in wi_cmd 0x0002; event status 0x8000
wi0: timeout in wi_cmd 0x; event stat
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
Ever since RC2 I have had to manually execute the following two lines
from my rc.conf, because they are not set at boot.
ifconfig_fxp0="DHCP"
ifconfig_wi0="inet up ssid my_ap mediaopt hostap"
Have I missed something?
Thanks,
Pete...
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscr
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
Anyone else get more digest than normal. In the last week or so I
now get 5 copies of each digest and have done nothing at all on my
side with any subscriptions.
Bill
--
Bill Vermillion - bv @ wjv . com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the bod
Hello,
[taken from -hackers]
> Can you try use tcpdump to comparte something that works with the code
> that doesn't.
tcpdump -i fec0 shows the following:
if I ping our-router I see the packages going out, but nothing coming
back.
The switch shows 0 input packets.
I pinged the machine, then it p
Tinderbox FAQ: http://people.FreeBSD.org/~mike/tinderbox.html
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
-
In message <[EMAIL PROTECTED]>, Andrey Koklin writes:
>Hi folks,
>
>Silly question, perhaps, but I wasn't able to figure out source of the
>problem myself...
>
>I used rarely magneto-optical disks to transfer data to/from Windows
>machine. For compatibility, disks used HDD FAT16 format.
>About a m
> Agreed. It really should be an int * like it used to be. But it's
> up to Mark Murray to fix it since it was his commit that changed it
> to a size_t in the first place.
I'm not religiously attached to this. If you want to change it before
I get to it, go ahead.
M
--
Mark Murray
i
Tinderbox FAQ: http://people.FreeBSD.org/~mike/tinderbox.html
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
-
On Mon, Dec 23, 2002 at 10:55:05 -0800, Matthew Dillon wrote:
>
> That's very odd. I see them on my development box too which is just
> talking FreeBSD<->FreeBSD. We should not be seeing them at all.
I found that big source of them is Windows machines when Selective
acknowledgement is
Hi folks,
Silly question, perhaps, but I wasn't able to figure out source of the
problem myself...
I used rarely magneto-optical disks to transfer data to/from Windows
machine. For compatibility, disks used HDD FAT16 format.
About a month ago the disks began to refuse to mount under -current:
#
On Sun, Dec 29, 2002 at 08:24:23PM +0100, Simon 'corecode' Schubert wrote:
> would please somebody look into this case and explain why wchar_t
> support wasn't enabled?
Because the GCC developers disabled it for GCC 3.2.1
> tim robins already provided a patch that will make stuff working.
Pleas
46 matches
Mail list logo
