Re: 5.2 STABLE?

2003-11-26 Thread Ryan Sommers
Document of interest to you:
http://www.freebsd.org/doc/en_US.ISO8859-1/articles/5-roadmap/index.html 

The schedule can be found at (when RELENG_5 is scheduled to be branched):
http://www.freebsd.org/doc/en_US.ISO8859-1/articles/5-roadmap/schedule.html 

Thomas T. Veldhouse writes: 

Will 5.2-RELEASE mark the beginning of the new STABLE branch?  If not, do we
know approximately when this branch is planned? 

Thanks in advance, 

Tom Veldhouse 

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


--
Ryan leadZERO Sommers
Gamer's Impact President
[EMAIL PROTECTED]
ICQ: 1019590
AIM/MSN: leadZERO 

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


Re: 5.2-BETA: giving up on 4 buffers (ata)

2003-11-26 Thread Ryan Sommers
I'll also note in my FreeBSD current debugging of some drivers it was
about a 50/50 shot as to if this would happen.  Having to fsck every 
other reboot was only made less painful by the background fsck thing. 

Don't some BIOS' protect the superblocks as a kind of virus protection? 
Could this be related to them? 

--
Ryan leadZERO Sommers
Gamer's Impact President
[EMAIL PROTECTED]
ICQ: 1019590
AIM/MSN: leadZERO 

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


ACPI and APM testing on Dell Inspiron 8200

2003-11-22 Thread Ryan Sommers
I'm having difficulty getting battery and thermal status. If I compile the 
kernel with APM support I get battery statistics but if I try to put 
APM/ACPI in the kernel ACPI reports that another PM system is enabled and 
doesn't load the /dev/acpi device. If I take APM out and compile in ACPI I 
get /dev/acpi and all that goes with it; but the battery status does not 
show up correctly. 

I've attached 2 files, test1.log which is with: 

device acpi
device apm 

in the kernel. (Which brings me to the point, in the NOTES file it's noted 
that device acpi is deprecated, but if you don't add the device you don't 
get acpi support...) 

Then test2.log is with only acpi support compiled in. 

Another thing I tested while I was testing was suspend states. With apm 
compiled in I tried doing a 'apm -z'. Suspending seems to work fine, 
however, when you try to bring it back it says it is resyncing the disks 
(think this was the last message) and then it sits there frozen; meanwhile 
the harddrive light is constantly on. I let it sit there for a minute and 
still had no signs of activity. If I go into X suspend works with the only 
hitch that the screen goes all white before it blacks out and upon 
unsuspending the screen is still all white with traces of colors of the 
background. 

Then with ACPI compiled in I tried dropping it to S1 with 'acpiinfo -s 1'. 
Again it seems to drop into the state just fine, however the LCD does not 
black out upon suspending. But the power light starts flashing like it 
should. Then when you hit the power button the screen blanks out. However, 
otherwise it unsuspends, I was able to sucessfully Ssh into the machine. I 
don't know if it's related but changing the hw.acpi.reset_video to 0 made no 
difference. Also to note, with X running S1 works fine with the exception 
that when it is suspended the display does not turn off, but when you come 
out of S1 the display goes back into X. I was able to sucessfully suspend it 
and bring it back using the lidswitch too, with same exceptions. S3, S4 and 
S5 all result in the computer rebooting though. 

Processor is P4m. Video card is ATI Radeon 9k mobility. 

If you need any other information please feel free to contact me. 

--
Ryan leadZERO Sommers
Gamer's Impact President
[EMAIL PROTECTED]
ICQ: 1019590
AIM/MSN: leadZERO 

-= http://www.gamersimpact.com =-Script started on Sat Nov 22 13:53:08 2003
lilshadow# dmsegsg| | grep -i apm
apm0: APM BIOS on motherboard
apm0: found APM BIOS v1.2, connected at v1.2
WARNING: apm_saver module requires apm enabled
lilshadow# dmesg | grep -i apmacpi
Preloaded acpi_dsdt /boot/acpi_dsdt.aml at 0xc07811cc.
  
