Maxtor STM3250310AS is recognized as SATA150 instead of SATA300

2008-09-17 Thread Roman Serbski
Hi list-

I'm running FreeBSD 7.1-PRERELEASE (cvsuped and built yesterday) on
Asus P5KPL-VM with Maxtor STM3250310AS (250GB) for some reason being
recognized as SATA150. According to P5KPL-VM specs
(http://www.asus.com/products.aspx?l1=3l2=11l3=563l4=0model=1772modelmenu=2)
it does support 3Gb/s, so does STM3250310AS
(http://www.seagate.com/staticfiles/support/disc/manuals/maxtor/100451230c.pdf).
Maxtor hard drive came with jumper but removing it didn't help -- I
still see SATA150 in dmesg output. I also updated Asus BIOS to the
latest version and replaced SATA cables -- none of this helped.

Here is more detailed information:

%dmesg | grep SATA
atapci1: Intel ICH7 SATA300 controller port
0xc400-0xc407,0xc080-0xc083,0xc000-0xc007,0xbc00-0xbc03,0xb880-0xb88f
irq 19 at device 31.2 on pci0
ad4: 238475MB MAXTOR STM3250310AS 3.AAC at ata2-master SATA150

%atacontrol cap ad4

Protocol  Serial ATA II
device model  MAXTOR STM3250310AS
serial number 9RY1LHWX
firmware revision 3.AAC
cylinders 16383
heads 16
sectors/track 63
lba supported 268435455 sectors
lba48 supported   488397168 sectors
dma supported
overlap not supported

Feature  Support  EnableValue   Vendor
write cacheyes  yes
read ahead yes  yes
Native Command Queuing (NCQ)   yes   -  31/0x1F
Tagged Command Queuing (TCQ)   no   no  31/0x1F
SMART  yes  yes
microcode download yes  yes
security   yes  no
power management   yes  yes
advanced power management  no   no  65278/0xFEFE
automatic acoustic management  no   no  0/0x00  208/0xD0

%pciconf -lv
[EMAIL PROTECTED]:0:31:2:class=0x01018f card=0x81791043 chip=0x27c08086
rev=0x01 hdr=0x00
vendor = 'Intel Corporation'
device = '82801GB/GR/GH (ICH7 Family) Serial ATA Storage Controller'
class  = mass storage
subclass   = ATA

There were couple of similar threads and one guy reported that he was
able to get SATA300 by playing with AHCI settings in BIOS, but I don't
really see anything related to AHCI in my BIOS.

Any hints would be greatly appreciated.

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


Re: Help with IP Filter 4.1.8

2006-03-10 Thread Roman Serbski
On 3/10/06, Giorgos Keramidas [EMAIL PROTECTED] wrote:
 Here's your problem then.

 This is *NOT* the way to install IP Filter on a FreeBSD system.
 You should only upgrade parts of the base system using the process
 documented and recommended in ``/usr/src/UPDATING''.

 Start over with a clean /usr/src and /usr/obj tree and read the file
 ``/usr/src/UPDATING'' for instructions about upgrading from source.

Dear Erik and Giorgos,

Thanks a lot for your assistance! I just cvsuped one hour ago,
build/install kernel/world and now everything is working just fine! I
had probably a bad luck during first cvsup...

One last question (just for curiosity). What is the procedure for
_upgrading_ of ipf? I mean, since ipf is already included in the base
(v4.1.8), is it possible to upgrade it to v4.1.10?

Thank you once again and have a nice day!
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Help with IP Filter 4.1.8

2006-03-09 Thread Roman Serbski
Hello Erik. Thank you for your help.

 Ok, here are some things to try:

 1) Other udp services, are responces also blocked? you can for example
 try ntp. If so, then it is likely a bug in ip-filter.

Yes. Same for other udp (I tested with ntp). The symptoms are the same
- there is a hit on a rule allowing outgoing ntp, but then reply is
blocked.

 2) Try using snort or tcpdump to capture the blocked packet and analyse
 if it is malformed. Possibly include such a packet with your next post.

