Re: After uprade to buster: QEMU doesn't support -drive if=scsi

Hello, I have never used SCSI hardware nor SCSI emulation but there is an Oracle doc here that seems to separate options between -device and - drive lines: https://blogs.oracle.com/linux/post/how-to-emulate-block-devices-with-qemu

After uprade to buster: QEMU doesn't support -drive if=scsi

After uprading from stretch to buster on my server (x86_64), I cannot start one of my VMs anymore. The guest is a *very* old Linux (non Debian, i686, kernel 2.4, GRUB 1.99) and uses the Symbios Logic sym53c8xx_2 SCSI driver in its init-ramdisk to mount the root file system and another virtual

Re: linux 4.19 scsi-mq default?

Hi. On Sun, Aug 26, 2018 at 07:47:54PM -0400, Boyan Penkov wrote: > Hello folks, > > Likely not the exact right list to ask, but likely someone here knows — did > scsi-mq by default make it into linux 4.19? > > http://lkml.iu.edu/hypermail/linux/kernel/1807.0/02224

Re: linux 4.19 scsi-mq default?

Hi Boyan, Am Montag, 27. August 2018 schrieb Boyan Penkov: > Hello folks, > > Likely not the exact right list to ask, but likely someone here knows — did > scsi-mq by default make it into linux 4.19? > > http://lkml.iu.edu/hypermail/linux/kernel/1807.0/02224.html > <http

linux 4.19 scsi-mq default?

Hello folks, Likely not the exact right list to ask, but likely someone here knows — did scsi-mq by default make it into linux 4.19? http://lkml.iu.edu/hypermail/linux/kernel/1807.0/02224.html <http://lkml.iu.edu/hypermail/linux/kernel/1807.0/02224.html> Cheers! -- Boyan

SCSI rescan (Mint 17.3)

switched on: echo rescan >/proc/scsi/cciss/6 According to things I have read, the following should work with a modern system: echo 1 >/sys/class/scsi_host/host0/scan But all I get is an error message if I try that. Does anyone have an idea of where I'm going wrong? Thanks! Paul.

Re: wodim "Cannot open SCSI driver!"

Gene Heskett writes: > Point being Lisi, that its without a doubt of > Chinese manufacture and the price on your store > shelf should be comparable +- shipping and of course > any resttrictive tarrifs your government may have in > place one way or the other. Some call it a

Re: wodim "Cannot open SCSI driver!"

On Monday 25 January 2016 05:13:23 Lisi Reisz wrote: > On Monday 25 January 2016 00:45:58 Gene Heskett wrote: > > I bought the last burner I have, about 3 or 4 years ago at wallmart, > > everything but Blue Ray, for about a $25 dollar bill. Internal, sata > > interface. > > Don't gloat, Gene.

Re: wodim "Cannot open SCSI driver!"

Hi, Emanuel Berg wrote: > Sense Code: 0x3A Qual 0x00 (medium not present) Fru 0x0 That's another member of the family of medium-not-present messages: 2 3A 00 MEDIUM NOT PRESENT 2 3A 01 MEDIUM NOT PRESENT TRAY CLOSED 2 3A 02 MEDIUM NOT PRESENT TRAY OPEN 2 3A 03 MEDIUM NOT PRESENT

Re: wodim "Cannot open SCSI driver!"

On Monday 25 January 2016 00:45:58 Gene Heskett wrote: > I bought the last burner I have, about 3 or 4 years ago at wallmart, > everything but Blue Ray, for about a $25 dollar bill. Internal, sata > interface. Don't gloat, Gene. ;-)* Lisi *Tech prices in the USA are very low compared with many

Re: wodim "Cannot open SCSI driver!"

Hi, > I have suspected a hardware error as well. Is there > any way to confirm this? You could try whether it can recognize any kind of other medium: wodim -v dev=/dev/sr0 -toc If i run this on an empty drive, i get ... Current: 0x (Reserved/Unknown) ... Sense Code: 0x3A Qual

Re: wodim "Cannot open SCSI driver!"

t 3 or 4 years ago at wallmart, everything but Blue Ray, for about a $25 dollar bill. Internal, sata interface. It has to date burned 2 or 3 100 count spindles of cd's and dvd's, and has never hicupped unless the disk was phony. Some brands have a high phony percentage. From an lshw repor

Re: wodim "Cannot open SCSI driver!"

"Thomas Schmitt" writes: > wodim -v dev=/dev/sr0 -toc > > If i run this on an empty drive, i get > > ... Current: 0x (Reserved/Unknown) ... Sense > Code: 0x3A Qual 0x01 (medium not present - tray > closed) Fru 0x0 ... wodim: No disk / Wrong disk! I get the same, only:

