* [parisc-linux] Failed boot on D310
@ 2001-06-03 13:33 djweis
2001-06-03 13:57 ` Richard Hirst
0 siblings, 1 reply; 8+ messages in thread
From: djweis @ 2001-06-03 13:33 UTC (permalink / raw)
To: parisc-linux
I've got a D310 with a 100mhz processor and 128 megs of RAM. I tried to
boot the ISO version 0.9 last night, but it crashed on boot. I can get the
exact error messages, it looked like a register dump.
Is there any reason to assume that this will or won't boot?
dave
--
Dave Weis "I believe there are more instances of the abridgement
djweis@sjdjweis.com of the freedom of the people by gradual and silent
encroachments of those in power than by violent
and sudden usurpations."- James Madison
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [parisc-linux] Failed boot on D310
2001-06-03 13:33 [parisc-linux] Failed boot on D310 djweis
@ 2001-06-03 13:57 ` Richard Hirst
2001-06-03 17:41 ` djweis
0 siblings, 1 reply; 8+ messages in thread
From: Richard Hirst @ 2001-06-03 13:57 UTC (permalink / raw)
To: djweis; +Cc: parisc-linux
On Sun, Jun 03, 2001 at 08:33:23AM -0500, djweis@sjdjweis.com wrote:
>
> I've got a D310 with a 100mhz processor and 128 megs of RAM. I tried to
> boot the ISO version 0.9 last night, but it crashed on boot. I can get the
> exact error messages, it looked like a register dump.
>
> Is there any reason to assume that this will or won't boot?
Listed as untested on http://parisc-linux.org/release-0.9/systems.html
Are you trying the serial or sti image? If you can use serial, and
get you terminal emulator to capture the boot messages and crash for us,
that would help.
Thanks,
Richard
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [parisc-linux] Failed boot on D310
2001-06-03 13:57 ` Richard Hirst
@ 2001-06-03 17:41 ` djweis
2001-06-03 18:29 ` Richard Hirst
0 siblings, 1 reply; 8+ messages in thread
From: djweis @ 2001-06-03 17:41 UTC (permalink / raw)
To: Richard Hirst; +Cc: parisc-linux
On Sun, 3 Jun 2001, Richard Hirst wrote:
> On Sun, Jun 03, 2001 at 08:33:23AM -0500, djweis@sjdjweis.com wrote:
> > I've got a D310 with a 100mhz processor and 128 megs of RAM. I tried to
> > boot the ISO version 0.9 last night, but it crashed on boot. I can get the
> > exact error messages, it looked like a register dump.
> >
> > Is there any reason to assume that this will or won't boot?
> Listed as untested on http://parisc-linux.org/release-0.9/systems.html
> Are you trying the serial or sti image? If you can use serial, and
> get you terminal emulator to capture the boot messages and crash for us,
> that would help.
It's headless, I was using the serial image. Below is my terminal output
Main Menu: Enter command > search
Searching for potential boot
device(s)... This may take several
minutes. To
discontinue search, press any key (termination may not be
immediate). Path
Number Device Path (dec) Device Type
----------- ----------------- -----------
P0 4.5 Random access media
P1 4.11 Random access media
P2 4.10 Random access media
P3 4.9 Random access media
P4 4.8 Random access media
P5 16/5.2 Random access media
P6 16/5.0 Sequential access media
P7 16/6.0 LAN Module
Main Menu: Enter command > boot P5
Interact with IPL (Y or N)?> n
Booting...
Boot IO Dependent Code (IODC) revision 1
WARN 80F9
Cannot find ENTRY_TEST.
WARN 80F7
Failed I/O operation with
ENTRY_IO
Status = -4
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00004001 00000028 E8040782 01000084 800400DC 00000000 0025F040 00000000
98080000 0000DA2C 0000DA2C 00000000 00000002 00000003 00000011 00000005
WARN C7F0
Error Reading IPL
Thanks for any help.
dave
--
Dave Weis "I believe there are more instances of the abridgement
djweis@sjdjweis.com of the freedom of the people by gradual and silent
encroachments of those in power than by violent
and sudden usurpations."- James Madison
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [parisc-linux] Failed boot on D310
2001-06-03 17:41 ` djweis
@ 2001-06-03 18:29 ` Richard Hirst
2001-06-03 21:33 ` djweis
2001-06-03 22:44 ` djweis
0 siblings, 2 replies; 8+ messages in thread
From: Richard Hirst @ 2001-06-03 18:29 UTC (permalink / raw)
To: djweis; +Cc: parisc-linux
On Sun, Jun 03, 2001 at 12:41:46PM -0500, djweis@sjdjweis.com wrote:
>
> On Sun, 3 Jun 2001, Richard Hirst wrote:
> > On Sun, Jun 03, 2001 at 08:33:23AM -0500, djweis@sjdjweis.com wrote:
> > > I've got a D310 with a 100mhz processor and 128 megs of RAM. I tried to
> > > boot the ISO version 0.9 last night, but it crashed on boot. I can get the
> > > exact error messages, it looked like a register dump.
> > >
> > > Is there any reason to assume that this will or won't boot?
> > Listed as untested on http://parisc-linux.org/release-0.9/systems.html
> > Are you trying the serial or sti image? If you can use serial, and
> > get you terminal emulator to capture the boot messages and crash for us,
> > that would help.
>
> It's headless, I was using the serial image. Below is my terminal output
>
> Main Menu: Enter command > search
> Searching for potential boot
> device(s)... This may take several
> minutes. To
> discontinue search, press any key (termination may not be
> immediate). Path
> Number Device Path (dec) Device Type
> ----------- ----------------- -----------
> P0 4.5 Random access media
> P1 4.11 Random access media
> P2 4.10 Random access media
> P3 4.9 Random access media
> P4 4.8 Random access media
> P5 16/5.2 Random access media
> P6 16/5.0 Sequential access media
> P7 16/6.0 LAN Module
> Main Menu: Enter command > boot P5
> Interact with IPL (Y or N)?> n
>
> Booting...
> Boot IO Dependent Code (IODC) revision 1
> WARN 80F9
> Cannot find ENTRY_TEST.
> WARN 80F7
> Failed I/O operation with
> ENTRY_IO
> Status = -4
>
> 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> 00004001 00000028 E8040782 01000084 800400DC 00000000 0025F040 00000000
> 98080000 0000DA2C 0000DA2C 00000000 00000002 00000003 00000011 00000005
> WARN C7F0
> Error Reading IPL
Ah, I'd assumed it got as far as starting the kernel and then the
kernel crashed. In this case I think it has failed reading the
CD. Can you read the CD on some other system to check it burned
ok? Are you confident that the CD drive is P5 and is working?
An alternative is to boot the relevant lifimage over the network,
and then either install from the network or from the CD (if the
net booted kernel sees the CD). See the REAME on the CD for details.
Richard
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [parisc-linux] Failed boot on D310
2001-06-03 18:29 ` Richard Hirst
@ 2001-06-03 21:33 ` djweis
2001-06-03 22:44 ` djweis
1 sibling, 0 replies; 8+ messages in thread
From: djweis @ 2001-06-03 21:33 UTC (permalink / raw)
To: Richard Hirst; +Cc: parisc-linux
On Sun, 3 Jun 2001, Richard Hirst wrote:
> On Sun, Jun 03, 2001 at 12:41:46PM -0500, djweis@sjdjweis.com wrote:
> > On Sun, 3 Jun 2001, Richard Hirst wrote:
> > > On Sun, Jun 03, 2001 at 08:33:23AM -0500, djweis@sjdjweis.com wrote:
> > > > I've got a D310 with a 100mhz processor and 128 megs of RAM. I tried to
> > > > boot the ISO version 0.9 last night, but it crashed on boot. I can get the
> > > > exact error messages, it looked like a register dump.
> > > >
> > > > Is there any reason to assume that this will or won't boot?
> > > Listed as untested on http://parisc-linux.org/release-0.9/systems.html
> > > Are you trying the serial or sti image? If you can use serial, and
> > > get you terminal emulator to capture the boot messages and crash for us,
> > > that would help.
> >
> > It's headless, I was using the serial image. Below is my terminal output
> >
> Ah, I'd assumed it got as far as starting the kernel and then the
> kernel crashed. In this case I think it has failed reading the
> CD. Can you read the CD on some other system to check it burned
> ok? Are you confident that the CD drive is P5 and is working?
I'll give that a try. It's definitely P5, I tried P0 a few times and
noticed that hpux kept booting. According to the legend inside the drive
cover, P5 is correct.
The cd did mount and read fine on another machine.
> An alternative is to boot the relevant lifimage over the network,
> and then either install from the network or from the CD (if the
> net booted kernel sees the CD). See the REAME on the CD for details.
I'll give that a try.
dave
--
Dave Weis "I believe there are more instances of the abridgement
djweis@sjdjweis.com of the freedom of the people by gradual and silent
encroachments of those in power than by violent
and sudden usurpations."- James Madison
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [parisc-linux] Failed boot on D310
2001-06-03 18:29 ` Richard Hirst
2001-06-03 21:33 ` djweis
@ 2001-06-03 22:44 ` djweis
2001-06-04 10:39 ` Richard Hirst
1 sibling, 1 reply; 8+ messages in thread
From: djweis @ 2001-06-03 22:44 UTC (permalink / raw)
To: Richard Hirst; +Cc: parisc-linux
On Sun, 3 Jun 2001, Richard Hirst wrote:
> On Sun, Jun 03, 2001 at 12:41:46PM -0500, djweis@sjdjweis.com wrote:
> > On Sun, 3 Jun 2001, Richard Hirst wrote:
> > > On Sun, Jun 03, 2001 at 08:33:23AM -0500, djweis@sjdjweis.com wrote:
> > > > I've got a D310 with a 100mhz processor and 128 megs of RAM. I trie=
d to
> > > > boot the ISO version 0.9 last night, but it crashed on boot. I can =
get the
> > > > exact error messages, it looked like a register dump.=20
> > > >=20
> Ah, I'd assumed it got as far as starting the kernel and then the
> kernel crashed. In this case I think it has failed reading the
> CD. Can you read the CD on some other system to check it burned
> ok? Are you confident that the CD drive is P5 and is working?
Okay, I managed to get bootp and tftp set up enough to get an image over
the wire. It did get into the kernel after a while and here are the boot
messages:
Main Menu: Enter command > boot lan =
Interact with IPL (Y or N)?> n =
=
Booting... =
Network Station Address 080009-ae8800 =
=
Boot IO Dependent Code (IODC) revision 2 =
=
=
HARD Booted. =
palo ipl bame@palinux Fri=
May 11 16:10:29 MDT 2001 0/vmlinux 2622963 by=
tes @ 0x6800 0/palo-cmdline =
'0/vmlinux HOME=3D/ TERM=3Dlinux root=3D/dev/ram initrd=3D0/ramdisk cons'0/=
ramdisk 1678201 bytes @ 0x286df3 =
Kernel: partition 0 file /vmlinux =
Ramdisk: partition 0 file /ramdisk =
ELF32 executable =
Entry 00100000 first 00100000 n 4 =
Segment 0 load 00100000 size 1469948 mediaptr 0x1000=
Segment 1 load 00268000 size 192312 mediaptr 0x=
168000 Segment 2 load 00298000 size 221184 mediap=
tr 0x197000 Segment 3 load 002fa7c8 size 73264 me=
diaptr 0x1cd7c8 Loading ramdisk 1678201 bytes @ =
07e55000... branching to kernel entry p=
oint 0x00100000 Set default PSW W bit =
to 0 PDC Console Initi=
alized Linux versio=
n 2.4.0-pa10 (root@slab) (gcc version 3.0 20010315 (prerelease)) #11FP[0] e=
nabled: Rev 1 Model 13 Th=
e 32-bit Kernel has started... =
=20
Determining PDC firmware type: Newer Box =
setup_cmdline(0x64cc4,0x64cc4,0x7e55000,0x7feeb79) =
PALO command line: 'HOME=3D/ TERM=3Dlinux root=3D/dev/ram console=
=3DttyS0' PALO initrd 7e55000-7feeb79 =
model 00004840 00000481 00000000 00000000 773=
61cea 100000f0 00000004 000000722vers 0000000c =
CPUID vers 0 rev 0 =
model 9000/811/D310 =
Total Memory: 128 Mb =
initrd: 17e55000-17fee=
b79 pagetable_init =
On node 0 to=
talpages: 32768 zone(0)=
: 32768 pages. zo=
ne(1): 0 pages. =
zone(2): 0 pages. =
Searching for devices... =
Found devices: =
1. UL 550 Lasi Core BA (11) at 0xf0100000, versions 0x2f,=
0x0, 0x81, 0x0, 0x0, 2. UL 550 Core SCSI (10) at 0xf0106000, versions 0x2=
f, 0x0, 0x82, 0x0, 0x0 3. UL 350 Core LAN (802.3) (10) at 0xf0107000, =
versions 0x2f, 0x0, 0x8a, 0x0, 004. UL 550 Core Centronics (10) at 0xf01020=
00, versions 0x2f, 0x0, 0x74, 0x0, 0x 5. UL 550 Core PC Keyboard (10) at 0x=
f0108000, versions 0x2f, 0x0, 0x84, 0x0, 006. UL 550 Core PC Keyboard (10) =
at 0xf0108100, versions 0x2f, 0x0, 0x84, 0x0, 007. UL 550 Core Wax BA (11) =
at 0xffe00000, versions 0x31, 0x0, 0x8e, 0x0, 0x0 8. UL 550 Wax Core RS-=
232 (10) at 0xffe02000, versions 0x31, 0x0, 0x8c, 0x0, 0x09. UL 550 Wax EIS=
A BA (11) at 0xfc000000, versions 0x31, 0x0, 0x90, 0x0, 0x0, 10. Gecko BO=
A BC GSC+ Port (7) at 0xfff80000, versions 0x500, 0x0, 0xc, 0x0, 0x011. Blu=
efish Add-on FW-SCSI (4) at 0xfff84000, versions 0x13, 0x1, 0x89, 0x0, 0012=
=2E Unknown device (0) at 0xfffbe000, versions 0x484, 0x0, 0x4, 0x0, 0x81 =
13. UL Proc L 100 (1) at 0xfffbf000, versions 0x57, 0x0, 0x9, 0x0, 0x0=
That's a total of 13 devices. =
CPU(s): 1 x PA7100LC (PCX-L) at 100.000000 MHz =
Kernel command line: HOME=3D/ TERM=3Dlinux root=3D/dev/=
ram console=3DttyS0 Calibrating delay loop... 99.73 BogoMIPS =
Memory: 125076k available =
Dentry-cache hash table entries:=
16384 (order: 5, 131072 bytes) Buffer-cache hash table ent=
ries: 4096 (order: 2, 16384 bytes) Page-cache hash table =
entries: 32768 (order: 5, 131072 bytes) Inode-cache hash =
table entries: 8192 (order: 4, 65536 bytes) POSIX confor=
mance testing by UNIFIX Lasi ve=
rsion 0 at 0xf0100000 found. Wa=
x at 0xffe00000 found. =
Wax: HIL Keyboard-NMI registered. =
Wax EISA bus adapter version 0x5761 at 0xffe00000 =
Initializing Lasi PS/2-keyboard port at 0xf0108000... =
Support for Lasi PS/2-psaux not yet available ! =
Found i82596 at 0xf0107000, IRQ 87 =
early initialization of device eth0 is deferred=
Linux NET4.0 for Linux 2.4 =
Based upon Swansea University Compute=
r Society NET3.039 Starting kswapd v1.8 =
pty: 25<4>Lasi PS/2 transmi=
t buffer timeout Lasi PS/2 transmit buf=
fer timeout PS/2 transmit bu=
ffer timrequest_module[parport_lowlevel]: Root fs not mounted lp: driver l=
oaded but no devices found RAMDISK=
driver initialized: 16 RAM disks of 4096K size 1024 blocksize et=
h0: 82596 at 0xf0107000, 08 00 09 AE 88 00 IRQ 87. =
82596.c $Revision: 1.18 $ =
RAMDISK: Compressed image found at block 0 =
Serial driver version 5.02 (2000-08-09) with MANY_PORTS SHARE_=
IRQ SERIAL_PCI endttyS00 at iomem 0xffe02800 (irq =3D 121) is a 16550A =
=
=20
There doesn't seem to be linefeeds at the end of the line, I hope it
wraps correctly.
The mac address was read correctly. The ttyS00 line is the last thing to
be printed.
dave
--=20
Dave Weis "I believe there are more instances of the abridgemen=
t
djweis@sjdjweis.com of the freedom of the people by gradual and silent
encroachments of those in power than by violent=20
and sudden usurpations."- James Madison
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [parisc-linux] Failed boot on D310
2001-06-03 22:44 ` djweis
@ 2001-06-04 10:39 ` Richard Hirst
2001-06-04 11:47 ` djweis
0 siblings, 1 reply; 8+ messages in thread
From: Richard Hirst @ 2001-06-04 10:39 UTC (permalink / raw)
To: djweis; +Cc: parisc-linux
On Sun, Jun 03, 2001 at 05:44:33PM -0500, djweis@sjdjweis.com wrote:
>
> On Sun, 3 Jun 2001, Richard Hirst wrote:
> > On Sun, Jun 03, 2001 at 12:41:46PM -0500, djweis@sjdjweis.com wrote:
> > > On Sun, 3 Jun 2001, Richard Hirst wrote:
> > > > On Sun, Jun 03, 2001 at 08:33:23AM -0500, djweis@sjdjweis.com wrote:
> > > > > I've got a D310 with a 100mhz processor and 128 megs of RAM. I tried to
> > > > > boot the ISO version 0.9 last night, but it crashed on boot. I can get the
> > > > > exact error messages, it looked like a register dump.
> > > > >
>
> > Ah, I'd assumed it got as far as starting the kernel and then the
> > kernel crashed. In this case I think it has failed reading the
> > CD. Can you read the CD on some other system to check it burned
> > ok? Are you confident that the CD drive is P5 and is working?
>
> Okay, I managed to get bootp and tftp set up enough to get an image over
> the wire. It did get into the kernel after a while and here are the boot
> messages:
I've untangled the formatting to make them more readable:
Main Menu: Enter command > boot lan
Interact with IPL (Y or N)?> n
Booting...
Network Station Address 080009-ae8800
Boot IO Dependent Code (IODC) revision 2
HARD Booted.
palo ipl bame@palinux Fri May 11 16:10:29 MDT 2001
/vmlinux 2622963 bytes @ 0x6800
/palo-cmdline '0/vmlinux HOME=/ TERM=linux root=/dev/ram initrd=0/ramdisk cons'0/ramdisk 1678201 bytes @ 0x286df3
Kernel: partition 0 file /vmlinux
Ramdisk: partition 0 file /ramdisk
ELF32 executable
Entry 00100000 first 00100000 n 4
Segment 0 load 00100000 size 1469948 mediaptr 0x1000
Segment 1 load 00268000 size 192312 mediaptr 0x168000
Segment 2 load 00298000 size 221184 mediaptr 0x197000
Segment 3 load 002fa7c8 size 73264 mediaptr 0x1cd7c8
Loading ramdisk 1678201 bytes @ 07e55000...
branching to kernel entry point 0x00100000
Set default PSW W bit to 0
PDC Console Initialized
Linux version 2.4.0-pa10 (root@slab) (gcc version 3.0 20010315 (prerelease)) #11
FP[0] enabled: Rev 1 Model 13
The 32-bit Kernel has started...
Determining PDC firmware type: Newer Box
setup_cmdline(0x64cc4,0x64cc4,0x7e55000,0x7feeb79)
PALO command line: 'HOME=/ TERM=linux root=/dev/ram console=ttyS0'
PALO initrd 7e55000-7feeb79
model 00004840 00000481 00000000 00000000 77361cea 100000f0 00000004 000000722
vers 0000000c
CPUID vers 0 rev 0
model 9000/811/D310
Total Memory: 128 Mb
initrd: 17e55000-17feeb79
pagetable_init
On node 0 totalpages: 32768
zone(0): 32768 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Searching for devices...
Found devices:
1. UL 550 Lasi Core BA (11) at 0xf0100000, versions 0x2f, 0x0, 0x81, 0x0, 0x0,
2. UL 550 Core SCSI (10) at 0xf0106000, versions 0x2f, 0x0, 0x82, 0x0, 0x0
3. UL 350 Core LAN (802.3) (10) at 0xf0107000, versions 0x2f, 0x0, 0x8a, 0x0, 00
4. UL 550 Core Centronics (10) at 0xf0102000, versions 0x2f, 0x0, 0x74, 0x0, 0x
5. UL 550 Core PC Keyboard (10) at 0xf0108000, versions 0x2f, 0x0, 0x84, 0x0, 00
6. UL 550 Core PC Keyboard (10) at 0xf0108100, versions 0x2f, 0x0, 0x84, 0x0, 00
7. UL 550 Core Wax BA (11) at 0xffe00000, versions 0x31, 0x0, 0x8e, 0x0, 0x0
8. UL 550 Wax Core RS-232 (10) at 0xffe02000, versions 0x31, 0x0, 0x8c, 0x0, 0x0
9. UL 550 Wax EISA BA (11) at 0xfc000000, versions 0x31, 0x0, 0x90, 0x0, 0x0,
10. Gecko BOA BC GSC+ Port (7) at 0xfff80000, versions 0x500, 0x0, 0xc, 0x0, 0x0
11. Bluefish Add-on FW-SCSI (4) at 0xfff84000, versions 0x13, 0x1, 0x89, 0x0, 00
12. Unknown device (0) at 0xfffbe000, versions 0x484, 0x0, 0x4, 0x0, 0x81
13. UL Proc L 100 (1) at 0xfffbf000, versions 0x57, 0x0, 0x9, 0x0, 0x0
That's a total of 13 devices.
CPU(s): 1 x PA7100LC (PCX-L) at 100.000000 MHz
Kernel command line: HOME=/ TERM=linux root=/dev/ram console=ttyS0
Calibrating delay loop... 99.73 BogoMIPS
Memory: 125076k available
Dentry-cache hash table entries: 16384 (order: 5, 131072 bytes)
Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes)
Page-cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 8192 (order: 4, 65536 bytes)
POSIX conformance testing by UNIFIX
Lasi version 0 at 0xf0100000 found.
Wax at 0xffe00000 found.
Wax: HIL Keyboard-NMI registered.
Wax EISA bus adapter version 0x5761 at 0xffe00000
Initializing Lasi PS/2-keyboard port at 0xf0108000...
Support for Lasi PS/2-psaux not yet available !
Found i82596 at 0xf0107000, IRQ 87
early initialization of device eth0 is deferred
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Starting kswapd v1.8
pty: 25<4>Lasi PS/2 transmit buffer timeout
Lasi PS/2 transmit buffer timeout
PS/2 transmit buffer timrequest_module[parport_lowlevel]: Root fs not mounted
lp: driver loaded but no devices found
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
eth0: 82596 at 0xf0107000, 08 00 09 AE 88 00 IRQ 87.
82596.c $Revision: 1.18 $
RAMDISK: Compressed image found at block 0
Serial driver version 5.02 (2000-08-09) with MANY_PORTS SHARE_IRQ SERIAL_PCI end
ttyS00 at iomem 0xffe02800 (irq = 121) is a 16550A
> There doesn't seem to be linefeeds at the end of the line, I hope it
> wraps correctly.
If you are using minicom, do 'ctrl-Z w' (assuming ctrl-z is the attention
char). That turns on line wrap, so the output isn't truncated at 80 chars.
Also, 'ctrl-Z l' will let you turn on logging to a file.
> The mac address was read correctly. The ttyS00 line is the last thing to
> be printed.
For reference, my 715/old, which seems to have a similar initialisation
order to your system, continues something like this:
Serial driver version 5.02 (2000-08-09) with MANY_PORTS SHARE_IRQ SERIAL_PCI ena bled
ttyS00 at iomem 0xf0823800 (irq = 90) is a 16550A
ttyS01 at iomem 0xf0822800 (irq = 89) is a 16550A
Generic RTC Driver v1.02 05/27/1999 Sam Creasey (sammy@oh.verio.com)
parport_init_chip: enhanced parport-modes not supported.
parport0: PC-style at 0xf0824800, irq 88 [PCSPP]
lp0: using parport0 (interrupt-driven).
SCSI subsystem driver Revision: 1.00
I wonder whether the serial driver has done something which killed
the serial port. My approach would be to set up a cross-compile
environment to build kernels with printk debugging to see where
it actually stops. Don't know if you fancy doing that though...
Richard
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [parisc-linux] Failed boot on D310
2001-06-04 10:39 ` Richard Hirst
@ 2001-06-04 11:47 ` djweis
0 siblings, 0 replies; 8+ messages in thread
From: djweis @ 2001-06-04 11:47 UTC (permalink / raw)
To: Richard Hirst; +Cc: parisc-linux
On Mon, 4 Jun 2001, Richard Hirst wrote:
> On Sun, Jun 03, 2001 at 05:44:33PM -0500, djweis@sjdjweis.com wrote:
> > On Sun, 3 Jun 2001, Richard Hirst wrote:
> > > On Sun, Jun 03, 2001 at 12:41:46PM -0500, djweis@sjdjweis.com wrote:
> > > > On Sun, 3 Jun 2001, Richard Hirst wrote:
> > > > > On Sun, Jun 03, 2001 at 08:33:23AM -0500, djweis@sjdjweis.com wrote:
> > > > > > I've got a D310 with a 100mhz processor and 128 megs of RAM. I tried to
> > > > > > boot the ISO version 0.9 last night, but it crashed on boot. I can get the
> > > > > > exact error messages, it looked like a register dump.
> > > Ah, I'd assumed it got as far as starting the kernel and then the
> > > kernel crashed. In this case I think it has failed reading the
> > > CD. Can you read the CD on some other system to check it burned
> > > ok? Are you confident that the CD drive is P5 and is working?
> >
> > Okay, I managed to get bootp and tftp set up enough to get an image over
> > the wire. It did get into the kernel after a while and here are the boot
> > messages:
>
> I've untangled the formatting to make them more readable:
>
> RAMDISK: Compressed image found at block 0
> Serial driver version 5.02 (2000-08-09) with MANY_PORTS SHARE_IRQ SERIAL_PCI end
> ttyS00 at iomem 0xffe02800 (irq = 121) is a 16550A
Good news, I noticed after a few boots that the hd access lights were
sequentially lighting up. It does make it into userspace because...
> I wonder whether the serial driver has done something which killed
> the serial port. My approach would be to set up a cross-compile
> environment to build kernels with printk debugging to see where
> it actually stops. Don't know if you fancy doing that though...
Already have it going. I grabbed nfsroot-small from the ftp server and it
does mount successfully. It kind of looks like it may be a mismatch
between my console= line for palo and the actual /dev tree. There was
another message to the list on the same thing earlier this AM. I'll try to
play with it tonite again.
Thanks for the help
dave
--
Dave Weis "I believe there are more instances of the abridgement
djweis@sjdjweis.com of the freedom of the people by gradual and silent
encroachments of those in power than by violent
and sudden usurpations."- James Madison
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2001-06-04 11:46 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-06-03 13:33 [parisc-linux] Failed boot on D310 djweis
2001-06-03 13:57 ` Richard Hirst
2001-06-03 17:41 ` djweis
2001-06-03 18:29 ` Richard Hirst
2001-06-03 21:33 ` djweis
2001-06-03 22:44 ` djweis
2001-06-04 10:39 ` Richard Hirst
2001-06-04 11:47 ` djweis
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.