make world failure with today's current. (in /usr/src/sys/boot/i386/boot2/boot2.c)

2003-11-11 Thread Mark Sergeant
Hi Guys,

Source as of 4 hours ago I get the following in make world ...

Cheers,

Mark


Full log of error follows :

objcopy -S -O binary boot1.out boot1
dd if=/dev/zero of=boot2.ldr bs=276 count=1 2/dev/null
nm -t d boot1.out | awk '/([0-9])+ T xread/  { x = $1 - ORG1;
printf(#define X
READORG %#x\n, REL1 + x) }'  ORG1=`printf %d 0x7c00`  REL1=`printf
%d 0x700
`  boot2.h
cc -elf -ffreestanding -Os -fno-builtin  -fno-guess-branch-probability
-fomit-fr
ame-pointer -mno-align-long-strings  -mrtd  -DUFS1_AND_UFS2
-I/usr/src/sys/boot
/i386/boot2/../../common  -I/usr/src/sys/boot/i386/boot2/../btx/lib -I.
-Wall -
Waggregate-return -Wbad-function-cast -Wcast-align
-Wmissing-declarations -Wmis
sing-prototypes -Wnested-externs  -Wpointer-arith -Wshadow
-Wstrict-prototypes -
Wwrite-strings -ffreestanding -mpreferred-stack-boundary=2  -S -o
boot2.s.tmp /u
sr/src/sys/boot/i386/boot2/boot2.c
/usr/src/sys/boot/i386/boot2/boot2.c: In function `load':
/usr/src/sys/boot/i386/boot2/boot2.c:362: error: `RB_BOOTINFO'
undeclared (first
 use in this function)
/usr/src/sys/boot/i386/boot2/boot2.c:362: error: (Each undeclared
identifier is
reported only once
/usr/src/sys/boot/i386/boot2/boot2.c:362: error: for each function it
appears in
.)
*** Error code 1

Stop in /usr/src/sys/boot/i386/boot2.
*** Error code 1

Stop in /usr/src/sys/boot/i386.
*** Error code 1

Stop in /usr/src/sys/boot.
*** Error code 1

Stop in /usr/src/sys.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

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


Re: mysql-client compiler error

2003-09-14 Thread Mark Sergeant
I get the same problem in the same place with current as of today.

Cheers,

Mark

On Sat, 2003-09-13 at 20:37, Matt wrote:
 After building world as of late last night I decided to portupgrade 
 -rRaf, mainly due to having the libintl.so.4 missing problem when I 
 tried to start X. Everything compiled perfectly fine (and X is now 
 working fine) except for databases/mysql40-client. I get this error:
 
 checking for C compiler default output... configure: error: C compiler 
 cannot create executables
 configure: error: could not configure Berkeley DB
 
 I just wish to know is this something wrong with my system in general or 
 is this just due to the -pthread discussions that have been occuring and 
 that this port is one example of those that no longer works on -current?
 
 It is not a problem as I have the previously compiled/installed version 
 still on the system but I just wish to confirm if the problem is likely 
 to be down to the pthreads changes, and if I should report it to the 
 port maintainer etc?
 
 Matt.
 
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to [EMAIL PROTECTED]
-- 
Mark Sergeant [EMAIL PROTECTED]
SNSOnline Technical Services
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: [patch] usb ohci suspend/resume v2

2003-09-09 Thread Mark Sergeant
I've cvsup'ed applied this patch and am now compiling world and kernel,
should have an update in a few hours.

Cheers,

Mark

On Tue, 2003-09-09 at 17:18, Anish Mistry wrote:
 On Monday 08 September 2003 02:39 am, you wrote:
  I've tried this patch but was unable to compile my kernel against it
  with any of the sources from the past couple of weeks, it does apply
  cleanly though.
 
  Cheers,
 
  Mark
 
 Updated patch at (same as attached):
 http://am-productions.biz/docs/usb-3.patch
 
 This still causes the same problem as setting hw.acpi.sleep_delay on my laptop
 which cause a reset.  I can't seem to figure out what in this patch that is
 causing that same behavior, but I've yet to see anyone with that same
 problem, so I'm going to assume that this should work for everyone else :(.
 Please if you are a usb guru, I could use some help, I've looked at the spec
 and some of the usb code, but am stuck for now.
 If you try it, let me know your outcome so I can then clean up the patch so
 that someone can commit it.
 
 Anish Mistry
-- 
Mark Sergeant [EMAIL PROTECTED]
SNSOnline Technical Services
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: [patch] usb ohci suspend/resume v2

2003-09-09 Thread Mark Sergeant
When compiling 

/usr/src/sys/dev/usb/ohci.c: In function `ohci_resume':
/usr/src/sys/dev/usb/ohci.c:1035: warning: unused variable `hcr'
/usr/src/sys/dev/usb/ohci.c:1035: warning: unused variable `desca'
/usr/src/sys/dev/usb/ohci.c: In function `ohci_suspend':
/usr/src/sys/dev/usb/ohci.c:1125: warning: unused variable `i'



On Tue, 2003-09-09 at 17:18, Anish Mistry wrote:
 On Monday 08 September 2003 02:39 am, you wrote:
  I've tried this patch but was unable to compile my kernel against it
  with any of the sources from the past couple of weeks, it does apply
  cleanly though.
 
  Cheers,
 
  Mark
 
 Updated patch at (same as attached):
 http://am-productions.biz/docs/usb-3.patch
 
 This still causes the same problem as setting hw.acpi.sleep_delay on my laptop
 which cause a reset.  I can't seem to figure out what in this patch that is
 causing that same behavior, but I've yet to see anyone with that same
 problem, so I'm going to assume that this should work for everyone else :(.
 Please if you are a usb guru, I could use some help, I've looked at the spec
 and some of the usb code, but am stuck for now.
 If you try it, let me know your outcome so I can then clean up the patch so
 that someone can commit it.
 
 Anish Mistry
-- 
Mark Sergeant [EMAIL PROTECTED]
SNSOnline Technical Services
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Kernel compile problem with device wi in kernel. (GENERIC custom kernels)

2003-09-08 Thread Mark Sergeant
I've got the following problem when trying to compile a kernel with
todays sources and the device wi in it.

linking kernel
if_wi.o: In function `wi_attach':
if_wi.o(.text+0x2b4): undefined reference to `ieee80211_ieee2mhz'
if_wi.o(.text+0x673): undefined reference to `ieee80211_ifattach'
if_wi.o(.text+0x6a7): undefined reference to `ieee80211_media_init'
if_wi.o: In function `wi_detach':
if_wi.o(.text+0x7b2): undefined reference to `ieee80211_ifdetach'
if_wi.o: In function `wi_init':
if_wi.o(.text+0xd21): undefined reference to `ieee80211_chan2ieee'
if_wi.o(.text+0x12c9): undefined reference to `ieee80211_chan2ieee'
if_wi.o: In function `wi_start':
if_wi.o(.text+0x18f2): undefined reference to `ieee80211_encap'
if_wi.o(.text+0x1958): undefined reference to `ieee80211_wep_crypt'
if_wi.o(.text+0x1989): undefined reference to `ieee80211_free_node'
if_wi.o(.text+0x1b08): undefined reference to `ieee80211_free_node'
if_wi.o: In function `wi_watchdog':
if_wi.o(.text+0x1f07): undefined reference to `ieee80211_watchdog'
if_wi.o: In function `wi_ioctl':
if_wi.o(.text+0x2348): undefined reference to `ieee80211_ioctl'
if_wi.o: In function `wi_media_change':
if_wi.o(.text+0x23f2): undefined reference to `ieee80211_media_change'
if_wi.o: In function `wi_media_status':
if_wi.o(.text+0x2520): undefined reference to `ieee80211_rate2media'
if_wi.o: In function `wi_rx_intr':
if_wi.o(.text+0x2d6d): undefined reference to `ieee80211_find_node'
if_wi.o(.text+0x2da7): undefined reference to `ieee80211_input'
if_wi.o(.text+0x2dc5): undefined reference to `ieee80211_free_node'
if_wi.o: In function `wi_get_cfg':
if_wi.o(.text+0x408a): undefined reference to `ieee80211_cfgget'
if_wi.o: In function `wi_set_cfg':
if_wi.o(.text+0x47a2): undefined reference to `ieee80211_cfgset'
if_wi.o: In function `wi_newstate':
if_wi.o(.text+0x56e4): undefined reference to `ieee80211_state_name'
if_wi.o: In function `wi_dump_pkt':
if_wi.o(.text+0x5cee): undefined reference to `ieee80211_dump_pkt'
*** Error code 1

Stop in /usr/src/sys/i386/compile/XYZZY.


uname -a output :

FreeBSD xyzzy.wireless.snsonline.net 5.1-CURRENT FreeBSD 5.1-CURRENT #0:
Mon Sep  8 13:25:52 EST 2003
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/XYZZY  i386


Cheers,

-- 
Mark Sergeant [EMAIL PROTECTED]
SNSOnline Technical Services
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Various problems after latest -CURRENT build. (USB, WI, KSE)

2003-09-04 Thread Mark Sergeant
Hi Guys,

I've noticed a bunch of problems with my latest current build...

1. With device wi in my kernel I was unable to compile at all, had to
take it out and then use a module to get it to work.
2. My USB mouse no longer works, Works fine on my 5.1-RELEASE machine
but nothing as of last nights kernel and world.
3. libkse seems to be causing hangs in various processes including
evolution, once I changed libmap to libc_r everything has run smoothly.

Cheers,
-- 
Mark Sergeant [EMAIL PROTECTED]
SNSOnline Technical Services
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Broken kernel compile on 5.1-RELEASE / 5-CURRENT (SMP, PAE scsi)

2003-08-19 Thread Mark Sergeant
Hi All,

When trying to compile a kernel for my 8 cpu DELL 8450's I recieve an
extremly puzzling error, I get a bunch of errors when compiling a kernel
that has the following options in it...

options WITNESS
options NETSMB
options NETSMBCRYPTO
options LIBMCHAIN
options LIBICONV
options PAE
options SMP 
options APIC_IO

Without  PAE SMP or APIC_IO the kernel will compile fine. With these
options I get the following error when compiling the sym scsi driver.
cc -c -O -pipe -march=pentium3 -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline
-Wcast-qual  -fformat-extensions -std=c99  -nostdinc -I-  -I. -I../../..
-I../../../dev -I../../../contrib/dev/acpica -I../../../contrib/ipfilter
-D_KERNEL -include opt_global.h -fno-common  -mno-align-long-strings
-mpreferred-stack-boundary=2 -ffreestanding -Werror 
../../../dev/sym/sym_hipd.c
cc1: warnings being treated as errors
../../../dev/sym/sym_hipd.c: In function `sym_setup_data_and_start':
../../../dev/sym/sym_hipd.c:8146: warning: cast from pointer to integer
of different size
*** Error code 1

This is rather unfortunate as the only disks I have run off this
controller. I've found that it does compile with the ahc driver but even
then some usb stuff needs removing.

Does anyone have any insight into this and what I can do to get it
fixed.

Cheers,
-- 
Mark Sergeant [EMAIL PROTECTED]
SNSOnline Technical Services
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Broken kernel compile on 5.1-RELEASE / 5-CURRENT (SMP, PAE scsi)

2003-08-19 Thread Mark Sergeant
Ohh bugger. I suppose I'll have to live without PAE then. Thanks anyway.

Cheers,

Mark

On Tue, 2003-08-19 at 17:19, Don Lewis wrote:
 On 19 Aug, Mark Sergeant wrote:
  Hi All,
  
  When trying to compile a kernel for my 8 cpu DELL 8450's I recieve an
  extremly puzzling error, I get a bunch of errors when compiling a kernel
  that has the following options in it...
  
  options WITNESS
  options NETSMB
  options NETSMBCRYPTO
  options LIBMCHAIN
  options LIBICONV
  options PAE
  options SMP 
  options APIC_IO
  
  Without  PAE SMP or APIC_IO the kernel will compile fine. With these
  options I get the following error when compiling the sym scsi driver.
 
 Take a look at /usr/src/sys/i386/conf/PAE.  It says:
 
 # What follows is a list of drivers that are normally in GENERIC, but either
 # don't work or are untested with PAE.  Be very careful before enabling any
 # of these drivers.  Drivers which use DMA and don't handle 64 bit physical
 # address properly may cause data corruption when used in a machine with more
 # than 4 gigabytes of memory.
 
 and under this comment it lists the sym and usb drivers.
-- 
Mark Sergeant [EMAIL PROTECTED]
SNSOnline Technical Services
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Broken kernel compile on 5.1-RELEASE / 5-CURRENT (SMP, PAE scsi)

2003-08-19 Thread Mark Sergeant
On Tue, 2003-08-19 at 17:47, Scott Long wrote:
 Mark Sergeant wrote:
  Hi All,
  
  When trying to compile a kernel for my 8 cpu DELL 8450's I recieve an
  extremly puzzling error, I get a bunch of errors when compiling a kernel
  that has the following options in it...
  
  options WITNESS
  options NETSMB
  options NETSMBCRYPTO
  options LIBMCHAIN
  options LIBICONV
  options PAE
  options SMP 
  options APIC_IO
  
  Without  PAE SMP or APIC_IO the kernel will compile fine. With these
  options I get the following error when compiling the sym scsi driver.
  cc -c -O -pipe -march=pentium3 -Wall -Wredundant-decls -Wnested-externs
  -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline
  -Wcast-qual  -fformat-extensions -std=c99  -nostdinc -I-  -I. -I../../..
  -I../../../dev -I../../../contrib/dev/acpica -I../../../contrib/ipfilter
  -D_KERNEL -include opt_global.h -fno-common  -mno-align-long-strings
  -mpreferred-stack-boundary=2 -ffreestanding -Werror 
  ../../../dev/sym/sym_hipd.c
  cc1: warnings being treated as errors
  ../../../dev/sym/sym_hipd.c: In function `sym_setup_data_and_start':
  ../../../dev/sym/sym_hipd.c:8146: warning: cast from pointer to integer
  of different size
  *** Error code 1
  
  This is rather unfortunate as the only disks I have run off this
  controller. I've found that it does compile with the ahc driver but even
  then some usb stuff needs removing.
  
  Does anyone have any insight into this and what I can do to get it
  fixed.
  
  Cheers,
 
 The key kere is likely PAE, not APIC_IO, as PAE changes the size of
 some data types.  The USB problem is known.  The sym problem looks to
 be harmless assuming that the warning you got is the only one that
 is emitted.  However, it appears that it was never certified as being
 ready for PAE.  If you're adventurous, you can try compiling and
 loading it as a module (warnings when compiling modules are not fatal
 like they are in when compiling the kernel).
 
 If there are more errors/warning that what you list, I'd be interested
 in seeing them.
 
 Scott

There are no other errors apart from those listed so I may try compiling
as a module that gets loaded on boot. Just one problem, I succesfully
build an SMP kernel without PAE and then rebooted and the server is no
longer responding, it seems it crashed just after coming up as I was
able to ping it 5 or 6 times and then it went away again. If I've got a
crash dump I'll post it.

Cheers,

-- 
Mark Sergeant [EMAIL PROTECTED]
SNSOnline Technical Services
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Broken kernel on 5.1-RELEASE was :[compile on 5.1-RELEASE /5-CURRENT (SMP, PAE scsi)]

2003-08-19 Thread Mark Sergeant
Ok I've now got problems with the compiled kernel, I get panics on my
multiple cpu machine on boot just after boot  before the prompt is
reached. It's a lock on cpu #2 ( I believe cpu 3 ).

Unfortunately I don't have the exact message nor do I have a kernel dump
as this machine is meant to be a production one and as such a boot of
kernel.old was done.

Does anyone have a 4 or greater cpu machine running 5.1-RELEASE
succesfully ? I've got a 5.1-RELEASE machine running with the same
kernel config  2 cpu's  without any problem so I can only think that
it's something to do with more than 2 cpu's.

Cheers,

Mark

On Tue, 2003-08-19 at 17:55, Mark Sergeant wrote:
 On Tue, 2003-08-19 at 17:47, Scott Long wrote:
  Mark Sergeant wrote:
   Hi All,
   
 When trying to compile a kernel for my 8 cpu DELL 8450's I recieve an
   extremly puzzling error, I get a bunch of errors when compiling a kernel
   that has the following options in it...
   
   options WITNESS
   options NETSMB
   options NETSMBCRYPTO
   options LIBMCHAIN
   options LIBICONV
   options PAE
   options SMP 
   options APIC_IO
   
   Without  PAE SMP or APIC_IO the kernel will compile fine. With these
   options I get the following error when compiling the sym scsi driver.
   cc -c -O -pipe -march=pentium3 -Wall -Wredundant-decls -Wnested-externs
   -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline
   -Wcast-qual  -fformat-extensions -std=c99  -nostdinc -I-  -I. -I../../..
   -I../../../dev -I../../../contrib/dev/acpica -I../../../contrib/ipfilter
   -D_KERNEL -include opt_global.h -fno-common  -mno-align-long-strings
   -mpreferred-stack-boundary=2 -ffreestanding -Werror 
   ../../../dev/sym/sym_hipd.c
   cc1: warnings being treated as errors
   ../../../dev/sym/sym_hipd.c: In function `sym_setup_data_and_start':
   ../../../dev/sym/sym_hipd.c:8146: warning: cast from pointer to integer
   of different size
   *** Error code 1
   
   This is rather unfortunate as the only disks I have run off this
   controller. I've found that it does compile with the ahc driver but even
   then some usb stuff needs removing.
   
   Does anyone have any insight into this and what I can do to get it
   fixed.
   
   Cheers,
  
  The key kere is likely PAE, not APIC_IO, as PAE changes the size of
  some data types.  The USB problem is known.  The sym problem looks to
  be harmless assuming that the warning you got is the only one that
  is emitted.  However, it appears that it was never certified as being
  ready for PAE.  If you're adventurous, you can try compiling and
  loading it as a module (warnings when compiling modules are not fatal
  like they are in when compiling the kernel).
  
  If there are more errors/warning that what you list, I'd be interested
  in seeing them.
  
  Scott
 
 There are no other errors apart from those listed so I may try compiling
 as a module that gets loaded on boot. Just one problem, I succesfully
 build an SMP kernel without PAE and then rebooted and the server is no
 longer responding, it seems it crashed just after coming up as I was
 able to ping it 5 or 6 times and then it went away again. If I've got a
 crash dump I'll post it.
 
 Cheers,
-- 
Mark Sergeant [EMAIL PROTECTED]
SNSOnline Technical Services
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Problem with dhclient wi0 on resume.

2003-08-14 Thread Mark Sergeant

On Tue, 2003-08-12 at 21:10, Martin Blapp wrote:
 Hi,
 
  Unfortunately this system hasn't worked for me. As it is I have a script
 

I've put the sleep command in rc.suspend and the wake in rc.resume but
they didn't help. I also tried to use these commands manually and again
no luck. Killing dhclient and restarting manually works though.

 Have you tested it and included theses commands in rc.resume and rc.suspend ?
 
  which lives in rc.d which starts up dhclient with the appropriate
  wireless options. Unfortunately after each suspend and resume this is
  what I have to use.
 
  If anyone comes up with a solution to this it'd be much appreciated.
 
 Which script do you use ? The dhclient script in /etc/rc.d ?
 

The script I use is a homemade one, after looking at
/etc/rc.d/dhclient it seems that this will do the job nicely enough,
thanks for this tip. 

My main problem now comes back to the wi driver spitting up a whole lot
of errors, it's now quite often freezing up entirely with the following
...

wi0: timeout in wi_cmd 0x0002; event status 0x8080
wi0: timeout in wi_cmd 0x0121; event status 0x8080
wi0: wi_cmd: busy bit won't clear.
wi0: wi_cmd: busy bit won't clear.
wi0: wi_cmd: busy bit won't clear.
wi0: wi_cmd: busy bit won't clear.
wi0: wi_cmd: busy bit won't clear.
wi0: wi_cmd: busy bit won't clear.
wi0: wi_cmd: busy bit won't clear.
wi0: wi_cmd: busy bit won't clear.
wi0: wi_cmd: busy bit won't clear.
wi0: wi_cmd: busy bit won't clear.
wi0: wi_cmd: busy bit won't clear.
wi0: wi_cmd: busy bit won't clear.
wi0: wi_cmd: busy bit won't clear.
wi0: wi_cmd: busy bit won't clear.
wi0: wi_cmd: busy bit won't clear.
wi0: wi_cmd: busy bit won't clear.
wi0: wi_cmd: busy bit won't clear.
wi0: failed to allocate 2372 bytes on NIC
wi0: tx buffer allocation failed (error 12)
wi0: interface not running
wi0: wi_cmd: busy bit won't clear.
wi0: wi_cmd: busy bit won't clear.
wi0: wi_cmd: busy bit won't clear.
wi0: wi_cmd: busy bit won't clear.
wi0: wi_cmd: busy bit won't clear.
wi0: wi_cmd: busy bit won't clear.
wi0: wi_cmd: busy bit won't clear.
wi0: wi_cmd: busy bit won't clear.
wi0: wi_cmd: busy bit won't clear.

The machine then has to be hard reset when this happens. 

 Martin
-- 
Mark Sergeant [EMAIL PROTECTED]
SNSOnline Technical Services
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Problem with dhclient wi0 on resume.

2003-08-14 Thread Mark Sergeant
Unfortunately this system hasn't worked for me. As it is I have a script
which lives in rc.d which starts up dhclient with the appropriate
wireless options. Unfortunately after each suspend and resume this is
what I have to use. 

If anyone comes up with a solution to this it'd be much appreciated.

Cheers,

Mark

On Tue, 2003-08-12 at 18:52, Martin Blapp wrote:
 Hi,
 
 I've got a toshiba portege 4000 with inbuilt wi0 wireless card. On
 resume dhclient kicks off straight away which then breaks as the card
 
 You mean dhclient gets killed ? One way could be to kill dhclient when you
 sleep. Afterwords, devd should restart it, right ? Unfortunatly I cannot
 test this myself as resume on my lapton is horribly broken.
 
 isn't loaded as yet. Is there anyway to specify a sleep value for
 dhclient on resume from suspend ? I'm running current from today, I
 should note I'm also seeing a bunch of wi0 bad_alloc messages as well
 with this card. It gets quite annoying to have to restart dhclient
 everytime I resume.
 
 There is one:
 
 /etc/dhclient.conf
 #
 #
 #
 omapi port 7911;
 
 /etc/sleep_dhclient
 
 #!/bin/sh
 
 omshell  /dev/null  EOF
 connect
 new control
 open
 set state = 3
 update
 close
 
 /etc/wakeup_dhclient
 
 #!/bin/sh
 
 omshell  /dev/null  EOF
 connect
 new control
 open
 set state = 4
 update
 close
 
 Please tell me if you have success with these.
 
 Martin
 
 Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED]
 --
 ImproWare AG, UNIXSP  ISP, Zurlindenstrasse 29, 4133 Pratteln, CH
 Phone: +41 61 826 93 00 Fax: +41 61 826 93 01
 PGP: finger -l [EMAIL PROTECTED]
 PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E
 --
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to [EMAIL PROTECTED]
-- 
Mark Sergeant [EMAIL PROTECTED]
SNSOnline Technical Services
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ntop broken?

2003-08-14 Thread Mark Sergeant
On Fri, 2003-08-08 at 15:26, Charlie Schluting wrote:
 On Thu, 7 Aug 2003, Kris Kennaway wrote:
On Wed, Aug 06, 2003 at 08:57:53AM -0700, Charlie Schluting wrote:
 Running 5.0.
   
cvsup to 5.1 and retry.  The package currently builds on a clean 5.1 system.
  
   Ok, done, and still:
   *  crypt() in -lc...no -lcrypt...no
   makes it fail.
   I cvsuped the ports with tag=.
   Any ideas?
 
  It's likely you have stale files lying around that are confusing the
  build.  ntop builds successfully on a clean 5.x system.
 
  Kris
 
 Ok, sorry for being a PITA, but..
 
 I try to install mcrypt, and it is marked broken. I'm kinda stuck. Any
 idea what files those would be? It seems that it can't find crypt.h and
 stuff like that, so it sounds to me like files are missing?
 
 Is there any particular approach you'd take in solving this?
 
 Thanks  :)
 
 --Charlie
I get the same error building latest ports version of ntop on my FreeBSD
5.1-CURRENT #0: Sat Jul 26 20:26:37 EST 2003 system. I'll look into this
and see if an easy fix can be found.

Cheers,

-- 
Mark Sergeant [EMAIL PROTECTED]
SNSOnline Technical Services
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


makemap problem in virtusertable.

2003-08-14 Thread Mark Sergeant
I'm running current as of two weeks ago I get the following problem when
doing a make in /etc/mail ...

makemap: virtusertable.db: line 206: key [EMAIL PROTECTED]: put error:
Operation not permitted
*** Error code 74

This line contains ...

[EMAIL PROTECTED]  [EMAIL PROTECTED]

As far as I am concerned this line should be valid, does anyone have any
idea why this would be an issue ?

Cheers,

-- 
Mark Sergeant [EMAIL PROTECTED]
SNSOnline Technical Services
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Problem with dhclient wi0 on resume.

2003-08-14 Thread Mark Sergeant
I've got a toshiba portege 4000 with inbuilt wi0 wireless card. On
resume dhclient kicks off straight away which then breaks as the card
isn't loaded as yet. Is there anyway to specify a sleep value for
dhclient on resume from suspend ? I'm running current from today, I
should note I'm also seeing a bunch of wi0 bad_alloc messages as well
with this card. It gets quite annoying to have to restart dhclient
everytime I resume.

The dmesg info is ...

wi0: detached
ata0: resetting devices ..
done
ata1: resetting devices ..
done
wakeup from sleeping state (slept 00:00:08)
wi0: TOSHIBA Wireless LAN Card at port 0x100-0x13f irq 11 function 0
config 1 on pccard0
wi0: 802.11 address: 00:02:2d:24:ec:d6
wi0: using Lucent Embedded WaveLAN/IEEE
wi0: Lucent Firmware: Station (6.14.1)
wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
wi0: bad alloc 62b != 100, cur 0 nxt 0
wi0: bad alloc 451 != 100, cur 0 nxt 0
wi0: bad alloc 345 != 100, cur 0 nxt 0
wi0: bad alloc 298 != 100, cur 0 nxt 0

the log from /var/log/messages is...

Aug 12 18:27:13 xyzzy kernel: wi0: detached
Aug 12 18:27:13 xyzzy kernel: ata0: resetting devices ..
Aug 12 18:27:13 xyzzy kernel: done
Aug 12 18:27:13 xyzzy kernel: ata1: resetting devices ..
Aug 12 18:27:13 xyzzy kernel: done
Aug 12 18:27:13 xyzzy kernel: wakeup from sleeping state (slept
00:00:08)
Aug 12 18:27:13 xyzzy dhclient: send_packet: No route to host
Aug 12 18:27:13 xyzzy dhclient: receive_packet failed on wi0: No route
to host
Aug 12 18:27:15 xyzzy kernel: wi0: TOSHIBA Wireless LAN Card at port
0x100-0x13f irq 11 function 0 config 1 on pccard0
Aug 12 18:27:15 xyzzy kernel: wi0: 802.11 address: 00:02:2d:24:ec:d6
Aug 12 18:27:15 xyzzy kernel: wi0: using Lucent Embedded WaveLAN/IEEE
Aug 12 18:27:15 xyzzy kernel: wi0: Lucent Firmware: Station (6.14.1)
Aug 12 18:27:15 xyzzy kernel: wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps


Cheers,

-- 
Mark Sergeant [EMAIL PROTECTED]
SNSOnline Technical Services
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: makemap problem in virtusertable.

2003-08-12 Thread Mark Sergeant
On Tue, 2003-08-12 at 10:30, Chris Larsen wrote:
 In the year of 2003, on Monday, August 11 at 16:30 +0200, Mark Sergeant proclaimed:
  I'm running current as of two weeks ago I get the following problem when
  doing a make in /etc/mail ...
  
  makemap: virtusertable.db: line 206: key [EMAIL PROTECTED]: put error:
  Operation not permitted
  *** Error code 74
  
  This line contains ...
  
  [EMAIL PROTECTED]  [EMAIL PROTECTED]
  
  As far as I am concerned this line should be valid, does anyone have any
  idea why this would be an issue ?
  
 
 Do you by any chance have a duplicate '[EMAIL PROTECTED]' in the virtusertable
 file ?
 
Ahh that was it, thanks heaps.

Cheers,

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


Re: LiveCD FBSD Current

2003-07-27 Thread Mark Sergeant
On Sat, 2003-07-26 at 21:09, Sebastian Yepes [ESN] wrote:
 On Fri, Jul 25, 2003 at 09:57:04PM -0700, Kris Kennaway wrote:
  On Sat, Jul 26, 2003 at 06:31:03AM +0200, Sebastian Yepes [ESN] wrote:
   
   Hi all
   
   I have made a liveCD of FreeBSD Current and it boot's and looks like it
   run ok..
   
   The only problem i am haveing is with the md system.. it dus not let me do
   the newfs on the md dev, i have runing devfs and mounted the procfs..
   
   
   mdcondig -a -t malloc -s 2m -u 0  - work's ok
   newfs /dev/md0
   --
   'pid xxx (newfs), uid 0: exited on signal 4
   IIIegal instruction
   --
   And with   mdmfs -M -s 2m md1 -tmp  i get the same error
   
   Can any one plz informe me on how to fix this or what am i duing bad...
  
  This typically means you compiled the binary with CPU optimizations
  that are incorrect for the target system.
  
  Kris
 
 Thanx for the tip..
 I was compiling the kernel for other box..
 
 It work 100% now thanx

Any chance of a website with a howto for others looking at doing the
same thing ?

Cheers,

-- 
Mark Sergeant [EMAIL PROTECTED]
SNSOnline Technical Services
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Recommended kernel config for a dell 8450, 8 cpu, 8GB of ram.

2003-07-27 Thread Mark Sergeant
Hi Guys,

Just seeking some general information. I've got a couple of dell
8 cpu
boxes here running FreeBSD 5.1-RELEASE and am interested in peoples
thoughts on the best kernel configs for this type of machine. I'm
interested in the best way of making use of 8 cpu's and also seeing the
whole 8GB of RAM.

Cheers,
-- 
Mark Sergeant [EMAIL PROTECTED]
SNSOnline Technical Services
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Disk/FS I/O issues in -CURRENT

2003-06-30 Thread Mark Sergeant
I get the same problem on a smp machine and my laptop both running
kernels as from today.

On Mon, Jun 30, 2003 at 03:26:13PM +0200, Eirik Oeverby wrote:
 Hi,
 
 Good to see I'm not the only one.
 I'm currently going back to a kernel dated 2003.06.27.12.00.00, and I'll test
 again with that one.
 
 /Eirik
 
 On Mon, 30 Jun 2003, Peter Holm wrote:
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.1-RELEASE TODO

2003-06-02 Thread Mark Sergeant
-snip-
 Monday, 02. June 2003, 09:16:59
 {0} FreeBSD 5.1-BETA [Magelan:~]
 (6) [EMAIL PROTECTED] # cp /mnt/ftpchroot-test.sh /tmp/
 
 Monday, 02. June 2003, 09:17:12
 {0} FreeBSD 5.1-BETA [Magelan:~]
 (7) [EMAIL PROTECTED] # umount /tmp
 umount: unmount of /tmp failed: Device busy
 
 Monday, 02. June 2003, 09:17:15
 {1} FreeBSD 5.1-BETA [Magelan:~]
 (8) [EMAIL PROTECTED] # sync;sync;sync
 
 Monday, 02. June 2003, 09:17:22
 {0} FreeBSD 5.1-BETA [Magelan:~]
 (9) [EMAIL PROTECTED] # umount /tmp
 umount: unmount of /tmp failed: Device busy
 ---snip---

Umm shouldn't you be trying to umount /mnt ?

-- 
Mark Sergeant [EMAIL PROTECTED]
SNSOnline Technical Services
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: your mail

2003-04-09 Thread Mark Sergeant

 Did you look at M. Warner Losh's commits in cbb framework?
 
 They seem to be relevant to me.

Having a look at it now, seems that yes pccbb.c has been updated and
could be the cause of my problems, unfortunately my c is abysmal so bar
rolling back to the previous version of this file I'll just have to sit
patiently. Thanks for the pointer.

Warner, if you're reading this any ideas ?

Cheers,

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


Re: USB problems after resume from suspend in current as ofJanuary 9

2003-01-13 Thread Mark Sergeant
on resume with a usbdevs -v I get ...

Controller /dev/usb0:
addr 1: full speed, self powered, config 1, OHCI root hub(0x),
AcerLabs(0x), rev 1.00
 port 1 addr 2: low speed, power 100 mA, config 1, USB Mouse(0xc00c),
Logitech(0x046d), rev 6.20
 port 2 powered
 port 3 powered

Regardless of whether the mouse is plugged in or not. I also tried
plugging in an intellimouse explorer  a usb keyboard, both of which
failed to work, neither were powered up at all. 

I should note that under 4.7 suspend and resume works fine. I tried to
kill and restart usbd but no luck.  So for now I'm stuck with shutting
down the system.

Cheers,

Mark

On Tue, 2003-01-14 at 09:28, Marc Butler wrote:
 On Fri, Jan 10, 2003 at 12:22:22PM +1100, Mark Sergeant wrote:
  I'm running a toshiba portege 4000 with -CURRENT as of January 9.
  Suspending and resuming runs fine apart from USB, on resume it is unable
  to recognise my USB mouse (logitech), nothing even registers that it is
  plugged in, nor does the mouse get any power yet on booting normally USB
  works fine. Has anyone got any ideas how I can work around this issues ?
 
 It may be the USB controller is being shutdown and not restarted.  To
 check whether the USB controller is up try: usbdevs -v which I
 believe should complain: no USB controllers found or similar.
 
 You may want to check the BIOS for any obvious settings related to
 USB and power management.
 
 Is ACPI involved in suspension?  I'm sorry but I know nothing about
 ACPI (or laptop power management).
-- 
Mark Sergeant [EMAIL PROTECTED]
SNSOnline Technical Services.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: USB problems after resume from suspend in current as ofJanuary 9

2003-01-10 Thread Mark Sergeant
Both are turned on yes. Restarting both doesn't work, nothing works when
plugged into the usb ports after a resume.

Cheers,

Mark
On Sat, 2003-01-11 at 07:49, Andrew Y Ng wrote:
 are usbd and moused are turned on.
 
 /ayn
 
 On  0, Mark Sergeant [EMAIL PROTECTED] wrote:
  I'm running a toshiba portege 4000 with -CURRENT as of January 9.
  Suspending and resuming runs fine apart from USB, on resume it is unable
  to recognise my USB mouse (logitech), nothing even registers that it is
  plugged in, nor does the mouse get any power yet on booting normally USB
  works fine. Has anyone got any ideas how I can work around this issues ?
  
  Cheers,
  -- 
  Mark Sergeant [EMAIL PROTECTED]
  SNSOnline Technical Services.
  
  To Unsubscribe: send mail to [EMAIL PROTECTED]
  with unsubscribe freebsd-mobile in the body of the message
-- 
Mark Sergeant [EMAIL PROTECTED]
SNSOnline Technical Services.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



USB problems after resume from suspend in current as of January 9

2003-01-09 Thread Mark Sergeant
I'm running a toshiba portege 4000 with -CURRENT as of January 9.
Suspending and resuming runs fine apart from USB, on resume it is unable
to recognise my USB mouse (logitech), nothing even registers that it is
plugged in, nor does the mouse get any power yet on booting normally USB
works fine. Has anyone got any ideas how I can work around this issues ?

Cheers,
-- 
Mark Sergeant [EMAIL PROTECTED]
SNSOnline Technical Services.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: My network is dead because of this program :(

2001-05-15 Thread Mark Sergeant

Another solution would be to remove this users access ? 

On Tue, 15 May 2001 20:16:15 -0700, Kris Kennaway said:

:: On Wed, May 16, 2001 at 09:20:35AM +0700, John Indra wrote:
::   Dear all...
::   
::   First of all, really sorry for cross-posting...
::   
::   I am running a -CURRENT system (Apr 30th 2001). There is a user in my
::   machine running this small program to DoS my xl0 interface. I doubt that
::   this program is specifically designed for xl cards though.
::  
::  Don't run -current on a production system.  Seriously, just don't,
::  unless you like dealing with this kind of stuff.  The bug report may
::  be useful, but you're playing with fire.
::  
::  Kris
::  

-- 
Mark Sergeant
Unix Systems Administrator

Fortune follows...

Machine-Independent, adj.:
Does not run on any existing machine.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message