Re: wodim "Cannot open SCSI driver!"

Hi, Emanuel Berg wrote: > http://user.it.uu.se/~embe8573/wodim_log where i read > Executing 'test unit ready' command on Bus 1 Target 0, Lun 0 timeout 200s > CDB: 00 00 00 00 00 00 > Errno: 5 (Input/output error), test unit ready scsi sendcmd: no error > CDB: 00 00 00 00 00 0

Re: wodim "Cannot open SCSI driver!"

"Thomas Schmitt" writes: > Bad news is that you will probably have to get > a new burner. I have suspected a hardware error as well. Is there any way to confirm this? Strange thing tho I recently burned an ISO DVD movie to a DVD with no problem. I'm used to things in the

wodim "Cannot open SCSI driver!"

Hi, Emanuel Berg wrote: > When I try to burn with wodim, it says > Errno: 5 (Input/output error), test unit ready >scsi sendcmd: no error We will have to dig deeper to untangle this message. But first i need to send a few complaints to heaven: > $ wodim --devices > I get &q

Re: wodim "Cannot open SCSI driver!"

Hi, Emanuel Berg wrote: > > $ wodim --devices > > I get "Cannot open SCSI driver!" strace reveils that this confusing message comes from the total lack of /dev/scd* and /dev/hd* device files or links. I can fix it on my Jessie by for i in 0 1 2 3 4 5 do test -

wodim "Cannot open SCSI driver!"

When I try to burn with wodim, it says Errno: 5 (Input/output error), test unit ready scsi sendcmd: no error and $ wodim --devices I get "Cannot open SCSI driver!" Ideas? -- underground experts united http://user.it.uu.se/~embe8573

Re: wodim "Cannot open SCSI driver!"

"Thomas Schmitt" writes: > wodim -V ...your.wodim.options... 2>&1 | tee -i > /tmp/wodim_log http://user.it.uu.se/~embe8573/wodim_log > What wodim options did you use, exactly ? zsh: http://user.it.uu.se/~embe8573/conf/.zsh/dvd burn-iso-to-cd () { local

Re: wodim "Cannot open SCSI driver!"

Emanuel Berg writes: > The disc is a CD-R I have tried two CD-Rs brand new from the (same) box - same thing. -- underground experts united http://user.it.uu.se/~embe8573

Cannot access SCSI device

Hi all, at the oment, I'm struggling with a server containing a SCSI card (Adaptec ASC-29320ALP) which is connected to an easyRAID. On the easyRAID, I've created a big RAID6 array which is divided into two slices. Unformntunately, I didn't succeed in accessing those devices: # gdisk /dev

Re: Attached SCSI removable disk niet in /proc/partitions

:02:28 nero kernel: [3500671.803243] sd 20:0:0:1: [sdc] Attached SCSI removable disk Nov 22 10:02:28 nero kernel: [3500671.803871] sd 20:0:0:0: [sdb] Attached SCSI removable disk maar in /proc/partitions zie ik die disk niet terug. Bij mijn telefoon verschijnt bij het inpluggen

Attached SCSI removable disk niet in /proc/partitions

Hoi, Een Android device via USB aangesloten. In /var/log/syslog komt o.a. Nov 22 10:02:28 nero kernel: [3500671.803243] sd 20:0:0:1: [sdc] Attached SCSI removable disk Nov 22 10:02:28 nero kernel: [3500671.803871] sd 20:0:0:0: [sdb] Attached SCSI removable disk maar in /proc/partitions zie

Re: Attached SCSI removable disk niet in /proc/partitions

