I would like to add the following modules to modules.conf so that they are available from boot up: advansys.o (for my scsi cdwriter and hard drive) sg.o (for my ATAPI cdwriter, so I can use ide-scsi) ppa (for my old parallel port zip drive) Can somebody please let me know what I need to put into modules.conf. Please "explain like your talking to a four year old" to quote a famous saying. Thanks Phil
On Fri, 2002-04-19 at 14:27, Philip Burness wrote:
I would like to add the following modules to modules.conf so that they are available from boot up: advansys.o (for my scsi cdwriter and hard drive) sg.o (for my ATAPI cdwriter, so I can use ide-scsi) ppa (for my old parallel port zip drive)
Can somebody please let me know what I need to put into modules.conf.
Well, with SuSE especially the newer versions 7.2 ?? onwards, only "few flags of caution". I'm going to assume that you're usung a normal and default SuSE kernel and config, as most modules settings in /etc/modules are already on and ready. If you're booting from the scsi hd, then you'll have to include the advansys and ide-scsi modules amongst those needed immediately at boot-up. This is achieved by the utility command called "mk_initrd" and easily manipulated by using the YaST , this way: As root, in a terminal big enough or in console mode..... type without quotes... "yast" go to........ System Admin go to........ Change config file OK, now this THE zone for configuring most things SuSE. Now press F4 and search for initrd. Hit Return key. There you are. Press F3 and now include your needed modules i.e. advansys and ide-scsi to the end of the list, if any exist. Modules here are essential to a bootable Linux box. F10 to exit that segment. Now scroll back up to.... Kernel/Boot config Open up... Lilo config Edit here in the space given ...hdX=ide-scsi Of course [X] for you, has to be ide channel which holds the cdwriter. PLEASE note 1st IDE channel master => hd[a] slave => hd[b] 2nd IDE channel master => hd[c] slave => hd[d] Apply as needed if you to grab hold of the cdwriter for the scsi emulation. You should now cycle through with the RETURN key to Continue. Then check carefully the confirmation dialogue, in case you have IDE and SCSI disks onboard. Choose which one, you'll be booting with. RETURN. Use the Escape key to roll back down to the main YaST page. With the down arrow key ...go to ...Exit YaST. RETURN. That's it !! Let SuSEconfig run and do its stuff. As for the ppa module, I'm not so sure, but you can try editing /etc/init.d/local.boot to include the lines below #(for my old parallel port zip drive) modprobe -k ppa Then try running /sbin/SuSEconfig again. On your next reboot, I hope all's good and well. That's all from me Anyone else, is welcome to correct any mistakes. Let's all help Philip -- Kemdi IN_SuSE_d Since 5.2 123792 of counter.li.org ICQ:112290572
Teriffic instructions thanks. Certainly the advansys has worked, and the ppa, however, I am not sure of the ide-scsi. This is another silly question but what will it's device name now be? if it was /dev/hdb what will it become if using it as an ide-scsi device? Phil
On Fri, 2002-04-19 at 14:27, Philip Burness wrote:
I would like to add the following modules to modules.conf so that they are available from boot up: advansys.o (for my scsi cdwriter and hard drive) sg.o (for my ATAPI cdwriter, so I can use ide-scsi) ppa (for my old parallel port zip drive)
Can somebody please let me know what I need to put into modules.conf.
Well, with SuSE especially the newer versions 7.2 ?? onwards, only "few flags of caution". I'm going to assume that you're usung a normal and default SuSE kernel and config, as most modules settings in /etc/modules are already on and ready.
If you're booting from the scsi hd, then you'll have to include the advansys and ide-scsi modules amongst those needed immediately at boot-up.
This is achieved by the utility command called "mk_initrd" and easily manipulated by using the YaST , this way:
As root, in a terminal big enough or in console mode.....
type without quotes... "yast" go to........ System Admin go to........ Change config file
OK, now this THE zone for configuring most things SuSE. Now press F4 and search for initrd. Hit Return key. There you are.
Press F3 and now include your needed modules i.e. advansys and ide-scsi to the end of the list, if any exist. Modules here are essential to a bootable Linux box. F10 to exit that segment.
Now scroll back up to.... Kernel/Boot config Open up... Lilo config
Edit here in the space given ...hdX=ide-scsi Of course [X] for you, has to be ide channel which holds the cdwriter.
PLEASE note 1st IDE channel master => hd[a] slave => hd[b] 2nd IDE channel master => hd[c] slave => hd[d]
Apply as needed if you to grab hold of the cdwriter for the scsi emulation.
You should now cycle through with the RETURN key to Continue. Then check carefully the confirmation dialogue, in case you have IDE and SCSI disks onboard. Choose which one, you'll be booting with. RETURN.
Use the Escape key to roll back down to the main YaST page.
With the down arrow key ...go to ...Exit YaST. RETURN.
That's it !! Let SuSEconfig run and do its stuff.
As for the ppa module, I'm not so sure, but you can try editing
/etc/init.d/local.boot to include the lines below
#(for my old parallel port zip drive) modprobe -k ppa
Then try running /sbin/SuSEconfig again.
On your next reboot, I hope all's good and well. That's all from me
Anyone else, is welcome to correct any mistakes. Let's all help Philip
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Philip Burness (föstudagur 19. apríl 2002 22:10)
Teriffic instructions thanks. Certainly the advansys has worked, and the ppa, however, I am not sure of the ide-scsi. This is another silly question but what will it's device name now be?
if it was /dev/hdb what will it become if using it as an ide-scsi device?
Depending on the type of device, and wether you already have a scsi controller, it may become: CDROM: /dev/sr0 [ or sr1 or... ] DISK: /dev/sda [ or sdb or sdc or... ] TAPE: /dev/st0 [ or st1 or... ] Optical Drive: /dev/sda etc and so on and so forth... - -tosi
Phil
On Fri, 2002-04-19 at 14:27, Philip Burness wrote:
I would like to add the following modules to modules.conf so that they are available from boot up: advansys.o (for my scsi cdwriter and hard drive) sg.o (for my ATAPI cdwriter, so I can use ide-scsi) ppa (for my old parallel port zip drive)
Can somebody please let me know what I need to put into modules.conf.
Well, with SuSE especially the newer versions 7.2 ?? onwards, only "few flags of caution". I'm going to assume that you're usung a normal and default SuSE kernel and config, as most modules settings in /etc/modules are already on and ready.
If you're booting from the scsi hd, then you'll have to include the advansys and ide-scsi modules amongst those needed immediately at boot-up.
This is achieved by the utility command called "mk_initrd" and easily manipulated by using the YaST , this way:
As root, in a terminal big enough or in console mode.....
type without quotes... "yast" go to........ System Admin go to........ Change config file
OK, now this THE zone for configuring most things SuSE. Now press F4 and search for initrd. Hit Return key. There you are.
Press F3 and now include your needed modules i.e. advansys and ide-scsi to the end of the list, if any exist. Modules here are essential to a bootable Linux box. F10 to exit that segment.
Now scroll back up to.... Kernel/Boot config Open up... Lilo config
Edit here in the space given ...hdX=ide-scsi Of course [X] for you, has to be ide channel which holds the cdwriter.
PLEASE note 1st IDE channel master => hd[a] slave => hd[b] 2nd IDE channel master => hd[c] slave => hd[d]
Apply as needed if you to grab hold of the cdwriter for the scsi emulation.
You should now cycle through with the RETURN key to Continue. Then check carefully the confirmation dialogue, in case you have IDE and SCSI disks onboard. Choose which one, you'll be booting with. RETURN.
Use the Escape key to roll back down to the main YaST page.
With the down arrow key ...go to ...Exit YaST. RETURN.
That's it !! Let SuSEconfig run and do its stuff.
As for the ppa module, I'm not so sure, but you can try editing
/etc/init.d/local.boot to include the lines below
#(for my old parallel port zip drive) modprobe -k ppa
Then try running /sbin/SuSEconfig again.
On your next reboot, I hope all's good and well. That's all from me
Anyone else, is welcome to correct any mistakes. Let's all help Philip
- -- This mail is sent using KMail and Linux. Thus it is 100% guaranteed virus free. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8wJtO6mRH+PEpr2YRAiXDAJ9eV6yd5RnqM15GwCD6dmy7WpuV6QCgkMn9 XIwCYcCBcWiZXcyKBqSYeWU= =W+cP -----END PGP SIGNATURE-----
On Saturday 20 April 2002 00:33, Tor Sigurdsson wrote:
Philip Burness (föstudagur 19. apríl 2002 22:10)
Teriffic instructions thanks. Certainly the advansys has worked, and the ppa, however, I am not sure of the ide-scsi. This is another silly question but what will it's device name now be?
if it was /dev/hdb what will it become if using it as an ide-scsi device?
Depending on the type of device, and wether you already have a scsi controller, it may become:
CDROM: /dev/sr0 [ or sr1 or... ] DISK: /dev/sda [ or sdb or sdc or... ] TAPE: /dev/st0 [ or st1 or... ] Optical Drive: /dev/sda etc
When the driver module is loaded there should be text in /var/log/messages saying which device was allocated to it. Also note that for some applications, such as cd writing, it's the generic scsi interface (/dev/sg*) that's used. Anders
participants (4)
-
Anders Johansson -
Philip Burness -
Tor Sigurdsson -
Uzo Kemdi Anyamele