May 2006 - openSUSE Autoinstall - openSUSE Mailing Lists

Scripting dirinstall?
by Teun 25 Feb '07

25 Feb '07

Does anyone know if it is possible to use the 'dirinstall' from the command line? For instance i would like to be able to do something like: # yast dirinstall -d /someroot -s mypackages.sel If i do yast -h it says: "Usage: /sbin/yast [OPTIONS] [MODULE] [module specific parameters]" But is there a way to find out what 'module specific parameters' are available for a specific module? Thanks, Teun

3 2

FYI: adding own RPMs to a SLES10 inst. source
by Uwe Gansert 06 Jul '06

06 Jul '06

Hi, here is a small documentation how to add own RPMs to a SLES10/SL10.1 installation source. To create a tree with RPMs in parallel of your other installation source, use at least version 20060418 of create_update_source.sh from my SUSE Homepage (http://www.suse.de/~ug) The latest autoyast2-utils RPM will contain that script too. You can find documentation on how to use that script on my homepage. After you have created the tree with your own RPMS, you have two options· to tell autoyast about that new installation source. Either in the autoyast profile like this: > <add-on> > <add_on_products config:type="list"> > <listentry> > <media_url>http://192.168.66.1/SLES10/updates</media_url> > <product>SuSE-Linux-Updates</product> > <product_dir>/</product_dir> > </listentry> > </add_on_products> > </add-on> You can do that with the autoyast UI on SLES10/SL10.1 too. Or another option is to create a file called "add_on_products" on the main installation source. So it looks like this (the "updates" directory was created by the script): > #:/space/SLES10 # tree -L 1 > . > |-- ARCHIVES.gz > |-- COPYING > |-- COPYING.de > |-- COPYRIGHT > |-- COPYRIGHT.de > |-- ChangeLog > |-- INDEX.gz > |-- LICENSE.TXT > |-- NEWS > |-- README > |-- README.BETA > |-- README.BETA.DOS > |-- README.DOS > |-- add_on_products > |-- boot > |-- content > |-- control.xml > |-- directory.yast > |-- docu > |-- dosutils > |-- gpg-pubkey-0dfb3188-41ed929b.asc > |-- gpg-pubkey-1d061a62-427a396f.asc > |-- gpg-pubkey-307e3d54-44201d5d.asc > |-- gpg-pubkey-3d25d3d9-36e12d04.asc > |-- gpg-pubkey-9c800aca-40d8063e.asc > |-- ls-lR.gz > |-- media.1 > |-- pubring.gpg > |-- suse > `-- updates > > #:/space/SLES10 # cat add_on_products > http://192.168.66.1/SLES10/updates With that file on the installation source, you don't need to specify the additional installation sources in the autoyast profile. You can mix those two options. So it's possible to specify one installation source in the autoyast profile and another one in the "add_on_products"-file. The "add_on_products"-file is not supported by autoyast in RC1 but will be with later versions. I hope that helps. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert(a)suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de

1 2

SELS 10 Network Installation Directory Layout?
by Pete Nishimoto 07 Jun '06

07 Jun '06

Hi, I'm trying to setup a PXE server to autoinstall SELS 10 and I'm running into a problem because I'm not sure how to layout the installation directories for the network install. I've setup the installation directories and links to sucessfully network install SELS 9 and I figured it would be pretty much the same. However, I've run into a problem. I've created a SELS 10 (Beta 9) installation directory much like a SLES 9 installation directory, with a sles10 directory (containing CD 1) and a core10 direcotry (containining the contents of CD 2-4 in the directories CD1-CD3). I'm able to install the first CD once I get a number of extra links (which wasn't in SELS 9), such as content.asc, content.key. I've found that I also need a link ./suse->sels10/CD1/suse to get the first CD to install. However, when the installation reboots (after installing CD1), and it start to go through the other packages, etc., it first looks for the media.2 file. Ok, so I put a link for media.2 to core10/CD1/media.2. But then it turns out that the installation procedure is trying to find the first package that I want to install (aalib) and it traverses the ./suse link to look for it. Since ./suse->sles10/CD1/suse, the aalib rpm is not there (it's in ./core10/CD1/suse). Of course, if I restart at this point and have ./suse->core01/CD1/suse, it can't find 'setup' and then the installation fails. So, I still need to know what's the right directory tree layout for SELS10. Is there any script/documentation/pointer to anything that can help me here? I'm stuck because of the problem with the ./suse link, and the installer wanting different contents for different times. I was thinking, does it have to do with the ./yast/instorder or ./yast/order files (are these still used?). Please help. I'm really close and just need a nudge in the right direction. I'll continue to search the mail lists, but a shortcut would be greatly appreciated. Pete

