Re: [lfs-support] LFS 7.3 - VFS: Cannot open root device "/dev/sda4" or unknown-block(0,0)‏

2013-07-18 Thread William Harrington 


On Jul 18, 2013, at 18:54, Kevin Abraham  wrote:

> What would the right driver be?

Perhaps AHCI?

Sincerely,

William Harrington
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] GPT Partitioned Drive on BIOS Station, Unable to Mount Root

2013-07-18 Thread Aleksandar Kuktin 
One of the great things about hanging around on LFS mail-lists is that
you often get to learn about new hardware (in this case Tyan stuff).
Specifically, about its existance.

>On Fri, 19 Jul 2013 03:13:51 +0200
>Esben Stien  wrote:
> 
> [snip]
> 
> I've confirmed that the kernel works fine as I still have my old LFS
> build on another drive on the same station.

So, let me get this straight. When you put the new kernel into the old
LFS, it boots like a charm but when you put that same kernel into the
new LFS, it fails?

Also, the old LFS is on a normal HDD, and the new LFS is on a SSD,
right?

If yes, then the problem seems to be either triggered by the difference
in the housing drives or by differences in the userland, correct?

Maybe you could try that trick in booting USBs where you configure the
kernel to wait a bit before trying to boot the userland.

> [snip]
> 
> I'm on a Tyan Thunder n3600B (S2927-E) (S2927A2NRF-E) station and
> I've compiled SATA chipset and XFS filesystem support into the kernel:
> 
> CONFIG_SATA_NV=y
> CONFIG_XFS_FS=y
> 
> I'm quite stuck on this one and I'm open to anything. I've sat up the
> last two days/nights trying to figure this one out and I've read the
> whole internet;).
> 
> Any pointers as to what I can try?
> 


-- 
You don't need an AI for a robot uprising.
Humans will do just fine.


signature.asc
Description: PGP signature
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] GPT Partitioned Drive on BIOS Station, Unable to Mount Root

2013-07-18 Thread Esben Stien 
Glendon Blount  writes:

> [..] your grub bios boot partition is over 900mb [..] Did you make a
> separate bios boot partion or did you include it into your boot
> partition?

Yeah, sdf1 is that big, because I had no idea what GPT was until a few
days ago. 

I figured that I wouldn't need a BIOS Boot Partition, if you are
referring to an ESP (EFI System Partition), because I use a BIOS and I
understood it like I didn't need one. It's only on UEFI systems that an
ESP is needed, as far as I understand. 

I made a bios_grub partition on sdf1, so that grub-2 could install its
magic in there. Then I made /boot on sdf2 and / on sdf3. I have swap on
sdf4.

Then I ran grub-install on /dev/sdf which completed successfully. 

-- 
Esben Stien is b0ef@e s  a 
 http://www. s tn m
  irc://irc.  b  -  i  .   e/%23contact
   sip:b0ef@   e e 
   jid:b0ef@n n
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] GPT Partitioned Drive on BIOS Station, Unable to Mount Root

2013-07-18 Thread Esben Stien 
Fernando de Oliveira  writes:

> Is there any chance that you have forgotten:
> 

Thanks, but no, this is included: 

CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y

-- 
Esben Stien is b0ef@e s  a 
 http://www. s tn m
  irc://irc.  b  -  i  .   e/%23contact
   sip:b0ef@   e e 
   jid:b0ef@n n
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] GPT Partitioned Drive on BIOS Station, Unable to Mount Root

2013-07-18 Thread Glendon Blount 
The one thing I noticed was your grub bios boot partition is over 900mb
mine on my arch Linux install is 32kb. Did you make a separate bios boot
partion or did you include it into your boot partition?
On Jul 18, 2013 6:36 PM, "Fernando de Oliveira"  wrote:

