Debian installer build: failed or old builds

2013-08-03 Thread Daily build aggregator
Debian installer build overview
---

Failed or old builds:

* OLD BUILD:ia64 May 26 00:12 buildd@alkman build_cdrom 
http://d-i.debian.org/daily-images/ia64/daily/build_cdrom.log

* OLD BUILD:ia64 May 26 00:16 buildd@alkman build_netboot 
http://d-i.debian.org/daily-images/ia64/daily/build_netboot.log

* FAILED BUILD: kfreebsd-amd64 Aug 04 00:34 buildd@fano build_netboot 

http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot.log

* FAILED BUILD: kfreebsd-amd64 Aug 04 00:36 buildd@fano build_netboot-9 

http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot-9.log

* FAILED BUILD: kfreebsd-amd64 Aug 04 00:40 buildd@fano build_netboot-gtk 

http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot-gtk.log

* FAILED BUILD: kfreebsd-amd64 Aug 04 00:43 buildd@fano build_netboot-gtk-9 

http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot-gtk-9.log

* FAILED BUILD: kfreebsd-i386 Aug 04 00:34 buildd@finzi build_netboot 

http://d-i.debian.org/daily-images/kfreebsd-i386/daily/build_netboot.log

* FAILED BUILD: kfreebsd-i386 Aug 04 00:36 buildd@finzi build_netboot-9 

http://d-i.debian.org/daily-images/kfreebsd-i386/daily/build_netboot-9.log

* FAILED BUILD: powerpc Aug 04 00:01 buildd@praetorius build_powerpc_netboot 

http://d-i.debian.org/daily-images/powerpc/daily/build_powerpc_netboot.log

* FAILED BUILD: powerpc Aug 04 00:02 buildd@praetorius 
build_powerpc_netboot-gtk 

http://d-i.debian.org/daily-images/powerpc/daily/build_powerpc_netboot-gtk.log

* FAILED BUILD: powerpc Aug 04 00:05 buildd@praetorius build_powerpc64_netboot 

http://d-i.debian.org/daily-images/powerpc/daily/build_powerpc64_netboot.log

* FAILED BUILD: powerpc Aug 04 00:05 buildd@praetorius 
build_powerpc64_netboot-gtk 

http://d-i.debian.org/daily-images/powerpc/daily/build_powerpc64_netboot-gtk.log


Totals: 82 builds (10 failed, 2 old)


-- 
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/e1v5mg5-0004yk...@ravel.debian.org



grub issues

2013-08-03 Thread Miles Fidelman


Hi Folks,

Just installed Debian Wheezy onto a remote server, and encountered some
problems getting grub to boot properly.  I Figured it out through trial
and error, but it's pretty clear that the stock install did not configure
grub properly.

So... note sure if this is a special case that needs special handling (perhaps
better documentation), or a bug (in which case a bug report is in order). Right
now, just trying to understand what happened.

Note: Note, most of my familiarity is with grub-legacy, this is
my first time working through things with grub 2.

Step by step:

- remote install - starting w/ IPMI lan console, continuing w/ SSH

- PXEboot into the installer

- partition and configure 4 disk drives into md devices for boot, swap,
root, LVM

- USB drive shows up as /dev/sda during install - with hard drives as
/dev/sdb-e

- after install hard drives show up as /dev/sda-d, usb drive as /dev/sde

- pretty standard install process until the end

- between the RAID devices and the USB stick as /dev/sda - had to fiddle a
bit to install MBR into hard drives

- attempted to boot, end up at grub prompt on the remote console

- typed "boot" and got "error: no kernel loaded"




- did some googling, based on what I found, tried the following (from
the grub> prompt)
-- set prefix=(md/0)/boot/grub
-- set root=(md/2)
-- boot
-- still get "error: no kernel loaded"

-- noted that ls (md/0)/ showed System.map, config-, vmlinuz, initrd as
well as grub
-- tried the command "linux (md/0)/vmlinuz..." - let it autocomplete the
full file name
- got "error: file not found"  #THIS IS CONFUSING - SINCE LS AND
AUTOCOMPLETE FOUND THE FILE"

-- insmod normal
-- insmod
-- now I get a boot screen, and after the timeout, everything booted
normally

- reboot brought be back to the grub> prompt

