Bug#366168: debian-installer: usbhid NOT loaded by udev at initrd stage = no keyboard on USB-only system

2006-05-05 Thread Joey Hess
Martin-Éric Racine wrote:
> 2.4 kernels waste time trying to find an AT keyboard that isn't there,
> then forget to load usbhid.

So usb-discover is not working then? It should load hid (it's not called
usbhid in 2.4) when it runs, unconditionally, assuming there is a
/proc/bus/pci/devices. Don't you have that file?

> 2.6 kernels don't try finding any AT keyboard and forget usbhid too.

Until today when Kamion put it back in, we didn't have usb-discover on
2.6 images, relying on just udev to load usb stuff for 2.6. It sounds
like udev is not working on your hardware; maybe you need to file a bug
on udev? 

I'm also interested in whether Kamion's change of adding usb-discover
back to the 2.6 images fixed the issue for you, since based on what you
said about 2.4 it seems usb-discover is also not working on your
hardware.

BTW: What geode hardware exactly is it?

-- 
see shy jo


signature.asc
Description: Digital signature


Bug#366168: debian-installer: usbhid NOT loaded by udev at initrd stage = no keyboard on USB-only system

2006-05-05 Thread Martin-Éric Racine
Package: debian-installer
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

As suggested by Kamion, I'm filing the bug I discussed on #debian-boot.

My particular situation is an installation on a Geode (i586 compatible 
single-chip PC) with a Compact Flash attached to the Geode's IDE bus. 

I'm using the hd-media kernels, following a recipe similar to the USB 
stick installation.

I bootstrap d-i kernels using LILO from the Geode's CF (to compensate 
for the Geode's lack of a complete BIOS), while the businesscard ISO 
resides on a USB stick to avoid file locks during the drive formating 
stage (the CF is my root drive).

The problem is that udev doesn't load usbhid during the initrd stage, 
which later makes it impossible for me to run through the installation 
because the keyboard is not accessible without usbhid.

I have tried the daily hd-media kernels and initrds (both 2.4 and 2.6).

2.4 kernels waste time trying to find an AT keyboard that isn't there,
then forget to load usbhid.

2.6 kernels don't try finding any AT keyboard and forget usbhid too.

The funny thing in both cases is that usbcore and usb-storage are both
found, which means that the USB stick on which the ISO resides and the 
keyboard's built-in hub are accessible; the only missing part is usbhid
to actually be able to type something.

The LILO config I use to bootstrap d-i kernels from the CF:

lba32
disk=/dev/sda
bios=0x80
boot=/dev/sda
install=/boot/boot.b
image=/vmlinuz
  append="initrd=initrd.gz ramdisk_size=12000 root=/dev/ram rw"
  initrd=/initrd.gz
  root=/dev/ram0

I'd appreciate any help on getting the udev in initrd to successfully
detect the hardware and systematically load usbhid.

Thanks!

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFEW6lfeXr56x4Muc0RAswmAJ9avqQ+Be+4ldb896lgFoLkhXLDvQCfYCij
pK5NUTwprWzIvjQJxbGu1YA=
=LLIw
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#366177: Tyan S2877 installation-report

2006-05-05 Thread Karl Schmidt

Package: installation-reports

Boot method: 
Image version: 
http://cdimage.debian.org/cdimage/etch_di_beta2/amd64/iso-cd/debian-testing-amd64-businesscard.iso>
Date: 

Machine: 
Processor: Dual AMD OSA265C
Memory: 4 1 Gig sticks (to support 128bit)
Partitions: 

Output of lspci and lspci -n: <
# lspci
:00:00.0 Memory controller: nVidia Corporation CK804 Memory Controller (rev 
a3)
:00:01.0 ISA bridge: nVidia Corporation CK804 ISA Bridge (rev a3)
:00:01.1 SMBus: nVidia Corporation CK804 SMBus (rev a2)
:00:02.0 USB Controller: nVidia Corporation CK804 USB Controller (rev a2)
:00:02.1 USB Controller: nVidia Corporation CK804 USB Controller (rev a3)
:00:06.0 IDE interface: nVidia Corporation CK804 IDE (rev a2)
:00:07.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev 
a3)
:00:08.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev 
a3)
:00:09.0 PCI bridge: nVidia Corporation CK804 PCI Bridge (rev a2)
:00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a3)
:00:0b.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
:00:0c.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
:00:0d.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
:00:0e.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
HyperTransport Technology Configuration
:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
Address Map
:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
DRAM Controller
:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
Miscellaneous Control
:00:19.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
HyperTransport Technology Configuration
:00:19.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
Address Map
:00:19.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
DRAM Controller
:00:19.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
Miscellaneous Control
:01:06.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5705_2 
Gigabit Ethernet (rev 03)

:01:07.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)

