I would say that you either need to wait until SUSE ships the functionality in a pre-built kernel, or compile your own for testing purposes, with the understanding that they won't support you.
Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Tom Shilson Sent: Friday, March 17, 2006 10:47 PM To: [email protected] Subject: dcssblk.segments= Kernel Parameter Invalid?? My z/VM wizard returned from share greatly excited to try swapping to DCSS. He set up the segments and an EXEC that would properly define storage with the gap. It was up to me to do the Linux part. With only a few stumbles I got it running. There is one inconsistency. I set up the zipl.conf parameter to specify dcss.segments=SWAP16M,<more segments> . The console log says that the dcss.segments= parameter is invalid, yet it must be there for swapping to DCSS to work. /proc/cmdline shows the entire parameter string. Here is a snip from the console log: Kernel command line: root=/dev/dasdb1 selinux=0 TERM=dumb elevator=cfq vmpoff=LOGOFF dcssblk.segments=SWAP16M,SWAP32M,SWAP64M,SWAP128M,SWAP256M,SWAP512M BOOT_IMAGE=0 Unknown boot option `dcssblk.segments=SWAP16M,SWAP32M,SWAP64M,SWAP128M,SWAP256M,SWAP512M': ignoring Here is my zipl.conf parameter string: parameters = "root=/dev/dasdb1 selinux=0 TERM=dumb elevator=cfq vmpoff=LOGOFF dcssblk.segments=SWAP16M,SWAP32M,SWAP64M,SWAP128M,SWAP256M,SWAP512M " This is SuSE SLES9 64-bit SP3 recently patched running on z/VM 5.2 on a z900. Can anyone explain it or tell me which organization I should notify? Thanks, Tom ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