- this time, after booting:
-- ran update-grub and grub-install on all four drives, and and on
/dev/md0 (boot) and /dev/md2 (root) for good measure
-- rebooted - everything came up fine So problem is solved but 2 questions

So... it seems like the installer is doing something different, and wrong, as
compared to update-grub and grub-install.
- could be a bug
- could be that I needed to do something special during the install procedure

Perhaps somebody could shed some light on what's going on, and if this warrants
a bug report or documentation input, point me in the right direction to do so?

Thanks!

Miles Fidelman

p.s So far - no input whatever from either the debian-user list or the 
help-grub list.



--
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/51fd8787.5050...@meetinghouse.net



Bug#718659: installer does not find usb pendrives as cdrom sources

2013-08-03 Thread Josep Lladonosa
Package: installation-reports

Boot method: iso image of testing installer in a USB pendrive.
Image version: 
http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-xfce-CD-1.iso
Date: 2013-07-29 07:21

Machine: Lenovo ThinkPad E130
Processor: i3
Memory: 8 GiB
Partitions: none yet (sda disk, sdb mSATA SSD)


Comments/Problems:

Installer starts but in the finding cdrom stage, it cannot find any
source. Having a look at the /dev folder, no disk/partition as
/dev/sdc /dev/sdc? can be found (although they are seen as usb
drive/partitions in the /sys/bus/usb/... hierarchy.

I add also that I have opened a wish in the wishlist bug system asking
for the inclusion of bcache-tools and bcache module in the kernel of
the installer...


-- 
--
Salutacions...Josep
--


-- 
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/CAPBO7TZszfBN506jCvmbetu0AUSSGnOWemgmn4ODBG9rL=e...@mail.gmail.com



Bug#709456: Same behaviour with current installer from sid

2013-08-03 Thread Bernhard
Hello,

Only for your information:
The same behaviour is shown with current installer from sid.

I tried to format the partitions with btrfs during installation.

The lzo library is missing.

Best regards
Bernhard



signature.asc
Description: This is a digitally signed message part


Bug#718634: marked as done (Installation was successfully on old Asus Laptop)

2013-08-03 Thread Debian Bug Tracking System
Your message dated Sat, 3 Aug 2013 16:09:22 +0200
with message-id <20130803140922.gj4...@mykerinos.kheops.frmug.org>
and subject line Re: Bug#718634: Installation was successfully on old Asus 
Laptop
has caused the Debian Bug report #718634,
regarding Installation was successfully on old Asus Laptop
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.)


-- 
718634: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718634
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports

Boot method: USB-Stick
Image version: Self-made ISO image with actual installer from sid
Date: 2013-08-03

Machine: ASUS Laptop Z7750
Processor: Pentium M @ 1,6GHz
Memory: 512MB
Partitions:

> DateisystemTyp  1K-Blöcke 
> Benutzt Verfügbar Verw% Eingehängt auf
> rootfs rootfs14286320 
> 4626924   8927032   35% /
> udev   devtmpfs 10240 
>   0 102400% /dev
> tmpfs  tmpfs51372 
> 272 511001% /run
> /dev/disk/by-uuid/1c5dc4e8-8dcc-4205-8ad4-3b4918767dc8 ext4  14286320 
> 4626924   8927032   35% /
> tmpfs  tmpfs 5120 
>   0  51200% /run/lock
> tmpfs  tmpfs   297900 
>   02979000% /run/shm
> /dev/sda6  ext4  42172672   
> 49268  399744921% /home

Output of lspci -knn:


