Bug 117203 - RC1 installation lockup immediately after first reboot with Sat TV PCI card
Summary: RC1 installation lockup immediately after first reboot with Sat TV PCI card
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Kernel (show other bugs)
Version: RC 1
Hardware: Other All
: P5 - None : Normal
Target Milestone: ---
Assignee: Torsten Duwe
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-15 12:18 UTC by Keith Goggin
Modified: 2006-08-08 13:31 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Keith Goggin 2005-09-15 12:18:26 UTC
The installation failed after first reboot on AMD Athlon 2400+ with VVmer TV@SAT
PCI card (BT Conexant Fusion 878A/Twinhan DTV20023)system freezes after
Comment 1 Keith Goggin 2005-09-15 12:29:41 UTC
"System Boot Control: The system has been running /etc/unit.d/boot.local
Starting syslog services"
Problem reproducable as follows
Select ACPI disabled install F3 screen resolution 800x600 minimal text mode
system. Selected /dev/hda9 as root in place of /dev/hda6 otherwise default
options. No logs recovered as system locked during reboot.
Same problem observed in SUPER 10 work around is to remove ofending PCI card.  
Comment 2 Lukas Ocilka 2005-09-15 13:04:56 UTC
Werner, could you, please have a look at it? Is it a base-system related?
Comment 3 Dr. Werner Fink 2005-09-15 13:28:35 UTC
No, TV sat cards are not common hardware on all systems.
IMHO this is a hardware problem with the motherboard
and/or its BIOS combined with the TV sat card.

Maybe changing the PCI slot and/or changing the
BIOS/CMOS setup for the used slot may help ...
it may also required to update the BIOS of
the motherboard.
Comment 4 Klaus Kämpf 2005-09-15 13:41:34 UTC
A lock up sounds more like a kernel problem. 
 
Please try booting with "save settings" 
Comment 5 Keith Goggin 2005-09-15 15:13:07 UTC
Tried "installation -- Safe settings" with the same result. I have to say I've
not previously got this card to work properly in linux but was tempted try now
because of reported hardware detection changes in kernel 2.6.13. But I have had
it working in 'a non-Linux OS' so the hardware has had at least some testing.
The motherboard is ASUS A7N8X DeLuxe. I'll look to see if there is a bios
upgrade available. I'll also install without the card and see if I can add it later.
Comment 6 Olaf Kirch 2005-09-22 07:35:05 UTC
Torsten, you're the DVB guy; can you help debug this? 
Comment 7 Torsten Duwe 2005-09-22 09:55:54 UTC
The Bt878 is quite common on very cheap hardware, IIRC we have no similar  
reports from these cards. I second Werner in comment #3, plugging the card  
into another slot is worth a try. Asus likes to do weird and undocumented  
things on their mainboards :-( OTOH having it working with "other OS" special  
drivers is at least half a point.  
 
Needless to ask, RC4 / final shows the same behaviour? 
Comment 8 Gerd Hoffmann 2005-09-22 11:08:54 UTC
"lspci -v" for the card in question please.  Booting the rescue system should
work ok for that as it doesn't come with v4l/dvb drivers ;)

There is at least one pretty shitty bt878-based dvb card design (I think it is
the twinhan one) where the normal bttv initialization kills the machine by some
hardware lockup.  The only way around that I know of is to identify the card by
PCI Subsystem ID and then never ever touch any register of PCI function #0.

So it might be simply the ID of the card in question isn't in the drivers list
yet.  Some motherboard issue is possible as well though.
Comment 9 Torsten Duwe 2006-04-20 12:13:31 UTC
So, does this still occur with a recent kernel? If so, please supply lspci -v for the card.
Comment 10 Torsten Duwe 2006-08-08 13:31:11 UTC
Assumed fixed.