Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have not been able to change the tag queue length of my
aic7xxx controller for target 0.
I've added several versions of this line to /etc/modules.conf
[root@proxy11 root]# cat /etc/modules.conf
alias parport_lowlevel parport_pc
alias scsi_hostadapter aic7xxx
add options aic7xxx "aic7xxx=tag_info:{{8,8,8,8}}"
alias sound-slot-0 es1371
post-install sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -L >/dev/null 2>&1 || :
pre-remove sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -S >/dev/null 2>&1 || :
alias usb-controller usb-uhci
alias eth0 dmfe
[root@proxy11 root]# set -o vi
[root@proxy11 root]# mkinitrd -f /boot/initrd-2.4.18-3-jgm.img 2.4.18-3
[root@proxy11 root]# cat /etc/lilo.conf.ana*
prompt
timeout=50
default=linux
boot=/dev/sda
map=/boot/map
install=/boot/boot.b
message=/boot/message
linear
I have been able to create initrd-xx.img files that hang and
I've seen the "Command Openings" move between 127 and 253
but never have I achieved a queue depth of 8.
Distribution: openSUSE, Raspbian, Slackware. Previous: MacOS, Red Hat, Coherent, Consensys SVR4.2, Tru64, Solaris
Posts: 2,818
Rep:
Re: aic7xxx tagged queue option.
Quote:
Originally posted by jgmarce I have not been able to change the tag queue length of my
aic7xxx controller for target 0.
I've added several versions of this line to /etc/modules.conf
[root@proxy11 root]# cat /etc/modules.conf
alias parport_lowlevel parport_pc
alias scsi_hostadapter aic7xxx
add options aic7xxx "aic7xxx=tag_info:{{8,8,8,8}}"
Take look at the file ``/usr/src/linux-2.4/drivers/scsi/README.aic7xxx''. There seems to be something about commas in the command string that affects the way module options need to be specified (to make insmod happy). If I read the caveat correctly, it looks like you might have to enter the options strings as:
"aic7xxx=tag_info:{{8.8.8.8}}"
Looks weird to me but might be worth a try. I'd have a boot floppy or rescue CD available before trying this.
Retrieving list of all available packages...
########################################
Removing installed packages from list of updates...
########################################
Removing packages marked to skip from list...
########################################
Getting headers for available packages...
There was a fatal error communicating with the server. The message was:
Connection aborted by the user
[root@proxy11 root]# tail /var/log/messages
Feb 24 10:44:32 proxy11 -- root[1071]: ROOT LOGIN ON tty1
Feb 24 10:45:08 proxy11 sshd(pam_unix)[1124]: session opened for user root by (uid=0)
Feb 24 10:46:31 proxy11 kernel: scsi0: PCI error Interrupt at seqaddr = 0x7
Feb 24 10:46:31 proxy11 kernel: scsi0: Data Parity Error Detected during address or write data phase
Feb 24 10:46:32 proxy11 kernel: scsi0: PCI error Interrupt at seqaddr = 0x8
Feb 24 10:46:32 proxy11 kernel: scsi0: Data Parity Error Detected during address or write data phase
Feb 24 10:46:32 proxy11 kernel: scsi0: PCI error Interrupt at seqaddr = 0x9
Feb 24 10:46:32 proxy11 kernel: scsi0: Data Parity Error Detected during address or write data phase
Feb 24 10:46:32 proxy11 kernel: scsi0: PCI error Interrupt at seqaddr = 0x7
Feb 24 10:46:32 proxy11 kernel: scsi0: Data Parity Error Detected during address or write data phase
[root@proxy11 root]#
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.