Re: [gentoo-user] mount cdrom: No buffer space available

2008-01-01 Thread Cocoy Dayao


On Jan 2, 2008, at 2:42 PM, Paul Colquhoun wrote:


On Wed, 2 Jan 2008, Cocoy Dayao wrote:






You could try moving iso9660 to the top in /etc/filesystems, so it  
gets

tried first.




yep. done. thanks!

--
Cocoy
"People who are really serious about software should make their own  
hardware." --Alan Kay


--
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] mount cdrom: No buffer space available

2008-01-01 Thread Paul Colquhoun
On Wed, 2 Jan 2008, Cocoy Dayao wrote:
> 
> On Jan 2, 2008, at 1:32 PM, Adam Carter wrote:
> 
> >>
> > If it says
> > CONFIG_ISO9660_FS=y -> its built into the kernel, and should be  
> > working
> 
> yep. it is built into the kernel. so auto should work, correct?


You could try moving iso9660 to the top in /etc/filesystems, so it gets 
tried first.


-- 
Reverend Paul Colquhoun, ULC.http://andor.dropbear.id.au/~paulcol
 Asking for technical help in newsgroups?  Read this first:
http://catb.org/~esr/faqs/smart-questions.html#intro
-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] mount cdrom: No buffer space available

2008-01-01 Thread Cocoy Dayao


On Jan 2, 2008, at 1:32 PM, Adam Carter wrote:




If it says
CONFIG_ISO9660_FS=y -> its built into the kernel, and should be  
working


yep. it is built into the kernel. so auto should work, correct?

--
Cocoy
"People who are really serious about software should make their own  
hardware." --Alan Kay


--
[EMAIL PROTECTED] mailing list



RE: [gentoo-user] mount cdrom: No buffer space available

2008-01-01 Thread Adam Carter
> data
> 
> > However, if it's a data cd, then iso9660 MUST either be build into  
> > the kernel
> > or available as a module for the "auto" part of your cdrom fstab  
> > line to work
> > correctly... hmmm... maybe need also "autoload" in the module  
> > loading section
> > of the kernel configurator.
> >
> 
> 
> ok. thanks! i'll check that out.

Try;
$ grep ISO9660 /usr/src/linux/.config

If it says
CONFIG_ISO9660_FS=y -> its built into the kernel, and should be working
CONFIG_ISO9660_FS=m -> its built as a module, so try 'modprobe iso9660'
and attempt the mount again (but it should load the module automatically
# CONFIG_ISO9660_FS is not set -> you need to build it. You might as
well just build it as a module, so you don't have to change your kernel
and reboot etc. Just update your .config file, then run "make modules &&
make modules_install && modprobe iso9660" and try to mount it again. 

-Ad


--
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] mount cdrom: No buffer space available

2008-01-01 Thread Cocoy Dayao


On Jan 2, 2008, at 12:22 PM, Jerry McBride wrote:


On Tuesday 01 January 2008 10:50:26 pm Cocoy Dayao wrote:




What is the cdrom? Music or Data? You can't mount a music cdrom...  
period.


data

However, if it's a data cd, then iso9660 MUST either be build into  
the kernel
or available as a module for the "auto" part of your cdrom fstab  
line to work
correctly... hmmm... maybe need also "autoload" in the module  
loading section

of the kernel configurator.




ok. thanks! i'll check that out.

--
Cocoy
"People who are really serious about software should make their own  
hardware." --Alan Kay


--
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] mount cdrom: No buffer space available

