**** BEGIN LOGGING AT Sat Jan 26 02:59:57 2008
Jan 26 05:11:53 <jaem> hey all
Jan 26 05:12:24 <jaem> anyone around that I can ask a question of?
Jan 26 05:16:12 <johnx> sure
Jan 26 05:16:47 <jaem> it's probably pretty stupid, but I've tried the way I could already find on the Intertubes, so bear with me...
Jan 26 05:17:12 <johnx> ok
Jan 26 05:17:26 <jaem> I've installed Angstrom on a Pentium Pro-based Desktop, since it's pretty much the only modern distro I could find that would run on it
Jan 26 05:18:05 <jaem> I've installed three network cards, two of which I definitely have drivers for (they're the same,b ut I'm not sure about the drivers for the other one)
Jan 26 05:19:11 <jaem> they use the 3c59x.ko module
Jan 26 05:19:47 <jaem> my issue is that either they're not being recognized, or at least not being brought up at boot time, and I don't currently have access to a monitor for it
Jan 26 05:19:55 <johnx> aah
Jan 26 05:20:02 <jaem> I *do* have a modern Ubuntu Gutsy laptop and a USB-IDE adapter
Jan 26 05:20:15 <jaem> and a decent amount of know-how
Jan 26 05:20:43 <jaem> the link light is on the cards when they're plugged in, but nmap can't find them, and there's not data/act light
Jan 26 05:21:11 <jaem> I'm running both computers on a LAN - they're the only ones on it
Jan 26 05:21:12 <johnx> so, have you added some debugging to the init scripts?
Jan 26 05:22:01 <jaem> I'm not sure exactly what you're referring to - I'm okay with Linux, but still pretty new, and shell scripting is a bad area for me...
Jan 26 05:22:15 <johnx> ah
Jan 26 05:22:28 <jaem> I can't access the box at all except for SSH, which of course, doesn't work without the iface being up
Jan 26 05:22:32 <johnx> ok, well you know how to make a command output to a file, right?
Jan 26 05:22:35 <jaem> yep
Jan 26 05:22:36 <jaem> >
Jan 26 05:23:05 <johnx> are you familiar with what happens when the system boots, how scripts are run from /etc/init.d ?
Jan 26 05:23:11 <jaem> more or less
Jan 26 05:23:11 <NAbyss> jaem: Might also help to redirect dmesg to a file, see what it does
Jan 26 05:23:21 <jaem> ok thx - I hadn't thought of that
Jan 26 05:23:43 <johnx> you can also add other debugging as well to the inits scripts
Jan 26 05:24:00 <johnx> just carefully stick a command at the beginning or end
Jan 26 05:24:09 <jaem> ok... following so far
Jan 26 05:24:18 <johnx> lsmod > /root/lsmod.txt
Jan 26 05:24:23 <jaem> right
Jan 26 05:24:24 <johnx> to see what's loaded
Jan 26 05:24:26 <jaem> ok
Jan 26 05:24:30 <johnx> and dmesg like NAbyss said
Jan 26 05:24:39 <johnx> ifconfig > /root/ifconfig.txt
Jan 26 05:24:42 <jaem> just dmesg? no switches or anything?
Jan 26 05:24:45 <jaem> ok
Jan 26 05:24:48 <NAbyss> er, ifconfig -a, most likely
Jan 26 05:24:52 <jaem> yes
Jan 26 05:24:53 <NAbyss> jaem: correct
Jan 26 05:25:08 <jaem> which init script should I put this in
Jan 26 05:26:00 <jaem> this makes a lot of sense - I actually should have thought of this... but using Ubuntu can make one a bit soft sometimes; the things that "just work" don't give you the chance to learn as much
Jan 26 05:26:04 <jaem> lol
Jan 26 05:26:18 <johnx> it's true
Jan 26 05:26:32 <jaem> but I tinker enough that I often have to fix things
Jan 26 05:26:33 <johnx> having learned the hard way I can say it's really nice that things "just work" now though :)
Jan 26 05:26:38 <jaem> lol
Jan 26 05:27:19 <jaem> yeah - I took a look at Backtrack (Slackware-based), when I was virus-hunting last semester, and the package manager kind of scared me (no dep checking)
Jan 26 05:27:51 <johnx> so jaem you've written a /etc/network/interfaces file, right?
Jan 26 05:27:55 <jaem> I like things that are powerful, but they sometimes assume too much knowledge to be convenient
Jan 26 05:27:56 <jaem> yes
Jan 26 05:28:16 <jaem> I assumed they would be called ethX - is that still the case in Angstrom?
Jan 26 05:28:24 <NAbyss>  Yes
Jan 26 05:28:37 <jaem> and would DHCP or static IPs be easier initially?
Jan 26 05:28:45 <NAbyss> Static
Jan 26 05:28:47 <jaem> ok
Jan 26 05:29:05 <johnx> and of course make sure that you have:
Jan 26 05:29:07 <johnx> auto eth0
Jan 26 05:29:09 <johnx> in there
Jan 26 05:29:10 <jaem> yes
Jan 26 05:29:23 <jaem> what exactly does that do again?  load it at boot?
Jan 26 05:29:43 <johnx> yes
Jan 26 05:29:43 <NAbyss>  yep
Jan 26 05:29:58 <jaem> so I'll need address, netmask, gateway - anything else?
Jan 26 05:30:20 <NAbyss> That should do it, for now at least
Jan 26 05:30:48 <jaem> auto lo
Jan 26 05:30:48 <jaem> iface lo inet loopback
Jan 26 05:30:48 <jaem> auto eth0
Jan 26 05:30:48 <jaem> iface eth0 inet static
Jan 26 05:30:48 <jaem>         address 192.168.1.3
Jan 26 05:30:49 <jaem>         netmask 255.255.255.0
Jan 26 05:30:51 <jaem>         gateway 192.168.1.1
Jan 26 05:30:53 <jaem> auto eth1
Jan 26 05:30:55 <jaem> iface eth1 inet static
Jan 26 05:30:57 <jaem>         address 192.168.1.4
Jan 26 05:30:59 <jaem>         netmask 255.255.255.0
Jan 26 05:31:01 <jaem>         gateway 192.168.1.1
Jan 26 05:31:03 <jaem> auto eth2
Jan 26 05:31:05 <jaem> iface eth2 inet static
Jan 26 05:31:07 <jaem>         address 192.168.1.5
Jan 26 05:31:08 <jaem>         netmask 255.255.255.0
Jan 26 05:31:10 <jaem>         gateway 192.168.1.1
Jan 26 05:31:13 <jaem> ?
Jan 26 05:31:15 <jaem> sorry! forgot how long it was..
Jan 26 05:31:15 <johnx> looks fine
Jan 26 05:31:17 * jaem is sheepish
Jan 26 05:31:25 <johnx> jaem, in terms of what script to add debugging to, look under /etc/rc5.d/
Jan 26 05:31:26 <NAbyss> jaem: Only one IF should have the gateway
Jan 26 05:32:23 <johnx> scripts that begin with S are started in that runlevel (5) and they start in numerical order
Jan 26 05:33:18 <NAbyss> A script named /etc/rc5.d/S99logging should do the job
Jan 26 05:34:41 <johnx> just make sure that it's executable
Jan 26 05:34:54 <johnx> chmod +x S99logging
Jan 26 05:38:54 <hvontres|home> jaem: do you have a null modem cable? if so, you could use a serial console to take a look at what's going wrong
Jan 26 05:44:11 <jae1> hello?
Jan 26 05:44:17 <johnx> hi
Jan 26 05:44:19 <jae1> ah
Jan 26 05:44:25 <jae1> good - my internet went out
Jan 26 05:44:35 <jae1> the residence network really stinks
Jan 26 05:44:42 <jae1> sorry about that
Jan 26 05:44:58 <jae1> where did I cut off?
Jan 26 05:45:29 <jae1> I last got "johnx: jaem, in terms of what script to add debugging to, look under /etc/rc5.d/"
Jan 26 05:45:53 <johnx> we didn't see anything from you after that
Jan 26 05:46:06 <jae1> ah
Jan 26 05:46:15 <jae1> I was saying that I wanted runlevel 2 for now
Jan 26 05:46:27 <jae1> just SSH and a console - I can go from there
Jan 26 05:46:37 <jae1> and that's all I need for now
Jan 26 05:46:44 <johnx> you know how to set runlevels then?
Jan 26 05:46:48 <hvontres|home> jael: do you have a null modem cable? if so, you could use a serial console to take a look at what's going wrong
Jan 26 05:47:59 <jae1> no - I could go to the lab and make one, but even though they're open 24/7, I don't really like going out there at this time, and it would take a while
Jan 26 05:48:05 <jae1> I probably should sometime
Jan 26 05:49:04 <jaem> sorry... stupid network again
Jan 26 05:50:10 <jaem> no, I keep meaning to make a null modem cable, but I'd have to take a trip to the lab across campus, and I can't do that now
Jan 26 05:51:41 <jaem> hello?
Jan 26 05:51:54 <johnx> hello
Jan 26 05:51:58 <jaem> ah good
Jan 26 05:52:04 <jaem> gah - stupid network...
Jan 26 05:52:24 <jaem> sorry
Jan 26 05:52:30 <johnx> no problem
Jan 26 05:52:38 <hvontres|home> jaem: any other geeks in the dorm that might have one?
Jan 26 05:52:41 <jaem> it always has "issues"
Jan 26 05:52:46 <jaem> none that I know of
Jan 26 05:52:49 <jaem> not here, anyways
Jan 26 05:52:53 <johnx> maybe /ping johnx would be easier than waiting for a response
Jan 26 05:52:54 <jaem> the one guy's at a LAN
Jan 26 05:52:57 <jaem> oh ok
Jan 26 05:52:59 <jaem> didn't know that
Jan 26 05:53:09 <johnx> neither did I til yesterday :)
Jan 26 05:53:12 <jaem> lol
Jan 26 05:53:26 <jaem> anyhow... which script should I put it in?
Jan 26 05:53:43 <johnx> any one you want or make your own
Jan 26 05:54:00 <johnx> !logs
Jan 26 05:54:01 <cdbot2> Channel logs for #angstrom are archived at:
Jan 26 05:54:02 <cdbot2> http://hentges.net/tmp/logs/irc/%23angstrom
Jan 26 05:54:03 <cdbot2> Live-logs are available at
Jan 26 05:54:05 <cdbot2> http://hentges.net/tmp/logs/irc/livelogs/%23angstrom.livelog
Jan 26 05:54:07 <cdbot2> See ?? help-logs for usage instructions
Jan 26 05:54:22 <johnx> might want to look at the couple msgs you missed
Jan 26 05:54:27 <jaem> ok thx
Jan 26 05:54:31 <johnx> sure
Jan 26 05:54:38 <jaem> I've started up WireShark - overkill, but hey...
Jan 26 05:54:39 <jaem> lol
Jan 26 05:56:31 <jaem> I don't see anything I missed...
Jan 26 05:56:47 <jaem> nvm
Jan 26 05:59:12 <jaem> ok - I've got the script set up...
Jan 26 05:59:20 <jaem> am I good to install the HDD and boot?
Jan 26 05:59:37 <johnx> I don't see why not
Jan 26 05:59:52 <johnx> out of curiosity what kind of bootloader did you setup for it?
Jan 26 05:59:57 <jaem> grub
Jan 26 06:00:00 <jaem> what I'm used to
Jan 26 06:00:09 <johnx> makes sense
Jan 26 06:00:19 <jaem> I put id:2:initdefault:
Jan 26 06:00:19 <jaem> in /etc/inittab - is that right?
Jan 26 06:00:25 <jaem> for runlevel 2?
Jan 26 06:00:29 <johnx> yes
Jan 26 06:00:32 <jaem> ok
Jan 26 06:00:46 <jaem> brb
Jan 26 06:00:52 <johnx> k
Jan 26 06:02:01 <jaem> ...installed...
Jan 26 06:02:35 <jaem> and booting...
Jan 26 06:02:43 <jaem> brb
Jan 26 06:05:01 * johnx goes afk, will be back later
Jan 26 06:05:16 <jae1> just had to swap cables
Jan 26 06:05:27 <jae1> it has (presumably) booted
Jan 26 06:10:26 <jae1> I'm just going to check the logs now
Jan 26 06:12:30 <jae1> made a stupid mistake - I'll have to do it over
Jan 26 06:55:55 <jaem> johnx: are you still around?
Jan 26 08:02:37 <jaem> hey again...
Jan 26 08:04:37 <jaem> is anyone that I was talking to earlier still on?
Jan 26 10:12:29 <gints> which feed I could find latest/unstable opie packages in?
Jan 26 17:29:46 <treitmayr> Hi, I just tried to use the Angstrom 2007.12 image for the NSLU2 but was not able to ssh into the box as root seems to have an empty password. Anyone having similar problems?
Jan 26 17:30:32 <treitmayr> Or a solution ;)
Jan 26 17:53:32 <wvdschel> where can i find the source for the old 2.4 kernel for collie?
Jan 26 17:53:48 <wvdschel> i need to look at how it handles sound, trying to figure out how to make an alsa driver
Jan 26 18:39:29 <DaedalusX> hey all
Jan 26 21:30:48 <gasparikm> !logs
Jan 26 21:30:48 <cdbot2> Channel logs for #angstrom are archived at:
Jan 26 21:30:49 <cdbot2> http://hentges.net/tmp/logs/irc/%23angstrom
Jan 26 21:30:50 <cdbot2> Live-logs are available at
Jan 26 21:30:51 <cdbot2> http://hentges.net/tmp/logs/irc/livelogs/%23angstrom.livelog
Jan 26 21:30:53 <cdbot2> See ?? help-logs for usage instructions
Jan 26 21:32:47 <gasparikm> ?? help-logs
Jan 26 21:32:48 <cdbot2> help-logs[1]: Available commands are: !logs !pauselog <MINUTES> !logstatus 
Jan 26 21:32:49 <cdbot2> help-logs[2]: !enablelog, !disablelog 
Jan 26 21:32:50 <cdbot2> help-logs[3]: !stamp (Add timestamp to channel logfile) 
**** ENDING LOGGING AT Sun Jan 27 02:59:57 2008