3 3

problems with ask
by Simon Crute 07 Jun '06

07 Jun '06

Hi, I'm trying to use the new Ask feature of autoyast, and prompt the user if they want their disk initialising. This is how the ask lines are looking in the /tmpautoinst.xml after the profiles have been merged etc. <ask-list config:type="list"> <listentry> <default>false</default> <path>partitioning,drive,initialize</path> <question>Do you want to remove all existing partitions ?</question> <stage>initial</stage> <title>Fdisk</title> <type>boolean</type> </listentry> </ask-list> However, I'm not seeing any popups during the install This is on SLED10-rc2 -- Simon Crute IS&T Bracknell Novell UK Ltd

2 6

SLES10 RC2 network install - No catalog found
by Jeremy Silver 31 May '06

31 May '06

I have been doing network installation of SUSE 9.3/10.0 and SLES 9 (pxe/tftp/http) for some time, and am now having a problem with SLES 10 RC2. I have downloaded the CD ISO's, installed them using the YaST installation server module as I did with my other SUSE sources. The installation (not automated, just pointing to the installation tree via http) starts fine but once it gets to "Installation Settings" the Software section reports "No catalog found at http://x.x.x.x/autoyast/sles10-rc2/" and "ERROR: No proposal". Beta 8 worked fine but I ran into the same problem with RC1, hoping it was just an issue with that release. However, now I am not sure what is going on. I have tried two different installation servers, my main one running SUSE 10.0 and a temporary server to try and figure out this problem running SLES10 Beta 8. Does anyone have any idea what is going on? I am surprised the both release candidates are not installable via the network; I guess it is back to CD's. ------------------------------------------------ Jeremy Silver Technical Services Manager BroadWare Technologies 408-342-2611 (direct) 650-346-7246 (mobile) jeremy(a)broadware.com <blocked::mailto:jeremy@broadware.com> http://www.broadware.com <blocked::http://www.broadware.com/> This message (including any attachments) is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

2 3

AutoYaST problems with SuSE 10.1
by Lee Mayes 31 May '06

31 May '06

