headers
Nick Moffitt | 1 Jan 2003 02:14

bug#225: Driver request.

package: linux

----- Forwarded message from Jeff Mock <jeff <at> mock.com> -----

At 04:38 PM 12/31/2002 -0800, Nick Moffitt wrote:
>[discussion moved to lnx-bbc-devel]
>
>begin  Jeff Mock  quotation:
>> I supposed everyone has their favorite feature, I just downloaded a
>> build from 12/31.  I quite like it and I have two little
>> configuration features requests that would make me happy...
>>
>>   Add orinoco_pci for PRISM2.5 wireless support.  For me, my T23
>>   Thinkpad with built-in wireless (mini-PCI, not PCMCIA) needs this.
>
>        Do you mean to say that the module is not included, or that
>discover does not detect and load it?  Are you not able to modprobe it
>from the shell?

The module is not included.  I believe the kernel config option is
CONFIG_PCI_HERMES.  This adds orinoco_pci.o to orinoco.o and orinoco_cs.o.
I think it's quite small.

I agree with the trimming that you've done on all of the possible
PRISM wireless driver possibilities, except that the pci version
shows up on a lot of machines with the PRISM 2.5 chip.

I am using
   http://www.lnx-bbc.org/builds/bbc-2002-12-31T00:31:13-0800.iso
(Continue reading)

Permalink | Reply | 0 comments |
headers
Nick Moffitt | 1 Jan 2003 02:16

bug#226: should include all vesa modes

package: syslinux

----- Forwarded message from Jeff Mock <jeff <at> mock.com> -----

At 04:38 PM 12/31/2002 -0800, Nick Moffitt wrote:
>begin  Jeff Mock  quotation:
>>   Add a 1280x1024 boot option.  I think this is the only VESA video
>>   resolution not in the boot options.  For me... my T23 with a
>>   1400x1050 screen looks wicked horrible at 1024x768, but very nice
>>   at 1280x1024.
>
>        Sneakums has toyed with this in the past, and might be best
>suited to adding this to our syslinux configs.  I would agree that the
>options should at least be present.
>
>> The great thing over 1.618 is that the old version would hang during
>> boot on my T23, the latest build works great.
>
>        That is reassuring!  Thank you for testing it out!  Which
>build did you use, precisely?

I am using
   http://www.lnx-bbc.org/builds/bbc-2002-12-31T00:31:13-0800.iso

jeff

----- End forwarded message -----

--

-- 
A: No.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Sean Neakums | 1 Jan 2003 02:21

bug#225: [Lnx-bbc-devel] Re: Request for lnx-bbc

commence  Jeff Mock quotation:

> At 04:38 PM 12/31/2002 -0800, Nick Moffitt wrote:
>>[discussion moved to lnx-bbc-devel]
>>
>>begin  Jeff Mock  quotation:
>> >   Add orinoco_pci for PRISM2.5 wireless support.  For me, my T23
>> >   Thinkpad with built-in wireless (mini-PCI, not PCMCIA) needs this.
>>
>>         Do you mean to say that the module is not included, or that
>>discover does not detect and load it?  Are you not able to modprobe it
>>from the shell?
>
>
> The module is not included.  I believe the kernel config option is
> CONFIG_PCI_HERMES.  This adds orinoco_pci.o to orinoco.o and orinoco_cs.o.
> I think it's quite small.

Note that our orinoco_cs.o and orinoco.o come from pcmcia-cs, and not
the kernel proper.

--

-- 
                   BACK OFF ... I'VE GOT AN LNX-BBC
Permalink | Reply | 0 comments |
headers
Jeff Mock | 1 Jan 2003 02:40

bug#225: [Lnx-bbc-devel] Re: Request for lnx-bbc

Now you're beyond me, I've only built the kernel drivers
for wireless.  It makes sense that the PCMCIA package doesn't have
the PCI drivers for the Prism.

jeff

