Re: msdos Zip on Pismo internal drive?
On Thu, Feb 17, 2005 at 03:19:46PM -0500, vze26m98 wrote:
> Hi all-
>
> More newbie questions:
>
> I've got a stable Woody distro on my Pismo laptop and an internal VST
> 250 meg Zip drive in the CD Rom bay.
>
> I can mount an HFS formatted Zip like this:
>
> mount -t hfs /dev/hde ./zip
>
> ...and I can of course mount and read ISO9660 CDs when the CD in is the
> bay.
>
> I have the msdos driver loading, I think, although the output of dmesg
> attached below isn't too encouraging. (if anyone actually reads the
> dump, the msdos driver is called between the usb audio driver the
> appletalk driver...)
>
> Any pointers?
>
> Best,
>
> Charles Turner
>
>
> ====================================
>
> Memory BAT mapping: BAT2=256Mb, BAT3=64Mb, residual: 0Mb
> Total memory = 320MB; using 2048kB for hash table (at c0400000)
> Linux version 2.4.18-newpmac (root@voltaire) (gcc version 2.95.4
> 20011002 (Debian prerelease)) #1 Thu Mar 14 22:44:49 EST 2002
> Found Uninorth memory controller & host bridge, revision: 8
> Found a Keylargo mac-io controller, rev: 3, mapped at 0xfdf7f000
> Processor NAP mode on idle enabled.
> PowerMac motherboard: PowerBook Pismo
> Found UniNorth PCI host bridge at 0xf0000000. Firmware bus number: 0->0
> Found UniNorth PCI host bridge at 0xf2000000. Firmware bus number: 0->1
> Found UniNorth PCI host bridge at 0xf4000000. Firmware bus number: 0->0
> PMU driver 2 initialized for Core99, firmware: 0c
> On node 0 totalpages: 81920
> zone(0): 81920 pages.
> zone(1): 0 pages.
> zone(2): 0 pages.
> Kernel command line: root=/dev/hda11 ro
> PowerMac using OpenPIC irq controller
> OpenPIC Version 1.2 (4 CPUs and 64 IRQ sources) at fc731000
> OpenPIC timer frequency is 4.166666 MHz
> GMT Delta read from XPRAM: -300 minutes, DST: off
> via_calibrate_decr: ticks per jiffy = 249664 (1497989 ticks)
> Console: colour dummy device 80x25
> Calibrating delay loop... 797.90 BogoMIPS
> Memory: 317028k available (1828k kernel code, 952k data, 284k init, 0k
> highmem)
> AGP special page: 0xd3fff000
> Dentry-cache hash table entries: 65536 (order: 7, 524288 bytes)
> Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
> Mount-cache hash table entries: 8192 (order: 4, 65536 bytes)
> Buffer-cache hash table entries: 32768 (order: 5, 131072 bytes)
> Page-cache hash table entries: 131072 (order: 7, 524288 bytes)
> POSIX conformance testing by UNIFIX
> PCI: Probing PCI hardware
> Fixup res 1 (101) of dev 00:10.0: 400 -> 802400
> Can't get bus-range for /pci@f2000000/cardbus@1a
> PCI->OF bus map:
> 0 -> 0
> 1 -> 0
> 6 -> 0
> PCI:00:10.0: Resource 0: a4000000-a7ffffff (f=1208)
> PCI:00:10.0: Resource 2: a0000000-a0003fff (f=200)
> PCI:01:17.0: Resource 0: 80000000-8007ffff (f=200)
> PCI:01:1a.0: Resource 0: 80080000-80080fff (f=200)
> PCI:06:0f.0: Resource 0: f5200000-f53fffff (f=200)
> PCI:00:10.0: Resource 1: 00802400-008024ff (f=101)
> PCI:01:18.0: Resource 0: 80082000-80082fff (f=200)
> PCI:01:19.0: Resource 0: 80081000-80081fff (f=200)
> PCI:06:0e.0: Resource 0: f5000000-f5000fff (f=200)
> mediabay0: Registered KeyLargo media-bay
> mediabay0: powering down
> mediabay0: switching to 3
> mediabay0: powering up
> mediabay0: enabling (kind:3)
> mediabay0: waiting reset (kind:3)
> mediabay0: waiting IDE reset (kind:3)
> mediabay0: waiting IDE ready (kind:3)
> mediabay0: up before IDE init
> Linux NET4.0 for Linux 2.4
> Based upon Swansea University Computer Society NET3.039
> Initializing RT netlink socket
> Thermal assist unit using timers, shrink_timer: 200 jiffies
> Starting kswapd
> VFS: Diskquotas version dquot_6.4.0 initialized
> Journalled Block Device driver loaded
> PCI: Enabling device 00:10.0 (0086 -> 0087)
> aty128fb: Rage Mobility M3 (AGP) [chip rev 0x0] 8M 128-bit SDR SGRAM
> (1:1)
> Console: switching to colour frame buffer device 128x48
> Registered "ati" backlight controller, level: 7/15
> fb0: ATY Rage128 frame buffer device on PCI
> no framebuffer address found for
> /pci@f0000000/ATY,RageM3pParent@10/ATY,RageM3pB
> input0: Macintosh mouse button emulation
> pty: 256 Unix98 ptys configured
> block: 128 slots per queue, batch=32
> RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
> Uniform Multi-Platform E-IDE driver Revision: 6.31
> ide: Assuming 33MHz system bus speed for PIO modes; override with
> idebus=xx
> IN from bad port cfc at c00f5598
> IN from bad port cfc at c00f5598
> IN from bad port cfc at c00f5598
> IN from bad port cfc at c00f5598
> IN from bad port cfc at c00f5598
> IN from bad port cfc at c00f5598
> IN from bad port cfc at c00f5598
> IN from bad port cfc at c00f5598
> IN from bad port cfc at c00f5598
> IN from bad port cfc at c00f5598
> IN from bad port cfc at c00f5598
> IN from bad port cfc at c00f5598
> IN from bad port cfc at c00f5598
> IN from bad port cfc at c00f5598
> IN from bad port cfc at c00f5598
> IN from bad port cfc at c00f5598
> IN from bad port cfc at c00f5598
> IN from bad port cfc at c00f5598
> IN from bad port cfc at c00f5598
> IN from bad port cfc at c00f5598
> IN from bad port cfc at c00f5598
> IN from bad port cfc at c00f5598
> IN from bad port cfc at c00f5598
> IN from bad port cfc at c00f5598
> IN from bad port cfc at c00f5598
> IN from bad port cfc at c00f5598
> IN from bad port cfc at c00f5598
> IN from bad port cfc at c00f5598
> IN from bad port cfc at c00f5598
> IN from bad port cfc at c00f5598
> IN from bad port cfc at c00f5598
> IN from bad port cfc at c00f5598
> IN from bad port c000 at c00f56ac
> IN from bad port c100 at c00f56ac
> IN from bad port c200 at c00f56ac
> IN from bad port c300 at c00f56ac
> IN from bad port c400 at c00f56ac
> IN from bad port c500 at c00f56ac
> IN from bad port c600 at c00f56ac
> IN from bad port c700 at c00f56ac
> IN from bad port c800 at c00f56ac
> IN from bad port c900 at c00f56ac
> IN from bad port ca00 at c00f56ac
> IN from bad port cb00 at c00f56ac
> IN from bad port cc00 at c00f56ac
> IN from bad port cd00 at c00f56ac
> IN from bad port ce00 at c00f56ac
> IN from bad port cf00 at c00f56ac
It's totally unrelated to your problem, but please
remove the CMD640 from your configuration. These
messages are an attempt to access PCI config space
bypassing the kernel functions.
On 2.6 this driver is X86 only, and what it does
is too ugly for words. The only possible cure for
this code is euthanasy :-)
Gabriel
Reply to: