> Absolutely worst case, the root user could log in remotely, gdb
> your screen saver, type "foobar" as the password, and then hack
> the authentication function return value to say "yes, that's the
> correct password for "[EMAIL PROTECTED]", and get in without needing
> to have xscreensaver accept
On Thursday 28 August 2003 10:33 pm, Orion Hodson wrote:
> Could you revert to head and check that the mixer "ogain" is non-zero
> (say 100 :-)? On some codecs "ogain" provides the traditional
> functionality of "vol". I appreciate this is not ideal.
OTOH, "OGain" makes *SLIGHTLY* more sense for
On Monday 25 August 2003 09:27 pm, Craig Boston wrote:
> Anyway, I'm attaching a quick workaround if anyone else running current
> runs in to this.
Earth to brain, come in please! Actually attaching the patch this time.
--- unix_mixer.c.orig Mon Aug 25 21:10:46 2003
+++ unix_mixer.c
Cameron Grant wrote:
> cg 2003/08/14 18:24:36 PDT
>
> FreeBSD src repository
>
> Modified files:
>sys/sys soundcard.h
> Log:
> add a few missing bits for future use
>
> Revision ChangesPath
> 1.42 +27 -1 src/sys/sys/soundcard.h
FYI, this change breaks
On Monday 11 August 2003 11:04 am, Joe Marcus Clarke wrote:
> [EMAIL PROTECTED]:29:7:class=0x0c0320 card=0x015f1028 chip=0x24cd8086
> rev=0x03
> hdr=0x00
> vendor = 'Intel Corporation'
> device = '82801DB (ICH4) USB EHCI Controller'
> class= serial bus
> subclass = U
As a data point, here's what happens with mine (this is on current cvsupped
this morning). Lots of output that probably isn't very useful. I'm pretty
baffled as to why the controller suddenly decides that it doesn't want to
work. Guess it's time to try to find the EHCI spec...
usb_event_thre
On Wednesday 23 July 2003 04:26 pm, Ryan T. Dean wrote:
> [...] The FreeBSD boot program came back,
> however, when I attempt to load FreeBSD, it merely beeps at me. It will,
> however, boot into W2k. I've tried supping, rebuilding the boot blocks (cd
> src/sys/boot; make install; fdisk -B -b /bo
On Friday 11 July 2003 04:09 pm, Mike Porter wrote:
> ON the old nvidia driver, I couldn't use GL without crashing, now, it works
> fine. Granted I haven't done anything like repeatedly running glxinfo or
> anything (is there a need/desire for this?)
Just to clarify, repetedly running glxinfo see
Hi, all,
Just wondering if anyone has had any experiences (good or bad) with the new
nvidia driver on CURRENT? So far I've found it to be pretty unstable... I
tried reverting back to 5.1-RELEASE and recompiling the driver (i'm
installing it from the port), but no luck.
It works fine in 2D mo
On Monday 30 June 2003 08:34 pm, Jud wrote:
> I think Jesse Guardini's suggestion works when Win and FreeBSD are on the
> same drive. You can still use the NT/2K/XP bootloader when the OSs are on
> different drives, but problem is, I could never figure out exactly what the
> FAQ was trying to tell
> : xl0: <3Com 3c575B Fast Etherlink XL> port 0x1000-0x107f mem
> : 0x8800-0x887f,0x8880-0x88ff irq 11 at device 0.0 on
> : cardbus0
>
> That's not 4k! :-(
Ok, if I'm reading this right:
rman_reserve_resource: request: [0x8880,
0x88ff],
length 0x80, flags 12288, device x
On Tue, 2003-06-17 at 08:21, M. Warner Losh wrote:
> Does the following, untested, patch help any better than your gross
> kludges?
Hrm, actually it seems to have made it worse... Now they don't attach
at all.
xl0: <3Com 3c575B Fast Etherlink XL> port 0x1000-0x107f mem
0x8800-0x887f,0x88
In continuing my quest to make FreeBSD current run flawlessly on my
laptop, I'm trying to track down some issues with using multiple cardbus
cards (more info on my particular problem and a workaround at the end of
this message). I'd like to gather some information from people who have
cardbus cont
Below is a preliminary patch that seems to at least keep the machine from
panicing when detaching USB cards :)
It's still highly experimental, so use at your own risk. It works well enough
for me to plug in / unplug my cardbus card repeatedly (even with devices
attached to it). Theoretically
Okay, sorry for the reply-to-self, but I think I've nailed down the detach
problem and it looks like it will require some more work. In short, the OHCI
driver may be ready for hot-plugging but the USB subsystem isn't. Here's a
play-by-play of what's happening:
1. On card removal, cardbus_deta
On Thursday 12 June 2003 07:15 am, Bernd Walter wrote:
> I'm not shure if the code would work, but it was also ported into ehci
> and therefor ehci should be in a similar state.
> Well loosing memory is better than panic.
> I have no cardbus - can this be tested with a module?
Well, the card no lo
On Fri, 2003-06-13 at 14:17, Tony Naggs wrote:
> Yes, I think you should also do this for Uhci. There are probably not
> many straight Uhci USB 1.1 Cardbus cards, but it is likely some of the
> USB 2.0 cards have an UHCI controller rather than OHCI for USB 1.x
> support.
Never mind, it seems Warn
On Thu, 2003-06-12 at 08:14, Anthony Naggs wrote:
> Sorry, I don't understand this comment. All OHCI, UHCI & EHCI USB
> controllers need PCI bus mastering in order to read & update their
> various lists of pending & completed transfers.
That was speculation on my part as to why bus mastering was
On Thu, 2003-06-12 at 03:10, John-Mark Gurney wrote:
> Craig Boston wrote this message on Wed, Jun 11, 2003 at 22:44 -0500:
> Hey, thanks for the great work. This got me past the same problem on
> the sparc box I have...
Don't look at me -- thank Warner for all his hard work on C
Cut-and-paste of the patch since the attachment disappeared... Probably won't
apply cleanly because of tabs.
--- ohci_pci.c.orig 2003-06-11 22:32:42.0 -0500
+++ ohci_pci.c 2003-06-11 22:01:43.0 -0500
@@ -173,6 +173,8 @@
/* XXX where does it say so in the spec? */
On Wednesday 11 June 2003 07:21 pm, Bernd Walter wrote:
> On Wed, Jun 11, 2003 at 11:45:38PM +0100, Josef Karthauser wrote:
> > The detach code could be made to work fairly easily. It's mostly there
> > I believe, but disabled. Nick couldn't convince himself that all the
> > used memory was being
Believe it or not, after futzing with the debugger for hours, reading the OHCI
spec, and trying to figure out why writing to the control registers works
exactly as it should but the card seems to ignore the ED list, I decided to
try something completely crazy and put the line
pci_enable_busmast
On Wed, 2003-06-11 at 19:37, Bernd Walter wrote:
> There are known problems with USB2.0 cardbus cards.
> We have some kind of resource problem - Warner already wrote something
> about it some time ago.
Ah, thanks. Any hints on where to find it? I tried adding his name to
my archive/google search
On Wed, 2003-06-11 at 17:08, Alistair Sutton wrote:
> [snip dmesg]
> > cardbus1: at device 0.2 (no driver attached)
> >
> > That output seems a little funny, between the "Resource not specified in
> > CIS" and claiming there is no driver attached right after it attaches
> > ohci...
>
> Only the U
I recently purchased a generic CompUSA branded CardBus USB 2.0
controller for a challenge to try to get it to work under FreeBSD ;) It
appears to use an NEC chip -- one that I've seen reports of the PCI
version working -- so at least some of the support for it is already
there. I'm willing to tak
On Mon, 2003-05-26 at 17:51, Mike Makonnen wrote:
> Most major locking work in libthr is finished. I believe it is stable enough now
> that it can be used for most applications[1]. I would appreciate it if people
> would try it out and report any bugs.
Just installed a freshly cvsup-ped current an
I was trying some network diagnostics yesterday and needed to generate a
continuous stream of small packets going across a few routers. So I
used ifconfig to set my MTU to some very low values (100, 300, 500, and
a few others). I know there's probably a better way to accomplish that,
but couldn't
On a recently compiled current the sound from an Intel 82801BA
integrated sound chip seems to be accelerated (high pitched and too
fast). While it's amusing to listen to certain songs this way, I don't
think it should be the default mode of operation ;)
Relevant dmesg output:
pcm0: port 0xdc40-
On Wed, 2003-02-19 at 21:48, Terry Lambert wrote:
> Lars Eggert wrote:
> > Poul-Henning Kamp wrote:
> > > Fatal trap 12: page fault while in kernel mode
> >
> > FWIW, Craig Boston and me see the same panics (threads on -current:
> > "panic starting gn
On Wed, 2003-02-19 at 16:44, Lars Eggert wrote:
> #11 0xc0302ff8 in calltrap () at {standard input}:97
> #12 0xc02098a4 in namei (ndp=0x9e) at /usr/src/sys/kern/vfs_lookup.c:158
> #13 0xc021bcfc in vn_open_cred (ndp=0xeb3b1a44, flagp=0xeb3b1a0c, cmode=0,
> cred=0xc2195e80) at /usr/src/sys/kern
On Wed, 2003-02-19 at 15:12, Lars Eggert wrote:
> Poul-Henning Kamp wrote:
> > Fatal trap 12: page fault while in kernel mode
>
> FWIW, Craig Boston and me see the same panics (threads on -current:
> "panic starting gnome" and "VFS panic (possibly NFS-lock
FWIW, this looks nearly identical to the panic I reported last night in
the thread "VFS panic (possibly NFS locking related?)". I didn't manage
to catch the ddb trace and had to work postmortem with a crash dump and
gdb. But it looked just like here.
Lars: Do you by any chance have your home dir
Hi everyone,
Just cvsuped from RELENG_5_0 to CURRENT and now the system panics when I
try to log in to gnome. It's a different process every time, but it
seems to be things that use file locks (my home dir is NFS mounted).
NFS access by programs that don't acquire locks seems to work okay.
Here
I remember a couple of posts about this problem; but don't recall (and
am unable to find in the archives) if there was ever any resolution.
Anyway, this just started on a RELENG_5_0 box this morning -- been
working fine up until now. I noticed that /dev/dsp wasn't being cloned,
so I went about tr
On Sun, 2003-01-12 at 18:54, Greg 'groggy' Lehey wrote:
> I haven't done much with PCCARD on -CURRENT lately. Last time I
> tried, a couple of months ago, I got repeated freezes on the two 100
> Mb/s NICs I have. I've just built a kernel as of about 30 hours ago,
> and I find:
> 2. 3Com 3c905.
On a laptop running current, I have a problem using the su program
multiple times (nested).
I have two accounts, I'll call them "auser" and "buser". I use auser
for my everyday activities; it has no special privileges. buser is a
member of the wheel group. I don't make auser a member of wheel b
On Wed, 2002-12-11 at 13:45, Aaron D. Gifford wrote:
> Let me correct this to state that the full volume name was "raid5volume"
> and I just shortened it to save typing. This turns out to be important.
> Looking at newfs.c, it looks like the last letter of the special
> device is used to cho
Apparently the listserver ate my message for breakfast, resending.
Maybe too big? I'm only attaching the patch this time; the other files
are available on request.
-Forwarded Message-
From: Craig Boston <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: ACPI + Compaq
of testing and then submit to Matthew Dodd
for his review after code freeze is over.
Thanks!
Craig Boston
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
of testing and then submit to Matthew Dodd
for his review after code freeze is over.
Thanks!
Craig Boston
Index: if_ex.c
===
RCS file: /home/ncvs/src/sys/dev/ex/if_ex.c,v
retrieving revision 1.39
diff -u -r1.39 if_ex.c
--- if
> Hello!
> Can 5.x properly cross-buildworld a 4.x source tree?
I've tried this once when downgrading a not-so-stable -CURRENT (SMP) box to
a hopefully-more-stable -STABLE box. I remember running into problems with
gcc 3.x failing to compile gcc 2.95 and some C++ related things. I ended up
unpa
Dag-Erling Smorgrav said:
> I have, somewhere in my big bag of tricks, an unfinished patch which
> would allow us to implement negative sleep times by directing the PSU
> to emit positrons instead of electrons for the required period of
> time, thereby causing the system to run backward in time.
I
ugh a pipe and wants to keep tabs on the download
progress. Modifying fetch seemed to be the simplest and most
straightforward of all my options; rather than requiring wget or
re-implementing some of make's logic.
Hopefully this will be useful to someone in a similar situation.
Craig Boston
>In this day of larger disk drives, I've modified
> the code in sysinstall to automatically create a /home
> partition and increase the rest of the sizes if the
> size of the disk (or slice) exceeds a given size (currently
> 58gig in my patch). For example, using A(uto in the label
> editor on
CC: -current since that's what I'm using, but keeping -stable as this
was just MFC'd.
On Mon, 2002-08-12 at 19:13, Bryan Liesner wrote:
>
> I would like to try the uvisor/ucom stuff just comitted, but don't have
> a clue how to use it... Can you point me in the right direction?
Has anyone ma
Seth Hettich wrote:
>I'd be interested to know if any other -current users with a
>G200 AGP are having problems.
>
Not a G200, but I have a G400 AGP in my system along with a 3DLabs
Permedia 2 (PCI, glint driver) and a NVidia Riva 128 (PCI, nv). This is
on a -current system supped right before
Kyle Butt said:
>To upgrade from 4.x-stable to current
>-
snip
>reboot in single user [3]
>Did you do this? IIRC, Sig 12 is unimplemented syscall, which would occur
>when userland and the kernel are out of sync.
I don't recall seeing this in any of t
Crist J. Clark wrote:
> These are actually very different in that they are set{u,g}id commands
> (well, ps(1) is not set{u,g}id anymore and is root:wheel owned). The
> sniffing tools we've been discussing, and pretty much all of the ones
> I've used, tcpdump(1), snort(8), nmap(1), etc., are not.
Not really on any topic at all, so please ignore this message if you've got
better things to do, but I just wanted to express my admiration of the
hard-working developers and contributers of the FreeBSD project.
I've mentioned my annoying workstation of weirdness (the one with the
tricked up vinu
49 matches
Mail list logo
