Linux-Hardware Digest #462, Volume #10 Fri, 11 Jun 99 00:13:53 EDT
Contents:
Re: SCSI scanners - progress (Randy Olinger)
Re: Celeron or PII? (bryan)
Re: Linux doesn't see ide1 (Randy Olinger)
Re: Yamaha OPL-3SA Sound Card and RH 6.0 ([EMAIL PROTECTED])
Astra 1200S and Adaptec 2906 ? (Gilles Auger)
Re: Viewsonic G790 Equivalent for XFree86 Setup ... (Frank Singleton)
Re: Celeron or PII? (bryan)
No PS/2 mouse for linux on UMAX ActionBook 335T Notebook (Donald M Burns)
Drivers for DIGI SYNC/570i ("Luis")
----------------------------------------------------------------------------
From: Randy Olinger <[EMAIL PROTECTED]>
Subject: Re: SCSI scanners - progress
Date: Thu, 10 Jun 1999 09:37:54 -0500
Reply-To: [EMAIL PROTECTED]
Hang in there, you'll get it...
xscanimage needs to find the scanner. There are a couple ways. In the
tools directory in SANE, there is a program called find_scanner. Try
running this. I think you can also type
scanimage -L
which will list the valid scanners.
Remember, you have to have the SCSI generic driver compiled in to your
kernel or added as a module in order to scan. If you look at the
/proc/scsi/scsi
output your scanner should have a /dev/sgx associated with it. (x will be
between
a-h depending on how many scsi devices you have and what order the kernel
finds them at boot time) Make sure the scanner is powered on at boot time.
If you can find the generic scsi device, (/dev/sgxx) then make a symbolic
link
to /dev/scanner and it makes life a lot easier.
If this makes no sense, e-mail me and I'll try to help.
Randy
[EMAIL PROTECTED]
Daniel Naughton wrote:
> I finally got the new advansys card to be recognized. I need to create
> a new boot image (page 200 of the RH5.2 manual on making a new initrd
> image), add the new boot image into the /etc/lilo.conf file, then
> running lilo - v to write the whole mess to the MBR. (This is detailed
> on the redhat support pages on updating the kernel)
>
> I still have a problem that xscanimage returns with "ne devices
> detected", but I think that is something I can work through with the
> SANE docs (hopefully)
>
> I'm still optimistic after 7 straight days of trying to get a scanner
> working. There have been times when I thought just format the drive
> with NT and get on with your life. Those thoughts are still kept at bay
>
> Dan
------------------------------
From: bryan <[EMAIL PROTECTED]>
Subject: Re: Celeron or PII?
Date: Thu, 10 Jun 1999 14:47:51 GMT
Johannes Nix <[EMAIL PROTECTED]> wrote:
: Johan Kullstam <[EMAIL PROTECTED]> writes:
: >
: > if you *really* *need* raw cpu performance, then alpha might be a good
: > choice - especially for floating point. they are a bit more expensive
: > than the intel offering however.
: >
: This is very interesting for me.
: I would like to have some numbers, especially concerning floating
: point arithmetics.
: Are there SMP Alphas?
I can't answer that, but I can say that my dual celeron linux box can
build a 2.2 kernel (with reasonable options) in 1:45. I believe that
would be on-par with alphas - if not beating them.
and for a fraction of the cost, too.
--
Bryan [at] Grateful.Net
http://www.Grateful.Net
------------------------------
From: Randy Olinger <[EMAIL PROTECTED]>
Subject: Re: Linux doesn't see ide1
Date: Thu, 10 Jun 1999 09:41:05 -0500
Reply-To: [EMAIL PROTECTED]
Make sure the drive is detected before the system boots. You should
see it listed during the power-on-self-test (POST)
Randy
[EMAIL PROTECTED] wrote:
> I'm having trouble getting Linux to see a 120 MB "superdisk" ATAPI
> floppy drive that I've installed on ide1. I've got ide-floppy
> compiled into the kernel (ver. 2.2.9). As the dmesg quote below
> indicates, the kernel acknowledges that ide1 exists in the machine,
> but doesn't see the device on it (which I guess would be assigned
> hdc). And ide1 does not appear in the /proc/interrupts table, but it
> does appear in /proc/ioports.
>
> I checked the drive's documentation, and the best suggestion I could
> find was to make sure that LBA was enabled in the BIOS, which it is.
>
> At the suggestion of linux/Documentation/ide.txt, I tried booting
> through lilo with ide1=0x170,0x376,15, but that didn't help.
>
> I'm stumped. Anyone got a clue they'd care to offer?
>
> Relevant lines from dmesg:
> >PIIX3: IDE controller on PCI bus 00 dev 39
> >PIIX3: not 100% native mode: will probe irqs later
> > ide0: BM-DMA at 0xfbf0-0xfbf7, BIOS settings: hda:DMA, hdb:pio
> > ide1: BM-DMA at 0xfbf8-0xfbff, BIOS settings: hdc:pio, hdd:pio
> >hda: Maxtor 88400D8, ATA DISK drive
> >hdb: CREATIVEDVD-ROM DVD2240E 12/24/97, ATAPI CDROM drive
> >ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> >hda: Maxtor 88400D8, 8011MB w/256kB Cache, CHS=1021/255/63, (U)DMA
> >hdb: ATAPI 24X DVD-ROM drive, 256kB Cache
> >Uniform CDROM driver Revision: 2.55
> >Floppy drive(s): fd0 is 1.44M
> >FDC 0 is a post-1991 82077
> >md driver 0.36.6 MAX_MD_DEV=4, MAX_REAL=8
>
> /proc/interrupts:
> > CPU0 CPU1
> > 0: 90778 62956 IO-APIC-edge timer
> > 1: 556 510 IO-APIC-edge keyboard
> > 2: 0 0 XT-PIC cascade
> > 5: 0 3 IO-APIC-edge soundblaster
> > 10: 1095 1223 IO-APIC-edge NE2000
> > 12: 2996 2396 IO-APIC-edge PS/2 Mouse
> > 13: 1 0 XT-PIC fpu
> > 14: 30195 26219 IO-APIC-edge ide0
> > 19: 1123 1064 IO-APIC-level eth0
>
> /proc/ioports:
> >fbf0-fbf7 : ide0
> >fbf8-fbff : ide1
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Yamaha OPL-3SA Sound Card and RH 6.0
Date: 11 Jun 1999 02:55:59 GMT
Jonathan Bruce <[EMAIL PROTECTED]> wrote:
: Hi folks,
: As any one managed to get this sound card to install and work under
: RedHat 6.0 ? When I ran the PnP utility it picked out my card no
: problem, but the install failed :-(
Me Too(TM)
Compiling support into the kernel, it sees it but mpg123 says that /dev/dsp
doesn't exist (when indeed its there). As a module, it has unresolved
symbol problems - this is a vanilla, virgin RH6.0/x86 install.
Any clues would be appreciated.
Cheers
/dave
--
/ David Manchester <[EMAIL PROTECTED]> [TDH] Netware/UNIX droid. \
Tell someone who's interested, tell someone who can keep their lunch digested
Tell someone who wants your conversation, tell someone who doesn't regard you
\as an argument for compulsory sterilisation." [TISM], `How Do I Love Thee?'/
------------------------------
From: [EMAIL PROTECTED] (Gilles Auger)
Subject: Astra 1200S and Adaptec 2906 ?
Date: Fri, 11 Jun 1999 03:19:42 GMT
Hi
In a few months, like you i will enter the Linux world..
For nearly all of my hardware I have found driver for Linux
with one exeption, my Astras 1200S with his Adaptec 2906 SCSI PCI
card.
Is this possible to run these two devices together under Linux ??
Thanks for your collaboration.
Gilles Auger
[EMAIL PROTECTED]
------------------------------
From: Frank Singleton <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc,comp.os.linux.x
Subject: Re: Viewsonic G790 Equivalent for XFree86 Setup ...
Date: Thu, 10 Jun 1999 21:47:37 -0500
> On 8 Jun 1999 01:10:58 GMT, Flash <[EMAIL PROTECTED]> wrote:
> >Hey,
> >
> >Just got a nice 19" Viewsonic G790 Monitor. I need to upgrade the video card
Hi,
I run G790 with expert@work 8MB with the following config file
and it is just great !!
Mostly I run at 16bpp 1600x1200 at FH=93.6khz and FV=74.9hz
according to the VIEWMETER on your monitor.
/ Frank
<snip>
# **********************************************************************
# Monitor section
# **********************************************************************
# Any number of monitor sections may be present
Section "Monitor"
Identifier "ViewSonic G790"
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 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-180
# 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 8192
# Insert Clocks lines here if appropriate
EndSection
# **********************************************************************
# Screen sections
# **********************************************************************
# The Colour SVGA server
Section "Screen"
Driver "svga"
Device "Generic VGA"
#Device "My Video Card"
Monitor "ViewSonic G790"
Subsection "Display"
Depth 8
#Modes (null)
ViewPort 0 0
EndSubsection
EndSection
# The 16-color VGA server
Section "Screen"
Driver "vga16"
Device "Generic VGA"
Monitor "ViewSonic G790"
Subsection "Display"
Modes "640x480" "800x600"
ViewPort 0 0
EndSubsection
EndSection
# The Mono server
Section "Screen"
Driver "vga2"
Device "Generic VGA"
Monitor "ViewSonic G790"
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 "ViewSonic G790"
Subsection "Display"
Depth 32
Modes "1280x1024"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1600x1200" "1280x1024" "1024x768" "800x600"
"640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 8
Modes "1600x1200" "1280x1024" "1024x768" "800x600"
"640x480"
ViewPort 0 0
EndSubsection
EndSection
<snip>
------------------------------
From: bryan <[EMAIL PROTECTED]>
Subject: Re: Celeron or PII?
Date: Thu, 10 Jun 1999 14:46:40 GMT
Dave Edick <[EMAIL PROTECTED]> wrote:
: I agree that you can't beat the deal you get from overclocking a Cel 300a
: to 450MHz. But overclocking doesn't always work and not everyone WANTS
: to overclock. Any overclocked system is less stable than a non-overclocked
: one.
I used to believe this myself. I really did. I used to believe that
you should always 'blindly follow the specs'. but in the case of the
celeron, you -are- following the specs - sort of. the cpu is the same
basic part they use in the p2-450 - it just has a different cache part
inside. and that cache part can usually work very well at 450.
raising the voltage from 2.0 to 2.2 is 10%. that's the margin that's
allowed by the specs, too, I believe. and almost no celeron won't o/c
at 2.2 v.
: And many people will buy pre-built systems that won't necessarily
: be overclock compatible.
true - but if you buy the right MoBo and fan setup, the chances are
probably better than 90% that it will o/c.
again, I used to turn my nose up at overclockers. 'silly gamers', I
used to say. not anymore. on -some- chips (the 300a was a one-time
'gift' from intel) you are actually staying within the region of
stability even when you o/c. its just that intel won't admit they
designed such a great cost/performance item. they'd lose sales of
their extremely expensive (overpriced) p2 and p3 chips.
: On Wed, 09 Jun 1999 16:00:14 GMT, bryan <[EMAIL PROTECTED]> wrote:
: >Dave Edick <[EMAIL PROTECTED]> wrote:
: >: Closer, but not quite.
: >
: >: The Celeron L2 cache does run at CPU speed, but the P2 L2 cache runs at 1/2
: >: CPU speed, not bus speed. That difference pretty well neutralizes any
: >: advantage of the P2's larger cache.
: >
: >: A significant item not mentioned so far is bus speed. Non-overclocked
: >: Celerons all run the bus at 66MHz. Most P2s and all P3s run the bus at
: >: 100Mhz. But most overclocked Celerons run at 100Mhz bus speed as well.
: >
: >: Between the two, I'd go with the Celeron. Especially if I were interested
: >: in overclocking. P2s have pretty poor price/performance and P3s are a
: >: total joke IMHO.
: >
: >: My biases? I went with AMD, since I'm no big fan of Intel. A K6-3 (256k
: >: CPU speed L2 cache, 100MHz bus, and L3 cache on the motherboard) is a better
: >: choice than either Intel in my book.
: >
: >I agree that AMD is the underdog and its good to help them out, but
: >the k6-3 is way overpriced. a cel 300a o/c to 450 is still the best
: >price/perf on the market.
: >
: >--
: >Bryan [at] Grateful.Net
: >http://www.Grateful.Net
--
Bryan [at] Grateful.Net
http://www.Grateful.Net
------------------------------
From: Donald M Burns <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.portable,uk.comp.os.linux
Subject: No PS/2 mouse for linux on UMAX ActionBook 335T Notebook
Date: Thu, 10 Jun 1999 22:32:46 +0100
Hi all,
I just bought a UMAX Action Book 335T and although the
touch-pad works just fine under Win98 I can't get it to
work under Linux.
Symptoms:-
PS/2 Mouse is compiled as a module. When the psaux.o
module loads a message about it initialising is left in
/var/log/messages.
If we then do a "cat /dev/psaux" we get no output
when I dabble with the touch-pad. Also procinfo shows
no activity for interupt 12 the "PS/2 Mouse".
One other point, after the thing fails to work in Linux
it won't work in windows if you warm-booted to get there.
To make it work again in windows one has to cycle the
power.
Any suggestion or helped are much appreciated.
Donald.
------------------------------
From: "Luis" <Luis@a>
Subject: Drivers for DIGI SYNC/570i
Date: Thu, 10 Jun 1999 07:19:13 +0100
Hello
I`m looking for drivers of a DIGI SYNC/570i. �Anyone knows anything
about this?.
Thanks
Luis Quart
------------------------------
** 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
******************************
