|
Who's Online
|
16 user(s) are online (7 user(s) are browsing Forums)
Members: 1
Guests: 15
cha05e90, more... |
|
|
Browsing this Thread:
1 Anonymous Users
|
|
|
Mrodfr [image]
|
Re: usb 16go key copy problem on SAM |
|
Not too shy to talk
From:
France
|
|
Posts:
486
|
|
Posted on: 2009/5/21 16:18:22
|
|
@ZeroG
The key has been formated as FAT32 with AOS4.1. Take now a verry long time to be initialized by AOS (key led flicker during a long time).
after formating by AOS4:
L:crossdodfilesystem (FAT2)
used: 9.3 go (62%)
free: 5.6 fo (38%)
size: 14.9 go
block:512 octets
A verry strange formated result by OS4. This key work without problems with a PC usually. It's why I have the problem to said It's a faulty Key and must be remplaced because no problems on a PC (key used often at job or on the classic+spider2).
I think I will full this key with the classic+spider2 for checking where came the problem 
to be continued....
Edited by Mrodfr on 2009/5/21 17:00:01
|
|
_________________
A1200+Mediator+VooDoo3+060/50+96mo+IIYAMA 17"+CD,CDRW,ZIP SCSI-KIT
SAM440EP on Mapower 3000+AOS4.1
|
 Transfer
