networkstation-developers — Porting Linux and related applications to the NetworkStation

Re: [nwst-dev] kernel not booting

[Geltmar B. <ge...@gm...>]

Hi Vlok,

if your dhcp anf nfs stuff is allright, the complicated bits are already 
done.


Am 14.06.2004 um 22:45 schrieb vlok stone:

>Hi and Thank You, Still can't boot. Error msg =  kernel panic no init
>found. try passing init= to kernel. it does mount nfs. so that's good.
>I think I need to know how to build the root fs and where it goes.

At http://networkstation.aytolacoruna.es/ you will find four files,
each starting with "woody". Each contains a basic linux file system,
which should get you started.
Download one of them and unpack it to the location where your
kernel command line expects it. This should be
/NetworkStationV2/prodbase/linuxppc
in your case, if you use the kernel.1000 from the same page.
Once this boots, you have got the debian apt tools to install all
the stuff you want to (i.e. use deselect)

>What does your root fs look like. Or how I pass init= to the kernel (
>and which kernel do I pass it to? kernel.1000?)

As far as I understand it, you can't pass arguments to the kernel,
as the firmware of the networkstation boots it and there is no such thing
as lilo, grub, bootX, colo or any other bootloader. So it is compiled into
the kernel.

thanks again in advance. I got the kernel and config file from coruna.
just having trouble w/ initial console.

Vlok

Hope to get you started with this. X11 config would be next. I can't 
remember
if it worked out of the box. But I have a working config to help you with.

Greetings

Geltmar


-- 
+++ Jetzt WLAN-Router für alle DSL-Einsteiger und Wechsler +++
GMX DSL-Powertarife zudem 3 Monate gratis* http://www.gmx.net/dsl

[nwst-dev] kernel not booting

[vlok s. <iv...@ve...>]

Hi and Thank You, Still can't boot. Error msg =  kernel panic no init
found. try passing init= to kernel. it does mount nfs. so that's good. 
I think I need to know how to build the root fs and where it goes. 
What does your root fs look like. Or how I pass init= to the kernel (
and which kernel do I pass it to? kernel.1000?)
thanks again in advance. I got the kernel and config file from coruna.
just having trouble w/ initial console. 

Vlok


Hi again,
 
 I am not sure what is going wrong with your setup.
 Enclosed you will find the bits, which work for me.
 
 ###########
 The relevant bits during startup look like this:
 
 Linux version 2.4.21 (root@debian) (gcc version 2.95.4 20011002 (Debian
 prerelease)) #2 Tue Aug 5 23:25:22 CEST 2003
 ...
 Kernel command line: console=ttyS0,9600 console=tty0 root=/dev/nfs
 nfsroot=/home/NetworkStation ip=dhcp
 ...
 Sending DHCP requests ., OK
 IP-Config: Got DHCP answer from 10.0.1.100, my address is 10.0.1.50
 IP-Config: Complete:
       device=eth0, addr=10.0.1.50, mask=255.255.255.0, gw=10.0.1.1,
      host=10.0.1.50, domain=buxhoeveden.net, nis-domain=(none),
      bootserver=10.0.1.100, rootserver=10.0.1.100, rootpath=
 NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
 Looking up port of RPC 100003/2 on 10.0.1.100
 Looking up port of RPC 100005/1 on 10.0.1.100
 VFS: Mounted root (nfs filesystem).
 Freeing unused kernel memory: 136k init 36k pmac 8k chrp 4k openfirmware
 ############
 
 #/etc/exports on the computer that acts as dhcp and nfs server:
 
 /netstation/prodbase	10.0.1.50(rw)	#that is where my kernel.1000 lives
 /home/NeworkStation		10.0.1.50(rw,no_root_squash) # that is root i.e. "/"
 for the Netstation
 /home/geltmar			10.0.1.50(rw)	#my home directory on the server
 #############
 
 #/etc/hosts.allow on dhcp/nfs server
 
 ALL: 10.0.1.*
 #############
 
 #/etc/dhcp3/dhcpd.conf on dhcp/nfs server
 
 option domain-name "buxhoeveden.net";
 option name-name-servers 145.253.2.11;
 default-lease-time 600;
 max-lease-time 7200;
 
 host netstation {
 	hardware ethernet 0:0:a7:24:17:4b;
 	fixed-address 10.0.1.50;
 	filename "kernel.1000";
 	server-name "10.0.1.100";
 }
 
 the filename "kernel.1000" is
 probably not necessary, if you configure the NVRAM in the netstation itself
 ???
 to boot a kernel from a specified location,
 but the kernel is configured to use dhcp for an IP, so I guess it is needed
 in the
 second phase of booting to get the nfs stuff running.
 #############
 
 My kernel is 2.2.21 self compiled, as I had to change the
 nfsroot=/home/Networkstation bit
 for the kernel command line. Other changes are, that I compiled drivers for
 the
 parallel port as modules to keep the kernel small, as I don"t use a printer.
 
 Have a look in /var/log/syslog et al on your dhcp server and try to find outJun 14 15:55:53 localhost rpc.mountd: authenticated mount request from 192.168.1.102:608 for /netstation/Prodbase (/netstation)

 mounting nfs works. I used to get "permission denied for..." errors by the
 nfs server,

