On Dec 01 09:44:25, T. Valent wrote:
> > Because if someone simply says "this is impossible", it is only
> > natural to ask "why is that impossible?".
>
> Might be a question of culture. For me this doesn't sound "natural". If
> I'm being asked a question and given (detailed?) circumstances, I'd
On Thu, 01 Dec 2011 12:08:38 +0100
"T. Valent" wrote:
> Yeah, I know and I don't think that this is a problem with OpenBSD.
> However, I'm in an unusual situation not comparable to the standard user
> or developer. I have a very special demand. I'm asking if anybody can
> tell me anything about ho
> It seems well established by now that there is no magic bullet for your
> problem, since it is a problem few if anyone has had to address before
> within the constraints you have described.
This is a good summary for that quite long thread.
Again, thanks to everybody! I really do appreciate all
On Thu, Dec 01, 2011 at 09:44:25AM +0100, T. Valent wrote:
> > So: your machine has 32MB of Flash storage that holds the entire
> > system. On boot, it all gets loaded as a RAMDISK. Right?
>
> Doesn't have to do with my question, but: more or less correct.
>
>
> > It certainly sounds interesting
* Henning Brauer [2011-12-01 13:21]:
> the extra cost for a flash card of a reasonable
> size, yes even hundreds of cases, can't be cheaper than the (not free)
> work time it takes you to build your strange images.
err... that is pretty much the opposite of what I wanted to say. "can
be cheaper"
* T. Valent [2011-12-01 10:19]:
> > It certainly sounds interesting. Out of curiosity: what do these
> > system do? Are their routers? Rocket launchers?
> These machines are used for measuring and controlling. (In German:
> Steuerungscomputer). Now come on. I got complaints about "wasting
> people
Otto,
thanks for your hint.
> Can we end this now?
I thought I had initiated the end of this thread this morning by writing:
> I'm happy that some of you took the time and tried to explain over
> and over again what you thought was best for me. I really appreciate the
> good will.
But I have
On Thu, Dec 01, 2011 at 12:08:38PM +0100, T. Valent wrote:
> @marc
> > If you really want that, tell us how much you're prepared to spend, maybe
> > someone would be willing to sell you time to solve that very specific
> > problem
> > since obviously, no OpenBSD developer wants to do it for free,
@Gregory
> What he rather need is to boot GENERIC, then record dmesg, and strip
> the kernel down according to that dmesg.
That is exactly what I've done and this led me to my first posting here,
because it generally worked fine, but only to a certain extend. It
didn't work completely. Something
On Tue, Nov 29, 2011 at 11:09:25PM +, Stuart Henderson wrote:
> On 2011-11-29, Torsten Valentin wrote:
> >> welcome to the "ignore" list of many developers. You aren't even
> >> following directions on how to hurt yourself properly without wasting
> >> people's time.
> >
> > I always found th
On 2011 Dec 01 (Thu) at 09:44:25 +0100 (+0100), T. Valent wrote:
:> You have been told several times already: strip GENERIC down to what
:> will fit on your system. Start with things you definitely do not need
:> (sound? wifi?), then continue with the rest. If things break, put
:> the last thing th
> So: your machine has 32MB of Flash storage that holds the entire
> system. On boot, it all gets loaded as a RAMDISK. Right?
Doesn't have to do with my question, but: more or less correct.
> It certainly sounds interesting. Out of curiosity: what do these
> system do? Are their routers? Rocket
On Wed, 30 Nov 2011 21:05:05 +0100
Jan Stary wrote:
> On Nov 30 10:26:46, T. Valent wrote:
> > sure will solve what you have understood to be my problem. But what
> > really annoys me here is that I'm not taken seriously when I say
> > "this isn't an option". Why don't you just believe my words i
On Nov 30 10:26:46, T. Valent wrote:
> sure will solve what you have understood to be my problem. But what
> really annoys me here is that I'm not taken seriously when I say "this
> isn't an option". Why don't you just believe my words instead of
> permanently speaking about things that I explicitl
On Nov 30 18:15:30, Torsten Valentin wrote:
> > dmesg is the lazy way to get this info, the same info is written to
> > /var/log/messages during boot. Are you saying your system is so
> > stripped down you don't even log anything?
>
> Yep. And because the only persistent memory is Flash (32MB, wh
> Would you be able to use TFTP to try booting test kernels off a
> remote machine?
Nope. I try every attempt with a hardware flash drive which I generate
for that test machine. But I've got to get the kernel basically running
on my test VM, then another not that damn small hardware. Once this is
On Nov 30, 2011, at 12:15 PM, Torsten Valentin wrote:
>> dmesg is the lazy way to get this info, the same info is written to
>> /var/log/messages during boot. Are you saying your system is so
>> stripped down you don't even log anything?
>
> Yep. And because the only persistent memory is Flash (3
> dmesg is the lazy way to get this info, the same info is written to
> /var/log/messages during boot. Are you saying your system is so
> stripped down you don't even log anything?
Yep. And because the only persistent memory is Flash (32MB, which
quickly dies if you permanently write to it), the
On Wed, 30 Nov 2011, T. Valent wrote:
SNIP
dmesg output of any of these devices would be possible, but like I said
it's a very stripped down environment. dmesg is not part of it. I'd have
to setup an old system with dmsg on it, then export the output, just to
dmesg is the lazy way to get this
Thanks to everybody. I'll dig deeper into the config files soon. For now
I think we've got it discussed as much as is possible in a ML.
Stuart,
I really don't want to be misunderstood: I really appreciate the help
that's being offered from various users of this ML.
However, the following is somewhat off topic as it does not contribute
to the thread itself.
>> Because of the permanent repeating of "USE THE GENERIC KERNEL"
> not
Hello,
> De : Kevin Chadwick
> Split your config in
half, choose the half you think is most likely to
> cause the problem and diff
that half back to defaults and compile.
Just to ack what Kevin says. You're
trying to add and remove too many different things at once.
First take the
Generic kernel
On 2011-11-29, Torsten Valentin wrote:
>> welcome to the "ignore" list of many developers. You aren't even
>> following directions on how to hurt yourself properly without wasting
>> people's time.
>
> I always found that people waste my time when they write explanations
> and tons of bla bla tha
On Tue, Nov 29, 2011 at 9:25 PM, Miod Vallat wrote:
>> # grep -rw mem_range_softc /sys/arch/i386
>>
>> [...]
>> /sys/arch/i386/i386/mem.c:struct mem_range_softc mem_range_softc;
>> [...]
>
That's no that complicated to find dependencies as it may seem.
Carefully read the kernel config file and m
> # grep -rw mem_range_softc /sys/arch/i386
>
> [...]
> /sys/arch/i386/i386/mem.c:struct mem_range_softc mem_range_softc;
> [...]
grep will not show you the #ifdef constructs surrounding some of these
declarations.
> # grep -rw mem /sys/arch/i386/conf/files.i386
> /sys/arch/i386/conf/files.i386:
On Tue, 29 Nov 2011 10:05:11 +0100
"T. Valent" wrote:
> `fpu_mxcsr_mask'
>
> The above line is just an example. I have poked around with more or less
> guessing what could be missing, but after 2 days I'm quite sure I need a
> general solution to finding the dependencies instead of guessing.
>
>
On Nov 29 14:48:47, Torsten Valentin wrote:
> > So why don't you show us the dmesg
> > of the most recent kernel that worked for you?
>
> Because I don't see what that has to do with the issue.
If the "issue" still is to get OpenBSD running on that hardware,
then here is what it has to do with th
On Tue, 29 Nov 2011, Torsten Valentin wrote:
So why don't you show us the dmesg
of the most recent kernel that worked for you?
Because I don't see what that has to do with the issue. I'm not looking
for that one line that's missing in my current config files. I'm not
hoping for someone to tell
er "need" this sort of
information...
- Mail original -
De: "Torsten Valentin"
C: misc@openbsd.org
EnvoyC): Mardi 29 Novembre 2011 14:48:47
Objet: Which drivers are required for proper system functioning? (was: how to
find dependencies when building a new kernel)
>
Am 29.11.2011 14:03, schrieb Torsten Valentin:
welcome to the "ignore" list of many developers. You aren't even
following directions on how to hurt yourself properly without wasting
people's time.
I always found that people waste my time when they write explanations
and tons of bla bla that doe
> So why don't you show us the dmesg
> of the most recent kernel that worked for you?
Because I don't see what that has to do with the issue. I'm not looking
for that one line that's missing in my current config files. I'm not
hoping for someone to tell me that I should include line #5 and then it
Jan Stary wrote
> That's not what "cannot run GENERIC" means.
Indeed. But at the beginning of the 21st century I installed netbsd
in a laptop with 4MB ram through the serial port. The programs to
install an OS are normaly the biggest problem: need more resources
than the OS, they may not run,
On Nov 29 14:03:31, Torsten Valentin wrote:
> > welcome to the "ignore" list of many developers. You aren't even
> > following directions on how to hurt yourself properly without wasting
> > people's time.
>
> I always found that people waste my time when they write explanations
> and tons of bla
On Nov 29 13:55:45, sc...@web.de wrote:
> Nick Holland wrote to T. Valent:
>
> > IF your hardware is so anemic that it can't run GENERIC, I think you
> > will do much better getting more realistic hardware
>
> I differ. I have an old, very old laptop, running OpenBSD. The value
> of the laptop
> welcome to the "ignore" list of many developers. You aren't even
> following directions on how to hurt yourself properly without wasting
> people's time.
I always found that people waste my time when they write explanations
and tons of bla bla that does not have to do with the issue itself,
ins
Nick Holland wrote to T. Valent:
> IF your hardware is so anemic that it can't run GENERIC, I think you
> will do much better getting more realistic hardware
I differ. I have an old, very old laptop, running OpenBSD. The value
of the laptop is not "the hardware", but its use as typewriter - an
Read through the changes you made, see if anything looks a likely cause,
revert it, rebuild, repeat as necessary.
Start with any changes you've made yourself rather than changes
dmassage has made (I'm pretty certain it would not have removed the
npx device you had problems with in your first emai
reading the npx(4) gives out a really strong clue as to why you
shouldn't custom compile until you're familiar with everything:
"The npx driver is required for proper system functioning regardless
of whether or not an NPX is present."
so there's no 1:1 mapping between the devices you have and the
On 29-11-2011 13:00, Otto Moerbeek wrote:
> On Tue, Nov 29, 2011 at 12:29:28PM +0100, Camiel Dobbelaar wrote:
>
>> On 29-11-2011 11:38, T. Valent wrote:
>>
> dmassage -t
>>>
i might be wrong, but is this really aggressive auto spelling
corrector for "dmesg"?
>>>
>>> I found an exampl
On 11/29/11 04:04, T. Valent wrote:
...
> This is what I do:
> edit /usr/src/sys/conf/GENERIC
...
> edit /usr/src/sys/arch/i386/conf/GENERIC
welcome to the "ignore" list of many developers. You aren't even
following directions on how to hurt yourself properly without wasting
people's time.
...
>
On 29 Nov 2011, at 04:05, T. Valent wrote:
> This is what I do:
> edit /usr/src/sys/conf/GENERIC
> I'm fine with this so far.
I have to admit I've never needed to build my own OpenBSD kernel, so things
might be a bit different from NetBSD and FreeBSD. However, unless you are a
kernel maintainer,
On Tue, Nov 29, 2011 at 12:29:28PM +0100, Camiel Dobbelaar wrote:
> On 29-11-2011 11:38, T. Valent wrote:
>
> >>> dmassage -t
> >
> >> i might be wrong, but is this really aggressive auto spelling
> >> corrector for "dmesg"?
> >
> > I found an example usage of dmassage on the web, but could not
Andres,
may I kindly ask one more question, I'm sure after that I'll get it
right myself.
See:
# make
ld -Ttext 0xD0200120 -e start -N --warn-common -S -x -o bsd
${SYSTEM_HEAD} vers.o ${OBJS}
acpi_machdep.o(.text+0xcf): In function `acpi_sl
On 29-11-2011 11:38, T. Valent wrote:
>>> dmassage -t
>
>> i might be wrong, but is this really aggressive auto spelling
>> corrector for "dmesg"?
>
> I found an example usage of dmassage on the web, but could not find the
> program. So I thought the same way as you did.
>
> It's not part of th
On Tue, Nov 29, 2011 at 11:38, T. Valent wrote:
> [dmassage] It's not part of the official OpenBSD or the ports tree.
Are you sure it's not in sysutils/dmassage?
It would seem you're trying to build your own stripped-down kernel.
Doing that sort of thing is typically a "you break it, you get to
On 2011 Nov 29 (Tue) at 10:05:11 +0100 (+0100), T. Valent wrote:
:I know I am recommended to use the generic kernel. I need the kernel for
:an embedded device where the hardware is well known in detail, it is
:always the same, will not change and memory is very limited. So I need
:to get rid of the
Andres,
thanks a lot for your quick reply! I'm going to try this in a minute.
>> dmassage -t
> i might be wrong, but is this really aggressive auto spelling
> corrector for "dmesg"?
I found an example usage of dmassage on the web, but could not find the
program. So I thought the same way as yo
On Tue, Nov 29, 2011 at 4:35 AM, T. Valent wrote:
> Hi!
>
> I'm trying to build a new kernel. However, while compiling I get
> complaints about undefined references like this:
>
> ld -Ttext 0xD0200120 -e start -N --warn-common -S -x -o bsd
> ${SYSTEM_HEAD} vers.o ${OBJS}
> machdep.o(.text+0x2791):
Hi!
I'm trying to build a new kernel. However, while compiling I get
complaints about undefined references like this:
ld -Ttext 0xD0200120 -e start -N --warn-common -S -x -o bsd
${SYSTEM_HEAD} vers.o ${OBJS}
machdep.o(.text+0x2791): In function `sys_sigreturn':
: undefined reference to `fpu_mxcsr
49 matches
Mail list logo
