RE: [parisc-linux] What keywords should I use to find the answer?

RE: [parisc-linux] What keywords should I use to find the answer?

[Edward Alfert]

Thanks for the reply... Following is the entire dmsg... 
I notice it twice says "I'm not trying to set up your PCI graphics card
now... It would freeze your machine."

Linux version 2.4.9-32 (root@paer) (gcc version 3.0.2 (Debian)) #1 Fri
Nov 30 19
:36:30 MST 2001
FP[0] enabled: Rev 0 Model 14
The 32-bit Kernel has started...
Determining PDC firmware type: System Map.
model   00005990 00000481 00000000 00000002 77ab680d 100000f0 00000008
000000b2 
000000b2
vers    00000501
cpuid   000001d7
CPUID   vers 14 rev 23
model   9000/782/C240+
Total Memory: 512 Mb
pagetable_init
On node 0 totalpages: 131072
zone(0): 131072 pages.
zone(1): 0 pages.
zone(2): 0 pages.
LED display at f0190001 registered
Kernel command line: root=/dev/sda4 HOME=/ console=ttyS0 TERM=vt102
Console: colour dummy device 160x64
Calibrating delay loop... 470.22 BogoMIPS
Memory: 512860k available
Dentry-cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Mount-cache hash table entries: 8192 (order: 4, 65536 bytes)
Buffer-cache hash table entries: 32768 (order: 5, 131072 bytes)
Page-cache hash table entries: 131072 (order: 7, 524288 bytes)
Searching for devices...
Found devices:
1. U2-IOA BC Runway Port (12) at 0xfff88000 [8], versions 0x580, 0xf,
0xb
2. Dino PCI Bridge (13) at 0xf2000000 [8/0], versions 0x680, 0x3, 0xa
3. Raven U/L2 Dino RS-232 (10) at 0xf2003000 [8/0/63], versions 0x6,
0x0, 0x8c
4. Raven+ w SE FWSCSI Core BA (11) at 0xffd00000 [8/16], versions 0x56,
0x0, 0x8
1,  additional addresses: 0xffc00000 
5. Raven+ w SE FWSCSI Core Centronics (10) at 0xffd02000 [8/16/0],
versions 0x56
, 0x0, 0x74,  additional addresses: 0xffd03000 
6. Raven+ w SE FWSCSU Core Audio (10) at 0xffd04000 [8/16/1], versions
0x56, 0x4
, 0x7b
7. Raven+ w SE FWSCSI Core RS-232 (10) at 0xffd05000 [8/16/4], versions
0x56, 0x
0, 0x8c
8. Raven+ w SE FWSCSI Core SCSI (10) at 0xffd06000 [8/16/5], versions
0x56, 0x0,
 0x82
9. Raven+ w SE FWSCSI Core PS/2 Port (10) at 0xffd08000 [8/16/7],
versions 0x56,
 0x0, 0x84