On Sat, 2014-11-22 at 10:12 +0100, Geert Stappers wrote: Hoi, Een Android device via USB aangesloten. In /var/log/syslog komt o.a. Nov 22 10:02:28 nero kernel: [3500671.803243] sd 20:0:0:1: [sdc] Attached SCSI removable disk Nov 22 10:02:28 nero kernel: [3500671.803871] sd 20:0:0:0: [sdb

Re: Attached SCSI removable disk niet in /proc/partitions

On Sat, Nov 22, 2014 at 10:12:43AM +0100, Geert Stappers wrote: Hoi, Een Android device via USB aangesloten. In /var/log/syslog komt o.a. Nov 22 10:02:28 nero kernel: [3500671.803243] sd 20:0:0:1: [sdc] Attached SCSI removable disk Nov 22 10:02:28 nero kernel: [3500671.803871] sd 20:0

Re: Attached SCSI removable disk niet in /proc/partitions

On Sat, Nov 22, 2014 at 12:28:31PM +0100, Huub Reuver wrote: On Sat, Nov 22, 2014 at 10:12:43AM +0100, Geert Stappers wrote: Hoi, Een Android device via USB aangesloten. In /var/log/syslog komt o.a. Nov 22 10:02:28 nero kernel: [3500671.803243] sd 20:0:0:1: [sdc] Attached SCSI

Re: Attached SCSI removable disk niet in /proc/partitions

On Saturday 22 November 2014 12:28:31 Huub Reuver wrote: Beter is dan via een netwerkschijf/wifi bestanden over te zetten. (ES file explorer kan dat, maar heeft root access nodig) ES File Explorer heeft geen root access nodig, althans ik gebruik het en heb mijn android device (nog) niet

Re: Attached SCSI removable disk niet in /proc/partitions

Diederik de Haas: Huub Reuver: Beter is dan via een netwerkschijf/wifi bestanden over te zetten. (ES file explorer kan dat, maar heeft root access nodig) ES File Explorer heeft geen root access nodig, althans ik gebruik het en heb mijn android device (nog) niet ge-root. Ga in ES File

SCSI driver for use with Jessie: which one?

I found today that I don't have a scsi driver on my Jessie install. I search for 'scsi' in aptitude and see several competing packages. Which one is most likely to enable burning a new debian netinst CD today or tomorrow? I need to reinstall Jessie on a different host before this one crashes. I'm

Re: SCSI driver for use with Jessie: which one?

On 26/10/14 09:33 PM, Paul E Condon wrote: I found today that I don't have a scsi driver on my Jessie install. I search for 'scsi' in aptitude and see several competing packages. Which one is most likely to enable burning a new debian netinst CD today or tomorrow? I need to reinstall Jessie

Re: SCSI driver for use with Jessie: which one? [Solved]

On 20141026_2314-0400, Gary Dale wrote: On 26/10/14 09:33 PM, Paul E Condon wrote: I found today that I don't have a scsi driver on my Jessie install. I search for 'scsi' in aptitude and see several competing packages. Which one is most likely to enable burning a new debian netinst CD today

Error: SCSI subsystem not active

salut la liste, j'ai un souci avec une VM wheezy (3.2.0-4-amd64 #1 SMP Debian 3.2.46-1+deb7u1 x86_64) sous wmware. toutes les autres VM marchent bien, mais celle-ci n'a pas son sous-système activé, en effet, /proc/scsi n'existe pas. et j'ai un script de détection de disque scsi qui detecte

[SOLVED]Re: Error: SCSI subsystem not active

Le 13/09/2013 16:07, admini a écrit : salut la liste, j'ai un souci avec une VM wheezy (3.2.0-4-amd64 #1 SMP Debian 3.2.46-1+deb7u1 x86_64) sous wmware. toutes les autres VM marchent bien, mais celle-ci n'a pas son sous-système activé, en effet, /proc/scsi n'existe pas. et j'ai un script de

Re: clean hd-media install onto hard drive partition of old SCSI box

Hi, Chris, You do realise that posts on this mailing list are archived at various places around the Internet, don't you? Yes, I realize posting to this mailing list exposes the e-mail address I have used. The statement, which my editor automatically adds to all of my emails, indicates my

clean hd-media install onto hard drive partition of old SCSI box

Hello, I want to install a recent Debian distribution on a clean partition of a stand-alone SCSI box which runs multiple legacy OSes, including Woody. I did not upgrade Woody because driver support for my Initio SCSI host adapter was problematic with supplied 2.6 kernels for several years

Re: clean hd-media install onto hard drive partition of old SCSI box

On Wed 17 Jul 2013 at 15:18:27 -0400, sar0...@nc.rr.com wrote: I want to install a recent Debian distribution on a clean partition of a stand-alone SCSI box which runs multiple legacy OSes, including Woody. I did not upgrade Woody because driver support for my Initio SCSI host adapter

Re: clean hd-media install onto hard drive partition of old SCSI box

install which was painful in the past on this machine. I prefer to take my headaches one at a time - base install (SCSI driver), X install (video config) then ethernet access (past problems getting=20 driver settings to 'stick'). I wrote: I have initialized a 3.3 MB ext3 root partition

Re: clean hd-media install onto hard drive partition of old SCSI box

On Wed 17 Jul 2013 at 18:12:49 -0400, sar0...@nc.rr.com wrote: Thanks for the response (and sorry about replying to your email address rather than the list) Not a problem. I read the list and reply through it and never get to see mails sent directly to me via that address. Which does not mean

Re: Reescaneo de dispositivos scsi sin reiniciar

reiniciar. He probado estas opciones: http://www.cyberciti.biz/tips/vmware-add-a-new-hard-disk-without-rebooting-guest.html y en algunas máquinas me funciona y en otras no. También he probado con este script: http://www.garloff.de/kurt/linux/#rescan-scsi y me pasa

Re: Reescaneo de dispositivos scsi sin reiniciar

no. También he probado con este script: http://www.garloff.de/kurt/linux/#rescan-scsi y me pasa igual, en algunas si y en otras no. Lo único que me ha funcionado en todas es el reinicio. http://www.cyberciti.biz/tips/vmware-add-a-new-hard-disk-without-rebooting-guest.html

Re: Reescaneo de dispositivos scsi sin reiniciar

On Thursday 02 August 2012 10:22:30 Esteban Torres Rodríguez wrote: Salida del fdisk después de seguir tus mismos pasos: fdisk /dev/sdb No se puede leer /dev/sdb Nada que me toca quedarme a horas que nadie curra y reiniciar el server. Esta vida del informático no está pagada

Re: Reescaneo de dispositivos scsi sin reiniciar

El día 2 de agosto de 2012 10:29, Marc Olive marc.ol...@blauadvisors.com escribió: On Thursday 02 August 2012 10:22:30 Esteban Torres Rodríguez wrote: Salida del fdisk después de seguir tus mismos pasos: fdisk /dev/sdb No se puede leer /dev/sdb Nada que me toca quedarme a horas que

Reescaneo de dispositivos scsi sin reiniciar

-a-new-hard-disk-without-rebooting-guest.html y en algunas máquinas me funciona y en otras no. También he probado con este script: http://www.garloff.de/kurt/linux/#rescan-scsi y me pasa igual, en algunas si y en otras no. Lo único que me ha funcionado en todas es el reinicio. Por que

Re: Reescaneo de dispositivos scsi sin reiniciar

servidores, excepto reiniciar. He probado estas opciones: http://www.cyberciti.biz/tips/vmware-add-a-new-hard-disk-without-rebooting-guest.html y en algunas máquinas me funciona y en otras no. También he probado con este script: http://www.garloff.de/kurt/linux/#rescan-scsi y me pasa igual

Re: Reescaneo de dispositivos scsi sin reiniciar

probado con este script: http://www.garloff.de/kurt/linux/#rescan-scsi y me pasa igual, en algunas si y en otras no. Lo único que me ha funcionado en todas es el reinicio. http://www.cyberciti.biz/tips/vmware-add-a-new-hard-disk-without-rebooting-guest.html Por que? Perdón, se me

Re: Reescaneo de dispositivos scsi sin reiniciar

-a-new-hard-disk-without-rebooting-guest.html y en algunas máquinas me funciona y en otras no. También he probado con este script: http://www.garloff.de/kurt/linux/#rescan-scsi y me pasa igual, en algunas si y en otras no. Lo único que me ha funcionado en todas es el reinicio

Re: Reescaneo de dispositivos scsi sin reiniciar

ambos sistemas, no sólo de software (versiones, sistemas operativos, tipo de controlador de disco duro...) y configuración sino de hardware. También he probado con este script: http://www.garloff.de/kurt/linux/#rescan-scsi y me pasa igual, en algunas si y en otras no. Lo único que me ha

Re: insmod: error inserting /lib/modules/2.6.32-5-486/kernel/drivers/scsi/aacraid/aacraid.ko : -1 File exists

On 2012-05-03, Joey L mjh2...@gmail.com wrote: insmod: error inserting /lib/modules/2.6.32-5-486/kernel/drivers/scsi/aacraid/aacraid.ko : -1 File exists Does it (is it already loaded)? lsmod | grep aacraid -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject

insmod: error inserting /lib/modules/2.6.32-5-486/kernel/drivers/scsi/aacraid/aacraid.ko : -1 File exists

i downloaded the new aacraid driver from ibm. - I need to install it during debian install - but getting an error - insmod: error inserting /lib/modules/2.6.32-5-486/kernel/drivers/scsi/aacraid/aacraid.ko : -1 File exists I have no clue what this means -- here are the instructions

scsi Install problem

I am trying to reinstall an older machine with an Advansys SCSI host adapter and not having much luck. I have two of the same model adapters and both have the same issues. When I boot without either in the machine, it gets well past my error/stopping point. I'm booting off of the CD 1, I

Re: scsi Install problem

On Wed, Apr 04, 2012 at 08:20:08AM -0700, cletusjenkins wrote: I am trying to reinstall an older machine with an Advansys SCSI host adapter and not having much luck. I have two of the same model adapters and both have the same issues. When I boot without either in the machine, it gets well

Re: scsi Install problem

On Wed, 04 Apr 2012 08:20:08 -0700, cletusjenkins wrote: (...) scsi host0: error: init_state 0x1f, warn 0xfffe, error 0x0 firmware: requisting advansys/mcode.bin Failed to load image advansys/mcode.bin err -2 scsi 0:0:0:0: SCSI bus reset started... The internet seems to say

Re: aacraid and smp kernel: SCSI hang

Opteron CPU. When we tried to boot the system with the SMP kernel it gave the following messages just after the login prompt and hung: Nov 9 09:52:58 myhost kernel: aacraid: Host adapter reset request. SCSI hang ? Nov 9 09:52:58 myhost kernel: aacraid: Host adapter reset request. SCSI hang ? Nov

scsi device files not created when called for

] firewire_sbp2: fw1.0: 127s mgt_ORB_timeout limited to 40s [ 8377.529108] firewire_core: created device fw1: GUID 484ee815, S400 [ 8377.728590] firewire_sbp2: fw1.0: logged in to LUN (0 retries) [ 8377.729957] scsi 7:0:0:0: Processor EPSONGT-X900 1.06 PQ: 0

