[SLE] SuSE 6.4, SCSI LUN probing, ...
I've stumbled across some issues wrt SuSE 6.3's install that I hope to see
fixed in 6.4, but I'm not on the beta list, so I hope this is the
appropriate forum.
- The stock SuSE kernel appears to be compiled with the "Probe all SCSI
LUNs" option enabled. The Yamaha CRW4416 CD-RW doesn't like this at all,
and YaST2 hangs while scanning the SCSI bus.
- YaST1 appears not to include a SCSI driver for the Initio 9100/UW (I'm
pretty sure 6.2 had them.)
- Since I also have IDE disks, I can skip SCSI detection and just install
with YaST1. However, if I then 'modprobe initio' after install, the driver
hangs (due to the LUN probing issue above.) Recompiling the kernel with
LUN probing disabled solves the problem nicely.
- RedHat 6.1's stock kernel has modular support for matroxfb, and their
6.2 beta has integrated support. Since 6.3's kernel supported vesafb, is
there any chance that matroxfb will be in 6.4? It seems fairly harmless
(besides extra kernel bloat, but that's a non-issue if it's compiled as
a module.)
Thanks, and keep up the good work ...
--
Ed McKenzie
Ed McKenzie wrote:
I've stumbled across some issues wrt SuSE 6.3's install that I hope to see fixed in 6.4, but I'm not on the beta list, so I hope this is the appropriate forum.
- The stock SuSE kernel appears to be compiled with the "Probe all SCSI LUNs" option enabled. The Yamaha CRW4416 CD-RW doesn't like this at all, and YaST2 hangs while scanning the SCSI bus.
- YaST1 appears not to include a SCSI driver for the Initio 9100/UW (I'm pretty sure 6.2 had them.)
- Since I also have IDE disks, I can skip SCSI detection and just install with YaST1. However, if I then 'modprobe initio' after install, the driver hangs (due to the LUN probing issue above.) Recompiling the kernel with LUN probing disabled solves the problem nicely.
- RedHat 6.1's stock kernel has modular support for matroxfb, and their 6.2 beta has integrated support. Since 6.3's kernel supported vesafb, is there any chance that matroxfb will be in 6.4? It seems fairly harmless (besides extra kernel bloat, but that's a non-issue if it's compiled as a module.)
Thanks, and keep up the good work ...
-- Ed McKenzie
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Ok, if we are going to ask for improvements: Why does yast1 keep asking for the floppy when booting from CD or DVD and attempting to load one of the modules of the module-diskette ? Could this be changed please. Tia, Erland. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Mon, 06 Mar 2000, Erland Moller wrote:
Ok, if we are going to ask for improvements:
Why does yast1 keep asking for the floppy when booting from CD or DVD and attempting to load one of the modules of the module-diskette ? Could this be changed please.
This only makes sense if you have to load modules not compiled into the kernel to make an installation. Even in this case, it should only ask for the floppy once. What is happening here? Why is this a problem? For reference, I'm willing to bet that YaST2 handles modules in a different way than YaST1/linuxrc did. Maybe one day soon (6.4 ?!?), YaST2 will have built-in disk partitioning, package selection, and work on all VESA 2.0 video cards, and this will be a non-issue. -- -=|JP|=- Jon Pennington | Atipa Linux Solutions -o) jpennington@atipa.com | Kansas City, MO /\\ 816-241-2641 x121 | http://www.atipa.com _\_V -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Jon Pennington wrote:
On Mon, 06 Mar 2000, Erland Moller wrote:
Ok, if we are going to ask for improvements:
Why does yast1 keep asking for the floppy when booting from CD or DVD and attempting to load one of the modules of the module-diskette ? Could this be changed please.
This only makes sense if you have to load modules not compiled into the kernel to make an installation. Even in this case, it should only ask for the floppy once. What is happening here? Why is this a problem?
For reference, I'm willing to bet that YaST2 handles modules in a different way than YaST1/linuxrc did. Maybe one day soon (6.4 ?!?), YaST2 will have built-in disk partitioning, package selection, and work on all VESA 2.0 video cards, and this will be a non-issue.
-- -=|JP|=- Jon Pennington | Atipa Linux Solutions -o) jpennington@atipa.com | Kansas City, MO /\\ 816-241-2641 x121 | http://www.atipa.com _\_V
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
I recently bought the DVD version. It comes without floppy's. My harddisk is on a SCSI interface that's not on the standard boot-disk or boot-disk image of which the dvd boots. When i ask to load other modules to get my SCSI-if recognised it ask's for the "module floppy". Now i have two problems: 1. i didn't write the module-image (which, by the way, is corrupted on my DVD version!) to a floppy 2. i don't have a floppy in my PC anymore, why should i put one in, i don't use it anymore. So i have the problem as wel with a new install as with an upgrade. I hope you do understand my problem now ? Erland. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Hi, On Mon, Mar 06 2000 at 22:38 -0500, Ed McKenzie wrote:
I've stumbled across some issues wrt SuSE 6.3's install that I hope to see fixed in 6.4, but I'm not on the beta list, so I hope this is the appropriate forum.
- The stock SuSE kernel appears to be compiled with the "Probe all SCSI LUNs" option enabled. The Yamaha CRW4416 CD-RW doesn't like this at all, and YaST2 hangs while scanning the SCSI bus.
If you get a chance to enter something at a lilo prompt during install (don't know, I've never used YaST 2), you can try to pass the max_scsi_luns option to the kernel <kernel image> max_scsi_luns=1 Ciao, Stefan -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (4)
-
ed＠eem12.resnet.cornell.edu -
erland＠pandora.be -
jpennington＠atipa.com -
stefan.troeger＠wirtschaft.tu-chemnitz.de