Re: end-of-story (USB keyboard support on complicated hardware)

[bounce-debian-boot=archive=jab . org]

On Tue, Jan 01, 2002 at 11:24:01PM +0100, Eduard Bloch wrote:
> 
> It does not for me. It works the same was as usuall: loads and starts
> the kernel immediately, no initrd loading.

Please reread my message, you need to tell syslinux to load the initrd.
-- 
Debian GNU/Linux 2.2 is out! ( http://www.debian.org/ )
Email:  Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt


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

Bug#127417: boot-floppies: Problem report saved to /instmnt (on ramdisk) by default

[Chris Tillman]

Package: boot-floppies
Version: 3.0.19 built locally 12/31/2001
Severity: normal

I tried out the Problem Report function on my last install. It worked 
very well, except for the save-where dialog (which John Robinson has 
been working on). Since I couldn't get the save dialog to work, I left 
the line blank and tabbed to the OK button. It said it had saved the 
report at /instmnt//dbg_log.tgz (two slashes were there). 

I switched to vc2 and it wasn't lying; that's where it had saved it. But 
that is the mount point on the ram disk, so if I had rebooted the report 
would have disappeared. A different default like /target would be better. 

I looked at the information dump and all seemed good.

The only other thing is, the title of the function really isn't accurate.
It doesn't allow you to report a problem, just saves the machine status. 
How about Save Debugging Log instead?

-- System Information
Debian Release: 3.0
Architecture: powerpc
Kernel: Linux test2219 2.2.19-pmac #1 Sun Oct 21 13:45:25 EDT 2001 ppc
Locale: LANG=C, LC_CTYPE=C



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

Re: packages required in installation (Re: apt-utils in debootstrap)

[Anthony Towns]

On Wed, Jan 02, 2002 at 01:22:11PM +0900, Junichi Uekawa wrote:
> The following script checks for validity of priority/section (and 
> I think this is what should be done, please tell me if something looks wrong) :
> for A in $(/usr/sbin/debootstrap --arch $ARCH --print-debs woody); do (apt-cache 
>show $A | awk '/^Package:/{package=$2} /^Section:/{section=$2} 
>/^Priority:/{priority=$2} END{print package " " section " " priority}') ; done | awk 
>'{if ($2 != "base" && $3 != "required") {print "Bad base program: " $0 }} '
> 
> I believe, if the section is "base", or is "required" priority,
> it should be found in the first CD. Would "important" suffice?

No, "base" cannot be determined by priorities and sections. You need to 
get debootstrap, and run "debootstrap --print-debs woody" to get a list
of packages debootstrap expects on the first CD. If those packages aren't
on the first CD, it's a bug in the CD.

Cheers,
aj

-- 
Anthony Towns <[EMAIL PROTECTED]> 
I don't speak for anyone save myself. GPG signed mail preferred.

The daffodils are coming. Are you?
  linux.conf.au, February 2002, Brisbane, Australia
--- http://linux.conf.au/


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

packages required in installation (Re: apt-utils in debootstrap)

[Junichi Uekawa]

On Wed, 2 Jan 2002 12:01:55 +0900
Junichi Uekawa <[EMAIL PROTECTED]> wrote:

CC'd to debian-cd, because that's probably the relevant list.



The following script checks for validity of priority/section (and 
I think this is what should be done, please tell me if something looks wrong) :

for A in $(/usr/sbin/debootstrap --arch $ARCH --print-debs woody); do (apt-cache show 
$A | awk '/^Package:/{package=$2} /^Section:/{section=$2} /^Priority:/{priority=$2} 
END{print package " " section " " priority}') ; done | awk '{if ($2 != "base" && $3 != 
"required") {print "Bad base program: " $0 }} '



I believe, if the section is "base", or is "required" priority,
it should be found in the first CD. Would "important" suffice?

If this seems like a good check, I would add this check to 
the debian installer check so that things will get clearer.


The following is my check (against current testing)

Bad base program: debconf admin optional
Bad base program: libdb2 libs optional
Bad base program: libgdbmg1 libs standard
Bad base program: apt-utils admin optional
Bad base program: at admin important
Bad base program: bsdmainutils utils important
Bad base program: console-common utils important
Bad base program: cpio utils important
Bad base program: cron admin important
Bad base program: dhcp-client net optional
Bad base program: ed editors important
Bad base program: exim mail important
Bad base program: groff-base text important
Bad base program: info doc important
Bad base program: libident libs important
Bad base program: libldap2 libs important
Bad base program: liblockfile1 libs important
Bad base program: libpcre3 libs important
Bad base program: libsasl7 libs important
Bad base program: logrotate admin important
Bad base program: mailx mail important
Bad base program: man-db doc important
Bad base program: manpages doc important
Bad base program: nano editors important
Bad base program: net-tools net standard
Bad base program: netkit-inetd net standard
Bad base program: netkit-ping net standard
Bad base program: nvi editors important
Bad base program: pppoe net optional
Bad base program: libpcap0 libs optional
Bad base program: telnet net standard
Bad base program: pciutils admin optional
Bad base program: psmisc admin optional



regards,
junichi


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

apt-utils in debootstrap

[Junichi Uekawa]

Hi,

Manoj told me on IRC that apt-utils is not on the first CD-Rom.

debootstrap seems to want apt-utils, and apt-utils is "optional".
Something needs fixing, either debootstrap, or apt-utils.

comments?


regards,
junichi


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

Re: end-of-story (USB keyboard support on complicated hardware)

[Chris Tillman]

On Tue, Jan 01, 2002 at 11:24:01PM +0100, Eduard Bloch wrote:
> Okay, I am fed up with this conversation. If you don't like my
> suggestion, okay. I managed to get USB support in current BFs, so it
> will work for users with similar problems, even if not with _your_
> kernels. It does not work with floppy disks, but the users with
> legacy-free systems will probably not have any floppy drives though.
> 
> Gruss/Regards,
> Eduard.
> -- 

Before you get away, Eduard: what if anything do I need to document
about this problem in the install manual? How about:

The USB keyboard driver subsystem on some machines doesn't start up
quickly enough during the boot process to be available when the prompt
is given to insert the root disk. If you have a USB keyboard and get
no response at the root disk prompt, try attaching a regular (AT)
keyboard in order to enter . Then the AT keyboard can be
detached.

-- 
*--v- Installing Debian GNU/Linux 3.0 v--*
|    |
|   debian-imac (potato):    |
|Chris Tillman[EMAIL PROTECTED]  |
|   May the Source be with you   |
**


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

Re: 3.0.18 testing needed

[Michel Dänzer]

On Wed, 2002-01-02 at 01:05, Philip Blundell wrote:
> In message <[EMAIL PROTECTED]>, Michel Lanners writes:
> >- trying to use mac-fdisk from a shell, I get this error:
> >
> >  /sbin/mac-fdisk: 1: Syntax error: "(" unexpected
> >
> >  Hmmm.. looks like ash tries to execute mac-fdisk as a shell script?
> 
> Apparently the mac-fdisk binary is corrupted somehow.  There's already a bug
> open on this: I don't know if those builds of boot-floppies were just bad
> for some reason, or the binary in the archive is actually broken, or something
> else.  One of the PPC folks probably needs to look at it.

daenzer@pismo> file /mnt/sbin/mac-fdisk~
/mnt/sbin/mac-fdisk: ELF 32-bit MSB executable, no machine, version 1
(SYSV), dynamically linked (uses shared libs), stripped
daenzer@pismo> /mnt/sbin/mac-fdisk ~
zsh: exec format error: /mnt/sbin/mac-fdisk
(1)daenzer@pismo> /mnt/sbin/fdisk  ~
mac-fdisk: bad usage - no device argument

mac-fdisk [-h|--help]
mac-fdisk [-v|--version]
mac-fdisk [-l|--list [name ...]]
mac-fdisk [-r|--readonly] name ...
mac-fdisk name ...


So /sbin/mac-fdisk is hosed for some reason, but /sbin/fdisk seems to be
a working mac-fdisk.


-- 
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member   /  CS student, Free Software enthusiast


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

Re: 3.0.18 testing needed

[Philip Blundell]

In message <[EMAIL PROTECTED]>, Michel Lanners writes:
>- trying to use mac-fdisk from a shell, I get this error:
>
>  /sbin/mac-fdisk: 1: Syntax error: "(" unexpected
>
>  Hmmm.. looks like ash tries to execute mac-fdisk as a shell script?

Apparently the mac-fdisk binary is corrupted somehow.  There's already a bug
open on this: I don't know if those builds of boot-floppies were just bad
for some reason, or the binary in the archive is actually broken, or something
else.  One of the PPC folks probably needs to look at it.

p.


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

Re: 3.0.18 testing needed

[Michel Lanners]

Hey,

Maybe a bit late but testing nevertheless ;-)

On  15 Dec, this message from Adam Di Carlo echoed through cyberspace:
> I've uploaded i386 and powerpc boot-floppies to 
> http://people.debian.org/~aph/debian/dists/woody/main/>.

OK, tested these (in fact the 20011221 build of bf 3.0.18) for a new
install on a 7600 Powermac (SCSI disks, Oldworld, installation booted
via BootX).

I've come across a few problems:

- I need to repartition the SCSI disk. I want to keep Apple-style
  partirions, so I need to use mac-fdisk. First problem: debootstrap
  doesn't offer the choice of the aprtitioning tool. On PowerPC, I guess
  one should be able to use either mac-fdisk or standard fdisk.

- trying to use mac-fdisk from a shell, I get this error:

  /sbin/mac-fdisk: 1: Syntax error: "(" unexpected

  Hmmm.. looks like ash tries to execute mac-fdisk as a shell script?

- from debootstrap, choosing 'partition harddisk' brings up the disk
  selection screen. Selecting /dev/sda brings me back immediately to the
  debootstrap screen, and the log shows fdisk exited normally. But I
  have no chance to see why it exits immediately. I still have to try it
  manually from a shell to see what's up.

FWIW, this is using my own 2.4.16 kernel since I need special stuff in
the kernel (Promise IDE controller).

Thanks, and cheers

Michel

PS I haven't looked, but I suppose LVM tools are not suported on bf?

-
Michel Lanners |  " Read Philosophy.  Study Art.
23, Rue Paul Henkes|Ask Questions.  Make Mistakes.
L-1710 Luxembourg  |
email   [EMAIL PROTECTED]|
http://www.cpu.lu/~mlan| Learn Always. "


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

end-of-story (USB keyboard support on complicated hardware)

[Eduard Bloch]

> > And now tell, how should this be used? Initrd is on the second floppy,
> > syslinux and the kernel is on the first. The default behaviour is to
> > load the kernel from the main disk, and not do anything with another
> > exchangeble disks.
> 
> Huh? This works exactly the same way as it does now.  You put in the

It does not for me. It works the same was as usuall: loads and starts
the kernel immediately, no initrd loading.

> boot disk first, then when it comes around to load the initrd, it
> prompts you and you put in the second disk.

Did you test it?

> > drivers/block/rd.c, and it still would tell you to change the disk (before
> > the keyboard driver is loaded). YOU ARE THE MAINTAINER, YOU SHOULD KNOW
> > THIS.
> 
> No it wouldn't, for the same reason why it doesn't prompt you for a root
> disk in the case of a CD with our resc2880 file.

Recently, I was able to test USB keyboard emulation
on different machines. On my system, it fails in most cases (that is why
I wanted to have the drivers). Sometimes but very seldom, the keyboard
wakes up after some time and IMHO only when the kernel which is running
does not have any USB support (weird, I know). Similar on another box
(Epox boards). Suprisingly, it works on another machine flawlessly. So I
assume there is something in the linux kernel which confuses the
hardware, since the emulation works flawless under DOS.

Okay, I am fed up with this conversation. If you don't like my
suggestion, okay. I managed to get USB support in current BFs, so it
will work for users with similar problems, even if not with _your_
kernels. It does not work with floppy disks, but the users with
legacy-free systems will probably not have any floppy drives though.

Gruss/Regards,
Eduard.
-- 
 Und mal wieder ein paar Pakete, die sich nicht mal installieren
lassen
 Ich kanns nicht verstehen.
 * Alfie . o O ( .. zumindest solange nicht, bis es mir mal passiert ist )
  -- #debian.de


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