2008-01-01 Thread Jerry McBride
On Tuesday 01 January 2008 10:50:26 pm Cocoy Dayao wrote:
> Encountered:
>
> warhammer etc # mount /dev/cdrom
> mount: block device /dev/cdrom is write-protected, mounting read-only
> mount: No buffer space available
>
> i googled and found a "no buffer space available".
>
> followed suggestions on the thread:
>
> warhammer etc # mount -va && df && mount -v /mnt/cdrom
> mount: /dev/sda7 already mounted on /mnt/home1
> mount: /dev/sda5 already mounted on /mnt/oldroot
> mount: /dev/sda1 already mounted on /mnt/Movies
> mount: /dev/sda2 already mounted on /mnt/windows2
> mount: /dev/sda3 already mounted on /mnt/boot
> mount: shm already mounted on /dev/shm
> mount: you didn't specify a filesystem type for /dev/cdrom
> I will try all types mentioned in /etc/filesystems or /proc/
> filesystems
> Trying #
> Trying #vfat
> Trying ext4dev
> mount: block device /dev/cdrom is write-protected, mounting read-only
> mount: you didn't specify a filesystem type for /dev/cdrom
> I will try all types mentioned in /etc/filesystems or /proc/
> filesystems
> Trying #
> Trying #vfat
> Trying ext4dev
> Trying squashfs
> Trying msdos
> Trying hfsplus
> Trying gfs2
> mount: No buffer space available
>
> ***
> so i guess it was looking for a lot of fs, but the machine couldn't
> find the right one.
> i dunno why.
>
> my fstab:
>
> /dev/cdrom/mnt/cdrom  autoauto,users  0 0
> #/dev/fd0 /mnt/floppy autonoauto  0 0
> /dev/hda1 /   ext3noatime 0 1
> /dev/sda7 /mnt/home1  xfs user0 0
> /dev/sda6 noneswapsw  0 0
> /dev/sda5 /mnt/oldrootxfs user0 0
> /dev/sda1 /mnt/Movies xfs user0 0
> /dev/sda2 /mnt/windows2   vfatuser0 0
> /dev/sda3 /mnt/boot   ext3noatime 1 2
> /dev/sdb  /mnt/ipod   hfsplus noauto,user 0 0
>
> so i changed /mnt/cdrom from auto to iso9660
>
> and... everything works. no more "no buffer buffer space available"
> error after that.
>
> my question is... is there a way to set it to auto and still it will
> pick up iso9660? or maybe i missed some setting on the kernel that
> needs to be set?
>

What is the cdrom? Music or Data? You can't mount a music cdrom... period. 
However, if it's a data cd, then iso9660 MUST either be build into the kernel 
or available as a module for the "auto" part of your cdrom fstab line to work 
correctly... hmmm... maybe need also "autoload" in the module loading section 
of the kernel configurator.


Cheers.








-- 


From the Desk of: Jerome D. McBride
--
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] mount cdrom: No buffer space available

2008-01-01 Thread Cocoy Dayao

Encountered:

warhammer etc # mount /dev/cdrom
mount: block device /dev/cdrom is write-protected, mounting read-only
mount: No buffer space available

i googled and found a "no buffer space available".

followed suggestions on the thread:

warhammer etc # mount -va && df && mount -v /mnt/cdrom
mount: /dev/sda7 already mounted on /mnt/home1
mount: /dev/sda5 already mounted on /mnt/oldroot
mount: /dev/sda1 already mounted on /mnt/Movies
mount: /dev/sda2 already mounted on /mnt/windows2
mount: /dev/sda3 already mounted on /mnt/boot
mount: shm already mounted on /dev/shm
mount: you didn't specify a filesystem type for /dev/cdrom
   I will try all types mentioned in /etc/filesystems or /proc/ 
filesystems

Trying #
Trying #vfat
Trying ext4dev
mount: block device /dev/cdrom is write-protected, mounting read-only
mount: you didn't specify a filesystem type for /dev/cdrom
   I will try all types mentioned in /etc/filesystems or /proc/ 
filesystems

Trying #
Trying #vfat
Trying ext4dev
Trying squashfs
Trying msdos
Trying hfsplus
Trying gfs2
mount: No buffer space available

***
so i guess it was looking for a lot of fs, but the machine couldn't  
find the right one.

i dunno why.

my fstab:

/dev/cdrom  /mnt/cdrom  autoauto,users  0 0
#/dev/fd0   /mnt/floppy autonoauto  0 0
/dev/hda1   /   ext3noatime 0 1
/dev/sda7   /mnt/home1  xfs user0 0
/dev/sda6   noneswapsw  0 0
/dev/sda5   /mnt/oldrootxfs user0 0
/dev/sda1   /mnt/Movies xfs user0 0
/dev/sda2   /mnt/windows2   vfatuser0 0
/dev/sda3   /mnt/boot   ext3noatime 1 2
/dev/sdb/mnt/ipod   hfsplus noauto,user 0 0