Re: scsi device files not created when called for

On Sat, 11 Feb 2012 14:06:40 +0100, Morten Bo Johansen wrote: My scanner suddenly stopped working. It is connected through firewire and when I turn it on, the firewire devices are created: (...) My Epson scanner is thus recognized. However, the scanner is also being attached to a scsi

Re: scsi device files not created when called for

Camaleón noela...@gmail.com wrote: On Sat, 11 Feb 2012 14:06:40 +0100, Morten Bo Johansen wrote: In the latter case, which package should I report against? I'd say libsane. I think I'll go for udev. Once the scanner is attached to to a scsi device file, then the appropriate module should

[Squeeze] noyau 2.6.32-5-686 et scsi

Bonjour à tous :) Un peu en urgence ma boite m'a demandé d'installer un OS GNU/Linux sur un serveur IBM xSeries 336 et j'ai donc choisi ma distrib préférée Debian mais je fais face à des problèmes que je ne rencontre jamais d'habitude. Je précise que le serveur à deux disques scsi en RAID 1 (géré

Re: [Squeeze] noyau 2.6.32-5-686 et scsi

Hello, Le jeudi 23 décembre 2010 à 15:55 +0100, Kevin Hinault a écrit : 2 / Me voilà donc à installer une Lenny puis a faire une migration vers Squeeze ce qui devrait en théorie fonctionner pareil. Donc je mets à jour le source.list comme d'habitude, je fais la migration, il m'installe les

Re: [Squeeze] noyau 2.6.32-5-686 et scsi

Le 23 décembre 2010 16:22, Bruno Muller br...@inertiacreeps.net a écrit : Je suppose que tu finis dans le shell busybox de l'initrd... Exact Je suppose aussi que le disque est bien trouvé (/dev/sd?? existent) mais que /dev/mapper/ est vide. Exact Si c'est bien ça, il y a des chances

Re: kernel option for scsi emulation

On Fri, 12 Nov 2010 14:10:48 -0600, Hugo Vanwoerkom wrote: On 11/12/2010 01:49 PM, Camaleón wrote: (...) Compare both lsmod | grep ata outputs. Good suggestion: h...@debian:/$ grep ata 11.2.6.32-5-686.lsmod ata_generic 2047 0 libata115745 3

kernel option for scsi emulation

Hi, I have 2 kernels: Debian's 2.6.32-5-686 and my own 2.6.36-hvw. The former no longer has /dev/hd* the latter does as shown by blkid. [1] blkid for 2.6.32-5-686 and [2] for 2.6.36-hvw. What kernel option is responsible for that? Obviously I don't have that set in 2.6.36-hvw. Thanks.

Re: kernel option for scsi emulation

On Fri, 12 Nov 2010 12:06:16 -0600, Hugo Vanwoerkom wrote: I have 2 kernels: Debian's 2.6.32-5-686 and my own 2.6.36-hvw. The former no longer has /dev/hd* the latter does as shown by blkid. [1] blkid for 2.6.32-5-686 and [2] for 2.6.36-hvw. What kernel option is responsible for that?

Re: kernel option for scsi emulation

On 11/12/2010 01:49 PM, Camaleón wrote: On Fri, 12 Nov 2010 12:06:16 -0600, Hugo Vanwoerkom wrote: I have 2 kernels: Debian's 2.6.32-5-686 and my own 2.6.36-hvw. The former no longer has /dev/hd* the latter does as shown by blkid. [1] blkid for 2.6.32-5-686 and [2] for 2.6.36-hvw. What

Re: kernel option for scsi emulation

CONFIG_BLK_DEV_SR=m that is the SCSI CDrom module and that is set in the kernel. Don't know why it does not show up in lsmod. That leaves the pata_via module and that indeed is not set. So the difference in getting /dev/hd* is solely due to the absence of the pata_via module? Hugo

Re: kernel option for scsi emulation

CONFIG_BLK_DEV_SR=m that is the SCSI CDrom module and that is set in the kernel. Don't know why it does not show up in lsmod. That leaves the pata_via module and that indeed is not set. So the difference in getting /dev/hd* is solely due to the absence of the pata_via module? Hugo

Re: kernel option for scsi emulation

On Fri, 12 Nov 2010 14:10:48 -0600, Hugo Vanwoerkom wrote: On 11/12/2010 01:49 PM, Camaleón wrote: (...) Compare both lsmod | grep ata outputs. Good suggestion: h...@debian:/$ grep ata 11.2.6.32-5-686.lsmod ata_generic 2047 0 libata115745 3

Re: [Total HS] Récupère( rais) connecteurs SCSI HD50 (et autres) pour câbla ge audio

On Mon, Sep 20, 2010 at 09:08:24PM +0200, Jean-Yves F. Barbier wrote : On Mon, 20 Sep 2010 20:38:37 +0200, Aurelien tyran...@free.fr wrote: 47 K pour un micro ? tu parles d'ohms ? Ca n'a pas trop de sens sur un micro, vu que la courbe d'impédance est tout sauf plate (si ce n'est sur une

[Total HS] Récupère(rai s) connecteurs SCSI HD50 (et autres) pour câblag e audio

Salut, Je suis à la recherche de connectique type HD50 (connecteur SCSI-2, ceux qui se clipsent sur les côtés, pas ceux qui se vissent) pour faire essayer de voir si on peut s'en servir comme d'une connectique groupée pour de l'audio sur scène (en gros HD50 ~= 15 XLR et 1 XLR = 1 instrument ou 1

Re: [Total HS] Récupère(rais) connecteurs SCSI HD50 (et autres) pour câblage audio

On Mon, 20 Sep 2010 17:10:33 +0200, Aurelien tyran...@free.fr wrote: ... Au passage, je me posais un peu des questions quant à l'isolation entre les pins. En audio, on traite avec des signaux très petits (150mV), là où j'imagine que d'habitude c'est du 5V qui passe. Du coup, je ne sais pas

Re: [Total HS] Récupère( rais) connecteurs SCSI HD50 (et autres) pour câbla ge audio

On Mon, Sep 20, 2010 at 06:01:00PM +0200, Jean-Yves F. Barbier wrote : On Mon, 20 Sep 2010 17:10:33 +0200, Aurelien tyran...@free.fr wrote: ... Au passage, je me posais un peu des questions quant à l'isolation entre les pins. En audio, on traite avec des signaux très petits (150mV), là

Re: [Total HS] Récupère(rais) connecteurs SCSI HD50 (et autres) pour câblage audio

On Mon, 20 Sep 2010 19:09:15 +0200, Aurelien tyran...@free.fr wrote: En effet, j'aurais dû préciser que je comptais avoir très très court de câbles (de fils, en fait) avant de revenir à un format de câble (multipaire, dans le jargon) standard. Il s'agit juste d'une adaptation finale. Donc ça

Re: [Total HS] Récupère( rais) connecteurs SCSI HD50 (et autres) pour câbla ge audio

On Mon, Sep 20, 2010 at 07:36:42PM +0200, Jean-Yves F. Barbier wrote : On Mon, 20 Sep 2010 19:09:15 +0200, Aurelien tyran...@free.fr wrote: En effet, j'aurais dû préciser que je comptais avoir très très court de câbles (de fils, en fait) avant de revenir à un format de câble (multipaire,

Re: [Total HS] Récupère(rais) connecteurs SCSI HD50 (et autres) pour câblage audio

On Mon, 20 Sep 2010 20:38:37 +0200, Aurelien tyran...@free.fr wrote: 47 K pour un micro ? tu parles d'ohms ? Ca n'a pas trop de sens sur un micro, vu que la courbe d'impédance est tout sauf plate (si ce n'est sur une petite partie de la bande). Enfin, en général, on se place avant la

