WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Problem with disk on chip  (Read 5220 times)

Offline jjacobs

  • Newbie
  • *
  • Posts: 34
Problem with disk on chip
« on: June 02, 2010, 06:18:39 PM »
All,

I have a problem with tinycore recognizing my MD2202-D32-P 32M M-SYSTEMS disk on chip. The DOC currently is formatted for FAT16 and runs DOS.  I ran fdisk -l which showed nothing.

I booted from the CD drive.

Offline popolon

  • Newbie
  • *
  • Posts: 5
Re: Problem with disk on chip
« Reply #1 on: June 02, 2010, 07:49:09 PM »
Maybe it does not have a partition table, just one filesystem taking the whole device (like a floppy). In this case it will not appear in fdisk -l.
You could try "fstype <device name>" where <device name> is something like /dev/msys/fla to see if a filesystem is detected on the whole device.

Offline maro

  • Hero Member
  • *****
  • Posts: 1228
Re: Problem with disk on chip
« Reply #2 on: June 02, 2010, 08:48:05 PM »
Any indication in the 'dmesg' output as what device it is recognized?

You might want to then use 'blkid' on this device. Please note that 'fstype' is using 'blkid' but throwing away some information.

Offline jjacobs

  • Newbie
  • *
  • Posts: 34
Re: Problem with disk on chip
« Reply #3 on: June 03, 2010, 10:58:18 AM »
I don't see a directory titled /dev/msys below is the result of dmesg:


Linux version 2.6.29.1-tinycore (root@box) (gcc version 4.2.2) #1337 SMP Fri Apr 10 19:12:39 EEST 2009
KERNEL supported cpus:
  Intel GenuineIntel
  AMD AuthenticAMD
  NSC Geode by NSC
  Cyrix CyrixInstead
  Centaur CentaurHauls
  Transmeta GenuineTMx86
  Transmeta TransmetaCPU
  UMC UMC UMC UMC
PAT WC disabled due to known CPU erratum.
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 0000000000097800 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 0000000008000000 (usable)
 BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
 BIOS-e820: 00000000fffc0000 - 0000000100000000 (reserved)
DMI 2.1 present.
AMI BIOS detected: BIOS may corrupt low RAM, working around it.
last_pfn = 0x8000 max_arch_pfn = 0x100000
kernel direct mapping tables up to 8000000 @ 10000-14000
RAMDISK: 07809000 - 07fde21b
ACPI Error (tbxfroot-0219): A valid RSDP was not found [20081204]
0MB HIGHMEM available.
128MB LOWMEM available.
  mapped low ram: 0 - 08000000
  low ram: 00000000 - 08000000
  bootmap 00010000 - 00011000
(9 early reservations) ==> bootmem [0000000000 - 0008000000]
  #0 [0000000000 - 0000001000]   BIOS data page ==> [0000000000 - 0000001000]
  #1 [0000001000 - 0000002000]    EX TRAMPOLINE ==> [0000001000 - 0000002000]
  #2 [0000006000 - 0000007000]       TRAMPOLINE ==> [0000006000 - 0000007000]
  #3 [0000100000 - 0000528674]    TEXT DATA BSS ==> [0000100000 - 0000528674]
  #4 [0007809000 - 0007fde21b]          RAMDISK ==> [0007809000 - 0007fde21b]
  #5 [0000529000 - 000052c000]    INIT_PG_TABLE ==> [0000529000 - 000052c000]
  #6 [0000097800 - 0000100000]    BIOS reserved ==> [0000097800 - 0000100000]
  #7 [0000010000 - 0000010000]          PGTABLE
  #8 [0000010000 - 0000011000]          BOOTMAP ==> [0000010000 - 0000011000]
Zone PFN ranges:
  DMA      0x00000010 -> 0x00001000
  Normal   0x00001000 -> 0x00008000
  HighMem  0x00008000 -> 0x00008000
Movable zone start PFN for each node
early_node_map[2] active PFN ranges
    0: 0x00000010 -> 0x00000097
    0: 0x00000100 -> 0x00008000
On node 0 totalpages: 32647
free_area_init_node: node 0, pgdat c0450d80, node_mem_map c1000200
  DMA zone: 32 pages used for memmap
  DMA zone: 0 pages reserved
  DMA zone: 3943 pages, LIFO batch:0
  Normal zone: 224 pages used for memmap
  Normal zone: 28448 pages, LIFO batch:7
