Bug#712999: linux-image-3.9-1-amd64: Unable to find LVM volume
Package: initramfs-tools Version: 0.113 Followup-For: Bug #712999 Dear Maintainer, Many thanks for the job you all been doing! Great work! I am writing because I've just upgraded initramfs-tools to 0.113 (jessie) and it regenerated /boot/initrd.img-3.9-1-amd64 but the boot process got stuck in the very same point as 0.112 did. If you need any other info about my system or if you want me to try anything else, please ask! cheers, Gunther -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 11M Oct 16 2012 /boot/initrd.img-3.2.0-3-amd64 -rw-r--r-- 1 root root 11M Jun 16 14:53 /boot/initrd.img-3.2.0-4-amd64 -rw-r--r-- 1 root root 12M Jun 29 06:56 /boot/initrd.img-3.9-1-amd64 -- /proc/cmdline BOOT_IMAGE=/vmlinuz-3.2.0-4-amd64 root=/dev/mapper/shreknemo-root ro quiet -- resume RESUME=/dev/mapper/shreknemo-swap_1 -- /proc/filesystems ext3 fuseblk ext4 -- lsmod Module Size Used by ipheth 12979 0 cryptd 14517 0 aes_x86_64 16843 2 aes_generic33026 1 aes_x86_64 ip6table_filter12540 0 ip6_tables 22175 1 ip6table_filter ebtable_nat12580 0 ebtables 26235 1 ebtable_nat ppdev 12763 0 lp 17149 0 rfcomm 33700 0 bnep 17567 2 bluetooth 119455 10 bnep,rfcomm 8021q 19291 0 garp 13193 1 8021q pci_stub 12429 1 vboxpci19096 0 vboxnetadp 25443 0 vboxnetflt 23608 0 binfmt_misc12957 1 vboxdrv 217144 3 vboxnetflt,vboxnetadp,vboxpci nfsd 216170 2 nfs 308313 0 nfs_acl12511 2 nfs,nfsd auth_rpcgss37143 2 nfs,nfsd fscache36739 1 nfs lockd 67306 2 nfs,nfsd sunrpc173730 6 lockd,auth_rpcgss,nfs_acl,nfs,nfsd xt_TCPMSS 12670 1 xt_limit 12638 8 xt_tcpudp 12570 15 nf_nat_irc 12454 0 nf_nat_ftp 12460 0 ipt_LOG12605 8 ipt_MASQUERADE 12594 1 xt_DSCP12643 0 ipt_REJECT 12502 1 nf_conntrack_irc 12427 1 nf_nat_irc nf_conntrack_ftp 12605 1 nf_nat_ftp xt_state 12503 8 iptable_nat12928 1 nf_nat 18242 4 iptable_nat,ipt_MASQUERADE,nf_nat_ftp,nf_nat_irc nf_conntrack_ipv4 14078 11 nf_nat,iptable_nat nf_defrag_ipv4 12483 1 nf_conntrack_ipv4 nf_conntrack 52720 9 nf_conntrack_ipv4,nf_nat,iptable_nat,xt_state,nf_conntrack_ftp,nf_conntrack_irc,ipt_MASQUERADE,nf_nat_ftp,nf_nat_irc iptable_mangle 12536 0 iptable_filter 12536 1 ip_tables 22042 3 iptable_filter,iptable_mangle,iptable_nat x_tables 19118 15 ip_tables,iptable_filter,iptable_mangle,iptable_nat,xt_state,ipt_REJECT,xt_DSCP,ipt_MASQUERADE,ipt_LOG,xt_tcpudp,xt_limit,xt_TCPMSS,ebtables,ip6_tables,ip6table_filter bridge 70564 0 stp12437 2 bridge,garp ext4 350763 1 crc16 12343 2 ext4,bluetooth jbd2 62115 1 ext4 loop 22641 0 fuse 62020 1 kvm_amd47218 0 kvm 287749 1 kvm_amd nvidia 11239101 50 arc4 12458 2 snd_usb_audio 84836 1 snd_usbmidi_lib23369 1 snd_usb_audio snd_hda_codec_via 41160 1 snd_seq_midi 12848 0 snd_seq_midi_event 13316 1 snd_seq_midi snd_rawmidi23060 2 snd_seq_midi,snd_usbmidi_lib gspca_pac7302 13916 0 carl9170 67916 0 snd_hda_intel 26259 2 ath21370 1 carl9170 mac80211 192806 1 carl9170 snd_hda_codec 78031 2 snd_hda_intel,snd_hda_codec_via i2c_nforce212584 0 gspca_main 22764 1 gspca_pac7302 videodev 70889 1 gspca_main v4l2_compat_ioctl3216655 1 videodev cfg80211 137243 3 mac80211,ath,carl9170 snd_hwdep 13186 2 snd_hda_codec,snd_usb_audio media 18148 1 videodev snd_pcm68083 4 snd_hda_codec,snd_hda_intel,snd_usb_audio i2c_core 23876 3 videodev,i2c_nforce2,nvidia snd_page_alloc 13003 2 snd_pcm,snd_hda_intel powernow_k817618 0 rfkill 19012 5 cfg80211,bluetooth snd_seq45126 2 snd_seq_midi_event,snd_seq_midi snd_seq_device 13176 3 snd_seq,snd_rawmidi,snd_seq_midi snd_timer 22917 2 snd_seq,snd_pcm edac_mce_amd 17103 0 edac_core 35258 0 parport_pc 22364 1 parport31858 3 parport_pc,lp,ppdev snd52889 16 snd_
Bug#614221: iMac-G3 fails to boot with 2.6.37-1-powerpc (Bug#614221)
Em 05.Mar.2011 (sábado), Risto Suominen disse: > I would try video=ofonly. > And you would correct! Just added _ append="video=ofonly" _ to /etc/yaboot.conf, run ybin and rebooted into 2.6.37-2-powerpc which did not complete the booting procces just the way 2.6.37-1-powerpc did. thanks, -- "...agora, só nos sobrou o futuro...", visto em www.manuchao.net Gunther Furtado Curitiba - Paraná - Brasil gunfurt...@gmail.com -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110305161946.57215...@azul.gbcm
Bug#614221: linux-image-2.6.37-1-powerpc: 2.6.37-1-powerpc does not but on iMac G3
2011/2/21 Gunther Furtado : > Hi, > > 2011/2/20 Ben Hutchings : >> On Sun, 2011-02-20 at 10:17 -0300, Gunther Furtado wrote: >>> Package: linux-2.6 >>> Version: 2.6.37-1 >>> Severity: critical >>> Tags: d-i >>> Justification: breaks the whole system >>> >>> Hi, >>> >>> First of all: I cannot run reportbug while running the package I am >>> reporting >>> this bug because I cannot boot from it. >> >> I suspect this is due to my changes to framebuffer driver selection, >> which you obviously noticed. >> >> The problem is that on PowerPC systems we cannot assume hardware support >> for a text mode (as on PCs) and so we must select from the following >> sets of framebuffer drivers: >> 1. Generic drivers using firmware or standard registers >> (FB_OF, FB_VGA16, ...) >> 2. Specific drivers without support for GPU acceleration >> (FB_INTEL, FB_NVIDIA, FB_RADEON, ...) >> 3. Specific drivers with KMS and GEM/TTM >> (DRM_I915, DRM_NOUVEAU, DRM_RADEON) >> >> The type 1 drivers generally allow switching to a different driver for >> the same hardware. But once we have loaded a type 2 or 3 driver there >> is no way to switch without rebooting. >> >> Previously we built-in several type 2 drivers, which meant KMS was not >> possible. However, current X drivers for Intel, Nvidia and AMD/ATI >> hardware require KMS and GEM/TTM so we cannot continue to do this. We >> need to load type 3 drivers, but they are so large that we don't want to >> make them built-in. Also, the AMD/ATI Radeon driver requests firmware >> for 3D acceleration, which is not available at the time built-in drivers >> are initialised. >> >> Therefore, I'm trying to build-in type 1 drivers that cover all PowerPC >> hardware. Apparently that doesn't work. >> >> Do you see any messages from the kernel, or just a blank screen? >> > > Sorry I didn't mention it in my previous message but it seems that > your suspicions are correct: > > The boot messages start to appear until the last to lines that mention > FB and tty1 (i am not close to my box right now but they have very > similar structure to the ones that appear when I successfully boot > 2.6.37-trunk-powerpc). Being precise: --- Console: colour dummy device 80x25 console [tty0] enabled, boot console disable --- those are the last two line I see before rebooting. cheers, -- “Estes aprazíveis pensamentos tornam de tal modo leve o meu trabalho que nunca estou tão ocioso como quando a ele me dedico." Nietzsche citando Shakespeare (e como o Niezsche era muito mentiroso, me resguardo o direito de transferir a culpa) Gunther Furtado Curitiba - Paraná - Brasil gunfurt...@gmail.com -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktingppm3phap5uurjmwjo6kzzwwr46q48_mef...@mail.gmail.com
Bug#614221: linux-image-2.6.37-1-powerpc: 2.6.37-1-powerpc does not but on iMac G3
Hi, 2011/2/20 Ben Hutchings : > On Sun, 2011-02-20 at 10:17 -0300, Gunther Furtado wrote: >> Package: linux-2.6 >> Version: 2.6.37-1 >> Severity: critical >> Tags: d-i >> Justification: breaks the whole system >> >> Hi, >> >> First of all: I cannot run reportbug while running the package I am reporting >> this bug because I cannot boot from it. > > I suspect this is due to my changes to framebuffer driver selection, > which you obviously noticed. > > The problem is that on PowerPC systems we cannot assume hardware support > for a text mode (as on PCs) and so we must select from the following > sets of framebuffer drivers: > 1. Generic drivers using firmware or standard registers > (FB_OF, FB_VGA16, ...) > 2. Specific drivers without support for GPU acceleration > (FB_INTEL, FB_NVIDIA, FB_RADEON, ...) > 3. Specific drivers with KMS and GEM/TTM > (DRM_I915, DRM_NOUVEAU, DRM_RADEON) > > The type 1 drivers generally allow switching to a different driver for > the same hardware. But once we have loaded a type 2 or 3 driver there > is no way to switch without rebooting. > > Previously we built-in several type 2 drivers, which meant KMS was not > possible. However, current X drivers for Intel, Nvidia and AMD/ATI > hardware require KMS and GEM/TTM so we cannot continue to do this. We > need to load type 3 drivers, but they are so large that we don't want to > make them built-in. Also, the AMD/ATI Radeon driver requests firmware > for 3D acceleration, which is not available at the time built-in drivers > are initialised. > > Therefore, I'm trying to build-in type 1 drivers that cover all PowerPC > hardware. Apparently that doesn't work. > > Do you see any messages from the kernel, or just a blank screen? > Sorry I didn't mention it in my previous message but it seems that your suspicions are correct: The boot messages start to appear until the last to lines that mention FB and tty1 (i am not close to my box right now but they have very similar structure to the ones that appear when I successfully boot 2.6.37-trunk-powerpc). What happens next is complete silence for about two or tree minutes and then the machine reboots for itself. cheers, > Ben. > > -- > Ben Hutchings > Once a job is fouled up, anything done to improve it makes it worse. > -- “Estes aprazíveis pensamentos tornam de tal modo leve o meu trabalho que nunca estou tão ocioso como quando a ele me dedico." Shakespeare Gunther Furtado Curitiba - Paraná - Brasil gunfurt...@gmail.com -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/AANLkTi=+7Fv-JkojayWfKÁxzk2khnindh-k_b-i...@mail.gmail.com
Bug#614221: linux-image-2.6.37-1-powerpc: 2.6.37-1-powerpc does not but on iMac G3
Package: linux-2.6 Version: 2.6.37-1 Severity: critical Tags: d-i Justification: breaks the whole system Hi, First of all: I cannot run reportbug while running the package I am reporting this bug because I cannot boot from it. I've been running 2.6.37-trunk-powerpc for a while now without any problems. But whe aptitude told me it became obsolete and install 2.6.37-1-powerpc my machine (output of report-hw is at the bottom of the message) I am sending you a diff detween the two config files. Please let me know what other info do you need. azul:~#diff /boot/config-2.6.37-trunk-powerpc /boot/config-2.6.37-1-powerpc 4c4 < # Thu Jan 6 13:32:54 2011 --- > # Tue Feb 15 17:04:16 2011 2346c2346 < CONFIG_I2C_ALGOBIT=y --- > CONFIG_I2C_ALGOBIT=m 3150,3151c3150,3151 < CONFIG_FB_DDC=y < CONFIG_FB_BOOT_VESA_SUPPORT=y --- > CONFIG_FB_DDC=m > # CONFIG_FB_BOOT_VESA_SUPPORT is not set 3178c3178 < CONFIG_FB_CT65550=y --- > # CONFIG_FB_CT65550 is not set 3181c3181 < # CONFIG_FB_VGA16 is not set --- > CONFIG_FB_VGA16=y 3184c3184 < CONFIG_FB_NVIDIA=y --- > CONFIG_FB_NVIDIA=m 3189c3189 < CONFIG_FB_MATROX=y --- > CONFIG_FB_MATROX=m 3195c3195 < CONFIG_FB_RADEON=y --- > CONFIG_FB_RADEON=m 3199c3199 < CONFIG_FB_ATY128=y --- > CONFIG_FB_ATY128=m 3201c3201 < CONFIG_FB_ATY=y --- > CONFIG_FB_ATY=m 3210c3210 < CONFIG_FB_SIS=y --- > CONFIG_FB_SIS=m 3215c3215 < CONFIG_FB_3DFX=y --- > CONFIG_FB_3DFX=m 4011c4011,4012 < # CONFIG_FANOTIFY is not set --- > CONFIG_FANOTIFY=y > # CONFIG_FANOTIFY_ACCESS_PERMISSIONS is not set 4101a4103,4118 > CONFIG_AUFS_FS=m > CONFIG_AUFS_BRANCH_MAX_127=y > # CONFIG_AUFS_BRANCH_MAX_511 is not set > # CONFIG_AUFS_BRANCH_MAX_1023 is not set > # CONFIG_AUFS_BRANCH_MAX_32767 is not set > CONFIG_AUFS_SBILIST=y > # CONFIG_AUFS_HNOTIFY is not set > # CONFIG_AUFS_EXPORT is not set > # CONFIG_AUFS_RDU is not set > # CONFIG_AUFS_SP_IATTR is not set > # CONFIG_AUFS_SHWH is not set > # CONFIG_AUFS_BR_RAMFS is not set > # CONFIG_AUFS_BR_FUSE is not set > CONFIG_AUFS_BR_HFSPLUS=y > CONFIG_AUFS_BDEV_LOOP=y > # CONFIG_AUFS_DEBUG is not set 4135,4136c4152,4153 < # CONFIG_CIFS_FSCACHE is not set < # CONFIG_CIFS_ACL is not set --- > CONFIG_CIFS_FSCACHE=y > CONFIG_CIFS_ACL=y --- azul$ report-hw uname -a: Linux azul 2.6.37-trunk-powerpc #1 Thu Jan 6 15:21:31 UTC 2011 ppc GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Motorola MPC106 [Grackle] [1057:0002] (rev 40) lspci -knn: 00:10.0 Unassigned class [ff00]: Apple Computer Inc. Paddington Mac I/O [106b:0017] lspci -knn: Kernel driver in use: macio lspci -knn: 00:12.0 VGA compatible controller [0300]: ATI Technologies Inc 3D Rage Pro 215GP [1002:4750] (rev 5c) lspci -knn: Kernel driver in use: atyfb lspci -knn: 00:14.0 USB Controller [0c03]: Agere Systems USB [11c1:5801] (rev 12) lspci -knn: Subsystem: Agere Systems USB [11c1:5801] lspci -knn: Kernel driver in use: ohci_hcd usb-devices: usb-devices: T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 usb-devices: D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 usb-devices: P: Vendor=1d6b ProdID=0001 Rev=02.06 usb-devices: S: Manufacturer=Linux 2.6.37-trunk-powerpc ohci_hcd usb-devices: S: Product=OHCI Host Controller usb-devices: S: SerialNumber=:00:14.0 usb-devices: C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA usb-devices: I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub usb-devices: usb-devices: T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 usb-devices: D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1 usb-devices: P: Vendor=0cf3 ProdID=9170 Rev=01.06 usb-devices: S: Manufacturer=ATHER usb-devices: S: Product=USB2.0 WLAN usb-devices: S: SerialNumber=12345 usb-devices: C: #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA usb-devices: I: If#= 0 Alt= 0 #EPs= 4 Cls=ff(vend.) Sub=00 Prot=00 Driver=ar9170usb usb-devices: usb-devices: T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 3 Spd=12 MxCh= 4 usb-devices: D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 usb-devices: P: Vendor=05e3 ProdID=0604 Rev=03.05 usb-devices: S: Product=USB Hub usb-devices: C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mA usb-devices: I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub usb-devices: usb-devices: T: Bus=01 Lev=02 Prnt=03 Port=00 Cnt=01 Dev#= 4 Spd=1.5 MxCh= 0 usb-devices: D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 usb-devices: P: Vendor=04f3 ProdID=0230 Rev=24.58 usb-devices: S: Product=USB+PS/2 Optical Mouse usb-devices: C: #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA usb-devices: I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=usbhid usb-devices: usb-devices: T: Bus=01 Lev=02 Prnt=03 Port=01 Cnt=02 Dev#= 5 Spd=1.5 MxCh= 0 usb-devices: D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 usb-devices: P: Vendor=1241 ProdID=0022 Rev=03.90 usb-devices: S: Manufacturer=Chicony usb-devices: S: Product=USB Keyboard usb-devices: C: #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=100mA usb-devices: I: If#= 0 Alt= 0 #EPs
Bug#433127: system unbootable after update to linux-image-2.6.21-2
Hi, I am writing to say the same thing happens to me when I upgrade to 2.6.22-2-k7 and I didn't wnat to open a new bugreport. The workaround worked just fine for me. cheers, -- Gunther Furtado [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
