Messages in this thread | | | From | nathan.zook@amd ... | Subject | RE: 2.3.34-pre1: chopped boot command line problem | Date | Fri, 17 Dec 1999 09:24:45 -0600 |
| |
First, this is not our problem. The buffer we are working on holds 256 bytes, so this looks like a SEP.
Does the ramdisk work? If so, it might just be a reporting issue. If not, main.c says something about a function call to process the "non-memory" command line options. I would look there.
Nathan
-----Original Message----- From: Tigran Aivazian [mailto:tigran@sco.COM] Sent: Friday, December 17, 1999 3:46 AM To: Zook, Nathan Cc: linux-kernel@vger.rutgers.edu Subject: 2.3.34-pre1: chopped boot command line problem
On Thu, 16 Dec 1999 nathan.zook@amd.com wrote: > Oh, the long command line problem is getting a partial fix, too. For our > edification, could you send an actual command line that is getting chopped? > It will let me know if my fix sufficies, or if a deeper fix is needed.
# wc /proc/cmdline 1 7 79 /proc/cmdline # cat /proc/cmdline auto BOOT_IMAGE=2333 ro root=803 console=ttyS1,9600 console=tty0 ramdisk_start # grep append /etc/lilo.conf append="console=ttyS1,9600 console=tty0 ramdisk_start=0x1000 ramdisk_prompt=0 ramdisk_load=1 ramdisk_blabla=0123456789"
(obviously ramdisk_blabla is not a real parameter ;)
Regards, ------ Tigran A. Aivazian | http://www.sco.com Escalations Research Group | tel: +44-(0)1923-813796 Santa Cruz Operation Ltd | http://www.ocston.org/~tigran
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |