Linux-Hardware Digest #377, Volume #13 Tue, 8 Aug 00 08:13:06 EDT
Contents:
Deutschers: Was fuer ein Modem haben Sie? (Karen Heiby)
Rechten vraagje over getty/mgetty/uugetty --- BELANGRIJK !!! ("Jan Stolk")
IDE tape drive setup (Jef Peeraer)
Re: What distribution to install ? (James Stafford)
Question for RIGHTS on getty/mgetty/uugetty --- IMPORTANT !!! ("Jan Stolk")
Re: 45GB harddisk with old BIOS??!! ("K. Posern")
Re: 45GB harddisk with old BIOS??!! ([EMAIL PROTECTED])
Hard Drive Errors (Nicholas Wolverson)
USB scanner for Linux? ([EMAIL PROTECTED])
[Q] VOIP on Linux (Mohd-Hanafiah Abdullah)
Re: 45GB harddisk with old BIOS??!! (Jon Larsson)
Strange problems with Promise Ultra100 (Jon Larsson)
Re: Cannon BJC printer (Romek Pitera)
problems with a 30GB hard disk (under Suse6.4) (Torsten Metzner)
Re: How to Install a SCSI Card (Guy Maskall)
Re: Problems with SCSI card (RH 6.2) (Guy Maskall)
----------------------------------------------------------------------------
From: Karen Heiby <[EMAIL PROTECTED]>
Subject: Deutschers: Was fuer ein Modem haben Sie?
Date: Tue, 08 Aug 2000 08:59:15 GMT
Hallo, ich brauche ein neues Modem. Koennen Sie ein Modem empfehlen? Ich
brauche 56K v90, ISA (internal).
Ich habe jetzt, nur eine *sehr* langsame Verbindung hier in Deutschland mit
meinem Amerikanischen Modem, und Internet Suchen sind sehr schwer.
Es w�rde einfacher sein, wenn Sie ein gerade vorschlagen konnten.
Vielen Dank,
Karen Heiby
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: "Jan Stolk" <[EMAIL PROTECTED]>
Subject: Rechten vraagje over getty/mgetty/uugetty --- BELANGRIJK !!!
Date: 8 Aug 2000 08:55:37 GMT
Ik heb een situatie dat 2 (RedHat) linux servers met elkaar moeten bellen.
Laten we zeggen server A en server B. Dit t.b.v. van een UUCP sessie.
Alle UUCP zaken zijn in orde. Als vanaf server A via UUCP bestanden naar
server B gekopieerd wordt dan werkt dit feilloos. Het maakt niet uit hoe
vaak dit gebeurd.
Echter... en nu komt mijn eigenlijke probleem: Als server B heeft ingebeld
op server A dan worden de rechten van mijn modem device "/dev/ttyS2" terug
gezet naar: "crwx------", de owner wordt "root" en de group "tty".
Het is natuurlijk duidelijk dat de getty/mgetty/uugetty op device
/dev/ttyS2 de rechten terugzet op het moment dat de inbelsessie vanaf de
andere kant wordt beeindigd. Er wordt dan een nieuwe getty/mgetty/uugetty
voor dit device gestart die deze rechten zet.
Met andere woorden alleen de root heeft nog rechten te bellen met dit
device. Mijn UUCP sessie naar server B gaan nu niet meer goed vanwege deze
rechten. Zet ik handmatig de rechten op "crwx------", owner "uucp" dan
werkt het weer.
Hoe kan ik regelen dat deze rechten automatisch op bijvoorbeeld owner
"uucp" of crwxrwxrwx gezet ?
Is dit een instelling bij getty/mgetty/uugetty ?
Dank u.
Jan Stolk
[EMAIL PROTECTED]
------------------------------
From: Jef Peeraer <[EMAIL PROTECTED]>
Subject: IDE tape drive setup
Date: Tue, 08 Aug 2000 09:13:58 GMT
I have a HP colorado 20 GB interbal IDE. I tried to set it up with SCSI
emulation, but it didn.t work. Now I saw someone just setting it up as a
ide-tape drive ( standard kernel ). At a certain point I've got this
ide-tape drive error :
Uniform Multi-Platform E-IDE driver Revision: 6.30
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
ALI15X3: IDE controller on PCI bus 00 dev 78
ALI15X3: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:pio, hdd:pio
hda: IBM-DPTA-372050, ATA DISK drive
hdc: MATSHITA CR-583, ATAPI CDROM drive
hdd: HP COLORADO 20GB, ATAPI TAPE drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: IBM-DPTA-372050, 19574MB w/1961kB Cache, CHS=2495/255/63, UDMA(33)
hdc: ATAPI 8X CD-ROM drive, 128kB Cache, DMA
Uniform CD-ROM driver Revision: 3.09
ide-tape: hdd <-> ht0: HP COLORADO 20GB rev 4.01
ide-tape: ht0: I/O error, pc = 1a, key = 4, asc = 40, ascq = a0
ide-tape: Can't get tape parameters - assuming some default values
ide-tape: hdd <-> ht0: 450KBps, 6*26kB buffer, 4394kB pipeline, 110ms
tDSC, DMA
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
rtl8139.c:v1.07 5/6/99 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/rtl8139.html
eth0: SMC1211TX EZCard 10/100 (RealTek RTL8139) at 0xd400, IRQ 11,
00:10:b5:07:44:2d.
Partition check:
hda: hda1 < hda5 hda6 hda7 >
Jef
------------------------------
From: James Stafford <[EMAIL PROTECTED]>
Subject: Re: What distribution to install ?
Date: Tue, 08 Aug 2000 09:18:33 GMT
> Yeah, right.... All you had to do was, at the LILO prompt, type 'linux
> single'
> When it booted, it would have dropped you to single user mode.
> You could have then fsck'ed and mounted the filesystems, then used the
> passwd program to your heart's content, changing the password.
> Then reboot.....
>
> As for the kernel compiling... obviously you didn't "make install" the first
> time you compiled a new kernel revision, which would have made all the .map
> and symbol files for you, etc... mod.conf? I think it's called modules.conf,
> and again, it would have been done for you with a simple 'make modules &&
> make modules_install'
>
> I hear lot of people putting RedHat down... and some of the reasons are
> valid. Your ignorance is not a valid reason to insult an otherwise stable
> and useable linux distribution.
>
> Just my two cents
Well be it my ignorance or not, every time I've ever booted a Red Hat
distro it takes me right to X, no chance to type anything. The Red Hat
boot disks take me right to an install/update screen. I've been using
Linux for years. Here is the real problem; Red Hat has changed and moved
so much a experienced Linux user can't find a single thing, because
nothing is where they're used to it being. I always do a make
modules/_install on my Slackware box when I recompile the kernel, I
can't see why I would forget to do it with Red Hat. I guess I could go
and buy a book just to learn how Red Hat has screwed up Linux.
MHO,
jamess
--
"On the side of the software box, in the 'System Requirements' section,
it said 'Requires Windows 95 or better'. So I installed Linux."
-Anonymous
------------------------------
From: "Jan Stolk" <[EMAIL PROTECTED]>
Subject: Question for RIGHTS on getty/mgetty/uugetty --- IMPORTANT !!!
Date: 8 Aug 2000 09:19:13 GMT
I have this situation that 2 (RedHat) linux servers need to communicate
with each other.
Let's say server A and server B. This is to use UUCP.
All UUCP things are OK. When server A (via UUCP) copies files to server B
this works excellent. It works all the time.
But... (here's the problem) : When server B only once called server A the
rights of /dev/ttyS2 on server A are reset to:
"crwx------", the owner becomes "root" and the group becomes "tty".
Ofcourse... when server B ends the connection a new getty/mgett/uugetty is
initialized for /dev/ttyS2 and at this point the rights (as described
above) are set for /dev/ttyS2. Now... my UUCP is not working anymore :-(((
>From this moment on it is not possible anymore to use UUCP because the
access is denied for this proces.
When I manually set the rights for /dev/ttyS2 to "crwxrwxrwx" or set the
owner to user "uucp" the UUCP is working again.
...until server B calls server A again.
How do I get the rights to "crwxrwxrwx" or set the user to "uucp" on device
/dev/ttyS2 automaticly every time a new getty/mgetty/uugetty is initialized
???
Thank u.
Jan Stolk
[EMAIL PROTECTED]
------------------------------
From: "K. Posern" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: 45GB harddisk with old BIOS??!!
Date: 8 Aug 2000 09:35:48 GMT
Hi.
Fist: Thanks for your answer!
E J wrote:
> Look at the IBM documentation and find out what the correct CHS and pass
> the correct parameters to the kernal.
But which are the *correct* CHS?
At the hdd itself are noted the following ones:
Capacity: 46.1GB
LBA: 90,069,840 Sectors
CHS: 16383/16/63
At the homepage of IBM there I found the following (under Product Specs of my
hdd):
Sector size (bytes): 512
Recording zone: 15
User cylinders (physical): 27,724
Data heads (physical): 6
Data disks: 3
?
So what should I pass to the kernel?
"hdc=x,y,z" ?
And: IS Linux capable to work with my harddisc even if it is DEACTIVATED in
the BIOS?
And: The error-messages "hdc: IRQ probe failed (0)" at boot-time will
disappear with the right CHS-values?
And: Will there further be the message: "hdc: non-IDE (!!!!) drive, CHS=x/y/z"
at boot-time?
> The recent fix to the handle hard disk bigger than 32G is probably in your
> kernal.
How can I test this? - I've got 2.2.14.
> I know in the Maxtor, you can jumper the 40G so it looks like a 2G hard
> drive, but it give you a new set of
> CHS numbers to access the entire hard disk. See if you can do the same
> thing for the IBM drive.
That's with the IBM drive too.
But does this bring a lack of performance?
> As a last resort, you can get a disk overlay for your IBM 45G Hard drive.
> You might try the IBM website to see if you download it.
> For Maxtor, I usually get the disk overlay program EZ-BIOS from their
> website.
Yes there is something like that for IBM too.
But again (for this workaround): Would The use of an ondisk-manager mean to
have less performance?
Ciao,
Knuth Posern
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.setup
Subject: Re: 45GB harddisk with old BIOS??!!
Date: Tue, 08 Aug 2000 09:36:41 GMT
In article <[EMAIL PROTECTED]>,
E J <[EMAIL PROTECTED]> wrote:
> Look at the IBM documentation and find out what the correct CHS and
pass
> the correct parameters to the kernal.
No, do NOT do this. Following an industry convention for large disks,
the documentation will say it has a CHS of 16383/16/63.
However, I have the exact same disk and for me it works just fine with a
CHS of 5606/255/63. In toher words, that is what you should specify.
> You can't fool it by giving fake CHS numbers hoping to get the correct
CHS
> from autoprobing.
> The recent fix to the handle hard disk bigger than 32G is probably in
your
> kernal.
Then again, it might NOT be. What kernel version are you using? Upgrade
to 2.2.16 if you have the possibility.
> I know in the Maxtor, you can jumper the 40G so it looks like a 2G
hard
> drive, but it give you a new set of
> CHS numbers to access the entire hard disk. See if you can do the
same
> thing for the IBM drive.
Not a good idea, as IBM disks have a history of not only reporting a
different CHS if you set that jumper, but also disabling all IO
operations beyond the clipped capacity.
> As a last resort, you can get a disk overlay for your IBM 45G Hard
drive.
> You might try the IBM website to see if you download it.
> For Maxtor, I usually get the disk overlay program EZ-BIOS from their
> website.
IBM supplies the OnTrack Disk Manager. However, when I tried using it
for my IBM drive, it failed to recognize the correct CHS every now and
then (in fact, it seemed to find different CHS values each time I
started the program). In other words, if you have a Linux-only system
or don't need the IBM disk in other OS:s you might run, just disable hdc
in BIOS and pass hdc=5606,255,63 to the kernel (though both 2.2.15 and
2.2.16 autodetected mine).
Good luck!
Jon
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: Nicholas Wolverson <[EMAIL PROTECTED]>
Subject: Hard Drive Errors
Date: Tue, 08 Aug 2000 09:51:56 GMT
Recently (last night, actually) my hard disk started spinning up and
down and not doing much. This caused everything to go *really* slowly,
and some things to crash, so I had a look at my logs. These error
messages appeard - note that I've actually got two hard drives,
configured as hda and hdb. hdb is my main drive, and the one most of the
errors seem to come from. The first one is repeated most often; it
happened many times while I was trying to write this.
hdb: status timeout: status=0x90 { Busy }
hdb: drive not ready for command
ide0: reset: success
##
hdb: irq timeout: status=0x90 { Busy }
ide0: reset: success
##
hdb: irq timeout: status=0x90 { Busy }
end_request: I/O error, dev 03:45 (hdb), sector 376870
##
hdb: status error: status=0x7e { DriveReady DeviceFault SeekComplete
DataRequest CorrectedError Index }
hdb: drive not ready for command
ide0: reset: success
##
And on the other one:
Aug 8 05:17:19 localhost kernel: hda: status error: status=0x10 {
SeekComplete
}
Aug 8 05:17:19 localhost kernel: hda: drive not ready for command
I'm unsure as to whether this is a hardware problem, or something
software related, or what. I'm suspicious as to why both HD's show
errors. I thought somebody might be able to enlighten me as to what's
happening.
Thanks.
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: [EMAIL PROTECTED]
Subject: USB scanner for Linux?
Date: Tue, 08 Aug 2000 09:51:24 GMT
hi
are there USB scanners that work under Linux? which can you recommend?
martin
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: [EMAIL PROTECTED] (Mohd-Hanafiah Abdullah)
Crossposted-To:
comp.os.linux.advocacy,comp.os.linux.misc,comp.os.linux.networking,comp.os.linux.setup
Subject: [Q] VOIP on Linux
Date: 8 Aug 2000 18:06:41 +0800
How do I use VOIP on Linux? What's the necessary hardware/software that's
need for this purpose?
Thanks.
Napi
------------------------------
From: Jon Larsson <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: 45GB harddisk with old BIOS??!!
Date: Tue, 08 Aug 2000 10:14:57 GMT
In article <[EMAIL PROTECTED]>,
"K. Posern" <[EMAIL PROTECTED]> wrote:
> But which are the *correct* CHS?
See my previous post.
> And: IS Linux capable to work with my harddisc even if it is
> DEACTIVATED in the BIOS?
Yes, unless you want to boot from it, that is.
> And: The error-messages "hdc: IRQ probe failed (0)" at boot-time will
> disappear with the right CHS-values?
That is really odd. Haven't seen anything like that before. You'll just
have to try it out and see what happens.
> And: Will there further be the message: "hdc: non-IDE (!!!!) drive,
> CHS=x/y/z" at boot-time?
Once again, hopefully not. =)
> > The recent fix to the handle hard disk bigger than 32G is probably
> > in your kernal.
>
> How can I test this? - I've got 2.2.14.
Just get the latest one to make sure. However, there should be some sort
of info in /usr/src/linux/Documentation (or wherever you store your
source tree).
> That's with the IBM drive too.
>
> But does this bring a lack of performance?
See my previous post.
> Yes there is something like that for IBM too.
> But again (for this workaround): Would The use of an ondisk-manager
> mean to have less performance?
Not necessarily, but it can cause a bunch of other problems, so try to
avoid it. However, using Ontrack is _necessary_ if you want to use the
drive with any Microsoft OS.
/ Jon
=====
The box said "Requires Windows 95 or better", so I installed Linux!
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: Jon Larsson <[EMAIL PROTECTED]>
Subject: Strange problems with Promise Ultra100
Date: Tue, 08 Aug 2000 10:48:59 GMT
I hope you will excuse this slightly lengthy post. This problem actually
spans across a bunch of forums, but I thought I'd start here, as this is
where I think I will find the people most qualified to deal with it.
I have a Dell Dimension XPS P200s that came with a WDC 2.5GB drive. The
onboard controller I believe is Fast ATA-2 (at least not UDMA). A couple
of years ago I installed a Seagate Medalist Pro 9.1GB UDMA/33. Neither
the BIOS, nor Linux, Win9x or Win2k had any problems whatsoever with
that configuration.
A couple of weeks ago, my WDC went to the happy hunting-grounds and I
bought an IBM DeskStar 75GXP 46.1GB UDMA/100 to replace it. After some
tweaking, everything except Win98 worked (it refused to recognize both
drives together - it was one or the other). To correct that problem (and
gain some performance), I bought a Promise Ultra100 controller.
When I moved my drives to the Ultra100, Linux was just fine (after
passing ide0=[ultra100 IO] too the kernel), but Win98 didn't even want
to boot (it dropped to CLI during boot). However, DOS saw all partitions
on both drives. Promise suggested repartitioning the IBM drive. With
fdisk from within Linux (Mandrake 7.1, kernel 2.2.16)
I removed all partitions except the two primary Linux partitions. With
DOS fdisk I then recreated all other partitions and with Linux fdisk
changed the type of some of them. After this Win98 booted just fine.
After this I replaced Mandrake 7.1 with RedHat 6.2. Then Win98 dropped
to CLI during boot again. I thought it might help to repartition the
drives from Win2k, so I disconnected my IBM drive and reconnected the
Seagate to be master (still on the Ultra100). I cleared the Seagate
disk, installed Win2k and repartitioned. I then reconnected the IBM as
master again, only to see Win98 boot without problems - and this was
without the IBM drive even being touched.
I recompiled my Linux kernel and ran LILO. And then Win98 died again.
Repeating the Win2k installation/partitioning procedure did not help
this time.
Conclusions:
1. Installing LILO in the MBR (tried both with and without linear
option) makes Win98 drop to CLI during boot.
2. *Something* makes everything work again.
3. I need to find out what this something is. Could someone assisst me?
Oh, as an interesting sidenote, I could mention that I tried compiling
2.4.0-test5 when I had Mandrake installed. I included support for the
Ultra100 card (which required commenting a line about hwif->tri_proc in
pdc202xx.c as tri_proc didn't exist in hwif). This resulted in the
drives being translated with 16 heads instead of 255 (and subsequently
an obscene number of cylinders, for the IBM drive even in excess of
65535) and the partition check during boot reported both drives as
PTBL'ed into 1027/16/63. Odd, eh?
Grateful for any help,
/ Jon
=====
The box said "Requires Windows 95 or better", so I installed Linux!
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: Romek Pitera <[EMAIL PROTECTED]>
Subject: Re: Cannon BJC printer
Date: Tue, 8 Aug 2000 12:17:59 +0100
On Tue, 8 Aug 2000, Lake Park wrote:
> G'day.
>
> My linux is Redhat 6.2`
> It detects printer port as lp0
> When I try to print anything, printer doesn't work.
> On Windows 98, 2000 that is OK.
>
> The cannon bjc printer is not possible to print on Linux?
> Does anybody have an idea? How?
Have you checked printer list in Printing-HOWTO?
R Pitera
Direct your response to: r dot pitera at qmw dot ac dot uk
Direct spam or unsolicited commercial e-mail to: [EMAIL PROTECTED]
------------------------------
From: Torsten Metzner <[EMAIL PROTECTED]>
Subject: problems with a 30GB hard disk (under Suse6.4)
Date: 8 Aug 2000 11:32:36 GMT
Hi,
the following problem seems similar to the just discussed "45GB hard disk
problem and old bios" thread but in my opinion it is still
a little bit different, because I think I have a "new" bios which
can handle large disks !? OK here it comes:
I have a problem with the hardware, this means with a
30 GB Maxtor 33073U4 hard disk.
The follwing works fine:
- The bios recognizes the hard disk with 3736 cylinders, 255 heads and
63 sectors using the LBA mode.
- The fdisk of Windows95b recognizes the disk and can partitonize it without
any problems.
- My old Debian2.0 system with a 2.0.36 kernel recognizes the disk. It's no
problem to mount the disk, work on it or use cfdisk to modify something.
For this reasons it seems to me that my hardware is OK and the bios can
work with large disks.
But besides of this here are some information about my system:
- Epox board EP-51 MVP3E-M with a Award bios (bios is April 2000)
- VIA Apollo MVP3 AGP/PCIset chipset
_But_ the following does not work and I can't understand why:
- With Suse6.4 and a 2.2.14 kernel the disk is not recognized by the system,
so the syystem hangs during the boot sequence.
>From the boot messages:
Uniform Multi-Platform E-IDE driver Revision: 6.30
ide: Assuming 40MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller on PCI bus 00 dev 39
VP_IDE: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xe000-0xe007, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xe008-0xe00f, BIOS settings: hdc:DMA, hdd:DMA
hda: QUANTUM FIREBALL_TM2550A, ATA DISK drive
hdc: Maxtor 33073U4, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
OK here everything seems to be fine. Only the message:
VP_IDE: not 100% native mode: will probe irqs later
make me a little bit "nervous". Should I change ide bus speed
with the kernel parameter idebus=33 ? I think I will try it this evening.
After this I get the messages:
hda: QUANTUM FIREBALL_TM2550A, 2445MB w/76kB Cache, CHS=621/128/63, DMA
hdc: Maxtor 33073U4, 29311MB w/512kB Cache, CHS=59554/16/63, UDMA(33)
For my old Quantum disk this seems to be ok, this means I get the
same values as in the bios. But for the Maxtor disk it seems to be wrong,
because in the bios I have: 3736 cylinders, 255 heads, 63 sectors. 59554
is the value of the landing zone from the bios. It seems to be that here
something is wrong (to my regret at the moment I can't remember the
output of my Debian system).
A little bit later I get, if I get something:
hdc: [PTBL] [1027/255/63] hdc1 hdc2 hdc3 < hdc5 hdc6 >
Mostly I get only:
hdc:
or
hdc: [PTBL] [1027/255/63] hdc1 hdc2 hdc3 <
and the system hangs.
With my Debian system I get the correct values:
hdc: [PTBL] [3736/255/63] hdc1 hdc2 hdc3 < hdc5 hdc6 >
What I've tried:
- I booted the kernel with the parameter hdc=noprobe.
Surely the system booted and I can't access the disk.
- I booted the kernel with the parameter hdc=3736,255,63
The system booted. After this I can mount the partition hdc1 but e.g.
if I execute a ls -l on this partition the system hangs. It also hangs
if I try a cfdisk /dev/hdc. With hdparm I can access the disk.
hdparm -v, hdparm -i, hdparm -I or hdparm -g are working.
Some more remarks:
- The small Quantum disk works. I can access it under
the Suse6.4 system without any problem.
- I don't want to boot from the Maxtor disk. My Linux system is on another
SCSI disk and booted without a problem. It only has problems detecting
the new EIDE disk. At the moment it is "tolerable" because I don't need
the EIDE disk under my Linux system. But it is still a little bit
frustrated because it's possible that I want to access the Wind*
partition which is on this disk from my Linux system or that I need
a free partition from this disk to extend my Linux system. And last but
not least I don't like it if something does not work the usual way.
Any idea concerning this problem ?
Greetings,
Torsten.
------------------------------
From: Guy Maskall <[EMAIL PROTECTED]>
Subject: Re: How to Install a SCSI Card
Date: Tue, 08 Aug 2000 12:50:07 +0100
MH wrote:
> [EMAIL PROTECTED] wrote:
> >
> > I have an adaptec 1542 with a scanner hanging off it. During Boot the
> > SCSI bios lists the scanner but I can't seem to find out how to get the
> > card recognised under RH 6.2. I've tried loading the aha152x from the
> > linux boot prompt but linuxconf still shows no devices. Is there a
> > seperate module that I should be loading ?
> >
> > Sent via Deja.com http://www.deja.com/
> > Before you buy.
>
> You may need to edit /etc/conf.modules. If it doesn't already exist, try
> adding:
>
> aha152x=io_base,IRQ,scsi_id,reconnect,parity
>
> Note: The 1542 is NOT fully compatible, according to RH.
Your *card* is an actual aha1542? You don't want the aha152x driver then.
The driver is aha1542.o
Do you have scsi support modularized? (Have you compiled the kernel yourself
at all?)
Assuming that it's a proper aha1542 and you have support for scsi set up as
modules the line you do want in your /etc/conf.modules is "alias
scsi_hostadapter aha1542".
To access the scanner you will need to have the following modules loaded:
scsi_mod
aha1542
sg
scsi_mod has to be the first to load. If your dependencies are set up
correctly then trying to use the scanner should load sg.o, but the system
will know to load scsi_mod.o (first) as well as aha1542.o
Typing '/sbin/lsmod -a' should show all of these modules loaded. You should
also then be able to do 'cat /proc/scsi/scsi' and see your scanner listed
(assuming you have proc fs support).
You also need at least kernel 2.2.14, but with redhat 6.2 this shouldn't be
an issue.
Regards, Guy.
--
"The Information contained in this e-mail and any
subsequent correspondence is private and is intended
solely for the intended recipient(s). For those
other than the intended recipient any disclosure,
copying, distribution, or any action taken or
omitted to be taken in reliance on such information
is prohibited and may be unlawful."
------------------------------
From: Guy Maskall <[EMAIL PROTECTED]>
Subject: Re: Problems with SCSI card (RH 6.2)
Date: Tue, 08 Aug 2000 12:58:45 +0100
Neil Golstein wrote:
> Not sure if this will help but when I had a scanner on my 1502 card I used
> to initialize the driver with the following command in my rc.local:
> insmod aha152x aha152x=0x140,10,7,1,1,0,500,0
> The only thing you would change would be the first two parameters, being the
> memory address and IRQ respectively, the rest of it I just copied from what
> another poster wrote!
> The 1502 however was an ISA card that you could set these parameters via
> jumpers on the card.
> Since the 1542 is an ISA plug and play device you probably have to run
> isapnp and write an isapnp.conf file first to set the memory address and IRQ
> (out of the available choices). You just have to do this once and it's set.
> If you can override pnp with jumpers though just do that, it's simpler.
>
> <[EMAIL PROTECTED]> wrote in message news:8lh0gb$9ne$[EMAIL PROTECTED]...
> > I have an adaptec 1542 with a scanner hanging off it. During Boot the
> > SCSI bios lists the scanner but I can't seem to find out how to get the
> > card recognised under RH 6.2. I've tried loading the aha152x from the
> > linux boot prompt but linuxconf still shows no devices. Is there a
> > seperate module that I should be loading ?
> >
> >
> > Sent via Deja.com http://www.deja.com/
> > Before you buy.
The 1542 has dip switches, one of them does disable pnp (as I did 'cos my
motherboard isn't pnp). IIRC there's also a dipswitch to disable the internal
floppy connector, which you'll probably want to do as you'll already have a
normal floppy drive.
The aha1542 driver doesn't take those options you mentioned for the aha152x. I
can't recall offhand if it does take any option, certainly only one or two if
it does but it autoprobes the two address (320 and 340 IIRC) so should find the
card on its own.
I replied to an earlier post on this thread with more info that might help.
Guy
------------------------------
** 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
******************************
