Hugo Vanwoerkom wrote:
Hi,
I have 2 internal ATA HDD's and 2 disks in external USB enclosures.
When you boot (this is Sid) the 2 USB disks report their presence
between the messages:
'Loading, please wait...'
and
'Init 2.86 booting'
in the very beginning of the boot process.
Now the funny
On Saturday 16 January 2010 12:33:32 Hugo Vanwoerkom wrote:
This has been solved by Ben Hutchings and was reported as
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534324
The solution was to put ums-cypress in /etc/initramfs/modules and rerun
update-initramfs -u for that kernel. Linux
On Sun December 27 2009, Stan Hoeppner wrote:
I do have ecryptfs a Private filesystem, but ecryptfs was under file
systems ( I think..) I did find that.
Have you tried pressing H for Help, on each feature or feature class?
Note what help tells you. In many/most cases Help will assist you
On Sat, 26 Dec 2009 23:53:55 -0600
Stan Hoeppner s...@hardwarefreak.com wrote:
...
Have you tried pressing H for Help, on each feature or feature class? Note
what help tells you. In many/most cases Help will assist you in figuring out
whether you need a given feature or not.
Many -
On Fri December 25 2009, Stan Hoeppner wrote:
-rw-r--r-- 1 root root 18548960 2009-12-25 05:58
linux-image-2.6.31.9_custom.1.0_i386.deb
18MB? Yikes! Am I reading that correctly? My latest custom kernel is:
-rw-r--r-- 1 root src 1.5M Dec 8 13:29
On Fri December 25 2009, Stan Hoeppner wrote:
18MB? Yikes! Am I reading that correctly? My latest custom kernel is:
-rw-r--r-- 1 root src 1.5M Dec 8 13:29
linux-image-2.6.31.1_custom.greer.sata.1.3_i386.deb
ok, so I go through and delete stuff ( make menuconfig). When I get to an
entry
On Fri December 25 2009, Celejar wrote:
Absolutely. I'm just warning you to be prepared for a lot of very
frustrating why can't the kernel find my root filesystem? and why
has this piece of HW / SW suddenly stopped working.
ok, so it gets deep in those menus...
network, device drivers,
On Sat, 26 Dec 2009 07:47:10 -0500
Paul Cartwright a...@pcartwright.com wrote:
...
[Warning: I'm no expert, so take everything I write with a grain of
salt.]
kernel hacking??
Various options that control the behavior of the kernel, for debugging,
testing, troubleshooting, etc. You can
On Sat December 26 2009, Celejar wrote:
kernel hacking??
Various options that control the behavior of the kernel, for debugging,
testing, troubleshooting, etc. You can generally ignore this section
and turn things off, although there are some useful things there (Magic
SysRq, various
On Fri December 25 2009, Celejar wrote:
Absolutely. I'm just warning you to be prepared for a lot of very
frustrating why can't the kernel find my root filesystem? and why
has this piece of HW / SW suddenly stopped working.
yeah, found that one... something about can't boot from (0,0)..
Paul Cartwright put forth on 12/26/2009 6:47 AM:
On Fri December 25 2009, Celejar wrote:
Absolutely. I'm just warning you to be prepared for a lot of very
frustrating why can't the kernel find my root filesystem? and why
has this piece of HW / SW suddenly stopped working.
ok, so it gets
Paul Cartwright put forth on 12/26/2009 5:32 AM:
this DELL box is my first PC with SATA. When I opened it up a while back to
add a 2nd HD, THAT is when I found out it was SATA, and my old drives
wouldn't work! but I don't remember looking at the CDROM cables..
Sounds like the perfect time
On Thu December 24 2009, Stan Hoeppner wrote:
Remember what many of us have said: Building a custom kernel is as much
about learning as it is about accomplishing. Becoming proficient at
building a custom kernel can take a while, sometimes months, sometimes
years, depending on one's aptitude
On Thu December 24 2009, Stan Hoeppner wrote:
make[1]: Leaving directory
`/home/pbc/Documents/software/linux-2.6.31.9/linux-2.6.31.9/Documentation
/lguest' make: *** [debian/stamp/build/kernel] Error 2
http://cakebox.homeunix.net/wordpress/?p=100
THAT I can follow!
my googling didn't find
On Thu December 24 2009, Celejar wrote:
relating to doing so. When compiling one's first custom kernel one
should start with _ONLY_ the functionality one needs. Then build things
up from there as you need more abilities from you kernel. ;)
But I'd add that it's very easy to disable
Paul Cartwright put forth on 12/25/2009 4:07 AM:
this is the learning part.. knowing what you need, what you MIGHT need, and
what you don't have to have to make it work..
You've just passed the first milestone, and seem to be continuing down the right
path in your kernel building journey. :)
On Fri, 25 Dec 2009 05:07:55 -0500
Paul Cartwright a...@pcartwright.com wrote:
On Thu December 24 2009, Celejar wrote:
relating to doing so. When compiling one's first custom kernel one
should start with _ONLY_ the functionality one needs. Then build things
up from there as you need
On 09-12-25 09:04:42, Celejar wrote:
On Fri, 25 Dec 2009 05:07:55 -0500
...
this is the learning part.. knowing what you need, what you MIGHT
need, and what you don't have to have to make it work..
Absolutely. I'm just warning you to be prepared for a lot of very
frustrating why can't
On Fri, 25 Dec 2009 10:35:59 -0500
Tony Nelson tonynel...@georgeanelson.com wrote:
On 09-12-25 09:04:42, Celejar wrote:
On Fri, 25 Dec 2009 05:07:55 -0500
...
this is the learning part.. knowing what you need, what you MIGHT
need, and what you don't have to have to make it work..
On Fri December 25 2009, Stan Hoeppner wrote:
You've just passed the first milestone, and seem to be continuing down the
right path in your kernel building journey. :)
after editing that file, and doing the steps, I now have my first custom
kernel:
-rw-r--r-- 1 root root 18548960 2009-12-25
On Fri December 25 2009, Celejar wrote:
Absolutely. I'm just warning you to be prepared for a lot of very
frustrating why can't the kernel find my root filesystem? and why
has this piece of HW / SW suddenly stopped working.
right.. I get it..
One thing I'd recommend, although I've never
On Fri December 25 2009, Celejar wrote:
How about: build a kernel with everything as modules, boot it, look at
the output of lsmod, then build a kernel with (at least) those modules?
Probably a good idea, but note that connecting kernel module names with
the relevant kernel config options
Paul Cartwright put forth on 12/25/2009 6:56 PM:
-rw-r--r-- 1 root root 18548960 2009-12-25 05:58
linux-image-2.6.31.9_custom.1.0_i386.deb
18MB? Yikes! Am I reading that correctly? My latest custom kernel is:
-rw-r--r-- 1 root src 1.5M Dec 8 13:29
On Tue December 22 2009, Celejar wrote:
Exactly. And you can turn off all the sound card and video drivers
except the one(s) you actually need, and the same for networking hw,
etc.
so I was reading this:
http://www.wowway.com/~zlinuxman/Kernel.htm
which is about the same..
I ran these
Paul Cartwright put forth on 12/23/2009 7:47 PM:
On Wed December 23 2009, Celejar wrote:
I'm not sure exactly what you've tried, but if you're building the
kernel itself from source, you shouldn't be installing any header
packages - they're only for when you need to build stuff against a
Paul Cartwright put forth on 12/24/2009 12:04 PM:
On Tue December 22 2009, Celejar wrote:
Exactly. And you can turn off all the sound card and video drivers
except the one(s) you actually need, and the same for networking hw,
etc.
so I was reading this:
On Thu, 24 Dec 2009 20:53:31 -0600
Stan Hoeppner s...@hardwarefreak.com wrote:
...
relating to doing so. When compiling one's first custom kernel one should
start
with _ONLY_ the functionality one needs. Then build things up from there as
you
need more abilities from you kernel. ;)
But
Paul Cartwright put forth on 12/22/2009 4:36 PM:
On Tue December 22 2009, Celejar wrote:
I think I have done this before, I think I tried it for a 64bit kernel,
for my Duo-Core processor, but it didn't turn out well. Seems to me the
configure' part takes 2 days, or way too many options. I seem
On Wed December 23 2009, Stan Hoeppner wrote:
Paul, have you read this yet? It will be very helpful.
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html
I was doing it a different way, getting the kernel from kernel.org. This looks
a little different.. I'll take a look, thanks!
Paul Cartwright put forth on 12/23/2009 3:46 PM:
On Wed December 23 2009, Stan Hoeppner wrote:
Paul, have you read this yet? It will be very helpful.
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html
I was doing it a different way, getting the kernel from kernel.org. This
On Wed December 23 2009, Stan Hoeppner wrote:
I get my source from kernel.org also. But there are instructions in that
document that tell you how to install from kernel.org sources The Debian
Way.
I see that, but I'm still having problems..
Back in the day I was exclusively using Debian
On Wed December 23 2009, Stan Hoeppner wrote:
Back in the day I was exclusively using Debian kernel sources. At one
point I wanted a newer kernel version than was available via the Debian
mirrors, so after reading in this document that it was possible, I started
getting my source from
On Wed, 23 Dec 2009 20:18:44 -0500
Paul Cartwright a...@pcartwright.com wrote:
On Wed December 23 2009, Stan Hoeppner wrote:
Back in the day I was exclusively using Debian kernel sources. At one
point I wanted a newer kernel version than was available via the Debian
mirrors, so after
On Wed December 23 2009, Celejar wrote:
I'm not sure exactly what you've tried, but if you're building the
kernel itself from source, you shouldn't be installing any header
packages - they're only for when you need to build stuff against a
kernel for which you don't have the source.
I think
On Mon December 21 2009, Celejar wrote:
2) From the appropriate directory, run make menuconfig (or xconfig or
whatever you prefer) and configure appropriately
I think I have done this before, I think I tried it for a 64bit kernel, for my
Duo-Core processor, but it didn't turn out well. Seems
On Mon December 21 2009, Celejar wrote:
1) Faster booting, since irrelevant drivers aren't loaded and won't
spend time probing.
just faster booting, or doesn't it also run faster, since it isn't loaded with
a bunch of PORK?
2) Security - one of these null pointer dereferences that they
On Mon December 21 2009, Celejar wrote:
Yes and no WRT flexibility. Yes because you an choose exactly what does
and does not go into your kernel. No, because once it's built, if you
want to add a new hardware device later, you might have to build a new
kernel. With the modular prebuilt
Paul Cartwright wrote:
On Mon December 21 2009, Celejar wrote:
2) From the appropriate directory, run make menuconfig (or xconfig or
whatever you prefer) and configure appropriately
I think I have done this before, I think I tried it for a 64bit kernel, for my
Duo-Core processor, but it
Andrew Reid wrote:
On Monday 21 December 2009 15:52:29 Hugo Vanwoerkom wrote:
Hi,
I have 2 internal ATA HDD's and 2 disks in external USB enclosures.
When you boot (this is Sid) the 2 USB disks report their presence
between the messages:
'Loading, please wait...'
and
'Init 2.86 booting'
in
On Mon, 21 Dec 2009 23:02:53 -0600
Stan Hoeppner s...@hardwarefreak.com wrote:
Celejar put forth on 12/21/2009 9:13 PM:
I run desktops / laptops, and I always build netfilter - I run
shorewall on all my boxes.
For me, the firewall is always going to be upstream of desktops in a properly
On Tue, 22 Dec 2009 05:36:42 -0500
Paul Cartwright a...@pcartwright.com wrote:
On Mon December 21 2009, Celejar wrote:
2) From the appropriate directory, run make menuconfig (or xconfig or
whatever you prefer) and configure appropriately
I think I have done this before, I think I tried
On Tue, 22 Dec 2009 05:41:22 -0500
Paul Cartwright a...@pcartwright.com wrote:
On Mon December 21 2009, Celejar wrote:
1) Faster booting, since irrelevant drivers aren't loaded and won't
spend time probing.
just faster booting, or doesn't it also run faster, since it isn't loaded
with
On Tue, 22 Dec 2009 05:46:27 -0500
Paul Cartwright a...@pcartwright.com wrote:
On Mon December 21 2009, Celejar wrote:
Yes and no WRT flexibility. Yes because you an choose exactly what does
and does not go into your kernel. No, because once it's built, if you
want to add a new
On Tue December 22 2009, Celejar wrote:
Try 'make menuconfig', or copy over a config file from a running kernel
of the same version.
I downloaded 2.6.32.2 from kernel.org
config file from my kernel? 2.6.26.2 ?
would that work, and what is the config file?
--
Paul Cartwright
Registered Linux
On Tue December 22 2009, Celejar wrote:
I think I have done this before, I think I tried it for a 64bit kernel,
for my Duo-Core processor, but it didn't turn out well. Seems to me the
configure' part takes 2 days, or way too many options. I seem to
remember it asked whether i wanted
On Tue December 22 2009, Celejar wrote:
Unfortunately, there's no easy answer to this one. Read, read, read,
and learn from your mistakes (you *will* make them). To be safe,
always err on the side of caution and enable anything not marked
'experimental' unless you're pretty sure that you
Check the apropriate config from
http://merkel.debian.org/~jurij/
before doing make menuconfig do:
make oldconfig
then
make menuconfig
And I suppose to use tool like make-kpkg
See for example:
http://www.debianhelp.co.uk/kernel2.6.htm
Robert.
Dne Út 22. prosince 2009 23:36:29 Paul
On Tue, 22 Dec 2009 17:26:20 -0500
Paul Cartwright a...@pcartwright.com wrote:
On Tue December 22 2009, Celejar wrote:
Try 'make menuconfig', or copy over a config file from a running kernel
of the same version.
I downloaded 2.6.32.2 from kernel.org
config file from my kernel? 2.6.26.2 ?
On Tue, 22 Dec 2009 17:36:29 -0500
Paul Cartwright a...@pcartwright.com wrote:
On Tue December 22 2009, Celejar wrote:
I think I have done this before, I think I tried it for a 64bit kernel,
for my Duo-Core processor, but it didn't turn out well. Seems to me the
configure' part takes 2
On Tue, 22 Dec 2009 17:38:12 -0500
Paul Cartwright a...@pcartwright.com wrote:
On Tue December 22 2009, Celejar wrote:
Unfortunately, there's no easy answer to this one. Read, read, read,
and learn from your mistakes (you *will* make them). To be safe,
always err on the side of caution
On Tuesday 22 December 2009 07:48:05 Hugo Vanwoerkom wrote:
Andrew Reid wrote:
It's likely the devices aren't being recognized in the initramfs --
possibly they require kernel modules which are not present by default.
But I would think that to be the case of the custom kernel, not the
Hi,
I have 2 internal ATA HDD's and 2 disks in external USB enclosures.
When you boot (this is Sid) the 2 USB disks report their presence
between the messages:
'Loading, please wait...'
and
'Init 2.86 booting'
in the very beginning of the boot process.
Now the funny part: in my homegrown
Hugo Vanwoerkom put forth on 12/21/2009 2:52 PM:
This isn't the first time I've asked this, but nobody seems to have an
answer.
I do: stick with your homegrown kernel.
(From the guy who only uses custom kernels)
--
Stan
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
On Monday 21 December 2009 15:52:29 Hugo Vanwoerkom wrote:
Hi,
I have 2 internal ATA HDD's and 2 disks in external USB enclosures.
When you boot (this is Sid) the 2 USB disks report their presence
between the messages:
'Loading, please wait...'
and
'Init 2.86 booting'
in the very
On Mon December 21 2009, Stan Hoeppner wrote:
I do: stick with your homegrown kernel.
(From the guy who only uses custom kernels)
what would I gain from using a custom kernel, what would it take to
make/install one, ( a how-to?).
for a regular desktop user, web, email... what advantage is
On Mon, 21 Dec 2009 21:07:08 -0500
Paul Cartwright a...@pcartwright.com wrote:
On Mon December 21 2009, Stan Hoeppner wrote:
I do: stick with your homegrown kernel.
(From the guy who only uses custom kernels)
what would I gain from using a custom kernel, what would it take to
On Mon, 21 Dec 2009 21:07:08 -0500
Paul Cartwright a...@pcartwright.com wrote:
On Mon December 21 2009, Stan Hoeppner wrote:
I do: stick with your homegrown kernel.
(From the guy who only uses custom kernels)
what would I gain from using a custom kernel, what would it take to
Celejar put forth on 12/21/2009 8:22 PM:
1) Faster booting, since irrelevant drivers aren't loaded and won't
spend time probing.
Correct. And not just drivers. Prebuilt kernels usually include netfilter
support (for iptables), which increases the size of the kernel substantially,
along with
On Mon, 21 Dec 2009 20:50:15 -0600
Stan Hoeppner s...@hardwarefreak.com wrote:
Celejar put forth on 12/21/2009 8:22 PM:
1) Faster booting, since irrelevant drivers aren't loaded and won't
spend time probing.
Correct. And not just drivers. Prebuilt kernels usually include netfilter
Celejar put forth on 12/21/2009 9:13 PM:
I run desktops / laptops, and I always build netfilter - I run
shorewall on all my boxes.
For me, the firewall is always going to be upstream of desktops in a properly
configured infrastructure. WRT laptops, I guess it couldn't hurt to run a local
60 matches
Mail list logo