10. Raven+ w SE FWSCSI Core PS/2 Port (10) at 0xffd08100 [8/16/8],
versions 0x56
, 0x0, 0x84
11. U2-IOA BC GSC+ Port (7) at 0xf203f000 [8/63], versions 0x501, 0x1,
0xc
12. U2-IOA BC Runway Port (12) at 0xfff8a000 [10], versions 0x580, 0xf,
0xb
13. Cujo PCI Bridge (13) at 0xf1000000 [10/0], versions 0x682, 0x1, 0xa,
additi
onal addresses: 0xf6000000 
14. U2-IOA BC GSC+ Port (7) at 0xf103f000 [10/63], versions 0x501, 0x1,
0xc
15. Raven U 240 (9000/780/C240) (0) at 0xfffa0000 [32], versions 0x599,
0x0, 0x4
16. Raven U 240 (1) at 0xfffb1000 [49], versions 0x6f, 0x0, 0x9
CPU(s): 1 x PA8200 (PCX-U+) at 236.000000 MHz
ccio found U2 at 0xfff88000
io_io_low: 0xf2000000
17. Dino PCI Bridge (13) at 0xf2000000 [8/0], versions 0x680, 0x3, 0xa
18. Raven U/L2 Dino RS-232 (10) at 0xf2003000 [8/0/63], versions 0x6,
0x0, 0x8c
19. Raven U/L2 Dino PS/2 Port (10) at 0xf2001000 [8/1], versions 0x6,
0x0, 0x96
20. Raven+ w SE FWSCSI Core BA (11) at 0xffd00000 [8/16], versions 0x56,
0x0, 0x
81,  additional addresses: 0xffc00000 
21. Raven+ w SE FWSCSI Core Centronics (10) at 0xffd02000 [8/16/0],
versions 0x5
6, 0x0, 0x74,  additional addresses: 0xffd03000 
22. Raven+ w SE FWSCSU Core Audio (10) at 0xffd04000 [8/16/1], versions
0x56, 0x
4, 0x7b
23. Raven+ w SE FWSCSI Core RS-232 (10) at 0xffd05000 [8/16/4], versions
0x56, 0
x0, 0x8c
24. Raven+ w SE FWSCSI Core SCSI (10) at 0xffd06000 [8/16/5], versions
0x56, 0x0
, 0x82
25. Raven+ w SE FWSCSI Core PS/2 Port (10) at 0xffd08000 [8/16/7],
versions 0x56
, 0x0, 0x84
26. Raven+ w SE FWSCSI Core PS/2 Port (10) at 0xffd08100 [8/16/8],
versions 0x56
, 0x0, 0x84
27. U2-IOA BC GSC+ Port (7) at 0xf203f000 [8/63], versions 0x501, 0x1,
0xc
ccio found U2 at 0xfff8a000
io_io_low: 0xf1000000
28. Cujo PCI Bridge (13) at 0xf1000000 [10/0], versions 0x682, 0x1, 0xa,
additi
onal addresses: 0xf6000000 
29. Dino RS-232 (10) at 0xf1003000 [10/3], versions 0x7, 0x0, 0x8c
30. U2-IOA BC GSC+ Port (7) at 0xf103f000 [10/63], versions 0x501, 0x1,
0xc
Lasi version 0 at 0xffd00000 found.
Dino version 3.1 found at 0xf2000000
Cujo version 2.0 found at 0xf1000000
Enabling Cujo 2.0 bug workaround
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Starting kswapd v1.8
parport_init_chip: initialize bidirectional-mode.
parport0: PC-style at 0xffd02800, irq 88 [PCSPP,TRISTATE]
STI PCI ROM enabled at 0xf1e00000
PCI graphic ROM found at f1e00000 (2048 kB), fb @ f6000000 (32 MB)
PCI region 0: f6000000 with 32768 kB
PCI region 1: 00000000 with 0 kB
PCI region 2: 00000000 with 0 kB
PCI region 3: 00000000 with 0 kB
PCI region 4: 00000000 with 0 kB
PCI region 5: 00000000 with 0 kB
PCI region 6: f1e00000 with 2048 kB
PCI region 7: 00000000 with 0 kB
PCI region 8: 00000000 with 0 kB
PCI region 9: 00000000 with 0 kB
PCI region 10: 00000000 with 0 kB
PCI region 11: 00000000 with 0 kB
Trying PCI STI ROM at f1e00000, PCI hpa at f6000000
I'm not trying to set up the PCI graphic card now... It would freeze
your machin
e
Unable to handle STI device 'PCI device 103c:1008 (Hewlett-Packard
Company)'
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ
SERIAL_PCI en
abled
ttyS00 at iomem 0xffd05800 (irq = 90) is a 16550A
ttyS01 at iomem 0xf2003800 (irq = 106) is a 16550A
ttyS02 at iomem 0xf1003800 (irq = 170) is a 16550A
Lasi PS/2 receive buffer timeout
PS/2 keyboard port at 0xffd08000 (irq 69) found, no device attached.
Lasi PS/2 transmit buffer timeout
PS/2 psaux port at 0xffd08100 (irq 69) found, no device attached.
lp0: using parport0 (interrupt-driven).
Generic RTC Driver v1.02 05/27/1999 Sam Creasey (sammy@oh.verio.com)
block: 128 slots per queue, batch=16
RAMDISK driver initialized: 16 RAM disks of 6144K size 1024 blocksize
loop: loaded (max 8 devices)
Linux Tulip driver version 0.9.15-pre6 (July 2, 2001)
tulip0: no phy info, aborting mtable build
tulip0:  MII transceiver #1 config 1000 status 782d advertising 01e1.
eth0: Digital DS21143 Tulip rev 48 at 0xff00, 00:60:B0:D0:4D:57, IRQ 96.
SCSI subsystem driver Revision: 1.00
sym53c8xx: at PCI bus 0, device 19, function 0
sym53c8xx: 53c875 detected 
sym53c875-0: rev 0x4 on pci bus 0 device 19 function 0 irq 99
sym53c875-0: ID 7, Fast-20, Parity Checking
scsi0 : sym53c8xx-1.7.3c-20010512
  Vendor: IBM       Model: DDRS-34560WS      Rev: HP01
  Type:   Direct-Access                      ANSI SCSI revision: 02
