RE: 5.2.1 to 6.2 Migration.

2007-11-04 Thread Chris Haulmark
 
 Kevin Kinsey [EMAIL PROTECTED] writes:
 
  Lowell Gilbert wrote:
  Chris Haulmark [EMAIL PROTECTED] writes:
 
  Grant Peel wrote:
 
  I thought I would ask the question before I do it the hard way
 
 
  1. Can FreeBSD be upgraded from 5.2.1 to 6.2 ?
 
  Yes.
 
  2. Can it be done through an ssh connection, or MUST I make the
 trip
  to the farm and do it from the console?
 
  I've done 5.x to 6.x upgrades via ssh.  It is possible.
 
  In the handbook, you will see mentions of booting into single user
 mode
  and I can tell you that it is not required.
 
  It's a good safety precaution; if your updated kernel won't boot,
 you
  will need to reinstall most of the system.

That is over the board.  

Only times that I have made the mistakes in the past are:

1.  Misconfiguring the kernel options such as disabling the
meeded network driver built in the kernel.
2.  Anything related to having kernel panics to occur.
3.  Enabling firewall and getting locked out via network.

 
  That sounds a tad alarmist; if the new kernel won't boot, you'll
  have to be at (or have someone at) the console who can boot
  kernel.old (I stand open for correction, but last time I did
  it, 'twas that way).  And, possibly, that person (you?) will
  also have to be able to do some other magic.

Magic such as having other remote possibilities.  DRAC access for
example.

 
  But the phrase reinstall most of the system doesn't, at
  the very least, *sound* like the BSD Way(tm).  Granted,
  sometimes it's quicker --- I know that's why it's used so
  often on that Other System  ;-)
 
 If you have reinstalled a userland that depends on a kernel that
 doesn't boot, you are quite likely to be in trouble.

I always do buildworld/installworld as part of my kernel build/installs.
That is to ensure staying in sync.

I reboot after the installworld then again after the installkernel.

 
 The BSD way does not necessarily involve easy recovery from making
 up procedures that haven't been worked out or tested by the release
 engineers.  In fact, I don't think any operating system guarantees
 that you will have an easy time after making up your own upgrade
 procedures.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 to 6.2 Migration.

2007-11-04 Thread Beech Rintoul
On Saturday 03 November 2007, Chris Haulmark said:
  Kevin Kinsey [EMAIL PROTECTED] writes:
   Lowell Gilbert wrote:
   Chris Haulmark [EMAIL PROTECTED] writes:
   Grant Peel wrote:
   I thought I would ask the question before I do it the hard
   way
 
  
 
   1. Can FreeBSD be upgraded from 5.2.1 to 6.2 ?
  
   Yes.
  
   2. Can it be done through an ssh connection, or MUST I make
   the
 
  trip
 
   to the farm and do it from the console?
  
   I've done 5.x to 6.x upgrades via ssh.  It is possible.
  
   In the handbook, you will see mentions of booting into single
   user
 
  mode
 
   and I can tell you that it is not required.
  
   It's a good safety precaution; if your updated kernel won't
   boot,
 
  you
 
   will need to reinstall most of the system.

 That is over the board.

 Only times that I have made the mistakes in the past are:

 1.  Misconfiguring the kernel options such as disabling the
 meeded network driver built in the kernel.
 2.  Anything related to having kernel panics to occur.
 3.  Enabling firewall and getting locked out via network.

   That sounds a tad alarmist; if the new kernel won't boot,
   you'll have to be at (or have someone at) the console who can
   boot kernel.old (I stand open for correction, but last time I
   did it, 'twas that way).  And, possibly, that person (you?)
   will also have to be able to do some other magic.

 Magic such as having other remote possibilities.  DRAC access for
 example.

   But the phrase reinstall most of the system doesn't, at
   the very least, *sound* like the BSD Way(tm).  Granted,
   sometimes it's quicker --- I know that's why it's used so
   often on that Other System  ;-)
 
  If you have reinstalled a userland that depends on a kernel that
  doesn't boot, you are quite likely to be in trouble.

 I always do buildworld/installworld as part of my kernel
 build/installs. That is to ensure staying in sync.

 I reboot after the installworld then again after the installkernel.

You should do it the other way around. That way if the new kernel 
doesn't boot you aren't stuck with an out of sync userland which may 
not play nicely with your old kernel. Also, depending on the changes 
booting an old kernel with a new userland may (and has) result in 
your system not booting at all.

The proper sequence is:

# make buildworld
# make buildkernel
# make installkernel
# reboot
# mergemaster -p
# make installworld
# mergemaster
# reboot



  The BSD way does not necessarily involve easy recovery from
  making up procedures that haven't been worked out or tested by
  the release engineers.  In fact, I don't think any operating
  system guarantees that you will have an easy time after making up
  your own upgrade procedures.

 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to
 [EMAIL PROTECTED]



-- 
---
Beech Rintoul - FreeBSD Developer - [EMAIL PROTECTED]
/\   ASCII Ribbon Campaign  | FreeBSD Since 4.x
\ / - NO HTML/RTF in e-mail   | http://www.freebsd.org
 X  - NO Word docs in e-mail | Latest Release:
/ \  - http://www.FreeBSD.org/releases/6.2R/announce.html
---



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: 5.2.1 to 6.2 Migration.

2007-11-04 Thread Chris Haulmark
But the phrase reinstall most of the system doesn't, at
the very least, *sound* like the BSD Way(tm).  Granted,
sometimes it's quicker --- I know that's why it's used so
often on that Other System  ;-)
  
   If you have reinstalled a userland that depends on a kernel that
   doesn't boot, you are quite likely to be in trouble.
 
  I always do buildworld/installworld as part of my kernel
  build/installs. That is to ensure staying in sync.
 
  I reboot after the installworld then again after the installkernel.
 
 You should do it the other way around. That way if the new kernel
 doesn't boot you aren't stuck with an out of sync userland which may
 not play nicely with your old kernel. Also, depending on the changes
 booting an old kernel with a new userland may (and has) result in
 your system not booting at all.
 
 The proper sequence is:
 
 # make buildworld
 # make buildkernel
 # make installkernel
 # reboot
 # mergemaster -p
 # make installworld
 # mergemaster
 # reboot

I prefer to do [build|install]world prior to building the kernel
with the new installed tools.

Even with an outsynced system, the most common tools to be affected
are ps and top.  Even when a kernel fails to boot all the
way through, you can still rebuild a new kernel after booting
with the old kernel.  Having the new system tools will not
hurt.

The OP's primary goal was to discuss about if it was possible
to upgrade 5.x to 6.x remotely via ssh.  I provided that it
was possible and what my method is.

Chris

 
 
 
   The BSD way does not necessarily involve easy recovery from
   making up procedures that haven't been worked out or tested by
   the release engineers.  In fact, I don't think any operating
   system guarantees that you will have an easy time after making up
   your own upgrade procedures.
 
  ___
  freebsd-questions@freebsd.org mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-questions
  To unsubscribe, send any mail to
  [EMAIL PROTECTED]
 
 
 
 --

---
 
 Beech Rintoul - FreeBSD Developer - [EMAIL PROTECTED]
 /\   ASCII Ribbon Campaign  | FreeBSD Since 4.x
 \ / - NO HTML/RTF in e-mail   | http://www.freebsd.org
  X  - NO Word docs in e-mail | Latest Release:
 / \  - http://www.FreeBSD.org/releases/6.2R/announce.html

---
 
 
 

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 to 6.2 Migration.

2007-11-04 Thread Olivier Nicole
 I prefer to do [build|install]world prior to building the kernel
 with the new installed tools.
 
 Even with an outsynced system, the most common tools to be affected
 are ps and top.  Even when a kernel fails to boot all the
 way through, you can still rebuild a new kernel after booting
 with the old kernel.  Having the new system tools will not
 hurt.

Am I wrong thinking that even when running an old system (kernel and
tools) for the buildkernel step, only new tools (/usr/src/...) are
being used?

Bests,

Olivier
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 to 6.2 Migration.

2007-11-03 Thread Derek Ragona

At 11:56 AM 11/3/2007, Grant Peel wrote:

Hi all,

I thought I would ask the question before I do it the hard way 

1. Can FreeBSD be upgraded from 5.2.1 to 6.2 ?

if so ...

2. Can it be done through an ssh connection, or MUST I make the trip to 
the farm and do it from the console?


-Grant


I did a source upgrade and rebuild from 5.1 to 6.1 remotely.  Read 
upgrading carefully after you pull down the new src though for any extra 
steps you might need to make.  However, also be prepared to make the trip 
should the upgrade go awry.


-Derek

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: 5.2.1 to 6.2 Migration.

2007-11-03 Thread Chris Haulmark

 
 Hi all,
 
 I thought I would ask the question before I do it the hard way 
 
 1. Can FreeBSD be upgraded from 5.2.1 to 6.2 ?

Yes.

 
 if so ...
 
 2. Can it be done through an ssh connection, or MUST I make the trip
to
 the
 farm and do it from the console?

I've done 5.x to 6.x upgrades via ssh.  It is possible.

In the handbook, you will see mentions of booting into single user mode
and I can tell you that it is not required.

Chris

 
 -Grant
 
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to freebsd-questions-
 [EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 to 6.2 Migration.

2007-11-03 Thread Lowell Gilbert
Chris Haulmark [EMAIL PROTECTED] writes:

 Grant Peel wrote:
 Hi all,
 
 I thought I would ask the question before I do it the hard way 
 
 1. Can FreeBSD be upgraded from 5.2.1 to 6.2 ?

 Yes.

 
 if so ...
 
 2. Can it be done through an ssh connection, or MUST I make the trip
 to
 the
 farm and do it from the console?

 I've done 5.x to 6.x upgrades via ssh.  It is possible.

 In the handbook, you will see mentions of booting into single user mode
 and I can tell you that it is not required.

It's a good safety precaution; if your updated kernel won't boot, you
will need to reinstall most of the system.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 to 6.2 Migration.

2007-11-03 Thread Kevin Kinsey

Lowell Gilbert wrote:

Chris Haulmark [EMAIL PROTECTED] writes:


Grant Peel wrote:



I thought I would ask the question before I do it the hard way 

1. Can FreeBSD be upgraded from 5.2.1 to 6.2 ?



Yes.



2. Can it be done through an ssh connection, or MUST I make the trip
to the farm and do it from the console?



I've done 5.x to 6.x upgrades via ssh.  It is possible.

In the handbook, you will see mentions of booting into single user mode
and I can tell you that it is not required.


It's a good safety precaution; if your updated kernel won't boot, you
will need to reinstall most of the system.


That sounds a tad alarmist; if the new kernel won't boot, you'll
have to be at (or have someone at) the console who can boot 
kernel.old (I stand open for correction, but last time I did

it, 'twas that way).  And, possibly, that person (you?) will
also have to be able to do some other magic.

But the phrase reinstall most of the system doesn't, at
the very least, *sound* like the BSD Way(tm).  Granted,
sometimes it's quicker --- I know that's why it's used so
often on that Other System  ;-)

Kevin Kinsey
--
Only through hard work and perseverance can one truly suffer.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 to 6.2 Migration.

2007-11-03 Thread Lowell Gilbert
Kevin Kinsey [EMAIL PROTECTED] writes:

 Lowell Gilbert wrote:
 Chris Haulmark [EMAIL PROTECTED] writes:

 Grant Peel wrote:

 I thought I would ask the question before I do it the hard way 

 1. Can FreeBSD be upgraded from 5.2.1 to 6.2 ?

 Yes.

 2. Can it be done through an ssh connection, or MUST I make the trip
 to the farm and do it from the console?

 I've done 5.x to 6.x upgrades via ssh.  It is possible.

 In the handbook, you will see mentions of booting into single user mode
 and I can tell you that it is not required.

 It's a good safety precaution; if your updated kernel won't boot, you
 will need to reinstall most of the system.

 That sounds a tad alarmist; if the new kernel won't boot, you'll
 have to be at (or have someone at) the console who can boot
 kernel.old (I stand open for correction, but last time I did
 it, 'twas that way).  And, possibly, that person (you?) will
 also have to be able to do some other magic.

 But the phrase reinstall most of the system doesn't, at
 the very least, *sound* like the BSD Way(tm).  Granted,
 sometimes it's quicker --- I know that's why it's used so
 often on that Other System  ;-)

If you have reinstalled a userland that depends on a kernel that
doesn't boot, you are quite likely to be in trouble.

The BSD way does not necessarily involve easy recovery from making
up procedures that haven't been worked out or tested by the release
engineers.  In fact, I don't think any operating system guarantees
that you will have an easy time after making up your own upgrade
procedures.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1-RELEASE FTP site error suddenly

2005-09-08 Thread Kris Kennaway
On Thu, Sep 08, 2005 at 12:41:31PM -0400, John Do wrote:
 Here is what happens:
 
 pkg_add -r apache+mod_ssl
 Error: FTP Unable to get
 ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/old-releases/i386/5.2.1-RELEASE/packages/Latest/apache+mod_ssl.tbz:
 Protocol error
 pkg_add: unable to fetch
 'ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/old-releases/i386/5.2.1-RELEASE/packages/Latest/apache+mod_ssl.tbz'
 by URL
 
 
 Even if I try to do a wget to the ftp I still get an
 error.
 
 I am able to successfully wget from other FTP sites.
 
 Anyone have any solutions?

It works for me, maybe it was something transient.

 Is there a mirror of the packages for 5.2.1-RELEASE I
 can try?

Try http://mirrorlist.freebsd.org/ - it only lists the release bits
(not packages directly), but if they have one there's a better chance
they have the other.

Kris


pgpEZlLMqmggh.pgp
Description: PGP signature


Re: 5.2.1-RELEASE FTP site error suddenly

2005-09-08 Thread John Do
Thanks Kris!

I found a successful mirror site.

You can FTP through a Windows box or other client but
from FreeBSD 5.2.1 the mirror site I mentioned still
doesn't work with pkg_add or wget (it worked about a
day or two ago) whereas the one below does work for
pkg_add and also wget at this time

ftp://ftp3.de.freebsd.org/pub/FreeBSD/releases/i386/5.2.1-RELEASE/5.2.1-RELEASE/packages/Latest/
--- Kris Kennaway [EMAIL PROTECTED] wrote:

 On Thu, Sep 08, 2005 at 12:41:31PM -0400, John Do
 wrote:
  Here is what happens:
  
  pkg_add -r apache+mod_ssl
  Error: FTP Unable to get
 

ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/old-releases/i386/5.2.1-RELEASE/packages/Latest/apache+mod_ssl.tbz:
  Protocol error
  pkg_add: unable to fetch
 

'ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/old-releases/i386/5.2.1-RELEASE/packages/Latest/apache+mod_ssl.tbz'
  by URL
  
  
  Even if I try to do a wget to the ftp I still get
 an
  error.
  
  I am able to successfully wget from other FTP
 sites.
  
  Anyone have any solutions?
 
 It works for me, maybe it was something transient.
 
  Is there a mirror of the packages for
 5.2.1-RELEASE I
  can try?
 
 Try http://mirrorlist.freebsd.org/ - it only lists
 the release bits
 (not packages directly), but if they have one
 there's a better chance
 they have the other.
 
 Kris
 


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 install error

2004-12-15 Thread Gable Barber
On Mon, 13 Dec 2004 11:17:02 -0600, Gable Barber [EMAIL PROTECTED] wrote:
 Hello,
 I am trying to install FreebSD 5.2.1 from CD, on the following box, I
 am getting an error when it is installing /usr/ports.
 
 The gear:
 
 Duron 1000
 512meg RAM
 Mylex Acceleraid 150 (DAC960)
 4x9G IBM SCSI drives (7200rpm)
 
 The error :
 
 anic: free: address 0xc978f00 has not been allocated
 
 cpuid:0
 
 syncing discs
 
 from there it counts about 4 lines of 4 digit codes, then reboots..
 
 I have searched the questions archive, and google.com/bsd without much
 avail. There were 2-3 similar posts with no follow ups.
 
 I thouhgt it might be a RAM problem, so I have tested with 2 different
 modules (256each). The error continues to happen.
 
 Possibly CPU?
 
 I am at a loss, thank you in advance for any ideas...
 
 Gable
 


The problem was the SCSI card. For some reason, it didnt like writing
a bunch of small directories and files (installing /usr/ports). It
would pass the error and reboot.

I tried 3 different cpu's on 2 different motherboards. 3 different RAM modules.

If anyone has had any experience with these controllers, and has any
idea where to go, I would certainly appreciate it. I hate to write off
the card as toast..

Thank you,
Gable
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1, installed Mozilla -- X reverses background colors when used!!

2004-10-30 Thread Matthew Seaman
On Fri, Oct 29, 2004 at 12:59:52PM -0700, Bill Schoolcraft wrote:
 At Fri, 29 Oct 2004 it looks like Volker Eckert composed:
 
  On Fri, Oct 29, 2004 at 05:57:59AM -0700, Bill Schoolcraft wrote:
   ...
   I have run 5.2.1 successfully on many machines and X is actually
   working fine except when I use Mozilla as installed from ports.
  
   The whole background turns into a negative and so does the Mozilla
   browser.  All returns to normal once I exit Mozilla.
   ...
 
  since nobody else replied... my 2 cents:
  maybe your X is running with too few colours? is it changing the
  colours when you change the focus?
 
 Thanks for your reply,
 
 What happens is all is fine with Opera, and Konqueror web
 browsers but once I start Mozilla, all hell breaks loose...
 
 It's like looking at a negative of a picture, whites turn black
 and the reversal of all colors, I can't describe to you the color
 changes for I was never aware of how much whole desktop can
 change.
 
 I mean EVERYTHING including the toolbars etc.
 
 I may go and install 4.10 and see what happens.  4.10 failed to
 install when the installation kernel hit the parallel port...
 Install/Kernel just wedged shut.

