Trouble getting started.....

[Antony Stone]

Hi.

Can somebody tell me what I'm missing here please ?   I've just started with 
LinuxBios after seeing it at the LBW workshop ten days ago, and I can't seem 
to get even to stage 1....

I have a PCChips M810LR motherboard, and I've fitted a ZIF socket to swap the 
flash Bios for a Millennium MD-2800-D08 DoC device.

I've compiled a 2.4.19 kernel and modules (although I'm not sure I've done 
this correctly - I can't find any instructions on which MTD options I need to 
make this setup work), and rebooted with the new kernel.

I've built the various tools I seem to need for the SiS-based motherboard.

When I do this:

1. Remove Flash Bios
2. Insert DoC (brand new device, just purchased)
3. flash_on
4. modprobe doc2001
5. modprobe docprobe
6. dmesg

I get this:

Possible DiskOnChip with unknown ChipID 00 found at 0xc8000
Possible DiskOnChip with unknown ChipID 35 found at 0xca000
Possible DiskOnChip with unknown ChipID F6 found at 0xcc000
Possible DiskOnChip with unknown ChipID E8 found at 0xce000
Possible DiskOnChip with unknown ChipID 97 found at 0xd0000
Possible DiskOnChip with unknown ChipID 63 found at 0xd2000
Possible DiskOnChip with unknown ChipID FF found at 0xd4000
Possible DiskOnChip with unknown ChipID FF found at 0xd6000
Possible DiskOnChip with unknown ChipID FF found at 0xd8000
Possible DiskOnChip with unknown ChipID FF found at 0xda000
Possible DiskOnChip with unknown ChipID FF found at 0xdc000
Possible DiskOnChip with unknown ChipID FF found at 0xde000
Possible DiskOnChip with unknown ChipID FF found at 0xe0000
Possible DiskOnChip with unknown ChipID FF found at 0xe2000
Possible DiskOnChip with unknown ChipID FF found at 0xe4000
Possible DiskOnChip with unknown ChipID FF found at 0xe6000
Possible DiskOnChip with unknown ChipID FF found at 0xe8000
Possible DiskOnChip with unknown ChipID FF found at 0xea000
Possible DiskOnChip with unknown ChipID FF found at 0xec000
Possible DiskOnChip with unknown ChipID FF found at 0xee000
No recognised DiskOnChip devices found

I *am* inserting the DoC the right way round :-)

My /dev/mtd0 is a char device with major/minor node 90,0

Can someone suggest which I'm doing wrong, what I've missed out, or where I 
can look for instructions to get it right ?

Thanks,

Antony.

Here are the relevant sections of the .config options I compiled my kernel 
with:

#
# Memory Technology Devices (MTD)
#
CONFIG_MTD=m
# CONFIG_MTD_DEBUG is not set
# CONFIG_MTD_PARTITIONS is not set
# CONFIG_MTD_CONCAT is not set
# CONFIG_MTD_REDBOOT_PARTS is not set
CONFIG_MTD_CHAR=m
CONFIG_MTD_BLOCK=m
# CONFIG_MTD_BLOCK_RO is not set
CONFIG_FTL=m
CONFIG_NFTL=m
CONFIG_NFTL_RW=y

#
# RAM/ROM/Flash chip drivers
#
CONFIG_MTD_CFI=m
CONFIG_MTD_JEDECPROBE=m
CONFIG_MTD_GEN_PROBE=m
# CONFIG_MTD_CFI_ADV_OPTIONS is not set
# CONFIG_MTD_CFI_INTELEXT is not set
# CONFIG_MTD_CFI_AMDSTD is not set
# CONFIG_MTD_RAM is not set
# CONFIG_MTD_ROM is not set
# CONFIG_MTD_ABSENT is not set
# CONFIG_MTD_OBSOLETE_CHIPS is not set
# CONFIG_MTD_AMDSTD is not set
# CONFIG_MTD_SHARP is not set
# CONFIG_MTD_JEDEC is not set

#
# Mapping drivers for chip access
#
# CONFIG_MTD_PHYSMAP is not set
# CONFIG_MTD_PNC2000 is not set
# CONFIG_MTD_SC520CDP is not set
# CONFIG_MTD_NETSC520 is not set
# CONFIG_MTD_SBC_GXX is not set
# CONFIG_MTD_ELAN_104NC is not set
# CONFIG_MTD_DILNETPC is not set
# CONFIG_MTD_MIXMEM is not set
# CONFIG_MTD_OCTAGON is not set
# CONFIG_MTD_VMAX is not set
# CONFIG_MTD_L440GX is not set
# CONFIG_MTD_AMD766ROM is not set
# CONFIG_MTD_ICH2ROM is not set
# CONFIG_MTD_PCI is not set

