Re: [RFC] Listing USB devices in hardware-summary

[Christian Perrier]

Quoting Frans Pop (elen...@planet.nl):
> Because /proc/bus/usb/devices is going away in 2.6.31 (patch got merged in 
> kernel upstream mainline today), we are going to need an alternative way 
> to list USB devices in the hardware summary.
> 
> The file is being moved to debugfs, but I don't think mounting debugfs 
> just to get this info is the correct solution for us.
> 
> Instead I propose to add the attached script in installation-report.


I tried your script on a few machines I have root access to (incl. my
own laptops). The same devices are reported.

I have one question, though:

Why is "Manufacturer:" reporting something like "Linux 2.6.29-1-686
uhci_hcd". There's the same in what you reported in indeed in
/proc/bus/usb/devices but your examples shows clearer things such as
"Hewlett Packard" when showing the output of /proc/bus/usb/devices.

I also wonder if it could be possible to get the equivalent of
"Product". There seem to be useful information there, isn't it?




signature.asc
Description: Digital signature

Bug#533492: debian-installer not detecting drives using mesh SCSI driver

[Charlie Sirchuk]

Package: debian-installer
Version: 20090123lenny1

When I try to install powerpc testing om my Beige G3, the installer fails to
detect my SCSI hard drive. The mesh driver appears to be loading during boot
and the harddrive is visible as /dev/sda1-7. When I use the lenny installer,
the drive is recognized correctly.

Bug#516347: debian-installer: guided-with-lvm no longer allows multiple primary partition

[Julio C. Ortega]