This sounds to me as if you're simply using a display which isn't
running at least 24bit colour depth.  All that's happening is that
Mozilla is installing its own colour map in the X server -- so when
you move your mouse pointer into or out of the Mozilla window, your
whole display switches from the default colour map to the Mozilla
colour map or back again.  ie.  it's not a bug.  It's a feature of
your graphics setup.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   26 The Paddocks
  Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614  Bucks., SL7 1TH UK


pgpZoWBy8xUwu.pgp
Description: PGP signature


Re: 5.2.1, installed Mozilla -- X reverses background colors when used!!

2004-10-30 Thread Bill Schoolcraft
At Sat, 30 Oct 2004 it looks like Matthew Seaman composed:

 This sounds to me as if you're simply using a display which isn't
 running at least 24bit colour depth.  All that's happening is that
 Mozilla is installing its own colour map in the X server -- so when
 you move your mouse pointer into or out of the Mozilla window, your
 whole display switches from the default colour map to the Mozilla
 colour map or back again.  ie.  it's not a bug.  It's a feature of
 your graphics setup.

   Cheers,

   Matthew

Thanks Matthew,

I will go in and do some edits to my XF86Config file after backing
it up.


(question)

It's an integrated SiS, 32mb video chipset and I was also
wondering the command that best works like lspci -v on other Unix
variants.  I wanted to get a more accurate output if the video
cards attributes as the FreeBSD operating sees it.


I did also try Netscape7 and it did the same thing.  Only two
current browser perform normally without any changes and those
are:  Opera and Konqueror

Thanks.

--
Bill Schoolcraft   | Life's journey is not to arrive at the
PO Box 210076  | grave safely in a well preserved body,
San Francisco,CA 94121 | but rather to skid in sideways, totally
http://billschoolcraft.com | spent, yelling holy shit, what a ride!

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1, installed Mozilla -- X reverses background colors when used!!

2004-10-30 Thread Matthew Seaman
On Sat, Oct 30, 2004 at 08:57:12AM -0700, Bill Schoolcraft wrote:
 
 It's an integrated SiS, 32mb video chipset and I was also
 wondering the command that best works like lspci -v on other Unix
 variants.  I wanted to get a more accurate output if the video
 cards attributes as the FreeBSD operating sees it.

xdpyinfo(1) will show you what settings your display is currently
using.  You can also divine that information, plus stuff like howmuch
video RAM the X server thinks you have from the log file --
/var/log/Xorg.0.log or /var/log/XFree86.0.log according to which X
implementation you're using.

pciconf(1) will tell you what hardware is plugged into your PCI busses
-- for best results, run that as:

# pciconf -v -l

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   26 The Paddocks
  Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614  Bucks., SL7 1TH UK


pgpdy1NQTgpNu.pgp
Description: PGP signature


Re: 5.2.1, installed Mozilla -- X reverses background colors when used!!

2004-10-29 Thread Volker Eckert
On Fri, Oct 29, 2004 at 05:57:59AM -0700, Bill Schoolcraft wrote:
 ... 
 I have run 5.2.1 successfully on many machines and X is actually
 working fine except when I use Mozilla as installed from ports.
 
 The whole background turns into a negative and so does the Mozilla
 browser.  All returns to normal once I exit Mozilla. 
 ...

since nobody else replied... my 2 cents:
maybe your X is running with too few colours? is it changing the
colours when you change the focus?
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1, installed Mozilla -- X reverses background colors when used!!

2004-10-29 Thread Bill Schoolcraft
At Fri, 29 Oct 2004 it looks like Volker Eckert composed:

 On Fri, Oct 29, 2004 at 05:57:59AM -0700, Bill Schoolcraft wrote:
  ...
  I have run 5.2.1 successfully on many machines and X is actually
  working fine except when I use Mozilla as installed from ports.
 
  The whole background turns into a negative and so does the Mozilla
  browser.  All returns to normal once I exit Mozilla.
  ...

 since nobody else replied... my 2 cents:
 maybe your X is running with too few colours? is it changing the
 colours when you change the focus?

Thanks for your reply,

What happens is all is fine with Opera, and Konqueror web
browsers but once I start Mozilla, all hell breaks loose...

It's like looking at a negative of a picture, whites turn black
and the reversal of all colors, I can't describe to you the color
changes for I was never aware of how much whole desktop can
change.

I mean EVERYTHING including the toolbars etc.

I may go and install 4.10 and see what happens.  4.10 failed to
install when the installation kernel hit the parallel port...
Install/Kernel just wedged shut.

--
Bill Schoolcraft   | Life's journey is not to arrive at the
PO Box 210076  | grave safely in a well preserved body,
San Francisco,CA 94121 | but rather to skid in sideways, totally
http://billschoolcraft.com | spent, yelling holy shit, what a ride!

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1, installed Mozilla -- X reverses background colors

2004-10-29 Thread Bill Schoolcraft
At Fri, 29 Oct 2004 it looks like Volker Eckert composed:

 On Fri, Oct 29, 2004 at 05:57:59AM -0700, Bill Schoolcraft
 wrote:
  ...
  I have run 5.2.1 successfully on many machines and X is
  actually
  working fine except when I use Mozilla as installed from
  ports.
 
  The whole background turns into a negative and so does the
  Mozilla
  browser.  All returns to normal once I exit Mozilla.
  ...

 since nobody else replied... my 2 cents:
 maybe your X is running with too few colours? is it changing the
 colours when you change the focus?

Thanks for your reply,

What happens is all is fine with Opera, and Konqueror web
browsers but once I start Mozilla, all hell breaks loose...

It's like looking at a negative of a picture, whites turn black
and the reversal of all colors, I can't describe to you the color
changes for I was never aware of how much whole desktop can
change.

I mean EVERYTHING including the toolbars etc.

I may go and install 4.10 and see what happens.  4.10 failed to
install when the installation kernel hit the parallel port...
Install/Kernel just wedged shut.


--
Bill Schoolcraft   | Life's journey is not to arrive at the
PO Box 210076  | grave safely in a well preserved body,
San Francisco,CA 94121 | but rather to skid in sideways, totally
http://billschoolcraft.com | spent, yelling holy shit, what a ride!

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1, installed Mozilla -- X reverses background colors when used!!

2004-10-29 Thread epilogue
On Fri, 29 Oct 2004 12:59:52 -0700 (PDT)
Bill Schoolcraft [EMAIL PROTECTED] wrote:

 At Fri, 29 Oct 2004 it looks like Volker Eckert composed:
 
  On Fri, Oct 29, 2004 at 05:57:59AM -0700, Bill Schoolcraft wrote:
   ...
   I have run 5.2.1 successfully on many machines and X is actually
   working fine except when I use Mozilla as installed from ports.
  
   The whole background turns into a negative and so does the
   Mozilla browser.  All returns to normal once I exit Mozilla.

 I may go and install 4.10 and see what happens.  4.10 failed to
 install when the installation kernel hit the parallel port...
 Install/Kernel just wedged shut.

have you considered installing moz via packages?
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1, installed Mozilla -- X reverses background colors when used!!

2004-10-29 Thread Bill Schoolcraft
At Fri, 29 Oct 2004 it looks like epilogue composed:

 On Fri, 29 Oct 2004 12:59:52 -0700 (PDT)
 Bill Schoolcraft [EMAIL PROTECTED] wrote:

  At Fri, 29 Oct 2004 it looks like Volker Eckert composed:
 
   On Fri, Oct 29, 2004 at 05:57:59AM -0700, Bill Schoolcraft wrote:
...
I have run 5.2.1 successfully on many machines and X is actually
working fine except when I use Mozilla as installed from ports.
   
The whole background turns into a negative and so does the
Mozilla browser.  All returns to normal once I exit Mozilla.
 
  I may go and install 4.10 and see what happens.  4.10 failed to
  install when the installation kernel hit the parallel port...
  Install/Kernel just wedged shut.

 have you considered installing moz via packages?

Hmm, actually no.  I was always feeling pretty safe using the
ports system.  Aren't they the same packages?


--
Bill Schoolcraft   | Life's journey is not to arrive at the
PO Box 210076  | grave safely in a well preserved body,
San Francisco,CA 94121 | but rather to skid in sideways, totally
http://billschoolcraft.com | spent, yelling holy shit, what a ride!

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1, installed Mozilla -- X reverses background colors when used!!

2004-10-29 Thread epilogue
On Fri, 29 Oct 2004 15:30:43 -0700 (PDT)
Bill Schoolcraft [EMAIL PROTECTED] wrote:

 At Fri, 29 Oct 2004 it looks like epilogue composed:
 
  On Fri, 29 Oct 2004 12:59:52 -0700 (PDT)
  Bill Schoolcraft [EMAIL PROTECTED] wrote:
 
   At Fri, 29 Oct 2004 it looks like Volker Eckert composed:
  
On Fri, Oct 29, 2004 at 05:57:59AM -0700, Bill Schoolcraft
wrote:
 ...
 I have run 5.2.1 successfully on many machines and X is
 actually working fine except when I use Mozilla as installed
 from ports.

 The whole background turns into a negative and so does the
 Mozilla browser.  All returns to normal once I exit Mozilla.
  
   I may go and install 4.10 and see what happens.  4.10 failed to
   install when the installation kernel hit the parallel port...
   Install/Kernel just wedged shut.
 
  have you considered installing moz via packages?
 
 Hmm, actually no.  I was always feeling pretty safe using the
 ports system.  Aren't they the same packages?

it would be a quick way to test a binary that is 'supposed' to work. 
pehaps, you compiled your port with strange options (on the CLI or via
make.conf or even pkgtools.conf)

fwiw, trying a pkg is probably easier than reinstalling your system.

also, you might want cause the problem again, then check your /var/logs
to see if anything interesting shows up in either Xorg.0.log,
console.log, messages.log...

 
 --
 Bill Schoolcraft   | Life's journey is not to arrive at the
 PO Box 210076  | grave safely in a well preserved body,
 San Francisco,CA 94121 | but rather to skid in sideways, totally
 http://billschoolcraft.com | spent, yelling holy shit, what a ride!
 
 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: 5.2.1-RELEASE ethernet troubles

2004-09-25 Thread Stephen Krauth
On Thu, 23 Sep 2004, Ted Mittelstaedt wrote:

  -Original Message-
  From: Stephen Krauth [mailto:[EMAIL PROTECTED]
  Sent: Thursday, September 23, 2004 11:20 PM
  To: Ted Mittelstaedt
  Cc: [EMAIL PROTECTED]
  Subject: RE: 5.2.1-RELEASE ethernet troubles
 

 
  I would have tried that but the PnP config on my BIOS won't let me.
  It only lets you reserve IRQs 3-15 (skipping a few) and these cards
  consistently show up on IRQ 17.
 

 I've run across that too, idiot bios code writers.

 Your only option is a fully pnp-aware card.  The ne2000's generally
 wern't.  If you must use ISA, a 3com 3c509b set into pnp mode with
 the dos configuration program would probably work.  But your probably
 better off with a pci card.

 If the intel/pro isn't an option then try a cheapie Realtek 8029-based
 job (ne2000 clone) and see what happens.  You can often find these in
 junk bins and such.  If you want to wait for one I probably have one or
 two around here.

 Ted

Thanks for the offer, but I'm sure I'll get it working one way or
another.  Plus, I only tried the ne2000 card out of desperation; I'd
like to have at least 100Mbs between my two machines.

I'll tell how it goes when I get some time to work on it again.

- Steve K

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: 5.2.1-RELEASE ethernet troubles

2004-09-24 Thread Stephen Krauth

On Thu, 23 Sep 2004, Ted Mittelstaedt wrote:
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] Behalf Of Stephen Krauth
  Sent: Thursday, September 23, 2004 12:37 AM
  To: [EMAIL PROTECTED]
  Subject: 5.2.1-RELEASE ethernet troubles
 
 
  I'm at wits end here trying to setup a new Athlon64 machine with the
  i386 release of 5.2.1-RELEASE.  The problem is getting it to like a
  network card of some sort; I've tried and failed with 4 so far:
 
  1.  Motherboard built-in NVidia gigethernet (Ok, didn't expect that
  one to be supported)
  2.  Cheapo VT6105-based card using vr(4) driver:  It's recongnized in
  ifconfig but I get the dreaded watchdog timeout errors.  I can't
  seem to disable PnP in the BIOS per archive suggestions.  Also
  tried swapping slots, but it always shows on the same IRQ.  ACPI
  on/off doesn't matter.

 your bios on the motherboard doesen't like that card.  try flashing the
 bios if possible with a newer version.

  3.  Slightly less cheap LinkSys LNE100TX, using dc0 driver: dmesg
  reports MII without PHY! error and ifconfig therefore doesn't
  see it.

 lots of hardware versions of that card, just for grins try booting
 fbsd 4.10 and see if it is recognized.  driver issues galore.

  4.  ANCIENT 10BaseT card using ed0 driver:  It's recongnized but
  gives kernel: ed0 device timeout errors.
 

 To get that to work you need to go into bios and change the resources to
 manually assigned then exclude the irq you have on that card from the
 pnp manager in the bios.  even then, this may not work on all irq's.
 you may be a while at testing different ones.

I would have tried that but the PnP config on my BIOS won't let me.
It only lets you reserve IRQs 3-15 (skipping a few) and these cards
consistently show up on IRQ 17.

 Jsut keep trying different pci nics.  a intel etherexpress pro100 would be
 my next choice (fxp0)

 Ted

Anyway, I'll try all of these suggestions and hopefully get it to
work.  Thanks!

- Steve K

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: 5.2.1-RELEASE ethernet troubles

2004-09-24 Thread Ted Mittelstaedt


 -Original Message-
 From: Stephen Krauth [mailto:[EMAIL PROTECTED]
 Sent: Thursday, September 23, 2004 11:20 PM
 To: Ted Mittelstaedt
 Cc: [EMAIL PROTECTED]
 Subject: RE: 5.2.1-RELEASE ethernet troubles
 

 
 I would have tried that but the PnP config on my BIOS won't let me.
 It only lets you reserve IRQs 3-15 (skipping a few) and these cards
 consistently show up on IRQ 17.
 

I've run across that too, idiot bios code writers.

Your only option is a fully pnp-aware card.  The ne2000's generally
wern't.  If you must use ISA, a 3com 3c509b set into pnp mode with
the dos configuration program would probably work.  But your probably
better off with a pci card.

If the intel/pro isn't an option then try a cheapie Realtek 8029-based
job (ne2000 clone) and see what happens.  You can often find these in
junk bins and such.  If you want to wait for one I probably have one or
two around here.

Ted
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: 5.2.1-RELEASE ethernet troubles

2004-09-23 Thread Ted Mittelstaedt


 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] Behalf Of Stephen Krauth
 Sent: Thursday, September 23, 2004 12:37 AM
 To: [EMAIL PROTECTED]
 Subject: 5.2.1-RELEASE ethernet troubles
 
 
 I'm at wits end here trying to setup a new Athlon64 machine with the
 i386 release of 5.2.1-RELEASE.  The problem is getting it to like a
 network card of some sort; I've tried and failed with 4 so far:
 
 1.  Motherboard built-in NVidia gigethernet (Ok, didn't expect that
 one to be supported)
 2.  Cheapo VT6105-based card using vr(4) driver:  It's recongnized in
 ifconfig but I get the dreaded watchdog timeout errors.  I can't
 seem to disable PnP in the BIOS per archive suggestions.  Also
 tried swapping slots, but it always shows on the same IRQ.  ACPI
 on/off doesn't matter.

your bios on the motherboard doesen't like that card.  try flashing the
bios if possible with a newer version.

 3.  Slightly less cheap LinkSys LNE100TX, using dc0 driver: dmesg
 reports MII without PHY! error and ifconfig therefore doesn't
 see it.

lots of hardware versions of that card, just for grins try booting
fbsd 4.10 and see if it is recognized.  driver issues galore.

 4.  ANCIENT 10BaseT card using ed0 driver:  It's recongnized but
 gives kernel: ed0 device timeout errors.
 

To get that to work you need to go into bios and change the resources to
manually assigned then exclude the irq you have on that card from the
pnp manager in the bios.  even then, this may not work on all irq's.
you may be a while at testing different ones.

Jsut keep trying different pci nics.  a intel etherexpress pro100 would be
my next choice (fxp0)

Ted

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 hangs solved and now find a way to split the ntfs hard drive.

2004-09-15 Thread Richard Lynch
Choy Kho Yee wrote:
 On 2004/09/15, at 12:58, esmaeel pashapouri wrote:

 Now as in subject line, have to figure a way to split
 the hard drive which short sitedly by the hp was
 patitioned in  1 big chunk and formated in ntfs
 format.
 According to freebsd docs I am out of lock for now,
 unless to use comercial programs.
 If any one know of any other way i'll be glad to hear
 from them.

 I heard that some linux live-cds have the utility to resize NTFS
 partitions on them.
 I can't provide further information as I have never used them before.
 Perhaps you could check them out.