SMP: Allowing 1 CPUs, 0 hotplug CPUs
Found and enabled local APIC!
nr_irqs_gsi: 16
PM: Registered nosave memory: 0000000000097000 - 00000000000a0000
PM: Registered nosave memory: 00000000000a0000 - 00000000000e0000
PM: Registered nosave memory: 00000000000e0000 - 0000000000100000
Allocating PCI resources starting at 10000000 (gap: 8000000:f6e00000)
NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:1 nr_node_ids:1
PERCPU: Allocating 32768 bytes of per cpu data
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32391
Kernel command line: initrd=/boot/tinycore.gz quiet max_loop=256 BOOT_IMAGE=/boot/bzImage vga=791
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 512 (order: 9, 2048 bytes)
Fast TSC calibration using PIT
Detected 729.747 MHz processor.
Console: colour dummy device 80x25
console [tty0] enabled
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 116964k/131072k available (2433k kernel code, 13480k reserved, 1088k data, 344k init, 0k highmem)
virtual kernel memory layout:
    fixmap  : 0xfff50000 - 0xfffff000   ( 700 kB)
    pkmap   : 0xff800000 - 0xffc00000   (4096 kB)
    vmalloc : 0xc8800000 - 0xff7fe000   ( 879 MB)
    lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
      .init : 0xc0477000 - 0xc04cd000   ( 344 kB)
      .data : 0xc0360468 - 0xc04707b0   (1088 kB)
      .text : 0xc0100000 - 0xc0360468   (2433 kB)
