Hi,
Colin Williams wrote:
> I seem to have resolved the issue above after rebooting.
Congrats.
I planned to propose lsmod today, but your exploration work was faster.
Nevertheless, i wonder why the loop module was not loaded when you had
the difficulties with your script runs.
Have a nice day
I seem to have resolved the issue above after rebooting. Thanks for
helping to debug Thomas and everyone.
On Sat, Aug 7, 2021 at 1:29 PM Colin Williams
wrote:
>
> > --
> >
> > Do you have a file
> > /dev/loop-control
> > ?
> >
> --
>
> Do you have a file
> /dev/loop-control
> ?
>
> What is listed by
>
> ls -ld /dev/loop*
>
colin@M00974055-VM:~$ sudo ls /dev/loop-control
[sudo] password for colin:
ls: cannot access '/dev/loop-control': No such file
On Sat 07 Aug 2021 at 05:03:10 (-0700), Colin Williams wrote:
> >The error message of losetup does not match this theory.
>
> Re-reading http://ix.io/3v6K and it does appear that possibly
> /mnt/src/host/ does exist based on some of the debugging output.
> Thanks for making me look back. I made th
Hi,
Colin Williams wrote:
> http://ix.io/3vfj
Where i read
+++ sudo losetup --show -f /mnt/host/source/src/build/ima
ges/kukui/R94-14125.0.2021_08_07_0451-a1/chromiumos_base_
image.bin
losetup: cannot find an unused loop device
++ lb_dev=
++ sudo losetup -l -a
+++ sudo partx -v -d
Hi Thomas,
>The error message of losetup does not match this theory.
Re-reading http://ix.io/3v6K and it does appear that possibly
/mnt/src/host/ does exist based on some of the debugging output.
Thanks for making me look back. I made this "theory" on trying to `ls
/mnt/host/src/rc/build/images/k
Hi Thomas,
It's not entirely clear that what I was trying to express was
understood. Then in short:
1) A file
./src/build/images/kukui/R94-14125.0.2021_08_05_1510-a1/chromiumos_base_image.bin
is created
2) It seems that commands use a variable called GCLIENT_ROOT and it's
value is set to /mnt/h
Hi,
Colin Williams:
> 3) When trying to create the loopback device the script tries to use a
> path
> /mnt/host/src/rc/build/images/kukui/R94-14125.0.2021_08_05_1510-a1/chromiumos_base_image.bin
> which does not exist
The error message of losetup does not match this theory.
Did you make sure tha
Hi,
Colin Williams wrote:
> http://ix.io/3v3i
At least this shows an impressive partition table.
(Among them 5 partitions of size 512 bytes.)
> http://ix.io/3v6K
(Best to be downloaded and viewed in a text editor.)
> I believe the issues arise in
> https://github.com/drocsid/cros-scripts/blo
On Fri, Aug 06, 2021 at 09:48:29PM -0700, Colin Williams wrote:
> Hello everyone,
>
> In hindsight after looking at this much too late there were many
> mistakes in my initial mail. The issue may or may not be debian
> related and involves at least analyzing the script. There is a claim
> in the d
Hello everyone,
In hindsight after looking at this much too late there were many
mistakes in my initial mail. The issue may or may not be debian
related and involves at least analyzing the script. There is a claim
in the documentation that
Then I'll make another attempt to further expose my ignor
;t there a way to inquire the running kernel's configuration ?)
The Wanderer wrote:
> Debian started putting the kernel
> config on-disk instead, under the filename /boot/config-`uname -r`.
Ah yes. That exists here and says
CONFIG_BLK_DEV_LOOP=m
(Last year i igot missing CONFIG
ebian.net/search?q=package%3Alinux+BLK_DEV_LOOP%3Dn&literal=0
> but lots of "y" and "m".
>
> (Wasn't there a way to inquire the running kernel's configuration ?)
AFAIK, that's /proc/config.gz; it's present only if a specific Kconfig
setting is enable
Hi,
> Can someone tell me where I should look for the kernel for the
> loopback setting?
Quite exactly a year ago i learned the hard way that it's
CONFIG_BLK_DEV_LOOP which on amd64 should be set to "m" to get /dev/loop*.
See its description at
https://sources.debian.org/src/linux/5.10.46-1/dri
On Thu, Aug 05, 2021 at 04:36:59AM -0700, Colin Williams wrote:
> I'm running bullseye / debian 11.0 testing. I have been running a
> script that is supposed to write a filesystem image (for chromiumOS).
> In short I'm getting the following
>
> losetup: cannot find an unused loop device
> partx: s
d: No such file or directory
Or for a greater description http://ix.io/3v3i
Looking up the error someone mentioned that the kernel needed to be
configured to support loopback devices. I was curious where the kernel
config is located. I looked at https://wiki.debian.org/KernelFAQ and
it seems to be
On Ma, 27 oct 20, 20:15:13, Jonathan wrote:
> Good Evening,
>
> I was attempting to get my microphone working on my T14 AMD as it is the
> only non-functioning piece I was aware of. Browsing possible solutions I was
> shown the following could fix the issue if added to th
Good Evening,
I was attempting to get my microphone working on my T14 AMD as it is the
only non-functioning piece I was aware of. Browsing possible solutions I
was shown the following could fix the issue if added to the kernel config:
CONFIG_SND_SOC_AMD_RENOIR=m
On Sun, Oct 04, 2020 at 02:33:43AM +0200, Janis Hamme wrote:
> Am 04.10.20 um 00:35 schrieb deloptes:
> > cp /boot/config-..xxx .config
> > make .oldconfig
> > make -j`nproc` bindeb-pkg
>
> The oldconfig hassle is something that I'd rather like to avoid, there are a
> lot changes between
On Sun, 4 Oct 2020 at 11:34, Janis Hamme wrote:
> I think I found a proper way to do it. It turns out the buster-backports repo
> actually has the Debian sources for all kernel versions that were released
> in the past. Maybe the steps are useful for others as well:
Hi, thank you very much for s
Am 04.10.20 um 00:35 schrieb deloptes:
> cp /boot/config-..xxx .config
> make .oldconfig
> make -j`nproc` bindeb-pkg
>
> as mentioned in https://wiki.debian.org/BuildADebianKernelPackage
>
> After make .oldconfig you will be asked questions about new stuff.
The oldconfig hassle is somethin
Janis Hamme wrote:
> I'd like to build the vanilla 5.4.69 LTS Kernel for one of my Debian
> machines (Buster).
>
> The easiest way seems to build the Kernel with the built in "make
> deb-pkg" target. Since I do not really want to go through all the config
> changes,
> my plan was to get a 5.4 con
Hi,
I'd like to build the vanilla 5.4.69 LTS Kernel for one of my Debian
machines (Buster).
The easiest way seems to build the Kernel with the built in "make
deb-pkg" target. Since I do not really want to go through all the config
changes,
my plan was to get a 5.4 config for amd64 from
https://sa
Also, apologies for double posting this, I only just found that the first
time I sent this went through as well :P
On 17 Jan 2014 19:28, "Sum Guy" wrote:
> Hi, I'm trying to enable interrupt remapping and DMA remapping to try and
> use PCI passthrough as described here:
> http://www.linux-kvm.org
Hi, I'm trying to enable interrupt remapping and DMA remapping to try and
use PCI passthrough as described here:
http://www.linux-kvm.org/page/How_to_assign_devices_with_VT-d_in_KVM
I'm following the guide for rebuilding an official Debian kernel package
(the parts under the "Add a patch to linux
On 2011-07-11 21:52 +0200, Tech Geek wrote:
>> AFAIK the kernel in the installer is
>> split into many small packages from the regular linux-image package. So
>> the possible differences are version skews when a newer kernel hits the
>> archive, and missing modules that are not packaged for the i
Sven,
> AFAIK the kernel in the installer is
> split into many small packages from the regular linux-image package. So
> the possible differences are version skews when a newer kernel hits the
> archive, and missing modules that are not packaged for the installer.
You are right. I discovered that
there might be some
> difference between the kernel that installs Debian and the kernel that
> gets installed on the hard drive.
This might indeed be the case, however you will generally not be able to
tell that from the kernel config. AFAIK the kernel in the installer is
split into many sm
On Fri, 08 Jul 2011 13:41:32 -0700, Tech Geek wrote:
>> It should be available at /boot/config-`uname -r`
> That would be true after the system installation finishes. What I am
> looking for is the config file for the kernel runs the installation
> process. For some reasons I suspect that there m
On 07/08/11 at 02:26pm, Tech Geek wrote:
> > It is in the boot directory of the linux-image package, which is on the
> > first disk or in the packages section at www.debian.org.
>
> So, from what you just said, it means that both the kernels, one that
> runs from the install disc and the one that
On Fri 08 Jul 2011 at 14:26:25 -0700, Tech Geek wrote:
> > It is in the boot directory of the linux-image package, which is on the
> > first disk or in the packages section at www.debian.org.
>
> So, from what you just said, it means that both the kernels, one that
> runs from the install disc an
> It is in the boot directory of the linux-image package, which is on the
> first disk or in the packages section at www.debian.org.
So, from what you just said, it means that both the kernels, one that
runs from the install disc and the one that gets installed on the hard
drive are exactly the sa
On Fri 08 Jul 2011 at 11:58:00 -0700, Tech Geek wrote:
> Hello,
>
> I was wondering where can I find (or view) the .config file for the
> kernel (vmlinuz) that comes on the Debian Squeeze install discs. I
> tried searching on the internet but nothing came up.
It is in the boot directory of the l
> It should be available at /boot/config-`uname -r`
That would be true after the system installation finishes. What I am
looking for is the config file for the kernel runs the installation
process. For some reasons I suspect that there might be some
difference between the kernel that installs Debia
On 07/08/2011 03:58 PM, Tech Geek wrote:
> Hello,
>
> I was wondering where can I find (or view) the .config file for the
> kernel (vmlinuz) that comes on the Debian Squeeze install discs. I
> tried searching on the internet but nothing came up.
It should be available at /boot/config-`uname -r`
Hello,
I was wondering where can I find (or view) the .config file for the
kernel (vmlinuz) that comes on the Debian Squeeze install discs. I
tried searching on the internet but nothing came up.
Thanks.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubs
Jim Green wrote at 2011-04-23 22:53 -0500:
> first is run time and the latter is compile time, but what is the
> difference here, is one of the other's subset? do their parameters
> overlap? which is the preferred file to change? changing .config
> requires a recompile.
I suppose that if a setting
Hello debianers:
today i successfully compiled 2.38.4 kernel using make-kmkg and fixed
the hibernate can't resume issue for kernel 2.38-2, got a couple
questions here:
first is run time and the latter is compile time, but what is the
difference here, is one of the other's subset? do their paramete
>
>
>
> Original Message
>From: s...@hardwarefreak.com
>To: debian-user@lists.debian.org
>Subject: Re: Debian stock kernel config -- CONFIG_NR_CPUS=32?
>Date: Sat, 23 Oct 2010 12:13:06 -0500
>
>>ow...@netptc.net put forth on 10/22/2010 8:15 PM:
>>
Ron Johnson put forth on 10/22/2010 8:48 PM:
> Bah, humbug.
>
> Instead of a quad-core at lower GHz, I just got my wife a dual-core at
> higher speed.
Not to mention the fact that for desktop use 2 higher clocked cores will
yield faster application performance (think of the single threaded Flash
ow...@netptc.net put forth on 10/22/2010 8:15 PM:
> Actually Amdahl's Law IS a law of diminishing returns but is intended
> to be applied to hardware, not software. The usual application is to
> compute the degree to which adding another processor increases the
> processing power of the system
>
On 10/22/2010 07:08 PM, Andrew Reid wrote:
On Friday 22 October 2010 03:22:02 Sven Joachim wrote:
On 2010-10-22 03:15 +0200, Andrew Reid wrote:
I recently deployed some new many-core servers at work, with
48 cores each (4x 12 core AMD 6174s), and ran into an issue where
the stock Debian kern
>
>
>
> Original Message
>From: rei...@bellatlantic.net
>To: debian-user@lists.debian.org
>Subject: Re: Debian stock kernel config -- CONFIG_NR_CPUS=32?
>Date: Fri, 22 Oct 2010 20:05:49 -0400
>
>>On Friday 22 October 2010 11:34:19 ow...@netptc.net wrote:
&
On Friday 22 October 2010 03:22:02 Sven Joachim wrote:
> On 2010-10-22 03:15 +0200, Andrew Reid wrote:
> > I recently deployed some new many-core servers at work, with
> > 48 cores each (4x 12 core AMD 6174s), and ran into an issue where
> > the stock Debian kernel is compiled with CONFIG_NR_CPUS
ow...@netptc.net put forth on 10/22/2010 5:18 PM:
> Ron et al
> See the following:
> http://en.wikipedia.org/wiki/Amdahl's_law
> Larry
Amdahl's law doesn't apply to capacity systems, only capability systems.
Capacity systems are limited almost exclusively by memory,
IPC/coherence, and I/O bandwi
On Friday 22 October 2010 11:34:19 ow...@netptc.net wrote:
> In fact IIRC the additional overhead follows the square of the number
> of CPUs. I seem to recall this was called Amdahl's Law after Gene
> Amdahl of IBM (and later his own company)
Either that's not it, or there's more than one "Amd
>
>
>
> Original Message
>From: ron.l.john...@cox.net
>To: debian-user@lists.debian.org
>Subject: Re: Debian stock kernel config -- CONFIG_NR_CPUS=32?
>Date: Fri, 22 Oct 2010 12:44:39 -0500
>
>>On 10/22/2010 10:34 AM, ow...@netptc.net wrote:
>>>&
On 10/22/2010 10:34 AM, ow...@netptc.net wrote:
Original Message
From: ron.l.john...@cox.net
To: debian-user@lists.debian.org
Subject: Re: Debian stock kernel config -- CONFIG_NR_CPUS=32?
Date: Fri, 22 Oct 2010 02:00:45 -0500
Correct. The amount of effort needed for cross-CPU
>
>
>
> Original Message
>From: ron.l.john...@cox.net
>To: debian-user@lists.debian.org
>Subject: Re: Debian stock kernel config -- CONFIG_NR_CPUS=32?
>Date: Fri, 22 Oct 2010 02:00:45 -0500
>
>>On 10/22/2010 12:53 AM, Arthur Machlas wrote:
>>> On
Ron Johnson put forth on 10/22/2010 2:00 AM:
> On 10/22/2010 12:53 AM, Arthur Machlas wrote:
>> On Thu, Oct 21, 2010 at 8:15 PM, Andrew Reid
>> wrote:
>>> But I'm curious if anyone on the list knows the rationale for
>>> distributing kernels with this set to 32. Is that just a
>>> reasonable nu
On 2010-10-22 03:15 +0200, Andrew Reid wrote:
> I recently deployed some new many-core servers at work, with
> 48 cores each (4x 12 core AMD 6174s), and ran into an issue where
> the stock Debian kernel is compiled with CONFIG_NR_CPUS=32,
> meaning it will only use the first 32 cores that it see
On 10/22/2010 12:53 AM, Arthur Machlas wrote:
On Thu, Oct 21, 2010 at 8:15 PM, Andrew Reid wrote:
But I'm curious if anyone on the list knows the rationale for
distributing kernels with this set to 32. Is that just a
reasonable number that's never been updated? Or is there some
complication
On Thu, Oct 21, 2010 at 8:15 PM, Andrew Reid wrote:
> But I'm curious if anyone on the list knows the rationale for
> distributing kernels with this set to 32. Is that just a
> reasonable number that's never been updated? Or is there some
> complication that arises after 32 cores, and should I
Hi all --
I recently deployed some new many-core servers at work, with
48 cores each (4x 12 core AMD 6174s), and ran into an issue where
the stock Debian kernel is compiled with CONFIG_NR_CPUS=32,
meaning it will only use the first 32 cores that it sees.
For old Debian hands like me, thi
Arthur Machlas put forth on 7/30/2010 9:04 AM:
>> BTW, I'm curious as to your motivations for this. Is this basically a
>> "Windows can do 800MHz, so $deity dammit, Linux should be able to do it as
>> well!" thing?
>
> Not as such. More like a my processor is supposed to scale from 800Mhz
> to 1
On Thu, Jul 29, 2010 at 8:20 PM, Christian Jaeger wrote:
> How do you read the possible cpu frequencies?
>
> Your kernel needs cpufreq support and ondemand, powersave, etc.
> governors; check with
> cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
> cat /sys/devices/system/cp
here. It is the key to you
> succeeding at this. You may have to experiment some, but that's a requirement
> when rolling one's own kernels. Welcome to the club. It's rarely "easy". ;)
>
Asking on here isn't my first attempt at figuring things out. My
kernel c
Arthur Machlas put forth on 7/29/2010 12:01 PM:
> Things are running nicely, but the problem I hoped
> to resolve hasn't been. Namely, the lowest frequency my cpu can reach
> is 1Ghz... instead of the 800Mhz that it reaches on windows and in the
> spec sheets.
>
> Advice on how to proceed from he
How do you read the possible cpu frequencies?
Your kernel needs cpufreq support and ondemand, powersave, etc.
governors; check with
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
cat /sys/devices/system/cp
On Thu, Jul 29, 2010 at 5:46 AM, Stan Hoeppner wrote:
> Arthur Machlas put forth on 7/28/2010 11:14 PM:
> In "make menuconfig":
>
> These last two are probably the reason for the "unknown", especially given
> you're running 2.6.34 which has all the CPU models currently on the market.
Probably ju
ther doesn't support CPU_ID or doesn't have the tables
for Atom CPUs, or both. This is a kernel config option.
> r...@hpm210:/home/arthur/Misc/Linux/2.6.34-1# linuxinfo
> Linux HPm210 2.6.32-5-686 #1 SMP Tue Jun 1 04:59:47 UTC 2010
> Two Intel Unknown 1666MHz processors, 6650.42
r, but I can't
solve this cpu thing and hoping someone can weigh in with some
friendly advice. The help in kernel config says things will run better
if I don't enable smp on a single cpu system. Hence, the question to
you, lazyweb, with much appreciation in advance.
--
To UNSUBSCR
Jochen Schulz wrote:
Hugo Vanwoerkom:
But that the combination of 'Y's and 'M's is immaterial as to the
functioning of the driver.
Am I correct?
Generally yes. There are modules which are better compiled statically
(IDE/S-ATA, filesystems) but they work either way.
This in regard to trying
Hugo Vanwoerkom:
>
> But that the combination of 'Y's and 'M's is immaterial as to the
> functioning of the driver.
>
> Am I correct?
Generally yes. There are modules which are better compiled statically
(IDE/S-ATA, filesystems) but they work either way.
> This in regard to trying to get smar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hugo Vanwoerkom schrieb:
> Dave Ewart wrote:
>> On Monday, 13.10.2008 at 09:46 -0500, Hugo Vanwoerkom wrote:
>>
[...]
>>
>
> It works regarding smartctl but *not* using vga= or uvesafb, which is
> a severe problem compared to using smartctl.
>
For m
Dave Ewart wrote:
On Monday, 13.10.2008 at 09:46 -0500, Hugo Vanwoerkom wrote:
I am under the impression that for a kernel function, like a driver,
to be present and function correctly one has to mark it either 'Y' or
'M' in the kernel .config.
But that the combination
On Monday, 13.10.2008 at 09:46 -0500, Hugo Vanwoerkom wrote:
> I am under the impression that for a kernel function, like a driver,
> to be present and function correctly one has to mark it either 'Y' or
> 'M' in the kernel .config.
>
> But that the combinatio
Hi,
I am under the impression that for a kernel function, like a driver, to
be present and function correctly one has to mark it either 'Y' or 'M'
in the kernel .config.
But that the combination of 'Y's and 'M's is immaterial as to the
functioning
Hugo Vanwoerkom wrote:
Hi,
I can't use the Debian (Sid) kernels because VGA= does not work on
my box: gets 'invalid videomode'.
I can use Debian kernels with uvesafb but its companion v86d dies with
my new GeForce 6200 AGP after a while.
But all works well when I roll my own kernel. Except t
Hi,
I can't use the Debian (Sid) kernels because VGA= does not work on
my box: gets 'invalid videomode'.
I can use Debian kernels with uvesafb but its companion v86d dies with
my new GeForce 6200 AGP after a while.
But all works well when I roll my own kernel. Except then I cannot use
smart
On 2008-07-11 09:58 +0200, David Baron wrote:
> Trying to compile a 2.6.25.8 kernel.
>
> The make oldconfig asks numerous questions, mostly about newly supported new
> hardware and options that are probably not relevant or helpful to me.
>
> However, it did ask for a uevent driver path which want
Trying to compile a 2.6.25.8 kernel.
The make oldconfig asks numerous questions, mostly about newly supported new
hardware and options that are probably not relevant or helpful to me.
However, it did ask for a uevent driver path which wants to default to
/sbin/hotplug
This does not exist since
On Thu, 03 Jan 2008 09:58:28 -0600, Ron Johnson <[EMAIL PROTECTED]>
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 01/03/08 09:42, Bernd Prager wrote:
>> Hi,
>>
>> I am running kernel 2.6.23.12 and compiled with SMP on.
>
> Home-rolled or built-by-Debian?
Home-rolled
> Are you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/03/08 09:42, Bernd Prager wrote:
> Hi,
>
> I am running kernel 2.6.23.12 and compiled with SMP on.
Home-rolled or built-by-Debian?
Are you sure SMP is enabled? What does "uname -v" say?
> Unfortunately the kernel doesn't recognize my dual co
Hi,
I am running kernel 2.6.23.12 and compiled with SMP on.
Unfortunately the kernel doesn't recognize my dual core processor:
$ dmesg | grep -i cpu
CPU has 2 num_cores
Processor #0 (Bootup-CPU)
SMP: Allowing 1 CPUs, 0 hotplug CPUs
PERCPU: Allocating 34344 bytes of per cpu data
Initializing CPU#0
In the root of the kernel sources do a make menuconfig, goto processor type
and features and select the wanted option, recompile the kernel, install
the kernel, update the bootloader and you're done, for the other stuff I
don't
know because me english it's a little scarse (yet),
good luck friend.
On Sun, Oct 28, 2007 at 07:17:29PM -0400, Frederick N. Brier wrote:
> I made the mistake of taking a default or selecting the wrong kernel (my
> machine is an AMD X2). So I now have a 64 bit kernel (x86_64), which I
> have read is "transitional". Since so many packages are only 32 bit, my
> li
I made the mistake of taking a default or selecting the wrong kernel (my
machine is an AMD X2). So I now have a 64 bit kernel (x86_64), which I
have read is "transitional". Since so many packages are only 32 bit, my
life has gotten complex trying to make everything work and with
contemplation
On Wed, 20 Jun 2007 10:16:53 -0700
David Brodbeck <[EMAIL PROTECTED]> wrote:
>
> On Jun 19, 2007, at 2:59 PM, Julian De Marchi wrote:
> > Try this
> >
> > cp /boot/.config /usr/src/linux
> >
> > Then when you load your kernel menu, go to load alternative config
> > file. Then input the file nam
On Jun 19, 2007, at 2:59 PM, Julian De Marchi wrote:
Try this
cp /boot/.config /usr/src/linux
Then when you load your kernel menu, go to load alternative config
file. Then input the file name .config.
This should help!
What I usually do is copy the .config file to the kernel build
dire
On Jun 19, 2007, at 2:54 PM, yong lee wrote:
Hi,
I am trying to build a custom kernel with openMosix
patches for my debian 4.0 system. I copied an existing
config file from /boot/config-2.6.18-4-686 to my new
kernel source tree folder and renamed it to be
.config. Then I ran 'make-kpkg kernel
On 2007-06-19, yong lee <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I am trying to build a custom kernel with openMosix
> patches for my debian 4.0 system. I copied an existing
> config file from /boot/config-2.6.18-4-686 to my new
> kernel source tree folder and renamed it to be
> .config. Then I ran 'm
Hey mate,
My mistake, you original post you had the right idea.
You already have the .config file as you got it from /boot/'uname
-r'.config (/boot/config-2.6.18-4-686 to my new
kernel source tree folder and renamed it to be
.config.)
The only step you missed is to load the alternative config
On Tue, 19 Jun 2007 14:54:37 -0700 (PDT)
yong lee <[EMAIL PROTECTED]> wrote:
Based on my experience you miss one "important" step, before do any command do
a make oldconfig
with your config in place in the kernel tree, answer all the questions and do a
make menuconfig and the others commands, ho
yong lee wrote:
Hi,
I am trying to build a custom kernel with openMosix
patches for my debian 4.0 system. I copied an existing
config file from /boot/config-2.6.18-4-686 to my new
kernel source tree folder and renamed it to be
.config. Then I ran 'make-kpkg kernel_image' to build
the kernel. Bu
Hi,
I am trying to build a custom kernel with openMosix
patches for my debian 4.0 system. I copied an existing
config file from /boot/config-2.6.18-4-686 to my new
kernel source tree folder and renamed it to be
.config. Then I ran 'make-kpkg kernel_image' to build
the kernel. But when I reboot wi
Marc D Ronell <[EMAIL PROTECTED]> writes:
> Hi,
>
> Is it currently possible to configure a linux kernel to directly
> (without an initrd image) boot from a Hitachi HTS541080G9SA00 drive
> which I believe is a SATA-I serial ATA drive. I believe my machine is
> using an Intel 945pm chip
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 06 July 2006 13:05, Brian C wrote:
> Hi,
>
> I must be missing something. The standard Sarge 2.6.8.2 kernel with
> initrd boots fine on this ASUS P4C800-E Deluxe Motherboard with a single
> 500GB IDE Hard drive as /dev/hda, but the config I
Hi,
I must be missing something. The standard Sarge 2.6.8.2 kernel with
initrd boots fine on this ASUS P4C800-E Deluxe Motherboard with a single
500GB IDE Hard drive as /dev/hda, but the config I made for 2.6.17.3
kernel panics at the point where it is looking for the hard disk (which
it cannot fi
something. I'll be happy to file one if you think it won't be
>> perceived as nitpicking. Personally, I think the idea of
>> kernel-config-* packages is a good one.
>
> Yeah I think it's a good idea. Please do :)
I've been corresponding with Andrew Pimlot
won't be
> perceived as nitpicking. Personally, I think the idea of
> kernel-config-* packages is a good one.
Yeah I think it's a good idea. Please do :)
--
Jon Dowland
http://alcopop.org/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Jon Dowland <[EMAIL PROTECTED]> writes:
> On Mon, Dec 19, 2005 at 01:08:34AM -0600, D. Michael McFarland wrote:
>
> Redhat puts the configs used in the srpm under ./configs ; perhaps
> putting the debian config file in a seperate package (kernel-config-*)
> would be a
On Mon, Dec 19, 2005 at 12:01:44PM -0500, Ron Peterson wrote:
> It seems like the easiest solution would be to simply ensure that the
> distributed kernels are compiled to put config.gz in /proc. That
> would certainly remove any ambiguity about which config file to look
> at.
That is one solutio
On Mon, Dec 19, 2005 at 10:20:08AM +, Jon Dowland wrote:
> Redhat puts the configs used in the srpm under ./configs ; perhaps
> putting the debian config file in a seperate package (kernel-config-*)
> would be a good idea.
It seems like the easiest solution would be to simply ensure
e srpm under ./configs ; perhaps
putting the debian config file in a seperate package (kernel-config-*)
would be a good idea. Is there a wishlist bug open to this effect? If
not, would you be interested in filing one?
[1] I've been bitten by the non-standard behaviour of the kernel
p
Robert Kopp <[EMAIL PROTECTED]> writes:
> --- "D. Michael McFarland" <[EMAIL PROTECTED]> wrote:
>
>> I've installed the package linux-source-2.6.14 with the intention
>> of building a kernel with the stock Debian configuration. However,
>> I've been unable to locate the .config file corresponding
--- "D. Michael McFarland" <[EMAIL PROTECTED]> wrote:
> I've installed the package linux-source-2.6.14 with
> the intention of
> building a kernel with the stock Debian
> configuration. However, I've
> been unable to locate the .config file corresponding
> to
> linux-image-2.6.14-2-amd64-k8. A
I've installed the package linux-source-2.6.14 with the intention of
building a kernel with the stock Debian configuration. However, I've
been unable to locate the .config file corresponding to
linux-image-2.6.14-2-amd64-k8. According to
/usr/share/doc/linux-source-2.6.14/README.Debian,
Conf
How do I manually configure my kernel to build snd-hwdep.ko?
I built an extra kernel module (snd-bt-sco.ko) which requires
snd-hwdep.ko, but snd-hwdep.ko isn't built, & there's no kernel
configuration option to enable it.
I tried manually adding "CONFIG_SND_HWDEP=m" to my .config, but it is
rem
Hi!
Does anybody have a working kernel .config file for a custom kernel
running on an HP Omnibook 6000? Thanxs a lot! :)
- Martin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
1 - 100 of 218 matches
Mail list logo