> 00:00.0 Host bridge [0600]: Intel Corporation 82855PM Processor to I/O 
> Controller [8086:3340] (rev 21)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:186a]
>   Kernel driver in use: agpgart-intel
> 00:01.0 PCI bridge [0604]: Intel Corporation 82855PM Processor to AGP 
> Controller [8086:3341] (rev 21)
> 00:1d.0 USB controller [0c03]: Intel Corporation 82801DB/DBL/DBM 
> (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 [8086:24c2] (rev 03)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:1869]
>   Kernel driver in use: uhci_hcd
> 00:1d.1 USB controller [0c03]: Intel Corporation 82801DB/DBL/DBM 
> (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 [8086:24c4] (rev 03)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:1869]
>   Kernel driver in use: uhci_hcd
> 00:1d.2 USB controller [0c03]: Intel Corporation 82801DB/DBL/DBM 
> (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 [8086:24c7] (rev 03)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:1869]
>   Kernel driver in use: uhci_hcd
> 00:1d.7 USB controller [0c03]: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) 
> USB2 EHCI Controller [8086:24cd] (rev 03)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:1868]
>   Kernel driver in use: ehci-pci
> 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge 
> [8086:2448] (rev 83)
> 00:1f.0 ISA bridge [0601]: Intel Corporation 82801DBM (ICH4-M) LPC Interface 
> Bridge [8086:24cc] (rev 03)
>   Kernel driver in use: lpc_ich
> 00:1f.1 IDE interface [0101]: Intel Corporation 82801DBM (ICH4-M) IDE 
> Controller [8086:24ca] (rev 03)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:1869]
>   Kernel driver in use: ata_piix
> 00:1f.3 SMBus [0c05]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) 
> SMBus Controller [8086:24c3] (rev 03)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:1869]
>   Kernel driver in use: i801_smbus
> 00:1f.5 Multimedia audio controller [0401]: Intel Corporation 82801DB/DBL/DBM 
> (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller [8086:24c5] (rev 03)
>   Subsystem: ASUSTeK Computer Inc. M2400N/M6800N laptop [1043:1713]
>   Kernel driver in use: snd_intel8x0
> 00:1f.6 Modem [0703]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) 
> AC'97 Modem Controller [8086:24c6] (rev 03)
>   Subsystem: ASUSTeK Computer Inc. M6800N [1043:1826]
>   Kernel driver in use: snd_intel8x0m
> 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
> [AMD/ATI] RV350/M10 [Mobility Radeon 9600 PRO Turbo] [1002:4e50]
>   Subsystem: ASUSTeK Computer Inc. Device [1043:1772]
>   Kernel driver in use: radeon
> 02:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5788 
> Gigabit Ethernet [14e4:169c] (rev 03)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:1735]
>   Kernel driver in use: tg3
> 02:01.0 CardBus bridge [0607]: Ricoh Co Ltd RL5c476 II [1180:0476] (rev ac)
>   Subsystem: ASUSTeK Computer Inc. Device [

Bug#718633: marked as done (Installation was successfully at AMD A10-5700)

2013-08-03 Thread Debian Bug Tracking System
Your message dated Sat, 3 Aug 2013 16:08:50 +0200
with message-id <20130803140850.gi4...@mykerinos.kheops.frmug.org>
and subject line Re: Bug#718633: Installation was successfully at AMD A10-5700
has caused the Debian Bug report #718633,
regarding Installation was successfully at AMD A10-5700
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.)


-- 
718633: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718633
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports

Boot method: USB-Stick
Image version: Self-made ISO image with actual installer from sid
Date: 2013-08-03

Machine: Self-made Desktop PC
Processor: AMD A10-5700 @ 3,4GHz
Memory: 4GB
Partitions:

> DateisystemTyp  1K-Blöcke 
> Benutzt Verfügbar Verw% Eingehängt auf
> rootfs rootfs14286320 
> 4717540   8836416   35% /
> udev   devtmpfs 10240 
>   0 102400% /dev
> tmpfs  tmpfs   387376 
> 3683870081% /run
> /dev/disk/by-uuid/1a1ec68c-74be-48a0-924f-a2c0bad5fa4d ext4  14286320 
> 4717540   8836416   35% /
> tmpfs  tmpfs 5120 
>   0  51200% /run/lock
> tmpfs  tmpfs   969920 
>   09699200% /run/shm
> /dev/sda6  ext4  99867104   
> 61308  947260921% /home

Output of lspci -knn (or lspci -nn):