Checking if this processor honours the WP bit even in supervisor mode...Ok.
Calibrating delay loop (skipped), value calculated using timer frequency.. 1460.30 BogoMIPS (lpj=2432490)
Mount-cache hash table entries: 512
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 128K
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 9k freed
weird, boot CPU (#0) not listed by the BIOS.
SMP motherboard not detected.
SMP disabled
Brought up 1 CPUs
Total of 1 processors activated (1460.30 BogoMIPS).
net_namespace: 944 bytes
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xfdb81, last bus=0
PCI: Using configuration type 1 for base access
bio: create slab <bio-0> at 0
ACPI: Interpreter disabled.
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
pci 0000:00:00.0: reg 10 32bit mmio: [0xf8000000-0xfbffffff]
pci 0000:00:07.1: reg 20 io port: [0xffa0-0xffaf]
pci 0000:00:07.2: reg 20 io port: [0xef80-0xef9f]
* Found PM-Timer Bug on the chipset. Due to workarounds for a bug,
* this clock source is slow. Consider trying other clock sources
pci 0000:00:07.3: quirk: region 0400-043f claimed by PIIX4 ACPI
pci 0000:00:07.3: quirk: region 0440-044f claimed by PIIX4 SMB
pci 0000:00:07.3: PIIX4 devres C PIO at 0290-0297
pci 0000:00:0e.0: reg 10 32bit mmio: [0x000000-0x000fff]
pci 0000:00:0e.0: reg 14 io port: [0x00-0x3f]
pci 0000:00:0e.0: reg 18 32bit mmio: [0x000000-0x01ffff]
pci 0000:00:0e.0: supports D1 D2
pci 0000:00:0e.0: PME# supported from D0 D1 D2 D3hot
pci 0000:00:0e.0: PME# disabled
pci 0000:00:12.0: reg 10 32bit mmio: [0x000000-0x00007f]
pci 0000:00:12.0: reg 14 io port: [0x00-0x7f]
pci 0000:00:12.0: reg 18 io port: [0x00-0xff]
pci 0000:00:14.0: reg 10 32bit mmio: [0xfd000000-0xfdffffff]
pci 0000:00:14.0: reg 30 32bit mmio: [0xfebf0000-0xfebfffff]
pci 0000:00:14.0: supports D1 D2
pnp: PnP ACPI: disabled
PnPBIOS: Scanning system for PnP BIOS support...
PnPBIOS: Found PnP BIOS installation structure at 0xc00f74e0
PnPBIOS: PnP BIOS version 1.0, entry 0xf0000:0x6d34, dseg 0xf0000
pnp 00:08: io resource (0x10-0x1f) overlaps 0000:00:0e.0 BAR 1 (0x0-0x3f), disabling
pnp 00:08: io resource (0x22-0x3f) overlaps 0000:00:0e.0 BAR 1 (0x0-0x3f), disabling
pnp 00:08: io resource (0x10-0x1f) overlaps 0000:00:12.0 BAR 1 (0x0-0x7f), disabling
pnp 00:08: io resource (0x22-0x3f) overlaps 0000:00:12.0 BAR 1 (0x0-0x7f), disabling
pnp 00:08: io resource (0x50-0x52) overlaps 0000:00:12.0 BAR 1 (0x0-0x7f), disabling
pnp 00:08: io resource (0x72-0x77) overlaps 0000:00:12.0 BAR 1 (0x0-0x7f), disabling
pnp 00:08: io resource (0x10-0x1f) overlaps 0000:00:12.0 BAR 2 (0x0-0xff), disabling
pnp 00:08: io resource (0x22-0x3f) overlaps 0000:00:12.0 BAR 2 (0x0-0xff), disabling
pnp 00:08: io resource (0x50-0x52) overlaps 0000:00:12.0 BAR 2 (0x0-0xff), disabling
pnp 00:08: io resource (0x72-0x77) overlaps 0000:00:12.0 BAR 2 (0x0-0xff), disabling
pnp 00:08: io resource (0x91-0x93) overlaps 0000:00:12.0 BAR 2 (0x0-0xff), disabling
pnp 00:08: io resource (0xa2-0xbe) overlaps 0000:00:12.0 BAR 2 (0x0-0xff), disabling
PnPBIOS: 15 nodes reported by PnP BIOS; 15 recorded by driver
system 00:00: iomem range 0x0-0x9fbff could not be reserved
system 00:00: iomem range 0x9fc00-0x9ffff could not be reserved
system 00:00: iomem range 0xe0000-0xfffff could not be reserved
system 00:00: iomem range 0x100000-0x7ffffff could not be reserved
system 00:00: iomem range 0xfee00000-0xfee00fff has been reserved
system 00:00: iomem range 0xfffc0000-0xffffffff has been reserved
system 00:08: ioport range 0x4d0-0x4d1 has been reserved
system 00:08: ioport range 0xcf8-0xcff could not be reserved
system 00:08: ioport range 0x400-0x43f has been reserved
system 00:08: ioport range 0x440-0x44f has been reserved
system 00:09: ioport range 0x290-0x297 has been reserved
pci_bus 0000:00: resource 0 io:  [0x00-0xffff]
pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffff]
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
NET: Registered protocol family 1
checking if image is initramfs... it is
Freeing initrd memory: 8020k freed
fuse init (API version 7.11)
msgmni has been set to 244
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler deadline registered (default)
pci 0000:00:00.0: Limiting direct PCI/PCI transfers
pci 0000:00:14.0: Boot video device
vesafb: framebuffer at 0xfd000000, mapped to 0xc8880000, using 3072k, total 4096k
vesafb: mode is 1024x768x16, linelength=2048, pages=1
vesafb: protected mode interface info at ca7f:000a
vesafb: pmi: set display start = c00ca82f, set palette = c00ca883
vesafb: pmi: ports =
vesafb: scrolling: redraw
vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
Console: switching to colour frame buffer device 128x48
fb0: VESA VGA frame buffer device
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Real Time Clock Driver v1.12b
Non-volatile memory driver v1.3
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
00:0b: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:0c: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
brd: module loaded
loop: loaded (max 256 devices)
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
NET: Registered protocol family 24
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Uniform Multi-Platform E-IDE driver
piix 0000:00:07.1: IDE controller (0x8086:0x7111 rev 0x01)
piix 0000:00:07.1: IDE port disabled
piix 0000:00:07.1: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xffa0-0xffa7
Probing IDE interface ide0...
hdb: GCR-8481B, ATAPI CD/DVD-ROM drive
hdb: host max PIO4 wanted PIO255(auto-tune) selected PIO4
hdb: UDMA/33 mode selected
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide_generic: please use "probe_mask=0x3f" module parameter for probing all legacy ISA IDE ports
ide-gd driver 1.18
ide-cd driver 5.00
ide-cd: hdb: ATAPI 48X CD-ROM drive, 128kB Cache
Uniform CD-ROM driver Revision: 3.20
Driver 'sd' needs updating - please use bus_type methods
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
uhci_hcd: USB Universal Host Controller Interface driver
uhci_hcd 0000:00:07.2: enabling device (0000 -> 0001)
uhci_hcd 0000:00:07.2: can't find IRQ for PCI INT D; please try using pci=biosirq
uhci_hcd 0000:00:07.2: Found HC with no IRQ.  Check BIOS/PCI 0000:00:07.2 setup!
uhci_hcd 0000:00:07.2: init 0000:00:07.2 fail, -19
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
PNP: PS/2 Controller [PNP0303] at 0x60,0x64 irq 1
PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
cpuidle: using governor ladder
cpuidle: using governor menu
padlock: VIA PadLock not detected.
padlock: VIA PadLock Hash Engine not detected.
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 15
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
IO APIC resources could be not be allocated.
Using IPI No-Shortcut mode
Freeing unused kernel memory: 344k freed
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
e100: Intel(R) PRO/100 Network Driver, 3.5.23-k6-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
e100 0000:00:0e.0: enabling device (0000 -> 0003)
e100 0000:00:0e.0: can't find IRQ for PCI INT A; please try using pci=biosirq
e100 0000:00:0e.0: setting latency timer to 64
e100 0000:00:0e.0: PME# disabled
e100: eth0: e100_probe: addr 0x10020000, irq 0, MAC addr 00:07:b8:dc:52:ea
squashfs: version 4.0 (2009/01/31) Phillip Lougher
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
e100 0000:00:0e.0: firmware: requesting e100/d102e_ucode.bin
e100: eth0: e100_request_firmware: Failed to load firmware "e100/d102e_ucode.bin": -2
ISO 9660 Extensions: Microsoft Joliet Level 3
ISOFS: changing to secondary root
e100 0000:00:0e.0: firmware: requesting e100/d102e_ucode.bin


