I'm getting this error:
chroot to NEW_ROOT, delete all in /, move NEW_ROOT to /,
execute NEW_INIT. PID must be 1. NEW_ROOT must be a mountpoint.
-c DEV Reopen stdio to DEV after switch
Switch_root (1) used greatest stack depth: 5876 bytes left
Kernel panic - not syncing: Attempte
Another follow-up: I upgraded the server to 11.04 per the suggestion
of a tech from HP. To avoid hosing other working images, I built a
special image just for that machine. It boots now. Still tweaking
things, but it boots. I updated the NIC driver on the server, but I'm
not sure whether that
A follow up on this. I tried installing Ubuntu 10.04.2 directly on
the machine. It doesn't recognize the NIC (Intel 82579LM) -- doesn't
think there is a network device at all during the install. I'm
looking for options.
On Mon, Jul 11, 2011 at 6:02 PM, Lachele Foley (Lists)
wrote:
> Using 10.
Using 10.04.2 to PXE boot an HP Z210
Z210 product page:
http://h10010.www1.hp.com/wwpc/us/en/sm/WF06a/12454-12454-296719-307907-4270226-5053190.html
The proc is an Intel Xeon E3-1225
Other specs upon request (not sure what you need)
This happens with an amd64 client as well as a fat-amd64 c
hi,
On Mo, 2008-01-21 at 11:45 -0500, Andy Sargent wrote:
> Hello,
>
> I am playing around with LTSP to see if I can get it to work on a
> Jetway mini-ITX MoBo with a via chipset. I have an Elo serial touch
> screen attached. Everything looks good except during the kernel boot,
> I get an error
Hello,
I am playing around with LTSP to see if I can get it to work on a
Jetway mini-ITX MoBo with a via chipset. I have an Elo serial touch
screen attached. Everything looks good except during the kernel boot,
I get an error right after mounting /PROC that it can't auto detect
the NIC. It is a
-snip
eth0: setting full-duplex
input: ImPS/2 Logitech Wheel Mouse as /class/input/input1
ERROR! dhcpd failed!
Kernel panic - not syncing: Attempted to kill init!
-snip
i got this err msg when i run the LTSP 4.2.update2 thin client on old
fashion "Compaq Deskpro EN Series SFF Pentium II
Andy Trevor wrote:
> I have just had the same issue with this and HP5125 thins. I changed
> the kernel on load to one of the 2.6.16 ones and it all worked fine. I
> have not had time to dig around to find what the issue is with the
> 2.6.17 kernel and 5125s. Once I do I will post back.
>
> And
how do you do for compiled it ?
I ve the same pb
Le mercredi 23 août 2006 à 23:19 +0200, Nicolas CHEVE a écrit :
Le Mon, 21 Aug 2006 23:54:18 +0200
Nicolas CHEVE <[EMAIL PROTECTED]> a écrit:
>>
>>If existing LTSP 2.6.16 kernel exist, could someone give me an url ?
>>
>>If not, does it mea
Le Mon, 21 Aug 2006 23:54:18 +0200
Nicolas CHEVE <[EMAIL PROTECTED]> a écrit:
>>
>>If existing LTSP 2.6.16 kernel exist, could someone give me an url ?
>>
>>If not, does it mean that I do compile myself such kind of kernel ?
>>In these case, could someone give me help about compiling kernel for
>
On 8/21/06, CHEVE Nicolas <[EMAIL PROTECTED]> wrote:
> Quoting Andy Trevor <[EMAIL PROTECTED]>:
>
> > Dave Cotton wrote:
> >> If it's a recent version of dhcp you'll need a
> >>
> >> next-server 192.168.10.254;
> >>
> >> statement.
> >>
> > I have just had the same issue with this and HP5125 thins.
Le Mon, 21 Aug 2006 18:28:29 +0200
CHEVE Nicolas <[EMAIL PROTECTED]> a écrit:
>Quoting Andy Trevor <[EMAIL PROTECTED]>:
>
>> Dave Cotton wrote:
>>> If it's a recent version of dhcp you'll need a
>>>
>>> next-server 192.168.10.254;
>>>
>>> statement.
>>>
>> I have just had the same issue with this
Quoting Andy Trevor <[EMAIL PROTECTED]>:
> Dave Cotton wrote:
>> If it's a recent version of dhcp you'll need a
>>
>> next-server 192.168.10.254;
>>
>> statement.
>>
> I have just had the same issue with this and HP5125 thins. I changed
> the kernel on load to one of the 2.6.16 ones and it all wo
Dave Cotton wrote:
> If it's a recent version of dhcp you'll need a
>
> next-server 192.168.10.254;
>
> statement.
>
I have just had the same issue with this and HP5125 thins. I changed
the kernel on load to one of the 2.6.16 ones and it all worked fine. I
have not had time to dig around to f
If it's a recent version of dhcp you'll need a
next-server 192.168.10.254;
statement.
--
Dave Cotton <[EMAIL PROTECTED]>
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly
Hello,
Here is my dhcp.conf file :
http://www.rafb.net/paste/results/4yV1u958.html
When I start my terminal, he get an IP adress from the DHCP server, then
TFTP seem working succesfully and pxelinux is loaded.
Hope my dhcp.cof coul help
Thank's
Nicolas
Tom Barber a écrit :
>-BEGIN PG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Well at first glance your server isn't issuing your client PC with a IP
address. This will probably be a problem with your dhcp configuration,
either got an error in the file or its looking at the wrong network card
HTH
TOm
Nicolas CHEVE wrote:
> H
Hello,
I'm try to run an LTSP 4.2 server with an HP t5125 term.
The LTSP 4.2 update 3 is hosted on a Mandriva 2006 with all updates
installed.
After configuring the LTSP server, the client go througt the follonwing
steps :
- get DHCP conf
- get file thru TFTP
- boot
The
On Wednesday 10 May 2006 03:07, [EMAIL PROTECTED]
wrote:
> RATS!
> I was hoping to be able to pass it some option 129 line that would tell it
> which to use.
> They consistently use the same IRQ's. Any way to destinguish between them?
> I'd use a 3com that I have but, this thing only has 1 pci slo
t; <[EMAIL PROTECTED]>
05/09/2006 01:48 PM
Please respond to
[EMAIL PROTECTED]
To
"Brad C Delozier" <[EMAIL PROTECTED]>
cc
ltsp-discuss@lists.sourceforge.net
Subject
Re: [Ltsp-discuss] Kernel Panic Problem on Crusoe 5500 w/ 2xRTL8139
Brad,
I don't know what you can
Brad,
I don't know what you can do about that 2nd nic issue. It's hard to deal
with, if they are both the same.
As for your myth tv stuff, use google, and search for 'mythtv ltsp', you
should find lots of info about how to do what you are trying to do.
Jim.
On Tue, May 9, 2006 2:47 pm, Brad C
RATS!
I was hoping to be able to pass it some option 129 line that would tell it
which to use.
They consistently use the same IRQ's. Any way to destinguish between them?
I'd use a 3com that I have but, this thing only has 1 pci slot and no on
board video.
Any other suggestions there? I cannot di
Brad,
If you have 2 of the same nics in the client, that's probably going to
cause you massive grief.
You can use the 2nd card to do the initial boot, but once the kernel
starts running, then the /linuxrc script is going look at the PCI bus for
the network card, and use the first one it finds.
N
Hello, I'm having serious difficulties trying to get my crusoe 5500 (500MHz) working. Here is my config. 128mb ram, no hard drive, 2x RTL8139C network cards (one of which doesn't appear to be working). 1 Compact Flash Card (64MB) I'm only using the CF card because there is no network booting optio
Hello,
I'm having serious difficulties trying to get my crusoe 5500 (500MHz)
working. Its out of an FIC MAAT 1.2 server sold by Gallantry.com (they
went out of business and the red hat dist. software deactivated itself)
Here is my config.
128mb ram, no hard drive, 2x RTL8139C network cards (one
You can check ext3 or reiserFS in your Kernel.
Because Kernel unchecked filesystems option default.
--- Jesper Berth <[EMAIL PROTECTED]> wrote:
> Hi i need some help
>
> My klients get this error on boot
>
> crc error<6>Freeing initrd memory: 1012k freed
> VFS: Mounted root (ext2 filesystem).
>
Hi i need some help
My klients get this error on boot
crc error<6>Freeing initrd memory: 1012k freed
VFS: Mounted root (ext2 filesystem).
Mounted devfs on /dev
Freeing unused kernel memory: 88k freed
Kernel panic: No init found. Try passing init= option to kernel
Cheers Jesper
--
Jesper Berth <
Hi,
There is one client here, an old 486 DX2/100, that run well on a 10 MBit
LAN card but will crash after I swapped it with a 100 MBit one (RTL 8139).
The thing is that it starts normally, loads everything, does pivot root,
but one or two lines later, there is a screen full of error messages an
Am Freitag 06 August 2004 15:09 schrieb Ashraf:
> Are you booting over PXE or floppy
I am booting over floppy.
When the system is running i will by an networkcard with bootprom.
cu
--
Roland Kruggel mailto: [EMAIL PROTECTED]
System: Intel 3.2Ghz, Debian sid, 2.6.7, KDE 3.2.2
--
Are you booting over PXE or floppy
-Original message-
From: "Roland M. Kruggel" [EMAIL PROTECTED]
Date: Fri, 6 Aug 2004 12:47:28 +0300
To: [EMAIL PROTECTED]
Subject: Re: [Ltsp-discuss] Kernel Panic
> Am Dienstag 03 August 2004 19:57 schrieb Roland M. Kruggel:
> >
Am Dienstag 03 August 2004 19:57 schrieb Roland M. Kruggel:
> Hi Liste,
>
> I habe installed ltsp 4 on my server. The Kernel
> ltsp_kernel-3.0.15-i386.tgz
>
> The Installation is ok. (I hope so) The dhcp server runs fine.
>
> Whe I boot the Client i get a Kernel panic.
> Following the last lines fr
Am Dienstag 03 August 2004 20:34 schrieb [EMAIL PROTECTED]:
> Roland,
>
> the /linuxrc file is in the initrd, which gets downloaded with
> the kernel.
>
> my guess is you don't have enough ram in the workstation.
512 MB
cu
--
Roland Kruggel mailto: [EMAIL PROTECTED]
System: Intel 3.2Gh
Roland,
the /linuxrc file is in the initrd, which gets downloaded with the
kernel.
my guess is you don't have enough ram in the workstation.
Jim McQuillan
[EMAIL PROTECTED]
On Tue, 3 Aug 2004, Roland M. Kruggel wrote:
> Hi Liste,
>
> I habe installed ltsp 4 on my server. The Kernel
> ltsp
Hi Liste,
I habe installed ltsp 4 on my server. The Kernel
ltsp_kernel-3.0.15-i386.tgz
The Installation is ok. (I hope so) The dhcp server runs fine.
Whe I boot the Client i get a Kernel panic.
Following the last lines from the boot screen:
--snip
NET4: Protocols: ICMP, UDP, TCP
IP: routing
Am Montag, 22. März 2004 12:35 schrieb Andrew Langdon-Davies:
> Hello,
> A prospective client dies as described below.
>
> Setup:
> Server PII 266 512RAM Mandrake 9.2 LTSP-4 NIC:3c509
> Client 486DX2-S 66Mhz (But exactly the same happens with an AM486
> DX4-100 on the same board) 16RAM NIC:3c509.
Original Message
Subject: Re: [Ltsp-discuss] kernel panic
Timothy Legge wrote:
Server PII 266 512RAM Mandrake 9.2 LTSP-4 NIC:3c509
Client 486DX2-S 66Mhz (But exactly the same happens with an AM486
DX4-100 on the same board) 16RAM NIC:3c509. No HD)
Which version of etherboot
> Server PII 266 512RAM Mandrake 9.2 LTSP-4 NIC:3c509
> Client 486DX2-S 66Mhz (But exactly the same happens with an AM486
> DX4-100 on the same board) 16RAM NIC:3c509. No HD)
Which version of etherboot are you using and which ltsp kernel version?
-
Hello,
A prospective client dies as described below.
Setup:
Server PII 266 512RAM Mandrake 9.2 LTSP-4 NIC:3c509
Client 486DX2-S 66Mhz (But exactly the same happens with an AM486
DX4-100 on the same board) 16RAM NIC:3c509. No HD)
I have tried different RAM modules - no difference.
Checking for p
On Tue, 13 Jan 2004, Barbara Drake wrote:
> I've asked this question on the K12LTSP list and although everyone has been
> great, I'm still no closer to the solution, can someone out there help me:
>
> On Tue, 2004-01-13 at 03:01, Barbara Drake wrote:
> > Hi everyone, I am very new with Linux. I ha
Barbara-
Don't give up! The answer is Out There. First, can you get any Linux
kernel running on these machines? I would suggest downloading Knoppix
from http://www.knoppix.org and burning the ISO to a CD, and then boot
this from one or more of the machines. Even if you have to install a
CD-ROM
I've asked this question on the K12LTSP list and although everyone has been
great, I'm still no closer to the solution, can someone out there help me:
On Tue, 2004-01-13 at 03:01, Barbara Drake wrote:
> Hi everyone, I am very new with Linux. I have just set up my first LTSP
at
> an elementary sch
Hello peter,
Wednesday, December 25, 2002, 9:17:10 PM, you wrote:
pmws> Hi,
pmws> my diskless machine is a 386, ISA NE2000 clone, 3840 kB RAM.
pmws> The kernel image is downloaded, started and then it hangs on this line:
pmws> IP: routing cache hastable of 512 buckets, 4 KBytes
pmws> TCP: Has
Hi,
my diskless machine is a 386, ISA NE2000 clone, 3840 kB RAM.
The kernel image is downloaded, started and then it hangs on this line:
IP: routing cache hastable of 512 buckets, 4 KBytes
TCP: Hash tables configured (established 512 bind 512)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0
do you have this in your /etc/exports? (thats 2 lines)
/opt/ltsp/i386
192.168.0.0/255.255.255.0(ro,no_root_squash,sync)
/var/opt/ltsp/swapfiles
192.168.0.0/255.255.255.0(rw,no_root_squash,async)
--- Gerson Caicedo <[EMAIL PROTECTED]> wrote:
> I am having some problems getting a workstation to
>> Did you add the 'problem' workstation to your /etc/hosts file?
> No I did not, but neither did I add the first workstation
Check the docs for why host resolution is required:
http://www.ltsp.org/documentation/ltsp-3.0-4-en.html#AEN382
---
T
On Wed, 4 Dec 2002 14:56:15 -0500
"Gerson Caicedo" <[EMAIL PROTECTED]> wrote:
> I am having some problems getting a workstation to boot up; this
> workstation consists of a generic motherboard with an AMD K7 ATHLON
> 750MHz processor, 128mb of ram and a Linksys network card from
> Disklessworksta
I am having some
problems getting a workstation to boot up; this workstation consists of a
generic motherboard with an AMD K7 ATHLON 750MHz processor, 128mb of ram and a
Linksys network card from Disklessworkstations.com. When I turn the workstation
on it gets all the way through the boot
On Sat, 2002-09-28 at 11:49, Mike Eggleston wrote:
> The box is an old p150 with 64mb of core, one floppy, no dasd, 10/100 LNE100TX nic.
> I'm having a problem keeping this box running; it is one of my test boxes before I
> start a full rollout of ltsp.
>
> syslogd: syslogd: cannot write to remot
- Original Message -
From:
Mike
Eggleston
To: [EMAIL PROTECTED]
Sent: Saturday, September 28, 2002 10:49
AM
Subject: [Ltsp-discuss] kernel
panic
The box is an old p150 with 64mb of core, one
floppy, no dasd, 10/100 LNE100TX nic.
I'm hav
EMAIL PROTECTED]
Sent: Saturday, September 28, 2002 10:49
AM
Subject: [Ltsp-discuss] kernel
panic
The box is an old p150 with 64mb of core, one
floppy, no dasd, 10/100 LNE100TX nic.
I'm having a problem keeping this box running;
it is one of my test boxes before I
start a fu
The box is an old p150 with 64mb of core, one
floppy, no dasd, 10/100 LNE100TX nic.
I'm having a problem keeping this box running;
it is one of my test boxes before I
start a full rollout of ltsp.
syslogd: syslogd: cannot write to remote file
handle on192.168.5.254:514
bash-2.05# Unable to
Adriano,
Please send me your /etc/dhcpd.conf file and your /etc/exports
file. I'll take a look and see what could be causing that
problem.
Jim McQuillan
[EMAIL PROTECTED]
On Fri, 16 Aug 2002, Rhea - CPD - Adriano dos Santos Vieira wrote:
> Hi, people!
>
> We need your help now and fast (if
Hi, people!
We need your help now and fast (if possible),
please!
We are testing the LTSP and an error was
find.
That is it: Kernel panic: VFS: Unable to mount
root fs on 01:00
Our configuration for the first worksation that we
was installed:
Server:
Suse Linux 7.3 - Kernel 2.4.1
Tom,
which kernel are you using ?
we had a problem with 486's and the vmlinuz-2.4.9-ltsp-6 kernel.
You should be using the vmlinuz-2.4.18-ltsp-1 kernel that
is part of the ltsp_kernel-3.0.5 package.
Jim McQuillan
[EMAIL PROTECTED]
On Sat, 3 Aug 2002, Tom Manning wrote:
> Hi all,
>
> After
Hi all,
After many hours figuring this all out, I've got a 486 -100Mhz (16MB RAM) with
a boot floppy image from rom-o-matic trying to connect to my Mandrake-8.2
system. It detects the card, runs tft and downloads the kernel. The kernel
appears to go through the usual bootup stuff (detecting t
Ken,
the /opt/ltsp/i386 SHOULD be read-only. You certainly don't want any
of your workstations modifying anything in that directory.
Jim McQuillan
[EMAIL PROTECTED]
On 28 Jun 2002, Ken wrote:
> It turns out that it was the exports file. It had the LTSP directory as
> read only. I changed tha
I'm getting a kernel panic that says something about not being able to
mount "/opt/ltsp/... I can't remember the rest. Is there a log that LTSP
keeps of failed boot attempts that I can print and stick in here so you
can see exactly what error I get?
I'm using a different IP range since our networ
Am Freitag, 26. April 2002 16:47 schrieb Tobias Bandh:
> Hi,
>
> today I tried to add a new Client to my already working lts.
>
> Its a 486 DX 80 with 24 Mb Ram
> 3c509b ethernet card
> While booting it seems to work perfectly but at the end it gets stuck?
>
> Does anybody have an idea why???
Ye
Hi,
today I tried to add a new Client to my already working lts.
Its a 486 DX 80 with 24 Mb Ram
3c509b ethernet card
To avoid any questions here my dhcpd.conf
host terminal3{
filename "/lts/vmlinuz-2.4.9-ltsp-6";
hardware ehternet ...
Am Freitag, 19. April 2002 20:09 schrieb Jon Cushman:
> I am getting the same problem with a Compaq 486 using an ISA NE2000
> compatible NIC. The following is a portion of the message lines that
> proceeded the kernel panic stop message.
> ...
> mknbi-1.2-7/first32.c (GPL)
> Top of initrd is 21504
I am getting the same problem with a Compaq 486 using an ISA NE2000
compatible NIC. The following is a portion of the message lines that
proceeded the kernel panic stop message.
...
mknbi-1.2-7/first32.c (GPL)
Top of initrd is 21504k
Ramdisk at 0X01483000, size 0X0007D000
Uncompressing Linux... Ok
On Thu, 18 Apr 2002, Olav Øiehaug wrote:
> Same problem
> With me the message:
> initrd extends beyond end of memory -
> disabling initrd
>
> What do I do next?
I've just had one out of nine HP Vectras (P166's) do this to me. It had 80
megs of ram in it. I took out some (leaving 64 I thi
Måndag 15. april 2002 16:32 skreiv du:
> Sheilafel,
>
> If you are getting the 'VFS' panic, that probably indicates
> there was a problem with installing the initrd in memory.
>
> Press Shift-PageUp, and scroll back through the boot messages.
> Way up near the top, you should see where the memory
Sheilafel,
If you are getting the 'VFS' panic, that probably indicates
there was a problem with installing the initrd in memory.
Press Shift-PageUp, and scroll back through the boot messages.
Way up near the top, you should see where the memory map
is, and you might see some messages about the i
i've been getting the following message when trying to boot my diskless workstation
running on pentium 1 at 133 mhz...
VFS: Cannot openroot device "ram0" or 01:00
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 01:00
Sandro!
i've tried checking dhcpd.co
we encountered the same problems as the posted "KERNEL PANIC". we need help! our
workstations are running on pentium 1 133mhz. thanks a lot!
See Dave Matthews Band live or win a signed guitar
http://r.lycos.com/r/bmgfly_mail_dmb/http://win.ipromotions.com/lycos_020201/splash.asp
yes, 486 ...
On Tue, 9 Apr 2002 [EMAIL PROTECTED] wrote:
> Kaspar,
>
> Please tell us more about your workstation hardware.
> Is it a 486 ?
>
> Jim McQuillan
> [EMAIL PROTECTED]
>
>
>
> On Tue, 9 Apr 2002, Kaspar Rammo wrote:
>
> >
> > hi!
> > my discless workstation kernel tells me at booting:
hi!
my discless workstation kernel tells me at booting:
VFS: Cannot openroot device "ram0" or 01:00
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 01:00
can anybody help me??
thanks ...
kaspar
__
Help !
We have an ASUS TUSI-M motherboard with a SiS900 Network Interface.
We are using PXE to load Etherboot to load the ltsp3.0 supplied kermel.
After the usual hastles with DHCP etc, we have PXE running and loading
Etherboot. They are both finding and driving the SiS900 OK.
They report its M
client. If you only have one card then try changing the network
card. (just for testing.)
Asbjørn Morell
mailto:[EMAIL PROTECTED]
-Oprindelig meddelelse-
Fra: lee kh [mailto:[EMAIL PROTECTED]]
Sendt: 14. december 2001 14:20
Til: [EMAIL PROTECTED]
Emne: [Ltsp-discuss] kernel panic
i use ltsp 3.0 and the workstation used the
vmlinuz-2.4.9-ltsp-5.
But after pivoting root it show up
[kernel panic : attempted to kill init!] .
And workstation hang!
Any idea about this?
Help!PLS
Thanks!
__
Do You Yahoo!?
Check out Yahoo! Shoppi
Jim,
I am using a standard redhat 6.2 system. The only
think i did was to upgrade the kernel to 2.2.19* .
chetan.
--- Jim McQuillan <[EMAIL PROTECTED]> wrote:
> Chetan,
>
> Did you build your own kernel ?
>
> Looks like you've got support for raid built into
> the kernel.
>
> I'm wonderin
ng to be missing something possibly
support for NFS as Root
Good luck.
Matt
-Original Message-
From: Chetan Ganpati [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 24, 2001 11:44 PM
To: [EMAIL PROTECTED]
Subject:[Ltsp-discuss] Kernel Panic Error
Hi ,
Thanks to
Chetan,
Did you build your own kernel ?
Looks like you've got support for raid built into the kernel.
I'm wondering what else you've included, or excluded.
Jim McQuillan
[EMAIL PROTECTED]
Chetan Ganpati wrote:
>
>Hi ,
>Thanks to Matt Egan for the tip .
>Making a different floppy did hel
Hi ,
Thanks to Matt Egan for the tip .
Making a different floppy did help but now when I boot
up the client I get this error.
"VFS: Mounted root(ext2 filesystem)
Loading sis900 module
/lib/sis900.o: init_module: Device or resource busy
autodetecting RAID arrays
autorun ...
... autorun DONE
k
Hi ,
Thanks to Matt Egan for that tip .
Making a different floppy did help but now when I boot
up the client I get this error.
kmod: failed to exec /sbin/modprobe -s -k
block-major-3, errno =2
VFS: Cannot open root device 03:07
Kernel panic: VFS: Unable to mount root fs on 03:07
What could be w
76 matches
Mail list logo
