Tiny Core v4.0 Alpha 3

[hjkl]

Hi,

I have a USB CompactFlash card reader.  When I use it with a 64MB CompactFlash card on TC3 and DSL, I get a message like this:


usb 2-2: new full speed USB device using uhci_hcd and address 2
scsi1 : usb-storage 2-2:1.0
scsi 1:0:0:0: Direct-Access     Generic  STORAGE DEVICE   0.01 PQ: 0 ANSI: 0
sd 1:0:0:0: Attached scsi generic sg1 type 0
sd 1:0:0:0: [sdb] 125185 512-byte logical blocks: (64.0 MB/61.1 MiB)
sd 1:0:0:0: [sdb] Test WP failed, assume Write Enabled
sd 1:0:0:0: [sdb] Assuming drive cache: write through
sd 1:0:0:0: [sdb] Test WP failed, assume Write Enabled
sd 1:0:0:0: [sdb] Assuming drive cache: write through
 sdb: sdb1
sd 1:0:0:0: [sdb] Test WP failed, assume Write Enabled
sd 1:0:0:0: [sdb] Assuming drive cache: write through
sd 1:0:0:0: [sdb] Attached SCSI removable disk


My memory card looks like this:

tc@box[~]$ fdisk -l /dev/sdb

Disk /dev/sdb: 64 MB, 64094720 bytes
2 heads, 62 sectors/track, 1009 cylinders
Units = cylinders of 124 * 512 = 63488 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sdb1   *           1        1009       62527  83 Linux


TC3:
Linux box 2.6.33.3-tinycore #2012 SMP Wed May 12 17:05:42 EEST 2010 i686 GNU/Linux


DSL:
Linux box 2.4.31 #1 SMP Sat Jul 12 16:12:42 EDT 2008 i686 GNU/Linux


But, when I connect the same device to Alpha3, I get a message like this:


usb 2-2: new full speed USB device number 2 using uhci_hcd
scsi3 : usb-storage 2-2:1.0
scsi 3:0:0:0: Direct-Access     Generic  STORAGE DEVICE   0.01 PQ: 0 ANSI: 0
sd 3:0:0:0: Attached scsi generic sg2 type 0
sd 3:0:0:0: [sdc] 125185 512-byte logical blocks: (64.0 MB/61.1 MiB)
sd 3:0:0:0: [sdc] Test WP failed, assume Write Enabled
sd 3:0:0:0: [sdc] Cache data unavailable
sd 3:0:0:0: [sdc] Assuming drive cache: write through
sd 3:0:0:0: [sdc] Test WP failed, assume Write Enabled
sd 3:0:0:0: [sdc] Cache data unavailable
sd 3:0:0:0: [sdc] Assuming drive cache: write through
 sdc: sdc1
sd 3:0:0:0: [sdc] Test WP failed, assume Write Enabled
sd 3:0:0:0: [sdc] Cache data unavailable
sd 3:0:0:0: [sdc] Assuming drive cache: write through
sd 3:0:0:0: [sdc] Attached SCSI removable disk
sd 3:0:0:0: [sdc] Unhandled sense code
sd 3:0:0:0: [sdc]  Result: hostbyte=0x10 driverbyte=0x08
sd 3:0:0:0: [sdc]  Sense Key : 0x3 [current]
sd 3:0:0:0: [sdc]  ASC=0x14 ASCQ=0x0
sd 3:0:0:0: [sdc] CDB: cdb[0]=0x28: 28 00 00 01 e9 00 00 00 01 00
end_request: critical target error, dev sdc, sector 125184
Buffer I/O error on device sdc, logical block 125184


Is this a kernel problem?  By the way, my memory card is fine.

Thank you.

[Juanito]

Also, compiletc depends on linux-3.0.1_api-headers, is this correct? I thought the kernel was 3.0.3.

The toolchain was built with the linux-3.0.1 api headers - I don't believe (I may be wrong) that changing to the 3.0.3 kernel requires re-building the toolchain.

[yoshi314]

Also, compiletc depends on linux-3.0.1_api-headers, is this correct? I thought the kernel was 3.0.3.

The toolchain was built with the linux-3.0.1 api headers - I don't believe (I may be wrong) that changing to the 3.0.3 kernel requires re-building the toolchain.

only thing that is really influenced by kernel headers is (e)glibc feature set during build time.

also minor releases are just security updates, as 3.0.x series is.

also, i cannot install sdl. the sdl.tcz file starts downloading but i eventually get 404 error. where should i report this ?

[Rich]

Hi hjkl
Try the following boot code:

usb-storage.quirks=VID:PID:cw

Where  VID  is the vendor ID and  PID  is the product ID for the storage device.

You can get the  VID:PID  by running  lsusb  which is found in  usb-utils.tcz

If that does not fix it you can try:

usb-storage.quirks=VID:PID:bcw

[hjkl]

Hi Rich,

Thank you for the information.  The boot code you suggested fixed the problem.
Now, my extlinux.conf looks like this:

Code: [Select]

label tc
   kernel /tc4/vmlinuz
   append vga=791 usb-storage.quirks=05e3:0700:cw initrd=/tc4/tinycore.gz

The error message I got changed from:

Code: [Select]

sd 3:0:0:0: [sdc] 125185 512-byte logical blocks: (64.0 MB/61.1 MiB)
.
.
end_request: critical target error, dev sdc, sector 125184
Buffer I/O error on device sdc, logical block 125184

to:

Code: [Select]

sd 3:0:0:0: [sdc] Adjusting the sector count from its reported value: 125185
sd 3:0:0:0: [sdc] 125184 512-byte logical blocks: (64.0 MB/61.1 MiB)

Thank you.

[curaga]

hjkl, please open a bug against the kernel's usb system with these details. It's a regression from the previous kernel.

[Juanito]

I ran some quick builds of ccache to look at the different optimizations.  The build tests failed without the -fno-omit-frame-pointer switch.  The builds finished and produced the binary but the binary failed at runtime with the testsuites.  I would recommend adding the --enable-frame-pointer into gcc to prevent any runtime problems.

Looking at http://gcc.gnu.org/onlinedocs/gcc-4.6.1/gcc/Optimize-Options.html#Optimize-Options:

-O also turns on -fomit-frame-pointer on machines where doing so does not interfere with debugging

Starting with GCC version 4.6, the default setting (when not optimizing for size) for 32-bit Linux x86 and 32-bit Darwin x86 targets has been changed to -fomit-frame-pointer. The default can be reverted to -fno-omit-frame-pointer by configuring GCC with the --enable-frame-pointer configure option.

Given:

-fomit-frame-pointer
Don't keep the frame pointer in a register for functions that don't need one. This avoids the instructions to save, set up and restore frame pointers; it also makes an extra register available in many functions. It also makes debugging impossible on some machines.

..it is somehow hard to see why including "instructions to save, set up and restore frame pointers" makes the size of compiled binaries smaller.

I'll look at this some more in the next couple of days.

[hjkl]

hjkl, please open a bug against the kernel's usb system with these details. It's a regression from the previous kernel.

Hi curaga,
I got your suggestion.  But, I'm afraid I don't know where to go from here in order to report "a bug against the kernel's usb system."  I realize that I have to learn a lot more. 

[curaga]

Hi curaga,
I got your suggestion.  But, I'm afraid I don't know where to go from here in order to report "a bug against the kernel's usb system."  I realize that I have to learn a lot more. 

It would be bugzilla.kernel.org, but kernel.org is down right now after the server was rooted.