53c700: Version 2.6 By James.Bottomley@HansenPartnership.com
scsi1: 53c710 rev 2 
scsi1 : LASI SCSI 53c700
scsi1: (2:0) Synchronous at offset 8, period 100ns
  Vendor: TOSHIBA   Model: CD-ROM XM-6201TA  Rev: 1037
  Type:   CD-ROM                             ANSI SCSI revision: 02
Attached scsi disk sda at scsi0, channel 0, id 6, lun 0
sym53c875-0-<6,*>: FAST-20 WIDE SCSI 40.0 MB/s (50.0 ns, offset 15)
SCSI device sda: 8388314 512-byte hdwr sectors (4295 MB)
Partition check:
 sda: sda1 sda2 sda3 sda4
Attached scsi CD-ROM sr0 at scsi1, channel 0, id 2, lun 0
sr0: scsi-1 drive
Uniform CD-ROM driver Revision: 3.12
Lasi Harmony Audio rev. 31 at 0xffd04000, using IRQ 82
sticonsole_init: searching for STI ROMs
BUG: Skipping previously registered driver: sti (native)
STI PCI ROM enabled at 0xf1e00000
PCI graphic ROM found at f1e00000 (2048 kB), fb @ f6000000 (32 MB)
PCI region 0: f6000000 with 32768 kB
PCI region 1: 00000000 with 0 kB
PCI region 2: 00000000 with 0 kB
PCI region 3: 00000000 with 0 kB
PCI region 4: 00000000 with 0 kB
PCI region 5: 00000000 with 0 kB
PCI region 6: f1e00000 with 2048 kB
PCI region 7: 00000000 with 0 kB
PCI region 8: 00000000 with 0 kB
PCI region 9: 00000000 with 0 kB
PCI region 10: 00000000 with 0 kB
PCI region 11: 00000000 with 0 kB
Trying PCI STI ROM at f1e00000, PCI hpa at f6000000
I'm not trying to set up the PCI graphic card now... It would freeze
your machin
e
Unable to handle STI device 'PCI device 103c:1008 (Hewlett-Packard
Company)'
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 32768 bind 65536)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
VFS: Mounted root (ext2 filesystem) readonly.
Adding Swap: 498872k swap-space (priority -1)
eth0: Setting full-duplex based on MII#1 link partner capability of
45e1.
VFS: Disk change detected on device sr(11,0)
ISO 9660 Extensions: RRIP_1991A
ISO 9660 Extensions: RRIP_1991A
Lasi PS/2 transmit buffer timeout
-----Original Message-----
From: Helge Deller [mailto:helge.deller@sap.com] 
Sent: Thursday, December 13, 2001 4:10 AM
To: Edward Alfert
Subject: Re: [parisc-linux] What keywords should I use to find the
answer?


On Thursday 13 December 2001 05:42, Edward Alfert wrote:
> ?) Does 0.9.3 support the graphics card on a c240? Or only serial?

Hi Edward,

You maybe should have mentioned the name of the graphic card in 
your machine.
Boot up in serial-console mode and give us the inventory listing (or the
whole
dmesg) which the pa-kernel prints right at the beginning.

Greetings,
Helge

Re: [parisc-linux] What keywords should I use to find the answer?

[Helge Deller]

Hi Edward,

Hmm, I think we forgot to backport the stifb-PCI hack :-(

The reson behind this "I'm not trying to set up the PCI graphic 
card now... It would freeze your machine" message is, that
during the initialisation of the A4977A Visualize EG PCI card 
(which is often found in c3000 workstations) my machine
completely freezes.

Since you have another PCI card you should try a recent kernel 
from CVS which explicitly checks for this combination of c3000 and 
Visualize EG combo and avoids to initialize it. For all other 
combinations of workstations and graphic cards this check isn't 
done and the graphic card will be initialized.
(PS: This should be added to the 0.9.3 FAQ!)

Helge

On Thursday 13 December 2001 14:37, Edward Alfert wrote:
> Thanks for the reply... Following is the entire dmsg...
> I notice it twice says "I'm not trying to set up your PCI graphics card
> now... It would freeze your machine."
>
> Linux version 2.4.9-32 (root@paer) (gcc version 3.0.2 (Debian)) #1 Fri
> Nov 30 19
> .....
> STI PCI ROM enabled at 0xf1e00000
> PCI graphic ROM found at f1e00000 (2048 kB), fb @ f6000000 (32 MB)
> PCI region 0: f6000000 with 32768 kB
> PCI region 1: 00000000 with 0 kB
> PCI region 2: 00000000 with 0 kB
> PCI region 3: 00000000 with 0 kB
> PCI region 4: 00000000 with 0 kB
> PCI region 5: 00000000 with 0 kB
> PCI region 6: f1e00000 with 2048 kB
> PCI region 7: 00000000 with 0 kB
> PCI region 8: 00000000 with 0 kB
> PCI region 9: 00000000 with 0 kB
> PCI region 10: 00000000 with 0 kB
> PCI region 11: 00000000 with 0 kB
> Trying PCI STI ROM at f1e00000, PCI hpa at f6000000
> I'm not trying to set up the PCI graphic card now... It would freeze
> your machine
> Unable to handle STI device 'PCI device 103c:1008 (Hewlett-Packard
> Company)'
>....
> -----Original Message-----
> From: Helge Deller [mailto:helge.deller@sap.com]
> Sent: Thursday, December 13, 2001 4:10 AM
> To: Edward Alfert
> Subject: Re: [parisc-linux] What keywords should I use to find the
> answer?
>
> On Thursday 13 December 2001 05:42, Edward Alfert wrote:
> > ?) Does 0.9.3 support the graphics card on a c240? Or only serial?
>
> Hi Edward,
>
> You maybe should have mentioned the name of the graphic card in
> your machine.
> Boot up in serial-console mode and give us the inventory listing (or the
> whole
> dmesg) which the pa-kernel prints right at the beginning.
>
> Greetings,
> Helge

