> But why hurry it? The debian dependency system lets you
> upgrade the bits and pieces you want and leave the ones that
> work alone. Upgrade the packages you need.
> apt-get update
> apt-get --simulate install pkg1 pkg2 pkg3
> .. and then if it looks OK ...
> apt-get install pkg1 pkg2 pkg
> But why hurry it? The debian dependency system lets you
> upgrade the bits and pieces you want and leave the ones that
> work alone. Upgrade the packages you need.
> apt-get update
> apt-get --simulate install pkg1 pkg2 pkg3
> .. and then if it looks OK ...
> apt-get install pkg1 pkg2 pk
> But why hurry it? The debian dependency system lets you
> upgrade the bits and pieces you want and leave the ones that
> work alone. Upgrade the packages you need.
> apt-get update
> apt-get --simulate install pkg1 pkg2 pkg3
> .. and then if it looks OK ...
> apt-get install pkg1 pkg2 pkg
> > > - What output is produced if you run "X -probeonly" ?
> > "bash: X: command not found"
> 1) /usr/X11R6/bin is not on your path. Not surprising in single user
mode.
> 2) does it run when you give it an explicit path to X ?
Yes. So much to learn about Linux!
A ton of text whining about NEOM
> But why hurry it? The debian dependency system lets you
> upgrade the bits and pieces you want and leave the ones that
> work alone. Upgrade the packages you need.
> apt-get update
> apt-get --simulate install pkg1 pkg2 pkg3
> .. and then if it looks OK ...
> apt-get install pkg1 pkg2 pk
> > > - What output is produced if you run "X -probeonly" ?
> > "bash: X: command not found"
> 1) /usr/X11R6/bin is not on your path. Not surprising in single user
mode.
> 2) does it run when you give it an explicit path to X ?
Yes. So much to learn about Linux!
A ton of text whining about NEO
> Well, you might take a "package pools" approach - rescue your own control
> files to a clas of apps or utilities, remove it entirely, use the
> packaging system to reintroduce the pool, and then look at the control
> files that come with the "standard" kit and apply only the changes you
> need ba
Sure appreciate the help!
Remembering that I am in "Single" mode, does that kill off some
stuff like "Safe Mode" in M$ Windows?
> - What output is produced if you run "X -probeonly" ?
"bash: X: command not found"
> - Which X server you are using (or : trying to use)
The default, left over from
> Well, you might take a "package pools" approach - rescue your own control
> files to a clas of apps or utilities, remove it entirely, use the
> packaging system to reintroduce the pool, and then look at the control
> files that come with the "standard" kit and apply only the changes you
> need b
Sure appreciate the help!
Remembering that I am in "Single" mode, does that kill off some
stuff like "Safe Mode" in M$ Windows?
> - What output is produced if you run "X -probeonly" ?
"bash: X: command not found"
> - Which X server you are using (or : trying to use)
The default, left over fro
> I made my laptop my principle machine years ago. I've never looked back.
> Be seeing you, norm
I have been using a laptop as a "desktop replacement" for many years, and
according to technology media reports such is the wave of the future.
As for Linux versus M$ Windows products -- efficient res
> I made my laptop my principle machine years ago. I've never looked back.
> Be seeing you, norm
I have been using a laptop as a "desktop replacement" for many years, and
according to technology media reports such is the wave of the future.
As for Linux versus M$ Windows products -- efficient re
I went from Progeny to Unstable and PCMCIA works fine.
Also loaded 2.4.14 ... then my troubles started with X. Have
not yet even looked at sound which has never worked under
Progeny-Debian, though it did with Stormix.
Think I may load 2.4.15 and hope that whatever X bug was
introduced in 2.4.14 w
I went from Progeny to Unstable and PCMCIA works fine.
Also loaded 2.4.14 ... then my troubles started with X. Have
not yet even looked at sound which has never worked under
Progeny-Debian, though it did with Stormix.
Think I may load 2.4.15 and hope that whatever X bug was
introduced in 2.4.14
My HP OmniBook 4100 uses the CS4237B chip.
http://www.alsa-project.org/alsa-doc/alsa-howto/x834.htm
CS4235,CS4236,CS4236B,CS4237B,CS4238B,CS4239.
Module snd-card-cs4236.o for soundcards based on CS4235, CS4236,
CS4236B, CS4237B, CS4238B, CS4239 chips. This Module supports
up to 8 cards. This modu
My HP OmniBook 4100 uses the CS4237B chip.
http://www.alsa-project.org/alsa-doc/alsa-howto/x834.htm
CS4235,CS4236,CS4236B,CS4237B,CS4238B,CS4239.
Module snd-card-cs4236.o for soundcards based on CS4235, CS4236,
CS4236B, CS4237B, CS4238B, CS4239 chips. This Module supports
up to 8 cards. This mod
> > "make-kpkg" complains that I am not is the top level linux kernel
> > source directory. I tried to launch it from /, /boot, /usr/src to no
avail.
> >
> > I looked around and still couldn't find linux-2.4.12.gz anywhere.
>
> apt-get update
> apt-get install kernel-package
> glen
Did these two s
> > "make-kpkg" complains that I am not is the top level linux kernel
> > source directory. I tried to launch it from /, /boot, /usr/src to no
avail.
> >
> > I looked around and still couldn't find linux-2.4.12.gz anywhere.
>
> apt-get update
> apt-get install kernel-package
> glen
Did these two
> Here is my steps for install (btw, who ever maintains the GRUB docs,
> I think I might be willing to write a first draft install guide):
>
> Partitions:
> /dev/hda1 - /boot
> /dev/hda2 - /root
>
> * grub-install /dev/hda
> It warns me it can't find /dev/hda, but it creates a
> /boot/grub/device
> Here is my steps for install (btw, who ever maintains the GRUB docs,
> I think I might be willing to write a first draft install guide):
>
> Partitions:
> /dev/hda1 - /boot
> /dev/hda2 - /root
>
> * grub-install /dev/hda
> It warns me it can't find /dev/hda, but it creates a
> /boot/grub/devic
I am trying the comand (see below) sequence just to see if it works
better than the Progeny->Woody version that repeatedly fails to
support pcmcia on my laptop.
This is an upgrade to Unstable.
There is one change, on line two "deps" needs to be "depends".
Also, under "Configuring PCMCIA" it asks
I am trying the comand (see below) sequence just to see if it works
better than the Progeny->Woody version that repeatedly fails to
support pcmcia on my laptop.
This is an upgrade to Unstable.
There is one change, on line two "deps" needs to be "depends".
Also, under "Configuring PCMCIA" it ask
> Progeny to Woody howto
> http://www.debianplanet.org/debianplanet/article.php?sid=450
Been using that one. It is incomplete since it fails to mention the
trashing
of pcmcia, among other things.
> Progeny to unstable
> http://www.debianplanet.org/debianplanet/article.php?sid=414
> scott
No
> Progeny to Woody howto
> http://www.debianplanet.org/debianplanet/article.php?sid=450
Been using that one. It is incomplete since it fails to mention the
trashing
of pcmcia, among other things.
> Progeny to unstable
> http://www.debianplanet.org/debianplanet/article.php?sid=414
> scott
N
> Note: I'm re-posting this to the debian-laptops list too, in case
> someone there has any ideas.
> Hubert
>
> OK. If you're still on 2.2.18, then the old pcmcia-modules should still
> work. My guess is that Woody and Progeny have a different set of
> startup scripts, and somehow the upgrade cau
> Note: I'm re-posting this to the debian-laptops list too, in case
> someone there has any ideas.
> Hubert
>
> OK. If you're still on 2.2.18, then the old pcmcia-modules should still
> work. My guess is that Woody and Progeny have a different set of
> startup scripts, and somehow the upgrade ca
Just upgraded from Progeny-Debian 2.2.18 to Woody, or
so I thought.
When I boot 2.2.18 still shows up but Grub has changed appearance
as has Gnome.
Problems:
Cannot access my pcmcia nic (3Com 589c which worked perfectly
prior to the upgrade).
When I remove then re-insert the card there are no
Just upgraded from Progeny-Debian 2.2.18 to Woody, or
so I thought.
When I boot 2.2.18 still shows up but Grub has changed appearance
as has Gnome.
Problems:
Cannot access my pcmcia nic (3Com 589c which worked perfectly
prior to the upgrade).
When I remove then re-insert the card there are n
28 matches
Mail list logo
