Linux-Hardware Digest #871, Volume #9 Mon, 29 Mar 99 22:13:46 EST
Contents:
Re: Hardware RAID-controllers supported under Linux. ([EMAIL PROTECTED])
Re: Creative Labs Banshee AGP 16mb (Conrad B Nelson)
AudiExcel info-check ("Erik")
Re: Q: Fujitsu Dynamo 640SE and Kernel 2.2.3 (Pas Moi)
Re: Kernel 2.2.3 post-compilation problems ([EMAIL PROTECTED])
Re: Yet Another PIC Modem Question (Byron A Jeff)
Re: network is unreachable ("James Washer")
Re: v90 internal modem ("Mortimer, Ian (EXCHANGE:MDN03:4634)")
drivers for dynasonix pro soundcard (Eugene VonNiederhausern)
Re: All the current OSes are idiotic (was Re: Is Windows for idiots?) ("Osvaldo
Pinali Doederlein")
Re: All the current OSes are idiotic (was Re: Is Windows for idiots?) ("Osvaldo
Pinali Doederlein")
----------------------------------------------------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Hardware RAID-controllers supported under Linux.
Date: Tue, 30 Mar 1999 01:16:48 GMT
Hi
The driver will not be found during installation. U need to build the kernel
by applying the patch given in the website. Then only ur Smart 2/p will be
recognised. Follow these steps to build the kernel.
The following steps need to be followed for building a Smart Controller driver
using the PATCH available at
http://www.insync.net/~frantzc/cpqarray.html
a) The SMART-2 patch which is downloaded from the above mentioned web site
needs to patched at /usr/src/linux directory.
b) Before doing SMART-2 patch, First you need to patch Leonard's Zubkoff's
DAC960 patch, which is available at
http://www.dandelion.com/Linux/DAC960.html. This patch adds some important
functionality to the block code in ll_rw_blk.c.
This driver will not work without it.
c) Now first extract the downloaded Leonard's Zubkoff's DAC960 patch by using
tar xvf DAC960-2_0_0-Beta4_tar.gz for
kernel 2.0.36 ( Redhat 5.2) and DAC960-2_2_0-Beta4_tar.gz for kernel 2.1.130
and above. It will extract all the readme
files and DAC960.patch file.
d) Now you patch the DAC960.patch file at /usr/src/linux by using the command
patch -p1 <DAC960.patch
e) Then patch the file smart2-0.9.8p1-for-2.0.patch for kernel 2.0.36 and
smart2-0.9.8p1-for-2.1.patch for kernel 2.1.130
and above .
f) Now execute "make mrproper."
g)Execute "make menuconfig"
There will be a option as Compaq SMART Support which you can e ither select
as built-in (*). Then select the next
sub-options Compaq SMART2 PCI Support and Compaq SMART-2 EISA Support . Which
needs to be selected as built-in
only.
h). Execute make dep to set up all the dependencies correctly. After
completion of make dep, execute make clean. i). Execute either make boot or
make zImage (If zImage gives error such as file too big execute "make
bzImage") j). Once make boot or make zImage is successful then copy the file
from cp /usr/src/linux/arch/i386/boot/zImage /boot/vmlinuz-arr Eg., cp
/usr/src/linux/arch/i386/boot/zImage /boot/vmlinuz-arr k) Execute "insomd
loop" l) Execute make modules m). Execute make modules_install n) Execute
mkinitrd /boot/initrd-arr 2.0.36 o) Now edit /etc/lilo.conf file and include
these following lines after timeout=< > Eg :
image=/boot/vmlinuz-arr
label=linux-arr
initrd=/boot/initrd-arr
root=/dev/sda
read-only
But you need to retain the earlier boot image.
Without fail need to execute the command as "lilo"
p)reboot the system
q) Now change the directory to /usr/src/linux/drivers/block/ where you can
find a file MKDEV.ida whose executable
permission needs to be provided. Now execute the file as ./MKDEV.ida <no of
smart2-controllers>. defaults to 1 if not
specified.
k) Now the inodes for the SMART Controllers will be created at /dev as
/dev/ida/c0d0
/dev/ida/c0d0 Controller 0, disk 0, whole device
/dev/ida/c0d0p1 Controller 0, disk 0, partition 1
/dev/ida/c0d0p2 Controller 0, disk 0, partition 2
/dev/ida/c0d0p3 Controller 0, disk 0, partition 3
/dev/ida/c1d1 Controller 1, disk 1, whole device
/dev/ida/c1d1p1 Controller 1, disk 1, partition 1
/dev/ida/c1d1p2 Controller 1, disk 1, partition 2
/dev/ida/c1d1p3 Controller 1, disk 1, partition 3
If you want to use an EISA controller you'll have to turn on EISA support and
supply some insmod/lilo parameters. If the
driver is compiled into the kernel, must give it port/irq data at boot time.
For example, if you had two SMART-2/E controllers,
in EISA slots 1 and 2, on irqs 15 and 5 respectively you'd give it a boot
argument like this:
smart2=0x1000,0xf,0x2000,0x5
If you were loading the driver as a module ie., Selecting Compaq SMART Support
as Module then , you'd give load it like this:
insmod cpqarray.o eisa=0x1000,0xf,0x2000,0x5
You can use EISA and PCI adapters at the same time.
l) Now reboot the system after doing running lilo.
m) The system should recognize the no of SMART-2 Controllers. Now login to the
system as root and create the filesystem for
the logical disks using mkfs eg., mkfs /dev/ida/c0d0 ( a default file system
will be ext2) which are configured through Array
Configuration utility which is available in SMART-START CD
To make the Smart Controller Bootable follow the steps given below.
Make a filesystem on the disk array (assume /dev/ida/c0d0p1)
# mke2fs /dev/ida/c0d0p1
4. Install the patched utilities (lilo) ( available in the above mentioned
website)
5. Copy the enitre linux installation from your scsi disk to the disk array
# mount /dev/ida/c0d0p1 /mnt
# mkdir /mnt/mnt /mnt/proc
# cd /
# ls | grep -v mnt | grep -v proc > z
# (tar cf - `cat z`) | (cd /mnt; tar xvpf -)
6. Edit the boot config files in /mnt/etc to point to /dev/ida/c0d0p1
instead of /dev/sda1 # vi /mnt/etc/fstab # vi /mnt/etc/lilo.conf 7. Execute
QuickInst from /mnt/usr/src/linux/directory lilo executable file will be
created and also boot.b file will get created. 8. # cp
/mnt/usr/src/linux/lilo/boot.b /boot 9. # cd /mnt/usr/src/linux 10. Run
lilo on the array to install the bootloader # ./lilo -r /mnt 11. Reboot and
run sysconfig and make the array first in the boot order
Regards
In article <7do57q$9ae$[EMAIL PROTECTED]>,
[EMAIL PROTECTED] wrote:
> I'm trying to get the Compaq drivers to work on my 4-way Proliant 5000. The
> drivers (when compiled into the kernel) are not finding the card, and when
> compiled as a module I get undefined symbols.
>
> Has anyone else gotten this to work on the same setup? I have a SmartArray/2P.
>
> Regards,
> -scott anderson
>
> In article <y34L2.43072$[EMAIL PROTECTED]>,
> "Tony" <[EMAIL PROTECTED]> wrote:
> > What about Compaq ????
> >
> > There Raid array controllers are just brilliant and as for there servers
> > (droool Droool)
> >
> > There is a link here for support under linux
> >
> > http://www.insync.net/~frantzc/cpqarray.html
> >
> > tony
> >
> > [EMAIL PROTECTED] wrote in message
> > <7clma1$2g9$[EMAIL PROTECTED]>...
> > >I'm trying to find out which hardware PCI-controllers are supported under
> > >Linux. Can anyone tell me some options for hardware RAID-systems that will
> > >work under Linux?
> > >
> > >Thanks!
> > >
> > >Arjan
> > >
> > >-----------== Posted via Deja News, The Discussion Network ==----------
> > >http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
> >
> >
>
> -----------== Posted via Deja News, The Discussion Network ==----------
> http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
>
============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
From: Conrad B Nelson <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.x,linux.redhat.misc
Subject: Re: Creative Labs Banshee AGP 16mb
Date: Tue, 30 Mar 1999 01:38:27 GMT
This is a multi-part message in MIME format.
==============E6654CC6D474486C0F41DB86
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Steve wrote:
> Newbie here
>
> I just installed RH5.2 on my system. However, I cannot get X to recognize
> my video card. I can start X using the Creative Labe Banshee PCI but the
> resolution is 640x480 with the virtual desktop top set to 800x600.
>
> Other problem, how do i get x to dial into a internet provider?
>
> Any help is appreciated.
>
> SG
Take a look at http://www.uno.edu/~adamico/banshee
Conrad
==============E6654CC6D474486C0F41DB86
Content-Type: text/x-vcard; charset=us-ascii;
name="cnelson.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for Conrad B Nelson
Content-Disposition: attachment;
filename="cnelson.vcf"
begin:vcard
n:Nelson;Conrad
x-mozilla-html:FALSE
org:Cognos Corporation
adr:;;;;;;
version:2.1
email;internet:[EMAIL PROTECTED]
title:Solutions Specialist
x-mozilla-cpt:;0
fn:Conrad Nelson
end:vcard
==============E6654CC6D474486C0F41DB86==
------------------------------
From: "Erik" <[EMAIL PROTECTED]>
Subject: AudiExcel info-check
Date: Tue, 30 Mar 1999 00:15:01 +0200
Hi to all of ya!
I been searching for some info on my AudioExcel AV-530 (FM801 chipset)
soundcard in relation to Linux for several weeks now, but there seems to be
no info at all. I don't think my soundcard is yet supported, but it's weird
that there's no info att all. Does anybody out there know anything or maybe
someone has this card (or card with the same chipset) working on Linux? Any
information is welcom.
Erik Akkermans ([EMAIL PROTECTED])
------------------------------
Subject: Re: Q: Fujitsu Dynamo 640SE and Kernel 2.2.3
From: Pas Moi <[EMAIL PROTECTED]>
Date: Tue, 30 Mar 1999 01:30:48 GMT
>> "m" == mardy113 wrote on Fri, 26 Mar 1999 18:09:58 GMT:
m> In article <7ddhs0$5tf$[EMAIL PROTECTED]>,
m> [EMAIL PROTECTED] (Matthias Meixner) wrote:
>> - The drive can be accessed using kernel 2.2.3
m> I have 2.2.2
>> - I could use the disk without partitioning using ext2 and FAT
>> (remember to use '-b 2048' with mke2fs)
m> No... It doesn't work... That is, it does work, but it only
m> recognizes 1/4 of the sectors of the MO, that is about 150MB. I've
m> tried to full it up and it confirmed it. The thisk has about
m> 300.000 sectors; it reported about 70.000 :-(
>> - using normal fdisk does not work for partitioning - The disk can
>> be partitioned using fdisk from www.erlangen.netsurf.de/linux-
m> mo/
>> (thanks for the hint :-) )
m> Yes, I used that FDISK.
me too. i also had the problem of only 150mb showing up. moreover, i
got lots of errors reading and writing to mo disks. i called fujitsu,
and the guy said it was probably a faulty laser. i exchanged drives,
but the problems continued. i finally put all the little switches in
the off position and stuck an active scsi terminator on the thing. my
problems have disappeared. i'd recommend using the stuff from
www.erlangen.netsurf.de/linux-mo/, and if problems persist, to think
about hardware problems.
good luck,
g.y.
--
Guy Yasko -- [EMAIL PROTECTED]
Uh-oh!! I'm having TOO MUCH FUN!!
------------------------------
From: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
Crossposted-To:
alt.os.linux,aus.computers.linux,comp.os.linux.networking,comp.os.linux.setup
Subject: Re: Kernel 2.2.3 post-compilation problems
Date: Tue, 30 Mar 1999 01:44:14 GMT
Aaron Saikovski wrote:
> Ok here's my problem...
> I have compiled my kernel using bzImage
> moved the bzimage to /boot/zImage
> done the make modules and make modules_install
> edited my /etc/lilo.conf and ran lilo to update the boot loader
> Now when I reboot and press tab I don't get the new entry that I put into
> lilo.conf
> when I login as root and try rerunning lilo it adds the new kernel entry to
> lilo and then I reboot.
>
> All is pretty straight forward thus far
>
> now when lilo comes up it looks like the following
> "LI-"
> LILO doesn't even come up!!
>
> and thats it, the machine freezes and game over.
>
> Also I got the message the other day "Not enough input data" when it started
> to uncompress the kernel on boot.
>
> What do I do now short of fdisking the machine and putting NT workstation
> back on?
> I love linux and think that KDE is the bees knees!
>
> Thanks,
> Aaron Saikovski
> email: [EMAIL PROTECTED]
You need to give us more information, like the content of /etc/lilo.conf.
You definetely don't need to fdsik your system. If you have redhat installed,
you can use their boot disk to boot the computer. Insert the boot disk in, and
when you get to the ifisrt prompt, choose rescue. From there insert the resque
disk in and tyep rescue root=/dev/partition_with_linux (e.g. /dev/hda1). This
will boot you into linux and you can tango with lilo from there.
-- Nadeem
------------------------------
From: [EMAIL PROTECTED] (Byron A Jeff)
Subject: Re: Yet Another PIC Modem Question
Date: 29 Mar 1999 09:20:54 -0500
In article <OtmL2.137$04.217@stones>,
nicholas butler <[EMAIL PROTECTED]> wrote:
-Ok so lets review, I just spent and Hour reviewing messages posted to this
-and other conferences that go something like
- person 1 : I have PCI Modem
- person 2: Oh its Winmodem , your screwed....
- person 1: Yes but how can I try to configure it
- person 2: Oh its Winmodem , your screwed....
- person 1:Ok heres the speck
- person 2: Oh its Winmodem , your screwed....
- person 1: Funny but its not listed at the usual sites, maybe its
-difference
- person 2: Oh its Winmodem , your screwed....
- person 1: Look how do I set up PCI/DEVICES etc ...
- person 2: Oh its Winmodem , your screwed....
- and so it goes on..
-
-Here is a thought. My PCI Modem is a
- PRO MEDIA Internal ITU-T (previously CCITT) V.90 Spec
- FM-56RI
-
-
- No mention of HCP or HSP
-
- Plenty of mention Lucent Technologies.
-
-
- So all that is left is ....
-
- How the hell does any one irrespective of ***modem, validate and
-configure the PCI devices in order to attempt to configure the modem.
-
- Dont tell me it cant be done.
-
- Ive got a Ditto Max (PNP) accelerattor card, AWE 64 and Diamond Stealth
-3d Card all in here and working just fine in my RH systems, hell I can even
-get Ftape working so I an darned if someone is gonna
- person 2: Oh its Winmodem , your screwed....
- me as a response.
-
- Your chance , lets get definitive here please?
OK let's. I'm presuming you have Some version of Windows and the modem works
under it.
0) Download a DOS modem program. An old Procomm will do fine. You can find
these at the DOS archive at oak.oakland.edu.
1) Reboot your machine. Get the windows boot menu by pressing F8 for Win95
or CTRL for 98 just before the splash screen comes up.
2) Choose Safe mode command prompt. This will boot DOS only and load no
drivers.
3) Run your modem program. Attempt to send ATDT commands to where the modem
is supposed to be.
If the modem picks up then congratulations! You can a PCI modem that isn't a
Winmodem. Treat it in Linux just like any other modem.
However there is only one known modem from MultiTech that fits this profile.
All the rest are Winmodems, which have no drivers in DOS, Linux, Mac, NT, or
anything else other than Win95 and Win98.
In short "Oh it's probably a Winmodem. You're screwed..."
BAJ
-
-
-
------------------------------
From: "James Washer" <[EMAIL PROTECTED]>
Subject: Re: network is unreachable
Date: Mon, 29 Mar 1999 15:29:40 +0100
If you are saying that when you go to another computer, and try to ping your
linux-system, and the response is 'network unreachable', then that mean the
the other computer does not have a route to your linux-system.. What are the
IP addresses of your linux-system and the other computer? Are they on the
same net? etc etc
- jim
Jim Kingdon wrote in message ...
>> But when i try to ping or try to access my linux-system from somewhere
>> else on the network it says: network is unreachable.
>
>Try "ifconfig" on the linux system; you should see eth0 or something
>like that. I'm guessing you won't. Then you need to go back to the
>scripts which run at boot time and see what errors they got (I think;
>I'm not sure I ever did track down the similar problem which happened
>to me when I upgraded to Red Hat 5.1 (from 5.0 or 4.x, I forget
>which)).
------------------------------
From: "Mortimer, Ian (EXCHANGE:MDN03:4634)" <[EMAIL PROTECTED]>
Subject: Re: v90 internal modem
Date: Mon, 29 Mar 1999 15:06:20 +0100
I have just been nosing around www.searchlinux.com for info about this problem
and it seems that there may be an IRQ conlict.
You have to use the SETSERIAL program to alter this.
Rgds,
Ian.
Olle Soderqvist wrote:
> Hi!
>
> I have a Rockwell internal v90 modem and I have the problem that I have seen
> that a whole bounce of other also have!
> Linux can find my modem on COM3 but everything takes a very, very long
> time....for exampel writing the letters ATDT takes 20 seconds before they
> appear on the screen! And everything goes so damn slow! So does anyone know
> it that's because I have a winmodem or is this problem fixeble??
>
> Please help me!
>
> Regards, Olle
------------------------------
From: Eugene VonNiederhausern <[EMAIL PROTECTED]>
Crossposted-To: linux.dev.sound,comp.os.linux.setup
Subject: drivers for dynasonix pro soundcard
Date: Mon, 29 Mar 1999 20:32:51 -0600
Are there any linux drivers for the Dynasonix pro soundcard by core
dynamics?
------------------------------
From: "Osvaldo Pinali Doederlein" <[EMAIL PROTECTED]>
Crossposted-To:
comp.lang.java.advocacy,comp.os.linux.advocacy,comp.os.ms-windows.advocacy
Subject: Re: All the current OSes are idiotic (was Re: Is Windows for idiots?)
Date: Mon, 29 Mar 1999 23:54:14 +0200
jedi <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> >That is an excellent way to fix bugs, but it is totally unable to fix
poor
> >initial design decisions. What happens on Linux when you type 'rm * .tmp'
> >instead of 'rm *.tmp'? Just the same as on any Unix system for the last
20
> >years. Why hasn't it been fixed? Because it would break old programs.
> >It simply isn't possible to design a 21st Century operating system that
is
> >backwards compatible with a 1980 OS.
> Then write a new utility named foo or rewrite rm to exhibit
> your notion of 'the one true interface'. Unix has less such
> problems as it is nearly completely modular.
The problem is not rm's, it's a fundamental problem of the CLI because the
shell, not the rm program, will expand the wildcards. The right thing to do
is having the tool to expand the wildcards when appropriate. You could
stuff the expansion functionality in a shared lib so the developer has the
same convenience of not having to write it. And the developer would have a
change to check for suspicious parameters before the expansion.
------------------------------
From: "Osvaldo Pinali Doederlein" <[EMAIL PROTECTED]>
Crossposted-To:
comp.lang.java.advocacy,comp.os.linux.advocacy,comp.os.ms-windows.advocacy
Subject: Re: All the current OSes are idiotic (was Re: Is Windows for idiots?)
Date: Mon, 29 Mar 1999 23:58:08 +0200
Terry Sikes <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> >That is an excellent way to fix bugs, but it is totally unable to fix
poor
> >initial design decisions. What happens on Linux when you type 'rm * .tmp'
> >instead of 'rm *.tmp'? Just the same as on any Unix system for the last
20
> >years. Why hasn't it been fixed? Because it would break old programs.
> You're confusing user-level programs like rm with operating system
> functionality.
We can find examples of bad design in the core OS functionality quite
easily. Should I mention "multithreading support"? :)
------------------------------
** 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
******************************
