CF card is not detected

[casm]

My WebDT 366 (Geode) has an integral Compact Flash slot which is not detected by Haiku; a SanDisk 4GB CF card is inserted in it. No apparent reference to it is made in either syslog or `listdev'.

The CF adapter is attached to the USB bus; output of `listusb -v' is attached. Connected USB devices at the time of running the command: Logitech USB keyboard; no-name USB mouse; no-name USB hub.

[casm]

WebDT 366 `listusb -v' output.

[casm]

WebDT 366 `listdev' output.

[casm]

WebDT 366 syslog output.

[mmlr]

What makes you think the card reader is attached to USB?

[casm]

Replying to mmlr:

What makes you think the card reader is attached to USB?

Community consensus - that and IIRC, it was identified as USB-attached under both XP Embedded and Puppy Linux prior to installing Haiku. I'll confirm this under Puppy Linux and update the ticket.

[mmlr]

To clarify the original question, the listusb output only shows a mouse, a keyboard, a hub and two (virtual) root hubs of the two OHCI controllers. There is no evidence of a mass storage device.

The syslog has entries from usb_disk which detects a "FLASH DISK". It does contain a GPT and a ~954MB partition according to syslog. This may be the CF Card, or a USB stick plugged in at a later point to transfer the syslog.

Without further information (for example device lists from Linux to determine if there are additional controllers we don't support) this can not be further investigated.

[pkacperski]

I have a VIA C7 based thin terminal with a built-in CompactFlash-IDE adapter on board. I usually set up an instance of Debian Linux there and it serves as a simple, ad-hoc Linux server if needed. As comfort of using virtualised Haiku is rather disputable, I decided to run it natively on the thin client. Unfortunately I failed miserably, as Haiku booted from an external USB flash drive seems to be completely helpless with dealing with the on-board CF-IDE adapter. It is aware of presence of the ATA0 disk, but it is inaccessible anyways. syslog shows multiple ATA errors:

pjk@pjk-pc ~ $ grep "ata" syslog 
KERN:   field: "disk identifier"   (RAWT): data at 0x81bd6f1c, 79 bytes 
KERN: ata 0: _DevicePresent: device 0, presence 1 
KERN: ata 0: _DevicePresent: device 1, presence 1 
KERN: ata 0: deviceMask 3 
KERN: ata 0: probing device 0 
KERN: ata 0: signature of device 0: 0x0000 
KERN: ata 0-0: model number: SanDisk SDCFHSNJC-008G                   
KERN: ata 0-0: serial number:      AMZ072315235020 
KERN: ata 0-0: firmware rev.: HDX 7.08 
KERN: ata 0-0: using DMA mode 0x12 
KERN: ata 0: identified ATA device 0 
KERN: ata 0: probing device 1 
KERN: ata 0: signature of device 1: 0x0000 
KERN: ata 0 error: device ready not set 
KERN: ata 0-1 error: sending identify request failed 
KERN: ata 0 error: command failed, error bit is set. status 0x51, error 0x04 
KERN: publish device: node 0x82b4a248, path disk/ata/0/master/raw, module drivers/disk/scsi/scsi_disk/device_v1 
KERN: ata 0-0 error: invalid target lun 1 for ATA device 
KERN: ata 0-0 error: invalid target lun 2 for ATA device 
KERN: ata 0-0 error: invalid target lun 3 for ATA device 
KERN: ata 0-0 error: invalid target lun 4 for ATA device 
KERN: ata 0-0 error: invalid target lun 5 for ATA device 
KERN: ata 0-0 error: invalid target lun 6 for ATA device 
KERN: ata 0-0 error: invalid target lun 7 for ATA device 
KERN: ata 0 error: target device not present 
KERN: ata 0 error: invalid target device 
KERN: ata 1: _DevicePresent: device 0, presence 0 
KERN: ata 1: _DevicePresent: device 1, presence 0 
KERN: ata 1: deviceMask 0 
KERN: ata 1: ignoring device 0 
KERN: ata 1: ignoring device 1 
KERN: ata 1 error: target device not present 
KERN: ata 1 error: invalid target device 
KERN: KDiskDeviceManager::_Scan(/dev/disk/ata) 
KERN: KDiskDeviceManager::_Scan(/dev/disk/ata/0) 
KERN: KDiskDeviceManager::_Scan(/dev/disk/ata/0/master) 
KERN: KDiskDeviceManager::_Scan(/dev/disk/ata/0/master/raw) 
KERN:   found device: /dev/disk/ata/0/master/raw 
KERN: ata 0 error: command failed, error bit is set. status 0x51, error 0x04 
KERN: device 0: /dev/disk/ata/0/master/raw 
KERN: ata 0 error: command failed, error bit is set. status 0x51, error 0x04 
KERN: ata 0 error: command failed, error bit is set. status 0x51, error 0x04 
KERN: ata 0 error: command failed, error bit is set. status 0x51, error 0x04 
KERN: ata 0 error: command failed, error bit is set. status 0x51, error 0x04

...and so on. I tried dd-ing USB flash drive with Haiku on to /dev/sda (that is a 8 GB compact flash card sitting on the motherboard) from Linux, but then Haiku PANICs with information that it is unable to find any boot partition. I will attach logs from Debian as soon as I finish restoring it on the device.

[pkacperski]

Haiku syslog

[pkacperski]

on Debian:

root@debian:/home/pjk# lspci -k
00:00.0 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
	Subsystem: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
	Kernel driver in use: agpgart-via
00:00.1 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
00:00.2 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
00:00.3 Host bridge: VIA Technologies, Inc. PT890 Host Bridge
00:00.4 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
00:00.7 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237/VX700 PCI Bridge
00:0f.0 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
	Subsystem: VIA Technologies, Inc. VT82C586/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE
	Kernel driver in use: pata_via
00:10.0 USB controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
	Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
	Kernel driver in use: uhci_hcd
00:10.1 USB controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
	Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
	Kernel driver in use: uhci_hcd
00:10.2 USB controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
	Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
	Kernel driver in use: uhci_hcd
00:10.3 USB controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
	Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
	Kernel driver in use: uhci_hcd
00:10.4 USB controller: VIA Technologies, Inc. USB 2.0 (rev 86)
	Subsystem: VIA Technologies, Inc. USB 2.0 Controller
	Kernel driver in use: ehci-pci
00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South]
	Subsystem: VIA Technologies, Inc. DFI KT600-AL / Soltek SL-B9D-FGR Motherboard
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
	Subsystem: VIA Technologies, Inc. K7VT2 motherboard
	Kernel driver in use: snd_via82xx
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
	Subsystem: VIA Technologies, Inc. VT6102 [Rhine II] Embeded Ethernet Controller on VT8235
	Kernel driver in use: via-rhine
