It's suppossed to. What you do, is start the item in #2, then go do item #1 on another VT and that will save the log messages somewhere so that they can be sent to me. The only thing you have to do is make sure that the output of #2 is directed to a file on your IDE drive instead of a SCSI drive. Now, once you have #2 started, switch to another VT and start #1. Also have another shell open on a third VT, and after about 20 seconds, switch to it and issue the command "shutdown -nr now" to force a reboot and close out

FWD: to [SuSE] news groups Hello world, SuSE, Hello Doug Ledford, the

log file. In case you're wondering what I'm talking about by VTs, when you hit <ALT-F1) that takes you to VT #1, <ALT-F2> goes to VT #2, etc. You need to be logged in on three of them to do everything I've talked about here.

No go:tty1 : cd /lib/2.0.33/modules/scsi #insmod aic7xxx.o tty2 : tail -f /proc/kmsg > /tmp/kernel.output 2>&1 tty3 : shutdown -nr now after 30seconds This will produce a file named kernel.output in /tmp/ BUT it has nothing in it. So I can't give you want I need to give you. :( something wrong here? tty1 is virtual terminal 1 and so on to 6 (7 is reserved for X)

If you don't want to have to mess around with compiling new kernels all

time, there is a disk image on my ftp site (ftp.dialnet.net) under /pub/linux/aic7xxx/boot_disks/5.0.7/SuSE that is an SuSE provided boot disk of my latest code. It may help. If nothing else, with it you can boot from floppy instead of having to recompile your kernel all the time, and you can hit <ALT-F4) to see the messages the driver prints out. Additionally,

the the

5.0.7 driver made a change that might help you out (it disables tagged queueing by default, which may help).

:(This bootdisk.img does not work. Actualy it gives me the same message as when doing a normal aic7xxx kernel direct support normal boot (lilo) the looping thing. The only bootdisk that is working is the orignal suse5.1 disk (distro boot) and I think it is *386 speed compiled* and *4.1.1 version of aic7xxx* Now the thing is with the '*' notes of intrest. Now my kernel is compiled with 'pentium speed' now if the new bootdisk.img is compiled with 'pentium speed' this might be the reason, tho I don't know if it is. I gona write to SuSE news groups asking if the new bootdisk.img is compiled with 'pentium speed' Ehh.. Ok with that (prob I am not right) but I might be right on why my kernel is failing, as I am compiled with 'pentium speed' and I will be trying after I write this letter, and after downloading a 6meg kernel ver 7, I will compile it with '386 speed' note* I do not have an intel processor, I do have an AMD K6 233, this might make a difference here. I guess I go try, this is an update of what I am doing. Steven Udell hettar@teleport.com I wonder why the new bootdisk.img is not working like the orignal bootdisk.img (distro) I mean I did everything I do on the (distros,old) boot disk that I do on the new one. It LOOPS with the new one. -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e