I can collect tcpdump data only if I disable ipf or configure it to
'pass in/out all'. If I turn on my ruleset I don't see any data from
tcpdump. Running 'tcpdump -vvv -i xl0' generates a message that
tcpdump is listening on xl0 but no data is captured...

 3) try to see if you can upgrade to a newer ipfilter, latest is v4.1.10

I will try that, although I have faced with the problem while
upgrading to v4.1.10. According to ipf docs (INSTALL.FreeBSD):

To build a kernel with the IP filter, follow these steps:

make freebsd5 - went successfully
make install-bsd - went successfully
FreeBSD/kinstall - generated patch error about conf.c file not being found...

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


Re: Help with IP Filter 4.1.8

2006-02-27 Thread Roman Serbski
On 2/26/06, Donald J. O'Neill [EMAIL PROTECTED] wrote:
 I don't see anything in the OP's message that requires kernel debugging.
 Just some advice that he should check to see what changes have been
 made to ipf v4.1.8 as compared to v3.4.35 and how they affect rules.

Thank you Don. Exactly. I can only guess that there were some changes
in ipf, and I was not able to track what was actually changed to
adjust my v3.4.XX ruleset to v4.1.8.

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


Re: Help with IP Filter 4.1.8

2006-02-27 Thread Roman Serbski
On 2/27/06, Erik Nørgaard [EMAIL PROTECTED] wrote:
 Could you change your last rule to this:

 block in log quick on xl0 all

 and then tell what you see in the log. This would give some information
 if any traffic is blocked in the first place. Actually, adding the log
 keyword to all rules for the xl0 interface might be a good idea for
 debugging.

 Also, is this the complete ruleset or did you remove rules you thought
 were irrelevant? If so, then post the whole ruleset.

Thank you. I removed 'flags' as it was suggested by Giorgos Keramidas
but it didn't help.

This is not the complete ruleset, I mean there are a lot of other
rules, but I removed everything to be sure and left only outgoing
53/udp, 53/tcp. Once again, I checked this ruleset on 5.3-STABLE with
ipf v3.4.35 (336) and it worked good.

Adding the 'log' keyword produced the following record:

xl0 @0:2 b XXX.XXX.XXX.XXX,53 - YYY.YYY.YYY.YYY,60808 PR udp len 20 298 IN bad

where XXX - is IP address of DNS server of ISP, and YYY is the server
I'm running ipf on. There was a hit on a rule allowing outgoing 53/udp
and it seems like the response from DNS server was blocked. Outgoing
port number returned by YYY is always changing - on a second run it
was 51212.

Of course I can allow incoming connections to ports  1024, but I
really would like to understand why it was working with ipf v3.4.35
and not with v4.1.8.

Once again, thank you all for your help.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Help with IP Filter 4.1.8

2006-02-27 Thread Roman Serbski
On 2/27/06, Giorgos Keramidas [EMAIL PROTECTED] wrote:
 One reason why this could fail is that the xl0 interface is not part of
 the route to your ISP's DNS servers.

 How many interfaces does the system have?  Is xl0 in the path to your
 ISP's router?

There are two interfaces - xl0 and xl1 with no cable connected to xl1.
gateway_enable is not defined in rc.conf so is off.
I can successfully access ISP's DNS both if I disable ipf or configure
ifp to 'pass in all'.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Help with IP Filter 4.1.8

