ref: d153e5bc60fe181d1ddb382b5c19dfd21cdcb146
dir: /fqa9.ms/
.\" This troff source is processed to create all forms of the
.\" 9FRONT DASH 1 book and the http://fqa.9front.org website.
.\" NOTE: Purely experimental. Methods employed may change.
.\" troff -ms -mpictures fqa9.ms | page
.\" htmlroff -u -ms -mhtml fqa9.ms >fqa9.html
.de FG \" .FG <basename>
.ie h .html - <img src="\\$1.\\$2" />
.el .BP \\$1.ps
.br
..
.po 1i \" page offset (from left)
.fp 1 R LucidaSans
.fp 2 I LucidaSansI
.fp 3 B LucidaSansB
.fp 4 BI LucidaSansI
.fp 5 CW LucidaCW
.paragraph 0
.margin 0
.HTML "FQA 9 - Troubleshooting
.html - <style type="text/css">body{font-size:10pt}; a{font-size:10pt}</style>
.html - <a href="fqa.html">FQA INDEX</a> |
.html - <a href="fqa8.html">FQA 8 - Using 9front</a> |
.html - <a href="appendixb.html">FQA Appendix B - Bounties</a>
.html - <hr />
.SH
.LG
.ihtml h1 <h1>
FQA 9 - Troubleshooting
.ihtml h1
.NL
.R
.html - <a href="fqa9.html">html</a> |
.html - <a href="fqa9.pdf">pdf</a> |
.html - <a href="fqa9.ms">troff</a>
.FG methods jpg
.html - <a name="9.1" />
.ihtml h2 <h2>
.SH
9.1 - First
.R
.ihtml h2
.html - <br />
.FG sweat gif
.ihtml ul <ul>
.IP
• STATE YOUR ASSUMPTIONS.
•
.CW
cat /etc/os-release
.R
to verify you are not, in fact, running Ubuntu Linux with a Plan 9 theme.
• Are you running
.ihtml a <a href="http://drawterm.9front.org">
drawterm?
.ihtml a
• Verify your OpenBSD configuration.
• Are you using the
.CW qwerty
keyboard layout?
• Before reporting a bug, try the latest
.ihtml a <a href="fqa1.html#1.11.1">
ISO image.
.ihtml a
• MAKE SENSE.
• When all else fails, see:
.ihtml a <a href="fqa2.html#2.4">
.I
FQA 2.4 - Reporting Bugs
.R
.ihtml a
.LP
.ihtml ul
.FG yesno jpg
.html - <a name="9.2" />
.ihtml h2 <h2>
.SH
9.2 - Booting
.R
.ihtml h2
.html - <a name="9.2.1" />
.ihtml h3 <h3>
.SH
9.2.1 - Boot parameters
.R
.ihtml h3
.ihtml ul <ul>
.IP
• Immediately after the BIOS screen, hit any key until you see the
.CW >
prompt. From there, values from
.ihtml a <a href="http://man.9front.org/8/plan9.ini">
.CW plan9.ini
.ihtml a
may be temporarily added or changed. Read:
.ihtml a <a href="http://man.9front.org/8/9boot">
.CW 9boot(8)
.ihtml a
• Boot parameters beginning with a
.CW *
are interpreted by the kernel. All other parameters are passed as enviroment variables to the boot process.
• Adding or changing a parameter:
.CW param=value
• Removing a parameter:
.CW
clear param=
.R
• When finished, type
.CW boot
to resume booting.
.LP
.ihtml ul
.html - <a name="9.2.2" />
.ihtml h3 <h3>
.SH
9.2.2 - Break into a shell
.R
.ihtml h3
At the
.CW [bootargs]
prompt, type
.CW !rc
and hit enter to break into a shell. Type
.CW exit
to return to the
.CW [bootargs]
prompt.
.html - <a name="9.2.3" />
.ihtml h3 <h3>
.SH
9.2.3 - Editing plan9.ini
.R
.ihtml h3
.ihtml ul <ul>
.IP
• It is not possible to edit
.ihtml a <a href="http://man.9front.org/8/plan9.ini">
plan9.ini
.ihtml a
stored on the ISO, but parameters can be changed temporarily before booting. See above.
• On a harddrive installation,
.ihtml a <a href="http://man.9front.org/8/plan9.ini">
.CW plan9.ini
.ihtml a
is stored with the bootloader and the kernel in a small FAT partition called
.CW 9fat
at the beginning of the
.CW plan9
partition. The
.CW 9fat
can be mounted by executing
.CW
9fs 9fat
.R
from the livecd or the installed system. The file
.CW /n/9fat/plan9.ini
can then be edited with a text editor like
.ihtml a <a href="http://man.9front.org/1/acme">
.CW acme(1) ,
.ihtml a
.ihtml a <a href="http://man.9front.org/1/sam">
.CW sam(1)
.ihtml a
or
.ihtml a <a href="http://man.9front.org/1/ed">
.CW ed(1) .
.ihtml a
• If your change to
.ihtml a <a href="http://man.9front.org/8/plan9.ini">
.CW plan9.ini
.ihtml a
or the
.CW 9fat
made the system unbootable, it is always possible to manually override parameters on the
.CW >
prompt (see above) or start the system from the livecd and pick your installed
.CW cwfs
or
.CW hjfs
partition on the
.CW [bootargs]
prompt. Example:
.CW local!/dev/sdC0/fscache
.LP
.ihtml ul
.html - <a name="9.2.4" />
.ihtml h3 <h3>
.SH
9.2.4 - Boot media not recognized
.R
.ihtml h3
.ihtml ul <ul>
.IP
• Break into a shell, then type
.CW
grep -n '^01' '#$/pci/'*ctl
.R
to get the pci vid/did of the installed disk controllers. then look in the sd drivers to see if the controller is already recognized.
• Sometimes, there is a problem with the drive, not the controller.
.CW
cat /dev/sd*/ctl
.R
to get the status of the individual drives.
• Try different BIOS settings like AHCI/IDE mode.
• Try the USB troubleshooting steps (see below). Sometimes USB problems prevent unrelated devices from working properly.
.LP
.ihtml ul
.html - <a name="9.2.5" />
.ihtml h3 <h3>
.SH
9.2.5 - I moved my hard drive between ports
.R
.ihtml h3
If your file system is
.ihtml a <a href="http://man.9front.org/4/cwfs">
.CW cwfs(4) :
.ihtml a
.ihtml ul <ul>
.IP
• Let's assume it went from sdE0 to sdE1.
• At the bootargs prompt:
.P1
local!/dev/sdE1/fscache -c
filsys main c(/dev/sdE1/fscache)(/dev/sdE1/fsworm)
filsys dump o
filsys other /dev/sdE1/other
end
.P2
.LP
.ihtml ul
.bp
.html - <a name="9.3" />
.ihtml h2 <h2>
.SH
9.3 - Graphics
.R
.ihtml h2
.html - <a name="9.3.1" />
.ihtml h3 <h3>
.SH
9.3.1 - Rio fails to start
.R
.ihtml h3
See the discussion of graphics in
.ihtml a <a href="fqa4.html">
.I
FQA 4 - 9front Installation Guide.
.R
.ihtml a
When you find a working mode, update your
.ihtml a <a href="http://man.9front.org/8/plan9.ini">
.CW plan9.ini .
.ihtml a
.html - <a name="9.3.2" />
.ihtml h3 <h3>
.SH
9.3.2 - VESA BIOS does not contain a valid mode
.R
.ihtml h3
The standard solution is to have the customer send the computer back to the manufacturer, who reflashes the EEPROM with the correct information and return the computer to the customer.
.html - <a name="9.4" />
.ihtml h2 <h2>
.SH
9.4 - Networking
.R
.ihtml h2
.html - <a name="9.4.1" />
.ihtml h3 <h3>
.SH
9.4.1 - Networking is not working
.R
.ihtml h3
Read:
.ihtml a <a href="fqa6.html#6.2.8">
.I
FQA 6.2.8 - Verifying network settings
.R
.ihtml a
.html - <a name="9.4.2" />
.ihtml h3 <h3>
.SH
9.4.2 - Cannot resolve domain names
.R
.ihtml h3
If
.CW ndb/dns
is running but you are still unable to resolve domains, you can try adding a DNS server directly to
.CW /net/ndb .
Read:
.ihtml a <a href="fqa6.html#6.2.5">
.I
FQA 6.2.5 - DNS Resolution
.R
.ihtml a
.html - <a name="9.4.3" />
.ihtml h3 <h3>
.SH
9.4.3 - /mnt/web/clone does not exist
.R
.ihtml h3
Programs that require
.ihtml a <a href="http://man.9front.org/4/webfs">
.CW webfs(4)
.ihtml a
to be running require
.ihtml a <a href="http://man.9front.org/4/webfs">
.CW webfs(4)
.ihtml a
to be running.
Read:
.ihtml a <a href="http://man.9front.org/1/hget">
.CW hget(1) ,
.ihtml a <a href="http://man.9front.org/1/mothra">
.CW mothra(1)
.ihtml a
.html - <a name="9.4.4" />
.ihtml h3 <h3>
.SH
9.4.4 - PCMCIA WiFi stopped working after reboot
.R
.ihtml h3
Do
.CW fshalt
and power down completely instead of just rebooting with \f(CWfshalt -r\fR.
.html - <a name="9.5" />
.ihtml h2 <h2>
.SH
9.5 - USB
.R
.ihtml h2
.html - <a name="9.5.1" />
.ihtml h3 <h3>
.SH
9.5.1 - Devices not recognized or not working
.R
.ihtml h3
.ihtml ul <ul>
.IP
• Break into a shell, or simply type in a
.CW rio
window:
.CW
cat /dev/usbevent
.R
and try plugging in a USB device. If the devices where detected, some output should appear on screen. This doesnt mean we have a working driver for it but verifies that the USB controller and HUB driver recognized the device.
• Dump USB controller status to the console with
.CW
echo dump >/dev/usb/ctl
.R
after that, you might recover the output from
.CW /dev/kmesg
or run
.CW
cat /dev/kprint
.R
in a separate rio window to not spill it all over the screen. Check the
.CW nintr
and
.CW tdintr
counters to see if they are all zero. If thats the case, then this is might be a interrupt routing problem sometimes caused by broken/incomplete BIOS MP tables. See below.
• If USB keyboard is the only option, try to enable PS2 emulation in the BIOS and disable kernel usb support. See below.
• if the machine employs a USB3.0 (xHCI) controller, try to disable USB3.0 support in BIOS as the driver may not support your chipset yet.
.LP
.ihtml ul
.html - <a name="9.5.2" />
.ihtml h3 <h3>
.SH
9.5.2 - System freezes after showing memory sizes
.R
.ihtml h3
.ihtml ul <ul>
.IP
• The boot parameter
.CW *acpi=1
might solve interrupt routing problems in the case of broken or incomplete BIOS MP tables. (acpi is still experimental)
• Try the boot parameter
.CW *nomp=
to disable multiprocessor mode.
• Try the boot parameter
.CW *nousbehci=
(This disables USB 2.0.)
• Try the boot parameter
.CW *nousbuhci=
• Try the boot parameter
.CW *nousbohci=
• Try the boot parameter
.CW *nousbprobe=
(This disables USB completely)
.LP
.ihtml ul
.html - <a name="9.6" />
.ihtml h2 <h2>
.SH
9.6 - auth
.R
This space left intentionally blank.
.ihtml h2
.bp
.html - <a name="9.99999999999999999999999999999999999999" />
.ihtml h2 <h2>
.SH
9.99999999999999999999999999999999999999 - GIVE UP
.R
.ihtml h2
Give up now.
Go away.
.FG giveup1 jpg
.FG giveup2 jpg
.DS
.I
Every joke is a tiny revolution
.R
\(em George Orwell
.DE
.html - <hr />
.html - <a href="fqa.html">FQA INDEX</a> |
.html - <a href="fqa8.html">FQA 8 - Using 9front</a> |
.html - <a href="appendixb.html">FQA Appendix B - Bounties</a>