Processed: Re: Bug#686314: Wheezy Instalation Report on Samsung NP305U1A
Processing commands for cont...@bugs.debian.org: > reassign 686314 os-prober Bug #686314 [installation-reports] Wheezy Instalation Report on Samsung NP305U1A Bug reassigned from package 'installation-reports' to 'os-prober'. Ignoring request to alter found versions of bug #686314 to the same values previously set Ignoring request to alter fixed versions of bug #686314 to the same values previously set > retitle 686314 Requires the fuse module to be loaded in order to detect > Windows 7 Bug #686314 [os-prober] Wheezy Instalation Report on Samsung NP305U1A Changed Bug title to 'Requires the fuse module to be loaded in order to detect Windows 7' from 'Wheezy Instalation Report on Samsung NP305U1A' > thanks Stopping processing here. Please contact me if you need assistance. -- 686314: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686314 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.134638979023226.transcr...@bugs.debian.org
Bug#686314: Wheezy Instalation Report on Samsung NP305U1A
reassign 686314 os-prober retitle 686314 Requires the fuse module to be loaded in order to detect Windows 7 thanks Quoting Ruben Leote Mendes (ru...@nocturno.org): > The error on Detect network card is Bug #683849. After workaround the > instalation proceeds until installing GRUB. It does not detect Windows 7. > The problem is grub-mount requires fuse kernel support but the module is > not available. I did "insmod > /target/lib/modules/3.2.0-3-amd64/kernel/fs/fuse/fuse.ko". Retried the > bootloader install and it detected Windows 7. The instalation then > finished successfully. That's very interesting information as it seems we have several reports of Win7 not being detected if I'm correct. Can you confirm that loading the fuse module *during the install process before the boot loader setup* was enough for W7 to be detected? If so, we would really need to do it but we can't do it the way you did of course-->we'd need the fuse module in the installer's kernel. signature.asc Description: Digital signature
Bug#686314: Wheezy Instalation Report on Samsung NP305U1A
Package: installation-reports Boot method: USB stick Image version: Beta 1 - http://cdimage.debian.org/cdimage/wheezy_di_beta1/amd64/iso-cd/debian-wheezy-DI-b1-amd64-netinst.iso Date: 2012/08/30 Machine: Samsung NP305U1A Processor: AMD E-450 Memory: 4GB Partitions: Filesystem Type 1K-blocks Used Available Use% Mounted on rootfs rootfs19464068 4097784 15170988 22% / udev devtmpfs 10240 0 10240 0% /dev tmpfs tmpfs 38 732379268 1% /run /dev/disk/by-uuid/72d72937-453a-4690-95e2-12ef2ac3f4c7 ext4 19464068 4097784 15170988 22% / tmpfs tmpfs 5120 0 5120 0% /run/lock tmpfs tmpfs 759996 92759904 1% /tmp tmpfs tmpfs 759996 80759916 1% /run/shm /dev/mapper/sda6_crypt ext4 392900060 6092452 382874048 2% /home Output of lspci -knn: 00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] Family 14h Processor Root Complex [1022:1510] Subsystem: Samsung Electronics Co Ltd Device [144d:c600] 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI Wrestler [Radeon HD 6320] [1002:9806] Subsystem: Samsung Electronics Co Ltd Device [144d:c600] 00:01.1 Audio device [0403]: Advanced Micro Devices [AMD] nee ATI Wrestler HDMI Audio [Radeon HD 6250/6310] [1002:1314] Subsystem: Samsung Electronics Co Ltd Device [144d:c600] Kernel driver in use: snd_hda_intel 00:04.0 PCI bridge [0604]: Advanced Micro Devices [AMD] Family 14h Processor Root Port [1022:1512] Kernel driver in use: pcieport 00:11.0 SATA controller [0106]: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] [1002:4391] Subsystem: Samsung Electronics Co Ltd Device [144d:c600] Kernel driver in use: ahci 00:12.0 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397] Subsystem: Samsung Electronics Co Ltd Device [144d:c600] Kernel driver in use: ohci_hcd 00:12.2 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396] Subsystem: Samsung Electronics Co Ltd Device [144d:c600] Kernel driver in use: ehci_hcd 00:13.0 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397] Subsystem: Samsung Electronics Co Ltd Device [144d:c600] Kernel driver in use: ohci_hcd 00:13.2 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396] Subsystem: Samsung Electronics Co Ltd Device [144d:c600] Kernel driver in use: ehci_hcd 00:14.0 SMBus [0c05]: Advanced Micro Devices [AMD] nee ATI SBx00 SMBus Controller [1002:4385] (rev 42) Subsystem: Samsung Electronics Co Ltd Device [144d:c600] Kernel driver in use: piix4_smbus 00:14.2 Audio device [0403]: Advanced Micro Devices [AMD] nee ATI SBx00 Azalia (Intel HDA) [1002:4383] (rev 40) Subsystem: Samsung Electronics Co Ltd Device [144d:c600] Kernel driver in use: snd_hda_intel 00:14.3 ISA bridge [0601]: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 LPC host controller [1002:439d] (rev 40) Subsystem: Samsung Electronics Co Ltd Device [144d:c600] 00:14.4 PCI bridge [0604]: Advanced Micro Devices [AMD] nee ATI SBx00 PCI to PCI Bridge [1002:4384] (rev 40) 00:14.5 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB OHCI2 Controller [1002:4399] Subsystem: Samsung Electronics Co Ltd Device [144d:c600] Kernel driver in use: ohci_hcd 00:15.0 PCI bridge [0604]: Advanced Micro Devices [AMD] nee ATI SB700/SB800/SB900 PCI to PCI bridge (PCIE port 0) [1002:43a0] Kernel driver in use: pcieport 00:15.1 PCI bridge [0604]: Advanced Micro Devices [AMD] nee ATI SB700/SB800/SB900 PCI to PCI bridge (PCIE port 1) [1002:43a1] Kernel driver in use: pcieport 00:15.2 PCI bridge [0604]: Advanced Micro Devices [AMD] nee ATI SB900 PCI to PCI bridge (PCIE port 2) [1002:43a2] Kernel driver in use: pcieport 00:15.3 PCI bridge [0604]: Advanced Micro Devices [AMD] nee ATI SB900 PCI to PCI bridge (PCIE port 3) [1002:43a3] Kernel driver in use: pcieport 00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 0 [1022:1700] (rev 43) 00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 1 [1022:1701] 00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 2 [1022:1702] 00:18.3 Host bridge [0600]: Advance
Bug#686097: understanding/contributing to partman-btrfs
On 30/08/12 22:07, Joey Hess wrote: > Daniel Pocock wrote: >> I've described such a solution in the bug report: >> >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686097 >> >> If you think it is sensible (or if something looks obviously silly), >> could you comment on it? I will hopefully have more time next week to >> play with it, but I'll let it sit there for a few days to see if >> anyone has comments about it. > > I don't know if that's worth it, it'll be a feature that entirely lacks > discoverability for users. > Maybe not such a bad thing: the btrfs crew still insist it is experimental. Just the other day I saw something about btrfs crashing the kernel when all RAID elements are not present -- 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/503fcec6.90...@pocock.com.au
Bug#686097: understanding/contributing to partman-btrfs
Daniel Pocock wrote: > I've described such a solution in the bug report: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686097 > > If you think it is sensible (or if something looks obviously silly), > could you comment on it? I will hopefully have more time next week to > play with it, but I'll let it sit there for a few days to see if > anyone has comments about it. I don't know if that's worth it, it'll be a feature that entirely lacks discoverability for users. > Anything more comprehensive than what I've described would require UI > changes (e.g. prompting user for RAID level) Of course, d-i already knows how to promt the user for the RAID level -- when setting up normal software RAID. Finding a way to make partman-md also support btrfs raid seems like a nice approach, but I don't know how it would work either in the UI or internally. -- see shy jo signature.asc Description: Digital signature
Bug#686226: marked as done ([FATAL] Wheezy Debian installer fails on Qosmio hardware)
Your message dated Thu, 30 Aug 2012 21:44:40 +0200 with message-id <20120830194440.gr5...@mykerinos.kheops.frmug.org> and subject line Re: Bug#686226: [FATAL] Wheezy Debian installer fails on Qosmio hardware has caused the Debian Bug report #686226, regarding [FATAL] Wheezy Debian installer fails on Qosmio hardware 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.) -- 686226: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686226 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debian-installer Version: 20120712 Severity: serious Hi, I'm trying to install Debian from Wheezy DVD (BETA1) on amd64. (Qosmio X300-130 laptop). Actual Result: It fails during the "Detect network hardware" phase. Ie. stops progressing, and no way to skip this stage. and in console (F4) it complains about the lack of iwl Intel Wireless firmware and missing eth1394 (Firewire Ethernet). Expected Result: Should proceed without problematic firmware or drivers. Debian 6.0 works great on this same hardware. (installed from amd64 DVD) -- -Alexey Eromenko "Technologov" --- End Message --- --- Begin Message --- Quoting Alexey Eromenko (al4...@gmail.com): > Package: debian-installer > Version: 20120712 > Severity: serious > > Hi, > > I'm trying to install Debian from Wheezy DVD (BETA1) on amd64. (Qosmio > X300-130 laptop). > > Actual Result: > It fails during the "Detect network hardware" phase. Ie. stops > progressing, and no way to skip this stage. > > and in console (F4) it complains about the lack of iwl Intel Wireless > firmware and missing eth1394 (Firewire Ethernet). This is fixed in upcoming beta2. Known kernel bug, currently worked around in mountmedia. signature.asc Description: Digital signature --- End Message ---
Bug#686097: possible solution
Suggested that any enhancement to support this for wheezy must be non-disruptive and must not require changes to any strings that would need to be translated. The only way I see of supporting that for wheezy is described below: Concept: * user can specify two partitions with the same mount point, provided they are both btrfs * partman-btrfs will recognise this special case and assume that RAID1 is desired * due to the requirement to avoid changing any text strings, this will happen silently and the user will not be prompted to choose RAID level or other possible choices * if filesystems are not btrfs, the normal error will appear package partman-target -- check.d/ proper_mountpoints duplicate_labels same_mountpoint and same_label errors must be suppressed when this special case is detected package partman-btrfs - commit.d/ format_btrfs * must do a pre-screening of all filesystem specs and identify those that need RAID * format the normal filesystems first, and the RAID ones in a second pass fstab.d/ btrfs * must do a pre-screening of all filesystem specs and identify those that need RAID * output the normal filesystems first * for the RAID filesystems, must mount by UUID= syntax (due to bug #612402) http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612402 * one possible technique is to just check UUID of each filesystem, and parse the resulting fstab output via uniq -- 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/503f95e2.50...@pocock.com.au
Re: Install Debian Squeeze on Alix 2d2 over Serial Console
On Thu, Aug 30, 2012 at 11:35:23AM +0200, Jonas Meier wrote: > dear list > > I want to install Debian Squeeze on a Alix 2d2 > (http://www.pcengines.ch/alix2d2.htm). This little Box only boots from a > CF-Card or PXE and can only be managed over a serial interface. > > So I installed tfpd-hpa on an other server, downloaded the Debian Netboot > from > (ftp://ftp.ch.debian.org/debian/dists/squeeze/main/installer-i386/current/images/netboot/) > and configured the daemon. In "pxelinux.cfg/default" I added the line > "serial 0 38400". Now when I started the Alix board and booted it over PXE I > came to the menu, where I could choose the normal or the expert installation. > No matter which one I choose, I always had the error "Undefined video mode > number: 314". Here a copy of the output: > - > Loading debian-installer/i386/linux. > Loading debian-installer/i386/initrd.gz.ready. > Probing EDD (edd=off to disable)... ok > Undefined video mode number: 314 > Press to see video modes available, to continue, or wait 30 > sec > Mode: Resolution: Type: ER to boot or TAB to edit a menu entry > 0 F00 80x25 CGA/MDA/HGC > - > It doesn't matter what I do, nothing happens. How can I define that it should > use again the serial console and not an other video mode? If it doesn't have video but only serial, then you probably have to pass an option to the kernel when booting to disable the normal video. Something like: console=ttyS0,38400 video=off I didn't look them up to check that I remembered them right. -- Len Sorensen -- 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/20120830145506.gt1...@csclub.uwaterloo.ca
Install Debian Squeeze on Alix 2d2 over Serial Console
dear list I want to install Debian Squeeze on a Alix 2d2 (http://www.pcengines.ch/alix2d2.htm). This little Box only boots from a CF-Card or PXE and can only be managed over a serial interface. So I installed tfpd-hpa on an other server, downloaded the Debian Netboot from (ftp://ftp.ch.debian.org/debian/dists/squeeze/main/installer-i386/current/images/netboot/) and configured the daemon. In "pxelinux.cfg/default" I added the line "serial 0 38400". Now when I started the Alix board and booted it over PXE I came to the menu, where I could choose the normal or the expert installation. No matter which one I choose, I always had the error "Undefined video mode number: 314". Here a copy of the output: - Loading debian-installer/i386/linux. Loading debian-installer/i386/initrd.gz.ready. Probing EDD (edd=off to disable)... ok Undefined video mode number: 314 Press to see video modes available, to continue, or wait 30 sec Mode: Resolution: Type: ER to boot or TAB to edit a menu entry 0 F00 80x25 CGA/MDA/HGC - It doesn't matter what I do, nothing happens. How can I define that it should use again the serial console and not an other video mode? Regards Jonas _ Jonas Meier MSW Informatikdienste jonas.me...@msw.ch -- 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/503f4ffb021eb...@gwia.msw.ch
disable l2 cache on kirkwood devices (workaround #658904)
A while back a bug was discovered in u-boot on the kirkwood platform
which prevented modern kernels from booting[0]. Specifically u-boot was
failing to disable the L2 cache which interacts badly with kernels using
CONFIG_ARM_PATCH_PHYS_VIRT. CONFIG_ARM_PATCH_PHYS_VIRT relates to
running a single kernel image on multiple machines and so disabling it
was not really an option.
It's not immediately obvious which kirkwood platforms are effected,
since the only real way to tell is to try it (since the u-boot shipped
by the factory on these boards are many and varied). From the bug
reports we know that Dockstar, Shivaplug, Gruruplug and Dreamplug have
this issue. I've got a QNAP device which I indend to try as soon as I
can solder a serial console together[1].
u-boot has been fixed and the fix is available in Wheezy. However not
all kirkwood platforms have a serial console or a JTAG port so there is
a chance that upgrade will either brick the board (due to a botched
u-boot upgrade) or fail to boot the new kernel with no easy way to
recover (due to a lack of serial console to roll back).
I've just tried injecting the following onto the head of the zImage (in
a similar manner to flash-kernel's set_machine_id function):
# disable l2 caches
devio "wl 0xee3f3f11,4" # mrc 15, 1, r3, cr15, cr1, {0}
devio "wl 0xe3c33501,4" # bic r3, r3, #0x40
devio "wl 0xee2f3f11,4" # mcr 15, 1, r3, cr15, cr1, {0}
# flush caches
devio "wl 0xe3a03000,4" # mov r3, #0
devio "wl 0xee073f17,4" # mcr 15, 0, r3, cr7, cr7, {0}
This works around the issue on my dreamplug (this is effectively the
same code sequence as what the u-boot fix does).
I can see two ways of distributing this fix. Either a kernel patch gated
on CONFIG_ARCH_KIRKWOOD to some early bit of code or use devio in
flash-kernel + the installer build.
If it's to be flash kernel then I suppose gating on the kernel flavour =
"kirkwood" would be wise, but we could also gate on a per machine basis.
In this case we would also need to duplicate the injection in the
installer build.
My only concern is whether this code sequence is valid on all the
kirkwood platforms which we support. I'd like to assume that the
processors were all similar enough but I don't really know.
Anybody have any thoughts on the best way to go about this or the sanity
of the approach generally?
Ian.
[0]
- http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658904
- http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658759
- http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685713
[1] Not a skill which I am renowned for possessing, so we'll see when
that actually happens ;-)
--
Ian Campbell
Current Noise: Anathema - Lightning Song
any new sendmail hole I have to fix before going on vacations?
-- Seen on #Linux
--
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/1346319361.27277.52.ca...@zakaz.uk.xensource.com
Bug#686226: [FATAL] Wheezy Debian installer fails on Qosmio hardware
Package: debian-installer Version: 20120712 Severity: serious Hi, I'm trying to install Debian from Wheezy DVD (BETA1) on amd64. (Qosmio X300-130 laptop). Actual Result: It fails during the "Detect network hardware" phase. Ie. stops progressing, and no way to skip this stage. and in console (F4) it complains about the lack of iwl Intel Wireless firmware and missing eth1394 (Firewire Ethernet). Expected Result: Should proceed without problematic firmware or drivers. Debian 6.0 works great on this same hardware. (installed from amd64 DVD) -- -Alexey Eromenko "Technologov" -- 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/CAOJ6w=EKwrniVrHngdjH0B_cSsKKjSe5Gz+DnJ6Nfs=5tud...@mail.gmail.com
