kernel compile
I have been trying to get linux-2.4.20-pa23 to work with my j2240. For awhile now I thought it was the console, but it isn't it is the kernel. Here are the steps I took:
Got the box running with debian kernel 2.4.17-32, updated to 2.4.18-32, and everything was working fine. I took the config from 2.4.18-32 and
used that as my starting point for 2.4.20-pa23
ran make dep and make vmlinux; made and installed the modules
The box just stops at the branching message. Let me note the console is set properly. I posted here before but think I was ignored becuase it was assumed I hadn't read the faq. Please I have read the faq, I just need help I would love to get this box working with a recent kernel and not have to depend on the packaged debian kernels.
Thanks.
Signature · 4 lines
Aaron St. Pierre tel: 978.828.6177 [email protected] Increased knowledge will help you now. Have mate's phone bugged.
Quoted 2 lines · Aaron St. Pierre
I took the config from 2.4.18-32
and used that as my starting point for 2.4.20-pa23
Can you:
# mv .config ../config-orig # yes "" | make oldconfig (or something like that)
The default kernel should work on j2240.
grant
ps. FAQ has a link to "how to report kernel bugs"
http://www.parisc-linux.org/faq/index.html#kernelbugreport
First, thanks for the response, I really appreciate it.
I setup a page with all of the information from the "basics" section of the faq. That page is : http://hadron.dyndns.org/parisc/
Grant, I did as you said, and the same thing happened. What disturbs me is when it stopped at the brancing message and I waited about 15 minutes then pressed the toc button there was still nothing in the pim ( I cleared it prior to boot) I hope this doesn't mean the kernel isn't even loading and it has something to do with palo.
Maybe I am once again making this too complicated. If I left anything out let me know and I will add it.
Thanks again for your help. :)
Quoted 15 lines · In another life Grant Grundler
Quoted 2 lines · Aaron St. Pierre
I took the config from 2.4.18-32
and used that as my starting point for 2.4.20-pa23Can you:
# mv .config ../config-orig # yes "" | make oldconfig (or something like that)The default kernel should work on j2240.
grant
ps. FAQ has a link to "how to report kernel bugs"
http://www.parisc-linux.org/faq/index.html#kernelbugreport
Signature · 4 lines
Aaron St. Pierre tel: 978.828.6177 [email protected] A day without sunshine is like a day without orange juice.
Quoted 2 lines · Aaron St. Pierre
I setup a page with all of the information from the "basics" section of the faq. That page is : http://hadron.dyndns.org/parisc/
very good.
j2240 is pa8200 - ie 64-bit capable.
But don't use 64-bit kernel unless you know why you need to.
Quoted 5 lines
Grant, I did as you said, and the same thing happened. What disturbs me is when it stopped at the brancing message and I waited about 15 minutes then pressed the toc button there was still nothing in the pim ( I cleared it prior to boot) I hope this doesn't mean the kernel isn't even loading and it has something to do with palo.
your PIM dump only has the HPMC/memory/IO sections. Didn't "ser pim" give you LPMC and TOC sections too?
Secondly, since your j2240 is dual CPU, the PIM dump should contain the same info (HPMC, LPMC, TOC) for both CPUs.
Can you check if you firmware is anywhere near the current? (See http://www.parisc-linux.org/faq/index.html#PDCupdate)
And the following from your log worries me despite the "ignore" part:
| Information: Boot device can't seek past 2Gb (ignore next error). | byteio_read: seekread() returned -1 expected 2048
But nothing else indicated a problem loading the vmlinux. I just don't see that when booting my a500.
It could be a difference in how palo interacts with IODC.
If you don't get any other hot tips, start disabling things in the .config that you don't need: Parport, SBA/LBA/IOSAPIC, USB, LCD/LED support, wireless, extra lan/scsi drivers, etc.
grant
Quoted 3 lines · Grant Grundler
If you don't get any other hot tips, start disabling things in the .config that you don't need: Parport, SBA/LBA/IOSAPIC, USB, LCD/LED support, wireless, extra lan/scsi drivers, etc.
I forgot to mention STI drivers - ditch those if you are using serial console even though I doubt they are the problem.
grant
Yea I missed that one. With this version of the firmware you have to request the specific PIM, HPMC, LPMC, TOC. Anyway I got the the TOC information for both processors after I tried to boot my kernel. It is all on that page ( http://hadron.dyndns.org/parisc/ )
I also added a link to the firmware. I am running 2.0 of the firmware and according to hp the most recent is 2.1 or :
Patch Name: /firmware_patches/hp/cpu/PF_CJ224021
Description: HP 9000 Model J2240 firmware 2.1 patch
Date : 00/10/06
I will start popping stuff out of the kernel, although I am sure I took out all of the stuff wrt graphics. Another try for persistance sake wont hurt :)
As far as the palo message, i only started noticing it when I went to v1.2 of palo. One thing I should note, when I set up / i made it ext3, boot is off of / and not its own fs so when i realized what i did I just changed fstab accordingly so it would mount as ext2, although that couldn't be the problem either since it is loading the debian kernels. Perhaps sleep is in order ?
:)
Quoted 42 lines · In another life Grant Grundler
Quoted 2 lines · Aaron St. Pierre
I setup a page with all of the information from the "basics" section of the faq. That page is : http://hadron.dyndns.org/parisc/
very good.
j2240 is pa8200 - ie 64-bit capable.
But don't use 64-bit kernel unless you know why you need to.Quoted 5 lines
Grant, I did as you said, and the same thing happened. What disturbs me is when it stopped at the brancing message and I waited about 15 minutes then pressed the toc button there was still nothing in the pim ( I cleared it prior to boot) I hope this doesn't mean the kernel isn't even loading and it has something to do with palo.
your PIM dump only has the HPMC/memory/IO sections. Didn't "ser pim" give you LPMC and TOC sections too?
Secondly, since your j2240 is dual CPU, the PIM dump should contain the same info (HPMC, LPMC, TOC) for both CPUs.
Can you check if you firmware is anywhere near the current? (See http://www.parisc-linux.org/faq/index.html#PDCupdate)
And the following from your log worries me despite the "ignore" part:
| Information: Boot device can't seek past 2Gb (ignore next error). |byteio_read:seekread()returned -1 expected 2048But nothing else indicated a problem loading the vmlinux. I just don't see that when booting my a500.
It could be a difference in how palo interacts with IODC.If you don't get any other hot tips, start disabling things in the .config that you don't need: Parport, SBA/LBA/IOSAPIC, USB, LCD/LED support, wireless, extra lan/scsi drivers, etc.
grant
_______________________________________________
parisc-linux mailing list
[email protected]
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
Signature · 5 lines
Aaron St. Pierre tel: 978.828.6177 [email protected] Men say of women what pleases them; women do with men what pleases them. -- DeSegur
On Mon, Feb 03, 2003 at 01:43:28AM -0500, Aaron St. Pierre wrote:
[snip]
Quoted 3 lines
As far as the palo message, i only started noticing it when I went to v1.2 of palo. One thing I should note, when I set up / i made it ext3, boot is off of / and not its own fs so when i realized what i did I
[snip]
Your boot partition (/) is < 2GB, right?
Signature · 1 line
Michael Wood <[email protected]>
Yes, the boot partition is < 2GB. In fact here is the partion table as reported from fdisk.
Disk /dev/sda: 9100 MB, 9100044288 bytes
64 heads, 32 sectors/track, 8678 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Device Boot Start End Blocks Id System /dev/sda1 * 1 29 29680 f0 Linux/PA-RISC boot /dev/sda2 30 267 243712 83 Linux /dev/sda3 268 1221 976896 82 Linux swap /dev/sda4 1222 5989 4882432 5 Extended /dev/sda5 1222 3128 1952752 83 Linux /dev/sda6 3129 5989 2929648 83 Linux
I will also add this info to my parisc page. I am going to start ripping things out of the kernel a bit later today. One thing I will admit ignorance about is the F0 partition. The debian install got vmlinux32 to live in there but I haven't gotten any other kernels to live in there. Not that that really matters since once can boot off of a kernel that lives in an ext2 fs as long as it is within the first 2GB. Yawn, just waking up ...
Quoted 11 lines · In another life Michael Wood
On Mon, Feb 03, 2003 at 01:43:28AM -0500, Aaron St. Pierre wrote:
[snip]Quoted 3 lines
As far as the palo message, i only started noticing it when I went to v1.2 of palo. One thing I should note, when I set up / i made it ext3, boot is off of / and not its own fs so when i realized what i did I
[snip]
Your boot partition (/) is < 2GB, right?
Signature · 1 line
Michael Wood <[email protected]>
Signature · 4 lines
Aaron St. Pierre tel: 978.828.6177 [email protected] Have at you!
Quoted 10 lines · Aaron St. Pierre
Yes, the boot partition is < 2GB. In fact here is the partion table as reported from fdisk.
Disk
/dev/sda: 9100 MB, 9100044288 bytes
64 heads, 32 sectors/track, 8678 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytesDevice Boot Start End Blocks Id System /dev/sda1 * 1 29 29680 f0 Linux/PA-RISC boot /dev/sda2 30 267 243712 83 Linux
Your TOC dump indicated a likely death in firmware, which is consistent with trying to load a kernel from beyond the 2G mark. Indeed your /dev/sda2 ends past the 2G mark, so you can expect that sometimes it'll work and sometimes it won't.
-P
Quoted 8 lines · Paul Bame
Quoted 7 lines · Aaron St. Pierre
Yes, the boot partition is < 2GB. In fact here is the partion table as reported from fdisk.
Disk
/dev/sda: 9100 MB, 9100044288 bytes
64 heads, 32 sectors/track, 8678 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Quoted 8 lines
Quoted 3 lines
Device Boot Start End Blocks Id System /dev/sda1 * 1 29 29680 f0 Linux/PA-RISC boot /dev/sda2 30 267 243712 83 LinuxYour TOC dump indicated a likely death in firmware, which is consistent with trying to load a kernel from beyond the 2G mark. Indeed your
/dev/sda2ends past the 2G mark, so you can expect that sometimes it'll work and sometimes it won't.
Paul,
Are you sure?
267*1048576 == 279969792 == 279,969,792
That's 280MB if I've placed the comas right.
grant
Paul,
My root filesystem is 250MB.
parisc:~# df -kh
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 231M 52M 168M 24% /
/dev/sda5 1.9G 212M 1.6G 12% /var
/dev/sda6 2.8G 1009M 1.7G 38% /usr
Don't know if you saw the thread, but for some reason 2.5.58 boots, there are problems after, which is expected with a development kernel, but it boots nonetheless and that is hopeful :)
Is there perhaps some other way I should be organizing my swap and filesystems ? I followed the instructions from
http://www.parisc-linux.org/software/install.html.
Thanks
Quoted 22 lines · In another life Paul Bame
Quoted 10 lines · Aaron St. Pierre
Yes, the boot partition is < 2GB. In fact here is the partion table as reported from fdisk.
Disk
/dev/sda: 9100 MB, 9100044288 bytes
64 heads, 32 sectors/track, 8678 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytesDevice Boot Start End Blocks Id System /dev/sda1 * 1 29 29680 f0 Linux/PA-RISC boot /dev/sda2 30 267 243712 83 LinuxYour TOC dump indicated a likely death in firmware, which is consistent with trying to load a kernel from beyond the 2G mark. Indeed your
/dev/sda2ends past the 2G mark, so you can expect that sometimes it'll work and sometimes it won't.-P_______________________________________________
parisc-linux mailing list
[email protected]
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
Signature · 4 lines
Aaron St. Pierre tel: 978.828.6177 [email protected] <rcw> liiwi: printk("CPU0 on fire\n");
Quoted 3 lines · Aaron St. Pierre
Anyway I got the the TOC information for both processors after I tried to boot my kernel. It is
all on that page ( http://hadron.dyndns.org/parisc/ )
IIA Offset = 0x00000000f0080570
that's not a kernel address. Looks like a PDC call died. :^(
Quoted 6 lines
I also added a link to the firmware. I am running 2.0 of the firmware and according to hp the most recent is 2.1 or :
Patch Name: /firmware_patches/hp/cpu/PF_CJ224021
Description: HP 9000 Model J2240 firmware 2.1 patch
Date : 00/10/06
hmm...I'd stick with 2.0 for now.
Quoted 3 lines
I will start popping stuff out of the kernel, although I am sure I took out all of the stuff wrt graphics. Another try for persistance sake wont hurt :)
You still have STI drivers enabled and CONFIG_FB enabled. I'd start with those and then remove others one-by-one.
Quoted 5 lines
As far as the palo message, i only started noticing it when I went to v1.2 of palo. One thing I should note, when I set up / i made it ext3, boot is off of / and not its own fs so when i realized what i did I just changed fstab accordingly so it would mount as ext2, although that couldn't be the problem either since it is loading the debian kernels.
/ can be ext3. Palo doesn't care since ext2/ext3 are compatible. What's important is /boot/vmlinux is < 2GB on disk.
grant
Aaron,
Just A comment on your web page 'Comments':
warning concerning 'mathemu' code are well known annoying but armless.
I try to remove them but this broken to much original hp code :(
Now, the stupid question: do you try to boot from a serial console?
I also would like to know if you really have an ide cdrom on your J?
If yes, could you try to unplug it (pw supply and data flat cable) to reboot with your new kernel?
hth,
Joel
Quoted 39 lines
-- Original Message --
To: "Aaron St. Pierre" <[email protected]>
Cc: [email protected]
Subject: Re: [parisc-linux] kernel compile
From: [email protected] (Grant Grundler)
Date: Mon, 3 Feb 2003 09:53:21 -0700Quoted 3 lines · Aaron St. Pierre
Anyway I got the the TOC information for both processors after I tried to boot my kernel. It is
all on that page ( http://hadron.dyndns.org/parisc/ )IIA Offset =
0x00000000f0080570that's not a kernel address. Looks like a PDC call died. :^(
Quoted 6 lines
I also added a link to the firmware. I am running 2.0 of the firmware and according to hp the most recent is 2.1 or :
Patch Name: /firmware_patches/hp/cpu/PF_CJ224021
Description: HP 9000 Model J2240 firmware 2.1 patch
Date : 00/10/06hmm...I'd stick with 2.0 for now.
Quoted 3 lines
I will start popping stuff out of the kernel, although I am sure I took out all of the stuff wrt graphics. Another try for persistance sake wont hurt :)
You still have STI drivers enabled and
CONFIG_FBenabled. I'd start with those and then remove others one-by-one.Quoted 5 lines
As far as the palo message, i only started noticing it when I went to v1.2 of palo. One thing I should note, when I set up / i made it ext3, boot is off of / and not its own fs so when i realized what i did I just changed fstab accordingly so it would mount as ext2, although that couldn't be the problem either since it is loading the debian kernels.
Quoted 8 lines
/ can be ext3. Palo doesn't care since ext2/ext3 are compatible. What's important is
/boot/vmlinuxis < 2GB on disk.grant
_______________________________________________
parisc-linux mailing list
[email protected]
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
---------------------------------
Vous surfez avec une ligne classique ?
Faites des economies avec Tiscali Complete
... Plus d'info sur http://complete.tiscali.be
Joel,
I figured so, but thought I should note it since well I am running out of answers ;)
Here is the setup right now: I have a laptop running minicom connected to the J2240 through the serial port. I can see the init codes and tests happening through the serial console, so to answer your question :) yes I do boot from a serial console...
As far as the cdrom, it is not ide, it is scsi, and it seems to work fine /dev/cdrom --> sr0. I inserted a cdrom (just to test) and mounted iso9660 without problems.
I am going to remove ide stuff from the kernel after I test with what grant suggested.
Just for the sake of documentation I will add compile logs as script files for the next builds. They will be on that page as I complete them.
Fun day of pancake making ahead :)
Quoted 73 lines · In another life Joel Soete
Aaron,
Just A comment on your web page 'Comments':
warning concerning 'mathemu' code are well known annoying but armless.I try to remove them but this broken to much original hp code :(
Now, the stupid question: do you try to boot from a serial console?
I also would like to know if you really have an ide cdrom on your J?
If yes, could you try to unplug it (pw supply and data flat cable) to reboot with your new kernel?
hth,
JoelQuoted 39 lines
-- Original Message --
To: "Aaron St. Pierre" <[email protected]>
Cc: [email protected]
Subject: Re: [parisc-linux] kernel compile
From: [email protected] (Grant Grundler)
Date: Mon, 3 Feb 2003 09:53:21 -0700Quoted 3 lines · Aaron St. Pierre
Anyway I got the the TOC information for both processors after I tried to boot my kernel. It is
all on that page ( http://hadron.dyndns.org/parisc/ )IIA Offset =
0x00000000f0080570that's not a kernel address. Looks like a PDC call died. :^(
Quoted 6 lines
I also added a link to the firmware. I am running 2.0 of the firmware and according to hp the most recent is 2.1 or :
Patch Name: /firmware_patches/hp/cpu/PF_CJ224021
Description: HP 9000 Model J2240 firmware 2.1 patch
Date : 00/10/06hmm...I'd stick with 2.0 for now.
Quoted 3 lines
I will start popping stuff out of the kernel, although I am sure I took out all of the stuff wrt graphics. Another try for persistance sake wont hurt :)
You still have STI drivers enabled and
CONFIG_FBenabled. I'd start with those and then remove others one-by-one.Quoted 5 lines
As far as the palo message, i only started noticing it when I went to v1.2 of palo. One thing I should note, when I set up / i made it ext3, boot is off of / and not its own fs so when i realized what i did I just changed fstab accordingly so it would mount as ext2, although that couldn't be the problem either since it is loading the debian kernels.
Quoted 8 lines
/ can be ext3. Palo doesn't care since ext2/ext3 are compatible. What's important is
/boot/vmlinuxis < 2GB on disk.grant
_______________________________________________
parisc-linux mailing list
[email protected]
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux---------------------------------
Vous surfez avec une ligne classique ?
Faites des economies avec Tiscali Complete
... Plus d'info sur http://complete.tiscali.be
Signature · 5 lines
Aaron St. Pierre tel: 978.828.6177 [email protected] 667: The neighbor of the beast.
Okay....
I cannot explain this AT ALL, but look at this :
Linux parisc 2.5.58-pa2 #1 Mon Feb 3 19:05:50 EST 2003 parisc unknown unknown GNU/Linux
Yes 2.5 compiled and booted. It was a crap shoot. Now I have to figure out how to get modules to work. I had to take them out since I was getting a compile time error. This is just wierd.
Well I suppose I shouldn't complain, this was the FIRST kernel that I built that actually booted. After about thirty or fourty compiles I have to say my persistence has paid off ;)
I am gonna muck with the module stuff, If it is important to anyone I will maintain the page at http://hadron.dyndns.org/parisc/
Thanks again for all of your help !
Signature · 5 lines
Aaron St. Pierre tel: 978.828.6177 [email protected] "I'm in Pittsburgh. Why am I here?" -- Harold Urey, Nobel Laureate
Quoted 2 lines · Aaron St. Pierre
Yes 2.5 compiled and booted. It was a crap shoot. Now I have to figure out how to get modules to work.
Modules are broken in 2.5.x and still not fixed with 2.5.59. Someone volunteered already to fix it but it hasn't happened yet. Not sure if access to HW or lack of time is the problem.
Quoted 3 lines
Well I suppose I shouldn't complain, this was the FIRST kernel that I built that actually booted. After about thirty or fourty compiles I have to say my persistence has paid off ;)
wierd. I guess it has.
grant