Linux-Hardware Digest #824, Volume #13            Wed, 1 Nov 00 06:13:03 EST

Contents:
  Re: Yamaha 4416S troubles (Dr Arm�)
  Re: DualMonitor Matrox (Steffen Kluge)
  Re: Not using all available RAM (Webmaster SITE Spain)
  Re: Problems with SB Live! (Daryl Fonseca-Holt)
  Re: DualMonitor Matrox (Johannes Eriksson)
  Re: Please help with Yamaha CDRW (Eric)
  mp3+embedded+linux? ("kevin")
  Re: lilo configuration for SCSI hard drives? (Eric)
  Re: modem won't transmit binary data (Enver Haase)
  Re: I'm throwing away my Diamond FireGL1 Card... (Albert A Arendsen)
  Re: I'm throwing away my Diamond FireGL1 Card... (Albert A Arendsen)
  Re: I'm throwing away my Diamond FireGL1 Card... (Albert A Arendsen)
  Re: I'm throwing away my Diamond FireGL1 Card... (Albert A Arendsen)
  Re: 3Com 3c509B ISA on Corel Linux (Guenter Richter)
  Re: Text console on serial port ??? ("Miguel Angel")

----------------------------------------------------------------------------

From: Dr Arm� <[EMAIL PROTECTED]>
Crossposted-To: comp.sys.ibm.pc.hardware.storage
Subject: Re: Yamaha 4416S troubles
Date: Wed, 01 Nov 2000 06:50:47 GMT

Peter Stein wrote:
> 
> Recently my 4416S recorder started experiencing "Focus Servo Error"
> faults as reported by cdrecord. It goes without saying that on each
> occurence the media was turned into a coaster. Has anyone else seen
> this problem? Is there a fix or is it the end? I'm more than just
> annoyed considering I've taken great pains to ensure the PC is dust
> free and well cooled.
> 
> Peter Stein


Have you tried cleaning the lens recently? This seems to be a worse
peoblem with Yahamas, but is easily solved. Get one of those CD lens
cleaning CD disks and use it a few times. It worked wonders for me.

da

------------------------------

From: [EMAIL PROTECTED] (Steffen Kluge)
Subject: Re: DualMonitor Matrox
Date: 1 Nov 2000 07:46:39 GMT
Reply-To: [EMAIL PROTECTED]

In article <[EMAIL PROTECTED]>,
Monte Richardson  <[EMAIL PROTECTED]> wrote:
>> Does anybody have a positive experience installing a Matrox
>> G100/G200/G400 dual monitor video cards on a linux system?  I have been
>> having some difficulties...  Any comments appreciated.
>It's my understanding that Xfree doesn't support dual monitor set ups, 
>yet.  There are plans to include that in the next major release.  All is 
>according to my recollection after reading the Xfree FAQ.

You can try the Matrox supplied mga driver with XFree86-4.01.
See my post from a week ago.

Cheers
Steffen.

-- 
Steffen Kluge <[EMAIL PROTECTED]>
Fujitsu Australia Ltd
Keywords: photography, Mozart, UNIX, Islay Malt, dark skies
--

------------------------------

From: Webmaster SITE Spain <[EMAIL PROTECTED]>
Subject: Re: Not using all available RAM
Date: Wed, 1 Nov 2000 08:38:13 +0100
Reply-To: [EMAIL PROTECTED]

Darren Satkunas wrote:

> Im am running RedHat Linux 7.0. The machine has 128Megs of RAM and when I
> 
> # cat /proc/meminfo
> 
> tells me that my total memory is only 64 Megs.
> 
> I added append="mem=128M" to my /etc/lilo.conf. I've tried adding this
> line both at the top and at the bottom of lilo.conf. But still no change
> after reboot.
> 
> It shows 128Megs during POST at boot time, but once Linux has loaded it
> only shows 64MB available.
> 
> Im still a Linux newbie so any suggestions in laymans terms would be
> appreciated. I have recompiled my kernel, is there something I missed
> during the make config? Do I have to do something to activate the changes
> in
> lilo.conf  (other than rebooting)?
> 
> *Working my linux bugs out so I can say goodbye to winblows ;O)
> 
> 

