On Wed, May 04, 2005 at 10:28:57AM -0500, Dan Nelson wrote:
> In the last episode (May 04), Gerrit Khn said:
> > port 3 addr 2: full speed, power 40 mA, config 1, ThumbDrive(0x), Trek
> > Technology(0x0a16), rev 1.00, device ugen0
> umass only attaches to devices it recognizes. There are en
I'm writing this message to attempt to determine if anyone is actually
using either of these drivers. Please write if you are both:
- Using these drivers to connect to a real, production FDDI network
- Are running FreeBSD 5.3+ or will be in the near future
Please DO NOT write if:
- Your product
On Tue, 3 May 2005, Doug White wrote:
> Hey folks,
>
> I've taken a crack at working around the ttwwakeup() panic thats been
> reported now and again. My early analysis, based on debugging output from
> rwatson, is that a defunct struct tty gets reused without cleaning out the
> associated (stale
Marcello Maggioni wrote:
>The problem is that if I reboot without umounting that filesystem I
>get this message on reboot :
>syncing disks, buffers remaining... 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
>giving up on 2 buffers
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/56675
mkb.
___
On 5/4/05, Pete French <[EMAIL PROTECTED]> wrote:
> > Bingo! Restarting sysinstall always causes this problem. It's a well
> > known problem with several open PRs (see for example bin/38854,
> > bin/42162 and bin/45565 - all dating back to 2002). It's 100%
> > recreateable by restarting sysinsta
Hi all,
I've just installed my FreeBSD system and upgraded it to the lastest
-STABLE with buildworld .
I have an EXT3 partition on my second harddrive that I mount read-only
with the command :
mount -o ro -t ext2fs /dev/ad1s1 /mount_point
The problem is that if I reboot without umounting that f
Hello,
Just an update to my previous post about the clock speed being
misreported. As of RC4, the clockspeed appears to be reported correctly.
Thanks,
John
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-sta
Hi all,
I've just installed my FreeBSD system and upgraded it to the lastest
-STABLE with buildworld .
I have an EXT3 partition on my second harddrive that I mount read-only
with the command :
mount -o ro -t ext2fs /dev/ad1s1 /mount_point
The problem is that if I reboot without umounting that f
Running FreeBSD 4.11-STABLE ...
Has anyone seen this before? Only reference on the 'net I can find seems
to be similar issue on a Dragonfly system:
http://leaf.dragonflybsd.org/mailarchive/bugs/2004-09/msg00176.html
Mine is a 9500-4LP controller ...
Marc G. Fournier Hub.Org Netwo
> Bingo! Restarting sysinstall always causes this problem. It's a well
> known problem with several open PRs (see for example bin/38854,
> bin/42162 and bin/45565 - all dating back to 2002). It's 100%
> recreateable by restarting sysinstall realatively early in the install
> procedure, and I've
On Wed, 2005-05-04 at 12:29 +0100, Pete French wrote:
> > I haven't been able to reproduce this yet. I've successfully done an
> > FTP install both from an initial floppy boot and from an initial disc1
> > CD boot. So it's not a "totally generic" problem, it might have
> > something to do with th
In the last episode (May 04), Gerrit Khn said:
> has anyone used the subject successfully with -stable? umass(4)
> mentions the 8MB version, so I thought 16MB should actually work,
> too. However, when I plug the device in, I just get
>
> ugen0: Trek Technology ThumbDrive, rev 1.10/1.00, addr 2
>
On Wed, May 04, 2005 at 04:26:48PM +0200, Marc Olzheim wrote:
> > You _do_ have scsi disk support (device da) enabled in your kernel ?
> And loaded the umass module or have it in your kernel, for that matter ?
Yes, of course. As I said before: I have working externel USB-HD, a working
USB-MP3-Pla
On Wed, May 04, 2005 at 04:23:51PM +0200, Marc Olzheim wrote:
> > ugen0: Trek Technology ThumbDrive, rev 1.10/1.00, addr 2
> > and no umass device.
> > Any hints how to make this work?
> You _do_ have scsi disk support (device da) enabled in your kernel ?
Yes, I do. I have two SCSI-Controllers
On Wed, May 04, 2005 at 04:23:51PM +0200, Marc Olzheim wrote:
> > Any hints how to make this work?
>
> You _do_ have scsi disk support (device da) enabled in your kernel ?
And loaded the umass module or have it in your kernel, for that matter ?
Marc
pgpWpcRUFu55s.pgp
Description: PGP signature
On Wed, May 04, 2005 at 02:19:13PM +0200, Gerrit Khn wrote:
> Hi folks,
>
> has anyone used the subject successfully with -stable?
> umass(4) mentions the 8MB version, so I thought 16MB should actually work,
> too. However, when I plug the device in, I just get
>
> ugen0: Trek Technology ThumbDri
Hi folks,
has anyone used the subject successfully with -stable?
umass(4) mentions the 8MB version, so I thought 16MB should actually work,
too. However, when I plug the device in, I just get
ugen0: Trek Technology ThumbDrive, rev 1.10/1.00, addr 2
and no umass device.
usbdevs shows
port 3 add
> I haven't been able to reproduce this yet. I've successfully done an
> FTP install both from an initial floppy boot and from an initial disc1
> CD boot. So it's not a "totally generic" problem, it might have
> something to do with the pathway you are following through sysinstall.
Possibly. I h
El Miércoles, 4 de Mayo de 2005 09:36, Danny Braniss escribió:
> sorry if this looks like im highjacking hte thread, but i've
> submitted a PR http://www.freebsd.org/cgi/query-pr.cgi?pr=61239
> which among other things, places ALL the dhcp variables in the
> environment.
>
> danny
I can't see how
sorry if this looks like im highjacking hte thread, but i've submitted
a PR http://www.freebsd.org/cgi/query-pr.cgi?pr=61239
which among other things, places ALL the dhcp variables in the environment.
danny
___
freebsd-stable@freebsd.org mailing list
h
El Jueves, 28 de Abril de 2005 15:42, Jose M Rodriguez escribió:
> Hi,
>
> I note that the long standing bug that prevents do a nfsroot mount
> after operate pxeloader in tftp mode is recent solved in -CURRENT
> pxe.c
>
> I think this can be missed for 5.4 REL, but I'll be glad to see this
> MFC as
21 matches
Mail list logo