I created my 10.1 installation depot (i386 & x86_64) by mounting the retail DVD and cp -ar. This has worked great in the past for the non enterprise releases, and I can install manually against the depot, but autoyast installations all fail when they attempt to resolve the software section. I tried using a 'clone' of my manual install, as well as a very simple <software> section with only <base>default-Gnome</base>. No matter what's in autoyast.xml, the installs fail at the same place. Thinking I had a problem with my depot, I even pointed at one of the internet mirrors. No Joy. Here are snippets of y2log on the machines when they fail, and a working one when I did the install manually (the one I cloned). For some reason when autoyast is in play, it says it cannot create the mountpoint due to: "Create attach point: attach root is not a writable directory: '/var/adm/mount'". After failure, I've pushed a shell and verified I can create a directory and touch a file there. When using HTTP, there are no 404's in the log that are unexpected (basically the same ones as during manual). I tried increasing the ramdisk size to 64M thinking maybe it was out of space, no luck there either. Any ideas? I'm stumped! I can provide full logfiles and my autoyast.xml file on request, but it's pretty simple, and from the error it appears no matter what's in there it wasn't going to be able to resolve the software section as it fails to create the mountpoint where it would mount media.1/products, etc. HTTP against my local source - AutoYaST 2006-05-30 07:59:19 <1> 192.168.1.105(3147) [wfm] Packages.ycp:554 Pkg Builtin called: SourceCreateBase 2006-05-30 07:59:19 <1> 192.168.1.105(3147) [media] MediaAccess.cc(open):109 Trying scheme 'http' 2006-05-30 07:59:19 <1> 192.168.1.105(3147) [media] MediaCurl.cc(MediaCurl):120 MediaCurl::MediaCurl(http://192.168.1.5/LinuxCOE/SuSE/i386/10.1, ) 2006-05-30 07:59:19 <1> 192.168.1.105(3147) [media] MediaAccess.cc(open):142 Opened: http(http://192.168.1.5/LinuxCOE/SuSE/i386/10.1 not attached; localRoot "") 2006-05-30 07:59:19 <0> 192.168.1.105(3147) [media] MediaManager.cc(open):412 Opened new media access using id 2 to http://192.168.1.5/LinuxCOE/SuSE/i386/10.1 2006-05-30 07:59:19 <0> 192.168.1.105(3147) [media] MediaManager.cc(attach):557 attach(id=2) 2006-05-30 07:59:19 <0> 192.168.1.105(3147) [media] MediaHandler.cc(createAttachPoint):337 Create attach point: attach root is not a writable directory: '/var/adm/mount' 2006-05-30 07:59:19 <0> 192.168.1.105(3147) [media] MediaHandler.cc(createAttachPoint):337 Create attach point: attach root is not a writable directory: '/var/tmp' 2006-05-30 07:59:19 <5> 192.168.1.105(3147) [base] Exception.cc(log):94 MediaCurl.cc(attachTo):193 THROW: MediaCurl.cc(attachTo):193: Bad media attach point: http://192.168.1.5/LinuxCOE/SuSE/i386/10.1 2006-05-30 07:59:19 <5> 192.168.1.105(3147) [base] Exception.cc(log):94 2006-05-30 07:59:19 <0> 192.168.1.105(3147) [media] MediaHandler.cc(removeAttachPoint):127 MediaHandler - checking if to remove attach point 2006-05-30 07:59:19 <5> 192.168.1.105(3147) [base] Exception.cc(log):94 MediaHandler.cc(attach):580 RETHROW: MediaCurl.cc(attachTo):193: Bad media attach point: http://192.168.1.5/LinuxCOE/SuSE/i386/10.1 2006-05-30 07:59:19 <5> 192.168.1.105(3147) [base] Exception.cc(log):94 2006-05-30 07:59:19 <3> 192.168.1.105(3147) [wfm] Source.cc(SourceCreateEx):1002 Cannot read the product list from the media 2006-05-30 07:59:19 <3> 192.168.1.105(3147) [YCP] Packages.ycp:557 No source on 'http://192.168.1.5/LinuxCOE/SuSE/i386/10.1' 2006-05-30 07:59:19 <1> 192.168.1.105(3147) [wfm] AutoinstSoftware.ycp:378 Pkg Builtin called: ResolvableInstall 2006-05-30 07:59:19 <3> 192.168.1.105(3147) [YCP] AutoinstSoftware.ycp:380 Error while setting base selection: default-Gnome NFS against my local source - AutoYaST 2006-05-30 08:20:27 <1> 192.168.1.105(3151) [wfm] Packages.ycp:554 Pkg Builtin called: SourceCreateBase 2006-05-30 08:20:27 <1> 192.168.1.105(3151) [media] MediaAccess.cc(open):109 Trying scheme 'nfs' 2006-05-30 08:20:27 <1> 192.168.1.105(3151) [media] MediaNFS.cc(MediaNFS):47 MediaNFS::MediaNFS(nfs://192.168.1.5/var/opt/LinuxCOE/SuSE/i386/10.1, ) 2006-05-30 08:20:27 <1> 192.168.1.105(3151) [media] MediaAccess.cc(open):142 Opened: nfs(nfs://192.168.1.5/var/opt/LinuxCOE/SuSE/i386/10.1 not attached; localRoot "") 2006-05-30 08:20:27 <0> 192.168.1.105(3151) [media] MediaManager.cc(open):412 Opened new media access using id 2 to nfs://192.168.1.5/var/opt/LinuxCOE/SuSE/i386/10.1 2006-05-30 08:20:27 <0> 192.168.1.105(3151) [media] MediaManager.cc(attach):557 attach(id=2) 2006-05-30 08:20:27 <0> 192.168.1.105(3151) [media] MediaHandler.cc(createAttachPoint):337 Create attach point: attach root is not a writable directory: '/var/adm/mount' 2006-05-30 08:20:27 <0> 192.168.1.105(3151) [media] MediaHandler.cc(createAttachPoint):337 Create attach point: attach root is not a writable directory: '/var/tmp' 2006-05-30 08:20:27 <5> 192.168.1.105(3151) [base] Exception.cc(log):94 MediaNFS.cc(attachTo):96 THROW: MediaNFS.cc(attachTo):96: Bad media attach point: nfs://192.168.1.5/var/opt/LinuxCOE/SuSE/i386/10.1 2006-05-30 08:20:27 <5> 192.168.1.105(3151) [base] Exception.cc(log):94 2006-05-30 08:20:27 <1> 192.168.1.105(3151) [media] Mount.cc(~Mount):45 ~Mount() 2006-05-30 08:20:27 <1> 192.168.1.105(3151) [media] Mount.cc(~Mount):52 ~Mount() end 2006-05-30 08:20:27 <0> 192.168.1.105(3151) [media] MediaHandler.cc(removeAttachPoint):127 MediaHandler - checking if to remove attach point 2006-05-30 08:20:27 <5> 192.168.1.105(3151) [base] Exception.cc(log):94 MediaHandler.cc(attach):580 RETHROW: MediaNFS.cc(attachTo):96: Bad media attach point: nfs://192.168.1.5/var/opt/LinuxCOE/SuSE/i386/10.1 2006-05-30 08:20:27 <5> 192.168.1.105(3151) [base] Exception.cc(log):94 2006-05-30 08:20:27 <3> 192.168.1.105(3151) [wfm] Source.cc(SourceCreateEx):1002 Cannot read the product list from the media 2006-05-30 08:20:27 <3> 192.168.1.105(3151) [YCP] Packages.ycp:557 No source on 'nfs://192.168.1.5/var/opt/LinuxCOE/SuSE/i386/10.1' 2006-05-30 08:20:27 <1> 192.168.1.105(3151) [wfm] AutoinstSoftware.ycp:378 Pkg Builtin called: ResolvableInstall 2006-05-30 08:20:27 <3> 192.168.1.105(3151) [YCP] AutoinstSoftware.ycp:380 Error while setting base selection: default-Gnome FTP against an internet source - AutoYaST 2006-05-30 10:25:29 <1> 192.168.1.105(3147) [wfm] Packages.ycp:554 Pkg Builtin called: SourceCreateBase 2006-05-30 10:25:29 <1> 192.168.1.105(3147) [media] MediaAccess.cc(open):109 Trying scheme 'ftp' 2006-05-30 10:25:29 <1> 192.168.1.105(3147) [media] MediaCurl.cc(MediaCurl):120 MediaCurl::MediaCurl(ftp://128.138.238.174/%2fpub/opensuse/distribution/SL-10.1/inst-source/, ) 2006-05-30 10:25:29 <1> 192.168.1.105(3147) [media] MediaAccess.cc(open):142 Opened: ftp(ftp://128.138.238.174/%2fpub/opensuse/distribution/SL-10.1/inst-source/ not attached; localRoot "") 2006-05-30 10:25:29 <0> 192.168.1.105(3147) [media] MediaManager.cc(open):412 Opened new media access using id 2 to ftp://128.138.238.174/%2fpub/opensuse/distribution/SL-10.1/inst-source/ 2006-05-30 10:25:29 <0> 192.168.1.105(3147) [media] MediaManager.cc(attach):557 attach(id=2) 2006-05-30 10:25:29 <0> 192.168.1.105(3147) [media] MediaHandler.cc(createAttachPoint):337 Create attach point: attach root is not a writable directory: '/var/adm/mount' 2006-05-30 10:25:29 <0> 192.168.1.105(3147) [media] MediaHandler.cc(createAttachPoint):337 Create attach point: attach root is not a writable directory: '/var/tmp' 2006-05-30 10:25:29 <5> 192.168.1.105(3147) [base] Exception.cc(log):94 MediaCurl.cc(attachTo):193 THROW: MediaCurl.cc(attachTo):193: Bad media attach point: ftp://128.138.238.174/%2fpub/opensuse/distribution/SL-10.1/inst-source/ 2006-05-30 10:25:29 <5> 192.168.1.105(3147) [base] Exception.cc(log):94 2006-05-30 10:25:29 <0> 192.168.1.105(3147) [media] MediaHandler.cc(removeAttachPoint):127 MediaHandler - checking if to remove attach point 2006-05-30 10:25:29 <5> 192.168.1.105(3147) [base] Exception.cc(log):94 MediaHandler.cc(attach):580 RETHROW: MediaCurl.cc(attachTo):193: Bad media attach point: ftp://128.138.238.174/%2fpub/opensuse/distribution/SL-10.1/inst-source/ 2006-05-30 10:25:29 <5> 192.168.1.105(3147) [base] Exception.cc(log):94 2006-05-30 10:25:29 <3> 192.168.1.105(3147) [wfm] Source.cc(SourceCreateEx):1002 Cannot read the product list from the media 2006-05-30 10:25:29 <3> 192.168.1.105(3147) [YCP] Packages.ycp:557 No source on 'ftp://128.138.238.174/%2fpub/opensuse/distribution/SL-10.1/inst-source/' 2006-05-30 10:25:29 <1> 192.168.1.105(3147) [wfm] AutoinstSoftware.ycp:378 Pkg Builtin called: ResolvableInstall 2006-05-30 10:25:29 <3> 192.168.1.105(3147) [YCP] AutoinstSoftware.ycp:380 Error while setting base selection: default-Gnome And lastly, here's HTTP against my source during a *MANUAL* install: 2006-05-18 11:57:12 <1> 192.168.1.103(3233) [wfm] Packages.ycp:554 Pkg Builtin called: SourceCreateBase 2006-05-18 11:57:12 <1> 192.168.1.103(3233) [media] MediaAccess.cc(open):109 Trying scheme 'http' 2006-05-18 11:57:12 <1> 192.168.1.103(3233) [media] MediaCurl.cc(MediaCurl):120 MediaCurl::MediaCurl(http://192.168.1.5/LinuxCOE/SuSE/i386/10.1, ) 2006-05-18 11:57:12 <1> 192.168.1.103(3233) [media] MediaAccess.cc(open):142 Opened: http(http://192.168.1.5/LinuxCOE/SuSE/i386/10.1 not attached; localRoot "") 2006-05-18 11:57:12 <0> 192.168.1.103(3233) [media] MediaManager.cc(open):412 Opened new media access using id 1 to http://192.168.1.5/LinuxCOE/SuSE/i386/10.1 2006-05-18 11:57:12 <0> 192.168.1.103(3233) [media] MediaManager.cc(attach):557 attach(id=1) 2006-05-18 11:57:12 <0> 192.168.1.103(3233) [media] MediaHandler.cc(createAttachPoint):342 Trying to create attach point in /var/adm/mount 2006-05-18 11:57:12 <0> 192.168.1.103(3233) [zypp] PathInfo.cc(_Log_Result):291 mkdir /var/adm/mount/AP_0x00000001 00755 2006-05-18 11:57:12 <1> 192.168.1.103(3233) [media] MediaHandler.cc(createAttachPoint):319 Created default attach point /var/adm/mount/AP_0x00000001 2006-05-18 11:57:12 <0> 192.168.1.103(3233) [DEFINE_LOGGROUP] ProxyInfoSysconfig.cc(sysconfigRead):32 Load '/etc/sysconfig/proxy' 2006-05-18 11:57:12 <0> 192.168.1.103(3233) [DEFINE_LOGGROUP] ProxyInfoSysconfig.cc(sysconfigRead):55 KEY: 'PROXY_ENABLED' VALUE: 'no' 2006-05-18 11:57:12 <0> 192.168.1.103(3233) [DEFINE_LOGGROUP] ProxyInfoSysconfig.cc(sysconfigRead):55 KEY: 'HTTP_PROXY' VALUE: '' <snip> and the install continues as mkdir of the mountpoint succeeded and it's able to see software selections. Best Regards, Lee