so i changed /mnt/cdrom from auto to iso9660

and... everything works. no more "no buffer buffer space available"  
error after that.


my question is... is there a way to set it to auto and still it will  
pick up iso9660? or maybe i missed some setting on the kernel that  
needs to be set?


thanks.
--
Cocoy
"People who are really serious about software should make their own  
hardware." --Alan Kay


--
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] 64-bit blues: ndiswrapper

2008-01-01 Thread david

Grant wrote:

The built-in Atheros AR5006EG wireless adapter in my Acer Aspire 4720Z
laptop doesn't work with madwifi-ng yet.  ndiswrapper is reported to
work on ndiswrapper.sourceforge.net but there is no 64-bit driver
listed.  I've found a 64-bit Vista driver but ndiswrapper doesn't work
with Vista drivers.  Is there any way to use a 32-bit driver with
ndiswrapper on a 64-bit system?

If this wireless card is impossible to use on a 64-bit Linux system I
guess I'll buy a PCI Express or USB card.  Any form factor,
manufacturer, or chipset recommendations?

- Grant

P.S. 64-bits just aren't worth it on the desktop.
  

I have used the windows 64 from here;
http://www.atheros.cz/

--
Powered by GNU/Linux

--
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] Kodak Z1275

2008-01-01 Thread Ted Ozolins
[EMAIL PROTECTED] wrote:
> On Tuesday 01 January 2008 21:43:49 Florian Philipp wrote:
>> On Tue, 2008-01-01 at 20:14 +0200, [EMAIL PROTECTED] wrote:
>>> Hi all.
>>> How I can connect my digital camera Kodak Z1275 to my love gentoo?
>> Did you try media-gfx/gphoto2 ?
> 
> I try with emerge media-libs/libgphoto2 with CAMERAS="cameras_kodak_dc120 
> cameras_kodak_dc210 cameras_kodak_dc240 cameras_kodak_dc3200 
> cameras_kodak_ez200". But my camera don't support
did you connect your camera and use gphoto2 to scan for it?

-- 
Ted Ozolins (VE7TVO)
Cranbrook, B.C.
-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] Nvidia users: please sign petition for open/free drivers

2008-01-01 Thread Jesús Guerrero
On Tue, 1 Jan 2008 19:51:36 +0100
"Hemmann, Volker Armin" <[EMAIL PROTECTED]> wrote:

> On Montag, 31. Dezember 2007, Enrico Weigelt wrote:
> > Hi folks,
> >
> >
> > I'd just want to let you know there's an petition to NV on
> > opening their driver code (or at least specs) to the free world:
> >
> > * http://www.petitiononline.com/nvfoss/
> 
> no, 'online petitions' are a worthless waste of time. They are like a fart in 
> the wind - just worse. They are like farting and then tell everybody that you 
> have farted. You are just angry that your beloved, but maybe crappy hardware 
> does not work with a driver that is pretty old by now.

Not true. It is true that a petition by itself will not do anything,
but it serves another purposes. Any joining effort demonstrates that
people actually care about a problem. And, by the way, if you fart,
the less you can do is to be honest, and not blame anyone else while
you are the only guilty.

This is not about old or new hardware, this is about getting a free
driver, and that, as linux users, is something that would benefit
everyone in this list. You don't seem to understand what this is
about at all.

> >
> > Please sign the petition and spread around this link.
> 
> Please don't spam.

We could argue if this topic is valid for the list or not, that is
debatable, but everything you wrote above this last sentence is pure
spam. Far more spammy than the post of the original poster. And, in
turn, you generated a need for additional responses, like the one from
Neil Walker and this one that I am writing right now.

Thing that could have been avoided if you just posted something in
the lines of "Isn't this offtopic?", and nothing more.

Regards.
-- 
Jesús Guerrero <[EMAIL PROTECTED]>
--
[EMAIL PROTECTED] mailing list



[gentoo-user] 64-bit blues: ndiswrapper

