|
Bugzilla – Full Text Bug Listing |
| Summary: | RC1 installation lockup immediately after first reboot with Sat TV PCI card | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Keith Goggin <keith.goggin> |
| Component: | Kernel | Assignee: | Torsten Duwe <duwe> |
| Status: | RESOLVED FIXED | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | lnussel |
| Version: | RC 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Keith Goggin
2005-09-15 12:18:26 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. Werner, could you, please have a look at it? Is it a base-system related? 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. A lock up sounds more like a kernel problem. Please try booting with "save settings" 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. Torsten, you're the DVB guy; can you help debug this? 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? "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. So, does this still occur with a recent kernel? If so, please supply lspci -v for the card. Assumed fixed. |