2006-02-27 Thread Roman Serbski
On 2/27/06, Erik Norgaard [EMAIL PROTECTED] wrote:
 read this line: This tells you where the packet is blocked. IIRC @0:2
 means group 0 (you don't use groups) and 2 should be the second rule.

 If you list the ruleset with ipfstat -n that should give you rules with
 the same labeling.

 Also, add log keyword to your outgoing rule, to see that it is actually
 there the decision is made. You could have some default pass that does
 not create the state.

 I know that you've checked and rechecked - but it is really helpful for
 us to have the whole ruleset. If you like, change your ip's to x.x.x.x
 (but keep different ips different).

Hello Erik,

My ruleset consists of only 6 rules:

pass out quick on lo0 from any to any
pass out quick on xl0 proto tcp from any to any port = domain flags
S/FSRPAU keep state
pass out quick on xl0 proto udp from any to any port = domain keep state
block out log quick on xl0 all
pass in quick on lo0 from any to any
block in quick on xl0 all

The rule # 2 which was blocking reply from DNS server is 'block in
quick on xl0 all'.

Adding 'log' keyword to the rule allowing outgoing 53/udp gives the following:

xl0 @0:3 p YYY.YYY.YYY.YYY,50359 - XXX.XXX.XXX.XXX,53 PR udp len 20 57 K-S OUT

So outgoing 53/udp was successfully passed through, but incoming reply
was blocked again:

xl0 @0:2 b XXX.XXX.XXX.XXX,53 - YYY.YYY.YYY.YYY,50359 PR udp len 20 298 IN bad

Yes, I also tried another DNS server - same results.

I think this is more ipf issue, so I'll try to ask for assistance in
ipf maling list, I was just thinking if someone else has faced with
the similar problem during upgrade from ipf v3.4.35 to v4.1.8.

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


Help with IP Filter 4.1.8

2006-02-26 Thread Roman Serbski
Hi all,

I am having a problem with ipf after recent upgrade to 6.1-PRERELEASE.
Any help would be greatly appreciated.

ipf: IP Filter: v4.1.8 (416)
Kernel: IP Filter: v4.1.8
Running: yes
Log Flags: 0 = none set
Default: pass all, Logging: available
Active list: 0
Feature mask: 0xa

I am trying to allow outgoing dns requests from my server to DNS
server of ISP. Here is my ruleset:

ipfstat -oh
0 pass out quick on lo0 from any to any
0 pass out quick on xl0 proto tcp from any to any port = domain flags
S/FSRPAU keep state
1 pass out quick on xl0 proto udp from any to any port = domain keep state
0 block out log quick on xl0 all

ipfstat -ih
0 pass in quick on lo0 from any to any
0 block in quick on xl0 all

I tried `host www.google.com` and the connection was timed out,
although there was a hit on a rule allowing 53/udp.

The interesting thing is that there is another server running
5.3-STABLE with ipf v3.4.35 (336) and it has the same ruleset and
everything is working just fine.

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


Please help with pppd and routing

2005-10-25 Thread Roman Serbski
Dear all,

I would appreciate your advise regarding pppd and routing. FreeBSD
5.4-STABLE, pppd with mgetty acting as dial-in server with one
external modem. I can connect to server with no problem but it seems
like routing doesn't work for dial-in user. I cannot even ping the ip
address of dial-in server. Here is my configuration:

The IP address of dial-in server: 192.168.1.35/28
The end address of the PPP link is 192.168.1.41/28
The IP address to be assigned to dial-in user is 192.168.1.44/28

IP forwarding is on.
# sysctl -a | grep forward

net.inet.ip.forwarding: 1

# cat /etc/ppp/ppp.conf

default:
set device /dev/cuaa0
set log Phase Chat LCP IPCP CCP tun command
enable passwdauth
set speed 38400
set dial ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \\ AT OK-AT-OK
ATE1Q0 OK \\dATDT\\TTIMEOUT 40 CONNECT
set timeout 120
set ifaddr 192.168.1.35/28 255.255.255.240 0.0.0.0
add default HISADDR
enable dns

cuaa0:
set ifaddr 192.168.1.41 192.168.1.44
enable passwdauth
allow users ppp mef
accept dns
set dns 192.168.1.3
enable proxy

ttyd0:
set ifaddr 192.168.1.41 192.168.1.44
enable passwdauth
allow users testppp
accept dns
set dns 192.168.1.3
enable proxy

pap:
enable pap
set ifaddr 192.168.1.41 192.168.1.44
enable proxy
enable passwdauth

ifconfig and netstat -rn information before ppp session:

# ifconfig
tl0: flags=108843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
inet 192.168.1.35 netmask 0xfff0 broadcast 192.168.1.47
ether 00:50:8b:50:f2:0e
media: Ethernet autoselect (100baseTX full-duplex)
status: active
plip0: flags=108810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500
lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384
inet 127.0.0.1 netmask 0xff00
tun0: flags=8010POINTOPOINT,MULTICAST mtu 1500

# netstat -rn
Destination Gateway Flags Refs Use Netif Expire
default 192.168.1.33 UGS 1 499 tl0
127.0.0.1 127.0.0.1 UH 0 42 lo0
192.168.1.32/28 link#1 UC 0 0 tl0
192.168.1.33 00:09:7c:61:93:30 UHLW 1 0 tl0 953

ifconfig and netstat -rn information after ppp session:

# ifconfig

tl0: flags=108843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
inet 192.168.1.35 netmask 0xfff0 broadcast 192.168.1.47
ether 00:50:8b:50:f2:0e
media: Ethernet autoselect (100baseTX full-duplex)
status: active
plip0: flags=108810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500
lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384
inet 127.0.0.1 netmask 0xff00
tun0: flags=8051UP,POINTOPOINT,RUNNING,MULTICAST mtu 1500
inet 192.168.1.41 -- 192.168.1.44 netmask 0xfff0
Opened by PID 747

# netstat -rn

Destination Gateway Flags Refs Use Netif Expire
default 192.168.1.33 UGS 1 599 tl0
127.0.0.1 127.0.0.1 UH 0 42 lo0
192.168.1.32/28 link#1 UC 0 0 tl0
192.168.1.33 00:09:7c:61:93:30 UHLW 1 0 tl0 1002
192.168.1.44 192.168.1.41 UH 0 0 tun0
192.168.1.44 00:50:8b:50:f2:0e UHLS2 0 0 tl0

Dial-in user receives 192.168.1.44 IP address but it cannot be pinged
from dial-in server:

PING 192.168.1.44 (192.168.1.44): 56 data bytes
ping: sendto: No route to host
ping: sendto: No route to host
ping: sendto: No route to host

I think I made a mistake in default: section of ppp.conf. Please advise.

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


Problem with PHP

2005-06-16 Thread Roman Serbski
Hello,

Please help with the installation of PHP 4.3.11 under FreeBSD 5.4-STABLE.

pkg_info | grep apache
apache-2.0.54   Version 2 of Apache web server with prefork MPM.

pkg_info | grep libtool
libtool-1.5.10_1Generic shared library support script (version 1.5)

Apache has been compiled from ports with the following options:

make WITH_STATIC_MODULES=include rewrite auth vhost_alias ssl
WITH_LDAP=yes WITH_SUEXEC=yes SUEXEC_DOCROOT=/home install clean

I'm trying to build PHP 4.3.11 from sources:

./configure \
--prefix=/usr/local/php4 \
--with-apxs2=/usr/local/sbin/apxs \
--with-zlib=/usr \
--with-mysql=/usr/local \
--with-gettext=/usr/local \
--enable-ftp \
--with-gd=/usr/local \
--with-expat=/usr/local \
--with-dom=/usr/local \
--with-iconv=/usr/local \
--enable-mime-magic \
--with-xml=/usr/local \
--enable-mbstring \
--with-jpeg-dir=/usr/local \
--with-png-dir=/usr/local \
--with-freetype-dir=/usr/local

`./configure` and `make` do not show any errors, but when I try to
`make install` the following error appears:

Installing PHP SAPI module:   apache2handler
/usr/local/share/apache2/build/instdso.sh
SH_LIBTOOL='/usr/local/share/apache2/build/libtool' libphp4.la
/usr/local/libexec/apache2
/usr/local/share/apache2/build/libtool --mode=install cp libphp4.la
/usr/local/libexec/apache2/
libtool: install: `libphp4.la' is not a valid libtool archive
Try `libtool --help --mode=install' for more information.
apxs:Error: Command failed with rc=65536
.
*** Error code 1

Any hints would be greatly appreciated!

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


Re: Problem with PHP

2005-06-16 Thread Roman Serbski
On 6/16/05, Alexandr Kosarev [EMAIL PROTECTED] wrote:
 On Thu, Jun 16, 2005 at 03:07:21PM +0600, Roman Serbski wrote:
  Hello,
 
  Please help with the installation of PHP 4.3.11 under FreeBSD 5.4-STABLE.
 
  pkg_info | grep apache
  apache-2.0.54   Version 2 of Apache web server with prefork MPM.
 
  pkg_info | grep libtool
  libtool-1.5.10_1Generic shared library support script (version 1.5)
 
  Apache has been compiled from ports with the following options:
 
  make WITH_STATIC_MODULES=include rewrite auth vhost_alias ssl
  WITH_LDAP=yes WITH_SUEXEC=yes SUEXEC_DOCROOT=/home install clean
 
  I'm trying to build PHP 4.3.11 from sources:
 
  ./configure \
  --prefix=/usr/local/php4 \
  --with-apxs2=/usr/local/sbin/apxs \
  --with-zlib=/usr \
  --with-mysql=/usr/local \
  --with-gettext=/usr/local \
  --enable-ftp \
  --with-gd=/usr/local \
  --with-expat=/usr/local \
  --with-dom=/usr/local \
  --with-iconv=/usr/local \
  --enable-mime-magic \
  --with-xml=/usr/local \
  --enable-mbstring \
  --with-jpeg-dir=/usr/local \
  --with-png-dir=/usr/local \
  --with-freetype-dir=/usr/local
 
  `./configure` and `make` do not show any errors, but when I try to
  `make install` the following error appears:
 
  Installing PHP SAPI module:   apache2handler
  /usr/local/share/apache2/build/instdso.sh
  SH_LIBTOOL='/usr/local/share/apache2/build/libtool' libphp4.la
  /usr/local/libexec/apache2
  /usr/local/share/apache2/build/libtool --mode=install cp libphp4.la
  /usr/local/libexec/apache2/
  libtool: install: `libphp4.la' is not a valid libtool archive
  Try `libtool --help --mode=install' for more information.
  apxs:Error: Command failed with rc=65536
  .
  *** Error code 1
 
  Any hints would be greatly appreciated!
 
  Thank you.
  Roman
  ___
  freebsd-questions@freebsd.org mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-questions
  To unsubscribe, send any mail to [EMAIL PROTECTED]
 
 Hello, Roman.
 Can your try to install php4 with ports collection?
 Modules for PHP4 your cat install with port /usr/ports/lang/php4-extensions/
 (make config) and your can install modules by other ports.
 
 So why your try install php4 from source???

Hello,

I was always thinking that building PHP from sources gives more
flexibility rather than from ports. For example, I want to build gd
support for PHP. If I compile PHP from sources all I have to do is to
install ports/graphics/gd and define --with-gd for PHP configure. As
for php4-extensions, I don't know why, but it tries to fetch X11R
sources:

===   php4-gd-4.3.11_1 depends on executable: phpize - found
===   php4-gd-4.3.11_1 depends on file: /usr/local/bin/automake15 - found
===   php4-gd-4.3.11_1 depends on file: /usr/local/bin/autoconf253 - found
===   php4-gd-4.3.11_1 depends on shared library: freetype.9 - found
===   php4-gd-4.3.11_1 depends on shared library: png.5 - found
===   php4-gd-4.3.11_1 depends on shared library: jpeg.9 - found
===   php4-gd-4.3.11_1 depends on shared library: X11.6 - not found
===Verifying install for X11.6 in /usr/ports/x11/xorg-libraries
===  Vulnerability check disabled, database not found
= X11R6.8.2-src1.tar.gz doesn't seem to exist in /usr/ports/distfiles/xorg.
= Attempting to fetch from ftp://ftp.gwdg.de/pub/x11/x.org/pub/X11R6.8.2/src/.

Why do I need to download 32MB to have gd support enabled? I was not
able to find any way to disable this behavior.

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