Re: howto sidestep sysinstall during installation

2009-05-10 Thread Daniel O'Connor
On Mon, 11 May 2009, Saifi Khan wrote:
> Is there a way to sidestep the sysinstall during the
> installation process, beyond selecting the 'location' ?
>
> i'm using FreeBSD 8.0 200905 i386 snapshot DVD and looking
> for an approach to drive the entire installation from the
> Fixit# command line console.
>
> i'm a experienced Gentoo Linux user.
>
> Any suggestions, pointers or observations ?

You won't be able to partition the disk from the command line because 
the install MFS doesn't have any of the requisite tools to do so.

You could do it from a livefs disk however.

As for observations.. I think you're wasting your time :)

-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C


signature.asc
Description: This is a digitally signed message part.


Re: Reading warnings when installing multiple ports

2009-05-10 Thread Matthew Seaman

Kelly Jones wrote:

I often use "make -DBATCH install" to install ports.

Problem: many ports spew out a warning/todo message after you install
them (eg, "you must manually create an x user" or something).

Since ports install "recursively", I miss most of these messages.

Can I tell ports to store these messages for me somewhere?

Obviously, I can "make -DBATCH install > /tmp/outfile", but that'll
log all the "install", "test", etc commands that I don't want to see:
I just want to see the warnings at the end of each install.



portmaster will save up package messages and display them all at the
end of the session.  I believe a similar feature is planned for portupgrade
but as far as I know it hasn't been released yet.

In any case, you can redisplay the pkg-message for any installed port
by:

  % pkg_info -Dx portname

Cheers,

Matthew


--
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
 Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
 Kent, CT11 9PW



signature.asc
Description: OpenPGP digital signature


fdisk: class not found

2009-05-10 Thread Saifi Khan
Hi all:

Trying to write a partition table using fdisk supplied in the
installation DVD of FreeBSD 8.0 i386 200905 snapshot.

Should we write new partition table ? [n] y
fdisk: Class not found

When i again run 'fdisk' it should the old partition table.

What exactly does 'Class not found' mean ?

There is no mention of the 'Class' in fdisk man page at
http://www.freebsd.org/cgi/man.cgi?query=fdisk&sektion=8

Can the experienced BSD guys explain ?


thanks
Saifi.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


howto sidestep sysinstall during installation

2009-05-10 Thread Saifi Khan
Hi all:

Is there a way to sidestep the sysinstall during the
installation process, beyond selecting the 'location' ?

i'm using FreeBSD 8.0 200905 i386 snapshot DVD and looking
for an approach to drive the entire installation from the
Fixit# command line console.

i'm a experienced Gentoo Linux user.

Any suggestions, pointers or observations ?


thanks
Saifi.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Unable to find device node for /dev/ad4s1b in /dev !

2009-05-10 Thread Saifi Khan
Hi all:

Issue faced
 Installer on 'Commit' step shows
  Unable to find device node for /dev/ad4s1b in /dev!
  The creation of filesystems will be aborted.

System
 Intel Celeron M 1.6 GHz 
 Intel 945GM board
 2GB DDR2
 160GB SATA Seagate HDD

i'm using FreeBSD 8.0 200905 i386 DVD to try and install 
the OS.

Using the FreeBSD 7.1 DVD, i'm able to make the partition,
define the slices and install a 'minimal' distribution set.

However with FreeBSD 8.0 200905 snapshot i'm getting the 
above mentioned error.

Any pointers or workarounds ?


thanks
Saifi.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: cups-base upgrade failure

2009-05-10 Thread Terry Sposato

Quoting "Jasvinder S. Bahra" :


Hi,

I'm trying to upgrade cups-base on my system, but i'm having some problems.

When I try (using portupgrade), i'm presented with the following...

--8<--
gmake[1]: Nothing to be done for `all'.
gmake[1]: Leaving directory  
`/var/ports/basejail/usr/ports/print/cups-client/work/cups-1.3.10/ppd'

