Prev: Tomcat is only listening with ip6 and not ip4
Next: xorg.conf for vesa
From: Hugo Vanwoerkom on 21 Dec 2009 16:00
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 kernel both show up together. But
with recent Debian kernel images only one shows up. I have a delay of 10
secs. in initramfs-tools but that makes no difference.

The 2nd USB disk shows up eventually, but after 'Init 2.86 booting' when
it is too late to be of use by fstab.

This isn't the first time I've asked this, but nobody seems to have an
answer.

Hugo


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Stan Hoeppner on 21 Dec 2009 18:30
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-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Andrew Reid on 21 Dec 2009 20:40
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 beginning of the boot process.
>
> Now the funny part: in my homegrown kernel both show up together. But
> with recent Debian kernel images only one shows up. I have a delay of 10
> secs. in initramfs-tools but that makes no difference.
>
> The 2nd USB disk shows up eventually, but after 'Init 2.86 booting' when
> it is too late to be of use by fstab.
>
> This isn't the first time I've asked this, but nobody seems to have an
> answer.

It's likely the devices aren't being recognized in the initramfs --
possibly they require kernel modules which are not present by default.

If you know which modules drive these devices, add them by name
to /etc/initramfs-tools/modules (one module per line, I think), and
re-generate your initramfs with update-initramfs. This should allow
the udev scan in the initramfs to see the devices, and set them
up earlier.

"Init 2.86 booting" is a very important milestone in the boot
process, it marks the transition from initramfs activity to
root file-system activity. Anything you want to do *before* that
has to be in the initramfs.

Or, as the other responder mentioned, you can just stick with
a custom kernel. I used to do that, but I like getting security
updates.

-- A.

--
Andrew Reid / reidac(a)bellatlantic.net


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Paul Cartwright on 21 Dec 2009 21:10
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 there??

--
Paul Cartwright
Registered Linux user # 367800
Registered Ubuntu User #12459


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Celejar on 21 Dec 2009 21:20
On Mon, 21 Dec 2009 21:07:08 -0500
Paul Cartwright <ale(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
> make/install one, ( a how-to?).

GIYF, but it's not that complicated, although there are quite a lot of
'gotchas'. Basically:

1) Download some source - either some linux-source package, or vanilla
from kernel.org (via http or git)

2) From the appropriate directory, run make menuconfig (or xconfig or
whatever you prefer) and configure appropriately

3) Run (as root, or using fakeroot) 'make-kpkg [--initrd]
[--revision=revisionstring] kernel_image'

4) Run 'dpkg -i kernelname'

If you're using an initrd, you'll need to install the appropriate hook
scripts. Read the README.gz and other documentation.

Celejar
--
foffl.sourceforge.net - Feeds OFFLine, an offline RSS/Atom aggregator
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
 |  Next  |  Last
Pages: 1 2 3 4 5 6 7
Prev: Tomcat is only listening with ip6 and not ip4
Next: xorg.conf for vesa