Re: scsi/firewire kernel oops, any point in reporting a bug ?

On 2010-07-14 04:31 +0200, bri...@aracnet.com wrote: The question is , submit to Debian or to LKML ? Report a bug in Debian, they will likely instruct how to report upstream. But first of all, boot a newer kernel because your current one… [24128.816259] Pid: 716, comm: scsi_eh_10 Tainted: P

Re: scsi/firewire kernel oops, any point in reporting a bug ?

On Wed, 14 Jul 2010 09:09:10 +0200 Sven Joachim svenj...@gmx.de wrote: On 2010-07-14 04:31 +0200, bri...@aracnet.com wrote: The question is , submit to Debian or to LKML ? Report a bug in Debian, they will likely instruct how to report upstream. But first of all, boot a newer kernel

Re: scsi/firewire kernel oops, any point in reporting a bug ?

On 2010-07-15 03:35 +0200, bri...@aracnet.com wrote: Looks like the latest kernel is -5, is that correct ? Yes. Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive:

scsi/firewire kernel oops, any point in reporting a bug ?

Hi All, I've attached the output of dmesg at the end of the e-mail. As usual everything was perfectly stable before I made the mistake of doing dist-upgrade. I've really got to quit doing that unless I _really_ need to. So I can't see that anyone is going to be able to use the information to

