Menu
▾
▴
linux-apus-user
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(177) |
Jun
(100) |
Jul
(56) |
Aug
(143) |
Sep
(366) |
Oct
(142) |
Nov
(221) |
Dec
(56) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(364) |
Feb
(705) |
Mar
(185) |
Apr
(267) |
May
(238) |
Jun
(59) |
Jul
(22) |
Aug
(47) |
Sep
(42) |
Oct
(54) |
Nov
(72) |
Dec
(42) |
| 2002 |
Jan
(32) |
Feb
(130) |
Mar
(77) |
Apr
(23) |
May
(15) |
Jun
(17) |
Jul
(31) |
Aug
(38) |
Sep
(61) |
Oct
(35) |
Nov
(36) |
Dec
(42) |
| 2003 |
Jan
(57) |
Feb
(13) |
Mar
(31) |
Apr
(28) |
May
(4) |
Jun
(22) |
Jul
(22) |
Aug
(5) |
Sep
|
Oct
(5) |
Nov
(9) |
Dec
(37) |
| 2004 |
Jan
(7) |
Feb
(11) |
Mar
(6) |
Apr
(1) |
May
(1) |
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
|
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(5) |
Aug
|
Sep
(3) |
Oct
(3) |
Nov
(1) |
Dec
(6) |
| 2006 |
Jan
(18) |
Feb
(8) |
Mar
|
Apr
|
May
(14) |
Jun
(1) |
Jul
|
Aug
(6) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Alan B. <al...@ms...> - 2002-10-15 18:23:12
|
hi, > woody). I get an error message that linux.bin is too big to uncompress, > but I haven't had any time to test things out further. I know though that > linux.bin is compressed with gzip. Maybe you can test uncompressing it and > report if it works better :) linux.bin is the root-disk, not the kernel....so you need to make sure you have 1) latest bootstrap from APUS site 2) latest kernel from APUS site then bootstrap --apus -k latestkernel -r linux.bin root=/dev/ram other_options_here alan |
|
From: David J. <jo...@co...> - 2002-10-15 17:40:28
|
Hi, I have problems booting the 2.4.18-2 kernal. It fails at a point when it probes for ide stuff. Is there a solution to this problem being worked on for us A1200 users? Does this problem occur with different ide doublers. I use one from powercomputing. Regards, Dave ( jo...@co... ) A man sits with a pretty girl for an hour, it seems like a minute. He sits on a hot stove for a minute, it's longer than any hour. That is relativity. -- Albert Einstein |
|
From: Björn J. <kh...@te...> - 2002-10-15 13:30:38
|
Paul W. Martin wrote about Linux-APUS-user digest, Vol 1 #652 - 2 msgs: > Hello Bj=F6rn > > On 14-Oct-02, you wrote: > . > > > > Why not try the kernel(2.4.18-2) from: > > http://linux-apus.sourceforge.net/ > > > > It works perfectly on my Amiga4000. > > My Amiga config: > > > > Amiga4000, CyberstormPPC @ 233Mhz, 040 @ 25Mhz > > 64MB FAST and 2MB CHIP(AGA) > > X-Surf 10 Mbit Ethernet > > AmigaOS3.5 and Debian3.0(woody). > > > > My only problem right now is that PPP don't > > work. > > > > That is the kernel I'm using and the latest bootstrap > > I have also tried AGA and VGA using a monitor on the internal connector, > still no joy :( > > Debian 3.0 works fine for 68k it just doesn't seem to work on ppc :( > > Regards > > Paul > -- > Evaluating system... > Central Processing Unit: MC68060 49.9 MHz (rev 1) > 1 WarpUP Processor(s): PPC 604e 200 MHz (rev 2.4), 66 MHz busclock > Floating Point Unit: 68060fpu 49.9 MHz > Memory Management Unit: 68060mmu running > Custom graphics chip: AGA Lisa 4203 (rev 0) > Custom animation chip: AGA PAL Alice 8374 2M (rev 3-4) > Other custom chip(s): Paula 8364 (rev 0), Ramsey (rev 15), Gary (rev 0= ) > Graphics system: Picasso96 > Graphics board(s): Picasso IV [Paloma Concierto] > Soundcard(s): Concierto > Hardware Clock: clock + battmem found, sunday 21-apr-2002 18:38:= 28 > Max. Chipmem available: 2048 K > Max. Fastmem available: 130048 K > ROM chip version: 45.20 (Kickstart 3.9) > Workbench version: 45.3 (Workbench 3.9) > SetPatch version: 44.38 > Expansion board(s): > 5001/6: individual Computers/VMC HyperCOM Z4 (@$00E90000 64k) > 4626/23: individual Computers X-Surf (@$00EA0000 64k) > 2167/24: Village Tronic Picasso IV (@$40000000 32M) > 8512/100: Phase 5 Digital Products CyberStorm PPC/MK III SCSI (@$00F01060= > 128k) > Cyberstorm PPC serial #: DCC0270 > > Your computer is an Amiga 4000 Tower. Have you updated your flash rom? If so, do you have the latest version installed? Your config says you're using kickstart3.9, hmm. I was only aware of 3.1 kickroms, is it a soft kick or is it really new hardware? -- Bj=F6rn Johansson "Debian rocks!!" |
|
From: Paul W. M. <pau...@nt...> - 2002-10-15 09:03:00
|
Hello Bj=F6rn On 14-Oct-02, you wrote: =2E > = > Why not try the kernel(2.4.18-2) from: > http://linux-apus.sourceforge.net/ > = > It works perfectly on my Amiga4000. > My Amiga config: > = > Amiga4000, CyberstormPPC @ 233Mhz, 040 @ 25Mhz > 64MB FAST and 2MB CHIP(AGA) > X-Surf 10 Mbit Ethernet > AmigaOS3.5 and Debian3.0(woody). > = > My only problem right now is that PPP don't > work. > = That is the kernel I'm using and the latest bootstrap I have also tried AGA and VGA using a monitor on the internal connector, still no joy :( Debian 3.0 works fine for 68k it just doesn't seem to work on ppc :( Regards Paul -- = Evaluating system... Central Processing Unit: MC68060 49.9 MHz (rev 1) 1 WarpUP Processor(s): PPC 604e 200 MHz (rev 2.4), 66 MHz busclock Floating Point Unit: 68060fpu 49.9 MHz Memory Management Unit: 68060mmu running Custom graphics chip: AGA Lisa 4203 (rev 0) Custom animation chip: AGA PAL Alice 8374 2M (rev 3-4) Other custom chip(s): Paula 8364 (rev 0), Ramsey (rev 15), Gary (rev 0= ) Graphics system: Picasso96 Graphics board(s): Picasso IV [Paloma Concierto] Soundcard(s): Concierto Hardware Clock: clock + battmem found, sunday 21-apr-2002 18:38:= 28 Max. Chipmem available: 2048 K Max. Fastmem available: 130048 K ROM chip version: 45.20 (Kickstart 3.9) Workbench version: 45.3 (Workbench 3.9) SetPatch version: 44.38 Expansion board(s): 5001/6: individual Computers/VMC HyperCOM Z4 (@$00E90000 64k) 4626/23: individual Computers X-Surf (@$00EA0000 64k) 2167/24: Village Tronic Picasso IV (@$40000000 32M) 8512/100: Phase 5 Digital Products CyberStorm PPC/MK III SCSI (@$00F01060= 128k) Cyberstorm PPC serial #: DCC0270 Your computer is an Amiga 4000 Tower.= |
|
From: Michel <mi...@da...> - 2002-10-14 20:38:05
|
On Mon, 2002-10-14 at 19:37, Giorgio Terzi wrote:=20 > Alle 18:03, domenica 13 ottobre 2002, Robert Johansson ha scritto: >=20 > > I have the same problem as you, and I'm using the same files (Debian > > woody). I get an error message that linux.bin is too big to uncompress, > > but I haven't had any time to test things out further. I know though th= at > > linux.bin is compressed with gzip. Maybe you can test uncompressing it = and > > report if it works better :) >=20 > Yes you're true, there is a simple patch to bootstrap that i have done bu= t =20 > not still submitted. This because bootstrap can only handle compressed=20 > kernels with no more than 2 Megs of dimension.=20 > I will submit this patch to CVS during this week! Yes, you committed it on May 21st 2001, and the 010623 boothack release has the fix. It's just that the boothack that comes with the boot-floppies is outdated. --=20 Earthling Michel D=E4nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast |
|
From: Giorgio T. <de...@ip...> - 2002-10-14 17:39:49
|
Alle 18:03, domenica 13 ottobre 2002, Robert Johansson ha scritto: > I have the same problem as you, and I'm using the same files (Debian > woody). I get an error message that linux.bin is too big to uncompress, > but I haven't had any time to test things out further. I know though that > linux.bin is compressed with gzip. Maybe you can test uncompressing it and > report if it works better :) Yes you're true, there is a simple patch to bootstrap that i have done but not still submitted. This because bootstrap can only handle compressed kernels with no more than 2 Megs of dimension. I will submit this patch to CVS during this week! I think that for Paul there is also another thing to try: the idea is this: you may try is to substitute video=clgen:low with video=amifb:vga This because clgen driver has some programming problems and if the kernel is compiled with also the PCI option (i think it is so because PCI is used for CVisionPPC) a preprocessor #if cuts out all the Zorro driver's part. Time ago i promised to correct it. Because i have a Picasso 4 too. And i will, if i shall find the time... Regards, Giorgio Terzi |
|
From: Giorgio T. <de...@ip...> - 2002-10-14 17:39:46
|
Alle 16:56, domenica 13 ottobre 2002, Paul W. Martin ha scritto: > Hello, > > I can't seem to get my System to boot into Apus, I run the command line the > screen goes black and then just sits there doing nothing, I have waited > upto 10mins to see if there was a delay before booting but still nothing, > anyideas? > My bootstrap line is:- > > BootStrap --apus -d -k "APUS Boot:apus/vmlinux" -r "APUS > Boot:Apus/images-1.44/root.bin" nobats root=/dev/ram video=clgen:low -d > debug=mem One idea is this: you may try is to substitute video=clgen:low with video=amifb:vga This because clgen driver has some programming problems and if the kernel is compiled with also the PCI option (i think it is so because PCI is used for CVisionPPC) a preprocessor #if cuts out all the Zorro driver's part. Time ago i promised to correct it. Because i have a Picasso 4 too. And i will, if i shall find the time... Regards, Giorgio Terzi |
|
From: Giorgio T. <de...@ip...> - 2002-10-14 17:39:45
|
Alle 16:56, domenica 13 ottobre 2002, Paul W. Martin ha scritto: > Hello, > > I can't seem to get my System to boot into Apus, I run the command line the > screen goes black and then just sits there doing nothing, I have waited > upto 10mins to see if there was a delay before booting but still nothing, > anyideas? > My bootstrap line is:- > > BootStrap --apus -d -k "APUS Boot:apus/vmlinux" -r "APUS > Boot:Apus/images-1.44/root.bin" nobats root=/dev/ram video=clgen:low -d > debug=mem One idea is this: you may try is to substitute video=clgen:low with video=amifb:vga This because clgen driver has some programming problems and if the kernel is compiled with also the PCI option (i think it is so because PCI is used for CVisionPPC) a preprocessor #if cuts out all the Zorro driver's part. Time ago i promised to correct it. Because i have a Picasso 4 too. And i will, if i shall find the time... Regards, Giorgio Terzi |
|
From: Björn J. <kh...@te...> - 2002-10-14 11:38:25
|
Paul W. Martin wrote about Linux-APUS-user digest, Vol 1 #652 - 2 msgs: > Hello Robert > > On 13-Oct-02, you wrote: > > > I have the same problem as you, and I'm using the same files (Debian > > woody). I get an error message that linux.bin is too big to uncompress,= > > but I haven't had any time to test things out further. I know though th= at > > linux.bin is compressed with gzip. Maybe you can test uncompressing it = and > > report if it works better :) > > > /Robert > > vmlinux is the ungziped linux.bin, originally it did complain about the > compressed size so I ungziped it. > > Regards > > Paul > -- > Evaluating system... > Central Processing Unit: MC68060 49.9 MHz (rev 1) > 1 WarpUP Processor(s): PPC 604e 200 MHz (rev 2.4), 66 MHz busclock > Floating Point Unit: 68060fpu 49.9 MHz > Memory Management Unit: 68060mmu running > Custom graphics chip: AGA Lisa 4203 (rev 0) > Custom animation chip: AGA PAL Alice 8374 2M (rev 3-4) > Other custom chip(s): Paula 8364 (rev 0), Ramsey (rev 15), Gary (rev 0= ) > Graphics system: Picasso96 > Graphics board(s): Picasso IV [Paloma Concierto] > Soundcard(s): Concierto > Hardware Clock: clock + battmem found, sunday 21-apr-2002 18:38:= 28 > Max. Chipmem available: 2048 K > Max. Fastmem available: 130048 K > ROM chip version: 45.20 (Kickstart 3.9) > Workbench version: 45.3 (Workbench 3.9) > SetPatch version: 44.38 > Expansion board(s): > 5001/6: individual Computers/VMC HyperCOM Z4 (@$00E90000 64k) > 4626/23: individual Computers X-Surf (@$00EA0000 64k) > 2167/24: Village Tronic Picasso IV (@$40000000 32M) > 8512/100: Phase 5 Digital Products CyberStorm PPC/MK III SCSI (@$00F01060= > 128k) > Cyberstorm PPC serial #: DCC0270 > > Your computer is an Amiga 4000 Tower. Why not try the kernel(2.4.18-2) from: http://linux-apus.sourceforge.net/ It works perfectly on my Amiga4000. My Amiga config: Amiga4000, CyberstormPPC @ 233Mhz, 040 @ 25Mhz 64MB FAST and 2MB CHIP(AGA) X-Surf 10 Mbit Ethernet AmigaOS3.5 and Debian3.0(woody). My only problem right now is that PPP don't work. -- Bj=F6rn Johansson "Debian rocks!!" |
|
From: Paul W. M. <pau...@nt...> - 2002-10-14 08:00:30
|
Hello Robert
On 13-Oct-02, you wrote:
> I have the same problem as you, and I'm using the same files (Debian
> woody). I get an error message that linux.bin is too big to uncompress,
> but I haven't had any time to test things out further. I know though that
> linux.bin is compressed with gzip. Maybe you can test uncompressing it and
> report if it works better :)
> /Robert
vmlinux is the ungziped linux.bin, originally it did complain about the
compressed size so I ungziped it.
Regards
Paul
--
Evaluating system...
Central Processing Unit: MC68060 49.9 MHz (rev 1)
1 WarpUP Processor(s): PPC 604e 200 MHz (rev 2.4), 66 MHz busclock
Floating Point Unit: 68060fpu 49.9 MHz
Memory Management Unit: 68060mmu running
Custom graphics chip: AGA Lisa 4203 (rev 0)
Custom animation chip: AGA PAL Alice 8374 2M (rev 3-4)
Other custom chip(s): Paula 8364 (rev 0), Ramsey (rev 15), Gary (rev 0)
Graphics system: Picasso96
Graphics board(s): Picasso IV [Paloma Concierto]
Soundcard(s): Concierto
Hardware Clock: clock + battmem found, sunday 21-apr-2002 18:38:28
Max. Chipmem available: 2048 K
Max. Fastmem available: 130048 K
ROM chip version: 45.20 (Kickstart 3.9)
Workbench version: 45.3 (Workbench 3.9)
SetPatch version: 44.38
Expansion board(s):
5001/6: individual Computers/VMC HyperCOM Z4 (@$00E90000 64k)
4626/23: individual Computers X-Surf (@$00EA0000 64k)
2167/24: Village Tronic Picasso IV (@$40000000 32M)
8512/100: Phase 5 Digital Products CyberStorm PPC/MK III SCSI (@$00F01060
128k)
Cyberstorm PPC serial #: DCC0270
Your computer is an Amiga 4000 Tower.
|
|
From: Robert J. <rob...@st...> - 2002-10-13 16:03:52
|
On Sun, 13 Oct 2002, Paul W. Martin wrote:
> My bootstrap line is:-
>
> BootStrap --apus -d -k "APUS Boot:apus/vmlinux" -r "APUS
> Boot:Apus/images-1.44/root.bin" nobats root=/dev/ram video=clgen:low -d
> debug=mem
>
> vmlinux is the latest linux.bin file from debian 3.0r0 the same for root.bin
I have the same problem as you, and I'm using the same files (Debian
woody). I get an error message that linux.bin is too big to uncompress,
but I haven't had any time to test things out further. I know though that
linux.bin is compressed with gzip. Maybe you can test uncompressing it and
report if it works better :)
/Robert
Robert Johansson * gu...@ha... * +46 (0)7 39 8000 39
In pursuit of a M.Sc. in Computer Science
|
|
From: Paul W. M. <pau...@nt...> - 2002-10-13 15:56:40
|
Hello,
I can't seem to get my System to boot into Apus, I run the command line the
screen goes black and then just sits there doing nothing, I have waited
upto 10mins to see if there was a delay before booting but still nothing,
anyideas?
My bootstrap line is:-
BootStrap --apus -d -k "APUS Boot:apus/vmlinux" -r "APUS
Boot:Apus/images-1.44/root.bin" nobats root=/dev/ram video=clgen:low -d
debug=mem
vmlinux is the latest linux.bin file from debian 3.0r0 the same for root.bin
when I run dmesg afterwards the reply is
Searching for SAVEKMSG magic...
Not found
I'm using the internal scsi on the A4000T.
Regards,
Paul
--
Evaluating system...
Central Processing Unit: MC68060 49.9 MHz (rev 1)
1 WarpUP Processor(s): PPC 604e 200 MHz (rev 2.4), 66 MHz busclock
Floating Point Unit: 68060fpu 49.9 MHz
Memory Management Unit: 68060mmu running
Custom graphics chip: AGA Lisa 4203 (rev 0)
Custom animation chip: AGA PAL Alice 8374 2M (rev 3-4)
Other custom chip(s): Paula 8364 (rev 0), Ramsey (rev 15), Gary (rev 0)
Graphics system: Picasso96
Graphics board(s): Picasso IV [Paloma Concierto]
Soundcard(s): Concierto
Hardware Clock: clock + battmem found, sunday 21-apr-2002 18:38:28
Max. Chipmem available: 2048 K
Max. Fastmem available: 130048 K
ROM chip version: 45.20 (Kickstart 3.9)
Workbench version: 45.3 (Workbench 3.9)
SetPatch version: 44.38
Expansion board(s):
5001/6: individual Computers/VMC HyperCOM Z4 (@$00E90000 64k)
4626/23: individual Computers X-Surf (@$00EA0000 64k)
2167/24: Village Tronic Picasso IV (@$40000000 32M)
8512/100: Phase 5 Digital Products CyberStorm PPC/MK III SCSI (@$00F01060
128k)
Cyberstorm PPC serial #: DCC0270
Your computer is an Amiga 4000 Tower.
|
|
From: Giorgio T. <de...@ip...> - 2002-10-12 17:15:08
|
Alle 13:47, sabato 12 ottobre 2002, schneider ha scritto: > Well, without the SCSI driver everything works fine... without any > crash. It=B4s just the damn scsi ... same problem for the buildin a4000= t > or the uw csppc scsi. I have also a 4000 but not T, and honestly i don't know what different=20 hardware interactions there are on this more "recent" Amy. I use a self-compiled 2.4.18 kernel taken from APUS CVS and after=20 the last Rene Brothum's (i hope the spelling is correct) patches of th= e=20 CS-PPC SCSI driver i am using the scsi hdisks (CDrom has still some=20 problems) with Linux quitely easy. If this may help you i envoy my kernel configuration file that is a=20 personalization of what you can find in APUS site. Regards Giorgio |
|
From: schneider <sch...@te...> - 2002-10-12 11:42:00
|
Giorgio Terzi wrote: > Alle 12:31, sabato 12 ottobre 2002, schneider ha scritto: > >>>Post Scriptum. >>>In my last mail i forgotten to say that after the migration of my Linux >>>partitions from IDE to SCSI hdisks, a strange bug seems disappeared: >>>Sometimes, when connected to internet and using X, something >>>hanged the X task or the whole machine. Now seems solved... >>>(I cross my fingers... :-) ). >> >>Seems the same problem like i have. >>Btw: i still have problems with it, sometime it even crashes during init >>of the scsi disks! Sometimes later... bug is still present. > > > I think that the problem, in my case, was some X interactions. This because > excluding step by step every possible source of problems (e.g. daemons like > named etc) i have found that without X, using internet with, for example, > ftp, cvs, and so on, none bug appeared. > To say the true i haven't still stressed a lot the machine after the SCSI > drive migration, but now i haven't found bugs during startup. > > Thinking better i had problems during startup! But this was an hardware > problem : when in my Cyberstorm was broken the PPC MPU. > The symptoms was that 68000 side was perfectly working but in the PPC > side during Linux init the machine crashed. In the beginning only sometimes > but at the end everytime. I hope this is not your case. Well, without the SCSI driver everything works fine... without any crash. It´s just the damn scsi ... same problem for the buildin a4000t or the uw csppc scsi. > > Good Luck! > > Regards > > Giorgio > |
|
From: Giorgio T. <de...@ip...> - 2002-10-12 11:22:27
|
Alle 12:31, sabato 12 ottobre 2002, schneider ha scritto: > > Post Scriptum. > > In my last mail i forgotten to say that after the migration of my Linux > > partitions from IDE to SCSI hdisks, a strange bug seems disappeared: > > Sometimes, when connected to internet and using X, something > > hanged the X task or the whole machine. Now seems solved... > > (I cross my fingers... :-) ). > > Seems the same problem like i have. > Btw: i still have problems with it, sometime it even crashes during init > of the scsi disks! Sometimes later... bug is still present. I think that the problem, in my case, was some X interactions. This because excluding step by step every possible source of problems (e.g. daemons like named etc) i have found that without X, using internet with, for example, ftp, cvs, and so on, none bug appeared. To say the true i haven't still stressed a lot the machine after the SCSI drive migration, but now i haven't found bugs during startup. Thinking better i had problems during startup! But this was an hardware problem : when in my Cyberstorm was broken the PPC MPU. The symptoms was that 68000 side was perfectly working but in the PPC side during Linux init the machine crashed. In the beginning only sometimes but at the end everytime. I hope this is not your case. Good Luck! Regards Giorgio |
|
From: Alan B. <al...@ms...> - 2002-10-09 19:27:54
|
hi, > Hi, > After trying all the 2.4.? kernals, I have found they fail on my system at the PCI probe.(why it fails on my machine and not on others, I cannot > understand, but...) > Kernal 2.4.18 doesn't fail at this point but probes for the Ide doubler and then seems to fail due to some keyboard problem. > Is there any way round this problem. I have a power computing keyboard interface attached to a pc keyboard. > I s there anything I can do, or is there a fix to be implemented into a new kernal? ummm, as far as i can make out, you have no keyboard problem - what you see in your dmesg is just the result of you reseting your Amiga after it locks. the problem is with A1200 IDE driver-code and has been 'fixed' recently in the CVS tree. my Amiga died and i've just got it back up and running again so havent been able to file a 'success' with the development team. but i have my new shiney Debian CD's (went to LinuxEXPO 2002 today) and i have the 2.4.x CVS tree in a nice tar archive ready for compiling and testing a new kernel will be released once problem issue is confirmed alan |
|
From: David J. <jo...@co...> - 2002-10-07 20:10:55
|
Hi, After trying all the 2.4.? kernals, I have found they fail on my system at the PCI probe.(why it fails on my machine and not on others, I cannot understand, but...) Kernal 2.4.18 doesn't fail at this point but probes for the Ide doubler and then seems to fail due to some keyboard problem. Is there any way round this problem. I have a power computing keyboard interface attached to a pc keyboard. I s there anything I can do, or is there a fix to be implemented into a new kernal? Regards, Dave A1200 + PPC + BVision ( jo...@co... ) The day of the Bible is passed. Books have taken its place. -- Washburn |
|
From: Michel <mi...@da...> - 2002-10-05 16:30:55
|
On Sam, 2002-10-05 at 05:05, David Jones wrote: > I have tidied up my XF86Config-4 but still X crashes. (Included files) > X now doesn't report unresolved symbols but still doesn't work. > I have included my dmesg which relates to the crash, it does mention X bu= t not sure why. Because the kernel panics while X runs. (Kind of an ambiguous sentence isn't it? :) > The unresolved symbol problem was recently mentioned on the debian-powerp= c ml > (Petro 20/9) but no answer seems to have come up. (So it's not just > me!) Unresolved symbols usually aren't a problem but at worst a symptom of another problem. > In the Xlog the only errors reported seem to be > (ww) Cannot open APM > (EE) No OS PCI support available > Are these errors significant, and what do they mean. Neither APM nor PCI support is available from the kernel, which shouldn't be a problem. > My system clock still goes wrong on every attempted boot into Linux. The = time is correctly read on startup(the same as on the miggy), but then it > resets the hardware clock to 1902. > I have tried reseting the date from within Linux, using > date -s D10/03/02=20 > this always does the trick (and it survives a reboot?) but sets the time = at 17.00 > what is the syntax to set the time correctly? I usually call date twice, once for the date and once for the time, e.g. date -s 18:30. But if you're connected, you want to try ntpdate. > NIP: 00000000 XER: 20000000 LR: C010CC90 REGS: c1243c60 TRAP: 0400 > MSR: 20009072 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11 > TASK =3D c1242000[235] 'XFree86' mm->pgd c1513000 Last syscall: 54=20 > last math c1242000 > GPR00: 00000000 C1243D10 C1242000 C1A13200 C1477F40 00004611 00000001 000= 00006=20 > GPR08: C01AF530 00000006 C0037CE0 C1275000 02000000 101D34E0 00000000 7FF= FFE04=20 > GPR16: 10280DE0 7FFFFE04 00000005 101D9C64 00009072 77243E80 00000000 C00= 03C98=20 > GPR24: C00039CC 00000000 C1477F40 C1A13200 00004611 C0169A28 00000001 C01= AF530=20 > Call backtrace:=20 > C010C7DC C0037F68 C0003A20 00000001 10054220 102C6F20 10280E74=20 > 1008E8E8 1002458C 1008DDE4 0FDE0C30 00000000=20 > Kernel panic: kernel access of bad area pc 0 lr c010cc90 address 0 tsk XF= ree86/235 Piping this through ksymoops might be interesting. > Section "Device" > Identifier "BVPPC" > Driver "fbdev" > # Option "UseFBDev" > Option "ShadowFB" "off" > Option "NoInt10" > EndSection Have you tried without switching off ShadowFB? > (II) FBDev(0): using default device > (II) Running in FRAMEBUFFER Mode > (**) FBDev(0): Depth 16, (--) framebuffer bpp 16 > (=3D=3D) FBDev(0): RGB weight 565 > (=3D=3D) FBDev(0): Default visual is TrueColor > (=3D=3D) FBDev(0): Using gamma correction (1.0, 1.0, 1.0) > (II) FBDev(0): Hardware: Permedia2 (vidmem: 8192k) > (**) FBDev(0): Option "ShadowFB" "off" > (II) FBDev(0): Checking Modes against framebuffer device... > (II) FBDev(0): Checking Modes against monitor... > (--) FBDev(0): Virtual size is 1024x768 (pitch 1024) > (**) FBDev(0): Built-in mode "current": 78.9 MHz, 60.2 kHz, 75.2 Hz > (II) FBDev(0): Modeline "current" 78.93 1024 1040 1136 1312 768 769 7= 72 800 +hsync +vsync -csync > (++) FBDev(0): DPI set to (100, 100) > (II) Loading sub module "fb" > (II) LoadModule: "fb" > (II) Loading /usr/X11R6/lib/modules/libfb.a > (II) Module fb: vendor=3D"The XFree86 Project" > compiled for 4.1.0.1, module version =3D 1.0.0 > ABI class: XFree86 ANSI C Emulation, version 0.1 This is probably truncated due to the panic. As you're probably using ext2 filesystems, you could remount the one containing /var/log synchronously, e.g. mount -o remount,sync / to get the full log. --=20 Earthling Michel D=E4nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast |
|
From: David J. <jo...@co...> - 2002-10-05 14:52:39
|
Hi, Thanks for the replies. I have tidied up my XF86Config-4 but still X crashes. (Included files) X now doesn't report unresolved symbols but still doesn't work. I have included my dmesg which relates to the crash, it does mention X but not sure why. The unresolved symbol problem was recently mentioned on the debian-powerpc ml (Petro 20/9) but no answer seems to have come up. (So it's not just me!) In the Xlog the only errors reported seem to be (ww) Cannot open APM (EE) No OS PCI support available Are these errors significant, and what do they mean. My system clock still goes wrong on every attempted boot into Linux. The time is correctly read on startup(the same as on the miggy), but then it resets the hardware clock to 1902. I have tried reseting the date from within Linux, using date -s D10/03/02 this always does the trick (and it survives a reboot?) but sets the time at 17.00 what is the syntax to set the time correctly? The time problem isn't important though until X works properly. Regards, Dave ( jo...@co... ) If nominated, I will not run; if elected, I will not serve. -- Gen. William Sherman, on the request that he accept the Republican presidential nomination |
|
From: Michel <mi...@da...> - 2002-10-03 22:02:07
|
On Don, 2002-10-03 at 23:09, Andreas W=FCst wrote: >=20 > > Section "Module" > > Load "ddc" > > Load "GLcore" > > Load "dbe" > > #=20 > > Load "dri" >=20 > what happended here ... >=20 > > Load "extmod" > > Load "glx" > > Load "pex5" > > Load "record" > > Load "xie" > > Load "bitmap" > > Load "freetype" > > Load "speedo" > > Load "type1" > > Load "vbe" > > #=20 > > Load "int10" >=20 > ... and here? >=20 > If you want to comment a line out, you have to put the # in the same line > which you want to comment, but not one above. Good point, I didn't notice this before. In fact, you only need to load extmod and maybe bitmap, type1 and freetype, depending on what fonts you want to use. > > EndSection >=20 > > Section "Device" > > Identifier "CVPPC" > > Driver "fbdev" > > Option "NoInt10" > > EndSection >=20 > Add: Option "UseFBDev" This _is_ the fbdev driver, it can't do anything else but use a framebuffer device. ;) This option is important for the glint driver though. [ loads of unresolved symbols ] > Hmm, it looks like it has something to do with int10, because this gets > mentioned at the beginning of each line. Please comment out >=20 > Load "int10" >=20 > by using >=20 > # Load "int10" >=20 > and keep the >=20 > Option "NoInt10" >=20 > in your Device section! Yes, please try only loading the minimum set of modules I mentioned above. If that helps with the fbdev driver, you might also try glint again... --=20 Earthling Michel D=E4nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast |
|
From: Andreas <an...@po...> - 2002-10-03 21:17:20
|
Hello David > Hi, > I have again attempting to get XFree-4 up and running, I seem to have > problems with the glint driver causing "symbol unresolved" problems. I have > mentioned this before but nobody can explain the fault. I therefore have > decide to try to use the FBDev instead of glint. I hope this is possible. It's always possible to use FBDev I think. > I > have had a little more success but still things are not working correctly. I > have included my XF86Config-4 to see if there are any obvious mistakes. > Using this config I do get output to the monitor, this is an uncorrupted > screen which is a vertically offset version of my workbench screen. Yes, seen this effect here too, maybe something about initialisation. > I can > then go no further the machine seems to lock, with no keyboard or mouse > response at all. Well, it goes away after a sec or so, and then proceeds loading. Seems as your X server crashes here. Please cf. my comments on your X error log below. > I have included my XFree-log if that helps solve the > problem. The problem seems related to the unresolved symbols. I am wondering > if these "symbols" could have become corrupted in some way, are they part of > a .deb file. Could I reinstall the necessary files from my woody cd's? I did > have similar X output to this when first using XF86-3, but it was solved by > using a correct config file, I hope this will be the same. As usual, any > help would be great. I am sorry to keep coming back to this, but I am > completely stuck. > > Section "Module" > Load "ddc" > Load "GLcore" > Load "dbe" > # > Load "dri" what happended here ... > Load "extmod" > Load "glx" > Load "pex5" > Load "record" > Load "xie" > Load "bitmap" > Load "freetype" > Load "speedo" > Load "type1" > Load "vbe" > # > Load "int10" ... and here? If you want to comment a line out, you have to put the # in the same line which you want to comment, but not one above. > EndSection > Section "Device" > Identifier "CVPPC" > Driver "fbdev" > Option "NoInt10" > EndSection Add: Option "UseFBDev" cf. http://linux-apus.sourceforge.net/contrib/ I use the following one: Section "Device" Identifier "Generic Video Card" Driver "fbdev" Option "UseFBDev" "true" Option "NoInt10" EndSection > Symbol xf86ExecX86int10 from module /usr/X11R6/lib/modules/libvbe.a is > unresolved! Symbol xf86ExecX86int10 from module > /usr/X11R6/lib/modules/libvbe.a is unresolved! Symbol xf86ExecX86int10 from > module /usr/X11R6/lib/modules/libvbe.a is unresolved! Symbol > xf86ExecX86int10 from module /usr/X11R6/lib/modules/libvbe.a is unresolved! > Symbol xf86ExecX86int10 from module /usr/X11R6/lib/modules/libvbe.a is > unresolved! Symbol xf86ExecX86int10 from module > /usr/X11R6/lib/modules/libvbe.a is unresolved! Symbol xf86ExecX86int10 from > module /usr/X11R6/lib/modules/libvbe.a is unresolved! Symbol > xf86ExecX86int10 from module /usr/X11R6/lib/modules/libvbe.a is unresolved! > Symbol xf86Int10AllocPages from module /usr/X11R6/lib/modules/libvbe.a is > unresolved! Symbol xf86ExecX86int10 from module > /usr/X11R6/lib/modules/libvbe.a is unresolved! Symbol xf86ExecX86int10 from > module /usr/X11R6/lib/modules/libvbe.a is unresolved! Symbol > xf86ExecX86int10 from module /usr/X11R6/lib/modules/libvbe.a is unresolved! > Symbol xf86ExecX86int10 from module /usr/X11R6/lib/modules/libvbe.a is > unresolved! Symbol xf86int10Addr from module /usr/X11R6/lib/modules/libvbe.a > is unresolved! Symbol xf86int10Addr from module > /usr/X11R6/lib/modules/libvbe.a is unresolved! Symbol xf86int10Addr from > module /usr/X11R6/lib/modules/libvbe.a is unresolved! Symbol xf86int10Addr > from module /usr/X11R6/lib/modules/libvbe.a is unresolved! Symbol > xf86int10Addr from module /usr/X11R6/lib/modules/libvbe.a is unresolved! > Symbol xf86ExecX86int10 from module /usr/X11R6/lib/modules/libvbe.a is > unresolved! Symbol xf86ExecX86int10 from module > /usr/X11R6/lib/modules/libvbe.a is unresolved! Symbol xf86ExecX86int10 from > module /usr/X11R6/lib/modules/libvbe.a is unresolved! Symbol xf86FreeInt10 > from module /usr/X11R6/lib/modules/libvbe.a is unresolved! Symbol > xf86Int10FreePages from module /usr/X11R6/lib/modules/libvbe.a is > unresolved! Symbol xf86FreeInt10 from module /usr/X11R6/lib/modules/libvbe.a > is unresolved! Symbol xf86Int10FreePages from module > /usr/X11R6/lib/modules/libvbe.a is unresolved! Symbol xf86int10Addr from > module /usr/X11R6/lib/modules/libvbe.a is unresolved! Symbol xf86int10Addr > from module /usr/X11R6/lib/modules/libvbe.a is unresolved! Symbol > xf86int10Addr from module /usr/X11R6/lib/modules/libvbe.a is unresolved! > Symbol xf86int10Addr from module /usr/X11R6/lib/modules/libvbe.a is > unresolved! Symbol xf86ExecX86int10 from module > /usr/X11R6/lib/modules/libvbe.a is unresolved! Symbol xf86Int10AllocPages > from module /usr/X11R6/lib/modules/libvbe.a is unresolved! Symbol > xf86InitInt10 from module /usr/X11R6/lib/modules/libvbe.a is unresolved! Hmm, it looks like it has something to do with int10, because this gets mentioned at the beginning of each line. Please comment out Load "int10" by using # Load "int10" and keep the Option "NoInt10" in your Device section! I have no idea what is going on here (I am not the xf86 guy), but maybe it has something to do with the lacking pci support of the kernel?? PS: have you mastered your system clock going nuts? -- Hope you have some succes now, wishes, Andi |
|
From: David J. <jo...@co...> - 2002-10-03 19:08:38
|
Hi, I have again attempting to get XFree-4 up and running, I seem to have problems with the glint driver causing "symbol unresolved" problems. I have mentioned this before but nobody can explain the fault. I therefore have decide to try to use the FBDev instead of glint. I hope this is possible. I have had a little more success but still things are not working correctly. I have included my XF86Config-4 to see if there are any obvious mistakes. Using this config I do get output to the monitor, this is an uncorrupted screen which is a vertically offset version of my workbench screen. I can then go no further the machine seems to lock, with no keyboard or mouse response at all. I have included my XFree-log if that helps solve the problem. The problem seems related to the unresolved symbols. I am wondering if these "symbols" could have become corrupted in some way, are they part of a .deb file. Could I reinstall the necessary files from my woody cd's? I did have similar X output to this when first using XF86-3, but it was solved by using a correct config file, I hope this will be the same. As usual, any help would be great. I am sorry to keep coming back to this, but I am completely stuck. Regards, Dave ( jo...@co... ) God cannot alter the past, but historians can. -- Samuel Butler A1200 + PPC + BVision (All working flawlessly on the Amiga side) |
|
From: Björn J. <kh...@te...> - 2002-10-02 09:19:12
|
Michel =3D?ISO-8859-1?Q?D=3DE4nzer?=3D wrote about PPP support: > On Die, 2002-10-01 at 15:12, Bj=F6rn Johansson wrote: > > Michel =3D?ISO-8859-1?Q?D=3DE4nzer?=3D wrote about PPP support: > > > > > On Mon, 2002-09-30 at 20:15, Bj=F6rn Johansson wrote: > > > > > > > > I can't find the ppp module for 2.4.18-apus, does > > > > it even exist for the 2.4.x yet? > > > > > > find /lib/modules/`uname -r`/kernel -name \*ppp\* > > > > No such file or directory. > > > > > > Searching the /lib/modules/2.2.10/net > > I find ppp. > > > > But searching the /lib/modules/2.4.18-apus/kernel/net > > I don't find ppp. > > > > Do you know if ppp exist somewhere else? > > Yes, I forgot that it's built into the kernel. What was the problem > again? :) The problem right now is that pon won't start the internet-connection. I thought one of the reason because of this could be that pppd wasn't started correctly, this is what happens when I try to initialize the pppd from /etc/init.d/ pppd: The remote system is required to authenticate itself pppd: but I couldn't find any suitable secret(password) for it to do so. pppd: (None of the available passwords would let it use an IP address.) Any clues? -- Bj=F6rn Johansson "Debian rocks!!" |
|
From: Alan B. <al...@ms...> - 2002-10-02 08:51:12
|
Hi, > I've tried get on the net by using pon provider, but nothing happens :(. possibly a software issue. > Is there another tool besides pon which can start my internet connection? > Btw. I've used pppconfig to setup the provider script, so there's nothing > wrong with my script. ..i wouldnt assume that - there could be a bug in the code and the config is not correct etc - NEVER assume that a config tool or fancy GUI wizard does its job correctly. the solution here is to either go to a general Linux PPP lists armed with your files....or send us your PPP config files (though my system is /dev/null right now (along with all configs). i would, if you, check /etc/ppp and see what each file says. does the modem light not blink etc at all when using 'pon'? can you echo "ATZ" > /dev/ttyS0 ? are you in the 'dialup' group? theres some security to fix before you can use PPP as a user. alan |
|
From: Björn J. <kh...@te...> - 2002-10-01 17:02:13
|
Michel =3D?ISO-8859-1?Q?D=3DE4nzer?=3D wrote about PPP support: > On Die, 2002-10-01 at 15:12, Bj=F6rn Johansson wrote: > > Michel =3D?ISO-8859-1?Q?D=3DE4nzer?=3D wrote about PPP support: > > > > > On Mon, 2002-09-30 at 20:15, Bj=F6rn Johansson wrote: > > > > > > > > I can't find the ppp module for 2.4.18-apus, does > > > > it even exist for the 2.4.x yet? > > > > > > find /lib/modules/`uname -r`/kernel -name \*ppp\* > > > > No such file or directory. > > > > > > Searching the /lib/modules/2.2.10/net > > I find ppp. > > > > But searching the /lib/modules/2.4.18-apus/kernel/net > > I don't find ppp. > > > > Do you know if ppp exist somewhere else? > > Yes, I forgot that it's built into the kernel. What was the problem > again? :) I've tried get on the net by using pon provider, but nothing happens :(. Is there another tool besides pon which can start my internet connection? Btw. I've used pppconfig to setup the provider script, so there's nothing wrong with my script. > > > It is really bad not having ppp working with Linux, besides > > that, I don't have any working graphics either, since someone > > told me earlier that Xfree86 4.1.x doesn't work with AGA, and > > that definitely seems to be the case. > > Yep. -- Bj=F6rn Johansson "Debian rocks!!" |
45 messages has been excluded from this view by a project administrator.