Features=0xbfebf9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE
ACPI: DSDT was overridden.
ACPI-0375: *** Info: Table [DSDT] replaced by host OS
acpi0: Other PM system enabled.
lilshadow# apm
APM version: 1.2
APM Management: Enabled
AC Line status: on-line
Battery status: charging
Remaining battery life: 100%
Remaining battery time:  2:34:00
Number of batteries: 2
Battery 0:
Battery status: not present
Battery 1:
Battery status: charging
Remaining battery life: 100%
Remaining battery time:  2:34:00
Resume timer: disabled
Resume on ring indicator: disabled
APM Capabilities:
global suspend state
resume timer from suspend
lilshadow# acpiinfoconf -i 0
acpiconf: /dev/acpi: No such file or directory
lilshadow# acpiconf -i 01
acpiconf: /dev/acpi: No such file or directory
lilshadow# exit
exit

Script done on Sat Nov 22 13:53:50 2003
Script started on Sat Nov 22 14:11:19 2003
lilshadow# dmesg | grep -i apm
lilshadow# dmesg | grep -i apmacipi
Preloaded acpi_dsdt /boot/acpi_dsdt.aml at 0xc077e1cc.
  
Features=0xbfebf9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE
ACPI: DSDT was overridden.
ACPI-0375: *** Info: Table [DSDT] replaced by host OS
acpi0: DELL   CPi R   on motherboard
Timecounter ACPI-fast frequency 3579545 Hz quality 1000
acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0
acpi_cpu0: CPU on acpi0
acpi_tz0: Thermal Zone on acpi0
acpi_acad0: AC Adapter on acpi0
acpi_cmbat0: Control Method Battery on acpi0
acpi_cmbat1: Control Method Battery on acpi0
acpi_lid0: Control Method Lid Switch on acpi0
acpi_button0: Power Button on acpi0
acpi_button1: Sleep Button on acpi0
pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0
pci0: ACPI PCI bus on pcib0
pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0
pci1: ACPI PCI bus on pcib1
pcib2: ACPI PCI-PCI bridge at device 30.0 on pci0
pci2: ACPI PCI bus on pcib2
atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0
fdc0: Enhanced floppy controller (i82077, NE72065 or clone) port 0x3f7,0x3f2-0x3f5 
irq 6 drq 2 on acpi0
sio0 port 0x3f8-0x3ff irq 4 on acpi0
ppc0 port 

DStumbler / BSD-AirTools Error with new Wi code?

2003-11-19 Thread Ryan Sommers
I have been getting the following error when attempting to use dstumbler 
with 5.1-RELEASE-p10: 

error: unable to ioctl device socket: Invalid argument 

After much searching around newsgroups/mailing lists it looks like the Wi(4) 
code was changed and dstumbler never got updated. I found one patch that 
supposedly fixed support on some cards, however, it didn't seem to work on 
mine. Has anyone worked on this in -current? Or does anyone know of patches 
that aren't in CVS yet that might work? 

Here is my info:
lilshadow# dmesg |grep wi0
wi0: Dell TrueMobile 1150 Series PC Card at port 0x100-0x13f irq 11 
function 0 config 1 on pccard2
wi0: 802.11 address: 00:02:2d:84:22:18
wi0: using Lucent Embedded WaveLAN/IEEE
wi0: Lucent Firmware: Station (8.10.1)
wi0: supported rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 

Wireless card works fine otherwise. 

Thanks for the help in advance. 

--
Ryan leadZERO Sommers
Gamer's Impact President
[EMAIL PROTECTED]
ICQ: 1019590
AIM/MSN: leadZERO 

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


Re: DStumbler / BSD-AirTools Error with new Wi code?

2003-11-19 Thread Ryan Sommers
I upgraded to 0.3 and installed. However, I'm still getting errors no matter 
how I run it: 

dstumbler wi0 -o
error: cannot use monitor mode on non-prism2 cards 

dstumbler wi0 -s
error: unable to ioctl device socket: Invalid argument 

same for just running dstumbler wi0. 

Any ideas? 

Sean Chittenden writes: 

I have been getting the following error when attempting to use dstumbler 
with 5.1-RELEASE-p10:  

error: unable to ioctl device socket: Invalid argument  

After much searching around newsgroups/mailing lists it looks like the 
Wi(4) code was changed and dstumbler never got updated. I found one patch 
that supposedly fixed support on some cards, however, it didn't seem to 
work on mine. Has anyone worked on this in -current? Or does anyone know of 
patches that aren't in CVS yet that might work? 
I just updated it yesterday.  Update to 0.3 and things should work: 

dstumbler wi0 -o 

-sc 

--
Sean Chittenden


