DaemonForums  

Go Back   DaemonForums > OpenBSD > OpenBSD General

OpenBSD General Other questions regarding OpenBSD which do not fit in any of the categories below.

Reply
 
Thread Tools Display Modes
  #1   (View Single Post)  
Old 31st March 2010
mfaridi's Avatar
mfaridi mfaridi is offline
Spam Deminer
 
Join Date: May 2008
Location: Afghanistan
Posts: 320
Default can I run fluxbox on pentium 233

I install OpenBSD 4.6 on pentium 233
This is (dmesg; sysctl hw.sensors)

Code:
OpenBSD 4.6 (GENERIC) #58: Thu Jul  9 21:24:42 MDT 2009
    deraadt@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel Pentium/MMX ("GenuineIntel" 586-class) 234 MHz
cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,MMX
real mem  = 133787648 (127MB)
avail mem = 120565760 (114MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 12/09/97, BIOS32 rev. 0 @ 0xfb6e0
apm0 at bios0: Power Management spec V1.2 (slowidle)
apm0: AC on, battery charge unknown
pcibios0 at bios0: rev 2.1 @ 0xf0000/0xbba8
pcibios0: PCI BIOS has 6 Interrupt Routing table entries
pcibios0: PCI Exclusive IRQs: 9 10 11
pcibios0: PCI Interrupt Router at 000:07:0 ("Intel 82371AB PIIX4 ISA" rev 0x00)
pcibios0: PCI bus #0 is the last bus
bios0: ROM list: 0xc0000/0x8000
cpu0 at mainbus0: (uniprocessor)
cpu0: F00F bug workaround installed
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82439TX System" rev 0x01
piixpcib0 at pci0 dev 7 function 0 "Intel 82371AB PIIX4 ISA" rev 0x01
pciide0 at pci0 dev 7 function 1 "Intel 82371AB IDE" rev 0x01: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 1: <QUANTUM FIREBALLlct20 30>
wd0: 8-sector PIO, LBA, 28629MB, 58633344 sectors
wd0(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 2
atapiscsi0 at pciide0 channel 1 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: <ASUS, CD-S400/A, 1.9K> ATAPI 5/cdrom removable
cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
uhci0 at pci0 dev 7 function 2 "Intel 82371AB USB" rev 0x01: irq 11
piixpm0 at pci0 dev 7 function 3 "Intel 82371AB Power" rev 0x01: SMI
iic0 at piixpm0
"eeprom" at iic0 addr 0x50 not configured
spdmem0 at iic0 addr 0x51: 64MB SDRAM non-parity PC100CL3
ne3 at pci0 dev 8 function 0 "Compex Compexe" rev 0x0a: irq 10, address 00:80:48:c3:d5:74
vga1 at pci0 dev 9 function 0 "S3 ViRGE DX/GX" rev 0x01
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
ne4 at pci0 dev 10 function 0 "Compex Compexe" rev 0x0a: irq 9, address 00:80:48:ca:1c:2c
isa0 at piixpcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pmsi0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pmsi0 mux 0
sb0 at isa0 port 0x220/24 irq 5 drq 1: dsp v4.12
midi0 at sb0: <SB MIDI UART>
audio0 at sb0
opl0 at sb0: model OPL3
midi1 at opl0: <SB Yamaha OPL3>
pcppi0 at isa0 port 0x61
midi2 at pcppi0: <PC speaker>
spkr0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
usb0 at uhci0: USB revision 1.0
uhub0 at usb0 "Intel UHCI root hub" rev 1.00/1.00 addr 1
biomask e945 netmask ef45 ttymask ffdf
softraid0 at root
root on wd0a swap on wd0b dump on wd0b
I want use it for desktop
Reply With Quote
  #2   (View Single Post)  
Old 31st March 2010
vermaden's Avatar
vermaden vermaden is offline
Administrator
 
Join Date: Apr 2008
Location: pl_PL.lodz
Posts: 1,056
Default

Yes we can! ... I mean you can

I have run fluxbox on oldschool AMD K6-2 cpu with 192 RAM and Opera on fluxbox run as usual.
__________________
religions, worst damnation of mankind
"If 386BSD had been available when I started on Linux, Linux would probably never had happened." Linus Torvalds

Linux is not UNIX! Face it! It is not an insult. It is fact: GNU is a recursive acronym for “GNU's Not UNIX”.
vermaden's: links resources deviantart spreadbsd
Reply With Quote
  #3   (View Single Post)  
Old 31st March 2010
mfaridi's Avatar
mfaridi mfaridi is offline
Spam Deminer
 
Join Date: May 2008
Location: Afghanistan
Posts: 320
Default

Quote:
Originally Posted by vermaden View Post
Yes we can! ... I mean you can

I have run fluxbox on oldschool AMD K6-2 cpu with 192 RAM and Opera on fluxbox run as usual.
I install Fluxbox with pkg_add and want config Xorg , I do not know why when I run this command
Code:
X -config /root/xorg.conf.new
I see black screen and after that system hang , and everything hang and I can not do anything . ssh connection freez and I have reset system with reset button.
Reply With Quote
  #4   (View Single Post)  
Old 31st March 2010
J65nko J65nko is offline
Administrator
 
Join Date: May 2008
Location: Budel - the Netherlands
Posts: 4,128
Default

You have to configure X from the console, not through an ssh connection.
http://www.openbsd.dk/faq/faq11.html has all the details.
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump
Reply With Quote
  #5   (View Single Post)  
Old 31st March 2010
mfaridi's Avatar
mfaridi mfaridi is offline
Spam Deminer
 
Join Date: May 2008
Location: Afghanistan
Posts: 320
Default

Quote:
Originally Posted by J65nko View Post
You have to configure X from the console, not through an ssh connection.
http://www.openbsd.dk/faq/faq11.html has all the details.
I configure it from console

I said about ssh , because I want say everything is hang and I can reset system by ssh . so I have rest it by reset button
Reply With Quote
  #6   (View Single Post)  
Old 31st March 2010
ocicat ocicat is offline
Administrator
 
Join Date: Apr 2008
Posts: 3,318
Default

Quote:
Originally Posted by mfaridi View Post
I do not know why when I run this command
Code:
X -config /root/xorg.conf.new
I see black screen and after that system hang...
You are omitting important information.

Why are you manually attempting to configure X at all? Quote Section 11.2.6 of the FAQ:
Quote:
...in many cases, X "Just Works" by invoking "startx". In these cases, your hardware will be detected and queried for its abilities, and X will run very well.
Manually creating xorg.conf isn't necessarily required anymore.

Section 11.3.2 discusses changing the color depth & mode only after auto-configuration was found to fail.
Reply With Quote
  #7   (View Single Post)  
Old 31st March 2010
mfaridi's Avatar
mfaridi mfaridi is offline
Spam Deminer
 
Join Date: May 2008
Location: Afghanistan
Posts: 320
Default

Quote:
Originally Posted by ocicat View Post
You are omitting important information.

Why are you manually attempting to configure X at all? Quote Section 11.2.6 of the FAQ:
after I can not config xorg and I run this command
Code:
echo "exec fluxbox" >.xinitrc
I run startx in terminal
But I see black screen again and system hang and I can ssh to system
Reply With Quote
  #8   (View Single Post)  
Old 31st March 2010
ocicat ocicat is offline
Administrator
 
Join Date: Apr 2008
Posts: 3,318
Default

Quote:
Originally Posted by mfaridi View Post
after I can not config xorg and I run this command
Code:
echo "exec fluxbox" >.xinitrc
I run startx in terminal
You are skipping ahead.

What happens when you start X without customizing ~/.xinitrc? Delete ~/.xinitrc & start with the default fvwm(1) window manager first without any ~/.xinitrc at all. Simplify.
Reply With Quote
  #9   (View Single Post)  
Old 31st March 2010
mfaridi's Avatar
mfaridi mfaridi is offline
Spam Deminer
 
Join Date: May 2008
Location: Afghanistan
Posts: 320
Default

Quote:
Originally Posted by ocicat View Post
You are skipping ahead.

What happens when you start X without customizing ~/.xinitrc? Delete ~/.xinitrc & start with the default fvwm(1) window manager first without any ~/.xinitrc at all. Simplify.
I delete .xinitrc and type startx
system hang again , and I can not ssh and ping it
Reply With Quote
Old 31st March 2010
ocicat ocicat is offline
Administrator
 
Join Date: Apr 2008
Posts: 3,318
Default

Quote:
Originally Posted by mfaridi View Post
system hang again , and I can not ssh and ping it
From your dmesg(1) output, you only have 127MB of RAM in the system. This is even below what vermaden quoted from his system.

I see two questions:
  • Can X be run in only 127MB RAM?
  • Is the memory good?
My suggestion would be to ensure the memory is good by downloading memtest86 & strenuously test the memory next. Report your findings afterwards.
Reply With Quote
Old 31st March 2010
mfaridi's Avatar
mfaridi mfaridi is offline
Spam Deminer
 
Join Date: May 2008
Location: Afghanistan
Posts: 320
Default

Quote:
Originally Posted by ocicat View Post
From your dmesg(1) output, you only have 127MB of RAM in the system. This is even below what vermaden quoted from his system.

I see two questions:
  • Can X be run in only 127MB RAM?
  • Is the memory good?
My suggestion would be to ensure the memory is good by downloading memtest86 & strenuously test the memory next. Report your findings afterwards.
thanks
I go to travel for two days
I will test ram after two days and say what happen in next saturday
Reply With Quote
Old 31st March 2010
BSDfan666 BSDfan666 is offline
Real Name: N/A, this is the interweb.
Banned
 
Join Date: Apr 2008
Location: Ontario, Canada
Posts: 2,223
Default

Quote:
Originally Posted by ocicat View Post
Can X be run in only 127MB RAM?
Sure it can, that's plenty of RAM.. I have systems with far less.

X doesn't use that much memory.. nor does fluxbox.

Still, the fact that OpenBSD is freezing is not a good thing.. I do have some P1's around with S3 ViRGE cards, so I can't explain this problem.

@mfaridi, As I suspect the Xorg log to be empty, trying connecting to the system via SSH.. tail -f /var/log/Xorg.0.log, and startx from the console.

At least with that we'll be able to see any obvious issues, although ultimately none of us are kernel/X developers.. so we may not be able to help you.

Can you try a recent snapshot mfaridi? see if the problem remains.. if it does, send a bug report and hopefully someone will be able to help you.

Good luck.
Reply With Quote
Old 31st March 2010
J65nko J65nko is offline
Administrator
 
Join Date: May 2008
Location: Budel - the Netherlands
Posts: 4,128
Default

Has "machdep.allowaperture=2" in /etc/sysctl.conf been set?
Code:
#kern.watchdog.period=32        # >0=Enable hardware watchdog(4) timer if available
#kern.watchdog.auto=0           # 0=Disable automatic watchdog(4) retriggering
machdep.allowaperture=2         # See xf86(4)
#machdep.apmhalt=1              # 1=powerdown hack, try if halt -p doesn't work
#machdep.kbdreset=1             # permit console CTRL-ALT-DEL to do a nice halt
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump
Reply With Quote
Old 1st April 2010
tetrodozombie tetrodozombie is offline
Real Name: bill slusser
Banned
 
Join Date: Dec 2009
Location: atlanta, ga
Posts: 82
Default

I can't believe I've got another OpenBSD laptop running Fluxbox and Fvwm. I like Fvwm, but Flux takes less time to configure on a new system when you don't want to import .fvwmrc config files and pixmap directories. I like starting afresh and learning new things when I can. I've been using OpenBSD for a year now and I don't believe all the hype about it being as difficult as they say. To me it's easier because all the crud in other Unixes just get in the way and block you. I like having a barebones OpenBSD install and setting it up from there. I don't think you even have to run 'Xorg --configure' as root or anything to get Fluxbox working just put 'exec /your/fluxbox/directory/path' in your .xinitrc after you 'sudo make install && sudo make clean' from the /usr/ports/x11/fluxbox directory and it should fly. Don't over complicate things. And, remember you're learning this OS and all it's intricacies and you should be having fun. If not, don't even bother.
Reply With Quote
Old 3rd April 2010
mfaridi's Avatar
mfaridi mfaridi is offline
Spam Deminer
 
Join Date: May 2008
Location: Afghanistan
Posts: 320
Default

Quote:
Originally Posted by J65nko View Post
Has "machdep.allowaperture=2" in /etc/sysctl.conf been set?
Code:
#kern.watchdog.period=32        # >0=Enable hardware watchdog(4) timer if available
#kern.watchdog.auto=0           # 0=Disable automatic watchdog(4) retriggering
machdep.allowaperture=2         # See xf86(4)
#machdep.apmhalt=1              # 1=powerdown hack, try if halt -p doesn't work
#machdep.kbdreset=1             # permit console CTRL-ALT-DEL to do a nice halt
Yes I have it .
Reply With Quote
Old 3rd April 2010
mfaridi's Avatar
mfaridi mfaridi is offline
Spam Deminer
 
Join Date: May 2008
Location: Afghanistan
Posts: 320
Default

Quote:
Originally Posted by BSDfan666 View Post
Sure it can, that's plenty of RAM.. I have systems with far less.

X doesn't use that much memory.. nor does fluxbox.

Still, the fact that OpenBSD is freezing is not a good thing.. I do have some P1's around with S3 ViRGE cards, so I can't explain this problem.

@mfaridi, As I suspect the Xorg log to be empty, trying connecting to the system via SSH.. tail -f /var/log/Xorg.0.log, and startx from the console.

At least with that we'll be able to see any obvious issues, although ultimately none of us are kernel/X developers.. so we may not be able to help you.

Can you try a recent snapshot mfaridi? see if the problem remains.. if it does, send a bug report and hopefully someone will be able to help you.

Good luck.
I do this
first ssh to OpenBSD from another system and run this
Code:
tail -f /var/log/Xorg.0.log
and go to OpenBSD system and run
Code:
startx
and system hang , but I see this log
Code:
tail: /var/log/Xorg.0.log has been replaced, reopening.
(--) checkDevMem: using aperture driver /dev/xf86
(--) Using wscons driver on /dev/ttyC4 in pcvt compatibility mode (version 3.32)

X.Org X Server 1.5.3
Release Date: 5 November 2008
X Protocol Version 11, Revision 0
Build Operating System: OpenBSD 4.6 i386 
Current Operating System: OpenBSD home.4.2.2.4 4.6 GENERIC#58 i386
Build Date: 01 July 2009  05:20:42PM
 
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun Jan 31 18:40:08 2010
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "X.org Configured"
(**) |-->Screen "Screen0" (0)
(**) |   |-->Monitor "Monitor0"
(**) |   |-->Device "Card0"
(**) |-->Input Device "Mouse0"
(**) |-->Input Device "Keyboard0"
(==) Not automatically adding devices
(==) Not automatically enabling devices
(==) Including the default font path /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/TTF/,/usr/X11R6/lib/X11/fonts/OTF,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/100dpi/,/usr/X11R6/lib/X11/fonts/75dpi/.
(**) FontPath set to:
        /usr/X11R6/lib/X11/fonts/misc/,
        /usr/X11R6/lib/X11/fonts/TTF/,
        /usr/X11R6/lib/X11/fonts/OTF,
        /usr/X11R6/lib/X11/fonts/Type1/,
        /usr/X11R6/lib/X11/fonts/100dpi/,
        /usr/X11R6/lib/X11/fonts/75dpi/,
        /usr/X11R6/lib/X11/fonts/misc/,
        /usr/X11R6/lib/X11/fonts/TTF/,
        /usr/X11R6/lib/X11/fonts/OTF,
        /usr/X11R6/lib/X11/fonts/Type1/,
        /usr/X11R6/lib/X11/fonts/100dpi/,
        /usr/X11R6/lib/X11/fonts/75dpi/
(**) ModulePath set to "/usr/X11R6/lib/modules"
(II) Loader magic: 0x3c01e2e0
(II) Module ABI versions:
        X.Org ANSI C Emulation: 0.4
        X.Org Video Driver: 4.1
        X.Org XInput driver : 2.1
        X.Org Server Extension : 1.1
        X.Org Font Renderer : 0.6
(II) Loader running on openbsd
(--) PCI:*(0@0:9:0) S3 ViRGE DX/GX rev 1, Mem @ 0xe0000000/0
(II) System resource ranges:
        [0] -1  0       0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
        [1] -1  0       0x000f0000 - 0x000fffff (0x10000) MX[B]
        [2] -1  0       0x000c0000 - 0x000effff (0x30000) MX[B]
        [3] -1  0       0x00000000 - 0x0009ffff (0xa0000) MX[B]
        [4] -1  0       0x0000ffff - 0x0000ffff (0x1) IX[B]
        [5] -1  0       0x00000000 - 0x000000ff (0x100) IX[B]
(II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
(II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
(II) "glx" will be loaded. This was enabled by default and also specified in the config file.
(II) "freetype" will be loaded. This was enabled by default and also specified in the config file.
(II) "dri" will be loaded. This was enabled by default and also specified in the config file.
(II) LoadModule: "dbe"

(II) Loading /usr/X11R6/lib/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
        compiled for 1.5.3, module version = 1.0.0
        Module class: X.Org Server Extension
        ABI class: X.Org Server Extension, version 1.1
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "dri"

(II) Loading /usr/X11R6/lib/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
        compiled for 1.5.3, module version = 1.0.0
        ABI class: X.Org Server Extension, version 1.1
(II) Loading extension XFree86-DRI
(II) LoadModule: "extmod"

(II) Loading /usr/X11R6/lib/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
        compiled for 1.5.3, module version = 1.0.0
        Module class: X.Org Server Extension
        ABI class: X.Org Server Extension, version 1.1
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "glx"

(II) Loading /usr/X11R6/lib/modules/extensions//libglx.so
(II) Module glx: vendor="X.Org Foundation"
        compiled for 1.5.3, module version = 1.0.0
        ABI class: X.Org Server Extension, version 1.1
(==) AIGLX enabled
(==) Exporting typical set of GLX visuals
(II) Loading extension GLX
(II) LoadModule: "freetype"

(II) Loading /usr/X11R6/lib/modules/fonts//libfreetype.so
(II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
        compiled for 1.5.3, module version = 2.1.0
        Module class: X.Org Font Renderer
        ABI class: X.Org Font Renderer, version 0.6
(II) Loading font FreeType
(II) LoadModule: "s3virge"

(II) Loading /usr/X11R6/lib/modules/drivers//s3virge_drv.so
(II) Module s3virge: vendor="X.Org Foundation"
        compiled for 1.5.3, module version = 1.10.2
        Module class: X.Org Video Driver
        ABI class: X.Org Video Driver, version 4.1
(II) LoadModule: "mouse"

(II) Loading /usr/X11R6/lib/modules/input//mouse_drv.so
(II) Module mouse: vendor="X.Org Foundation"
        compiled for 1.5.3, module version = 1.4.0
        Module class: X.Org XInput Driver
        ABI class: X.Org XInput driver, version 2.1
(II) LoadModule: "kbd"

(II) Loading /usr/X11R6/lib/modules/input//kbd_drv.so
(II) Module kbd: vendor="X.Org Foundation"
        compiled for 1.5.3, module version = 1.3.2
        Module class: X.Org XInput Driver
        ABI class: X.Org XInput driver, version 2.1
(II) S3VIRGE: driver (version 1.10.2) for S3 ViRGE chipsets: virge, 86C325,
        virge vx, 86C988, virge dx, virge gx, 86C375, 86C385, virge gx2,
        86C357, virge mx, 86C260, virge mx+, 86C280, trio 3d, 86C365,
        trio 3d/2x, 86C362, 86C368
(II) Primary Device is: PCI 00@00:09:0
(WW) Falling back to old probe method for s3virge
(--) Chipset virge dx found
(II) resource ranges after xf86ClaimFixedResources() call:
        [0] -1  0       0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
        [1] -1  0       0x000f0000 - 0x000fffff (0x10000) MX[B]
        [2] -1  0       0x000c0000 - 0x000effff (0x30000) MX[B]
        [3] -1  0       0x00000000 - 0x0009ffff (0xa0000) MX[B]
        [4] -1  0       0x0000ffff - 0x0000ffff (0x1) IX[B]
        [5] -1  0       0x00000000 - 0x000000ff (0x100) IX[B]
(II) resource ranges after probing:
        [0] -1  0       0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
        [1] -1  0       0x000f0000 - 0x000fffff (0x10000) MX[B]
        [2] -1  0       0x000c0000 - 0x000effff (0x30000) MX[B]
        [3] -1  0       0x00000000 - 0x0009ffff (0xa0000) MX[B]
        [4] 0   0       0x000a0000 - 0x000affff (0x10000) MS[B]
        [5] 0   0       0x000b0000 - 0x000b7fff (0x8000) MS[B]
        [6] 0   0       0x000b8000 - 0x000bffff (0x8000) MS[B]
        [7] -1  0       0x0000ffff - 0x0000ffff (0x1) IX[B]
        [8] -1  0       0x00000000 - 0x000000ff (0x100) IX[B]
        [9] 0   0       0x000003b0 - 0x000003bb (0xc) IS[B]
        [10] 0  0       0x000003c0 - 0x000003df (0x20) IS[B]
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"

(II) Loading /usr/X11R6/lib/modules//libvgahw.so
(II) Module vgahw: vendor="X.Org Foundation"
        compiled for 1.5.3, module version = 0.1.0
        ABI class: X.Org Video Driver, version 4.1
(==) S3VIRGE(0): Depth 24, (--) framebuffer bpp 24
(==) S3VIRGE(0): RGB weight 888
(==) S3VIRGE(0): Default visual is TrueColor
(==) S3VIRGE(0): Using HW Cursor
(==) S3VIRGE(0): mx_cr3a_fix.
(II) Loading sub module "vbe"
(II) LoadModule: "vbe"

(II) Loading /usr/X11R6/lib/modules//libvbe.so
(II) Module vbe: vendor="X.Org Foundation"
        compiled for 1.5.3, module version = 1.1.0
        ABI class: X.Org Video Driver, version 4.1
(II) Loading sub module "int10"
(II) LoadModule: "int10"

(II) Loading /usr/X11R6/lib/modules//libint10.so
(II) Module int10: vendor="X.Org Foundation"
        compiled for 1.5.3, module version = 1.0.0
        ABI class: X.Org Video Driver, version 4.1
(II) S3VIRGE(0): initializing int10
(II) S3VIRGE(0): Primary V_BIOS segment is: 0xc000
(II) S3VIRGE(0): VESA BIOS detected
(II) S3VIRGE(0): VESA VBE Version 2.0
(II) S3VIRGE(0): VESA VBE Total Mem: 2048 kB
(II) S3VIRGE(0): VESA VBE OEM: S3 Incorporated. ViRGE /DX /GX
(II) S3VIRGE(0): VESA VBE OEM Software Rev: 1.1
(II) S3VIRGE(0): VESA VBE OEM Vendor: S3 Incorporated.
(II) S3VIRGE(0): VESA VBE OEM Product: ViRGE /DX /GX
(II) S3VIRGE(0): VESA VBE OEM Product Rev: Rev B
(--) S3VIRGE(0): Chipset: "virge dx"
(==) S3VIRGE(0): XVideo supported.
(II) S3VIRGE(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
(II) S3VIRGE(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Module "ddc" already built-in
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Module "ddc" already built-in
(II) S3VIRGE(0): VESA VBE DDC supported
(II) S3VIRGE(0): VESA VBE DDC Level 2
(II) S3VIRGE(0): VESA VBE DDC transfer in appr. 1 sec.
(II) S3VIRGE(0): VESA VBE DDC read successfully
(II) S3VIRGE(0): Manufacturer: GSM  Model: 42d1  Serial#: 0
(II) S3VIRGE(0): Year: 2001  Week: 0
(II) S3VIRGE(0): EDID Version: 1.1
(II) S3VIRGE(0): Analog Display Input,  Input Voltage Level: 0.700/0.300 V
(II) S3VIRGE(0): Sync:  Separate
(II) S3VIRGE(0): Max Image Size [cm]: horiz.: 31  vert.: 23
(II) S3VIRGE(0): Gamma: 2.85
(II) S3VIRGE(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
(II) S3VIRGE(0): redX: 0.631 redY: 0.328   greenX: 0.295 greenY: 0.600
(II) S3VIRGE(0): blueX: 0.144 blueY: 0.070   whiteX: 0.282 whiteY: 0.298
(II) S3VIRGE(0): Supported VESA Video Modes:
(II) S3VIRGE(0): 720x400@70Hz
(II) S3VIRGE(0): 720x400@88Hz
(II) S3VIRGE(0): 640x480@60Hz
(II) S3VIRGE(0): 640x480@67Hz
(II) S3VIRGE(0): 640x480@72Hz
(II) S3VIRGE(0): 640x480@75Hz
(II) S3VIRGE(0): 800x600@56Hz
(II) S3VIRGE(0): 800x600@60Hz
(II) S3VIRGE(0): 800x600@72Hz
(II) S3VIRGE(0): 800x600@75Hz
(II) S3VIRGE(0): 832x624@75Hz
(II) S3VIRGE(0): 1024x768@87Hz (interlaced)
(II) S3VIRGE(0): 1024x768@60Hz
(II) S3VIRGE(0): 1024x768@70Hz
(II) S3VIRGE(0): 1024x768@75Hz
(II) S3VIRGE(0): 1152x870@75Hz
(II) S3VIRGE(0): Manufacturer's mask: 0
(II) S3VIRGE(0): Supported Future Video Modes:
(II) S3VIRGE(0): #0: hsize: 640  vsize 480  refresh: 75  vid: 20273
(II) S3VIRGE(0): #1: hsize: 640  vsize 480  refresh: 85  vid: 22833
(II) S3VIRGE(0): #2: hsize: 800  vsize 600  refresh: 75  vid: 20293
(II) S3VIRGE(0): #3: hsize: 800  vsize 600  refresh: 85  vid: 22853
(II) S3VIRGE(0): #4: hsize: 1024  vsize 768  refresh: 75  vid: 20321
(II) S3VIRGE(0): #5: hsize: 1024  vsize 768  refresh: 85  vid: 22881
(II) S3VIRGE(0): #6: hsize: 1280  vsize 1024  refresh: 60  vid: 32897
(II) S3VIRGE(0): #7: hsize: 832  vsize 624  refresh: 75  vid: 20297
(II) S3VIRGE(0): Supported additional Video Mode:
(II) S3VIRGE(0): clock: 36.0 MHz   Image Size:  310 x 230 mm
(II) S3VIRGE(0): h_active: 640  h_sync: 696  h_sync_end 752 h_blank_end 832 h_border: 0
(II) S3VIRGE(0): v_active: 480  v_sync: 481  v_sync_end 484 v_blanking: 509 v_border: 0
(II) S3VIRGE(0): Supported additional Video Mode:
(II) S3VIRGE(0): clock: 108.0 MHz   Image Size:  310 x 230 mm
(II) S3VIRGE(0): h_active: 1280  h_sync: 1328  h_sync_end 1440 h_blank_end 1688 h_border: 0
(II) S3VIRGE(0): v_active: 1024  v_sync: 1025  v_sync_end 1028 v_blanking: 1066 v_border: 0
(II) S3VIRGE(0): Ranges: V min: 50 V max: 160 Hz, H min: 30 H max: 70 kHz, PixClock max 110 MHz
(II) S3VIRGE(0): Monitor name: FLATRON 775FT
(II) S3VIRGE(0): Number of EDID sections to follow: 10
(II) S3VIRGE(0): EDID (in hex):
(II) S3VIRGE(0):        00ffffffffffff001e6dd14200000000
(II) S3VIRGE(0):        000b0101081f17b9e88ac5a1544b9924
(II) S3VIRGE(0):        12484cfffe80314f3159454f4559614f
(II) S3VIRGE(0):        61598180494f100e80c020e01d103838
(II) S3VIRGE(0):        130036e610000018302a009851002a40
(II) S3VIRGE(0):        3070130036e61000001e000000fd0032
(II) S3VIRGE(0):        a01e460b000a202020202020000000fc
(II) S3VIRGE(0):        00464c4154524f4e2037373546540a51
(II) S3VIRGE(0): EDID vendor "GSM", prod id 17105
(II) S3VIRGE(0): Using hsync ranges from config file
(II) S3VIRGE(0): Using vrefresh ranges from config file
(II) S3VIRGE(0): Printing DDC gathered Modelines:
(II) S3VIRGE(0): Modeline "640x480"x0.0   36.00  640 696 752 832  480 481 484 509 -hsync -vsync (43.3 kHz)
(II) S3VIRGE(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
(II) S3VIRGE(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz)
(II) S3VIRGE(0): Modeline "800x600"x0.0   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz)
(II) S3VIRGE(0): Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz)
(II) S3VIRGE(0): Modeline "640x480"x0.0   31.50  640 664 704 832  480 489 491 520 -hsync -vsync (37.9 kHz)
(II) S3VIRGE(0): Modeline "640x480"x0.0   30.24  640 704 768 864  480 483 486 525 -hsync -vsync (35.0 kHz)
(II) S3VIRGE(0): Modeline "640x480"x0.0   25.20  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz)
(II) S3VIRGE(0): Modeline "720x400"x0.0   35.50  720 738 846 900  400 421 423 449 -hsync -vsync (39.4 kHz)
(II) S3VIRGE(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz)
(II) S3VIRGE(0): Modeline "1024x768"x0.0   78.80  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.1 kHz)
(II) S3VIRGE(0): Modeline "1024x768"x0.0   75.00  1024 1048 1184 1328  768 771 777 806 -hsync -vsync (56.5 kHz)
(II) S3VIRGE(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz)
(II) S3VIRGE(0): Modeline "1024x768"x0.0   44.90  1024 1032 1208 1264  768 768 776 817 interlace +hsync +vsync (35.5 kHz)
(II) S3VIRGE(0): Modeline "832x624"x0.0   57.28  832 864 928 1152  624 625 628 667 -hsync -vsync (49.7 kHz)
(II) S3VIRGE(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz)
(II) S3VIRGE(0): Modeline "800x600"x0.0   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync (48.1 kHz)
(II) S3VIRGE(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz)
(II) S3VIRGE(0): Modeline "640x480"x75.0   30.72  640 664 728 816  480 481 484 502 -hsync +vsync (37.7 kHz)
(II) S3VIRGE(0): Modeline "640x480"x85.0   35.71  640 672 736 832  480 481 484 505 -hsync +vsync (42.9 kHz)
(II) S3VIRGE(0): Modeline "800x600"x75.0   48.91  800 840 920 1040  600 601 604 627 -hsync +vsync (47.0 kHz)
(II) S3VIRGE(0): Modeline "800x600"x85.0   56.55  800 840 928 1056  600 601 604 630 -hsync +vsync (53.5 kHz)
(II) S3VIRGE(0): Modeline "1024x768"x75.0   81.80  1024 1080 1192 1360  768 769 772 802 -hsync +vsync (60.2 kHz)
(II) S3VIRGE(0): Modeline "1024x768"x85.0   94.39  1024 1088 1200 1376  768 769 772 807 -hsync +vsync (68.6 kHz)
(II) S3VIRGE(0): Modeline "1280x1024"x60.0  108.88  1280 1360 1496 1712  1024 1025 1028 1060 -hsync +vsync (63.6 kHz)
(II) S3VIRGE(0): Modeline "832x624"x75.0   53.20  832 872 960 1088  624 625 628 652 -hsync +vsync (48.9 kHz)
(==) S3VIRGE(0): Using gamma correction (1.0, 1.0, 1.0)
(--) S3VIRGE(0): videoram:  2048k

Fatal server error:
Caught signal 11.  Server aborting
I do not have .xinitrc in home directory.
Reply With Quote
Old 3rd April 2010
mfaridi's Avatar
mfaridi mfaridi is offline
Spam Deminer
 
Join Date: May 2008
Location: Afghanistan
Posts: 320
Default

I want go to check RAM with memory test .
I have only one 128 MB ram and I want test it.
Reply With Quote
Old 3rd April 2010
ocicat ocicat is offline
Administrator
 
Join Date: Apr 2008
Posts: 3,318
Default

Quote:
Originally Posted by mfaridi View Post
I want go to check RAM with memory test .
I have only one 128 MB ram and I want test it.
It is unclear whether you are telling us you are doing so, or whether you are asking the question about how to do it.

If the latter, look at the Website mentioned in response #10 in this thread. The Website has ISO's at the bottom of the home page which can be burned containing the application needed to test memory.

Reply With Quote
Old 3rd April 2010
mfaridi's Avatar
mfaridi mfaridi is offline
Spam Deminer
 
Join Date: May 2008
Location: Afghanistan
Posts: 320
Default

I run memory test for 180 min and this program dose not find error on RAM , so after 180 min , I understand my RAM dose not has problem , I think problem is another thing .
__________________
http://www.mfaridi.com
First site about FreeBSD and OpenBSD in persian or Farsi.
Reply With Quote
Old 3rd April 2010
jggimi's Avatar
jggimi jggimi is offline
More noise than signal
 
Join Date: May 2008
Location: USA
Posts: 7,977
Default

Do you have swap space defined, mfaridi? How much?

180 minutes (2.5 hrs) is -not usually enough- to confirm RAM is working. I've had memory tests fail after 22 hours.
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Fluxbox don't start Artur FreeBSD General 4 3rd September 2009 01:04 PM
fluxbox crash? HELP bsdnewbie999 OpenBSD General 9 2nd April 2009 04:35 AM
HOWTO: Fluxbox from GIT vermaden Guides 6 3rd November 2008 12:13 PM
OpenBSD 4.3, XDM + FluxBox WeakSauceIII General software and network 2 19th May 2008 08:34 PM
gtk themes for fluxbox rex FreeBSD General 0 18th May 2008 03:24 AM


All times are GMT. The time now is 07:34 PM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Content copyright © 2007-2010, the authors
Daemon image copyright ©1988, Marshall Kirk McKusick