I've also been bedeviled by the ldconfig problem reported by Andy
so I'm wondering if there has been any new thinking emerged
in the past two years on this topic.
Bruce sends the interested reader to a Bug report wherein someone
seemed to be comfortable with a suggested fix(?) found there.
Hi Martins,
... the usb mouse I have connected seems to be constantly disconnecting and
reconnecting
after the system boots, filling the screen constantly connect/disconnect
messages
like the following ...
I wouldn't chuck my mouse out the window yet.
I've been plagued by these nonsensical
A recent incident in compiling 'udev-181' TRIGGERed me to again
wonder what's going on and where and how I've been doing things wrong.
I figure maybe this time, with a real world example, a good soul
will understand what's been bothering me and take the time to
calmly explain in _plain_ English
Hi Andy Bruce,
Many thanks for your prompt, clear and helpful answers.
Andy:
You should leave the kernel headers in /usr/include
as they were when you installed glibc.
Bruce:
The kernel varies, but you build glibc against one specific kernel.
The programs that are built later need to be
Hi Jason,
I'm detecting a slight note of desperation in your voice, so before you do
anything
drastic, maybe you would like to spend a few minutes with my trouble-shooting
procedure.
In a similar (NOT exact) situation it worked for me simply, quickly, reliably
and
100% (that's one-hundred,
Nov 29, 2011 02:09:37 AM, Simon wrote:
A little dramatic, don't you think? The world isn't going to end, just
because you've found a bug in a video driver...
In the KERNEL Simon, in the KERNEL, NOT the driver.
Also, come to think of it, I didn't find the BUG, it found me! :)
Speaking of
Hi Bruce,
On Tue Nov 15 2011 at 15:12:33 MST
... we've made some improvements and fixed some bugs in the bootscripts. ...
Thank you for the excellent lfs-bootscripts-2014 release.
At the risk of sounding picayunish (just striving for an even higher
perfection), I do have some
On Thu Nov 17 2011 at 14:41:17 MST, Bruce Dubbs schrieb
I don't really use this script [console], so can you test it for me?
Just try the attached file [console.txt].
Hi Bruce,
On a Native English speaker console (i.e., missing the
'/etc/sysconfig/console'):
[]$ ./console
Usage: ./console
On 06/03/2011 09:28 PM, Alex wrote:
Thank you very much for the total silence you met this thread with.
It warms the cockles of my heart to see there are still people
of character around in this wild and crazy world of ours.
Jun 4, 2011 01:43:13 AM, DJ Lucas wrote:
On a related note, it is
Hello All,
IMPORTANT UPDATE (very good news!!)
As of 06/03/2011 12:34:00 AM (German time), my issue
was removed by the new 2.6.39.1 release.
As soon as I reached line 3502 (of 4164 overall) in reading the
ChangeLog-2.6.39.1:
block: always allocate genhd-ev if check_events is implemented,
I knew
May 1, 2011 12:12:01 AM, neal.p.murphy wrote.
Hi Neil,
Thank you very much for your comments.
I'm trying to comment on your comments now.
Alex said:
'/lib/udev/rules.d/50-udev-default.rules':
SUBSYSTEM==rtc, DRIVERS==rtc_cmos, SYMLINK+=rtc
FWIW, I don't see the relevance of rule 50-udev
May 2, 2011 05:24:23 PM, Bruce wrote:
Alex wrote:
That's a 360 (as they say) reversal of what I said in my previous post.
Not sure if I got the attribution right.LOL.
I think you mean 180. :)
Hi Bruce,
This is a relatively known joke (expression) in relative wide use.
It is attributed
Apr 30, 2011 09:50:09 PM, Bruce wrote: perhaps a sleep( 2 ) before or after after '/sbin/udevadm settle' in the udev script would isolate the problem.You're right. On a slower machine, where I played with 168a "sleep 3" (for good measure - worked with 2 secs. as well)just before the end (::) of
Apr 30, 2011 09:50:09 PM, Bruce Dubbs wrote:
perhaps a sleep( 2 ) before or after after '/sbin/udevadm settle'
in the udev script would isolate the problem.
You're right. On a slower machine, where I played with 168
a sleep 3 (for good measure - worked with 2 secs. as well)
just before the
htmlhead
link media=all type=text/css
href=/netmail/static/deg/css/wysiwyg-3933289048.css rel=stylesheet
/headbody
Hello,brbrI'm confused about 'setclock' script activation in the boot
sequence.brMaybe I'm missing something:brnbsp;seems to have disappeared
from
Hello,
I'm confused about 'setclock' script activation in the boot sequence.
Maybe I'm missing something:
seems to have disappeared from '/etc/rc.d/rcsysinit.d/'
Thanks,
-- Alex
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Apr 28, 2011 03:32:59 PM, Andrew Benton wrote:
According to 55-lfs.rules udev should run the setclock script
when /dev/rtc becomes available.
Does /dev/rtc exist?
Maybe you configured your kernel without real time clock support?
It seems we're in the fortunate situation here where people
Mar 27, 2011 12:47:52 PM, Andrew Benton wrote:
Alex:
I tried my damnedest; each time I use --with-system-png
the compile fails
Can we see the actual error message (and some lines of context before
the crash happens). Maybe we can find a fix for you?
Hi Andy,
Thank you very much.
Please
As promised, I ran a number of tests to clarify Udev
interaction with '/lib/udev/devices/' and the creation
of some essential nodes during a boot-up.
PRELIMINARIES
A. [/sbin]$ strings udevd | grep devices
/lib/udev/devices
/devices/
So, 'udevd' is aware of '/lib/udev/devices/'
Bruce Dubbs wrote:
When I rebooted, I got the following messages:
cannot open /dev/null
...
FATAL: Module LNXSYTEM: not found
...
When I added null back to /lib/udev/devices/ and reenabled
the copy in the bootscripts, I got none of these messages.
...
I don't have any modules to
SYSTEM
~~
ASUS P5E-VM HDMI with Intel G35/ICH9R.
Intel Core2 Duo CPU E8400 @ 3.00GHz, 4GB
(B)LFS i686-pc-linux-gnu, 2.6.37.1, Udev-166
PROBLEM
~~~
No problems. I'm just trying to recap and maybe bring
this thread to a merciful end.
In the following, I'm trying to present a time-line
Bruce Dubbs wrote,
It's in section 6.2.1, not 6.2.21
Hi Bruce,
Typo. Sorry.
C.2. The whole Create some devices and directories ... in
udev-1xx should go. Misleading, outdated and nonsensical.
No, it really can't go. I went into my sandbox, deleted
/lib/udev/devices/null, and commented
Feb 25, 2011 04:26:29 AM, Simon Geard wrote:
On Wed, 2011-02-23 at 12:24 -0600, al...@verizon.net wrote:
BTW, there is a [rant][/rant] I'm skipping, although the idea
is not the first time to come up, where people grow from LFS
to BLFS and become confused and/or _misunderstood_ about
Feb 25, 2011 03:11:51 PM, Bruce Dobbs wrote:
I haven't looked at this code in quite a while, but I don't
see these instructions as contradictory.
Hi Bruce,
I commented out 'cp -a /lib/udev/devices/null /dev' in udev script.
and did a reboot.
_I_ didn't notice any changes (messages, etc.) in
Feb 23, 2011 04:58:10 AM, Simon Geard wrote:
... those nodes [null and console] are supposed to be there in
/dev on the root partition.
If you don't have them, you've missed a step in the build.
Hi Simon,
We're totally in sync here (if you take a look at the grand
finale of my OP :)
I had
Hello,
SYSTEM
(B)LFS i686-pc-linux-gnu, 2.6.37.1, Udev-166
LFS book: Version SVN-20110218
Script activation order in '... rcsysinit.d/':
mountkernfs
consolelog
modules (no modules to install, in my case)
udev
...
INTRODUCTION
While my system has worked well for a long time,
a
Feb 3, 2011 01:19:42 PM, Stuart Stegall wrote:
[the keyboard] It's still being detected as a keyboard right?
Hi Stuart,
Yes. As I alluded in my OP a few times, I never had any
problems with the keyboard and mice (they do act as one
would expect a keyboard and a mouse to at all times)
Send
(B)LFS i686-pc-linux-gnu, 2.6.37, Udev-165. Keyboard:
Microsoft ANB-1 Black 104 Normal Keys USB Wired Slim Keyboard 600
Hello,
INTRO
I got into some slight and strange (for me) problems
in tuning up my Xorg-7.6 experience. Unimportant for
the subject questions to follow.
However, the
Jan 30, 2011 11:20:29 PM, lfs-support@linuxfromscratch.org wrote:
Sorry for the late reply. I don't frequent LFS-Support (This belongs on
BLFS-Support or even BLFS-Dev).
Hi DJ,
The fault is mine; should've used BLFS-Support.
Apologies.
Anyway, thanks for the clear reply and Xorg-7.6
BLFS Development svn-20110124
* January 23rd, 2011
+ [dj] - Removed luit from the book as it is now installed as
part of Xorg Applications.
Hello,
luit-1.1.0 is in the Xorg-7.6 wget list (no surprize here).
1. luit is not in the applications Installed Programs list
2. For
Hello,
ASUS P5E-VM HDMI with Intel G35/ICH9R.
Intel Core2 Duo CPU E8400 @ 3.00GHz, 4GB
(B)LFS i686-pc-linux-gnu 2.6.37
I upgraded to 2.6.37 (from 2.6.36.2) and, for the first time
in recent memory, the system freezes solid on trying to go to graphics.
My long standing intel driver seems to
On Thu Jan 6 2011 09:24 PM, William Immendorf wrote:
Intriguing. This is something that you should report to both
LKML and linux-hotplug (the Udev list).
Also, be sure to provide the kdump of that kernel, the log,
and the hardware that you think is causing the Udev issue.
Hi William,
First,
Jan 11, 2011 08:39:03 PM, Ken Moffat wrote:
Perhaps, you could try a newer xorg intel driver,
but it's probably a kernel regression.
Hi Ken,
Thank you for your interesting and detailed comments.
I don't have much choice, so maybe just upgrading the Xorg-7.6's
xserver and the intel driver
On Thu, 2011-01-06 at 02:08 AM, Simon Geard wrote:
... udevd supports a couple of options that might help, --debug and
--debug-trace.
1. FWIW, udevd-165 does not (no-longer?) have a --debug-trace option.
Maybe it's undocumented now (shades of Undocumented DOS of yore :)
Please see 'man
On Saturday 08 January 2011 02:48 PM Neal Murphy wrote:
While I was integrating udev into my test/dev version of Smoothwall ...
Hi Neal,
This is only to acknowledge and thank you for your detailed comments.
I haven't had time to go into any depth at all, what with the NFL playoffs and
all, but
On Thu, 2011-01-06 at 02:08:45 AM, Simon Geard wrote ... if the system is completely frozen, it may be hardware related ...Hi Simon,Very good points, overall.When it crashes it's frozen all right (i.e. a crash crash).No hardware changes as of late.Seems some old hardware the latest Udev iteration
Hello,
Hardware: ASUS P4S533-MX, Intel Pentium 4, 3.06 GHz, 1 GB, PATA
Software: i686-pc-linux-gnu, (B)LFS, 2.6.36.2, ext2, udev-165
PROBLEM
System started crashing on boot-up recently, about 50% of the time.
Softly, i.e. after reboot, fsck returns 1 (errors found and corrected).
In the Udev
Simon, Trent, Mike:
Thank you very much for the rich, detailed, interesting
theories and explanations about video drivers, booting,
X, fonts, pixels, my boot-up component steps, etc.
All this knowledge and experience is obviously worth a
thread of its own, something I'd be following keenly.
BUT
On Jun 29, 07:40:18 AM, Simon wrote:
What exactly is your problem with running in the high-res mode?
If it's just that the font size is too small, I'd have to repeat
Stephane's suggestion of selecting a different console font
(somewhere in the kernel config, I think).
I'm confused. So
Hi Aleksandar, Andy, Neil, Simon and
all the other great participants in this thread:
Jun 22, 11:54:28 AM, Alex wrote:
At that point (nouveau Udev load? ), the screen goes
blank for a split second then continues OK all the way
to the console prompt.
Note: The screen resolution switches from
Hi
I played some more with the parameters you suggested be
changed in order to finally reach a config that would work with
nouveau and GeForce 8300GS on my system.
In the final analysis it seems that only two (2) are CRITICAL:
DD Graphics support Console display driver support
{*} Framebuffer
Jun 21, 2010 06:11:14 PM, Andrew Benton wrote.
Jun 21, 2010 08:54:20 PM, Aleksandar Kuktin wrote.
Jun 22, 2010 04:25:40 AM, Simon Geard wrote.
Hi guys,
The nouveau now works !! Boot-up, KDE, Fluxbox.
THANK YOU VERY MUCH!
Details:
The boot-up proceeds to the point it would go blank permanently
Jun 20, 2010 06:21:59 AM, Andrew Benton wrote
Jun 20, 2010 08:51:09 AM, Aleksandar Kuktin wrote
Can we see your 'config' file?
Sure. I'll try to attach it. If you do not get it
point me to some other way to pass it along.
...
Unfortunately (could my nouveau driver be jinxed? :):
Jun 20, 2010
Jun 20, 2010 06:21:59 AM, Andrew Benton wrote
Jun 20, 2010 08:51:09 AM, Aleksandar Kuktin wrote
Can we see your 'config' file?
Sure. I'll try to attach it. If you do not get it
point me to some other way to pass it along.
Back at the ranch ...
Jun 20, 2010 05:36:11 PM,
Jun 18, 2010 12:41:04 PM, Andrew Benton wrote
me his comments on the subject.
Hi Andy,
Thanks for your message. As I told Neil below,
I'm hard at work at going over some log datails, etc. now.
(I was hoping against hope Neil's interesting workaround
will bring me afloat, but no cigar).
Hello,i686-pc-linux-gnu, 2.6.34, udev-156, (B)LFSNVidia GeForce 8300GSI've been trying to install/run the nouveau "nouveau"kernel driver, to avoid installing the NVIDIA driverafter each kernel upgrade.PROBLEM:So far, if on the "nouveau" kernel, I lose the video (the screen goes blank) on boot-up
Hi,
System: Development (B)LFS
i686-pc-linux-gnu, 2.6.33.1, GRUB: 0.97
Motherboard: ASUS P5E-VM HDMI
Internal Graphics Display (IGD): Intel G35, HDMI output
External Video Card (PEG): ASUS GeForce 9500GT, PCIe x16, HDMI output
Monitor: Samsung SM2494, Wide (16:9), DVI input (through
Hello Simon Linux Fan,
The thread started as a complaint about UDEV
eliminating the only workaround, last_rule,
I could use to avoid the pollution of the
/dev with a relatively large number of
nonsensical floppy nodes (from my standpoint),
which was followed by a pleading for help.
It's taken
Alex:
In the past, I was able to avoid creation
of unnecessary fd nodes.
Mike McCarty:
In what sense unnecessary?
Do your floppy drives not support those modes?
There are tools which use the name of the device
to select their mode of operation, and
if you don't have a /dev node for that
On Fri, May 1, 2009 at 10:50 PM, Chris Staub ch...@beaker67.com wrote.
Hi Chris,
I think the main problem here is that youse guys
have not read my original post in any depth.
Let me be very clear:
You DON'T have to. Nor to give any reason for not
going over it at all or in any meaningful
Hi,
If true, this should go to the attention of LFS Developers.
If specific to my type configuration, maybe in a Wiki,
to whom it may concern.
If wrong, please disregard.
Before installing the 5.7, on my ncurses-5.4 system
(circa Oct. 2005), I had this chain of five links:
Hi Bruce,
On Fri, May 1, 2009 at 3:53 PM, Bruce Dubbs bruce.du...@gmail.com wrote:
are there any exceptions you may have to the prereqs that
are specified in section iv. Host System Requirements?
1. None that I know of. The steps ran successfully (as far
as they went). Nothing seems to have
On Fri, May 1, 2009 at 8:54 PM, Ken Moffat k...@linuxfromscratch.org wrote:
I'm still having trouble understanding this : you're saying that
you are in chroot building lfs-dev, and symlinks in your original
install are breaking, causing problems in e.g. Vim.
Note that at this point in a normal
Hello,
How can one find out what ALSA-project release
is used for the drivers in a specific Kernel version.
As a practical example, currently
ALSA-project: 1.0.19
BLFS-ALSA: 1.0.18
LFS-Kernel: 2.6.28.8
Which version ALSA drivers are actually used in, say, 2.6.28.8?
Thanks,
-- Alex
--
On Mon Mar 16 00:43:54 MDT 2009 Simon Geard wrote
Don't know about the BLFS checksums
Normally, when they use the phrase
Download MD5 sum: in the BLSF book,
I assume it's the md5sum, and in 99% of the instances
it is (with rare exceptions :-).
that url has version 0.95, also
with the md5sum
Hello,
In the BLFS Development book the md5sum for
'fop-0.95-src.tar.gz'
downloaded from
ftp://anduin.linuxfromscratch.org/BLFS/svn/f/;
is given as
184c578a6269a8287ed150e0fc12868d.
It appears to me more like
58593e6c86be17d7dc03c829630fd152
Please note that the other source
Hello,
i686-pc-linux-gnu, (B)LFS 2.6.28.2
Absolutely by happenstance, I noticed these first lines
in 'kern.log' file on any system boot:
... kernel: klogd 1.4.1, log source = /proc/kmsg started.
... kernel: Inspecting /boot/System.map
... kernel: Cannot find map file.
... kernel: No module
Hello,
i686-pc-linux-gnu, (B)LFS
The installation of udev-137 went very smoothly
and everything is humming along beautifully on
my 2.6.28.2 SATA machine.
Kudos and many thanks to the LFS developers.
LFS had fallen somewhat behind Udev releases,
so at some point, I decided to upgrade revision
by
Hi Simon,
On Sat, Jan 24, 2009 at 6:07 AM, Simon Geard wrote:
On Wed, 2009-01-14 at 21:15 -0500, alupu wrote:
- QUESTION
Does anybody know anything about the transition to 2.6.28 changing the
view of the system to a Universal, Uniform, Consistent, SATA
centric, etc.?
Disclaimer - I'm
Hello,
- SYSTEM (relevant points)
i686-pc-linux-gnu, (B)LFS.
ASUS P4S533-MX, Intel Pentium 4.
Two ATA (PATA native) drives, hdb (Linux) and hda (Windows)
Two ATAPI (PATA native) opticals, hdc and hdd.
SiS651 chipset connected with SiS652 for the integrated IDE
Master/Slave controllers featuring
Update: I managed to SUCCESSFULLY boot up the IDE LFS Linux 2.6.25.4 drive on
my new SATA machine.
Many thanks to Phill Upson, cx8508 and Mr. Beekmans.
Also thanks to the cast of thousands who rooted for me all along.
There are of course a lot of things still left for me to work on (clean up,
On 2008/05/19 Mon PM 09:27:30 EDT cx8508 wrote
try to enable the SCSI disk support and Serial ATA (SATA) support option
in the kernel configuration, and compile them directly into the kernel, not
as modules.
cx8508,
Thank you very much.
Please read on, if interested.
UPDATE
Since my last
Hello,
I'm trying to move an IDE LFS drive from an older PATA computer to a new
SATA computer. I've been unsuccessful so far.
After literally hundreds of iterations/permutations of Master/Slave, various
'rdev' settings, BIOS settings, kernel ... root=/dev/... in GRUB, Linux
versions
On 2008/05/19 Mon PM 06:00:57 EDT, Phill Upson wrote:
I think you are missing the driver for your hard disk controller in the
kernel (or as a module to be loaded by initrd). Try booting from a
livecd again and look at the output of lspci and lsmod, try to work out
which module is your disk
Hello Everybody,
SYSTEM
~~
686-pc-linux-gnu (B)LFS, 2.6.21.3,
UDEV-113, 26-modprobe.rules v.20070304.
Machine hardware pretty standard and run-of-the-mill.
Nothing complicated or fancy (including peripherals).
I'm not aware of any problem, the system just works.
BTW, no USB standalone
Hi Dan,
I apologize for my tardiness in thanking you for your interest in this.
In desperation, I had sent a cold e-mail to Roland McGrath (content at the end,
section 5).
He seemed to be one of the people most involved in glibc so I said what the
heck.
I left a period of time to account for
Hi Ken,
First, thanks again for your interest and words.
I'm quickly cutting to the chase now:
The printing is fixed!
All I did was to simply delete it ('lpadmin -x printer') and then run the
_exact_ command I once used to install it (I keep records :-). Absolutely no
any other action
Hi everybody,
LFS/BLFS system.
i686-pc-linux-gnu 2.6.19.2
CUPS 1.2.7. Parallel printer (garden variety).
Udev 056 (LFS circa Sept. 2005)
Works perfectly.
BTW, by perfect here I mean the basic functions work clean and fully:
- Graphics (Xfree86-4.6)
- Networking
- Sound
- Printing
(other functions
Dan, Ken, Randy:
Thank you very much for your interest in the subject.
Unfortunately your comments while very interesting and meaningful haven't
helped in moved me any closer to solving the problem.
Except Dan's try running strace around the lp call. I will.
Going over your comments I realized
Andrew, Ken,
Alex:
there's a confusion on page 103: 'console'
and 'null' are mounted twice and 'console' with different modes (622
seems to be the correct choice).
Apologies for using ?mount? instead of ?mknod?. I guess it can happen to a
fella when the embarrassment of having compiled
PROBLEM: New, complete LFS-6.1 system doesn't boot (details below).
- Book: LFS v6.1 All packages installed. No deviations. No errors.
- Host: LiveCD (lfslivcd-x86-6.1-2.iso)
- i686-pc-linux-gnu
- ASUS P4S533, P4-3.066GHz, BIOS Award v6.0 v1006, HT enabled
DETAILS:
lfskernel-2.6.11.12
71 matches
Mail list logo