**** BEGIN LOGGING AT Sat Mar 15 02:59:56 2008 Mar 15 13:26:40 hmmm. Mar 15 13:28:00 just built a fresh nslu2le and still no joy with the mounting anything. Mar 15 13:28:07 gonna try be. Mar 15 14:10:02 hi Mar 15 14:10:34 hi Varoudis Mar 15 14:13:50 hello Mar 16 00:55:40 anyone awake? Mar 16 02:12:35 rwhitby: give me a shout if you have a moment pls. Mar 16 02:12:45 im at my wits end with my slug :( Mar 16 02:15:56 HRH_H_Crab: I'm here, whassup? Mar 16 02:16:06 hey! Mar 16 02:16:08 well, Mar 16 02:16:18 If it's about Angstrom, yep it's broken with a null password. Mar 16 02:16:24 the good news is, ive taught myself oe! Mar 16 02:16:26 yeah, Mar 16 02:16:31 ive worked round that now. Mar 16 02:16:39 i can build images with preset passwords! Mar 16 02:16:41 \o/ Mar 16 02:16:49 ive built little endian ones, and big endian ones, Mar 16 02:16:51 and they boot, Mar 16 02:16:53 and work, Mar 16 02:16:56 and i can log in. Mar 16 02:17:07 but ive come up against an unexpected impasse. Mar 16 02:17:16 ive loaded the various usb modules, Mar 16 02:17:27 and i can detect devices in dmesg. Mar 16 02:17:29 but... Mar 16 02:17:35 i cannot mount anything. Mar 16 02:17:41 hang on, let me pastebin... Mar 16 02:19:19 http://pastebin.com/d36f314a1 Mar 16 02:19:35 ive tried this with the little endian image, and the big endian image. Mar 16 02:19:41 the memory stick works fine in my laptop. Mar 16 02:19:58 ive also tried larger external disks and i get the same issue. Mar 16 02:20:11 strangely, the slug is more than happy to format my media! Mar 16 02:20:15 it just won't mount it. Mar 16 02:21:25 what does /proc/filesystems have in it? Mar 16 02:21:46 hmmm Mar 16 02:22:02 root@nslu2be:~# more /proc/filesystems Mar 16 02:22:02 nodev sysfs Mar 16 02:22:02 nodev rootfs Mar 16 02:22:02 nodev bdev Mar 16 02:22:02 nodev proc Mar 16 02:22:04 nodev sockfs Mar 16 02:22:07 nodev usbfs Mar 16 02:22:10 nodev pipefs Mar 16 02:22:12 nodev anon_inodefs Mar 16 02:22:15 nodev futexfs Mar 16 02:22:17 nodev tmpfs Mar 16 02:22:20 nodev inotifyfs Mar 16 02:22:22 nodev devpts Mar 16 02:22:25 nodev ramfs Mar 16 02:22:27 nodev jffs2 Mar 16 02:22:29 aaah... Mar 16 02:22:43 so is that the "no such device" that its speaking of? Mar 16 02:24:02 you need to load the kernel modules for the filesystems you want to load Mar 16 02:24:09 aaaah! Mar 16 02:24:14 im a buffoon. Mar 16 02:24:16 o.k. Mar 16 02:24:28 thanks, i'll give that a try. Mar 16 02:25:30 np Mar 16 02:30:24 im guessing im going to have to bitbake that as i can't seem to find it? Mar 16 02:30:36 something like bitbake kernel-module-ext2 or whatever? Mar 16 02:30:41 and then scp it across? Mar 16 02:31:13 they should all be in the feeds Mar 16 02:31:22 aaah! Mar 16 02:31:24 \o/ Mar 16 02:32:36 while you are about, if its not too annoying a question, can you briefly explain to me if there are any issues surrounding endian-ness i should consider? Mar 16 02:32:48 im no programmer, but i have a rough idea of what it means. Mar 16 02:33:01 i started out using le images, but im currently running a be image. Mar 16 02:33:17 are there any pros / cons i should be aware of? Mar 16 02:33:25 just that some packages (like usb camera drivers) are badly written for one endianness and don't work on the other. Mar 16 02:33:53 networking is faster in BE, cause you don't have to swap fields, but on a slug that is swamped by the slowness of the usb anyway so it doesn't matter. Mar 16 02:34:08 so just choose based on the packages you need to run Mar 16 02:34:16 cool Mar 16 02:34:17 99% of the packages will run on either Mar 16 02:34:20 thanks for everything Mar 16 02:39:51 i think i made a mistake using nslu2be, i should have used ixp4xxbe shouldn't i? Mar 16 02:40:06 there seems to be a glitch in these feeds. Mar 16 02:40:22 nm. i can work on that tomorrow. **** ENDING LOGGING AT Sun Mar 16 02:59:56 2008