nfs gets mounted , but the weird thing is this 


 how farJun 14 15:55:08 localhost rpc.mountd: authenticated mount request from 192.168.1.102:1023 for /netstation/Prodbase (/netstation)
Jun 14 15:55:09 localhost rpc.mountd: authenticated unmount request from 192.168.1.102:1023 for /netstation/Prodbase (/netstation)
Jun 14 15:55:20 localhost rpc.mountd: authenticated mount request from 192.168.1.102:604 for /NetworkStationV2/prodbase/linuxppc (/NetworkStationV2/prodbase/linuxppc)
Jun 14 15:55:21 localhost rpc.mountd: authenticated mount request from 192.168.1.102:608 for /netstation/Prodbase (/netstation)
Jun 14 15:55:41 localhost rpc.mountd: authenticated mount request from 192.168.1.102:1023 for /netstation/Prodbase (/netstation)
Jun 14 15:55:41 localhost rpc.mountd: authenticated unmount request from 192.168.1.102:1023 for /netstation/Prodbase (/netstation)
Jun 14 15:55:53 localhost rpc.mountd: authenticated mount request from 192.168.1.102:604 for /NetworkStationV2/prodbase/linuxppc (/NetworkStationV2/prodbase/linuxppc)

does it have to mount on 1023? Which it does w/ the regular kernel.63a


 if the IP address of the Networkstation and the lines in /etc/exports did
 not match.
 
 Did you have a working 2.4.19 kernel, as another user reported and it
 stopped
 working once you switched to 2.4.21? Or did the station not boot at all?

the regular kernel.63a boot fine. but I want to get the sound going :-)  

 No I never tried the 2.4.19. 

 Maybe having the kernel "ouside" nfsroot as in my configuration is
 necessary, I am not sure?
 I had to move nfsroot to a disk partition with more space so I ended up with
 this configuration.
 
 Maybe you can find any differences to your configuration.
 
 Good luck
 
 Geltmar

[nwst-dev] Working config for kernel 2.4.21

[Geltmar B. <ge...@gm...>]

Hi again,

I am not sure what is going wrong with your setup.
Enclosed you will find the bits, which work for me.

###########
The relevant bits during startup look like this:

Linux version 2.4.21 (root@debian) (gcc version 2.95.4 20011002 (Debian
prerelease)) #2 Tue Aug 5 23:25:22 CEST 2003
...
Kernel command line: console=ttyS0,9600 console=tty0 root=/dev/nfs
nfsroot=/home/NetworkStation ip=dhcp
...
Sending DHCP requests ., OK
IP-Config: Got DHCP answer from 10.0.1.100, my address is 10.0.1.50
IP-Config: Complete:
      device=eth0, addr=10.0.1.50, mask=255.255.255.0, gw=10.0.1.1,
     host=10.0.1.50, domain=buxhoeveden.net, nis-domain=(none),
     bootserver=10.0.1.100, rootserver=10.0.1.100, rootpath=
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Looking up port of RPC 100003/2 on 10.0.1.100
Looking up port of RPC 100005/1 on 10.0.1.100
VFS: Mounted root (nfs filesystem).
Freeing unused kernel memory: 136k init 36k pmac 8k chrp 4k openfirmware
############

#/etc/exports on the computer that acts as dhcp and nfs server:

/netstation/prodbase	10.0.1.50(rw)	#that is where my kernel.1000 lives
/home/NeworkStation		10.0.1.50(rw,no_root_squash) # that is root i.e. "/"
for the Netstation
/home/geltmar			10.0.1.50(rw)	#my home directory on the server
#############

#/etc/hosts.allow on dhcp/nfs server

ALL: 10.0.1.*
#############

#/etc/dhcp3/dhcpd.conf on dhcp/nfs server

option domain-name "buxhoeveden.net";
option name-name-servers 145.253.2.11;
default-lease-time 600;
max-lease-time 7200;

host netstation {
	hardware ethernet 0:0:a7:24:17:4b;
	fixed-address 10.0.1.50;
	filename "kernel.1000";
	server-name "10.0.1.100";
}

the filename "kernel.1000" is
probably not necessary, if you configure the NVRAM in the netstation itself
???
to boot a kernel from a specified location,
but the kernel is configured to use dhcp for an IP, so I guess it is needed
in the
second phase of booting to get the nfs stuff running.
#############

My kernel is 2.2.21 self compiled, as I had to change the
nfsroot=/home/Networkstation bit
for the kernel command line. Other changes are, that I compiled drivers for
the
parallel port as modules to keep the kernel small, as I don't use a printer.