>
> - Mensagem original -
> > De: Esben Stien
> > Para: lfs-support
> > Cc:
> > Enviadas: Quinta-feira, 18 de Julho de 2013 22:13
> > Assunto: [lfs-support] GPT Partitioned Drive on BIOS Station,
> Unable to Mount Root
> >
> >
> > I've installed LFS on a GPT SSD on a BIOS station with the help of
> > jhalfs and the kernel, started with grub-2, fails to boot completely as
> > it can't find the root filesystem. The familiar "VFS Unable to mount
> > root fs, Panic".
>
> Is there any chance that you have forgotten:
> <
> http://www.linuxfromscratch.org/lfs/view/development/chapter08/kernel.html
> >
>
> Note
> Due to recent changes in udev, be sure to select:
>
> Device Drivers  --->
>   Generic Driver Options  --->
>  Maintain a devtmpfs filesystem to mount at /dev
> make LANG= LC_ALL= menuconfig
>
> []s,
> Fernando
>
> --
> http://linuxfromscratch.org/mailman/listinfo/lfs-support
> FAQ: http://www.linuxfromscratch.org/lfs/faq.html
> Unsubscribe: See the above information page
>
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] libxslt

2013-07-18 Thread francisco martinez 
Yea, i was doing that, recompiled Python and worked all fine. Thanks a lot
both of you.


2013/7/18 Armin K. 

> On 07/18/2013 10:46 PM, francisco martinez wrote:
> > Hello.
> > My error is
> > make[3]: Entering directory `/xc/proto/libxslt-1.1.28/python'
> > SRCDIR=. /usr/bin/python ./generator.py
> > Traceback (most recent call last):
> >   File "./generator.py", line 923, in 
> > buildStubs()
> >   File "./generator.py", line 405, in buildStubs
> > (parser, target)  = getparser()
> >   File "./generator.py", line 26, in getparser
> > parser = xml.sax.make_parser()
> >   File "/usr/lib/python2.7/xml/sax/__init__.py", line 93, in make_parser
> > raise SAXReaderNotAvailable("No parsers found", None)
> > xml.sax._exceptions.SAXReaderNotAvailable: No parsers found
> > make[3]: *** [gen_prog] Error 1
> > make[3]: Leaving directory `/xc/proto/libxslt-1.1.28/python'
> > make[2]: *** [all-recursive] Error 1
> > make[2]: Leaving directory `/xc/proto/libxslt-1.1.28/python'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory `/xc/proto/libxslt-1.1.28'
> > make: *** [all] Error 2
> >
> >
> >
> >
> > i suspect, it has to do with python,i already installed this package,
> > and also made the tests on it(on python).
> > the dependency libxml2-2.9.1 was also installed.
> > i already tried the archives and google, and couldnt find something
> > specific to my problem, if you can point me in the right direction, or
> > any kind of help, would be great.
> > Thanks in advance.
> >
> >
>
> You didn't had expat installed when you built python2 ... Read the
> instructions and honor recommended deps, they are not recommended
> without a reason.
> --
> http://linuxfromscratch.org/mailman/listinfo/blfs-support
> FAQ: http://www.linuxfromscratch.org/blfs/faq.html
> Unsubscribe: See the above information page
>
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] LFS 7.3 - VFS: Cannot open root device "/dev/sda4" or unknown-block(0,0)‏

2013-07-18 Thread Armin K. 
On 07/19/2013 01:54 AM, Kevin Abraham wrote:
> Hello,
> 
> When I boot my LFS 7.3 system, I get a "VFS: Cannot open root device
> "/dev/sda4" or unknown-block(0,0)" error. I have traced the problem down
> to a driver missing from the kernel, but can't figure out which one. I
> have tried the SATA_NV driver and the SATA_SIL driver but none of those
> are working. What would the right driver be?
> 
> Thanks in advance,
> Kevin
> 
> 

Well, you can post lspci -v output from your host. Also, be sure to
build filesystem driver into kernel, too.
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

[lfs-support] LFS 7.3 - VFS: Cannot open root device "/dev/sda4" or unknown-block(0,0)‏

2013-07-18 Thread Kevin Abraham 
Hello,

When I boot my LFS 7.3 system, I get a "VFS: Cannot open root device 
"/dev/sda4" or unknown-block(0,0)" error. I have traced the problem down to a 
driver missing from the kernel, but can't figure out which one. I have tried 
the SATA_NV driver and the SATA_SIL driver but none of those are working. What 
would the right driver be?

Thanks in advance,
Kevin-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] GPT Partitioned Drive on BIOS Station, Unable to Mount Root

2013-07-18 Thread Fernando de Oliveira 