#
# Self-contained MTD device drivers
#
# CONFIG_MTD_PMC551 is not set
# CONFIG_MTD_SLRAM is not set
# CONFIG_MTD_MTDRAM is not set
# CONFIG_MTD_BLKMTD is not set
# CONFIG_MTD_DOC1000 is not set
CONFIG_MTD_DOC2000=m
CONFIG_MTD_DOC2001=m
CONFIG_MTD_DOCPROBE=m
# CONFIG_MTD_DOCPROBE_ADVANCED is not set
CONFIG_MTD_DOCPROBE_ADDRESS=0
# CONFIG_MTD_DOCPROBE_HIGH is not set
# CONFIG_MTD_DOCPROBE_55AA is not set

#
# NAND Flash Device Drivers
#
# CONFIG_MTD_NAND is not set

# Linuxbios Options
#
CONFIG_LINUXBIOS_PM=y
CONFIG_LINUXBIOS_PM_SIS503=y
# CONFIG_LINUXBIOS_PM_PIIX4E is not set

[Andrew Ip]

Antony,
> Can someone suggest which I'm doing wrong, what I've missed out, or where I 
> can look for instructions to get it right ?
> # CONFIG_MTD_DOCPROBE_HIGH is not set

You may either need to enable docprobe high or type
$ flash_on
$ modprobe docprobe doc_config_location=0xfffc8000

-Andrew

[Antony Stone]

On Saturday 07 September 2002 12:49 pm, Andrew Ip wrote:
> Antony,
> > Can someone suggest which I'm doing wrong, what I've missed out, or where
> > I can look for instructions to get it right ?
> > # CONFIG_MTD_DOCPROBE_HIGH is not set
>
> You may either need to enable docprobe high or type
> $ flash_on
> $ modprobe docprobe doc_config_location=0xfffc8000

Thanks for that.   It's now working, and I've booted a kernel from DoC :-)

Now to figure out how to get the keyboard working.....

Incidentally, I noticed that the SiS config file for the 2.4.17 kernel was 
bigger than the config file for 2.4.19.   So I looked at both, and found the 
MTD options I needed were in the 2.4.17 config file, whereas the 2.4.19 one 
which I'd started with has MTD turned off !

Maybe whoever maintains these config files could check that the 2.4.19 
version is sensible/useful ?   Leaving out the MTD stuff seems a bit odd to 
me...

Anyway, thanks for the help.

Antony.

[Ronald G Minnich]

Thanks for the tip on the kernel config Antony. I will look at that too.

What's wrong with the keyboard? No output at all?

ron

[Steve M. Gehlbach]

I suspect Antony needs either "kbd-reset" on the kernel command line or
"keyboard=1" in the nsuperio line in mainboard/Config.

-Steve
> -----Original Message-----
> From: [e-mail]
> [mailto:[e-mail]]On Behalf Of Ronald G Minnich
> Sent: Saturday, September 07, 2002 8:25 AM
> To: Antony Stone
> Cc: [e-mail]
> Subject: Re: Trouble getting started.....
>
> Thanks for the tip on the kernel config Antony. I will look at that too.
>
> What's wrong with the keyboard? No output at all?
>
> ron
>
> Linuxbios mailing list
> [e-mail]
> http://www.clustermatic.org/mailman/listinfo/linuxbios

[Antony Stone]

On Saturday 07 September 2002 5:16 pm, Steve M. Gehlbach wrote:
> I suspect Antony needs either "kbd-reset" on the kernel command line or
> "keyboard=1" in the nsuperio line in mainboard/Config.

Thanks for the suggestions Steve, but no, neither of those (not even both 
together) worked.

In response to Ronald's question:
> What's wrong with the keyboard? No output at all?

There are two problems:

1. Several hundred messages at boot time saying:
pc_keyb: controller jammed (0xFF)

The messages stop after a while and the system decides there's no keyboard 
attached....

2. Keyboard completely non-functional.   Even pressing numlock doesn't toggle 
the light.

