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 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
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
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
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
being 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.
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 customs
> tax, but the
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. ;-)*
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 of
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 LO
go 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 report:
"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:
Sense Code: 0x
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 0x0
"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
computer world either w
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
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
"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 iso=$1
wodim -v
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 -
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
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
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:
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 en
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 reinst
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 o
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 a
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
void a net
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
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
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, but
On 2012-05-03, Joey L 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 of
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 :( it
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 inte
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
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
Wed, Dec 5, 2007 at 5:09 AM, Kostas Magkos
>>>>> wrote:
>>>>>
>>>>>
>>>>>> Greetings all,
>>>>>>
>>>>>> Our main server is an Opteron system with an Adaptec SATA RAID 2410SA
>>>>>&g
Camaleón 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 appropr
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
> attach
] 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
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 ata_generic,sata_via,pata_
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 ata_generic,
bian:/usr/src/linux-2.6.36$ grep CONFIG_BLK_DEV_SR .config
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 so
bian:/usr/src/linux-2.6.36$ grep CONFIG_BLK_DEV_SR .config
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 so
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 kernel
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
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.
Hug
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: http://lists.debian.o
On Wed, 14 Jul 2010 09:09:10 +0200
Sven Joachim 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 because your
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
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 d
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, th
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 wa
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..
>
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..
>
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
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
**
-initramfs again. Check to make sure that the eata module is
>> still included in your initial RAM 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
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 contr
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]: A
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 \#
initial RAM
filesystem or not depends on when 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
ound chip. snd_cs4236
is the correct driver in my case; I don't need the other two.
This is the preferred method for loading kernel modules that are device
drivers for hardware devices. Whether they need to be in the initial RAM
filesystem or not depends on when the correspon
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
N
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 ...
>&g
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
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.
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
"
>
>
>
> Original Message
>From: longwind2...@gmail.com
>To: debian-user@lists.debian.org
>Subject: Re: need advice on scsi disk failure
>Date: Fri, 21 Aug 2009 14:33:10 -0800
>
>>On Fri, Aug 21, 2009 at 7:34 AM, wrote:
>>>>
>>> The c
;>>
>>>--
You are right!
I don't have alcohol
so I just use my hand to rub the connection between cable and connector
the new power supply (which always fails to power my scsi disk) can power it now
The human's hand is the best tool!
I still have to buy a new scsi cable (an
but I don't have alcohol
"If that doesn't work ", the scsi card doesn't find the disk and can't
run disk diagnostic
I have a new power supply and an old one.
Using the new one, the scsi disk always can't be found
but with the old one, I have more luck
--
To UNSUBSCR
>
>
>
> Original Message
>From: longwind2...@gmail.com
>To: debian-user@lists.debian.org
>Subject: RE: need advice on scsi disk failure
>Date: Fri, 21 Aug 2009 08:50:21 -0400
>
>>I bought a scsi 50G disk a few years ago
>>The seller said it had be
On Fri, 21 Aug 2009 09:35:25 -0400
Long Wind wrote:
> On Fri, Aug 21, 2009 at 8:56 AM, mitch
> wrote:
> >
> > I had the same problem, scsi drives failing to start, shutting down
> > while running.
> >
> > Bad power connector. The pins were not ma
On Fri, Aug 21, 2009 at 8:56 AM, mitch wrote:
>
> I had the same problem, scsi drives failing to start, shutting down
> while running.
>
> Bad power connector. The pins were not making proper contact at all
> times.
>
> Changed the connectors and the problem stopped.
>
On Fri, 21 Aug 2009 08:50:21 -0400
Long Wind wrote:
> It's no surprise because the light on scsi disk isn't on
> I reconnect the power cable to scsi disk again and again
> and then with some luck the disk works normally.
> It seems that the power connection becomes loose
I bought a scsi 50G disk a few years ago
The seller said it had been used on server for a long time
The scsi card used to warn that the disk will fail soon during boot
Then I change SCSI card firmware, the warning disappear
>From 5 days ago, the card often can't find disk during boot
Bhasker C V writes:
> The native driver can directly do all the tasks and SCSI emulation
> is not needed anymore.
>
> For programs like growisofs, cdrecord in the option dev=
> instead of giving 0,0,0 etc., you can give /dev/hdc directly.
Thank you. That is great new
Hi,
The native driver can directly do all the tasks and SCSI emulation
is not needed anymore.
For programs like growisofs, cdrecord in the option dev=
instead of giving 0,0,0 etc., you can give /dev/hdc directly.
On Tue, 5 May 2009, Martin McCormick wrote:
I upgraded my kernel from an
I upgraded my kernel from an old 2.6.5 kernel to a newer 2.6.18
kernel and noticed that the boot process ignored the passing of
/dev/hdc to scsi emulation. The drive worked fine after I
mounted it as /dev/cdrom rather than /dev/hcd0. Do I need to do
anything different to such programs as cdrecord
On Tuesday 2009 January 20 05:39:37 Arthur Marsh wrote:
>Ron Johnson wrote, on 20/01/09 06:08:
>> On 01/19/2009 01:30 PM, Boyd Stephen Smith Jr. wrote:
>>> On Monday 2009 January 19 13:15:28 Arthur Marsh wrote:
>>>> I have a machine that boots from and IDE drive th
Ron Johnson wrote, on 20/01/09 06:08:
On 01/19/2009 01:30 PM, Boyd Stephen Smith Jr. wrote:
On Monday 2009 January 19 13:15:28 Arthur Marsh wrote:
I have a machine that boots from and IDE drive then finds an internal
SCSI drive after any USB drives are found.
The SCSI disk gets fsck'
On 01/19/2009 01:30 PM, Boyd Stephen Smith Jr. wrote:
On Monday 2009 January 19 13:15:28 Arthur Marsh wrote:
I have a machine that boots from and IDE drive then finds an internal
SCSI drive after any USB drives are found.
The SCSI disk gets fsck'd and mounted fine if there is no USB dri
On Monday 2009 January 19 13:15:28 Arthur Marsh wrote:
>I have a machine that boots from and IDE drive then finds an internal
>SCSI drive after any USB drives are found.
>
>The SCSI disk gets fsck'd and mounted fine if there is no USB drive in
>the machine, but the mount -a
I have a machine that boots from and IDE drive then finds an internal
SCSI drive after any USB drives are found.
The SCSI disk gets fsck'd and mounted fine if there is no USB drive in
the machine, but the mount -a process at start-up mounts the USB drive
in place of one of the partitio
On 01/11/09 12:48, Jude DaShiell wrote:
I have a parallel to scsi converter and a jazz drive. If I hook that up
to the debian box I have running, how will debian see that drive? I
expect I can activate parallel port support but once done what kind of a
new device should I expect to find
I have a parallel to scsi converter and a jazz drive. If I hook that up
to the debian box I have running, how will debian see that drive? I
expect I can activate parallel port support but once done what kind of a
new device should I expect to find?
--
To UNSUBSCRIBE, email to debian-user
Arthur Marsh wrote, on 2008-12-09 00:53:
lee wrote, on 2008-11-29 04:07:
Hm, I've always been using the kernels from kernel.org without
problems.
How do you make .deb's of kernel.org kernels under Debian
(kernel-package, checkinstall, ???)
Arthur.
To make the DPT SCSI ca
On Mon, Dec 08, 2008 at 10:22:51PM +0100, Sven Joachim wrote:
>
> > Create new default link to new source code
>
> This is absolutely unnecessary and maybe even harmful. Read the README
> in the Linux kernel tree why you should not do it.
The NVIDIA driver doesn't install when it wants to comp
Arthur Marsh wrote, on 2008-12-08 19:58:
I'm still trying to get to the source of the bug that prevents me from
using a DPT2044W SCSI card that uses the eata module, and have narrowed
down the working and non-working Debian kernel images to between
linux-image-2.6.22-3-686 version 2.6
Sven Joachim:
>
>> Create a new config file based on the old one, this will prompt for new
>> configuration settings. Read carefully every question.
>> root# make oldconfig
>
> Finally, some good advice. But before this step, you need to copy your
> old config to linux-2.6.22.1/.config and cd t
I feel the need to correct a few bad ideas here.
On 2008-12-08 21:53 +0100, subscriptions wrote:
> Download the source code and unpack
Note, none but one of the steps below require root privileges if you are
a member of the `src' group or perform them below your home directory
instead of /usr/sr
On Mon, 2008-12-08 at 15:23 +0100, Arthur Marsh wrote:
> lee wrote, on 2008-11-29 04:07:
>
> > Hm, I've always been using the kernels from kernel.org without
> > problems.
>
> How do you make .deb's of kernel.org kernels under Debian
> (kernel-package, checkinstall, ???)
>
> Arthur.
Download
lee wrote, on 2008-11-29 04:07:
Hm, I've always been using the kernels from kernel.org without
problems.
How do you make .deb's of kernel.org kernels under Debian
(kernel-package, checkinstall, ???)
Arthur.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Tr
ing to get to the source of the bug that prevents me from
using a DPT2044W SCSI card that uses the eata module, and have narrowed
down the working and non-working Debian kernel images to between
linux-image-2.6.22-3-686 version 2.6.22-6.lenny1 which works, and
linux-image-2.6.23-1-686 versio
On Sat, Nov 29, 2008 at 12:53:26AM +1030, Arthur Marsh wrote:
> Arthur Marsh wrote, on 28/11/08 20:33:
>
>>
>> The 2.6.18.dfsg.1-12etch2 kernel allowed me to modprobe eata and I
>> received similar messages to those quoted above.
>>
>> The next newest kernel I can download is 2.6.24-etchnhalf.1-686
Arthur Marsh wrote, on 28/11/08 20:33:
The 2.6.18.dfsg.1-12etch2 kernel allowed me to modprobe eata and I
received similar messages to those quoted above.
The next newest kernel I can download is 2.6.24-etchnhalf.1-686.
kernel 2.6.24-etchnhalf.1-686 had problems after modprobe eata
Is there
http://ubuntuforums.org/showthread.php?t=472253
https://bugs.launchpad.net/ubuntu/+bug/120426
http://www.google.com/search?hl=en&q=modprobe+eata&btnG=Search
The sysrescuecd 0.30 beta that found the SCSI controller and hard disk
identified its kernel version as:
Linux sysrescuecd 2.6.18.3-fd01
kernel/0707.1/0621.html
nothing much there, but thanks for the links.
Any suggestions?
No good ones ... You could put the SCSI controller into another slot
and see what happens then --- I've had some SCSI controllers that
won't work in one slot but in another, and I've seen
On Thu, Nov 27, 2008 at 10:08:07PM +1030, Arthur Marsh wrote:
>> The correct module for the DPT SCSI card is eata but when I do:
>>
>> modprobe eata
>>
>> I get a kernel stack trace and a system lock-up )-:.
>>
>> I had no problem accessing the SCSI
Arthur Marsh wrote, on 2008-11-25 17:22:
lee wrote, on 25/11/08 01:24:
On Mon, Nov 24, 2008 at 04:29:52PM +1030, Arthur Marsh wrote:
Hi, I have a DPT2044W SCSI adaptor identified with lspci -vv as:
which has an IBM SCSI disk attached, which contains MS-Windows95 OSR2.
If I set the BIOS to
lee wrote, on 25/11/08 01:24:
On Mon, Nov 24, 2008 at 04:29:52PM +1030, Arthur Marsh wrote:
Hi, I have a DPT2044W SCSI adaptor identified with lspci -vv as:
which has an IBM SCSI disk attached, which contains MS-Windows95 OSR2.
If I set the BIOS to boot SCSI first, the disk is recognised and
On Mon, Nov 24, 2008 at 04:29:52PM +1030, Arthur Marsh wrote:
> Hi, I have a DPT2044W SCSI adaptor identified with lspci -vv as:
> which has an IBM SCSI disk attached, which contains MS-Windows95 OSR2.
>
> If I set the BIOS to boot SCSI first, the disk is recognised and boots.
>
1 - 100 of 2620 matches
Mail list logo
