Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#26821 - with kernel linux-3.1-4 system not detects hardware

Attached to Project: Arch Linux
Opened by gymka (gymka) - Wednesday, 09 November 2011, 16:58 GMT
Last edited by Thomas Bächler (brain0) - Wednesday, 09 November 2011, 21:49 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Thomas Bächler (brain0)
Architecture x86_64
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
ok updated kernel to version 3.1-4, first thing which i noticed: if i connect usb flash, system not detects it, even "fdisk -l" don't shows it. later i restarted, new updates, so maybe it's need to be reloaded. after restart problems started:
at system boot i can see error "no sound card detected"(or similar) everything else looks good. then starts gdm keyboard and mouse is ignored, i can press any button on keyboard and there is no reaction, same with mouse. so i can't login.(system not hanged, because clock still goes)
booted live cd, disabled gdm:
i can login, keyboard works, network not works.

Additional info:
* tried to downgrade udev(as i understand detect hardware is udev's work)
* tried to reinstall gdm
* only thing which helped was kernel("linux" and "linux-headers" packages) downgrade to 3.0.7
* gdm 3.2.1.1-1
* udev 175-1

Steps to reproduce:
install linux-3.1-4 and linux-headers-3.1-4, start archlinux with gdm
This task depends upon

Closed by  Thomas Bächler (brain0)
Wednesday, 09 November 2011, 21:49 GMT
Reason for closing:  Not a bug
Additional comments about closing:  This is a bugtracker, not a helpdesk for misconfigured systems.
Comment by Jan de Groot (JGC) - Wednesday, 09 November 2011, 17:05 GMT
Because of recent changes to the linux kernel package, you'll have to reboot after a kernel update, modules from the current version will not load with a running older version. This is a regression compared to the old kernel where minor version updates didn't change the module directory name, but given the fact that many kernel panics and oopses are caused by loading modules from a different kernel, I don't think this is a very important regression at all.

As for your other issues after rebooting: please attach outputs of dmesg and /var/log/Xorg.0.log, we can't do anything without that information.
Comment by gymka (gymka) - Wednesday, 09 November 2011, 17:13 GMT
eg. /var/log/messages.log and /var/log/kernel.log don't have that part of log then i had problems... there is "Nov 9 16:43" and later "Nov 9 18:44" there is no logs from that time while i tried to fix the problem
   Xorg.0.log (122.7 KiB)
   dmesg.txt (44.4 KiB)
Comment by Thomas Bächler (brain0) - Wednesday, 09 November 2011, 17:20 GMT
Is this dmesg.txt from a failed attempt or a working one? Because it does recognize the USB drive.

I suspect that you upgraded to 3.1-4, yet you still boot 3.0.7. This cannot work, and it is not a bug. Your /boot partition was not mounted during the update, which is due to a broken fstab file. Refer to google or the Arch forums for help.
Comment by gymka (gymka) - Wednesday, 09 November 2011, 17:42 GMT
that dmesg.txt is from system with downgraded kernel, this(which attached) is then i booted with kernel 3.1.4 before gdm launch.
how my could be not mounted? if boot to OS, so it must be mounted. i have separate /boot partition if this matters.
my boot is mounted, i tried to mount /boot, i get error that is already mounted or busy, then i installed kernel 3.1.4
   dmesg.txt (44.4 KiB)
Comment by Jan de Groot (JGC) - Wednesday, 09 November 2011, 17:55 GMT
The attached dmesg.txt is from 3.0, not 3.1
Comment by gymka (gymka) - Wednesday, 09 November 2011, 17:59 GMT
attached file is after 3.1 install, maybe 3.0 is booted. 3.1 and 3.0 have same filenames "/boot/initramfs-linux.img" and "/boot/vmlinuz-linux", maybe settings is for 3.1 and these files is not updated...
Comment by Ionut Biru (wonder) - Wednesday, 09 November 2011, 18:02 GMT
pretty much your /boot is not mounted when upgrading to 3.1, or your bootloader configuration is busted.
Comment by Jan de Groot (JGC) - Wednesday, 09 November 2011, 18:18 GMT
Can you attach /etc/fstab and the output of the "mount" command?

Loading...