> 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
> (Models 10h-1fh) Processor Root Complex [1022:1410]
>   Subsystem: ASUSTeK Computer Inc. Device [1043:8526]
> 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
> [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901]
>   Subsystem: ASUSTeK Computer Inc. Device [1043:8526]
>   Kernel driver in use: radeon
> 00:01.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Trinity 
> HDMI Audio Controller [1002:9902]
>   Subsystem: ASUSTeK Computer Inc. Device [1043:8526]
>   Kernel driver in use: snd_hda_intel
> 00:10.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> XHCI Controller [1022:7812] (rev 03)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:8527]
>   Kernel driver in use: xhci_hcd
> 00:10.1 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> XHCI Controller [1022:7812] (rev 03)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:8527]
>   Kernel driver in use: xhci_hcd
> 00:11.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA 
> Controller [AHCI mode] [1022:7801] (rev 40)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:8527]
>   Kernel driver in use: ahci
> 00:12.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> OHCI Controller [1022:7807] (rev 11)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:8527]
>   Kernel driver in use: ohci_hcd
> 00:12.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> EHCI Controller [1022:7808] (rev 11)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:8527]
>   Kernel driver in use: ehci-pci
> 00:13.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> OHCI Controller [1022:7807] (rev 11)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:8527]
>   Kernel driver in use: ohci_hcd
> 00:13.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> EHCI Controller [1022:7808] (rev 11)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:8527]
>   Kernel driver in use: ehci-pci
> 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller 
> [1022:780b] (rev 14)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:8527]
>   Kernel driver in use: piix4_smbus
> 00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] FCH Azalia 
> Controller [1022:780d] (rev 01)
>   Subsystem: ASUSTeK Computer Inc. F2A85-M Series [1043:8444]
>   Kernel driver in use: snd_hda_intel
> 00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge 
> [1022:780e] (rev 11)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:8527]
> 00:14.4 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] FCH PCI Bridge 
> [1022:780f] (rev 40)
> 00:15.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Hudson PCI to 
> PCI bridge (PCIE port 0) [1022:43a0]
>   Kernel dri

Re: D-I build failures for kfreebsd-amd64....

2013-08-03 Thread Christian PERRIER
Quoting Steven Chamberlain (ste...@pyro.eu.org):

> Yes, for grub2 >> 2.0 we just need to drop pxecmd.  Sort of related to

So, you mean drop it from there?

installer/build/config/hurd.cfg:GRUB_MODULES_PXE=pxe pxecmd



signature.asc
Description: Digital signature


Bug#718634: Installation was successfully on old Asus Laptop

2013-08-03 Thread Bernhard
Package: installation-reports

Boot method: USB-Stick
Image version: Self-made ISO image with actual installer from sid
Date: 2013-08-03

Machine: ASUS Laptop Z7750
Processor: Pentium M @ 1,6GHz
Memory: 512MB
Partitions:

> DateisystemTyp  1K-Blöcke 
> Benutzt Verfügbar Verw% Eingehängt auf
> rootfs rootfs14286320 
> 4626924   8927032   35% /
> udev   devtmpfs 10240 
>   0 102400% /dev
> tmpfs  tmpfs51372 
> 272 511001% /run
> /dev/disk/by-uuid/1c5dc4e8-8dcc-4205-8ad4-3b4918767dc8 ext4  14286320 
> 4626924   8927032   35% /
> tmpfs  tmpfs 5120 
>   0  51200% /run/lock
> tmpfs  tmpfs   297900 
>   02979000% /run/shm
> /dev/sda6  ext4  42172672   
> 49268  399744921% /home

Output of lspci -knn:


> 00:00.0 Host bridge [0600]: Intel Corporation 82855PM Processor to I/O 
> Controller [8086:3340] (rev 21)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:186a]
>   Kernel driver in use: agpgart-intel
> 00:01.0 PCI bridge [0604]: Intel Corporation 82855PM Processor to AGP 
> Controller [8086:3341] (rev 21)
> 00:1d.0 USB controller [0c03]: Intel Corporation 82801DB/DBL/DBM 
> (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 [8086:24c2] (rev 03)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:1869]
>   Kernel driver in use: uhci_hcd
> 00:1d.1 USB controller [0c03]: Intel Corporation 82801DB/DBL/DBM 
> (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 [8086:24c4] (rev 03)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:1869]
>   Kernel driver in use: uhci_hcd
> 00:1d.2 USB controller [0c03]: Intel Corporation 82801DB/DBL/DBM 
> (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 [8086:24c7] (rev 03)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:1869]
>   Kernel driver in use: uhci_hcd
> 00:1d.7 USB controller [0c03]: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) 
> USB2 EHCI Controller [8086:24cd] (rev 03)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:1868]
>   Kernel driver in use: ehci-pci
> 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge 
> [8086:2448] (rev 83)
> 00:1f.0 ISA bridge [0601]: Intel Corporation 82801DBM (ICH4-M) LPC Interface 
> Bridge [8086:24cc] (rev 03)
>   Kernel driver in use: lpc_ich
> 00:1f.1 IDE interface [0101]: Intel Corporation 82801DBM (ICH4-M) IDE 
> Controller [8086:24ca] (rev 03)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:1869]
>   Kernel driver in use: ata_piix
> 00:1f.3 SMBus [0c05]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) 
> SMBus Controller [8086:24c3] (rev 03)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:1869]
>   Kernel driver in use: i801_smbus
> 00:1f.5 Multimedia audio controller [0401]: Intel Corporation 82801DB/DBL/DBM 
> (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller [8086:24c5] (rev 03)
>   Subsystem: ASUSTeK Computer Inc. M2400N/M6800N laptop [1043:1713]
>   Kernel driver in use: snd_intel8x0
> 00:1f.6 Modem [0703]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) 
> AC'97 Modem Controller [8086:24c6] (rev 03)
>   Subsystem: ASUSTeK Computer Inc. M6800N [1043:1826]
>   Kernel driver in use: snd_intel8x0m
> 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
> [AMD/ATI] RV350/M10 [Mobility Radeon 9600 PRO Turbo] [1002:4e50]
>   Subsystem: ASUSTeK Computer Inc. Device [1043:1772]
>   Kernel driver in use: radeon
> 02:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5788 
> Gigabit Ethernet [14e4:169c] (rev 03)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:1735]
>   Kernel driver in use: tg3
> 02:01.0 CardBus bridge [0607]: Ricoh Co Ltd RL5c476 II [1180:0476] (rev ac)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:1864]
>   Kernel driver in use: yenta_cardbus
> 02:01.1 CardBus bridge [0607]: Ricoh Co Ltd RL5c476 II [1180:0476] (rev ac)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:1864]
>   Kernel driver in use: yenta_cardbus
> 02:01.2 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd R5C552 IEEE 1394 Controller 
> [1180:0552] (rev 04)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:1867]
>   Kernel driver in use: firewire_ohci
> 02:02.0 Network controller [0280]: Intel Corporation PRO/Wireless 2200BG 
> [Calexico2] Network Connection [8086:4220] (rev 05)
>   Subsystem: Intel Corporation WM3B2300BG Mini-PCI Card [8086:2701]
>   Kernel driver in use: ipw2200

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:   

Bug#718633: Installation was successfully at AMD A10-5700

2013-08-03 Thread Bernhard
Package: installation-reports

Boot method: USB-Stick
Image version: Self-made ISO image with actual installer from sid
Date: 2013-08-03

Machine: Self-made Desktop PC
Processor: AMD A10-5700 @ 3,4GHz
Memory: 4GB
Partitions:

> DateisystemTyp  1K-Blöcke 
> Benutzt Verfügbar Verw% Eingehängt auf
> rootfs rootfs14286320 
> 4717540   8836416   35% /
> udev   devtmpfs 10240 
>   0 102400% /dev
> tmpfs  tmpfs   387376 
> 3683870081% /run
> /dev/disk/by-uuid/1a1ec68c-74be-48a0-924f-a2c0bad5fa4d ext4  14286320 
> 4717540   8836416   35% /
> tmpfs  tmpfs 5120 
>   0  51200% /run/lock
> tmpfs  tmpfs   969920 
>   09699200% /run/shm
> /dev/sda6  ext4  99867104   
> 61308  947260921% /home

Output of lspci -knn (or lspci -nn):