Making all in templates...
gmake[1]: Entering directory  
`/var/ports/basejail/usr/ports/print/cups-client/work/cups-1.3.10/templates'

gmake[1]: Nothing to be done for `all'.
gmake[1]: Leaving directory  
`/var/ports/basejail/usr/ports/print/cups-client/work/cups-1.3.10/templates'

===>  Installing for cups-client-1.3.10_1
===>   Generating temporary packing list
===>  Checking if print/cups-client already installed
===>   cups-client-1.3.10_1 is already installed
 You may wish to ``make deinstall'' and install this port again
 by ``make reinstall'' to upgrade it properly.
 If you really wish to overwrite the old port of print/cups-client
 without deleting it first, set the variable "FORCE_PKG_REGISTER"
 in your environment or the "make install" command line.
*** Error code 1

Stop in /basejail/usr/ports/print/cups-client.
*** Error code 1

Stop in /basejail/usr/ports/print/cups-client.
*** Error code 1

Stop in /basejail/usr/ports/print/cups-base.
*** Error code 1

Stop in /basejail/usr/ports/print/cups-base.
*** Error code 1

Stop in /basejail/usr/ports/print/cups-base.
** Command failed [exit code 1]: /usr/bin/script -qa  
/tmp/portupgrade20090510-49660-5q2d8w-0 env UPGRADE_TOOL=portupgrade  
UPGRADE_PORT=cups-base-1.3.9_3 UPGRADE_PORT_VER=1.3.9_3 make reinstall

--->  Restoring the old version
** Fix the installation problem and try again.
[Updating the pkgdb  in /var/db/pkg ... - 39  
packages found (-0 +1) . done]

** Listing the failed packages (-:ignored / *:skipped / !:failed)
   ! print/cups-base (cups-base-1.3.9_3)   (install error)
--8<--

If I do a "uname -a", I get the following...

--8<--
FreeBSD pearl.xx.xxx 6.4-RELEASE-p4 FreeBSD 6.4-RELEASE-p4  
#0: Mon Apr 27 19:11:59 BST 2009  
j...@watchtower.xx.xxx:/usr/obj/usr/src/sys/WATCHTOWER  i386

--8<--

I've looked in /usr/ports/UPDATING, but i'm not seeing anything  
regarding cups.


Anyone have any ideas?


Jazz ___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"



Try re-installing cups-client and then upgrading cups-base.
I see the same issue when using portmaster, after you re-install the  
dependency it usually builds/installs fine.


Regards,

Terry Sposato
te...@sucked-in.com
Have you been sucked in?
http://www.sucked-in.com

-
This message was sent from the Sucked In Webmail Interface -  
http://www.sucked-in.com



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


geometry does not match label

2009-05-10 Thread Saifi Khan
Hi all:

when i try to boot the system using FreeBSD 8.0 i386 200905
bootonly CD, the following line is shown.

GEOM: ad4: geometry does not match label (255h,63S != 16h, 63s)

i just selected the entire disk and marked it bootable in the
fdisk partition editor option.

The system has a 160GB SATA HDD with
255 heads, 63 sectors/track, 19457 cylinders

Any pointers or suggestions ?


thanks
Saifi.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: Reading warnings when installing multiple ports

2009-05-10 Thread Glen Barber
On Sun, May 10, 2009 at 7:49 PM, Kelly Jones
 wrote:
> I often use "make -DBATCH install" to install ports.
>
> Problem: many ports spew out a warning/todo message after you install
> them (eg, "you must manually create an x user" or something).
>
> Since ports install "recursively", I miss most of these messages.
>
> Can I tell ports to store these messages for me somewhere?
>
> Obviously, I can "make -DBATCH install > /tmp/outfile", but that'll
> log all the "install", "test", etc commands that I don't want to see:
> I just want to see the warnings at the end of each install.
>

Have a look at:
   /usr/ports///pkg-message

Some ports have the message output in the Makefile instead.

-- 
Glen Barber
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: Booting question

2009-05-10 Thread Michel Di Croci
On Sun, May 10, 2009 at 9:52 PM, Glen Barber wrote:

> On Sun, May 10, 2009 at 8:31 PM, Michel Di Croci
>  wrote:
> > Hello!
> >
> > When I boot, it takes about 5 mins before being up and running. Since
> it's
> > my first FreeBSD, I didn't thought there was an issue, but I think
> there's
> > one ;)
> >
> > I have a P4 2.8 HT which is too bad computer and I really think the issue
> is
> > in freeBSD and the Giant Locked and stuff like that. The computer stays
> in a
> > waiting "mode" for about 3 minutes or something like that. It's
> unbearable,
> > however, since I reboot like once in a month, it's not that bad ;) But
> I'm
> > still wondering why it's so slow.
> >
> > I have compiled my own kernel, removed driver I don't use but I kept all
> usb
> > drivers. Like I told you, it's really the USB part that seems to be long
> to
> > load. It's like it's waiting for a stabilization mode that is never
> coming.
> >
> > Anyone had that kind of issue? I'm running 7.2 and it's been there since
> the
> > installation with 7.1.
> >
>
> Did it hang with GENERIC?  If not, do a diff on your config and the
> GENERIC config, and paste it for us.
>

If I remember correctly, yes but I don,t remember. Can you tell me if I
don't want to lose my actual kernel, how can I make a new kernel and install
it not as principal one.


>
> (On a side note, is your machine's `hostname` in /etc/hosts?  I've had
> a problem with sendmail hanging for some time because the hostname was
> not resolvable.  Just a side-thought.)
>

Yes it is in. And it's not the sendmail that is slow, it's the detection /
kernel step... not the service steps.

Michel


>
> --
> Glen Barber
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: Booting question

2009-05-10 Thread Glen Barber
On Sun, May 10, 2009 at 9:57 PM, Michel Di Croci
 wrote:
>>
>> Did it hang with GENERIC?  If not, do a diff on your config and the
>> GENERIC config, and paste it for us.
>
> If I remember correctly, yes but I don,t remember. Can you tell me if I
> don't want to lose my actual kernel, how can I make a new kernel and install
> it not as principal one.
>

This is explained in the handbook and the manual pages.

http://www.freebsd.org/doc/en/books/handbook/kernelconfig-trouble.html

You want to use 'nextboot' and specify the kernel location.

>>
>> (On a side note, is your machine's `hostname` in /etc/hosts?  I've had
>> a problem with sendmail hanging for some time because the hostname was
>> not resolvable.  Just a side-thought.)
>
> Yes it is in. And it's not the sendmail that is slow, it's the detection /
> kernel step... not the service steps.
>

If you're using 7.2 (-RELEASE I assume?) and this has been happening
since 7.1, it's not something that has changed recently.  I don't
recall seeing issues like this on this list (or stable@ for that
matter).  Perhaps it is a hardware problem, but I've never been good
at diagnosing hardware issues.

-- 
Glen Barber
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: Booting question

2009-05-10 Thread Glen Barber
On Sun, May 10, 2009 at 8:31 PM, Michel Di Croci
 wrote:
> Hello!
>
> When I boot, it takes about 5 mins before being up and running. Since it's
> my first FreeBSD, I didn't thought there was an issue, but I think there's
> one ;)
>
> I have a P4 2.8 HT which is too bad computer and I really think the issue is
> in freeBSD and the Giant Locked and stuff like that. The computer stays in a
> waiting "mode" for about 3 minutes or something like that. It's unbearable,
> however, since I reboot like once in a month, it's not that bad ;) But I'm
> still wondering why it's so slow.
>
> I have compiled my own kernel, removed driver I don't use but I kept all usb
> drivers. Like I told you, it's really the USB part that seems to be long to
> load. It's like it's waiting for a stabilization mode that is never coming.
>
> Anyone had that kind of issue? I'm running 7.2 and it's been there since the
> installation with 7.1.
>

Did it hang with GENERIC?  If not, do a diff on your config and the
GENERIC config, and paste it for us.

(On a side note, is your machine's `hostname` in /etc/hosts?  I've had
a problem with sendmail hanging for some time because the hostname was
not resolvable.  Just a side-thought.)

-- 
Glen Barber
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Booting question

2009-05-10 Thread Michel Di Croci
Hello!

When I boot, it takes about 5 mins before being up and running. Since it's
my first FreeBSD, I didn't thought there was an issue, but I think there's
one ;)

I have a P4 2.8 HT which is too bad computer and I really think the issue is
in freeBSD and the Giant Locked and stuff like that. The computer stays in a
waiting "mode" for about 3 minutes or something like that. It's unbearable,
however, since I reboot like once in a month, it's not that bad ;) But I'm
still wondering why it's so slow.

I have compiled my own kernel, removed driver I don't use but I kept all usb
drivers. Like I told you, it's really the USB part that seems to be long to
load. It's like it's waiting for a stabilization mode that is never coming.

Anyone had that kind of issue? I'm running 7.2 and it's been there since the
installation with 7.1.

Thanks and have a nice day

Michel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: Command-line IRC client

2009-05-10 Thread Kalle Møller
irssi + screen

On Fri, May 8, 2009 at 2:19 AM, Nerius Landys  wrote:
> What is the most recommended IRC client that runs in a terminal?
> rtorrent is to bit torrent what  is to IRC.
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
>



-- 

Med Venlig Hilsen

Kalle R. Møller
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Reading warnings when installing multiple ports

2009-05-10 Thread Kelly Jones
I often use "make -DBATCH install" to install ports.

Problem: many ports spew out a warning/todo message after you install
them (eg, "you must manually create an x user" or something).

Since ports install "recursively", I miss most of these messages.

Can I tell ports to store these messages for me somewhere?

Obviously, I can "make -DBATCH install > /tmp/outfile", but that'll
log all the "install", "test", etc commands that I don't want to see:
I just want to see the warnings at the end of each install.

-- 
We're just a Bunch Of Regular Guys, a collective group that's trying
to understand and assimilate technology. We feel that resistance to
new ideas and technology is unwise and ultimately futile.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: GDM users list

2009-05-10 Thread Marco Beishuizen

On Mon, 11 May 2009, Giorgos Keramidas wrote:


FWIW, the gdm user list applet seems to be having a few problems in
8.0-CURRENT too.

It is auto-enabled when procfs(5) is mounted at `/proc' but it only
shows `other' a few dozen times on my laptop, and clicking on them
sometimes crashes gdm.  I'm still trying to find out why, but you may
find it easier to get help by posting to the freebsd-gnome list.


Procfs is mounted at /proc on my system, but I'm not experiencing crashes. 
I'll send my question to the freebsd-gnome mailing list. Thanks.


Marco

--
Mustgo, n.:
Any item of food that has been sitting in the refrigerator so
long it has become a science project.
-- Rich Hall & Friends, "Sniglets"
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: GDM users list

2009-05-10 Thread Giorgos Keramidas
On Mon, 11 May 2009 01:07:10 +0200 (CEST), Marco Beishuizen  
wrote:
> When I use GDM for logging in, the only possible users I can choose
> from are the "logcheck system account" and "other", but not my regular
> user account. Why is that?

FWIW, the gdm user list applet seems to be having a few problems in
8.0-CURRENT too.

It is auto-enabled when procfs(5) is mounted at `/proc' but it only
shows `other' a few dozen times on my laptop, and clicking on them
sometimes crashes gdm.  I'm still trying to find out why, but you may
find it easier to get help by posting to the freebsd-gnome list.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


GDM users list

2009-05-10 Thread Marco Beishuizen


Hi,

When I use GDM for logging in, the only possible users I can choose from 
are the "logcheck system account" and "other", but not my regular user 
account. Why is that?


Marco

--
Only way to open lips of pigeon, sledgehammer.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


cups-base upgrade failure

2009-05-10 Thread Jasvinder S. Bahra

Hi,

I'm trying to upgrade cups-base on my system, but i'm having some problems.

When I try (using portupgrade), i'm presented with the following...

--8<--
gmake[1]: Nothing to be done for `all'.
gmake[1]: Leaving directory 
`/var/ports/basejail/usr/ports/print/cups-client/work/cups-1.3.10/ppd'

Making all in templates...
gmake[1]: Entering directory 
`/var/ports/basejail/usr/ports/print/cups-client/work/cups-1.3.10/templates'