2008-01-01 Thread Grant
The built-in Atheros AR5006EG wireless adapter in my Acer Aspire 4720Z
laptop doesn't work with madwifi-ng yet.  ndiswrapper is reported to
work on ndiswrapper.sourceforge.net but there is no 64-bit driver
listed.  I've found a 64-bit Vista driver but ndiswrapper doesn't work
with Vista drivers.  Is there any way to use a 32-bit driver with
ndiswrapper on a 64-bit system?

If this wireless card is impossible to use on a 64-bit Linux system I
guess I'll buy a PCI Express or USB card.  Any form factor,
manufacturer, or chipset recommendations?

- Grant

P.S. 64-bits just aren't worth it on the desktop.
-- 
[EMAIL PROTECTED] mailing list



{Spam?} Re: [gentoo-user] Nvidia users: please sign petition for open/free drivers

2008-01-01 Thread Neil Walker

Hemmann, Volker Armin wrote:

no, 'online petitions' are a worthless waste of time.


Not true. Here is just one recent example:

http://www.pm.gov.uk/output/Page13090.asp



Be lucky,

Neil



--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


--
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] Kodak Z1275

2008-01-01 Thread [EMAIL PROTECTED]
On Tuesday 01 January 2008 21:43:49 Florian Philipp wrote:
> On Tue, 2008-01-01 at 20:14 +0200, [EMAIL PROTECTED] wrote:
> > Hi all.
> > How I can connect my digital camera Kodak Z1275 to my love gentoo?
>
> Did you try media-gfx/gphoto2 ?

I try with emerge media-libs/libgphoto2 with CAMERAS="cameras_kodak_dc120 
cameras_kodak_dc210 cameras_kodak_dc240 cameras_kodak_dc3200 
cameras_kodak_ez200". But my camera don't support
-- 
--
With best regards, ezotrank
kernel 2.6.23-gentoo-r2, system uptime: 22:05:32 up 9:46, 1 user, load 
average: 0.43, 0.83, 0.73
--


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] Kodak Z1275

2008-01-01 Thread Florian Philipp
On Tue, 2008-01-01 at 20:14 +0200, [EMAIL PROTECTED] wrote:
> Hi all. 
> How I can connect my digital camera Kodak Z1275 to my love gentoo?

Did you try media-gfx/gphoto2 ?


signature.asc
Description: This is a digitally signed message part


Re: [gentoo-user] Nvidia users: please sign petition for open/free drivers

2008-01-01 Thread Hemmann, Volker Armin
On Montag, 31. Dezember 2007, Enrico Weigelt wrote:
> Hi folks,
>
>
> I'd just want to let you know there's an petition to NV on
> opening their driver code (or at least specs) to the free world:
>
> * http://www.petitiononline.com/nvfoss/

no, 'online petitions' are a worthless waste of time. They are like a fart in 
the wind - just worse. They are like farting and then tell everybody that you 
have farted. You are just angry that your beloved, but maybe crappy hardware 
does not work with a driver that is pretty old by now.

>
> Please sign the petition and spread around this link.

Please don't spam.
-- 
[EMAIL PROTECTED] mailing list



[gentoo-user] Kodak Z1275

2008-01-01 Thread [EMAIL PROTECTED]
Hi all. 
How I can connect my digital camera Kodak Z1275 to my love gentoo?
-- 
--
With best regards, ezotrank
kernel 2.6.23-gentoo-r2, system uptime: 20:13:39 up 7:54, 1 user, load 
average: 0.27, 0.28, 0.13
--


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] xdm login problems after recent emerge

2008-01-01 Thread Michal 'vorner' Vaner
Hello