- Mensagem original -
> De: Esben Stien
> Para: lfs-support
> Cc: 
> Enviadas: Quinta-feira, 18 de Julho de 2013 22:13
> Assunto: [lfs-support] GPT Partitioned Drive on BIOS Station,
    Unable to Mount Root
> 
> 
> I've installed LFS on a GPT SSD on a BIOS station with the help of
> jhalfs and the kernel, started with grub-2, fails to boot completely as
> it can't find the root filesystem. The familiar "VFS Unable to mount
> root fs, Panic".

Is there any chance that you have forgotten:


Note
Due to recent changes in udev, be sure to select:

Device Drivers  --->
  Generic Driver Options  --->
 Maintain a devtmpfs filesystem to mount at /dev
make LANG= LC_ALL= menuconfig

[]s,
Fernando

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

[lfs-support] GPT Partitioned Drive on BIOS Station, Unable to Mount Root

2013-07-18 Thread Esben Stien 

I've installed LFS on a GPT SSD on a BIOS station with the help of
jhalfs and the kernel, started with grub-2, fails to boot completely as
it can't find the root filesystem. The familiar "VFS Unable to mount
root fs, Panic".

I've built LFS since 2003 or was it 2002 and I've seen this message
quite a few times. However this time, I'm unable to get it to boot
anything.

I've confirmed that the kernel works fine as I still have my old LFS
build on another drive on the same station.

I have /boot on sdf2 and / on sdf3

Model: ATA Crucial_CT120M50 (scsi)
Disk /dev/sdf: 120GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start   End SizeFile system Name Flags
 1  1049kB  1000MB  999MB   primary  bios_grub
 2  1000MB  5000MB  3999MB  ext3primary
 3  5000MB  118GB   113GB   xfs primary  boot
 4  118GB   120GB   2034MB  linux-swap(v1)  primary

/dev/sdf2: UUID="a6960224-5c35-43e9-920b-7d9e1225ab26" SEC_TYPE="ext2" 
TYPE="ext3" PARTLABEL="primary" PARTUUID="96326d8d-fe5e-4c2d-acd5-6b9380441476" 
/dev/sdf3: UUID="7440b882-aecb-4e4a-8ecb-24d7a31dc9f9" TYPE="xfs" 
PARTLABEL="primary" PARTUUID="6335e500-106b-4a33-9e54-709a33681ba6" 
/dev/sdf4: UUID="8128605c-690e-49d3-bbaa-5214f21c8c89" TYPE="swap" 
PARTLABEL="primary" PARTUUID="a9e95be4-db76-4c4d-9f02-5b4f22c796b1" 
/dev/sdf1: PARTLABEL="primary" PARTUUID="bb8dc183-06bc-4500-a205-afd753de1802"

When I boot the SSD, I set this drive in the BIOS as the first drive, so
as to be able to boot from it. I refer to the drive as hd0 in grub
console. It is still however referred to sdf when linux boots. I've
confirmed this in initrd.

linux (hd0,gpt2)/linux-3.10 root=/dev/sdf3

..and I've also tried: 

linux (hd0,gpt2)/linux-3.10 root=PARTUUID=6335e500-106b-4a33-9e54-709a33681ba6

I've also tried initrd, which dumps me right in its simple shell. I'm
there able to mount /dev/sdf3 to /.root/, but not successful in running
"switch_root .root /sbin/init". I can post all that is happening in
initrd, but I think first I'll try to get this out and see if there's
anything I forgot. I've expected LFS to be bootable after running jhalfs
and fixing fstab.

# Begin /etc/fstab
#UUID=7440b882-aecb-4e4a-8ecb-24d7a31dc9f9  / xfs defaults   00 
#UUID=8128605c-690e-49d3-bbaa-5214f21c8c89  swap swap   pri=10 0
/dev/sdf3   /   xfs defaults0   0
/dev/sdf4   swapswappri=1   0   0
proc   /procproc nosuid,noexec,nodev 0 0
sysfs  /sys sysfsnosuid,noexec,nodev 0 0
devpts /dev/pts devpts   gid=5,mode=620  0 0
tmpfs  /run tmpfsdefaults0 0
devtmpfs   /dev devtmpfs mode=0755,nosuid0 0
#UUID=a6960224-5c35-43e9-920b-7d9e1225ab26  /boot   ext3
defaults0   0
/dev/sdf2   /boot   ext3defaults0   0
# End /etc/fstab

