[Kernel-packages] [Bug 2038759] Re: ubuntu does not mount usb disks
The failure is strange, since it initially affected USB ports 3 and 2. Several hours later, when I turned the machine back on, it recognized a USB memory in a USB 2 port and subsequently recognized a 500 GB HDD in a USB port 3. When I disconnected the HDD disk and reconnected a similar one into USB port 3, the system does not recognize it, the lights on the disk turn on but with the lsusb instruction it does not appear; Next I mounted the 15 GB USB memory again in USB port 2, and it was recognized, then the 500 GB HDD disk that was connected was also recognized and I was able to make a backup of 4 internal HDD disks, which are mounted automatically when turning on the computer. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038759 Title: ubuntu does not mount usb disks Status in linux package in Ubuntu: Confirmed Bug description: A week ago this problem appeared and was corrected by changing the cat file /sys/module/usbcore/parameters/autosuspend from 2 to -1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-86-generic 5.15.0-86.96 ProcVersionSignature: Ubuntu 5.15.0-86.96-generic 5.15.122 Uname: Linux 5.15.0-86-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Oct 8 08:15:59 2023 HibernationDevice: RESUME=UUID=b5cba8c3-2b5b-4e92-8409-cb3f5249bdc5 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2021-05-23 (867 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: MSI MS-7978 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-86-generic root=UUID=8e20c169-8bb1-4137-9a73-42655ef53e43 ro acpi_enforce_resources=lax quiet libata.noacpi=1 quiet splash usbcore.autosuspend=-1 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-86-generic N/A linux-backports-modules-5.15.0-86-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.19 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 08:16:20.065: The udisks-daemon is running (name-owner :1.6). UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.G0 dmi.board.asset.tag: Default string dmi.board.name: B150A GAMING PRO (MS-7978) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.G0:bd07/04/2018:br5.12:svnMSI:pnMS-7978:pvr1.0:rvnMSI:rnB150AGAMINGPRO(MS-7978):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7978 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038759] [NEW] ubuntu does not mount usb disks
Public bug reported: A week ago this problem appeared and was corrected by changing the cat file /sys/module/usbcore/parameters/autosuspend from 2 to -1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-86-generic 5.15.0-86.96 ProcVersionSignature: Ubuntu 5.15.0-86.96-generic 5.15.122 Uname: Linux 5.15.0-86-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Oct 8 08:15:59 2023 HibernationDevice: RESUME=UUID=b5cba8c3-2b5b-4e92-8409-cb3f5249bdc5 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2021-05-23 (867 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: MSI MS-7978 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-86-generic root=UUID=8e20c169-8bb1-4137-9a73-42655ef53e43 ro acpi_enforce_resources=lax quiet libata.noacpi=1 quiet splash usbcore.autosuspend=-1 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-86-generic N/A linux-backports-modules-5.15.0-86-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.19 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 08:16:20.065: The udisks-daemon is running (name-owner :1.6). UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.G0 dmi.board.asset.tag: Default string dmi.board.name: B150A GAMING PRO (MS-7978) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.G0:bd07/04/2018:br5.12:svnMSI:pnMS-7978:pvr1.0:rvnMSI:rnB150AGAMINGPRO(MS-7978):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7978 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038759 Title: ubuntu does not mount usb disks Status in linux package in Ubuntu: Confirmed Bug description: A week ago this problem appeared and was corrected by changing the cat file /sys/module/usbcore/parameters/autosuspend from 2 to -1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-86-generic 5.15.0-86.96 ProcVersionSignature: Ubuntu 5.15.0-86.96-generic 5.15.122 Uname: Linux 5.15.0-86-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Oct 8 08:15:59 2023 HibernationDevice: RESUME=UUID=b5cba8c3-2b5b-4e92-8409-cb3f5249bdc5 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2021-05-23 (867 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: MSI MS-7978 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-86-generic root=UUID=8e20c169-8bb1-4137-9a73-42655ef53e43 ro acpi_enforce_resources=lax quiet libata.noacpi=1 quiet splash usbcore.autosuspend=-1 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-86-generic N/A linux-backports-modules-5.15.0-86-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.19 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 08:16:20.065: The udisks-daemon is running (name-owner :1.6). UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.G0 dmi.board.asset.tag: Default string dmi.board.name: B150A GAMING PRO (MS-7978) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor:
[Kernel-packages] [Bug 1637031] Re: In cold startup there is dark/blank screen
Every body can read the complete information that boot-repair gave me in: http://paste.ubuntu.com/23463038/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1637031 Title: In cold startup there is dark/blank screen Status in linux package in Ubuntu: Invalid Bug description: When I startup my computer, I can see very fast screen given any information. When cold startup process finish the screen is dark, usb mouse light is on, keyboard light is on, but the computer does not accept ctrl+alt+del and I must reboot with reset button on computer case. Several seconds latter, the screen displays such as hard drives, one ssd, are mounted and then the system information appears until the gnome desktop. This problem always appears in the cold start. I changed CR2032 motherboard battery and the problems continues. This problem first appeared in the update and upgrade kernel and grub cat /proc/version_signature Ubuntu 3.13.0-101.148-lowlatency 3.13.11-ckt39 sudo lspci -vnvn [sudo] password for hugo: 00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller [8086:29c0] (rev 02) Subsystem: Gigabyte Technology Co., Ltd Device [1458:5000] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:01.0 PCI bridge [0604]: Intel Corporation 82G33/G31/P35/P31 Express PCI Express Root Port [8086:29c1] (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [88] Subsystem: Gigabyte Technology Co., Ltd Device [1458:5000] Capabilities: [80] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0300c Data: 4191 Capabilities: [a0] Express (v1) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #2, Speed 2.5GT/s, Width x16, ASPM L0s, Exit Latency L0s <256ns, L1 <64us ClockPM- Surprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- Slot #32, PowerLimit 75.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Off, PwrInd On, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet+ LinkState- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- Capabilities: [100 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb:Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0:Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb:Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01 Status: NegoPending- InProgress- Capabilities: [140 v1] Root Complex Link Desc: PortNumber=02 ComponentID=01 EltType=Config Link0: Desc: TargetPort=00 TargetComponent=01 AssocRCRB- LinkType=MemMapped LinkValid+ Addr: fed19000 Kernel driver in use: pcieport 00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 02) (prog-if 00 [UHCI]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:5004] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
[Kernel-packages] [Bug 1637031] Re: In cold startup there is dark/blank screen
The real problem is grub. When I ran boot-repair, this tool gave the following answer: "The boot files of [The operating system being used - Ubuntu 14.04.5 LTS] are far from the beginning of the disk. Your BIOS might not detect them. You may want to retry it after creating a / boot partition (EXT4,> 200MB, beginning of the disk). This can be done with tools like gParted. Then select this partition via the [Partition / separate boot:] option in [Boot Repair]. (Https://help.ubuntu.com/community/BootPartition)". This problem is problematic to find because when I turn off the computer and then startup again several minutes later, the computer works very well, but if I startup the computer several hours later, the computer fails miserably. I think of that this problem is a bug because the manual in /usr/share/info/grub.info.gz says: "GRUB understands filesystems and kernel executable formats, so you can load an arbitrary operating system the way you like, without recording the physical position of your kernel on the disk.". If this is true, what: The boot files of [The operating system being used - Ubuntu 14.04.5 LTS] are far from the beginning of the disk, means? I do not know. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1637031 Title: In cold startup there is dark/blank screen Status in linux package in Ubuntu: Invalid Bug description: When I startup my computer, I can see very fast screen given any information. When cold startup process finish the screen is dark, usb mouse light is on, keyboard light is on, but the computer does not accept ctrl+alt+del and I must reboot with reset button on computer case. Several seconds latter, the screen displays such as hard drives, one ssd, are mounted and then the system information appears until the gnome desktop. This problem always appears in the cold start. I changed CR2032 motherboard battery and the problems continues. This problem first appeared in the update and upgrade kernel and grub cat /proc/version_signature Ubuntu 3.13.0-101.148-lowlatency 3.13.11-ckt39 sudo lspci -vnvn [sudo] password for hugo: 00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller [8086:29c0] (rev 02) Subsystem: Gigabyte Technology Co., Ltd Device [1458:5000] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:01.0 PCI bridge [0604]: Intel Corporation 82G33/G31/P35/P31 Express PCI Express Root Port [8086:29c1] (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [88] Subsystem: Gigabyte Technology Co., Ltd Device [1458:5000] Capabilities: [80] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0300c Data: 4191 Capabilities: [a0] Express (v1) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #2, Speed 2.5GT/s, Width x16, ASPM L0s, Exit Latency L0s <256ns, L1 <64us ClockPM- Surprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- Slot #32, PowerLimit 75.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Off, PwrInd On, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet+ LinkState- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible- RootCap: CRSVisible-
[Kernel-packages] [Bug 1637031] Re: In cold startup there is dark/blank screen
Answer to:Joseph Salisbury (jsalisbury) Firstly I want to say thanks a lot! Before I test the latest upstream kernel, I want to give more information about this problem 1) I was reading a web page: PC Repair and Maintenance: In-depth Look at Power Supply, that it was reading By Scott Mueller Feb 28, 2003 (http://www.informit.com/articles/article.aspx?p=31105) 2) In the page 2, I found the following paragraph that describes the problem: If you find that a system consistently fails to boot up properly the first time you turn on the switch, but that it subsequently boots up if you press the reset or Ctrl+Alt+Delete warm boot command, you likely have a problem with the Power_Good timing. You should install a new, higher-quality power supply and see whether that solves the problem. 3) The unique difference is that I need to push reset button case not Ctrl+Alt+delete because keyboard is death 4) I changed the power supply for another with 650 W output 5) But the problem continues: startup+reset to keep the computer running 6) I was reading carefully the following paragraphs: "The Power_Good Signal In addition to supplying electrical power to run the system, the power supply also ensures that the system does not run unless the power supplied is sufficient to operate the system properly. In other words, the power supply actually prevents the computer from starting up or operating until all the power supply voltages are within the proper ranges. The power supply completes internal checks and tests before allowing the system to start. If the tests are successful, the power supply sends a special signal to the motherboard, called Power_Good. This signal must be continuously present for the system to run. Therefore, when the AC voltage dips and the power supply cannot maintain outputs within regulation tolerance, the Power_Good signal is withdrawn (goes low) and forces the system to reset. The system will not restart until the Power_Good signal returns. The Power_Good signal (sometimes called Power_OK or PWR_OK) is a +5v (nominal) active high signal (with variation from +2.4v through +6.0v generally being considered acceptable) that is supplied to the motherboard when the power supply has passed its internal self tests and the output voltages have stabilized. This normally takes place anywhere from 100ms to 500ms (0.1–0.5 seconds) after you turn on the power supply switch. The power supply then sends the Power_Good signal to the motherboard, where the processor timer chip that controls the reset line to the processor receives it. In the absence of Power_Good, the timer chip holds the reset line on the processor, which prevents the system from running under bad or unstable power conditions. When the timer chip receives the Power_Good signal, it releases the reset, and the processor begins executing whatever code is at address : (usually the ROM BIOS). If the power supply cannot maintain proper outputs (such as when a brownout occurs), the Power_Good signal is withdrawn, and the processor is automatically reset. When the power output returns to its proper levels, the power supply regenerates the Power_Good signal and the system again begins operation (as if you had just powered on). By withdrawing Power_Good before the output voltages fall out of regulation, the system never sees the bad power because it is stopped quickly (reset) rather than being allowed to operate using unstable or improper power levels, which can cause memory parity errors and other problems." 7) My motherboard is a GIGABYTE P35-DS3L and pin 8 of the main power connector receives Power Good signal 8) When power supply is ON, the following occurs: the main task performed by SMPS, is to inform about the good power supply. As I told if the voltage is more/ or is less, in both the conditions a computer cannot work. As soon as you supply power to the computer, the SMPS checks the voltage level's its providing to the motherboard. If the power signal level is perfect, then SMPS will send a POWER GOOD signal to the motherboard timer.On receiving this POWER GOOD signal from SMPS, the motherboard timer will stop sending reset signal to the CPU. Which means the power level is good and the computer can boot. 9) Bootstrapping: Something has to be programmed by default, so that the CPU knows where to search for instructions. This is an address location in the ROM. This address location is almost always constant in X86 based computers. The address location is :h. This address location is the last region of the ROM. It only contains one instruction. The instruction is to jump to another memory address location. This JUMP command, will tell the location of the BIOS program in the ROM. This is how the computer will come to know where the BIOS program is located. 9) The Role of BIOS in booting process: The word booting comes from another word called bootstrapping. The computer knows how to bring itself up, when
[Kernel-packages] [Bug 1637031] [NEW] In cold startup there is dark/blank screen
Public bug reported: When I startup my computer, I can see very fast screen given any information. When cold startup process finish the screen is dark, usb mouse light is on, keyboard light is on, but the computer does not accept ctrl+alt+del and I must reboot with reset button on computer case. Several seconds latter, the screen displays such as hard drives, one ssd, are mounted and then the system information appears until the gnome desktop. This problem always appears in the cold start. I changed CR2032 motherboard battery and the problems continues. This problem first appeared in the update and upgrade kernel and grub cat /proc/version_signature Ubuntu 3.13.0-101.148-lowlatency 3.13.11-ckt39 sudo lspci -vnvn [sudo] password for hugo: 00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller [8086:29c0] (rev 02) Subsystem: Gigabyte Technology Co., Ltd Device [1458:5000] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:01.0 PCI bridge [0604]: Intel Corporation 82G33/G31/P35/P31 Express PCI Express Root Port [8086:29c1] (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [88] Subsystem: Gigabyte Technology Co., Ltd Device [1458:5000] Capabilities: [80] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0300c Data: 4191 Capabilities: [a0] Express (v1) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #2, Speed 2.5GT/s, Width x16, ASPM L0s, Exit Latency L0s <256ns, L1 <64us ClockPM- Surprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- Slot #32, PowerLimit 75.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Off, PwrInd On, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet+ LinkState- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- Capabilities: [100 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb:Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0:Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb:Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01 Status: NegoPending- InProgress- Capabilities: [140 v1] Root Complex Link Desc: PortNumber=02 ComponentID=01 EltType=Config Link0: Desc: TargetPort=00 TargetComponent=01 AssocRCRB- LinkType=MemMapped LinkValid+ Addr: fed19000 Kernel driver in use: pcieport 00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 02) (prog-if 00 [UHCI]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:5004] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v1) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0
