>Hello,
>Does anynone know why I might receive the following error when trying to
add
>an additional
>dasd vol to my system ? ('cause you're a dolt.. is not a valid answer ;)># insmod dasd dasd=33a2 >insmod: dasd: no module by that name found >I have added volumes before, but that was during the initial install phase. A block device driver can either be statically linked with the kernel or built as a separately loadable module. You choose how you wish the module to be linked with the kernel when you configure the kernel prior to building it. So, if insmod cant find a module then either it wasn't built or else it is already linked in with the kernel. Since your system is up and running then this driver must have been linked into the kernel. The only way I know how to specify dasd to the block device driver is via the parm file or in your zipl.conf file. BTW, the statement you show above is using insmod to set a module variable called dasd to a value of 33a2. I dont know how this would cause the dasd driver to do a rediscover of disks but then I am kinda new to 390. -Don
