**** BEGIN LOGGING AT Mon Jan 01 02:59:59 2007 Jan 01 10:23:23 Morning all Jan 01 10:23:39 sorry - try again with a name change..morning all! Jan 01 10:47:42 can anyone explain winscp to me? Jan 01 11:42:00 hello all - anyone help me out with thttpd? Jan 01 11:42:46 i had it all running and working yesterday and could access on the internet my website..but i edited the files today and it just wont display now - i get this error: here was an unusual problem serving the requested URL - for the web page Jan 01 11:43:09 tried restarting it and things - makes no difference Jan 01 11:46:06 Hello. I'm unclear: does the nslu2 have an mmu? Is it running ucLinux or "normal" linux? Jan 01 11:46:38 I couldn't find out reading the nslu2-linux.org website. Jan 01 12:04:16 anyone have any idea for my website problem? Jan 01 12:24:48 ? Jan 01 12:34:23 really bugging me Jan 01 12:46:05 m1ch how did you edit the files? Jan 01 12:46:54 i deleted the old ones...and copied in some new ones (a new website infact) in windows Jan 01 12:47:14 i'm going to guess you will say that is the wrong way to go about it:) Jan 01 12:50:38 which files did you delete? Jan 01 12:50:48 in the admin/website part... Jan 01 12:51:04 i deleted index.html, page1.html etc - all the test files i had for a website Jan 01 12:51:19 i deleted them...and copied in my own website Jan 01 12:51:31 through the windows interface...not through putty Jan 01 12:51:45 did i need to delete them and copy them in using putty for it to work? Jan 01 12:52:45 so you used the samba/cifs share to copy the files over? Jan 01 12:53:05 yes Jan 01 12:53:14 i've just tried again with putty to move them that way as well Jan 01 12:54:05 now when i type my slug address (192.168.1.77) as my website is on port 80 now..i get this error:There was an unusual problem serving the requested URL. Jan 01 12:54:19 last night before i messed i got my website! Jan 01 12:56:51 any ideas? Jan 01 13:03:37 nick /m1ch Jan 01 13:04:06 my website works now again Jan 01 13:04:15 i had to copy in putty, rather than copy in windows Jan 01 17:24:17 Heyy i've got a problem with been unable to connect to my debian slug slug after an apt-get upgrade Jan 01 17:24:44 restarted with same problem, wont ping it either, the ready/status light is flashing between green/yellow as it always has Jan 01 17:24:58 do i need to be here or one of the debian channels for some help? Jan 01 17:30:27 Do the slug's have a serial port? Jan 01 17:30:41 * pflanze is a newbie and does not have a NSLU2 Jan 01 17:32:02 not this one, unfortunately Jan 01 17:34:44 Maybe detach the storage and mount it from a PC? (just an idea) Jan 01 17:34:54 and read the logs? Jan 01 17:35:50 i was thinking that, it'll be ext3 wont it? Jan 01 17:36:40 able to boot without the storage? Jan 01 17:36:56 i wouldnt have thought so, as it runs like a normal pc using the storage Jan 01 17:37:16 at best, i may get the installer... but it writes the kernel stuff near the end Jan 01 17:37:52 at first i thought it may have just been ssh being funny, as the apt-get upgrade updated it, but when it doesnt ping, even though theres the led for network... Jan 01 17:39:04 maybe the network is f*cked up (like the proprietary code not loaded or something?) (beware of my ignorance) Jan 01 17:39:42 if you have linux running on a pc, it should recognize the partition type automatically. Jan 01 17:39:50 hmm, thats why i thought a reboot might have sorted it Jan 01 17:39:54 s/partition/filesystem/ type Jan 01 17:40:11 its a windows box im on... Jan 01 17:40:17 ive got an ext3 reader Jan 01 17:40:45 hmm, maybe you're better off burning knoppix onto a cd and boot from that. Jan 01 17:40:46 ext2 or whatever explore2fs is Jan 01 17:41:02 ive got a knoppix disk about, but my pc's dont always like it Jan 01 17:41:09 i can read from the disk :) Jan 01 17:42:10 I don't know about anything about windows. Maybe it's even safe. Jan 01 17:42:22 all i can do is read from it Jan 01 17:42:27 or you could switch it to read-only. Jan 01 17:42:28 ah. Jan 01 17:42:33 heh Jan 01 17:42:38 where would the logs be stored? Jan 01 17:42:39 that should give you enough to read the logs. Jan 01 17:42:43 var/log Jan 01 17:43:05 ok, in that root folder? or one of the sub folders Jan 01 17:43:34 from the top. like /var/log/ Jan 01 17:43:40 yeah Jan 01 17:43:55 i was wondering if we needed a folder inside that, but none of them are relevant i think Jan 01 17:44:24 no, list the files sorted by modification time, and look into the latest ones. Jan 01 17:45:07 strange, the clock seems to be a 11 months behind Jan 01 17:45:08 no matter Jan 01 17:45:27 syslog and messages were the last updated Jan 01 17:46:08 syslog: Jan 01 17:46:09 Feb 3 13:13:25 SLUG -- MARK -- Jan 01 17:46:09 Feb 3 13:17:02 SLUG /USR/SBIN/CRON[1884]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Jan 01 17:46:09 Feb 3 13:33:25 SLUG -- MARK -- Jan 01 17:46:31 well from the mtime you should see the year. Jan 01 17:46:53 maybe it's way off anyway. Jan 01 17:47:06 yeah, its reporting 3rd February 2006 Jan 01 17:47:37 so im going by the newest date Jan 01 17:47:51 so check the other logs, esp. "boot","daemon", "messages", "syslog" Jan 01 17:48:01 ah and "kern.log" Jan 01 17:48:49 boot & daemon nothing Jan 01 17:49:14 (btw if time did change, you have to be careful about the file ordering. just look at the files without .0 etc attached) Jan 01 17:49:40 yeah Jan 01 17:50:35 btw have you waited long enough after boot? it might be it was doing a disk check. Jan 01 17:51:14 Worst if it was stuck because of an error happening during the check (normally one then has to log into the console, dunno about how Debian on the nslu2 is set up). Jan 01 17:51:37 i last restarted it around dinner time (6 hours ago) Jan 01 17:51:47 i tried to get on before i came on here now, and nothing Jan 01 17:52:00 ok then just the "worst" of the above cases remains. Jan 01 17:52:05 :~) Jan 01 17:52:22 hmm Jan 01 17:52:23 Feb 3 10:53:23 SLUG kernel: IXP4XX NPE driver Version 0.2.0 initialized Jan 01 17:52:24 Feb 3 10:53:23 SLUG kernel: IXP4XX Q Manager 0.2.0 initialized. Jan 01 17:52:24 Feb 3 10:53:23 SLUG kernel: ixp4xx_mac driver 0.2.1: eth0 on NPE-B with PHY[1] initialized Jan 01 17:52:31 from messages - so network is coming up Jan 01 17:52:44 you could check /etc/network/interfaces for the network setttings. Jan 01 17:53:14 i did wonder if the ip may have changed, but nothing was on the slug default of 192.168.1.77 or whatever (did a network scan) Jan 01 17:53:17 the interesting thing is Jan 01 17:53:32 during boot, the ssh request is cancelled quickly, as it should Jan 01 17:54:04 but later it takes a while - like it does, just then doesnt connect, but it isnt pingable Jan 01 17:54:19 is it pingable in the first phase? Jan 01 17:54:30 no Jan 01 17:54:40 well, i havent pinged it all the way through boot Jan 01 17:54:41 iface eth0 inet static Jan 01 17:54:41 address 192.168.0.70 Jan 01 17:54:41 netmask 255.255.255.0 Jan 01 17:54:41 network 192.168.0.0 Jan 01 17:54:42 broadcast 192.168.0.255 Jan 01 17:54:45 gateway 192.168.0.1 Jan 01 17:54:46 thats as it should be Jan 01 17:55:04 that's what I would suggest, ping right from the begin. Could be the kernel crashes later on.. Jan 01 17:55:09 ok Jan 01 17:55:33 which log woudl the apt-get log be Jan 01 17:55:34 ? Jan 01 17:55:39 so we can see what packages were last updated Jan 01 17:55:42 and if you have an arp ping, that would be better (pinging with arp requests; on linux there's "arping") Jan 01 17:56:11 if this is etch, then /var/log/dpkg iirc Jan 01 17:56:18 dpkg.log Jan 01 17:56:52 ah and check the size of the disk, is it full?.. Jan 01 17:57:33 the date seems to skip 3 days in the log dates... Jan 01 17:57:53 its got 8gb to play with Jan 01 17:58:07 7.37GB + swap on top Jan 01 17:58:45 1731632 free blocks Jan 01 17:59:45 on the last apt-get update Jan 01 18:00:39 libldap, exim4-config, exim4-base, exim4-deamon-light, exim4, openssh-server, openseeh-client, libcupsys2 Jan 01 18:04:47 hmm Jan 01 18:04:56 arp -a (lists broadcasting arp's) Jan 01 18:05:14 shows nslu2 ip, with mac of 00-00-00-00-00-00 Jan 01 18:05:44 that's probably not what it should be.. Jan 01 18:05:56 nope, haha Jan 01 18:06:03 putty reports request timed out Jan 01 18:07:04 One can set the arp address of some cards from userspace. Jan 01 18:07:24 Maybe you have / it is accidenally configured this somewhere now. Jan 01 18:07:53 and does not succeed setting it and it is left as 0. Jan 01 18:07:53 arp -a reports it as invalid for the debian slug, but dynamic for my working unslung Jan 01 18:08:04 i can add a static entry? Jan 01 18:08:10 Or maybe another driver is being used now. Jan 01 18:08:36 hm maybe. I really don't know whether a zero arp address is working or what it would mean Jan 01 18:08:49 you mean "static entry" in your windows box? Jan 01 18:09:01 for the mapping arp->ip? Jan 01 18:09:10 yeah Jan 01 18:09:17 yea, that's what I thought you mean Jan 01 18:09:28 its worth a try for the moment at least Jan 01 18:09:42 do you have running both slugs and both have 00-00-.. as arp address? Jan 01 18:09:53 that should give a conflict of course.. Jan 01 18:09:59 no, the other reports its MAC Jan 01 18:10:21 my two slug2 1 unslung the other debian report mac Jan 01 18:11:08 iirc you can set the arp address from /etc/network/interface. maybe just by calling ifconfig from there. Jan 01 18:11:37 (but in the first place it would be good to know why it fails now) Jan 01 18:12:59 setting static doesnt like it Jan 01 18:13:08 I'd try checking arp while it is booting. Jan 01 18:13:12 my interfaces looks like this Jan 01 18:13:14 auto lo Jan 01 18:13:14 iface lo inet loopback Jan 01 18:13:14 # Jan 01 18:13:14 # The NSLU2 built-in ethernet Jan 01 18:13:17 auto eth0 Jan 01 18:13:19 iface eth0 inet static pre-up modprobe -f ixp400 pre-up modprobe -f ixp400_eth address 192.168.0.77 netmask 255.255.255.0 gateway 192.168.0.1 Jan 01 18:13:33 i did notice running arp -a a few times, it would appear and dissapear from the list Jan 01 18:13:48 cheers, let me just stick the drive back on my pc and i can check Jan 01 18:15:20 interfaces: Jan 01 18:15:21 # This file describes the network interfaces available on your system Jan 01 18:15:21 # and how to activate them. For more information, see interfaces(5). Jan 01 18:15:21 # The loopback network interface Jan 01 18:15:21 auto lo Jan 01 18:15:23 iface lo inet loopback Jan 01 18:15:25 # The primary network interface Jan 01 18:15:27 allow-hotplug eth0 Jan 01 18:15:29 iface eth0 inet static Jan 01 18:15:31 address 192.168.0.70 Jan 01 18:15:33 netmask 255.255.255.0 Jan 01 18:15:35 network 192.168.0.0 Jan 01 18:15:37 broadcast 192.168.0.255 Jan 01 18:15:39 gateway 192.168.0.1 Jan 01 18:15:41 # dns-* options are implemented by the resolvconf package, if installed Jan 01 18:15:43 dns-nameservers 212.159.13.49 212.159.13.50 212.159.6.9 Jan 01 18:15:45 dns-search example.org Jan 01 18:16:36 looks like the drivers aren´t loaded Jan 01 18:17:03 but why would it appear and disappear? Jan 01 18:17:08 are the wrong drivers loaded? Jan 01 18:17:45 i think there are no network drivers loaded at all Jan 01 18:18:01 pre-up modprobe -f ixp400 and pre-up modprobe -f ixp400_eth Jan 01 18:18:03 are missing Jan 01 18:18:15 there was something in the log about something with the ixp400 in one of the logs Jan 01 18:18:22 hm Jan 01 18:18:34 errm Jan 01 18:18:42 maybe with the installer version things are set up diffrent from bootstrap install Jan 01 18:18:53 well allow-hotplug suggests it looks for the driver itself, and those could be wrong if opensource drivers are now there but not functional (just an idea) Jan 01 18:19:00 its been fine since christmas day, its just since that last apt-get upgrade Jan 01 18:19:52 Feb 3 15:29:14 SLUG kernel: ixp4xx_mac driver 0.2.1: eth0 on NPE-B with PHY[1] initialized Jan 01 18:20:03 we know the date is wrong, but that is from the last boot up i think Jan 01 18:20:15 Happy New Year! Anybody knows how to find the find specific location (sectors) on the disk of a particular file? Jan 01 18:21:02 Reedy_Boy: has the interfaces file changed? (compare the mtime of the var/network/interfaces file with the times of the logs). Or has it installed new drivers? (the drivers are under /lib/modules/*). Jan 01 18:21:25 interfaces is listed as 25/01 Jan 01 18:21:41 and its using today as 03/02 Jan 01 18:21:54 so that would seem ti hasnt changed since install Jan 01 18:22:06 ahh Jan 01 18:22:24 2.6.17-2-ixp4xx Jan 01 18:22:31 and there is also Jan 01 18:22:37 2.6.18-3-ixp4xx Jan 01 18:23:12 with the lower number reporting a date later than the higher Jan 01 18:23:40 did it install one of those in the update from today (as seen in dpkg.log)? Jan 01 18:25:02 doesnt look to have done recently, just the conseuctive dates like on the files Jan 01 18:25:16 chacko: man locate Jan 01 18:25:18 i cant remember when i last rebooted it, so it *may* have been an older file Jan 01 18:25:28 chacko: eh forget that Jan 01 18:26:11 chacko: lilo can do it, so there must a way to do this from C. Jan 01 18:27:11 Reedy_Boy: you have to find out how to set the kernel which is being choosen on boot for slugs. Jan 01 18:27:11 last restart before todays seems to be 3 days ago Jan 01 18:27:12 I am looking for an available utility under SlubOS/BE, just to inspect where one of my files is located. Just a one time use... Jan 01 18:27:14 which sounds about right Jan 01 18:28:10 Feb 3 10:53:23 SLUG kernel: Linux version 2.6.18-3-ixp4xx Jan 01 18:28:17 Feb 3 seems to be today from the other logs Jan 01 18:28:29 Feb 3 10:53:23 SLUG kernel: Linux version 2.6.18-3-ixp4xx (Debian 2.6.18-7) (waldi@debian.org) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-20)) #1 Tue Dec 5 16:52:07 UTC 2006 Jan 01 18:28:29 Feb 3 10:53:23 SLUG kernel: CPU: XScale-IXP42x Family [690541f1] revision 1 (ARMv5TE), cr=0000397f Jan 01 18:28:46 from kern.log Jan 01 18:29:20 chacko: dunno about utilities. Shouldn't be nlsu2 specific (SlubOS/BE is linux as well, right?). Jan 01 18:29:46 Maybe lilo does it just by reading /dev/hdaX and interpreting the filesystem structure itself, in the end. Jan 01 18:30:02 maybe not. Jan 01 18:30:13 in kern.log.0 it reports the same version Jan 01 18:30:39 pfanze: slubosbe is linux. If I can find the linux utility name, then I can see if that is available as a pkg. Jan 01 18:30:46 hmm... Jan 01 18:31:07 the 2.6.17-2 has drivers/ixp400 Jan 01 18:31:13 the 2.6.18-3 doesnt Jan 01 18:31:17 pfanze: some basic utility, I assume, can be used to find this... Jan 01 18:31:37 where can i see which kernel version iam runnin ? Jan 01 18:32:02 cat /proc/version Jan 01 18:32:05 i think? Jan 01 18:32:16 cat /proc/version Jan 01 18:32:16 Linux version 2.6.16 (slug@nudi) (gcc version 3.4.4) #1 PREEMPT Thu Jun 8 23:38:13 PDT 2006 Jan 01 18:32:19 hm Jan 01 18:32:21 yeah it is Jan 01 18:32:29 chacko: well you might assume too much. Why would anyone want to know this information. My next best guess would be e2fsck. Jan 01 18:32:35 eiffel: what os ru running. In my bash, there is an ii marcro that came with it Jan 01 18:32:56 debian sid bootstrapped Jan 01 18:33:14 eiffel: using bash? Jan 01 18:33:18 yes Jan 01 18:33:23 try ii Jan 01 18:33:29 Got dogs to walk, back in a few guys Jan 01 18:33:35 * Reedy_Boy is AFK Jan 01 18:33:43 what is ii ?? Jan 01 18:34:19 My bash in slugos and unslung came with an alias ii, which gives some such info Jan 01 18:34:50 # ii Jan 01 18:34:50 You are logged on periyar from-to 192.168.1.50 1340 192.168.1.203 22 Jan 01 18:34:50 Linux periyar 2.6.16 #1 PREEMPT Fri Jun 9 07:34:31 PDT 2006 armv5teb unknown Jan 01 18:34:50 Mon Jan 1 11:01:44 UTC 2007 Jan 01 18:34:50 11:01:44 up 14:16, load average: 1.00, 1.00, 1.00 Jan 01 18:34:50 Memory stats : Jan 01 18:34:52 total used free shared buffers Jan 01 18:34:55 Mem: 30300 24852 5448 0 1744 Jan 01 18:34:56 Swap: 12268 0 12268 Jan 01 18:34:58 Total: 42568 24852 17716 Jan 01 18:35:01 Free Disk Space : Jan 01 18:35:02 Filesystem 1k-blocks Used Available Use% Mounted on Jan 01 18:35:04 tmpfs 10240 28 10212 0% /dev Jan 01 18:35:06 tmpfs 15148 0 15148 0% /media/ram Jan 01 18:35:23 hm dont have such a thing not under unslung nor debian Jan 01 18:35:33 chacko: do you mean df ? Jan 01 18:36:05 but that doesn't report the "sector a file is at", only the partition. Jan 01 18:36:09 pflanze: I typed the command and output into this chat see above Jan 01 18:36:29 pflanze: I was helping eiffel :( Jan 01 18:36:42 ah Jan 01 18:41:22 eiffel: Try uname -a Jan 01 18:41:35 uname -a Jan 01 18:41:35 Linux linksys2 2.6.16 #1 PREEMPT Thu Jun 8 23:38:13 PDT 2006 armv5tel GNU/Linux Jan 01 18:41:41 k Jan 01 18:42:55 linksys2:/lib/modules# ls -la Jan 01 18:42:55 insgesamt 20 Jan 01 18:42:55 drwxr-xr-x 4 root root 4096 2006-12-29 00:36 . Jan 01 18:42:55 drwxr-xr-x 9 root root 8192 2006-12-29 00:31 .. Jan 01 18:42:57 drwxrwxr-x 3 root root 4096 1970-01-01 01:00 2.6.16 Jan 01 18:43:00 drwxr-xr-x 3 root root 4096 2006-12-29 00:36 2.6.18-3-ixp4xx Jan 01 18:43:03 hm Jan 01 18:43:27 cd 2.6.16 Jan 01 18:43:28 ls -la Jan 01 18:43:31 ups Jan 01 18:44:40 hm Jan 01 18:44:57 the 2.6.18-3-ixp4xx one only has isdn stuff in it Jan 01 18:45:40 but i dont know if that can work as my kernel is 2.6.16 not 2.6.18 ?!? Jan 01 18:46:26 'evening Jan 01 18:46:46 ~ugt Jan 01 18:46:47 well, ugt is Universial Greeting Time. Created in #mipslinux, it is a rule that states that whenever somebody enters an IRC channel it is always morning, and it is always late when the person leaves. The local time of any other people in the channel, including the greeter, is irrelevant. Jan 01 18:46:56 ;-p Jan 01 18:49:30 eiffel: if the relevant drivers are compiled into the kernel, there is no need for a module to be present. Jan 01 18:50:02 okay. Jan 01 18:50:02 eiffel: check /boot/config-* whether that is the case. Jan 01 18:50:29 sorry, I'm not talking in english channel usually Jan 01 18:50:30 (well that's the place on a 'normal' debian machine, dunno about slug) Jan 01 18:53:02 well its the misdn module i got with apt-get Jan 01 18:53:23 is it possible to use mplayer with debian on a nslu2 or is mplayer too heavy ? Jan 01 18:53:25 still wondering why there is not one for my kernel version Jan 01 18:55:54 mial try vlc-nox Jan 01 18:56:05 its vlc commandline version Jan 01 18:56:15 eiffel: why? "is not one" meaning "available from debian" or "not present as module on the box"? Jan 01 18:56:16 I'll try, thanks Jan 01 18:57:39 pflanze my /boot dir is empty Jan 01 18:57:55 eiffel: are you running Debian on it? Jan 01 18:58:31 yes Jan 01 18:59:36 When a kernel is installed, there are 3 parts: 1) the kernel config, 2) the kernel image, 3) the modules. Jan 01 18:59:58 So the config should theoretically be around somewhere. Jan 01 19:00:25 Dunno if the kernel on a slug install is in a debian package, but I'd expect so. Jan 01 19:00:44 thus: dpkg -l "*kernel*" Jan 01 19:00:51 to see which ones you have installed. Jan 01 19:01:21 I'm bacj Jan 01 19:02:28 COLUMNS=140 dpkg -l "*kernel-image*"|grep ^i Jan 01 19:02:49 to filter out the installed ones, and make the output wide enough not to clip anyhting Jan 01 19:03:31 no output yet dpkg sucks ipkg is way faster Jan 01 19:04:32 (hum, no idea what ipkg is, not in normal Debian) Jan 01 19:04:55 ipkg is used under unslung for paket installation Jan 01 19:05:02 uses less memory Jan 01 19:05:12 so there is no swapping Jan 01 19:05:23 ah Jan 01 19:05:24 and the cpu isnt used as much too Jan 01 19:06:33 hm, is ipkg keeping it's own list of installed packages? I couldn't help you then. Jan 01 19:07:21 no thats only under unslung Jan 01 19:07:21 If neither has a *kernel* package, the kernel would have to have been installed directly somehow. Jan 01 19:07:32 i am using apitude with debian Jan 01 19:07:35 ah. Jan 01 19:09:47 for example "dpkg -S /lib/modules/2.2.19/misc/esp.o" (or another *existing* module file) would show the package name containing it. Jan 01 19:10:10 But the config file would be part of the kernel-image package, iirc. So that would be no help. Jan 01 19:11:06 ii flash-kernel 0.8 utility to write kernel and initramfs to MTD Jan 01 19:11:17 ii kernel-package 10.065 A utility for building Linux kernel related Jan 01 19:11:28 ii linux-kernel-h 2.6.18-6 Linux Kernel Headers for development Jan 01 19:11:37 thats it Jan 01 19:12:52 dpkg -L linux-kernel-headers-2.6.18 |grep config just to be sure Jan 01 19:13:17 * pflanze usually builds his kernels himself Jan 01 19:13:19 not installed Jan 01 19:13:44 hm, dunno what the unclipped name is above Jan 01 19:13:57 that's why I suggested COLUMNS=140 Jan 01 19:14:48 (note: that's at the start of the same line as the dpkg -l command; *or* you have to say "export COLUMNS=140" to keep it over to the next lines) Jan 01 19:18:03 if you're running updatedb, "locate config" (maybe grepping for your kernel numbers) could be a more fruitful alternative. Jan 01 19:18:34 ("running updatedb" meaning, if it is set (as by default on x86 debian installations) to run by cron) Jan 01 19:19:32 (or you could do like me and: find / -xdev > ~/tmp/filelist, then grep that filelist.) Jan 01 19:20:43 (but that only scans the filesystem on /, check with df to see other filesystems and run a find on them as well) Jan 01 19:21:11 Going back to the people who did the installer would be the logical next step (or getting the installer sources/documentation). Jan 01 19:21:39 i am not running the installer version Jan 01 19:22:34 but somehow you got the kernel on your device. Jan 01 19:22:47 i think the kernel comes from openslug and on top is running debian somehow Jan 01 19:23:59 ah. well the person who built the kernel knows the config (it's the ".config" file in the toplevel directory of the kernel sources after configuration). Jan 01 19:24:28 even if it's not been packaged up and delivered with the binary. Jan 01 19:25:10 And in that file you could see which modules have been built, and which parts have been compiled in statically (not as module). Jan 01 19:25:22 hm k Jan 01 19:27:16 So it's entirely possible that your other kernel works.. if it doesn't, there must be a procedure to revert to the older kernel. How to do this, I don't know (again, I don't own such a device and have just begun reading the docs). Jan 01 19:50:48 anyone around? Jan 01 19:51:44 ~ask Jan 01 19:51:45 If you have a question, just ask, maybe someone have an answer... sometimes. Jan 01 19:53:52 lol Jan 01 19:54:27 Guts neus! Jan 01 19:54:55 pflanze/eiffel: any ideas about my debian slug? Jan 01 19:55:53 Reedy_Boy: well, do you now know whether the upgrade changed the installed kernel? Jan 01 19:56:12 no, it didnt Jan 01 19:56:19 hm. Jan 01 19:56:45 other packages have changed, but not the kernel since the install Jan 01 19:57:40 One thing you could do (without me knowing more about NSLU2-Debian) is put beep signals into the boot process. Jan 01 19:57:53 hmm, didn't Jim Buzbee have some problems with his debian... Jan 01 19:57:54 errm Jan 01 19:57:54 And use ifconfig to give the interface a MAC address. Jan 01 19:58:42 Ahh Jan 01 19:59:01 Case in point is that I had been successfully running my new Debian Slug for a couple of days, booting and rebooting a number of times. At some point, I noticed that I couldn't reach the slug on the network. I don't remember exactly what I had done last, but to bring it back, I just unplugged and re-plugged the power. As it booted back up, everything looked normal. The LEDs flashed, the disk clicked and all seemed right with the world. But Jan 01 19:59:01 when the boot finished, the NSLU2 was again nowhere to be found on my network. Jan 01 19:59:08 The only way I could see what was happening was to add debug statements to the boot, building my own boot log. This was a tedious process of adding statements, unplugging the drive from my MacBook, plugging it back into my NSLU2, rebooting the NSLU2, putting the disk back on my MacBook, examining the logs, etc. What I finally found is that everything was normal except that the "interfaces" file, which tells the Debian boot which network in Jan 01 19:59:08 terfaces to bring up, was missing the one line that told it to automatically configure the internal Ethernet device. Once I added this line, I rebooted and was back to normal. Jan 01 19:59:15 sounds familiar to me! Jan 01 19:59:18 http://www.smallnetbuilder.com/content/view/29774/77/1/4/ Jan 01 20:00:30 ok my problem is this, I can flash my slug with any firmware, using the sercomm tool, it works great, but I never see my slug on the network, not even arp gives me its mac address Jan 01 20:00:49 has anyone seen this before? Jan 01 20:01:21 I tried zeroing the sysconfig area but it doesn't help Jan 01 20:01:42 I get the same behaviour if I use openslug, unslung or link sys software Jan 01 20:02:10 mines doing something similar, just started recently though... Jan 01 20:02:19 was it ok before? Jan 01 20:02:50 Reedy_Boy: I don't really know what "allow-hotplug" is doing. There's an "auto eth0" missing, maybe add this instead? Jan 01 20:03:01 I've never seen it on the network, but got it from a friend who said it worked for him (I don't think he bricked it though!) Jan 01 20:03:16 its not bricked if you can upgrade it and stuff Jan 01 20:03:29 tmp3434, but you are on the same subnet? Jan 01 20:04:07 well, I have put up both nets on my computers .1 and .0 so I should see it somewhere Jan 01 20:04:19 19.2168.1 and .0 that is Jan 01 20:04:25 depends what you mate had his on Jan 01 20:04:37 you could reset it from the back, and use the linksys tool to set hte ip and stuff Jan 01 20:04:37 hi Jan 01 20:04:39 he had unslung on it Jan 01 20:04:45 does someone use gentoo on the nslu2? Jan 01 20:05:16 well, the linksys software doesn't see it either, should I try the eraseall.exe thingy? Jan 01 20:05:21 NO Jan 01 20:05:24 no Jan 01 20:05:30 tmp3434: NO, it's broken Jan 01 20:05:32 ok I read that in the FAQ Jan 01 20:05:37 that is one thing, that if that screws it up, you've had it Jan 01 20:06:22 but as sercomm reports successful upgrades then I guess it's working ok, I just need to do something at the redboot rpompt? Jan 01 20:06:24 tmp3434,http://www.nslu2-linux.org/wiki/HowTo/ResetSysConf may help you, follow the procedures and the slug should have 192.168.1.77 Jan 01 20:06:28 tmp3434: what is the problem? Jan 01 20:06:54 ok my problem is this, I can flash my slug with any firmware, using the sercomm tool, it works great, but I never see my slug on the network, not even arp gives me its mac address Jan 01 20:06:55 I have done the resetsysconf several times, it doesn't seemm to help, I can try again Jan 01 20:07:31 the ethernet link light is lit and it shows packets crossing the net Jan 01 20:07:41 so not physical I don't think Jan 01 20:07:45 do you have it attached to a router or anything? Jan 01 20:07:55 if so, you could have like an attached devices, see if that see's it Jan 01 20:07:56 its in a switch Jan 01 20:07:58 tmp3434: dp you use dhcp? Jan 01 20:08:38 yes I have netgear gw but I don't see it in the attached devices, but I did set it to get the same ip address for it's mac Jan 01 20:08:45 the 1.77 one Jan 01 20:09:17 have you asked ur mate what IP he had it on? Jan 01 20:09:19 is there someway to "start from scratch", i.e wipe everything begin over? Jan 01 20:09:28 he used dhcp Jan 01 20:10:00 there is the reset button on the back...? Jan 01 20:10:21 an inset button I use that to get the redboot Jan 01 20:10:21