A quick Google yields these two:
http://www.sysresccd.org/
http://overclockix.octeams.com

I have used the first one.  It worked.  It was awesome.

One thing though:  BE PATIENT!!!

While it's trying to re-size the partition, it sits there for a LONG time
doing nothing at the end of the process, and your mouse and keyboard are
frozen.

Do *NOT* re-boot.  *WAIT*.

BE PATIENT.

It will *eventually* finish, and you'll be happy.  If you re-boot in the
middle of it re-partitioning, you will not be happy.

Pre-requisite:
You'll want to defrag the drive under windows first.

You should be able to poke around in the Control Panel/Admin/System areas
and get a visual display of where Windows has all its files.

You want to see a big chunk of white space on the right hand side, with
NOTHING but white on the right.

Sometimes Windows put hidden un-movable files at the end of the disk. 
You have to go into DOS and change their attributes and get them moved by
defrag before you can re-partition.

-- 
Like Music?
http://l-i-e.com/artists.htm

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 hangs solved and now find a way to split the ntfs hard drive.

2004-09-15 Thread Murray Taylor
On Thu, 2004-09-16 at 08:10, Richard Lynch wrote:
 Choy Kho Yee wrote:
  On 2004/09/15, at 12:58, esmaeel pashapouri wrote:
 
  Now as in subject line, have to figure a way to split
  the hard drive which short sitedly by the hp was
  patitioned in  1 big chunk and formated in ntfs
  format.
  According to freebsd docs I am out of lock for now,
  unless to use comercial programs.
  If any one know of any other way i'll be glad to hear
  from them.
 
  I heard that some linux live-cds have the utility to resize NTFS
  partitions on them.
  I can't provide further information as I have never used them before.
  Perhaps you could check them out.
 
 A quick Google yields these two:
 http://www.sysresccd.org/
 http://overclockix.octeams.com
 
 I have used the first one.  It worked.  It was awesome.
 
 One thing though:  BE PATIENT!!!
 
 While it's trying to re-size the partition, it sits there for a LONG time
 doing nothing at the end of the process, and your mouse and keyboard are
 frozen.
 
 Do *NOT* re-boot.  *WAIT*.
 
 BE PATIENT.
 
 It will *eventually* finish, and you'll be happy.  If you re-boot in the
 middle of it re-partitioning, you will not be happy.
 
 Pre-requisite:
 You'll want to defrag the drive under windows first.
 
 You should be able to poke around in the Control Panel/Admin/System areas
 and get a visual display of where Windows has all its files.
 
 You want to see a big chunk of white space on the right hand side, with
 NOTHING but white on the right.
 
 Sometimes Windows put hidden un-movable files at the end of the disk. 
 You have to go into DOS and change their attributes and get them moved by
 defrag before you can re-partition.

Sysrescue is very good .. I used it to partition my IBM A30 laptop
and all worked as advertised.

It boots from the CD into gentoo linux and gives a list of options ..
choose ntfsresize and work through.

You can fiddle about with the size 'balance' as much as you like,
nothing happens until you commit the resizing.

And then _wait_

It does seem to do nothing for long enough to suggest that it has
died . but it hasnt, and it does work ( I did two machines,
an A30P with 40 G HDD and the A30 with a 20G HDD. ) 
Both survived the experience and are running Winblows (at work)
and FreeBSD/KDE at home.

The hardest bit is to figure out which files windows has marked hidden
or system and which _DONT DEFRAG_ (Arggghh)

It took me 4 hours and a couple of shareware tools to properly 
clear up the high disk area .. . .#$%#^% *%*% .
The ntftresize then took about 10 minutes and the FReeBSD install took
about 40 minutes.

NB Windows will want to reboot a couple of times after installing
FreeBSD and / or the partitioning as the silly thing seems
to think that you have added  / changed devices or some such
nonsense. Once you get past that, the OS (FreeBSD) and the 
toy (Windows 2000) co-exist quite peacefully.

And mount_ntfs works fine too (RTFM man mount_ntfs for caveats)

mjt

-- 
Murray Taylor
Special Projects Engineer
-
Bytecraft Systems  Entertainment
P: +61 3 8710 2555
F: +61 3 8710 2599
D: +61 3 9238 4275
M: +61 417 319 256
E: [EMAIL PROTECTED]
or visit us on the web
http://www.bytecraftsystems.com
http://www.bytecraftentertainment.com



---
The information transmitted in this e-mail is for the exclusive
use of the intended addressee and may contain confidential
and/or privileged material. Any review, re-transmission,
dissemination or other use of it, or the taking of any action
in reliance upon this information by persons and/or entities
other than the intended recipient is prohibited. If you
received this in error, please inform the sender and/or
addressee immediately and delete the material. 

E-mails may not be secure, may contain computer viruses and
may be corrupted in transmission. Please carefully check this
e-mail (and any attachment) accordingly. No warranties are
given and no liability is accepted for any loss or damage
caused by such matters.
---


This Email has been scanned for Viruses by MailMarshal.

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 hangs solved and now find a way to split the ntfs hard drive.

2004-09-14 Thread Choy Kho Yee
On 2004/09/15, at 12:58, esmaeel pashapouri wrote:
Now as in subject line, have to figure a way to split
the hard drive which short sitedly by the hp was
patitioned in  1 big chunk and formated in ntfs
format.
According to freebsd docs I am out of lock for now,
unless to use comercial programs.
If any one know of any other way i'll be glad to hear
from them.
I heard that some linux live-cds have the utility to resize NTFS 
partitions on them.
I can't provide further information as I have never used them before.
Perhaps you could check them out.

---
Choy Kho Yee
url: http://dotkoyi.infoseek.ne.jp/
blog: http://dotkoyi.blogspot.com/
There are only 10 types of people in the world, i.e. those who 
understand binary numbers and those who do not.

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1-RELEASE and install.cfg unable to find ad0s1b dev node

2004-09-13 Thread Christian Hiris
On Tuesday 14 September 2004 02:12, Ivan Fetch wrote:
 Hello,

 I've searched the mailing lists and found others with this issue, but
 haven't found a solution yet - can someone point me in the right direction
 please?

 When using an install.cfg file with 5.2.1-RELEASE, I get:
  Unable to find device node for /dev/ad0s1b in /dev!
  The creation of filesystems will be aborted.

[...]

 debug=yes
 # Networking Options
 hostname=geo
 domainname=domain.com
 nameserver=192.168.0.254
 defaultrouter=192.168.0.254
 ipaddr=192.168.0.201
 netmask=255.255.255.0
 netDev=fxp0
 # Install Media Options
 mediaSetCDROM
 # Distribution Selection
 distSetKernDeveloper
 # Partitioning
 disk=ad0
 partition=all
 bootManager=boot
 diskPartitionEditor
 diskPartitionWrite
 ad0s1-1=ufs 524288 /
 ad0s1-2=swap 131072 none
 ad0s1-3=ufs 524288 /var
 ad0s1-4=ufs 0 /usr
 # Even commenting out the above and uncomminting the below, install still
 fails.
 #diskInteractive=yes
 diskLabelEditor
 diskLabelCommit
 installCommit

I think you should remove the functions diskPartitionWrite and 
diskLabelCommit, try this instead:

 debug=yes

 # Networking Options
 hostname=geo
 domainname=domain.com
 nameserver=192.168.0.254
 defaultrouter=192.168.0.254
 ipaddr=192.168.0.201
 netmask=255.255.255.0
 netDev=fxp0

 # Partitioning
 disk=ad0
 partition=all
 bootManager=boot
 diskPartitionEditor

 # disklabel
 ad0s1-1=ufs 524288 /
 ad0s1-2=swap 131072 none
 ad0s1-3=ufs 524288 /var
 ad0s1-4=ufs 0 /usr
 diskLabelEditor

 # install sys
 mediaSetCDROM
 distSetKernDeveloper
 installCommit


Cheers,
ch

-- 
Christian Hiris [EMAIL PROTECTED] | OpenPGP KeyID 0x3BCA53BE 
OpenPGP-Key at hkp://wwwkeys.eu.pgp.net and http://pgp.mit.edu
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 fs in 4.10

2004-09-09 Thread Bill Moran
mikko [EMAIL PROTECTED] wrote:
 Hello,
 
 I had 5.2 installed before, and have all my data on a 5.2 -made
 disk (separate from the system disk). After that I decided to use
 4.10 for the system. Now I cannot mount the data diskslice, I get
 incorrect superblock. Is it possible to use 5.x made disks in 4,
 or am I just simply screwed?

5.x use UFS2 filesystems by default.  To my knowledge, 4.x does not
have any way to access these.  You'll have to reinstlal 5.X to get
at your data.

When installing 5.X, you can use the options in the disk partitioning
section to choose UFS1 filesystems, which can be used by 4.X ... and
even Linux, I believe.

-- 
Bill Moran
Potential Technologies
http://www.potentialtech.com
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: 5.2.1 fs in 4.10

2004-09-09 Thread JJB
if you installed 5.2.1 from iso file burned to cdrom then the new
file system was used. 4.10 can not access the new 5.x file system.
So in your own words 'you are screwed'.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of mikko
Sent: Thursday, September 09, 2004 10:54 AM
To: [EMAIL PROTECTED]
Subject: 5.2.1 fs in 4.10


Hello,

I had 5.2 installed before, and have all my data on a 5.2 -made
disk (separate from the system disk). After that I decided to use
4.10 for the system. Now I cannot mount the data diskslice, I get
incorrect superblock. Is it possible to use 5.x made disks in 4,
or am I just simply screwed?

Thank you for your time,
Mikko
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
[EMAIL PROTECTED]

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 fs in 4.10

2004-09-09 Thread mikko
Thank you for the info. I guess I'll go back to 5 until 5-stable.

Mikko

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 custom kernel build fails with floating point exception error#1 during make on Cyrix 333 cpu

2004-08-27 Thread Subhro
You need to install the cvsup package before you can go through it. First 

pkg_add -r cvsup-without-gui (if you are just on a dumb terminal as I am on)
or pkg_add cvsup

After it completes, then copy the supfiles from
/usr/share/example/supfile to you home (I mean the root's home) or
anywhere you feel convinient to access. Open the stable supfile ( if
you want to track stable) in your favourite text editor ( mine is vi,
so I do vi stable-supfile). Read through the file, its well
documented. Change the hostname for the cvsup server (refer to the
handbook for cvsup locations, I generally use cvsup2.freebsd.org or
cvsup6.freebsd.org). Save the file and exit (in my case its :wq). Then
run the cvsup with the stable-supfile as argument. I do is:

cvsup -g -L 2 stable-supfile

If you want to schedule it as a cron job as I do then 

cvsup -g -L 1 stable-supfile

Let it complete. Now you have an updated source tree. Refer to the
make world section of the handbook and remake the whole tree (as I
always do on a freshly installed system) or just the kernel (your
choice). You should be on track. Refer to the handbook and man cvsup
for further details. And btw its not cvup its cvsup :-). Ket us know
if you again got stuck up.

Regards
S.
 

On Thu, 26 Aug 2004 22:44:25 -0700, Gordon Price [EMAIL PROTECTED] wrote:
 Specifically, how do you do that. I know what CVS is, but I do not know the
 correct way to cvup like you say. There is a CVS command with an update
 parameter. Would you be kind enough to give me the correct syntax and what
 directory I should run it from?
 
 Thanks,
 Gordon
 
 
 
 - Original Message -
 From: Subhro [EMAIL PROTECTED]
 To: FreeBSD-questions [EMAIL PROTECTED]
 Cc: Gordon Price [EMAIL PROTECTED]
 Sent: Thursday, August 26, 2004 9:40 PM
 Subject: Re: 5.2.1 custom kernel build fails with floating point exception
 error#1 during make on Cyrix 333 cpu
 
  I would recommend to cvsup before going with the compile.
 
  Regards
  S.
 
  On Thu, 26 Aug 2004 21:11:28 -0700, Gordon Price [EMAIL PROTECTED]
 wrote:
   I did not cvsup before compiling. My /etc/make.conf only has some Perl
 5.6.1
   stuff in it.
  
   Thanks,
   Gordon
  
  
  
   - Original Message -
   From: Subhro [EMAIL PROTECTED]
   To: FreeBSD-questions [EMAIL PROTECTED]
   Cc: Gordon Price [EMAIL PROTECTED]
   Sent: Thursday, August 26, 2004 8:18 PM
   Subject: Re: 5.2.1 custom kernel build fails with floating point
 exception
   error#1 during make on Cyrix 333 cpu
  
cat /etc/make.conf Please.
   
Did you cvsup before compiling?
   
Regards
S.
   
On Thu, 26 Aug 2004 16:51:26 -0700, Gordon Price [EMAIL PROTECTED]
   wrote:
 Folks!

I just tried to add option IPFIREWALL etal + IPDIVERT to the
 GENERIC
   conf file and while doing make, the compiler errors out with error #1,
   floating point exception. If I make the kernel from GENERIC with no
 changes,
   it builds properly. There are 5 option lines I added at the bottom of
   GENERIC that I have been using for several years:

 option   IPFIREWALL
 option   IPFIREWALL_VERBOSE
 option   IPFIREWALL_VERBOSE_LIMIT=100
 option   IPFIREWALL_DEFAULT_TO_ACCEPT
 option   IPDIVERT

I used the traditional kernel build method I have been using for
   years. Maybe the old Cyrix 333 which is a 686 class cpu is not supported
   anymore??

 Thanks for you help!

 R. Gordon Price
 [EMAIL PROTECTED]
 [EMAIL PROTECTED]
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to
   [EMAIL PROTECTED]

   
   
--
Subhro Sankha Kar
School of Information Technology
Block AQ-13/1 Sector V
ZIP 700091
India
   
   
  
  
 
 
  --
  Subhro Sankha Kar
  School of Information Technology
  Block AQ-13/1 Sector V
  ZIP 700091
  India
 
 
 
 


-- 
Subhro Sankha Kar
School of Information Technology
Block AQ-13/1 Sector V
ZIP 700091
India
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 custom kernel build fails with floating point exception error#1 during make on Cyrix 333 cpu

2004-08-26 Thread Subhro
cat /etc/make.conf Please.

Did you cvsup before compiling?

Regards
S.

On Thu, 26 Aug 2004 16:51:26 -0700, Gordon Price [EMAIL PROTECTED] wrote:
 Folks!
 
I just tried to add option IPFIREWALL etal + IPDIVERT to the GENERIC conf file 
 and while doing make, the compiler errors out with error #1, floating point 
 exception. If I make the kernel from GENERIC with no changes, it builds properly. 
 There are 5 option lines I added at the bottom of GENERIC that I have been using for 
 several years:
 
 option   IPFIREWALL
 option   IPFIREWALL_VERBOSE
 option   IPFIREWALL_VERBOSE_LIMIT=100
 option   IPFIREWALL_DEFAULT_TO_ACCEPT
 option   IPDIVERT
 
I used the traditional kernel build method I have been using for years. Maybe the 
 old Cyrix 333 which is a 686 class cpu is not supported anymore??
 
 Thanks for you help!
 
 R. Gordon Price
 [EMAIL PROTECTED]
 [EMAIL PROTECTED]
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]
 


-- 
Subhro Sankha Kar
School of Information Technology
Block AQ-13/1 Sector V
ZIP 700091
India
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 custom kernel build fails with floating point exception error#1 during make on Cyrix 333 cpu

2004-08-26 Thread Subhro
I would recommend to cvsup before going with the compile.

Regards
S.

On Thu, 26 Aug 2004 21:11:28 -0700, Gordon Price [EMAIL PROTECTED] wrote:
 I did not cvsup before compiling. My /etc/make.conf only has some Perl 5.6.1
 stuff in it.
 
 Thanks,
 Gordon
 
 
 
 - Original Message -
 From: Subhro [EMAIL PROTECTED]
 To: FreeBSD-questions [EMAIL PROTECTED]
 Cc: Gordon Price [EMAIL PROTECTED]
 Sent: Thursday, August 26, 2004 8:18 PM
 Subject: Re: 5.2.1 custom kernel build fails with floating point exception
 error#1 during make on Cyrix 333 cpu
 
  cat /etc/make.conf Please.
 
  Did you cvsup before compiling?
 
  Regards
  S.
 
  On Thu, 26 Aug 2004 16:51:26 -0700, Gordon Price [EMAIL PROTECTED]
 wrote:
   Folks!
  
  I just tried to add option IPFIREWALL etal + IPDIVERT to the GENERIC
 conf file and while doing make, the compiler errors out with error #1,
 floating point exception. If I make the kernel from GENERIC with no changes,
 it builds properly. There are 5 option lines I added at the bottom of
 GENERIC that I have been using for several years:
  
   option   IPFIREWALL
   option   IPFIREWALL_VERBOSE
   option   IPFIREWALL_VERBOSE_LIMIT=100
   option   IPFIREWALL_DEFAULT_TO_ACCEPT
   option   IPDIVERT
  
  I used the traditional kernel build method I have been using for
 years. Maybe the old Cyrix 333 which is a 686 class cpu is not supported
 anymore??
  
   Thanks for you help!
  
   R. Gordon Price
   [EMAIL PROTECTED]
   [EMAIL PROTECTED]
   ___
   [EMAIL PROTECTED] mailing list
   http://lists.freebsd.org/mailman/listinfo/freebsd-questions
   To unsubscribe, send any mail to
 [EMAIL PROTECTED]
  
 
 
  --
  Subhro Sankha Kar
  School of Information Technology
  Block AQ-13/1 Sector V
  ZIP 700091
  India
 
 
 
 


