You are not logged in.
:shock: Booted way faster but one i had no sound and two no network.
and i get a bunch of errors about status, stat_busy and stat_done not being commands.O well back to normal. But i did remove devfs, lvm, and usbcore things since i have them built-in to the kernel. I made it mount local filesystems simultaniously like eWoud said.
Thanks for some tips tho.
that's funny, it shouldnt do that.
what's the /etc/rc.d/hwd got in it?
#!/bin/bash
. /etc/rc.conf
. /etc/rc.d/functions
case "$1" in
start)
stat_busy "Autodetecting Hardware with lshwd"
lshwd -a >/dev/null
if [ $? -gt 0 ]; then
stat_fail
else
stat_done
fi
;;
stop)
/bin/true
;;
restart)
$0 stop
sleep 1
$0 start
;;
*)
echo "usage: $0 {start|stop|restart}"
;;
esacis what i have...
iphitus
Offline
Hmm, I run all my computers without hotplug in rc.conf.. basically I used lshwd and put all of the (needed) modules into modules array in rc.conf. Removing hotplug from rc.conf does not mean that I lose the ability to have various thingies automagically detected when I plug them in (USB sticks and my MIDI keyboard is what I use).
Offline
Another thing which could be used is giving kernel command-line parameters "ideX=noprobe" or "hdX=noprobe".
In my box I have a hard disk connected to /dev/hda (ide0 master), and a DVD-drive connected to /dev/hdc (ide1 master),ide interfaces ide2-ide5 (Yes K8T Neo has quite many;-) are not used so I commanded kernel to not probe them:
ide2=noprobe ide3=noprobe ide4=noprobe ide5=noprobe
Jari
Only gardening is important.
Offline
:shock: Booted way faster but one i had no sound and two no network.
and i get a bunch of errors about status, stat_busy and stat_done not being commands.O well back to normal. But i did remove devfs, lvm, and usbcore things since i have them built-in to the kernel. I made it mount local filesystems simultaniously like eWoud said.
Thanks for some tips tho.
Yeah, I had to revert back to normal scripts after my box refused to shut down anymore
Things that seem to work for me:
1. In /etc/inittab: rm:once:rc.multi
2. sleep 10 in the beginning of rc.multi
3. ideX=noprobe kernel command-line parameter
4. "ShortIDEDelays"- patch using ide_delay=10 (original is 50). ide_delay=5 sometimes failed to boot and oopsed the kernel.
5. "RTCNoSync" kernel patch
Jari
Only gardening is important.
Offline
3. Changed from Kdm to Gdm
--------------------------
-At the moment Gdm seems to start about 4-5 seconds faster than Kdm. I don't know why.
Shameless advertising but... you can also use Simple Login Manager. It's in AUR.
I use it because I don't want gnome/kde, but I think it must be faster than kdm/gdm too.
One of the main causes of the fall of the Roman Empire was that, lacking zero,
they had no way to indicate successful termination of their C programs.
Offline
I don't use hwd or hotplug, for my USB thumbdrive/CDRW/DVD drives i use Autofs. I just load them via modules array, or built-in to the kernel. I got sound working by issuing "alsaconf" and it worked again. Network worked really but had a host problem so it was
myusername@(none). XFCE complained about it.
What's usbfs good for and if i removed rc.sysinit can i remove it the entry from fstab too?
Shameless advertising but... you can also use Simple Login Manager. It's in AUR.
I use it because I don't want gnome/kde, but I think it must be faster than kdm/gdm too.
Looks easy enough... one thing can you choose between WM/DEs cause i sometimes want to use KDE instead of XFCE... and logging in and changes .xinitrc every time doesn't sound like much fun.
Offline
Shameless advertising but... you can also use Simple Login Manager. It's in AUR.
I use it because I don't want gnome/kde, but I think it must be faster than kdm/gdm too.
Thanks for pointing this out! For a long time I was looking for a decent DM but they all have too many dependancies (gnome, kde), or they are too ugly (wdm) or just a wrong shade of pink
.
Offline
Looks easy enough... one thing can you choose between WM/DEs cause i sometimes want to use KDE instead of XFCE... and logging in and changes .xinitrc every time doesn't sound like much fun.
I'm not sure if it is possible. It seems to be disabled in the latest version. Perhaps the CVS/SVN version has the functionality, but I wouldn't know, because I only use SLIM to start xfce4 using xinitrc.
Perhaps you can have a question dialog using (g)xmessage from your xinitrc, asking you whether you want to start xfce or KDE.
One of the main causes of the fall of the Roman Empire was that, lacking zero,
they had no way to indicate successful termination of their C programs.
Offline
Another thing which could be used is giving kernel command-line parameters "ideX=noprobe" or "hdX=noprobe".
In my box I have a hard disk connected to /dev/hda (ide0 master), and a DVD-drive connected to /dev/hdc (ide1 master),ide interfaces ide2-ide5 (Yes K8T Neo has quite many;-) are not used so I commanded kernel to not probe them:
ide2=noprobe ide3=noprobe ide4=noprobe ide5=noprobeJari
where do i put these? i can think of a number of places for a a 'kernel command-line parameter'
thx
"Ignorance is bliss, for stupid people."
"open-source is [...] programming Darwinism."
Vaughan-Nichols
Offline
citral wrote:Shameless advertising but... you can also use Simple Login Manager. It's in AUR.
I use it because I don't want gnome/kde, but I think it must be faster than kdm/gdm too.
Thanks for pointing this out! For a long time I was looking for a decent DM but they all have too many dependancies (gnome, kde), or they are too ugly (wdm) or just a wrong shade of pink
.
Woah... very nice
There's also http://qingy.sourceforge.net/ which is a little different (it uses directfb... doesn't even use X, you can use it to log into a terminal too)
Maybe I'll try out slim... it looks really nice
Offline
Woah... very nice
There's also http://qingy.sourceforge.net/ which is a little different (it uses directfb... doesn't even use X, you can use it to log into a terminal too)
Maybe I'll try out slim... it looks really nice
Nice indeed! I've never really been one to use all the graphical login stuff, but "Simple Login Manager" and the one you mentioned "Gingy" both look pretty interesting. I may have to give them a try.
Phrakture, do you use gingy currently?
--
Some of the world's greatest feats were
accomplished by people not smart enough
to know they were impossible.
-- Doug Larson
Offline
These both look like what I've been looking for in a login manager! Good lookin' and not branded by GNOME or KDE. I'll have to try them both and report back.
Offline
Nice indeed! I've never really been one to use all the graphical login stuff, but "Simple Login Manager" and the one you mentioned "Gingy" both look pretty interesting. I may have to give them a try.
Phrakture, do you use gingy currently?
Heh, it's a Q, by the way. But no I don't use it.... yet. This week I think I'm going to set it up, and see how it works.
I like it because it allows you to login to the console as well as X
Offline
I like it because it allows you to login to the console as well as X
Yep, that's what caught my eye on it also. I use the console a good bit, so I thought that would be interesting.
Let us know how it goes iBertus!
--
Some of the world's greatest feats were
accomplished by people not smart enough
to know they were impossible.
-- Doug Larson
Offline
I've used qingy before I used slim, and I can say qingy is a nice and mature app.
There was just one thing I didn't like about it. Since it runs on the framebuffer, if you want to start up your KDE, xfce, or whatever, you have to wait for the X server to start up first. The advantage of a classical login manager(gdm/kdm/slim) is that X is already started (so you don't have that extra step of starting X).
You start to notice the difference if you reboot a lot (like I do).
One of the main causes of the fall of the Roman Empire was that, lacking zero,
they had no way to indicate successful termination of their C programs.
Offline
I've used qingy before I used slim, and I can say qingy is a nice and mature app.
There was just one thing I didn't like about it. Since it runs on the framebuffer, if you want to start up your KDE, xfce, or whatever, you have to wait for the X server to start up first. The advantage of a classical login manager(gdm/kdm/slim) is that X is already started (so you don't have that extra step of starting X).
You start to notice the difference if you reboot a lot (like I do).
Right, but I was planning on using qingy for text only logins, having it run on vt1 through vt6 and vt7 will startup slim...
I'm just speculating now... i'll mess with some things tonight, and we'll see how it goes
Offline
I read about qingy in Arch forum long time ago and tried it.
It is fast and can be made to look better by using themes. Setting it up is also not that difficult.
As I use gnome most of the times (kde, xfce4 and e17-cvs other times), so an X based DM is better suited for my use. I'll give a try to SLiM sometime.
~ Aha ~
Offline
where do i put these? i can think of a number of places for a a 'kernel command-line parameter'
thx
Long time, no see, sorry.
I use lilo, so I have these in /etc/lilo.conf on its "append"-line:
append="ide2=noprobe ide3=noprobe"
With grub, the file is /boot/grub/menu.lst but and these go directly on "kernel"- line (no "append"- line with grub)
Jari
Only gardening is important.
Offline