gmake[1]: Nothing to be done for `all'.
gmake[1]: Leaving directory 
`/var/ports/basejail/usr/ports/print/cups-client/work/cups-1.3.10/templates'

===>  Installing for cups-client-1.3.10_1
===>   Generating temporary packing list
===>  Checking if print/cups-client already installed
===>   cups-client-1.3.10_1 is already installed
 You may wish to ``make deinstall'' and install this port again
 by ``make reinstall'' to upgrade it properly.
 If you really wish to overwrite the old port of print/cups-client
 without deleting it first, set the variable "FORCE_PKG_REGISTER"
 in your environment or the "make install" command line.
*** Error code 1

Stop in /basejail/usr/ports/print/cups-client.
*** Error code 1

Stop in /basejail/usr/ports/print/cups-client.
*** Error code 1

Stop in /basejail/usr/ports/print/cups-base.
*** Error code 1

Stop in /basejail/usr/ports/print/cups-base.
*** Error code 1

Stop in /basejail/usr/ports/print/cups-base.
** Command failed [exit code 1]: /usr/bin/script -qa 
/tmp/portupgrade20090510-49660-5q2d8w-0 env UPGRADE_TOOL=portupgrade 
UPGRADE_PORT=cups-base-1.3.9_3 UPGRADE_PORT_VER=1.3.9_3 make reinstall

--->  Restoring the old version
** Fix the installation problem and try again.
[Updating the pkgdb  in /var/db/pkg ... - 39 packages 
found (-0 +1) . done]

** Listing the failed packages (-:ignored / *:skipped / !:failed)
   ! print/cups-base (cups-base-1.3.9_3)   (install error)
--8<--

If I do a "uname -a", I get the following...

--8<--
FreeBSD pearl.xx.xxx 6.4-RELEASE-p4 FreeBSD 6.4-RELEASE-p4 #0: Mon 
Apr 27 19:11:59 BST 2009 
j...@watchtower.xx.xxx:/usr/obj/usr/src/sys/WATCHTOWER  i386

--8<--

I've looked in /usr/ports/UPDATING, but i'm not seeing anything regarding 
cups.


Anyone have any ideas?


Jazz 




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: how to fix "interrupt storm"

2009-05-10 Thread perryh
"Paul B. Mahol"  wrote:
> On 5/10/09, per...@pluto.rain.com  wrote:
...
> >> >> >   interrupt storm detected on "irq9:"; throttling interrupt source
> >> >> >   interrupt storm detected on "irq9:"; throttling interrupt source
> >> >> >   ad6: FAILURE - SET_MULTI status=51
> >> >> >error=4
> >> >> >   ad6: TIMEOUT - READ_DMA retrying (1 retry left) LBA=136936
> >> >> >
> >> >> > etc. etc. until I killed it with ^C ...
> >> >>
> >> >> Output of "vmstat -i"?
> >> >
> >> > $ vmstat -i
> >> > interrupt  total   rate
> >> > irq0: clk  497386851   1004
> >> > irq1: atkbd02491  0
> >> > irq3: xl0   2030  0
> >> > irq6: fdc011  0
> >> > irq7: ppbus0 ppc0  1  0
> >> > irq8: rtc   63654324128
> >> > irq9: uhci0+  166216  0
> >>
> >> uhci0 is doing strange things, what usb device are connected?
> >
> > There are no USB devices connected.  I think those must actually
> > be atapci1 interrupts, since irq9 is where dmesg reported it.
>
> Try editing /boot/device.hints lines with irq or adding similar
> lines ...

How would I go about figuring out what to add or change?

I suppose I want to move either uhci0 or atapci1 to an unused irq,
but my recollection is that I don't have unlimited choice in the
matter because the IRQ used by a particular PCI device -- or at
least the set available for assignment -- is determined by how the
motherboard is wired.

Granted it's been several years since I was into PCI at this level.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: 7.2-release and xorg

2009-05-10 Thread Chris Whitehouse

firak jotawski wrote:

hi sirs,

apologized me for disturbing the list but i really have problem, X -config 
/root/xorg.conf.new produce a black screen and die.

i attached my machine uname -a, my xorg packages installed, X -configure output 
and its' configuration file.

any helps anf hints would highly appreciated.

with best regards,
psr

_
More than messages–check out the rest of the Windows Live™.
http://www.microsoft.com/windows/windowslive/




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html

eg

# Xorg -config xorg.conf.new

Starting with Xorg 7.4 and above, this test produces a black screen 
which may make it difficult to diagnose whether X11 is working properly. 
The older behavior is still available by using the retro option:


# Xorg -config xorg.conf.new -retro


Chris
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: how to fix "interrupt storm"

2009-05-10 Thread Paul B. Mahol
On 5/10/09, per...@pluto.rain.com  wrote:
> "Paul B. Mahol"  wrote:
>> On 5/9/09, per...@pluto.rain.com  wrote:
>> > "Paul B. Mahol"  wrote:
>> >> On 5/8/09, per...@pluto.rain.com  wrote:
>> >> > What, exactly, is an "interrupt storm", and how do I fix it?
>> > ...
>> >> >   interrupt storm detected on "irq9:"; throttling interrupt source
>> >> >   interrupt storm detected on "irq9:"; throttling interrupt source
>> >> >   interrupt storm detected on "irq9:"; throttling interrupt source
>> >> >   interrupt storm detected on "irq9:"; throttling interrupt source
>> >> >   interrupt storm detected on "irq9:"; throttling interrupt source
>> >> >   ad6: FAILURE - SET_MULTI status=51
>> >> > error=4
>> >> >   ad6: TIMEOUT - READ_DMA retrying (1 retry left) LBA=136936
>> >> >
>> >> > etc. etc. until I killed it with ^C.  (Just entering "q", to cause
>> >> > more(1) to exit and presumably stop od(1) with a SIGPIPE, did not
>> >> > stop the spew of messages.)
>> >> >
>> >> > What does this indicate?  Hardware problems?  Bad configuration?
>> >> > Something else?
>> >>
>> >> Output of "vmstat -i"?
>> >
>> > $ vmstat -i
>> > interrupt  total   rate
>> > irq0: clk  497386851   1004
>> > irq1: atkbd02491  0
>> > irq3: xl0   2030  0
>> > irq6: fdc011  0
>> > irq7: ppbus0 ppc0  1  0
>> > irq8: rtc   63654324128
>> > irq9: uhci0+  166216  0
>>
>> uhci0 is doing strange things, what usb device are connected?
>
> There are no USB devices connected.  I think those must actually
> be atapci1 interrupts, since irq9 is where dmesg reported it.

Try editing /boot/device.hints lines with irq or adding similar lines ...

>
>> It could be bad configuration, bug or hardware problem.
>


-- 
Paul
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


7.0 -> 7.1 crash every two day

2009-05-10 Thread mailinglist
Dear List,