|
|
|
|
|
Mrodfr [image]
|
Re: usb 16go key copy problem on SAM |
|
Not too shy to talk
From:
France
|
|
Posts:
486
|
|
Posted on: 2009/11/8 15:30:46
|
|
@all
Just for resurrected an old thread (but just related to USB and SAM).
Sometime copy USB stop strangely. This time a memguard hits when copying a file to a Memory stick adaptator.
The hit came and dopus4 PPC stop to copy. just reboot the SAM.
SFS: Warning: Task 0x5fe9a010 ("OHCI Controller Task Unit 0") called DoPkt()
SFS: Warning: Task 0x5fe9a010 ("OHCI Controller Task Unit 0") called DoPkt()
SFS: Warning: Task 0x5fe9a010 ("OHCI Controller Task Unit 0") called DoPkt()
SFS: Warning: Task 0x5fe9a010 ("OHCI Controller Task Unit 0") called DoPkt()
SFS: Warning: Task 0x5fe9a010 ("OHCI Controller Task Unit 0") called DoPkt()
SFS: Warning: Task 0x5fe9a010 ("OHCI Controller Task Unit 0") called DoPkt()
MEMGUARD HIT - "OHCI Controller Task Unit 0" (5fe9a010)
allocation of 32768 bytes by AllocVecTagList() failed
0: 6f8c2be4 5fe86e00 00000000 01c997c4 00008000 5fe86e88 80000005 80000003
8: 80000002 00000008 80000001 ffffff80 80000004 00000000 00000000 00000001
16: 4b421148 01e70000 5fe6b680 00008000 5ff99200 01e70000 ffffff0e 00000040
24: 4af6c508 00000003 00000000 00000000 00000040 00000001 00000001 00000080
----> 6f8c2be4 : "MemGuard" segment 0005 offset 8bdc
----> 01c997c4 : "Kickstart/kernel" segment 0001 offset 497c0
LR 01413690 : "Kickstart/kernel" segment 0000 offset 1368c
CTR 6f8c2be4 : "MemGuard" segment 0005 offset 8bdc
Stack backtrace:
----> 01413690 : "Kickstart/kernel" segment 0000 offset 1368c
----> 018b29dc : "Kickstart/ohci.usbhcd" segment 0000 offset 3bb8
----> 018b178c : "Kickstart/ohci.usbhcd" segment 0000 offset 2968
----> 018b5674 : "Kickstart/ohci.usbhcd" segment 0000 offset 6850
----> 018b59f8 : "Kickstart/ohci.usbhcd" segment 0000 offset 6bd4
----> 018b4508 : "Kickstart/ohci.usbhcd" segment 0000 offset 56e4
----> 0141581c : "Kickstart/kernel" segment 0000 offset 15818
Disassembly:
0141368c: 4e800421 bctrl
01413690: 80010084 lwz r0,132(r1)
01413694: 38210080 addi r1,r1,128
01413698: 7c0803a6 mtlr r0
0141369c: 4e800020 blr
It's just because I don't know how reporting this problem to AOS4 developpers. Hope one of them will see this post.
EDIT: Why allocated just little 32768 bytes for buffer (IMHO). We have 512mo of memory, or more 
Edited by Mrodfr on 2009/11/8 16:08:17
|
|
_________________
A1200+Mediator+VooDoo3+060/50+96mo+IIYAMA 17"+CD,CDRW,ZIP SCSI-KIT
SAM440EP on Mapower 3000+AOS4.1
|
| Transfer
|
|
|
|
|
Mrodfr [image]
|
Re: usb 16go key copy problem on SAM |
|
Not too shy to talk
From:
France
|
|
Posts:
486
|
|
Posted on: 2009/12/25 6:32:10
|
|
@all
Hum, I like this particular personnal thread, just for the USB problems I could have.
On my OCZ rally, I have copied AOS4.1 inside long time ago. one week ago, I have choosen to delete the copy located on the OCZ rally key, on the SAM. All have been well deleted but only:
DH1:utilities/sgrab/catalogs/aeeetina
hasn't been deleted (the path just with 0 size but on the key).
Ok. Some days ago, I have tried to use the key on a PC at job and the key has not been recognized on the PC.
This morning, I have used poseidon on the classic and the key work fine. try to play with aeetina (try to delete or rename or other things without luck). I have also copied some picture I have on the key safely on the classic (the only one who continue to recognize the key well).
OK, I have after copied one file on the key and... strangely, the name become 8+3.
hum, refresh the key content with dopus and all the key contend become 8+3 and with strange size. Again another time.
All this explanation to say that I have found that on sgrab, the langae aeeetina drawer (of course, sould be witten with the exact caracters langage) could lost you the content of your fat95 medias on particular conditions.
This time, the problem began on SAM, media not work on PC and finally, I have killed the usb content with the classic+poseidon
just for your information, be carefull with strange caracters on your SAM files installation.... could be destructed if copied on fat medias...
Bye.
|
|
_________________
A1200+Mediator+VooDoo3+060/50+96mo+IIYAMA 17"+CD,CDRW,ZIP SCSI-KIT
SAM440EP on Mapower 3000+AOS4.1
|
| Transfer
|
|
|
|
|
Mrodfr [image]
|
Re: usb 16go key copy problem on SAM |
|
Not too shy to talk
From:
France
|
|
Posts:
486
|
|
Posted on: 2010/1/28 15:59:00
|
|
@All and kicko,
Have tested my brand new (return warranty) OCZ Rally2 16gb key with AOS4.1.1.
First was to copy all WB content to the key, as a first test. Choosing the wb content and the copy start fine. Some 100mo copied and suddenly a crash, catched by memguard:
MEMGUARD HIT - "OHCI Controller Task Unit 0" (5fe5a070)
allocation of 8192 bytes by AllocVecTagList() failed
0: 6f452be4 5fe3ad90 00000000 01ca97c4 00002000 5fe3ae18 5a1bd198 59af60a8
8: 00002000 00000008 01ca97c4 0000207f 24000082 00000000 00000000 00000000
16: 00000000 00000001 59af60a8 5a28b7b0 5fe23680 00002000 01e70000 5ff9fb40
24: 00000000 00000040 5a695668 5fe955b8 00000000 00000040 00000002 00000003
----> 6f452be4 : "MemGuard" segment 0005 offset 8bdc
----> 01ca97c4 : "Kickstart/kernel" segment 0001 offset 497c0
----> 01ca97c4 : "Kickstart/kernel" segment 0001 offset 497c0
----> 01e70000 : "Kickstart/newlib.library.kmod" segment 0001 offset 061c
LR 014136f0 : "Kickstart/kernel" segment 0000 offset 136ec
CTR 6f452be4 : "MemGuard" segment 0005 offset 8bdc
Stack backtrace:
----> 014136f0 : "Kickstart/kernel" segment 0000 offset 136ec
----> 018c6dfc : "Kickstart/ohci.usbhcd" segment 0000 offset 5558
----> 018c45b4 : "Kickstart/ohci.usbhcd" segment 0000 offset 2d10
----> 018cb608 : "Kickstart/ohci.usbhcd" segment 0000 offset 9d64
----> 018cb788 : "Kickstart/ohci.usbhcd" segment 0000 offset 9ee4
----> 018c90b4 : "Kickstart/ohci.usbhcd" segment 0000 offset 7810
----> 0141587c : "Kickstart/kernel" segment 0000 offset 15878
Disassembly:
014136ec: 4e800421 bctrl
014136f0: 80010084 lwz r0,132(r1)
014136f4: 38210080 addi r1,r1,128
014136f8: 7c0803a6 mtlr r0
014136fc: 4e800020 blr
and after a requester said:
disk Rally2 has an error on block=298992.
error = 20
disk error
And I have seen and reported the same error on AOS4.1 version also(see post #22 before-look like the same), and allways on AOS4.1.1 
A reboot and the key is allways recognized fine. great. I wil continue some tests soon.
NOTE 1:
Yes, catched by memguard and no by grim reaper and also sorry for not having the usb.log because as the error = 20 is showed on the requester and I have teied to open ram:=bad idea. next time will be to quit the error requester and try to open the Ram:
NOTE 2:
The USB copy become more and more slower with drawer like AISS / toolbarimages, with 3500+ small images inside. At the end of this drawer copy, a little bytes file take one second or two ???????
Edited by Mrodfr on 2010/1/28 16:23:36
|
|
_________________
A1200+Mediator+VooDoo3+060/50+96mo+IIYAMA 17"+CD,CDRW,ZIP SCSI-KIT
SAM440EP on Mapower 3000+AOS4.1
|
| Transfer
|
|
|
|
|
Elwood [image]
|
Re: usb 16go key copy problem on SAM |
|
Quite a regular
From:
Lyon, France
|
|
Posts:
571
|
|
Posted on: 2010/1/28 19:00:14
|
|
@Mrodfr
I just copied my whole OS4 installation on a FAT32 formated Kingston 2 GB key. The copy process works fine but when I plug the key on a PC, it says it's broken :-/
Edited by Elwood on 2010/1/30 21:24:03
|
|
|
| Transfer
|
|
|
|
|
robo-ant [image]
|
Re: usb 16go key copy problem on SAM and AOS4.1 U1 (now) |
|
Just popping in
|
Posts:
21
|
|
Posted on: 2010/2/25 15:05:45
|
|
@Mrodfr
Quote:What mean your before AOS4.1, FAT95 failed allways ??? I don't understand really the before and after AOS4.1U1 explanation.
FAT32 USB volumes used to get read errors for me, with the OS4.1 beta (SAM). It was dangerous to copy files _from_ a USB stick. Now with OS4.1u1 I have successfully copied many, and large, files from USB media, with no errors.
With either version of the OS, it seems dangerous to copy files _to_ a FAT32 USB device.
Note that the small file I copied last night was named simply "files.md5", so no special characters or long filenames were involved.
Quote:
What look like the write error requester ???
Um, a normal system requester, I guess. I didn't pay that much attention to what it looked like, and I couldn't get a grab of it because Workbench was locked-up.
It said there was a write error on some block with a big number that I didn't write down.
Quote:
You copied things with a filemanager (dopus4) ???
Nope. I dragged the file to the volume using Workbench.
Quote:
The USB reset during the copy (USB mouse and keyboard) ???
I don't know if USB reset during the copy. I have a SAM440EP so I have to use USB mouse and keyboard. The mouse was still working after the error. Workbench was locked-up and I didn't have anything I could type into, so I don't know if the keyboard was still working.
Also, I don't have any USB hubs connected, or anything like that. Apart from the mouse and keyboard, the USB stick was the only USB device connected to the SAM.
I use this same USB stick with Windows all the time, and occasionally with Linux, and I haven't experienced a problem with it on those operating systems.
|
|
|
| Transfer
|
|
|
|
You can view topic.
You cannot start a new topic.
You cannot reply to posts.
You cannot edit your posts.
You cannot delete your posts.
You cannot add new polls.
You cannot vote in polls.
You cannot attach files to posts.
You cannot post without approval.
Home |
hehe
