Hello?
> Back to the original topic ... do you have any news with regard to putting
> the code back into the sym8xx driver that reads the user configured
> channel/device negotiation settings (transfer speed and width limits,
> timeouts, disconnect, etc. etc.) from the EEPROM? This is really causi
Hi Matthew!
I see ... so there is an alternate method for the kernel to find its system
volume by not using the dynamically built /dev/sdX names? I'll dig into that,
thanks for the pointer!
Back to the original topic ... do you have any news with regard to putting the
code back into the sym8xx
On Sat, Apr 09, 2005 at 12:57:22AM +0200, Peter Missel wrote:
> It also makes the driver ignore the adapter ordering in multiple-channel
> setups. This machine here has an LSI 21002, where the LVD channel is on
> device function 1 and the UW channel is on 0. Naturally the user will set the
> ada
Help! Help! I'm being ignored!
I just found out that this problem (the driver no longer reading the user's
adjustments from the SCSI BIOS EEPROM configuration data) not only removes
the possibility to limit transfer speed and width for single devices or
entire channels.
It also makes the drive
Greetings!
Now that producing another pair of coasters reminded me that this here system
has a problem on SCSI branch 1, I'd like to inquire about the current state
of affairs regarding this topic. (Also, I've encountered another machine I'd
like to upgrade to a newer Linux kernel but can't sin
5 matches
Mail list logo
