First, make sure the module exists: find /lib/modules/`uname -r`/ -name "*dasd*"
If it does, then "depmod -a" followed by "insmod" I suspect the modules are not where you expect them to be, and you'll need to find out where they really are located. Then issue the insmod command with the fully qualified name. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Massimiliano Belardi Sent: Wednesday, December 07, 2005 6:03 AM To: [email protected] Subject: Recovery from Rescue Disk Guys, I'm trying to recovery my Linux System in an LPAR environment, using the rescue disk via HMC. After configred the network, I take an SSH connection in order to configure the kernel to get the new UCB Dasds. After the login... as documented, I try to get the new dasds via: insmod dasd_mod dasd=5000,5001 But system is not able to work with this command... The result is: "Can't read dasd_mod" What's wrong??? I've tryied all the possibile solution.... insmod dasd dasd=5000,5001 insmod dasd dasd_mod=5000,5001 insmod dasd_mod dasd=0.0.5000,0.0.5001 But the result is the same... Anyone experienced this problem? Have a nice day Max ---------------------------------------------------------------------- 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
