All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wesley Hosking <wes@atlantek.com.au>
To: ultralinux@vger.kernel.org
Subject: Re: shm problems ?
Date: Mon, 28 Sep 1998 07:01:48 +0000	[thread overview]
Message-ID: <marc-linux-ultrasparc-90696509909734@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-90671327306006@msgid-missing>

David S. Miller writes:
 > 
 > Upgrade to and install latest CVS kernel.
 > 
 > ftp://vger.rutgers.edu/pub/linux/README.CVS
 > 
It turned out I had to do both....
Jakub put a fix into the CVS archive for sg.o
(the generic scsi device) 

AND it required the stuff below (I changed the 1024's for SHMMAX to
4096)... 

(cdrecord requires a 4Mbyte chunk to ensure the SCSI flow is kept 
full to the CD - I just made it 4 * larger to make sure ;-)

It works fine ! (now).

wes


In response to Wesley Hosking writes:
 > I am VGER 2.1.121 with shm enabled, on an Ultra 30.
 > 
 > When I use xcdroast to burn a CD it gives me :
 > /usr/lib/xcdroast-0.96d/bin/cdrecord-1.6: Invalid argument. shmget failed
 > Cdrecord release 1.6 Copyright (C) 1995-1998 Jörg Schilling
 > 
 > (I also get the same in sparc32 mode :
 > 
 > /usr/lib/xcdroast-0.96d/bin/cdrecord-1.6: Invalid argument. shmget failed
 > Cdrecord release 1.6 Copyright (C) 1995-1998 Jörg Schilling
 > 
 > .....
 > 
 > ok - its probably the 
 > #define SHMMAX (1024 * 1024)
 > in include/asm-sparc64/shmparam.h   
 > 
 > 
 > cdrecord requires a 4M chunk...
 > will try it at 16Mb, and see if that is the problem.
 > 
 > If you don't hear from me there thats probably what the fix is ;-)
 > 
 > wes

      parent reply	other threads:[~1998-09-28  7:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-09-25  3:33 shm problems ? Wesley Hosking
1998-09-25  8:04 ` David S. Miller
1998-09-28  7:01 ` Wesley Hosking [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-ultrasparc-90696509909734@msgid-missing \
    --to=wes@atlantek.com.au \
    --cc=ultralinux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.