Linux-Hardware Digest #673, Volume #13 Wed, 4 Oct 00 20:13:07 EDT
Contents:
Re: Stylus Color 760 (Andrey Vlasov)
XF86Config Intellimouse 1.1A PS/2 Compatible Solution ([EMAIL PROTECTED])
Drivers for Guide Technology Boards ("Judah Levine")
Adaptec 29160N problem (Ant Sims)
Re: Best OS (Rod Smith)
Re: kodak DC215 zoom (Rod Smith)
Re: CDROM burning ("Paul")
Re: 2.4.0-test8 and PDC 20265 (Bryan Siemon)
Passing huge command lines to kernel??? ([EMAIL PROTECTED])
Re: CD Writer errors: Hot connecting and removing devices on SCSI bus ("Richard M.
Denney")
tar but no dump - help? ("ekkis")
Re: SB Live! doesn't work under Red Hat 7.0 (New Information) ("Paul Kuliniewicz")
BIOS Limitations on HP Vectra ("seldan")
Re: how can I use my IDE CD-RW for linux ? ("R.K.Aa.")
Re: how can I use my IDE CD-RW for linux ? ("R.K.Aa.")
Re: scanners ("R.K.Aa.")
----------------------------------------------------------------------------
From: Andrey Vlasov <[EMAIL PROTECTED]>
Subject: Re: Stylus Color 760
Date: Wed, 04 Oct 2000 13:07:42 -0700
Hi there,
did you check next webpage?
ftp://ftp.cs.rpi.edu/.2/FreeBSD/branches/-current/src/contrib/groff/pfbtops/
for graphic printing use gimp-print pluging and you will get a very nice photos on
photo paper. (Check for it at http://freshmeat.net or sorceforge web site)
Andrey
Tajvidi wrote:
> Hi Linux lover!
>
> I've purchased an Epson Stylus Color 760 printer and I use the stcolor device
> driver provided by ghostscript. My problem is that I can just print in the
> resolution 360x360 dpi. My printer supports higher resolution (up to
> 1440x720dpi). I've already tried several resolutions (720x720, ...) with the -r
> option but no results :( If anybody has a solution....
>
> Thanks in advance
> Charles
------------------------------
From: [EMAIL PROTECTED]
Subject: XF86Config Intellimouse 1.1A PS/2 Compatible Solution
Date: Wed, 04 Oct 2000 20:20:49 GMT
Hi people
I've Just started into the wonderful world of Linux and of course
straight into more than I can handle.
for the last week I have been battleing with the problem of getting my
mouse to work.
Thought I had fixed it then I got the latest stable version of Debian
and had to start again.
O.k. I'm running Kernel 2.2.17
I have configured Gpm to
/dev/psaux
imps/2
with no repeat.
xf86config program does not display all the options for mice and such
like.
I had a brain wave about half an hour ago something along the lines of
RTFM.
Do a man XF86Config and wade throught the pages until you get the list
of mice's pick the one and edit
/etc/X11/XF86Config
to the correct one.
For my Mouse I used imPS/2
And it works like a charm!!!!!!
O.K. next problem......
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: "Judah Levine" <[EMAIL PROTECTED]>
Subject: Drivers for Guide Technology Boards
Date: Wed, 4 Oct 2000 15:34:36 -0600
I am looking for Linux drivers for Guide Technlogy Boards. I am especially
interested in drivers for:
GT200 Time Interval Counter
GT401 Event Timing Controller
Judah Levine
Time and Frequency Division
National Institute of Standards and Technlogy
Boulder, Colorado
e-mail: [EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (Ant Sims)
Subject: Adaptec 29160N problem
Date: 4 Oct 2000 21:05:04 GMT
I've got major problems getting an Adaptec 29160N to work under
Linux. When I insert the aic7xxx module (5.1.31), I get errors of the
form:
scsi : aborting command due to timeout : pid x, scsi0, channel 0,
id x, lun 0 Test Unit Ready 00 00 00 00 00
For the first few IDs, followed by unending:
SCSI host 0 abort (pid x) timed out - resetting
SCSI bus is being reset for host 0 channel 0.
SCSI host 0 channel 0 reset (pid x) timed out - trying harder
SCSI bus is being reset for host 0 channel 0.
I've tried changing just about every module parameter listed in
linux/drivers/scsi/README.aic7xxx, paying special attention to
override_term and stpwlev.
I've tried the card with a single narrow 10MHZ SCSI 2 device (Toshiba
DVD RAM drive) attached to the non-LVD segment and, more
significantly, with no cables attached to the card - both produce
identical results.
Strangely, the card appears to work fine under Windows
95. Benchmarking the DVD RAM drive with CDROM and DVD RAM media
produces the expected data rates, so I don't think there's a problem
with the SCSI cabling.
I don't know if it's significant, but after installing the SCSI card,
Windows (95 OSR 2) failed to boot and Linux (2.2.17) claimed the IRQ
used by my Creative Labs AWE 64 was in use. For some reason, telling
the motherboard BIOS not to assign an interrupt to the video card
cured both these problems, although the IRQ occupied by the video card
(12) is never used by anything and nothing shares the AWE 64's
IRQ. Personally, I'm putting this down the dodgy PNP support of the
AWE 64.
BTW, the motherboard uses the VIA MVP3 chipset and the only expansion
cards in the system are an AGP Voodoo Banshee, the AWE 64 and the
29160N.
I'm running out of ideas ... Help please.
--
I apologize if most of what I have written is total rubbish
Ant Sims
[EMAIL PROTECTED]
------------------------------
Reply-To: [EMAIL PROTECTED]
From: [EMAIL PROTECTED] (Rod Smith)
Subject: Re: Best OS
Date: Wed, 04 Oct 2000 22:03:34 GMT
[Posted and mailed]
In article <8rfccp$sfc$[EMAIL PROTECTED]>,
manny <[EMAIL PROTECTED]> writes:
> I want to hear feedback from the users on this list for their
> recommendation for the best Linux OS to use.
There is no single best answer to that questions, and your hardware and
applications don't really narrow the field much, aside from removing
ancient stuff (Red Hat 4.0, say). Check my web page on Linux
distributions for my thoughts on several:
http://www.rodsbooks.com/distribs/
--
Rod Smith, [EMAIL PROTECTED]
http://www.rodsbooks.com
Author of books on Linux & multi-OS configuration
------------------------------
Reply-To: [EMAIL PROTECTED]
From: [EMAIL PROTECTED] (Rod Smith)
Subject: Re: kodak DC215 zoom
Date: Wed, 04 Oct 2000 22:07:24 GMT
[Posted and mailed]
In article <[EMAIL PROTECTED]>,
"Ali" <cracker@$$$$redhotant.com> writes:
> has anyone managed to get a Kodak DC 215 zoom digital camera to work in
> linux. What is needed for twain support?
You don't use TWAIN to access digital cameras (or anything else) in
Linux. For digital cameras, the usual method is to use gPhoto
(http://www.gphoto.org), although you can also mount a CF or similar
media using an appropriate reader or occasionally use some
camera-specific package. According to the gPhoto web site, the DC215 is
supported. I use it with a DC240, and it works fairly well, given that
it's beta software, so some features are flaky or just plain broken. It
does work well enough to transfer images. I can manipulate them further
in the GIMP, xv, or whatever.
--
Rod Smith, [EMAIL PROTECTED]
http://www.rodsbooks.com
Author of books on Linux & multi-OS configuration
------------------------------
From: "Paul" <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux.mandrake
Subject: Re: CDROM burning
Date: Wed, 4 Oct 2000 23:14:49 +0100
Burn baby Burn
"William A. Maniatty" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Hello All:
>
> I have a PlexWriter RW 4/2/20 CD scsi CD burner on a dual processor
> Asus P2BDS motherboard (Dual PIII 500's) and 256 MB of ECC RAM.
> I am using mandrake 7.0 from a boxed distribution set, xcdroast might
> and its supporting software could have been downloaded from say
rpmfind.net
> by the guy my vendor had install the cdwriter.
>
> I have 2 possibly related problems:
>
> 1) When I go to burn a CD using xcdroast it takes a long time
> (about 75 minutes) although xcdroast indicates the write speed is 4x.
>
> 2) I've been having difficulty getting my cd burner to do complete burns
> (often failing with write errors).
>
> xcdroast's front screeen claims that is is 0.96e and relies on:
> cdrecord-1.61
> mkisofs-1.12b4
>
> rpm -q, reports:
> cdrecord-1.8a29-3mdk
> mkisofs-1.12b5-3mdk
> xcdroast-0.96e-7mdk
>
>
> Is there a way to determine if this is due to driver software or a
> hardware error on the cd burner?
>
> Thanks:
>
> Bill Maniatty
------------------------------
From: Bryan Siemon <[EMAIL PROTECTED]>
Subject: Re: 2.4.0-test8 and PDC 20265
Date: Wed, 04 Oct 2000 22:32:45 GMT
You have an IRQ conflict. That first PCI slot will automatically share its
IRQ with the AGP slot. Unfortunately, the Ultra 66 card requires its own
IRQ. You have to move the Ultra 66 card off that first PCI slot. (You can
put the NIC there in its place)
[EMAIL PROTECTED] wrote:
> Hi all,
>
> I am trying very hard to get kernel 2.4.0-test8 to recognize the Promise
> Ultra66 PCI IDE add-on card -- based on PDC 20265.
>
> The motherboard is a FIC SD-11 (Athlon 700). The only other PCI card is
> a
> D-link quad ethernet card (DFE-570TX).
>
> The kernel correctly recognizes the card as a PDC-20265, but the drives
> on
> the controller are not recognized. The drive is a standard IBM 4.3 G
> IDE
> drive.
>
> The card is in PCI Slot-1 (next to the AGP slot). The award BIOS doesn't
> recognize the card. I dont' see anything in the BIOS boot messages that
> say
> "Promise Ultra66".
>
> The odd thing is that, the motherboard won't boot unless I disable the
> BIOS
> interrupts for the addon card -- this is an option in one of the award
> BIOS
> setup screens.
>
> The rest of the box is a clean install of SuSE 6.4.
>
> The following messages are from Linux startup:
> === dmesg ===
> mtrr: v1.36 (20000221) Richard Gooch ([EMAIL PROTECTED])
> PCI: PCI BIOS revision 2.10 entry at 0xfdb01, last bus=2
> PCI: Using configuration type 1
> PCI: Probing PCI hardware
> PCI: Using IRQ router VIA [1106/0586] at 00:07.0
> Linux NET4.0 for Linux 2.4
> Based upon Swansea University Computer Society NET3.039
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP
> IP: routing cache hash table of 512 buckets, 4Kbytes
> TCP: Hash tables configured (established 8192 bind 8192)
> Starting kswapd v1.7
> pty: 256 Unix98 ptys configured
> Uniform Multi-Platform E-IDE driver Revision: 6.31
> ide: Assuming 33MHz system bus speed for PIO modes; override with
> idebus=xx
> PDC20262: IDE controller on PCI bus 00 dev 18
> PDC20262: device not capable of full native PCI mode
> PDC20262: device disabled (BIOS)
> VP_IDE: IDE controller on PCI bus 00 dev 39
> VP_IDE: chipset revision 6
> VP_IDE: not 100% native mode: will probe irqs later
> VP_IDE: VIA vt82c686a IDE UDMA66 controller on pci0:7.1
> ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DMA
> ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:pio, hdd:pio
> hda: WDC WD64AA, ATA DISK drive
> hdb: WDC WD64AA, ATA DISK drive
> ide: Assuming 33MHz system bus speed for PIO modes; override with
> idebus=xx
> hdc: Maxtor 91361U3, ATA DISK drive
> hdd: CREATIVE CDROM CD5232E, ATAPI CDROM drive
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> ide1 at 0x170-0x177,0x376 on irq 15
> hda: 12594960 sectors (6449 MB) w/2048KiB Cache, CHS=784/255/63, UDMA
> (33)
> hdb: 12594960 sectors (6449 MB) w/2048KiB Cache, CHS=784/255/63, UDMA
> (33)
> hdc: 26588016 sectors (13613 MB) w/512KiB Cache, CHS=26377/16/63, UDMA
> (33)
> Partition check:
> hda: hda1 hda2 hda3 hda4 < hda5 hda6 >
> hdb: hdb1 hdb2
> hdc: [PTBL] [1655/255/63] hdc1
> Floppy drive(s): fd0 is 1.44M
> FDC 0 is a post-1991 82077
> Serial driver version 5.02 (2000-08-09) with MANY_PORTS SHARE_IRQ
> SERIAL_PCI
> enabled
> ttyS00 at 0x03f8 (irq = 4) is a 16550A
> Real Time Clock Driver v1.10c
> Linux Tulip driver version 0.9.10 (September 6, 2000)
> eth0: Digital DS21143 Tulip rev 65 at 0xbc00, 00:80:C8:CA:A7:69, IRQ 9.
> eth0: EEPROM default media type Autosense.
> eth0: Index #0 - Media MII (#11) described by a 21142 MII PHY (3)
> block.
> eth0: MII transceiver #1 config 3100 status 7869 advertising 01e1.
> eth1: Digital DS21143 Tulip rev 65 at 0xb800, 00:80:C8:CA:A7:6A, IRQ 11.
> eth1: EEPROM default media type Autosense.
> eth1: Index #0 - Media MII (#11) described by a 21142 MII PHY (3)
> block.
> eth1: MII transceiver #1 config 3100 status 7849 advertising 01e1.
> eth2: Digital DS21143 Tulip rev 65 at 0xb400, 00:80:C8:CA:A7:6B, IRQ 5.
> eth2: EEPROM default media type Autosense.
> eth2: Index #0 - Media MII (#11) described by a 21142 MII PHY (3)
> block.
> eth2: MII transceiver #1 config 3100 status 7849 advertising 01e1.
> eth3: Digital DS21143 Tulip rev 65 at 0xb000, 00:80:C8:CA:A7:6C, IRQ 10.
> eth3: EEPROM default media type Autosense.
> eth3: Index #0 - Media MII (#11) described by a 21142 MII PHY (3)
> block.
> eth3: MII transceiver #1 config 3100 status 7849 advertising 01e1.
> Linux agpgart interface v0.99 (c) Jeff Hartmann
> agpgart: Maximum main memory to use for agp memory: 94M
> agpgart: Detected AMD Irongate chipset
> agpgart: AGP aperture is 512M @ 0xc0000000
> [drm] AGP 0.99 on AMD Irongate @ 0xc0000000 512MB
> [drm] Initialized tdfx 1.0.0 20000719 on minor 63
> kmem_create: Forcing size word alignment - nfs_fh
> ===== end dmesg ===
>
> This is from /proc/ioports:
> 0000-001f : dma1
> 0020-003f : pic1
> 0040-005f : timer
> 0060-006f : keyboard
> 0070-007f : rtc
> 0080-008f : dma page reg
> 00a0-00bf : pic2
> 00c0-00df : dma2
> 00f0-00ff : fpu
> 0170-0177 : ide1
> 01f0-01f7 : ide0
> 0376-0376 : ide1
> 03c0-03df : vga+
> 03f6-03f6 : ide0
> 03f8-03ff : serial(auto)
> 0400-040f : VIA Technologies, Inc. VT82C686 [Apollo Super ACPI]
> 0cf8-0cff : PCI conf1
> 1170-1177 : Promise Technology, Inc. 20262
> 11f0-11f7 : Promise Technology, Inc. 20262
> 1374-1377 : Promise Technology, Inc. 20262
> 13f4-13f7 : Promise Technology, Inc. 20262
> 5000-50ff : VIA Technologies, Inc. VT82C686 [Apollo Super ACPI]
> 6000-607f : VIA Technologies, Inc. VT82C686 [Apollo Super ACPI]
> 6800-683f : Promise Technology, Inc. 20262
> 8000-8fff : PCI Bus #01
> 8c00-8cff : 3Dfx Interactive, Inc. Voodoo 3
> 9000-bfff : PCI Bus #02
> b000-b07f : Digital Equipment Corporation DECchip 21142/43 (#4)
> b000-b07f : eth3
> b400-b47f : Digital Equipment Corporation DECchip 21142/43 (#3)
> b400-b47f : eth2
> b800-b87f : Digital Equipment Corporation DECchip 21142/43 (#2)
> b800-b87f : eth1
> bc00-bc7f : Digital Equipment Corporation DECchip 21142/43
> bc00-bc7f : eth0
> d400-d41f : VIA Technologies, Inc. UHCI USB
> d800-d81f : VIA Technologies, Inc. UHCI USB (#2)
> dc00-dc03 : Advanced Micro Devices [AMD] AMD-751 [Irongate] System
> Controller
> ffa0-ffaf : VIA Technologies, Inc. Bus Master IDE
> ffa0-ffa7 : ide0
> ffa8-ffaf : ide1
>
> == End /proc/ioports ===
>
> I did try:
> "ide2=0x1170,0x1376"
> on the command line -- but, it didn't make any difference.
>
> Looking at pdc202xx.c doesn't yield any helpful hints for me to try.
>
> Unfortunately, this box has _never_ had any other OS other than Linux --
> infact, it is a brand new box assembled from parts. So, I can't verify
> if
> lesser OSen can see the card.
>
> I'd appreciate if anyone can share their experiences and thoughts on
> where I
> might try to find a fix for this.
>
> Thanks.
> -Sudhi.
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
------------------------------
From: [EMAIL PROTECTED]
Subject: Passing huge command lines to kernel???
Date: 04 Oct 2000 18:39:33 -0400
Dear Linux Hackers,
Earlier, I asked how to get a RAID system working with a four drives connected
to two Promise Ultra66 controllers.
It turns out that to detect the drives properly, I need a boot option like
this:
append="hde=7473,255,63 hdg=7473,255,63 hdi=7473,255,63 hdk=7473,255,63"
(The numbers are the C/H/S values for a Maxtor 60G drive.)
Well it boots OK, except it only sees the command line for the first two
drives! After this it bails out with an error message:
ide_setup: hdi=7473,255 -- BAD OPTION
So, drives three and four are detected wrong.
I noticed that this command line (with the other stuff the kernel adds) is
exactly 80 characters long. Is it a coincidence? Is there any way to parse a
longer bootprompt???
Thanks in advance,
Richard
PS: I'm running 2.4.0-test8 if that matters.
------------------------------
Date: Wed, 04 Oct 2000 17:19:14 -0500
From: "Richard M. Denney" <[EMAIL PROTECTED]>
Subject: Re: CD Writer errors: Hot connecting and removing devices on SCSI bus
"Richard M. Denney" wrote:
> Question: Can one add to or remove from a SCSI bus non-busy SCSI
> devices? On the basis of the May 1996 SCSI-HOWTO, I have been trying
>
> echo "scsi remove-single-device 0 0 1 0" /proc/scsi/scsi
> and
> echo "scsi add-single-device 0 0 1 0" /proc/scsi/scsi
> to no avail.
>
> The reason I would like to be able to do this has to do with my
> difficulties writing verifiable CDROMS is as follows:
> -------------------------------------------------------------------
>
> I have a pentium III 450 MHz system with Redhat 6.0 upgraded to kernel
> 2.2.17. It generally works fine.
>
> On a SCSI bus (aix7xxxdriver) Adaptec 2930CU card, I have a Yamaha
> CRW4416SX cd writer (scsi device 1), two microtek scanners (a flatbed E6
> as device 4, a 35t slide scanner as device 5), and a zip drive as device
> 6. All these components work find, with the exception noted below.
>
> Situation 1 (bad CDROMS): Boot Linux with all SCSI devices turned on and
> attempt to write a CDROM with cdrecord 1.6. Result: I get write errors:
> the writer stops at random times during the write phase.
>
> Situation 2 (some good CDROMS): Boot as in Situation 1 (all SCSI
> devices on). Turn off the CD Writer, disconnect the downstream devices
> (scanners and zip drive) and turn on termination on writer to "ON".
> Result: The writer now writes complete CDROMS and never stops during the
> writing phase. However, about one-third of written CDROMS cannot be
> "verified" with xcdroast. The failures to verify occur at different
> places in different CDROMS, usually somewhere between one-third and
> two-thirds of the way through the CDROM. Most files appear to be OK when
> such a CDROM is mounted. Thus, there appear to be infrequent, but
> troublesome, write errors.
>
> Situation 3 (good CDROMS, at least so far): Boot with only the CD writer
> attached to the SCSI card (and termination "ON"). The CD writer seems to
> work fine and the resulting CDROMS appear to be verifiable. (At least a
> few in a row, which is much better than in situation 2.
>
> Rebooting linux when I need to write a CDROM (a la situation 3) is a
> considerable nuisance if I am also scanning images with the SCSI
> scanners. As indicated above, attempts to add or remove the downstream
> SCSI devices with the the echo commands in the SCSI-HOWTO do not seem to
> work in my hands (no change in the /proc/scsi/scsi file.) Perhaps the
> problem is that that HOWTO is written for general scsi (sg) devices. The
> cdwiter is assigned to scd0 (not sg0). The zip drive is assigned to sd0,
> and I am not sure what the scanners are assigned to.
>
> The /proc/scsi/scsi file (with the CDWRITER only):
>
> Attached devices:
> Host: scsi0 Channel: 00 Id: 01 Lun: 00
> Vendor: YAMAHA Model: CRW4416S Rev: 1.0g
> Type: CD-ROM ANSI SCSI revision: 02
> ---------------------------------------------------------------
>
> Any suggestions appreciated.
>
> Rick
Sorry! I just found the answer to my own problem. I see in the "echo ..."
statement (see above) that I left out the ">" before /proc/scsi/scsi. I can
add and subtract downstream SCSI devices with no problem. Yay!
Rick
------------------------------
From: "ekkis" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.admin,comp.os.linux.misc,linux.redhat.misc,linux.scsi
Subject: tar but no dump - help?
Date: Wed, 4 Oct 2000 16:24:57 -0700
hi all,
I'm having a problem backing up a file system to tape using "dump". I can
tar to the device (read and write) so I know there's nothing wrong
with the hardware or drivers... can anyone help point me ine right
direction?
here's my command and it's output:
root@beowulf:/root # dump -0u -f /dev/st0 /home/ftp/mp3z
DUMP: Date of this level 0 dump: Mon Oct 2 13:32:48 2000
DUMP: Date of last level 0 dump: the epoch
DUMP: Dumping /dev/hdb1 (/ (dir home/ftp/mp3z)) to /dev/st0
DUMP: Label: none
DUMP: mapping (Pass I) [regular files]
DUMP: mapping (Pass II) [directories]
DUMP: estimated 3913078 tape blocks on 99.97 tape(s).
DUMP: Volume 1 started at: Mon Oct 2 13:32:49 2000
DUMP: dumping (Pass III) [directories]
DUMP: dumping (Pass IV) [regular files]
DUMP: Closing /dev/st0
DUMP: Volume 1 completed at: Mon Oct 2 13:34:44 2000
DUMP: Volume 1 took 0:01:55
DUMP: Volume 1 transfer rate: 333 KB/s
DUMP: Change Volumes: Mount volume #2
DUMP: Is the new volume mounted and ready to go?: ("yes" or "no") y
DUMP: Cannot open output "/dev/st0".
DUMP: Do you want to retry the open?: ("yes" or "no") n
DUMP: The ENTIRE dump is aborted.
the drive has 4 tapes. When dump first asks
whether the "new volume" is mounted, I switch to the next tape by issuing:
root@beowulf:/var/log # mtx -f /dev/sg1 next
Unloading Data Transfer Element into Storage Element 1...done
and then respond "y" (which fails).
Some useful info:
root@beowulf:/root # uname -a
Linux beowulf 2.2.14-5.0 #1 Tue Mar 7 20:53:41 EST 2000 i586 unknown
root@beowulf:/root # tapeinfo -f /dev/sg1
Product Type: Tape Drive
Vendor ID: 'ARCHIVE '
Product ID: 'Python 28849-XXX'
Revision: '4.CM'
Attached Changer: No
DataCompEnabled: yes
DataCompCapable: yes
DataDeCompEnabled: yes
CompType: 0x20
DeCompType: 0x20
ActivePartition: 0
EarlyWarningSize: 0
NumPartitions:0
MaxPartitions:1
MinBlock:1
MaxBlock:16777215
root@beowulf:/root # mtx -f /dev/sg1 status
Storage Changer /dev/sg1:1 Drives, 4 Slots ( 0 Import/Export )
Data Transfer Element 0:Full (Storage Element 2 Loaded)
Storage Element 1:Full
Storage Element 2:Empty
Storage Element 3:Full
Storage Element 4:Full
Also, something weird, the directory I'm trying to dump is a little over
3GB:
root@beowulf:/root # ls /home/ftp/mp3z |head -1
total 3885396
and my tapes should fit 4GB (uncompressed), however if you'll notice in the
dump output:
DUMP: estimated 3913078 tape blocks on 99.97 tape(s).
the number of tapes calculated is BIG! What's up with this?
any help greatly appreciated. - erick
p.s. please e-mail so I don't have to keep coming back to the newsgroup,
thx!
------------------------------
From: "Paul Kuliniewicz" <[EMAIL PROTECTED]>
Subject: Re: SB Live! doesn't work under Red Hat 7.0 (New Information)
Date: Wed, 4 Oct 2000 18:21:20 -0500
OK, I did a little digging and, after scouring the Sound HOWTO and poking
around, I believe I may have found the problem.
According to Windows 2000, my SB Live! is on IRQ 9 and has an I/O range of
0xDF80-0xDF9F. However, I get the following information from dmesg on
Linux:
Creative EMU10K1 PCI Audio Driver, version 0.6, 16:53:07 Aug 22 2000
emu10k1: EMU10K1 rev 7 model 0x8031 found, IO at 0xdf80-0xdf9f, IRQ11
It finds the proper I/O range, but it thinks that the IRQ is 11 and not 9,
where it should be. I'm no expert on this stuff, but that seems to be a
likely candidate for the cause of this problem.
So now my question is, just how do I override this and explicitly tell
emu10k1 or soundcore or whatever module what the proper IRQ is. In
sndconfig that comes with Red Hat 7.0, it doesn't prompt for an IRQ when you
select SB Live!, so I'm guessing there's going to be some manually editing
config files. Does anyone know what I have to do to make it look on IRQ 9?
In case that's not enough, here's some symptoms of this problem:
/dev/sndstat seems to be empty -- a "cat /dev/sndstat" returns an error and
not information about the sound hardware etc.
/dev/audio does not play sound -- I tried "cat sample.au >/dev/audio" and no
sound played
/dev/dsp does not play sound -- I tried "cat sample >/dev/dsp" and no sound
played
To reiterate, since this is likely a result of a mistaken IRQ, how do I tell
the sound module what the proper IRQ is? Thanks in advance.
------------------------------
From: "seldan" <[EMAIL PROTECTED]>
Subject: BIOS Limitations on HP Vectra
Date: Wed, 04 Oct 2000 23:33:24 GMT
Hello all,
I am getting ready to configure an old HP Vectra 5/xxx series 5 machine
(200MHz) as an FTP server running linux.
I am planning on installing two 20.5GB hard drives into the computer,
however I was notified that the BIOS may have difficulty recognizing them.
After searching around, I discovered that the BIOS will not support over 8GB
without an upgrade, provided on the HP Support site. However, this upgrade
will only extend the limit to 12GB. The wording from HP is "Disks larger
than 8GB, and smaller than 12GB... as a boot disk" "Disks larger than 12GB
and smaller than 30GB... supported under WinNT4 as 2nd disk."
My question is... would these limitations still apply if I run linux on the
machine? I am under the impression that they would not but it will be some
time before I can get 2 20GB drives to test and I'd rather avoid the wait
and look into newer hardware alternatives if this is bound to fail.
Any help on this would be greatly appreciated as it would help me get linux
up and running for my company!!!
Regards,
Tom.
[EMAIL PROTECTED]
------------------------------
From: "R.K.Aa." <[EMAIL PROTECTED]>
Subject: Re: how can I use my IDE CD-RW for linux ?
Date: Thu, 05 Oct 2000 01:38:12 +0200
??? wrote:
> Hi all,
> I have a IDE WPI 4424 CD-RW
> I was downloaded "gtoaster", in preferences valid drives is /dev/scd0
> but my drive on /dev/hdd for CD-RW
> I edit it but cant work...
>
the CD-Writing HOWTO is found at
http://www.guug.de/~winni/linux/CD-Writing/html/
in t he quickstart there's a few sample scripts to load/test drivers with.
As for making linux recognize the CD/RW as a fake SCSI device (which
you'll have to do) you at least initially should place this line in
your lilo.conf (if you use that) and then run /sbin/lilo
append="hdb=ide-scsi"
Read more about this in the HOWTO.
I just installed a CD/RW myself and found that several of the drivers
(or modules) the HOWTO refer to were actually precompiled into the
kernel (RH6.2). Took me a while to figure out why i didn't find those
modules at first. At least in RH6.2 ALL the modules you need are already
in the kernel - or it's made modular for them, so they are where they
should be, just waiting to be insmod'ed (or modprobe'd - whatever you
prefer.)
Good luck.
R.K.Aa.
------------------------------
From: "R.K.Aa." <[EMAIL PROTECTED]>
Subject: Re: how can I use my IDE CD-RW for linux ?
Date: Thu, 05 Oct 2000 01:41:25 +0200
??? wrote:
> Hi all,
> I have a IDE WPI 4424 CD-RW
> I was downloaded "gtoaster", in preferences valid drives is /dev/scd0
> but my drive on /dev/hdd for CD-RW
> I edit it but cant work...
>
an error in my previous reply:
you of course refer to the actual drive, so in your case it would be
append="hdd=ide-scsi"
R.K.Aa.
------------------------------
From: "R.K.Aa." <[EMAIL PROTECTED]>
Subject: Re: scanners
Date: Thu, 05 Oct 2000 01:49:42 +0200
Ken Siersma wrote:
> Hello,
> A few easy questions -Would like to hook up a USB scanner to a linux
> machine. Will it work? Any suggestions on software for using it? Does
> Windoze NT support USB?
>
> Thanks,
> Ken
go to http://www.qbik.ch/usb/devices/ and click working devices.
Some USB Scanners are supported. (those with a green tag at end)
More USB info about eventual patches needed etc. at
http://www.linux-usb.org/
As for software, use SANE in combo with Xsane or the Gimp.
http://panda.mostang.com/sane/
http://www.wolfsburg.de/~rauch/sane/sane-xsane.html
R.K.Aa.
------------------------------
** 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
******************************