Have a look in /var/log/syslog et al on your dhcp server and try to find out
how far
mounting nfs works. I used to get "permission denied for..." errors by the
nfs server,
if the IP address of the Networkstation and the lines in /etc/exports did
not match.

Did you have a working 2.4.19 kernel, as another user reported and it
stopped
working once you switched to 2.4.21? Or did the station not boot at all?

Maybe having the kernel "ouside" nfsroot as in my configuration is
necessary, I am not sure?
I had to move nfsroot to a disk partition with more space so I ended up with
this configuration.

Maybe you can find any differences to your configuration.

Good luck

Geltmar


-- 
+++ Jetzt WLAN-Router für alle DSL-Einsteiger und Wechsler +++
GMX DSL-Powertarife zudem 3 Monate gratis* http://www.gmx.net/dsl

[nwst-dev] can't boot kernel.1000

[vlok s. <iv...@ve...>]

Hi thanks for replying. I downloaded kernel.1000 ( 2.4.21)  I get to
start booting, but then crashes w/ nkernel panic no init found. How do I
pass the necessary parameters to this kernel. I created a /NetstationV2/
direcory and it mounts that then craps out. Any ideas? 

Vlok
-- 
vlok stone <iv...@ve...>

Re: [nwst-dev] is this list still active?

[Geltmar B. <ge...@gm...>]

Hm? I am on the list as well. It is quiet ans I am non of the 
developers,
but I have a networkstation running with kernel 2.4.19 and some
experience with ppc (i.e. linux on mac) and diskless configurations.
So just ask and I will do my best to answer.

Geltmar

Am 08.06.2004 um 16:51 schrieb Vlok Stone:

> just checking to see if this project is alive. i'm having porblems.
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: GNOME Foundation
> Hackers Unite!  GUADEC: The world's #1 Open Source Desktop Event.
> GNOME Users and Developers European Conference, 28-30th June in Norway
> http://2004/guadec.org
> _______________________________________________
> Networkstation-developers mailing list
> Net...@li...
> https://lists.sourceforge.net/lists/listinfo/networkstation-developers
>

[nwst-dev] is this list still active?

[Vlok S. <iv...@ve...>]

just checking to see if this project is alive. i'm having porblems.

[nwst-dev] Network Station 8362-A53 for Sale

[Timo A. H. <ti...@ti...>]

My network station is for sale:

http://cgi.ebay.de/ws/eBayISAPI.dll?ViewItem&item=3058040870&category=8075&rd=1

Sorry but I can't participate in this project any further - but I wish you
(us) a good project. Maybe I'll join later again, but currently, I'm
pretty busy with my life so I can't help you out any further :(

best regards,
 Timo

[nwst-dev] Can boot 2.4.19, cannot boot 2.4.21, other misc. issues

[J.P. L. <pi...@el...>]

Hello,

I own a Network Station 1000, model 8362-A53, with 64MB of RAM and no
PC Card carrier installed.  There is a module in the cache slot,
however the boot monitor reports L2 cache failure in the "view
hardware configuration" screen.  It's running version 3.1.1.0 of the
boot monitor.

I'm new to the list, and by no means a kernel hacker--just a
disclaimer.  There are a few problems I've had with running Linux on
the NS1000 that I'll describe in detail.  Overall, I'm impressed with
the quality of this machine, even for its low price (about
$20-something on eBay, _after_ shipping), and appreciate the work
you've all done to make Linux work on these systems.

This message is a bit long (sorry!), so I've broken it into sections
roughly reverse-ordered by importance.

2.4.21 will not boot
~~~~~~~~~~~~~~~~~~~~

I've been able to use both 2.4.19 kernels at
http://networkstation.aytolacoruna.es/.  However, the 2.4.21 kernel
does not work.  The system prints this:

  dev fn  boot  deviceid  cmd_st    bar0      bar1      bar2
  0x0a 0  0x00  00371014  02000006  00000000  00000000 00000000  ibm 27-826=
60
  0x0b 0  0x08  000a1014  04000147  00100021  00000000 00000000  ibm 27-823=
76
  0x0c 0  0x10  20001022  02800005  00100001  04000000 00000000  amd pcnet
  0x0e 0  0x20  89015333  02000003  00000000  00000000 00000000  s3 trio64v=
2/dx
 =20
  reconfiguring frame buffer to 0xcc000000
 =20
  IBM NetworkStation 1000
 =20
  total dram:    00000000 04000000
  loaded at:     00800000 008BE86C
  board data at: 008AE078 008B4A84
  relocated to:  008B4B84 008BB590
  zimage at:     0080A230 008ADC2E
  avail ram:     00400000 00800000
 =20
  Linux/PPC load: console=3DttyS0,9600 console=3Dtty0 root=3D/dev/nfs nfsro=
ot=3D/NetworkStationV2/prodbase/linuxppc ip=3Ddhcp
  Uncompressing Linux...done.
  Now booting the kernel