Re: [parisc-linux] What keywords should I use to find the answer?

[Edward Alfert]

i consider myself a newbie (but i'm willing to learn), so please cut me some
slack, but building the kernel didn't work for me.

this is what i did:
su
cd
mkdir source
ftp ftp.parisc-linux.org
user: anonymous
password: edward@alfert.com
cd cvs
get linux-latest.tar.gz     (also tried linux-2.4.16-pa19.tar.gz)
get palo-latest.tar.gz
quit

cd source

zcat linux-latest.tar.gz | tar -xf -    (nothing gets extracted)
zcat linux-2.4.16-pa19.tar.gz | tar -xv -    (nothing gets extracted)
zcat palo-latest.tar.gz | tar -xf -  (tons of files are extracted into palo
folder)

gunzip *
tar -tvf linux-latest.tar   (no files are listed)
tar -tvf linux-2.4.16-pa19.tar.gz   (no files are listed)
tar -tvf palo-latest.tar.gz   (tons of files are listed)

Why is the linux* files empty?  did i do something wrong?

----- Original Message -----
From: "Helge Deller" <helge.deller@sap.com>
To: "Edward Alfert" <edward@alfert.com>;
<parisc-linux@lists.parisc-linux.org>
Sent: Thursday, December 13, 2001 9:30 AM
Subject: Re: [parisc-linux] What keywords should I use to find the answer?


> Hi Edward,
>
> Hmm, I think we forgot to backport the stifb-PCI hack :-(
>
> The reson behind this "I'm not trying to set up the PCI graphic
> card now... It would freeze your machine" message is, that
> during the initialisation of the A4977A Visualize EG PCI card
> (which is often found in c3000 workstations) my machine
> completely freezes.
>
> Since you have another PCI card you should try a recent kernel
> from CVS which explicitly checks for this combination of c3000 and
> Visualize EG combo and avoids to initialize it. For all other
> combinations of workstations and graphic cards this check isn't
> done and the graphic card will be initialized.
> (PS: This should be added to the 0.9.3 FAQ!)
>
> Helge
>

Re: [parisc-linux] What keywords should I use to find the answer?

[Paul Bame]

= 
= Why is the linux* files empty?  did i do something wrong?
= 

Bug in the script which creates them.  Should be a new tarball in
under an hour from now.

	-P

Re: [parisc-linux] What keywords should I use to find the answer?

[Matthew Wilcox]

On Thu, Dec 13, 2001 at 09:36:31AM -0700, Paul Bame wrote:
> = 
> = Why is the linux* files empty?  did i do something wrong?
> = 
> 
> Bug in the script which creates them.  Should be a new tarball in
> under an hour from now.

Sure it wasn't due to /var filling up last night?

-- 
Revolutions do not require corporate support.

Re: [parisc-linux] What keywords should I use to find the answer?

[Edward Alfert]

ok...was able to follow all the steps in creating the new kernel including
make oldconfig
make dep
make palo

now what? (this is where the Building the Kernel FAQ ends)

So from this point forward i'm guessing (trial and error)...

I rebooted and it still booted to the old kernel 2.4.9

i then manually moved /root/source/palo/lifimage to
/boot/vmlinux-2.4.16-pa19
then created link to it from vmlinux

I then rebooted and i get:
Opening /vmlinux
Opening /vmlinux-2.4.16-pa19
Couldn't grok your kernel executable format
ERROR: failed to load kernel

Now i know i shouldn't have manually moved the files over and there was a
correct way of doing this... but i looked in all docs i could find and can't
find the right way to move a new kernel into place from the new created
palo/lifimage

1) what is the right way?
2) how do i recover? do i interrup the boot process... interact with IPL and
pass some parameter to boot from the old kernel (that i left behind at
/boot/vmlinux-2.4.9)?

