[parisc-linux] Problem with FS of ESIEE on 720 !

[parisc-linux] Problem with FS of ESIEE on 720 !

[Christoph Plattner]

Hello PA-RISCers !

I have tried the current and the last ESIEE file system,
but I have problems with both. I used my own kernel,
running with the palinux-0.5, but the ESIEE always hangs.
If I do not change the /dev/console, I get the warning...
(of course, I have not compiled in the STI). So tried
to set the `mknod console c 5 1' and I also tried the
"hack" doing a link to `ttyS0'. In both cases `init'
gives no welcome message (version, etc...) and the machine
hangs !

Now I will instrument the kernel with `printk's to see,
if he can start something,.....

What's the topic with the TERM variable ??
Have I set it to a special value ???
Can that be the reason ???

Cheers
	Christoph P.


-----------------------------------------------------------------
private:        christoph.plattner@dot.at
company:        christoph.plattner@alcatel.at

Re: [parisc-linux] Problem with FS of ESIEE on 720 !

[marteau]

Hi Christoph and PA-RISCers !                                         
                                                                      
>I have tried the current and the last ESIEE file system,             
>but I have problems with both. I used my own kernel,                 
The kernels you will find are designed for 712 but it seems to work   
many others boxes!                                                    
vmlinux.mou is a kernel that integrate the low level mouse driver!    
(you can check via /proc/interrupts)                                  
                                                                      
>running with the palinux-0.5, but the ESIEE always hangs.            
>If I do not change the /dev/console, I get the warning...            
>(of course, I have not compiled in the STI). So tried                
>to set the `mknod console c 5 1' and I also tried the                
>"hack" doing a link to `ttyS0'. In both cases `init'                 
I read what Matthew wrote. We goona look at it in order to be         
automatic                                                             
                                                                      