I've upgraded from source my 7.0-RELEASE to 7.1-RELEASE. It's a general
purpose server for a small company and it's clients, running web, sql, mail
and recursive dns. The machine is a Compaq ML350 G2. Version 7.0 was
running on it for a year now without any problem. After 30 of April I've
upgraded to 7.1 (I've followed the handbook) and since then nearly every
two day the machine becomes unreachable except for echorequest. If i try to
log in in the terminal it just hangs after i give my password.

I'm out of any ideas. Please feel free to ask any more info that I've
forgotten to provide. Thank You for your help in advance.

Here's the dmesg:

Copyright (c) 1992-2009 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 7.1-RELEASE-p5 #2: Fri Apr 24 18:44:13 CEST 2009
r...@lildevil.datawlan:/usr/obj/usr/src/sys/FIREWALL
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel Pentium III (996.85-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x686  Stepping = 6
 
Features=0x383f9ff
real memory  = 536854528 (511 MB)
avail memory = 511340544 (487 MB)
kbd1 at kbdmux0
ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
ACPI Warning (tbfadt-0505): Optional field "Gpe1Block" has zero address or
length:0   0/2 [20070320]
acpi0:  on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
unknown: I/O range not supported
Timecounter "ACPI-safe" frequency 3579545 Hz quality 850
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x240-0x243 on acpi0
pcib0:  on acpi0
pci_link0: apparently invalid index 0
pci0:  on pcib0
sym0: <1510d> port 0x2000-0x20ff mem
0xc6effc00-0xc6ef,0xc6efe000-0xc6efefff irq 10 at device 1.0 on pci0
sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking
sym0: [ITHREAD]
sym1: <1510d> port 0x2400-0x24ff mem
0xc6efdc00-0xc6efdfff,0xc6efc000-0xc6efcfff irq 11 at device 1.1 on pci0
sym1: No NVRAM, ID 7, Fast-40, LVD, parity checking
sym1: [ITHREAD]
fxp0:  port 0x2800-0x283f mem
0xc6efb000-0xc6efbfff,0xc6d0-0xc6df irq 15 at device 2.0 on pci0
miibus0:  on fxp0
inphy0:  PHY 1 on miibus0
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp0: Ethernet address: 00:50:8b:ee:d2:d6
fxp0: [ITHREAD]
vgapci0:  port 0x2c00-0x2cff mem
0xc500-0xc5ff,0xc6cff000-0xc6cf at device 3.0 on pci0
pci0:  at device 4.0 (no driver attached)
isab0:  at device 15.0 on pci0
isa0:  on isab0
atapci0:  port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x3000-0x300f at device 15.1 on pci0
ata0:  on atapci0
ata0: [ITHREAD]
ata1:  on atapci0
ata1: [ITHREAD]
pcib1:  on acpi0
pci3:  on pcib1
ida0:  port 0x4000-0x40ff mem
0xc6fff000-0xc6ff irq 5 at device 3.0 on pci3
ida0: [GIANT-LOCKED]
ida0: [ITHREAD]
ida0: drives=1 firm_rev=1.22
idad0:  on ida0
idad0: 34727MB (71122560 sectors), blocksize=512
acpi_tz0:  on acpi0
atkbdc0:  port 0x60,0x64 irq 1 on acpi0
atkbd0:  irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
fdc0:  port 0x3f2-0x3f5 irq 6 drq 2 on acpi0
fdc0: [FILTER]
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
sio0:  port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
sio0: type 16550A
sio0: [FILTER]
sio1:  port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
sio1: [FILTER]
cpu0:  on acpi0
pmtimer0 on isa0
orm0:  at iomem
0xc-0xc7fff,0xc8000-0xcbfff,0xe8000-0xedfff,0xee000-0xe pnpid
ORM on isa0
ppc0:  at port 0x378-0x37f irq 7 on isa0
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
ppbus0:  on ppc0
ppbus0: [ITHREAD]
plip0:  on ppbus0
plip0: WARNING: using obsoleted IFF_NEEDSGIANT flag
lpt0:  on ppbus0
lpt0: Interrupt-driven port
ppi0:  on ppbus0
ppc0: [GIANT-LOCKED]
ppc0: [ITHREAD]
sc0:  at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0:  at port 0x3c0-0x3df iomem 0xa-0xb on isa0
Timecounter "TSC" frequency 996851056 Hz quality 800
Timecounters tick every 1.000 msec
acd0: CDROM  at ata0-master PIO4
Waiting 5 seconds for SCSI devices to settle
GEOM_LABEL: Label for provider idad0s3 is msdosfs/SYSTEMCFG.
Trying to mount root from ufs:/dev/idad0s1a
WARNING: / was not properly dismounted
WARNING: /tmp was not properly dismounted
WARNING: /usr was not properly dismounted
WARNING: /usr/home was not properly dismounted
/usr/home: mount pending error: blocks 48 files 4
WARNING: /usr/home/ftp was not properly dismounted
WARNING: /var was not properly dismounted
/var: mount pending error: blocks 4 files 1

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: 4 apcupsd problems using USB to connect on FreeBSD 7.2-RELEASE

2009-05-10 Thread Frank Shute
On Sun, May 10, 2009 at 05:08:03PM +0800, Chun-fan Ivan Liao wrote:
>
> OS version: FreeBSD 7.2 RELEASE
> apcupsd version: 3.14.5
> UPS model: APC-MGE Back-UPS RS 1000VA (BR1000TW)
> UPS cable type: usb
> 
> 3 important lines in /usr/local/etc/apcupsd/apcupsd.conf:
> -
> UPSCABLE usb
> UPSTYPE usb
> DEVICE
> -
> Other lines are default.

I've got an APC SmartUPS 750 (USB on 6.4-RELEASE).

When I hacked my apcupsd.conf (sometime ago now), I put in:

DEVICE ugen0

I don't know if that's your problem i.e: you haven't specified the
DEVICE.

> 
> 
> Problem Description:
> 1.
> The APC box cannot be detected when connected to the FreeBSD system on
> system boot. (apcupsd_enable="YES" is set in /etc/rc.conf )
> 
> The associated messages in /var/log/messages:
> -
> May 10 16:08:27 aura-cosmetics apcupsd[901]: apcupsd FATAL ERROR in
> bsd-usb.c at line 735 Cannot find UPS device -- For a link to detailed
> USB trouble shooting information, please see
> .
> May 10 16:08:27 aura-cosmetics apcupsd[901]: apcupsd error shutdown completed
> -
> 
> 2.
> Continuing 1, if I unplug the connecting USB then re-plug it to the
> same port, the USB cannot be identified.
> 
> The associated message in /var/log/messages:
> -
> May 10 16:36:17 aura-cosmetics kernel: uhub0: device problem
> (TIMEOUT), disabling port 3
> -
> 
> 3.
> Contiuning 2, changing the port to plug the USB will do, and
> /var/log/messages reads:
> -
> May 10 16:41:07 aura-cosmetics root: Unknown USB device: vendor 0x051d
> product 0x0002 bus uhub1
> May 10 16:41:08 aura-cosmetics kernel: ugen0:  Conversion Back-UPS RS 1000 FW:7.g9a.D USB FW:g9a, class 0/0, rev
> 1.10/1.06, addr 2> on uhub1
> -
> 
> But when starting the apcupsd now using [apcupsd start], there is no
> "freebsd startup succeeded" message appearing in /var/log/messages.
> 
> However using [ps ax| grep apcupsd], there is the following associated
> procedure in the standard output:
> -
> 1264  ??  Ss 0:00.01 apcupsd start
> -
> 
> 4.
> The last problem continuing 3, if stopping the apcupsd now using
> [apcupsd stop], the following error messages occur in
> /var/log/messages:
> -
> May 10 16:48:11 aura-cosmetics apcupsd[1270]: Valid lock file for
> pid=1264, but not ours pid=1270
> May 10 16:48:11 aura-cosmetics apcupsd[1271]: apcupsd FATAL ERROR in
> bsd-usb.c at line 735 Cannot find UPS device -- For a link to detailed
> USB trouble shooting information, please see
> .
> May 10 16:48:11 aura-cosmetics apcupsd[1271]: Valid lock file for
> pid=1264, but not ours pid=1271
> May 10 16:48:11 aura-cosmetics apcupsd[1271]: apcupsd error shutdown completed
> -
> 
> Any help will be greatly appreciated.

Regards,

-- 

 Frank 


 Contact info: http://www.shute.org.uk/misc/contact.html 

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: how to fix "interrupt storm"

2009-05-10 Thread perryh
"Paul B. Mahol"  wrote:
> On 5/9/09, per...@pluto.rain.com  wrote:
> > "Paul B. Mahol"  wrote:
> >> On 5/8/09, per...@pluto.rain.com  wrote:
> >> > What, exactly, is an "interrupt storm", and how do I fix it?
> > ...
> >> >   interrupt storm detected on "irq9:"; throttling interrupt source
> >> >   interrupt storm detected on "irq9:"; throttling interrupt source
> >> >   interrupt storm detected on "irq9:"; throttling interrupt source
> >> >   interrupt storm detected on "irq9:"; throttling interrupt source
> >> >   interrupt storm detected on "irq9:"; throttling interrupt source
> >> >   ad6: FAILURE - SET_MULTI status=51 error=4
> >> >   ad6: TIMEOUT - READ_DMA retrying (1 retry left) LBA=136936
> >> >
> >> > etc. etc. until I killed it with ^C.  (Just entering "q", to cause
> >> > more(1) to exit and presumably stop od(1) with a SIGPIPE, did not
> >> > stop the spew of messages.)
> >> >
> >> > What does this indicate?  Hardware problems?  Bad configuration?
> >> > Something else?
> >>
> >> Output of "vmstat -i"?
> >
> > $ vmstat -i
> > interrupt  total   rate
> > irq0: clk  497386851   1004
> > irq1: atkbd02491  0
> > irq3: xl0   2030  0
> > irq6: fdc011  0
> > irq7: ppbus0 ppc0  1  0
> > irq8: rtc   63654324128
> > irq9: uhci0+  166216  0
>
> uhci0 is doing strange things, what usb device are connected?

There are no USB devices connected.  I think those must actually
be atapci1 interrupts, since irq9 is where dmesg reported it.

> It could be bad configuration, bug or hardware problem.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


FreeBSD 8.0 i386 200905 snapshot DVD does not boot

2009-05-10 Thread Saifi Khan
Hi all:

The FreeBSD 8.0 i386 200905 snapshot DVD does not boot up.

I'm on a normal Celeron 1.6GHz Presario C300TU laptop
with 160GB HDD and 2GB DDR2 RAM.

The system just whirrs up the DVD drive, the LEDs blink for a few
moments and then the installed FreeBSD 7.1 screen is presented.

I tested the DVD drive by putting in the old FreeBSD 7.1 DVD and
it works fine.

As an additional investigation i wrote another DVD with -J -R
flags (unnecessary though in my opinion) and even this DVD does
not get booted up.

The first thing i did was do a md5sum on the downloaded .ISO
image and that is fine.

Has anybody tried FreeBSD 8.0 i386 200905 DVD and could get it
to boot ? Is there something that i'm missing here ? 
Any pointers are appreciated.


thanks
Saifi.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: Building gimp without gvfs

2009-05-10 Thread Roland Smith
On Sun, May 10, 2009 at 03:00:26PM +0100, Mike Clarke wrote:
> 
> Each time gimp-app gets upgraded I lose the ability to open URI's 
> with "Open location" or by dragging images from firefox.
> 
> Apparently this is because I need to explicitly pass --without-gvfs to 
> configure [1] [2]. I was rather surprised that I needed to do this 
> since I have the gvfs port installed but it did the trick for me. What 
> I do is to edit the Makefile and add --without-gvfs to the 
> CONFIGURE_ARGS lines. The snag is that I invariably forget about this 
> by the next time the port gets upgraded and I have to sort the problem 
> out again. What could I add to /etc/make.conf to have this option added 
> to CONFIGURE_ARGS automatically?
> 
> [1] http://www.shallowsky.com/blog/gimp/index.html
> [2] http://www.gimp.org/release-notes/gimp-2.6.html

The gimp-app port Makefile should be hacked so that it adds --without-gvfs to
CONFIGURE_ARGS if the existing GVFS option is set to "no". You can try
the attached patch 'gimp-app.Makefile.diff'. If it works, you can submit
it with a PR. 

From the first link, I understand that it _could_ be that the
--without-gnomevfs currently in CONFIGURE_ARGS needs to be added to the
first part of the if-statement. If the first patch isn't sufficient,
restore the original Makefile and try the second patch
'gimp-app2.Makefile.diff'. 


Roland
-- 
R.F.Smith   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)
--- Makefile.orig	2009-05-10 17:53:17.0 +0200
+++ Makefile	2009-05-10 17:56:17.0 +0200
@@ -132,12 +132,14 @@
 CONFIGURE_ARGS+=	--without-dbus
 .endif
 
-.if defined(WITH_GVFS) || ${HAVE_GNOME:Mgvfs}!=""
+.if defined(WITH_GVFS)
 LIB_DEPENDS+=	gnome-keyring.0:${PORTSDIR}/security/gnome-keyring
 USE_GNOME+=	gvfs
 .  if ${HAVE_GNOME:Mlibgnomeui}!=""
 USE_GNOME+=	libgnomeui
 .  endif
+.else
+CONFIGURE_ARGS+=--without-gvfs
 .endif
 
 .endif
--- Makefile.orig	2009-05-10 17:53:17.0 +0200
+++ Makefile	2009-05-10 18:00:20.0 +0200
@@ -55,8 +55,7 @@
 		--disable-python \
 		--with-desktop-dir=${PREFIX}/share \
 		--docdir=${PREFIX}/share/doc/gimp \
-		--enable-default-binary \
-		--without-gnomevfs
+		--enable-default-binary
 CONFIGURE_ENV=	CPPFLAGS="-I${LOCALBASE}/include" \
 		LDFLAGS="-L${LOCALBASE}/lib" \
 		GIMP_THREAD_LIBS=${PTHREAD_LIBS}
@@ -132,12 +131,15 @@
 CONFIGURE_ARGS+=	--without-dbus
 .endif
 
-.if defined(WITH_GVFS) || ${HAVE_GNOME:Mgvfs}!=""
+.if defined(WITH_GVFS)
+CONFIGURE_ARGS+=	--without-gnomevfs
 LIB_DEPENDS+=	gnome-keyring.0:${PORTSDIR}/security/gnome-keyring
 USE_GNOME+=	gvfs
 .  if ${HAVE_GNOME:Mlibgnomeui}!=""
 USE_GNOME+=	libgnomeui
 .  endif
+.else
+CONFIGURE_ARGS+=--without-gvfs --with-gnomevfs
 .endif
 
 .endif


pgp0K8oGPxana.pgp
Description: PGP signature


Re: Problems after upgrading to xorg-7.4_1

2009-05-10 Thread Mike Clarke
On Friday 08 May 2009, Boris Samorodov wrote:

> New xorg uses hal by default.
>
> You have two options: either use hal [1] (i.e. start dbus and hald
> while booting) or not use it (then you should tweak xorg.conf).
> Either way please read recent freebsd-x11@ mail list archieves to
> understand what's up and what to do.

> [1]  
http://lists.freebsd.org/pipermail/freebsd-x11/2009-April/008185.html


Thanks for the link. I was aware that xorg now uses hal but I didn't 
realise I would need to make any configuration adjustments to hal. 
Adding the keyboard details 
to /usr/local/share/hal/fdi/policy/10osvendor/10-x11-input.fdi as 
described in the link fixed the problem. I was also able to get the 
keyboard working correctly without hal and dbus by adding 
Option "AllowEmptyInput" "off" to xorg.conf. Since hal doesn't appear 
to usefully do anything else for me I've gone for the AllowEmptyInput 
option.

I still need to fix my problem with the nv and nvidia drivers but I've 
discovered that things work OK with the vesa driver so I'll use that 
for now.

-- 
Mike Clarke
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Building gimp without gvfs

2009-05-10 Thread Mike Clarke

Each time gimp-app gets upgraded I lose the ability to open URI's 
with "Open location" or by dragging images from firefox.

Apparently this is because I need to explicitly pass --without-gvfs to 
configure [1] [2]. I was rather surprised that I needed to do this 
since I have the gvfs port installed but it did the trick for me. What 
I do is to edit the Makefile and add --without-gvfs to the 
CONFIGURE_ARGS lines. The snag is that I invariably forget about this 
by the next time the port gets upgraded and I have to sort the problem 
out again. What could I add to /etc/make.conf to have this option added 
to CONFIGURE_ARGS automatically?

[1] http://www.shallowsky.com/blog/gimp/index.html
[2] http://www.gimp.org/release-notes/gimp-2.6.html

-- 
Mike Clarke
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: Upgrading to New Kernel - Hung on Boot

2009-05-10 Thread Boris Samorodov
On Sun, 10 May 2009 09:48:04 -0400 APseudoUtopia wrote:
> On Sun, May 10, 2009 at 8:05 AM, Boris Samorodov  wrote:
> > On Sun, 10 May 2009 00:08:42 -0400 APseudoUtopia wrote:
> >
> >> I have a FreeBSD 7.0-RELEASE system. I'm trying to upgrade to 7.2,
> >> specifically the RELENG_7_2 tag.
> >
> >> I synced my sources via csup, built world, built kernel, and installed
> >> kernel. All went well. I rebooted into single user mode, and the
> >> kernel hung. The loader menu came up, but when the kernel starts
> >> loading it hangs.
> >
> >> I recovered it by dropping to a loader prompt and loading kernel.old.
> >> It booted up fine.
> >
> >> I have attached the kernel config I used to buildkernel. I'm guessing
> >> it has something to do with this.
> >
> >> In case it's relevant, the system is a dual-core Intel Xeon, with
> >> HyperThreading disabled.
> >
> > If you have a custom kernel and get any problems than the first thing to
> > do is to build GENERIC kernel and see if the problem still exists. BTW,
> > don't forget to copy your /boot/kernel.old directory to
> > /boot/kernel.good, else it will be deletted when installing a new
> > kernel.

> Ah, yes, sorry, I forgot to mention that I have GENERIC installed to
> /boot/GENERIC, and it does load perfectly fine without any problems.
> It's just the new kernel that hangs on boot.

Is it a GENERIC kernel from the new FreeBSD version?


WBR
-- 
Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone & Internet SP
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: Upgrading to New Kernel - Hung on Boot

2009-05-10 Thread APseudoUtopia
On Sun, May 10, 2009 at 8:05 AM, Boris Samorodov  wrote:
> On Sun, 10 May 2009 00:08:42 -0400 APseudoUtopia wrote:
>
>> I have a FreeBSD 7.0-RELEASE system. I'm trying to upgrade to 7.2,
>> specifically the RELENG_7_2 tag.
>
>> I synced my sources via csup, built world, built kernel, and installed
>> kernel. All went well. I rebooted into single user mode, and the
>> kernel hung. The loader menu came up, but when the kernel starts
>> loading it hangs.
>
>> I recovered it by dropping to a loader prompt and loading kernel.old.
>> It booted up fine.
>
>> I have attached the kernel config I used to buildkernel. I'm guessing
>> it has something to do with this.
>
>> In case it's relevant, the system is a dual-core Intel Xeon, with
>> HyperThreading disabled.
>
> If you have a custom kernel and get any problems than the first thing to
> do is to build GENERIC kernel and see if the problem still exists. BTW,
> don't forget to copy your /boot/kernel.old directory to
> /boot/kernel.good, else it will be deletted when installing a new
> kernel.
>
>

Ah, yes, sorry, I forgot to mention that I have GENERIC installed to
/boot/GENERIC, and it does load perfectly fine without any problems.
It's just the new kernel that hangs on boot.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: 4 apcupsd problems using USB to connect on FreeBSD 7.2-RELEASE

2009-05-10 Thread Ion-Mihai Tetcu
On Sun, 10 May 2009 17:08:03 +0800
Chun-fan Ivan Liao  wrote:

> OS version: FreeBSD 7.2 RELEASE
> apcupsd version: 3.14.5
> UPS model: APC-MGE Back-UPS RS 1000VA (BR1000TW)
> UPS cable type: usb
> 
> 3 important lines in /usr/local/etc/apcupsd/apcupsd.conf:
> -
> UPSCABLE usb
> UPSTYPE usb
> DEVICE
> -
> Other lines are default.
> 
> 
> Problem Description:
> 1.
> The APC box cannot be detected when connected to the FreeBSD system on
> system boot. (apcupsd_enable="YES" is set in /etc/rc.conf )
> 
> The associated messages in /var/log/messages:
> -
> May 10 16:08:27 aura-cosmetics apcupsd[901]: apcupsd FATAL ERROR in
> bsd-usb.c at line 735 Cannot find UPS device -- For a link to detailed
> USB trouble shooting information, please see
> .
> May 10 16:08:27 aura-cosmetics apcupsd[901]: apcupsd error shutdown
> completed -

Please post your /var/run/dmesg.boot after a roobot.
 
> 2.
> Continuing 1, if I unplug the connecting USB then re-plug it to the
> same port, the USB cannot be identified.
> 
> The associated message in /var/log/messages:
> -
> May 10 16:36:17 aura-cosmetics kernel: uhub0: device problem
> (TIMEOUT), disabling port 3
> -

I'd say we hava a problem here.

I'd be curios to know if you see the same thing with a kernel w/o usb
in it and the following klds loaded: usb.ko, ugen.ko, umass.ko



-- 
IOnut - Un^d^dregistered ;) FreeBSD "user"
  "Intellectual Property" is   nowhere near as valuable   as "Intellect"
