![]() |
2008-07-03
, 07:50
|
|
Posts: 166 |
Thanked: 26 times |
Joined on Jun 2007
@ Hampshire, UK
|
#2
|
![]() |
2008-07-03
, 14:09
|
Posts: 100 |
Thanked: 17 times |
Joined on Mar 2008
@ Hillsboro, Nh.
|
#3
|
![]() |
2008-07-03
, 14:21
|
Posts: 83 |
Thanked: 18 times |
Joined on Jun 2008
|
#4
|
![]() |
2008-07-03
, 18:26
|
|
Posts: 698 |
Thanked: 129 times |
Joined on Oct 2007
@ CA
|
#6
|
![]() |
2008-07-04
, 04:37
|
|
Posts: 221 |
Thanked: 182 times |
Joined on Jul 2007
@ Central Illinois
|
#7
|
The Following User Says Thank You to terrencegf For This Useful Post: | ||
![]() |
2008-07-04
, 15:18
|
Posts: 833 |
Thanked: 124 times |
Joined on Nov 2007
@ Based in the USA
|
#8
|
Okay, I think I'm a little closer to resolving the issue. I reflashed with chinook and realized that not all of my flash drives worked correctly. So apparently I tried some "new" flash drives under diablo and incorrectly figured that they had worked with chinook.
Then I reflashed with diablo, and eventually managed to get all of the flash drives which worked with chinook to also work with diablo. I say "eventually" because I had to plug/unplug the flash drives a couple of times before diablo recognized them. This was not the case with chinook.
So I think the title of the thread should be "Diablo SLIGHTLY less tolerant" since I managed to get the same drives working under diablo (with a little fiddling).
As to the wired network issue, I also cannot get my ethernet adapter to work. But as stated in other posts, until the DUMMY interface issue can be hacked around, I don't think I can effectively debug it.
![]() |
2008-07-07
, 15:09
|
Posts: 13 |
Thanked: 2 times |
Joined on Jul 2008
|
#9
|
![]() |
2008-07-08
, 00:36
|
|
Posts: 221 |
Thanked: 182 times |
Joined on Jul 2007
@ Central Illinois
|
#10
|
Just for info could you provide models etc of flash drives that work and don't, for those of us who have not bought them yet?
ID 04e8:1a23 Samsung Electronics Co., Ltd (2G Black Samsung) ID 090c:1000 Feiya Technology Corp. Memory Bar (2G A-Data MyFlash) ID 0204:6025 Chipsbank Microelectronics Co., Ltd CBM2080 Flash drive controller (256M Generic) ID 0d7d:1300 Phison Electronics Corp. Flash Disk (128M PNY Attache) ID 0ea0:2168 Ours Technology, Inc. Transcend JetFlash 2.0 / Astone USB Drive (64mb Micro Advantange QuickDrive) ID 1370:2168 Swissbit (512M Swissbit)
ID 058f:6331 Alcor Micro Corp. (Rosewill SDHC card reader) ID 0781:a7a8 SanDisk Corp. (SanDisk SDHC card reader) ID 058f:6369 Alcor Micro Corp. (Black generic SD card reader) ID 14cd:6700 Super Top (Generic T-Flash/MicroSD card reader)
The Following User Says Thank You to terrencegf For This Useful Post: | ||
Then I thought that perhaps all the extra stuff I installed was causing problems. So I reflashed diablo and tried with a fresh system. Still no luck. It took me a couple of hours to get everything back to normal (external boot menu, mainly). I can boot to my cloned diablo partition AND also my old cloned chinook system. The results are the same regardless of which partition/OS I boot to. "/sys/devices/platform/musb_hdrc/mode" shows "a_host", so it's definitely seeing the device, and "lsusb" shows a couple of the thumb drives (but not all).
As a last ditch effort, I tried my external USB HDD (self-powered). SUCCESS!!! So the thing works after all, wow!
But this makes me wonder why the flash drives that worked just fine with chinook fail to work in diablo. And why don't those flash drives work when I boot into the chinook partition? Is it something to do with the initfs bootmenu stuff? I'm curious if other people have seen something similar with their chinook-to-diablo upgrade experience.
Thanks for reading my plaint.