Re: [arch-general] Kernel 3.13
On 01/26/2014 02:17 PM, Dave wrote: Jonathan Hudson jh+a...@daria.co.uk wrote: When you upgrade to kernel 3.13, pacman considerately informs you that you must have a keyboard hook in mkinitcpio.conf. What you're not told is that if you have an AT keyboard, you also need to ensure that the atkbd module is loaded, otherwise you probably won't have a working keyboard on reboot. -jh Do you subscribe to arch-dev-public? It's under discussion there and saved me. Yes, and I am still unclear what is required to insure that an appropriate module is loaded for a normal laptop/desktop. I already include 'keyboard' in HOOKS -- is that all that is needed or are there additional specific modules that need to be probed? Does HOOKS=.. keyboard.. insure the atkbd module will be loaded/probed? I vote for a solution that insures a keyboard is always probed/detected/provided if one exists whether that is shipping a modules-load.d fragment or leaving it built-in. From the discussion, a manual probing seems like a bad answer. -- David C. Rankin, J.D.,P.E.
Re: [arch-general] Kernel 3.13
Am 28.01.2014 09:07, schrieb David C. Rankin: Yes, and I am still unclear what is required to insure that an appropriate module is loaded for a normal laptop/desktop. Nothing. The keyboard should simply. I already include 'keyboard' in HOOKS This is only required if you want to use the keyboard in early userspace, which 90% of the time, you don't even have to (encrypted root is one popular exception, handling a failsafe shell is another). The 'keyboard' hook has been in the defaullt configuration for a a while now. I vote for a solution that insures a keyboard is always probed/detected/provided If your keyboard doesn't work out of the box with 3.13-2, please add a comment to the appropriate bug report [1] (that is for everyone - comment on that bug if you have keyboard problems with 3.13-2). Everything else is just a waste of time. [1] https://bugs.archlinux.org/task/38671 signature.asc Description: OpenPGP digital signature
Re: [arch-general] Kernel 3.13
have been using [testing] for a couple of years now and this is the first time i'm getting in trouble which i don't understand. i don't use a PS2 keyboard and was encouraged from others' positive reports with 3.13, so i upgraded. unfortunately this doesn't work with me, apparently because of my bios / graphics card and i received a bunch of repeating errors during boot (pasted below). i haven't seen this type of thing before and am not sure if this is bug report material or lack of understanding on my part -- and if bug report, against what, exactly? first here's my system (inxi -b): System:Host: phani Kernel: 3.12.8-1-ARCH x86_64 (64 bit) Desktop: Awesome 3.5.2 Distro: Arch Linux Machine: Mobo: ASUSTeK model: K53SK version: 1.0 Bios: American Megatrends version: K53SK.203 date: 10/11/2011 CPU: Quad core Intel Core i7-2670QM CPU (-HT-MCP-) clocked at 1178.289 MHz Graphics: Card-1: Intel 2nd Generation Core Processor Family Integrated Graphics Controller Card-2: Advanced Micro Devices [AMD/ATI] Whistler LE [Radeon HD 6610M/7610M] X.Org: 1.15.0 driver: intel Resolution: 1366x768@60.0hz, 1920x1080@60.0hz GLX Renderer: Mesa DRI Intel Sandybridge Mobile GLX Version: 3.0 Mesa 10.0.2 Network: Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8168 Card-2: Intel Centrino Wireless-N 100 driver: iwlwifi Drives:HDD Total Size: 750.2GB (42.2% used) Info: Processes: 252 Uptime: 21 min Memory: 1598.1/5876.2MB Client: Shell (bash) inxi: 1.9.18 and then there's the errors, during two separate boots. once with acpi_call-git installed, once without: Jan 28 01:52:38 phani kernel: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting Jan 28 01:52:38 phani kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CEDE (len 62, WS 0, PS 0) @ 0xCEFA Jan 28 01:52:38 phani kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing BBDE (len 1036, WS 4, PS 0) @ 0xBCDB Jan 28 01:52:38 phani kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing BB74 (len 76, WS 0, PS 8) @ 0xBB7C Jan 28 01:52:38 phani kernel: [drm] PCIE gen 2 link speeds already enabled Jan 28 01:52:39 phani kernel: radeon :01:00.0: Wait for MC idle timedout ! Jan 28 01:52:39 phani kernel: radeon :01:00.0: Wait for MC idle timedout ! Jan 28 01:52:39 phani kernel: [drm] PCIE GART of 1024M enabled (table at 0x00273000). Jan 28 01:52:39 phani kernel: radeon :01:00.0: WB enabled Jan 28 01:52:39 phani kernel: radeon :01:00.0: fence driver on ring 0 use gpu addr 0x8c00 and cpu addr 0x8800a3148c00 Jan 28 01:52:39 phani kernel: radeon :01:00.0: fence driver on ring 3 use gpu addr 0x8c0c and cpu addr 0x8800a3148c0c Jan 28 01:52:39 phani kernel: radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00072118 and cpu addr 0xc90017632118 Jan 28 01:52:39 phani kernel: [drm:r600_ring_test] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0x) Jan 28 01:52:39 phani kernel: [drm:evergreen_resume] *ERROR* evergreen startup failed on resume Jan 28 01:52:39 phani kernel: [drm:radeon_pm_resume_dpm] *ERROR* radeon: dpm resume failed Jan 28 01:52:44 phani kernel: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting Jan 28 01:52:44 phani kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing C588 (len 1136, WS 0, PS 0) @ 0xC5B2 Jan 28 01:52:49 phani kernel: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting Jan 28 01:52:49 phani kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CEDE (len 62, WS 0, PS 0) @ 0xCEFA Jan 28 01:52:54 phani kernel: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting Jan 28 01:52:54 phani kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CEDE (len 62, WS 0, PS 0) @ 0xCEFA Jan 28 01:52:56 phani kdm[1076]: X server startup timeout, terminating Jan 28 01:52:59 phani kernel: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting Jan 28 01:52:59 phani kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CEDE (len 62, WS 0, PS 0) @ 0xCEFA Jan 28 01:53:04 phani kernel: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting Jan 28 01:53:04 phani kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CEDE (len 62, WS 0, PS 0) @ 0xCEFA Jan 28 01:53:09 phani kernel: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting Jan 28 01:53:09 phani kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CEDE (len 62, WS 0, PS 0) @ 0xCEFA Jan 28 01:53:14 phani kernel: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting Jan 28
Re: [arch-general] Kernel 3.13
i haven't seen this type of thing before and am not sure if this is bug report material or lack of understanding on my part -- and if bug report, against what, exactly? Try disabling Radeon DPM with kernel switch. I don't remember the exact name, but it's probably something like radeon.dpm=0. I have recently read on the channel that DPM is enabled by default as of 3.13. If it's not DPM to blame I suggest to ask the guys on #radeon directly. -- Kind regards, Damian Nowak StratusHost www.AtlasHost.eu
Re: [arch-general] Kernel 3.13
On 27/01/2014 21:07, phanisvara wrote: (..) Jan 28 01:58:33 phani kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CEDE (len 62, WS 0, PS 0) @ 0xCEFA (...) Have a look at https://bugs.freedesktop.org and search for your bug in the DRI section. If you find none, report it with full dmesg log. -- Timothée Ravier
Re: [arch-general] Kernel 3.13
On Monday 27 Jan 2014 22:31:36 Nowaker wrote: i haven't seen this type of thing before and am not sure if this is bug report material or lack of understanding on my part -- and if bug report, against what, exactly? Try disabling Radeon DPM with kernel switch. I don't remember the exact name, but it's probably something like radeon.dpm=0. I have recently read on the channel that DPM is enabled by default as of 3.13. If it's not DPM to blame I suggest to ask the guys on #radeon directly. thanks a lot, disabling DPM with radeon.dpm=0 as kernel param. workded fine. i then remembered that i had some custom config. in /etc/X11/xorg.conf.d/ which had proven useful earlier. after removing both, 20-radeon.conf 20-intel.conf from that directory, everything starts fine w/o the no-DPM parameter. seems with the new kernel, these tweaks aren't needed anymore :) -- phani.
Re: [arch-general] Kernel 3.13
On Monday 27 Jan 2014 22:40:18 Timothée Ravier wrote: On 27/01/2014 21:07, phanisvara wrote: (..) Jan 28 01:58:33 phani kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CEDE (len 62, WS 0, PS 0) @ 0xCEFA (...) Have a look at https://bugs.freedesktop.org and search for your bug in the DRI section. If you find none, report it with full dmesg log. thanks, i would have done that if i hadn't found that this wasn't a bug but my own mistake. i had some weird radeon configuration in xorg.conf.d which aren't needed, or even working anymore. -- phani.
[arch-general] Kernel 3.13
When you upgrade to kernel 3.13, pacman considerately informs you that you must have a keyboard hook in mkinitcpio.conf. What you're not told is that if you have an AT keyboard, you also need to ensure that the atkbd module is loaded, otherwise you probably won't have a working keyboard on reboot. -jh
Re: [arch-general] Kernel 3.13
Jonathan Hudson jh+a...@daria.co.uk wrote: When you upgrade to kernel 3.13, pacman considerately informs you that you must have a keyboard hook in mkinitcpio.conf. What you're not told is that if you have an AT keyboard, you also need to ensure that the atkbd module is loaded, otherwise you probably won't have a working keyboard on reboot. -jh Do you subscribe to arch-dev-public? It's under discussion there and saved me. -- Dave GPG/PGP ID: CDB94DA1
Re: [arch-general] Kernel 3.13
On Sun, Jan 26, 2014 at 9:01 PM, Jonathan Hudson jh+a...@daria.co.uk wrote: When you upgrade to kernel 3.13, pacman considerately informs you that you must have a keyboard hook in mkinitcpio.conf. What you're not told is that if you have an AT keyboard, you also need to ensure that the atkbd module is loaded, otherwise you probably won't have a working keyboard on reboot. -jh linux 3.13-1 is in [testing] and if you use [testing] repos you should subscribe to arch-dev-public ML: https://mailman.archlinux.org/pipermail/arch-dev-public/2014-January/025830.html
Re: [arch-general] Kernel 3.13
On Sun, 26 Jan 2014 20:17:13 +, Dave wrote: Jonathan Hudson jh+a...@daria.co.uk wrote: When you upgrade to kernel 3.13, pacman considerately informs you that you must have a keyboard hook in mkinitcpio.conf. What you're not told is that if you have an AT keyboard, you also need to ensure that the atkbd module is loaded, otherwise you probably won't have a working keyboard on reboot. -jh Do you subscribe to arch-dev-public? It's under discussion there and saved me. -- Dave GPG/PGP ID: CDB94DA1 Thanks for the clue. -jh
