You are not logged in.
After updating to 4.1.6-1-ARCH my iptables shut down. System loaded okay but I had zero network access. Tried booting from another arch install (usb) and using arch-chroot and pacman to fix the problem. No avail. Downgrading to 4.1.5-1-ARCH fixed everything without a hassle. Even checked that boot was loaded up correctly; it was.
Was going to file a bug report but (a) guidelines say check the forums first, so here I am. And (b) I don't know if this is a linux kernel issue or an ARCH kernel issue.
is it common for each kernel update to cause somebody some problems? If not, should a bug report go to arch or linux?
Linux XXXXXX 4.1.5-1-ARCH #1 SMP PREEMPT Tue Aug 11 15:41:14 CEST 2015 x86_64 GNU/Linux
Could it have something to do with /boot being mounted properly? On my currently working system:
# ls -l /boot/
total 30496
-rw-r--r-- 1 root root 20960913 Aug 25 18:39 initramfs-linux-fallback.img
-rw-r--r-- 1 root root 6036845 Aug 25 18:39 initramfs-linux.img
-rw-r--r-- 1 root root 4224960 Aug 11 09:42 vmlinuz-linux
# file /boot/vmlinuz-linux
/boot/vmlinuz-linux: Linux kernel x86 boot executable bzImage, version 4.1.5-1-ARCH (builduser@tobias) #1 SMP PREEMPT Tue Aug 11 15:41, RO-rootFS, swap_dev 0x4, Normal VGAOdd given that I just used pacman -U to downgrade to 4.1.5-1-ARCH today, the 25th. Why does the vmlinuz-linux file have a date stamp of 11th?
Probem is that with 4.1.6 iptables just won't load. Filesystem is fine, but I can't connect to anything at all. Network device just doesn't show up at all.
Last edited by Orobouros (2015-08-25 23:10:19)
Offline
Read the new answers in the thread you cross-posted in.
About the date: That's the date the package was built.
Package files are in archives and retain their metadata when extracted; the only exceptions are directories and dynamically created files (via .install scripts).
1000
Offline