-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2001-05-09 20:07, Garry Roseman at [EMAIL PROTECTED] wrote:
> A related question: how can one determine what options were set
> when any given kernel was compiled? Specifically, is there a way
> to find out what options produced the stock Debia
I compiled the Debian 2.2.19 kernel on my PowerMac and found that with my
new kernel the usb keyboard generates weird characters. The stock 2.2.19
kernel works fine but I don't know what magic combination of USB and Mac
Driver options gives that correct behavior. Having read through the
docum
On Wed, May 09, 2001 at 06:13:23PM +0200, Lorenzo De Vito wrote:
> Yesterday, my RISC, with Linux installed, was corrupted by a command
> launched from superuser by my brother (a mistake), the command was:
> (root don't have password)
^^
WHY?
this is exceedingly stupid
OK, solved.
On 9 May, this message from To: Debian-powerpc echoed through cyberspace:
> Today my X server stoped working, and complained about not finding the
> 'fixed' font. I got it started finally by pointing it at some other Unix
> box' font server, whihc has 'fixed' as an alias in
> fonts/m
Hi all,
Today my X server stoped working, and comlained about not finding the
'fixed' font. I got it started finally by pointing it at some other Unix
box' font server, whihc has 'fixed' as an alias in
fonts/misc/fonts.alias.
And indeed, I don't have a fonts.alias in my fonts/misc directory. I'm
Hello,
I've two questions.
I'm looking for some advices for my network configuration. Here is the physical
configuration : I've a Zyxel ADSL router wired on the Ethernet port (eth0).
This router has a dhcp buit-in, and it have to give me an IP address. The IP
address of the router is 192.168.1
Yesterday, my RISC, with Linux installed, was corrupted by a command
launched from superuser by my brother (a mistake), the command was:
(root don't have password)
$ su
# /bin
# chmod 777 *
at this point if I try to enter like user to root with "su":
$ su
password: (??password, but there isn
Jason E. Stewart wrote:
Having struggled quite a bit with getting video working on the
external video of the pismo, I have been wondering a lot about all the
different video drivers and what their relation is to one another.
If someone in the know could give a brief description, or point me t
Rob Pfile wrote:
>
> Bastien Nocera writes:
> >
> > [eject -v]
> >
> > Post the result here when you have something
> >
>
> my symlinks are wrong:
I tried to point that out, but I don't think anyone was
listening
> so that problem is solved. i'll reboot without ide-scsi and see how
> c
On 09 May 2001 13:19:22 +0200, Michael Schmitz wrote:
> > > hdx=scsi is necessary to let cdparanoia or other tools access the audio
> > > data on the device (though you'd think that it should be possible using
^^^
> > > IDE ATAPI commands directly). Without a conex
Michael Schmitz writes:
> > > Does anyone have a moment to explay exactly why this makes it work?
> >
> > I think the reason is that there is no IDE cdrom driver. there are,
>
> BS. IDE CDROM drivers have been around for like three or four years in the
> Linux kernel. That's approximately fo
"Michel Dänzer" <[EMAIL PROTECTED]> writes:
> Doesn't work on my Pismo, of course that could also be due to missing mixer
> functionality.
Sorry to be ignorant, what's the issue with the mixer on the Pismo?
Thanks,
jas.
Bastien Nocera writes:
>
> [eject -v]
>
> Post the result here when you have something
>
my symlinks are wrong:
[EMAIL PROTECTED] ~]$ eject -v /dev/scd0
eject: using default device `cdrom'
eject: device name is `cdrom'
eject: expanded name is `/dev/cdrom'
eject: `/dev/cdrom' is a link to `
"Michel Dänzer" <[EMAIL PROTECTED]> writes:
> Michael Schmitz wrote:
> >
> > > > Could you post your kernel options? This sounds like you're not using
> > > > the aty1288fb driver.
> > >
> > > You can easily verify that by catting /proc/fb.
> >
> > That would probably find aty128fb. :-) My bad.
Michael Schmitz wrote:
> IDE CDs have analog output lines for audio data (so have SCSI drives but
> if you keep them in regular external drive boxes these wires aren't
> usually connected on the back panel). The audio lines are connected to the
> soundcard or MB sound HW in PCs (a small jack that
Michael Schmitz wrote:
>
> > > Could you post your kernel options? This sounds like you're not using
> > > the aty1288fb driver.
> >
> > You can easily verify that by catting /proc/fb.
>
> That would probably find aty128fb. :-) My bad. Another post revealed the
> user had used the novideo option,
> > Could you post your kernel options? This sounds like you're not using the
> > aty1288fb driver.
>
> You can easily verify that by catting /proc/fb.
That would probably find aty128fb. :-) My bad. Another post revealed the
user had used the novideo option, bypassing the aty128fb init.
Now why X
> Fine, thanks for the history lesson. enlighten us as to how to force
> linuxppc to recognize the cdrom drive in the tibook and attach an IDE
> cdrom driver to it.
According to my guesses that may take a soldering iron. But there's plenty
of information you can use to determine if, in fact, the a
> > I think the reason is that there is no IDE cdrom driver. there are,
> > however, lots of scsi drivers in the linux kernel, probably inherited
> > from other *nixes (BSD?). SCSI has been around for a long time and is
> > very popular, so that probably explains the wealth of drivers.
>
> I don't
> > Does anyone have a moment to explay exactly why this makes it work?
>
> I think the reason is that there is no IDE cdrom driver. there are,
BS. IDE CDROM drivers have been around for like three or four years in the
Linux kernel. That's approximately forever. ide-cd.c has the ollowing
changelog
On Wed, 9 May 2001, Michael Schmitz wrote:
> > >>ioctl FBIOPUT_VSCREENINFO: Invalid argument
> > >Use 15?
> >
> > Any depth greater than 8 gives the same error.
>
> Could you post your kernel options? This sounds like you're not using the
> aty1288fb driver.
You can easily verify that by ca
> > hdx=scsi is necessary to let cdparanoia or other tools access the audio
> > data on the device (though you'd think that it should be possible using
> > IDE ATAPI commands directly). Without a conextion from the CD audio out to
>
> Are you talking about the TiPB or PowerPC/PowerMacs in general ?
> >>ioctl FBIOPUT_VSCREENINFO: Invalid argument
> >Use 15?
>
> Any depth greater than 8 gives the same error.
Could you post your kernel options? This sounds like you're not using the
aty1288fb driver.
Michael
> > Nope, it's actuakky pretty difficult to implement and probably
> > not worth the hassle (at least not for anyone who'll never use
> > that feature, sorry this is how free software works).
>
> No, I know. I'm half inclined to tackle this myself, but I'm
> currently too interested in spending tim
I've updated the penguinppc mozilla archive to 0.9
deb http://penguinppc.org/~eb/mozilla ./
--
Ethan Benson
http://www.alaska.net/~erbenson/
pgp6CwRasUrRT.pgp
Description: PGP signature
Um... oops?
I'm sorry. I was working off of Herbert Xu's i386 configs, and when I
made it capable of non-initrd booting I completely missed this.
For those who don't read -bugs-dist: Be careful if you install the
kernel image 2.4.4 packages I just uploaded! I accidentally left ext2
as a module
26 matches
Mail list logo