FreeBSD committer -> ite...@freebsd.org, PGP Key ID 057E9F8B493A297B


signature.asc
Description: PGP signature


Re: Upgrading to New Kernel - Hung on Boot

2009-05-10 Thread Tim Judd
On Sun, May 10, 2009 at 6:05 AM, Boris Samorodov  wrote:

> On Sun, 10 May 2009 00:08:42 -0400 APseudoUtopia wrote:
>
> > I have a FreeBSD 7.0-RELEASE system. I'm trying to upgrade to 7.2,
> > specifically the RELENG_7_2 tag.
>
> > I synced my sources via csup, built world, built kernel, and installed
> > kernel. All went well. I rebooted into single user mode, and the
> > kernel hung. The loader menu came up, but when the kernel starts
> > loading it hangs.
>
> > I recovered it by dropping to a loader prompt and loading kernel.old.
> > It booted up fine.
>
> > I have attached the kernel config I used to buildkernel. I'm guessing
> > it has something to do with this.
>
> > In case it's relevant, the system is a dual-core Intel Xeon, with
> > HyperThreading disabled.
>
> If you have a custom kernel and get any problems than the first thing to
> do is to build GENERIC kernel and see if the problem still exists. BTW,
> don't forget to copy your /boot/kernel.old directory to
> /boot/kernel.good, else it will be deletted when installing a new
> kernel.
>
>
> WBR
>