# lspci -n
:00:00.0 0580: 10de:005e (rev a3)
:00:01.0 0601: 10de:0051 (rev a3)
:00:01.1 0c05: 10de:0052 (rev a2)
:00:02.0 0c03: 10de:005a (rev a2)
:00:02.1 0c03: 10de:005b (rev a3)
:00:06.0 0101: 10de:0053 (rev a2)
:00:07.0 0101: 10de:0054 (rev a3)
:00:08.0 0101: 10de:0055 (rev a3)
:00:09.0 0604: 10de:005c (rev a2)
:00:0a.0 0680: 10de:0057 (rev a3)
:00:0b.0 0604: 10de:005d (rev a3)
:00:0c.0 0604: 10de:005d (rev a3)
:00:0d.0 0604: 10de:005d (rev a3)
:00:0e.0 0604: 10de:005d (rev a3)
:00:18.0 0600: 1022:1100
:00:18.1 0600: 1022:1101
:00:18.2 0600: 1022:1102
:00:18.3 0600: 1022:1103
:00:19.0 0600: 1022:1100
:00:19.1 0600: 1022:1101
:00:19.2 0600: 1022:1102
:00:19.3 0600: 1022:1103
:01:06.0 0200: 14e4:1654 (rev 03)
:01:07.0 0300: 1002:4752 (rev 27)>

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot worked:[O]
Configure network HW:   [O]
Config network: [E]
Detect CD:  [E]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [E]
Create file systems:[E]
Mount partitions:   [O]
Install base system:[E]
Install boot loader:[ ]
Reboot: [ ]

Comments/Problems:

<
Would not DHCP correctly until I booted with Knoppix and it created a lease 
file.  I could see the requests on the DHCP server, looked like the MAC address 
was incremented by 1 from what it really was?? Very strange. There are two NICs 
on this MB - the first one is nvidia and the second Broadcom


From Tyan's web site :
• One Broadcom BCM5705 GbE LAN (G2NR)
- One RJ-45 LAN connector with LEDs
 • One Marvell 88E GbE PHY
- One RJ-45 LAN connectors with LEDs

I don't think this is correct?? etho is a nvidia ck804 and the one that will 
work (after there is a lease file) and eth1 is the broadcom that would never 
work. Note they are listing the  Marvell as PHY instead of a Lan device --


see http://en.wikipedia.org/wiki/PHYceiver

I'm not sure I understand - could be two physical devices for the same eth0???

The drivers seem to be forcedeth and tg3

:00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a3)
:01:06.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5705_2 
Gigabit Ethernet (rev 03)


Could be that the nvidia part just bridges the Broadcom controller with the PHY 
interface chip?? There is a bridge enabled setting in the BIOS.




