Bug 115432 - ACER TRAVELMATE 8100 - First installation - ERROR-List
Summary: ACER TRAVELMATE 8100 - First installation - ERROR-List
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Beta 4
Hardware: i586 SUSE Other
: P5 - None : Major
Target Milestone: ---
Assignee: Olaf Kirch
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-06 15:01 UTC by Daniel Gramsch
Modified: 2005-09-22 08:15 UTC (History)
1 user (show)

See Also:
Found By: Beta-Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
hwinfo via suse10b4 (217.23 KB, text/plain)
2005-09-06 15:04 UTC, Daniel Gramsch 		Details
boot.msg (25.86 KB, text/plain)
2005-09-06 15:04 UTC, Daniel Gramsch 		Details
boot.omsg (23.41 KB, text/plain)
2005-09-06 15:05 UTC, Daniel Gramsch 		Details
warn.log (61.91 KB, text/x-log)
2005-09-06 15:05 UTC, Daniel Gramsch 		Details
kdm.log (7.08 KB, text/x-log)
2005-09-06 15:06 UTC, Daniel Gramsch 		Details
Xorg.0.log (16.16 KB, text/x-log)
2005-09-06 15:07 UTC, Daniel Gramsch 		Details
Xorg.0.log.old (40.48 KB, application/octet-stream)
2005-09-06 15:07 UTC, Daniel Gramsch 		Details
Xorg.99.log (40.09 KB, text/x-log)
2005-09-06 15:07 UTC, Daniel Gramsch 		Details
Xorg.99.log.old (39.95 KB, application/octet-stream)
2005-09-06 15:08 UTC, Daniel Gramsch 		Details
messages (170.78 KB, application/octet-stream)
2005-09-06 15:09 UTC, Daniel Gramsch 		Details
boot.msg v.2 (27.20 KB, text/plain)
2005-09-06 16:40 UTC, Daniel Gramsch 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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.