Linux-Hardware Digest #401, Volume #14 Sun, 25 Feb 01 19:13:08 EST
Contents:
Re: Conexant HCF Modem Driver? (Uwe Bonnes)
Re: what kind of motherborad is this? (reader of news)
Re: difficulty mounting ATAPI zip (Dances With Crows)
Re: SB live, *has* to be module? ("D. Stimits")
ALSA & Intel 8x0 sound card: Error... (Dan Smith)
Re: Linux partitioning question (Tim Moore)
Re: Best RAID controller for Linux (Juergen Sauer)
Re: Hewlett-Packard CD-Writer Plus 9300, which is an IDE device, and (Michael
Fischer)
Trident 9850 AGP (Minaxi Kapadia)
Re: Linux partitioning question (Eric P. McCoy)
Re: Linux partitioning question (Rod Smith)
----------------------------------------------------------------------------
From: Uwe Bonnes <[EMAIL PROTECTED]>
Subject: Re: Conexant HCF Modem Driver?
Date: 25 Feb 2001 21:56:13 GMT
Rinaldo Bergamini <[EMAIL PROTECTED]> wrote:
: I'm trying to configure a winmodem under Mandrake 7.2 . The card is a PCI
: Conexant (ex Rockwell) soft56k HSF modem. Some people report that with
: the "driver" (Kernel module) provided by Olitech
: (http://www.olitec.com/pub/PCI_56K_V2_K2.2.17.tar.gz) and kernel
: 2.2.17 the modem works fine, so I downloaded this tarball, expanded
: it under the root dir, get into the cerated dir and launched
: ./ins_all. An error occurred: unable to open "lin_hsf.inf" but this
: file is in the directory, what should I do?
: In the dir there is an executable called "inf2bin". I launched it
: with the requested parameters (inf2bin lin_hsf.inf lin_hsf.bin)
: but another error occurred saying that my country and the one of
: the file anren't equal.
Those failures sound strange.
Scrap the first download. Fetch the file again. Run ./ins_all as root.
Bye
--
Uwe Bonnes [EMAIL PROTECTED]
Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
========= Tel. 06151 162516 ======== Fax. 06151 164321 ==========
------------------------------
From: [EMAIL PROTECTED] (reader of news)
Subject: Re: what kind of motherborad is this?
Reply-To: [EMAIL PROTECTED]
Date: 25 Feb 2001 17:01:43 -0500
Thanks for the suggestion.. Would you
mind sharing what your /sbin/hdparm -Tt looks
like?
On Sun, 25 Feb 2001 21:29:00 GMT,
Tim Moore <[EMAIL PROTECTED]> wrote:
>> Anyway I like to juice as much as
>> possible out of my server... I
>> have now 2.4.2 on the server and
>> it has an quantum ide drive. /sbin/hdparm
>
>> VIA82CXXX chipset support (CONFIG_BLK_DEV_VIA82CXXX) [N/y/?]
> ^
>Change this to 'Y'. Also try passing kernal parameter at boot time,
>usually in /etc/lilo.conf: append="ide0=ata66". Your dmesg output
>should look something like this:
>...
>ide: Assuming 33MHz system bus speed for PIO modes
>VP_IDE: IDE controller on PCI bus 00 dev 39
>VP_IDE: chipset revision 16
>VP_IDE: not 100% native mode: will probe irqs later
>VT 8371
> Chipset Core ATA-66
>VP_IDE: ATA-66/100 forced bit set (WARNING)!!
>Split FIFO Configuration: 8 Primary buffers, threshold = 1/2
> 8 Second. buffers, threshold = 1/2
> ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:DMA, hdb:DMA
>ide0: VIA Bus-Master (U)DMA Timing Config Success
>VP_IDE: ATA-66/100 forced bit set (WARNING)!!
> ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:DMA, hdd:DMA
>ide1: VIA Bus-Master (U)DMA Timing Config Success
>hda: IBM-DTLA-307020, ATA DISK drive
>hdb: YAMAHA CRW4416E, ATAPI CDROM drive
>hdc: IBM-DTLA-307020, ATA DISK 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-DTLA-307020, 19623MB w/1916kB Cache, CHS=2501/255/63, UDMA(66)
>hdc: IBM-DTLA-307020, 19623MB w/1916kB Cache, CHS=39870/16/63, UDMA(66)
>...
>--
>timothymoore
> bigfoot
> com
------------------------------
From: [EMAIL PROTECTED] (Dances With Crows)
Subject: Re: difficulty mounting ATAPI zip
Date: 25 Feb 2001 22:04:17 GMT
Reply-To: [EMAIL PROTECTED]
On Sun, 25 Feb 2001 19:30:07 -0000, mougs staggered into the Black Sun
and said:
>I've had no luck mounting my Zip100 under RH6 with kernel 2.2.14-5.0.
>At start up it says that my Iomega Zip is linked to /dev/hdd.
>
>mount -t vfat /dev/hdd /zip
>mount: wrong fs type, bad option, bad superblock on /dev/hdd,
> or too many mounted file systems
>I've tried this with couple of PC100 disks with no success. I've read
>all the how-to's and can't get beyond this point.
You didn't read the HOWTOs carefully enough--they all mention that ZIP
disks that are formatted with FAT filesystems are partitioned, and that
the partition most commonly used is #4. So the command you want is
mount -t vfat /dev/hdd4 /zip
In contrast, if you have a MacOS ZIP disk, the command would be:
mount -t hfs /dev/hdd /maczip
or something similar.
This partitioning is a bit confusing, contrary to the normal method of
using removable media, and such, but it's the way ZIPs work under 'Doze.
You can, of course, make an unpartitioned ZIP with a FAT16 filesystem on
it, but no 'Doze box will be able to read it, making it useless for data
exchange. HTH,
--
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin / Workin' in a code mine, hittin' Ctrl-Alt
http://www.brainbench.com / Workin' in a code mine, whoops!
=============================/ I hit a seg fault....
------------------------------
Date: Sun, 25 Feb 2001 15:19:49 -0700
From: "D. Stimits" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Re: SB live, *has* to be module?
win wrote:
>
> Hi,
>
> I compiled a new kernel with the SBlive support, emu10k1, compiled
> into it.
> I do get the messages that it's found on boot..
> Creative EMU10K1 PCI Audio Driver, version 0.6, 21:37:35 Sep 4 2000
> emu10k1: EMU10K1 rev 5 model 0x8040 found, IO at 0xb400-0xb41f, IRQ 11
> But i can't get it to work...as in..i don't get any sound..
> What am i missing here?
>
> Been doing some reading on the net and see a lot of SBlive installing
> as module.
> Does it only work when it's a module?
>
> running debian with 2.2.18pre21 kernel...
>
> Thanx and cheers
> Wim
I believe it was intended to only be a module, though that might have
changed. Go to
http://opensource.creative.com
Get the most recent emu10k1 snapshot, or use cvs. Unpack it somewhere
temporarily, and view the docs that come with it. I suspect those docs
are more accurate than the make config option to compile as a
non-module. In the past it could not be compiled in, but I haven't paid
attention to this detail in a while, it may be possible to compile in
with the 2.4.x kernels, but it is unlikely to succeed on a 2.2.x kernel.
------------------------------
From: Dan Smith <[EMAIL PROTECTED]>
Subject: ALSA & Intel 8x0 sound card: Error...
Date: 25 Feb 2001 17:14:19 -0500
Everything seems to be setup correctly. All the modules insert fine. Here is my
lsmod after "modprobe snd-card-intel8x0":
Module Size Used by
snd-card-intel8x0 2028 0 (unused)
snd-intel8x0 6480 0 [snd-card-intel8x0]
snd-ac97-codec 24960 0 [snd-intel8x0]
snd-mixer 24912 0 [snd-ac97-codec]
snd-pcm 32184 0 [snd-intel8x0]
snd-timer 9248 0 [snd-pcm]
snd 37932 1 [snd-card-intel8x0 snd-intel8x0 snd-ac97-codec
snd-mixer snd-pcm snd-timer]
sound 60248 0 (autoclean) (unused)
soundlow 336 0 (autoclean) [sound]
soundcore 2916 3 (autoclean) [snd sound]
Is that correct?
Anyway, when I try 'aplay something.wav' I get this error:
Aplay: version 0.4.1 by Jaroslav Kysela <[EMAIL PROTECTED]>
Error: audio open error: Sound protocol isn't compatible
Can someone help me???
Thanks!
--Dan
------------------------------
From: Tim Moore <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup,comp.os.linux.misc
Subject: Re: Linux partitioning question
Date: Sun, 25 Feb 2001 22:31:25 GMT
Minimum traditional place to start for 6GB drive, in this order:
/ 50MB }
/usr 2500MB } primary partitions
swap 250MB }
extended partition here
/var 100MB }
/tmp 250MB } logical partitions
/home 1000MB }
/big (rest) }
/ (root) contains critical directories like /lib /etc /bin /boot. Don't
skimp. Remember the outside 1/3 of the disk (smaller cylinder numbers)
is almost 50% faster than the inside 1/3. swap is after /usr to reduce
head travel. You can always carve up /big later using fdisk. Also you
could do a minimal:
/ 50MB }
/usr 3500MB } primary partitions
swap 250MB }
/home (rest) }
where things like /var /tmp and /opt all end up in the /usr partition.
This is ok but you only get 4 primary partitions just like DOS.
Here's my partition table which dual boots W95. Note /dev/hda11 is not
used for anything at the moment. If the old W95 wasn't there, swap
would be after /usr.
# fdisk -l /dev/hda
Disk /dev/hda: 255 heads, 63 sectors, 2501 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 62 497983+ 6 FAT16
/dev/hda2 * 63 68 48195 83 Linux
/dev/hda3 69 100 257040 82 Linux swap
/dev/hda4 101 2491 19205707+ 5 Extended
/dev/hda5 101 483 3076416 83 Linux
/dev/hda6 484 499 128488+ 83 Linux
/dev/hda7 500 565 530113+ 83 Linux
/dev/hda8 566 820 2048256 83 Linux
/dev/hda9 821 922 819283+ 6 FAT16
/dev/hda10 923 1305 3076416 83 Linux
/dev/hda11 1306 2491 9526513+ 83 Linux
# df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/hda2 46636 38377 5851 87% /
/dev/hda5 3027852 1401390 1626462 46% /usr
/dev/hda6 124427 23013 94990 20% /var
/dev/hda7 521748 696 494548 0% /tmp
/dev/hda8 2015964 906674 1109290 45% /home
/dev/hda10 3028080 1485700 1542380 49% /kits
Gregg Black wrote:
>
> I'm reading up on setting up linux, and it states that many will setup
> separate partitions for /usr and /home besides ones swap space. I would
> like to ask you how you usually setup your partitioning. I was a little bit
> confused on it, for you at least need a mounting point of root. This is how
> I did it, but I'm not sure if it's how it should be done. I set one
> partition for about 3/4 of the drive as '/'. I thought that would cover my
> separate partition for /usr as well as the mount point. My second partition
> and about 1/4 of the drive (not all, as the last is for swap) I set as mount
> point /home. Then of course the remaining 256 megs I set for swap.
>
> At first I was going to create a 7 meg partition just for mounting root,
> then the larger 3/4 approx for /usr, and then the last primary for /home but
> I thought it just made more sense to make just a / and /home partition.
> Maybe I'm just not thinking about this correctly. Any suggestions would be
> appreciated!
>
> I'm running Mandrake 7.2
--
timothymoore
bigfoot
com
------------------------------
From: Juergen Sauer <[EMAIL PROTECTED]>
Crossposted-To: linux.dev.raid
Subject: Re: Best RAID controller for Linux
Date: 25 Feb 2001 21:18:29 GMT
K. Nung <[EMAIL PROTECTED]> schrieb
am 25 Feb 2001 08:50:05 GMT in comp.os.linux.hardware:
> In <sXdi6.73438$[EMAIL PROTECTED]> [EMAIL PROTECTED] (Pros
> torage) writes:
> Really? I spent 1 hour now at Adaptecs web site and didn't find a
> driver for the 3200S for Linux kernel 2.4.2... Are you sure that
> they have one besides their old RedHat 6.X and SuSe 6.X/7.0?
We do server manufacturing.
We use icp-vortex SCSI (Raid x) controllers with great success,
ICP supports completely linux directly by manufacturer, including
waranty and all drivers, utilities ...
There is no wish open ... Great thing.
http://www.icp-vortex.com
ICP-Vortex Compared to mylex, adaptec et.al, they can't reach vortex.
We sold Servers >4 Terabyte ...
mfG
Jojo
--
J�rgen Sauer - AutomatiX GmbH, +49-4209-4699, [EMAIL PROTECTED]
http://www.automatix.de to Mail me: remove: -not-for-spawm-
------------------------------
From: [EMAIL PROTECTED] (Michael Fischer)
Subject: Re: Hewlett-Packard CD-Writer Plus 9300, which is an IDE device, and
Date: 25 Feb 2001 22:50:53 GMT
Reply-To: [EMAIL PROTECTED] (Michael Fischer)
I got the CD-Writer in my HP Pavilion 9680C working some time ago.
Basically I followed the directions in CD-Writing-HOWTO. I rebuilt
the kernel, changing the standard options from the RedHat 6.2
distribution of the 2.2.16 kernel as follows:
85c85
< CONFIG_BLK_DEV_IDECD=y
---
> CONFIG_BLK_DEV_IDECD=m
203c203
< CONFIG_BLK_DEV_SD=y
---
> CONFIG_BLK_DEV_SD=m
205c205
< CONFIG_BLK_DEV_SR=y
---
> CONFIG_BLK_DEV_SR=m
I then added the following lines to my /etc/conf.modules file (now called
/etc/modules.conf in more recent linux distributions):
# Added for CD-RW support
options ide-cd ignore=hdc # tell the ide-cd module to ignore hdc
alias scd0 sr_mod # load sr_mod upon access of scd0
below sg ide-scsi # load ide-scsi before sg
below sr_mod ide-scsi # load ide-scsi before sr_mod
below ide-scsi ide-cd # load ide-cd before ide-scsi
I also put the following lines in my /etc/lilo.conf file:
image=/boot/vmlinuz-2.2.16
label=linux
read-only
root=/dev/hda2
append="hdc=ide-scsi ide0=dma"
Voila, it works! I don't pretend to understand any more what all this
stuff does (or even that I ever did understand it). There may be much
simpler ways of getting it to work. (If so, I'd like to know about
them!) But it should give you a checklist of things to consider.
Here's a little more data on my configuration:
# cdrecord -scanbus
Cdrecord 1.8 (i686-pc-linux-gnu) Copyright (C) 1995-2000 J�rg Schilling
Using libscg version 'schily-0.1'
scsibus0:
0,0,0 0) 'LG ' 'CD-RW CED-8083B ' '1.09' Removable CD-ROM
0,1,0 1) *
0,2,0 2) *
0,3,0 3) *
0,4,0 4) *
0,5,0 5) *
0,6,0 6) *
0,7,0 7) *
# /sbin/lsmod
Module Size Used by
sg 15712 0 (autoclean)
ide-cd 23968 0 (autoclean)
riptide 42784 1
audiobuf 10304 1 [riptide]
opl3 13360 1 [riptide]
uart401 6832 1 [riptide]
midi 26000 1 [opl3 uart401]
soundbase 307968 1 [riptide audiobuf opl3 uart401 midi]
sndshield 4928 0 [riptide audiobuf opl3 uart401 midi soundbase]
sr_mod 16160 1 (autoclean)
ide-scsi 7344 1 (autoclean)
cdrom 27520 0 (autoclean) [ide-cd sr_mod]
ip_masq_ftp 2656 0 (unused)
nfs 28736 1 (autoclean)
ipip 5136 1 (autoclean)
nfsd 143856 8 (autoclean)
lockd 31216 1 (autoclean) [nfs nfsd]
sunrpc 52976 1 (autoclean) [nfs nfsd lockd]
ppp 20240 2 (autoclean)
slhc 4544 1 (autoclean) [ppp]
rtl8139 12416 1 (autoclean)
==================================================
| Michael Fischer <[EMAIL PROTECTED]> |
| Professor of Computer Science |
==================================================
------------------------------
From: Minaxi Kapadia <[EMAIL PROTECTED]>
Subject: Trident 9850 AGP
Date: Sun, 25 Feb 2001 23:30:07 -0000
I have Trident 9850 AGP in my computer.
I am using Simply Accounting Version 7
When I am exiting from simply accounting it comes with
an error message as - File proteccion error in windows sgiul98.drv
Can u guide me how to solve this problem?
--
Posted via CNET Help.com
http://www.help.com/
------------------------------
Crossposted-To: comp.os.linux.setup,comp.os.linux.misc
Subject: Re: Linux partitioning question
From: [EMAIL PROTECTED] (Eric P. McCoy)
Date: 25 Feb 2001 18:40:49 -0500
"Gregg Black" <[EMAIL PROTECTED]> writes:
> I'm reading up on setting up linux, and it states that many will setup
> separate partitions for /usr and /home besides ones swap space. I would
> like to ask you how you usually setup your partitioning.
Right now I use just three partitions: /boot, root, and swap. This is
not really a good solution.
The /boot partition is a RAID1 (mirrored) array. That makes it useful
as a "failproof" device so I can boot my system even if something goes
wrong. I should thus probably have /bin and /sbin on there and use
that as my root directory.
> I was a little bit confused on it, for you at least need a mounting
> point of root. This is how I did it, but I'm not sure if it's how
> it should be done. I set one partition for about 3/4 of the drive
> as '/'. I thought that would cover my separate partition for /usr
> as well as the mount point. My second partition and about 1/4 of
> the drive (not all, as the last is for swap) I set as mount point
> /home. Then of course the remaining 256 megs I set for swap.
That's basically what I did.
> At first I was going to create a 7 meg partition just for mounting root,
> then the larger 3/4 approx for /usr, and then the last primary for /home but
> I thought it just made more sense to make just a / and /home partition.
Sometimes it does. But if you know what size /usr is going to be, you
might be able to fill it up on installation and then mount it
readonly.
/tmp is also a good target for another partition. This will keep
malicious users from filling up your root filesystem and making the
system unusuable by anyone except root.
For a single-user box, I don't think there's a significant advantage
to having many partitions if you have a big enough disk - now that
LILO can boot from most anywhere on the disk on modern systems.
--
Eric McCoy <[EMAIL PROTECTED]>
"Knowing that a lot of people across the world with Geocities sites
absolutely despise me is about the only thing that can add a positive
spin to this situation." - Something Awful, 1/11/2001
------------------------------
From: [EMAIL PROTECTED] (Rod Smith)
Crossposted-To: comp.os.linux.setup,comp.os.linux.misc
Subject: Re: Linux partitioning question
Date: Sun, 25 Feb 2001 23:50:15 -0000
Reply-To: [EMAIL PROTECTED]
[Posted and mailed]
In article <97bpqn$e0o$[EMAIL PROTECTED]>,
"Gregg Black" <[EMAIL PROTECTED]> writes:
> I'm reading up on setting up linux, and it states that many will setup
> separate partitions for /usr and /home besides ones swap space. I would
> like to ask you how you usually setup your partitioning. I was a little bit
> confused on it, for you at least need a mounting point of root.
...
> Maybe I'm just not thinking about this correctly. Any suggestions would be
> appreciated!
There is no single correct way to do it. There are pros and cons to just
about any partitioning scheme you can think of. For newbies, I generally
recommend a fairly minimal approach: root (/) and swap, with an optional
split of /home and, on some systems, a separate /boot partition to keep
the kernel below the 1024-cylinder mark. This last is increasingly
unnecessary as distributions include GRUB or versions of LILO that can
boot from beyond the 1024-cylinder mark. The main advantage of the
separate /home partition is that it makes it easier to do a clean 100%
reinstall without mucking up the user files.
The drawback to creating multiple partitions is that it's hard to
predict how large to make them. This is true of experienced users, but
it's especially true for new users, who really have no idea how big
these things should be. It's also something for which somebody else's
experience is useless. For instance, somebody with lots of experience
administering major mail servers will likely want a big separate /var
partition; but the average home system needs very little space devoted
to /var. /home at least, as the storage space for user files, is
something the size of which new users have some chance of estimating. If
you guess wrong, you've got to juggle data around, repartition, or
dynamically resize a partition.
Splitting off multiple partitions has several advantages, such as a
reduced chance of problems should a runaway process create a too-large
file and a reduced chance losing all your data in case of a filesystem
problem. IMHO, these are all dwarfed for new users by the near certainty
of getting partition sizes wrong, but those who know how big to make
their partitions may prefer to split things up.
--
Rod Smith, [EMAIL PROTECTED]
http://www.rodsbooks.com
Author of books on Linux & multi-OS configuration
------------------------------
** 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 by posting to comp.os.linux.hardware.
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
******************************