-- 
Subhro Sankha Kar
School of Information Technology
Block AQ-13/1 Sector V
ZIP 700091
India
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 pccard woes, -current iso?

2004-08-13 Thread Chris
Sam wrote:
Greetings,
I'm trying to get pccard networking up on my laptop (Thinkpad 600E).
Ifconfig -a doesn't show anything despite two cards plugged, and I
think this is why:
# dmesg | grep pccard
pccard0: 16-bit PCCard bus on cbb0
pccard1: 16-bit PCCard bus on cbb1
pccard0: Card has no functions!
pccard1: Card has no functions!
I've seen a list message indicating that -current has fixed this.
Unfortunately no-networking precludes cvsup.
If -current indeed has a fix for this, can someone
either a) tell me where I can find a -current iso, or
b) tell me where I can get the latest pccard sources so I can
patch 5.2.1 -release myself?
Any other ideas warmly welcomed.
Cheers,
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to 
[EMAIL PROTECTED]


You can cvsup the src (not a wise move - unless you are a very 
experianced user) OR - wait a bit longer for 5.3-REL

--
Best regards,
Chris
If you have to park six blocks away, you will find two
new parking spaces right in front of the building
entrance.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1-p9 kernel hang (unknown reason, but more info)

2004-08-12 Thread Hugo Silva
Hugo Silva wrote:
Hey list,
My last move on the server trouble was changing back some sysctl's to 
their original values.
Here is how loader.conf and sysctl.conf look now:
(the #commented values were the sysctls active when the server used to 
die. one of these was causing the problem,
since the server has been running for 2 days now (just got rebooted, 
but it didnt panic because it wouldn't have come back on its own and 
it wasn't rebooted by me.. datacenter must have reset it) when it 
wouldn't run for more than 8 hours until panic.

sysctl.conf:
security.bsd.see_other_uids=0
net.inet.tcp.recvspace=32768
net.inet.tcp.sendspace=32768
net.inet.icmp.drop_redirect=1
net.inet.tcp.blackhole=2
net.inet.udp.blackhole=2
net.inet.tcp.log_in_vain=0
net.inet.udp.log_in_vain=0
kern.maxfiles=32768
security.jail.set_hostname_allowed=0
#kern.maxfilesperproc=2000
#kern.maxprocperuid=400
kern.coredump=0
net.inet.tcp.msl=7500
kern.ipc.somaxconn=16424
loader.conf:
hint.acpi.0.disabled=1
#kern.ipc.nmbclusters=32768
#kern.ipc.maxsockets=16424
kern.maxproc=8000
boot_verbose=YES
In my opinion, it was kern.ipc.nmbclusters causing the problem.. now 
I've set it as default: kern.ipc.nmbclusters: 25600

Can anyone confirm this high value of nmbclusters could cause a panic 
on 5.2.1-RELEASE-p9 ? Perhaps this is a bug
fixed in -CURRENT?

One of the sysctls that are now commented out was causing the problem.
p.s: reply to the mailing lists, I am not subscribed with this email 
but need to use it since I can't send this large copy by my webmail 
(it stalls).

Many thanks!
Regards,
Hugo

Hugo Silva wrote:
(note: I'm not subscribed to the list with this email, but I couldn't 
send this large mail by my webmail)

Hey list,
Recently my server started failing daily, I though it was because of 
high loads. Now it even goes down if completely idle after a few hours.

I *still* don't have the panic message (lazy datacenter lol) but I 
booted the server with verbose enabled and got the list of hardware. 
I also removed any optimizations in sysctl stuff I had added 
(maxfiles, maxprocs, ipc stuff, etc, all defaults now)

The server ran fine for the first 20 days or so, then it kept dying 
on a daily basis. Unfortunately i still don't have the panic message. 
But if someone can give some hints based on hardware 
list+dmesg+mptable, it would help. I've been shooting in the dark so 
far..

Here is the dmesg (long):
Frequency 1193182 Hz quality 0
Calibrating TSC clock ... TSC clock: 2800121436 Hz
CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2800.12-MHz 686-class CPU)
 Origin = GenuineIntel  Id = 0xf25  Stepping = 5
 
Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE 

 Hyperthreading: 2 logical CPUs
real memory  = 4088397824 (3899 MB)
Physical memory chunk(s):
0x1000 - 0x0009efff, 647168 bytes (158 pages)
0x0010 - 0x003f, 3145728 bytes (768 pages)
0x00c29000 - 0xef64, 4003622912 bytes (977447 pages)
avail memory = 3973623808 (3789 MB)
APIC ID: physical 0, logical 0:0
APIC ID: physical 1, logical 0:1
APIC ID: physical 6, logical 0:2
APIC ID: physical 7, logical 0:3
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
cpu0 (BSP): APIC ID:  0
cpu1 (AP): APIC ID:  1
cpu2 (AP): APIC ID:  6
cpu3 (AP): APIC ID:  7
bios32: Found BIOS32 Service Directory header at 0xc00fdb70
bios32: Entry = 0xfdb80 (c00fdb80)  Rev = 0  Len = 1
pcibios: PCI BIOS entry at 0xf+0xdba1
pnpbios: Found PnP BIOS data at 0xc00f4420
pnpbios: Entry = f:32c4  Rev = 1.0
Other BIOS signatures found:
ioapic0: Assuming intbase of 0
ioapic0: intpin 0 - ExtINT (edge, activehi)
ioapic0: intpin 1 - irq 1 (edge, activehi)
ioapic0: intpin 2 - irq 2 (edge, activehi)
ioapic0: intpin 3 - irq 3 (edge, activehi)
ioapic0: intpin 4 - irq 4 (edge, activehi)
ioapic0: intpin 5 - irq 5 (edge, activehi)
ioapic0: intpin 6 - irq 6 (edge, activehi)
ioapic0: intpin 7 - irq 7 (edge, activehi)
ioapic0: intpin 8 - irq 8 (edge, activehi)
ioapic0: intpin 9 - irq 9 (edge, activehi)
ioapic0: intpin 10 - irq 10 (edge, activehi)
ioapic0: intpin 11 - irq 11 (edge, activehi)
ioapic0: intpin 12 - irq 12 (edge, activehi)
ioapic0: intpin 13 - irq 13 (edge, activehi)
ioapic0: intpin 14 - irq 14 (edge, activehi)
ioapic0: intpin 15 - irq 15 (edge, activehi)
ioapic1: Assuming intbase of 16
ioapic1: intpin 0 - irq 16 (level, activelo)
ioapic1: intpin 1 - irq 17 (level, activelo)
ioapic1: intpin 2 - irq 18 (level, activelo)
ioapic1: intpin 3 - irq 19 (level, activelo)
ioapic1: intpin 4 - irq 20 (level, activelo)
ioapic1: intpin 5 - irq 21 (level, activelo)
ioapic1: intpin 6 - irq 22 (level, activelo)
ioapic1: intpin 7 - irq 23 (level, activelo)
ioapic1: intpin 8 - irq 24 (level, activelo)
ioapic1: intpin 9 - irq 25 (level, activelo)
ioapic1: intpin 10 - irq 26 (level, activelo)
ioapic1: intpin 11 - irq 27 (level, activelo)
ioapic1: intpin 12 - irq 28 (level, activelo)
ioapic1: 

Re: 5.2.1 hang during install attempt.

2004-08-11 Thread Dick Davies

try setting 'pnp os installed' to no in the bios, it's surprising how 
many hardware problems that can fix.

* Egon Spengler [EMAIL PROTECTED] [0830 05:30]:
 maxlat=0x00(0ns)
intpin=a, irq=3
powerspec 2 supports D0 D1 D2 D3 current D0
map[10]: type 3, range 32, base , size 27, 
 memory disabled
 and there it sits, requiring hard reboot to start up again. It appears 
 to be related to the irq 3, which both one nic and my video card share, 

I think i remember having problems with this if I used DRI - I assumed bog
standard displays didn't need a VGA interrupt, but DRI did - do you have an
'assign irq to vga' or similar bios setting?


-- 
A great many people think they are thinking when they are merely
rearranging their prejudices.
-- William James
Rasputin :: Jack of All Trades - Master of Nuns
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: 5.2.1-p9 kernel hang (unknown reason, but more info)

2004-08-10 Thread Dave Stephens
I know this may seem a silly suggestion after all the info you've dug up, 
but it almost sounds like a bad power supply.  I've seen virtually identical 
problems with my old dual P2/333 box and it turned out to be the AT 
Motherboard power connectors from the power supply that were screwed up and 
making a flakey connection.

http://life.trollserver.com/image/dsc00332.jpg - very burnt AT connector
http://life.trollserver.com/image/dsc00333.jpg - visible scarring on the 
motherboard itself

The electrical engineer explanation is:  The power connector was making a 
crappy connection on one or more of the 5v lines, the others carried the 
load.  Burning caused by the excessive current caused other 5v lines to fail 
and the load on the remaining got higher still...  Queue the cascade effect 
to utter failure (and nearly a fire.)  After getting the power connectors 
replaced on the power supply and polishing the motherboard pins it worked 
well for a while and then started acting like your descriptions.  The 
eventual solution (keep in mind this was an old AT board and that this 
solution is not recommended for the hardware you/the data center have) was 
to cut the power connectors off completely and solder them directly to the 
motherboard.  no more flakey power issues.  :)

dave
Original Message Follows
(note: I'm not subscribed to the list with this email, but I couldn't send 
this large mail by my webmail)

Hey list,
Recently my server started failing daily, I though it was because of high 
loads. Now it even goes down if completely idle after a few hours.

I *still* don't have the panic message (lazy datacenter lol) but I booted 
the server with verbose enabled and got the list of hardware. I also removed 
any optimizations in sysctl stuff I had added (maxfiles, maxprocs, ipc 
stuff, etc, all defaults now)

The server ran fine for the first 20 days or so, then it kept dying on a 
daily basis. Unfortunately i still don't have the panic message. But if 
someone can give some hints based on hardware list+dmesg+mptable, it would 
help. I've been shooting in the dark so far..

Here is the dmesg (long):
Frequency 1193182 Hz quality 0
Calibrating TSC clock ... TSC clock: 2800121436 Hz
CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2800.12-MHz 686-class CPU)
 Origin = GenuineIntel  Id = 0xf25  Stepping = 5
 
Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE
 Hyperthreading: 2 logical CPUs
real memory  = 4088397824 (3899 MB)
Physical memory chunk(s):
0x1000 - 0x0009efff, 647168 bytes (158 pages)
0x0010 - 0x003f, 3145728 bytes (768 pages)
0x00c29000 - 0xef64, 4003622912 bytes (977447 pages)
avail memory = 3973623808 (3789 MB)
APIC ID: physical 0, logical 0:0
APIC ID: physical 1, logical 0:1
APIC ID: physical 6, logical 0:2
APIC ID: physical 7, logical 0:3
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
cpu0 (BSP): APIC ID:  0
cpu1 (AP): APIC ID:  1
cpu2 (AP): APIC ID:  6
cpu3 (AP): APIC ID:  7
bios32: Found BIOS32 Service Directory header at 0xc00fdb70
bios32: Entry = 0xfdb80 (c00fdb80)  Rev = 0  Len = 1
pcibios: PCI BIOS entry at 0xf+0xdba1
pnpbios: Found PnP BIOS data at 0xc00f4420
pnpbios: Entry = f:32c4  Rev = 1.0
Other BIOS signatures found:
ioapic0: Assuming intbase of 0
ioapic0: intpin 0 - ExtINT (edge, activehi)
ioapic0: intpin 1 - irq 1 (edge, activehi)
ioapic0: intpin 2 - irq 2 (edge, activehi)
ioapic0: intpin 3 - irq 3 (edge, activehi)
ioapic0: intpin 4 - irq 4 (edge, activehi)
ioapic0: intpin 5 - irq 5 (edge, activehi)
ioapic0: intpin 6 - irq 6 (edge, activehi)
ioapic0: intpin 7 - irq 7 (edge, activehi)
ioapic0: intpin 8 - irq 8 (edge, activehi)
ioapic0: intpin 9 - irq 9 (edge, activehi)
ioapic0: intpin 10 - irq 10 (edge, activehi)
ioapic0: intpin 11 - irq 11 (edge, activehi)
ioapic0: intpin 12 - irq 12 (edge, activehi)
ioapic0: intpin 13 - irq 13 (edge, activehi)
ioapic0: intpin 14 - irq 14 (edge, activehi)
ioapic0: intpin 15 - irq 15 (edge, activehi)
ioapic1: Assuming intbase of 16
ioapic1: intpin 0 - irq 16 (level, activelo)
ioapic1: intpin 1 - irq 17 (level, activelo)
ioapic1: intpin 2 - irq 18 (level, activelo)
ioapic1: intpin 3 - irq 19 (level, activelo)
ioapic1: intpin 4 - irq 20 (level, activelo)
ioapic1: intpin 5 - irq 21 (level, activelo)
ioapic1: intpin 6 - irq 22 (level, activelo)
ioapic1: intpin 7 - irq 23 (level, activelo)
ioapic1: intpin 8 - irq 24 (level, activelo)
ioapic1: intpin 9 - irq 25 (level, activelo)
ioapic1: intpin 10 - irq 26 (level, activelo)
ioapic1: intpin 11 - irq 27 (level, activelo)
ioapic1: intpin 12 - irq 28 (level, activelo)
ioapic1: intpin 13 - irq 29 (level, activelo)
ioapic1: intpin 14 - irq 30 (level, activelo)
ioapic1: intpin 15 - irq 31 (level, activelo)
ioapic2: Assuming intbase of 32
ioapic2: intpin 0 - irq 32 (level, activelo)
ioapic2: intpin 1 - irq 33 (level, activelo)
ioapic2: intpin 2 - irq 34 

Re: 5.2.1 Install Error (Unable To Find Device Node)

2004-07-13 Thread Phil Schulz
I'm getting an Unable to find device node for
/dev/da0s1b in /dev error that is causing
installation to abort.  The disk is a 4x200GB IDE
RAID array.
[...]
I see Adaptec 2400A ATA-100 RAID controller ( asr(4)
driver) in the list; do I need to do anything
special, or will the driver load with the standard mfs
and kernel floppies?
Rishi,
I'm sorry but I don't /know/. But the driver floppy image doesn't have 
the driver included (according to the DRIVERS.TXT file) - it is possible 
that the driver is not included on the floppies just to save space. You 
might want to download the miniinst.iso from

ftp://ftp.CHANGE_THIS.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/5.2.1/5.2.1-RELEASE-i386-miniinst.iso
burn it to a blank cd and see if you can boot from the CD. Note that the 
URL above is for the i386 platform (ordinary PC) only. For other 
platforms, you'll need to go to the respective directory on the FTP 
server - I guess you'll find the file :-)

Phil.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 Install Error (Unable To Find Device Node)

2004-07-13 Thread Rishi Chopra
--- Phil Schulz [EMAIL PROTECTED] wrote:
 I'm getting an Unable to find device node for
 /dev/da0s1b in /dev error that is causing
 installation to abort.  The disk is a 4x200GB IDE
 RAID array.
 
 [...]
 
  I see Adaptec 2400A ATA-100 RAID controller (
 asr(4)
  driver) in the list; do I need to do anything
  special, or will the driver load with the standard
 mfs
  and kernel floppies?
 
 Rishi,
 
 I'm sorry but I don't /know/. But the driver floppy
 image doesn't have 
 the driver included (according to the DRIVERS.TXT
 file) - it is possible 
 that the driver is not included on the floppies just
 to save space. You 
 might want to download the miniinst.iso from
 

ftp://ftp.CHANGE_THIS.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/5.2.1/5.2.1-RELEASE-i386-miniinst.iso
 
 burn it to a blank cd and see if you can boot from
 the CD. Note that the 
 URL above is for the i386 platform (ordinary PC)
 only. For other 
 platforms, you'll need to go to the respective
 directory on the FTP 
 server - I guess you'll find the file :-)
 
 Phil.
 
 


My understanding is that DRIVERS.TXT applies only to
the additional driver floppy, and that all supported
hardware is included with the installation floppies. 
The BIOS does indeed boot for the array, and the array
is intact; can you think of anything else that would
prevent the installation?  The array also shows up as
asr0 when /stand/sysinstall boots.

=
Rishi Chopra
http://www.ocf.berkeley.edu/~rchopra



__
Do you Yahoo!?
Read only the mail you want - Yahoo! Mail SpamGuard.
http://promotions.yahoo.com/new_mail 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 Install Error (Unable To Find Device Node)

2004-07-12 Thread Phil Schulz
Hi Rishi,
I'm getting an Unable to find device node for
/dev/da0s1b in /dev error that is causing
installation to abort.  The disk is a 4x200GB IDE RAID
array.  Any idea what the problem might be?
This is a wild guess... but is the RAID controller supported? You might 
want to check http://www.freebsd.org/releases/5.2.1R/hardware.html and 
go on from there.

Regards,
Phil.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 Install Error (Unable To Find Device Node)

