On Wednesday 07 Mar 2007, Michal Piotrowski wrote:For the record, I used console=lp0 quite recently (stock 2.6.19 according to the printout, running on i386) [to find out what was causing a panic that immediately vanished off the top of the screen because of "atkbd.c: Spurious ACK..."s from the flashing kb LEDs] and it worked just fine. The parport-related lines went: lp: driver loaded but no devices found parport: PnPBIOS parport detected. parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE,EPP] parport0: Printer, EPSON Stylus COLOR 600 lp0: using parport0 (interrupt-driven) lp0: console ready ... then the kernel continued booting until the panic occurred (it was a silly storage-related misconfig on my part). If anyone wants me to try anything (newer kernel or different parport-related BIOS settings, perhaps, to see if I can duplicate the problem?) and report back, let me know. Stephen -
| Hiten Pandya | Re: up? (emacs docbook xml ide) |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Roland Dreier | Re: Integration of SCST in the mainstream Linux kernel |
| Florian Schmidt | blacklist kernel boot option |
git: | |
| Linus Torvalds | Re: iptables very slow after commit 784544739a25c30637397ace5489eeb6e15d7d49 |
| Arjan van de Ven | Re: [GIT]: Networking |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
