Hi,
i just forgot to add following output from FreeBSD 8.3:
# atacontrol status ar0
ar0: ATA RAID1 status: READY
subdisks:
0 ad4 ONLINE
1 ad6 ONLINE
Thanks,
Bosko
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/
Hi Michael,
thank you for your response.
> So it's not an LSI MegaRAID, but an Intel Controller?
It is LSI MegaRAID chip but connected to Intel's I/O Controller Hub
(southbridge). On FreeBSD 8.3 gmirror is not configured:
# gmirror list
gmirror: Command 'list' not available.
# gmirror status
gm
On 07/10/2012 10:51, Wojciech Puchar wrote:
quote from:
http://serverfault.com/questions/275875/raid-bus-controller-intel-corporation-82801jir-ich10r-sata-raid-controller
"ICH10R-based RAID controllers are so called fake- or software-RAID
controllers, the OS needs to do all the work."
It is
quote from:
http://serverfault.com/questions/275875/raid-bus-controller-intel-corporation-82801jir-ich10r-sata-raid-controller
"ICH10R-based RAID controllers are so called fake- or software-RAID
controllers, the OS needs to do all the work."
It is always better to use gmirror instead of "hard
Am 09.07.2012, 16:31 Uhr, schrieb Bosko Radivojevic
:
Hi all!
I have a problem installing FreeBSD 9.0 on Fujitsu Primergy RX200 S5
server with LSI MegaRAID SATA controller (two SATA HDDs in RAID1
array). When booted from a CD, FreeBSD doesn't recognize RAID Array,
it recognizes HDDs
Hi all!
I have a problem installing FreeBSD 9.0 on Fujitsu Primergy RX200 S5
server with LSI MegaRAID SATA controller (two SATA HDDs in RAID1
array). When booted from a CD, FreeBSD doesn't recognize RAID Array,
it recognizes HDDs only (ad4 & ad6). On the same server, FreeBSD 8.3
ins
Hi,
On Saturday 23 June 2012 15:33:45 RetspaN Code wrote:
> also this
>
> 14417 ?? Ss 0:00.02 /bin/sh - /usr/sbin/periodic daily
> 14425 ?? I 0:00.04 /bin/sh - /usr/sbin/periodic daily
as long it is online, there is a very, very low chance to get anything done.
And even when it
Hi,
On Saturday 23 June 2012 14:44:18 RetspaN Code wrote:
>
> I did own now by root:wheel but now i'm under on ddos attack. :( but still
> not yet done the exploit not yet remove.
>
> too lag my server due to ddos attack.
>
the server must be off-line if you want to have the tiniest chance to
t access and might have left the company since then?
Erich
>
> Thanks! Erich
>
> Regards,
>
> FredFoxs
>
>
>
> From: Erich Dollansky
> To: RetspaN Code ; freebsd-questions@freebsd.org
> Sent: Saturday, June 23, 2012 3:02
Hi,
On Saturday 23 June 2012 13:41:24 RetspaN Code wrote:
> 49129472 drwxr-x--x 20 root tonyx 512 Jun 5 13:00 ..
who belongs to this group?
> 49134586 -rw-r--r--1 root wheel6206 Jun 13 2010 COPYRIGHT
> 49134587 -rw-r--r--1 root wheel 442 Jun 13 2010 LOCKS
> 49134588 -
Hi,
On Saturday 23 June 2012 13:24:02 RetspaN Code wrote:
> Hello,
>
> Intruder already block, but my problem is the intruder before they get
> block they load their exploit file to my machine that cause of my machine
> /usr/src directory is set to read only i can't uploa
Hi,
On Saturday 23 June 2012 12:59:26 RetspaN Code wrote:
> Hello,
>
> Yes I'm still have a root access... that is why i right you a letter for a
> help regarding to this problem on my server which is running freebsd 8.1
> p1 release... i did paste the error that i encounter
Hi,
On Saturday 23 June 2012 09:47:35 RetspaN Code wrote:
> Hello,
>
> Since you all the responsible of freebsd source and updates... Is there
you are the only one responsible for the break in. So, what was the problem?
> anyway to fix my server without re install the system?
&g
g_em0=" inet 192.168.1.10 netmask 255.255.255.0"
> ifconfig_em1=" inet 192.168.2.1 netmask 255.255.255.0"
> defaultrouter="192.168.1.1"
> gateway_enable="YES"
>
>
> now after reboot the problem still the same.
>
> ping -S 192.1
Thank you, Mark!
All work!
-
Вы писали 22 июня 2012 г., 16:31:39:
> On Fri, 22 Jun 2012 08:10:43 -0500, UNIX developer @ Google.com
> wrote:
>> now after reboot the problem still the same.
>> ping -S 192.168.2.1 192.168.1.1
>> PING 192.168.1.1 (192.168.1
1x Quad-Core i5-2500 3.3GHz, 6M Cache
> 16GB DDR3
> 2x 500GB SATAII
>
> then ask from my COLOCATION to install FreeBSD 8.2 or 8.3 with RAID 1, after
> many times of fail in installation from colocation they said that we have
> problem with RAID 1.we suggest them to play with diff
On Thu, 21 Jun 2012 15:59:36 -0500, UNIX developer @ Google.com
wrote:
/etc/rc.conf
ifconfig_em0=" inet 192.168.1.10 netmask 255.255.255.0"
ifconfig_em1=" inet 192.168.2.1 netmask 255.255.255.0"
defaultrouter="192.168.1.1"
gateway_enable="YES"
static_routes="clnet"
route_clnet="-net 192.168.2
Hi!
I have problem with routing on FreeBSD.
I have ESXi 5 host. In there is 5 VMs and one of them is a BSD.
I need create router on BSD.
I try to setting up it with this manual:
http://www.freebsd.org/doc/handbook/network-routing.html
but problem is still the same...
I cant ping external network
I have an Intel Wifi Link 1000 BGN NIC that
I'm having trouble getting to work. I have
FreeBSD 8.3 installed. I looked in the NOTES file under
/usr/src/sys/conf
for the driver and did not see it listed. It is PCI.
I have tried to configure the settings
via the sysinstall command post configur
I have another problem . >_<
Sometimes , I cannot connect to server ( in trust zone ) from untrust.
Even I turn off the firewall, the situation still come up.
But, when the state appears, I ping some ip from the server ( in trust
) to a host ( in untrust ).
Suddenly, I connect
> 2012/6/20 Erik Osterholm :
>
>
> Try adding logging to the rules, enable pflog, and see which rule is blocking.
>
> Erik
hmm
I discovered some things from log.
Even if the packet hit a rule ( pass in quick on bridge0 ) , the
packet still is blocked by block out rule ( block out on brid
I have some trouble with pf on freebsd bridge.
Network topology:
( untrust ) -- { em0 , bridge0 , em1 } -- ( trust )
Bridge Network: 10.1.1.0/24
bridge0 IP: 10.1.1.1 ( freebsd's ip )
default gw: 10.1.1.254 ( in untrust area )
server: 10.1.1.101 ~ 200 ( in trust area )
pf.conf on freebsd
serv1
I tried to update an amd64 FreeBSD 9.0 p0 system via freebsd-update tonight.
It fetched everything fine. However, the install just hung after about 10
minutes. The 2 sh processes are basically doing nothing. Not consuming any
processor time and not doing any I/O. I killed it and tried anoth
e:
>
>> On 17/06/2012 11:45, Doug Hardie wrote:
>>> I am using spamd on several systems and started encountering a problem
>>> awhile ago with FreeBSD 7.2 servers, but let it go since I am in the
>>> process of upgrading the servers. However, I now am en
On 17 June 2012, at 06:29, Matthew Seaman wrote:
> On 17/06/2012 11:45, Doug Hardie wrote:
>> I am using spamd on several systems and started encountering a problem
>> awhile ago with FreeBSD 7.2 servers, but let it go since I am in the process
>> of upgrading the server
On 17/06/2012 11:45, Doug Hardie wrote:
> I am using spamd on several systems and started encountering a problem awhile
> ago with FreeBSD 7.2 servers, but let it go since I am in the process of
> upgrading the servers. However, I now am encountering the same issue on
> Free
I am using spamd on several systems and started encountering a problem awhile
ago with FreeBSD 7.2 servers, but let it go since I am in the process of
upgrading the servers. However, I now am encountering the same issue on
FreeBSD 9.0 with spamlogd. It never reads pflog0. pflogd reads the
Hi,
Hopefully a simple problem with a simple solution. Trying to update a server
using freebsd-update, but when I try I get the following:
# freebsd-update fetch install
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 8.3-RELEASE from update5.FreeBSD.org
On 08/06/2012 06:59, Matthew Seaman wrote:
Probably. The good news is that once you've got it running the IPv6
support in FreeBSD is rock solid and works like a charm.
It turns out that PF was being too helpful and trying to NAT for both
IPv4 and IPv6 - adding 'inet' to the "nat on $ext_if..
"
dhcpd_chroot_enable="YES"
dhcpd6_chroot_enable="YES"
dhcpd_devfs_enable="YES"
dhcpd6_devfs_enable="YES"
dhcpd_rootdir="/var/db/dhcpd"
dhcpd6_rootdir="/var/db/dhcpd6"
rtadvd_enable="NO"
rtadvd_interfaces="em0"
I've tried configuring a machine with a static configuration, bypassing
any issues with rtadvd/dhcpd6 so I'm fairly sure the problem is on the
router.
--
Bruce Cran
___
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"
e em0 and tun0 public addresses in different subnets
(tun0 is assigned the address via ppp.linkup).
I've added all the IPv6 settings to rc.conf (ipv6_gateway_enable,
ipv6_network_interfaces, rtadvd_enable etc.) and I can ping IPv6 sites
from the router.
The problem is that rtadvd
ss via ppp.linkup).
> I've added all the IPv6 settings to rc.conf (ipv6_gateway_enable,
> ipv6_network_interfaces, rtadvd_enable etc.) and I can ping IPv6 sites
> from the router.
rtadvd can be limited to operate on a specific interface. Try setting
rtadvd_interfaces="em0"
p.linkup).
> I've added all the IPv6 settings to rc.conf (ipv6_gateway_enable,
> ipv6_network_interfaces, rtadvd_enable etc.) and I can ping IPv6 sites
> from the router.
>
> The problem is that rtadvd continues advertising the default gateway as
> tun0's link-local
to rc.conf (ipv6_gateway_enable,
ipv6_network_interfaces, rtadvd_enable etc.) and I can ping IPv6 sites
from the router.
The problem is that rtadvd continues advertising the default gateway as
tun0's link-local address - and pinging from a machine on the network
results in "cannot f
3/eprn -o bin/pcl3opts contrib/pcl3/src/pcl3opts.c
contrib/pcl3/src/pclscan.c contrib/pcl3/eprn/mediasize.c contrib/pcl3/src/p
clsize.c
test: -eq: unexpected operator
In file included from contrib/pcl3/eprn/mediasize.c:26:
./base/std.h:23:18: error: arch.h: No such file or directo
On Tue, May 22, 2012 at 6:31 PM, Chuck Swiger wrote:
> On May 22, 2012, at 6:05 AM, Odhiambo Washington wrote:
> > Can someone please tell me how to resolve the following multiplicity of
> > libraries, to ensure I only compile applications against a particular
> > library. I believe this emanates
On May 22, 2012, at 6:05 AM, Odhiambo Washington wrote:
> Can someone please tell me how to resolve the following multiplicity of
> libraries, to ensure I only compile applications against a particular
> library. I believe this emanates from my installing of openssl from the
> ports.
You could run
Hi,
Can someone please tell me how to resolve the following multiplicity of
libraries, to ensure I only compile applications against a particular
library. I believe this emanates from my installing of openssl from the
ports.
FreeBSD 8.3-STABLE i386:
(15:58:10 <~>) 0 $ ls -al /usr/lib/libcrypt*
On Sat, 19 May 2012 11:18:37 -0500
CyberLeo Kitsana wrote:
> On 05/19/2012 03:29 AM, Andriy Babiy wrote:
> >>> "Makefile.inc1", line 160: CPUTYPE global should be set with ?=.
> ...
> > In make.conf I have CPUTYPE=nocona
>
> As it says, you need CPUTYPE?=nocona instead of CPUTYPE=nocona in
> /et
update (major version number), you should
always reinstall (update) your applications. You can avoid it
by installing the compat-Nx-i386 or compat-Nx-amd64 ports (where
N is the previously used major version number).
You've found many advices on how to do that already from the
list.
The prob
On 19/05/2012 21:09, Polytropon wrote:
>> Sorry i cant paste logs, bsd is running on another machine.
> You can use SSH to log into the BSD machine and cut text from
> the session. :-)
Or just run:
% script /tmp/session.log
Do all your updating tasks, then type 'exit' when done, and you'll g
ber), you should
always reinstall (update) your applications. You can avoid it
by installing the compat-Nx-i386 or compat-Nx-amd64 ports (where
N is the previously used major version number).
You've found many advices on how to do that already from the
list.
> The problem i had was that
On 19/05/2012 20:08, Beastie-Boy wrote:
> I forgot to tell that i recently upgraded from 8.1 to 9.0-RELEASE.
> That excplains maybe why i had obsolete/old packages/ports on my disk.
Ahah! That is exactly the situation where you do want to remove all your
installed ports and rebuild them.
On Sat, 19 May 2012 19:43:09 +0100, RW wrote:
> On Sat, 19 May 2012 11:08:19 -0700 (PDT)
> Beastie-Boy wrote:
>
> > Ok, many thanks for your replies.
> > I forgot to tell that i recently upgraded from 8.1 to 9.0-RELEASE.
> > That excplains maybe why i had obsolete/old packages/ports on my disk.
>
On Sat, 19 May 2012 11:08:19 -0700 (PDT)
Beastie-Boy wrote:
> Ok, many thanks for your replies.
> I forgot to tell that i recently upgraded from 8.1 to 9.0-RELEASE.
> That excplains maybe why i had obsolete/old packages/ports on my disk.
When you cross a major OS release boundary, you need to fo
Ok, many thanks for your replies.
I forgot to tell that i recently upgraded from 8.1 to 9.0-RELEASE.
That excplains maybe why i had obsolete/old packages/ports on my disk.
The problem i had was that gdm, gnome didnt start after the upgrade.
So i tried to build the gnome and gdm thing again via
On 05/19/2012 09:18 AM, CyberLeo Kitsana wrote:
As it says, you need CPUTYPE?=nocona instead of CPUTYPE=nocona in
/etc/make.conf or /etc/src.conf; otherwise the build process chokes
while building the 32-bit compatibility stuff, since it cannot override
your 64-bit CPU selection with a 32-bit one
On 05/19/2012 03:29 AM, Andriy Babiy wrote:
>>> "Makefile.inc1", line 160: CPUTYPE global should be set with ?=.
...
> In make.conf I have CPUTYPE=nocona
As it says, you need CPUTYPE?=nocona instead of CPUTYPE=nocona in
/etc/make.conf or /etc/src.conf; otherwise the build process chokes
while buil
On 5/19/2012 3:11 AM, Edward M wrote:
Try 'env -i make buildworld' after cleaning obj.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubsc
On 19/05/2012 16:07, Warren Block wrote:
> The -f is probably not needed. I've done this rarely enough to not
> recall, but -a should sort everything in the right order so dependencies
> are uninstalled in order.
I find that 'pkg_delete -af' gives more reliable results. Agreed, it
should not be
On Sat, 19 May 2012, Matthew Seaman wrote:
That's a bit drastic and pretty much something you'ld never actually
want to do in normal usage. However, for completeness' sake:
# pkg_delete -af
will remove all installed ports. After doing that there should be
hardly anything left under /usr/lo
The way it works, you shouldn't get any old ports left
cluttering up /usr/ports unless things have gone very wrong. In which
case portsnap would be emitting all sorts of error messages and the fact
that there was a problem would be obvious.
> I tried to compile a programm and it complain
, did the fetch and extract again, problem
persists still.
Yes, i searched all the forums and read a lot about managing ports and
packages.
Right now i am stuck.
So, how do i delete really *all* ports and *all* packages at once?
Is it possible with doing a fectch and extract having the latest ports?
I
On 05/18/2012 09:17 PM, Andriy Babiy wrote:
Makefile.inc1", line 160: CPUTYPE global should be set with ?=
I think the problem is the wrong cpu type define. . I took a
glance at the code in the makefile.inc1 to see what would set that
error off and i found this in the makefile
my head on this one:-)
> However to my understanding it seems, it is trying to build 32
> bit on a amd 64bit install?
>
Since 7.0 I upgraded this machine via buildworld. It was always amd64.
As you see in uname output, I upgraded it from 8.X to 9.0 with no
problem. Time/date is in syn
On 05/18/2012 09:17 PM, Andriy Babiy wrote:
FreeBSD myhost 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Fri Mar 23 20:00:59
PDT 2012 root@myhost:/usr/obj/usr/src/sys/GENERIC amd64
root#cd /usr/obj
root#chflags -R noschg *
root#rm -rf *
root#make buildworld
...
cd /usr/src; MACHINE=i386 MACHINE_ARCH=
Hi list:
root#uname -a
FreeBSD myhost 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Fri Mar 23 20:00:59
PDT 2012 root@myhost:/usr/obj/usr/src/sys/GENERIC amd64
root#cd /usr/obj
root#chflags -R noschg *
root#rm -rf *
root#make buildworld
...
cd /usr/src; MACHINE=i386 MACHINE_ARCH=i386 MACHINE_CPU="i68
On 16/05/2012 11:04, James Edwards wrote:
I use mutt (1.5.21) with msmtp (1.4.28) as MDA. Usually, everything goes
smoothly, but every once in a while I lose network connectivity when
sending email (I don't recall whether there is a correlation between
this problem and my trying to send n
On 16/05/2012 11:04, James Edwards wrote:
I use mutt (1.5.21) with msmtp (1.4.28) as MDA. Usually, everything goes
smoothly, but every once in a while I lose network connectivity when
sending email (I don't recall whether there is a correlation between
this problem and my trying to send n
> I use mutt (1.5.21) with msmtp (1.4.28) as MDA. Usually, everything goes
> smoothly, but every once in a while I lose network connectivity when
> sending email (I don't recall whether there is a correlation between
> this problem and my trying to send not-so-big but yet
I use mutt (1.5.21) with msmtp (1.4.28) as MDA. Usually, everything goes
smoothly, but every once in a while I lose network connectivity when
sending email (I don't recall whether there is a correlation between
this problem and my trying to send not-so-big but yet around 1mb files).
Basi
. Only the last release have the problem described in the
following text.
For the first time I got a problem after a kernel is recompiled. Below one
can see that what now, after a recompilation should be FreeBSD 8.3-RELEASE
#1 still is #0, and with a faulty date/time stamp.
The number after the
nSSL 0.9.8q 2 Dec 2010
>
>openssl version
>OpenSSL 1.0.1a 19 Apr 2012
>
>It appears I have two different versions of OpenSSL installed. I
>deliberately installed the newer version and placed this in the
>"/etc/make.conf" file:
>
>WITH_OPENSSL_PORT=yes
>
>I
two different versions of OpenSSL installed. I
deliberately installed the newer version and placed this in the
"/etc/make.conf" file:
WITH_OPENSSL_PORT=yes
I have no idea what happened or how to correct this problem. I tried
rebuilding Perl and the two ports listed in the "sendemail
On 10 May 2012 08:14, Carmel wrote:
> I am continuing to have a problem with certain "flash" videos not
> displaying with Firefox on FreeBSD-8.3.
>
> I have discovered numerous messages like this in the system log file.
>
> May 10 07:59:04 scorpio kernel: linux: pid 9
I am continuing to have a problem with certain "flash" videos not
displaying with Firefox on FreeBSD-8.3.
I have discovered numerous messages like this in the system log file.
May 10 07:59:04 scorpio kernel: linux: pid 96942 (npviewer.bin): syscall pipe2
not implemented
I have also
be initialized until the update to FreeBSD-8.3. I am not sure
if this should be considered a BUG or what. It doesn't appear that any
of the software that requires it to be installed also require it to be
running at boot-up. I don't even know who, if anyone, I should report
this behavior t
On Sun, 6 May 2012 04:25:52 -0600 (MDT)
Warren Block articulated:
>On Sun, 6 May 2012, Matthew Seaman wrote:
>> On 05/05/2012 19:30, Carmel wrote:
>
>>> All I guess I really have to get corrected is the "dhclient" thing,
>>> assuming it is a real problem an
On Sun, 6 May 2012, Matthew Seaman wrote:
On 05/05/2012 19:30, Carmel wrote:
All I guess I really have to get corrected is the "dhclient" thing,
assuming it is a real problem and just not some useless noise.
The 'dhclient already running' message is untidy, but harmless.
n't try starting up
webcamd any more.
> All I guess I really have to get corrected is the "dhclient" thing,
> assuming it is a real problem and just not some useless noise.
The 'dhclient already running' message is untidy, but harmless. It's
the rc system refus
sing FreeBSD-8.2. I am still
confused as to why "devd" wants to start "webcamd"
All I guess I really have to get corrected is the "dhclient" thing,
assuming it is a real problem and just not some useless noise.
--
Carmel ✌
carmel...@hotmail.com
_
On 25/04/2012 22:54, Taras Marusin wrote:
Hello!
How can I track the solution to this problem?
T.Marusin
-- Forwarded message --
From:
Date: 2012/4/21
Subject: Re: bin/167156: looping process mksnap_ffs when run in a chroot
environment named. CPU 100%
To: Taras Marusin
Thank
when playing movie. In linux there was no problem, so it cannot
be the problem of HRT music streamer.
any ideas?
--
*Kim*
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any
Hello!
How can I track the solution to this problem?
T.Marusin
-- Forwarded message --
From:
Date: 2012/4/21
Subject: Re: bin/167156: looping process mksnap_ffs when run in a chroot
environment named. CPU 100%
To: Taras Marusin
Thank you very much for your problem report.
It
subclass = ethernet
>>>>>>>
>>>>>>> ifconfig_vlan100="inet 192.168.0.1 netmask 255.255.255.0 vlan 100
>>>>>>> vlandev igb2" #nALL
>>>>>>> ifconfig_vlan101="inet 192.168.1.1 netmask 255.255.255.0 vlan 10
#n1 p23
>>>>>> ifconfig_vlan103="inet 192.168.3.1 netmask 255.255.255.0 vlan 103
>>>>>> vlandev igb2" #n3 p22
>>>>>> ifconfig_vlan104="inet 192.168.4.1 netmask 255.255.255.0 vlan 104
>>>>>> vlandev igb2"
Здравствуйте, Damien.
Вы писали 13 апреля 2012 г., 4:42:31:
DF> Yes, I suggest you try with "-vlanhwtag" as well.
DF> If that stops your unwanted reboots, you may want to remove it and see
DF> if the situation changes.
igb0: flags=8843 metric 0 mtu 1500
options=400b8
ether a0:36:
; #n7,9 p21
>>>>> ifconfig_vlan105="inet 192.168.5.1 netmask 255.255.255.0 vlan 105
>>>>> vlandev igb2" #n11 p20
>>>>> ifconfig_vlan106="inet 192.168.6.1 netmask 255.255.255.0 vlan 106
>>>>> vlandev igb2" #n13 p19
68.7.1 netmask 255.255.255.0 vlan 107
>>>> vlandev igb2" #n223 p18
>>>> ifconfig_vlan108="inet 192.168.8.1 netmask 255.255.255.0 vlan 108
>>>> vlandev igb2" #n225 p17
>>>> ifconfig_vlan109="inet 192.168.9.1 netmask 2
>> ifconfig_vlan109="inet 192.168.9.1 netmask 255.255.255.0 vlan 109
>>> vlandev igb2" #n221 p16
>>> ifconfig_vlan110="inet 192.168.10.1 netmask 255.255.255.0 vlan 110
>>> vlandev igb2" #n229 p15
>>> ifconfig_vlan111="inet 192.
On 04/12/12 02:28, Bernt Hansson wrote:
2012-04-10 16:50, Da Rock skrev:
It gives a black screen. Vesa or not.
Is that with the retro option?
No it was not. Now I have fixed it, wife on my back so I had to fix it
quickly. Pkg_delete \* cd x11-wm/xfce4 so now it starts up without
errors.
sk 255.255.255.0 vlan 110 vlandev
>> igb2" #n229 p15
>> ifconfig_vlan111="inet 192.168.11.1 netmask 255.255.255.0 vlan 111 vlandev
>> igb2" #n233 p14
>> ifconfig_vlan112="inet 192.168.12.1 netmask 255.255.255.0 vlan 112 vlandev
>> igb2" #n
09:22 kernel:
>>>
>>> running manually:
>>> # fsck -y /dev/ad8s1e
>>> ** /dev/ad8s1e (NO WRITE)
>
> EG> You cannot run fsck on mounted filesystem, unmount it first.
> Why not? fsck can do its job at background, on mounted FS.
It is run in special mod
WRITE)
EG> You cannot run fsck on mounted filesystem, unmount it first.
Why not? fsck can do its job at background, on mounted FS.
So I also can run it on mounted FS. in this case (as I have showed)
it do not find any errors.
In any case I have run fsck on this FS when it was dismounted.
Ther
2012-04-10 16:50, Da Rock skrev:
It gives a black screen. Vesa or not.
Is that with the retro option?
No it was not. Now I have fixed it, wife on my back so I had to fix it
quickly. Pkg_delete \* cd x11-wm/xfce4 so now it starts up without errors.
Thank you all for your input.
__
ed using real GPUs as Radeon and Nvidia in
laptops :)
If I remember correctly, I had trouble with an Intel 845 (your exact
chipset- pciconf showed the same as yours) a while back. I was able to
use vesa, but then it broke. Mind you the whole laptop had started to go
(usb, mouse, etc) so I had a
sk 255.255.255.0 vlan 112 vlandev
igb2" #n231 p13
ifconfig_vlan113="inet 192.168.13.1 netmask 255.255.255.0 vlan 113 vlandev
igb2" #n237 p12
ifconfig_vlan114="inet 192.168.14.1 netmask 255.255.255.0 vlan 114 vlandev
igb2" #n424 p11
ifconfig_vlan115="inet 192.168.15.1 net
10.04.2012 01:36, Коньков Евгений пишет:
> Hi.
>
> Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY, CANNOT RUN FAST
> FSCK
> Apr 9 19:51:58 fsck:
> Apr 9 19:51:58 fsck:
> Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY; RUN fsck
> MANUALLY.
> Apr 9 19:51:58 fsck: /dev/
dev
igb2" #n237 p12
ifconfig_vlan114="inet 192.168.14.1 netmask 255.255.255.0 vlan 114 vlandev
igb2" #n424 p11
ifconfig_vlan115="inet 192.168.15.1 netmask 255.255.255.0 vlan 115 vlandev
igb2" #
PAP> Nothing logged in /var/log/* or crashes that exist in /var/crash
Nothing logged in /var/log/* or crashes that exist in /var/crash would indicate
to me some sort of hardware related problem.
Have you tested your hardware lately and know that it is in operational order?
~Paul
On Mon, Apr 09, 2012 at 09:36:54PM +0300, ??? ??? wrote:
> Hi.
>
>
- empty, in /var/log/messages there is no any messages before crash.
Can any help to fix problem?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-ques
On 04/10/12 00:36, Warren Block wrote:
On Mon, 9 Apr 2012, Da Rock wrote:
On 04/09/12 21:38, Bernt Hansson wrote:
4. What does Xorg -configure produce?
No idea, haven't tried it. Using HAL.
Given your previous answers, I'd say you _have_ to run it. Then the
last option I offered _will_ wo
On Mon, 9 Apr 2012, Da Rock wrote:
On 04/09/12 21:38, Bernt Hansson wrote:
4. What does Xorg -configure produce?
No idea, haven't tried it. Using HAL.
Given your previous answers, I'd say you _have_ to run it. Then the last
option I offered _will_ work. You need to force it to use vesa and
On 04/09/12 21:38, Bernt Hansson wrote:
2012-04-09 13:03, Da Rock skrev:
On 04/09/12 20:38, Bernt Hansson wrote:
Hello list.
When I try to start X I'm getting this error
Yep. This one will be fun... :)
X.Org X Server 1.7.7
Release Date: 2010-05-04
X Protocol Version 11, Revision 0
Build Op
On 04/09/12 20:38, Bernt Hansson wrote:
Hello list.
When I try to start X I'm getting this error
Yep. This one will be fun... :)
X.Org X Server 1.7.7
Release Date: 2010-05-04
X Protocol Version 11, Revision 0
Build Operating System: FreeBSD 8.2-RELEASE i386
Current Operating System: FreeBSD
On Mon, Apr 09, 2012 at 12:38:45PM +0200, Bernt Hansson wrote:
Hi Bernt,
> Hello list.
>
> When I try to start X I'm getting this error
>
> X.Org X Server 1.7.7
> Release Date: 2010-05-04
> X Protocol Version 11, Revision 0
> Build Operating System: FreeBSD 8.2-RELEASE i386
> Current Operating Sy
needs to be up to
date.
I have decided to recompile bind in the latest version and I am running into a
problem which is caused by bind port not following the FreeBSD requisites and
trying to install things in /usr/include/isc
making all in /s/portbuild/usr/ports/dns/bind98/work/bind-9.8.2/lib/isc
On 05/04/2012 18:24, bsd wrote:
> I have decided to recompile bind in the latest version and I am
> running into a problem which is caused by bind port not following the
> FreeBSD requisites and trying to install things in /usr/include/isc
What on earth gives you the idea that dns/bind9
decided to recompile bind in the latest version and I am running into a
problem which is caused by bind port not following the FreeBSD requisites and
trying to install things in /usr/include/isc
making all in /s/portbuild/usr/ports/dns/bind98/work/bind-9.8.2/lib/isc/x86_32
making all in
/s
The format of named files isn't quite as free-form as you apparently
think. :-) Compare one of mine:
$TTL 1H
@ IN SOA ns3.radel.com. jon.radel.com. (
2010100400 ; serial
1H ; refresh
401 - 500 of 10751 matches
Mail list logo
