OpenWrt

[00:16] <kimosabe> im getting unknowk or no flash chip detected via jtag can i get a hand please
[00:18] <Dabian> heh :)
[00:19] Action: Dabian throws a dried monkey hand at kimosabe.
[00:19] <Dabian> right :)
[00:20] <[mbm]> kimosabe: usually the cable is miswired or the wrong length
[00:20] <nullboy> should it be as short as possible?
[00:20] <kimosabe> do you have the pin out please
[00:20] <[mbm]> pretty much
[00:20] <[mbm]> kimosabe: it's on the wiki
[00:21] <KragenSitaker> sweet! i can now run stuff from hotplug when I press the SES button
[00:21] <[mbm]> customization -> jtag
[00:21] <kimosabe> yes its short ive used this cable before and i use this same one for jtaging dishnetwork also
[00:21] <KragenSitaker> it doesn't seem very reliable --- sometimes hotplug fires the events in the wrong order
[00:21] <KragenSitaker> so it'll end up firing a pressed event after the last released event
[00:21] <[mbm]> KragenSitaker: ?
[00:21] <KragenSitaker> [mbm]: well, i wrote this script:
[00:22] <KragenSitaker> if [ "$BUTTON" = ses ] ; then
[00:22] <KragenSitaker> if [ "$ACTION" = "pressed" ] ; then
[00:22] <KragenSitaker> echo 1; else echo 0; fi > /proc/diag/led/ses_orange
[00:22] <KragenSitaker> fi
[00:22] <Dabian> [mBm]!
[00:22] <KragenSitaker> and sometimes when I walk away from the router after having pressed the button, the LED stays on
[00:23] <[mbm]> KragenSitaker: try writing the results to a file to see what's broken, the hotplug events or the led support
[00:23] <KragenSitaker> [mbm]: oh, eh, good point, thank :)
[00:23] <KragenSitaker> it hadn't occurred to me that the LED support might be broken
[00:23] <[mbm]> think it's the led support
[00:23] <KragenSitaker> also sometimes it takes a noticeable amount of time --- maybe 100ms or 200ms
[00:23] <Dabian> He is not stupid :)
[00:24] <EQ> hey
[00:24] <EQ> anybody here?
[00:24] <[mbm]> KragenSitaker: the button press fires off a hotplug process instantly; unless your router is busy there should be almost no lag
[00:25] <EQ> i have a big problem, i must to increase the package ttl, becouse my isp is sux
[00:25] <EQ> i install all of the ipt packages with ipkg, but these not have the ipt_TTL.o file
[00:26] <EQ> so i cant load this module
[00:26] <Dabian> EQ: Show him what the barrel-end of a shutgun looks like when it is fired.
[00:26] <EQ> and the ttl inc not works
[00:26] <KragenSitaker> nope, reproduced problem, and the last thing written to the log file is a 1
[00:26] <KragenSitaker> does hotplug run only one process at a time?
[00:27] <[mbm]> EQ:download the openwrt sources, pretty easy to compile it, and when you do you'll have a ipt_TTL.o file
[00:27] <KragenSitaker> or could there be multiple processes perhaps running concurrently?
[00:27] <EQ> i have a fon router, but it will not works, while i dont fix the ttl
[00:27] <KragenSitaker> let me back up a second
[00:27] <KragenSitaker> is hotplug documented somewhere? i'm unfortunately using a mac, and my linux servers other than my WRT don't have hotplug installed
[00:27] <EQ> [mbm] do you have any documentation about the compiling?
[00:28] <Dabian> hotplug is depicated as of 2.6.20 of the kernel or so.
[00:28] <[mbm]> EQ: read the wiki, it's pretty much download, and type make
[00:28] <Dabian> (If I understand it correctly)
[00:28] <EQ> thx
[00:28] <KragenSitaker> i'd like to be able to use the SES button for morse code or something cool like that, but if events get delivered out of order and there's no way to poll the button state, that could be very difficult
[00:28] <loswillios> KragenSitaker: google for hotplug2
[00:28] <Dabian> EQ : Compile is what it always was.
[00:29] <[mbm]> KragenSitaker: the buttons are irq events, the irq handler sets the variables and then executes hotplug
[00:29] <KragenSitaker> loswillios: thanks!
[00:29] <EQ> Dabian thx, i will try it
[00:29] <KragenSitaker> [mbm]: is there any protection from multiple hotplug processes running at a time?
[00:29] <Shak-> I just attempted to setup wpa on my fon route, it broadcasts the network with protection but I cant connect wirelessly or by ethernet
[00:29] <Shak-> is gonna take a reflash to fix?
[00:29] <[mbm]> KragenSitaker: nope
[00:30] <Shak-> *is this
[00:30] <KragenSitaker> [mbm]: is there any way to reliably get the button-press events in the correct order, then?
[00:30] <KragenSitaker> or reliably find out whether the button is currently pressed or currently released?
[00:30] <KragenSitaker> i could downgrade to RC5 --- it was possible in RC5, I know
[00:31] <KragenSitaker> by, ick, busy-waiting
[00:31] <KragenSitaker> but at least it was possible
[00:31] <[mbm]> KragenSitaker: I'm still trying to understand how they'd get in the wrong order unless you were flooding the irqs with rapid fire clicking or the router was too busy to execute hotplug when it got called
[00:32] <Dabian> [mbm]: Quick question - please dont kick my ribs if its out of line - where do I put a line to add an IP to listen to on the wan side?
[00:32] <KragenSitaker> [mbm]: what I perceive as a single button press is often six or eight button presses from hotplug's point of view. I suspect bouncing contacts.
[00:32] <KragenSitaker> the router isn't particularly busy; the 15-second load average got up to 0.04 during that time
[00:32] <KragenSitaker> but rapid-fire clicking is exactly what I want to do for morse code
[00:33] <[mbm]> KragenSitaker: hmm we are internally keeping track of the time between presses, which is then truncated to the seconds you see in the SEEN variable
[00:33] <[mbm]> we could enforce a debounce time between presses
[00:33] <KragenSitaker> [mbm]: yes, but that doesn't help in telling whether the actually last event was actually a press or a release
[00:34] <KragenSitaker> you could, which would be fine for people who want to reset the router by pressing the button
[00:34] <[mbm]> I wasn't expecting a hotplug failure
[00:34] <KragenSitaker> where would you do the enforcing? in the kernel?
[00:34] <[mbm]> haven't seen it fail in tests here
[00:34] <[mbm]> yeah it would be an ignore in the kernel
[00:35] <KragenSitaker> ignore an event?
[00:35] <KragenSitaker> rather than delay it?
[00:35] <[mbm]> depends what the actual cause is
[00:35] <KragenSitaker> that approach wouldn't really be helpful for my application --- i really would like to be able to get sub-25ms response time
[00:36] <[mbm]> if it's a dirty button press that causes a single press to be seen as multiple presses then we need a debounce ignore
[00:36] <KragenSitaker> but maybe using the SES button as an actual input device is too eccentric to be worth worrying about
[00:36] <[mbm]> if it's a flood of real button presses that gets out of sequence when passed out of the kernel then we need a sequence number
[00:37] <[mbm]> in other words we get the event in realtime at a kernel level, and then we execute a userspace program
[00:37] <[mbm]> userspace does not run at realtime
[00:37] <KragenSitaker> indeed not
[00:37] <KragenSitaker> if i can get the presses sequenced, especially if i can get timestamps, i can do whatever debouncing is necessary at user level
[00:38] <KragenSitaker> and the usual kind of application --- turning the wireless off, resetting the router --- probably doesn't care very much either way
[00:39] <KragenSitaker> if the button bounces the wrong number of times, either it's idempotent or the guy will press the button again to get the right solution
[00:41] <[mbm]> so help me understand exactly what you're doing here so I can reproduce it
[00:41] <KragenSitaker> so here's the current script:
[00:41] <KragenSitaker> if [ "$BUTTON" = ses ] ; then
[00:41] <KragenSitaker> if [ "$ACTION" = "pressed" ] ; then
[00:41] <KragenSitaker> echo 1; else echo 0; fi | tee -a /tmp/ledsettings > /proc/diag/led/ses_orange
[00:41] <KragenSitaker> fi
[00:41] <[mbm]> because the normal press, release doesn't cause concurrency issues
[00:42] <KragenSitaker> if i press the button repeatedly with this script in /etc/hotplug.d/button/ledflash
[00:42] <KragenSitaker> eventually i get to a state where the LED remains on
[00:42] <KragenSitaker> and the last thing in /tmp/ledsettings is a 1
[00:43] <KragenSitaker> if the kernel is asynchronously firing off /sbin/hotplug every time a button event happens, and there's hardware bouncing going on, this is guaranteed to happen eventually
[00:44] <KragenSitaker> i'm still a little sketchy on how this first link in the chain works --- I guess the *kernel* sets the ACTION, BUTTON, and SEEN variables?
[00:45] <KragenSitaker> but eventually there will be a press followed by a release a short time after --- i'm not sure what a short time means in this context, but anyway, far less than the 40-50ms needed to run /sbin/hotplug
[00:45] <KragenSitaker> actually, time /sbin/hotplug button takes a whole 100ms on my AP
[00:46] <KragenSitaker> so it's entirely plausible that the wrong hotplug script will finish first
[00:50] <[mbm]> KragenSitaker: right, the kernel basically executes the following command: "ACTION=x BUTTON=x SEEN=x hotplug button"
[00:50] <[mbm]> so the action button and seen are environment variables set by the kernel
[00:51] <FinboySlick> Any hardware hackers awake? I need a bit of info referse-engineering something.
[00:51] <KragenSi1aker> oh, and apparently if you click the heck out of the button, the AP will eventualy hang
[00:51] <Dabian> ehehehe
[00:51] <KragenSi1aker> eventually
[00:51] <KragenSi1aker> sorry about that
[00:51] <[mbm]> but you're right that if multiple copies of the hotplug script fire up in a short time span they might execute in the wrong order
[00:51] <[mbm]> FinboySlick: ?
[00:51] <Dabian> FinboySlick : LGPL, right?
[00:52] <FinboySlick> Nah, it probably isn't even legal ;)
[00:52] <FinboySlick> But I'm curious, what can I say?
[00:52] <KragenSi1aker> [mbm]: is there any other way to find out the current state of the button?
[00:52] <Dabian> You know this channel is logged forever and ever, FinboySlick ?
[00:52] <KragenSi1aker> i'd be perfectly happy with something i can poll from a small C program
[00:53] <Dabian> FinboySlick : Publicly. Free access for the FBI and other curious kids.
[00:53] <[mbm]> KragenSi1aker: we used to have it as a polled item where you'd just look at /proc .. but then people started flooding the system by constantly checking it so we switched it to an irq to tell you the state via a hotplug event
[00:53] <FinboySlick> Heh, I don't think it's *that* illegal.
[00:53] <KragenSi1aker> [mbm]: yeah, i saw that when i first started trying to figure out how to do it
[00:54] <FinboySlick> And since there is no encryption, I doubt the DMCA applies.
[00:54] <Dabian> Wasn't the DMCA broken, btw?
[00:54] <[mbm]> KragenSi1aker: I can pass more information to hotplug but I really don't want to switch back to polled
[00:54] <FinboySlick> I just have some ROM images I've managed to decompress, and now I'm trying to figure out if it's an FS I could read.
[00:54] <KragenSi1aker> Dabian: it was broken as designed :)
[00:55] <FinboySlick> 0700000 should be fat12 or fat16, right?
[00:55] <KragenSi1aker> [mbm]: what would be ideal, of course, is a way to wake up some existing process when the state changes, and then have that process read the current state --- like how epoll works
[00:55] <Dabian> FinboySlick : Which OS are you on?
[00:56] <Dabian> ahh
[00:56] <FinboySlick> This is windows. I've got a few gentoo boxes handy.
[00:56] <Dabian> Miranda == Microsoft Something.
[00:56] <Dabian> (W32)
[00:56] <Dabian> FinboySlick : Fine.
[00:56] <FinboySlick> Yeah, I love that little bit of software. I wish it was portable.
[00:56] <Dabian> FinboySlick : open a prompt, type fdisk, type l
[00:57] <KragenSi1aker> [mbm]: i'm trying to think of a way to do that that would allow that process to be a shell script
[00:57] <Dabian> FinboySlick : Tried gaim?
[00:57] <FinboySlick> Of course.
[00:57] <FinboySlick> Works quite well, but Miranda is a whole lot more modular.
[00:57] <[mbm]> KragenSi1aker: yeah, I don't want to have to register which programs get notified
[00:57] <Dabian> FinboySlick : Anyhow .. do taht on on either gentoo box, and I think you are set.
[00:57] <KragenSi1aker> [mbm]: probably by having them open a file in /proc
[00:58] <Dabian> FinboySlick s/taht/that/
[00:58] <FinboySlick> Dabian: The number is the FS magic number?
[00:58] <KragenSi1aker> [mbm]: i'll think about this for a while. i have to go grocery shopping, and maybe in the mean time i can downgrade to rc5 if it won't make me too sad
[00:58] <Dabian> FinboySlick : open a prompt, type fdisk, hit <enter>, type l, hit <enter>.
[00:59] <Dabian> (I forgot <enter> at first)
[00:59] <FinboySlick> Dabian: I have, and I can remember what that table looks like well enough anyway.
[00:59] <Dabian> FinboySlick : I don't know what it is .. but what I typed should get you somewhere, I hope.
[00:59] <FinboySlick> I'm an unix admin, I just run windows on this machine.
[01:01] <FinboySlick> So anyway. my decompressed image starts with 0x0700000000000000D8AF000000000080E8D01E8020DC
[01:02] <FinboySlick> I'm trying to figure out if it's cramfs or fat or what not. I doubt fdisk would tell me that.
[01:05] <totalanni> anyone know how to mount a mtdblock?
[01:05] <totalanni> i used redboot to create a filesystem
[01:06] <totalanni> and want to mount it...sorta like jffs2
[01:22] <EQ> how can i get mips-linux-uclibc-gcc ?
[01:22] <[mbm]> EQ: built automatically
[01:22] <EQ> hm
[01:37] <wintix> i'm using kamikaze on two fonera aps. i'm trying to set them up as a wireless bridge. the main problem is: ethernet and wireless aren't bridged by default. after a bit experimentation with brctl and one fonera in wireless mode ap i discovered that i have to add wifi0 and eth0 to a bridge that i can ping it via wifi and ethernet. i created a bridge br0 with the devices eth0 and wifi0 on both devices. one is set in ap mode, ...
[01:37] <wintix> ... the other in client mode. i can ping the bridge ips via ethernet from both ends. and i am able to ping the bridge ip of the ap with my notebook via wireless. if i try to ping the other aps bridge ip from one of the foneras i get a flashing ethernet led on the other fonera but no packets come back. any suggestions? may that be some weird firewall thing?
[01:38] <wintix> note: i have to use kamikaze because there is no atheros support in whiterussian.
[01:38] <[mbm]> your kamikaze image is slightly out of date
[01:39] <[mbm]> we used to default to wifi on, not bridged and the 'option network lan' commented out in /etc/config/network
[01:39] <[mbm]> lately we've changed to wifi bridged to lan but off, disabled by a 'option disabled 1' in the /etc/config/network
[01:40] <[mbm]> also you should really look into using wds
[01:40] <wintix> i wanted to test it with a classic ap-client setup first and then switch to wds.
[01:41] <wintix> i tried yesterdays svn version but it didn't boot.
[01:42] <wintix> no idea why, since i have no serial adapter
[01:42] <wintix> the fonera has redboot so it's quite nice to debrick but that takes about 50 minutes.
[01:42] <wintix> so i figured maybe i better try to get the old version working
[01:43] <[mbm]> well, version you have should work
[01:43] <wintix> so just uncomment 'option network lan' in the wireless config and maybe it works?
[01:43] <[mbm]> you just need to spend some more time on the configuration
[01:44] <[mbm]> that option means "this is part of the lan network" and "lan" is defined in the /etc/config/network
[01:44] <totalanni> [mbm]: how do you mount a mtdblock?
[01:44] <[mbm]> totalanni: via the mount command
[01:45] <wintix> [mbm]: in /etc/config/network i have config interface lan and config interface loopback. so it should bind to the lan port then?
[01:45] <totalanni> mount -t jffs2 /dev/mtdblock/4 /jffs
[01:45] <totalanni> like that?
[01:45] <wintix> or do i have to declare the network name seperately, [mbm] ?
[01:45] <[mbm]> totalanni: yes, but that should be mounted automatically at bootup
[01:46] <totalanni> [mbm]: does those filesystems have to be formated in anyway? i made them through "fis create" in redboot
[01:46] <[mbm]> wintix: when you do 'option network lan' in the wireless it bridges it to 'config interface lan' in the network config
[01:46] <[mbm]> wintix: which is probably what you want
[01:47] <wintix> [mbm]: yes. that is what i want. i will try that. the foneras are rebooting. hang on.
[01:47] <[mbm]> totalanni: jffs2 just requires an empty partition .. still not sure what you're doing since openwrt automatically sets up the jffs2 partition
[01:48] <totalanni> [mbm]: sorta trying to split the foneras partition into 2
[01:48] <totalanni> for no reason ;)
[01:48] <[mbm]> totalanni: I suspect you will break a few things
[01:51] <wintix> [mbm]: after uncommenting and rebooting the two foneras can't ping each other. my laptop via wireless connection to the ap can ping both foneras but no host connected to the foneras.
[01:52] <[mbm]> sounds like a firewall issue
[01:53] <wintix> i have the standard firewall.user and no other things done to the firewall, [mbm]
[01:55] <[mbm]> wintix: I don't have time to poke at it right now, try relaxing the forwarding rules, they default to drop (or if you didn't understand that just disable the firewall
[01:56] <wintix> how do i disable the firewall at all, [mbm]? sorry to bother but i really have no idea how to get rid of it.
[01:57] <hexa> wrt, ?
[01:57] <wintix> [mbm]: seems like chmod 000 /etc/init.d/firewall should take care of it, hm?
[01:58] <[mbm]> wintix: /etc/init.d/firewall disable, then reboot
[01:58] <[mbm]> or you can just run /etc/init.d/firewall stop
[01:59] <wintix> thank you, [mbm]. your help is greatly appreciated.
[02:05] <totalanni> so [mbm]...once i mount that mtdblock...will it show up in "df"?
[02:08] <wintix> [mbm]: with the firewall gone it still doesn't work. i will try with brctl again. maybe that works without the firewall.
[02:18] <totalanni> so [mbm]...once i mount that mtdblock...will it show up in "df"?
[02:19] <darmou> Does anone know what the progress is of the WGT-624? Is it vaguley usable? I notice from the wiki it's a work in progress but was not sure how much is completed.
[02:32] Action: wintix will build a new version of kamikaze now.
[02:33] <wintix> hm. being able to set the initial ip, gateway and dns is a nice feature.
[02:43] <EQ> thx
[02:43] <EQ> bye
[02:43] <EQ> :D
[02:55] <kimosabe> 2 <- > 100ohm <-> 3
[02:55] <kimosabe> 3 <- > 100ohm <-> 9
[02:55] <kimosabe> 4 <- > 100ohm <-> 7
[02:55] <kimosabe> 13 <- > 100ohm <-> 5
[02:55] <kimosabe> 2 <- > 100ohm <-> 3
[02:55] <kimosabe> 3 <- > 100ohm <-> 9
[02:55] <kimosabe> 4 <- > 100ohm <-> 7
[02:55] <kimosabe> 13 <- > 100ohm <-> 5
[02:56] <kimosabe> does any one know the correct pin out for flashing the wrt54g via jtag
[02:56] <Kevin`> you dont need that many resistors
[02:56] <kimosabe> sorry is this the correct one
[02:56] <kimosabe> i pasted it twice
[02:56] <Kevin`> im not sure of the pinout though - check the diagram on the wiki
[02:57] <kimosabe> can u give me the link please
[02:57] <Kevin`> no, im at school on my pda, search for jtag will find it I believe
[03:03] <wintix> what the hell. i just flashed the new kamikaze image and it is, in total ignorance of the config settings, 192.168.1.1 instead of 192.168.0.50 with gateway and dns set.
[03:03] <wintix> well. at least it works.
[03:04] <Weedy> wintix, check /etc/config/network
[03:05] <wintix> Weedy: yes, but i configured the wish ip in make menuconfig and thought it might actually work. :)
[03:06] <wintix> hm. it worked. the configured ip, dns and gw are set but seems like it ignored those settings on the first boot.
[03:10] <Shak-> if we set the lan interface with the settings to route to the modem, do we have to do anything with interface wan?
[03:15] <wintix> [mbm]: ping
[03:17] <wintix> [mbm]: i now have kamikaze r6733 up and running. after enabling wireless and leaving everything else to default i still can't get traffic from wireless to ethernet. same with firewall disabled.
[03:30] <Shak-> why are interfaces sometimes called eth0.1 and eth0.0 ?
[03:31] <[mbm]> vlan tagging
[03:31] <Shak-> so if I want everything to stay on the same subnet I ignore that?
[03:33] <[mbm]> it means you need to read the section of the manual about switches and vlans
[03:33] <Shak-> roger
[03:34] <Shak-> now, theres an interface wan and an interface lan, if I configure the lan interface with a static ip and give it a gateway to 192.168.1.254 (modem), what does the wan interface do?
[03:35] <Shak-> im dealing with a fonera here (only one ethernet port) so I figured the lan connection goes to the modem
[04:17] <darmou> Does anone know what the progress is of the WGT-624? Is it vaguley usable? I notice from the wiki it's a work in progress but was not sure how much is completed.
[04:17] <johnf_> quick question, I'm working on a presentation on open source routers and openwrt
[04:17] <johnf_> and I wanted to know
[04:17] <johnf_> when was the first version of openwrt released?
[04:17] <darmou> the WGT-624 is a Netgear btw
[04:52] <Quazgaa> what doc should i read to setup openwrt to act as an access point for my cable modem
[04:55] <obnauticus> Hmm
[04:55] <obnauticus> can someone help me
[04:55] <obnauticus> I bricked my router, and I did that thing where i jump the shit
[04:55] <obnauticus> like short the two pins on it.
[04:55] <obnauticus> I have a WRT54G v6 btw
[04:55] <obnauticus> and umm it replies to pings
[04:55] <obnauticus> i tftp
[04:55] <obnauticus> tftp'd my firmware onto it.
[04:55] <obnauticus> and it still won't work...
[04:55] <obnauticus> well
[04:55] <obnauticus> it replies to pings..
[05:59] <Quazgaa> anybody around
[06:00] <obnauticus> I am.
[06:01] <Quazgaa> is there a problem with wpa2 in whiterussian 0.9
[07:00] <Anti-Police> Isn't /etc/hotplug.d/usb/01-ln wrong? it points to "/dev/scsi/host${HOST}/bus0/target0/lun0" but my usb device is /dev/sda
[07:02] <bre-bri> can be the same device. scsi devices are listed like that
[07:02] <bre-bri> just try a dd on the device and look if the first bytes are equal ;)
[07:04] <Anti-Police> the /dev/scsi directory doesnt exist though, that normal?
[07:04] <bre-bri> nope
[07:05] <bre-bri> usually it should be there
[07:05] <Anti-Police> hasnt been there for me with latest kamikaze for the past few months
[07:06] <bre-bri> actually, I don't have a kamikaze running with usb
[07:07] <bre-bri> but you can just create the path and mknod the device
[07:08] <bre-bri> it would be mknod /dev/scsi/0/bus0/target0/lun0 8 0 probably
[07:09] <bre-bri> or just file a bug ;)
[07:39] <totalanni> hey guys
[07:39] <totalanni> for a wrap board
[07:39] <totalanni> what image would i use?
[08:14] <Quazgaa> in client mode, how do i get openwrt to statically connect to an access point
[08:15] <Quazgaa> dhcp sets things up fine
[08:15] <Quazgaa> but i dont know how to bring the connection up without using dhcp
[08:40] <Quazgaa> anybody around that knows anything
[08:43] <sep> Quazgaa, i dont know if i know anything you need help with. but i know you'r never going to get help with so little real detail in your problem description
[08:43] <Quazgaa> yeah ive been idling in here all night with no intelligent activity
[08:44] <Quazgaa> im trying to figure out how to get openwrt (in client mode) to statically connect to an openwrt access point
[08:45] <Quazgaa> i dont want it to use dhcp to obtain a lease on an ip
[08:45] <Quazgaa> and i shouldnt have to do everything manually
[08:46] <Quazgaa> 'ifup wan' is kinda handy
[08:48] <sep> Quazgaa, your doing something like ? http://martybugs.net/wireless/openwrt/client.cgi
[08:48] <Quazgaa> yes
[08:48] <Quazgaa> the client already "works"
[08:49] <Quazgaa> im just trying to use it to connect in a different way
[09:36] <sn9_> hello, everyone
[10:34] <as> is there a way to log in a file? or can i only log into logread ... imanaged to boot from a hd .... therefor id like to change the logging options ... can this be done while the system is up and running?
[11:12] <as> how can i mount all drives in fstab at bootup?
[11:14] <Ge0rG> "mount -a"
[11:34] <sn9_> ok, this is just wrong: why is "make menuconfig" in kamikaze broken in this way? out of all the things that can go wrong... http://www.busybox.net/lists/busybox/2006-March/019107.html
[11:41] <sn9_> can't use make 3.80 for even a simple "make menuconfig"
[11:45] <sn9_> is this affecting anyone else?
[11:50] <hundfred> need help: how to switch of the option usepeerdns / pppoe ? root 200 S /usr/sbin/pppd nodetach plugin rp-pppoe.so connect /bin/true usepeerdns defaultroute replacedefaul
[11:55] <ronny> re
[12:49] <Suschman> morning
[12:50] <Kevin`> morning
[12:53] <Suschman> someone here who has an br6140k router?
[12:53] <Suschman> sry, 6104
[12:54] <Kevin`> what "board type" is that
[12:54] <Kevin`> has a bunch of ? in the table of hardware, that could do with filling in :)
[12:54] <Kevin`> oh K
[12:55] <Suschman> i have the kp, exactly with usb
[12:56] <Suschman> im interrested in testing openwrt on it, serial connection is there
[12:56] <Suschman> trying compile run atm
[12:56] <Kevin`> well obviously I don't have one, but what problems are you having?
[12:56] <Suschman> there is a edimax image target in svn, but i dont see how to select it
[12:57] <Suschman> so i build jffs2 image now with no wifi selected
[12:57] <Kevin`> you might need to select the "enable broken/experimental" option
[12:57] <Suschman> i have
[12:57] <Suschman> edimax uses a fixed ofset to jump into the kernel, hardcoded to the start of the 2.4.18 original kernel (argh)
[12:58] <Suschman> so i dont expect the openwrt kernel to boot straight off with the headers addet :(
[12:58] <Kevin`> there's an option for the entry point somewhere in the kernel config
[12:59] <Suschman> i have do hand-edit these (not by menuconfig) ?
[12:59] <Kevin`> I suspect so, unless you see the option there
[12:59] <Suschman> ok
[13:01] <Suschman> hrml
[13:01] <Suschman> actual svn does not compile
[13:01] <Suschman> hehe
[13:01] <Suschman> have to wait a bit it seems
[13:02] <Suschman> now the new bluetooth stuff hangs at kernel module stage
[13:02] <Kevin`> why do you have bluetooth
[13:03] <Suschman> cp: cannot stat `/data/home/suschman/edimax/openwrt/trunk/build_mipsel/linux-2.6-adm5120/modules/lib/modules/2.6.19.2/kernel/
[13:03] <Suschman> drivers/bluetooth/hci_usb.ko': No such file or directory
[13:03] <Suschman> make[3]: *** [/data/home/suschman/edimax/openwrt/trunk/bin/packages/kmod-bluetooth_2.6.19.2-adm5120-1_mipsel.ipk] Error 1
[13:03] <Suschman> duno, default selection
[13:04] <Kevin`> mm that's interesting, I wonder why that file would not exist
[13:05] <Suschman> i had this 3 revision before with the kmod sheduler
[13:05] <Suschman> seems florian is still commiting stuff
[13:06] <Kevin`> i'd just poke one of the developers when they wake up
[13:06] <Suschman> nah, i think this clears itself. florian adds revision like all 15 minutes atm
[13:06] <Suschman> :)
[13:06] <des> seems like a .config problem, which is reasonable given all the changes in that areas
[13:07] <Suschman> cul
[13:08] <Susch|AW> i check back later
[13:50] <Ge0rG> is it possible to configure one of the wrt54g switch ports as a monitor port for the WAN interface?
[13:50] <Kevin`> yes
[13:51] <Ge0rG> can it be done with robocfG?
[14:16] <johnf_> whoa
[14:17] <johnf_> monitor ports? nice!
[14:17] <crazy_imp> ?
[14:17] <johnf_> I was unaware of that capability
[14:18] <Ge0rG> so the question still is: how can I do it?
[14:25] <as> whats the advantages i get from the 2.6 kernel compared to 2.4?
[14:25] <as> what are the advantages i get from the 2.6 kernel compared to 2.4?
[14:43] <zabi> bot : |
[14:43] <Weedy> zabi, hda?
[14:44] <Weedy> wouldnt you be better off with dd?
[14:44] <zabi> nope i tried mtd0 as thats what was in /proc/mtd
[14:44] <zabi> yea that works
[14:44] <Weedy> the util dd
[14:44] <zabi> i just waanted to avoid removing the cf card from slot again and again
[14:45] <nbd> you can use dd on the device itself
[14:45] <zabi> ohh yea
[14:45] <Weedy> i have no idea about x86 boards, but i assume dd on /dev/hda
[14:45] <Weedy> damn nbd beat me
[14:46] <zabi> fine ill figure it out.thanks.i was stuck on mtd as thats whay i saw in xwrt upgrade script
[14:46] <johnf_> Ge0rG: it looks to me (and I'm no expert) that you would need to do it yourself, possibly using bridging, unless there are options to the vconfig command that I don't know about, and that aren't documented
[14:47] <Ge0rG> johnf_: vconfig won't help... rather brctl
[14:47] <johnf_> did you read what I said?
[14:48] <johnf_> unless vconfig can do it using secret options
[14:48] <johnf_> you will need to do it using bridging, yourself (which obviously means you'll need to use brctl)
[14:54] <Ge0rG> johnf_: actually I just wondered how vconfig could enable this feature at all
[14:55] <Ge0rG> Kevin`: do you have some more insights?
[15:02] <johnf_> bbl, meeting
[15:07] <zabi> Weedy,nbd: dd brings the same problem dd if=firmware.image of=/dev/hda
[15:07] <nbd> is the firmware image located in ram?
[15:09] <zabi> well its on the /frimware.image so not on ram
[15:10] <zabi> i mean i have the image on cfcard
[15:10] <Weedy> put it in /tmp/
[15:10] <Weedy> /tmp/ is ram on x86 isnt it?
[15:10] <zabi> ohh ok /tmp's the ram
[15:10] <Weedy> source and destinantion cannot be the same :P
[15:29] <zabi> Weedy,nbd:thanks it works with dd :)
[15:41] <nbd> as: no
[15:42] <as> nbd: where does this driver work?
[15:42] <as> is the a driver for my cad that isnt completly developed?
[15:43] <nbd> as: it's not ready and it'll be a while before it is
[15:43] <as> and nbd does the 2.6 kernle work smoother then the 2.4?
[15:43] <as> kernel
[15:44] <nbd> typically yes, but of course not with broadcom wifi
[15:44] <as> i dont need the wifi
[15:44] <nbd> try it and see if it works well for you
[15:44] <as> im using 2.4 now .. but it feels very ... slow ... maybe 2.6 changes this
[15:44] <nbd> slw? how?
[15:44] <as> ssh connections seem to stuck
[15:45] <as> and then after some seconds they work again
[15:45] <as> maybe i should test openssh
[15:45] <nbd> don't bother
[15:45] <nbd> it's not going to work any better
[15:45] <as> why
[15:46] <as> nbd in my homelan i never have this stucking .... when im online over inet it's not working very well
[15:47] <as> nbd whats the cause for this?
[15:47] <nbd> no idea
[15:47] <as> nbd do the same happen to u?
[15:47] <as> does the same happen to u
[15:47] <nbd> no
[15:48] <as> are u on openssh or dropbear?
[15:50] <nbd> sorry, i'm busy right now
[15:50] <as> okay
[15:50] <as> thanks
[15:52] <as> do i need udev on the 2.6 kernel?
[15:54] <nbd> don't worry about what you need, the openwrt build system will take care of things for you
[15:55] <toboz> scuse me to disturb you but do you know if the fastcgi module works with perl scripts ?
[15:57] Action: agaffney has been disturbed!
[16:04] <as> <nbd> but i select the modules by my own ... and udev isnt selected .....but --- udevtrigger.. Small utility to request kernel devices events for coldplug ---- is .....
[16:12] <nbd> as: and that's the way it should be
[16:18] <as> nbd thanks
[16:41] <jan_> i'm looking at the TableOfHardware
[16:41] <jan_> but so many are supported
[16:41] <jan_> now
[16:41] <jan_> what do YOU think is the best suitable device?
[16:42] <jan_> what chipset? what ..? etc :)
[16:42] <jan_> i'm thinking about linksys anyway
[16:43] <jan_> (perhaps the device with most flash/ram ?
[16:51] <jan_> i'm thinking about WRTSL54GS , lates is v7 i think, but i have no clue if it's supported
[16:58] <sn9_> jan_: asus wl-500g premium is the cheapest thing with 8/32, just like the wrtsl54gs
[16:59] <Ge0rG> an 8/32 device with atheros wlan would be nice to have
[17:00] <sn9_> there has been no v7 of the wrtsl54gs, btw
[17:00] <Wonka> Ge0rG: meraki mini? fonera?
[17:00] <sn9_> wrtsl54gs is only up to v1.1 on wikipedia
[17:02] <Ge0rG> Wonka: one that I can actually buy without signing some kind of social contract?
[17:02] <Wonka> Ge0rG: meraki mini
[17:02] <Wonka> Ge0rG: http://meraki.net/products/mini/
[17:03] <sn9_> jan_:
[17:03] <sn9_> http://wiki.openwrt.org/OpenWrtDocs/Hardware/Linksys/WRTSL54GS
[17:03] <sn9_> http://wiki.openwrt.org/OpenWrtDocs/Hardware/Asus/WL500GP
[17:05] <sn9_> also, if you buy older equipment, you may get more flash/ram
[17:05] <Ge0rG> Wonka: looks exactly like the idea behind fon... what are the implications of installing my own firmware?
[17:05] <Kevin`> Ge0rG they don't offer support for unnoficial software. beyond that, nothing
[17:06] <Ge0rG> then I'd only need a german distributor
[17:07] <Kevin`> they ship worldwide last I heard
[17:07] <fiXXXerMet> Problem with my openwrt + x-wrt. The webif come up fine, I can modify and save changes fine, but I can't see the wireless network when I scan
[17:07] <thepeople_work> fiXXXerMet: kamikaze?
[17:07] <fiXXXerMet> Nope
[17:08] <nullboy> fiXXXerMet: what hardware?
[17:08] <fiXXXerMet> White Russian 0.9. WRTSL54GS
[17:08] <thepeople_work> if you refesh the page 2-3 times does anything come up?
[17:09] <fiXXXerMet> You mean where I am browsing for the wireless network? Nope, nothing.
[17:09] <fiXXXerMet> Mode: Access Point. Correct?
[17:10] <fiXXXerMet> OK, changed the channel from 6 to 11 and now it shows up, but with a very weak single, though the router is only ~20 feet away
[17:11] <fiXXXerMet> Not showing up, nevermind. Must be a really weak single
[17:11] <fiXXXerMet> signal?
[17:11] <thepeople_work> looks like it
[17:11] <thepeople_work> or that is what the broadcom driver is reporting
[17:12] <fiXXXerMet> Going to try moving the router - it's sitting ontop of our 40-port switch
[17:12] <thepeople_work> I do know the page works
[17:15] <fiXXXerMet> The page? Yes, I'm at it now.
[17:15] <fiXXXerMet> I'm going to post my settings, maybe I have something configured wrong.
[17:15] <Kevin`> fiXXXerMet post nvram show|sort output
[17:16] <thepeople_work> fiXXXerMet: try running "iwlist wl0 scan" from the command line
[17:16] <fiXXXerMet> The command line of the router?
[17:16] <thepeople_work> yes
[17:17] <fiXXXerMet> root@OpenWrt:~# nvram show|sort output
[17:17] <fiXXXerMet> sort: output: No such file or directory
[17:17] <fiXXXerMet> root@OpenWrt:~# iwlist wl0 scan
[17:17] <fiXXXerMet> wl0 Interface doesn't support scanning.
[17:17] <thepeople_work> just run iwlist scan
[17:17] <fiXXXerMet> Same for lo, eth0, eth1, br0. eth2 says "No scan results"
[17:18] <thepeople_work> run the command a couple of times in a row
[17:18] <thepeople_work> I think I might know that is wrong
[17:18] <fiXXXerMet> http://www.pastehere.com/?jtikmx is the wireless configuration page.
[17:18] <fiXXXerMet> Just ran 6 times - same results.
[17:20] <thepeople_work> well the broadcom driver isn't returning any results. I don't know how afterburner may effect that though
[17:20] <fiXXXerMet> It was on g with b deferred. I'll try some others
[17:21] <thepeople_work> it shouldn't matter
[17:21] <fiXXXerMet> oh
[17:21] <fiXXXerMet> Doesn't it have to be in client mode to show results?
[17:22] <thepeople_work> not in 0.9
[17:22] <fiXXXerMet> oh
[17:23] <sn9_> is the problem i've run into a known issue? (scroll up about 6 hrs)
[17:24] <thepeople_work> sn9_: repaste the problem
[17:25] <sn9_> it was described at http://www.busybox.net/lists/busybox/2006-March/019107.html
[17:25] <fiXXXerMet> Well the network is showing up pretty consistantly now, just with a very weak signal.
[17:25] <sn9_> this is kamikaze
[17:26] <sn9_> still present in rev 6742
[17:27] <sn9_> even "make menuconfig" doesn't work
[17:27] <thepeople_work> sn9_: I am of no help on this issue
[17:28] <sn9_> not encountered it?
[17:28] <thepeople_work> nope
[17:28] <sn9_> so, everyone uses make 3.79 or 3.81 and not 3.80?
[17:28] <thepeople_work> I am using 3.81
[17:29] <fiXXXerMet> Be back in a bit.
[17:30] <toboz> thepeople_work: excuse me to bother you one more time, but as microperl seems to be build without the md5 function, all my scripts fail. So do you know where I can find an other microperl package with md5 or can you explain how to build perl with md5 with the OpenWRT SDK ?
[17:31] <agaffney> toboz: `which md5sum`
[17:31] <sn9_> 3.81 being a requirement is not stated anywhere that i've seen, so i'm having a hard time believing that it's mere coincidence that nobody tries to build with 3.80
[17:32] <thepeople_work> toboz: I don't use perl. To include it you would have to edit the makefile, I think
[17:37] <toboz> agaffney:Digest::MD5
[17:38] <as> i have created a /etc/fstab file and put the command mount -a into my init.d/boot script
[17:38] <h3sp4wn> toboz: Its not simple to build a full perl - read - Cross/README (maybe you can adept it for mipsel)
[17:38] <toboz> agaffney:md5 md5_hex md5_base64
[17:39] <toboz> h3sp4wn: I think so yes ... not easy it's sure
[17:39] <as> and this line is inside my fstab
[17:39] <as> "/dev/scsi/host0/bus0/target0/lun0/part2 none swap sw 0 0"
[17:39] <as> but my swappartition isnt mounted at boot time
[17:39] <as> how do i change this?
[17:55] <toboz> thanks for your help, I'm going to try to build perl and mysql, tell me good luck :) - many thanks for your help !
[18:20] <nullboy> sysctl: error: 'net.ipv4.tcp_syncookies' is an unknown keysysctl: error: 'net.ipv4.ip_conntrack_tcp_timeouts' is an unknown key
[18:20] <nullboy> sysctl: error: 'net.ipv4.ip_conntrack_udp_timeouts' is an unknown key
[18:20] <nullboy> oh crap
[18:20] <nullboy> sorry
[18:21] <nullboy> well...anyone know what that is all about?
[18:21] <nullboy> lol
[18:21] <nullboy> kami
[18:21] <nullboy> i get that via serial port output on startup
[18:22] <bstock> hey, if i setup WDS on my WRT54GL running RC6, does that hurt overall performance? i thought i had read that somewhere
[18:30] <nullboy> bstock: yes
[18:30] <h3sp4wn> nullboy: remove them from /etc/sysctl.conf
[18:30] <nullboy> bstock: you have to divide wifi bandwidth between WDS stuff and client access
[18:30] <nullboy> h3sp4wn: thanks
[18:31] <nullboy> h3sp4wn: i have a serial port on this little bugger now so i can see a whole lot more
[18:37] <bstock> thanks
[18:41] <fiXXXerMet> Any suggestions on why my signal strength might be so low?
[18:55] <shadsec> anyone knows how to add a "dummy" interface to openwrt? ie: assigning more than one ip addresses to one interface
[18:58] <nullboy> http://pastebin.ca/413698
[18:58] <nullboy> how can i stop that spamtastic output?
[18:58] <nullboy> i just keeps outputting that to console
[18:59] <crazy_imp> shadsec: ifconfig <interfacename>:1 ip
[19:02] <shadsec> crazy_imp, great, thanks!
[19:20] <davidg> what is the approved way to get kamikaze make to re-patch the kernel before compiling it?
[19:21] <nullboy> so anyone know how to fix this: http://pastebin.ca/413698
[19:21] <nullboy> it keeps spamming that whenever i enable wifi
[19:24] <h3sp4wn> nullboy: Are you using multissid ?
[19:25] <nullboy> nope
[19:25] <h3sp4wn> one in ap mode - one in sta mode (anything out of the ordinary)
[19:26] <nullboy> all i did was enable the wifi inteface
[19:27] <h3sp4wn> as an accesspoint ?
[19:27] <h3sp4wn> be clear (I cannot be bothered for 20 questions)
[19:27] <nullboy> h3sp4wn: nevermind, i'll figure it out myself. i was just wondering if that was a common issue with a common fix. sorry.
[19:28] <h3sp4wn> nullboy: The only time I have seen that is when using more than virtual interface (without using nobeacon)
[19:29] <nullboy> h3sp4wn: in that scenario, what was the fix?
[19:30] <h3sp4wn> using nobeacon (its an option with wlanconfig) but you shouldn't need it for a single interface
[19:30] <h3sp4wn> look in madwifi.sh and find the relevant bit for the config option
[19:30] <nullboy> h3sp4wn: i'll mess with the wifi driver options
[19:30] <nullboy> yep
[19:31] <fiXXXerMet> My WLAN is reporting 7 dBm transmit power and -98 dBm noise level. Are these normal?
[19:31] <nullboy> i must say that playing with these routers and openwrt is a great way to start learning about embedded stuff
[19:38] <Heini66> fiXXXerMet: on what device?
[19:38] <daxroc> Where would I start debuging why my wrt needs frequent restarts ( just functioning as a bridge with wpa(tkip) )
[19:38] <fiXXXerMet> Heini66: WRTSL54GS
[19:38] <nbd> daxroc: bridge as in client bridge?
[19:39] <daxroc> yeah
[19:40] <Heini66> fiXXXerMet: something wrong wtih antenna's and/or setup for it?
[19:40] <fiXXXerMet> My signal strength is very weak (~20 feet away and barely any connection). Trying to find the problem.
[19:40] <fiXXXerMet> Wondering if those were OK
[19:44] <daxroc> nbd, using it for online gaming so Im thought it might be the transfer but its only in/out (7.55 MB/49.12 MB)
[19:44] <puchu> does the 2.6 config use the same config scripts as 2.4 or is the complete system managed with other scripts?
[19:45] <nbd> same config scripts, same base system
[19:45] <puchu> cool thanks
[19:51] <davidg> nbd: what is the best way to get the kamikaze build system to re-patch the kernel?
[19:51] <nbd> re-patch? how?
[19:52] <davidg> nbd: reapply the patches from the target/linux/*/patches
[19:52] <nbd> why should it do that?
[19:52] <davidg> nbd: against a clean kernel, I have changed a patch and I want it to start again
[19:52] <forum2006> make target/clean world
[19:52] <nbd> ah
[19:52] <nbd> yeah, that command does the trick
[19:53] <nbd> but use target/linux-clean instead of target/clean
[19:53] <forum2006> what's the difference?
[19:53] <fiXXXerMet> So is 7 dBm and -98 dBm noise level normal?
[19:54] <davidg> ta, I had tried clean and distclean, but I had not come across these target ones.
[19:54] <nbd> forum2006: target/clean nukes sdk, imagebuilder and linux kernel
[19:54] <nbd> forum2006: target/linux-clean just nukes the kernel
[19:54] <forum2006> ah. so for rebuilding the kernel target/linux-clean is the faster way :)
[19:55] <nbd> yep
[19:57] <sn9_> make[4] -C toolchain/gcc install <-- this step sure takes a long time
[19:57] <CaNsA> openwrt on a wrt54gsv6 can it be done? or shall i stick with the ddwrt?
[19:58] <Teemu_k> CaNsA: go and see table of hardware
[19:58] <Teemu_k> at www.openwrt.org
[19:59] <CaNsA> it says Wip. so i guess it can. but will openwrt be more flexible?
[19:59] <CaNsA> like, is is poss to run a shell on a router?
[19:59] <CaNsA> for irc and stuff
[19:59] <forum2006> no. not on a v6. to little flash and ram. get a better router :)
[20:00] <CaNsA> if i add a sd reader, will that help?
[20:00] <forum2006> still too little ram
[20:00] <sn9_> it's 16MB ram -- too little?
[20:01] <h3sp4wn> possible to use a 2/16 device but only for very specific purposes
[20:01] <sn9_> original wrt was 4/16, iirc
[20:02] <thepeople_work> sn9_: ram isn't the issue with 16meg flash is
[20:02] <sn9_> that's what i thought
[20:03] <CaNsA> 16meg flash? i thought the max on a wrt was 8
[20:03] <sn9_> CaNsA: "16meg, flash" not "16meg flash"
[20:04] <thepeople_work> ram isn't the issue with 16meg, flash is
[20:04] <CaNsA> ahh i c
[20:04] <CaNsA> :P
[20:04] <CaNsA> i guess ill go kik myself in the balls
[20:05] <fiXXXerMet> Something has to be wrong. Tested with two computers wnic, both (w)are no more than a foot away from the router, and still a terrible signal strength
[20:06] <sn9_> CaNsA: when you've finished doing that, try some of the micro images
[20:06] <CaNsA> im having a looksee at http://www.bitsum.com/openwiking/owbase/ow.asp?WRT54G5_CFE
[20:07] <CaNsA> sn9_, would this be the one then?
[20:07] <CaNsA> openwrt-wrt54gs-squashfs.bin
[20:07] <CaNsA> 1.3M
[20:08] <fiXXXerMet> Maybe trying out kamakizi would help?
[20:10] <CaNsA> brb
[20:10] <thepeople_work> fiXXXerMet: could be bad hardware also
[20:10] <sn9_> CaNsA: has to be in a folder called "micro"
[20:11] <fiXXXerMet> thepeople_work: Yes. I suppose the best idea is to flash it's original firmware and then test. can I just flash from the webif of openwrt/x-wrt with the original?
[20:12] <thepeople_work> yes
[20:12] <thepeople_work> should be able to
[20:21] <Jkx> Hy all I'm just trying to build kamikaze (for a WGT634U), but i get a lot of errors...like this:
[20:21] <Jkx> bin/sh: tmp/info/.pkginfo-aodv-uu: No such file or directory
[20:21] <agaffney> Jkx: that's a very vague and useless error
[20:21] <agaffney> Jkx: pastebin a bit more
[20:22] <Jkx> agaffney: I get it.. ./tmp/info/ is missing ..
[20:23] <sn9_> 634u still needs kamikaze, too?
[20:23] <agaffney> there is no atheros support in whiterussian
[20:23] <agaffney> and likely never will be
[20:23] <sn9_> oh, that's right, 634u is atheros -- i forgot that
[20:24] <fiXXXerMet> OK, told openwrt to upgrade the firmware from it's webif. That was a few minutes ago, and the page is still loading
[20:24] <Jkx> sn9_: 634u use a atheros wireless card (not a CPU like on fonera)
[20:25] <sn9_> oh, white russian can't even use that, either?
[20:26] <nbd> Jkx: fixed now
[20:27] <fiXXXerMet> thepeople_work: OK, flashed with newest linksys firmware and signal is at 100%, where-as with 0.9 it was at ~10%
[20:27] <sn9_> i'm feeling even more adventurous than trying the atheros port -- building rdc-2.6 right now
[20:28] <nbd> don't bother
[20:28] <nbd> it won't work
[20:28] <nbd> at least not properly
[20:28] <sn9_> i wanna see exactly how it fails
[20:29] <sn9_> i backed up the original fw (assuming the hd doesn't fail), so i can always undo it
[20:29] <sn9_> serial console works beautifully
[20:29] <nullboy> hell yeah
[20:29] <nbd> sn9_: so if you think you can help with fixing it, [florian]'s the guy to talk to
[20:30] <sn9_> can't help fix until i see what's wrong
[20:30] <nbd> :)
[20:31] <sn9_> so i'll wait at least until it finishes building before pinging him
[20:31] <nullboy> i made the USB->serial cable mod for my serial console
[20:31] <nullboy> uses the PL-2303
[20:31] <nbd> sn9_: yes
[20:32] <sn9_> nullboy: i tried that first and have a $20 paperweight. maxim-ic to the rescue
[20:33] <Jkx> nbd: what is fixed now ?
[20:33] <nullboy> sn9_: haha you bricked the serial adapter
[20:33] <nullboy> lol
[20:33] <sn9_> yes
[20:33] <nullboy> i had to resort to the chip maker's pin out
[20:33] <nbd> Jkx: the missing tmp/info thing
[20:33] <sn9_> i'd love to unbrick that, too
[20:34] <Jkx> nbd: ok ;)
[20:35] <sn9_> and mine didn't even use Prolific Semi
[20:35] <sn9_> chip maker's pinout is not enough; i need an expert in surface-mount soldering :(
[20:35] <fiXXXerMet> Does the whiterussian snapshot include a webif?
[20:37] <sn9_> fiXXXerMet: http://x-wrt.org/
[20:37] <fiXXXerMet> Erm s/whiterussian/kamakazi
[20:38] <fiXXXerMet> I used the http://downloads.openwrt.org/snapshots/brcm-2.4/openwrt-wrtsl54gs-2.4-squashfs.bin file
[20:38] <thepeople_work> the webif is broke in kamikaze at the monment
[20:38] <thepeople_work> moment
[20:38] <fiXXXerMet> oh :(
[20:38] <thepeople_work> hope to have it fixed soon
[20:38] <fiXXXerMet> fair enough :)
[20:39] <fiXXXerMet> well... I guess I'll have to use the linksys firmware for a while, unless someone else has an idea why 0.9 would be destroying my signal strength?
[20:39] <fiXXXerMet> (100% using linksys')
[20:39] <thepeople_work> or look at http://wiki.openwrt.org/OpenWrtDocs/KamikazeConfiguration for help configuring kamikaze from the commandline
[20:40] <sn9_> nullboy: it took me many hours just to solder the max3232
[20:40] <nullboy> sn9_: did you PCB it or just mid air it?
[20:40] <sn9_> mid-air, of course
[20:40] <nullboy> hehe
[20:40] <sn9_> why did you think it took so long?
[20:41] <nullboy> i was going to mid air the PL-2303 but that chip is even smaller and even higher pin density than the mx
[20:41] <nullboy> max*
[20:41] <sn9_> pl-2303 is surface-mount only, too
[20:42] <nullboy> it's a tiny little thing
[20:43] <sn9_> the mid-air approach was only possible for me using a DIP ic-socket
[20:43] <nullboy> that is a good method though
[20:43] <sn9_> i even broke a couple of pins on the socket in the process
[20:43] <nullboy> you risk screwing up the chip if you don;t do that
[20:44] <nullboy> so i just realized that carrying around a box of assorted heat shrink tubing might be the sign that you have a problem
[20:45] <sn9_> that's why, when i was done, i encased as much of the circuit as i could in candle wax before putting the chip in the socket
[20:48] <nullboy> hey so in the snapshots download area of openwrt, is it just a daily script regardless of having changes or not? or does it only get a new date if there were changes made?
[20:50] <nullboy> http://downloads.openwrt.org/snapshots/_USE_AT_OWN_RISK_
[20:50] <nullboy> nm
[20:50] <nullboy> ;)
[20:50] <sn9_> nullboy: which hardware are you using, again?
[20:50] <nullboy> fon
[20:50] <sn9_> ah, nice and spacious
[20:50] <nullboy> yep
[20:51] <nullboy> that 8mb flash is really the only good thing
[20:51] <nullboy> and the atheros
[20:51] <nullboy> but the package...
[20:51] <sn9_> 8/32 seems the most one can get in a consumer-priced device
[20:52] <h3sp4wn> There is some nas devices with more
[20:52] <nullboy> sn9_: i;ve been tempted to spend the bucks on that 16mb Avila
[20:52] <sn9_> buffalo tech discontined their 8/64 stuff
[20:52] <sn9_> *discontinued
[20:52] <h3sp4wn> buffalo sells a linkstation pro (with either 8 or 16 - 128)
[20:53] <h3sp4wn> and a drive
[20:57] <michube> hello... just a question, i try to compile the soundmodule for whiterussian, i configured the kernel in (openwrt/build_mipsel/linux), i compiled all modules (make modules), and i also see the compiled modules... but HOW do i create the ipkg package?
[21:05] <michube> any help?
[21:06] <sn9_> michube: have you seen this? http://wiki.openwrt.org/OpenWrtDocs/Packages
[21:07] <sn9_> oops, i mean http://wiki.openwrt.org/BuildingPackagesHowTo
[21:09] <michube> i read http://wiki.openwrt.org/BuildRoot?highlight=%28module%29%7C%28kernel%29#Creatingpackagesforkernelmodules.. but it looks lik
[21:09] <michube> e this is just for linux 2.6
[21:10] <michube> can i just copy the soundcore.o to the openwrt?
[21:10] <sn9_> sure, but that's not an ipkg
[21:11] <sn9_> btw, is there an sshfs ipkg anywhere?
[21:11] <h3sp4wn> No use shfs
[21:12] <h3sp4wn> (if its working)
[21:12] <sn9_> shfs?
[21:12] <h3sp4wn> similar thing but its smaller (and doesn't need fuse)
[21:12] <sn9_> really?
[21:13] <h3sp4wn> sn9_: Haven't tried it recently (and its not maintained)
[21:13] <sn9_> url?
[21:13] <h3sp4wn> its in openwrt
[21:13] <h3sp4wn> No idea of a url
[21:14] <sn9_> i'll just look at the readme in the openwrt tree, then
[21:15] <h3sp4wn> I have never needed any docs for it (its kind of obvious how to use it)
[21:15] <sn9_> not from the name alone, it isn't
[21:16] <h3sp4wn> With the Makefile for it you get a pretty good idea
[21:17] <h3sp4wn> but it is marked as broken hmmm
[21:17] <sn9_> ok, Makefile has a url...
[21:18] <fiXXXerMet> Anyone here on the X-Wrt dev team?
[21:19] <thepeople_work> fiXXXerMet: I am
[21:19] <thepeople_work> fiXXXerMet: we are in #x-wrt
[21:19] <fiXXXerMet> oo
[21:21] <forum2006> nbd, how to make telnet still enabled/working after setting a password?
[21:21] <nbd> why do you want that?
[21:21] <h3sp4wn> sn9_: Its working on gentoo the patches probably just need ripping from there if you want to
[21:22] <sn9_> nice to know
[21:23] <sn9_> i just noticed that fuse was being built for openwrt, and thought that would be the best use for it. bypassing fuse is even better
[21:23] <forum2006> nbd, because this router is in my lan, behind another nat router and windows have only telnet
[21:23] <sn9_> it's on to openssl now
[21:23] <nbd> forum2006: why don't you install putty there?
[21:23] <nbd> :)
[21:24] <forum2006> i see no reason for installing putty there. i like to use telnet
[21:24] <h3sp4wn> every windows should have putty.exe in c:\winnt
[21:24] <nbd> you can of course hack the scripts a bit to keep telnet open
[21:25] <nbd> but it's easier to just install putty :)
[21:25] <johnf_> it's easy
[21:25] <johnf_> if you use telnet, you have no security anyways
[21:25] <johnf_> so just don't set a password
[21:25] <johnf_> and you can continue to use telnet
[21:26] <johnf_> see, easy :)
[21:26] <sn9_> hehe, every windows should either have, or be in, a virtual machine
[21:26] <forum2006> lol
[21:27] <sn9_> that way, you don't have to keep looking for extra stuff to install
[21:27] <johnf_> it's been fun, but I'll ask my history of openwrt question on the forum
[21:27] <johnf_> later
[21:28] <sn9_> a login passwd? lol. i was thinking a .htaccess-type thing...
[21:29] <forum2006> nbd, which scripts should i look for?
[21:30] <Le_Vert-Ntbk> hey mates
[21:30] <Le_Vert-Ntbk> what's openwrt state on wgt634u
[21:30] <sn9_> forum2006: if it's lan-only, why even have a login passwd?
[21:30] <Le_Vert-Ntbk> http://downloads.openwrt.org/snapshots/brcm47xx-2.6/
[21:31] <sn9_> Le_Vert-Ntbk: from what i've heard, the 634u greatly suffers from an underpowered cpu
[21:31] <Le_Vert-Ntbk> there's a image in snapshots
[21:31] <Le_Vert-Ntbk> but I don't know if it works fine
[21:31] <Bracki> where can i find detailed logs for troubleshooting? if got a pcmcia card and i just cant associate. logread doesnt show anything though...
[21:31] <h3sp4wn> My wgt634u is working better than any hardware I have
[21:31] <Bracki> if/i've
[21:31] <h3sp4wn> (only one feature is missing)
[21:32] <Le_Vert-Ntbk> tell me more h3sp4wn
[21:32] <sn9_> h3sp4wn: which feature?
[21:32] <Le_Vert-Ntbk> I'm plan to buy one for routing, wlan, openvpn and maybe backup MX
[21:32] <Le_Vert-Ntbk> s/'m//
[21:32] <h3sp4wn> sn9_: The crypto hardware (but its also broken on the wl500-gd I have)
[21:33] <Le_Vert-Ntbk> oh
[21:33] <Bracki> Is there anytihng that shows connection attempts etc.?
[21:33] <sn9_> Le_Vert-Ntbk: you do know they were discontinued over a year ago, right?
[21:33] <Le_Vert-Ntbk> embedded ipsec hardware acceleration?
[21:33] <Le_Vert-Ntbk> sn9_: yeah maybe, I don't know
[21:33] <h3sp4wn> Le_Vert-Ntbk: Yep - it can also accelerate openssl (at least under bsd that driver can)
[21:34] <Le_Vert-Ntbk> but it seems to have 8mb flash + 32Mb ram
[21:34] <Le_Vert-Ntbk> usb2 port and a nice atheros wifi card
[21:34] <h3sp4wn> You need serial if you get one though
[21:34] <Le_Vert-Ntbk> why?
[21:34] <h3sp4wn> (randomly fails to flash often)
[21:34] <sn9_> Le_Vert-Ntbk: there are a couple of currently made things with 8/32
[21:35] <Le_Vert-Ntbk> h3sp4wn: does the pin are soldered on it?
[21:35] <h3sp4wn> Le_Vert-Ntbk: The headers already on
[21:35] <Le_Vert-Ntbk> okay
[21:35] <h3sp4wn> *header
[21:35] <Le_Vert-Ntbk> then I guess I still have some serial portwith maxx32
[21:35] <Le_Vert-Ntbk> i guess it's the right stuff, right?
[21:36] <sn9_> max3232
[21:36] <h3sp4wn> as long as its 3.3v or 5v it will be ok
[21:36] <Le_Vert-Ntbk> yeah it is :)
[21:36] <h3sp4wn> 12v isn't though (obviously)
[21:36] <sn9_> ok, build failed -- investigating
[21:36] <Le_Vert-Ntbk> 3.3 if I remember well
[21:37] <Le_Vert-Ntbk> I'll give a try and see if it's fine
[21:37] <Le_Vert-Ntbk> but when looking at the supported hardware table
[21:37] <Le_Vert-Ntbk> it seems the best hardware
[21:37] <Le_Vert-Ntbk> with some asus routers
[21:38] <h3sp4wn> There is other stuff but its not polished in the same way
[21:38] <sn9_> Le_Vert-Ntbk: are you planning on using white russian, or kamikaze with what you are gonna buy?
[21:38] <forum2006> sn9_, because i like to use telnet. don't start another useless discussion what's better and not. i'm really tired from this kind of discussions
[21:38] <Le_Vert-Ntbk> dunno
[21:38] <Le_Vert-Ntbk> for now I'm used to have WRAP
[21:39] <Le_Vert-Ntbk> running monowall or pfsense
[21:39] <Le_Vert-Ntbk> but it's a bit expensive for my needs
[21:39] <h3sp4wn> Le_Vert-Ntbk: Do you have the vpn accelerator for the wap ?
[21:39] <h3sp4wn> wrap ?
[21:39] <Le_Vert-Ntbk> no
[21:39] <Le_Vert-Ntbk> but it's fine
[21:39] <Le_Vert-Ntbk> it's a 266mhz geod proc
[21:39] <Le_Vert-Ntbk> not really powerfull, but enough for what i do
[21:40] <Bracki> i guess one of the iw* tools can help but i dont know which one...
[21:40] <Le_Vert-Ntbk> sn9_: why do you ask me that ?
[21:40] <Le_Vert-Ntbk> is it really important?
[21:40] <sn9_> forum2006: telnet's fine; the reason i asked was to evaluate whether your reason for a login passwd might apply to me, too
[21:41] <h3sp4wn> I don't bother enabling ssh until I am not going to touch it again for a long time
[21:41] <sn9_> Le_Vert-Ntbk: because the table only lists a couple of current 8/32 things that white russian supports
[21:42] <forum2006> sn9_, ok
[21:42] <Le_Vert-Ntbk> where did you see that?
[21:43] <sn9_> Le_Vert-Ntbk: asus wl-500gp and linksys wrtsl54gs
[21:43] <sn9_> maybe a third, but not for less money
[21:43] <nullboy> sn9_: hey, here's my serial cable setup: http://home.pacbell.net/morticus/serial-pl2303.jpg
[21:44] <Le_Vert-Ntbk> yeah but if you check this page: http://wiki.openwrt.org/OpenWrtDocs/Hardware/Netgear/WGT634U
[21:44] <Le_Vert-Ntbk> it seems 634 is supported too
[21:44] <sn9_> not in white russian
[21:44] <h3sp4wn> Le_Vert-Ntbk: supported by kamikaze (very well at the moment but it could break at anytime)
[21:44] <epa_> I'm about to upgrade to white russian
[21:44] <epa_> from a very old openwrt
[21:45] <Le_Vert-Ntbk> okay
[21:45] <Le_Vert-Ntbk> I'll see
[21:45] <Le_Vert-Ntbk> I'm not really new with gnu/linux systems
[21:45] <epa_> how can I see what version of openwrt I have now?
[21:45] <Le_Vert-Ntbk> so I should be able to keep it working ;)
[21:46] <epa_> at least "mtd" doesn't have -r option in usage()
[21:46] <h3sp4wn> Le_Vert-Ntbk: with serial its no problem (without you only get one chance)
[21:46] <sn9_> if you don't need the extra ethernet connectors and usb, http://meraki.net/products/mini/ looks good
[21:47] <nullboy> oh man the packaged suction cups sold me
[21:47] <nullboy> ;)
[21:47] <KragenSitaker> meraki looks awesome
[21:48] <Le_Vert-Ntbk> okay h3sp4wn, I'll check my serial console works fine before doing anything elese
[21:48] <Le_Vert-Ntbk> else
[21:48] <sn9_> nullboy: was that a cell phone cable before?
[21:48] <nullboy> sn9_: yeah
[21:48] Action: epa_ tried atftp but it didn't reflash the box
[21:48] <sn9_> which phone, and how much did the cable originally cost?
[21:48] <Bartman007> epa_: do you see any mention of the version when you connect via ssh? (in the banner)
[21:49] <nullboy> sn9_: i think this one was for kyocera (sp?) ~20$USD
[21:49] <Bartman007> epa_: use a tftp *client* not server, the bootloader has an elementary tftp server built-in
[21:49] <nullboy> actuallty no
[21:49] <nullboy> 9.99$usd
[21:49] <epa_> Bartman007: I used the reset button so only telnet works anymore
[21:49] <epa_> BusyBox v1.00 (2005.03.29-02:54+0000) Built-in shell (ash)
[21:49] <epa_> Bartman007: that is all I get
[21:50] <forum2006> wow. pretty old
[21:50] <epa_> yes
[21:50] <sn9_> the shrink tubing looks really fancy-shmancy compared to mine
[21:50] <nullboy> sn9_: hehe i just had to do it
[21:50] <epa_> worked fine until now
[21:50] <Bartman007> epa_: http://wiki.openwrt.org/Faq#head-f6622cc15ff6bb6aa500d793a1445cc504d07f1b
[21:50] <epa_> I installed some new packages and didn't work after that anymore
[21:50] <Bartman007> doh! nevermind, someone changed it.
[21:50] <wintix> epa_: never change a running system ;)
[21:50] <Bartman007> http://wiki.openwrt.org/OpenWrtDocs/About#head-cec173e34ef70145eeb5a5304d3db3381ac015df
[21:51] <epa_> wintix: true
[21:52] <sn9_> nullboy: i'm half-tempted to take a pic of my serial console just to show you
[21:52] <Le_Vert-Ntbk> so h3sp4wn, is this image fine http://downloads.openwrt.org/snapshots/brcm47xx-2.6/openwrt-wgt634u-2.6-squashfs.bin ?
[21:52] <epa_> white russian was just coming when I put this version in
[21:52] <epa_> maybe my best bet is to try the tftp install
[21:52] <nullboy> sn9_: i'll show you my port if you show me yours lol
[21:53] <Bracki> Ok. wl sta_info mac shows i'm AUTHENTICATED and ASSOCIATED still i dont get a dhcp address. nothing comes up in logread. what could be the reason?
[21:53] <epa_> If I'd know mtd works then I would use that
[21:54] <wintix> epa_: if you have boot_wait on then ther's no reason not to try, afaik.
[21:55] <epa_> I still seem to have to image (Mar 29 2005 openwrt-wrt54gs-squashfs.bin md5:04b2f95b2a9a221961538d577ab36d50) on the disk
[21:55] <sn9_> looks like a yacc file is broken in iproute2 in trunk
[21:55] <epa_> wintix: I just put it back to "on"
[21:55] Action: epa_ goes back to workbench
[21:57] <sn9_> emp_ematch.y:11: unrecognized: %error-verbose
[21:58] <sn9_> lo
[21:59] <Suschman> [florian]: im trying openwrt on edimax
[21:59] <Suschman> br6104kp has only 2mb of flash, so the build image is to big
[21:59] <sn9_> Suschman: kewl! i'm trying on airlink101
[21:59] <Suschman> how can i make it smaller, ie what can i left away?
[22:00] <Suschman> and, is your image alignment made for the original 32k big bootloader or the 64k enhanced one?
[22:00] <Suschman> missmadge here can destroy the loader with the csys header
[22:01] <Bartman007> Suschman: where are you getting an adm-5120 image from?
[22:02] <Suschman> the untested one openwrt builds right now
[22:02] <sn9_> isn't edimax rdc-2.6?
[22:02] <Suschman> no, adm 5120
[22:02] <Suschman> at least the 6140kp
[22:02] <Suschman> 6104
[22:02] <Bartman007> Suschman: I don't see any snapshots, so are you building the image yourself?
[22:03] <Suschman> yep, fresh from svn
[22:03] <Suschman> img is 3,7mb or so, wont fit into flash
[22:03] <sn9_> ah, i was thinking br6216mg
[22:03] <Bartman007> Suschman: keep in mind that OpenWrt doesn't support any 2MB flash devices
[22:04] <Suschman> no minimal builds? i thought there were atleast for whiterussian
[22:04] <Bartman007> certain devices can run OpenWrt in 2MB of flash, but they are not supported because there isn't enough space to do anything except for basic networking.
[22:04] <Suschman> i "can" upgrade the flash onboard, but this is no fun ;)
[22:04] <thepeople_work> you can make it fit in 2 meg you just need to start removing anything that is not needed
[22:04] <Bartman007> Suschman: you can compare the package list in the default/micro brcm images to get an idea of what you can strip out.
[22:05] <Suschman> kp has usb port, if the strange usb logic cell is once supportet fully storage would be less a problem
[22:05] <Suschman> Bartman007: thx for the tip
[22:05] <Bartman007> but you are largely on your own with any 2MB router, the devs consider them to be a waste of time.
[22:05] <Suschman> hmm
[22:06] <Suschman> florian at least builds the edimax image with csys headers, just to big :(
[22:06] <Bartman007> Suschman: ok, then grab your scalpel and start cutting :-)
[22:06] <Suschman> there is no root-on-nfs configuration out of the box, no?
[22:06] <Suschman> Bartman007: damn :)
[22:07] <Bartman007> Suschman: not out of the box, but you can configure it yourself.
[22:07] <Suschman> hmm, need to go deeper into buildroot then
[22:07] <Suschman> i will see
[22:08] <Bartman007> Suschman: if you've built an image and just want to do some quick tests you can modify the files in trunk/build_<arch>/root/ then generate a new image
[22:11] <Suschman> make image then?
[22:35] <kimosabe> does aosome one have the pinout for the wrt54g jtag ing
[22:38] <epa_> well tftp doesn't seem to work and box only seems to be able to boot up if I press "Reset" button for ~7sec when I plug in power
[22:38] <epa_> any other way to upgrade?
[22:38] <epa_> mtd should work, but I wonder what is the syntax for the older mtd
[22:38] <epa_> mtd [write|update] imagefile device
[22:39] <epa_> so mtd write openwrt-wrt54gs-squashfs.bin <device>
[22:48] <Dimitry|> mtd -r write openbla.trx linux
[22:48] <Dimitry|> epa_
[22:49] <Dimitry|> aber wennde sicher sein willst
[22:49] <Dimitry|> guck im wiki
[22:49] <Dimitry|> but if you wanna be sure...read the wiki
[22:49] <Dimitry|> and...mtd only works with a *.trx ni *.bin
[22:50] <epa_> Dimitry|: no -r option in my mtd
[22:50] <Dimitry|> yeah...read the wiki..... there you can also load a new mtd bin...
[22:50] <Dimitry|> which is able to upgrade your wrt
[22:51] <epa_> Dimitry|: yes I've been trying to find the page.....
[22:51] <Dimitry|> its in the wiki...how to install
[22:51] <Dimitry|> nahhh
[22:51] <Dimitry|> wait
[22:51] <Dimitry|> http://wiki.openwrt.org/OpenWrtDocs/Installing#head-7ba9a807eb37097e3a278612475bccfc64a987dd
[22:52] <Dimitry|> down there is a link "backup and restore"
[22:52] <Dimitry|> there you can find the new mtd
[22:52] <epa_> http://downloads.openwrt.org/people/wbx/mtd.static
[22:53] <Dimitry|> sounds good
[22:54] <nullboy> how can i get around this: http://pastebin.ca/index.php
[22:54] <nullboy> oops
[22:54] <nullboy> http://pastebin.ca/414074
[22:55] <nullboy> i don't need anything ppp related
[22:55] <Dimitry|> sweet
[22:55] <Dimitry|> delete the
[22:55] <Dimitry|> wait
[22:55] <Dimitry|> the files in the dir
[22:55] <Dimitry|> /usr/lib/ipkg/lists
[22:56] <Dimitry|> then you should have some space
[22:57] <nullboy> nothing in there
[22:58] <Dimitry|> then...
[22:58] <Dimitry|> flash a smaller firmware
[22:58] <nullboy> this fonera supposedly has 8mb flash though
[22:58] <Dimitry|> hm...my got 2mb
[22:58] <Dimitry|> so what
[22:59] <KragenSitaker> 2mb isn't much space
[22:59] <Dimitry|> you have to much things installed...
[22:59] <nullboy> Dimitry|: all i installed was hostapd and wpa-supplicant on to a default flash
[22:59] <Dimitry|> KragenSitaker, i got all i need.... pppoe aiccu ipv6 tc qos and openvpn
[22:59] <nullboy> that's too much?
[22:59] <Dimitry|> nullboy, no..there must be more...those apps dont waste 8bm flash
[23:00] <Dimitry|> KragenSitaker, and i still got 248kb :D
[23:01] <Bartman007> ameyer
[23:01] <Dimitry|> ?
[23:01] <nullboy> so how is one supposed to free up space if you can';t remove anything because it says there is no space left?
[23:02] <Dimitry|> i flashed the device with a smaller firmware...and then i cleared the /etc for unnessacry stuff
[23:03] <Dimitry|> and installed only what i really need
[23:12] <KragenSitaker> Dimitry|: awesome!
[23:13] <Dimitry|> what?
[23:13] <KragenSitaker> having so much space free
[23:13] <KragenSitaker> that's cool!
[23:13] <nullboy> okay i looked up the specs on this flash chip. it is 8meg so why do i only see 2.8MB in df?
[23:13] <Dimitry|> yeah...should i host your webpage there?
[23:13] <nullboy> how can i gain access to the rest of it?
[23:14] <Dimitry|> maybe....you have 2,8mb flash...and 8mb ram
[23:14] <nullboy> no the sd chip is 16
[23:14] <nullboy> i can confirm that
[23:14] <Dimitry|> ok
[23:14] <nullboy> dmesg even shows that correct
[23:15] <Dimitry|> i dont know....i only have my wrt...never see any other
[23:15] <nullboy> Dimitry|: oh you are speaking of a wrt
[23:15] <nullboy> i'm talking about a fonera
[23:15] <Dimitry|> after all...you install openwrt on it...
[23:17] <Dimitry|> didnt you?
[23:18] <nullboy> yeah
[23:18] <nullboy> so i should still have at least 4
[23:18] <nullboy> Dimitry|: any idea what this is about? : http://pastebin.ca/414135
[23:20] <h3sp4wn> nullboy: You might need to repartition it with redboot
[23:20] <h3sp4wn> maybe its not partitioned well
[23:20] <nullboy> h3sp4wn: any decent tut on that?
[23:20] <h3sp4wn> nullboy: The redboot manual
[23:20] <nullboy> k
[23:21] <nullboy> h3sp4wn: i can do it all from serial con right?
[23:22] <h3sp4wn> nullboy: yep - use fis list
[23:22] <h3sp4wn> ``fis list''
[23:22] <h3sp4wn> whatever you are using for the rootfs should be most of the space (the redboot manual is clear the tutorials have loads of hardcoded hex in that you don't need)
[23:23] <nullboy> h3sp4wn: this sounds fun
[23:23] <nullboy> anything i should specifically not screw with?
[23:25] <h3sp4wn> redboot, redboot config and fis
[23:25] <h3sp4wn> look at if it looks like its configured in a silly way first
[23:26] <h3sp4wn> Whatever redboot uses + 1Mb for the kernel + rest rootfs (thats what I used)
[23:26] <h3sp4wn> (but on a different device)
[23:27] <nullboy> i'll pastebin fis list
[23:29] <nullboy> http://pastebin.ca/414153
[23:29] <nullboy> i have no idea how to read fis list output
[23:30] <_trine> http://vbm.lan23.ru/wifi/fa20en.html
[23:31] <nullboy> and fis free shows: 0xA83D0000 .. 0xA87E0000
[23:35] <h3sp4wn> so there is free space
[23:35] <h3sp4wn> You should read the redboot docs (I don't know it well enough to give you advice - but it worked well enough for me to what I wanted at the weekend)
[23:36] <nullboy> h3sp4wn: do you have a link to the docs you read? i found the redboot manual but it's very generic
[23:36] <h3sp4wn> nullboy: I read the generic redboot manual
[23:36] <nullboy> http://ecos.sourceware.org/docs-latest/redboot/redboot-guide.html
[23:36] <nullboy> that one?
[23:36] <h3sp4wn> Yep
[23:36] <nullboy> ugh
[23:36] <nullboy> ok
[23:37] <nullboy> if i could read hex i think this wouldn't be so daunting
[23:47] <nullboy> does the open space for rootfs have to be contiguous?
[23:51] <Suschman> hmm
[23:57] <nullboy> when i use ipkg to remove a package, the output of df doesn't change
[00:00] --- Thu Mar 29 2007