[opensuse-edu] LIFE no login, no remote X but otherwise fine
Hi list and gurus - I'm new with this list and LI-F-E, but not new to LTSP and KIWI/LTSP. - over the last 7 days I've struggled to setup a plain vanilla KIWI/LTSP5 server - the problem being that ALL HP clients, but not any other type of client, causes a kernel panic at initrd stage. The network module in use is tg3. I've received lots of kind help from the people over at KIWI/LTSP. One of the suggestions (as we're all pretty desperate now) was to download and install LI-F-E. So done. This is now installed on a standard HP ProLiant serverbox (32bit). A part from a slight confusion on my part setting up the network - you use something called br (bridged) and you don't use eth0 directly - once I got that configured correctly, the server itself works fine. I browses the net and all. Then I run into problems. a) I enable 'remote access to X' in the sysconfig. I run SuSEconfig, switch down to runlevel 3 and back up to 5 again. No remote X. Nada. And I kill the firewall as well. I reboot. Nada. Eh...that's the first thing I don't understand, I give (on my laptop) X :1 -query <IP-of-server>. Any hints to what I'm doing wrong here? b) THIS IMPLEMENTATION OF LTSP BOOTS MY TROUBLED HP CLIENTS! I shout that out, because it's a major step forward :-) And it's fast. c) but alas, it will not let me login. I setup a virginal new user, type the username and password, it then takes a long time verifying and finally states that there is no contact to server. Restarts and over we go again... What could be that culprit here? The logs are empty. 2.6.31.12-0.1-default is the kernel version that came with the LI-F-E iso. All and any help is greatly appreciated! Thanks a lot. -- ------------------------------ Med venlig hilsen/Best regards Verner Kjærsgaard Novell Certified Linux Professional 10035701 Linux Counter no 114954 ------------------------------ -- To unsubscribe, e-mail: opensuse-edu+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-edu+help@opensuse.org
On Sun, Apr 25, 2010 at 1:43 AM, Verner Kjærsgaard <vk@os-academy.dk> wrote:
Hi list and gurus
- I'm new with this list and LI-F-E, but not new to LTSP and KIWI/LTSP. - over the last 7 days I've struggled to setup a plain vanilla KIWI/LTSP5 server - the problem being that ALL HP clients, but not any other type of client, causes a kernel panic at initrd stage. The network module in use is tg3.
I've received lots of kind help from the people over at KIWI/LTSP. One of the suggestions (as we're all pretty desperate now) was to download and install LI-F-E.
So done.
This is now installed on a standard HP ProLiant serverbox (32bit). A part from a slight confusion on my part setting up the network - you use something called br (bridged) and you don't use eth0 directly - once I got that configured correctly, the server itself works fine. I browses the net and all.
http://en.opensuse.org/LTSP/Configuration/Network
Then I run into problems.
a) I enable 'remote access to X' in the sysconfig. I run SuSEconfig, switch down to runlevel 3 and back up to 5 again. No remote X. Nada. And I kill the firewall as well. I reboot. Nada. Eh...that's the first thing I don't understand, I give (on my laptop) X :1 -query <IP-of-server>. Any hints to what I'm doing wrong here?
Don't know about that, but why do you want to enable remote access? LTSP5 uses ssh -X not XDMCP.
b) THIS IMPLEMENTATION OF LTSP BOOTS MY TROUBLED HP CLIENTS! I shout that out, because it's a major step forward :-) And it's fast.
That is a good news :)
c) but alas, it will not let me login. I setup a virginal new user, type the username and password, it then takes a long time verifying and finally states that there is no contact to server. Restarts and over we go again... What could be that culprit here? The logs are empty.
Provide needed info from here: http://en.opensuse.org/LTSP/Troubleshooting Now that you have same question on three different mailing list, it would be great if you can post on your threads elsewhere that the client now boots up using Li-f-e DVD so someone else running into the similar situation know what you did to get it working. It would be better to continue your thread on ltsp-discuss ML as your question is more LTSP related than Education. Ciao -J -- To unsubscribe, e-mail: opensuse-edu+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-edu+help@opensuse.org
Jigish Gohil skrev:
On Sun, Apr 25, 2010 at 1:43 AM, Verner Kjærsgaard <vk@os-academy.dk> wrote:
Hi list and gurus
It would be better to continue your thread on ltsp-discuss ML as your question is more LTSP related than Education.
Ciao
-J
Dear Sir, - thank you for your answer(s)! - I'll stick with ltsp-discuss as you say. - I must admit I feel a little embaressed about all this, in the past I've been able to get 20+ LTSP's (back from version 3 something) in the air, facing all sorts of problems. Only this one... - I was so disturbed last night that I thought today would be monday...I now realize that I've got one whole day more before deadline :-) The direct XDMCP connection now works(!) after this nights stand-still and this mornings reboot. I use the XDMCP way simply because I've only got one LCD 15" monitor that I would need to physically connect to the server if I want to watch it directly. ======== SOLVED!! ======== It now boots and runs fine, even with sound and local devices! The reason...when I installed and ran life/'kiwi-ltsp-setup -c', I noticed that the dhcp server wasn't starting, it was not assigned an interface to listen to. So I edited /etc/sysconfig/dhcpd and gave it the ANY interface to listen to, it was eth0. I then re-started the dhcpd server - I don't remember if I also ran 'kiwi-ltsp-setup -c', then it prompted me and I logged in just fine! Yesterday, I did the same thing - but I named the interface 'br0'. When one runs the 'kiwi-ltsp-setup -c', the firewall automatically gets setup and started, is the an easy way to avoid this? Thank You Houston, we're breathing again :-) -- ------------------------------ Med venlig hilsen/Best regards Verner Kjærsgaard Novell Certified Linux Professional 10035701 Linux Counter no 114954 ------------------------------ -- To unsubscribe, e-mail: opensuse-edu+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-edu+help@opensuse.org
Hi list and gurus :-) I'm on openSuSE11.2 with LIFE. On a brand new client (a UNO box, works just fine), I've connected this brand new widescreen LCD screen. Its resolution is something like 1680 x 900. When I boot up the TC as a standard PC with, say, Ubuntu or something similar, the screen is detected just fine. When I PXE boot with LIFE, the screen geometry is not correctly deteced and thus the screen ration is distorted. Where can I read about fixing this, a howto perhaps? Or - what can I do? I have edited lts.conf - the settings have no effect - the screen defaults back to 1280 x 1024. As always, thanks a LOT! -- ------------------------------------ Med venlig hilsen Verner Kjærsgaard -- To unsubscribe, e-mail: opensuse-edu+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-edu+help@opensuse.org
On Fri, Jan 21, 2011 at 7:33 PM, Verner Kjærsgaard <vk@os-academy.dk> wrote:
Hi list and gurus :-)
I'm on openSuSE11.2 with LIFE. On a brand new client (a UNO box, works just fine), I've connected this brand new widescreen LCD screen. Its resolution is something like 1680 x 900.
When I boot up the TC as a standard PC with, say, Ubuntu or something similar, the screen is detected just fine.
When I PXE boot with LIFE, the screen geometry is not correctly deteced and thus the screen ration is distorted.
Where can I read about fixing this, a howto perhaps? Or - what can I do?
Try gnome-display-properties after loging in. -- To unsubscribe, e-mail: opensuse-edu+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-edu+help@opensuse.org
Den 22-01-2011 05:39, Jigish Gohil skrev:
On Fri, Jan 21, 2011 at 7:33 PM, Verner Kjærsgaard <vk@os-academy.dk> wrote:
Hi list and gurus :-)
I'm on openSuSE11.2 with LIFE. On a brand new client (a UNO box, works just fine), I've connected this brand new widescreen LCD screen. Its resolution is something like 1680 x 900.
When I boot up the TC as a standard PC with, say, Ubuntu or something similar, the screen is detected just fine.
When I PXE boot with LIFE, the screen geometry is not correctly deteced and thus the screen ration is distorted.
Where can I read about fixing this, a howto perhaps? Or - what can I do?
Try gnome-display-properties after loging in.
- Thank you for your suggestion! - gee why didn't I think myself... - I'll report back! -- ------------------------------------ Med venlig hilsen Verner Kjærsgaard -- To unsubscribe, e-mail: opensuse-edu+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-edu+help@opensuse.org
participants (2)
-
Jigish Gohil -
Verner Kjærsgaard