> Yup, this is biting me too... Sorry for the long stream-of-conscious 
> report here, but I wrote as I worked through this issue and it shows. ;) 
> I don't know what someone may find important or not.
> 
> It's an odd bug though. When I create a small /boot partition as the 
> first item in the recipe, it rolls right along.
> [.] 
> 
> part_start = 19535040
> part_end   = 117212774 <--- more sectors than the disk has
> 
> The formula used in parted_server.c for calculating the part_end value is:
> 
> 1824: part_start = range_start / PED_SECTOR_SIZE_DEFAULT;
> 1825: part_end = (range_start + length) / PED_SECTOR_SIZE_DEFAULT;
> 
> So if there is a bounds check just after this code to keep the part_end 
> value at less than the range_end it should work (see attached patch).
> 
> I'll dig some more in the partman-auto-lvm package and see if the 
> calculations are borked there. Based upon the other bug reports claiming 
> this is not an lvm specific issue, I bet the size/offset calculations 
> are being done in some shared resource.
> 
> Does anyone know how to force the debian installer to use an unsigned 
> udeb source? I have a local debian mirror for netboot installs, but 
> since deb started using signed installer packages I've found it 
> difficult to replace or override the default installer udebs.
> 
> Tony
> 
> [parted_server.c.diff (text/plain, inline)]
> 
> --- parted_server.c.orig2009-06-17 17:08:04.0 +
> +++ parted_server.c 2009-06-17 16:34:12.0 +
> @@ -1823,6 +1823,10 @@
>  } else if (!strcasecmp(position, "beginning")) {
>  part_start = range_start / PED_SECTOR_SIZE_DEFAULT;
>  part_end = (range_start + length) / PED_SECTOR_SIZE_DEFAULT;
> +// Truncate the partition end to fit the maximum disk size
> +if ( part_end > ( range_end / PED_SECTOR_SIZE_DEFAULT ) ) {
> +  part_end = ( range_end / PED_SECTOR_SIZE_DEFAULT );
> +}
>  } else if (!strcasecmp(position, "end")) {
>  part_start = (range_end - length) / PED_SECTOR_SIZE_DEFAULT;
>  part_end = ((range_end - PED_SECTOR_SIZE_DEFAULT + 1)

Greetings all.

I've hit this bug also.

I've also tried the patch from Anthony to no avail.

I've been trying to make a recipe for a PowerPC based IBM Machine.
keeping "/" from entering the LVM, because Debian (and other distros
too) have major bugs when "/" it's inside it (in this architecture). So
there's no point on making only a "/boot" partition that stays out of it.

I've made it work at last making these changes in
lib/partman/lib/auto-lvm.sh: (partman-auto-lvm UDEB)

17c17
  echo "$scheme${NL}100 1000 -1 ext3 \$primary{ } method{ $method }"
---
  echo "$scheme${NL}100 1000 -1 ext3 method{ $method }"


As we know, device mapper doesn't care if it's physical volume it's on a
primary or a logical partition. He is there only to activate it(/them).

I've also included in this test installation (made a couple of them,
successfully) a partman-base modified UDEB with anthony's patch (but, as
stated earlier, it's not making difference)

Thanks to anthony for keeping alive this bug, and for the proposed
patch, else i couldn't have solved it.

The recipe im using is below.

d-i partman-auto/expert_recipe string \
  boot-root ::\
  8 1 1 prep  \
  $primary{ } \
  $bootable{ }\
  method{ prep }  \
  .   \
  8192 1 8192 ext3\
  $primary{ } \
  method{ format } format{ }  \
  use_filesystem{ } filesystem{ ext3 }\
  mountpoint{ / } \
  .   \
  64 512 300% linux-swap  \
  $lvmok{ }   \
  method{ swap } format{ }\
  .   \
  500 1 -1 ext3   \
  $lvmok{ }   \
  $defaultignore{ }   \
  method{ format } format{ }  \
  use_filesystem{ } filesystem{ ext3 }\
  mountpoint{ /srv }  \
  .


Again. Thanks, and have a nice day.

-- 

Julio C. Ortega
Equipo de Infraestructura
ONUVA | Integración de Sistemas



signature.asc
Description: OpenPGP digital

[RFC] Listing USB devices in hardware-summary

[Frans Pop]

Because /proc/bus/usb/devices is going away in 2.6.31 (patch got merged in 
kernel upstream mainline today), we are going to need an alternative way 
to list USB devices in the hardware summary.

The file is being moved to debugfs, but I don't think mounting debugfs 
just to get this info is the correct solution for us.

Instead I propose to add the attached script in installation-report.
It is based on a script I found on the linux-usb mailing list [0] which 
reads sysfs to provide info similar to the /p/b/u/devices file.
I've simplified the script and rearranged its output because IMO a lot of 
the info in /p/b/u/devices is not all that relevant for us [1].

Below some examples for comparison of current and proposed info. The full 
output of the script for my notebook is attached.

Cheers,
FJP

[0] http://article.gmane.org/gmane.linux.usb.general/16828
[1] I've kept the serial number field for now; should we drop that too?


Example content from /p/b/u/devices
===
T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480 MxCh= 4
B:  Alloc=  0/800 us ( 0%), #Int=  4, #Iso=  0
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev= 2.06
S:  Manufacturer=Linux 2.6.30 ehci_hcd
S:  Product=EHCI Host Controller
S:  SerialNumber=:00:1a.7
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

T:  Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 44 Spd=480 MxCh= 4
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=02 MxPS=64 #Cfgs=  1
P:  Vendor=0424 ProdID=2504 Rev= 0.01
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  2mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=01 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   1 Ivl=256ms
I:* If#= 0 Alt= 1 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=02 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   1 Ivl=256ms

T:  Bus=01 Lev=02 Prnt=44 Port=01 Cnt=01 Dev#= 45 Spd=12  MxCh= 0
D:  Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=03f0 ProdID=3102 Rev= 1.00
S:  Manufacturer=Hewlett-Packard
S:  Product=PhotoSmart P1100
S:  SerialNumber=MX01B1B1HRID
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr=  2mA
I:  If#= 0 Alt= 0 #EPs= 2 Cls=07(print) Sub=01 Prot=01 Driver=usblp
E:  Ad=81(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
I:* If#= 0 Alt= 1 #EPs= 2 Cls=07(print) Sub=01 Prot=02 Driver=usblp
E:  Ad=01(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms

Output from script for the same devices
===
Bus 001 Device 001: EHCI Host Controller [1d6b:0002]
   Class 09(hub) Subclass 00 Protocol 00
   Manufacturer: Linux 2.6.30 ehci_hcd
   SerialNumber: :00:1a.7
   Interface 00: Class 09(hub) Subclass 00 Protocol 00 Driver hub

Bus 001 Device 044: EHCI Host Controller [0424:2504]
   Class 09(hub) Subclass 00 Protocol 02
   Interface 00: Class 09(hub) Subclass 00 Protocol 02 Driver hub

Bus 001 Device 045: PhotoSmart P1100 [03f0:3102]
   Class 00(>ifc) Subclass 00 Protocol 00
   Manufacturer: Hewlett-Packard
   SerialNumber: MX01B1B1HRID
   Interface 00: Class 07(print) Subclass 01 Protocol 02 Driver usblp



usb-list.sh
Description: application/shellscript

Bus 001 Device 001: EHCI Host Controller [1d6b:0002]
   Class 09(hub) Subclass 00 Protocol 00
   Manufacturer: Linux 2.6.30 ehci_hcd
   SerialNumber: :00:1a.7
   Interface 00: Class 09(hub) Subclass 00 Protocol 00 Driver hub

Bus 001 Device 044: EHCI Host Controller [0424:2504]
   Class 09(hub) Subclass 00 Protocol 02
   Interface 00: Class 09(hub) Subclass 00 Protocol 02 Driver hub

Bus 001 Device 045: PhotoSmart P1100 [03f0:3102]
   Class 00(>ifc) Subclass 00 Protocol 00
   Manufacturer: Hewlett-Packard
   SerialNumber: MX01B1B1HRID
   Interface 00: Class 07(print) Subclass 01 Protocol 02 Driver usblp

Bus 001 Device 046: USB Receiver [046d:c50d]
   Class 00(>ifc) Subclass 00 Protocol 00
   Manufacturer: Logitech
   Interface 00: Class 03(HID) Subclass 01 Protocol 02 Driver usbhid

Bus 001 Device 047: USB Compliant Keyboard [05a4:9841]
   Class 00(>ifc) Subclass 00 Protocol 00
   Interface 00: Class 03(HID) Subclass 01 Protocol 01 Driver usbhid
   Interface 01: Class 03(HID) Subclass 01 Protocol 02 Driver usbhid

Bus 002 Device 001: EHCI Host Controller [1d6b:0002]
   Class 09(hub) Subclass 00 Protocol 00
   Manufacturer: Linux 2.6.30 ehci_hcd
   SerialNumber: :00:1d.7
   Interface 00: Class 09(hub) Subclass 00 Protocol 00 Driver hub

Bus 003 Device 001: UHCI Host Controller [1d6b:0001]
   Class 09(hub) Subclass 00 Protocol 00
   Manufacturer: Linux 2.6.30 uhci_hcd
   SerialNumber: :00:1a.0
   Interface 00: Class 09(hub) Subclass 00 Protocol 00 Driver hub

Bus 003 Device 002: HP Integrated Module [03f0:171d]
   Class e0(wlcon) Subclass 01 Protocol 01
   Manufacturer: Broadcom Corp
   Interface 00: Class e0(wlcon) Subclass 01 Protocol 01 Driver 
   Interface 01: Class e0(wlcon) Subclass 01 Pr

Re: DHCP Config fail on Lenny stable

[Daniel Torreblanca]

On Tue, Jun 16, 2009 at 12:33 AM, Otavio Salvador
wrote:

> In this case it has been detected; please try to call "dhclient3 eth0"
> and see if it can properly configure the network.
>
> A good thing would be if you could use a pendrive to save your
> installer syslog and the output of dmesg. It could allow us to see how
> it has been identified.
>
>  Those are for i386. I guess this is what you're looking for. If it is
> not, please let me know and I point you to the image link.
>

I downloaded the daily for amd64 yesterday and just tried installing now. It
appears that the DHCP configuration is successful this time, but now I'm
running into some weirdness with partitioning. I have a 20gb NTFS partition
booting Windows XP right now... After that 20gb partition I create a large
ext3 partition and a 2gb swap. When I create the swap partition, the
installer pops up a window that only has "?? ??" written in it, and
"go back" and "continue" options. When I go back to the partition overview
window, it only displays my hard drive information and no longer shows any
of the partitions on the drive. Not sure what to make of it, but again I
didn't continue with the installation. Any ideas?

Thanks for the help so far :)

Daniel

Re: Switch to udhcpc in netcfg

[Christian Perrier]

Quoting Luk Claes (l...@debian.org):
> Hi
> 
> Attached is a first try to support udhcpc in netcfg.
> 
> I opted for dropping support for pump and the ISC dhcp client, though
> that could be reverted if really wanted.
> 
> I don't know how DHCP_OPTION_LEN for udhcpc can be found, so I did not
> touch it for now.
> 
> Note that I did not test my patch yet except for compilation errors.
> Please do test it and come back to me, any feedback appreciated!


I just tested it with a locally built netboot image in Virtualbox.

I applied the patch, compiled netcfg and built with that udeb in
build/localudebs

It unfortunately doesn't work. netcfg times out.

When trying to do "udhcpc eth0", I get:

udhcpc (v1.13.3) started
udhcpc: exec /usr/share/udhcpc/default.script: No such file or
directory
Sending discover...
udhcpc: sendto: Network is down

Is there anything else that I could investigate?




signature.asc
Description: Digital signature

Re: Spam cleaning for August 2004

[Don Wright]

Frans Pop wrote:
>Possibly they can filter them directly using either a filter rule or a 
>list of message IDs.

And the apology from the user is here:



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Spam cleaning for August 2004

[Don Wright]

On Wed, 17 Jun 2009 12:59:43 +0200, Frans Pop  wrote:

>On Wednesday 17 June 2009, Christian Perrier wrote:
>> Back in August 2004, a huge "storm" happened with someone's
>> autoresponder spamming the list with hundreds of messages, apparently
>> looping.

>If they are, maybe it would be best to contact the listmasters (Cord) 
>directly about them. See if then can be removed without needing five 
>people to nominate and three people to review them.
>Possibly they can filter them directly using either a filter rule or a 
>list of message IDs.

You probably know this already, but...
The [1]thread begins on page 5 of the August list and extends to page 7.
It seems collected in a single chain. From the headers:

Please stop sending me emails

* To: debian-boot@lists.debian.org
* Subject: Please stop sending me emails
* From: "Frank Carmickle" 
* Date: Fri, 27 Aug 2004 16:11:11 -0400
* Message-id: 

There is an apology/analysis from the software author at [2].  --Don

[1] 
[2] 


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#533407: Testing weekly image does not detect hard drive.

[Frans Pop]

On Wednesday 17 June 2009, Otavio Salvador wrote:
> When I read the log I read it as it hasn't find the file of the module
> .. not that the module has failed to find  the device.

So what? That module really has nothing at all to do with normal hard disk 
controllers. How many people do you think have their primary hard disk 
behind PCMCIA?
With CD images the actual detection of normal hard disks happens *way* 
before disk-detect is run in 99.99% of installs.



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#489006: debian-installer: After grub software raid installation, machine fails to boot with first drive removed or blanked.

[Felix Zielcke]

Am Mittwoch, den 17.06.2009, 15:43 +0200 schrieb Raphael Hertzog:
> On Thu, 04 Jun 2009, Felix Zielcke wrote:
> > I think this shouldn't anymore happen with grub2.
> > It supports the Linux Software RAID.
> > Could you please try it? (grub-pc package)
> 
> How are we supposed to try it?
> 
> grub-install /dev/md0 ?

Either grub-install '(md0)' if you want to have grub2 in all MBRs
of /dev/md0 or just the old way like grub-install /dev/sda for every
disk.
update-grub generates grub.cfg with `set root=(md0)' and the same is
used for the --prefix in the grub-mkimage call in grub-install.
The prefix is the variable where grub2 loads all it's modules and the
config from.

> In any case, grub-installer still needs some modifications to do the
> proper operation, whatever it is.
> 
> I'm interested in seeing this bug resolved and I can do the required
> tests if needed.
> 

-- 
Felix Zielcke




-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#533407: marked as done (Testing weekly image does not detect hard drive.)

[Debian Bug Tracking System]

Your message dated Wed, 17 Jun 2009 15:50:39 +0200
with message-id <200906171550.39787.elen...@planet.nl>
and subject line Re: Bug#533407: Testing weekly image does not detect hard 
drive.
has caused the Debian Bug report #533407,
regarding Testing weekly image does not detect hard drive.
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.)


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

Boot method: CD
Image version: 
http://cdimage.debian.org/cdimage/weekly-builds/i386/iso-cd/debian-testing-i386-kde-CD-1.iso
Date: 17 June 2009

Machine: Various
Processor:Various
Memory:Various
Partitions: Various

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

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:  [O]
Load installer modules: [O]
Detect hard drives: [E]
Partition hard drives:  [ ]
Install base system:[ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:
Installer does not detect hard drive. Copied from syslog:
INFO: Menu item 'disk-detect' selected
net/hw-detect.hotplug: Detected hotpluggable network interface eth0
net/hw-detect.hotplug: Detected hotpluggable network interface lo
hw-detect: Loading PCMCIA bridge driver module: i82365
Kernel: [  47.534066] Intel isa PCIC probe: not found
hw-detect: FATAL: Error intserting i82365
(/lib/modules/2.6.29-2-486/kernel/driver/pcmcia/i82365.ko): No such
device
check-missing-firmware: no missing firmware in /tmp/missing-firmware
--- End Message ---
--- Begin Message ---
On Wednesday 17 June 2009, Untitled wrote:
> 2. Attached syslog and hardware summary of the installation. I couldn't
> find a way to save lspci -nn as the coputer doesn't have a floppy drive
> and the hard drive is not detected so I can't mount a disk...

Jun 17 12:37:03 kernel: [1.558634] sd 1:0:0:0: [sda] Write cache: 
enabled, read cache: enabled, doesn't support DPO or FUA
Jun 17 12:37:03 kernel: [1.558636]  sda:<5>sr 0:0:1:0: Attached scsi 
generic sg0 type 5
Jun 17 12:37:03 kernel: [1.562420] sd 1:0:0:0: Attached scsi generic 
sg1 type 0
Jun 17 12:37:03 kernel: [1.571860]  sda1 sda2 < sda5 > sda3
Jun 17 12:37:03 kernel: [1.597691] sd 1:0:0:0: [sda] Attached SCSI 
disk

Your harddisk is detected fine.

Jun 17 12:39:26 main-menu[1076]: (process:5905): parted_devices: error 
while loading shared libraries: libparted-1.8.so.10: cannot open shared 
object file: No such file or directory

Just as I expected: the new version of libparted is screwing things up. 
Will probably be fixed within the next few days if Otavio (who is 
responsible for that transition) is managing things properly.

Closing this report as there's not really a bug here. Just a normal issue 
that can be expected when using daily development images.

Cheers,
FJP

--- End Message ---

Bug#533407: Testing weekly image does not detect hard drive.

[Frans Pop]

On Wednesday 17 June 2009, Frans Pop wrote:
> Jun 17 12:39:26 main-menu[1076]: (process:5905): parted_devices: error
> while loading shared libraries: libparted-1.8.so.10: cannot open shared
> object file: No such file or directory
>
> Just as I expected: the new version of libparted is screwing things up.
> Will probably be fixed within the next few days if Otavio (who is
> responsible for that transition) is managing things properly.
>
> Closing this report as there's not really a bug here. Just a normal
> issue that can be expected when using daily development images.

Just see you were using weekly images, so it should be fixed after the 
next weeklies are built, i.e. some time Monday next week.



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#489006: debian-installer: After grub software raid installation, machine fails to boot with first drive removed or blanked.

[Raphael Hertzog]

On Thu, 04 Jun 2009, Felix Zielcke wrote:
> I think this shouldn't anymore happen with grub2.
> It supports the Linux Software RAID.
> Could you please try it? (grub-pc package)

How are we supposed to try it?

grub-install /dev/md0 ?

In any case, grub-installer still needs some modifications to do the
proper operation, whatever it is.

I'm interested in seeing this bug resolved and I can do the required
tests if needed.

Cheers,
-- 
Raphaël Hertzog

Contribuez à Debian et gagnez un cahier de l'admin Debian Lenny :
http://www.ouaza.com/wp/2009/03/02/contribuer-a-debian-gagner-un-livre/



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#533407: Testing weekly image does not detect hard drive.

[Otavio Salvador]

Hello,

On Wed, Jun 17, 2009 at 8:28 AM, Frans Pop wrote:
> On Wednesday 17 June 2009, Otavio Salvador wrote:
>> On Wed, Jun 17, 2009 at 6:02 AM, Untitled wrote:
>> > INFO: Menu item 'disk-detect' selected
>> > net/hw-detect.hotplug: Detected hotpluggable network interface eth0
>> > net/hw-detect.hotplug: Detected hotpluggable network interface lo
>> > hw-detect: Loading PCMCIA bridge driver module: i82365
>> >
>> > Kernel: [  47.534066] Intel isa PCIC probe: not found
>> > hw-detect: FATAL: Error intserting i82365
>> > (/lib/modules/2.6.29-2-486/kernel/driver/pcmcia/i82365.ko): No such
>> > device
>> > check-missing-firmware: no missing firmware in /tmp/missing-firmware
>>
>> Please do following test:
>> After the network has been setuped please go to console 2 and call:
>> #: anna-install pcmcia-modules
>>
>> And see if it works and if it solves your problem.
>
> I can tell you the result of that test now: it's not going to help.
> Basically the quoted log messages can be found in 99% of x86 installs.
>
> What is needed here is the output of 'lspci -nn' and the *full* syslog
> (gzipped). The snippet above is very clearly not where the problem is
> (and you should know that!).

When I read the log I read it as it hasn't find the file of the module
.. not that the module has failed to find  the device.

-- 
Otavio Salvador  O.S. Systems
E-mail: ota...@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#533407: Testing weekly image does not detect hard drive.

[Untitled]

Thank you both for helping...

1. modprobe i82365 returns Error Inserting i82365 [] No such device.

2. Attached syslog and hardware summary of the installation. I couldn't find
a way to save lspci -nn as the coputer doesn't have a floppy drive and the
hard drive is not detected so I can't mount a disk...

Thanks,
Golan.

On Wed, Jun 17, 2009 at 12:28 PM, Frans Pop  wrote:

> On Wednesday 17 June 2009, Otavio Salvador wrote:
> > On Wed, Jun 17, 2009 at 6:02 AM, Untitled wrote:
> > > INFO: Menu item 'disk-detect' selected
> > > net/hw-detect.hotplug: Detected hotpluggable network interface eth0
> > > net/hw-detect.hotplug: Detected hotpluggable network interface lo
> > > hw-detect: Loading PCMCIA bridge driver module: i82365
> > >
> > > Kernel: [  47.534066] Intel isa PCIC probe: not found
> > > hw-detect: FATAL: Error intserting i82365
> > > (/lib/modules/2.6.29-2-486/kernel/driver/pcmcia/i82365.ko): No such
> > > device
> > > check-missing-firmware: no missing firmware in /tmp/missing-firmware
> >
> > Please do following test:
> > After the network has been setuped please go to console 2 and call:
> > #: anna-install pcmcia-modules
> >
> > And see if it works and if it solves your problem.
>
> I can tell you the result of that test now: it's not going to help.
> Basically the quoted log messages can be found in 99% of x86 installs.
>
> What is needed here is the output of 'lspci -nn' and the *full* syslog
> (gzipped). The snippet above is very clearly not where the problem is
> (and you should know that!).
>


syslog.tar.gz
Description: GNU Zip compressed data

Armel Lenny on ARM

[Amandeep Bhullar]

Hi guys,

I am using ARM board (AT91SAM9263-EK) and want to install Debian Lenny using
tftp image. I am new to this. Can someone please give me brief steps or
point to to a resource about how to install Debian using tftp and U-boot on
my board.

many thanks in advance.

Aman.

Bug#533407: Testing weekly image does not detect hard drive.

[Frans Pop]

On Wednesday 17 June 2009, Otavio Salvador wrote:
> On Wed, Jun 17, 2009 at 6:02 AM, Untitled wrote:
> > INFO: Menu item 'disk-detect' selected
> > net/hw-detect.hotplug: Detected hotpluggable network interface eth0
> > net/hw-detect.hotplug: Detected hotpluggable network interface lo
> > hw-detect: Loading PCMCIA bridge driver module: i82365
> >
> > Kernel: [  47.534066] Intel isa PCIC probe: not found
> > hw-detect: FATAL: Error intserting i82365
> > (/lib/modules/2.6.29-2-486/kernel/driver/pcmcia/i82365.ko): No such
> > device
> > check-missing-firmware: no missing firmware in /tmp/missing-firmware
>
> Please do following test:
> After the network has been setuped please go to console 2 and call:
> #: anna-install pcmcia-modules
>
> And see if it works and if it solves your problem.

I can tell you the result of that test now: it's not going to help.
Basically the quoted log messages can be found in 99% of x86 installs.

What is needed here is the output of 'lspci -nn' and the *full* syslog 
(gzipped). The snippet above is very clearly not where the problem is 
(and you should know that!).



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#533407: Testing weekly image does not detect hard drive.

[Otavio Salvador]

On Wed, Jun 17, 2009 at 7:30 AM, Untitled wrote:
[...]
> Then the disk detection returns the same error as before.

I forgot to tell you to run, after anna-install:

#: depmod -a
#: modprobe i82365

-- 
Otavio Salvador  O.S. Systems
E-mail: ota...@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Spam cleaning for August 2004

[Frans Pop]

On Wednesday 17 June 2009, Christian Perrier wrote:
> Back in August 2004, a huge "storm" happened with someone's
> autoresponder spamming the list with hundreds of messages, apparently
> looping.
>
> I found these in the list archive which one can download as a mailbox.
>
> I haven't checked whether they are in the web archives, but that
> should be easy to check: with them, August 2004 has about 3400 mails
> instead of the usual 2000-2500 we were having at that time.

If they are, maybe it would be best to contact the listmasters (Cord) 
directly about them. See if then can be removed without needing five 
people to nominate and three people to review them.
Possibly they can filter them directly using either a filter rule or a 
list of message IDs.


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#533407: Testing weekly image does not detect hard drive.

[Otavio Salvador]

Hello,

On Wed, Jun 17, 2009 at 6:02 AM, Untitled wrote:
> INFO: Menu item 'disk-detect' selected
> net/hw-detect.hotplug: Detected hotpluggable network interface eth0
> net/hw-detect.hotplug: Detected hotpluggable network interface lo
> hw-detect: Loading PCMCIA bridge driver module: i82365
>
> Kernel: [  47.534066] Intel isa PCIC probe: not found
> hw-detect: FATAL: Error intserting i82365
> (/lib/modules/2.6.29-2-486/kernel/driver/pcmcia/i82365.ko): No such device
> check-missing-firmware: no missing firmware in /tmp/missing-firmware

Please do following test:

After the network has been setuped please go to console 2 and call:

#: anna-install pcmcia-modules

And see if it works and if it solves your problem.

-- 
Otavio Salvador  O.S. Systems
E-mail: ota...@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#533384: do not add ff02::3 to /etc/hosts

[Otavio Salvador]

Hello Christian,

On Wed, Jun 17, 2009 at 2:23 AM, Christian Perrier wrote:
> Confident in the wisdom of your suggestions, I created the attached
> revolutionary patch.
>
> Other D-I folks, any objection to apply it?

Please do.

-- 
Otavio Salvador  O.S. Systems
E-mail: ota...@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: Re: Bug#533384: do not add ff02::3 to /etc/hosts

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 533384 patch
Bug#533384: do not add ff02::3 to /etc/hosts
There were no tags set.
Tags added: patch

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#533384: do not add ff02::3 to /etc/hosts

[Christian Perrier]

tags 533384 patch
thanks

Quoting Marco d'Itri (m...@linux.it):
> Package: netcfg
> Version: 0.66
> Severity: normal
> 
> Please remove the ff02::3 address from netcfg.h, it is not actually
> assigned and the same change has already been done in netbase.
> 
> Reference:
> http://www.iana.org/assignments/ipv6-multicast-addresses/

Confident in the wisdom of your suggestions, I created the attached
revolutionary patch.

Other D-I folks, any objection to apply it?


--- netcfg.h.ori2009-06-17 07:21:35.865026707 +0200
+++ netcfg.h2009-06-17 07:21:48.173027165 +0200
@@ -38,8 +38,7 @@
 "fe00::0 ip6-localnet\n" \
 "ff00::0 ip6-mcastprefix\n" \
 "ff02::1 ip6-allnodes\n" \
-"ff02::2 ip6-allrouters\n" \
-"ff02::3 ip6-allhosts\n"
+"ff02::2 ip6-allrouters\n"
 
 typedef enum { NOT_ASKED = 30, GO_BACK } response_t;
 typedef enum { DHCP, STATIC, DUNNO } method_t;


signature.asc
Description: Digital signature

Bug#533407: Testing weekly image does not detect hard drive.

[Untitled]

Package: installation-reports

Boot method: CD
Image version: 
http://cdimage.debian.org/cdimage/weekly-builds/i386/iso-cd/debian-testing-i386-kde-CD-1.iso
Date: 17 June 2009

Machine: Various
Processor:Various
Memory:Various
Partitions: Various

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

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:  [O]
Load installer modules: [O]
Detect hard drives: [E]
Partition hard drives:  [ ]
Install base system:[ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:
Installer does not detect hard drive. Copied from syslog:
INFO: Menu item 'disk-detect' selected
net/hw-detect.hotplug: Detected hotpluggable network interface eth0
net/hw-detect.hotplug: Detected hotpluggable network interface lo
hw-detect: Loading PCMCIA bridge driver module: i82365
Kernel: [  47.534066] Intel isa PCIC probe: not found
hw-detect: FATAL: Error intserting i82365
(/lib/modules/2.6.29-2-486/kernel/driver/pcmcia/i82365.ko): No such
device
check-missing-firmware: no missing firmware in /tmp/missing-firmware