[01:22] <ari_stress> morning all
[03:43] <ari_stress> i'm stuck with tftp being timeout
[03:43] <ari_stress> :(
[03:44] <ari_stress> i guess the NIC is the culprit
[04:05] <lns> ari_stress, i've had that
[04:05] <lns> what's the hardware?
[04:06] <ari_stress> lns: really?
[04:06] <ari_stress> it's on board rtl8139
[04:06] <lns> hmm
[04:06] <lns> those are usually pretty damn solid actually
[04:06] <ari_stress> let me get the wireshark result
[04:07] <lns> my issue was on a specific line of compaq ipaq workstations with buggy PXE revision
[04:07] <lns> and no updates since mid 90's.. heh
[04:08] <ari_stress> Ethernet II, Src: Micro-St_c6:35:95 (00:13:d3:c6:35:95), Dst: QuantaCo_28:15:65 (00:c0:9f:28:15:65)
[04:08] <ari_stress> did you find a workaround for it?
[04:08] <lns> no
[04:08] <lns> they got tossed
[04:08] <lns> unfortunately
[04:09] <lns> ari_stress, that doesn't really say much.. just the source/dest macs i believe
[04:09] <lns> do they match client and server? where is your dhcp server? are you sure you have correct parms for pxe?
[04:09] <ari_stress> i'm quite sure the dhcpd.conf is correct, because other client can boot into ltsp OK
[04:11] <ari_stress> the failed client symptoms are: seems like it doesn't recognize the 'next-server' parameter, because it looks for tftp server at 192.168.0.254 (my gateway), whereas it should be 192.168.0.237
[04:11] <ari_stress> then for testing, i change all 192.168.0.254 in dhcpd.conf to 192.168.0.237, so it then connect to 237
[04:11] <ari_stress> it requests for pxeclient.0, but still time out
[04:12] <lns> ahh i think i've had that before too
[04:12] <lns> what's the thin client?
[04:12] <ari_stress> what do you mean
[04:12] <lns> i got around that actually by specifying (in dhcp) a couple of other random similar parms like 'next-server' ... i think 'server-identifier' and another one
[04:13] <lns> is it an actual thin client or just a random computer with a rt8139
[04:13] <ari_stress> oh, just a regular desktop pc with onboard rtl8139
[04:13] <lns> for whatever reason the pxe stack (?) required some non-standard parms from dhcp to find the tftp server
[04:14] <ari_stress> oh no
[04:14] <ari_stress> can you share the parameter to me?
[04:14] <lns>  i think 'server-identifier' and another one
[04:14] <ari_stress> ok let me google it
[04:15] <lns> tftp-server-name
[04:15] <lns> was the other one
[04:15] <lns> is dhcp on your ltsp server?
[04:16] <lns> make sure you have correct 'filename', 'root-path' and 'next-server'
[04:16] <ari_stress> yes it;s on the same machine as ltsp
[04:16] <lns> k
[04:16] <ari_stress> let me experiment with it
[04:16] <lns> ok
[04:16] <lns> lemme know how it turns out
[04:17] <ari_stress> all of the above parameter is followed by ip address?
[04:18] <lns> no not all of them
[04:23] <lns> http://pastebot.ltsp.org/401
[04:23] <lns> look at that, that's my dhcp conf in ipcop
=== bddebian2 is now known as bddebian
[05:34] <ari_stress> lns: still not working
[05:55] <lns> you got me then
[06:09] <ari_stress> i suspect maybe the 'filename' parameter needs tobe modified, so i change it into various setting, still not working
=== RichEd-1 is now known as RichEd
[07:29] <ari_stress> root@ubuntu710:~# ltsp-update-image
[07:29] <ari_stress> Parallel mksquashfs: Using 1 processor
[07:29] <ari_stress> Creating little endian 3.0 filesystem on /opt/ltsp/images/i386.img.tmp, block size 65536.
[08:14] <neil_d> I am having trouble with edubuntu  I have just installed it the client boot untill the splash screen progress bar is about 3/4 done then stops can anyone help ?
[08:21] <HedgeMage> neil_d:  it helps if we can see the boot messages -- press Alt+some Fkey to see them -- I forget which one but trial and error is safe :)
[08:28] <neil_d> The client boot is stoping at "setup LSTP client"
[08:37] <riot_le> hi @all, anyone here experiences with Neoware Eon-Thinclients in combination with Edubuntu?
[08:47] <ari_stress> hi all, how do i add printer in client?
[08:47] <ari_stress> should i logon first as admin?
[09:45] <ari_stress> hi guys
[09:45] <ari_stress> i made it
[09:46] <ari_stress> printing in ltsp5 is a success
[09:46] <ari_stress> :D
[10:02] <neil_d> I have been having trouble getting my client to boot, I think I found the problem, in that the video hardware isn't detected correctly, how do I fix this ?
[10:10] <ari_stress> neil_d: u use ltsp5 from edubuntu?
[10:10] <neil_d> ari_stress, yes
[10:13] <ari_stress> i'm afrain i cannot help. i'm new. and from what i read in lts.conf, ltsp5 now shouldn't be configured in any way, it will detect all things
[10:13] <ari_stress> # Note that things like sound and local device support are
[10:13] <ari_stress> # auto-enabled if the corresponding packages are installed,
[10:13] <ari_stress> # there is no need to manually set these options anymore.
[10:13] <ari_stress> #
[10:13] <ari_stress> # **** THIS FILE SHOULD NO LONGER BE USED FROM HERE !!! ****
[10:13] <ari_stress> #
[10:13] <ari_stress> # With the introduction of the nbd/unionfs/squashfs structure
[10:13] <ari_stress> # the lts.conf file moved to the tftp root please create:
[10:13] <ari_stress> # /var/lib/tftpboot/ltsp/i386/lts.conf instead for your changes
[10:13] <ari_stress> #
[10:13] <ari_stress> # In case you want to use the lts.conf here, this still works,
[10:13] <ari_stress> # but you need to run ltsp-update-image after every change.
[10:13] <ari_stress> sorry for the paste
[10:14] <ari_stress> i've just found it after pulling out my hair setting up printing
[10:15] <neil_d> yes I saw this I have a lts.conf in /var/lib/tftpboot/ltsp/i386 and it seems to be parsed ok.
[10:23] <neil_d> how do I setup to which xorg.conf to use for a client ?
[11:07] <neil_d> what is meant to happen after "Starting LTSP client" ?
[11:07]  * neil_d that printed by the client startup.
[11:14] <neil_d> I think I have a OK version of the xorg.conf being used (at least I don't get a black screen now).  But it does nothing after printing "Starting LTSP client    [OK]" :(  what is meant to happen ? how do I fix this ?
[12:43] <Flosoft> hey
[12:43] <Flosoft> I have some questions about IPCop and PXE boots
[12:43] <Flosoft> I have a server which  runs Edubuntu with the possibility to boot PXE ... but I use IPCop as DHCP server
[12:43] <Flosoft> can I set up IPCop to use the Edubuntu server as host for the PXE boot image?
[12:47] <Bauer|> i have not tried myself, but may I suggest,,
[12:47] <Bauer|> filename "/ltsp/pxelinux.0"; and option root-path "/opt/ltsp/i386"; in dhcpd.conf
[12:48] <Bauer|> plus "next-server (ip-adress to edubuntu server)"
[12:49] <Flosoft> ok
[12:49] <Flosoft> next-server is not the DHCP host?
[12:49] <Flosoft> so IPCop in this case?
[12:49] <Bauer|> next-server name;   The hostname or address of the server from which the boot file is to be loaded.
[12:50] <Bauer|> you should put this on the dhcpd.conf on the dhcp-server
[12:50] <Bauer|> next-server should be pointing to where the boot image is, which probably would be edubuntu-server
[12:50] <Flosoft> but I disabled DHCP on the Edubuntu box
[12:51] <Bauer|> but you have a linux based dhcp-server? put it in the dhcpd.conf in your dhcp server
[12:51] <Flosoft> ok
[12:51] <Flosoft> but that one is IPCop
[12:51] <Flosoft> not the Edubuntu server with the image
[12:51] <Bauer|> but isn't IPcop linux based?
[12:52] <Flosoft> yes
[12:52] <Bauer|> the point with "next-server" is that it redirects to the server serving the boot image
[12:53] <Bauer|> so you should edit dhcpd.conf on IPCop, and make "next-server" pointing at your edubuntu-server
[12:53] <Bauer|> it's just a suggestion, not sure if it works
[12:54] <Bauer|> check out http://www.unix.org.ua/orelly/networking/tcpip/appd_03.htm as well
[12:55] <Bauer|> if you don't get my explanation, I will try to explain it better :p
[13:14] <Flosoft> ok
[13:14] <Flosoft> I get a TFTP server error
[13:14] <Flosoft> File Not Found
[13:16] <xyxvv> What have I done!? I installed the DebianEDU and DebianJr. packages on my Edubuintu desktop and now I \'m getting weird issues with updating the system, it even now identifies itself as Debian instead of Edubuntu 7.10!
[13:17] <xyxvv> sandy@sandy-desktop:~$ lsb_release -a
[13:17] <xyxvv> No LSB modules are available.
[13:17] <xyxvv> Distributor ID: Debian
[13:17] <xyxvv> Description:    DebianEdu/Skolelinux (terra)
[13:17] <xyxvv> Release:        3.2
[13:17] <xyxvv> Codename:       etch
[14:06] <bddebian> Heya
[14:36] <sbalneav> Morning all
[15:35] <RichEd> anyone here used kompozer - web page creator : http://kompozer.sourceforge.net/ - and have an opinion on it ?
[15:40] <sbalneav> RichEd: Haven't used that.  I've used the one that's got the blue fish for a symbol... what's it called...?
[15:41] <sbalneav> These days, if I need a web page, I tend to just use OO.o, and do a save as html :)
[15:44] <RichEd> sbalneav: not sure which one you mean ... kompozer just got a nice review from Chris Dawson at ZDnet with some good talkback comments
[15:45] <RichEd> I like him and his column ... he's a teacher / administrator, who write a column, and lurves Edubuntu LTSP :)
[15:45] <RichEd> http://education.zdnet.com/?p=1425
[15:45] <RichEd> * writes a regular column
[16:58] <Flosoft> hey again
[17:11] <sbalneav> Hello
[17:13] <johnny> hi
[17:13] <johnny> i got autologin working with francis` patch
[17:13] <johnny> learned package building, etc
[17:14] <johnny> odd problem tho
[17:14] <johnny> nobody seems to believe it
[17:14] <johnny> if i hve lts.conf in the chroot, autologin works, but if it's in the /var/lib/tftboot/ltsp/i386 it doesn't
[18:19] <me4u> anybody know anything about this "young" theme bug
[18:19] <me4u> can't seem to set it
[20:25] <musashi1> any thoughts on why print jobs will show up in the print manager window but not actually print? the printer is working and it will print a test page. just doesn't release jobs from clients.
[20:26] <musashi1> printing was working before
[20:28] <musashi1> okay, it finally printed. it sat there for a good 5 minutes before finally printing. not sure why.