And it does not proceed any further.  (Not even on the serial console,
which is how I copied those messages.)

I've managed to install Debian using one of the 2.4.19 kernels, and
I've compiled my own 2.4.19 kernel with the 2003/06/25 patch on
networkstation.sf.net.  It seems the binary 2.4.19 kernels at
aytolacoruna.es are older than the patch: booting my own kernel
resulted in being able to change framebuffer modes and use XFree86
(version 4.1.0.1; the stock version that comes with Debian woody).

I compiled a 2.4.21 kernel with the 2003/07/15 NS1000 patch, and it
failed the same way the 2.4.21 kernel at aytolacoruna.es fails.  Since
I changed the configuration a bit from my 2.4.19 kernel, and also had
preemptible kernel and NFS-swap patches added (the corresponding older
versions of those patches did work with my 2.4.19 kernel), I
re-applied the NS1000 patch to a clean 2.4.21 tree, and used the exact
same .config from my 2.4.19 kernel (after running 'make oldconfig');
booting this new 2.4.21 kernel failed, too.

It printed some slightly different information on boot.  If it matters
any, here's a diff (- is from the aytolacoruna.es kernel, and + is
from mine):

   total dram:    00000000 04000000
  -loaded at:     00800000 008BE86C
  +loaded at:     00800000 008E486C
  -board data at: 008AE078 008B4A84
  +board data at: 008D4078 008DAA84
  -relocated to:  008B4B84 008BB590
  +relocated to:  008DAB84 008E1590
  -zimage at:     0080A230 008ADC2E
  +zimage at:     0080A200 008D31C8
   avail ram:     00400000 00800000

Any known problems booting 2.4.21 on the NS1000?  Anyone else had this
issue?

Shifted Video
~~~~~~~~~~~~~

I noticed that in my custom-compiled 2.4.19 kernel, the video is
shifted to the right by about 15-30 pixels (a wild guess) compared to
the aytolacoruna.es 2.4.19 kernel and compared to using the monitor
with a completely different system, in the same video mode (which is
1024x768/60Hz).  I'd like to know if that's correctable without using
the monitor controls.  I seem to recall some talk on the lists about
imprecise video timing problems; is that relevant?

Bad Video (?)
~~~~~~~~~~~~~

I've also noticed that running XFree86, the image quality seems odd.
I can't put my finger on it; perhaps it's slightly fuzzy, perhaps
there's ghosting.  I tried creating some contrasting vertical patterns
in The Gimp to create ghosting, but the result wasn't very bad.  The
same monitor in the same mode seems to produce a better image on a
different system.  Is this a problem others have noticed?  Could it be
because of the NS1000's display hardware, and/or caused by the same
problem that causes the image to shift to the right?  I'm running with
16-bit color, if that makes a difference.

Can't Reboot
~~~~~~~~~~~~

Linux can't seem to reboot the machine, both when going into runlevel
6, and when there's a kernel panic followed by a message to the effect
of "Reboot in 180 seconds".  Just a minor annoyance, of course.  (I
certainly don't feel bad about power-cycling a system with no moving
parts.)

With an aytolacoruna.es 2.4.19 kernel, it just hangs.  With my own
2.4.19 kernel with preemptible kernel and NFS-swap patches, the kernel
will print a message like:

  <4>Oops: kernel access of bad area, sig: 11
  NIP: FFF019AC XER: 00000000 LR: FFF00178 SP: C100FE10 REGS: c100fd60 TRAP=
: 0400    Not tainted
  MSR: 20000030 EE: 0 PR: 0 FP: 0 ME: 0 IR/DR: 11
  TASK =3D c100e000[458] 'reboot' Last syscall: 88
  last math c100e000 last altivec 00000000
  [omitting 32-bit hex numbers are probably not useful to others]
  Call backtrace:
  C100FE38
  note: reboot[458] exited with preempt_count 1

And print this repeatedly:

  RPC: sendmsg returned error 101
  nfs: RPC call returned error 101

The exact result varies.  (Before I run this into ksymoops and make a
proper bug report, I should at least see which patch is causing the
oops.)

Problems with i386 X Clients
~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Several programs compiled for i386 don't work correctly over the
network: Eterm and aterm with tinted transparency enabled display
bogus colors in the background; and xscreensaver with the fade option
enabled crashes on activation.

After some testing I realized these problems also occur with programs
on i386 systems remotely using XFree86 on my Power Mac also running
Debian.  For now I've reported the xscreensaver bug to the Debian BTS,
and will hopefully do so with aterm and Eterm (or a library they might
share that causes the problem (?)).

Just a heads-up for anyone else that's had this problem and couldn't
figure out what was wrong.

Documentation
~~~~~~~~~~~~~