I'm on a Tyan Thunder n3600B (S2927-E) (S2927A2NRF-E) station and
I've compiled SATA chipset and XFS filesystem support into the kernel:

CONFIG_SATA_NV=y
CONFIG_XFS_FS=y

I'm quite stuck on this one and I'm open to anything. I've sat up the
last two days/nights trying to figure this one out and I've read the
whole internet;).

Any pointers as to what I can try?

-- 
Esben Stien is b0ef@e s  a 
 http://www. s tn m
  irc://irc.  b  -  i  .   e/%23contact
   sip:b0ef@   e e 
   jid:b0ef@n n
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] Missing the good, old RTC

2013-07-18 Thread alex lupu 
Dear Mr. Radley,

> The question: Will there be any practical difference for me now
considering
> this comment in Help for CONFIG_RTC?...

>  If you run Linux on a multiprocessor machine and said Y to
> "Symmetric Multi Processing" above, you should say Y here to read
>  and set the RTC in an SMP compatible fashion.
> The comment: Maybe the kernel folks should edit the Help text for
> CONFIG_SMP...
 > People using multiprocessor machines who say Y here should also say
 > Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
 > Management" code will be disabled if you say Y here.
>
> ...since that option is no longer always possible when CONFIG_RTC_CLASS is
> disabled.

We have received your E-mail and are in the process of redirecting it.
Your comments and questions we'll probably be reviewed by our
Help Analysis Department in (the nearest) due time.

If any (or all) of your suggestions are deemed of value they will most
likely be
included in a future release of the kernel.
Please note that based on our preliminary present schedule, we see a
possible
opening for 3.14.7-rc5 or thereafter.

We would like to thank you for your interest in our products and are
looking forward
to hearing from you in the future.

mit Hochachtungsvoll,
Your Friendly Kernel Team


On Thu, Jul 18, 2013 at 11:00 AM, Arthur Radley <
misterarthurrad...@gmail.com> wrote:

> Markku Pesonen  gmail.com> writes:
>
> >
> > alex lupu wrote:
> > > BTW, what's a "Generic RTC class"?
> > >   Would save me some research time ...
> >
> > Generic RTC class supports many different RTC chips found on all kinds
> > of hardware, unlike the legacy PC RTC driver.
> >
> > I assume you are using "make menuconfig". Go to Device Drivers and
> > select at least these:
> > [*] Real Time Clock  --->   (CONFIG_RTC_CLASS)
> >[*] /sys/class/rtc/rtcN (sysfs)   (CONFIG_RTC_INTF_SYSFS)
> >[*] /proc/driver/rtc (procfs for rtcN)   (CONFIG_RTC_INTF_PROC)
> >[*] /dev/rtcN (character devices)   (CONFIG_RTC_INTF_DEV)
> >[*] PC-style 'CMOS'   (CONFIG_RTC_DRV_CMOS)
> >
>
> I, too, have been enabling CONFIG_RTC "Enhanced Real Time Clock Support
> (legacy PC RTC driver)" and today enabled CONFIG_RTC_CLASS "Real Time
> Clock" as suggested here (thanks, BTW). But I still have a question and a
> comment...
>
> The question: Will there be any practical difference for me now considering
> this comment in Help for CONFIG_RTC?...
>
>   If you run Linux on a multiprocessor machine and said Y to
>   "Symmetric Multi Processing" above, you should say Y here to read
>   and set the RTC in an SMP compatible fashion.
>
> The comment: Maybe the kernel folks should edit the Help text for
> CONFIG_SMP...
>
>   People using multiprocessor machines who say Y here should also say
>   Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
>   Management" code will be disabled if you say Y here.
>
> ...since that option is no longer always possible when CONFIG_RTC_CLASS is
> disabled.
>
> Arthur
>
> --
> http://linuxfromscratch.org/mailman/listinfo/lfs-support
> FAQ: http://www.linuxfromscratch.org/lfs/faq.html
> Unsubscribe: See the above information page
>
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] Missing the good, old RTC