Extract from BootPrompt HOWTO:

  3.3.1.  The `mem=' Argument

  The original BIOS call defined in the PC specification  that returns
  the amount of installed memory was only designed to be able to report
  up to 64MB. (Yes, another lack of foresight, just like the 1024
  cylinder disks... sigh.) Linux uses this BIOS call at boot to
  determine how much memory is installed.  If you have more than 64MB of
  RAM installed, you can use this boot argument to tell Linux how much
  memory you have.  Here is a quote from Linus on the usage of the mem=
  parameter.

  ``The kernel will accept any `mem=xx' parameter you give it, and if it
  turns out that you lied to it, it will crash horribly sooner or later.
  The parameter indicates the highest addressable RAM address, so
  `mem=0x1000000' means you have 16MB of memory, for example.  For a
  96MB machine this would be `mem=0x6000000'.  If you tell Linux that it
  has more memory than it actually does have, bad things will happen:
  maybe not at once, but surely eventually.''

  Note that the argument does not have to be in hex, and the suffixes
  `k' and `M' (case insensitive) can be used to specify kilobytes and
  Megabytes, respectively. (A `k' will cause a 10 bit shift on your
  value, and a `M' will cause a 20 bit shift.)  A typical example for a
  128MB machine would be "mem=128m".

Seems that you added the append="mem=128M" in a not correct place.

The file lilo.conf normally have global parameters at the top and
then one or mode OS entries. A normal lilo.cong file looks like this:

# LILO global section
boot=/dev/hda7
vga = normal
read-only
prompt
timeout=100
# End LILO global section

# Linux section
image = /boot/vmlinuz
  append="mem=128M"
  root = /dev/hda7
  label = Linux

It should work this way.

Hope this help.

-- 
Webmaster SITE Spain
http://www.site-spain.com
[EMAIL PROTECTED]


------------------------------

From: [EMAIL PROTECTED] (Daryl Fonseca-Holt)
Subject: Re: Problems with SB Live!
Reply-To: [EMAIL PROTECTED]
Date: Tue, 31 Oct 2000 08:23:43 -0600

I don't understand how you got the SB16 modules if you are using SB Live! My
modules are:
snd-pcm-oss            20332   0 
snd-pcm-plugin         16232   0  [snd-pcm-oss]
snd-mixer-oss           5428   0  [snd-pcm-oss]
snd-card-emu10k1        2672   2 
snd-emu10k1            26472   0  [snd-card-emu10k1]
snd-emux-mem            2680   0  [snd-emu10k1]
snd-pcm                34744   1  [snd-pcm-oss snd-pcm-plugin snd-emu10k1]
snd-timer              10784   0  [snd-pcm]
snd-rawmidi            11640   0  [snd-emu10k1]
snd-ac97-codec         24480   0  [snd-emu10k1]
snd-mixer              25744   1  [snd-mixer-oss snd-emu10k1 snd-ac97-codec]
snd-seq-device          5912   0  [snd-card-emu10k1 snd-rawmidi]
snd                    47884   1  [snd-pcm-oss snd-pcm-plugin snd-mixer-oss
snd-card-emu10k1 snd-emu10k1 snd-emux-mem snd-pcm snd-timer snd-rawmidi
snd-ac97-codec snd-mixer snd-seq-device]
soundcore               4196   5  [snd]

Also, the error "Device or resource busy" usually indicates an IRQ conflict.
You can check those out with 'lspci -v' and compare which PCI cards get which
IRQs. These can be changed by moving cards around or sometimes the BIOS allows
assigning IRQs to specific slots.

I suspect the "Device or resource busy" is due to using the SB-16 drivers and
will clear up when you get the right modules built.

Also, is sound support turned on in your kernel config? The following should
be found in your /usr/src/linux/.config file:
CONFIG_SOUND=m
CONFIG_SOUND_OSS=m

No other CONFIG_SOUND=x items should be m (modules) or y (kernel).
Specifically,  CONFIG_SOUND_EMU10K1 should be commented out, you do not use the
kernel support, just ALSA. If  CONFIG_SOUND_EMU10K1 is not present in the
config at all, that's good.


My /etc/modules.conf contains:

# ALSA native device support
alias char-major-116 snd
options snd snd_major=116 snd_cards_limit=1
alias snd-card-0 snd-card-emu10k1
options snd-card-emu10k1 snd_id="SBLive!"
alias sound emu10k1

When I built the ALSA drivers I used:

 ./configure --with-cards=emu10k1

to get the SB Live! drivers.


Hope this helps.

On Mon, 30 Oct 2000 10:08:00 -0600, [EMAIL PROTECTED] <[EMAIL PROTECTED]> 
wrote:
>Paul Kuliniewicz wrote:
>> 
>> > Hi I have a SBLive!, so i recommend the Alsa player, work better and
>> > sound quality, se at the url : www.alsa-project.org download the drivers
>> > libs and utils , compile and install first the drivers, libs..... so, in
>> the file
>> > README and INSTALL it will explain you how to do, makes the steps
>> > there described and WOW it works!
>> >
>> > PS.: The ALSA drivers are compatible with the OSS, that mean that the
>> > programs compiled for OSS will work with these, one thing you must do,
>> > enable sound in your kernel, and only enable soundcard compatible
>> > OSS as module nothing more, dont select some cards only mark as mo
>> > dule the compatible OSS.
>> >
>> > For more info or explanation, here I am
>> 
>> You asked for it. <g>
>> 
>> I downloaded the ALSA drivers and compiled them as per the instructions on
>> the web site.  However, when I try to load the modules, I get this:
>> 
>> [root@holly /sbin]# ./modprobe snd-card-sb16
>> /lib/modules/2.2.16-22/misc/snd-card-sb16.o: init_module: Device or
>> resource busy
>> Hint: insmod errors can be caused by incorrect module parameters,
>> including invalid IO or IRQ parameters
>> /lib/modules/2.2.16-22/misc/snd-card-sb16.o: insmod
>> /lib/modules/2.2.16-22/misc/snd-card-sb16.o failed
>> /lib/modules/2.2.16-22/misc/snd-card-sb16.o: insmod snd-card-sb16 failed
>> [root@holly /sbin]# ./lsmod
>> Module                  Size  Used by
>> ide-cd                 23628   0  (autoclean)
>> 3c90x                  22224   1  (autoclean)
>> nls_cp437               3876   4  (autoclean)
>> vfat                    9404   2  (autoclean)
>> fat                    30688   2  (autoclean) [vfat]
>> usb-uhci               19052   0  (unused)
>> usbcore                42088   1  [usb-uhci]
>> 
>> It complains that init_module is busy, but I don't see what would be using
>> it.  Is there a different (better or correct) way to load the ALSA driver
>> module?
>> 
>> (In case it matters, when make-ing the ALSA drivers, the makefile spit out a
>> *lot* of warnings, although it finished with a success message.  Neither the
>> lib nor utils makefiles did this.  Could this be a part of the problem?
>> I've got Red Hat 7.0 and whatever version of gcc comes with it.)
>I don't know if you have found the problem yet, but I can suggest a few
>things. One, RH 7.0 comes with a new version of gcc by default. 2.96 I
>believe is what they called it and it has a ton of problems. You may
>consider installing 2.95.2 and removing the current gcc. Also, just as a
>point of reference. Check the permissions on /dev/audio, /dev/mixer,
>/dev/dsp. I think that these are the relevant devices, but if not,
>someone point out those that I missed. Sometimes, this is the issue. And
>finally, you may try a later kernel. I had the Live Platinum working
>flawlessly under 2.4.0-test7 for quite some time. Good luck should you
>still need it.
>-- 
>remove nospam and replace with putzin to reply to me!
>Pete Buelow
>-- True believer in any OS other than MS!

------------------------------

From: [EMAIL PROTECTED] (Johannes Eriksson)
Crossposted-To: alt.os.linux,linux.redhat.install,comp.os.linux.setup,comp.os.linux.x
Subject: Re: DualMonitor Matrox
Reply-To: [EMAIL PROTECTED]
Date: 1 Nov 2000 10:08:17 +0200

On Tue, 31 Oct 2000 18:03:19 -0600, Milan Kratka <[EMAIL PROTECTED]> wrote:
>Does anybody have a positive experience installing a Matrox
>G100/G200/G400 dual monitor video cards on a linux system?  I have been
>having some difficulties...  Any comments appreciated.
>
>Milan Kratka
>[EMAIL PROTECTED]
>
>

At least Matrox G400 users should have no problem getting X running with a
dualhead display using the latest beta drivers from http://www.matrox.com and 
the Xinerama extensions in X 4.0.1. Some window managers may have problems with
different resolutions across screens, however.

The release notes accompanying the beta driver contains good instructions on
how to set up a dual headed display.


--

Johannes Eriksson
[EMAIL PROTECTED]

------------------------------

From: Eric <[EMAIL PROTECTED]>
Subject: Re: Please help with Yamaha CDRW
Date: Wed, 01 Nov 2000 09:26:00 +0100
Reply-To: [EMAIL PROTECTED]

> Paul Silver wrote:
> How do I know which device is the last *physical* device on the chain.

You open the box and take a look?

Eric

------------------------------

From: "kevin" <[EMAIL PROTECTED]>
Subject: mp3+embedded+linux?
Date: Wed, 01 Nov 2000 08:31:47 GMT

I'm a CS student interested in making an mp3 player using an embedded chip.
I have little experiece and I would like to gain some :)  I've saw a project
similar to my idea at www.empeg.com that uses the intel StrongARM processor
SA-1110.  Apparently it has system on chip?  I'm guessing this is much like
a motherboard on the chip? Anyways, assuming this is the correct chip to use
in my application, would linux be a good choice to use in operating my chip?
As the empeg project uses linux on theirs.

Thanx in advance to any pointers, tips to help me get started on my
journey....-Kevin



------------------------------

From: Eric <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc
Subject: Re: lilo configuration for SCSI hard drives?
Date: Wed, 01 Nov 2000 09:40:57 +0100
Reply-To: [EMAIL PROTECTED]

Ilya wrote:
> 
> I installed a second SCSI hard drive in my all SCSI machine. Where is a
> good example of a /etc/lilo.conf file that allows for a 10 second
> window to select the OS to boot? The device files for the disks
> are /dev/sda and probably /dev/sdb. I don't know what the name for the
> second Windows disk is since it obviously does not show up in Linux df
> command. Right now I manually plug in the correponding hard drive to

No, not in df, but what about dmesg?
and take a look a fdisk too.

Eric

> boot either into Redhat 6.1 or Windows 2000 Pro. My Linux disk is SCSI
> id of 0, my Windows has SCSI id of 1, tape drive 4 and CDROM 6 so there
> is no conflict there.
> 
> Sent via Deja.com http://www.deja.com/
> Before you buy.

------------------------------

From: Enver Haase <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup,comp.os.linux.networking
Subject: Re: modem won't transmit binary data
Date: Wed, 01 Nov 2000 10:44:00 +0100

JEREMY S BEIM wrote:
> 
> I'm setting up Slackware Linux 7 with kernel 2.3.99-pre3. My modem is an
> external Zoom 56K which I got specifically because I heard it's compatible
> with Linux. It works fine in Windows. I can connect with minicom, but when
> I try to download a binary file, I get a bunch of CRC errors and it fails.
> When I try to connect with pppd, my script connects but then times out
> sending LCP requests. I've tried using hardware, software, and bare
> flow control. I've tried using three different accounts: Earthlink, my
> school, and another. Nothing works. Can someone please help me?!?

Be sure, an external Hayes-compatible ("AT-command") modem WORKS FINE
with Linux.
You need to play with the settings a little- ever tried out "Hardware
Flow Control"
(= RTS/CTS)? And is your cable capable of this (most are)?

Bye
E.

------------------------------

From: Albert A Arendsen <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.x
Subject: Re: I'm throwing away my Diamond FireGL1 Card...
Date: Wed, 01 Nov 2000 11:36:23 +0100

[EMAIL PROTECTED] wrote:
> 
> >No, ofcourse that doesn't help the situation now. Can you think of
> >anything, ANYthing, that COULD help the situation NOW?
> 
> Yes.  Diamond produces an open specification for the devices in question,
> with permission granted to create software drivers to use the devices.
> 
> I don't understand what's so hard about that.

And that, good sir, is exactly your problem: you don't understand. :)

S3/DiamondMM is run by businessmen. Businessmen see dollars. They see
that if they open their specifications, other companies might think
"hey, that's a good idea", impliment their API in their own hardware,
and make money off it. Businessmen want to keep as much as possible
about their products secret. Never mind that it's illogical and
counterproductive, but that's how they see it.

-- 
Albert Arendsen --- aka --- Reyn Eaglestorm
>>>>> The Gods have a sense of humour <<<<<
>>>>> So be sure you don't lose yours <<<<<
http://home.student.utwente.nl/a.a.arendsen

------------------------------

From: Albert A Arendsen <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.x
Subject: Re: I'm throwing away my Diamond FireGL1 Card...
Date: Wed, 01 Nov 2000 11:40:35 +0100

[EMAIL PROTECTED] wrote:
> 
> In article <[EMAIL PROTECTED]>,
> Albert A Arendsen  <[EMAIL PROTECTED]> wrote:
> 
> >I bring it up constantly. As I said previously, a steady drop can hollow
> >out a stone. Over half of our tech support crew runs Linux at home
> >either as some sort of server or, like me, exclusively. We're constantly
> >pushing. But sometimes we do feel like ants trying to move a mountain :(
> 
> How do I communicate my decision to buy a competitor's card based on this
> problem?  How would that information ever reach someone in a senior chair
> of a marketing role?

Send it to [EMAIL PROTECTED], that way it'll end up in the
mailbox of my collegues and I, we'll put it in the "Thankyous" folder,
which is read by the top dogs of S3/DMM every month or so. We love
nothing more than putting a "thanks for your non-support, I'm going to
buy a competitor's card" message in the Thankyous folder :)

> I used to be a repeat Diamond customer, and recommended the cards to
> everyone, back in the S3/S3V days.  Now, I can do no such thing, and I
> cannot buy one because of this defect.  And I do see it as a defect.
> I've been called out in the n.g. for insulting you; I don't mean to
> insult you personally, but I am attempting to speak as a former customer
> (and until this morning, a potential return customer), to a company who's
> lost my business.  It stinks for me, and it should really stink for someone
> whose job it is to maximize market saturation.  Your company's marketing
> department is dismissing the entire non-windows segment of the pc world.
> Maybe it doesn't matter to them, but it should.

Please write a well thought out message with your concerns and your
reason for choosing to buy a competitor's product to
[EMAIL PROTECTED] Yet another drop helping to hollow out the
stone :)

-- 
Albert Arendsen --- aka --- Reyn Eaglestorm
>>>>> The Gods have a sense of humour <<<<<
>>>>> So be sure you don't lose yours <<<<<
http://home.student.utwente.nl/a.a.arendsen

------------------------------

From: Albert A Arendsen <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.x
Subject: Re: I'm throwing away my Diamond FireGL1 Card...
Date: Wed, 01 Nov 2000 11:42:07 +0100

Steve Wolfe wrote:
> 
>   Sheesh.  I never saw a system with an S3 that didn't have problems.  I
> avoided them like the plague.   I'm glad that you had a better experience
> than I did.  ; )