Getting started with the NS1000 was a bit of a pain.  There weren't
very many sources of information about these machines in general, let
alone the port of Linux to them.  I hope to find the time/motivation
to write some FAQ or HOWTO material, based on my experiences so far,
for either the WikiWiki at http://howto.ipng.be/NetstationWiki/,
and/or the Netstation HOWTO, and/or my (as of yet non-existent) own
personal web site.

I'm soliciting suggestions on content to write about and where I
should send it to.

Offtopic/Misc
~~~~~~~~~~~~~

Anyone know where I can buy those PC Card carriers?  Is it possible to
boot Linux from them and otherwise use them?  That'd be great for
securely booting the NCs (eg, not relying on a crackable NFS server)
and using X11 with IPsec transport-mode.  It's been a goal of mine to
set up something like this for quite some time.

Are there any other discussion lists relating to NS1000s?

Does anyone have archives of this list?  I Googled for a phrase from
one message, and apparently SourceForge's own mail archive is the only
public archive.  About a week ago, when I was browsing the archive,
links would often lead to pages that say "forum not found".  Sometimes
reloading the page a few hours later worked, sometimes it didn't.  The
problem seems to be cleared up at this point, though.

--=20
- J.P. Larocque, <pi...@el...>, <pi...@th...>
- The attachment is a PGP sig, not a "virus"; you don't have to open it.
- Encrypted e-mail preferred; 0x0c14cdda; http://ely.ath.cx/~piranha/pgp
- Join the Army, meet interesting people, kill them.

Re: [nwst-dev] new 2.4.21 patch + web upgrade

[Santiago G. M. <ma...@ay...>]

> I was out of town the last two weeks, and busy with work-related
> things as well.

I was out as well ;-)

> Yes, I just verified the problem. I don't see any hangs per se, but the
> command line buffer gets filled with junk. I will try to look at it in
> the next few days, time permitting. This is likely something with the
> setup of the super-io chip by the ROM.

It would be great to have this solved, see what you can do.

Regards!

[nwst-dev] X

[Christian R. <r.c...@gm...>]

Hi,

just a few more words from me. I tested multiple X-Versions and got 
nearly equal results:
X 3.3.6 FB works
X 4.1.0.1 FB works
X 4.3.0.0 locks up - remote action or power-cycling required.


I also did an s-trace. Last words:
open("/proc/bus/pci/devices", O_RDONLY) = 5
fstat64(5, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) 
= 0x30016000
read(5, "0058\t1014000a\t0\t00100021\t0000000"..., 1024) = 444
close(5)                                = 0
munmap(0x30016000, 4096)                = 0


X-Log says:
(II) LoadModule: "pcidata"
(II) Loading /usr/X11R6/lib/modules/libpcidata.a
(II) Module pcidata: vendor="The XFree86 Project"
         compiled for 4.3.0, module version = 1.0.0
         ABI class: XFree86 Video Driver, version 0.6
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:0b:0: chip 1014,000a card 0000,0000 rev 03 class 06,01,00 
hdr 00
(II) PCI: 00:0c:0: chip 1022,2000 card 0000,0000 rev 25 class 02,00,00 
hdr 00
(II) PCI: 00:0e:0: chip 5333,8901 card 0000,0000 rev 16 class 03,00,00 
hdr 00
(II) PCI: End of PCI scan
(II) PCI-to-ISA bridge:
(II) Bus -1: bridge is at (0:11:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set)
(II) Host-to-PCI bridge:
(II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 0 I/O range:
         [0] -1  0       0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) Bus 0 non-prefetchable memory range:
         [0] -1  0       0x00000000 - 0xffffffff (0x0) MX[B]
(II) Bus 0 prefetchable memory range:
         [0] -1  0       0x00000000 - 0xffffffff (0x0) MX[B]

XFree86 Version 4.3.0 (Debian 4.3.0-0ds4 20030417161212 
ds...@ve...)
Release Date: 18 March 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: Linux 2.4.20-ben1 ppc [ELF]
Build Date: 17 April 2003
         Before reporting problems, check http://www.XFree86.Org/
         to make sure that you have the latest version.
Module Loader present
OS Kernel: Linux version 2.4.21 (sad@riazor) (gcc version 2.95.4 
20011002 (Debian prerelease)) #1 Thu Jul 10 13:36:29 CEST 2003


Unfortunatly I do not know debian as good - so i was not able to test X 
4.2. due to missing knowledge of apt-get and dpkg. But it is supposed 
not to work according to the mail from Manty (12.6.). What can be done 
to get X working? I have not found the Trio 64 V2/DX specification and 
my cross-compiler does not work like it is supposed to do. NFS-Swap 
seems to be not possible - so i cannot compile X on the Network-station 
itsself - year i only know normal X86-Architecture right now...

Is this an X or a Kernel-problem? I assumed X.

Ciao
	Christian


ps: I also read something about revisions and such stuff. Here are the 
numbers out of my 8362-A52, S/N 23-W1301 . 0200146, D/W # 1042, AJ0018C

[nwst-dev] Feedback

[Christian R. <r.c...@gm...>]