Thanks for all the previous help... i'm close but yet so far....

----- Original Message -----
From: "Paul Bame" <bame@fc.hp.com>
To: "Edward Alfert" <edward@alfert.com>
Cc: <parisc-linux@lists.parisc-linux.org>
Sent: Thursday, December 13, 2001 11:36 AM
Subject: Re: [parisc-linux] What keywords should I use to find the answer?


> =
> = Why is the linux* files empty?  did i do something wrong?
> =
>
> Bug in the script which creates them.  Should be a new tarball in
> under an hour from now.
>
> -P
>

Re: [parisc-linux] What keywords should I use to find the answer?

[Tom]

On Thu, 13 Dec 2001, Edward Alfert wrote:
> ok...was able to follow all the steps in creating the new kernel including
> make oldconfig
> make dep
> make palo
>
> now what? (this is where the Building the Kernel FAQ ends)
>
> So from this point forward i'm guessing (trial and error)...
>
> I rebooted and it still booted to the old kernel 2.4.9
>
> i then manually moved /root/source/palo/lifimage to
> /boot/vmlinux-2.4.16-pa19
> then created link to it from vmlinux
>
> I then rebooted and i get:
> Opening /vmlinux
> Opening /vmlinux-2.4.16-pa19
> Couldn't grok your kernel executable format
> ERROR: failed to load kernel

Exactly what I had happen. Someone was nice enough to point out to me the
*right* way <g>...

In your linux root (with the Makefile) is vmlinux. Move that to
/boot/vmlinux-xxx, then edit palo.conf (second line has the kernel you're
wanting to boot by default). Then, run palo (gives you a two-line 'before'
and 'after' which should show the new kernel) and reboot.

> Now i know i shouldn't have manually moved the files over and there was a
> correct way of doing this... but i looked in all docs i could find and can't
> find the right way to move a new kernel into place from the new created
> palo/lifimage

Don't think there's any way other than manual - 'make install' isn't
working yet AFAIK.

Recover by using 'boot pri ipl' at the initial boto menu, then change your
kernel name to the last one you used.

RE: [parisc-linux] What keywords should I use to find the answer?

[Edward Alfert]

Thanks... This is fun... 

New kernel 2.4.19 is up and running... I'm able to use my monitor ...
Initially I couldn't log in but found in the FAQ that I needed to
"uncomment" tty0 from /etc/inittab ... By the way, there is no entry for
tty0 in /etc/inittab, so I created one... So the FAQ shouldn't read
"uncomment" but instead "create".

I'm now trying to get Xfree working... I know I ask a lot of questions,
but I promise to return the favor to other newbies that experience the
same problems as me.

I executed /usr/X11R6/bin/xf86config and set all the parameters for the
mouse, monitor, and graphics card... But it doesn't work... The screen
goes black (as if it was changing resolutions) then comes back to text
mode and dumps the messages.

I have included the contents of /var/log/XFree86.0.log in hopes that one
of you will guide me in the right direction...

The system is a C240 with FX4 video card (that's HP Visualize FX-4 with
18mb RAM) ... The GRAPHICS(4) is set to 1280 x 1024 @ 72Hz.

c240:~# cat /var/log/XFree86.0.log

