Bug#509244: marked as done (debian-installer: Configure clock ignores my chosen country)
Your message dated Sat, 20 Dec 2008 20:22:35 +1100 with message-id 1229764955.8446.1.ca...@antec.timtris.org and subject line Closed has caused the Debian Bug report #509244, regarding debian-installer: Configure clock ignores my chosen country to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 509244: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=509244 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: debian-installer Version: 20081220 Severity: normal I'm using the business card nightly lenny install downloaded 20081220. After entering Australia as my region, I am only presented with US timezones for Configure the Clock -- System Information: Debian Release: 5.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash ---End Message--- ---BeginMessage--- Sorry, I must have made a mistake. I interrupted and repeated the install, and could not reproduce this report. ---End Message---
Bug#509244: debian-installer: Configure clock ignores my chosen country
Package: debian-installer Version: 20081220 Severity: normal I'm using the business card nightly lenny install downloaded 20081220. After entering Australia as my region, I am only presented with US timezones for Configure the Clock -- System Information: Debian Release: 5.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509178: installation-reports: sparc fails to boot 2.6.26: Memory Address not Aligned
Hi, This might be the same bug as #509202. I'll try to setup cu or minicom to collect kernel messages on tuesday, while I am at the university again. FWIW, the boot fails in the same way with http://cdimage.debian.org/cdimage/lenny_di_rc1/sparc/iso-cd/debian-testing-sparc-netinst.iso , built on 20081104-23:58 : Allocated 8 Megs of memory at 0x4000 for kernel Loaded kernel version 2.6.26 Loading initial ramdisk (4284688 bytes at Memory Address not Aligned I'll try to get it to boot with the latest etch kernel on tuesday. Thanks, Bye, Joost -- Joost van Baalhttp://abramowitz.uvt.nl/ Tilburg University mailto:joostvb.uvt.nl The Netherlands signature.asc Description: Digital signature
Bug#509290: Package: installation-reports
Package: installation-reports Boot method: DVD from ISO image from jigdo server. Image version: http://debian.lcs.mit.edu/debian/debian-40r5-i386-DVD-1.jigdo Date: 12/15/08 10:00PM Machine: Intel P45 Express Chipset Processor: Intel core2 Quad Q6700 2.66ghz Memory: Corsair XMS3 2GB PC3-10666 Partitions: default scenario Output of lspci -nn and lspci -vnn: ? Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[E] Configure network: [E] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [E] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: Everything seemed to work until I got to the network setup. My two network adapters were not detected at all. I could not continue with the network setup. Then, I went on to partition the disks, using the default whole disk scenario, the partition creation process would always freeze at 33%. This was the case in numerous installation attempts. I could not complete the rest of the installation. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509290: Package: installation-reports
George Pinto gmpin...@gmail.com writes: Image version: http://debian.lcs.mit.edu/debian/debian-40r5-i386-DVD-1.jigdo Machine: Intel P45 Express Chipset Processor: Intel core2 Quad Q6700 2.66ghz Memory: Corsair XMS3 2GB PC3-10666 Partitions: default scenario Output of lspci -nn and lspci -vnn: ? Either select spawning a shell from the installer menu or switch to another virtual console (Alt+F2) and issue these commands there. Comments/Problems: Everything seemed to work until I got to the network setup. My two network adapters were not detected at all. [...] You'd probably have better chance with the Lenny installer on recent hardware. Is there any special reason you can't use that? http://www.debian.org/devel/debian-installer/ -- Cheers, Feri. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509238: panic backtrace
First of all, it would be nice if you could precise what exact version you tested. I tried both the rc1 debian-testing-i386-netinst.iso and the daily build as of a few days ago. Same result. The version we would like to see tested at this moment is: - RC1, which you can download from: hd-media image=A0: http://ftp.nl.debian.org/debian/dists/testing/main/installer-i386/current/i= mages/hd-media/ netinst ISO: http://cdimage.debian.org/cdimage/lenny_di_rc1/i386/iso-cd/debian-testing-i= 386-netinst.iso - Daily builds: hd-media: http://people.debian.org/~joeyh/d-i/images/daily/hd-media/ netinst ISO: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-c= d/debian-testing-i386-netinst.iso Ok, I downloaded these 4 again. It turns out that the daily build iso was the exact same I had tried last. The boot.imb.gz was different so I re-made the usb stick disk with the one in the daily build link above and the daily build iso. So the backtrace below applies to the daily builds above. Then we could probably narrow the problem by using the expert modewhich will interrupt some steps more often and make the exact moment the problem happens more easy to spot. Actually, I was able to capture the problem in non-expert mode. I figure the least amount of changes made in the flow of execution of the program, the easier it would be to duplicate the problem. I chose the defaults in the language selection, locale, etc... Also, when you've spotted the moment where the installer hangs, please retry the installation and, just before the hang happens, try switching to console 4 (Alt+F4) and look at what's displayed there... Ok, it happens immediately after the identifying network hardware screen. So soon after in fact that I thought I would have no time to swtich to console 4, but quick fingers did it and quite a bit scrolled off the screen, ending in this: [ 23.523397] EAX: EBX: df6f ECX: EDX: df413440 [ 23.523397] ESI: df6f EDI: EBP: ESP: df449f84 [ 23.523397] DS: 007b ES: 007b FS: GS: SS: 0068 [ 23.523397] Process events/0 (pid: 5, ti=df448000 task=df43e860 task.ti=df448000) [ 23.523397] Stack: c025d42d df6f 0002 c025830e df413440 c0356f00 c025833e [ 23.523397]c025835b c012716d df413440 c01276e9 df413448 c0127794 df43e860 [ 23.523397]c012990b df449fc8 df449fc8 df413440 c0129763 c012972d [ 23.523397] Call Trace: [ 23.523397] [c025d42d] dev_deactivate+0x1e/0xbd [ 23.523397] [c025830e] __linkwatch_run_queue+0x118/0x148 [ 23.523397] [c025833e] linkwatch_event+0x0/0x22 [ 23.523397] [c025835b] linkwatch_event+0x1d/0x22 [ 23.523397] [c012716d] run_workqueue+0x75/0xee [ 23.523397] [c01276e9] worker_thread+0x0/0xb5 [ 23.523397] [c0127794] worker_thread+0xab/0xb5 [ 23.523397] [c012990b] autoremove_wake_function=0x0/0x2d [ 23.523397] [c0129763] kthread+0x36/0x5b [ 23.523397] [c012972d] kthread+0x0/0x5b [ 23.523397] [c0104937] kernel_thread_helper+0x7/0x10 [ 23.523397] === [ 23.523397] Code: ff 42 50 5b c3 89 c1 8d 90 80 00 00 00 89 12 8d 81 a4 00 00 00 89 52 04 c7 42 08 00 00 00 00 83 c2 0c 39 c2 75 e7 31 c0 c3 89 c1 8b 40 10 8b 50 30 85 d2 74 04 89 c8 ff d2 c3 53 89 c3 e8 a8 af [ 23.523397] EIP: [c025d074] qdisc_reset+0x2/0x11 SS:ESP 0068:df449f84 [ 23.915430] Kernel panic - not syncing: Fatall exception in interrupt Of course, the machine is now totally frozen, so no scrolling back. Any other tests? Let me know. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reassign 509299 to win32-loader
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35 reassign 509299 win32-loader Bug#509299: installation: Error in Windows-Based Debial Installation Warning: Unknown package 'installation' Bug reassigned from package `installation' to `win32-loader'. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reassign 509303 to win32-loader
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35 reassign 509303 win32-loader Bug#509303: installation: Debian Install Should have Restart Points Warning: Unknown package 'installation' Bug reassigned from package `installation' to `win32-loader'. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reassign 509303 to installation-reports
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35 reassign 509303 installation-reports Bug#509303: installation: Debian Install Should have Restart Points Bug reassigned from package `win32-loader' to `installation-reports'. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509314: Lenny installer RC1
Package: installation-reports Boot method: How did you boot the installer? CD? floppy? network? CD Image version: Full URL to image you downloaded is best any Date: Date and time of the install December 13, 2008 Machine: Description of machine (eg, IBM Thinkpad R32) custom older AMD64 machine Processor: AMD Athlon 64 Memory: 1G Partitions: df -Tl will do; the raw partition table is preferred never got that far Output of lspci -knn (or lspci -nn): Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [E] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: I've downloaded the .iso image twice and burned it 3 times using two different machines. I get the same problem each time. The boot CD is not recognized and the machine tries to boot from the hard disk. I booted the system from an Ubuntu 8,10 disk and just finished install Etch+1/2 on it so there is nothing wrong with the machine. The notes on the Etch+1/2 install indicate it's using the Lenny RC1 installer so I suspect it's not a problem with the installer either. It may be the .iso image simply doesn't have the boot code on it. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509315: Lenny installer RC1
Package: installation-reports Boot method: How did you boot the installer? CD? floppy? network? CD Image version: Full URL to image you downloaded is best AMD64 netinst Date: Date and time of the install December 13, 2008 Machine: Description of machine (eg, IBM Thinkpad R32) custom older AMD64 machine Processor: AMD Athlon 64 Memory: 1G Partitions: df -Tl will do; the raw partition table is preferred never got that far Output of lspci -knn (or lspci -nn): Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [E] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: I've downloaded the .iso image twice and burned it 3 times using two different machines. I get the same problem each time. The boot CD is not recognized and the machine tries to boot from the hard disk. I booted the system from an Ubuntu 8,10 disk and just finished install Etch+1/2 on it so there is nothing wrong with the machine. The notes on the Etch+1/2 install indicate it's using the Lenny RC1 installer so I suspect it's not a problem with the installer either. It may be the .iso image simply doesn't have the boot code on it. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509291: Lenovo SL500, Debian lenny installation report
Quoting Joey Hess (jo...@debian.org): In tasksel, I was suprised to see it did not select the laptop task. This turns out to be due to this in the logs. Some read error from the iso on the USB key (which had successfully installed another machine), which caused laptop-detect to fail to install, w/o indicating it to the user. From what I read in scripts, laptop-detect is simply installed in pre-pkgsel.d, with apt-install laptop-detect. From my understanding, if that fails, the user will be notified.so, the only explanation I see is that laptop-detect postinst exited normally even though the package wasn't installed properly. Is this the correct interpretation? signature.asc Description: Digital signature
Bug#509291: Lenovo SL500, Debian lenny installation report
Christian Perrier wrote: Quoting Joey Hess (jo...@debian.org): In tasksel, I was suprised to see it did not select the laptop task. This turns out to be due to this in the logs. Some read error from the iso on the USB key (which had successfully installed another machine), which caused laptop-detect to fail to install, w/o indicating it to the user. From what I read in scripts, laptop-detect is simply installed in pre-pkgsel.d, with apt-install laptop-detect. From my understanding, if that fails, the user will be notified.so, the only explanation I see is that laptop-detect postinst exited normally even though the package wasn't installed properly. Is this the correct interpretation? From what I can see in the log, the deb could not be copied from the usb stick at all, so its postinst never got a chance to run. Dpkg and apt should, AFAIK, exit nonzero in that situation. -- see shy jo signature.asc Description: Digital signature
Bug#509238: panic backtrace
Quoting The Eclectic One (eclec...@sdf.lonestar.org): First of all, it would be nice if you could precise what exact version you tested. I tried both the rc1 debian-testing-i386-netinst.iso and the daily build as of a few days ago. Same result. OK. Are you in the position of testing with something else than a USB stick boot ? The best would be using the netboot ISO (called mini.iso) from a CD. Ok, I downloaded these 4 again. It turns out that the daily build iso was the exact same I had tried last. The boot.imb.gz was different so Yes, daily builds have not been rebuilt since Dec 18th. Though this is not the source of your problems, we might prefer really testing with the version we will release. Actually, I was able to capture the problem in non-expert mode. I figure the least amount of changes made in the flow of execution of the program, the easier it would be to duplicate the problem. There are no changes in the flow of execution, but more places where the process is stopped, which might help narrowing things down. Ok, it happens immediately after the identifying network hardware screen. So soon after in fact that I thought I would have no time to after identifying network HW means 'after the system displays a progress bar saying Identifying network hardware, right? This is where we would need to really narrow things down and where using the expert mode could help. [ 23.523397] EAX: EBX: df6f ECX: EDX: df413440 [ 23.523397] ESI: df6f EDI: EBP: ESP: df449f84 [ 23.523397] DS: 007b ES: 007b FS: GS: SS: 0068 [ 23.523397] Process events/0 (pid: 5, ti=df448000 task=df43e860 task.ti=df448000) [ 23.523397] Stack: c025d42d df6f 0002 c025830e df413440 c0356f00 c025833e [ 23.523397]c025835b c012716d df413440 c01276e9 df413448 c0127794 df43e860 [ 23.523397]c012990b df449fc8 df449fc8 df413440 c0129763 c012972d [ 23.523397] Call Trace: [ 23.523397] [c025d42d] dev_deactivate+0x1e/0xbd [ 23.523397] [c025830e] __linkwatch_run_queue+0x118/0x148 [ 23.523397] [c025833e] linkwatch_event+0x0/0x22 [ 23.523397] [c025835b] linkwatch_event+0x1d/0x22 [ 23.523397] [c012716d] run_workqueue+0x75/0xee [ 23.523397] [c01276e9] worker_thread+0x0/0xb5 [ 23.523397] [c0127794] worker_thread+0xab/0xb5 [ 23.523397] [c012990b] autoremove_wake_function=0x0/0x2d [ 23.523397] [c0129763] kthread+0x36/0x5b [ 23.523397] [c012972d] kthread+0x0/0x5b [ 23.523397] [c0104937] kernel_thread_helper+0x7/0x10 [ 23.523397] === [ 23.523397] Code: ff 42 50 5b c3 89 c1 8d 90 80 00 00 00 89 12 8d 81 a4 00 00 00 89 52 04 c7 42 08 00 00 00 00 83 c2 0c 39 c2 75 e7 31 c0 c3 89 c1 8b 40 10 8b 50 30 85 d2 74 04 89 c8 ff d2 c3 53 89 c3 e8 a8 af [ 23.523397] EIP: [c025d074] qdisc_reset+0x2/0x11 SS:ESP 0068:df449f84 [ 23.915430] Kernel panic - not syncing: Fatall exception in interrupt OK. Thanks for the help trying to narrow things. Being an obvious problem with the kernel, we really need to triple check that it happens or not with the last kernel package from unstable (which is likely, but still...) signature.asc Description: Digital signature
Bug#509291: Lenovo SL500, Debian lenny installation report
Quoting Joey Hess (jo...@debian.org): From what I can see in the log, the deb could not be copied from the usb stick at all, so its postinst never got a chance to run. Dpkg and apt should, AFAIK, exit nonzero in that situation. Hmmm, apt-install is basically doing apt-get install $packages (in the chroot and inside debconf-apt-progress). So, that would mean that apt does not fail when it can't read a file. It's very surprising that it doesn't, indeedbut, then that would mean the bug is to reassign to apt. Any chance that you can manually debug this further (by running apt manually or so)? -- signature.asc Description: Digital signature
Bug#509314: Lenny installer RC1
Quoting Gary Dale (garyd...@rogers.com): Comments/Problems: I've downloaded the .iso image twice and burned it 3 times using two different machines. I get the same problem each time. The boot CD is not recognized and the machine tries to boot from the hard disk. I booted the system from an Ubuntu 8,10 disk and just finished install Etch+1/2 on it so there is nothing wrong with the machine. The notes on the Etch+1/2 install indicate it's using the Lenny RC1 installer so I suspect it's not a problem with the installer either. It may be the .iso image simply doesn't have the boot code on it. I'd rather suspect a CD burn issue. However, you don't give any information about the ISO image you downloaded. Could you be more specific? signature.asc Description: Digital signature
Bug#509315: marked as done (Lenny installer RC1)
Your message dated Sun, 21 Dec 2008 08:29:32 +0100 with message-id 20081221072932.gj30...@mykerinos.kheops.frmug.org and subject line Re: Bug#509315: Lenny installer RC1 has caused the Debian Bug report #509315, regarding Lenny installer RC1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 509315: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=509315 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Boot method: How did you boot the installer? CD? floppy? network? CD Image version: Full URL to image you downloaded is best AMD64 netinst Date: Date and time of the install December 13, 2008 Machine: Description of machine (eg, IBM Thinkpad R32) custom older AMD64 machine Processor: AMD Athlon 64 Memory: 1G Partitions: df -Tl will do; the raw partition table is preferred never got that far Output of lspci -knn (or lspci -nn): Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [E] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: I've downloaded the .iso image twice and burned it 3 times using two different machines. I get the same problem each time. The boot CD is not recognized and the machine tries to boot from the hard disk. I booted the system from an Ubuntu 8,10 disk and just finished install Etch+1/2 on it so there is nothing wrong with the machine. The notes on the Etch+1/2 install indicate it's using the Lenny RC1 installer so I suspect it's not a problem with the installer either. It may be the .iso image simply doesn't have the boot code on it. ---End Message--- ---BeginMessage--- Closing duplicate install report signature.asc Description: Digital signature ---End Message---
