Linux-Hardware Digest #653, Volume #14 Thu, 19 Apr 01 23:13:03 EDT
Contents:
Re: No logitech mouse works with any distribution of linux... (Juergen Pfann)
Sound SCSI conflict? ([EMAIL PROTECTED])
Re: GA-7ZX Onboard Sound Problem (chronos)
Re: mandrake and the iomega zip100 (parallel) (Static)
Re: Sound Blaster 16 PCI\Ensoniq 5880 (Dances With Crows)
Re: LS120 (Dances With Crows)
Re: linux and cray j90 (Martha H Adams)
Re: ATI Xpert 2000 Pro Problem (Static)
Re: Sending voice to a modem (Static)
Re: question about modules (Static)
Re: Sound Blaster 16 PCI\Ensoniq 5880 (Static)
Re: remount HD rw (Static)
Re: Partitioning problem (Static)
----------------------------------------------------------------------------
From: Juergen Pfann <[EMAIL PROTECTED]>
Subject: Re: No logitech mouse works with any distribution of linux...
Date: Fri, 20 Apr 2001 03:09:26 +0200
iQXth wrote:
>
> ...or do they?
>
Yes, they do, and they do fine... - I just can't resist to reply
to such a general statement like in your subject.
But to be precisely, my own experience is restricted to serial
"MouseMen" and "Pilots" - never had any problems with these in any
OS, so I'll stick to these somewhat longer.
I personally don't see any need for 10-button, 5-wheel, infrared, USB
mice and such stuff - serial i/f and 3 "normal" buttons just do
their job. Especially, I don't understand the wheel hype - IMHO that's
more disadvantage than advantage; but any1 as he likes to.
Juergen
------------------------------
From: [EMAIL PROTECTED]
Subject: Sound SCSI conflict?
Date: 19 Apr 2001 18:13:07 PDT
I am trying to configure sound on my machine. I run sndconfig, startx to start
Gnome, then pop a CD in and run XMMS or whatever
At that point the music plays for a few minutes and then starts slowing down.
Then things start going wrong like I cannot open up a terminal window. Before
long everything stops working and I have to reboot.
I think what is happening is some sort of interrupt conflict with the SCSI.
Any thoughts on how to solve this problem? Thanks.
Here is lspci output:
00:00.0 Host bridge: VIA Technologies, Inc. VT82C691 [Apollo PRO] (rev c4)
00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598 [Apollo MVP3 AGP]
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C596 ISA [Apollo PRO] (rev 23)
00:07.1 IDE interface: VIA Technologies, Inc. VT82C586 IDE [Apollo] (rev 10)
00:07.2 USB Controller: VIA Technologies, Inc. VT82C586B USB (rev 11)
00:07.3 Host bridge: VIA Technologies, Inc.: Unknown device 3050 (rev 30)
00:0e.0 Multimedia audio controller: Ensoniq ES1371 [AudioPCI-97] (rev 08)
00:10.0 Ethernet controller: Lite-On Communications Inc LNE100TX (rev 20)
00:11.0 SCSI storage controller: Adaptec 7892A (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation Vanta [NV6] (rev 15)
Here is what /proc/interrupts looks like:
CPU0
0: 46935 XT-PIC timer
1: 1304 XT-PIC keyboard
2: 0 XT-PIC cascade
5: 21890 XT-PIC aic7xxx
8: 1 XT-PIC rtc
9: 0 XT-PIC es1371
10: 0 XT-PIC usb-uhci
11: 1024 XT-PIC eth0
12: 1255 XT-PIC PS/2 Mouse
13: 1 XT-PIC fpu
15: 2 XT-PIC ide1
NMI: 0
--
Manatee
------------------------------
From: chronos <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: GA-7ZX Onboard Sound Problem
Date: Thu, 19 Apr 2001 20:11:43 -0500
ET1Mac wrote:
>
> I'm using RH6.2 and have installed it on a GA-7ZX with a Duron 800.
>
> When configuring sound with sndconfig it autodetects Ensoniq:CT5880. But
> when it goes to play the sample sound the system locks up.
>
> /etc/conf.modules has the following inserted: alias sound-slot-0 es1371
>
> Reading other post with similar issues I changed it to the following: alias
> char-major-14 es1371 with no success.
>
> I even tried modprobe with different arguments; es1371, char-major-14
> es1371, es1370 just to see what will happen, but still no success.
>
> Is this a 6.2 issue, would upgrading fix it?
Think I may have been the author of at least one of the other posts on
this particular subject. ;-)
I've had enough trouble with it. I've got almost the same system, except
it's a 700 instead of an 800. I do know that sound is possible on the
system in Linux. I've been able to get excellent sound with the trial
OSS from ForeFront, and I built the latest ALSA system and installed it
today with a 2.2.19 kernel, and have excellent sound in all my systems
to include the KwinTV with my Hauppage bttv card.
The trick to getting it going with ALSA was to do everything seemingly
in contravention to what I've been told and taught lately about
compiling and linking /usr/src/linux to the new kernel, leaving all
modules out of the new kernel build, and only including sound support
and building alsa-driver-0.5.10b and configuring with the:
./configure --with-sequencer=yes --with-isapnp=yes --with-debug=full
You will wind up with the alsa driver for snd-card-ens1371 and the
following if you do all correctly, and sound will work on the damn
thing. ;-)
Module Size Used by
snd-pcm-oss 16432 0 (autoclean)
snd-pcm-plugin 14088 0 (autoclean) [snd-pcm-oss]
ppp 19980 2 (autoclean)
slhc 4324 1 (autoclean) [ppp]
bttv 33240 1
videodev 2400 3 [bttv]
tuner 1996 1
i2c 3264 2 [bttv tuner]
snd-mixer-oss 3924 1 (autoclean) [snd-pcm-oss]
snd-card-ens1371 1964 1 (autoclean)
snd-ens1371 9164 0 (autoclean) [snd-card-ens1371]
snd-pcm 28952 0 (autoclean) [snd-pcm-oss snd-pcm-plugin snd-ens1371]
snd-timer 7648 0 (autoclean) [snd-pcm]
snd-rawmidi 9048 0 (autoclean) [snd-ens1371]
snd-seq-device 3404 0 (autoclean) [snd-rawmidi]
snd-ac97-codec 24000 0 (autoclean) [snd-ens1371]
snd-mixer 23088 0 (autoclean) [snd-mixer-oss snd-ens1371 snd-ac97-codec]
snd 34700 1 [snd-pcm-oss snd-pcm-plugin snd-mixer-oss snd-card-ens1371
snd-ens1371
snd-pcm snd-timer snd-rawmidi snd-seq-device snd-ac97-codec snd-mixer]
nls_cp437 3676 4 (autoclean)
vfat 9412 2 (autoclean)
fat 30784 2 (autoclean) [vfat]
soundcore 2372 5 (autoclean) [snd]
Okay....Now back to trying to get some native Linux drivers to work. ;-)
Charlie
------------------------------
From: Static <[EMAIL PROTECTED]>
Subject: Re: mandrake and the iomega zip100 (parallel)
Date: Fri, 20 Apr 2001 01:24:48 GMT
Snowman wrote:
> I do actually, it's in the subject line. the zip how-to is what I
> followed
> to get the drive up and going initially. it worked great. until I
> rebooted the box and kudzu forgot where my drives were.
[snip]
Nothing against the guys at Mandrake, I'm playing with 8.0 and liking it so
far, but kudzu is one thing that I take out of the init - its plagued me a
few times in the past, and I found the easiest way around the issues were
to simply remove the symlinks to it in the /etc/rc.d tree.
St.
------------------------------
From: [EMAIL PROTECTED] (Dances With Crows)
Subject: Re: Sound Blaster 16 PCI\Ensoniq 5880
Reply-To: [EMAIL PROTECTED]
Date: 20 Apr 2001 01:38:05 GMT
On Thu, 19 Apr 2001 02:46:57 GMT, Chris staggered into the Black Sun and
said:
>[root@SMOKEY cbruton]# /sbin/modprobe es1371
>/lib/modules/2.4.2/kernel/drivers/sound/es1371.o: init_module: No such
>device
>Hint: insmod errors can be caused by incorrect module parameters,
>including invalid IO or IRQ parameters
>/lib/modules/2.4.2/kernel/drivers/sound/es1371.o: insmod
>/lib/modules/2.4.2/kernel/drivers/sound/es1371.o failed
>/lib/modules/2.4.2/kernel/drivers/sound/es1371.o: insmod es1371 failed
>[root@SMOKEY cbruton]#
>
>That is what I get when I do that. That is kind of weird though that it
>fails if it is supported.
Hmmm. OK, checking groups.google.com finds that the 5880 *should* work
with es1371 in kernel 2.2.16... so why isn't this working? Hmm, do you
have the ac97_codec module loaded? The es1371 module depends on this;
if it isn't getting loaded, something's wrong and you need to do a
depmod -a at the very least. Also check for IRQ conflicts; the thing is
a PCI card and should be able to share an IRQ, but you never know.
(Yes, I'm grasping at straws here.)
BTW, there's a serious problem with the loopback device in 2.4.2, so if
you were looking for an excuse to upgrade to 2.4.3, go for it.
--
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....
------------------------------
From: [EMAIL PROTECTED] (Dances With Crows)
Subject: Re: LS120
Reply-To: [EMAIL PROTECTED]
Date: 20 Apr 2001 01:38:08 GMT
On Thu, 19 Apr 2001 10:31:49 -0500, Bill Wooldridge staggered into the
Black Sun and said:
>Does anyone here work with LS120 floppies in their Linux boxes? If so,
>what system and version?
Yes. Just about any distro made since early 1999 should support an
internal LS-120. Since the internal LS-120 is an IDE device, it's
supported via the ide-floppy.o module, and you can access a DOS
formatted floppy disk or LS-120 disk like so:
mount -t vfat /dev/hdX /mnt/ls120
where X is the letter of the IDE interface the drive is on ("b" for
primary slave, "c" for secondary master, "d" for secondary slave.)
The main problem people have with LS-120s under Linux AFAICT is that
it's difficult to low-level format a floppy disk, since fdformat looks
for /dev/fd0 , which doesn't normally exist in a system with an LS-120
since /dev/hdX is used for accessing either 1.4M floppies or LS-120
disks.
Go to http://groups.google.com/ and search this NG for "LS-120" and see
what you find. HTH, bonne chance....
--
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....
------------------------------
From: [EMAIL PROTECTED] (Martha H Adams)
Subject: Re: linux and cray j90
Date: Fri, 20 Apr 2001 01:58:42 GMT
I've been thinking some more about that possible Cray. I think jwendel's
points about the J90 series are compelling, and maybe they kill the J90
idea. However, one of these days, something else of the sort will be
along. Another *big* machine. Well, how about that?
My thinking about this came together when I recalled a news piece I saw
in the television news last night. The North Shore Railroad Club (just a
little north of Boston), and it included pictures of the large model
railroad they have set up. This is a major project, years of work by many
people, and an amazing and beautiful outcome.
Well now, a big machine is not a desktop; seems to me, when someone gets
one into their hands the very first thing is, it's one machine but it is
necessarily a group project. It's *social.* So how does that work? I
think it works very like a model railroad club: several to many people over
much time. By the way, Eric Raymond in his book The New Hacker's Dictionary,
3rd ed., mentions the importance of a model railroad club at MIT back in
the 1960's. So if someone is going to pick up one of those large computers
that will certainly turn up from time to time (or if they set out to make
a Beowulf array) then what does there need to be?
I'll speculate. The group needs to be at least six persistent and stable
people but not more than about 15. A sort of a club. They need mostly to
be hands-on hacker people with diverse backgrounds. At least one-third of
these people should be women -- men-only groups tend to be kind of harsh.
A few children in there would be good, some kids are super bright and they
experience the conventional educational system as only destructive; and here
would be a way out. The space needed would be at least the size of a 2-car
garage; a very clean basement would be ideal *if* it can't get flooded and
it can be dehumidified.
Then this space gets the machine; *several* terminals; a couple of book
cases; a big root terminal; some work tables; a refrigerator; a meeting
area with folding chairs and a large whiteboard.
The interesting thing about my thinking on this topic is, I started thinking
about hardware but the central topic proved to be *people.* Whoever gets
a hand on a large machine, wants to be a member of a group, not a loner.
Cheers -- Martha Adams
------------------------------
From: Static <[EMAIL PROTECTED]>
Subject: Re: ATI Xpert 2000 Pro Problem
Date: Fri, 20 Apr 2001 02:17:25 GMT
Markku Kolkka wrote:
> "Francisco Galvan" <[EMAIL PROTECTED]> writes:
>> I have an ATI Xpert 2000 Pro with chipset Rage 128 Pro, it works fine in
>> text mode with RH 6.0 and RH6.2 but in the screen goes black when running
>> startx,
>
> You need to upgrade to a later version of XFree86, 4.0.1 or better. You
> don't have to change the whole Linux distribution.
>
I'll second that, while I recently trashed my Ati Rage 128 card, it worked
beautifully under X 4.0.x.
One side note, if for some silly reason you decide to replace your whole
distro with Suse, or Mandrake, or whatever - and it asks you if you want to
test the X configuration during the installation phase, say no.
------------------------------
From: Static <[EMAIL PROTECTED]>
Subject: Re: Sending voice to a modem
Crossposted-To: comp.os.linux.misc
Date: Fri, 20 Apr 2001 02:22:48 GMT
JF Bertrand wrote:
> Hi!
>
> I need to write a program the will call a number and play a message.
>
> I need to find out how to connect to the modem, put the modem in voice
> mode, route the sound card to the modem and play the message. I will
> also need to modem to keep the line open for DTMF after the connection
> is made.
>
> Where can I start, is there a linux book on com programming? Or program
> that already does that. Can I make the initial connection using chat?
>
> Pleae help me
>
Sending the same message three times to two different groups in less than
11 minutes... why? - and you can't even correct the spelling mistakes.
1. The correct commands for putting the modem into voice mode should be
listed in your modem's manual somewhere, and you probably could use chat to
send it, or just redirect to your serial port.
2. As for the sending the audio data to/through the modem - you got me,
hopefully someone else can field that one.
------------------------------
From: Static <[EMAIL PROTECTED]>
Subject: Re: question about modules
Date: Fri, 20 Apr 2001 02:31:37 GMT
Eric P. McCoy wrote:
> [EMAIL PROTECTED] writes:
>
>> I was wondering if someone could explain the concept of compiling
>> support for modules into the kernel and loadable modules?
>
> Modules are like device drivers, but you can load and unload them
> without having to restart the system. This is most useful because...
>
>> And, also, why does the kernel have to be re-compiled when support
>> of a new module is added?
>
> ...you can add new modules without recompiling your entire kernel.
> When you enable that module, just do `make modules; make
> modules_install' and you're set. No reboot required.
>
> This is in contrast to Windows 2000, which requires a reboot after
> certain types of drivers are modified, and marked contrast to lesser
> Windowses, which require a reboot after almost _any_ drivers are
> modified.
>
Another nice thing about modules is that you can reduce the amount of
memory required by the kernel - if you're not using a device, and module
can be unloaded automagically (in a properly configured system).
------------------------------
From: Static <[EMAIL PROTECTED]>
Subject: Re: Sound Blaster 16 PCI\Ensoniq 5880
Date: Fri, 20 Apr 2001 02:36:09 GMT
Dances With Crows wrote:
> On Thu, 19 Apr 2001 00:44:20 GMT, Chris staggered into the Black Sun and
> said:
>>I am running Red Hat 7.0 with a 2.4.2 kernel (Sound support is compiled
>>as a module). I'm have a dual boot with Windows NT.
>>
>>Although my sound card is a Sound Blaster 16 PCI, sndconfig says that
>>it is an Ensoniq 5880, so they are probably basically the same. But
>>then it says it is not supported! I think this is kind of odd, because
>>I don't really know what to do to make it work. So if anyone has any
>>suggestions...they would be appreciated.
>
> "modprobe es1371". The 5880 is specifically supported within es1371.c
> AFAICT from reading the source. sndconfig must be screwed up somewhere.
>
I think sndconfig must be getting a little screwed up somewhere, last time
I checked, the Ensoniq 5880 had nothing in common with the SB16 - beyond
that, I can honesty say I have no idea what is going on there.
------------------------------
From: Static <[EMAIL PROTECTED]>
Subject: Re: remount HD rw
Date: Fri, 20 Apr 2001 02:46:10 GMT
Joeri Sebrechts wrote:
> Frederik Himpe wrote:
>> 1. How can I remount the filesystem so that I can write on it again?
[snip]
> *blinking light above head* Hmmmm, maybe I should install another linux
> on a separate partition, just to be able to repair from there in case
> this ever happens again.
>
> have a nice day,
> Joeri Sebrechts
>
I always like to keep two root partitions on the go, that way if I screw up
too massively, I can boot the other partition and still get to my data...
------------------------------
From: Static <[EMAIL PROTECTED]>
Subject: Re: Partitioning problem
Date: Fri, 20 Apr 2001 03:09:03 GMT
Jonadab the Unsightly One wrote:
[snip]
>> FIPS has detected that the 'physical' start or end sector (head/cylinder/
>> sector) do not match with the 'logical' start/end sector. This is not
>> an error since the 'physical' values are redundant and not used anyway.
>> There are many configurations where the values differ. This message is
>> meant only to inform you that FIPS has adapted the 'physical' values
>> according to the current drive geometry.
>
Basically, WinME was probably 'imaged' or 'ghosted' on his hd
(pre-installed), and either the geometry of the master drive is somewhat
different then that of the destination drive - or Windows is just up to its
normal tricks again.
> I'm no a head/cylinder guru, but I think it's a touch more
> complicated than that, although perhaps FIPS is trying to
> keep things simple for the layman.
>
As long as he stays in the Windows environment, its no big deal. If you
every have to send that drive to some data recovery agency though, he'd be
screwed.
>> and then it prints the following and then dies:
>>
>> ****
>> Checking boot sector ...
>> Error: Invalid jump instruction in boot sector: 00 00 00
>>
>> The first three bytes of the boot sector must be a 3-byte jump (E9 xx xx)
>> or a 2-byte jump (EB xx 90). Perhaps the partition is not yet formatted.
>> FIPS can only split DOS-formatted partitions.
>> ****
>
> Hmmm. This is over my head, particularly since I don't know
The first (I forget the exact count) xxx bytes in the boot sector is
intended to be read by the bios routines during boot, control is then
transfered to this code to take over the boot sequence. The first three
bytes are supposed to be the offset address into that code space indicating
where the 'entry point' is. While I've never played with an WME machine's
hd yet, I'd have to guess that its entry point is at offset 0, which makes
little to no sense whatsoever.
I'm also not sure if M$ decided to change the FAT/VFAT/VFAT32/VCRAP....
filesystem again with WME, so I'd have to think long and hard before I
tried something like FIPs to split a working partition - actually, no I
won't have to think about it, I wouldn't do it.
> jack diddley about FIPS (what's that?). I always do all my
> partitioning with fdisk. However, fdisk cannot resize an
fdisk - a lovely tool, but occassionally I get the feeling its like letting
your kid play with a hammer drill near an antique china cabinet. :-)
[snip]
>
> If worst comes to worst and you can't resize your existing
> Windoze partition, you'll be left with three choices:
>
> 1. Back everything up, delete your Windoze partition (using
> fdisk), then recreate it at a smaller size and restore
> from your backups. This is a definite pain.
>
> 2. Use the "Linux for Windows" thingy. It's not as good
> as having real partitions for Linux, but it doesn't
> require you to repartition anything.
>
> 3. Buy a second hard drive and install Linux there.
> You'll be able to boot it either via floppy (which
> can use your partition on the second hard drive for
> the root filesystem) or else by putting LILO on the
> MBR of the first hard drive. (If you go the second
> route, keep the boot floppy around anyway, because
> if you ever have to reinstall Windoze it will
> overwrite the MBR.)
>
> - jonadab
>
I never saw the original message, but going from Jonadab's reply, I'm
guessing that you want to use FIPS to split the windows partition to give
you some space for Linux.
While this is theoretically possible, I haven't heard of anyone
successfully pulling it off since Win95 (perhaps Win95 OSR2).
IMHO, I'd have to recommend (if you've got a few bucks kicking around)
going with Jonadab's option #3, otherwise, go with #1. If you go with #1,
wipe the drive clean, do your linux install (or at least use a linux
utility to create the linux partition(s) - don't forget, the entire boot
partition must be beliw the 8g limit), making your linux boot disk in the
process - then re-install WME, restore whatever you need from your backups.
Reboot with the linux boot disk, mount your root parition, and rerun lilo
(you'll probably have to edit /etc/lilo.conf, or use linuxconf, to insert a
label for WME)
Whichever route you use, ensure that you keep a fairly up-to-date Linux
emergency boot/repair/recovery (whatever you want to call it) disk handy...
every version of Windows 9x/ME/2K/NT (with the noteable exception on
Win98SE, some wierd build number) will overwrite the MBR if you have to
(and you will someday) re-install, and I've heard (never actually used it
yet) WinME will alter the MBR every time you use its recovery mode.
St.
------------------------------
** 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
******************************