Offline ^thehatsrule^

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 1726
Re: Problem with disk on chip
« Reply #4 on: June 03, 2010, 11:18:27 AM »
See the mtd-* extension for the modules.

Offline jjacobs

  • Newbie
  • *
  • Posts: 34
Re: Problem with disk on chip
« Reply #5 on: June 04, 2010, 11:48:29 AM »
^thehatsrule^

I installed the mtd extension, but I still don't know where to look for the device.  There is still no /dev/msys directory.

I really don't know what to expect from mtd. Is there documentation?

I've looked at what documentation I could find on the web and am only more confused. After installing mtd I see a directory containing gz files in /usr/local/lib/modules/2.6.29.1-tinycore/kernel/drivers/mtd/test. In order to use those do I need to unzip them?  There also appear to be zipped kernel modules one directory up.  Do I need to unzip and insmod those?

I may be taking this out of context, but in the MTD documentation from http://www.linux-mtd.infradead.org/faq/general.html I read, "The block devices are then accessible via /dev/mtdblockX device nodes." I do not see any mtdblockX devices in /dev.

« Last Edit: June 04, 2010, 01:16:34 PM by jjacobs »

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 11049
Re: Problem with disk on chip
« Reply #6 on: June 04, 2010, 04:15:36 PM »
You could modprobe the necessary module if it isn't autodetected. For example for doc2000.ko.gz it is "sudo modprobe doc2000" (I'm not sure that's the right one, just an example).
The only barriers that can stop you are the ones you create yourself.

Offline jjacobs

  • Newbie
  • *
  • Posts: 34
Re: Problem with disk on chip
« Reply #7 on: June 07, 2010, 11:53:39 AM »
I tried your suggestion curaga, but was still unable to see the device. 

Looking on the net I found a patch to the 2.4 kernel for this DOC.  I think its a bad idea to try to use the old 2.4 kernel, so I am suggesting my company dump the DOC and go to a hard drive.

Offline ^thehatsrule^

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 1726
Re: Problem with disk on chip
« Reply #8 on: June 08, 2010, 01:00:48 AM »
Did you try other modules...?

Looking through the modules (ie modinfo) shows that a good starting point might be `modprobe diskonchip`.  Then maybe looking in /proc/mtd or /sys/class/mtd or dmesg might be useful.  Then look into "higher levels" things such as FTLs and so on.

My guess is that that patch is probably not that useful anyways (code is probably already available in the kernel tree).