(SuSE 9.1 Pro) I've been trying to get grip to work. On the grip list, they tell me I need to specify a specific ATAPI device using a command-line option something like: -D ATA:0,0,0 except that I need to replace the zeros with my specific system information. Unfortunately, no one of the grip list seems to know how I can determine my specific system information. I'm sure there's a command somewhere, similar to fdisk for partitions, that will give me the info I need but I'll be danged if I can find it. Will some kind soul please tell me what command I'm looking for? Sincere appreciation for your time. -- Donald D. Henson, Managing Director West El Paso Information Network The Non-Aggression Principle Rules
* Donald D Henson
I've been trying to get grip to work. On the grip list, they tell me I need to specify a specific ATAPI device using a command-line option something like:
-D ATA:0,0,0
/usr/bin/cdrecord --scanbus -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
Patrick Shanahan
* Donald D Henson
[07-26-04 11:11]: I've been trying to get grip to work. On the grip list, they tell me I need to specify a specific ATAPI device using a command-line option something like:
-D ATA:0,0,0
/usr/bin/cdrecord --scanbus
Actually, I have to use # /usr/bin/cdrecord --scanbus dev=ATA Cdrecord-Clone-dvd 2.01a27 ... ... scsidev: 'ATA' devname: 'ATA' scsibus: -2 target: -2 lun: -2 ... scsibus1: 1,0,0 100) 'AOPEN ' 'CD-RW CRW5232 ' '1.03' Removable CD-ROM 1,1,0 101) * 1,2,0 102) * 1,3,0 103) * 1,4,0 104) * 1,5,0 105) * 1,6,0 106) * 1,7,0 107) * otherwise real SCSI devices are listed # /usr/bin/cdrecord --scanbus Cdrecord-Clone-dvd 2.01a27 ... ... scsibus0: 0,0,0 0) * 0,1,0 1) * 0,2,0 2) * 0,3,0 3) 'HP ' 'Ultrium 2-SCSI ' 'F48D' Removable Tape 0,4,0 4) * 0,5,0 5) * 0,6,0 6) * 0,7,0 7) * scsibus1: 1,0,0 100) '3ware ' 'Logical Disk 0 ' '1.0' Disk 1,1,0 101) '3ware ' 'Logical Disk 1 ' '1.0' Disk 1,2,0 102) * 1,3,0 103) * 1,4,0 104) * 1,5,0 105) * 1,6,0 106) * 1,7,0 107) * -- A.M.
Hi if anyone can help me..? I have Clie palm Tj37 connected to a USB craddle When i try to make a hoptsync with kpilot, after hitting the hotsync button on the Clie, all suse 9.1 freeze ??? in general, if I hit the hotsync with my Clie connected to USB, it freeze SuSe again even without being in kpilot. mouse and keyboard don't response, I must reboot my PC. On the other hand, I try the same operation with a boot-cd of knoppix the hotsync works perfectly on it... really, thanks in advance Gr
Gr, Do you have other USB devices? I found that the BIOS "legacy USB" mode would cause the kernel 2.6 from SuSE 9.1 to hang, either during initial detection, if USB devices were present on the bus and powered up or if they were latter connected or turned on. Turning of the "legacy" support made the symptom go away. Randall Schulz On Friday 06 August 2004 11:33, bea-gr wrote:
Hi
if anyone can help me..? I have Clie palm Tj37 connected to a USB craddle When i try to make a hoptsync with kpilot, after hitting the hotsync button on the Clie, all suse 9.1 freeze ??? in general, if I hit the hotsync with my Clie connected to USB, it freeze SuSe again even without being in kpilot. mouse and keyboard don't response, I must reboot my PC.
On the other hand, I try the same operation with a boot-cd of knoppix the hotsync works perfectly on it...
really, thanks in advance Gr
participants (5)
-
Alexandr Malusek
-
bea-gr
-
Donald D Henson
-
Patrick Shanahan
-
Randall R Schulz