2004-07-12 Thread Rishi Chopra
--- Phil Schulz [EMAIL PROTECTED] wrote:
 Hi Rishi,
 
  I'm getting an Unable to find device node for
  /dev/da0s1b in /dev error that is causing
  installation to abort.  The disk is a 4x200GB IDE
 RAID
  array.  Any idea what the problem might be?
 
 This is a wild guess... but is the RAID controller
 supported? You might 
 want to check
 http://www.freebsd.org/releases/5.2.1R/hardware.html
 and 
 go on from there.
 
 Regards,
 
 Phil.
 
 

Phil,

I see Adaptec 2400A ATA-100 RAID controller ( asr(4)
driver) in the list; do I need to do anything
special, or will the driver load with the standard mfs
and kernel floppies?


=
Rishi Chopra
http://www.ocf.berkeley.edu/~rchopra



__
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
http://promotions.yahoo.com/new_mail
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1-rel install CD hangs Tecra 9100

2004-06-30 Thread Vince Hoffman


On Wed, 30 Jun 2004, xpi wrote:

   -or-
 Idiot user can't find the any key.


   I have a Toshiba Tecra 9100 laptop 1700mhz/256m, I'd like 5.2.1-rel on it. 
 Think I'm falling off the directions about disabling laptop pcibios ..but I'm out of 
 FAQ's

   Boot(8) sucessfully loads a kernel and displays the  boot menu, and no matter 
 how I tell the kernel to boot ( no APCI ) we hang after this... Sorry no serial 
 cable dmesg =) Tell me if we need to type _the whole thing_.


 agp0: Intel 82845 host to AGP brige mem 0xe-0xefff at device 0.0 on 
 pci0

 and then nothing, no disk access, no kbd interaction only zuul.

   The faq  has a note about disabling pcibios by getting '-c' to the kernel via 
 the boot prompt. I can't seem to get at that prompt in any way. The suggested 
 technique is to hit the any key at the boottrap spinner cursor; but those keystrokes 
 are buffered until the loader's menu comes up. (Idiot user can't find the any key, 
 tee hee)  Issuing boot -c to the loader prompt gets me to the same nowhere.

Help. I'm ignorant of the magick of boot(8) and it's gang.  I don't belive 
 that this machine has a text bios meny to tweak hw compatibility settings.

erk your mailer doesnt wrap at a sensible length (hint hint)
to get to the bios on all the tosiba tecra laptops i've come across,
(8000,8100,8200) you hold the esc key as soon as you turn it on, wait for
it to say there is an error, then press F1 to check the bios settings.

havent played with the 9000 series much though, so not sure what, if any,
useful options the bios will have.

Vince

   Hmm.. I should give darwin a shot that this HW g.
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 SMP problems

