00:09 | <cellofellow> ok, got another problem with another client. I'm using fat clients for a Cinelerra just so you know. This client boots fine but Cinelerra doesn't run because I have the SSE3 version installed in my chroot but this particular box doesn't support SSE3 so it just crashes. I need to clone this chroot and make another with the non-SSE3 Cinelerra installed. I can do that easily, but how do I tell this particular box (by MAC address) to load the
| |
00:12 | hello?
| |
00:19 | alkisg has joined #ltsp | |
00:19 | shogunx has joined #ltsp | |
00:23 | <alkisg> cellofellow: you can pass a different nbdroot (port) in pxelinux/mac-address
| |
00:24 | About the kernel panic, what's the last error messages before and at the panic?
| |
00:25 | More info about pxelinux.cfg/mac-address: https://help.ubuntu.com/community/UbuntuLTSP/StaticIPsWithDHCP
| |
00:26 | rpm_: when you get that nbd error, do you get a busybox (initramfs) shell?
| |
00:38 | <cellofellow> I can't see what the error is in the kernel panic because it occurs right after the kernel switches to full-resolution graphics, and all I see is a black smear. I added break=premount which stops the kernel panic (no blinking caps lock) but it looks precisely the same.
| |
00:38 | If I leave quiet splash on the kopts line then Plymouth loads for a second then the kernel panic.
| |
00:39 | I need to find a way to disable the graphics stuff so I can see the kernel error. nomodeset on the kernel opts line hasn't done the trick.
| |
00:40 | alkisg: wait, how did you see my questions if you weren't in the channel?
| |
00:40 | <alkisg> Logs :) See the topic
| |
00:41 | SCREEN_07=shell should prevent X from starting
| |
00:41 | Try also XSERVER=vesa, maybe it helps
| |
00:42 | <cellofellow> heh, not using X at all.
| |
00:42 | <alkisg> "the kernel switches to full-resolution graphics" ==> so how it's switching to graphics?
| |
00:42 | svgalib?
| |
00:43 | <cellofellow> kms I think. Whatever it does, it switches from the 80-column plain text display to a native-resolution framebuffer that plymouth normally uses. But it's just black, I can't see the output from the kernel or the initramfs shell.
| |
00:43 | the initramfs shell works, I know. With break=premount I can then type "poweroff" and it shuts down.
| |
00:43 | but I can't see anything, I'm blind.
| |
00:44 | <alkisg> What graphics card?
| |
00:45 | <cellofellow> nvidia something. I could boot the installed Win7 and have a look.
| |
00:45 | <alkisg> No need you can do that from SCREEN_07=shell
| |
00:45 | Remove quiet splash and put nomodeset though
| |
00:46 | <cellofellow> already did that
| |
00:46 | <alkisg> You tried SCREEN_02=shell and it didn't work?
| |
00:46 | *07
| |
00:48 | <cellofellow> ok, let me start over. It kernel panics just about when it's attempting to mount the root image. Just before it does this, the kernel graphics driver (probably nvidiafb) activates and sets the resolution to the native resolution. This is fine when using Plymouth but for some reason using a plain text console it's just black. When it's just black, I can't see the kernel panic message, nor when using break=premount can I see the initramfs p
| |
00:49 | My SCREEN setup is SCREEN_02=shell, SCREEN_03=ldm, SCREEN_04=cinelerra (custom script that launches Cinelerra farm client.)
| |
00:49 | X does not start unless I manually switch to VT3.
| |
00:50 | What the monkey? According to the Windows Device Manager there are two video cards, an Intel and an Nvidia.
| |
00:52 | when the initramfs prompt comes up, what do I run to continue the boot?
| |
00:52 | even though I can't see it I can still type it.
| |
00:52 | <alkisg> Ctrl+d
| |
00:52 | (or exit[enter])
| |
00:52 | <cellofellow> ok
| |
00:52 | <alkisg> You can also try 'break=init', that's the last stage of the initramfs
| |
00:53 | <johnny> it shouldn't be using nvidiafb should it? does that even work?
| |
00:53 | cellofellow, it's supposed to be using the nouveau kms driver
| |
00:53 | oh yyour distro...
| |
00:53 | <alkisg> Also try connecting the vga cable to the other card. And, on another try, try disabling the internal card from the bios.
| |
00:53 | * johnny is really used to using fedora 13 :) | |
00:54 | <cellofellow> eh, whatever. Adding vga=771 to the kopts worked
| |
00:54 | <johnny> nouveau kms comes with it
| |
00:54 | cellofellow, hopefully in the next ubuntu you can rely on nouveau kms
| |
00:54 | <cellofellow> not sure if ubuntu uses nvidiafb or nouveau kms.
| |
00:54 | <johnny> neither
| |
00:54 | <alkisg> johnny: 10.04 does have nouveau kms
| |
00:54 | <johnny> nvidiafb can't coexist with nvidia-drivers
| |
00:54 | alkisg, oh.. neat
| |
00:54 | and neither can nouveau kms :)
| |
00:54 | <cellofellow> I think it disables the kernel driver if the non-free X driver is enabled.
| |
00:55 | part of jockey
| |
00:55 | <johnny> ah yes, that is true.. distro specific mechanisms
| |
00:55 | <alkisg> cellofellow: so with just vga=771 it got to booting X etc?
| |
00:55 | <cellofellow> anyway, vga=771 on the kernel opts line removed the blindfold.
| |
00:55 | <johnny> cellofellow, then it would be using the standard vesafb or some userspace fb driver
| |
00:55 | <cellofellow> no, no booting X. I got the initramfs prompt, typed exit and I got the kernel panic message.
| |
00:55 | <alkisg> Ah, k
| |
00:55 | What does it say?
| |
00:56 | <johnny> well you could be a kernel panic right?
| |
00:56 | coudn't run init
| |
00:56 | <cellofellow> said Kernel panic - not syncing: Attempted to kill init!
| |
00:56 | <alkisg> And before that?
| |
00:56 | <johnny> ah yes.. attempted to kill init
| |
00:56 | cellofellow, i don't think tha'ts necessarily abnormal
| |
00:56 | <alkisg> Any hints about no suitable network modules present?
| |
00:56 | <cellofellow> Pid: 1, comm: init Tainted: G W 2.6.32-24-generic #41-Ubuntu
| |
00:56 | yes
| |
00:57 | <johnny> well there ya go..
| |
00:57 | <cellofellow> no such device eth0
| |
00:57 | so, what now?
| |
00:57 | <alkisg> Which network card?
| |
00:57 | <johnny> lspci
| |
00:57 | if ubuntu's busybox ships with it...
| |
00:57 | <alkisg> lspci isn't there at that point...
| |
00:57 | <johnny> alkisg, it could be. if you compiled busybox with it
| |
00:57 | <alkisg> johnny: well, ubuntu doesn't, so it isn't there :)
| |
00:57 | <cellofellow> dunno precisely, a jmc250 I think.
| |
00:58 | <johnny> alkisg, i can tell
| |
00:58 | cellofellow, can you boot a livecd or something?
| |
00:58 | or liveusb..
| |
00:58 | <cellofellow> don't have one handy
| |
00:58 | <johnny> get one?
| |
00:58 | <cellofellow> I could run and get one, I guess.
| |
00:58 | <alkisg> Boot into windows and check the pciid
| |
00:58 | (on the device manager)
| |
00:58 | <johnny> cellofellow, or you could use ubuntu wubi..
| |
00:58 | <cellofellow> meh
| |
00:59 | <johnny> uggh.. that sucks alkisg :(
| |
00:59 | <cellofellow> no lspci in ubuntu's iinitramfs
| |
00:59 | <johnny> cellofellow, yeah, you have to compile busybox with support for it, and they didn't
| |
00:59 | ps.. busybox is amazing
| |
00:59 | :)
| |
00:59 | <cellofellow> ifconfig -a just shows lo
| |
00:59 | my first exposure to Linux was with DSL which uses BusyBox.
| |
00:59 | <johnny> cellofellow, that's normal if you have no network module
| |
01:00 | you might have to rebuild your initramfs in the chroot
| |
01:00 | <cellofellow> Funny thing with the BusyBox-based Linux distros is that RMS can't insist they be called GNU/Linux.
| |
01:00 | ok, I go get my LiveUSB.
| |
01:00 | brb
| |
01:00 | <johnny> cellofellow, well alkisg suggested devicemanager
| |
01:00 | <alkisg> cellofellow: didn't you say you have windows?
| |
01:01 | Right, you can just look the pci id there
| |
01:01 | <cellofellow> it's a jmc250
| |
01:01 | <alkisg> No, not the name. The pci id
| |
01:01 | <cellofellow> I'll get the PCI ID
| |
01:01 | <alkisg> 1234:5678
| |
01:01 | <johnny> alkisg, searching for jmc250 in google might give you that tho
| |
01:01 | <cellofellow> i think it's so odd that syslinux/pxelinux works with the card but then linux doesn't know what to do with it.
| |
01:02 | <johnny> yeah, i remember thinking that ..
| |
01:02 | but they can rely on the onboard hardware directly
| |
01:03 | i think neboot in linux might have been designed a bit differently if pxe was built into all chipsets
| |
01:03 | <alkisg> The card rom is providing the pxe stack
| |
01:03 | It's very slow though, so a normal driver is used later on
| |
01:04 | <johnny> hmm, didn't know anything about the speed
| |
01:04 | that's an interesting fact
| |
01:05 | <alkisg> http://manpages.ubuntu.com/manpages/lucid/man4/jme.4freebsd.html
| |
01:05 | <cellofellow> where do I find the PCI-ID in Winblows Device Manager?
| |
01:06 | <alkisg> cellofellow: also check the link above, it says something about `if_jme_load="YES"`
| |
01:07 | <cellofellow> ok, I'll try that
| |
01:07 | <alkisg> The pci id is when you right click on the card, select properties, there's a combo box there
| |
01:07 | One of the values is the pci id
| |
01:08 | /lib/modules/2.6.32-24-generic-pae/kernel/drivers/net/jme.ko
| |
01:09 | Also check if that jme.ko is present in the initramfs, if it isn't you'd need to add the module to the initramfs
| |
01:09 | https://help.ubuntu.com/community/UbuntuLTSP/AddingModules
| |
01:09 | <cellofellow> it's in there, but how do I tell if it's in the initramfs?
| |
01:10 | <alkisg> Search for the name while booting the client with break=init
| |
01:10 | Or you can gunzip the initramfs...
| |
01:11 | <cellofellow> while in the chroot grep jme /etc/initramfs-tools/modules turns up blank
| |
01:11 | <alkisg> OK then follow that wiki page above
| |
01:12 | <cellofellow> already echoed it in there
| |
01:13 | that worked! thanks a whole big bunch alkisg
| |
01:13 | oh, and johnny. You helped too. :)
| |
01:13 | <alkisg> You're welcome :)
| |
01:22 | <cellofellow> now I can get some real work done: rendering a boatload of videos
| |
01:28 | alkisg has quit IRC | |
01:30 | alkisg has joined #ltsp | |
01:47 | alkisg has quit IRC | |
02:23 | vmlintu has joined #ltsp | |
02:31 | sweetpi has quit IRC | |
03:22 | lasersoft has joined #ltsp | |
03:27 | alkisg has joined #ltsp | |
03:28 | johnny has left #ltsp | |
03:31 | alkisg1 has joined #ltsp | |
03:33 | alkisg has quit IRC | |
03:41 | alkisg has joined #ltsp | |
03:43 | alkisg1 has quit IRC | |
03:58 | hiltunen has joined #ltsp | |
04:02 | alkisg has quit IRC | |
04:05 | alkisg has joined #ltsp | |
04:09 | alkisg has quit IRC | |
04:28 | shogunx has quit IRC | |
04:43 | alkisg has joined #ltsp | |
04:47 | Selveste1___ has quit IRC | |
04:50 | Selveste1 has joined #ltsp | |
05:55 | pmatulis has joined #ltsp | |
05:55 | alkisg has quit IRC | |
06:10 | alkisg has joined #ltsp | |
06:10 | shogunx has joined #ltsp | |
06:12 | BWMerlin has quit IRC | |
06:54 | Selveste1 has quit IRC | |
06:58 | BWMerlin has joined #ltsp | |
07:01 | alkisg has quit IRC | |
07:19 | puck1 has joined #ltsp | |
07:22 | <puck1> I need some help moving to a separate DHCP server. LTSP works fine as a standalone but when I stop the DHCP server on the LTSP server and then using the same dhcpd.conf file run a DHCP server on a box without LTSP I get a TFTP timeout message. The client is getting a correct address and the next-server option is set correctly. Where do I look?
| |
07:40 | BWMerlin has quit IRC | |
07:44 | alkisg has joined #ltsp | |
07:50 | bobby_C has joined #ltsp | |
08:24 | GodFather has joined #ltsp | |
08:25 | moose-tek has quit IRC | |
08:26 | moose-tek has joined #ltsp | |
09:06 | moose-tek has quit IRC | |
09:07 | moose-tek has joined #ltsp | |
09:45 | alkisg has joined #ltsp | |
09:48 | bobby_C has quit IRC | |
09:59 | bobby_C has joined #ltsp | |
10:00 | <lasersoft> Out of curiosity, I have a LTSP desktop working normally most of the time. When I connect the terminals directly to the switch they are not receiving dhcp, when connected through a hub they work fine. On these same terminals, I get a kernel panic and hang on boot. With a different netcard (realtek) they work fine. Kernel 2.6.32-24, On board netcard Attansic Technology Corp. atl2.ko.
| |
10:00 | begin: run /script/init-premount...
| |
10:00 | no interfaces found! Aborting...
| |
10:11 | <puck1> Bump... I need some help moving to a separate DHCP server. LTSP works fine as a standalone but when I stop the DHCP server on the LTSP server and then using the same dhcpd.conf file run a DHCP server on a box without LTSP I get a TFTP timeout message. The client is getting a correct address and the next-server option is set correctly. Where do I look?
| |
10:12 | Is DHCP doing anything to allow the TFTP connection?
| |
10:29 | <alkisg> lasersoft: you probably need to add the module to the initramfs. For ubuntu, instructions here: https://help.ubuntu.com/community/UbuntuLTSP/AddingModules
| |
10:30 | puck1: the dhcp "next-server" option should point to the ltsp server for the kernel to be downloaded via tftp
| |
10:47 | bobby_C has quit IRC | |
10:48 | jhutchins_lt has joined #ltsp | |
10:58 | <puck1> alkisg: That is what I want to happen but I just get TFTP timeout if I stop the DHCP server on the LTSP server.
| |
10:58 | <alkisg> puck1: so you do have next-server==the ltsp server IP?
| |
10:59 | (on the other dhcp server of course)
| |
10:59 | <puck1> Here is the 192.168.0.201 dhcp server conf
| |
10:59 | authoritative;
| |
10:59 | option domain-name "glenstorm.oisankara.org";
| |
10:59 | option domain-name-servers 192.168.0.252;
| |
10:59 | option broadcast-address 192.168.0.255;
| |
10:59 | option routers 192.168.0.252;
| |
10:59 | next-server 192.168.0.205;
| |
10:59 | option subnet-mask 255.255.255.0;
| |
10:59 | option root-path "/opt/ltsp/i386";
| |
10:59 | if substring( option vendor-class-identifier, 0, 9 ) = "PXEClient" {
| |
10:59 | filename "/ltsp/i386/pxelinux.0";
| |
10:59 | } else {
| |
10:59 | filename "/ltsp/i386/nbi.img";
| |
10:59 | }
| |
10:59 | <alkisg> !pastebot
| |
11:00 | <ltspbot> alkisg: "pastebot" :: The LTSP pastebot is at http://ltsp.pastebin.com. Please paste all text longer than a line or two to the pastebot, as it helps to reduce traffic in the channel. Don't forget to paste the URL of the text here.
| |
11:00 | <alkisg> Please use the pastebot for pasting files
| |
11:01 | If you run this command on the ltsp server, what do you get? sudo /usr/lib/klibc/bin/ipconfig -n eth0
| |
11:01 | <puck1> wasn't thinking
| |
11:03 | IP-Config: eth0 hardware address 00:0a:cd:19:d5:6f mtu 1500 DHCP RARP ... but it doesn't return to a prompt
| |
11:03 | <alkisg> OK, ctrl+c it
| |
11:03 | <puck1> had already.
| |
11:04 | <alkisg> That means that it doesn't get an offer from the new dhcp server
| |
11:04 | <puck1> I am trying to consolidate my various LTSP servers without going to ltsp cluster.
| |
11:04 | I don't understand, The LTSP server has a static address why does it need DHCP
| |
11:05 | <alkisg> Just as a test, to check if your dhcp server is working properly
| |
11:05 | That would also return the filename, next-server etc info (without changing the ip address, it's just a test)
| |
11:05 | puck1: do you see any tftp requests on /var/log/daemon.log?
| |
11:07 | <puck1> the TC gets address 192.168.0.20 from 192.168.0.201 but the TFTP server times out
| |
11:11 | <alkisg> So no tftp requests in the log file? Then it may be getting the wrong address.
| |
11:11 | If it's an option, boot with gpxe, it explicitly lists everything it gets from dhcp
| |
11:12 | <puck1> I don't see anything in the log. What is GPXE?
| |
11:12 | <alkisg> To check your tftp server, you get try `tftp server; get /ltsp/i386/lts.conf` from some pc on your network.
| |
11:12 | !gpxe
| |
11:12 | <ltspbot> alkisg: "gpxe" :: the successor to etherboot (http://etherboot.org). To download bootable floppy, cd, usb, kernel etc images, visit http://rom-o-matic.net/
| |
11:16 | <puck1> the tftp server is responding correctly. I'll try the gpxe boot. Should this give all the dhcp details?
| |
11:17 | I am using the same dhcp conf file on both boxes. Is there something specific I need to do on a dhcp box without ltsp?
| |
11:20 | <alkisg> If you boot from gpxe, and press ctrl+b to get a command line, and run: dhcp net0, and then: config, you'll see all the dhcp details there
| |
11:20 | And you can also try downloading from tftp from the command line there
| |
11:20 | No, there's nothing special to do on a dhcp box without ltsp, except of course of correctly setting the next-server
| |
11:20 | Are you sure you don't have _another_ dhcp server (a 3rd one) around? E.g. a router?
| |
11:29 | <puck1> No I can change the dhcp conf and the ip address changes correctly. I'll try the gpxe
| |
11:30 | <lasersoft> alkisg: thanks for the link, I have been looking for that
| |
11:46 | jhutchins has quit IRC | |
11:46 | jhutchins has joined #ltsp | |
11:51 | jhutchins has quit IRC | |
12:50 | moose-tek has quit IRC | |
12:52 | moose-tek has joined #ltsp | |
12:56 | johnny has joined #ltsp | |
13:02 | jhutchins has joined #ltsp | |
13:02 | jhutchins has quit IRC | |
13:06 | jhutchins has joined #ltsp | |
13:40 | puck1 has left #ltsp | |
13:53 | slidesinger has joined #ltsp | |
13:55 | lasersoft has left #ltsp | |
13:57 | cellofellow has quit IRC | |
14:01 | Guerdal82 has quit IRC | |
14:38 | Ghidorah has quit IRC | |
14:59 | jhutchins_lt has quit IRC | |
15:16 | alkisg has quit IRC | |
15:25 | alkisg has joined #ltsp | |
15:28 | vagrantc has joined #ltsp | |
15:34 | Selveste1 has joined #ltsp | |
15:39 | Selveste1_ has joined #ltsp | |
15:39 | Selveste1 has quit IRC | |
15:47 | Selveste1_ has quit IRC | |
15:56 | alkisg has quit IRC | |
15:57 | alkisg has joined #ltsp | |
16:07 | Guerdal82 has joined #ltsp | |
16:40 | rpm_ has quit IRC | |
16:46 | irule has joined #ltsp | |
16:51 | irule has quit IRC | |
17:09 | avena has joined #ltsp | |
17:15 | alkisg has quit IRC | |
17:17 | avena has quit IRC | |
18:01 | GodFather has quit IRC | |
18:10 | moose-tek has quit IRC | |
18:10 | moose-tek has joined #ltsp | |
18:52 | chupacabra has quit IRC | |
19:07 | Selveste1_ has joined #ltsp | |
19:23 | sweetpi has joined #ltsp | |
19:28 | jhutchins_lt has joined #ltsp | |
19:43 | Selveste1_ has quit IRC | |
19:46 | ogra_cmpc has quit IRC | |
19:58 | ogra_cmpc has joined #ltsp | |
20:03 | Guerdal82 has quit IRC | |
20:19 | hawkI_ has quit IRC | |
20:22 | jhutchins_lt has quit IRC | |
21:13 | Selveste1 has joined #ltsp | |
21:16 | sweetpi has quit IRC | |
21:35 | slidesinger has quit IRC | |
21:45 | F-GT has quit IRC | |
21:54 | vagrantc has quit IRC | |
21:59 | vagrantc has joined #ltsp | |
22:00 | moose-tek has quit IRC | |
22:00 | moose-tek has joined #ltsp | |
22:02 | vagrantc has quit IRC | |
22:02 | F-GT has joined #ltsp | |
22:07 | Selveste1 has quit IRC | |
22:09 | Guerdal82 has joined #ltsp | |
22:13 | vvinet has quit IRC | |
22:55 | moose-tek has quit IRC | |
22:56 | moose-tek has joined #ltsp | |
23:17 | vvinet has joined #ltsp | |
23:27 | vvinet has quit IRC | |
23:28 | vvinet has joined #ltsp | |
23:51 | rjune has quit IRC | |
23:54 | sweetpi has joined #ltsp | |