Resolu : Scsi installation bloque le boot

Bonjour, Effectivement, en supprimant le disque sata et en installant le système sur l'un des disques scsi le problème a été résolu. Question subsidiaire : est-il possible d'installer conjointement un disque sata et un disque scsi sans provoquer ce conflit de nom ? Merci pour votre aide

Re: Resolu : Scsi installation bloque le boot

Le mardi 27 avril 2010 à 08:44:10 tu as dit : Bonjour, Salut, Effectivement, en supprimant le disque sata et en installant le système sur l'un des disques scsi le problème a été résolu. Question subsidiaire : est-il possible d'installer conjointement un disque sata et un disque scsi

Re: Resolu : Scsi installation bloque le boot

alain vanranst a écrit : Effectivement, en supprimant le disque sata et en installant le système sur l'un des disques scsi le problème a été résolu. Question subsidiaire : est-il possible d'installer conjointement un disque sata et un disque scsi sans provoquer ce conflit de nom ? Je

Scsi installation bloque le boot

Scsi installation bloque le boot Bonjour, La situation: PC avec motherboard Supermicro P4SCi 1 HD sata 160 G avec le systeme Debian 5.0 Lenny; kernel 2.6.26-2-686 Tout fonctionne parfaitement. Je decide d'installer un raid 0 avec 6 disques scsi Carte : adaptec 39160 (bi-canal) 6 HD scsi 36.4G

