Menu
▾
▴
linux-apus-devel
|
From: Reinhard N. <rn...@gm...> - 2000-10-18 20:50:51
|
Hi, I've successfully installed Debian Potato some days ago and was now going to compile a recent developer kernel. I've got the 2.3 module via cvs as mentioned on the web site and successfully compiled a kernel. I've started the kernel configuration from scratch, so it could be that I forgot some essential options. My first problem is, that when I enable PCI support for Permedia2, the kernel stops after the first heartbeat (bootmesg indicates, that the kernel was started), with no output on console. When I disable PCI support, I cannot use CVPPC and therefore open the console on my CV64/3D. There I get the following lines: Non-serviced A3000 SCSI-Interrupt? ISTR xxxx where xxxx changes from 64b1 to 44b1 then to 4b1 and finally to b1. Each value remains stable for about a second or two before the next value appears. The last value stays constant forever (<= 15 min). A note on the message frequency: my console is 1280x1024-8 and I can see max. two of the above mentioned values on the screen at the same time. Finally: has anyone such a system up and running with a recent cvs kernel (e. g. from today 20:00)? Can anyone send me a .config file for an A3000T with CVPPC? Is this a known problem and has anyone an idea what could be wrong? Thanks in advance. Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:rn...@gm... |
|
From: <gri...@ps...> - 2000-10-19 11:18:00
|
> When I disable PCI support, I cannot use CVPPC and therefore open the console
> on my CV64/3D. There I get the following lines:
>
> Non-serviced A3000 SCSI-Interrupt? ISTR xxxx
Whooo.. That's an *old* problem. Write-reordering to the WD33C93 chip.
Check out drivers/scsi/a3000.c. Are there any [rw]mb() calls in there?
If not then the original fix for APUS is missing..
Add these lines (sorry, no line numbers.. Just quick cut'n'paste):
/* start DMA */
+ mb(); /* make sure setup is completed */
DMA(a3000_host)->ST_DMA = 1;
+ mb(); /* make sure DMA has started before next IO */
And:
DMA(instance)->CNTR = cntr;
+ mb(); /* make sure CNTR is updated before next IO */
/* flush if we were reading */
if (HDATA(instance)->dma_dir) {
DMA(instance)->FLUSH = 1;
+ mb(); /* don't allow prefetch */
while (!(DMA(instance)->ISTR & ISTR_FE_FLG))
- ;
+ barrier();
+ mb(); /* no IO until FLUSH is done */
}
Also:
/* stop DMA */
DMA(instance)->SP_DMA = 1;
+ mb(); /* make sure DMA is stopped before next IO */
/* restore the CONTROL bits (minus the direction flag) */
DMA(instance)->CNTR = CNTR_PDMD | CNTR_INTEN;
+ mb(); /* make sure CNTR is updated before next IO */
/* copy from a bounce buffer, if necessary */
That should fix it..
Bye, Arno.
--
PSINetworks Europe Fax: +31-23-5699841 | One disk to rule them all,
Siriusdreef 34 Tel: +31-23-5699840 | One disk to bind them,
2132WT Hoofddorp+--------------------------------+ One disk to hold the files
The Netherlands | * Musical Interlude * | And in the darkness grind 'em
----------------+--------------------------------+------------------------------
We say Retribution, We say Vengeance is bliss, We say Revolution,
With a Cast-Iron fist! (Megadeth, 'The Disintegrators')
--------------------------------------------------------------------------------
|
|
From: Reinhard N. <rn...@gm...> - 2000-10-19 18:54:30
Attachments:
a3000.c.diff.gz
|
Hi, Arno Griffioen wrote: > > > When I disable PCI support, I cannot use CVPPC and therefore open the console > > on my CV64/3D. There I get the following lines: > > > > Non-serviced A3000 SCSI-Interrupt? ISTR xxxx > > Whooo.. That's an *old* problem. Write-reordering to the WD33C93 chip. > > Check out drivers/scsi/a3000.c. Are there any [rw]mb() calls in there? You are right, they were missing. The changes you've mentioned got it going :-) I've attached a diff file that makes the required changes in 2.3, so that the file is similar to 2.2 in this concern. Could any of the registerd developers apply this patch to the cvs sources? Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:rn...@gm... |
|
From: <fp...@zu...> - 2000-10-19 19:06:14
|
On Thu, Oct 19, 2000 at 08:53:49PM +0200, Reinhard Nissl wrote: > Could any of the registerd developers apply this patch to the cvs sources? Why don't you put it into the patch manager? -- Frank Petzold, IBM Zurich Research Laboratory, Säumerstrasse 4, CH-8803 Rüschlikon/Switzerland, Tel. +41-1-724-84-42 Fax. +41-1-724-89-56 Business email: fp...@zu... Private email: pe...@he... The opinions expressed here are mine and not necessarily those of IBM. |
|
From: Michel <dae...@st...> - 2000-10-29 01:19:08
|
Reinhard Nissl wrote: > My first problem is, that when I enable PCI support for Permedia2, the > kernel stops after the first heartbeat (bootmesg indicates, that the kernel > was started), with no output on console. No output at all? What about dmesg? > When I disable PCI support, I cannot use CVPPC You should be able to (unlike in 2.2), doesn't it work? Michel -- Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and The DRI Project |
|
From: Reinhard N. <rn...@gm...> - 2000-10-29 19:11:36
|
Hi, Michel Dänzer wrote: > > Reinhard Nissl wrote: > > > My first problem is, that when I enable PCI support for Permedia2, the > > kernel stops after the first heartbeat (bootmesg indicates, that the kernel > > was started), with no output on console. > > No output at all? What about dmesg? Nothing. See attached files. > > When I disable PCI support, I cannot use CVPPC > > You should be able to (unlike in 2.2), doesn't it work? No. I don't get a console on CVPPC. I've attached a couple of files, maybe somethings is wrong with them. What is a minimalistic AmigaOS configuration to boot linux? As far as I have tried yet, I get an 0x80000004, when ppcboot_pup is starting. Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:rn...@gm... |
|
From: Michel <da...@re...> - 2000-10-30 13:43:53
|
Reinhard Nissl wrote: > > > My first problem is, that when I enable PCI support for Permedia2, the > > > kernel stops after the first heartbeat (bootmesg indicates, that the > > > kernel was started), with no output on console. > > > > No output at all? What about dmesg? > > Nothing. See attached files. The boothack line you attached lacks the debug=mem, I suppose you had that when you tried dmesg? > > > When I disable PCI support, I cannot use CVPPC > > > > You should be able to (unlike in 2.2), doesn't it work? > > No. I don't get a console on CVPPC. > > I've attached a couple of files, maybe somethings is wrong with them. I've got some remarks, see below. > What is a minimalistic AmigaOS configuration to boot linux? > > As far as I have tried yet, I get an 0x80000004, when ppcboot_pup is > starting. So how do you boot? :) Nothing about that in this or the user list's archive? > CONFIG_PCI=y This config is with PCI enabled, so I can't check if pm2fb is enabled. > CONFIG_FB_PM2=y > CONFIG_FB_PM2_FIFO_DISCONNECT=y > CONFIG_FB_PM2_PCI=y > CONFIG_FB_PM2_CVPPC=y FIFO disconnect doesn't work with our cards. It used to only produce wrong colors for me, but one never knows. Michel -- Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and the DRI project |
|
From: Reinhard N. <rn...@gm...> - 2000-10-30 17:22:33
|
Hi, Michel Dänzer wrote: > > Reinhard Nissl wrote: > > > > > My first problem is, that when I enable PCI support for Permedia2, the > > > > kernel stops after the first heartbeat (bootmesg indicates, that the > > > > kernel was started), with no output on console. > > > > > > No output at all? What about dmesg? > > > > Nothing. See attached files. > > The boothack line you attached lacks the debug=mem, I suppose you had that > when you tried dmesg? Oops. Will try it again this evening. > > > > When I disable PCI support, I cannot use CVPPC > > > > > > You should be able to (unlike in 2.2), doesn't it work? > > > > No. I don't get a console on CVPPC. > > > > I've attached a couple of files, maybe somethings is wrong with them. > > I've got some remarks, see below. > > > What is a minimalistic AmigaOS configuration to boot linux? > > > > As far as I have tried yet, I get an 0x80000004, when ppcboot_pup is > > starting. > > So how do you boot? :) Nothing about that in this or the user list's archive? Well, I can boot, but some problems could be triggered by running software, that is actually not necessary for booting Linux. Haven't checked the archive yet. > > CONFIG_PCI=y > > This config is with PCI enabled, so I can't check if pm2fb is enabled. I don't get your answer. Is it ok or is it wrong? > > CONFIG_FB_PM2=y > > CONFIG_FB_PM2_FIFO_DISCONNECT=y > > CONFIG_FB_PM2_PCI=y > > CONFIG_FB_PM2_CVPPC=y > > FIFO disconnect doesn't work with our cards. It used to only produce wrong > colors for me, but one never knows. So I'd better start with FIFO disabled? Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:rn...@gm... |
|
From: Michel <da...@re...> - 2000-10-30 17:47:00
|
Reinhard Nissl wrote: > > > CONFIG_PCI=y > > > > This config is with PCI enabled, so I can't check if pm2fb is enabled. > > I don't get your answer. Is it ok or is it wrong? I can't tell because PCI is enabled in your config. I would have liked to check if pm2fb is enabled if PCI is disabled. > > > CONFIG_FB_PM2=y > > > CONFIG_FB_PM2_FIFO_DISCONNECT=y > > > CONFIG_FB_PM2_PCI=y > > > CONFIG_FB_PM2_CVPPC=y > > > > FIFO disconnect doesn't work with our cards. It used to only produce wrong > > colors for me, but one never knows. > > So I'd better start with FIFO disabled? Yes, please try that. Seems I tend to be too little explicit? Michel -- Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and the DRI project |
|
From: Reinhard N. <rn...@gm...> - 2000-10-30 19:38:54
Attachments:
dmesg.txt
|
Michel Dänzer wrote: > > Reinhard Nissl wrote: > > > > > CONFIG_PCI=y > > > > > > This config is with PCI enabled, so I can't check if pm2fb is enabled. > > > > I don't get your answer. Is it ok or is it wrong? > > I can't tell because PCI is enabled in your config. I would have liked to > check if pm2fb is enabled if PCI is disabled. Now, I see. I didn't get you, because I wanted to use PCI, while you wanted to get CVPPC to work without PCI. Fine. I'll modify my .config and compile a new kernel. Would you like dmesg output then? > > > > CONFIG_FB_PM2=y > > > > CONFIG_FB_PM2_FIFO_DISCONNECT=y > > > > CONFIG_FB_PM2_PCI=y > > > > CONFIG_FB_PM2_CVPPC=y > > > > > > FIFO disconnect doesn't work with our cards. It used to only produce wrong > > > colors for me, but one never knows. > > > > So I'd better start with FIFO disabled? > > Yes, please try that. I'll right now. BTW: attached you'll find the dmesg output after adding kernel option debug=mem. Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:rn...@gm... |
|
From: Michel <dae...@st...> - 2000-10-30 20:11:47
|
Reinhard Nissl wrote: > parse_bootinfo: unknown tag 0x8008 ignored > parse_bootinfo: unknown tag 0x8009 ignored Ah! You're using the latest boothack, right? The 2.4 tree _still_ hasn't got the necessary changes, so you need an old boothack, 990106 worked for me so I included it with the test kernel tarball. This is probably the cause for your problems with or without PCI, because the kernel doesn't know there is a CVisionPPC. > PCI: Probing PCI hardware > NIP: 00000000 XER: 00000000 LR: C000B76C REGS: c032fad0 TRAP: 0400 Granted, it shouldn't panic even in this case :) I'll look into it when I get time, not before next weekend. Michel -- Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and The DRI Project |
|
From: Reinhard N. <rn...@gm...> - 2000-10-30 20:21:59
Attachments:
dmesg.txt
|
Hi, Reinhard Nissl wrote: > > Michel Dänzer wrote: > > > > Reinhard Nissl wrote: > > > > > > > CONFIG_PCI=y > > > > > > > > This config is with PCI enabled, so I can't check if pm2fb is enabled. > > > > > > I don't get your answer. Is it ok or is it wrong? > > > > I can't tell because PCI is enabled in your config. I would have liked to > > check if pm2fb is enabled if PCI is disabled. > > Now, I see. I didn't get you, because I wanted to use PCI, while you wanted to > get CVPPC to work without PCI. > > Fine. I'll modify my .config and compile a new kernel. Would you like dmesg > output then? Well, I assume, you would like :-) Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:rn...@gm... |
|
From: Roman Z. <zi...@fh...> - 2000-10-30 22:33:12
|
Hi, On Mon, 30 Oct 2000, Reinhard Nissl wrote: > Warning: unable to open an initial console. Hmm, I don't see a "fb0: ..." line in your output so your card is not detected at all. I just commited a small change, that should get you further. > request_module[net-pf-1]: waitpid(5814,...) failed, errno 1 That's unix domain sockets (CONFIG_UNIX), it's always a good idea to keep it compiled in. :) bye, Roman |
|
From: Michel <dae...@st...> - 2000-10-30 22:45:12
|
Roman Zippel wrote: > > Warning: unable to open an initial console. > > Hmm, I don't see a "fb0: ..." line in your output so your card is not > detected at all. I just commited a small change, that should get you > further. What did you change? I think the problem is that he's using too new a boothack. Michel -- Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and The DRI Project |
|
From: Roman Z. <zi...@fh...> - 2000-10-30 23:03:18
|
Hi, On Mon, 30 Oct 2000, Michel Dänzer wrote: > What did you change? I think the problem is that he's using too new a > boothack. pm2fb.c tests for powerup_PCI_present and I took the changes from 2.2, so it might be set now. :) bye, Roman |
|
From: Michel <dae...@st...> - 2000-10-30 23:08:09
|
Roman Zippel wrote: > > What did you change? I think the problem is that he's using too new a > > boothack. > > pm2fb.c tests for powerup_PCI_present Like apus_pci.c ... > and I took the changes from 2.2, so it might be set now. :) Finally, thanks! Michel -- Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and The DRI Project |
|
From: Reinhard N. <rn...@gm...> - 2000-11-01 17:59:32
Attachments:
dmesg.txt
|
Hi, let's start with the good news: CVPPC console works after the recent changes from cvs if you use the new (current) bootstrap programme. But for any reason, the console isn't cleared properly or not at all (e. g. when in vi and pressing Ctrl+L). Has anyone experienced such problems like overtyping characters on console when you edit a commandline? Internally, the typed characters were properly inserted. A Ctrl+L shows them on screen then. If I delete characters from the line, I don't see any change on screen. A Ctrl+L updates the screen, but 'old' characters remain on screen. To make it clear, see the following example: The line consists of abcdefghijk Then you delete 'def' and you see on screen abcdefghijk After pressing Ctrl+L you see abcghijkijk While compiling the kernel, I've seen, that usually empty areas on console show word fragments, that were output some time ago, e. g. at boot time. After that, I've tried PCI support again. But the kernel fails booting. See attached dmesg.txt. Am I right, that a recent X server needs PCI support? Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:rn...@gm... |
|
From: Michel <dae...@st...> - 2000-11-01 18:41:57
|
Reinhard Nissl wrote: > While compiling the kernel, I've seen, that usually empty areas on console > show word fragments, that were output some time ago, e. g. at boot time. Sounds like the old 'Permedia2 isn't initialized correctly' bug which can be worked around by booting AmigaOS or a working kernel before. I thought I had (at least tried to) fix(ed) it in 2.4 as well... > After that, I've tried PCI support again. But the kernel fails booting. See > attached dmesg.txt. Am I right, that a recent X server needs PCI support? Yes, but only due to a bug which prevents it from working without. > PCI: Probing PCI hardware > PCI: Cannot allocate resource region 1 of device 00:01.0 > PCI: Failed to allocate resource 3 for Texas Instruments TVP4020 [Permedia > 2] Interesting. Geert, I suppose this is your new resource code? Any idea what's going on? > Starting kswapd v1.8 > Machine check in kernel mode. > Caused by (from SRR1=49070): Transfer error ack signal This is probably when pm2fb tries to probe the PCI device(s), could it be due to the resource code's failure? Michel -- Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and The DRI Project |
|
From: Geert U. <ge...@li...> - 2000-11-03 11:45:00
|
On Wed, 1 Nov 2000, Michel [iso-8859-1] Dänzer wrote:
> Reinhard Nissl wrote:
> > PCI: Probing PCI hardware
> > PCI: Cannot allocate resource region 1 of device 00:01.0
> > PCI: Failed to allocate resource 3 for Texas Instruments TVP4020 [Permedia
> > 2]
>
> Interesting. Geert, I suppose this is your new resource code? Any idea what's
> going on?
Probably there's no parent resource for that device. Do you fill in the bus
resources for the PCI bus on the CSPPC? Please enable #define DEBUG everywhere
in drivers/pci/ and in arch/ppc/kernel/ for more info.
The output of /proc/iomem and `lspci -vv' also helps. But you do need to be
able to boot into userspace for that :-)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li...
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
|
|
From: Michel <dae...@st...> - 2000-11-03 11:56:43
|
Geert Uytterhoeven wrote: > > On Wed, 1 Nov 2000, Michel [iso-8859-1] Dänzer wrote: > > Reinhard Nissl wrote: > > > PCI: Probing PCI hardware > > > PCI: Cannot allocate resource region 1 of device 00:01.0 > > > PCI: Failed to allocate resource 3 for Texas Instruments TVP4020 > > > [Permedia 2] > > > > Interesting. Geert, I suppose this is your new resource code? Any idea > > what's going on? > > Probably there's no parent resource for that device. Do you fill in the bus > resources for the PCI bus on the CSPPC? No, how can I do that? > Please enable #define DEBUG everywhere in drivers/pci/ and in > arch/ppc/kernel/ for more info. Okay, thanks. > The output of /proc/iomem and `lspci -vv' also helps. But you do need to be > able to boot into userspace for that :-) Interestingly, that problem didn't occur with my BVision, it only failed later due to the SCSI driver. I thought the two kinds of cards were identical... Michel -- Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and The DRI Project |
|
From: Geert U. <ge...@li...> - 2000-11-03 18:42:51
|
On Fri, 3 Nov 2000, Michel [iso-8859-1] Dänzer wrote:
> Geert Uytterhoeven wrote:
> > On Wed, 1 Nov 2000, Michel [iso-8859-1] Dänzer wrote:
> > > Reinhard Nissl wrote:
> > > > PCI: Probing PCI hardware
> > > > PCI: Cannot allocate resource region 1 of device 00:01.0
> > > > PCI: Failed to allocate resource 3 for Texas Instruments TVP4020
> > > > [Permedia 2]
> > >
> > > Interesting. Geert, I suppose this is your new resource code? Any idea
> > > what's going on?
> >
> > Probably there's no parent resource for that device. Do you fill in the bus
> > resources for the PCI bus on the CSPPC?
>
> No, how can I do that?
>
> > Please enable #define DEBUG everywhere in drivers/pci/ and in
> > arch/ppc/kernel/ for more info.
>
> Okay, thanks.
Look at the other PPC platforms.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li...
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
|
|
From: Reinhard N. <rn...@gm...> - 2000-11-02 08:17:49
|
Hi, Michel Dänzer wrote: > > Reinhard Nissl wrote: > > > While compiling the kernel, I've seen, that usually empty areas on console > > show word fragments, that were output some time ago, e. g. at boot time. > > Sounds like the old 'Permedia2 isn't initialized correctly' bug which can be > worked around by booting AmigaOS or a working kernel before. I thought I had > (at least tried to) fix(ed) it in 2.4 as well... Well, none of the two suggestions makes it work. Is it a problem, if Workbench runs at 1280x1024x16@85 and console at 1280x1024x8@75? > > After that, I've tried PCI support again. But the kernel fails booting. See > > attached dmesg.txt. Am I right, that a recent X server needs PCI support? > > Yes, but only due to a bug which prevents it from working without. :-) BTW: I've some problems in using modules with Debian. What is /etc/modules good for? Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:rn...@gm... |
|
From: Michel <da...@re...> - 2000-11-02 08:44:15
|
Reinhard Nissl wrote: > > > While compiling the kernel, I've seen, that usually empty areas on > > > console show word fragments, that were output some time ago, e. g. at > > > boot time. > > > > Sounds like the old 'Permedia2 isn't initialized correctly' bug which can > > be worked around by booting AmigaOS or a working kernel before. I thought > > I had (at least tried to) fix(ed) it in 2.4 as well... > > Well, none of the two suggestions makes it work. Is it a problem, if > Workbench runs at 1280x1024x16@85 and console at 1280x1024x8@75? No, shouldn't matter. Looks like a new bug :-/ Michel -- Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and the DRI project |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X