--
Ryan leadZERO Sommers
Gamer's Impact President
[EMAIL PROTECTED]
ICQ: 1019590
AIM/MSN: leadZERO 

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


Re: 5.0 Install Troubles

2002-12-19 Thread Ryan Sommers
To see if it was related to installing in a vmware vm I whipped out the
laptop last night and ran an install. Sure enough I ran into the same
problem on the laptop when trying to install only base + linux
compatability. When it gets to installing linux compatability it
complains about libssl not being installed.

So, is this a 5.0 bug? I'm running an install of minimal right now to
see if that works. I really don't like having to install a whole bunch
of documentation that I already have in a number of other boxes, anyone
know why libssl isn't in base?

Ryan

On Thu, 2002-12-19 at 04:29, Kris Kennaway wrote:
 On Wed, Dec 18, 2002 at 05:53:17PM -0600, Ryan Sommers wrote:
  Yah, there isn't a secure dist. I'm doing a full install now, to see if
  it hits it. I don't understand why only installing base would work on
  4.7 but not on 5.0.
 
 I believe it's called 'crypto' not 'secure'.  I'm not sure why you ran
 into this problem..it's not supposed to be mandatory.
 
 Kris
-- 
Ryan leadZERO Sommers
[EMAIL PROTECTED]
ICQ: 1019590   AIM/MSN: leadZERO




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



Port package on RC1

2002-12-17 Thread Ryan Sommers
Today for the fun of it I decided to try installing RC1 on VMware
running in Win2K. (very bored today). Everything goes fine until the
ports installation. I choose all the default options, I have it running
in a 256mb of RAM 10gb virtual disk environment. Like I said up until
the ports installation everything goes as expected. Then when it gets to
unpacking the ports collection the rate goes down from about 1mb/sec for
the other packages and it's now still installing at 1.5kb/sec. This is
the first time I've tried installing RC1, I installed DP2 on a laptop
and it went smooth. Has anyone else experienced this or is this related
to running it in a VM environment. 

What seems odd to me is that CPU utilization for the VMware process is
at 99% constantly. I'm wondering what it's doing because it isn't
copying over ports very fast.

Ryan

PS I know this isn't the way it's meant to be run, I'm just curious why
the rest would install fine until ports. (This is the second time I've
tried.)

-- 
Ryan leadZERO Sommers
[EMAIL PROTECTED]
ICQ: 1019590   AIM/MSN: leadZERO




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



[Fwd: Compiling -CURRENT and PCMCIA support.]

2002-11-22 Thread Ryan Sommers
I got this back so I will try resending/asking it.