This is a pre-release version of XFree86, and is not supported in any
way.  Bugs may be reported to XFree86@XFree86.Org and patches submitted
to fixes@XFree86.Org.  Before reporting bugs in pre-release versions,
please check the latest version in the XFree86 CVS repository
(http://www.XFree86.Org/cvs)

XFree86 Version 4.1.0.1 / X Window System
(protocol Version 11, revision 0, vendor release 6510)
Release Date: xx August 2001
        If the server is older than 6-12 months, or if your card is
        newer than the above date, look for a newer version before
        reporting problems.  (See http://www.XFree86.Org/FAQ)
Build Operating System: Linux 2.4.9-pa79 parisc64 [ELF] 
(==) Log file: "/var/log/XFree86.0.log", Time: Thu Dec 13 22:59:57 2001
(==) Using config file: "/etc/X11/XF86Config"
Markers: (--) probed, (**) from config file, (==) default setting,
         (++) from command line, (!!) notice, (II) informational,
         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) ServerLayout "Simple Layout"
(**) |-->Screen "Screen 1" (0)
(**) |   |-->Monitor "Cornerstone p1500"
(**) |   |-->Device "HP Visualize FX4"
(**) |-->Input Device "Mouse1"
(**) |-->Input Device "Keyboard1"
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xfree86"
(**) XKB: rules: "xfree86"
(**) Option "XkbModel" "pc101"
(**) XKB: model: "pc101"
(**) Option "XkbLayout" "us"
(**) XKB: layout: "us"
(==) Keyboard: CustomKeycode disabled
(**) FontPath set to
"/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75
dpi/:unscaled,/usr/X11R6/lib/X11/fonts/100dpi/:unscaled,/usr/X11R6/lib/X
11/fonts
/Type1/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/75dpi/
,/usr/X1
1R6/lib/X11/fonts/100dpi/"
(**) RgbPath set to "/usr/X11R6/lib/X11/rgb"
(--) using VT number 2

(WW) Cannot open APM
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:13:0: chip 1000,000f card 0000,0000 rev 04 class 01,00,00
hdr 00
(II) PCI: 00:14:0: chip 1011,0019 card 103c,104f rev 30 class 02,00,00
hdr 00
(II) PCI: 01:04:0: chip 103c,1008 card 0000,0000 rev 02 class 03,80,00
hdr 00
(II) PCI: End of PCI scan
(II) Host-to-PCI bridge:
(II) Host-to-PCI bridge:
(II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x00 (VGA_EN is
cleared)
(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]
(II) Bus 1: bridge is at (0:0:0), (-1,1,0), BCTRL: 0x00 (VGA_EN is
cleared)
(II) Bus 1 I/O range:
        [0] -1 0        0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) Bus 1 non-prefetchable memory range:
        [0] -1 0        0x00000000 - 0xffffffff (0x0) MX[B]
(II) Bus 1 prefetchable memory range:
        [0] -1 0        0x00000000 - 0xffffffff (0x0) MX[B]
(--) PCI: (1:4:0) HP unknown chipset (0x1008) rev 2, Mem @
0xf6000000/25, BIOS @
 0xf1e00000/21
(II) Addressable bus resource ranges are
        [0] -1 0        0x00000000 - 0xffffffff (0x0) MX[B]
        [1] -1 0        0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) OS-reported resource ranges:
        [0] -1 0        0xffffffff - 0xffffffff (0x1) MX[B]
        [1] -1 0        0x00000000 - 0x00000000 (0x1) MX[B]
        [2] -1 0        0x0000ffff - 0x0000ffff (0x1) IX[B]
        [3] -1 0        0x00000000 - 0x00000000 (0x1) IX[B]
(II) Active PCI resource ranges:
        [0] -1 0        0xf2fff000 - 0xf2fff07f (0x80) MX[B]
        [1] -1 0        0xf2ffe000 - 0xf2ffefff (0x1000) MX[B]
        [2] -1 0        0xf2ffd000 - 0xf2ffd0ff (0x100) MX[B]
        [3] -1 0        0xf1e00000 - 0xf1ffffff (0x200000) MX[B](B)
        [4] -1 0        0xf6000000 - 0xf7ffffff (0x2000000) MX[B](B)
        [5] -1 0        0x0000ff00 - 0x0000ff7f (0x80) IX[B]
        [6] -1 0        0x0000fe00 - 0x0000feff (0x100) IX[B]
(II) Active PCI resource ranges after removing overlaps:
        [0] -1 0        0xf2fff000 - 0xf2fff07f (0x80) MX[B]
        [1] -1 0        0xf2ffe000 - 0xf2ffefff (0x1000) MX[B]
        [2] -1 0        0xf2ffd000 - 0xf2ffd0ff (0x100) MX[B]
        [3] -1 0        0xf1e00000 - 0xf1ffffff (0x200000) MX[B](B)
        [4] -1 0        0xf6000000 - 0xf7ffffff (0x2000000) MX[B](B)
        [5] -1 0        0x0000ff00 - 0x0000ff7f (0x80) IX[B]
        [6] -1 0        0x0000fe00 - 0x0000feff (0x100) IX[B]
(II) OS-reported resource ranges after removing overlaps with PCI:
        [0] -1 0        0xffffffff - 0xffffffff (0x1) MX[B]
        [1] -1 0        0x00000000 - 0x00000000 (0x1) MX[B]
        [2] -1 0        0x0000ffff - 0x0000ffff (0x1) IX[B]
        [3] -1 0        0x00000000 - 0x00000000 (0x1) IX[B]
