Linux-Hardware Digest #224, Volume #14 Mon, 22 Jan 01 14:13:04 EST
Contents:
Re: Scanning SCSI hardware after startup ("Christian T. Steigies")
[Advice]: Multi-Modem for a Small ISP (Youngert)
Re: Swap size / Memory upgrade (Eric P. McCoy)
Re: Swap size / Memory upgrade (ekk)
Artisoft noderunner under 2.4 ("Ex Machina [xm]")
Re: Swap size / Memory upgrade ("Steve Wolfe")
Re: Swap size / Memory upgrade (Johan Kullstam)
Linux and USB and SmartMedia, oh my! ([EMAIL PROTECTED])
----------------------------------------------------------------------------
From: "Christian T. Steigies" <[EMAIL PROTECTED]>
Subject: Re: Scanning SCSI hardware after startup
Date: Mon, 22 Jan 2001 16:14:01 +0100
On 22 Jan 2001, Udo Wolter wrote:
> At first I must say that it's not recommended for SCSI-systems if a device
> will be powered on or off. Except the bus is hot pluggable (only newer
> RAID controllers support this). Anyway, nevertheless it's possible.
> The problem is that there is no rescan-command. But if you compile your
Huh? This question did not come up here the first time, and always the
answer was something like this:
#!/bin/bash
cat /proc/scsi/scsi
echo "scsi remove-single-device 0 0 0 0 " >/proc/scsi/scsi
echo -n 0
echo "scsi remove-single-device 0 0 1 0 " >/proc/scsi/scsi
echo -n 1
[...] # up to 7
echo "scsi add-single-device 0 0 0 0 " >/proc/scsi/scsi
echo -n 0
echo "scsi add-single-device 0 0 1 0 " >/proc/scsi/scsi
echo -n 1
[...] # up to 7
cat /proc/scsi/scsi
Thats what I use and its working just fine with MOD and CD-R. I am sure the
numbering thingy can be done more elegant though.
Christian
------------------------------
From: Youngert <[EMAIL PROTECTED]>
Subject: [Advice]: Multi-Modem for a Small ISP
Crossposted-To: comp.os.linux.misc
Date: Mon, 22 Jan 2001 17:02:32 GMT
Hi,
My linux system is connected to the Internet through a cable modem. So
far, I have setup my Linux machine as a PPP dial-in for several accounts and
am planning to provide a four local PPP dial-in for my friends whom do not
have a cable modem access. What I am looking for is a small equipment I
can use to connect to my Linux machine and phone lines so that my Linux
machine can act as a small ISP for my friends. It will also be nice if
such equipment can emulate a phone line in the sense that I can connect my
aplio/phone as well as webTV and dreamcast machine to my Linux. Any
suggestion on the equipment part as well as software setup?
TIA.
------------------------------
Crossposted-To: comp.os.linux.setup,comp.os.linux.misc
Subject: Re: Swap size / Memory upgrade
From: [EMAIL PROTECTED] (Eric P. McCoy)
Date: 22 Jan 2001 12:24:35 -0500
ekk <[EMAIL PROTECTED]> writes:
> I just upgraded from 512 RAM to 1 GB. My swap space is 768. Should
> I increase the swap? We do often use all of the RAM available on a
> machine, but we of course try to avoid using the swap.
Somewhat tangentially, why would you want to do this? It seems that
if your memory requirements stay about the same and you add RAM, you
shouldn't be increasing swap.
On the other hand, I've seen people advise exactly what you're
suggesting here. Is it for performance reasons?
So I guess I'm asking the same thing. I have 64MB RAM on this box and
gave it 128MB swap, which I surely don't need, but I figure this
prevents repartitioning should I, at some point, need that much.
--
Eric McCoy <[EMAIL PROTECTED]>
"Knowing that a lot of people across the world with Geocities sites
absolutely despise me is about the only thing that can add a positive
spin to this situation." - Something Awful, 1/11/2001
------------------------------
From: ekk <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup,comp.os.linux.misc
Subject: Re: Swap size / Memory upgrade
Date: Mon, 22 Jan 2001 12:34:10 -0500
Eric,
Ah, but my memory requirements are not going to be the same, now that I
have put more memory in. My users will most definitely use the extra RAM
to its full potential!
You do bring up an interesting point about only needing that much swap in
case you need it in the future. Maybe that is the reason my 'linux
mentor' advised me so.
"Eric P. McCoy" wrote:
> ekk <[EMAIL PROTECTED]> writes:
>
> > I just upgraded from 512 RAM to 1 GB. My swap space is 768. Should
> > I increase the swap? We do often use all of the RAM available on a
> > machine, but we of course try to avoid using the swap.
>
> Somewhat tangentially, why would you want to do this? It seems that
> if your memory requirements stay about the same and you add RAM, you
> shouldn't be increasing swap.
>
> On the other hand, I've seen people advise exactly what you're
> suggesting here. Is it for performance reasons?
>
> So I guess I'm asking the same thing. I have 64MB RAM on this box and
> gave it 128MB swap, which I surely don't need, but I figure this
> prevents repartitioning should I, at some point, need that much.
>
> --
> Eric McCoy <[EMAIL PROTECTED]>
> "Knowing that a lot of people across the world with Geocities sites
> absolutely despise me is about the only thing that can add a positive
> spin to this situation." - Something Awful, 1/11/2001
------------------------------
From: "Ex Machina [xm]" <[EMAIL PROTECTED]>
Subject: Artisoft noderunner under 2.4
Date: Mon, 22 Jan 2001 12:47:18 -0500
Hi. I can't the artisoft noderunner working under 2.4 in native or
ne1000/2000 modes.
in native mode:
ne.c:v1.10 9/23/94 Donald Becker ([EMAIL PROTECTED])
Last modified Nov 1, 2000 by Paul Gortmaker
NE*000 ethercard probe at 0x300: not found (no reset ack).
in ne2000/1000 mode:
ne.c:v1.10 9/23/94 Donald Becker ([EMAIL PROTECTED])
Last modified Nov 1, 2000 by Paul Gortmaker
NE*000 ethercard probe at 0x340: not found (invalid signature 42 42).
I've actually gotten these cards working before.
I"m running:
Linux moxie 2.4.0-ac9 #5 Thu Jan 18 18:45:55 EST 2001 i686 unknown
xm@moxie:~$ cat /proc/interrupts
CPU0
0: 62883 XT-PIC timer
1: 2503 XT-PIC keyboard
2: 0 XT-PIC cascade
7: 0 XT-PIC parport0
8: 1 XT-PIC rtc
9: 0 XT-PIC es1371
10: 10763 XT-PIC usb-uhci, eth0
12: 30150 XT-PIC PS/2 Mouse
14: 4396 XT-PIC ide0
15: 4 XT-PIC ide1
NMI: 0
LOC: 0
ERR: 0
The card is set to use irq 3 0x300 (the same occurs with 0x340).
The driver is staticly loaded.
Ex Machina ([EMAIL PROTECTED]) http://www.while1.net/~xm/
phone: +1-877-LPT-WHIP icq: 3387005 aim: ExMachina
------------------------------
From: "Steve Wolfe" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup,comp.os.linux.misc
Subject: Re: Swap size / Memory upgrade
Date: Mon, 22 Jan 2001 10:51:38 -0700
> Thanks, Jamess for your advice. The person whose job I inherited told me
> that the swap space should be double the amount of RAM for up to 512 MB,
> 1.5x for 512 - 1024, and 1x for above 1024 MB.
Ideally, you should have more RAM than you'll use, and some swap for a
backup. If you don't have that much RAM, then your RAM + swap should be
more than you'll use, and then some for safety. If you regularly use a half
gig of swap, then having a gig total (perhaps more) would be a good idea -
but I hate to think of the performance at that point. With RAM getting
cheaper and cheaper, I'm of the opinion that swap is simply there for
extremely abnormal situations.
> I'm not terribly sure why he
> thought so much swap was required, but I think he arrived at those ratios
> through experience dealing with many different machines and RAM amounts.
No, he just read them. "rules of thumb" on swap are about as useful as
saying "Oh, a size 12 ought to fit any woman that's between 50 and 150
pounds." Like women, each machine (and it's uses/needs) are different, and
need individual consideration.
> The machines he set up are stable and rarely get bogged down, as long as
the
> users don't push them over the RAM!
There you go, his magic numbers for swap haven't helped. You're still
stuch in the fact that swap is a few hundred (or thousand) times slower than
RAM. If your machine is swapping, you're hamstrung. If not, you're OK.
steve
------------------------------
Crossposted-To: comp.os.linux.setup,comp.os.linux.misc
Subject: Re: Swap size / Memory upgrade
From: Johan Kullstam <[EMAIL PROTECTED]>
Date: 22 Jan 2001 12:41:00 -0500
ekk <[EMAIL PROTECTED]> writes:
> Thanks, Jamess for your advice. The person whose job I inherited told me
> that the swap space should be double the amount of RAM for up to 512 MB,
> 1.5x for 512 - 1024, and 1x for above 1024 MB.
certain older (and maybe some current) unix distributions require that
you have enough swap space for all your memory, i.e., anything in
memory is also mirrored on disk swap. the left-over is swap storage.
it's similar to inclusive/exclusive L1/L2 caching on a CPU. the AMD
(tbird and duron) uses exclusive, the intel uses inclusive.
linux does not repeat core in swap. thus the linux swap is whatever
the left-over would have under the traditional regime.
> I'm not terribly sure why he
> thought so much swap was required, but I think he arrived at those ratios
> through experience dealing with many different machines and RAM
> amounts.
old system experience.
> The machines he set up are stable and rarely get bogged down, as long as the
> users don't push them over the RAM!
swap can be used for storing dead shells and dormant daemons at
virtually no performance penalty. some use of swap is just moving the
sleeping, non-running stuff out of the way of a process which wants to
run.
> Thank you kindly,
> Ken
>
> [EMAIL PROTECTED] wrote:
>
> > ekk wrote:
> > >
> > > Trying to make a judgement call without enough experience -
> > >
> > > I just upgraded from 512 RAM to 1 GB. My swap space is 768. Should
> > > I increase the swap? We do often use all of the RAM available on a
> > > machine, but we of course try to avoid using the swap.
don't bother unless you find yourself running out of swap.
> > > In the same way, I also downgraded a 1 GB RAM machine to 512 (bad RAM).
> > > Do I need to lower the swap space?
> > >
> > > In both situations disk space is not a concern.
> > >
> > > I assume the best way to adjust the swap is to use Partition Magic?
> > > I don't want to go through a whole reinstall of either machine.
> > >
> > > Ken
> >
> > I have 256 MB RAM and 128 MB swap on my box. It hardly ever uses any of
> > the swap at all except for programs like Netscape, and then it uses very
> > little swap. I don't think that you need more than 128 MB of swap when
> > you have a lot of ram.
> >
> > jamess
> > --
> > "On the side of the software box, in the 'System Requirements' section,
> > it said 'Requires Windows 95 or better'. So I installed Linux."
> >
> > -Anonymous
>
--
J o h a n K u l l s t a m
[[EMAIL PROTECTED]]
sysengr
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.setup
Subject: Linux and USB and SmartMedia, oh my!
Date: Mon, 22 Jan 2001 18:16:49 GMT
Hello all,
I've been working at getting a ZiO! USB SmartMedia reader working under
Linux 2.4.0-test12. The ZiO uses the SDDR-09 driver and I've gone to
the Linux USB homepage and the SDDR-09 mini-howto homepage
(http://www.theneals.net/linux/SDDR09-HOWTO) for help, but so far I
haven't been able to mount the drive.
I have compiled into the kernel scsi support, scsi disk support, scsi
generic support, and scsi emulation support (as per the SDDR-09
mini-howto). I have compiled the USB support as modules (usbcore,
usb-uhci, & usb-storage).
When I boot up it appears that the SCSI drivers come up ok. When I
load up the USB modules and plug in the ZiO I get the following output
from the following proc files:
/proc/bus/usb/devices:
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 7 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 0.00
S: Product=USB UHCI-alt Root Hub
S: SerialNumber=ff80
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
T: Bus=01 Lev=01 Prnt=07 Port=00 Cnt=01 Dev#= 10 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=16 #Cfgs= 1
P: Vendor=04e6 ProdID=0003 Rev= 2.07
S: Manufacturer=SCM Microsystems Inc.
S: Product=eUSB SmartMedia Adapter
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01
Driver=usb-storage
E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl= 0ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl= 0ms
E: Ad=83(I) Atr=03(Int.) MxPS= 2 Ivl= 32ms
/proc/scsi/scsi:
Attached devices:
Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: Sandisk Model: ImageMate SDDR09 Rev: 0207
Type: Direct-Access ANSI SCSI revision: 02
/var/log/messages shows this after insmod usb-uhci & usb-storage:
Jan 22 13:02:04 zee kernel: usb-uhci.c: $Revision: 1.251 $ time 07:03:35
Jan 22 2001
Jan 22 13:02:04 zee kernel: usb-uhci.c: High bandwidth mode enabled
Jan 22 13:02:04 zee kernel: usb-uhci.c: USB UHCI at I/O 0xff80, IRQ 10
Jan 22 13:02:04 zee kernel: usb.c: new USB bus registered, assigned bus
number 1
Jan 22 13:02:04 zee kernel: Product: USB UHCI Root Hub
Jan 22 13:02:04 zee kernel: SerialNumber: ff80
Jan 22 13:02:04 zee kernel: hub.c: USB hub found
Jan 22 13:02:04 zee kernel: hub.c: 2 ports detected
Jan 22 13:02:22 zee kernel: usb.c: registered new driver usb-storage
Jan 22 13:02:22 zee kernel: USB Mass Storage support registered.
after plugging in the ZiO /var/log/messages has this addition output:
Jan 22 13:03:42 zee kernel: hub.c: USB new device connect on bus1/1,
assigned device number 13
Jan 22 13:03:42 zee kernel: Manufacturer: SCM Microsystems Inc.
Jan 22 13:03:42 zee kernel: Product: eUSB SmartMedia Adapter
Jan 22 13:03:42 zee kernel: scsi1 : SCSI emulation for USB Mass Storage
devices
Jan 22 13:03:43 zee kernel: sda:<7>usb-storage: queuecommand() called
/var/log/debug has a MUCH longer output (please see end of post for
debug output)
When I try to mount the scsi device I get this:
zee:~# mount /dev/sda1 /mnt
mount: block device /dev/sda1 is write-protected, mounting read-only
mount: /dev/sda1 is not a valid block device
zee:~#
And /var/log/debug spits out:
Jan 22 13:08:33 zee kernel: usb-storage: queuecommand() called
Jan 22 13:08:33 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:08:33 zee kernel: usb-storage: Skipping START_STOP command
Jan 22 13:08:33 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:08:33 zee kernel: usb-storage: queuecommand() called
Jan 22 13:08:33 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:08:33 zee kernel: usb-storage: Skipping START_STOP command
Jan 22 13:08:33 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:08:33 zee kernel: usb-storage: queuecommand() called
Jan 22 13:08:33 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:08:33 zee kernel: usb-storage: Skipping START_STOP command
Jan 22 13:08:33 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:08:33 zee kernel: usb-storage: queuecommand() called
Jan 22 13:08:33 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:08:33 zee kernel: usb-storage: Skipping START_STOP command
Jan 22 13:08:33 zee kernel: usb-storage: *** thread sleeping.
I'm stuck now because I haven't found any info on what to try next.
Has anyone else ran into this problem and if so, what was your solution?
Thanks,
Kevin
/var/log/debug output:
Jan 22 13:03:42 zee kernel: hub.c: port 1 connection change
Jan 22 13:03:42 zee kernel: hub.c: port 1, portstatus 101, change 1, 12
Mb/s
Jan 22 13:03:42 zee kernel: hub.c: port 1, portstatus 103, change 0, 12
Mb/s
Jan 22 13:03:42 zee kernel: usb.c: kmalloc IF c12b4560, numif 1
Jan 22 13:03:42 zee kernel: usb.c: new device strings: Mfr=1, Product=2,
SerialNumber=0
Jan 22 13:03:42 zee kernel: usb.c: USB device number 13 default language
ID 0x409
Jan 22 13:03:42 zee kernel: usb-storage: Searching unusual device list
for (0x4e6, 0x3, 0x207)...
Jan 22 13:03:42 zee kernel: usb-storage: -- found matching device:
Sandisk ImageMate SDDR09
Jan 22 13:03:42 zee kernel: usb-storage: USB Mass Storage device
detected
Jan 22 13:03:42 zee kernel: usb-storage: Endpoints: In: 0xc65acd34 Out:
0xc65acd20 Int: 0xc65acd48 (Period 32)
Jan 22 13:03:42 zee kernel: usb-storage: Result from
usb_set_configuration is 0
Jan 22 13:03:42 zee kernel: usb-storage: New GUID
04e600030000000000000000
Jan 22 13:03:42 zee kernel: usb-storage: Transport: EUSB/SDDR09
Jan 22 13:03:42 zee kernel: usb-storage: Protocol: Transparent SCSI
Jan 22 13:03:42 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:42 zee kernel: usb-storage: queuecommand() called
Jan 22 13:03:42 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:03:42 zee kernel: usb-storage: Command INQUIRY (6 bytes)
Jan 22 13:03:42 zee kernel: usb-storage: 12 00 00 00 ff 00 12 c0 28 ec
22 c1
Jan 22 13:03:42 zee kernel: usb-storage: Fixing INQUIRY data to show
SCSI rev 2
Jan 22 13:03:42 zee kernel: usb-storage: scsi cmd done, result=0x0
Jan 22 13:03:42 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:42 zee kernel: usb-storage: queuecommand() called
Jan 22 13:03:42 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:03:42 zee kernel: usb-storage: Bad LUN (0/1)
Jan 22 13:03:42 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:42 zee kernel: usb-storage: queuecommand() called
Jan 22 13:03:42 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:03:42 zee kernel: usb-storage: Bad target number (1/0)
Jan 22 13:03:42 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:42 zee kernel: usb-storage: queuecommand() called
Jan 22 13:03:42 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:03:42 zee kernel: usb-storage: Bad target number (2/0)
Jan 22 13:03:42 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:42 zee kernel: usb-storage: queuecommand() called
Jan 22 13:03:42 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:03:42 zee kernel: usb-storage: Bad target number (3/0)
Jan 22 13:03:42 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:42 zee kernel: usb-storage: queuecommand() called
Jan 22 13:03:42 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:03:42 zee kernel: usb-storage: Bad target number (4/0)
Jan 22 13:03:42 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:42 zee kernel: usb-storage: queuecommand() called
Jan 22 13:03:42 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:03:42 zee kernel: usb-storage: Bad target number (5/0)
Jan 22 13:03:42 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:42 zee kernel: usb-storage: queuecommand() called
Jan 22 13:03:42 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:03:42 zee kernel: usb-storage: Bad target number (6/0)
Jan 22 13:03:42 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:42 zee kernel: usb-storage: queuecommand() called
Jan 22 13:03:42 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:03:42 zee kernel: usb-storage: Bad target number (7/0)
Jan 22 13:03:42 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:42 zee kernel: usb-storage: queuecommand() called
Jan 22 13:03:42 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:03:42 zee kernel: usb-storage: Command TEST_UNIT_READY (6
bytes)
Jan 22 13:03:42 zee kernel: usb-storage: 00 00 00 00 00 00 00 00 00 00
57 c3
Jan 22 13:03:42 zee kernel: usb-storage: SDDR09: Send control for
command 00 20 00 00 00 00 00 00 00 00 00 00
Jan 22 13:03:43 zee kernel: usb-storage: -- Stall on control pipe.
Clearing
Jan 22 13:03:43 zee kernel: usb-storage: -- usb_clear_halt() returns 0
Jan 22 13:03:43 zee kernel: usb-storage: -- transport indicates command
failure
Jan 22 13:03:43 zee kernel: usb-storage: Issuing auto-REQUEST_SENSE
Jan 22 13:03:43 zee kernel: usb-storage: SDDR09: Send control for
command 03 20 00 00 12 00 00 00 00 00 00 00
Jan 22 13:03:43 zee kernel: usb-storage: SDDR09: Control for command OK
Jan 22 13:03:43 zee kernel: usb-storage: SDDR09: receiving 18 bytes
Jan 22 13:03:43 zee kernel: usb-storage: SCM data in transfer 18 sg
buffers 0
Jan 22 13:03:43 zee kernel: usb-storage: Transfered 18 of 18 bytes
Jan 22 13:03:43 zee kernel: usb-storage: rd: 70 00 06 00 00 00 00 0B 00
00 00 00 28 00 00 00
Jan 22 13:03:43 zee kernel: usb-storage: rd: 00 00
Jan 22 13:03:43 zee kernel: usb-storage: -- Result from auto-sense is 0
Jan 22 13:03:43 zee kernel: usb-storage: -- code: 0x70, key: 0x6, ASC:
0x28, ASCQ: 0x0
Jan 22 13:03:43 zee kernel: usb-storage: Unit Attention: (unknown
ASC/ASCQ)
Jan 22 13:03:43 zee kernel: usb-storage: scsi cmd done, result=0x2
Jan 22 13:03:43 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:43 zee kernel: usb-storage: queuecommand() called
Jan 22 13:03:43 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:03:43 zee kernel: usb-storage: Command TEST_UNIT_READY (6
bytes)
Jan 22 13:03:43 zee kernel: usb-storage: 00 00 00 00 00 00 00 00 00 00
57 c3
Jan 22 13:03:43 zee kernel: usb-storage: SDDR09: Send control for
command 00 20 00 00 00 00 00 00 00 00 00 00
Jan 22 13:03:43 zee kernel: usb-storage: SDDR09: Control for command OK
Jan 22 13:03:43 zee kernel: usb-storage: scsi cmd done, result=0x0
Jan 22 13:03:43 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:43 zee kernel: usb-storage: queuecommand() called
Jan 22 13:03:43 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:03:43 zee kernel: usb-storage: Command READ_CAPACITY (10
bytes)
Jan 22 13:03:43 zee kernel: usb-storage: 25 00 00 00 00 00 00 00 00 00
57 c3
Jan 22 13:03:43 zee kernel: usb-storage: Reading capacity...
Jan 22 13:03:43 zee kernel: usb-storage: Result of send_control for
device ID is 0
Jan 22 13:03:43 zee kernel: usb-storage: SCM data in transfer 64 sg
buffers 0
Jan 22 13:03:43 zee kernel: usb-storage: Transfered 64 of 64 bytes
Jan 22 13:03:43 zee kernel: usb-storage: rd: 98 EA 41 69 22 22 22 22 22
22 22 22 22 22 22 22
Jan 22 13:03:43 zee kernel: usb-storage: rd: 22 22 22 22 22 22 22 22 22
22 22 22 22 22 22 22
Jan 22 13:03:43 zee kernel: usb-storage: rd: 22 22 22 22 22 22 22 22 22
22 22 22 22 22 22 22
Jan 22 13:03:43 zee kernel: usb-storage: Result of read_deviceID is 0
Jan 22 13:03:43 zee kernel: usb-storage: Device ID = EA
Jan 22 13:03:43 zee kernel: usb-storage: Manuf ID = 98
Jan 22 13:03:43 zee kernel: usb-storage: Read control address 00000000
blocks 0200
Jan 22 13:03:43 zee kernel: usb-storage: Result for send_control in
read_control 0
Jan 22 13:03:43 zee kernel: usb-storage: SCM data in transfer 32768 sg
buffers 1
Jan 22 13:03:43 zee kernel: usb-storage: Transfered 32768 of 32768 bytes
Jan 22 13:03:43 zee kernel: usb-storage: Result for bulk read in
read_control 0
Jan 22 13:03:43 zee kernel: usb-storage: LBA 0000 <-> PBA 0002
Jan 22 13:03:43 zee kernel: usb-storage: LBA 0002 <-> PBA 0003
Jan 22 13:03:43 zee kernel: usb-storage: LBA 0006 <-> PBA 0007
Jan 22 13:03:43 zee kernel: usb-storage: LBA 0007 <-> PBA 0008
Jan 22 13:03:43 zee kernel: usb-storage: LBA 0008 <-> PBA 0009
Jan 22 13:03:43 zee kernel: usb-storage: LBA 0009 <-> PBA 000A
Jan 22 13:03:43 zee kernel: usb-storage: LBA 000A <-> PBA 000B
Jan 22 13:03:43 zee kernel: usb-storage: LBA 000B <-> PBA 000C
Jan 22 13:03:43 zee kernel: usb-storage: LBA 000C <-> PBA 000D
Jan 22 13:03:43 zee kernel: usb-storage: LBA 000D <-> PBA 000E
Jan 22 13:03:43 zee kernel: usb-storage: LBA 000E <-> PBA 000F
Jan 22 13:03:43 zee kernel: usb-storage: LBA 000F <-> PBA 0010
Jan 22 13:03:43 zee kernel: usb-storage: LBA 0003 <-> PBA 0017
Jan 22 13:03:43 zee kernel: usb-storage: LBA 0005 <-> PBA 0033
Jan 22 13:03:43 zee kernel: usb-storage: LBA 0001 <-> PBA 0053
Jan 22 13:03:43 zee kernel: usb-storage: LBA 0004 <-> PBA 0059
Jan 22 13:03:43 zee kernel: usb-storage: scsi cmd done, result=0x0
Jan 22 13:03:43 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:43 zee kernel: usb-storage: queuecommand() called
Jan 22 13:03:43 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:03:43 zee kernel: usb-storage: Command MODE_SENSE (6 bytes)
Jan 22 13:03:43 zee kernel: usb-storage: 1a 00 3f 00 08 00 00 00 00 00
57 c3
Jan 22 13:03:43 zee kernel: usb-storage: CB_reset() called
Jan 22 13:03:43 zee kernel: usb-storage: CB[I] soft reset failed -32
Jan 22 13:03:43 zee kernel: usb-storage: -- transport indicates
transport failure
Jan 22 13:03:43 zee kernel: usb-storage: scsi cmd done, result=0x70000
Jan 22 13:03:43 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:43 zee kernel: usb-storage: queuecommand() called
Jan 22 13:03:43 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:03:43 zee kernel: usb-storage: Command MODE_SENSE (6 bytes)
Jan 22 13:03:43 zee kernel: usb-storage: 1a 00 3f 00 08 00 00 00 00 00
57 c3
Jan 22 13:03:43 zee kernel: usb-storage: CB_reset() called
Jan 22 13:03:43 zee kernel: usb-storage: CB[I] soft reset failed -32
Jan 22 13:03:43 zee kernel: usb-storage: -- transport indicates
transport failure
Jan 22 13:03:43 zee kernel: usb-storage: scsi cmd done, result=0x70000
Jan 22 13:03:43 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:43 zee kernel: usb-storage: queuecommand() called
Jan 22 13:03:43 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:03:43 zee kernel: usb-storage: Command MODE_SENSE (6 bytes)
Jan 22 13:03:43 zee kernel: usb-storage: 1a 00 3f 00 08 00 00 00 00 00
57 c3
Jan 22 13:03:43 zee kernel: usb-storage: CB_reset() called
Jan 22 13:03:43 zee kernel: usb-storage: CB[I] soft reset failed -32
Jan 22 13:03:43 zee kernel: usb-storage: -- transport indicates
transport failure
Jan 22 13:03:43 zee kernel: usb-storage: scsi cmd done, result=0x70000
Jan 22 13:03:43 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:43 zee kernel: usb-storage: queuecommand() called
Jan 22 13:03:43 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:03:43 zee kernel: usb-storage: Command MODE_SENSE (6 bytes)
Jan 22 13:03:43 zee kernel: usb-storage: 1a 00 3f 00 08 00 00 00 00 00
57 c3
Jan 22 13:03:43 zee kernel: usb-storage: CB_reset() called
Jan 22 13:03:43 zee kernel: usb-storage: CB[I] soft reset failed -32
Jan 22 13:03:43 zee kernel: usb-storage: -- transport indicates
transport failure
Jan 22 13:03:43 zee kernel: usb-storage: scsi cmd done, result=0x70000
Jan 22 13:03:43 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:43 zee kernel: usb-storage: queuecommand() called
Jan 22 13:03:43 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:03:43 zee kernel: usb-storage: Command MODE_SENSE (6 bytes)
Jan 22 13:03:43 zee kernel: usb-storage: 1a 00 3f 00 08 00 00 00 00 00
57 c3
Jan 22 13:03:43 zee kernel: usb-storage: CB_reset() called
Jan 22 13:03:43 zee kernel: usb-storage: CB[I] soft reset failed -32
Jan 22 13:03:43 zee kernel: usb-storage: -- transport indicates
transport failure
Jan 22 13:03:43 zee kernel: usb-storage: scsi cmd done, result=0x70000
Jan 22 13:03:43 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:43 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:03:43 zee kernel: usb-storage: Command READ_10 (10 bytes)
Jan 22 13:03:43 zee kernel: usb-storage: 28 00 00 00 00 00 00 00 02 00
57 c3
Jan 22 13:03:43 zee kernel: usb-storage: READ_10: read block 0002 (LBA
0000) page 0 pages 2
Jan 22 13:03:43 zee kernel: usb-storage: Read 02 pages, from PBA 0002
(LBA 0000) page 00
Jan 22 13:03:43 zee kernel: usb-storage: Result for send_control in
read_data 0
Jan 22 13:03:43 zee kernel: usb-storage: SCM data in transfer 512 sg
buffers 0
Jan 22 13:03:43 zee kernel: usb-storage: Transfered 512 of 512 bytes
Jan 22 13:03:43 zee kernel: usb-storage: rd: 01 03 D9 01 FF 18 02 DF 01
20 04 00 00 00 00 21
Jan 22 13:03:43 zee kernel: usb-storage: rd: 02 04 01 22 02 01 01 22 03
02 04 07 1A 05 01 03
Jan 22 13:03:43 zee kernel: usb-storage: rd: 00 02 0F 1B 08 C0 C0 A1 01
55 08 00 20 1B 0A C1
Jan 22 13:03:43 zee kernel: usb-storage: scsi cmd done, result=0x0
Jan 22 13:03:43 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:43 zee kernel: WARNING: USB Mass Storage data integrity not
assured
Jan 22 13:03:43 zee kernel: USB Mass Storage device found at 13
Jan 22 13:03:43 zee kernel: usb.c: usb-storage driver claimed interface
c12b4560
Jan 22 13:03:43 zee kernel: usb.c: kusbd: /sbin/hotplug add 13
Jan 22 13:03:43 zee kernel: usb.c: kusbd policy returned 0xfffffffe
Sent via Deja.com
http://www.deja.com/
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list by posting to comp.os.linux.hardware.
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Hardware Digest
******************************