2013-07-18 Thread Markku Pesonen 
Arthur Radley wrote:
> I, too, have been enabling CONFIG_RTC "Enhanced Real Time Clock Support 
> (legacy PC RTC driver)" and today enabled CONFIG_RTC_CLASS "Real Time 
> Clock" as suggested here (thanks, BTW). But I still have a question and a 
> comment...
> 
> The question: Will there be any practical difference for me now considering 
> this comment in Help for CONFIG_RTC?...
> 
>   If you run Linux on a multiprocessor machine and said Y to
>   "Symmetric Multi Processing" above, you should say Y here to read
>   and set the RTC in an SMP compatible fashion.
> 
> The comment: Maybe the kernel folks should edit the Help text for 
> CONFIG_SMP...
> 
>   People using multiprocessor machines who say Y here should also say
>   Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
>   Management" code will be disabled if you say Y here.
> 
> ...since that option is no longer always possible when CONFIG_RTC_CLASS is
> disabled.

I think the kernel maintainers just forgot to update the help text for
CONFIG_SMP. There should not be any problems using CONFIG_SMP with
CONFIG_RTC_CLASS.
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] Missing the good, old RTC

2013-07-18 Thread Arthur Radley 
Markku Pesonen  gmail.com> writes:

> 
> alex lupu wrote:
> > BTW, what's a "Generic RTC class"?
> >   Would save me some research time ...
> 
> Generic RTC class supports many different RTC chips found on all kinds
> of hardware, unlike the legacy PC RTC driver.
> 
> I assume you are using "make menuconfig". Go to Device Drivers and
> select at least these:
> [*] Real Time Clock  --->   (CONFIG_RTC_CLASS)
>[*] /sys/class/rtc/rtcN (sysfs)   (CONFIG_RTC_INTF_SYSFS)
>[*] /proc/driver/rtc (procfs for rtcN)   (CONFIG_RTC_INTF_PROC)
>[*] /dev/rtcN (character devices)   (CONFIG_RTC_INTF_DEV)
>[*] PC-style 'CMOS'   (CONFIG_RTC_DRV_CMOS)
> 

I, too, have been enabling CONFIG_RTC "Enhanced Real Time Clock Support 
(legacy PC RTC driver)" and today enabled CONFIG_RTC_CLASS "Real Time 
Clock" as suggested here (thanks, BTW). But I still have a question and a 
comment...

The question: Will there be any practical difference for me now considering 
this comment in Help for CONFIG_RTC?...

  If you run Linux on a multiprocessor machine and said Y to
  "Symmetric Multi Processing" above, you should say Y here to read
  and set the RTC in an SMP compatible fashion.

The comment: Maybe the kernel folks should edit the Help text for 
CONFIG_SMP...

  People using multiprocessor machines who say Y here should also say
  Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
  Management" code will be disabled if you say Y here.

...since that option is no longer always possible when CONFIG_RTC_CLASS is
disabled.

Arthur

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] Can not start system log and kernel log daemons

2013-07-18 Thread Niels Terp 
Niels Terp wrote:

> I have just finished building LFS SVN-20130711. During boot I get:

> Starting system log daemon   [FAIL]
> Starting kernel log daemon[FAIL]
> and those two logs are empty.

Did you build Sysklogd?  Do /sbin/syslogd and /sbin/klogd exist?

Does /etc/syslog.conf exist?

   -- Bruce

-- 
Hi Bruce,

Just a few minutes ago I got it working. The Sysklogd was at fault, I
recompiled it, and everything worked !

Thanks for your input anyway !

Niels

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] Can not start system log and kernel log daemons

2013-07-18 Thread Bruce Dubbs 
Niels Terp wrote:

> I have just finished building LFS SVN-20130711. During boot I get:

> Starting system log daemon   [FAIL]
> Starting kernel log daemon[FAIL]
> and those two logs are empty.

Did you build Sysklogd?  Do /sbin/syslogd and /sbin/klogd exist?

Does /etc/syslog.conf exist?

   -- Bruce

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

[lfs-support] Can not start system log and kernel log daemons

2013-07-18 Thread Niels Terp 
Hi there,

 

I have just finished building LFS SVN-20130711. During boot I get:

 

Starting system log daemon   [FAIL]

Starting kernel log daemon[FAIL]

 

and those two logs are empty.

 

Anybody has a hint ?

 

Niels

 

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page