Among the same lines, when it's convenient, when there's time, I normally
compile an updated GENERIC and store it to /boot/kernel.GENERIC

My normal custom kernel enables IPSEC and PF (among others), and if there's
time i throw a GENERIC buildkernel under the above to keep as good record.
:)

Just $.02
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: Upgrading to New Kernel - Hung on Boot

2009-05-10 Thread Boris Samorodov
On Sun, 10 May 2009 00:08:42 -0400 APseudoUtopia wrote:

> I have a FreeBSD 7.0-RELEASE system. I'm trying to upgrade to 7.2,
> specifically the RELENG_7_2 tag.

> I synced my sources via csup, built world, built kernel, and installed
> kernel. All went well. I rebooted into single user mode, and the
> kernel hung. The loader menu came up, but when the kernel starts
> loading it hangs.

> I recovered it by dropping to a loader prompt and loading kernel.old.
> It booted up fine.

> I have attached the kernel config I used to buildkernel. I'm guessing
> it has something to do with this.

> In case it's relevant, the system is a dual-core Intel Xeon, with
> HyperThreading disabled.

If you have a custom kernel and get any problems than the first thing to
do is to build GENERIC kernel and see if the problem still exists. BTW,
don't forget to copy your /boot/kernel.old directory to
/boot/kernel.good, else it will be deletted when installing a new
kernel.


