Description of problem: - At boot time, system locks after showing #starting udev - Even magickeys do not work - Removing /lib/modules/*/kernel/drivers/video/via/viafb.ko.gz resolves the problem. Could this module be blacklisted? Card:S3 UniChrome-based cards with 3D support: VIA Technologies, Inc.|K8M800/K8N800/K8N800A [S3 UniChrome Pro] [DISPLAY_VGA] (vendor:1106 device:3108 subv:17aa subd:1008) (rev: 01)
CC: (none) => anssi.hannula, pterjanAssignee: bugsquad => tmbSource RPM: (none) => kernel
I have found that the file /etc/modprobe.d/blacklist-compat already blocks all fb modules except viafb one. This looks like it was forgotten. Adding the line : blacklist viafb solves the bug. As this bug prevents using Mageïa LiveCD on VIA video hardware and a solution is known, I make it release blocker. Hoping it can be done before RC1?
Priority: Normal => release_blockerAssignee: tmb => bugsquadTarget Milestone: --- => Mageia 1Source RPM: kernel => module-init-tools
tks i just commited your change. Please test next module-init-tools rpm and reopen this bugreport if needed.
Status: NEW => RESOLVEDCC: (none) => dmorganecResolution: (none) => FIXED
It is OK
Status: RESOLVED => VERIFIED
Closing then
Status: VERIFIED => RESOLVEDCC: (none) => ennael1
Hi there, I hit the exact same symptoms but with a fresh install of mageia 1 on one of my computers :-( The reason is not the same though, it comes from the modules firewire-core firewire-ohci that segfaults at boot on that device: 01:00.4 FireWire (IEEE 1394): ALi Corporation M5253 P1394 OHCI 1.1 Controller I solved the pb by blacklisting them after having mounted my partition by other means. I guess I am a bit unlucky on that one, but that certainly needs to be reported in the install notes because is a no-go install for those having that card :-/ That precise card is known to have pb with the firewire module, but up to now, it was not imparing the kernel: see https://qa.mandriva.com/show_bug.cgi?id=62631 Cheers, Chris.
Status: RESOLVED => REOPENEDCC: (none) => dirteatResolution: FIXED => (none)
(In reply to comment #6) That's a different issue (same symptoms, but different cause), please open a new report.
Status: REOPENED => RESOLVEDResolution: (none) => FIXED
ok, done in https://bugs.mageia.org/show_bug.cgi?id=1574