(II) All system resource ranges:
        [0] -1 0        0xffffffff - 0xffffffff (0x1) MX[B]
        [1] -1 0        0x00000000 - 0x00000000 (0x1) MX[B]
        [2] -1 0        0xf2fff000 - 0xf2fff07f (0x80) MX[B]
        [3] -1 0        0xf2ffe000 - 0xf2ffefff (0x1000) MX[B]
        [4] -1 0        0xf2ffd000 - 0xf2ffd0ff (0x100) MX[B]
        [5] -1 0        0xf1e00000 - 0xf1ffffff (0x200000) MX[B](B)
        [6] -1 0        0xf6000000 - 0xf7ffffff (0x2000000) MX[B](B)
        [7] -1 0        0x0000ffff - 0x0000ffff (0x1) IX[B]
        [8] -1 0        0x00000000 - 0x00000000 (0x1) IX[B]
        [9] -1 0        0x0000ff00 - 0x0000ff7f (0x80) IX[B]
        [10] -1 0       0x0000fe00 - 0x0000feff (0x100) IX[B]
(II) MGA: driver for Matrox chipsets: mga2064w, mga1064sg, mga2164w,
        mga2164w AGP, mgag100, mgag100 PCI, mgag200, mgag200 PCI,
mgag400
(II) GLINT: driver for 3Dlabs chipsets: gamma, ti_pm2, ti_pm, pm3, pm2v,
        pm2, pm, 300sx, 500tx, mx, delta
        S3VIdentify
(II) S3VIRGE: driver (version 1.6.0) for S3 ViRGE chipsets: virge,
86C325,
        virge vx, 86C988, virge dx, virge gx, 86C375, 86C385, virge gx2,
        86C357, virge mx, 86C260, virge mx+, 86C280, trio 3d, 86C365,
        trio 3d/2x, 86C362, 86C368
(II) SIS: driver for SiS chipsets: SIS5597, SIS5598, SIS530, SIS6326,
        SIS300, SIS630, SIS540
(II) SAVAGE: driver (version 1.1.16) for S3 Savage chipsets: Savage4,
        Savage3D, Savage3D-MV, Savage2000, Savage/MX-MV, Savage/MX,
        Savage/IX-MV, Savage/IX, ProSavage PM133, ProSavage KM133,
Twister,
        TwisterK
(II) TRIDENT: driver for Trident chipsets: tvga8900d, cyber9320,
cyber9388,
        cyber9397, cyber9397dvd, cyber9520, cyber9525dvd, cyberblade/e4,
        tgui9420dgi, tgui9440agi, tgui9660, tgui9680, providia9682,
        providia9685, cyber9382, cyber9385, 3dimage975, 3dimage985,
blade3d,
        cyberbladei7, cyberbladei7d, cyberbladei1, cyberbladei1d,
        cyberbladeAi1, cyberbladeAi1d, cyberbladeXP, cyberbladeXPm
(II) CHIPS: Driver for Chips and Technologies chipsets: ct65520,
ct65525,
        ct65530, ct65535, ct65540, ct65545, ct65546, ct65548, ct65550,
        ct65554, ct65555, ct68554, ct69000, ct69030, ct64200, ct64300
(II) TDFX: Driver for 3dfx Banshee/Voodoo3 chipsets: 3dfx Banshee,
        3dfx Voodoo3, 3dfx Voodoo5
(II) FBDev: driver for framebuffer: fbdev, afb
(II) ATI: ATI driver (version 6.3.6) for chipsets: ati
(II) R128: Driver for ATI Rage 128 chipsets: ATI Rage 128 RE (PCI),
        ATI Rage 128 RF (AGP), ATI Rage 128 RG (AGP), ATI Rage 128 RK
(PCI),
        ATI Rage 128 RL (AGP), ATI Rage 128 Pro PD (PCI),
        ATI Rage 128 Pro PF (AGP), ATI Rage 128 Pro PP (PCI),
        ATI Rage 128 Pro PR (PCI), ATI Rage 128 Mobility LE (PCI),
        ATI Rage 128 Mobility LF (AGP), ATI Rage 128 Mobility MF (AGP),
        ATI Rage 128 Mobility ML (AGP)
(II) RADEON: Driver for ATI Radeon chipsets: ATI Radeon QD (AGP),
        ATI Radeon QE (AGP), ATI Radeon QF (AGP), ATI Radeon QG (AGP),
        ATI Radeon VE (AGP)