WBR
-- 
Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone & Internet SP
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: how to fix "interrupt storm"

2009-05-10 Thread Paul B. Mahol
On 5/9/09, per...@pluto.rain.com  wrote:
> "Paul B. Mahol"  wrote:
>> On 5/8/09, per...@pluto.rain.com  wrote:
>> > What, exactly, is an "interrupt storm", and how do I fix it?
> ...
>> >   interrupt storm detected on "irq9:"; throttling interrupt source
>> >   interrupt storm detected on "irq9:"; throttling interrupt source
>> >   interrupt storm detected on "irq9:"; throttling interrupt source
>> >   interrupt storm detected on "irq9:"; throttling interrupt source
>> >   interrupt storm detected on "irq9:"; throttling interrupt source
>> >   ad6: FAILURE - SET_MULTI status=51 error=4
>> >   ad6: TIMEOUT - READ_DMA retrying (1 retry left) LBA=136936
>> >
>> > etc. etc. until I killed it with ^C.  (Just entering "q", to cause
>> > more(1) to exit and presumably stop od(1) with a SIGPIPE, did not
>> > stop the spew of messages.)
>> >
>> > What does this indicate?  Hardware problems?  Bad configuration?
>> > Something else?
>>
>> Output of "vmstat -i"?
>
> $ vmstat -i
> interrupt  total   rate
> irq0: clk  497386851   1004
> irq1: atkbd02491  0
> irq3: xl0   2030  0
> irq6: fdc011  0
> irq7: ppbus0 ppc0  1  0
> irq8: rtc   63654324128
> irq9: uhci0+  166216  0

uhci0 is doing strange things, what usb device are connected?

It could be bad configuration, bug or hardware problem.

> irq14: ata0   369620  0
> irq15: ata1  691  0
> Total  561582235   1133
>


-- 
Paul
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: libcups missing

2009-05-10 Thread Robert Huff

Roland Smith writes:

