1140 lines
25 KiB
HTML
1140 lines
25 KiB
HTML
<HTML
|
|
><HEAD
|
|
><TITLE
|
|
>Questions and Troubleshooting</TITLE
|
|
><META
|
|
NAME="GENERATOR"
|
|
CONTENT="Modular DocBook HTML Stylesheet Version 1.63
|
|
"><LINK
|
|
REL="HOME"
|
|
TITLE="Linux on the Sun JavaStation
|
|
NC HOWTO"
|
|
HREF="index.html"><LINK
|
|
REL="PREVIOUS"
|
|
TITLE="Booting Your JavaStation"
|
|
HREF="javastationboot-bootyourjavastationchapter.html"><LINK
|
|
REL="NEXT"
|
|
TITLE="Reference Docs"
|
|
HREF="referencedocs-chapter.html"></HEAD
|
|
><BODY
|
|
CLASS="sect1"
|
|
BGCOLOR="#FFFFFF"
|
|
TEXT="#000000"
|
|
LINK="#0000FF"
|
|
VLINK="#840084"
|
|
ALINK="#0000FF"
|
|
><DIV
|
|
CLASS="NAVHEADER"
|
|
><TABLE
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TH
|
|
COLSPAN="3"
|
|
ALIGN="center"
|
|
><SPAN
|
|
CLASS="application"
|
|
>Linux</SPAN
|
|
> on the <SPAN
|
|
CLASS="productname"
|
|
>Sun JavaStation
|
|
</SPAN
|
|
> <SPAN
|
|
CLASS="acronym"
|
|
>NC</SPAN
|
|
> HOWTO</TH
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="left"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="javastationboot-bootyourjavastationchapter.html"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="80%"
|
|
ALIGN="center"
|
|
VALIGN="bottom"
|
|
></TD
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="right"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="referencedocs-chapter.html"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"></DIV
|
|
><DIV
|
|
CLASS="sect1"
|
|
><H1
|
|
CLASS="sect1"
|
|
><A
|
|
NAME="QuestionsandTroubleshooting-QuestionsandTroubleShootingChapter"
|
|
>9. Questions and Troubleshooting</A
|
|
></H1
|
|
><P
|
|
> This chapter is intended to provide solutions to frequently and
|
|
infrequently encountered problems in enabling <SPAN
|
|
CLASS="application"
|
|
>Linux
|
|
</SPAN
|
|
> on the <SPAN
|
|
CLASS="productname"
|
|
>JavaStations</SPAN
|
|
>.
|
|
</P
|
|
><DIV
|
|
CLASS="sect2"
|
|
><H2
|
|
CLASS="sect2"
|
|
><A
|
|
NAME="QuestionsandTroubleshooting-NotExecutableTSSection"
|
|
>9.1. When booting, the message <SPAN
|
|
CLASS="QUOTE"
|
|
>"The file just loaded does not
|
|
appear to be executable."</SPAN
|
|
> Why?</A
|
|
></H2
|
|
><P
|
|
> On systems that have the older OpenBoot version 2.3, and are not set
|
|
up to use PROLL, you will get this message when attempting to boot
|
|
up a kernel image that is not in AOUT format. Be sure to run
|
|
<TT
|
|
CLASS="userinput"
|
|
><B
|
|
>elftoaout</B
|
|
></TT
|
|
> on your kernel image, as described
|
|
in the "Kernel Build" chapter.
|
|
</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="sect2"
|
|
><H2
|
|
CLASS="sect2"
|
|
><A
|
|
NAME="QuestionsandTroubleshooting-NoMagicTSSection"
|
|
>9.2. When booting, the message <SPAN
|
|
CLASS="QUOTE"
|
|
>"no a.out magic"</SPAN
|
|
> appears
|
|
and halts the boot. Why?</A
|
|
></H2
|
|
><P
|
|
> On systems that are set up to use PROLL, you will see this message
|
|
when attempting to boot up a kernel image that is not in AOUT format.
|
|
Be sure to run <TT
|
|
CLASS="userinput"
|
|
><B
|
|
>elftoaout</B
|
|
></TT
|
|
> on your kernel image,
|
|
as described in the "Kernel Build" chapter.
|
|
</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="sect2"
|
|
><H2
|
|
CLASS="sect2"
|
|
><A
|
|
NAME="QuestionsandTroubleshooting-FlashTSSection"
|
|
>9.3. I tried booting a Krups but JavaOS comes up. I don't even have JavaOS!</A
|
|
></H2
|
|
><P
|
|
> This likely means you have a flash SIMM install, and the flash SIMM has
|
|
JavaOS loaded on it. Remove the SIMM and the problem should go away.
|
|
</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="sect2"
|
|
><H2
|
|
CLASS="sect2"
|
|
><A
|
|
NAME="QuestionsandTroubleshooting-TenMBLimitTSSection"
|
|
>9.4. Cannot Boot an <SPAN
|
|
CLASS="QUOTE"
|
|
>"Embedded-Root"</SPAN
|
|
> image > 10 <SPAN
|
|
CLASS="acronym"
|
|
>MB
|
|
</SPAN
|
|
>on my <SPAN
|
|
CLASS="productname"
|
|
>JavaStation</SPAN
|
|
>. Why?</A
|
|
></H2
|
|
><P
|
|
> There is a known limit of 8 <SPAN
|
|
CLASS="acronym"
|
|
>MB</SPAN
|
|
> when using the
|
|
<SPAN
|
|
CLASS="QUOTE"
|
|
>"Embedded-Root"</SPAN
|
|
> boot image option.
|
|
</P
|
|
><P
|
|
> The cause of this is the current version of the <SPAN
|
|
CLASS="application"
|
|
>PROLL
|
|
</SPAN
|
|
> software, which map only 8 <SPAN
|
|
CLASS="acronym"
|
|
>MB</SPAN
|
|
>
|
|
of low memory. Any more and banking support would need to be
|
|
added to it.
|
|
</P
|
|
><P
|
|
> If needed, this limit can be fixed by someone, as the source
|
|
to <SPAN
|
|
CLASS="application"
|
|
>PROLL</SPAN
|
|
> has been released under terms
|
|
of the General Public License (<SPAN
|
|
CLASS="acronym"
|
|
>GPL</SPAN
|
|
>).
|
|
</P
|
|
><P
|
|
> So in reality, the embedded image size limit is really 8 <SPAN
|
|
CLASS="acronym"
|
|
>MB</SPAN
|
|
>
|
|
, not 10 <SPAN
|
|
CLASS="acronym"
|
|
>MB</SPAN
|
|
>. If 10 <SPAN
|
|
CLASS="acronym"
|
|
>MB</SPAN
|
|
> somehow works
|
|
for you, it is sheerly by <SPAN
|
|
CLASS="QUOTE"
|
|
>"luck"</SPAN
|
|
>!
|
|
</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="sect2"
|
|
><H2
|
|
CLASS="sect2"
|
|
><A
|
|
NAME="QuestionsandTroubleshooting-KeyGarblesTSSection"
|
|
>9.5. After Booting, Typing Anything Yields Garbage Characters. Why?</A
|
|
></H2
|
|
><P
|
|
> There are a few possibilities for this. Among them:
|
|
</P
|
|
><P
|
|
></P
|
|
><OL
|
|
TYPE="1"
|
|
><LI
|
|
><P
|
|
> You have an incorrect device # for tty0.
|
|
</P
|
|
></LI
|
|
><LI
|
|
><P
|
|
> The <SPAN
|
|
CLASS="QUOTE"
|
|
>"keytable"</SPAN
|
|
> loaded is incorrect. Make sure you use
|
|
<SPAN
|
|
CLASS="QUOTE"
|
|
>"sun"</SPAN
|
|
> instead of <SPAN
|
|
CLASS="QUOTE"
|
|
>"PC"</SPAN
|
|
> if you use the keytable
|
|
program. Look for the keytable configuration file if it exists.
|
|
</P
|
|
></LI
|
|
></OL
|
|
></DIV
|
|
><DIV
|
|
CLASS="sect2"
|
|
><H2
|
|
CLASS="sect2"
|
|
><A
|
|
NAME="QuestionsandTroubleshooting-FontServTSSection"
|
|
>9.6. In X Sessions to a <SPAN
|
|
CLASS="application"
|
|
>Solaris</SPAN
|
|
> server, the
|
|
font server <SPAN
|
|
CLASS="QUOTE"
|
|
>"xfs"</SPAN
|
|
> crashes. Why?</A
|
|
></H2
|
|
><P
|
|
> If you do <SPAN
|
|
CLASS="application"
|
|
>X</SPAN
|
|
> sessions to a <SPAN
|
|
CLASS="application"
|
|
>Solaris
|
|
</SPAN
|
|
> server, and you find that your sessions are no longer opening
|
|
up new windows, chances are the font server on the <SPAN
|
|
CLASS="application"
|
|
>Solaris
|
|
</SPAN
|
|
> host has crashed. This is a known bug in <SPAN
|
|
CLASS="application"
|
|
> Solaris</SPAN
|
|
> 2.6 and 2.7 when you have about 2 dozen <SPAN
|
|
CLASS="hardware"
|
|
> X terminals</SPAN
|
|
> sessions running.
|
|
</P
|
|
><P
|
|
> The fix is to move the font server to a different OS and point your
|
|
<SPAN
|
|
CLASS="productname"
|
|
>JavaStations</SPAN
|
|
> there, or to upgrade your
|
|
<SPAN
|
|
CLASS="application"
|
|
>Solaris</SPAN
|
|
> to the 2.7 11/99 maintenance
|
|
release or <SPAN
|
|
CLASS="application"
|
|
>Solaris 8</SPAN
|
|
> which both (apparently)
|
|
have fixes to this problem.
|
|
</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="sect2"
|
|
><H2
|
|
CLASS="sect2"
|
|
><A
|
|
NAME="QuestionsandTroubleshooting-XDMCPTSSection"
|
|
>9.7. Performing Indirect <SPAN
|
|
CLASS="acronym"
|
|
>XDMCP</SPAN
|
|
> to a <SPAN
|
|
CLASS="application"
|
|
> Solaris</SPAN
|
|
> Server Results in Session Login Failures. Why?</A
|
|
></H2
|
|
><P
|
|
> Congratulations! You probably have one of patch numbers 107180-12 through
|
|
107180-19 installed on a <SPAN
|
|
CLASS="application"
|
|
>Solaris 7</SPAN
|
|
>
|
|
server. You need to upgrade to 107180-20 or above to fix this problem.
|
|
</P
|
|
><P
|
|
> I (your HOWTO author) reported this problem to Sun in November 1999,
|
|
at which time I was told a fix was not scheduled to be made, since I
|
|
was using an <SPAN
|
|
CLASS="QUOTE"
|
|
>"unsupported configuration."</SPAN
|
|
>. Never mind
|
|
that the client was a piece of hardware made by Sun itself. Also never
|
|
mind that indirect <SPAN
|
|
CLASS="acronym"
|
|
>XDMCP</SPAN
|
|
> queries is a standard itself
|
|
which was broken by Sun. A call back in late January 2000, and I learn that
|
|
the record of my previous call was non-existant, but a fix was now on
|
|
its way. The fix finally was made available in April 2000, five months
|
|
after first reporting the problem. Considering revisions to this
|
|
patch during the broken <SPAN
|
|
CLASS="acronym"
|
|
>XDMCP</SPAN
|
|
> period dealt with
|
|
fixing system security issues, we were forced to run the older insecure
|
|
software for five months while waiting for a fix to a problem which
|
|
should have been patched immediately.
|
|
</P
|
|
><P
|
|
> The moral of the story: test your <SPAN
|
|
CLASS="productname"
|
|
>JavaStation</SPAN
|
|
>
|
|
configuration against an upgraded server that is not in production mode.
|
|
</P
|
|
><P
|
|
> If you have XDMCP problems not related to these faulty Solaris patches,
|
|
it may be a new problem, so please report it.
|
|
</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="sect2"
|
|
><H2
|
|
CLASS="sect2"
|
|
><A
|
|
NAME="QuestionsandTroubleshooting-SUSETftpTSSection"
|
|
>9.8. TFTPd config doesn't work on SUSE 6.3. Why?</A
|
|
></H2
|
|
><P
|
|
> This was reported by a user after this document was first released.
|
|
</P
|
|
><P
|
|
> In SUSE 6.3, using the tftpd from the 'a' package of the netkit rpm,
|
|
you must be sure your tftpd line in /etc/inetd.conf has the -s flag.
|
|
Otherwise you need to specify a full path.
|
|
</P
|
|
><P
|
|
> Also, it is not necessary to run tftpd as root, so the suggested username
|
|
and group for tftpd on SUSE 6.3 is 'nobody' and 'nogroup'
|
|
</P
|
|
><P
|
|
> It is not known whether these changes are needed for newer versions of
|
|
SUSE.
|
|
</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="sect2"
|
|
><H2
|
|
CLASS="sect2"
|
|
><A
|
|
NAME="QuestionsandTroubleshooting-RARPFAQSection"
|
|
>9.9. Regarding <SPAN
|
|
CLASS="acronym"
|
|
>RARP</SPAN
|
|
>: Is it Needed or Not?</A
|
|
></H2
|
|
><P
|
|
> <SPAN
|
|
CLASS="acronym"
|
|
>RARP</SPAN
|
|
> is not needed with the <SPAN
|
|
CLASS="productname"
|
|
>Krups
|
|
</SPAN
|
|
> or <SPAN
|
|
CLASS="productname"
|
|
>Espresso</SPAN
|
|
> models and
|
|
recent <SPAN
|
|
CLASS="application"
|
|
>PROLL</SPAN
|
|
> software. <SPAN
|
|
CLASS="acronym"
|
|
>RARP
|
|
</SPAN
|
|
> is required for <SPAN
|
|
CLASS="productname"
|
|
>Mr. Coffee</SPAN
|
|
>,
|
|
however.
|
|
</P
|
|
><P
|
|
> This 'Server Configuration' chapter explained how to set up
|
|
kernel-level <SPAN
|
|
CLASS="acronym"
|
|
>RARP</SPAN
|
|
> on 2.2.x systems.
|
|
</P
|
|
><P
|
|
> On servers with kernel versions 2.3.x/2.4.x, kernel-level
|
|
<SPAN
|
|
CLASS="acronym"
|
|
>RARP</SPAN
|
|
> support is removed. The ZLS holds a
|
|
version of <SPAN
|
|
CLASS="application"
|
|
> ANK userland RARP</SPAN
|
|
> from Andi
|
|
Klein of SuSE that will work with Linux/SPARC. It is available
|
|
from: <A
|
|
HREF="http://people.redhat.com/zaitcev/linux/rarpd-ap1.tar.bz2"
|
|
TARGET="_top"
|
|
>
|
|
http://people.redhat.com/zaitcev/linux/rarpd-ap1.tar.bz2</A
|
|
>.
|
|
The command to use then is <TT
|
|
CLASS="userinput"
|
|
><B
|
|
>rarpd-ank -e eth0</B
|
|
></TT
|
|
>.
|
|
<SPAN
|
|
CLASS="QUOTE"
|
|
>"-e"</SPAN
|
|
> makes it ignore /tftpboot checking, and
|
|
<SPAN
|
|
CLASS="QUOTE"
|
|
>"eth0"</SPAN
|
|
> is needed if you are behind a firewall.
|
|
</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="sect2"
|
|
><H2
|
|
CLASS="sect2"
|
|
><A
|
|
NAME="QuestionsandTroubleshooting-EspressoCardReaderFAQSection"
|
|
>9.10. Can One Use the Smart Card Reader on the Espresso models?</A
|
|
></H2
|
|
><P
|
|
> This is not currently supported, but the reader follows an
|
|
ISO standard (ISO 7816-3). On <SPAN
|
|
CLASS="productname"
|
|
> Espresso</SPAN
|
|
>, if you look into <SPAN
|
|
CLASS="application"
|
|
>PROLL</SPAN
|
|
>,
|
|
there are definitions for the <SPAN
|
|
CLASS="acronym"
|
|
>GPIO</SPAN
|
|
> smartcard data/clock in
|
|
<SPAN
|
|
CLASS="QUOTE"
|
|
>"eeprom.c"</SPAN
|
|
>. So a programmer should technically be able to get
|
|
the Smart Card slot running.
|
|
</P
|
|
><P
|
|
> Whether the smartcard reader on Dover and Espresso are equivalent is
|
|
not known.
|
|
</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="sect2"
|
|
><H2
|
|
CLASS="sect2"
|
|
><A
|
|
NAME="QuestionsandTroubleshooting-SolarisDHCPFAQSection"
|
|
>9.11. Can One Use the <SPAN
|
|
CLASS="application"
|
|
>Solaris</SPAN
|
|
> <SPAN
|
|
CLASS="acronym"
|
|
>DHCP</SPAN
|
|
>
|
|
server instead of <SPAN
|
|
CLASS="acronym"
|
|
>ISC</SPAN
|
|
>?</A
|
|
></H2
|
|
><P
|
|
> Yes, this is possible. Earlier ISC daemons had problems dealing
|
|
with 1514-byte requests of the JavaStations, while the Solaris
|
|
server was able to handle them without problems. Also, former
|
|
users of JavaOS may already have their Solaris DHCP server
|
|
active, and wish to keep things on one machine.
|
|
</P
|
|
><P
|
|
> Here is how to configure it:
|
|
</P
|
|
><P
|
|
> First, fill in your /var/dhcp/<SPAN
|
|
CLASS="QUOTE"
|
|
>"networks"</SPAN
|
|
> file, populating
|
|
it with ethernet to IP info, and the appropriate leastime.
|
|
</P
|
|
><TABLE
|
|
BORDER="0"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="screen"
|
|
> # This example uses "infinite" leastime
|
|
#
|
|
0108002081C2AE 03 192.168.128.1 192.168.128.100 -1 java01 # JavaStation
|
|
010800208E4CF6 03 192.168.128.2 192.168.128.100 -1 java02 # JavaStation
|
|
</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
><P
|
|
> Next, fill in your /var/dhcp/dhcptab file with entries similar to:
|
|
</P
|
|
><TABLE
|
|
BORDER="0"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="screen"
|
|
> ##
|
|
# First, some network info
|
|
#
|
|
Locale m :UTCoffst=21600:
|
|
www m :Include=Locale:Timeserv=192.168.128.100:DNSdmain=my.own.net:DNSserv=192.168.128.100:
|
|
192.168.128.0 m :Broadcst=192.168.128.255:Subnet=255.255.255.0:MTU=1500:BootSrvA=192.168.128.100:Router=192.168.128.101:NISdmain=my.own.net:NISservs=192.168.128.100:
|
|
#
|
|
# note: BootServA can point to a different TFTP server to get the kernel image
|
|
# off of.
|
|
#
|
|
#
|
|
##
|
|
# Now we define the JavaStation TFTPboot parameters
|
|
#
|
|
SUNW.Linux m :Include=www:JOSchksm=0x155dbf97:Rootpath=/tftpboot:BootFile=proll.mrcoffee:BootSrvA=192.168.128.100:TFTPsrvN=lnxserv:
|
|
SUNW.Linux.Krups m :Include=www:Rootpath=/tftpboot:BootFile=proll.krups:BootSrvA=192.168.128.100:TFTPsrvN=lnxserv:
|
|
#
|
|
#
|
|
# note: different classes are defined for the different PROLL images.
|
|
#
|
|
##
|
|
# Lastly, we list our hosts and which boot class each one gets.
|
|
java01 m :LeaseTim=-1:Include=SUNW.Linux:
|
|
java02 m :LeaseTim=-1:Include=SUNW.Linux.Krups:
|
|
#
|
|
#
|
|
#
|
|
###
|
|
</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></DIV
|
|
><DIV
|
|
CLASS="sect2"
|
|
><H2
|
|
CLASS="sect2"
|
|
><A
|
|
NAME="QuestionsandTroubleshooting-BootOptionsFAQSection"
|
|
>9.12. Can One Pass Arguments to <SPAN
|
|
CLASS="QUOTE"
|
|
>"/sbin/init"</SPAN
|
|
> in a Diskless
|
|
Boot like This?</A
|
|
></H2
|
|
><P
|
|
> <SPAN
|
|
CLASS="application"
|
|
>PROLL</SPAN
|
|
> ships with <SPAN
|
|
CLASS="acronym"
|
|
>DHCP</SPAN
|
|
>
|
|
options disabled, but it could be changed. You would then do something
|
|
like <SPAN
|
|
CLASS="QUOTE"
|
|
>"/tftpboot/0A0A0000.ARGS"</SPAN
|
|
> to get those parameters in.
|
|
</P
|
|
><P
|
|
> If you boot from flash memory, <SPAN
|
|
CLASS="application"
|
|
>PROLL</SPAN
|
|
> picks up
|
|
<SPAN
|
|
CLASS="application"
|
|
>SILO</SPAN
|
|
> options (where <SPAN
|
|
CLASS="application"
|
|
>SILO
|
|
</SPAN
|
|
> is > version 0.9.6 and <SPAN
|
|
CLASS="application"
|
|
>PROLL</SPAN
|
|
>
|
|
is >= version 11)
|
|
</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="sect2"
|
|
><H2
|
|
CLASS="sect2"
|
|
><A
|
|
NAME="QuestionsandTroubleshooting-EnablingXFAQSection"
|
|
>9.13. Enabling <SPAN
|
|
CLASS="application"
|
|
>X</SPAN
|
|
> on the
|
|
<SPAN
|
|
CLASS="productname"
|
|
>JavaStation</SPAN
|
|
></A
|
|
></H2
|
|
><P
|
|
> This is a very frequently asked question.
|
|
</P
|
|
><P
|
|
> Enabling <SPAN
|
|
CLASS="application"
|
|
>X</SPAN
|
|
> on the <SPAN
|
|
CLASS="productname"
|
|
>JavaStation
|
|
</SPAN
|
|
> is possible.
|
|
</P
|
|
><P
|
|
> First, be sure you have enabled the appropriate framebuffer device
|
|
in your kernel's configuration, as described in the "Kernel Build"
|
|
chapter.
|
|
</P
|
|
><P
|
|
> Next, you'll want to use the generic <SPAN
|
|
CLASS="application"
|
|
>Sun Framebuffer X server
|
|
</SPAN
|
|
> and <SPAN
|
|
CLASS="QUOTE"
|
|
>"XF86Config"</SPAN
|
|
> file. You can build this
|
|
yourself, or you can try someone's prebuilt binaries, such as the samples
|
|
pointed to in the "FileSystem Build" chapter.
|
|
</P
|
|
><P
|
|
> Recent editions of the framebuffer server coinciding with XFree 4 are
|
|
reported not to work. Use the older version based on XFree 3.3, or
|
|
fix the new version and be a hero to thousands.
|
|
</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="sect2"
|
|
><H2
|
|
CLASS="sect2"
|
|
><A
|
|
NAME="QuestionsandTroubleshooting-MailingListFAQSection"
|
|
>9.14. Is There Mailing List Help?</A
|
|
></H2
|
|
><P
|
|
> There are two mailing devoted exclusively to running <SPAN
|
|
CLASS="application"
|
|
>Linux
|
|
</SPAN
|
|
> on <SPAN
|
|
CLASS="hardware"
|
|
>SPARC processor</SPAN
|
|
> based machines
|
|
such as the <SPAN
|
|
CLASS="productname"
|
|
>JavaStations</SPAN
|
|
>.
|
|
</P
|
|
><P
|
|
> The first mailing list is the sparclinux list on VGER,
|
|
at <TT
|
|
CLASS="email"
|
|
><<A
|
|
HREF="mailto:sparclinux@vger.kernel.org"
|
|
>sparclinux@vger.kernel.org</A
|
|
>></TT
|
|
>.
|
|
You should first subscribe to it by sending a message to
|
|
<TT
|
|
CLASS="email"
|
|
><<A
|
|
HREF="mailto:majordomo@vger.kernel.org"
|
|
>majordomo@vger.kernel.org</A
|
|
>></TT
|
|
> with a subject and body line
|
|
of <SPAN
|
|
CLASS="QUOTE"
|
|
>"subscribe sparclinux <your_email_address>"</SPAN
|
|
>. You
|
|
can leave out your email address, but it is helpful to put it in if you
|
|
have multiple valid addresses at your site.
|
|
</P
|
|
><P
|
|
> Archives of the VGER sparclinux mailing list are kept at:
|
|
<A
|
|
HREF="http://www.progressive-comp.com/Lists/?l=linux-sparc&r=1& w=2"
|
|
TARGET="_top"
|
|
>http://www.progressive-comp.com/Lists/?l=linux-sparc&r=1&w=2"
|
|
</A
|
|
>
|
|
</P
|
|
><P
|
|
> The second mailing list is the debian-sparc list at the Debian Project,
|
|
at <TT
|
|
CLASS="email"
|
|
><<A
|
|
HREF="mailto:debian-sparc@lists.debian.org"
|
|
>debian-sparc@lists.debian.org</A
|
|
>></TT
|
|
>. You should first
|
|
subscribe to it by sending a message to
|
|
<TT
|
|
CLASS="email"
|
|
><<A
|
|
HREF="mailto:debian-sparc-request@lists.debian.org"
|
|
>debian-sparc-request@lists.debian.org</A
|
|
>></TT
|
|
> with a subject and
|
|
body line of <SPAN
|
|
CLASS="QUOTE"
|
|
>"subscribe <your_email_address>"</SPAN
|
|
>. You
|
|
can leave out your email address, but it is helpful to put it in if you
|
|
have multiple valid addresses at your site.
|
|
</P
|
|
><P
|
|
> As many of the SPARC kernel hackers run Debian, it is helpful to
|
|
subscribe to both lists.
|
|
</P
|
|
><P
|
|
> Please do not report problems about this document to either list, but
|
|
send them to <TT
|
|
CLASS="email"
|
|
><<A
|
|
HREF="mailto:rsd@dubinski-family.org"
|
|
>rsd@dubinski-family.org</A
|
|
>></TT
|
|
> instead. Also,
|
|
please use the list archives. JavaStations have been supported on
|
|
Linux for a while now, and chances are any questions you have not
|
|
answered by this document are answered in the archives.
|
|
</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="sect2"
|
|
><H2
|
|
CLASS="sect2"
|
|
><A
|
|
NAME="QuestionsandTroubleshooting-FlashBootFAQSection"
|
|
>9.15. Can One Boot a JavaStation from Onboard Flash Memory?</A
|
|
></H2
|
|
><P
|
|
> It is possible to boot a JavaStation-NC from flash, but requires
|
|
too much arcane knowledge at the moment to be recommended. One problem
|
|
even if you do go this route is that flash can only be mounted read-only.
|
|
This gets to be a problem with many things, like X, which require the
|
|
writing of socket files. A hybrid ramdisk/flash solution would be required.
|
|
</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="sect2"
|
|
><H2
|
|
CLASS="sect2"
|
|
><A
|
|
NAME="QuestionsandTroubleshooting-PiggybackOtherPlatform"
|
|
>9.16. Does <SPAN
|
|
CLASS="QUOTE"
|
|
>"Piggyback"</SPAN
|
|
> work for the <SPAN
|
|
CLASS="hardware"
|
|
>x86</SPAN
|
|
>
|
|
too?</A
|
|
></H2
|
|
><P
|
|
> With the great embedded-root solution for the JavaStations, the question
|
|
popped up whether something similar can be done for stock x86 hardware.
|
|
While there are some x86 NICs that have boot roms on them, you'd also need
|
|
the piggyback program to put things together. According to Eric Brower,
|
|
this currently is not possible as the piggyback program looks for a header
|
|
specific to the SPARC platform. (28-Apr-2000)
|
|
</P
|
|
><P
|
|
> Robert Thornburrow<TT
|
|
CLASS="email"
|
|
><<A
|
|
HREF="mailto:robert@tsac.fsnet.co.uk"
|
|
>robert@tsac.fsnet.co.uk</A
|
|
>></TT
|
|
> sent a version
|
|
of piggyback which runs on non-SPARCLinux architectures like Linux/x86
|
|
and Solaris. This automates the task of creating your embedded root
|
|
image. You can get his updated piggyback package at:
|
|
|
|
<A
|
|
HREF="http://dubinski-family.org/~jshowto/Files/tools/piggyback_nonsparc.tar.gz"
|
|
TARGET="_top"
|
|
> http://dubinski-family.org/~jshowto/Files/tools/piggyback_nonsparc.tar.gz
|
|
</A
|
|
>
|
|
</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="sect2"
|
|
><H2
|
|
CLASS="sect2"
|
|
><A
|
|
NAME="QuestionsandTroubleshooting-NotBootingWithNewMemorySection"
|
|
>9.17. I put new memory in, but now it doesn't boot. Why?</A
|
|
></H2
|
|
><P
|
|
> Are you using EDO memory by chance? Mr. Coffee uses fast-page memory
|
|
only, not EDO.
|
|
</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="sect2"
|
|
><H2
|
|
CLASS="sect2"
|
|
><A
|
|
NAME="QuestionsandTroubleshooting-AlternateOSSupport"
|
|
>9.18. Now that JavaStations work with Linux, what about other Free OSs?</A
|
|
></H2
|
|
><P
|
|
> JavaStation support is now available with the NetBSD OS as well as Linux.
|
|
</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="sect2"
|
|
><H2
|
|
CLASS="sect2"
|
|
><A
|
|
NAME="QuestionsandTroubleshooting-Linux24Support"
|
|
>9.19. Do the Linux 2.4 kernels work? What's the latest that works?</A
|
|
></H2
|
|
><P
|
|
> As of this date (Oct 31, 2001), the current stable Linux kernel version
|
|
is 2.4.13. Kernels in the stable 2.4 series <EM
|
|
>should</EM
|
|
>
|
|
work with the JavaStations, but there are a few reasons why they may not
|
|
work for you. For details, check the "Kernel Build" chapter's entry on
|
|
supported kernels.
|
|
</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="sect2"
|
|
><H2
|
|
CLASS="sect2"
|
|
><A
|
|
NAME="QuestionsandTroubleshooting-CrossCompileKernel"
|
|
>9.20. Can I compile the kernel on a non-SPARC machine?</A
|
|
></H2
|
|
><P
|
|
> It should be technically possible to compile your kernel on a
|
|
non Sun workstation, such as a PC. Currently there are no reports
|
|
of anyone doing this, but if you wanted, the first place to look is
|
|
the GCC CrossCompiling HOWTO.
|
|
</P
|
|
><P
|
|
> Of course, you can also compile a new kernel on a working JavaStation,
|
|
if your filesystem image supports it.
|
|
</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="sect2"
|
|
><H2
|
|
CLASS="sect2"
|
|
><A
|
|
NAME="QuestionsandTroubleshooting-OpenBootBreak"
|
|
>9.21. Can I get an ok> prompt like other Sun equipment?</A
|
|
></H2
|
|
><P
|
|
> A curious thing happens when you send a JavaStation a break: it resets,
|
|
not break down to the openboot prom prompt like other Sun equipment.
|
|
This can be changed on a Krups by setting jumper J1300, pins 7-8.
|
|
Doing this gets a OBP ok prompt with a Ctrl-Alt-Break on a PS/2 keyboard
|
|
or break through a serial terminal.
|
|
</P
|
|
><P
|
|
> You can also get the ok prompt on the Dover unit, but it requires a hardware
|
|
fix. To do so on this unit, you must solder a 220K ohm resistor in
|
|
location R362 (near the FDD connector).
|
|
</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="sect2"
|
|
><H2
|
|
CLASS="sect2"
|
|
><A
|
|
NAME="QuestionsandTroubleshooting-KeyboardTroubleshooting"
|
|
>9.22. My keyboard isn't recognized. What can I do?</A
|
|
></H2
|
|
><P
|
|
> While it's unlikely, it could be possible that you have a javastation
|
|
set in the wrong input device mode. To rectify this, you need to enable
|
|
the openboot prom prompt as described elsewhere in this HOWTO, and then
|
|
set the 'input-device' directive accordingly. Or, as one contributor
|
|
did before the OBP setting was discovered, load up NetBSD on your
|
|
JavaStation and run the eeprom command there. Convoluted, but it
|
|
works too.
|
|
</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="sect2"
|
|
><H2
|
|
CLASS="sect2"
|
|
><A
|
|
NAME="QuestionsandTroubleshooting-ProllARPTimeOut"
|
|
>9.23. Proll reports "TFTP: ARP Timeout". Why?</A
|
|
></H2
|
|
><P
|
|
> This has been reported to happen when the file PROLL looks for isn't
|
|
available. Doublecheck your configuration before retrying.
|
|
</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="sect2"
|
|
><H2
|
|
CLASS="sect2"
|
|
><A
|
|
NAME="QuestionsandTroubleshooting-TrueColorKrups"
|
|
>9.24. Why Can't I Get TrueColor on Krups?</A
|
|
></H2
|
|
><P
|
|
> Truecolor on Krups with Linux is a bit of a controversy. Some believe
|
|
it is possible, while others do not.
|
|
</P
|
|
><P
|
|
> First, the Krups is listed as having the IGS C1682 framebuffer, while
|
|
the Espresso has the IGS C2000 chip.
|
|
</P
|
|
><P
|
|
> According to an earlier report by one kernel hacker, the reason for Krups
|
|
not supporting TrueColor is due to lack of kernel support for the Cyber2000
|
|
chip. Perhaps the C2000 for the Espresso is the 'Cyber2000'? And perhaps
|
|
the C2000 is near equal to the C1682. Notes on the ZLS website seem
|
|
to point to this.
|
|
</P
|
|
><P
|
|
> Recent 2.4.x series kernels have an entry labeled 'Cyber2000'. Perhaps this
|
|
works? One contributor tried and failed.
|
|
</P
|
|
><P
|
|
> Ok, there is a userland utility called 'fbset' to change the modes of
|
|
a framebuffer. Does that work? One contributor said no.
|
|
</P
|
|
><P
|
|
> In the sparclinux archives is a report of a user using the 24-bit TCX
|
|
framebuffer and having success. But TCX chip was in Mr. Coffee, not
|
|
Krups, and TCX onboard Mr. Coffee had 8-bit max, not 24.
|
|
</P
|
|
><P
|
|
> So what is the real scoop with 24-bit color on the Krups? Until others
|
|
try things and speak up, we don't know.
|
|
</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="sect2"
|
|
><H2
|
|
CLASS="sect2"
|
|
><A
|
|
NAME="QuestionsandTroubleshooting-DoverHOWTO"
|
|
>9.25. I followed this HOWTO, but my Dover doesn't work. Why?</A
|
|
></H2
|
|
><P
|
|
> The Dover is not a SPARC-based JavaStation, which this HOWTO caters to.
|
|
You must use x86 procedures to make it work properly. You did read the
|
|
warning in the Dover introduction section, didn't you?
|
|
</P
|
|
><P
|
|
> I am receiving multiple reports of kernel load failures with the Dover unit.
|
|
As more information comes in, this HOWTO will present it.
|
|
</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="sect2"
|
|
><H2
|
|
CLASS="sect2"
|
|
><A
|
|
NAME="QuestionsandTroubleshooting-LoadXAfterSerial"
|
|
>9.26. Can framebuffer be loaded following a serial console initialization?</A
|
|
></H2
|
|
><P
|
|
> If you boot a JavaStation via the serial console, the framebuffer console
|
|
is completely disabled. Is there any way to activate the framebuffer console
|
|
after booting? (asked on Sparclinux mailing list 2001-05-11).
|
|
</P
|
|
><P
|
|
> Not to our knowledge.
|
|
</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="sect2"
|
|
><H2
|
|
CLASS="sect2"
|
|
><A
|
|
NAME="QuestionsandTroubleshooting-OutoftheBox"
|
|
>9.27. I really need a complete out-of-the-box solution, pronto!</A
|
|
></H2
|
|
><P
|
|
> You better get busy then.
|
|
</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="sect2"
|
|
><H2
|
|
CLASS="sect2"
|
|
><A
|
|
NAME="QuestionsandTroubleshooting-YouDidntAnswer"
|
|
>9.28. You Didn't Answer My Question.</A
|
|
></H2
|
|
><P
|
|
> So ask it. Email <TT
|
|
CLASS="email"
|
|
><<A
|
|
HREF="mailto:rsd@dubinski-family.org"
|
|
>rsd@dubinski-family.org</A
|
|
>></TT
|
|
> and I will
|
|
try to help. If I can not help, I will direct you to the mailing
|
|
lists or suitable contacts.
|
|
</P
|
|
></DIV
|
|
></DIV
|
|
><DIV
|
|
CLASS="NAVFOOTER"
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"><TABLE
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="javastationboot-bootyourjavastationchapter.html"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="index.html"
|
|
>Home</A
|
|
></TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="referencedocs-chapter.html"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
>Booting Your JavaStation</TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
> </TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
>Reference Docs</TD
|
|
></TR
|
|
></TABLE
|
|
></DIV
|
|
></BODY
|
|
></HTML
|
|
> |