After upgrade from 6.14.4-r1 to 7.0.0 I've got two issues, disgrade to 6.14.6-r1 fix both, so looks like it's 7.0.0 bug. I've found only one report about similar issue, and that guy also use very old card - he have R250 while mine is R350 [Radeon 9800 Pro] - so this bug is probably happens only on old cards. First problem - X doesn't start after upgrade, with this error in logs: [ 33.188] (II) [KMS] drm report modesetting isn't supported. [ 33.188] (EE) Screen 0 deleted because of no matching config section. [ 33.188] (II) UnloadModule: "radeon" [ 33.188] (EE) Device(s) detected, but none match those in the config file. This can be solved by switching off CONFIG_FB_RADEON in kernel. All radeon-related howtos insist this option MUST be switched on, but looks like it conflict with 7.0.0. As side-effect switching off this option result in using very small font while booting kernel, and ignoring attempt to increase it with vga= kernel option. Second problem - when X switching to text mode (with Ctrl-Alt-F1) or just switching off (after pressing power button on case to shutdown system) it often hang overall system: shutdown process freezes, kernel reply on ping but daemons like ssh doesn't work, and only way to switch it off is reset button or press power button for 5 seconds.
> All radeon-related howtos insist this option MUST be switched on disproven - read http://www.gentoo.org/doc/en/xorg-config.xml *carefully* Looks INVALID altogether - xf86-video-ati 7.0.0 is KMS-only and these problems seems to be caused by misconfiguration.
(In reply to comment #1) > > All radeon-related howtos insist this option MUST be switched on > disproven - read http://www.gentoo.org/doc/en/xorg-config.xml *carefully* Ok, I agree, framebuffer mentioned in howtos to allow lm_sensors. But, anyway, I've used 7.0.0 with disabled framebuffer driver (because it won't work with enabled driver) but still have issue with hang on shutdown/switch to text mode. Also, I'm enabling framebuffer driver just to get readable text while kernel boot, because without it text is too small, and I can't change this using vga= option. Is there another way to control video mode while kernel boot without framebuffer driver? > Looks INVALID altogether - xf86-video-ati 7.0.0 is KMS-only and these > problems seems to be caused by misconfiguration. Ok, let's inspect my configuration and explain how it misconfigured. I'll include some lines/files below, and attach the rest. Let me know if you need some else files. Motherboard: ASUS A7N8X-E Deluxe (REV 2.xx) Chipset: nForce2 Video (AGP): ATI Radeon R350 [Radeon 9800 Pro] ---from /etc/make.conf--- INPUT_DEVICES="evdev" VIDEO_CARDS="r300 radeon fbdev vesa" --- There is no /etc/X11/xorg.conf file, here is files from /etc/X11/xorg.conf.d/: ---/etc/X11/xorg.conf.d/keyboard.conf--- Section "InputClass" Identifier "keyboard-all" Driver "evdev" Option "XkbLayout" "us,ru" Option "XkbOptions" "grp:ctrl_shift_toggle,terminate:ctrl_alt_bksp,compose:caps" MatchIsKeyboard "on" EndSection --- ---/etc/X11/xorg.conf.d/screen.conf--- Section "Monitor" Identifier "Monitor[0]" # VendorName "NEC" # ModelName "HR17" HorizSync 30-96 VertRefresh 50-160 ModeLine "1024x768_100" 110.00 1024 1072 1168 1376 768 769 772 808 -hsync +vsync EndSection Section "Device" Identifier "Device[0]" Driver "radeon" # Option "NoAccel" "True" EndSection Section "Screen" Identifier "Screen" Monitor "Monitor[0]" Device "Device[0]" DefaultDepth 24 Subsection "Display" Depth 24 Modes "1024x768_100" "1024x768" "800x600" ViewPort 0 0 EndSubsection EndSection ---
Created attachment 332370 [details] kernel config
Created attachment 332372 [details] Xorg.0.log (working ok on xf86-video-ati-6.14.6-r1)
Unless your monitor is one of those with bogus EDID data, neither Screen nor Monitor sections are necessary (well, if it's still CRT, there might be need for Screen to correct/tweak a bit). Anyway, just as the guide says, CONFIG_FB_RADEON must be off. Also, you either need CONFIG_DRM_RADEON=m or the firmware needs to be builtin too.
(In reply to comment #5) > Unless your monitor is one of those with bogus EDID data, neither Screen nor > Monitor sections are necessary (well, if it's still CRT, there might be need > for Screen to correct/tweak a bit). As mentioned in comment in config file, it's NEC HR17 (CRT, ~2001 year). And it require these settings to work at 100Hz. > Anyway, just as the guide says, CONFIG_FB_RADEON must be off. > Also, you either need CONFIG_DRM_RADEON=m or the firmware needs to be > builtin too. Firmware? What firmware for R350? At far as I see, firmware exists for RadeonHD 2000 and newer, my card is much older than that. ... So, why this report was marked INVALID? My system hangs nearly each time when I'm switching it off, which in turn require pressing reset button which isn't good for filesystem. This happens using correct configuration (with CONFIG_FB_RADEON disabled), so what's wrong with this bugreport? Also, that's a different story, but I still wonder how to work around issue with small font while system boot, which happens only when CONFIG_FB_RADEON disabled (i.e. using recommended settings)?
:roll: ls /usr/src/linux/firmware/radeon That radeon-ucode package, which you *might* be referring to, was just for the more recent firmware (which might already be included in the recent enough kernels). This *is* INVALID, cause incorrect configuration is not a bug - at least not one, that could be fixed on this side. 'vga=' obviously *can't* work while CONFIG_FB_RADEON is disabled - it's controlled by 'video=' (with a different syntax). Also, by disabled, I mean 'is not set', not '=m'. Once you load the correct firmware (either by CONFIG_DRM_RADEON=m or including the firmware into kernel), things should work fine (they definitely do on my old r200).
(In reply to comment #7) > ls /usr/src/linux/firmware/radeon > > That radeon-ucode package, which you *might* be referring to, was just for > the more recent firmware (which might already be included in the recent > enough kernels). Thanks a lot, this helps! It may make sense to improve docs to make this needs in standard firmware blobs for old cards more clear - I really had impression firmware needed only for newer cards, because old cards works ok without any firmware before xf86-video-ati-7.0.0. My R350 works ok using R300 firmware.
