This is the bug/patch tracker for Rockbox. Click here for more information.
Quick links: Bugs · Patches · Rockbox frontpage
FS#10706 - Tag DB Never Builds
Attached to Project:
Rockbox
Opened by Brian Sutherland (rmaniac) - Thursday, 22 October 2009, 06:43 GMT+2
Last edited by sideral (sideral) - Thursday, 19 May 2011, 17:58 GMT+2
Opened by Brian Sutherland (rmaniac) - Thursday, 22 October 2009, 06:43 GMT+2
Last edited by sideral (sideral) - Thursday, 19 May 2011, 17:58 GMT+2
|
DetailsI am running 3.4 on a 5.5G iPod modified with a 240gb drive. Rockbox is stock 3.4 with LBA48 added in and the max sector size turned off. The database was working ok on 3.3. Only issue was it took forever to add new files. After upgrading to 3.4 I noticed every time I powered on rockbox would lock up in the menus for up to 10 minutes before functioning normally. So I completely removed the .rockbox dir (including the database files of course) and re-expanded a fresh copy. I then tried to init the db. It runs until it is around ~44k files and 99% and then just sits there. If left alone it will eventually just turn it self off. When I turn it back on it will ask me to init the db again. I have seen it try to commit once or twice but it never takes. I am not really sure how to debug this at this point. Also in the debug disk info area, it things my drive is 131071MB. Under Rockbox Info it says 223GB which is better, but these two things are the same as in 3.3. All my Oggs are converted via a script I wrote from my flacs. I do not believe my flacs have any art, I am not even sure you can store art in a flac tag and even them I don't think the ogg encoder is transferring them. I ran a tag dump (ogginfo) against my oggs and do not see anything to do with album art. I had 4 files on the device with album art. They were all in a directory with a database.ignore file. So they should not have been noticed. Just in case I removed that directory and rebuilt. It went though 44k files, commited 1-9 and then went back to "scanning" but the disk activity had stopped. Upon reboot it asked me to init the db again.
This is not a patched build. I simply changed the config to include large drive support. This is an issue that needs to be looked at. Please check into it, I will be happy to test any ideas. |
This task depends upon
#define HAVE_LBA48
/*#define MAX_PHYS_SECTOR_SIZE 1024*/
Added a define and removed a define. Other than that I did a normal build for a 64mb iPod Video.
Thanks
Anyway, this is *still* requesting support for a patched build. I'll leave it up to someone else whether to close it though...
/* define this if the hard drive uses large physical sectors (ATA-7 feature) */
/* and doesn't handle them in the drive firmware */
The 240gb seems to handle them in the firmware fine.