Linux-Hardware Digest #238, Volume #13 Sat, 15 Jul 00 17:13:06 EDT
Contents:
Re: QUES: FIC PAG2130/VIA VT8501 /VIA Apollo MVP4/Trident (Chem-R-Us)
USB MS Intellimouse - keyboard doesn't respond ("binary boy")
CD-ROM Problem in Mandrake 7.1 ("PETTER ARNE EKROLL")
problem installing ethernet adaptor ([EMAIL PROTECTED])
Looking for scanner (Eric Ho)
monitor resolutions with linux (Neil Hollow)
Re: Asus P2B-D, dual PIII-650MHz, SMP not working right (James Knowles)
vivitron 17 monitor resolutions with linux (Neil Hollow)
Re: USB MS Intellimouse - keyboard doesn't respond ([EMAIL PROTECTED])
----------------------------------------------------------------------------
Date: Sat, 15 Jul 2000 13:41:57 -0700
From: Chem-R-Us <[EMAIL PROTECTED]>
Subject: Re: QUES: FIC PAG2130/VIA VT8501 /VIA Apollo MVP4/Trident
Hi Tom,
See your email.
Tom J wrote:
>
> Hello. Have you ever run this hardware successfully?
Yes. I have X up and running well. XFree86 3.3.6. I haven't fooled with
sound yet. I have never used Linux & sound, but am going to attempt it.
> I have a FIC PAG2130 motherboard with a VIA Vt8501 Northbridge, which has
> a VIA APollo MVP4 with on-board Trident Blade3D graphics and 82Cxxxx codec.
> I have installed linux 2.3.99-pre9, back-installed the 1.1.8 82cxxxx sound
> driver, and installed XFree86 3.3.6. Sound and video fail.
I am using kernel 2.2.16. XF_SVGA server. I ended up using Trident
CyberBlade (generic) setting for the device.
> Actually, under linux 2.2.12 and XFree86 3.3.5, I got a generic server
> running but I couldn't get 15-bit color (5 bits red, 5 bits green 5 bits blue),
> which I need. Sound didn't work at all in worse ways than now.
>
> Sound:When I use bplay to play a .wav file, bplay makes normal reports that it
> is sending out buffers, but there is no sound (there had been sound with a
> funny driver from FIC, but it cut off sound files and couldn't play all of them
> but instead make a single click).
>
> Video:
> I ran XF86Setup graphically, but when it's done or when I later run startx,
> the image of the screen is timed wrong and there are unreadable images of
> a screen, although I can see movement of the pointer if I move the mouse.
> So it's a little like being interlaced when I didn't want to, or putting
> four rows of data on one line kind of thing.
> If I specify the Chipset as blade3d, and run startx, it hangs the entire
> system. I have tried setting options such as no_program_clocks,
> no_pixmap_cache, "slow_dram" "pci_burst_off", but no difference results.
>
> Have you ever seen this stuff work?
Blade3D chipset didn't work for me. Cyberblade (generic) did. Here's my
/etc/X11/XF86Config file:
# File generated by XFdrake.
# **********************************************************************
# Refer to the XF86Config(4/5) man page for details about the format of
# this file.
# **********************************************************************
Section "Files"
RgbPath "/usr/X11R6/lib/X11/rgb"
# Multiple FontPath entries are allowed (they are concatenated together)
# By default, Mandrake 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
# This allows the server to start up even if the
# mouse device can't be opened/initialised.
AllowMouseOpenFail
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 250 30
# 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(pc105)"
XkbGeometry "pc"
XkbRules "xfree86"
XkbModel "pc105"
XkbLayout "us"
EndSection
# **********************************************************************
# Pointer section
# **********************************************************************
Section "Pointer"
Protocol "Microsoft"
Device "/dev/mouse"
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 ""
VendorName ""
ModelName ""
# 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 30-95
# 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-120
# 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
# 640x480, 60.0Hz; hfreq=31.469000, vfreq=59.939999
ModeLine "640x480" 25.17 640 648 744 784 480 482 484 509 -hsync
-vsync
# 640x480, 75.0Hz; hfreq=37.500000, vfreq=75.000000
ModeLine "640x480" 31.50 640 656 720 840 480 481 484 500 -hsync
-vsync
# 640x480, 85.0Hz; hfreq=43.269001, vfreq=85.008003
ModeLine "640x480" 36.00 640 696 752 832 480 481 484 509 -hsync
-vsync
# 800x600, 60.0Hz; hfreq=37.879002, vfreq=60.317001
ModeLine "800x600" 40.00 800 840 968 1056 600 601 605 628 +hsync
+vsync
# 800x600, 72.0Hz; hfreq=48.077000, vfreq=72.188004
ModeLine "800x600" 50.00 800 856 976 1040 600 637 643 666 +hsync
+vsync
# 800x600, 75.0Hz; hfreq=46.875000, vfreq=75.000000
ModeLine "800x600" 49.50 800 816 896 1056 600 601 604 625 +hsync
+vsync
# 800x600, 85.0Hz; hfreq=53.674000, vfreq=85.060997
ModeLine "800x600" 56.25 800 832 896 1048 600 601 604 631 +hsync
+vsync
# 1024x768, 70.0Hz; hfreq=56.476002, vfreq=70.069000
ModeLine "1024x768" 75.00 1024 1048 1184 1328 768 771 777 806
-hsync -vsync
# 1024x768, 75.0Hz; hfreq=60.022999, vfreq=75.028999
ModeLine "1024x768" 78.75 1024 1040 1136 1312 768 769 772 800
+hsync +vsync
# 1024x768, 85.0Hz; hfreq=68.677002, vfreq=84.997002
ModeLine "1024x768" 94.50 1024 1072 1168 1376 768 769 772 808
+hsync +vsync
# 1152x864, 75.0Hz; hfreq=67.500000, vfreq=75.000000
ModeLine "1152x864" 108.00 1152 1216 1344 1600 864 865 868 900
+hsync +vsync
# 1280x1024, 85.0Hz; hfreq=91.146004, vfreq=85.024002
ModeLine "1280x1024" 157.50 1280 1344 1504 1728 1024 1025 1028 1072
+hsync +vsync
# 1600x1200, 75.0Hz; hfreq=93.750000, vfreq=75.000000
ModeLine "1600x1200" 202.50 1600 1664 1856 2160 1200 1201 1204 1250
+hsync +vsync
# 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
# **********************************************************************
Section "Device"
Identifier "Generic VGA"
Chipset "generic"
EndSection
Section "Device"
Identifier "Trident CyberBlade (generic)"
VendorName "Unknown"
BoardName "Unknown"
VideoRam 8192
# Clock lines
# Uncomment following option if you see a big white block
# instead of the cursor!
#Option "sw_cursor"
Option "power_saver"
EndSection
# **********************************************************************
# Screen sections
# **********************************************************************
# The Colour SVGA server
Section "Screen"
Driver "svga"
Device "Trident CyberBlade (generic)"
Monitor ""
DefaultColorDepth 8
Subsection "Display"
Depth 8
Modes "1280x1024" "1152x864" "1024x768" "800x600"
"640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 15
Modes "1280x1024" "1152x864" "1024x768" "800x600"
"640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1280x1024" "1152x864" "1024x768" "800x600"
"640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1280x1024" "1152x864" "1024x768" "800x600"
"640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 32
Modes "1280x1024" "1152x864" "1024x768" "800x600"
"640x480"
ViewPort 0 0
EndSubsection
EndSection
Section "Screen"
Driver "vga16"
Device "Generic VGA"
Monitor ""
Subsection "Display"
Modes "640x480" "800x600"
ViewPort 0 0
EndSubsection
EndSection
Section "Screen"
Driver "vga2"
Device "Generic VGA"
Monitor ""
Subsection "Display"
Modes "640x480" "800x600"
ViewPort 0 0
EndSubsection
EndSection
Section "Screen"
Driver "accel"
Device "Trident CyberBlade (generic)"
Monitor ""
DefaultColorDepth 16
#8
Subsection "Display"
Depth 8
Modes "1280x1024" "1152x864" "1024x768" "800x600"
"640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 15
Modes "1280x1024" "1152x864" "1024x768" "800x600"
"640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1280x1024" "1152x864" "1024x768" "800x600"
"640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1280x1024" "1152x864" "1024x768" "800x600"
"640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 32
Modes "1280x1024" "1152x864" "1024x768" "800x600"
"640x480"
ViewPort 0 0
EndSubsection
EndSection
Section "Screen"
Driver "fbdev"
Device "Trident CyberBlade (generic)"
Monitor ""
DefaultColorDepth 8
Subsection "Display"
Depth 8
Modes "default"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 15
Modes "default"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "default"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "default"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 32
Modes "default"
ViewPort 0 0
EndSubsection
EndSection
--
Chem-R-Us
------------------------------
From: "binary boy" <[EMAIL PROTECTED]>
Subject: USB MS Intellimouse - keyboard doesn't respond
Date: Sat, 15 Jul 2000 15:36:44 -0500
Just got my first USB device, a MS Intellimouse Explorer. Running
2.4.0-test2, I compiled support for USB, OHCI (I have an ALI Aladdin
chipset), HID, and mouse support in the USB section of the kernel.
Upon rebooting, bootup messages reported recognizing the USB device and knew
it was an MS Intellimouse. However, upon reaching the console login screen,
the keyboard did not respond as if it weren't recognized. I unplugged the
USB mouse, put back in the PS/2 mouse, rebooted, and everything was fine. Do
I have to change something relative to the keyboard in the kernel config? I
checked the HOWTOS, and found nothing on point.
Thanks.
--
____________________________________________
"I think not" said Descartes, and promptly disappeared.
------------------------------
From: "PETTER ARNE EKROLL" <[EMAIL PROTECTED]>
Subject: CD-ROM Problem in Mandrake 7.1
Date: Sat, 15 Jul 2000 20:41:32 GMT
I can't get my CD-Rom to work in Mandrake 7.1.
It is a Hitachi GD-2500 DVD-Rom.
When I go to /mnt/cdrom it says I/O Error.
I've configured the kernel and compiled it,
but it doesn't seem to work. I've tried to mount it, but get an error. Allso
I get an error that sounds like "error in block-major-33". Anyone know what
to do???
- TranceJay
- [EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED]
Subject: problem installing ethernet adaptor
Date: Sat, 15 Jul 2000 20:40:04 GMT
I recently installed a Linksys 10/100 LAN PCI card in my Redhat 6.1
system in anticipation of getting DSL. During the first reboot Redhat
detected the new hardware and, presumably, did some sort of
configuration. It then asked if I wanted to configure networking. I said
"no" since my DSL wasn't in yet. The system seemed to work just fine.
Yesterday my DSL was hooked up and I tried configuring networking only
to find that, apparently, the card was not properly installed. I added
the lines
alias eth0 tulip
options tulip options=0 debug=3
to /etc/conf.modules as per the instructions that came with the card.
However, there is a problem loading the tulip module both at boot-up and
interactively. Here's what happens when I play with module commands:
[root@localhost /etc]# modprobe eth0
/lib/modules/2.2.12-20/net/tulip.o: init_module: Device or resource
busy
[root@localhost /etc]# insmod tulip
/lib/modules/2.2.12-20/net/tulip.o: init_module: Device or resource
busy
[root@localhost /etc]# rmmod tulip
rmmod: module tulip not loaded
My only guess at this point is that their is a resource conflict. PNP
has the card sharing IRQ7 with the display adaptor (also PCI) and with
LPT1 (not being used).
Any suggestions about how to fix this or proceed with troubleshooting
will be much appreciated.
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: Eric Ho <[EMAIL PROTECTED]>
Subject: Looking for scanner
Date: 15 Jul 2000 20:58:34 GMT
Hi,
I am looking for a good scanner to use with my Slackware 7.0 Linux,
any suggestion ?
Best Regards,
Eric Ho
------------------------------
From: Neil Hollow <[EMAIL PROTECTED]>
Subject: monitor resolutions with linux
Date: Sat, 15 Jul 2000 22:00:48 +0100
I've just bought a second hand gateway monitor CPD-17F23 and of course
don't have a any technical details supplied. Does anyone have any
experience of getting X to work with this machine. Running RH6.0 on a
philips monitor using an ATI RAGE II card (I'm keeping the card). What
vertical and horizontal refresh rate should I use? NH.
------------------------------
From: James Knowles <[EMAIL PROTECTED]>
Crossposted-To: alt.comp.periphs.mainboard.asus,alt.comp.hardware
Subject: Re: Asus P2B-D, dual PIII-650MHz, SMP not working right
Date: Sat, 15 Jul 2000 15:00:58 -0600
(I've reorded the quotations from the original posting.)
> **** The P2B-D ... can be supported by Coppermine CPU in the later shipment
> of the same PCB version. Please contact our reseller for detail information.
This is the first thing I'd check. I've a bit older P2B-D with dual
P-II/400's. Beautiful setup with zero hiccoughs. My first P2B-D needed
the BIOS flashed, however.
> The power supply is only 250W, but I think I have 80 watts to spare
[...]
> went right by it this time!
I did run my first SMP machine (PII/233s) out of power (250W PS) with
three SCSI HDs running SW RAID-5 out of the kernel. I got wierd flakey
errors not unlike what you see. I've always been paranoid since and have
insisted on *at least* a 350W PS ever since for an SMP system. I have a
400W PS powering four SCSI HD, one IDE HD (&CDROM), and a DAT. It may
(or may not) be excessive, but after going through that headache once
overkill become appealing. :)
> OK, so I need at least rev 1.06 of the motherboard, and rev 1011 of the BIOS.
> My vendor sealed the case (!) so I'm going to let him check the motherboard
> version. Presumably it's new and should be up to snuff, but...
[...]
> I think I'm going to take it back to the vendor and let him fix it...
Is the vendor experienced in SMP systems? I've come to explicitly trust
the guys I buy stuff from over time. They understand that they're not in
the computer hardware business, but the people business.
> make -j2 bzImage
As an aside, IIRC, to burn both CPUs with gmake you'll need to specify
"-j3" not "-j2"; the parameter needs to be number of CPUs+1. Two threads
for compiling, one master thread.
HTH,
James
--
C makes it easy for you to shoot yourself in the foot. C++ makes that
harder, but when you do, it blows away your whole leg.
- Bjarne Stroustrup
------------------------------
From: Neil Hollow <[EMAIL PROTECTED]>
Subject: vivitron 17 monitor resolutions with linux
Date: Sat, 15 Jul 2000 22:01:29 +0100
I've just bought a second hand gateway monitor vivitron 17 (CPD-17F23)
and of course don't have a any technical details supplied. Does anyone
have any experience of getting X to work with this machine? Running
RH6.0 on a philips monitor using an ATI RAGE II card (I'm keeping the
card). What vertical and horizontal refresh rates should I use? NH.
------------------------------
Subject: Re: USB MS Intellimouse - keyboard doesn't respond
From: [EMAIL PROTECTED]
Date: Sat, 15 Jul 2000 21:03:49 GMT
"binary boy" <[EMAIL PROTECTED]> writes:
> Upon rebooting, bootup messages reported recognizing the USB device and knew
> it was an MS Intellimouse. However, upon reaching the console login screen,
> the keyboard did not respond as if it weren't recognized. I unplugged the
> USB mouse, put back in the PS/2 mouse, rebooted, and everything was fine. Do
> I have to change something relative to the keyboard in the kernel config? I
> checked the HOWTOS, and found nothing on point.
On my motherboard, there are settings for "legacy USB keyboard" and
"legacy USB mouse" support, which are, by default, disabled. It's
possible that you will have to either enable or disable these options,
or ones like them. There is a lot of nastiness going on with USB,
particularly on the Mac side of the aisle, that results in horrific
incompatability with a lot of devices.
--
Eric P. McCoy ([EMAIL PROTECTED])
"Dude... my hands are huge. They can touch anything but themselves...
oh, wait."
------------------------------
** 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
******************************