However, for the purpose I'm interested in I'm nottoo bothered about the 
keyboard, and I've now got my system to the stage where it boots a kernel 
from DoC, allows me to log on from the serial port, and successfully 
initialises a wireless LAN card I have on the PCI bus, so I can also ssh in 
from my laptop (I use this machine as an access point for my home network).

The biggest thing I'm trying to fix now is the onboard ethernet interface 
(SiS900) which the standard kernel driver tells me (from dmesg):
sis900.c: v1.08.04 4/25/2002
PCI: Found IRQ 5 for device 00:01.1
PCI: Sharing IRQ 5 with 00:01.6
eth0: No MII transceivers found!

Under the normal Bios boot, the same driver gives me:
sis900.c: v1.08.04 4/25/2002
PCI: Found IRQ 12 for device 00:01.1
eth0: Realtek RTL8201 PHY transceiver found at address 1.
eth0: Using transceiver found at address 1 as default
eth0: SiS 900 PCI Fast Ethernet at 0xd400, IRQ 12, 00:07:95:e2:c0:b6

The motherboard is a PCChips M810LMR.

Any ideas about this ?

Antony.

[Antony Stone]

On Saturday 07 September 2002 6:03 pm, Antony Stone wrote:
> On Saturday 07 September 2002 5:16 pm, Steve M. Gehlbach wrote:
> > I suspect Antony needs either "kbd-reset" on the kernel command line or
> > "keyboard=1" in the nsuperio line in mainboard/Config.
>
> Thanks for the suggestions Steve, but no, neither of those (not even both
> together) worked.

Just in case it helps, I spotted the NO_KEYBOARD option in some of the other 
motherboard config files, so I thought "if it's not going to work, I may as 
well disable it, then it won't waste time trying to get it working", so I put

option NO_KEYBOARD=1

into my config file, built a new image and re-flashed it, but I still get 
exactly the same several hundred "pc_keyb: controller jammed (0xFF)" messages 
at startup.

However, I have noticed a discrepancy between the box the motherboard came in 
and the manual which was with it, and although I said previously that it was 
a PC-Chips M810LMR, the manual says it's actually an M810LR - if there's any 
other info I can provide to pin down whether this is significant please let 
me know.
> The biggest thing I'm trying to fix now is the onboard ethernet interface
> (SiS900) which the standard kernel driver tells me (from dmesg):
> sis900.c: v1.08.04 4/25/2002
> PCI: Found IRQ 5 for device 00:01.1
> PCI: Sharing IRQ 5 with 00:01.6
> eth0: No MII transceivers found!
>
> Under the normal Bios boot, the same driver gives me:
> sis900.c: v1.08.04 4/25/2002
> PCI: Found IRQ 12 for device 00:01.1
> eth0: Realtek RTL8201 PHY transceiver found at address 1.
> eth0: Using transceiver found at address 1 as default
> eth0: SiS 900 PCI Fast Ethernet at 0xd400, IRQ 12, 00:07:95:e2:c0:b6

Antony.

[Ronald G Minnich]

On Sat, 7 Sep 2002, Steve M. Gehlbach wrote:
> I suspect Antony needs either "kbd-reset" on the kernel command line or
> "keyboard=1" in the nsuperio line in mainboard/Config.

we don't typically put that in mainboard/config because not all setups
want the keyboard enabled. It should be in the config for a given build.

But that's confusing. I wish for systems like the m801lmr we had configs
called "desktop.example" or some such.

ron

[ollie lho]

On Sat, 2002-09-07 at 20:13, Antony Stone wrote:
> Incidentally, I noticed that the SiS config file for the 2.4.17 kernel was 
> bigger than the config file for 2.4.19.   So I looked at both, and found the 
> MTD options I needed were in the 2.4.17 config file, whereas the 2.4.19 one 
> which I'd started with has MTD turned off !
>
> Maybe whoever maintains these config files could check that the 2.4.19 
> version is sensible/useful ?   Leaving out the MTD stuff seems a bit odd to 
> me...

The reason that the MTD stuff is not enabled is we (SiS) has dropped DoC
Millennium as our flash device/root filesysten. We turn to 256kB EEPROM
and use Etherboot to load kernel from IDE Disk or Compact Flash.

Ollie

[Ronald G Minnich]

you are very close. The DoC is very frustrating and has caused trouble for
MTD (just ask David Woodhouse :-)

You need to NOT use the "single driver" mode of DoC.