2004-06-05 Thread Toomas Aas
Hi!

 Installed 5.2.1 on a high load server - albeit not recommended - and 
 it was working perfectly with SMP support. It picked up 4 cpu's and 
 appeared to be using them all. (The box is a dual 2.4gig Xeon machine). 
 Anyway, the box was as I said under quite a bit of load, and would die 
 about once a day - just reboot. I looked into it a bit and found 
 whenever I put more load on (e.g. a make install in ports) it would 
 panic - vm_load_page or something like that - sorry about being so 
 vague. Anyway I took out SMP support, and now it boots with 2 cpu's - 
 one normal Xeon + HT for the second (no idea how to disable that - but I 
 don't need to)... its been running perfect for 4 days now and I put it 
 under SERIOUS load.. has anyone else had SMP problems on 5.2.1? 

I put 5.2.1-RELEASE on an IBM Netfinity 5000 (dual Pentium III) and I 
had problems, although different from yours. This system has some 
warning LEDs on the motherboard which light up when something is wrong. 
Quite often, when booting, the NMI and PCI1 LEDs would light up, the 
message NMI ISA 34, EISA ff appears among the boot messages and 
system reboots shortly after that. PCI1 LED indicates a problem with 
the first PCI bus, which is where I have IBM ServeRAID controller.

Interesting thing is that sometimes this problem during booting does 
not happen and once the system boots successfully there are never any 
problems.

When I removed the second CPU, the problem disappeared. I am not quite 
convinced yet that the problem is completely gone (haven't rebooted too 
many times) but it certainly has been greatly reduced.

Downgrading the firmware of ServeRAID controller from 6.10 to 5.10 (as 
recommended by another poster on this list) may also have contributed 
to resolving the problem. But the first thing I did was removing the 
2nd CPU and I successfully booted several times between that and 
downgrading the ServeRAID firmware. I *seem* to remember one NMI-boot 
after removing the second CPU, but I'm not quite sure my memory isn't 
failing me - it has been quite a rough ride with this NF5000 during the 
past few days. Anyway, *before* removing the second CPU, the boot 
failure rate was 50%, so I'm sure removing the second CPU did help, 
even if downgrading the ServeRAID firmware may have helped further.
--
Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/
* Feeling compressed ARJ you?

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 SMP problems

2004-06-04 Thread Albert Shih
 Le 04/06/2004 à 11:47:14+0200, Dave Raven a écrit
 Hi all,
Installed 5.2.1 on a high load server - albeit not recommended - and 
 it was working perfectly with SMP support. It picked up 4 cpu's and 
 appeared to be using them all. (The box is a dual 2.4gig Xeon machine). 
 Anyway, the box was as I said under quite a bit of load, and would die 
 about once a day - just reboot. I looked into it a bit and found 
 whenever I put more load on (e.g. a make install in ports) it would 
 panic - vm_load_page or something like that - sorry about being so 
 vague. Anyway I took out SMP support, and now it boots with 2 cpu's - 
 one normal Xeon + HT for the second (no idea how to disable that - but I 
 don't need to)... its been running perfect for 4 days now and I put it 
 under SERIOUS load.. has anyone else had SMP problems on 5.2.1? I 
 couldn't find anything about it at first glimpse...
 

Have you shure this problem is with FreeBSD ?

First check your memory with some software like memtest86 (http://www.memtest86.com/)

When I've this kind of problem, always it's because some error in RAM.

Regards



--
Albert SHIH
Universite de Paris 7 (Denis DIDEROT)
U.F.R. de Mathematiques.
Heure local/Local time:
Fri Jun 4 13:43:52 CEST 2004
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: 5.2.1 SMP problems

2004-06-04 Thread Dave Raven
Well all the tests I ran (about 2 memory testers and 2 benchmarks) caused
the box to die - even the make installs did half the time. Now that I've
disabled SMP there are no problems, and the same tests are working
perfectly...

The only thing I've changed is the SMP support, and now its been running for
4 days, before it wouldn't run for 12 hours

Thanks
Dave

-Original Message-
From: Albert Shih [mailto:[EMAIL PROTECTED] 
Sent: 04 June 2004 01:47 PM
To: Dave Raven
Cc: [EMAIL PROTECTED]
Subject: Re: 5.2.1 SMP problems


 Le 04/06/2004 à 11:47:14+0200, Dave Raven a écrit
 Hi all,
Installed 5.2.1 on a high load server - albeit not recommended - and 
 it was working perfectly with SMP support. It picked up 4 cpu's and 
 appeared to be using them all. (The box is a dual 2.4gig Xeon machine). 
 Anyway, the box was as I said under quite a bit of load, and would die 
 about once a day - just reboot. I looked into it a bit and found 
 whenever I put more load on (e.g. a make install in ports) it would 
 panic - vm_load_page or something like that - sorry about being so 
 vague. Anyway I took out SMP support, and now it boots with 2 cpu's - 
 one normal Xeon + HT for the second (no idea how to disable that - but I 
 don't need to)... its been running perfect for 4 days now and I put it 
 under SERIOUS load.. has anyone else had SMP problems on 5.2.1? I 
 couldn't find anything about it at first glimpse...
 

Have you shure this problem is with FreeBSD ?

First check your memory with some software like memtest86
(http://www.memtest86.com/)

When I've this kind of problem, always it's because some error in RAM.

Regards



--
Albert SHIH
Universite de Paris 7 (Denis DIDEROT)
U.F.R. de Mathematiques.
Heure local/Local time:
Fri Jun 4 13:43:52 CEST 2004

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 SMP problems

2004-06-04 Thread Bill Moran
Dave Raven [EMAIL PROTECTED] wrote:

 Well all the tests I ran (about 2 memory testers and 2 benchmarks) caused
 the box to die - even the make installs did half the time. Now that I've
 disabled SMP there are no problems, and the same tests are working
 perfectly...
 
 The only thing I've changed is the SMP support, and now its been running for
 4 days, before it wouldn't run for 12 hours

You may want to take this problem to hackers@ (with more details about the panic
and the hardware involved - the actual panic message and dmesg output) and see
if anyone is aware of the problem.

Since 5 is in heavy development, it's possible that this problem has already
been dealt with and fixed in 5-CURRENT.  If not, I'm sure the development team
would be interested in your assistance in fixing it.

 
 Thanks
 Dave
 
 -Original Message-
 From: Albert Shih [mailto:[EMAIL PROTECTED] 
 Sent: 04 June 2004 01:47 PM
 To: Dave Raven
 Cc: [EMAIL PROTECTED]
 Subject: Re: 5.2.1 SMP problems
 
 
  Le 04/06/2004 à 11:47:14+0200, Dave Raven a écrit
  Hi all,
 Installed 5.2.1 on a high load server - albeit not recommended - and 
  it was working perfectly with SMP support. It picked up 4 cpu's and 
  appeared to be using them all. (The box is a dual 2.4gig Xeon machine). 
  Anyway, the box was as I said under quite a bit of load, and would die 
  about once a day - just reboot. I looked into it a bit and found 
  whenever I put more load on (e.g. a make install in ports) it would 
  panic - vm_load_page or something like that - sorry about being so 
  vague. Anyway I took out SMP support, and now it boots with 2 cpu's - 
  one normal Xeon + HT for the second (no idea how to disable that - but I 
  don't need to)... its been running perfect for 4 days now and I put it 
  under SERIOUS load.. has anyone else had SMP problems on 5.2.1? I 
  couldn't find anything about it at first glimpse...
  
 
 Have you shure this problem is with FreeBSD ?
 
 First check your memory with some software like memtest86
 (http://www.memtest86.com/)
 
 When I've this kind of problem, always it's because some error in RAM.
 
 Regards
 
 
 
 --
 Albert SHIH
 Universite de Paris 7 (Denis DIDEROT)
 U.F.R. de Mathematiques.
 Heure local/Local time:
 Fri Jun 4 13:43:52 CEST 2004
 
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]


-- 
Bill Moran
Potential Technologies
http://www.potentialtech.com
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 boot-install

2004-06-02 Thread Bart Silverstrim
On Jun 2, 2004, at 8:21 AM, Bart Silverstrim wrote:
I have used this technique with 4.9, and it worked.  On a machine i 
wanted to install 5.2.1 on, it won't (this is a machine the 4.9 
install worked on fine).  The boot process starts, and it locks up 
ending with this in the bootup sequence:
GEOM: create disk ad0 dp=0xc2006560
ad0: 19092MB ST320014A [38792/16/63] at ata0-masster UDMA100
ata1-master: FAILURE - ATA_IDENTIFY status=7f READY, DMA_READY, DSC, 
DRQ, CORRECTABLE, INDEX_ERROR error=7fUNCORRECTABLE, MEDIA_CHANGED, 
NID_NOT_FOUND, MEDIA_CHANGE_REQUEST, ABORTED,NO_MEDIA,ILLEGAL_LENGTH 
LBA=0

Answering myself for the archives..
This *should* have worked and would have worked if not for a bug I had 
to workaround in 4.9 on that CDROM.  The CDROM is the only device on 
the bus, and if it were set to master, I kept getting ata1-master 
resetting ad infinitum; the jumper, once removed from the back of the 
CDROM drive, allowed 4.9 to work like a charm.  I remembered this after 
downloading and burning the bootonly ISO and having that fail with the 
same error...

Once I put the jumper back in to set the device to master, the 5.2.1 
CD booted straight to sysinstall.

Something for people to keep in mind... :-)
-Bart
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 goes beserk on EPIA M board

2004-05-31 Thread Chuck Swiger
Robert Downes wrote:
[ ... ]
ad0: FAILURE - WRITE_DMA status=11 DSC,ERROR error=84ICRC,ABORTED 
LBA=4127103

I did have, yesterday, FreeBSD 5.0 running on my EPIA M successfully 
until I tried to buildworld using 5.2.1 sources, at which point my EPIA 
hard crashed and reset itself. I assumed my PSU had failed briefly, but 
is it possible that 5.2.1 has special problems with the EPIA board or 
processor?
Sure, it's possible.  5.2.1 is very close to tracking -CURRENT, and there can 
be some fallout after people make changes to APCI, the ATAng code, and 
whatnot.  However, I have to say that the EPIA hardware tends to be fairly 
sensitive to things like poor IDE cables, jumping everything according to 
spec, etc.

--
-Chuck
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 can't find sound card

2004-04-21 Thread dslb
On Tuesday 20 April 2004 09:52 am, [EMAIL PROTECTED] wrote:
 Hmm, I read that you could download and install
 emu10kx-2004-04-14.tar.bz2 from http://chibis.persons.gfk.ru/audigy/
 ? But you all recommend that he wait for the 5.3-release?

Ok, my friend really wants his card to work now, so we downloaded the above
file from the site. Build a kernel with device pcm and device midi and
unpacked the file and ran make all make install. A file called snd_emu10kx.ko
has copied to /boot/kernel.
Next we rebooted and tried to load the module with kldload snd_emu10kx
but it says there is no such file, even though we can see it in /boot/kernel

So now what?

br
db

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 can't find sound card

2004-04-21 Thread Jan Christian Meyer
 snd_emu10kx.ko has copied to /boot/kernel.
 Next we rebooted and tried to load the module with kldload snd_emu10kx
 but it says there is no such file, even though we can see it in /boot/kernel

 So now what?

That should have been kldload /boot/kernel/snd_emu10kx.ko, I imagine...

Cheers,
 -Jan Christian

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 can't find sound card

2004-04-21 Thread User LAFFER1
I can tell you that Audigy Gamers work in freebsd current.  I *finally*
got my sound working last night.

I had a similar problem to yours when i had pcm in the kernel.  You don't
need it there.  Just compile the kernel without sound and then kldload the
snd_emu10k1 (or x in your case).  If that works, add the options to
loader.conf to make it auto load at boot time.

On Wed, 21 Apr 2004 [EMAIL PROTECTED] wrote:

 On Tuesday 20 April 2004 09:52 am, [EMAIL PROTECTED] wrote:
  Hmm, I read that you could download and install
  emu10kx-2004-04-14.tar.bz2 from http://chibis.persons.gfk.ru/audigy/
  ? But you all recommend that he wait for the 5.3-release?

 Ok, my friend really wants his card to work now, so we downloaded the above
 file from the site. Build a kernel with device pcm and device midi and
 unpacked the file and ran make all make install. A file called snd_emu10kx.ko
 has copied to /boot/kernel.
 Next we rebooted and tried to load the module with kldload snd_emu10kx
 but it says there is no such file, even though we can see it in /boot/kernel

 So now what?

 br
 db

 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 can't find sound card

2004-04-21 Thread dslb
On Wednesday 21 April 2004 12:00, Jan Christian Meyer wrote:
  snd_emu10kx.ko has copied to /boot/kernel.
  Next we rebooted and tried to load the module with kldload snd_emu10kx
  but it says there is no such file, even though we can see it in
  /boot/kernel
 
  So now what?

 That should have been kldload /boot/kernel/snd_emu10kx.ko, I imagine...

Already tried that:
DT# ls -l /boot/kernel/snd_emu10kx.ko
-r-xr-xr-x  1 root  wheel  391434 Apr 20 23:38 /boot/kernel/snd_emu10kx.ko
DT# kldload /boot/kernel/snd_emu10kx.ko
kldload: can't load /boot/kernel/snd_emu10kx.ko: No such file or directory
DT# kldload snd_emu10kx.ko
kldload: can't load snd_emu10kx.ko: No such file or directory

br
db

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 can't find sound card

2004-04-20 Thread Kent Stewart
On Tuesday 20 April 2004 02:17 am, [EMAIL PROTECTED] wrote:
 Hi all

 I have just installed FreeBSD 5.2.1 release on my friends i386
 computer with a Creative soundblaster audigy sound card. We compiled
 a new kernel with device pcm, but the kernel doesn't find the card.
 We have tried turning PnP on and off in the BIOS, but still no luck.
 Any ideas?


I found an email that said Audigy support was added to current after 5.2 
was released. I doubt it ever made it into 5.2.1. You might do your own 
search of the archives. I was looking for the commit. I thought O'Brien 
did it but couldn't find it.

Kent
-- 
Kent Stewart
Richland, WA

http://users.owt.com/kstewart/index.html
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 can't find sound card

2004-04-20 Thread dslb
On Tuesday 20 April 2004 12:18, you wrote:
  I found an email that said Audigy support was added to current after
  5.2 was released. I doubt it ever made it into 5.2.1. You might do
  your own search of the archives. I was looking for the commit. I
  thought O'Brien did it but couldn't find it.

 Look at

 http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/sound/pci/emu10k1.c

 It has no commit to any RELENG_* branch.

Ok, so in order to get it to work you sugests we do.?

br
db

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 can't find sound card

2004-04-20 Thread Chris
On Tuesday 20 April 2004 07:02 am, [EMAIL PROTECTED] wrote:
 On Tuesday 20 April 2004 12:18, you wrote:
   I found an email that said Audigy support was added to current after
   5.2 was released. I doubt it ever made it into 5.2.1. You might do
   your own search of the archives. I was looking for the commit. I
   thought O'Brien did it but couldn't find it.
 
  Look at
 
  http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/sound/pci/emu10k1.c
 
  It has no commit to any RELENG_* branch.

 Ok, so in order to get it to work you sugests we do.?

 br
 db

Wait till next release in the 5.x branch comes out?

-- 
Best regards,
Chris
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 can't find sound card

2004-04-20 Thread User LAFFER1
Audigy cards are not supported.  I have the same problem.  Supposedly,
current supports audigy's and there are several patches that i could not
get to work on the internet.  I'm trying to build a current kernel right
now to hopefully get sound on my desktop.

On Tue, 20 Apr 2004 [EMAIL PROTECTED] wrote:

 Hi all

 I have just installed FreeBSD 5.2.1 release on my friends i386 computer
 with a Creative soundblaster audigy sound card. We compiled a new kernel
 with device pcm, but the kernel doesn't find the card. We have tried turning
 PnP on and off in the BIOS, but still no luck. Any ideas?

 br
 db

 ps: please cc to me as I am not on the list

 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 can't find sound card

2004-04-20 Thread Kevin D. Kinsey, DaleCo, S.P.
Chris wrote:

On Tuesday 20 April 2004 07:02 am, [EMAIL PROTECTED] wrote:
 

On Tuesday 20 April 2004 12:18, you wrote:
   

I found an email that said Audigy support was added to current after
5.2 was released. I doubt it ever made it into 5.2.1. You might do
your own search of the archives. I was looking for the commit. I
thought O'Brien did it but couldn't find it.
   

Look at

http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/sound/pci/emu10k1.c

It has no commit to any RELENG_* branch.
 

Ok, so in order to get it to work you sugests we do.?

br
db
   

Wait till next release in the 5.x branch comes out?

 

Or run -CURRENT, as I understand it.

Kevin KInsey
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 can't find sound card

2004-04-20 Thread Kent Stewart
On Tuesday 20 April 2004 08:40 am, Kevin D. Kinsey, DaleCo, S.P. wrote:
 Chris wrote:
 On Tuesday 20 April 2004 07:02 am, [EMAIL PROTECTED] wrote:
 On Tuesday 20 April 2004 12:18, you wrote:
 I found an email that said Audigy support was added to current
  after 5.2 was released. I doubt it ever made it into 5.2.1. You
  might do your own search of the archives. I was looking for the
  commit. I thought O'Brien did it but couldn't find it.
 
 Look at
 
 http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/sound/pci/emu10k
 1.c
 
 It has no commit to any RELENG_* branch.
 
 Ok, so in order to get it to work you sugests we do.?
 
 br
 db
 
 Wait till next release in the 5.x branch comes out?

 Or run -CURRENT, as I understand it.


That was my implication. I don't run any releases but YMMV.

If it is a new machine and you want sound, you don't have much choice. 
The Audigy has never been MFCed to 4-stable.

Kent

-- 
Kent Stewart
Richland, WA

http://users.owt.com/kstewart/index.html
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 can't find sound card

2004-04-20 Thread dslb
On Tuesday 20 April 2004 17:47, you wrote:
  Wait till next release in the 5.x branch comes out?
 
  Or run -CURRENT, as I understand it.

 That was my implication. I don't run any releases but YMMV.

 If it is a new machine and you want sound, you don't have much choice.
 The Audigy has never been MFCed to 4-stable.

Hmm, I read that you could download and install emu10kx-22-june-2003.tar.gz
from http://chibis.persons.gfk.ru/audigy/ ? But you all recommend that he
wait for the 5.3-release?

br
db

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 can't find sound card

2004-04-20 Thread Kent Stewart
On Tuesday 20 April 2004 09:52 am, [EMAIL PROTECTED] wrote:
 On Tuesday 20 April 2004 17:47, you wrote:
   Wait till next release in the 5.x branch comes out?
  
   Or run -CURRENT, as I understand it.
 
  That was my implication. I don't run any releases but YMMV.
 
  If it is a new machine and you want sound, you don't have much
  choice. The Audigy has never been MFCed to 4-stable.

 Hmm, I read that you could download and install
 emu10kx-22-june-2003.tar.gz from http://chibis.persons.gfk.ru/audigy/
 ? But you all recommend that he wait for the 5.3-release?

I didn't but then I run 5-current. It has an Ensoniq sound card that 
worked from the boot of the first modified kernel.

I have a system that 99% of the time runs Windows XP because that is the 
place where the support for my Creative Nomad Zen2 is located. It has 
an Audigy Gamer sound card that has never worked on 4-stable. I have 
found that digital audio extraction from my audio CDs was very 
important and the Audigy supports that on XP. Since it is on a kvm with 
3 other systems with working sound support, I have never missed it. 

I am going to try Chibis' driver on it. I tried the OSS driver and it 
sounded terrible. No sound was better than what I was hearing and I 
really didn't want to spend the time to figure out what was wrong. 
There are a lot of DK (don't knows) on the Audigy. A kldload is too 
simple to try to not make the effort.

Kent


 br
 db

-- 
Kent Stewart
Richland, WA

http://users.owt.com/kstewart/index.html
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 FTP install over ISDN com-port ppp

2004-04-11 Thread Matthew Seaman
On Sun, Apr 11, 2004 at 12:16:47AM +0200, Srdjan Kupresanin wrote:

 I am a new addition to the FreeBSD community and don't even have a working
 installation yet. Please help with that, as I tried all other resources on
 the net (or at least I think I did).

Welcome.
  
 Anyway, I am trying to install 5.2.1 over FTP (I have downloaded the
 bootable CD image) and when I connect to my ISP through my ISDN TA on com1
 and using ppp PAP/CHAP, the connection gets established, but then the
 installation tries to establish IPv6 protocol, which gets rejected. It loops
 three times, and then stalls indefinitely.

Hmmm... Does your ISP publish IPv6 data from their PPP server?  It may
be that if your FreeBSD box gets assigned an IPv6 address it assumes
it should use IPv6 to do the install.  However most networking kit of
the sort you'ld use at home doesn't understand IPv6 yet, so won't pass
the traffic.

Can you try the installation, and instead of using the settings PPP
gives you automatically, configure the settings manually -- use the
same data as you got from PPP (except for the IPv6 address,
obviously), or whatever your ISP recommends.

The other alternative would be to do a minimal installation from the
mini ISO image, which will get you a bare bones but working FreeBSD
system, then:

# pkg_add -r cvsup-without-gui

and proceed to grab the system sources and the ports with cvsup.  And
then spend a few days building and installing everything you ned.

Once you've got the minimal system installed you'll be able to
configure PPP to do the right thing.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   26 The Paddocks
  Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614  Bucks., SL7 1TH UK


pgp0.pgp
Description: PGP signature


Re: 5.2.1 FTP install over ISDN com-port ppp

2004-04-11 Thread Kyryll A Mirnenko
  Just switch IPv6 off. I've got such problem when establishing callback 
dialup connection. Better idea is not to spend your money for low-speed modem 
connection but buy a distribution CD set.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 compiling error

2004-04-07 Thread Jonathan Arnold
Kris Kennaway wrote:

On Wed, Mar 31, 2004 at 09:57:14PM -0300, j.c.f. wrote:

greetings,

below is the compiling error and attached is the kernel config. I've tried 
several times. GENERIC compiles without a hitch. any help is appreciated.
thank you, karma

compile stops at vesa:
-warn-common -o vesa.ko vesa.kld
1 error
*** Error code 2


That doesn't show the error.  You truncated too much, and it looks
like you're building with make -j, which obscures the error message.
Rerun without -j and include more context.
And if you are building with make -j, don't. It isn't officially supported
and I've found on the rare times I've tried to use it, that it creates more
headaches than it solves.
--
Jonathan Arnold (mailto:[EMAIL PROTECTED])
Daemon Dancing in the Dark, a FreeBSD weblog:
http://freebsd.amazingdev.com/blog/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 ncplist s - kernel panic

2004-04-02 Thread Dave McCammon

--- Feczak Szabolcs [EMAIL PROTECTED] wrote:

http://www.mail-archive.com/[EMAIL PROTECTED]/msg60154.html
 
 Im having nearly the same thing as the above thread
 ...
 Though I have RELEASE not rc,
 any solution for this yet ?
 
 I would like to use samba and ncpfs on the machine
 and looks like smaba is buggy on 4.9, and ok on
 5.2.1
 see th PR by me : 
 http://www.freebsd.org/cgi/query-pr.cgi?pr=64719
 
 though ncpfs seems to be broken in 5.2.1 
 critical
 ...
 
 any suggestions ?
 
 
 -- 

I haven't seen anything back on this yet.
I upgraded to current after posting the dumps 
(see
http://groups.google.com/groups?hl=enlr=ie=UTF-8oe=UTF-8selm=20040219150356.GA53711%40faq.goivytech.net
)
 
I was going to wait until 5.3 stable was released to
see if any changes had been made. I haven't posted to
the current list as I don't subscribe to it.
If anyone needs anymore info on this let me know.



__
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway 
http://promotions.yahoo.com/design_giveaway/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 ncplist s - kernel panic

2004-04-02 Thread Dave McCammon

--- Feczak Szabolcs [EMAIL PROTECTED] wrote:
 On Fri, Apr 02, 2004 at 09:50:00AM -0800, Dave
 McCammon wrote:
  I haven't seen anything back on this yet.
  I upgraded to current after posting the dumps 
  (see
 

http://groups.google.com/groups?hl=enlr=ie=UTF-8oe=UTF-8selm=20040219150356.GA53711%40faq.goivytech.net
  )
   
  
 So does this means, that it is still broken in
 current ?
 
 

I haven't cvsuped since the posting to be sure if any
changes have been made. (I dual boot the machine so I
haven't had a real need to do more work on it.)
If I have time next week I'll upgrade to the latest
current code and see what happens.


__
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway 
http://promotions.yahoo.com/design_giveaway/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 sysinstall disk geometry problem

2004-03-31 Thread Jorge Mario G.
 When scripting sysinstall, it still halts with an
 error about my disk
 geometry. The problem is, even if I specify the
 geometry that FreeBSD
 wants to use by setting the geometry= variable, I
 still get the error.
 
 Everything else in sysinstall is being scripted
 correctly. The only
 problems I am having are disk related. Can anyone
 shed any light on this
 subject?
 
 Thanks,
 -Don
 
Hi there
the very same happened to me with a maxtor hard drive
and it happened to be a bad cable

check jumper settings, cables, controlers etc


jorge

_
Do You Yahoo!?
Información de Estados Unidos y América Latina, en Yahoo! Noticias.
Visítanos en http://noticias.espanol.yahoo.com
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 sysinstall disk geometry problem

2004-03-31 Thread Don
 the very same happened to me with a maxtor hard drive
 and it happened to be a bad cable

 check jumper settings, cables, controlers etc
It wasn't a jumper problem as it happened with a number of hard disks. I
simply commented out the code in sysinstall that generated the error and
supplied the geometry through the geometry directive in install.cfg.

I was also calling diskPartitionEditor and diskPartitionWrite.

If I just called diskPartitionEditor and left the rest for install commit
most of the other problems I was having went away.

-Don
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 sysinstall disk geometry problem

2004-03-31 Thread Jorn Argelo

 When scripting sysinstall, it still halts with an
 error about my disk
 geometry. The problem is, even if I specify the
 geometry that FreeBSD
 wants to use by setting the geometry= variable, I
 still get the error.

 Everything else in sysinstall is being scripted
 correctly. The only
 problems I am having are disk related. Can anyone
 shed any light on this
 subject?

 Thanks,
 -Don

Even when you use the exact values your BIOS thinks it is?

Jorn

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1-R sysinstall NFS install failure

2004-03-31 Thread Don
 Error mounting 10.3.1.20:/usr/FreeBSD/5.2.1-RELEASE on /dist: No such
 file or directory

 I can mount 10.3.1.20:/usr/FreeBSD/5.2.1-RELEASE on other systems within
 the network. The pxeboot loader is also pulling /kernel from an NFS mount
 on this server.
As usual this was my own stupidity. NFS is a kernel module on the boot
floppies and the module is on the drivers floppy and not the mfsroot
floppy. rsync'd the NFS modules over and the NFS install worked
flawlessly.

I think the above error is just _slightly_ misleading for a missing kernel
module but perhaps that is just me :)

-Don
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 sysinstall disk geometry problem

2004-03-31 Thread Don
  When scripting sysinstall, it still halts with an
  error about my disk
  geometry. The problem is, even if I specify the
  geometry that FreeBSD
  wants to use by setting the geometry= variable, I
  still get the error.

 Even when you use the exact values your BIOS thinks it is?
I am pretty sure it was still happening even then. Unfortunately, I had
several other minor problems and it was easy enough to hack sysinstall so
I did not bother to really check. If I have some time I will go back and
look into it again.

-Don
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 compiling error

2004-03-31 Thread Kris Kennaway
On Wed, Mar 31, 2004 at 09:57:14PM -0300, j.c.f. wrote:
 greetings,
 
 below is the compiling error and attached is the kernel config. I've tried 
 several times. GENERIC compiles without a hitch. any help is appreciated.
 thank you, karma
 
 compile stops at vesa:
 -warn-common -o vesa.ko vesa.kld
 1 error
 *** Error code 2

That doesn't show the error.  You truncated too much, and it looks
like you're building with make -j, which obscures the error message.
Rerun without -j and include more context.

Kris


pgp0.pgp
Description: PGP signature


Re: [5.2.1] trouble with an USB key

2004-03-29 Thread Bernd Walter
On Wed, Mar 10, 2004 at 08:45:29PM +0100, Jacques Beigbeder wrote:
 On a FreeBSD 5.2.1, I have an *OLD* USB disk which works:
 
 [ ... ] kernel: vendor 0x0c45 USB Mass Storage Device, rev 1.10/1.00, addr 2
 [ ... ]
 [ ... ] kernel: da2: 31MB (64000 512 byte sectors: 64H 32S/T 31C)
 
 Another one fails:
 [ ... ] umass0: Kingston DataTraveler2.0, rev 2.00/2.00, addr 2
 
 No da2 appears...

No error message apperas in your mail too.

 Is it because this second USB disk is USB2?

Unlikely - USB2 is just a revision.
If it's a high speed device (which most intermix with being USB2
because USB2 introduced high speed) then the device may not work with
a full speed capable controller.
But in your case it already said to be umass compliant so that's not
an issue.

 Is there any way to use it?

Is there any more debug output?
If not then add USB_DEBUG to your kernel and repeat.

-- 
B.Walter   BWCThttp://www.bwct.de
[EMAIL PROTECTED]  [EMAIL PROTECTED]

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: 5.2.1 Dell Power Edge 1400 install

2004-03-29 Thread Michael Clark
We have a 1400SC running 5.2.1.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, March 29, 2004 9:42 AM
To: Liste FreeBSD
Subject: 5.2.1 Dell Power Edge 1400 install 


Has anyone installed a 5.2.1 on a Dell Power Edge ?

 From what I have read so far It seems ok with the 4.7 version

--  
http://66.102.9.104/search?q=cache:fT11f82O3U0J:prioris.mini.pw.edu.pl/ 
~gregory/FreeBSD/ 
delli386.html+freeBSD+dell+poweredge+1400hl=enie=UTF-8

But i have no echo on a 5.2.1 install

__
«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§
¯¯
Gregober --- PGP ID -- 0x1BA3C2FD
omni_osx_ml @at@ todoo.biz
__
«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§
¯¯

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


CONFIDENTIALITY NOTE: This electronic transmission, including all
attachments, is directed in confidence solely to the person(s) to whom it is
addressed, or an authorized recipient, and may not otherwise be distributed,
copied or disclosed. The contents of the transmission may also be subject to
intellectual property rights and all such rights are expressly claimed and
are not waived. If you have received this transmission in error, please
notify the sender immediately by return electronic transmission and then
immediately delete this transmission, including all attachments, without
copying, distributing or disclosing same. 


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1-R == CURRENT????

2004-03-13 Thread Mark Ovens
Loren M. Lang wrote:
On Sat, Mar 13, 2004 at 01:00:38AM +, Mark Ovens wrote:
Kris Kennaway wrote:
On Fri, Mar 12, 2004 at 07:51:48PM +, Mark Ovens wrote:
Surely not? I was advised that a problem I'm experiencing is 
fixed in -current. I just updated my source tree to -current 
with ''cvs co src/'' but no files have been updated :-/
Did you cvsup your CVS repository first?

No, my src/ tree was pulled using

cvs up -Pd -rRELENG_5_2_1_RELEASE src/
Yes, of course no files were updates because you are pulling 5.2.1-R.
 Try removine the -r tag, I believe the default should be current, or
 use -rRELENG_5 which should pull the latest code in the 5-CURRENT.
That was how I pulled my _existing_ tree, as per my original post I
tried updating to current using ''cvs up src/''.
Part of this thread is missing as I clicked Reply instead of Reply All
to one of Kris' questions - here's what Kris has said (in reply to No,
my src/ tree was pulled...):
I don't understand.  Are you checking your tree out from an 
anomymous CVS server instead of a local CVS repository updated 
using cvsup?


Yes.
It's possible the CVS server is not being updated..they often fall 
into disrepair since most people don't use them.  YOu could also try 
just updating your 5.2.1 tree to current using cvs update -A.
I'll try pulling a new tree using CVSup instead.

Thanks for your help guys.

Regards,

Mark

 Kris

Mark

Kris
___ 
[EMAIL PROTECTED] mailing list 
http://lists.freebsd.org/mailman/listinfo/freebsd-questions To 
unsubscribe, send any mail to 
[EMAIL PROTECTED]

!DSPAM:40525fe3172951412226411!




___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1-R == CURRENT????

2004-03-13 Thread Mark Ovens
Mark Ovens wrote:
I'll try pulling a new tree using CVSup instead.

That did the trick; I zapped src/ and ports/ and started again with 
CVSup (pulling the trees directly, prefix=/usr, rather than via a local 
repository).

Thanks again.

Regards,

Mark

Thanks for your help guys.

Regards,

Mark

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1-R == CURRENT????

2004-03-12 Thread Kris Kennaway
On Fri, Mar 12, 2004 at 07:51:48PM +, Mark Ovens wrote:
 Surely not? I was advised that a problem I'm experiencing is fixed in 
 -current. I just updated my source tree to -current with ''cvs co src/'' 
 but no files have been updated :-/

Did you cvsup your CVS repository first?

Kris


pgp0.pgp
Description: PGP signature


Re: 5.2.1 miniinst cd panic during 3rd phase boot (kernel start).

2004-03-11 Thread kybu
SCN I haven't seen anything in the PR list or -questions just like this.

SCN My Compaq 1850 (2x PII-450, 1GByte Ram) boots up the 5.2.1-release
SCN miniinst cdrom just fine, loads the kenel, and just after waiting
SCN for SCSI devices to settle, panics.

SCN It does this with or without devices on the scsi bus.

SCN Anyone else have one of these critters working with 5.x?  Otherwise,
SCN anyone else have the same/a similar symptom?

Yeah, I got similar problem on Compaq 1650. I just change the OS
system type with SmartStart CD to Linux and then it works fine.

kybu

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 hanging on boot

2004-03-07 Thread Aaron Walker
On Sat, 2004-03-06 at 19:18, Lowell Gilbert wrote:
 Aaron Walker [EMAIL PROTECTED] writes:
 
  On Sat, 2004-03-06 at 16:01, Lowell Gilbert wrote:
   Aaron Walker [EMAIL PROTECTED] writes:
   
I just installed 5.2.1 and upon boot, it hangs at:

Timecounter TSC frequency 2153331273 Hz quality 800
Timecounters tick every 10.000 msec

It also did this when trying to boot via the 5.2.1 install CD, which was
circumvented by booting via floppy... 

It does not do this with 4.9. 

any ideas?
   
   You're booting without ACPI?
  
  If that is something you have to do manually, then no.  I'm just booting
  normally.  How would I turn off ACPI?
 
 Please read the errata and release notes before starting the install.
 I promise you'll have a much easier time.

Well, I read the errata.  Unfortunately, I am using GRUB as my boot
loader (this system runs win xp, linux, openbsd, and freebsd), which
doesn't support ufs2, so I have to boot FreeBSD 5+ indirectly using
grub's chainloading.  I am therefore unable to pass any kernel options,
and I don't have FreeBSD's boot loader installed, which I assume is
where you boot safe mode from.  

Is there any other way to turn off ACPI?

Thanks again,
Aaron

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 hanging on boot

2004-03-06 Thread Lowell Gilbert
Aaron Walker [EMAIL PROTECTED] writes:

 I just installed 5.2.1 and upon boot, it hangs at:
 
 Timecounter TSC frequency 2153331273 Hz quality 800
 Timecounters tick every 10.000 msec
 
 It also did this when trying to boot via the 5.2.1 install CD, which was
 circumvented by booting via floppy... 
 
 It does not do this with 4.9. 
 
 any ideas?

You're booting without ACPI?
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 hanging on boot

2004-03-06 Thread Aaron Walker
On Sat, 2004-03-06 at 16:01, Lowell Gilbert wrote:
 Aaron Walker [EMAIL PROTECTED] writes:
 
  I just installed 5.2.1 and upon boot, it hangs at:
  
  Timecounter TSC frequency 2153331273 Hz quality 800
  Timecounters tick every 10.000 msec
  
  It also did this when trying to boot via the 5.2.1 install CD, which was
  circumvented by booting via floppy... 
  
  It does not do this with 4.9. 
  
  any ideas?
 
 You're booting without ACPI?

If that is something you have to do manually, then no.  I'm just booting
normally.  How would I turn off ACPI?

Thanks again,
Aaron

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 hanging on boot

2004-03-06 Thread Lowell Gilbert
Aaron Walker [EMAIL PROTECTED] writes:

 On Sat, 2004-03-06 at 16:01, Lowell Gilbert wrote:
  Aaron Walker [EMAIL PROTECTED] writes:
  
   I just installed 5.2.1 and upon boot, it hangs at:
   
   Timecounter TSC frequency 2153331273 Hz quality 800
   Timecounters tick every 10.000 msec
   
   It also did this when trying to boot via the 5.2.1 install CD, which was
   circumvented by booting via floppy... 
   
   It does not do this with 4.9. 
   
   any ideas?
  
  You're booting without ACPI?
 
 If that is something you have to do manually, then no.  I'm just booting
 normally.  How would I turn off ACPI?

Please read the errata and release notes before starting the install.
I promise you'll have a much easier time.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 booting problem - hardware, software?

2004-02-26 Thread Przemek Ceglowski
Hi, I've got the same chipset in my mobo. There is
some kind of problem with ACPI, so its better to boot
without it (either disable it in bios/either choose
the right boot option).

Later on you will have some more problems with onboard
NIC and (if you have one) nvidia gfx.

Write to me if you will have the problems that I think
you will.

Przemyslaw Ceglowski


--- Grzegorz Burzyñski [EMAIL PROTECTED] wrote:
 Witam
 
  I got problem with installing 5.2.1 RC2 after
 i've changed my
  MBO. Earlier I've used MSI kt4v on VIA chipset
 and there was no
  problem. Now I got ABIT NF7-SL on nForce2
 chipset and I'm
  wondering what's goin' on? When I try to
 install fbsd,
  installation stops every time at this same
 point. The last thing
  in the output is:
  
#  Timocounters tick every 10.000 msec //or
 something like this
 
  in the next step, there should be /root/mfs...
 mounted, but
  install stops. I've tried to change my RAM, hd,
 cdrom with no
  result.
  I found in the output some lines like this:
 
  pci0: memory, RAM at device 0.1 on pci 0
 (driver not attached)
  pci0: memory, RAM at device 0.2 on pci 0
 (driver not attached)
  pci0: memory, RAM at device 0.3 on pci 0
 (driver not attached)
  ..
  the same with some other devices.
 
  Anyone got idea what could be wrong?
 -- 
 Pozdrowienia,
  Grzegorz 
 mailto:[EMAIL PROTECTED]
 
 ___
 [EMAIL PROTECTED] mailing list

http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to
[EMAIL PROTECTED]


__
Do you Yahoo!?
Get better spam protection with Yahoo! Mail.
http://antispam.yahoo.com/tools
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1-RC1 and RC2

2004-02-19 Thread Scott W
ian j hart wrote:

On Monday 16 February 2004 3:16 am, Kent Stewart wrote:
 

On Sunday 15 February 2004 07:04 pm, Chris wrote:
   

On Sunday 15 February 2004 09:00 pm, Thomas T. Veldhouse wrote:
 

Chris wrote:
   

Is is me? Or has something changed in 5.2 that tends to make
systems freeze up during portupgrade? Mainly - KDE-3.2.0
That being said, I seem to be seeing this more often on other
upgrades. Strange thing is, I considered it to be my PC however,
I never seem to run into the total freeze when doing a
buildworld.
 

No trouble here upgrading 5.2 to current on my desktop and no
trouble upgrading my 5.2p1 to 5.2RC2 on my server.  I suspect your
problem is hardware or driver related.
Tom Veldhouse
   

Tom,

My upgrades (5.2.1 - 5.2.1-RC1 - 5.2.1-RC2) went flawless. The
issues I'm having is during portupgrade.
Kent,
	Interesting - I did as you advised. I am typically running between
113 and 125 degrees (F) My AMD did come with a fan. Perchance I ought
to look into alternative cooling?
 

Mine ran like that for 53 weeks. The warranty was for 52. When it died,
it litterally blew one of the voltage regulator ICs on the motherboard.
All I saw was a flash of light at the same time as a loud bang and the
top right corner of the IC disappeared. Out was towards me but I didn't
feel it hit nor could I find it.
   

Much as I love AMD, I would have to agree about the fans. I bought boxed CPUs 
with fans as I expected that this would provide the right level of cooling 
(and reliability). IIRC the warranty was 2 years. When the first one went 
wobbly I replaced the lot. It's just not worth taking the chance.

To the OP, re temperatures. I wouldn't rely too much on what other peoples 
systems report.

The actual temperature of the CPU is going to depend on the speed and CPU core 
architecture (and maybe the BIOS) vs the ambient temp/cooling.

This is as opposed to the temperature reported. The accuracy is going vary 
with method (chip) which means, which M/B. I somehow doubt the sensors are 
individually calibrated against a lab standard.

If you can find somone with the same CPU/Motherboard, those numbers would be 
slightly more useful.

As a counter example my 2100+/Gigabyte GA-VTXE+ (BIOS F6a) sits at 54C idle 
and around 60C when busy. It's perfectly stable (on stable, not current).
[With fvcool idle temp = 30C]

If I forget to clean the filters, the temperature will rise, and the system 
becomes increasingly unstable. A few degrees increase is enough.

My advice is to clean any filters, fans and heatsinks and check the fans spin 
correctly. If the box runs cooler, note the temperature for future reference.

 

The current fans look like the Antec fans you can see in a Circuit City
or Best Buy. You can mail order them but I think I would buy one sooner
than that :). You have been having problems for quite a while now and
that may be what is going on.
Kent
   

 

Just another 'me too' on the lousy ^$#(# AMD supplied Athlon fans.  Had 
a dual AMD 1800+ setup with OE/Retail AMD fans, system less than a year 
old, actually purchased from a company that went under, so the system 
sat idle for a good part of that year.  Ran it for about a month, CPU 
fan failure, one _very_ cooked Athlon MP 1800+ CPU later...was cheaper 
to buy a pair of MP 2000+ off eBay than a new (or used) 1800+ CPU, but 
went ahead and spent the $ on ThermalTake Silent Boost fans- I don't 
overclock server systems, but they _are_ quiet by comparison, and are 
basically 80mm case fans with copper heat sink.  Both (replacement) CPUs 
I think I paid $140 for, and ~$50 for the fans, so it's a fair amount of 
$ by comparison, but have used TT fans in the past and haven't had one 
die on me yet.  Probably overkill, but lose a few CPUs (PIII CPUs seem 
to be able to survive a CPU fan failure, P4 and Xeons generally survive, 
but AMD chips will cook themselves in a heartbeat!) and it'll seem worth 
the few extra $$..

Scott

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1-RC1 and RC2

2004-02-19 Thread Scott W
ian j hart wrote:

On Monday 16 February 2004 3:16 am, Kent Stewart wrote:
 

On Sunday 15 February 2004 07:04 pm, Chris wrote:
   

On Sunday 15 February 2004 09:00 pm, Thomas T. Veldhouse wrote:
 

Chris wrote:
   

Is is me? Or has something changed in 5.2 that tends to make
systems freeze up during portupgrade? Mainly - KDE-3.2.0
That being said, I seem to be seeing this more often on other
upgrades. Strange thing is, I considered it to be my PC however,
I never seem to run into the total freeze when doing a
buildworld.
 

No trouble here upgrading 5.2 to current on my desktop and no
trouble upgrading my 5.2p1 to 5.2RC2 on my server.  I suspect your
problem is hardware or driver related.
Tom Veldhouse
   

Tom,

My upgrades (5.2.1 - 5.2.1-RC1 - 5.2.1-RC2) went flawless. The
issues I'm having is during portupgrade.
Kent,
	Interesting - I did as you advised. I am typically running between
113 and 125 degrees (F) My AMD did come with a fan. Perchance I ought
to look into alternative cooling?
 

Mine ran like that for 53 weeks. The warranty was for 52. When it died,
it litterally blew one of the voltage regulator ICs on the motherboard.
All I saw was a flash of light at the same time as a loud bang and the
top right corner of the IC disappeared. Out was towards me but I didn't
feel it hit nor could I find it.
   

Much as I love AMD, I would have to agree about the fans. I bought boxed CPUs 
with fans as I expected that this would provide the right level of cooling 
(and reliability). IIRC the warranty was 2 years. When the first one went 
wobbly I replaced the lot. It's just not worth taking the chance.

To the OP, re temperatures. I wouldn't rely too much on what other peoples 
systems report.

The actual temperature of the CPU is going to depend on the speed and CPU core 
architecture (and maybe the BIOS) vs the ambient temp/cooling.

This is as opposed to the temperature reported. The accuracy is going vary 
with method (chip) which means, which M/B. I somehow doubt the sensors are 
individually calibrated against a lab standard.

If you can find somone with the same CPU/Motherboard, those numbers would be 
slightly more useful.

As a counter example my 2100+/Gigabyte GA-VTXE+ (BIOS F6a) sits at 54C idle 
and around 60C when busy. It's perfectly stable (on stable, not current).
[With fvcool idle temp = 30C]

If I forget to clean the filters, the temperature will rise, and the system 
becomes increasingly unstable. A few degrees increase is enough.

My advice is to clean any filters, fans and heatsinks and check the fans spin 
correctly. If the box runs cooler, note the temperature for future reference.

 

The current fans look like the Antec fans you can see in a Circuit City
or Best Buy. You can mail order them but I think I would buy one sooner
than that :). You have been having problems for quite a while now and
that may be what is going on.
Kent
   

 

Oops, forgot to add on last post...in case anyone is looking for CPU 
temps..I've monitored a _lot_ of CPU temps on different systems, and the 
previous poster is right- different systems definitely run at different 
CPU temps, even with the same CPU and CPU fans, and I'd also question 
the CPU and MB temps themselves within ~5* as far as being 'accurate' 
against a standardbut FWIW, on a Tyan S2466-N MB, dual Althon MP 
2000+ with the ThermalTake Silent Boost fans (PITA to get on this MB BTW 
;-( ), claimed CPU Temps via BIOS after a week+ uptime and some large 
compiles putting load on the system, CPU Temp rarely goes above 55*C 
(reported), after compiling for several hours (KDE in this case).

Scott

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1-RC1 and RC2

2004-02-18 Thread ian j hart
On Monday 16 February 2004 3:16 am, Kent Stewart wrote:
 On Sunday 15 February 2004 07:04 pm, Chris wrote:
  On Sunday 15 February 2004 09:00 pm, Thomas T. Veldhouse wrote:
   Chris wrote:
Is is me? Or has something changed in 5.2 that tends to make
systems freeze up during portupgrade? Mainly - KDE-3.2.0
   
That being said, I seem to be seeing this more often on other
upgrades. Strange thing is, I considered it to be my PC however,
I never seem to run into the total freeze when doing a
buildworld.
  
   No trouble here upgrading 5.2 to current on my desktop and no
   trouble upgrading my 5.2p1 to 5.2RC2 on my server.  I suspect your
   problem is hardware or driver related.
  
   Tom Veldhouse
 
  Tom,
 
  My upgrades (5.2.1 - 5.2.1-RC1 - 5.2.1-RC2) went flawless. The
  issues I'm having is during portupgrade.
 
  Kent,
  Interesting - I did as you advised. I am typically running between
  113 and 125 degrees (F) My AMD did come with a fan. Perchance I ought
  to look into alternative cooling?

 Mine ran like that for 53 weeks. The warranty was for 52. When it died,
 it litterally blew one of the voltage regulator ICs on the motherboard.
 All I saw was a flash of light at the same time as a loud bang and the
 top right corner of the IC disappeared. Out was towards me but I didn't
 feel it hit nor could I find it.

Much as I love AMD, I would have to agree about the fans. I bought boxed CPUs 
with fans as I expected that this would provide the right level of cooling 
(and reliability). IIRC the warranty was 2 years. When the first one went 
wobbly I replaced the lot. It's just not worth taking the chance.

To the OP, re temperatures. I wouldn't rely too much on what other peoples 
systems report.

The actual temperature of the CPU is going to depend on the speed and CPU core 
architecture (and maybe the BIOS) vs the ambient temp/cooling.

This is as opposed to the temperature reported. The accuracy is going vary 
with method (chip) which means, which M/B. I somehow doubt the sensors are 
individually calibrated against a lab standard.

If you can find somone with the same CPU/Motherboard, those numbers would be 
slightly more useful.

As a counter example my 2100+/Gigabyte GA-VTXE+ (BIOS F6a) sits at 54C idle 
and around 60C when busy. It's perfectly stable (on stable, not current).
[With fvcool idle temp = 30C]

If I forget to clean the filters, the temperature will rise, and the system 
becomes increasingly unstable. A few degrees increase is enough.

My advice is to clean any filters, fans and heatsinks and check the fans spin 
correctly. If the box runs cooler, note the temperature for future reference.


 The current fans look like the Antec fans you can see in a Circuit City
 or Best Buy. You can mail order them but I think I would buy one sooner
 than that :). You have been having problems for quite a while now and
 that may be what is going on.

 Kent

-- 
ian j hart

http://ars.userfriendly.org/cartoons/?id=20031016

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1-RC1 and RC2

2004-02-18 Thread Chris
On Wednesday 18 February 2004 01:59 pm, ian j hart wrote:

 If I forget to clean the filters, the temperature will rise, and the system
 becomes increasingly unstable. A few degrees increase is enough.

 My advice is to clean any filters, fans and heatsinks and check the fans
 spin correctly. If the box runs cooler, note the temperature for future
 reference.

Funny you bring this up - I took the case off, cleaned everything out 
including the powersupply. I'm leaving the case off - currently, I'm running 
at 109 degrees (F) and I was able to do my portupgrade of KDE without issues.

All in all, better ventelation is helping out tremendously.

-- 
Best regards,
Chris
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1-RC2

2004-02-15 Thread Rowdy
Kris Kennaway wrote:

On Fri, Feb 13, 2004 at 12:55:16PM -0600, Chris wrote:

I see the above mentioned is on the site under ISO's


But the release candidate has not yet been announced, so these may
change at any time.  Don't use them until the announcement comes out,
because you might encounter a bug that was fixed in the real RC2.
Kris
I don't recall seeing an announcement about 5.2.1-RC (presumably RC1) 
anywhere (I am subscribed to freebsd-announce).

How does one determine whether a RC is real or not?

Dave

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1-RC2

2004-02-15 Thread Dan Strick
On Mon, 16 Feb 2004 08:20:08 +1100, [EMAIL PROTECTED] wrote:

 I don't recall seeing an announcement about 5.2.1-RC (presumably RC1) 
 anywhere (I am subscribed to freebsd-announce).


It was announced in freebsd-current.  Here is a copy of the announcement
of the second release candidate:



From [EMAIL PROTECTED]  Sat Feb 14 06:54:42 2004
Delivered-To: [EMAIL PROTECTED]
Message-ID: [EMAIL PROTECTED]
Date: Sat, 14 Feb 2004 07:52:01 -0700
From: Scott Long [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: FreeBSD 5.2.1-RC2 available

All,

FreeBSD 5.2.1-RC2 is now available for downloading.  Changes since the
RC1 include more bug fixes for ATA, working kernel modules on the
install floppies, and numerous security fixes to the src and XFree86
packages.  Note that the sparc64 XFree86-4-Server package in this set
does not have the latest updates.  This will be fixed in the final
release.

Please test this and let us know of any new problems.  There are a
couple of minor changes in our queue that will be committed soon,
after which we expect to do the final release.  Thanks!  Attached
are the MD5 sums for the CD images.

Scott

MD5 (5.2.1-RC2-i386-bootonly.iso) = 5c87912963b9d4d05d5a60cfc1bec486
MD5 (5.2.1-RC2-i386-disc1.iso) = 7cdfff4e1e378222f7f02c5465ca52e5
MD5 (5.2.1-RC2-i386-disc2.iso) = 7554bf9881e8235bfa002ca79209297f
MD5 (5.2.1-RC2-i386-miniinst.iso) = ff6a8fc30efbd53c13781382b1c80944

MD5 (5.2.1-RC2-alpha-bootonly.iso) = c6993f8de7411fae3c9dd9dd0c13ead4
MD5 (5.2.1-RC2-alpha-disc1.iso) = 002addc7353a88d369e8703d82ac934d
MD5 (5.2.1-RC2-alpha-disc2.iso) = c4004af3df38ee5da930b2387e24fcce
MD5 (5.2.1-RC2-alpha-miniinst.iso) = 6ed57031129bb9499318e66f1f86cf32

MD5 (5.2.1-RC2-sparc64-bootonly.iso) = 543b592da93a34f45ba25db0658f7e67
MD5 (5.2.1-RC2-sparc64-disc1.iso) = 9094e60baa66af49884cd2768a5ccf68
MD5 (5.2.1-RC2-sparc64-disc2.iso) = 934dc4fd8ecbb39128b1d8bd40252250
MD5 (5.2.1-RC2-sparc64-miniinst.iso) = a9e2329d9b3a2890fb95cdc5e548a6dd

MD5 (5.2.1-RC2-amd64-bootonly.iso) = d0a7e439a6738cee1ad5fa39b0a46520
MD5 (5.2.1-RC2-amd64-disc2.iso) = ae0fcf1c8ec59aed534f6e4c9c58a1a9
MD5 (5.2.1-RC2-amd64-miniinst.iso) = f8cc9687e23a8e9e2ca849c62917ffc8

MD5 (5.2.1-RC2-pc98-disc2.iso) = e3849821bd03d70ee71b58c31b5d9497
MD5 (5.2.1-RC2-pc98-miniinst.iso) = 52c407af87e6db58f5e3c312b2392308
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1-RC1 and RC2

2004-02-15 Thread Kent Stewart
On Sunday 15 February 2004 06:46 pm, Chris wrote:
 Is is me? Or has something changed in 5.2 that tends to make systems
 freeze up during portupgrade? Mainly - KDE-3.2.0

 That being said, I seem to be seeing this more often on other
 upgrades. Strange thing is, I considered it to be my PC however, I
 never seem to run into the total freeze when doing a buildworld.

A partial list of my ports shows

opal# pkgrep kde
kde-3.2.0   The meta-port for KDE
kdeaddons-3.2.0 Additional plugins and scripts for some KDE 
applications
kdeadmin-3.2.0  KDE applications related to system administration

I think I would install xmbmon and watch the termperature while you are 
building. AMD used to provide fans that were insufficient for long time 
100% cpu activity. I had a 2000+ XP that ran 54+oC while running 
setiathome and buildworlds. My current 2400+ XPs run around 40-43oC 
with the factory fans doing the same thing.

Kent

-- 
Kent Stewart
Richland, WA

http://users.owt.com/kstewart/index.html
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1-RC1 and RC2

2004-02-15 Thread Thomas T. Veldhouse
Chris wrote:
Is is me? Or has something changed in 5.2 that tends to make systems freeze up 
during portupgrade? Mainly - KDE-3.2.0

That being said, I seem to be seeing this more often on other upgrades. 
Strange thing is, I considered it to be my PC however, I never seem to run 
into the total freeze when doing a buildworld.


No trouble here upgrading 5.2 to current on my desktop and no trouble 
upgrading my 5.2p1 to 5.2RC2 on my server.  I suspect your problem is 
hardware or driver related.

Tom Veldhouse


signature.asc
Description: OpenPGP digital signature


Re: 5.2.1-RC1 and RC2

2004-02-15 Thread Chris
On Sunday 15 February 2004 09:00 pm, Thomas T. Veldhouse wrote:
 Chris wrote:
  Is is me? Or has something changed in 5.2 that tends to make systems
  freeze up during portupgrade? Mainly - KDE-3.2.0
 
  That being said, I seem to be seeing this more often on other upgrades.
  Strange thing is, I considered it to be my PC however, I never seem to
  run into the total freeze when doing a buildworld.

 No trouble here upgrading 5.2 to current on my desktop and no trouble
 upgrading my 5.2p1 to 5.2RC2 on my server.  I suspect your problem is
 hardware or driver related.

 Tom Veldhouse

Tom,

My upgrades (5.2.1 - 5.2.1-RC1 - 5.2.1-RC2) went flawless. The issues I'm 
having is during portupgrade.

Kent,
Interesting - I did as you advised. I am typically running between 113 and 
125 degrees (F) My AMD did come with a fan. Perchance I ought to look into 
alternative cooling?

-- 
Best regards,
Chris

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1-RC1 and RC2

2004-02-15 Thread Kent Stewart
On Sunday 15 February 2004 07:04 pm, Chris wrote:
 On Sunday 15 February 2004 09:00 pm, Thomas T. Veldhouse wrote:
  Chris wrote:
   Is is me? Or has something changed in 5.2 that tends to make
   systems freeze up during portupgrade? Mainly - KDE-3.2.0
  
   That being said, I seem to be seeing this more often on other
   upgrades. Strange thing is, I considered it to be my PC however,
   I never seem to run into the total freeze when doing a
   buildworld.
 
  No trouble here upgrading 5.2 to current on my desktop and no
  trouble upgrading my 5.2p1 to 5.2RC2 on my server.  I suspect your
  problem is hardware or driver related.
 
  Tom Veldhouse

 Tom,

   My upgrades (5.2.1 - 5.2.1-RC1 - 5.2.1-RC2) went flawless. The
 issues I'm having is during portupgrade.

 Kent,
   Interesting - I did as you advised. I am typically running between
 113 and 125 degrees (F) My AMD did come with a fan. Perchance I ought
 to look into alternative cooling?

Mine ran like that for 53 weeks. The warranty was for 52. When it died, 
it litterally blew one of the voltage regulator ICs on the motherboard. 
All I saw was a flash of light at the same time as a loud bang and the 
top right corner of the IC disappeared. Out was towards me but I didn't 
feel it hit nor could I find it.

The current fans look like the Antec fans you can see in a Circuit City 
or Best Buy. You can mail order them but I think I would buy one sooner 
than that :). You have been having problems for quite a while now and 
that may be what is going on. 

Kent

-- 
Kent Stewart
Richland, WA

http://users.owt.com/kstewart/index.html
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1-RC2

2004-02-13 Thread Kris Kennaway
On Fri, Feb 13, 2004 at 12:55:16PM -0600, Chris wrote:
 I see the above mentioned is on the site under ISO's

But the release candidate has not yet been announced, so these may
change at any time.  Don't use them until the announcement comes out,
because you might encounter a bug that was fixed in the real RC2.

Kris


pgp0.pgp
Description: PGP signature


RE: 5.2.1 - KDELibs and total freeze-up

2004-02-12 Thread Graeme Smith
The same thing happened to me on a PII Siemens laptop last night.  At the
time I figured it was just a heat issue, but perhaps there is more to it.  I
hard booted it and just let make carry on.  I can't tell if there is a
problem running KDE 3.20 yet as it's not finished compiling...  It was
definitely kdelibs where it froze though.

KDE-3.1.4  KDE-3.20 on 5.2

Good Luck!

Graeme

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf Of Chris
 Sent: 12 February 2004 4:24 am
 To: FreeBSD Questions
 Subject: 5.2.1 - KDELibs and total freeze-up

 Well folks, 
 
   Like the subject states - is anyone having this issue 
 when portupgrading 
 KDE-3.1.4 to KDE-3.20 (kdelibs) under 5.2.1?
 
   Some stats, I'm using an AthelonXP 2100 and the mb type 
 fleas my thought 
 process at the moment.  In any event, portupgrade hums along 
 then nada - 
 total freeze. 
 
   I'm forced to hard boot the box.
 - -- 
 Best regards,
 Chris
 

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


[Fwd: Re: 5.2.1-RC floppy install: many if_X.ko modules failed to load]

2004-02-10 Thread Rostislav Krasny
Members of freebsd-current mailing list are probably too busy, so I'm 
forwarding my question to more dynamic freebsd-questions mailing list. 
Is my guess about the /src/release/Makefile right or wrong?

BTW when 5.2.1-RC2 is going to be released? I saw few cvs commits with 
preparation to this release.

Thanks

 Original Message 
Subject: Re: 5.2.1-RC floppy install: many if_X.ko modules failed to load
Date: Sun, 08 Feb 2004 16:38:31 +0200
From: Rostislav Krasny [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
References: [EMAIL PROTECTED]
Rostislav Krasny wrote:
Hello.

When I boot from the installation floppies of 5.2.1-RC, at the beginning 
of sysinstall is starting I get a window on the blue background with 
following error message on it:

Loading module if_pcn.ko failed
AMD Am79c79x PCI ethernet card
then next window with the same error message:

Loading module if_vr.ko failed
VIA VT3043/VT86C100A Rhide PCI ethernet card
and so on about if_ste.ko, if_xl.ko, if_ed.ko, if_bge.ko, if_re.ko, 
if_wb.ko, if_rl.ko, if_sis.ko, if_dc.ko, if_bfe.ko, if_aue.ko, if_fxp.ko 
and if_sf.ko modules.

Previously I successfully installed FreeBSD 5.2-RELEASE from the 
floppies. Now, when I'm trying to install FreeBSD 5.2.1-RC by the same 
way, I'm geting the above error messages, so I'm forbearing to continue 
this installation. This problem is always repeatable, even after I made 
the floppies on different diskettes. This system doesn't have any AMD or 
VIA chip on it.
Could it be a result of revision 1.825.2.2 of the /src/release/Makefile
that adds a 'strip -x' run on the kernel modules on the mfsroot floppy?


 Original Message 
Subject: Re: 5.2.1-RC floppy install: many if_X.ko modules failed to load
Date: Sat, 7 Feb 2004 14:04:41 + (UTC)
From: [EMAIL PROTECTED] (Lowell Gilbert)
 [my very first email, skipped]

It looks like miibus is having some sort of problem:  the modules that
complain are all dependent on it.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.2.1 problems

2004-02-07 Thread Kris Kennaway
On Sat, Feb 07, 2004 at 04:31:56PM -0500, paul wrote:
 when I try to install 5.2.1 from ISO while booting i recieve this 
 message ata0-master: TIMEOUT - SETFEATURES SET TRANSFER MODE retrying 
 (0 retries left)
 
 I recieve this message twice then my whole system freezes and I can't do 
 nothing I also tryed installing 5.2 which installs fine then cvsuping to 
 5.2.1 and recieve the same problem. Anyone help me out?
 -Paul

There's another ATA fix waiting to be merged from HEAD.  Wait for
another 5.2.1 release candidate and tr yagain.

Kris


pgp0.pgp
Description: PGP signature


Re: [5.2.1-RC, IPFW] Traffic Shaping

2004-02-03 Thread Bjorn Eikeland
There isnt much you can really do as to shape incomming traffic, however
you can limit how fast you accept the incomming data. (At least this is
what im used to from my little experience with linux.)
I tried* the following rule, and in theroy it sounds up to the job:
ipfw add pipe 1 tcp from not me to me smtp
*)when I say tried I really mean ipfw didnt complain, but no traffic
actually saw it.
Obviously you can replace 'me' with your actual ip and 'smtp' with 25, but
I find its easier to read english.
Feel free to try that though :)

Hi all,

I am using FreeBSD 5.2.1-RC + IPFW2 + DUMMYNET to do traffic shaping.
This works well for my setup.
I have the following configuration:
The machine has 2 NIC's, xl0, dc0. The kernel is configured to do 
bridging. The bridged
packets is passed to IPFW (net.link.ether.bridge.ipfw=1).

I shape traffic this way:
The bridge is setup between a router and an internal mail server.
I am limiting bandwith using the following rules:
pipe 1 config bw 16KBytes/s
pipe 2 config bw 12KBytes/s
and then:

add pipe 1 tcp from any to any 25  (limit incoming traffic towards smtp)
add pipe 2 tcp from any 110 to any (limit outgoing traffic from pop3)
Yesterday, while browsing through Absolute BSD by Michael Lucas I read 
an interesting part:
You cannot shape incoming traffic the way that I do at the moment.

Now, my question:
How can I limit the incoming traffic towards my smtp server properly?
Any advice would be apreciated.

Thank you,
Regards
Jaco van Tonder
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: [5.2.1-RC, IPFW] Traffic Shaping

2004-02-03 Thread Bjorn Eikeland
Ok, so miss read the question a bit... (Was thinking the bridge was the
mail server too - used to my own hardware shortage :)
But still, I think you'll get it working by swapping 'me' with the ip of 
your
mail server. Can also use subnet to allow your own net unlimited access.

There isnt much you can really do as to shape incomming traffic, however
you can limit how fast you accept the incomming data. (At least this is
what im used to from my little experience with linux.)
I tried* the following rule, and in theroy it sounds up to the job:
ipfw add pipe 1 tcp from not me to me smtp
*)when I say tried I really mean ipfw didnt complain, but no traffic
actually saw it.
Obviously you can replace 'me' with your actual ip and 'smtp' with 25, 
but
I find its easier to read english.

Feel free to try that though :)

Hi all,

I am using FreeBSD 5.2.1-RC + IPFW2 + DUMMYNET to do traffic shaping.
This works well for my setup.
I have the following configuration:
The machine has 2 NIC's, xl0, dc0. The kernel is configured to do 
bridging. The bridged
packets is passed to IPFW (net.link.ether.bridge.ipfw=1).

I shape traffic this way:
The bridge is setup between a router and an internal mail server.
I am limiting bandwith using the following rules:
pipe 1 config bw 16KBytes/s
pipe 2 config bw 12KBytes/s
and then:

add pipe 1 tcp from any to any 25  (limit incoming traffic towards smtp)
add pipe 2 tcp from any 110 to any (limit outgoing traffic from pop3)
Yesterday, while browsing through Absolute BSD by Michael Lucas I read 
an interesting part:
You cannot shape incoming traffic the way that I do at the moment.

Now, my question:
How can I limit the incoming traffic towards my smtp server properly?
Any advice would be apreciated.

Thank you,
Regards
Jaco van Tonder
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to 
[EMAIL PROTECTED]



___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


  1   2   >