At 01:21 AM 1/1/2003 +0000, Sean Neakums wrote:
>commence  Jeff Mock quotation:
>
> > At 04:38 PM 12/31/2002 -0800, Nick Moffitt wrote:
> >>[discussion moved to lnx-bbc-devel]
> >>
> >>begin  Jeff Mock  quotation:
> >> >   Add orinoco_pci for PRISM2.5 wireless support.  For me, my T23
> >> >   Thinkpad with built-in wireless (mini-PCI, not PCMCIA) needs this.
> >>
> >>         Do you mean to say that the module is not included, or that
> >>discover does not detect and load it?  Are you not able to modprobe it
> >>from the shell?
> >
> >
> > The module is not included.  I believe the kernel config option is
> > CONFIG_PCI_HERMES.  This adds orinoco_pci.o to orinoco.o and orinoco_cs.o.
> > I think it's quite small.
>
>Note that our orinoco_cs.o and orinoco.o come from pcmcia-cs, and not
>the kernel proper.
>
>--
>                    BACK OFF ... I'VE GOT AN LNX-BBC
(Continue reading)

Permalink | Reply | 0 comments |
headers
LNX-BBC bug Tracking System | 1 Jan 2003 04:25

bug#226: marked as done (should include all vesa modes)

Your message dated Tue, 31 Dec 2002 19:20:15 -0800
with message-id <E18TZQV-0008LL-00 <at> gar.lnx-bbc.org>
and subject line Bug modified from CVS checkin
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.)

Nick Moffitt
(administrator, LNX-BBC bugs database)

