headers
Beat Burgener | NetSuccess GmbH | 4 May 2011 10:14
Picon

Re: Problem starting TS 2.2.2.g

The detailed message is:

/sbin/init: missing file argument
Try /sbin/init --help"
Kernel panic - not syncing: Attempt to kill init!

Beat

On 03.05.2011 19:45, Stephen Welch wrote:
> You tried to remove splash=
> silent from the default file in the pxelinux.cfg directory?
>
> It may not be called default it depends on your setup.

In this case, removing the console redirection "console=ttyS3" enabled 
the kernel output, as otherwise it would be redirected to a serial port 
that does not exist.

Now, I could see that "/sbin/init: invalid file argument or similar was 
displayed ...

I'll try to get into that ...

Beat

> HTH
>
> Stephen
>
> On Tuesday, 3 May 2011, Beat Burgener | NetSuccess GmbH
(Continue reading)

Permalink | Reply |
headers
Stephen Welch | 4 May 2011 10:27
Picon

Re: Problem starting TS 2.2.2.g

Hi Beat.

On 4 May 2011 09:14, Beat Burgener | NetSuccess GmbH
<beat.burgener@...> wrote:
> The detailed message is:
>
> /sbin/init: missing file argument
> Try /sbin/init --help"
> Kernel panic - not syncing: Attempt to kill init!
>
> Beat

I also get this error with version 2.2.2g?

I have not had a chance to check (trying to get TS working on a
completely new Client) with 2.2.2f which works fine on my other
clients.

There are errors similar to this floating around the forums.

I was building from the command line.  A build from the TS-O-Matic
site works up to the point of errors for the network card.

I have an Atheros NIC and need to build from the cmd line so I can
include the drivers I need.

Are you building from the TS-O-Matic or cmd line build?

Stephen
(Continue reading)

Permalink | Reply |
headers
Mike Eriksen | 4 May 2011 10:32
Picon

Re: Problem starting TS 2.2.2.g

On Wed, May 4, 2011 at 10:14 AM, Beat Burgener | NetSuccess GmbH
<beat.burgener@...> wrote:
> The detailed message is:
>
> /sbin/init: missing file argument
> Try /sbin/init --help"
> Kernel panic - not syncing: Attempt to kill init!

I have made hundreds of 2.2.2g build and used them with both iso, pxe
and syslinux and *never* had this error.

Please send me your build.conf and ts.conf.buildtime off-list and I'll
have a look.

Mike

> Beat
>
>
> On 03.05.2011 19:45, Stephen Welch wrote:
>> You tried to remove splash=
>> silent from the default file in the pxelinux.cfg directory?
>>
>> It may not be called default it depends on your setup.
>
> In this case, removing the console redirection "console=ttyS3" enabled
> the kernel output, as otherwise it would be redirected to a serial port
> that does not exist.
>
> Now, I could see that "/sbin/init: invalid file argument or similar was
(Continue reading)

Permalink | Reply |
headers
Beat Burgener | NetSuccess GmbH | 4 May 2011 11:14
Picon

Re: Problem starting TS 2.2.2.g

Hi

I tried "g" and "f" from the German TSOM (GUI) ...
Both produce the same error....

As the build.conf does not contain any confidential data, I have it 
attached here:

module     acpi #
module     e1000 #
module     e1000e #
module     tg3 #
module     aes-i586 #
module     usb-hid #
module     usb-storage #
module     usb-cdrom #
module     ide-cd #
module     ahci #
module     ata_piix #
module     isofs #
module     vfat #
module     ntfs #
module     ext2 #
module     ext3 #
module     supermount #
package     hwclock #
package     rdate #
package     xorg6-radeon #
package     xorg6-vesa #
package     keymaps-de_ch #
(Continue reading)

Permalink | Reply |
headers
TrevorB | 4 May 2011 13:42
Picon
Gravatar

Re: Problem starting TS 2.2.2.g

It sound more like a corrupted vmlinuz or initrd to me.

Just make sure that they are transferred as binary files and not ascii.

The vmlinuz should be the same as 2.2.2f, but the initrd is your built
one.

Also try the same configs on the DK site (Mike is pretty fastidious
about his setup).

Good Luck
Trevor B

