Integrating scsi modul in autoyast installation
Hello guys, maybe someone of you tried the same, like I am doing now since 1 week. I have a server with a scsi controller, that is not supported by the standard kernel of suse. If I a the modul manual at the installation everything works. But I want to use autoyast. The FAQ of autoyast points to http://ftp.softnet.tuc.gr/pub/linux/suse/people/hvogel/Update-Media-HOWTO/Up... for this. So I created the directory linux/suse/i386-sles8 with the subdirectories install and module in my HTTP-Repository and also at my bootcd (SLES8 SP3), but nothing works, the module could not be loaded. Any hints or suggestions how to deal with this problem??? thanks ___________________________________________________________ Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de
On Tue, 24 May 2005, FITZ MAILING wrote:
Hello guys,
maybe someone of you tried the same, like I am doing now since 1 week.
I have a server with a scsi controller, that is not supported by the standard kernel of suse. If I a the modul manual at the installation everything works.
But I want to use autoyast. The FAQ of autoyast points to http://ftp.softnet.tuc.gr/pub/linux/suse/people/hvogel/Update-Media-HOWTO/Up... for this.
So I created the directory linux/suse/i386-sles8 with the subdirectories install and module in my HTTP-Repository and also at my bootcd (SLES8 SP3), but nothing works, the module could not be loaded.
It will not work via http unless you pack it into a 'driverupdate' file. It does not work via CD as it won't look at the CD for network installations anyway. Steffen
This was the only list that mentioned YAST. I hope this is OK. When I log into root from the login dialog, or use 'switch user', YAST comes up, when I close YAST I get thrown out of root back to where I came from. When I log into root using a terminal program all is ok. This came about when I change my network card to get a dynamic IP address. I changed back to static but that didn't fix it. ifconfig gives the static IP address so the change back works. It has happened to two systems, the first was dealt with by killing the firewall. If you switch the firewall off using YAST it doesn't deal with the problem. I suspect the firewall has got itself in a knot and the result is YAST Has anyone got any ideas? Regards Charles Esson
participants (3)
-
Charles Esson -
FITZ MAILING -
Steffen Winterfeldt