On Tue, Jan 01, 2008 at 03:29:25PM +, Mick wrote:
> I stopped/zapped xdm, ran startx and from an xterm I was able to run fluxbox 
> which started OK.  So, I am not sure if you are right that the start up 
> script crashes (I wonder, shouldn't I see something in the logs about it?)  
> If it crashed wouldn't it also crash when called from within an xterm?  When 
> I ran etc-update I had to update a number of scripts (some of them were 
> trivial - automerged) and some of them were related to halt.sh, and so on, 
> but I cannot recall any xdm related scripts.  Is there an etc-update history 
> somewhere on my machine?

I didn't mean the xdm script (which, obviously, works fine), but the
script started when you log in. The one in sessions is probably the one.

Actually, how it works: xdm starts X and shows the login screen. When
you log in, it starts something on the X server. When the something
stops (for any reason), xdm restarts X and shows the login screen again.

So I think the thing started by xdm terminates too early for some
reason, crash was the first idea I got. All this is just a guess, how it
looks to me, I do not say it is the only possible cause (crashing X
could be the cause too, and xdm would just restart it).

-- 
Support your right to arm bears!!

Michal 'vorner' Vaner


pgpjQoUeWlAXM.pgp
Description: PGP signature


Re: [gentoo-user] Gentoo & GRUB help

2008-01-01 Thread BRM
--- BRM <[EMAIL PROTECTED]> wrote:
> When Grub came up, it was
> thinking hdb equalled hd0 instead of hd1. So while it worked fine
> with
> hd1 from the CD (it didn't like hd0 then), it was mixed up when grub
> actually ran.

> Any suggestions on how to fix this so that grub runs well from within
> Linux?

Ok, well - I got it working by setting up grub.conf to focus on hd0,
while at the grub prompt I referred to it as hd1. That is, imho, just
weird, and another reason why LILO wins out in my book as LILO matches
Linux's device names pretty well.

Now if I can just figure out this "base-layout-1" versus
"base-layout-2" thing that Device Mapper and LVM init scripts are
complaining about. (Tips welcomed!)

Thanks!

Ben
-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] Gentoo & GRUB help

2008-01-01 Thread BRM
--- Iain Buchanan <[EMAIL PROTECTED]> wrote:
> Happy new year!

Happy new year to you all to!
 
> On Mon, 2007-12-31 at 11:16 -0800, BRM wrote:
> [snip]
> > All seems well. It boots and presents the menu, but then can't find
> the
> > kernel when I select "Gentoo Linux" or try to manually run the
> lines. I
> > tried using "find" at the grub command prompt during the boot
> process,
> > but it couldn't find it either. I haven't tried the Slackware
> kernel
> > yet, as I am mostly concerned about the Gentoo kernel.
> have you tried grubs completion?  if you type "kernel (hd1,1)/" and
> then
>  it should try and complete the line for you.  (from the grub
> command prompt, once you've booted into the grub shell)  It could be
> possible that your bios / grub have swapped the drive assignment
> around
> during boot.  Try all your (hdx,y) combinations with grub completion
> until you find one that has /gentoo on it.
"Mick" <[EMAIL PROTECTED]> wrote:
> Your system will look at the first device that the BIOS finds for a
> bootloader.  That 'should' be /dev/hda, but it could well be /dev/sda
> (check device map and also use Grub's tab completion to see what the
> BIOS/Grub sees first).


Thanks. I had tried tab-completion while at the grub command-line from
the CD during install, but it wasn't working. When Grub came up, it was
thinking hdb equalled hd0 instead of hd1. So while it worked fine with
hd1 from the CD (it didn't like hd0 then), it was mixed up when grub
actually ran.

Any suggestions on how to fix this so that grub runs well from within
Linux?

"Mick" <[EMAIL PROTECTED]> wrote:
> Check your /boot/grub/device.map to make sure that devices correspond
> to the expected grub nomenclature.
Also - (per Mick's e-mail)

> > Note: I am using LVM2 under this Gentoo install - but not for /boot
> or
> > /.
> it shouldn't interfere with /boot or /

That's what I thought, I just figured I mention it just in case.
 
> > What am I missing?
> don't know, hope my hints can help.

Thanks, it sure did. :->

Ben
-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] xdm login problems after recent emerge

2008-01-01 Thread Mick
On Tuesday 01 January 2008, Michal 'vorner' Vaner wrote:
> Hello
>
> On Tue, Jan 01, 2008 at 10:48:52AM +, Mick wrote:
> > Happy New Year to all!
> >
> > I find my self in a bit of a pickle after a recent emerge.  When I
> > enter my username+passwd at the xdm login screen it sort of tries to
> > load up fluxbox, but within a second or so it returns to the login
> > screen. I can't see anything worth mentioning in the logs. I have
> > downgraded baselayout, sysvinit and freetype but the problem remains.
> > Any ideas? These are the packages emerged recently:
>
> This sounds to me like the fluxbox starter (I'm not sure if fluxbox by
> itself or some script that starts it with one or two other programs)
> crashes. Did you try running revdep-rebuild?

Thanks, I am running it now.  It only wants to remerge:

All prepared. Starting rebuild...
emerge --oneshot -v =media-video/ffmpeg-0.4.9_p20070616 
=media-libs/libquicktime-1.0.1 =media-libs/xine-lib-1.1.8

I believe this is because of the media-libs/x264-svn-20070924 emerged package.

> And, if you want to experiment, you can start X from vt, lets say:
>
> X :1.0 (on :0.0, it is already running with xdm)
>
> then switch back to vt (probably different one) and start an xterm
>
> DISPLAY=:1.0 xterm
>
> then switch back to your new X (ctrl+f8 -- f7 is the xdm one) and try
> starting fluxbox from the xterm to see what happens.
>
> Did it help?

I stopped/zapped xdm, ran startx and from an xterm I was able to run fluxbox 
which started OK.  So, I am not sure if you are right that the start up 
script crashes (I wonder, shouldn't I see something in the logs about it?)  
If it crashed wouldn't it also crash when called from within an xterm?  When 
I ran etc-update I had to update a number of scripts (some of them were 
trivial - automerged) and some of them were related to halt.sh, and so on, 
but I cannot recall any xdm related scripts.  Is there an etc-update history 
somewhere on my machine?

BTW, this is what I have under /etc/X11/Sessions/fluxbox:

eval "$(gpg-agent --daemon)"
/usr/bin/startfluxbox
kill `echo ${GPG_AGENT_INFO} | cut -d ':' -f 2`


Thank you very much for your help!
-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] xdm login problems after recent emerge

2008-01-01 Thread Michal 'vorner' Vaner
Hello

On Tue, Jan 01, 2008 at 10:48:52AM +, Mick wrote:
> Happy New Year to all!
> 
> I find my self in a bit of a pickle after a recent emerge.  When I
> enter my username+passwd at the xdm login screen it sort of tries to
> load up fluxbox, but within a second or so it returns to the login
> screen. I can't see anything worth mentioning in the logs. I have
> downgraded baselayout, sysvinit and freetype but the problem remains.
> Any ideas? These are the packages emerged recently:

This sounds to me like the fluxbox starter (I'm not sure if fluxbox by
itself or some script that starts it with one or two other programs)
crashes. Did you try running revdep-rebuild?

And, if you want to experiment, you can start X from vt, lets say:

X :1.0 (on :0.0, it is already running with xdm)

then switch back to vt (probably different one) and start an xterm

DISPLAY=:1.0 xterm

then switch back to your new X (ctrl+f8 -- f7 is the xdm one) and try
starting fluxbox from the xterm to see what happens.

Did it help?

-- 
No, you will not fix me
Computer

Michal 'vorner' Vaner


pgpndmnVXPEm0.pgp
Description: PGP signature


Re: [gentoo-user] xdm login problems after recent emerge

2008-01-01 Thread Mick
On 01/01/2008, Iain Buchanan <[EMAIL PROTECTED]> wrote:
>
> On Tue, 2008-01-01 at 10:48 +, Mick wrote:
> > Happy New Year to all!
> >
> > I find my self in a bit of a pickle after a recent emerge.  When I
> > enter my username+passwd at the xdm login screen it sort of tries to
> > load up fluxbox, but within a second or so it returns to the login
> > screen. I can't see anything worth mentioning in the logs. I have
> > downgraded baselayout, sysvinit and freetype but the problem remains.
> > Any ideas? These are the packages emerged recently:
>
> [snip]
>
> > I don't have a problem login in at the console, so this must be
> > xdm/Xorg related I guess.  As this is the laptop that I take to work
> > and my holidays end today all suggestions are welcomed!  :)
>
> This happens to me when one of my services has errors, or fails to
> start.  Look for any [ !! ] or other messages on vt1.  btw, this assumes
> you can switch back to X ok (ctrl-alt-f7 usually)?

Thanks Iain,

On my machines if a service fails to start it returns me to vt1, but I
am still able to load xorg and login fine after I switch to vt7.  I
didn't notice something amiss with the vt1 boot messages.

What else I could try? I guess downgrading all the packages of the
last emerge could be a short term solution, albeit a bit blunt.
-- 
Regards,
Mick
-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] xdm login problems after recent emerge

2008-01-01 Thread Iain Buchanan

On Tue, 2008-01-01 at 10:48 +, Mick wrote:
> Happy New Year to all!
> 
> I find my self in a bit of a pickle after a recent emerge.  When I
> enter my username+passwd at the xdm login screen it sort of tries to
> load up fluxbox, but within a second or so it returns to the login
> screen. I can't see anything worth mentioning in the logs. I have
> downgraded baselayout, sysvinit and freetype but the problem remains.
> Any ideas? These are the packages emerged recently:

[snip]

> I don't have a problem login in at the console, so this must be
> xdm/Xorg related I guess.  As this is the laptop that I take to work
> and my holidays end today all suggestions are welcomed!  :)