01:00.0 VGA compatible controller: VIA Technologies, Inc. CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] (rev 01)
	Subsystem: VIA Technologies, Inc. CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro]

root@debian:/home/pjk# dmesg | grep -i "ata"
[    0.000000] BIOS-e820: [mem 0x000000003bee3000-0x000000003beeffff] ACPI data
[    0.000000] Memory: 951036K/981496K available (4610K kernel code, 522K rwdata, 1452K rodata, 660K init, 460K bss, 30460K reserved, 74632K highmem)
      .data : 0xc1480b8c - 0xc166fbc0   (1980 kB)
[    2.502945] Write protecting the kernel read-only data: 1456k
[    2.502953] NX-protecting the kernel data: 3580k
[    2.829450] libata version 3.00 loaded.
[    2.837512] pata_via 0000:00:0f.0: version 0.3.4
[    2.837805] pata_via 0000:00:0f.0: VIA VLink IRQ fixup, from 255 to 11
[    2.863474] scsi0 : pata_via
[    2.874969] scsi1 : pata_via
[    2.875350] ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xeb00 irq 14
[    2.875362] ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xeb08 irq 15
[    3.048462] ata1.00: CFA: SanDisk SDCFHSNJC-008G, HDX 7.08, max UDMA/100
[    3.048481] ata1.00: 15625216 sectors, multi 1: LBA48 
[    3.048501] ata1.00: limited to UDMA/33 due to 40-wire cable
[    3.056320] ata1.00: configured for UDMA/33
[    3.056703] scsi 0:0:0:0: Direct-Access     ATA      SanDisk SDCFHSNJ 7.08 PQ: 0 ANSI: 5
[    6.019056] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)

[waddlesplash]

The CF card is clearly attached via ATA, not USB.

[pulkomandy]

I may have CF cards and a machine where I can test this.

[SuperPrower]

I experience the same problem with exact same errors in syslog. I plug CF card trough adapter into my main and only ATA/IDE port in laptop, in Master mode (there is a jumper that allows to plug it as a Slave, I think). I am sure that card is working since I was able to install and boot Debian from it, while in Haiku I was unable to do anything about it with DriveSetup - every menu option is greyed out, and Haiku doesn't see existing partitions there. Even if I manually make a filesystem using a command line, after reboot all changes perish.