Actually, the S3 Virge chipset is the most widely supported graphics
chipset out there. Heck, it even works better under Linux than it does
under Windows :)

-- 
Albert Arendsen --- aka --- Reyn Eaglestorm
>>>>> The Gods have a sense of humour <<<<<
>>>>> So be sure you don't lose yours <<<<<
http://home.student.utwente.nl/a.a.arendsen

------------------------------

From: Albert A Arendsen <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.x
Subject: Re: I'm throwing away my Diamond FireGL1 Card...
Date: Wed, 01 Nov 2000 11:45:37 +0100

[EMAIL PROTECTED] wrote:
> 
> My guess is that Diamond doesn't really own all the IP in their products
> and that this NDA business is being propogated from the vendor of one of
> their chips.  Is that so?

I don't know, could be. For the FireGL cards at least. But the Stealth
III and the Viper II are definitely fully S3/DMM products, chipset and
board and all.

-- 
Albert Arendsen --- aka --- Reyn Eaglestorm
>>>>> The Gods have a sense of humour <<<<<
>>>>> So be sure you don't lose yours <<<<<
http://home.student.utwente.nl/a.a.arendsen

------------------------------

From: [EMAIL PROTECTED] (Guenter Richter)
Subject: Re: 3Com 3c509B ISA on Corel Linux
Date: Wed, 01 Nov 2000 09:46:29 GMT