1 0

multiple installation sources
by Dejan Muhamedagic 31 May '06

31 May '06

Hello, Is it possible to have multiple (network) installation sources with autoyast? The idea is to use the official SuSE site for the SLES packages and also have a local repository of home made RPMs. Cheers, -- Dejan Muhamedagic

2 5

autoyast with pre partitioned harddisk
by Mario Gzuk 31 May '06

31 May '06

Hi, i have several problems with a pre partitioned harddisk and autoyast. This is the p. section: <partitioning config:type="list"> <drive> <device>/dev/hda</device> <partitions config:type="list"> <partition> <create config:type="boolean">false</create> <filesystem config:type="symbol">ntfs</filesystem> <format config:type="boolean">false</format> <mount>/mnt/C</mount> <partition_nr>1</partition_nr> </partition> <partition> <create config:type="boolean">false</create> <filesystem config:type="symbol">ext2</filesystem> <format config:type="boolean">true</format> <mount>/boot</mount> <partition_nr>5</partition_nr> </partition> <partition> <create config:type="boolean">false</create> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_nr>6</partition_nr> </partition> <partition> <create config:type="boolean">false</create> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/var</mount> <partition_nr>7</partition_nr> </partition> <partition> <create config:type="boolean">false</create> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_nr>8</partition_nr> </partition> <partition> <create config:type="boolean">false</create> <filesystem config:type="symbol">vfat</filesystem> <format config:type="boolean">true</format> <mount>/mnt/D</mount> <partition_nr>9</partition_nr> </partition> </partitions> <initialize config:type="boolean">false</initialize> </drive> </partitioning> All partitions except partition one (ntfs) are NOT mounted during the installation. So the installation fails after the ram disk is full.... Any hints? thank you. greetings mario gzuk