>  On Sun, May 10, 2009 at 09:51:25AM +0200, kenneth hatteland wrote:
>  > First of all I`d like to say thank you for putting up with all my 
>  > amateur questions. I hope I can be of use here on the list some day...:)
>  > 
>  > I had CUPS working nicely on an networked HP cp1515n from all machines 
>  > in the house. But after upgrading FreeBSD and ports to 7.2 my FreeBSD 
>  > machines states this problem when reaching login : /libexec/ld-elf.so.1 
>  > : shared object "libcups.so.2" not found, required by "cupsd"
>  > 
>  > I guess this has something either to do with cups being recently 
>  > upgraded, or I have negelcted inspecting a file when doing mergemaster 
>  > during upgrade to 7.2
>  
>  I had the same problem when upgrading recently. Rebuilding the
>  cups-client port fixed it. If you have portmaster installed you can do:
>  
>  portmaster -B -d cups-client
>  
>  If not, go to /usr/ports/print/cups-client and run 'make
>  deinstall' and 'make install clean' as root.

I ended up having to de-install both -client and -base, then
install -base.
(Mergemaster should have nothing to do with this, as it only
affects files porvided by FreeBSD proper.)


Robert Huff


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: Perl upgrade

2009-05-10 Thread Jerry
On Sat, 9 May 2009 08:31:45 -0500 (CDT)
Lars Eighner  wrote:

>On Sat, 9 May 2009, Jos Chrispijn wrote:
>
>> Lars Eighner wrote:
>>> On Sat, 9 May 2009, Jos Chrispijn wrote:
>>> 
>>> You must be new around here.
>> Yes, I am L-)
>>> The process described in UPDATING for upgrading to Perl 5.10 is
>>> relatively painless compared to previous perl upgrades.  So much
>>> stuff depends upon perl that:
>> [snip]
>>
>> Do you recommend having Perl updated or should I stay with 5.8?
>
>Unless you know there is something in 5.10 that you need now, I
>recommend waiting at least a little bit.  Let the
>gotta-have-the-newest-shiny folks take the sharp edges off.  Study the
>dependencies list from pkg_info and dependencies of any big thing you
>plan to install.  If you are going to (re-)build something big or a
>lot of little things anyway, it may make sense to upgrade perl just
>before you do that so that rebuilding the ports that depend on perl
>will kill two birds with one stone.  If such an opportunity doesn't
>arise, maybe do it anyway about the time of the first frost ---
>snuggle up in front of the blazing compiler and sip hot chocolate.

Perl-5.10 was released to the public over a year ago. Another year
transpired before it was released into the ports system. There was an
immediate problem that was corrected when the maintainer switched to
'bison' from 'YACC'. Other than that, it has performed flawlessly as
far as I can tell.

-- 
Jerry
ges...@yahoo.com

The Martian Canals were clearly the Martian's last ditch effort!


signature.asc
Description: PGP signature


4 apcupsd problems using USB to connect on FreeBSD 7.2-RELEASE

2009-05-10 Thread Chun-fan Ivan Liao
OS version: FreeBSD 7.2 RELEASE
apcupsd version: 3.14.5
UPS model: APC-MGE Back-UPS RS 1000VA (BR1000TW)
UPS cable type: usb

3 important lines in /usr/local/etc/apcupsd/apcupsd.conf:
-
UPSCABLE usb
UPSTYPE usb
DEVICE
-
Other lines are default.


Problem Description:
1.
The APC box cannot be detected when connected to the FreeBSD system on
system boot. (apcupsd_enable="YES" is set in /etc/rc.conf )

The associated messages in /var/log/messages:
-
May 10 16:08:27 aura-cosmetics apcupsd[901]: apcupsd FATAL ERROR in
bsd-usb.c at line 735 Cannot find UPS device -- For a link to detailed
USB trouble shooting information, please see
.
May 10 16:08:27 aura-cosmetics apcupsd[901]: apcupsd error shutdown completed
-

2.
Continuing 1, if I unplug the connecting USB then re-plug it to the
same port, the USB cannot be identified.

The associated message in /var/log/messages:
-
May 10 16:36:17 aura-cosmetics kernel: uhub0: device problem
(TIMEOUT), disabling port 3
-

3.
Contiuning 2, changing the port to plug the USB will do, and
/var/log/messages reads:
-
May 10 16:41:07 aura-cosmetics root: Unknown USB device: vendor 0x051d
product 0x0002 bus uhub1
May 10 16:41:08 aura-cosmetics kernel: ugen0:  on uhub1
-

But when starting the apcupsd now using [apcupsd start], there is no
"freebsd startup succeeded" message appearing in /var/log/messages.

However using [ps ax| grep apcupsd], there is the following associated
procedure in the standard output:
-
1264  ??  Ss 0:00.01 apcupsd start
-

4.
The last problem continuing 3, if stopping the apcupsd now using
[apcupsd stop], the following error messages occur in
/var/log/messages:
-
May 10 16:48:11 aura-cosmetics apcupsd[1270]: Valid lock file for
pid=1264, but not ours pid=1270
May 10 16:48:11 aura-cosmetics apcupsd[1271]: apcupsd FATAL ERROR in
bsd-usb.c at line 735 Cannot find UPS device -- For a link to detailed
USB trouble shooting information, please see
.
May 10 16:48:11 aura-cosmetics apcupsd[1271]: Valid lock file for
pid=1264, but not ours pid=1271
May 10 16:48:11 aura-cosmetics apcupsd[1271]: apcupsd error shutdown completed
-

Any help will be greatly appreciated.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: Tips & Trix: Eclipse on 7.1 STABLE and swt-gtk issue

2009-05-10 Thread Glen Barber
On Sat, May 9, 2009 at 4:34 PM, Roger Olofsson <240olofs...@telia.com> wrote:
[snip]
> Do _not_ make clean until you have made:
>  cp
> /usr/ports/java/eclipse/work/plugins/org.eclipse.swt.gtk.freebsd.x86/gtk/library/libswt*
> /usr/local/diablo-jdk1.6.0/jre/lib/i386/client/
>
> It seems like make install builds the swt-gtk:s but that the .jar somehow
> 'misses' adding them in.
>

That should automatically happen when building the port.  If your tree
is current, try contacting the port maintainer:

   cd /usr/ports/java/eclipse; make maintainer

If that fails, submit a PR:

   http://freebsd.org/send-pr.html

Regards,

-- 
Glen Barber
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: Openvpn question

2009-05-10 Thread Octavian Ionescu

Darryl Hoar wrote:

Installed Openvpn on my freebsd server.  Had to revoke a certificate
already.  The Openvpn howto guide says to add crl-verify crl.pem to the
server config script.  Is that the openvpn server config script or the
openssl config script (I self generate certificates) ?

Been googling and searching but can't find a definitive answer.

Thanks and I know this is not strictly a Freebsd question.



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"



read this,

http://openvpn.net/index.php/documentation/howto.html#revoke

you have to revoke the certificate(s) using the scripts and adding 
"crl-verify crl.pem" to the server configuration file.


first time when you add that line you have to restart the openvpn 
daemon, afterthat it will check every time the crl.pem to see if the 
certificate is revoked or not.


--
Best regards,
Octavian
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: 7.2-RELEASE Xorg Problem

2009-05-10 Thread Manolis Kiagias

Fabian Krook wrote:

I see, well i have done that in xorg.conf.new file (snice it didn't create
any xorg.conf) the ctrl + alt + backspace
doesn't seems to work even with X -config xorg.conf.new.



2009/5/9 Frank Shute 

  
There are several changes in Xorg 7.4. Please read the updated handbook 
section:


http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html

particularly section 5.4.2
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: libcups missing

2009-05-10 Thread Roland Smith
On Sun, May 10, 2009 at 09:51:25AM +0200, kenneth hatteland wrote:
> First of all I`d like to say thank you for putting up with all my 
> amateur questions. I hope I can be of use here on the list some day...:)
> 
> I had CUPS working nicely on an networked HP cp1515n from all machines 
> in the house. But after upgrading FreeBSD and ports to 7.2 my FreeBSD 
> machines states this problem when reaching login : /libexec/ld-elf.so.1 
> : shared object "libcups.so.2" not found, required by "cupsd"
> 
> I guess this has something either to do with cups being recently 
> upgraded, or I have negelcted inspecting a file when doing mergemaster 
> during upgrade to 7.2

I had the same problem when upgrading recently. Rebuilding the
cups-client port fixed it. If you have portmaster installed you can do:

portmaster -B -d cups-client

If not, go to /usr/ports/print/cups-client and run 'make deinstall' and
'make install clean' as root.

> While I am bugging you anyway, I have a problem getting my permissions 
> for use of my Packard Bell scanner with xscan not as root to stick when 
> I rebbot. It all works nicely when I chmod every time, but where and how 
> to make this stick ?

You need to set that in /etc/devfs.rules, and activate the ruleset in
/etc/rc.conf. The devfs.rules(5) manual pages explains it. Scanners are
even used as an example. :-) If you wish to give unrestricted access,
change the mode to 0666.

Roland
-- 
R.F.Smith   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)


pgp4rJgjSxfmj.pgp
Description: PGP signature


Re: isc-dhcpd server, HOSTNAME

2009-05-10 Thread Matthew Seaman

Pieter Donche wrote:

FreeBSD7 with isc-dhcp30-server.
It hands out an IP address, OK,
but the BASH environment variable HOSTNAME is not set. Why?

(A DNS server is active on the network and can succesfully be queried 
from a FreeBSD bash command (nslookup or host) to see the hostname 
associated with the IP-address)


Hostname is not one of the parameters usually requested from a DHCP server
by a Unix machine.  In fact, it's normally the other way round: the client
tells the DHCP server what it's hostname is and the DHCP server can then
inject an A record into the DNS dynamically.

However it is possible to operate in the way you want.  To tell the dhcp
server to look up names from the DNS based on the address supplied to a
host, search for the description of the 'get-lease-hostnames' flag in
the dhcpd.conf(5) man page.

To tell dhcp clients to fetch their hostname from DHCP, you need to add it
to a 'request' or 'require' block in dhclient.conf -- see dhclient.conf(5).

It's been a long time since I ran a setup anything like that, so I cannot
recall if that was all that was required, or if it was also necessary to
write a small dhclient-script(8) to actually set the hostname. 


Another alternative is to use a dhclient-script to take the IP number
allocated by the DHCP server, look up the corresponding address and then
set that as the hostname.

The bash HOSTNAME environment variable will be set from the output of the
hostname(1) command, which is usually set from the hostname variable in
/etc/rc.conf or from the output of '/bin/kenv dhcp.host-name' if that 
is set. Otherwise it uses a default hostname of 'amnesiac'. 


Cheers,

Matthew

--
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
 Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
 Kent, CT11 9PW



signature.asc
Description: OpenPGP digital signature


libcups missing

2009-05-10 Thread kenneth hatteland
First of all I`d like to say thank you for putting up with all my 
amateur questions. I hope I can be of use here on the list some day...:)


I had CUPS working nicely on an networked HP cp1515n from all machines 
in the house. But after upgrading FreeBSD and ports to 7.2 my FreeBSD 
machines states this problem when reaching login : /libexec/ld-elf.so.1 
: shared object "libcups.so.2" not found, required by "cupsd"


I guess this has something either to do with cups being recently 
upgraded, or I have negelcted inspecting a file when doing mergemaster 
during upgrade to 7.2


Googling and reading the handbook etc haven`t enlightened me so far

Anyone have an idea or a know a online source that can help ?

While I am bugging you anyway, I have a problem getting my permissions 
for use of my Packard Bell scanner with xscan not as root to stick when 
I rebbot. It all works nicely when I chmod every time, but where and how 
to make this stick ?


Blessed be

kenneth, Norway
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"