Hi,

first of all:
Congratulation. You really managed it, to get linux working on the 
Networkstation (1000).

When i bought mine about two years ago, i was very disapointed, because 
of the software delivered by IBM - now i can really have a debian on my 
box :-)

But there is still some work to do.
First of all, i would suggest, to provide binary packets directly on 
sourceforge. I already installed the cross-compiler and patched the 
kernel - but i did not manage to build my own Kernel :-( So i was very 
happy about the link to http://networkstation.aytolacoruna.es/ where i 
downloaded the kernel and a root-fs - so everything worked fine.

Second: Is there a way to get X to work with 16bpp? I get an ugly green 
double-picture...

The last point on my wish-list is really a add-on:
I root-image, only providing an X-Server using xdmcp

.. but i hope i will be able to do this myself by stripping the provided 
root-image.

Thanks a lot and keep on this good work!

Ciao
	Christian

Re: [nwst-dev] new 2.4.21 patch + web upgrade

[Jochen R. <jo...@pa...>]

Hi Manty,

I was out of town the last two weeks, and busy with work-related
things as well.

> I was wondering if there are any news, we seem to have stopped our
> development lately. I'm really worried about the bug with the mouse not
> allowing the machine to boot, Jochen, have you been able to replicate this
> problem? Any sugestions?

Yes, I just verified the problem. I don't see any hangs per se, but the
command line buffer gets filled with junk. I will try to look at it in
the next few days, time permitting. This is likely something with the
setup of the super-io chip by the ROM.

> We are now using Linux 2.4.21 here on the NS1000 for our everyday work and
> so far no problems recorded, everything is smooth and stable.

Great!

Regards,
Jochen

[nwst-dev] new 2.4.21 patch + web upgrade

[Santiago G. M. <ma...@ay...>]

Hi!

I had forgotten to update the patch for 2.4.21 with the DPMS fix, I did so
today and also I removed the DPMS problem from the TODO things in the web
page.

I was wondering if there are any news, we seem to have stopped our
development lately. I'm really worried about the bug with the mouse not
allowing the machine to boot, Jochen, have you been able to replicate this
problem? Any sugestions?

We are now using Linux 2.4.21 here on the NS1000 for our everyday work and
so far no problems recorded, everything is smooth and stable.

Regards...

Re: [nwst-dev] New patch and kernel, 2.4.21 + web page

[Santiago G. M. <ma...@ay...>]

Sorry I hadn't replied before :-(

> And a very nice web page, finally -- great job!

That is a work from Jesus, one of the igalia guys ;-)

> Based on the setterm command lines you emailed me I was able to see recreate
> the video non-blanking issue. The old driver was blanking in the default
> blanking mode, i.e. with 'setterm -powersave off' in effect. I am attaching
> a patch against the 2.4.19 ns1000 kernel. Also with hard tabs here:
> http://www.panix.com/~jochen/ns1000/patch-2.4.19-s3trio-blank-20030715.gz

This seems to work ok, at first I thought there was a problem as the monitor
enters DPMS and doesn't do blanking first, but then I realised that this was
also happening to me on a normal PC, so maybe things have changed or I'm
doing something wrong :-? Anyway, your code works ok now :-)

I'm going to try to upload a new version of the 2.4.21 patch with this patch
applied today if time permits.

Regards...

Re: [nwst-dev] New patch and kernel, 2.4.21 + web page

[Jochen R. <jo...@pa...>]

Hi Manty,

> I have just made available through the file release system of our
> sourceforge project a new patch, it is the 2.4.19-20030625 patch that Jochen
> had publised but ported to 2.4.21. I have not ported the IDE patches as IDE
> has changed a lot in 2.4.21 and the machine doesn't support it out of the
> box.

Great. I will see that I take a look at the IDE stuff. I am still on
the 2.4.19 kernel at the moment.

And a very nice web page, finally -- great job!

Based on the setterm command lines you emailed me I was able to see recreate
the video non-blanking issue. The old driver was blanking in the default
blanking mode, i.e. with 'setterm -powersave off' in effect. I am attaching
a patch against the 2.4.19 ns1000 kernel. Also with hard tabs here:
http://www.panix.com/~jochen/ns1000/patch-2.4.19-s3trio-blank-20030715.gz

It should apply cleanly against 2.4.21 as well, but I have not tried that.

Jochen

