Trying to mount a cdrom from my XP box using
mount_smbfs //jason@desktop/cdrom /cdrom
Causes my machine to panic and die. Below is hopefully some info that
will help resolve the problem
Included as an attachment in plain text format the boot sequence showing
my hardware. The motherboard i
On Tue, 2002-04-16 at 13:43, Daniel Eischen wrote:
> On 16 Apr 2002, Benno Rice wrote:
> > On Tue, 2002-04-16 at 10:07, Dan Eischen wrote:
> > > Fresh cvsup and buildworld from today's -current seems to have
> > > broken pam logins for telnet and ssh. Fresh mergemaster too.
> >
> > [snip]
> >
>
On 16 Apr 2002, Benno Rice wrote:
> On Tue, 2002-04-16 at 10:07, Dan Eischen wrote:
> > Fresh cvsup and buildworld from today's -current seems to have
> > broken pam logins for telnet and ssh. Fresh mergemaster too.
>
> [snip]
>
> > Any clues?
>
> Remove -DYP from the CFLAGS in /usr/lib/libpam
On Tue, 2002-04-16 at 10:07, Dan Eischen wrote:
> Fresh cvsup and buildworld from today's -current seems to have
> broken pam logins for telnet and ssh. Fresh mergemaster too.
[snip]
> Any clues?
Remove -DYP from the CFLAGS in /usr/lib/libpam/modules/pam_unix/Makefile
and rebuild/reinstall lib
On Mon, 15 Apr 2002, Maksim Yevmenkin wrote:
>
> > Folks,
> >
> > [probably should be cc'd to -mobile as well]
> >
> > An engineering release of Bluetooth stack for -current FreeBSD
> > is available for download at
> >
> > http://www.geocitie
Fresh cvsup and buildworld from today's -current seems to have
broken pam logins for telnet and ssh. Fresh mergemaster too.
Apr 15 19:59:14 rigel telnetd[285]: in openpam_load_module(): no pam_unix.so found
Apr 15 19:59:14 rigel telnetd[285]: in openpam_load_module(): no pam_unix.so found
Apr
On Mon, Apr 15, 2002 at 03:25:12PM -0700, David O'Brien wrote:
> I have requested of both the XFree86-4 Server and of Portmgr to make the
> default mouse device /dev/sysmouse. But my emails have gone unanswered.
They did not go unanswered. I said it was a good idea and that I
would do it, but d
At 04:30 PM 4/15/2002 +0100, you wrote:
>--- John Angelmo <[EMAIL PROTECTED]> wrote:
> > I wonder how the pcm sound support is in 5.0?
>
>Hmm, I am using the emu10k1 aka Sound Blaster 1024 Live!, which has some
>locking problems, but apart from that I dont think there is any other
>problems AFAIK
>Date: Mon, 15 Apr 2002 15:47:32 -0700 (PDT)
>From: David Wolfskill <[EMAIL PROTECTED]>
>Have had a touch more turbulence than usual in -CURRENT-land today.
>Finally got it built; re-booted, and got the following panic while
>setting up an md-resident file system (for /tmp):
[Panic stuff elided
Matthias Schuendehuette wrote:
> I still have an old FreeBSD Test-Installation (45GB are big enough :-)
> with a 4.4-STABLE as of Okt 23, 2001...
>
> It boots off the DTLA, uses tagged-queuing and connects using UDMA100...
> ... and doesn't have any problems!!
>
> So, to bring some of you down t
On Mon, 15 Apr 2002, Maksim Yevmenkin wrote:
> Folks,
>
> [probably should be cc'd to -mobile as well]
>
> An engineering release of Bluetooth stack for -current FreeBSD
> is available for download at
>
> http://www.geocities.com/m_evmenkin/ngbt-fbsd-20020415.tar.
Have had a touch more turbulence than usual in -CURRENT-land today.
Finally got it built; re-booted, and got the following panic while
setting up an md-resident file system (for /tmp):
...
add net default: gateway 172.16.8.1
Additional routing options:.
Routing daemons:.
Additional daemons: sysl
On Mon, Apr 15, 2002 at 10:02:33AM +0200, John Angelmo wrote:
> When I start XFree86 I get the error that /dev/mouse can't be found, OK
> devfs seems to be installd so MAKEDEV dosn't exist anymore, is there
> anyway to get /dev/mouse working as in FreeBSD 4?
I have requested of both the XFree86
On Mon, Apr 15, 2002 at 04:08:43PM -0500, Patrick Hartling wrote:
> Bernd,
> This sounds very promising, but I want to make sure I do this
> correctly. When you say to remove the plexes, that means to use 'vinum rm'
> with appropriate options, correct? As far as reconfiguring, can I
On Sat, 13 Apr 2002, Clive Lin wrote:
> Hi, sort and gperf was not installed after make world.
>
> I think sort is easy to deal with, but I have no idea about gperf. Does
> this intend to be ? (On regular i386 platform, of course)
> ...
> gperf: (Only gperf.info.gz installed !?)
> /usr/src/gnu/us
Bernd,
This sounds very promising, but I want to make sure I do this correctly.
When you say to remove the plexes, that means to use 'vinum rm' with
appropriate options, correct? As far as reconfiguring, can I use the
output from 'vinum printconfig' as the input configuration file?
Folks,
[probably should be cc'd to -mobile as well]
An engineering release of Bluetooth stack for -current FreeBSD
is available for download at
http://www.geocities.com/m_evmenkin/ngbt-fbsd-20020415.tar.gz
i'm interested to hear from people who familiar with FreeBSD
kernel, Netgr
I'm very sorry if I will be a bit unpolite, but I have to mail the
following statement concerning the DTLA-Disks and FreeBSD:
It may be all true and horrible, but -
I still have an old FreeBSD Test-Installation (45GB are big enough :-)
with a 4.4-STABLE as of Okt 23, 2001...
It boots off the
On Mon, Apr 15, 2002 at 21:57 +0900, Makoto Matsushita wrote:
>
> But unfortunately, my kernel.debug prints
>
> uhub0: device problem, disabling port 2
>
> and doesn't panic :-(
Oh, how I know this message ... :)
Does http://www.FreeBSD.org/cgi/query-pr.cgi?pr=33004 help you
here? It h
On Mon, Apr 15, 2002 at 12:35:46PM -0500, Will Andrews wrote:
> On Mon, Apr 15, 2002 at 11:11:36AM +0200, Nick Hibma wrote:
> > device_set_ivars is always called (in usbd_probe_and_attach) with as an
> > argument a stack variable. Also, the ivar is not stored or anything in
> > the if_aue.c driver
On Mon, Apr 15, 2002 at 11:11:36AM +0200, Nick Hibma wrote:
> device_set_ivars is always called (in usbd_probe_and_attach) with as an
> argument a stack variable. Also, the ivar is not stored or anything in
> the if_aue.c driver. So this problem sounds like a problem in revisions
> of various file
Hiten Pandya wrote:
> --- John Angelmo <[EMAIL PROTECTED]> wrote:
>
>>I wonder how the pcm sound support is in 5.0?
>
>
> Hmm, I am using the emu10k1 aka Sound Blaster 1024 Live!, which has some
> locking problems, but apart from that I dont think there is any other
> problems AFAIK. :)
>
>
>
Giorgos Keramidas wrote:
> On 2002-04-14 23:46, Terry Lambert wrote:
> > Is your drive perchance an IBM DTLA?
> > It's known to have these problems.
>
> Nay. A Western Digital disk I bought about 2.5 years ago.
Well that shoots that idea down.
Try hacking the code to limit it to 3/4ths the num
On Mon, 15 Apr 2002, M. Warner Losh wrote:
:In message: <[EMAIL PROTECTED]>
:Dag-Erling Smorgrav <[EMAIL PROTECTED]> writes:
:: Check that your Makefile.inc1 is up to date.
:
:ah, looks like I didn't. Will update and try again.
:
--
Andrew R. Reiter
[EMAIL PROTECTED]
[EMAIL PROTECTE
--- John Angelmo <[EMAIL PROTECTED]> wrote:
> I wonder how the pcm sound support is in 5.0?
Hmm, I am using the emu10k1 aka Sound Blaster 1024 Live!, which has some
locking problems, but apart from that I dont think there is any other
problems AFAIK. :)
> I didn't get it working in 4.5 but perh
In message: <[EMAIL PROTECTED]>
Dag-Erling Smorgrav <[EMAIL PROTECTED]> writes:
: Check that your Makefile.inc1 is up to date.
ah, looks like I didn't. Will update and try again.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of
"M. Warner Losh" <[EMAIL PROTECTED]> writes:
> make: don't know how to make /usr/obj/home/imp/FreeBSD/src/i386/usr/lib/libypcln
Check that your Makefile.inc1 is up to date.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-c
===> libpam/modules/pam_unix
cc -fpic -DPIC -O -pipe -DYP -I.
-I/home/imp/FreeBSD/src/lib/libpam/modules/pam_unix/../../../../usr.sbin/vipw
-I/home/imp/FreeBSD/src/lib/libpam/modules/pam_unix/../../../../usr.bin/chpass
-I/home/imp/FreeBSD/src/lib/libpam/modules/pam_unix/../../../../li
On 2002-04-15 15:56, S&psgr;ren Schmidt wrote:
> It seems Giorgos Keramidas wrote:
> > On 2002-04-14 23:46, Terry Lambert wrote:
> > > Is your drive perchance an IBM DTLA?
> > > It's known to have these problems.
> >
> > Nay. A Western Digital disk I bought about 2.5 years ago.
>
> Hmm, AFAIK WD
I wonder how the pcm sound support is in 5.0?
I didn't get it working in 4.5 but perhaps theres better support in 5.0
but I didn't find any info in NOTES
/John
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Hiten Pandya wrote:
> --- Gary Stanley <[EMAIL PROTECTED]> wrote:
>
>>Sysinstall - post configure and re-do your mouse. The only workaround I
>>have found.
>
>
> The other way, is to edit your XF86Config to point to
> /dev/pcm0 (if you are using a PS2 mouse), or /dev/sioN (N being the COM por
--- Gary Stanley <[EMAIL PROTECTED]> wrote:
> Sysinstall - post configure and re-do your mouse. The only workaround I
> have found.
The other way, is to edit your XF86Config to point to
/dev/pcm0 (if you are using a PS2 mouse), or /dev/sioN (N being the COM port
number), which gives XFree86 dir
--- Alexander Leidinger <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I've got a lot of LINT compiled with icc. If someone feels
> adventuresomely he may grab
> http://www.leidinger.net/FreeBSD/icc_20020415.diff, apply it, and do a
FYI, You need to rename your online patch from icc_2020415.diff to
icc_
I had this similiar problem.
Sysinstall - post configure and re-do your mouse. The only workaround I
have found.
/ges
At 10:02 AM 4/15/2002 +0200, John Angelmo wrote:
>Hello
>
>When I start XFree86 I get the error that /dev/mouse can't be found, OK
>devfs seems to be installd so MAKEDEV dosn'
Hi,
I've got a lot of LINT compiled with icc. If someone feels
adventuresomely he may grab
http://www.leidinger.net/FreeBSD/icc_20020415.diff, apply it, and do a
cd /sys/i386/compile/
make clean && make depend
make -i CWARNFLAGS="" NO_WARNS="YES" USE_ICC="YES"
I'm interested in everything
It seems Giorgos Keramidas wrote:
> On 2002-04-14 23:46, Terry Lambert wrote:
> > Is your drive perchance an IBM DTLA?
> > It's known to have these problems.
>
> Nay. A Western Digital disk I bought about 2.5 years ago.
Hmm, AFAIK WD newer had a disk that worked right with tags,
and I've newer
On 15 Apr, Giorgos Keramidas wrote:
>> Is your drive perchance an IBM DTLA?
>> It's known to have these problems.
>
> Nay. A Western Digital disk I bought about 2.5 years ago.
And it does tagged queing? I thought IBM is the only manufacturer of
such IDE drives...
Bye,
Alexander.
--
Good afternoon
After upgrading FREEBSD to version 4.5 STABLE can't make any port.
Always it's stoped with error:
Error: your port uses an old layout. Please update it to match this
bsd.port.mk
. If you have updated your ports collection via cvsup and are still
getting thi
s error, see Q12 and Q
On 2002-04-14 23:46, Terry Lambert wrote:
> Is your drive perchance an IBM DTLA?
> It's known to have these problems.
Nay. A Western Digital disk I bought about 2.5 years ago.
G.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Le 2002-04-15, Edwin Culp écrivait :
> This could already be fixed but if not, mine broke at:
It is fixed in Makefile.inc1 rev. 1.256.
--
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
This could already be fixed but if not, mine broke at:
/lib/libpam/modules/pam_unix/../../../../contrib/openpam/include
-I/usr/src/lib/libpam/modules/pam_unix/../../libpam -Werror -Wall -W
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type
-Wcast-qual -Wwrite-strings -Wswitch
On 15 Apr, Søren Schmidt wrote:
> Again that has *nothing* to do with the DTLA drives and DMA speed
> and the phase of the moon...
But perhaps it depends on the distance between the drive and the
nordpole... the ones with the problems are all more far away from it
than you... ;-)
> But it shows
On 15 Apr, Terry Lambert wrote:
> Obviously, turning off tagged commands works, according to at least
> one person who is reporting the problem.
It helps every one I know of.
[...]
> Limiting the outstanding tagged commands to less than the advertised
> amount would actually be my first choice
It seems Terry Lambert wrote:
> "Søren Schmidt" wrote:
> > > For a more "scientific test", downloading the firmware tool and
> > > setting the DMA transfer rate down, and checking for problems,
> > > would be pretty overwhelming evidence. Personally, I don't have
> > > any of the buggers lying ar
jhb> Can you get a backtrace in ddb? It looks like a null pointer
jhb> dereference, and knowing where it happened would help.
Backtrace told me that the panic was occured when
usbd_get_interface_descriptor() is called from aue_attach().
jhb> Finding the file and line of the instruction pointer
"Søren Schmidt" wrote:
> > For a more "scientific test", downloading the firmware tool and
> > setting the DMA transfer rate down, and checking for problems,
> > would be pretty overwhelming evidence. Personally, I don't have
> > any of the buggers lying around to test with any more.
>
> Why on
The models with lines looking like:
ad0: 19073MB [38752/16/63] at ata0-master UDMA100
are of the 60GXP range, the DTLA model numbers indicate the 75GXP range, one
of which has already died on me personally.
hth
Andrew
- Original Message -
From: "Terry Lambert" <[EMAIL PROTECTED]>
To: "
It seems Terry Lambert wrote:
> > > IBM DTLA drives are known to be problematic. If you use that
> > > in a search engine, it will find numerous references to the
> > > drive electronics being too slow for sustained access to the
> > > sectors closes to the spindle.
> >
> > This thread is about
"Søren Schmidt" wrote:
> > Is your drive perchance an IBM DTLA?
> >
> > It's known to have these problems.
>
> Cool! would you like to share where that information is available so
> I can possibly work around the problem ??
IBM DTLA drives are known to be problematic. If you use that
in a searc
"Søren Schmidt" wrote:
> It seems Terry Lambert wrote:
> > "Søren Schmidt" wrote:
> > > > Is your drive perchance an IBM DTLA?
> > > >
> > > > It's known to have these problems.
> > >
> > > Cool! would you like to share where that information is available so
> > > I can possibly work around the pr
It seems Terry Lambert wrote:
> "Søren Schmidt" wrote:
> > > Is your drive perchance an IBM DTLA?
> > >
> > > It's known to have these problems.
> >
> > Cool! would you like to share where that information is available so
> > I can possibly work around the problem ??
>
> IBM DTLA drives are know
Alexander Leidinger wrote:
> >> >> Some people see this after the "mega" MFC on -stable too.
> >> > Could I have you guys try this simple patch ?
> >> Does not work.
> > No change or breaks completely (if so how)...
> Sorry: "No change".
Download the Windows executable I pointed to in a previous
Alexander Leidinger wrote:
> On 14 Apr, Terry Lambert wrote:
> > Is your drive perchance an IBM DTLA?
> >
> > It's known to have these problems.
>
> Does this also apply to other IBM drives?
Potentially. IBM renamed the part number when the drives got
known to be dogs. I thought they also defa
Whats about editing
/etc/rc.devfs
and inserting a symlink from /dev/mouse to /dev/sysmouse ?
On Mon, 2002-04-15 at 08:26, Munish Chopra wrote:
> On Mon, Apr 15, 2002 at 10:02:33AM +0200, John Angelmo wrote:
> > Hello
> >
> > When I start XFree86 I get the error that /dev/mouse can't be found,
device_set_ivars is always called (in usbd_probe_and_attach) with as an
argument a stack variable. Also, the ivar is not stored or anything in
the if_aue.c driver. So this problem sounds like a problem in revisions
of various files.
Please check that your kernel modules kernel are in sync. Do th
On 15 Apr, =?x-unknown?Q?S=F8ren?= Schmidt wrote:
>> >> Some people see this after the "mega" MFC on -stable too.
>> >
>> > Could I have you guys try this simple patch ?
>>
>> Does not work.
>
> As in:
>
> No change or breaks completely (if so how)...
Sorry: "No change".
Bye,
Alexander.
-
It seems Alexander Leidinger wrote:
> On 15 Apr, Søren Schmidt wrote:
>
> >> Some people see this after the "mega" MFC on -stable too.
> >
> > Could I have you guys try this simple patch ?
>
> Does not work.
As in:
No change or breaks completely (if so how)...
-Søren
To Unsubscribe: send m
On 15 Apr, Søren Schmidt wrote:
>> Some people see this after the "mega" MFC on -stable too.
>
> Could I have you guys try this simple patch ?
Does not work.
Bye,
Alexander.
--
Actually, Microsoft is sort of a mixture between the Borg and the Ferengi.
http://www.Leidinger.net
On Mon, Apr 15, 2002 at 10:02:33AM +0200, John Angelmo wrote:
> Hello
>
> When I start XFree86 I get the error that /dev/mouse can't be found, OK
> devfs seems to be installd so MAKEDEV dosn't exist anymore, is there
> anyway to get /dev/mouse working as in FreeBSD 4?
>
> Thanks
>
> /John
Se
On 15 Apr, =?x-unknown?Q?S=F8ren?= Schmidt wrote:
>> Some people see this after the "mega" MFC on -stable too.
>
> Could I have you guys try this simple patch ?
It failed to apply, applied it by hand. Compiling a new kernel now.
Bye,
Alexander.
--
Where do you think you're
On 14 Apr, Terry Lambert wrote:
>> > Turn off tagged queing. S?ren knows about this error and tries to
>> > reproduce it (but fails as far as I know).
>>
>> I've seen this quite a few times, but I can't reliably reproduce it
>> yet. It seems to hit me a lot when the ad0 drive spins like crazy
>
It seems Alexander Leidinger wrote:
> > I've seen this quite a few times, but I can't reliably reproduce it
> > yet. It seems to hit me a lot when the ad0 drive spins like crazy
> > doing stuff that is heavy on disk I/O. Disabling tag queueing now to
> > see if this fixes things. But even if it
Hello
When I start XFree86 I get the error that /dev/mouse can't be found, OK
devfs seems to be installd so MAKEDEV dosn't exist anymore, is there
anyway to get /dev/mouse working as in FreeBSD 4?
Thanks
/John
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current"
On 15 Apr, Giorgos Keramidas wrote:
>> > I updated to -current today and am now getting these errors
>> >
>> > ad0: READ command timeout tag=1 serv=1 - resetting
>> > ata0: resetting devices .. ad0: invalidating queued requests
>> > done
>>
>> Turn off tagged queing. S?ren knows about this error
It seems Terry Lambert wrote:
> Giorgos Keramidas wrote:
> > > > ad0: READ command timeout tag=1 serv=1 - resetting
> > > > ata0: resetting devices .. ad0: invalidating queued requests
> > > > done
> > >
> > > Turn off tagged queing. S?ren knows about this error and tries to
> > > reproduce it (bu
65 matches
Mail list logo
