From: Jeff R. <bue...@gm...> - 2006-09-27 01:19:51
|
Well I finally got a custom 1092 jffs2 built and got it working on my gumstix. I added Openssh and cKermit to the build. Went from 773 to 1092.. not a bad jump. But I have noticed there is no HDA node, therefore no mounting the CF. How do I remedy this problem? Thanks Jeff Robertson |
From: Jim F. <jf...@gm...> - 2006-09-27 02:36:58
|
Jeff, On 9/26/06, Jeff Robertson <bue...@gm...> wrote: > > Well I finally got a custom 1092 jffs2 built and got it working on my > gumstix. I added Openssh and cKermit to the build. Went from 773 to 1092.. > not a bad jump. But I have noticed there is no HDA node, therefore no > mounting the CF. How do I remedy this problem? > > Not sure about 1092 but I ran into a similar problem a couple of days ago when I went from 773 to 1078. I found a suggestion in the archives to: modprobe ide-disk This generated the hda device nodes and I was able to mount after that. -- Jim Felsheim jf...@gm... |
From: Jeff R. <bue...@gm...> - 2006-09-27 03:28:00
|
Seems like there are a few people having this problem. I did the modprobe >ide-disk and then followed it with a >mount -t vfat /dev/hda1 /mnt/cf . The CF came up nicely. Now what files do I need to modifiy so it goes automatically? modprobe.conf, modules, rc.modules or udev.conf? On 9/26/06, Jim Felsheim <jf...@gm...> wrote: > > Jeff, > > On 9/26/06, Jeff Robertson <bue...@gm...> wrote: > > > > Well I finally got a custom 1092 jffs2 built and got it working on my > > gumstix. I added Openssh and cKermit to the build. Went from 773 to 1092.. > > not a bad jump. But I have noticed there is no HDA node, therefore no > > mounting the CF. How do I remedy this problem? > > > > > > Not sure about 1092 but I ran into a similar problem a couple of days ago > when I went from 773 to 1078. I found a suggestion in the archives to: > > modprobe ide-disk > > This generated the hda device nodes and I was able to mount after that. > > > -- > Jim Felsheim > jf...@gm... > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > |
From: Dave H. <dhy...@gm...> - 2006-09-27 03:51:06
|
Hi Jeff, > I did the modprobe >ide-disk and then followed it with a >mount -t vfat > /dev/hda1 /mnt/cf . The CF came up nicely. Now what files do I need to > modifiy so it goes automatically? modprobe.conf, modules, rc.modules or > udev.conf? Add the following lines to /etc/modules ide-disk vfat I then copied the mmc line and adjusted (in /etc/fstab) /dev/hda1 /mnt/cf vfat sync,noauto 0 0 Finally, I added the following to /etc/inittab after the rcS start line: ::sysinit:/etc/init.d/rcS start ::sysinit:/bin/mount /mnt/cf Then /mnt/cf was mounted when I logged in. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Craig H. <cr...@gu...> - 2006-09-27 19:10:52
|
On Sep 26, 2006, at 8:51 PM, Dave Hylands wrote: > Hi Jeff, > >> I did the modprobe >ide-disk and then followed it with a >mount -t >> vfat >> /dev/hda1 /mnt/cf . The CF came up nicely. Now what files do I >> need to >> modifiy so it goes automatically? modprobe.conf, modules, >> rc.modules or >> udev.conf? > > Add the following lines to /etc/modules > > ide-disk > vfat > > I then copied the mmc line and adjusted (in /etc/fstab) > > /dev/hda1 /mnt/cf vfat sync,noauto > 0 0 > > Finally, I added the following to /etc/inittab after the rcS start > line: > ::sysinit:/etc/init.d/rcS start > ::sysinit:/bin/mount /mnt/cf > > Then /mnt/cf was mounted when I logged in. I think a "better" way to do it (ie more generic) would be to modify the udev rules so that when it sees an IDE device appear, it loads ide-disk correctly, and then even have a rule whereby it then runs fdisk -l against the new device, figures out the partitions and mounts the intelligently somewhere, possibly creating mountpoints under /mnt or something... It likely wouldn't be more than a line or two of udev rules; I'm kind of busy right now with a stack of other stuff, but it shouldn't be too hard modulo learning how to do udev rules, which is kind of lacking in all the online documentation I've ever found. C |