-Forwarded Message-

 From: Ryan Sommers [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Subject: Compiling -CURRENT and PCMCIA support.
 Date: 21 Nov 2002 12:50:53 -0600
 
 ?On Tue, 2002-11-19 at 22:13, Ryan Sommers wrote:
  My question is could I keep and build the CURRENT source tree on the
  FreeBSD desktop, mount it over NFS to the laptop, and install it over
  the NFS mount? 
 
 Is the kernel on the 5.0SP2 ISO built with PCCard support? I installed
 from CD-ROM onto a Compaq laptop only to notice nothing about the PCMCIA
 Ethernet card I had in the dmesg output. I saw the PCCARD Support
 section of the release notes and I'm wondering if this has anything to
 do with it.
 
 I'm probably going to have to compile a kernel with either the OLDCARD
 support or some other options so my next question, is it possible to
 build a -CURRENT kernel on 4.7? I'm getting the following when I tried
 to build a kernel for the laptop on my 4.7 workstation. Note: I
 installed net/cvsup-mirror and then fetched current with the following
 supfile and all of this is run as my cvs user:
 
 *default host=localhost
 
 *default prefix=/usr/home/cvs/
 *default base=/usr/home/cvs/
 *default release=cvs delete use-rel-suffix
 *default tag=.
 
 #cvs-all
 src-all
 
 
 
 bash-2.05a$ uname -a
 FreeBSD lobo 4.7-RELEASE FreeBSD 4.7-RELEASE #5: Fri Nov  8 15:29:17 CST
 2002 ryans@lobo:/usr/obj/usr/src/sys/LOBO  i386
 bash-2.05a$ make buildkernel KERNCONF=LAPTOP MAKEOBJDIRPREFIX=~
 make: no target to make.
 /usr/home/cvs/src/Makefile.inc1, line 141: warning: make -f /dev/null
 -m /usr/home/cvs/src/share/mk  CPUTYPE=dummy -V CPUTYPE returned
 non-zero status
 
 --
  Kernel build for LAPTOP started on Thu Nov 21 09:37:05 CST 2002
 --
 === LAPTOP
 mkdir -p /usr/home/cvs/usr/home/cvs/src/sys
 cd /usr/home/cvs/src/sys/i386/conf; 
 
PATH=/usr/home/cvs/usr/home/cvs/src/i386/usr/sbin:/usr/home/cvs/usr/home/cvs/src/i386/usr/bin:/usr/home/cvs/usr/home/cvs/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
  config  -d /usr/home/cvs/usr/home/cvs/src/sys/LAPTOP  
/usr/home/cvs/src/sys/i386/conf/LAPTOP
 ../../conf/files: coda/coda_fbsd.c must be optional, mandatory or
 standard
 Your version of config(8) is out of sync with your kernel source.
 *** Error code 1
 
 Stop in /usr/home/cvs/src.
 *** Error code 1
 
 Stop in /usr/home/cvs/src.
 bash-2.05a$
 
 Ryan.
 
 -- 
 Ryan leadZERO Sommers
 [EMAIL PROTECTED]
 ICQ: 1019590   AIM/MSN: leadZERO
 
 
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-current in the body of the message
-- 
Ryan leadZERO Sommers
[EMAIL PROTECTED]
ICQ: 1019590   AIM/MSN: leadZERO




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



Compiling -CURRENT and PCMCIA support.

2002-11-21 Thread Ryan Sommers
?On Tue, 2002-11-19 at 22:13, Ryan Sommers wrote:
 My question is could I keep and build the CURRENT source tree on the
 FreeBSD desktop, mount it over NFS to the laptop, and install it over
 the NFS mount? 

Is the kernel on the 5.0SP2 ISO built with PCCard support? I installed
from CD-ROM onto a Compaq laptop only to notice nothing about the PCMCIA
Ethernet card I had in the dmesg output. I saw the PCCARD Support
section of the release notes and I'm wondering if this has anything to
do with it.

I'm probably going to have to compile a kernel with either the OLDCARD
support or some other options so my next question, is it possible to
build a -CURRENT kernel on 4.7? I'm getting the following when I tried
to build a kernel for the laptop on my 4.7 workstation. Note: I
installed net/cvsup-mirror and then fetched current with the following
supfile and all of this is run as my cvs user:

*default host=localhost

*default prefix=/usr/home/cvs/
*default base=/usr/home/cvs/
*default release=cvs delete use-rel-suffix
*default tag=.

#cvs-all
src-all



bash-2.05a$ uname -a
FreeBSD lobo 4.7-RELEASE FreeBSD 4.7-RELEASE #5: Fri Nov  8 15:29:17 CST
2002 ryans@lobo:/usr/obj/usr/src/sys/LOBO  i386
bash-2.05a$ make buildkernel KERNCONF=LAPTOP MAKEOBJDIRPREFIX=~
make: no target to make.
/usr/home/cvs/src/Makefile.inc1, line 141: warning: make -f /dev/null
-m /usr/home/cvs/src/share/mk  CPUTYPE=dummy -V CPUTYPE returned
non-zero status

--
 Kernel build for LAPTOP started on Thu Nov 21 09:37:05 CST 2002
--
=== LAPTOP
mkdir -p /usr/home/cvs/usr/home/cvs/src/sys
cd /usr/home/cvs/src/sys/i386/conf; 
PATH=/usr/home/cvs/usr/home/cvs/src/i386/usr/sbin:/usr/home/cvs/usr/home/cvs/src/i386/usr/bin:/usr/home/cvs/usr/home/cvs/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
  config  -d /usr/home/cvs/usr/home/cvs/src/sys/LAPTOP  
/usr/home/cvs/src/sys/i386/conf/LAPTOP
../../conf/files: coda/coda_fbsd.c must be optional, mandatory or
standard
Your version of config(8) is out of sync with your kernel source.
*** Error code 1

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

Stop in /usr/home/cvs/src.
bash-2.05a$

Ryan.

-- 
Ryan leadZERO Sommers
[EMAIL PROTECTED]
ICQ: 1019590   AIM/MSN: leadZERO




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