Bug#697486: Asus N56DP-DH11 Debian install issues - installation-reports
Ah, I'll give that a shot next time I install Debian 6 on this laptop, Debian 7 beta 4 seems to work well minus a few xorg issues on this laptop. On Fri, Jan 18, 2013 at 3:13 PM, Steve McIntyre wrote: > adn5...@gmail.com wrote: > > > >Package: installation-reports > > > >Boot method: USB Flash drive > >Image version: Unetbootin Debian Unstable_NetInstall_x64 > >Date: 1-5-2012 > > > >Machine: Asus N56DP-DH11 > >Processor: A10-4600m > >Memory: 8GB DDR3 > >Partitions: Unknown, I selected the guided encrypted LVM option. > > ... > > >Comments/Problems: > >Debian appears to not boot after installing it on this system, I have > >CSM enabled so as to avoid the whole SecureBoot/UEFI mess. If I pull > >the SSD from another laptop with an A4-3300M and a Debian Unstable > >64-bit install, that copy of Debian will boot up just fine on this > >Asus laptop, although I'll have a mess of drivers to clean up. > > Hi, > > It sounds like you have a problem with grub EFI booting, then. If you > grab a more recent CD image, you should be able to boot in rescue mode > to be able to see what's happened. efibootmgr should show all the > possible EFI boot options, and if you could check what you have > installed on in /boot/efi that would be very helpful. > > Thanks, > -- > Steve McIntyre, Cambridge, UK. > st...@einval.com > "We're the technical experts. We were hired so that management could > ignore our recommendations and tell us how to do our jobs." -- Mike > Andrews >
Bug#697486: Asus N56DP-DH11 Debian install issues - installation-reports
adn5...@gmail.com wrote: > >Package: installation-reports > >Boot method: USB Flash drive >Image version: Unetbootin Debian Unstable_NetInstall_x64 >Date: 1-5-2012 > >Machine: Asus N56DP-DH11 >Processor: A10-4600m >Memory: 8GB DDR3 >Partitions: Unknown, I selected the guided encrypted LVM option. ... >Comments/Problems: >Debian appears to not boot after installing it on this system, I have >CSM enabled so as to avoid the whole SecureBoot/UEFI mess. If I pull >the SSD from another laptop with an A4-3300M and a Debian Unstable >64-bit install, that copy of Debian will boot up just fine on this >Asus laptop, although I'll have a mess of drivers to clean up. Hi, It sounds like you have a problem with grub EFI booting, then. If you grab a more recent CD image, you should be able to boot in rescue mode to be able to see what's happened. efibootmgr should show all the possible EFI boot options, and if you could check what you have installed on in /boot/efi that would be very helpful. Thanks, -- Steve McIntyre, Cambridge, UK.st...@einval.com "We're the technical experts. We were hired so that management could ignore our recommendations and tell us how to do our jobs." -- Mike Andrews -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1twl7y-0006wp...@mail.einval.com
Bug#693891: Fails to boot in UEFI mode on Dell PowerEdge R520
On Tue, Jan 15, 2013 at 08:09:35PM +0100, Thomas Schmitt wrote: >Hi, > >> will hopefully fix a number of the issues we're seeing with UEFI. > >What problems are there in particular ? We've had a few (admittedly vague, in some cases) reports of boot failures. Some are probably grub, but some include machines apparently just not recognising our boot media. We'll just have to see if we get any more feedback. >Similar as with BIOS we have two main starting points of booting: >El Torito for CD, DVD, BD. >GPT for hard disk and alike. >But i do not know whether the distinction between both is as strict as >it is with BIOS. I.e. we possibly have to expect CD booting via GPT. I don't think so, but who knows what the vendors might do... :-) >Then there is APM in test5 which would be for Macs. >Do you already have test feedback from those ? Not yet, no. Anyway, I've switched daily/weekly production over to xorriso 1.2.6 now. So all of our images should get the latest and greatest features (and bugs :-))... -- Steve McIntyre, Cambridge, UK.st...@einval.com "We're the technical experts. We were hired so that management could ignore our recommendations and tell us how to do our jobs." -- Mike Andrews -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130118230050.gm8...@einval.com
Re: Fwd: Missing network configuration after installing Wheezy image
Hi, On 18 Jan 2013 12:46:24 +0100, Julian Pawlowski wrote: > For me the line "No interface given; clearing /etc/network/interfaces" > looks like the file could not be written correctly due to a missing > interface name. The write_loopback procedure of netcfg-common.c will wipe any existing /etc/network/interfaces file (writing only an 'informative header') and then add only a loopback interface: > 1118 netcfg_write_interface(NULL); > 1119 netcfg_write_interface(&lo); This is triggered once from 40netcfg, and copied into the target immediately. Presumably ifupdown configuration happens sometime after. The above write_loopback procedure is triggered again after install from 55netcfg-copy-config, if "netcfg/target_network_config" is set to "nm_config" or "loopback". (Wiping then writing just a loopback entry). Maybe you need to preseed this setting to "ifupdown" for it to work as expected? Please attach your full /var/log/installer/syslog (gzipped) if that doesn't help. Thanks! Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50f9b2f5.8050...@pyro.eu.org
Re: Fwd: Missing network configuration after installing Wheezy image
Forwarding private mail to list: Date: Fri, 18 Jan 2013 12:46:24 +0100 From: Julian Pawlowski To: Holger Wansing Subject: Re: Fwd: Missing network configuration after installing Wheezy image Hi Holger, actually Daniel from the debian-live team just gave me the opposite advice ;-) Let's see: I believe the issue is in the netcfg package. I just had a look into /var/log/installer/syslog after the installation where I can find the following lines: Jan 16 16:43:10 netcfg[5970]: INFO: Starting netcfg v.1.103 (built 20121210-1746) Jan 16 16:43:10 netcfg[5970]: WARNING **: Couldn't read Wpasupplicant pid file, not trying to kill. Jan 16 16:43:10 netcfg[5970]: INFO: Could not find valid BOOTIF= entry in /proc/cmdline Jan 16 16:43:10 netcfg[5970]: INFO: Taking down interface eth0 Jan 16 16:43:22 netcfg[5970]: INFO: Taking down interface lo Jan 16 16:43:22 netcfg[5970]: INFO: Taking down interface lo Jan 16 16:43:22 netcfg[5970]: INFO: Activating interface eth0 Jan 16 16:43:23 kernel: [ 40.433149] pcnet32 :02:01.0: eth0: link up Jan 16 16:43:23 netcfg[5970]: INFO: executing: ip addr add 192.168.6.61/24 broadcast 192.168.6.255 dev eth0 Jan 16 16:43:23 netcfg[5970]: INFO: Waiting time set to 3 Jan 16 16:43:24 netcfg[5970]: INFO: ethtool-lite: eth0 is connected. Jan 16 16:43:24 netcfg[5970]: INFO: Found link on eth0 Jan 16 16:43:24 netcfg[5970]: ARPING to 192.168.6.30 from 192.168.6.61 via eth0 Jan 16 16:43:24 netcfg[5970]: Unicast reply from 192.168.6.30 [0:24:fe:eb:bc:53] 0.856ms Jan 16 16:43:24 netcfg[5970]: Sent 1 probe(s) (1 broadcast(s)) Jan 16 16:43:24 netcfg[5970]: Received 1 replies (0 request(s), 0 broadcast(s)) Jan 16 16:43:24 netcfg[5970]: INFO: Gateway reachable on eth0 Jan 16 16:43:24 netcfg[5970]: DEBUG: Getting default hostname from rDNS lookup of static-configured address 192.168.6.61 Jan 16 16:43:24 netcfg[5970]: DEBUG: getnameinfo() returned -2: errno 11 (Resource temporarily unavailable) Jan 16 16:43:27 netcfg[5970]: DEBUG: No interface given; clearing /etc/network/interfaces Jan 16 16:43:27 netcfg[5970]: DEBUG: Writing informative header Jan 16 16:43:27 netcfg[5970]: DEBUG: Success! Jan 16 16:43:27 netcfg[5970]: DEBUG: Writing loopback interface Jan 16 16:43:27 netcfg[5970]: DEBUG: Success! Jan 16 16:43:27 netcfg[5970]: DEBUG: Writing static IPv4 stanza for eth0 For me the line "No interface given; clearing /etc/network/interfaces" looks like the file could not be written correctly due to a missing interface name. That is why I added "d-i netcfg/choose_interface select eth0" to preseed.cfg but unfortunately there was not change with a new ISO image build with it. Is my assumption correct, should I open a bug report for netcfg with these information? In fact it's just the /etc/network/interfaces file which is missing information. It's not written by any debian-live specific script IMHO. Cheers, Julian On Thu, Jan 17, 2013 at 5:26 PM, Holger Wansing wrote: > Hi, > > Julian Pawlowski wrote: > > I am currently evaluating the new Debian Installer for Wheezy and am > about > > to migrate a Debian Live 2.0 ISO image creation to Debian Live 3.0. > > > > However it seems I have an issue with the Installer when the live image > > gets installed to a harddrive. I have activated user manual network > > configuration by preseeding the installer (see > > https://gist.github.com/64fd3d812400438d7f6e). However it seems the > > configuration for eth0 is not written to /etc/network/interfaces so after > > the first boot no network is available. As soon as I add settings for > eth0 > > to /etc/network/interfaces everything is working fine. > > Oh and I am using current Debian Live version from Sid to actually build > > the Wheezy ISO, I guess it also includes the latest version of the Debian > > Installer then. > > > > I'm not sure if this is a standalone issue with the Installer, > > unfortunately I got no answer from the debian-live mailing list regarding > > this so far which is why I hope anybody here could maybe shortly comment > on > > this. > > The install functionality from the live-images is completely different > from the debian-installer. So debian-boot is the wrong list. > debian-live is what you want... (as you have guessed). > > Holger -- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Created with Sylpheed 3.0.2 under D e b i a n G N U / L I N U X 6.0 ( S q u e e z e ) Registered LinuxUser #311290 - http://linuxcounter.net/ = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130118205705.c1606675.li...@wansing-online.de
Re: Debian installer build: failed or old builds
On 18/01/13 19:36, Philipp Kern wrote: > rem% ls -al ~buildd/ > ls: cannot access /home/buildd/: No such file or directory Oh. Could a /home partition or network share be not mounted? The machines database still calls it a mipsel buildd, and before the outage it was responsible for the nightly d-i builds on that arch. "Disk space:40g+120g" sounds to me like /home might be the 120 GB disk. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50f9a567.3010...@pyro.eu.org
Re: Debian installer build: failed or old builds
On Fri, Jan 18, 2013 at 06:48:22PM +, Steven Chamberlain wrote: > On 18/01/13 07:03, Martin Zobel-Helas wrote: > > On 18/01/13 05:49, Christian PERRIER wrote: > >> Are there any news? We apparently had no D-I build for mipsel since > >> Jan 10th. > > > > rem is back since Monday. > > Thanks Martin, > > Please could mipsel porters or wb-team see why the nightly d-i builds on > rem.debian.org are not running? There's no buildd on rem anymore. bui...@rem.debian.org SMTP error from remote mail server after RCPT TO:: host rem.debian.org [2001:41b8:202:deb:202:4cff:fefe:d06]: 550 Unrouteable address rem% ls -al ~buildd/ ls: cannot access /home/buildd/: No such file or directory Kind regards Philipp Kern signature.asc Description: Digital signature
Re: Debian installer build: failed or old builds
On 18/01/13 07:03, Martin Zobel-Helas wrote: > On 18/01/13 05:49, Christian PERRIER wrote: >> Are there any news? We apparently had no D-I build for mipsel since >> Jan 10th. > > rem is back since Monday. Thanks Martin, Please could mipsel porters or wb-team see why the nightly d-i builds on rem.debian.org are not running? Thanks, Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50f998f6.9060...@pyro.eu.org
Bug#695048: installation-reports: Must manually reboot into non-EFI mode
Steve McIntyre (18/01/2013): > reassign 695048 partman-efi > thanks > > On Tue, Dec 25, 2012 at 07:47:34PM +0100, Cyril Brulebois wrote: > >Hi Steve, > > > >any insight on this one? > > Basically, our existing EFI support doesn't recognise pre-existing EFI > partitions on dos-partitioned disks. Trivial patch for partman-efi > here. OK to commit? I think it's a safe thing to add for RC1... ACK, thanks. Mraw, KiBi. signature.asc Description: Digital signature
