|
From: Diego T. <dt...@co...> - 2004-03-13 13:33:17
|
yesterday i updated from the cvs and downloaded all the new files from the ftp, built with a small config (2.4 kernel, via-c3 cpu) and the resulting iso doesn't boot from the usual usb flashdisk. did someone made any changes to the bootup process? currently, the boot process stops with vmlinuz......(lots of dots displayed). any idea/suggestion? -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dtorres at anthalia dot org - Madrid / España |
|
From: Roland P. <pa...@ta...> - 2004-03-13 14:03:37
|
On Saturday 13 March 2004 14:25, Diego Torres wrote: > yesterday i updated from the cvs and downloaded all the new files from the > ftp, built with a small config (2.4 kernel, via-c3 cpu) and the resulting > iso doesn't boot from the usual usb flashdisk. > > did someone made any changes to the bootup process? > > currently, the boot process stops with vmlinuz......(lots of dots > displayed). > > any idea/suggestion? which was the last version that worked for you? In the past, an error like this one was usually caused by either ACPI (IRQ stuff) or FB errors... I don't know what kind of cpu the via-c3 exactly is, perhaps it's because the Processor type is now 586 per default? I'd start by disabling FB and booting with acpi=off And try booting with a CD or in vmware (to verify it's not the iso image) Roland -- ICQ UIN 49339118 Linux Counter #88774 GPG-Key 1024D/59C6AFA6 2003-02-07 Roland Pabel <ro...@pa...> |
|
From: Diego T. <dt...@co...> - 2004-03-13 15:32:05
|
On Sat, Mar 13, 2004 at 03:03:19PM +0100, Roland Pabel wrote: > > any idea/suggestion? > which was the last version that worked for you? In the past, an error like devil-linux-1.1.1-2003-12-02-i686 this was my last working version (custom compiled) > this one was usually caused by either ACPI (IRQ stuff) or FB errors... > I don't know what kind of cpu the via-c3 exactly is, perhaps it's because the > Processor type is now 586 per default? i'm changing it to 686 via the config option. > I'd start by disabling FB and booting with acpi=off i'll try to append that in the boot process an see... thxs > And try booting with a CD or in vmware (to verify it's not the iso image) i believe that it is a working iso, but i'll try to burn a cd to check (right now i can't install vmware). -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dtorres at anthalia dot org - Madrid / España |
|
From: Diego T. <dt...@co...> - 2004-03-14 14:19:43
|
On Sat, Mar 13, 2004 at 03:03:19PM +0100, Roland Pabel wrote: > I'd start by disabling FB and booting with acpi=off acpi=off doesn't solve the problem. the loading process ends with a "Loading vmlinuz......(lots of dots)" -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dtorres at anthalia dot org - Madrid / España |
|
From: Heiko Z. <he...@zu...> - 2004-03-13 15:02:09
|
Diego Torres wrote: > yesterday i updated from the cvs and downloaded all the new files from the ftp, built with a small config (2.4 kernel, via-c3 cpu) and the resulting iso doesn't boot from the usual usb flashdisk. > > did someone made any changes to the bootup process? > > currently, the boot process stops with vmlinuz......(lots of dots displayed). > > any idea/suggestion? > Yes there were some changes to the isolinux boot menu. The error must happen when the isolinux.cfg gets "converted" to syslinux.cfg in the install-on-usb script. I don't have a latest build available at the moment, so I can't test it. Heiko |
|
From: Diego T. <dt...@co...> - 2004-03-13 15:29:41
|
On Sat, Mar 13, 2004 at 09:57:54AM -0500, Heiko Zuerker wrote: > Yes there were some changes to the isolinux boot menu. > The error must happen when the isolinux.cfg gets "converted" to > syslinux.cfg in the install-on-usb script. i'll look at it... but i was expecting some error like "couldn't mount root" or something like that... but i have a backup of my last working configuration, so i will check. about the script with md5sum, should be change to the short-command version an abort on mismatch? -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dtorres at anthalia dot org - Madrid / España |
|
From: Heiko Z. <he...@zu...> - 2004-03-13 15:56:18
|
Diego Torres wrote: > On Sat, Mar 13, 2004 at 09:57:54AM -0500, Heiko Zuerker wrote: > > >>Yes there were some changes to the isolinux boot menu. >>The error must happen when the isolinux.cfg gets "converted" to >>syslinux.cfg in the install-on-usb script. > > > i'll look at it... but i was expecting some error like "couldn't mount root" or something like that... but i have a backup of my last working configuration, so i will check. > > about the script with md5sum, should be change to the short-command version an abort on mismatch? > It simply should list all the packages which don't match the calculated checksum. Heiko |
|
From: Diego T. <dt...@co...> - 2004-03-14 03:30:07
|
On Sat, Mar 13, 2004 at 10:52:49AM -0500, Heiko Zuerker wrote: > > > >i'll look at it... but i was expecting some error like "couldn't mount > >root" or something like that... but i have a backup of my last working > >configuration, so i will check. is there an easy way to make changes on the .config file from the kernel, and build and iso without recompiling everthing? maybe there is some weird problem with the 2.4.25 kernel and a compiled driver on my epia board.... ¿? -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dtorres at anthalia dot org - Madrid / España |
|
From: Heiko Z. <he...@zu...> - 2004-03-14 15:56:17
|
Diego Torres wrote: > On Sat, Mar 13, 2004 at 10:52:49AM -0500, Heiko Zuerker wrote: > >>>i'll look at it... but i was expecting some error like "couldn't mount >>>root" or something like that... but i have a backup of my last working >>>configuration, so i will check. > > > > is there an easy way to make changes on the .config file from the kernel, and > build and iso without recompiling everthing? maybe there is some weird problem > with the 2.4.25 kernel and a compiled driver on my epia board.... ¿? > Just run scripts/build.sh build opt=linux after that run a "make clean install iso" You need to de-select pcmcia support, because it doesn't like having the kernel re-compiled. Heiko |
|
From: Diego T. <dt...@co...> - 2004-03-14 16:10:50
|
On Sat, Mar 13, 2004 at 10:52:49AM -0500, Heiko Zuerker wrote: problem solved! :) heiko, you're guilty :P http://cvs.sourceforge.net/viewcvs.py/devil-linux/build/scripts/config/config_linux?r1=1.65&r2=1.66 in this changeset, you made: <*> BIOS Enhanced Disk Drive calls determine boot disk (EXPERIMENTAL) CONFIG_EDD=y Disabling it makes my epia board boot without problems. Should i change it in the /scripts/config/linux_config file, or some other app needs it? -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dtorres at anthalia dot org - Madrid / España |
|
From: Heiko Z. <he...@zu...> - 2004-03-14 16:41:21
|
Diego Torres wrote: > On Sat, Mar 13, 2004 at 10:52:49AM -0500, Heiko Zuerker wrote: > > problem solved! :) > > heiko, you're guilty :P shit ;-) > http://cvs.sourceforge.net/viewcvs.py/devil-linux/build/scripts/config/config_linux?r1=1.65&r2=1.66 > > in this changeset, you made: > > <*> BIOS Enhanced Disk Drive calls determine boot disk (EXPERIMENTAL) > CONFIG_EDD=y > > Disabling it makes my epia board boot without problems. Cool. > Should i change it in the /scripts/config/linux_config file, or some other app needs it? Yes change it. Heiko |
|
From: Diego T. <dt...@co...> - 2004-03-14 03:29:50
|
On Sat, Mar 13, 2004 at 09:57:54AM -0500, Heiko Zuerker wrote: > > Yes there were some changes to the isolinux boot menu. > The error must happen when the isolinux.cfg gets "converted" to > syslinux.cfg in the install-on-usb script. that conversion was done on november, while my last booting iso is from december. there has been some changes on the build-iso script, but none of them looks guilty (addition of ext2, branches for 2.4/2.6) btw, memtest boots correctly. i'm lost, help! :) -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dtorres at anthalia dot org - Madrid / España |