On Mon, 30 Oct 2000 17:15:23 -0500, mst <[EMAIL PROTECTED]> wrote:

>Read the Ethernet-HOWTO at http://linuxdoc.org. Your problem is the
>3c509 is a PnP card, so you have either to disable the PnP mode with a
>3com utility (it's on their web site) or use pnpdump and isapnp to
>allocate the hardware resources on the card.
>
>MST

Agreed on the howto-issue, but: there could be different versions of
the 3c509b out there, because mine doesn't care about pnp at all .
There is a utility from 3com on their installation disk to be run in
DOS (3c5x9cfg.exe) which can be used to change the hardware settings
in the eeprom on the card. Once set, this did the trick for me.
HTH
Gu:nter

------------------------------

From: "Miguel Angel" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc
Subject: Re: Text console on serial port ???
Date: Wed, 1 Nov 2000 12:03:32 +0100

Hi ,thaks .
The Solution is :

1.- Your kernel must have support for serial consoles ( Block Devices ->
Virtual Console + Serial port + Console on serial Prot )
2.- Install getty_ps.XXX.rpm package.
3.- Add line to lilo.conf as it
        serial=0,9600n8
4.- Add kenel parameter on lilo.conf:
        append="console=ttyS0,9600
5.- Add suport for login on serial console on /etc/inittab
    s1:123:respanw:/sbin/getty ttyS0 -L DT9600 vt100
6.- Add suport for root login on serial console on /etc/securetty add to the
end "ttyS0"

OK


"Jim Bonnet" <[EMAIL PROTECTED]> escribi� en el mensaje
news:[EMAIL PROTECTED]...
> Falcon wrote:
> >
> > Hi ,
> >
> >     I'm traing to put a text console attached to serial port , I'm
traing to
> > use lilo.conf parameters and kernel command line , but it don't work .
>
> There are HOW-TO's on both lilo & serial terminals. www.linux.com/howto
>
> Why don't you look there first, and then post specific problems that you
> may encounter.
>
> >
> >     Any suggestion
> >
> > Thanks



------------------------------


** 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
******************************

Reply via email to