Bug 115432

Summary:	ACER TRAVELMATE 8100 - First installation - ERROR-List
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Daniel Gramsch <info>
Component:	Kernel	Assignee:	Olaf Kirch <okir>
Status:	RESOLVED WONTFIX	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Major
Priority:	P5 - None	CC:	behlert
Version:	Beta 4
Target Milestone:	---
Hardware:	i586
OS:	SUSE Other
Whiteboard:
Found By:	Beta-Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	hwinfo via suse10b4 boot.msg boot.omsg warn.log kdm.log Xorg.0.log Xorg.0.log.old Xorg.99.log Xorg.99.log.old messages boot.msg v.2

Description Daniel Gramsch 2005-09-06 15:01:15 UTC

After booting with safe settings and options "... BrokenModules=yenta_socket"
(Bug 113778) the installation one accomplished. The last Monitor
"Hardware-Konfiguration" hung itself up. After the reeboot the following errors
were determined:

- change for the dissolution of monitor produced a black screen (system hung
itself up)
- look for the printer >>> system hung itself up
- for the modem no driver was found.
- language and key assignment had to be assigned manually
- with the configuration of the sound yast have the system stopped
- wlan & bluetooth I could not test.
- errors for PCI, IRQ and others i fount in logsfiles

thanks for your help

mario

Comment 1 Daniel Gramsch 2005-09-06 15:04:00 UTC

Created attachment 48937 [details]
hwinfo via suse10b4

Comment 2 Daniel Gramsch 2005-09-06 15:04:47 UTC

Created attachment 48939 [details]
boot.msg

Comment 3 Daniel Gramsch 2005-09-06 15:05:12 UTC

Created attachment 48940 [details]
boot.omsg

Comment 4 Daniel Gramsch 2005-09-06 15:05:56 UTC

Created attachment 48942 [details]
warn.log

Comment 5 Daniel Gramsch 2005-09-06 15:06:24 UTC

Created attachment 48943 [details]
kdm.log

Comment 6 Daniel Gramsch 2005-09-06 15:07:00 UTC

Created attachment 48944 [details]
Xorg.0.log

Comment 7 Daniel Gramsch 2005-09-06 15:07:25 UTC

Created attachment 48945 [details]
Xorg.0.log.old

Comment 8 Daniel Gramsch 2005-09-06 15:07:49 UTC

Created attachment 48946 [details]
Xorg.99.log

Comment 9 Daniel Gramsch 2005-09-06 15:08:13 UTC

Created attachment 48947 [details]
Xorg.99.log.old

Comment 10 Daniel Gramsch 2005-09-06 15:09:59 UTC

Created attachment 48948 [details]
messages

Comment 11 Klaus Kämpf 2005-09-06 15:15:07 UTC

I see lots of 
"PCI: No IRQ known for interrupt pin A of device 0000:00:01.0. Please try 
using pci=biosirq" 
in boot.msg. 
 
Please try booting with "pci=biosirq" (and complain to your vendor about 
broken BIOS :-))

Comment 12 Daniel Gramsch 2005-09-06 16:37:27 UTC

(In reply to comment #11)
> I see lots of 
> "PCI: No IRQ known for interrupt pin A of device 0000:00:01.0. Please try 
> using pci=biosirq" 
> in boot.msg. 
>  
> Please try booting with "pci=biosirq" (and complain to your vendor about 
> broken BIOS :-)) 

OKAY, the new boot.msg i have attached. but by ping to LAN the network is
not reachable by this boot-option.

Comment 13 Daniel Gramsch 2005-09-06 16:40:00 UTC

Created attachment 48959 [details]
boot.msg v.2

Comment 14 Klaus Kämpf 2005-09-07 05:58:07 UTC

btw, please use the correct MIME type for your attachments.

Comment 15 Klaus Kämpf 2005-09-07 05:59:51 UTC

Now I see 
"<4>PCI: IRQ 0 for device 0000:00:01.0 doesn't match PIRQ mask - try 
pci=usepirqmask" 
in the log. 
 
Looks more and more like a kernel resp. BIOS issue. 
 
Is your system at the latest BIOS revision ? 
Can you try to boot with "pci=usepirqmask" ?

Comment 16 Klaus Kämpf 2005-09-07 06:00:28 UTC

Moving this to 'Kernel' now

Comment 17 Klaus Kämpf 2005-09-07 06:02:06 UTC

Stefan, do we have such a system for testing ?

Comment 18 Stefan Behlert 2005-09-07 07:59:45 UTC

Unfortunately no :(

Comment 19 Olaf Kirch 2005-09-14 13:19:49 UTC

We seen to have a workaround for the yenta problem in bug #113778 now,  
so please grab the test kernels referenced there and re-try. Other 
fixes we have applied in the meanwhile may fix the other issues as well.

Comment 20 Olaf Kirch 2005-09-22 08:15:57 UTC

This doesn't seem to be relevant anymore.