Re: Scsi installation bloque le boot

- Mail d'origine - De: alain vanranst alainvanra...@gmail.com À: debian debian-user-french@lists.debian.org Envoyé: Mon, 26 Apr 2010 09:54:57 +0200 (CEST) Objet: Scsi installation bloque le boot Scsi installation bloque le boot Bonjour, La situation: PC avec motherboard Supermicro

Re: Scsi installation bloque le boot

Salut, Prière d'éviter le HTML la prochaine fois. alain vanranst a écrit : La situation: PC avec motherboard Supermicro P4SCi 1 HD sata 160 G avec le systeme Debian 5.0 Lenny; kernel 2.6.26-2-686 Tout fonctionne parfaitement. Je decide d'installer un raid 0 avec 6 disques scsi Carte

SCSI tape library ISCSI

Hi all, it's possible to manage a SCSI tape library (IBM 3581) with ISCSI? I need to use that library attached to a server into another server... Thanks Regards M **

Re: SCSI tape library ISCSI

Hi, it's possible to manage a SCSI tape library (IBM 3581) with ISCSI? I need to use that library attached to a server into another server... well, the aim is to share the tape library across the network.. Is there a way (iscsi or other) to do the job? Regards M

Re: SCSI tape library ISCSI

On 4/9/2010 10:39 AM, Mirco Piccin wrote: Hi, it's possible to manage a SCSI tape library (IBM 3581) with ISCSI? I need to use that library attached to a server into another server... well, the aim is to share the tape library across the network.. Is there a way (iscsi or other) to do

Re: SCSI tape library ISCSI

Mirco Piccin put forth on 4/9/2010 9:39 AM: Hi, it's possible to manage a SCSI tape library (IBM 3581) with ISCSI? I need to use that library attached to a server into another server... well, the aim is to share the tape library across the network.. Is there a way (iscsi or other) to do

Re: SCSI tape library ISCSI

Hi, thanks for replies. it's possible to manage a SCSI tape library (IBM 3581) with ISCSI? I need to use that library attached to a server into another server... well, the aim is to share the tape library across the network.. Is there a way (iscsi or other) to do the job? What you need