Next error:
Would not boot from the SATA CD/DVD plextor drive (px-755SA) - not a big deal - 
so I put in an older IDE drive for now.  (note not a proble

Processed: Re: Bug#366140: installation: general daemon upgrade problem

2006-05-05 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> severity 366140 normal
Bug#366140: installation: general daemon upgrade problem
Severity set to `normal'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#366140: installation: general daemon upgrade problem

2006-05-05 Thread Christian Perrier
severity 366140 normal
thanks

Quoting Balázs Hámorszky ([EMAIL PROTECTED]):
> Package: installation
> Severity: important
> 
> 
> I want to refer to bug #363657 and #362825.
> Upgradeing a daemon shouldn't presume that the deamon is must be running if 
> it's installed. The script must previously check it.

Could you be more specific ?




signature.asc
Description: Digital signature


Booting order - problem

2006-05-05 Thread Vladimir Strycek

Hi,

Could somebody help me with setting booting order in kernel ?

My actual problem is that fstab wont mount harddisk USB and SATA ( no 
problem with IDE where my system is)


Actualy i can mount them manulay when its boot finish and i log in.

I looked in dmesg and there i found that all HDD i need mount are 
inicialised as almoust last thing...


So  problem is that fstab start mounting before they inicialise ...

Any idea how to fix this ?

Thanks
Vlado


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#366140: installation: general daemon upgrade problem

2006-05-05 Thread Frans Pop
On Friday 05 May 2006 16:46, Balázs Hámorszky wrote:
> I want to refer to bug #363657 and #362825.
> Upgradeing a daemon shouldn't presume that the deamon is must be
> running if it's installed. The script must previously check it.

Please explain why you are filing this bug.
The bugs you quote seem to speak for themselves and will no doubt be 
solved by their respective package maintainers in due course.

Also, your bug report does not seem to have anything to do with Debian 
Installer, which is what the "installation" pseudo package is supposed to 
be used for.



Bug#366140: marked as done (installation: general daemon upgrade problem)

2006-05-05 Thread Debian Bug Tracking System
Your message dated Fri, 05 May 2006 18:32:08 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Fwd: Re: Bug#366140: installation: general daemon upgrade 
problem
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

--- Begin Message ---
Package: installation
Severity: important


I want to refer to bug #363657 and #362825.
Upgradeing a daemon shouldn't presume that the deamon is must be running if 
it's installed. The script must previously check it.


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16
Locale: LANG=hu_HU, LC_CTYPE=hu_HU (charmap=ISO-8859-2)

--- End Message ---
--- Begin Message ---
--  Forwarded Message  --
Subject: Re: Bug#366140: installation: general daemon upgrade problem
Date: Friday 05 May 2006 18:21
From: Hámorszky Balázs <[EMAIL PROTECTED]>
To: Frans Pop <[EMAIL PROTECTED]>

I've misunderstood the meaning of installation.

otherwise i think that debian should make a policy about daemon
upgrading to avoid things like that bugs.

sorry!
---

No problem.

In that case I propose you first check the Debian policy manual [1] to see 
if this subject is already covered or not. I would expect that the basic 
principles of daemons should already be covered there.

After that it is probably best to propose a solution and discuss it on the 
debian-devel mailing list before maybe filing a bug against 
debian-policy.

I'm closing this bug report.

Cheers,
FJP

[1] http://www.debian.org/doc/debian-policy/
--- End Message ---


Bug#366140: installation: general daemon upgrade problem

2006-05-05 Thread Balázs Hámorszky
Package: installation
Severity: important


I want to refer to bug #363657 and #362825.
Upgradeing a daemon shouldn't presume that the deamon is must be running if 
it's installed. The script must previously check it.


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16
Locale: LANG=hu_HU, LC_CTYPE=hu_HU (charmap=ISO-8859-2)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



localechooser_1.14_i386.changes ACCEPTED

2006-05-05 Thread Debian Installer

Accepted:
localechooser_1.14.dsc
  to pool/main/l/localechooser/localechooser_1.14.dsc
localechooser_1.14.tar.gz
  to pool/main/l/localechooser/localechooser_1.14.tar.gz
localechooser_1.14_all.udeb
  to pool/main/l/localechooser/localechooser_1.14_all.udeb
Announcing to debian-devel-changes@lists.debian.org


Thank you for your contribution to Debian.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Processing of localechooser_1.14_i386.changes

2006-05-05 Thread Archive Administrator
localechooser_1.14_i386.changes uploaded successfully to localhost
along with the files:
  localechooser_1.14.dsc
  localechooser_1.14.tar.gz
  localechooser_1.14_all.udeb

Greetings,

Your Debian queue daemon


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



usb-discover_1.05_powerpc.changes ACCEPTED

2006-05-05 Thread Debian Installer

Accepted:
usb-discover_1.05.dsc
  to pool/main/u/usb-discover/usb-discover_1.05.dsc
usb-discover_1.05.tar.gz
  to pool/main/u/usb-discover/usb-discover_1.05.tar.gz
usb-discover_1.05_all.udeb
  to pool/main/u/usb-discover/usb-discover_1.05_all.udeb
Announcing to debian-devel-changes@lists.debian.org


Thank you for your contribution to Debian.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Processing of usb-discover_1.05_powerpc.changes

2006-05-05 Thread Archive Administrator
usb-discover_1.05_powerpc.changes uploaded successfully to localhost
along with the files:
  usb-discover_1.05.dsc
  usb-discover_1.05.tar.gz
  usb-discover_1.05_all.udeb

Greetings,

Your Debian queue daemon


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: an awful lot of energy

2006-05-05 Thread Geert Stappers
On Thu, May 04, 2006 at 03:42:31PM +0200, Sven Luther wrote:
> 
> In this case, actions speak louder than words. So, i await the restoration of
> the svn commit rights, but until then, it is clear that they want to get ride
> of me.
> 
> The excuses they have put (that i would abuse the svn commit rights) are
> bordering on the insulting, and the fact they did it while i was at the
> sickbed of my dying mother show a complete lack of human decency.
> 
> So, they may say many things, but it is actions that count.


Yes, you are right.

Right now we are telling "we don't like your attitude".
It is not told in written word, it is told by action. (actions do count)
The action is "ignore the whatever[1]"


The rest of this E-mail are an explanation of obvious things.

* Freedom of speech is good. 
  But it does not mean "Each speech has to be honoured"

* Each group has good members and better members
 - Addressing the group includes all members
 - Asking the group to do better, includes the member all ready doing so

* Each porter group has good porters and better porters
 - Addressing the group includes all porters
 - Asking the porters to do better, includes the porter all ready doing so
 - If the better porter feels offended by such request,
   then it is his point of view to feel offend

* Writing a resignation means writing a resignation.

* There is nothing wrong with "Hi, I'm back."

* Recieving a resignation letter means revoking things (keys, rights)
 
* Expressing feelings at a seperation is very hard.
 - Working together and then stop working together is strange, very strange
 - Saying "I'm glad that you leave" does no good.

* Holding a patch in hostage is holding a patch in hostage

* There is a difference between "being offended" and "feeling offended"



Sven,

I think this is going to happen:

* Things go worse
* Someone thinks to fix a social problem by a technical thing,
  like a ban or expulsion
* I will miss your request for support, due being occupied elsewhere
* There will be a call for votes for expulsion/banning you
* I vote to keep you in. Only to express
  that "Kicking out those who think different doesn't help"
* You will be remembered as the one with the odd point of view.
  (and spending / draining an awful lot of energy proofing so )


All of this will go parallell with other things in life we care about.

Hopefully we can all find the right balance for it.


Cheers
Geert Stappers


[1] person, angry person, live form, low live form;  take you pick.


signature.asc
Description: Digital signature