Sorry! Can't do this anymore: The underlying issue was indeed a hardware
problem (broken pin); however,
linux should have handled this more gracefully (and older kernels, maybe by
accident, did). Anyways, the
broken cable has long been replaced, so I could not reproduce the bug anymore.
Aside fr
Sorry, I forgot a very important question all this brings up ...
Given that I now have a kernel that boots (and leaving aside that fact that
hopefully my hardware
will be fixed soon, so that all of this is mute), how do I go about and build a
working boot medium (netboot) for
the install? For re
I have reported my problems also to linux-scsi, where Mark Bottomly very quickly
diagnosed that I must have a hardware problem (i.e., wide is not working,
although it
should), but that the newer kernels do not handle the situation correctly. I
post links
to the relevant thread(s) and attach the p
For what it's worth ... Since the vendor (transtec) mostly supports Suse, I
booted opensuse 10.2 into
rescue mode. This works, and all disks are recognized. There are fewer, yet
some messages ("transmission
error" etc) from the aic79xx drivers as for dapper. The driver claims to be at
version 3.
described, the machine is frozen solid at this point (it's
quite some time that I have seen such a kernel crash)
Please let me know what other information you need. The system at
the moment is again running dapper, but can be rebooted
at any point.
Sincerely,
Stefan Bo
