On Mon, Jun 21, 2004 at 08:58:43PM -0400, Emma Jane Hogbin wrote:
> I'm recompiling again with as much as possible as modules instead of
> compiled directly into the kernel. I'm sure that I'm running the right
> kernel; the iPod is brand new. I can only assume that it is fine. It
> definitely turns on and is recognized.

Module                  Size  Used by
hfsplus                58116  0 
hfs                    45316  0 
sbp2                   23944  1 
sg                     32800  0 
sd_mod                 18688  0 
raw1394                29292  0 
nvidia               2074984  14 
snd_pcm_oss            52132  0 
orinoco_cs              9224  1 
orinoco                40460  1 orinoco_cs
hermes                  8832  2 orinoco_cs,orinoco
snd_mixer_oss          19584  1 snd_pcm_oss
ds                     18180  7 orinoco_cs
yenta_socket           20992  2 
pcmcia_core            61892  3 orinoco_cs,ds,yenta_socket
ohci1394               34308  0 
ieee1394              105652  3 sbp2,raw1394,ohci1394
snd_ali5451            22980  0 
snd_ac97_codec         62596  1 snd_ali5451
snd_pcm                91940  2 snd_pcm_oss,snd_ali5451
snd_page_alloc         11396  1 snd_pcm
snd_timer              23812  1 snd_pcm
snd                    51300  6 
snd_pcm_oss,snd_mixer_oss,snd_ali5451,snd_ac97_codec,snd_pcm,snd_timer
soundcore               9568  1 snd
button                  6552  0 
battery                 9740  0 
ac                      5132  0 
fan                     4236  0 
thermal                12944  0 
processor              17584  1 thermal


I've updated /etc/fstab to try each of:
        auto
        hfs
        hfsplus
        vfat

It's definitely on /dev/sda but i'm getting this error message any time I
try to set a file system type:
smeagol:/mnt 21:28:04 $ mount ipod2
mount: wrong fs type, bad option, bad superblock on /dev/sda2,
       or too many mounted file systems

And this one if I try to use auto:
mount: I could not determine the filesystem type, and none was specified

But I guess this is because the auto mount already caught it:

/dev/hda1 / unknown rw,errors=remount-ro 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
devpts /dev/pts devpts rw,gid=5,mode=620 0 0
tmpfs /dev/shm tmpfs rw 0 0
usbfs /proc/bus/usb usbfs rw 0 0
/dev/hda5 /usr ext2 rw 0 0
/dev/hda7 /var ext2 rw 0 0
/dev/hda8 /tmp ext2 rw 0 0
/dev/hda9 /home ext2 rw 0 0
/dev/hda10 /cdrom ext2 rw 0 0
/dev/hda11 /web ext2 rw 0 0
/dev/hda12 /cvsroot ext2 rw 0 0
/dev/hda13 /safety ext2 rw 0 0
/dev/hda14 /backups ext2 rw 0 0
automount(pid1813) /var/autofs/misc autofs rw,fd=5,pgrp=1813,minproto=2,maxproto=4 0 0
automount(pid1839) /var/autofs/net autofs rw,fd=5,pgrp=1839,minproto=2,maxproto=4 0 0
automount(pid1871) /var/autofs/removable autofs 
rw,fd=5,pgrp=1871,minproto=2,maxproto=4 0 0


-- 
Emma Jane Hogbin
[[ 416 417 2868 ][ www.xtrinsic.com ]]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to