Re: SCSI tape library ISCSI

Mirco Piccin put forth on 4/9/2010 6:48 PM: Hi, thanks for replies. it's possible to manage a SCSI tape library (IBM 3581) with ISCSI? I need to use that library attached to a server into another server... well, the aim is to share the tape library across the network.. Is there a way

Re: SCSI module eata no longer loading automatically from initrd on Sid on i386

the corresponding devices are detected. Things like SCSI adapters, IDE controllers, etc. are generally probed for *before* the permanent root filesystem is mounted, for obvious reasons. Things which are not likely to be required to mount the permanent root file system, such as sound chips

Re: SCSI module eata no longer loading automatically from initrd on Sid on i386

Stephen Powell wrote, on 24/03/10 01:29: On Tue, 23 Mar 2010 04:56:05 -0400 (EDT), Arthur Marsh wrote: Stephen Powell wrote, on 2010-03-23 00:50: OK, there are a couple of things to check. First of all, make sure you have MODULES=most listed in /etc/initramfs-tools/initramfs.conf. grep -v \#

Re: SCSI module eata no longer loading automatically from initrd on Sid on i386

On Wed, 24 Mar 2010 07:05:13 -0400 (EDT), Arthur Marsh wrote: Why shouldn't the eata driver be loaded once the PCI bus has been scanned and a device that the eata driver knows about [1044:a400] in this case is detected? 00:08.0 SCSI storage controller [0100]: Adaptec (formerly DPT

Re: SCSI module eata no longer loading automatically from initrd on Sid on i386

Stephen Powell wrote, on 25/03/10 02:47: On Wed, 24 Mar 2010 07:05:13 -0400 (EDT), Arthur Marsh wrote: Why shouldn't the eata driver be loaded once the PCI bus has been scanned and a device that the eata driver knows about [1044:a400] in this case is detected? 00:08.0 SCSI storage controller

[SOLVED] SCSI module eata no longer loading automatically from initrd on Sid on i386

filesystem. Re-run lilo, if you're using lilo, then shutdown and reboot. If I have the syntax right for the alias command above, the hotplug system should load the eata module at the proper time for SCSI adapter device drivers to be loaded, but only if the card is actually found in the system

Re: SCSI module eata no longer loading automatically from initrd on Sid on i386

Stephen Powell wrote, on 2010-03-23 00:50: OK, there are a couple of things to check. First of all, make sure you have MODULES=most listed in /etc/initramfs-tools/initramfs.conf. grep -v \# /etc/initramfs-tools/initramfs.conf|uniq MODULES=most BUSYBOX=y KEYMAP=n BOOT=local DEVICE=eth0

Re: SCSI module eata no longer loading automatically from initrd on Sid on i386

devices are detected. Things like SCSI adapters, IDE controllers, etc. are generally probed for *before* the permanent root filesystem is mounted, for obvious reasons. Things which are not likely to be required to mount the permanent root file system, such as sound chips, may

Re: SCSI module eata no longer loading automatically from initrd on Sid on i386

On Sun, 21 Mar 2010 07:50:57 -0400 (EDT), Arthur Marsh wrote: On Sun, 21 Mar 2010 07:28:24 -0400 (EDT), Stephen Powell wrote: On Sun, 21 Mar 2010 04:25:45 -0400 (EDT), Arthur Marsh wrote: Hi, I have a DPT 2044W SCSI adaptor in this pc for a non-boot disk ... So what's the problem

SCSI module eata no longer loading automatically from initrd on Sid on i386

Hi, I have a DPT 2044W SCSI adaptor in this pc for a non-boot disk, and previously had it working fine with dependency-based booting with the required SCSI module eata listed in /etc/modules, all under Debian Sid on i386. Module eata would load about 4 seconds into the boot before the INIT

Re: SCSI module eata no longer loading automatically from initrd on Sid on i386

On Sun, 21 Mar 2010 04:25:45 -0400 (EDT), Arthur Marsh wrote: Hi, I have a DPT 2044W SCSI adaptor in this pc for a non-boot disk ... Your post is quite long; and after reading it twice, I still don't understand exactly what your question is or what problem you are trying to solve. I would

Re: SCSI module eata no longer loading automatically from initrd on Sid on i386

Stephen Powell wrote, on 21/03/10 21:58: On Sun, 21 Mar 2010 04:25:45 -0400 (EDT), Arthur Marsh wrote: Hi, I have a DPT 2044W SCSI adaptor in this pc for a non-boot disk ... Your post is quite long; and after reading it twice, I still don't understand exactly what your question is or what

  1   2   3   4   5   6   7   8   9   10   >