Anish Mistry wrote:
> I've been using -CURRENT for while now and have finally gotten some time to
> come up with a list of problems I'm getting:
> When I su to change to the root user I get a "Bus Error" from su. This have
> been around for about a month, still happens after multiple build and ins
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've been using -CURRENT for while now and have finally gotten some time to
come up with a list of problems I'm getting:
When I su to change to the root user I get a "Bus Error" from su. This have
been around for about a month, still happens after m
> From: Orion Hodson <[EMAIL PROTECTED]>
> Date: Fri, 28 Mar 2003 17:21:45 -0800
> Sender: [EMAIL PROTECTED]
>
>
> Kevin Oberman writes:
> | More information on my AC97 experiences:
> |
> | I forced the card to 4.8 KHz which is what it was running at on V4. This
> | seems to have not helped the p
Kevin Oberman writes:
| More information on my AC97 experiences:
|
| I forced the card to 4.8 KHz which is what it was running at on V4. This
| seems to have not helped the performance of GnomeMeeting at all. The
| sound I hear is in "spurts" which are at the correct frequency and last
| about a t
More information on my AC97 experiences:
I forced the card to 4.8 KHz which is what it was running at on V4. This
seems to have not helped the performance of GnomeMeeting at all. The
sound I hear is in "spurts" which are at the correct frequency and last
about a tenth of a second. with gaps betwee
> Date: Wed, 26 Mar 2003 22:43:17 -0700
> From: Scott Long <[EMAIL PROTECTED]>
>
> Orion Hodson wrote:
> > Kevin Oberman writes:
> > |
> > | After upgrading my laptop from STABLE to CURRENT on 3/14 I have been
> > | having problems with GnomeMeeting. Often the sound is badly broken with
> > | 'spu
--- John Hay <[EMAIL PROTECTED]> wrote:
> >
> > | > There is a calibration step in the driver to
> determine the clock rate of th
> > | e
> > | > AC97 link. What you are seeing is the
> calibration step failing and setting
> > | a
> > | > bogus ac97 link rate. I took a cursory look a
> coupl
>
> | > There is a calibration step in the driver to determine the clock rate of th
> | e
> | > AC97 link. What you are seeing is the calibration step failing and setting
> | a
> | > bogus ac97 link rate. I took a cursory look a couple of weeks back and it
> | > smelt like the timecounter in
/-- Scott Long wrote:
| Orion Hodson wrote:
| > There is a calibration step in the driver to determine the clock rate of th
| e
| > AC97 link. What you are seeing is the calibration step failing and setting
| a
| > bogus ac97 link rate. I took a cursory look a couple of weeks back and it
| >
Orion Hodson wrote:
Kevin Oberman writes:
|
| After upgrading my laptop from STABLE to CURRENT on 3/14 I have been
| having problems with GnomeMeeting. Often the sound is badly broken with
| 'spurts' of sound with silent gaps in between. This was never the case
| with STABLE. Other times it's fine.
Kevin Oberman writes:
|
| After upgrading my laptop from STABLE to CURRENT on 3/14 I have been
| having problems with GnomeMeeting. Often the sound is badly broken with
| 'spurts' of sound with silent gaps in between. This was never the case
| with STABLE. Other times it's fine.
|
| When I looked
After upgrading my laptop from STABLE to CURRENT on 3/14 I have been
having problems with GnomeMeeting. Often the sound is badly broken with
'spurts' of sound with silent gaps in between. This was never the case
with STABLE. Other times it's fine.
When I looked at my dmesg output I noticed some ch
> Since it works with 4.7-STABLE it must(?) be a current problem
> more than a XFree86 problem. Or?
I had the same problem -- something to do with files left
over from the original 4.7 installation. Cured by
deinstalling XFree86-* ports, renaming /usr/X11R6 to
something else (in case something wa
Resending due to the fact that I didn' include the
/var/log/XFree86.0.log
I have a Compaq Evo N800c witch runs with 4.7-STABLE and
XFree86 with no problems. The exact same configuration for
X and same version of XFree86-libs etc does not run on
Current a few days old. The problems started a few we
On Mon, Feb 10, 2003 at 11:20:24AM +0100, Gunnar Flygt wrote:
> Since it works with 4.7-STABLE it must(?) be a current problem
> more than a XFree86 problem. Or?
>
> Any suggestions?
>
> --
> Gunnar Flygt, SR
Could you paste your /var/log/XFree86*.log with the error parts? Maybe some will be
ab
Am I the only person having problems with a laptop with
Current and XFree86?
I have a Compaq Evo N800c witch runs with 4.7-STABLE and
XFree86 with no problems. The exact same configuration for
X and same version of XFree86-libs etc does not run on
Current a few days old. The problems started a few
On Wed, Jan 22, 2003 at 12:49:04AM -0600, Chip Norkus wrote:
> But try disabling ACPI and see if your PS/2 mouse suddenly works. ;)
As you can see from my first post
>> Same part of newer -CURRENT (I have disable ACPI, but I get same
>> result with ACPI too):
>> atkbdc0: at port 0x64,0x60 on isa
On Wed Jan 22, 2003; 09:38AM +0300 Igor Roboul propagated the following:
> On Fri, Jan 17, 2003 at 04:27:36PM +0300, Igor Roboul wrote:
> > Hello,
> > does anybody have problems with PS/2 mouse attached to PC with recent
> > -CURRENT?
> >
> > Motherboard: MSI MS6337LE5 (i815 chipset)
> > Mouse: Ge
On Fri, Jan 17, 2003 at 04:27:36PM +0300, Igor Roboul wrote:
> Hello,
> does anybody have problems with PS/2 mouse attached to PC with recent
> -CURRENT?
>
> Motherboard: MSI MS6337LE5 (i815 chipset)
> Mouse: Genius NetScroll+
Can't belive that this promlem is specific to exUSSR :-) But who knows?
On Fri, Jan 17, 2003 at 04:27:36PM +0300, Igor Roboul wrote:
> Hello,
> does anybody have problems with PS/2 mouse attached to PC with recent
> -CURRENT?
>
> Mouse is recognized by kernel and moused, but cursor is moving VERY
> slow, no visible reaction to buttons etc. This happens in text mode
>
Hello,
does anybody have problems with PS/2 mouse attached to PC with recent
-CURRENT?
Mouse is recognized by kernel and moused, but cursor is moving VERY
slow, no visible reaction to buttons etc. This happens in text mode
and in X11. When in X11, it happens when
Option "Device" "/dev/sysmou
On Tue, Aug 21, 2001 at 05:42:55PM -0500, Jim Bryant wrote:
>
>
> Kris Kennaway wrote:
>
> >On Mon, Aug 20, 2001 at 11:52:07AM +0100, Josef Karthauser wrote:
> >
> >>I'm having strange problems with -current on a laptop with 64mb of
> >&g
Kris Kennaway wrote:
> On Mon, Aug 20, 2001 at 11:52:07AM +0100, Josef Karthauser wrote:
>
>>I'm having strange problems with -current on a laptop with 64mb of
>>memory. Periodically "things go strange" [tm].
>>
>>Because of the lack of memory I&#
On Tue, Aug 21, 2001 at 12:54:35PM -0700, Kris Kennaway wrote:
> On Mon, Aug 20, 2001 at 11:52:07AM +0100, Josef Karthauser wrote:
> > I'm having strange problems with -current on a laptop with 64mb of
> > memory. Periodically "things go strange" [tm].
> >
&
On Mon, Aug 20, 2001 at 11:52:07AM +0100, Josef Karthauser wrote:
> I'm having strange problems with -current on a laptop with 64mb of
> memory. Periodically "things go strange" [tm].
>
> Because of the lack of memory I'm using a fair amount of swap.
>
&g
I'm having strange problems with -current on a laptop with 64mb of
memory. Periodically "things go strange" [tm].
Because of the lack of memory I'm using a fair amount of swap.
Everything runs smoothly up until a point, which seems to depend upon
not running too many lar
dent Computer Professionals
Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795
Web: http://www.aims.com.au
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of
> Matthew Schlegel
> Sent: Saturday, 14 April 2001 4:05
> To: [EMAIL PROT
On 13-Apr-01 Matthew Schlegel wrote:
> I have been working on doing an update to the latest -CURRENT (last cvsup for
> this upgrade attempt was this morning at about 9:30 PDT) for the last
> couple days from :
> FreeBSD msops.crossgain.com 5.0-CURRENT FreeBSD 5.0-CURRENT
>#0: Wed Jun 28 13:23:44
I have been working on doing an update to the latest -CURRENT (last cvsup for
this upgrade attempt was this morning at about 9:30 PDT) for the last
couple days from :
FreeBSD msops.crossgain.com 5.0-CURRENT FreeBSD 5.0-CURRENT
#0: Wed Jun 28 13:23:44 PDT 2000
Right now I can boot into single user
[Dell XPS B800 w/ 3c905C-TX and Aureal Vortex 8830 soundcard]
I tried to upgrade my -current today. It had been running a -current
from Aug 14. However, neither my NIC (xl0) nor my soundcard (pcm0)
were detected on boot. All the relevant drivers are compiled into the
kernel, but the PCI code se
> Tried to install the snapshot, but it hangs at Probing devices.
> ALT-F2 shows as last entry:
>
> DEBUG: Found a disk device named mlxd0
>
> Verbose boot seems not to show more. System is still active, ALT-CONTROL-DEL
> will ask if you really want to stop the install.
>
> System is an AMD K7-
On Thu, Feb 24, 2000 at 08:31:30PM -0800, Ulf Zimmermann wrote:
> Tried to install the snapshot, but it hangs at Probing devices.
> ALT-F2 shows as last entry:
>
> DEBUG: Found a disk device named mlxd0
>
> Verbose boot seems not to show more. System is still active, ALT-CONTROL-DEL
> will ask i
Tried to install the snapshot, but it hangs at Probing devices.
ALT-F2 shows as last entry:
DEBUG: Found a disk device named mlxd0
Verbose boot seems not to show more. System is still active, ALT-CONTROL-DEL
will ask if you really want to stop the install.
System is an AMD K7-750, 256MB memory,
I just upgraded one of my linux boxes to FreeBSD 4.0-CURRENT since I can
kind of run the one application that was keeping me on linux (vmware).
Well I am having one hell of a time though. I use this box as a NAT box
for my local lan, and for some reason I am getting massive errors like
the follow
Arthur H. Johnson II
http://www.linuxberg.com
Linuxberg Manager
[EMAIL PROTECTED]
On Fri, 3 Sep 1999, Doug Rabson wrote:
> On Fri, 3 Sep 1999, Arthur H. Johnson II wrote:
>
> > Okay.
> >
> > Arthur H. Johnson II
> > http://www.linuxberg.com
> > Linuxberg Manager
> > [EMAIL PROTECTED]
>
> No
On Fri, 3 Sep 1999, Arthur H. Johnson II wrote:
> Okay.
>
> Arthur H. Johnson II
> http://www.linuxberg.com
> Linuxberg Manager
> [EMAIL PROTECTED]
Now I'm really confused. It looks like you have an explicit line for the
soundcard in your config (e.g. "device pcm0 at isa? port ? ...") but the
c
Okay.
Arthur H. Johnson II
http://www.linuxberg.com
Linuxberg Manager
[EMAIL PROTECTED]
On Fri, 3 Sep 1999, Doug Rabson wrote:
> On Fri, 3 Sep 1999, Arthur H. Johnson II wrote:
>
> > Well, I got rid of the old Voxware drivers and went with the pnp drivers
> > and still nothing. Here is the dm
On Fri, 3 Sep 1999, Arthur H. Johnson II wrote:
> Well, I got rid of the old Voxware drivers and went with the pnp drivers
> and still nothing. Here is the dmesg:
> --
> pcm0: at port 0x220-0x22f irq 5 drq 5 flags 0x15 on isa0
> unknown0: on isa0
> unknown1: at port 0x240-0x24f,0x300-0x301,0x
Well, i recompiled with the Voxware drivers and commented out the pnp0
device, and now it works.
Arthur H. Johnson II
http://www.linuxberg.com
Linuxberg Manager
[EMAIL PROTECTED]
On Fri, 3 Sep 1999, Mike Hoskins wrote:
> On Fri, 3 Sep 1999, Arthur H. Johnson II wrote:
>
> > That didnt work. W
On Fri, 3 Sep 1999, Arthur H. Johnson II wrote:
> That didnt work. When I ran mpg123 it said can't access /dev/dsp but the
> mixer worked. And yes, i did run makedev.
What are the permissions on /dev/dsp*? Are other deamons running that are
attempting to access /dev/dsp? As an example, I ran
That didnt work. When I ran mpg123 it said can't access /dev/dsp but the
mixer worked. And yes, i did run makedev.
Arthur H. Johnson II
http://www.linuxberg.com
Linuxberg Manager
[EMAIL PROTECTED]
On Fri, 3 Sep 1999, Sheldon Hearn wrote:
>
>
> On Fri, 03 Sep 1999 11:27:55 -0400, "Arthur H.
On Fri, 03 Sep 1999 11:27:55 -0400, "Arthur H. Johnson II" wrote:
> Well, I got rid of the old Voxware drivers and went with the pnp drivers
> and still nothing. Here is the dmesg:
What does "still nothing" mean? I can't see anything in your e-mail
message which indicates what you're doing to
Well, I got rid of the old Voxware drivers and went with the pnp drivers
and still nothing. Here is the dmesg:
--
Copyright (c) 1992-1999 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 4.0-CURRENT #
On Sun, 9 May 1999, Tomer Weller wrote:
> Nope.
Well, is root.o truncated or otherwise corrupted? Are you seeing any other
filesystem problems on this machine? Did you crash/reboot during the build?
Kris
> Maxim Sobolev wrote:
>
> > Tomer Weller wrote:
> >
> > > re -lXext -lqt -lX11 -lkdeui -
On Sun, May 9, 1999, Tomer Weller wrote:
> kdebase-1.1.1 port errors with :
> root.o: file not recognized: File truncated
Try doing:
make deinstall
make clean
make all
It looks like root.o may have been built with an older version
of egcs, or perhaps it was an a.out object file.
--
Chri
Nope.
Maxim Sobolev wrote:
> Tomer Weller wrote:
>
> > re -lXext -lqt -lX11 -lkdeui -lkdecore -lXext -lqt -lX11
> > root.o: file not recognized: File truncated
>
> Maybe you are building ports over NFS - some time ago NFS client code on
> -CURRENT was broken, however now it seems to be fixed.
Tomer Weller wrote:
> re -lXext -lqt -lX11 -lkdeui -lkdecore -lXext -lqt -lX11
> root.o: file not recognized: File truncated
Maybe you are building ports over NFS - some time ago NFS client code on
-CURRENT was broken, however now it seems to be fixed.
Sincerely,
Maxim
To Unsubscribe: send
i had problems with the old kdelibs packages(1.1), all the programs i compiled
couldn't link.
i think it's an EGCS issue, so i decided to compile the kdelibs (1.1.1) with
-current.
it compiled, but no KDE software worked (including kwm).
tried to go back to the old pkg, but got the same error,
On Thu, 6 May 1999, Scott Michel wrote:
> > % gdb foobar foobar.core
> > Register %s not found in core file.
>^^
> Should read:
>
> "Register eax not found in core file."
>
> Silly me... :-)
I'll look at it today - My head is in gdb mode at the moment after doing
the import.
--
Dou
> % gdb foobar foobar.core
> Register %s not found in core file.
^^
Should read:
"Register eax not found in core file."
Silly me... :-)
-scooter
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Current's gdb cannot read core files today (cvsup'd on Monday
and installed Monday). It reports:
% gdb foobar foobar.core
Register %s not found in core file.
%
The error emanates in gdb/gdb/core-aout.c. I was going to try
to diagnose the problem this weekend but unfortunately I have
USNR duty.
A
hello!
I have some critical problems with fbsd. When I try to boot with fbsd
install disk (boot.flp), my system is halt.
I tried different versions of fbsd from 2.2.8R and 3.0-STABLE till
4.0-CURRENT.
I have IBM server, model 8640ES0, with PPro 200, 128 MB RAM,
SCSII-adapter AIC-7880 (it was "modi
52 matches
Mail list logo
