| Summary: | 4_a3: no console video with 3.12.0-desktop-2.mga4 kernel | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Bit Twister <bittwister2> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | tmb |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | kernel | CVE: | |
| Status comment: | |||
|
Description
Bit Twister
2013-11-09 08:26:54 CET
Installation of fglrx-kernel-desktop-latest-13.250.18-11.mga4.nonfree.x86_64.rpm and dkms modules did not fix the problem. Severity:
normal =>
major try to reconfigure graphic setup through mcc, as it's probably still set to use the free driver CC:
(none) =>
tmb (In reply to Thomas Backlund from comment #2) > try to reconfigure graphic setup through mcc, as it's probably still set to > use the free driver I would hope an upgrade/update would not change whatever driver was set by the user. :( Example: I have fglrx set as driver, new fglrx kernel/driver release should not change it to radeon or vesa. In this case it was fglrx before the update. Quick run through mcc, graphic setup, reboot did nothing towards fixing the problem. I saw no errors in journalctl. Falling back to desktop 3.12.0-1.mga4 boot will give console video. (In reply to Bit Twister from comment #3) > (In reply to Thomas Backlund from comment #2) > > try to reconfigure graphic setup through mcc, as it's probably still set to > > use the free driver > > I would hope an upgrade/update would not change whatever driver was set by > the user. :( > In normal situation (as in stable releases) it should not happend. > Example: I have fglrx set as driver, new fglrx kernel/driver release should > not change it to radeon or vesa. What happend here was you updated before the matching fglrx prebuilt driver was available (due to a forgotten commit by me, so the sheduled build failed), so the the needed kernel module was not available, so drakx tries to switch back to a config according to available modules... (In reply to Thomas Backlund from comment #4) > What happend here was you updated before the matching fglrx prebuilt driver > was available (due to a forgotten commit by me, I think it would be nice if a successful kernel build would kickoff a fglrx build or at least send the submitter an email to commit a fglrx build. > so drakx tries to switch back to a config according to available modules Hmmm, in that case I would have thought I would have had video. I'll go ahead and configure radeon/vesa/reboot to see if I can get any video. Changing to Xorg/vesa did not provide console video. :( Guessing problem needs to be assigned to kernel or dracut maybe since kde/startx is working. And if you reconfigure it for fglrx again ? (In reply to Thomas Backlund from comment #7) > And if you reconfigure it for fglrx again ? Yes as soon as I read comment 2. FYI, I have reconfigured back to fglrx, rebooted, no video, startx, su - root, dracut -f, reboot, no video. Found the problem. Workaround solution, remove the vga-xxx argument from the kernel line in /boot/grub/menu.lst Source RPM:
(none) =>
kernel 3.12.0-desktop-3.mga4 resolved the problem. $ journalctl | grep 'kernel: Command line:' Nov 17 00:22:07 wb.home.test kernel: Command line: BOOT_IMAGE=mga4_64_beta1 root=LABEL=cauldron nokmsboot vga=790 Status:
NEW =>
RESOLVED |