(II) imstt: driver (version 1.0.0 for IMS TwinTurbo chipsets : imstt128,
        imstt3d
(II) VGA: Generic VGA driver (version 4.0) for chipsets: generic
(II) v4l driver for Video4Linux
        S3VProbe begin
(EE) No devices detected.

Fatal server error:
no screens found

When reporting a problem related to a server crash, please send
the full server output, not just the last messages.
This can be found in the log file "/var/log/XFree86.0.log".
Please report problems to submit@bugs.debian.org.

Re: [parisc-linux] What keywords should I use to find the answer?

[Grant Grundler]

"Edward Alfert" wrote:
> Thanks... This is fun... 

cool!

> New kernel 2.4.19 is up and running... I'm able to use my monitor ...
> Initially I couldn't log in but found in the FAQ that I needed to
> "uncomment" tty0 from /etc/inittab ... By the way, there is no entry for
> tty0 in /etc/inittab, so I created one... So the FAQ shouldn't read
> "uncomment" but instead "create".

I punt. Met my web site hacking quota for the day...some substantial
updates to the 0.9.3 errata:
	http://www.parisc-linux.org/release-0.9/errata-093.html

(You do want to know how to avoid file corruption right?)

> The system is a C240 with FX4 video card (that's HP Visualize FX-4 with
> 18mb RAM) ... The GRAPHICS(4) is set to 1280 x 1024 @ 72Hz.

I don't think FX-4 is supported yet. Helger Deller or Thomas Bogendoerf
should be able to confirm in a few hours if no one else can.
Looks like we could use a seperate table for unsupported IO devices
and supported gfx on:
	http://www.parisc-linux.org/release-0.9/systems-093.html

grant

RE: [parisc-linux] What keywords should I use to find the answer?

[Edward Alfert]

Ok... So I'm experimenting with leaving the fx4 for booting and
interacting in text mode (/dev/tty0) and then I installed a PCI voodoo 3
in graphics pci slot number 1.   the fx4 is in slot 4.

I reran /usr/X11R6/bin/xf86config and entered the new information.

When executing startx, it probes the hardware and sees both the FX4
(which it doesn't know what it is), and it also sees the Voodoo 3 which
it identifies correctly.

But it still fails to start the server.  Same error messages:
       (EE) No devices detected.
       Fatal server error:
       no screens found

Any ideas if this is possible.. Have 2 video cards and use the supported
one for gui?

> 
> > The system is a C240 with FX4 video card (that's HP Visualize FX-4 
> > with 18mb RAM) ... The GRAPHICS(4) is set to 1280 x 1024 @ 72Hz.
> 
> I don't think FX-4 is supported yet. Helger Deller or Thomas 
> Bogendoerf should be able to confirm in a few hours if no one 
> else can. Looks like we could use a seperate table for 
> unsupported IO devices and supported gfx on:
> 	http://www.parisc-linux.org/release-0.9/systems-093.html
> 

[parisc-linux] fs corruption

[Michael Wood]

On Thu, Dec 13, 2001 at 10:25:32PM -0700, Grant Grundler wrote:
[snip]
> I punt. Met my web site hacking quota for the day...some substantial
> updates to the 0.9.3 errata:
> 	http://www.parisc-linux.org/release-0.9/errata-093.html
> 
> (You do want to know how to avoid file corruption right?)
[snip]

Oh I'm glad that's fixed :)  I was seeing fs corruption on a
D270 with an NCR53c720 and wasn't sure if it was the hardware or
the kernel or something stupid I had done :)

-- 
Michael Wood <mwood@its.uct.ac.za>

Re: [parisc-linux] What keywords should I use to find the answer?

[Grant Grundler]

Helge Deller wrote:
> (PS: This should be added to the 0.9.3 FAQ!)

(Re C3000/VizEG incompatibility and Vis-EG support on older boxes))

I'm almost done adding a note about that now.
Please review later today when the official website
has been updated.

thanks!
grant

[parisc-linux] What keywords should I use to find the answer?

[Edward Alfert]

#1) I successfully installed 0.9.3 on a C240!!!
#2) it works if I use the serial console.  Absolutely no problems... Was
able to use dselect after install to install graphical environment (x11,
gnome, and kde)
#3) I want to use a graphical console (my color monitor) that does
support the following resolutions 1280 x 1024 @ 72 , 1280 x 1024 @ 75,
and 1024 x 768 @ 72.
#4) if disconnect the serial connection, plug in the ps2 mouse and ps2
keyboard and the monitor to the graphics card (system detects Console
path: Graphics(4))
#5) the system gets as far as:
Branching to kernel entry point 0x00100000.  If this is the last
message you see, you may need to switch your console.  This is
a common symptom -- search the FAQ and mailing list at parisc-linux.org

A) the FAQ is short and I can't find any reference. I have read it
several time. either it's not there or I'm blind
B) I tried searching the lists on parisc-linux.org but the search
feature doesn't return any hits for "0x00100000" or "switch your
console"
C) I manually searched over 1 years' worth of archives but didn't find
an answer

?) Does 0.9.3 support the graphics card on a c240? Or only serial?
?) If only serial, how do you get a gui environment like gnome of kde to
interact with this version of linux?
?) am I just clueless?

Thanks for any and all feedback...
----------------------
http://www.sysadmin.info/
HP-UX SysAdmin Information