Re: Experience and problems in installing wheezy b-4
Hi, L V Gandhi wrote: > > I am attaching my syslog > You have attached a syslog of an kubuntu installation. So what? We cannot help on kubuntu installations! 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://counter.li.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/20121125091031.d9e0e473.li...@wansing-online.de
Re: d-i manual (Re: building and testing d-i with jenkins)
Hi, Holger Levsen wrote: > On Donnerstag, 22. November 2012, Holger Wansing wrote: > > > http://jenkins.debian.net/view/d-i_manual/job/d-i_manual_ro_html/1/parsed > > > _console/? would show a lot less warnings, but still some. > > At that url I see only warnings like "Warning: no PO file found for ...", > > no others. > > I'm pretty sure there are others if you scroll down, but I'm writing this > offline, so cannot check. Ok, you are right. There were additional warnings, but not in _that_ language that I checked. 1. for da and nn there were warnings about not existing entity files. I have added empty entity files to avoid that warnings. 2. in el I found this: Warning: pdf and ps formats are currently not supported for Chinese, Greek, Japanese and Vietnamese Info: The following formats were skipped: pdf So, remove them from the build jobs. 3. In de.html I found: Building in workspace /var/lib/jenkins/jobs/d-i_manual_de_html/workspace Updating svn://svn.debian.org/svn/d-i/trunk to revision '2012-11-19T20:31:15.498 +' U manual/en/boot-installer/x86.xml U manual/de/boot-installer/x86.xml U manual/po/da/boot-installer.po U packages/po/sublevel6/mr.po Why do you checkout the packages/po/sublevelX/xx.po ? That files are for installer translation. They are not relevant for the manual and can savely be removed. Holger W. -- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = 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://counter.li.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/20121125093133.baace1ea.li...@wansing-online.de
Re: netinst install-time compilation of network drier
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/24/2012 7:52 AM, Keith Moyer wrote: > There are a few aspects of my installations that add complications > (I'll mention the others at the end), but this email is primarily > to focus on the fact that neither my Ethernet nor wireless > networking cards are supported natively by the (beta4) netinst > image. The DebianInstaller wiki FAQ [1] contains an entry on > building a needed network drivers for debian-installer, but > mentions that instructions aren't available because you're waiting > for someone to try/document it. I'd be willing to do this, if you > think my situation is a good candidate. > > I have Atheros AR8161 gigabit Ethernet and Realtek 8723 b/g/n > wireless networking [2]. The Ethernet card appears to be supported > by the alx driver [3], but is not included in the kernel yet. > Apparently, a compat-wireless tarball is available that can be > compiled to provide support. I have other Wheezy installations > available, but neither is amd64 so cross-compiling would be > necessary if not done on the target. Does this sound like a good > candidate to try install-time compilation? If so, can you provide > guidance on how to do so? I've been able to get around my issue by installing Wheezy in an amd64 VirtualBox VM on the target laptop (in Windows), compiling the alx driver, running the debian-installer on the target and waiting for it to fail (due to no network), dropping to a shell, calling insmod on the driver .ko files, and resuming the installation at network detection. The network was then functional. I cancelled the installation at disk partitioning for the reason I'll explain below. This will work for me, but I'd still be willing to do it the "right" way (install-time compilation) and document the process (as the wiki indicated was needed) if guidance is provided. Now, my primary issue that I'll be trying to overcome is that the debian-installer has gibberish graphics when booting via UEFI. I'd really like to run the installer in UEFI so that I won't have to correct the installation after the fact. If I don't receive help on that in the next couple days (and I don't figure it out on my own), I'll start a new thread (since it's not really related to my original request). - - Keith -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (MingW32) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlCx6lkACgkQmuZlGCxCU2V9SwCghBsRhbpi2HF/SjiLu9at0dcP +3IAoJRWzHbyzVBcZlrIypdj0s/OiUmR =3t/3 -END PGP SIGNATURE- -- 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/50b1ea59.60...@keithmoyer.com
Bug#694310: debootstrap: test-exec function does not work on android
Package: debootstrap
Severity: normal
Tags: patch
Dear Maintainer,
Please accept this patch making the test-exec function work on Android. It is
against current git HEAD.
Note you will still need busybox and root to use debootstrap on Android. You
will
also need to build pkgconfig.c from base-installer statically.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: armhf (armv7l)
Kernel: Linux 3.5.4-00581-g5930e52 (PREEMPT)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
>From c63c87f6e430f628d11d5ca927d4931e09c25da5 Mon Sep 17 00:00:00 2001
From: Shawn Landden
Date: Sun, 25 Nov 2012 10:47:55 +
Subject: [PATCH] functions: check for /bin/sh before using it in shebang
(android)
---
functions | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/functions b/functions
index b450396..097650b 100644
--- a/functions
+++ b/functions
@@ -1299,10 +1299,18 @@ check_sane_mount () {
;;
esac
- cat > "$1/test-exec" < "$1/test-exec" < "$1/test-exec" <
D-I talk at Paris mini-DebConf
Hi folks, I've just given a D-I talk at Paris mini-DebConf, and I've published the handout here: http://people.debian.org/~kibi/talks/ I plan to add its LaTeX source to the debian-installer source package, in doc/talks, if nobody objects. Mraw, KiBi. signature.asc Description: Digital signature
Bug#694310: debootstrap: test-exec function does not work on android
Package: debootstrap
Followup-For: Bug #694310
here is a lighter-weight patch
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: armhf (armv7l)
Kernel: Linux 3.5.4-00581-g5930e52 (PREEMPT)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
>From ca977c0d4d0e6564f54f521aa49ebffe834a50fe Mon Sep 17 00:00:00 2001
From: Shawn Landden
Date: Sun, 25 Nov 2012 10:47:55 +
Subject: [PATCH] functions: check for /bin/sh before using it in shebang
(android)
---
functions |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/functions b/functions
index b450396..881231b 100644
--- a/functions
+++ b/functions
@@ -1300,7 +1300,7 @@ check_sane_mount () {
esac
cat > "$1/test-exec" <
Bug#693464: installation-reports: Root password not recognized when requested and can run in rescue mode wo password
reassign 693464 user-setup-udeb thanks On Sat 24 Nov 2012 at 22:29:39 +0100, Holger Wansing wrote: > Richard Owlett wrote: > > I did the install twice. > > When "shadow password" was *NOT* enabled the problem > > occurred as in my original report. > > When "shadow password" was enabled the problem did *NOT* > > occur. > > I did several test installations (with different beta4 i386 images), > and the problem is reproducible: > when shadow passwords are not used, the installation ends up with > a locked root account. > There is nothing related in the installation logs. It is the same here. The password field is a * in /etc/passwd. Easily changed by booting into rescue mode. Reassigning to what I think is the correct package. Regards, Brian. -- 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/20121125123844.GA23777@desktop
Processed: Re: Bug#693464: installation-reports: Root password not recognized when requested and can run in rescue mode wo password
Processing commands for cont...@bugs.debian.org: > reassign 693464 user-setup-udeb Bug #693464 [installation-reports] installation-reports: Root password not recognized when requested and can run in rescue mode wo password Bug reassigned from package 'installation-reports' to 'user-setup-udeb'. Ignoring request to alter found versions of bug #693464 to the same values previously set Ignoring request to alter fixed versions of bug #693464 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 693464: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693464 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.135384732112612.transcr...@bugs.debian.org
Re: d-i manual (Re: building and testing d-i with jenkins)
Quoting Holger Wansing (li...@wansing-online.de): > Hi, > > Holger Levsen wrote: This thread is funny to see in my MUA: Holger talks to Holger who answers to Holger, etc. I should use Holger as first name to add more confusion..:-) signature.asc Description: Digital signature
Re: D-I talk at Paris mini-DebConf
Quoting Cyril Brulebois (k...@debian.org): > Hi folks, > > I've just given a D-I talk at Paris mini-DebConf, and I've published > the handout here: > http://people.debian.org/~kibi/talks/ > > I plan to add its LaTeX source to the debian-installer source package, > in doc/talks, if nobody objects. I object. signature.asc Description: Digital signature
Re: Experience and problems in installing wheezy b-4
On Sun 25 Nov 2012 at 19:46:58 +0530, L V Gandhi wrote: Hello L V Gandhi, > Sorry for the error. > Attached wheezy installer syslog. However this syslog is from my last > attempt in which I did not select debian desktop as task option. Your very first mail in this thread described three issues. The first two were dealt with quite quickly and do not appear to involve any misbehaviour in the installer or the ISO you downloaded. Indeed, the syslog you provided shows wlan0 being set up correctly for your Wheezy install. The third problem is the important one. A KDE ISO giving you a GNOME desktop is unexpected. We now realise you are booting with UEFI and work in this area is still in progress. I think we have gone as far as we can to address your problems at this stage. Thanks to your report another bug is in the process of being fixed. The result may be in the next version of the KDE ISO. We hope you can find the time to test it when it is released. -- 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/20121125153218.GM13112@desktop
Bug#694068: netcfg: Wireless connectivity present during an install but absent afterwards
Hello, On Fri, Nov 23, 2012 at 4:31 PM, Brian Potkin wrote: > Package: netcfg > Version: 1.102 > Severity: important > Tags: d-i > > > > I installed in expert mode over a wireless link from > > Debian GNU/Linux testing "Wheezy" - Official Snapshot i386 NETINST Binary-1 > 20121122-21:21 > > This ISO has netcfg_1.102. Only "Standard system utilities" was selected > as a task. Re-booted as instructed. No network! Checked the contents of > /etc/network/interfaces. The only interface available is lo. I'm still > in a state of shock. :) > > >From the netcfg changelog: > > * On Linux: Write a network-manager configuration file in perference > to ifupdown if network-manager is found in the installed system. > Configure wired networking with ifupdown if not. Do not configure > wireless networking through ifupdown. > > and > > * Reword target_network_config template; do not ask the question. > > Not only am I deprived of network connectivity because I did not install > network-manager or use a network cable, but this is done silently. > > The machine that Debian was put on is a desktop model and isn't going > anywhere. Now I have try to recollect what to put in /e/n/i to restore > the network connection. Also, the WPA passphrase is a machine generated > 63 random characters. With gpm it's a snap to copy and paste. Except > > If I'd installed to a laptop I might have wanted wpagui to deal with any > roaming. Or network-manager for that matter. Having to start from > scratch is tiresome. > > Anyone who used a network during an install would, in my opinion, most > likely want it available afterwards. Please consider leaving it set up > as configured by ifupdown when the install takes place as described > above. > > Some discussion of the issue is in the thread starting at > >http://lists.debian.org/debian-boot/2012/09/msg00252.html For most cases, I think not adding configuration for wireless in /e/n/i is good, however for the kind a situations you described I think the best solution would be to have the question asked, at least with a low priority. If that would be the case, changing the permissions of /e/n/i to 600 should also be considered. Sorina -- 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/CA+qfQp8H+ATeidnpO1HHM9Rn=sgsindafh2zg12ffr0pf4_...@mail.gmail.com
Re: Experience and problems in installing wheezy b-4
On Sun, Nov 25, 2012 at 9:02 PM, Brian Potkin wrote: > On Sun 25 Nov 2012 at 19:46:58 +0530, L V Gandhi wrote: > > Hello L V Gandhi, > > > Sorry for the error. > > Attached wheezy installer syslog. However this syslog is from my last > > attempt in which I did not select debian desktop as task option. > > Your very first mail in this thread described three issues. The first > two were dealt with quite quickly and do not appear to involve any > misbehaviour in the installer or the ISO you downloaded. Indeed, the > syslog you provided shows wlan0 being set up correctly for your Wheezy > install. > > The third problem is the important one. A KDE ISO giving you a GNOME > desktop is unexpected. We now realise you are booting with UEFI and work > in this area is still in progress. > > I think we have gone as far as we can to address your problems at this > stage. Thanks to your report another bug is in the process of being > fixed. The result may be in the next version of the KDE ISO. We hope > you can find the time to test it when it is released. > > > Thanks. -- L V Gandhi
Re: Trying to install Wheezy on an Asus Zenbook UX32VD
On 24-11-12 21:47, Steve McIntyre wrote: bart...@vrielink.net wrote: On 24-11-12 20:07, Steve McIntyre wrote: If you're only being offered grub-pc, then you've booted already in BIOS mode. If you'd booted in EFI mode, the installer would only be offering grub-efi and would set up using GPT partitions by default. Are you sure? I have to admit that this is the first time I've encountered EFI (my current laptop is 5 years old), but I see in the "BIOS" under the "Boot" tab options such as "Add New Boot Option" for which the context help explicitly mentions EFI. I also do not have an option (or at least, I cannot find it) to revert to the old way of booting. Maybe it's doing implicit fallback if it doesn't like something about the EFI boot setup we've done. There's a lot of variation in how BIOSes behave... :-( If you've booted in EFI mode, then the installer code I wrote should be offering GPT etc. When you boot the installer on your system, do you see a grub boot menu or an isolinux boot menu? At first I used the mini.iso file. That one only showed an isolinux (I assume, I did not recognize it as grub) option. With that one, I eventually managed to do a test-install using "classic" grub2. However, the installer tries to install to /dev/sda, which is the USB stick I booted from. Please try to make it smart enough to pick /dev/sdb (which I did manually). Now I'm trying with the disk1 iso copied to another USB disk. This time it manages to complete the installation without any issues, but fails to boot. After grub, I do get the following at bootup: Loading Linux 3.2.0-4-amd64 ... Loading initial ramdisk ... error: no suitable mode found. Booting however -- 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/50b24b8b.9090...@vrielink.net
Re: Trying to install Wheezy on an Asus Zenbook UX32VD
On Sun, Nov 25, 2012 at 11:47 AM, Bart-Jan Vrielink wrote: > Now I'm trying with the disk1 iso copied to another USB disk. This time it > manages to complete the installation without any issues, but fails to boot. > After grub, I do get the following at bootup: > Loading Linux 3.2.0-4-amd64 ... > Loading initial ramdisk ... > error: no suitable mode found. > Booting however That is grub bug #661789. Best wishes, Mike -- 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/CANTw=mmdhbg52inxa9jipwnoekdswq364l4cidepd6srvxc...@mail.gmail.com
Re: Trying to install Wheezy on an Asus Zenbook UX32VD
On Sun 25 Nov 2012 at 17:47:07 +0100, Bart-Jan Vrielink wrote: > On 24-11-12 21:47, Steve McIntyre wrote: > > > >When you boot the installer on your system, do you see a grub boot > >menu or an isolinux boot menu? > > At first I used the mini.iso file. That one only showed an isolinux > (I assume, I did not recognize it as grub) option. With that one, I > eventually managed to do a test-install using "classic" grub2. > However, the installer tries to install to /dev/sda, which is the > USB stick I booted from. Please try to make it smart enough to pick > /dev/sdb (which I did manually). When you relate ". . . the installer tries to install to /dev/sda, . ." do you mean it tried and failed or it tried and succeeded? GRUB tells you: If all of your operating systems are listed above, then it should be safe to install the boot loader to the master boot record of your first hard drive. In fact, GRUB will always install to /dev/sda, which may or may not be the MBR of your first hard drive. I do not know why this screen cannot say GRUB will go in the MBR of /dev/sda. Also, how could GRUB guess you really wanted it in the MBR of /dev/sdX? I think this is why you are given the opportunity to decline its offer. -- 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/20121125174650.GN13112@desktop
Bug#694344: installation-report: Wheezy beta set up on FSC Futro S400
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports Version: 2.47 Severity: wishlist Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** - -- Package-specific info: Boot method:USB Image version: http://napoleon.acc.umu.se/cdimage/weekly-builds/i386/iso-cd/debian-testing-i386-xfce-CD-1.iso, 2012-11-19 Date: 2012-11-24, about 7.00 h Machine: FSC Futro S400 Partitions: Filesystem Type 1K-blocks Used Available Use% Mounted on rootfs rootfs 6824960 4633048 2191912 68% / udev devtmpfs 10240 0 10240 0% /dev tmpfs tmpfs 44940 608 44332 2% /run /dev/disk/by-uuid/e69a7799-2b82-41ed-8386-8be7a78263d8 xfs6824960 4633048 2191912 68% / tmpfs tmpfs 5120 0 5120 0% /run/lock tmpfs tmpfs 2885201720286800 1% /run/shm Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [o] Detect network card:[o] Configure network: [o] Detect CD: [] Load installer modules: [o] Clock/timezone setup: [o] User/password setup:[o] Detect hard drives: [o] Partition hard drives: [o] Install base system:[o] Install tasks: [o] Install boot loader:[o] Overall install:[o] Comments/Problems: It was probably a normal installation, though not the first one. Initially, I used an ext4 filesystem, but the system showed intermittent boot-problems. Then I tried to use jfs instead, which also hung some time. Turning off S.M.A.R.T. for harddisks probably did the trick, to achieve a reliably booting system, now with an xfs root-filesystem. First I installed only the base-system and standard-system-utilities, then rebooted to set up the debian-desktop-environment with tasksel. Next I used aptitude to also install task-gnome-desktop, but the GNOME-desktop did not start properly. First there was a message, telling, that the 'notification-daemon' failed to start, then I was informed, that the fallback-mode is used. It is unclear to me why this happened. I can try to install the standard-version of wheezy instead of the xfce-version some time to see, if possibly task-gnome-desktop is broken in some way, or incompatible with tasksel-xfce-debian-desktop-environment. 3D-graphics are in working condition and glxgears delivered a framerate of 20, which should be enough for gnome-shell to run. I attach Xorg.0.log.bz2 to give some more insight on this issue. Maybe configuring Xorg manually could be a remedy for this ? If there is no quick fix for this problem it will probably be sufficient to remove the 'gnome-session'-package to prevent users from trying to use GNOME, but still being able to use gnome-services and applications with XFCE. Finally CPU-frequency-scaling was enabled, but I did not manage to make this persistent through reboots at first try. I am going to file this separately against the package 'cpufreqd'. - -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="7.0 (wheezy) - installer build 20121119-00:05" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux s400 3.2.0-4-486 #1 Debian 3.2.32-1 i686 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Silicon Integrated Systems [SiS] 741/741GX/M741 Host [1039:0741] (rev 03) lspci -knn: Subsystem: Silicon Integrated Systems [SiS] 741/741GX/M741 Host [1039:0741] lspci -knn: Kernel driver in use: agpgart-sis lspci -knn: 00:01.0 PCI bridge [0604]: Silicon Integrated Systems [SiS] AGP Port (virtual PCI-to-PCI bridge) [1039:0002] lspci -knn: 00:02.0 ISA bridge [0601]: Silicon Integrated Systems [SiS] SiS963 [MuTIOL Media IO] LPC Controller [1039:0963] (rev 25) lspci -knn: 00:02.1 SMBus [0c05]: Silicon Integrated Systems [SiS] SiS961/2/3 SMBus controller [1039:0016] lspci -knn: 00:02.5 IDE interface [0101]: Silicon Integrated Systems [SiS] 5513 IDE Controller [1039:5513] lspci -knn: Subsystem: Silicon Integrat
Re: Trying to install Wheezy on an Asus Zenbook UX32VD
On 25-11-12 18:46, Brian Potkin wrote: On Sun 25 Nov 2012 at 17:47:07 +0100, Bart-Jan Vrielink wrote: On 24-11-12 21:47, Steve McIntyre wrote: When you boot the installer on your system, do you see a grub boot menu or an isolinux boot menu? At first I used the mini.iso file. That one only showed an isolinux (I assume, I did not recognize it as grub) option. With that one, I eventually managed to do a test-install using "classic" grub2. However, the installer tries to install to /dev/sda, which is the USB stick I booted from. Please try to make it smart enough to pick /dev/sdb (which I did manually). When you relate ". . . the installer tries to install to /dev/sda, . ." do you mean it tried and failed or it tried and succeeded? Tried and failed. (fortunately). During installation, /dev/sda is my USB stick used to boot the installer, /dev/sdb is my first SSD and /dev/sdc my second. After installation, I expect /dev/sda and /dev/sdb to be my first and second SSD's. GRUB tells you: If all of your operating systems are listed above, then it should be safe to install the boot loader to the master boot record of your first hard drive. In fact, GRUB will always install to /dev/sda, which may or may not be the MBR of your first hard drive. I do not know why this screen cannot say GRUB will go in the MBR of /dev/sda. Also, how could GRUB guess you really wanted it in the MBR of /dev/sdX? I think this is why you are given the opportunity to decline its offer. Well, maybe because it is not that unusual to boot off an USB stick in order to install the OS? More and more laptops come without optical drives these days, and an installer should be able to cope with that... Yeah, there is a manual option to override, but GRUB should be smarter than that, and attempt to install to the first drive on which software was installed to, and not just the alphabetically first drive. -- 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/50b25cf4.8000...@vrielink.net
Re: Trying to install Wheezy on an Asus Zenbook UX32VD
On 25-11-12 18:44, Michael Gilbert wrote: On Sun, Nov 25, 2012 at 11:47 AM, Bart-Jan Vrielink wrote: Now I'm trying with the disk1 iso copied to another USB disk. This time it manages to complete the installation without any issues, but fails to boot. After grub, I do get the following at bootup: Loading Linux 3.2.0-4-amd64 ... Loading initial ramdisk ... error: no suitable mode found. Booting however That is grub bug #661789. Looks like it is. Anyone knows a workaround? -- 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/50b25d50.1000...@vrielink.net
Re: Trying to install Wheezy on an Asus Zenbook UX32VD
On Sun, Nov 25, 2012 at 1:02 PM, Bart-Jan Vrielink wrote: >> That is grub bug #661789. > > Looks like it is. Anyone knows a workaround? Yes. Take a look at the merged bug reports. Best wishes, Mike -- 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/CANTw=MP7xUqP1MRTnh8DLn1T13ncEUaRpM2oZkvt=tY_Jkga=w...@mail.gmail.com
Bug#694348: wheezy installer not detecting all usb-storage devices
Package: debian-installer Version: 7.0 (wheezy) - installer build 20121114 Severity: important debian-wheezy-DI-b4-amd64-CD-1.iso on 4 GB USB stick I intended to install wheezy to internally USB connected SD card slot on 16 GB SD which contained successfully installed amd64 squeeze 6.0.6 w/default gnome desktop. Also had no problems installing same w/desktop=lxde boot parameter on different 16 GB SD. Both have grub on their own card and boot fine. Similarly no problems installing amd64 Ubuntu 11.10 on the 16 GB card that currently has squeeze or installing both amd64 Ubuntu and Lubuntu 12.04 on a single 32 GB SD. wheezy gui install proceeded smoothly (configured wlan0, users, clock, etc.) until partitioning. When I selected Manual it only showed partitions on sda (32 GB SSD w/Win7 Pro) and sdb (4 GB USB stick w/wheezy installer. Only those 2 devices showed being detected in syslog. wheezy installer fdisk -l Disk /dev/sda: 32.0 GB, 32017047552 bytes 255 heads, 63 sectors/track, 3892 cylinders, total 62533296 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xd0c93913 Device Boot Start End Blocks Id System /dev/sda1 *2048 206847 1024007 HPFS/NTFS/exFAT /dev/sda2 20684862533295311632247 HPFS/NTFS/exFAT Disk /dev/sdb: 4022 MB, 4022337024 bytes 124 heads, 62 sectors/track, 1021 cylinders, total 7856127 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x653fd82c Device Boot Start End Blocks Id System /dev/sdb1 * 64 1298431 649184 17 Hidden HPFS/NTFS /dev/sdb2 1298432 1299327 4481 FAT12 I expected wheezy installer to find 3 storage devices sda (32 GB SSD), sdb (16 GB SD), and sdc (4 GB USB installer). Since the intended target was 16 GB SD and that was not detected, I had to abort wheezy installation. Note that there is nothing wrong with the SD card, because after several attempted wheezy installations, I could still successfully boot squeeze from that same 16 GB SD card in that same card slot. Expected fdisk -l Disk /dev/sda: 32.0 GB, 32017047552 bytes 255 heads, 63 sectors/track, 3892 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xd0c93913 Device Boot Start End Blocks Id System /dev/sda1 * 1 13 1024007 HPFS/NTFS /dev/sda2 133893311632247 HPFS/NTFS Disk /dev/sdb: 15.9 GB, 15931539456 bytes 255 heads, 63 sectors/track, 1936 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xa387 Device Boot Start End Blocks Id System /dev/sdb1 * 1185214872576 83 Linux /dev/sdb218521937 6830095 Extended /dev/sdb518521937 683008 82 Linux swap / Solaris Disk /dev/sdc: 4022 MB, 4022337024 bytes 124 heads, 62 sectors/track, 1021 cylinders Units = cylinders of 7688 * 512 = 3936256 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x653fd82c Device Boot Start End Blocks Id System /dev/sdc1 * 1 169 649184 17 Hidden HPFS/NTFS /dev/sdc2 169 170 4481 FAT12 Hardware: Acer W500P tablet PC detachable keyboard, Logitech wireless mouse AMD C-50 1 GHz 2 core 2 GB ATI HD 6250 graphics I have wheezy installer debug log if needed, although, it would show an additional USB memory stick connected at the end to dump the log to. -- 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/pine.neb.4.64.1211251719330.29...@sdf.lonestar.org
Bug#685801: (no subject)
I tried the official debian-wheezy-live-a2-i386-lxde-desktop.img now. But the problem is still the same: it hangs up with a black and white pixeled screen (just like heavy snowfall). In failsafe mode it's the same. Boot option vga=0 has no effect too. Because I can't see anything on the screen I can't read any messages nor have a look at a log file. Oliver -- 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/20121125200408.2276e3bb.os.n...@gmx.de
Re: Trying to install Wheezy on an Asus Zenbook UX32VD
On Sun 25 Nov 2012 at 19:01:24 +0100, Bart-Jan Vrielink wrote: > On 25-11-12 18:46, Brian Potkin wrote: > >On Sun 25 Nov 2012 at 17:47:07 +0100, Bart-Jan Vrielink wrote: > > > >When you relate ". . . the installer tries to install to /dev/sda, . ." > >do you mean it tried and failed or it tried and succeeded? > > Tried and failed. (fortunately). During installation, /dev/sda is my > USB stick used to boot the installer, /dev/sdb is my first SSD and > /dev/sdc my second. After installation, I expect /dev/sda and > /dev/sdb to be my first and second SSD's. It would be highly unfortunate if you had wanted GRUB to be on /dev/sda. But I could not resist checking whether you had hit #655532. Not a high profile bug, as I imagine the number of people using the mini.iso to install to the USB device which holds the ISO to be low. But it's a nice trick if you can pull it off. > >GRUB tells you: > > > > If all of your operating systems are listed above, then it > > should be safe to install the boot loader to the master > > boot record of your first hard drive. > > > >In fact, GRUB will always install to /dev/sda, which may or may not be > >the MBR of your first hard drive. I do not know why this screen cannot > >say GRUB will go in the MBR of /dev/sda. > > > >Also, how could GRUB guess you really wanted it in the MBR of /dev/sdX? > >I think this is why you are given the opportunity to decline its offer. > > Well, maybe because it is not that unusual to boot off an USB stick > in order to install the OS? More and more laptops come without > optical drives these days, and an installer should be able to cope > with that... It is the combination of USB stick and netboot mini.iso which gave rise to your confusion. > Yeah, there is a manual option to override, but GRUB should be > smarter than that, and attempt to install to the first drive on > which software was installed to, and not just the alphabetically > first drive. It would be nice to have this, but I'm not well up with the intricacies of GRUB and grub-installer to comment further. Something based on UUIDs, perhaps? -- 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/20121125191033.GO13112@desktop
Re: netinst + uefi (was Re: netinst install-time compilation of network drier)
On Sun, Nov 25, 2012 at 12:13 AM, Keith Moyer wrote: > On 11/24/2012 4:53 PM, Steve McIntyre wrote: >> No, you're doing the right thing. dd to the raw device is the >> right way to use the image, I was just checking that was what >> you'd done. Hmmm. Another machine that doesn't like the UEFI stuff >> we've got, it seems. :-( > > I think it was just the fault of a cheap USB key. I reflashed the > netinst image onto a better one, and it is UEFI bootable. Is there anything of interest about that USB drive? What brand/model was it? Which USB standard does it conform to? What does dmesg say when you plug it in? Best wishes, Mike -- 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/CANTw=MNzKLa2QRz6BGVYew6Vv=gqtyjeg9jkvghbv+6uqjj...@mail.gmail.com
Bug#693510: kfreebsd: Could not get identity of device (was: Fwd: Bug#693510: installation report)
Control: clone -1
Control: retitle -1 kfreebsd: Could not get identity of device
Control: reassign -1 src:parted
Control: found -1 2.3-11
Control: user debian-...@lists.debian.org
Control: usertags -1 kfreebsd
Hi!
On 19/11/12 17:23, Arno Töll wrote:
> It might be helpful to know which ioctl d-i tries to call down the bus,
> as I suspect it is one not supported by the FreeBSD kernel. Hence,
> bypassing that code may help.
It's probably this, in parted-2.3 debian/patches/kfreebsd-gnu.patch:
> +++ b/libparted/arch/freebsd.c
[...]
> + if (ioctl (arch_specific->fd, IOCATAGPARM, ¶ms) != 0) {
> + ex_status = ped_exception_throw (
> + PED_EXCEPTION_WARNING,
> + PED_EXCEPTION_IGNORE_CANCEL,
> + _("Could not get identity of device %s - %s"),
> + dev->path, strerror (errno));
This would normally look up the IDE drive model/revision to identify it
in the partition editor. It will fall back to 'Generic IDE' if the user
selects 'Ignore' in the dialog and is otherwise harmless.
I can't guess from upstream's SVN changelog why it would have stopped
working, so maybe we we can try old kfreebsd-8 installer images to see
when the problem started. (Or does it only affect kfreebsd-9?)
If somehow it's not fixable before release, the Ignore/Cancel dialog
might be removed, to avoid confusing users, and it could always return
'Generic IDE' without attempting the ioctl.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: OpenPGP digital signature
Processed (with 3 errors): Re: kfreebsd: Could not get identity of device (was: Fwd: Bug#693510: installation report)
Processing control commands: > clone -1 > retitle -1 kfreebsd: Could not get identity of device Bug #693510 [installation-reports] installation report Changed Bug title to 'kfreebsd: Could not get identity of device' from 'installation report' > reassign -1 src:parted Bug #693510 [installation-reports] kfreebsd: Could not get identity of device Bug reassigned from package 'installation-reports' to 'src:parted'. Ignoring request to alter found versions of bug #693510 to the same values previously set Ignoring request to alter fixed versions of bug #693510 to the same values previously set > found -1 2.3-11 Bug #693510 [src:parted] kfreebsd: Could not get identity of device Marked as found in versions parted/2.3-11. > user debian-...@lists.debian.org > usertags -1 kfreebsd -- 693510: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693510 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.b693510.13538728087565.transcr...@bugs.debian.org
Processed: Re: Processed (with 3 errors): Re: kfreebsd: Could not get identity of device
Processing commands for cont...@bugs.debian.org: > # oops; retry clone, and put original report back how it was > clone 693510 -1 Bug #693510 [src:parted] kfreebsd: Could not get identity of device Bug 693510 cloned as bug 694358 > retitle -1 installation report Bug #694358 [src:parted] kfreebsd: Could not get identity of device Changed Bug title to 'installation report' from 'kfreebsd: Could not get identity of device' > reassign -1 installation-reports Bug #694358 [src:parted] installation report Bug reassigned from package 'src:parted' to 'installation-reports'. No longer marked as found in versions parted/2.3-11. Ignoring request to alter fixed versions of bug #694358 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 693510: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693510 694358: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694358 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.135387334211759.transcr...@bugs.debian.org
Bug#694068: netcfg: Wireless connectivity present during an install but absent afterwards
On Sun 25 Nov 2012 at 17:30:28 +0200, Sorina - Gabriela Sandu wrote: Hello Sorina. > For most cases, I think not adding configuration for wireless in > /e/n/i is good, however for the kind a situations you described I > think the best solution would be to have the question asked, at least > with a low priority. If that would be the case, changing the > permissions of /e/n/i to 600 should also be considered. Having the question asked in *all* cases would be far preferable to having something you may not want forced on you. I still do not understand "For most cases . . .". Without a handful of CDs available there is only one way to restore the disallowed connection to a network - ifupdown. Set it up, pull it down, set it up again isn't my idea of what Debian should do. Because the opportunity may not arise again: I have been following the development of wireless connectivity in D-I for the past year. The implementation (from the point of view of whether it works) is very good. I would like to thank you and everybody else for the work which has been done. The quality of the emerging end result is a credit to the Debian Project and shows what can be achieved with Free software and a team of committed developers. -- 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/20121125195902.GP13112@desktop
Bug#694358: kfreebsd: Could not get identity of device
On 25/11/12 19:21, Steven Chamberlain wrote: > I can't guess from upstream's SVN changelog why it would have stopped > working, so maybe we we can try old kfreebsd-8 installer images to see > when the problem started. (Or does it only affect kfreebsd-9?) Actually this only affects kfreebsd-9... Regards, -- Steven Chamberlain ste...@pyro.eu.org signature.asc Description: OpenPGP digital signature
Processed: Re: Processed: Re: Processed (with 3 errors): Re: kfreebsd: Could not get identity of device
Processing commands for cont...@bugs.debian.org: > retitle 693510 installation report Bug #693510 [src:parted] kfreebsd: Could not get identity of device Changed Bug title to 'installation report' from 'kfreebsd: Could not get identity of device' > # cloned issue for parted: > retitle 694358 parted: [kfreebsd-9] Could not get identity of device Bug #694358 [installation-reports] installation report Changed Bug title to 'parted: [kfreebsd-9] Could not get identity of device' from 'installation report' > thanks Stopping processing here. Please contact me if you need assistance. -- 693510: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693510 694358: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694358 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.135387400716947.transcr...@bugs.debian.org
Re: d-i manual (Re: building and testing d-i with jenkins)
Hi, Holger Wansing wrote: > 3. In de.html I found: > > Building in workspace /var/lib/jenkins/jobs/d-i_manual_de_html/workspace > Updating svn://svn.debian.org/svn/d-i/trunk to revision > '2012-11-19T20:31:15.498 +' > U manual/en/boot-installer/x86.xml > U manual/de/boot-installer/x86.xml > U manual/po/da/boot-installer.po > U packages/po/sublevel6/mr.po > > Why do you checkout the packages/po/sublevelX/xx.po ? > That files are for installer translation. > They are not relevant for the manual and can savely be removed. Also, in http://jenkins.debian.net/view/d-i_manual/job/d-i_manual_ko_pdf/2/consoleFull I just found, that all po files from all sublevels are included in the checkout: A packages/po/sublevel1 A packages/po/sublevel1/eo.po A packages/po/sublevel1/mg.po A packages/po/sublevel1/bs.po A packages/po/sublevel1/cs.po A packages/po/sublevel1/kk.po A packages/po/sublevel1/pt_BR.po A packages/po/sublevel1/es.po A packages/po/sublevel1/mk.po A packages/po/sublevel1/ko.po A packages/po/sublevel1/lo.po A packages/po/sublevel1/ug.po A packages/po/sublevel1/is.po A packages/po/sublevel1/sk.po A packages/po/sublevel1/uk.po A packages/po/sublevel1/ms.po and so on. Holger W. -- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = 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/20121125213810.a5ab3440.li...@wansing-online.de
Re: Bug#651720: new ZFS installs completely broken in Wheezy/Sid
Control: reassign -1 src:grub-installer Control: found -1 1.83 Control: severity -1 grave Control: tags -1 + patch Hi, This issue relates to GNU/kFreeBSD installs with a ZFS root filesystem, but with a non-ZFS /boot partition. The previously attempted fix in partman-zfs would have worked for all cases except this one. On 20/11/12 23:19, Arno Töll wrote: > I've prepared a _completely untested_ patch which may fix the issue but > I have no idea how to test it. I was able to test Arno's patch by editing the /usr/bin/grub-installer by hand while running d-i. I can confirm that it triggers creation of the necessary zpool.cache within /target/boot/zfs, GRUB installation succeeds, and the installed system is bootable. http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=30;filename=0001-Also-create-boot-zfs-zpool.cache-if-the-root-fs-is-o.patch;att=1;bug=651720 Thanks! Regards, -- Steven Chamberlain ste...@pyro.eu.org signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#651720: new ZFS installs completely broken in Wheezy/Sid
Processing control commands: > reassign -1 src:grub-installer Bug #651720 [partman-zfs] new ZFS installs completely broken in Wheezy/Sid Bug reassigned from package 'partman-zfs' to 'src:grub-installer'. No longer marked as found in versions partman-zfs/23. Ignoring request to alter fixed versions of bug #651720 to the same values previously set > found -1 1.83 Bug #651720 [src:grub-installer] new ZFS installs completely broken in Wheezy/Sid Marked as found in versions grub-installer/1.83. > severity -1 grave Bug #651720 [src:grub-installer] new ZFS installs completely broken in Wheezy/Sid Ignoring request to change severity of Bug 651720 to the same value. > tags -1 + patch Bug #651720 [src:grub-installer] new ZFS installs completely broken in Wheezy/Sid Added tag(s) patch. -- 651720: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651720 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.b651720.13538768327744.transcr...@bugs.debian.org
Bug#694068: netcfg: Wireless connectivity present during an install but absent afterwards
Hello, On Sun, Nov 25, 2012 at 9:59 PM, Brian Potkin wrote: > On Sun 25 Nov 2012 at 17:30:28 +0200, Sorina - Gabriela Sandu wrote: > > Hello Sorina. > >> For most cases, I think not adding configuration for wireless in >> /e/n/i is good, however for the kind a situations you described I >> think the best solution would be to have the question asked, at least >> with a low priority. If that would be the case, changing the >> permissions of /e/n/i to 600 should also be considered. > > Having the question asked in *all* cases would be far preferable to > having something you may not want forced on you. Yes, the question should be asked for all installs, but with a low priority. I can't think of a criterion on which to decide whether to ask it or not and I also don't believe that having such criterion would be useful. > I still do not understand "For most cases . . .". Without a handful of > CDs available there is only one way to restore the disallowed connection > to a network - ifupdown. Set it up, pull it down, set it up again isn't > my idea of what Debian should do. What I wanted to say by "For most cases" is that I believe that having the _default_ to not write wireless config in /e/n/i is good, and this would work for most installs (but obviously not for the case you mentioned). I wasn't thinking of asking the questions is "some cases" and not in others. I hope it's more clear now :) > Because the opportunity may not arise again: > > I have been following the development of wireless connectivity in D-I > for the past year. The implementation (from the point of view of whether > it works) is very good. I would like to thank you and everybody else for > the work which has been done. The quality of the emerging end result is > a credit to the Debian Project and shows what can be achieved with Free > software and a team of committed developers. Thanks, Sorina -- 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/ca+qfqp9difr5lc1spmo4kdxey5fhsgq3tagktcs46jotuqx...@mail.gmail.com
Re: d-i manual (Re: building and testing d-i with jenkins)
Hi, Holger Levsen wrote: > Hi, > > On Donnerstag, 22. November 2012, Holger Wansing wrote: > > > http://jenkins.debian.net/view/d-i_manual/job/d-i_manual_ro_html/1/parsed > > > _console/? would show a lot less warnings, but still some. I investigated the build errors for korean pdf format. That one builds fine here, but I had to install korean fonts additionally. Maybe you also have the package ko.tex-base not installed on jenkins? Holger W. -- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = 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/20121125220300.e0fe9099.li...@wansing-online.de
Re: D-I talk at Paris mini-DebConf
Nobody at "Sun, 25 Nov 2012 14:32:12 +0100" wrote: N> Quoting Cyril Brulebois (k...@debian.org): >> Hi folks, >> >> I've just given a D-I talk at Paris mini-DebConf, and I've published >> the handout here: >> http://people.debian.org/~kibi/talks/ >> >> I plan to add its LaTeX source to the debian-installer source package, >> in doc/talks, if nobody objects. N> I object. ROTFL. Christian you playing the fool ;-) Bye sc -- Stefano Canepa aka sc: s...@linux.it - http://www.stefanocanepa.it Three great virtues of a programmer: laziness, impatience and hubris. Le tre grandi virtù di un programmatore: pigrizia, impazienza e arroganza. (Larry Wall) -- 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/87sj7xqpmo@lepre.stefanocanepa.home
Bug#694344: installation-report: Wheezy beta set up on FSC Futro S400
On Sun, 2012-11-25 at 18:48 +0100, Andreas Glaeser wrote: [...] > Finally CPU-frequency-scaling was enabled, but I did not manage to > make this persistent through reboots at first try. I am going to file > this separately against the package 'cpufreqd'. The kernel is supposed to trigger loading of the CPU frequency scaling driver that is appropriate for your CPU. It should no longer rely on cpufreqd or cpufrequtils. Did this not happen? Which driver did you need to load? Ben. -- Ben Hutchings Never attribute to conspiracy what can adequately be explained by stupidity. signature.asc Description: This is a digitally signed message part
Intel Core i7-3630QM UEFI boot results in corrupt display
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I am attempting to install Debian Wheezy onto my new Toshiba Satellite S855-S5378 laptop using the beta4 debian-installer (I've tried the DVD images and the netinst images on USB and CD). When I boot debian-installer in Compatibility Support Module (CSM) mode, the installer runs fine. However, it would install grub in BIOS mode. I need it to be in UEFI mode to allow dual booting Windows 8 (which came pre-installed). When I boot the debian-installer in UEFI mode, however, I just get a flash of: Welcome to Grub! Error: "prefix" not set. then the screen is all scrambled. It appears as though a smaller horizontal resolution is being used and the scan lines are just being appended to each other. So, image is squished to the stop ~40% of the screen and the image is illegible. Is this a UEFI issue or a Grub issue? Any ideas on how I should proceed? I've noticed that newer versions of grub has a commit (revno: 4412) to "Reject invalid resolutions" in efi_gop.c. I'm not familiar with either either UEFI or Grub code, but that sounds promising to me. I've checked out and compiled the debian-installer code. Would updating Grub to 2.00 be difficult or have bad consequences? If this would be the thing to do, I'd appreciate a pointer on how to build netinst images from the compiled debian-installer; I can't seem to find anything on how to do that. Thanks! - - Keith -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (MingW32) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlCyutkACgkQmuZlGCxCU2VH7wCgvY21nWmXOw1kPA1tzs7YD1F4 RSQAoN3rPOFhzuEfqvmljhUWBNKpvcOP =sHze -END PGP SIGNATURE- -- 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/50b2bad9.3080...@keithmoyer.com
Bug#694348: wheezy installer not detecting all usb-storage devices
debian-installer debug info is now at: http://efflandt.freeshell.org/install-bug-694348/ -- 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/pine.neb.4.64.1211260134240.18...@faeroes.freeshell.org
Re: Re: netinst + uefi (was Re: netinst install-time compilation of network drier)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/25/2012 01:23 PM, Michael Gilbert wrote: > Is there anything of interest about that USB drive? What > brand/model was it? Which USB standard does it conform to? What > does dmesg say when you plug it in? It's a USB drive incorporated into the end of a bottle opener that my company gives away to college students at career fairs (containing a pamphlet PDF). :-) I originally chose it because it's the smallest one I had that could fit the netinst image. The USB part of it is probably the cheapest hardware they could find (understandably)... So, I wouldn't worry about any real-world incompatibility issues. [ 125.072066] usb 1-1: new high-speed USB device number 3 using ehci_hcd [ 125.204935] usb 1-1: New USB device found, idVendor=8644, idProduct=800b [ 125.204947] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 125.204958] usb 1-1: Product: USB Flash Disk [ 125.204966] usb 1-1: Manufacturer: General -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlCy+gQACgkQmuZlGCxCU2X5DQCgkvU9Bxa6UaguXGOQ/qaFqexz rQkAn1svWS2O/xFHfFCP4dIgqLOobn+8 =Y/Et -END PGP SIGNATURE- -- 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/50b2fa04.8020...@keithmoyer.com
yaboot-installer and base-installer need upload
Hi Christian and Cyril, As d-i beta 4 is out, could you please upload yaboot-installer and base-installer? Thanks, Milan signature.asc Description: OpenPGP digital signature
