Linux-Hardware Digest #341, Volume #10 Thu, 27 May 99 12:13:30 EDT
Contents:
Re: Redhat 6.0 on an IBM thinkpad 360CSE? ("Jeff Volckaert")
#BR on SMPs on LX (Suran)
sb module question (mpu_irq option) (Eugene VonNiederhausern)
How to get multiple replies quickly ([EMAIL PROTECTED])
Re: Redhat 6.0 on an IBM thinkpad 360CSE? ("Jeff Volckaert")
Re: Internal Modem Help (Johan Kullstam)
Re: HP LaserJet 4M Plus (Johan Kullstam)
Re: smp multi cpu motherboards - multithreading (bryan)
Re: Dual Celeron's and SMP Performance Problems ("Tony Platt")
is this Sound Card supported? ([EMAIL PROTECTED])
Re: Dual Celeron's and SMP Performance Problems (Totally Lost)
Re: Attempted RedHat install kills HDD ("Curt")
----------------------------------------------------------------------------
From: "Jeff Volckaert" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.portable,comp.os.linux.setup,comp.os.linux.x
Subject: Re: Redhat 6.0 on an IBM thinkpad 360CSE?
Date: Thu, 27 May 1999 09:31:21 -0400
I've attached my XF86Config file. If anyone can see anything wrong please
let me know.
TIA,
Jeff Volckaert
*** SNIP ***
# File generated by XConfigurator.
# **********************************************************************
# Refer to the XF86Config(4/5) man page for details about the format of
# this file.
# **********************************************************************
# **********************************************************************
# Files section. This allows default font and rgb paths to be set
# **********************************************************************
Section "Files"
# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
RgbPath "/usr/X11R6/lib/X11/rgb"
# Multiple FontPath entries are allowed (they are concatenated together)
# By default, Red Hat 6.0 and later now use a font server independent of
# the X server to render fonts.
FontPath "unix/:-1"
EndSection
# **********************************************************************
# Server flags section.
# **********************************************************************
Section "ServerFlags"
# Uncomment this to cause a core dump at the spot where a signal is
# received. This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging
#NoTrapSignals
# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.
#DontZap
# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.
#DontZoom
EndSection
# **********************************************************************
# Input devices
# **********************************************************************
# **********************************************************************
# Keyboard section
# **********************************************************************
Section "Keyboard"
Protocol "Standard"
# when using XQUEUE, comment out the above line, and uncomment the
# following line
#Protocol "Xqueue"
AutoRepeat 500 5
# Let the server do the NumLock processing. This should only be
# required when using pre-R6 clients
#ServerNumLock
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
#Xleds 1 2 3
#To set the LeftAlt to Meta, RightAlt key to ModeShift,
#RightCtl key to Compose, and ScrollLock key to ModeLock:
LeftAlt Meta
RightAlt Meta
ScrollLock Compose
RightCtl Control
# To disable the XKEYBOARD extension, uncomment XkbDisable.
# XkbDisable
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# XkbModel "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# XkbModel "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# XkbLayout "de"
# or:
# XkbLayout "de"
# XkbVariant "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# XkbOptions "ctrl:swapcaps"
# These are the default XKB settings for XFree86
# XkbRules "xfree86"
# XkbModel "pc101"
# XkbLayout "us"
# XkbVariant ""
# XkbOptions ""
XkbKeycodes "xfree86"
XkbTypes "default"
XkbCompat "default"
XkbSymbols "us(pc101)"
XkbGeometry "pc"
XkbRules "xfree86"
XkbModel "pc101"
XkbLayout "us"
EndSection
# **********************************************************************
# Pointer section
# **********************************************************************
Section "Pointer"
Protocol "PS/2"
Device "/dev/mouse"
# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
# Protocol "Xqueue"
# Baudrate and SampleRate are only for some Logitech mice
# BaudRate 9600
# SampleRate 150
# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
Emulate3Buttons
Emulate3Timeout 50
# ChordMiddle is an option for some 3-button Logitech mice
# ChordMiddle
EndSection
# **********************************************************************
# Monitor section
# **********************************************************************
# Any number of monitor sections may be present
Section "Monitor"
Identifier "My Monitor"
VendorName "Unknown"
ModelName "Unknown"
# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
HorizSync 31.5
# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
VertRefresh 50-70
# Modes can be specified in two formats. A compact one-line format, or
# a multi-line format.
# These two are equivalent
# ModeLine "1024x768i" 45 1024 1048 1208 1264 768 776 784 817 Interlace
# Mode "1024x768i"
# DotClock 45
# HTimings 1024 1048 1208 1264
# VTimings 768 776 784 817
# Flags "Interlace"
# EndMode
# This is a set of standard mode timings. Modes that are out of monitor spec
# are automatically deleted by the server (provided the HorizSync and
# VertRefresh lines are correct), so there's no immediate need to
# delete mode timings (unless particular mode timings don't work on your
# monitor). With these modes, the best standard mode that your monitor
# and video card can support for a given resolution is automatically
# used.
# 640x400 @ 70 Hz, 31.5 kHz hsync
Modeline "640x400" 25.175 640 664 760 800 400 409 411 450
# 640x480 @ 60 Hz, 31.5 kHz hsync
Modeline "640x480" 25.175 640 664 760 800 480 491 493 525
# 800x600 @ 56 Hz, 35.15 kHz hsync
ModeLine "800x600" 36 800 824 896 1024 600 601 603 625
# 1024x768 @ 87 Hz interlaced, 35.5 kHz hsync
Modeline "1024x768" 44.9 1024 1048 1208 1264 768 776 784 817
Interlace
# 640x400 @ 85 Hz, 37.86 kHz hsync
Modeline "640x400" 31.5 640 672 736 832 400 401 404 445 -HSync
+VSync
# 640x480 @ 72 Hz, 36.5 kHz hsync
Modeline "640x480" 31.5 640 680 720 864 480 488 491 521
# 640x480 @ 75 Hz, 37.50 kHz hsync
ModeLine "640x480" 31.5 640 656 720 840 480 481 484
500 -HSync -VSync
# 800x600 @ 60 Hz, 37.8 kHz hsync
Modeline "800x600" 40 800 840 968 1056 600 601 605 628 +hsync
+vsync
# 640x480 @ 85 Hz, 43.27 kHz hsync
Modeline "640x480" 36 640 696 752 832 480 481 484
509 -HSync -VSync
# 1152x864 @ 89 Hz interlaced, 44 kHz hsync
ModeLine "1152x864" 65 1152 1168 1384 1480 864 865 875 985
Interlace
# 800x600 @ 72 Hz, 48.0 kHz hsync
Modeline "800x600" 50 800 856 976 1040 600 637 643 666 +hsync
+vsync
# 1024x768 @ 60 Hz, 48.4 kHz hsync
Modeline "1024x768" 65 1024 1032 1176 1344 768 771 777
806 -hsync -vsync
# 640x480 @ 100 Hz, 53.01 kHz hsync
Modeline "640x480" 45.8 640 672 768 864 480 488 494
530 -HSync -VSync
# 1152x864 @ 60 Hz, 53.5 kHz hsync
Modeline "1152x864" 89.9 1152 1216 1472 1680 864 868 876
892 -HSync -VSync
# 800x600 @ 85 Hz, 55.84 kHz hsync
Modeline "800x600" 60.75 800 864 928 1088 600 616 621
657 -HSync -VSync
# 1024x768 @ 70 Hz, 56.5 kHz hsync
Modeline "1024x768" 75 1024 1048 1184 1328 768 771 777
806 -hsync -vsync
# 1280x1024 @ 87 Hz interlaced, 51 kHz hsync
Modeline "1280x1024" 80 1280 1296 1512 1568 1024 1025 1037 1165
Interlace
# 800x600 @ 100 Hz, 64.02 kHz hsync
Modeline "800x600" 69.65 800 864 928 1088 600 604 610
640 -HSync -VSync
# 1024x768 @ 76 Hz, 62.5 kHz hsync
Modeline "1024x768" 85 1024 1032 1152 1360 768 784 787 823
# 1152x864 @ 70 Hz, 62.4 kHz hsync
Modeline "1152x864" 92 1152 1208 1368 1474 864 865 875 895
# 1280x1024 @ 61 Hz, 64.2 kHz hsync
Modeline "1280x1024" 110 1280 1328 1512 1712 1024 1025 1028 1054
# 1024x768 @ 85 Hz, 70.24 kHz hsync
Modeline "1024x768" 98.9 1024 1056 1216 1408 768 782 788
822 -HSync -VSync
# 1152x864 @ 78 Hz, 70.8 kHz hsync
Modeline "1152x864" 110 1152 1240 1324 1552 864 864 876 908
# 1280x1024 @ 70 Hz, 74.59 kHz hsync
Modeline "1280x1024" 126.5 1280 1312 1472 1696 1024 1032 1040
1068 -HSync -VSync
# 1600x1200 @ 60Hz, 75.00 kHz hsync
Modeline "1600x1200" 162 1600 1664 1856 2160 1200 1201 1204 1250 +HSync
+VSync
# 1152x864 @ 84 Hz, 76.0 kHz hsync
Modeline "1152x864" 135 1152 1464 1592 1776 864 864 876 908
# 1280x1024 @ 74 Hz, 78.85 kHz hsync
Modeline "1280x1024" 135 1280 1312 1456 1712 1024 1027 1030 1064
# 1024x768 @ 100Hz, 80.21 kHz hsync
Modeline "1024x768" 115.5 1024 1056 1248 1440 768 771 781
802 -HSync -VSync
# 1280x1024 @ 76 Hz, 81.13 kHz hsync
Modeline "1280x1024" 135 1280 1312 1416 1664 1024 1027 1030 1064
# 1600x1200 @ 70 Hz, 87.50 kHz hsync
Modeline "1600x1200" 189 1600 1664 1856 2160 1200 1201 1204
1250 -HSync -VSync
# 1152x864 @ 100 Hz, 89.62 kHz hsync
Modeline "1152x864" 137.65 1152 1184 1312 1536 864 866 885
902 -HSync -VSync
# 1280x1024 @ 85 Hz, 91.15 kHz hsync
Modeline "1280x1024" 157.5 1280 1344 1504 1728 1024 1025 1028 1072 +HSync
+VSync
# 1600x1200 @ 75 Hz, 93.75 kHz hsync
Modeline "1600x1200" 202.5 1600 1664 1856 2160 1200 1201 1204 1250 +HSync
+VSync
# 1600x1200 @ 85 Hz, 105.77 kHz hsync
Modeline "1600x1200" 220 1600 1616 1808 2080 1200 1204 1207 1244 +HSync
+VSync
# 1280x1024 @ 100 Hz, 107.16 kHz hsync
Modeline "1280x1024" 181.75 1280 1312 1440 1696 1024 1031 1046
1072 -HSync -VSync
# 1800x1440 @ 64Hz, 96.15 kHz hsync
ModeLine "1800X1440" 230 1800 1896 2088 2392 1440 1441 1444 1490 +HSync
+VSync
# 1800x1440 @ 70Hz, 104.52 kHz hsync
ModeLine "1800X1440" 250 1800 1896 2088 2392 1440 1441 1444 1490 +HSync
+VSync
# 512x384 @ 78 Hz, 31.50 kHz hsync
Modeline "512x384" 20.160 512 528 592 640 384 385 388
404 -HSync -VSync
# 512x384 @ 85 Hz, 34.38 kHz hsync
Modeline "512x384" 22 512 528 592 640 384 385 388
404 -HSync -VSync
# Low-res Doublescan modes
# If your chipset does not support doublescan, you get a 'squashed'
# resolution like 320x400.
# 320x200 @ 70 Hz, 31.5 kHz hsync, 8:5 aspect ratio
Modeline "320x200" 12.588 320 336 384 400 200 204 205 225
Doublescan
# 320x240 @ 60 Hz, 31.5 kHz hsync, 4:3 aspect ratio
Modeline "320x240" 12.588 320 336 384 400 240 245 246 262
Doublescan
# 320x240 @ 72 Hz, 36.5 kHz hsync
Modeline "320x240" 15.750 320 336 384 400 240 244 246 262
Doublescan
# 400x300 @ 56 Hz, 35.2 kHz hsync, 4:3 aspect ratio
ModeLine "400x300" 18 400 416 448 512 300 301 302 312
Doublescan
# 400x300 @ 60 Hz, 37.8 kHz hsync
Modeline "400x300" 20 400 416 480 528 300 301 303 314
Doublescan
# 400x300 @ 72 Hz, 48.0 kHz hsync
Modeline "400x300" 25 400 424 488 520 300 319 322 333
Doublescan
# 480x300 @ 56 Hz, 35.2 kHz hsync, 8:5 aspect ratio
ModeLine "480x300" 21.656 480 496 536 616 300 301 302 312
Doublescan
# 480x300 @ 60 Hz, 37.8 kHz hsync
Modeline "480x300" 23.890 480 496 576 632 300 301 303 314
Doublescan
# 480x300 @ 63 Hz, 39.6 kHz hsync
Modeline "480x300" 25 480 496 576 632 300 301 303 314
Doublescan
# 480x300 @ 72 Hz, 48.0 kHz hsync
Modeline "480x300" 29.952 480 504 584 624 300 319 322 333
Doublescan
EndSection
# **********************************************************************
# Graphics device section
# **********************************************************************
# Any number of graphics device sections may be present
Section "Device"
Identifier "Generic VGA"
VendorName "Unknown"
BoardName "Unknown"
Chipset "generic"
# VideoRam 256
# Clocks 25.2 28.3
EndSection
# Device configured by Xconfigurator:
Section "Device"
Identifier "My Video Card"
VendorName "Unknown"
BoardName "Unknown"
#VideoRam 512
#Chipset "wd90c24"
#Option "noaccel" # Use this if acceleration is causing problems
#Clocks 25.175 28.322 65 36 # These are not programmable
#Clocks 29.979 77.408 62.195 59.957 # These are programmable
#Clocks 31.5 35.501 75.166 50.114 # These are not programmable
#Clocks 39.822 72.038 44.744 80.092 # These are programmable
#Clocks 44.297 # Must match Mclk
# Insert Clocks lines here if appropriate
EndSection
# **********************************************************************
# Screen sections
# **********************************************************************
# The Colour SVGA server
Section "Screen"
Driver "svga"
# Use Device "Generic VGA" for Standard VGA 320x200x256
#Device "Generic VGA"
Device "My Video Card"
Monitor "My Monitor"
Subsection "Display"
Depth 8
# Omit the Modes line for the "Generic VGA" device
Modes "640x480"
ViewPort 0 0
EndSubsection
EndSection
# The 16-color VGA server
Section "Screen"
Driver "vga16"
Device "Generic VGA"
Monitor "My Monitor"
Subsection "Display"
Modes "640x480" "800x600"
ViewPort 0 0
EndSubsection
EndSection
# The Mono server
Section "Screen"
Driver "vga2"
Device "Generic VGA"
Monitor "My Monitor"
Subsection "Display"
Modes "640x480" "800x600"
ViewPort 0 0
EndSubsection
EndSection
# The accelerated servers (S3, Mach32, Mach8, 8514, P9000, AGX, W32, Mach64
# I128, and S3V)
Section "Screen"
Driver "accel"
Device "My Video Card"
Monitor "My Monitor"
Subsection "Display"
Depth 8
Modes "640x480"
ViewPort 0 0
EndSubsection
EndSection
*** SNIP ***
Jeff Volckaert <[EMAIL PROTECTED]> wrote in message news:...
> Well, I tried redhat 5.2 & 4.2 with the same bad results. I even tried
Sci
> Tech Display Doctor, but the chip isn't on the list (tried it anyway).
>
> People have mentioned get two of everything (which tpdualscan fixes). I
> just get screwy lines. The display is completely unreadable. In
> Xconfigurator I select WD90C24 and LCD 640x480. I don't do any probing
and
> select 640x480 * bit. Is this correct?
>
> TIA,
> Jeff Volckaert
>
> Dave Weis <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]...
> >
> > On Wed, 26 May 1999, Jeff Volckaert wrote:
> >
> > > I tried the tpdualscan fix and that didn't work. I even tried the
VGA16
> > > server. I'm going to try Redhat 5.2 (and maybe 5.1 and 5.0 if I have
> to).
> > > I'll see if they work any better. Maybe I'll try Debian after that.
> > > What is the deal with this dual scan screen?
> > > Jeff Volckaert
> >
> > I had x running on my 360cs using tpdualscan. Make sure you do a bit of
a
> > delay after running tpdualscan -e (or was it -d??). Also, sometimes you
> > have to run it twice or three times to make it stick.
> >
> > dave
> >
> >
> > --
> > David Weis | 10520 New York Ave, Des Moines, IA 50322
> > [EMAIL PROTECTED] | Voice 515-278-0133 Ext 231
> >
> > When they took the Fourth Amendment, I was quiet because I didn't deal
> drugs.
> > When they took the Sixth Amendment, I was quiet because I was innocent.
> > When they took the Second Amendment, I was quiet because I didn't own a
> gun.
> > Now they've taken the First Amendment and I can't say anything.
> >
>
>
------------------------------
From: Suran <[EMAIL PROTECTED]>
Subject: #BR on SMPs on LX
Date: Thu, 27 May 1999 16:08:55 +0200
Reply-To: [EMAIL PROTECTED]
I've an dual LX-board (2 PII) with supports multiplicators up to 66/366.
Is there a proven posibility to run 2x466 Celeron on it?
(No questions on the Celerons please, this is about the Multiplicators.)
On an uniprocessor it's pretty easy to make the next highest #BR get the
same
voltage-level as the one next to it but I don't know the wiring on the
board
that's behind it. Would it work to shorten the pins (pretty easy on an
adapter)
on one, on both or not? Are there PPGA-Slot1 Adaptors with SMP and
selection of
Multiplicator?
---
[EMAIL PROTECTED]
------------------------------
From: Eugene VonNiederhausern <[EMAIL PROTECTED]>
Subject: sb module question (mpu_irq option)
Date: Thu, 27 May 1999 09:19:48 -0500
I have recently tried to install sound on my linux box (running redhat
6.0). I can the sndconfig it detected my sound card (als100, avance
logic). When it tried to load the module I got an error.
invalid option mpu_irq; device busy
I unloaded the module (modprobe -r sb).
I removed the� mpu_irq option from conf.modules. Using the
pnpdump/isapnp I have setup (what I think is the mpu io/irq) for io=330
and irq=9. The isapnp uses that io/irq with no complaints. But, sb
modules doesn't like that option.
I reloaded the sb module (modprobe sb).
I can play sounds with
cat xx.wav>/dev/dsp
or
cat xx.au>/dev/audio
But, If i try to use any of the sound utilites (play, x11amp, esd, etc).
I get no sound.
I am not that familiar with how the sound utilities work. What am I
missing, or how do I get the sound utilities to work?
�
�
------------------------------
From: [EMAIL PROTECTED]
Subject: How to get multiple replies quickly
Date: Thu, 27 May 1999 14:24:35 GMT
I have posted several messages in the past but I rarely ever get
replies. Since I am a newbie my questions are usually straight forwrd
and to the point. Why don't I get replies? Any advise would be
apreciated.
Thanks,
Mike B.
p.s. I suppose it would not be too ironic if I got no replies on this
message :P
--== Sent via Deja.com http://www.deja.com/ ==--
---Share what you know. Learn what you don't.---
------------------------------
From: "Jeff Volckaert" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.portable,comp.os.linux.setup,comp.os.linux.x
Subject: Re: Redhat 6.0 on an IBM thinkpad 360CSE?
Date: Thu, 27 May 1999 08:44:12 -0400
Well, I tried redhat 5.2 & 4.2 with the same bad results. I even tried Sci
Tech Display Doctor, but the chip isn't on the list (tried it anyway).
People have mentioned get two of everything (which tpdualscan fixes). I
just get screwy lines. The display is completely unreadable. In
Xconfigurator I select WD90C24 and LCD 640x480. I don't do any probing and
select 640x480 * bit. Is this correct?
TIA,
Jeff Volckaert
Dave Weis <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
>
> On Wed, 26 May 1999, Jeff Volckaert wrote:
>
> > I tried the tpdualscan fix and that didn't work. I even tried the VGA16
> > server. I'm going to try Redhat 5.2 (and maybe 5.1 and 5.0 if I have
to).
> > I'll see if they work any better. Maybe I'll try Debian after that.
> > What is the deal with this dual scan screen?
> > Jeff Volckaert
>
> I had x running on my 360cs using tpdualscan. Make sure you do a bit of a
> delay after running tpdualscan -e (or was it -d??). Also, sometimes you
> have to run it twice or three times to make it stick.
>
> dave
>
>
> --
> David Weis | 10520 New York Ave, Des Moines, IA 50322
> [EMAIL PROTECTED] | Voice 515-278-0133 Ext 231
>
> When they took the Fourth Amendment, I was quiet because I didn't deal
drugs.
> When they took the Sixth Amendment, I was quiet because I was innocent.
> When they took the Second Amendment, I was quiet because I didn't own a
gun.
> Now they've taken the First Amendment and I can't say anything.
>
------------------------------
From: Johan Kullstam <[EMAIL PROTECTED]>
Subject: Re: Internal Modem Help
Date: 27 May 1999 10:59:49 -0400
Robert Woodworth <[EMAIL PROTECTED]> writes:
> if(Winmodem == SoftModem != LinuxCompatible == PieceOfMShit)
> then return(toStore);
why are you saying linux-compatible == piece-of-shit?
--
johan kullstam
------------------------------
From: Johan Kullstam <[EMAIL PROTECTED]>
Subject: Re: HP LaserJet 4M Plus
Date: 27 May 1999 10:54:57 -0400
Andr� Dahlqvist <[EMAIL PROTECTED]> writes:
> Does anyone know if the printer mentioned in the subject is
> supported under linux? It wasn't listed in the supported printers
> section of the Printing-HOWTO, but I've been using one on my linux
> box for 2 days now, and yet I haven't ran into any problems. I use
> it as a native postscript printer. Are there some things that don't
> work with this printer that I just haven't ran into yet?
i've had my HP 4MP for about 6 years. it's still working great. i
guess if you are used to having configure ghostscript translation in
printcap and lpr you expect problems and lots of debugging work. the
printer postscript support makes life very easy. don't worry; it
really *is* this easy.
--
johan kullstam
------------------------------
From: bryan <[EMAIL PROTECTED]>
Subject: Re: smp multi cpu motherboards - multithreading
Date: Thu, 27 May 1999 15:00:37 GMT
Menelik <[EMAIL PROTECTED]> wrote:
: No way. Celerons and Pentium Processors are not the same thing.
: FX chipset is 430 FX. Dual FX boards will only take specific Pentium
: chips (watch out for the chipset). You cannot put a Celeron in a Pentium
: mobo.
the board I saw was a dual slot-1 system. other than bios issues,
slot1 is slot1, isn't it?
--
Bryan
------------------------------
From: "Tony Platt" <[EMAIL PROTECTED]>
Crossposted-To: alt.comp.hardware.overclocking,csu.unix.linux
Subject: Re: Dual Celeron's and SMP Performance Problems
Date: Fri, 28 May 1999 01:44:54 +1000
> >The work done by Tomohiro Kawada and others has been interesting.
> >I can think of a number of applications where dual/quad overclocked
> >Celeron's can produce very cost effective clusters for number
>crunching.
> >The crypt cracking teams will get a great windfall from this work.
I would love you to show me a quad Pentium II anything
let alone a Quad Celeron
hahahah
Duel maybe but quad, I think not.
Tony
------------------------------
From: [EMAIL PROTECTED]
Subject: is this Sound Card supported?
Date: Thu, 27 May 1999 14:58:46 GMT
Hi all,
I'd like to know if anyone has esperience with the
I/O Magic MagicSound PCI 32-Bit Sound Card (under linux,
certainly)? Or would somebody be kind to recommend a
working sound card with Abit-BH6?
Please cc: to my email address.
TIA.
Pinwu
--== Sent via Deja.com http://www.deja.com/ ==--
---Share what you know. Learn what you don't.---
------------------------------
From: Totally Lost <[EMAIL PROTECTED]>
Crossposted-To: alt.comp.hardware.overclocking,csu.unix.linux
Subject: Re: Dual Celeron's and SMP Performance Problems
Date: Thu, 27 May 1999 15:41:07 GMT
So what's the point? I started this thread with an initial post that
had a very important disclaimer right up front:
"The work done by Tomohiro Kawada and others has been
interesting. I can think of a number of applications
where dual/quad overclocked Celeron's can produce very
cost effective clusters for number crunching. The crypt
cracking teams will get a great windfall from this work."
There are many small working set applications that will have a big
win on SMP Celerons, possibly including yours. There are also some
medium working set applications with well localized accesses and
sequential memory accesses that will perform well too ... like gcc.
There are also many medium working set applications that would run
much faster on your quad PPro simply because of the 128K to 256K L2
cache size increase, and some significant common cases where dual
Celerons will fall on their face due to excessive memory contention
and L2 cache thrashing.
I started this thread simply to raise the issue that people need to
think about properly fiting their application to the hardware
architecture ... Dual Celerons are not a one size fits all SMP design,
dispite the testimonials of how well they work in some cases. SMP and
NUMA multi-processing has many suprises, one of which is that sometimes
applications run much faster, on the same hardware, when the second
processor is disabled. Any SMP or CC-NUMA performance guy with
significant experience has seen this at least once, and sometimes
more often than the industry would like to talk about.
In article <[EMAIL PROTECTED]>,
Johan Kullstam <[EMAIL PROTECTED]> wrote:
> Totally Lost <[EMAIL PROTECTED]> writes:
>
> > Linux is not well multi-threaded, and has a pretty large foot print
> > with very little locality in either the OS or it's primary
applications.
> > I would expect that for many users, dual Celeron's may have a
negative
> > performance impact much of the time.
> >
> > To observe that Dual Celron's produce an observed improvement under
> > certain lightly loading applications may be true. To assert that
> > they scale under modest to heavy work loads is probably a huge
mistake.
> > To expect that they will scale well under Linux with heavy loads is
> > almost certainly folly.
>
> this depends on the type of loads. i do number crunching and have a
> quad ppro-200 (512k cache) machine. the jobs are trivially
> parallelizable (i need to run many to build up stats, i can run
> multiple copies of the same job with differing random number seeds)
> and involve little or no disk activity. the quad box really does give
> four times the performance of my older single ppro-200 (256k cache).
> with four jobs active i have 399% user cpu loading. since i am never
> in the kernel for much, i didn't seem much improvement going from
> 2.0.x to 2.2.x (once the shopping deadlock problem in 2.0.34 and lower
> got fixed - 2.0.34 and below could only handle two cpus).
>
> --
> johan kullstam
>
--== Sent via Deja.com http://www.deja.com/ ==--
---Share what you know. Learn what you don't.---
------------------------------
Reply-To: "Curt" <[EMAIL PROTECTED]>
From: "Curt" <[EMAIL PROTECTED]>
Subject: Re: Attempted RedHat install kills HDD
Date: Thu, 27 May 1999 09:10:13 -0500
It seems that most of the systems I've installed RH5.0,5.1.5.2 on have
failed the
last step of writing to the boot sector. I have had to boot from a floppy,
mount the
drive and run lilo by hand. This always has fixed the problem.
Hope this helps.
Robert C McDougle <[EMAIL PROTECTED]> wrote in message
news:7ii2pq$l3j$[EMAIL PROTECTED]...
> I just tried to install RedHat 5.2 to my Tyan 1563D with 1 p133 processor
> and a WD 2.5g HDD. The drive was recognized fine by the BIOS prior to the
> install and could be hit by FDISK on a win98 boot disk. After attempting
> the Linux install (which seemed to go fine), the boot fails with the
message
>
> "not found any [active partition] in HDD
> DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER"
>
> pressing enter just gets me to a repeat of the message.
> Now that this message has occurred, I can't even boot from a floppy. I
> changed the boot sequence in the BIOS to A, C, SCSI but even with a
> previously working boot disk only get to the same message.
>
> Does anyone know what is going on???
>
> --
> R C McDougle
> rcm Arch Design
>
>
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list (and comp.os.linux.hardware) via:
Internet: [EMAIL PROTECTED]
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Hardware Digest
******************************