This happens to me when one of my services has errors, or fails to
start.  Look for any [ !! ] or other messages on vt1.  btw, this assumes
you can switch back to X ok (ctrl-alt-f7 usually)?

HTH,
-- 
Iain Buchanan 

You know you're using the computer too much when:
you look out of the bus/car window on the way to work and think "hey, these
graphics are pretty cool" 

-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] Re: Gentoo & GRUB help

2008-01-01 Thread Iain Buchanan

On Tue, 2008-01-01 at 10:20 +, Mick wrote:
> Happy New Year!

so far :) 1 almost down and 365 to go!

> BRM wrote:
> 
> > The system is set to boot off of /dev/hdb2 (ext2) and use /dev/hdb1 as
> > the root. I believe the boot device is hd1,1 in grub terminology.
> 
> Yes.
> 
> > The system has 3 hard drives: hda, hdb, and sda; as well as a dvd drive
> > (hdc).
> 
> Check your /boot/grub/device.map to make sure that devices correspond to the
> expected grub nomenclature.  Use  after you run # grub for
> root to find out where Grub thinks its root fs resides.

in my experience, it is not enough just to run grub from within linux -
you have to boot to grub.  YMMV.

> > /dev/hdb2 has the following structure:
> >  - list of all my Slackware kernels
> >  - gentoo/bzImage
> >  - gentoo/bzImage_2-6-23-gentoo-r3
> >  - grub/
> > 
> > Below is my grub.conf (minus comment lines):
> > 
> > timeout 30
> > default 0
> > fallback 1
> > title Gentoo Linux
> > root (hd1,1)
> > kernel /gentoo/bzImage root=/dev/hdb1
> 
> I assume from what you said above that when you run ls -la /gentoo/bzImage
> you can see the kernel image you are trying to boot, right?

