Re: BUG: Problem while booting Debian with LVDS connector instead of VGA
Hello, I do not if it is related but just in case. With some MacMini, at least old ones, this issue exists as well: this is not a linux issue but a bootcamp issue. hth, Jerome User Debian wrote: Hello, I have a problem that I meet each time I boot Linux on an embedded computer. Configuration: Embedded PC : ECM-LX800 Screen: LVDS (and not VGA) Linux: Debian ETCH version 2.6.18-6-686 The problem comes after GRUB gives the instruction on which partition to boot, BUT before that Linux kernel is loaded. Noticed facts: 1- in short-cutting the VGA connector (i.e. pin 5 and 12 strapped together), which simulates the presence of a VGA display attached to the PC, Linux boots normally. The video signal is indeed sent to the LVDS output. 2- Linux installation was proceeded with success, but with the VGA connector connected to an external display as described in item 1. 3- When the VGA connector is free from any connector or from any strap between pins 5 and 12, after GRUB has started: the display becomes then black. Linux kernel is not loaded. Question: Is there a configuration file to modify before the kernel is loaded to tell Linux not to take into account the VGA connector, but instead to send straight the video signal on the LVDS output, and then to boot normally ? Many thanks in advance, Best regards, Eric -- Jerome BENOIT jgmbenoit_at_mailsnare_dot_net -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RE: A problem with booting
From: Mohammed ElGhwell, Sent: Wednesday, February 26, 2003 3:10 AM [snip]... Now I have a problem booting the system. It stops telling 0Kernel panic: Aieee, Killing Interrupt handler ... I tried even to re-install it but it stops with the same message. So, will you please tell me is it because of the hardware or what? I think we will all need to see more output before we can say. Are you compiling your own kernel(1)? If so, you have likely misconfigured something essential. (I have made my hard drive only loadable as a module, but modules aren't available the first time a booting system needs to access the hard drive!) What are you installing (Woody 3.0r0 from CD?) What install option did you choose (install or install24)? If this computer works with other operating systems, it's probably not the hardware :) good luck -- This message is intended only for the personal and confidential use of the designated recipient(s) named above. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Help: problem with booting from HD
In article [EMAIL PROTECTED] you wrote: Thank you for the suggestion. this is what I got so far. I repartitioned the disk with a 500mb primary partition for DOS (06) (some of my pc friends insisted I put DOS as the first one :-), forllowed with two 300mb primary linux partitions, and a 64mb logical linux swap, and ... image=/vmlinuz /vmlinuz points at /boot/vmlinuz-2.0.27, which is there. Where is /boot? The kernel image (and, I think, the LILO map file, /boot/map) usually needs to be in the first 504 Mb for the BIOS to be able to find it. Try moving your kernel image and /boot/map to a directory on your DOS partition and rerunning LILO. For example (assuming /dos is your mounted DOS partition): mkdir /dos/boot.lnx cp /vmlinuz /dos/boot.lnx/vmlinuz mv /vmlinuz /vmlinuz.backup ln -s /dos/boot.lnx/vmlinuz /vmlinuz cp /boot/map /dos/boot.lnx/map mv /boot/map /boot/map.backup ln -s /dos/boot.lnx/map /boot/map lilo (I hope LILO didn't need anything else than the kernel image and /boot/map in the first 504 Mb. Someone reply to this and tell us? :)) Also I was trying to use dselect to do the install from Yggdrasil Winter 97 CD collection's Debian 1.1 i386 distribution. dselect asked me to enter the block device name what I suppose to enter. If it asked you that after you chose cdrom as the installation method, I think it's asking for the device name of the CD-ROM drive (/dev/sonycd or whatever it is)... -- -=- Rjs -=- [EMAIL PROTECTED], [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Help: problem with booting from HD
In article [EMAIL PROTECTED], R [EMAIL PROTECTED] wrote: LILO Loading Linux Uncompressing Linux... crc error System halted Apparently, LILO was installed correctly, and accessed the /vmlinuz file without (disk i/o) errors. It seems, though, that the correct data wasn't loaded, which could mean a disk geometry problem (in fact, that's the only thing I can think of). I asked you this before: do you have LBA mode or Large mode turned on in the BIOS settings for your harddisk? How many cylinders does it say your HD has? If this number is bigger than 1024, you're in trouble. If either Large or LBA mode is on, try the other one (and prepare to reinstall!). (The BC manual explains all this in the section on Cylinder-Head-Sector translation). If you have to reinstall, hold off on W95 and try Linux first; W95 will overwrite your MBR, but BC is easy to reinstall. Your lilo.conf looks OK to me - and from the above messages, LILO itself appears to be working fine (it's the kernel uncompression code that complains). Gertjan. -- Gertjan Klein [EMAIL PROTECTED] The Boot Control home page: http://www.xs4all.nl/~gklein/bcpage.html -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Help: problem with booting from HD
Thank you for the suggestion. this is what I got so far. I repartitioned
the disk with a 500mb primary partition for DOS (06) (some of my pc
friends insisted I put DOS as the first one :-), forllowed with
two 300mb primary linux partitions, and a 64mb logical linux swap, and
3 or 4 logical partitions. i installed Win95 first. ( after all the time
wasted, I finally figured out Win95 install chews up the MBR), and then
installed BC (bc /i 3), which worked great. I could select different
boot partition without problem.
Then I installed Linux from 6 floppies into the 2nd partition, and make
the hard disk bootable (I suppose that made LILO installed onto the 2nd
partiton) but didn't touch the MBR. When I restart, first I got to see
the BC, and select the Debian (2nd) partition, and saw LILO Loading Linux
Uncompressing Linux...
crc error
System halted
and it just died there.
btw, can someone explain to me this error. I am really a newbie.
I could boot from the custom boot floopy without problem.
here is the /etc/lilo.conf I can't think of a way to attach the file, so
I am typing it in.
--
boot=/dev/hda2
root=/dev/hda2
compact
install=/boot/boot.b
map=/boot/map
vga=normal
delay=20
image=/vmlinuz
label=Linux
read-only
--
/vmlinuz points at /boot/vmlinuz-2.0.27, which is there.
Also I was trying to use dselect to do the install from Yggdrasil Winter 97
CD collection's Debian 1.1 i386 distribution. dselect asked me to enter
the block device name what I suppose to enter.
also, I read some where that i can mount the CD with command like
mount -r -t iso9660 /dev/sonycd_31a /mnt
but sonycd_31a is not there. Is there any other device I can use?
I will probably have a lot more questions to come :-)
please also cc the reply to me. thank you.
--
Ray Zhang ~{UESjLo~} [EMAIL PROTECTED] http://www.cnd.org/HYPLAN/ray/
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Help: problem with booting from HD
R [EMAIL PROTECTED] wrote: i made four primary partition (500mb for linux native, 500mb for linux native, 64mb for linux swap, and 900somethinb mb for DOS-32 bit) and marked all but the linux swap as bootable. Install went thru without problem. This is a serious error: only _one_ partition may be marked bootable. If cfdisk let you do this, report this as an error to it's author. I doubt if LILO cares very much, but W95 would probably choke, and anyway it's against the specifications. Your best bet is to mark the W95 partition as bootable, and the others not. Just to make sure: you _did_ turn on Large mode (or LBA mode) in your BIOS setup of your harddisk, didn't you? Both LILO and W95 need to use BIOS to load themselves, and using BIOS you can't access cylinders greater than 1024. The above modes fix this problems, and Linux can handle them in it's own drivers as well. Now the problem is I can't boot from the hard drive. I can boot from the custom boot floopy without problem, and log in as root, etc, and /dev/hda is already mounted at that point. I did du and see that the install used about 15MB, which i assume is correct. if i do shutdown, and reset the pc or turn off and back on the pc, it will produce various kinds of errors. most of the time it will get as far as lilo, uncompress linux and give me a crc error -- system halt and at that point I can't even alt-ctrl-del. Boot from floppy again, go to the mounted harddisk, and check /etc/lilo.conf. (If you can't fix the problems, include this file in your next post). If it is ok, rerun LILO thus (assuming your /dev/hda1 is mounted on /mnt): lilo -C /mnt/etc/lilo.conf (or, if lilo isn't present on your boot floppy, /mnt/sbin/lilo -C /mnt/etc/lilo.conf). Your /etc/lilo.conf should look something like this: boot=/dev/hda root=/dev/hda1 delay=50 image=/vmlinuz label=Linux read-only other=/dev/hda4 label=W95 table=/dev/hda The image= should of course point at your kernel. Note that the W95 installation program will overwrite the MBR that LILO installs, so after installing W95 you'll have to boot from floppy again and rerun LILO. You may also want to try Boot Control (see address in my sig). It comes with documentation that describes the boot process a bit better. You'd still need LILO, but you could then install it to the Linux partition's boot sector (i.e., change the above boot=/dev/hda to boot=/dev/hda1). Gertjan. -- Gertjan Klein [EMAIL PROTECTED] The Boot Control home page: http://www.xs4all.nl/~gklein/bcpage.html -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] From miss Received: from mongo.pixar.com (138.72.50.60) by master.debian.org with SMTP; 8 Jan 1997 16:14:23 - Received: (qmail 15372 invoked from network); 8 Jan 1997 15:22:12 - Received: from primer.i-connect.net (HELO master.debian.org) ([EMAIL PROTECTED]) by mongo.pixar.com with SMTP; 8 Jan 1997 15:22:12 - Message-Id: [EMAIL PROTECTED] Date:Wed, 8 Jan 1997 10:23:05 -0500 From: Ami Ganguli [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Organization: Ganguli Consulting Inc. X-Sender: Ami Ganguli [EMAIL PROTECTED] X-Mailer: Mozilla 4.0b1 (Win95; I) MIME-Version: 1.0 To: [EMAIL PROTECTED] CC: Martin Konold [EMAIL PROTECTED], Ben Gertzfield [EMAIL PROTECTED], Debian-Users debian-user@lists.debian.org Subject: Re: Maintaining multiple Debian boxes X-Priority: Normal References: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Resent-Message-ID: gtZ513.0.0x.vkxqo@master.debian.org Resent-From: debian-user@lists.debian.org Resent-Reply-To: debian-user@lists.debian.org X-Mailing-List: debian-user@lists.debian.org archive/latest/2840 X-Loop: debian-user@lists.debian.org Precedence: list Priority: non-urgent Importance: low Resent-Sender: [EMAIL PROTECTED] Has anybody used GNU cfengine? I don't really know what it's capable of, but it's a free part of Debian. I was considering using it myself, but I haven't had time to investigate it properly. ... Ami. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
