Hi,
I've launched thinclients on Skole, I have splashy and as usual it crached
at one moment, but then I don't have verbose and if I wait I have this
message :
[215.042458] Kernel panic - not syncing : Attempt to kill init !
What does it mean on a thinclient ?
Does anybody had this ?
I have 3 s
So I have to quit/kill splashy so I can have all verbose ?
Because when splashy stops, I don't have any text except : [215.042458]
Kernel panic - not syncing : Attempt to kill init !
it's the only thing I have on the screen.
2011/1/5 Ronny Aasen
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA
And I have to wait a few minutes before having kernel panic message.
2011/1/5 Jean-Charles Skolelinux
> So I have to quit/kill splashy so I can have all verbose ?
>
> Because when splashy stops, I don't have any text except : [215.042458]
> Kernel panic - not syncing : Attempt to kill init !
>
>
Onsdag 5. januar 2011 11.23.34 skrev Jean-Charles Skolelinux :
> [215.042458] Kernel panic - not syncing : Attempt to kill init !
>
> What does it mean on a thinclient ?
> Does anybody had this ?
If this is a new client, that you never had in production before, then
this "normally" means that y
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05. jan. 2011 11:23, Jean-Charles Skolelinux wrote:
> Hi,
>
> I've launched thinclients on Skole, I have splashy and as usual it
> crached at one moment, but then I don't have verbose and if I wait I
> have this message :
>
> [215.042458] Kernel p
This client was not in production before. BUT this client comes from a serie
of computer (Compaq Evo), the network card is a 3com.
Is this error could come because the MAC address of my thinclient is the
same as an other thinclient ?
2011/1/5 Klaus Ade Johnstad
> Onsdag 5. januar 2011 11.23.34
Hi,
I had the same problem with amd cpu on asus pc.
Try different ram it sounds like the ram is either not compatible with
the motherboard or bad or set into the bios the correct speed ram (I
solved with last option).
Ross
Il 2011/01/05 11:49, Klaus Ade Johnstad ha scritto:
Onsdag 5
Hi,
I had the same problem with amd cpu on asus pc.
Try different ram it sounds like the ram is either not compatible with
the motherboard or bad or set into the bios the correct speed ram (I
solved with last option).
cheers
Ross
Il 2011/01/05 11:49, Klaus Ade Johnstad ha scritto:
Hello Jean-Charles,
On Mi, 05 Jan 2011, Jean-Charles Siegel wrote:
> This client was not in production before. BUT this client comes from
> a serie of computer (Compaq Evo), the network card is a 3com.
Is it 3cR990? If you're testing debian-edu squeeze the failure is due
to missing package fir
On Wed, Jan 05, 2011 at 11:23:34AM +0100, Jean-Charles Skolelinux wrote:
I've launched thinclients on Skole, I have splashy and as usual it
crached at one moment, but then I don't have verbose and if I wait I
have this message :
[215.042458] Kernel panic - not syncing : Attempt to kill init !
I don't know how disable splashy :(
I'm looking for a tutorial but I don't find...
2011/1/5 Jonas Smedegaard
> On Wed, Jan 05, 2011 at 11:23:34AM +0100, Jean-Charles Skolelinux wrote:
>
>> I've launched thinclients on Skole, I have splashy and as usual it crached
>> at one moment, but then I don
[Jean-Charles Skolelinux]
> I don't know how disable splashy :(
> I'm looking for a tutorial but I don't find...
Try booting with the kernel argument 'nosplash'.
Happy hacking,
--
Petter Reinholdtsen
--
To UNSUBSCRIBE, email to debian-edu-requ...@lists.debian.org
with a subject of "unsubscrib
Onsdag 5. januar 2011 13.22.43 skrev Jean-Charles Skolelinux :
> I don't know how disable splashy :(
> I'm looking for a tutorial but I don't find...
Look in the file "default", either in
/var/lib/tftpboot/pxelinux.cfg/default or in
/var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default
(If you can'
Onsdag 5. januar 2011 13.43.15 skrev Jean-Charles Skolelinux :
> I have change /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default
>
> I had this : DEFAULT vmlinuz ro initrd=initrd.img boot=nfs quiet
>
> I add nosplash.
>
> The message is : nfsmount : need a path
>
> But it's only on this thincli
No for now, I don't change Ip-address and I won't do that on a production
server before I test it
2011/1/5 Klaus Ade Johnstad
> Onsdag 5. januar 2011 13.43.15 skrev Jean-Charles Skolelinux :
> > I have change /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default
> >
> > I had this : DEFAULT vmlinuz
Onsdag 5. januar 2011 14.01.47 skrev Jean-Charles Skolelinux :
> No for now, I don't change Ip-address and I won't do that on a
> production server before I test it
Maybe you can give us the few lines from syslog when the thinclient
boots?
--
Klaus Ade
kl...@bzz.no
67E61D18B2C44F8A3DA35C6D849F9
I change thinclient. I'm on a eVectra from HP
I have :
IP config : eth0 hardware address 00:00:02:02:67:0a mtu 1500 DHCP RARP
and then after a few minutes I obtain an address from 10.0.2.2 and not from
192.168.0.254.
Just after that I have the message : nfsmount : need a path
but other thincli
Onsdag 5. januar 2011 14.34.05 skrev Jean-Charles Skolelinux :
> and then after a few minutes I obtain an address from 10.0.2.2 and
> not from 192.168.0.254.
Then either you have misconfiguration in your network (eth0 and eth1 on
the server is somehow connected), or you have your thinclients on
I beg your pardon, I've wasted your time.
The mistake is human, but skole is perfect.
My mistake was to use a routeur as a switch and I forgot to shutdown the
dhcp server on the routeur, so there were conflicts between the dhcp of
tjener and the dhcp of the routeur.
I thank all of you very much
Onsdag 5. januar 2011 16.05.14 skrev Jean-Charles Skolelinux :
> I beg your pardon, I've wasted your time.
False.
> The mistake is human, but skole is perfect.
True.
:-)
--
Klaus Ade
kl...@bzz.no
67E61D18B2C44F8A3DA35C6D849F9F5F 26FA477D
signature.asc
Description: This is a digitally signe
Hi all,
the last days I found a little time to have a look into the issue of
using NFSv4 (and perhaps Kerberos) to mount the home directories.
I first configured NFS4 to export the home directories. After that I
tried kerberos authentication. However, I observed that it works only
in some cases,
[Andreas B. Mundt]
> I tried to find the reason for these corresponding A-records,
There are two aspects coming together to cause this effect. We use
strict mode in powerdns, allowing shared A/PTR entries in LDAP, and
the fact that SRV and MX records need to point to A records. As our
design all
On Wed, Jan 05, 2011 at 07:10:24PM +0100, Petter Reinholdtsen wrote:
[...]
> > I am not an expert regarding that stuff and I don't know if there
> > are other ways to achieve the desired. However, it looks as with the
> > current setup we need service principals for all host aliases.
>
> That isn'
Dear Andreas, dear Petter,
On Mi 05 Jan 2011 19:10:24 CET Petter Reinholdtsen wrote:
[Andreas B. Mundt]
I tried to find the reason for these corresponding A-records,
There are two aspects coming together to cause this effect. We use
strict mode in powerdns, allowing shared A/PTR entries in
[This e-mail has been automatically generated.]
You have one or more bugs assigned to you in the Bugzilla bug tracking system
(http://bugs.skolelinux.org/) that require
attention.
All of these bugs are in the NEW or REOPENED state, and have not been
touched in 7 days or more.
You need to take a
25 matches
Mail list logo