--------------------------------------
Received: (at submit) by bugs.lnx-bbc.org; 1 Jan 2003 01:16:03 +0000
From nick <at> zork.net Tue Dec 31 17:16:03 2002
Received: from zork.zork.net ([66.92.188.166] ident=mail)
	by gar.lnx-bbc.org with esmtp (Exim 3.36 #1 (Debian))
	id 18TXUJ-0007cj-00
	for <submit <at> bugs.lnx-bbc.org>; Tue, 31 Dec 2002 17:16:03 -0800
Received: from nick by zork.zork.net with local (Exim 3.35 #1 (Debian))
	id 18TXUn-0007Wp-00; Tue, 31 Dec 2002 17:16:33 -0800
Date: Tue, 31 Dec 2002 17:16:33 -0800
From: Nick Moffitt <nick <at> zork.net>
To: submit <at> bugs.lnx-bbc.org
Subject: should include all vesa modes
Message-ID: <20030101011633.GQ11839 <at> zork.net>
(Continue reading)

Permalink | Reply | 0 comments |
headers
LNX-BBC bug Tracking System | 1 Jan 2003 05:20

bug#195: marked as done (VESA server resolution)

Your message dated Tue, 31 Dec 2002 20:17:57 -0800
with message-id <E18TaKL-0001kq-00 <at> gar.lnx-bbc.org>
and subject line Bug modified from CVS checkin
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.)

Nick Moffitt
(administrator, LNX-BBC bugs database)

--------------------------------------
Received: (at submit) by bugs.lnx-bbc.org; 21 Nov 2002 00:46:35 +0000
From schoen <at> zork.net Wed Nov 20 16:46:35 2002
Received: from zork.zork.net ([66.92.188.166] ident=mail)
	by gar.lnx-bbc.org with esmtp (Exim 3.36 #1 (Debian))
	id 18EfUI-0003KA-00
	for <submit <at> bugs.lnx-bbc.org>; Wed, 20 Nov 2002 16:46:34 -0800
Received: from schoen by zork.zork.net with local (Exim 3.35 #1 (Debian))
	id 18EfUf-00037i-00; Wed, 20 Nov 2002 16:46:57 -0800
Date: Wed, 20 Nov 2002 16:46:57 -0800
From: Seth David Schoen <schoen <at> loyalty.org>
To: submit <at> bugs.lnx-bbc.org
Subject: VESA server resolution
Message-ID: <20021121004657.GF14546 <at> zork.net>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Anand Kanagala | 1 Jan 2003 23:46

bug#227: Package: flex

Package: flex

It appears that the path to usr/bin/install is missing the initial /

-anand

------------------------

make[1]: Entering directory `/home/anand/downloads/gar/devel/flex'
[===== NOW BUILDING:    flex-2.5.4      =====]
        [fetch] complete for flex.
        [checksum] complete for flex.
        [extract] complete for flex.
        [patch] complete for flex.
        [configure] complete for flex.
        [build] complete for flex.
 ==> Running make install in work/flex-2.5.4
make[2]: Entering directory `/home/anand/downloads/gar/devel/flex/work/flex-2.5.4'
/bin/sh ./mkinstalldirs \
  /tmp/gar//bin /tmp/gar//lib /tmp/gar/../../tmp/build/include /tmp/gar/../../tmp/build/man
rm -f /tmp/gar/../../tmp/build/man/flexdoc.1
usr/bin/install -c -m 644 ./flex.1 /tmp/gar/../../tmp/build/man/flex.1
make[2]: usr/bin/install: Command not found
make[2]: *** [install.man] Error 127
make[2]: Leaving directory `/home/anand/downloads/gar/devel/flex/work/flex-2.5.4'
make[1]: *** [install-work/flex-2.5.4/Makefile] Error 2
make[1]: Leaving directory `/home/anand/downloads/gar/devel/flex'
make: *** [dep-../../devel/flex] Error 2
Permalink | Reply | 6 comments |
headers
The One True Dave Barry | 2 Jan 2003 03:13

bug#227: bug#227: Package: flex

Quothe Anand Kanagala <anand <at> xebeo.com>, on Wed, Jan 01, 2003:
> Package: flex
> 
> It appears that the path to usr/bin/install is missing the initial /
> 

What distro are you building on?  I have observed this behavior on
Slackware.  You might try our chroot setup for building a bbc.
Instructions are available at:  

http://lnx-bbc.org/chroot.html.

We use Debian testing for our build setup, and this problem does not
occur there.

--

-- 
=================-------------------------------=========================
| Dave Barry	| All the freaky people make	| dave <at> zork.net         |
| ...  		| the beauty of the world.	| http://psax.org/~dave |
|		|	--Michael Franti	|			|
=================-------------------------------=========================
Permalink | Reply | 4 comments |
headers
Paul Gray | 2 Jan 2003 03:26
Picon

Re: [Lnx-bbc-devel] bug#227: bug#227: Package: flex

On Wed, 1 Jan 2003, The One True Dave Barry wrote:

> Quothe Anand Kanagala <anand <at> xebeo.com>, on Wed, Jan 01, 2003:
> > Package: flex
> >
> > It appears that the path to usr/bin/install is missing the initial /
> >
>
> What distro are you building on?  I have observed this behavior on
> Slackware.  You might try our chroot setup for building a bbc.
> Instructions are available at:
>
> http://lnx-bbc.org/chroot.html.
>

Sounds like either ac_dir is being messed up (in flex' configure) with
your PATH setting, or INSTALL is being clobbered.

Can you cd into devel/flex and issue

"make clean && INSTALL='/usr/bin/install -c' make configure"

Then run make build.  Does that work?
If so, it might be as simple as adding:

 INSTALL = $(shell which install)
 CONFIGURE_ARGS = 'INSTALL=$(INSTALL)'

to the Makefile.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Jeff Mock | 2 Jan 2003 03:51

bug#222: Package: gar

At 11:09 AM 12/31/2002 -0800, Nick Moffitt wrote:
>begin  Jeff Mock  quotation:
> > Package: gar
> >
> > Hi, I've always enjoyed the old version of the lnx-bbc, I'm so happy
> > to hear that your doing a 2.0 version.  I'm hip to test so I'm doing
> > a cvs source build for the first time.
> >
> > I'm running on a pretty vanilla redhat 8.0 machine, I got the cvs
> > tree this morning (12/31) and it dies pretty quickly with some
> > nonsense C compiler errors as follows:
>
>         We currently use debian testing as our build platform, and our
>release schedule doesn't allow us to accomodate a lot of the unstable
>stuff that goes on in Red Hat releases.  If you're eager to run a
>build on your own, check out the file "chroot.txt" in the base gar
>directory, or head over to http://lnx-bbc.org/chroot.html for the HTML
>version.

Well. I've got to say that I was pretty skeptical about
the whole chroot thing, but it works really well.  It's an
interesting idea for complex build environments.

I loaded the chroot Debian image onto a redhat 8.0 system and it
works great.  The only thing missing from the Debian chroot image
is cvs, but it's no problem to run cvs outside the chroot world.

I built the current top of the tree and was pleased to see the
1280x1024 boot option, which works well...
(Continue reading)

Permalink | Reply | 0 comments |

Gmane