not quite!  root is (hd1,1) which is hdb2.  This is grub's root device,
ie your boot partition (if you have one).  The kernel line specifies the
linux root as hdb1.  so `ls -la /boot/gentoo/bzImage` should show as you
expected, given that hdb2 is mounted as /boot.

HTH!
-- 
Iain Buchanan 

#if _FP_W_TYPE_SIZE < 32
#error "Here's a nickel kid.  Go buy yourself a real computer."
#endif
-- linux/arch/sparc64/double.h

-- 
[EMAIL PROTECTED] mailing list



[gentoo-user] xdm login problems after recent emerge

2008-01-01 Thread Mick
Happy New Year to all!

I find my self in a bit of a pickle after a recent emerge.  When I
enter my username+passwd at the xdm login screen it sort of tries to
load up fluxbox, but within a second or so it returns to the login
screen. I can't see anything worth mentioning in the logs. I have
downgraded baselayout, sysvinit and freetype but the problem remains.
Any ideas? These are the packages emerged recently:

 Mon Dec 31 18:38:51 2007 >>> sys-devel/gcc-config-1.4.0-r4
 Mon Dec 31 18:41:08 2007 >>> dev-lang/spidermonkey-1.7.0
 Mon Dec 31 18:52:59 2007 >>> sys-libs/ncurses-5.6-r2
 Mon Dec 31 18:53:58 2007 >>> sys-kernel/linux-headers-2.6.23-r3
 Mon Dec 31 18:57:40 2007 >>> app-shells/bash-3.2_p17-r1
 Mon Dec 31 18:58:09 2007 >>> sys-apps/sysvinit-2.86-r10
 Mon Dec 31 19:01:55 2007 >>> dev-libs/libcdio-0.78.2-r2
 Mon Dec 31 19:03:17 2007 >>> dev-lang/yasm-0.6.2
 Mon Dec 31 19:04:03 2007 >>> sys-apps/less-416
 Mon Dec 31 19:06:50 2007 >>> media-libs/freetype-2.3.5-r2
 Mon Dec 31 19:08:01 2007 >>> media-libs/x264-svn-20070924
 Mon Dec 31 19:09:43 2007 >>> media-libs/giflib-4.1.6
 Mon Dec 31 19:10:27 2007 >>> app-crypt/johntheripper-1.7.2-r3
 Mon Dec 31 19:11:28 2007 >>> dev-python/imaging-1.1.5
 Mon Dec 31 19:11:55 2007 >>> sys-apps/baselayout-1.12.10-r5
 Mon Dec 31 19:12:53 2007 >>> app-crypt/dirmngr-1.0.1
 Mon Dec 31 19:30:13 2007 >>> media-video/mplayer-1.0_rc2
 Mon Dec 31 19:35:16 2007 >>> net-print/hplip-2.7.10
 Mon Dec 31 19:40:40 2007 >>> dev-lang/ruby-1.8.6_p111