> 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
> (Models 10h-1fh) Processor Root Complex [1022:1410]
>   Subsystem: ASUSTeK Computer Inc. Device [1043:8526]
> 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
> [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901]
>   Subsystem: ASUSTeK Computer Inc. Device [1043:8526]
>   Kernel driver in use: radeon
> 00:01.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Trinity 
> HDMI Audio Controller [1002:9902]
>   Subsystem: ASUSTeK Computer Inc. Device [1043:8526]
>   Kernel driver in use: snd_hda_intel
> 00:10.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> XHCI Controller [1022:7812] (rev 03)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:8527]
>   Kernel driver in use: xhci_hcd
> 00:10.1 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> XHCI Controller [1022:7812] (rev 03)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:8527]
>   Kernel driver in use: xhci_hcd
> 00:11.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA 
> Controller [AHCI mode] [1022:7801] (rev 40)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:8527]
>   Kernel driver in use: ahci
> 00:12.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> OHCI Controller [1022:7807] (rev 11)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:8527]
>   Kernel driver in use: ohci_hcd
> 00:12.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> EHCI Controller [1022:7808] (rev 11)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:8527]
>   Kernel driver in use: ehci-pci
> 00:13.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> OHCI Controller [1022:7807] (rev 11)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:8527]
>   Kernel driver in use: ohci_hcd
> 00:13.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> EHCI Controller [1022:7808] (rev 11)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:8527]
>   Kernel driver in use: ehci-pci
> 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller 
> [1022:780b] (rev 14)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:8527]
>   Kernel driver in use: piix4_smbus
> 00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] FCH Azalia 
> Controller [1022:780d] (rev 01)
>   Subsystem: ASUSTeK Computer Inc. F2A85-M Series [1043:8444]
>   Kernel driver in use: snd_hda_intel
> 00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge 
> [1022:780e] (rev 11)
>   Subsystem: ASUSTeK Computer Inc. Device [1043:8527]
> 00:14.4 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] FCH PCI Bridge 
> [1022:780f] (rev 40)
> 00:15.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Hudson PCI to 
> PCI bridge (PCIE port 0) [1022:43a0]
>   Kernel driver in use: pcieport
> 00:15.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Hudson PCI to 
> PCI bridge (PCIE port 1) [1022:43a1]
>   Kernel driver in use: pcieport
> 00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
> (Models 10h-1fh) Processor Function 0 [1022:1400]
> 00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
> (Models 10h-1fh) Processor Function 1 [1022:1401]
> 00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
> (Models 10h-1fh) Processor Function 2 [1022:1402]
> 00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
> (Models 10h-1fh) Processor Function 3 [1022:1403]
>   Kernel driver in use: k10temp
> 00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
> (Models 10h-1fh) Processor Function 4 [1022:1404]
> 00:18.5 Host bridge 

Bug#718632: chroot fails due to incorrect path on Arch Linux

2013-08-03 Thread Heinrich Schuchardt

Package: debootstrap
Version: 1.0.48+deb7u1
Severity: normal

Dear maintainer,

I tried to install a Debian chroot on an armhf Arch Linux system.

/usr/sbin/debootstrap --variant=minbase --arch armhf wheezy 
debian-chroot http://ftp.de.debian.org/debian

failed when reaching
chroot /home/user/temp/debian-chroot mount -t proc proc /proc
because command mount was not found.

The reason is that on Arch Linux /bin is not in the path. And chroot 
inherits this path.


When calling chroot the variable PATH should be set explicitly and not 
be inherited.


A good idea would be to use chroot -i to clear all environment variables 
and to set explicitly those that are needed like PATH.


Best regards

Heinrich Schuchardt


--
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/51fce7f2.8020...@gmx.de



Re: D-I build failures for kfreebsd-amd64....

2013-08-03 Thread Steven Chamberlain
Hello,

On 03/08/13 07:41, Christian PERRIER wrote:
> grub-mkimage: error: cannot stat `/usr/lib/grub/i386-pc/pxecmd.mod': No such 
> file or directory.

> It's like several weeks that this is happening. Anyone with an  idea
> how to fix this?

Yes, for grub2 >> 2.0 we just need to drop pxecmd.  Sort of related to
this, KiBi mentioned it "could be nice" to wait until after it enters
testing[0] but that still hasn't really happened.

[0]: http://lists.debian.org/2013072913.ga9...@mraw.org

I think jessie d-i images might actually still work without pxecmd and
the old grub2 (we might only lose the pxe_unload command which we don't
use anyway);  in that case I won't have to alter Build-Depends and can
fix it without waiting for grub2 to migrate.

It's quite important to resume building the sid images because I know
there's at least one more bug to be fixed in grub2 >> 2.0 (#711799)
affecting PXE booting.

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/51fcd858.9070...@pyro.eu.org