>gives no welcome message (version, etc...) and the machine           
>hangs !                                                              
Our inittab file is specific for dual screen (if you use STI console  
and Serial terminal!)                                                 
I do not know how it reacts if the kernel expect a console with the   
serail port :( Any idea?                                              
                                                                      
Also you can refer to this mail:                                      
http://lists.parisc-linux.org/pipermail/parisc-linux/2001-March/011997
.html                                                                 
                                                                      
>Now I will instrument the kernel with `printk's to see,              
>if he can start something,.....                                      
You can but once init is launched the dmesg is less usefull.          
                                                                      
>What's the topic with the TERM variable ??                           
TERM=LINUX is not operational                                         
TERM=vt100 or pcansi are working!                                     
                                                                      
>Have I set it to a special value ???                                 
>Can that be the reason ???                                           
Don't think so                                                        
                                                                      
Bye, Thomas                                                           

Re: [parisc-linux] Problem with FS of ESIEE on 720 !

[Christoph Plattner]

Topic /dev/console :

You have to do nothing for "automatic" !!
The kernel manage this. The device `/dev/console' has
the major=5 minor=1. This device driver registered to this
major uses the system console. The system console driver
itself is internal a wrapper to the configured device
driver, defined via "console=ttyS0" the kernel command line
parameter. In this case (ttyS0) the driver on major=5
(/dev/console) intern calls the console i/o functions
(an own structure in the kernel) which are pointing to the
serial driver. In an other case, the pointer points to a
STI console interface. Also printk uses the pointer to
the write operation of the defined console !!

This console stuff was introduced in kernel 2.2
(2.1.xxx).

So the file system only should have the entry

crw-rw-rw-  root  root  5  1  xxxx xxxx /dev/console

Cheers
	Christop P.


marteau wrote:
> 
> Hi Christoph and PA-RISCers !
> 
> >I have tried the current and the last ESIEE file system,
> >but I have problems with both. I used my own kernel,
> The kernels you will find are designed for 712 but it seems to work
> many others boxes!
> vmlinux.mou is a kernel that integrate the low level mouse driver!
> (you can check via /proc/interrupts)
> 
> >running with the palinux-0.5, but the ESIEE always hangs.
> >If I do not change the /dev/console, I get the warning...
> >(of course, I have not compiled in the STI). So tried
> >to set the `mknod console c 5 1' and I also tried the
> >"hack" doing a link to `ttyS0'. In both cases `init'
> I read what Matthew wrote. We goona look at it in order to be
> automatic
> 
> >gives no welcome message (version, etc...) and the machine
> >hangs !
> Our inittab file is specific for dual screen (if you use STI console
> and Serial terminal!)
> I do not know how it reacts if the kernel expect a console with the
> serail port :( Any idea?
> 
> Also you can refer to this mail:
> http://lists.parisc-linux.org/pipermail/parisc-linux/2001-March/011997
> .html
> 
> >Now I will instrument the kernel with `printk's to see,
> >if he can start something,.....
> You can but once init is launched the dmesg is less usefull.
> 
> >What's the topic with the TERM variable ??
> TERM=LINUX is not operational
> TERM=vt100 or pcansi are working!
> 
> >Have I set it to a special value ???
> >Can that be the reason ???
> Don't think so
> 
> Bye, Thomas
> 
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/cgi-bin/mailman/listinfo/parisc-linux

-- 
  +--------V--------+	Christoph.Plattner@alcatel.at
  |  A L C A T E L  |	-----------------------------
  +-----------------+	Phone: +43 1 27722 3706	
         T A S		Fax:   +43 1 27722 3955

[parisc-linux] Again problem with FS of ESIEE on 720 !

[Christoph Plattner]

Again and again. The ESIEE file system does not work. The kernel
is built myself (not from ESIEE !!!) and the nfs_root is set to
ESIEE. The problem is, that the init or other processes like shell
do not start. The hang before any output is done.

I instruemented the kernel for testing stdout via /dev/console and
to print out where it is. In the kernel everything is perfect.

No process is able to start (giver per init= command line or patched
in init/main.c in the kernel tree.

Also an old trick of mine, starting the bash or init via strace from
the kernel (calling strace instead of init in execve) does not work,
noi reaction, the system seems to be halted or no I/O is working,
or perhaps there is a problem with the shared libraries.

Is there something to do special by building the kernel to use ESIEE ??
Cheers
	Christoph


marteau wrote:
> 
> Hi Christoph and PA-RISCers !
> 
> >I have tried the current and the last ESIEE file system,
> >but I have problems with both. I used my own kernel,
> The kernels you will find are designed for 712 but it seems to work
> many others boxes!
> vmlinux.mou is a kernel that integrate the low level mouse driver!
> (you can check via /proc/interrupts)
> 
> >running with the palinux-0.5, but the ESIEE always hangs.
> >If I do not change the /dev/console, I get the warning...
> >(of course, I have not compiled in the STI). So tried
> >to set the `mknod console c 5 1' and I also tried the
> >"hack" doing a link to `ttyS0'. In both cases `init'
> I read what Matthew wrote. We goona look at it in order to be
> automatic
> 
> >gives no welcome message (version, etc...) and the machine
> >hangs !
> Our inittab file is specific for dual screen (if you use STI console
> and Serial terminal!)
> I do not know how it reacts if the kernel expect a console with the
> serail port :( Any idea?
> 
> Also you can refer to this mail:
> http://lists.parisc-linux.org/pipermail/parisc-linux/2001-March/011997
> .html
> 
> >Now I will instrument the kernel with `printk's to see,
> >if he can start something,.....
> You can but once init is launched the dmesg is less usefull.
> 
> >What's the topic with the TERM variable ??
> TERM=LINUX is not operational
> TERM=vt100 or pcansi are working!
> 
> >Have I set it to a special value ???
> >Can that be the reason ???
> Don't think so
> 
> Bye, Thomas
> 
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/cgi-bin/mailman/listinfo/parisc-linux

-- 
-------------------------------------------------------------------------
private:	christoph.plattner@dot.at
company:	christoph.plattner@alcatel.at