2 5

RE: [suse-autoinstall] SLES10 RC2 network install - No catalog found
by Kevin Lyons 30 May '06

30 May '06

>I have been doing network installation of SUSE 9.3/10.0 and SLES 9 >(pxe/tftp/http) for some time, and am now having a problem with SLES 10 RC2. >I have downloaded the CD ISO's, installed them using the YaST installation >server module as I did with my other SUSE sources. The installation (not >automated, just pointing to the installation tree via http) starts fine but >once it gets to "Installation Settings" the Software section reports "No >catalog found at http://x.x.x.x/autoyast/sles10-rc2/" and "ERROR: No >proposal". > >Beta 8 worked fine but I ran into the same problem with RC1, hoping it was >just an issue with that release. However, now I am not sure what is going >on. I have tried two different installation servers, my main one running >SUSE 10.0 and a temporary server to try and figure out this problem running >SLES10 Beta 8. This is a bug that has supposedly been fixed in the installation server module of SLES10 RC2. I do not know if there is a plan to release a fix to the yast2-instserver module for SLES9/SL9.3/SL10.0/SL10.1. When the post-Beta8-pre-RC2 module copied the files from the CD isos to the directory the directory.yast file gets repeated overwritten so that it ends up with the directory.yast file from CD4. The directory.yast file lists the contents of the root directory of the install source, which YaST then uses during the installation to find stuff. The directory.yast file from CD4 does not list all of the files, so YaST cannot find things and you get the error that you have seen. You can do one of the following: 1. Manually recreate the directory.yast file so that it lists the contents of the root directory of the install source with directories ending with a '/'. 2. Download the SLES10 DVD, copy all of it's contents to a directory and use that as the install source instead of what the installation server module created for you. 3. Upgrade the SLES10 Beta8 system to RC2 (or just the yast2-instserver module) and recreate the installation source. If your intent is to deploy from the SL10.0 box, #2 would probably be the easiest route. Thanks, Kevin

2 1

Auto identifying the sound card
by Simon Crute 30 May '06

30 May '06

Hi, I'm putting together an autoyast setup for sled10 (rc2 right now). I'm having problems getting the sound to be autoidentified. The section of my autoyast file is <sound> <autoinstall config:type="boolean">true</autoinstall> <configure_detected config:type="boolean">true</configure_detected> <volume_settings config:type="list"> <volume_entry> <Front config:type="integer">75</Front> <Headphone config:type="integer">75</Headphone> <Master config:type="integer">75</Master> </volume_entry> </volume_settings> </sound> but if I go into yast after the install, the sound is still showing up as undetected. After Looking at Frank van Tol's posting of 27/1/2006 I've started alsasound manually but still no joy. This is on a dell D610 machine. Does anyone have any clues ? -- Simon Crute IS&T Bracknell Novell UK Ltd

1 1