Mailinglist Archive: opensuse-amd64 (380 mails)

[detlef oertel <oertel@xxxxxx>]

Hello Willibald Krenn,

you told that your kylix IDE is running.
I got the Problem that my kylix IDE is running too, but
I always get a error if compile a program with kylix.
The error is:
[Fehler] Falsches Dateiformat: libX11.so.6

I installed kylix with
linux32 setup.sh
and i start kylix with
linux32 startdelphi

my system is a suse9/amd64
kernel 2.4.21-201-default

any hint for me ?

thank you

detlef oertel

Willibald Krenn wrote:
> Am Montag, 12. Januar 2004 09:36 schrieb Andi Kleen:
>
> > On Sun, 11 Jan 2004 22:38:27 +0100
> > [..]
> > ataraid doesn't work on 2.6. Known problem. The driver still
> > needs to be ported.
>
>
> Thanks for pointing that out.. Well, as everything is now working with the 
> patched SuSE 2.4 kernel (even Kylix IDE!) I've absolutely no reason to switch 
> to 2.6.
>
>
> > It's most likely a bug in the shuttle BIOS. Try updating the BIOS.
> > Or disable "USB legacy support" in the BIOS setup (may or may not help)
>
>
> True, after disabling 'USB Keyboard support' (buried somewhere deep in the 
> BIOS config) even the automatic installer managed to boot from DVD!
>
>
> > You can test that by booting the kernel with idle=poll (not recommended
> > as a permanent solution because it burns a lot of power). If that
> > helps the BIOS is missing a workaround for an CPU bug that causes
> > it to corrupt 64bit registers when running the USB emulation code.
>
>
> Hmm, I hope Shuttle will provide an update for this. But on the other hand 
> it's not a complete disaster because my keyboard has a PS/2 and an USB plug, 
> so I have the choice..
>
>
> > In the worst case you can run a 32bit X server as a workaround. That should
> > work.
>
>
> I'll keep that in mind - if I'll somewhen need hardware acceleration this will 
> probably the only way to go.
>
>
> > Well, the idea is when you do things with your grub configuration or your
> > kernel rpm you should be also able to fix it manually from a repair system.
>
>
> I understand. However I thought the install DVD would also feature such a 
> minimal repair system. In the old SuSE days (5.3 etc.) there always was the 
> option to re-install the kernel IIRC..
>
>
> > The automatic options are more aimed at people who don't change intimate
> > details of the system. Obviously they cannot undo all the damage an user
> > is able to do by hand.
>
>
> However, I'm still of the opinion that it would be very helpful if the install 
> DVD featured a package reinstall/delete/.. dialog without having to go 
> through all the disk-scans etc.
>
>
> > In general every time you have oopses you should report them. Otherwise
> > they cannot get fixed.
>
>
> Seems this oops was related to the USB bug; Nevertheless, see below:
>
> Thanks,
>  Willi
>
> USB-Keyboard support turned ON in Shuttle BIOS (AN50S00Y):
> ==================================================
>
> Display 1:
>
> > > > SuSE Linux installation program v 1.5 (c) 1996-2003 SuSE Linux AG <<<
>
> Starting hardware detection...
>
> Display 3:
> [...]
> insmod usb-ohci
> Using /modules/usb-ohci.o
>
>
> Display 4:
> [...]
> usb-ohci.c: usb-00:02.1, PCI device 10de:00d7
> Unable to handle kernel paging request at virtual address 000000008010ddbf
>  printing rip:
> 000000008010ddbf
> PML4 4e43067 PGD 0
> Oops: 0010
> CPU 0
> Pid: 0, comm: swapper Not tainted
> RIP: 0010:[<000000008010ddbf>]
> RSP: 0000:ffffffff8048dfd8 EFLAGS: 00010246
> RAX: 0000000000000000 RBX: ffffffff8010dda0 RCX: 0000000000000001
> RDX: ffffffff80479620 RSI: 0000000000000032 RDI: 0000000000000019
> RBP: 0000000000000000 R08: ffffffff80488d00 R09: 0000000000000001
> R10: 0000010037b8cb80 R11: 0000000000000090 R12: 0000000000000000
> R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
> FS: 0(0) GS:ffffffff80484c80(0000) knlGS:0
> CS: 0010 DS: 0018 CR0: 000000008005003b
> CR2: 000000008010ddbf CR3: 00000000101000 CR4: 6e0
> Process swapper (pid:0, stackpage=ffffffff8048d000)
> Stack: ffffffff8048dfd8 0 0 ffffffff8010de2a
>        10a ffffffff8048f775 ffffffff803e4ca0 0
> Call Trace: [<ffffffff8010de2a>]{cpu_idle+42}
>
> Code: Bad RIP value
>  <0>Kernel panic: Attempted to kill the idle task!
> In idle task - not syncing