On Wed, 2011-05-04 at 11:14 +0200, Beat Burgener | NetSuccess GmbH
wrote:
> Hi
> 
> I tried "g" and "f" from the German TSOM (GUI) ...
> Both produce the same error....
> 
> As the build.conf does not contain any confidential data, I have it 
> attached here:
> 
> module     acpi #
> module     e1000 #
> module     e1000e #
> module     tg3 #
> module     aes-i586 #
> module     usb-hid #
> module     usb-storage #
(Continue reading)

Permalink | Reply |
headers
Beat Burgener | NetSuccess GmbH | 4 May 2011 14:24
Picon

Re: Problem starting TS 2.2.2.g

Trevor

Thank you. As I can unsquashfs the initrd (the main method to modify the 
installation for 802.1X), I guess the initrd is ok (binary).
BTW: The initrd in questions was NOT modified by me but was unsquashed 
for a test and still shows this behaviour ...

I'll create a new image from DK and try during the break when they 
students have left for a coffee.

Regards

Beat

On 04.05.2011 13:42, TrevorB wrote:
> It sound more like a corrupted vmlinuz or initrd to me.
>
> Just make sure that they are transferred as binary files and not ascii.
>
> The vmlinuz should be the same as 2.2.2f, but the initrd is your built
> one.
>
> Also try the same configs on the DK site (Mike is pretty fastidious
> about his setup).
>
> Good Luck
> Trevor B
>
> On Wed, 2011-05-04 at 11:14 +0200, Beat Burgener | NetSuccess GmbH
> wrote:
(Continue reading)

Permalink | Reply |
headers
Mike Eriksen | 4 May 2011 15:07
Picon

Re: Problem starting TS 2.2.2.g

Well, this is getting interesting.

I took a fresh Thinstation-2.2.2g.tar.gz and decompressed it. Then I
copy-pasted you build.conf from your post. I needed to add "module
pcnet32" and changed the ICA URL. Otherwise I didn't touch a thing.

I made a build and it crashed exactly like you said. I then
comment-out'ed almost everything leaving just pcnet32, vesa, icewm a
other minor bit. And now it worked nicely. Next I added module by
module, package by package back into the image until I was back to
your full build.conf. And it still works! Well, except for package
debug, that seems troublesome, but just removing that package alone
didn't solve the original problem (That was the first thing I tried -
unsuccessful).

It seems to me that your build.conf contains invalid non-printable
characters (whitespace or sub-asccii 32) that I somehow got edited out
through my tiresome process. The short fact is that the viewable part
of your build.conf and 2.2.2g produces a working image.

I'd still like to get an emailed copy of your build.conf. If it get
email as an attachment it gets properly mime encoded and doesn't have
to depend on weird email programs obscure ideas of character encoding.

Mike
--

-- 
Operator of the Danish TS-O-Matic.
http://thinstation.org
- a light, full featured linux based thin client OS
(Continue reading)

Permalink | Reply |
headers
Mike Eriksen | 4 May 2011 16:38
Picon

Re: Problem starting TS 2.2.2.g

OK, I have to withdraw this one. I've repeated the procedure making a
build.conf from Beat's post, and no matter what I do I can't provoke
the error anymore. It works correctly every time now.

I really need that attachment.

Mike

On Wed, May 4, 2011 at 3:07 PM, Mike Eriksen
<thinstation.mike@...> wrote:
> Well, this is getting interesting.
>
> I took a fresh Thinstation-2.2.2g.tar.gz and decompressed it. Then I
> copy-pasted you build.conf from your post. I needed to add "module
> pcnet32" and changed the ICA URL. Otherwise I didn't touch a thing.
>
> I made a build and it crashed exactly like you said. I then
> comment-out'ed almost everything leaving just pcnet32, vesa, icewm a
> other minor bit. And now it worked nicely. Next I added module by
> module, package by package back into the image until I was back to
> your full build.conf. And it still works! Well, except for package
> debug, that seems troublesome, but just removing that package alone
> didn't solve the original problem (That was the first thing I tried -
> unsuccessful).
>
> It seems to me that your build.conf contains invalid non-printable
> characters (whitespace or sub-asccii 32) that I somehow got edited out
> through my tiresome process. The short fact is that the viewable part
> of your build.conf and 2.2.2g produces a working image.
>
(Continue reading)

Permalink | Reply |

Gmane