Re: [flashrom] join IRC
Hi, On 14.08.2018 19:50, Владимир Амельянович wrote: > I would be nice to get the patch. I will check my board tomorrow. > I have 3 different boards. Would you like to get reports from all of them? it seems the issue is already mitigated by other changes in the core of flashrom (though, the actual bug is still there). For the moment, it would be nice if you could try flashrom-1.0 to see if the issue persists. Nico ___ flashrom mailing list flashrom@flashrom.org https://mail.coreboot.org/mailman/listinfo/flashrom
Re: [flashrom] join IRC
On 14.08.2018 10:53, Владимир Амельянович wrote: > I made 3) > 3) verify image - flashrom -p > internal:laptop=force_I_want_a_brick,ich_spi_mode=auto > -v boxpc899_0.rom > > And result is VERIFIED. Heh, I missed this (your other mail went into another folder). So you can ignore my other mail, I guess. Though, if you want to try a patch for the error you've seen before, let me know :) Nico ___ flashrom mailing list flashrom@flashrom.org https://mail.coreboot.org/mailman/listinfo/flashrom
Re: [flashrom] join IRC
Hi Владимир, On 14.08.2018 09:46, Владимир Амельянович wrote: > I have tried to write saved image finally. And got the following message: > > FAILED! > Uh oh. Erase/write failed. Checking if anything has changed. > Reading current flash chip contents... Reading 8388608 bytes starting at > 0x00. > done. > Apparently at least some data has changed. > Your flash chip is in an unknown state. > Get help on IRC at chat.freenode.net (channel #flashrom) or > mail flashrom@flashrom.org with the subject "FAILED: "! > --- > DO NOT REBOOT OR POWEROFF! > Restoring MMIO space at 0x7fb5896f08a0 > Restoring PCI config space for 00:1f:0 reg 0xdc > > -V output attached. > > What should i do next? PC is power on. Try to verify (flashrom -v) the image you just wrote. I hope it just succeeded but run into an error afterwards. >From your log: >> 0x805000-0x805fff:E >> Request to erase some inaccessible memory address(es) (addr=0x805000, >> len=4096). Not erasing anything. This is already beyond your actual flash chip (0x80), so it al- ready wrote the image. I also found the cause for flashrom running off, your firmware descriptor seems misconfigured which triggered a bug in flashrom: >> 0xD0: 0x (FPB) This register is supposed to be 0 instead *shrug*. But there's obviously something to fix in flashrom to handle wrong values more gracefully. So, hope your board is fine, Nico 0xBD56B4A4138B3CE3.asc Description: application/pgp-keys ___ flashrom mailing list flashrom@flashrom.org https://mail.coreboot.org/mailman/listinfo/flashrom
Re: [flashrom] join IRC
I made 3) 3) verify image - flashrom -p internal:laptop=force_I_want_a_brick,ich_spi_mode=auto -v boxpc899_0.rom And result is VERIFIED. 2018-08-14 10:46 GMT+03:00 Владимир Амельянович < amelyanovich.vladi...@gmail.com>: > Hello, > > 1) save image - flashrom -p > internal:laptop=force_I_want_a_brick,ich_spi_mode=auto > -r boxpc899_0.rom > 2) write image - flashrom -p > internal:laptop=force_I_want_a_brick,ich_spi_mode=auto > -w boxpc899_0.rom -V -o /lib/live/mount/medium/ > > I have tried to write saved image finally. And got the following message: > > FAILED! > Uh oh. Erase/write failed. Checking if anything has changed. > Reading current flash chip contents... Reading 8388608 bytes starting at > 0x00. > done. > Apparently at least some data has changed. > Your flash chip is in an unknown state. > Get help on IRC at chat.freenode.net (channel #flashrom) or > mail flashrom@flashrom.org with the subject "FAILED: "! > > --- > DO NOT REBOOT OR POWEROFF! > Restoring MMIO space at 0x7fb5896f08a0 > Restoring PCI config space for 00:1f:0 reg 0xdc > > -V output attached. > > What should i do next? PC is power on. > > > 2018-08-09 23:16 GMT+03:00 Владимир Амельянович < > amelyanovich.vladi...@gmail.com>: > >> Hello Nico, >> >> Thank you very much for your information. >> >> Does the image of SPI chip which i get with -r key contain BIOS firmware >> or BIOS settings or both? >> My goal is to create BIOS master image which i can write to 10,20,100 >> devices with same hardware. >> >> Regards, >> Vladimir >> >> >> 2018-08-09 22:11 GMT+03:00 Nico Huber : >> >>> Hi Владимир, >>> >>> On 08.08.2018 10:07, Владимир Амельянович wrote: >>> flashrom -p internal:laptop=this_is_not_a_laptop didn't change anything >>> >>> yes, because your BIOS claims that it's a laptop: `DMI string >>> chassis-type: "Notebook"`. >>> >>> flashrom -p internal:laptop=force_I_want_a_brick show more info. Logs with different V number are attached. Please could you please tell me if i can use flashrom in my case? >>> >>> You already did. If you let it probe with the above force option, >>> it can already harm some laptops. But in your case (SPI chip directly >>> attached) it's safe. You can go ahead (if you have a valid image to >>> flash). In either case of success of failure, please always keep >>> logs (best use the -o option) and report back. >>> >>> Please note that your message got filtered from the mailing list (there >>> is a 256KiB limit for the mail size). So I'll attach your least verbose >>> log for reference. >>> >>> Regards, >>> Nico >>> >> >> > ___ flashrom mailing list flashrom@flashrom.org https://mail.coreboot.org/mailman/listinfo/flashrom
Re: [flashrom] join IRC
Hello, 1) save image - flashrom -p internal:laptop=force_I_want_a_brick,ich_spi_mode=auto -r boxpc899_0.rom 2) write image - flashrom -p internal:laptop=force_I_want_a_brick,ich_spi_mode=auto -w boxpc899_0.rom -V -o /lib/live/mount/medium/ I have tried to write saved image finally. And got the following message: FAILED! Uh oh. Erase/write failed. Checking if anything has changed. Reading current flash chip contents... Reading 8388608 bytes starting at 0x00. done. Apparently at least some data has changed. Your flash chip is in an unknown state. Get help on IRC at chat.freenode.net (channel #flashrom) or mail flashrom@flashrom.org with the subject "FAILED: "! --- DO NOT REBOOT OR POWEROFF! Restoring MMIO space at 0x7fb5896f08a0 Restoring PCI config space for 00:1f:0 reg 0xdc -V output attached. What should i do next? PC is power on. 2018-08-09 23:16 GMT+03:00 Владимир Амельянович < amelyanovich.vladi...@gmail.com>: > Hello Nico, > > Thank you very much for your information. > > Does the image of SPI chip which i get with -r key contain BIOS firmware > or BIOS settings or both? > My goal is to create BIOS master image which i can write to 10,20,100 > devices with same hardware. > > Regards, > Vladimir > > > 2018-08-09 22:11 GMT+03:00 Nico Huber : > >> Hi Владимир, >> >> On 08.08.2018 10:07, Владимир Амельянович wrote: >> >>> flashrom -p internal:laptop=this_is_not_a_laptop didn't change anything >>> >> >> yes, because your BIOS claims that it's a laptop: `DMI string >> chassis-type: "Notebook"`. >> >> flashrom -p internal:laptop=force_I_want_a_brick show more info. Logs >>> with >>> different V number are attached. >>> Please could you please tell me if i can use flashrom in my case? >>> >> >> You already did. If you let it probe with the above force option, >> it can already harm some laptops. But in your case (SPI chip directly >> attached) it's safe. You can go ahead (if you have a valid image to >> flash). In either case of success of failure, please always keep >> logs (best use the -o option) and report back. >> >> Please note that your message got filtered from the mailing list (there >> is a 256KiB limit for the mail size). So I'll attach your least verbose >> log for reference. >> >> Regards, >> Nico >> > > flashrom v0.9.9-r1954 on Linux 4.15.0-2-amd64 (x86_64) flashrom was built with libpci 3.5.2, GCC 6.3.0 20170221, little endian Command line (7 args): flashrom -p internal:laptop=force_I_want_a_brick,ich_spi_mode=auto -w boxpc899_0.rom -V -o /lib/live/mount/medium/flashrom899write.log Calibrating delay loop... OS timer resolution is 1 usecs, 1374M loops per second, 10 myus = 10 us, 100 myus = 98 us, 1000 myus = 984 us, 1 myus = 11855 us, 4 myus = 4 us, OK. Initializing internal programmer No coreboot table found. Using Internal DMI decoder. DMI string chassis-type: "Notebook" Laptop detected via DMI. DMI string system-manufacturer: "To be filled by O.E.M." DMI string system-product-name: "To be filled by O.E.M." DMI string system-version: "To be filled by O.E.M." DMI string baseboard-manufacturer: "INTEL Corporation" DMI string baseboard-product-name: "CRESCENTBAY" DMI string baseboard-version: "To be filled by O.E.M." WARNING! You seem to be running flashrom on an unsupported laptop. Laptops, notebooks and netbooks are difficult to support and we recommend to use the vendor flashing utility. The embedded controller (EC) in these machines often interacts badly with flashing. See the manpage and https://flashrom.org/Laptops for details. If flash is shared with the EC, erase is guaranteed to brick your laptop and write may brick your laptop. Read and probe may irritate your EC and cause fan failure, backlight failure and sudden poweroff. You have been warned. Proceeding anyway because user forced us to. Found chipset "Intel Lynx Point LP Mainstream" with PCI ID 8086:9c45. This chipset is marked as untested. If you are using an up-to-date version of flashrom *and* were (not) able to successfully update your firmware with it, then please email a report to flashrom@flashrom.org including a verbose (-V) log. Thank you! Enabling flash write... Root Complex Register Block address = 0xfed1c000 GCS = 0x61: BIOS Interface Lock-Down: enabled, Boot BIOS Straps: 0x0 (SPI) Top Swap: enabled (A16(+) inverted) 0xfff8/0xffb8 FWH IDSEL: 0x0 0xfff0/0xffb0 FWH IDSEL: 0x0 0xffe8/0xffa8 FWH IDSEL: 0x1 0xffe0/0xffa0 FWH IDSEL: 0x1 0xffd8/0xff98 FWH IDSEL: 0x2 0xffd0/0xff90 FWH IDSEL: 0x2 0xffc8/0xff88 FWH IDSEL: 0x3 0xffc0/0xff80 FWH IDSEL: 0x3 0xff70/0xff30 FWH IDSEL: 0x4 0xff60/0xff20 FWH IDSEL: 0x5 0xff50/0xff10 FWH IDSEL: 0x6 0xff40/0xff00 FWH IDSEL: 0x7 0xfff8/0xffb8 FWH
Re: [flashrom] join IRC
Hello Nico, Thank you very much for your information. Does the image of SPI chip which i get with -r key contain BIOS firmware or BIOS settings or both? My goal is to create BIOS master image which i can write to 10,20,100 devices with same hardware. Regards, Vladimir 2018-08-09 22:11 GMT+03:00 Nico Huber : > Hi Владимир, > > On 08.08.2018 10:07, Владимир Амельянович wrote: > >> flashrom -p internal:laptop=this_is_not_a_laptop didn't change anything >> > > yes, because your BIOS claims that it's a laptop: `DMI string > chassis-type: "Notebook"`. > > flashrom -p internal:laptop=force_I_want_a_brick show more info. Logs with >> different V number are attached. >> Please could you please tell me if i can use flashrom in my case? >> > > You already did. If you let it probe with the above force option, > it can already harm some laptops. But in your case (SPI chip directly > attached) it's safe. You can go ahead (if you have a valid image to > flash). In either case of success of failure, please always keep > logs (best use the -o option) and report back. > > Please note that your message got filtered from the mailing list (there > is a 256KiB limit for the mail size). So I'll attach your least verbose > log for reference. > > Regards, > Nico > ___ flashrom mailing list flashrom@flashrom.org https://mail.coreboot.org/mailman/listinfo/flashrom
Re: [flashrom] join IRC
Hi Владимир, On 08.08.2018 10:07, Владимир Амельянович wrote: flashrom -p internal:laptop=this_is_not_a_laptop didn't change anything yes, because your BIOS claims that it's a laptop: `DMI string chassis-type: "Notebook"`. flashrom -p internal:laptop=force_I_want_a_brick show more info. Logs with different V number are attached. Please could you please tell me if i can use flashrom in my case? You already did. If you let it probe with the above force option, it can already harm some laptops. But in your case (SPI chip directly attached) it's safe. You can go ahead (if you have a valid image to flash). In either case of success of failure, please always keep logs (best use the -o option) and report back. Please note that your message got filtered from the mailing list (there is a 256KiB limit for the mail size). So I'll attach your least verbose log for reference. Regards, Nico flashrom v0.9.9-r1954 on Linux 4.15.0-2-amd64 (x86_64) flashrom is free software, get the source code at https://flashrom.org flashrom was built with libpci 3.5.2, GCC 6.3.0 20170221, little endian Command line (3 args): flashrom -V -p internal:laptop=force_I_want_a_brick Calibrating delay loop... OS timer resolution is 1 usecs, 1795M loops per second, 10 myus = 10 us, 100 myus = 100 us, 1000 myus = 1000 us, 1 myus = 10003 us, 4 myus = 4 us, OK. Initializing internal programmer No coreboot table found. Using Internal DMI decoder. DMI string chassis-type: "Notebook" Laptop detected via DMI. DMI string system-manufacturer: "To be filled by O.E.M." DMI string system-product-name: "To be filled by O.E.M." DMI string system-version: "To be filled by O.E.M." DMI string baseboard-manufacturer: "INTEL Corporation" DMI string baseboard-product-name: "MAHOBAY" DMI string baseboard-version: "To be filled by O.E.M." Found ITE Super I/O, ID 0x8782 on port 0x2e Found chipset "Intel HM65" with PCI ID 8086:1c49. This chipset is marked as untested. If you are using an up-to-date version of flashrom *and* were (not) able to successfully update your firmware with it, then please email a report to flashrom@flashrom.org including a verbose (-V) log. Thank you! Enabling flash write... Root Complex Register Block address = 0xfed1c000 GCS = 0xc61: BIOS Interface Lock-Down: enabled, Boot BIOS Straps: 0x3 (SPI) Top Swap: enabled (A16(+) inverted) 0xfff8/0xffb8 FWH IDSEL: 0x0 0xfff0/0xffb0 FWH IDSEL: 0x0 0xffe8/0xffa8 FWH IDSEL: 0x1 0xffe0/0xffa0 FWH IDSEL: 0x1 0xffd8/0xff98 FWH IDSEL: 0x2 0xffd0/0xff90 FWH IDSEL: 0x2 0xffc8/0xff88 FWH IDSEL: 0x3 0xffc0/0xff80 FWH IDSEL: 0x3 0xff70/0xff30 FWH IDSEL: 0x4 0xff60/0xff20 FWH IDSEL: 0x5 0xff50/0xff10 FWH IDSEL: 0x6 0xff40/0xff00 FWH IDSEL: 0x7 0xfff8/0xffb8 FWH decode enabled 0xfff0/0xffb0 FWH decode enabled 0xffe8/0xffa8 FWH decode enabled 0xffe0/0xffa0 FWH decode enabled 0xffd8/0xff98 FWH decode enabled 0xffd0/0xff90 FWH decode enabled 0xffc8/0xff88 FWH decode enabled 0xffc0/0xff80 FWH decode enabled 0xff70/0xff30 FWH decode enabled 0xff60/0xff20 FWH decode enabled 0xff50/0xff10 FWH decode enabled 0xff40/0xff00 FWH decode enabled Maximum FWH chip size: 0x10 bytes SPI Read Configuration: prefetching enabled, caching enabled, BIOS_CNTL = 0x09: BIOS Lock Enable: disabled, BIOS Write Enable: enabled SPIBAR = 0x7f8a329c2000 + 0x3800 0x04: 0xe008 (HSFS) HSFS: FDONE=0, FCERR=0, AEL=0, BERASE=1, SCIP=0, FDOPSS=1, FDV=1, FLOCKDN=1 Reading OPCODES... done 0x06: 0x (HSFC) HSFC: FGO=0, FCYCLE=0, FDBC=0, SME=0 0x50: 0x (FRAP) BMWAG 0x00, BMRAG 0x00, BRWA 0xff, BRRA 0xff 0x54: 0x FREG0: Flash Descriptor region (0x-0x0fff) is read-write. 0x58: 0x03ff0180 FREG1: BIOS region (0x0018-0x003f) is read-write. 0x5C: 0x017f0001 FREG2: Management Engine region (0x1000-0x0017) is read-write. 0x90: 0x84 (SSFS) SSFS: SCIP=0, FDONE=1, FCERR=0, AEL=0 0x91: 0xf94240 (SSFC) SSFC: SCGO=0, ACS=0, SPOP=0, COP=4, DBC=2, SME=0, SCF=1 0x94: 0x0006 (PREOP) 0x96: 0x043b (OPTYPE) 0x98: 0x05200302 (OPMENU) 0x9C: 0x019f (OPMENU+4) 0xA0: 0x (BBAR) 0xC4: 0x00802005 (LVSCC) LVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20, VCL=1 0xC8: 0x2005 (UVSCC) UVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20 0xD0: 0x (FPB) OK. The following protocols are supported: FWH, SPI. Probing for AMIC A25L05PT, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for AMIC A25L05PU, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for AMIC A25L10PT, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for AMIC A25L10PU, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for AMIC A25L20PT, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for AMIC A25L20PU, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for AMIC A25L40PT, 512 kB:
Re: [flashrom] join IRC
Hello Владимир, On 07.08.2018 11:14, Владимир Амельянович wrote: > Thank you for information. > One more question. > I have industrial PC, manufacturer didn't provide any BIOS tool. > When i run flashrom i get the warning about problems with unsupported > laptops BIOSes and the following message: > "Aborting. > Error: Programmer initialization failed" > I use command "flashrom -p internal" > How could i fix it? whether or not flashing is safe despite this message depends on your board. If you provide a verbose log for this board, we might be able to tell you more. For instance, newer systems with the BIOS flash con- nected through SPI to the southbridge or almost always safe to flash (you can see in the manpage how to tell flashrom that your board is not a laptop, or that it should flash anyway). Hope that helps, Nico ___ flashrom mailing list flashrom@flashrom.org https://mail.coreboot.org/mailman/listinfo/flashrom
Re: [flashrom] join IRC
Maybe it would've been easier to just tear down that PC and directly connect to a BIOS chip (In-System Programming, using some test clip to avoid the soldering, or maybe your chip is socketed so you could remove it and insert to your hardware programmer). Although this way requires you to have the external programmer, there are some models like CH341A which could be got for really cheap ($2-$3 from China in this case). And there is 100% confidence that this way will work, regardless of your chipset and other factors On Tue, Aug 7, 2018 at 12:14 PM, Владимир Амельянович wrote: > Thank you for information. > One more question. > I have industrial PC, manufacturer didn't provide any BIOS tool. > When i run flashrom i get the warning about problems with unsupported > laptops BIOSes and the following message: > "Aborting. > Error: Programmer initialization failed" > I use command "flashrom -p internal" > How could i fix it? > > 2018-08-06 14:17 GMT+03:00 Stefan Tauner : >> >> On Mon, 6 Aug 2018 10:07:47 +0300 >> Владимир Амельянович wrote: >> >> > Hello. >> > Please could you help me? >> > I have chipset "Intel ICH7/ICH7R". It is marked as fully supported. I >> > did >> > the following steps 1) made backup 2) changed some setting(disable >> > internal >> > audio) 3) made backup again. I made hexdump comparision of files from >> > steps 1), 3) and there are no changes at all. What did i wrong? >> > >> >> Hi, >> >> there is nothing wrong. On old boards such settings are often saved in >> the CMOS NVRAM, which is not part of the flash memory. >> >> -- >> Kind regards/Mit freundlichen Grüßen, Stefan Tauner > > > > ___ > flashrom mailing list > flashrom@flashrom.org > https://mail.coreboot.org/mailman/listinfo/flashrom ___ flashrom mailing list flashrom@flashrom.org https://mail.coreboot.org/mailman/listinfo/flashrom
Re: [flashrom] join IRC
Thank you for information. One more question. I have industrial PC, manufacturer didn't provide any BIOS tool. When i run flashrom i get the warning about problems with unsupported laptops BIOSes and the following message: "Aborting. Error: Programmer initialization failed" I use command "flashrom -p internal" How could i fix it? 2018-08-06 14:17 GMT+03:00 Stefan Tauner : > On Mon, 6 Aug 2018 10:07:47 +0300 > Владимир Амельянович wrote: > > > Hello. > > Please could you help me? > > I have chipset "Intel ICH7/ICH7R". It is marked as fully supported. I did > > the following steps 1) made backup 2) changed some setting(disable > internal > > audio) 3) made backup again. I made hexdump comparision of files from > > steps 1), 3) and there are no changes at all. What did i wrong? > > > > Hi, > > there is nothing wrong. On old boards such settings are often saved in > the CMOS NVRAM, which is not part of the flash memory. > > -- > Kind regards/Mit freundlichen Grüßen, Stefan Tauner > ___ flashrom mailing list flashrom@flashrom.org https://mail.coreboot.org/mailman/listinfo/flashrom
Re: [flashrom] join IRC
On Mon, 6 Aug 2018 10:07:47 +0300 Владимир Амельянович wrote: > Hello. > Please could you help me? > I have chipset "Intel ICH7/ICH7R". It is marked as fully supported. I did > the following steps 1) made backup 2) changed some setting(disable internal > audio) 3) made backup again. I made hexdump comparision of files from > steps 1), 3) and there are no changes at all. What did i wrong? > Hi, there is nothing wrong. On old boards such settings are often saved in the CMOS NVRAM, which is not part of the flash memory. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner ___ flashrom mailing list flashrom@flashrom.org https://mail.coreboot.org/mailman/listinfo/flashrom
Re: [flashrom] join IRC
Hello. Please could you help me? I have chipset "Intel ICH7/ICH7R". It is marked as fully supported. I did the following steps 1) made backup 2) changed some setting(disable internal audio) 3) made backup again. I made hexdump comparision of files from steps 1), 3) and there are no changes at all. What did i wrong? Best regards, Vladimir 2018-08-02 2:46 GMT+03:00 Stefan Tauner : > On Thu, 2 Aug 2018 00:42:57 +0200 > Stefan Tauner wrote: > > > joining and speaking is possible with unregistered user names again. > > Well, that turned out to be a bit too optimistic on my part... we have > re-enabled the mute mode for unregistered users for the time being. But > anybody can join the channel and request permission to speak by sending > a message to one of the operators if need be. Just registering your > current nickname on freenode is of course preferred: > /msg NickServ REGISTER password yourem...@example.com > when connected with your desired nickname. > -- > Kind regards/Mit freundlichen Grüßen, Stefan Tauner > ___ flashrom mailing list flashrom@flashrom.org https://mail.coreboot.org/mailman/listinfo/flashrom
Re: [flashrom] join IRC
On Thu, 2 Aug 2018 00:42:57 +0200 Stefan Tauner wrote: > joining and speaking is possible with unregistered user names again. Well, that turned out to be a bit too optimistic on my part... we have re-enabled the mute mode for unregistered users for the time being. But anybody can join the channel and request permission to speak by sending a message to one of the operators if need be. Just registering your current nickname on freenode is of course preferred: /msg NickServ REGISTER password yourem...@example.com when connected with your desired nickname. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner ___ flashrom mailing list flashrom@flashrom.org https://mail.coreboot.org/mailman/listinfo/flashrom
Re: [flashrom] join IRC
On Wed, 1 Aug 2018 15:28:24 +0200 Stefan Tauner wrote: > On Wed, 1 Aug 2018 11:27:12 +0300 > Владимир Амельянович wrote: > > > Hello. > > > > Please could you help me join your IRC chanel? > > I have registered at freenode. But i recieve the following message: > > > > hello > > * #flashrom :Cannot send to channel > > Hi Владимир, > > you need not only to register but also to identify (I am not sure if > that happens automatically when you register). Have you done that? > The restrictions is due to a spam wave on freenode and we are looking > for alternatives but that will take a while. Hi, joining and speaking is possible with unregistered user names again. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner ___ flashrom mailing list flashrom@flashrom.org https://mail.coreboot.org/mailman/listinfo/flashrom
Re: [flashrom] join IRC
On Wed, 1 Aug 2018 11:27:12 +0300 Владимир Амельянович wrote: > Hello. > > Please could you help me join your IRC chanel? > I have registered at freenode. But i recieve the following message: > > hello > * #flashrom :Cannot send to channel Hi Владимир, you need not only to register but also to identify (I am not sure if that happens automatically when you register). Have you done that? The restrictions is due to a spam wave on freenode and we are looking for alternatives but that will take a while. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner ___ flashrom mailing list flashrom@flashrom.org https://mail.coreboot.org/mailman/listinfo/flashrom