--- linux-2.4.19/drivers/video/s3trio.c.old     Tue Jul 15 02:25:17 2003
+++ linux-2.4.19/drivers/video/s3trio.c Tue Jul 15 02:38:24 2003
@@ -769,6 +769,9 @@
 {
        uint8_t v;
        debug_flow("s3_display_enable %d\n", enable);
+       if(enable) {
+               s3_crtc_outb(trio, 0x0d, s3_crtc_inb(trio, 0x0d) & 0x0f);
+       }
        /* SR1 is clock mode */
        v = s3_seq_inb(trio, 0x01) & 0xdf;
        if(!enable)
@@ -1891,11 +1894,35 @@
 static void s3triofbcon_blank(int blank, struct fb_info *info)
 {
        triofb_t *trio = (triofb_t*)info;
-       uint8_t x;
-       debug_flow("s3triofb_con_blank %d\n", blank);
+       uint8_t sr1, srd;
+       debug_msg("s3triofb_con_blank %d\n", blank);
+
+#if 0
        s3_mmio_put8(trio, 0x3c4, 0x1, trio->mmio_regs + 0x03c4);
        x = s3_mmio_get8(trio, 0x3c5);
        s3_mmio_put8(trio, 0x3c5, (x & (~0x20)) | (blank << 5), trio->mmio_regs + 0x03c5);
+#endif
+       sr1 = s3_seq_inb(trio, 0x01) & ~0x20;
+       srd = s3_seq_inb(trio, 0x0d) & 0x0f;
+       if(blank) {
+               sr1 |= 0x20;
+               switch(blank - 1) {
+               default:
+               case VESA_NO_BLANKING:
+                       break;
+               case VESA_VSYNC_SUSPEND:
+                       srd |= 0x40;
+                       break;
+               case VESA_HSYNC_SUSPEND:
+                       srd |= 0x10;
+                       break;
+               case VESA_POWERDOWN:
+                       srd |= 0x50;
+                       break;
+               }
+       }
+       s3_seq_outb(trio, 0x0d, srd);
+       s3_seq_outb(trio, 0x01, sr1);
 }

     /*

[nwst-dev] New patch and kernel, 2.4.21 + web page

[Santiago G. M. <ma...@ay...>]

Hi!

I have just made available through the file release system of our
sourceforge project a new patch, it is the 2.4.19-20030625 patch that Jochen
had publised but ported to 2.4.21. I have not ported the IDE patches as IDE
has changed a lot in 2.4.21 and the machine doesn't support it out of the
box.

This patch doesn't fix anything, it is only a port of what we had to 2.4.21.
We have been running it here for some days and it seems stable.

Also we have published some days ago a dirty page for the project, so that
if you now go to http://networkstation.sourceforce.net you'll be able to see
our marvelous NCs and click on some links there. Ideas or redesigns are
welcome.

I have also published at http://networksstation.aytolacoruna.es a binary
2.4.21 kernel and the config I used for compiling it. This config has much
fewer things than the ones I used before, as I have been working in removing
all the not necesary things out of it.

Well, I guess that is all for now, hope you like it.

Regards!

Re: [nwst-dev] Re: X configuration

[Santiago G. M. <ma...@ay...>]

> > I'm still wondering what is being done wrong with the clock computations, we
> > are not getting the exact clock we should, while the NetBSD and also the
> > native S3 driver for X 4.2.1 does, right now I have XFree 4.2.1 running at
> > 16 bits 1024 x 768 67.7KHz 84Hz as my monitor says, I'm using the standard
> > modeline for 85Hz:
> > 
> > ModeLine "1024x768"   94.5 1024 1072 1168 1376    768  769  772  808 +hsync
> > +vsync
> 
> The fbdev X server has special requirements for ModeLines, iirc. There is a
> tool around somewhere to convert fbset modes to ModeLine data, or something
> like that. Check the fbdev howto, perhaps.

The problem is not with X, even in the console when I set up 60Hz I get 59
and things like that, your debugging info says that it is computing one
clock and only gets an approximation, that is the main problem I see with
this. You can see this in my previous messages and in the dmesgs I made
available.

BTW, there seems to be a problem with 800x600 in the last patches, the
screen gets borked when you try to set this mode, I believe this didn't
happen before :-?

Also we have discovered that DPMS doesn't work, in X we don't get DPMS nor
blanking. Was it supposed to be working?

Regards...

[nwst-dev] Re: X configuration

[Jochen R. <jo...@pa...>]

> I'm still wondering what is being done wrong with the clock computations, we
> are not getting the exact clock we should, while the NetBSD and also the
> native S3 driver for X 4.2.1 does, right now I have XFree 4.2.1 running at
> 16 bits 1024 x 768 67.7KHz 84Hz as my monitor says, I'm using the standard
> modeline for 85Hz:
> 
> ModeLine "1024x768"   94.5 1024 1072 1168 1376    768  769  772  808 +hsync
> +vsync

The fbdev X server has special requirements for ModeLines, iirc. There is a
tool around somewhere to convert fbset modes to ModeLine data, or something
like that. Check the fbdev howto, perhaps.

It is also possible that I am not setting up some register correctly...

> Well, I'll try to work on porting this patch to 2.4.21 in the next days.

Let me know if I can help.

Jochen

[nwst-dev] New patch, fixes pcmcia bridge

[Jochen R. <jo...@pa...>]

I hope this will work for all configurations out there:

http://networkstation.sourceforge.net/patch-2.4.19-ns1000-20030625.gz

For pcmcia to work, you will need to install card services, and you
will need to compile the needed modules for your setup. I have not yet
figured out how to do a cross-compiled 'make modules_install', and I
did not feel like trashing my development machine. So I copied the
kernel tree into the NFS-mounted rootfs and did the modules_install
there -- works well.

If this works reasonably well then I suppose we can put this up in
the files section.

Jochen

Re: [nwst-dev] Re: X configuration

[Jochen R. <jo...@pa...>]

> > BTW, this is the best patch we have, and we don't have it published on the
> > sourceforge archives, if you don't mind I'd like to make this one available.
> 
> If you don't mind I'd like units with PCMCIA sockets to be bootable :)

I will post a new patch tonight that fixes the boot problem and gets the PCMCIA
port working. I have this running here with an older 10mbps card.

Regards,
Jochen

Re: [nwst-dev] Re: X configuration

[Miguel B. P. <en...@fi...>]

> BTW, this is the best patch we have, and we don't have it published on the
> sourceforge archives, if you don't mind I'd like to make this one available.

If you don't mind I'd like units with PCMCIA sockets to be bootable :)

[nwst-dev] Re: X configuration

[Santiago G. M. <ma...@ay...>]

> I put up a new patch that should get around this problem:
> http://networkstation.sourceforge.net/patch-2.4.19-ns1000-20030623.gz

Great, this is really working here, I'm gonna change our NCs to Linux right
away.

I'm still wondering what is being done wrong with the clock computations, we
are not getting the exact clock we should, while the NetBSD and also the
native S3 driver for X 4.2.1 does, right now I have XFree 4.2.1 running at
16 bits 1024 x 768 67.7KHz 84Hz as my monitor says, I'm using the standard
modeline for 85Hz:

ModeLine "1024x768"   94.5 1024 1072 1168 1376    768  769  772  808 +hsync
+vsync

If you check with vidtune the line is perfectly ok, exactly 85.00Hz however
we are not getting that because we are not getting the 94.5Mhz from the
card.

The other thing I'm wondering is why don't we get the pixmaps and the fonts
on the S3 driver.

> PCBA 0200134 ECO 4905D

I really don't understand this numbers, they are in a completely different
format than ours, anyway, it seems that you got the problem right and that
this was not it ;-)

Well, I'll try to work on porting this patch to 2.4.21 in the next days.

BTW, this is the best patch we have, and we don't have it published on the
sourceforge archives, if you don't mind I'd like to make this one available.

Regards!

[nwst-dev] Re: X configuration

[Jochen R. <jo...@pa...>]

Manty,

Could you check the patch I posted yesterday?

If this fixes your problems, then I will have to come up with a
more long-time solution. The patch from yesterday will not boot
on NS1000 models with the pcmcia bridge board installed.

Regards,
Jochen

[nwst-dev] Re: X configuration

[Jochen R. <jo...@pa...>]

Manty,

Thanks for the serial port output.

> then typing ^C all I got was the usual problem the userspace was locked :-(
> This last problem is a really big problem we have, of course that we must
> get the X working first, but this last problem is a big one.
[...]
> kernel now responds to pings, but doesn't work on userspace mode
> no ssh and nothing here, where I'm typing this, at the serial console
> :-(

Ah, that is news to me, and very helpful. I was able to recreate your
problems here after removing my pcmcia carrier board. This will shift
the PCI configuration values around, and that in turn will cause the
hangs.

I put up a new patch that should get around this problem:

http://networkstation.sourceforge.net/patch-2.4.19-ns1000-20030623.gz

BTW, here is the revision information from my machine here:

PCBA 0200134 ECO 4905D

Regards,
Jochen

Re: [nwst-dev] netstation 8361-110 with Linux?

[Aleksandr K. <cz...@io...>]

Replying my previous mail :-)

> > It would help if someone could post some dmesg logs from the NetBSD-
> > derived kernel that comes with the IBM NSM. The 8361-110 uses ISA and
> > Vesa local bus-style peripheral chips, so knowing the IO addresses etc
> > comes in handy.
> 
> Ok, I'll try to get the box up as soon I'm done making some coffee. I

ok, I got the box up and running (debian/stable as the boot server,
debian/testing with kdm as the X server), however, I do not know how
to get the dmesg logs? I manage to get the console open, and telnet
into diag and so forth, but are there any instructions on how to get
the logs? As I gather, the kernel.Z (which is loaded on boot),
contains the kernel and the X server. and I have diagnostic output
enabled now, but nothing very interesting is seen.

the kernel seems to be an ELF file (sysv/unix), but gnu/objdump
doesn't seem to recognize it too well (I'm running it on the
non-compressed kernel).

also, on another note, the x server seems to be in 8-bit color depth,
is it possible to change this? at least I failed to find any
documentation on this (also the rs/6000 nsm link that you have in the
howto doesn't work anymore).

ak.