I don't have a problem login in at the console, so this must be
xdm/Xorg related I guess.  As this is the laptop that I take to work
and my holidays end today all suggestions are welcomed!  :)
-- 
Regards,
Mick
-- 
[EMAIL PROTECTED] mailing list



[gentoo-user] Re: Gentoo & GRUB help

2008-01-01 Thread Mick
Happy New Year!

BRM wrote:

> The system is set to boot off of /dev/hdb2 (ext2) and use /dev/hdb1 as
> the root. I believe the boot device is hd1,1 in grub terminology.

Yes.

> The system has 3 hard drives: hda, hdb, and sda; as well as a dvd drive
> (hdc).

Check your /boot/grub/device.map to make sure that devices correspond to the
expected grub nomenclature.  Use  after you run # grub for
root to find out where Grub thinks its root fs resides.

> /dev/hdb2 has the following structure:
>  - list of all my Slackware kernels
>  - gentoo/bzImage
>  - gentoo/bzImage_2-6-23-gentoo-r3
>  - grub/
> 
> Below is my grub.conf (minus comment lines):
> 
> timeout 30
> default 0
> fallback 1
> title Gentoo Linux
> root (hd1,1)
> kernel /gentoo/bzImage root=/dev/hdb1

I assume from what you said above that when you run ls -la /gentoo/bzImage
you can see the kernel image you are trying to boot, right?

> title Slackware Linux
> root (hd1,1)
> kernel /vmlinuz root=/dev/sda1
> 
> title Install GRUB into the hard disk
> root (hd1,1)
> setup (hd1)
> 
> title Change the colors
> color light-green/brown blink-red/blue
> 
> I installed it via:
> 
> # grub
> grub: root (hd1,1)
> grub: setup (hd1)
> grub: exit
> 
> All seems well. It boots and presents the menu, but then can't find the
> kernel when I select "Gentoo Linux" or try to manually run the lines. I
> tried using "find" at the grub command prompt during the boot process,
> but it couldn't find it either. I haven't tried the Slackware kernel
> yet, as I am mostly concerned about the Gentoo kernel.
> 
> Note: I am using LVM2 under this Gentoo install - but not for /boot or
> /.
> 
> What am I missing?

Your system will look at the first device that the BIOS finds for a
bootloader.  That 'should' be /dev/hda, but it could well be /dev/sda
(check device map and also use Grub's tab completion to see what the
BIOS/Grub sees first).  Then install your grub in that first device. 
There's nothing wrong with your Grub installation other than it is in the
second (third?) device and it need to be either chainloaded or directly
booted from the Grub installation in the first device that comes up on boot
up.

HTH
-- 
Regards,
Mick

-- 
[EMAIL PROTECTED] mailing list