So my config looks like this for the kernel
#
# Self-contained MTD device drivers
#
# CONFIG_MTD_PMC551 is not set
# CONFIG_MTD_SLRAM is not set
# CONFIG_MTD_MTDRAM is not set
# CONFIG_MTD_DOC1000 is not set
# CONFIG_MTD_DOC2000 is not set
CONFIG_MTD_DOC2001=m
CONFIG_MTD_DOCPROBE=m
CONFIG_MTD_DOCPROBE_ADVANCED=y
CONFIG_MTD_DOCPROBE_ADDRESS=0000
CONFIG_MTD_DOCPROBE_HIGH=y
# CONFIG_MTD_DOCPROBE_55AA is not set

And you need to UNDEFINE DOC_SINGLE_DRIVER in docprobe.c

See the HOWTO /root/src/freebios/HOWTO/ALIM1631_M1535D

for more info.

Also, if you end up writing notes for the M810 and your kernel, and you
want to send them to me, I will post them. This process is still a
headache for new guys, and if you have hints for making it better I'll
take them too.

Thanks for your patience.

ron

[ollie lho]

On Sat, 2002-09-07 at 18:58, Antony Stone wrote:
> Hi.
>
> Can somebody tell me what I'm missing here please ?   I've just started with 
> LinuxBios after seeing it at the LBW workshop ten days ago, and I can't seem 
> to get even to stage 1....

LBW, is it the one that with mountain climbing and beer ??
> When I do this:
> Remove Flash Bios
> Insert DoC (brand new device, just purchased)
> flash_on
> modprobe doc2001
> modprobe docprobe
> dmesg
>
> I get this:
>
> Possible DiskOnChip with unknown ChipID 00 found at 0xc8000
> Possible DiskOnChip with unknown ChipID 35 found at 0xca000
> Possible DiskOnChip with unknown ChipID F6 found at 0xcc000
> Possible DiskOnChip with unknown ChipID E8 found at 0xce000
> Possible DiskOnChip with unknown ChipID 97 found at 0xd0000
> Possible DiskOnChip with unknown ChipID 63 found at 0xd2000
> Possible DiskOnChip with unknown ChipID FF found at 0xd4000
> Possible DiskOnChip with unknown ChipID FF found at 0xd6000
> Possible DiskOnChip with unknown ChipID FF found at 0xd8000
> Possible DiskOnChip with unknown ChipID FF found at 0xda000
> Possible DiskOnChip with unknown ChipID FF found at 0xdc000
> Possible DiskOnChip with unknown ChipID FF found at 0xde000
> Possible DiskOnChip with unknown ChipID FF found at 0xe0000
> Possible DiskOnChip with unknown ChipID FF found at 0xe2000
> Possible DiskOnChip with unknown ChipID FF found at 0xe4000
> Possible DiskOnChip with unknown ChipID FF found at 0xe6000
> Possible DiskOnChip with unknown ChipID FF found at 0xe8000
> Possible DiskOnChip with unknown ChipID FF found at 0xea000
> Possible DiskOnChip with unknown ChipID FF found at 0xec000
> Possible DiskOnChip with unknown ChipID FF found at 0xee000
> No recognised DiskOnChip devices found

I don't use DoC for a long time but I believe you need to enable the
"probe advance" and "probe high" options.

Ollie

[Antony Stone]

On Monday 09 September 2002 2:02 am, ollie lho wrote:
> On Sat, 2002-09-07 at 18:58, Antony Stone wrote:
> > Hi.
> >
> > Can somebody tell me what I'm missing here please ?   I've just started
> > with LinuxBios after seeing it at the LBW workshop ten days ago, and I
> > can't seem to get even to stage 1....
>
> LBW, is it the one that with mountain climbing and beer ??

Yes, that's it :-)   We get together every year in a different European 
country, and this year we had a LinuxBios workshop during the week, which 
resulted in a working DoC boot on an SiS motherboard.
> > Possible DiskOnChip with unknown ChipID FF found at 0xee000
> > No recognised DiskOnChip devices found
>
> I don't use DoC for a long time but I believe you need to enable the
> "probe advance" and "probe high" options.

Yes, that was the problem.   Ron already gave me some help with this, and now 
less than 48 hours after getting a DoC device I have a working system booting 
from DoC (including the IDE power-on spin-up patch to make sure cold boots 
work too).

Thanks for the help.

Antony.